From owner-freebsd-current Sun Jan 7 2:15:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id CA13737B400; Sun, 7 Jan 2001 02:15:37 -0800 (PST) Received: from fwd07.sul.t-online.com by mailout05.sul.t-online.com with smtp id 14FCrQ-0004fb-01; Sun, 07 Jan 2001 11:15:36 +0100 Received: from neutron.cichlids.com (520050424122-0001@[62.225.192.100]) by fmrl07.sul.t-online.com with esmtp id 14FCrD-1PXKHgC; Sun, 7 Jan 2001 11:15:23 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 403E3AB0C; Sun, 7 Jan 2001 11:16:20 +0100 (CET) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id A950714B32; Sun, 7 Jan 2001 11:15:23 +0100 (CET) Date: Sun, 7 Jan 2001 11:15:23 +0100 To: Jeremy Lea Cc: freebsd-ports@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Latest on rewrite of pkg_install tools. Message-ID: <20010107111523.F1193@cichlids.cichlids.com> Mail-Followup-To: alex@cichlids.cichlids.com, Jeremy Lea , freebsd-ports@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <20010106234655.K388@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010106234655.K388@shale.csir.co.za>; from reg@FreeBSD.ORG on Sat, Jan 06, 2001 at 11:46:55PM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! This is great! However, the patch has some whitespace-fubars: diff -urN -x CVS pkg_install/info/main.c pkg_install.jdl/info/main.c --- pkg_install/info/main.c Tue Dec 12 10:07:19 2000 +++ pkg_install.jdl/info/main.c Sat Jan 6 02:13:47 2001 @@ -7,10 +7,10 @@ * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright - * notice, this list of conditions and the following disclaimer. + * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright - * notice, this list of conditions and the following disclaimer in the - * documentation and/or other materials provided with the distribution. + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. * * Jordan K. Hubbard * 18 July 1993 @@ -19,168 +19,227 @@ * */ And similar, everywhere. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 8: 8: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 5880037B400 for ; Sun, 7 Jan 2001 08:07:49 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id f07G0Zv14715; Sun, 7 Jan 2001 16:00:36 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id f07G6YR18713; Sun, 7 Jan 2001 16:06:34 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200101071606.f07G6YR18713@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: weird cvs update problem In-Reply-To: Message from Archie Cobbs of "Sat, 06 Jan 2001 17:16:35 PST." <200101070116.f071GZR41032@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jan 2001 16:06:34 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ISTR Christian Weisgerber was having this problem too. I don't know if there was any fix as such.... > I have a -current system from Dec. 7 on which I'm trying to do > a cvs update in preparation of make world, and am seeing wierd > stuff like this: > > > cvs server: Updating crypto/kerberosIV/appl/afsutil > > U crypto/kerberosIV/appl/afsutil/Makefile.in > > U crypto/kerberosIV/appl/afsutil/aklog.c > > U crypto/kerberosIV/appl/afsutil/kstring2key.c > > U crypto/kerberosIV/appl/afsutil/pagsh.c > > cvs server: Updating crypto/kerberosIV/appl/bsd > > U crypto/kerberosIV/appl/bsd/Makefile.in > > U crypto/kerberosIV/appl/bsd/README.login > > U crypto/kerberosIV/appl/bsd/bsd_locl.h > > U crypto/kerberosIV/appl/bsd/encrypt.c > > U crypto/kerberosIV/appl/bsd/forkpty.c > > U crypto/kerberosIV/appl/bsd/kcmd.c > > U crypto/kerberosIV/appl/bsd/klogin.c > > U crypto/kerberosIV/appl/bsd/krcmd.c > > U crypto/kerberosIV/appl/bsd/login.c > > U crypto/kerberosIV/appl/bsd/login_access.c > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > U crypto/kerberosIV/appl/bsd/osfc2.c > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > cvs update: warning: unrecognized response ` */' from cvs server > > cvs update: warning: unrecognized response `' from cvs server > > cvs update: warning: unrecognized response `void' from cvs server > > cvs update: warning: unrecognized response `ip_options_and_die (int sock, struct sockaddr_in *fromp)' from cvs server > > cvs update: warning: unrecognized response `{' from cvs server > > cvs update: warning: unrecognized response `#if defined(IP_OPTIONS) && defined(HAVE_GETSOCKOPT)' from cvs server > > cvs update: warning: unrecognized response ` u_char optbuf[BUFSIZ/3], *cp;' from cvs server > > cvs update: warning: unrecognized response ` char lbuf[BUFSIZ], *lp;' from cvs server > > The file data is somehow getting mixed into the "control stream" > or something. The cvs server is a 5.0-20000506-CURRENT machine > that has been working fine for many months (and I don't see the > same problem when cvs updating from other machines). > > I notice that "cvs" was updated to version 1.11 on 10/31/00... > > Has anyone else seen this, and if so, what's the fix?? > > Thanks, > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 12:14:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from host.warwick.net (unknown [204.255.24.254]) by hub.freebsd.org (Postfix) with ESMTP id 9143F37B400; Sun, 7 Jan 2001 12:14:37 -0800 (PST) Received: from ns1 (m201-3-p27.warwick.net [208.242.201.132]) by host.warwick.net (8.11.0/8.11.0) with SMTP id f07KEZw10720; Sun, 7 Jan 2001 15:14:35 -0500 (EST) Message-ID: <002901c078e5$c5197e00$45450a0a@evilicey.com> From: "Justin/Mike Ovens" To: Cc: Subject: Debugging... Date: Sun, 7 Jan 2001 15:09:40 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C078BB.DB61A180" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C078BB.DB61A180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I compiled my kernel with Debuggin symols.. how do i debug the running = kernel? and can i make it log the info to a file? ------=_NextPart_000_0026_01C078BB.DB61A180 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I compiled my kernel with Debuggin = symols.. how do=20 i debug the running kernel?
and can i make it log the info to a=20 file?
------=_NextPart_000_0026_01C078BB.DB61A180-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 13:23:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 7EB4F37B404 for ; Sun, 7 Jan 2001 13:23:13 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA54545 for ; Sun, 7 Jan 2001 13:23:13 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id f07LNCB43746 for current@FreeBSD.ORG; Sun, 7 Jan 2001 13:23:12 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101072123.f07LNCB43746@curve.dellroad.org> Subject: Re: weird cvs update problem In-Reply-To: <200101070126.f071QT512153@vashon.polstra.com> "from John Polstra at Jan 6, 2001 05:26:29 pm" To: current@FreeBSD.ORG Date: Sun, 7 Jan 2001 13:23:12 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > > U crypto/kerberosIV/appl/bsd/osfc2.c > > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > > cvs update: warning: unrecognized response ` */' from cvs server > [...] > > It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the > CVS server. Just a guess. I haven't seen the problem here. Don't think so.. this happens rather randomly for random files (i.e., more than one). The same file will update correctly on the second try (but then it barfs on another one). It doesn't seem to happen for patched files, only for files that are downloaded whole.. ie, if you blow away an entire directory and then download it again. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 13:41:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 0398A37B6A0 for ; Sun, 7 Jan 2001 13:41:11 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA09245 for ; Sun, 7 Jan 2001 16:41:09 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA20333 for ; Sun, 7 Jan 2001 16:41:09 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA20329 for ; Sun, 7 Jan 2001 16:41:09 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sun, 7 Jan 2001 16:41:09 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: cardbus installs on -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is installing FreeBSD-CURRENT with sysinstall using a cardbus supported card (such as a 3com cardbus 3cfe575 or something) working yet? Just wondering because I want to get windows off my laptop, and this will bring me one step closer... (with support for my ess maestro3 chip being the last step) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 13:57:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B60E537B6A9 for ; Sun, 7 Jan 2001 13:56:06 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f07Lu3s39164; Sun, 7 Jan 2001 14:56:03 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101072156.f07Lu3s39164@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: cardbus installs on -current Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 07 Jan 2001 16:41:09 EST." References: Date: Sun, 07 Jan 2001 14:56:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : is installing FreeBSD-CURRENT with sysinstall using a cardbus supported : card (such as a 3com cardbus 3cfe575 or something) working yet? Just : wondering because I want to get windows off my laptop, and this will bring : me one step closer... (with support for my ess maestro3 chip being the : last step) I don't think anybody has ever gone down this path. If you do, please drop a note to -current and/or -mobile telling about your woes and wonders. I'd suspect that it would just work *IF* the card probes before sysinstall's device harvesting mechanism kicks in. Of course, pccardd will not start, but don't worry too much about that. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 14:30:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 5097E37B400 for ; Sun, 7 Jan 2001 14:30:03 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id PAA21514; Sun, 7 Jan 2001 15:30:02 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id PAA06937; Sun, 7 Jan 2001 15:30:01 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14936.60905.340826.334042@nomad.yogotech.com> Date: Sun, 7 Jan 2001 15:30:01 -0700 (MST) To: Archie Cobbs Cc: current@FreeBSD.ORG Subject: Re: weird cvs update problem In-Reply-To: <200101072123.f07LNCB43746@curve.dellroad.org> References: <200101070126.f071QT512153@vashon.polstra.com> <200101072123.f07LNCB43746@curve.dellroad.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > > > U crypto/kerberosIV/appl/bsd/osfc2.c > > > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > > > cvs update: warning: unrecognized response ` */' from cvs server > > [...] > > > > It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the > > CVS server. Just a guess. I haven't seen the problem here. > > Don't think so.. this happens rather randomly for random files > (i.e., more than one). The same file will update correctly on the > second try (but then it barfs on another one). > > It doesn't seem to happen for patched files, only for files that > are downloaded whole.. ie, if you blow away an entire directory > and then download it again. Just a question. Are you using any sort of transport mechanism (besides rsh) in the middle? I had problems like this when using F-Secure's Windows client using compression, which blew up. We switched the users to SecureCRT and the problems went away. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 14:31:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D77637B699 for ; Sun, 7 Jan 2001 14:30:30 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14FOKb-00088J-00; Sun, 7 Jan 2001 23:30:29 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id f07LpNU43214 for freebsd-current@freebsd.org; Sun, 7 Jan 2001 22:51:23 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: weird cvs update problem Date: Sun, 7 Jan 2001 21:51:22 +0000 (UTC) Message-ID: <93aocq$19ro$1@kemoauc.mips.inka.de> References: <200101071606.f07G6YR18713@hak.lan.Awfulhak.org> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > ISTR Christian Weisgerber was having this problem > too. Sorry, you're misremembering. I've never seen anything like this. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 14:42:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 9815637B400 for ; Sun, 7 Jan 2001 14:42:11 -0800 (PST) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA10399; Sun, 7 Jan 2001 17:42:08 -0500 (EST) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA17302; Sun, 7 Jan 2001 17:42:08 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA17298; Sun, 7 Jan 2001 17:42:07 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sun, 7 Jan 2001 17:42:07 -0500 (EST) From: Kenneth Wayne Culver To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: cardbus installs on -current In-Reply-To: <200101072156.f07Lu3s39164@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : is installing FreeBSD-CURRENT with sysinstall using a cardbus supported > : card (such as a 3com cardbus 3cfe575 or something) working yet? Just > : wondering because I want to get windows off my laptop, and this will bring > : me one step closer... (with support for my ess maestro3 chip being the > : last step) > > I don't think anybody has ever gone down this path. If you do, please > drop a note to -current and/or -mobile telling about your woes and > wonders. I'd suspect that it would just work *IF* the card probes > before sysinstall's device harvesting mechanism kicks in. > > Of course, pccardd will not start, but don't worry too much about that. > Is the cardbus stuff in the GENERIC kernel, or will I have to change it and build my own release or custom sysinstall? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 14:44:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 858C737B400 for ; Sun, 7 Jan 2001 14:44:02 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id OAA54957; Sun, 7 Jan 2001 14:44:01 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id f07Mi1144150; Sun, 7 Jan 2001 14:44:01 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101072244.f07Mi1144150@curve.dellroad.org> Subject: Re: weird cvs update problem In-Reply-To: <14936.60905.340826.334042@nomad.yogotech.com> "from Nate Williams at Jan 7, 2001 03:30:01 pm" To: Nate Williams Date: Sun, 7 Jan 2001 14:44:01 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: > > > > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > > > > U crypto/kerberosIV/appl/bsd/osfc2.c > > > > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > > > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > > > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > > > > cvs update: warning: unrecognized response ` */' from cvs server > > > [...] > > > > > > It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the > > > CVS server. Just a guess. I haven't seen the problem here. > > > > Don't think so.. this happens rather randomly for random files > > (i.e., more than one). The same file will update correctly on the > > second try (but then it barfs on another one). > > > > It doesn't seem to happen for patched files, only for files that > > are downloaded whole.. ie, if you blow away an entire directory > > and then download it again. > > Just a question. Are you using any sort of transport mechanism (besides > rsh) in the middle? I had problems like this when using F-Secure's > Windows client using compression, which blew up. We switched the users > to SecureCRT and the problems went away. Nope.. just using cvs in pserver mode to a server on the same subnet, not encrypted or compressed or anything. Once I actually get all of the -current sources I'll rebuild world and see if the problem still exists. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 15: 2:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 748A337B402; Sun, 7 Jan 2001 15:01:51 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Jan 2001 23:01:50 +0000 (GMT) Date: Sun, 7 Jan 2001 23:01:50 +0000 From: David Malone To: Justin/Mike Ovens Cc: freebsd-current@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Debugging... Message-ID: <20010107230150.B38108@walton.maths.tcd.ie> References: <002901c078e5$c5197e00$45450a0a@evilicey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002901c078e5$c5197e00$45450a0a@evilicey.com>; from ice@warwick.net on Sun, Jan 07, 2001 at 03:09:40PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 07, 2001 at 03:09:40PM -0500, Justin/Mike Ovens wrote: > I compiled my kernel with Debuggin symols.. how do i debug the running kernel? gdb -k /kernel.debug /dev/mem > and can i make it log the info to a file? Log what into a file? Syslog can log the messages the kernel produces into a file. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 15:25:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6350437B400 for ; Sun, 7 Jan 2001 15:25:04 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f07NP1s39670; Sun, 7 Jan 2001 16:25:01 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101072325.f07NP1s39670@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: cardbus installs on -current Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 07 Jan 2001 17:42:07 EST." References: Date: Sun, 07 Jan 2001 16:25:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : Is the cardbus stuff in the GENERIC kernel, or will I have to change it : and build my own release or custom sysinstall? You'll have to build a NEWCARD kernel, and put it on the install disk. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 16:58:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id C627437B400 for ; Sun, 7 Jan 2001 16:58:10 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id f080p0a17379; Mon, 8 Jan 2001 00:51:00 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id f080usS22723; Mon, 8 Jan 2001 00:56:54 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200101080056.f080usS22723@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: weird cvs update problem In-Reply-To: Message from naddy@mips.inka.de (Christian Weisgerber) of "Sun, 07 Jan 2001 21:51:22 GMT." <93aocq$19ro$1@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Jan 2001 00:56:54 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > ISTR Christian Weisgerber was having this problem > > too. > > Sorry, you're misremembering. I've never seen anything like this. You're right you know - my apologies ! > -- > Christian "naddy" Weisgerber naddy@mips.inka.de -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 17:18:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id D7E0937B400; Sun, 7 Jan 2001 17:18:35 -0800 (PST) Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id DAA32941; Mon, 8 Jan 2001 03:18:22 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by C992631-A.pinol1.sfba.home.com (8.11.1/8.11.1) id f081Hud54971; Sun, 7 Jan 2001 17:17:56 -0800 (PST) (envelope-from reg) Date: Sun, 7 Jan 2001 17:17:56 -0800 From: Jeremy Lea To: alex@cichlids.cichlids.com, freebsd-ports@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Latest on rewrite of pkg_install tools. Message-ID: <20010107171756.C50118@shale.csir.co.za> Mail-Followup-To: Jeremy Lea , alex@cichlids.cichlids.com, freebsd-ports@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <20010106234655.K388@shale.csir.co.za> <20010107111523.F1193@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010107111523.F1193@cichlids.cichlids.com>; from alex@big.endian.de on Sun, Jan 07, 2001 at 11:15:23AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sun, Jan 07, 2001 at 11:15:23AM +0100, Alexander Langer wrote: > This is great! Thanks. With a litle bit more work, I'm hoping to have solved all of my current peeves with ports/packages. Then it'll be time to look for new peeves... > However, the patch has some whitespace-fubars: Sorry about that... I've corrected the patch (and also removed the CVS .#* leftovers...). The current source uses a wierd 8 space tab and 4 hard space indentation, which I just wacked with perl, and I've been editting the code using 4 space tabs. Before this gets committed, I'll make sure that the indentation is correct, although I'll probably keep it at 4 space tabs, and not 8 space like style(9), because I prefer that, and I know Jordan does too. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 17:54:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id 71B0337B400 for ; Sun, 7 Jan 2001 17:54:10 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.162.22) by relay4.inwind.it (5.1.056) id 3A4B0A72002951BD for freebsd-current@freebsd.org; Mon, 8 Jan 2001 02:54:06 +0100 From: Salvo Bartolotta To: freebsd-current@freebsd.org Subject: SCSI CD recorder no longer attached; minor issues Date: Mon, 8 Jan 2001 02:55:06 +0100 X-Mailer: Drake [wild veersioon] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01010802550600.00359@bartequi.ottodomain.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD'ers, I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can see the following (a # sign precedes my comments): Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad2s1a # YAMAHA CRW4416S: it is correctly recognized by -STABLE. # OTOH, the archives seem to report just *minor* SCSI issues. (cd0:ahc0:0:3:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:3:0): error code 0 (cd0:ahc0:0:3:0): fatal error, failed to attach to device (cd0:ahc0:0:3:0): lost device (cd0:ahc0:0:3:0): removing device entry # My cd player works cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present # It is unusual on this system pcm0: hwptr went backwards 20 -> 12 pcm0: hwptr went backwards 2072 -> 2048 pcm0: hwptr went backwards 2184 -> 2048 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 2068 -> 2048 pcm0: hwptr went backwards 2240 -> 2048 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 2204 -> 2048 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 2068 -> 2048 pcm0: hwptr went backwards 2068 -> 204 I forgot to reboot via 'shutdown -r now' *sigh* On a couple of subsequent occasions, however, shutdown -r now was timed out, and no entropy file was created; 'dd if=/dev/random of=/entropy bs=4096 count=1' (within the shutdown sequence) did NOT create anything. In s.u.m., I issued it as an ordinary explicit command, but it stalled. So... workaround: 'dd if=/dev/urandom of=/entropy bs=4096 count=1'. Then /dev/random, asked again to do its duty, helped dd (to) create an entropy file. I was wondering whether such a sanity check would be worth adding (in rc.shutdown ?) in order to prevent the above entropy (minor) issue. Does this make sense at all? Is this just a little temporary problem ? Thanks for your patience and best regards,. Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 17:54:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id 5E7BD37B404 for ; Sun, 7 Jan 2001 17:54:12 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.162.22) by relay4.inwind.it (5.1.056) id 3A4B0A72002951BE for freebsd-current@freebsd.org; Mon, 8 Jan 2001 02:54:08 +0100 From: Salvo Bartolotta To: freebsd-current@freebsd.org Subject: SCSI CD recorder no longer attached; minor issues Date: Mon, 8 Jan 2001 02:56:15 +0100 X-Mailer: Drake [wild veersioon] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01010802550600.00359@bartequi.ottodomain.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD'ers, I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can see the following (a # sign precedes my comments): Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad2s1a # YAMAHA CRW4416S: it is correctly recognized by -STABLE. # OTOH, the archives seem to report just *minor* SCSI issues. (cd0:ahc0:0:3:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:3:0): error code 0 (cd0:ahc0:0:3:0): fatal error, failed to attach to device (cd0:ahc0:0:3:0): lost device (cd0:ahc0:0:3:0): removing device entry # My cd player works cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present # It is unusual on this system pcm0: hwptr went backwards 20 -> 12 pcm0: hwptr went backwards 2072 -> 2048 pcm0: hwptr went backwards 2184 -> 2048 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 2068 -> 2048 pcm0: hwptr went backwards 2240 -> 2048 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 2204 -> 2048 pcm0: hwptr went backwards 20 -> 0 pcm0: hwptr went backwards 2068 -> 2048 pcm0: hwptr went backwards 2068 -> 204 I forgot to reboot via 'shutdown -r now' *sigh* On a couple of subsequent occasions, however, shutdown -r now was timed out, and no entropy file was created; 'dd if=/dev/random of=/entropy bs=4096 count=1' (within the shutdown sequence) did NOT create anything. In s.u.m., I issued it as an ordinary explicit command, but it stalled. So... workaround: 'dd if=/dev/urandom of=/entropy bs=4096 count=1'. Then /dev/random, asked again to do its duty, helped dd (to) create an entropy file. I was wondering whether such a sanity check would be worth adding (in rc.shutdown ?) in order to prevent the above entropy (minor) issue. Does this make sense at all? Is this just a little temporary problem ? Thanks for your patience and best regards,. Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 20:28:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 7D94337B400 for ; Sun, 7 Jan 2001 20:28:39 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA28311; Sun, 7 Jan 2001 23:28:35 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA08026; Sun, 7 Jan 2001 23:28:35 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA08020; Sun, 7 Jan 2001 23:28:35 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Sun, 7 Jan 2001 23:28:35 -0500 (EST) From: Kenneth Wayne Culver To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: cardbus installs on -current In-Reply-To: <200101072325.f07NP1s39670@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, will do. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 7 Jan 2001, Warner Losh wrote: > In message Kenneth Wayne Culver writes: > : Is the cardbus stuff in the GENERIC kernel, or will I have to change it > : and build my own release or custom sysinstall? > > You'll have to build a NEWCARD kernel, and put it on the install disk. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 20:30:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 04CF637B400 for ; Sun, 7 Jan 2001 20:30:41 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA28352; Sun, 7 Jan 2001 23:30:37 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA08402; Sun, 7 Jan 2001 23:30:37 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA08398; Sun, 7 Jan 2001 23:30:37 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Sun, 7 Jan 2001 23:30:37 -0500 (EST) From: Kenneth Wayne Culver To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: cardbus installs on -current In-Reply-To: <200101072325.f07NP1s39670@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on another note, did you ever get a chance to look at that code that supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I believe. I could still find it for you if you want. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 7 Jan 2001, Warner Losh wrote: > In message Kenneth Wayne Culver writes: > : Is the cardbus stuff in the GENERIC kernel, or will I have to change it > : and build my own release or custom sysinstall? > > You'll have to build a NEWCARD kernel, and put it on the install disk. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 20:46:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2C39B37B400 for ; Sun, 7 Jan 2001 20:46:42 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f084kds41219; Sun, 7 Jan 2001 21:46:39 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101080446.f084kds41219@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: cardbus installs on -current Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 07 Jan 2001 23:30:37 EST." References: Date: Sun, 07 Jan 2001 21:46:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : on another note, did you ever get a chance to look at that code that : supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I : believe. I could still find it for you if you want. I believe that those issues have been fixed with the pmtimer device. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 22:26: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 3531437B6F4 for ; Sun, 7 Jan 2001 22:18:48 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f086Hks69274; Sun, 7 Jan 2001 23:18:12 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101080618.f086Hks69274@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Salvo Bartolotta Cc: freebsd-current@FreeBSD.ORG Subject: Re: SCSI CD recorder no longer attached; minor issues In-Reply-To: Your message of "Mon, 08 Jan 2001 02:55:06 +0100." <01010802550600.00359@bartequi.ottodomain.org> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-17191975020" Date: Sun, 07 Jan 2001 23:17:46 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-17191975020 Content-Type: text/plain; charset=us-ascii >Dear FreeBSD'ers, > >I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can >see the following (a # sign precedes my comments): Can you see if this patch corrects the problem? -- Justin --==_Exmh_-17191975020 Content-Type: text/plain ; name="diffs"; charset=us-ascii Content-Description: diffs Content-Disposition: attachment; filename="diffs" Index: dev/aic7xxx/aic7xxx.c =================================================================== RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx.c,v retrieving revision 1.63 diff -c -r1.63 aic7xxx.c *** dev/aic7xxx/aic7xxx.c 2001/01/05 19:15:36 1.63 --- dev/aic7xxx/aic7xxx.c 2001/01/08 04:48:36 *************** *** 487,494 **** printf("Sending Sense\n"); } #endif ! sg->addr = ahc->scb_data->sense_busaddr ! + (hscb->tag*sizeof(struct scsi_sense_data)); sg->len = ahc_get_sense_bufsize(ahc, scb); sg->len |= AHC_DMA_LAST_SEG; --- 487,493 ---- printf("Sending Sense\n"); } #endif ! sg->addr = ahc_get_sense_bufaddr(ahc, scb); sg->len = ahc_get_sense_bufsize(ahc, scb); sg->len |= AHC_DMA_LAST_SEG; Index: dev/aic7xxx/aic7xxx_freebsd.c =================================================================== RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx_freebsd.c,v retrieving revision 1.16 diff -c -r1.16 aic7xxx_freebsd.c *** dev/aic7xxx/aic7xxx_freebsd.c 2000/12/20 01:11:37 1.16 --- dev/aic7xxx/aic7xxx_freebsd.c 2001/01/08 04:46:28 *************** *** 337,343 **** */ memset(&ccb->csio.sense_data, 0, sizeof(ccb->csio.sense_data)); memcpy(&ccb->csio.sense_data, ! &ahc->scb_data->sense[scb->hscb->tag], (scb->sg_list->len & AHC_SG_LEN_MASK) - ccb->csio.sense_resid); scb->io_ctx->ccb_h.status |= CAM_AUTOSNS_VALID; --- 337,343 ---- */ memset(&ccb->csio.sense_data, 0, sizeof(ccb->csio.sense_data)); memcpy(&ccb->csio.sense_data, ! ahc_get_sense_buf(ahc, scb), (scb->sg_list->len & AHC_SG_LEN_MASK) - ccb->csio.sense_resid); scb->io_ctx->ccb_h.status |= CAM_AUTOSNS_VALID; Index: dev/aic7xxx/aic7xxx_inline.h =================================================================== RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx_inline.h,v retrieving revision 1.9 diff -c -r1.9 aic7xxx_inline.h *** dev/aic7xxx/aic7xxx_inline.h 2000/12/20 01:11:37 1.9 --- dev/aic7xxx/aic7xxx_inline.h 2001/01/08 04:55:49 *************** *** 200,205 **** --- 200,211 ---- static __inline void ahc_swap_with_next_hscb(struct ahc_softc *ahc, struct scb *scb); static __inline void ahc_queue_scb(struct ahc_softc *ahc, struct scb *scb); + static __inline struct scsi_sense_data * + ahc_get_sense_buf(struct ahc_softc *ahc, + struct scb *scb); + static __inline uint32_t + ahc_get_sense_bufaddr(struct ahc_softc *ahc, + struct scb *scb); /* * Determine whether the sequencer reported a residual *************** *** 344,349 **** --- 350,374 ---- if ((ahc->features & AHC_AUTOPAUSE) == 0) unpause_sequencer(ahc); } + } + + static __inline struct scsi_sense_data * + ahc_get_sense_buf(struct ahc_softc *ahc, struct scb *scb) + { + int offset; + + offset = scb - ahc->scb_data->scbarray; + return (&ahc->scb_data->sense[offset]); + } + + static __inline uint32_t + ahc_get_sense_bufaddr(struct ahc_softc *ahc, struct scb *scb) + { + int offset; + + offset = scb - ahc->scb_data->scbarray; + return (ahc->scb_data->sense_busaddr + + (offset * sizeof(struct scsi_sense_data))); } /************************** Interrupt Processing ******************************/ --==_Exmh_-17191975020-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 7 23:43:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 6F50B37B400 for ; Sun, 7 Jan 2001 23:42:27 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA02269; Mon, 8 Jan 2001 02:42:24 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id CAA20610; Mon, 8 Jan 2001 02:42:23 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA20606; Mon, 8 Jan 2001 02:42:23 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 8 Jan 2001 02:42:23 -0500 (EST) From: Kenneth Wayne Culver To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: cardbus installs on -current In-Reply-To: <200101080446.f084kds41219@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oh ok, sounds good then... I'll definitly try it out soon then. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 7 Jan 2001, Warner Losh wrote: > In message Kenneth Wayne Culver writes: > : on another note, did you ever get a chance to look at that code that > : supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I > : believe. I could still find it for you if you want. > > I believe that those issues have been fixed with the pmtimer device. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 0:56:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id B3A6337B400 for ; Mon, 8 Jan 2001 00:56:33 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id JAA14701 for ; Mon, 8 Jan 2001 09:56:31 +0100 (MET) Date: Mon, 8 Jan 2001 09:56:31 +0100 (CET) From: Harti Brandt To: current@FreeBSD.ORG Subject: Re: weird cvs update problem In-Reply-To: <200101072123.f07LNCB43746@curve.dellroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Jan 2001, Archie Cobbs wrote: > John Polstra writes: > > > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > > > U crypto/kerberosIV/appl/bsd/osfc2.c > > > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > > > cvs update: warning: unrecognized response ` */' from cvs server > > [...] > > > > It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the > > CVS server. Just a guess. I haven't seen the problem here. > > Don't think so.. this happens rather randomly for random files > (i.e., more than one). The same file will update correctly on the > second try (but then it barfs on another one). > > It doesn't seem to happen for patched files, only for files that > are downloaded whole.. ie, if you blow away an entire directory > and then download it again. Since the new version CVS appears to have random problems. Is used to have a command like find . -type f | grep -v CVS | xargs cvs status | ... in my Makefiles, but this does not work anymore. The cvs fails in random ways with different error messages. Using cvs status with only one file name works most of the time, but can be really slow when you have a large tree. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 3: 5:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A785D37B400 for ; Mon, 8 Jan 2001 03:04:57 -0800 (PST) Received: from swbell.net (adsl-64-217-250-96.dsl.rcsntx.swbell.net [64.217.250.96]) by mx1.FreeBSD.org (Postfix) with SMTP id AD3396E2A35 for ; Mon, 8 Jan 2001 03:04:56 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=200101080127=" To: current@freebsd.org From: jbdreads@swbell.net X-Mailer: 15D7A676.6757BC7D.f30768bef22c2a52042ce90a7872e792 Subject: "Dreadlocks Are Easy to Get!"....The Hard Part Is....... Organization: Message-Id: <20010108110456.AD3396E2A35@mx1.FreeBSD.org> Date: Mon, 8 Jan 2001 03:04:56 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=200101080127= Content-Type: text/plain;charset=US-ASCII ==================================================== Growing dreadlocks or locking you hair is easy! The hard part is living successfully in America's society with your bold new look. ============================================== New book "Don't Worry Be Nappy! - How To Grow Dreadlocks In America and Still Get Everything You Want" is packed full great ideas, tips, and advice to make you a success with dreadlocks. Author Jeffery Bradley has been growing dreadlocks for 15 years and has worked in 3 major corporations. He knows about living very successfully with dreadlocks. Now he's giving YOU everything that has made him a success in both growing dreadlocks and succeeding with his unique hair style. You will learn: * How easy it is to grow dreadlocks * Tips and techniques for keeping them strong and beautiful * How to prepare to succeed * Ways to successfully deal with society * Personal experiences from the author Call TOLL FREE at 1 877 217 2346 for more information. Sincere, Jeffery Bradley Author "Don't Worry Be NAPPY!" ========================================= If you would like to remove yourself from this list, please click mailto:isucceed@swbell.net?subject=removenow then hit the send button and you will be removed immediately. Thank you. --=200101080127=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 5:54:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 926FB37B402 for ; Mon, 8 Jan 2001 05:54:01 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f08Dqvk07586 for current@freebsd.org; Mon, 8 Jan 2001 08:52:57 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101081352.f08Dqvk07586@hda.hda.com> Subject: Fan speed control sony vaio lx800 slimtop To: current@freebsd.org Date: Mon, 8 Jan 2001 08:52:57 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've installed current on a Vaio LX800 slimtop, configured ACPI and can turn the thing on and off with the "power" button. By the way, the 4.2R to -current upgrade was painless. Now I'd like to figure out how to turn the damn fan up and down. This machine is quiet under windows but sets the fan to high under FreeBSD and never turns it down. The fan has three settings - 0V, 6V and 12V. Under windows it stays between 0 and 6V. I've tried "apm -h 1; apm -e 1;" hoping something would happen but it still doesn't slow down the fan. If someone can sketch out a road map of what I should do I'll do the dirty work. I don't know about ACPI etc and so would appreciate a kick start. I've picked up the spec but haven't printed it out yet. Peter PS minimal Sony Vaio LX700/LX800 technical info is available on the Italian Sony web site. -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 7:51: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from lolita.speakeasy.net (lolita.speakeasy.net [216.254.0.13]) by hub.freebsd.org (Postfix) with SMTP id 0832C37B400 for ; Mon, 8 Jan 2001 07:50:44 -0800 (PST) Received: (qmail 28579 invoked from network); 8 Jan 2001 15:43:27 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 8 Jan 2001 15:43:27 -0000 Received: (qmail 787 invoked from network); 8 Jan 2001 15:50:33 -0000 Received: from unknown (HELO celebris.tddhome) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 8 Jan 2001 15:50:33 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.1/8.11.1) id f08FoW513598; Mon, 8 Jan 2001 07:50:32 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Mon, 8 Jan 2001 07:50:32 -0800 (PST) Message-Id: <200101081550.f08FoW513598@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: current@FreeBSD.ORG Subject: UP Stray irq7's and SMP Fatal Trap 12's Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running -current UP. I try to run SMP, but, I get Fatal Trap 12's. The easiest way to trigger the trap is to cause a transactiopn to lpd. In the UP kernel, I get a group of stray irq7's every time I print somethting. I started seeing stray irq7's around Sep. 1, 2000. The result of three print requests: Jan 7 18:15:28 celebris /boot/kernel/kernel: stray irq 7 Jan 7 18:15:28 celebris /boot/kernel/kernel: stray irq 7 Jan 7 18:15:28 celebris last message repeated 3 times Jan 7 18:15:28 celebris /boot/kernel/kernel: got 5 stray irq 7's: \ not logging anymore Jan 7 18:15:28 celebris last message repeated 3 times Jan 7 18:15:28 celebris /boot/kernel/kernel: got 5 stray irq 7's: \ not logging anymore Are the stray irq7's somehow connected to the fatal trap 12's? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 12:30:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4176D37B800 for ; Mon, 8 Jan 2001 11:51:25 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f08JpPN11179 for ; Mon, 8 Jan 2001 20:51:25 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: Make release barfs... From: Poul-Henning Kamp Date: Mon, 08 Jan 2001 20:51:25 +0100 Message-ID: <11177.978983485@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> stage 4: populating /usr/obj/usr/src/i386/usr/include -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/ libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/li b:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexe c PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/s rc/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/ sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/u sr/sbin:/usr/bin make -f Makefile.inc1 SHARED=symlinks includes cd /usr/src/include; make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys /conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \# 'define __FreeBSD_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 13:39:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from kdmail.netcologne.de (kdmail.netcologne.de [194.8.194.80]) by hub.freebsd.org (Postfix) with ESMTP id 3742837B755 for ; Mon, 8 Jan 2001 13:02:49 -0800 (PST) Received: from EXCHANGE01.hgk-koeln.de ([195.14.232.162]) by kdmail.netcologne.de (Post.Office MTA v3.5.3 release 223 ID# 127-61375U6500L550S0V35) with ESMTP id de; Mon, 8 Jan 2001 22:02:27 +0100 Received: from 1Cust1.tnt11.tacoma.wa.da.uu.net by EXCHANGE01.hgk-koeln.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id YRV12H8G; Mon, 8 Jan 2001 22:02:21 +0100 Message-ID: <000058310e82$000041be$000032d6@202.84.178.7> To: From: xloj@navrcholu.cz Subject: Put CASH In Your Pocket NOW! 13014 Date: Wed, 07 Feb 2001 06:12:03 -0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_59C9_00004C7D.000055E3" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_59C9_00004C7D.000055E3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Get The Cash YOU NEED!

Receive Up To 200% Of Your Homes Value!
Bad Credit... Slow Credit... NO PROBLEM!

Click Here Now For Complete Details!




------=_NextPart_000_59C9_00004C7D.000055E3 Content-Type: text/plain; file=TheMoneyYouNeed.txt Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=TheMoneyYouNeed.txt V2UgZ2V0IGJhbmtzIHRvIHdvcmsgZm9yIHlvdS4NCg0KaHR0cDovL3d3dy5nb2pvaG5ueTMu bmV0L2ZyZWVtb3J0Z2FnZXF1b3Rlcw== ------=_NextPart_000_59C9_00004C7D.000055E3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 16:17:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id 752ED37B400 for ; Mon, 8 Jan 2001 16:17:31 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.171.30) by relay4.inwind.it (5.1.056) id 3A4B0A72002CF67B; Tue, 9 Jan 2001 01:16:21 +0100 From: Salvo Bartolotta Date: Tue, 09 Jan 2001 00:18:35 GMT Message-ID: <20010109.183500@bartequi.ottodomain.org> Subject: SOLVED: SCSI CD recorder no longer attached; minor issues To: "Justin T. Gibbs" Cc: freebsd-current@FreeBSD.ORG References: <200101080618.f086Hks69274@aslan.scsiguy.com> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/8/01, 7:17:46 AM, "Justin T. Gibbs" wrote regarding Re: SCSI CD recorder no longer attached; minor issues : > Can you see if this patch corrects the problem? /* The patch in question, if not yet committed, can be retrieved in the previous message */ On my FreeBSD 5-0 CURRENT (sources as of... the day before yesterday ~ 18:15 GMT): perl -pi -e "s:^V^M::g" Gibbsdiffs # How come... :-) patch -d /usr/src/sys/dev/aic7xxx/ ; Mon, 8 Jan 2001 16:50:12 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f090mYs84303; Mon, 8 Jan 2001 17:49:38 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101090049.f090mYs84303@aslan.scsiguy.com> To: Salvo Bartolotta Cc: freebsd-current@FreeBSD.ORG Subject: Re: SOLVED: SCSI CD recorder no longer attached; minor issues In-Reply-To: Your message of "Tue, 09 Jan 2001 00:18:35 GMT." <20010109.183500@bartequi.ottodomain.org> Date: Mon, 08 Jan 2001 17:48:34 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >perl -pi -e "s:^V^M::g" Gibbsdiffs # How come... :-) That's MH's mime for you. >Summing up: SCSI seems to work like a charm. The patch has been committed to both -current and -stable. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 18:40:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B02F337B400 for ; Mon, 8 Jan 2001 18:40:06 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA06114 for ; Mon, 8 Jan 2001 18:40:06 -0800 Date: Mon, 8 Jan 2001 18:40:06 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: sio && serial console in -current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something wierd has been happening lately- the serial console on my i386 machine works fine up until init is forked.. THen the output is mangled, and one gets replicated and/or mangled stuff. On a reboot I'm getthing things like: WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd It's like the output is being repeated... Anyone seen same? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 19: 6:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C510A37B401 for ; Mon, 8 Jan 2001 19:06:09 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0934AG54247; Mon, 8 Jan 2001 19:04:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 08 Jan 2001 19:06:14 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: RE: sio && serial console in -current? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Jan-01 Matthew Jacob wrote: > > Something wierd has been happening lately- the serial console on my i386 > machine works fine up until init is forked.. THen the output is mangled, and > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > like: > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd > > > It's like the output is being repeated... > > > Anyone seen same? Nope, I've been booting my laptop over 115200 serial console to a my 4.x workstation during ACPI testing w/o any problems. I've also logged in and done stuff on it over 115200 as well. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 19:11:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id CF5C037B69D; Mon, 8 Jan 2001 19:10:57 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f093AuG16245; Mon, 8 Jan 2001 19:10:57 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101090310.f093AuG16245@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: Make release barfs... In-Reply-To: <11177.978983485@critter> Date: Mon, 08 Jan 2001 19:10:56 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > -------------------------------------------------------------- > >>> stage 4: populating /usr/obj/usr/src/i386/usr/include > -------------------------------------------------------------- > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h > rpcgen: cannot find any C preprocessor (cpp) > *** Error code 1 David O'Brien would be the most likely candidate having renamed cpp to cpp0. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 19:11:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F19837B400; Mon, 8 Jan 2001 19:10:57 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA06305; Mon, 8 Jan 2001 19:10:56 -0800 Date: Mon, 8 Jan 2001 19:10:56 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: current@FreeBSD.org Subject: RE: sio && serial console in -current? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, weird. I'm at 9600... What's wierd is that it's got to be some userland induced thing because printouts from the kernel are fine until init is invoked... sio for alpha seems fine..... wahhh..... > > On 09-Jan-01 Matthew Jacob wrote: > > > > Something wierd has been happening lately- the serial console on my i386 > > machine works fine up until init is forked.. THen the output is mangled, and > > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > > like: > > > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd > > > > > > It's like the output is being repeated... > > > > > > Anyone seen same? > > Nope, I've been booting my laptop over 115200 serial console to a my 4.x > workstation during ACPI testing w/o any problems. I've also logged in and done > stuff on it over 115200 as well. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 20:16:15 2001 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 3820637B402; Mon, 8 Jan 2001 20:15:58 -0800 (PST) Date: Mon, 8 Jan 2001 20:15:58 -0800 From: "John W. De Boskey" To: Current List Subject: make release - no luck Message-ID: <20010108201558.A60352@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying to create a -current release for awhile now and have run into numerouse problems. However, this one seems to be reproducible (last 3 days or so): -------------------------------------------------------------- >>> stage 4: populating /usr/obj/usr/src/i386/usr/include -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 SHARED=symlinks includes cd /usr/src/include; make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys/conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __FreeBSD_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 There is a cpp in /usr/obj/usr/src/i386/usr/bin which is really /snap/release/usr/obj/usr/src/i386/usr/bin. I'll look into this more closely if no one has any quick answers. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 22:29:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id B6AF237B400; Mon, 8 Jan 2001 22:29:21 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f096TGG16888; Mon, 8 Jan 2001 22:29:19 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101090629.f096TGG16888@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: mjacob@feral.com Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: sio && serial console in -current? In-Reply-To: Date: Mon, 08 Jan 2001 22:29:16 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > Yeah, weird. I'm at 9600... What's wierd is that it's got to be some userland > induced thing because printouts from the kernel are fine until init is > invoked... This is an ongoing "Hmm, that is strange!" type problem. There are several symptoms that I see at times: 1: console turns to garbage part way through /etc/rc and comes back to life when /etc/rc exits and getty starts 2: console *disappears* part way through /etc/rc and comes back to life when /etc/rc exits and getty starts 3: there is a burst of garbage after /etc/rc and before getty 4: the problem you describe I think I have seen a long time ago, once. 5: ^T and ^C and ^\ do not work ("not a controlling terminal") during the execution of /etc/rc. There are several different ways this happens depending on whether you go via the single user shell or not. This happens on some machines semi regularly and occasionally on others and "never" (yet) on some others. These are all serial consoles, and all machines are different. SMP machines are far worse than UP, but my UP machines have this sort of thing occasionally too. > sio for alpha seems fine..... wahhh..... I am sure we can break it for compatability :-) > > On 09-Jan-01 Matthew Jacob wrote: > > > > > > Something wierd has been happening lately- the serial console on my i386 > > > machine works fine up until init is forked.. THen the output is mangled, and > > > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > > > like: > > > > > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > > > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > > > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > > > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > > > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd > > > > > > > > > It's like the output is being repeated... > > > > > > > > > Anyone seen same? > > > > Nope, I've been booting my laptop over 115200 serial console to a my 4.x > > workstation during ACPI testing w/o any problems. I've also logged in and done > > stuff on it over 115200 as well. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 8 23:24:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 27CBE37B400 for ; Mon, 8 Jan 2001 23:23:59 -0800 (PST) Received: by heechee.tobez.org (Postfix, from userid 1001) id 2116B54C4; Tue, 9 Jan 2001 08:23:36 +0100 (CET) Date: Tue, 9 Jan 2001 08:23:36 +0100 From: Anton Berezin To: Raymond Hicks Cc: current@freebsd.org Subject: Re: CURRENT breaks some apps Message-ID: <20010109082336.A18603@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Raymond Hicks , current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rayhicks@UU.NET on Sat, Jan 06, 2001 at 12:12:24AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 06, 2001 at 12:12:24AM -0500, Raymond Hicks wrote: > I have had a problem with running infobot after my recent cvsup to > current. I have heard that there is a problem with the newer perl > version.. is this a result of that? Here is error: > deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near ">>> $b" > Missing braces on \N{} at ./src/Irc.pl line 133, near ">>> $b" > Missing braces on \N{} at ./src/Irc.pl line 152, within string > Compilation failed in require at ./infobot line 39. > BEGIN failed--compilation aborted at ./infobot line 42. > > and here is perl -v > > deepwoods# perl -v > > This is perl, v5.6.0 built for i386-freebsd > (with 1 registered patch, see perl -V for more detail) 5.6.0 introduced new escape: \N{}, named chars for UTF-8. See man charnames for details. If you want to fix Irc.pl yourself, go there and remove unnecessary backslashes (if one wants `N', why would one use `\N' anyway?). HTH, Cheers, ^Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 0:11:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 9869737B400 for ; Tue, 9 Jan 2001 00:11:21 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f098BKN14715 for ; Tue, 9 Jan 2001 09:11:20 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: make release still broken... From: Poul-Henning Kamp Date: Tue, 09 Jan 2001 09:11:20 +0100 Message-ID: <14713.979027880@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> stage 4: populating /usr/obj/usr/src/i386/usr/include -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBR ARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PER L5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr /bin make -f Makefile.inc1 SHARED=symlinks includes cd /usr/src/include; make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys/conf/newvers.sh; ec ho "$COPYRIGHT" > osreldate.h; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __F reeBSD_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 3:10:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A4B0537B401 for ; Tue, 9 Jan 2001 03:10:34 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA98886; Tue, 9 Jan 2001 12:10:33 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: bogus microuptime() warnings? From: Dag-Erling Smorgrav Date: 09 Jan 2001 12:10:32 +0100 Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I regularly get "microuptime() went backwards" warnings on my desktop box. The funny thing about them is that the reported timevals have the same seconds part, but the microseconds part of the second timeval is so large that it's wrapped around to a negative number (causing the signed comparison to report that it went backwards). This suggests that the current process has been running uninterrupted for several seconds, which seems unlikely - or that the timecounter was adjusted upwards while the process was running (could ntp cause that?) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 3:14:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4703237B400 for ; Tue, 9 Jan 2001 03:14:38 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f09BEZN15660; Tue, 9 Jan 2001 12:14:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: bogus microuptime() warnings? In-Reply-To: Your message of "09 Jan 2001 12:10:32 +0100." Date: Tue, 09 Jan 2001 12:14:35 +0100 Message-ID: <15658.979038875@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >I regularly get "microuptime() went backwards" warnings on my desktop >box. The funny thing about them is that the reported timevals have the >same seconds part, but the microseconds part of the second timeval is >so large that it's wrapped around to a negative number (causing the >signed comparison to report that it went backwards). This suggests >that the current process has been running uninterrupted for several >seconds, which seems unlikely - or that the timecounter was adjusted >upwards while the process was running (could ntp cause that?) No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. If you sysctl's indicate that you are running on the TSC timecounter and you can reproduce this there is some chance we can create a workaround. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 3:52:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EE46637B400 for ; Tue, 9 Jan 2001 03:52:12 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA99038; Tue, 9 Jan 2001 12:49:40 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: bogus microuptime() warnings? References: <15658.979038875@critter> From: Dag-Erling Smorgrav Date: 09 Jan 2001 12:49:39 +0100 In-Reply-To: Poul-Henning Kamp's message of "Tue, 09 Jan 2001 12:14:35 +0100" Message-ID: Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > No, this is either a problem reading the i8254 timecounter reliably > or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... > If you sysctl's indicate that you are running on the TSC timecounter > and you can reproduce this there is some chance we can create a workaround. I'll check. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 3:58:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id DDDF437B400 for ; Tue, 9 Jan 2001 03:58:04 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f09Bw2N15845; Tue, 9 Jan 2001 12:58:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: bogus microuptime() warnings? In-Reply-To: Your message of "09 Jan 2001 12:49:39 +0100." Date: Tue, 09 Jan 2001 12:58:02 +0100 Message-ID: <15843.979041482@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >Poul-Henning Kamp writes: >> No, this is either a problem reading the i8254 timecounter reliably >> or an interrupt latency problem. > >Given that this is -CURRENT, interrupt latency is a likely >explanation... > >Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" >with the latest -CURRENT than I used to... That's also the irq-latency if I understand it right. The latency went from "abysmal" to "bad" recently. We used to do "ok". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 4:54:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from radiac.mine.nu (h37n2fls20o974.telia.com [212.181.170.37]) by hub.freebsd.org (Postfix) with ESMTP id 7AE3037B400 for ; Tue, 9 Jan 2001 04:54:34 -0800 (PST) Received: (from ps@localhost) by radiac.mine.nu (8.11.1/8.11.1) id f09CsRi06209 for current@freebsd.org; Tue, 9 Jan 2001 13:54:27 +0100 (CET) (envelope-from ps) Date: Tue, 9 Jan 2001 13:54:26 +0100 From: Patrik Sundberg To: current@freebsd.org Subject: newpcm audio recording Message-ID: <20010109135426.A6188@radiac.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? -- Patrik Sundberg - email: ps@raditex.se || ps@radiac.mine.nu ---> telefon: 013-178 567 - mobiltelefon: 070-760 22 40 <--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 5:30:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from lupinella.troll.no (lupinella.troll.no [213.203.59.59]) by hub.freebsd.org (Postfix) with ESMTP id 925C737B404 for ; Tue, 9 Jan 2001 05:30:33 -0800 (PST) Received: from breiflabb.troll.no ([213.203.59.91]:39691 "HELO breiflabb" ident: "NO-IDENT-SERVICE[2]") by trolltech.com with SMTP id ; Tue, 9 Jan 2001 14:30:18 +0100 Message-ID: <018101c07a40$43440240$5b3bcbd5@breiflabb> From: "Erik H. Bakke" To: "Patrik Sundberg" , References: <20010109135426.A6188@radiac.mine.nu> Subject: Re: newpcm audio recording Date: Tue, 9 Jan 2001 14:29:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I have been trying to do some audio-recording lately without much success. > After searching the archieves etc I found some reports of this problem and > there are also some PR's about it (8bit at low rates ok, 16bit and higher > rates is not). > > I was wondering if someone is working on this and if we could expect some > progress soon? > I believe this may be related to the soundcard driver, which soundcard are you using? I am using an SB Live 1024 in my computer, and I am reading from the audio input, 16 bits at 44.1KHz, although only in mono, doing fourier transform on the data, and displaying the results graphically, without any problems. --- Erik H. Bakke Don't ask "Who invented time?", the real question is "When was time invented?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 6:16:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from radiac.mine.nu (h37n2fls20o974.telia.com [212.181.170.37]) by hub.freebsd.org (Postfix) with ESMTP id DFF5D37B400 for ; Tue, 9 Jan 2001 06:15:55 -0800 (PST) Received: (from ps@localhost) by radiac.mine.nu (8.11.1/8.11.1) id f09EFpk06447; Tue, 9 Jan 2001 15:15:51 +0100 (CET) (envelope-from ps) Date: Tue, 9 Jan 2001 15:15:49 +0100 From: Patrik Sundberg To: "Erik H. Bakke" Cc: current@freebsd.org Subject: Re: newpcm audio recording Message-ID: <20010109151549.A6427@radiac.mine.nu> References: <20010109135426.A6188@radiac.mine.nu> <018101c07a40$43440240$5b3bcbd5@breiflabb> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <018101c07a40$43440240$5b3bcbd5@breiflabb>; from ebakke@trolltech.com on Tue, Jan 09, 2001 at 02:29:59PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 02:29:59PM +0100, Erik H. Bakke wrote: > > Hi, > > > > I have been trying to do some audio-recording lately without much success. > > After searching the archieves etc I found some reports of this problem and > > there are also some PR's about it (8bit at low rates ok, 16bit and higher > > rates is not). > > > > I was wondering if someone is working on this and if we could expect some > > progress soon? > > > > I believe this may be related to the soundcard driver, which soundcard are > you using? > > > I am using an SB Live 1024 in my computer, and I am reading from the audio > input, 16 bits at 44.1KHz, although only in mono, doing fourier transform > on the data, and displaying the results graphically, without any problems. I have a SB32 isa-card. -- Patrik Sundberg - email: ps@raditex.se || ps@radiac.mine.nu ---> telefon: 013-178 567 - mobiltelefon: 070-760 22 40 <--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 6:48: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 1112B37B401 for ; Tue, 9 Jan 2001 06:47:45 -0800 (PST) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id f09Elgk27046; Tue, 9 Jan 2001 23:47:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: dufault@hda.hda.com Cc: current@freebsd.org Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101081352.f08Dqvk07586@hda.hda.com> References: <200101081352.f08Dqvk07586@hda.hda.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010109234742E.iwasaki@jp.FreeBSD.org> Date: Tue, 09 Jan 2001 23:47:42 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Now I'd like to figure out how to turn the damn fan up and down. This > machine is quiet under windows but sets the fan to high under FreeBSD > and never turns it down. The fan has three settings - 0V, 6V and > 12V. Under windows it stays between 0 and 6V. Thermal management implementation is in our queue. We'll create policy manager for ACPI subsystems including thermal (Active, Passive cooling etc.). Of course any help would be welcome :-) > I've tried "apm -h 1; apm -e 1;" hoping something would happen > but it still doesn't slow down the fan. Currently we don't have any means to control fan device (except for the machine specific tools). > If someone can sketch out a road map of what I should do I'll do the > dirty work. I don't know about ACPI etc and so would appreciate a > kick start. I've picked up the spec but haven't printed it out yet. You could find `3.10 Thermal Management' for overview and `12 THERMAL MANAGEMENT' for detail in ACPI 2.0 spec. Also `7.1 Declaring a Power Resource Object' and `10.6 Fan Device' may help you. acpi-jp@jp.freebsd.org is a mailing list for ACPI development. # English and Japanese are mixed :-) If you are interested in it, please send a mail to Majordomo@jp.freebsd.org with subscribe acpi-jp on body. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 6:51:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id B832737B401 for ; Tue, 9 Jan 2001 06:50:52 -0800 (PST) Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id EB013D9B8; Tue, 9 Jan 2001 14:50:49 +0000 (GMT) Message-ID: <002701c07a4b$a51b2790$0504020a@haveblue> From: "Cameron Grant" To: "Patrik Sundberg" , "Erik H. Bakke" Cc: References: <20010109135426.A6188@radiac.mine.nu> <018101c07a40$43440240$5b3bcbd5@breiflabb> <20010109151549.A6427@radiac.mine.nu> Subject: Re: newpcm audio recording Date: Tue, 9 Jan 2001 14:51:27 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a SB32 isa-card. what revision of sys/dev/sound/isa/sb16.c ? -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 9:12:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 699B137B6C6; Tue, 9 Jan 2001 09:11:51 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA27786; Tue, 9 Jan 2001 09:11:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f09HBnD76351; Tue, 9 Jan 2001 09:11:49 -0800 (PST) (envelope-from obrien) Date: Tue, 9 Jan 2001 09:11:49 -0800 From: "David O'Brien" To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: make release still broken... Message-ID: <20010109091149.A76331@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <14713.979027880@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14713.979027880@critter>; from phk@freebsd.org on Tue, Jan 09, 2001 at 09:11:20AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 09:11:20AM +0100, Poul-Henning Kamp wrote: > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h > rpcgen: cannot find any C preprocessor (cpp) > *** Error code 1 Let me start a release. This means rpcgen has been using /usr/libexec/cpp which is *only* for the compiler's use. rpcgen should have been using /usr/bin/cpp all this time. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 9:17:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 12C4B37B6C8; Tue, 9 Jan 2001 09:17:05 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id A50452CE79; Tue, 9 Jan 2001 19:16:13 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id f09HHDV09966; Tue, 9 Jan 2001 19:17:13 +0200 (EET) (envelope-from vallo) Date: Tue, 9 Jan 2001 19:17:13 +0200 From: Vallo Kallaste To: Justin Gibbs Cc: freebsd-current@freebsd.org Subject: FYI: got back second channel of aic7896 Message-ID: <20010109191713.A9933@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Didn't get around rebuilding world and kernel until today. Got back my cdrom and old Fireball_TM disk, thank you. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 9:45:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 18E0B37B6D0 for ; Tue, 9 Jan 2001 09:45:17 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA67900 for ; Tue, 9 Jan 2001 09:45:15 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id f09HjEB51427 for freebsd-current@freebsd.org; Tue, 9 Jan 2001 09:45:14 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101091745.f09HjEB51427@curve.dellroad.org> Subject: proposed small change to .cshrc To: freebsd-current@freebsd.org Date: Tue, 9 Jan 2001 09:45:14 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the patch below (in some form) was agreed upon a while ago but nobody actually committed it.. in any case, are there any objections? This makes it so if root's shell is /bin/tcsh then CTRL-W erases only the previous word instead of the entire line. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com Index: src/etc/root/dot.cshrc =================================================================== RCS file: /home/ncvs/src/etc/root/dot.cshrc,v retrieving revision 1.27 diff -u -r1.27 dot.cshrc --- dot.cshrc 2000/05/28 15:09:31 1.27 +++ dot.cshrc 2001/01/09 17:44:00 @@ -27,4 +27,7 @@ set history = 100 set savehist = 100 set mail = (/var/mail/$USER) + if ( `basename $SHELL` == "tcsh" ) then + bindkey ^W backward-delete-word + endif endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 9:49:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 47C8C37B6D7 for ; Tue, 9 Jan 2001 09:49:02 -0800 (PST) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id C0047124D; Tue, 9 Jan 2001 12:49:01 -0500 (EST) Received: by fury.csh.rit.edu (Postfix, from userid 37404) id 03F1F2E194; Tue, 9 Jan 2001 12:48:58 -0500 (EST) Date: Tue, 9 Jan 2001 12:48:58 -0500 From: Jon Parise To: Archie Cobbs Cc: freebsd-current@freebsd.org Subject: Re: proposed small change to .cshrc Message-ID: <20010109124858.E23533@csh.rit.edu> References: <200101091745.f09HjEB51427@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <200101091745.f09HjEB51427@curve.dellroad.org>; from archie@dellroad.org on Tue, Jan 09, 2001 at 09:45:14AM -0800 X-Operating-System: SunOS 5.8 (sun4u) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: > + if ( `basename $SHELL` == "tcsh" ) then > + bindkey ^W backward-delete-word > + endif I generally test for tcsh like this: if ( $?tcsh ) then bindkey ^W backward-delete-word endif -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 10:46:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 4DE5937B698 for ; Tue, 9 Jan 2001 10:46:38 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f09IkTr49535; Tue, 9 Jan 2001 10:46:29 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Jan 2001 10:46:29 -0800 (PST) From: Matt Dillon Message-Id: <200101091846.f09IkTr49535@earth.backplane.com> To: Jon Parise Cc: Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: proposed small change to .cshrc References: <200101091745.f09HjEB51427@curve.dellroad.org> <20010109124858.E23533@csh.rit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: : :> + if ( `basename $SHELL` == "tcsh" ) then :> + bindkey ^W backward-delete-word :> + endif : :I generally test for tcsh like this: : : if ( $?tcsh ) then : bindkey ^W backward-delete-word : endif : :-- :Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology How about this: if ( $?tcsh ) then bindkey "^W" backward-delete-word bindkey -k up history-search-backward bindkey -k down history-search-forward endif For personal use I also do (for tcsh): set prompt = "%m:%/%# " But the Amiga-style integrated history search is the feature I use the most. Having a multi-thousand line history actually becomes useful. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 11:16:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D93C237B69E for ; Tue, 9 Jan 2001 11:16:06 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA10075 for ; Tue, 9 Jan 2001 11:16:06 -0800 Date: Tue, 9 Jan 2001 11:16:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: HEADSUP: kernel config required Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG isp_pci.c just moved from sys/pci to sys/dev/isp (for maintenance ease). You will need to reconfig kernels if you included this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 12: 6:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 239A937B400; Tue, 9 Jan 2001 12:05:57 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA04952; Tue, 9 Jan 2001 13:05:54 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA13366; Tue, 9 Jan 2001 13:05:48 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14939.28441.595746.233763@nomad.yogotech.com> Date: Tue, 9 Jan 2001 13:05:45 -0700 (MST) To: obrien@FreeBSD.ORG Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: make release still broken... In-Reply-To: <20010109091149.A76331@dragon.nuxi.com> References: <14713.979027880@critter> <20010109091149.A76331@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ===> rpcsvc > > rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h > > rpcgen: cannot find any C preprocessor (cpp) > > *** Error code 1 > > > Let me start a release. This means rpcgen has been using > /usr/libexec/cpp which is *only* for the compiler's use. rpcgen should > have been using /usr/bin/cpp all this time. From rpc_main.c #ifdef __FreeBSD__ #define SUNOS_CPP "/usr/libexec/cpp" Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 12:38:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 96FDE37B401 for ; Tue, 9 Jan 2001 12:38:40 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f09KpqJ00792; Tue, 9 Jan 2001 12:51:52 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101092051.f09KpqJ00792@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: dufault@hda.hda.com, current@freebsd.org Subject: Re: Fan speed control sony vaio lx800 slimtop In-reply-to: Your message of "Tue, 09 Jan 2001 23:47:42 +0900." <20010109234742E.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jan 2001 12:51:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Note also that Scott Long (scottl@freebsd.org) is also working on this, you will want to check with him to work out where he's up to... > > > Now I'd like to figure out how to turn the damn fan up and down. This > > machine is quiet under windows but sets the fan to high under FreeBSD > > and never turns it down. The fan has three settings - 0V, 6V and > > 12V. Under windows it stays between 0 and 6V. > > Thermal management implementation is in our queue. We'll create > policy manager for ACPI subsystems including thermal (Active, Passive > cooling etc.). Of course any help would be welcome :-) > > > I've tried "apm -h 1; apm -e 1;" hoping something would happen > > but it still doesn't slow down the fan. > > Currently we don't have any means to control fan device (except for > the machine specific tools). > > > If someone can sketch out a road map of what I should do I'll do the > > dirty work. I don't know about ACPI etc and so would appreciate a > > kick start. I've picked up the spec but haven't printed it out yet. > > You could find `3.10 Thermal Management' for overview and > `12 THERMAL MANAGEMENT' for detail in ACPI 2.0 spec. Also > `7.1 Declaring a Power Resource Object' and `10.6 Fan Device' > may help you. > > acpi-jp@jp.freebsd.org is a mailing list for ACPI development. > # English and Japanese are mixed :-) > If you are interested in it, please send a mail to > Majordomo@jp.freebsd.org with > subscribe acpi-jp > on body. > > Thanks > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 13:12:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from ocnet02.co.orange.ca.us (unknown [206.194.127.110]) by hub.freebsd.org (Postfix) with ESMTP id C598F37B69B for ; Tue, 9 Jan 2001 13:12:24 -0800 (PST) Received: from oc_bridge.co.orange.ca.us (marty [206.194.124.99]) by ocnet02.co.orange.ca.us (8.9.3+Sun/8.9.3) with ESMTP id NAA29661 for ; Tue, 9 Jan 2001 13:05:32 -0800 (PST) Received: by bridge.co.orange.ca.us with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 13:11:09 -0800 Message-ID: <3B69B479657BD311A7F700508B44257C0BA5AB91@ceodcxbdc2.co.orange.ca.us> From: "Sidwell, Josh" To: "'current@FreeBSD.ORG'" Subject: Current-ISO Date: Tue, 9 Jan 2001 13:11:06 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been unsucessfully trying to build an ISO image of the 5.0-CURRENT branch for the past several weeks. Is anyone aware of a tool to pull the latest tree and turn it into an ISO image? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 13:44:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id EBC7D37B400; Tue, 9 Jan 2001 13:43:52 -0800 (PST) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f09Lhmv07154; Tue, 9 Jan 2001 23:43:50 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id f09HrT901853; Tue, 9 Jan 2001 19:53:29 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A5B5019.7514E6CE@FreeBSD.org> Date: Tue, 09 Jan 2001 19:53:29 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@FreeBSD.org, obrien@FreeBSD.org Subject: Problems related to disappearnce of libgcc_r Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility shim is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_r.a automatically created by installworld would do the trick nicely. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 13:58:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id EF14E37B400; Tue, 9 Jan 2001 13:58:00 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA11993; Tue, 9 Jan 2001 16:57:39 -0500 (EST) Date: Tue, 9 Jan 2001 16:57:38 -0500 (EST) From: Daniel Eischen To: Maxim Sobolev Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: Problems related to disappearnce of libgcc_r In-Reply-To: <3A5B5019.7514E6CE@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Jan 2001, Maxim Sobolev wrote: > Hi, > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > ports to break. Therefore it would be nice if some form of compatibility shim > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_r.a > automatically created by installworld would do the trick nicely. Fix the ports to not use libgcc_r any longer. Wasn't linking to -lgcc_r just a hack to work around the problems we introduced just before 4.2R (also into -current)? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 13:58:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1CD9437B401; Tue, 9 Jan 2001 13:58:26 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA30131; Tue, 9 Jan 2001 13:58:25 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f09LwOg84892; Tue, 9 Jan 2001 13:58:24 -0800 (PST) (envelope-from obrien) Date: Tue, 9 Jan 2001 13:58:24 -0800 From: "David O'Brien" To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: Problems related to disappearnce of libgcc_r Message-ID: <20010109135824.A84872@dragon.nuxi.com> Reply-To: current@FreeBSD.org References: <3A5B5019.7514E6CE@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5B5019.7514E6CE@FreeBSD.org>; from sobomax@FreeBSD.org on Tue, Jan 09, 2001 at 07:53:29PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > ports to break. Therefore it would be nice if some form of compatibility shim > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_r.a > automatically created by installworld would do the trick nicely. I really don't want to propogate libgcc_r. Lets just fix the ports that break. They can be seen at http://bento.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 14: 3:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 1D00B37B401 for ; Tue, 9 Jan 2001 14:03:16 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f09M34G25565; Tue, 9 Jan 2001 14:03:05 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101092203.f09M34G25565@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Matt Dillon Cc: Jon Parise , Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: proposed small change to .cshrc In-Reply-To: <200101091846.f09IkTr49535@earth.backplane.com> Date: Tue, 09 Jan 2001 14:03:04 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > :On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: > : > :> + if ( `basename $SHELL` == "tcsh" ) then > :> + bindkey ^W backward-delete-word > :> + endif > : > :I generally test for tcsh like this: > : > : if ( $?tcsh ) then > : bindkey ^W backward-delete-word > : endif > : > :-- > :Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology > > How about this: > > if ( $?tcsh ) then > bindkey "^W" backward-delete-word > bindkey -k up history-search-backward > bindkey -k down history-search-forward > endif I was about to write a 'over my dead body' here, but I tried it out and discovered that the POLA (for tcsh users) is not too bad after all. In fact, I think I will add this to my .tcshrc :-) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 14: 4:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 62C6C37B400; Tue, 9 Jan 2001 14:04:05 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f09M45G25580; Tue, 9 Jan 2001 14:04:05 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101092204.f09M45G25580@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: current@FreeBSD.ORG Cc: Maxim Sobolev Subject: Re: Problems related to disappearnce of libgcc_r In-Reply-To: <20010109135824.A84872@dragon.nuxi.com> Date: Tue, 09 Jan 2001 14:04:05 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > ports to break. Therefore it would be nice if some form of compatibility sh im > > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ r.a > > automatically created by installworld would do the trick nicely. > > I really don't want to propogate libgcc_r. Lets just fix the ports that > break. They can be seen at http://bento.freebsd.org/ We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 14:22:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 9DEC537B402 for ; Tue, 9 Jan 2001 14:21:59 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA16104; Tue, 9 Jan 2001 17:21:27 -0500 (EST) Date: Tue, 9 Jan 2001 17:21:27 -0500 (EST) From: Daniel Eischen To: Peter Wemm Cc: Matt Dillon , Jon Parise , Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: proposed small change to .cshrc In-Reply-To: <200101092203.f09M34G25565@mobile.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Jan 2001, Peter Wemm wrote: > Matt Dillon wrote: > > > > :On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: > > : > > :> + if ( `basename $SHELL` == "tcsh" ) then > > :> + bindkey ^W backward-delete-word > > :> + endif > > : > > :I generally test for tcsh like this: > > : > > : if ( $?tcsh ) then > > : bindkey ^W backward-delete-word > > : endif > > : > > :-- > > :Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology > > > > How about this: > > > > if ( $?tcsh ) then > > bindkey "^W" backward-delete-word > > bindkey -k up history-search-backward > > bindkey -k down history-search-forward > > endif > > I was about to write a 'over my dead body' here, but I tried it out and > discovered that the POLA (for tcsh users) is not too bad after all. In > fact, I think I will add this to my .tcshrc :-) Just use bash ;-) -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 14:23:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id B1C1037B402; Tue, 9 Jan 2001 14:23:35 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA16328; Tue, 9 Jan 2001 17:23:09 -0500 (EST) Date: Tue, 9 Jan 2001 17:23:09 -0500 (EST) From: Daniel Eischen To: Peter Wemm Cc: current@FreeBSD.ORG, Maxim Sobolev Subject: Re: Problems related to disappearnce of libgcc_r In-Reply-To: <200101092204.f09M45G25580@mobile.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Jan 2001, Peter Wemm wrote: > "David O'Brien" wrote: > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > ports to break. Therefore it would be nice if some form of compatibility sh > im > > > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ > r.a > > > automatically created by installworld would do the trick nicely. > > > > I really don't want to propogate libgcc_r. Lets just fix the ports that > > break. They can be seen at http://bento.freebsd.org/ > > We need to be a little careful for ports that are supposed to work on > RELENG_4 and -CURRENT. OSVERSION checks? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:12: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 31E9637B401 for ; Tue, 9 Jan 2001 16:11:45 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0A090G72437; Tue, 9 Jan 2001 16:09:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 09 Jan 2001 16:11:16 -0800 (PST) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: bogus microuptime() warnings? Cc: current@FreeBSD.org, Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Jan-01 Dag-Erling Smorgrav wrote: > Poul-Henning Kamp writes: >> No, this is either a problem reading the i8254 timecounter reliably >> or an interrupt latency problem. > > Given that this is -CURRENT, interrupt latency is a likely > explanation... > > Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" > with the latest -CURRENT than I used to... Which soundcard? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:14:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 801A637B400; Tue, 9 Jan 2001 16:13:53 -0800 (PST) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0A0Dkv08951; Wed, 10 Jan 2001 02:13:48 +0200 Received: (from max@localhost) by vic.sabbo.net (8.11.1/8.9.3) id f0A0Dla02999; Wed, 10 Jan 2001 02:13:47 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200101100013.f0A0Dla02999@vic.sabbo.net> Subject: Re: Problems related to disappearnce of libgcc_r To: peter@netplex.com.au (Peter Wemm) Date: Wed, 10 Jan 2001 02:13:42 +0200 (EET) Cc: current@FreeBSD.ORG, sobomax@FreeBSD.ORG (Maxim Sobolev) In-Reply-To: <200101092204.f09M45G25580@mobile.wemm.org> from "Peter Wemm" at Jan 09, 2001 02:04:05 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "David O'Brien" wrote: > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > ports to break. Therefore it would be nice if some form of compatibility sh > im > > > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ > r.a > > > automatically created by installworld would do the trick nicely. > > > > I really don't want to propogate libgcc_r. Lets just fix the ports that > > break. They can be seen at http://bento.freebsd.org/ > > We need to be a little careful for ports that are supposed to work on > RELENG_4 and -CURRENT. Yes, it's why I think we need this compatability hack. Bloating all 20+ ports that have to use gcc_r on 4-STABLE and downwards with OSVERSION check is PITA. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:20:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 2D3E837B400; Tue, 9 Jan 2001 16:20:11 -0800 (PST) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0A0K6v09078; Wed, 10 Jan 2001 02:20:06 +0200 Received: (from max@localhost) by vic.sabbo.net (8.11.1/8.9.3) id f0A0K6j03025; Wed, 10 Jan 2001 02:20:06 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200101100020.f0A0K6j03025@vic.sabbo.net> Subject: Re: Problems related to disappearnce of libgcc_r To: eischen@vigrid.com (Daniel Eischen) Date: Wed, 10 Jan 2001 02:20:01 +0200 (EET) Cc: peter@netplex.com.au (Peter Wemm), current@FreeBSD.ORG, sobomax@FreeBSD.ORG (Maxim Sobolev) In-Reply-To: from "Daniel Eischen" at Jan 09, 2001 05:23:09 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Tue, 9 Jan 2001, Peter Wemm wrote: > > "David O'Brien" wrote: > > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > > ports to break. Therefore it would be nice if some form of compatibility sh > > im > > > > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ > > r.a > > > > automatically created by installworld would do the trick nicely. > > > > > > I really don't want to propogate libgcc_r. Lets just fix the ports that > > > break. They can be seen at http://bento.freebsd.org/ > > > > We need to be a little careful for ports that are supposed to work on > > RELENG_4 and -CURRENT. > > OSVERSION checks? Yes, I know it's possible, but to provide a hack in one place istead of 20+ places (find /usr/ports -type f | xargs grep -l gcc_r | wc -l) is much easier both in the terms of efforts and testing required. After all, it would only cost us one inode for symlink and probably two-three lines in appropriate Makefile. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:24: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BA05837B400; Tue, 9 Jan 2001 16:23:52 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA31014; Tue, 9 Jan 2001 16:23:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0A0Ne485681; Tue, 9 Jan 2001 16:23:40 -0800 (PST) (envelope-from obrien) Date: Tue, 9 Jan 2001 16:23:40 -0800 From: "David O'Brien" To: Peter Wemm Cc: current@FreeBSD.ORG, Maxim Sobolev Subject: Re: Problems related to disappearnce of libgcc_r Message-ID: <20010109162340.A85531@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010109135824.A84872@dragon.nuxi.com> <200101092204.f09M45G25580@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101092204.f09M45G25580@mobile.wemm.org>; from peter@netplex.com.au on Tue, Jan 09, 2001 at 02:04:05PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 02:04:05PM -0800, Peter Wemm wrote: > We need to be a little careful for ports that are supposed to work on > RELENG_4 and -CURRENT. RELENG_4 and -current are the same in this reguard. I should bump __FreeBSD_version in both and then people can use that as the cut over date. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:24:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A3D3A37B404; Tue, 9 Jan 2001 16:24:22 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA31019; Tue, 9 Jan 2001 16:24:21 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0A0OKB85692; Tue, 9 Jan 2001 16:24:20 -0800 (PST) (envelope-from obrien) Date: Tue, 9 Jan 2001 16:24:19 -0800 From: "David O'Brien" To: Maxim Sobolev Cc: Daniel Eischen , Peter Wemm , current@FreeBSD.ORG Subject: Re: Problems related to disappearnce of libgcc_r Message-ID: <20010109162419.B85531@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200101100020.f0A0K6j03025@vic.sabbo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101100020.f0A0K6j03025@vic.sabbo.net>; from sobomax@FreeBSD.ORG on Wed, Jan 10, 2001 at 02:20:01AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 02:20:01AM +0200, Maxim Sobolev wrote: > Yes, I know it's possible, but to provide a hack in one place istead of > 20+ places (find /usr/ports -type f | xargs grep -l gcc_r | wc -l) is > much easier both in the terms of efforts and testing required. After > all, it would only cost us one inode for symlink and probably two-three > lines in appropriate Makefile. The answer is "NO". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:30:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from genesis.k.pl (genesis.korbank.pl [195.117.162.253]) by hub.freebsd.org (Postfix) with ESMTP id D524437B400 for ; Tue, 9 Jan 2001 16:30:28 -0800 (PST) Received: (from ns88@localhost) by genesis.k.pl (8.11.1/8.11.1) id f0A0Tma01051 for freebsd-current@freebsd.org; Wed, 10 Jan 2001 01:29:48 +0100 (CET) (envelope-from ns88) Date: Wed, 10 Jan 2001 01:29:48 +0100 From: Tomasz Paszkowski To: freebsd-current@freebsd.org Subject: securelevel and sysctl Message-ID: <20010110012948.A19896@genesis.k.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'am working on module, which catches __sysctl system call, and on securelevel grater than 3, refuse any changes of sysctl oids. Are there any problems, which might happen after blocking sysctl oids change ? AFAIR there is no such application running in user Space,which requires ability to change sysctl oids,is there ? Secondly I'was thinking about oids,which are needed for user space aplications to work. I figured out,that vi use some (I didn't check which one) oid on startup, so is there a list of oids used by user space applications ? -- _ _ _ _ _ / \ | | / / / \ / \ ---------- Tomasz Paszkowski --- NS88-6BONE -------- | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix ================ /_/ \__/ /_/ \_/ \_/ --- Linux is for people who hate Microsoft --------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:35:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id EB36E37B400 for ; Tue, 9 Jan 2001 16:35:11 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id QAA70084; Tue, 9 Jan 2001 16:35:09 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id f0A0Z8A52612; Tue, 9 Jan 2001 16:35:08 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101100035.f0A0Z8A52612@curve.dellroad.org> Subject: Re: proposed small change to .cshrc In-Reply-To: <200101091846.f09IkTr49535@earth.backplane.com> "from Matt Dillon at Jan 9, 2001 10:46:29 am" To: Matt Dillon Date: Tue, 9 Jan 2001 16:35:08 -0800 (PST) Cc: Jon Parise , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > if ( $?tcsh ) then > bindkey "^W" backward-delete-word > bindkey -k up history-search-backward > bindkey -k down history-search-forward > endif Why do you need the 'up' and 'down' ones.. doesn't it already do that without explicit configuration? -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 16:53:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 088DD37B401 for ; Tue, 9 Jan 2001 16:53:01 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0A0qTi54396; Tue, 9 Jan 2001 16:52:29 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Jan 2001 16:52:29 -0800 (PST) From: Matt Dillon Message-Id: <200101100052.f0A0qTi54396@earth.backplane.com> To: Archie Cobbs Cc: Jon Parise , freebsd-current@FreeBSD.ORG Subject: Re: proposed small change to .cshrc References: <200101100035.f0A0Z8A52612@curve.dellroad.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt Dillon writes: :> if ( $?tcsh ) then :> bindkey "^W" backward-delete-word :> bindkey -k up history-search-backward :> bindkey -k down history-search-forward :> endif : :Why do you need the 'up' and 'down' ones.. doesn't it already do that :without explicit configuration? : :-Archie This is the history *search* function. Lets say you did a complex 'find' command 5 minutes ago and a hundred intervening commands since, and you want to run the 'find' again. You type: % fin If you did a bunch of find's, hit up arrow as many times as necessary. You can type as few or as many characters as you like prior to hitting the up arrow, depends on what you are looking for. If you just hit the up or down arrow without having partial text on the line, it works just like normal history. Once you start using it, you will never be able to go back. This is how the Amiga used to do it. It's the only right way. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 17:39:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 05A0637B400 for ; Tue, 9 Jan 2001 17:38:54 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA09289; Wed, 10 Jan 2001 12:38:43 +1100 Date: Wed, 10 Jan 2001 12:39:36 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: sio && serial console in -current? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Jan 2001, Matthew Jacob wrote: > Something wierd has been happening lately- the serial console on my i386 > machine works fine up until init is forked.. THen the output is mangled, and > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > like: > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd This may be caused by inconsistent settings in /etc/rc.serial. /etc/rc.serial should rarely be changed from its default of doing nothing. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 17:53:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 994F637B402 for ; Tue, 9 Jan 2001 17:53:09 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA12044; Tue, 9 Jan 2001 17:53:05 -0800 Date: Tue, 9 Jan 2001 17:53:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: sio && serial console in -current? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good guess, I shouldn't wonder, but: quarm.feral.com > diff /etc/rc.serial /usr/src/etc/ quarm.feral.com > On Wed, 10 Jan 2001, Bruce Evans wrote: > On Mon, 8 Jan 2001, Matthew Jacob wrote: > > > Something wierd has been happening lately- the serial console on my i386 > > machine works fine up until init is forked.. THen the output is mangled, and > > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > > like: > > > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd > > This may be caused by inconsistent settings in /etc/rc.serial. > /etc/rc.serial should rarely be changed from its default of doing nothing. > > Bruce > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 21: 4:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id CEB4037B401 for ; Tue, 9 Jan 2001 21:04:19 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA01689 for ; Wed, 10 Jan 2001 00:04:18 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA24584 for ; Wed, 10 Jan 2001 00:04:18 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA24576 for ; Wed, 10 Jan 2001 00:04:17 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Wed, 10 Jan 2001 00:04:17 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: YES! laptop installing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is to let everyone know that right now as I type I am setting up FreeBSD to start downloading over my cardbus ethernet card. It seems to work great except it doesn't beep when the card enables, but that's fine with me. :-) ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 22:51:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id AC7D537B400 for ; Tue, 9 Jan 2001 22:51:37 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0A6pEI03345; Wed, 10 Jan 2001 08:51:18 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101100651.f0A6pEI03345@gratis.grondar.za> To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: YES! laptop installing References: In-Reply-To: ; from Kenneth Wayne Culver "Wed, 10 Jan 2001 00:04:17 EST." Date: Wed, 10 Jan 2001 08:51:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is to let everyone know that right now as I type I am setting up > FreeBSD to start downloading over my cardbus ethernet card. It seems to > work great except it doesn't beep when the card enables, but that's fine > with me. :-) What card? My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy MAC address, and then doesn't work. It doesn't even go UP. MAC=00:00:80:00:00:80, FWIW. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 22:55:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id C4D3E37B400 for ; Tue, 9 Jan 2001 22:55:15 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA11538; Wed, 10 Jan 2001 01:54:57 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA03252; Wed, 10 Jan 2001 01:54:56 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA03248; Wed, 10 Jan 2001 01:54:56 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Wed, 10 Jan 2001 01:54:56 -0500 (EST) From: Kenneth Wayne Culver To: Mark Murray Cc: freebsd-current@FreeBSD.ORG Subject: Re: YES! laptop installing In-Reply-To: <200101100651.f0A6pEI03345@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a 3ccfe575ct-d, it works great, I just installed using it by making my own GENERIC kernel with the cardbus stuff on it, and putting it on an install boot floppy instead of the one that normally comes on it. I'm not sure the pmtimer is working though, and I keep getting dmesg: malloc failed ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 10 Jan 2001, Mark Murray wrote: > > This is to let everyone know that right now as I type I am setting up > > FreeBSD to start downloading over my cardbus ethernet card. It seems to > > work great except it doesn't beep when the card enables, but that's fine > > with me. :-) > > What card? > > My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy > MAC address, and then doesn't work. It doesn't even go UP. > > MAC=00:00:80:00:00:80, FWIW. > > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 23: 9:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 00E4937B400; Tue, 9 Jan 2001 23:08:59 -0800 (PST) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA04780; Wed, 10 Jan 2001 02:08:57 -0500 (EST) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id CAA18222; Wed, 10 Jan 2001 02:08:57 -0500 (EST) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA18218; Wed, 10 Jan 2001 02:08:56 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Wed, 10 Jan 2001 02:08:56 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Cc: imp@freebsd.org Subject: pmtimer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure what pmtimer is supposed to do. Isn't it supposed to give support for the broken statclock on laptops? I saw my friend running 4.1 with some patches that allowed him to use the statclock (and the rtc device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to do anything; and I couldn't find a manpage on it ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 9 23:30:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 1E78737B400 for ; Tue, 9 Jan 2001 23:29:53 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id IAA29139; Wed, 10 Jan 2001 08:29:51 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14GFhe-0007un-00 for ; Wed, 10 Jan 2001 08:29:50 +0100 Date: Wed, 10 Jan 2001 08:29:50 +0100 From: Szilveszter Adam To: current@FreeBSD.org Subject: Re: bogus microuptime() warnings? Message-ID: <20010110082950.A30003@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , current@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Jan 09, 2001 at 04:11:16PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 04:11:16PM -0800, John Baldwin wrote: > > Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" > > with the latest -CURRENT than I used to... > > Which soundcard? SB 64 AWE ISA PNP... almost no hwptr... messages any more and sound is no longer popping under normal circumstances. (even if eg disk io is in progress) I was already rejoicing about this to the list in the last millenium... ( 30th December to be precise:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 1:37:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C804337B400; Wed, 10 Jan 2001 01:37:21 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id KAA03912; Wed, 10 Jan 2001 10:37:20 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: John Baldwin Cc: current@FreeBSD.org, Poul-Henning Kamp Subject: Re: bogus microuptime() warnings? References: From: Dag-Erling Smorgrav Date: 10 Jan 2001 10:37:18 +0100 In-Reply-To: John Baldwin's message of "Tue, 09 Jan 2001 16:11:16 -0800 (PST)" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > On 09-Jan-01 Dag-Erling Smorgrav wrote: > > Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" > > with the latest -CURRENT than I used to... > Which soundcard? SoundBlaster Vibra 16X. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 2: 7:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from flute.daconcepts.dyndns.org (wks-29-177-219.kscable.com [24.29.177.219]) by hub.freebsd.org (Postfix) with ESMTP id 4F10C37B400 for ; Wed, 10 Jan 2001 02:07:30 -0800 (PST) Received: from localhost (natedac@localhost) by flute.daconcepts.dyndns.org (8.11.1/8.11.1) with ESMTP id f0AA7ph04843 for ; Wed, 10 Jan 2001 04:07:52 -0600 (CST) (envelope-from natedac@kscable.com) X-Authentication-Warning: flute.daconcepts.dyndns.org: natedac owned process doing -bs Date: Wed, 10 Jan 2001 04:07:50 -0600 (CST) From: Nate Dannenberg X-Sender: natedac@flute.daconcepts.dyndns.org To: current@freebsd.org Subject: device driver oddities. (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using 5.0-Current (actually intended to get 4.2-Stable, but anyways)... It appears there is a problem with the way the system is dealing with the mouse, keyboard, and sound devices. My source tree was updated via CVSup just a day or so ago, and compiled on that day, with no errors. Kernel has since been re-compiled for my usual settings (changes in the way sound devices are handled was noted and adapted), and of course to trim out some unneeded stuff (SCSI and RAID drivers, etc) Consider this line from the obvious Beach Boys hit (an mp3 playing under mpg123 0.59r): "I wish they all could be california... girls..." At one point, the sound, mouse, and keyboard all stalled in the middle of the word "be". It sounded like: "I wish they all could brbrbrbrbrbrbrbrbebebe california... girls..." At that moment, the mouse stops moving, for as long as the sound stalls, and the keyboard will insert a garbage character to whatever application I am focused on, if I happen to be pressing a key at that moment. This happens frequently when I move the mouse around, and moreso if something else occurs along with that movement, such as a focus change from one window to another. Occasionally, typing on the keyboard also induces a stall in the sound and mouse drivers. Machine: Compaq Presario 4764. P166 MMX, 24 Megs RAM. Sound: ESS Audiodrive 18xx series on the motherboard, non PnP. Mouse: A typical IBM three-button wheel mouse. Environment: X Free86 3.3.6, Gnome/Sawmill. (Problem is not limited to X, it also happens at the consolem, before X is even started). To me this looks like an IRQ handling problem, but I am not certain. On my hobby platform, IRQ software malfunctions would be the first thing to look for if such a problem were to occur. My applications (mostly ports and packages) from 4.1 have not yet been updated. This same problem also exists in 4.2-Release as obtained via kern.flp and mfsroot.flp images for 4.2-Release, FTP Install. There have been no hardware changes made in several months. In 4.1-Release (also obtained via FTP Install), this problem does NOT exist. I also verified that the problem goes away when 4.1 is present by "downgrading" back to 4.1-Release from 4.2-Release (using a rather brute-force method to insure a clean install). In all cases I have of course obtained kernel source during the install, and always compile it using the same settings (or equivalent, as with sound parameters in 5.0-C compared to 4.1-R). After mentioning my guess about possible IRQ problems in #freebsdhelp on IRC/EFnet, someone suggested I take a look at the output of vmstat -i and dmesg. Here are those outputs: Output from vmstat: interrupt total rate stray irq0 1 0 stray irq6 1 0 stray irq7 1 0 stray irq15 1 0 ata0 irq14 109593 1 ata1 irq15 10 0 fdc0 irq6 1 0 atkbd0 irq1 144561 1 psm0 irq12 107832 1 sio0 irq4 1 0 sbc0 irq5 1051032 12 ep0 irq3 40721 0 clk irq0 8750437 99 rtc irq8 11197886 127 lpt0 irq7 245507 2 Total 21647585 247 Output from dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #3: Tue Jan 9 03:04:54 CST 2001 root@flute.daconcepts.dyndns.org:/usr/src/sys/compile/FLUTE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 167046462 Hz CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping = 4 Features=0x8001bf real memory = 25165824 (24576K bytes) config> di sio1 config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 20930560 (20440K bytes) Preloaded elf kernel "kernel" at 0xc039e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039e09c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1000-0x101f irq 11 at device 1.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 2.0 (no driver attached) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 pcm1: on sbc0 ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 3 on isa0 ep0: Ethernet address 00:a0:24:1c:21:e4 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled ad0: 2445MB [4969/16/63] at ata0-master WDMA2 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a pcm1: hwptr went backwards 2068 -> 1900 pcm1: hwptr went backwards 3088 -> 2996 pcm1: hwptr went backwards 3092 -> 3084 pcm1: hwptr went backwards 1044 -> 804 pcm1: hwptr went backwards 2068 -> 2032 pcm1: hwptr went backwards 16 -> 3876 pcm1: hwptr went backwards 2064 -> 1872 pcm1: hwptr went backwards 3092 -> 2992 pcm1: hwptr went backwards 3088 -> 3004 -- ___________________________________ _____ _____ | _///@@@| | | natedac@kscable.com /'//ZZ@@|____ | | |'''/ |'/@7 | | http://home.kscable.com/natedac |`'| `~~' | | | `| .--. | | C64/C128 - What's *YOUR* hobby? | `\____|___\ | | \_ | | |___________________________________ \_____| _____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 2:14:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from flute.daconcepts.dyndns.org (wks-29-177-219.kscable.com [24.29.177.219]) by hub.freebsd.org (Postfix) with ESMTP id 8522D37B400 for ; Wed, 10 Jan 2001 02:14:15 -0800 (PST) Received: from localhost (natedac@localhost) by flute.daconcepts.dyndns.org (8.11.1/8.11.1) with ESMTP id f0AAEbE04868 for ; Wed, 10 Jan 2001 04:14:38 -0600 (CST) (envelope-from natedac@kscable.com) X-Authentication-Warning: flute.daconcepts.dyndns.org: natedac owned process doing -bs Date: Wed, 10 Jan 2001 04:14:37 -0600 (CST) From: Nate Dannenberg X-Sender: natedac@flute.daconcepts.dyndns.org To: current@freebsd.org Subject: device driver oddities Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Addendum to previous message describing what seems like IRQ problems... One thing I forgot to mention, and which is the whole reason I decided to send this to the list, is that the ESS Audiodrive does not play in Stereo under 4.2-Release or 5.0-Current. Sound is in mono, out of both speakers. The music being tested shows very clear, clean stereo separation under 4.1-Release. The upgrade to 4.2-Release was done via Sysinstall, which I eventually downgraded back to 4.1-Release via the brute force "delete-everything-except-/pub-and-/proc-and-do-an-FTP-Install". At that point (after I compiled my kernel as usual), sound returned to normal. The upgrade path from 4.1-Release to 5.0-Current was of course done via CVSup/make buildworld/make installworld followed by a normal kernel recompile to get my preferred settings into place. -- ___________________________________ _____ _____ | _///@@@| | | natedac@kscable.com /'//ZZ@@|____ | | |'''/ |'/@7 | | http://home.kscable.com/natedac |`'| `~~' | | | `| .--. | | C64/C128 - What's *YOUR* hobby? | `\____|___\ | | \_ | | |___________________________________ \_____| _____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 3:53:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id 1269337B402 for ; Wed, 10 Jan 2001 03:53:13 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id DC6832DC0B; Wed, 10 Jan 2001 12:57:02 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id C875C781B; Wed, 10 Jan 2001 12:52:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id C18A510E1B; Wed, 10 Jan 2001 12:52:24 +0100 (CET) Date: Wed, 10 Jan 2001 12:52:17 +0100 (CET) From: Andrzej Bialecki To: Tomasz Paszkowski Cc: freebsd-current@freebsd.org Subject: Re: securelevel and sysctl In-Reply-To: <20010110012948.A19896@genesis.k.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jan 2001, Tomasz Paszkowski wrote: > > I'am working on module, which catches __sysctl system call, and on > securelevel grater than 3, refuse any changes of sysctl oids. Are there any You might want to take a look at SPY module (http://people.freebsd.org/~abial/spy). > problems, which might happen after blocking sysctl oids change ? > AFAIR there is no such application running in user Space,which requires > ability to change sysctl oids,is there ? Several oids are changed on system startup. Others are accessed read-only to provide system information. > Secondly I'was thinking about oids,which are needed for user space aplications > to work. I figured out,that vi use some (I didn't check which one) oid on > startup, so is there a list of oids used by user space applications ? Well, it depends on what the user applications want to access, doesn't it :-). Theoretically, this list could be all oids. Practically, it depends on the user applications that are installed... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 4:26:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4DC1B37B400 for ; Wed, 10 Jan 2001 04:26:18 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Jan 2001 12:26:13 +0000 (GMT) Date: Wed, 10 Jan 2001 12:26:12 +0000 From: David Malone To: Matt Dillon Cc: Archie Cobbs , Jon Parise , freebsd-current@FreeBSD.ORG Subject: Re: proposed small change to .cshrc Message-ID: <20010110122612.A14873@walton.maths.tcd.ie> References: <200101100035.f0A0Z8A52612@curve.dellroad.org> <200101100052.f0A0qTi54396@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101100052.f0A0qTi54396@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Jan 09, 2001 at 04:52:29PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 04:52:29PM -0800, Matt Dillon wrote: > If you just hit the up or down arrow without having partial text on the > line, it works just like normal history. Once you start using it, > you will never be able to go back. As a side note - this is usually mapped to escpae-p - it is very useful. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 6:23:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 06BC637B400 for ; Wed, 10 Jan 2001 06:23:16 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f0AEN1T41137 for freebsd-current@freebsd.org; Wed, 10 Jan 2001 15:23:01 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.1/8.11.0) with ESMTP id f0AEMUi23844 for ; Wed, 10 Jan 2001 15:22:37 +0100 (CET) (envelope-from leifn@neland.dk) Date: Wed, 10 Jan 2001 15:22:30 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: rebuilding sendmail without building world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do I remake sendmail without making a buildworld? I'm experimenting with cyrus-sasl and sendmail. cd /usr/src/contrib/sendmail && make doesn't work, because there is no Build there. I could import the original source from sendmail.org, but I'd rather not; I'd prefer using the paths and flags from buildworld. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 6:27:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id BFE8F37B401 for ; Wed, 10 Jan 2001 06:27:11 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id f0AEPpP71146; Wed, 10 Jan 2001 16:25:51 +0200 (EET) (envelope-from ru) Date: Wed, 10 Jan 2001 16:25:51 +0200 From: Ruslan Ermilov To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: rebuilding sendmail without building world Message-ID: <20010110162551.A48389@sunbay.com> Mail-Followup-To: Leif Neland , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from leifn@neland.dk on Wed, Jan 10, 2001 at 03:22:30PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 03:22:30PM +0100, Leif Neland wrote: > How do I remake sendmail without making a buildworld? > > I'm experimenting with cyrus-sasl and sendmail. > > cd /usr/src/contrib/sendmail && make > > doesn't work, because there is no Build there. > > I could import the original source from sendmail.org, but I'd rather > not; I'd prefer using the paths and flags from buildworld. > (cd /usr/src; grep NO_SENDMAIL */Makefile) should give you an idea. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 6:38: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 3615537B400; Wed, 10 Jan 2001 06:37:51 -0800 (PST) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id f0AEbfk07136; Wed, 10 Jan 2001 23:37:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: culverk@wam.umd.edu Cc: freebsd-current@freebsd.org, imp@freebsd.org Subject: Re: pmtimer In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010110233740Z.iwasaki@jp.FreeBSD.org> Date: Wed, 10 Jan 2001 23:37:40 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > I'm not sure what pmtimer is supposed to do. Isn't it supposed to give > support for the broken statclock on laptops? I saw my friend running 4.1 > with some patches that allowed him to use the statclock (and the rtc > device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to > do anything; and I couldn't find a manpage on it Please refer to src/UPDATING for -current. The new pmtimer device is necessary for laptops. Failure to include the device will cause suspended laptops losing time when they resume. Currently pmtimer won't solve the broken statclock problem... The timer related code at suspend/resume time have been moved from APM to pmtimer so that ACPI (includes new power management system) use pmtimer at sleep/wakeup time as well. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 6:59:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 6EEBE37B402; Wed, 10 Jan 2001 06:59:13 -0800 (PST) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id f0AExAk27792; Wed, 10 Jan 2001 23:59:10 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, dufault@hda.hda.com, current@freebsd.org, scottl@freebsd.org Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101092051.f09KpqJ00792@mass.osd.bsdi.com> References: <20010109234742E.iwasaki@jp.FreeBSD.org> <200101092051.f09KpqJ00792@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010110235910A.iwasaki@jp.FreeBSD.org> Date: Wed, 10 Jan 2001 23:59:10 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 7 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Note also that Scott Long (scottl@freebsd.org) is also working on this, > you will want to check with him to work out where he's up to... OK, I intended to try acpi_thermal hacking for the next target, now I can be a tester and feed back something for Scott's hack :-) Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 7: 7:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id B677837B401; Wed, 10 Jan 2001 07:07:26 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f0AF7PF09486; Wed, 10 Jan 2001 16:07:25 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.1/8.11.0) with ESMTP id f0AF77i24223; Wed, 10 Jan 2001 16:07:11 +0100 (CET) (envelope-from leifn@neland.dk) Date: Wed, 10 Jan 2001 16:07:07 +0100 (CET) From: Leif Neland To: Ruslan Ermilov Cc: freebsd-current@FreeBSD.ORG Subject: Re: rebuilding sendmail without building world In-Reply-To: <20010110162551.A48389@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jan 2001, Ruslan Ermilov wrote: > On Wed, Jan 10, 2001 at 03:22:30PM +0100, Leif Neland wrote: > > How do I remake sendmail without making a buildworld? > > > > I'm experimenting with cyrus-sasl and sendmail. > > > > cd /usr/src/contrib/sendmail && make > > > > doesn't work, because there is no Build there. > > > > I could import the original source from sendmail.org, but I'd rather > > not; I'd prefer using the paths and flags from buildworld. > > > (cd /usr/src; grep NO_SENDMAIL */Makefile) should give you an idea. > Yes, the idea I got was: cd /usr/src/usr.sbin/sendmail && make && make install Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 7:44:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 1A2FD37B402; Wed, 10 Jan 2001 07:44:33 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f0AFg8n15964; Wed, 10 Jan 2001 10:42:08 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101101542.f0AFg8n15964@hda.hda.com> Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <20010110235910A.iwasaki@jp.FreeBSD.org> from Mitsuru IWASAKI at "Jan 10, 2001 11:59:10 pm" To: Mitsuru IWASAKI Date: Wed, 10 Jan 2001 10:41:31 -0500 (EST) Cc: msmith@freebsd.org, current@freebsd.org, scottl@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Note also that Scott Long (scottl@freebsd.org) is also working on this, > > you will want to check with him to work out where he's up to... > > OK, I intended to try acpi_thermal hacking for the next target, now > I can be a tester and feed back something for Scott's hack :-) Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump that I submitted for the ACPI collection. I'm not sure where that collection is - I don't see it off www.jp.freebsd.org/acpi, if anyone wants to see that .asl file I can put it somewhere public. I also haven't found any "PNPxxxx" devices corresponding to an ACPI fan (I forget the exact number) during boot -v. Would I have to do anything special to see it? If anyone has any other ideas of what to do let me know - I'm wondering if throttling down the CPU turns down the fan. In the meantime I've made terrific progress by putting "dynamat" sound absorbing material on the bottom of the plastic drum-like base of the Vaio, it is quieter and now my desk doesn't vibrate when the fan is on high. (www.dynamat.com, new web site in progress) Next I'll open it up and put dynamat on the inside of the plastic - I assume most heat loss is by convection and this won't make much difference. Once I do get the fan throttling working I'll have a real quiet system. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 7:57:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from exchange1.vikingnetworks.net (unknown [63.140.222.6]) by hub.freebsd.org (Postfix) with ESMTP id 55F1A37B404 for ; Wed, 10 Jan 2001 07:57:25 -0800 (PST) Received: from Gary (63.140.222.17 [63.140.222.17]) by exchange1.vikingnetworks.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CPYS0NCR; Wed, 10 Jan 2001 10:50:39 -0500 Message-ID: <006d01c07b1d$ef865480$2d01a8c0@Gary> From: "Gary Lee" To: "David Malone" , "Matt Dillon" Cc: "Archie Cobbs" , "Jon Parise" , References: <200101100035.f0A0Z8A52612@curve.dellroad.org> <200101100052.f0A0qTi54396@earth.backplane.com> <20010110122612.A14873@walton.maths.tcd.ie> Subject: unsubscribe freebsd-current Date: Wed, 10 Jan 2001 10:56:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please Take me off of your list. THANK YOU unsubscribe freebsd-current > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 8:30:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 4DE2B37B401 for ; Wed, 10 Jan 2001 08:30:02 -0800 (PST) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id f0AGU0k74002 for ; Thu, 11 Jan 2001 01:30:00 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: current@freebsd.org Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101101542.f0AFg8n15964@hda.hda.com> References: <20010110235910A.iwasaki@jp.FreeBSD.org> <200101101542.f0AFg8n15964@hda.hda.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010111012957C.iwasaki@jp.FreeBSD.org> Date: Thu, 11 Jan 2001 01:29:57 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 26 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Cc trimed] Quick news from acpi-jp :-) > Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump > that I submitted for the ACPI collection. I'm not sure where that > collection is - I don't see it off www.jp.freebsd.org/acpi, if > anyone wants to see that .asl file I can put it somewhere public. Sorry, project page haven't been updated for a long time. CVSuping ACPI data collection is also with following supfile. ----------------------------------------- *default host=cvsup.jp.FreeBSD.org *default base=/home/iwasaki/ACPI-data # XXX *default prefix=/home/iwasaki/ACPI-data # XXX *default release=cvs tag=. *default delete use-rel-suffix *default compress jp-acpi-data ----------------------------------------- Also cvsweb at http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 9:28:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 77F4E37B402 for ; Wed, 10 Jan 2001 09:28:29 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0AHSHe59692; Wed, 10 Jan 2001 09:28:17 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Jan 2001 09:28:17 -0800 (PST) From: Matt Dillon Message-Id: <200101101728.f0AHSHe59692@earth.backplane.com> To: David Malone Cc: Archie Cobbs , Jon Parise , freebsd-current@FreeBSD.ORG Subject: Re: proposed small change to .cshrc References: <200101100035.f0A0Z8A52612@curve.dellroad.org> <200101100052.f0A0qTi54396@earth.backplane.com> <20010110122612.A14873@walton.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Tue, Jan 09, 2001 at 04:52:29PM -0800, Matt Dillon wrote: : :> If you just hit the up or down arrow without having partial text on the :> line, it works just like normal history. Once you start using it, :> you will never be able to go back. : :As a side note - this is usually mapped to escpae-p - it is very useful. : : David. Yes, but not as a multi-key keystroke. Up-arrow is a thousand times easier to hit. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 9:41:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 6C57837B401; Wed, 10 Jan 2001 09:41:04 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA28401; Wed, 10 Jan 2001 12:40:55 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA00399; Wed, 10 Jan 2001 12:40:55 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA00394; Wed, 10 Jan 2001 12:40:55 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Wed, 10 Jan 2001 12:40:54 -0500 (EST) From: Kenneth Wayne Culver To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, imp@freebsd.org Subject: Re: pmtimer In-Reply-To: <20010110233740Z.iwasaki@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, that's what I thought. A while back someone sent me some patches that fix the broken statclock and make it work on laptops, I can't remember his name right now. However those patches are against FreeBSD 4.1-RELEASE, and I'm not sure if they'd work for -CURRENT. I suppose I could do without the statclock for now, but it'd be nice to have :-) ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 10 Jan 2001, Mitsuru IWASAKI wrote: > Hi, > > > I'm not sure what pmtimer is supposed to do. Isn't it supposed to give > > support for the broken statclock on laptops? I saw my friend running 4.1 > > with some patches that allowed him to use the statclock (and the rtc > > device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to > > do anything; and I couldn't find a manpage on it > > Please refer to src/UPDATING for -current. > The new pmtimer device is necessary for laptops. Failure to > include the device will cause suspended laptops losing time > when they resume. > > Currently pmtimer won't solve the broken statclock problem... > The timer related code at suspend/resume time have been moved from APM > to pmtimer so that ACPI (includes new power management system) use > pmtimer at sleep/wakeup time as well. > > Thanks > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 12: 4:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0642337B401 for ; Wed, 10 Jan 2001 12:04:36 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA18673 for current@freebsd.org; Wed, 10 Jan 2001 21:04:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101102004.VAA18673@freebsd.dk> Subject: HEADSUP! change to atapi-cd driver and burncd To: current@freebsd.org Date: Wed, 10 Jan 2001 21:04:35 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The changes require that kernel and burncd are in sync... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 12:39:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 5DA2637B401 for ; Wed, 10 Jan 2001 12:39:33 -0800 (PST) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.1/8.11.1) id f0AKYxT60795 for current@FreeBSD.Org; Wed, 10 Jan 2001 12:34:59 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.200.120.86 ( [63.200.120.86]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Wed, 10 Jan 2001 12:34:59 -0800 Message-ID: <979158899.3a5cc773b0f7b@Mail.MexComUSA.net> Date: Wed, 10 Jan 2001 12:34:59 -0800 From: Edwin Culp To: current@FreeBSD.Org Subject: /boot/kernel/kernel: swap_pager_getswapspace: failed MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.6-cvs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am starting to get the following error. I've never seen it before and don't really understand why it should fail. Where should I start looking for the problem? /boot/kernel/kernel: swap_pager_getswapspace: failed This seems to have started in the last week. Thanks, ed -- EnContacto.Net - InternetSalon.Org - CafeMania.Net -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 13:35:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 07A8D37B401 for ; Wed, 10 Jan 2001 13:35:18 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0ALmog00877; Wed, 10 Jan 2001 13:48:50 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101102148.f0ALmog00877@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Dufault Cc: current@freebsd.org Subject: Re: Fan speed control sony vaio lx800 slimtop In-reply-to: Your message of "Wed, 10 Jan 2001 10:41:31 EST." <200101101542.f0AFg8n15964@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jan 2001 13:48:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump > that I submitted for the ACPI collection. I'm not sure where that > collection is - I don't see it off www.jp.freebsd.org/acpi, if > anyone wants to see that .asl file I can put it somewhere public. Is there a thermal zone *anywhere* (ACPI 2.0 moves it into _SB_, for example). > Would I have to do anything special to see it? If anyone has any > other ideas of what to do let me know - I'm wondering if throttling > down the CPU turns down the fan. It's possible that the EC is solely responsible for the fan, or that Sony decided in their infinite wisdom to do it all in a driver somewhere. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 15:22:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 1F27D37B69B for ; Wed, 10 Jan 2001 15:22:08 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0ANLu193317; Wed, 10 Jan 2001 15:21:57 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <979158899.3a5cc773b0f7b@Mail.MexComUSA.net> Date: Wed, 10 Jan 2001 15:22:09 -0800 (PST) From: John Baldwin To: Edwin Culp Subject: RE: /boot/kernel/kernel: swap_pager_getswapspace: failed Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Jan-01 Edwin Culp wrote: > I am starting to get the following error. I've never seen it before and > don't > really understand why it should fail. Where should I start looking for the > problem? > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > This seems to have started in the last week. > > Thanks, You are running out of swap space. Run fewer programs, buy more memory, add more swap space, or a combo of the three. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 16:44:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id CA92137B400; Wed, 10 Jan 2001 16:44:16 -0800 (PST) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.1/8.11.1) id f0B0dgN66049; Wed, 10 Jan 2001 16:39:42 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.200.120.86 ( [63.200.120.86]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Wed, 10 Jan 2001 16:39:42 -0800 Message-ID: <979173582.3a5d00ce0a0fb@Mail.MexComUSA.net> Date: Wed, 10 Jan 2001 16:39:42 -0800 From: Edwin Culp To: John Baldwin Cc: current@FreeBSD.org Subject: RE: /boot/kernel/kernel: swap_pager_getswapspace: failed References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.6-cvs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, John. I wish that it were that simple, that is if I am interpreting pstat and vmstat correctly. /root # pstat -s Device 1K-blocks Used Avail Capacity Type /dev/rad0s2b 262016 0 262016 0% Interleaved I have two another disks that aren't being used with an additional 512M of swap each that are not being mounted because this machine isn't carrying much load right now. /root # vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad2 in sy cs us sy id 0 2 0 118972 15100 849 0 1 0 834 4 0 0 414 3136 599 33 8 59 It really seems to be related to my upgrading to XFree86-4.0.2_3 and KDE-2. If no one else is seeing it, it isn't critical and with patience it'll show itself with a little time. Thanks, ed Quoting John Baldwin : > > On 10-Jan-01 Edwin Culp wrote: > > I am starting to get the following error. I've never seen it before and > > don't > > really understand why it should fail. Where should I start looking for > the > > problem? > > > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > > > This seems to have started in the last week. > > > > Thanks, > > You are running out of swap space. Run fewer programs, buy more memory, > add > more swap space, or a combo of the three. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > -- EnContacto.Net - InternetSalon.Org - CafeMania.Net -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 16:57:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A5BF237B698 for ; Wed, 10 Jan 2001 16:56:57 -0800 (PST) Received: from newsguy.com (p06-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.135]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id JAA19599; Thu, 11 Jan 2001 09:56:47 +0900 (JST) Message-ID: <3A5D0432.DC472940@newsguy.com> Date: Thu, 11 Jan 2001 09:54:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Wm Brian McCane Cc: current@FreeBSD.ORG Subject: Re: Problem installing on T20 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wm Brian McCane wrote: > > I have an IBM T20 laptop that I want to run FreeBSD on. I have run [etc] You have a problem which is technically called an "IBM laptop". IBM, in their infinite wisdom, decided to hibernate on the first partition it doesn't recognize (hypothesis #1) or on the first partition identified as 165 decimal (hypothesis #2). Whatever the case is, when the shitty thing boots, the BIOS checks said partition to see if the system had hybernated. Upon finding stuff there (the FreeBSD partition), it does something which screws the system and locks up. One possible fix to enable normal operation is creating an hybernate partition explicitly and a FreeBSD partition *after* that. You should be able to find out from IBM how to create an hybernate partition. If not, check the next fix. Another fix some people have resorted to is returning the laptop for a refund and, optionally, never again buying from IBM. You might also explain to them why you are doing so, but IBM does not support FreeBSD, so, technically speaking, they are not required to make it compatible with FreeBSD. Legend goes that Linux had the same problem at first (which is the origin of hypothesis #1) and got fixed by having IBM add their partition numbers to to BIOS as recognized partition numbers. It's beyond my ability to understand why they refuse to fix the #%'&%$%'& BIOS so it would use a SAFE hybernate partition number (like the one they used before). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 17:54:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7F65C37B402 for ; Wed, 10 Jan 2001 17:54:11 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0B1s2197255; Wed, 10 Jan 2001 17:54:02 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <979173582.3a5d00ce0a0fb@Mail.MexComUSA.net> Date: Wed, 10 Jan 2001 17:54:16 -0800 (PST) From: John Baldwin To: Edwin Culp Subject: RE: /boot/kernel/kernel: swap_pager_getswapspace: failed Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Edwin Culp wrote: > Thanks, John. I wish that it were that simple, that is if I am interpreting > pstat and vmstat correctly. It might be asking for more swap space than you have. I.e., it may need mroe than 256 meg of swap. :( > > /root # pstat -s > Device 1K-blocks Used Avail Capacity Type > /dev/rad0s2b 262016 0 262016 0% Interleaved > > I have two another disks that aren't being used with an additional 512M of > swap > each that are not being mounted because this machine isn't carrying much > load > right now. > > /root # vmstat > procs memory page disks faults cpu > r b w avm fre flt re pi po fr sr ad0 ad2 in sy cs us sy id > 0 2 0 118972 15100 849 0 1 0 834 4 0 0 414 3136 599 33 8 59 > > It really seems to be related to my upgrading to XFree86-4.0.2_3 and KDE-2. > If > no one else is seeing it, it isn't critical and with patience it'll show > itself > with a little time. > > Thanks, > > ed > > Quoting John Baldwin : > >> >> On 10-Jan-01 Edwin Culp wrote: >> > I am starting to get the following error. I've never seen it before and >> > don't >> > really understand why it should fail. Where should I start looking for >> the >> > problem? >> > >> > /boot/kernel/kernel: swap_pager_getswapspace: failed >> > >> > This seems to have started in the last week. >> > >> > Thanks, >> >> You are running out of swap space. Run fewer programs, buy more memory, >> add >> more swap space, or a combo of the three. >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> > > > > -- > EnContacto.Net - InternetSalon.Org - CafeMania.Net > -- -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 18:53:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 7514937B400 for ; Wed, 10 Jan 2001 18:53:31 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0B2rBQ63980; Wed, 10 Jan 2001 18:53:11 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101110253.f0B2rBQ63980@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Daniel C. Sobral" Cc: Wm Brian McCane , current@FreeBSD.ORG Subject: Re: Problem installing on T20 In-Reply-To: <3A5D0432.DC472940@newsguy.com> Date: Wed, 10 Jan 2001 18:53:11 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > Wm Brian McCane wrote: > > > > I have an IBM T20 laptop that I want to run FreeBSD on. I have run > > [etc] > > You have a problem which is technically called an "IBM laptop". IBM, in > their infinite wisdom, decided to hibernate on the first partition it > doesn't recognize (hypothesis #1) or on the first partition identified > as 165 decimal (hypothesis #2). Whatever the case is, when the shitty > thing boots, the BIOS checks said partition to see if the system had > hybernated. Upon finding stuff there (the FreeBSD partition), it does > something which screws the system and locks up. Well, I can definatively answer one thing. If you change the partition ID to 166 and change the boot code to boot from that, then the laptops are just happy. Paul Saab has an A20 or A21 something that has this problem and he changed nothing but the partition ID to 166 and it solved the problem. As far as I'm concerned, this pretty much clinches the need to provide an alternate partition id booting capability so that people can enter 166 (openbsd) or 175 (believed free) when sysinstall is doing the setup and the bootblocks will just deal with it. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 19: 5:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0C61A37B400 for ; Wed, 10 Jan 2001 19:05:02 -0800 (PST) Received: from newsguy.com (p06-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.71]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id MAA27347; Thu, 11 Jan 2001 12:04:55 +0900 (JST) Message-ID: <3A5D2232.72F85E11@newsguy.com> Date: Thu, 11 Jan 2001 12:02:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Wm Brian McCane Cc: current@FreeBSD.ORG Subject: Re: Problem installing on T20 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wm Brian McCane wrote: > > I have an IBM T20 laptop that I want to run FreeBSD on. I have run BTW, I just found that this is covered on the FAQ. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 20:11:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from phnxpop4.phnx.uswest.net (phnxpop4.phnx.uswest.net [206.80.192.4]) by hub.freebsd.org (Postfix) with SMTP id 17D1237B400 for ; Wed, 10 Jan 2001 20:11:04 -0800 (PST) Received: (qmail 11890 invoked by alias); 11 Jan 2001 04:10:52 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 11252 invoked by uid 0); 11 Jan 2001 04:10:37 -0000 Received: from ndslppp221.phnx.uswest.net (HELO pinyon.org) (63.224.136.221) by phnxpop4.phnx.uswest.net with SMTP; 11 Jan 2001 04:10:37 -0000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id E5D5757 for ; Wed, 10 Jan 2001 21:10:37 -0700 (MST) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@FreeBSD.ORG Subject: Re: Problem installing on T20 In-Reply-To: Message from "Daniel C. Sobral" of "Thu, 11 Jan 2001 12:02:10 +0900." <3A5D2232.72F85E11@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jan 2001 21:10:37 -0700 From: "Russell L. Carter" Message-Id: <20010111041037.E5D5757@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %Wm Brian McCane wrote: %> %> I have an IBM T20 laptop that I want to run FreeBSD on. I have run % %BTW, I just found that this is covered on the FAQ. Otay, I must be blind. Where in http://www.freebsd.org/FAQ/book.html is this? Thanks! Russell %-- %Daniel C. Sobral (8-DCS) %dcs@newsguy.com %dcs@freebsd.org %capo@a.crazy.bsdconspiracy.net % % "There is no spoon." -- Kiki % % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 21:43:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D271037B401 for ; Wed, 10 Jan 2001 21:43:29 -0800 (PST) Received: from newsguy.com (p14-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.15]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id OAA09419; Thu, 11 Jan 2001 14:43:20 +0900 (JST) Message-ID: <3A5D476C.67A2DC29@newsguy.com> Date: Thu, 11 Jan 2001 14:41:00 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "Russell L. Carter" Cc: current@FreeBSD.ORG Subject: Re: Problem installing on T20 References: <20010111041037.E5D5757@pinyon.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Russell L. Carter" wrote: > > %Wm Brian McCane wrote: > %> > %> I have an IBM T20 laptop that I want to run FreeBSD on. I have run > % > %BTW, I just found that this is covered on the FAQ. > > Otay, I must be blind. Where in http://www.freebsd.org/FAQ/book.html > is this? MMmmm. I think I have gone blind too. Beats me. I was reading december e-mail when I just stumbled on a thread about the same problem, where it was mentioned it had been added to the FAQ. Well, I can't seem to find any reference either. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 10 23:31:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 623A737B401; Wed, 10 Jan 2001 23:30:49 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Wed, 10 Jan 2001 23:29:02 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0B7Ujv86131; Wed, 10 Jan 2001 23:30:45 -0800 (PST) (envelope-from cjc) Date: Wed, 10 Jan 2001 23:30:45 -0800 From: "Crist J. Clark" To: stable@freebsd.org, current@freebsd.org Subject: sysinstall.8 Breaking buildworld Message-ID: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had some buildworld failures earlier this week. In src/share/man/man8 the Makefile includes code to get the sysinstall.8 manpage. Since the manpage lives in src/release, this requires that you CVSup src-release. I had not been. This broke buildworld which had worked in the past. sysinstall.8 is the only file in src-release that is required for a buildworld. It seems somewhat silly to me that you are required to grab the whole thing for that one file. I made the change to the Makefile which makes sysinstall.8 and src-release optional. I included it in a reply to the PR that precipitated the change, http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 Steven G. Kargl ealier, independently submitted the almost exact same thing, http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24122 In a separate PR. Anyone have a good reason why everyone _must_ have src-release to buildworld? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 2: 4:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from txnsvr.toxin.net (txnsvr.toxin.net [210.175.77.11]) by hub.freebsd.org (Postfix) with ESMTP id CBCBA37B404 for ; Thu, 11 Jan 2001 02:04:19 -0800 (PST) Received: from mercurius (nat.1st.ne.jp [210.253.25.32]) by txnsvr.toxin.net (8.9.3+3.1W/3.7W/TOXIN1999042900) with ESMTP id TAA24681 for ; Thu, 11 Jan 2001 19:04:08 +0900 (JST) Date: Thu, 11 Jan 2001 19:06:36 +0900 From: FUJII Tomoyasu To: freebsd-current@FreeBSD.org Message-Id: <20010111190615.8CD4.YKM@toxin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.00 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 5:26:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id D4E2C37B400 for ; Thu, 11 Jan 2001 05:26:32 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id FAA03477 for ; Thu, 11 Jan 2001 05:26:32 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A5DB488.7A74332@FreeBSD.org> Date: Thu, 11 Jan 2001 05:26:32 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Head's up: Yarrow-style periodic entropy saving Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the sake of those who don't follow commit messages (shame on you!), here's your fair warning regarding this change. This is the promised update that periodically (every 3 minutes by default) saves 2k of randomness to a set of rotating files stored by default in /.entropy. That location was chosen so that it could be loaded as early as possible in the boot process. As mentioned in the commit message, Mark suggested the defaults for size, period, and number of files based on the requirements of the Yarrow algorithm. System load for this should be negligible. All the parameters are tunable if load becomes a problem. I chose the operator user as the custodian of the entropy files since that both isolates them from unprivileged users to a certain extent, and minimizes the possibility of damaged caused by file based exploits that could be caused if the files were owned by root. This is bike shed material. For now my opinion is that the best option is to leave the single file written out at shutdown intact. First, I'd rather make one change at a time. Second, having both systems in place gives users with special needs (like diskless boots) more options in terms of saving entropy. I've no objection to ripping this out down the road if circumstances warrant. Enjoy, Doug -------- Original Message -------- Subject: cvs commit: src/etc crontab rc src/etc/defaults rc.confsrc/etc/mtree BSD.root.dist src/libexec Makefilesrc/libexec/save-entropy Makefile save-entropy.sh Date: Thu, 11 Jan 2001 05:01:20 -0800 (PST) From: Doug Barton To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org dougb 2001/01/11 05:01:20 PST Modified files: etc crontab rc etc/defaults rc.conf etc/mtree BSD.root.dist libexec Makefile Added files: libexec/save-entropy Makefile save-entropy.sh Log: Add a system to save entropy from /dev/random periodically so that it can be used to reseed at boot time. This will greatly increase the chances that there will be sufficient entropy available at boot time to prevent long delays. For /etc/rc, remove the vmstat and iostat runs from the attempt to provide some cheesy randomness if the files fail, since those programs are dynamically linked, and ldd seems to want some randomness to do its magic. Guidance and parameters for this project were provided by Mark Murray, based on the requirements of the Yarrow algorithm. Some helpful suggestions for implementation (including the tip about iostat and vmstat) were provided by Sheldon Hearn. All blame for problems or mistakes is mine of course. Revision Changes Path 1.28 +4 -1 src/etc/crontab 1.247 +27 -11 src/etc/rc 1.84 +4 -1 src/etc/defaults/rc.conf 1.48 +5 -1 src/etc/mtree/BSD.root.dist 1.44 +2 -1 src/libexec/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/crontab.diff?&r1=1.27&r2=1.28&f=h http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/rc.diff?&r1=1.246&r2=1.247&f=h http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf.diff?&r1=1.83&r2=1.84&f=h http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/mtree/BSD.root.dist.diff?&r1=1.47&r2=1.48&f=h http://www.FreeBSD.org/cgi/cvsweb.cgi/src/libexec/Makefile.diff?&r1=1.43&r2=1.44&f=h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 6:14:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 9367F37B400; Thu, 11 Jan 2001 06:13:53 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f0BED3V19649; Thu, 11 Jan 2001 09:13:03 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101111413.f0BED3V19649@hda.hda.com> Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101102148.f0ALmog00877@mass.osd.bsdi.com> from Mike Smith at "Jan 10, 2001 01:48:50 pm" To: Mike Smith Date: Thu, 11 Jan 2001 09:13:03 -0500 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's possible that the EC is solely responsible for the fan, or that > Sony decided in their infinite wisdom to do it all in a driver somewhere. "acpiconf -s 1" switches the fan to its low setting, so we do know how to do it. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 6:23: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by hub.freebsd.org (Postfix) with ESMTP id AFB4637B401 for ; Thu, 11 Jan 2001 06:22:45 -0800 (PST) Received: from camtech.net.au ([203.55.241.7]) by mta05.mail.mel.aone.net.au with ESMTP id <20010111142234.HEQV19572.mta05.mail.mel.aone.net.au@camtech.net.au>; Fri, 12 Jan 2001 01:22:34 +1100 Message-ID: <3A5DC228.2E5D2504@camtech.net.au> Date: Fri, 12 Jan 2001 00:54:40 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Edwin Culp Cc: current@FreeBSD.Org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <979158899.3a5cc773b0f7b@Mail.MexComUSA.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > > I am starting to get the following error. I've never seen it before and don't > really understand why it should fail. Where should I start looking for the > problem? > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > This seems to have started in the last week. > I saw the same problem until I stopped using mfs on /tmp. Stop using mfs for /tmp. P.S. you might want to add the following to /etc/rc.conf: clear_tmp_enable="YES" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 6:43:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 4972437B400 for ; Thu, 11 Jan 2001 06:42:52 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14GiwC-00025Y-00; Thu, 11 Jan 2001 16:42:48 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA22316; Thu, 11 Jan 2001 16:42:43 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 22124; Thu Jan 11 16:41:20 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14Gium-0001eb-00; Thu, 11 Jan 2001 16:41:20 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-reply-to: Your message of "Fri, 12 Jan 2001 00:54:40 +1030." <3A5DC228.2E5D2504@camtech.net.au> Date: Thu, 11 Jan 2001 16:41:20 +0200 Message-ID: <6360.979224080@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Jan 2001 00:54:40 +1030, Matthew Thyer wrote: > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > > > This seems to have started in the last week. > > > > I saw the same problem until I stopped using mfs on /tmp. > > Stop using mfs for /tmp. Are you sure it's not just /tmp "filling up" swap? If it's just that, all Edwin needs to do is limit the size of his MFS /tmp. I do this in /etc/fstab: /dev/ad0s1b /tmp mfs rw,-s=245760 0 0 See the description of the -s option in mount_mfs(8). Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 6:50:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id DB5C237B698; Thu, 11 Jan 2001 06:50:10 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id 7B1BFBA80; Thu, 11 Jan 2001 09:45:53 -0500 (EST) X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-current@freebsd.org Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Heads Up Re: cvs commit: src/sys/alpha/include globals.h src/sys/conf files.i386 src/sys/i386/i386 locore.s globals.s src/sys/i386/include asnames.h globals.h src/sys/ia64/include globals.h In-Reply-To: Message from Jake Burkholder of "Thu, 11 Jan 2001 06:46:27 PST." <200101111446.f0BEkRv12082@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jan 2001 09:45:53 -0500 From: Jake Burkholder Message-Id: <20010111144553.7B1BFBA80@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > jake 2001/01/11 06:46:26 PST > > Modified files: > sys/alpha/include globals.h > sys/conf files.i386 > sys/i386/i386 locore.s > sys/i386/include asnames.h globals.h > sys/ia64/include globals.h > Removed files: > sys/i386/i386 globals.s > Log: > - Remove compatibility macros for accessing per-cpu variables. > __FreeBSD_version 500015 can be used to detect their disappearance. > - Move the symbols for SMP_prvspace and lapic from globals.s to > locore.s. > - Remove globals.s with extreme prejudice. > > Revision Changes Path > 1.6 +1 -14 src/sys/alpha/include/globals.h > 1.345 +1 -2 src/sys/conf/files.i386 > 1.140 +12 -1 src/sys/i386/i386/locore.s > 1.50 +1 -44 src/sys/i386/include/asnames.h > 1.16 +1 -25 src/sys/i386/include/globals.h > 1.5 +1 -13 src/sys/ia64/include/globals.h > > If you have not rebuilt your modules in the past few days you must do so now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 7: 9:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from moran.grauel.com (usr1-16.mintel.net [63.81.123.31]) by hub.freebsd.org (Postfix) with ESMTP id B771C37B402 for ; Thu, 11 Jan 2001 07:09:27 -0800 (PST) Received: (from rjk@localhost) by moran.grauel.com (8.11.1/8.11.1) id f0BF9JR98503; Thu, 11 Jan 2001 10:09:19 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14941.52383.537828.73883@localhost.grauel.com> Date: Thu, 11 Jan 2001 10:09:19 -0500 (EST) To: freebsd-current@freebsd.org Subject: ppp/samba (configuration?) question X-Mailer: VM 6.75 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If this isn't the right place for this, I apologize. Feel free to set followups appropriately. I'm running ppp on a -current system (12/7/2000 vintage) named `moran'. I'm using it as a gateway for small in-home network (a couple of windoze boxes and a laptop running -stable), and I have NAT enabled. ppp is started automatically at boot as follows: /usr/sbin/ppp -quiet -auto -nat mintel Here's the appropriate part of ppp.conf: mintel: allow users rjk set openmode active 5 set phone 1234567 set timeout 2700 set socket /var/tmp/internet "" set authname a set authkey b deny lqr disable lqr set ifaddr 10.0.0.1/0 10.0.0.2/0 0.0.0.0 0.0.0.0 delete all add default HISADDR enable dns In ppp.linkdown, I have: mintel: iface clear I'm using 10.1.0.0/24 internally, and moran is also running dhcpd and samba. Everything is working fine, except (you knew there'd be an except, right?:) the windoze boxes on my local network can't find the samba server on moran immediately after moran reboots. After some experimenting with config files and playing with ethereal, I think I know what's going on but I don't know what to do about it. If I don't put "10.0.0.1 localhost" in /etc/hosts, rebooting is very slow; I have to wait for ppp to make a connection before sendmail gets going. If I add it to /etc/hosts I don't have to wait on sendmail but I have problems with nmbd. With the above configuration for ppp, ifconfig always shows 2 IP addresses associated with tun0. Immediately after boot, it looks like (for example): tun0: flags=8051 mtu 1514 inet 10.0.0.1 --> 255.255.255.255 netmask 0xffffffff inet 63.xx.xx.13 --> 63.xx.xx.2 netmask 0xff000000 Opened by PID 115 After I lose my connection for whatever reason (which normally happens at least 3 or 4 times a day with our local telephone service :() ppp automatically redials and reconnects. After this happens, ifconfig would show: tun0: flags=8051 mtu 1514 inet 63.xx.xx.13 --> 255.255.255.255 netmask 0xffffffff inet 63.xx.xx.47 --> 63.xx.xx.2 netmask 0xff000000 Opened by PID 115 The 10. address is gone, my last address is still there but points to 255.255.255.255, and my new address is fine. ethereal shows that nmbd is saying it lives at 10.0.0.1. If I kill nmbd and restart it after having lost and remade my ppp connection, everything is fine. Note that this only affects nmbd. Browsers and ssh work just fine. Have I got something misconfigured? Should ppp be keeping my last IP address around like that? Sorry for the length of this message. Any comments and/or suggestions? Thanks. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 9:30:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 8EE5137B401; Thu, 11 Jan 2001 09:29:47 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id JAA23289; Thu, 11 Jan 2001 09:29:49 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0BHTji13857; Thu, 11 Jan 2001 09:29:45 -0800 (PST) (envelope-from bmah) Message-Id: <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: cjclark@alum.mit.edu Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> References: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Comments: In-reply-to "Crist J. Clark" message dated "Wed, 10 Jan 2001 23:30:45 -0800." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-203044208P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 11 Jan 2001 09:29:45 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-203044208P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Crist J. Clark" wrote: > I had some buildworld failures earlier this week. In > src/share/man/man8 the Makefile includes code to get the sysinstall.8 > manpage. Since the manpage lives in src/release, this requires that > you CVSup src-release. I had not been. This broke buildworld which had > worked in the past. sysinstall.8 is the only file in src-release that > is required for a buildworld. It seems somewhat silly to me that you > are required to grab the whole thing for that one file. OK...I was one of the people who (indirectly) pushed for this. In a nutshell, I (and, independently, several other people) noticed that the sysinstall(8) manpage never gets installed as a part of the binary distributions or by an installworld. (I got highly confused by this while rewriting some other parts of the documentation.) The solution was to make sure that an installworld installs this manpage. > I made the change to the Makefile which makes sysinstall.8 and > src-release optional. I included it in a reply to the PR that > precipitated the change, > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 My personal opinion is that sysinstall.8 is a part of the base system and shouldn't be optional. If we take your suggestion, it means that installworld will sometimes install this manpage and sometimes it won't. A good counter-argument is that installworld doesn't touch /stand/sysinstall, and therefore shouldn't touch the manpage either. Idea: Maybe we need the release building process to do this instead? On all of my systems, the sysinstall binary came from a CD, and never got touched by any subsequent installworlds. > Anyone have a good reason why everyone _must_ have src-release to > buildworld? I never thought of trying to do a buildworld with anything less than src-all. I guess my counter question is: Anyone have a good reason to do buildworlds *without* /usr/src/release/? Bruce. --==_Exmh_-203044208P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6Xe2I2MoxcVugUsMRAi18AKDolT60SbJn+cmj+lw71PGWPBi47QCeMr+N 7oMXfcOVHa+sieC+tNY2cVw= =Pi8x -----END PGP SIGNATURE----- --==_Exmh_-203044208P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 9:41:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id D088B37B402; Thu, 11 Jan 2001 09:41:07 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0BHeEi18459; Thu, 11 Jan 2001 09:40:14 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: bmah@FreeBSD.ORG Cc: cjclark@alum.mit.edu, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: Message from "Bruce A. Mah" of "Thu, 11 Jan 2001 09:29:45 PST." <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> Date: Thu, 11 Jan 2001 09:40:14 -0800 Message-ID: <18455.979234814@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My personal opinion is that sysinstall.8 is a part of the base system > and shouldn't be optional. If we take your suggestion, it means that > installworld will sometimes install this manpage and sometimes it won't. I think we should simply move the stupid man page into man8. It's a bit weird to have a man page and its utility live in seperate places, but the release/ directory in the hierarchy has always been a red-headed stepchild in any case. If I had it to do over, it would have all gone into /usr/src/sbin somewhere. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 9:45:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id CF4CF37B402; Thu, 11 Jan 2001 09:45:37 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0BHjb971425; Thu, 11 Jan 2001 09:45:37 -0800 (PST) (envelope-from dillon) Date: Thu, 11 Jan 2001 09:45:37 -0800 (PST) From: Matt Dillon Message-Id: <200101111745.f0BHjb971425@earth.backplane.com> To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: Head's up: Yarrow-style periodic entropy saving References: <3A5DB488.7A74332@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : For the sake of those who don't follow commit messages (shame on you!), :here's your fair warning regarding this change. This is the promised update :that periodically (every 3 minutes by default) saves 2k of randomness to a Please make the default something more reasonable, like every 30 minutes. It is simply not necessary to save entropy every 3 minutes. It's massive overkill. :set of rotating files stored by default in /.entropy. That location was This is broken. The files should be in /var somewhere... for example, /var/db/entropy/ You should never modify files from a system cron job in / by default, certainly not periodically. Nor do you need to make it a dot file or directory. Please put this file in /var/db. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 10: 1:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 10CEA37B404; Thu, 11 Jan 2001 10:00:53 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14GjSB-0003gU-00; Thu, 11 Jan 2001 15:15:51 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0BFFoA81809; Thu, 11 Jan 2001 15:15:50 GMT (envelope-from ben) Date: Thu, 11 Jan 2001 15:15:50 +0000 From: Ben Smithurst To: stable@freebsd.org, current@freebsd.org Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111151549.Z79365@strontium.scientia.demon.co.uk> References: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crist J. Clark wrote: > Anyone have a good reason why everyone _must_ have src-release to > buildworld? No. Sorry. I kind of assumed people doing buildworlds would just get src-all. Pointy hat this way please... As I said in a reply to a private mail to Crist, I'll commit a fix for this tonight and MFC it soon. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 10:54: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 78DDA37B401; Thu, 11 Jan 2001 10:53:38 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BIrI110455; Thu, 11 Jan 2001 10:53:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.4.0.FreeBSD:010111105204:458=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> Date: Thu, 11 Jan 2001 10:53:43 -0800 (PST) From: John Baldwin To: "Bruce A. Mah" , jkh@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld Cc: current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.0.FreeBSD:010111105204:458=_ Content-Type: text/plain; charset=us-ascii On 11-Jan-01 Bruce A. Mah wrote: > If memory serves me right, "Crist J. Clark" wrote: >> I had some buildworld failures earlier this week. In >> src/share/man/man8 the Makefile includes code to get the sysinstall.8 >> manpage. Since the manpage lives in src/release, this requires that >> you CVSup src-release. I had not been. This broke buildworld which had >> worked in the past. sysinstall.8 is the only file in src-release that >> is required for a buildworld. It seems somewhat silly to me that you >> are required to grab the whole thing for that one file. > > OK...I was one of the people who (indirectly) pushed for this. In a > nutshell, I (and, independently, several other people) noticed that the > sysinstall(8) manpage never gets installed as a part of the binary > distributions or by an installworld. (I got highly confused by this > while rewriting some other parts of the documentation.) The solution > was to make sure that an installworld installs this manpage. > >> I made the change to the Makefile which makes sysinstall.8 and >> src-release optional. I included it in a reply to the PR that >> precipitated the change, >> >> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 > > My personal opinion is that sysinstall.8 is a part of the base system > and shouldn't be optional. If we take your suggestion, it means that > installworld will sometimes install this manpage and sometimes it won't. > > A good counter-argument is that installworld doesn't touch > /stand/sysinstall, and therefore shouldn't touch the manpage either. > > Idea: Maybe we need the release building process to do this instead? > On all of my systems, the sysinstall binary came from a CD, and never > got touched by any subsequent installworlds. > >> Anyone have a good reason why everyone _must_ have src-release to >> buildworld? > > I never thought of trying to do a buildworld with anything less than > src-all. I guess my counter question is: Anyone have a good reason to > do buildworlds *without* /usr/src/release/? The real fix is that sysinstall does not belong in /usr/src/release, it needs to move back into /sbin or /usr/sbin and be a part of the regular world build. Jordan, is there any reason why we keep sysinstall out of sync with world? We can still leave /stand on teh system, but having a 3.x sysinstall in /stand on a -current system is less than useless. Whereas having an up-to-date sysinstall in /sbin or /usr/sbin as well as an up-to-date sysinstall.8 manpage that doesn't require weird hacks to be installed would be useful. The new sysinstall isn't coming anytime soon and we both know that, so that is not a valid argument for not moving it. It used to live in /sbin, so my only question is which directory should it move to: /sbin or /usr/sbin? I will do all the legwork on this.. > Bruce. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ --_=XFMail.1.4.0.FreeBSD:010111105204:458=_ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6Xe2I2MoxcVugUsMRAi18AKDolT60SbJn+cmj+lw71PGWPBi47QCeMr+N 7oMXfcOVHa+sieC+tNY2cVw= =Pi8x -----END PGP SIGNATURE----- --_=XFMail.1.4.0.FreeBSD:010111105204:458=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 10:54:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 9EA4837B404; Thu, 11 Jan 2001 10:53:44 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BIrJ110459; Thu, 11 Jan 2001 10:53:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <18455.979234814@winston.osd.bsdi.com> Date: Thu, 11 Jan 2001 10:53:43 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Cc: current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu, bmah@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Jordan Hubbard wrote: >> My personal opinion is that sysinstall.8 is a part of the base system >> and shouldn't be optional. If we take your suggestion, it means that >> installworld will sometimes install this manpage and sometimes it won't. > > I think we should simply move the stupid man page into man8. It's a bit > weird to have a man page and its utility live in seperate places, but > the release/ directory in the hierarchy has always been a red-headed > stepchild in any case. If I had it to do over, it would have all gone > into /usr/src/sbin somewhere. Let's put sysinstall back in sbin/ then. It _used_ to live there until someone moved it. :) -r--r--r-- 1 root src 62356 Dec 30 1995 /usr/cvs/src/sbin/sysinstall/Attic/sysinstall.c,v -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 11: 0:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 6855F37B401; Thu, 11 Jan 2001 11:00:02 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 11 Jan 2001 10:58:18 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0BJ03O90286; Thu, 11 Jan 2001 11:00:03 -0800 (PST) (envelope-from cjc) Date: Thu, 11 Jan 2001 11:00:03 -0800 From: "Crist J. Clark" To: "Bruce A. Mah" Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111110003.A90221@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com>; from bmah@FreeBSD.ORG on Thu, Jan 11, 2001 at 09:29:45AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 09:29:45AM -0800, Bruce A. Mah wrote: [snip] > My personal opinion is that sysinstall.8 is a part of the base system > and shouldn't be optional. If we take your suggestion, it means that > installworld will sometimes install this manpage and sometimes it won't. Bu-ut, as you point out... > A good counter-argument is that installworld doesn't touch > /stand/sysinstall, and therefore shouldn't touch the manpage either. I think getting the sysinstall binary and manpages out of sync, which is what the current configuration promises to do, is in itself a bug. > Idea: Maybe we need the release building process to do this instead? > On all of my systems, the sysinstall binary came from a CD, and never > got touched by any subsequent installworlds. I had assumed that the 'release' target would do something like this which explains why I was so puzzled by this change. I now understand why some people wanted it. > > Anyone have a good reason why everyone _must_ have src-release to > > buildworld? > > I never thought of trying to do a buildworld with anything less than > src-all. I guess my counter question is: Anyone have a good reason to > do buildworlds *without* /usr/src/release/? When I was CVSup'ing over a phone line to a notebook PC with a 750MB HDD, I trimmed my supfile to only what I needed, no src-games, no src-kerberosIV, no src-kerberos5, no src-release, etc. But to reiterate, I think the best reason not to do this is the potential for getting /stand/sysinstall and sysinstall(8) out of sync on your system. That is Just Wrong. The manpage should only be installed when /stand/sysinstall changes. The fact that src-release is now required was just an annoyance since I lost a build before I tracked it down. I woulda got over it. ;) I had not even noticed the change on some builds over the weekend since I do ususally grab src-release. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 11: 9:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 7A0C137B69C; Thu, 11 Jan 2001 11:09:19 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 11 Jan 2001 11:07:18 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0BJ93090368; Thu, 11 Jan 2001 11:09:03 -0800 (PST) (envelope-from cjc) Date: Thu, 11 Jan 2001 11:09:03 -0800 From: "Crist J. Clark" To: John Baldwin Cc: Jordan Hubbard , current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu, bmah@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <18455.979234814@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jan 11, 2001 at 10:53:43AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 10:53:43AM -0800, John Baldwin wrote: > > On 11-Jan-01 Jordan Hubbard wrote: > >> My personal opinion is that sysinstall.8 is a part of the base system > >> and shouldn't be optional. If we take your suggestion, it means that > >> installworld will sometimes install this manpage and sometimes it won't. > > > > I think we should simply move the stupid man page into man8. It's a bit > > weird to have a man page and its utility live in seperate places, but > > the release/ directory in the hierarchy has always been a red-headed > > stepchild in any case. If I had it to do over, it would have all gone > > into /usr/src/sbin somewhere. > > Let's put sysinstall back in sbin/ then. It _used_ to live there until someone > moved it. :) > > -r--r--r-- 1 root src 62356 Dec 30 1995 > /usr/cvs/src/sbin/sysinstall/Attic/sysinstall.c,v I had assumed that sysinstall was not part of the standard installworld for recovery purposes. That is, if a buildworld-installworld were to totally hose your system (but of course that _never_ happens), you would still have a reliable /stand/sysinstall uncorrupted by the errant installworld to aid in fixing things. Again, this is just what I assumed the reason for the design to be. And I have never actually used sysinstall to recover a hosed upgrade, I like the fixit.flp. But IMHO, either both /stand/sysinstall and sysinstall.8 get installed when building world or neither do. To me, that seems clear cut. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 11:14:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id D9D4437B401; Thu, 11 Jan 2001 11:14:01 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0BJE0i18987; Thu, 11 Jan 2001 11:14:01 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: John Baldwin Cc: current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu, bmah@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: Message from John Baldwin of "Thu, 11 Jan 2001 10:53:43 PST." Date: Thu, 11 Jan 2001 11:14:00 -0800 Message-ID: <18983.979240440@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let's put sysinstall back in sbin/ then. It _used_ to live there until someo ne > moved it. :) I won't argue - move away! Just have one of the CVSmeisters do it as a repo-copy, of course. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 11:53: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 48EA137B400; Thu, 11 Jan 2001 11:52:48 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BJqM112128; Thu, 11 Jan 2001 11:52:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <18983.979240440@winston.osd.bsdi.com> Date: Thu, 11 Jan 2001 11:52:47 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Cc: bmah@FreeBSD.org, cjclark@alum.mit.edu, stable@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Jordan Hubbard wrote: >> Let's put sysinstall back in sbin/ then. It _used_ to live there until >> someo > ne >> moved it. :) > > I won't argue - move away! Just have one of the CVSmeisters do it as > a repo-copy, of course. Yay! Thanks. Will do. :) > - Jordan -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 11:53:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D368337B699; Thu, 11 Jan 2001 11:53:10 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BJqJ112120; Thu, 11 Jan 2001 11:52:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> Date: Thu, 11 Jan 2001 11:52:43 -0800 (PST) From: John Baldwin To: cjclark@alum.mit.edu Subject: Re: sysinstall.8 Breaking buildworld Cc: bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Crist J. Clark wrote: > On Thu, Jan 11, 2001 at 10:53:43AM -0800, John Baldwin wrote: >> >> On 11-Jan-01 Jordan Hubbard wrote: >> >> My personal opinion is that sysinstall.8 is a part of the base system >> >> and shouldn't be optional. If we take your suggestion, it means that >> >> installworld will sometimes install this manpage and sometimes it won't. >> > >> > I think we should simply move the stupid man page into man8. It's a bit >> > weird to have a man page and its utility live in seperate places, but >> > the release/ directory in the hierarchy has always been a red-headed >> > stepchild in any case. If I had it to do over, it would have all gone >> > into /usr/src/sbin somewhere. >> >> Let's put sysinstall back in sbin/ then. It _used_ to live there until >> someone >> moved it. :) >> >> -r--r--r-- 1 root src 62356 Dec 30 1995 >> /usr/cvs/src/sbin/sysinstall/Attic/sysinstall.c,v > > I had assumed that sysinstall was not part of the standard > installworld for recovery purposes. That is, if a > buildworld-installworld were to totally hose your system (but of > course that _never_ happens), you would still have a reliable > /stand/sysinstall uncorrupted by the errant installworld to aid in > fixing things. Erm, many things live in both /stand and other places: > ll /stand/ | wc -l 35 > ll /stand/rm /bin/rm -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm Putting it in world wouldn't touch /stand, it would just add it to either /usr/sbin or /sbin and keep that copy updated. > Again, this is just what I assumed the reason for the design to > be. And I have never actually used sysinstall to recover a hosed > upgrade, I like the fixit.flp. > > But IMHO, either both /stand/sysinstall and sysinstall.8 get installed > when building world or neither do. To me, that seems clear cut. I vote for both, but not to touch /stand. We don't keep rm.1 in sync with /stand/rm, we keep it in sync with /bin/rm, so this seems to be the most consistent.. > -- > Crist J. Clark cjclark@alum.mit.edu -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 12:26:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 8569737B401 for ; Thu, 11 Jan 2001 12:26:06 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id VAA28504 for freebsd-current@FreeBSD.ORG; Thu, 11 Jan 2001 21:26:05 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id 2243787AE; Thu, 11 Jan 2001 21:20:45 +0100 (CET) Date: Thu, 11 Jan 2001 21:20:44 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Head's up: Yarrow-style periodic entropy saving Message-ID: <20010111212044.A68879@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <3A5DB488.7A74332@FreeBSD.org> <200101111745.f0BHjb971425@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101111745.f0BHjb971425@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Jan 11, 2001 at 09:45:37AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matt Dillon: > Please make the default something more reasonable, like every 30 minutes. > It is simply not necessary to save entropy every 3 minutes. It's massive > overkill. Agreed. > This is broken. The files should be in /var somewhere... for example, > /var/db/entropy/ Agreed too, this is the standard location for such things. I know we need entropy at boot time (hopefully after mounting /var) but that's not a good reason to put them in / IMHO. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 12:36:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D6A737B401; Thu, 11 Jan 2001 12:36:30 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA22696; Thu, 11 Jan 2001 12:36:24 -0800 Date: Thu, 11 Jan 2001 12:36:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: sio && serial console in -current? In-Reply-To: <200101090629.f096TGG16888@mobile.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matthew Jacob wrote: > > > > Yeah, weird. I'm at 9600... What's wierd is that it's got to be some userland > > induced thing because printouts from the kernel are fine until init is > > invoked... > > This is an ongoing "Hmm, that is strange!" type problem. There are several > symptoms that I see at times: > 1: console turns to garbage part way through /etc/rc and comes back to life > when /etc/rc exits and getty starts > 2: console *disappears* part way through /etc/rc and comes back to life > when /etc/rc exits and getty starts > 3: there is a burst of garbage after /etc/rc and before getty > 4: the problem you describe I think I have seen a long time ago, once. > 5: ^T and ^C and ^\ do not work ("not a controlling terminal") during > the execution of /etc/rc. There are several different ways this happens > depending on whether you go via the single user shell or not. > > This happens on some machines semi regularly and occasionally on others and > "never" (yet) on some others. These are all serial consoles, and all > machines are different. SMP machines are far worse than UP, but my UP > machines have this sort of thing occasionally too. > > > sio for alpha seems fine..... wahhh..... > > I am sure we can break it for compatability :-) > No doubt. What I'm really curious about is whether I'm the only one seeing this consistently- not the 1-3,5 above, but #4- where as soon as /sbin/init is invoked, the serial console has this repeated output that makes it unusable, period. I really don't want to debug this myself- I am *sooooooo* behind on other FreeBSD issues that I need to spend what few FreeBSD cycles I have on those. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 12:55:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id F318C37B400 for ; Thu, 11 Jan 2001 12:55:04 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14GokO-0005YU-00; Thu, 11 Jan 2001 22:55:00 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id WAA15779; Thu, 11 Jan 2001 22:54:59 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 15646; Thu Jan 11 22:54:01 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14GojR-0002j4-00; Thu, 11 Jan 2001 22:54:01 +0200 From: Sheldon Hearn To: Ollivier Robert Cc: freebsd-current@freebsd.org Subject: Re: Head's up: Yarrow-style periodic entropy saving In-reply-to: Your message of "Thu, 11 Jan 2001 21:20:44 +0100." <20010111212044.A68879@keltia.freenix.fr> Date: Thu, 11 Jan 2001 22:54:01 +0200 Message-ID: <10481.979246441@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Jan 2001 21:20:44 +0100, Ollivier Robert wrote: > > This is broken. The files should be in /var somewhere... for example, > > /var/db/entropy/ > > Agreed too, this is the standard location for such things. I know we need > entropy at boot time (hopefully after mounting /var) but that's not a good > reason to put them in / IMHO. Hop off the bandwagon. The system didn't use /var/db/ before Doug's commit either. See my _long_ explanation (before/after/future) on the cvs-all mailing list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 13:29:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 6C53737B401 for ; Thu, 11 Jan 2001 13:29:19 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id NAA17043; Thu, 11 Jan 2001 13:29:21 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0BLTHE18545; Thu, 11 Jan 2001 13:29:17 -0800 (PST) (envelope-from bmah) Message-Id: <200101112129.f0BLTHE18545@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: "Sidwell, Josh" Cc: "'current@FreeBSD.ORG'" Subject: Re: Current-ISO In-Reply-To: <3B69B479657BD311A7F700508B44257C0BA5AB91@ceodcxbdc2.co.orange.ca.us> References: <3B69B479657BD311A7F700508B44257C0BA5AB91@ceodcxbdc2.co.orange.ca.us> Comments: In-reply-to "Sidwell, Josh" message dated "Tue, 09 Jan 2001 13:11:06 -0800." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_337910401P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 11 Jan 2001 13:29:17 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_337910401P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Sidwell, Josh" wrote: > I have been unsucessfully trying to build an ISO image of the 5.0-CURRENT > branch for the past several weeks. Is anyone aware of a tool to pull the > latest tree and turn it into an ISO image? http://www.freebsd.org/FAQ/hackers.html#CUSTREL Bruce. --==_Exmh_337910401P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6XiWt2MoxcVugUsMRAhYmAKDNSyCKsFFW6Op4VjuHGltC79BGmgCgnPiG 4awAaioRQw8quD6IteBGXU4= =tYcf -----END PGP SIGNATURE----- --==_Exmh_337910401P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 13:46:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 7491937B401; Thu, 11 Jan 2001 13:46:36 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 11 Jan 2001 13:44:36 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0BLkLK91229; Thu, 11 Jan 2001 13:46:21 -0800 (PST) (envelope-from cjc) Date: Thu, 11 Jan 2001 13:46:16 -0800 From: "Crist J. Clark" To: John Baldwin Cc: bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jan 11, 2001 at 11:52:43AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: [snip] > Erm, many things live in both /stand and other places: > > > ll /stand/ | wc -l > 35 > > ll /stand/rm /bin/rm > -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm > -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm I am not clear what you are saying here. Only sysinstall lives in /stand, [592:~] ls -li /stand total 45250 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 -sh 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 [ 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 arp 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 boot_crunch 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 cpio 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 dhclient 3 drwx------ 3 root wheel 512 Jun 19 2000 etc 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 find 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 fsck 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 gunzip 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 gzip 29952 drwxr-xr-x 2 root wheel 1024 Jun 19 2000 help 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 hostname 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 ifconfig 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 minigzip 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 mount_mfs 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 mount_nfs 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 newfs 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 pccardc 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 pccardd 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 ppp 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 pwd 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 rm 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 route 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 sed 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 sh 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 slattach 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 sysinstall 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 test 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 zcat But it lives by many names. (Ignoring the directories.) > Putting it in world wouldn't touch /stand, it would just add it to either > /usr/sbin or /sbin and keep that copy updated. [snip] > I vote for both, but not to touch /stand. We don't keep rm.1 in sync with > /stand/rm, we keep it in sync with /bin/rm, so this seems to be the most > consistent.. Well, /stand/rm is not _really_ rm at all, but I get the point. I guess the only question is whether to put it in /sbin or /usr/sbin. I think /sbin makes sense (so it is bootable), but it is 1.6MB of /-bloat... But from another thread about making 250MB the default / size, I guess few care too much about that anymore. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14: 1: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id CDDCA37B402; Thu, 11 Jan 2001 14:00:40 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14Gplf-0004UP-00; Thu, 11 Jan 2001 22:00:23 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0BM0Ml93543; Thu, 11 Jan 2001 22:00:22 GMT (envelope-from ben) Date: Thu, 11 Jan 2001 22:00:21 +0000 From: Ben Smithurst To: cjclark@alum.mit.edu Cc: John Baldwin , bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111220021.C79365@strontium.scientia.demon.co.uk> References: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crist J. Clark wrote: > On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: > >> Erm, many things live in both /stand and other places: >> >>> ll /stand/ | wc -l >> 35 >>> ll /stand/rm /bin/rm >> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm >> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm > > I am not clear what you are saying here. Only sysinstall lives in > /stand, yeah, but it can be used as many things. If invoked as "rm" sysinstall behaves just like the real rm, it happens to be one big binary. > Well, /stand/rm is not _really_ rm at all, but I get the point. I > guess the only question is whether to put it in /sbin or /usr/sbin. I > think /sbin makes sense (so it is bootable), but it is 1.6MB of > /-bloat... But from another thread about making 250MB the default / > size, I guess few care too much about that anymore. I'd prefer it in /usr/sbin, some of my root partitions are only 32MB, and that's not big enough at the moment. If your /usr is hosed to the extent you can't mount it you've probably got more problems than sysinstall will help you with. But that's just my opinion. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14:16:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id 7F86D37B400; Thu, 11 Jan 2001 14:16:21 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id OAA12226; Thu, 11 Jan 2001 14:15:51 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0BMFgT19311; Thu, 11 Jan 2001 14:15:42 -0800 (PST) (envelope-from bmah) Message-Id: <200101112215.f0BMFgT19311@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: Ben Smithurst Cc: cjclark@alum.mit.edu, John Baldwin , bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <20010111220021.C79365@strontium.scientia.demon.co.uk> References: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> <20010111220021.C79365@strontium.scientia.demon.co.uk> Comments: In-reply-to Ben Smithurst message dated "Thu, 11 Jan 2001 22:00:21 +0000." From: bmah@FreeBSD.org (Bruce A. Mah) Reply-To: bmah@FreeBSD.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_454632526P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 11 Jan 2001 14:15:42 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_454632526P Content-Type: text/plain; charset=us-ascii If memory serves me right, Ben Smithurst wrote: > yeah, but it can be used as many things. If invoked as "rm" sysinstall > behaves just like the real rm, it happens to be one big binary. The thing in /stand is a crunchgen(8) binary. sysinstall itself is (chug, chug) 850K. After being stripped, it's 798K: 1616 -rwxr-xr-x 1 root wheel 817416 Jan 11 14:14 sysinstall Bruce. --==_Exmh_454632526P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6XjCO2MoxcVugUsMRAkxjAKCROr/S8NkW1Dhh4f1w9/NAvkspZgCglb77 qOredvmGB+Ekd7gsD8LEZcU= =RaKn -----END PGP SIGNATURE----- --==_Exmh_454632526P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14:23: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 74E5537B699; Thu, 11 Jan 2001 14:22:39 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0BMMNQ69170; Thu, 11 Jan 2001 14:22:24 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101112222.f0BMMNQ69170@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jordan Hubbard Cc: John Baldwin , current@FreeBSD.ORG, stable@FreeBSD.ORG, cjclark@alum.mit.edu, bmah@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <18983.979240440@winston.osd.bsdi.com> Date: Thu, 11 Jan 2001 14:22:23 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > Let's put sysinstall back in sbin/ then. It _used_ to live there until som eo > ne > > moved it. :) > > I won't argue - move away! Just have one of the CVSmeisters do it as > a repo-copy, of course. We cannot repo-copy it to src/sbin - there is a copy there already. We could blow the old one away and lose the history (RELEASE_2_0 and earlier) but I guess that is no big deal these days. Personally I would prefer it in src/usr.sbin/sysinstall and have it dynamically linked. The release crunchgen can still take the .o's and make the giant /stand version.. dynamic: 390769 shared: 892921 On the other hand, if we had the static version in src/sbin, we could have a "LINKS+= /sbin/sysinstall /stand/sysinstall" and blow away the old installed version with each make world. This would avoid POLA with people following old instructions to run /stand/sysinstall. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14:23:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 26D2737B6BC; Thu, 11 Jan 2001 14:23:04 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0BMN2i19749; Thu, 11 Jan 2001 14:23:02 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Ben Smithurst Cc: cjclark@alum.mit.edu, John Baldwin , bmah@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: Message from Ben Smithurst of "Thu, 11 Jan 2001 22:00:21 GMT." <20010111220021.C79365@strontium.scientia.demon.co.uk> Date: Thu, 11 Jan 2001 14:23:02 -0800 Message-ID: <19745.979251782@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yeah, but it can be used as many things. If invoked as "rm" sysinstall > behaves just like the real rm, it happens to be one big binary. This, however, is merely "post-installation behavior" - if you rebuild and reinstall sysinstall in order to catch up with a bug fix to it, however, then this behavior goes away. - Jordan > > > Well, /stand/rm is not _really_ rm at all, but I get the point. I > > guess the only question is whether to put it in /sbin or /usr/sbin. I > > think /sbin makes sense (so it is bootable), but it is 1.6MB of > > /-bloat... But from another thread about making 250MB the default / > > size, I guess few care too much about that anymore. > > I'd prefer it in /usr/sbin, some of my root partitions are only 32MB, > and that's not big enough at the moment. If your /usr is hosed to > the extent you can't mount it you've probably got more problems than > sysinstall will help you with. But that's just my opinion. > > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14:25:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 8C04837B400 for ; Thu, 11 Jan 2001 14:24:52 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id XAA07122 for freebsd-current@freebsd.org; Thu, 11 Jan 2001 23:24:49 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id 41F3187AE; Thu, 11 Jan 2001 22:11:53 +0100 (CET) Date: Thu, 11 Jan 2001 22:11:53 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: Head's up: Yarrow-style periodic entropy saving Message-ID: <20010111221153.A69406@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <20010111212044.A68879@keltia.freenix.fr> <10481.979246441@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <10481.979246441@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Thu, Jan 11, 2001 at 10:54:01PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Sheldon Hearn: > Hop off the bandwagon. The system didn't use /var/db/ before Doug's > commit either. See my _long_ explanation (before/after/future) on the > cvs-all mailing list. I know the system used now stores it in /entropy. I was too busy to react at that time but I still dislike using / for that. I read your message as well but I'm still behind Matt & Jordan on that one. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14:39:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6E2F037B401; Thu, 11 Jan 2001 14:38:50 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BMcS117827; Thu, 11 Jan 2001 14:38:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111220021.C79365@strontium.scientia.demon.co.uk> Date: Thu, 11 Jan 2001 14:38:55 -0800 (PST) From: John Baldwin To: Ben Smithurst Subject: Re: sysinstall.8 Breaking buildworld Cc: Jordan Hubbard , current@FreeBSD.org, stable@FreeBSD.org, bmah@FreeBSD.org, cjclark@alum.mit.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Ben Smithurst wrote: > Crist J. Clark wrote: > >> On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: >> >>> Erm, many things live in both /stand and other places: >>> >>>> ll /stand/ | wc -l >>> 35 >>>> ll /stand/rm /bin/rm >>> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm >>> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm >> >> I am not clear what you are saying here. Only sysinstall lives in >> /stand, > > yeah, but it can be used as many things. If invoked as "rm" sysinstall > behaves just like the real rm, it happens to be one big binary. > >> Well, /stand/rm is not _really_ rm at all, but I get the point. I >> guess the only question is whether to put it in /sbin or /usr/sbin. I >> think /sbin makes sense (so it is bootable), but it is 1.6MB of >> /-bloat... But from another thread about making 250MB the default / >> size, I guess few care too much about that anymore. > > I'd prefer it in /usr/sbin, some of my root partitions are only 32MB, > and that's not big enough at the moment. If your /usr is hosed to > the extent you can't mount it you've probably got more problems than > sysinstall will help you with. But that's just my opinion. Erm, sysinstall can be used as a replacement for fdisk and disklabel, both of which are in /sbin. In fact, in 4.2 the only tool you can realistically use to splat a virgin disklabel onto a slice w/o weird hoop jumping that isn't documented _is_ sysinstall. disklabel should have that fixed by 4.3, however. However, 800k is big for /sbin: > ll /sbin/ | sort -n -k 5 ... -r-xr-sr-x 2 root tty 299956 Jan 9 08:25 restore -r-xr-sr-x 2 root tty 299956 Jan 9 08:25 rrestore -r-xr-xr-x 1 root wheel 424448 Jan 9 08:24 ipfstat -r-xr-xr-x 1 root wheel 484912 Jan 9 08:24 fsdb -r-xr-xr-x 1 root wheel 513748 Jan 9 08:25 vinum -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 14:39:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BE56537B69C; Thu, 11 Jan 2001 14:38:55 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BMcQ117823; Thu, 11 Jan 2001 14:38:27 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Date: Thu, 11 Jan 2001 14:38:53 -0800 (PST) From: John Baldwin To: "Crist J. Clark" Subject: Re: sysinstall.8 Breaking buildworld Cc: Jordan Hubbard , current@FreeBSD.org, stable@FreeBSD.org, bmah@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Crist J. Clark wrote: > On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: > > [snip] > >> Erm, many things live in both /stand and other places: >> >> > ll /stand/ | wc -l >> 35 >> > ll /stand/rm /bin/rm >> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm >> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm > > I am not clear what you are saying here. Only sysinstall lives in > /stand, Heh, no. That is a crunch. It has the object code for _all_ of those binaries in it. So /stand/rm will remove a file just like the normal rm: > /stand/rm usage: rm [-f | -i] [-dPRrvW] file ... unlink file >> Putting it in world wouldn't touch /stand, it would just add it to either >> /usr/sbin or /sbin and keep that copy updated. > > [snip] > >> I vote for both, but not to touch /stand. We don't keep rm.1 in sync with >> /stand/rm, we keep it in sync with /bin/rm, so this seems to be the most >> consistent.. > > Well, /stand/rm is not _really_ rm at all, but I get the point. I > guess the only question is whether to put it in /sbin or /usr/sbin. I > think /sbin makes sense (so it is bootable), but it is 1.6MB of > /-bloat... But from another thread about making 250MB the default / > size, I guess few care too much about that anymore. It isn't that big: > file $owd/sysinstall /usr/obj/usr/src/sbin/sysinstall/sysinstall: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, not stripped > ll !:1 ll /usr/obj/usr/src/sbin/sysinstall/sysinstall -rwxrwxr-x 1 john src 899374 Jan 11 14:06 /usr/obj/usr/src/sbin/sysinstall/sysinstall The stripped version is about 840k, which isn't but so bad. That is if it lives in /sbin (which I vote for). The dynamic version if it goes in /usr/sbin would be smaller again. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 15: 1: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id B806337B400; Thu, 11 Jan 2001 15:00:47 -0800 (PST) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA11651; Thu, 11 Jan 2001 15:00:35 -0800 (PST) (envelope-from DougB@gorean.org) Date: Thu, 11 Jan 2001 15:00:35 -0800 (PST) From: Doug Barton X-X-Sender: To: Warner Losh Cc: Sheldon Hearn , , Subject: entropy bikesheds In-Reply-To: <200101112222.f0BMMNs75120@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since this post actually has some content I'm moving it to -current. On Thu, 11 Jan 2001, Warner Losh wrote: > I agree. RO / is absoultely *REQUIRED* for our application. As stated, all concerned are sympathetic to that. This is why it's configurable. > we have > a small, writable partition that we can use to store the random > entropy files. Any attempts to force / to be writable will be met > with extreme resistance. The good thing about this ridiculous thread is that the next time someone asks me if I've read the code, I can simply respond with, "No one reads the code for my projects, even when I include the cvsweb links in my head's up mail, so why should I be bothered?" > Our /var isn't persistant accross boots, btw. It is a mfs file > system. Having a requirement that /var contain persistant data would > likely lead to problems. It's precisely for these, and other hairy examples that I haven't put the thing in /var yet. Even a diskless workstation can read files from a RO root that the host writes out periodically, but there is no guarantee that there will be a /var filesystem that we can read from at boot time. I actually started to write some code to handle some obvious cases and got a major headache just thinking about it. > I'm still not sure why we can't do something like: > > date > /dev/random > cat /bin/ls > /dev/random > fsck > mount the file systems > read in the entropy file > > Eg, toss some bone to the random pool. Sure, it will be highly > preditable, but for the mount commands it doesn't matter. We fix > before anything interesting happens. I have a lot of sympathy for this idea, but I don't know if it would work for yarrow. Mark will have to weigh in on it first. FYI, the things rc does first (as needed) are below. / is already mounted RO at this point. 1. rc.diskless 2. source the *rc.conf* files 3. try seeding from /entropy 4. ccdconfig 5. vinum start 6. fsck 7. mount root RW (exit if this fails) 8. umount -a 9. mount -a -t nonfs For my money that's a fairly large number of things that could potentially break if I fooled around with the mount'ing order, so I felt that putting the default in /.entropy was a good way to get started with the minimum amount of real pain. Bikeshed pain I can deal with. One way to deal with this is to introduce a new variable that specifies the filesystem mount point that needs to be mounted to read the seed files. That way we could mount that fs RO, do the seeding, then unmount it and proceed with the rest of the steps from 4. on. I would need some advice on potential pitfalls here though, which is why I haven't acted on it yet. The one that leaps immediately to mind is am I getting myself into trouble by mounting a potentially dirty filesystem, even though it's RO? I know this is done with /, but I'd like someone with more fs experience to confirm that I won't be digging a hole for someone if they have some sort of funky /var/foo fs that I haven't heard of. Doug -- "The most difficult thing in the world is to know how to do a thing and to watch someone else do it wrong without comment." -- Theodore H. White Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 17: 7: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 8298B37B400 for ; Thu, 11 Jan 2001 17:06:48 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id f0C107a40277; Fri, 12 Jan 2001 01:00:07 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id f0C18cx06287; Fri, 12 Jan 2001 01:08:38 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200101120108.f0C18cx06287@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Richard J Kuhns Cc: freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: ppp/samba (configuration?) question In-Reply-To: Message from Richard J Kuhns of "Thu, 11 Jan 2001 10:09:19 EST." <14941.52383.537828.73883@localhost.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Jan 2001 01:08:38 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You should get away with adding your ``set ifaddr'' line to ppp.linkdown (you can remove the ``iface clear'' too). > If this isn't the right place for this, I apologize. Feel free to set > followups appropriately. > > I'm running ppp on a -current system (12/7/2000 vintage) named `moran'. > I'm using it as a gateway for small in-home network (a couple of windoze > boxes and a laptop running -stable), and I have NAT enabled. > > ppp is started automatically at boot as follows: > > /usr/sbin/ppp -quiet -auto -nat mintel > > Here's the appropriate part of ppp.conf: > > mintel: > allow users rjk > set openmode active 5 > set phone 1234567 > set timeout 2700 > set socket /var/tmp/internet "" > set authname a > set authkey b > deny lqr > disable lqr > set ifaddr 10.0.0.1/0 10.0.0.2/0 0.0.0.0 0.0.0.0 > delete all > add default HISADDR > enable dns > > In ppp.linkdown, I have: > > mintel: > iface clear > > I'm using 10.1.0.0/24 internally, and moran is also running dhcpd and > samba. Everything is working fine, except (you knew there'd be an except, > right?:) the windoze boxes on my local network can't find the samba server > on moran immediately after moran reboots. After some experimenting with > config files and playing with ethereal, I think I know what's going on but > I don't know what to do about it. > > If I don't put "10.0.0.1 localhost" in /etc/hosts, rebooting is very slow; > I have to wait for ppp to make a connection before sendmail gets going. If > I add it to /etc/hosts I don't have to wait on sendmail but I have problems > with nmbd. > > With the above configuration for ppp, ifconfig always shows 2 IP addresses > associated with tun0. Immediately after boot, it looks like (for example): > > tun0: flags=8051 mtu 1514 > inet 10.0.0.1 --> 255.255.255.255 netmask 0xffffffff > inet 63.xx.xx.13 --> 63.xx.xx.2 netmask 0xff000000 > Opened by PID 115 > > After I lose my connection for whatever reason (which normally happens at > least 3 or 4 times a day with our local telephone service :() ppp > automatically redials and reconnects. After this happens, ifconfig would > show: > > tun0: flags=8051 mtu 1514 > inet 63.xx.xx.13 --> 255.255.255.255 netmask 0xffffffff > inet 63.xx.xx.47 --> 63.xx.xx.2 netmask 0xff000000 > Opened by PID 115 > > The 10. address is gone, my last address is still there but points to > 255.255.255.255, and my new address is fine. > > ethereal shows that nmbd is saying it lives at 10.0.0.1. If I kill nmbd > and restart it after having lost and remade my ppp connection, everything > is fine. > > Note that this only affects nmbd. Browsers and ssh work just fine. > > Have I got something misconfigured? Should ppp be keeping my last IP > address around like that? > > Sorry for the length of this message. > > Any comments and/or suggestions? > > Thanks. > > -- > Richard Kuhns rjk@grauel.com > PO Box 6249 Tel: (765)477-6000 \ > 100 Sawmill Road x319 > Lafayette, IN 47903 (800)489-4891 / -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 17:22:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from gateway.symark.com (firewall.symark.westlake.iswest.net [207.178.203.34]) by hub.freebsd.org (Postfix) with ESMTP id C723C37B400; Thu, 11 Jan 2001 17:22:36 -0800 (PST) Received: (from mailer@localhost) by gateway.symark.com (8.9.3/8.9.3) id RAA17294; Thu, 11 Jan 2001 17:22:30 -0800 Received: from camel.symark.com(128.1.1.97) by gateway.symark.com via smap (V2.1+anti-relay+anti-spam) id xma017290; Thu, 11 Jan 01 17:22:11 -0800 Received: by localhost with Microsoft MAPI; Thu, 11 Jan 2001 17:24:54 -0800 Message-ID: <01C07BF3.695D3780.ggross@symark.com> From: Glen Gross Reply-To: "ggross@symark.com" To: "'Alfred Perlstein'" , Carl Makin Cc: "stable@FreeBSD.ORG" Subject: RE: Running Linux kernel modules. Date: Thu, 11 Jan 2001 17:24:52 -0800 Organization: Symark Software X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a possibility of a generalized interface where any linux kernel module could be loaded, in the event that the linux emulator were loaded? Or would this require running the linux kernel in RAM, and therefore running two virtual machines? On Thursday, January 11, 2001 3:12 PM, Alfred Perlstein [SMTP:bright@wintelcom.net] wrote: > * Carl Makin [010111 14:52] wrote: > > > > There are a couple of linux kernel modules that I'd love to run under > > FreeBSD. I've always assumed that I'd have to rewrite them substantially > > to make that happen. > > > > Can anyone give me some pointers on how hard it could be to port a linux > > kernel module to FreeBSD? > > Depends on how familiar you are with kernel internals, for instance > after taking a quick look at the kernel module needed to run vmware > it was pretty clear that someone with the experience and time could > have it done in under a week, about 2 weeks later some maniac ( :) ) > surfaced who had done just that. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com pp-support@symark.com pb-support@symark.com Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 17:33:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from email_server.midstream.com (unknown [63.113.115.195]) by hub.freebsd.org (Postfix) with ESMTP id EEF2A37B404 for ; Thu, 11 Jan 2001 17:33:31 -0800 (PST) Received: by EMAIL_SERVER with Internet Mail Service (5.5.2650.21) id ; Thu, 11 Jan 2001 17:35:43 -0800 Message-ID: <31E4B6337A4FD411BD45000102472E0C05E729@EMAIL_SERVER> From: Jeff Roberson To: "'freebsd-current@freebsd.org'" Subject: Broken mmap in current? Date: Thu, 11 Jan 2001 17:35:37 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C07C37.FA49D1D0" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C07C37.FA49D1D0 Content-Type: text/plain; charset="iso-8859-1" I have written a character device driver for a proprietary PCI device that has a large sum of mapable memory. The character device supports mmap() which I use to export the memory into a user process. I have no problems accessing the memory on this device, but I notice that my mmap routine is called for every access! Is this a problem with current, or a problem with my mmap? I use bus_alloc_resource and then rman_get_start to get the physical address in my attach, and then the mmap just returns atop(physical address). I assumed this is correct since I have verified with a logical analyzer that I am indeed writing to the memory on the device. Also, I noticed that the device's mmap interface does not provide any way to limit the size of the block being mapped? Can I specify the length of the region? Thanks, Jeff ------_=_NextPart_001_01C07C37.FA49D1D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Broken mmap in current?

I have written a character device driver for a = proprietary PCI device that has a large sum of mapable memory.  = The character device supports mmap() which I use to export the memory = into a user process.  I have no problems accessing the memory on = this device, but I notice that my mmap routine is called for every = access!  Is this a problem with current, or a problem with my = mmap?

I use bus_alloc_resource and then rman_get_start to = get the physical address in my attach, and then the mmap just returns = atop(physical address).  I assumed this is correct since I have = verified with a logical analyzer that I am indeed writing to the memory = on the device.  Also, I noticed that the device's mmap interface = does not provide any way to limit the size of the block being = mapped?  Can I specify the length of the region?

Thanks,
Jeff

------_=_NextPart_001_01C07C37.FA49D1D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 17:43:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1532237B400; Thu, 11 Jan 2001 17:43:35 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA45854; Thu, 11 Jan 2001 17:43:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0C1hXt79841; Thu, 11 Jan 2001 17:43:33 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Jan 2001 17:43:32 -0800 From: "David O'Brien" To: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111174332.B74480@dragon.nuxi.com> Reply-To: current@FreeBSD.org, stable@FreeBSD.org References: <20010111220021.C79365@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jan 11, 2001 at 02:38:55PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 02:38:55PM -0800, John Baldwin wrote: > Erm, sysinstall can be used as a replacement for fdisk and disklabel, > both of which are in /sbin. In fact, in 4.2 the only tool you can > realistically use to splat a virgin disklabel onto a slice w/o weird > hoop jumping that isn't documented _is_ sysinstall. disklabel should > have that fixed by 4.3, however. But disklabel/fdisk can't even accept MB's as a unit. Until they grow the functionality of the NetBSD and OpenBSD versions of them, sysinstall is really the only tolerable disk label manipulation tool our users have. This includes those with a bummed /usr that needs to install a new disk to get it back. On Thu, Jan 11, 2001 at 02:22:23PM -0800, Peter Wemm wrote: > Personally I would prefer it in src/usr.sbin/sysinstall and have it > dynamically linked. That would be OK, *once* our fdisk/disklable grows some modern [heck even late 1990's] user interface. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 17:49: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 61A7D37B404 for ; Thu, 11 Jan 2001 17:48:45 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA45885; Thu, 11 Jan 2001 17:48:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0C1mRC79881; Thu, 11 Jan 2001 17:48:27 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Jan 2001 17:48:26 -0800 From: "David O'Brien" To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111174826.C74480@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <18983.979240440@winston.osd.bsdi.com> <200101112222.f0BMMNQ69170@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101112222.f0BMMNQ69170@mobile.wemm.org>; from peter@netplex.com.au on Thu, Jan 11, 2001 at 02:22:23PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 02:22:23PM -0800, Peter Wemm wrote: > > I won't argue - move away! Just have one of the CVSmeisters do it as > > a repo-copy, of course. > > We cannot repo-copy it to src/sbin - there is a copy there already. We > could blow the old one away and lose the history (RELEASE_2_0 and earlier) > but I guess that is no big deal these days. It wouldn't be that much history (how about moving /home/ncvs/src/sbin/sysinstall/Attic to /home/ncvs/src/sbin/sysinstall/Old to preserve it??) Unfortuneatly in those days repo copies weren't done as well as now. :-(( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 17:51:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D05FD37B400 for ; Thu, 11 Jan 2001 17:51:19 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA45905; Thu, 11 Jan 2001 17:51:18 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0C1pAj79901; Thu, 11 Jan 2001 17:51:10 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Jan 2001 17:51:10 -0800 From: "David O'Brien" To: Doug Barton Cc: freebsd-current@freebsd.org Subject: Re: entropy bikesheds Message-ID: <20010111175109.D74480@dragon.nuxi.com> Reply-To: current@freebsd.org References: <200101112222.f0BMMNs75120@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from DougB@gorean.org on Thu, Jan 11, 2001 at 03:00:35PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 03:00:35PM -0800, Doug Barton wrote: > Since this post actually has some content I'm moving it to > -current. > > On Thu, 11 Jan 2001, Warner Losh wrote: > > > I agree. RO / is absoultely *REQUIRED* for our application. > > As stated, all concerned are sympathetic to that. This is why it's > configurable. Not really -- specifying /var as the home of these files will not work very well (as you even show why below). So things *appear* to be configurable, but aren't. > The good thing about this ridiculous thread is that the next time > someone asks me if I've read the code, I can simply respond with, "No one > reads the code for my projects, even when I include the cvsweb links in my > head's up mail, so why should I be bothered?" I *did* read the diff you committed. So don't use that on me. ;-) > Do YOU Yahoo!? Yep! -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 18:39: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 3DA9C37B400 for ; Thu, 11 Jan 2001 18:38:49 -0800 (PST) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA12887 for ; Thu, 11 Jan 2001 18:38:48 -0800 (PST) (envelope-from DougB@gorean.org) Date: Thu, 11 Jan 2001 18:38:48 -0800 (PST) From: Doug Barton X-X-Sender: To: Subject: Re: entropy bikesheds In-Reply-To: <20010111175109.D74480@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Jan 2001, David O'Brien wrote: > On Thu, Jan 11, 2001 at 03:00:35PM -0800, Doug Barton wrote: > > Since this post actually has some content I'm moving it to > > -current. > > > > On Thu, 11 Jan 2001, Warner Losh wrote: > > > > > I agree. RO / is absoultely *REQUIRED* for our application. > > > > As stated, all concerned are sympathetic to that. This is why it's > > configurable. > > > Not really -- specifying /var as the home of these files will not work > very well (as you even show why below). So things *appear* to be > configurable, but aren't. We're talking about the defaults only. There is nothing to prevent you from putting the entropy files in /my/blue/pony if that's where you really want them. I still need to splatter test the really obscure cases in /etc/rc, but our ultimate goal is for total configurability. Doug -- "The most difficult thing in the world is to know how to do a thing and to watch someone else do it wrong without comment." -- Theodore H. White Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 20:13:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E67337B400 for ; Thu, 11 Jan 2001 20:13:21 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA25122; Thu, 11 Jan 2001 23:13:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0C4DEG03271; Thu, 11 Jan 2001 23:13:15 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 11 Jan 2001 23:13:14 -0500 (EST) To: freebsd-current@freebsd.org Cc: "'Alfred Perlstein'" Subject: RE: Running Linux kernel modules. In-Reply-To: <01C07BF3.695D3780.ggross@symark.com> References: <01C07BF3.695D3780.ggross@symark.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14942.32188.899333.434988@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thursday, January 11, 2001 3:12 PM, Alfred Perlstein > [SMTP:bright@wintelcom.net] wrote: > > * Carl Makin [010111 14:52] wrote: > > > > > > There are a couple of linux kernel modules that I'd love to run under > > > FreeBSD. I've always assumed that I'd have to rewrite them substantially > > > to make that happen. > > > > > > Can anyone give me some pointers on how hard it could be to port a linux > > > kernel module to FreeBSD? > > > > Depends on how familiar you are with kernel internals, for instance > > after taking a quick look at the kernel module needed to run vmware > > it was pretty clear that someone with the experience and time could > > have it done in under a week, about 2 weeks later some maniac ( :) ) > > surfaced who had done just that. The biggest problem I've had porting linux drivers is that linux exports enough internals to allow drivers to distinguish between multiple opens of the same device. Eg: int foo_ioctl(struct inode *inode, struct file *filp, unsigned int cmd, unsigned long arg) { foo_per_open_data *priv = filp->private_data; foo_softc *sc = priv->dev; <..> } AFAIK, there's no clean way to do this with FreeBSD. I think this is why VMware is limited to running one virtual machine. This can be somewhat overcome in a very ugly way -- At my day job, I'm porting a driver for Giganet cLAN1000 VIA adapters. This has much the same problem as VMware. They've got an open-source linux kernel module and a closed source userland binary. To handle the multiple open problem, I'm overloading the open and close system calls. Upon open, I call the native open, then I grovel around in the process' open file table looking for my special file. When I find it, I mark fp->f_nextread with a magic number, then store a pointer to the per-open private data in fp->f_offset. On close, I go grovelling again. I deallocate the private data, clear the magic number, and call the system close function. I've also got an at_exit() hook that does much the same thing. Obtaining the file descripter at ioctl() and mmap() time is much more interesting. When I'm called from a syscall, I pull the args out of the process and grab the fd, index the process' file table and bingo. The real problem is when mmap is called out of a fault (and not dev_pager_alloc, which is what gets called when the mmap syscall is issued). Right now I throw up my hands and return the private data from the first instance I find when walking the process' open file table. If this becomes a problem, I'm planning on prefaulting the pages at dev_pager_alloc() time (when I can get an fd from the process) and wiring them -- its only 20k per process.. Isn't this gross? Is there a better way? Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 20:50:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7F9C837B401 for ; Thu, 11 Jan 2001 20:50:25 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id PAA02399; Fri, 12 Jan 2001 15:50:19 +1100 Date: Fri, 12 Jan 2001 15:52:09 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jeff Roberson Cc: "'freebsd-current@freebsd.org'" Subject: Re: Broken mmap in current? In-Reply-To: <31E4B6337A4FD411BD45000102472E0C05E729@EMAIL_SERVER> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Jan 2001, Jeff Roberson wrote: > I have written a character device driver for a proprietary PCI device that > has a large sum of mapable memory. The character device supports mmap() > which I use to export the memory into a user process. I have no problems > accessing the memory on this device, but I notice that my mmap routine is > called for every access! Is this a problem with current, or a problem with > my mmap? Maybe both. The device mmap routine is called mainly by the mmap syscall for every page to be mmapped. It is also called by dev_pager_getpages() for some pagefaults, but I think this rarely happens. > I use bus_alloc_resource and then rman_get_start to get the physical address > in my attach, and then the mmap just returns atop(physical address). I > assumed this is correct since I have verified with a logical analyzer that I > am indeed writing to the memory on the device. This is correct. I looked at some examples. Many drivers get this wrong by using i386_btop(), alpha_btop(), etc. (AFAIK, atop() is for addresses which are what we are converting here, btop() is for (byte) offsets, and the machine-dependent prefixes are a vestige of page clustering code that mostly went away 7 years ago. > Also, I noticed that the > device's mmap interface does not provide any way to limit the size of the > block being mapped? Can I specify the length of the region? The length is implicitly PAGE_SIZE. The device mmap function is called for each page to be mapped. It must verify that the memory from offset to (offset + PAGE_SIZE - 1) belongs to the device and can be accessed with the given protection, and do any device-specific things necessary to enable this memory. This scheme can't support bank-switched device memory very well, if at all. pcvvt_mmap() in the pcvt driver is the simplest example of this. agp_mmap() is a more up to date example with the same old bug that the vga drivers used to have (off by 1 (page) error checking the offset). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 22:20:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 24C9037B400; Thu, 11 Jan 2001 22:20:03 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0C6JQI12558; Fri, 12 Jan 2001 08:19:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101120619.f0C6JQI12558@gratis.grondar.za> To: Doug Barton Cc: Warner Losh , Sheldon Hearn , markm@freebsd.org, freebsd-current@freebsd.org Subject: Re: entropy bikesheds References: In-Reply-To: ; from Doug Barton "Thu, 11 Jan 2001 15:00:35 PST." Date: Fri, 12 Jan 2001 08:19:21 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton said: > Since this post actually has some content I'm moving it to > -current. Cool! > > Our /var isn't persistant accross boots, btw. It is a mfs file > > system. Having a requirement that /var contain persistant data would > > likely lead to problems. > > It's precisely for these, and other hairy examples that I haven't > put the thing in /var yet. Even a diskless workstation can read files from > a RO root that the host writes out periodically, but there is no guarantee > that there will be a /var filesystem that we can read from at boot time. I > actually started to write some code to handle some obvious cases and got a > major headache just thinking about it. What is needed is some form of persistant storage to stash the Yarrow state over a reboot or a crash. There are a number of people saying "Over my dead body can you put it ${HERE}!!", without coming up with alternatives that are useful. At BSDCon, the concept of using the first swap partition was discussed, and I think it is a great idea, but the volunteer has yet to offer any code. > > I'm still not sure why we can't do something like: > > > > date > /dev/random > > cat /bin/ls > /dev/random > > fsck > > mount the file systems > > read in the entropy file > > > > Eg, toss some bone to the random pool. Sure, it will be highly > > preditable, but for the mount commands it doesn't matter. We fix > > before anything interesting happens. Just as usable is "echo 'sekrit password' > /dev/random". Might as well not bother. There is no usable randomness here, so rather than pretending, it is better to simply admit to ourselves that the entropy generator is giving crap numbers at this point. I originally put a block-at-startup in precicesly because of this complaint. Remember that on a brand-new system, at first boot, the sshd is going to use /dev/random to make keys. How insecure do you want that? Can we decide this, please - do we want secure startup (which will take some effort to achieve), or can we say "screw it" and start insecure like the old system? I'm happy to accomodate folks, but the constant lack of concensus combined with extreme positions is wearing a bit thin. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 22:38:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5A69237B400; Thu, 11 Jan 2001 22:38:42 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0C6ces78463; Thu, 11 Jan 2001 23:38:40 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101120638.f0C6ces78463@harmony.village.org> To: John Baldwin Subject: Re: bogus microuptime() warnings? Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG, Poul-Henning Kamp In-reply-to: Your message of "Tue, 09 Jan 2001 16:11:16 PST." References: Date: Thu, 11 Jan 2001 23:38:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Baldwin writes: : > Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" : > with the latest -CURRENT than I used to... : : Which soundcard? I get them on sbc0: at port 0x220-0x22f,0x388-0x38b,0x320-0x321 irq 5 drq 1,5 on isa0 pcm0: on sbc0 on m VAIO. I see them more when there's lots of traffic on my zoomair awi card. But I also see them when playing mp3s off my hard disk. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 22:41:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D1C8D37B401 for ; Thu, 11 Jan 2001 22:41:35 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0C6fHs78490; Thu, 11 Jan 2001 23:41:17 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101120641.f0C6fHs78490@harmony.village.org> To: Mark Murray Subject: Re: YES! laptop installing Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 10 Jan 2001 08:51:41 +0200." <200101100651.f0A6pEI03345@gratis.grondar.za> References: <200101100651.f0A6pEI03345@gratis.grondar.za> Date: Thu, 11 Jan 2001 23:41:17 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101100651.f0A6pEI03345@gratis.grondar.za> Mark Murray writes: : My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy : MAC address, and then doesn't work. It doesn't even go UP. : : MAC=00:00:80:00:00:80, FWIW. There's about 4 different dc based cards that don't work because they don't get the nic address right. Well, that's what I think. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 23: 5:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from flute.daconcepts.dyndns.org (wks-29-177-219.kscable.com [24.29.177.219]) by hub.freebsd.org (Postfix) with ESMTP id 5205A37B402 for ; Thu, 11 Jan 2001 23:04:58 -0800 (PST) Received: from localhost (natedac@localhost) by flute.daconcepts.dyndns.org (8.11.1/8.11.1) with ESMTP id f0C75IK75658 for ; Fri, 12 Jan 2001 01:05:18 -0600 (CST) (envelope-from natedac@kscable.com) X-Authentication-Warning: flute.daconcepts.dyndns.org: natedac owned process doing -bs Date: Fri, 12 Jan 2001 01:05:12 -0600 (CST) From: Nate Dannenberg X-X-Sender: To: Subject: Re: entropy bikesheds In-Reply-To: <200101120619.f0C6JQI12558@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > Can we decide this, please - do we want secure startup (which will > take some effort to achieve), or can we say "screw it" and start > insecure like the old system? > > I'm happy to accomodate folks, but the constant lack of concensus > combined with extreme positions is wearing a bit thin. Although I'm not a coder on this platform, I do have an idea that we sometimes use on my hobby platform, maybe this might help... Start some kind of hardware-managed timer at the earliest possible opportunity (perhaps start it in the boot loader!), then when you need to pick up your first seed, read the timer's value and seed your random generator from that. The idea is to catch that timer at an unknown condition, and certainly the computer is not going to boot in the exact same amount of time, every time it's restarted. This would be especially true if the boot sequence gets interrupted (to load another kernel perhaps) or the user forces the machine into single-user mode while it's booting. In my hobby platform, it's common to start the timer, then grab a value from it after the user hits a key after viewing some introduction screen. The value grabbed is often used as the actual random number, but it could be just as useful if used to seed a random generator. If you're particularly paranoid, you set both timers for 32-bit mode, start one first thing at startup, and the other when the user hits the key, then read both of them the first time a random number is needed. Seed your random generator from that, along with any other sources you can (such as the video raster counter and the sound device's readable oscillator, set to generate a noise waveform). Just my two cents. -- ___________________________________ _____ _____ | _///@@@| | | natedac@kscable.com /'//ZZ@@|____ | | |'''/ |'/@7 | | http://home.kscable.com/natedac |`'| `~~' | | | `| .--. | | C64/C128 - What's *YOUR* hobby? | `\____|___\ | | \_ | | |___________________________________ \_____| _____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 23:11:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from flute.daconcepts.dyndns.org (wks-29-177-219.kscable.com [24.29.177.219]) by hub.freebsd.org (Postfix) with ESMTP id 0B08E37B402 for ; Thu, 11 Jan 2001 23:10:58 -0800 (PST) Received: from localhost (natedac@localhost) by flute.daconcepts.dyndns.org (8.11.1/8.11.1) with ESMTP id f0C7BFs76716; Fri, 12 Jan 2001 01:11:19 -0600 (CST) (envelope-from natedac@kscable.com) X-Authentication-Warning: flute.daconcepts.dyndns.org: natedac owned process doing -bs Date: Fri, 12 Jan 2001 01:11:11 -0600 (CST) From: Nate Dannenberg X-X-Sender: To: Warner Losh Cc: Subject: Re: bogus microuptime() warnings? In-Reply-To: <200101120638.f0C6ces78463@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Jan 2001, Warner Losh wrote: > In message John Baldwin writes: > : > Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" > : > with the latest -CURRENT than I used to... > : > : Which soundcard? > > sbc0: at port 0x220-0x22f,0x388-0x38b,0x320-0x321 irq 5 drq 1,5 on isa0 > pcm0: on sbc0 I have also been experiencing this problem ("hwptr went backwards") with my ESS Audiodrive (integrated on the motherboard), which uses the same chip of course. Also, mine shows up as pcm1, rather than pcm0 as it did in 4.1-Release, and I am forced to use a bridge driver. What am I doing wrong? Do you get stereo playback from yours? Mine's only mono in anything over 4.1-Release. Of course I'm tracking 5.0-current. > But I also see them when playing mp3s off my hard disk. Ditto. -- ___________________________________ _____ _____ | _///@@@| | | natedac@kscable.com /'//ZZ@@|____ | | |'''/ |'/@7 | | http://home.kscable.com/natedac |`'| `~~' | | | `| .--. | | C64/C128 - What's *YOUR* hobby? | `\____|___\ | | \_ | | |___________________________________ \_____| _____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 23:14:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (oe42.law7.hotmail.com [216.33.236.37]) by hub.freebsd.org (Postfix) with ESMTP id D5D4637B401; Thu, 11 Jan 2001 23:13:50 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 11 Jan 2001 23:13:50 -0800 X-Originating-IP: [130.240.193.170] From: "electro" To: , Subject: Bug in src tree? Date: Fri, 12 Jan 2001 08:17:01 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01C07C70.0A42DF70" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: X-OriginalArrivalTime: 12 Jan 2001 07:13:50.0712 (UTC) FILETIME=[36AC6F80:01C07C67] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001D_01C07C70.0A42DF70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi! I try to compile a new kernel with the latest source and I always end up with this (in the end). Any suggestions? I mean the error message is fun...dont match any know i386 = instruction???? cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs = -Wst rict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline = -Wcast-qual =20 -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev = -I../../.. /include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL = -include opt_global.h -elf -mpreferred-stack-boundary=3D2 = ../../i386/i386/bioscall.s /tmp/ccmJEqq7.s: Assembler messages: /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 instruction /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 instruction *** Error code 1 Stop in /usr/src/sys/compile/PROFESSOR.010110. ------=_NextPart_000_001D_01C07C70.0A42DF70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hi!
I try to=20 compile a new kernel with the latest source and I always end up
with = this (in=20 the end). Any suggestions?
I mean the error message is fun...dont = match any=20 know i386 instruction????

cc -c -x
assembler-with-cpp -DLOCORE = -O=20 -Wall -Wredundant-decls -Wnested-externs -Wst
rict-prototypes =20 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual =20
-fformat-extensions -ansi  -nostdinc -I-  -I. -I../.. = -I../../dev=20 -I../../..
/include = -I../../contrib/dev/acpica/Subsystem/Include =20 -D_KERNEL -include
opt_global.h -elf  = -mpreferred-stack-boundary=3D2=20 ../../i386/i386/bioscall.s
/tmp/ccmJEqq7.s: Assembler=20 messages:
/tmp/ccmJEqq7.s:758: Error: operands given don't match any = known=20 386
instruction
/tmp/ccmJEqq7.s:822: Error: operands given don't = match any=20 known 386
instruction
*** Error code 1

Stop in=20 /usr/src/sys/compile/PROFESSOR.010110.


------=_NextPart_000_001D_01C07C70.0A42DF70-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 23:30:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.82]) by hub.freebsd.org (Postfix) with ESMTP id 7DDF537B401 for ; Thu, 11 Jan 2001 23:30:15 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 4CAA560F4C; Fri, 12 Jan 2001 14:30:24 +0700 (JAVT) Date: Fri, 12 Jan 2001 14:30:24 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: Still... hwptr went backwards... Message-ID: <20010112143024.B34647@naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all... Just a few days ago, I thought I saw a few posts that state the latest -CURRENT emits less hwptr went backwards messages. Apparently this doesn't happen on my system :( Currently running KDE 2.0.0 with XFree86 4.0.1 and when I play MP3, and want to lock my screen, MP3 playing choked heavily. If disk is heavily access, MP3 playing choke more worse. $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 10 2001 18:06:06 Installed devices: pcm0: at io 0xd400 irq 9 (1p/1r channels duplex) $ dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Jan 10 18:07:41 JAVT 2001 root@dante.naver.co.id:/usr/obj/usr/src/sys/DANTE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 737023115 Hz CPU: Pentium III/Pentium III Xeon/Celeron (737.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 133083136 (129964K bytes) avail memory = 125952000 (123000K bytes) Preloaded elf kernel "kernel" at 0xc0312000. Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00f0ed0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xf7000000-0xf707ffff,0xf8000000-0xfbffffff irq 11 at device 2.0 on pci0 pcib1: at device 30.0 on pci0 pci1: on pcib1 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd800-0xd87f mem 0xf6800000-0xf680007f irq 9 at device 10.0 on pci1 xl0: Ethernet address: 00:50:da:95:85:dc miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xd400-0xd43f irq 9 at device 11.0 on pci1 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 31.3 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 14324MB [29104/16/63] at ata0-master UDMA33 acd0: CDROM at ata0-slave using PIO4 Mounting root from ufs:/dev/ad0s2a pcm0: hwptr went backwards 64 -> 32 pcm0: hwptr went backwards 192 -> 4032 pcm0: hwptr went backwards 384 -> 192 pcm0: hwptr went backwards 2752 -> 2720 pcm0: hwptr went backwards 192 -> 32 pcm0: hwptr went backwards 2304 -> 2048 pcm0: hwptr went backwards 2176 -> 2080 pcm0: hwptr went backwards 2112 -> 2048 pcm0: hwptr went backwards 2112 -> 1856 pcm0: hwptr went backwards 64 -> 4064 Sound card is Creative SoundBlaster Vibra 128. Motherboard ASUS CUSL2. /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 11 23:31:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 49FA237B400; Thu, 11 Jan 2001 23:30:49 -0800 (PST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by white.imgsrc.co.jp (8.11.2/8.11.0) with ESMTP id f0C7Ucj22362; Fri, 12 Jan 2001 16:30:39 +0900 (JST) Date: Fri, 12 Jan 2001 16:30:38 +0900 Message-ID: <7m1yu9mdlt.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Julian Elischer Cc: net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming In-Reply-To: <3A566BCB.BFD6FA2D@elischer.org> References: <3A5567A7.A11F47E3@elischer.org> <3A566BCB.BFD6FA2D@elischer.org> User-Agent: Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Julian, I tried netgraph for the first time to work with latest vmware2 port. When I try to load netgraph kernel module, it failed with: # kldload ng_bridge kldload: can't load ng_bridge: Exec format error And /var/log/messages says: Jan 12 16:27:07 waterblue /boot/kernel/kernel: KLD ng_bridge.ko: depends on ng_ether - not available But ng_ether.ko is already loaded automatically (checked by kldstat). Is this known problem, or my local configuration mistake? # My environment is "make world"ed yesterday and kernel is latest. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 0:52:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4910737B400 for ; Fri, 12 Jan 2001 00:52:33 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0C8qSs13520; Fri, 12 Jan 2001 00:52:28 -0800 (PST) Date: Fri, 12 Jan 2001 00:52:28 -0800 From: "'Alfred Perlstein'" To: Andrew Gallatin Cc: freebsd-current@freebsd.org Subject: Re: Running Linux kernel modules. Message-ID: <20010112005228.S7240@fw.wintelcom.net> References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14942.32188.899333.434988@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jan 11, 2001 at 11:13:14PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Andrew Gallatin [010111 20:13] wrote: > > > On Thursday, January 11, 2001 3:12 PM, Alfred Perlstein > > [SMTP:bright@wintelcom.net] wrote: > > > * Carl Makin [010111 14:52] wrote: > > > > > > > > There are a couple of linux kernel modules that I'd love to run under > > > > FreeBSD. I've always assumed that I'd have to rewrite them substantially > > > > to make that happen. > > > > > > > > Can anyone give me some pointers on how hard it could be to port a linux > > > > kernel module to FreeBSD? > > > > > > Depends on how familiar you are with kernel internals, for instance > > > after taking a quick look at the kernel module needed to run vmware > > > it was pretty clear that someone with the experience and time could > > > have it done in under a week, about 2 weeks later some maniac ( :) ) > > > surfaced who had done just that. > > The biggest problem I've had porting linux drivers is that linux > exports enough internals to allow drivers to distinguish between > multiple opens of the same device. Eg: [snip] > > Isn't this gross? Is there a better way? Beyond gross. :) I've heard of many requests for this special functionality in FreeBSD, things as you've mentioned (vmware, your driver) as well as ptys. If you wanted to fix our interface I'd be glad to help review it and assist if possible. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 0:56:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7047D37B400 for ; Fri, 12 Jan 2001 00:56:08 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA47384; Fri, 12 Jan 2001 00:56:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0C8u2C83078; Fri, 12 Jan 2001 00:56:02 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Jan 2001 00:56:02 -0800 From: "David O'Brien" To: Warner Losh Cc: Mark Murray , Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: YES! laptop installing Message-ID: <20010112005602.A83055@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <200101100651.f0A6pEI03345@gratis.grondar.za> <200101100651.f0A6pEI03345@gratis.grondar.za> <200101120641.f0C6fHs78490@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101120641.f0C6fHs78490@harmony.village.org>; from imp@harmony.village.org on Thu, Jan 11, 2001 at 11:41:17PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 11:41:17PM -0700, Warner Losh wrote: > In message <200101100651.f0A6pEI03345@gratis.grondar.za> Mark Murray writes: > : My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy > : MAC address, and then doesn't work. It doesn't even go UP. > : > : MAC=00:00:80:00:00:80, FWIW. > > There's about 4 different dc based cards that don't work because they > don't get the nic address right. Well, that's what I think. Use an /etc/start_if.dc0 script that uses `ifconfig' to set the eithernet address. wpaul show me how to find mine, and I just put in the start_if.dc0 and forget about it. :) -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 1:25:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 2F82A37B400 for ; Fri, 12 Jan 2001 01:24:41 -0800 (PST) Received: (qmail 84661 invoked by uid 1003); 12 Jan 2001 09:24:38 -0000 Date: Fri, 12 Jan 2001 11:24:38 +0200 From: Neil Blakey-Milner To: electro Cc: freebsd-current@FreeBSD.ORG, freebsd-bugs@freebsd.org Subject: Re: Bug in src tree? Message-ID: <20010112112438.A84108@mithrandr.moria.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from electro_p@hotmail.com on Fri, Jan 12, 2001 at 08:17:01AM +0100 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2001-01-12 (08:17), electro wrote: > I try to compile a new kernel with the latest source and I always end up > with this (in the end). Any suggestions? > I mean the error message is fun...dont match any know i386 instruction???? > > cc -c -x > assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wst > rict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev -I../../.. > /include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include > opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s > /tmp/ccmJEqq7.s: Assembler messages: > /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 > instruction > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > instruction > *** Error code 1 > > Stop in /usr/src/sys/compile/PROFESSOR.010110. You're not using buildkernel, and thus you don't have the necessarily updated tools to handle that source. Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 1:58:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id EE66437B402; Fri, 12 Jan 2001 01:58:07 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id AEA252DC0F; Fri, 12 Jan 2001 11:02:00 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 301DA7817; Fri, 12 Jan 2001 10:57:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 2BCF510E1B; Fri, 12 Jan 2001 10:57:10 +0100 (CET) Date: Fri, 12 Jan 2001 10:57:10 +0100 (CET) From: Andrzej Bialecki To: Doug Barton Cc: freebsd-current@FreeBSD.org Subject: Re: Head's up: Yarrow-style periodic entropy saving In-Reply-To: <3A5DB488.7A74332@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Jan 2001, Doug Barton wrote: > For the sake of those who don't follow commit messages (shame on you!), > here's your fair warning regarding this change. This is the promised update > that periodically (every 3 minutes by default) saves 2k of randomness to a > set of rotating files stored by default in /.entropy. That location was > chosen so that it could be loaded as early as possible in the boot process. On / ? that's quite inconvenient for systems running with read-only root FS... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 2:18:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from cav.logica.co.uk (cav.logica.co.uk [158.234.10.66]) by hub.freebsd.org (Postfix) with ESMTP id EF6C637B404 for ; Fri, 12 Jan 2001 02:18:20 -0800 (PST) Received: from eckert.logica.co.uk (eckert.logica.co.uk [158.234.10.17]) by cav.logica.co.uk (8.9.1/8.9.1) with ESMTP id KAA17566 for ; Fri, 12 Jan 2001 10:18:19 GMT Received: by eckert.logica.co.uk with Internet Mail Service (5.5.2448.0) id ; Fri, 12 Jan 2001 10:18:17 -0000 Message-ID: From: "Newton, Harry" To: "'freebsd-current@freebsd.org'" Subject: Crash dumps during initialisation Date: Fri, 12 Jan 2001 10:17:47 -0000 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I get the kernel to make crash dumps if it fails before the 'dumpon' command is issued ? There used to be a line in the kernel configuration file beginning with the keyword 'config' which had options 'dumps on' or 'crash on' but this has gone. Regards, Harry Harry Newton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 3:27:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 287DB37B400; Fri, 12 Jan 2001 03:27:16 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id LAA59696; Fri, 12 Jan 2001 11:27:14 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101121127.LAA59696@ns.a1.org.uk> Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <20010111174332.B74480@dragon.nuxi.com> from "David O'Brien" at "Jan 11, 2001 05:43:32 pm" To: current@FreeBSD.ORG, stable@FreeBSD.ORG Date: Fri, 12 Jan 2001 11:27:13 +0000 (GMT) Reply-To: current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why does sysinstall have to move at all? Whenever I buildworld/installworld, I always go into release/sysinstall and do a make all install, as suggested in handbook/makeworld.html Why can't the man page be included and installed with this? Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 3:29:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta02.mail.mel.aone.net.au (mta02.mail.au.uu.net [203.2.192.82]) by hub.freebsd.org (Postfix) with ESMTP id C9A2E37B698 for ; Fri, 12 Jan 2001 03:29:08 -0800 (PST) Received: from camtech.net.au ([203.55.242.79]) by mta02.mail.mel.aone.net.au with ESMTP id <20010112112851.GGAU6914.mta02.mail.mel.aone.net.au@camtech.net.au>; Fri, 12 Jan 2001 22:28:51 +1100 Message-ID: <3A5EEAF7.E337C28E@camtech.net.au> Date: Fri, 12 Jan 2001 22:01:03 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <6360.979224080@axl.fw.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Fri, 12 Jan 2001 00:54:40 +1030, Matthew Thyer wrote: > > > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > > > > > This seems to have started in the last week. > > > > > > > I saw the same problem until I stopped using mfs on /tmp. > > > > Stop using mfs for /tmp. > > Are you sure it's not just /tmp "filling up" swap? If it's just that, > all Edwin needs to do is limit the size of his MFS /tmp. I do this in > /etc/fstab: > > /dev/ad0s1b /tmp mfs rw,-s=245760 0 0 > > See the description of the -s option in mount_mfs(8). Well, limits are nice if you can predict your usage in advance. In my case I was using an unlimited mfs (as I have for years): /dev/ad0s2b /tmp mfs rw 0 0 I seem to remember some changes to mfs a while ago and (without checking cvsweb) I assume that's when this: -s size The size of the file system in sectors. This value defaults to the size of the raw partition specified in special (in other words, newfs will use the entire partition for the file system). became the default behaviour. This seems a bit of a pain. Is there anyway to go back (if I'm correct) to a dynamic swap user. I suppose I'm talking about a real tmpfs ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 3:30:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by hub.freebsd.org (Postfix) with ESMTP id 240E337B400 for ; Fri, 12 Jan 2001 03:30:28 -0800 (PST) Received: from camtech.net.au ([203.55.242.79]) by mta05.mail.mel.aone.net.au with ESMTP id <20010112113022.WFVG19572.mta05.mail.mel.aone.net.au@camtech.net.au>; Fri, 12 Jan 2001 22:30:22 +1100 Message-ID: <3A5EEB53.3D48F34E@camtech.net.au> Date: Fri, 12 Jan 2001 22:02:35 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <6360.979224080@axl.fw.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Fri, 12 Jan 2001 00:54:40 +1030, Matthew Thyer wrote: > > > > /boot/kernel/kernel: swap_pager_getswapspace: failed > > > > > > This seems to have started in the last week. > > > > > > > I saw the same problem until I stopped using mfs on /tmp. > > > > Stop using mfs for /tmp. > > Are you sure it's not just /tmp "filling up" swap? If it's just that, > all Edwin needs to do is limit the size of his MFS /tmp. I do this in > /etc/fstab: > > /dev/ad0s1b /tmp mfs rw,-s=245760 0 0 > > See the description of the -s option in mount_mfs(8). Well, limits are nice if you can predict your usage in advance. In my case I was using an unlimited mfs (as I have for years): /dev/ad0s2b /tmp mfs rw 0 0 I seem to remember some changes to mfs a while ago and (without checking cvsweb) I assume that's when this: -s size The size of the file system in sectors. This value defaults to the size of the raw partition specified in special (in other words, newfs will use the entire partition for the file system). became the default behaviour. This seems a bit of a pain. Is there anyway to go back (if I'm correct) to dynamic usage of swap ? I suppose I'm talking about a real tmpfs ala Solaris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 3:38:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 6174037B400 for ; Fri, 12 Jan 2001 03:38:16 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14H2X4-0006RA-00; Fri, 12 Jan 2001 13:38:10 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA21004; Fri, 12 Jan 2001 13:38:08 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 20774; Fri Jan 12 13:37:41 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14H2Wb-0000Ar-00; Fri, 12 Jan 2001 13:37:41 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-reply-to: Your message of "Fri, 12 Jan 2001 22:01:03 +1030." <3A5EEAF7.E337C28E@camtech.net.au> Date: Fri, 12 Jan 2001 13:37:41 +0200 Message-ID: <672.979299461@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Jan 2001 22:01:03 +1030, Matthew Thyer wrote: > This seems a bit of a pain. > > Is there anyway to go back (if I'm correct) to a dynamic swap user. > I suppose I'm talking about a real tmpfs ? The way it is now is the way it's always been. Think about what you mean when you say "dynamic swap user". You want mfs to use more swap than you have? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 4: 3:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 4564337B400; Fri, 12 Jan 2001 04:03:28 -0800 (PST) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by mother.ludd.luth.se (8.9.3+Sun/8.9.3) with ESMTP id NAA20812; Fri, 12 Jan 2001 13:02:28 +0100 (MET) Date: Fri, 12 Jan 2001 13:02:27 +0100 (CET) From: hubbe snubbe To: Neil Blakey-Milner Cc: electro , freebsd-current@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in src tree? In-Reply-To: <20010112112438.A84108@mithrandr.moria.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope.. sorry... I now use the correct command(namely make buildkernel) only problem now is that I cant make A succesfully make world before that so my following question is how important is it to get it(the computer) to succesfully boot up? The story is that FreeBSD4.0 boots with out problem but there is a problem concering my networkcard(vr0 watchdog timeout locks allports for around 10sec) If I install FreeBSD4.1.1 or FreeBSD4.2 I get kernel page fault(?) trap 11? during boot and have to reinstall to FreeBSD4.0 again. I talked to a person in #freebsdhelp (efnet) how said that it probably has to do with the fact I am using an D-link DFE530-TX networkcard that is digital(!?) and not compiled into the kernel. Down below is the error result from my make world in /usr/src (using today source) cc -O -pipe -I. -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc.295 -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc.295/config -c /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc.295/genrecog.c {standard input}: Assembler messages: {standard input}:3555: Error: Rest of line ignored. First ignored character is `p'. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_tools. TIA Jerker On Fri, 12 Jan 2001, Neil Blakey-Milner wrote: > On Fri 2001-01-12 (08:17), electro wrote: > > I try to compile a new kernel with the latest source and I always end up > > with this (in the end). Any suggestions? > > I mean the error message is fun...dont match any know i386 instruction???? > > > > cc -c -x > > assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wst > > rict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev -I../../.. > > /include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include > > opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s > > /tmp/ccmJEqq7.s: Assembler messages: > > /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 > > instruction > > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > > instruction > > *** Error code 1 > > > > Stop in /usr/src/sys/compile/PROFESSOR.010110. > > You're not using buildkernel, and thus you don't have the necessarily > updated tools to handle that source. > > Neil > -- > Neil Blakey-Milner > nbm@mithrandr.moria.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------------------------------------------------------- http://www.ludd.luth.se/~electro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 5: 6:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id CF99F37B400 for ; Fri, 12 Jan 2001 05:06:27 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f0CD5kx23941 for current@freebsd.org; Fri, 12 Jan 2001 08:05:46 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200101121305.f0CD5kx23941@hda.hda.com> Subject: Re: Fan speed control sony vaio lx800 slimtop In-Reply-To: <200101102148.f0ALmog00877@mass.osd.bsdi.com> from Mike Smith at "Jan 10, 2001 01:48:50 pm" To: current@freebsd.org Date: Fri, 12 Jan 2001 08:04:31 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Would I have to do anything special to see it? If anyone has any > > other ideas of what to do let me know - I'm wondering if throttling > > down the CPU turns down the fan. > > It's possible that the EC is solely responsible for the fan, or that > Sony decided in their infinite wisdom to do it all in a driver somewhere. I have a new theory - do we need to enable some sort of suspend on halt for Intel chips? I see we do this for various cyrix chips, and I saw in a search that pentiums with MMX have "auto halt" and "low power on auto halt" options: http://www-student.informatik.uni-bonn.de:8001/~petera/lpp/ Do we enable these? I don't see any CPU_SUSP_HLT options in initcpu.c for Intel chips. Chip is > CPU: Pentium III/Pentium III Xeon/Celeron (801.82-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x686 Stepping = 6 > Features=0x383f9ff Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 5:47:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 8E66B37B400 for ; Fri, 12 Jan 2001 05:47:02 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0CDkVI13562; Fri, 12 Jan 2001 15:46:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101121346.f0CDkVI13562@gratis.grondar.za> To: Nate Dannenberg Cc: current@FreeBSD.ORG Subject: Re: entropy bikesheds References: In-Reply-To: ; from Nate Dannenberg "Fri, 12 Jan 2001 01:05:12 CST." Date: Fri, 12 Jan 2001 15:46:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Start some kind of hardware-managed timer at the earliest possible > opportunity (perhaps start it in the boot loader!), then when you need to > pick up your first seed, read the timer's value and seed your random > generator from that. I have some much more sophisticated code (written by JHB) that does effectively this. It does it by hooking interrupt randomness, and by using the interrupts from your disk controllers (SCSI and IDE/ATA), a nicely fast reseed is gained. I'll happily commit it now, but I'd prefer a code review first, and is suspect that this will be better received once Jake's preemptive ithread code is committed. > The idea is to catch that timer at an unknown condition, and certainly the > computer is not going to boot in the exact same amount of time, every time > it's restarted. This would be especially true if the boot sequence gets > interrupted (to load another kernel perhaps) or the user forces the > machine into single-user mode while it's booting. All entropy harvesting uses some kind of harvesting. On i386, (Pentium and better) it is the TSC register. 80386 and 80486 use nanotime(9) and other CPUs have a TSC-like register. > In my hobby platform, it's common to start the timer, then grab a value > from it after the user hits a key after viewing some introduction screen. > The value grabbed is often used as the actual random number, but it could > be just as useful if used to seed a random generator. SOP :-) > If you're particularly paranoid, you set both timers for 32-bit mode, > start one first thing at startup, and the other when the user hits the > key, then read both of them the first time a random number is needed. > Seed your random generator from that, along with any other sources you can > (such as the video raster counter and the sound device's readable > oscillator, set to generate a noise waveform). Slight overkill, when the TSC register is already used and deliberately underestimated to improve randomness quality. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 6:59:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 9C1EB37B401 for ; Fri, 12 Jan 2001 06:59:03 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0CEwcs10477; Fri, 12 Jan 2001 07:58:38 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101121458.f0CEwcs10477@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Warner Losh Cc: Mark Murray , Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: YES! laptop installing In-Reply-To: Your message of "Thu, 11 Jan 2001 23:41:17 MST." <200101120641.f0C6fHs78490@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Jan 2001 07:58:38 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: MAC=00:00:80:00:00:80, FWIW. > >There's about 4 different dc based cards that don't work because they >don't get the nic address right. Well, that's what I think. That is fixed with my cardbus patch set... at least for the xircom. It should be trivial to fix for the others if they store their nic address the same way. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 7:11:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by hub.freebsd.org (Postfix) with ESMTP id E8BAD37B402 for ; Fri, 12 Jan 2001 07:10:57 -0800 (PST) Received: from camtech.net.au ([203.55.243.26]) by mta05.mail.mel.aone.net.au with ESMTP id <20010112151055.YKZJ19572.mta05.mail.mel.aone.net.au@camtech.net.au>; Sat, 13 Jan 2001 02:10:55 +1100 Message-ID: <3A5F1F05.B9A3C536@camtech.net.au> Date: Sat, 13 Jan 2001 01:43:09 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: sio && serial console in -current? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > Something wierd has been happening lately- the serial console on my i386 > machine works fine up until init is forked.. THen the output is mangled, and > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > like: > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd > > It's like the output is being repeated... > > Anyone seen same? My guess is you might be using PHK's syslog feature and be sending console output to the console ? (I haven't tried it tho). Check your syslog.conf (or disable syslogd and see what happens). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 7:14:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta03.mail.mel.aone.net.au (mta03.mail.au.uu.net [203.2.192.83]) by hub.freebsd.org (Postfix) with ESMTP id 28BB637B401 for ; Fri, 12 Jan 2001 07:14:36 -0800 (PST) Received: from camtech.net.au ([203.55.243.26]) by mta03.mail.mel.aone.net.au with ESMTP id <20010112151432.HXWA4972.mta03.mail.mel.aone.net.au@camtech.net.au>; Sat, 13 Jan 2001 02:14:32 +1100 Message-ID: <3A5F1FDE.AAF40577@camtech.net.au> Date: Sat, 13 Jan 2001 01:46:46 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <672.979299461@axl.fw.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Fri, 12 Jan 2001 22:01:03 +1030, Matthew Thyer wrote: > > > This seems a bit of a pain. > > > > Is there anyway to go back (if I'm correct) to a dynamic swap user. > > I suppose I'm talking about a real tmpfs ? > > The way it is now is the way it's always been. Think about what you > mean when you say "dynamic swap user". You want mfs to use more swap > than you have? :-) No I want mfs to grow and shrink its filesystem dynamically. I never had these messages until recent changes in mfs but it will take me too much time to narrow it down as the message is hard to reproduce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 7:53:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 0A36637B69F for ; Fri, 12 Jan 2001 07:53:29 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14H6W1-0001xw-00; Fri, 12 Jan 2001 17:53:21 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id RAA17749; Fri, 12 Jan 2001 17:53:20 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 17557; Fri Jan 12 17:52:45 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14H6VR-0000lN-00; Fri, 12 Jan 2001 17:52:45 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-reply-to: Your message of "Sat, 13 Jan 2001 01:46:46 +1030." <3A5F1FDE.AAF40577@camtech.net.au> Date: Fri, 12 Jan 2001 17:52:45 +0200 Message-ID: <2936.979314765@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Jan 2001 01:46:46 +1030, Matthew Thyer wrote: > > The way it is now is the way it's always been. Think about what you > > mean when you say "dynamic swap user". You want mfs to use more swap > > than you have? :-) > > No I want mfs to grow and shrink its filesystem dynamically. Then don't limit the size! :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 8:40: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9370637B400; Fri, 12 Jan 2001 08:39:45 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0CGdjs81328; Fri, 12 Jan 2001 09:39:45 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101121639.f0CGdjs81328@harmony.village.org> To: Maxim Sobolev Subject: Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/etc/mtree BSD.root.dist src/libexec Makefile src/libexec/save-entropy Makefile save-entropy.sh Cc: current@FreeBSD.org In-reply-to: Your message of "Fri, 12 Jan 2001 12:14:43 +0200." <3A5ED913.6B09A21F@FreeBSD.org> References: <3A5ED913.6B09A21F@FreeBSD.org> <200101120644.f0C6hvI12630@gratis.grondar.za> <200101120534.f0C5YYH96390@earth.backplane.com> <200101120652.f0C6qls78578@harmony.village.org> <200101120711.f0C7B4Y97991@earth.backplane.com> Date: Fri, 12 Jan 2001 09:39:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A5ED913.6B09A21F@FreeBSD.org> Maxim Sobolev writes: : I like this idea, but perhaps it would be nice to have more : fine-grained control over when /dev/random is blocking and when : not. Why not to add sysctl to switch between blocking/non-blocking : behaviour (defaulting to non-blocking), so our startup scripts would : be able to switch /dev/random to be secure at the point when it's : safe to do (all f/s mounted) much like it copes with : kern.securelevel. Additionaly it would solve the problem that you : are not able to use almost anything in single-user mode (less, vi, : ee etc) w/o feeding /dev/random by hand first. That's why I had the first write clause in my statement. The act of seeing it, which writes to /dev/random, would be enough. No need to make it more complex than it has to be. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 8:43:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3181037B6A1 for ; Fri, 12 Jan 2001 08:43:05 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0CGgXs81367; Fri, 12 Jan 2001 09:42:33 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101121642.f0CGgXs81367@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: YES! laptop installing Cc: Mark Murray , Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Jan 2001 07:58:38 MST." <200101121458.f0CEwcs10477@aslan.scsiguy.com> References: <200101121458.f0CEwcs10477@aslan.scsiguy.com> Date: Fri, 12 Jan 2001 09:42:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101121458.f0CEwcs10477@aslan.scsiguy.com> "Justin T. Gibbs" writes: : >: MAC=00:00:80:00:00:80, FWIW. : > : >There's about 4 different dc based cards that don't work because they : >don't get the nic address right. Well, that's what I think. : : That is fixed with my cardbus patch set... at least for the xircom. : It should be trivial to fix for the others if they store their : nic address the same way. Interestingly enough, they do. However, of all my cards, the both my xircom just work w/o this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 9:10: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.iadfw.net (mail2.iadfw.net [206.66.12.234]) by hub.freebsd.org (Postfix) with SMTP id 0349C37B404 for ; Fri, 12 Jan 2001 09:09:49 -0800 (PST) Received: from Jason from [64.31.207.237] by mail2.iadfw.net (/\##/\ Smail3.1.30.16 #30.27) with smtp for sender: id ; Fri, 12 Jan 2001 11:09:51 -0600 (CST) Message-ID: <000f01c07cbb$379df040$edcf1f40@pdq.net> From: "Jason Smethers" To: Subject: module privlages Date: Fri, 12 Jan 2001 11:15:09 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone put any thought into putting restrictions on what a module can modify when loaded into the kernel? If there is, say, ever binary third party driver support and this is provided without source some restrictions on what kernel data this module can link to and modify when loaded might be a good idea. I was thinking something along the lines of a list of symbols that a kernel module may call, and a list of symbols that a kernel module may modify. Allowing the update of these lists may be a little tricky to prevent already load modules from detecting this and adding their own symbols. Doing this with module types might be simple. When a module is loaded it would contain flags to the module type(s) it is uses and this selects the list of symbols it may interact with. A module may be then be used to update these symbols but root is warned and must OK a load of a kernel module with the type which allows updating the symbol lists. With the module types it would also help prevent a module from messing around in an area that is not expected from such a module. e.g. a network driver messing around in the VFS. Any thoughts? - Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 9:44: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 8817337B401; Fri, 12 Jan 2001 09:43:47 -0800 (PST) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id f0CHhek18470; Sat, 13 Jan 2001 02:43:40 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: current@freebsd.org, hackers@freebsd.org Subject: Re: CFR: Generalized power-management interface In-Reply-To: <20001231180216L.iwasaki@jp.FreeBSD.org> References: <20001231180216L.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010113024339Z.iwasaki@jp.FreeBSD.org> Date: Sat, 13 Jan 2001 02:43:39 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 59 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've update the patch based on some comments so far and added wmpm (actually ACPI support for wmapm which is utility for WindowMaker) ports files as a example. http://people.freebsd.org/~iwasaki/acpi/power-20010113.tar.gz http://people.freebsd.org/~iwasaki/acpi/wmpm-20010113.tar.gz Note that ioctl number for power device have been changed, so rebuilding your kernel and recompiling lib/libpower/ and usr.sbin/power/ are needed. Added API is; u_int power_get_pm_type(void); I'll get device major number for /dev/power and commit them within a few days if no objection. Thanks > I've created new common framework on generalized power-management > interface for userland utilities. > > http://people.freebsd.org/~iwasaki/acpi/power-20001229.tar.gz > > This provides some PM APIs to APM applications, such as wmapm, so that > these applications can be ported smoothly to use ACPI (power > management portion). Currently following APIs are implemented; > > int power_get_syspm_info(struct power_syspm_info *); > int power_get_batt_info(u_int, struct power_batt_info *); > int power_standby(void); > int power_suspend(void); > int power_hibernate(void); > > And PM event notification mechanism is suggested to be implemented so far. > > Sample application is included in usr.sbin/power/ which is very similar > to apm(8) but supports ACPI as well. > > usr.sbin/acpi/acpibatt/ is for displaying acpi_cmbat (ACPI Control > Method Battery), can be used to verify that generalized > power-management interface is working correctly. > Note that many ACPI BIOS give us unknown battery remaining time when > ac-line is plugged in. MIB 'hw.battery.full_charge_time' can be used to > specify the full charged remaining time of batteries in minutes, like > sysctl -w hw.battery.full_charge_time=60,60 > for multiple number of batteries, or > sysctl -w hw.battery.full_charge_time=120 > for a battery installed. > > To test them, /dev/power is required as a device control file. > > % ls -l /dev/power > crw-r--r-- 1 root wheel 210, 0 12/19 04:51 /dev/power > > I'll commit them at sometime early in coming century. > > Any comments would be appreciated. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 9:59:11 2001 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 423C637B401; Fri, 12 Jan 2001 09:58:52 -0800 (PST) Subject: Any people with 3c905CX cards out there? To: freebsd-current@freebsd.org Date: Fri, 12 Jan 2001 09:58:52 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010112175852.423C637B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3Com has yet another revision of the Tornado chipset floating around out there on newer 3c905C adapters. Supposedly, these are marked as 3c905CX and have become available within the last couple of months. I've seen some noise on the Linux mailing lists that seems to indicate that some driver mods were necessary due to reset timing differences introduced in the new chipset, however I haven't been able to get my hands on one of these cards yet so I don't know whether or not there are also problems with FreeBSD. Nobody has reported any yet, but it would be nice to confirm the issue one way or the other. If someone has one of these cards and is using it with the xl driver, I'd be interested to know how well (or how badly) it's working. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 10:49:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 7B40437B401 for ; Fri, 12 Jan 2001 10:48:55 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0CImeb18577; Fri, 12 Jan 2001 20:48:40 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id f0CIDwr23056; Fri, 12 Jan 2001 20:13:58 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A5F4960.76BB8A2B@FreeBSD.org> Date: Fri, 12 Jan 2001 20:13:52 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.org Subject: Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/etc/mtree BSD.root.dist src/libexec Makefile src/libexec/save-entropy Makefile save-entropy.sh References: <3A5ED913.6B09A21F@FreeBSD.org> <200101120644.f0C6hvI12630@gratis.grondar.za> <200101120534.f0C5YYH96390@earth.backplane.com> <200101120652.f0C6qls78578@harmony.village.org> <200101120711.f0C7B4Y97991@earth.backplane.com> <200101121639.f0CGdjs81328@harmony.village.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <3A5ED913.6B09A21F@FreeBSD.org> Maxim Sobolev writes: > : I like this idea, but perhaps it would be nice to have more > : fine-grained control over when /dev/random is blocking and when > : not. Why not to add sysctl to switch between blocking/non-blocking > : behaviour (defaulting to non-blocking), so our startup scripts would > : be able to switch /dev/random to be secure at the point when it's > : safe to do (all f/s mounted) much like it copes with > : kern.securelevel. Additionaly it would solve the problem that you > : are not able to use almost anything in single-user mode (less, vi, > : ee etc) w/o feeding /dev/random by hand first. > > That's why I had the first write clause in my statement. The act of > seeing it, which writes to /dev/random, would be enough. No need to > make it more complex than it has to be. Seeding it with *something* (ls, vmstat, date etc) is not equial to seeding it properly, i.e using data with high enough amount of entropy in it. Therefore, such sysctl may be potentially used to determine that random generator is in insecure state and should not be used for anything that require high level of randomness (key generation for example - ssh may check such sysctl and refuse to generate a key or at least warn a user about possible problems). Just my UAH0.02 ;). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 11:39:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 4AAB437B402; Fri, 12 Jan 2001 11:39:07 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14HA2S-0003rW-00; Fri, 12 Jan 2001 21:39:04 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id VAA19674; Fri, 12 Jan 2001 21:39:02 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 19664; Fri Jan 12 21:38:40 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14HA24-0001IC-00; Fri, 12 Jan 2001 21:38:40 +0200 From: Sheldon Hearn To: Neil Blakey-Milner Cc: electro , freebsd-current@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Bug in src tree? In-reply-to: Your message of "Fri, 12 Jan 2001 11:24:38 +0200." <20010112112438.A84108@mithrandr.moria.org> Date: Fri, 12 Jan 2001 21:38:40 +0200 Message-ID: <4971.979328320@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Jan 2001 11:24:38 +0200, Neil Blakey-Milner wrote: > > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > > instruction > > *** Error code 1 > > > > Stop in /usr/src/sys/compile/PROFESSOR.010110. > > You're not using buildkernel, and thus you don't have the necessarily > updated tools to handle that source. Are you sure? I think "electro" _is_ using buildkernel but without a buildworld. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 11:43:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id CD58737B400 for ; Fri, 12 Jan 2001 11:43:13 -0800 (PST) Received: (qmail 15285 invoked by uid 1003); 12 Jan 2001 19:43:11 -0000 Date: Fri, 12 Jan 2001 21:43:11 +0200 From: Neil Blakey-Milner To: Sheldon Hearn Cc: electro , freebsd-current@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Bug in src tree? Message-ID: <20010112214311.A13973@mithrandr.moria.org> References: <20010112112438.A84108@mithrandr.moria.org> <4971.979328320@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4971.979328320@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Fri, Jan 12, 2001 at 09:38:40PM +0200 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2001-01-12 (21:38), Sheldon Hearn wrote: > > > On Fri, 12 Jan 2001 11:24:38 +0200, Neil Blakey-Milner wrote: > > > > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > > > instruction > > > *** Error code 1 > > > > > > Stop in /usr/src/sys/compile/PROFESSOR.010110. > > > > You're not using buildkernel, and thus you don't have the necessarily > > updated tools to handle that source. > > Are you sure? I think "electro" _is_ using buildkernel but without a > buildworld. Oops, that's quite possible too. Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 12:42:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 2270B37B402; Fri, 12 Jan 2001 12:42:26 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 16F93198B; Fri, 12 Jan 2001 15:42:24 -0500 (EST) Date: Fri, 12 Jan 2001 15:42:24 -0500 From: Will Andrews To: electro Cc: FreeBSD Stable Subject: Re: Bug in src tree? Message-ID: <20010112154224.E471@puck.firepipe.net> Reply-To: Will Andrews References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from electro_p@hotmail.com on Fri, Jan 12, 2001 at 08:17:01AM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ .. moved to -stable .. ] On Fri, Jan 12, 2001 at 08:17:01AM +0100, electro wrote: > I try to compile a new kernel with the latest source and I always end up > with this (in the end). Any suggestions? > I mean the error message is fun...dont match any know i386 instruction???? [...] > /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 > instruction > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > instruction [...] You appear to be upgrading from a very old version of FreeBSD. The last time I encountered this was when binutils was upgraded in 4.x-STABLE around July or August 2000. In any case that means (most likely) that you may need to install the newer binutils manually before compiling. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 12:44:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from [213.104.69.98] (m354-mp1-cvx1a.col.ntl.com [213.104.69.98]) by hub.freebsd.org (Postfix) with ESMTP id 1FBD137B400 for ; Fri, 12 Jan 2001 12:44:14 -0800 (PST) Received: by boreas (chainmail); Fri, 12 Jan 2001 20:45:59 GMT To: Subject: ext2 root filesystem From: "John Fremlin" Date: 12 Jan 2001 20:45:58 +0000 Message-ID: Lines: 15 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (GTK) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to have an ext2 filesystem on /? Sorry if this is a FAQ, but I couldn't find any details after a bit of searching. Two issues come to my inexperienced mind. There is the trouble of booting the kernel. GRUB can grok ext2 so I could use that (or at least, I could probably hack GRUB till it can boot FreeBSD again). But before that there is probably going to be a problem building the kernel. Does anybody have any experience doing a cross compile from Linux? -- http://www.penguinpowered.com/~vii To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 13:27: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id D02E037B400 for ; Fri, 12 Jan 2001 13:26:43 -0800 (PST) Received: (qmail 3466 invoked by uid 1000); 12 Jan 2001 21:20:29 -0000 Date: Fri, 12 Jan 2001 22:20:29 +0100 From: Andrea Campi To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: YES! laptop installing Message-ID: <20010112222029.C560@webcom.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from culverk@wam.umd.edu on Wed, Jan 10, 2001 at 12:04:17AM -0500 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 12:04:17AM -0500, Kenneth Wayne Culver wrote: > This is to let everyone know that right now as I type I am setting up > FreeBSD to start downloading over my cardbus ethernet card. It seems to > work great except it doesn't beep when the card enables, but that's fine > with me. :-) Just to add my $0.02, and in case anybody cares... Cardbus is working ok on by Thinkpad with a 3Com pccard, except that the system freezes when I remove the card... Bye, Andrea -- The dark ages were caused by the Y1K problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 13:58:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 075FC37B401 for ; Fri, 12 Jan 2001 13:58:10 -0800 (PST) Received: from dwcjr.inethouston.net (unknown [216.118.21.154]) by leviathan.inethouston.net (Postfix) with SMTP id E0831177EF1 for ; Fri, 12 Jan 2001 15:58:12 -0600 (CST) From: David W.Chapman Jr. To: current@FreeBSD.org Subject: unknown devices Date: Fri, 12 Jan 2001 15:58:08 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01011215580804.01504@dwcjr.inethouston.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Down near the botton I have some unknown pnp devices, is there any way to figure out what devices they are, they must be motherboard resources because all other devices seem to be accounted for. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Fri Jan 12 11:14:56 CST 2001 poseiden@dwcjr.inethouston.net:/usr/src/sys/compile/DWCJR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1102506314 Hz CPU: AMD Athlon(tm) Processor (1102.51-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 402587648 (393152K bytes) config> avail memory = 387854336 (378764K bytes) Preloaded elf kernel "kernel" at 0xc03b3000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03b309c. Preloaded elf module "vesa.ko" at 0xc03b30ec. Preloaded elf module "if_xl.ko" at 0xc03b3188. Preloaded elf module "miibus.ko" at 0xc03b3228. Preloaded elf module "usb.ko" at 0xc03b32c8. Preloaded elf module "bktr.ko" at 0xc03b3364. Preloaded elf module "bktr_mem.ko" at 0xc03b3400. Preloaded elf module "random.ko" at 0xc03b34a0. Preloaded elf module "agp.ko" at 0xc03b3540. Preloaded elf module "snd_es137x.ko" at 0xc03b35dc. Preloaded elf module "snd_pcm.ko" at 0xc03b3680. bktr_mem: memory holder loaded Pentium Pro MTRR support enabled VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc032a2e2 (1000022) VESA: NVidia ACPI debug layer 0x0 debug level 0x0 Using $PIR table, 8 entries at 0xc00f7960 acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. acpi_tz0: on acpi0 acpi_tz0: current temperature 52.0C acpi_button0: on acpi0 acpi_pcib0: on acpi0 pci0: on acpi_pcib0 agp0: mem 0xe0000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.4 (no driver attached) ahc0: port 0xd800-0xd8ff mem 0xdffff000-0xdfffffff irq 9 at device 12.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs bktr0: mem 0xdddfc000-0xdddfcfff irq 10 at device 13.0 on pci0 bktr0: Warning - card vendor 0x1002 (model 0x0001) unknown. bktr0: Detected a MSP3430G-A4 at 0x80 bktr0: Pinnacle/Miro TV, Temic NTSC tuner, msp3400c stereo. pci0: at 13.1 (no driver attached) pcm0: port 0xd400-0xd43f irq 11 at device 14.0 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem 0xdfffef80-0xdfffefff irq 5 at device 15.0 on pci0 xl0: Ethernet address: 00:50:04:b7:13:09 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto acpi_button1: on acpi0 acpi_timer0: <24-bit timer at 3.579545MHz> on acpi0 npx0: on motherboard npx0: INT 16 interface atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 pmtimer0 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 6149MB [13328/15/63] at ata0-master UDMA66 ad1: 2317MB [4708/16/63] at ata0-slave UDMA33 acd0: CDROM at ata1-master using PIO4 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad1s1a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [1 x 2048 byte records] pcm0: hwptr went backwards 2208 -> 2016 ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 14:46: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 11B5437B400 for ; Fri, 12 Jan 2001 14:45:41 -0800 (PST) Received: from kairo-46.budapest.interware.hu ([195.70.50.110] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14HCwq-0002Rb-00; Fri, 12 Jan 2001 23:45:28 +0100 Message-ID: <3A5F16D8.2E1B471C@elischer.org> Date: Fri, 12 Jan 2001 06:38:16 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-current@freebsd.org, 'Alfred Perlstein' Subject: Re: Running Linux kernel modules. References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > > > > > To handle the multiple open problem, I'm overloading the open and > close system calls. Upon open, I call the native open, then I grovel > around in the process' open file table looking for my special file. > When I find it, I mark fp->f_nextread with a magic number, then store > a pointer to the per-open private data in fp->f_offset. On close, I > go grovelling again. I deallocate the private data, clear the magic > number, and call the system close function. I've also got an > at_exit() hook that does much the same thing. > > Obtaining the file descripter at ioctl() and mmap() time is much more > interesting. When I'm called from a syscall, I pull the args out of > the process and grab the fd, index the process' file table and bingo. > > The real problem is when mmap is called out of a fault (and not > dev_pager_alloc, which is what gets called when the mmap syscall is > issued). Right now I throw up my hands and return the private data > from the first instance I find when walking the process' open file > table. If this becomes a problem, I'm planning on prefaulting the > pages at dev_pager_alloc() time (when I can get an fd from the > process) and wiring them -- its only 20k per process.. > > Isn't this gross? Is there a better way? I think that the better way is to actually have each open have a different minor number. i.e. each process opens a different copy. The way to achieve this best is with cloning devices. apply within phk for more info :-) I could imagine however that you could assume that each process opens the device only once, and thus have a hash-table of private info, keyed on curproc. You should be able to store the curproc key with the request currently being serviced so that teh interrupt routines can also use the same key. > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 14:46:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 5281B37B402; Fri, 12 Jan 2001 14:45:43 -0800 (PST) Received: from kairo-46.budapest.interware.hu ([195.70.50.110] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14HCws-0002Rr-00; Fri, 12 Jan 2001 23:45:31 +0100 Message-ID: <3A5F1788.9AD8509A@elischer.org> Date: Fri, 12 Jan 2001 06:41:12 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Jun Kuriyama Cc: net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <3A5567A7.A11F47E3@elischer.org> <3A566BCB.BFD6FA2D@elischer.org> <7m1yu9mdlt.wl@waterblue.imgsrc.co.jp> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama wrote: > > Hi Julian, > > I tried netgraph for the first time to work with latest vmware2 port. > > When I try to load netgraph kernel module, it failed with: > > # kldload ng_bridge > kldload: can't load ng_bridge: Exec format error something is terribly broken with the kld loading at the moment. netgraph actually tries to load modules it needs but it hasn't been able to for some months. Also kldload ca SEE what the dependency is so the module is telling it correctly, just the kernel is failing to load the dependency.. I don't think this is Netgraph's fault. we haven;t changed anything.. it just stopped working one day. > > And /var/log/messages says: > > Jan 12 16:27:07 waterblue /boot/kernel/kernel: KLD ng_bridge.ko: depends on ng_ether - not available > > But ng_ether.ko is already loaded automatically (checked by kldstat). > > Is this known problem, or my local configuration mistake? > > # My environment is "make world"ed yesterday and kernel is latest. > > -- > Jun Kuriyama // IMG SRC, Inc. > // FreeBSD Project -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 15:10:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3496437B400 for ; Fri, 12 Jan 2001 15:10:24 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA29186; Fri, 12 Jan 2001 15:10:17 -0800 Date: Fri, 12 Jan 2001 15:10:16 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: sio && serial console in -current? In-Reply-To: <3A5F1F05.B9A3C536@camtech.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting theory, but no- that wasn't it. > Matthew Jacob wrote: > > > > Something wierd has been happening lately- the serial console on my i386 > > machine works fine up until init is forked.. THen the output is mangled, and > > one gets replicated and/or mangled stuff. On a reboot I'm getthing things > > like: > > > > WWWWWaaaaaiiiiitttttiiiiinnnnnggggg (((((mmmmmaaaaaxxxxx 6666600000 > > ssssseeeeecccccooooonnnnndddddsssss))))) fffffooooorrrrr > > sssssyyyyysssssttttteeeeemmmmm ppppprrrrroooooccccceeeeessssssssss > > `````bbbbbuuuuufffffdddddaaaaaeeeeemmmmmooooonnnnn''''' tttttooooo > > ssssstttttoooooppppp...............ssssstttttoooooppppppppppeeeeeddddd > > > > It's like the output is being repeated... > > > > Anyone seen same? > > My guess is you might be using PHK's syslog feature and be sending > console output to the console ? (I haven't tried it tho). > > Check your syslog.conf (or disable syslogd and see what happens). > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 15:27:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 19FF737B400; Fri, 12 Jan 2001 15:26:56 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id AAA12528; Sat, 13 Jan 2001 00:26:33 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Julian Elischer Cc: Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming References: <3A5567A7.A11F47E3@elischer.org> <3A566BCB.BFD6FA2D@elischer.org> <7m1yu9mdlt.wl@waterblue.imgsrc.co.jp> <3A5F1788.9AD8509A@elischer.org> From: Dag-Erling Smorgrav Date: 13 Jan 2001 00:26:28 +0100 In-Reply-To: Julian Elischer's message of "Fri, 12 Jan 2001 06:41:12 -0800" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > Jun Kuriyama wrote: > > # kldload ng_bridge > > kldload: can't load ng_bridge: Exec format error > > And /var/log/messages says: > > > > Jan 12 16:27:07 waterblue /boot/kernel/kernel: KLD ng_bridge.ko: depends on ng_ether - not available > > something is terribly broken with the kld loading at the moment. Something is terribly broken with ng_ether at the moment. It lacks a MODULE_VERSION line. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 15:28:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2B9D037B400; Fri, 12 Jan 2001 15:28:35 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA16979; Fri, 12 Jan 2001 18:28:34 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0CNSYH05299; Fri, 12 Jan 2001 18:28:34 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 12 Jan 2001 18:28:34 -0500 (EST) To: Julian Elischer Cc: phk@freebsd.org, freebsd-current@freebsd.org Subject: Re: Running Linux kernel modules. In-Reply-To: <3A5F16D8.2E1B471C@elischer.org> References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> <3A5F16D8.2E1B471C@elischer.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14943.37198.480690.136547@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > > > > Isn't this gross? Is there a better way? > > I think that the better way is to actually have each open have a > different minor number. > i.e. each process opens a different copy. > The way to achieve this best is with cloning devices. > apply within phk for more info :-) Does this mean that the processes can open /dev/foo0 twice and the driver sees a different minor number for each open? Or does it mean that the process has to open /dev/foo0 and /dev/foo1? If the former, that's awesome!... How do I use it? If the latter, then it isn't practical for things like vmware and my Giganet VI driver because both depend on closed-source userland code which cannot be taught to open differently named special files. > I could imagine however that you could assume that each process > opens the device only once, and thus have a hash-table of > private info, keyed on curproc. You should be able to store the curproc > key with the request currently being serviced so that teh interrupt routines > can also use the same key. It would simplifly things, but I don't think that this is going to be a valid assumption in general.. Thanks! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 16: 3:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 3C38937B400 for ; Fri, 12 Jan 2001 16:03:19 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0D02fk16650; Fri, 12 Jan 2001 16:02:41 -0800 (PST) (envelope-from dillon) Date: Fri, 12 Jan 2001 16:02:41 -0800 (PST) From: Matt Dillon Message-Id: <200101130002.f0D02fk16650@earth.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG, "'Alfred Perlstein'" Subject: Re: RE: Running Linux kernel modules. References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :To handle the multiple open problem, I'm overloading the open and :close system calls. Upon open, I call the native open, then I grovel :around in the process' open file table looking for my special file. :When I find it, I mark fp->f_nextread with a magic number, then store :a pointer to the per-open private data in fp->f_offset. On close, I :go grovelling again. I deallocate the private data, clear the magic :number, and call the system close function. I've also got an :at_exit() hook that does much the same thing. Wait a sec... f_nextread and f_offset can be messed around with by the user process, what prevents the user process from screwing up your kernel data pointer? Why not just track the opens independantly in the overloading code? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 16: 4:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 8DEB137B400; Fri, 12 Jan 2001 16:04:13 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id RAA18043; Fri, 12 Jan 2001 17:03:57 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id RAA16065; Fri, 12 Jan 2001 17:03:56 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14943.39713.160666.695146@nomad.yogotech.com> Date: Fri, 12 Jan 2001 17:02:41 -0700 (MST) To: Mark Murray Cc: Doug Barton , Warner Losh , Sheldon Hearn , markm@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: entropy bikesheds In-Reply-To: <200101120619.f0C6JQI12558@gratis.grondar.za> References: <200101120619.f0C6JQI12558@gratis.grondar.za> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can we decide this, please - do we want secure startup (which will > take some effort to achieve), or can we say "screw it" and start > insecure like the old system? Can we have both? Ie; by default we are insecure until some point we call an ioctl() that says 'no more, you must get real randomness now'. So, that way we can do the stuff that doesn't require real randomness (like mounting disks and such), and then once that's over with, the system forces it into 'secure' mode, at which time it's up to the user to supply some randomness for it. If that happens, a user could decide comment out the 'real secure' thing, and /dev/random would never block. You can all laugh at me now. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 16: 6: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 0DCE137B400 for ; Fri, 12 Jan 2001 16:05:49 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0D05Vs13002; Fri, 12 Jan 2001 17:05:31 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101130005.f0D05Vs13002@aslan.scsiguy.com> To: Warner Losh Cc: Mark Murray , Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: YES! laptop installing In-Reply-To: Your message of "Fri, 12 Jan 2001 09:42:33 MST." <200101121642.f0CGgXs81367@harmony.village.org> Date: Fri, 12 Jan 2001 17:05:31 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: That is fixed with my cardbus patch set... at least for the xircom. >: It should be trivial to fix for the others if they store their >: nic address the same way. > >Interestingly enough, they do. However, of all my cards, the both my >xircom just work w/o this. > >Warner The dc driver would get the mac address wrong for one of my xircom cards but not so wrong as to make it non-functional. The other xircom card (the type-III with modem) seemed to end up with a mac address that was considered invalid by many switches. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 16:16: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 49E9537B401; Fri, 12 Jan 2001 16:15:44 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0D0Fb209446; Fri, 12 Jan 2001 16:15:37 -0800 (PST) Date: Fri, 12 Jan 2001 16:15:37 -0800 From: Alfred Perlstein To: Andrew Gallatin Cc: Julian Elischer , phk@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Running Linux kernel modules. Message-ID: <20010112161535.B7240@fw.wintelcom.net> References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> <3A5F16D8.2E1B471C@elischer.org> <14943.37198.480690.136547@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14943.37198.480690.136547@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, Jan 12, 2001 at 06:28:34PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Andrew Gallatin [010112 15:29] wrote: > > Julian Elischer writes: > > > > > > Isn't this gross? Is there a better way? > > > > I think that the better way is to actually have each open have a > > different minor number. > > i.e. each process opens a different copy. > > > The way to achieve this best is with cloning devices. > > apply within phk for more info :-) > > Does this mean that the processes can open /dev/foo0 twice and the > driver sees a different minor number for each open? Or does it mean > that the process has to open /dev/foo0 and /dev/foo1? > > If the former, that's awesome!... How do I use it? Well you have to write it, but you basically have the open(2) syscall path optionally return a seperate void * 'cookie' that you must pass into all operations (fileops) on that file. It's not a major rewrite of any code, you just need an extra parameter per fileop and store it in the struct file. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 16:27:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from email_server.midstream.com (unknown [63.113.115.195]) by hub.freebsd.org (Postfix) with ESMTP id 8F5C737B402 for ; Fri, 12 Jan 2001 16:27:18 -0800 (PST) Received: by EMAIL_SERVER with Internet Mail Service (5.5.2650.21) id ; Fri, 12 Jan 2001 16:29:37 -0800 Message-ID: <31E4B6337A4FD411BD45000102472E0C05E72A@EMAIL_SERVER> From: Jeff Roberson To: 'Bruce Evans' Cc: "'freebsd-current@freebsd.org'" Subject: RE: Broken mmap in current? Date: Fri, 12 Jan 2001 16:29:29 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C07CF7.E8E735A0" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C07CF7.E8E735A0 Content-Type: text/plain; charset="iso-8859-1" I think I spoke too soon.. I saw thousands of calls to mmap and assumed it was the thousands of read/writes that I was doing. It's actually for the thousands (8192) of pages that I'm mapping in. Oddly enough though there are only 3272 calls to my mmap routine each time I run the program. I will investigate further. I did find a bug in mlock() and munlock(). I tried mlock()ing after I mmaped, which I later realized was bogus since the pages are always resident as they exist on the bus. Anyway the kernel faults in vm_page_unwire when I munlock. I will investigate further and post a pr though. Thanks for your help! Jeff -----Original Message----- From: Bruce Evans [mailto:bde@zeta.org.au] Sent: Thursday, January 11, 2001 8:52 PM To: Jeff Roberson Cc: 'freebsd-current@freebsd.org' Subject: Re: Broken mmap in current? On Thu, 11 Jan 2001, Jeff Roberson wrote: > I have written a character device driver for a proprietary PCI device that > has a large sum of mapable memory. The character device supports mmap() > which I use to export the memory into a user process. I have no problems > accessing the memory on this device, but I notice that my mmap routine is > called for every access! Is this a problem with current, or a problem with > my mmap? Maybe both. The device mmap routine is called mainly by the mmap syscall for every page to be mmapped. It is also called by dev_pager_getpages() for some pagefaults, but I think this rarely happens. > I use bus_alloc_resource and then rman_get_start to get the physical address > in my attach, and then the mmap just returns atop(physical address). I > assumed this is correct since I have verified with a logical analyzer that I > am indeed writing to the memory on the device. This is correct. I looked at some examples. Many drivers get this wrong by using i386_btop(), alpha_btop(), etc. (AFAIK, atop() is for addresses which are what we are converting here, btop() is for (byte) offsets, and the machine-dependent prefixes are a vestige of page clustering code that mostly went away 7 years ago. > Also, I noticed that the > device's mmap interface does not provide any way to limit the size of the > block being mapped? Can I specify the length of the region? The length is implicitly PAGE_SIZE. The device mmap function is called for each page to be mapped. It must verify that the memory from offset to (offset + PAGE_SIZE - 1) belongs to the device and can be accessed with the given protection, and do any device-specific things necessary to enable this memory. This scheme can't support bank-switched device memory very well, if at all. pcvvt_mmap() in the pcvt driver is the simplest example of this. agp_mmap() is a more up to date example with the same old bug that the vga drivers used to have (off by 1 (page) error checking the offset). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message ------_=_NextPart_001_01C07CF7.E8E735A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Broken mmap in current?

I think I spoke too soon..  I saw thousands of = calls to mmap and assumed it was the thousands of read/writes that I = was doing.  It's actually for the thousands (8192) of pages that = I'm mapping in.  Oddly enough though there are only 3272 calls to = my mmap routine each time I run the program.  I will investigate = further.

I did find a bug in mlock() and munlock().  I = tried mlock()ing after I mmaped, which I later realized was bogus since = the pages are always resident as they exist on the bus.  Anyway = the kernel faults in vm_page_unwire when I munlock.  I will = investigate further and post a pr though.

Thanks for your help!
Jeff

-----Original Message-----
From: Bruce Evans [mailto:bde@zeta.org.au]
Sent: Thursday, January 11, 2001 8:52 PM
To: Jeff Roberson
Cc: 'freebsd-current@freebsd.org'
Subject: Re: Broken mmap in current?


On Thu, 11 Jan 2001, Jeff Roberson wrote:

> I have written a character device driver for a = proprietary PCI device that
> has a large sum of mapable memory.  The = character device supports mmap()
> which I use to export the memory into a user = process.  I have no problems
> accessing the memory on this device, but I = notice that my mmap routine is
> called for every access!  Is this a = problem with current, or a problem with
> my mmap?

Maybe both.  The device mmap routine is called = mainly by the mmap
syscall for every page to be mmapped.  It is = also called by
dev_pager_getpages() for some pagefaults, but I = think this rarely happens.

> I use bus_alloc_resource and then rman_get_start = to get the physical address
> in my attach, and then the mmap just returns = atop(physical address).  I
> assumed this is correct since I have verified = with a logical analyzer that I
> am indeed writing to the memory on the = device.

This is correct.  I looked at some = examples.  Many drivers get this
wrong by using i386_btop(), alpha_btop(), etc.  = (AFAIK, atop() is
for addresses which are what we are converting here, = btop() is for
(byte) offsets, and the machine-dependent prefixes = are a vestige of
page clustering code that mostly went away 7 years = ago.

> Also, I noticed that the
> device's mmap interface does not provide any = way to limit the size of the
> block being mapped?  Can I specify the = length of the region?

The length is implicitly PAGE_SIZE.  The device = mmap function is called
for each page to be mapped.  It must verify = that the memory from offset
to (offset + PAGE_SIZE - 1) belongs to the device = and can be accessed
with the given protection, and do any = device-specific things necessary to
enable this memory.  This scheme can't support = bank-switched device
memory very well, if at all.

pcvvt_mmap() in the pcvt driver is the simplest = example of this.
agp_mmap() is a more up to date example with the = same old bug that the
vga drivers used to have (off by 1 (page) error = checking the offset).

Bruce



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

------_=_NextPart_001_01C07CF7.E8E735A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 17:51:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id EBA4D37B404 for ; Fri, 12 Jan 2001 17:51:04 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id RAA24795; Fri, 12 Jan 2001 17:52:21 -0800 Date: Fri, 12 Jan 2001 17:52:21 -0800 From: Kris Kennaway To: Jason Smethers Cc: current@FreeBSD.ORG Subject: Re: module privlages Message-ID: <20010112175221.E23818@citusc.usc.edu> References: <000f01c07cbb$379df040$edcf1f40@pdq.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T6xhMxlHU34Bk0ad" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000f01c07cbb$379df040$edcf1f40@pdq.net>; from jsmethers@pdq.net on Fri, Jan 12, 2001 at 11:15:09AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --T6xhMxlHU34Bk0ad Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm not sure what the point of this would really be..nor how you could enforce it. Perhaps you should submit a proof of concept ;-) Kris On Fri, Jan 12, 2001 at 11:15:09AM -0600, Jason Smethers wrote: > Has anyone put any thought into putting restrictions on what a module > can modify when loaded into the kernel? If there is, say, ever binary > third party driver support and this is provided without source some > restrictions on what kernel data this module can link to and modify > when loaded might be a good idea. >=20 > I was thinking something along the lines of a list of symbols that a > kernel module may call, and a list of symbols that a kernel module may > modify. Allowing the update of these lists may be a little tricky to > prevent already load modules from detecting this and adding their own > symbols. >=20 > Doing this with module types might be simple. When a module is loaded > it would contain flags to the module type(s) it is uses and this > selects the list of symbols it may interact with. A module may be then > be used to update these symbols but root is warned and must OK a load > of a kernel module with the type which allows updating the symbol > lists. >=20 > With the module types it would also help prevent a module from messing > around in an area that is not expected from such a module. e.g. a > network driver messing around in the VFS. >=20 > Any thoughts? >=20 > - Jason >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --T6xhMxlHU34Bk0ad Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6X7TVWry0BWjoQKURAoAJAJ4kptl5TXrqkz4eALO0h4OeVLEohACfSb0N TAsiZ+ZNryZFQz9IIVBTR3Q= =DwzM -----END PGP SIGNATURE----- --T6xhMxlHU34Bk0ad-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 18:47: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 0548E37B69B; Fri, 12 Jan 2001 18:46:49 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0D2kji18674; Fri, 12 Jan 2001 18:46:45 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Cc: jhb@freebsd.org Subject: Anybody else seeing a broken /dev/lpt with SMP on -current? Date: Fri, 12 Jan 2001 18:46:45 -0800 Message-ID: <18670.979354005@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've actually been seeing this for about 2 months now but only just now got motivated enough to enable crashdumps and get some information on what happens whenver I try to use the printer attached to my (sadly :) -current SMP box: IdlePTD 3682304 initial pcb at 2e70e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 00000000 fault virtual address = 0xffff8640 fault code = supervisor write, page not present instruction pointer = 0x8:0xc8dc8676 stack pointer = 0x10:0xc8280f88 frame pointer = 0x10:0xc8280f9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12322 (irq7: lpt0) trap number = 12 panic: page fault cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 If anybody wants a fuller traceback then I'll compile up a kernel with debugging symbols, but it's going to be pretty sparse anyway since it basically only shows the trap() from the page fault and the subsequent panic. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 18:56:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5F03137B400 for ; Fri, 12 Jan 2001 18:56:00 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0D2tD147465; Fri, 12 Jan 2001 18:55:13 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <18670.979354005@winston.osd.bsdi.com> Date: Fri, 12 Jan 2001 18:55:59 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: RE: Anybody else seeing a broken /dev/lpt with SMP on -current? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-01 Jordan Hubbard wrote: > I've actually been seeing this for about 2 months now but only just > now got motivated enough to enable crashdumps and get some information > on what happens whenver I try to use the printer attached to my (sadly :) > -current SMP box: > > IdlePTD 3682304 > initial pcb at 2e70e0 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > cpuid = 0; lapic.id = 00000000 > fault virtual address = 0xffff8640 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc8dc8676 > stack pointer = 0x10:0xc8280f88 > frame pointer = 0x10:0xc8280f9c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12322 (irq7: lpt0) > trap number = 12 > panic: page fault > cpuid = 0; lapic.id = 00000000 > boot() called on cpu#0 > > If anybody wants a fuller traceback then I'll compile up a kernel with > debugging symbols, but it's going to be pretty sparse anyway since it > basically only shows the trap() from the page fault and the subsequent > panic. All the other traces show the kerenl having returned to an address that is beyongd the end of the kernel (which causes the page fault) meaning that the stack is fubar'd, so the trace isn't meaningful anyways. :( Knowing how and why the lpd interrupt handler trashes the stack is the useful info, and with teh stack already trashed, I don't know of an easy way to figure that out. Suggestions welcome. > - Jordan -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 19: 6:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 259C637B400; Fri, 12 Jan 2001 19:05:55 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0D35sa13985; Fri, 12 Jan 2001 19:05:54 -0800 (PST) Date: Fri, 12 Jan 2001 19:05:54 -0800 From: Alfred Perlstein To: John Baldwin Cc: Jordan Hubbard , current@FreeBSD.ORG Subject: Re: Anybody else seeing a broken /dev/lpt with SMP on -current? Message-ID: <20010112190554.E7240@fw.wintelcom.net> References: <18670.979354005@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Fri, Jan 12, 2001 at 06:55:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Baldwin [010112 18:56] wrote: > > On 13-Jan-01 Jordan Hubbard wrote: > > I've actually been seeing this for about 2 months now but only just > > now got motivated enough to enable crashdumps and get some information > > on what happens whenver I try to use the printer attached to my (sadly :) > > -current SMP box: > > > > All the other traces show the kerenl having returned to an address that is > beyongd the end of the kernel (which causes the page fault) meaning that the > stack is fubar'd, so the trace isn't meaningful anyways. :( Knowing how and > why the lpd interrupt handler trashes the stack is the useful info, and with > teh stack already trashed, I don't know of an easy way to figure that out. > Suggestions welcome. printf(9) :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 20: 6:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E7D537B402 for ; Fri, 12 Jan 2001 20:06:15 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA19786; Fri, 12 Jan 2001 23:06:14 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0D46Ds07966; Fri, 12 Jan 2001 23:06:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 12 Jan 2001 23:06:13 -0500 (EST) To: Matt Dillon Cc: freebsd-current@freebsd.org Subject: Re: RE: Running Linux kernel modules. In-Reply-To: <200101130002.f0D02fk16650@earth.backplane.com> References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> <200101130002.f0D02fk16650@earth.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14943.53910.930029.953797@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > :To handle the multiple open problem, I'm overloading the open and > :close system calls. Upon open, I call the native open, then I grovel > :around in the process' open file table looking for my special file. > :When I find it, I mark fp->f_nextread with a magic number, then store > :a pointer to the per-open private data in fp->f_offset. On close, I > :go grovelling again. I deallocate the private data, clear the magic > :number, and call the system close function. I've also got an > :at_exit() hook that does much the same thing. > > Wait a sec... f_nextread and f_offset can be messed around with > by the user process, what prevents the user process from screwing > up your kernel data pointer? Pure ignorance. Since the device doesn't support reads/writes, I'm hoping nobody will try to lseek on it ;) I could overload the syscalls that touch these fields if I have to, but I'm hoping this will be just an interum hack and don't want to waste time polishing it. > Why not just track the opens independantly in the overloading code? I'm not sure I know what you mean. I don't just need to track multiple open/closes, I need to be able to hang a pointer off of something that I can get at durning an mmap() or ioctl() syscall so that I can tell which instance I'm dealing with. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 20: 9:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5EC6A37B402 for ; Fri, 12 Jan 2001 20:09:20 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0D48W148004; Fri, 12 Jan 2001 20:08:33 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010112190554.E7240@fw.wintelcom.net> Date: Fri, 12 Jan 2001 20:09:20 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: Re: Anybody else seeing a broken /dev/lpt with SMP on -current? Cc: current@FreeBSD.org, Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-01 Alfred Perlstein wrote: > * John Baldwin [010112 18:56] wrote: >> >> On 13-Jan-01 Jordan Hubbard wrote: >> > I've actually been seeing this for about 2 months now but only just >> > now got motivated enough to enable crashdumps and get some information >> > on what happens whenver I try to use the printer attached to my (sadly :) >> > -current SMP box: >> > >> >> All the other traces show the kerenl having returned to an address that is >> beyongd the end of the kernel (which causes the page fault) meaning that the >> stack is fubar'd, so the trace isn't meaningful anyways. :( Knowing how and >> why the lpd interrupt handler trashes the stack is the useful info, and with >> teh stack already trashed, I don't know of an easy way to figure that out. >> Suggestions welcome. > > printf(9) > >:) Maybe if I had a printer lying around. :) I can send jkh some patches to dump out stuff, but I was looking more for suggestions on making sense of the crashdump, not just brute-forcing it. :-P > -Alfred -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 20:18: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 1E71937B698 for ; Fri, 12 Jan 2001 20:17:52 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0D4HKO21209; Fri, 12 Jan 2001 20:17:20 -0800 (PST) (envelope-from dillon) Date: Fri, 12 Jan 2001 20:17:20 -0800 (PST) From: Matt Dillon Message-Id: <200101130417.f0D4HKO21209@earth.backplane.com> To: Andrew Gallatin Cc: freebsd-current@freebsd.org Subject: Re: RE: Running Linux kernel modules. References: <01C07BF3.695D3780.ggross@symark.com> <14942.32188.899333.434988@grasshopper.cs.duke.edu> <200101130002.f0D02fk16650@earth.backplane.com> <14943.53910.930029.953797@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : > Why not just track the opens independantly in the overloading code? : :I'm not sure I know what you mean. I don't just need to track :multiple open/closes, I need to be able to hang a pointer off of :something that I can get at durning an mmap() or ioctl() syscall so :that I can tell which instance I'm dealing with. : :Drew f_data? Or if f_data is a vnode, a field in the vnode ? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 21: 1:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 654BC37B400 for ; Fri, 12 Jan 2001 21:00:54 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f0D50r715357 for ; Sat, 13 Jan 2001 00:00:53 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 13 Jan 2001 00:00:53 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Subject: Building -STABLE on -CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sending this to freebsd-stable or freebsd-current was somewhat of a toss-up, but since I expect more committers hang out on -current than -stable, here it is. For the last few days (not sure when it started) I've been unable to build -STABLE on a -CURRENT machine. This has proven a problem for recent RELENG_3 MFC's of security fixes; I've tried upgrading to the most recent -CURRENT on the box, making sure /usr/include is updated, et al. I'm guessing this is /usr/include pollution in the /usr/src build, but won't speculate too much more as I'm travelling tomorrow. Attached below is the breakage from buildworld. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services cd /usr/src/share/syscons/scrnmaps; make build-tools cc -static -O -pipe -I/usr/src/share/syscons/scrnmaps -DFIL=\"koi8-r2cp866\" -o koi8-r2cp866.mk /usr/src/share/syscons/scrnmaps/mkscrfil.c In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:28: /usr/include/machine/console.h:3: #error "this file includes which is deprecated, use instead" In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:31: /usr/src/share/syscons/scrnmaps/koi8-r2cp866:27: syntax error before `scrmap' /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements in scalar initializer /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: (near initialization for `scrmap') /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements in scalar initializer /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: (near initialization for `scrmap') /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements in scalar initializer /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: (near initialization for `scrmap') /usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements in scalar initializer ... /usr/src/share/syscons/scrnmaps/mkscrfil.c: In function `main': /usr/src/share/syscons/scrnmaps/mkscrfil.c:42: `scrmap_t' undeclared (first use in this function) /usr/src/share/syscons/scrnmaps/mkscrfil.c:42: (Each undeclared identifier is reported only once /usr/src/share/syscons/scrnmaps/mkscrfil.c:42: for each function it appears in.) *** Error code 1 Stop in /usr/src/share/syscons/scrnmaps. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 21:12: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta01.mail.mel.aone.net.au (mta01.mail.au.uu.net [203.2.192.81]) by hub.freebsd.org (Postfix) with ESMTP id F171B37B404; Fri, 12 Jan 2001 21:11:42 -0800 (PST) Received: from camtech.net.au ([203.55.242.195]) by mta01.mail.mel.aone.net.au with ESMTP id <20010113051139.PEUZ26418.mta01.mail.mel.aone.net.au@camtech.net.au>; Sat, 13 Jan 2001 16:11:39 +1100 Message-ID: <3A5FE415.514893C7@camtech.net.au> Date: Sat, 13 Jan 2001 15:43:57 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Cc: ports@FreeBSD.org, jwz@jwz.org, jseger@FreeBSD.org Subject: Data corruption whilst debugging sonar module of ports/graphics/xscreensaver-gtk-3.26 ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Both of my main FreeBSD-CURRENT machines cant seem to run the sonar module from xscreensaver-gtk-3.26 for very long. It crashes with a SIGBUS on line 1654 of xscreensaver-3.26/hacks/sonar.c when the sonar sweep gets back around to the first bogie that was ever displayed. Since my home box is XFree 3.3.6 and work is XFree 4.0.2, I assume this is a bug with the screensaver itself. Note both machines are recent -CURRENT (within 1 week of today). Today I had some spare time (wife and kids out of my hair) so I installed ports/devel/ddd to have a look at whats going on. To reproduce what I'm doing: - Install ports/devel/ddd - Set "CFLAGS=-g -pipe" in /etc/make.conf - cd /usr/ports/x11/xscreensaver ; sudo make install - Set your CFLAGS back to what they were - cd /usr/ports/x11/xscreensaver/work/xscreensaver-3.26/hacks - ddd & - File->Open Program... and choose "sonar" - Run until it dies with the SIGBUS on line 1654 (subroutine "Sonar") - Display "si", "*si", "*si->visable", all the "*si->visable{->next}*" (e.g. "*si->visable->next", "*si->visable->next->next" etc) and the local variables. I'm seeing the local variable "bp" with a value of 0xd0d0d0d0. I cant see how this happens when "bp" is initialised from si->visable in the for loop at line 1647 and thereafter follows the list (via ->next) where no members have an address of 0xd0d0d0d0. It seems that something in sonar.c is overwriting memory it shouldn't. I haven't done much debugging since Uni, so I was wonderring if others can reproduce this and does someone have some ideas how I can easily detect this data corruption with ddd or is it a compiler bug ? (I suspect not as it always happens when the sweep gets back around to the first bogie ever displayed). Does anyone recognise where 0xd0d0d0d0 may have come from ? 1635 static void 1636 Sonar(sonar_info *si, Bogie *bl) 1637 { 1638 1639 /* Local Variables */ 1640 1641 Bogie *bp, *prev; 1642 int i; 1643 1644 /* Check for expired tagets and remove them from the visable list */ 1645 1646 prev = NULL; 1647 for (bp = si->visable; bp != NULL; bp = bp->next) { 1648 1649 /* 1650 * Remove it from the visable list if it's expired or we have 1651 * a new target with the same name. 1652 */ 1653 1654 bp->age ++; 1655 Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 21:18:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by hub.freebsd.org (Postfix) with ESMTP id 9E8D737B400 for ; Fri, 12 Jan 2001 21:18:32 -0800 (PST) Received: from camtech.net.au ([203.55.242.195]) by mta05.mail.mel.aone.net.au with ESMTP id <20010113051824.EWUP19572.mta05.mail.mel.aone.net.au@camtech.net.au>; Sat, 13 Jan 2001 16:18:24 +1100 Message-ID: <3A5FE58E.D72D9126@camtech.net.au> Date: Sat, 13 Jan 2001 15:50:15 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <2936.979314765@axl.fw.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Sat, 13 Jan 2001 01:46:46 +1030, Matthew Thyer wrote: > > > > The way it is now is the way it's always been. Think about what you > > > mean when you say "dynamic swap user". You want mfs to use more swap > > > than you have? :-) > > > > No I want mfs to grow and shrink its filesystem dynamically. > > Then don't limit the size! :-) I dont. So what next ? Since I dont have much time for debugging FreeBSD, I stopped using mfs instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 21:36:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 254FC37B400 for ; Fri, 12 Jan 2001 21:36:12 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id f0D5ZgF05410 for freebsd-current@freebsd.org; Fri, 12 Jan 2001 21:35:42 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200101130535.f0D5ZgF05410@troutmask.apl.washington.edu> Subject: sysinstall.8 bike shed To: FreeBSD Current Date: Fri, 12 Jan 2001 21:35:42 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've already filed a PR about this. And, yes I know people have discussed this the last day or two, but until the color is chosen can someone please remove the the installation of sysinstall.8 from src/share/man/man8/Makefile. -- Steve ===> share/man/man8 gzip -cn /usr/src/share/man/man8/adding_user.8 > adding_user.8.gz gzip -cn /usr/src/share/man/man8/crash.8 > crash.8.gz gzip -cn /usr/src/share/man/man8/diskless.8 > diskless.8.gz gzip -cn /usr/src/share/man/man8/intro.8 > intro.8.gz gzip -cn /usr/src/share/man/man8/picobsd.8 > picobsd.8.gz gzip -cn /usr/src/share/man/man8/rc.8 > rc.8.gz gzip -cn /usr/src/share/man/man8/sticky.8 > sticky.8.gz make: don't know how to make sysinstall.8. Stop *** Error code 2 Stop in /usr/src/share/man. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 21:53:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 9531837B401 for ; Fri, 12 Jan 2001 21:53:08 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14HJcH-000845-00; Sat, 13 Jan 2001 05:52:41 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0D5qaJ04828; Sat, 13 Jan 2001 05:52:36 GMT (envelope-from ben) Date: Sat, 13 Jan 2001 05:52:36 +0000 From: Ben Smithurst To: Steve Kargl Cc: FreeBSD Current Subject: Re: sysinstall.8 bike shed Message-ID: <20010113055236.D35575@strontium.scientia.demon.co.uk> References: <200101130535.f0D5ZgF05410@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101130535.f0D5ZgF05410@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > I've already filed a PR about this. And, yes > I know people have discussed this the last day or > two, but until the color is chosen can someone > please remove the the installation of sysinstall.8 > from src/share/man/man8/Makefile. ugh, sorry. I forgot to fix that. :-( ... Fixed now, I hope. If this fixes it for you I'll MFC it. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 12 23:16: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by hub.freebsd.org (Postfix) with ESMTP id F275F37B400 for ; Fri, 12 Jan 2001 23:15:46 -0800 (PST) Received: from camtech.net.au ([203.55.245.112]) by mta04.mail.mel.aone.net.au with ESMTP id <20010113071537.DAMG19873.mta04.mail.mel.aone.net.au@camtech.net.au>; Sat, 13 Jan 2001 18:15:37 +1100 Message-ID: <3A600121.97AFD6EC@camtech.net.au> Date: Sat, 13 Jan 2001 17:47:53 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Heffner Cc: current@FreeBSD.org Subject: Re: Data corruption whilst debugging sonar module of ports/graph References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Heffner wrote: > > On 13-Jan-2001 Matthew Thyer wrote: > > | Does anyone recognise where 0xd0d0d0d0 may have come from ? > | > > [snip] > > Read the "Tuning" section of malloc(3). 0xd0 is what allocated and deallocated > memory is set to. xscreensaver is probably not initializing malloc()'d memory, > and therefore it's left at 0xd0. A work around is to turn off this feature: > > ln -s aj /etc/malloc.conf > > however, xscreensaver should be fixed instead. Yes, that's what I'm trying to achieve. I thought it was "0xdeadcode" that got put in the malloc'd memory but if that's changed then thanks for the lead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 5:53:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id B1E0D37B401; Sat, 13 Jan 2001 05:52:53 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 127F831B7; Sat, 13 Jan 2001 13:53:00 +0000 (GMT) Date: Sat, 13 Jan 2001 13:53:00 +0000 From: Josef Karthauser To: Julian Elischer Cc: Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP! New netgraph code coming Message-ID: <20010113135300.B987@tao.org.uk> Mail-Followup-To: Josef Karthauser , Julian Elischer , Jun Kuriyama , net@FreeBSD.ORG, current@FreeBSD.ORG References: <3A5567A7.A11F47E3@elischer.org> <3A566BCB.BFD6FA2D@elischer.org> <7m1yu9mdlt.wl@waterblue.imgsrc.co.jp> <3A5F1788.9AD8509A@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5F1788.9AD8509A@elischer.org>; from julian@elischer.org on Fri, Jan 12, 2001 at 06:41:12AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 06:41:12AM -0800, Julian Elischer wrote: > Jun Kuriyama wrote: > > > > Hi Julian, > > > > I tried netgraph for the first time to work with latest vmware2 port. > > > > When I try to load netgraph kernel module, it failed with: > > > > # kldload ng_bridge > > kldload: can't load ng_bridge: Exec format error > > something is terribly broken with the kld loading at the moment. > netgraph actually tries to load modules it needs but it hasn't been > able to for some months. Also kldload ca SEE what the dependency is > so the module is telling it correctly, just the kernel is failing > to load the dependency.. I don't think this is Netgraph's fault. > we haven;t changed anything.. it just stopped working one day. It was broken for me last week - but upon testing yesterday it appeared to work again: genius# uname -a FreeBSD genius.tao.org.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #12: Thu Jan 11 15:32:11 GMT 2001 joe@genius.tao.org.uk:/usr/obj/usr/src/sys/GENIUS i386 genius# kldload /boot/kernel/ng_bridge.ko genius# kldstat Id Refs Address Size Name 1 13 0xc0100000 2c90f0 kernel 2 1 0xc144c000 7000 linprocfs.ko 3 3 0xc1454000 12000 linux.ko 4 1 0xc14b9000 3000 daemon_saver.ko 5 1 0xc0a7c000 2000 rtc.ko 6 1 0xc0a86000 9000 vmmon_up.ko 7 1 0xc0a92000 4000 if_tap.ko 8 1 0xc1adb000 5000 ng_bridge.ko 9 1 0xc1ae1000 4000 ng_ether.ko Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 6:17:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 828B237B400 for ; Sat, 13 Jan 2001 06:17:37 -0800 (PST) Received: (qmail 20942 invoked by uid 0); 13 Jan 2001 14:17:35 -0000 Received: from p3ee20a80.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.128) by mail.gmx.net (mp003-rz3) with SMTP; 13 Jan 2001 14:17:35 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id PAA04849 for freebsd-current@freebsd.org; Sat, 13 Jan 2001 15:10:56 +0100 Date: Sat, 13 Jan 2001 15:10:56 +0100 From: Gerhard Sittig To: "'freebsd-current@freebsd.org'" Subject: Re: Crash dumps during initialisation Message-ID: <20010113151056.P253@speedy.gsinet> Mail-Followup-To: "'freebsd-current@freebsd.org'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from NewtonHa@logica.com on Fri, Jan 12, 2001 at 10:17:47AM -0000 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 10:17 -0000, Newton, Harry wrote: > > How can I get the kernel to make crash dumps if it fails before > the 'dumpon' command is issued ? See my freebsd-stable message from back in December with Msg-Id <20001222155115.Z253@speedy.gsinet> where I propose to extend the DDB_UNATTENDED comment. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 6:18:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 6A9A137B401 for ; Sat, 13 Jan 2001 06:18:25 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14HRVc-0003zZ-00; Sat, 13 Jan 2001 16:18:20 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA15644; Sat, 13 Jan 2001 16:18:17 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 15526; Sat Jan 13 16:17:23 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14HRUh-0003Ds-00; Sat, 13 Jan 2001 16:17:23 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-reply-to: Your message of "Sat, 13 Jan 2001 15:50:15 +1030." <3A5FE58E.D72D9126@camtech.net.au> Date: Sat, 13 Jan 2001 16:17:23 +0200 Message-ID: <12391.979395443@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Jan 2001 15:50:15 +1030, Matthew Thyer wrote: > > Then don't limit the size! :-) > > I dont. So what next ? > > Since I dont have much time for debugging FreeBSD, I stopped using > mfs instead. This is a very simple problem -- you're running out of space. If you can't do anything about the amount of space used in /tmp, then either swap fills up or you limit the size of mfs. If you don't like either of those, use a separate partition for /tmp. But then you may as well use that partition as extra swap space and continue to mount /tmp in mfs. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 14:25: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id EDF9D37B402 for ; Sat, 13 Jan 2001 14:24:43 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0DMNk159924; Sat, 13 Jan 2001 14:23:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A600121.97AFD6EC@camtech.net.au> Date: Sat, 13 Jan 2001 14:24:46 -0800 (PST) From: John Baldwin To: Matthew Thyer Subject: Re: Data corruption whilst debugging sonar module of ports/graph Cc: current@FreeBSD.org, Mike Heffner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-01 Matthew Thyer wrote: > Mike Heffner wrote: >> >> On 13-Jan-2001 Matthew Thyer wrote: >> >> | Does anyone recognise where 0xd0d0d0d0 may have come from ? >> | >> >> [snip] >> >> Read the "Tuning" section of malloc(3). 0xd0 is what allocated and >> deallocated >> memory is set to. xscreensaver is probably not initializing malloc()'d >> memory, >> and therefore it's left at 0xd0. A work around is to turn off this feature: >> >> ln -s aj /etc/malloc.conf >> >> however, xscreensaver should be fixed instead. > > Yes, that's what I'm trying to achieve. I thought it was "0xdeadcode" > that got put in the malloc'd memory but if that's changed then thanks > for the lead. 0xdeadc0de is used by kernel malloc, and 0xd0d0d0d0 by the userland malloc, AFAIK. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 15:20: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.iadfw.net (mail2.iadfw.net [206.66.12.234]) by hub.freebsd.org (Postfix) with SMTP id 76CC337B400; Sat, 13 Jan 2001 15:19:45 -0800 (PST) Received: from Jason from [64.31.207.237] by mail2.iadfw.net (/\##/\ Smail3.1.30.16 #30.47) with smtp for sender: id ; Sat, 13 Jan 2001 17:19:48 -0600 (CST) Message-ID: <008001c07db8$0775f7c0$edcf1f40@pdq.net> From: "Jason Smethers" To: "Kris Kennaway" Cc: References: <000f01c07cbb$379df040$edcf1f40@pdq.net> <20010112175221.E23818@citusc.usc.edu> Subject: Re: module privlages Date: Sat, 13 Jan 2001 17:24:50 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Kris Kennaway" >I'm not sure what the point of this would really be..nor how you could >enforce it. Perhaps you should submit a proof of concept ;-) > >Kris With more thought I suppose this would be a lot more effort than I had first thought, and a different out come for speed/correctness. One way to do this would be to have all kernel code pages be invalid so they always page fault. The page fault handler then could use reserved page table bits to mark read/write/exec the page to insure that no unaurthorized code reads a page containing kernel code. I'm sure that everyone would love to have every memory access to a page containing kernel code page fault... Otherwise, on IA32 this won't work as function calls without additional hardware support. The closet you could probably get is preventing everything except for the module reading through kernel memory looking for a signature of what it wants to call and jumping to it at a point past permission and safety checks. There would have to be a bit of safety checking added to interfacing code such as device types and ownerships in the bus subsystem, and memory range validity and ownerships in the VM subsystem. The correctest way of any acceptable speed would require a module/system call gate. At that point just add in a separate VM space and you're basically working on userland kernel support. If only hardware had separate Read/Write/Execute page bits... Never mind. =) - Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 17:13:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id BD1BE37B400; Sat, 13 Jan 2001 17:13:30 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA407260; Sat, 13 Jan 2001 20:13:28 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sat, 13 Jan 2001 20:13:27 -0500 To: John Baldwin , Jordan Hubbard From: Garance A Drosihn Subject: RE: Anybody else seeing a broken /dev/lpt with SMP on -current? Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:55 PM -0800 1/12/01, John Baldwin wrote: >On 13-Jan-01 Jordan Hubbard wrote: > > If anybody wants a fuller traceback then I'll compile up a kernel > > with debugging symbols, but it's going to be pretty sparse anyway > > since it basically only shows the trap() from the page fault and > > the subsequent panic. > >All the other traces show the kernel having returned to an address >that is beyond the end of the kernel (which causes the page fault) >meaning that the stack is fubar'd, so the trace isn't meaningful >anyways. :( Knowing how and why the lpd interrupt handler trashes >the stack is the useful info, and with the stack already trashed, >I don't know of an easy way to figure that out. Do you really mean the "lpd interrupt handler", or do you mean the "lpt interrupt handler"? Does this problem only happen when lpd is sending data thru /dev/lpt? -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 18:47:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id A0DBD37B401 for ; Sat, 13 Jan 2001 18:47:01 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0E2l1Z76682 for current@freebsd.org; Sat, 13 Jan 2001 18:47:01 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Jan 2001 18:47:00 -0800 From: "David O'Brien" To: current@freebsd.org Subject: ** HEADS UP ** bug in pkg_update Message-ID: <20010113184700.G53530@dragon.nuxi.com> Reply-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Until Paul Richards fixes the bug, do NOT run `pkg_update' on a package w/o a version number in the name. Ie, ``pkg_update gtk.tgz'' will delete every package off your system. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 19:34: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3EF3437B400; Sat, 13 Jan 2001 19:33:45 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA01381; Sat, 13 Jan 2001 19:33:45 -0800 Date: Sat, 13 Jan 2001 19:33:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** bug in pkg_update In-Reply-To: <20010113184700.G53530@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool! On Sat, 13 Jan 2001, David O'Brien wrote: > Until Paul Richards fixes the bug, do NOT run `pkg_update' on a package > w/o a version number in the name. Ie, ``pkg_update gtk.tgz'' will delete > every package off your system. > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 19:34: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3EF3437B400; Sat, 13 Jan 2001 19:33:45 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA01381; Sat, 13 Jan 2001 19:33:45 -0800 Date: Sat, 13 Jan 2001 19:33:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** bug in pkg_update In-Reply-To: <20010113184700.G53530@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool! On Sat, 13 Jan 2001, David O'Brien wrote: > Until Paul Richards fixes the bug, do NOT run `pkg_update' on a package > w/o a version number in the name. Ie, ``pkg_update gtk.tgz'' will delete > every package off your system. > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 20: 2: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5A52537B401 for ; Sat, 13 Jan 2001 20:01:51 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id XAA80787; Sat, 13 Jan 2001 23:01:41 -0500 (EST) (envelope-from wollman) Date: Sat, 13 Jan 2001 23:01:41 -0500 (EST) From: Garrett Wollman Message-Id: <200101140401.XAA80787@khavrinen.lcs.mit.edu> To: Matthew Thyer Cc: Sheldon Hearn , Edwin Culp , current@FreeBSD.ORG Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed In-Reply-To: <3A5F1FDE.AAF40577@camtech.net.au> References: <672.979299461@axl.fw.uunet.co.za> <3A5F1FDE.AAF40577@camtech.net.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > No I want mfs to grow and shrink its filesystem dynamically. MFS has never done so. MFS is simply a UFS which uses (swap-backed) memory instead of a physical disk; it relies on the filesystem to avoid touching blocks that it doesn't need, and on the VM system to avoid wasting memory on allocated-but-untouched address space. Historically, MFS would waste time copying disk blocks twice on their way to the user, but I think this may have been fixed by Matt Dillon. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 20:51:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 5BDAD37B6ED for ; Sat, 13 Jan 2001 20:51:05 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0E4QHw00656 for ; Sun, 14 Jan 2001 00:26:17 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 14 Jan 2001 00:26:17 -0400 (AST) From: The Hermit Hacker To: Subject: playing through pcm generates high-pitched sound ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying to get my sound to once more work, I added the pcm device to my kernel, but if I try to play a "known to work" mp3 through it, it generates a high-pitched "whistle" ... Looking at dmesg, I have a bunch of irq's that appears to be overlapping, and am wondering if that might be the cause? IOAPIC #0 intpin 2 -> irq 0 ata0: at 0x1f0 irq 14 on atapci0 ahc0: port 0xc400-0xc4ff mem 0xef101000-0xef101fff irq 19 at device 9.0 on pci0 ahc1: port 0xcc00-0xccff mem 0xef100000-0xef100fff irq 17 at device 13.0 on pci0 pcm0: port 0xd000-0xd03f irq 19 at device 17.0 on pci0 atapci1: port 0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 18 at device 19.0 on pci0 atapci2: port 0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 18 at device 19.1 on pci0 atkbd0: flags 0x1 irq 1 on atkbdc0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio1 at port 0x2f8-0x2ff irq 3 on isa0 fxp0: port 0xc800-0xc83f mem 0xef000000-0xef0fffff,0xef102000-0xef102fff irq 18 at device 11.0 on pci0 namely: pcm0 == ahc0 atapci1 == atapci2 == fxp0 could this be the cause? or should I be looking at somethign else? thanks ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 20:51:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from flute.daconcepts.dyndns.org (wks-29-177-219.kscable.com [24.29.177.219]) by hub.freebsd.org (Postfix) with ESMTP id 6AD5E37B792 for ; Sat, 13 Jan 2001 20:51:39 -0800 (PST) Received: from localhost (natedac@localhost) by flute.daconcepts.dyndns.org (8.11.1/8.11.1) with ESMTP id f0E4q4B22538; Sat, 13 Jan 2001 22:52:09 -0600 (CST) (envelope-from natedac@kscable.com) X-Authentication-Warning: flute.daconcepts.dyndns.org: natedac owned process doing -bs Date: Sat, 13 Jan 2001 22:52:02 -0600 (CST) From: Nate Dannenberg X-X-Sender: To: , Subject: ESS Audiodrive/5.0-Current/mpg123 - problem solved Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was having problems with the ESS Audiodrive under 5.0-Current, when used with mpg123 - the system refused to play any music in stereo. It turns out the problem is the way the pre-compiled Package of mpg123 v0.59r cooperates with 4.2-R and 5.0-C. Compiling mpg123 from sources, with EsounD support, seems to have fixed the problem - it now works in stereo just like before. The packaged version doesn't have it built in, and compiling my own without EsounD acts similar to the packaged version - no stereo sound on ESS Audiodrive 18xx series. Has anyone else noticed this reaction? Over the last few days I've been fetching and compiling many applications and libraries (including EsounD) from source code, to replace all the packages I had relied on previously, and to gain a little extra speed (mpg123 didn't improve any though :-) and hopefully save me a few megs of HD space and memory. (a copy of this message is being sent to Michael Hipp as well). -- ___________________________________ _____ _____ | _///@@@| | | natedac@kscable.com /'//ZZ@@|____ | | |'''/ |'/@7 | | http://home.kscable.com/natedac |`'| `~~' | | | `| .--. | | C64/C128 - What's *YOUR* hobby? | `\____|___\ | | \_ | | |___________________________________ \_____| _____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 22: 9:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta01.mail.mel.aone.net.au (mta01.mail.au.uu.net [203.2.192.81]) by hub.freebsd.org (Postfix) with ESMTP id 34CE837B400 for ; Sat, 13 Jan 2001 22:09:14 -0800 (PST) Received: from camtech.net.au ([203.55.243.183]) by mta01.mail.mel.aone.net.au with ESMTP id <20010114060906.YCZA26418.mta01.mail.mel.aone.net.au@camtech.net.au>; Sun, 14 Jan 2001 17:09:06 +1100 Message-ID: <3A614312.DAAEA5E0@camtech.net.au> Date: Sun, 14 Jan 2001 16:41:30 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Edwin Culp , current@freebsd.org Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <12391.979395443@axl.fw.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Sat, 13 Jan 2001 15:50:15 +1030, Matthew Thyer wrote: > > > > Then don't limit the size! :-) > > > > I dont. So what next ? > > > > Since I dont have much time for debugging FreeBSD, I stopped using > > mfs instead. > > This is a very simple problem -- you're running out of space. If you > can't do anything about the amount of space used in /tmp, then either > swap fills up or you limit the size of mfs. > > If you don't like either of those, use a separate partition for /tmp. > But then you may as well use that partition as extra swap space and > continue to mount /tmp in mfs. :-) Sheldon, I'm not stupid. At the time the message occurred I had less than 6 MB usage in /tmp if that. I have 128MB of RAM and 500MB swap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 22:30:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id DA5F837B402 for ; Sat, 13 Jan 2001 22:30:11 -0800 (PST) Received: from cain.gsoft.com.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id RAA99262 for ; Sun, 14 Jan 2001 17:00:09 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 14 Jan 2001 17:00:08 +1030 (CST) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Subject: Sound gets the occassional 'beep' coming through Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I play music (or at least mp3's) I get a beep at random intervals. It lasts for <1/10th of a second and is sometimes in the left or right. It seems to be that the the beep is caused by a block of audio being played very fast because the beep occurs and the audio pauses for a fraction of a second. I'm getting quite a few 'hwptr went backwards' messages too (kernel building going on). I have a -> FreeBSD Audio Driver (newpcm) Jan 13 2001 17:44:45 Installed devices: pcm0: at io 0xe800 irq 9 (4p/1r channels duplex) Recording is hosed as well.. It just plays back as a low pitched buzz.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 13 22:37:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 5A4D437B401 for ; Sat, 13 Jan 2001 22:37:26 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0E6ajX43032; Sat, 13 Jan 2001 22:36:45 -0800 (PST) (envelope-from dillon) Date: Sat, 13 Jan 2001 22:36:45 -0800 (PST) From: Matt Dillon Message-Id: <200101140636.f0E6ajX43032@earth.backplane.com> To: Garrett Wollman Cc: Matthew Thyer , Sheldon Hearn , Edwin Culp , current@FreeBSD.ORG Subject: Re: /boot/kernel/kernel: swap_pager_getswapspace: failed References: <672.979299461@axl.fw.uunet.co.za> <3A5F1FDE.AAF40577@camtech.net.au> <200101140401.XAA80787@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> No I want mfs to grow and shrink its filesystem dynamically. : :MFS has never done so. MFS is simply a UFS which uses (swap-backed) :memory instead of a physical disk; it relies on the filesystem to :avoid touching blocks that it doesn't need, and on the VM system to :avoid wasting memory on allocated-but-untouched address space. :Historically, MFS would waste time copying disk blocks twice on their :way to the user, but I think this may have been fixed by Matt Dillon. : :-GAWollman Both MFS and VN have the ability to dynamically allocate and free their swap backing store. However, due to limitations in the way filesystems 'free' blocks, only 'full block frees' can be returned to the system. Since files often contain fragments, neither MFS or VN can fully free the backing store related to a file. At a minimum the inode and bitmap blocks will always remain persistent, and filesystem blocks used to store file fragments will tend to remain persistent even when the underlying files have been deleted. -- MFS is very inefficient. I didn't fix that... it isn't possible to fix it without a lot of work. Data must still be copied twice. Even worse, data is cached twice in the system rather then once, so the active data set is bloated over what it could be. VN and MD do not have this problem. Poul is working on integrating the feature of VN, MFS, and MD all into MD. The VN device is probably one's best bet on sharing swap efficiently with a temp filesystem. That said, I do *NOT* recommend any sort of temp/swap sharing, because it makes for a very fragile system. If anything fills up swap, your temp filesystem is screwed. If anything fills up your temp filesystem, your swap is screwed. Bad news all around. Today's hard drives are large enough that you should keep them separate. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message