From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 02:22:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D88C16A402; Sun, 28 Jan 2007 02:22:00 +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 A609513C478; Sun, 28 Jan 2007 02:21:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0S2LaJg069344; Sat, 27 Jan 2007 19:21:37 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 27 Jan 2007 19:22:04 -0700 (MST) Message-Id: <20070127.192204.-862243883.imp@bsdimp.com> To: hselasky@c2i.net From: "M. Warner Losh" In-Reply-To: <200701241254.51900.hselasky@c2i.net> References: <20070124113858.GG64263@hoeg.nl> <200701241254.51900.hselasky@c2i.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 27 Jan 2007 19:21:40 -0700 (MST) Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, ed@fxq.nl, pietro.cerutti@gmail.com Subject: Re: atacontrol kernel crash (atausb?) 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, 28 Jan 2007 02:22:00 -0000 In message: <200701241254.51900.hselasky@c2i.net> Hans Petter Selasky writes: : Instead of having all these quirks, isn't it possible that the SCSI layer can : auto-probe this? The short answer is no. There's no reliable way to tell if a device supports a given scsi command, and some devices freak out (lock up) when sent one. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 05:31:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EEB4716A401 for ; Sun, 28 Jan 2007 05:31:51 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: from smtp111.sbc.mail.mud.yahoo.com (smtp111.sbc.mail.mud.yahoo.com [68.142.198.210]) by mx1.freebsd.org (Postfix) with SMTP id C049F13C4AA for ; Sun, 28 Jan 2007 05:31:51 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: (qmail 69911 invoked from network); 28 Jan 2007 05:31:47 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=zd6QYFoPgeosh6Xy+gqiqXKBSLmd4uWYnFWj9kSabfQWeckUAUMbLRj+mJX8o6GXJPfNlpGpHm9l4ra3fiI1Cc7bMtUbV49f0pilhfRTZlhaYgKBt0hMeb5+dLOnHjAJivXdHfj3kGIPvmXEAm84qSSIlZkyO+AXxJHheXWrTa0= ; Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@71.146.53.89 with plain) by smtp111.sbc.mail.mud.yahoo.com with SMTP; 28 Jan 2007 05:31:47 -0000 X-YMail-OSG: gVuzVL8VM1lxDiyZUsTwf6HKDYDxOzSiN11KcTzKrYHBkeogVMwPANI2ofBr2N7BYGRoa4WS4j5AMtAVn9YjW1TSzImCChShmT4mGFNHdbxXBkDFkfmQ9ObABpL53zxygBSghXQ.vQWIXGHLhFXNdMIPqf9yHCE9 Message-ID: <45BC3624.3000608@pacbell.net> Date: Sat, 27 Jan 2007 21:35:32 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 6.1-RELEASE-p7; en-US; ja-JP; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: "Devon H. O'Dell" References: <4587F6F1.1050000@metro.cx> <9ab217670612190719r4d72c1d5tcf793aca5c781401@mail.gmail.com> In-Reply-To: <9ab217670612190719r4d72c1d5tcf793aca5c781401@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Koen Martens , freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 28 Jan 2007 05:31:52 -0000 At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the following: > 2006/12/19, Koen Martens : >> Hi All, >> >> I was wondering, if something like a unique hardware identification >> would be possible on FreeBSD. >> >> I'd like a machine to authenticate to a server, for which it will >> need a unique identification. Problem is, it should be generated >> automatically and not easy to fake / detect without already having >> root access to the box. >> >> I'm thinking of something like combining serial numbers from >> CPU/disks for example, but there does not seem to be a clear way to >> obtain these (not all cpu's even have a serial number in there). >> >> I am just inquiring if someone on this list has an idea that might >> help with this problem. >> >> Gr, >> >> Koen > > Hey Koen, > > I know a lot of people / companies use the MAC address of a given > interface for this purpose, but it's not generally very useful since > most interfaces will allow you to set your own MAC address. > > Something you could use instead is a one-wire device, attached to the > motherboard (if it has a header for it). If the motherboard does not, > you can get LCDs from e.g. CrystalFontz that provide an interface to > such devices. The Dallas one-wire thermometers have a unique 64-bit > identifier on them, however this is only really useful if you have the > ability to control the hardware platform. > > If you are attempting to identify a specific hardware platform (e.g. a > standard set of motherboards and devices), you can enumerate devices > and device IDs on the PCI bus, creating some sort of hash of those. > > In the end, with the client controlling the hardware, client-side > security and validation is rather difficult. Even hacking the kernel > to only run signed binaries is going to be difficult to keep secure, > even keeping the key in some hardware secured storage, shipping the > system without a debugger or symbols, and controlling the hardware. > > Thank you, media, for blowing the Pentium III CPUID feature up into > something horrible. Uniquely identifiable hardware is very useful when > licensing :\. > > Regarding your questions, the serial number of the hard drive is > usually not too difficult to figure out. Take a look at atacontrol(8), > for instance: > > dho# atacontrol cap ad4 > > Protocol Serial ATA II > device model WDC WD1600JS-75NCB2 > serial number WD-WCANM3753524 > > The serial number should be unique. camcontrol(8) can probably give > you similar information for SCSI disks. > > Hope this is of some use. I'd be interested in seeing what others are doing. > > Kind regards, > > Devon H. O'Dell > _______________________________________________ > 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 had this very question myself. Here's what I've done: 1) Use a USB Flash Drive as a hardware dongle. These devices have a vendor id, product id, and a serial number that is garunteed to be unique. 2) Get the Link Layer Address off all the network interfaces in the system. 3) Get the model, serial, and firmware revision off the first harddrive in the system. 4) Using the sysctl(3) interface, I found some undocumented stuff that let's you enumerate the pnp devices in the system. Well, the kernel tells you what they are. -- Daniel Rudy From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 09:37:58 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35C6E16A405; Sun, 28 Jan 2007 09:37:58 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (palm.hoeg.nl [83.98.131.212]) by mx1.freebsd.org (Postfix) with ESMTP id EE0F313C49D; Sun, 28 Jan 2007 09:37:57 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 76CEC1CC78; Sun, 28 Jan 2007 10:37:56 +0100 (CET) Date: Sun, 28 Jan 2007 10:37:56 +0100 From: Ed Schouten To: "M. Warner Losh" Message-ID: <20070128093756.GS64263@hoeg.nl> References: <20070124113858.GG64263@hoeg.nl> <200701241254.51900.hselasky@c2i.net> <20070127.192204.-862243883.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MhZKc0eW5aU1X1vX" Content-Disposition: inline In-Reply-To: <20070127.192204.-862243883.imp@bsdimp.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Mailman-Approved-At: Sun, 28 Jan 2007 12:32:17 +0000 Cc: FreeBSD Hackers , freebsd-stable@freebsd.org, pietro.cerutti@gmail.com, hselasky@c2i.net Subject: Re: atacontrol kernel crash (atausb?) 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, 28 Jan 2007 09:37:58 -0000 --MhZKc0eW5aU1X1vX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * M. Warner Losh wrote: > In message: <200701241254.51900.hselasky@c2i.net> > Hans Petter Selasky writes: > : Instead of having all these quirks, isn't it possible that the SCSI lay= er can=20 > : auto-probe this? >=20 > The short answer is no. There's no reliable way to tell if a device > supports a given scsi command, and some devices freak out (lock up) > when sent one. Well, in one of the scenario's there is. USB UFI devices never support synchronize. --=20 Ed Schouten WWW: http://g-rave.nl/ --MhZKc0eW5aU1X1vX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFvG7052SDGA2eCwURAoe7AJkBVMPbaliNAzvM3M7dW4ucRtAoZwCfbNc5 +jjy6M2SJeWB8/RxES3XEOc= =euv/ -----END PGP SIGNATURE----- --MhZKc0eW5aU1X1vX-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 12:48:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BE63E16A404 for ; Sun, 28 Jan 2007 12:48:09 +0000 (UTC) (envelope-from deuza42@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 5AF0E13C48D for ; Sun, 28 Jan 2007 12:48:09 +0000 (UTC) (envelope-from deuza42@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1643522nfc for ; Sun, 28 Jan 2007 04:48:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=uhKu2fJ6J3MI1qe4Qn7IoEBxBxazMBuhWDnvx8jI5GleirU5H3e2jYzq4qUcT4hdcV7S176Lx4jknUBErGcVEPdaFGL6h43eK8KGEqJTsTtsqx1g91SZvrLDgSGY6WGQcWzAWhhRJiIP31JMg8VOO5Qpb3UVItC6UA4D6M3uwYA= Received: by 10.82.148.7 with SMTP id v7mr508872bud.1169988488062; Sun, 28 Jan 2007 04:48:08 -0800 (PST) Received: by 10.82.183.13 with HTTP; Sun, 28 Jan 2007 04:48:08 -0800 (PST) Message-ID: Date: Sun, 28 Jan 2007 13:48:08 +0100 From: DeuZa To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Local mirror 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, 28 Jan 2007 12:48:11 -0000 Hi the list, I post this in questions@ without result :( Maybe here ? :) For 3 box I want make a "little" FTP mirror : I have activate anonymous account behind a NAT, in private adress so .. No problem about secu All the 2 hours I running a little script for synch this directory : ROOT=/var/ftp/pub/FreeBSD $ROOT/tools (for installation) $ROOT/ports/distfiles/ (53Go All the last ports sources ?) $ROOT/ports/i386/packages-6.2-release/ (15Go All the last package for 6.2-RELEASE ?) $ROOT/ports/i386/packages-6-stable/ (20Go All the last packages for 6-STABLE) $ROOT/releases/i386/6.2-RELEASE (282Mo For make installation about this server) $ROOT/releases/i386/ISO-IMAGES/6.2 (1,4Go To have some my hands :) My questions is for mirror-master :) What's your politic about distfiles/ packages*/ directory ? How many time about retention ? We're ok if my 3 boxes are in /etc/make.conf : MASTER_SITE_BACKUP?= ftp://localserver/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ MASTER_SITE_OVERRIDE?=${MASTER_SITE_BACKUP} I using portinstall/portupgrade In the /usr/local/etc/pkgtools.conf I have add : USE_PKGS = [ '*', ] All is fine ? How indicate a package server ? Thanks for your help 2A From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 13:02:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E87B16A402 for ; Sun, 28 Jan 2007 13:02:17 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 518F513C441 for ; Sun, 28 Jan 2007 13:02:17 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (unknown [89.53.125.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 6202412882A for ; Sun, 28 Jan 2007 13:30:02 +0100 (CET) Received: from [192.168.18.3] (unknown [192.168.18.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 73F372E56B for ; Sun, 28 Jan 2007 13:29:48 +0100 (CET) Message-ID: <45BC973C.9040703@vwsoft.com> Date: Sun, 28 Jan 2007 13:29:48 +0100 From: Volker User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Subject: installing fbsd from foreign system 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, 28 Jan 2007 13:02:17 -0000 Hi hackers! Probably I will be proud to have the chance to support one of Europe's major players in root server hosting for deploying FreeBSD as a target platform for their customers. I need to find a way to integrate the FreeBSD install process into their current deployment system. Currently their install process is running from a Linux install system which does the partitioning, make_fs etc. I found several options to integrate: 1) install a FAT partition, copy a bootable install system in it, boot (bsdboot) an install kernel from FAT partition and begin (unattended) installation (including fdisk, labeling, make_fs'ing). Any thoughts on that? I think this might be the best option. 2) fdisk'ing, labeling and make fs from the Linux system if there are any ported label + fs tools for Linux available - are they? 3) create an ext2 partition and copy the fbsd install system into it and boot from there to begin install process (same as 1 except running from ext2fs). Does a FreeBSD kernel support booting from ext2fs (using mdfs for root-fs)? If so, how? Any better thoughts? Any hints on how to proceed with one of the 3 options? PXE or anything else is not an option. I need to integrate the install process into an existing deployment system. I suspect to be the UFS problem to be the biggest one when it comes to deal with that from a running Linux system. Also as anything needs to run unattended, how do I set FreeBSD to try DHCP on any local interface the kernel can find? Greetings, Volker From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 14:29:47 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9039716A403 for ; Sun, 28 Jan 2007 14:29:47 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.227]) by mx1.freebsd.org (Postfix) with ESMTP id 532C513C491 for ; Sun, 28 Jan 2007 14:29:47 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so1076047nzh for ; Sun, 28 Jan 2007 06:29:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=t3UsHyAGbGxdYOpkBjx8D2ezn6IQ6RDiyTlRPY3GGytwoh7L8RzNrHAQVqDLVPhbyoCYHlsH29kd5fRRSVWQp+OpukfxlGWAgVnepN0RcB+zIs2Y6wH+VuhH4OBnzEG/tvixi3n+pS1bklUCin8BVqvchox8NkjS5EEK9hU++HY= Received: by 10.114.205.1 with SMTP id c1mr206175wag.1169994586228; Sun, 28 Jan 2007 06:29:46 -0800 (PST) Received: by 10.114.111.17 with HTTP; Sun, 28 Jan 2007 06:29:46 -0800 (PST) Message-ID: <6eb82e0701280629jcbcfb82if73da80d8b3c421d@mail.gmail.com> Date: Sun, 28 Jan 2007 22:29:46 +0800 From: "Rong-en Fan" To: freebsd-hackers@freebsd.org In-Reply-To: <6eb82e0701271136n5538792eu31f464414e7dbaae@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0701271136n5538792eu31f464414e7dbaae@mail.gmail.com> Subject: Re: how to determine if we are building lib32 in Makefile? 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, 28 Jan 2007 14:29:47 -0000 On 1/28/07, Rong-en Fan wrote: > I'm working on wide character support in base's ncurses. For some > reason, I have to make lib/ncurses/ncursesw to include ncurses.h from > its object directory. However, current lib32 uses something like > > cc ... -I${LIB32TMP}/usr/includes ... -IFROM_NCURSES_MAKEFILE ... > > Right now, I have the following: > > .if ${.TARGET} == "installincludes" && !empty(${DESTDIR:M*/lib32/*}) > INCS= ${HEADERS} ${SRCHDRS} > INCSLINKS= curses.h ${INCLUDEDIR}/ncurses.h > .endif > > It works, but it's really ugly. Is there any other way to do this? Oops, it's wrong. Now I have "-DWORLD32" in LIB32MAKE and the following lines in lib/ncurses/Makefile .if !defined(WORLD32) INCS= ${HEADERS} ${SRCHDRS} INCSLINKS= curses.h ${INCLUDEDIR}/ncurses.h .endif While make universe is still running, but I have amd64, i386, pc98 work and on my -current i386 box. The resulting world works well (tested by mutt). I'm not sure if this is the best way to handle this. I noticed that Dragonfly has something like # include files are not installed when building bootstrap programs .if !defined(BOOTSTRAPPING) realinstall: installincludes .ORDER: beforeinstall installincludes .endif in bsd.incs.mk. For ncurses, since the include path for 32-bit includes are specified in LIB32POSTFLAGS, which is part of ${CC}. When building ncurses + ncursesw, I need different versions of ncurses.h (for runtime, it is not the case).The only way to get them build in lib32 is NOT to install ncurses.h in lib32/usr/include. Any comments or suggestions are welcome :) Regards, Rong-En Fan From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 15:22:56 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0E3916A400 for ; Sun, 28 Jan 2007 15:22:56 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 2F80013C46B for ; Sun, 28 Jan 2007 15:22:55 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (jqdovs@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l0SFMnTr093333; Sun, 28 Jan 2007 16:22:55 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l0SFMnZu093332; Sun, 28 Jan 2007 16:22:49 +0100 (CET) (envelope-from olli) Date: Sun, 28 Jan 2007 16:22:49 +0100 (CET) Message-Id: <200701281522.l0SFMnZu093332@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, volker@vwsoft.com In-Reply-To: <45BC973C.9040703@vwsoft.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sun, 28 Jan 2007 16:22:55 +0100 (CET) X-Mailman-Approved-At: Sun, 28 Jan 2007 15:48:25 +0000 Cc: Subject: Re: installing fbsd from foreign system 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, 28 Jan 2007 15:22:56 -0000 Volker wrote: > Probably I will be proud to have the chance to support one of > Europe's major players in root server hosting for deploying FreeBSD > as a target platform for their customers. We've done things like that before, too. > I need to find a way to integrate the FreeBSD install process into > their current deployment system. Currently their install process is > running from a Linux install system which does the partitioning, > make_fs etc. > > I found several options to integrate: > > 1) install a FAT partition, copy a bootable install system in it, > boot (bsdboot) an install kernel from FAT partition and begin > (unattended) installation (including fdisk, labeling, make_fs'ing). > > Any thoughts on that? I think this might be the best option. I don't think you can boot a FreeBSD system from a FAT file system. > 2) fdisk'ing, labeling and make fs from the Linux system if there > are any ported label + fs tools for Linux available - are they? No. > 3) create an ext2 partition and copy the fbsd install system into it > and boot from there to begin install process (same as 1 except > running from ext2fs). Does a FreeBSD kernel support booting from > ext2fs (using mdfs for root-fs)? If so, how? That _might_ work, but I haven't tried it myself. > Any better thoughts? Any hints on how to proceed with one of the 3 > options? PXE or anything else is not an option. I need to integrate > the install process into an existing deployment system. PXE would really be the cleanest and easiest way, and it's also very easy to maintain. If you can't do that, maybe you need to re-think your existing deplayment process and make it more flexible ...? Another possibility is to prepare a boot image, i.e. a file containing boot sector and a UFS root partition with wverything needed for bootstrapping (/boot/loader etc., kernel, base system). It doesn't have to cover the whole disk, it should be just large enough for a base system and some support software. It should contain a script which configures the rest of the disk when it's booted (e.g. set up remaining disk space, fetch packages from the net, whatever). >From within your Linux deployment process, simply copy the image to the beginning of the hard disk, then reboot. > I suspect to be the UFS problem to be the biggest one when it comes > to deal with that from a running Linux system. Right, Linux support for UFS is weak, not to mention UFS2. > Also as anything needs to run unattended, how do I set FreeBSD to > try DHCP on any local interface the kernel can find? The FreeBSD Handbook covers that topic (chapter 25.5). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing."         -- Mother Teresa From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 17:12:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6305816A402 for ; Sun, 28 Jan 2007 17:12:46 +0000 (UTC) (envelope-from jon.passki@hursk.com) Received: from davie.textdrive.com (davie.textdrive.com [207.7.108.101]) by mx1.freebsd.org (Postfix) with ESMTP id 474DD13C467 for ; Sun, 28 Jan 2007 17:12:46 +0000 (UTC) (envelope-from jon.passki@hursk.com) Received: from [10.1.2.34] (v-209-98-139-33.mn.visi.com [209.98.139.33]) by davie.textdrive.com (Postfix) with ESMTP id C3FE8BF2A1; Sun, 28 Jan 2007 16:39:49 +0000 (GMT) In-Reply-To: <45BC3624.3000608@pacbell.net> References: <4587F6F1.1050000@metro.cx> <9ab217670612190719r4d72c1d5tcf793aca5c781401@mail.gmail.com> <45BC3624.3000608@pacbell.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3B777B32-AB3A-4244-BBE1-9E11B287D78B@hursk.com> Content-Transfer-Encoding: 7bit From: Jon Passki Date: Sun, 28 Jan 2007 10:39:36 -0600 To: Daniel Rudy X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.3) Cc: Koen Martens , freebsd-hackers@freebsd.org, "Devon H. O'Dell" Subject: Re: unique hardware identification 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, 28 Jan 2007 17:12:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 27, 2007, at 23:35 , Daniel Rudy wrote: > At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the > following: >> 2006/12/19, Koen Martens : >>> Hi All, >>> >>> I was wondering, if something like a unique hardware identification >>> would be possible on FreeBSD. [snip] If the machine is a PXE-compliant device [2], it should have a GUID/ UUID [1] available. This can be exposed by sysutil/hal [3] via the smbios.system.uuid field. The sysutil/hal port, though, requires a decent amount of dependencies. You might want to give the pkg install a try first. (I happened to have a lot of those ports installed, so it was not an issue for me.) # dbus-daemon --system # hald --verbose=yes 16:39:24.418 [I] hald.c:469: hal 0.5.8 16:39:24.418 [I] hald.c:478: Will daemonize 16:39:24.418 [I] hald.c:479: Becoming a daemon # hal-get-property --udi /org/freedesktop/Hal/devices/computer --key smbios.system.uuid 64837263-8462-7493-1212-FFFFFFFFFFFF Cheers, Jon [1] http://en.wikipedia.org/wiki/Globally_Unique_Identifier [2] http://en.wikipedia.org/wiki/Preboot_Execution_Environment [3] http://www.freshports.org/sysutils/hal/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFvNHRZpJsLIS+QSIRAvygAJwMqBHhdPhCwkaAnEo/MSBsbeig+QCeMc+c HR4Wcvmt4kcZyaD1S76Hby4= =YQQw -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 17:35:37 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B702616A404 for ; Sun, 28 Jan 2007 17:35:37 +0000 (UTC) (envelope-from lists-freebsd-hackers@biaix.org) Received: from grummit.biaix.org (86.Red-213-97-212.staticIP.rima-tde.net [213.97.212.86]) by mx1.freebsd.org (Postfix) with SMTP id 3052413C481 for ; Sun, 28 Jan 2007 17:35:36 +0000 (UTC) (envelope-from lists-freebsd-hackers@biaix.org) Received: (qmail 28266 invoked by uid 1012); 28 Jan 2007 17:07:36 -0000 Date: Sun, 28 Jan 2007 18:07:36 +0100 From: Joan Picanyol i Puig To: freebsd-hackers@freebsd.org Message-ID: <20070128170736.GA28157@grummit.biaix.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <45BC973C.9040703@vwsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45BC973C.9040703@vwsoft.com> User-Agent: Mutt/1.5.11 Subject: Re: installing fbsd from foreign system 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, 28 Jan 2007 17:35:37 -0000 * Volker [20070128 14:03]: > I need to find a way to integrate the FreeBSD install process into > their current deployment system. Currently their install process is > running from a Linux install system which does the partitioning, > make_fs etc. Sounds like you could use a depenguinator... http://www.daemonology.net/depenguinator/ qvb -- pica From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 18:11:42 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FDE816A418 for ; Sun, 28 Jan 2007 18:11:42 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 4A16313C4DB for ; Sun, 28 Jan 2007 18:11:34 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0SIBXLO020158; Mon, 29 Jan 2007 05:11:33 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0SIBWof020157; Mon, 29 Jan 2007 05:11:32 +1100 (EST) (envelope-from peter) Date: Mon, 29 Jan 2007 05:11:32 +1100 From: Peter Jeremy To: Jon Passki Message-ID: <20070128181132.GR927@turion.vk2pj.dyndns.org> References: <4587F6F1.1050000@metro.cx> <9ab217670612190719r4d72c1d5tcf793aca5c781401@mail.gmail.com> <45BC3624.3000608@pacbell.net> <3B777B32-AB3A-4244-BBE1-9E11B287D78B@hursk.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0z5c7mBtSy1wdr4F" Content-Disposition: inline In-Reply-To: <3B777B32-AB3A-4244-BBE1-9E11B287D78B@hursk.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Koen Martens , freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 28 Jan 2007 18:11:42 -0000 --0z5c7mBtSy1wdr4F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: >If the machine is a PXE-compliant device [2], it should have a GUID/=20 >UUID [1] available. This can be exposed by sysutil/hal [3] via the =20 >smbios.system.uuid field. You can also get it via kenv(8) without needing any ports: # kenv smbios.system.uuid 9F345F4F-BEFC-D431-1340-61235A56DEF9 --=20 Peter Jeremy --0z5c7mBtSy1wdr4F Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFvOdU/opHv/APuIcRAhxpAKCrSCMdivtPRCrnM9pp8vVrOyDi8wCgkC0T d9RNF+1/BNBGzLrd30t4DXw= =/apc -----END PGP SIGNATURE----- --0z5c7mBtSy1wdr4F-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 28 16:33:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA93F16A404 for ; Sun, 28 Jan 2007 16:33:20 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4008613C49D for ; Sun, 28 Jan 2007 16:33:20 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by postfix1-g20.free.fr (Postfix) with ESMTP id B8DB688FD0C for ; Sun, 28 Jan 2007 17:06:33 +0100 (CET) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp5-g19.free.fr (Postfix) with ESMTP id 82C1027BAF for ; Sun, 28 Jan 2007 17:06:32 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id l0SG6QRs025886; Sun, 28 Jan 2007 17:06:30 +0100 (CET) From: Thierry Herbelot To: freebsd-hackers@freebsd.org Date: Sun, 28 Jan 2007 17:06:17 +0100 User-Agent: KMail/1.9.5 References: <200701281522.l0SFMnZu093332@lurza.secnetix.de> In-Reply-To: <200701281522.l0SFMnZu093332@lurza.secnetix.de> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200701281706.19382.thierry@herbelot.com> X-Mailman-Approved-At: Sun, 28 Jan 2007 19:00:44 +0000 Cc: volker@vwsoft.com Subject: Re: installing fbsd from foreign system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2007 16:33:20 -0000 Le Sunday 28 January 2007 16:22, Oliver Fromme a écrit : > Another possibility is to prepare a boot image, i.e. a file > containing boot sector and a UFS root partition with > wverything needed for bootstrapping (/boot/loader etc., > kernel, base system). It doesn't have to cover the whole > disk, it should be just large enough for a base system and > some support software. It should contain a script which > configures the rest of the disk when it's booted (e.g. > set up remaining disk space, fetch packages from the net, > whatever). > > >From within your Linux deployment process, simply copy > > the image to the beginning of the hard disk, then reboot. > Oone good *starting point* is the depenguinator (http://www.daemonology.net/depenguinator/), which I used some time ago. There are rough edges, but at least, it gives a way to convert a PC running some version of Linux to FreeBSD. (in my experience, I had to resort to manual tweakings to get the final BSD to run). TfH -- Internet users, on the other hand, are perhaps not dealt with harshly enough; ultimately, the only way to secure the Internet is to ensure that these users secure their systems. Harvard Law Review, june06 ("immunizing the internet") From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 29 00:29:41 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1185516A404 for ; Mon, 29 Jan 2007 00:29:41 +0000 (UTC) (envelope-from bckno@hotmail.com) Received: from bay0-omc2-s40.bay0.hotmail.com (bay0-omc2-s40.bay0.hotmail.com [65.54.246.176]) by mx1.freebsd.org (Postfix) with ESMTP id F1DAD13C47E for ; Mon, 29 Jan 2007 00:29:40 +0000 (UTC) (envelope-from bckno@hotmail.com) Received: from hotmail.com ([65.54.229.17]) by bay0-omc2-s40.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sun, 28 Jan 2007 16:17:41 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 28 Jan 2007 16:17:41 -0800 Message-ID: Received: from 65.54.229.220 by by110fd.bay110.hotmail.msn.com with HTTP; Mon, 29 Jan 2007 00:17:39 GMT X-Originating-IP: [189.140.140.63] X-Originating-Email: [bckno@hotmail.com] X-Sender: bckno@hotmail.com In-Reply-To: <20070128120039.E125916A4F6@hub.freebsd.org> From: "Hugo Alfredo Cano Bravo" To: freebsd-hackers@freebsd.org Date: Mon, 29 Jan 2007 00:17:39 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 29 Jan 2007 00:17:41.0402 (UTC) FILETIME=[E3E617A0:01C7433A] Subject: RE: freebsd-hackers Digest, Vol 200, Issue 7 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, 29 Jan 2007 00:29:41 -0000 I want to be a member. What can I do.? >From: freebsd-hackers-request@freebsd.org >Reply-To: freebsd-hackers@freebsd.org >To: freebsd-hackers@freebsd.org >Subject: freebsd-hackers Digest, Vol 200, Issue 7 >Date: Sun, 28 Jan 2007 12:00:39 +0000 (UTC) > >Send freebsd-hackers mailing list submissions to > freebsd-hackers@freebsd.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >or, via email, send a message with subject or body 'help' to > freebsd-hackers-request@freebsd.org > >You can reach the person managing the list at > freebsd-hackers-owner@freebsd.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of freebsd-hackers digest..." > > >Today's Topics: > > 1. Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN > controller (Gilbert Cao) > 2. Review request: new OMNIKEY CardMan 4040 driver > (Daniel Roethlisberger) > 3. sysctl(3) interface (Daniel Rudy) > 4. how to determine if we are building lib32 in Makefile? > (Rong-en Fan) > 5. Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN > controller (Sam Fourman Jr.) > 6. Re: atacontrol kernel crash (atausb?) (M. Warner Losh) > 7. Re: unique hardware identification (Daniel Rudy) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Sat, 27 Jan 2007 11:19:00 +0100 >From: Gilbert Cao >Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN > controller >To: Benjamin Close >Cc: Massimo Lusetti , Florent Thoumie > , freebsd-hackers@freebsd.org, > freebsd-drivers@freebsd.org, Attilio Rao , > damien.bergamini@free.fr, sam@freebsd.org, gabor@freebsd.org, Max > Laier >Message-ID: <20070127101900.GB1099@bsdmon.com> >Content-Type: text/plain; charset="us-ascii" > >On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: > > Hi Gilbert, > > Thanks for the custom version. I've integrated the changes into the > > driver I'm working on. > > For those wanting to test out the driver which is now fully up to date > > with all change from NetBSD & OpenBSD - and has a few minor improvements > > over them, grab it from: > > > > http://www.clearchain.com/~benjsc/download/ > > > > File is: 20070125-wpi-freebsd.tar.gz > > > > Full instructions on how to build / install the driver are in the README > > in the tar file. > > > > This should work both under -current and 6.2-Stable now. > > > > Info about the driver and what's working/broken can be found at: > > > > http://www.clearchain.com/wiki/wpi > > > > Cheers, > > Benjamin > >I have tried the new 20070125 version. >However, I did not manage to make work. At least, it compiles. >I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. >wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. > >When, I "kldload if_wpi", here is a small sample of /var/log/messages > >Jan 27 10:30:39 vaio kernel: wpi0: mem >0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 >Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory >properly. >Jan 27 10:30:39 vaio last message repeated 6 times >Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a >Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] >Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: >Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: >Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image >wpi_fw >Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' >Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image >wpi_fw >Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' >Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware image >wpi_fw >Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image 'wpi_fw' > >In kldstat, both modules are loaded. >Then, I have "kldunload if_wpi" (and if_wpi seems to be reload, >automatically, I don't know why). Same problem, it seems that wpi_fw >could not be load (found ?). > >As a result, no AP is "associated". > > >After a fresh reboot, I have reinstall the custom 20070121 version of >mine, and all returns OK. >Another strange thing: when "kldload if_wpi" with 20070121 version, and >then kldstat, I don't see "wpi_ucode". It seems that wpi_ucode.ko does >not need to be loaded, in my case. >My wpi_ucode.ko lies in /boot/modules > >After another fresh reboot, I first moved wpi_ucode.ko to another place. >When I "kldload if_wpi", I got the following message: > >Jan 27 09:47:16 vaio kernel: wpi0: mem >0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 >Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory >properly. >Jan 27 09:47:16 vaio last message repeated 6 times >Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a >Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] >Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps >24Mbps 36Mbps 48Mbps 54Mbps >Jan 27 09:47:16 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >Jan 27 09:47:16 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >Jan 27 09:47:16 vaio kernel: firmware_get: failed to load firmware image >wpi_ucode >Jan 27 09:47:16 vaio kernel: wpi0: could not load firmware image >'wpi_ucode' > >So, it seems that wpi_ucode.ko have to lied in my /boot/modules (the >place where I have also put if_wpi 20070121 version), even if it is not >loaded. > >-- >-------------------------------- > (hika) Gilbert Cao > http://www.miaouirc.com > - MiaouIRC Project 2002-2003 > http://www.bsdmon.com > - The BSD DMON Power to serve > IRC : #miaule at IRCNET Network >-------------------------------- >-------------- next part -------------- >A non-text attachment was scrubbed... >Name: not available >Type: application/pgp-signature >Size: 187 bytes >Desc: not available >Url : >http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20070127/db655aef/attachment-0001.pgp > >------------------------------ > >Message: 2 >Date: Sat, 27 Jan 2007 14:53:59 +0100 >From: Daniel Roethlisberger >Subject: Review request: new OMNIKEY CardMan 4040 driver >To: freebsd-hackers@freebsd.org >Message-ID: <20070127135359.GA2167@dragon.roe.ch> >Content-Type: text/plain; charset=us-ascii > >I've already tried -drivers, but got no answers so far, so I am trying >here. > >I'm looking for source code review or early testers for my new OMNIKEY >CardMan 4040 `cmx' driver (pccard smartcard reader). It seems to work, >but there are some areas I am unsure about, especially the mutex, >callout and msleep interaction when detaching. > >Here is a diff against RELENG_6_1: > > http://dragon.roe.ch/~roe/cmx/cmx-6.1-20070124.diff.gz > >There's no manual page yet, but the driver itself should be complete. >I can make the code available in other forms than a diff vs 6.1 if >desired. > >Thanks, >Dan > >-- >Daniel Roethlisberger > > >------------------------------ > >Message: 3 >Date: Sat, 27 Jan 2007 07:42:14 -0800 >From: Daniel Rudy >Subject: sysctl(3) interface >To: freebsd-hackers@freebsd.org >Message-ID: <45BB72D6.9070809@pacbell.net> >Content-Type: text/plain; charset=ISO-8859-1 > > >Hello List, > >I've been taking apart and analyzing the sysctl(8) program to gain a >better insight into how to use the sysctl(3) interface. Adding some >debugging code to the program in strategic locations, this is what I >have as an output: > >debug: name: dev >debug: all: oid: 0 2 440 >debug: name: dev.nexus.%parent >debug: oid: 440 912 913 >debug: all: oid: 0 2 440 912 913 >debug: name: dev.nexus.0.%desc >debug: oid: 440 912 914 915 >debug: all: oid: 0 2 440 912 914 915 >debug: name: dev.nexus.0.%driver >debug: oid: 440 912 914 916 >debug: value: nexusdev.nexus.0.%driver: nexus >debug: all: oid: 0 2 440 912 914 916 >debug: name: dev.nexus.0.%location >debug: oid: 440 912 914 917 >debug: all: oid: 0 2 440 912 914 917 >debug: name: dev.nexus.0.%pnpinfo >debug: oid: 440 912 914 918 >debug: all: oid: 0 2 440 912 914 918 >debug: name: dev.nexus.0.%parent >debug: oid: 440 912 914 919 >debug: value: root0dev.nexus.0.%parent: root0 >debug: all: oid: 0 2 440 912 914 919 >debug: name: dev.acpi.%parent >debug: oid: 440 920 921 >debug: all: oid: 0 2 440 920 921 >debug: name: dev.acpi.0.%desc >debug: oid: 440 920 922 923 >debug: value: AMIINT dev.acpi.0.%desc: AMIINT >debug: all: oid: 0 2 440 920 922 923 >debug: name: dev.acpi.0.%driver >debug: oid: 440 920 922 924 >debug: value: acpidev.acpi.0.%driver: acpi >debug: all: oid: 0 2 440 920 922 924 >debug: name: dev.acpi.0.%location >debug: oid: 440 920 922 925 >debug: all: oid: 0 2 440 920 922 925 >debug: name: dev.acpi.0.%pnpinfo >debug: oid: 440 920 922 926 > >It's using an oid of 0 and 2 to get something, then it comes up with 440 >and then a sequence of numbers that are incrementing in a peculiar >pattern. I went looking and found that 0 is CTL_UNSPEC which according >to the comment is unused, but I see it here in the program output. > > >I also noticed this little blurb in the source code too: > >/* > * These functions uses a presently undocumented interface to the kernel > * to walk the tree and get the type so it can print the value. > * This interface is under work and consideration, and should probably > * be killed with a big axe by the first person who can find the time. > * (be aware though, that the proper interface isn't as obvious as it > * may seem, there are various conflicting requirements. > */ > >But I figure it's for the actual display of the various variables and >not for returning information about the dev tree. > > >So, my question is, how do I walk the tree to get the PnP info for all >the devices in the system? > >-- >Daniel Rudy > > >------------------------------ > >Message: 4 >Date: Sun, 28 Jan 2007 03:36:07 +0800 >From: "Rong-en Fan" >Subject: how to determine if we are building lib32 in Makefile? >To: freebsd-hackers@freebsd.org >Message-ID: > <6eb82e0701271136n5538792eu31f464414e7dbaae@mail.gmail.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >I'm working on wide character support in base's ncurses. For some >reason, I have to make lib/ncurses/ncursesw to include ncurses.h from >its object directory. However, current lib32 uses something like > >cc ... -I${LIB32TMP}/usr/includes ... -IFROM_NCURSES_MAKEFILE ... > >Right now, I have the following: > >.if ${.TARGET} == "installincludes" && !empty(${DESTDIR:M*/lib32/*}) > INCS= ${HEADERS} ${SRCHDRS} > INCSLINKS= curses.h ${INCLUDEDIR}/ncurses.h >.endif > >It works, but it's really ugly. Is there any other way to do this? > >Thanks, >Rong-En Fan > > >------------------------------ > >Message: 5 >Date: Sat, 27 Jan 2007 13:14:04 -0600 >From: "Sam Fourman Jr." >Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN > controller >To: "Gilbert Cao" >Cc: Massimo Lusetti , Benjamin Close > , Florent Thoumie , > freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org, Attilio Rao > , damien.bergamini@free.fr, sam@freebsd.org, > gabor@freebsd.org, Max Laier >Message-ID: > <11167f520701271114j66f82398h83c43885b9d25e12@mail.gmail.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >I can also confirm that i get the firmware_get: failed to load >firmware image wpi_fw on the >20070125 version. >I should note that I tried it on a fresh 6.2 RELEASE install. > >Sam Fourman Jr. > >On 1/27/07, Gilbert Cao wrote: > > On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: > > > Hi Gilbert, > > > Thanks for the custom version. I've integrated the changes into the > > > driver I'm working on. > > > For those wanting to test out the driver which is now fully up to date > > > with all change from NetBSD & OpenBSD - and has a few minor >improvements > > > over them, grab it from: > > > > > > http://www.clearchain.com/~benjsc/download/ > > > > > > File is: 20070125-wpi-freebsd.tar.gz > > > > > > Full instructions on how to build / install the driver are in the >README > > > in the tar file. > > > > > > This should work both under -current and 6.2-Stable now. > > > > > > Info about the driver and what's working/broken can be found at: > > > > > > http://www.clearchain.com/wiki/wpi > > > > > > Cheers, > > > Benjamin > > > > I have tried the new 20070125 version. > > However, I did not manage to make work. At least, it compiles. > > I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. > > wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. > > > > When, I "kldload if_wpi", here is a small sample of /var/log/messages > > > > Jan 27 10:30:39 vaio kernel: wpi0: mem >0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 > > Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory >properly. > > Jan 27 10:30:39 vaio last message repeated 6 times > > Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a > > Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] > > Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: > > Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: > > Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image >wpi_fw > > Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image >'wpi_fw' > > Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image >wpi_fw > > Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image >'wpi_fw' > > Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware image >wpi_fw > > Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image >'wpi_fw' > > > > In kldstat, both modules are loaded. > > Then, I have "kldunload if_wpi" (and if_wpi seems to be reload, > > automatically, I don't know why). Same problem, it seems that wpi_fw > > could not be load (found ?). > > > > As a result, no AP is "associated". > > > > > > After a fresh reboot, I have reinstall the custom 20070121 version of > > mine, and all returns OK. > > Another strange thing: when "kldload if_wpi" with 20070121 version, and > > then kldstat, I don't see "wpi_ucode". It seems that wpi_ucode.ko does > > not need to be loaded, in my case. > > My wpi_ucode.ko lies in /boot/modules > > > > After another fresh reboot, I first moved wpi_ucode.ko to another place. > > When I "kldload if_wpi", I got the following message: > > > > Jan 27 09:47:16 vaio kernel: wpi0: mem >0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 > > Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory >properly. > > Jan 27 09:47:16 vaio last message repeated 6 times > > Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a > > Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] > > Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps >24Mbps 36Mbps 48Mbps 54Mbps > > Jan 27 09:47:16 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > Jan 27 09:47:16 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > > Jan 27 09:47:16 vaio kernel: firmware_get: failed to load firmware image >wpi_ucode > > Jan 27 09:47:16 vaio kernel: wpi0: could not load firmware image >'wpi_ucode' > > > > So, it seems that wpi_ucode.ko have to lied in my /boot/modules (the > > place where I have also put if_wpi 20070121 version), even if it is not > > loaded. > > > > -- > > -------------------------------- > > (hika) Gilbert Cao > > http://www.miaouirc.com > > - MiaouIRC Project 2002-2003 > > http://www.bsdmon.com > > - The BSD DMON Power to serve > > IRC : #miaule at IRCNET Network > > -------------------------------- > > > > > > > > >------------------------------ > >Message: 6 >Date: Sat, 27 Jan 2007 19:22:04 -0700 (MST) >From: "M. Warner Losh" >Subject: Re: atacontrol kernel crash (atausb?) >To: hselasky@c2i.net >Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, > ed@fxq.nl, pietro.cerutti@gmail.com >Message-ID: <20070127.192204.-862243883.imp@bsdimp.com> >Content-Type: Text/Plain; charset=us-ascii > >In message: <200701241254.51900.hselasky@c2i.net> > Hans Petter Selasky writes: >: Instead of having all these quirks, isn't it possible that the SCSI layer >can >: auto-probe this? > >The short answer is no. There's no reliable way to tell if a device >supports a given scsi command, and some devices freak out (lock up) >when sent one. > >Warner > > >------------------------------ > >Message: 7 >Date: Sat, 27 Jan 2007 21:35:32 -0800 >From: Daniel Rudy >Subject: Re: unique hardware identification >To: "Devon H. O'Dell" >Cc: Koen Martens , freebsd-hackers@freebsd.org >Message-ID: <45BC3624.3000608@pacbell.net> >Content-Type: text/plain; charset=ISO-8859-1 > >At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the >following: > > 2006/12/19, Koen Martens : > >> Hi All, > >> > >> I was wondering, if something like a unique hardware identification > >> would be possible on FreeBSD. > >> > >> I'd like a machine to authenticate to a server, for which it will > >> need a unique identification. Problem is, it should be generated > >> automatically and not easy to fake / detect without already having > >> root access to the box. > >> > >> I'm thinking of something like combining serial numbers from > >> CPU/disks for example, but there does not seem to be a clear way to > >> obtain these (not all cpu's even have a serial number in there). > >> > >> I am just inquiring if someone on this list has an idea that might > >> help with this problem. > >> > >> Gr, > >> > >> Koen > > > > Hey Koen, > > > > I know a lot of people / companies use the MAC address of a given > > interface for this purpose, but it's not generally very useful since > > most interfaces will allow you to set your own MAC address. > > > > Something you could use instead is a one-wire device, attached to the > > motherboard (if it has a header for it). If the motherboard does not, > > you can get LCDs from e.g. CrystalFontz that provide an interface to > > such devices. The Dallas one-wire thermometers have a unique 64-bit > > identifier on them, however this is only really useful if you have the > > ability to control the hardware platform. > > > > If you are attempting to identify a specific hardware platform (e.g. a > > standard set of motherboards and devices), you can enumerate devices > > and device IDs on the PCI bus, creating some sort of hash of those. > > > > In the end, with the client controlling the hardware, client-side > > security and validation is rather difficult. Even hacking the kernel > > to only run signed binaries is going to be difficult to keep secure, > > even keeping the key in some hardware secured storage, shipping the > > system without a debugger or symbols, and controlling the hardware. > > > > Thank you, media, for blowing the Pentium III CPUID feature up into > > something horrible. Uniquely identifiable hardware is very useful when > > licensing :\. > > > > Regarding your questions, the serial number of the hard drive is > > usually not too difficult to figure out. Take a look at atacontrol(8), > > for instance: > > > > dho# atacontrol cap ad4 > > > > Protocol Serial ATA II > > device model WDC WD1600JS-75NCB2 > > serial number WD-WCANM3753524 > > > > The serial number should be unique. camcontrol(8) can probably give > > you similar information for SCSI disks. > > > > Hope this is of some use. I'd be interested in seeing what others are >doing. > > > > Kind regards, > > > > Devon H. O'Dell > > _______________________________________________ > > 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 had this very question myself. Here's what I've done: > >1) Use a USB Flash Drive as a hardware dongle. These devices have a >vendor id, product id, and a serial number that is garunteed to be unique. > >2) Get the Link Layer Address off all the network interfaces in the system. > >3) Get the model, serial, and firmware revision off the first harddrive >in the system. > >4) Using the sysctl(3) interface, I found some undocumented stuff that >let's you enumerate the pnp devices in the system. Well, the kernel >tells you what they are. > > >-- >Daniel Rudy > > >------------------------------ > >_______________________________________________ >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" > >End of freebsd-hackers Digest, Vol 200, Issue 7 >*********************************************** _________________________________________________________________ Visita MSN Latino Noticias: Todo lo que pasa en el mundo y en tu paín, ¡en tu idioma! http://latino.msn.com/noticias/ From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 29 01:09:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09F8016A402 for ; Mon, 29 Jan 2007 01:09:31 +0000 (UTC) (envelope-from joe@joeholden.co.uk) Received: from claire.ber.rewt.org.uk (claire.ber.rewt.org.uk [217.160.200.67]) by mx1.freebsd.org (Postfix) with ESMTP id BD87313C467 for ; Mon, 29 Jan 2007 01:09:30 +0000 (UTC) (envelope-from joe@joeholden.co.uk) Received: from localhost (localhost [127.0.0.1]) by claire.ber.rewt.org.uk (Postfix) with ESMTP id B25EBBBF7; Mon, 29 Jan 2007 00:44:19 +0000 (GMT) X-Virus-Scanned: amavisd-new at claire.ber.rewt.org.uk Received: from claire.ber.rewt.org.uk ([127.0.0.1]) by localhost (claire.ber.rewt.org.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MmRe+npJKRGD; Mon, 29 Jan 2007 00:44:13 +0000 (GMT) Received: from [195.28.169.201] (jwh.lon.rewt.org.uk [195.28.169.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by claire.ber.rewt.org.uk (Postfix) with ESMTP id B77D2BBE3; Mon, 29 Jan 2007 00:44:12 +0000 (GMT) Message-ID: <45BD435A.30407@joeholden.co.uk> Date: Mon, 29 Jan 2007 00:44:10 +0000 From: Joe Holden User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Hugo Alfredo Cano Bravo References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: freebsd-hackers Digest, Vol 200, Issue 7 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, 29 Jan 2007 01:09:31 -0000 Hugo Alfredo Cano Bravo wrote: > I want to be a member. > > What can I do.? > > > > http://lists.freebsd.org and please, don't top post! -- Thanks, Joe Holden Telephone: +44 (0) 207 100 9593 Email: joe@joeholden.co.uk Website: http://www.joeholden.co.uk IRC: raindance@Quakenet/#FreeBSD From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 29 03:09:43 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2FD1616A400 for ; Mon, 29 Jan 2007 03:09:43 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 3356913C48E for ; Mon, 29 Jan 2007 03:09:39 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.7/jtpda-5.4) with ESMTP id l0T19lag056409 ; Mon, 29 Jan 2007 02:09:58 +0100 (CET) X-Ids: 165 Received: by parthe.lpthe.jussieu.fr (Postfix, from userid 99) id CF78DA084C; Mon, 29 Jan 2007 02:09:55 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on parthe.lpthe.jussieu.fr X-Spam-Level: X-Spam-Status: No, score=-101.5 required=10.0 tests=AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.1.7 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 837E5A0090; Mon, 29 Jan 2007 02:09:53 +0100 (CET) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 7204C68; Mon, 29 Jan 2007 02:09:44 +0100 (CET) Date: Mon, 29 Jan 2007 02:09:44 +0100 From: Michel Talon To: freebsd-hackers@freebsd.org Message-ID: <20070129010944.GA78336@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.165]); Mon, 29 Jan 2007 02:09:58 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.5/2496/Sun Jan 28 13:32:31 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 45BD495B.002 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Mailman-Approved-At: Mon, 29 Jan 2007 04:40:11 +0000 Cc: Benjamin Close Subject: Re: Updated Driver for 3945ABG ... 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, 29 Jan 2007 03:09:43 -0000 Gilbert Cao wrote: > > I have put a custom version of mine from your last package here: > http://www.bsdmon.com/download/20070121-wpi-freebsd.tar.gz > > What I have mainly done is to make the package compile and work (for me > a least) on 6.2-RELEASE (and possibly other 6.x ?). This is to confirm that for me this above 20070121 driver works, while the driver from B. Close 20070125 does *not* work. In fact i have downloaded a lot of things using this driver, so in my experience it works *very* well. It even associates better with the access point than the Linux driver, which loses connection from time to time. My laptop is a Vaio VGN C1, and for reference i have added some dmesg stuff with the above two drivers. Both produce error messages, but one definitely works. This is with 20070121-wpi-freebsd on a Sony Vaio VGN-C1S (note that 20070125-wpi-freebsd does not work for me) rose# kldload if_wpi rose# dmesg ..... wpi0: mem 0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. .... pi0: Ethernet address: 00:18:de:ad:78:b1 wpi0: [GIANT-LOCKED] wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps rose# ifconfig wpi0 up rose# ifconfig ... wpi0: flags=8802 mtu 1500 ether 00:18:de:ad:78:b1 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 1 authmode OPEN privacy OFF txpowmax 100 bmiss 7 protmode CTS rose# dmesg ... pi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wpi0: fatal firmware error wpi0: configure command failed wpi0: could not configure device still running dhclient rose# dhclient wpi0 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 192.168.1.1 DHCPREQUEST on wpi0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.107 -- renewal in 43200 seconds. and it works perfectly OK for me. This is what 20070125-wpi-freebsd gives: an 28 00:47:49 kernel: wpi0: mem 0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 Jan 28 00:47:49 kernel: bus_dmamem_alloc failed to align memory properly. Jan 28 00:47:49 last message repeated 6 times Jan 28 00:47:49 kernel: wpi0: Ethernet address: 00:18:de:ad:78:b1 Jan 28 00:47:49 kernel: wpi0: 11a rates: Jan 28 00:47:49 kernel: wpi0: 11b rates: Jan 28 00:48:19 kernel: firmware_get: failed to load firmware image wpi_fw Jan 28 00:48:19 kernel: wpi0: could not load firmware image 'wpi_fw' Jan 28 00:49:12 kernel: firmware_get: failed to load firmware image wpi_fw Jan 28 00:49:12 kernel: wpi0: could not load firmware image 'wpi_fw' Jan 28 00:49:12 dhclient[1351]: send_packet: Network is down Jan 28 00:49:15 dhclient[1351]: send_packet: Network is down -- Michel TALON From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 29 10:06:04 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8216A16A404 for ; Mon, 29 Jan 2007 10:06:04 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from com1.ht-systems.ru (com1.ht-systems.ru [83.97.104.204]) by mx1.freebsd.org (Postfix) with ESMTP id 38AE813C461 for ; Mon, 29 Jan 2007 10:06:04 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [213.87.72.70] (helo=phonon.SpringDaemons.com) by com1.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1HBSvX-0001ld-NQ; Mon, 29 Jan 2007 12:35:53 +0300 Received: from localhost (localhost [IPv6:::1]) by phonon.SpringDaemons.com (Postfix) with SMTP id 053C811B36; Mon, 29 Jan 2007 12:43:56 +0300 (MSK) Date: Mon, 29 Jan 2007 12:43:51 +0300 From: Stanislav Sedov To: DeuZa Message-Id: <20070129124351.0f563d54.stas@FreeBSD.org> In-Reply-To: References: Organization: The FreeBSD Project X-Mailer: carrier-pigeon X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-ICQ: 208105021 X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__29_Jan_2007_12_43_51_+0300_wnV2wn5j4=rODjL7" X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona 1.6.0 X-Mailman-Approved-At: Mon, 29 Jan 2007 12:26:11 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Local mirror 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, 29 Jan 2007 10:06:04 -0000 --Signature=_Mon__29_Jan_2007_12_43_51_+0300_wnV2wn5j4=rODjL7 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Sun, 28 Jan 2007 13:48:08 +0100 DeuZa mentioned: > I using portinstall/portupgrade > In the /usr/local/etc/pkgtools.conf I have add : > > > USE_PKGS = [ > '*', > ] > > > All is fine ? How indicate a package server ? > You can specify a server to get packages from using PKG_SITES directive of portupgrade. Note, that you should mirror packages for this as well -- Stanislav Sedov ST4096-RIPE --Signature=_Mon__29_Jan_2007_12_43_51_+0300_wnV2wn5j4=rODjL7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFvcHbK/VZk+smlYERAuIlAJ4hax1DBdWiSeVI6maiSdBo2ORt7wCfXneT hc5mu0qNUHHNOoxpHKjBKtA= =LgCk -----END PGP SIGNATURE----- --Signature=_Mon__29_Jan_2007_12_43_51_+0300_wnV2wn5j4=rODjL7-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 29 15:49:23 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C677B16A403 for ; Mon, 29 Jan 2007 15:49:23 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 7AB3D13C494 for ; Mon, 29 Jan 2007 15:49:23 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 85F82EB459D for ; Mon, 29 Jan 2007 23:49:20 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id ewp3HbdMtTTG for ; Mon, 29 Jan 2007 23:49:04 +0800 (CST) Received: from [192.168.1.32] (unknown [61.51.109.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id B7272EB7875 for ; Mon, 29 Jan 2007 23:49:04 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:x-enigmail-version:content-type; b=KQZCx6s/XqPbJVfqMM/jbK6Dx3kQRNVs43xZu9AqAgRdDLXKA83uDuURckW3JD+/n Z91XMbL4J4OzRb7oqpWgw== Message-ID: <45BE1769.1080806@delphij.net> Date: Mon, 29 Jan 2007 23:48:57 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: freebsd-hackers X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigB6A8B176357085330151696C" Subject: Reading SPD information? 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, 29 Jan 2007 15:49:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB6A8B176357085330151696C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Just curious: is there any way to read RAM's SPD information on a running system? Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enigB6A8B176357085330151696C 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.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFvhdpOfuToMruuMARAw9lAKCIjyH24MAMX33xSM0oZtyIcBcpmQCfc6gL m0IjB/0m8sq9VvnItMgMXOY= =Kd0q -----END PGP SIGNATURE----- --------------enigB6A8B176357085330151696C-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 29 16:15:33 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4EACF16A400 for ; Mon, 29 Jan 2007 16:15:33 +0000 (UTC) (envelope-from david@madole.net) Received: from d.omd3.com (mx1.omd3.com [69.90.174.41]) by mx1.freebsd.org (Postfix) with ESMTP id 2FBB013C4BB for ; Mon, 29 Jan 2007 16:15:32 +0000 (UTC) (envelope-from david@madole.net) Received: from static-66-212-193-19.myeastern.com ([66.212.193.19] helo=david) by d.omd3.com with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.54) id 1HBYvA-000Ghk-Bv; Mon, 29 Jan 2007 10:59:52 -0500 Date: Mon, 29 Jan 2007 10:56:00 -0500 From: "David S. Madole" To: 'freebsd-hackers' X-Priority: 3 Organization: Optimized Micro Devices X-Mailer: Bynari Insight Connector 3.1.1-1128233 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <20070129161533.2FBB013C4BB@mx1.freebsd.org> Cc: 'LI Xin' Subject: RE: Reading SPD information? 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, 29 Jan 2007 16:15:33 -0000 > From LI Xin Monday, January 29, 2007 10:49 AM >=20 > Just curious: is there any way to read RAM's SPD information on a > running system? Yes, not only can you read them, on many systems you can write to them too. There is an unfinished program here that decodes and displays data for SDRA= Ms and has an example of reprogramming bytes: http://madole.net/spd/spd.c I used this to re-program some SDRAM after adding parity chips to them. Note that there is a write-protect pin on the DIMMs that motherboards are s= upposed to activate to prevent writing in a system (i.e. so that a virus do= es not trash your DIMMs) but none of the systems I have tested on actually = implement this. It's fairly easy to find the specs of the SPD contents with Google -- sorry= I don't have a direct reference handy. David From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 09:31:54 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F407116A402; Tue, 30 Jan 2007 09:31:53 +0000 (UTC) (envelope-from takawata@init-main.com) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.freebsd.org (Postfix) with ESMTP id 6E5A713C46B; Tue, 30 Jan 2007 09:31:51 +0000 (UTC) (envelope-from takawata@init-main.com) Received: from ns.init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.13.8/8.13.8) with ESMTP id l0U90kFA049949; Tue, 30 Jan 2007 18:00:46 +0900 (JST) (envelope-from takawata@ns.init-main.com) Message-Id: <200701300900.l0U90kFA049949@sana.init-main.com> To: freebsd-hackers@freebsd.org From: takawata@jp.freebsd.org Date: Tue, 30 Jan 2007 18:00:46 +0900 Sender: takawata@init-main.com Cc: nork@freebsd.org Subject: some symbols of libc may be resolved by RTLD internal entities. 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, 30 Jan 2007 09:31:54 -0000 Hi, It seems that some symbols in libc is resolved by libc entities which is linked with RTLD to implement it. % nm -D ld-elf.so.1 ... 000158ec T mmap 0000c4fc W mprotect 0000c4dc W munmap ... And running Flash9 with Symbol Versioning-aware Linux Plugin Wrapper shows that mmap cannot be overrided. mmap is called with strange argument. 4201 seamonkey-bin CALL mmap(0xffffffff,0x100000,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_FIXED|MAP_RENAME,0xffffffff,0,0,0x280875e4) But sometimes munmap can be hooked. Is this intended behavior that libc symbols in rtld is exported? And are there any way to stop exporting it? From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 14:19:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0343F16A405 for ; Tue, 30 Jan 2007 14:19:31 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id B68FA13C471 for ; Tue, 30 Jan 2007 14:19:28 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1962041wxc for ; Tue, 30 Jan 2007 06:19:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=JmlAtoFsoeVXawvutcmrMYlQzhD92jvIJTvJboSZLZkxbR5j0hXA15QSUM7fgrF3AbU/zYUKkJTER9vmma5yP0lqbmERa9sjbR/tMJq6TDUsT9NO60IcO4tZzNZ26DLqGGEufK7/SQm5PyLkuJ2YSs2EvBOloQBPIkoANfWN9Is= Received: by 10.90.27.15 with SMTP id a15mr1085613aga.1170166767770; Tue, 30 Jan 2007 06:19:27 -0800 (PST) Received: from kan.dnsalias.net ( [24.34.98.164]) by mx.google.com with ESMTP id 20sm9640426agd.2007.01.30.06.19.26; Tue, 30 Jan 2007 06:19:26 -0800 (PST) Date: Tue, 30 Jan 2007 09:19:21 -0500 From: Alexander Kabaev To: takawata@jp.freebsd.org Message-ID: <20070130091921.76335b35@kan.dnsalias.net> In-Reply-To: <200701300900.l0U90kFA049949@sana.init-main.com> References: <200701300900.l0U90kFA049949@sana.init-main.com> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_W5g5PTc83mm3EoINbX8hv_="; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-hackers@freebsd.org, nork@freebsd.org Subject: Re: some symbols of libc may be resolved by RTLD internal entities. 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, 30 Jan 2007 14:19:31 -0000 --Sig_W5g5PTc83mm3EoINbX8hv_= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 30 Jan 2007 18:00:46 +0900 takawata@jp.freebsd.org wrote: > Hi,=20 >=20 > It seems that some symbols in libc is resolved by libc entities > which is linked with RTLD to implement it. >=20 > % nm -D ld-elf.so.1 > ... > 000158ec T mmap > 0000c4fc W mprotect > 0000c4dc W munmap > ... It doesn't. rtld is a special beast and its symbols availability to user programs is controlled by a special code in rtld. Look up static func_ptr_type exports[] in rtld.c and see how it is used. --=20 Alexander Kabaev P.S. The proper way to control symbol visibility is to use version script file when linking rtld-elf.so.1 in order to force all unintended symbols to local scope. exports array is there for historical reasons. --Sig_W5g5PTc83mm3EoINbX8hv_= Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFv1PtQ6z1jMm+XZYRArQmAJ9UR7VjIop6Nkq5TMUJOQqyyYXFnwCeLcqD R+lm1xbsbs4tUpCjKOxGfSQ= =4sdY -----END PGP SIGNATURE----- --Sig_W5g5PTc83mm3EoINbX8hv_=-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 14:34:38 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 917BB16A408 for ; Tue, 30 Jan 2007 14:34:38 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: from hk2.uwaterloo.ca (hk2.uwaterloo.ca [129.97.47.5]) by mx1.freebsd.org (Postfix) with ESMTP id 71E7313C4B4 for ; Tue, 30 Jan 2007 14:34:38 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: from uwaterloo.ca (localhost.localdomain [127.0.0.1]) by hk2.uwaterloo.ca (Postfix) with SMTP id 26613101832 for ; Tue, 30 Jan 2007 09:02:27 -0500 (EST) Message-Id: <20070130140227.26613101832@hk2.uwaterloo.ca> Date: Tue, 30 Jan 2007 09:02:27 -0500 (EST) From: waldeck@gmx.de To: undisclosed-recipients:; X-Mailman-Approved-At: Tue, 30 Jan 2007 14:55:10 +0000 Subject: top delay value 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, 30 Jan 2007 14:34:38 -0000 Hello, An unprivileged user could waste all CPU time by setting a low delay value in top (interactive or via -s). Is there any possibility to deactivate this functionality without recompilation? There are other top implementations that use a "secure mode" configuration which avoids the setting of the delay value for unprivileged users. Thanks Dr. Markus Waldeck From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 15:21:42 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A55D16A400 for ; Tue, 30 Jan 2007 15:21:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id DCC8F13C494 for ; Tue, 30 Jan 2007 15:21:41 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (azwtcf@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l0UFLY3c055510; Tue, 30 Jan 2007 16:21:40 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l0UFLYgE055509; Tue, 30 Jan 2007 16:21:34 +0100 (CET) (envelope-from olli) Date: Tue, 30 Jan 2007 16:21:34 +0100 (CET) Message-Id: <200701301521.l0UFLYgE055509@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de In-Reply-To: <20070130140227.26613101832@hk2.uwaterloo.ca> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 30 Jan 2007 16:21:40 +0100 (CET) Cc: Subject: Re: top delay value X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2007 15:21:42 -0000 waldeck@gmx.de wrote: > An unprivileged user could waste all CPU time by setting a low delay > value in top (interactive or via -s). Well, an unprivileged user can achieve the same effect by typing "while :; do :; done". There are a thousand ways to waste CPU time, and there is no way to prevent a user from doing it. > There are other top implementations that use a "secure mode" configuration > which avoids the setting of the delay value for unprivileged users. Really? I don't think such a function has got anything to do with being more "secure". If you want to make top more secure, type "chmod 700 /usr/bin/top". Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Perl is worse than Python because people wanted it worse. -- Larry Wall From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 15:26:35 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A20316A401 for ; Tue, 30 Jan 2007 15:26:35 +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 CCD4913C461 for ; Tue, 30 Jan 2007 15:26:34 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.6/8.13.8) id l0UFQY77081483; Tue, 30 Jan 2007 09:26:34 -0600 (CST) (envelope-from dan) Date: Tue, 30 Jan 2007 09:26:34 -0600 From: Dan Nelson To: waldeck@gmx.de Message-ID: <20070130152633.GF19656@dan.emsphone.com> References: <20070130140227.26613101832@hk2.uwaterloo.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070130140227.26613101832@hk2.uwaterloo.ca> X-OS: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-hackers@freebsd.org Subject: Re: top delay value 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, 30 Jan 2007 15:26:35 -0000 In the last episode (Jan 30), waldeck@gmx.de said: > An unprivileged user could waste all CPU time by setting a low delay > value in top (interactive or via -s). Are you sure? In 6.2 at least, "s0" in interactive mode results in a 1-second delay, and "top -s0" prints top: warning: seconds delay should be positive -- using default .... What version of FreeBSD are you seeing this on? > Is there any possibility to deactivate this functionality without > recompilation? > > There are other top implementations that use a "secure mode" > configuration which avoids the setting of the delay value for > unprivileged users. Users can hog CPU by running "while true ; do done" or any number of other methods. That's what CPU limits are for :) -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 15:56:08 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D6D5A16A402 for ; Tue, 30 Jan 2007 15:56:08 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 7EC3B13C441 for ; Tue, 30 Jan 2007 15:56:08 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 96596 invoked by uid 1001); 30 Jan 2007 15:56:46 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Tue, 30 Jan 2007 10:56:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17855.27326.236882.38629@bhuda.mired.org> Date: Tue, 30 Jan 2007 10:56:46 -0500 To: waldeck@gmx.de In-Reply-To: <20070130140227.26613101832@hk2.uwaterloo.ca> References: <20070130140227.26613101832@hk2.uwaterloo.ca> 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.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: top delay value 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, 30 Jan 2007 15:56:08 -0000 In <20070130140227.26613101832@hk2.uwaterloo.ca>, waldeck@gmx.de typed: > An unprivileged user could waste all CPU time by setting a low delay value in top (interactive or via -s). No, they can't. Should they use the interactive facility to set the delay to 0 (you can't do that via the -s switch), then top will compete evenly with normal users processes until it accumulates enough CPU that the scheduler changes it's nice value. It then no longer competes with normal user processes for CPU. At that point, the CPU cyles it's "wasting" are mostly cycles that would have been "wasted" in an idle loop anyway. Generally (but not always), there's no real reason to care about such. > Is there any possibility to deactivate this functionality without recompilation? chmod 0 /usr/bin/top > There are other top implementations that use a "secure mode" configuration > which avoids the setting of the delay value for unprivileged users. There are *lots* of commands on the system that can be coerced into spinning on the CPU doing nothing, starting with /bin/sh. The correct place to deal with this issue is in the kernel scheduler, so you can do it once and for all. That said, there may be a use case where you want a top display to be available without the interactive commands being available, ala the "secure mode" you mention. That can be provided with a little work, depending on the exact goals. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 15:59:35 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 125FC16A404 for ; Tue, 30 Jan 2007 15:59:35 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.freebsd.org (Postfix) with ESMTP id D29AA13C467 for ; Tue, 30 Jan 2007 15:59:34 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from [10.0.0.4] (12-216-254-44.client.mchsi.com[12.216.254.44]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20070130155933m9200jir1qe>; Tue, 30 Jan 2007 15:59:34 +0000 Message-ID: <45BF6B65.1000105@math.missouri.edu> Date: Tue, 30 Jan 2007 09:59:33 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20070130140227.26613101832@hk2.uwaterloo.ca> <20070130152633.GF19656@dan.emsphone.com> In-Reply-To: <20070130152633.GF19656@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: top delay value 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, 30 Jan 2007 15:59:35 -0000 Dan Nelson wrote: > In the last episode (Jan 30), waldeck@gmx.de said: > >>An unprivileged user could waste all CPU time by setting a low delay >>value in top (interactive or via -s). > > > Are you sure? In 6.2 at least, "s0" in interactive mode results in a > 1-second delay, and "top -s0" prints > > top: warning: seconds delay should be positive -- using default > .... You can run "top -s0" as root (not that this negates your point in any way). Incidently, this is an excellent way to generate those "calcru going backwards" errors, at least in some recent versions of FreeBSD. Just run a highly threaded, CPU intensive job at the same time. I did this on SMP systems, so I don't know if it also does this on non-SMP systems. On versions of FreeBSD 5.x I was able to induce kernel panics, the likes of which produced useless core dumps, but this seems to have been fixed with more recent versions. Stephen From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 16:50:31 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE68516A485 for ; Tue, 30 Jan 2007 16:50:31 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 3C4EB13C461 for ; Tue, 30 Jan 2007 16:50:31 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: (qmail 14058 invoked by uid 0); 30 Jan 2007 16:23:50 -0000 Received: from 129.97.47.9 by www072.gmx.net with HTTP; Tue, 30 Jan 2007 17:23:50 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 30 Jan 2007 17:23:50 +0100 From: "Dr. Markus Waldeck" In-Reply-To: <200701301521.l0UFLYgE055509@lurza.secnetix.de> Message-ID: <20070130162350.126210@gmx.net> MIME-Version: 1.0 References: <200701301521.l0UFLYgE055509@lurza.secnetix.de> To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de, freebsd-hackers@FreeBSD.ORG X-Authenticated: #646368 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: top delay value 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, 30 Jan 2007 16:50:32 -0000 > Well, an unprivileged user can achieve the same effect by > typing "while :; do :; done". There are a thousand ways > to waste CPU time, and there is no way to prevent a user > >from doing it. It is not the same effect. You describe fork bombing. Many forked processes eat up the CPU. I could limit the number of process via :maxproc=100: \ in /etc/login.conf > If you want to make top more secure, type "chmod 700 /usr/bin/top". :-) -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 16:50:32 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3CE916A488 for ; Tue, 30 Jan 2007 16:50:31 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 464FD13C478 for ; Tue, 30 Jan 2007 16:50:31 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: (qmail 14058 invoked by uid 0); 30 Jan 2007 16:23:50 -0000 Received: from 129.97.47.9 by www072.gmx.net with HTTP; Tue, 30 Jan 2007 17:23:50 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 30 Jan 2007 17:23:50 +0100 From: "Dr. Markus Waldeck" In-Reply-To: <200701301521.l0UFLYgE055509@lurza.secnetix.de> Message-ID: <20070130162350.126210@gmx.net> MIME-Version: 1.0 References: <200701301521.l0UFLYgE055509@lurza.secnetix.de> To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de, freebsd-hackers@FreeBSD.ORG X-Authenticated: #646368 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: top delay value 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, 30 Jan 2007 16:50:32 -0000 > Well, an unprivileged user can achieve the same effect by > typing "while :; do :; done". There are a thousand ways > to waste CPU time, and there is no way to prevent a user > >from doing it. It is not the same effect. You describe fork bombing. Many forked processes eat up the CPU. I could limit the number of process via :maxproc=100: \ in /etc/login.conf > If you want to make top more secure, type "chmod 700 /usr/bin/top". :-) -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 17:19:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6FA0A16A4C9 for ; Tue, 30 Jan 2007 17:19:17 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by mx1.freebsd.org (Postfix) with ESMTP id 3310113C481 for ; Tue, 30 Jan 2007 17:19:16 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: by britannica.bec.de (Postfix, from userid 1000) id 1B0F148C8; Tue, 30 Jan 2007 18:19:02 +0100 (CET) Date: Tue, 30 Jan 2007 18:19:02 +0100 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20070130171902.GA4545@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <200701301521.l0UFLYgE055509@lurza.secnetix.de> <20070130162350.126210@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070130162350.126210@gmx.net> User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: top delay value 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, 30 Jan 2007 17:19:17 -0000 On Tue, Jan 30, 2007 at 05:23:50PM +0100, Dr. Markus Waldeck wrote: > > Well, an unprivileged user can achieve the same effect by > > typing "while :; do :; done". There are a thousand ways > > to waste CPU time, and there is no way to prevent a user > > >from doing it. > > It is not the same effect. > > You describe fork bombing. No, this is just the shell equivalent of for (;;) ; in C. Aka a busy loop. Joerg From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 20:01:14 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9168D16A400 for ; Tue, 30 Jan 2007 20:01:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 6020C13C4A3 for ; Tue, 30 Jan 2007 20:01:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.8/8.13.8) with ESMTP id l0UJxLli007627 for ; Tue, 30 Jan 2007 11:59:21 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.8/8.13.8/Submit) id l0UJxHt2007626 for freebsd-hackers@freebsd.org; Tue, 30 Jan 2007 11:59:17 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Jan 2007 11:59:17 -0800 From: Steve Kargl To: freebsd-hackers@freebsd.org Message-ID: <20070130195917.GA7585@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: ptrace equivalents between freebsd and linux? 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, 30 Jan 2007 20:01:14 -0000 MPICH2 has the ability to use shared memory as one of its communication channel. Unfortuantely, the build dies with an error realted to ptrace. In looking at a linux manpage for ptrace, I've identified that the linux PTRACE_ATTACH and PTRACE_DETACH are equilavent to out PT_ATTACH and PT_DETACH. The build dies later with a problem with PTRACE_PEEKDATA. Is our PT_READ_D the right equivalent? -- Steve From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 30 23:50:55 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43BBD16A406 for ; Tue, 30 Jan 2007 23:50:55 +0000 (UTC) (envelope-from John.Giacomoni@colorado.edu) Received: from suburban.colorado.edu (suburban.colorado.edu [128.138.189.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1A67213C48D for ; Tue, 30 Jan 2007 23:50:54 +0000 (UTC) (envelope-from John.Giacomoni@colorado.edu) Received: from [IPv6:::1] (suburban.colorado.edu [127.0.0.1]) by suburban.colorado.edu (8.13.1/8.13.1) with ESMTP id l0ULcogX008110 for ; Tue, 30 Jan 2007 16:38:50 -0500 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <200609090833.14856.davidxu@freebsd.org> References: <57213DB3-3D5A-4B11-AB29-5696DC4B3AC2@colorado.edu> <200609090833.14856.davidxu@freebsd.org> Content-Type: multipart/mixed; boundary=Apple-Mail-47-766824067 Message-Id: <722B66D4-4030-4C12-8C8D-8B3288F86498@colorado.edu> From: John Giacomoni Date: Tue, 30 Jan 2007 16:34:28 -0700 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: pin/bind a pthread to a processor? (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: Tue, 30 Jan 2007 23:50:55 -0000 --Apple-Mail-47-766824067 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Previously when I asked this question it turned out to not be as necessary as I thought. However, I now need a way to pin/bind a user-space thread to a processor until I'm done with it as my timing constraints are too tight to account for. I checked sys/sched.h, sys/proc.h, pthread.h, and pthread_np.h but it doesn't look like an API to do this was added in 6.2. Can someone point me at a way to hack this in? I'm working on a conference submission and I unfortunately need to pin in user-space as abusing non-preemptive kernel threads is not sufficient for my task. The plan is to have 1-3 threads pinned through the execution of the test (30s - 10min, maybe more) but to leave a cpu untouched so that normal system function can continue on it. When pinning I'd also like to be able to pin to specific processors so I account for the effects placement of different dies, important for my work on dual-processor dual-core AMD systems where IO is routed via hypertransport through the first processor. For those who are interested, this work is focused on building pipeline-parallel systems that overlap sequential work by streaming data through a sequence of processors. One app that I've built with it is to support GigE forwarding at the maximum rate for all frame sizes through user-space. When this work is complete it may be able to help Daniel O'Connor and his question about streaming data from the kernel to userland (1/18/07). Additional information and papers are available at http://www.cs.colorado.edu/~jgiacomo thanks for any help! John G On Sep 8, 2006, at 6:33 PM, David Xu wrote: > On Saturday 09 September 2006 04:18, John Giacomoni wrote: >> Is it possible to bind a pthread to a processor in 5.5 or 6.1? >> >> I currently have a code base that uses libpthread with multiple >> threads, mutexes and condition variables. >> The problem I'm having is that I seem to be suffering wall-clock >> timing aberrations that I believe are introduced by the scheduler. >> >> Thanks, >> >> John G >> >> -- >> >> John.Giacomoni@colorado.edu >> University of Colorado at Boulder >> Department of Computer Science >> Engineering Center, ECCR 1B50 >> 430 UCB >> Boulder, CO 80303-0430 >> USA > > I don't think we have such API allowing you to bind a thread to > a specific CPU, I had implemented such an API for DragonFlyBSD, but > its 1:1 threading is not mature yet. > > David Xu > _______________________________________________ > 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" -- John.Giacomoni@colorado.edu University of Colorado at Boulder Department of Computer Science Engineering Center, ECCR 1B50 430 UCB Boulder, CO 80303-0430 USA --Apple-Mail-47-766824067 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed --Apple-Mail-47-766824067-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 07:55:32 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B018216A403 for ; Wed, 31 Jan 2007 07:55:32 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 4E8B613C441 for ; Wed, 31 Jan 2007 07:55:32 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so459801nfc for ; Tue, 30 Jan 2007 23:55:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=MrVgoER6aHP3sAYIYKtreb6SRR4v9JiKWmijTNkhxvST4Pasl9NCSzoRkxxitgeY5GSj4VCA5JL+GgZkZ3DP+KpvPXtgeSqtVU2XQKg/vIad5dZNQdpf2YQ+C3LZxbsQzJmAcAir3EQvKeYNIc7WUl0PzpoPQS12Q93TQ0Oce+c= Received: by 10.48.48.1 with SMTP id v1mr233058nfv.1170228631846; Tue, 30 Jan 2007 23:30:31 -0800 (PST) Received: from chekov.ufp.fli4l ( [87.166.102.193]) by mx.google.com with ESMTP id k23sm4975630nfc.2007.01.30.23.30.30; Tue, 30 Jan 2007 23:30:30 -0800 (PST) Message-ID: <45C04593.2090704@gmail.com> Date: Wed, 31 Jan 2007 08:30:27 +0100 From: Pascal Hofstee User-Agent: Thunderbird 2.0b1 (X11/20061222) MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: a question regarding 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, 31 Jan 2007 07:55:32 -0000 Hi, In a recent attempt in trying to clean up some compiler warnings in a GNUstep related project i came upon a case where the FreeBSD datatypes seemed to disagree with the Linux ones. Though this in itself is not unusual i do wonder if in this case the Linux definition isn't the more proper one. The definition in question is inside and involves struct shmid_ds.shm_segsz which seems to be defined as "int" whereas Linux defines this as "size_t". I understand these definitions are usually platform dependent but am wondering if Linux's size_t wouldn't be a more proper type for this field .. and if it would make sense to perhaps synchronize our datatypes used here with those used by Linux? With kind regards, -- Pascal Hofstee From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 09:16:59 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D3EF916A400 for ; Wed, 31 Jan 2007 09:16:59 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 5A9B013C4A6 for ; Wed, 31 Jan 2007 09:16:58 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0V8q6Oa006345; Wed, 31 Jan 2007 19:52:06 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0V8q6Br006344; Wed, 31 Jan 2007 19:52:06 +1100 (EST) (envelope-from peter) Date: Wed, 31 Jan 2007 19:52:06 +1100 From: Peter Jeremy To: Pascal Hofstee Message-ID: <20070131085206.GW892@turion.vk2pj.dyndns.org> References: <45C04593.2090704@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/8E7gjuj425jZz9t" Content-Disposition: inline In-Reply-To: <45C04593.2090704@gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: hackers@freebsd.org Subject: Re: a question regarding 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, 31 Jan 2007 09:16:59 -0000 --/8E7gjuj425jZz9t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 2007-Jan-31 08:30:27 +0100, Pascal Hofstee wrote: >In a recent attempt in trying to clean up some compiler warnings in a=20 >GNUstep related project i came upon a case where the FreeBSD datatypes=20 >seemed to disagree with the Linux ones. Though this in itself is not=20 >unusual i do wonder if in this case the Linux definition isn't the more=20 >proper one. > >The definition in question is inside and involves >struct shmid_ds.shm_segsz which seems to be defined as "int" whereas=20 >Linux defines this as "size_t". Whilst I agree that the Linux defn is the more sensible one, System V IPC and common sense are not commonly found together. Tradionally the definition was "int". It appears that the definition changed from "int" to "size_t" in issue 5 of the Open Group base definition but FreeBSD has not caught up with this. I'm not sure what plans there are to change this. You could try putting together a patch to address this and submitting it as a PR (this means addressing all references to shm_segsz in the base system, not just ). --=20 Peter Jeremy --/8E7gjuj425jZz9t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwFi2/opHv/APuIcRAhnsAJ9smPx1OTEMTarJX37PNoylkebjjACcCwxL 3T3EZBnnZcSiaHT3pnzyvXU= =uLxS -----END PGP SIGNATURE----- --/8E7gjuj425jZz9t-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 09:29:20 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D14816A400 for ; Wed, 31 Jan 2007 09:29:20 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id DA31213C4B2 for ; Wed, 31 Jan 2007 09:29:19 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so116307uge for ; Wed, 31 Jan 2007 01:29:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=kEABzlMC4LM9aTPWNskYRCzko7PoGF7PzZVSJWYAlTzujQPs6FXJZkR0SnQB4MbFylujvh1N+5GweUsWiAjLlu31Fx0bO4dzt4BzaWrErEDrGW49Tgegp525K61wYm89xyXCTs50lW3XVGL0qYFMLIgjMB+bvOuzJv9cUqJmrK0= Received: by 10.67.119.13 with SMTP id w13mr753139ugm.1170235758616; Wed, 31 Jan 2007 01:29:18 -0800 (PST) Received: from chekov.ufp.fli4l ( [87.166.102.193]) by mx.google.com with ESMTP id e23sm729468ugd.2007.01.31.01.29.17; Wed, 31 Jan 2007 01:29:17 -0800 (PST) Message-ID: <45C06167.60401@gmail.com> Date: Wed, 31 Jan 2007 10:29:11 +0100 From: Pascal Hofstee User-Agent: Thunderbird 2.0b1 (X11/20061222) MIME-Version: 1.0 To: Peter Jeremy References: <45C04593.2090704@gmail.com> <20070131085206.GW892@turion.vk2pj.dyndns.org> In-Reply-To: <20070131085206.GW892@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: a question regarding 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, 31 Jan 2007 09:29:20 -0000 Peter Jeremy wrote: > Whilst I agree that the Linux defn is the more sensible one, System V > IPC and common sense are not commonly found together. Tradionally the > definition was "int". It appears that the definition changed from > "int" to "size_t" in issue 5 of the Open Group base definition but > FreeBSD has not caught up with this. > > I'm not sure what plans there are to change this. You could try > putting together a patch to address this and submitting it as a PR > (this means addressing all references to shm_segsz in the base > system, not just ). First of all, thanks for the quick response. At the very least this sheds some light onto the history and how this situation likely came to pass. I'll see if i can put together a patch during the next week or so that would bring our definitions regarding System V IPC in synch, i'll also try to see if i can find additional occurances of similar discrepancies so these could be fixed in a single run. Any additional sugestions/objections are always greatly appreciated. -- Pascal Hofstee From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 10:28:46 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 229BB16A401 for ; Wed, 31 Jan 2007 10:28:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id D6ACB13C4A3 for ; Wed, 31 Jan 2007 10:28:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id DF4652083; Wed, 31 Jan 2007 11:05:17 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id D02A82081; Wed, 31 Jan 2007 11:05:17 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id A47A6B815; Wed, 31 Jan 2007 11:05:17 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Pascal Hofstee References: <45C04593.2090704@gmail.com> <20070131085206.GW892@turion.vk2pj.dyndns.org> <45C06167.60401@gmail.com> Date: Wed, 31 Jan 2007 11:05:17 +0100 In-Reply-To: <45C06167.60401@gmail.com> (Pascal Hofstee's message of "Wed, 31 Jan 2007 10:29:11 +0100") Message-ID: <86odofjyua.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: a question regarding 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, 31 Jan 2007 10:28:46 -0000 Pascal Hofstee writes: > Any additional sugestions/objections are always greatly appreciated. On 32-bit platforms (i386, powerpc), int is a 32-bit signed integer while size_t is a 32-bit unsigned integer. On 64-bit platforms (amd64, sparc64 etc), int is a 32-bit signed integer while size_t is a 64-bit unsigned integer. In both cases, changing this structure member from int to size_t will break the ABI. This doesn't mean you shouldn't do it, just that it should be done with care. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 10:28:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25C2216A406 for ; Wed, 31 Jan 2007 10:28:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id DAAE213C4A5 for ; Wed, 31 Jan 2007 10:28:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 280A72081; Wed, 31 Jan 2007 11:10:27 +0100 (CET) X-Spam-Tests: AWL,MAILTO_TO_SPAM_ADDR X-Spam-Learn: disabled X-Spam-Score: 0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 0D79F2049; Wed, 31 Jan 2007 11:10:27 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id E62A3B815; Wed, 31 Jan 2007 11:10:26 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Daniel Rudy References: <45BB72D6.9070809@pacbell.net> Date: Wed, 31 Jan 2007 11:10:26 +0100 In-Reply-To: <45BB72D6.9070809@pacbell.net> (Daniel Rudy's message of "Sat, 27 Jan 2007 07:42:14 -0800") Message-ID: <86k5z3jylp.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: sysctl(3) interface 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, 31 Jan 2007 10:28:46 -0000 Daniel Rudy writes: > I've been taking apart and analyzing the sysctl(8) program to gain a > better insight into how to use the sysctl(3) interface. [...] > It's using an oid of 0 and 2 to get something, then it comes up with 440 > and then a sequence of numbers that are incrementing in a peculiar > pattern. sysctl(8) uses undocumented interfaces to a) enumerate the nodes in the sysctl tree and b) obtain the name of a node, given its OID. > So, my question is, how do I walk the tree to get the PnP info for all > the devices in the system? man 3 devinfo DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 11:22:21 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70E6316A400 for ; Wed, 31 Jan 2007 11:22:21 +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 470CB13C441 for ; Wed, 31 Jan 2007 11:22:21 +0000 (UTC) (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 549714D127; Wed, 31 Jan 2007 05:52:04 -0500 (EST) Date: Wed, 31 Jan 2007 10:52:02 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= In-Reply-To: <86odofjyua.fsf@dwp.des.no> Message-ID: <20070131105024.L91177@fledge.watson.org> References: <45C04593.2090704@gmail.com> <20070131085206.GW892@turion.vk2pj.dyndns.org> <45C06167.60401@gmail.com> <86odofjyua.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-728634878-1170240722=:91177" Cc: hackers@freebsd.org, Pascal Hofstee Subject: Re: a question regarding 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, 31 Jan 2007 11:22:21 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-728634878-1170240722=:91177 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Wed, 31 Jan 2007, Dag-Erling Sm=F8rgrav wrote: > Pascal Hofstee writes: >> Any additional sugestions/objections are always greatly appreciated. > > On 32-bit platforms (i386, powerpc), int is a 32-bit signed integer while= =20 > size_t is a 32-bit unsigned integer. > > On 64-bit platforms (amd64, sparc64 etc), int is a 32-bit signed integer= =20 > while size_t is a 64-bit unsigned integer. > > In both cases, changing this structure member from int to size_t will bre= ak=20 > the ABI. > > This doesn't mean you shouldn't do it, just that it should be done with= =20 > care. If we do decide to go ahead with the ABI change, there are a number of othe= r=20 things that should be done simultaneously, such as changing the uid and gid= =20 fields to uid_t and gid_t. I would very much like to see the ABI change=20 happen, and the first step (breaking out kernel from user structures) has b= een=20 done already as part of the MAC work. The next step is to add routines tha= t=20 translate internal/external formats, which isn't hard, but requires a moder= ate=20 pile of code to do (as well as great care :-). Robert N M Watson Computer Laboratory University of Cambridge --0-728634878-1170240722=:91177-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 14:42:33 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A0F2D16A407 for ; Wed, 31 Jan 2007 14:42:33 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 12A7213C4B3 for ; Wed, 31 Jan 2007 14:42:32 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (spslgh@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l0VEgQOb093492; Wed, 31 Jan 2007 15:42:31 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l0VEgQbA093491; Wed, 31 Jan 2007 15:42:26 +0100 (CET) (envelope-from olli) Date: Wed, 31 Jan 2007 15:42:26 +0100 (CET) Message-Id: <200701311442.l0VEgQbA093491@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de In-Reply-To: <20070130162350.126210@gmx.net> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 31 Jan 2007 15:42:31 +0100 (CET) Cc: Subject: Re: top delay value X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 14:42:33 -0000 Dr. Markus Waldeck wrote: > Oliver Fromme wrote: > > Well, an unprivileged user can achieve the same effect by > > typing "while :; do :; done". There are a thousand ways > > to waste CPU time, and there is no way to prevent a user > > > from doing it. > > It is not the same effect. > > You describe fork bombing. No. What I write above is not a "fork bomb", it's a single process which is wasting CPU in a busy loop. It's exactly equivalent to top(1) with zero delay, except that top produces some output, while a busy loop does nothing useful at all. > I could limit the number of process via > :maxproc=100: \ > in /etc/login.conf Which doesn't help against a busy loop. > > If you want to make top more secure, type "chmod 700 /usr/bin/top". > > :-) Actually I was serious. Normal users don't really need to run top (which is only contributed third-party software anyway). It doesn't provide any information that you can't get with other regular tools, such as ps(1) which is a native FreeBSD tools. By the way, you can "emulate" top(1) with run ps(1) in a shell loop like this (sh/zsh/ksh/bash syntax): while :; do clear; ps -a; sleep 1; done Do get zero delay, simply remove the sleep command from the loop ... That's actually _worse_ than top(1) with zero delay, because kernel cycles are wasted for the fork() and exec() calls, not to mention I/O and other syscalls. An empty shell loop ("while :; do :; done") doesn't perform any syscalls into the kernel. Bottom line: Disabling zero-delay in top doesn't buy you anything at all. In fact, it might cause your users to invent work-arounds (for example shell loops) that waste even more resources. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies." -- C.A.R. Hoare, ACM Turing Award Lecture, 1980 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 14:58:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3D3316A403 for ; Wed, 31 Jan 2007 14:58:06 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay08.ispgateway.de (smtprelay08.ispgateway.de [80.67.29.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4D83A13C494 for ; Wed, 31 Jan 2007 14:58:05 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 10316 invoked from network); 31 Jan 2007 14:31:25 -0000 Received: from unknown (HELO localhost) (775067@[217.50.129.24]) (envelope-sender ) by smtprelay08.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 31 Jan 2007 14:31:25 -0000 Date: Wed, 31 Jan 2007 15:31:14 +0100 From: Fabian Keil To: freebsd-hackers@freebsd.org Message-ID: <20070131153114.4e76a6ea@localhost> In-Reply-To: <20070131105024.L91177@fledge.watson.org> References: <45C04593.2090704@gmail.com> <20070131085206.GW892@turion.vk2pj.dyndns.org> <45C06167.60401@gmail.com> <86odofjyua.fsf@dwp.des.no> <20070131105024.L91177@fledge.watson.org> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd6.2) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_HDCpO/+1fVQfn4OGVmJ+kpN"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Re: a question regarding 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, 31 Jan 2007 14:58:07 -0000 --Sig_HDCpO/+1fVQfn4OGVmJ+kpN Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Wed, 31 Jan 2007, Dag-Erling Sm=F8rgrav wrote: >=20 > > Pascal Hofstee writes: > >> Any additional sugestions/objections are always greatly appreciated. > > > > On 32-bit platforms (i386, powerpc), int is a 32-bit signed integer whi= le=20 > > size_t is a 32-bit unsigned integer. > > > > On 64-bit platforms (amd64, sparc64 etc), int is a 32-bit signed intege= r=20 > > while size_t is a 64-bit unsigned integer. > > > > In both cases, changing this structure member from int to size_t will b= reak=20 > > the ABI. > > > > This doesn't mean you shouldn't do it, just that it should be done with= =20 > > care. >=20 > If we do decide to go ahead with the ABI change, there are a number of ot= her=20 > things that should be done simultaneously, such as changing the uid and g= id=20 > fields to uid_t and gid_t. struct tm's members could be changed as well. Quoting a response I got from Juliusz Chroboczek (the author of Polipo) after reporting a compiler warning: |By the way, IEEE 1003.1-2003 says that tv_sec should be a time_t, |hence by making it a long, FreeBSD and NetBSD are violating the POSIX |standard. Could you please file a bug report with them? I didn't find any claims about FreeBSD being IEEE 1003.1-2003 compliant and therefore didn't consider it a bug, but given that the topic is *_t changes and time_t hasn't come up yet, I'd like to mention it anyway. Fabian --Sig_HDCpO/+1fVQfn4OGVmJ+kpN Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwKg7BYqIVf93VJ0RAkgkAJ46e6l4q5xAOmv1QCpCoD33so+U6QCfeeJo 8K137VWewQtzvGOxM27m5gc= =h41F -----END PGP SIGNATURE----- --Sig_HDCpO/+1fVQfn4OGVmJ+kpN-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 15:15:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C298C16A504; Wed, 31 Jan 2007 15:15:22 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0C13B13C4B9; Wed, 31 Jan 2007 15:15:20 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ppp230-38.lns2.adl4.internode.on.net (HELO mail.clearchain.com) ([203.122.230.38]) by ipmail01.adl2.internode.on.net with ESMTP; 01 Feb 2007 01:45:16 +1030 X-IronPort-AV: i="4.13,263,1167571800"; d="scan'208"; a="81872122:sNHT35457240" Received: from [192.168.155.248] ([192.168.155.248]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id l0VFEwg7025896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Feb 2007 01:45:06 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <45C0B271.4040100@clearchain.com> Date: Thu, 01 Feb 2007 01:44:57 +1030 From: Benjamin Close User-Agent: Thunderbird 1.5.0.8 (X11/20061211) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <459E6477.2010508@clearchain.com> <200701051634.00293.max@love2party.net> <459E75A5.7000309@FreeBSD.org> <200701051732.27176.max@love2party.net> <45A0F739.3030202@clearchain.com> <499c70c0701201038w6960174n3006ffd525f17bf6@mail.gmail.com> <20070124204443.GA1107@bsdmon.com> <45B9F697.1090402@clearchain.com> <20070127101900.GB1099@bsdmon.com> <11167f520701271114j66f82398h83c43885b9d25e12@mail.gmail.com> In-Reply-To: <11167f520701271114j66f82398h83c43885b9d25e12@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.7/2507/Wed Jan 31 09:30:28 2007 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.155.1]); Thu, 01 Feb 2007 01:45:13 +1030 (CST) X-Mailman-Approved-At: Wed, 31 Jan 2007 17:01:04 +0000 Cc: Massimo Lusetti , Florent Thoumie , freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org, Attilio Rao , sam@freebsd.org, gabor@freebsd.org, Max Laier , Gilbert Cao Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller 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, 31 Jan 2007 15:15:22 -0000 Hi Folks, A new version of the driver is up which fixes the firmware issues. Seems the wpi-firmware-kmod port was creating corrupt modules. Things should work much better now. Download at the same place, file: 20070131-wpi-freebsd.tar.gz Cheers, Benjamin Sam Fourman Jr. wrote: > I can also confirm that i get the firmware_get: failed to load > firmware image wpi_fw on the > 20070125 version. > I should note that I tried it on a fresh 6.2 RELEASE install. > > Sam Fourman Jr. > > On 1/27/07, Gilbert Cao wrote: >> On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: >> > Hi Gilbert, >> > Thanks for the custom version. I've integrated the changes into the >> > driver I'm working on. >> > For those wanting to test out the driver which is now fully up to date >> > with all change from NetBSD & OpenBSD - and has a few minor >> improvements >> > over them, grab it from: >> > >> > http://www.clearchain.com/~benjsc/download/ >> > >> > File is: 20070125-wpi-freebsd.tar.gz >> > >> > Full instructions on how to build / install the driver are in the >> README >> > in the tar file. >> > >> > This should work both under -current and 6.2-Stable now. >> > >> > Info about the driver and what's working/broken can be found at: >> > >> > http://www.clearchain.com/wiki/wpi >> > >> > Cheers, >> > Benjamin >> >> I have tried the new 20070125 version. >> However, I did not manage to make work. At least, it compiles. >> I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. >> wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. >> >> When, I "kldload if_wpi", here is a small sample of /var/log/messages >> >> Jan 27 10:30:39 vaio kernel: wpi0: >> mem 0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 >> Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory >> properly. >> Jan 27 10:30:39 vaio last message repeated 6 times >> Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a >> Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] >> Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: >> Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: >> Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware >> image wpi_fw >> Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image >> 'wpi_fw' >> Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware >> image wpi_fw >> Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image >> 'wpi_fw' >> Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware >> image wpi_fw >> Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image >> 'wpi_fw' >> >> In kldstat, both modules are loaded. >> Then, I have "kldunload if_wpi" (and if_wpi seems to be reload, >> automatically, I don't know why). Same problem, it seems that wpi_fw >> could not be load (found ?). >> >> As a result, no AP is "associated". >> >> >> After a fresh reboot, I have reinstall the custom 20070121 version of >> mine, and all returns OK. >> Another strange thing: when "kldload if_wpi" with 20070121 version, and >> then kldstat, I don't see "wpi_ucode". It seems that wpi_ucode.ko does >> not need to be loaded, in my case. >> My wpi_ucode.ko lies in /boot/modules >> >> After another fresh reboot, I first moved wpi_ucode.ko to another place. >> When I "kldload if_wpi", I got the following message: >> >> Jan 27 09:47:16 vaio kernel: wpi0: >> mem 0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 >> Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory >> properly. >> Jan 27 09:47:16 vaio last message repeated 6 times >> Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a >> Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] >> Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps >> 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >> Jan 27 09:47:16 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >> Jan 27 09:47:16 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps >> 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >> Jan 27 09:47:16 vaio kernel: firmware_get: failed to load firmware >> image wpi_ucode >> Jan 27 09:47:16 vaio kernel: wpi0: could not load firmware image >> 'wpi_ucode' >> >> So, it seems that wpi_ucode.ko have to lied in my /boot/modules (the >> place where I have also put if_wpi 20070121 version), even if it is not >> loaded. >> >> -- >> -------------------------------- >> (hika) Gilbert Cao >> http://www.miaouirc.com >> - MiaouIRC Project 2002-2003 >> http://www.bsdmon.com >> - The BSD DMON Power to serve >> IRC : #miaule at IRCNET Network >> -------------------------------- >> >> >> > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to > "freebsd-drivers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 15:18:11 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C03AC16A405; Wed, 31 Jan 2007 15:18:11 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.freebsd.org (Postfix) with ESMTP id 48AA413C442; Wed, 31 Jan 2007 15:18:11 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from smtp.xbsd.org (unknown [82.233.2.192]) by smtp3-g19.free.fr (Postfix) with ESMTP id 5B4504A2CA; Wed, 31 Jan 2007 16:18:10 +0100 (CET) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id E92B711ADC; Wed, 31 Jan 2007 16:18:08 +0100 (CET) X-Virus-Scanned: amavisd-new at xbsd.org Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZ9MG45clBj2; Wed, 31 Jan 2007 16:18:02 +0100 (CET) Received: from [193.95.134.156] (mayday.esat.net [193.95.134.156]) by smtp.xbsd.org (Postfix) with ESMTP id 4C2D011410; Wed, 31 Jan 2007 16:18:01 +0100 (CET) Message-ID: <45C0B33B.9000807@FreeBSD.org> Date: Wed, 31 Jan 2007 15:18:19 +0000 From: Florent Thoumie User-Agent: Thunderbird 1.5.0.9 (X11/20070122) MIME-Version: 1.0 To: Benjamin Close References: <459E6477.2010508@clearchain.com> <200701051634.00293.max@love2party.net> <459E75A5.7000309@FreeBSD.org> <200701051732.27176.max@love2party.net> <45A0F739.3030202@clearchain.com> <499c70c0701201038w6960174n3006ffd525f17bf6@mail.gmail.com> <20070124204443.GA1107@bsdmon.com> <45B9F697.1090402@clearchain.com> <20070127101900.GB1099@bsdmon.com> <11167f520701271114j66f82398h83c43885b9d25e12@mail.gmail.com> <45C0B271.4040100@clearchain.com> In-Reply-To: <45C0B271.4040100@clearchain.com> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig9D14E6904D00B4B6935167C0" X-Mailman-Approved-At: Wed, 31 Jan 2007 17:01:17 +0000 Cc: Massimo Lusetti , freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org, Attilio Rao , sam@freebsd.org, gabor@freebsd.org, "Sam Fourman Jr." , Max Laier , Gilbert Cao Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller 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, 31 Jan 2007 15:18:11 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9D14E6904D00B4B6935167C0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Benjamin Close wrote: > Hi Folks, > A new version of the driver is up which fixes the firmware issues. > Seems the wpi-firmware-kmod port was creating corrupt modules. > Things should work much better now. Download at the same place, file: > 20070131-wpi-freebsd.tar.gz So, when is it going to HEAD? :-) --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --------------enig9D14E6904D00B4B6935167C0 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.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwLM/MxEkbVFH3PQRCgTfAJ9W9MByYZLyuNljVNjG9Bdv5rhG4QCdHxrs wQ50ljQO98SZZynJ8hJw17Q= =nYrP -----END PGP SIGNATURE----- --------------enig9D14E6904D00B4B6935167C0-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 17:02:43 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C726A16A406 for ; Wed, 31 Jan 2007 17:02:43 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 2547A13C428 for ; Wed, 31 Jan 2007 17:02:42 +0000 (UTC) (envelope-from waldeck@gmx.de) Received: (qmail 19463 invoked by uid 0); 31 Jan 2007 17:02:41 -0000 Received: from 82.141.47.50 by www120.gmx.net with HTTP; Wed, 31 Jan 2007 18:02:41 +0100 (CET) Content-Type: text/plain; charset="us-ascii" Date: Wed, 31 Jan 2007 18:02:41 +0100 From: "Dr. Markus Waldeck" In-Reply-To: <200701311442.l0VEgQbA093491@lurza.secnetix.de> Message-ID: <20070131170241.230960@gmx.net> MIME-Version: 1.0 References: <200701311442.l0VEgQbA093491@lurza.secnetix.de> To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de X-Authenticated: #646368 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: top delay value 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, 31 Jan 2007 17:02:43 -0000 > > > typing "while :; do :; done". There are a thousand ways > No. What I write above is not a "fork bomb", it's a single > process which is wasting CPU in a busy loop. It's exactly > equivalent to top(1) with zero delay, except that top > produces some output, while a busy loop does nothing useful > at all. I tested different shells and I found out that an exlicit sub shell is required to let the shell fork: while :; do (:); done > By the way, you can "emulate" top(1) with run ps(1) in a > shell loop like this (sh/zsh/ksh/bash syntax): > > while :; do clear; ps -a; sleep 1; done > > Do get zero delay, simply remove the sleep command from the > loop ... That's actually _worse_ than top(1) with zero > delay, because kernel cycles are wasted for the fork() and > exec() calls, not to mention I/O and other syscalls. An > empty shell loop ("while :; do :; done") doesn't perform > any syscalls into the kernel. > > Bottom line: Disabling zero-delay in top doesn't buy you > anything at all. In fact, it might cause your users to > invent work-arounds (for example shell loops) that waste > even more resources. So I have to limit the CPU time in /etc/login.conf and :cputime=300:\ invoke cap_mkdb /etc/login.conf. -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: http://www.gmx.net/de/go/promail From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 17:07:36 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A1DE16A400 for ; Wed, 31 Jan 2007 17:07:36 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 6226513C428 for ; Wed, 31 Jan 2007 17:07:36 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id A952D285C8; Wed, 31 Jan 2007 10:44:35 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 2A33861C3B; Wed, 31 Jan 2007 10:44:35 -0600 (CST) Date: Wed, 31 Jan 2007 10:44:35 -0600 From: "Matthew D. Fuller" To: freebsd-hackers@FreeBSD.ORG, waldeck@gmx.de Message-ID: <20070131164435.GM12602@over-yonder.net> References: <20070130162350.126210@gmx.net> <200701311442.l0VEgQbA093491@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701311442.l0VEgQbA093491@lurza.secnetix.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: Subject: Re: top delay value 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, 31 Jan 2007 17:07:36 -0000 On Wed, Jan 31, 2007 at 03:42:26PM +0100 I heard the voice of Oliver Fromme, and lo! it spake thus: > > Bottom line: Disabling zero-delay in top doesn't buy you anything > at all. Meanwhile, you still can't zero-delay unless you're root. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 17:33:30 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0AB4A16A400 for ; Wed, 31 Jan 2007 17:33:30 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 8B4D313C4A3 for ; Wed, 31 Jan 2007 17:33:29 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 17643 invoked by uid 1001); 31 Jan 2007 17:34:09 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Wed, 31 Jan 2007 12:34:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17856.54032.973691.182086@bhuda.mired.org> Date: Wed, 31 Jan 2007 12:34:08 -0500 To: "Dr. Markus Waldeck" In-Reply-To: <20070131170241.230960@gmx.net> References: <200701311442.l0VEgQbA093491@lurza.secnetix.de> <20070131170241.230960@gmx.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.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: top delay value 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, 31 Jan 2007 17:33:30 -0000 In <20070131170241.230960@gmx.net>, Dr. Markus Waldeck typed: > > > > typing "while :; do :; done". There are a thousand ways > > > No. What I write above is not a "fork bomb", it's a single > > process which is wasting CPU in a busy loop. It's exactly > > equivalent to top(1) with zero delay, except that top > > produces some output, while a busy loop does nothing useful > > at all. > > I tested different shells and I found out that an exlicit sub shell > is required to let the shell fork: > > while :; do (:); done That's still not a fork bomb. While it creates a process every time through the loop, the process exits before the loop continues, so you've still got just a few processes. Basicaly, it's still a busy loop. A true fork bomb creates an ever-increasing number of processes, typically by forking copies of itself (which led to them being called "rabbit jobs" when I first ran into one). http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 18:06:05 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 631D416A400 for ; Wed, 31 Jan 2007 18:06:05 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id E74B013C428 for ; Wed, 31 Jan 2007 18:06:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0VI5xin008133; Thu, 1 Feb 2007 05:05:59 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0VI5w9s008132; Thu, 1 Feb 2007 05:05:58 +1100 (EST) (envelope-from peter) Date: Thu, 1 Feb 2007 05:05:58 +1100 From: Peter Jeremy To: Robert Watson Message-ID: <20070131180558.GY892@turion.vk2pj.dyndns.org> References: <45C04593.2090704@gmail.com> <20070131085206.GW892@turion.vk2pj.dyndns.org> <45C06167.60401@gmail.com> <86odofjyua.fsf@dwp.des.no> <20070131105024.L91177@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6THr7QwYWIbrk6Kt" Content-Disposition: inline In-Reply-To: <20070131105024.L91177@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , hackers@freebsd.org, Pascal Hofstee Subject: Re: a question regarding 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, 31 Jan 2007 18:06:05 -0000 --6THr7QwYWIbrk6Kt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 2007-Jan-31 10:52:02 +0000, Robert Watson wrote: >If we do decide to go ahead with the ABI change, there are a number of=20 >other things that should be done simultaneously, such as changing the uid= =20 >and gid fields to uid_t and gid_t. And mode to mode_t. The uid and gid fields in struct shmid_ds have already been converted, though the ones in struct ipc_perm are obsolete. At a quick glance, everything else is up to date. http://www.opengroup.org/onlinepubs/009695399/ is a useful reference in this area. --=20 Peter Jeremy --6THr7QwYWIbrk6Kt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwNqG/opHv/APuIcRAi9TAJ9h6rnY40PFujkk3cXeZeqXrwWrzwCgqQNy jIKnFUIl2y4VgpzNusAbflE= =nTpG -----END PGP SIGNATURE----- --6THr7QwYWIbrk6Kt-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 31 21:30:12 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40F3116A400 for ; Wed, 31 Jan 2007 21:30:12 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id B04E713C48D for ; Wed, 31 Jan 2007 21:30:11 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so671217nfc for ; Wed, 31 Jan 2007 13:30:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=kN6LNfro2h1kaO3xD6ifq0v5Mc5QhD/CQ7vWsH7qIy3JZcSJjL+Mup6/2oS5wBIoUpB1hu8Zh6/4Sck+M3Y/tDvU3NiSKapIJsCwD9huenwUIbzURiRPg7G1vKvw9jKpEaLQD9TbH3QUoD+e92drd30pzqs1e4l9nGHDu9FaVME= Received: by 10.48.216.8 with SMTP id o8mr3197117nfg.1170279005764; Wed, 31 Jan 2007 13:30:05 -0800 (PST) Received: by 10.49.63.7 with HTTP; Wed, 31 Jan 2007 13:30:05 -0800 (PST) Message-ID: <346a80220701311330t389914c7rec2c24ca6df351c9@mail.gmail.com> Date: Wed, 31 Jan 2007 14:30:05 -0700 From: "Coleman Kane" To: "Mike Meyer" In-Reply-To: <17856.54032.973691.182086@bhuda.mired.org> MIME-Version: 1.0 References: <200701311442.l0VEgQbA093491@lurza.secnetix.de> <20070131170241.230960@gmx.net> <17856.54032.973691.182086@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Dr. Markus Waldeck" , freebsd-hackers@freebsd.org Subject: Re: top delay value X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 21:30:12 -0000 On 1/31/07, Mike Meyer wrote: > > In <20070131170241.230960@gmx.net>, Dr. Markus Waldeck > typed: > > > > > typing "while :; do :; done". There are a thousand ways > > > > > No. What I write above is not a "fork bomb", it's a single > > > process which is wasting CPU in a busy loop. It's exactly > > > equivalent to top(1) with zero delay, except that top > > > produces some output, while a busy loop does nothing useful > > > at all. > > > > I tested different shells and I found out that an exlicit sub shell > > is required to let the shell fork: > > > > while :; do (:); done > > That's still not a fork bomb. While it creates a process every time > through the loop, the process exits before the loop continues, so > you've still got just a few processes. Basicaly, it's still a busy > loop. > > A true fork bomb creates an ever-increasing number of processes, > typically by forking copies of itself (which led to them being called > "rabbit jobs" when I first ran into one). > > -- > Mike Meyer > http://www.mired.org/consulting.html > Independent Network/Unix/Perforce consultant, email for more information. Don't forget that a real fork bomb would fork forking forkers thereby growing the process overhead and time exponentially! e.g: perl -e 'while(1) { fork; };' -- Coleman Kane From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 02:51:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8E1C16A407 for ; Thu, 1 Feb 2007 02:51:00 +0000 (UTC) (envelope-from kazakov@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 8848613C481 for ; Thu, 1 Feb 2007 02:51:00 +0000 (UTC) (envelope-from kazakov@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so347142uge for ; Wed, 31 Jan 2007 18:50:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nefNk/SZSu0jMKaTCl8m+RG2OizTW3MScSPwsf5rCoMGMr6qFr0Uxt7uxOtf/8HZKrIuQTZ1IARkKP+LE8M5Y9w9c3gW+FwFIrj8q4kEDjMXkWaPfVYxaHBKG9RIm4W75R8MYcovJE9oQzJmB+iZN2oGrdRydjQlJ1SzbDhDJes= Received: by 10.67.99.1 with SMTP id b1mr1984814ugm.1170296603613; Wed, 31 Jan 2007 18:23:23 -0800 (PST) Received: by 10.67.119.17 with HTTP; Wed, 31 Jan 2007 18:23:23 -0800 (PST) Message-ID: Date: Thu, 1 Feb 2007 11:23:23 +0900 From: "Artem Kazakov" To: "FreeBSD Hackers" , freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: diskless boot /usr/local/etc/rc.d/ scripts do not run, why? 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, 01 Feb 2007 02:51:01 -0000 Hello everyone, I'm using 6-stable on 4 amd64 machines. One of them has FreeBSD on its local hard drive and others are booted via network with PXE. But I encounter that /usr/local/etc/rc.d/* are not executed during the boot process? Is there some kind of option to change this? Or may be I misconfigured something ? Also, I do not see any messages on console after kernel is loaded into memory. The next thing I see is login: prompt. How to turn on boot messages for network booted machines. I have to say that I use this loader.rc for network boot: load /boot/kernel/kernel echo \007\007 set console="vidconsole" autoboot Cheers, Tyoma. From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 15:31:39 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CAD2016A401 for ; Thu, 1 Feb 2007 15:31:39 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id 8D9A613C48E for ; Thu, 1 Feb 2007 15:31:39 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l11FVWiI089927; Thu, 1 Feb 2007 09:31:32 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l11FVWSk089926; Thu, 1 Feb 2007 09:31:32 -0600 (CST) (envelope-from brooks) Date: Thu, 1 Feb 2007 09:31:32 -0600 From: Brooks Davis To: Artem Kazakov Message-ID: <20070201153132.GC67362@lor.one-eyed-alien.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7qSK/uQB79J36Y4o" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Thu, 01 Feb 2007 09:31:32 -0600 (CST) Cc: FreeBSD Hackers , freebsd-questions@freebsd.org Subject: Re: diskless boot /usr/local/etc/rc.d/ scripts do not run, why? 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, 01 Feb 2007 15:31:39 -0000 --7qSK/uQB79J36Y4o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 01, 2007 at 11:23:23AM +0900, Artem Kazakov wrote: > Hello everyone, >=20 > I'm using 6-stable on 4 amd64 machines. One of them has FreeBSD on its > local hard drive and others are booted via network with PXE. > But I encounter that /usr/local/etc/rc.d/* are not executed during the > boot process? > Is there some kind of option to change this? > Or may be I misconfigured something ? If you boot diskless and /usr or /usr/local is a seperate NFS mount you must adjust the value of the rc.conf(5) variable early_late_divider for your scripts to be processed. See the rc.conf manpage for details. > Also, I do not see any messages on console after kernel is loaded into= =20 > memory. > The next thing I see is login: prompt. How to turn on boot messages > for network booted machines. >=20 > I have to say that I use this loader.rc for network boot: > load /boot/kernel/kernel > echo \007\007 > set console=3D"vidconsole" > autoboot Do you by chance have a /boot.config? It sounds like your system is probably running on a serial console. -- Brooks --7qSK/uQB79J36Y4o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwgfTXY6L6fI4GtQRAmxcAJ0WpXn5L+FH2vwU4PLuz3e2ejGxcwCfSD3E pMKOpt739rwEwxAO6wyyZoc= =pK5r -----END PGP SIGNATURE----- --7qSK/uQB79J36Y4o-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 18:39:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F338616A405 for ; Thu, 1 Feb 2007 18:39:51 +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 B8ECE13C474 for ; Thu, 1 Feb 2007 18:39:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l11IcKBl062686; Thu, 1 Feb 2007 11:38:21 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 01 Feb 2007 11:38:51 -0700 (MST) Message-Id: <20070201.113851.689651534.imp@bsdimp.com> To: peterjeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20070128181132.GR927@turion.vk2pj.dyndns.org> References: <45BC3624.3000608@pacbell.net> <3B777B32-AB3A-4244-BBE1-9E11B287D78B@hursk.com> <20070128181132.GR927@turion.vk2pj.dyndns.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 01 Feb 2007 11:38:23 -0700 (MST) Cc: jon.passki@hursk.com, fbsd@metro.cx, freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 01 Feb 2007 18:39:52 -0000 In message: <20070128181132.GR927@turion.vk2pj.dyndns.org> Peter Jeremy writes: : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: : >If the machine is a PXE-compliant device [2], it should have a GUID/ : >UUID [1] available. This can be exposed by sysutil/hal [3] via the : >smbios.system.uuid field. : : You can also get it via kenv(8) without needing any ports: : # kenv smbios.system.uuid : 9F345F4F-BEFC-D431-1340-61235A56DEF9 I wonder why the smbios stuff isn't exported via sysctls as well... Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 18:43:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 215CE16A405 for ; Thu, 1 Feb 2007 18:43:03 +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 DC3A613C4AC for ; Thu, 1 Feb 2007 18:43:02 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l11IeoFW062692; Thu, 1 Feb 2007 11:40:51 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 01 Feb 2007 11:41:21 -0700 (MST) Message-Id: <20070201.114121.110116525.imp@bsdimp.com> To: des@des.no From: "M. Warner Losh" In-Reply-To: <86k5z3jylp.fsf@dwp.des.no> References: <45BB72D6.9070809@pacbell.net> <86k5z3jylp.fsf@dwp.des.no> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 01 Feb 2007 11:40:52 -0700 (MST) Cc: freebsd-hackers@freebsd.org, dr2867@pacbell.net Subject: Re: sysctl(3) interface 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, 01 Feb 2007 18:43:03 -0000 In message: <86k5z3jylp.fsf@dwp.des.no> des@des.no (Dag-Erling Sm=F8rgrav) writes: : Daniel Rudy writes: : > I've been taking apart and analyzing the sysctl(8) program to gain = a : > better insight into how to use the sysctl(3) interface. [...] : > It's using an oid of 0 and 2 to get something, then it comes up wit= h 440 : > and then a sequence of numbers that are incrementing in a peculiar : > pattern. : = : sysctl(8) uses undocumented interfaces to a) enumerate the nodes in : the sysctl tree and b) obtain the name of a node, given its OID. : = : > So, my question is, how do I walk the tree to get the PnP info for = all : > the devices in the system? : = : man 3 devinfo devinfo -v will also give that information. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 18:45:55 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFDDC16A400 for ; Thu, 1 Feb 2007 18:45:55 +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 931C013C48E for ; Thu, 1 Feb 2007 18:45:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l11IiD2u062721; Thu, 1 Feb 2007 11:44:14 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 01 Feb 2007 11:44:44 -0700 (MST) Message-Id: <20070201.114444.29501661.imp@bsdimp.com> To: freebsd-listen@fabiankeil.de From: "M. Warner Losh" In-Reply-To: <20070131153114.4e76a6ea@localhost> References: <86odofjyua.fsf@dwp.des.no> <20070131105024.L91177@fledge.watson.org> <20070131153114.4e76a6ea@localhost> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 01 Feb 2007 11:44:14 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: a question regarding 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, 01 Feb 2007 18:45:56 -0000 In message: <20070131153114.4e76a6ea@localhost> Fabian Keil writes: : Robert Watson wrote: : = : > On Wed, 31 Jan 2007, Dag-Erling Sm=F8rgrav wrote: : > = : > > Pascal Hofstee writes: : > >> Any additional sugestions/objections are always greatly apprecia= ted. : > > : > > On 32-bit platforms (i386, powerpc), int is a 32-bit signed integ= er while = : > > size_t is a 32-bit unsigned integer. : > > : > > On 64-bit platforms (amd64, sparc64 etc), int is a 32-bit signed = integer = : > > while size_t is a 64-bit unsigned integer. : > > : > > In both cases, changing this structure member from int to size_t = will break = : > > the ABI. : > > : > > This doesn't mean you shouldn't do it, just that it should be don= e with = : > > care. : > = : > If we do decide to go ahead with the ABI change, there are a number= of other = : > things that should be done simultaneously, such as changing the uid= and gid = : > fields to uid_t and gid_t. : = : struct tm's members could be changed as well. struct tm doesn't have a member that's tv_sec. Maybe you mean struct timeval and struct timespec? : Quoting a response I got from Juliusz Chroboczek : (the author of Polipo) after reporting a compiler : warning: : = : |By the way, IEEE 1003.1-2003 says that tv_sec should be a time_t, : |hence by making it a long, FreeBSD and NetBSD are violating the POSI= X : |standard. Could you please file a bug report with them? : = : I didn't find any claims about FreeBSD being IEEE 1003.1-2003 : compliant and therefore didn't consider it a bug, but given that : the topic is *_t changes and time_t hasn't come up yet, : I'd like to mention it anyway. I think this is already fixed: /* * Structure returned by gettimeofday(2) system call, and used in other= calls. */ struct timeval { time_t tv_sec; /* seconds */ suseconds_t tv_usec; /* and microseconds */ }; as is timespec: struct timespec { time_t tv_sec; /* seconds */ long tv_nsec; /* and nanoseconds */ }; Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 19:09:12 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7ED6816A401 for ; Thu, 1 Feb 2007 19:09:12 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.18.16]) by mx1.freebsd.org (Postfix) with ESMTP id E83B013C4C2 for ; Thu, 1 Feb 2007 19:09:11 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 2595 invoked from network); 1 Feb 2007 19:09:10 -0000 Received: from unknown (HELO localhost) (775067@[217.50.150.85]) (envelope-sender ) by smtprelay04.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 1 Feb 2007 19:09:10 -0000 Date: Thu, 1 Feb 2007 20:08:44 +0100 From: Fabian Keil To: freebsd-hackers@freebsd.org Message-ID: <20070201200844.47626a58@localhost> In-Reply-To: <20070201.114444.29501661.imp@bsdimp.com> References: <86odofjyua.fsf@dwp.des.no> <20070131105024.L91177@fledge.watson.org> <20070131153114.4e76a6ea@localhost> <20070201.114444.29501661.imp@bsdimp.com> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd6.2) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_4b_y8_RYx58iUEOau3F0mB.; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Re: a question regarding 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, 01 Feb 2007 19:09:12 -0000 --Sig_4b_y8_RYx58iUEOau3F0mB. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "M. Warner Losh" wrote: > In message: <20070131153114.4e76a6ea@localhost> > Fabian Keil writes: > : Robert Watson wrote: > : > If we do decide to go ahead with the ABI change, there are a number o= f other=20 > : > things that should be done simultaneously, such as changing the uid a= nd gid=20 > : > fields to uid_t and gid_t. > :=20 > : struct tm's members could be changed as well. >=20 > struct tm doesn't have a member that's tv_sec. >=20 > Maybe you mean struct timeval and struct timespec? I did indeed. Sorry for the noise. Fabian --Sig_4b_y8_RYx58iUEOau3F0mB. Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwjrTBYqIVf93VJ0RAi7HAJ0S0Rv59O1FeB7Lj4hpA4KdkGwg2wCggVp/ S1MyM9AeUYropVQM35Y7bxM= =WsCX -----END PGP SIGNATURE----- --Sig_4b_y8_RYx58iUEOau3F0mB.-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 19:28:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F173116A402 for ; Thu, 1 Feb 2007 19:28:48 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id D921013C4A5 for ; Thu, 1 Feb 2007 19:28:48 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l11InHmA083405; Thu, 1 Feb 2007 10:49:17 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l11InHKx083404; Thu, 1 Feb 2007 10:49:17 -0800 (PST) (envelope-from rizzo) Date: Thu, 1 Feb 2007 10:49:17 -0800 From: Luigi Rizzo To: "M. Warner Losh" Message-ID: <20070201104917.C82313@xorpc.icir.org> References: <45BC3624.3000608@pacbell.net> <3B777B32-AB3A-4244-BBE1-9E11B287D78B@hursk.com> <20070128181132.GR927@turion.vk2pj.dyndns.org> <20070201.113851.689651534.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20070201.113851.689651534.imp@bsdimp.com>; from imp@bsdimp.com on Thu, Feb 01, 2007 at 11:38:51AM -0700 Cc: jon.passki@hursk.com, fbsd@metro.cx, freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 01 Feb 2007 19:28:49 -0000 On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: > In message: <20070128181132.GR927@turion.vk2pj.dyndns.org> > Peter Jeremy writes: > : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: > : >If the machine is a PXE-compliant device [2], it should have a GUID/ > : >UUID [1] available. This can be exposed by sysutil/hal [3] via the > : >smbios.system.uuid field. > : > : You can also get it via kenv(8) without needing any ports: > : # kenv smbios.system.uuid > : 9F345F4F-BEFC-D431-1340-61235A56DEF9 > > I wonder why the smbios stuff isn't exported via sysctls as well... and this is probably a lazy vendor :) smbios.bios.reldate="07/12/2006" smbios.bios.vendor="American Megatrends Inc." smbios.bios.version="P1.10" smbios.chassis.maker="To Be Filled By O.E.M." smbios.chassis.serial="To Be Filled By O.E.M." smbios.chassis.tag="To Be Filled By O.E.M." smbios.chassis.version="To Be Filled By O.E.M." smbios.planar.maker=" " smbios.planar.product="775i945GZ" smbios.planar.serial=" " smbios.planar.version=" " smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="To Be Filled By O.E.M." smbios.system.product="775i945GZ" smbios.system.serial="To Be Filled By O.E.M." smbios.system.uuid="00020003-0004-0005-0006-000700080009" smbios.system.version="To Be Filled By O.E.M." cheers luigi From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 1 19:47:32 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3AD816A406 for ; Thu, 1 Feb 2007 19:47:32 +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 3F2A913C4A7 for ; Thu, 1 Feb 2007 19:47:32 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l11JeQip063303; Thu, 1 Feb 2007 12:40:27 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 01 Feb 2007 12:40:57 -0700 (MST) Message-Id: <20070201.124057.709402517.imp@bsdimp.com> To: rizzo@icir.org From: "M. Warner Losh" In-Reply-To: <20070201104917.C82313@xorpc.icir.org> References: <20070128181132.GR927@turion.vk2pj.dyndns.org> <20070201.113851.689651534.imp@bsdimp.com> <20070201104917.C82313@xorpc.icir.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 01 Feb 2007 12:40:29 -0700 (MST) Cc: jon.passki@hursk.com, fbsd@metro.cx, freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 01 Feb 2007 19:47:32 -0000 In message: <20070201104917.C82313@xorpc.icir.org> Luigi Rizzo writes: : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: : > In message: <20070128181132.GR927@turion.vk2pj.dyndns.org> : > Peter Jeremy writes: : > : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: : > : >If the machine is a PXE-compliant device [2], it should have a GUID/ : > : >UUID [1] available. This can be exposed by sysutil/hal [3] via the : > : >smbios.system.uuid field. : > : : > : You can also get it via kenv(8) without needing any ports: : > : # kenv smbios.system.uuid : > : 9F345F4F-BEFC-D431-1340-61235A56DEF9 : > : > I wonder why the smbios stuff isn't exported via sysctls as well... : : and this is probably a lazy vendor :) : : smbios.bios.reldate="07/12/2006" : smbios.bios.vendor="American Megatrends Inc." : smbios.bios.version="P1.10" : smbios.chassis.maker="To Be Filled By O.E.M." : smbios.chassis.serial="To Be Filled By O.E.M." : smbios.chassis.tag="To Be Filled By O.E.M." : smbios.chassis.version="To Be Filled By O.E.M." : smbios.planar.maker=" " : smbios.planar.product="775i945GZ" : smbios.planar.serial=" " : smbios.planar.version=" " : smbios.socket.enabled="1" : smbios.socket.populated="1" : smbios.system.maker="To Be Filled By O.E.M." : smbios.system.product="775i945GZ" : smbios.system.serial="To Be Filled By O.E.M." : smbios.system.uuid="00020003-0004-0005-0006-000700080009" : smbios.system.version="To Be Filled By O.E.M." Heh! My comment though is why do we have to go to kenv when we could export these via sysctl, like everything else. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 05:41:58 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18E3616A400 for ; Fri, 2 Feb 2007 05:41:58 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: from smtp113.sbc.mail.mud.yahoo.com (smtp113.sbc.mail.mud.yahoo.com [68.142.198.212]) by mx1.freebsd.org (Postfix) with SMTP id CB74713C474 for ; Fri, 2 Feb 2007 05:41:57 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: (qmail 6506 invoked from network); 2 Feb 2007 05:41:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=aG3KHUIcNp1ChwSgSVKdWzJk+1stZXwI34/JHhoLIHXNAMsYC5PizKOXqqParlUv8boz+8G7FqfEDlh3N8CjOXTLJjmZGjJG/u3t67va1lckxqP69a24f8c3sTMRghUgtJwO60kj+/EQWNkIkl4HchaJxEkciQgcIRymbFHgAno= ; Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@71.146.53.89 with plain) by smtp113.sbc.mail.mud.yahoo.com with SMTP; 2 Feb 2007 05:41:55 -0000 X-YMail-OSG: Dc8l9lcVM1mN_JUk3ImlJpNy5qu9X.B1rY.FFabbWw5ay8aMbdF7VhjkhBOeBZEQ_VRod4uNjFvzuCMmekLSLkosDJtzy1K.8c5BprLb_owN4.7i.bDq.H0hePe6jHVSEwBd.5aNPf7p82Y- Message-ID: <45C2D000.3070300@pacbell.net> Date: Thu, 01 Feb 2007 21:45:36 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 6.1-RELEASE-p7; en-US; ja-JP; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <45BB72D6.9070809@pacbell.net> <86k5z3jylp.fsf@dwp.des.no> In-Reply-To: <86k5z3jylp.fsf@dwp.des.no> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org Subject: Re: sysctl(3) interface 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, 02 Feb 2007 05:41:58 -0000 At about the time of 1/31/2007 2:10 AM, Dag-Erling Smørgrav stated the following: > Daniel Rudy writes: >> I've been taking apart and analyzing the sysctl(8) program to gain a >> better insight into how to use the sysctl(3) interface. [...] >> It's using an oid of 0 and 2 to get something, then it comes up with 440 >> and then a sequence of numbers that are incrementing in a peculiar >> pattern. > > sysctl(8) uses undocumented interfaces to a) enumerate the nodes in > the sysctl tree and b) obtain the name of a node, given its OID. > >> So, my question is, how do I walk the tree to get the PnP info for all >> the devices in the system? > > man 3 devinfo > > DES A little too late since I already hacked the source for sysctl(8) and figured out how it works. Here's what I have: mib[0] = 0; Unused according to sys/sysctl.h. So, 0,1 - get name from oid. 0,2 - get first sysctl node/leaf? (I haven't used this one yet) 0,3 - get oid from name. 0,4 - get format for oid? (I haven't used this one yet either) At least that's that I have. I wrote a program based on that and it does work, quite well in fact. I am not concerned about portability since the software that I'm writing will run ONLY on FreeBSD and maybe some of the variants. -- Daniel Rudy From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 05:45:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1267516A405 for ; Fri, 2 Feb 2007 05:45:51 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: from smtp107.sbc.mail.mud.yahoo.com (smtp107.sbc.mail.mud.yahoo.com [68.142.198.206]) by mx1.freebsd.org (Postfix) with SMTP id CE07613C4BB for ; Fri, 2 Feb 2007 05:45:50 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: (qmail 96133 invoked from network); 2 Feb 2007 05:45:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=d8UoeWSHQDRMJiP3xT1zEXyz58PkA1OGq+KJCWLpxntOUq/PvUoMUwjhUE0YVLS4oNAJcRDPulZ3pvIc1Ow9cDK6iQecdvdA3lbQcr8eD4TLIQT9Dy+mHegkQG/MmWiAksPH+wQtihOJz9P3k4upIGPbntG719DkWMqTNMfNHM4= ; Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@71.146.53.89 with plain) by smtp107.sbc.mail.mud.yahoo.com with SMTP; 2 Feb 2007 05:45:50 -0000 X-YMail-OSG: mbCh5eEVM1mXvWNhCmR_Fwwl.Gb93I.TSxEP6XQqbggISmiKM6bGxXj6US6FsLv9SGvBkz3Fi_fLVWC2LG9MMFSyIa1uSFCSI5ohk4cnAGjl66MxQim.tIcXjp7pl7pwaHWMe8v1wfMJtl0- Message-ID: <45C2D0F7.3000007@pacbell.net> Date: Thu, 01 Feb 2007 21:49:43 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 6.1-RELEASE-p7; en-US; ja-JP; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: "M. Warner Losh" References: <20070128181132.GR927@turion.vk2pj.dyndns.org> <20070201.113851.689651534.imp@bsdimp.com> <20070201104917.C82313@xorpc.icir.org> <20070201.124057.709402517.imp@bsdimp.com> In-Reply-To: <20070201.124057.709402517.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: jon.passki@hursk.com, rizzo@icir.org, fbsd@metro.cx, freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 02 Feb 2007 05:45:51 -0000 At about the time of 2/1/2007 11:40 AM, M. Warner Losh stated the following: > In message: <20070201104917.C82313@xorpc.icir.org> > Luigi Rizzo writes: > : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: > : > In message: <20070128181132.GR927@turion.vk2pj.dyndns.org> > : > Peter Jeremy writes: > : > : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: > : > : >If the machine is a PXE-compliant device [2], it should have a GUID/ > : > : >UUID [1] available. This can be exposed by sysutil/hal [3] via the > : > : >smbios.system.uuid field. > : > : > : > : You can also get it via kenv(8) without needing any ports: > : > : # kenv smbios.system.uuid > : > : 9F345F4F-BEFC-D431-1340-61235A56DEF9 > : > > : > I wonder why the smbios stuff isn't exported via sysctls as well... > : > : and this is probably a lazy vendor :) > : > : smbios.bios.reldate="07/12/2006" > : smbios.bios.vendor="American Megatrends Inc." > : smbios.bios.version="P1.10" > : smbios.chassis.maker="To Be Filled By O.E.M." > : smbios.chassis.serial="To Be Filled By O.E.M." > : smbios.chassis.tag="To Be Filled By O.E.M." > : smbios.chassis.version="To Be Filled By O.E.M." > : smbios.planar.maker=" " > : smbios.planar.product="775i945GZ" > : smbios.planar.serial=" " > : smbios.planar.version=" " > : smbios.socket.enabled="1" > : smbios.socket.populated="1" > : smbios.system.maker="To Be Filled By O.E.M." > : smbios.system.product="775i945GZ" > : smbios.system.serial="To Be Filled By O.E.M." > : smbios.system.uuid="00020003-0004-0005-0006-000700080009" > : smbios.system.version="To Be Filled By O.E.M." > > Heh! > > My comment though is why do we have to go to kenv when we could > export these via sysctl, like everything else. > > Warner > _______________________________________________ > 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" > You know that's a good idea, but there is a problem with that.... None of this stuff appears on my system and I'm running 6.1. I can't even find dmidump anywhere on the system or in ports either. -- Daniel Rudy From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 06:20:56 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 04AF016A400 for ; Fri, 2 Feb 2007 06:20:56 +0000 (UTC) (envelope-from kazakov@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 8D3EC13C474 for ; Fri, 2 Feb 2007 06:20:55 +0000 (UTC) (envelope-from kazakov@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so667879uge for ; Thu, 01 Feb 2007 22:20:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bGslnEPmjbjJOz53rVEagVdyKy9xqWNnNxOHja+Y+r/anM1iJGTvRXvkmsQuLWTd3ZYWQm8zcKsG4meLbxdvRT1VtKLW87KTv48YiTLg/92JPXb5W1spSBjCqeFp4dFR9G5wDPArYS8VyWpfCaFbHIH9A0qsfraOQ1si2rZMSyk= Received: by 10.67.103.7 with SMTP id f7mr3914961ugm.1170397254604; Thu, 01 Feb 2007 22:20:54 -0800 (PST) Received: by 10.67.119.17 with HTTP; Thu, 1 Feb 2007 22:20:54 -0800 (PST) Message-ID: Date: Fri, 2 Feb 2007 15:20:54 +0900 From: "Artem Kazakov" To: "Brooks Davis" In-Reply-To: <20070201153132.GC67362@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070201153132.GC67362@lor.one-eyed-alien.net> Cc: FreeBSD Hackers , freebsd-questions@freebsd.org Subject: Re: diskless boot /usr/local/etc/rc.d/ scripts do not run, why? 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, 02 Feb 2007 06:20:56 -0000 Hi, Brooks! Thanks for the advice, it helped! > > I have to say that I use this loader.rc for network boot: > > load /boot/kernel/kernel > > echo \007\007 > > set console="vidconsole" > > autoboot > > Do you by chance have a /boot.config? It sounds like your system is > probably running on a serial console. I do not have boot.config and that machine has vga card and keyboard and etc. From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 07:06:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A12AA16A405 for ; Fri, 2 Feb 2007 07:06:57 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF4D13C481 for ; Fri, 2 Feb 2007 07:06:56 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l1276seC001183; Fri, 2 Feb 2007 18:06:54 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l1276sX5001182; Fri, 2 Feb 2007 18:06:54 +1100 (EST) (envelope-from peter) Date: Fri, 2 Feb 2007 18:06:54 +1100 From: Peter Jeremy To: Daniel Rudy Message-ID: <20070202070654.GD909@turion.vk2pj.dyndns.org> References: <20070128181132.GR927@turion.vk2pj.dyndns.org> <20070201.113851.689651534.imp@bsdimp.com> <20070201104917.C82313@xorpc.icir.org> <20070201.124057.709402517.imp@bsdimp.com> <45C2D0F7.3000007@pacbell.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <45C2D0F7.3000007@pacbell.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 02 Feb 2007 07:06:57 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: >None of this stuff appears on my system and I'm running 6.1. I can't >even find dmidump anywhere on the system or in ports either. Please elaborate. kenv(8) states that it first appeared in 4.1.1 and I don't recall seeing any reference to 'dmidump' in this thread. If you're referring to getting smbios data reported in kenv - that is up to your system/BIOS vendor: If they don't embed the information in the BIOS, FreeBSD can't report it. The response on my laptop is complete. My older whitebox desktops either don't have the data populated or don't report it at all. --=20 Peter Jeremy --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwuMO/opHv/APuIcRApppAKCvYPSiUp0CL8Yu0vXOv2iDLJnm7QCdETHZ PABAWbzNcU8OxscEwqEqYxY= =fQ9o -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 07:33:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69E2E16A400 for ; Fri, 2 Feb 2007 07:33:10 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 170AF13C474 for ; Fri, 2 Feb 2007 07:33:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1HCsus-0001RB-6u; Fri, 02 Feb 2007 09:33:02 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Peter Jeremy In-reply-to: <20070202070654.GD909@turion.vk2pj.dyndns.org> References: <20070128181132.GR927@turion.vk2pj.dyndns.org> <20070201.113851.689651534.imp@bsdimp.com> <20070201104917.C82313@xorpc.icir.org> <20070201.124057.709402517.imp@bsdimp.com> <45C2D0F7.3000007@pacbell.net> <20070202070654.GD909@turion.vk2pj.dyndns.org> Comments: In-reply-to Peter Jeremy message dated "Fri, 02 Feb 2007 18:06:54 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Feb 2007 09:33:02 +0200 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, Daniel Rudy Subject: Re: unique hardware identification 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, 02 Feb 2007 07:33:10 -0000 > > --ikeVEW9yuYc//A+q > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: > >None of this stuff appears on my system and I'm running 6.1. I can't > >even find dmidump anywhere on the system or in ports either. > > Please elaborate. kenv(8) states that it first appeared in 4.1.1 and > I don't recall seeing any reference to 'dmidump' in this thread. > > If you're referring to getting smbios data reported in kenv - that is > up to your system/BIOS vendor: If they don't embed the information in > the BIOS, FreeBSD can't report it. The response on my laptop is > complete. My older whitebox desktops either don't have the data > populated or don't report it at all. kenv appeared in 4.1, the smbios. stuff only appeared midway in 6.1 danny From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 09:53:45 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85AED16A401 for ; Fri, 2 Feb 2007 09:53:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 4524313C481 for ; Fri, 2 Feb 2007 09:53:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 325FC2081; Fri, 2 Feb 2007 10:53:36 +0100 (CET) X-Spam-Tests: AWL,MAILTO_TO_SPAM_ADDR X-Spam-Learn: disabled X-Spam-Score: 0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 1FC7F2049; Fri, 2 Feb 2007 10:53:35 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id 7DC97B815; Fri, 2 Feb 2007 10:53:35 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Daniel Rudy References: <45BB72D6.9070809@pacbell.net> <86k5z3jylp.fsf@dwp.des.no> <45C2D000.3070300@pacbell.net> Date: Fri, 02 Feb 2007 10:53:35 +0100 In-Reply-To: <45C2D000.3070300@pacbell.net> (Daniel Rudy's message of "Thu, 01 Feb 2007 21:45:36 -0800") Message-ID: <863b5olwbk.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: sysctl(3) interface 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, 02 Feb 2007 09:53:45 -0000 Daniel Rudy writes: > Dag-Erling Sm=F8rgrav writes: > > man 3 devinfo > A little too late since I already hacked the source for sysctl(8) and > figured out how it works. The dev sysctl tree contains only a subset of the information available through devinfo(3). DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 16:39:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C952316A400 for ; Fri, 2 Feb 2007 16:39:31 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: from smtp105.sbc.mail.mud.yahoo.com (smtp105.sbc.mail.mud.yahoo.com [68.142.198.204]) by mx1.freebsd.org (Postfix) with SMTP id 8B02013C441 for ; Fri, 2 Feb 2007 16:39:31 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: (qmail 49377 invoked from network); 2 Feb 2007 16:39:30 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=h8pzJcGe8URDMR8WJLXsc8XK0H1Mhkh3JFMB1t+LR7PnrNz68bomkpDRQN4aLPE+gPIgRSJuU65hQchTglKo74HYQvgzM6SFItojDrSvPeS8Fa4tBHZqRulZ/t85s4BgqGDqqOKOuBL/LDU+gDlPgpjxg1sap/S/ZCsGKQODZjQ= ; Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@71.146.53.89 with plain) by smtp105.sbc.mail.mud.yahoo.com with SMTP; 2 Feb 2007 16:39:30 -0000 X-YMail-OSG: TTyPWyIVM1nvLDPiPCdvwfFrn01tlivzgmYXq0xWhc48DawRXqi.siCA7_xsb1q3fZotPd60QTqLzqf88C82jVTGq5z4Pb9VLT1Ti5mW0frgtJiSRrtgyVuyeQI07a0RiAWYgKe0Bcho8SyhRqeX8PiW5KmIOBy.3iLKext3TuPWYaDUqkfH7VnjaaMv Message-ID: <45C36A2C.10408@pacbell.net> Date: Fri, 02 Feb 2007 08:43:24 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 6.1-RELEASE-p7; en-US; ja-JP; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Danny Braniss References: <20070128181132.GR927@turion.vk2pj.dyndns.org> <20070201.113851.689651534.imp@bsdimp.com> <20070201104917.C82313@xorpc.icir.org> <20070201.124057.709402517.imp@bsdimp.com> <45C2D0F7.3000007@pacbell.net> <20070202070654.GD909@turion.vk2pj.dyndns.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: unique hardware identification 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, 02 Feb 2007 16:39:31 -0000 At about the time of 2/1/2007 11:33 PM, Danny Braniss stated the following: >> --ikeVEW9yuYc//A+q >> Content-Type: text/plain; charset=us-ascii >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: >>> None of this stuff appears on my system and I'm running 6.1. I can't >>> even find dmidump anywhere on the system or in ports either. >> Please elaborate. kenv(8) states that it first appeared in 4.1.1 and >> I don't recall seeing any reference to 'dmidump' in this thread. >> >> If you're referring to getting smbios data reported in kenv - that is >> up to your system/BIOS vendor: If they don't embed the information in >> the BIOS, FreeBSD can't report it. The response on my laptop is >> complete. My older whitebox desktops either don't have the data >> populated or don't report it at all. > > kenv appeared in 4.1, the smbios. stuff only appeared midway in 6.1 > > danny > That would explain it then. I'm running 6.1 release with the security updates, not stable. -- Daniel Rudy From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 17:00:34 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 127EE16A407 for ; Fri, 2 Feb 2007 17:00:34 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 90D4813C461 for ; Fri, 2 Feb 2007 17:00:33 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wvmzsx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l12H0KuY096687; Fri, 2 Feb 2007 18:00:26 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l12H0KIv096686; Fri, 2 Feb 2007 18:00:20 +0100 (CET) (envelope-from olli) Date: Fri, 2 Feb 2007 18:00:20 +0100 (CET) Message-Id: <200702021700.l12H0KIv096686@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, dr2867@pacbell.net, peterjeremy@optushome.com.au In-Reply-To: <20070202070654.GD909@turion.vk2pj.dyndns.org> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 02 Feb 2007 18:00:30 +0100 (CET) Cc: Subject: Re: unique hardware identification X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, dr2867@pacbell.net, peterjeremy@optushome.com.au List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 17:00:34 -0000 Peter Jeremy wrote: > Daniel Rudy wrote: > > None of this stuff appears on my system and I'm running 6.1. I can't > > even find dmidump anywhere on the system or in ports either. > > Please elaborate. kenv(8) states that it first appeared in 4.1.1 and > I don't recall seeing any reference to 'dmidump' in this thread. For retrieving DMI information, please see sysutils/dmidecode in the ports collection. It works fine on the HP Proliant machines here, it even reports the exact population of the RAM slots and other things, which makes remote administration easier. Of course, it only works on machines with DMI-compliant BIOS interface. If you don't get SMBIOS information, I very much doubt that it'll provide DMI information either. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 22:43:30 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D28816A401 for ; Fri, 2 Feb 2007 22:43:30 +0000 (UTC) (envelope-from jgrosch@mooseriver.com) Received: from gdead.mooseriver.com (gdead.mooseriver.com [205.166.121.45]) by mx1.freebsd.org (Postfix) with ESMTP id 04F8C13C474 for ; Fri, 2 Feb 2007 22:43:29 +0000 (UTC) (envelope-from jgrosch@mooseriver.com) Received: by gdead.mooseriver.com (Postfix, from userid 2010) id 826A93DE1EF; Fri, 2 Feb 2007 14:22:49 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on gdead.mooseriver.com X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_05, DNS_FROM_RFC_WHOIS,FORGED_RCVD_HELO autolearn=no version=3.1.7 Received: from mooseriver.com (adsl-75-61-201-134.dsl.pltn13.sbcglobal.net [75.61.201.134]) by gdead.mooseriver.com (Postfix) with ESMTP id 4C7433DE1A1; Fri, 2 Feb 2007 14:22:44 -0800 (PST) Received: by mooseriver.com (Postfix, from userid 200) id 17B4C2E5C14; Fri, 2 Feb 2007 14:22:44 -0800 (PST) Date: Fri, 2 Feb 2007 14:22:44 -0800 From: Josef Grosch To: questions@freebsd.org Message-ID: <20070202222244.GA84430@mooseriver.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Organization: Moose River, LLC Cc: hackers@freebsd.org Subject: Fast SCSI RAID controller X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jgrosch@MooseRiver.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 22:43:30 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Can anyone suggest a fast SCSI RAID controller for FreeBSD 6.2 ? Our vendor is having trouble with the latest Adaptec Josef --=20 Josef Grosch | Another day closer to a | FreeBSD 6.2 jgrosch@MooseRiver.com | Micro$oft free world | Berkeley, Ca. --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFFw7myy8prLS1GYSERAqR0AKDMFa98U73rQjiAkSm7uoFdH8KzGQCfdIwM 3h+De1UZv5U9x3B9WTSZzgM= =AfIC -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 23:42:49 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D87316A413 for ; Fri, 2 Feb 2007 23:42:49 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id BA19B13C474 for ; Fri, 2 Feb 2007 23:42:48 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.7/jtpda-5.4) with ESMTP id l12NgOES084504 ; Sat, 3 Feb 2007 00:42:28 +0100 (CET) X-Ids: 164 Received: by parthe.lpthe.jussieu.fr (Postfix, from userid 99) id 8736BA0880; Sat, 3 Feb 2007 00:42:33 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on parthe.lpthe.jussieu.fr X-Spam-Level: X-Spam-Status: No, score=-101.3 required=10.0 tests=AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.1.7 Received: from asmodee.lpthe.jussieu.fr (asmodee.lpthe.jussieu.fr [134.157.10.34]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id CB161A0259; Sat, 3 Feb 2007 00:42:31 +0100 (CET) Received: by asmodee.lpthe.jussieu.fr (Postfix, from userid 10093) id 1145E4760; Sat, 3 Feb 2007 00:42:21 +0100 (CET) Date: Sat, 3 Feb 2007 00:42:21 +0100 From: Michel Talon To: freebsd-hackers@freebsd.org Message-ID: <20070202234220.GA9505@asmodee.lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.164]); Sat, 03 Feb 2007 00:42:28 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.5/2517/Fri Feb 2 17:47:59 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 45C3CC60.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Mailman-Approved-At: Sat, 03 Feb 2007 03:07:38 +0000 Cc: Massimo Lusetti , Benjamin Close , Florent Thoumie Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller 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, 02 Feb 2007 23:42:49 -0000 > A new version of the driver is up which fixes the firmware issues. > Seems the wpi-firmware-kmod port was creating corrupt modules. > Things should work much better now. Download at the same place, file: > 20070131-wpi-freebsd.tar.gz Unfortunately, i must report that this last version still does not work for me. Even worse the computer is flooded with error messages to the point it is hard to reboot. These are like so: Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=92 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=93 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=94 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 14 status 1 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=95 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=96 flags=0 type=132 len=16 Feb 3 00:11:31 rose kernel: scan finished nchan=14 status=1 chan=14 Feb 3 00:11:31 rose kernel: rx notification qid=4 idx=136 flags=0 type=128 len=8 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=97 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=98 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 36 status 1 continually repeating and the WLAN light never lights up. For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. -- Michel Talon From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 04:31:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AAC1816A400 for ; Sat, 3 Feb 2007 04:31:22 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 47ADB13C461 for ; Sat, 3 Feb 2007 04:31:22 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1429379nfc for ; Fri, 02 Feb 2007 20:31:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kEkwFGAr302RnuR9z+9ZKelEbNWeg/Nsu1P1RRPN40RpVokEShvWOEkxjdy1C9TiycoPXpVRW+SiDsQnOq9V5FR1Qoi8F1BJAKEz3/SrqxYNYDBpZJUTXsRhXkbB2aE4lOmV8zQKzJY6eVs0RkuuYMviDGGxyjsWxGteZ09nQE0= Received: by 10.78.158.11 with SMTP id g11mr884853hue.1170477080684; Fri, 02 Feb 2007 20:31:20 -0800 (PST) Received: by 10.78.151.6 with HTTP; Fri, 2 Feb 2007 20:31:20 -0800 (PST) Message-ID: <11167f520702022031g4829b957i70006603de946b6e@mail.gmail.com> Date: Fri, 2 Feb 2007 22:31:20 -0600 From: "Sam Fourman Jr." To: "Michel Talon" In-Reply-To: <20070202234220.GA9505@asmodee.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070202234220.GA9505@asmodee.lpthe.jussieu.fr> Cc: freebsd-hackers@freebsd.org Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller 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, 03 Feb 2007 04:31:22 -0000 Michel, I was told a few days ago that those messages are nothing more than debug messages, and that is how it is supposed to work. Sam Fourman Jr. On 2/2/07, Michel Talon wrote: > > A new version of the driver is up which fixes the firmware issues. > > Seems the wpi-firmware-kmod port was creating corrupt modules. > > Things should work much better now. Download at the same place, file: > > 20070131-wpi-freebsd.tar.gz > > Unfortunately, i must report that this last version still does not work for > me. Even worse the computer is flooded with error messages to the point it is > hard to reboot. > These are like so: > Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=92 flags=0 type=131 > len=20 > Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=93 flags=0 > type=157 len=244 > Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=94 > flags=0 type=130 len=24 > Feb 3 00:11:31 rose kernel: scanning channel 14 > status 1 > Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=95 flags=0 > type=131 len=20 > Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=96 > flags=0 type=132 len=16 Feb 3 00:11:31 rose kernel: scan finished nchan=14 > status=1 chan=14 > Feb 3 00:11:31 rose kernel: rx notification qid=4 idx=136 > flags=0 type=128 len=8 > Feb 3 00:11:31 rose kernel: rx notification qid=96 > idx=97 flags=0 type=157 len=244 > Feb 3 00:11:31 rose kernel: rx notification > qid=96 idx=98 flags=0 type=130 len=24 > Feb 3 00:11:31 rose kernel: scanning > channel 36 status 1 > continually repeating and the WLAN light never lights up. > > For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof > Gilbert Cao is the only one that works, and works very well. I am just using it > now. My computer is a Sony Vaio VGN C1 in 32 bits mode. > > -- > > Michel Talon > _______________________________________________ > 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 Sat Feb 3 11:56:34 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27ACF16A405; Sat, 3 Feb 2007 11:56:34 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from com1.ht-systems.ru (com1.ht-systems.ru [83.97.104.204]) by mx1.freebsd.org (Postfix) with ESMTP id D0CDC13C4B7; Sat, 3 Feb 2007 11:56:33 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [83.97.105.125] (helo=phonon.SpringDaemons.com ident=postfix) by com1.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1HDIxY-00020g-Ty; Sat, 03 Feb 2007 14:21:33 +0300 Received: from localhost (localhost [IPv6:::1]) by phonon.SpringDaemons.com (Postfix) with SMTP id 561F11148B; Sat, 3 Feb 2007 14:30:18 +0300 (MSK) Date: Sat, 3 Feb 2007 14:30:13 +0300 From: Stanislav Sedov To: jgrosch@MooseRiver.com Message-Id: <20070203143013.f053405c.stas@FreeBSD.org> In-Reply-To: <20070202222244.GA84430@mooseriver.com> References: <20070202222244.GA84430@mooseriver.com> Organization: The FreeBSD Project X-Mailer: carrier-pigeon X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-ICQ: 208105021 X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Sat__3_Feb_2007_14_30_13_+0300_=9xO1MCrrAt9q3Ew" X-Spam-Flag: SKIP Cc: hackers@freebsd.org, questions@freebsd.org Subject: Re: Fast SCSI RAID controller 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, 03 Feb 2007 11:56:34 -0000 --Signature=_Sat__3_Feb_2007_14_30_13_+0300_=9xO1MCrrAt9q3Ew Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Fri, 2 Feb 2007 14:22:44 -0800 Josef Grosch mentioned: > Can anyone suggest a fast SCSI RAID controller for FreeBSD 6.2 ? Our vendor > is having trouble with the latest Adaptec > LSI Logic produce very good SCSI controllers that work just fine with amr (4). -- Stanislav Sedov ST4096-RIPE --Signature=_Sat__3_Feb_2007_14_30_13_+0300_=9xO1MCrrAt9q3Ew Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFxHJJK/VZk+smlYERAkoBAKCBSVio8NbdYfez9LFr79Y5n84XYACeLgFd kbPYHIcSq98SCMf5qtWjELI= =YXBv -----END PGP SIGNATURE----- --Signature=_Sat__3_Feb_2007_14_30_13_+0300_=9xO1MCrrAt9q3Ew-- From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 09:04:03 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC3A516A403 for ; Sat, 3 Feb 2007 09:04:03 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (dsl081-227-250.chi1.dsl.speakeasy.net [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 34D2413C441 for ; Sat, 3 Feb 2007 09:04:01 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.13.8/8.12.11) with ESMTP id l131W3xp061604; Fri, 2 Feb 2007 19:32:03 -0600 (CST) Message-Id: <6.0.0.22.2.20070202193036.024c2ac0@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 02 Feb 2007 19:31:56 -0600 To: jgrosch@MooseRiver.com, questions@freebsd.org From: Derek Ragona In-Reply-To: <20070202222244.GA84430@mooseriver.com> References: <20070202222244.GA84430@mooseriver.com> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No X-Mailman-Approved-At: Sat, 03 Feb 2007 14:56:14 +0000 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Re: Fast SCSI RAID controller 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, 03 Feb 2007 09:04:03 -0000 Take a look at LSI controllers. With any SCSI make sure you get one for the correct slot you have, i.e. PCI, PCI-X, etc. -Derek At 04:22 PM 2/2/2007, Josef Grosch wrote: >Can anyone suggest a fast SCSI RAID controller for FreeBSD 6.2 ? Our vendor >is having trouble with the latest Adaptec > > >Josef > >-- >Josef Grosch | Another day closer to a | FreeBSD 6.2 >jgrosch@MooseRiver.com | Micro$oft free world | Berkeley, Ca. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 16:40:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C052D16A5AE for ; Sat, 3 Feb 2007 16:40:46 +0000 (UTC) (envelope-from cats@catslab.com) Received: from racoon.catslab.com (racoon.catslab.com [88.191.13.229]) by mx1.freebsd.org (Postfix) with SMTP id 3299F13C48D for ; Sat, 3 Feb 2007 16:40:45 +0000 (UTC) (envelope-from cats@catslab.com) Received: (qmail 3101 invoked by uid 2010); 3 Feb 2007 16:14:04 -0000 Received: from 81.56.179.92 by racoon.catslab.com (envelope-from , uid 2009) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.2/1524. spamassassin: 3.1.1. perlscan: 1.25-st-qms. Clear:RC:0(81.56.179.92):SA:0(-2.5/3.5):. Processed in 9.158592 secs); 03 Feb 2007 16:14:04 -0000 X-Spam-Status: No, hits=-2.5 required=3.5 X-Antivirus-CATSLAB-COM-Mail-From: cats@catslab.com via racoon.catslab.com X-Antivirus-CATSLAB-COM: 1.25-st-qms (Clear:RC:0(81.56.179.92):SA:0(-2.5/3.5):. Processed in 9.158592 secs Process 3091) Received: from spyro.catslab.com (HELO poppa) (cats@catslab.com@81.56.179.92) by racoon.catslab.com with SMTP; 3 Feb 2007 16:13:54 -0000 From: Cats To: X-Mailer: PocoMail 4.1 (3650) - Licensed Version X-URL: http://www.pocomail.com/ Date: Sat, 3 Feb 2007 17:10:21 +0100 Message-ID: <200723171021.907086@poppa> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Geode SC1100 i2c bus 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, 03 Feb 2007 16:40:46 -0000 Hello all, I've been looking for some technical infos and/or driver for the i2c bus on= the Geode SC1100 processor under FreeBSD 6. I found i2c stuff, tried to compile a kernel with it but nothing showed up.= I had a look at the sources and apparently it doesn't hook up to isa bus. From the geode databook, on page 11, i2c bus that is called ACB bus is in= the superIO block. This superIO block is attached on the isa bus. The ACB is at the same level than Uart, so I had a look at sio source and= got a big headache. I'm not really used to drivers nor kernel programming stuff, that's why I= need your help. My goal is to use the i2c bus on a wrap board to supervise voltages, pilot a= servo motor and so on. I do not want to use USB because it's easier with i2c and I already have i2c= hardware ready. Does someone already tried to use i2c bus on a wrap board under FreeBSD ? I had a look at openbsd and looks like it has already i2c support, but I= ain't had time to build a system and test it on the wrap. For now all my wrap boards run flawlessly with FreeBSD. I searched the mailing list archive but did not found something that could= help me. Remember I'm not really good at writing drivers stuff. I'd like to learn but I have no start point. Thanks for your help. Regards, Cedric From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 18:50:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BB5D16A405 for ; Sat, 3 Feb 2007 18:50:15 +0000 (UTC) (envelope-from freebsd-hackers@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.freebsd.org (Postfix) with ESMTP id 87E4913C4AC for ; Sat, 3 Feb 2007 18:50:15 +0000 (UTC) (envelope-from freebsd-hackers@dino.sk) Received: from [192.168.16.241] (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by bsd.dino.sk with esmtp; Sat, 03 Feb 2007 19:45:06 +0100 id 00000036.45C4D832.00015D33 From: Milan Obuch To: freebsd-hackers@freebsd.org Date: Sat, 3 Feb 2007 19:39:59 +0100 User-Agent: KMail/1.9.5 References: <200723171021.907086@poppa> In-Reply-To: <200723171021.907086@poppa> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702031940.00128.freebsd-hackers@dino.sk> Subject: Re: Geode SC1100 i2c bus 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, 03 Feb 2007 18:50:16 -0000 On Saturday 03 February 2007 17:10, Cats wrote: > Hello all, > Hi, > I've been looking for some technical infos and/or driver for the i2c bus on > the Geode SC1100 processor under FreeBSD 6. > I tried it too, but no success yet, partially due to ENOTIME :( > I found i2c stuff, tried to compile a kernel with it but nothing showed up. > I had a look at the sources and apparently it doesn't hook up to isa bus. > There is no driver yet. > From the geode databook, on page 11, i2c bus that is called ACB bus is in > the superIO block. This superIO block is attached on the isa bus. > Geode has hardware i2c controller. > The ACB is at the same level than Uart, so I had a look at sio source and > got a big headache. I'm not really used to drivers nor kernel programming > stuff, that's why I need your help. > Why do you compare ACB and UART? In FreeBSD, sio is serial i/o controller, not superIO, maybe you are confused... ACB and UART does not have much in common... > My goal is to use the i2c bus on a wrap board to supervise voltages, pilot > a servo motor and so on. I do not want to use USB because it's easier with > i2c and I already have i2c hardware ready. > > Does someone already tried to use i2c bus on a wrap board under FreeBSD ? > Well, the best I achieved was working bit-banged i2c for wrap's onboard lm77. I was able to read temperature and that's all. Unfortunatelly, external i2c bus works only with geode's hardware i2c controller, which I did not got into working state, internal bus can be switched into gpio mode, which works for me. But that is not really usefull. > I had a look at openbsd and looks like it has already i2c support, but I > ain't had time to build a system and test it on the wrap. For now all my > wrap boards run flawlessly with FreeBSD. > I looked there too, but OpenBSD has different infrastructure, and porting is not easy, at least for me. They have even some more Geode's resources working, but, again, porting is not easy for me. > I searched the mailing list archive but did not found something that could > help me. Remember I'm not really good at writing drivers stuff. I'd like to > learn but I have no start point. > All I can offer is bit-banged stuff, which I got into working state... Regards, Milan -- This address is used only for mailing list response. Do not send any personal messages to it, use milan in address instead. From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 19:53:01 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81F2616A401 for ; Sat, 3 Feb 2007 19:53:01 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3629613C442 for ; Sat, 3 Feb 2007 19:53:01 +0000 (UTC) (envelope-from frank@exit.com) Received: from jill.exit.com (jill.exit.com [206.223.0.4]) by tinker.exit.com (8.13.8/8.13.8) with ESMTP id l13JKHPx012018 for ; Sat, 3 Feb 2007 11:20:17 -0800 (PST) (envelope-from frank@exit.com) Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.13.8/8.13.8) with ESMTP id l13JKHNp022847 for ; Sat, 3 Feb 2007 11:20:17 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.13.8/8.13.8/Submit) id l13JKHAJ022846 for hackers@freebsd.org; Sat, 3 Feb 2007 11:20:17 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: hackers Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Sat, 03 Feb 2007 11:20:17 -0800 Message-Id: <1170530417.20968.14.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.88.6/2522/Sat Feb 3 08:30:44 2007 on tinker.exit.com X-Virus-Status: Clean Cc: Subject: UFS2 version of ffsrecov. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2007 19:53:01 -0000 No, I'm not looking for one, I'm releasing one. This is a heavily modified version of John-Mark Gurney's ffsrecov, adapted to use libufs and to work (only) with UFS2 file systems. I call it ffs2recov and it is available at http://www.exit.com/Archives/FreeBSD/ffs2recov.tar.bz2 I wrote this a couple of years ago so that I could recover a file system that had been stomped by a misconfigured RAID controller. It worked well enough for me to recover a couple of hundred gigabytes worth of data, which was a great relief (although some stuff was gone forever, sigh). I had intended to polish it up and release it long before now, but I've never managed to get around to doing the polishing. In particular, while it has a nice little summary of implemented options, the manpage needs a lot of work. On the positive side, however, I extended it to be a lot more robust in the face of corrupt pointers and file system offsets, so it doesn't just fall over when it sees garbage in a block address or whatnot. I'm releasing it under the BSD two-clause license, with due credit to John-Mark. It's my hope that someone else will take it, clean it up a bit, rewrite the manpage and maybe make a port out of it. If you do and you need a place to host the distfile, let me know. In any event, it's a tool that people often need. Enjoy. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 20:37:38 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FAA316A402 for ; Sat, 3 Feb 2007 20:37:38 +0000 (UTC) (envelope-from hika@bsdmon.com) Received: from bigfugu.bsdmon.com (137.128.101-84.rev.gaoland.net [84.101.128.137]) by mx1.freebsd.org (Postfix) with ESMTP id B100513C478 for ; Sat, 3 Feb 2007 20:37:36 +0000 (UTC) (envelope-from hika@bsdmon.com) Received: from localhost (localhost [127.0.0.1]) by bigfugu.bsdmon.com (Postfix) with ESMTP id 847F462E5 for ; Sat, 3 Feb 2007 16:43:35 +0100 (CET) Received: from bigfugu.bsdmon.com ([127.0.0.1]) by localhost (bigfugu.bsdmon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94393-11 for ; Sat, 3 Feb 2007 16:43:33 +0100 (CET) Received: from vaio.bsdmon.com (unknown [192.168.0.14]) by bigfugu.bsdmon.com (Postfix) with ESMTP id 8DAD662E4 for ; Sat, 3 Feb 2007 16:43:32 +0100 (CET) Date: Sat, 3 Feb 2007 16:45:00 +0100 From: Gilbert Cao To: freebsd-hackers@freebsd.org Message-ID: <20070203154438.GA1207@bsdmon.com> References: <45A0F739.3030202@clearchain.com> <499c70c0701201038w6960174n3006ffd525f17bf6@mail.gmail.com> <20070124204443.GA1107@bsdmon.com> <45B9F697.1090402@clearchain.com> <20070127101900.GB1099@bsdmon.com> <11167f520701271114j66f82398h83c43885b9d25e12@mail.gmail.com> <45C0B271.4040100@clearchain.com> <45C0B33B.9000807@FreeBSD.org> <11167f520702010148w4cb84122r6412c2d8eebade74@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11167f520702010148w4cb84122r6412c2d8eebade74@mail.gmail.com> X-Operating-System: FreeBSD 6.2-RELEASE i386 Organization: BSDMon X-GPG-Key: http://www.bsdmon.com/public_key.gpg User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: amavisd-new at bsdmon.com Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller 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, 03 Feb 2007 20:37:38 -0000 (Sorry hackers, I have forgotten you, and here is my previous post below to freebsd-drivers) On Thu, Feb 01, 2007 at 03:48:49AM -0600, Sam Fourman Jr. wrote: > I installed 20070131-wpi-freebsd.tar.gz (file date was 2-1-2007 on the > website) > > I am using a fresh install of 6.2 REALESE > > when I try ifconfig wpi0 up > I get a infinite loop and looks like it is scanning channels > > scanning channel 6 status 1 > a bunch of rx notifications > > the trouble is the loop never ends > > > Sam Fourman Jr. I tried the wpi 20070131 driver. It seems that I have the same problem as the previous version (20070125). According to the /var/log/messages below, no AP associated, and still scanning. Moreover, those 4 lines seems suspicious. Feb 3 11:45:41 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Feb 3 11:45:41 vaio kernel: wpi0: [GIANT-LOCKED] Feb 3 11:45:41 vaio kernel: wpi0: 11a rates: Feb 3 11:45:41 vaio kernel: wpi0: 11b rates: In the current "custom" version I have, I have the following lines : Feb 3 12:02:59 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Feb 3 12:02:59 vaio kernel: wpi0: [GIANT-LOCKED] Feb 3 12:02:59 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Feb 3 12:02:59 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Feb 3 12:02:59 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Here is the /var/log/messages sample. Feb 3 11:45:41 vaio kernel: wpi0: mem 0xcc000000-0xcc000fff irq 18 at device 0.0 on pci6 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 44, alignment: 4096 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 245760, alignment: 4096 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 512, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: channel 1 pwr1 0x007c pwr2 0x007a Feb 3 11:45:41 vaio kernel: channel 2 pwr1 0x0077 pwr2 0x007c Feb 3 11:45:41 vaio kernel: channel 3 pwr1 0x008b pwr2 0x008d Feb 3 11:45:41 vaio kernel: channel 4 pwr1 0x008f pwr2 0x008a Feb 3 11:45:41 vaio kernel: channel 5 pwr1 0x0000 pwr2 0x0000 Feb 3 11:45:41 vaio kernel: channel 6 pwr1 0x0080 pwr2 0x007f Feb 3 11:45:41 vaio kernel: channel 7 pwr1 0x007f pwr2 0x0080 Feb 3 11:45:41 vaio kernel: channel 8 pwr1 0x0085 pwr2 0x0085 Feb 3 11:45:41 vaio kernel: channel 9 pwr1 0x0086 pwr2 0x0085 Feb 3 11:45:41 vaio kernel: channel 10 pwr1 0x0000 pwr2 0x0000 Feb 3 11:45:41 vaio kernel: channel 11 pwr1 0xfffe pwr2 0xfffe Feb 3 11:45:41 vaio kernel: channel 12 pwr1 0xffff pwr2 0xfffe Feb 3 11:45:41 vaio kernel: channel 13 pwr1 0xfffe pwr2 0xfffe Feb 3 11:45:41 vaio kernel: channel 14 pwr1 0xffff pwr2 0xfffe Feb 3 11:45:41 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Feb 3 11:45:41 vaio kernel: wpi0: [GIANT-LOCKED] Feb 3 11:45:41 vaio kernel: wpi0: 11a rates: Feb 3 11:45:41 vaio kernel: wpi0: 11b rates: Feb 3 11:45:41 vaio kernel: setting h/w config 1200 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:41 vaio last message repeated 2 times Feb 3 11:45:41 vaio kernel: firmware status=0xffff0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: firmware status=0xffff0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: rx notification qid=80 idx=0 flags=0 type=1 len=36 Feb 3 11:45:41 vaio kernel: microcode alive notification version 10d00 alive 1 Feb 3 11:45:41 vaio kernel: temperature -195 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=0 flags=0 type=176 len=4 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=1 flags=0 type=119 len=4 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=2 flags=0 type=155 len=4 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=3 flags=0 type=16 len=4 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=4 flags=0 type=24 len=8 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=5 flags=0 type=72 len=4 Feb 3 11:45:41 vaio kernel: rx notification qid=4 idx=6 flags=2d type=128 len=8 Feb 3 11:45:41 vaio kernel: rx notification qid=80 idx=1 flags=0 type=157 len=244 Feb 3 11:45:41 vaio kernel: rx notification qid=80 idx=2 flags=0 type=130 len=24 Feb 3 11:45:41 vaio kernel: scanning channel 1 status 1 Feb 3 11:45:41 vaio kernel: setting h/w config 1200 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:41 vaio last message repeated 2 times Feb 3 11:45:41 vaio kernel: firmware status=0xffff0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: firmware status=0xffff0000 need val=0x40400000 Feb 3 11:45:41 vaio kernel: wpi0: fatal firmware error Feb 3 11:45:41 vaio kernel: ((Software Error)) Feb 3 11:45:41 vaio kernel: wpi0: timeout resetting Rx ring Feb 3 11:45:42 vaio kernel: wpi0: timeout waiting for adapter to initialize Feb 3 11:45:42 vaio kernel: setting h/w config 1200 Feb 3 11:45:42 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:42 vaio last message repeated 2 times Feb 3 11:45:42 vaio kernel: firmware status=0xffff0000 need val=0x40400000 Feb 3 11:45:42 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:42 vaio kernel: firmware status=0xbfbf0000 need val=0x40400000 Feb 3 11:45:42 vaio kernel: firmware status=0xffff0000 need val=0x40400000 Feb 3 11:45:42 vaio kernel: rx notification qid=80 idx=0 flags=0 type=1 len=36 Feb 3 11:45:42 vaio kernel: microcode alive notification version 10d00 alive 1 Feb 3 11:45:42 vaio kernel: temperature -188 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=0 flags=0 type=176 len=4 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=1 flags=0 type=119 len=4 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=2 flags=0 type=155 len=4 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=3 flags=0 type=16 len=4 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=4 flags=0 type=24 len=8 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=5 flags=0 type=72 len=4 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=6 flags=2d type=128 len=8 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=1 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=2 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 1 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=3 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=4 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=5 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 2 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=6 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=7 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=8 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 3 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=9 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=10 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=11 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 4 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=12 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=13 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=14 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 5 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=15 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=16 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=17 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 6 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=18 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=19 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=20 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 7 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=21 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=22 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=23 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 8 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=24 flags=2 type=27 len=124 Feb 3 11:45:43 vaio kernel: rx intr: idx=31 len=124 stat len=88 rssi=24 rate=a chan=8 tstamp=61334 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=25 flags=2 type=27 len=152 Feb 3 11:45:43 vaio kernel: rx intr: idx=32 len=152 stat len=114 rssi=21 rate=a chan=8 tstamp=62620 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=26 flags=2 type=27 len=152 Feb 3 11:45:43 vaio kernel: rx intr: idx=33 len=152 stat len=114 rssi=22 rate=a chan=8 tstamp=63852 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=27 flags=2 type=27 len=164 Feb 3 11:45:43 vaio kernel: rx intr: idx=34 len=164 stat len=126 rssi=21 rate=a chan=8 tstamp=65207 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=28 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=29 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=30 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 9 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=31 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=32 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=33 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 10 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=34 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=35 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=36 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 11 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=37 flags=2 type=27 len=152 Feb 3 11:45:43 vaio kernel: rx intr: idx=44 len=152 stat len=114 rssi=7 rate=a chan=11 tstamp=95310 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=38 flags=2 type=27 len=152 Feb 3 11:45:43 vaio kernel: rx intr: idx=45 len=152 stat len=114 rssi=7 rate=a chan=11 tstamp=96560 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=39 flags=2 type=27 len=164 Feb 3 11:45:43 vaio kernel: rx intr: idx=46 len=164 stat len=126 rssi=10 rate=a chan=11 tstamp=97879 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=40 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=41 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=42 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 12 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=43 flags=2 type=27 len=116 Feb 3 11:45:43 vaio kernel: rx intr: idx=50 len=116 stat len=77 rssi=31 rate=a chan=12 tstamp=118060 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=44 flags=2 type=27 len=116 Feb 3 11:45:43 vaio kernel: rx intr: idx=51 len=116 stat len=77 rssi=29 rate=a chan=12 tstamp=119267 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=45 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=46 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=47 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 13 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=48 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=49 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=50 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 14 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=51 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=52 flags=0 type=132 len=16 Feb 3 11:45:43 vaio kernel: scan finished nchan=14 status=1 chan=14 Feb 3 11:45:43 vaio kernel: rx notification qid=4 idx=7 flags=0 type=128 len=8 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=53 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=54 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 36 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=55 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=56 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=57 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 40 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=58 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=59 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=60 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 44 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=61 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=62 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=63 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 48 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=64 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=65 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=66 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 52 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=67 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=68 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=69 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 56 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=70 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=71 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=72 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 60 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=73 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=74 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=75 flags=0 type=130 len=24 Feb 3 11:45:43 vaio kernel: scanning channel 64 status 1 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=76 flags=0 type=131 len=20 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=77 flags=0 type=157 len=244 Feb 3 11:45:43 vaio kernel: rx notification qid=80 idx=78 flags=0 type=130 len=24 -- -------------------------------- (hika) Gilbert Cao http://www.miaouirc.com - MiaouIRC Project 2002-2003 http://www.bsdmon.com - The BSD DMON Power to serve IRC : #miaule at IRCNET Network -------------------------------- From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 3 23:10:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8288316A401 for ; Sat, 3 Feb 2007 23:10:03 +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 224D713C46B for ; Sat, 3 Feb 2007 23:10:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l13N95jM001201; Sat, 3 Feb 2007 16:09:06 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 03 Feb 2007 16:09:37 -0700 (MST) Message-Id: <20070203.160937.-1632632820.imp@bsdimp.com> To: cats@catslab.com From: "M. Warner Losh" In-Reply-To: <200723171021.907086@poppa> References: <200723171021.907086@poppa> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 03 Feb 2007 16:09:06 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: Geode SC1100 i2c bus 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, 03 Feb 2007 23:10:03 -0000 In message: <200723171021.907086@poppa> Cats writes: : Does someone already tried to use i2c bus on a wrap board under FreeBSD ? All that should be needed is an i2c bridge controller driver. Much of the rest of the support is there, or nearly there. OpenBSD has a wider variety of devices, but their i2c stack is optimized a little too heavily for monitoring... Warner