From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 00:05:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2085116A402 for ; Sun, 9 Apr 2006 00:05:08 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 937AB43D46 for ; Sun, 9 Apr 2006 00:05:06 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k39052Cp020313; Sat, 8 Apr 2006 18:05:02 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44384FAD.8020608@samsco.org> Date: Sat, 08 Apr 2006 18:05:01 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Huff References: <44354224.6090002@errno.com> <17464.19693.901106.621298@jerusalem.litteratus.org> In-Reply-To: <17464.19693.901106.621298@jerusalem.litteratus.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Kernel Quality? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 00:05:08 -0000 Robert Huff wrote: > Sam Leffler writes: > > >> OTOH we've done nothing with user application code and based on >> the work I've seen done by netbsd there's plenty of stuff to be >> fixed there. > > > When you say "user application code", is this an alias for > ports or do you mean non-ported applications? > > > Robert Huff "user application code" == code not in src/sys/... That means src/lib, src/bin, src/sbin, src/usr.bin, etc. Scott From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 00:28:22 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D2E116A401 for ; Sun, 9 Apr 2006 00:28:22 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC6E843D45 for ; Sun, 9 Apr 2006 00:28:21 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id BDE7319F2C; Sat, 8 Apr 2006 17:28:20 -0700 (PDT) Message-ID: <44385525.8000203@bitfreak.org> Date: Sat, 08 Apr 2006 17:28:21 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Mike Meyer References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <20060408224140.GA15366@outcold.yadt.co.uk> <17464.17494.251794.271711@bhuda.mired.org> In-Reply-To: <17464.17494.251794.271711@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 00:28:22 -0000 Mike Meyer wrote: > In <20060408224140.GA15366@outcold.yadt.co.uk>, David Taylor typed: >> That doesn't quite work, though. Unless you require everyone wanting >> to distinguish between LAN and WAN interfaces uses different types >> of hardware for each card, they'll still end up with xl0 and xl1 >> (or whatever), which is in no way better than eth0 and eth1, > > You're right - but at least you have the option of using different > types of cards to get different names. I agree that this sucks, but > it's better than nothing. This is a script to rename interfaces based on the MAC address: #!/bin/csh set mac_list = "/etc/MACaddr_list" foreach ifn ( `ifconfig -l link` ) set ifn_mac = "`ifconfig $ifn link | grep ether | cut -d ' ' -f 2`" set ifn_name = "`grep $ifn_mac $mac_list | cut -d ' ' -f 2`" ifconfig $ifn name $ifn_name end Where /etc/MACaddr_list contains entries of the format: 00:00:00:00:00:00 NameLengthMax15 If you add something to /etc/rc.d so that a sh-ified version of this script runs after all interfaces have attached but before any numbering or cloning takes place you can have lines like this in /etc/rc.conf: ifconfig_PublicLAN="inet a.b.c.d/24" That's far better than trying to remember what's on em0. This is an off-the-top-of-my-head, 2-minute solution, largely untested due to present lack of a victim machine. pf doesn't seem to have any issue, but I haven't tested /etc/rc.d/netif, dhclient, wpa_supplicant, interface cloning and other things people do to their network interfaces. An rc-friendly version would probably make use of something like: ifconfig_UsefulName_linkaddr="00:00:00:00:00:00" in /etc/rc.conf rather than a seperate file, but this is just a proof of concept. Comments please! From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 00:57:15 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93C5716A403 for ; Sun, 9 Apr 2006 00:57:15 +0000 (UTC) (envelope-from dd@freebsd.org) Received: from charade.trit.org (charade.trit.org [65.19.139.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32A4243D48 for ; Sun, 9 Apr 2006 00:57:15 +0000 (GMT) (envelope-from dd@freebsd.org) Received: from maverick.trit.org (maverick.trit.org [IPv6:2001:4830:2381:2062:212:f0ff:fe4c:896a]) by charade.trit.org (Postfix) with ESMTP id C582F1AF62E; Sun, 9 Apr 2006 00:57:14 +0000 (UTC) Received: from maverick.trit.org (localhost [127.0.0.1]) by maverick.trit.org (8.13.6/8.13.4) with ESMTP id k390vEdt060834; Sun, 9 Apr 2006 00:57:14 GMT (envelope-from dd@freebsd.org) Received: (from dima@localhost) by maverick.trit.org (8.13.6/8.13.4/Submit) id k390vDOR060832; Sun, 9 Apr 2006 00:57:13 GMT (envelope-from dd@freebsd.org) X-Authentication-Warning: maverick.trit.org: dima set sender to dd@freebsd.org using -f Date: Sun, 9 Apr 2006 00:57:13 +0000 From: Dima Dorfman To: Mike Meyer Message-ID: <20060409005712.GA856@trit.org> References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <443811EF.2020509@samsco.org> <17464.8074.937742.701480@bhuda.mired.org> <44383346.2030207@samsco.org> <17464.16087.217524.843667@bhuda.mired.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <17464.16087.217524.843667@bhuda.mired.org> X-PGP-Key: 69FAE582 (https://www.trit.org/~dima/dima.asc) X-PGP-Fingerprint: B340 8338 7DA3 4D61 7632 098E 0730 055B 69FA E582 User-Agent: Mutt/1.5.9i Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 00:57:15 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Mike Meyer wrote: > What do I want for that? I identify ethernet boards by which slot on > the back of the system I plug the cable into. Currently, I have to map > that to board types to and which board is plugged into which slot to > know which name to use. I want a name that tells me which slot I plug > a cable in to plug it into that interface. Is information about the slot even available on a PC? For something like this: : em0@pci6:7:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 hdr=0x00 : vendor = 'Intel Corporation' : device = '82547EI Gigabit Ethernet Controller' : class = network : subclass = ethernet would you consider eth-6-7-0 to be an improvement over em0? It has the advantage of not changing if another card is added to the system, but it's not very informative. For a system that has only its two on-board NICs, "em0" and "em1" are very obvious--at least it's clear which one corresponds to the label "eth 0" on the chassis. --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFEOFvoBzAFW2n65YIRArj9AJ4vBLlHsCNfgSpEVtNCEESWcAxSGQCeKcz4 dikHHTP5TU+99KlYMaLW7dY= =uSwv -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 01:07:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F50D16A403 for ; Sun, 9 Apr 2006 01:07:33 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11A4343D45 for ; Sun, 9 Apr 2006 01:07:32 +0000 (GMT) (envelope-from roberthuff@rcn.com) Received: from 209-6-22-29.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.29]) by smtp02.lnh.mail.rcn.net with ESMTP; 08 Apr 2006 21:07:31 -0400 X-IronPort-AV: i="4.04,103,1144036800"; d="scan'208"; a="221166648:sNHT111995314" From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17464.24074.871941.332919@jerusalem.litteratus.org> Date: Sat, 8 Apr 2006 21:06:18 -0400 To: freebsd-hackers@freebsd.org In-Reply-To: <44384FAD.8020608@samsco.org> References: <44354224.6090002@errno.com> <17464.19693.901106.621298@jerusalem.litteratus.org> <44384FAD.8020608@samsco.org> X-Mailer: VM 7.17 under 21.5 (beta26) "endive" XEmacs Lucid Subject: Re: FreeBSD Kernel Quality? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 01:07:33 -0000 Scott Long writes: > > When you say "user application code", is this an alias for > > ports or do you mean non-ported applications? > > "user application code" == code not in src/sys/... That means > src/lib, src/bin, src/sbin, src/usr.bin, etc. Got it. Thanks. Robert Huff From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 01:28:03 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE4816A400 for ; Sun, 9 Apr 2006 01:28:03 +0000 (UTC) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0ABA143D48 for ; Sun, 9 Apr 2006 01:28:02 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5D240.dip.t-dialin.net [84.165.210.64]) by deadcafe.de (8.13.6/8.13.4/Rock) with ESMTP id k391S0iv066489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 9 Apr 2006 03:28:01 +0200 (CEST) X-Envelope-To: Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id k391RgpF058260 for ; Sun, 9 Apr 2006 03:27:42 +0200 (CEST) Message-ID: <4438630E.4090300@deadcafe.de> Date: Sun, 09 Apr 2006 03:27:42 +0200 From: Daniel Rock User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: hackers@freebsd.org References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <20060408233740.GA84768@submonkey.net> <44384A55.2010103@samsco.org> In-Reply-To: <44384A55.2010103@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de X-Mailman-Approved-At: Sun, 09 Apr 2006 02:08:59 +0000 Cc: Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 01:28:03 -0000 Scott Long schrieb: > Ceri Davies wrote: > >> On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote: > >>> Well, the real question is why we force the details of driver names >>> onto users. Network and storage drivers are especially guilty of >>> this, but tty devices also are annoying. How do you know which manual page to read for driver specifics if they are all named eth0, eth1, ... With the current naming scheme you know when to read the man page for em(4), fxp(4), nve(4), ... > I'll say again, how does having em0, em1, em2, and em3 help me know what > is going on with each of those interfaces? FreeBSD doesn't support persistent instance numbering, unlike Solaris. If you unplug device em0 in FreeBSD the remaining interfaces get renamed em0, em1, em2 - which is a bad thing. If you unplug e1000g0 in Solaris the remaining interfaces will still be named e1000g1, e1000g2, e1000g3. So I doubt that the overwriting of an Ingres database really happened in Solaris, like some other poster described - unless the administrator fiddled with /etc/path_to_inst by hand (you are free to shoot in your own foot). Daniel From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 02:34:13 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2078616A400 for ; Sun, 9 Apr 2006 02:34:13 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 709E843D45 for ; Sun, 9 Apr 2006 02:34:12 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 73574 invoked by uid 1001); 9 Apr 2006 02:34:11 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Sat, 08 Apr 2006 22:34:11 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17464.29347.529203.354768@bhuda.mired.org> Date: Sat, 8 Apr 2006 22:34:11 -0400 To: Daniel Rock In-Reply-To: <4438630E.4090300@deadcafe.de> References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <20060408233740.GA84768@submonkey.net> <44384A55.2010103@samsco.org> <4438630E.4090300@deadcafe.de> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 02:34:13 -0000 In <4438630E.4090300@deadcafe.de>, Daniel Rock typed: > So I doubt that the overwriting of an Ingres database really > happened in Solaris, like some other poster described - unless the > administrator fiddled with /etc/path_to_inst by hand (you are free > to shoot in your own foot). That happened very early in the life of Solaris, in the early 90s. Persistent numbering was added to Solaris in response to this incident (there were probably others as well). This was on a relatively large server, with something like 4 SCSI buses. A drive was added to a previously unused bus, making it appear "between" two drives that were already in the system. This gave all the drives further on in the probe sequence a device number one higher than they had previously had. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 02:44:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A64516A402 for ; Sun, 9 Apr 2006 02:44:49 +0000 (UTC) (envelope-from ashok.shrestha@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5921643D49 for ; Sun, 9 Apr 2006 02:44:48 +0000 (GMT) (envelope-from ashok.shrestha@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so491699nfc for ; Sat, 08 Apr 2006 19:44:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=J8k0+Ei6P9pqQuHluynbaWmEk3K3F+Ya+MPXx/7Bv03X2Nh9tWUNC7bhOm8LGPeSUumOF8pIrC1zonWZeEBcdNr2X3wYCZQNNueZtAyTdAkX+6i9XG0MN1z5AJvuH3I+ERAyy6qtg7xHdMA/6NmW375fW9GLy/PTlv1WkRVZ2QM= Received: by 10.49.8.9 with SMTP id l9mr2828702nfi; Sat, 08 Apr 2006 19:44:47 -0700 (PDT) Received: by 10.49.93.3 with HTTP; Sat, 8 Apr 2006 19:44:47 -0700 (PDT) Message-ID: <79e2026f0604081944m79d1621cv1668266689fd5f3f@mail.gmail.com> Date: Sat, 8 Apr 2006 22:44:47 -0400 From: "Ashok Shrestha" To: freebsd-perl@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <79e2026f0604081616h2dab7552m38b7d53744c474db@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <79e2026f0604081616h2dab7552m38b7d53744c474db@mail.gmail.com> Cc: Subject: Re: Net::FTPSSL error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 02:44:49 -0000 Adding freebsd-hackers@freebsd.org On 4/8/06, Ashok Shrestha wrote: > Hi all, > > System Info: > FreeBSD 6.0-RELEASE > bsdpan-Net-FTPSSL-0.04 > p5-Net-SSLeay-1.30_1 > perl-5.8.7 > > > > I'm trying to use Net::FTPSSL to connect to an FTP server via SSL. > > > > Here is the script: > > #!/usr/bin/perl -w > > use Net::FTPSSL; > > my $ftps =3D Net::FTPSSL->new('127.0.0.1', > 'Encryption' =3D> 'E', > 'Debug' =3D> 1, > 'Timeout' =3D> 20) > or die "Can't open 127.0.0.1"; > > $ftps->login('username123', 'password123') or die "Can't login: ", > $ftps->$last_message(); > > $ftps->cwd("/working") or die "Can't change directory: ", $ftps->last_m= essage; > > $ftps->get("C13.txt") or die "Can't get file: ", $ftps->last_message; > > $ftps->quit(); > > > > > Here is my error: > ./test_FTPSSL.pl > Name "main::last_message" used only once: possible typo at > ./test_FTPSSL.pl line 11. > >>> USER username123 > <<< 331 Please specify the password. > >>> PASS password123 > Use of uninitialized value in length at (eval 7) line 1. > Use of uninitialized value in string eq at blib/lib/Net/SSLeay.pm > (autosplit into blib/lib/auto/Net/S > > SLeay/ssl_read_all.al) line 1615. > Can't read on socket: at ./test_FTPSSL.pl line 11 > > > > > > Are there any relevant conf files I should post? Any ideas how to > resolve this issue? > > > > > > > -- Ashok Shrestha > -- Ashok Shrestha From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 02:45:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBEEF16A403 for ; Sun, 9 Apr 2006 02:45:41 +0000 (UTC) (envelope-from ashok.shrestha@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A53143D45 for ; Sun, 9 Apr 2006 02:45:40 +0000 (GMT) (envelope-from ashok.shrestha@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so491739nfc for ; Sat, 08 Apr 2006 19:45:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Po6B/cJ/a+7y2MK5YxUG3+HS1RPCBXn2F3MZ8vHXbESNMUsUYNX5C+H3v2f3BgPVUr7NrSMyQF78xGaV7BO2GY7p3DV6zKsEvk5XcIByWODlivzDcsAbtvHhTC6jffdwst6EtSKKO5UckXhq6mE0dQQOx1gDPYAD1sjnsThVrvo= Received: by 10.49.90.6 with SMTP id s6mr2269647nfl; Sat, 08 Apr 2006 19:45:39 -0700 (PDT) Received: by 10.49.93.3 with HTTP; Sat, 8 Apr 2006 19:45:39 -0700 (PDT) Message-ID: <79e2026f0604081945s5330b394tb09cf4a9db32a2e0@mail.gmail.com> Date: Sat, 8 Apr 2006 22:45:39 -0400 From: "Ashok Shrestha" To: freebsd-perl@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <79e2026f0604081606w3f9327dbv2129c0c58aeb9945@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <79e2026f0604081606w3f9327dbv2129c0c58aeb9945@mail.gmail.com> Cc: Subject: Re: unable to SSH using Net::SSH::Perl X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 02:45:42 -0000 Adding freebsd-hackers@freebsd.org On 4/8/06, Ashok Shrestha wrote: > Hi all, > > System Info: > FreeBSD 6.0-RELEASE > p5-Net-SSH-Perl-1.30 > perl-5.8.7 > > > > I'm trying to use Net::SSH::Perl to connect to an SSH server. > > > > Here is the script: > > > #!/usr/bin/perl -w > > # test.pl > > use Net::SSH::Perl; > > my $ssh =3D Net::SSH::Perl->new("10.0.0.243", 'debug' =3D> '1'); > $ssh->login("username", "password"); > > > > Here is my error: > ./test.pl > Reading configuration data /root/.ssh/config > Reading configuration data /etc/ssh_config > Allocated local port 1023. > Connecting to 10.0.0.243, port 22. > Remote version string: SSH-2.0-OpenSSH_3.8.1p1 FreeBSD-20040419 > > Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1 > FreeBSD-20040419 > Net::SSH::Perl Version 1.30, protocol version 2.0. > No compat match: OpenSSH_3.8.1p1 FreeBSD-20040419. > Connection established. > Sent key-exchange init (KEXINIT), wait response. > Algorithms, c->s: 3des-cbc hmac-sha1 none > Algorithms, s->c: 3des-cbc hmac-sha1 none > Entering Diffie-Hellman Group 1 key exchange. > Sent DH public key, waiting for reply. > Received host key, type 'ssh-dss'. > Host '10.0.0.243' is known and matches the host key. > Computing shared secret key. > Verifying server signature. > Waiting for NEWKEYS message. > Enabling incoming encryption/MAC/compression. > Send NEWKEYS, enable outgoing encryption/MAC/compression. > Sending request for user-authentication service. > Service accepted: ssh-userauth. > Trying empty user-authentication request. > Authentication methods that can continue: publickey,keyboard-interactive= . > Next method to try is publickey. > Trying pubkey authentication with key file '/root/.ssh/id_rsa' > Authentication methods that can continue: publickey,keyboard-interactive= . > Next method to try is publickey. > Permission denied at ./test_SSH.pl line 8 > > > > > > > > Here is the relevant portion of my /root/.ssh/config > > # Host * > # ForwardAgent no > # ForwardX11 no > # RhostsRSAAuthentication no > # RSAAuthentication yes > # PasswordAuthentication yes > # HostbasedAuthentication no > # BatchMode no > # CheckHostIP no > # AddressFamily any > # ConnectTimeout 0 > # StrictHostKeyChecking ask > # IdentityFile ~/.ssh/identity > IdentityFile ~/.ssh/id_rsa > # IdentityFile ~/.ssh/id_dsa > # Port 22 > # Protocol 2,1 > # Cipher 3des > # Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-c= bc,aes256-cbc > # EscapeChar ~ > # VersionAddendum FreeBSD-20050903 > > > > > > > > Any ideas what I'm doing incorrect? > > > -- > Ashok Shrestha > -- Ashok Shrestha From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 03:00:12 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9AE016A402 for ; Sun, 9 Apr 2006 03:00:12 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 7EE8643D46 for ; Sun, 9 Apr 2006 03:00:11 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 74174 invoked by uid 1001); 9 Apr 2006 03:00:11 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Sat, 08 Apr 2006 23:00:11 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17464.30906.793504.199832@bhuda.mired.org> Date: Sat, 8 Apr 2006 23:00:10 -0400 To: Dima Dorfman In-Reply-To: <20060409005712.GA856@trit.org> References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <443811EF.2020509@samsco.org> <17464.8074.937742.701480@bhuda.mired.org> <44383346.2030207@samsco.org> <17464.16087.217524.843667@bhuda.mired.org> <20060409005712.GA856@trit.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 03:00:12 -0000 In <20060409005712.GA856@trit.org>, Dima Dorfman typed: > Mike Meyer wrote: > > What do I want for that? I identify ethernet boards by which slot on > > the back of the system I plug the cable into. Currently, I have to map > > that to board types to and which board is plugged into which slot to > > know which name to use. I want a name that tells me which slot I plug > > a cable in to plug it into that interface. > Is information about the slot even available on a PC? For something like this: The BIOS seems to get that information from somewhere. But I'm not a hardware guru, so I can't say for sure. > : em0@pci6:7:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 hdr=0x00 > : vendor = 'Intel Corporation' > : device = '82547EI Gigabit Ethernet Controller' > : class = network > : subclass = ethernet > > would you consider eth-6-7-0 to be an improvement over em0? Not really, because the magic numbers aren't tied to anything real. You want the magic numbers to corrspond to the physical objects you manipulate. For disk devices, the numbers were originally tied to bus ids, which were set on the device. ra's had swappable plugs with the drive number on them and a light behind the plug, so /dev/ra3 referred to the drive in the rack of 16 drives with the number "3" in the front panel lights. > It has the advantage of not changing if another card is added to the > system, but it's not very informative. For a system that has only nn> its two on-board NICs, "em0" and "em1" are very obvious--at least > it's clear which one corresponds to the label "eth 0" on the > chassis. I'll have to take your word for that, as I haven't got a box handy with two onboard NICs. Is there anything that says we can't have multiple names for an interface? If we do that, then we could (random brainstorming here): Have a name like eth-pci-slot-3 (it's an ethernet device on a pci bus at slot 3), eth-pci-onboard-0 (onboard ethernet port 0) or eth-usb-2 (for the usb-ethernet dongles). The class part - "eth" - is redundant, as the rest of the name identifies the device exactly, but it helps prevent errors, as you get "no such device" errors instead of trying to do something completely inappropriate to a device. This is what you'd use on systems with multiple identical devices. All network devices also get a name of the form net0, net1, .... This is for systems with just one network interface - no matter what kind it is - which can just refer to "net0" and get the one and only network interface. All network devices also get a name corresponding to the media, so you'd have eth0, eth1, or fw0, fw1 (firewire), meaning that if you specifically want an ethernet - as opposed to an arbitrary network interface - you'd use eth0 instead of net0. This allows you to use eth0, fw0 and wifi0 for the ethernet, firewire and wifi network interfaces on a modern laptop, without having to worry about which net# device map to which of those devices. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 03:18:02 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 922F516A401 for ; Sun, 9 Apr 2006 03:18:02 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id EFF6543D45 for ; Sun, 9 Apr 2006 03:18:01 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 74545 invoked by uid 1001); 9 Apr 2006 03:18:01 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Sat, 08 Apr 2006 23:18:01 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17464.31976.938131.944829@bhuda.mired.org> Date: Sat, 8 Apr 2006 23:18:00 -0400 To: Darren Pilgrim In-Reply-To: <44385525.8000203@bitfreak.org> References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <20060408224140.GA15366@outcold.yadt.co.uk> <17464.17494.251794.271711@bhuda.mired.org> <44385525.8000203@bitfreak.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 03:18:02 -0000 In <44385525.8000203@bitfreak.org>, Darren Pilgrim typed: > Mike Meyer wrote: > > In <20060408224140.GA15366@outcold.yadt.co.uk>, David Taylor typed: > >> That doesn't quite work, though. Unless you require everyone wanting > >> to distinguish between LAN and WAN interfaces uses different types > >> of hardware for each card, they'll still end up with xl0 and xl1 > >> (or whatever), which is in no way better than eth0 and eth1, > > > > You're right - but at least you have the option of using different > > types of cards to get different names. I agree that this sucks, but > > it's better than nothing. > > This is a script to rename interfaces based on the MAC address: Very nice. > If you add something to /etc/rc.d so that a sh-ified version of this script > runs after all interfaces have attached but before any numbering or cloning > takes place you can have lines like this in /etc/rc.conf: > > ifconfig_PublicLAN="inet a.b.c.d/24" > > That's far better than trying to remember what's on em0. That's certainly true. But is there an advantage to tieing the PublicLAN name to a MAC address as opposed to em0? > Comments please! This is certainly a move in the right direction. However, MAC addresses are of about the same order of obscurity as device probe order numbers. It might be more usefull to do something like: ifn_list=/etc/NETIF_list for ifn in $(ifconfig -l link) do ifn_addr=$(pciconf -l | grep "^$ifn" | sed -e 's/^[^@]*@//' -e 's/: .*//') ifn_name=$(grep $ifn_addr $ifn_list | cut -d ' ' -f 2$) ifconfig $ifn name $ifn_name done This way, the name would be tied to the slot on the backplane that the device is plugged into. If you changed the card in that slot, it'd still get the same name, even if it was a different card type. That seems like desirable behavior to me, but I can also see cases where the name should follow the card if it moves to a different slot, which is what your version does. The real problem with what I proposed is that you have to arrange to search config information for things that may not be tied to a pci bus. That could get real messy. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 04:37:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65F7316A40F; Sun, 9 Apr 2006 04:37:31 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BD3743D55; Sun, 9 Apr 2006 04:37:30 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k394bUUK087722; Sat, 8 Apr 2006 23:37:30 -0500 (CDT) (envelope-from dan) Date: Sat, 8 Apr 2006 23:37:29 -0500 From: Dan Nelson To: Ashok Shrestha Message-ID: <20060409043729.GD64658@dan.emsphone.com> References: <79e2026f0604081616h2dab7552m38b7d53744c474db@mail.gmail.com> <79e2026f0604081944m79d1621cv1668266689fd5f3f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79e2026f0604081944m79d1621cv1668266689fd5f3f@mail.gmail.com> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, freebsd-perl@freebsd.org Subject: Re: Net::FTPSSL error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 04:37:31 -0000 In the last episode (Apr 08), Ashok Shrestha said: > Adding freebsd-hackers@freebsd.org > > On 4/8/06, Ashok Shrestha wrote: > > I'm trying to use Net::FTPSSL to connect to an FTP server via SSL. > > Here is the script: > > > > #!/usr/bin/perl -w > > > > use Net::FTPSSL; > > > > my $ftps = Net::FTPSSL->new('127.0.0.1', > > 'Encryption' => 'E', > > 'Debug' => 1, > > 'Timeout' => 20) > > or die "Can't open 127.0.0.1"; > > > > $ftps->login('username123', 'password123') or die "Can't login: ", > > $ftps->$last_message(); > > > > $ftps->cwd("/working") or die "Can't change directory: ", $ftps->last_message; > > > > $ftps->get("C13.txt") or die "Can't get file: ", $ftps->last_message; > > > > $ftps->quit(); > > > > Here is my error: > > ./test_FTPSSL.pl > > Name "main::last_message" used only once: possible typo at > > ./test_FTPSSL.pl line 11. > > >>> USER username123 > > <<< 331 Please specify the password. > > >>> PASS password123 > > Use of uninitialized value in length at (eval 7) line 1. > > Use of uninitialized value in string eq at blib/lib/Net/SSLeay.pm > > (autosplit into blib/lib/auto/Net/S > > > > SLeay/ssl_read_all.al) line 1615. > > Can't read on socket: at ./test_FTPSSL.pl line 11 I don't know any perl, but why is your test script printing an error message ("Can't read on socket") that's not in the source you pasted, and does the warning "Name "main::last_message" used only once: possible typo at ./test_FTPSSL.pl line 11" have anything to do with it? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 05:50:27 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E20FC16A407 for ; Sun, 9 Apr 2006 05:50:27 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AE8643D53 for ; Sun, 9 Apr 2006 05:50:27 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 7BB1119F2C; Sat, 8 Apr 2006 22:50:26 -0700 (PDT) Message-ID: <4438A0A3.3050600@bitfreak.org> Date: Sat, 08 Apr 2006 22:50:27 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Mike Meyer References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <20060408224140.GA15366@outcold.yadt.co.uk> <17464.17494.251794.271711@bhuda.mired.org> <44385525.8000203@bitfreak.org> <17464.31976.938131.944829@bhuda.mired.org> In-Reply-To: <17464.31976.938131.944829@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 05:50:28 -0000 Mike Meyer wrote: > In <44385525.8000203@bitfreak.org>, Darren Pilgrim typed: >> >> If you add something to /etc/rc.d so that a sh-ified version of this script >> runs after all interfaces have attached but before any numbering or cloning >> takes place you can have lines like this in /etc/rc.conf: >> >> ifconfig_PublicLAN="inet a.b.c.d/24" >> >> That's far better than trying to remember what's on em0. > > That's certainly true. But is there an advantage to tieing the > PublicLAN name to a MAC address as opposed to em0? The network interface name the user sees becomes tied directly to the physical device by way of a unique, configuration-independent identifier. The probe order and driver name become transparent to the network configuration. You could test two different drivers on the same hardware and you wouldn't have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run: /etc/rc.d/netif stop PublicLAN kldunload olddriver kldload newdriver /etc/rc.d/netif start PublicLAN Within the currently available capabilities, we get the network interface equivalent of disk volume labels. [ Proposed use of PCI addresses instead of MAC addresses. ] > The real problem with what I proposed is that you have to arrange to > search config information for things that may not be tied to a pci > bus. That could get real messy. Right, it doesn't scale to ISA or USB devices. The prior probably isn't a big deal these days, but I imagine compatibility with USB devices is fairly important. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 09:02:16 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A22816A402 for ; Sun, 9 Apr 2006 09:02:16 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (ns0.infracaninophile.co.uk [81.187.76.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E18543D45 for ; Sun, 9 Apr 2006 09:02:14 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from [IPv6:::1] (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.13.6/8.13.6) with ESMTP id k39922QQ043938; Sun, 9 Apr 2006 10:02:02 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4438CD84.1020906@infracaninophile.co.uk> Date: Sun, 09 Apr 2006 10:01:56 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Thunderbird 1.5 (X11/20060401) MIME-Version: 1.0 To: Mike Meyer References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <20060408233740.GA84768@submonkey.net> <44384A55.2010103@samsco.org> <4438630E.4090300@deadcafe.de> <17464.29347.529203.354768@bhuda.mired.org> In-Reply-To: <17464.29347.529203.354768@bhuda.mired.org> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig5A8B6881266714BDB20380B9" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.infracaninophile.co.uk [IPv6:::1]); Sun, 09 Apr 2006 10:02:02 +0100 (BST) X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on happy-idiot-talk.infracaninophile.co.uk Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 09:02:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5A8B6881266714BDB20380B9 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Mike Meyer wrote: > In <4438630E.4090300@deadcafe.de>, Daniel Rock ty= ped: >> So I doubt that the overwriting of an Ingres database really >> happened in Solaris, like some other poster described - unless the >> administrator fiddled with /etc/path_to_inst by hand (you are free >> to shoot in your own foot). >=20 > That happened very early in the life of Solaris, in the early 90s. > Persistent numbering was added to Solaris in response to this incident > (there were probably others as well). >=20 > This was on a relatively large server, with something like 4 SCSI > buses. A drive was added to a previously unused bus, making it appear > "between" two drives that were already in the system. This gave all > the drives further on in the probe sequence a device number one higher > than they had previously had. It sounds for me as if you (Mike Meyer) are asking for something like 'acpidump -d' or 'pciconf -l -v' output, but translated into a filesystem= abstraction -- ie a tree of directories corresponding to different busses= containing device files ordered according to the bus slot they are plugged into. This would be something that you can use either in place of the traditional /dev or as an adjunct to it. I believe Solaris has a /devices tree which does essentially this. In practice however on the systems we deploy we know that the principal network interfaces are the ones on-board the motherboard, and we know that em0 or bge0 is the one closest to the PSU. Similarly for other devices -- disk device numbers can be deduced from the physical slot they= are in. Sure it's just a convention, and it helps that the equipment supplier we use is very consistent about such things, and that in general= we don't go around plugging USB disk devices into server systems that frequently. But on the whole it works. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enig5A8B6881266714BDB20380B9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEOM2J8Mjk52CukIwRA3eGAJ9fIvHwgwv3yIoSd8USWv77AGlFigCfYdeL xewb3JZgzBoH2GvFRrU/b4c= =L4uX -----END PGP SIGNATURE----- --------------enig5A8B6881266714BDB20380B9-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 09:08:08 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4425216A422 for ; Sun, 9 Apr 2006 09:08:08 +0000 (UTC) (envelope-from bms@spc.org) Received: from mindfull.spc.org (mindfull.spc.org [83.167.185.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F8443D46 for ; Sun, 9 Apr 2006 09:08:07 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org ([83.167.185.2]) by mindfull.spc.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FSVtp-0002iM-8Z; Sun, 09 Apr 2006 10:08:01 +0100 Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id D3A2D65499; Sun, 9 Apr 2006 10:07:58 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 61476-05; Sun, 9 Apr 2006 10:07:57 +0100 (BST) Received: by arginine.spc.org (Postfix, from userid 1078) id A10EF653F9; Sun, 9 Apr 2006 10:07:57 +0100 (BST) Date: Sun, 9 Apr 2006 10:07:57 +0100 From: Bruce M Simpson To: Mike Meyer Message-ID: <20060409090757.GW80492@spc.org> References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <443811EF.2020509@samsco.org> <17464.8074.937742.701480@bhuda.mired.org> <44383346.2030207@samsco.org> <17464.16087.217524.843667@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17464.16087.217524.843667@bhuda.mired.org> User-Agent: Mutt/1.4.1i Organization: Incunabulum X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mindfull.spc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - spc.org X-Source: X-Source-Args: X-Source-Dir: Cc: Ceri Davies , Scott Long , hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 09:08:08 -0000 Mike, Tell me about it, I know exactly what you mean! On Sat, Apr 08, 2006 at 06:53:11PM -0400, Mike Meyer wrote: > My question about labels for ethernet devices wasn't meant to be > rhetorical. Ethernet device names on Unix are pretty much > worthless. They tell you basically nothing about which device you've > got. On FreeBSD, different card types have different names, which is > better than nothing - but that's about all it's better than. We need > something akin to labels for ethernet devices. The LAN it's plugged > into is the equivalent of the data on the disk - but there's no > equivalent for the label. > > What do I want for that? I identify ethernet boards by which slot on > the back of the system I plug the cable into. Currently, I have to map > that to board types to and which board is plugged into which slot to > know which name to use. I want a name that tells me which slot I plug > a cable in to plug it into that interface. I investigated this problem when doing research on XORP. The behaviour you describe is a functional requirement for a router chassis. What it really comes down to is that one needs a PCI variant which supports what's known as 'geographical addressing', and for FreeBSD's device / ifnet framework to support naming cards according to the geographic i.e. physical address. If you look at the very bottom of the man page pci(9) you'll see I've left a footnote about this. Unfortunately the only systems which tend to implement this feature at the moment are CompactPCI based chassis systems. Although there is support for geographical addressing in a recent ACPI spec but as far as I know it may only really have made its way into blade systems. Hope this helps. Regards, BMS P.S. If etiquette were taken more seriously then society as a whole might function better -- I think of it as part of the 'operating system' of the human spirit! From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 11:55:33 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 637A416A405 for ; Sun, 9 Apr 2006 11:55:33 +0000 (UTC) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-0-0-cust107.cdif.cable.ntl.com [81.104.168.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id F21AC43D46 for ; Sun, 9 Apr 2006 11:55:31 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FSYVo-000C6M-3Y; Sun, 09 Apr 2006 12:55:24 +0100 Date: Sun, 9 Apr 2006 12:55:23 +0100 From: Ceri Davies To: Scott Long Message-ID: <20060409115523.GB84768@submonkey.net> Mail-Followup-To: Ceri Davies , Scott Long , Brooks Davis , hackers@freebsd.org References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <20060408233740.GA84768@submonkey.net> <44384A55.2010103@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5I6of5zJg18YgZEa" Content-Disposition: inline In-Reply-To: <44384A55.2010103@samsco.org> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.11 Sender: Ceri Davies Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 11:55:33 -0000 --5I6of5zJg18YgZEa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006 at 05:42:13PM -0600, Scott Long wrote: > Ceri Davies wrote: >=20 > >On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote: > > > >>>>On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote: > > > > > >>>>>For the filesystem I can use geom_label and /dev/ufs/UnlikelyString,= =20 > >>>>>but I'd > >>>>>also like to have it try to configure whatever interfaces the machine > >>>>>happens to have via DHCP. > >>>>> > >>>>>Other than specifying ifconfig_0=3D"DHCP" once for every possibl= e=20 > >>>>>value of > >>>>>, is there a mechanism to do this already? > >>>> > >>>>ifconfig_DEFAULT > >> > >>Well, the real question is why we force the details of driver names ont= o=20 > >>users. Network and storage drivers are especially guilty of this, but > >>tty devices also are annoying. > > > > > >The current situation on BSD, where I can identify which interface is > >meant by its type, is definitely preferable to the Linux situation where > >eth0 may mean something different tomorrow depending on what is plugged > >in. > > > >Since we can rename devices arbitrarily, I don't really see a problem > >with respect to anything else. > > > >Ceri >=20 > I'll say again, how does having em0, em1, em2, and em3 help me know what > is going on with each of those interfaces? Well it doesn't, but there is no way for the OS vendor to determine what you're doing. You're more than able to rename them to dmz0, world0 or whatever in order to reflect their real usage if you like. Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --5I6of5zJg18YgZEa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEOPYrocfcwTS3JF8RAto/AJ0aCspiu0sBZk5//NSBYR4QOv3Y8QCgjXTS wJrN/xPF6lKT/t0n9/d+Wx4= =Q/kI -----END PGP SIGNATURE----- --5I6of5zJg18YgZEa-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 13:30:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D98016A406 for ; Sun, 9 Apr 2006 13:30:55 +0000 (UTC) (envelope-from zazubrik@mail.ru) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8317643D45 for ; Sun, 9 Apr 2006 13:30:52 +0000 (GMT) (envelope-from zazubrik@mail.ru) Received: from [83.237.28.236] (port=54373 helo=[192.168.0.8]) by mx2.mail.ru with esmtp id 1FSa0A-000LX7-00 for freebsd-hackers@freebsd.org; Sun, 09 Apr 2006 17:30:50 +0400 Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <44370C06.900@san.rr.com> References: <1144042356.824.16.camel@shumai.marcuscom.com> <20060406234239.GB1913@dice.stsp.lan> <200604071013.38486.aren.tyr@gawab.com> <200604071619.18686.vvp@unicom.tomica.ru> <44370C06.900@san.rr.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0C0573D0-6988-4615-839C-F3971185341B@mail.ru> Content-Transfer-Encoding: 7bit From: Artem Ignatiev Date: Sun, 9 Apr 2006 17:30:49 +0400 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.749.3) Subject: Re: RFC: Adding a ``user'' mount option X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 13:30:55 -0000 On 08.04.2006, at 5:04, Jeremy Baggs wrote: > I suppose it would be nice to have something that works "out of the > box", but the solution I have been using > is group permissions on the devices and then making the mount point > in fstab relative instead of absolute. ie: > > /dev/cd0 cdrom cd9660 ro,noauto 0 0 > > Each user has a cdrom directory under their home directory. You > still need mount points designated for all > possible devices though. Does anyone know how Darwin / OsX are > handling their auto-mount magic? > There is a /Volumes folder, and each time user inserts usb flash or cd, the directory is created in that folder, named after a volume label, and mounts the media into newly created directory. Looks like the ``diskarbitrationd'' process is responsible for this. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 15:58:37 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8092B16A401; Sun, 9 Apr 2006 15:58:37 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03C7D43D45; Sun, 9 Apr 2006 15:58:36 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k39FwHVx023360; Sun, 9 Apr 2006 09:58:18 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Apr 2006 09:58:19 -0600 (MDT) Message-Id: <20060409.095819.67883917.imp@bsdimp.com> To: mwm-keyword-freebsdhackers.102a7e@mired.org From: "M. Warner Losh" In-Reply-To: <17464.30906.793504.199832@bhuda.mired.org> References: <17464.16087.217524.843667@bhuda.mired.org> <20060409005712.GA856@trit.org> <17464.30906.793504.199832@bhuda.mired.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, dd@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 15:58:37 -0000 eth0 works well for the degenerate case where there's a network card in the system, and nothing else. It works less well for systmes where there are more than one card, and where the hardware changes a lot for all the reasons discussed in this thread. It is too generic. Of course, when you have N copies of the same card on FreeBSD, it is as degenerate as ethN is. You can use devd right now to tie the device instance to a configuration using bus topology. That information is available to the devd script that's forked. However, experiments in doing that work only so long as chaning one card doesn't change the hardware topology of the other cards. For single-banger NICs, it won't. However, when you have multi-port NIC cards that are a bunch of individual chips behind a PCI bridge, the PCI bus numbers that they live on change as you insert/remove these multi-port NIC cards, so hardware topology fails you. Then you might think of tying the MAC address to an IP address/configuration. This works well in the above scenario since you can now remove cards that change topology. However, when you replace a defective card with another, you need to reconfigure because the MAC address changes. I've actually run into all of these problems on a machine we have at work that acts as a gateway to about 10-20 private networks. It has had between 2-4 dual cards and 2-4 quad cards, in various mix and match flavors over the years. We've replaced dual fxp cards with quad de cards that were replaced with quad dc cards, etc. Pairs of dual cards were replaced with a quad card at times. We've run a single fxp card in place of a failed quad fxp card for a few days too. The mobo has been replaced a few times as well, which also changes bus topology, as well as introduces new built-in NIC cards. The only solution that works for us has been to carefully desk check the results of each hardware change after the system has been rebooted. After the desk check, a ping of systems ensures that nothing has fallen through the cracks (usually). If there's a way that we can manage this chaotic system better, I'd love to hear about it. Warner P.S. There's conflicting netequite about what I should do with a long thread. some folks say quote the whole thing, others say quote tiny bits. I've decided to offend both camps by quoting nothing :-). From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 17:10:28 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC4C816A401; Sun, 9 Apr 2006 17:10:28 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 184E743D46; Sun, 9 Apr 2006 17:10:28 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.178.169] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1FSdQg3uhE-0002I7; Sun, 09 Apr 2006 19:10:27 +0200 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Sun, 9 Apr 2006 19:08:56 +0200 User-Agent: KMail/1.9.1 References: <20060330003628.GA81305@ender.liquidneon.com> In-Reply-To: <20060330003628.GA81305@ender.liquidneon.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1286877.yOxhjxUgie"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604091909.02664.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Call for FreeBSD Status Reports X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 17:10:28 -0000 --nextPart1286877.yOxhjxUgie Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 30 March 2006 02:36, Brad Davis wrote: > Hi All, > > It is time for the quarterly Status Reports. As always, reports are > encouraged for anything that relates to FreeBSD development, > documentation, independent projects, or anything else that might be > interesting to the community as a whole. Reports should be one to two > paragraphs in length. > > The template for submissions is here: > http://www.freebsd.org/news/status/report-sample.xml > > Submissions should be submitted to monthly at FreeBSD.org by April 7th. Unfortunately we have a not too convincing turnout so far. There are - as= =20 always - very interesting reports we'd like to publish as soon as possible,= =20 but as we have less than half of the reports we had last round we are=20 extending the deadline to Wednesday, April 12th. Please remember that even small progress to you might be worth reporting. = =20 Even if you didn't make progress at all it might help to expose your projec= t=20 in the status reports to get feedback to make progress as a consequence of= =20 that. Looking forward to your submissions. Thanks a lot. http://www.freebsd.org/cgi/monthly.cgi http://www.freebsd.org/news/status/report-sample.xml =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1286877.yOxhjxUgie Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEOT+uXyyEoT62BG0RAiGOAJ9/KcoXsRxKN6jZxSlHik8mR29RwQCfYALP v/9Eneuo6cnQUgx+hQBwNHM= =GWiL -----END PGP SIGNATURE----- --nextPart1286877.yOxhjxUgie-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 18:16:03 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CCE316A401 for ; Sun, 9 Apr 2006 18:16:03 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 4D78343D49 for ; Sun, 9 Apr 2006 18:16:02 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 97513 invoked by uid 1001); 9 Apr 2006 18:16:01 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Sun, 09 Apr 2006 14:16:01 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17465.20321.174794.576853@bhuda.mired.org> Date: Sun, 9 Apr 2006 14:16:01 -0400 To: Darren Pilgrim In-Reply-To: <4438A0A3.3050600@bitfreak.org> References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <20060408224140.GA15366@outcold.yadt.co.uk> <17464.17494.251794.271711@bhuda.mired.org> <44385525.8000203@bitfreak.org> <17464.31976.938131.944829@bhuda.mired.org> <4438A0A3.3050600@bitfreak.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 18:16:03 -0000 In <4438A0A3.3050600@bitfreak.org>, Darren Pilgrim typed: > Mike Meyer wrote: > > In <44385525.8000203@bitfreak.org>, Darren Pilgrim typed: [Tying names to MAC addresses.] > >> That's far better than trying to remember what's on em0. > > > > That's certainly true. But is there an advantage to tieing the > > PublicLAN name to a MAC address as opposed to em0? > You could test two different drivers on the same hardware and you wouldn't > have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run: Yup, and this is an advantage. On the other hand, if you tie the device name to the slot number (the real goal), you can swap different hardware into that slot without having to modify any configuration information at all. If you tie the name to the MAC address, you always have to change that part of the config. If you tie the name to the current name, then you only have to change it if you change drivers. > Within the currently available capabilities, we get the network interface > equivalent of disk volume labels. Not quite. With volume labels, I can arrange to keep a replicated drive with the same volume label, and can plug it in if the old drive fails without changing a single line of system configuration. Using the MAC address as the key requires that you reconfigure the name mapping (unless you have cards that let you change the MAC address, though I have no idea if those exist for any platform that FreeBSD runs on). > [ Proposed use of PCI addresses instead of MAC addresses. ] > > The real problem with what I proposed is that you have to arrange to > > search config information for things that may not be tied to a pci > > bus. That could get real messy. > Right, it doesn't scale to ISA or USB devices. The prior probably isn't a > big deal these days, but I imagine compatibility with USB devices is fairly > important. >From what Warner Losh posted (thanks for some hard data, Warner), the PCI address isn't fixed, though you're less likely to run into it moving. And Bruce Simpson (thanks Bruce) tells us that the solution I want - names based on slot addresses - is only available on some hardware, at least for now. There's no reason we can't extend your basic solution to handle configuration by either driver/number or MAC address, allowing the user to pick the properties they want for their names. Of course, this doesn't help the OP's problem of wanting to be able to address the sole interface in a system without knowing it's name in advance. Maybe a feature to provide a default name for an interface if one isn't found in the config file would do that. BTW, I'd like to point out that sound cards have the same problem, only they all get the same "driver" name. Worse yet, the numbering can change between reboots (at least, it could on 4.x). http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 18:50:39 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DFEF16A428 for ; Sun, 9 Apr 2006 18:50:39 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id D465243D45 for ; Sun, 9 Apr 2006 18:50:38 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail14.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k39IoRnX004061 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 Apr 2006 04:50:28 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k39IoRCQ049556; Mon, 10 Apr 2006 04:50:27 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k39IoQTa049555; Mon, 10 Apr 2006 04:50:26 +1000 (EST) (envelope-from peter) Date: Mon, 10 Apr 2006 04:50:26 +1000 From: Peter Jeremy To: "M. Warner Losh" Message-ID: <20060409185026.GD720@turion.vk2pj.dyndns.org> References: <17464.16087.217524.843667@bhuda.mired.org> <20060409005712.GA856@trit.org> <17464.30906.793504.199832@bhuda.mired.org> <20060409.095819.67883917.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060409.095819.67883917.imp@bsdimp.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 18:50:39 -0000 On Sun, 2006-Apr-09 09:58:19 -0600, M. Warner Losh wrote: >I've actually run into all of these problems on a machine we have at >work that acts as a gateway to about 10-20 private networks. It has >had between 2-4 dual cards and 2-4 quad cards, in various mix and >match flavors over the years. We have several machines (for redundancy) that act as gateways into over 40 private networks. When there were only 4 networks, we used multiple NICs but decided this approach wasn't expandable and we now use VLAN trunks and break out the different networks within the switches. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 19:43:15 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB26B16A403 for ; Sun, 9 Apr 2006 19:43:15 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EE8243D46 for ; Sun, 9 Apr 2006 19:43:15 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms070.mailsrvcs.net ([192.168.1.3]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IXH003W60425PG0@vms040.mailsrvcs.net> for hackers@freebsd.org; Sun, 09 Apr 2006 14:43:14 -0500 (CDT) Date: Sun, 09 Apr 2006 14:43:14 -0500 (CDT) From: Sergey Babkin To: Mike Meyer , Scott Long Message-id: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Sun, 09 Apr 2006 20:19:20 +0000 Cc: Ceri Davies , hackers@freebsd.org Subject: Re: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 19:43:15 -0000 >From: Mike Meyer >In <443811EF.2020509@samsco.org>, Scott Long typed: >> Youre' saying that >> instead of /dev/da0, we should have >> /dev/HITACHI-HUS103073FL3800-SA19-B0T1L0 > >That's a ridiculous extreme. All I advocated was that we be able to >easily identify the devices connected to the system, *not* that we be >able identify every device in the world. Sun solved disk device naming >back in the 80s. I think this is a problem consisting of multiple parts: 1. Identify physical devices and be able to access them. 2. Identify some stable "logical" names by device type, that stay fixed when the configuration changes. 3. Be able to find the mapping easily between these two. 4. Be able to change that mapping. USB is probably the subsystem that has a particular need in this kind of stuff. So, since we have devfs nowadays, why don't we just have multiple names (dev files) for the same device? For example, the same device can be named by driver aha0b0t0d0 and by logical type disk0. The 3rd part can be solved by using symlinks in devfs: i.e. disk0 would be a symlink to aha0b0t0d0, and you can do "ls" and find out what is linked to what. The 4th part can be solved by allowing the sysadmin to create symlinks in devfs. The network driver subsystem would obviously have to be changed to consult devfs for the device names. The next interesting question is how to keep these links persistent between boots. -SB From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 20:23:16 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A410416A401 for ; Sun, 9 Apr 2006 20:23:16 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D4F643D53 for ; Sun, 9 Apr 2006 20:23:16 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 4C22319F2C; Sun, 9 Apr 2006 13:23:15 -0700 (PDT) Message-ID: <44396D33.8070900@bitfreak.org> Date: Sun, 09 Apr 2006 13:23:15 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Mike Meyer References: <20060407225742.GA21619@odin.ac.hmc.edu> <20060407230247.GH16344@submonkey.net> <4437C9F6.5000008@samsco.org> <17463.65076.117616.563302@bhuda.mired.org> <20060408224140.GA15366@outcold.yadt.co.uk> <17464.17494.251794.271711@bhuda.mired.org> <44385525.8000203@bitfreak.org> <17464.31976.938131.944829@bhuda.mired.org> <4438A0A3.3050600@bitfreak.org> <17465.20321.174794.576853@bhuda.mired.org> In-Reply-To: <17465.20321.174794.576853@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 20:23:16 -0000 Mike Meyer wrote: > In <4438A0A3.3050600@bitfreak.org>, Darren Pilgrim typed: >> You could test two different drivers on the same hardware and you wouldn't >> have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run: > > Yup, and this is an advantage. On the other hand, if you tie the > device name to the slot number (the real goal), you can swap different > hardware into that slot without having to modify any configuration > information at all. It wouldn't be too difficult to extend the configuration to allow entries like this: Interface0_addr="MAC 01:23:45:67:89:ab" Interface1_addr="PCI 0:1:2" # pci0, device 1, function 2 Interface2_addr="USB 0:1:2" # usb0, addr 1, port 2 Add some bits to grok dmesg or pciconf/usbdevs or maybe even trigger from devd and there you go. I should mention that the second and third options could be broken by the addition or removal of a card with a PCI bridge or USB root hub on it. > Of course, this doesn't help the OP's problem of wanting to be able to > address the sole interface in a system without knowing it's name in > advance. Maybe a feature to provide a default name for an interface if > one isn't found in the config file would do that. # ifconfig `ifconfig -l link` name GenericName From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 19:54:21 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE7A416A408 for ; Sun, 9 Apr 2006 19:54:21 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ED8B43D46 for ; Sun, 9 Apr 2006 19:54:21 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms070.mailsrvcs.net ([192.168.1.3]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IXH008WJ0MLNVS7@vms044.mailsrvcs.net> for hackers@freebsd.org; Sun, 09 Apr 2006 14:54:21 -0500 (CDT) Date: Sun, 09 Apr 2006 14:54:20 -0500 (CDT) From: Sergey Babkin To: Mike Meyer , Darren Pilgrim Message-id: <2692976.1658881144612461043.JavaMail.root@vms070.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Sun, 09 Apr 2006 20:24:34 +0000 Cc: hackers@freebsd.org Subject: Re: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 19:54:21 -0000 >From: Mike Meyer >In <4438A0A3.3050600@bitfreak.org>, Darren Pilgrim typed: >> >> That's far better than trying to remember what's on em0. >> > >> > That's certainly true. But is there an advantage to tieing the >> > PublicLAN name to a MAC address as opposed to em0? >> You could test two different drivers on the same hardware and you wouldn't >> have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run: > >Yup, and this is an advantage. On the other hand, if you tie the >device name to the slot number (the real goal), you can swap different >hardware into that slot without having to modify any configuration >information at all. If you tie the name to the MAC address, you always Nope, there is more than one goal. Sometimes you want to tie the device name to the slot, so that you can change the cards seamlessly. Sometimes you want to tie the device name to the card, so that you can move the card around between the slots (this is especially true for USB where you can change the topology very easily). I think the better solution is to let the administrator decide which particular way of tying the names he wants to use for a particular card. (And maybe make some reasonable guess by default, maybe depending on the device type). -SB From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 21:45:47 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F35A16A402 for ; Sun, 9 Apr 2006 21:45:47 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id C394443D46 for ; Sun, 9 Apr 2006 21:45:46 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 2291 invoked by uid 1001); 9 Apr 2006 21:45:46 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Sun, 09 Apr 2006 17:45:46 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17465.32905.727289.260996@bhuda.mired.org> Date: Sun, 9 Apr 2006 17:45:45 -0400 To: babkin@users.sourceforge.net In-Reply-To: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: Ceri Davies , Scott Long , hackers@freebsd.org Subject: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 21:45:47 -0000 In <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net>, Sergey Babkin typed: > I think this is a problem consisting of multiple parts: > > 1. Identify physical devices and be able to access them. > > 2. Identify some stable "logical" names by device type, > that stay fixed when the configuration changes. > > 3. Be able to find the mapping easily between these two. > > 4. Be able to change that mapping. I think you're looking at only two of the three aspects of the naming problem. This covers dealing with systems administration, but not using the system. Solving that for a particular device type might make the "logical" name unneeded. Then again, it might not. > So, since we have devfs nowadays, why don't we just > have multiple names (dev files) for the same device? > For example, the same device can be named by driver > aha0b0t0d0 and by logical type disk0. The 3rd part > can be solved by using symlinks in devfs: i.e. > disk0 would be a symlink to aha0b0t0d0, and you can do > "ls" and find out what is linked to what. The 4th part > can be solved by allowing the sysadmin to create symlinks > in devfs. The network driver subsystem would obviously have > to be changed to consult devfs for the device names. This is essentially the solution that Sun adapted for Solaris. Note that the mapping from "logical" names to "physical" names needs to be fixed, so that you might have a system with disk1 and disk2, but no disk0 because it's been removed. The major problem with it is that todays bus architectures don't have stable device addresses. Instead of devices having a fixed address on the bus that the user sets, the addresses are assigned as the devices are discovered. This is pretty much a requirement if you want to sell hardware to 12:00 flashers. While that's not the market that FreeBSD deals with, it is the hardware that FreeBSD runs on. The other problem is that not all devices that need names have entries in /dev. While that's fixable, different solutions will be optimal for different kinds of devices anyway, so we may not want to fix it. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 9 22:15:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F32016A403; Sun, 9 Apr 2006 22:15:35 +0000 (UTC) (envelope-from duane@greenmeadow.ca) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id E728143D5E; Sun, 9 Apr 2006 22:15:28 +0000 (GMT) (envelope-from duane@greenmeadow.ca) Received: from ip02.eastlink.ca ([24.222.10.10]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IXH00M1P75YCAD0@mta01.eastlink.ca>; Sun, 09 Apr 2006 19:15:34 -0300 (ADT) Received: from blk-224-199-230.eastlink.ca (HELO [192.168.0.103]) ([24.224.199.230]) by ip02.eastlink.ca with ESMTP; Sun, 09 Apr 2006 19:15:27 -0300 Date: Sun, 09 Apr 2006 19:14:25 -0300 From: Duane Whitty To: freebsd-questions@freebsd.org Message-id: <44398741.9080704@greenmeadow.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= User-Agent: Thunderbird 1.5 (X11/20060309) Cc: freebsd-hackers@freebsd.org Subject: UFS extended attributes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 22:15:35 -0000 Hi, Started doing a little reading on the UFS and UFS2 file systems. I'm just wondering if all types of files have extended attribute blocks available including named pipes, sockets, and device files? Is it still the case that there are three unused extended attribute blocks available? Sincerely, Duane Whitty -- duane@greenmeadow.ca From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 00:49:42 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B6C616A407 for ; Mon, 10 Apr 2006 00:49:42 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91EE643D64 for ; Mon, 10 Apr 2006 00:49:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3A0mMqm027189; Sun, 9 Apr 2006 18:48:22 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Apr 2006 18:48:25 -0600 (MDT) Message-Id: <20060409.184825.99254285.imp@bsdimp.com> To: bms@spc.org From: "M. Warner Losh" In-Reply-To: <20060409090757.GW80492@spc.org> References: <44383346.2030207@samsco.org> <17464.16087.217524.843667@bhuda.mired.org> <20060409090757.GW80492@spc.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 00:49:42 -0000 In message: <20060409090757.GW80492@spc.org> Bruce M Simpson writes: : What it really comes down to is that one needs a PCI variant which supports : what's known as 'geographical addressing', and for FreeBSD's device / ifnet : framework to support naming cards according to the geographic i.e. physical : address. I though thtis was already supported. We export bus/slot/function information devd, which can be used to configure the device. : Unfortunately the only systems which tend to implement this feature at : the moment are CompactPCI based chassis systems. Although there is support : for geographical addressing in a recent ACPI spec but as far as I know : it may only really have made its way into blade systems. How is this different than bus/slot/function? Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 00:52:44 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6B0016A400 for ; Mon, 10 Apr 2006 00:52:44 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 978D543D6A for ; Mon, 10 Apr 2006 00:52:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3A0oF1t027208; Sun, 9 Apr 2006 18:50:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Apr 2006 18:50:18 -0600 (MDT) Message-Id: <20060409.185018.61267301.imp@bsdimp.com> To: mwm-keyword-freebsdhackers.102a7e@mired.org From: "M. Warner Losh" In-Reply-To: <17465.20321.174794.576853@bhuda.mired.org> References: <17464.31976.938131.944829@bhuda.mired.org> <4438A0A3.3050600@bitfreak.org> <17465.20321.174794.576853@bhuda.mired.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: darren.pilgrim@bitfreak.org, hackers@freebsd.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 00:52:45 -0000 In message: <17465.20321.174794.576853@bhuda.mired.org> Mike Meyer writes: : Of course, this doesn't help the OP's problem of wanting to be able to : address the sole interface in a system without knowing it's name in : advance. Maybe a feature to provide a default name for an interface if : one isn't found in the config file would do that. ifconfig_DEFAULT already handles that. If you have only one interface, it will use the default, no matter which interface you install. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 00:52:47 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8355C16A400 for ; Mon, 10 Apr 2006 00:52:47 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AFE943D46 for ; Mon, 10 Apr 2006 00:52:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3A0pilx027211; Sun, 9 Apr 2006 18:51:44 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Apr 2006 18:51:47 -0600 (MDT) Message-Id: <20060409.185147.25157954.imp@bsdimp.com> To: darren.pilgrim@bitfreak.org From: "M. Warner Losh" In-Reply-To: <44396D33.8070900@bitfreak.org> References: <4438A0A3.3050600@bitfreak.org> <17465.20321.174794.576853@bhuda.mired.org> <44396D33.8070900@bitfreak.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, mwm@mired.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 00:52:47 -0000 In message: <44396D33.8070900@bitfreak.org> Darren Pilgrim writes: : Mike Meyer wrote: : > In <4438A0A3.3050600@bitfreak.org>, Darren Pilgrim typed: : >> You could test two different drivers on the same hardware and you wouldn't : >> have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run: : > : > Yup, and this is an advantage. On the other hand, if you tie the : > device name to the slot number (the real goal), you can swap different : > hardware into that slot without having to modify any configuration : > information at all. : : It wouldn't be too difficult to extend the configuration to allow entries : like this: : : Interface0_addr="MAC 01:23:45:67:89:ab" : Interface1_addr="PCI 0:1:2" # pci0, device 1, function 2 : Interface2_addr="USB 0:1:2" # usb0, addr 1, port 2 : : Add some bits to grok dmesg or pciconf/usbdevs or maybe even trigger from : devd and there you go. : : I should mention that the second and third options could be broken by the : addition or removal of a card with a PCI bridge or USB root hub on it. The device subsystem already exports a bus-dependent plug and play position. No need to make it specific to USB/PCI/whatever. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 00:55:35 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A12216A405 for ; Mon, 10 Apr 2006 00:55:35 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEA3C43D49 for ; Mon, 10 Apr 2006 00:55:34 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3A0rWSK027226; Sun, 9 Apr 2006 18:53:32 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Apr 2006 18:53:35 -0600 (MDT) Message-Id: <20060409.185335.105395062.imp@bsdimp.com> To: mwm-keyword-freebsdhackers.102a7e@mired.org From: "M. Warner Losh" In-Reply-To: <17465.32905.727289.260996@bhuda.mired.org> References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, babkin@users.sourceforge.net, ceri@submonkey.net, scottl@samsco.org Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 00:55:35 -0000 In message: <17465.32905.727289.260996@bhuda.mired.org> Mike Meyer writes: : The major problem with it is that todays bus architectures don't have : stable device addresses. Instead of devices having a fixed address on : the bus that the user sets, the addresses are assigned as the devices : are discovered. This is pretty much a requirement if you want to sell : hardware to 12:00 flashers. While that's not the market that FreeBSD : deals with, it is the hardware that FreeBSD runs on. usb assigns addresses dynamically. Everyone else does it basically statically. PCI slot/device numbers are static, but extreme configurations can change the bus number. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 01:04:10 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76B6D16A400 for ; Mon, 10 Apr 2006 01:04:10 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3299743D45 for ; Mon, 10 Apr 2006 01:04:10 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 2CF3B19F40; Sun, 9 Apr 2006 18:04:09 -0700 (PDT) Message-ID: <4439AF09.6030209@bitfreak.org> Date: Sun, 09 Apr 2006 18:04:09 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "M. Warner Losh" References: <4438A0A3.3050600@bitfreak.org> <17465.20321.174794.576853@bhuda.mired.org> <44396D33.8070900@bitfreak.org> <20060409.185147.25157954.imp@bsdimp.com> In-Reply-To: <20060409.185147.25157954.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, mwm@mired.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 01:04:10 -0000 M. Warner Losh wrote: > > The device subsystem already exports a bus-dependent plug and play > position. No need to make it specific to USB/PCI/whatever. Where is this information found? I can't find anything obvious that wouldn't change if you inserted a bus in the middle of the probe order. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 02:46:31 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51EDA16A402 for ; Mon, 10 Apr 2006 02:46:31 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7F0F43D46 for ; Mon, 10 Apr 2006 02:46:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3A2j7FZ028008; Sun, 9 Apr 2006 20:45:07 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Apr 2006 20:45:10 -0600 (MDT) Message-Id: <20060409.204510.83724262.imp@bsdimp.com> To: darren.pilgrim@bitfreak.org From: "M. Warner Losh" In-Reply-To: <4439AF09.6030209@bitfreak.org> References: <44396D33.8070900@bitfreak.org> <20060409.185147.25157954.imp@bsdimp.com> <4439AF09.6030209@bitfreak.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, mwm@mired.org Subject: Re: Using any network interface whatsoever (solution?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 02:46:31 -0000 In message: <4439AF09.6030209@bitfreak.org> Darren Pilgrim writes: : M. Warner Losh wrote: : > : > The device subsystem already exports a bus-dependent plug and play : > position. No need to make it specific to USB/PCI/whatever. : : Where is this information found? I can't find anything obvious that : wouldn't change if you inserted a bus in the middle of the probe order. I was replying to the position stuff that was proposed as a way to find something. I was saying that you don't need to invent special locators, since all busses are required to provide them. For example: % devinfo -v | grep fxp0 fxp0 pnpinfo vendor=0x8086 device=0x103d subvendor=0x104d subdevice=0x8140 class=0x020000 at slot=8 function=0 handle=\_SB_.PCI0.PCIB.LANC You'd write the devd rule like: attach 10 { match "slot" "8"; match "function" "0"; action "configure-network $device-name"; }; This is technically independent of the bus, since the bus isn't exported (it should be). I'm told that some machines have multiple pci domains, so bus number isn't unique. devinfo(8) should provide a way to get this information as well, but it currently makes that kinda hard (you could parse out the parent device name). Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 02:47:56 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B87116A400 for ; Mon, 10 Apr 2006 02:47:56 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 4BBE243D45 for ; Mon, 10 Apr 2006 02:47:54 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 10737 invoked by uid 1001); 10 Apr 2006 02:47:54 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Sun, 09 Apr 2006 22:47:53 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17465.51033.78362.699332@bhuda.mired.org> Date: Sun, 9 Apr 2006 22:47:53 -0400 To: "M. Warner Losh" In-Reply-To: <20060409.185335.105395062.imp@bsdimp.com> References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org, babkin@users.sourceforge.net, ceri@submonkey.net, scottl@samsco.org Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 02:47:56 -0000 In <20060409.185335.105395062.imp@bsdimp.com>, M. Warner Losh typed: > In message: <17465.32905.727289.260996@bhuda.mired.org> > Mike Meyer writes: > : The major problem with it is that todays bus architectures don't have > : stable device addresses. Instead of devices having a fixed address on > : the bus that the user sets, the addresses are assigned as the devices > : are discovered. This is pretty much a requirement if you want to sell > : hardware to 12:00 flashers. While that's not the market that FreeBSD > : deals with, it is the hardware that FreeBSD runs on. > usb assigns addresses dynamically. Everyone else does it basically > statically. PCI slot/device numbers are static, but extreme > configurations can change the bus number. USB is popular enough and PCI changes enough that we have to be able to deal with them. Firewire would seem to be a lot like USB - hot pluggable and chainable, though I'm not sure if something like a firewire hub. What does it to do wire down device addresses? Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 06:45:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64CEE16A485; Mon, 10 Apr 2006 06:45:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0902743D46; Mon, 10 Apr 2006 06:45:10 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5184E46C6F; Mon, 10 Apr 2006 02:45:09 -0400 (EDT) Date: Mon, 10 Apr 2006 07:45:09 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Duane Whitty In-Reply-To: <44398741.9080704@greenmeadow.ca> Message-ID: <20060410074341.Y32454@fledge.watson.org> References: <44398741.9080704@greenmeadow.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: UFS extended attributes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 06:45:10 -0000 On Sun, 9 Apr 2006, Duane Whitty wrote: > Started doing a little reading on the UFS and UFS2 file systems. I'm just > wondering if all types of files have extended attribute blocks available > including named pipes, sockets, and device files? > > Is it still the case that there are three unused extended attribute blocks > available? Extended attribute storage is available for all objects in UFS, including files, directories, named pipes, UNIX domain sockets, and device nodes. I'm probably not th eright person to answer questions about the layout itself. Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 07:47:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9977416A400; Mon, 10 Apr 2006 07:47:57 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FEFA43D46; Mon, 10 Apr 2006 07:47:56 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (wlan032039.uni-rostock.de [139.30.32.39]) by hydra.bec.de (Postfix) with ESMTP id 0244035707; Mon, 10 Apr 2006 09:47:53 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 964206CBB8; Mon, 10 Apr 2006 09:47:40 +0200 (CEST) Date: Mon, 10 Apr 2006 09:47:40 +0200 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060410074740.GD1006@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17465.51033.78362.699332@bhuda.mired.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 07:47:57 -0000 On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: > Firewire would seem to be a lot like USB - hot pluggable and > chainable, though I'm not sure if something like a firewire hub. What > does it to do wire down device addresses? FireWire devices have uuids, you can simply enumerate them using those :-) Joerg From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 07:47:57 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9977416A400; Mon, 10 Apr 2006 07:47:57 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FEFA43D46; Mon, 10 Apr 2006 07:47:56 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (wlan032039.uni-rostock.de [139.30.32.39]) by hydra.bec.de (Postfix) with ESMTP id 0244035707; Mon, 10 Apr 2006 09:47:53 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 964206CBB8; Mon, 10 Apr 2006 09:47:40 +0200 (CEST) Date: Mon, 10 Apr 2006 09:47:40 +0200 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060410074740.GD1006@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17465.51033.78362.699332@bhuda.mired.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 07:47:57 -0000 On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: > Firewire would seem to be a lot like USB - hot pluggable and > chainable, though I'm not sure if something like a firewire hub. What > does it to do wire down device addresses? FireWire devices have uuids, you can simply enumerate them using those :-) Joerg From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 08:59:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F18816A400; Mon, 10 Apr 2006 08:59:18 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05B4943D46; Mon, 10 Apr 2006 08:59:18 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1FSsEt-0002d9-1J; Mon, 10 Apr 2006 09:59:17 +0100 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:57180) by mail.ilrt.bris.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1FSsEo-0001CZ-3c; Mon, 10 Apr 2006 09:59:14 +0100 Date: Mon, 10 Apr 2006 09:59:07 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: Robert Watson In-Reply-To: <20060410074341.Y32454@fledge.watson.org> Message-ID: <20060410095828.M15367@tribble.ilrt.bris.ac.uk> References: <44398741.9080704@greenmeadow.ca> <20060410074341.Y32454@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spamassassin: mail.ilrt.bris.ac.uk X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Score: -1.4 X-Spam-Level: - Cc: freebsd-hackers@freebsd.org, Duane Whitty , freebsd-questions@freebsd.org Subject: Re: UFS extended attributes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 08:59:18 -0000 On Mon, 10 Apr 2006, Robert Watson wrote: > > On Sun, 9 Apr 2006, Duane Whitty wrote: > > > Started doing a little reading on the UFS and UFS2 file systems. I'm just > > wondering if all types of files have extended attribute blocks available > > including named pipes, sockets, and device files? > > > > Is it still the case that there are three unused extended attribute blocks > > available? > > Extended attribute storage is available for all objects in UFS, including > files, directories, named pipes, UNIX domain sockets, and device nodes. I'm > probably not th eright person to answer questions about the layout itself. Looks like it is: see /usr/include/ufs/ufs/dinode.h -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Theoremhood is positively decidable. It just takes time at least exponential in the length of the proof. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 08:57:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 037D616A403 for ; Mon, 10 Apr 2006 08:57:44 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-out-01.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 301C243D8A for ; Mon, 10 Apr 2006 08:57:30 +0000 (GMT) (envelope-from dds@aueb.gr) Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.13.6/8.13.6) with ESMTP id k3A8vSj7025265 for ; Mon, 10 Apr 2006 11:57:28 +0300 Received: from mx-in-03.forthnet.gr (mx-in-03.forthnet.gr [193.92.150.26]) by mx-av-03.forthnet.gr (8.13.6/8.13.6) with ESMTP id k3A8vR3w004708 for ; Mon, 10 Apr 2006 11:57:27 +0300 Received: from [192.168.136.16] (ppp73-adsl-193.ath.forthnet.gr [195.74.243.193]) by mx-in-03.forthnet.gr (8.13.6/8.13.6) with ESMTP id k3A8vQM0017008 for ; Mon, 10 Apr 2006 11:57:27 +0300 Authentication-Results: mx-in-03.forthnet.gr from=dds@aueb.gr; sender-id=neutral; spf=neutral Message-ID: <443A13BF.1090807@aueb.gr> Date: Mon, 10 Apr 2006 11:13:51 +0300 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 10 Apr 2006 11:30:41 +0000 Subject: Code Quality and FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 08:57:44 -0000 A quick note to inform my fellow FreeBSD users and developers that my new book "Code Quality: The Open Source Perspective" (Addison-Wesley, 2006) is now available. Almost all the 623 examples I use in the book are drawn from actual code. NetBSD is the primary package I used for source code excerpts, but aggregate measures and observations of code evolution trends come from FreeBSD (at home FreeBSD systems outnumber NetBSD ones by a factor of 4 :-). For more details you can visit the book's web site at . Diomidis - dds@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 13:47:43 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A7C516A405 for ; Mon, 10 Apr 2006 13:47:43 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C41143D55 for ; Mon, 10 Apr 2006 13:47:42 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 29308 invoked by uid 1001); 10 Apr 2006 13:47:42 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Mon, 10 Apr 2006 09:47:41 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17466.25085.446099.450392@bhuda.mired.org> Date: Mon, 10 Apr 2006 09:47:41 -0400 To: joerg@britannica.bec.de In-Reply-To: <20060410074740.GD1006@britannica.bec.de> References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> <20060410074740.GD1006@britannica.bec.de> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 13:47:43 -0000 In <20060410074740.GD1006@britannica.bec.de>, joerg@britannica.bec.de typed: > On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: > > Firewire would seem to be a lot like USB - hot pluggable and > > chainable, though I'm not sure if something like a firewire hub. What > > does it to do wire down device addresses? > FireWire devices have uuids, you can simply enumerate them using those > :-) Where do those come from? Assigned by the user? Dynamically by the controller? By the manufacturer? Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 13:47:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52FCE16A406 for ; Mon, 10 Apr 2006 13:47:43 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C26943D49 for ; Mon, 10 Apr 2006 13:47:42 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 29305 invoked by uid 1001); 10 Apr 2006 13:47:41 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Mon, 10 Apr 2006 09:47:41 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17466.25085.446099.450392@bhuda.mired.org> Date: Mon, 10 Apr 2006 09:47:41 -0400 To: joerg@britannica.bec.de In-Reply-To: <20060410074740.GD1006@britannica.bec.de> References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> <20060410074740.GD1006@britannica.bec.de> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 13:47:43 -0000 In <20060410074740.GD1006@britannica.bec.de>, joerg@britannica.bec.de typed: > On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: > > Firewire would seem to be a lot like USB - hot pluggable and > > chainable, though I'm not sure if something like a firewire hub. What > > does it to do wire down device addresses? > FireWire devices have uuids, you can simply enumerate them using those > :-) Where do those come from? Assigned by the user? Dynamically by the controller? By the manufacturer? Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 13:54:56 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71D5016A401 for ; Mon, 10 Apr 2006 13:54:56 +0000 (UTC) (envelope-from nickolas@atlas.ua) Received: from colt.tsua.net (colt.tsua.net [212.40.34.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8953143D46 for ; Mon, 10 Apr 2006 13:54:54 +0000 (GMT) (envelope-from nickolas@atlas.ua) Received: from localhost (localhost [127.0.0.1]) by colt.tsua.net (Postfix) with ESMTP id 243801050E3 for ; Mon, 10 Apr 2006 16:54:54 +0300 (EEST) Received: from colt.tsua.net ([127.0.0.1]) by localhost (colt.tsua.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05690-07 for ; Mon, 10 Apr 2006 16:54:53 +0300 (EEST) Received: by colt.tsua.net (Postfix, from userid 426) id C0D461050BE; Mon, 10 Apr 2006 16:54:53 +0300 (EEST) Received: from mail.atlas.kiev.ua (atlas-ss-1.tsua.net [212.40.33.65]) by colt.tsua.net (Postfix) with ESMTP id 90F81105082 for ; Mon, 10 Apr 2006 16:54:53 +0300 (EEST) Received: from exim (helo=mail.atlas.kiev.ua) by mail.atlas.kiev.ua with local-smtp (Exim 4.43 (FreeBSD)) id 1FSwwf-0008Ly-EX for freebsd-hackers@freebsd.org; Mon, 10 Apr 2006 17:00:45 +0300 Received: from [172.16.4.222] (helo=dragon60116) by mail.atlas.kiev.ua with esmtp (Exim 4.43 (FreeBSD)) id 1FSwwf-0008Lr-8Z for freebsd-hackers@freebsd.org; Mon, 10 Apr 2006 17:00:45 +0300 Date: Mon, 10 Apr 2006 16:55:11 +0300 From: Nickolas X-Mailer: The Bat! (v3.71.04) UNREG / CD5BF9353B3B7091 Organization: atlas X-Priority: 3 (Normal) Message-ID: <1879959918.20060410165511@atlas.ua> To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at tsua.net Subject: Context switching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Nickolas List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 13:54:56 -0000 Hello All! I'm porting a CPI card driver from linux to FreeBSD. Some initialization routines require much time (~1-2 seconds). Initialization of hardware should be done during opening device special file. So, I need to switch thread context. I'm doing it in such way: mi_switch(SW_VOL, choosethread()); Main trouble: system panic after program exit. dmesg output: -------------------------- Fatal trap 12: page fault while in user mode fault virtual address = 0xbfbfe5bc fault code = user write, protection violation instruction pointer = 0x1f:0x8074604 stack pointer = 0x2f:0xbfbfe5c0 frame pointer = 0x2f:0xbfbfe5f8 code segment = base 0xc090f8c0, limit 0x0, type 0x13 = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 472 (bash) trap number = 12 panic: page fault -------------------------- Please, tell how correct context switching should be implemented? OS version: FreeBSD 5.4 -- Best regards, Nickolas mailto:nickolas@atlas.ua From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 14:05:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9310B16A407; Mon, 10 Apr 2006 14:05:09 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C1C143D5A; Mon, 10 Apr 2006 14:05:02 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id 07F3A35707; Mon, 10 Apr 2006 16:05:01 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 68ACA6D121; Mon, 10 Apr 2006 16:04:46 +0200 (CEST) Date: Mon, 10 Apr 2006 16:04:46 +0200 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060410140446.GB14117@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> <20060410074740.GD1006@britannica.bec.de> <17466.25085.446099.450392@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17466.25085.446099.450392@bhuda.mired.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 14:05:09 -0000 On Mon, Apr 10, 2006 at 09:47:41AM -0400, Mike Meyer wrote: > In <20060410074740.GD1006@britannica.bec.de>, joerg@britannica.bec.de typed: > > On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: > > > Firewire would seem to be a lot like USB - hot pluggable and > > > chainable, though I'm not sure if something like a firewire hub. What > > > does it to do wire down device addresses? > > FireWire devices have uuids, you can simply enumerate them using those > > :-) > > Where do those come from? Assigned by the user? Dynamically by the > controller? By the manufacturer? IIRC by the manufacturer, like MAC addresses. Joerg From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 14:05:09 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9310B16A407; Mon, 10 Apr 2006 14:05:09 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C1C143D5A; Mon, 10 Apr 2006 14:05:02 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id 07F3A35707; Mon, 10 Apr 2006 16:05:01 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 68ACA6D121; Mon, 10 Apr 2006 16:04:46 +0200 (CEST) Date: Mon, 10 Apr 2006 16:04:46 +0200 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060410140446.GB14117@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> <20060410074740.GD1006@britannica.bec.de> <17466.25085.446099.450392@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17466.25085.446099.450392@bhuda.mired.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 14:05:09 -0000 On Mon, Apr 10, 2006 at 09:47:41AM -0400, Mike Meyer wrote: > In <20060410074740.GD1006@britannica.bec.de>, joerg@britannica.bec.de typed: > > On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: > > > Firewire would seem to be a lot like USB - hot pluggable and > > > chainable, though I'm not sure if something like a firewire hub. What > > > does it to do wire down device addresses? > > FireWire devices have uuids, you can simply enumerate them using those > > :-) > > Where do those come from? Assigned by the user? Dynamically by the > controller? By the manufacturer? IIRC by the manufacturer, like MAC addresses. Joerg From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 14:09:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E001B16A400 for ; Mon, 10 Apr 2006 14:09:07 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44B3F43D6B for ; Mon, 10 Apr 2006 14:09:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k3AE8v3L030707; Mon, 10 Apr 2006 08:08:57 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <443A66F0.7050802@samsco.org> Date: Mon, 10 Apr 2006 08:08:48 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nickolas References: <1879959918.20060410165511@atlas.ua> In-Reply-To: <1879959918.20060410165511@atlas.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: Context switching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 14:09:08 -0000 Nickolas wrote: > Hello All! > > I'm porting a CPI card driver from linux to FreeBSD. > Some initialization routines require much time (~1-2 seconds). > Initialization of hardware should be done during opening device > special file. So, I need to switch thread context. > > I'm doing it in such way: > > mi_switch(SW_VOL, choosethread()); > > Main trouble: system panic after program exit. > > dmesg output: > -------------------------- > Fatal trap 12: page fault while in user mode > fault virtual address = 0xbfbfe5bc > fault code = user write, protection violation > instruction pointer = 0x1f:0x8074604 > stack pointer = 0x2f:0xbfbfe5c0 > frame pointer = 0x2f:0xbfbfe5f8 > code segment = base 0xc090f8c0, limit 0x0, type 0x13 > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 472 (bash) > trap number = 12 > panic: page fault > -------------------------- > > Please, tell how correct context switching should be implemented? > > OS version: FreeBSD 5.4 > tsleep and msleep are the appropriate ways to context switch. mi_switch is an implementation detail of the scheduler. Scott From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 13:14:08 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DC8A16A402 for ; Mon, 10 Apr 2006 13:14:08 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCFA43D45 for ; Mon, 10 Apr 2006 13:14:08 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms069.mailsrvcs.net ([192.168.1.2]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IXI00261CRGL422@vms042.mailsrvcs.net> for hackers@freebsd.org; Mon, 10 Apr 2006 08:14:05 -0500 (CDT) Date: Mon, 10 Apr 2006 08:14:04 -0500 (CDT) From: Sergey Babkin To: "M. Warner Losh" , mwm-keyword-freebsdhackers.102a7e@mired.org Message-id: <7062548.1416391144674845516.JavaMail.root@vms069.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 10 Apr 2006 14:35:39 +0000 Cc: ceri@submonkey.net, babkin@users.sourceforge.net, hackers@freebsd.org, scottl@samsco.org Subject: Re: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 13:14:08 -0000 >From: "M. Warner Losh" >usb assigns addresses dynamically. Everyone else does it basically >statically. PCI slot/device numbers are static, but extreme >configurations can change the bus number. Some USB devices (though not all of them) provide a unique device ID. If this ID is available, binding to a particular device is straightforward. The problems start when the device get replaced. For example, an USB printer dies and you replace it with another one. Form a tech support standpoint it's convenient if the new printer gets silently recognized as a replacement of the old one. -SB From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 15:33:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD03016A406 for ; Mon, 10 Apr 2006 15:33:15 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D285943D4C for ; Mon, 10 Apr 2006 15:33:14 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.146] (helo=anti-virus03-09) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1FSyO8-0000EW-Tx; Mon, 10 Apr 2006 16:33:12 +0100 Received: from [80.192.25.195] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1FSyO8-00085E-CU; Mon, 10 Apr 2006 16:33:12 +0100 Message-ID: <443A7AB7.8060101@dial.pipex.com> Date: Mon, 10 Apr 2006 16:33:11 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: No auto reboot after panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 15:33:15 -0000 (This message started life on questions, but no responses :-( If there's a better list to try, please point me! I have no clue how rebooting actually works). Setup: Dell 2850 running i386 FreeBSD 5.4-p5 (or so), ACPI enabled and apparently working (shutdown -p or -r work fine). After a kernel panic, the console showed "Automatic reboot in 60 seconds or press any key to interrupt", (or words to that effect), but actually the machine just sat there for several hours. When I got to the console, pressing a key said it was interrupting the automatic reboot (as if the key press had happened in the 60 second window) and pressing another key rebooted the server. Does anyone have any idea why the server didn't reboot automatically, and what might make it reboot next time it panics (if there is a next time)? I'm sure I've seen a similar problem mentioned before, but searching the mail archives and google didn't turn up anything useful that I could see. Thanks, --Alex From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 16:16:23 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCA5F16A400 for ; Mon, 10 Apr 2006 16:16:23 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E05743D49 for ; Mon, 10 Apr 2006 16:16:23 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 66D6F19F2C for ; Mon, 10 Apr 2006 09:16:22 -0700 (PDT) Message-ID: <443A84D5.8040503@bitfreak.org> Date: Mon, 10 Apr 2006 09:16:21 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net> <17465.32905.727289.260996@bhuda.mired.org> <20060409.185335.105395062.imp@bsdimp.com> <17465.51033.78362.699332@bhuda.mired.org> <20060410074740.GD1006@britannica.bec.de> <17466.25085.446099.450392@bhuda.mired.org> <20060410140446.GB14117@britannica.bec.de> In-Reply-To: <20060410140446.GB14117@britannica.bec.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: What's in a (device) name? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 16:16:23 -0000 joerg@britannica.bec.de wrote: > On Mon, Apr 10, 2006 at 09:47:41AM -0400, Mike Meyer wrote: >> In <20060410074740.GD1006@britannica.bec.de>, joerg@britannica.bec.de typed: >>> On Sun, Apr 09, 2006 at 10:47:53PM -0400, Mike Meyer wrote: >>>> Firewire would seem to be a lot like USB - hot pluggable and >>>> chainable, though I'm not sure if something like a firewire hub. What >>>> does it to do wire down device addresses? >>> FireWire devices have uuids, you can simply enumerate them using those >>> :-) >> Where do those come from? Assigned by the user? Dynamically by the >> controller? By the manufacturer? > > IIRC by the manufacturer, like MAC addresses. I think you mean the 64-bit EUI? From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 18:32:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAEFC16A402 for ; Mon, 10 Apr 2006 18:32:49 +0000 (UTC) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B12D43D79 for ; Mon, 10 Apr 2006 18:32:42 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id k3AIWfMZ079055 for ; Mon, 10 Apr 2006 13:32:41 -0500 (CDT) (envelope-from rand@meridian-enviro.com) Date: Mon, 10 Apr 2006 13:32:40 -0500 Message-ID: <87slol2sdz.wl%rand@meridian-enviro.com> From: "Douglas K. Rand" To: freebsd-hackers@freebsd.org User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: ClamAV 0.88/1389/Mon Apr 10 07:58:55 2006 on newman.meridian-enviro.com X-Virus-Status: Clean Subject: Nagios & Linux Threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 18:32:49 -0000 I'm running Nagios 2.0 on FreeBSD 6 and I occasionally experience the problem originally discussed http://www.freebsd.org/cgi/getmsg.cgi?fetch=165398+171880+/usr/local/www/db/text/2005/freebsd-hackers/20050821.freebsd-hackers (That is: a forked nagios process that consumes as much CPU time as it can.) Living with this problem while annoying isn't the end of the world. I was looking for workarounds. One solution for a work around was to use Linux threads. I was wondering if anybody had managed to get Nagios 2.0 to use Linux threads successfully. And if so, what changes to the port were required. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 19:47:57 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F1F916A400 for ; Mon, 10 Apr 2006 19:47:57 +0000 (UTC) (envelope-from bms@spc.org) Received: from mindfull.spc.org (mindfull.spc.org [83.167.185.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0C3643D53 for ; Mon, 10 Apr 2006 19:47:56 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org ([83.167.185.2]) by mindfull.spc.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FT2MW-0005me-1J; Mon, 10 Apr 2006 20:47:48 +0100 Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 0386465499; Mon, 10 Apr 2006 20:47:48 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 74910-04-2; Mon, 10 Apr 2006 20:47:46 +0100 (BST) Received: by arginine.spc.org (Postfix, from userid 1078) id D102C653F9; Mon, 10 Apr 2006 20:47:46 +0100 (BST) Date: Mon, 10 Apr 2006 20:47:46 +0100 From: Bruce M Simpson To: "M. Warner Losh" Message-ID: <20060410194746.GY80492@spc.org> References: <44383346.2030207@samsco.org> <17464.16087.217524.843667@bhuda.mired.org> <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060409.184825.99254285.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Organization: Incunabulum X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mindfull.spc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - spc.org X-Source: X-Source-Args: X-Source-Dir: Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@freebsd.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 19:47:57 -0000 On Sun, Apr 09, 2006 at 06:48:25PM -0600, M. Warner Losh wrote: > I though thtis was already supported. We export bus/slot/function > information devd, which can be used to configure the device. If I've read the specs or code incorrectly please do let me know -- my reading here is based on the PCI code as I understand it to be. As I understand things, the bus/slot/function numbers in pci(9), the *slot* number isn't guaranteed to have any meaning in geographic reality; it's purely what the PCI logic thinks the bus topology looks like and hence what the device numbers are. See BUGS in pci(9). It won't tell you that a given card is in a given slot with any degree of certainty or consistency across the range of backplanes available from multiple vendors -- although people may like to give PICMG a try as I hear such boards are consistent about such things. In the old Microsoft-specified $PIR tables there was a column which allowed you to map the bus/device/function tuple we use to a physical slot number, but this only ran 1-6. With multiple PCI buses and slot types, as well as multifunction devices, this information quickly became unusable and unreliable, although src/tools/tools/pirtool will happily display this information. ACPI as you no doubt know does away with the $PIR tables, although many BIOS still export them to allow legacy DOS programs which use PCI to work. There is an extension to ACPI which adds geographical slot addressing to the device tree but I haven't seen any systems which support it. Regards, BMS P.S. I have some notes somewhere about the ACPI geog stuff but can't remember if I posted them or filed them elsewhere -- check the XORP mailing lists, I think we bashed this out there around 14 months ago. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 20:13:56 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 776D716A406 for ; Mon, 10 Apr 2006 20:13:56 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FDFA43D45 for ; Mon, 10 Apr 2006 20:13:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3AKAa4w044559; Mon, 10 Apr 2006 14:10:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 10 Apr 2006 14:10:42 -0600 (MDT) Message-Id: <20060410.141042.25162164.imp@bsdimp.com> To: bms@spc.org From: "M. Warner Losh" In-Reply-To: <20060410194746.GY80492@spc.org> References: <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> <20060410194746.GY80492@spc.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@FreeBSD.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 20:13:56 -0000 In message: <20060410194746.GY80492@spc.org> Bruce M Simpson writes: : On Sun, Apr 09, 2006 at 06:48:25PM -0600, M. Warner Losh wrote: : > I though thtis was already supported. We export bus/slot/function : > information devd, which can be used to configure the device. : : If I've read the specs or code incorrectly please do let me know -- : my reading here is based on the PCI code as I understand it to be. : : As I understand things, the bus/slot/function numbers in pci(9), the : *slot* number isn't guaranteed to have any meaning in geographic reality; : it's purely what the PCI logic thinks the bus topology looks like and : hence what the device numbers are. See BUGS in pci(9). The device number is fixed for a given mother board slot. It will never change unless you change the mother board. However, for stacking topologies the slot is the position in the stack. : It won't tell you that a given card is in a given slot with any degree : of certainty or consistency across the range of backplanes available : from multiple vendors -- although people may like to give PICMG a try : as I hear such boards are consistent about such things. Correct. : In the old Microsoft-specified $PIR tables there was a column which : allowed you to map the bus/device/function tuple we use to a physical : slot number, but this only ran 1-6. With multiple PCI buses and slot : types, as well as multifunction devices, this information quickly became : unusable and unreliable, although src/tools/tools/pirtool will happily : display this information. Correct. : ACPI as you no doubt know does away with the $PIR tables, although many : BIOS still export them to allow legacy DOS programs which use PCI to work. : There is an extension to ACPI which adds geographical slot addressing : to the device tree but I haven't seen any systems which support it. OK. Physical slot information. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 21:23:12 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2758B16A401 for ; Mon, 10 Apr 2006 21:23:12 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D28843D66 for ; Mon, 10 Apr 2006 21:23:04 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 9DFE919F2C; Mon, 10 Apr 2006 14:23:03 -0700 (PDT) Message-ID: <443ACCB6.8080306@bitfreak.org> Date: Mon, 10 Apr 2006 14:23:02 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "M. Warner Losh" References: <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> <20060410194746.GY80492@spc.org> <20060410.141042.25162164.imp@bsdimp.com> In-Reply-To: <20060410.141042.25162164.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@FreeBSD.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 21:23:12 -0000 I think at this point it's been pretty well established that: - Device naming and unit numbering is not stable enough to avoid breakage across hardware changes. - There is a need for generic and/or descriptive interface naming independent of driver- and probe-order-based naming. - There are static bits of information available about each device in the system that can be used to locate a specific device that would be sufficient to allow assignment of a network configuration to a physical device, not it's attached name. If I were to write an rc.d script to use descriptive network interface names and wire configs to static hardware identification, would there be support for such a feature? From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 11 01:24:10 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA37916A401 for ; Tue, 11 Apr 2006 01:24:10 +0000 (UTC) (envelope-from joseph@randomnetworks.com) Received: from rhyll.com (rhyll.com [70.84.96.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 402FE43D75 for ; Tue, 11 Apr 2006 01:24:10 +0000 (GMT) (envelope-from joseph@randomnetworks.com) Received: from localhost (localhost [127.0.0.1]) by rhyll.com (Postfix) with ESMTP id BDE7D2E07F; Mon, 10 Apr 2006 18:24:09 -0700 (PDT) Received: from rhyll.com ([127.0.0.1]) by localhost (sm01.rhyll.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08287-08; Mon, 10 Apr 2006 18:24:08 -0700 (PDT) Received: from [192.168.1.102] (adsl-69-225-42-239.dsl.skt2ca.pacbell.net [69.225.42.239]) by rhyll.com (Postfix) with ESMTP id 14D9E2E036; Mon, 10 Apr 2006 18:24:08 -0700 (PDT) In-Reply-To: <443ACCB6.8080306@bitfreak.org> References: <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> <20060410194746.GY80492@spc.org> <20060410.141042.25162164.imp@bsdimp.com> <443ACCB6.8080306@bitfreak.org> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <40B160C1-719B-4FCA-A192-75432F3738D5@randomnetworks.com> Content-Transfer-Encoding: 7bit From: Joseph Scott Date: Mon, 10 Apr 2006 18:24:12 -0700 To: Darren Pilgrim X-Mailer: Apple Mail (2.749.3) X-Virus-Scanned: amavisd-new at rhyll.com Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@FreeBSD.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 01:24:10 -0000 On Apr 10, 2006, at 2:23 PM, Darren Pilgrim wrote: > I think at this point it's been pretty well established that: > > - Device naming and unit numbering is not stable enough to avoid > breakage across hardware changes. > - There is a need for generic and/or descriptive interface naming > independent of driver- and probe-order-based naming. > - There are static bits of information available about each device > in the system that can be used to locate a specific device that > would be sufficient to allow assignment of a network configuration > to a physical device, not it's attached name. > > If I were to write an rc.d script to use descriptive network > interface names and wire configs to static hardware identification, > would there be support for such a feature? Being mostly a lurker on this list I don't know that my vote would count for much, but yes I'd support such a feature. Thank you also for outlining the issues for this thread in a simple manner. -- Joseph Scott joseph@randomnetworks.com http://joseph.randomnetworks.com/ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 11 05:35:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B30C16A400 for ; Tue, 11 Apr 2006 05:35:31 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.19.101.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D6C43D45 for ; Tue, 11 Apr 2006 05:35:30 +0000 (GMT) (envelope-from hugo@barafranca.com) Received: from localhost (localhost [127.0.0.1]) by mail.barafranca.com (Postfix) with ESMTP id 9B5E6C38FD for ; Tue, 11 Apr 2006 05:40:51 +0000 (UTC) Received: from mail.barafranca.com ([67.19.101.164]) by localhost (mail.barafranca.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61179-06 for ; Tue, 11 Apr 2006 05:40:51 +0000 (UTC) Received: from [192.168.0.1] (unknown [81.84.174.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTP id A7A01C38EE for ; Tue, 11 Apr 2006 05:40:50 +0000 (UTC) Message-ID: <443B402F.2060409@barafranca.com> Date: Tue, 11 Apr 2006 06:35:43 +0100 From: Hugo Silva User-Agent: Thunderbird 1.5 (X11/20060318) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <87slol2sdz.wl%rand@meridian-enviro.com> In-Reply-To: <87slol2sdz.wl%rand@meridian-enviro.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at barafranca.com X-Spam-Status: No, score=-0.838 tagged_above=-1 required=4 tests=[AWL=-0.539, BAYES_00=-2.599, PERCENT_RANDOM=2.3] X-Spam-Score: -0.838 X-Spam-Level: Subject: Re: Nagios & Linux Threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 05:35:31 -0000 Douglas K. Rand wrote: > I'm running Nagios 2.0 on FreeBSD 6 and I occasionally experience the > problem originally discussed http://www.freebsd.org/cgi/getmsg.cgi?fetch=165398+171880+/usr/local/www/db/text/2005/freebsd-hackers/20050821.freebsd-hackers > > (That is: a forked nagios process that consumes as much CPU time as it > can.) > > Living with this problem while annoying isn't the end of the world. I > was looking for workarounds. > > One solution for a work around was to use Linux threads. I was > wondering if anybody had managed to get Nagios 2.0 to use Linux > threads successfully. And if so, what changes to the port were > required. > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > I've been running Nagios 2.0 on FreeBSD 6 for some time now, and never experienced this problem - just my 2 cents. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 11 15:20:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED3FD16A403 for ; Tue, 11 Apr 2006 15:20:48 +0000 (UTC) (envelope-from lists@sply.org) Received: from inc.ru (mail6.net.incru.net [62.205.161.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2E6743D67 for ; Tue, 11 Apr 2006 15:20:45 +0000 (GMT) (envelope-from lists@sply.org) Received: from [62.205.161.39] (account lists@sply.org) by inc.ru (CommuniGate Pro WebUser 4.1.8) with HTTP id 5333059; Tue, 11 Apr 2006 19:18:43 +0400 From: "Sply Splyeff" To: Peter Jeremy X-Mailer: CommuniGate Pro WebUser Interface v.4.1.8 Date: Tue, 11 Apr 2006 19:18:43 +0400 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="KOI8-R" Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org Subject: Re: setuid scripts wrapper (RFC, proposal) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 15:20:49 -0000 I've uploaded suidscript.c with updates: http://suidscript.sply.org/suidscript/suidscript.c http://suidscript.sply.org/suidscript.tgz Current implementation checks the safety of an interpreter path and of a script path - all nodes required to be owned by root or script owner and writable only by owner. It's a big limitation, but it works in most cases. I've tried /dev/fd/ way, but it requires fdescfs mounted which is not common for different freebsd versions and sometimes seems a little buggy. I've included suidscript_fdesc.c which implements /dev/fd/*, but I haven't evere tested it because mount_fdescfs crashes. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 12 11:22:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F12D16A400 for ; Wed, 12 Apr 2006 11:22:36 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3262E43D48 for ; Wed, 12 Apr 2006 11:22:36 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 18DEA171C0; Wed, 12 Apr 2006 13:22:35 +0200 (CEST) Date: Wed, 12 Apr 2006 13:22:35 +0200 From: Ed Schouten To: FreeBSD Hackers Message-ID: <20060412112235.GF87726@hoeg.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UlsYxwg8UDQn+EKZ" Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Wed, 12 Apr 2006 11:39:30 +0000 Subject: NAT-PT using pfil and if_clone - have fun :) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2006 11:22:36 -0000 --UlsYxwg8UDQn+EKZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello folks, The last few weeks I've been hacking on a NAT-PT implementation for the FreeBSD operating system in my spare time. I tried to use the NAT-PT code in KAME's tree, but that was for FreeBSD 5.4 and didn't compile properly. Because its implementation was also quite evil (hooks in the ip_input and ip6_input functions to capture packets), I thought: why not capture IPv4 traffic using pfil? That way we can also build it as a module. I also thought it would be more useful to send and receive IPv6 packets through a pseudo-interface, just like faith (except that you don't need the faithd). Today I'm releasing this code. It's also my 20th birthday, so instead of getting presents, I also have the honour of giving one away: http://g-rave.nl/projects/freebsd/natpt/distfiles/freebsd-natpt-20060412-bi= rthday.diff One note: there are still a few caveats in this code: - IPv4 source port is the same as IPv6 source port - ICMP and FTP are not translated - Timeout value for the state table is just a guess (15 minutes). Any feedback would be welcome. :) Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --UlsYxwg8UDQn+EKZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEPOL752SDGA2eCwURAv/GAJ0Shi5KR2tURsqZgeAJ0Y0xfHGfjwCfcczZ VDS3k0Bmw3tWs8hlWKVWuZc= =RdIG -----END PGP SIGNATURE----- --UlsYxwg8UDQn+EKZ-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 12 21:50:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A52E116A400 for ; Wed, 12 Apr 2006 21:50:25 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D10343D6B for ; Wed, 12 Apr 2006 21:50:24 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3CLoL8x002020; Wed, 12 Apr 2006 21:50:21 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3CLoLIZ002019; Wed, 12 Apr 2006 21:50:21 GMT (envelope-from marco) Date: Wed, 12 Apr 2006 21:50:21 +0000 From: Marco van Tol To: freebsd-hackers@freebsd.org Message-ID: <20060412215021.GB1146@tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1395/Wed Apr 12 18:44:32 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org X-Mailman-Approved-At: Wed, 12 Apr 2006 22:00:36 +0000 Cc: Marco van Tol Subject: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2006 21:50:25 -0000 Hi there, My apologies if this is the wrong list to ask this kind of question. I would appreciate a pointer to the correct list if it is please. :) I noticed in the code for gkrellm /usr/ports/sysutils/gkrellm2 that SMP per-cpu statistics were not yet supported under FreeBSD, and decided to check whether I could add that. (I'm running a (dual-core) Athlon64 X2 with FreeBSD 6.1-PRERELEASE) I can't find sample code and/or documentation on how to acquire that information from the kernel. I checked - gkrellm2 itself, which uses kern.cp_time in /src/sysdeps/freebsd.c - top, which also uses kern.cp_time in /usr/src/usr.bin/top/machine.c Some browsing around the internet doesn't get me much further either unfortunately. I keep hitting the per-cpu statistics mentioned with regard to uma(9). Under linux this can be acquired via /proc/stat. (And gkrellm looks realy funky with per-cpu stats, but that may or may not be relevant depending on the reader of this mail I guess ;) Is there an interface under FreeBSD to acquire the necessary per-cpu statistics? Thank you very much in advance, appreciated, Marco van Tol -- Gisteren is het niet gelukt. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 12 22:50:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 069C816A401 for ; Wed, 12 Apr 2006 22:50:15 +0000 (UTC) (envelope-from gs_stoller@juno.com) Received: from outbound-mail.nyc.untd.com (outbound-mail.nyc.untd.com [64.136.20.164]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B89943D45 for ; Wed, 12 Apr 2006 22:50:15 +0000 (GMT) (envelope-from gs_stoller@juno.com) Received: from webmail06.nyc.untd.com (webmail06.nyc.untd.com [10.141.27.146]) by smtpout04.nyc.untd.com with SMTP id AABCD5A97A32KRDJ for (sender ); Wed, 12 Apr 2006 15:49:33 -0700 (PST) Received: (from gs_stoller@juno.com) by webmail06.nyc.untd.com (jqueuemail) id LMSTR7CT; Wed, 12 Apr 2006 15:49:21 PDT Received: from [69.125.135.219] by webmail06.nyc.untd.com with HTTP: Wed, 12 Apr 2006 22:48:44 GMT X-Originating-IP: [69.125.135.219] Mime-Version: 1.0 From: "gs_stoller@juno.com" Date: Wed, 12 Apr 2006 22:48:44 GMT To: freebsd-hackers@freebsd.org X-Mailer: Webmail Version 4.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Type: text/plain Message-Id: <20060412.154921.26277.710543@webmail06.nyc.untd.com> X-ContentStamp: 8:4:645692108 X-UNTD-OriginStamp: /s5f1SIGSI3+WdnoYQ8yRMdj5FlmvkF06ACzq7UTfCY4R1DiN3/2/w== X-UNTD-Peer-Info: 10.141.27.146|webmail06.nyc.untd.com|webmail06.nyc.untd.com|gs_stoller@juno.com X-Mailman-Approved-At: Wed, 12 Apr 2006 23:20:08 +0000 Subject: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2006 22:50:16 -0000 I tried out FreeBSD 6.0 (sorry, I copied just part or uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") and was surprised to find that things in the echo command didn't work. When I typed = echo "a\tb" I got a\tb , no tab replacing the "\t" Same for "\n". When I tried to type echo "b" where stands for hitting the tab key, when I hit the first time, nothing happened, when I hit it immediately afterward, I got an ls -A listing. I did manage to get a tab into the string by typing something else there in place of tab and then editting the command with r (the replace function) to put a tab in it. When I hit similarly immediately after the command prompt I got a question asking if I wanted to see the 424 (or was it 242 ?) possibilities and the computer responded immediately after a 'y' or 'n' key was hit. How could this happen? The echo command (and builtin , I tried both [and I presume that echo by itself invokes the builtin ]) should be standard? From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 12 23:22:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B319416A405 for ; Wed, 12 Apr 2006 23:22:38 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 027FF43D7D for ; Wed, 12 Apr 2006 23:22:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 319051A4D8B; Wed, 12 Apr 2006 16:22:28 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5630551A02; Wed, 12 Apr 2006 19:22:27 -0400 (EDT) Date: Wed, 12 Apr 2006 19:22:27 -0400 From: Kris Kennaway To: "gs_stoller@juno.com" Message-ID: <20060412232226.GA33152@xor.obsecurity.org> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <20060412.154921.26277.710543@webmail06.nyc.untd.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2006 23:22:38 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: > I tried out FreeBSD 6.0 (sorry, I copied just part or > uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - > Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") No you didn't, since no version of FreeBSD reports itself as LINUX from uname. Kris --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEPYuyWry0BWjoQKURAsQFAJwLczERaYE9IkrhSwHApGN9eINqOgCg1qYC fCFB8ZI6Vtn6flsIq5gl0/g= =PuWE -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 00:49:08 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D258816A400 for ; Thu, 13 Apr 2006 00:49:08 +0000 (UTC) (envelope-from stsp@stsp.in-berlin.de) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C41B43D49 for ; Thu, 13 Apr 2006 00:49:07 +0000 (GMT) (envelope-from stsp@stsp.in-berlin.de) X-Envelope-From: stsp@stsp.in-berlin.de Received: from dice.stsp.lan (brln-d9ba5ba6.pool.mediaWays.net [217.186.91.166]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id k3D0n233024710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Apr 2006 02:49:03 +0200 Received: by dice.stsp.lan (nbSMTP-1.01-cvs) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) stsp@stsp.in-berlin.de; Thu, 13 Apr 2006 02:49:03 +0200 (CEST) Date: Thu, 13 Apr 2006 02:48:51 +0200 From: Stefan Sperling To: Kris Kennaway Message-ID: <20060413004851.GA1194@dice.stsp.lan> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <20060412232226.GA33152@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060412232226.GA33152@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i X-Spam-Score: (-0.129) AWL,BAYES_40,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Cc: hackers@freebsd.org Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 00:49:08 -0000 On Wed, Apr 12, 2006 at 07:22:27PM -0400, Kris Kennaway wrote: > On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: > > I tried out FreeBSD 6.0 (sorry, I copied just part or > > uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - > > Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") > > No you didn't, since no version of FreeBSD reports itself as LINUX > from uname. Unless uname is a Linux binary. -- stefan http://stsp.in-berlin.de PGP Key: 0xF59D25F0 From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 00:54:12 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B63816A405 for ; Thu, 13 Apr 2006 00:54:12 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5638743D4C for ; Thu, 13 Apr 2006 00:54:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3B2DC1A4D8B; Wed, 12 Apr 2006 17:54:12 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9AC6551A02; Wed, 12 Apr 2006 20:54:11 -0400 (EDT) Date: Wed, 12 Apr 2006 20:54:11 -0400 From: Kris Kennaway To: Stefan Sperling Message-ID: <20060413005411.GA34686@xor.obsecurity.org> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <20060412232226.GA33152@xor.obsecurity.org> <20060413004851.GA1194@dice.stsp.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <20060413004851.GA1194@dice.stsp.lan> User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org, Kris Kennaway Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 00:54:12 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 13, 2006 at 02:48:51AM +0200, Stefan Sperling wrote: > On Wed, Apr 12, 2006 at 07:22:27PM -0400, Kris Kennaway wrote: > > On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: > > > I tried out FreeBSD 6.0 (sorry, I copied just part or > > > uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - > > > Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") > >=20 > > No you didn't, since no version of FreeBSD reports itself as LINUX > > from uname. >=20 > Unless uname is a Linux binary. FreeBSD doesn't ship uname as a Linux binary either :-) Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEPaEzWry0BWjoQKURAkd8AKDcv3LfGC0PV2y85QLFzM3xmWGDoQCg3SHi cbRN6bxPTmaWHE1E0c60Zyo= =7+HM -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 00:57:50 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 364A516A400 for ; Thu, 13 Apr 2006 00:57:50 +0000 (UTC) (envelope-from anthony.maher@uts.edu.au) Received: from dib.itd.uts.edu.au (dib.itd.uts.edu.au [138.25.22.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id B05AD43D46 for ; Thu, 13 Apr 2006 00:57:49 +0000 (GMT) (envelope-from anthony.maher@uts.edu.au) Received: by dib.itd.uts.edu.au (Postfix, from userid 1011) id 72EF8499B7; Thu, 13 Apr 2006 10:57:10 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by dib.itd.uts.edu.au (Postfix/Intermediary) with ESMTP id 65814497DF; Thu, 13 Apr 2006 10:57:10 +1000 (EST) Received: from vimes (vimes.itd.uts.edu.au [138.25.243.34]) by dib.itd.uts.edu.au (Postfix/Ingress) with ESMTP id 501A3499B7; Thu, 13 Apr 2006 10:57:10 +1000 (EST) Received: from [138.25.81.47] by postoffice.uts.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTPS id <0IXM007XSYOCB900@postoffice.uts.edu.au>; Thu, 13 Apr 2006 10:57:48 +1000 (EST) Date: Thu, 13 Apr 2006 10:57:48 +1000 From: Tony Maher In-reply-to: <20060413005411.GA34686@xor.obsecurity.org> To: Kris Kennaway Message-id: <443DA20C.4070509@uts.edu.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Enigmail-Version: 0.93.0.0 References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <20060412232226.GA33152@xor.obsecurity.org> <20060413004851.GA1194@dice.stsp.lan> <20060413005411.GA34686@xor.obsecurity.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060306 Cc: hackers@freebsd.org, Stefan Sperling Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 00:57:50 -0000 Kris Kennaway wrote: > On Thu, Apr 13, 2006 at 02:48:51AM +0200, Stefan Sperling wrote: > >>On Wed, Apr 12, 2006 at 07:22:27PM -0400, Kris Kennaway wrote: >> >>>On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: >>> >>>> I tried out FreeBSD 6.0 (sorry, I copied just part or >>>> uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - >>>>Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") >>> >>>No you didn't, since no version of FreeBSD reports itself as LINUX >>>from uname. >> >>Unless uname is a Linux binary. > > > FreeBSD doesn't ship uname as a Linux binary either :-) > > Kris /compat/linux/bin/uname -a Linux karma.internal 2.4.2 FreeBSD 6.1-PRERELEASE #0: Tue Apr 4 22:24:50 EST 2006 i686 i686 i386 GNU/Linux -- Tony Maher Data Grid Specialist email: anthony.maher@uts.edu.au Computational Research Support Unit phone: +61 2 9514 2265 Department of Mathematical Sciences fax: +61 2 9514 2248 University of Technology, Sydney PO Box 123 Broadway NSW 2007 From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 01:00:32 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B27816A403 for ; Thu, 13 Apr 2006 01:00:32 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: from capeta.freebsdbrasil.com.br (vrrp.freebsdbrasil.com.br [200.210.70.30]) by mx1.FreeBSD.org (Postfix) with SMTP id EA21543D46 for ; Thu, 13 Apr 2006 01:00:03 +0000 (GMT) (envelope-from eksffa@freebsdbrasil.com.br) Received: (qmail 35454 invoked by uid 0); 12 Apr 2006 22:01:03 -0300 Received: from eksffa@freebsdbrasil.com.br by capeta.freebsdbrasil.com.br by uid 82 with qmail-scanner-1.22 (spamassassin: 2.64. Clear:RC:1(200.210.42.5):. Processed in 0.701192 secs); 13 Apr 2006 01:01:03 -0000 Received: from unknown (HELO ?10.69.69.69?) (200.210.42.5) by capeta.freebsdbrasil.com.br with SMTP; 12 Apr 2006 22:01:02 -0300 Message-ID: <443DA28D.2040503@freebsdbrasil.com.br> Date: Wed, 12 Apr 2006 21:59:57 -0300 From: Patrick Tracanelli Organization: FreeBSD Brasil LTDA User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051013 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <20060412232226.GA33152@xor.obsecurity.org> <20060413004851.GA1194@dice.stsp.lan> <20060413005411.GA34686@xor.obsecurity.org> In-Reply-To: <20060413005411.GA34686@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, Stefan Sperling Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 01:00:32 -0000 Kris Kennaway wrote: > On Thu, Apr 13, 2006 at 02:48:51AM +0200, Stefan Sperling wrote: > >>On Wed, Apr 12, 2006 at 07:22:27PM -0400, Kris Kennaway wrote: >> >>>On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: >>> >>>> I tried out FreeBSD 6.0 (sorry, I copied just part or >>>> uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - >>>>Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") >>> >>>No you didn't, since no version of FreeBSD reports itself as LINUX >>>from uname. >> >>Unless uname is a Linux binary. > > > FreeBSD doesn't ship uname as a Linux binary either :-) > > Kris Unless under Linux mode... # /compat/linux/bin/uname -a Linux claire.freebsdbrasil.com.br 2.4.2 FreeBSD 7.0-CURRENT #15: Wed Apr 12 13:23:25 BRST 2006 i686 i686 i386 GNU/Linux # chroot /compat/linux /bin/bash bash-2.05b# uname -a Linux claire.freebsdbrasil.com.br 2.4.2 FreeBSD 7.0-CURRENT #15: Wed Apr 12 13:23:25 BRST 2006 i686 i686 i386 GNU/Linux -- Patrick Tracanelli FreeBSD Brasil LTDA. (31) 3281-9633 / 3281-3547 316601@sip.freebsdbrasil.com.br http://www.freebsdbrasil.com.br "Long live Hanin Elias, Kim Deal!" From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 02:03:26 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F038216A403 for ; Thu, 13 Apr 2006 02:03:26 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6C4E43D45 for ; Thu, 13 Apr 2006 02:03:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8771A1A4D90; Wed, 12 Apr 2006 19:03:26 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 50CC1529B4; Wed, 12 Apr 2006 22:03:25 -0400 (EDT) Date: Wed, 12 Apr 2006 22:03:24 -0400 From: Kris Kennaway To: Tony Maher Message-ID: <20060413020323.GA35500@xor.obsecurity.org> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <20060412232226.GA33152@xor.obsecurity.org> <20060413004851.GA1194@dice.stsp.lan> <20060413005411.GA34686@xor.obsecurity.org> <443DA20C.4070509@uts.edu.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline In-Reply-To: <443DA20C.4070509@uts.edu.au> User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org, Stefan Sperling , Kris Kennaway Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 02:03:27 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 13, 2006 at 10:57:48AM +1000, Tony Maher wrote: > Kris Kennaway wrote: > > On Thu, Apr 13, 2006 at 02:48:51AM +0200, Stefan Sperling wrote: > >=20 > >>On Wed, Apr 12, 2006 at 07:22:27PM -0400, Kris Kennaway wrote: > >> > >>>On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: > >>> > >>>> I tried out FreeBSD 6.0 (sorry, I copied just part or > >>>> uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - > >>>>Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") > >>> > >>>No you didn't, since no version of FreeBSD reports itself as LINUX > >>>from uname. > >> > >>Unless uname is a Linux binary. > >=20 > >=20 > > FreeBSD doesn't ship uname as a Linux binary either :-) > >=20 > > Kris > /compat/linux/bin/uname -a > Linux karma.internal 2.4.2 FreeBSD 6.1-PRERELEASE #0: Tue Apr 4 22:24:50= EST > 2006 i686 i686 i386 GNU/Linux Right, and that's not the FreeBSD uname, it's the redhat (or whatever) uname. Kris --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEPbFrWry0BWjoQKURAti2AJ41K3TXIe+7lUojPdFpSiXTImU0GACgq05z oqq+xXyhUiTU9JgFt62Nbr8= =UEuL -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 03:20:42 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F8CE16A402 for ; Thu, 13 Apr 2006 03:20:42 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id BA90B43D6E for ; Thu, 13 Apr 2006 03:20:36 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 32743 invoked by uid 1001); 13 Apr 2006 03:20:36 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Wed, 12 Apr 2006 23:20:35 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17469.50051.423199.471854@bhuda.mired.org> Date: Wed, 12 Apr 2006 23:20:35 -0400 To: Patrick Tracanelli In-Reply-To: <443DA28D.2040503@freebsdbrasil.com.br> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <20060412232226.GA33152@xor.obsecurity.org> <20060413004851.GA1194@dice.stsp.lan> <20060413005411.GA34686@xor.obsecurity.org> <443DA28D.2040503@freebsdbrasil.com.br> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org, Stefan Sperling , Kris Kennaway Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 03:20:42 -0000 In <443DA28D.2040503@freebsdbrasil.com.br>, Patrick Tracanelli typed: > Kris Kennaway wrote: > > On Thu, Apr 13, 2006 at 02:48:51AM +0200, Stefan Sperling wrote: > >>On Wed, Apr 12, 2006 at 07:22:27PM -0400, Kris Kennaway wrote: > >>>On Wed, Apr 12, 2006 at 10:48:44PM +0000, gs_stoller@juno.com wrote: > >>>> I tried out FreeBSD 6.0 (sorry, I copied just part or > >>>> uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - > >>>>Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") > >>> > >>>No you didn't, since no version of FreeBSD reports itself as LINUX > >>>from uname. > >>Unless uname is a Linux binary. > > FreeBSD doesn't ship uname as a Linux binary either :-) > Unless under Linux mode... Which would also explains the rest of the behavior the OP saw. He's getting bash instead of sh - because /bin/sh on Linux is bash. The two really odd behaviors - a list of files and a question about the number of possibilities - is bash file completion, which is triggered by the tab character. As for echo having standardized behavior, that's simply wishful thinking. SysV and BSD echo commands have different behaviors. POSIX is SysV. Various shells builtin echos have have flags and/or shell variables to control whether you get a variant of the SysV or BSD behavior, and different defaults. To get the behavior you want with the bash builtin echo, use: echo -e "a\tb" Better yet, consider using the printf command instead of echo. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 06:20:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8D9416A404 for ; Thu, 13 Apr 2006 06:20:53 +0000 (UTC) (envelope-from ghos@mail.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC5243D45 for ; Thu, 13 Apr 2006 06:20:53 +0000 (GMT) (envelope-from ghos@mail.ru) Received: from [193.125.69.18] (port=62757 helo=localhost) by mx27.mail.ru with asmtp id 1FTvCF-0004Dn-00; Thu, 13 Apr 2006 10:20:51 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.0.10250, virus records: 114846, updated: 12.03.2006] Date: Thu, 13 Apr 2006 10:20:44 +0400 From: Vyacheslav Anikin X-Mailer: The Bat! (v3.65.03) Professional X-Priority: 3 (Normal) Message-ID: <654019656.20060413102044@mail.ru> To: "gs_stoller@juno.com" In-Reply-To: <20060412.154921.26277.710543@webmail06.nyc.untd.com> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vyacheslav Anikin List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 06:20:53 -0000 =C7=E4=F0=E0=E2=F1=F2=E2=F3=E9=F2=E5, gs. =C2=FB =EF=E8=F1=E0=EB=E8 13 =E0=EF=F0=E5=EB=FF 2006 =E3., 2:48:44: gjc> I tried out FreeBSD 6.0 (sorry, I copied just part or gjc> uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - gjc> Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") gjc> and was surprised to find that things in the echo command didn't gjc> work. When I typed=20 gjc> echo "a\tb" gjc> I got a\tb , no tab replacing the "\t" Same for "\n". gjc> When I tried to type gjc> echo "b" gjc> where stands for hitting the tab key, when I hit the gjc> first time, nothing happened, when I hit it immediately afterward, I gjc> got an ls -A listing. I did manage to get a tab into the string [skipped] ok. If you want to print out you must to use sequence ^V^I. Where ^I is char. Or you may use -key instead of ^I. That there's the same. Or I something didn't understand? --=20 =D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC, Vyacheslav mailto:ghos@mail.ru From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 07:28:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F49116A407 for ; Thu, 13 Apr 2006 07:28:13 +0000 (UTC) (envelope-from ryanm@miranetworks.net) Received: from ctb-mesg9.saix.net (ctb-mesg9.saix.net [196.25.240.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id E716243D49 for ; Thu, 13 Apr 2006 07:28:12 +0000 (GMT) (envelope-from ryanm@miranetworks.net) Received: from crock.local (dsl-146-233-120.telkomadsl.co.za [165.146.233.120]) by ctb-mesg9.saix.net (Postfix) with ESMTP id D49E836B9; Thu, 13 Apr 2006 09:28:10 +0200 (SAST) Received: from beasti.localnet ([10.2.2.47] helo=beasti.synapp.com) by crock.local with esmtp (Exim 4.50) id 1FTwFO-0006rb-6u; Thu, 13 Apr 2006 09:28:10 +0200 Date: Thu, 13 Apr 2006 09:28:10 +0200 (SAST) From: Ryan Maclear X-X-Sender: ryanm@beasti.synapp.com To: "gs_stoller@juno.com" In-Reply-To: <654019656.20060413102044@mail.ru> Message-ID: <20060413092548.N10399@beasti.synapp.com> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <654019656.20060413102044@mail.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=windows-1251 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: freebsd-hackers@freebsd.org Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 07:28:13 -0000 Hi, I haven't really been following this thread, and I'm not sure if this has been posted here already. Appologies if this has been already. To usually get a to be echoed, you can use echo -e "a\tb" Cheers, Ryan On Thu, 13 Apr 2006, Vyacheslav Anikin wrote: > =C7=E4=F0=E0=E2=F1=F2=E2=F3=E9=F2=E5, gs. > > =C2=FB =EF=E8=F1=E0=EB=E8 13 =E0=EF=F0=E5=EB=FF 2006 =E3., 2:48:44: > > gjc> I tried out FreeBSD 6.0 (sorry, I copied just part or > gjc> uname -a and I got something like "LINUX 2.4.2 FreeBSD 6.0 - > gjc> Release #0: Nov 3 09:36:13 UTC 2005 i686 i686 i386 GNU/LINUX") > gjc> and was surprised to find that things in the echo command didn't > gjc> work. When I typed > gjc> echo "a\tb" > gjc> I got a\tb , no tab replacing the "\t" Same for "\n". > gjc> When I tried to type > gjc> echo "b" > gjc> where stands for hitting the tab key, when I hit t= he > gjc> first time, nothing happened, when I hit it immediately afterward, I > gjc> got an ls -A listing. I did manage to get a tab into the string > [skipped] > > ok. If you want to print out you must to use sequence ^V^I. > Where ^I is char. Or you may use -key instead of ^I. > That there's the same. Or I something didn't understand? > > -- > =D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC, > Vyacheslav mailto:ghos@mail.ru > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 07:51:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA5A616A401; Thu, 13 Apr 2006 07:51:50 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 593C943D45; Thu, 13 Apr 2006 07:51:47 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k3D7pkaA060915; Thu, 13 Apr 2006 01:51:46 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <443E030E.80708@samsco.org> Date: Thu, 13 Apr 2006 01:51:42 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: re@freebsd.org Subject: FreeBSD 6.1-RC1 Available X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 07:51:51 -0000 Announcement ------------ The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.1-RC1. It is meant to be a refinement of the 6-STABLE, branch with few dramatic changes. A lot of bugfixes have been made, some drivers have been updated, and some areas have been tweaked for better performance, etc. but no large changes have been made to the basic architecture. This RC is late in coming due to many more bugs being fixed, as well as a keyboard multiplexer being added. This is enabled by default via the 'kbdmux' driver and allows multiple keyboards of any type to be plugged in and work at once. In turn, the boot menu option to handle USB keyboards specially has been removed as it is no longer needed. This feature has been tested for several months, but more testing is always needed. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6_1. Problem reports can be submitted using the send-pr(1) command. The FreeBSD 5.5 release process is on hold while we put the final touches on 6.1. It will resume within 1-2 weeks with a 5.5-RC1 release. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.1R/todo.html Known Issues ------------ The NDIS driver is known to not work correctly with the wpa_supplicant package. This will be fixed for the release. A string termination problem can cause geom(8) commands to abort randomly. This will be fixed for the release. Availability ------------ The RC1 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (6.1-RC1-alpha-disc1.iso) = c9ce5255facfc44a30f34f55dd6ee2d6 MD5 (6.1-RC1-alpha-bootonly.iso) = 9277c6cd9c5dd17a9aeaa9394fe1d2f8 MD5 (6.1-RC1-amd64-bootonly.iso) = 93abe294e7678e00b7391f47a01074fe MD5 (6.1-RC1-amd64-disc1.iso) = c1b718b6752f0e48edb8b822ee9b0dc8 MD5 (6.1-RC1-amd64-disc2.iso) = 4a67ae8ed7a7852e08442205d6a5cd7c MD5 (6.1-RC1-i386-bootonly.iso) = b56aac9ca1a868daaf5673cd21bf78f5 MD5 (6.1-RC1-i386-disc1.iso) = 12521c3f9d40f637e4cdb40ea398d072 MD5 (6.1-RC1-i386-disc2.iso) = 53615f19889fe85c41e2bcea0b2be525 MD5 (6.1-RC1-ia64-bootonly.iso) = b2f284c8f6c28455ac59cb37ff2f6658 MD5 (6.1-RC1-ia64-disc1.iso) = e1385927a3272674512f8205aef0addc MD5 (6.1-RC1-ia64-disc2.iso) = 8b212b2f0914f13621996a8ad8397c71 MD5 (6.1-RC1-ia64-livefs.iso) = 75fdb240f273e7f9b2cdefcab43144c2 MD5 (6.1-RC1-pc98-disc1.iso) = 65465e3298efc5122607ea3d0b3e7136 SHA256 (6.1-RC1-alpha-disc1.iso) = d40b8e3e1944f28c5ba1b1f55eb7b5cc22472177116b98f85f2c5bb0ffb59a5f SHA256 (6.1-RC1-alpha-bootonly.iso) = 43ceaf712475d00b7287d09753635383cb284ad8fc63b98608e55ab458aed157 SHA256 (6.1-RC1-amd64-bootonly.iso) = 88e072b4898692813517aa254a33f1e7469de0e590c36bfb3e92cb120ac0ad16 SHA256 (6.1-RC1-amd64-disc1.iso) = 017e69c5461fe2c865a395830dde88c8a55e7ec83d9a195b3b619346b44f9cc6 SHA256 (6.1-RC1-amd64-disc2.iso) = 81624f3b8dfa67ceab1dc6ec0a94c4485ad85955321c39d13c9ab4a678f776ef SHA256 (6.1-RC1-i386-bootonly.iso) = ec1a3fbf53186b5bc44dbfcdc77872c847f3c55532bb62f2afb4133328e7994f SHA256 (6.1-RC1-i386-disc1.iso) = e0b83f2cbd27db20f330036d0a25b8366b9e45df4b9c09354f76e584a9eb3b83 SHA256 (6.1-RC1-i386-disc2.iso) = de1fe5009229efd44b25bb18c4e68b03027259171cd9e017fe5bffadaa3402bb SHA256 (6.1-RC1-ia64-bootonly.iso) = 2b7290e4babcb647ec8b2a499fc5e0fc6918ac20ee0432e9ce2d216c84a540fa SHA256 (6.1-RC1-ia64-disc1.iso) = 64c035cf52544e2088720d6e6e602f95b53f6d7b342431a1aa2f4b4c32438847 SHA256 (6.1-RC1-ia64-disc2.iso) = e4f2f0599e9e80edec10f30de565e34e16bd8716da6673834036ce4c66d32dc0 SHA256 (6.1-RC1-ia64-livefs.iso) = cac9b95ba01a69d78af0034d96868a7b93e20840f3ec0eacb7a30c7e7dd0b39a SHA256 (6.1-RC1-pc98-disc1.iso) = b797113a34628130f759dc9756b741230dcd064f4519f1a477b3491a02f346ca From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 14:21:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE85D16A400 for ; Thu, 13 Apr 2006 14:21:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDEF443D8F for ; Thu, 13 Apr 2006 14:21:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3DEL26j037332; Thu, 13 Apr 2006 10:21:02 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 13 Apr 2006 10:20:40 -0400 User-Agent: KMail/1.9.1 References: <20060412215021.GB1146@tols.org> In-Reply-To: <20060412215021.GB1146@tols.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604131020.42417.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1396/Thu Apr 13 01:39:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Marco van Tol Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 14:21:08 -0000 On Wednesday 12 April 2006 17:50, Marco van Tol wrote: > Hi there, > > My apologies if this is the wrong list to ask this kind of question. > I would appreciate a pointer to the correct list if it is please. :) > > I noticed in the code for gkrellm /usr/ports/sysutils/gkrellm2 that SMP > per-cpu statistics were not yet supported under FreeBSD, and decided to > check whether I could add that. (I'm running a (dual-core) Athlon64 X2 > with FreeBSD 6.1-PRERELEASE) > I can't find sample code and/or documentation on how to acquire that > information from the kernel. > > I checked > - gkrellm2 itself, which uses kern.cp_time in /src/sysdeps/freebsd.c > - top, which also uses kern.cp_time in /usr/src/usr.bin/top/machine.c > > Some browsing around the internet doesn't get me much further either > unfortunately. I keep hitting the per-cpu statistics mentioned with regard > to uma(9). > > Under linux this can be acquired via /proc/stat. (And gkrellm looks realy > funky with per-cpu stats, but that may or may not be relevant depending on > the reader of this mail I guess ;) > > Is there an interface under FreeBSD to acquire the necessary per-cpu > statistics? > > Thank you very much in advance, appreciated, > > Marco van Tol They don't exist currently. I have a patch to make the stats per-CPU for performance reasons (though it only helps out on systems with lots of CPUs (like 10) and hurts on systems with fewer CPUs (like 4)). It doesn't include a sysctl to get the per-CPU stats, but I could add one. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 17:48:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D928316A400 for ; Thu, 13 Apr 2006 17:48:00 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DC1E43D46 for ; Thu, 13 Apr 2006 17:48:00 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k3DHlpu6071996; Thu, 13 Apr 2006 12:47:51 -0500 (CDT) (envelope-from dan) Date: Thu, 13 Apr 2006 12:47:51 -0500 From: Dan Nelson To: Ryan Maclear Message-ID: <20060413174750.GC89228@dan.emsphone.com> References: <20060412.154921.26277.710543@webmail06.nyc.untd.com> <654019656.20060413102044@mail.ru> <20060413092548.N10399@beasti.synapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060413092548.N10399@beasti.synapp.com> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, "gs_stoller@juno.com" Subject: Re: Problems with FreeBSD 6.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 17:48:00 -0000 In the last episode (Apr 13), Ryan Maclear said: > I haven't really been following this thread, and I'm not sure if this > has been posted here already. Appologies if this has been already. > > To usually get a to be echoed, you can use > > echo -e "a\tb" The echo command doesn't take a -e option. Your shell's echo builtin may or may not, but for portability, you have to assume it doesn't. Use the printf command if you want fancy formatting. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 18:17:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AB5216A400 for ; Thu, 13 Apr 2006 18:17:42 +0000 (UTC) (envelope-from matthew@digitalstratum.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E7D043D48 for ; Thu, 13 Apr 2006 18:17:41 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from [10.0.81.12] (unknown [10.0.81.1]) by mail.mundomateo.com (Postfix) with ESMTP id 7BC6B2844D for ; Thu, 13 Apr 2006 14:17:40 -0400 (EDT) Message-ID: <443E95C1.4030404@digitalstratum.com> Date: Thu, 13 Apr 2006 14:17:37 -0400 From: Matthew Hagerty Organization: Digital Stratum User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@digitalstratum.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 18:17:42 -0000 Greetings, I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon Intel motherboard with a LSILogic MegaRAID (amr0) controller. This machine has been running for about 2 years now, and was very stable until I updated from 5.3 to 5.4, and now 6.0. The crashing seems to be totally random and I have had it crash in as little as 12 hours and as long as 143 days. When the box goes down it does so in a strange way. First, it still responds to network probes like ping (usually), however, all console access is ignored. Also, some network ports still respond, like a telnet to port 22 to test SSH will yield an SSH banner, but trying to connect with SSH just hangs. Sometimes this is also true of the SMTP server, but not always. This also makes it impossible for me to use CARP to swap to the recently purchased spare machine, since the network interface is generally still responding so CARP does not detect a problem. My biggest problem with this is that there are *never* any console messages or log entries in any logs, no warnings about disk failure, buffer exhaustion, system failures, etc.. The machine simply seems to stop responding and the only way to correct the problem is a hard reboot. A strange thing did happen yesterday though, I believe I caught the box on the verge of failure. I was SSH'd in and did a ps to check things out. There were about 100 of these entries: 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup (postgres) The box runs a web-based app and connects to a local Postgres DB which seemed to be unable to start new connections being requested by the PHP scripts. At any rate, I stopped Apache and then tried to stop Postgres which resulted in (or just happened to coincide with) the box locking up and no longer responding to my SSH commands or attempts to reconnect with SSH. I hardly think this is a Postgres problem, but even if it was, a userland app should *not* be able to bring down a box... Can anyone shed some light on this, give me some options to try? What happened to kernel panics and such when there were serious errors going on? The only glimmer of information I have is that *one* time there was an error on the console about there not being any RAID controller available. I did purchase a spare controller and I'm about to swap it out and see if it helps, but for some reason I doubt it. If a controller like that was failing, I would certainly hope to see some serious error messages or panics going on. I have been running FreeBSD since version 1.01 and have never had a box so unstable in the last 12 or so years, especially one that is supposed to be "server" quality instead of the make-shift ones I put together with desktop hardware. And last, I'm getting sick of my Linux admin friends telling me "told you so! should have run Linux...", please give me something to stick in their pie holes! Thanks, Matthew From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 18:38:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0CF916A400 for ; Thu, 13 Apr 2006 18:38:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F9DF43D45 for ; Thu, 13 Apr 2006 18:38:20 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3DIcFHq038809; Thu, 13 Apr 2006 14:38:15 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org, matthew@digitalstratum.com Date: Thu, 13 Apr 2006 14:36:16 -0400 User-Agent: KMail/1.9.1 References: <443E95C1.4030404@digitalstratum.com> In-Reply-To: <443E95C1.4030404@digitalstratum.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604131436.17942.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1396/Thu Apr 13 01:39:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 18:38:21 -0000 On Thursday 13 April 2006 14:17, Matthew Hagerty wrote: > Greetings, > > I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon Intel > motherboard with a LSILogic MegaRAID (amr0) controller. This machine > has been running for about 2 years now, and was very stable until I > updated from 5.3 to 5.4, and now 6.0. The crashing seems to be totally > random and I have had it crash in as little as 12 hours and as long as > 143 days. > > When the box goes down it does so in a strange way. First, it still > responds to network probes like ping (usually), however, all console > access is ignored. Also, some network ports still respond, like a > telnet to port 22 to test SSH will yield an SSH banner, but trying to > connect with SSH just hangs. Sometimes this is also true of the SMTP > server, but not always. This also makes it impossible for me to use > CARP to swap to the recently purchased spare machine, since the network > interface is generally still responding so CARP does not detect a problem. > > My biggest problem with this is that there are *never* any console > messages or log entries in any logs, no warnings about disk failure, > buffer exhaustion, system failures, etc.. The machine simply seems to > stop responding and the only way to correct the problem is a hard reboot. > > A strange thing did happen yesterday though, I believe I caught the box > on the verge of failure. I was SSH'd in and did a ps to check things > out. There were about 100 of these entries: > > 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup (postgres) > > The box runs a web-based app and connects to a local Postgres DB which > seemed to be unable to start new connections being requested by the PHP > scripts. At any rate, I stopped Apache and then tried to stop Postgres > which resulted in (or just happened to coincide with) the box locking up > and no longer responding to my SSH commands or attempts to reconnect > with SSH. I hardly think this is a Postgres problem, but even if it > was, a userland app should *not* be able to bring down a box... > > Can anyone shed some light on this, give me some options to try? What > happened to kernel panics and such when there were serious errors going > on? The only glimmer of information I have is that *one* time there was > an error on the console about there not being any RAID controller > available. I did purchase a spare controller and I'm about to swap it > out and see if it helps, but for some reason I doubt it. If a > controller like that was failing, I would certainly hope to see some > serious error messages or panics going on. > > I have been running FreeBSD since version 1.01 and have never had a box > so unstable in the last 12 or so years, especially one that is supposed > to be "server" quality instead of the make-shift ones I put together > with desktop hardware. And last, I'm getting sick of my Linux admin > friends telling me "told you so! should have run Linux...", please give > me something to stick in their pie holes! It sounds like a livelock (or deadlock) more than a crash. Can you add 'DDB' in your kernel config and break into the debugger when it hangs and grab the output of 'ps'? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 18:45:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA51F16A404 for ; Thu, 13 Apr 2006 18:45:18 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13CCA43D48 for ; Thu, 13 Apr 2006 18:45:17 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.143] (helo=anti-virus02-10) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1FU6od-0001aE-V8; Thu, 13 Apr 2006 19:45:15 +0100 Received: from [80.192.25.195] (helo=[192.168.0.2]) by asmtp-out3.blueyonder.co.uk with esmtp (Exim 4.52) id 1FU6oa-0007SQ-Vy; Thu, 13 Apr 2006 19:45:13 +0100 Message-ID: <443E9C38.709@dial.pipex.com> Date: Thu, 13 Apr 2006 19:45:12 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: matthew@digitalstratum.com References: <443E95C1.4030404@digitalstratum.com> In-Reply-To: <443E95C1.4030404@digitalstratum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 18:45:18 -0000 Matthew Hagerty wrote: > Can anyone shed some light on this, give me some options to try? What > happened to kernel panics and such when there were serious errors > going on? The only glimmer of information I have is that *one* time > there was an error on the console about there not being any RAID > controller available. I did purchase a spare controller and I'm about > to swap it out and see if it helps, but for some reason I doubt it. > If a controller like that was failing, I would certainly hope to see > some serious error messages or panics going on. > > I have been running FreeBSD since version 1.01 and have never had a > box so unstable in the last 12 or so years, especially one that is > supposed to be "server" quality instead of the make-shift ones I put > together with desktop hardware. And last, I'm getting sick of my > Linux admin friends telling me "told you so! should have run > Linux...", please give me something to stick in their pie holes! Several times now I have had Linux servers (and production quality ones, not built by me ones :-)) die in a somewhat similar fashion. In every case the cause has been either a flaky disk or a flaky disk controller, or some combination. What seems to happen is that the disk is entirely "lost" by the OS. At that point any process which never accesses the disk (i.e. is already in memory) is able to run but the moment any process tries to access the disk it locks up. So you can't ssh in to the server, but if you happen to be logged in, you shell is probably cached and keeps working. If you typed ls recently, you can run ls (but see nothing or get a cryptic error message like I/O Error), for example. Clearly nothing is logged as the disk has gone AWOL. Often the machines behaved fine after a reboot and then did the same some time later. In one case, the supposedly transparent "RAID-1" array was completely broken, but Linux logged precisely nothing to tell you :-( You can stick that where you like in your Linux friends :-O This somewhat fits with your symptoms. If the disk vanished, then all those postgres processes would probably fail unless everything they needed happened to be cached in RAM. The Web server and PHP scripts probably are cached in RAM if they are called frequently so you might well see lots of postgres processes stacked up. LSI MegaRAID has a CLI of sorts in sysutils/megarc. You might start with that (and check the RAID BIOS next time the machine reboots). I'd say that if you have an alternative RAID controller that would be a good place to start. If LSI do any stndalone diagnostics, you could try those. --Alex PS Kernel's usually panic when some internal state is just too wrong to continue. A disk or even a controller disappearing isn't going to make the internal state wrong - it's just a device gone missing - so I would not be surprised if the machine just locked up. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 19:06:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F040B16A402; Thu, 13 Apr 2006 19:05:59 +0000 (UTC) (envelope-from matthew@digitalstratum.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 942D743D45; Thu, 13 Apr 2006 19:05:59 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from [10.0.81.12] (unknown [10.0.81.1]) by mail.mundomateo.com (Postfix) with ESMTP id A173A2844D; Thu, 13 Apr 2006 15:05:58 -0400 (EDT) Message-ID: <443EA113.10205@digitalstratum.com> Date: Thu, 13 Apr 2006 15:05:55 -0400 From: Matthew Hagerty Organization: Digital Stratum User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: John Baldwin References: <443E95C1.4030404@digitalstratum.com> <200604131436.17942.jhb@freebsd.org> In-Reply-To: <200604131436.17942.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@digitalstratum.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 19:06:00 -0000 John Baldwin wrote: > On Thursday 13 April 2006 14:17, Matthew Hagerty wrote: > >> Greetings, >> >> I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon Intel >> motherboard with a LSILogic MegaRAID (amr0) controller. This machine >> has been running for about 2 years now, and was very stable until I >> updated from 5.3 to 5.4, and now 6.0. The crashing seems to be totally >> random and I have had it crash in as little as 12 hours and as long as >> 143 days. >> >> When the box goes down it does so in a strange way. First, it still >> responds to network probes like ping (usually), however, all console >> access is ignored. Also, some network ports still respond, like a >> telnet to port 22 to test SSH will yield an SSH banner, but trying to >> connect with SSH just hangs. Sometimes this is also true of the SMTP >> server, but not always. This also makes it impossible for me to use >> CARP to swap to the recently purchased spare machine, since the network >> interface is generally still responding so CARP does not detect a problem. >> >> My biggest problem with this is that there are *never* any console >> messages or log entries in any logs, no warnings about disk failure, >> buffer exhaustion, system failures, etc.. The machine simply seems to >> stop responding and the only way to correct the problem is a hard reboot. >> >> A strange thing did happen yesterday though, I believe I caught the box >> on the verge of failure. I was SSH'd in and did a ps to check things >> out. There were about 100 of these entries: >> >> 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup (postgres) >> >> The box runs a web-based app and connects to a local Postgres DB which >> seemed to be unable to start new connections being requested by the PHP >> scripts. At any rate, I stopped Apache and then tried to stop Postgres >> which resulted in (or just happened to coincide with) the box locking up >> and no longer responding to my SSH commands or attempts to reconnect >> with SSH. I hardly think this is a Postgres problem, but even if it >> was, a userland app should *not* be able to bring down a box... >> >> Can anyone shed some light on this, give me some options to try? What >> happened to kernel panics and such when there were serious errors going >> on? The only glimmer of information I have is that *one* time there was >> an error on the console about there not being any RAID controller >> available. I did purchase a spare controller and I'm about to swap it >> out and see if it helps, but for some reason I doubt it. If a >> controller like that was failing, I would certainly hope to see some >> serious error messages or panics going on. >> >> I have been running FreeBSD since version 1.01 and have never had a box >> so unstable in the last 12 or so years, especially one that is supposed >> to be "server" quality instead of the make-shift ones I put together >> with desktop hardware. And last, I'm getting sick of my Linux admin >> friends telling me "told you so! should have run Linux...", please give >> me something to stick in their pie holes! >> > > It sounds like a livelock (or deadlock) more than a crash. Can you add > 'DDB' in your kernel config and break into the debugger when it hangs > and grab the output of 'ps'? > > I can probably figure out how to compile in DDB (I've never done if before though), but just two questions: 1. How do I break into DDB and grab the ps output? 2. How can I login if the box is not responding to SSH or the console? It was only by sheer luck that I caught it yesterday just before the lockup, I have never been able to do that before. Thanks, Matthew From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 19:14:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C74916A400 for ; Thu, 13 Apr 2006 19:14:55 +0000 (UTC) (envelope-from matthew@digitalstratum.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2A1243D45 for ; Thu, 13 Apr 2006 19:14:54 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from [10.0.81.12] (unknown [10.0.81.1]) by mail.mundomateo.com (Postfix) with ESMTP id 56EB62844D; Thu, 13 Apr 2006 15:14:54 -0400 (EDT) Message-ID: <443EA32B.408@digitalstratum.com> Date: Thu, 13 Apr 2006 15:14:51 -0400 From: Matthew Hagerty Organization: Digital Stratum User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Alex Zbyslaw References: <443E95C1.4030404@digitalstratum.com> <443E9C38.709@dial.pipex.com> In-Reply-To: <443E9C38.709@dial.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@digitalstratum.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 19:14:55 -0000 Alex Zbyslaw wrote: > Matthew Hagerty wrote: > >> Can anyone shed some light on this, give me some options to try? >> What happened to kernel panics and such when there were serious >> errors going on? The only glimmer of information I have is that >> *one* time there was an error on the console about there not being >> any RAID controller available. I did purchase a spare controller and >> I'm about to swap it out and see if it helps, but for some reason I >> doubt it. If a controller like that was failing, I would certainly >> hope to see some serious error messages or panics going on. >> >> I have been running FreeBSD since version 1.01 and have never had a >> box so unstable in the last 12 or so years, especially one that is >> supposed to be "server" quality instead of the make-shift ones I put >> together with desktop hardware. And last, I'm getting sick of my >> Linux admin friends telling me "told you so! should have run >> Linux...", please give me something to stick in their pie holes! > > Several times now I have had Linux servers (and production quality > ones, not built by me ones :-)) die in a somewhat similar fashion. In > every case the cause has been either a flaky disk or a flaky disk > controller, or some combination. > > What seems to happen is that the disk is entirely "lost" by the OS. > At that point any process which never accesses the disk (i.e. is > already in memory) is able to run but the moment any process tries to > access the disk it locks up. So you can't ssh in to the server, but > if you happen to be logged in, you shell is probably cached and keeps > working. If you typed ls recently, you can run ls (but see nothing or > get a cryptic error message like I/O Error), for example. > > Clearly nothing is logged as the disk has gone AWOL. Often the > machines behaved fine after a reboot and then did the same some time > later. In one case, the supposedly transparent "RAID-1" array was > completely broken, but Linux logged precisely nothing to tell you :-( > You can stick that where you like in your Linux friends :-O > > This somewhat fits with your symptoms. If the disk vanished, then all > those postgres processes would probably fail unless everything they > needed happened to be cached in RAM. The Web server and PHP scripts > probably are cached in RAM if they are called frequently so you might > well see lots of postgres processes stacked up. > > LSI MegaRAID has a CLI of sorts in sysutils/megarc. You might start > with that (and check the RAID BIOS next time the machine reboots). > > I'd say that if you have an alternative RAID controller that would be > a good place to start. If LSI do any stndalone diagnostics, you could > try those. > > --Alex > > PS Kernel's usually panic when some internal state is just too wrong > to continue. A disk or even a controller disappearing isn't going to > make the internal state wrong - it's just a device gone missing - so I > would not be surprised if the machine just locked up. > Hmm, that just seems odd that a disk controller just vanishing would not cause some sort of console message? Even if the disk device is gone, /dev/console should still be intact to display an error, no? Also, a disk device that is all of a sudden missing seems pretty serious to me, since a disk is one of the main devices that modern OSes cannot run without (generally speaking.) I would think *some* console message should be warranted. I'll see if there are any diag programs for the controller and I'll go ahead and swap the controller out. I wonder if the RAID configuration in stored in the controller or on the disks? I'd hate to have to rebuild the server install... Thanks for the info. Matthew From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 19:15:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81CEE16A400; Thu, 13 Apr 2006 19:15:41 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB5F243D5A; Thu, 13 Apr 2006 19:15:39 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.19.131]) ([10.251.19.131]) by a50.ironport.com with ESMTP; 13 Apr 2006 12:15:40 -0700 Message-ID: <443EA35B.4030909@elischer.org> Date: Thu, 13 Apr 2006 12:15:39 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: matthew@digitalstratum.com References: <443E95C1.4030404@digitalstratum.com> <200604131436.17942.jhb@freebsd.org> <443EA113.10205@digitalstratum.com> In-Reply-To: <443EA113.10205@digitalstratum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 19:15:41 -0000 Matthew Hagerty wrote: > John Baldwin wrote: > >> On Thursday 13 April 2006 14:17, Matthew Hagerty wrote: >> >> >>> Greetings, >>> >>> I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon >>> Intel motherboard with a LSILogic MegaRAID (amr0) controller. This >>> machine has been running for about 2 years now, and was very stable >>> until I updated from 5.3 to 5.4, and now 6.0. The crashing seems to >>> be totally random and I have had it crash in as little as 12 hours >>> and as long as 143 days. >>> >>> When the box goes down it does so in a strange way. First, it still >>> responds to network probes like ping (usually), however, all console >>> access is ignored. Also, some network ports still respond, like a >>> telnet to port 22 to test SSH will yield an SSH banner, but trying >>> to connect with SSH just hangs. Sometimes this is also true of the >>> SMTP server, but not always. This also makes it impossible for me >>> to use CARP to swap to the recently purchased spare machine, since >>> the network interface is generally still responding so CARP does not >>> detect a problem. >>> >>> My biggest problem with this is that there are *never* any console >>> messages or log entries in any logs, no warnings about disk failure, >>> buffer exhaustion, system failures, etc.. The machine simply seems >>> to stop responding and the only way to correct the problem is a hard >>> reboot. >>> >>> A strange thing did happen yesterday though, I believe I caught the >>> box on the verge of failure. I was SSH'd in and did a ps to check >>> things out. There were about 100 of these entries: >>> >>> 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup >>> (postgres) >>> >>> The box runs a web-based app and connects to a local Postgres DB >>> which seemed to be unable to start new connections being requested >>> by the PHP scripts. At any rate, I stopped Apache and then tried to >>> stop Postgres which resulted in (or just happened to coincide with) >>> the box locking up and no longer responding to my SSH commands or >>> attempts to reconnect with SSH. I hardly think this is a Postgres >>> problem, but even if it was, a userland app should *not* be able to >>> bring down a box... >>> >>> Can anyone shed some light on this, give me some options to try? >>> What happened to kernel panics and such when there were serious >>> errors going on? The only glimmer of information I have is that >>> *one* time there was an error on the console about there not being >>> any RAID controller available. I did purchase a spare controller >>> and I'm about to swap it out and see if it helps, but for some >>> reason I doubt it. If a controller like that was failing, I would >>> certainly hope to see some serious error messages or panics going on. >>> >>> I have been running FreeBSD since version 1.01 and have never had a >>> box so unstable in the last 12 or so years, especially one that is >>> supposed to be "server" quality instead of the make-shift ones I put >>> together with desktop hardware. And last, I'm getting sick of my >>> Linux admin friends telling me "told you so! should have run >>> Linux...", please give me something to stick in their pie holes! >>> >> >> >> It sounds like a livelock (or deadlock) more than a crash. Can you add >> 'DDB' in your kernel config and break into the debugger when it hangs >> and grab the output of 'ps'? >> >> > > I can probably figure out how to compile in DDB (I've never done if > before though), but just two questions: add options DDB to your kenrnel config file. > > 1. How do I break into DDB and grab the ps output? on the console, hit keys (at once) that should put you into the debugger.. then 'ps' will give you some output. It's a lot to write down but I've found a camera phone makes good enough snapshots :-) alternatively you can use a serial console, but getting into the debugger is harder, you have to have compiled in ALT_BREAK_TO_DEBUGGER into your kernel by adding # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. options ALT_BREAK_TO_DEBUGGER to the kernel config file you are using.. at the boot prompt (where the 10 second delay is) type set console="comconsole" (from memory) to make the serial port the console. then you can do console stuff from another window/machine and capture the outout easily. > > 2. How can I login if the box is not responding to SSH or the > console? It was only by sheer luck that I caught it yesterday just > before the lockup, I have never been able to do that before. > > Thanks, > Matthew > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 19:34:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF7F416A403 for ; Thu, 13 Apr 2006 19:34:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C47343D48 for ; Thu, 13 Apr 2006 19:34:13 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3DJY572039145; Thu, 13 Apr 2006 15:34:05 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Julian Elischer Date: Thu, 13 Apr 2006 15:33:41 -0400 User-Agent: KMail/1.9.1 References: <443E95C1.4030404@digitalstratum.com> <443EA113.10205@digitalstratum.com> <443EA35B.4030909@elischer.org> In-Reply-To: <443EA35B.4030909@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604131533.44115.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1396/Thu Apr 13 01:39:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: matthew@digitalstratum.com, freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 19:34:14 -0000 On Thursday 13 April 2006 15:15, Julian Elischer wrote: > Matthew Hagerty wrote: > > > John Baldwin wrote: > > > >> On Thursday 13 April 2006 14:17, Matthew Hagerty wrote: > >> > >> > >>> Greetings, > >>> > >>> I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon > >>> Intel motherboard with a LSILogic MegaRAID (amr0) controller. This > >>> machine has been running for about 2 years now, and was very stable > >>> until I updated from 5.3 to 5.4, and now 6.0. The crashing seems to > >>> be totally random and I have had it crash in as little as 12 hours > >>> and as long as 143 days. > >>> > >>> When the box goes down it does so in a strange way. First, it still > >>> responds to network probes like ping (usually), however, all console > >>> access is ignored. Also, some network ports still respond, like a > >>> telnet to port 22 to test SSH will yield an SSH banner, but trying > >>> to connect with SSH just hangs. Sometimes this is also true of the > >>> SMTP server, but not always. This also makes it impossible for me > >>> to use CARP to swap to the recently purchased spare machine, since > >>> the network interface is generally still responding so CARP does not > >>> detect a problem. > >>> > >>> My biggest problem with this is that there are *never* any console > >>> messages or log entries in any logs, no warnings about disk failure, > >>> buffer exhaustion, system failures, etc.. The machine simply seems > >>> to stop responding and the only way to correct the problem is a hard > >>> reboot. > >>> > >>> A strange thing did happen yesterday though, I believe I caught the > >>> box on the verge of failure. I was SSH'd in and did a ps to check > >>> things out. There were about 100 of these entries: > >>> > >>> 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup > >>> (postgres) > >>> > >>> The box runs a web-based app and connects to a local Postgres DB > >>> which seemed to be unable to start new connections being requested > >>> by the PHP scripts. At any rate, I stopped Apache and then tried to > >>> stop Postgres which resulted in (or just happened to coincide with) > >>> the box locking up and no longer responding to my SSH commands or > >>> attempts to reconnect with SSH. I hardly think this is a Postgres > >>> problem, but even if it was, a userland app should *not* be able to > >>> bring down a box... > >>> > >>> Can anyone shed some light on this, give me some options to try? > >>> What happened to kernel panics and such when there were serious > >>> errors going on? The only glimmer of information I have is that > >>> *one* time there was an error on the console about there not being > >>> any RAID controller available. I did purchase a spare controller > >>> and I'm about to swap it out and see if it helps, but for some > >>> reason I doubt it. If a controller like that was failing, I would > >>> certainly hope to see some serious error messages or panics going on. > >>> > >>> I have been running FreeBSD since version 1.01 and have never had a > >>> box so unstable in the last 12 or so years, especially one that is > >>> supposed to be "server" quality instead of the make-shift ones I put > >>> together with desktop hardware. And last, I'm getting sick of my > >>> Linux admin friends telling me "told you so! should have run > >>> Linux...", please give me something to stick in their pie holes! > >>> > >> > >> > >> It sounds like a livelock (or deadlock) more than a crash. Can you add > >> 'DDB' in your kernel config and break into the debugger when it hangs > >> and grab the output of 'ps'? > >> > >> > > > > I can probably figure out how to compile in DDB (I've never done if > > before though), but just two questions: > > > add > options DDB > to your kenrnel config file. > > > > > 1. How do I break into DDB and grab the ps output? > > on the console, hit keys (at once) > > that should put you into the debugger.. > > then 'ps' will give you some output. > > It's a lot to write down but I've found a camera phone makes good enough > snapshots :-) > > alternatively you can use a serial console, but getting into the > debugger is harder, > you have to have compiled in ALT_BREAK_TO_DEBUGGER > into your kernel by adding > > # Solaris implements a new BREAK which is initiated by a character > # sequence CR ~ ^b which is similar to a familiar pattern used on > # Sun servers by the Remote Console. > options ALT_BREAK_TO_DEBUGGER > > to the kernel config file you are using.. Or jsut use 'options BREAK_TO_DEBUGGER' and send a serial break signal to break into the debugger. Matthew, There's also a chapter in the handbook that explains how to use ddb, setup a serial console, etc. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 20:08:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4CE016A407 for ; Thu, 13 Apr 2006 20:08:37 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3FD43D4C for ; Thu, 13 Apr 2006 20:08:35 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.142] (helo=anti-virus02-09) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1FU87G-0006vE-AC; Thu, 13 Apr 2006 21:08:34 +0100 Received: from [80.192.25.195] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1FU87F-0003dJ-HO; Thu, 13 Apr 2006 21:08:33 +0100 Message-ID: <443EAFC0.6040308@dial.pipex.com> Date: Thu, 13 Apr 2006 21:08:32 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: matthew@digitalstratum.com References: <443E95C1.4030404@digitalstratum.com> <443E9C38.709@dial.pipex.com> <443EA32B.408@digitalstratum.com> In-Reply-To: <443EA32B.408@digitalstratum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 20:08:38 -0000 Matthew Hagerty wrote: > Alex Zbyslaw wrote: > >> Matthew Hagerty wrote: >> >>> Can anyone shed some light on this, give me some options to try? >>> What happened to kernel panics and such when there were serious >>> errors going on? The only glimmer of information I have is that >>> *one* time there was an error on the console about there not being >>> any RAID controller available. I did purchase a spare controller >>> and I'm about to swap it out and see if it helps, but for some >>> reason I doubt it. If a controller like that was failing, I would >>> certainly hope to see some serious error messages or panics going on. >>> >>> I have been running FreeBSD since version 1.01 and have never had a >>> box so unstable in the last 12 or so years, especially one that is >>> supposed to be "server" quality instead of the make-shift ones I put >>> together with desktop hardware. And last, I'm getting sick of my >>> Linux admin friends telling me "told you so! should have run >>> Linux...", please give me something to stick in their pie holes! >> >> >> Several times now I have had Linux servers (and production quality >> ones, not built by me ones :-)) die in a somewhat similar fashion. >> In every case the cause has been either a flaky disk or a flaky disk >> controller, or some combination. >> >> What seems to happen is that the disk is entirely "lost" by the OS. >> At that point any process which never accesses the disk (i.e. is >> already in memory) is able to run but the moment any process tries to >> access the disk it locks up. So you can't ssh in to the server, but >> if you happen to be logged in, you shell is probably cached and keeps >> working. If you typed ls recently, you can run ls (but see nothing >> or get a cryptic error message like I/O Error), for example. > > > Hmm, that just seems odd that a disk controller just vanishing would > not cause some sort of console message? Even if the disk device is > gone, /dev/console should still be intact to display an error, no? > Also, a disk device that is all of a sudden missing seems pretty > serious to me, since a disk is one of the main devices that modern > OSes cannot run without (generally speaking.) I would think *some* > console message should be warranted. Not if syslogd tries to access the disk :-( All can say is that I have seen three Linux boxes go this way; I've never had this kind of failure on a BSD box (touch wood) so all I can do is speculate about the similarities. Also, you did get a console message once, didn't you? > > I'll see if there are any diag programs for the controller and I'll go > ahead and swap the controller out. I wonder if the RAID configuration > in stored in the controller or on the disks? I'd hate to have to > rebuild the server install... I believe both and the RAID controller will compare what it thinks it should see with what it sees on the disks. If you are moving to a new, identical controller I would have thought that the worst you would have to do is to reconfigure it to accept the disks you give it as your specified configuration without it trying to rebuild anything. hth, --Alex From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 21:11:45 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8457816A402 for ; Thu, 13 Apr 2006 21:11:45 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E87243D49 for ; Thu, 13 Apr 2006 21:11:42 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 2263B275CD for ; Thu, 13 Apr 2006 23:11:41 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id C140A9B847 for ; Thu, 13 Apr 2006 21:12:24 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 9F7A6405B; Thu, 13 Apr 2006 23:12:24 +0200 (CEST) Date: Thu, 13 Apr 2006 23:12:24 +0200 From: Jeremie Le Hen To: freebsd-hackers@FreeBSD.org Message-ID: <20060413211224.GO71412@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: linker mysteries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 21:11:45 -0000 Hi list, (I got no answer on freebsd-questions@, thus I give a try here.) I was doing some testing on shared dependencies and fiddling libfetch's Makefile for this aim. I set LDFLAGS to "-v" in order to see the command executed for th linking. In the standard Makefile, we have this : % .if !defined(NO_CRYPT) && !defined(NO_OPENSSL) % CFLAGS+= -DWITH_SSL % DPADD= ${LIBSSL} ${LIBCRYPTO} % LDADD= -lssl -lcrypto % .endif And the resulting linker command is : % /usr/bin/ld -V -Bshareable -o libfetch.so.4 /usr/lib/crti.o /usr/lib/crtbeginS.o -L/usr/lib -x -soname libfetch.so.4 file.So http.So ftp.So common.So fetch.So -lssl -lcrypto -lgcc_pic -lgcc_pic /usr/lib/crtendS.o /usr/lib/crtn.o Dependencies are normal : % jarjarbinks# cd /usr/obj/usr/src/lib/libfetch % jarjarbinks# ldd libfetch.so % libfetch.so: % libssl.so.4 => /usr/lib/libssl.so.4 (0x3277d000) % libcrypto.so.4 => /lib/libcrypto.so.4 (0x3215f000) If I comment out the variable assignements : % .if !defined(NO_CRYPT) && !defined(NO_OPENSSL) % #CFLAGS+= -DWITH_SSL % #DPADD= ${LIBSSL} ${LIBCRYPTO} % #LDADD= -lssl -lcrypto % .endif The resulting linker command is now : % /usr/bin/ld -V -Bshareable -o libfetch.so.4 /usr/lib/crti.o /usr/lib/crtbeginS.o -L/usr/lib -x -soname libfetch.so.4 file.So http.So ftp.So common.So fetch.So -lgcc_pic -lgcc_pic /usr/lib/crtendS.o /usr/lib/crtn.o As you can see, we don't have "-lssl -lcrypto" any more. However, ldd(1) still says that libfetch.so is linked against those libraries : % jarjarbinks# ldd libfetch.so % libfetch.so: % libssl.so.4 => /usr/lib/libssl.so.4 (0x2c72e000) % libcrypto.so.4 => /lib/libcrypto.so.4 (0x2cd74000) Only linking addresses change, but they do at every compilation. I would be glad if someone could explain why this happens. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 22:22:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5038E16A402 for ; Thu, 13 Apr 2006 22:22:39 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 788FC43D55 for ; Thu, 13 Apr 2006 22:22:37 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd4mr2so.prod.shaw.ca (pd4mr2so-qfe3.prod.shaw.ca [10.0.141.213]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXO00H9DM4KT500@l-daemon> for freebsd-hackers@freebsd.org; Thu, 13 Apr 2006 16:21:56 -0600 (MDT) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd4mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXO00DBYM4KUX40@pd4mr2so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Thu, 13 Apr 2006 16:21:56 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXO003SBM4KE210@l-daemon> for freebsd-hackers@freebsd.org; Thu, 13 Apr 2006 16:21:56 -0600 (MDT) Date: Thu, 13 Apr 2006 15:21:54 -0700 From: soralx@cydem.org In-reply-to: <443EAFC0.6040308@dial.pipex.com> To: freebsd-hackers@freebsd.org Message-id: <200604131521.55405.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <443E95C1.4030404@digitalstratum.com> <443EA32B.408@digitalstratum.com> <443EAFC0.6040308@dial.pipex.com> User-Agent: KMail/1.9.1 Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 22:22:39 -0000 > > Hmm, that just seems odd that a disk controller just vanishing would > > not cause some sort of console message? Even if the disk device is > > gone, /dev/console should still be intact to display an error, no? > > Also, a disk device that is all of a sudden missing seems pretty > > serious to me, since a disk is one of the main devices that modern > > OSes cannot run without (generally speaking.) I would think *some* > > console message should be warranted. > > Not if syslogd tries to access the disk :-( All can say is that I have > seen three Linux boxes go this way; I've never had this kind of failure > on a BSD box (touch wood) so all I can do is speculate about the I have. I've got a Seagate X15k SCSI HDD with SCA2->68pin adapter, and sometimes it used to lose power and shut off (bad contact in the adapter perhaps). FreeBSD would spit SCSI diagnostic messages onto the console about failed field-replacable unit (which I couldn't see in X Windows), restart the HDD a few times (at this point the machine would hang until HDD is restarted), and then reboot (panic?). Timestamp: 0x443EC707 [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 00:01:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C49E016A402 for ; Fri, 14 Apr 2006 00:01:22 +0000 (UTC) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8995443D46 for ; Fri, 14 Apr 2006 00:01:22 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.88] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id 645A41A3C19; Thu, 13 Apr 2006 17:01:22 -0700 (PDT) Message-ID: <443EE652.1020806@freebsd.org> Date: Thu, 13 Apr 2006 17:01:22 -0700 From: Paul Saab User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: matthew@digitalstratum.com References: <443E95C1.4030404@digitalstratum.com> In-Reply-To: <443E95C1.4030404@digitalstratum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 00:01:22 -0000 There are serious race conditions with amr in 6.0 that can cause serious hangs. I suggest you take the amr driver from RELENG_6 and try that. Matthew Hagerty wrote: > Greetings, > > I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon Intel > motherboard with a LSILogic MegaRAID (amr0) controller. This machine > has been running for about 2 years now, and was very stable until I > updated from 5.3 to 5.4, and now 6.0. The crashing seems to be > totally random and I have had it crash in as little as 12 hours and as > long as 143 days. > > When the box goes down it does so in a strange way. First, it still > responds to network probes like ping (usually), however, all console > access is ignored. Also, some network ports still respond, like a > telnet to port 22 to test SSH will yield an SSH banner, but trying to > connect with SSH just hangs. Sometimes this is also true of the SMTP > server, but not always. This also makes it impossible for me to use > CARP to swap to the recently purchased spare machine, since the > network interface is generally still responding so CARP does not > detect a problem. > > My biggest problem with this is that there are *never* any console > messages or log entries in any logs, no warnings about disk failure, > buffer exhaustion, system failures, etc.. The machine simply seems to > stop responding and the only way to correct the problem is a hard reboot. > > A strange thing did happen yesterday though, I believe I caught the > box on the verge of failure. I was SSH'd in and did a ps to check > things out. There were about 100 of these entries: > > 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup > (postgres) > > The box runs a web-based app and connects to a local Postgres DB which > seemed to be unable to start new connections being requested by the > PHP scripts. At any rate, I stopped Apache and then tried to stop > Postgres which resulted in (or just happened to coincide with) the box > locking up and no longer responding to my SSH commands or attempts to > reconnect with SSH. I hardly think this is a Postgres problem, but > even if it was, a userland app should *not* be able to bring down a > box... > > Can anyone shed some light on this, give me some options to try? What > happened to kernel panics and such when there were serious errors > going on? The only glimmer of information I have is that *one* time > there was an error on the console about there not being any RAID > controller available. I did purchase a spare controller and I'm about > to swap it out and see if it helps, but for some reason I doubt it. > If a controller like that was failing, I would certainly hope to see > some serious error messages or panics going on. > > I have been running FreeBSD since version 1.01 and have never had a > box so unstable in the last 12 or so years, especially one that is > supposed to be "server" quality instead of the make-shift ones I put > together with desktop hardware. And last, I'm getting sick of my > Linux admin friends telling me "told you so! should have run > Linux...", please give me something to stick in their pie holes! > > Thanks, > Matthew > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 01:09:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3F3E16A401 for ; Fri, 14 Apr 2006 01:09:41 +0000 (UTC) (envelope-from andymac@bullseye.apana.org.au) Received: from mail.acis.com.au (atlantis.acis.com.au [203.14.230.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 11BCA43D45 for ; Fri, 14 Apr 2006 01:09:40 +0000 (GMT) (envelope-from andymac@bullseye.apana.org.au) Received: (qmail 37233 invoked from network); 14 Apr 2006 01:09:37 -0000 Received: from unknown (HELO bullseye.apana.org.au) (202.6.34.1) by atlantis.acis.com.au with SMTP; 14 Apr 2006 01:09:37 -0000 Received: from [203.9.107.238] (tenring.andymac.org [203.9.107.238]) by bullseye.apana.org.au (8.12.8p1/8.12.8) with ESMTP id k3E0vLPM025276 for ; Fri, 14 Apr 2006 10:57:21 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Message-ID: <443EE34A.2050906@bullseye.apana.org.au> Date: Fri, 14 Apr 2006 10:48:26 +1100 From: Andrew MacIntyre User-Agent: Thunderbird 1.5 (OS/2/20060113) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <443E95C1.4030404@digitalstratum.com> <443E9C38.709@dial.pipex.com> In-Reply-To: <443E9C38.709@dial.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 01:09:42 -0000 Alex Zbyslaw wrote: {...} > Several times now I have had Linux servers (and production quality ones, > not built by me ones :-)) die in a somewhat similar fashion. In every > case the cause has been either a flaky disk or a flaky disk controller, > or some combination. I've seen an instance of somewhat similar symptoms where a power supply was sagging out of spec on one supply rail some time after startup. When some disk activity happened, the extra power consumption caused the voltage to sag further triggering the disk going AWOL. At the time this started to happen, the power supply was more than 12 months old. ------------------------------------------------------------------------- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 03:08:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B21A16A402; Fri, 14 Apr 2006 03:08:55 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id B767C43D49; Fri, 14 Apr 2006 03:08:54 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.181.251] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1FUEg118oL-0002Ct; Fri, 14 Apr 2006 05:08:53 +0200 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Fri, 14 Apr 2006 05:06:49 +0200 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_LHxPEfzmILCscGB" Message-Id: <200604140506.51334.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report First Quarter 2006 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 03:08:56 -0000 --Boundary-00=_LHxPEfzmILCscGB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_LHxPEfzmILCscGB Content-Type: text/plain; charset="us-ascii"; name="report-jan-2006-mar-2006.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="report-jan-2006-mar-2006.txt" January-March 2006 Status Report Introduction The highlights of this quarters report certainly include the availability of native Java binaries thanks to the FreeBSD Foundation,=20 as well as progress has been made with Xen support and Sun's Ultrasparc T1. Futhermore we are looking forward to FreeBSD 6.1 and TrustedBSD audit support has been imported into FreeBSD 7-CURRENT. All in all, a very exiting start to 2006. In just under a month the developers will be gathering at BSDCan 2006 for, FreeBSD Dev Summit, a two day meeting of FreeBSD developers. Once again the BSDCan schedule is filled with many interesting talks. We hope you enjoy reading and look forward to hear from you for the next round. Consult the list of projects and ideas for ways to get involved. The submission date for the second quarter reports will be July, 7th 2006. Thanks to everybody who submitted a report and to Brad Davis, who joined the Status Report team, for proof reading. _________________________________________________________________ Projects * BSDInstaller * FreeSBIE * pfSense * Symbol Versioning * TrustedBSD Audit * TrustedBSD OpenBSM Network infrastructure * Bridge STP Improvements * FAST_IPSEC Upgrade * FreeBSD NFS Status Report * SMPng Network Stack Kernel * Low-overhead performance monitoring for FreeBSD * Sound subsystem improvements * Status Report ATA project * TMPFS (Filesystem) for FreeBSD Documentation * FreeBSD list of projects and ideas for volunteers Userland programs * Mouse Driver Framework * OpenBSD dhclient Architectures * ARM Support for TS-7200 * FreeBSD on Xen 3.0 * Ultrasparc T1 support Ports * libpkg - Package management library * Ports Collection * Update of the linux infrastructure in the Ports Collection Vendor / 3rd Party Software * HPLIP (Full HP Printer and MFD support) * Java Binaries * OpenBSD packet filter - pf Miscellaneous * BSDCan * FreeBSD Security Officer and Security Team * Fundraising for FreeBSD security development _________________________________________________________________ ARM Support for TS-7200 URL: http://www.embeddedarm.com/epc/ts7200-spec-h.html URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=3D//depot/use= r/jmg/arm&HIDEDEL=3DNO URL: http://people.freebsd.org/~jmg/dmesg.ts7200 Contact: John-Mark Gurney This is just an update to note that TS-7200 is building and running with a recent -current. I have been working on getting FreeBSD/arm running on the TS-7200. So far the board boots, and has somewhat working ethernet (some unexplained packet loss). I can netboot from a FreeBSD/i386 machine, and I can also mount msdosfs's on CF. Open tasks: 1. Figuring out why some small packets transmit with error (if someone can get Technologic Systems to pay attention to me and this issue, that'd be great!) 2. EP93xx identification information to properly attach various onboard devices _________________________________________________________________ Bridge STP Improvements Contact: Andrew Thompson Work has been started to implement the Rapid Spanning Tree Protocol which supersedes STP. RSTP has a much faster link failover time of around one second compared to 30-60 seconds for STP, this is very important on modern networks. Some progress has been made but a RSTP capable switch will be needed soon to proceed, see http://www.freebsd.org/donations/wantlist.html . Open tasks: 1. Donation of a RSTP switch _________________________________________________________________ BSDCan URL: http://www.bsdcan.org/2006/ Contact: Dan Langille The schedule for BSDCan 2006 demonstrates just how strong and popular BSDCan has become in a very short time. Three concurrent streams of talks make sure that there is something for everyone. We provide high quality talks at very affordable prices . BSDCan is the biggest BSD event of 2006. Ask others who attended in past years how much they enjoyed their time in Ottawa. Ask them who they met, who they talked to, the contacts they made, the information they learned. Remember to bring your wife/husband/spouse/etc because we will have things for them to do while you are attending the conference. Ottawa is a fantastic tourist destination. See you at BSDCan 2006! Open tasks: 1. Works in Progress - if you want to talk about your project for 5 minutes, this is your chance. Get in touch with us ASAP to reserve your spot. 2. We're looking for volunteers to help out just before and during the conference. Contact Dan at the above address. _________________________________________________________________ BSDInstaller URL: http://wikitest.freebsd.org/moin.cgi/BSDInstaller Contact: Andrew Turner The BSDInstaller integration work has progressed since the previous report. The backend has been changed to the new Lua version. This is to ensure the version we use will be maintained. The release Makefile now uses the Lua package rather the local copy in Perforce. Ports are also being created for the required modules to remove the need to bring Lua into the base. Open tasks: 1. Create a port for all the Lua modules required _________________________________________________________________ =46AST_IPSEC Upgrade URL: http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html Contact: George Neville-Neil Contact: Bjoern A. Zeeb Split out of PF_KEY code between the kernel and user space has been completed and committed to CVS. The diff between Kame IPv4 based IPSec and FAST_IPSEC IPv4 did not show any glaring issues. Moving on to making IPv6 work in FAST_IPSEC including being able to run the kernel with the following variations: * FAST_IPSEC in v4 only * KAME IPv6 and IPSec * KAME IPv6 and FAST_IPSEC Open tasks: 1. Any patches for FAST_IPSEC, KAME IPsec of either variant (v4 or v6) should be forwarded to bz@ and gnn@. 2. Build a better TAHI. TAHI, the test framework, will not be maintained and is not the easiest system to use and understand. A better test harness is possible and is necessary for other networking projects as well. Contact gnn@ if you have time to work on this as he has some code and ideas to start from. _________________________________________________________________ =46reeBSD list of projects and ideas for volunteers URL: http://www.FreeBSD.org/projects/ideas/ Contact: Joel Dahl Contact: Alexander Leidinger The FreeBSD list of projects and ideas for volunteers is doing well. Several items were picked up by volunteers and have found their way into the tree. Others are under review or in progress. We are looking forward to hear about new ideas, people willing to be technical contacts for generic topics (e.g. USB) or specific entries (already existing or newly created), suggestions for existing entries or completion reports for (parts of) an entry. Open tasks: 1. Add more ideas. 2. Find more technical contacts. 3. Find people willing to review/test implementations of (somewhat) finished items. _________________________________________________________________ =46reeBSD NFS Status Report Contact: Chuck Lever Support for NFS in FreeBSD received a boost this quarter as a kernel developer from Network Appliance has volunteered to help with the clients. Chuck Lever is now a src committer, mentored by Mike Silbersack. Mohan Srinivasan and Jim Rees have ended their apprenticeships and are now full committers. Mohan continues his effort to make the NFSv2/3 client SMP safe. He expects to make the changes available for review soon. FreeBSD gained presence at the annual NFS interoperability event known as Connectathon. Rick Macklem's FreeBSD NFSv4 server is pretty stable now and available via anonymous ftp. NFSv4.1 features are not a part of it yet and are not likely to happen until at least the end of 2006. Contact rick@snowhite.cis.uoguelph.ca for details. _________________________________________________________________ =46reeBSD on Xen 3.0 Contact: Scott Long Contact: Kip Macy We had hoped to finish a prototype of Xen DomU and possible Dom0 in time for FreeBSD 6.1. The primary work was focused on bringing Xen into the FreeBSD 'newbus' framework. Unfortunately, an architectural problem in FreeBSD has stopped us. Xen relies on message passing between to child and parent domains to communicate device configuration, and this message passing requires that tsleep and wakeup work early in boot. That doesn't seem to be the case, and it's unclear what it would take to make it work. Without the newbus work, it's hard to complete the Dom0 code, and impossible to support Xen 3.0 features like domain suspension. Open tasks: 1. Make tsleep and wakeup work during early boot 2. Continue DomU newbus work 3. Continue Dom0 work _________________________________________________________________ =46reeBSD Security Officer and Security Team URL: http://www.freebsd.org/security/ URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/st= aff-listing.html#STAFF-SECTEAM URL: http://vuxml.freebsd.org/ Contact: Security Officer Contact: Security Team In March 2006, Marcus Alves Grando, George Neville-Neil, and Philip Paeps joined the FreeBSD Security Team. The current Security Team membership is published on the web site. In the time since the last status report, eight security advisories have been issued concerning problems in the base system of FreeBSD; of these, three problems were in "contributed" code, while five were in code maintained within FreeBSD. The Vulnerabilities and Exposures Markup Language (VuXML) document has continued to be updated by the Security Team and the Ports Committers documenting new vulnerabilities in the FreeBSD Ports Collection; since the last status report, 50 new entries have been added, bringing the total up to 686. The following FreeBSD releases are supported by the FreeBSD Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, FreeBSD 5.4, and FreeBSD 6.0. Upon their release, FreeBSD 5.5 and FreeBSD 6.1 will also be supported. The respective End of Life dates of supported releases are listed on the web site; of particular note, FreeBSD 4.10 and FreeBSD 5.4 will cease to be supported at the end of May 2006. _________________________________________________________________ =46reeSBIE URL: http://www.freesbie.org URL: http://liste.gufi.org/mailman/listinfo/freesbie Contact: FreeSBIE Staff Contact: FreeSBIE Mailing List The project is alive and plans to release an ISO image of FreeSBIE 2.0 based on FreeBSD 6.1-RELEASE few day after the same has been release. FreeSBIE 2.0 will be available for i386 and amd64 archs. Tests images can be download via BitTorrent from torrent.freesbie.org . Open tasks: 1. Test "test ISO images" for both amd64 and i386 2. Suggest packages to be added to the ISO image. 3. Suggestions needed for Xfce and fluxbox look. 4. Suggestions needed for applications' configuration files. _________________________________________________________________ =46undraising for FreeBSD security development URL: http://people.freebsd.org/~cperciva/funding.html Contact: Colin Percival Since 2003, I have introduced the (now quite widely used) FreeBSD Update and Portsnap tools, but rarely had time to make improvements or add requested features. Consequently, on March 30th, I sent email to the the freebsd-hackers, freebsd-security, and freebsd-announce lists announcing that I was seeking funding to allow me to spend the summer working full-time on these and my role as FreeBSD Security Officer. Assuming that some cheques arrive as expected, I have reached my donation target and will start work at the beginning of May. Open tasks: 1. The work which I'm aiming to do is listed at the URL above. _________________________________________________________________ HPLIP (Full HP Printer and MFD support) URL: http://am-productions.biz/docs/hplip.php URL: http://hplip.sourceforge.net/ Contact: Anish Mistry A preliminary version of HP's hplip software for their printers and multi-function devices has been ported. This allows viewing of the status informantion from the printer. Such as ink levels, error messages, and queue information. If you have an Officejet you can also fax and scan. Photocard and Copies functionality is untested. Open tasks: 1. General Testing 2. Photocard Testing 3. Various ugen fixes 4. Fix Officejet Panel Display 5. Run hpiod and hpssd as unprivileged users 6. Banish the Linuxisms in the Makefile 7. Fix "Make Copies" 8. Automatically Setup Scanner _________________________________________________________________ Java Binaries URL: http://www.freebsdfoundation.org/downloads/java.shtml Contact: Deb Goodkin The FreeBSD Foundation released official certified JDK and JRE 1.5 binaries for the official FreeBSD 5.4 and FreeBSD 6.0 releases on the i386 platform. We were able to accomplish this by hiring a contractor to run the Sun certification tests and fixing the problems found. This could not have been completed with out the support from the BSD Java Team. We provided financial support for Java development and funded the certification process. We spent a significant amount of time and money on legal issues from contract and NDA creation for our contractor to license agreements from Sun and creating our own for the binaries. We worked with OEMs who would like to use the binaries, but needed to understand what they need to do legally to be able to redistribute the binaries. This is an area we are still working on at our end. We are waiting for a letter from Sun to put on our website to OEMs. We are also in the process of updating our OEM license agreement. This should be available by mid-April. We have received a positive response from the FreeBSD community regarding the release of the binaries. We received a few requests to support the FreeBSD 6.1/amd64 platform. We have decided to move forward and support this too. We currently are working with a contractor to provide Java support on 5.5/i386, 6.1/i386, and 6.1/amd64. Once 5.5 and 6.1 are released, we'll update the FreeBSD Foundation website with the Java status. Regular updates to the website will continue. _________________________________________________________________ libpkg - Package management library URL: http://libpkg.berlios.de/ URL: http://developer.berlios.de/projects/libpkg/ Contact: Andrew Turner Libpkg is a package management library using libarchive to extract the package files. It is able to download, install and get a list of installed packages. Work has also been started on implementing the package tools from the base system. Most of pkg_info has been implemented and pkg_add has been started. Open tasks: 1. Support for more command line options in pkg_info and pkg_add 2. Creating a package 3. Test pkg_add works as expected for all implemented command line options _________________________________________________________________ Low-overhead performance monitoring for FreeBSD URL: http://people.freebsd.org/~jkoshy/projects/perf-measurement Contact: Joseph Koshy This projects implements a kernel module (hwpmc(4)), an application programming interface (pmc(3)) and a few simple applications (pmcstat(8) and pmccontrol(8)) for measuring system performance using event monitoring hardware in modern CPUs. New features since the last status report: * Support for profiling dynamically loaded kernel and user objects has been added. * pmcstat(8) now supports command-line syntax for logging to a network socket. _________________________________________________________________ Mouse Driver Framework URL: http://www.semicomplete.com/projects/newpsm Contact: Jordan Sissel The current mouse system is a mess with moused, psm, ums, and mse supporting, individually, multiple kinds of mice. This project aims to move all driver support into moused modules in userland. In addition, many features lacking in the existing mouse infrastructure are being added. It is my hope that this new system will make both using mice and writing drivers easier down the road. Open tasks: 1. Testing. Contact if interested. _________________________________________________________________ OpenBSD dhclient Contact: Brooks Davis Contact: Sam Leffler All dhclient changes in HEAD have been merged to 6-STABLE for 6.1-RELEASE. New patches currently in testing include startup script support for fully asynchronous starting of dhclient which eliminates the wait for link during startup and support for sending the system hostname to the server when non is specified. _________________________________________________________________ OpenBSD packet filter - pf Contact: Max Laier Work towards importing the upcoming OpenBSD 3.9 version of pf is starting slowly. There are a couple of infrastructural changes (e.g. interface groups) that need to be imported beforehand. This work is in the final stage of progress. A couple of bugfixes have happend since the last report and will be available in FreeBSD 6.1/5.5. pf users are strongly encouraged to upgrade to RELENG_6 as the version present in RELENG_5 is collecting dust. _________________________________________________________________ pfSense URL: http://www.pfsense.com Contact: Scott Ullrich pfSense continues to grow and fix bugs. Since the last report we have grown to 14 developers working part and full time on bringing pfSense to 1.0. Beta 3 is scheduled for release on 4/15/2006. Open tasks: 1. Fix remaining bugs listed in CVSTrac 2. Fine tune existing code _________________________________________________________________ Ports Collection URL: http://www.freebsd.org/ports/ URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-po= rts/ URL: http://people.freebsd.org/~fenner/portsurvey/ URL: http://edwin.adsl.barnet.com.au/~edwin/ports/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.freebsd.org/portmgr/index.html URL: http://tinderbox.marcuscom.com Contact: Mark Linimon During this time, the number of ports PRs rose dramatically from its impressive low number seen late last quarter. This was due to the holidays, the freeze for the 5.5/6.1 release cycle, and the aggressive work several submitters have been doing to correct long-standing problems with stale distfiles, stale WWW sites, port that only work on i386, and so forth. Over 200 new ports have also been added. The statistics do not truly reflect the state of the Ports Collection, which continues to improve despite the increased number of ports. We now have 3 people who are qualified to run the 5-exp regression tests. Due to this, we were able to run several cycles, resulting in a series of commits that retired more than 3 dozen portmgr PRs. There were a few snags during one commit due to some unintended consequences, but the breakage was fixed in less than one day. Notable changes include the addition of physical category net-p2p and virtual categories hamradio and rubygems. Once 5.5 and 6.1 are released, portmgr hopes to be able to run regression tests more often. We have added 5 new committers since the last report. Open tasks: 1. We need help getting back to our modern low of 500 PRs. 2. We have over 4,000 unmaintained ports (see, for instance, the list on portsmon ). We are always looking for dedicated volunteers to adopt at least a few ports. _________________________________________________________________ SMPng Network Stack URL: http://www.FreeBSD.org/projects/netperf/ Contact: Robert Watson The FreeBSD netperf project has recently focused on revising the socket and protocol control block reference counts to define and enforce reference and memory management invariants, allowing the removal of unnecessary checks, error handling, and locking. Use of global pcbinfo locks has now been eliminated from the socket send and receive paths into all network protocols, including netipx, netnatm, netatalk, netinet, netinet6, netgraph, and others. Checks have generally been replaced with assertions; so_pcb is now guaranteed to be non-NULL. This should improve performance by reducing lock contention and unnecessary checks, as well as facilitate future work to eliminate long holding of pcbinfo locks in the TCP input path through proper reference counting for pcbs. These changes have been committed to FreeBSD 7-CURRENT, and will be merged in a few months once they have stabilized. _________________________________________________________________ Sound subsystem improvements URL: http://www.leidinger.net/FreeBSD/hdac-20060313.tbz Contact: Multimedia Mailinglist Contact: Ariff Abdullah Contact: Alexander Leidinger A lot of fixes (bugs, LORs, panics) and improvements (performance, compatibility, a new driver, 24/32bit samples support, ...) have been merged to RELENG_6. FreeBSD 6.1 is the first release which ships with the much improved sound system. Additionally there's work underway: * To make the sound system API endianess clean. This should make it easier (for a developer) to make the sound drivers usable on all architectures. * To rework character device allocation. This way someone can choose a specific channel, e.g. /dev/dsp0.r0 or /dev/dsp0.p0 to access the first recording or play channel respectively). With the "current" sound system (as in FreeBSD 6.1) this is not possible (accessing /dev/dsp0.0 and /dev/dsp0.1 may give you the first or the second channel, the number is just an enumeration, not a channel-chooser). * To add multi-channel support/processing. * To add Intel HDA support. There's already some code to look at (see URL referenced above), but is far from usable for an enduser (we need some programmers, but no testers ATM, since there are no user testable parts yet). Interested volunteers should contact the multimedia mailinglist. Parts of this work may be already in 6.1, but there's still a good portion which isn't even in -current as of this writting. Open tasks: 1. Style(9) cleanup, survive against WARNS=3D2 (at least). 2. Have a look at the sound related entries on the ideas list. 3. Rewrite some parts (e.g. a new mixer subsystem with OSS compatibility). 4. sndctl(1): tool to control non-mixer parts of the sound system (e.g. spdif switching, virtual-3D effects) by an user (instead of the sysctl approach in -current); pcmplay(1), pcmrec(1), pcmutil(1). 5. Plugable FEEDER infrastructure. For ease of debugging various feeder stuff and/or as userland library and test suite. 6. Closer compatibility with OSS, especially for the upcoming OSS v4. _________________________________________________________________ Status Report ATA project Contact: S=F8ren Schmidt The last months has mostly been about stabilizing ATA for 6.1-RELEASE, and adding support for new chipsets. On that front JMicron has raised the bar for vendors as they have provided not only hardware but documentation on both their hardware and their software RAID implementation, making it a breeze to add support for their, by the way excellent, products. Other vendors can join in here. :) Otherwise I'm always in the need for any amount of time or means to get it if nothing else. ATA has grown a USB backend so that fx. flash keys and external HD/CD/DVD drives can be used directly without atapicam/CAM etc. This is very handy on small (embedded) systems where resources are limitted and kernel space at a premium. burncd(8) is in the process of being updated so it will support this along with SATA ATAPI devices, and if time permits adding DVD support. The next months will be used to (hopefully) work on getting ATA to work properly on systems with > 4G of memory and utilize the 64bit addressing of controllers that supports it. RAID5 support for ataraid is on the list as well together with hardening of the RAID subsystem to help keep data alive and well. _________________________________________________________________ Symbol Versioning URL: http://people.freebsd.org/~deischen/symver/library_versioning.html URL: http://docs.sun.com/app/docs/doc/817-1984 URL: http://people.redhat.com/~drepper/symbol-versioning Contact: Daniel Eischen Symbol versioning libraries allows us to maintain binary compatibility without bumping library version numbers. Recently, symbol versioning for libc, libpthread, libthread_db, and libm was committed to -current. It is disabled by default, and can be enabled by adding "SYMVER_ENABLED=3Dtrue" to/etc/make.conf. A final version bump for libc and other affected libraries (perhaps all) should be done before enabling this by default. Open tasks: 1. Determining the impact on ports - portmgr (Kris) is running a portbuild to identify any problems. I am working to resolve the few problems that were found. 2. Making our linker link to libc and libpthread (when using (-pthread) when building shared libraries. This is needed so that symbol version dependencies are recorded in the shared library. I think kan is working on this.??? 3. Identify and symbol version any other libraries that should be symbol versioned. If anyone has any suggestions, I'm all ears. _________________________________________________________________ TMPFS (Filesystem) for FreeBSD URL: http://download.purpe.com/tmpfs URL: http://download.purpe.com/tmpfs/bmark.html Contact: Rohit Jalan Three betas have been released so far. The code is operational and seems to be stable but it is not MPSAFE as yet. The second and third betas used different mechanisms for data I/O. (sfbuf vs. kernel_map+vacache) and at present I am in the process on selecting one mechanism over the other. Your opinion is solicited. _________________________________________________________________ TrustedBSD Audit URL: http://www.TrustedBSD.org/audit.html Contact: Robert Watson Contact: In the past three months, the TrustedBSD CAPP audit implementation has been merged to the FreeBSD 7-CURRENT development tree in CVS, and the groundwork has been laid for a merge to 6.X. OpenBSM, a BSD-licensed implementation of Sun's Basic Security Module (BSM) API and file format, as well as extensions to support intrusion detect applications. New features included support for audit pipes, a pseudo-device that provides a live audit record trail interface for intrusion detection applications, and an audit filter daemon that allows plug-in modules to monitor live events. Open tasks: 1. Complete audit coverage of non-native system call ABIs, some more recent base system calls. 2. Integrate OpenBSM 1.0 alpha 6, which includes auditfilterd and the audit filter API. _________________________________________________________________ TrustedBSD OpenBSM URL: http://www.OpenBSM.org/ Contact: Robert Watson Contact: OpenBSM is a BSD-licensed implementation of Sun's Basic Security Module (BSM) API and file format, based on Apple's Darwin implementation. OpenBSM 1.0 alpha 5 is now available, and includes significant bugfixes, documentation, and feature enhancements over previous releases, including 64-bit token support, endian-independent operation, improved memory management, and bug fixes resulting from the static analysis tools provided by Coverity and FlexeLint. Recent versions are now built and configured using autoconf and automake, and have been built and tested with FreeBSD, Mac OS X, and Linux. Open tasks: 1. Complete OpenBSM file format validation test suite. 2. Finalize audit filter API. 3. Complete file format documentation; record documentation for new record types associated with Mac OS X, FreeBSD, and Linux specific events not present in documented Solaris record format. _________________________________________________________________ Ultrasparc T1 support URL: http://opensparc-t1.sunsource.net/index.html URL: http://www.fsmware.com/sun4v/todo.txt Contact: Kip Macy Contact: John Gurney FreeBSD has been ported the T1, Sun's newest processor. FreeBSD currently runs multi-user SMP. JMG is actively working on improving device support. The port has taken several weeks longer than initially anticipated as the majority of the current sparc64 port could not be re-used. _________________________________________________________________ Update of the linux infrastructure in the Ports Collection Contact: Emulation Mailinglist Contact: Alexander Leidinger Contact: Boris Samorodov Work is underway to use the new linux_base-fc3 as the new default linux base. Since there's some infrastructure work to do before it can be made the new default, this will not happen before the release of FreeBSD 5.5 and 6.1. At the same time a new X.org based linux port will replace the outdated XFree86 based linux X11 port. The use of fc3 instead of fc4 or fc5 is to make sure we have a smooth transition with as less as possible breakage. We already use several fc3 RPM's with the current default of linux_base-8, so there should be not much problems to solve. Open tasks: 1. Mark all old linux_base ports as DEPRECATED (after making fc3 the default linux_base port). 2. Have a look at a linux-dri version which works with the update to X.org. 3. When everything is switched to fc3 and everything works at least as good as before, have a look at porting fc4 or fc5. _________________________________________________________________ Legal Notices | =A9 1995-2006 The FreeBSD Project. All rights reserved. --Boundary-00=_LHxPEfzmILCscGB-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 03:13:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2460716A403 for ; Fri, 14 Apr 2006 03:13:58 +0000 (UTC) (envelope-from matthew@mundomateo.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA9B543D49 for ; Fri, 14 Apr 2006 03:13:57 +0000 (GMT) (envelope-from matthew@mundomateo.com) Received: from [10.0.81.12] (unknown [10.0.81.1]) by mail.mundomateo.com (Postfix) with ESMTP id EDD542844E; Thu, 13 Apr 2006 23:13:56 -0400 (EDT) Message-ID: <443F1371.9080905@mundomateo.com> Date: Thu, 13 Apr 2006 23:13:53 -0400 From: Matthew Hagerty User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Andrew MacIntyre References: <443E95C1.4030404@digitalstratum.com> <443E9C38.709@dial.pipex.com> <443EE34A.2050906@bullseye.apana.org.au> In-Reply-To: <443EE34A.2050906@bullseye.apana.org.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 14 Apr 2006 03:21:17 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@mundomateo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 03:13:58 -0000 Andrew MacIntyre wrote: > Alex Zbyslaw wrote: > > {...} > >> Several times now I have had Linux servers (and production quality >> ones, not built by me ones :-)) die in a somewhat similar fashion. >> In every case the cause has been either a flaky disk or a flaky disk >> controller, or some combination. > > I've seen an instance of somewhat similar symptoms where a power supply > was sagging out of spec on one supply rail some time after startup. > When some disk activity happened, the extra power consumption caused the > voltage to sag further triggering the disk going AWOL. > > At the time this started to happen, the power supply was more than 12 > months old. > > ------------------------------------------------------------------------- > Andrew I MacIntyre "These thoughts are mine alone..." > E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 > andymac@pcug.org.au (alt) | Belconnen ACT 2616 > Web: http://www.andymac.org/ | Australia > _______________________________________________ I considered power problems, however the server has dual redundant 400 Watt power supplies, and is in a server room and none of the other machines in there are having problems like this one. I suppose it is possible that both supplies are failing, but that seems highly unlikely? Matthew From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 03:34:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32A9916A401; Fri, 14 Apr 2006 03:34:41 +0000 (UTC) (envelope-from matthew@digitalstratum.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id C596343D49; Fri, 14 Apr 2006 03:34:40 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from [10.0.81.12] (unknown [10.0.81.1]) by mail.mundomateo.com (Postfix) with ESMTP id 262AE2844E; Thu, 13 Apr 2006 23:34:40 -0400 (EDT) Message-ID: <443F184C.4030306@digitalstratum.com> Date: Thu, 13 Apr 2006 23:34:36 -0400 From: Matthew Hagerty Organization: Digital Stratum User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Paul Saab References: <443E95C1.4030404@digitalstratum.com> <443EE652.1020806@freebsd.org> In-Reply-To: <443EE652.1020806@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@digitalstratum.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 03:34:41 -0000 Did these serious race conditions exist in 5.4 also? This is not good news and it would be nice if there was some place to find out about what hardware drivers are considered stable for production servers. I always assumed that this was the function of the supported hardware page. Is this not the case? Can I pull just a certain driver from stable and use it with a release branch (no even sure how I would do that)? Or will there be dependency problems? I suppose I could run on stable until the driver is fixed in a release branch, but I need this box up and online, and I've always read that the stable branch is not the place for production servers. Is there any place I read about the status and work being done on the arm driver? Thanks, Matthew Paul Saab wrote: > There are serious race conditions with amr in 6.0 that can cause > serious hangs. I suggest you take the amr driver from RELENG_6 and > try that. > > Matthew Hagerty wrote: >> Greetings, >> >> I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon Intel >> motherboard with a LSILogic MegaRAID (amr0) controller. This machine >> has been running for about 2 years now, and was very stable until I >> updated from 5.3 to 5.4, and now 6.0. The crashing seems to be >> totally random and I have had it crash in as little as 12 hours and >> as long as 143 days. >> >> When the box goes down it does so in a strange way. First, it still >> responds to network probes like ping (usually), however, all console >> access is ignored. Also, some network ports still respond, like a >> telnet to port 22 to test SSH will yield an SSH banner, but trying to >> connect with SSH just hangs. Sometimes this is also true of the SMTP >> server, but not always. This also makes it impossible for me to use >> CARP to swap to the recently purchased spare machine, since the >> network interface is generally still responding so CARP does not >> detect a problem. >> >> My biggest problem with this is that there are *never* any console >> messages or log entries in any logs, no warnings about disk failure, >> buffer exhaustion, system failures, etc.. The machine simply seems >> to stop responding and the only way to correct the problem is a hard >> reboot. >> >> A strange thing did happen yesterday though, I believe I caught the >> box on the verge of failure. I was SSH'd in and did a ps to check >> things out. There were about 100 of these entries: >> >> 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup >> (postgres) >> >> The box runs a web-based app and connects to a local Postgres DB >> which seemed to be unable to start new connections being requested by >> the PHP scripts. At any rate, I stopped Apache and then tried to >> stop Postgres which resulted in (or just happened to coincide with) >> the box locking up and no longer responding to my SSH commands or >> attempts to reconnect with SSH. I hardly think this is a Postgres >> problem, but even if it was, a userland app should *not* be able to >> bring down a box... >> >> Can anyone shed some light on this, give me some options to try? >> What happened to kernel panics and such when there were serious >> errors going on? The only glimmer of information I have is that >> *one* time there was an error on the console about there not being >> any RAID controller available. I did purchase a spare controller and >> I'm about to swap it out and see if it helps, but for some reason I >> doubt it. If a controller like that was failing, I would certainly >> hope to see some serious error messages or panics going on. >> >> I have been running FreeBSD since version 1.01 and have never had a >> box so unstable in the last 12 or so years, especially one that is >> supposed to be "server" quality instead of the make-shift ones I put >> together with desktop hardware. And last, I'm getting sick of my >> Linux admin friends telling me "told you so! should have run >> Linux...", please give me something to stick in their pie holes! >> >> Thanks, >> Matthew >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" >> From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 03:37:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCB9416A404 for ; Fri, 14 Apr 2006 03:37:14 +0000 (UTC) (envelope-from matthew@digitalstratum.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 695EE43D55 for ; Fri, 14 Apr 2006 03:37:13 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from [10.0.81.12] (unknown [10.0.81.1]) by mail.mundomateo.com (Postfix) with ESMTP id C980328452 for ; Thu, 13 Apr 2006 23:37:12 -0400 (EDT) Message-ID: <443F18E5.5030005@digitalstratum.com> Date: Thu, 13 Apr 2006 23:37:09 -0400 From: Matthew Hagerty Organization: Digital Stratum User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <443E95C1.4030404@digitalstratum.com> <443E9C38.709@dial.pipex.com> <443EE34A.2050906@bullseye.apana.org.au> In-Reply-To: <443EE34A.2050906@bullseye.apana.org.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@digitalstratum.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 03:37:14 -0000 Andrew MacIntyre wrote: > Alex Zbyslaw wrote: > > {...} > >> Several times now I have had Linux servers (and production quality >> ones, not built by me ones :-)) die in a somewhat similar fashion. >> In every case the cause has been either a flaky disk or a flaky disk >> controller, or some combination. > > I've seen an instance of somewhat similar symptoms where a power supply > was sagging out of spec on one supply rail some time after startup. > When some disk activity happened, the extra power consumption caused the > voltage to sag further triggering the disk going AWOL. > > At the time this started to happen, the power supply was more than 12 > months old. > > ------------------------------------------------------------------------- > Andrew I MacIntyre "These thoughts are mine alone..." > E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 > andymac@pcug.org.au (alt) | Belconnen ACT 2616 > Web: http://www.andymac.org/ | Australia I considered power problems, however the server has dual redundant 400 Watt power supplies, and is in a server room and none of the other machines in there are having problems like this one. I suppose it is possible that both supplies are failing, but that seems highly unlikely? Matthew From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 03:50:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C19B16A408 for ; Fri, 14 Apr 2006 03:50:58 +0000 (UTC) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2961443D45 for ; Fri, 14 Apr 2006 03:50:57 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.88] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id C38EA1A3C2C; Thu, 13 Apr 2006 20:50:57 -0700 (PDT) Message-ID: <443F1C21.4040109@freebsd.org> Date: Thu, 13 Apr 2006 20:50:57 -0700 From: Paul Saab User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: matthew@digitalstratum.com References: <443E95C1.4030404@digitalstratum.com> <443EE652.1020806@freebsd.org> <443F184C.4030306@digitalstratum.com> In-Reply-To: <443F184C.4030306@digitalstratum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 03:50:58 -0000 The amr driver was not MPSAFE in 5.4 (i think) so you would not have run into these problems. You should be able to just take the driver from RELENG_6 and use it on a released branch. If it doesn't compile, let me know and I'll generate you a tarball or diff that will work. We had major issues with amr at work until Scott Long and I (mostly Scott) helped iron out the stability issues with amr. You should either run RELENG_6 or take the driver from RELENG_6 and use that. You'll get the added benefit of being able to use the Linux management tools (megarc) to see the status of your raid. Matthew Hagerty wrote: > Did these serious race conditions exist in 5.4 also? This is not good > news and it would be nice if there was some place to find out about > what hardware drivers are considered stable for production servers. I > always assumed that this was the function of the supported hardware > page. Is this not the case? > > Can I pull just a certain driver from stable and use it with a release > branch (no even sure how I would do that)? Or will there be > dependency problems? I suppose I could run on stable until the driver > is fixed in a release branch, but I need this box up and online, and > I've always read that the stable branch is not the place for > production servers. > > Is there any place I read about the status and work being done on the > arm driver? > > Thanks, > Matthew > > > Paul Saab wrote: >> There are serious race conditions with amr in 6.0 that can cause >> serious hangs. I suggest you take the amr driver from RELENG_6 and >> try that. >> >> Matthew Hagerty wrote: >>> Greetings, >>> >>> I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon >>> Intel motherboard with a LSILogic MegaRAID (amr0) controller. This >>> machine has been running for about 2 years now, and was very stable >>> until I updated from 5.3 to 5.4, and now 6.0. The crashing seems to >>> be totally random and I have had it crash in as little as 12 hours >>> and as long as 143 days. >>> >>> When the box goes down it does so in a strange way. First, it still >>> responds to network probes like ping (usually), however, all console >>> access is ignored. Also, some network ports still respond, like a >>> telnet to port 22 to test SSH will yield an SSH banner, but trying >>> to connect with SSH just hangs. Sometimes this is also true of the >>> SMTP server, but not always. This also makes it impossible for me >>> to use CARP to swap to the recently purchased spare machine, since >>> the network interface is generally still responding so CARP does not >>> detect a problem. >>> >>> My biggest problem with this is that there are *never* any console >>> messages or log entries in any logs, no warnings about disk failure, >>> buffer exhaustion, system failures, etc.. The machine simply seems >>> to stop responding and the only way to correct the problem is a hard >>> reboot. >>> >>> A strange thing did happen yesterday though, I believe I caught the >>> box on the verge of failure. I was SSH'd in and did a ps to check >>> things out. There were about 100 of these entries: >>> >>> 55050 ?? D 0:00.00 postmaster: ipa ipa ::1(63061) startup >>> (postgres) >>> >>> The box runs a web-based app and connects to a local Postgres DB >>> which seemed to be unable to start new connections being requested >>> by the PHP scripts. At any rate, I stopped Apache and then tried to >>> stop Postgres which resulted in (or just happened to coincide with) >>> the box locking up and no longer responding to my SSH commands or >>> attempts to reconnect with SSH. I hardly think this is a Postgres >>> problem, but even if it was, a userland app should *not* be able to >>> bring down a box... >>> >>> Can anyone shed some light on this, give me some options to try? >>> What happened to kernel panics and such when there were serious >>> errors going on? The only glimmer of information I have is that >>> *one* time there was an error on the console about there not being >>> any RAID controller available. I did purchase a spare controller >>> and I'm about to swap it out and see if it helps, but for some >>> reason I doubt it. If a controller like that was failing, I would >>> certainly hope to see some serious error messages or panics going on. >>> >>> I have been running FreeBSD since version 1.01 and have never had a >>> box so unstable in the last 12 or so years, especially one that is >>> supposed to be "server" quality instead of the make-shift ones I put >>> together with desktop hardware. And last, I'm getting sick of my >>> Linux admin friends telling me "told you so! should have run >>> Linux...", please give me something to stick in their pie holes! >>> >>> Thanks, >>> Matthew >>> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to >>> "freebsd-hackers-unsubscribe@freebsd.org" >>> > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 05:18:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92FC816A400 for ; Fri, 14 Apr 2006 05:18:10 +0000 (UTC) (envelope-from V.Ovsyannikov@kr.ru) Received: from ns.kr.ru (ns.kr.ru [84.22.128.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21B6B43D48 for ; Fri, 14 Apr 2006 05:18:09 +0000 (GMT) (envelope-from V.Ovsyannikov@kr.ru) Received: from n128-i254.skala-net.ru (n128-i254.skala-net.ru [84.22.128.254]) by ns.kr.ru (Postfix) with ESMTP id 33B3522E80 for ; Fri, 14 Apr 2006 13:18:04 +0800 (KRAST) Date: Fri, 14 Apr 2006 13:18:08 +0800 From: Vitaliy Ovsyannikov X-Priority: 3 (Normal) Message-ID: <1812954269.20060414131808@kr.ru> To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: hiding freebsd box from traceroute X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vitaliy Ovsyannikov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 05:18:10 -0000 Hello, freebsd-hackers. Is it possible to hide freebsd gateway from ip traceroute? -- Sincerely, Vitaliy Ovsyannikov JSC Skala, Krasnoyarsk, Russia From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 05:24:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95E0316A401 for ; Fri, 14 Apr 2006 05:24:41 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D58D43D46 for ; Fri, 14 Apr 2006 05:24:41 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k3E5Oe7e009418; Thu, 13 Apr 2006 22:24:40 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k3E5Oe82009417; Thu, 13 Apr 2006 22:24:40 -0700 Date: Thu, 13 Apr 2006 22:24:40 -0700 From: Brooks Davis To: Vitaliy Ovsyannikov Message-ID: <20060414052440.GA8636@odin.ac.hmc.edu> References: <1812954269.20060414131808@kr.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <1812954269.20060414131808@kr.ru> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-hackers@freebsd.org Subject: Re: hiding freebsd box from traceroute X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 05:24:41 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 14, 2006 at 01:18:08PM +0800, Vitaliy Ovsyannikov wrote: > Hello, freebsd-hackers. >=20 > Is it possible to hide freebsd gateway from ip traceroute? Compile your kernel with the IPSTEALTH option and then enable if with sysctl net.inet.ip.stealth=3D1 -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEPzIWXY6L6fI4GtQRAq1KAKC93SggmM7MgCexzYc1P6XCm1/SnACfeMCS nTLX/l7v0ZENP0dhxt+Q95M= =HiEH -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 10:02:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A16816A400; Fri, 14 Apr 2006 10:02:22 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 362A443D46; Fri, 14 Apr 2006 10:02:21 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.136] (helo=anti-virus01-07) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1FUL88-0006Ky-M4; Fri, 14 Apr 2006 11:02:20 +0100 Received: from [80.192.25.195] (helo=[192.168.0.2]) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1FUL88-0006hK-5C; Fri, 14 Apr 2006 11:02:20 +0100 Message-ID: <443F7329.8000804@dial.pipex.com> Date: Fri, 14 Apr 2006 11:02:17 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Paul Saab References: <443E95C1.4030404@digitalstratum.com> <443EE652.1020806@freebsd.org> <443F184C.4030306@digitalstratum.com> <443F1C21.4040109@freebsd.org> In-Reply-To: <443F1C21.4040109@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 10:02:22 -0000 Paul Saab wrote: > The amr driver was not MPSAFE in 5.4 (i think) so you would not have > run into these problems. You should be able to just take the driver > from RELENG_6 and use it on a released branch. If it doesn't compile, > let me know and I'll generate you a tarball or diff that will work. > We had major issues with amr at work until Scott Long and I (mostly > Scott) helped iron out the stability issues with amr. You should > either run RELENG_6 or take the driver from RELENG_6 and use that. > You'll get the added benefit of being able to use the Linux management > tools (megarc) to see the status of your raid. > Presumably this change will make it into 6.1 and is already in the betas/RCs? I'm confused by the megarc comment. There is a port of megarc in the ports which appears to work under 5.4 already, though I've only used it for simple reporting. I've seen references to Scott and your work on improving the driver which uses the same phrase "Linux management tools" but have no real idea what that refers to. Are there tools beyond megarc which now work? If so, any pointers much appreciated. --Alex From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 10:38:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D978C16A402; Fri, 14 Apr 2006 10:38:14 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EE9643D45; Fri, 14 Apr 2006 10:38:13 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3EAcB8n018406; Fri, 14 Apr 2006 10:38:11 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3EAcAge018405; Fri, 14 Apr 2006 10:38:10 GMT (envelope-from marco) Date: Fri, 14 Apr 2006 10:38:10 +0000 From: Marco van Tol To: John Baldwin Message-ID: <20060414103810.GA18114@tols.org> References: <20060412215021.GB1146@tols.org> <200604131020.42417.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604131020.42417.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1398/Fri Apr 14 09:03:44 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org X-Mailman-Approved-At: Fri, 14 Apr 2006 11:41:52 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 10:38:14 -0000 On Thu, Apr 13, 2006 at 10:20:40AM -0400, John Baldwin wrote: > On Wednesday 12 April 2006 17:50, Marco van Tol wrote: > > Hi there, > > > > My apologies if this is the wrong list to ask this kind of question. > > I would appreciate a pointer to the correct list if it is please. :) > > > > I noticed in the code for gkrellm /usr/ports/sysutils/gkrellm2 that SMP > > per-cpu statistics were not yet supported under FreeBSD, and decided to > > check whether I could add that. (I'm running a (dual-core) Athlon64 X2 > > with FreeBSD 6.1-PRERELEASE) > > I can't find sample code and/or documentation on how to acquire that > > information from the kernel. [...] > > Is there an interface under FreeBSD to acquire the necessary per-cpu > > statistics? > > They don't exist currently. I have a patch to make the stats per-CPU > for performance reasons (though it only helps out on systems with lots > of CPUs (like 10) and hurts on systems with fewer CPUs (like 4)). It > doesn't include a sysctl to get the per-CPU stats, but I could add one. OK, that I could use to get started on the code for adding per-CPU stats to gkrellm under FreeBSD. Is the patch against FreeBSD CURRENT? Then if the per-CPU stats code hits the STABLE trunk, it's likely to be only a few changes to what I did perhaps. Or am I running a bit to far ahead here? :) Is the patch in available your home area on www.freebsd.org? Thanks! Marco -- A male gynecologist is like an auto mechanic who never owned a car. - Carrie Snow From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 12:32:11 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DAFC16A404 for ; Fri, 14 Apr 2006 12:32:11 +0000 (UTC) (envelope-from tomoyuki@pobox.com) Received: from proof.pobox.com (proof.pobox.com [207.106.133.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id E041343D48 for ; Fri, 14 Apr 2006 12:32:10 +0000 (GMT) (envelope-from tomoyuki@pobox.com) Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id EB00EE5179; Fri, 14 Apr 2006 08:32:09 -0400 (EDT) Received: from localhost (ZH076183.ppp.dion.ne.jp [222.3.76.183]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id BA7733B3E3; Fri, 14 Apr 2006 08:32:07 -0400 (EDT) Date: Fri, 14 Apr 2006 21:31:52 +0900 (JST) Message-Id: <20060414.213152.74737565.tomoyuki@pobox.com> To: jeremie@le-hen.org From: Tomoyuki Murakami In-Reply-To: <20060413211224.GO71412@obiwan.tataz.chchile.org> References: <20060413211224.GO71412@obiwan.tataz.chchile.org> X-Fingerprint: 3A 3C 3D 8A D3 7F D7 AC 0C 1C 2E C6 E1 8B 12 5B X-PGP-Key-URL: http://www.c-wind.com/tomoyuki@pobox.com.asc X-Mailer: Mew version 4.2.54 on Emacs 21.4 / Mule 5.0 (SAKAKI) X-Face: &9m:"[g#xi7*b@EePhiQRN|!8v_ZLJ2y36k=5R22P_.h].I8ti_*00uUULxu-o, 1)qF==5\ gB6^TJo0,+L!y?=zxth0iJbo65d List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 12:32:11 -0000 ----Security_Multipart(Fri_Apr_14_21_31_52_2006_253)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>> On Thu, 13 Apr 2006 23:12:24 +0200, >>> Jeremie Le Hen wrote: jeremie> If I comment out the variable assignements : jeremie> % .if !defined(NO_CRYPT) && !defined(NO_OPENSSL) jeremie> % #CFLAGS+= -DWITH_SSL jeremie> % #DPADD= ${LIBSSL} ${LIBCRYPTO} jeremie> % #LDADD= -lssl -lcrypto jeremie> % .endif jeremie> jeremie> The resulting linker command is now : jeremie> % /usr/bin/ld -V -Bshareable -o libfetch.so.4 /usr/lib/crti.o /usr/lib/crtbeginS.o -L/usr/lib -x -soname libfetch.so.4 file.So http.So ftp.So common.So fetch.So -lgcc_pic -lgcc_pic /usr/lib/crtendS.o /usr/lib/crtn.o jeremie> jeremie> As you can see, we don't have "-lssl -lcrypto" any more. However, ldd(1) jeremie> still says that libfetch.so is linked against those libraries : jeremie> % jarjarbinks# ldd libfetch.so jeremie> % libfetch.so: jeremie> % libssl.so.4 => /usr/lib/libssl.so.4 (0x2c72e000) jeremie> % libcrypto.so.4 => /lib/libcrypto.so.4 (0x2cd74000) jeremie> jeremie> Only linking addresses change, but they do at every compilation. jeremie> jeremie> I would be glad if someone could explain why this happens. Makefile of libfetch includes .include at last line, and, you can see /usr/share/mk/bsd.lib.mk includes bsd.libnames.mk this makefile has .... .if defined(LDFLAGS) && !empty(LDFLAGS:M-static) .if !defined(NO_KERBEROS) && !defined(NOCRYPT) && !defined(NO_OPENSSL) LIBPAM+= ${LIBKRB5} ${LIBASN1} ${LIBCRYPTO} ${LIBCRYPT} \ ${LIBROKEN} ${LIBCOM_ERR} MINUSLPAM+= -lkrb5 -lasn1 -lcrypto -lcrypt -lroken -lcom_err .endif LIBPAM+= ${LIBRADIUS} ${LIBTACPLUS} ${LIBCRYPT} \ ${LIBUTIL} ${LIBOPIE} ${LIBMD} MINUSLPAM+= -lradius -ltacplus -lcrypt \ -lutil -lopie -lmd .... So, if you wouldn't like to do with -lssl and -lcrypto, define NO_CRYPTO and NO_OPENSSL appropriately. e.g. in make.conf. --- Tomo ----Security_Multipart(Fri_Apr_14_21_31_52_2006_253)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iQCVAwUARD+WPscdBA2xrHKhAQIT7QP7BUxbukLWLYdgs/xveGrm57MAQuM29Cht ECTB6d6o5a2QGkeuSXuPndeASqz5u/YMdcJHoQjmd3YR9dAd4nOWbtKaDcwvppML z1k82Qmn09NYUSpLwEZxqWpHc/RDAFo6NW9xpPjtnCYHAdzQyu0FE1z25h+SvYn3 op8yfFzzzzE= =Lx3J -----END PGP SIGNATURE----- ----Security_Multipart(Fri_Apr_14_21_31_52_2006_253)---- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 14:32:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A18616A401 for ; Fri, 14 Apr 2006 14:32:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E258543D46 for ; Fri, 14 Apr 2006 14:32:34 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3EEWXw2046206; Fri, 14 Apr 2006 10:32:33 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marco van Tol Date: Fri, 14 Apr 2006 10:17:29 -0400 User-Agent: KMail/1.9.1 References: <20060412215021.GB1146@tols.org> <200604131020.42417.jhb@freebsd.org> <20060414103810.GA18114@tols.org> In-Reply-To: <20060414103810.GA18114@tols.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604141017.30635.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1399/Fri Apr 14 08:12:27 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 14:32:37 -0000 On Friday 14 April 2006 06:38, Marco van Tol wrote: > On Thu, Apr 13, 2006 at 10:20:40AM -0400, John Baldwin wrote: > > On Wednesday 12 April 2006 17:50, Marco van Tol wrote: > > > Hi there, > > > > > > My apologies if this is the wrong list to ask this kind of question. > > > I would appreciate a pointer to the correct list if it is please. :) > > > > > > I noticed in the code for gkrellm /usr/ports/sysutils/gkrellm2 that SMP > > > per-cpu statistics were not yet supported under FreeBSD, and decided to > > > check whether I could add that. (I'm running a (dual-core) Athlon64 X2 > > > with FreeBSD 6.1-PRERELEASE) > > > I can't find sample code and/or documentation on how to acquire that > > > information from the kernel. > > [...] > > > > Is there an interface under FreeBSD to acquire the necessary per-cpu > > > statistics? > > > > They don't exist currently. I have a patch to make the stats per-CPU > > for performance reasons (though it only helps out on systems with lots > > of CPUs (like 10) and hurts on systems with fewer CPUs (like 4)). It > > doesn't include a sysctl to get the per-CPU stats, but I could add one. > > OK, that I could use to get started on the code for adding per-CPU stats to > gkrellm under FreeBSD. Is the patch against FreeBSD CURRENT? > > Then if the per-CPU stats code hits the STABLE trunk, it's likely to be only > a few changes to what I did perhaps. Or am I running a bit to far ahead > here? :) > > Is the patch in available your home area on www.freebsd.org? An early one but it doesn't export the data to userland yet. I need to figure out what interface to use for that. I could have the cp_time sysctl just include the CPU arrays after the global array and key off the passed in length to determine if they should be included or not. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 18:28:51 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 247FF16A406 for ; Fri, 14 Apr 2006 18:28:51 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61D7243D58 for ; Fri, 14 Apr 2006 18:28:49 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id k3EISl5U046136 for ; Fri, 14 Apr 2006 20:28:48 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Fri, 14 Apr 2006 20:28:47 +0200 From: Victor Balada Diaz To: hackers@freebsd.org Message-ID: <20060414182846.GA702@pato.euesrg02.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 18:28:51 -0000 Hi, I found that ldd doesn't report libc as a dependency on most (all?) libraries: pato> ldd /usr/lib/libfetch.so /usr/lib/libfetch.so: libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) does anyone know why? -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 18:41:15 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6297816A401 for ; Fri, 14 Apr 2006 18:41:15 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AEC243D6A for ; Fri, 14 Apr 2006 18:41:11 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k3EIf6lj007281; Fri, 14 Apr 2006 14:41:06 -0400 (EDT) Date: Fri, 14 Apr 2006 14:41:06 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Victor Balada Diaz In-Reply-To: <20060414182846.GA702@pato.euesrg02.net> Message-ID: References: <20060414182846.GA702@pato.euesrg02.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 18:41:15 -0000 On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > Hi, > I found that ldd doesn't report libc as a dependency on most (all?) > libraries: > > pato> ldd /usr/lib/libfetch.so > /usr/lib/libfetch.so: > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > > does anyone know why? AFAIK, it's being worked on. It's not just libc either, -pthread also has to start linking to libpthread. -- DE From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 19:00:25 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2868A16A407; Fri, 14 Apr 2006 19:00:25 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1756A43D66; Fri, 14 Apr 2006 19:00:14 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id k3EJ0DU6046409; Fri, 14 Apr 2006 21:00:13 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Fri, 14 Apr 2006 21:00:10 +0200 From: Victor Balada Diaz To: Daniel Eischen Message-ID: <20060414190010.GB702@pato.euesrg02.net> References: <20060414182846.GA702@pato.euesrg02.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 19:00:25 -0000 On Fri, Apr 14, 2006 at 02:41:06PM -0400, Daniel Eischen wrote: > On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > > >Hi, > >I found that ldd doesn't report libc as a dependency on most (all?) > >libraries: > > > >pato> ldd /usr/lib/libfetch.so > >/usr/lib/libfetch.so: > > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > > > >does anyone know why? > > AFAIK, it's being worked on. It's not just libc either, -pthread > also has to start linking to libpthread. Thanks for your fast reply. I'm trying to create a dependency in some libraries, but it does have the same problem as the libc. Is there any way to workaround it? -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 19:20:44 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEDD316A400 for ; Fri, 14 Apr 2006 19:20:44 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ED5F43D45 for ; Fri, 14 Apr 2006 19:20:44 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k3EJKfBq008803; Fri, 14 Apr 2006 15:20:41 -0400 (EDT) Date: Fri, 14 Apr 2006 15:20:41 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Victor Balada Diaz In-Reply-To: <20060414190010.GB702@pato.euesrg02.net> Message-ID: References: <20060414182846.GA702@pato.euesrg02.net> <20060414190010.GB702@pato.euesrg02.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 19:20:44 -0000 On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > On Fri, Apr 14, 2006 at 02:41:06PM -0400, Daniel Eischen wrote: >> On Fri, 14 Apr 2006, Victor Balada Diaz wrote: >> >>> Hi, >>> I found that ldd doesn't report libc as a dependency on most (all?) >>> libraries: >>> >>> pato> ldd /usr/lib/libfetch.so >>> /usr/lib/libfetch.so: >>> libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) >>> libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) >>> >>> does anyone know why? >> >> AFAIK, it's being worked on. It's not just libc either, -pthread >> also has to start linking to libpthread. > > Thanks for your fast reply. > > I'm trying to create a dependency in some libraries, but it does > have the same problem as the libc. Is there any way to workaround it? Well, you can always try adding -lc. -- DE From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 14 19:48:47 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CAF816A403; Fri, 14 Apr 2006 19:48:47 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA75043D46; Fri, 14 Apr 2006 19:48:46 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id k3EJmi85046704; Fri, 14 Apr 2006 21:48:44 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Fri, 14 Apr 2006 21:48:43 +0200 From: Victor Balada Diaz To: Daniel Eischen Message-ID: <20060414194843.GC702@pato.euesrg02.net> References: <20060414182846.GA702@pato.euesrg02.net> <20060414190010.GB702@pato.euesrg02.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 19:48:47 -0000 On Fri, Apr 14, 2006 at 03:20:41PM -0400, Daniel Eischen wrote: > On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > > >On Fri, Apr 14, 2006 at 02:41:06PM -0400, Daniel Eischen wrote: > >>On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > >> > >>>Hi, > >>>I found that ldd doesn't report libc as a dependency on most (all?) > >>>libraries: > >>> > >>>pato> ldd /usr/lib/libfetch.so > >>>/usr/lib/libfetch.so: > >>> libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > >>> libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > >>> > >>>does anyone know why? > >> > >>AFAIK, it's being worked on. It's not just libc either, -pthread > >>also has to start linking to libpthread. > > > >Thanks for your fast reply. > > > >I'm trying to create a dependency in some libraries, but it does > >have the same problem as the libc. Is there any way to workaround it? > > Well, you can always try adding -lc. I tried, but it doesn't work. ldd continues to tell me that libc is not a dependency, but if i use objdump -p it does appear as NEEDED. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 02:16:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21F7516A400 for ; Sat, 15 Apr 2006 02:16:26 +0000 (UTC) (envelope-from dragosi@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3B7F43D45 for ; Sat, 15 Apr 2006 02:16:25 +0000 (GMT) (envelope-from dragosi@web.de) Received: from smtp08.web.de (fmsmtp08.dlan.cinetic.de [172.20.5.216]) by fmmailgate01.web.de (Postfix) with ESMTP id D0F7F1F9A4FF for ; Sat, 15 Apr 2006 04:16:23 +0200 (CEST) Received: from [61.9.137.225] (helo=[192.168.60.100]) by smtp08.web.de with asmtp (TLSv1:RC4-SHA:128) (WEB.DE 4.106 #94) id 1FUaKl-0007Ok-00 for freebsd-hackers@freebsd.org; Sat, 15 Apr 2006 04:16:23 +0200 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-hackers@freebsd.org From: Dragos Ionita Date: Sat, 15 Apr 2006 12:16:23 +1000 X-Mailer: Apple Mail (2.749.3) Sender: dragosi@web.de X-Sender: dragosi@web.de X-Mailman-Approved-At: Sat, 15 Apr 2006 02:40:49 +0000 Subject: grep out of memory error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 02:16:26 -0000 Hi, not sure that I'm in the right mailing list here, but I got myselft the 6.1-RC1 amd64 iso yesterday and installed it. I've got a minimum system running and just 10 minutes ago, I ran a 'grep' command and it returned an "out of memory" error. The command run was: grep -d recurse sasl /* The error caused: swap_pager: out of swap space swap_pager_getswapspace(16): failed HOSTNAME kernel: pid 618 (grep), uid 0, was killed: out of swap space Killed Not sure, but this seems a bit odd; I've got one GB of RAM and 512M of swap space allocated. Running top beside the command gives you a nice view of what's happening: All of the RAM is used up almost instantly and the the swap space. All in all, in about 3 seconds, I get that out of memory error. Again, I'm not an expert in these matters, but it seems odd that grep needs more than 1.5GB to grep (even if it's recursive from the root dir). Does anyone else experience that problem as well? Thanks, Dragos From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 03:19:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E35E316A401 for ; Sat, 15 Apr 2006 03:19:18 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B8FE43D49 for ; Sat, 15 Apr 2006 03:19:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4473F1A4DE0; Fri, 14 Apr 2006 20:19:18 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5FE1A51878; Fri, 14 Apr 2006 23:19:17 -0400 (EDT) Date: Fri, 14 Apr 2006 23:19:17 -0400 From: Kris Kennaway To: Dragos Ionita Message-ID: <20060415031917.GA12531@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: grep out of memory error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 03:19:19 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 15, 2006 at 12:16:23PM +1000, Dragos Ionita wrote: > Hi, >=20 > not sure that I'm in the right mailing list here, but I got myselft =20 > the 6.1-RC1 amd64 iso yesterday and installed it. >=20 > I've got a minimum system running and just 10 minutes ago, I ran a =20 > 'grep' command and it returned an "out of memory" error. >=20 > The command run was: >=20 > grep -d recurse sasl /* >=20 > The error caused: >=20 > swap_pager: out of swap space > swap_pager_getswapspace(16): failed > HOSTNAME kernel: pid 618 (grep), uid 0, was killed: out of swap space > Killed >=20 > Not sure, but this seems a bit odd; I've got one GB of RAM and 512M =20 > of swap space allocated. >=20 > Running top beside the command gives you a nice view of what's =20 > happening: All of the RAM is used up almost instantly and the the =20 > swap space. All in all, in about 3 seconds, I get that out of memory =20 > error. >=20 > Again, I'm not an expert in these matters, but it seems odd that grep =20 > needs more than 1.5GB to grep (even if it's recursive from the root =20 > dir). >=20 > Does anyone else experience that problem as well? It's probably grepping /dev/zero, which is an exercise in futility. Kris --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEQGY0Wry0BWjoQKURArIsAJ4v4K4WSJRmSdxJqmh4/a9WLn48qACfUinC PEkMNIuhCRBqhy78N4KqmpM= =xWhr -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 05:05:47 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B31E416A403 for ; Sat, 15 Apr 2006 05:05:47 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42DBC43D45 for ; Sat, 15 Apr 2006 05:05:46 +0000 (GMT) (envelope-from marcus@FreeBSD.org) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.13.6/8.13.6) with ESMTP id k3F56Pol089217 for ; Sat, 15 Apr 2006 01:06:25 -0400 (EDT) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: hackers@FreeBSD.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-wMhOnLIF7YziXY1uFGwg" Organization: FreeBSD, Inc. Date: Sat, 15 Apr 2006 01:05:45 -0400 Message-Id: <1145077545.83050.15.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Cc: Subject: User mounting take 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 05:05:47 -0000 --=-wMhOnLIF7YziXY1uFGwg Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Based on feedback I received on my initial diff, I took another crack at user mounting. To address Robert's concerns, I drop the setuid permissions until needed. Therefore, all permission checks are now done in the kernel. The same is true for umount(8). silby asked for wildcard support. To handle that, I added glob support to both the fs_file and fs_spec fstab components (via fnmatch(3)), and also added a special %u pattern that can be used to represent the current user (i.e. the user running mount(8)). This effectively allows the following in /etc/fstab: //%u@server/homes /home/%u/smb_home smbfs rw,noauto,user 0 0 Then, a user could just run, for example: mount /home/marcus/smb_home And their SMB home directory would get mounted (~/.nsmbrc is also respected). Additionally, something like the following is also possible: /dev/acd0 /home/*/cdrom cd9660 ro,noauto,user 0 0 Same mount command works here: mount /home/marcus/cdrom Wildcards can also be mixed and matched. Finally, in testing this, I found a problem with smbfs, msdosfs, and ntfs relating to the statfs(2) f_flags field. smbfs always set this to 0, msdosfs didn't set this at all, and ntfs set this to all flags (not just those visible to statfs(2)). By fixing this, umount(8) works properly on relative paths to user mount points for those three file systems. http://www.marcuscom.com/downloads/usermount.diff Comments? Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-wMhOnLIF7YziXY1uFGwg Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEQH8pb2iPiv4Uz4cRAlRAAJ96bl0rgO/AOrilqA3AlfzNX0SOrgCdFJhO nbxnzqRvQtkzibbzmQ+nbwY= =3LWH -----END PGP SIGNATURE----- --=-wMhOnLIF7YziXY1uFGwg-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 09:48:23 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C47616A404; Sat, 15 Apr 2006 09:48:23 +0000 (UTC) (envelope-from bms@spc.org) Received: from mindfull.spc.org (mindfull.spc.org [83.167.185.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1E3943D93; Sat, 15 Apr 2006 09:48:22 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org ([83.167.185.2]) by mindfull.spc.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FUhO6-0002js-V1; Sat, 15 Apr 2006 10:48:18 +0100 Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id BB85965499; Sat, 15 Apr 2006 10:48:20 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27993-03-10; Sat, 15 Apr 2006 10:48:20 +0100 (BST) Received: by arginine.spc.org (Postfix, from userid 1078) id EA62A653F9; Sat, 15 Apr 2006 10:48:19 +0100 (BST) Date: Sat, 15 Apr 2006 10:48:19 +0100 From: Bruce M Simpson To: Joe Marcus Clarke Message-ID: <20060415094819.GI94628@spc.org> References: <1145077545.83050.15.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1145077545.83050.15.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.1i Organization: Incunabulum X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mindfull.spc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - spc.org X-Source: X-Source-Args: X-Source-Dir: Cc: hackers@FreeBSD.org Subject: Re: User mounting take 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 09:48:23 -0000 On Sat, Apr 15, 2006 at 01:05:45AM -0400, Joe Marcus Clarke wrote: > Finally, in testing this, I found a problem with smbfs, msdosfs, and > ntfs relating to the statfs(2) f_flags field. smbfs always set this to > 0, msdosfs didn't set this at all, and ntfs set this to all flags (not > just those visible to statfs(2)). By fixing this, umount(8) works > properly on relative paths to user mount points for those three file > systems. Very very cool. I've seen this behaviour before and it was annoying because it meant having to sudo to do user SMB mounts in my home directory. Thanks muchly for doing this work. BMS From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 10:13:46 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FC1E16A400; Sat, 15 Apr 2006 10:13:46 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (ns0.infracaninophile.co.uk [81.187.76.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF5943D46; Sat, 15 Apr 2006 10:13:44 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from [IPv6:::1] (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.13.6/8.13.6) with ESMTP id k3FADYTK097922; Sat, 15 Apr 2006 11:13:34 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4440C749.1040702@infracaninophile.co.uk> Date: Sat, 15 Apr 2006 11:13:29 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Thunderbird 1.5 (X11/20060401) MIME-Version: 1.0 To: Joe Marcus Clarke References: <1145077545.83050.15.camel@shumai.marcuscom.com> In-Reply-To: <1145077545.83050.15.camel@shumai.marcuscom.com> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigF41D92636019DEBF8CD5EADB" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.infracaninophile.co.uk [IPv6:::1]); Sat, 15 Apr 2006 11:13:35 +0100 (BST) X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on happy-idiot-talk.infracaninophile.co.uk Cc: hackers@freebsd.org Subject: Re: User mounting take 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 10:13:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF41D92636019DEBF8CD5EADB Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Joe Marcus Clarke wrote: >=20 > //%u@server/homes /home/%u/smb_home smbfs rw,noauto,user 0 = 0 >=20 > Then, a user could just run, for example: >=20 > mount /home/marcus/smb_home >=20 > And their SMB home directory would get mounted (~/.nsmbrc is also > respected). Nice. Very nice. A couple of questions though: What happens if the 'noauto' flag is omitted? Or the 'user' flag? Shoul= d %u or wild cards work for root? Should they work at boot time (ie. when 'mount -a' is run)? Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enigF41D92636019DEBF8CD5EADB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEQMdO8Mjk52CukIwRA1AsAJ9DPG/urBz6AUwfTHGDqtFtRxVgdgCgkF7R WpPNKTrDcX4RJe7RQquUUpc= =Rxto -----END PGP SIGNATURE----- --------------enigF41D92636019DEBF8CD5EADB-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 10:40:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6894716A408; Sat, 15 Apr 2006 10:40:09 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC02943D45; Sat, 15 Apr 2006 10:40:08 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3FAe5of028366; Sat, 15 Apr 2006 10:40:05 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3FAe5Lr028365; Sat, 15 Apr 2006 10:40:05 GMT (envelope-from marco) Date: Sat, 15 Apr 2006 10:40:05 +0000 From: Marco van Tol To: John Baldwin Message-ID: <20060415104005.GB27978@tols.org> Mail-Followup-To: John Baldwin , freebsd-hackers@freebsd.org References: <20060412215021.GB1146@tols.org> <200604131020.42417.jhb@freebsd.org> <20060414103810.GA18114@tols.org> <200604141017.30635.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604141017.30635.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1402/Sat Apr 15 07:05:03 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 10:40:09 -0000 On Fri, Apr 14, 2006 at 10:17:29AM -0400, John Baldwin wrote: > On Friday 14 April 2006 06:38, Marco van Tol wrote: > > On Thu, Apr 13, 2006 at 10:20:40AM -0400, John Baldwin wrote: > > > On Wednesday 12 April 2006 17:50, Marco van Tol wrote: > > > > Hi there, > > > > > > > > My apologies if this is the wrong list to ask this kind of question. > > > > I would appreciate a pointer to the correct list if it is please. :) > > > > > > > > I noticed in the code for gkrellm /usr/ports/sysutils/gkrellm2 that SMP > > > > per-cpu statistics were not yet supported under FreeBSD, and decided to > > > > check whether I could add that. (I'm running a (dual-core) Athlon64 X2 > > > > with FreeBSD 6.1-PRERELEASE) > > > > I can't find sample code and/or documentation on how to acquire that > > > > information from the kernel. > > > > [...] > > > > > > Is there an interface under FreeBSD to acquire the necessary per-cpu > > > > statistics? > > > > > > They don't exist currently. I have a patch to make the stats per-CPU > > > for performance reasons (though it only helps out on systems with lots > > > of CPUs (like 10) and hurts on systems with fewer CPUs (like 4)). It > > > doesn't include a sysctl to get the per-CPU stats, but I could add one. > > > > OK, that I could use to get started on the code for adding per-CPU stats to > > gkrellm under FreeBSD. Is the patch against FreeBSD CURRENT? > > > > Then if the per-CPU stats code hits the STABLE trunk, it's likely to be only > > a few changes to what I did perhaps. Or am I running a bit to far ahead > > here? :) > > > > Is the patch in available your home area on www.freebsd.org? > > An early one but it doesn't export the data to userland yet. I need to > figure out what interface to use for that. I could have the cp_time > sysctl just include the CPU arrays after the global array and key > off the passed in length to determine if they should be included or not. I must admit that I had to read up a bit to understand what you meant here, but I think I do now. I think it should work. If I understand correctly, the first array would have the composite CPU stats, and following arrays would be the CPU specific stats. Right? That'd be just like the linux /proc/stat. In case it's going to be done like this, will the sum of the CPU specific stats be the composite stats? I'm not familiar with the formal process of adding/changing sysctl's for the kernel, so can't give much more comment. :) I'm assuming there are formal guidelines to do things like that. Thanks! Marco -- Gisteren is het niet gelukt. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 16:16:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC17816A402 for ; Sat, 15 Apr 2006 16:16:36 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D6C343D5C for ; Sat, 15 Apr 2006 16:16:35 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so193423ugc for ; Sat, 15 Apr 2006 09:16:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:reply-to:to:subject:date:user-agent:disposition-notification-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=grB7B1jYgBxVoGhlMKvlH4zvreZdJyUWPdBMRXfE7BOyjo/wRYxUoGja51810+XcgS+sbqEkdlOXpIBKjk+MxN8I8mBBNEwIjq/VdOMdx3GDOIIzbz39N3VgadVr2TYGUOqHzDJeSh9vUUAHG53mO7osj7EodZC9VszJLAgim38= Received: by 10.67.19.11 with SMTP id w11mr1328005ugi; Sat, 15 Apr 2006 09:16:34 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id k30sm499487ugc.2006.04.15.09.16.32; Sat, 15 Apr 2006 09:16:33 -0700 (PDT) From: Hannes Hauswedell To: freebsd-hackers@freebsd.org Date: Sat, 15 Apr 2006 16:35:15 +0000 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Message-Id: <200604151635.16110.hannes.hauswedell@gmail.com> X-Mailman-Approved-At: Sat, 15 Apr 2006 16:35:38 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: weird problems with porupgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hannes Hauswedell List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 16:16:37 -0000 hi everybody! since some time now i am developing kports an advanced kde frontend for the freebsd-ports and in future also pkgsrc and openbsd ports. since the last release last summer i have gone through a complete rewrite and right now am at the point where i monitor portupgrades output and am having severe problems with portupgrade's behaviour. the problem is: depending on certain conditions portupgrade doesnt show a big part of the output. these conditions are: the application is started as a subprocess of another application, e.g. kdevelop and/or i use kprocess/qprocess to run the portupgrade command. if i run the applicaiton on its own and use popen() and pipes to access the output it works. this might make it appear to be a problem of the kprocess implementation, however i am pretty sure it is not. i have run the command with "| tee logfile" and the logfile also only has part of the output. this whole problem has been discussed @ http://www.bsdforen.de/showthread.php?p=119650 (in german), so if you speak german you could check that out. an example of the problem: i run the command "portupgrade -v -y -N -PP games/angband" without root previliges (this way the process is over pretty quickly). if run from inside a unix system pipe (file descriptor opened with popen and read with fgets) the output looks like this: -> Session started at: Thu, 06 Apr 2006 10:46:10 +0000 ---> Fresh installation of games/angband started at: Thu, 06 Apr 2006 10:46:17 +0000 ---> Checking for the latest package of 'games/angband' ---> Fetching the package(s) for 'angband-3.0.6' (games/angband) ---> Fetching angband-3.0.6 ++ Will try the following sites in the order named: ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/ ---> Invoking a command: curl ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/angband-3.0.6.tbz -o /var/tmp/portupgradeURBFUqpc/angband-3.0.6.tbz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 579k 0 1404 0 0 1423 0 0:06:57 --:--:-- 0:06:57 1423 20 579k 20 120k 0 0 75560 0 0:00:07 0:00:01 0:00:06 183k 59 579k 59 344k 0 0 130k 0 0:00:04 0:00:02 0:00:02 207k 96 579k 96 559k 0 0 153k 0 0:00:03 0:00:03 --:--:-- 210k 100 579k 100 579k 0 0 151k 0 0:00:03 0:00:03 --:--:-- 204k ---> Downloaded as angband-3.0.6.tbz ---> Identifying the package /var/tmp/portupgradeURBFUqpc/angband-3.0.6.tbz ** Failed to save the dowloaded tarball as /usr/ports/packages/All/angband-3.0.6.tbz ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! angband-3.0.6 (Permission denied - /usr/ports/packages/All/angband-3.0.6.tbz) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgradeURBFUqpc ---> Fetching the latest package(s) for 'angband' (games/angband) ---> Fetching angband ++ Will try the following sites in the order named: ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/ ---> Invoking a command: curl ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/angband.tbz -o /var/tmp/portupgrade7LnEZ0Si/angband.tbz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 579k 0 1404 0 0 1451 0 0:06:49 --:--:-- 0:06:49 1451 9 579k 9 56160 0 0 39568 0 0:00:15 0:00:01 0:00:14 118k 25 579k 25 147k 0 0 62424 0 0:00:09 0:00:02 0:00:07 100k 55 579k 55 322k 0 0 95434 0 0:00:06 0:00:03 0:00:03 128k 80 579k 80 464k 0 0 105k 0 0:00:05 0:00:04 0:00:01 134k 100 579k 100 579k 0 0 110k 0 0:00:05 0:00:05 --:--:-- 135k ---> Downloaded as angband.tbz ---> Identifying the package /var/tmp/portupgrade7LnEZ0Si/angband.tbz ** Failed to save the dowloaded tarball as /usr/ports/packages/All/angband-3.0.6.tbz ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! angband@ (Permission denied - /usr/ports/packages/All/angband-3.0.6.tbz) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgrade7LnEZ0Si ---> Fresh installation of games/angband ended at: Thu, 06 Apr 2006 10:46:31 +0000 (consumed 00:00:13) ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! games/angband (package not found) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ---> Session ended at: Thu, 06 Apr 2006 10:46:31 +0000 (consumed 00:00:20) however the same code, run as a subprocess of kdevelop misses the code colored in red. i have also checked the environemnt inside those process and tried encapsulating the command in "sh -c" without any results... now am out of ideas.... thanks for any help hannes p.s.: please cc to my email address i amnot a subscriber From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 17:33:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AEFD16A401 for ; Sat, 15 Apr 2006 17:33:16 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3B6643D45 for ; Sat, 15 Apr 2006 17:33:15 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from [192.168.214.215] (c-24-1-232-64.hsd1.tx.comcast.net[24.1.232.64]) by comcast.net (sccrmhc12) with ESMTP id <2006041517331401200huckve>; Sat, 15 Apr 2006 17:33:14 +0000 Message-ID: <44412E5B.2050202@computer.org> Date: Sat, 15 Apr 2006 12:33:15 -0500 From: Eric Schuele User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Hannes Hauswedell References: <200604151635.16110.hannes.hauswedell@gmail.com> In-Reply-To: <200604151635.16110.hannes.hauswedell@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: weird problems with porupgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 17:33:16 -0000 Hannes Hauswedell wrote: > hi everybody! > since some time now i am developing kports an advanced kde frontend for the freebsd-ports and in future also pkgsrc and openbsd ports. > since the last release last summer i have gone through a complete rewrite and right now am at the point where i monitor portupgrades output and am having severe problems with portupgrade's behaviour. > the problem is: depending on certain conditions portupgrade doesnt show a big part of the output. these conditions are: > the application is started as a subprocess of another application, e.g. kdevelop and/or i use kprocess/qprocess to run the portupgrade command. Could it be you are seeing the differences between stdout and stderr? > > if i run the applicaiton on its own and use popen() and pipes to access the output it works. > > this might make it appear to be a problem of the kprocess implementation, however i am pretty sure it is not. i have run the command with "| tee logfile" and the logfile also only has part of the output. this whole problem has been discussed @ http://www.bsdforen.de/showthread.php?p=119650 (in german), so if you speak german you could check that out. an example of the problem: > > i run the command "portupgrade -v -y -N -PP games/angband" without root previliges (this way the process is over pretty quickly). if run from inside a unix system pipe (file descriptor opened with popen and read with fgets) the output looks like this: > > -> Session started at: Thu, 06 Apr 2006 10:46:10 +0000 > ---> Fresh installation of games/angband started at: Thu, 06 Apr 2006 10:46:17 +0000 > ---> Checking for the latest package of 'games/angband' > ---> Fetching the package(s) for 'angband-3.0.6' (games/angband) > ---> Fetching angband-3.0.6 > ++ Will try the following sites in the order named: > ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/ > ---> Invoking a command: curl ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/angband-3.0.6.tbz -o /var/tmp/portupgradeURBFUqpc/angband-3.0.6.tbz > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > > 0 579k 0 1404 0 0 1423 0 0:06:57 --:--:-- 0:06:57 1423 > 20 579k 20 120k 0 0 75560 0 0:00:07 0:00:01 0:00:06 183k > 59 579k 59 344k 0 0 130k 0 0:00:04 0:00:02 0:00:02 207k > 96 579k 96 559k 0 0 153k 0 0:00:03 0:00:03 --:--:-- 210k > 100 579k 100 579k 0 0 151k 0 0:00:03 0:00:03 --:--:-- 204k > ---> Downloaded as angband-3.0.6.tbz > ---> Identifying the package /var/tmp/portupgradeURBFUqpc/angband-3.0.6.tbz > ** Failed to save the dowloaded tarball as /usr/ports/packages/All/angband-3.0.6.tbz > ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > ! angband-3.0.6 (Permission denied - /usr/ports/packages/All/angband-3.0.6.tbz) > ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgradeURBFUqpc > ---> Fetching the latest package(s) for 'angband' (games/angband) > ---> Fetching angband > ++ Will try the following sites in the order named: > ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/ > ---> Invoking a command: curl ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/angband.tbz -o /var/tmp/portupgrade7LnEZ0Si/angband.tbz > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > > 0 579k 0 1404 0 0 1451 0 0:06:49 --:--:-- 0:06:49 1451 > 9 579k 9 56160 0 0 39568 0 0:00:15 0:00:01 0:00:14 118k > 25 579k 25 147k 0 0 62424 0 0:00:09 0:00:02 0:00:07 100k > 55 579k 55 322k 0 0 95434 0 0:00:06 0:00:03 0:00:03 128k > 80 579k 80 464k 0 0 105k 0 0:00:05 0:00:04 0:00:01 134k > 100 579k 100 579k 0 0 110k 0 0:00:05 0:00:05 --:--:-- 135k > ---> Downloaded as angband.tbz > ---> Identifying the package /var/tmp/portupgrade7LnEZ0Si/angband.tbz > ** Failed to save the dowloaded tarball as /usr/ports/packages/All/angband-3.0.6.tbz > ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > ! angband@ (Permission denied - /usr/ports/packages/All/angband-3.0.6.tbz) > ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgrade7LnEZ0Si > ---> Fresh installation of games/angband ended at: Thu, 06 Apr 2006 10:46:31 +0000 (consumed 00:00:13) > ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > ! games/angband (package not found) > ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > ---> Session ended at: Thu, 06 Apr 2006 10:46:31 +0000 (consumed 00:00:20) > > however the same code, run as a subprocess of kdevelop misses the code colored in red. > i have also checked the environemnt inside those process and tried encapsulating the command in "sh -c" without any results... > > now am out of ideas.... > > thanks for any help > > hannes > > > p.s.: please cc to my email address i amnot a subscriber > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Regards, Eric From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 17:38:09 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A8BF16A402; Sat, 15 Apr 2006 17:38:09 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10BD843D45; Sat, 15 Apr 2006 17:38:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3FHaFMF032220; Sat, 15 Apr 2006 11:36:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 15 Apr 2006 11:36:30 -0600 (MDT) Message-Id: <20060415.113630.81407700.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20060414182846.GA702@pato.euesrg02.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: victor@bsdes.net, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 17:38:09 -0000 In message: Daniel Eischen writes: : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: : : > Hi, : > I found that ldd doesn't report libc as a dependency on most (all?) : > libraries: : > : > pato> ldd /usr/lib/libfetch.so : > /usr/lib/libfetch.so: : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) : > : > does anyone know why? : : AFAIK, it's being worked on. It's not just libc either, -pthread : also has to start linking to libpthread. We don't record libc dependencies into shared libraries right now. If we did, that would create some problems and solve some problems. With symbol versioning, it most likely will become moot, since we'll never have to bump libc major version again... Warner From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 17:59:57 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8818516A400 for ; Sat, 15 Apr 2006 17:59:57 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2625143D45 for ; Sat, 15 Apr 2006 17:59:56 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k3FHxmo0006805; Sat, 15 Apr 2006 13:59:48 -0400 (EDT) Date: Sat, 15 Apr 2006 13:59:48 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20060415.113630.81407700.imp@bsdimp.com> Message-ID: References: <20060414182846.GA702@pato.euesrg02.net> <20060415.113630.81407700.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: victor@bsdes.net, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 17:59:57 -0000 On Sat, 15 Apr 2006, M. Warner Losh wrote: > In message: > Daniel Eischen writes: > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > : > : > Hi, > : > I found that ldd doesn't report libc as a dependency on most (all?) > : > libraries: > : > > : > pato> ldd /usr/lib/libfetch.so > : > /usr/lib/libfetch.so: > : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > : > > : > does anyone know why? > : > : AFAIK, it's being worked on. It's not just libc either, -pthread > : also has to start linking to libpthread. > > We don't record libc dependencies into shared libraries right now. If > we did, that would create some problems and solve some problems. With > symbol versioning, it most likely will become moot, since we'll never > have to bump libc major version again... kan stated he was working on doing this, which is what I was referring to above. -- DE From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:07:48 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C55416A401; Sat, 15 Apr 2006 18:07:48 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E636A43D48; Sat, 15 Apr 2006 18:07:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3FI6PPn032677; Sat, 15 Apr 2006 12:06:25 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 15 Apr 2006 12:06:40 -0600 (MDT) Message-Id: <20060415.120640.28764842.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20060415.113630.81407700.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: victor@bsdes.net, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:07:48 -0000 In message: Daniel Eischen writes: : On Sat, 15 Apr 2006, M. Warner Losh wrote: : : > In message: : > Daniel Eischen writes: : > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: : > : : > : > Hi, : > : > I found that ldd doesn't report libc as a dependency on most (all?) : > : > libraries: : > : > : > : > pato> ldd /usr/lib/libfetch.so : > : > /usr/lib/libfetch.so: : > : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) : > : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) : > : > : > : > does anyone know why? : > : : > : AFAIK, it's being worked on. It's not just libc either, -pthread : > : also has to start linking to libpthread. : > : > We don't record libc dependencies into shared libraries right now. If : > we did, that would create some problems and solve some problems. With : > symbol versioning, it most likely will become moot, since we'll never : > have to bump libc major version again... : : kan stated he was working on doing this, which is what I was : referring to above. That makes sense. If you explicitly include libc on the command line to build the library, it is included... Warner From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:10:13 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8115C16A412 for ; Sat, 15 Apr 2006 18:10:13 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CCA43D7B for ; Sat, 15 Apr 2006 18:10:01 +0000 (GMT) (envelope-from marcus@FreeBSD.org) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.13.6/8.13.6) with ESMTP id k3FIAdCE096618; Sat, 15 Apr 2006 14:10:42 -0400 (EDT) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Matthew Seaman In-Reply-To: <4440C749.1040702@infracaninophile.co.uk> References: <1145077545.83050.15.camel@shumai.marcuscom.com> <4440C749.1040702@infracaninophile.co.uk> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-PJe8sJBT6m5pOLAoPqxk" Organization: FreeBSD, Inc. Date: Sat, 15 Apr 2006 14:09:57 -0400 Message-Id: <1145124597.43095.7.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Cc: hackers@FreeBSD.org Subject: Re: User mounting take 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:10:13 -0000 --=-PJe8sJBT6m5pOLAoPqxk Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2006-04-15 at 11:13 +0100, Matthew Seaman wrote: > Joe Marcus Clarke wrote: > >=20 > > //%u@server/homes /home/%u/smb_home smbfs rw,noauto,user 0 = 0 > >=20 > > Then, a user could just run, for example: > >=20 > > mount /home/marcus/smb_home > >=20 > > And their SMB home directory would get mounted (~/.nsmbrc is also > > respected). >=20 > Nice. Very nice. A couple of questions though: >=20 > What happens if the 'noauto' flag is omitted? I thought about this for a while. I considered adding a "glob" flag similar to noauto that would have to be present in order to do wilcarding. I decided not to do it, and force all wilcarded entries to be noauto. > Or the 'user' flag? If the "user" flag is omitted, then users will not be able to mount those file systems. > Should %u > or wild cards work for root? Yes. > Should they work at boot time (ie. when > 'mount -a' is run)? At this point, no. Wildcard expansion will not be done for -a. Such mounts will fail. Joe=20 >=20 > Cheers, >=20 > Matthew >=20 --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-PJe8sJBT6m5pOLAoPqxk Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEQTb1b2iPiv4Uz4cRAtVyAJsFrDo09G4U6htkgXb1sIGPkrTCQwCfarpH af0ZyJKSjq0Ju6Z7RzCigxQ= =JnTu -----END PGP SIGNATURE----- --=-PJe8sJBT6m5pOLAoPqxk-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:16:08 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0A4C16A400 for ; Sat, 15 Apr 2006 18:16:08 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43FF443D45 for ; Sat, 15 Apr 2006 18:16:08 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k3FIG4QO018579; Sat, 15 Apr 2006 14:16:04 -0400 (EDT) Date: Sat, 15 Apr 2006 14:16:04 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20060415.120640.28764842.imp@bsdimp.com> Message-ID: References: <20060415.113630.81407700.imp@bsdimp.com> <20060415.120640.28764842.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: victor@bsdes.net, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:16:08 -0000 On Sat, 15 Apr 2006, M. Warner Losh wrote: > In message: > Daniel Eischen writes: > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > In message: > : > Daniel Eischen writes: > : > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > : > : > : > : > Hi, > : > : > I found that ldd doesn't report libc as a dependency on most (all?) > : > : > libraries: > : > : > > : > : > pato> ldd /usr/lib/libfetch.so > : > : > /usr/lib/libfetch.so: > : > : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > : > : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > : > : > > : > : > does anyone know why? > : > : > : > : AFAIK, it's being worked on. It's not just libc either, -pthread > : > : also has to start linking to libpthread. > : > > : > We don't record libc dependencies into shared libraries right now. If > : > we did, that would create some problems and solve some problems. With > : > symbol versioning, it most likely will become moot, since we'll never > : > have to bump libc major version again... > : > : kan stated he was working on doing this, which is what I was > : referring to above. > > That makes sense. If you explicitly include libc on the command line > to build the library, it is included... Here's the link to his original reply to -current. Also, if you look at linux shared libraries, you'll note they have dependencies to libc. $ readelf -d /usr/compat/linux/lib/libpthread.so.0 Dynamic segment at offset 0x15128 contains 24 entries: Tag Type Name/Value 0x00000001 (NEEDED) Shared library: [libc.so.6] 0x0000000e (SONAME) Library soname: [libpthread.so.0] ... http://docs.freebsd.org/cgi/getmsg.cgi?fetch=884395+0+archive/2006/freebsd-current/20060212.freebsd-current -- DE From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:28:54 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F0CB16A402; Sat, 15 Apr 2006 18:28:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B834B43D45; Sat, 15 Apr 2006 18:28:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3FIQgCx032950; Sat, 15 Apr 2006 12:26:42 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 15 Apr 2006 12:26:57 -0600 (MDT) Message-Id: <20060415.122657.111699385.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20060415.120640.28764842.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: victor@bsdes.net, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:28:54 -0000 In message: Daniel Eischen writes: : On Sat, 15 Apr 2006, M. Warner Losh wrote: : : > In message: : > Daniel Eischen writes: : > : On Sat, 15 Apr 2006, M. Warner Losh wrote: : > : : > : > In message: : > : > Daniel Eischen writes: : > : > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: : > : > : : > : > : > Hi, : > : > : > I found that ldd doesn't report libc as a dependency on most (all?) : > : > : > libraries: : > : > : > : > : > : > pato> ldd /usr/lib/libfetch.so : > : > : > /usr/lib/libfetch.so: : > : > : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) : > : > : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) : > : > : > : > : > : > does anyone know why? : > : > : : > : > : AFAIK, it's being worked on. It's not just libc either, -pthread : > : > : also has to start linking to libpthread. : > : > : > : > We don't record libc dependencies into shared libraries right now. If : > : > we did, that would create some problems and solve some problems. With : > : > symbol versioning, it most likely will become moot, since we'll never : > : > have to bump libc major version again... : > : : > : kan stated he was working on doing this, which is what I was : > : referring to above. : > : > That makes sense. If you explicitly include libc on the command line : > to build the library, it is included... : : Here's the link to his original reply to -current. Also, if you : look at linux shared libraries, you'll note they have dependencies : to libc. I guess what I'm saying is that on FreeBSD, the system built shared libraries don't have libc recorded in them because we don't add -lc on the commnad line to build them. Other libraries do have it recorded in them, for example I have libxvidcore.so from some port on my system: readelf -d libxvidcore.so Dynamic segment at offset 0x8a39c contains 20 entries: Tag Type Name/Value 0x00000001 (NEEDED) Shared library: [libc.so.6] 0x00000001 (NEEDED) Shared library: [libm.so.4] If we hacked bsd.lib.mk to include -lc always, all shared libraries would have a libc dependency. Warner From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:34:47 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 201D516A400 for ; Sat, 15 Apr 2006 18:34:47 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2E1143D53 for ; Sat, 15 Apr 2006 18:34:45 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k3FIYfX9001489; Sat, 15 Apr 2006 14:34:41 -0400 (EDT) Date: Sat, 15 Apr 2006 14:34:41 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20060415.122657.111699385.imp@bsdimp.com> Message-ID: References: <20060415.120640.28764842.imp@bsdimp.com> <20060415.122657.111699385.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: victor@bsdes.net, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:34:47 -0000 On Sat, 15 Apr 2006, M. Warner Losh wrote: > In message: > Daniel Eischen writes: > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > In message: > : > Daniel Eischen writes: > : > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > : > : > In message: > : > : > Daniel Eischen writes: > : > : > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > : > : > : > : > : > : > Hi, > : > : > : > I found that ldd doesn't report libc as a dependency on most (all?) > : > : > : > libraries: > : > : > : > > : > : > : > pato> ldd /usr/lib/libfetch.so > : > : > : > /usr/lib/libfetch.so: > : > : > : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > : > : > : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > : > : > : > > : > : > : > does anyone know why? > : > : > : > : > : > : AFAIK, it's being worked on. It's not just libc either, -pthread > : > : > : also has to start linking to libpthread. > : > : > > : > : > We don't record libc dependencies into shared libraries right now. If > : > : > we did, that would create some problems and solve some problems. With > : > : > symbol versioning, it most likely will become moot, since we'll never > : > : > have to bump libc major version again... > : > : > : > : kan stated he was working on doing this, which is what I was > : > : referring to above. > : > > : > That makes sense. If you explicitly include libc on the command line > : > to build the library, it is included... > : > : Here's the link to his original reply to -current. Also, if you > : look at linux shared libraries, you'll note they have dependencies > : to libc. > > I guess what I'm saying is that on FreeBSD, the system built shared > libraries don't have libc recorded in them because we don't add -lc on > the commnad line to build them. Other libraries do have it recorded > in them, for example I have libxvidcore.so from some port on my > system: I guess the original poster confused me. He said in another reply to this thread that adding -lc failed to record a dependency on libc. But whatever, I think we're in agreement no matter how much we try to imply we're not :-) -- DE From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:45:18 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFF9B16A401; Sat, 15 Apr 2006 18:45:18 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6EAB43D49; Sat, 15 Apr 2006 18:45:17 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id k3FIjBN8071323; Sat, 15 Apr 2006 20:45:12 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Sat, 15 Apr 2006 20:45:11 +0200 From: Victor Balada Diaz To: "M. Warner Losh" Message-ID: <20060415184511.GA697@pato.euesrg02.net> References: <20060415.120640.28764842.imp@bsdimp.com> <20060415.122657.111699385.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060415.122657.111699385.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i Cc: deischen@freebsd.org, hackers@freebsd.org Subject: Re: Missing dependencies on shared libraries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:45:18 -0000 On Sat, Apr 15, 2006 at 12:26:57PM -0600, M. Warner Losh wrote: > In message: > Daniel Eischen writes: > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > In message: > : > Daniel Eischen writes: > : > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > : > : > In message: > : > : > Daniel Eischen writes: > : > : > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > : > : > : > : > : > : > Hi, > : > : > : > I found that ldd doesn't report libc as a dependency on most (all?) > : > : > : > libraries: > : > : > : > > : > : > : > pato> ldd /usr/lib/libfetch.so > : > : > : > /usr/lib/libfetch.so: > : > : > : > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > : > : > : > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > : > : > : > > : > : > : > does anyone know why? > : > : > : > : > : > : AFAIK, it's being worked on. It's not just libc either, -pthread > : > : > : also has to start linking to libpthread. > : > : > > : > : > We don't record libc dependencies into shared libraries right now. If > : > : > we did, that would create some problems and solve some problems. With > : > : > symbol versioning, it most likely will become moot, since we'll never > : > : > have to bump libc major version again... > : > : > : > : kan stated he was working on doing this, which is what I was > : > : referring to above. > : > > : > That makes sense. If you explicitly include libc on the command line > : > to build the library, it is included... > : > : Here's the link to his original reply to -current. Also, if you > : look at linux shared libraries, you'll note they have dependencies > : to libc. > > I guess what I'm saying is that on FreeBSD, the system built shared > libraries don't have libc recorded in them because we don't add -lc on > the commnad line to build them. If i try to add -lc ldd doesn't show it as a dependency, but readelf/dumpelf does show it as NEEDED. Is this the expected behavior? Why isn't ldd showing the dependency? -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 18:56:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E083816A401 for ; Sat, 15 Apr 2006 18:56:08 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4358343D46 for ; Sat, 15 Apr 2006 18:56:08 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so208079ugc for ; Sat, 15 Apr 2006 11:56:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:disposition-notification-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=PxJYMdZ2fJp8ZFahaLSCwApHVhdCCd9nQLwnzL0+Gl8mnFMjToRU9OOE4FkG0gvg8n+6V2EAO1GQDe5vAiRcW3eKswB54YekDLy3V6+aBKb3NB+3qtq7BbqBc12HyZOLdxosMVoFB1le9A14wMdJtLTFFiZMdN75PTpvtMPmWus= Received: by 10.67.30.1 with SMTP id h1mr1581509ugj; Sat, 15 Apr 2006 11:56:07 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id q40sm72866ugc.2006.04.15.11.56.06; Sat, 15 Apr 2006 11:56:06 -0700 (PDT) From: Hannes Hauswedell To: freebsd-hackers@freebsd.org Date: Sat, 15 Apr 2006 19:14:50 +0000 User-Agent: KMail/1.9.1 References: <200604151635.16110.hannes.hauswedell@gmail.com> <44412E5B.2050202@computer.org> In-Reply-To: <44412E5B.2050202@computer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604151914.50718.hannes.hauswedell@gmail.com> X-Mailman-Approved-At: Sat, 15 Apr 2006 20:29:59 +0000 Subject: Re: weird problems with porupgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 18:56:09 -0000 > Could it be you are seeing the differences between stdout and stderr? no, of course not :D but thanks From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 21:26:10 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A21AA16A401 for ; Sat, 15 Apr 2006 21:26:10 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from Mail.elbekies.net (mail.elbekies.net [217.6.211.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34FDD43D66 for ; Sat, 15 Apr 2006 21:26:10 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-016.eplus-online.de [212.23.126.16]) by Mail.elbekies.net (Postfix) with ESMTP id 2A8D067870 for ; Sat, 15 Apr 2006 23:26:05 +0200 (CEST) Received: from [192.168.201.3] (unknown [192.168.201.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 1AC465C0F for ; Sat, 15 Apr 2006 23:26:10 +0200 (CEST) Message-ID: <444164F2.50103@vwsoft.com> Date: Sat, 15 Apr 2006 23:26:10 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.6.0.101 MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-Elbekies-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-Mailman-Approved-At: Sat, 15 Apr 2006 21:27:44 +0000 Cc: Subject: nozomi interface to 3g / umts cards X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 21:26:10 -0000 Hi hackers, I'm wondering if anyone is already working on a port of the nozomi card interface? For those not being aware of, the nozomi interface is the next generation interface for Option Wireless N.V. 3G / UMTS cards. Option released the source of their nozomi interface under a GPL style license and a Linux port already exists. I would like to try a port of the sources to BSD if no one else is already working on it. Nozomi is building the interface to HSDPA (high speed downlink packet access = up to 7.2 MBit/s) 3G cards which is highly of (at least my) interest for the BSDs. I'm already running a 3G router under FreeBSD RELENG_6 (more or less satisfiying as there's a total lack of manufacturer documentation from Novatel Wireless). Also I do see the need for improving parts of the FreeBSD system to automatically detect other (older) 3G cards (the only card currently being detected is a Novatel Wireless U530/U630 which implements serial-over-PCMCIA but with that card sio.c needs to get a very easy patch). Most Option N.V. cards do not run with stock FreeBSD but the changes are minimal to get it to work. But my number one task is the nozomi interface. As I've never developed kernel modules or device drivers I would probably need one of the current hackers (probably from core team) as a mentor and also as a commiter. Again, main question is currently: Is anybody already working on the nozomi interface? Greetings, Volker From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 21:30:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55DA416A408 for ; Sat, 15 Apr 2006 21:30:42 +0000 (UTC) (envelope-from peter@vk2pj.dyndns.org) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE0AC43D4C for ; Sat, 15 Apr 2006 21:30:38 +0000 (GMT) (envelope-from peter@vk2pj.dyndns.org) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail03.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k3FLUbvE028542 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 16 Apr 2006 07:30:37 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k3FLUa8m006717; Sun, 16 Apr 2006 07:30:37 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k3FLUaYL006716; Sun, 16 Apr 2006 07:30:36 +1000 (EST) (envelope-from peter) Date: Sun, 16 Apr 2006 07:30:36 +1000 From: Peter Jeremy To: Hannes Hauswedell Message-ID: <20060415213036.GC830@turion.vk2pj.dyndns.org> References: <200604151635.16110.hannes.hauswedell@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604151635.16110.hannes.hauswedell@gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Sat, 15 Apr 2006 21:45:08 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: weird problems with porupgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 21:30:42 -0000 On Sat, 2006-Apr-15 16:35:15 +0000, Hannes Hauswedell wrote: >however the same code, run as a subprocess of kdevelop misses the code colored in red. I don't see any red. Could you post a unidiff or similar please. -- Peter Jeremy