From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 15:47:50 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C488C106564A for ; Sun, 18 May 2008 15:47:50 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 512458FC32 for ; Sun, 18 May 2008 15:47:49 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so330111uge.37 for ; Sun, 18 May 2008 08:47:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=phSUhfO/nd8LhOnFMi7ebyTkrisMeGuvskZ7ezUm93Y=; b=dOUHRvaZdSF/9zw5PI1jk73wSEAlwyuAZV+F7nFU3QGn83s6SumrhL14cy+fpwFV/CZVL1nRJ6u1URJgiLUqNpMYwpDGMwpbbTImMcfjUn5l5QqXrLWI7sTczLjrNwyGwoXH6NvPfD/A4kBwKqGVlJxsmE95x4SrTQEfZaQ4VVQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=xC2i3Bwvs82hHWFfIRN5gjUn8oTtPx5b84PYi5AzsO9IxsSIF4ZcHyOKSaJtqKVs4zNk7T2YBNRaKtQfBfK5glXc57pqvxUeNJzZiDIvvsUEBn2kDigLJIJVtVKHCZe/HuV0/EkjUun78CDvr4dyJQm0LDpYvISJ89pg2dvUBXU= Received: by 10.67.106.19 with SMTP id i19mr2570899ugm.86.1211125668943; Sun, 18 May 2008 08:47:48 -0700 (PDT) Received: from epsilon.local ( [89.214.185.160]) by mx.google.com with ESMTPS id i6sm12731857gve.4.2008.05.18.08.47.46 (version=SSLv3 cipher=RC4-MD5); Sun, 18 May 2008 08:47:48 -0700 (PDT) Message-ID: <48304F9D.9030406@FreeBSD.org> Date: Sun, 18 May 2008 16:47:41 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Kostik Belousov References: <482E93C0.4070802@icyb.net.ua> <482EFBA0.30107@FreeBSD.org> <482F1191.70709@icyb.net.ua> <482F1529.5080409@FreeBSD.org> <20080517175312.GM18958@deviant.kiev.zoral.com.ua> In-Reply-To: <20080517175312.GM18958@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Rui Paulo Cc: freebsd-hackers@freebsd.org, Andriy Gapon Subject: Re: rdmsr from userspace 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, 18 May 2008 15:47:50 -0000 Kostik Belousov wrote: > On Sat, May 17, 2008 at 06:26:01PM +0100, Rui Paulo wrote: >> Andriy Gapon wrote: >>> on 17/05/2008 18:37 Rui Paulo said the following: >>>> Andriy Gapon wrote: >>>>> It seems that rdmsr instruction can be executed only at the highest >>>>> privilege level and thus is not permitted from userland. Maybe we >>>>> should provide something like Linux /dev/cpu/msr? >>>>> I don't like interface of that device, I think that ioctl approach >>>>> would be preferable in this case. >>>>> Something like create /dev/cpuN and allow some ioctls on it: >>>>> ioctl(cpu_fd, CPU_RDMSR, arg). >>>>> What do you think? >>>>> >>>> While I think this (devcpu) is good for testing and development, I >>>> prefer having a device driver to handle that specific MSR than a >>>> generic /dev/cpuN where you can issue MSRs. >>>> Both for security and reliability reasons. >>> What about /dev/pci, /dev/io? Aren't they a precedent? >> They are, but, IMHO, we should no longer continue to create this type of >> interfaces. > > Why ? Are developers some kind of the second-class users ? > > I would have no opinion on providing /dev/cpu by the loadable module, not > compiled into GENERIC. But the interface itself is useful at least for > three things: > - CPU identification (see x86info or whatever it is called); > - CPU tweaking for bugs workaround without patching the kernel; > - updating the CPU microcode. > None of these is limited to the developers only. Input validation is my main concern here. Regarding to your two last points, I would prefer to have a microcode driver than a microcode userland utility that relies on devcpu. Regards, -- Rui Paulo From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 15:50:36 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6361B106564A for ; Sun, 18 May 2008 15:50:36 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id E07DB8FC23 for ; Sun, 18 May 2008 15:50:35 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so330942uge.37 for ; Sun, 18 May 2008 08:50:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=K8Gb8EkZzQsezJdNJTXDT5S3pkrU/R29RtEHEh1/Zqk=; b=qaYzaHgNtShDcwr12U+ueUVMITa1QJlkf7pJv7NiYwwqaOGynQADaGCOMqzDqYUaTmsPJoslVItCUtIkO82htWp4uuTLrcKNm+g0+LGG5rsiLN4oNlyb/6ekKgeaWRcVQraL5hd0PEeOj8lFJhGt1PMs9iuVUHsKgtKqzFv7f8s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=gKaeFs7kr0P36Prge8US4I71IXo2pJP0rsmSwTAcDg8+xt9Mpho+aHSCE8WPSVFfaiMeV6Juk1ZY3cEVW6gjN6oACvf02r3qVGyUxMfIq3vpitg9u5W0m2sBSeNyRdFTvBFf6t/HHH9iix0yIanYaBbJwVGocB52Mr4plWuvm/w= Received: by 10.67.106.13 with SMTP id i13mr2607378ugm.49.1211125833988; Sun, 18 May 2008 08:50:33 -0700 (PDT) Received: from epsilon.local ( [89.214.185.160]) by mx.google.com with ESMTPS id j8sm12727142gvb.1.2008.05.18.08.50.31 (version=SSLv3 cipher=RC4-MD5); Sun, 18 May 2008 08:50:32 -0700 (PDT) Message-ID: <48305044.7000007@FreeBSD.org> Date: Sun, 18 May 2008 16:50:28 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Mike Meyer References: <482E93C0.4070802@icyb.net.ua> <20080517133037.3a3935db@bhuda.mired.org> In-Reply-To: <20080517133037.3a3935db@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Rui Paulo Cc: freebsd-hackers@freebsd.org Subject: Re: rdmsr from userspace 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, 18 May 2008 15:50:36 -0000 Mike Meyer wrote: > On Sat, 17 May 2008 11:13:52 +0300 > Andriy Gapon wrote: >> It seems that rdmsr instruction can be executed only at the highest >> privilege level and thus is not permitted from userland. Maybe we should >> provide something like Linux /dev/cpu/msr? >> I don't like interface of that device, I think that ioctl approach would >> be preferable in this case. >> Something like create /dev/cpuN and allow some ioctls on it: >> ioctl(cpu_fd, CPU_RDMSR, arg). >> What do you think? > > Ok, this points directly at a question I've been wondering about, but > haven't been able to find an answer in the google. > > I've been mucking about with general access to sysctl's (a sysctl > plugin for gkrellm, and a python module for accessing sysctls), and > with that hammer in my hand, the nail for this problem is obviously a > dev.cpu.#.msr sysctl. How can you request a rdmsr within the sysctl tree? I don't think sysctl is appropriate here either. -- Rui Paulo From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 18:06:26 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C1331065679 for ; Sun, 18 May 2008 18:06:26 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id D69C68FC15 for ; Sun, 18 May 2008 18:06:25 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 75378 invoked by uid 1001); 18 May 2008 14:06:52 -0400 Received: from bhuda.mired.org (bhuda [192.168.195.1]) by bhuda (tmda-ofmipd) with ESMTP; Sun, 18 May 2008 14:06:51 -0400 Date: Sun, 18 May 2008 14:06:50 -0400 To: Rui Paulo Message-ID: <20080518140650.2691af1c@bhuda.mired.org> In-Reply-To: <48305044.7000007@FreeBSD.org> References: <482E93C0.4070802@icyb.net.ua> <20080517133037.3a3935db@bhuda.mired.org> <48305044.7000007@FreeBSD.org> Organization: Meyer Consulting X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, Mike Meyer Subject: Re: rdmsr from userspace 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, 18 May 2008 18:06:26 -0000 On Sun, 18 May 2008 16:50:28 +0100 Rui Paulo wrote: > Mike Meyer wrote: > > On Sat, 17 May 2008 11:13:52 +0300 > > Andriy Gapon wrote: > >> It seems that rdmsr instruction can be executed only at the highest > >> privilege level and thus is not permitted from userland. Maybe we should > >> provide something like Linux /dev/cpu/msr? > >> I don't like interface of that device, I think that ioctl approach would > >> be preferable in this case. > >> Something like create /dev/cpuN and allow some ioctls on it: > >> ioctl(cpu_fd, CPU_RDMSR, arg). > >> What do you think? > > > > Ok, this points directly at a question I've been wondering about, but > > haven't been able to find an answer in the google. > > > > I've been mucking about with general access to sysctl's (a sysctl > > plugin for gkrellm, and a python module for accessing sysctls), and > > with that hammer in my hand, the nail for this problem is obviously a > > dev.cpu.#.msr sysctl. > > How can you request a rdmsr within the sysctl tree? I don't think sysctl > is appropriate here either. Reading (or writing) a sysctl mib can trigger a sysctl handler, which can do pretty much anything. In particular, there are already examples in the kernel where sysctl handlers use devices that don't have /dev entries to get & set their values. Look through kern/kern_cpu.c and i386/cpufreq/p4tcc.c to see the two ends of that kind of connection. In fact, the cpu frequency sysctls would seem to be an excellent model for something like the msr. ioctl, open+read/write, sysctl - they're all just interfaces to kernel handlers. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 18:16:05 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A6D0106566C; Sun, 18 May 2008 18:16:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay03.kiev.sovam.com (relay03.kiev.sovam.com [62.64.120.201]) by mx1.freebsd.org (Postfix) with ESMTP id CB2CE8FC0A; Sun, 18 May 2008 18:16:04 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay03.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JxnQR-000BxE-D3; Sun, 18 May 2008 21:16:03 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m4IIFpUF025605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 May 2008 21:15:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m4IIFnEW090884; Sun, 18 May 2008 21:15:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m4IIFnDT090883; Sun, 18 May 2008 21:15:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 18 May 2008 21:15:49 +0300 From: Kostik Belousov To: Rui Paulo Message-ID: <20080518181549.GZ18958@deviant.kiev.zoral.com.ua> References: <482E93C0.4070802@icyb.net.ua> <482EFBA0.30107@FreeBSD.org> <482F1191.70709@icyb.net.ua> <482F1529.5080409@FreeBSD.org> <20080517175312.GM18958@deviant.kiev.zoral.com.ua> <48304F9D.9030406@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PUO5JmOx8Q3B5DV1" Content-Disposition: inline In-Reply-To: <48304F9D.9030406@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on skuns.kiev.zoral.com.ua X-Scanner-Signature: b565934a9b6505813531773f2f5625c7 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 2835 [May 13 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0278], KAS30/Release Cc: freebsd-hackers@freebsd.org, Andriy Gapon Subject: Re: rdmsr from userspace 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, 18 May 2008 18:16:05 -0000 --PUO5JmOx8Q3B5DV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 18, 2008 at 04:47:41PM +0100, Rui Paulo wrote: > Kostik Belousov wrote: > >On Sat, May 17, 2008 at 06:26:01PM +0100, Rui Paulo wrote: > >>Andriy Gapon wrote: > >>>on 17/05/2008 18:37 Rui Paulo said the following: > >>>>Andriy Gapon wrote: > >>>>>It seems that rdmsr instruction can be executed only at the highest= =20 > >>>>>privilege level and thus is not permitted from userland. Maybe we=20 > >>>>>should provide something like Linux /dev/cpu/msr? > >>>>>I don't like interface of that device, I think that ioctl approach= =20 > >>>>>would be preferable in this case. > >>>>>Something like create /dev/cpuN and allow some ioctls on it:=20 > >>>>>ioctl(cpu_fd, CPU_RDMSR, arg). > >>>>>What do you think? > >>>>> > >>>>While I think this (devcpu) is good for testing and development, I=20 > >>>>prefer having a device driver to handle that specific MSR than a=20 > >>>>generic /dev/cpuN where you can issue MSRs. > >>>>Both for security and reliability reasons. > >>>What about /dev/pci, /dev/io? Aren't they a precedent? > >>They are, but, IMHO, we should no longer continue to create this type o= f=20 > >>interfaces. > > > >Why ? Are developers some kind of the second-class users ? > > > >I would have no opinion on providing /dev/cpu by the loadable module, not > >compiled into GENERIC. But the interface itself is useful at least for > >three things: > >- CPU identification (see x86info or whatever it is called); > >- CPU tweaking for bugs workaround without patching the kernel; > >- updating the CPU microcode. > >None of these is limited to the developers only. >=20 > Input validation is my main concern here. Regarding to your two last=20 > points, I would prefer to have a microcode driver than a microcode=20 > userland utility that relies on devcpu. Did you looked at the code ? It does exactly what you described. Driver has four basic operations: read/write msr perform cpu id work update microcode. The later is done as a whole operation, with the microcode blob supplied by the userspace. --PUO5JmOx8Q3B5DV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkgwclUACgkQC3+MBN1Mb4jcEACdEkxr4HlQQPcam9OvnXz4CGvv vOUAoOt2qNPEMPskskz1Pb3U08S0H/uE =yqm4 -----END PGP SIGNATURE----- --PUO5JmOx8Q3B5DV1-- From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 18:16:49 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 993D4106567A for ; Sun, 18 May 2008 18:16:49 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 4D06B8FC17 for ; Sun, 18 May 2008 18:16:49 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id m4IIGm8g037876 for ; Sun, 18 May 2008 11:16:48 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id m4IIGmCF037875 for hackers@freebsd.org; Sun, 18 May 2008 11:16:48 -0700 (PDT) (envelope-from david) Date: Sun, 18 May 2008 11:16:48 -0700 From: David Wolfskill To: hackers@freebsd.org Message-ID: <20080518181648.GA7468@bunrab.catwhisker.org> References: <20080512200901.GL66703@bunrab.catwhisker.org> <20080518170936.GB1797@roadrunner.spoerlein.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KLINyTCByxgMLuN/" Content-Disposition: inline In-Reply-To: <20080518170936.GB1797@roadrunner.spoerlein.net> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: [Patch] Using sysctl(8) to acquire info from different systems 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, 18 May 2008 18:16:49 -0000 --KLINyTCByxgMLuN/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 18, 2008 at 07:09:36PM +0200, Ulrich Spoerlein wrote: > ... > I find this functionality very useful, but the addition of another flag > as problematic. First of all, old releases don't have it. Secondly, the > behaviour you describe should be the default anyway (IMHO). Thank you for your support of the idea. I'll explain why I chose a different approach in the implementation. I agree that it would have been handy had it been the default behavior, but it hasn't been and wishing isn't likely to change that. Thus, if a change is to be seen in the older releases, *some* change will need to be made to the code for those releases. By making the change the addition of a flag, we are able to preserve the existing default behavior -- and thus avoid potentioal perception of a POLA violation. And I believe the change is easily merged from CURRENT to older releases, if someone is willing to do the commit. > So, when requesting OID a, b, and c, sysctl should print a, a warning > that it cannot find OID b (to STDERR), then print c and exit with a > return code !=3D 0. Well, the warning should be emitted in the absence of the -q flag, I expect, but in its presence, the warning should (IMO) be suppressed. > At least, that's what I would code it to do. I'd be happy for the default to be to (at least) "carry on" after finding a request for an unknown OID. I deliberately made my patch as non-invasive as I could to improve its chances of actually getting committed -- as well as the above-cited desire to avoid perception of a POLA violation. :-} And I'm hardly claiming that the approach I took is optimal, let alone the "only" one: it is an approach that I believe to be consistent with my requirements and thus serves to more clearly illustrate those requirements. BTW, I did file a PR -- it's bin/123644: Allow sysctl(8) to ignore unknown OIDs. Peace, david --=20 David H. Wolfskill david@catwhisker.org I submit that "conspiracy" would be an appropriate collective noun for cats. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --KLINyTCByxgMLuN/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkgwcpAACgkQmprOCmdXAD2T5ACfaFggw4NYBk9QpcxRuHXdnyEW 4ssAnjA6iEZcpfaIQA54d4WeYyBLRl3y =aS/v -----END PGP SIGNATURE----- --KLINyTCByxgMLuN/-- From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 18:32:20 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1677610656C2 for ; Sun, 18 May 2008 18:32:20 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by mx1.freebsd.org (Postfix) with ESMTP id 8B19A8FC17 for ; Sun, 18 May 2008 18:32:19 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1582531fkk.11 for ; Sun, 18 May 2008 11:32:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=6do2/KRBnidLn6Yphma4Otdmb3IC2V+gblcAl/654Zo=; b=kCo1FdCMbPJ10vMHmK9rkhZYbfQ00i0JM9gVVBORA3lDw0rQ1n93bhUFuilVIqHTWNeF2g9AoV5N8yNC+BtMadJv2gRy4VDzidDVUy8dWI/abvSjALiH+rbVruT6R1PijoOXgpa4ZuhmGly80cL0qf33bsKANgkF+CSnztvGjUg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=PKnPrAm08Sa81dh76pX6nQDpyUrTX9l3zVMCkzFILAGuiTOHLLjfO8rvmijXl42A/OO/6aUKllSd1tbtDKSyXWZEkm5oyzpqWbuC+1HsizcHLBSKfmkaM7o6M5VKGMhlGwfzGPdyjcWScGO7w3LJuqGAl4PfzDUpjIzTOPY213Y= Received: by 10.125.111.15 with SMTP id o15mr5104126mkm.127.1211133827179; Sun, 18 May 2008 11:03:47 -0700 (PDT) Received: from acme.spoerlein.net ( [217.172.44.86]) by mx.google.com with ESMTPS id 4sm7311583fgg.6.2008.05.18.11.03.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 18 May 2008 11:03:46 -0700 (PDT) Received: from roadrunner.spoerlein.net (e180148079.adsl.alicedsl.de [85.180.148.79]) by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id m4II3gip035558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 18 May 2008 20:03:44 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.2/8.14.2) with ESMTP id m4IH9bkC003625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 May 2008 19:09:37 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from uqs@localhost) by roadrunner.spoerlein.net (8.14.2/8.14.2/Submit) id m4IH9ap7003624; Sun, 18 May 2008 19:09:36 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Sun, 18 May 2008 19:09:36 +0200 From: Ulrich Spoerlein To: David Wolfskill Message-ID: <20080518170936.GB1797@roadrunner.spoerlein.net> Mail-Followup-To: David Wolfskill , hackers@freebsd.org References: <20080512200901.GL66703@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080512200901.GL66703@bunrab.catwhisker.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: hackers@freebsd.org Subject: Re: [Patch] Using sysctl(8) to acquire info from different systems 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, 18 May 2008 18:32:20 -0000 On Mon, 12.05.2008 at 13:09:01 -0700, David Wolfskill wrote: > In my case, I believe it would be useful to provide an ability to tell > sysctl(8) to report on everything asked for that it does know, and > ignore the OIDs it doesn't know. > > Is this percpetion so radical that I'm way off base? If so, please > educate me as to why. > > Otherwise, I'll plan on filing a PR with the attached patch, which adds > "-i" to sysctl(8)'s flags -- and which appears to work as described above: Hi David, I find this functionality very useful, but the addition of another flag as problematic. First of all, old releases don't have it. Secondly, the behaviour you describe should be the default anyway (IMHO). So, when requesting OID a, b, and c, sysctl should print a, a warning that it cannot find OID b (to STDERR), then print c and exit with a return code != 0. At least, that's what I would code it to do. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 18:33:04 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A72301065690 for ; Sun, 18 May 2008 18:33:04 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id A22F98FC0C for ; Sun, 18 May 2008 18:33:03 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so382044uge.37 for ; Sun, 18 May 2008 11:33:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=xgXno9Z/7p450r+6czwbiLGk2OJUE4mHqrIVLzltw8g=; b=P27yPXqe2inm4K6IAmfgtxVMYPoeOVjd5YdWJNcoywQdFA5GSDG/iRw1wOX0yNfEFPemgodBN6zpD8lksLT8R+ufLp3S9VMpDaP1sOWIRsHS+vKqvbFoGtD37Ch9dV52UjtpotjFiaihP/fx+LnzaxXmpfD6a0XamFR/nZxWM7Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=BI2/jIpyHbNq1SfEJ2DztoUj0crIpQu46/FLxVFd9Kxo4vg9DoDO3yWsaOJDxM4Ha6TUMlq3nDXNcf7duRF91R/8Qqx9mQ/+rokxeOg2Wu1QMQezMnyZXGpJe/dD+mDjiYRkyqkjflogORxWbZhajTocVRjSQgWGttDVGjuec2U= Received: by 10.67.116.2 with SMTP id t2mr2765639ugm.52.1211135582207; Sun, 18 May 2008 11:33:02 -0700 (PDT) Received: from epsilon.local ( [89.214.185.160]) by mx.google.com with ESMTPS id m38sm1056830ugd.44.2008.05.18.11.32.59 (version=SSLv3 cipher=RC4-MD5); Sun, 18 May 2008 11:33:01 -0700 (PDT) Message-ID: <48307658.2080502@FreeBSD.org> Date: Sun, 18 May 2008 19:32:56 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Kostik Belousov References: <482E93C0.4070802@icyb.net.ua> <482EFBA0.30107@FreeBSD.org> <482F1191.70709@icyb.net.ua> <482F1529.5080409@FreeBSD.org> <20080517175312.GM18958@deviant.kiev.zoral.com.ua> <48304F9D.9030406@FreeBSD.org> <20080518181549.GZ18958@deviant.kiev.zoral.com.ua> In-Reply-To: <20080518181549.GZ18958@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Rui Paulo Cc: freebsd-hackers@freebsd.org, Andriy Gapon Subject: Re: rdmsr from userspace 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, 18 May 2008 18:33:04 -0000 Kostik Belousov wrote: > On Sun, May 18, 2008 at 04:47:41PM +0100, Rui Paulo wrote: >> Kostik Belousov wrote: >>> On Sat, May 17, 2008 at 06:26:01PM +0100, Rui Paulo wrote: >>>> Andriy Gapon wrote: >>>>> on 17/05/2008 18:37 Rui Paulo said the following: >>>>>> Andriy Gapon wrote: >>>>>>> It seems that rdmsr instruction can be executed only at the highest >>>>>>> privilege level and thus is not permitted from userland. Maybe we >>>>>>> should provide something like Linux /dev/cpu/msr? >>>>>>> I don't like interface of that device, I think that ioctl approach >>>>>>> would be preferable in this case. >>>>>>> Something like create /dev/cpuN and allow some ioctls on it: >>>>>>> ioctl(cpu_fd, CPU_RDMSR, arg). >>>>>>> What do you think? >>>>>>> >>>>>> While I think this (devcpu) is good for testing and development, I >>>>>> prefer having a device driver to handle that specific MSR than a >>>>>> generic /dev/cpuN where you can issue MSRs. >>>>>> Both for security and reliability reasons. >>>>> What about /dev/pci, /dev/io? Aren't they a precedent? >>>> They are, but, IMHO, we should no longer continue to create this type of >>>> interfaces. >>> Why ? Are developers some kind of the second-class users ? >>> >>> I would have no opinion on providing /dev/cpu by the loadable module, not >>> compiled into GENERIC. But the interface itself is useful at least for >>> three things: >>> - CPU identification (see x86info or whatever it is called); >>> - CPU tweaking for bugs workaround without patching the kernel; >>> - updating the CPU microcode. >>> None of these is limited to the developers only. >> Input validation is my main concern here. Regarding to your two last >> points, I would prefer to have a microcode driver than a microcode >> userland utility that relies on devcpu. > Did you looked at the code ? It does exactly what you described. > > Driver has four basic operations: > read/write msr > perform cpu id work > update microcode. > > The later is done as a whole operation, with the microcode blob supplied > by the userspace. Yes, but I still don't like having everything mixed up in one driver. At the very least, I would like us to have two drivers. One for the microcode update and the other driver for the rest. I would like to see a microcode update utility (driver + something to parse Intel's file aka devcpu-data) in the base system, but not "the rest", though. Regards, -- Rui Paulo From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 18:35:52 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CA341065670 for ; Sun, 18 May 2008 18:35:52 +0000 (UTC) (envelope-from rpaulo@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 0882B8FC0A for ; Sun, 18 May 2008 18:35:51 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so382953uge.37 for ; Sun, 18 May 2008 11:35:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=wHI+n2VGbarWBEU237AwAuyKMPrgRTcwpAMNF/cFob4=; b=VmGpNdV4q6PiFJ9mroXBp5iHhxdqytE6nJL9pV6BcTTqbDzXtvuo+iTwpK6KAFkZVmHxWEXfaQKw0O39TWmO9dMN2XvKfzILXD9EOkUrQO1KB4dVYemAtAptj/Wwn2Jlkn/EI924ofXmoH2Is4PXaS2JscCfNjzHP5iGhcOba80= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=qgwQ97lvVKvE38OUK5aYL+jAmqgbUKaZZS+XHPALwyFZR+yL+0fUJ2TpOurTT8GFDfdSiU2A7nq9uZUEFSR4Zr80/kJ8kDG63Sk2981p6DK6PBqpYZaUiN8VqeBRpP8Ut2mH/7mVGmR2YteFAty/V0IqdZ4oG6ogIClXgDkAu2s= Received: by 10.67.29.4 with SMTP id g4mr2748009ugj.84.1211135750691; Sun, 18 May 2008 11:35:50 -0700 (PDT) Received: from epsilon.local ( [89.214.185.160]) by mx.google.com with ESMTPS id m1sm1048035ugc.59.2008.05.18.11.35.47 (version=SSLv3 cipher=RC4-MD5); Sun, 18 May 2008 11:35:48 -0700 (PDT) Message-ID: <48307700.70304@FreeBSD.org> Date: Sun, 18 May 2008 19:35:44 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Mike Meyer References: <482E93C0.4070802@icyb.net.ua> <20080517133037.3a3935db@bhuda.mired.org> <48305044.7000007@FreeBSD.org> <20080518140650.2691af1c@bhuda.mired.org> In-Reply-To: <20080518140650.2691af1c@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Rui Paulo Cc: freebsd-hackers@freebsd.org Subject: Re: rdmsr from userspace 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, 18 May 2008 18:35:52 -0000 Mike Meyer wrote: > On Sun, 18 May 2008 16:50:28 +0100 > Rui Paulo wrote: > >> Mike Meyer wrote: >>> On Sat, 17 May 2008 11:13:52 +0300 >>> Andriy Gapon wrote: >>>> It seems that rdmsr instruction can be executed only at the highest >>>> privilege level and thus is not permitted from userland. Maybe we should >>>> provide something like Linux /dev/cpu/msr? >>>> I don't like interface of that device, I think that ioctl approach would >>>> be preferable in this case. >>>> Something like create /dev/cpuN and allow some ioctls on it: >>>> ioctl(cpu_fd, CPU_RDMSR, arg). >>>> What do you think? >>> Ok, this points directly at a question I've been wondering about, but >>> haven't been able to find an answer in the google. >>> >>> I've been mucking about with general access to sysctl's (a sysctl >>> plugin for gkrellm, and a python module for accessing sysctls), and >>> with that hammer in my hand, the nail for this problem is obviously a >>> dev.cpu.#.msr sysctl. >> How can you request a rdmsr within the sysctl tree? I don't think sysctl >> is appropriate here either. > > Reading (or writing) a sysctl mib can trigger a sysctl handler, which > can do pretty much anything. In particular, there are already examples > in the kernel where sysctl handlers use devices that don't have /dev > entries to get & set their values. Look through kern/kern_cpu.c and > i386/cpufreq/p4tcc.c to see the two ends of that kind of > connection. In fact, the cpu frequency sysctls would seem to be an > excellent model for something like the msr. > > ioctl, open+read/write, sysctl - they're all just interfaces to kernel > handlers. > > ? I'll have to think about whether or not I like this interface. Regards, -- Rui Paulo From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 19:29:20 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 921C81065747 for ; Sun, 18 May 2008 19:29:20 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id 459D48FC0C for ; Sun, 18 May 2008 19:29:20 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 77204 invoked by uid 1001); 18 May 2008 15:29:47 -0400 Received: from bhuda.mired.org (bhuda [192.168.195.1]) by bhuda (tmda-ofmipd) with ESMTP; Sun, 18 May 2008 15:29:46 -0400 Date: Sun, 18 May 2008 15:29:45 -0400 To: Rui Paulo Message-ID: <20080518152945.60989b9c@bhuda.mired.org> In-Reply-To: <48307700.70304@FreeBSD.org> References: <482E93C0.4070802@icyb.net.ua> <20080517133037.3a3935db@bhuda.mired.org> <48305044.7000007@FreeBSD.org> <20080518140650.2691af1c@bhuda.mired.org> <48307700.70304@FreeBSD.org> Organization: Meyer Consulting X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, Mike Meyer Subject: Re: rdmsr from userspace 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, 18 May 2008 19:29:20 -0000 On Sun, 18 May 2008 19:35:44 +0100 Rui Paulo wrote: > Mike Meyer wrote: > > On Sun, 18 May 2008 16:50:28 +0100 > > Rui Paulo wrote: > > > >> Mike Meyer wrote: > >>> On Sat, 17 May 2008 11:13:52 +0300 > >>> Andriy Gapon wrote: > >>>> It seems that rdmsr instruction can be executed only at the highest > >>>> privilege level and thus is not permitted from userland. Maybe we should > >>>> provide something like Linux /dev/cpu/msr? > >>>> I don't like interface of that device, I think that ioctl approach would > >>>> be preferable in this case. > >>>> Something like create /dev/cpuN and allow some ioctls on it: > >>>> ioctl(cpu_fd, CPU_RDMSR, arg). > >>>> What do you think? > >>> Ok, this points directly at a question I've been wondering about, but > >>> haven't been able to find an answer in the google. > >>> > >>> I've been mucking about with general access to sysctl's (a sysctl > >>> plugin for gkrellm, and a python module for accessing sysctls), and > >>> with that hammer in my hand, the nail for this problem is obviously a > >>> dev.cpu.#.msr sysctl. > >> How can you request a rdmsr within the sysctl tree? I don't think sysctl > >> is appropriate here either. > > > > Reading (or writing) a sysctl mib can trigger a sysctl handler, which > > can do pretty much anything. In particular, there are already examples > > in the kernel where sysctl handlers use devices that don't have /dev > > entries to get & set their values. Look through kern/kern_cpu.c and > > i386/cpufreq/p4tcc.c to see the two ends of that kind of > > connection. In fact, the cpu frequency sysctls would seem to be an > > excellent model for something like the msr. > > > > ioctl, open+read/write, sysctl - they're all just interfaces to kernel > > handlers. > > > > > Yes, sure, but who do you select the MSR you want to read or write? > > dev.cpu.N. ? I don't think that would work - you'd have to register all those hexadecimal strings as sysctl names. You could do an interface like this, but the calling program would have to use sysctlnametomib to get dev.cpu.N.msr, then append the MSR number to the results. Not really very pretty. If you want to allow the user to poke at arbitrary msrs, this would be a way to do it with sysctls, but the file api is probably better. On the other hand, if you want to allow access to the fixed set of documented msr's (for each cpu model, anyway), then handing back that fixed set as an array would be a better approach, and would have the advantage of not having to deal with invalid requests (non-existent MSRs, 1-byte reads/writes of multi-byte MSRs, etc). On the other hand, it might be more useful - *especially* if the MSRs move around depending on processor types (I honestly don't know) - to provide a "named" interface: dev.cpu.0.msr.mtrr dev.cpu.0.msr.arr dev.cpu.0.msr.efer and so on. You'd register the names when the module was initialized, and would only register the ones that actually existed. You'd then never have to deal with a request for a non-existent MSR, because the sysctl call would return an error to the calling program without ever calling your handler. Of course, you can *combine* these two approaches, and have: dev.cpu.0.msr.all # returns an array of all available msrs dev.cpu.0.msr.have # an array of the available msrs but at this point it's just blue sky speculation... > I'll have to think about whether or not I like this interface. Actually, I'm more interested in why there seems to be a dislike of file-based interfaces in favor of sysctls in the freebsd community. Exploring this has been enlightening. Thank you. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 19:29:32 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5BFB1065670 for ; Sun, 18 May 2008 19:29:32 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id 78B368FC1C for ; Sun, 18 May 2008 19:29:32 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 77260 invoked by uid 1001); 18 May 2008 15:29:59 -0400 Received: from bhuda.mired.org (bhuda [192.168.195.1]) by bhuda (tmda-ofmipd) with ESMTP; Sun, 18 May 2008 15:29:58 -0400 Date: Sun, 18 May 2008 15:29:37 -0400 To: Rui Paulo Message-ID: <20080518152937.774cf492@bhuda.mired.org> In-Reply-To: <48307700.70304@FreeBSD.org> References: <482E93C0.4070802@icyb.net.ua> <20080517133037.3a3935db@bhuda.mired.org> <48305044.7000007@FreeBSD.org> <20080518140650.2691af1c@bhuda.mired.org> <48307700.70304@FreeBSD.org> Organization: Meyer Consulting X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, Mike Meyer Subject: Re: rdmsr from userspace 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, 18 May 2008 19:29:32 -0000 On Sun, 18 May 2008 19:35:44 +0100 Rui Paulo wrote: > Mike Meyer wrote: > > On Sun, 18 May 2008 16:50:28 +0100 > > Rui Paulo wrote: > > > >> Mike Meyer wrote: > >>> On Sat, 17 May 2008 11:13:52 +0300 > >>> Andriy Gapon wrote: > >>>> It seems that rdmsr instruction can be executed only at the highest > >>>> privilege level and thus is not permitted from userland. Maybe we should > >>>> provide something like Linux /dev/cpu/msr? > >>>> I don't like interface of that device, I think that ioctl approach would > >>>> be preferable in this case. > >>>> Something like create /dev/cpuN and allow some ioctls on it: > >>>> ioctl(cpu_fd, CPU_RDMSR, arg). > >>>> What do you think? > >>> Ok, this points directly at a question I've been wondering about, but > >>> haven't been able to find an answer in the google. > >>> > >>> I've been mucking about with general access to sysctl's (a sysctl > >>> plugin for gkrellm, and a python module for accessing sysctls), and > >>> with that hammer in my hand, the nail for this problem is obviously a > >>> dev.cpu.#.msr sysctl. > >> How can you request a rdmsr within the sysctl tree? I don't think sysctl > >> is appropriate here either. > > > > Reading (or writing) a sysctl mib can trigger a sysctl handler, which > > can do pretty much anything. In particular, there are already examples > > in the kernel where sysctl handlers use devices that don't have /dev > > entries to get & set their values. Look through kern/kern_cpu.c and > > i386/cpufreq/p4tcc.c to see the two ends of that kind of > > connection. In fact, the cpu frequency sysctls would seem to be an > > excellent model for something like the msr. > > > > ioctl, open+read/write, sysctl - they're all just interfaces to kernel > > handlers. > > > > > Yes, sure, but who do you select the MSR you want to read or write? > > dev.cpu.N. ? I don't think that would work - you'd have to register all those hexadecimal strings as sysctl names. You could do an interface like this, but the calling program would have to use sysctlnametomib to get dev.cpu.N.msr, then append the MSR number to the results. Not really very pretty. If you want to allow the user to poke at arbitrary msrs, this would be a way to do it with sysctls, but the file api is probably better. On the other hand, if you want to allow access to the fixed set of documented msr's (for each cpu model, anyway), then handing back that fixed set as an array would be a better approach, and would have the advantage of not having to deal with invalid requests (non-existent MSRs, 1-byte reads/writes of multi-byte MSRs, etc). On the other hand, it might be more useful - *especially* if the MSRs move around depending on processor types (I honestly don't know) - to provide a "named" interface: dev.cpu.0.msr.mtrr dev.cpu.0.msr.arr dev.cpu.0.msr.efer and so on. You'd register the names when the module was initialized, and would only register the ones that actually existed. You'd then never have to deal with a request for a non-existent MSR, because the sysctl call would return an error to the calling program without ever calling your handler. Of course, you can *combine* these two approaches, and have: dev.cpu.0.msr.all # returns an array of all available msrs dev.cpu.0.msr.have # an array of the available msrs but at this point it's just blue sky speculation... > I'll have to think about whether or not I like this interface. Actually, I'm more interested in why there seems to be a dislike of file-based interfaces in favor of sysctls in the freebsd community. Exploring this has been enlightening. Thank you. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 20:05:56 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45F59106564A; Sun, 18 May 2008 20:05:56 +0000 (UTC) (envelope-from ssouhlal@FreeBSD.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 315F98FC1F; Sun, 18 May 2008 20:05:56 +0000 (UTC) (envelope-from ssouhlal@FreeBSD.org) Received: from [192.168.0.100] (c-76-21-32-5.hsd1.ca.comcast.net [76.21.32.5]) by elvis.mu.org (Postfix) with ESMTP id 91BD21A4D7C; Sun, 18 May 2008 12:47:11 -0700 (PDT) In-Reply-To: <20080518181549.GZ18958@deviant.kiev.zoral.com.ua> References: <482E93C0.4070802@icyb.net.ua> <482EFBA0.30107@FreeBSD.org> <482F1191.70709@icyb.net.ua> <482F1529.5080409@FreeBSD.org> <20080517175312.GM18958@deviant.kiev.zoral.com.ua> <48304F9D.9030406@FreeBSD.org> <20080518181549.GZ18958@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <821D2BD4-4C79-49B6-ADD9-2C5EA16B852A@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Suleiman Souhlal Date: Sun, 18 May 2008 12:47:07 -0700 To: Kostik Belousov X-Mailer: Apple Mail (2.753) Cc: freebsd-hackers@freebsd.org, Rui Paulo , Andriy Gapon Subject: Re: rdmsr from userspace 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, 18 May 2008 20:05:56 -0000 On May 18, 2008, at 11:15 AM, Kostik Belousov wrote: > On Sun, May 18, 2008 at 04:47:41PM +0100, Rui Paulo wrote: >> Kostik Belousov wrote: >>> On Sat, May 17, 2008 at 06:26:01PM +0100, Rui Paulo wrote: >>>> Andriy Gapon wrote: >>>>> on 17/05/2008 18:37 Rui Paulo said the following: >>>>>> Andriy Gapon wrote: >>>>>>> It seems that rdmsr instruction can be executed only at the >>>>>>> highest >>>>>>> privilege level and thus is not permitted from userland. >>>>>>> Maybe we >>>>>>> should provide something like Linux /dev/cpu/msr? >>>>>>> I don't like interface of that device, I think that ioctl >>>>>>> approach >>>>>>> would be preferable in this case. >>>>>>> Something like create /dev/cpuN and allow some ioctls on it: >>>>>>> ioctl(cpu_fd, CPU_RDMSR, arg). >>>>>>> What do you think? >>>>>>> >>>>>> While I think this (devcpu) is good for testing and >>>>>> development, I >>>>>> prefer having a device driver to handle that specific MSR than a >>>>>> generic /dev/cpuN where you can issue MSRs. >>>>>> Both for security and reliability reasons. >>>>> What about /dev/pci, /dev/io? Aren't they a precedent? >>>> They are, but, IMHO, we should no longer continue to create this >>>> type of >>>> interfaces. >>> >>> Why ? Are developers some kind of the second-class users ? >>> >>> I would have no opinion on providing /dev/cpu by the loadable >>> module, not >>> compiled into GENERIC. But the interface itself is useful at >>> least for >>> three things: >>> - CPU identification (see x86info or whatever it is called); >>> - CPU tweaking for bugs workaround without patching the kernel; >>> - updating the CPU microcode. >>> None of these is limited to the developers only. >> >> Input validation is my main concern here. Regarding to your two last >> points, I would prefer to have a microcode driver than a microcode >> userland utility that relies on devcpu. > Did you looked at the code ? It does exactly what you described. > > Driver has four basic operations: > read/write msr > perform cpu id work For what it's worth, CPUID is not a privileged instruction, so this doesn't need to be done in the kernel (as long as you have a way to pin a userland thread to a cpu, which I believe we have, now). I would personally would *really* to see stas's driver committed as well, as it's really useful. (I had a similar driver (but only for MSRs) that I was about to commit to 7.0 a few months ago, but re@ asked that I add a manpage, and I never got around to doing it: http://people.freebsd.org/~ssouhlal/testing/msr-20070707.diff It's slightly different from devcpu in that it works with lseek + read/write instead of ioctl). -- Suleiman From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 20:13:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80A101065687 for ; Sun, 18 May 2008 20:13:34 +0000 (UTC) (envelope-from prvs=1024cbb3dd=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 12AA98FC19 for ; Sun, 18 May 2008 20:13:33 +0000 (UTC) (envelope-from prvs=1024cbb3dd=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1211140563; x=1211745363; q=dns/txt; h=Received: Message-ID:From:To:Subject:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; bh=8qc+1tqRbLKPapYsFyL+O4TZ+/yYF2iwxw 70jmIuDM0=; b=jNkUrJhhJsnUdOQgy/1e2HzDlkaJ340uYWYBaKT7SVqw93W67i TV6RgIa5eBccMZhO3eCe4UvX7Z1s3uwV7NQYU2q8EuHmuHSkLoCJ4JVhbw4ufjzs L4aOn+HX/zGvtWJCtYJzvwfOXWrOI+yKt4jjD+5KLQ+KrP/3S5llutz94= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.5) with ESMTP id md50005635508.msg for ; Sun, 18 May 2008 20:56:02 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=1024cbb3dd=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Message-ID: From: "Steven Hartland" To: Date: Sun, 18 May 2008 20:56:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 18 May 2008 20:56:02 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 18 May 2008 20:56:03 +0100 Subject: Using sendmsg for SCM_CREDS results in EINVAL on PF_INET socket 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, 18 May 2008 20:13:34 -0000 sendmsg is not documented as ever returning EINVAL but yet when using the following code to send credentials to a remote host results in EINVAL from sendmsg. I suspect that SCM_CREDS is only valid for PF_LOCAL / PF_UNIX sockets and not PF_INET sockets and hence the code in dbus is actually invalid. Can anyone confirm this is the case or not? [code from dbus-sysdeps-unix.c] write_credentials_byte (int server_fd, DBusError *error) { int bytes_written; char buf[1] = { '\0' }; #if defined(HAVE_CMSGCRED) union { struct cmsghdr hdr; char cred[CMSG_SPACE (sizeof (struct cmsgcred))]; } cmsg; struct iovec iov; struct msghdr msg; iov.iov_base = buf; iov.iov_len = 1; memset (&msg, 0, sizeof (msg)); msg.msg_iov = &iov; msg.msg_iovlen = 1; msg.msg_control = (caddr_t) &cmsg; msg.msg_controllen = CMSG_SPACE (sizeof (struct cmsgcred)); memset (&cmsg, 0, sizeof (cmsg)); cmsg.hdr.cmsg_len = CMSG_LEN (sizeof (struct cmsgcred)); cmsg.hdr.cmsg_level = SOL_SOCKET; cmsg.hdr.cmsg_type = SCM_CREDS; #endif _DBUS_ASSERT_ERROR_IS_CLEAR (error); again: #if defined(HAVE_CMSGCRED) bytes_written = sendmsg (server_fd, &msg, 0); #else bytes_written = write (server_fd, buf, 1); #endif if (bytes_written < 0 && errno == EINTR) goto again; if (bytes_written < 0) { dbus_set_error (error, _dbus_error_from_errno (errno), "Failed to write credentials byte: %s", _dbus_strerror (errno)); return FALSE; } else if (bytes_written == 0) { dbus_set_error (error, DBUS_ERROR_IO_ERROR, "wrote zero bytes writing credentials byte"); return FALSE; } else { _dbus_assert (bytes_written == 1); _dbus_verbose ("wrote credentials byte\n"); return TRUE; } } [/code from dbus-sysdeps-unix.c] ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 21:01:54 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB4781065686 for ; Sun, 18 May 2008 21:01:54 +0000 (UTC) (envelope-from rpaulo@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 31A5A8FC17 for ; Sun, 18 May 2008 21:01:53 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so751266nfh.33 for ; Sun, 18 May 2008 14:01:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=c71sap8NVnK5k5BIOan5bv9HRJFAPeaWBRzIpN/0Oas=; b=P04RV3Cr78fN6Eyq6RVeOE9+P2dzjvnrLkF2p0iCpzCoKJo+ar5L+s6M/zq+z8Fho3ePGKiLfl6poWdU+ZOLmhqxL4PJZgvf2Xc80EBO/gzi2I4u4oVs4oUC75MQHbXkANPxv3ZxbVovq5GfpSq4WtdsdyG8NXyzol0LDCy4RR8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=st2bBVkLbWAUH5/desA7F8XfY9EJcoWZI4fOJp9HpJZs4R+rbhwGP6hy0bf6dIib/K20sqE2zTKu4cUScoM4QipCtGPS8H3UfLQBEmO7ZZsUgdeh0cgScdDJZ8LoPK5QtamsCnJ5leDnyt1sjH9SiUqIS25tAXl0IMqYcoPNkRs= Received: by 10.210.10.1 with SMTP id 1mr6065059ebj.167.1211144512605; Sun, 18 May 2008 14:01:52 -0700 (PDT) Received: from epsilon.local ( [89.214.185.160]) by mx.google.com with ESMTPS id c24sm10558692ika.4.2008.05.18.14.01.50 (version=SSLv3 cipher=RC4-MD5); Sun, 18 May 2008 14:01:51 -0700 (PDT) Message-ID: <4830993B.5070400@FreeBSD.org> Date: Sun, 18 May 2008 22:01:47 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Mike Meyer References: <482E93C0.4070802@icyb.net.ua> <20080517133037.3a3935db@bhuda.mired.org> <48305044.7000007@FreeBSD.org> <20080518140650.2691af1c@bhuda.mired.org> <48307700.70304@FreeBSD.org> <20080518152937.774cf492@bhuda.mired.org> In-Reply-To: <20080518152937.774cf492@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Rui Paulo Cc: freebsd-hackers@freebsd.org Subject: Re: rdmsr from userspace 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, 18 May 2008 21:01:54 -0000 Mike Meyer wrote: > > I don't think that would work - you'd have to register all those > hexadecimal strings as sysctl names. Yes, in theory you could also hack sysctl in a way that it doesn't walk when you do a sysctl -a, but works fine when you issue sysctl dev.cpu.N.0xffaabbcc, for example. I would be against this, though, because this will be like "sysctl on steroids", a really crude hack. > You could do an interface like > this, but the calling program would have to use sysctlnametomib to get > dev.cpu.N.msr, then append the MSR number to the results. Not really > very pretty. If you want to allow the user to poke at arbitrary msrs, > this would be a way to do it with sysctls, but the file api is > probably better. Agreed. > On the other hand, if you want to allow access to the fixed set of > documented msr's (for each cpu model, anyway), then handing back that > fixed set as an array would be a better approach, and would have the > advantage of not having to deal with invalid requests (non-existent > MSRs, 1-byte reads/writes of multi-byte MSRs, etc). > > On the other hand, it might be more useful - *especially* if the MSRs > move around depending on processor types (I honestly don't know) They do. At least on Intel (I don't know about AMD). But this "moving" is not documented. > - to > provide a "named" interface: > > dev.cpu.0.msr.mtrr > dev.cpu.0.msr.arr > dev.cpu.0.msr.efer > > and so on. You'd register the names when the module was initialized, > and would only register the ones that actually existed. You'd then > never have to deal with a request for a non-existent MSR, because the > sysctl call would return an error to the calling program without ever > calling your handler. > > Of course, you can *combine* these two approaches, and have: > > dev.cpu.0.msr.all # returns an array of all available msrs > dev.cpu.0.msr.have # an array of the available msrs > > but at this point it's just blue sky speculation... > >> I'll have to think about whether or not I like this interface. > > Actually, I'm more interested in why there seems to be a dislike > of file-based interfaces in favor of sysctls in the freebsd > community. Speaking for myself, sometimes sysctl is an interface that "just works" and is simple enough. Of course there are some types of structured data that don't belong to sysctl, but overall, I don't think we are abusing it. Creating a /dev node, handling ioctl's, etc. is much more work and error prone. That's all. At least for me. Regards, -- Rui Paulo From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 21:03:08 2008 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F4B21065670; Sun, 18 May 2008 21:03:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4923D8FC1B; Sun, 18 May 2008 21:03:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1Jxq26-000JMB-G4; Mon, 19 May 2008 00:03:06 +0300 Message-ID: <48309983.3070900@icyb.net.ua> Date: Mon, 19 May 2008 00:02:59 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: Rui Paulo References: <482E93C0.4070802@icyb.net.ua> <482EFBA0.30107@FreeBSD.org> <482F1191.70709@icyb.net.ua> <482F1529.5080409@FreeBSD.org> <20080517175312.GM18958@deviant.kiev.zoral.com.ua> <48304F9D.9030406@FreeBSD.org> <20080518181549.GZ18958@deviant.kiev.zoral.com.ua> <48307658.2080502@FreeBSD.org> In-Reply-To: <48307658.2080502@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , freebsd-hackers@FreeBSD.org Subject: Re: rdmsr from userspace 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, 18 May 2008 21:03:08 -0000 on 18/05/2008 21:32 Rui Paulo said the following: > > Yes, but I still don't like having everything mixed up in one driver. At > the very least, I would like us to have two drivers. One for the > microcode update and the other driver for the rest. > > I would like to see a microcode update utility (driver + something to > parse Intel's file aka devcpu-data) in the base system, but not "the > rest", though. Well, I am not sure what is a basis for such a requirement. As I pointed out before we already have /dev/pci and /dev/io and those are not going to go away, because there are quite reasonable applications that require those devices (and wide-spread too). And I think that sufficiently structured (via ioctl interface) access to CPU is also needed for some quite useful (and reasonable) userland applications. I can understand efforts to prevent foot-shooting, but I can not understand an approach of limiting abilities of a (sufficiently) privileged user. After all, he/she can rebuild a kernel and put all they need into it. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 04:40:38 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB8BF1065672 for ; Mon, 19 May 2008 04:40:38 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from n54.bullet.mail.sp1.yahoo.com (n54.bullet.mail.sp1.yahoo.com [98.136.44.32]) by mx1.freebsd.org (Postfix) with SMTP id ABD028FC18 for ; Mon, 19 May 2008 04:40:38 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from [216.252.122.217] by n54.bullet.mail.sp1.yahoo.com with NNFMP; 19 May 2008 04:40:38 -0000 Received: from [69.147.65.162] by t2.bullet.sp1.yahoo.com with NNFMP; 19 May 2008 04:40:38 -0000 Received: from [127.0.0.1] by omp407.mail.sp1.yahoo.com with NNFMP; 19 May 2008 04:40:38 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 321602.5892.bm@omp407.mail.sp1.yahoo.com Received: (qmail 40010 invoked by uid 60001); 19 May 2008 04:40:38 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=wIFgXeausS5UZH1v0Bw1Q/9OYhLsuJgD7MBGf4XnTxQ7t4maLJfg/U/RhjMHavuQvlTS4a2dhZHiv1xkPTrjpeumM2dH8dGr6ZMctbXLFxmJyjxaGNXeTmTkx2HUwBBnmESN60osohyH4QTumDhpdegXl+V/Ur1fZPouoFMlx1k=; X-YMail-OSG: VeC4TVUVM1mRw5SbrGZuE70CSmVMxtVYgoo2ciIHD1WRmNbE8QJQOAMO37FsUChtb7.HOwozdmUZ Received: from [125.91.74.81] by web46316.mail.sp1.yahoo.com via HTTP; Sun, 18 May 2008 21:40:37 PDT X-Mailer: YahooMailRC/975.41 YahooMailWebService/0.7.185 Date: Sun, 18 May 2008 21:40:37 -0700 (PDT) From: John Timony To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Message-ID: <130587.38887.qm@web46316.mail.sp1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Net Mask Prob! 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, 19 May 2008 04:40:38 -0000 Hi,all=0A=A0=0AI have installed Freebsd 7.0 on my Acer TravelMate 220,my ro= uter ip is 192.168.0.1,the ip of my Freebsd is 192.168.1.4,Net Mask is 255.= 255.0.0,Why my system can not connect wiht the router?=0A=A0=0Aany idea?=0A= =0A=0A From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 06:11:07 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8254D106567B for ; Mon, 19 May 2008 06:11:07 +0000 (UTC) (envelope-from tomoyuki@pobox.com) Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by mx1.freebsd.org (Postfix) with ESMTP id 47E5A8FC18 for ; Mon, 19 May 2008 06:11:07 +0000 (UTC) (envelope-from tomoyuki@pobox.com) Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id B4E8E21C9 for ; Mon, 19 May 2008 01:51:32 -0400 (EDT) Received: from fmv.c-wind.com (U021059.ppp.dion.ne.jp [218.222.21.59]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 5B84F21C8 for ; Mon, 19 May 2008 01:51:30 -0400 (EDT) Date: Mon, 19 May 2008 14:51:12 +0900 (JST) Message-Id: <20080519.145112.193697958.tomoyuki@pobox.com> To: freebsd-hackers@freebsd.org From: Tomoyuki Murakami In-Reply-To: <130587.38887.qm@web46316.mail.sp1.yahoo.com> References: <130587.38887.qm@web46316.mail.sp1.yahoo.com> X-Fingerprint: 3A 3C 3D 8A D3 7F D7 AC 0C 1C 2E C6 E1 8B 12 5B X-PGP-Key-URL: http://www.c-wind.com/tomoyuki@pobox.com.asc X-Mailer: Mew version 6.0.51 on Emacs 22.2.50 / Mule 5.0 (SAKAKI) X-Face: &9m:"[g#xi7*b@EePhiQRN|!8v_ZLJ2y36k=5R22P_.h].I8ti_*00uUULxu-o, 1)qF==5\ gB6^TJo0,+L!y?=zxth0iJbo65d List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 06:11:07 -0000 ----Security_Multipart(Mon_May_19_14_51_13_2008_720)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>> On Sun, 18 May 2008 21:40:37 -0700 (PDT), >>> John Timony wrote: fabonacci> I have installed Freebsd 7.0 on my Acer TravelMate 220,my router ip is 192.168.0.1,the ip of my Freebsd is 192.168.1.4,Net Mask is 255.255.0.0,Why my system can not connect wiht the router? I guess, you have to re-check your router's netmask config. ----Security_Multipart(Mon_May_19_14_51_13_2008_720)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iQCVAwUASDEVUccdBA2xrHKhAQJ8FQQA27hZx5Ba51F2DLWoGqksvEt6xy6YfjEC COPapD6Hx1S1a/bvJxpr7K7ocatfZMeTYEtDAmESRgdm43sXRo2s/kd7hO0C+8aD cb3jpF8CJ3L3bOn0GAWALo7qedr1q1gyu1zdZj8unnF/qu2XSdf/kNpjp08VTTzR nsv8B9TfrQg= =8FQR -----END PGP SIGNATURE----- ----Security_Multipart(Mon_May_19_14_51_13_2008_720)---- From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 06:31:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43E7A106567A for ; Mon, 19 May 2008 06:31:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2EF658FC20 for ; Mon, 19 May 2008 06:31:33 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E1B331CC038; Sun, 18 May 2008 23:31:33 -0700 (PDT) Date: Sun, 18 May 2008 23:31:33 -0700 From: Jeremy Chadwick To: John Timony Message-ID: <20080519063133.GA54791@eos.sc1.parodius.com> References: <130587.38887.qm@web46316.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <130587.38887.qm@web46316.mail.sp1.yahoo.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: Net Mask Prob! 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, 19 May 2008 06:31:34 -0000 On Sun, May 18, 2008 at 09:40:37PM -0700, John Timony wrote: > Hi,all >   > I have installed Freebsd 7.0 on my Acer TravelMate 220,my router ip is 192.168.0.1,the ip of my Freebsd is 192.168.1.4,Net Mask is 255.255.0.0,Why my system can not connect wiht the router? >   > any idea? Chances are your router uses 255.255.255.0 as a default netmask; most residential routers do. FreeBSD doesn't have any issues/bugs relating to netmasks which would cause what you're seeing. Additionally, your request probably should have gone to -net, not -hackers. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 07:44:34 2008 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92B43106566C for ; Mon, 19 May 2008 07:44:34 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from freebsd.alaskaparadise.com (freebsd.alaskaparadise.com [208.79.80.117]) by mx1.freebsd.org (Postfix) with ESMTP id 607918FC2C for ; Mon, 19 May 2008 07:44:34 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from 251-47-237-24.gci.net (251-47-237-24.gci.net [24.237.47.251]) by freebsd.alaskaparadise.com (Postfix) with ESMTP id 87FD22383962; Mon, 19 May 2008 07:28:49 +0000 (UTC) From: Beech Rintoul To: freebsd-hackers@FreeBSD.org Date: Sun, 18 May 2008 23:28:41 -0800 User-Agent: KMail/1.9.7 X-Face: jC2w\k*Q1\0DA2Q0Eh&BrP/Rt2M, ^2O#R07VoT98m*>miQF9%Bi9vy`F6cPjwEe?m, )2 X?M\:OE9QgZ"xT3/n3,3MJ7N=Cfkmi%f(w^~X"SUxn>; 27NO; C+)g[7J`$G*SN>{ X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Beech Rintoul Subject: Help with copytree code X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Beech Rintoul List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 07:44:34 -0000 --Boundary-00=_twSMINpc+IpqKUH Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline This copytree code is from bsd.port.mk, and I've been asked to try and find a fix. This is very handy for installing a whole tree (like a web app) keeping everything intact. It wasn't designed to copy to a populated directory so it affects everything in that dir, not just what's being installed. We need to keep it's functionality, but a fix is more than I can come up with. So I thought I'd ask you code gurus to help. If this can be fixed many will thank you! I attached it so it won't get line wrapped. Thanks, Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- --Boundary-00=_twSMINpc+IpqKUH-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 07:55:28 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E3DA106564A for ; Mon, 19 May 2008 07:55:28 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from freebsd.alaskaparadise.com (freebsd.alaskaparadise.com [208.79.80.117]) by mx1.freebsd.org (Postfix) with ESMTP id 2C8928FC22 for ; Mon, 19 May 2008 07:55:28 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from 251-47-237-24.gci.net (251-47-237-24.gci.net [24.237.47.251]) by freebsd.alaskaparadise.com (Postfix) with ESMTP id 8BAD62383939 for ; Mon, 19 May 2008 07:55:27 +0000 (UTC) From: Beech Rintoul To: freebsd-hackers@freebsd.org Date: Sun, 18 May 2008 23:55:22 -0800 User-Agent: KMail/1.9.7 References: <200805182328.45822.beech@freebsd.org> In-Reply-To: <200805182328.45822.beech@freebsd.org> X-Face: jC2w\k*Q1\0DA2Q0Eh&BrP/Rt2M,^2O#R07VoT98m*>miQF9%Bi9vy`F6cPjwEe?m,)=?utf-8?q?2=0A=09X=3FM=5C=3AOE9QgZ?="xT3/n3,3MJ7N=Cfkmi%f(w^~X"SUxn>; 27NO; C+)g[7J`$G*SN>{<=?utf-8?q?O=3Bg7=7C=0A=09o=7D=265A=5D4?=@7D`=Eb@Zs1Ln814?]|k@'bG=.Ca"[|8+_.OsNAo8!#?4u MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805182355.24787.beech@freebsd.org> Subject: Re: Help with copytree code X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Beech Rintoul List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 07:55:28 -0000 On Sunday 18 May 2008, Beech Rintoul said: > This copytree code is from bsd.port.mk, and I've been asked to try > and find a fix. This is very handy for installing a whole tree > (like a web app) keeping everything intact. It wasn't designed to > copy to a populated directory so it affects everything in that dir, > not just what's being installed. We need to keep it's > functionality, but a fix is more than I can come up with. So I > thought I'd ask you code gurus to help. If this can be fixed many > will thank you! > > I attached it so it won't get line wrapped. > > Thanks, > > Beech Looks like it got stripped off, so I posted it here: http://www.alaskaparadise.com/freebsd/copytree_code -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 08:53:28 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DA0B106566B for ; Mon, 19 May 2008 08:53:28 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 940668FC19 for ; Mon, 19 May 2008 08:53:27 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so830416nfh.33 for ; Mon, 19 May 2008 01:53:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=kkiyQNxIIAGMaW8QeCieK/uG7TyoU5sov8U9IaIoGiM=; b=dMiGiOtcdNHoqbiTmbuXbwvzbnQYwrO9PCxdFK3RL7wlHbX8EKSb9mckThEln0mU1g3Ledw9BThOb44sEtyzabafxx5jrOO5PYFSxY5TyGAHOH/VBfOxHjvbvYjmkPvMalQru5jiVlsWyJ+SDtybMVMTt354zEKvKLuHpFy9dog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Mu2CkZLxxPBTheYsEOosxzUG13FJ8M6OZNOEzZVHVKRpfH2VXQ5iVYPs+GICoSV/t0jyCU8NOG5LG+/naOyfAH2Uu3vHKp2KnoETvXSAGykX6H9EQyC8ujpxN6OoDI0SsrGgOvNgqZR3Egi85U8q8B17l4NrxQAnu4XVCxMAimc= Received: by 10.125.89.5 with SMTP id r5mr5695123mkl.34.1211187204117; Mon, 19 May 2008 01:53:24 -0700 (PDT) Received: by 10.86.26.8 with HTTP; Mon, 19 May 2008 01:53:24 -0700 (PDT) Message-ID: <7d6fde3d0805190153w7440aeack9bb596cf38cceecf@mail.gmail.com> Date: Mon, 19 May 2008 01:53:24 -0700 From: "Garrett Cooper" To: "Beech Rintoul" In-Reply-To: <200805182355.24787.beech@freebsd.org> MIME-Version: 1.0 References: <200805182328.45822.beech@freebsd.org> <200805182355.24787.beech@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Re: Help with copytree code 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, 19 May 2008 08:53:28 -0000 On Mon, May 19, 2008 at 12:55 AM, Beech Rintoul wrote: > On Sunday 18 May 2008, Beech Rintoul said: > > This copytree code is from bsd.port.mk, and I've been asked to try > > and find a fix. This is very handy for installing a whole tree > > (like a web app) keeping everything intact. It wasn't designed to > > copy to a populated directory so it affects everything in that dir, > > not just what's being installed. We need to keep it's > > functionality, but a fix is more than I can come up with. So I > > thought I'd ask you code gurus to help. If this can be fixed many > > will thank you! > > > > I attached it so it won't get line wrapped. > > > > Thanks, > > > > Beech > > Looks like it got stripped off, so I posted it here: > > http://www.alaskaparadise.com/freebsd/copytree_code What file patterns are you trying to copy over and what are you trying to avoid copying over? -Garrett From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 13:17:19 2008 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A57D106564A; Mon, 19 May 2008 13:17:19 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id B3E998FC0A; Mon, 19 May 2008 13:17:18 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m4JDHGR3000933; Mon, 19 May 2008 15:17:17 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m4JDHGbl000932; Mon, 19 May 2008 15:17:16 +0200 (CEST) (envelope-from olli) Date: Mon, 19 May 2008 15:17:16 +0200 (CEST) Message-Id: <200805191317.m4JDHGbl000932@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, Beech Rintoul In-Reply-To: <200805182328.45822.beech@freebsd.org> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (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]); Mon, 19 May 2008 15:17:17 +0200 (CEST) Cc: Subject: Re: Help with copytree code X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, Beech Rintoul List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 13:17:19 -0000 Beech Rintoul wrote: > This copytree code is from bsd.port.mk, and I've been asked to try and > find a fix. This is very handy for installing a whole tree (like a > web app) keeping everything intact. It wasn't designed to copy to a > populated directory so it affects everything in that dir, not just > what's being installed. We need to keep it's functionality, but a fix > is more than I can come up with. Why don't you simply do the chown+chmod on the source tree instead of doing it afterwards on the target tree? I think that would solve the problem. By the way, cpio(1) does have the option -R to change owner and/or group on the target files, so you don't need to run chown(1) afterwards. Unfortunately there doesn't seem to be an option to set the permission modes, though. Finally, I recommend you use the "-print0" option of find and the -0 option of cpio, so it will also work if there are any file names that contain spaces or other special characters. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 15:01:07 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19993106566C for ; Mon, 19 May 2008 15:01:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 01F2D8FC19 for ; Mon, 19 May 2008 15:01:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id 8BCA11A4D84; Mon, 19 May 2008 08:01:06 -0700 (PDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 19 May 2008 10:32:02 -0400 User-Agent: KMail/1.9.7 References: <4828557B.9000506@icyb.net.ua> <20080512182328.09a8a173@gumby.homeunix.com.> In-Reply-To: <20080512182328.09a8a173@gumby.homeunix.com.> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805191032.03134.jhb@freebsd.org> Cc: RW Subject: Re: i386 cpu_reset_real: code/comment mismatch 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, 19 May 2008 15:01:07 -0000 On Monday 12 May 2008 01:23:28 pm RW wrote: > On Mon, 12 May 2008 17:34:35 +0300 > > Andriy Gapon wrote: > > This is not a real issue, just a code clarification. > > > > First a snippet from sys/i386/i386/vm_machdep.c, cpu_reset_real() > > /* > > * Attempt to force a reset via the Reset Control register at > > * I/O port 0xcf9. Bit 2 forces a system reset when it is > > * written as 1. Bit 1 selects the type of reset to attempt: > > * 0 selects a "soft" reset, and 1 selects a "hard" reset. We > > * try to do a "soft" reset first, and then a "hard" reset. > > */ > > outb(0xcf9, 0x2); > > outb(0xcf9, 0x6); > > > > I think that the comment is correct up to but not including the last > > sentence. Writing 0x2 sets bit 1 to 1 (thus selecting hard reset), and > > writing 0x6 sets both bits 2 and 1 to 1 (thus performing hard reset). > > So we always just do a hard reset, no trying of soft reset (would it > > even make sense to do the last line of the comment says). > > It looks to me as if the comment was added retrospectively by someone > who got the two bits mixed-up when reading the source. If bits 1 and 2 > were the other way around, it would be code for a soft-reset followed > by a hard-reset. Or I just fubar'd the code. The comment and code were added at the same time and it should do a soft reset first. I'll have to go check the docs again to see which is wrong (comment or code). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 15:01:08 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 668FC1065671; Mon, 19 May 2008 15:01:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4D00A8FC0C; Mon, 19 May 2008 15:01:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id 9E0791A4D8D; Mon, 19 May 2008 08:01:07 -0700 (PDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 19 May 2008 10:37:11 -0400 User-Agent: KMail/1.9.7 References: <482E93C0.4070802@icyb.net.ua> <48307700.70304@FreeBSD.org> <20080518152945.60989b9c@bhuda.mired.org> In-Reply-To: <20080518152945.60989b9c@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805191037.12130.jhb@freebsd.org> Cc: Mike Meyer , Rui Paulo Subject: Re: rdmsr from userspace 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, 19 May 2008 15:01:08 -0000 On Sunday 18 May 2008 03:29:45 pm Mike Meyer wrote: > On Sun, 18 May 2008 19:35:44 +0100 > > Rui Paulo wrote: > > Mike Meyer wrote: > > > On Sun, 18 May 2008 16:50:28 +0100 > > > > > > Rui Paulo wrote: > > >> Mike Meyer wrote: > > >>> On Sat, 17 May 2008 11:13:52 +0300 > > >>> > > >>> Andriy Gapon wrote: > > >>>> It seems that rdmsr instruction can be executed only at the highest > > >>>> privilege level and thus is not permitted from userland. Maybe we > > >>>> should provide something like Linux /dev/cpu/msr? > > >>>> I don't like interface of that device, I think that ioctl approach > > >>>> would be preferable in this case. > > >>>> Something like create /dev/cpuN and allow some ioctls on it: > > >>>> ioctl(cpu_fd, CPU_RDMSR, arg). > > >>>> What do you think? > > >>> > > >>> Ok, this points directly at a question I've been wondering about, but > > >>> haven't been able to find an answer in the google. > > >>> > > >>> I've been mucking about with general access to sysctl's (a sysctl > > >>> plugin for gkrellm, and a python module for accessing sysctls), and > > >>> with that hammer in my hand, the nail for this problem is obviously a > > >>> dev.cpu.#.msr sysctl. > > >> > > >> How can you request a rdmsr within the sysctl tree? I don't think > > >> sysctl is appropriate here either. > > > > > > Reading (or writing) a sysctl mib can trigger a sysctl handler, which > > > can do pretty much anything. In particular, there are already examples > > > in the kernel where sysctl handlers use devices that don't have /dev > > > entries to get & set their values. Look through kern/kern_cpu.c and > > > i386/cpufreq/p4tcc.c to see the two ends of that kind of > > > connection. In fact, the cpu frequency sysctls would seem to be an > > > excellent model for something like the msr. > > > > > > ioctl, open+read/write, sysctl - they're all just interfaces to kernel > > > handlers. > > > > > > > > > Yes, sure, but who do you select the MSR you want to read or write? > > > > dev.cpu.N. ? > > I don't think that would work - you'd have to register all those > hexadecimal strings as sysctl names. You could do an interface like > this, but the calling program would have to use sysctlnametomib to get > dev.cpu.N.msr, then append the MSR number to the results. Not really > very pretty. If you want to allow the user to poke at arbitrary msrs, > this would be a way to do it with sysctls, but the file api is > probably better. Actually, you don't have to register all of them. You can write a node handler which parses the next item in the MIB directly. Look at the all the proc sysctl's which accept a PID for example. That said, I think if someone already has a device driver done that is fine. I also think it is ok to let root request arbitrary MSR's from userland using an ioctl() or the like. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 15:39:18 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6ADD106567D; Mon, 19 May 2008 15:39:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay01.kiev.sovam.com (relay01.kiev.sovam.com [62.64.120.200]) by mx1.freebsd.org (Postfix) with ESMTP id 43ED78FC0C; Mon, 19 May 2008 15:39:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay01.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1Jy7SF-0006AD-Nk; Mon, 19 May 2008 18:39:16 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m4JFd4iD046128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 May 2008 18:39:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m4JFd2l9065516; Mon, 19 May 2008 18:39:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m4JFd28k065515; Mon, 19 May 2008 18:39:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 19 May 2008 18:39:02 +0300 From: Kostik Belousov To: John Baldwin Message-ID: <20080519153902.GG18958@deviant.kiev.zoral.com.ua> References: <482E93C0.4070802@icyb.net.ua> <48307700.70304@FreeBSD.org> <20080518152945.60989b9c@bhuda.mired.org> <200805191037.12130.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TG/adJaYDs0AFCGK" Content-Disposition: inline In-Reply-To: <200805191037.12130.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on skuns.kiev.zoral.com.ua X-Scanner-Signature: 8f05f8c1fbcffa8edf4596457ca31d97 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 2844 [May 13 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0278], KAS30/Release Cc: stas@freebsd.org, freebsd-hackers@freebsd.org, Mike Meyer , Rui Paulo Subject: Re: rdmsr from userspace 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, 19 May 2008 15:39:18 -0000 --TG/adJaYDs0AFCGK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 19, 2008 at 10:37:11AM -0400, John Baldwin wrote: > On Sunday 18 May 2008 03:29:45 pm Mike Meyer wrote: > > On Sun, 18 May 2008 19:35:44 +0100 > > > > Rui Paulo wrote: > > > Mike Meyer wrote: > > > > On Sun, 18 May 2008 16:50:28 +0100 > > > > > > > > Rui Paulo wrote: > > > >> Mike Meyer wrote: > > > >>> On Sat, 17 May 2008 11:13:52 +0300 > > > >>> > > > >>> Andriy Gapon wrote: > > > >>>> It seems that rdmsr instruction can be executed only at the high= est > > > >>>> privilege level and thus is not permitted from userland. Maybe we > > > >>>> should provide something like Linux /dev/cpu/msr? > > > >>>> I don't like interface of that device, I think that ioctl approa= ch > > > >>>> would be preferable in this case. > > > >>>> Something like create /dev/cpuN and allow some ioctls on it: > > > >>>> ioctl(cpu_fd, CPU_RDMSR, arg). > > > >>>> What do you think? > > > >>> > > > >>> Ok, this points directly at a question I've been wondering about,= but > > > >>> haven't been able to find an answer in the google. > > > >>> > > > >>> I've been mucking about with general access to sysctl's (a sysctl > > > >>> plugin for gkrellm, and a python module for accessing sysctls), a= nd > > > >>> with that hammer in my hand, the nail for this problem is obvious= ly a > > > >>> dev.cpu.#.msr sysctl. > > > >> > > > >> How can you request a rdmsr within the sysctl tree? I don't think > > > >> sysctl is appropriate here either. > > > > > > > > Reading (or writing) a sysctl mib can trigger a sysctl handler, whi= ch > > > > can do pretty much anything. In particular, there are already examp= les > > > > in the kernel where sysctl handlers use devices that don't have /dev > > > > entries to get & set their values. Look through kern/kern_cpu.c and > > > > i386/cpufreq/p4tcc.c to see the two ends of that kind of > > > > connection. In fact, the cpu frequency sysctls would seem to be an > > > > excellent model for something like the msr. > > > > > > > > ioctl, open+read/write, sysctl - they're all just interfaces to ker= nel > > > > handlers. > > > > > > > > > > > > > Yes, sure, but who do you select the MSR you want to read or write? > > > > > > dev.cpu.N. ? > > > > I don't think that would work - you'd have to register all those > > hexadecimal strings as sysctl names. You could do an interface like > > this, but the calling program would have to use sysctlnametomib to get > > dev.cpu.N.msr, then append the MSR number to the results. Not really > > very pretty. If you want to allow the user to poke at arbitrary msrs, > > this would be a way to do it with sysctls, but the file api is > > probably better. >=20 > Actually, you don't have to register all of them. You can write a node= =20 > handler which parses the next item in the MIB directly. Look at the all = the=20 > proc sysctl's which accept a PID for example. That said, I think if some= one=20 > already has a device driver done that is fine. I also think it is ok to = let=20 > root request arbitrary MSR's from userland using an ioctl() or the like. I started a conversation with Stas about committing the driver. --TG/adJaYDs0AFCGK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkgxnxYACgkQC3+MBN1Mb4iWDgCgtAOhfzbuL1VEJ69e09B8tOjO EVgAoLhCGDgAX31TLHuxtgsBii2YyHBd =ukOk -----END PGP SIGNATURE----- --TG/adJaYDs0AFCGK-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 18:55:30 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9F891065676 for ; Mon, 19 May 2008 18:55:30 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 40DC28FC2E for ; Mon, 19 May 2008 18:55:30 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A5226.dip.t-dialin.net [84.154.82.38]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id m4JItRWB090010; Mon, 19 May 2008 20:55:28 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m4JIvnqF038706; Mon, 19 May 2008 20:57:49 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m4JIvde7050309; Mon, 19 May 2008 20:57:49 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200805191857.m4JIvde7050309@fire.js.berklix.net> to: freebsd-hackers@freebsd.org In-reply-to: <200805151824.m4FIOFBm000937@fire.js.berklix.net> References: <200805151824.m4FIOFBm000937@fire.js.berklix.net> Comments: In-reply-to "Julian Stacey" message dated "Thu, 15 May 2008 20:24:15 +0200." Date: Mon, 19 May 2008 20:57:39 +0200 From: "Julian H. Stacey" Cc: Subject: Re: Not seeing enough memory though its there. 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, 19 May 2008 18:55:30 -0000 I've found the answer to my RAM puzzle: Hardware design limitation. - Main board has 32M soldered on, - Single slot. (lettering on PCB, 168 pin DIMM 3.3V Unbuffered), can take 1 DIMM (though board works without). - Plugging in a 32M Ram DIMM, BIOS reports 64 MB. - Chips on main board: 1 x SB82437VX System Controller 2 x S82438VX Data Path Intel PCIset 430 VX spec claims to support 4 to 128 M DRAM - I guess board implemented as up to 64 M on the DIMM slot & [up to 64M in theory, or 32M in practice] soldered on the board. So 96M max. - Weirdly, 128 DIMM +32 on board reported as 56, Bad DIMM maybe ? (RAMOS Technology Co Ltd RM28S180TC-13AC 128MB, Sync, 133 MHz, CL3.) - I have here loose: 32M, 128 & 256. To raise my dmesg from 64 to 96, I would need to use a 256M DIMM ! - Time to swap with my other machines (though not sure of speed issues). - I also found a probable red herring: Some problem with MS @ 64M http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=33937&lc=en&cc=us&lang=en&os=19&product=92286&dlc=en Presario Fix for Windows 95 NTKERN Error with 64 MB RAM Intended for use on systems with Windows 95 OSR1 or OSR2. Affects Compaq Presario desktops and notebooks with Windows 95 and EXACTLY 64 MB of memory (RAM). Last posting for Ref.: > Hi Hackers cc Gary J, > On a Compaq Presario 2254 with 7.0-Release & Generic kernel, I'm > not seeing enough RAM: A 128M DIM reports as 56M, a 256M reports as > 96M. Any ideas please ? > > dmesg > FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 > root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD-K6tm w/ multimedia extensions (233.03-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 > Features=0x8001bf > AMD Features=0x400<> > real memory = 100663296 (96 MB) > avail memory = 84484096 (80 MB) > pnpbios: Bad PnP BIOS data checksum # Dont know why bad > > With a 128M RAM > Without hw.physmem= in /boot/loader.conf > dmesg > real memory = 58720256 (56 MB) > avail memory = 43507712 (41 MB) > sysctl -a | grep mem > hw.physmem: 45572096 > hw.usermem: 33267712 > hw.realmem: 58720256 > With /boot/loader.conf hw.physmem=134217728 > same as above except > hw.usermem: 33312768 > With a 256 RAM > power on Bios auto resizes to about 96M ! > Without hw.physmem= > dmesg > real memory = 100663296 (96 MB) > avail memory = 84484096 (80 MB) > sysctl -a | grep mem > hw.physmem: 87515136 > hw.usermem: 74280960 > hw.realmem: 100663296 > With /boot/loader.conf hw.physmem=268435456 > same as above except > hw.usermem: 74141696 Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail just Ascii plain text. HTML & Base64 text are spam. From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 21:51:58 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DAF0106567F for ; Mon, 19 May 2008 21:51:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 78D108FC26 for ; Mon, 19 May 2008 21:51:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id 07AD61A4D82; Mon, 19 May 2008 14:51:57 -0700 (PDT) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m4JLpoY8041711; Mon, 19 May 2008 17:51:51 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 19 May 2008 17:51:32 -0400 User-Agent: KMail/1.9.7 References: <4828557B.9000506@icyb.net.ua> <20080512182328.09a8a173@gumby.homeunix.com.> <200805191032.03134.jhb@freebsd.org> In-Reply-To: <200805191032.03134.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805191751.32336.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 19 May 2008 17:51:51 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/7174/Mon May 19 15:48:02 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: RW Subject: Re: i386 cpu_reset_real: code/comment mismatch 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, 19 May 2008 21:51:58 -0000 On Monday 19 May 2008 10:32:02 am John Baldwin wrote: > On Monday 12 May 2008 01:23:28 pm RW wrote: > > On Mon, 12 May 2008 17:34:35 +0300 > > > > Andriy Gapon wrote: > > > This is not a real issue, just a code clarification. > > > > > > First a snippet from sys/i386/i386/vm_machdep.c, cpu_reset_real() > > > /* > > > * Attempt to force a reset via the Reset Control register at > > > * I/O port 0xcf9. Bit 2 forces a system reset when it is > > > * written as 1. Bit 1 selects the type of reset to attempt: > > > * 0 selects a "soft" reset, and 1 selects a "hard" reset. We > > > * try to do a "soft" reset first, and then a "hard" reset. > > > */ > > > outb(0xcf9, 0x2); > > > outb(0xcf9, 0x6); > > > > > > I think that the comment is correct up to but not including the last > > > sentence. Writing 0x2 sets bit 1 to 1 (thus selecting hard reset), and > > > writing 0x6 sets both bits 2 and 1 to 1 (thus performing hard reset). > > > So we always just do a hard reset, no trying of soft reset (would it > > > even make sense to do the last line of the comment says). > > > > It looks to me as if the comment was added retrospectively by someone > > who got the two bits mixed-up when reading the source. If bits 1 and 2 > > were the other way around, it would be code for a soft-reset followed > > by a hard-reset. > > Or I just fubar'd the code. The comment and code were added at the same time > and it should do a soft reset first. I'll have to go check the docs again to > see which is wrong (comment or code). So, the comment is correct and not the code. Curiously enough, OpenSolaris does the same thing (it writes 0x2 followed by 0x6), but it has some sort of comment which implies that you have to do a write to set or clear bit 1 before setting bit 2. Linux only uses 0xcf9 on a specific x86 machine (View workstation or some such) in which case it just does a single write of 0x6. I'll test locally to make sure 0x4 and 0x6 both work and if so I will commit the fix. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 22:25:35 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF0BC1065682; Mon, 19 May 2008 22:25:35 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id B30908FC0A; Mon, 19 May 2008 22:25:35 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [85.21.245.235] (helo=phonon.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1JyDKZ-0007BF-EF; Tue, 20 May 2008 01:55:43 +0400 Received: by phonon.ht-systems.ru (Postfix, from userid 1001) id CD5587EDDD9; Tue, 20 May 2008 01:55:45 +0400 (MSD) Date: Tue, 20 May 2008 01:55:45 +0400 From: Stanislav Sedov To: Beech Rintoul Message-Id: <20080520015545.c9456ac5.stas@FreeBSD.org> In-Reply-To: <200805182355.24787.beech@freebsd.org> References: <200805182328.45822.beech@freebsd.org> <200805182355.24787.beech@freebsd.org> Organization: The FreeBSD Project X-XMPP: ssedov@jabber.ru X-Voice: +7 916 849 20 23 X-PGP-Fingerprin: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Help with copytree code 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, 19 May 2008 22:25:36 -0000 On Sun, 18 May 2008 23:55:22 -0800 Beech Rintoul mentioned: > On Sunday 18 May 2008, Beech Rintoul said: > > This copytree code is from bsd.port.mk, and I've been asked to try > > and find a fix. This is very handy for installing a whole tree > > (like a web app) keeping everything intact. It wasn't designed to > > copy to a populated directory so it affects everything in that dir, > > not just what's being installed. We need to keep it's > > functionality, but a fix is more than I can come up with. So I > > thought I'd ask you code gurus to help. If this can be fixed many > > will thank you! > > > > I attached it so it won't get line wrapped. > > > > Thanks, > > > > Beech > > Looks like it got stripped off, so I posted it here: > > http://www.alaskaparadise.com/freebsd/copytree_code > I think the following will do the trick, though I have not tested it: http://mbsd.msk.ru/dist/copytree.diff -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@FreeBSD.ORG Mon May 19 21:55:13 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 857DE106566B for ; Mon, 19 May 2008 21:55:13 +0000 (UTC) (envelope-from lgj@usenix.org) Received: from usenix.org (voyager.usenix.org [131.106.3.1]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB118FC25 for ; Mon, 19 May 2008 21:55:13 +0000 (UTC) (envelope-from lgj@usenix.org) Received: from merope.usenix.org (merope.usenix.org [131.106.3.129]) by usenix.org (8.13.6/8.13.6) with ESMTP id m4JLtCXQ014024 for ; Mon, 19 May 2008 14:55:13 -0700 (PDT) Message-ID: <4831F73F.3080207@usenix.org> Date: Mon, 19 May 2008 14:55:11 -0700 From: Lionel Garth Jones User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Usenix-Metrics: voyager; whitelist X-Mailman-Approved-At: Tue, 20 May 2008 02:19:29 +0000 Subject: Top 5 Reasons to Attend USENIX '08 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, 19 May 2008 21:55:13 -0000 ---------------------------------------------- Top 5 Reasons to Attend the 2008 USENIX Annual Technical Conference June 22-27, 2008, Boston, MA http://www.usenix.org/usenix08/progb ---------------------------------------------- USENIX '08 offers a cost-effective, one-stop shop for the latest in IT training, breakthroughs, and systems research. Check out the top 5 reasons to join us in Boston, MA, June 22-27, 2008: 1. Top-notch training: Highly respected experts provide you with new information and skills you can take back to work tomorrow. Topics include: -- Bruce Potter on Botnets: Understanding and Defense -- Peter Baer Galvin on Solaris 10 Administration -- Phil Cox on Securing Virtual Environments -- Alan Robertson on Configuring and Deploying Linux-HA To view the entire training program, see: http://www.usenix.org/events/usenix08/training 2. Invited Talks that feature luminaries in computing discussing timely and important topics, such as: -- Keynote Address by David Patterson, Director of the U.C. Berkeley Parallel Computing Laboratory, on "The Parallel Revolution Has Started: Are You Part of the Solution or Part of the Problem?" -- Plenary Closing Session by Matthew Melis of the NASA Glenn Research Center on "The Columbia Accident Investigation and Returning NASA's Space Shuttle to Flight" -- Drew Endy, Cabot Assistant Professor of Biological Engineering at MIT and a co-founder of the BioBricks Foundation (BBF), on "Programming DNA: A 2-bit Language for Engineering Biology" -- And more! http://www.usenix.org/usenix08/ITs 3. You'll see it here first: -- The latest developments in cutting-edge systems research in the Refereed Papers track. http://www.usenix.org/events/usenix08/tech -- An introduction to interesting new or ongoing work at the Poster Session. http://www.usenix.org/events/usenix08/activities.html#poster 4. Answers to your toughest questions: -- Guru Is In sessions feature experts who come prepared to respond to your most burning technical questions on hot topics. The full list of topics will be announced soon! http://www.usenix.org/events/usenix08/tech 5. The chance to mingle with industry leaders: -- Evening events such as the Birds-of-a-Feather (BoF) sessions offer additional opportunities to network with peers to gain that all-important "insider" IT knowledge. http://www.usenix.org/events/usenix08/bofs.html And that's just the beginning. Visit http://www.usenix.org/usenix08/progb to see the full list of offerings. Don't forget: -- Register by June 6 and save up to $300! http://www.usenix.org/events/usenix08/registration -- Take advantage of the multiple employee discount for groups sending 5 or more: http://www.usenix.org/events/usenix08/registration/#multi -- Chat with other attendees on the USENIX '08 Facebook page: http://www.facebook.com/event.php?eid=12521903959 ---------------------------------------------- 2008 USENIX Annual Technical Conference June 22-27, 2008, Boston, MA http://www.usenix.org/usenix08/progb Early Bird Registration Deadline: June 6, 2008 ----------------------------------------------- From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 13:37:59 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38E89106564A; Tue, 20 May 2008 13:37:59 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id DB94E8FC22; Tue, 20 May 2008 13:37:58 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id CF9C7744005; Tue, 20 May 2008 16:37:56 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDVWcwrMWOJs; Tue, 20 May 2008 16:37:56 +0300 (EEST) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [88.81.251.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 328FC744004; Tue, 20 May 2008 16:37:56 +0300 (EEST) Message-ID: <4832D432.2050907@icyb.net.ua> Date: Tue, 20 May 2008 16:37:54 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080311) MIME-Version: 1.0 To: John Baldwin References: <1210616585.00069210.1210605002@10.7.7.3> <1210627393.00069294.1210614002@10.7.7.3> <1211221409.00072277.1211209802@10.7.7.3> <1211246591.00072455.1211234402@10.7.7.3> In-Reply-To: <1211246591.00072455.1211234402@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, RW Subject: Re: i386 cpu_reset_real: code/comment mismatch 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, 20 May 2008 13:37:59 -0000 on 20/05/2008 00:51 John Baldwin said the following: > So, the comment is correct and not the code. Curiously enough, OpenSolaris > does the same thing (it writes 0x2 followed by 0x6), but it has some sort of > comment which implies that you have to do a write to set or clear bit 1 > before setting bit 2. Linux only uses 0xcf9 on a specific x86 machine (View > workstation or some such) in which case it just does a single write of 0x6. > I'll test locally to make sure 0x4 and 0x6 both work and if so I will commit > the fix. And this code is most likely never reached in majority of the cases, reset via keyboard controller should just work. BTW, I understand that there is a difference between hard and soft reset in terms of hardware signals being asserted, but I don't quite understand general consequences. I.e. what is a practical difference between hard and soft reset? -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 14:03:47 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0BB7106564A for ; Tue, 20 May 2008 14:03:46 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from n74a.bullet.mail.sp1.yahoo.com (n74a.bullet.mail.sp1.yahoo.com [98.136.45.21]) by mx1.freebsd.org (Postfix) with SMTP id D4DCB8FC1E for ; Tue, 20 May 2008 14:03:46 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from [216.252.122.219] by n74.bullet.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:03:46 -0000 Received: from [69.147.65.166] by t4.bullet.sp1.yahoo.com with NNFMP; 20 May 2008 14:03:46 -0000 Received: from [127.0.0.1] by omp501.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:03:46 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 424681.70792.bm@omp501.mail.sp1.yahoo.com Received: (qmail 39569 invoked by uid 60001); 20 May 2008 14:03:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=loxk9WRzEXoF62P+LD6oSG07yMSq/EJ519+BDYbe+M/WH4Lg9L1kI1U969qXahiskkUr8l8Cban6DprDdLq583niL1FU0KSBzjW6MVHEZhCXxPo/6WFBPtP+QT7XTI7bXQlm6s1gVbbUgM5sbMN6QY2dX6MioCZaHQ3VHmK0NOs=; X-YMail-OSG: cY7g2vUVM1kK.AeYXZBG982ETJQbfxD6Kc9kFWM7DITBITpQLiHiI8sW2lZMsaoer2yptARUtZX9SwZfvHHvFEZllIimfS0- Received: from [59.35.34.174] by web46301.mail.sp1.yahoo.com via HTTP; Tue, 20 May 2008 07:03:45 PDT Date: Tue, 20 May 2008 07:03:45 -0700 (PDT) From: John Timony To: MIME-Version: 1.0 Message-ID: <171598.39316.qm@web46301.mail.sp1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Slowly Gnome on FreeBSD 7.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 14:03:47 -0000 BlankBODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; =FONT-FAMILY: Arial, Helvetica}P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =FONT-FAMILY: Helvetica, "Times New Roman"}LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =FONT-FAMILY: Helvetica, "Times New Roman"}Hi,all I have tried to post this =question to the=20right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I =install=20Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 =by=20sysinstall.. I type these =commands: #Xorg -configure #Xorg -config =xorg.conf.new #echo "exec=20gnome-session">~/.xinitrs #startx After this,I can enter gnome=20destop,but it shows me a window with a title "root",,,and then it=20disapears,,,and then apears again,,,and disapear again time and=20time... The gnome destop is slow,and =repeat the=20window again and again,,,I can not use gnome destop to do any=20thing... P.S. The Gnome destop icon =didn't=20apear... Any idea? S.O.S! By =Fabonacci. BlankBODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; FONT-FAMILY: Arial, Helvetica}P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; FONT-FAMILY: Helvetica, "Times New Roman"}LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; FONT-FAMILY: Helvetica, "Times New Roman"}Hi,all I have tried to post this question to the right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I install Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 by sysinstall.. I type these commands: #Xorg -configure #Xorg -config xorg.conf.new #echo "exec gnome-session">~/.xinitrs #startx After this,I can enter gnome destop,but it shows me a window with a title "root",,,and then it disapears,,,and then apears again,,,and disapear again time and time... The gnome destop is slow,and repeat the window again and again,,,I can not use gnome destop to do any thing... P.S. The Gnome destop icon didn't apear... Any idea? S.O.S! By Fabonacci. From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 14:06:19 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD3001065680 for ; Tue, 20 May 2008 14:06:19 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from n68.bullet.mail.sp1.yahoo.com (n68.bullet.mail.sp1.yahoo.com [98.136.44.44]) by mx1.freebsd.org (Postfix) with SMTP id B18098FC17 for ; Tue, 20 May 2008 14:06:19 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from [216.252.122.218] by n68.bullet.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:06:15 -0000 Received: from [69.147.65.166] by t3.bullet.sp1.yahoo.com with NNFMP; 20 May 2008 14:06:15 -0000 Received: from [127.0.0.1] by omp501.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:06:15 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 31708.92326.bm@omp501.mail.sp1.yahoo.com Received: (qmail 18988 invoked by uid 60001); 20 May 2008 14:06:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=mcbSUQSOTO41xjqjMJ9PhqexXm0/o4wgEJ1p42OWSF+GjZi7MH/reazw+CTCRNSu7/D9fF181anPhh0GEYjKN2Dkcn+I2itdFQmW0vQ6b4bZ+AMXi4YrfbGsq1v0jq0H7qKRcEUHWJ3Sscwvm6/kZde5NtH1i4zqDR65wOss9lY=; X-YMail-OSG: VxPtSoQVM1m2cbt4SwIMzePdURm8UTsBhmet4rqYIIe6OlqQ_ZM1n25fETkrzQhVeH95E.LGbZYl Received: from [59.35.34.174] by web46305.mail.sp1.yahoo.com via HTTP; Tue, 20 May 2008 07:06:14 PDT Date: Tue, 20 May 2008 07:06:14 -0700 (PDT) From: John Timony To: MIME-Version: 1.0 Message-ID: <870482.18832.qm@web46305.mail.sp1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Slowly Gnome on FreeBSD 7.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 14:06:19 -0000 BlankBODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; =FONT-FAMILY: Arial, Helvetica}P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =FONT-FAMILY: Helvetica, "Times New Roman"}LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =FONT-FAMILY: Helvetica, "Times New Roman"}Hi,all I have tried to post this =question to the=20right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I =install=20Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 =by=20sysinstall.. I type these =commands: #Xorg -configure #Xorg -config =xorg.conf.new #echo "exec=20gnome-session">~/.xinitrs #startx After this,I can enter gnome=20destop,but it shows me a window with a title "root",,,and then it=20disapears,,,and then apears again,,,and disapear again time and=20time... The gnome destop is slow,and =repeat the=20window again and again,,,I can not use gnome destop to do any=20thing... P.S. The Gnome destop icon =didn't=20apear... Any idea? S.O.S! By =Fabonacci. BlankBODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; FONT-FAMILY: Arial, Helvetica}P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; FONT-FAMILY: Helvetica, "Times New Roman"}LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; FONT-FAMILY: Helvetica, "Times New Roman"}Hi,all I have tried to post this question to the right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I install Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 by sysinstall.. I type these commands: #Xorg -configure #Xorg -config xorg.conf.new #echo "exec gnome-session">~/.xinitrs #startx After this,I can enter gnome destop,but it shows me a window with a title "root",,,and then it disapears,,,and then apears again,,,and disapear again time and time... The gnome destop is slow,and repeat the window again and again,,,I can not use gnome destop to do any thing... P.S. The Gnome destop icon didn't apear... Any idea? S.O.S! By Fabonacci. From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 14:06:28 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E8E1065682 for ; Tue, 20 May 2008 14:06:28 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from n59.bullet.mail.sp1.yahoo.com (n59.bullet.mail.sp1.yahoo.com [98.136.44.43]) by mx1.freebsd.org (Postfix) with SMTP id 780AC8FC18 for ; Tue, 20 May 2008 14:06:28 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from [216.252.122.219] by n59.bullet.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:06:28 -0000 Received: from [69.147.65.153] by t4.bullet.sp1.yahoo.com with NNFMP; 20 May 2008 14:06:27 -0000 Received: from [127.0.0.1] by omp401.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:06:27 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 899332.72583.bm@omp401.mail.sp1.yahoo.com Received: (qmail 85508 invoked by uid 60001); 20 May 2008 14:06:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ad9Ni/dM3Zqjkpn4jCIvg/B3tiyXkFabSFwJDunhRYGdA26KLvmajWFSW2fR+1EtU85ZRb7oxwCuqpIjpLc51Ki96ZL5OfNddPg1ZpP6kb1S6KT1OhqWpW2Gl2V77vSnox4sPq6HvsmV3tmU7hDO25ByHWC4Bdl922QJKp/y08A=; X-YMail-OSG: RB0pzvgVM1mX16zkjHbRt865ZuVa80Huejfq2v9SuGWKie3afc8Bf8uWuBZ4wrnUcZv7vMcXY61d Received: from [59.35.34.174] by web46311.mail.sp1.yahoo.com via HTTP; Tue, 20 May 2008 07:06:27 PDT Date: Tue, 20 May 2008 07:06:27 -0700 (PDT) From: John Timony To: MIME-Version: 1.0 Message-ID: <810582.84518.qm@web46311.mail.sp1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Slowly Gnome on FreeBSD 7.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 14:06:28 -0000 BlankBODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; =FONT-FAMILY: Arial, Helvetica}P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =FONT-FAMILY: Helvetica, "Times New Roman"}LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =FONT-FAMILY: Helvetica, "Times New Roman"}Hi,all I have tried to post this =question to the=20right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I =install=20Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 =by=20sysinstall.. I type these =commands: #Xorg -configure #Xorg -config =xorg.conf.new #echo "exec=20gnome-session">~/.xinitrs #startx After this,I can enter gnome=20destop,but it shows me a window with a title "root",,,and then it=20disapears,,,and then apears again,,,and disapear again time and=20time... The gnome destop is slow,and =repeat the=20window again and again,,,I can not use gnome destop to do any=20thing... P.S. The Gnome destop icon =didn't=20apear... Any idea? S.O.S! By =Fabonacci. BlankBODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; FONT-FAMILY: Arial, Helvetica}P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; FONT-FAMILY: Helvetica, "Times New Roman"}LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; FONT-FAMILY: Helvetica, "Times New Roman"}Hi,all I have tried to post this question to the right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I install Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 by sysinstall.. I type these commands: #Xorg -configure #Xorg -config xorg.conf.new #echo "exec gnome-session">~/.xinitrs #startx After this,I can enter gnome destop,but it shows me a window with a title "root",,,and then it disapears,,,and then apears again,,,and disapear again time and time... The gnome destop is slow,and repeat the window again and again,,,I can not use gnome destop to do any thing... P.S. The Gnome destop icon didn't apear... Any idea? S.O.S! By Fabonacci. From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 14:07:11 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E8091065671 for ; Tue, 20 May 2008 14:07:11 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from n62.bullet.mail.sp1.yahoo.com (n62.bullet.mail.sp1.yahoo.com [98.136.44.35]) by mx1.freebsd.org (Postfix) with SMTP id 732EA8FC12 for ; Tue, 20 May 2008 14:07:11 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from [216.252.122.219] by n62.bullet.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:07:11 -0000 Received: from [69.147.84.123] by t4.bullet.sp1.yahoo.com with NNFMP; 20 May 2008 14:07:11 -0000 Received: from [127.0.0.1] by omp209.mail.sp1.yahoo.com with NNFMP; 20 May 2008 14:07:11 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 221349.29730.bm@omp209.mail.sp1.yahoo.com Received: (qmail 12478 invoked by uid 60001); 20 May 2008 14:07:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=bNcklLb/KrXgVcwSMvTc5ghhk9aPnVsz7bjBD0yqckuYvFhnANllS1K6ui5jcjVyxzUZZdFrSbEqNvQYdMVbnaXULt1rnYbohSQO2dq67U2awNwW3N+tyFELOpLLDxVOpWmqOaG+oCs7kkjekfgWTjWQw+HCWv8BWWCSf1Cf1lE=; X-YMail-OSG: QQc2reMVM1myhS85.DZp89oTh7Jt6g_F4NokliRB Received: from [59.35.34.174] by web46306.mail.sp1.yahoo.com via HTTP; Tue, 20 May 2008 07:07:10 PDT Date: Tue, 20 May 2008 07:07:10 -0700 (PDT) From: John Timony To: MIME-Version: 1.0 Message-ID: <112879.11288.qm@web46306.mail.sp1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Slowly Gnome on FreeBSD 7.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 14:07:11 -0000 Hi,all I have tried to post this =question to the=20right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I =install=20Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 =by=20sysinstall.. I type these =commands: #Xorg -configure #Xorg -config =xorg.conf.new #echo "exec=20gnome-session">~/.xinitrs #startx After this,I can enter gnome=20destop,but it shows me a window with a title "root",,,and then it=20disapears,,,and then apears again,,,and disapear again time and=20time... The gnome destop is slow,and =repeat the=20window again and again,,,I can not use gnome destop to do any=20thing... P.S. The Gnome destop icon =didn't=20apear... Any idea? S.O.S! By=20Fabonacci. Hi,all I have tried to post this question to the right mail list,but have no responds,so i try to post here. In my Acer TravelMate 220,I install Freebsd7.0 by using Minimal way,and then install Xorg,ports,and Gnome2 by sysinstall.. I type these commands: #Xorg -configure #Xorg -config xorg.conf.new #echo "exec gnome-session">~/.xinitrs #startx After this,I can enter gnome destop,but it shows me a window with a title "root",,,and then it disapears,,,and then apears again,,,and disapear again time and time... The gnome destop is slow,and repeat the window again and again,,,I can not use gnome destop to do any thing... P.S. The Gnome destop icon didn't apear... Any idea? S.O.S! By Fabonacci. From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 15:11:12 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A3DE1065679 for ; Tue, 20 May 2008 15:11:12 +0000 (UTC) (envelope-from v.werth@bally-wulff.de) Received: from mail2.bally-wulff-berlin.de (mail2.bally-wulff-berlin.de [212.144.118.9]) by mx1.freebsd.org (Postfix) with ESMTP id B44218FC24 for ; Tue, 20 May 2008 15:11:11 +0000 (UTC) (envelope-from v.werth@bally-wulff.de) Received: from ex1.bally-wulff.de (ex1.bally.de [192.9.204.18]) by mail2.bally-wulff-berlin.de (Postfix) with ESMTP id 33AD09907E; Tue, 20 May 2008 16:53:59 +0200 (CEST) Thread-Index: Aci6iVYdBGNptQDyRSa/dx62+xLU4w== Thread-Topic: Slowly Gnome on FreeBSD 7.0 Received: from pc88.bally.de ([192.9.205.88]) by ex1.bally-wulff.de with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 May 2008 16:53:59 +0200 From: "Werth, Volker" To: "John Timony" Date: Tue, 20 May 2008 16:53:59 +0200 User-Agent: KMail/1.9.4 References: <112879.11288.qm@web46306.mail.sp1.yahoo.com> In-Reply-To: <112879.11288.qm@web46306.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Importance: normal Priority: normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-ID: <200805201653.59940.v.werth@bally-wulff.de> X-OriginalArrivalTime: 20 May 2008 14:53:59.0765 (UTC) FILETIME=[56165850:01C8BA89] Cc: freebsd-hackers@freebsd.org Subject: Re: Slowly Gnome on FreeBSD 7.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 15:11:12 -0000 Volker Werth schrieb am 20.05.2008 16:53 _____________________________________________________________________ Am Dienstag, 20. Mai 2008 16:07 schrieb John Timony: > Hi,all > > I have tried to post this =3Dquestion to the=3D20right mail list,but = have no > responds,so i try to post here. > > In my Acer TravelMate 220,I =3Dinstall=3D20Freebsd7.0 by using Minimal = way,and > then install Xorg,ports,and Gnome2 =3Dby=3D20sysinstall.. > > I type these =3Dcommands: > > #Xorg -configure > #Xorg -config =3Dxorg.conf.new > #echo "exec=3D20gnome-session">~/.xinitrs > #startx > > After this,I can enter gnome=3D20destop,but it shows me a window with = a title > "root",,,and then it=3D20disapears,,,and then apears again,,,and = disapear > again time and=3D20time... > > The gnome destop is slow,and =3Drepeat the=3D20window again and = again,,,I can > not use gnome destop to do any=3D20thing... > > P.S. The Gnome destop icon =3Ddidn't=3D20apear... > > Any idea? > > S.O.S! > > By=3D20Fabonacci. > > Hi,all > > I have tried to post this question to the right mail list,but have no > responds,so i try to post here. > > In my Acer TravelMate 220,I install Freebsd7.0 by using Minimal = way,and > then install Xorg,ports,and Gnome2 by sysinstall.. > > I type these commands: > > #Xorg -configure > #Xorg -config xorg.conf.new > #echo "exec gnome-session">~/.xinitrs > #startx > > After this,I can enter gnome destop,but it shows me a window with a = title > "root",,,and then it disapears,,,and then apears again,,,and disapear = again > time and time... > > The gnome destop is slow,and repeat the window again and again,,,I can = not > use gnome destop to do any thing... > > P.S. The Gnome destop icon didn't apear... > > Any idea? John, what do you think about `/usr/local/etc/rc.d/gdm start`? AFAIR it's in the Gnome documentation. Volker PS: Please - no html mail :( --=20 Volker Werth ph: +49(30)62002-109 Bally Wulff Entertainment GmbH, Maybachufer 48-51, 12045 Berlin, = Postanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: = 030-620 02-200, Gesch=E4ftsf=FChrer: Axel Herr, Amtsgericht = Berlin-Charlottenburg, HRB 91532 B, UST-ID DE 234 517 998 _____________________________________________________________________ Dieses E-Mail ist nur f=FCr den Empf=E4nger bestimmt, an den es = gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs- =E4u=DFerung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von Bally Wulff Entertainment GmbH dar. Sind Sie nicht der Empf=E4nger, so haben Sie diese E-Mail irrt=FCmlich erhalten und jegliche Verwendung, Ver=F6ffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder Bally Wulff Entertainment GmbH noch der Absender (Volker Werth) =FCbernehmen die Haftung f=FCr Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren 0 Anh=E4nge auf Viren zu pr=FCfen. 0 Anh=E4nge: _____________________________________________________________________ Versand am 20.05.2008 16:53 von Werth Volker From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 17:06:40 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79EE31065678 for ; Tue, 20 May 2008 17:06:40 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 41BC88FC0A for ; Tue, 20 May 2008 17:06:40 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 8B1591CEA1; Tue, 20 May 2008 19:06:39 +0200 (CEST) Date: Tue, 20 May 2008 19:06:39 +0200 From: Ed Schouten To: FreeBSD Hackers Message-ID: <20080520170639.GE1181@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zWzrvxVmtOAUrjYA" Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) Subject: FreeBSD and LLVM 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, 20 May 2008 17:06:40 -0000 --zWzrvxVmtOAUrjYA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everyone, First of all, for those of you who went to BSDCan, I hope you had a pleasant flight/trip back home. :-) On Saturday I went to the LLVM talk (see http://llvm.org/), which I really enjoyed. On Friday Remko Lodder and I already talked with him about the LLVM project. I was excited about the project, so I decided to give it a try at the office. At first I tried LLVM 2.2 with LLVM GCC4 4.2 from Ports, but it didn't work like expected. I won't go into many details about it. When I discussed the problems I was seeing on my system at the office, someone pointed me to the beta tarballs of the upcoming version 2.3, which I installed by patching our FreeBSD port. http://llvm.org/prereleases/2.3/ As an ideal benchmark, I decided to compile an i386 kernel using the LLVM 2.3 snapshot. I didn't expect it to happen, but it works! I was capable of successfully booting into single user mode and shutting it down safely. There is one problem however: http://llvm.org/bugs/show_bug.cgi?id=3D2267 For some reason, the inline asm support of LLVM is incomplete and causes compilation errors when generating some of the atomic functions in i386/include/atomic.h (lines 262 to 265). To work around this, I made the functions non-atomic. Silly, I know, but it was good enough to perform some basic tests. I think it would be nice if LLVM would once become our standard C compiler. LLVM currently uses GCC as its frontend, which proves to be somewhat compatible with the original GCC> --=20 Ed Schouten WWW: http://80386.nl/ --zWzrvxVmtOAUrjYA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkgzBR8ACgkQ52SDGA2eCwVAwQCfcEUS51U8d3mSYcRpQ5oTA2M9 Wn4Ani/M25lIXlGzSB9fMrwt3y+3WWF+ =1nzw -----END PGP SIGNATURE----- --zWzrvxVmtOAUrjYA-- From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 18:31:18 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 787E9106566B for ; Tue, 20 May 2008 18:31:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 52A948FC12 for ; Tue, 20 May 2008 18:31:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (server.baldwin.cx [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id B1E591A4D7C; Tue, 20 May 2008 11:31:17 -0700 (PDT) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m4KIV7sg052536; Tue, 20 May 2008 14:31:09 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Andriy Gapon Date: Tue, 20 May 2008 11:24:23 -0400 User-Agent: KMail/1.9.7 References: <1210616585.00069210.1210605002@10.7.7.3> <1211246591.00072455.1211234402@10.7.7.3> <4832D432.2050907@icyb.net.ua> In-Reply-To: <4832D432.2050907@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805201124.23850.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 20 May 2008 14:31:09 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/7182/Tue May 20 12:09:32 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org, RW Subject: Re: i386 cpu_reset_real: code/comment mismatch 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, 20 May 2008 18:31:18 -0000 On Tuesday 20 May 2008 09:37:54 am Andriy Gapon wrote: > on 20/05/2008 00:51 John Baldwin said the following: > > So, the comment is correct and not the code. Curiously enough, OpenSolaris > > does the same thing (it writes 0x2 followed by 0x6), but it has some sort of > > comment which implies that you have to do a write to set or clear bit 1 > > before setting bit 2. Linux only uses 0xcf9 on a specific x86 machine (View > > workstation or some such) in which case it just does a single write of 0x6. > > I'll test locally to make sure 0x4 and 0x6 both work and if so I will commit > > the fix. > > And this code is most likely never reached in majority of the cases, > reset via keyboard controller should just work. Except on boxes where it doesn't (and hence why I added it). > BTW, I understand that there is a difference between hard and soft reset > in terms of hardware signals being asserted, but I don't quite > understand general consequences. I.e. what is a practical difference > between hard and soft reset? I've no idea. It may be that we should just always do a hard reset as that is in effect what both Solaris and Linux do. I'll probably just change it to do that. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 18:58:59 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C1F11065680; Tue, 20 May 2008 18:58:59 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id DCE6B8FC26; Tue, 20 May 2008 18:58:58 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JyX32-000HsT-9v; Tue, 20 May 2008 21:58:56 +0300 Message-ID: <48331F69.3070205@icyb.net.ua> Date: Tue, 20 May 2008 21:58:49 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: John Baldwin References: <1210616585.00069210.1210605002@10.7.7.3> <1211246591.00072455.1211234402@10.7.7.3> <4832D432.2050907@icyb.net.ua> <200805201124.23850.jhb@freebsd.org> In-Reply-To: <200805201124.23850.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, RW Subject: Re: i386 cpu_reset_real: code/comment mismatch 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, 20 May 2008 18:58:59 -0000 on 20/05/2008 18:24 John Baldwin said the following: > On Tuesday 20 May 2008 09:37:54 am Andriy Gapon wrote: >> BTW, I understand that there is a difference between hard and soft reset >> in terms of hardware signals being asserted, but I don't quite >> understand general consequences. I.e. what is a practical difference >> between hard and soft reset? > > I've no idea. It may be that we should just always do a hard reset as that is > in effect what both Solaris and Linux do. I'll probably just change it to do > that. But I think it is already how the code works (maybe with extra port write that couldn't hurt anything). -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 19:35:32 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26895106566B for ; Tue, 20 May 2008 19:35:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 100CC8FC25 for ; Tue, 20 May 2008 19:35:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (server.baldwin.cx [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id B36A01A4D7E; Tue, 20 May 2008 12:35:31 -0700 (PDT) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m4KJZLXp053053; Tue, 20 May 2008 15:35:23 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Andriy Gapon Date: Tue, 20 May 2008 15:34:41 -0400 User-Agent: KMail/1.9.7 References: <1210616585.00069210.1210605002@10.7.7.3> <200805201124.23850.jhb@freebsd.org> <48331F69.3070205@icyb.net.ua> In-Reply-To: <48331F69.3070205@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805201534.42201.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 20 May 2008 15:35:23 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/7182/Tue May 20 12:09:32 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org, RW Subject: Re: i386 cpu_reset_real: code/comment mismatch 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, 20 May 2008 19:35:32 -0000 On Tuesday 20 May 2008 02:58:49 pm Andriy Gapon wrote: > on 20/05/2008 18:24 John Baldwin said the following: > > On Tuesday 20 May 2008 09:37:54 am Andriy Gapon wrote: > >> BTW, I understand that there is a difference between hard and soft reset > >> in terms of hardware signals being asserted, but I don't quite > >> understand general consequences. I.e. what is a practical difference > >> between hard and soft reset? > > > > I've no idea. It may be that we should just always do a hard reset as that is > > in effect what both Solaris and Linux do. I'll probably just change it to do > > that. > > But I think it is already how the code works (maybe with extra port > write that couldn't hurt anything). Right, I'll probably just update the comment and remove the '0x2' write. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed May 21 08:39:37 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F2AE106567D for ; Wed, 21 May 2008 08:39:37 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 291A88FC14 for ; Wed, 21 May 2008 08:39:37 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 9D91B67FAAC; Wed, 21 May 2008 10:22:35 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdF1O4NHRvc0; Wed, 21 May 2008 10:22:33 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id DD9C967FA76; Wed, 21 May 2008 10:22:33 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.2/8.14.2/Submit) id m4L8MX5m071420; Wed, 21 May 2008 10:22:33 +0200 (CEST) (envelope-from rdivacky) Date: Wed, 21 May 2008 10:22:33 +0200 From: Roman Divacky To: Ed Schouten Message-ID: <20080521082233.GA71289@freebsd.org> References: <20080520170639.GE1181@hoeg.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080520170639.GE1181@hoeg.nl> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Hackers Subject: Re: FreeBSD and LLVM 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, 21 May 2008 08:39:37 -0000 On Tue, May 20, 2008 at 07:06:39PM +0200, Ed Schouten wrote: > Hello everyone, > > First of all, for those of you who went to BSDCan, I hope you had a > pleasant flight/trip back home. :-) > > On Saturday I went to the LLVM talk (see http://llvm.org/), which I > really enjoyed. On Friday Remko Lodder and I already talked with him > about the LLVM project. I was excited about the project, so I decided to > give it a try at the office. > > At first I tried LLVM 2.2 with LLVM GCC4 4.2 from Ports, but it didn't > work like expected. I won't go into many details about it. > > When I discussed the problems I was seeing on my system at the office, > someone pointed me to the beta tarballs of the upcoming version 2.3, > which I installed by patching our FreeBSD port. > > http://llvm.org/prereleases/2.3/ > > As an ideal benchmark, I decided to compile an i386 kernel using the > LLVM 2.3 snapshot. I didn't expect it to happen, but it works! I was did you try clang as well? I wonder what it's able to do.... > capable of successfully booting into single user mode and shutting it > down safely. There is one problem however: > > http://llvm.org/bugs/show_bug.cgi?id=2267 > > For some reason, the inline asm support of LLVM is incomplete and causes > compilation errors when generating some of the atomic functions in > i386/include/atomic.h (lines 262 to 265). To work around this, I made > the functions non-atomic. Silly, I know, but it was good enough to > perform some basic tests. > > I think it would be nice if LLVM would once become our standard C > compiler. LLVM currently uses GCC as its frontend, which proves to be > somewhat compatible with the original GCC> yeah... thats a worthy goal :) thnx! roman From owner-freebsd-hackers@FreeBSD.ORG Wed May 21 17:23:54 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 734F21065687; Wed, 21 May 2008 17:23:54 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 3300C8FC20; Wed, 21 May 2008 17:23:54 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 7C36B1CEA1; Wed, 21 May 2008 19:23:52 +0200 (CEST) Date: Wed, 21 May 2008 19:23:52 +0200 From: Ed Schouten To: Stefan Esser Message-ID: <20080521172352.GJ1181@hoeg.nl> References: <20080520170639.GE1181@hoeg.nl> <48330CDA.2080802@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fuRgIt480xB0EInP" Content-Disposition: inline In-Reply-To: <48330CDA.2080802@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: FreeBSD Hackers Subject: Re: FreeBSD and LLVM 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, 21 May 2008 17:23:54 -0000 --fuRgIt480xB0EInP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Stefan, (CC'ing this back to the list) * Stefan Esser wrote: > this is great news! Can you provide your patches to upgrade the port > to 2.3-pre? I could, but I patched the ports rather poorly. The plists are incorrect. I just incremented the version numbers, updated the distinfo and made some changes to the llvm-gcc4 port to use the proper wrksrc. > Did you, by chance, record build times with llvm-gcc compared to the > system compiler? > > What about the quality of generated code (size, runtime)? > Did you manage to get a meaning-ful program built that could be used > as a benchmark? I was able to compile a kernel with SMP disabled and PAE enabled. Other combinations will not work. LLVM doesn't seem to be properly capable of dealing with the xchg instruction in inline asm statements. A non-SMP PAE kernel doesn't seem to use them :-) Below are some build stats: | llvm: |=20 | 114.04s user 24.86s system 176% cpu 1:18.73 total ^ output of time(1) |=20 | -rwxr-xr-x 1 ed wheel 4456839 May 21 12:59 ^ output of ls -l kernel before stripping | -rwxr-xr-x 1 ed wheel 3596008 May 21 13:16 ^ output of ls -l kernel after stripping |=20 | text data bss dec hex | 3286323 229605 462280 3978208 3cb3e0 ^ output of size(1) after stripping | gcc: |=20 | 119.04s user 22.64s system 178% cpu 1:19.27 total |=20 | -rwxr-xr-x 1 ed wheel 4098317 May 21 12:33 | -rwxr-xr-x 1 ed wheel 3463448 May 21 12:57 |=20 | text data bss dec hex | 3185574 220965 460216 3866755 3b0083 As you can see, compilation time is about the same, but the kernel image is a little bigger. I don't know anything about the quality of the generated code. > If 2.3-pre allows the kernel to boot and run, then many user-land > programs should work as well. Testing a make world (and preparing > the infrastructure to support llvm in addition to gcc and icc might > be worthwhile ...). We should really try that. Unfortunately I'm quite busy, hacking on the TTY layer. ;-) > You probably know about the clang project, which tries to completely > replace the gcc parts needed for llvm-gcc ... Yes. I haven't looked at it yet. It doesn't seem to be in Ports yet. Any takers? ;-) --=20 Ed Schouten WWW: http://80386.nl/ --fuRgIt480xB0EInP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkg0WqgACgkQ52SDGA2eCwWTLACfSPDGFk6gBTDbOOPS7IZsf7fn 8wgAn0eIWl61Q2gs2A2c+eUhsEDIRJEp =kXmS -----END PGP SIGNATURE----- --fuRgIt480xB0EInP-- From owner-freebsd-hackers@FreeBSD.ORG Wed May 21 17:46:16 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84A2A1065685 for ; Wed, 21 May 2008 17:46:16 +0000 (UTC) (envelope-from richard@vanmansom.net) Received: from mta-fe.casema.nl (cas-mta4-fe.casema.nl [83.80.1.32]) by mx1.freebsd.org (Postfix) with ESMTP id 41AC38FC1C for ; Wed, 21 May 2008 17:46:16 +0000 (UTC) (envelope-from richard@vanmansom.net) Received: from localhost (cas-filter3.mgmt.casema.nl [10.42.32.98]) by mta-fe.casema.nl (Postfix) with ESMTP id 01F4D3FCC for ; Wed, 21 May 2008 19:19:03 +0200 (CEST) X-Virus-Scanned: amavisd-new at casema.nl Received: from mta-fe.casema.nl ([10.42.32.32]) by localhost (cas-filter3.mgmt.casema.nl [10.42.32.211]) (amavisd-new, port 20024) with ESMTP id wXEm3n0SkIad for ; Wed, 21 May 2008 19:19:02 +0200 (CEST) Received: from SATIS2301087C9 (535334A9.cable.casema.nl [83.83.52.169]) by mta-fe.casema.nl (Postfix) with ESMTP id C4B82401D for ; Wed, 21 May 2008 19:19:02 +0200 (CEST) From: "Richard van Mansom" To: Date: Wed, 21 May 2008 19:19:03 +0200 Message-ID: <001001c8bb66$c4713170$4d539450$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Aci7ZsQzwHWw5+rsTby9iNK91T8ICw== Content-Language: en-us Subject: Hifn 7955 doesn't work with Freebsd 7.0-release 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, 21 May 2008 17:46:16 -0000 Hi, I am trying to setup two Soekris 4521 with a minipci vpn1411 (Hi/fn 7955) in a vpn. I understood that the crypto card should automatically work with only three kernel configuration file modification. So I added these three lines device crypto device cryptodev device hifn I tested with openvpn (the one release with pkg_add). I used the default cipher (I think this is BF-CBC - Blowfish 128 bit). The VPN works but I didn't notice any difference in performance (with or without the crypto card). I also tested the crypto card with AES128 but the performance only got worse (didn't have a baseline for that one) Relevant output: dmesg | grep hifn hifn0 mem 0xa0000000-0xa0000fff,0xa0002000-0xa0003fff,0xa0008000-0xa000ffff irq 10 at device 16.0 on pci0 hifn0: [ITHREAD] hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801 dmesg | grep crypto cryptosoft0: on motherboard uname -a FreeBSD Soekris 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sat May 17 10:53:38 UTC 2008 root@One:/usr/obj/usr/src/sys/C5 i386 Any help would be appreciated Richard From owner-freebsd-hackers@FreeBSD.ORG Wed May 21 18:39:01 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53B621065675 for ; Wed, 21 May 2008 18:39:01 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id D3FB58FC12 for ; Wed, 21 May 2008 18:39:00 +0000 (UTC) (envelope-from mwm@mired.org) Received: (qmail 25794 invoked from network); 21 May 2008 14:39:19 -0400 Received: from unknown (HELO mbook.local) (192.168.195.193) by 0 with SMTP; 21 May 2008 14:39:19 -0400 Date: Wed, 21 May 2008 14:38:57 -0400 From: Mike Meyer To: Stefan Farfeleder Message-ID: <20080521143857.454dc869@mbook.local> In-Reply-To: <20080516141307.GB1032@lizard.fafoe.narf.at> References: <20080309152712.42752293@bhuda.mired.org> <20080516074433.GA1032@lizard.fafoe.narf.at> <20080516101143.3545937c@bhuda.mired.org> <20080516141307.GB1032@lizard.fafoe.narf.at> Organization: Meyer Consulting X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.2.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 21 May 2008 18:48:36 +0000 Cc: hackers@freebsd.org Subject: Re: Why doesn't autoconf like our /bin/sh? 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, 21 May 2008 18:39:01 -0000 On Fri, 16 May 2008 16:13:07 +0200 Stefan Farfeleder wrote: > On Fri, May 16, 2008 at 10:11:43AM -0400, Mike Meyer wrote: > > On Fri, 16 May 2008 09:44:33 +0200 > > Stefan Farfeleder wrote: > > > > > On Sun, Mar 09, 2008 at 03:27:12PM -0400, Mike Meyer wrote: > > > > I've stumbled on to an obscure problem with autoconf 2.61, and I'm not > > > > sure quite what to do with it. I've already sent mail to the autoconf > > > > folks, but I'd like to understand what's going on. > > > > > > > > The problem is that, on a FreeBSD system with only /bin/sh and the > > > > ports zsh as installed shells, if you have SHELL set to zsh when > > > > invoking the autoconf-generated configure script, the script produces > > > > a broken Makefile. It doesn't generate an error, it just complains > > > > that: > > > > > > Can you please retry? /bin/sh now supports expanding $LINENO which was > > > often the reason for configure not liking it. And autoconf seems happy to use it. Thanks, Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 624D7106568B for ; Wed, 21 May 2008 23:04:48 +0000 (UTC) (envelope-from det135@hoenikker.aset.psu.edu) Received: from f05n03.cac.psu.edu (f05s03.cac.psu.edu [128.118.141.46]) by mx1.freebsd.org (Postfix) with ESMTP id 2329F8FC12 for ; Wed, 21 May 2008 23:04:47 +0000 (UTC) (envelope-from det135@hoenikker.aset.psu.edu) Received: from hoenikker.aset.psu.edu (hoenikker.aset.psu.edu [128.118.99.49]) by f05n03.cac.psu.edu (8.13.2/8.13.2) with ESMTP id m4LIRmpL146926 for ; Wed, 21 May 2008 14:27:48 -0400 Received: from hoenikker.aset.psu.edu (hoenikker.aset.psu.edu [128.118.99.49]) by hoenikker.aset.psu.edu (8.14.2/8.14.2) with ESMTP id m4LIRMS6036067 for ; Wed, 21 May 2008 14:27:22 -0400 (EDT) (envelope-from det135@hoenikker.aset.psu.edu) Received: (from det135@localhost) by hoenikker.aset.psu.edu (8.14.2/8.14.2/Submit) id m4LIRMV7036066 for freebsd-hackers@freebsd.org; Wed, 21 May 2008 14:27:22 -0400 (EDT) (envelope-from det135) Date: Wed, 21 May 2008 14:27:22 -0400 From: Derek Taylor To: freebsd-hackers@freebsd.org Message-ID: <20080521182722.GC40818@psu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: by amavisd-new Subject: Kerberized CIFS client? 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, 21 May 2008 23:04:48 -0000 This question was previously posed of the freebsd-questions list, but with no response for a week, I'd like to try my luck here. If there's any more information I should include, please speak up: I would be glad to oblige. I would like to use smb/cifs with kerberos auth, but mount_smbfs doesn't seem to support this. Is anyone aware of an alternate means of performing a mount via smb/cifs or any patches to provide such functionality? I already have smbclient working with -k, but I am also interested in a mount. Thanks -Derek. From owner-freebsd-hackers@FreeBSD.ORG Wed May 21 23:58:04 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DF1D106564A for ; Wed, 21 May 2008 23:58:04 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0F4E58FC15 for ; Wed, 21 May 2008 23:58:03 +0000 (UTC) (envelope-from mike@sentex.net) Received: from Mobile2.sentex.ca (cage.simianscience.com [64.7.134.1]) by smarthost1.sentex.ca (8.14.2/8.14.2) with SMTP id m4LNkcUK069657; Wed, 21 May 2008 19:46:38 -0400 (EDT) (envelope-from mike@sentex.net) From: mike@sentex.net To: "Richard van Mansom" Date: Wed, 21 May 2008 19:47:11 -0400 Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> In-Reply-To: <001001c8bb66$c4713170$4d539450$@net> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Hifn 7955 doesn't work with Freebsd 7.0-release 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, 21 May 2008 23:58:04 -0000 > >I tested with openvpn (the one release with pkg_add). I used the default >cipher (I think this is BF-CBC - Blowfish 128 bit). The VPN works but I Hi, See the man page for supported ciphers. =20 >didn't notice any difference in performance (with or without the crypto >card).=20 >I also tested the crypto card with AES128 but the performance only got = worse >(didn't have a baseline for that one) =46or single crypto streams, you are not going to see any improvement really. Where it works, is when you have multiple connections. e.g. on our old backup server, we would have several dumps coming in over ssh (3des) and the card made a significant reduction in CPU usage. It doesnt really improve single crypto streams performance wise. You can also confirm its working by using hifnstats in /usr/src/tools/tools/ ---Mike From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 03:59:28 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FCF0106566C for ; Thu, 22 May 2008 03:59:28 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id C9AB48FC19 for ; Thu, 22 May 2008 03:59:27 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m4M3JQj8030132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 May 2008 20:19:26 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4834E63E.10307@freebsd.org> Date: Wed, 21 May 2008 20:19:26 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Richard van Mansom References: <001001c8bb66$c4713170$4d539450$@net> In-Reply-To: <001001c8bb66$c4713170$4d539450$@net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers@freebsd.org Subject: Re: Hifn 7955 doesn't work with Freebsd 7.0-release 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, 22 May 2008 03:59:28 -0000 Richard van Mansom wrote: > Hi, > > I am trying to setup two Soekris 4521 with a minipci vpn1411 (Hi/fn 7955) in > a vpn. > > I understood that the crypto card should automatically work with only three > kernel configuration file modification. > > So I added these three lines > > device crypto > device cryptodev > device hifn > > I tested with openvpn (the one release with pkg_add). I used the default > cipher (I think this is BF-CBC - Blowfish 128 bit). The VPN works but I > didn't notice any difference in performance (with or without the crypto > card). > I also tested the crypto card with AES128 but the performance only got worse > (didn't have a baseline for that one) > > Relevant output: > dmesg | grep hifn > hifn0 mem 0xa0000000-0xa0000fff,0xa0002000-0xa0003fff,0xa0008000-0xa000ffff > irq 10 at device 16.0 on pci0 > hifn0: [ITHREAD] > hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801 > > dmesg | grep crypto > cryptosoft0: on motherboard > > uname -a > FreeBSD Soekris 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sat May 17 10:53:38 UTC > 2008 root@One:/usr/obj/usr/src/sys/C5 i386 > > Any help would be appreciated > > Unfortunately openssl doesn't use the accelerator by default. This means all apps that use openssl likewise are not automatically accelerated. I suggested a patch but it was not accepted. I can't recall how you force openssl and/or consumers to use the device. If you want to check whether the kernel support is working correctly look in src/tools/tools/crypto for cryptotest and hifnstats. Sam From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 04:36:06 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F00531065677 for ; Thu, 22 May 2008 04:36:06 +0000 (UTC) (envelope-from fhcarron@terra.es) Received: from IMPaqm1.telefonica.net (impaqm1.telefonica.net [213.4.149.61]) by mx1.freebsd.org (Postfix) with ESMTP id 37FE68FC13 for ; Thu, 22 May 2008 04:36:05 +0000 (UTC) (envelope-from fhcarron@terra.es) Received: from IMPmailhost3.adm.correo ([10.20.102.124]) by IMPaqm1.telefonica.net with bizsmtp id UFt31Z0072h2L9m01HhNoT; Wed, 21 May 2008 19:41:22 +0200 Received: from [192.168.1.5] ([62.174.105.229]) by IMPmailhost3.adm.correo with BIZ IMP id UHP81Z00C4wz1CW1jHPBzl; Wed, 21 May 2008 19:23:17 +0200 From: Fernando Herrero =?ISO-8859-1?Q?Carr=F3n?= To: freebsd-hackers@freebsd.org In-Reply-To: <689122.62781.qm@web56102.mail.re3.yahoo.com> References: <689122.62781.qm@web56102.mail.re3.yahoo.com> Content-Type: text/plain; charset=utf-8 Date: Wed, 21 May 2008 19:25:20 +0200 Message-Id: <1211390720.1152.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Subject: Re: Gprof C++ support 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, 22 May 2008 04:36:07 -0000 El sáb, 03-05-2008 a las 09:17 -0700, Purushotham Nayak escribió: > Hi All, > I've been trying to use gprof on some C++ code and appears it doesn't > demangle C++ function names. I was wondering if anyone is working on > it? I would like to contribute/help in adding this. > Purushotham You can try c++filt. From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 04:45:52 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54FCC1065674 for ; Thu, 22 May 2008 04:45:52 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 03A578FC17 for ; Thu, 22 May 2008 04:45:51 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAOSQNEiC1Apk/2dsb2JhbACwCA Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 21 May 2008 21:17:17 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052121171545-933 ; Wed, 21 May 2008 21:17:15 -0700 Date: Wed, 21 May 2008 21:17:15 -0700 (PDT) From: KAYVEN RIESE cc: freebsd-hackers@freebsd.org In-Reply-To: Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/21/2008 21:17:15, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/21/2008 21:17:16, Serialize complete at 05/21/2008 21:17:16 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: nessus gtk yields empty scan 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, 22 May 2008 04:45:52 -0000 [kayve@kv_bsd ~]$ uname -a FreeBSD kv_bsd 6.3-STABLE FreeBSD 6.3-STABLE #0: Wed May 7 19:40:55 PDT 2008 root@kv_bsd:/usr/obj/usr/src/sys/GENERIC i386 [kayve@kv_bsd ~]$ pkg_info | grep essus pkg_info: show_file: can't open '+COMMENT' for reading nessus-gtk2-2.2.9_1 A security scanner: looks for vulnerabilities in a given ne nessus-libnasl-2.2.9_1 Nessus Attack Scripting Language nessus-libraries-2.2.9_1 Libraries for Nessus, the security scanner [kayve@kv_bsd ~]$ when i boot there seems like there are a lot of rpm errors during the nessus loads. i think something is wrong but i don't know what. i don't know what to say i don't know what is wrong i can type faster without caps it is NOT that hard to read. the gtk GUI has a lot of plugins i think they are all selected there is a host called minkay.sfsu.edu i am supposed to scan i have a log in i put in host 10.1.1.1 like this webpage says ttp://www.securityfocus.com/infocus/1741 oops. i pasted it twice below sorry. 1.0 Introduction Nessus is a great tool designed to automate the testing and discovery of known security problems. Typically someone, a hacker group, a security company, or a researcher discovers a specific way to violate the security of a software product. The discovery may be accidental or through directed research; the vulnerability, in various levels of detail, is then released to the security community. Nessus is designed to help identify and solve these known problems, before a hacker takes advantage of them. Nessus is a great tool with lots of capabilities. However it is fairly complex and few articles exist to direct the new user through the intricacies of how to install and use it. Thus, this article shall endeavor to cover the basics of Nessus setup and configuration. The features of the current versions of Nessus (Nessus 2.0.8a and NessusWX 1.4.4) will be discussed. Future articles will cover Nessus in more depth. Nessus is a free program released under the GPL. Historically, many in the corporate world have ridiculed such public domain software as being a waste of time, instead choosing "supported" products developed by established companies. Typically these packages cost hundreds or thousands of dollars, and are often purchased using the logic that you get what you pay for. Some people are starting to realize that public domain software, such as Nessus, isn't always inferior and sometimes it is actually superior. Paid technical support for Nessus is even available from www.tenablesecurity.com. Nessus also has a great community of developers anchored by the primary author, Renaud Deraison. When allowed to fairly compete in reviews against other vulnerability scanners, Nessus has equaled or outshined products costing thousands of dollars. [ref: Information Security, Network Computing] One of the very powerful features of Nessus is its client server technology. Servers can be placed at various strategic points on a network allowing tests to be conducted from various points of view. A central client or multiple distributed clients can control all the servers. The server portion will run on most any flavor of Unix. It even runs on MAC OS X and IBM/AIX, but Linux tends to make the installation simpler. These features provide a great deal of flexibility for the penetration tester. Clients are available for both Windows and Unix. The Nessus server performs the actual testing while the client provides configuration and reporting functionality. 2.0 Installation Nessus server installation is fairly simple even for a Windows jockey like me. First an installed version of Unix is required. Secondly, prior installation of several external programs is recommended: NMAP is the industry standard for port scanners, Hydra is a weak password tester and Nikto is a cgi/.script checker. While not required, these external programs greatly enhance Nessus' scanning ability. They are included because they are the best applications in their class. If installed in the PATH$ before Nessus installation, they will automatically be available. The simplest installation method is using the Lynx automatic install. Lynx is included on many of the linux versions. The Lynx command is (logged in as a user, and not root) : lynx -source http://install.nessus.org | sh This should install the server on most platforms with no other steps necessary. Note that the latest install script can also be downloaded and run locally. Whether you install directly off the Website or using the same install script offline, either way the script will setup a temporary suid and ask for your root password when required -- if you don't like this feature you can download, compile and install the four required tarballs individually. The above command should also be used periodically to upgrade Nessus as new versions are regularly released. You will be questioned about proxy servers, a download method (www or CVS), and the branch of the development tree to use; most of the time the defaults are the best choice. This is the simplest method of installation however; you are effectively giving the install.nessus.org server temporary root privileges. Thus there is a security risk with this method albeit a low one. So if you are paranoid, and paranoid is not always a bad thing in the security field, installation can be done the old-fashioned way by downloading and compiling the source. For information on performing an install from scratch see: www.nessus.org/nessus_2_0.html. 3.0 Setup Once the server is installed, some basic setup steps are required. The first task to complete in the new install is to add a user. A new user can be added by the "nessus-adduser" command. The script will question you for the authentication method. Authentication can be performed by several means, however a password is the simplest and is recommended. The next question queries about rules to restrict the user account. When used across an enterprise, a user can be restricted and only allowed to scan specified IP addresses. However, for most uses this will be left blank, allowing the user to scan anything. A certificate also needs to be generated as well to be used to encrypt the traffic between the client and server. The nessus-mkcert command accomplishes this. 3.1 Update plug-ins Before a scan is done, the plug-ins should be updated. Nessus plug-ins are very much like virus signatures in a common virus scanner application. Each plug-in is written to test for a specific vulnerability. These can be written to actually exploit the vulnerability or just test for known vulnerable software versions. Plug-ins can be written in most any language but usually are written in the Nessus Attack Scripting Language (NASL). NASL is Nessus' own language, specifically designed for vulnerability test writing. Each plug-in is written to test for a specific known vulnerability and/or industry best practices. NASL plug-ins typically test by sending very specific code to the target and comparing the results against stored vulnerable values. There are a few built-in plug-ins that do not use NASL. These are C and Perl scripts to perform special purposes that can not easily be done in NASL. Among these is the Services plug-in which identifies port-to-program mappings. Plug-in updates should be done frequently. New vulnerabilities are being discovered and disseminated all the time. Typically after a new vulnerability is released to the public, someone in the Nessus community writes a NASL plug-in, releases it to the public and submits it to www.nessus.org. It is then reviewed by the developers and added to the approved plug-in list. For high risk, high profile vulnerabilities a plug-in is often released the same day the vulnerability information is publicly released. Updating plug-ins from the maintained list is fairly simple involving a simple command: nessus-update-plugins. This command must be done as root. By no means however, are you limited to the list of plug-ins from www.nessus.org. New and special purpose plug-ins can be written relatively easily using NASL, so you can write your own custom plug-ins as well. 3.2 Launch the daemon Nessus is now installed, updated and ready to go. The simplest way to get the server running is (as root) issue the nessusd -D command. In order to use it, one must use a client. There are three primary Nessus clients. The native Unix GUI version is installed at server install time. Alternatively, Nessus can be controlled from the command line. A third option, a Windows version also exists called NessusWX. The binaries for NessusWX can be found here . The NessusWX install is a straightforward Windows install. All three clients work well. Personally I prefer NessusWX. It is better organized, allows for easier reporting, and has a better facility for managing different sessions (groups of hosts to scan) then its Unix counterparts. To run the native Unix GUI client, run the nessus command or for NessusWX click the eye icon after installation. 3.3 Client connection Since Nessus is a client server technology, once running the client a connection must be made to the server. In the native client, enter the server IP, username and password (created with the nessus-adduser command) and hit login. The process in NessusWX is similar but uses the communications | connect menus. The client is connected to the server thru an SSL connection and a list of the currently installed plug-ins is downloaded. On the first run the SSL certificate is also downloaded and verification is requested. This verification ensures that in the future you are actually communicating with the server intended. Figures 1 and 2 shows the connection using the Unix and Windows GUI tools, respectively. Figure 3 shows user authentication using the NessusWX client. Figure 1: Starting the Nessus server and connecting with the Unix GUI Figure 1: Starting the Nessus server and connecting with the Unix GUI Figure 2: Connecting to the Nessus server with NessusWX (Windows Client) Figure 2: Connecting to the Nessus server with NessusWX (Windows Client) Figure 3: Enter in the server IP and the login and password setup with nessus_adduser Figure 3: Enter in the server IP and the login and password setup with nessus_adduser 4.0 Using Nessus Now that we have installed and connected to Nessus lets explore some of the options available. The most obvious and powerful aspect of Nessus is its plug-in feature. The choice of plug-ins is critical to the success of a scan. Most plug-ins are written very well and rarely trigger false positives or negatives; however, a few are not. One example of a poorly written plug-in is the test for the classic Windows IIS hack RFP's MSDAC /RDS vulnerability. Rain Forest Puppy (RFP) publicized this vulnerability in 1999. The vulnerability makes use of the %system%/msadc/msadcs.dll file and leads to total system compromise on un-patched IIS 4.0 servers. The problem is that the Nessus plug-in only tests for the existence of the /msadc/msadcs.dll file. It does not take into account patches, windows versions etc. Thus with this plug-in enabled, a false positive will show up on many IIS servers and must be sorted out manually. Before anyone yells out, "see the problems of public domain software," one should note that the same types of problems exist with the high priced "supported" vulnerability scanners as well. This problem is a result of the current state of the technology. The difference is that typically in purchased products you cannot easily examine the exact "proprietary" testing methodology as can be done with Nessus, thus making resolution of the false positive difficult. 4.1 Choosing dangerous/non-dangerous plug-ins Plug-ins are categorized in several different and sometimes confusing ways. One method of plug-in grouping is by category. Most importantly, some plug-ins are categorized as Dangerous/Denial of Service (DOS). These plug-ins will actually perform a DOS attack and crash systems that have these particular problems. Needless to say these should not be blindly run on production systems. They won't cause long term damage, but at least a reboot will be required. In both clients, there are buttons to "Enable all plug-ins" or just "Enable all but dangerous plug-ins" (called "Enable Non-DOS" in NessusWX). Note that the author of the plug-in decides if it is dangerous or not. Most of the time, this has been very well chosen. However there are instances (Exmple: the rpc_endpoint mapper plug-in), where the plug-in causes a DOS but it is not listed as dangerous. The native client denotes dangerous plug-ins with a caution triangle. NessusWX has no special way to notate a dangerous plug-in other then using the enable "Enable Non-DOS" button. One other thing to be aware of is that sometimes even a "non-dangerous" plug-in can crash software. Since the plug-ins are sending non-standard data, there is always the risk, albeit rare, that a new undiscovered DOS will be stumbled upon. Therefore anytime systems are being scanned one should be aware that system crashes, although unlikely, are possible even with "non-dangerous" plug-ins. Figure 4, below, shows plug-in selection using the Unix GUI. Similarly, Figures 5 and 6 show plug-in selection using NessusWX for Windows: Figure 4: Enabling all but dangerous plugins with the Unix Nessus GUI Figure 4: Enabling all but dangerous plugins with the Unix Nessus GUI Figure 5: Selecting plug-ins with the Windows NessusWX Client Figure 5: Selecting plug-ins with the Windows NessusWX Client Figure 6: Enabling non-dangerous plug-ins with the Windows NessusWX Client Figure 6: Enabling non-dangerous plug-ins with the Windows NessusWX Client 4.2 Safe-checks This is a good place to mention the related concept of safe-checks. Safe-checks disables the dangerous parts of safe-check compatible plug-ins and causes them to check just through passive methods such as version numbers in banners. Since a patch or workaround may be installed, safe-checks are not as reliable as actually exploiting the vulnerability. They might cause false positives or false negatives. The valuable trade off is that they should not crash a machine. The safe-check option is on the scan options tab (the options tab in NessusWX). Figure 7 shows the safe-check option in the NessusWX interface: Figure 7: Choosing Safe Checks Figure 7: Choosing Safe Checks The second method of plug-in organization is in families such as Windows, FTP SNMP, SMB, Cisco, etc. I find this to be a rather unhelpful grouping due to the arbitrary categorizing process. Should an FTP vulnerability that only exists on a Windows box go in the Windows family or the FTP family? Since this decision is left up to the plug-in writer with little guidance, there are examples of both. The filtering/search mechanism is very helpful to isolate certain vulnerabilities. A filter can be initiated on name, plug-in number, etc. Clicking on the family and then the plug-in will give details of what the plug-in tests for. If intricate details are needed, the actual NASL code at cgi.nessus.org/plugins/ can be referenced. Note the DOS family is not the same as the dangerous/DOS category of plug-ins. A dangerous/DOS category plug-in actually exploits the vulnerability while a plug-in in the DOS family may just check for the vulnerability by checking software versions, for example. To perform a simple noisy scan on a non-production system, enabling all plug-ins is the best choice. If stealth or a production system is involved, choices can get complicated. We will talk in-depth about plug-ins selection in a future article. 4.3 Port scanning The other critical part of the scanning process is port scanning. Port scanning is the process by which the active ports for an IP address are identified. Each port is tied to a specific application. Nessus is a smart scanner and only runs a test if the specific program for that test is available. For example, only Web server plug-ins are run if a Web server is found. Since often ports are changed from their default to hide them, Nessus has a plug-in called services. The services plug-in attempts to identify the program running on each port. Once the program is identified, only the user-selected and pertinent plug-ins are run against it. Nessus has several options to scan for ports. There is the built-in wrapper for NMAP, widely acknowledged as the best port scanner around. There is also an internal scanner and a custom ping scan. As with plug-in selection, port scanning is very dependent on the situation. For a simple scan, the internal "sync" scan using default parameters with pings enabled, found on the "Perf" tab of the Unix GUI and the Port scan tab of NessusWX, is sufficient. Figures 8 and 9, below, show the internal SYN scan option using NessusWX and the Unix GUI client, respectively: Figure 8: Configuring the internal SYN scan for a simple port scan on NessusWX Figure 8: Configuring the internal SYN scan for a simple port scan on NessusWX Figure 9: Configuring the internal SYN scan for a simple port scan on the Unix Client Figure 9: Configuring the internal SYN scan for a simple port scan on the Unix Client 4.3 Identify targets The final task is to identify your targets. This is done on the targets tab. Targets can be specified as a single IP Address, as a subnet or as a range of IP addresses. I normally try to break them down into logical groups. It is typically easier to deal with smaller groups at one time. Figures 10 and 11 show how to select targets in both client environments: Figure 10: Specifying Targets in the Unix GUI Figure 10: Specifying Targets in the Unix GUI Figure 11: Target Selection in NessusWX Figure 11: Target Selection in NessusWX 4.4 Start a scan With your Nessus client and server in hand you are ready to scan systems. To start a scan in the Unix GUI just click "Start Scan" at the bottom of the window. In NessusWX, right click the desired session and select Execute. Properly used, Nessus can and will pinpoint problems and provide solutions. However, misused it can and will crash systems, cause the loss of data, and possibly cost you your job. As with anything powerful, there comes risk and responsibilities. Scanned systems sometimes will crash. Don't scan any system without permission. I suggest your first scan be against your own isolated test system. Future articles will lead you thorough a scan, sort out false positives and talk about stealth and firewall scanning. Figures 12, 13 and 14 show a scan using NessusWX. Figure 12: Starting a scan in NessusWX Figure 12: Starting a scan in NessusWX Figure 13: Starting a scan in NessusWX Figure 13: Starting a scan in NessusWX Figure 14: NessusWX scan in Progress Figure 14: NessusWX scan in Progress 5.0 Conclusion Nessus is an excellent tool that will greatly aid your ability to test and discover known security problems. As has been mentioned several times in this article, the power that Nessus gives you should be used wisely as it can render production systems unavailable with some of the more dangerous plus-ins. For more information on Nessus, visit the official Nessus site at www.nessus.org. Happy Scanning! 1.0 Introduction Nessus is a great tool designed to automate the testing and discovery of known security problems. Typically someone, a hacker group, a security company, or a researcher discovers a specific way to violate the security of a software product. The discovery may be accidental or through directed research; the vulnerability, in various levels of detail, is then released to the security community. Nessus is designed to help identify and solve these known problems, before a hacker takes advantage of them. Nessus is a great tool with lots of capabilities. However it is fairly complex and few articles exist to direct the new user through the intricacies of how to install and use it. Thus, this article shall endeavor to cover the basics of Nessus setup and configuration. The features of the current versions of Nessus (Nessus 2.0.8a and NessusWX 1.4.4) will be discussed. Future articles will cover Nessus in more depth. Nessus is a free program released under the GPL. Historically, many in the corporate world have ridiculed such public domain software as being a waste of time, instead choosing "supported" products developed by established companies. Typically these packages cost hundreds or thousands of dollars, and are often purchased using the logic that you get what you pay for. Some people are starting to realize that public domain software, such as Nessus, isn't always inferior and sometimes it is actually superior. Paid technical support for Nessus is even available from www.tenablesecurity.com. Nessus also has a great community of developers anchored by the primary author, Renaud Deraison. When allowed to fairly compete in reviews against other vulnerability scanners, Nessus has equaled or outshined products costing thousands of dollars. [ref: Information Security, Network Computing] One of the very powerful features of Nessus is its client server technology. Servers can be placed at various strategic points on a network allowing tests to be conducted from various points of view. A central client or multiple distributed clients can control all the servers. The server portion will run on most any flavor of Unix. It even runs on MAC OS X and IBM/AIX, but Linux tends to make the installation simpler. These features provide a great deal of flexibility for the penetration tester. Clients are available for both Windows and Unix. The Nessus server performs the actual testing while the client provides configuration and reporting functionality. 2.0 Installation Nessus server installation is fairly simple even for a Windows jockey like me. First an installed version of Unix is required. Secondly, prior installation of several external programs is recommended: NMAP is the industry standard for port scanners, Hydra is a weak password tester and Nikto is a cgi/.script checker. While not required, these external programs greatly enhance Nessus' scanning ability. They are included because they are the best applications in their class. If installed in the PATH$ before Nessus installation, they will automatically be available. The simplest installation method is using the Lynx automatic install. Lynx is included on many of the linux versions. The Lynx command is (logged in as a user, and not root) : lynx -source http://install.nessus.org | sh This should install the server on most platforms with no other steps necessary. Note that the latest install script can also be downloaded and run locally. Whether you install directly off the Website or using the same install script offline, either way the script will setup a temporary suid and ask for your root password when required -- if you don't like this feature you can download, compile and install the four required tarballs individually. The above command should also be used periodically to upgrade Nessus as new versions are regularly released. You will be questioned about proxy servers, a download method (www or CVS), and the branch of the development tree to use; most of the time the defaults are the best choice. This is the simplest method of installation however; you are effectively giving the install.nessus.org server temporary root privileges. Thus there is a security risk with this method albeit a low one. So if you are paranoid, and paranoid is not always a bad thing in the security field, installation can be done the old-fashioned way by downloading and compiling the source. For information on performing an install from scratch see: www.nessus.org/nessus_2_0.html. 3.0 Setup Once the server is installed, some basic setup steps are required. The first task to complete in the new install is to add a user. A new user can be added by the "nessus-adduser" command. The script will question you for the authentication method. Authentication can be performed by several means, however a password is the simplest and is recommended. The next question queries about rules to restrict the user account. When used across an enterprise, a user can be restricted and only allowed to scan specified IP addresses. However, for most uses this will be left blank, allowing the user to scan anything. A certificate also needs to be generated as well to be used to encrypt the traffic between the client and server. The nessus-mkcert command accomplishes this. 3.1 Update plug-ins Before a scan is done, the plug-ins should be updated. Nessus plug-ins are very much like virus signatures in a common virus scanner application. Each plug-in is written to test for a specific vulnerability. These can be written to actually exploit the vulnerability or just test for known vulnerable software versions. Plug-ins can be written in most any language but usually are written in the Nessus Attack Scripting Language (NASL). NASL is Nessus' own language, specifically designed for vulnerability test writing. Each plug-in is written to test for a specific known vulnerability and/or industry best practices. NASL plug-ins typically test by sending very specific code to the target and comparing the results against stored vulnerable values. There are a few built-in plug-ins that do not use NASL. These are C and Perl scripts to perform special purposes that can not easily be done in NASL. Among these is the Services plug-in which identifies port-to-program mappings. Plug-in updates should be done frequently. New vulnerabilities are being discovered and disseminated all the time. Typically after a new vulnerability is released to the public, someone in the Nessus community writes a NASL plug-in, releases it to the public and submits it to www.nessus.org. It is then reviewed by the developers and added to the approved plug-in list. For high risk, high profile vulnerabilities a plug-in is often released the same day the vulnerability information is publicly released. Updating plug-ins from the maintained list is fairly simple involving a simple command: nessus-update-plugins. This command must be done as root. By no means however, are you limited to the list of plug-ins from www.nessus.org. New and special purpose plug-ins can be written relatively easily using NASL, so you can write your own custom plug-ins as well. 3.2 Launch the daemon Nessus is now installed, updated and ready to go. The simplest way to get the server running is (as root) issue the nessusd -D command. In order to use it, one must use a client. There are three primary Nessus clients. The native Unix GUI version is installed at server install time. Alternatively, Nessus can be controlled from the command line. A third option, a Windows version also exists called NessusWX. The binaries for NessusWX can be found here . The NessusWX install is a straightforward Windows install. All three clients work well. Personally I prefer NessusWX. It is better organized, allows for easier reporting, and has a better facility for managing different sessions (groups of hosts to scan) then its Unix counterparts. To run the native Unix GUI client, run the nessus command or for NessusWX click the eye icon after installation. 3.3 Client connection Since Nessus is a client server technology, once running the client a connection must be made to the server. In the native client, enter the server IP, username and password (created with the nessus-adduser command) and hit login. The process in NessusWX is similar but uses the communications | connect menus. The client is connected to the server thru an SSL connection and a list of the currently installed plug-ins is downloaded. On the first run the SSL certificate is also downloaded and verification is requested. This verification ensures that in the future you are actually communicating with the server intended. Figures 1 and 2 shows the connection using the Unix and Windows GUI tools, respectively. Figure 3 shows user authentication using the NessusWX client. Figure 1: Starting the Nessus server and connecting with the Unix GUI Figure 1: Starting the Nessus server and connecting with the Unix GUI Figure 2: Connecting to the Nessus server with NessusWX (Windows Client) Figure 2: Connecting to the Nessus server with NessusWX (Windows Client) Figure 3: Enter in the server IP and the login and password setup with nessus_adduser Figure 3: Enter in the server IP and the login and password setup with nessus_adduser 4.0 Using Nessus Now that we have installed and connected to Nessus lets explore some of the options available. The most obvious and powerful aspect of Nessus is its plug-in feature. The choice of plug-ins is critical to the success of a scan. Most plug-ins are written very well and rarely trigger false positives or negatives; however, a few are not. One example of a poorly written plug-in is the test for the classic Windows IIS hack RFP's MSDAC /RDS vulnerability. Rain Forest Puppy (RFP) publicized this vulnerability in 1999. The vulnerability makes use of the %system%/msadc/msadcs.dll file and leads to total system compromise on un-patched IIS 4.0 servers. The problem is that the Nessus plug-in only tests for the existence of the /msadc/msadcs.dll file. It does not take into account patches, windows versions etc. Thus with this plug-in enabled, a false positive will show up on many IIS servers and must be sorted out manually. Before anyone yells out, "see the problems of public domain software," one should note that the same types of problems exist with the high priced "supported" vulnerability scanners as well. This problem is a result of the current state of the technology. The difference is that typically in purchased products you cannot easily examine the exact "proprietary" testing methodology as can be done with Nessus, thus making resolution of the false positive difficult. 4.1 Choosing dangerous/non-dangerous plug-ins Plug-ins are categorized in several different and sometimes confusing ways. One method of plug-in grouping is by category. Most importantly, some plug-ins are categorized as Dangerous/Denial of Service (DOS). These plug-ins will actually perform a DOS attack and crash systems that have these particular problems. Needless to say these should not be blindly run on production systems. They won't cause long term damage, but at least a reboot will be required. In both clients, there are buttons to "Enable all plug-ins" or just "Enable all but dangerous plug-ins" (called "Enable Non-DOS" in NessusWX). Note that the author of the plug-in decides if it is dangerous or not. Most of the time, this has been very well chosen. However there are instances (Exmple: the rpc_endpoint mapper plug-in), where the plug-in causes a DOS but it is not listed as dangerous. The native client denotes dangerous plug-ins with a caution triangle. NessusWX has no special way to notate a dangerous plug-in other then using the enable "Enable Non-DOS" button. One other thing to be aware of is that sometimes even a "non-dangerous" plug-in can crash software. Since the plug-ins are sending non-standard data, there is always the risk, albeit rare, that a new undiscovered DOS will be stumbled upon. Therefore anytime systems are being scanned one should be aware that system crashes, although unlikely, are possible even with "non-dangerous" plug-ins. Figure 4, below, shows plug-in selection using the Unix GUI. Similarly, Figures 5 and 6 show plug-in selection using NessusWX for Windows: Figure 4: Enabling all but dangerous plugins with the Unix Nessus GUI Figure 4: Enabling all but dangerous plugins with the Unix Nessus GUI Figure 5: Selecting plug-ins with the Windows NessusWX Client Figure 5: Selecting plug-ins with the Windows NessusWX Client Figure 6: Enabling non-dangerous plug-ins with the Windows NessusWX Client Figure 6: Enabling non-dangerous plug-ins with the Windows NessusWX Client 4.2 Safe-checks This is a good place to mention the related concept of safe-checks. Safe-checks disables the dangerous parts of safe-check compatible plug-ins and causes them to check just through passive methods such as version numbers in banners. Since a patch or workaround may be installed, safe-checks are not as reliable as actually exploiting the vulnerability. They might cause false positives or false negatives. The valuable trade off is that they should not crash a machine. The safe-check option is on the scan options tab (the options tab in NessusWX). Figure 7 shows the safe-check option in the NessusWX interface: Figure 7: Choosing Safe Checks Figure 7: Choosing Safe Checks The second method of plug-in organization is in families such as Windows, FTP SNMP, SMB, Cisco, etc. I find this to be a rather unhelpful grouping due to the arbitrary categorizing process. Should an FTP vulnerability that only exists on a Windows box go in the Windows family or the FTP family? Since this decision is left up to the plug-in writer with little guidance, there are examples of both. The filtering/search mechanism is very helpful to isolate certain vulnerabilities. A filter can be initiated on name, plug-in number, etc. Clicking on the family and then the plug-in will give details of what the plug-in tests for. If intricate details are needed, the actual NASL code at cgi.nessus.org/plugins/ can be referenced. Note the DOS family is not the same as the dangerous/DOS category of plug-ins. A dangerous/DOS category plug-in actually exploits the vulnerability while a plug-in in the DOS family may just check for the vulnerability by checking software versions, for example. To perform a simple noisy scan on a non-production system, enabling all plug-ins is the best choice. If stealth or a production system is involved, choices can get complicated. We will talk in-depth about plug-ins selection in a future article. 4.3 Port scanning The other critical part of the scanning process is port scanning. Port scanning is the process by which the active ports for an IP address are identified. Each port is tied to a specific application. Nessus is a smart scanner and only runs a test if the specific program for that test is available. For example, only Web server plug-ins are run if a Web server is found. Since often ports are changed from their default to hide them, Nessus has a plug-in called services. The services plug-in attempts to identify the program running on each port. Once the program is identified, only the user-selected and pertinent plug-ins are run against it. Nessus has several options to scan for ports. There is the built-in wrapper for NMAP, widely acknowledged as the best port scanner around. There is also an internal scanner and a custom ping scan. As with plug-in selection, port scanning is very dependent on the situation. For a simple scan, the internal "sync" scan using default parameters with pings enabled, found on the "Perf" tab of the Unix GUI and the Port scan tab of NessusWX, is sufficient. Figures 8 and 9, below, show the internal SYN scan option using NessusWX and the Unix GUI client, respectively: Figure 8: Configuring the internal SYN scan for a simple port scan on NessusWX Figure 8: Configuring the internal SYN scan for a simple port scan on NessusWX Figure 9: Configuring the internal SYN scan for a simple port scan on the Unix Client Figure 9: Configuring the internal SYN scan for a simple port scan on the Unix Client 4.3 Identify targets The final task is to identify your targets. This is done on the targets tab. Targets can be specified as a single IP Address, as a subnet or as a range of IP addresses. I normally try to break them down into logical groups. It is typically easier to deal with smaller groups at one time. Figures 10 and 11 show how to select targets in both client environments: Figure 10: Specifying Targets in the Unix GUI Figure 10: Specifying Targets in the Unix GUI Figure 11: Target Selection in NessusWX Figure 11: Target Selection in NessusWX 4.4 Start a scan With your Nessus client and server in hand you are ready to scan systems. To start a scan in the Unix GUI just click "Start Scan" at the bottom of the window. In NessusWX, right click the desired session and select Execute. Properly used, Nessus can and will pinpoint problems and provide solutions. However, misused it can and will crash systems, cause the loss of data, and possibly cost you your job. As with anything powerful, there comes risk and responsibilities. Scanned systems sometimes will crash. Don't scan any system without permission. I suggest your first scan be against your own isolated test system. Future articles will lead you thorough a scan, sort out false positives and talk about stealth and firewall scanning. Figures 12, 13 and 14 show a scan using NessusWX. Figure 12: Starting a scan in NessusWX Figure 12: Starting a scan in NessusWX Figure 13: Starting a scan in NessusWX Figure 13: Starting a scan in NessusWX Figure 14: NessusWX scan in Progress Figure 14: NessusWX scan in Progress 5.0 Conclusion Nessus is an excellent tool that will greatly aid your ability to test and discover known security problems. As has been mentioned several times in this article, the power that Nessus gives you should be used wisely as it can render production systems unavailable with some of the more dangerous plus-ins. For more information on Nessus, visit the official Nessus site at www.nessus.org. Happy Scanning! *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 05:13:46 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3802B1065677 for ; Thu, 22 May 2008 05:13:46 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id 23CEE8FC15 for ; Thu, 22 May 2008 05:13:45 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEALudNEiC1Apk/2dsb2JhbACveg Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 21 May 2008 22:13:45 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052122134313-935 ; Wed, 21 May 2008 22:13:43 -0700 Date: Wed, 21 May 2008 22:13:43 -0700 (PDT) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org In-Reply-To: Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/21/2008 22:13:43, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/21/2008 22:13:45, Serialize complete at 05/21/2008 22:13:45 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: libz.so no found 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, 22 May 2008 05:13:46 -0000 kv_bsd#cd /usr/ports/distfiles kv_bsd#mv /usr/home/kayve/Nessus-3.2.0-fbsd7.tbz . kv_bsd#pkg_add Nessus-3.2.0-fbsd7.tbz pkg_add: package VisualOS-1.0.5_3 has no origin recorded /libexec/ld-elf.so.1: Shared object "libz.so.4" not found, required by "nessusd" - Please run /usr/local/nessus/sbin/nessus-adduser to add an admin user - Register your Nessus scanner at http://www.nessus.org/register/ to obtain all the newest plugins - You can start nessusd by typing /usr/local/etc/rc.d/nessusd.sh start kv_bsd#/usr/local/etc/rc.d/nessusd.sh start Nessus/libexec/ld-elf.so.1: Shared object "libz.so.4" not found, required by "nessusd" kv_bsd# *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 05:36:42 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F8AB1065672 for ; Thu, 22 May 2008 05:36:42 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id 3A32D8FC24 for ; Thu, 22 May 2008 05:36:42 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEALiiNEiC1Apk/2dsb2JhbACvdQ Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 21 May 2008 22:36:42 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052122364013-936 ; Wed, 21 May 2008 22:36:40 -0700 Date: Wed, 21 May 2008 22:36:40 -0700 (PDT) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org In-Reply-To: Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/21/2008 22:36:40, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/21/2008 22:36:41, Serialize complete at 05/21/2008 22:36:41 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: nessus@list.nessus.org Subject: Many Nessus startup errors 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, 22 May 2008 05:36:42 -0000 I am not generating reports http://www.monkeyview.net/id/965/fsck/nessus/nessus.vhtml During startup, 20K plugins try to load. A lot of them fail or something: http://www.monkeyview.net/id/965/fsck/nessus/p5210017.vhtml http://www.monkeyview.net/id/965/fsck/nessus/p5210018.vhtml *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 06:23:37 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F9F8106566C for ; Thu, 22 May 2008 06:23:37 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1185E8FC13 for ; Thu, 22 May 2008 06:23:36 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C6C721CC033; Wed, 21 May 2008 23:23:36 -0700 (PDT) Date: Wed, 21 May 2008 23:23:36 -0700 From: Jeremy Chadwick To: KAYVEN RIESE Message-ID: <20080522062336.GA30379@eos.sc1.parodius.com> References: <001001c8bb66$c4713170$4d539450$@net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: libz.so no found 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, 22 May 2008 06:23:37 -0000 On Wed, May 21, 2008 at 10:13:43PM -0700, KAYVEN RIESE wrote: > kv_bsd#cd /usr/ports/distfiles > kv_bsd#mv /usr/home/kayve/Nessus-3.2.0-fbsd7.tbz . > kv_bsd#pkg_add Nessus-3.2.0-fbsd7.tbz > pkg_add: package VisualOS-1.0.5_3 has no origin recorded > /libexec/ld-elf.so.1: Shared object "libz.so.4" not found, required by > "nessusd" First and foremost, you hijacked an existing thread by replying to it with regards to a completely different issue. Please don't do this, it confuses mail clients which follow thread references. Please don't hit reply on unrelated messages and start a new/unrelated discussion. Secondly, the missing library error shown above would happen on machines running FreeBSD 6.x or earlier. /lib/libz.so.4 exists on RELENG_7. Another possibility is that something completely destroyed ld.so's shared library cache path. Of course, you'd be seeing all sorts of programs reporting missing libraries, and not just nexxus. If the startup script for nessus calls ldconfig or uses $LD_LIBRARY_PATH, that could explain the missing library. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 06:41:23 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E439106567E for ; Thu, 22 May 2008 06:41:23 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 992F48FC1E for ; Thu, 22 May 2008 06:41:22 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (DSTO/DSTO) with ESMTP id m4M5PfL0014543 for ; Thu, 22 May 2008 14:55:41 +0930 (CST) Received: from fmbex510.dsto.defence.gov.au (fmbex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Thu, 22 May 2008 14:48:36 +0930 Received: from stlex510.dsto.defence.gov.au ([203.6.60.184]) by fmbex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 15:18:35 +1000 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by stlex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 13:18:35 +0800 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.14.2/8.14.2) with ESMTP id m4M5DKq7098427 for ; Thu, 22 May 2008 13:13:20 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.14.2/8.14.2/Submit) id m4M5DKLk098426 for freebsd-hackers@freebsd.org; Thu, 22 May 2008 13:13:20 +0800 (WST) (envelope-from wilkinsa) Date: Thu, 22 May 2008 13:13:20 +0800 From: "Wilkinson, Alex" To: freebsd-hackers@freebsd.org Message-ID: <20080522051320.GE97948@stlux503.dsto.defence.gov.au> Mail-Followup-To: freebsd-hackers@freebsd.org References: <001001c8bb66$c4713170$4d539450$@net> <4834E63E.10307@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <4834E63E.10307@freebsd.org> Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.17 (2007-11-01) X-OriginalArrivalTime: 22 May 2008 05:18:35.0218 (UTC) FILETIME=[48AE0B20:01C8BBCB] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-5.5.1026-15924.003 X-TM-AS-Result: No--8.995000-0.000000-31 Content-Transfer-Encoding: 7bit Subject: Re: Hifn 7955 doesn't work with Freebsd 7.0-release 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, 22 May 2008 06:41:23 -0000 0n Wed, May 21, 2008 at 08:19:26PM -0700, Sam Leffler wrote: >Unfortunately openssl doesn't use the accelerator by default. This means >all apps that use openssl likewise are not automatically accelerated. I >suggested a patch but it was not accepted. I can't recall how you force >openssl and/or consumers to use the device. How annoying is that. Why wasn't the patch accepted ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 07:29:24 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A095106567E for ; Thu, 22 May 2008 07:29:24 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 536208FC26 for ; Thu, 22 May 2008 07:29:22 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (DSTO/DSTO) with ESMTP id m4M6j3KY022086 for ; Thu, 22 May 2008 16:15:03 +0930 (CST) Received: from fmbex510.dsto.defence.gov.au (fmbex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Thu, 22 May 2008 16:18:37 +0930 Received: from stlex510.dsto.defence.gov.au ([203.6.60.184]) by fmbex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 16:48:36 +1000 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by stlex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 14:48:34 +0800 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.14.2/8.14.2) with ESMTP id m4M6hJxa098959 for ; Thu, 22 May 2008 14:43:19 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.14.2/8.14.2/Submit) id m4M6hJj0098958 for hackers@freebsd.org; Thu, 22 May 2008 14:43:19 +0800 (WST) (envelope-from wilkinsa) Date: Thu, 22 May 2008 14:43:19 +0800 From: "Wilkinson, Alex" To: hackers@freebsd.org Message-ID: <20080522064319.GB98797@stlux503.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.17 (2007-11-01) X-OriginalArrivalTime: 22 May 2008 06:48:34.0311 (UTC) FILETIME=[DACA4170:01C8BBD7] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-5.5.1026-15924.003 X-TM-AS-Result: No--0.073000-0.000000-31 Content-Transfer-Encoding: 7bit Cc: Subject: A Tale of Four Kernels... 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, 22 May 2008 07:29:24 -0000 Some may be interested in this. http://www.spinellis.gr/pubs/conf/2008-ICSE-4kernel/html/Spi08b.pdf -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 10:00:04 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADF4B1065670 for ; Thu, 22 May 2008 10:00:04 +0000 (UTC) (envelope-from frase@frase.id.au) Received: from mail6.tpgi.com.au (smtp-out6.tpgi.com.au [220.244.226.116]) by mx1.freebsd.org (Postfix) with ESMTP id 2685F8FC18 for ; Thu, 22 May 2008 10:00:03 +0000 (UTC) (envelope-from frase@frase.id.au) X-TPG-Antivirus: Passed Received: from [192.168.36.100] (203-219-142-174.static.tpgi.com.au [203.219.142.174]) by mail6.tpgi.com.au (envelope-from frase@frase.id.au) (8.14.2/8.14.2) with ESMTP id m4M9mUs9026597; Thu, 22 May 2008 19:48:35 +1000 Message-ID: <48354169.9040905@frase.id.au> Date: Thu, 22 May 2008 19:48:25 +1000 From: Fraser Tweedale User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: "Wilkinson, Alex" References: <20080522064319.GB98797@stlux503.dsto.defence.gov.au> In-Reply-To: <20080522064319.GB98797@stlux503.dsto.defence.gov.au> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig373D18F9B5B0A09E5C1A8EC1" Cc: hackers@freebsd.org Subject: Re: A Tale of Four Kernels... 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, 22 May 2008 10:00:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig373D18F9B5B0A09E5C1A8EC1 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Wilkinson, Alex wrote: > Some may be interested in this. > http://www.spinellis.gr/pubs/conf/2008-ICSE-4kernel/html/Spi08b.pdf >=20 > -aW Interesting study; thanks for posting. frase --------------enig373D18F9B5B0A09E5C1A8EC1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkg1QW4ACgkQPw/2FZbemTWDwQCglyY1stxKxw8h4Cu88tkKzkVs /xcAn0fxtQ7l4R50bElc2oIF684pyi0Y =L7Ug -----END PGP SIGNATURE----- --------------enig373D18F9B5B0A09E5C1A8EC1-- From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 11:25:11 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E56C0106567C for ; Thu, 22 May 2008 11:25:11 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.freebsd.org (Postfix) with ESMTP id 7B5CD8FC26 for ; Thu, 22 May 2008 11:25:11 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from [129.247.12.9] ([129.247.12.9]) by smtp-3.dlr.de with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 13:11:53 +0200 Message-ID: <483554FC.9040908@dlr.de> Date: Thu, 22 May 2008 13:11:56 +0200 From: Hartmut Brandt Organization: German Aerospace Center User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Derek Taylor References: <20080521182722.GC40818@psu.edu> In-Reply-To: <20080521182722.GC40818@psu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 May 2008 11:11:54.0112 (UTC) FILETIME=[A4349000:01C8BBFC] Cc: freebsd-hackers@freebsd.org Subject: Re: Kerberized CIFS client? 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, 22 May 2008 11:25:12 -0000 Derek Taylor wrote: > This question was previously posed of the freebsd-questions list, but > with no response for a week, I'd like to try my luck here. If there's > any more information I should include, please speak up: I would be glad > to oblige. > > I would like to use smb/cifs with kerberos auth, but mount_smbfs doesn't > seem to support this. > > Is anyone aware of an alternate means of performing a mount via smb/cifs > or any patches to provide such functionality? > > I already have smbclient working with -k, but I am also interested in a > mount. Try smbnetfs from ports. It's fuse based and seems to work very nice. If you have a large amount of shares floating in your network you want to restrict it to mount only the needed shares via the config file. Otherwise it will mount what it can find... It plays nicely with kerberors. When your ticket expires you immediately loose access; when you renew it you gain access again. All without the need to unmount/mount. Just call smbnetfs once you have your ticket. You may even do this from your .profile. harti From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 13:27:27 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60B18106564A for ; Thu, 22 May 2008 13:27:27 +0000 (UTC) (envelope-from adrian@thearle.com.au) Received: from albert.thearle.com.au (albert.thearle.com.au [150.101.115.54]) by mx1.freebsd.org (Postfix) with SMTP id 936EE8FC13 for ; Thu, 22 May 2008 13:27:26 +0000 (UTC) (envelope-from adrian@thearle.com.au) Received: (qmail 96090 invoked by uid 0); 22 May 2008 13:00:44 -0000 Received: from 192.168.123.139 (adrian@thearle.com.au@192.168.123.139) by albert.thearle.com.au (envelope-from , uid 1009) with qmail-scanner-2.01 (clamdscan: 0.88.2/1512. spamassassin: 3.1.1. Clear:RC:1(192.168.123.139):. Processed in 0.157855 secs); 22 May 2008 13:00:44 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=kambah; d=thearle.com.au; b=ogoJOKuEjdBF/1IghrMA2oaMo87QqyD+mSEXi4OQdmRayYn74WXu2rGSVdrARjoj ; Received: from unknown (HELO ?192.168.123.139?) (adrian@thearle.com.au@192.168.123.139) by albert.thearle.com.au with SMTP; 22 May 2008 13:00:43 -0000 Message-ID: <48356E75.1050105@thearle.com.au> Date: Thu, 22 May 2008 23:00:37 +1000 From: Adrian Thearle User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Maximum memory allocation per process 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, 22 May 2008 13:27:27 -0000 Hi Guys I have a problem with a perl script running out of memory. From my googling I have found that perl itself does not seem to impose any memory limits, and I have check ulimit and login.conf for any userclass limitations but found nothing that seems to be limiting my memory. I have 128MBytes of RAM and a 2Gbyte swap partition. I am currently running FreeBSD albert 6.2-STABLE FreeBSD 6.2-STABLE #11: Sun Sep 2 00:45:05 EST 2007 which I guess isn't exactly the latest... but the same thing happens on my REL7.0 Box The process (imapsync in this case) runs out of ram at pretty much 512MB. I read on a forum that BSD 6 imposes such a limit of 512MB per process, but i have found no where to tune this, or even see what it is. I have also read that there are two sysctl namely, kern.maxdsiz and kern.maxssiz, that can tune memory allocation but what happend to them in Freebsd 6. Your help is appreciated Adrian From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 13:38:19 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F7B11065671 for ; Thu, 22 May 2008 13:38:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 68D738FC17 for ; Thu, 22 May 2008 13:38:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 547F31CC033; Thu, 22 May 2008 06:38:19 -0700 (PDT) Date: Thu, 22 May 2008 06:38:19 -0700 From: Jeremy Chadwick To: Adrian Thearle Message-ID: <20080522133819.GA45578@eos.sc1.parodius.com> References: <48356E75.1050105@thearle.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48356E75.1050105@thearle.com.au> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: Maximum memory allocation per process 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, 22 May 2008 13:38:19 -0000 On Thu, May 22, 2008 at 11:00:37PM +1000, Adrian Thearle wrote: > I have a problem with a perl script running out of memory. From my googling > I have found that perl itself does not seem to impose any memory limits, > and I have check ulimit and login.conf for any userclass limitations but > found nothing that seems to be limiting my memory. > > I have 128MBytes of RAM and a 2Gbyte swap partition. > > I am currently running > FreeBSD albert 6.2-STABLE FreeBSD 6.2-STABLE #11: Sun Sep 2 00:45:05 EST > 2007 > which I guess isn't exactly the latest... but the same thing happens on my > REL7.0 Box > > The process (imapsync in this case) runs out of ram at pretty much 512MB. I > read on a forum that BSD 6 imposes such a limit of 512MB per process, but i > have found no where to tune this, or even see what it is. You need to modify some kernel settings via /boot/loader.conf and reboot. Here's what we use on our production RELENG_6 and RELENG_7 boxes: # Increase maximum allocatable memory on a process to 2GB. # (We don't choose 3GB (our max RAM) since that would # exhaust all memory, and result in a kernel panic.) # Set default memory size as 768MB. # Maximum stack size is 256MB. # kern.maxdsiz="2048M" kern.dfldsiz="768M" kern.maxssiz="256MB" > I have also read that there are two sysctl namely, kern.maxdsiz and > kern.maxssiz, that can tune memory allocation but what happend to them in > Freebsd 6. These are not sysctls, they are kernel settings. They exist on both RELENG_6 and RELENG_7. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 15:54:18 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF4B01065680 for ; Thu, 22 May 2008 15:54:18 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from n70.bullet.mail.sp1.yahoo.com (n70.bullet.mail.sp1.yahoo.com [98.136.44.38]) by mx1.freebsd.org (Postfix) with SMTP id 8A9FF8FC23 for ; Thu, 22 May 2008 15:54:18 +0000 (UTC) (envelope-from fabonacci@yahoo.com) Received: from [216.252.122.217] by n70.bullet.mail.sp1.yahoo.com with NNFMP; 22 May 2008 15:54:18 -0000 Received: from [69.147.65.173] by t2.bullet.sp1.yahoo.com with NNFMP; 22 May 2008 15:54:18 -0000 Received: from [127.0.0.1] by omp508.mail.sp1.yahoo.com with NNFMP; 22 May 2008 15:54:18 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 29478.81153.bm@omp508.mail.sp1.yahoo.com Received: (qmail 78762 invoked by uid 60001); 22 May 2008 15:54:17 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=tF8A3iEOb4Op/9leiI46BSJ8xBKerM1nCsAO7fJAl/2l/+pKlFnkcMYbV9KIpGlxqCHrbuhshUtQH/zV9/f1yUpS1p/g+oW9Dsk3XM20wlHsYGxCCYTtG6Pkn/65lkcFJWJUcQwGmOJPCJQCsslJ+1UOrFQpHd0AVsgMPT8r8ik=; X-YMail-OSG: 677lTlIVM1l_rj74j6oVgjQdtVXhHKUIqgrW9pn_HI8HScxCESxlA89CrJn4yUIxzq3qpcKxC5PS Received: from [219.128.147.242] by web46311.mail.sp1.yahoo.com via HTTP; Thu, 22 May 2008 08:54:17 PDT Date: Thu, 22 May 2008 08:54:17 -0700 (PDT) From: John Timony To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <839372.78392.qm@web46311.mail.sp1.yahoo.com> X-Mailman-Approved-At: Thu, 22 May 2008 16:06:44 +0000 Subject: How can I translate IP to hostname in C 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, 22 May 2008 15:54:18 -0000 Hi,guys I am writing a c program in FreeBSD,and I can not translate a ip to hostname ,i wonder if there is a function to take this job... s.o.s -Fabonacc From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 16:35:00 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 637D31065670 for ; Thu, 22 May 2008 16:35:00 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 163248FC2A for ; Thu, 22 May 2008 16:35:00 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id DCE9941C747; Thu, 22 May 2008 18:15:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id PMjyBGb4D9BE; Thu, 22 May 2008 18:15:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 5584C41C734; Thu, 22 May 2008 18:15:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 3F6EE44487F; Thu, 22 May 2008 16:14:47 +0000 (UTC) Date: Thu, 22 May 2008 16:14:46 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: John Timony In-Reply-To: <839372.78392.qm@web46311.mail.sp1.yahoo.com> Message-ID: <20080522161214.Y47338@maildrop.int.zabbadoz.net> References: <839372.78392.qm@web46311.mail.sp1.yahoo.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: How can I translate IP to hostname in C 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, 22 May 2008 16:35:00 -0000 On Thu, 22 May 2008, John Timony wrote: Hi, > I am writing a c program in FreeBSD,and I can not > translate a ip to hostname > ,i wonder if there is a function to take this job... You mean like gethostbyaddr()? See also http://www.unixguide.net/network/socketfaq/2.24.shtml for further inspiration on this but slightly different topic. -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 17:17:43 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47E15106566B for ; Thu, 22 May 2008 17:17:43 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 449978FC1D for ; Thu, 22 May 2008 17:17:41 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 1C0581A92DB for ; Thu, 22 May 2008 10:17:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fcfXnhbyJHyz for ; Thu, 22 May 2008 10:17:26 -0700 (PDT) Received: from iago.office.miralink.com (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id CFB2E1A92D9 for ; Thu, 22 May 2008 10:17:26 -0700 (PDT) Message-ID: <4835AAB4.60005@miralink.com> Date: Thu, 22 May 2008 10:17:40 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: FreeBSD Hackers Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ATA patch for RELENG_6 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, 22 May 2008 17:17:43 -0000 I got this patch a while ago and I don't see it appearing in RELENG_6 yet. Can someone "sheperd" this along or point out why it's not acceptable? This patch was generated by a failure to boot correctly off of a compact flash IDE module from Transcend. Index: dev/ata/ata-chipset.c =================================================================== --- dev/ata/ata-chipset.c (.../FreeBSD_RELENG_6_13APR07/src/sys) (revision 5436) +++ dev/ata/ata-chipset.c (.../miralink.FreeBSD.6/src/sys) (revision 5436) @@ -2059,7 +2059,8 @@ atadev->mode = ATA_SA150; } else { - mode = ata_limit_mode(dev, mode, ATA_UDMA5); + /*mode = ata_limit_mode(dev, mode, ATA_UDMA5);*/ + mode = ata_check_80pin(dev, ATA_UDMA5); if (!ata_controlcmd(dev, ATA_SETFEATURES, ATA_SF_SETXFER, 0, mode)) atadev->mode = mode; } -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 17:19:06 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A474106566B for ; Thu, 22 May 2008 17:19:06 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 08F898FC15 for ; Thu, 22 May 2008 17:19:05 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAKlHNUiC1Apk/2dsb2JhbACwPA Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 22 May 2008 10:19:05 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052210190450-945 ; Thu, 22 May 2008 10:19:04 -0700 Date: Thu, 22 May 2008 10:19:04 -0700 (PDT) From: KAYVEN RIESE To: Jeremy Chadwick In-Reply-To: <20080522062336.GA30379@eos.sc1.parodius.com> Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> <20080522062336.GA30379@eos.sc1.parodius.com> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/22/2008 10:19:04, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/22/2008 10:19:05, Serialize complete at 05/22/2008 10:19:05 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@FreeBSD.org Subject: Re: libz.so no found 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, 22 May 2008 17:19:06 -0000 On Wed, 21 May 2008, Jeremy Chadwick wrote: > On Wed, May 21, 2008 at 10:13:43PM -0700, KAYVEN RIESE wrote: >> kv_bsd#cd /usr/ports/distfiles >> kv_bsd#mv /usr/home/kayve/Nessus-3.2.0-fbsd7.tbz . >> kv_bsd#pkg_add Nessus-3.2.0-fbsd7.tbz >> pkg_add: package VisualOS-1.0.5_3 has no origin recorded >> /libexec/ld-elf.so.1: Shared object "libz.so.4" not found, required by >> "nessusd" > > First and foremost, you hijacked an existing thread by replying to it > with regards to a completely different issue. Please don't do this, it > confuses mail clients which follow thread references. Please don't hit > reply on unrelated messages and start a new/unrelated discussion. i don't know wtf you are talking about these are all my threads. > > Secondly, the missing library error shown above would happen on machines > running FreeBSD 6.x or earlier. /lib/libz.so.4 exists on RELENG_7. > i am still on freeBSD 6.3 is this a serious problem? > Another possibility is that something completely destroyed ld.so's > shared library cache path. Of course, you'd be seeing all sorts of > programs reporting missing libraries, and not just nexxus. > so running freeBSD 6.3 is a fatal problem, or just extraneously irrelevant? > If the startup script for nessus calls ldconfig or uses > $LD_LIBRARY_PATH, that could explain the missing library. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 18:19:55 2008 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CED0106568A for ; Thu, 22 May 2008 18:19:55 +0000 (UTC) (envelope-from xistence@0x58.com) Received: from mailexchange.osnn.net (1e.66.5646.static.theplanet.com [70.86.102.30]) by mx1.freebsd.org (Postfix) with SMTP id CFD4F8FC0C for ; Thu, 22 May 2008 18:19:54 +0000 (UTC) (envelope-from xistence@0x58.com) Received: (qmail 62584 invoked by uid 0); 22 May 2008 17:53:13 -0000 Received: from unknown (HELO ?192.168.1.137?) (xistence@0x58.com@168.158.222.244) by mailexchange.osnn.net with SMTP; 22 May 2008 17:53:13 -0000 Message-Id: <26302C14-3599-41FD-8EA0-4BA5B4C96462@0x58.com> From: Bert JW Regeer To: KAYVEN RIESE In-Reply-To: Content-Type: multipart/signed; boundary=Apple-Mail-1--904125059; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 22 May 2008 10:53:12 -0700 References: <001001c8bb66$c4713170$4d539450$@net> <20080522062336.GA30379@eos.sc1.parodius.com> X-Mailer: Apple Mail (2.919.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Hackers Subject: Re: libz.so no found 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, 22 May 2008 18:19:55 -0000 --Apple-Mail-1--904125059 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On May 22, 2008, at 10:19 , KAYVEN RIESE wrote: > On Wed, 21 May 2008, Jeremy Chadwick wrote: > >> On Wed, May 21, 2008 at 10:13:43PM -0700, KAYVEN RIESE wrote: >>> kv_bsd#cd /usr/ports/distfiles >>> kv_bsd#mv /usr/home/kayve/Nessus-3.2.0-fbsd7.tbz . >>> kv_bsd#pkg_add Nessus-3.2.0-fbsd7.tbz You are running on FreeBSD 6.3 and you are trying to add a package that clearly has fbsd7 in the name. Off course it is not going to work. >>> >>> pkg_add: package VisualOS-1.0.5_3 has no origin recorded >>> /libexec/ld-elf.so.1: Shared object "libz.so.4" not found, >>> required by >>> "nessusd" >> >> First and foremost, you hijacked an existing thread by replying to it >> with regards to a completely different issue. Please don't do >> this, it >> confuses mail clients which follow thread references. Please don't >> hit >> reply on unrelated messages and start a new/unrelated discussion. > > i don't know wtf you are talking about these are all my threads. You clicked reply, or something along those lines on a previous message sent to the mailling list, thereby copying over some crucial information into the header of said email: In-Reply-To: Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> For mail clients that do threading, and show the conversation more as one would expect on a message board, your emails now look as if they belong underneath the topic named "Hifn 7955 doesn't work with FreeBSD 7.0-RELEASE", which is annoying to most of us who would want your messages to show up in a new thread context. Next time, please just email hackers@ directly, and do not "hi-jack" the thread. Also, it is generally considered rude to suggest that you don't know what someone is talking about using the "wtf". We point the hi-jacking out so that the mistake does not re-occur. Please refrain from such rudeness when people are attempting to help you. > > >> >> Secondly, the missing library error shown above would happen on >> machines >> running FreeBSD 6.x or earlier. /lib/libz.so.4 exists on RELENG_7. >> > > i am still on freeBSD 6.3 is this a serious problem? If you want to use the package you are using, yes. Since that package is clearly for FreeBSD 7. > > >> Another possibility is that something completely destroyed ld.so's >> shared library cache path. Of course, you'd be seeing all sorts of >> programs reporting missing libraries, and not just nexxus. >> > > so running freeBSD 6.3 is a fatal problem, or just extraneously > irrelevant? Fatal, sure, especially if you want to use that package. > > >> If the startup script for nessus calls ldconfig or uses >> $LD_LIBRARY_PATH, that could explain the missing library. >> >> -- >> | Jeremy Chadwick jdc at >> parodius.com | >> | Parodius Networking http:// >> www.parodius.com/ | >> | UNIX Systems Administrator Mountain View, CA, >> USA | >> | Making life hard for others since 1977. PGP: >> 4BD6C0CB | >> >> > > *----------------------------------------------------------* > Kayven Riese, BSCS, MS (Physiology and Biophysics) > (415) 902 5513 cellular > http://kayve.net > Webmaster http://ChessYoga.org > *----------------------------------------------------------* > _______________________________________________ > 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 > " --Apple-Mail-1--904125059-- From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 18:31:25 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F10B106566C for ; Thu, 22 May 2008 18:31:25 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (unknown [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1EC398FC14 for ; Thu, 22 May 2008 18:31:25 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from [IPv6:2a01:348:10f:0:c179:988f:8401:ad08] (unknown [IPv6:2a01:348:10f:0:c179:988f:8401:ad08]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id D0CDA30120; Thu, 22 May 2008 19:31:23 +0100 (BST) Message-ID: <4835BBD5.1050003@cran.org.uk> Date: Thu, 22 May 2008 19:30:45 +0100 From: Bruce Cran User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: John Timony References: <839372.78392.qm@web46311.mail.sp1.yahoo.com> In-Reply-To: <839372.78392.qm@web46311.mail.sp1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How can I translate IP to hostname in C 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, 22 May 2008 18:31:25 -0000 John Timony wrote: > Hi,guys > > I am writing a c program in FreeBSD,and I can not > translate a ip to hostname > ,i wonder if there is a function to take this job... > You could use gethostbyaddr(3), but those traditional functions have been replaced with more flexible versions such as getnameinfo(3) on newer systems. There's a good introduction to modern sockets programming at http://people.redhat.com/drepper/userapi-ipv6.html -- Bruce Cran From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 18:47:49 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F22AC106566B for ; Thu, 22 May 2008 18:47:49 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 7A79C8FC0A for ; Thu, 22 May 2008 18:47:49 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m4MIOH0o084833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 May 2008 20:24:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m4MIOEBZ060022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 May 2008 20:24:15 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m4MIOBhD055717; Thu, 22 May 2008 20:24:11 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m4MIOB6X055716; Thu, 22 May 2008 20:24:11 +0200 (CEST) (envelope-from ticso) Date: Thu, 22 May 2008 20:24:11 +0200 From: Bernd Walter To: "Bjoern A. Zeeb" Message-ID: <20080522182410.GB55002@cicely7.cicely.de> References: <839372.78392.qm@web46311.mail.sp1.yahoo.com> <20080522161214.Y47338@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080522161214.Y47338@maildrop.int.zabbadoz.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on cicely12.cicely.de Cc: freebsd-hackers@freebsd.org, John Timony Subject: Re: How can I translate IP to hostname in C X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2008 18:47:50 -0000 On Thu, May 22, 2008 at 04:14:46PM +0000, Bjoern A. Zeeb wrote: > On Thu, 22 May 2008, John Timony wrote: > > Hi, > > >I am writing a c program in FreeBSD,and I can not > >translate a ip to hostname > >,i wonder if there is a function to take this job... > > You mean like gethostbyaddr()? > > See also http://www.unixguide.net/network/socketfaq/2.24.shtml for > further inspiration on this but slightly different topic. You can also use the newer getaddrinfo(3)/freeaddrinfo(3). I think it is bit easier to use and can it transparently handle inet6 addresses as well. The only downside is that some rare old systems don't support it. On FreeBSD it is suppoorted since FreeBSD-4, but some commerical OS implemented it later. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 21:16:55 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65A49106564A for ; Thu, 22 May 2008 21:16:55 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id E67978FC0C for ; Thu, 22 May 2008 21:16:54 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m4MLGnLF089724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 May 2008 23:16:50 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m4MLGhm7062125 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 May 2008 23:16:44 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m4MLGeJI056089; Thu, 22 May 2008 23:16:40 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m4MLGdFc056088; Thu, 22 May 2008 23:16:39 +0200 (CEST) (envelope-from ticso) Date: Thu, 22 May 2008 23:16:39 +0200 From: Bernd Walter To: Bruce Cran Message-ID: <20080522211639.GA55771@cicely7.cicely.de> References: <839372.78392.qm@web46311.mail.sp1.yahoo.com> <4835BBD5.1050003@cran.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4835BBD5.1050003@cran.org.uk> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on cicely12.cicely.de Cc: freebsd-hackers@freebsd.org, John Timony Subject: Re: How can I translate IP to hostname in C X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2008 21:16:55 -0000 On Thu, May 22, 2008 at 07:30:45PM +0100, Bruce Cran wrote: > John Timony wrote: > >Hi,guys > > > >I am writing a c program in FreeBSD,and I can not > >translate a ip to hostname > >,i wonder if there is a function to take this job... > > > > You could use gethostbyaddr(3), but those traditional functions have > been replaced with more flexible versions such as getnameinfo(3) on > newer systems. There's a good introduction to modern sockets > programming at http://people.redhat.com/drepper/userapi-ipv6.html Ups - yes that's what I ment in my mail. I wrote getaddrinfo, which is the other direction... -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 21:48:47 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC9C1065675 for ; Thu, 22 May 2008 21:48:47 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 1075D8FC0C for ; Thu, 22 May 2008 21:48:47 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAO+GNUiC1Apk/2dsb2JhbACwcg Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 22 May 2008 14:48:46 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052214484482-973 ; Thu, 22 May 2008 14:48:44 -0700 Date: Thu, 22 May 2008 14:48:44 -0700 (PDT) From: KAYVEN RIESE To: Bert JW Regeer In-Reply-To: <26302C14-3599-41FD-8EA0-4BA5B4C96462@0x58.com> Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> <20080522062336.GA30379@eos.sc1.parodius.com> <26302C14-3599-41FD-8EA0-4BA5B4C96462@0x58.com> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/22/2008 14:48:44, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/22/2008 14:48:45, Serialize complete at 05/22/2008 14:48:45 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Hackers Subject: Re: libz.so no found 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, 22 May 2008 21:48:47 -0000 On Thu, 22 May 2008, Bert JW Regeer wrote: > On May 22, 2008, at 10:19 , KAYVEN RIESE wrote: >> On Wed, 21 May 2008, Jeremy Chadwick wrote: >>> On Wed, May 21, 2008 at 10:13:43PM -0700, KAYVEN RIESE wrote: >> >> i don't know wtf you are talking about these are all my threads. > > You clicked reply, or something along those lines on a previous message sent > to the mailling list, thereby copying over some crucial information into the > header of said email: > > In-Reply-To: > Message-ID: > References: <001001c8bb66$c4713170$4d539450$@net> > > > > For mail clients that do threading, and show the conversation more as one > would expect on a message board, your emails now look as if they belong > underneath the topic named "Hifn 7955 doesn't work with FreeBSD 7.0-RELEASE", > which is annoying to most of us who would want your messages to show up in a > new thread context. Next time, please just email hackers@ directly, and do > not "hi-jack" the thread. okay, so I don't have a shortcut key for freeBSD-hacker.. I went into my freeBSD saved box, grabbed the first email, replied to all, deleted everything including the subject, and despite having revised the subject, your sooperphreekiness found out I was muddling around in the deally bobber? Is that what you are talking about then? So in the future, I should know that editing the subject line will not suffice to make a new thread? If so, sorry. I get it now. >>> >>> -- >>> | Jeremy Chadwick jdc at parodius.com | >>> | Parodius Networking http://www.parodius.com/ | >>> | UNIX Systems Administrator Mountain View, CA, USA | >>> | Making life hard for others since 1977. PGP: 4BD6C0CB | >>> >>> >> >> *----------------------------------------------------------* >> Kayven Riese, BSCS, MS (Physiology and Biophysics) >> (415) 902 5513 cellular >> http://kayve.net >> Webmaster http://ChessYoga.org >> *----------------------------------------------------------* >> _______________________________________________ >> 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" > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 06:58:59 2008 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D88921065676 for ; Fri, 23 May 2008 06:58:59 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 57A4D8FC12 for ; Fri, 23 May 2008 06:58:59 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m4N6wu0F005347; Fri, 23 May 2008 08:58:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m4N6wtm5005346; Fri, 23 May 2008 08:58:55 +0200 (CEST) (envelope-from olli) Date: Fri, 23 May 2008 08:58:55 +0200 (CEST) Message-Id: <200805230658.m4N6wtm5005346@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, fabonacci@yahoo.com, bzeeb-lists@lists.zabbadoz.net In-Reply-To: <20080522161214.Y47338@maildrop.int.zabbadoz.net> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (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]); Fri, 23 May 2008 08:58:58 +0200 (CEST) Cc: Subject: Re: How can I translate IP to hostname in C X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, fabonacci@yahoo.com, bzeeb-lists@lists.zabbadoz.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 06:58:59 -0000 Bjoern A. Zeeb wrote: > John Timony wrote: > > I am writing a c program in FreeBSD,and I can not > > translate a ip to hostname > > ,i wonder if there is a function to take this job... > > You mean like gethostbyaddr()? gethostbyaddr() is considered obsolete, I think. You should use getaddrinfo() instead, which is more flexible and easier to use, and it enables you to easily write code that is independent and agnostic of the address family (IPv4 vs. IPv6 vs. others). The manual page contains detailed example code. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "The most important decision in [programming] language design concerns what is to be left out." -- Niklaus Wirth From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 08:51:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96EF0106568B for ; Fri, 23 May 2008 08:51:34 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id ECC4F8FC1C for ; Fri, 23 May 2008 08:51:33 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-148-169.lns11.adl6.internode.on.net [121.45.148.169]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m4N8pLw5046554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 23 May 2008 18:21:27 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Fri, 23 May 2008 18:20:58 +0930 User-Agent: KMail/1.9.7 References: <001001c8bb66$c4713170$4d539450$@net> <26302C14-3599-41FD-8EA0-4BA5B4C96462@0x58.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1621568.tenAxI4IfI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200805231821.08105.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Bert JW Regeer , KAYVEN RIESE Subject: Re: libz.so no found 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, 23 May 2008 08:51:34 -0000 --nextPart1621568.tenAxI4IfI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 23 May 2008, KAYVEN RIESE wrote: > okay, so I don't have a shortcut key for freeBSD-hacker.. I went into > my freeBSD saved box, grabbed the first email, replied to all, > deleted everything including the subject, and despite having revised > the subject, your sooperphreekiness found out I was muddling around > in the deally bobber? Is that what you are talking about then? So > in the future, I should know that editing the subject line will not > suffice to make a new thread? > > If so, sorry. I get it now. Your mail client sets the In-Reply-To header to the message ID of the=20 email you pulled out of your saved folder. Mail clients use this header to track what thread a message is in (even=20 if someone changed the subject). =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1621568.tenAxI4IfI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBINoV85ZPcIHs/zowRAuKTAJ9V75EnWcuCKkca3tDZYmqBUg4IvgCbBAjG 10kjGAtyj97vUpPY6KZQaFE= =Aelj -----END PGP SIGNATURE----- --nextPart1621568.tenAxI4IfI-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 12:49:50 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D911D1065684 for ; Fri, 23 May 2008 12:49:50 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id C3D098FC22 for ; Fri, 23 May 2008 12:49:50 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEABtaNkiC1Apk/2dsb2JhbACuYw Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 23 May 2008 05:49:50 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052305494905-1010 ; Fri, 23 May 2008 05:49:49 -0700 Date: Fri, 23 May 2008 05:49:48 -0700 (PDT) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 05:49:49, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 05:49:50, Serialize complete at 05/23/2008 05:49:50 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: /usr/src/Makefile instructions 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, 23 May 2008 12:49:50 -0000 My professor told me about instructions being in /usr/src/Makefile for rebuilding my world. I feel better about following them because they are close to the command line to me and can't be out of date, right? I am looking at this list of makes: # check-old - List obsolete directories/files/libraries. # check-old-dirs - List obsolete directories. # check-old-files - List obsolete files. # check-old-libs - List obsolete libraries. # delete-old - Delete obsolete directories/files/libraries. # delete-old-dirs - Delete obsolete directories. # delete-old-files - Delete obsolete files. # delete-old-libs - Delete obsolete libraries. # I am wondering if I should try these out, or will it just be taken care of with the "cannonical" methods. I seem to have lots of big problems with my configuration.. I don't know. Things work, but dmesg has errors, and many ports fail and their makes, even if they succeed have errors and warnings. If I "delete-old-.." will I be messing things up? *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 12:52:14 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 268F4106566B for ; Fri, 23 May 2008 12:52:14 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0C04F8FC1B for ; Fri, 23 May 2008 12:52:13 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAAxbNkiC1Apk/2dsb2JhbACuZA Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 23 May 2008 05:52:13 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052305521277-1011 ; Fri, 23 May 2008 05:52:12 -0700 Date: Fri, 23 May 2008 05:52:12 -0700 (PDT) From: KAYVEN RIESE To: Daniel O'Connor In-Reply-To: <200805231821.08105.doconnor@gsoft.com.au> Message-ID: References: <001001c8bb66$c4713170$4d539450$@net> <26302C14-3599-41FD-8EA0-4BA5B4C96462@0x58.com> <200805231821.08105.doconnor@gsoft.com.au> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 05:52:12, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 05:52:13, Serialize complete at 05/23/2008 05:52:13 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Bert JW Regeer Subject: Re: libz.so no found 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, 23 May 2008 12:52:14 -0000 On Fri, 23 May 2008, Daniel O'Connor wrote: > On Fri, 23 May 2008, KAYVEN RIESE wrote: >> okay, so I don't have a shortcut key for freeBSD-hacker.. I went into >> my freeBSD saved box, grabbed the first email, replied to all, >> deleted everything including the subject, and despite having revised >> the subject, your sooperphreekiness found out I was muddling around >> in the deally bobber? Is that what you are talking about then? So >> in the future, I should know that editing the subject line will not >> suffice to make a new thread? >> >> If so, sorry. I get it now. > > Your mail client sets the In-Reply-To header to the message ID of the > email you pulled out of your saved folder. > > Mail clients use this header to track what thread a message is in (even > if someone changed the subject). Thanks. This makes things clear. I'm sorry that I felt "scolded" by the confusing barrage (I guess at least a couple of you thought this should have been obvious to me). > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 13:15:18 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 495FB1065671 for ; Fri, 23 May 2008 13:15:18 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id 331DA8FC1D for ; Fri, 23 May 2008 13:15:18 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAPdfNkiC1Apk/2dsb2JhbACuYQ Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 23 May 2008 06:15:17 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052306151587-1012 ; Fri, 23 May 2008 06:15:15 -0700 Date: Fri, 23 May 2008 06:15:15 -0700 (PDT) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 06:15:16, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 06:15:17, Serialize complete at 05/23/2008 06:15:17 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Warning during make buildworld 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, 23 May 2008 13:15:18 -0000 There was one about "mktemp()" ./gengtype warning: structure `VEC_cp_token_position_heap' used but not defined warning: structure `c_arg_info' used but not defined warning: structure `c_switch' used but not defined warning: structure `et_node' used but not defined warning: structure `loop' used but not defined warning: structure `ipa_reference_vars_info_d' used but not defined warning: structure `reg_info_def' used but not defined warning: structure `value_set' used but not defined warning: structure `VEC_cp_token_position_heap' used but not defined warning: structure `c_arg_info' used but not defined warning: structure `c_switch' used but not defined warning: structure `et_node' used but not defined warning: structure `loop' used but not defined warning: structure `ipa_reference_vars_info_d' used but not defined warning: structure `reg_info_def' used but not defined warning: structure `value_set' used but not defined touch gtype-desc.h *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 13:39:49 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9B66106564A for ; Fri, 23 May 2008 13:39:49 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 626F88FC16 for ; Fri, 23 May 2008 13:39:49 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by nf-out-0910.google.com with SMTP id h3so347558nfh.33 for ; Fri, 23 May 2008 06:39:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; bh=pc8X9fwrIS3Yds2Oy13vOJ0DlYfoFv6Kv5ysq4abYlo=; b=uMAxHeWrX0d8W5Mld/VyrpmzEDdBvh1aMQJMFBeRzIvnOCkvTcV7oCDO1RbxzqxxmxMGX6swuK1Ihr1Sv2JMrXQRY72m73uimf9p0bi5enLXHTtiK7NtryQtU5FpudUI2dH4ISPz2Ot4o/o6uQsumACod8ne+10uVETPevmkrx0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=a8o9jjwklpU3HCx2wiwhxrIXpfSltL36LRxou1HILrcy2patPncMoKwsIS9mjgoZvYYoGGOAVk7pww0lNRm1kbxyKdWQSF6jDgIw1/Wpw1zEgVCrYIyJYzgIqP80rjEE90gBN2ek1IUa2ighWmDB1yfmjdt4H7D41KG/JgNMwHQ= Received: by 10.210.39.2 with SMTP id m2mr1143477ebm.169.1211548244208; Fri, 23 May 2008 06:10:44 -0700 (PDT) Received: from ?127.0.0.1? ( [217.206.187.80]) by mx.google.com with ESMTPS id t12sm10148698gvd.10.2008.05.23.06.10.41 (version=SSLv3 cipher=RC4-MD5); Fri, 23 May 2008 06:10:42 -0700 (PDT) From: Tom Evans To: KAYVEN RIESE In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L3zPns5iiYRDETDqREIj" Date: Fri, 23 May 2008 14:10:39 +0100 Message-Id: <1211548239.10665.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port Cc: freebsd-hackers@freebsd.org Subject: Re: /usr/src/Makefile instructions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 13:39:49 -0000 --=-L3zPns5iiYRDETDqREIj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2008-05-23 at 05:49 -0700, KAYVEN RIESE wrote: > My professor told me about instructions being in /usr/src/Makefile > for rebuilding my world. I feel better about following them because > they are close to the command line to me and can't be out of date, right? >=20 > I am looking at this list of makes: >=20 > # check-old - List obsolete directories/files/libraries. > # check-old-dirs - List obsolete directories. > # check-old-files - List obsolete files. > # check-old-libs - List obsolete libraries. > # delete-old - Delete obsolete directories/files/libraries. > # delete-old-dirs - Delete obsolete directories. > # delete-old-files - Delete obsolete files. > # delete-old-libs - Delete obsolete libraries. > # >=20 >=20 > I am wondering if I should try these out, or will it just be > taken care of with the "cannonical" methods. I seem to have lots > of big problems with my configuration.. I don't know. Things > work, but dmesg has errors, and many ports fail and their makes, > even if they succeed have errors and warnings. >=20 > If I "delete-old-.." will I be messing things up? >=20 No, it will "Delete obsolete directories/files/libraries", with the usual meaning of obsolete. You should only need to do this when moving to a new (major?) release. I've redirected this to questions@, as this seems more like a 'User question/technical support' rather than 'General technical discussion'. Please try to keep the mailing lists on topic. Cheers Tom --=-L3zPns5iiYRDETDqREIj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkg2wkkACgkQlcRvFfyds/eK3ACeKropCSeXTWLuphSBrzt75R4b cwwAoKCCzbKtFP9i/lzDiZ8k0RwYinUX =sBsD -----END PGP SIGNATURE----- --=-L3zPns5iiYRDETDqREIj-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 13:45:50 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17F71106566B for ; Fri, 23 May 2008 13:45:50 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id D07098FC1B for ; Fri, 23 May 2008 13:45:49 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id m4NDQnE7070012; Fri, 23 May 2008 06:26:49 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id m4NDQnjV070011; Fri, 23 May 2008 06:26:49 -0700 (PDT) (envelope-from david) Date: Fri, 23 May 2008 06:26:49 -0700 From: David Wolfskill To: KAYVEN RIESE Message-ID: <20080523132649.GB69430@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , KAYVEN RIESE , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="61jdw2sOBCFtR2d/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: /usr/src/Makefile instructions 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, 23 May 2008 13:45:50 -0000 --61jdw2sOBCFtR2d/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 23, 2008 at 05:49:48AM -0700, KAYVEN RIESE wrote: >=20 > My professor told me about instructions being in /usr/src/Makefile > for rebuilding my world. I feel better about following them because > they are close to the command line to me and can't be out of date, right? No. Any comments or documentation *can* be "out of date" or otherwise misleading or incorrect. > I am looking at this list of makes: Err.. that would be "make targets," yeah? > # check-old - List obsolete directories/files/libraries. > # check-old-dirs - List obsolete directories. > # check-old-files - List obsolete files. > # check-old-libs - List obsolete libraries. > # delete-old - Delete obsolete directories/files/libraries. > # delete-old-dirs - Delete obsolete directories. > # delete-old-files - Delete obsolete files. > # delete-old-libs - Delete obsolete libraries. > # >=20 >=20 > I am wondering if I should try these out, or will it just be > taken care of with the "cannonical" methods. I expect that depends a great deal on what your objectives are. If you are merely trying to keep a system up-to-date, you are (IMO) better off reading, then paying attention to changes in, /usr/src/UPDATING. If, on the other hand, you are curious about just what make(1) will do when told to make a given target, by all means experiment to your heart's content (on your own system(s)). But I encourage you to consider the utility of the "-n" flag to make(1). Well, that, as well as the value of good backup & restore procedures. > I seem to have lots > of big problems with my configuration.. I don't know. Things > work, but dmesg has errors, and many ports fail and their makes, > even if they succeed have errors and warnings. >=20 > If I "delete-old-.." will I be messing things up? Hard to say without more information about your current configuration than is likely to fit in a message to the mailing list. If the complaints are sufficiently severe (note that the mere quantity of them isn't a relaible measure of this), you may be better off recording salient configuration information (e.g., what ports you tried to install), make a good backup (assuming there's data worth recovering), wiping the system clean, and starting over. It is certainly possible to mess a system up enough that recovery is problematic, at best. Peace, david --=20 David H. Wolfskill david@catwhisker.org I submit that "conspiracy" would be an appropriate collective noun for cats. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --61jdw2sOBCFtR2d/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkg2xhgACgkQmprOCmdXAD2wkwCffYLMcatUeykwevvVO94u+uMp Fy4AniFD6cLvvKsN+ZoFwIcJUuImnrTT =L7ac -----END PGP SIGNATURE----- --61jdw2sOBCFtR2d/-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 13:50:02 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24F3E106566B for ; Fri, 23 May 2008 13:50:02 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0A9818FC1E for ; Fri, 23 May 2008 13:50:01 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAO9nNkiC1Apk/2dsb2JhbACuWA Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 23 May 2008 06:50:01 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052306500138-1013 ; Fri, 23 May 2008 06:50:01 -0700 Date: Fri, 23 May 2008 06:50:00 -0700 (PDT) From: KAYVEN RIESE To: freebsd-questions@freebsd.org In-Reply-To: <1211548239.10665.4.camel@localhost> Message-ID: References: <1211548239.10665.4.camel@localhost> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 06:50:01, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 06:50:01, Serialize complete at 05/23/2008 06:50:01 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: /usr/src/Makefile instructions 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, 23 May 2008 13:50:02 -0000 On Fri, 23 May 2008, Tom Evans wrote: > On Fri, 2008-05-23 at 05:49 -0700, KAYVEN RIESE wrote: > > I've redirected this to questions@, as this seems more like a 'User > question/technical support' rather than 'General technical discussion'. > Please try to keep the mailing lists on topic. That list is too busy. I find I don't have to unsubscribe to "hackers," and it doesn't seem as hard core to misinterpret what "hackers" are, than say "ports" or "acpi" I realized that "make delete-old" and "make delete-old-libs" are both part of the "cannonical," I guess because I am going RELENG_6_3 to RELENG_7 On that note, was I given misinformation when I was advised that it would be impossible to upgrade RELENG_6_2 directly to RELENG_7 ? > > Cheers > > Tom > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 14:24:55 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20BA3106566B for ; Fri, 23 May 2008 14:24:55 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mo3so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id E9CBB8FC22 for ; Fri, 23 May 2008 14:24:54 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mr4so.prod.shaw.ca (pd4mr4so-qfe3.prod.shaw.ca [10.0.141.215]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K1B00IGQS0S44E0@l-daemon>; Fri, 23 May 2008 08:24:28 -0600 (MDT) Received: from pn2ml9so.prod.shaw.ca ([10.0.121.7]) by pd4mr4so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0K1B00CY2S0RXG80@pd4mr4so.prod.shaw.ca>; Fri, 23 May 2008 08:24:28 -0600 (MDT) Received: from soralx ([24.87.3.133]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K1B00AVPS0RWD10@l-daemon>; Fri, 23 May 2008 08:24:27 -0600 (MDT) Date: Fri, 23 May 2008 07:24:26 -0700 From: soralx@cydem.org In-reply-to: To: kayve@sfsu.edu Message-id: <20080523072426.7de88f38@soralx> MIME-version: 1.0 X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit References: <1211548239.10665.4.camel@localhost> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: /usr/src/Makefile instructions 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, 23 May 2008 14:24:55 -0000 > On that note, was I given misinformation when I was advised > that it would be impossible to upgrade RELENG_6_2 directly to > RELENG_7 ? Close to implausible, perhaps? That would indeed be the case, unless you truly are longing for a major workout, either with mergemaster et al, or both with mergemaster and the ports. The former case, which assumes you don't have many ports installed, is often a no-brainer: install a fresh system. The latter case may be somewhat more complicated: install a fresh system for the least effort on your side, or go the update route if you need to keep your system up and usable during the process. I should note that I always took the update trail, and never regretted it afterwards (well, if only so slightly). For instance, my workstation lived through 5.2.1-R, 6.2-R, RELENG_6, and finally RELENG_7, all with the aid of cvsup. The process is straightforward, well-designed and easily executed (thanks to the developers), but problems often pop-up with ports (especially such messy ones as Gnome, etc) which take lots of time to correct. So, in summary, a sane person should probably go with clean system update. P.S.: whoever replies next, it's safe to drop hackers@ from CC: anytime now > Kayven Riese, BSCS, MS (Physiology and Biophysics) [SorAlx] ridin' VS1400 From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 14:43:04 2008 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86E49106567F; Fri, 23 May 2008 14:43:04 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id EC9798FC1A; Fri, 23 May 2008 14:43:03 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m4NEgx2f022252; Fri, 23 May 2008 16:43:02 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m4NEgxnm022251; Fri, 23 May 2008 16:42:59 +0200 (CEST) (envelope-from olli) Date: Fri, 23 May 2008 16:42:59 +0200 (CEST) Message-Id: <200805231442.m4NEgxnm022251@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, kayve@sfsu.edu In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (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]); Fri, 23 May 2008 16:43:02 +0200 (CEST) Cc: Subject: Re: /usr/src/Makefile instructions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@FreeBSD.ORG, kayve@sfsu.edu List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 14:43:04 -0000 KAYVEN RIESE wrote: > Tom Evans wrote: > > I've redirected this to questions@, as this seems more like a 'User > > question/technical support' rather than 'General technical discussion'. > > Please try to keep the mailing lists on topic. > > That list is too busy. I find I don't have to unsubscribe to > "hackers," and it doesn't seem as hard core to misinterpret > what "hackers" are, than say "ports" or "acpi" Well, "hackers" usually means developers, i.e. people hacking on the FreeBSD code. Therefore I'm afraid I have to agree with Tom: Your questions should better go to the questions list. > I realized that "make delete-old" and "make delete-old-libs" > are both part of the "cannonical," I guess because I am going > RELENG_6_3 to RELENG_7 I always use "make delete-old", as instructed in the /usr/src/UPDATING file, and it has never bitten me. Please have a look at that file; the important part starts at the section titled "To rebuild everything". > On that note, was I given misinformation when I was advised > that it would be impossible to upgrade RELENG_6_2 directly to > RELENG_7 ? "Nothing is impossible!", as Dr. Farnsworth from the Futurama series used to say. :-) But seriously ... I think going from 6.2 to 7.0 should work fine. However, the official notion is that updates across major versions have to be supported only for the latest stable release. Any other configurations might work, but it's not guaranteed. If it fails, you're not expected to complain or ask for help, but instead try the officially supported way (i.e. first update to the latest stable on your existing branch, then update across the major version boundary). If that still fails, you may complain and ask for help. Note that it is IMPORTANT to rebuild *all* of your ports when you update from 6.x to 7.x. (This holds true for any major version update.) If you don't do this, you will get library dependency collisions, i.e. port A uses libc.so.7 and depends on port B, but port B still links against the older libc.so.6. Things will break sooner or later. That's why you should rebuild *all* ports after updating to 7.x. (You can keep older ports only if you are absolutely sure that they are not part of any dependencies, and never will be.) In your previous mail you mentioned: > Things work, but dmesg has errors, Would you please tell us what those errors are? We might be able to help you, but only if you tell us. > and many ports fail and their makes Again: Please post messages and everything relevant to the problems. There are really people on these lists that are willing to help, but we need as much information as possible in order to be able to help. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 17:18:28 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47AB7106566B for ; Fri, 23 May 2008 17:18:28 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 0F8488FC15 for ; Fri, 23 May 2008 17:18:27 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so918288rvf.43 for ; Fri, 23 May 2008 10:18:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=POFGbDmpl+zqKRXV9z3NVT0RL2J+7YExahTaNi7bxoE=; b=T3u/8yXyB92BaneWkf7n06/xE80KMG7YJn69YY4J6QBmjhIf6Gvjppynr2zQbL09zO3LSG2oROBTazTd0pBtMpO2B+UZfAfalqD9D0ewT2CUuu7DfyKRa0dqwPd7XT98RKoyC9O4tkuko3UnMPaQrdOboxq/jFzeuZ7fbuZaQs8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=OOwwiHj4NkQ2C2V0lWuf3Cqsveffp+jiQcxgAab2cOHsbLk0qiNEVAOxLOQ7IlJ2hTPb4Mg81z63bc21m/taUWH6l97JtaF/fDfUjo8PiOfUzYv+SxS1fUzJrJAhc10FqzFr9OH4tG6uE3FuP0oY/jz9vUik6BQpGL92kfcK9z0= Received: by 10.141.48.10 with SMTP id a10mr765315rvk.35.1211561552591; Fri, 23 May 2008 09:52:32 -0700 (PDT) Received: by 10.141.186.2 with HTTP; Fri, 23 May 2008 09:52:32 -0700 (PDT) Message-ID: <11167f520805230952t67ade6bboca089bf7752b107d@mail.gmail.com> Date: Fri, 23 May 2008 11:52:32 -0500 From: "Sam Fourman Jr." To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: patch for Intel G33 on FreeBSD 6.3 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, 23 May 2008 17:18:28 -0000 hello, I have a New motherboard that has a integrated Intel G33 based video card. I see there is support for this in FreeBSD 7 kernel. (Disabled by Default) http://lists.freebsd.org/pipermail/cvs-src/2007-July/080677.html I was wondering if anyone had a patch laying around that would apply on FreeBSD 6.3 I would be more than willing to test this and even provide back traces. Thank you Sam Fourman Jr. From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 01:57:29 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 717C8106564A; Sat, 24 May 2008 01:57:29 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 4082B8FC13; Sat, 24 May 2008 01:57:29 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAOUSN0iC1Apk/2dsb2JhbACufQ Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 23 May 2008 18:57:29 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052318572713-1045 ; Fri, 23 May 2008 18:57:27 -0700 Date: Fri, 23 May 2008 18:57:27 -0700 (PDT) From: KAYVEN RIESE To: soralx@cydem.org In-Reply-To: <20080523072426.7de88f38@soralx> Message-ID: References: <1211548239.10665.4.camel@localhost> <20080523072426.7de88f38@soralx> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 18:57:27, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 18:57:28, Serialize complete at 05/23/2008 18:57:28 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: /usr/src/Makefile instructions 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, 24 May 2008 01:57:29 -0000 On Fri, 23 May 2008, soralx@cydem.org wrote: > >> On that note, was I given misinformation when I was advised >> that it would be impossible to upgrade RELENG_6_2 directly to >> RELENG_7 ? > > Close to implausible, perhaps? That would indeed be the case, unless you > truly are longing for a major workout, either with mergemaster et al, or > both with mergemaster and the ports. The former case, which assumes you > don't have many ports installed, is often a no-brainer: install a fresh > system. The latter case may be somewhat more complicated: install a fresh > system for the least effort on your side, or go the update route if you need > to keep your system up and usable during the process. I didn't really understand that and I don't understand why I am a bad person for spamming my idiotic thoughts on the matter, but in any case this is moot because I am up an runing RELENG_6_3 and making kernel after editing the stable-supfiles RELENG_6_3 to RELENG_7 let's all cross our fingers that communication has just happened. > I should note that I always took the update trail, and never regretted it > afterwards (well, if only so slightly). For instance, my workstation lived > through 5.2.1-R, 6.2-R, RELENG_6, and finally RELENG_7, all with the aid of > cvsup. The process is straightforward, well-designed and easily executed > (thanks to the developers), but problems often pop-up with ports > (especially such messy ones as Gnome, etc) which take lots of time to > correct. I am feeling better about cvsup and even mergemaster nowadays. Thank you very much for your support. > > So, in summary, a sane person should probably go with clean system update. > Is that what I am doing? Umm.. maybe not. I have all these errors that I don't understand and that people ignore but I have a browser and a terminal, so I feel like a functioning pile of carbon compounds. > P.S.: whoever replies next, it's safe to drop hackers@ from CC: anytime now > Naaaaah.. hackers needs the publicity! >> Kayven Riese, BSCS, MS (Physiology and Biophysics) > > [SorAlx] ridin' VS1400 > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 02:00:51 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77F16106566C; Sat, 24 May 2008 02:00:51 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 40BE58FC19; Sat, 24 May 2008 02:00:51 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEADMUN0iC1Apk/2dsb2JhbACufQ Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 23 May 2008 19:00:48 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052319004557-1046 ; Fri, 23 May 2008 19:00:45 -0700 Date: Fri, 23 May 2008 19:00:46 -0700 (PDT) From: KAYVEN RIESE To: soralx@cydem.org In-Reply-To: <20080523072426.7de88f38@soralx> Message-ID: References: <1211548239.10665.4.camel@localhost> <20080523072426.7de88f38@soralx> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 19:00:45, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 19:00:48, Serialize complete at 05/23/2008 19:00:48 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: /usr/src/Makefile instructions 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, 24 May 2008 02:00:51 -0000 On Fri, 23 May 2008, soralx@cydem.org wrote: > >> On that note, was I given misinformation when I was advised >> that it would be impossible to upgrade RELENG_6_2 directly to >> RELENG_7 ? pcm/mixer.c /usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sndstat.c /usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sound.c /usr/src/sys/modules/sound/sound/../../../dev/sound/unit.c /usr/src/sys/module > > Close to implausible, perhaps? That would indeed be the case, unless you > truly are longing for a major workout, either with mergemaster et al, or > both with mergemaster and the ports. The former case, which assumes you > don't have many ports installed, is often a no-brainer: install a fresh > system. The latter case may be somewhat more complicated: install a fresh > system for the least effort on your side, or go the update route if you need > to keep your system up and usable during the process. > awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/sym/../../dev/sym/sym_hipd.c ===> syscons (depend) ===> syscons/apm (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/apm/../../../dev/syscons/apm/apm_saver.c ===> syscons/blank (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/blank/../../../dev/syscons/blank/blank_saver.c ===> syscons/daemon (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/daemon/../../../dev/syscons/daemon/daemon_saver.c ===> syscons/dragon (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/dragon/../../../dev/syscons/dragon/dragon_saver.c ===> syscons/fade (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/fade/../../../dev/syscons/fade/fade_saver.c ===> syscons/fire (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/fire/../../../dev/syscons/fire/fire_saver.c ===> syscons/green (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/green/../../../dev/syscons/green/green_saver.c ===> syscons/logo (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/logo/../../../dev/syscons/logo/logo_saver.c /usr/src/sys/modules/syscons/logo/../../../dev/syscons/logo/logo.c > I should note that I always took the update trail, and never regretted it > afterwards (well, if only so slightly). For instance, my workstation lived > through 5.2.1-R, 6.2-R, RELENG_6, and finally RELENG_7, all with the aid of > cvsup. The process is straightforward, well-designed and easily executed > (thanks to the developers), but problems often pop-up with ports > (especially such messy ones as Gnome, etc) which take lots of time to > correct. rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/sysvipc/sysvshm/../../../kern/sysv_shm.c ===> ti (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_ti.h opt_ti.h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_zero.h opt_zero.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/ti/../../dev/ti/if_ti.c ^C*** .depend removed kv_bsd# oops? mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/rain/../../../dev/syscons/rain/rain_saver.c ===> syscons/snake (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/snake/../../../dev/syscons/snake/snake_saver.c ===> syscons/star (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/star/../../../dev/syscons/star/star_saver.c ===> syscons/warp (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/syscons/warp/../../../dev/syscons/warp/warp_saver.c ===> sysvipc (depend) ===> sysvipc/sysvmsg (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include ln -sf /usr/obj/usr/src/sys/GENERIC/opt_mac.h opt_mac.h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_sysvipc.h opt_sysvipc.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/sysvipc/sysvmsg/../../../kern/sysv_msg.c ===> sysvipc/sysvsem (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include ln -sf /usr/obj/usr/src/sys/GENERIC/opt_mac.h opt_mac.h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_sysvipc.h opt_sysvipc.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/sysvipc/sysvsem/../../../kern/sysv_sem.c ===> sysvipc/sysvshm (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include ln -sf /usr/obj/usr/src/sys/GENERIC/opt_mac.h opt_mac.h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_sysvipc.h opt_sysvipc.h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_compat.h opt_compat.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/sysvipc/sysvshm/../../../kern/sysv_shm.c ===> ti (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_ti.h opt_ti.h ln -sf /usr/obj/usr/src/sys/GENERIC/opt_zero.h opt_zero.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/ti/../../dev/ti/if_ti.c ^C*** .depend removed kv_bsd#make kernel -------------------------------------------------------------- >>> Kernel build for GENERIC started on Fri May 23 18:59:22 PDT 2008 -------------------------------------------------------------- ===> GENERIC mkdir -p /usr/obj/usr/src/sys -------------------------------------------------------------- >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/GENERIC /usr/src/sys/i386/conf/GENERIC Kernel build directory is /usr/obj/usr/src/sys/GENERIC Don't forget to do ``make cleandepend && make depend'' -------------------------------------------------------------- >>> stage 2.1: cleaning up the object tree -------------------------------------------------------------- cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make KERNEL=kernel cleandir rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel kernel.symbols linterrs makelinks tags vers.c vnode_if.c vnode_if.h vnode_if_newproto.h vnode_if_typedef.h ata_if.c eisa_if.c miibus_if.c mmcbr_if.c mmcbus_if.c card_if.c power_if.c pci_if.c pcib_if.c ppbus_if.c uart_if.c usb_if.c g_part_if.c isa_if.c bus_if.c cpufreq_if.c device_if.c linker_if.c serdev_if.c agp_if.c acpi_if.c ata_if.h eisa_if.h miibus_if.h mmcbr_if.h mmcbus_if.h card_if.h power_if.h pci_if.h pcib_if.h ppbus_if.h uart_if.h usb_if.h g_part_if.h isa_if.h bus_if.h cpufreq_if.h device_if.h linker_if.h serdev_if.h agp_if.h acpi_if.h aicasm* y.tab.h aic7xxx_seq.h aic7xxx_reg.h aic7xxx_reg_print.c aic79xx_seq.h aic79xx_reg.h aic79xx_reg_print.c miidevs.h pccarddevs.h usbdevs.h usbdevs_data.h opt_ah.h rm -f .depend machine cd /usr/src/sys/modules; MAKEOBJDIRPREFIX=/usr/obj/usr/src/sys/GENERIC/modules KMODDIR=/boot/kernel DEBUG_FLAGS="-g" MACHINE=i386 KERNBUILDDIR="/usr/obj/usr/src/sys/GENERIC" make cleandir ===> 3dfx (cleandir) ===> 3dfx_linux (cleandir) ===> aac (cleandir) ===> aac/aac_linux (cleandir) rm -f export_syms aac_linux.ko aac_linux.kld aac_linux.o aac_linux.ko.debug aac_linux.ko.symbols rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> accf_data (cleandir) > > So, in summary, a sane person should probably go with clean system update. ==> netgraph/l2tp (cleandir) ==> netgraph/lmi (cleandir) ==> netgraph/mppc (cleandir) ==> netgraph/nat (cleandir) ==> netgraph/netflow (cleandir) ==> netgraph/netgraph (cleandir) ==> netgraph/one2many (cleandir) ==> netgraph/ppp (cleandir) ==> netgraph/pppoe (cleandir) ==> netgraph/pptpgre (cleandir) ==> netgraph/pred1 (cleandir) ==> netgraph/rfc1490 (cleandir) ==> netgraph/socket (cleandir) ==> netgraph/source (cleandir) ==> netgraph/split (cleandir) ==> netgraph/sppp (cleandir) ==> netgraph/sync_ar (cleandir) ==> netgraph/sync_sr (cleandir) ==> netgraph/tag (cleandir) ==> netgraph/tcpmss (cleandir) ==> netgraph/tee (cleandir) > > P.S.: whoever replies next, it's safe to drop hackers@ from CC: anytime now sr/src/sys/modules/cd9660_iconv => cdce (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cdce created for /usr/src ys/modules/cdce => ce (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/ce created for /usr/src/s /modules/ce => ciss (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/ciss created for /usr/src ys/modules/ciss => cm (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cm created for /usr/src/s /modules/cm => cmx (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cmx created for /usr/src/sys/modules/cmx => coda (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/coda created for /usr/src/sys/modules/coda => coda5 (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/coda5 created for /usr/src/sys/modules/coda5 => coff (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/coff created for /usr/src/sys/modules/coff => coretemp (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/coretemp created for /usr/src/sys/modules/coretemp => cp (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cp created for /usr/src/sys/modules/cp => cpufreq (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cpufreq created for /usr/src/sys/modules/cpufreq => crypto (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/crypto created for /usr/src/sys/modules/crypto => cryptodev (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cryptodev created for /usr/src/sys/modules/cryptodev => cs (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cs created for /usr/src/sys/modules/cs => ctau (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/ctau created for /usr/src/sys/modules/ctau => cue (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cue created for /usr/src/sys/modules/cue => cxgb (obj) => cxgb/cxgb (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cxgb/cxgb created for /usr/src/sys/modules/cxgb/cxgb => cxgb/cxgb_t3fw (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cxgb/cxgb_t3fw created for /usr/src/sys/modules/cxgb/cxgb_t3fw => cx (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/cx created for /usr/src/sys/modules/cx => dc (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/dc created for /usr/src/sys/modules/dc => dcons (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/dcons created for /usr/src/sys/modules/dcons => dcons_crom (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/dcons_crom created for /usr/src/sys/modules/dcons_crom => de (obj) sr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/de created for /usr/src/sys/modules/de => digi (obj) => digi/digi (obj) > >> Kayven Riese, BSCS, MS (Physiology and Biophysics) > > [SorAlx] ridin' VS1400 > _______________________________________________ > 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" > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 02:09:14 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29A4E1065670; Sat, 24 May 2008 02:09:14 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id EC0948FC26; Sat, 24 May 2008 02:09:13 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAF4VN0iC1Apk/2dsb2JhbACufw Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 23 May 2008 19:09:13 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052319091190-1047 ; Fri, 23 May 2008 19:09:11 -0700 Date: Fri, 23 May 2008 19:09:11 -0700 (PDT) From: KAYVEN RIESE To: freebsd-questions@FreeBSD.ORG, kayve@sfsu.edu In-Reply-To: <200805231442.m4NEgxnm022251@lurza.secnetix.de> Message-ID: References: <200805231442.m4NEgxnm022251@lurza.secnetix.de> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 19:09:12, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 19:09:13, Serialize complete at 05/23/2008 19:09:13 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-758783491-1211594951=:27721" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /usr/src/Makefile instructions 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, 24 May 2008 02:09:14 -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. ---559023410-758783491-1211594951=:27721 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed On Fri, 23 May 2008, Oliver Fromme wrote: > KAYVEN RIESE wrote: > > Tom Evans wrote: > > > I've redirected this to questions@, as this seems more like a 'User > > > question/technical support' rather than 'General technical discussion= '. > > > Please try to keep the mailing lists on topic. > > > > That list is too busy. I find I don't have to unsubscribe to > > "hackers," and it doesn't seem as hard core to misinterpret > > what "hackers" are, than say "ports" or "acpi" > > Well, "hackers" usually means developers, i.e. people > hacking on the FreeBSD code. Therefore I'm afraid I > have to agree with Tom: Your questions should better > go to the questions list. ergo: because obviously I am a flumming idiot. I thought hacker was something you took eucalyptus fro. > > > I realized that "make delete-old" and "make delete-old-libs" > > are both part of the "cannonical," I guess because I am going > > RELENG_6_3 to RELENG_7 > > I always use "make delete-old", as instructed in the > /usr/src/UPDATING file, and it has never bitten me. > Please have a look at that file; the important part > starts at the section titled "To rebuild everything". > Actually, after composing this I kicked myself, because /usr/src/Makefile has clearly instructed me to do make delete-old after make installworld and I think I will throw caution to the wind and append -U to my subsequent mergemaster followed by make delete-old-libs > > On that note, was I given misinformation when I was advised > > that it would be impossible to upgrade RELENG_6_2 directly to > > RELENG_7 ? > > "Nothing is impossible!", as Dr. Farnsworth from the > Futurama series used to say. :-) > Oh well. Water under the bridge. I expect to someday edit this to RELENG_7_1 or the like when freebsd.org says so and following the instructions in /usr/src/Makefile again. > But seriously ... I think going from 6.2 to 7.0 should > work fine. However, the official notion is that updates > across major versions have to be supported only for the > latest stable release. Any other configurations might > work, but it's not guaranteed. If it fails, you're not > expected to complain or ask for help, but instead try > the officially supported way (i.e. first update to the > latest stable on your existing branch, then update > across the major version boundary). If that still fails, > you may complain and ask for help. > Interesting. No. Fascinitating. Captian Kirk, I believe this star will supernova in approximately 12 days, 13 hours, 34 minutes and 23.3425 seconds. > Note that it is IMPORTANT to rebuild *all* of your ports > when you update from 6.x to 7.x. (This holds true for > any major version update.) If you don't do this, you > will get library dependency collisions, i.e. port A uses > libc.so.7 and depends on port B, but port B still links > against the older libc.so.6. Things will break sooner > or later. That's why you should rebuild *all* ports > after updating to 7.x. (You can keep older ports only > if you are absolutely sure that they are not part of any > dependencies, and never will be.) > My habit is to run cvsup standard-supfile followed by cvsup ports-supfile. IS that a dumb thing to do? > In your previous mail you mentioned: > > Things work, but dmesg has errors, > > Would you please tell us what those errors are? We might > be able to help you, but only if you tell us. > I told the ACPI folks and they told me nicely that my appropriate post was too much of a hassle to bother with. Some ding dong was attaching after the fact of the wing ding and the fact that the errors occured between the wing and the ding was irrelevant since the dong ding subsequent to the ding ding recalibrated the whosits in an adequate fashion before reaching single user mode. > > and many ports fail and their makes > > Again: Please post messages and everything relevant to > the problems. There are really people on these lists > that are willing to help, but we need as much information > as possible in order to be able to help. > > Best regards > Oliver > Well.. I reckon I mights a git up thah gumpshun whenis I's gonna get tootin' on sumptin that gits mah goat subsequently. > --=20 > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch=E4ftsfuehrun= g: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M=FC= n- > chen, HRB 125758, Gesch=E4ftsf=FChrer: Maik Bachmann, Olaf Erb, Ralf Geb= hart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > 'Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom.' > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* ---559023410-758783491-1211594951=:27721-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 03:38:18 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17AC21065674 for ; Sat, 24 May 2008 03:38:18 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id E2A5F8FC0C for ; Sat, 24 May 2008 03:38:17 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAIQqN0iC1Apk/2dsb2JhbACuVw Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 23 May 2008 20:38:17 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052320381565-1052 ; Fri, 23 May 2008 20:38:15 -0700 Date: Fri, 23 May 2008 20:38:15 -0700 (PDT) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 20:38:15, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 20:38:16, Serialize complete at 05/23/2008 20:38:16 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: kldxref oh oh 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, 24 May 2008 03:38:18 -0000 kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kv_bsd# *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 03:39:12 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46DD81065671 for ; Sat, 24 May 2008 03:39:12 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id 1BA568FC21 for ; Sat, 24 May 2008 03:39:12 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAIQqN0iC1Apk/2dsb2JhbACuVw Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 23 May 2008 20:39:11 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052320390980-1053 ; Fri, 23 May 2008 20:39:09 -0700 Date: Fri, 23 May 2008 20:39:10 -0700 (PDT) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 20:39:09, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/23/2008 20:39:10, Serialize complete at 05/23/2008 20:39:10 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: kldxref oh oh 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, 24 May 2008 03:39:12 -0000 On Fri, 23 May 2008, KAYVEN RIESE wrote: > > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked ref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kv_bsd#make kernel -------------------------------------------------------------- >>> Kernel build for GENERIC started on Fri May 23 20:38:21 PDT 2008 -------------------------------------------------------------- ===> GENERIC mkdir -p /usr/obj/usr/src/sys -------------------------------------------------------------- >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/GENERIC /usr/src/sys/i386/conf/GENERIC Kernel build directory is /usr/obj/usr/src/sys/GENERIC Don't forget to do ``make cleandepend && make depend'' -------------------------------------------------------------- >>> stage 2.1: cleaning up the object tree > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kv_bsd# > > > *----------------------------------------------------------* > Kayven Riese, BSCS, MS (Physiology and Biophysics) > (415) 902 5513 cellular > http://kayve.net > Webmaster http://ChessYoga.org > *----------------------------------------------------------* > _______________________________________________ > 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" > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 03:50:04 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41908106564A for ; Sat, 24 May 2008 03:50:04 +0000 (UTC) (envelope-from frase@frase.id.au) Received: from mail4.tpgi.com.au (smtp-out4.tpgi.com.au [220.244.226.114]) by mx1.freebsd.org (Postfix) with ESMTP id 6C2E08FC16 for ; Sat, 24 May 2008 03:50:03 +0000 (UTC) (envelope-from frase@frase.id.au) X-TPG-Antivirus: Passed Received: from [192.168.36.100] (203-219-142-174.static.tpgi.com.au [203.219.142.174]) by mail4.tpgi.com.au (envelope-from frase@frase.id.au) (8.14.2/8.14.2) with ESMTP id m4O3cBax004987 for ; Sat, 24 May 2008 13:38:13 +1000 Message-ID: <48378DA0.8040506@frase.id.au> Date: Sat, 24 May 2008 13:38:08 +1000 From: Fraser Tweedale User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8F5ED75A9E497ADE4D8385F5" Subject: temporary freezes when pressing capslock / numlock 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, 24 May 2008 03:50:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8F5ED75A9E497ADE4D8385F5 Content-Type: multipart/mixed; boundary="------------030801090505020604080900" This is a multi-part message in MIME format. --------------030801090505020604080900 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Since upgrading to RELENG_7_0 I was experiencing momentary freezes (of=20 about .5 seconds) whenever the capslock or numlock buttons were pressed. I would probably never have noticed it except for the strange noises=20 produced when music is playing, and of course that is when it is the=20 most annoying ;) The issue occurs both in console and in X, and for both ULE and 4BSD.=20 The problem was reproducible with USB keyboards only (ukbd); atkbd seems = fine. It also occurs when numlockx is used to set numlock on or off=20 without keyboard interaction. Interestingly, if you add enough keyboards, the problem vanishes, which=20 led me to kbdmux. Sure enough, removing device kbdmux from the kernel=20 makes the problem go away (at the expensive of some functionality of=20 course, but this is my current workaround). Kernel config and dmesg are attached. As you may notice, I enabled=20 kernel lock profiling for the purpose of troubleshooting this issue. I=20 recorded the stats over a single occurance of the glitch. It seems to=20 spend a vast amount of time waiting on giant as compared to any other=20 lock. The output is almost 100k so I've omitted it for now; if it is of = use to anyone let me know and I will certainly include it in reply. Fraser --------------030801090505020604080900 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="dmesg" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDggVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0 IChjKSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAx OTkzLCAxOTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlh LiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1h cmsgb2YgVGhlIEZyZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCA3LjAtUkVMRUFTRS1wMSAj MzA6IEZyaSBNYXkgMjMgMjM6MDQ6NTUgRVNUIDIwMDgKICAgIEZyYXNlckBmb286L3Vzci9v YmovdXNyL3NyYy9zeXMvQ1VTVE9NClRpbWVjb3VudGVyICJpODI1NCIgZnJlcXVlbmN5IDEx OTMxODIgSHogcXVhbGl0eSAwCkNQVTogSW50ZWwoUikgQ29yZShUTSkyIER1byBDUFUgICAg IEU4MjAwICBAIDIuNjZHSHogKDI2NjkuMzQtTUh6IDY4Ni1jbGFzcyBDUFUpCiAgT3JpZ2lu ID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHgxMDY3NiAgU3RlcHBpbmcgPSA2CiAgRmVhdHVy ZXM9MHhiZmViZmJmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LEFQSUMs U0VQLE1UUlIsUEdFLE1DQSxDTU9WLFBBVCxQU0UzNixDTEZMVVNILERUUyxBQ1BJLE1NWCxG WFNSLFNTRSxTU0UyLFNTLEhUVCxUTSxQQkU+CiAgRmVhdHVyZXMyPTB4OGUzZmQ8U1NFMyxS U1ZEMixNT04sRFNfQ1BMLFZNWCxTTVgsRVNULFRNMixTU1NFMyxDWDE2LHhUUFIsUERDTSw8 YjE5Pj4KICBBTUQgRmVhdHVyZXM9MHgyMDEwMDAwMDxOWCxMTT4KICBBTUQgRmVhdHVyZXMy PTB4MTxMQUhGPgogIENvcmVzIHBlciBwYWNrYWdlOiAyCnJlYWwgbWVtb3J5ICA9IDIxNDYz MDQwMDAgKDIwNDYgTUIpCmF2YWlsIG1lbW9yeSA9IDIwOTQ3MTQ4ODAgKDE5OTcgTUIpCkFD UEkgQVBJQyBUYWJsZTogPEdCVCAgICBHQlRVQUNQST4KRnJlZUJTRC9TTVA6IE11bHRpcHJv Y2Vzc29yIFN5c3RlbSBEZXRlY3RlZDogMiBDUFVzCiBjcHUwIChCU1ApOiBBUElDIElEOiAg MAogY3B1MSAoQVApOiBBUElDIElEOiAgMQppb2FwaWMwOiBDaGFuZ2luZyBBUElDIElEIHRv IDIKaW9hcGljMCA8VmVyc2lvbiAyLjA+IGlycXMgMC0yMyBvbiBtb3RoZXJib2FyZAprYmQx IGF0IGtiZG11eDAKYWNwaTA6IDxHQlQgR0JUVUFDUEk+IG9uIG1vdGhlcmJvYXJkCmFjcGkw OiBbSVRIUkVBRF0KYWNwaTA6IFBvd2VyIEJ1dHRvbiAoZml4ZWQpCmFjcGkwOiByZXNlcnZh dGlvbiBvZiAwLCBhMDAwMCAoMykgZmFpbGVkCmFjcGkwOiByZXNlcnZhdGlvbiBvZiAxMDAw MDAsIDdmZGUwMDAwICgzKSBmYWlsZWQKVGltZWNvdW50ZXIgIkFDUEktZmFzdCIgZnJlcXVl bmN5IDM1Nzk1NDUgSHogcXVhbGl0eSAxMDAwCmFjcGlfdGltZXIwOiA8MjQtYml0IHRpbWVy IGF0IDMuNTc5NTQ1TUh6PiBwb3J0IDB4NDA4LTB4NDBiIG9uIGFjcGkwCmFjcGlfaHBldDA6 IDxIaWdoIFByZWNpc2lvbiBFdmVudCBUaW1lcj4gaW9tZW0gMHhmZWQwMDAwMC0weGZlZDAw M2ZmIG9uIGFjcGkwClRpbWVjb3VudGVyICJIUEVUIiBmcmVxdWVuY3kgMTQzMTgxODAgSHog cXVhbGl0eSA5MDAKY3B1MDogPEFDUEkgQ1BVPiBvbiBhY3BpMAphY3BpX3BlcmYwOiA8QUNQ SSBDUFUgRnJlcXVlbmN5IENvbnRyb2w+IG9uIGNwdTAKcDR0Y2MwOiA8Q1BVIEZyZXF1ZW5j eSBUaGVybWFsIENvbnRyb2w+IG9uIGNwdTAKY3B1MTogPEFDUEkgQ1BVPiBvbiBhY3BpMApl c3QxOiA8RW5oYW5jZWQgU3BlZWRTdGVwIEZyZXF1ZW5jeSBDb250cm9sPiBvbiBjcHUxCmVz dDogQ1BVIHN1cHBvcnRzIEVuaGFuY2VkIFNwZWVkc3RlcCwgYnV0IGlzIG5vdCByZWNvZ25p emVkLgplc3Q6IGNwdV92ZW5kb3IgR2VudWluZUludGVsLCBtc3IgNjFhMDgyMDA2MDAwODIw CmRldmljZV9hdHRhY2g6IGVzdDEgYXR0YWNoIHJldHVybmVkIDYKcDR0Y2MxOiA8Q1BVIEZy ZXF1ZW5jeSBUaGVybWFsIENvbnRyb2w+IG9uIGNwdTEKYWNwaV9idXR0b24wOiA8UG93ZXIg QnV0dG9uPiBvbiBhY3BpMApwY2liMDogPEFDUEkgSG9zdC1QQ0kgYnJpZGdlPiBwb3J0IDB4 Y2Y4LTB4Y2ZmIG9uIGFjcGkwCnBjaTA6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIwCnBjaWIx OiA8UENJLVBDSSBicmlkZ2U+IGlycSAxNiBhdCBkZXZpY2UgMS4wIG9uIHBjaTAKcGNpMTog PFBDSSBidXM+IG9uIHBjaWIxCnZnYXBjaTA6IDxWR0EtY29tcGF0aWJsZSBkaXNwbGF5PiBw b3J0IDB4YjAwMC0weGIwN2YgbWVtIDB4ZjYwMDAwMDAtMHhmNmZmZmZmZiwweGUwMDAwMDAw LTB4ZWZmZmZmZmYsMHhmNDAwMDAwMC0weGY1ZmZmZmZmIGlycSAxNiBhdCBkZXZpY2UgMC4w IG9uIHBjaTEKdWhjaTA6IDxVSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gcG9ydCAw eGUxMDAtMHhlMTFmIGlycSAxNiBhdCBkZXZpY2UgMjYuMCBvbiBwY2kwCnVoY2kwOiBbR0lB TlQtTE9DS0VEXQp1aGNpMDogW0lUSFJFQURdCnVzYjA6IDxVSENJIChnZW5lcmljKSBVU0Ig Y29udHJvbGxlcj4gb24gdWhjaTAKdXNiMDogVVNCIHJldmlzaW9uIDEuMAp1aHViMDogPElu dGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxPiBv biB1c2IwCnVodWIwOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1 aGNpMTogPFVIQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVyPiBwb3J0IDB4ZTUwMC0weGU1 MWYgaXJxIDIxIGF0IGRldmljZSAyNi4xIG9uIHBjaTAKdWhjaTE6IFtHSUFOVC1MT0NLRURd CnVoY2kxOiBbSVRIUkVBRF0KdXNiMTogPFVIQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVy PiBvbiB1aGNpMQp1c2IxOiBVU0IgcmV2aXNpb24gMS4wCnVodWIxOiA8SW50ZWwgVUhDSSBy b290IGh1YiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYjEKdWh1 YjE6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkCnVoY2kyOiA8VUhD SSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhlMDAwLTB4ZTAxZiBpcnEgMTgg YXQgZGV2aWNlIDI2LjIgb24gcGNpMAp1aGNpMjogW0dJQU5ULUxPQ0tFRF0KdWhjaTI6IFtJ VEhSRUFEXQp1c2IyOiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG9uIHVoY2ky CnVzYjI6IFVTQiByZXZpc2lvbiAxLjAKdWh1YjI6IDxJbnRlbCBVSENJIHJvb3QgaHViLCBj bGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMT4gb24gdXNiMgp1aHViMjogMiBwb3J0 cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKZWhjaTA6IDxFSENJIChnZW5lcmlj KSBVU0IgMi4wIGNvbnRyb2xsZXI+IG1lbSAweGZhMTAxMDAwLTB4ZmExMDEzZmYgaXJxIDE4 IGF0IGRldmljZSAyNi43IG9uIHBjaTAKZWhjaTA6IFtHSUFOVC1MT0NLRURdCmVoY2kwOiBb SVRIUkVBRF0KdXNiMzogRUhDSSB2ZXJzaW9uIDEuMAp1c2IzOiBjb21wYW5pb24gY29udHJv bGxlcnMsIDIgcG9ydHMgZWFjaDogdXNiMCB1c2IxIHVzYjIKdXNiMzogPEVIQ0kgKGdlbmVy aWMpIFVTQiAyLjAgY29udHJvbGxlcj4gb24gZWhjaTAKdXNiMzogVVNCIHJldmlzaW9uIDIu MAp1aHViMzogPEludGVsIEVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDIuMDAvMS4w MCwgYWRkciAxPiBvbiB1c2IzCnVodWIzOiA2IHBvcnRzIHdpdGggNiByZW1vdmFibGUsIHNl bGYgcG93ZXJlZApwY2liMjogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGlycSAxNiBhdCBkZXZp Y2UgMjguMCBvbiBwY2kwCnBjaTI6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIyCnBjaWIzOiA8 QUNQSSBQQ0ktUENJIGJyaWRnZT4gaXJxIDE5IGF0IGRldmljZSAyOC4zIG9uIHBjaTAKcGNp MzogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjMKcGNpYjQ6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdl PiBpcnEgMTYgYXQgZGV2aWNlIDI4LjQgb24gcGNpMApwY2k0OiA8QUNQSSBQQ0kgYnVzPiBv biBwY2liNApyZTA6IDxSZWFsVGVrIDgxNjgvODExMUIgUENJZSBHaWdhYml0IEV0aGVybmV0 PiBwb3J0IDB4YzAwMC0weGMwZmYgbWVtIDB4ZjkwMDAwMDAtMHhmOTAwMGZmZiBpcnEgMTYg YXQgZGV2aWNlIDAuMCBvbiBwY2k0CnJlMDogVXNpbmcgMiBNU0kgbWVzc2FnZXMKbWlpYnVz MDogPE1JSSBidXM+IG9uIHJlMApyZ2VwaHkwOiA8UlRMODE2OVMvODExMFMvODIxMUIgbWVk aWEgaW50ZXJmYWNlPiBQSFkgMSBvbiBtaWlidXMwCnJnZXBoeTA6ICAxMGJhc2VULCAxMGJh c2VULUZEWCwgMTAwYmFzZVRYLCAxMDBiYXNlVFgtRkRYLCAxMDAwYmFzZVQsIDEwMDBiYXNl VC1GRFgsIGF1dG8KcmUwOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDoxZDo3ZDowMToxNjozOQpy ZTA6IFtGSUxURVJdCnJlMDogW0ZJTFRFUl0KdWhjaTM6IDxVSENJIChnZW5lcmljKSBVU0Ig Y29udHJvbGxlcj4gcG9ydCAweGUyMDAtMHhlMjFmIGlycSAyMyBhdCBkZXZpY2UgMjkuMCBv biBwY2kwCnVoY2kzOiBbR0lBTlQtTE9DS0VEXQp1aGNpMzogW0lUSFJFQURdCnVzYjQ6IDxV SENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gb24gdWhjaTMKdXNiNDogVVNCIHJldmlz aW9uIDEuMAp1aHViNDogPEludGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEu MDAvMS4wMCwgYWRkciAxPiBvbiB1c2I0CnVodWI0OiAyIHBvcnRzIHdpdGggMiByZW1vdmFi bGUsIHNlbGYgcG93ZXJlZAp1aGNpNDogPFVIQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVy PiBwb3J0IDB4ZTMwMC0weGUzMWYgaXJxIDE5IGF0IGRldmljZSAyOS4xIG9uIHBjaTAKdWhj aTQ6IFtHSUFOVC1MT0NLRURdCnVoY2k0OiBbSVRIUkVBRF0KdXNiNTogPFVIQ0kgKGdlbmVy aWMpIFVTQiBjb250cm9sbGVyPiBvbiB1aGNpNAp1c2I1OiBVU0IgcmV2aXNpb24gMS4wCnVo dWI1OiA8SW50ZWwgVUhDSSByb290IGh1YiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBh ZGRyIDE+IG9uIHVzYjUKdWh1YjU6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBw b3dlcmVkCnVoY2k1OiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhl NDAwLTB4ZTQxZiBpcnEgMTggYXQgZGV2aWNlIDI5LjIgb24gcGNpMAp1aGNpNTogW0dJQU5U LUxPQ0tFRF0KdWhjaTU6IFtJVEhSRUFEXQp1c2I2OiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNv bnRyb2xsZXI+IG9uIHVoY2k1CnVzYjY6IFVTQiByZXZpc2lvbiAxLjAKdWh1YjY6IDxJbnRl bCBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMT4gb24g dXNiNgp1aHViNjogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKZWhj aTE6IDxFSENJIChnZW5lcmljKSBVU0IgMi4wIGNvbnRyb2xsZXI+IG1lbSAweGZhMTAwMDAw LTB4ZmExMDAzZmYgaXJxIDIzIGF0IGRldmljZSAyOS43IG9uIHBjaTAKZWhjaTE6IFtHSUFO VC1MT0NLRURdCmVoY2kxOiBbSVRIUkVBRF0KdXNiNzogRUhDSSB2ZXJzaW9uIDEuMAp1c2I3 OiBjb21wYW5pb24gY29udHJvbGxlcnMsIDIgcG9ydHMgZWFjaDogdXNiNCB1c2I1IHVzYjYK dXNiNzogPEVIQ0kgKGdlbmVyaWMpIFVTQiAyLjAgY29udHJvbGxlcj4gb24gZWhjaTEKdXNi NzogVVNCIHJldmlzaW9uIDIuMAp1aHViNzogPEludGVsIEVIQ0kgcm9vdCBodWIsIGNsYXNz IDkvMCwgcmV2IDIuMDAvMS4wMCwgYWRkciAxPiBvbiB1c2I3CnVodWI3OiA2IHBvcnRzIHdp dGggNiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1aHViODogPHZlbmRvciAweDA1YWMgcHJv ZHVjdCAweDEwMDYsIGNsYXNzIDkvMCwgcmV2IDIuMDAvOTUuMTUsIGFkZHIgMj4gb24gdWh1 YjcKdWh1Yjg6IHNpbmdsZSB0cmFuc2FjdGlvbiB0cmFuc2xhdG9yCmRldmljZV9hdHRhY2g6 IHVodWI4IGF0dGFjaCByZXR1cm5lZCA2CnVodWI3OiBwb3J0IDYsIHNldCBjb25maWcgYXQg YWRkciAyIGZhaWxlZAp1aHViNzogZGV2aWNlIHByb2JsZW0gKFRJTUVPVVQpLCBkaXNhYmxp bmcgcG9ydCA2CnBjaWI1OiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDMwLjAg b24gcGNpMApwY2k1OiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liNQplbXUxMGt4MDogPENyZWF0 aXZlIEF1ZGlneSAyIFpTIFtTQjAzNTBdPiBwb3J0IDB4ZDAwMC0weGQwM2YgaXJxIDE4IGF0 IGRldmljZSAyLjAgb24gcGNpNQplbXUxMGt4MDogW0lUSFJFQURdCnBjbTA6IDxFTVUxMEt4 IERTUCBmcm9udCBQQ00gaW50ZXJmYWNlPiBvbiBlbXUxMGt4MApwY20wOiA8U2lnbWFUZWwg U1RBQzk3MjEvMjMgQUM5NyBDb2RlYz4KcGNtMTogPEVNVTEwS3ggRFNQIHJlYXIgUENNIGlu dGVyZmFjZT4gb24gZW11MTBreDAKcGNtMjogPEVNVTEwS3ggRFNQIGNlbnRlciBQQ00gaW50 ZXJmYWNlPiBvbiBlbXUxMGt4MApwY20zOiA8RU1VMTBLeCBEU1Agc3Vid29vZmVyIFBDTSBp bnRlcmZhY2U+IG9uIGVtdTEwa3gwCnBjbTQ6IDxFTVUxMEt4IERTUCBzaWRlIFBDTSBpbnRl cmZhY2U+IG9uIGVtdTEwa3gwCnBjaTU6IDxpbnB1dCBkZXZpY2U+IGF0IGRldmljZSAyLjEg KG5vIGRyaXZlciBhdHRhY2hlZCkKcGNpNTogPHNlcmlhbCBidXMsIEZpcmVXaXJlPiBhdCBk ZXZpY2UgMi4yIChubyBkcml2ZXIgYXR0YWNoZWQpCmlzYWIwOiA8UENJLUlTQSBicmlkZ2U+ IGF0IGRldmljZSAzMS4wIG9uIHBjaTAKaXNhMDogPElTQSBidXM+IG9uIGlzYWIwCmF0YXBj aTA6IDxJbnRlbCBJQ0g5IFNBVEEzMDAgY29udHJvbGxlcj4gcG9ydCAweDFmMC0weDFmNyww eDNmNiwweDE3MC0weDE3NywweDM3NiwweGYwMDAtMHhmMDBmLDB4ZmMwMC0weGZjMGYgYXQg ZGV2aWNlIDMxLjIgb24gcGNpMAphdGEwOiA8QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNpMAph dGEwOiBbSVRIUkVBRF0KYXRhMTogPEFUQSBjaGFubmVsIDE+IG9uIGF0YXBjaTAKYXRhMTog W0lUSFJFQURdCnBjaTA6IDxzZXJpYWwgYnVzLCBTTUJ1cz4gYXQgZGV2aWNlIDMxLjMgKG5v IGRyaXZlciBhdHRhY2hlZCkKYXRhcGNpMTogPEludGVsIElDSDkgU0FUQTMwMCBjb250cm9s bGVyPiBwb3J0IDB4ZTcwMC0weGU3MDcsMHhlODAwLTB4ZTgwMywweGU5MDAtMHhlOTA3LDB4 ZWEwMC0weGVhMDMsMHhlYjAwLTB4ZWIwZiwweGVjMDAtMHhlYzBmIGlycSAxOSBhdCBkZXZp Y2UgMzEuNSBvbiBwY2kwCmF0YXBjaTE6IFtJVEhSRUFEXQphdGEyOiA8QVRBIGNoYW5uZWwg MD4gb24gYXRhcGNpMQphdGEyOiBbSVRIUkVBRF0KYXRhMzogPEFUQSBjaGFubmVsIDE+IG9u IGF0YXBjaTEKYXRhMzogW0lUSFJFQURdCnBtdGltZXIwIG9uIGlzYTAKc2MwOiA8U3lzdGVt IGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTAKc2MwOiBWR0EgPDE2IHZpcnR1YWwg Y29uc29sZXMsIGZsYWdzPTB4MzAwPgp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0 IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwCmF0a2JkYzA6IDxL ZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+IGF0IHBvcnQgMHg2MCwweDY0IG9uIGlzYTAK YXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGlycSAxIG9uIGF0a2JkYzAKa2JkMCBhdCBhdGtiZDAK YXRrYmQwOiBbR0lBTlQtTE9DS0VEXQphdGtiZDA6IFtJVEhSRUFEXQp1bXMwOiA8QjE2X2Jf MDIgVVNCLVBTLzIgT3B0aWNhbCBNb3VzZSwgY2xhc3MgMC8wLCByZXYgMi4wMC85OC4wMiwg YWRkciAyPiBvbiB1aHViNgp1bXMwOiA4IGJ1dHRvbnMgYW5kIFogZGlyLgpUaW1lY291bnRl cnMgdGljayBldmVyeSAxLjAwMCBtc2VjCmFkMDogNzYzMTlNQiA8U2VhZ2F0ZSBTVDM4MDgx N0FTIDMuNDI+IGF0IGF0YTAtbWFzdGVyIFNBVEExNTAKYWQxOiAyMzg0NzVNQiA8U2VhZ2F0 ZSBTVDMyNTA0MTBBUyAzLkFBQz4gYXQgYXRhMC1zbGF2ZSBTQVRBMTUwClNNUDogQVAgQ1BV ICMxIExhdW5jaGVkIQpUcnlpbmcgdG8gbW91bnQgcm9vdCBmcm9tIHVmczovZGV2L2FkMHMx YQp1bmtub3duOiBGQUlMVVJFIC0gSU5RVUlSWSBJTExFR0FMIFJFUVVFU1QgYXNjPTB4MjQg YXNjcT0weDAwIHNrcz0weDQ4IDB4MDAgMHgwMQpjZDAgYXQgYXRhMiBidXMgMCB0YXJnZXQg MCBsdW4gMApjZDA6IDxQSU9ORUVSIERWRC1SVyAgRFZSLTIxNSAxLjA2PiBSZW1vdmFibGUg Q0QtUk9NIFNDU0ktMCBkZXZpY2UgCmNkMDogMy4zMDBNQi9zIHRyYW5zZmVycwpjZDA6IEF0 dGVtcHQgdG8gcXVlcnkgZGV2aWNlIHNpemUgZmFpbGVkOiBOT1QgUkVBRFksIE1lZGl1bSBu b3QgcHJlc2VudAp1aHViOTogPEFwcGxlLCBJbmMuIEtleWJvYXJkIEh1YiwgY2xhc3MgOS8w LCByZXYgMi4wMC85NS4xNSwgYWRkciAyPiBvbiB1aHViNwp1aHViOTogc2luZ2xlIHRyYW5z YWN0aW9uIHRyYW5zbGF0b3IKdWh1Yjk6IDMgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgYnVz IHBvd2VyZWQKdWtiZDA6IDxBcHBsZSwgSW5jIEFwcGxlIEtleWJvYXJkLCBjbGFzcyAwLzAs IHJldiAyLjAwLzAuNjcsIGFkZHIgMz4gb24gdWh1YjkKa2JkMiBhdCB1a2JkMAp1aGlkMDog PEFwcGxlLCBJbmMgQXBwbGUgS2V5Ym9hcmQsIGNsYXNzIDAvMCwgcmV2IDIuMDAvMC42Nywg YWRkciAzPiBvbiB1aHViOQo= --------------030801090505020604080900 Content-Type: text/plain; name="kernconf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="kernconf" IyBhdG9tc2tic2Qga2VybmVsIGNvbmZpZ3VyYXRpb24KCm1hY2hpbmUJCWkzODYKY3B1CQlJ Njg2X0NQVQppZGVudAkJQ1VTVE9NCgojIFRvIHN0YXRpY2FsbHkgY29tcGlsZSBpbiBkZXZp Y2Ugd2lyaW5nIGluc3RlYWQgb2YgL2Jvb3QvZGV2aWNlLmhpbnRzCiNoaW50cwkJIkdFTkVS SUMuaGludHMiCQkjIERlZmF1bHQgcGxhY2VzIHRvIGxvb2sgZm9yIGRldmljZXMuCgptYWtl b3B0aW9ucwlERUJVRz0tZwkJIyBCdWlsZCBrZXJuZWwgd2l0aCBnZGIoMSkgZGVidWcgc3lt Ym9scwpvcHRpb25zIAlMT0NLX1BST0ZJTElORwoKb3B0aW9ucyAJU0NIRURfNEJTRAkJIyA0 QlNEIHNjaGVkdWxlcgojb3B0aW9ucyAJU0NIRURfVUxFCm9wdGlvbnMgCVBSRUVNUFRJT04J CSMgRW5hYmxlIGtlcm5lbCB0aHJlYWQgcHJlZW1wdGlvbgpvcHRpb25zIAlJTkVUCQkJIyBJ bnRlck5FVHdvcmtpbmcKb3B0aW9ucwkJSU5FVDYgICAgICAgICAgIAkjIElQdjYgY29tbXVu aWNhdGlvbnMgcHJvdG9jb2xzCm9wdGlvbnMgCVNDVFAJCQkjIFN0cmVhbSBDb250cm9sIFRy YW5zbWlzc2lvbiBQcm90b2NvbApvcHRpb25zIAlGRlMJCQkjIEJlcmtlbGV5IEZhc3QgRmls ZXN5c3RlbQpvcHRpb25zIAlTT0ZUVVBEQVRFUwkJIyBFbmFibGUgRkZTIHNvZnQgdXBkYXRl cyBzdXBwb3J0Cm9wdGlvbnMgCVVGU19BQ0wJCQkjIFN1cHBvcnQgZm9yIGFjY2VzcyBjb250 cm9sIGxpc3RzCm9wdGlvbnMgCVVGU19ESVJIQVNICQkjIEltcHJvdmUgcGVyZm9ybWFuY2Ug b24gYmlnIGRpcmVjdG9yaWVzCm9wdGlvbnMgCVVGU19HSk9VUk5BTAkJIyBFbmFibGUgZ2pv dXJuYWwtYmFzZWQgVUZTIGpvdXJuYWxpbmcKb3B0aW9ucyAJTURfUk9PVAkJCSMgTUQgaXMg YSBwb3RlbnRpYWwgcm9vdCBkZXZpY2UKb3B0aW9ucwkJTkZTQ0xJRU5UICAgICAgIAkjIE5l dHdvcmsgRmlsZXN5c3RlbSBDbGllbnQKI29wdGlvbnMgCU5GU1NFUlZFUgkJIyBOZXR3b3Jr IEZpbGVzeXN0ZW0gU2VydmVyCiNvcHRpb25zIAlORlNfUk9PVAkJIyBORlMgdXNhYmxlIGFz IC8sIHJlcXVpcmVzIE5GU0NMSUVOVApvcHRpb25zIAlNU0RPU0ZTCQkJIyBNU0RPUyBGaWxl c3lzdGVtCm9wdGlvbnMgCUNEOTY2MAkJCSMgSVNPIDk2NjAgRmlsZXN5c3RlbQpvcHRpb25z IAlQUk9DRlMJCQkjIFByb2Nlc3MgZmlsZXN5c3RlbSAocmVxdWlyZXMgUFNFVURPRlMpCm9w dGlvbnMgCVBTRVVET0ZTCQkjIFBzZXVkby1maWxlc3lzdGVtIGZyYW1ld29yawpvcHRpb25z IAlHRU9NX1BBUlRfR1BUCQkjIEdVSUQgUGFydGl0aW9uIFRhYmxlcy4Kb3B0aW9ucyAJR0VP TV9MQUJFTAkJIyBQcm92aWRlcyBsYWJlbGl6YXRpb24Kb3B0aW9ucyAJQ09NUEFUXzQzVFRZ CQkjIEJTRCA0LjMgVFRZIGNvbXBhdCBbS0VFUCBUSElTIV0KI29wdGlvbnMgCUNPTVBBVF9G UkVFQlNENAkJIyBDb21wYXRpYmxlIHdpdGggRnJlZUJTRDQKb3B0aW9ucyAJQ09NUEFUX0ZS RUVCU0Q1CQkjIENvbXBhdGlibGUgd2l0aCBGcmVlQlNENQpvcHRpb25zIAlDT01QQVRfRlJF RUJTRDYJCSMgQ29tcGF0aWJsZSB3aXRoIEZyZWVCU0Q2Cm9wdGlvbnMgCVNDU0lfREVMQVk9 NTAwMAkJIyBEZWxheSAoaW4gbXMpIGJlZm9yZSBwcm9iaW5nIFNDU0kKb3B0aW9ucyAJS1RS QUNFCQkJIyBrdHJhY2UoMSkgc3VwcG9ydApvcHRpb25zIAlTWVNWU0hNCQkJIyBTWVNWLXN0 eWxlIHNoYXJlZCBtZW1vcnkKb3B0aW9ucyAJU1lTVk1TRwkJCSMgU1lTVi1zdHlsZSBtZXNz YWdlIHF1ZXVlcwpvcHRpb25zIAlTWVNWU0VNCQkJIyBTWVNWLXN0eWxlIHNlbWFwaG9yZXMK b3B0aW9ucyAJX0tQT1NJWF9QUklPUklUWV9TQ0hFRFVMSU5HICMgUE9TSVggUDEwMDNfMUIg cmVhbC10aW1lIGV4dGVuc2lvbnMKb3B0aW9ucyAJS0JEX0lOU1RBTExfQ0RFVgkjIGluc3Rh bGwgYSBDREVWIGVudHJ5IGluIC9kZXYKb3B0aW9ucyAJQURBUFRJVkVfR0lBTlQJCSMgR2lh bnQgbXV0ZXggaXMgYWRhcHRpdmUuCm9wdGlvbnMgCVNUT1BfTk1JCQkjIFN0b3AgQ1BVUyB1 c2luZyBOTUkgaW5zdGVhZCBvZiBJUEkKb3B0aW9ucyAJQVVESVQJCQkjIFNlY3VyaXR5IGV2 ZW50IGF1ZGl0aW5nCgojIFRvIG1ha2UgYW4gU01QIGtlcm5lbCwgdGhlIG5leHQgdHdvIGxp bmVzIGFyZSBuZWVkZWQKb3B0aW9ucwkJU01QCmRldmljZQkJYXBpYwkJCSMgSS9PIEFQSUMK CiMgQ1BVIGZyZXF1ZW5jeSBjb250cm9sCmRldmljZQkJY3B1ZnJlcQoKIyBCdXMgc3VwcG9y dC4KZGV2aWNlCQllaXNhCmRldmljZQkJcGNpCgojIEFUQSBhbmQgQVRBUEkgZGV2aWNlcwpk ZXZpY2UJCWF0YQpkZXZpY2UJCWF0YWRpc2sJCSMgQVRBIGRpc2sgZHJpdmVzCiNkZXZpY2UJ CWF0YXBpY2QJCSMgQVRBUEkgQ0RST00gZHJpdmVzCm9wdGlvbnMgCUFUQV9TVEFUSUNfSUQJ IyBTdGF0aWMgZGV2aWNlIG51bWJlcmluZwoKIyBTQ1NJIHBlcmlwaGVyYWxzCmRldmljZQkJ c2NidXMJCSMgU0NTSSBidXMgKHJlcXVpcmVkIGZvciBTQ1NJKQpkZXZpY2UJCWRhCQkjIERp cmVjdCBBY2Nlc3MgKGRpc2tzKQpkZXZpY2UJCWNkCQkjIENECmRldmljZQkJcGFzcwkJIyBQ YXNzdGhyb3VnaCBkZXZpY2UgKGRpcmVjdCBTQ1NJIGFjY2VzcykKZGV2aWNlCQlhdGFwaWNh bQoKIyBhdGtiZGMwIGNvbnRyb2xzIGJvdGggdGhlIGtleWJvYXJkIGFuZCB0aGUgUFMvMiBt b3VzZQpkZXZpY2UJCWF0a2JkYwkJIyBBVCBrZXlib2FyZCBjb250cm9sbGVyCmRldmljZQkJ YXRrYmQJCSMgQVQga2V5Ym9hcmQKZGV2aWNlCQlwc20JCSMgUFMvMiBtb3VzZQoKZGV2aWNl CQlrYmRtdXgJCSMga2V5Ym9hcmQgbXVsdGlwbGV4ZXIKCmRldmljZSAJCXZnYQkJIyBWR0Eg dmlkZW8gY2FyZCBkcml2ZXIKCmRldmljZQkJc3BsYXNoCQkjIFNwbGFzaCBzY3JlZW4gYW5k IHNjcmVlbiBzYXZlciBzdXBwb3J0CgojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQgY29uc29s ZSBkcml2ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUKZGV2aWNlCQlzYwoKZGV2aWNl CQlhZ3AJCSMgc3VwcG9ydCBzZXZlcmFsIEFHUCBjaGlwc2V0cwoKIyBQb3dlciBtYW5hZ2Vt ZW50IHN1cHBvcnQgKHNlZSBOT1RFUyBmb3IgbW9yZSBvcHRpb25zKQojZGV2aWNlCQlhcG0K IyBBZGQgc3VzcGVuZC9yZXN1bWUgc3VwcG9ydCBmb3IgdGhlIGk4MjU0LgpkZXZpY2UJCXBt dGltZXIKCiMgUENJIEV0aGVybmV0IE5JQ3MgdGhhdCB1c2UgdGhlIGNvbW1vbiBNSUkgYnVz IGNvbnRyb2xsZXIgY29kZS4KIyBOT1RFOiBCZSBzdXJlIHRvIGtlZXAgdGhlICdkZXZpY2Ug bWlpYnVzJyBsaW5lIGluIG9yZGVyIHRvIHVzZSB0aGVzZSBOSUNzIQpkZXZpY2UJCW1paWJ1 cwkJIyBNSUkgYnVzIHN1cHBvcnQKI2RldmljZQkJbmZlCQkjIG5WaWRpYSBuRm9yY2UgTUNQ IG9uLWJvYXJkIEV0aGVybmV0CiNkZXZpY2UJCW52ZQkJIyBuVmlkaWEgbkZvcmNlIE1DUCBv bi1ib2FyZCBFdGhlcm5ldCBOZXR3b3JraW5nCmRldmljZQkJcmUJCSMgUmVhbFRlayA4MTM5 QysvODE2OS84MTY5Uy84MTEwUwojZGV2aWNlCQlybAkJIyBSZWFsVGVrIDgxMjkvODEzOQoj ZGV2aWNlCQlzaXMJCSMgU2lsaWNvbiBJbnRlZ3JhdGVkIFN5c3RlbXMgU2lTIDkwMC9TaVMg NzAxNgojZGV2aWNlCQlzawkJIyBTeXNLb25uZWN0IFNLLTk4NHggJiBTSy05ODJ4IGdpZ2Fi aXQgRXRoZXJuZXQKCiMgUHNldWRvIGRldmljZXMuCmRldmljZQkJbG9vcAkJIyBOZXR3b3Jr IGxvb3BiYWNrCmRldmljZQkJcmFuZG9tCQkjIEVudHJvcHkgZGV2aWNlCmRldmljZQkJZXRo ZXIJCSMgRXRoZXJuZXQgc3VwcG9ydAojZGV2aWNlCQlzbAkJIyBLZXJuZWwgU0xJUAojZGV2 aWNlCQlwcHAJCSMgS2VybmVsIFBQUApkZXZpY2UJCXR1bgkJIyBQYWNrZXQgdHVubmVsLgpk ZXZpY2UJCXB0eQkJIyBQc2V1ZG8tdHR5cyAodGVsbmV0IGV0YykKZGV2aWNlCQltZAkJIyBN ZW1vcnkgImRpc2tzIgojZGV2aWNlCQlnaWYJCSMgSVB2NiBhbmQgSVB2NCB0dW5uZWxpbmcK I2RldmljZQkJZmFpdGgJCSMgSVB2Ni10by1JUHY0IHJlbGF5aW5nICh0cmFuc2xhdGlvbikK ZGV2aWNlCQlmaXJtd2FyZQkjIGZpcm13YXJlIGFzc2lzdCBtb2R1bGUKCiMgVGhlIGBicGYn IGRldmljZSBlbmFibGVzIHRoZSBCZXJrZWxleSBQYWNrZXQgRmlsdGVyLgojIEJlIGF3YXJl IG9mIHRoZSBhZG1pbmlzdHJhdGl2ZSBjb25zZXF1ZW5jZXMgb2YgZW5hYmxpbmcgdGhpcyEK IyBOb3RlIHRoYXQgJ2JwZicgaXMgcmVxdWlyZWQgZm9yIERIQ1AuCmRldmljZQkJYnBmCQkj IEJlcmtlbGV5IHBhY2tldCBmaWx0ZXIKCiMgVVNCIHN1cHBvcnQKZGV2aWNlCQl1aGNpCQkj IFVIQ0kgUENJLT5VU0IgaW50ZXJmYWNlCmRldmljZQkJb2hjaQkJIyBPSENJIFBDSS0+VVNC IGludGVyZmFjZQpkZXZpY2UJCWVoY2kJCSMgRUhDSSBQQ0ktPlVTQiBpbnRlcmZhY2UgKFVT QiAyLjApCmRldmljZQkJdXNiCQkjIFVTQiBCdXMgKHJlcXVpcmVkKQojZGV2aWNlCQl1ZGJw CQkjIFVTQiBEb3VibGUgQnVsayBQaXBlIGRldmljZXMKZGV2aWNlCQl1Z2VuCQkjIEdlbmVy aWMKZGV2aWNlCQl1aGlkCQkjICJIdW1hbiBJbnRlcmZhY2UgRGV2aWNlcyIKZGV2aWNlCQl1 a2JkCQkjIEtleWJvYXJkCmRldmljZQkJdW1hc3MJCSMgRGlza3MvTWFzcyBzdG9yYWdlIC0g UmVxdWlyZXMgc2NidXMgYW5kIGRhCmRldmljZQkJdW1zCQkjIE1vdXNlCgojIFNvdW5kIHN1 cHBvcnQKZGV2aWNlCQlzb3VuZApkZXZpY2UJCXNuZF9lbXUxMGt4Cgo= --------------030801090505020604080900-- --------------enig8F5ED75A9E497ADE4D8385F5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkg3jaMACgkQPw/2FZbemTWT+gCgsEuFw1Ondo46WcZ5jYQxRtll ZREAn1+VrBydVU6724LtagSejbDnkxqj =AAqg -----END PGP SIGNATURE----- --------------enig8F5ED75A9E497ADE4D8385F5-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 13:43:41 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76349106567B for ; Sat, 24 May 2008 13:43:41 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from mxf2.bahnhof.se (mxf2.bahnhof.se [213.80.101.26]) by mx1.freebsd.org (Postfix) with ESMTP id F2D5A8FC23 for ; Sat, 24 May 2008 13:43:40 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from localhost (mxf2.local [127.0.0.1]) by mxf2-reinject (Postfix) with ESMTP id DE1406BD0F7; Sat, 24 May 2008 15:24:24 +0200 (CEST) X-Virus-Scanned: by amavisd-new using ClamAV at bahnhof.se (MXF2) X-Spam-Score: -1.53 X-Spam-Level: X-Spam-Status: No, score=-1.53 tagged_above=-99 required=5 tests=[BAYES_00=-2.599, SPF_NEUTRAL=1.069] Received: from mxf2.bahnhof.se ([127.0.0.1]) by localhost (mxf2.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvktGY15tliU; Sat, 24 May 2008 15:24:22 +0200 (CEST) Received: from [10.0.0.3] (h-79-136-60-153.NA.cust.bahnhof.se [79.136.60.153]) by mxf2.bahnhof.se (Postfix) with ESMTP id 52FC56BD0A6; Sat, 24 May 2008 15:24:22 +0200 (CEST) Message-ID: <4838172B.9050008@gmail.com> Date: Sat, 24 May 2008 15:24:59 +0200 From: Niclas Zeising User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: KAYVEN RIESE 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: kldxref oh oh 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, 24 May 2008 13:43:41 -0000 KAYVEN RIESE wrote: > On Fri, 23 May 2008, KAYVEN RIESE wrote: > >> >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked > > ref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kv_bsd#make kernel > > -------------------------------------------------------------- >>>> Kernel build for GENERIC started on Fri May 23 20:38:21 PDT 2008 > -------------------------------------------------------------- > ===> GENERIC > mkdir -p /usr/obj/usr/src/sys > > -------------------------------------------------------------- >>>> stage 1: configuring the kernel > -------------------------------------------------------------- > cd /usr/src/sys/i386/conf; > PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > config -d /usr/obj/usr/src/sys/GENERIC /usr/src/sys/i386/conf/GENERIC > Kernel build directory is /usr/obj/usr/src/sys/GENERIC > Don't forget to do ``make cleandepend && make depend'' > > -------------------------------------------------------------- >>>> stage 2.1: cleaning up the object tree > > > >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kv_bsd# >> Hi! Please send error reports to freebsd-current@freebsd.org (for current, i. e. 8.0-CURRENT) or freebsd-stable@freebsd.org (for stable, i. e. 5-STABLE, 6-STABLE, 7-STABLE and the various releases) and questions to questions@freebsd.org. Apart from that, that error message shows when upgrading from an old version of FreeBSD (6.x i think) to a newer version (7 or 8). It's as far as I can tell completely harmless. I've seen it before, and my computers haven't malfunctioned yet. Regards! //Niclas From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 19:32:27 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7F53106566B for ; Sat, 24 May 2008 19:32:27 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from kazon.borderworlds.dk (kazon.borderworlds.dk [213.239.213.48]) by mx1.freebsd.org (Postfix) with ESMTP id C1FBA8FC14 for ; Sat, 24 May 2008 19:32:27 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from dominion.borderworlds.dk (localhost [127.0.0.1]) by kazon.borderworlds.dk (Postfix) with ESMTP id 209F61709C; Sat, 24 May 2008 21:15:22 +0200 (CEST) Received: by dominion.borderworlds.dk (Postfix, from userid 2000) id 7894F47B; Sat, 24 May 2008 21:15:21 +0200 (CEST) To: Fraser Tweedale References: <48378DA0.8040506@frase.id.au> From: Christian Laursen Date: Sat, 24 May 2008 21:15:21 +0200 In-Reply-To: <48378DA0.8040506@frase.id.au> (Fraser Tweedale's message of "Sat\, 24 May 2008 13\:38\:08 +1000") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-hackers@freebsd.org Subject: Re: temporary freezes when pressing capslock / numlock 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, 24 May 2008 19:32:28 -0000 Fraser Tweedale writes: > Since upgrading to RELENG_7_0 I was experiencing momentary freezes (of > about .5 seconds) whenever the capslock or numlock buttons were > pressed. I have experienced this too - also on RELENG_7_0. > I would probably never have noticed it except for the strange noises > produced when music is playing, and of course that is when it is the > most annoying ;) Indeed. > The issue occurs both in console and in X, and for both ULE and > 4BSD. The problem was reproducible with USB keyboards only (ukbd); > atkbd seems fine. It also occurs when numlockx is used to set numlock > on or off without keyboard interaction. For me the issue went away when I removed atkbd support from my kernel. I still have ukbd and kbdmux. -- Christian Laursen From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 20:16:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 267D31065672 for ; Sat, 24 May 2008 20:16:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2D57F8FC19 for ; Sat, 24 May 2008 20:16:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E7BAE1CC033; Sat, 24 May 2008 13:16:33 -0700 (PDT) Date: Sat, 24 May 2008 13:16:33 -0700 From: Jeremy Chadwick To: Fraser Tweedale Message-ID: <20080524201633.GA81364@eos.sc1.parodius.com> References: <48378DA0.8040506@frase.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48378DA0.8040506@frase.id.au> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org, m_evmenkin@yahoo.com Subject: Re: temporary freezes when pressing capslock / numlock 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, 24 May 2008 20:16:34 -0000 On Sat, May 24, 2008 at 01:38:08PM +1000, Fraser Tweedale wrote: > Since upgrading to RELENG_7_0 I was experiencing momentary freezes (of > about .5 seconds) whenever the capslock or numlock buttons were pressed. Let me guess -- you're using a USB keyboard. > The issue occurs both in console and in X, and for both ULE and 4BSD. The > problem was reproducible with USB keyboards only (ukbd); atkbd seems fine. > It also occurs when numlockx is used to set numlock on or off without > keyboard interaction. I figured as much. I hadn't checked numlock/capslock myself, but vcons switching also has that problem. Yes, it's semi-documented; see section "USB" below: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues For what it's worth, the systems I've confirmed the problem on are Intel and nForce 4. Meaning, the issue is not specific to a single chipset. > Interestingly, if you add enough keyboards, the problem vanishes, which led > me to kbdmux. Sure enough, removing device kbdmux from the kernel makes > the problem go away (at the expensive of some functionality of course, but > this is my current workaround). An interesting find! I'll add this to the details in the above wiki. I've also CC'd kbdmux's maintainer. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 20:37:52 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A5C81065680 for ; Sat, 24 May 2008 20:37:52 +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 7ACB38FC17 for ; Sat, 24 May 2008 20:37:52 +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 D516546C1D; Sat, 24 May 2008 16:37:51 -0400 (EDT) Date: Sat, 24 May 2008 21:37:51 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: KAYVEN RIESE In-Reply-To: Message-ID: <20080524213732.J9809@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: kldxref oh oh 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, 24 May 2008 20:37:52 -0000 On Fri, 23 May 2008, KAYVEN RIESE wrote: > On Fri, 23 May 2008, KAYVEN RIESE wrote: > >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked > > ref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kv_bsd#make kernel >From the 7.0 errata notes: [20080307] Source upgrades from FreeBSD 6.X to FreeBSD 7.0-RELEASE will generate warnings from kldxref(8) during the installkernel step. These warnings are harmless and can be ignored. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 22:01:55 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E903106564A for ; Sat, 24 May 2008 22:01:55 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 9CD278FC12 for ; Sat, 24 May 2008 22:01:55 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAEEtOEiC1Apk/2dsb2JhbACsSA Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 24 May 2008 15:01:55 -0700 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF378) with ESMTP id 2008052415015329-1065 ; Sat, 24 May 2008 15:01:53 -0700 Date: Sat, 24 May 2008 15:01:53 -0700 (PDT) From: KAYVEN RIESE To: Robert Watson In-Reply-To: <20080524213732.J9809@fledge.watson.org> Message-ID: References: <20080524213732.J9809@fledge.watson.org> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/24/2008 15:01:53, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF378 | February 28, 2008) at 05/24/2008 15:01:54, Serialize complete at 05/24/2008 15:01:54 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: kldxref oh oh 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, 24 May 2008 22:01:55 -0000 On Sat, 24 May 2008, Robert Watson wrote: > On Fri, 23 May 2008, KAYVEN RIESE wrote: >> On Fri, 23 May 2008, KAYVEN RIESE wrote: >> >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kldxref: file isn't dynamically-linked >> kv_bsd#make kernel > >> From the 7.0 errata notes: > > [20080307] Source upgrades from FreeBSD 6.X to FreeBSD 7.0-RELEASE will > generate warnings from kldxref(8) during the installkernel step. These > warnings are harmless and can be ignored. Thank you very much for showing me I should have RTFM in a very nice way. > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > 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" > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 22:36:25 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 317BF1065687 for ; Sat, 24 May 2008 22:36:25 +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 2198F8FC14 for ; Sat, 24 May 2008 22:36:25 +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 5A13446B35; Sat, 24 May 2008 18:36:24 -0400 (EDT) Date: Sat, 24 May 2008 23:36:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: KAYVEN RIESE In-Reply-To: Message-ID: <20080524233543.R9809@fledge.watson.org> References: <20080524213732.J9809@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: kldxref oh oh 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, 24 May 2008 22:36:25 -0000 On Sat, 24 May 2008, KAYVEN RIESE wrote: > On Sat, 24 May 2008, Robert Watson wrote: >> On Fri, 23 May 2008, KAYVEN RIESE wrote: >>> On Fri, 23 May 2008, KAYVEN RIESE wrote: >>> >>> kldxref: file isn't dynamically-linked >>> kldxref: file isn't dynamically-linked >>> kldxref: file isn't dynamically-linked >>> kv_bsd#make kernel >> >>> From the 7.0 errata notes: >> >> [20080307] Source upgrades from FreeBSD 6.X to FreeBSD 7.0-RELEASE will >> generate warnings from kldxref(8) during the installkernel step. These >> warnings are harmless and can be ignored. > > Thank you very much for showing me I should have RTFM in a very nice way. No problem :-). This is arguably a bug, and you're not the first person to ask about it, hence its being in the errata. I'd like to see this fixed for 7.1 so people sliding forwards from 6.x to 7.1 don't have the same obvious question. Robert N M Watson Computer Laboratory University of Cambridge