From owner-freebsd-current Sun Dec 3 0:44: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 39C6537B400 for ; Sun, 3 Dec 2000 00:44:02 -0800 (PST) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id eB38i0l28937; Sun, 3 Dec 2000 09:44:00 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.1/8.11.1) with ESMTP id eB38i0e6576146; Sun, 3 Dec 2000 09:44:00 +0100 (MET) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.1/8.11.1/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id eB38hxq15273; Sun, 3 Dec 2000 09:43:59 +0100 (CET) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.1/8.11.1/alaska [ $Revision: 1.4 ]) id eB38hxa14419; Sun, 3 Dec 2000 09:43:59 +0100 (CET) (envelope-from ust) Date: Sun, 3 Dec 2000 09:43:59 +0100 From: Udo Schweigert To: Nick Cc: freebsd-current@FreeBSD.ORG Subject: Re: ACPI and Sony laptop Message-ID: <20001203094359.A14364@alaska.cert.siemens.de> Mail-Followup-To: Nick , freebsd-current@FreeBSD.ORG References: <3A2975B8.6D757E65@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A2975B8.6D757E65@quack.kfu.com>; from nsayer@quack.kfu.com on Sat, Dec 02, 2000 at 02:20:40PM -0800 X-Operating-System: FreeBSD 4.2-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 02, 2000 at 14:20:40 -0800, Nick wrote: > I took the plunge. My Z505JE now runs -current. > > A couple of things I have observed: rebooting with other than > ctrl-alt-del doesn't result in rc.shutdown being run, which means I have > to whomp on the keyboard at the next reboot. Am I doing something wrong > that 'shutdown' and 'reboot' don't run rc.shutdown? > That seems to be intended. I also observed this behaviour some time ago because with -current the entropy file is written by the rc.shutdown script and if this is not done at shutdown the next boot will take more time. Now I use "init 0" for shutdown and "init 6" for reboot. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 3 4:38:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 963BE37B404 for ; Sun, 3 Dec 2000 04:21:03 -0800 (PST) Received: from earth.causticlabs.com (oca-c1s1-07.mfi.net [209.26.94.8]) by peitho.fxp.org (Postfix) with ESMTP id 4223913611 for ; Sun, 3 Dec 2000 07:21:07 -0500 (EST) Received: by earth.causticlabs.com (Postfix, from userid 1000) id 08B881F23; Sun, 3 Dec 2000 07:21:30 -0500 (EST) Date: Sun, 3 Dec 2000 07:21:30 -0500 From: Chris Faulhaber To: freebsd-current@FreeBSD.org Subject: unexpected vn driver lock Message-ID: <20001203072130.A86631@earth.causticlabs.com> Mail-Followup-To: Chris Faulhaber , freebsd-current@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 I ran a 'make release' last night on -current (NODOC and NOPORTS set). This morning, I find the following: unexpected vn driver lock: 0xc6312500: type VREG, usecount 2, writecount 1, refcount 270, flags (VOBJBUF) tag VT_UFS, ino 492145, on dev #ad/0x40004 (116, 262148) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc6312500: type VREG, usecount 2, writecount 1, refcount 253, flags (VOBJBUF) tag VT_UFS, ino 492145, on dev #ad/0x40004 (116, 262148) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc65ed500: type VREG, usecount 2, writecount 1, refcount 212, flags (VOBJBUF) tag VT_UFS, ino 492149, on dev #ad/0x40004 (116, 262148) lock type inode: EXCL (count 1) by pid 4 The release seemed to have completed successfully, though. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Sun Dec 3 6:17: 8 2000 From owner-freebsd-current@FreeBSD.ORG Sun Dec 3 06:17:06 2000 Return-Path: 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 3D61737B400 for ; Sun, 3 Dec 2000 06:17:03 -0800 (PST) Received: from grondar.za (gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id eB3EFJe33617; Sun, 3 Dec 2000 16:15:20 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200012031415.eB3EFJe33617@gratis.grondar.za> To: Udo Schweigert Cc: Nick , freebsd-current@FreeBSD.ORG Subject: Re: ACPI and Sony laptop References: <20001203094359.A14364@alaska.cert.siemens.de> In-Reply-To: <20001203094359.A14364@alaska.cert.siemens.de> ; from Udo Schweigert "Sun, 03 Dec 2000 09:43:59 +0100." Date: Sun, 03 Dec 2000 16:15:14 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That seems to be intended. I also observed this behaviour some > time ago because with -current the entropy file is written by the > rc.shutdown script and if this is not done at shutdown the next boot > will take more time. Definitely not "intended". It is intended that a seedfile get written at shutdown. Are you fully up to date with your mergemaster(1)ing? > Now I use "init 0" for shutdown and "init 6" for reboot. That is a bug if you are up to date. However, it is beyond my ken to fix. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 5:59:37 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 05:59:36 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from bofh.genesiseurope.net (tmp-gw.cork.mbits.net [194.125.130.115]) by hub.freebsd.org (Postfix) with SMTP id 2070A37B400 for ; Mon, 4 Dec 2000 05:59:23 -0800 (PST) Received: (qmail 14078 invoked by uid 1001); 4 Dec 2000 14:05:23 -0000 Date: Mon, 4 Dec 2000 14:05:23 +0000 From: Sascha Luck To: current@freebsd.org Subject: Re: Lucent Orinoco Gold PCCard? Message-ID: <20001204140523.A12859@genesiseurope.net> References: <200012010142.SAA33362@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200012010142.SAA33362@harmony.village.org>; from imp@village.org on Thu, Nov 30, 2000 at 06:42:24PM -0700 Sender: sascha@bofh.genesiseurope.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spoke Warner Losh: > In message John Baldwin writes: > : I'm sending this e-mail over a WaveLAN Gold, and from my > : understanding the Orinoco card is the same card with a different > : name and a different sticker, so it should work fine. > > I'm doing the same thing. It is the same card with a different > label. The newer firmware, however, sets the default channel > differently than the older cards. Doesn't matter for infrastructure > mode, but does for adhoc. > Thanks to all who replied. I wasn't sure it was still the same as the WaveLAN product. Cheers, Sascha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 6:17: 5 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 06:17:01 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id E40A737B400; Mon, 4 Dec 2000 06:16:56 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id QAA06410; Mon, 4 Dec 2000 16:16:51 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 6387; Mon Dec 4 16:16:26 2000 Sender: gram@citadel.cequrux.com Message-ID: <3A2B8ED4.CEA4D76@cequrux.com> Date: Mon, 04 Dec 2000 14:32:20 +0200 From: Graham Wheeler Reply-To: gramster@bigfoot.com Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Cc: freebsd-current@freebsd.org Subject: ATI Rage Mobility and VESA driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again With regard to my earlier message, I mentioned: > My laptop has an ATI Rage Mobility AGP card in it. According to ATI rech > support, this card is VESA-compliant - but FreeBSD doesn't recognise it > as such. > I searched the mailing list archives, and found >> /usr/src/sys/i386/isa/vesa.c, line 680: >> if ((vmode.v_modeattr & (V_MODEOPTINFO | V_MODENONVGA)) >> != (V_MODEOPTINFO)) >> continue; >> >> The v_modeattr returned by ATI VESA bios has V_MODENONVGA bit set, >> so all the vesa modes are ommited... >so I hacked this code to ignore the V_MODENONVGA flag. This was only >partially successful: I now get some VESA stuff being printed upon boot, >but still can't use any of the VESA modes. I noticed that vesa.c 1.34 has this change in it (4.2-stable is still using vesa.c 1.32). This does buy me some progress, in that I get some better dmesg output: VESA: v2.0, 8128k memory, flags:0x0, mode_table:0xc02b6f62 (1000022) VESA: ATI MACH64 However, using vidcontrol and attempting to set any VESA modes still produces "operation not supported by device". I guess the next step is to get all the debug output from vesa.c, and see if it finds any usable VESA modes at all. [I'm cross-posting this to freebsd-current, as it seems to be relevant to the latest vesa.c changes] gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 7:51:33 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 07:51:30 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 3D9D237B402 for ; Mon, 4 Dec 2000 07:51:30 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 142xwe-00007a-00; Mon, 04 Dec 2000 08:54:24 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A2BBE2F.FF5CA11@softweyr.com> Date: Mon, 04 Dec 2000 08:54:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sascha Luck Cc: current@freebsd.org Subject: Re: Lucent Orinoco Gold PCCard? References: <200012010142.SAA33362@harmony.village.org> <20001204140523.A12859@genesiseurope.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sascha Luck wrote: > > Thus spoke Warner Losh: > > In message John Baldwin writes: > > : I'm sending this e-mail over a WaveLAN Gold, and from my > > : understanding the Orinoco card is the same card with a different > > : name and a different sticker, so it should work fine. > > > > I'm doing the same thing. It is the same card with a different > > label. The newer firmware, however, sets the default channel > > differently than the older cards. Doesn't matter for infrastructure > > mode, but does for adhoc. > > > Thanks to all who replied. I wasn't sure it was still the same as > the WaveLAN product. Dell is selling a Lucent-OEMed card for $139. I don't know if it is a Silver or Gold, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 10:36:49 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 10:36:48 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5EF4037B400 for ; Mon, 4 Dec 2000 10:36:43 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eB4IabQ92711; Mon, 4 Dec 2000 11:36:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA62726; Mon, 4 Dec 2000 11:36:36 -0700 (MST) Message-Id: <200012041836.LAA62726@harmony.village.org> To: Wes Peters Subject: Re: Lucent Orinoco Gold PCCard? Cc: Sascha Luck , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 04 Dec 2000 08:54:23 MST." <3A2BBE2F.FF5CA11@softweyr.com> References: <3A2BBE2F.FF5CA11@softweyr.com> <200012010142.SAA33362@harmony.village.org> <20001204140523.A12859@genesiseurope.net> Date: Mon, 04 Dec 2000 11:36:36 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A2BBE2F.FF5CA11@softweyr.com> Wes Peters writes: : Dell is selling a Lucent-OEMed card for $139. I don't know if it is a : Silver or Gold, though. http://www.comready.com/dlindwwirlan.html is selling what appears to be a lucentOEM'd card for $119. It has 40-bit WEP, so I don't know what metal that makes it (despite having been told the last time this came up). There's no external antenna connector, however. Still not a bad price and with $20 of the price point for taking my whole house wireless. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 11: 1:41 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 11:01:38 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from west.lustig.com (west.lustig.com [209.157.26.130]) by hub.freebsd.org (Postfix) with SMTP id 2432937B402 for ; Mon, 4 Dec 2000 11:01:38 -0800 (PST) Received: (qmail 72672 invoked from network); 4 Dec 2000 19:01:36 -0000 Received: from lustig.ne.mediaone.net (HELO devious.lustig.com) (@24.91.125.166) by west.lustig.com with SMTP; 4 Dec 2000 19:01:36 -0000 Received: (qmail 11883 invoked by uid 1001); 4 Dec 2000 19:01:31 -0000 Message-ID: <20001204190131.11882.qmail@devious.lustig.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach_patches v148.2) In-Reply-To: <200012041836.LAA62726@harmony.village.org> X-Nextstep-Mailer: Mail 4.2mach_patches [i386] (Enhance 2.2p2) Received: by NeXT.Mailer (1.148.2.RR) From: Barry Lustig Date: Mon, 4 Dec 2000 14:01:30 -0500 To: Warner Losh Subject: Re: Lucent Orinoco Gold PCCard? Cc: Wes Peters , Sascha Luck , current@FreeBSD.ORG Reply-To: barry@Lustig.COM References: <3A2BBE2F.FF5CA11@softweyr.com> <200012010142.SAA33362@harmony.village.org> <20001204140523.A12859@genesiseurope.net> <200012041836.LAA62726@harmony.village.org> X-Organizations: Barry Lustig & Associates, Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 04 Dec 2000, Warner Losh wrote: > In message <3A2BBE2F.FF5CA11@softweyr.com> Wes Peters writes: > Dell is selling a Lucent-OEMed card for $139. I don't know if it is a > Silver or Gold, though. > > > is selling what appears to be a lucentOEM'd card for $119. It has > 40-bit WEP, so I don't know what metal that makes it (despite having > been told the last time this came up). There's no external antenna > connector, however. Still not a bad price and with $20 of the price > point for taking my whole house wireless. > 40-bit WEP means silver. barry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 12:38:49 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 12:38:46 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6283337B400 for ; Mon, 4 Dec 2000 12:38:46 -0800 (PST) Received: from laptop.baldwin.cx (root@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB4KcKC13408; Mon, 4 Dec 2000 12:38:20 -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: <200012041836.LAA62726@harmony.village.org> Date: Mon, 04 Dec 2000 12:38:56 -0800 (PST) From: John Baldwin To: Warner Losh Subject: Re: Lucent Orinoco Gold PCCard? Cc: current@FreeBSD.org, Sascha Luck , Wes Peters Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Dec-00 Warner Losh wrote: > In message <3A2BBE2F.FF5CA11@softweyr.com> Wes Peters writes: >: Dell is selling a Lucent-OEMed card for $139. I don't know if it is a >: Silver or Gold, though. > > http://www.comready.com/dlindwwirlan.html > > is selling what appears to be a lucentOEM'd card for $119. It has > 40-bit WEP, so I don't know what metal that makes it (despite having > been told the last time this came up). There's no external antenna > connector, however. Still not a bad price and with $20 of the price > point for taking my whole house wireless. 0 == bronze 40 == silver 128 == gold AFAIK > Warner -- 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 Dec 4 13: 0: 0 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 12:59:56 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id D07D737B401 for ; Mon, 4 Dec 2000 12:59:55 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eB4KxDP07949 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Mon, 4 Dec 2000 21:59:15 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eB4Kvqa83905 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Mon, 4 Dec 2000 21:59:21 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eA5GvkL42412; Sun, 5 Nov 2000 17:57:46 +0100 (CET) (envelope-from ticso) Date: Sun, 5 Nov 2000 17:57:46 +0100 From: Bernd Walter To: David Greenman Cc: janb@cs.utep.edu, freebsd-current@FreeBSD.ORG Subject: Re: current paging strategy Message-ID: <20001105175745.A42346@cicely8.cicely.de> References: <200011020845.AAA13439@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200011020845.AAA13439@implode.root.com>; from dg@root.com on Thu, Nov 02, 2000 at 12:45:30AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 02, 2000 at 12:45:30AM -0800, David Greenman wrote: > >Interesting. THis needs about two bytes per page for the counter? > > Actually, we found that a single byte per page was sufficient. Pages tended > to be either heavily accessed or rarely accessed. Even in the unusual case > where all pages are frequently accessed, the page reclaim rate (and thus > adjustment rate of the page references count) increases high enough to still > provide for a decent distribution of the counters and for the page LOU to be > effective. One byte sounds good for i386. Maybe it makes sense to have it 4 or 8 byte on risc platforms. I wonder if it's a critical path and if there are more of this in the kernel source. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 13:11:17 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 13:11:09 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from net2.gendyn.com (nat2.gendyn.com [204.60.171.12]) by hub.freebsd.org (Postfix) with ESMTP id 42EDA37B400 for ; Mon, 4 Dec 2000 13:11:09 -0800 (PST) Received: from [153.11.11.3] (helo=plunger.gdeb.com) by net2.gendyn.com with esmtp (Exim 2.12 #1) id 1432su-000Au2-00 for current@freebsd.org; Mon, 4 Dec 2000 16:10:52 -0500 Received: from orion.caen.gdeb.com ([153.11.109.11]) by plunger.gdeb.com with ESMTP id QAA19730 for ; Mon, 4 Dec 2000 16:07:00 -0500 (EST) Received: from vigrid.com (gpz.clc.gdeb.com [192.168.3.12]) by orion.caen.gdeb.com (8.9.3/8.9.3) with ESMTP id QAA12644 for ; Mon, 4 Dec 2000 16:07:15 -0500 (EST) (envelope-from eischen@vigrid.com) Sender: eghk@gdeb.com Message-ID: <3A2C088B.B9D23B7@vigrid.com> Date: Mon, 04 Dec 2000 16:11:39 -0500 From: Dan Eischen X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Making {open,close,read,tell,seek}dir thread-safe. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I started a cleanup of libc to make it thread-safe. I would like to get rid of the hash table in libc/gen/telldir.c and maintain telldir position information on a per-DIR basis. A summary of the changes are as follows: o Add a LIST_HEAD to DIR to contain a queue of telldir positions. Also add a location count (used as the magic for telldir) to DIR. A future change may also add a mutex/lock. o Remove the hash table from telldir.c. Recode to use queue macros. o Remove 'const' from 'telldir(const DIR *)'. o Remove 'register' variables as suggested in another recent thread. Question: Is there a reason to use a hash table in each DIR instead of a list (for performance reasons)? Proposed diffs below. -- Dan Eischen Index: dirent.h =================================================================== RCS file: /opt/FreeBSD/cvs/src/include/dirent.h,v retrieving revision 1.7 diff -u -r1.7 dirent.h --- dirent.h 1999/12/29 05:01:20 1.7 +++ dirent.h 2000/12/04 20:03:49 @@ -46,12 +46,15 @@ #ifdef _POSIX_SOURCE typedef void * DIR; #else +#include #define d_ino d_fileno /* backward compatibility */ /* definitions for library routines operating on directories. */ #define DIRBLKSIZ 1024 +struct ddloc; + /* structure describing an open directory. */ typedef struct _dirdesc { int dd_fd; /* file descriptor associated with directory */ @@ -61,7 +64,9 @@ int dd_len; /* size of data buffer */ long dd_seek; /* magic cookie returned by getdirentries */ long dd_rewind; /* magic cookie for rewinding */ - int dd_flags; /* flags for readdir */ + int dd_flags; /* flags for readdir */\ + long dd_loccnt; /* current key for dd_locq entry */ + LIST_HEAD(, ddloc) dd_locq; /* telldir position recording */ } DIR; #define dirfd(dirp) ((dirp)->dd_fd) @@ -89,7 +94,7 @@ int closedir __P((DIR *)); #ifndef _POSIX_SOURCE DIR *__opendir2 __P((const char *, int)); -long telldir __P((const DIR *)); +long telldir __P((DIR *)); void seekdir __P((DIR *, long)); int scandir __P((const char *, struct dirent ***, int (*)(struct dirent *), int (*)(const void *, const void *))); Index: libc/gen/closedir.c =================================================================== RCS file: /opt/FreeBSD/cvs/src/lib/libc/gen/closedir.c,v retrieving revision 1.6 diff -u -r1.6 closedir.c --- libc/gen/closedir.c 2000/01/27 23:06:14 1.6 +++ libc/gen/closedir.c 2000/12/04 20:03:30 @@ -58,7 +58,7 @@ dirp->dd_fd = -1; dirp->dd_loc = 0; free((void *)dirp->dd_buf); - free((void *)dirp); _reclaim_telldir(dirp); + free((void *)dirp); return(_close(fd)); } Index: libc/gen/opendir.c =================================================================== RCS file: /opt/FreeBSD/cvs/src/lib/libc/gen/opendir.c,v retrieving revision 1.10 diff -u -r1.10 opendir.c --- libc/gen/opendir.c 2000/01/27 23:06:18 1.10 +++ libc/gen/opendir.c 2000/12/04 20:03:13 @@ -259,6 +259,8 @@ dirp->dd_loc = 0; dirp->dd_fd = fd; dirp->dd_flags = flags; + dirp->dd_loccnt = 0; + LIST_INIT(&dirp->dd_locq); /* * Set up seek point for rewinddir. Index: libc/gen/telldir.c =================================================================== RCS file: /opt/FreeBSD/cvs/src/lib/libc/gen/telldir.c,v retrieving revision 1.4 diff -u -r1.4 telldir.c --- libc/gen/telldir.c 1995/05/30 05:40:26 1.4 +++ libc/gen/telldir.c 2000/12/04 20:18:22 @@ -54,39 +54,28 @@ * associated with that return value. */ struct ddloc { - struct ddloc *loc_next;/* next structure in list */ + LIST_ENTRY(ddloc) loc_lqe; /* list entry */ long loc_index; /* key associated with structure */ long loc_seek; /* magic cookie returned by getdirentries */ long loc_loc; /* offset of entry in buffer */ - const DIR* loc_dirp; /* directory which used this entry */ }; -#define NDIRHASH 32 /* Num of hash lists, must be a power of 2 */ -#define LOCHASH(i) ((i)&(NDIRHASH-1)) - -static long dd_loccnt; /* Index of entry for sequential readdir's */ -static struct ddloc *dd_hash[NDIRHASH]; /* Hash list heads for ddlocs */ - /* * return a pointer into a directory */ long telldir(dirp) - const DIR *dirp; + DIR *dirp; { - register int index; - register struct ddloc *lp; + struct ddloc *lp; if ((lp = (struct ddloc *)malloc(sizeof(struct ddloc))) == NULL) return (-1); - index = dd_loccnt++; - lp->loc_index = index; + lp->loc_index = dirp->dd_loccnt++; lp->loc_seek = dirp->dd_seek; lp->loc_loc = dirp->dd_loc; - lp->loc_dirp = dirp; - lp->loc_next = dd_hash[LOCHASH(index)]; - dd_hash[LOCHASH(index)] = lp; - return (index); + LIST_INSERT_HEAD(&dirp->dd_locq, lp, loc_lqe); + return (lp->loc_index); } /* @@ -95,20 +84,15 @@ */ void _seekdir(dirp, loc) - register DIR *dirp; + DIR *dirp; long loc; { - register struct ddloc *lp; - register struct ddloc **prevlp; + struct ddloc *lp; struct dirent *dp; - prevlp = &dd_hash[LOCHASH(loc)]; - lp = *prevlp; - while (lp != NULL) { + LIST_FOREACH(lp, &dirp->dd_locq, loc_lqe) { if (lp->loc_index == loc) break; - prevlp = &lp->loc_next; - lp = lp->loc_next; } if (lp == NULL) return; @@ -124,7 +108,7 @@ } found: #ifdef SINGLEUSE - *prevlp = lp->loc_next; + LIST_REMOVE(lp, loc_lqe); free((caddr_t)lp); #endif } @@ -134,24 +118,16 @@ */ void _reclaim_telldir(dirp) - register const DIR *dirp; + DIR *dirp; { - register struct ddloc *lp; - register struct ddloc **prevlp; - int i; - - for (i = 0; i < NDIRHASH; i++) { - prevlp = &dd_hash[i]; - lp = *prevlp; - while (lp != NULL) { - if (lp->loc_dirp == dirp) { - *prevlp = lp->loc_next; - free((caddr_t)lp); - lp = *prevlp; - continue; - } - prevlp = &lp->loc_next; - lp = lp->loc_next; - } + struct ddloc *lp; + struct ddloc *templp; + + lp = LIST_FIRST(&dirp->dd_locq); + while (lp != NULL) { + templp = lp; + lp = LIST_NEXT(lp, loc_lqe); + free(templp); } + LIST_INIT(&dirp->dd_locq); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 13:13:12 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 13:13:10 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 95F7E37B400; Mon, 4 Dec 2000 13:13:09 -0800 (PST) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.11.0/8.11.0) with ESMTP id eB4LD9q06142; Mon, 4 Dec 2000 13:13:09 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.11.1/8.11.1) with ESMTP id eB4LD8T74224; Mon, 4 Dec 2000 13:13:08 -0800 (PST) (envelope-from nsayer@sftw.com) Sender: nsayer@sftw.com Message-ID: <3A2C08E4.E0CA5057@sftw.com> Date: Mon, 04 Dec 2000 13:13:08 -0800 From: Nick Sayer X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > [...] > > 0 == bronze > 40 == silver > 128 == gold FWIW, it is more correct to say either 0 == bronze 40 == silver 104 == gold or 0 == bronze 64 == silver 128 == gold WEP has a 24 bit sequence number that perturbs the encryption. The fact that 24 bit sequence numbers can be run through on a busy LAN might make one wish to institute weekly key changes before bothering to go up to 128 bit encryption (that, and the fact that the front door to your house probably has a lot fewer than 40 bits of security). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 13:37:26 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 13:37:20 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 6D64737B400 for ; Mon, 4 Dec 2000 13:37:16 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eB4LahM02635; Mon, 4 Dec 2000 14:36:43 -0700 (MST) Date: Mon, 4 Dec 2000 14:36:44 -0700 (MST) From: X-Sender: To: Bernd Walter Cc: David Greenman , Subject: Re: current paging strategy In-Reply-To: <20001105175745.A42346@cicely8.cicely.de> 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 what exacly do you mean with critical path, here? JAn On Sun, 5 Nov 2000, Bernd Walter wrote: > On Thu, Nov 02, 2000 at 12:45:30AM -0800, David Greenman wrote: > > >Interesting. THis needs about two bytes per page for the counter? > > > > Actually, we found that a single byte per page was sufficient. Pages tended > > to be either heavily accessed or rarely accessed. Even in the unusual case > > where all pages are frequently accessed, the page reclaim rate (and thus > > adjustment rate of the page references count) increases high enough to still > > provide for a decent distribution of the counters and for the page LOU to be > > effective. > > One byte sounds good for i386. > Maybe it makes sense to have it 4 or 8 byte on risc platforms. > I wonder if it's a critical path and if there are more of this in > the kernel source. > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > > > > 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 Mon Dec 4 14:24:19 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 14:24:14 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 7129037B400; Mon, 4 Dec 2000 14:24:14 -0800 (PST) Date: Mon, 4 Dec 2000 14:24:14 -0800 From: "John W. De Boskey" To: Current List Subject: -current kernel panic: ufs_ihashget Message-ID: <20001204142414.A7479@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'm getting the following panic when I run the following command: tar -cvf - . | compress | dd bs=64m of=/dev/sa0 running with a blocksize of 2,4,8,16, or 32meg on the dd command run to completion with no problems. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x293944 instruction pointer = 0x8:0xc02a119f stack pointer = 0x10:0xd720dca4 frame pointer = 0x10:0xd720dcb4 code segment = base 0x0, limit 0xfffff, type = 0x1b = DPL 0, pres 1, def32 1, gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 290 (tar) trap number = 12 panic: page fault nm /boot/kernel/kernel | grep c02a11 | sort c02a1100 T ufs_ihashinit c02a1120 T ufs_ihashlookup c02a1168 T ufs_ihashget c02a11fc T ufs_ihashins System is -current as of 11:30am EST, Mon Dec 4, 2000 (today :-) dmesg output is included below. I'll compile up a kernel with gdb tomorrow. (Yes, it replicates...) -John Copyright (c) 1992-2000 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: Mon Dec 4 15:50:25 EST 2000 toor@FreeBSD.unx.sas.com:/usr/src/sys/compile/FreeBSD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 797416080 Hz CPU: Pentium III/Pentium III Xeon/Celeron (797.42-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 534933504 (522396K bytes) avail memory = 516440064 (504336K bytes) Preloaded elf kernel "kernel" at 0xc041a000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00fbbe0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: at 2.0 irq 9 pcib1: at device 30.0 on pci0 pci1: on pcib1 ahc0: port 0xec00-0xecff mem 0xfdfff000-0xfdffffff irq 9 at device 7.0 on pci1 aic7895: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xfdffe000-0xfdffefff irq 10 at device 7.1 on pci1 aic7895: Single Channel B, SCSI Id=7, 32/255 SCBs amr0: port 0xe480-0xe4ff irq 3 at device 9.0 on pci1 amr0: Firmware U.77, BIOS 1.47, 32MB RAM xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe400-0xe47f mem 0xfdffdc00-0xfdffdc7f irq 3 at device 12.0 on pci1 xl0: Ethernet address: 00:b0:d0:7d:7c:8e miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xff80-0xff9f irq 11 at device 31.2 on pci0 uhci0: (New UHCI DeviceId=0x24428086) usb0: on uhci0 usb0: USB revision 1.0 uhub0: (0x24428086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 31.3 irq 10 pci0: at 31.5 irq 10 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 isa_dmainit(2, 1024) failed 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 Generic PS/2 mouse, device ID 0 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 sio1: configured irq 3 not in bitmap of probed irqs 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/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 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: 19092MB [38792/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master using PIO4 Waiting 5 seconds for SCSI devices to settle amrd0: on amr0 amrd0: 69112MB (141541376 sectors) RAID 0 (optimal) sa0 at ahc0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/ad0s1a cd0 at ahc1 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 14:41:51 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 14:41:49 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 90D6737B400 for ; Mon, 4 Dec 2000 14:41:48 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eB4MfOV15907 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Mon, 4 Dec 2000 23:41:26 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eB4MfVm84235 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Mon, 4 Dec 2000 23:41:35 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id eB4MfRG05942; Mon, 4 Dec 2000 23:41:27 +0100 (CET) (envelope-from ticso) Date: Mon, 4 Dec 2000 23:41:26 +0100 From: Bernd Walter To: janb@cs.utep.edu Cc: Bernd Walter , David Greenman , freebsd-current@FreeBSD.ORG Subject: Re: current paging strategy Message-ID: <20001204234126.A5927@cicely5.cicely.de> References: <20001105175745.A42346@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from janb@cs.utep.edu on Mon, Dec 04, 2000 at 02:36:44PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 04, 2000 at 02:36:44PM -0700, janb@cs.utep.edu wrote: > what exacly do you mean with critical path, here? Performance critical. Most RISC platforms are optimized for 32 and maybe 64 bit structures. E.g. First generation alphas (without BWX) can't even access anything smaller than 32bit in memory without doing big magic. So one byte can become a big impact on performance. > On Sun, 5 Nov 2000, Bernd Walter wrote: > > On Thu, Nov 02, 2000 at 12:45:30AM -0800, David Greenman wrote: > > > >Interesting. THis needs about two bytes per page for the counter? > > > > > > Actually, we found that a single byte per page was sufficient. Pages tended > > > to be either heavily accessed or rarely accessed. Even in the unusual case > > > where all pages are frequently accessed, the page reclaim rate (and thus > > > adjustment rate of the page references count) increases high enough to still > > > provide for a decent distribution of the counters and for the page LOU to be > > > effective. > > > > One byte sounds good for i386. > > Maybe it makes sense to have it 4 or 8 byte on risc platforms. > > I wonder if it's a critical path and if there are more of this in > > the kernel source. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 14:55: 9 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 14:55:07 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id C313837B400 for ; Mon, 4 Dec 2000 14:55:06 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 1434Vl-0006Am-00; Mon, 04 Dec 2000 22:55:05 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eB4MsYc03414; Mon, 4 Dec 2000 23:54:34 +0100 (CET) (envelope-from wkb) Date: Mon, 4 Dec 2000 23:54:34 +0100 From: Wilko Bulte To: Bernd Walter Cc: janb@cs.utep.edu, Bernd Walter , David Greenman , freebsd-current@freebsd.org Subject: Re: current paging strategy Message-ID: <20001204235434.A3400@freebie.demon.nl> References: <20001105175745.A42346@cicely8.cicely.de> <20001204234126.A5927@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001204234126.A5927@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Mon, Dec 04, 2000 at 11:41:26PM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 04, 2000 at 11:41:26PM +0100, Bernd Walter wrote: > On Mon, Dec 04, 2000 at 02:36:44PM -0700, janb@cs.utep.edu wrote: > > what exacly do you mean with critical path, here? > > Performance critical. > Most RISC platforms are optimized for 32 and maybe 64 bit structures. > E.g. First generation alphas (without BWX) can't even access anything > smaller than 32bit in memory without doing big magic. > So one byte can become a big impact on performance. One of the reasons anything < EV56 falls out of favor by dBMS folks these days. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 16: 6:40 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 16:06:39 2000 Return-Path: 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 9F25437B400 for ; Mon, 4 Dec 2000 16:06:38 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB506PH77737; Mon, 4 Dec 2000 16:06:25 -0800 (PST) (envelope-from dillon) Date: Mon, 4 Dec 2000 16:06:25 -0800 (PST) From: Matt Dillon Message-Id: <200012050006.eB506PH77737@earth.backplane.com> To: Wilko Bulte Cc: Bernd Walter , janb@cs.utep.edu, Bernd Walter , David Greenman , freebsd-current@FreeBSD.ORG Subject: Re: current paging strategy References: <20001105175745.A42346@cicely8.cicely.de> <20001204234126.A5927@cicely5.cicely.de> <20001204235434.A3400@freebie.demon.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, Dec 04, 2000 at 11:41:26PM +0100, Bernd Walter wrote: :> On Mon, Dec 04, 2000 at 02:36:44PM -0700, janb@cs.utep.edu wrote: :> > what exacly do you mean with critical path, here? :> :> Performance critical. :> Most RISC platforms are optimized for 32 and maybe 64 bit structures. :> E.g. First generation alphas (without BWX) can't even access anything :> smaller than 32bit in memory without doing big magic. :> So one byte can become a big impact on performance. : :One of the reasons anything < EV56 falls out of favor by dBMS folks these :days. : :-- :Wilko Bulte Arnhem, the Netherlands :wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl sizeof(vm_page_t) is more critical. Bloating the structure eats a massive amount of memory, so messing around with all the short and char fields is out of the question even if we were to take a cpu hit. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 16: 9:11 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 16:09:09 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 9B14D37B400 for ; Mon, 4 Dec 2000 16:09:08 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA20858; Mon, 4 Dec 2000 16:05:22 -0800 (PST) Message-Id: <200012050005.QAA20858@implode.root.com> To: Bernd Walter Cc: janb@cs.utep.edu, freebsd-current@FreeBSD.ORG Subject: Re: current paging strategy In-reply-to: Your message of "Sun, 05 Nov 2000 17:57:46 +0100." <20001105175745.A42346@cicely8.cicely.de> From: David Greenman Reply-To: dg@root.com Date: Mon, 04 Dec 2000 16:05:22 -0800 Sender: dg@implode.root.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, Nov 02, 2000 at 12:45:30AM -0800, David Greenman wrote: >> >Interesting. THis needs about two bytes per page for the counter? >> >> Actually, we found that a single byte per page was sufficient. Pages tended >> to be either heavily accessed or rarely accessed. Even in the unusual case >> where all pages are frequently accessed, the page reclaim rate (and thus >> adjustment rate of the page references count) increases high enough to still >> provide for a decent distribution of the counters and for the page LOU to be >> effective. > >One byte sounds good for i386. >Maybe it makes sense to have it 4 or 8 byte on risc platforms. >I wonder if it's a critical path and if there are more of this in >the kernel source. No, space consumption of the vm_page data structure is by far the greatest concern. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 16:46:11 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 16:46:10 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.63]) by hub.freebsd.org (Postfix) with SMTP id 1A5B537B401 for ; Mon, 4 Dec 2000 16:46:08 -0800 (PST) Received: (qmail 12480 invoked by uid 1000); 5 Dec 2000 00:39:56 -0000 Date: Tue, 5 Dec 2000 01:39:55 +0100 From: Andrea Campi To: John Baldwin Cc: Andrea Campi , freebsd-current@FreeBSD.org Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001205013955.A2351@webcom.it> Mail-Followup-To: John Baldwin , Andrea Campi , freebsd-current@FreeBSD.org References: <20001129200041.M92759@inet.it> 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 Wed, Nov 29, 2000 at 11:50:20AM -0800 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 > > > > db> x/i,10 0xc025ad3c > > scrn_timer: pushl %ebp > > [...] > > > > nm just confirmed this, so it definitely looks like scrn_timer is to blame > > here. Any other instructions? ;-) For the time being, vidcontrol -t off > > (seems to) keep the machine up. > > > > Bye, > > Andrea > > Weird, I don't see anything offhand that syscons is doing that would cause it > to leak Giant. Hmm. Can you add a the same code before the mtx_enter() of Having gone through yet another series of cvsup - make kernel - panics, I can now confirm this happens if and only if I have VESA defined. A vidcontrol -t off stops the panics. Now I will try to understand what's up, but I should warn you that I'm not really confident with this part of the kernel yet. More details: this is an IBM Thinkpad laptop with APM enabled and in the kernel. As usual, any hint is more than welcome. This used to work... Bye, Andrea -- The three Rs of Microsoft support: Retry, Reboot, Reinstall. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 18:26:54 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 18:26:50 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 07D8937B400 for ; Mon, 4 Dec 2000 18:26:50 -0800 (PST) Received: from laptop.baldwin.cx (root@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB52QLC25831; Mon, 4 Dec 2000 18:26:21 -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: <20001205013955.A2351@webcom.it> Date: Mon, 04 Dec 2000 18:26:57 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Cc: freebsd-current@FreeBSD.org, Andrea Campi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Dec-00 Andrea Campi wrote: >> > >> > db> x/i,10 0xc025ad3c >> > scrn_timer: pushl %ebp >> > [...] >> > >> > nm just confirmed this, so it definitely looks like scrn_timer is to blame >> > here. Any other instructions? ;-) For the time being, vidcontrol -t off >> > (seems to) keep the machine up. >> > >> > Bye, >> > Andrea >> >> Weird, I don't see anything offhand that syscons is doing that would cause >> it >> to leak Giant. Hmm. Can you add a the same code before the mtx_enter() of > > Having gone through yet another series of cvsup - make kernel - panics, I can > now confirm this happens if and only if I have VESA defined. A > > vidcontrol -t off > > stops the panics. Now I will try to understand what's up, but I should warn > you > that I'm not really confident with this part of the kernel yet. > > More details: this is an IBM Thinkpad laptop with APM enabled and in the > kernel. > As usual, any hint is more than welcome. This used to work... Which screen saver? Does it do it with all of them? Just graphical ones, just text ones, just green_saver, etc.? > Bye, > Andrea -- 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 Dec 4 18:33:27 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 18:33:26 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.63]) by hub.freebsd.org (Postfix) with SMTP id 1339037B401 for ; Mon, 4 Dec 2000 18:33:24 -0800 (PST) Received: (qmail 36150 invoked by uid 1000); 5 Dec 2000 02:27:14 -0000 Date: Tue, 5 Dec 2000 03:27:13 +0100 From: Andrea Campi To: John Baldwin Cc: freebsd-current@FreeBSD.org, Andrea Campi Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001205032713.B2351@webcom.it> Mail-Followup-To: John Baldwin , freebsd-current@FreeBSD.org, Andrea Campi References: <20001205013955.A2351@webcom.it> 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 Mon, Dec 04, 2000 at 06:26:57PM -0800 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 > > More details: this is an IBM Thinkpad laptop with APM enabled and in the > > kernel. > > As usual, any hint is more than welcome. This used to work... > > Which screen saver? Does it do it with all of them? Just graphical ones, just > text ones, just green_saver, etc.? Rrrright... I can assure you I would never have thought this could make a difference... Ok, I will try each one. At the moment, I'm using logo_saver. I will let you know. Bye, Andrea -- Weird enough for government work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 18:41:53 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 18:41:50 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id AB81F37B400 for ; Mon, 4 Dec 2000 18:41:50 -0800 (PST) Received: from laptop.baldwin.cx (root@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB52fJC26576; Mon, 4 Dec 2000 18:41: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: <20001205032713.B2351@webcom.it> Date: Mon, 04 Dec 2000 18:41:55 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Cc: Andrea Campi , freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Dec-00 Andrea Campi wrote: >> > More details: this is an IBM Thinkpad laptop with APM enabled and in the >> > kernel. >> > As usual, any hint is more than welcome. This used to work... >> >> Which screen saver? Does it do it with all of them? Just graphical ones, >> just >> text ones, just green_saver, etc.? > > Rrrright... I can assure you I would never have thought this could make a > difference... That's ok, it didn't occur to me either at first. However, the green_saver calls into APM, and the graphical ones will call into VESA, so it might make a difference. > Ok, I will try each one. At the moment, I'm using logo_saver. > I will let you know. > > Bye, > Andrea > > -- > Weird enough for government work. -- 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 Dec 4 18:59:10 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 18:59:07 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cae88-102-101.sc.rr.com (unknown [24.88.102.101]) by hub.freebsd.org (Postfix) with ESMTP id A7BF037B400; Mon, 4 Dec 2000 18:59:06 -0800 (PST) Received: (from dmaddox@localhost) by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eB52xVl00277; Mon, 4 Dec 2000 21:59:31 -0500 (EST) (envelope-from dmaddox) Date: Mon, 4 Dec 2000 21:59:31 -0500 From: "Donald J . Maddox" To: John Baldwin Cc: Andrea Campi , Andrea Campi , freebsd-current@FreeBSD.ORG Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001204215931.A248@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: John Baldwin , Andrea Campi , Andrea Campi , freebsd-current@FreeBSD.ORG References: <20001205032713.B2351@webcom.it> 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 Mon, Dec 04, 2000 at 06:41:55PM -0800 Return-Receipt-To: dmaddox@sc.rr.com Sender: dmaddox@cae88-102-101.sc.rr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just as a data point, I just tried this as well... The daemon saver was ok, the fire saver was ok, but as soon as I loaded logo_saver and it activated, I got a 'dc0 timeout'(?) and I was unable to access any of the vtys after that... I could switch vtys, but could not type anything. The fire_saver module is obviously using a VESA mode, but I had no problem problem with it... On Mon, Dec 04, 2000 at 06:41:55PM -0800, John Baldwin wrote: > > On 05-Dec-00 Andrea Campi wrote: > >> > More details: this is an IBM Thinkpad laptop with APM enabled and in the > >> > kernel. > >> > As usual, any hint is more than welcome. This used to work... > >> > >> Which screen saver? Does it do it with all of them? Just graphical ones, > >> just > >> text ones, just green_saver, etc.? > > > > Rrrright... I can assure you I would never have thought this could make a > > difference... > > That's ok, it didn't occur to me either at first. However, the green_saver > calls into APM, and the graphical ones will call into VESA, so it might make a > difference. > > > Ok, I will try each one. At the moment, I'm using logo_saver. > > I will let you know. > > > > Bye, > > Andrea > > > > -- > > Weird enough for government work. > > -- > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 19: 3:45 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 19:03:41 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cae88-102-101.sc.rr.com (unknown [24.88.102.101]) by hub.freebsd.org (Postfix) with ESMTP id 739CE37B400; Mon, 4 Dec 2000 19:03:40 -0800 (PST) Received: (from dmaddox@localhost) by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eB5345Z00319; Mon, 4 Dec 2000 22:04:05 -0500 (EST) (envelope-from dmaddox) Date: Mon, 4 Dec 2000 22:04:05 -0500 From: "Donald J . Maddox" To: John Baldwin , Andrea Campi , Andrea Campi , freebsd-current@FreeBSD.ORG Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001204220405.B248@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: John Baldwin , Andrea Campi , Andrea Campi , freebsd-current@FreeBSD.ORG References: <20001205032713.B2351@webcom.it> <20001204215931.A248@cae88-102-101.sc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001204215931.A248@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Mon, Dec 04, 2000 at 09:59:31PM -0500 Return-Receipt-To: dmaddox@sc.rr.com Sender: dmaddox@cae88-102-101.sc.rr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I guess I should specify that this is a desktop with APM enabled in the BIOS, but not being used otherwise... VESA module loaded. #uname -a FreeBSD cae88-102-101.sc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Dec 2 16:07:54 EST 2000 root@cae88-102-101.sc.rr.com:/usr/src/sys/compile/RHIANNON i386 #kldstat Id Refs Address Size Name 1 9 0xc0100000 234878 kernel 2 1 0xc0335000 5540 vesa.ko 3 1 0xc033b000 9eb4 cd9660.ko 4 1 0xc0345000 eb44 msdos.ko 5 1 0xc0354000 7a98 procfs.ko 6 1 0xc035c000 158ec linux.ko 7 1 0xc0372000 b2cc if_dc.ko 8 2 0xc037e000 10004 miibus.ko 9 1 0xc038f000 76e0 linprocfs.ko On Mon, Dec 04, 2000 at 09:59:31PM -0500, Donald J . Maddox wrote: > Just as a data point, I just tried this as well... The daemon saver was ok, > the fire saver was ok, but as soon as I loaded logo_saver and it activated, > I got a 'dc0 timeout'(?) and I was unable to access any of the vtys after > that... I could switch vtys, but could not type anything. > > The fire_saver module is obviously using a VESA mode, but I had no problem > problem with it... > > On Mon, Dec 04, 2000 at 06:41:55PM -0800, John Baldwin wrote: > > > > On 05-Dec-00 Andrea Campi wrote: > > >> > More details: this is an IBM Thinkpad laptop with APM enabled and in the > > >> > kernel. > > >> > As usual, any hint is more than welcome. This used to work... > > >> > > >> Which screen saver? Does it do it with all of them? Just graphical ones, > > >> just > > >> text ones, just green_saver, etc.? > > > > > > Rrrright... I can assure you I would never have thought this could make a > > > difference... > > > > That's ok, it didn't occur to me either at first. However, the green_saver > > calls into APM, and the graphical ones will call into VESA, so it might make a > > difference. > > > > > Ok, I will try each one. At the moment, I'm using logo_saver. > > > I will let you know. > > > > > > Bye, > > > Andrea > > > > > > -- > > > Weird enough for government work. > > > > -- > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 21:43:48 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 21:43:46 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gw2-harmon.swau.edu (gw2-harmon.swau.edu [205.165.193.198]) by hub.freebsd.org (Postfix) with ESMTP id 3779837B400 for ; Mon, 4 Dec 2000 21:43:46 -0800 (PST) Received: from sphere.swau.edu (sphere.swau.edu [205.165.192.254]) by gw2-harmon.swau.edu (8.9.3/8.9.1) with ESMTP id XAA00664 for ; Mon, 4 Dec 2000 23:43:45 -0600 Received: from delta (mail@delta.swau.edu [198.215.22.253]) by sphere.swau.edu (8.9.3/8.9.1) with ESMTP id XAA31360 for ; Mon, 4 Dec 2000 23:43:41 -0600 Received: from edwardsa (helo=localhost) by delta with local-esmtp (Exim 3.12 #1 (Debian)) id 143AtA-0002zl-00 for ; Mon, 04 Dec 2000 23:43:40 -0600 Date: Mon, 4 Dec 2000 23:43:40 -0600 (CST) From: Adam Edwards To: freebsd-current@freebsd.org Subject: make buildworld trouble 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 just finished getting all the source, using cvsup. When I do a make buildworld, i get the following errors plus more but they are all related to the symhacks.h included from the crypto file. In file included from /usr/obj/usr/src/secure/lib/libcrypto/openssl/bio.h:67, from /usr/obj/usr/src/secure/lib/libcrypto/openssl/err.h:68, from /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cpt_err.c:62: I serched all through my system and the source and couldn't find the symhacks.h file. I was wondering if anybody else has had the same problem or if somebody knew how to fix it. Much Appreciated, Adam Edwards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 21:58:19 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 21:58:13 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 3072737B400; Mon, 4 Dec 2000 21:58:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id OAA91979; Tue, 5 Dec 2000 14:58:09 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: stable@freebsd.org, current@freebsd.org In-Reply-To: <20000927133044R.matusita@jp.FreeBSD.org> References: <20000731201222N.matusita@jp.FreeBSD.org> <200007311120.EAA03565@freefall.freebsd.org> <20000927133044R.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Notus) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 43 From: Makoto MATSUSHITA To: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/20311: src/release/Makefile: broken CHECKSUM.MD5 Date: Tue, 05 Dec 2000 14:58:07 +0900 Message-Id: <20001205145807I.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (forward to stable/current also, to open this problem widely) matusita> * CHECKSUM.MD5 is still broken. It also affected to 4.1.1-RELEASE I cannot believe that this problem is still there, and CHECKSUM.MD5s of 4.2-RELEASE/{src,crypto} are also broken. However, it's easy to fix just like this (CAUTION: I don't test with this): Index: Makefile =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/release/Makefile,v retrieving revision 1.586 diff -c -r1.586 Makefile *** Makefile 2000/11/21 04:37:30 1.586 --- Makefile 2000/12/05 05:43:41 *************** *** 503,509 **** if [ -f ssecure.aa ] ; then mv ssecure.* ../crypto ; fi && \ if [ -f scrypto.aa ] ; then mv scrypto.* ../crypto ; fi && \ if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi && \ ! if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; ) ; fi @echo "src distribution is finished." .endif touch release.7 --- 503,512 ---- if [ -f ssecure.aa ] ; then mv ssecure.* ../crypto ; fi && \ if [ -f scrypto.aa ] ; then mv scrypto.* ../crypto ; fi && \ if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi && \ ! if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; \ ! cd ${RD}/dists/crypto; rm -f CHECKSUM.MD5; \ ! md5 * > CHECKSUM.MD5 ) ; fi ! (cd ${RD}/dists/src; rm -f CHECKSUM.MD5; md5 * > CHECKSUM.MD5) @echo "src distribution is finished." .endif touch release.7 But if creating CHECKSUM.MD5 files are already totally broken feature, we can simply remove all CHECKSUM.MD5 files. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 4 23: 1:55 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 23:01:51 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from jhb-imta.mweb.co.za (jhb-imta.mweb.co.za [196.2.48.244]) by hub.freebsd.org (Postfix) with ESMTP id 9984A37B400; Mon, 4 Dec 2000 23:01:50 -0800 (PST) Received: from wheelerz.mweb.co.za ([196.7.200.49]) by jhb-imta.mweb.co.za (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G53003JS23YMW@jhb-imta.mweb.co.za>; Tue, 5 Dec 2000 09:00:01 +0200 (GMT-2) Received: (from gramroam@localhost) by wheelerz.mweb.co.za (8.11.1/8.11.1) id eB56NY907869; Tue, 05 Dec 2000 08:23:34 +0200 (SAST envelope-from gramster@mweb.co.za) Date: Tue, 05 Dec 2000 08:11:23 +0200 (SAST) From: Graham Wheeler Subject: Re: ATI Rage Mobility and VESA driver In-reply-to: <4.3.2.7.0.20001204210058.00d04900@mail.drwilco.net> To: "Rogier R. Mulhuijzen" Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Message-id: <200012050623.eB56NY907869@wheelerz.mweb.co.za> MIME-version: 1.0 X-Mailer: ELM [version 2.4ME+ PL68 (25)] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >However, using vidcontrol and attempting to set any VESA modes still > >produces "operation not supported by device". > > Just checking, but do you have > > options VGA_NO_MODE_CHANGE # don't change video modes Nope. But maybe I'm just expecting more modes than I can get. I can get 80x25, 80x30, 80x50 and 80x60 to work (modes 24, 30, 32, and 34 respectively). But these are the only text modes shown when I do a "vidcontrol -i mode". I can't get more than 80 columns, and the graphic screen savers won't work ("the console does not support M_VGA_CG320"). vidcontrol shows 15bpp, 16bpp, 24bpp and 32bpp 320x200 modes; perhaps the screen savers are 8bpp? I guess it makes sense I can't get 132 column modes, as even with an 8 pixel wide font a horizontal resolution of 1024 only makes 128 columns. "vidcontrol VESA_" fails which is why I was confused about the VESA capabilities of the ATI Rage Mobility. This includes VESA_800x600 (and yes, I do have "option SC_PIXEL_MODE" in the kernel config). regards Gram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 0: 6:35 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 00:06:33 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from crucian.comset.net (crucian.comset.net [213.172.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 73EAE37B400 for ; Tue, 5 Dec 2000 00:06:31 -0800 (PST) Received: from localhost (kong@localhost) by crucian.comset.net (8.11.1/8.8.7) with ESMTP id eB586C427726 for ; Tue, 5 Dec 2000 11:06:13 +0300 (MSK) Date: Tue, 5 Dec 2000 11:06:12 +0300 (MSK) From: Hostas Red To: freebsd-current@freebsd.org Subject: Problems in making 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 Hi! I have a following problem in making world for some time already: ===> gnu/usr.bin/binutils/strip cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip -I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils -I/usr/obj/usr/src/i386/usr/include -o strip objcopy.o is-strip.o ../libbinutils/libbinutils.a ../libbfd/libbfd.a ../libiberty/libiberty.a ../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname': bucomm.o(.text+0x35b): warning: mktemp() possibly used unsafely; consider using mkstemp() cp strip maybe_stripped strip maybe_stripped ===> gnu/usr.bin/binutils/doc ===> gnu/usr.bin/binutils/gdb make: don't know how to make /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include/wait.h. Stop *** Error code 2 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Any suggestions? Adios, /KONG ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 1:42:19 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 01:42:17 2000 Return-Path: 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 D705337B400; Tue, 5 Dec 2000 01:42:15 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id KAA22986; Tue, 5 Dec 2000 10:39:35 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Andrea Campi Cc: John Baldwin , freebsd-current@FreeBSD.ORG, Andrea Campi Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] References: <20001205013955.A2351@webcom.it> <20001205032713.B2351@webcom.it> From: Dag-Erling Smorgrav Date: 05 Dec 2000 10:39:34 +0100 In-Reply-To: Andrea Campi's message of "Tue, 5 Dec 2000 03:27:13 +0100" Message-ID: Lines: 13 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 Andrea Campi writes: > Ok, I will try each one. At the moment, I'm using logo_saver. > I will let you know. Take a long hard look at vesa_set_mode() and vesa_set_origin() in sys/i386/isa/vesa.c. If the panic occurs while the console is still in text mode, the bug is in vesa_set_mode(); if it occurs after the console has switched to graphics mode, it's probably in vesa_set_origin(). 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 Dec 5 2:26:29 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 02:26:26 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 0049637B400; Tue, 5 Dec 2000 02:26:24 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:wS/o/LbmhUYXzrLZFszj0ENZxDmvBgI2@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.11.0/3.7Wpl2) with ESMTP id eB5AQ8o15844; Tue, 5 Dec 2000 19:26:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:7jDE4t5WyNjmQTZmujI0psAvhN7ZWt/H@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id TAA12407; Tue, 5 Dec 2000 19:33:22 +0900 (JST) Message-Id: <200012051033.TAA12407@zodiac.mech.utsunomiya-u.ac.jp> To: Dag-Erling Smorgrav Cc: Andrea Campi , John Baldwin , freebsd-current@FreeBSD.ORG, Andrea Campi , yokota@zodiac.mech.utsunomiya-u.ac.jp Reply-To: kazutaka.yokota@nifty.com Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] In-reply-to: Your message of "05 Dec 2000 10:39:34 +0100." References: <20001205013955.A2351@webcom.it> <20001205032713.B2351@webcom.it> Date: Tue, 05 Dec 2000 19:33:21 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Andrea Campi writes: >> Ok, I will try each one. At the moment, I'm using logo_saver. >> I will let you know. > >Take a long hard look at vesa_set_mode() and vesa_set_origin() in >sys/i386/isa/vesa.c. If the panic occurs while the console is still in >text mode, the bug is in vesa_set_mode(); if it occurs after the >console has switched to graphics mode, it's probably in >vesa_set_origin(). The may be in the VESA BIOS on the video card :-) The vesa module calls the VESA BIOS to change video modes. The bug may not necessarily be in the BIOS "code", but the VESA video mode "table" to which the vesa module refers, when it sets up a new video mode, and calculates and initializes variables in the vesa module. I would like to see full dump of 'vidcontrol -i adapter', 'vidcontrol -i mode' and dmesg after the vesa module is loaded (you get very verbose output from the vesa module init code if you boot the kernel with 'boot -v'). You see, the VESA BIOS support on some video cards is not so complete. For example, we saw in the mailing list recently that the "VGA compatible" bit is somewhat turned off for VESA high resolution modes, didn't we? That possibly was a bug in that VESA BIOS. (OR, those mode ARE genuinely VGA-incompatible and we shouldn't use them the way the vesa modules accesses them...) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 7: 5:24 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 07:05:21 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id B5CBC37B400 for ; Tue, 5 Dec 2000 07:05:20 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 143Jhl-0000NV-00; Tue, 05 Dec 2000 08:08:29 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A2D04EC.E9494490@softweyr.com> Date: Tue, 05 Dec 2000 08:08:28 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: <3A2BBE2F.FF5CA11@softweyr.com> <200012010142.SAA33362@harmony.village.org> <20001204140523.A12859@genesiseurope.net> <200012041836.LAA62726@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3A2BBE2F.FF5CA11@softweyr.com> Wes Peters writes: > : Dell is selling a Lucent-OEMed card for $139. I don't know if it is a > : Silver or Gold, though. > > http://www.comready.com/dlindwwirlan.html > > is selling what appears to be a lucentOEM'd card for $119. It has > 40-bit WEP, so I don't know what metal that makes it (despite having > been told the last time this came up). Silver, according to the wicontrol(8) man page. ;^) > There's no external antenna > connector, however. Still not a bad price and with $20 of the price > point for taking my whole house wireless. Yeah, thanks. I still haven't decided if I'm going to stick (another) wireless card in my gateway machine or buy an access point/bridge. The prices of PCMCIA card cages are frightfully high, making the cost roughly the same, and the access point would support infrastructure mode also. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 11: 5:44 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 11:05:30 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from spaceghost.fuse.net (spaceghost.fuse.net [216.68.1.121]) by hub.freebsd.org (Postfix) with ESMTP id 0E75D37B401 for ; Tue, 5 Dec 2000 11:05:30 -0800 (PST) Received: from emaxamd1 ([216.68.44.122]) by spaceghost.fuse.net (InterMail vK.4.02.00.00 201-232-116 license 55099144ff2ca28e37c1a3433615ef97) with SMTP id <20001205190720.JLBT17981.spaceghost@emaxamd1>; Tue, 5 Dec 2000 14:07:20 -0500 From: To: Welcome Return-Receipt-To: Reply-To: forumarket@yahoo.com Subject: Welcome Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-Id: <20001205190720.JLBT17981.spaceghost@emaxamd1> Date: Tue, 5 Dec 2000 14:07:20 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NEWSLETTER * Home Come and Get a Free Painting www.artofspirit.net Welcome to Art of Spirit Art Of Spirit was started by Elizabeth O'Neill. She was born and= raised in Cleveland, Ohio and studied at two colleges, The= Cleveland Art Institute, and Illinois University. Elizabeth= O'Neill also studied with Corita Kent of California and has= taught art on all levels for twenty five years. She also became= a docent (tour guide) for the Cincinnati Art Museum in 1979. Elizabeth states "My art comes from the living experience of people. Our Country= has such a diversity, we have the opportunity of using all the= colors to their best advantage." Elizabeth O'Neill's art is abstract and against the grain. Her= Art Of Spirit is a mix of creativity and meaning. Her artwork is= not only abstract but expresses a thought that the world is= feeling or the way the world looks through Elizabeth's eyes. But= because her art work is abstract what you see in her art work is= drawn from the experiences that you have had in your lifetime.= Most people are under the erroneous opinion that abstract art= work is easier than realism, or still life, but this is far from= true. Most abstract artists are good or great painters that have= become tired and bored with painting that which is already there= and want to put their own ideas and thoughts into their= paintings. Elizabeth states:" Why just paint a tree, when you= can just take a picture of it!." Elizabeth is not alone in this thought, most abstract artists= feel this way. Take Picasso for instance: He was a great painter= and his abstractions taught everyone how to recreate using their= own imaginations. (More on picasso in the next news letter.) Click Here artofspirit.net Special This Month Free Watercolor Painting with your purchase of any painting on= the web. To be removed from our list please let us know at= takemeoffartofspirit@yahoo.com NEWSLETTER NEWSLETTER To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 11:35:10 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 11:35:07 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 2FE4237B400 for ; Tue, 5 Dec 2000 11:35:07 -0800 (PST) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA37245; Tue, 5 Dec 2000 11:33:05 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id LAA23532; Tue, 5 Dec 2000 11:32:51 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200012051932.LAA23532@whistle.com> Subject: Re: Lucent Orinoco Gold PCCard? In-Reply-To: <3A2D04EC.E9494490@softweyr.com> from Wes Peters at "Dec 5, 2000 08:08:28 am" To: Wes Peters Date: Tue, 5 Dec 2000 11:32:51 -0800 (PST) Cc: Warner Losh , Sascha Luck , 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 Wes Peters writes: | Warner Losh wrote: | > | > In message <3A2BBE2F.FF5CA11@softweyr.com> Wes Peters writes: | > : Dell is selling a Lucent-OEMed card for $139. I don't know if it is a | > : Silver or Gold, though. | > | > http://www.comready.com/dlindwwirlan.html | > | > is selling what appears to be a lucentOEM'd card for $119. It has | > 40-bit WEP, so I don't know what metal that makes it (despite having | > been told the last time this came up). | | Silver, according to the wicontrol(8) man page. ;^) | | > There's no external antenna | > connector, however. Still not a bad price and with $20 of the price | > point for taking my whole house wireless. | | Yeah, thanks. I still haven't decided if I'm going to stick (another) | wireless card in my gateway machine or buy an access point/bridge. The | prices of PCMCIA card cages are frightfully high, making the cost roughly | the same, and the access point would support infrastructure mode also. Well this is what I'm doing with the Aironet stuff. I have a script to flip between modes until it sync's up. I bought the PCMCIA ISA adapter for $25 from a local surplus place. BTW I saw ADDTRON http://www.addtron.com/ has a base station for around $220 that can do 128 bit encryption, has an antenna and is Web administered. I haven't used it but it looks interesting. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 12:46:58 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 12:46:56 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A6F0A37B400 for ; Tue, 5 Dec 2000 12:46:54 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eB5Kkq598778; Tue, 5 Dec 2000 13:46:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA72980; Tue, 5 Dec 2000 13:46:51 -0700 (MST) Message-Id: <200012052046.NAA72980@harmony.village.org> To: Doug Ambrisko Subject: Re: Lucent Orinoco Gold PCCard? Cc: Wes Peters , Sascha Luck , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Dec 2000 11:32:51 PST." <200012051932.LAA23532@whistle.com> References: <200012051932.LAA23532@whistle.com> Date: Tue, 05 Dec 2000 13:46:51 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012051932.LAA23532@whistle.com> Doug Ambrisko writes: : Well this is what I'm doing with the Aironet stuff. I have a script : to flip between modes until it sync's up. I bought the PCMCIA ISA : adapter for $25 from a local surplus place. Does this mean that the an driver can operate in "base station" mode? : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around : $220 that can do 128 bit encryption, has an antenna and is Web administered. : I haven't used it but it looks interesting. I'll have to check this out as well. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 13:10: 8 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 13:10:05 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 9F23A37B401 for ; Tue, 5 Dec 2000 13:10:04 -0800 (PST) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA41538; Tue, 5 Dec 2000 13:06:07 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id NAA19124; Tue, 5 Dec 2000 13:05:27 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200012052105.NAA19124@whistle.com> Subject: Re: Lucent Orinoco Gold PCCard? In-Reply-To: <200012052046.NAA72980@harmony.village.org> from Warner Losh at "Dec 5, 2000 01:46:51 pm" To: Warner Losh Date: Tue, 5 Dec 2000 13:05:27 -0800 (PST) Cc: Doug Ambrisko , Wes Peters , Sascha Luck , 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 Warner Losh writes: | In message <200012051932.LAA23532@whistle.com> Doug Ambrisko writes: | : Well this is what I'm doing with the Aironet stuff. I have a script | : to flip between modes until it sync's up. I bought the PCMCIA ISA | : adapter for $25 from a local surplus place. | | Does this mean that the an driver can operate in "base station" mode? No, just ad-hoc (atleast that's what is published). So on my laptop my script flips between modes (ad-hoc & infrastructure) until it sync's up with whatever it can find. I start it out of pccard.conf so it is automatic on card insertion, reboot or wakeup. | : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around | : $220 that can do 128 bit encryption, has an antenna and is Web administered. | : I haven't used it but it looks interesting. | | I'll have to check this out as well. Let us know what you find out. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 13:37:30 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 13:37:28 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [206.162.201.61]) by hub.freebsd.org (Postfix) with SMTP id 224C737B400 for ; Tue, 5 Dec 2000 13:37:28 -0800 (PST) Received: (qmail 39428 invoked by uid 1000); 5 Dec 2000 21:37:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Dec 2000 21:37:30 -0000 Date: Tue, 5 Dec 2000 16:37:30 -0500 (EST) From: Valentin Chopov To: freebsd-current@freebsd.org Subject: last changes in sys/kern/sysv_*.c in CURRENT and Squid 2.4 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 Hi, I have a problem with running server aplication which using message queues and shared memory - Squid 2.4 I'm giving short output of gdb. Thanks, Val (gdb) run -N Starting program: /usr/home/valentin/squid/squid-2.4-200012050000/src/squid -N Program received signal SIGSYS, Bad system call. 0x48160ba0 in msgsys () from /usr/lib/libc.so.5 (gdb) where #0 0x48160ba0 in msgsys () from /usr/lib/libc.so.5 #1 0x481568bf in msgget () from /usr/lib/libc.so.5 #2 0x80a9c4c in storeDiskdDirInit (sd=0x8203000) at store_dir_diskd.c:386 #3 0x80a073c in storeDirInit () at store_dir.c:55 #4 0x809d981 in storeInit () at store.c:937 #5 0x80872e1 in mainInitialize () at main.c:523 #6 0x80877f4 in main (argc=2, argv=0xbfbffb78) at main.c:696 #7 0x804a4f1 in _start () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 13:43:43 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 13:43:38 2000 Return-Path: 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 2C40337B400 for ; Tue, 5 Dec 2000 13:43:34 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id eB5LhMv86535; Tue, 5 Dec 2000 22:43:22 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id eB5Lgdj56253; Tue, 5 Dec 2000 22:43:01 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <02c201c05f04$a12c0b20$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Brian Somers" Cc: , References: <200011290110.eAT1ADD35445@hak.lan.Awfulhak.org> Subject: Re: How to debug ppp Date: Tue, 5 Dec 2000 22:42:28 +0100 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 It still doesn't work sometimes. I have a complete log (From dialing to hangup) at http://www.neland.dk/arnold.log My ppp.conf is at http://www.neland.dk/arnold.conf Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: LayerStart Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: State change Stopped --> Ack-Se nt Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: RecvConfigReq(2) state = Ack-Se nt Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: SendConfigAck(2) state = Ack-Se nt Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) ----- Original Message ----- From: "Brian Somers" To: "Leif Neland" Cc: ; Sent: Wednesday, November 29, 2000 2:10 AM Subject: Re: How to debug ppp > Well, I haven't seen this before !!! > > Your ISP is *insisting* that you negotiate a multi-link connection. > You can do this by simply adding > > set mrru 1506 > > to your config. > > > I sometimes have trouble connecting to my flat-rate isp via i4bsd. > > Most of the time it works, but sometimes the handshake fails. > > What is the log trying to tell me here? What can I tell my isp? > > > > When it fails, I can connect to another isp, which charges per minute > > charges, which I rather not use > > when I have flat rate. > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: Phone: xxxxxxxxx > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: Connected! > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: opening -> dial > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: 1: Dial attempt 1 of 2 > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: dial -> carrier > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: /dev/i4brbch0: CD detected > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: carrier -> login > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: login -> lcp > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: FSM: Using "1" as a transport > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Initial --> > > Closed > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: Entering STOPPED state for > > 2 s > > econds > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Closed --> > > Stopped > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(1) state = > > Stopped > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > 00:10:bc:06:fa:00 > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigReq(1) state = > > Stopped > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x0bde8bbc > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(1) state = > > Stopped > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: LayerStart > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Stopped --> > > Req-Sent > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(2) state = > > Req-Sent > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > 00:10:bc:06:fa:00 > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(2) state = > > Req-Sent > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > Looping: > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(3) state = > > Req-Sent > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > 00:10:bc:06:fa:00 > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(3) state = > > Req-Sent > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > Until hangup > > > > Leif > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 14:29:26 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 14:29:23 2000 Return-Path: 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 AC95B37B400 for ; Tue, 5 Dec 2000 14:29:22 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eB5MTLn01413; Tue, 5 Dec 2000 14:29:21 -0800 (PST) Date: Tue, 5 Dec 2000 14:29:21 -0800 From: Alfred Perlstein To: Valentin Chopov Cc: freebsd-current@FreeBSD.ORG Subject: Re: last changes in sys/kern/sysv_*.c in CURRENT and Squid 2.4 Message-ID: <20001205142920.G8051@fw.wintelcom.net> 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 valentin@valcho.net on Tue, Dec 05, 2000 at 04:37:30PM -0500 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Valentin Chopov [001205 13:37] wrote: > Hi, > > I have a problem with running server aplication which using message queues > and shared memory - Squid 2.4 > > I'm giving short output of gdb. > > Thanks, > > Val > > > (gdb) run -N > Starting > program: /usr/home/valentin/squid/squid-2.4-200012050000/src/squid -N > Program received signal SIGSYS, Bad system call. > 0x48160ba0 in msgsys () from /usr/lib/libc.so.5 > (gdb) where > #0 0x48160ba0 in msgsys () from /usr/lib/libc.so.5 > #1 0x481568bf in msgget () from /usr/lib/libc.so.5 > #2 0x80a9c4c in storeDiskdDirInit (sd=0x8203000) at store_dir_diskd.c:386 > #3 0x80a073c in storeDirInit () at store_dir.c:55 > #4 0x809d981 in storeInit () at store.c:937 > #5 0x80872e1 in mainInitialize () at main.c:523 > #6 0x80877f4 in main (argc=2, argv=0xbfbffb78) at main.c:696 > #7 0x804a4f1 in _start () I missed a SYSCALL_MODULE_HELPER() for msgsys, I have the fix, but just give me a minute to test it: Index: sysv_msg.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sysv_msg.c,v retrieving revision 1.27 diff -u -u -r1.27 sysv_msg.c --- sysv_msg.c 2000/12/01 08:57:45 1.27 +++ sysv_msg.c 2000/12/05 16:57:34 @@ -251,6 +251,7 @@ NULL }; +SYSCALL_MODULE_HELPER(msgsys, 6); SYSCALL_MODULE_HELPER(msgctl, 3); SYSCALL_MODULE_HELPER(msgget, 2); SYSCALL_MODULE_HELPER(msgsnd, 4); -- -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 Tue Dec 5 14:43:34 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 14:43:30 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id A717D37B401 for ; Tue, 5 Dec 2000 14:43:15 -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 eB5Mc0M09471; Tue, 5 Dec 2000 22:38:00 GMT (envelope-from brian@hak.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 eB5MelY05557; Tue, 5 Dec 2000 22:40:47 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012052240.eB5MelY05557@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Leif Neland" Cc: "Brian Somers" , freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: How to debug ppp In-Reply-To: Message from "Leif Neland" of "Tue, 05 Dec 2000 22:42:28 +0100." <02c201c05f04$a12c0b20$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Dec 2000 22:40:47 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What happens if you ``disable acfcomp protocomp'' and ``deny acfcomp protocomp'' in your config ? This should be negotiable with isdn.... but perhaps our requesting it is upsetting the peer ? > It still doesn't work sometimes. > > I have a complete log (From dialing to hangup) at > http://www.neland.dk/arnold.log > My ppp.conf is at http://www.neland.dk/arnold.conf > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: LayerStart > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: State change Stopped --> > Ack-Se > nt > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: RecvConfigReq(2) state = > Ack-Se > nt > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: SendConfigAck(2) state = > Ack-Se > nt > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > ----- Original Message ----- > From: "Brian Somers" > To: "Leif Neland" > Cc: ; > Sent: Wednesday, November 29, 2000 2:10 AM > Subject: Re: How to debug ppp > > > > Well, I haven't seen this before !!! > > > > Your ISP is *insisting* that you negotiate a multi-link connection. > > You can do this by simply adding > > > > set mrru 1506 > > > > to your config. > > > > > I sometimes have trouble connecting to my flat-rate isp via i4bsd. > > > Most of the time it works, but sometimes the handshake fails. > > > What is the log trying to tell me here? What can I tell my isp? > > > > > > When it fails, I can connect to another isp, which charges per minute > > > charges, which I rather not use > > > when I have flat rate. > > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: Phone: xxxxxxxxx > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: Connected! > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: opening -> dial > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: 1: Dial attempt 1 of 2 > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: dial -> carrier > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: /dev/i4brbch0: CD > detected > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: carrier -> login > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: login -> lcp > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: FSM: Using "1" as a > transport > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Initial --> > > > Closed > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: Entering STOPPED state > for > > > 2 s > > > econds > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Closed --> > > > Stopped > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(1) state = > > > Stopped > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > 00:10:bc:06:fa:00 > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigReq(1) state = > > > Stopped > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x0bde8bbc > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(1) state = > > > Stopped > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: LayerStart > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Stopped --> > > > Req-Sent > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(2) state = > > > Req-Sent > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > 00:10:bc:06:fa:00 > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(2) state = > > > Req-Sent > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > Looping: > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(3) state = > > > Req-Sent > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > 00:10:bc:06:fa:00 > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(3) state = > > > Req-Sent > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > Until hangup > > > > > > Leif -- 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 Tue Dec 5 15:30:34 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 15:30:24 2000 Return-Path: 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 6761137B400 for ; Tue, 5 Dec 2000 15:30:21 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id eB5NU9t44502; Wed, 6 Dec 2000 00:30:09 +0100 (CET) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id eB5NSYj57120; Wed, 6 Dec 2000 00:28:34 +0100 (CET) (envelope-from leif@neland.dk) Message-ID: <035201c05f13$5fea93c0$0e00a8c0@neland.dk> From: "Leif Neland" To: "Brian Somers" Cc: "Brian Somers" , References: <200012052240.eB5MelY05557@hak.lan.Awfulhak.org> Subject: Re: How to debug ppp Date: Wed, 6 Dec 2000 00:30:11 +0100 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 Didn't help: Dec 6 00:21:23 arnold ppp[56941]: tun0: Phase: bundle: Dead Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: bundle: Establish Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: closed -> opening Dec 6 00:21:24 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:24 arnold ppp[56941]: tun0: Chat: Phone: 103333361333 Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: Connected! Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: opening -> dial Dec 6 00:21:24 arnold ppp[56941]: tun0: Chat: 1: Dial attempt 1 of 2 Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: dial -> carrier Dec 6 00:21:25 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: /dev/i4brbch0: CD detected Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: carrier -> login Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: login -> lcp Dec 6 00:21:25 arnold ppp[56941]: tun0: LCP: FSM: Using "1" as a transport Dec 6 00:21:25 arnold ppp[56941]: tun0: LCP: 1: State change Initial --> Closed Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: Entering STOPPED state for 2 seconds Dec 6 00:21:25 arnold ppp[56941]: tun0: LCP: 1: State change Closed --> Stopped Dec 6 00:21:26 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(2) state = Stopped Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = Stopped Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(2) state = Stopped Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: LayerStart Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: State change Stopped --> Req-Sent Dec 6 00:21:27 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(3) state = Req-Sent Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(3) state = Req-Sent Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:28 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:29 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(4) state = Req-Sent Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(4) state = Req-Sent Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = Req-Sent Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] Dec 6 00:21:30 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(5) state = Req-Sent Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(5) state = Req-Sent Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:31 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:32 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(6) state = Req-Sent Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(6) state = Req-Sent Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = Req-Sent Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] Dec 6 00:21:33 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(7) state = Req-Sent Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(7) state = Req-Sent Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:34 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:35 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(8) state = Req-Sent Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(8) state = Req-Sent Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = Req-Sent Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] Dec 6 00:21:36 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(9) state = Req-Sent Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(9) state = Req-Sent Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(10) state = Req-Sent Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC 00:10:bc:06:fa:00 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(10) state = Req-Sent Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = Req-Sent Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Carrier lost Dec 6 00:21:40 arnold ppp[56941]: tun0: LCP: 1: State change Req-Sent --> Starting Dec 6 00:21:40 arnold ppp[56941]: tun0: LCP: 1: LayerFinish Dec 6 00:21:40 arnold ppp[56941]: tun0: LCP: 1: State change Starting --> Initial Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Disconnected! Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: lcp -> logout Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Disconnected! Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: logout -> hangup Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Connect time: 16 secs: 351 octets in, 228 octets out Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: : 19 packets in, 29 packets out Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: total 36 bytes/sec, peak 50 bytes/sec on Wed Dec 6 00:21:40 2000 Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: hangup -> closed Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: bundle: Dead ----- Original Message ----- From: "Brian Somers" To: "Leif Neland" Cc: "Brian Somers" ; ; Sent: Tuesday, December 05, 2000 11:40 PM Subject: Re: How to debug ppp > What happens if you ``disable acfcomp protocomp'' and ``deny acfcomp > protocomp'' in your config ? > > This should be negotiable with isdn.... but perhaps our requesting it > is upsetting the peer ? > > > It still doesn't work sometimes. > > > > I have a complete log (From dialing to hangup) at > > http://www.neland.dk/arnold.log > > My ppp.conf is at http://www.neland.dk/arnold.conf > > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC > > 00:10:bc:06:fa:00 > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: LayerStart > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: State change Stopped --> > > Ack-Se > > nt > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: RecvConfigReq(2) state = > > Ack-Se > > nt > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC > > 00:10:bc:06:fa:00 > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: SendConfigAck(2) state = > > Ack-Se > > nt > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > > ----- Original Message ----- > > From: "Brian Somers" > > To: "Leif Neland" > > Cc: ; > > Sent: Wednesday, November 29, 2000 2:10 AM > > Subject: Re: How to debug ppp > > > > > > > Well, I haven't seen this before !!! > > > > > > Your ISP is *insisting* that you negotiate a multi-link connection. > > > You can do this by simply adding > > > > > > set mrru 1506 > > > > > > to your config. > > > > > > > I sometimes have trouble connecting to my flat-rate isp via i4bsd. > > > > Most of the time it works, but sometimes the handshake fails. > > > > What is the log trying to tell me here? What can I tell my isp? > > > > > > > > When it fails, I can connect to another isp, which charges per minute > > > > charges, which I rather not use > > > > when I have flat rate. > > > > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: Phone: xxxxxxxxx > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: Connected! > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: opening -> dial > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: 1: Dial attempt 1 of 2 > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: dial -> carrier > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: /dev/i4brbch0: CD > > detected > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: carrier -> login > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: login -> lcp > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: FSM: Using "1" as a > > transport > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Initial --> > > > > Closed > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: Entering STOPPED state > > for > > > > 2 s > > > > econds > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Closed --> > > > > Stopped > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(1) state = > > > > Stopped > > > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > > 00:10:bc:06:fa:00 > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigReq(1) state = > > > > Stopped > > > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x0bde8bbc > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(1) state = > > > > Stopped > > > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: LayerStart > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change Stopped --> > > > > Req-Sent > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(2) state = > > > > Req-Sent > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > > 00:10:bc:06:fa:00 > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(2) state = > > > > Req-Sent > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > Looping: > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(3) state = > > > > Req-Sent > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > > 00:10:bc:06:fa:00 > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(3) state = > > > > Req-Sent > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > Until hangup > > > > > > > > Leif > > -- > 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 Tue Dec 5 15:42:57 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 15:42:55 2000 Return-Path: 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 52F9137B400 for ; Tue, 5 Dec 2000 15:42:55 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA19705; Tue, 5 Dec 2000 15:42:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eB5NgpM65812; Tue, 5 Dec 2000 15:42:51 -0800 (PST) (envelope-from obrien) Date: Tue, 5 Dec 2000 15:42:51 -0800 From: "David O'Brien" To: Hostas Red Cc: freebsd-current@freebsd.org Subject: Re: Problems in making world Message-ID: <20001205154251.A64895@dragon.nuxi.com> Reply-To: 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 kong@comset.net on Tue, Dec 05, 2000 at 11:06:12AM +0300 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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote: > I have a following problem in making world for some time already: ... > Any suggestions? rm -rf /usr/obj/* cd /usr/src && make cleandir update your /usr/src and try again To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 16: 2:37 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 16:02:26 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 1DCBD37B400 for ; Tue, 5 Dec 2000 16:02:22 -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 eB5Nu2M09827; Tue, 5 Dec 2000 23:56:02 GMT (envelope-from brian@hak.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 eB5Nwlo42561; Tue, 5 Dec 2000 23:58:47 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012052358.eB5Nwlo42561@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Leif Neland" Cc: "Brian Somers" , freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: How to debug ppp In-Reply-To: Message from "Leif Neland" of "Wed, 06 Dec 2000 00:30:11 +0100." <035201c05f13$5fea93c0$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Dec 2000 23:58:47 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you're probably stuck with either trying to convince your provider that their ppp implementation is wrong (it's ignoring ppp's rejects) or maybe trying to get the logs from a working ppp implementation that can connect to them. If you can get the logs, please send them to me and I'll see if I can make ppp do what they're doing..... > Didn't help: > > Dec 6 00:21:23 arnold ppp[56941]: tun0: Phase: bundle: Dead > Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: bundle: Establish > Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: closed -> opening > Dec 6 00:21:24 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:24 arnold ppp[56941]: tun0: Chat: Phone: 103333361333 > Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: Connected! > Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: opening -> dial > Dec 6 00:21:24 arnold ppp[56941]: tun0: Chat: 1: Dial attempt 1 of 2 > Dec 6 00:21:24 arnold ppp[56941]: tun0: Phase: 1: dial -> carrier > Dec 6 00:21:25 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: /dev/i4brbch0: CD > detected > Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: carrier -> login > Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: login -> lcp > Dec 6 00:21:25 arnold ppp[56941]: tun0: LCP: FSM: Using "1" as a transport > Dec 6 00:21:25 arnold ppp[56941]: tun0: LCP: 1: State change Initial --> > Closed > Dec 6 00:21:25 arnold ppp[56941]: tun0: Phase: 1: Entering STOPPED state > for 2 seconds > Dec 6 00:21:25 arnold ppp[56941]: tun0: LCP: 1: State change Closed --> > Stopped > Dec 6 00:21:26 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(2) state = > Stopped > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = > Stopped > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(2) state = > Stopped > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: LayerStart > Dec 6 00:21:26 arnold ppp[56941]: tun0: LCP: 1: State change Stopped --> > Req-Sent > Dec 6 00:21:27 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(3) state = > Req-Sent > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(3) state = > Req-Sent > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:27 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:28 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:29 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(4) state = > Req-Sent > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(4) state = > Req-Sent > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = > Req-Sent > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:29 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] > Dec 6 00:21:30 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(5) state = > Req-Sent > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(5) state = > Req-Sent > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:30 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:31 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:32 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(6) state = > Req-Sent > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(6) state = > Req-Sent > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = > Req-Sent > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:32 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] > Dec 6 00:21:33 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(7) state = > Req-Sent > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(7) state = > Req-Sent > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:33 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:34 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:35 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(8) state = > Req-Sent > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(8) state = > Req-Sent > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = > Req-Sent > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:35 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] > Dec 6 00:21:36 arnold ppp[56941]: tun0: TCP/IP: OUT ICMP: > 192.168.0.1:8 ---> 194.19.140.1:8 (36/84) > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(9) state = > Req-Sent > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(9) state = > Req-Sent > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:36 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: 1: RecvConfigReq(10) state = > Req-Sent > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0x01e25945 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: ENDDISC[9] MAC > 00:10:bc:06:fa:00 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: 1: SendConfigRej(10) state = > Req-Sent > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: PROTOCOMP[2] > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: ACFCOMP[2] > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: 1: SendConfigReq(1) state = > Req-Sent > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRU[4] 1500 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MAGICNUM[6] 0xc23c4361 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: MRRU[4] 1506 > Dec 6 00:21:38 arnold ppp[56941]: tun0: LCP: SHORTSEQ[2] > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Carrier lost > Dec 6 00:21:40 arnold ppp[56941]: tun0: LCP: 1: State change Req-Sent --> > Starting > Dec 6 00:21:40 arnold ppp[56941]: tun0: LCP: 1: LayerFinish > Dec 6 00:21:40 arnold ppp[56941]: tun0: LCP: 1: State change Starting --> > Initial > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Disconnected! > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: lcp -> logout > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Disconnected! > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: logout -> hangup > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: Connect time: 16 secs: > 351 octets in, 228 octets out > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: : 19 packets in, 29 > packets out > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: total 36 bytes/sec, peak 50 > bytes/sec on Wed Dec 6 00:21:40 2000 > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: 1: hangup -> closed > Dec 6 00:21:40 arnold ppp[56941]: tun0: Phase: bundle: Dead > > ----- Original Message ----- > From: "Brian Somers" > To: "Leif Neland" > Cc: "Brian Somers" ; ; > > Sent: Tuesday, December 05, 2000 11:40 PM > Subject: Re: How to debug ppp > > > > What happens if you ``disable acfcomp protocomp'' and ``deny acfcomp > > protocomp'' in your config ? > > > > This should be negotiable with isdn.... but perhaps our requesting it > > is upsetting the peer ? > > > > > It still doesn't work sometimes. > > > > > > I have a complete log (From dialing to hangup) at > > > http://www.neland.dk/arnold.log > > > My ppp.conf is at http://www.neland.dk/arnold.conf > > > > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC > > > 00:10:bc:06:fa:00 > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: LayerStart > > > Dec 5 22:28:28 arnold ppp[55986]: tun0: LCP: 1: State change > Stopped --> > > > Ack-Se > > > nt > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: RecvConfigReq(2) state > = > > > Ack-Se > > > nt > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MAGICNUM[6] 0xa14dc70c > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: PROTOCOMP[2] > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ACFCOMP[2] > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRRU[4] 1506 > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: ENDDISC[9] MAC > > > 00:10:bc:06:fa:00 > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: 1: SendConfigAck(2) state > = > > > Ack-Se > > > nt > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: MRU[4] 1500 > > > Dec 5 22:28:29 arnold ppp[55986]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > > > > > > ----- Original Message ----- > > > From: "Brian Somers" > > > To: "Leif Neland" > > > Cc: ; > > > Sent: Wednesday, November 29, 2000 2:10 AM > > > Subject: Re: How to debug ppp > > > > > > > > > > Well, I haven't seen this before !!! > > > > > > > > Your ISP is *insisting* that you negotiate a multi-link connection. > > > > You can do this by simply adding > > > > > > > > set mrru 1506 > > > > > > > > to your config. > > > > > > > > > I sometimes have trouble connecting to my flat-rate isp via i4bsd. > > > > > Most of the time it works, but sometimes the handshake fails. > > > > > What is the log trying to tell me here? What can I tell my isp? > > > > > > > > > > When it fails, I can connect to another isp, which charges per > minute > > > > > charges, which I rather not use > > > > > when I have flat rate. > > > > > > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: Phone: xxxxxxxxx > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: Connected! > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: opening -> dial > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Chat: 1: Dial attempt 1 of 2 > > > > > Nov 27 20:48:35 arnold ppp[7461]: tun0: Phase: 1: dial -> carrier > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: /dev/i4brbch0: CD > > > detected > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: carrier -> login > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: login -> lcp > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: FSM: Using "1" as a > > > transport > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change > Initial --> > > > > > Closed > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: Phase: 1: Entering STOPPED > state > > > for > > > > > 2 s > > > > > econds > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change > Closed --> > > > > > Stopped > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(1) > state = > > > > > Stopped > > > > > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 > (PAP) > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > > > 00:10:bc:06:fa:00 > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigReq(1) > state = > > > > > Stopped > > > > > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x0bde8bbc > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(1) > state = > > > > > Stopped > > > > > > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: LayerStart > > > > > Nov 27 20:48:36 arnold ppp[7461]: tun0: LCP: 1: State change > Stopped --> > > > > > Req-Sent > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(2) > state = > > > > > Req-Sent > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 > (PAP) > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > > > 00:10:bc:06:fa:00 > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(2) > state = > > > > > Req-Sent > > > > > Nov 27 20:48:37 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > > Looping: > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: RecvConfigReq(3) > state = > > > > > Req-Sent > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRU[4] 1500 > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: AUTHPROTO[4] 0xc023 > (PAP) > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MAGICNUM[6] 0x08f8f450 > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: PROTOCOMP[2] > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ACFCOMP[2] > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: ENDDISC[9] MAC > > > > > 00:10:bc:06:fa:00 > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: 1: SendConfigRej(3) > state = > > > > > Req-Sent > > > > > Nov 27 20:48:38 arnold ppp[7461]: tun0: LCP: MRRU[4] 1506 > > > > > Until hangup > > > > > > > > > > Leif -- 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 Tue Dec 5 16:20:45 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 16:20:43 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 5BFD937B400 for ; Tue, 5 Dec 2000 16:20:42 -0800 (PST) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.1/8.11.1) id eB60Kdq71427; Tue, 5 Dec 2000 19:20:39 -0500 (EST) (envelope-from morganw) Date: Tue, 5 Dec 2000 19:20:38 -0500 (EST) From: Wesley Morgan To: current@freebsd.org Subject: this just in: kernel broken 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 Source from latest cvs. World builds A-OK, kernel bombs, looks like it needs to include sys/lock.h: cc -c -O -pipe -mpentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 ../../kern/kern_synch.c ../../kern/kern_synch.c: In function `schedcpu': ../../kern/kern_synch.c:289: warning: implicit declaration of function `lockmgr' ../../kern/kern_synch.c:289: `LK_SHARED' undeclared (first use in this function) ../../kern/kern_synch.c:289: (Each undeclared identifier is reported only once ../../kern/kern_synch.c:289: for each function it appears in.) ../../kern/kern_synch.c:349: `LK_RELEASE' undeclared (first use in this function) *** Error code 1 -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 16:34:18 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 16:34:15 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 3827E37B400 for ; Tue, 5 Dec 2000 16:34:15 -0800 (PST) Received: from laptop.baldwin.cx (root@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB60Xb760779; Tue, 5 Dec 2000 16:33:37 -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, 05 Dec 2000 16:34:19 -0800 (PST) From: John Baldwin To: Wesley Morgan Subject: RE: this just in: kernel broken Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-00 Wesley Morgan wrote: > > Source from latest cvs. World builds A-OK, kernel bombs, looks like it > needs to include sys/lock.h: Doh, I forgot to do this, my bad. -- 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 Dec 5 19: 4:16 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 19:04:13 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 4EF9837B400 for ; Tue, 5 Dec 2000 19:04:13 -0800 (PST) Received: from ix.netcom.com (sil-wa16-20.ix.netcom.com [207.93.148.148]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA11733 for ; Tue, 5 Dec 2000 22:04:10 -0500 (EST) Received: (from tomdean@localhost) by ix.netcom.com (8.11.1/8.9.3) id eB632ZN28189; Tue, 5 Dec 2000 19:02:35 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Date: Tue, 5 Dec 2000 19:02:35 -0800 (PST) Message-Id: <200012060302.eB632ZN28189@ix.netcom.com> From: "Thomas D. Dean" To: current@FreeBSD.ORG Subject: Make World Time Format Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to go back to the old style of reporting world time in Makefile? I have been collecting make time stats. This is where the last 3 lines of the output are: -------------------------------------------------------------- >>> elf make world started on Thu Aug 31 09:47:50 PDT 2000 >>> elf make world completed on Thu Aug 31 17:44:08 PDT 2000 -------------------------------------------------------------- tomdean diff -c Makefile~ Makefile *** Makefile~ Tue Dec 5 18:57:41 2000 --- Makefile Tue Dec 5 18:56:31 2000 *************** *** 109,116 **** # success, regardless of how old your existing system is. # world: upgrade_checks @echo "--------------------------------------------------------------" ! @echo ">>> ${OBJFORMAT} make world started on `LC_TIME=C date`" @echo "--------------------------------------------------------------" .if target(pre-world) @echo --- 109,117 ---- # success, regardless of how old your existing system is. # world: upgrade_checks + WORLD_START="`LC_TIME=C date`" @echo "--------------------------------------------------------------" ! @echo ">>> ${OBJFORMAT} make world started on ${WORLD_START}" @echo "--------------------------------------------------------------" .if target(pre-world) @echo *************** *** 130,135 **** --- 131,137 ---- .endif @echo @echo "--------------------------------------------------------------" + @echo ">>> ${OBJFORMAT} make world started on ${WORLD_START}" @echo ">>> ${OBJFORMAT} make world completed on `LC_TIME=C date`" @echo "--------------------------------------------------------------" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 20:36:23 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 20:36:21 2000 Return-Path: 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 B7CD337B400 for ; Tue, 5 Dec 2000 20:36:21 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id UAA21420; Tue, 5 Dec 2000 20:36:20 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eB64aJw03076; Tue, 5 Dec 2000 20:36:19 -0800 (PST) (envelope-from obrien) Date: Tue, 5 Dec 2000 20:36:19 -0800 From: "David O'Brien" To: "Thomas D. Dean" Cc: current@FreeBSD.ORG Subject: Re: Make World Time Format Message-ID: <20001205203619.A3056@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <200012060302.eB632ZN28189@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012060302.eB632ZN28189@ix.netcom.com>; from tomdean@ix.netcom.com on Tue, Dec 05, 2000 at 07:02: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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 05, 2000 at 07:02:35PM -0800, Thomas D. Dean wrote: > Is it possible to go back to the old style of reporting world time in > Makefile? I have been collecting make time stats. I added it back, but in a way I think will not be objectionable for the reason it was removed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 21:25: 3 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 21:24:57 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.iconz.co.nz (etrn.iconz.co.nz [210.48.22.36]) by hub.freebsd.org (Postfix) with ESMTP id 4A46837B69C; Tue, 5 Dec 2000 21:24:56 -0800 (PST) Received: from creativejuice.co.nz (ip-210-48-60-242.iconz.net.nz [210.48.60.242] (may be forged)) by mail.iconz.co.nz (8.9.3/8.9.3) with ESMTP id SAA043700976080139; Wed, 6 Dec 2000 18:22:19 +1300 (NZDT) From: tom@aba.com Message-Id: <200012060522.SAA043700976080139@mail.iconz.co.nz> Received: from [62.159.146.73] by [192.168.1.2] with SMTP (QuickMail Pro Server for Mac 2.0.1); 06-Dec-2000 18:23:08 +1300 To: Subject: Search Engine Optimization Kit-2001 24123 Date: Wed, 06 Dec 2000 00:16:29 -0500 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 1 X-MSMail-Priority: High Errors-To: X-Mailer: Outlook Express X-Originating-IP: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG
Get Top 10 Positions With The Search Engine Optimization Kit-2001

No hype ... no gimmicks ... just the facts ... and only $59!

Hello Friend,

We created the Search Engine Optimization Kit-2001 to achieve high positions in search engines. This unique Kit includes:
  • Detailed information about how search engines work,

  • Step-by-step instructions to create, high-ranking,"search-= engine-friendly" pages,

  • All the tools and resources you need to create pages, submit to= engines and track your placements, and

  • Ongoing personal support by email and phone.

Click to receive Free In= formation about Search Engines and the Kit, or call direct to 937-640-2762.

We reply promptly to all inquires.

Dr. Jerry R. Perrich, Director
The Internet Marketing Institute, Inc.
Helping You Be Successful Online
937-640-2762


PS - Please forward this email to any of your business associates or friends who may benefit from it.

REMOVAL INSTRUCTIONS=
Per federal legislation, you can be removed from this mailing list at no c= ost to you by simply clicking here Remove Ple= ase. You will be promptly removed. Please note that interfering with this feder= ally approved method of removal will deny others the opportunity to be removed.

<= p>

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 5 22:24: 8 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 22:24:06 2000 Return-Path: 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 C821037B400 for ; Tue, 5 Dec 2000 22:24:05 -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 eB66NpM52198; Tue, 5 Dec 2000 22:23:51 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: current@FreeBSD.ORG Cc: "Thomas D. Dean" Subject: Re: Make World Time Format In-Reply-To: Message from "David O'Brien" of "Tue, 05 Dec 2000 20:36:19 PST." <20001205203619.A3056@dragon.nuxi.com> Date: Tue, 05 Dec 2000 22:23:51 -0800 Message-ID: <52195.976083831@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, good compromise. > On Tue, Dec 05, 2000 at 07:02:35PM -0800, Thomas D. Dean wrote: > > Is it possible to go back to the old style of reporting world time in > > Makefile? I have been collecting make time stats. > > I added it back, but in a way I think will not be objectionable for the > reason it was removed. > > > > 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 Tue Dec 5 22:33:33 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 5 22:33:31 2000 Return-Path: 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 91FE137B400; Tue, 5 Dec 2000 22:33:31 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id WAA10458; Tue, 5 Dec 2000 22:34:47 -0800 Date: Tue, 5 Dec 2000 22:34:47 -0800 From: kris@citusc.usc.edu To: Warner Losh Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: wall/rwall cleanups Message-ID: <20001205223447.A10388@citusc.usc.edu> References: <20001125215912.A15309@citusc17.usc.edu> <200011282157.OAA13412@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200011282157.OAA13412@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 28, 2000 at 02:57:45PM -0700, Warner Losh wrote: > In message <20001125215912.A15309@citusc17.usc.edu> Kris Kennaway writes: > : Please review. This syncs up our code with some NetBSD changes, as well > : as attempting to sync rwall up with wall. > > You might also want to bruing in the openBSD changes for wall -g. I thought that was your project ;-) > Plus a few nits: > + char *tty, hostname[MAXHOSTNAMELEN], lbuf[256], tmpname[64]; > > tmpname should be tmpname[MAXPATHLEN] since it is a path. Note well, > not MAXPATHLEN + 1 since MAXPATHLEN is defined to include the trailing > NUL (I have patches in my tree that fix this for the rest of the tree, > at least the +1 issue, other issues will have to wait until I can > audit all strings passed to open, mktemp, et al). Yeah..I pondered doing that, but it's used to store a #define'd string so I didn't worry about it too much. Since I'm out of touch, feel free to do this yourself before I get back. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 0:28:48 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 00:28:45 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id E7B5437B400; Wed, 6 Dec 2000 00:28:31 -0800 (PST) Received: from mail2.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id RAA25583; Wed, 6 Dec 2000 17:28:30 +0900 (JST) Received: from localhost.FromTo.Cc (shell [202.247.191.98]) by mail2.rim.or.jp (8.9.3/3.7W) id RAA17607; Wed, 6 Dec 2000 17:28:29 +0900 (JST) Date: Wed, 06 Dec 2000 17:28:28 +0900 Message-ID: <86g0k2q7gz.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: current@FreeBSD.org Cc: hosokawa@FreeBSD.org Subject: Progress report: Multilingual sysinstall for -current User-Agent: Wanderlust/1.1.0 (Overjoyed) 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: hosokawa@itc.keio.ac.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I've ported Multilingual sysinstall to -current. I put the latest source and binaries (Japanese/Englush only) is at http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ (please note that non-English docuemnt files are based on 4.2-RELEASE) Currently, this implementation supports Japanese, Korean, Traditional Chinese, and Russian. The status of translation work is: Japanese: finished Korean: finished Traditional Chinese: about to finish Russian: only *.hlp files have been translated This code has some minor problems, but it works. I think it's better to change the development of this project to open style. I would like to import this code to -current CVS repositry soon if there's no objections. FYI: for 4.2-RELEASE, http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001205-1/ contains source, and binaries for all supported languages. -- Tatsumi Hosokawa http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 1:46:11 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 01:46:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 1C3DB37B400; Wed, 6 Dec 2000 01:46:08 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id AA724573E3; Wed, 6 Dec 2000 03:46:25 -0600 (CST) Date: Wed, 6 Dec 2000 03:46:25 -0600 From: "Michael C . Wu" To: Tatsumi Hosokawa Cc: current@FreeBSD.org Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001206034625.A40075@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <86g0k2q7gz.wl@ringo.FromTo.Cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <86g0k2q7gz.wl@ringo.FromTo.Cc>; from hosokawa@FreeBSD.org on Wed, Dec 06, 2000 at 05:28:28PM +0900 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | I've ported Multilingual sysinstall to -current. I put the latest | source and binaries (Japanese/Englush only) is at | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | (please note that non-English docuemnt files are based on 4.2-RELEASE) | | Currently, this implementation supports Japanese, Korean, Traditional | Chinese, and Russian. The status of translation work is: | | Japanese: finished | Korean: finished | Traditional Chinese: about to finish | Russian: only *.hlp files have been translated | | This code has some minor problems, but it works. I think it's better | to change the development of this project to open style. I would like | to import this code to -current CVS repositry soon if there's no | objections. As we wait for libh development, I do not think we should exert efforts to try for another solution. This tends to allow for slack in further development of better products. A good example would be a proposal by Alfred Pernstein to slightly modify RELENG_4 SMP for the duration of SMPNG development. The proposal was not well accepted due to the reason I stated above. We really should concentrate on libh as a complete and _clean_ solution. In addition, the purpose of putting localized sysinstall in -CURRENT is rather dubious. -CURRENT/HEAD is a developers' branch, people who use this branch should be able to read English and the system error messages. If they cannot install the system with English sysinstall, I would have doubts on their programming and testing ability. People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. I would have no objections to L10N'ized sysinstall being maintained in the same way that PAO is maintained. The boot floppies and iso images can be put up somewhere for download, and maintained in RELENG_4. Normally, I would welcome any I18N/L10N efforts in FreeBSD. However, the FreeBSD Project's official position paraphrased is "If you don't know what to do with -CURRENT, don't install it." Combined with the point that we should not divert efforts from libh, I hold the opinion that we should not import this. Finally, still many thanks and applause to Tatsumi and others for this work. | FYI: for 4.2-RELEASE, | http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001205-1/ | contains source, and binaries for all supported languages. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 2:30:35 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 02:30:32 2000 Return-Path: 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 855E037B400; Wed, 6 Dec 2000 02:30:32 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eB6AULI21608; Wed, 6 Dec 2000 02:30:21 -0800 (PST) Date: Wed, 6 Dec 2000 02:30:21 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: Tatsumi Hosokawa , current@FreeBSD.ORG Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001206023020.X8051@fw.wintelcom.net> References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001206034625.A40075@peorth.iteration.net>; from keichii@iteration.net on Wed, Dec 06, 2000 at 03:46:25AM -0600 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [001206 01:46] wrote: > On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: > | I've ported Multilingual sysinstall to -current. I put the latest > | source and binaries (Japanese/Englush only) is at > | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ > | (please note that non-English docuemnt files are based on 4.2-RELEASE) > | > | Currently, this implementation supports Japanese, Korean, Traditional > | Chinese, and Russian. The status of translation work is: > | > | Japanese: finished > | Korean: finished > | Traditional Chinese: about to finish > | Russian: only *.hlp files have been translated > | > | This code has some minor problems, but it works. I think it's better > | to change the development of this project to open style. I would like > | to import this code to -current CVS repositry soon if there's no > | objections. > > As we wait for libh development, I do not think we should exert > efforts to try for another solution. This tends to allow for > slack in further development of better products. No, this motivates those working for a greater good to produce more than just promises of what's to come. > A good example would be a proposal by Alfred Pernstein to slightly > modify RELENG_4 SMP for the duration of SMPNG development. The proposal > was not well accepted due to the reason I stated above. The proposal was only rejected as something that wasn't going to be the be all and end all of our threading system. As a middle ground it would have many advantages over what's currently in place. The same applies here. Sure libh is supposed to be an order of magnitude better than internationalized sysinstall, but at the current time libh is as much vapourware as KSEs are. > We really should concentrate on libh as a complete and _clean_ solution. Yes, and no, you should continue doing so, and I have high hopes that it's the best installer system ever, however an interm solution would be a great way to attract new users and developers. > In addition, the purpose of putting localized sysinstall in -CURRENT > is rather dubious. -CURRENT/HEAD is a developers' branch, people > who use this branch should be able to read English and the system > error messages. If they cannot install the system with English > sysinstall, I would have doubts on their programming and testing ability. > > People who run -CURRENT should be able to read and write English to > understand the code comments, report bugs, and post to the lists in English. Why? It's my native tongue and even I have issues on occasion with comments and manpage additions that forieners correct (Bruce, Eivind, Asmodai and Sheldon to name a few.) Having a problem with english doesn't make anyone less of an intellectual. > I would have no objections to L10N'ized sysinstall being maintained in > the same way that PAO is maintained. The boot floppies and iso images > can be put up somewhere for download, and maintained in RELENG_4. Maybe after libh is released... since you guys aren't basing your work on sysinstall, it's not like you'd have to deal with a code merger. > Normally, I would welcome any I18N/L10N efforts in FreeBSD. > However, the FreeBSD Project's official position paraphrased is > "If you don't know what to do with -CURRENT, don't install it." > Combined with the point that we should not divert efforts from libh, > I hold the opinion that we should not import this. I think it should be brought in and quickly MFC'd for the next 4.3 release. I see no conflict between these two efforts and since one seems pretty much completed, I'd like to see it in the base system. -- -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 Wed Dec 6 2:53:48 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 02:53:45 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 21CA837B400; Wed, 6 Dec 2000 02:53:45 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 5B4DF573E6; Wed, 6 Dec 2000 04:54:02 -0600 (CST) Date: Wed, 6 Dec 2000 04:54:02 -0600 From: "Michael C . Wu" To: Alfred Perlstein Cc: Tatsumi Hosokawa , current@FreeBSD.ORG Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001206045402.A40657@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> <20001206023020.X8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001206023020.X8051@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Dec 06, 2000 at 02:30:21AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 02:30:21AM -0800, Alfred Perlstein scribbled: | * Michael C . Wu [001206 01:46] wrote: | > On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | > | I've ported Multilingual sysinstall to -current. I put the latest | > | source and binaries (Japanese/Englush only) is at | > | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | > | (please note that non-English docuemnt files are based on 4.2-RELEASE) | > | | > | Currently, this implementation supports Japanese, Korean, Traditional | > | Chinese, and Russian. The status of translation work is: | > | | > | Japanese: finished | > | Korean: finished | > | Traditional Chinese: about to finish | > | Russian: only *.hlp files have been translated | > | | > | This code has some minor problems, but it works. I think it's better | > | to change the development of this project to open style. I would like | > | to import this code to -current CVS repositry soon if there's no | > | objections. | > | > As we wait for libh development, I do not think we should exert | > efforts to try for another solution. This tends to allow for | > slack in further development of better products. | | No, this motivates those working for a greater good to produce | more than just promises of what's to come. [snip] | > People who run -CURRENT should be able to read and write English to | > understand the code comments, report bugs, and post to the lists in English. | | Why? It's my native tongue and even I have issues on occasion with | comments and manpage additions that forieners correct (Bruce, Eivind, | Asmodai and Sheldon to name a few.) Having a problem with english | doesn't make anyone less of an intellectual. | | > I would have no objections to L10N'ized sysinstall being maintained in | > the same way that PAO is maintained. The boot floppies and iso images | > can be put up somewhere for download, and maintained in RELENG_4. | | Maybe after libh is released... since you guys aren't basing your | work on sysinstall, it's not like you'd have to deal with a code | merger. | This is not about a code merge, this is about how we will support users who use this stuff. If we want to do this, we need to have a centralized support system/mailing lists, instead of the currently very segmented local support systems. I would have no objections if we can figure out a way to support this in a bug reporting system, mailing lists. But I agree you are right, we could use this in 4.x. Perhaps I did not think this one thoroughly. | I think it should be brought in and quickly MFC'd for the next | 4.3 release. | | I see no conflict between these two efforts and since one seems | pretty much completed, I'd like to see it in the base system. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 3:18:29 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 03:18:25 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 6EEC237B400; Wed, 6 Dec 2000 03:18:24 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:6ays7jJxqlxC9X3Jj30yT97pdFkLq7tz@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.11.0/3.7Wpl2) with ESMTP id eB6BIDo25665; Wed, 6 Dec 2000 20:18:14 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:pzNZvyFdambqzERUhIqmGo/ZO9tLDi7p@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id UAA27235; Wed, 6 Dec 2000 20:25:31 +0900 (JST) Message-Id: <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp> To: "Michael C . Wu" Cc: Tatsumi Hosokawa , current@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Progress report: Multilingual sysinstall for -current In-reply-to: Your message of "Wed, 06 Dec 2000 03:46:25 CST." <20001206034625.A40075@peorth.iteration.net> References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> Date: Wed, 06 Dec 2000 20:25:30 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >As we wait for libh development, I do not think we should exert >efforts to try for another solution. This tends to allow for >slack in further development of better products. >A good example would be a proposal by Alfred Pernstein to slightly >modify RELENG_4 SMP for the duration of SMPNG development. The proposal >was not well accepted due to the reason I stated above. > >We really should concentrate on libh as a complete and _clean_ solution. Sure, libh is a better solution. But, don't you think it's still good to have something working until it will become available. >In addition, the purpose of putting localized sysinstall in -CURRENT >is rather dubious. -CURRENT/HEAD is a developers' branch, people >who use this branch should be able to read English and the system >error messages. If they cannot install the system with English >sysinstall, I would have doubts on their programming and testing ability. > >People who run -CURRENT should be able to read and write English to >understand the code comments, report bugs, and post to the lists in English. I think you are missing the point here. As you point out, the -current is for developers; it's for development and for testing. I don't think Tatsumi wants -current users to use I18N sysinstall to install -current, but, rather wants them to have a look at the code and test it. >I would have no objections to L10N'ized sysinstall being maintained in >the same way that PAO is maintained. The boot floppies and iso images >can be put up somewhere for download, and maintained in RELENG_4. Why should it be in RELENG_4? If it's maintained in -current and regularly MFCed to RELENG_4, it is exposed to wide audience of -current developers and -stable users. That will attract more comments and bug reports, and will also minimize the delay between regular releases of FreeBSD and I18N/L10N sysinstall for them; the delay normally associated with L10N sysinstall (and PAO) after regular FreeBSD releases. >Normally, I would welcome any I18N/L10N efforts in FreeBSD. >However, the FreeBSD Project's official position paraphrased is >"If you don't know what to do with -CURRENT, don't install it." See my comments above. >Combined with the point that we should not divert efforts from libh, >I hold the opinion that we should not import this. I don't think importing multilingual sysinstall will detract effort from libh. You see, even if it is maintained separately from the -current, it has its own maintainers and developers. I expect they are the same people who will maintain and develop I18N sysinstall when it is imported to the -current. They may or may not be libh developers at the same time. But, I don't think I18N sysinstall is suddenly needing a large army of developers and will steal them from the libh developer base. >Finally, still many thanks and applause to Tatsumi and others >for this work. The same from me to them too. Kazu >| FYI: for 4.2-RELEASE, >| http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001205-1/ >| contains source, and binaries for all supported languages. > > >-- >+------------------------------------------------------------------+ >| keichii@peorth.iteration.net | keichii@bsdconspiracy.net | >| http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | >+------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 5:24:24 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 05:24:22 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from crucian.comset.net (crucian.comset.net [213.172.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 0422F37B400; Wed, 6 Dec 2000 05:24:20 -0800 (PST) Received: from localhost (kong@localhost) by crucian.comset.net (8.11.1/8.8.7) with ESMTP id eB6DOAZ07381; Wed, 6 Dec 2000 16:24:10 +0300 (MSK) Date: Wed, 6 Dec 2000 16:24:09 +0300 (MSK) From: Hostas Red To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems in making world In-Reply-To: <20001205154251.A64895@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 Hi! On Tue, 5 Dec 2000, David O'Brien wrote: > On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote: > > I have a following problem in making world for some time already: > ... > > Any suggestions? > > rm -rf /usr/obj/* > cd /usr/src && make cleandir > update your /usr/src and try again Yes, that helped, thank You. I did the 'rm -rf /usr/obj/*' several times, but didn't 'make cleandir'... And I'm cvsup'ing automatically once a day, so that wasn't a problem ;) Adios, /KONG ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 6:37:27 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 06:37:22 2000 Return-Path: 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 77DE737B400; Wed, 6 Dec 2000 06:37:21 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id PAA10667; Wed, 6 Dec 2000 15:37:20 +0100 (MET) Date: Wed, 6 Dec 2000 15:37:19 +0100 (CET) From: Harti Brandt To: hackers@freebsd.org, current@freebsd.org Subject: ATM broken 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 Hi, the ATM stuff in /sys/dev/h{e,f}a and /sys/netatm seems to be seriously broken in current. A simple 'atm show config' command leads to a kernel panic. I have tracked down the problem (and had to learn, that bzero is a function pointer rather than a function on i386). I cannot track, how the problem was introduced, but it appears to be somehow connected to phk's header file reorganisation in the ATM code in october. Many of the files miss a include and give a missing prototyp warning for functions like splnet, printf, log, bzero... This appears to be deadly for bzero(), because this is a function pointer now. (I always had the fealing, that the ANSI-C syntax for calling functions through pointers is bad ( fooptr() instead of (*fooptr)()). Now I know why :-( ) Adding a #include to the following files seem to fix the problem: dev/hea/eni_intr.c dev/hea/eni_vcm.c netatm/atm_if.c netatm/atm_signal.c netatm/atm_socket.c netatm/atm_usrreq.c netatm/ipatm/ipatm_event.c netatm/ipatm/ipatm_if.c netatm/ipatm/ipatm_load.c netatm/ipatm/ipatm_output.c netatm/ipatm/ipatm_vcm.c netatm/spans/spans_cls.c netatm/spans/spans_subr.c netatm/uni/sscf_uni.c netatm/uni/sscf_uni_lower.c netatm/uni/sscf_uni_upper.c netatm/uni/sscop.c netatm/uni/sscop_lower.c netatm/uni/sscop_subr.c netatm/uni/sscop_upper.c netatm/uni/uni_load.c netatm/uni/uniarp_input.c netatm/uni/uniarp_output.c netatm/uni/uniarp_vcm.c netatm/uni/unisig_encode.c netatm/uni/unisig_mbuf.c netatm/uni/unisig_msg.c netatm/uni/unisig_print.c netatm/uni/unisig_proto.c netatm/uni/unisig_sigmgr_state.c Regards, 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 Wed Dec 6 7:26:49 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 07:26:45 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from afs.itc.keio.ac.jp (afs.itc.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with SMTP id B056C37B400 for ; Wed, 6 Dec 2000 07:26:44 -0800 (PST) Received: (qmail 4762 invoked from network); 6 Dec 2000 15:26:35 -0000 Received: from pppb10.yk.rim.or.jp (HELO localhost.FromTo.Cc) (202.247.186.110) by afs.itc.keio.ac.jp with SMTP; 6 Dec 2000 15:26:35 -0000 Date: Thu, 07 Dec 2000 00:26:39 +0900 Message-ID: <86zoi91sgg.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: keichii@peorth.iteration.net, hosokawa@FreeBSD.org, current@FreeBSD.org Subject: Re: Progress report: Multilingual sysinstall for -current In-Reply-To: In your message of "Wed, 06 Dec 2000 20:25:30 +0900" <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp> References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp> User-Agent: Wanderlust/1.1.0 (Overjoyed) 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 At Wed, 06 Dec 2000 20:25:30 +0900, Kazutaka YOKOTA wrote: > > >As we wait for libh development, I do not think we should exert > >efforts to try for another solution. This tends to allow for > >slack in further development of better products. > >A good example would be a proposal by Alfred Pernstein to slightly > >modify RELENG_4 SMP for the duration of SMPNG development. The proposal > >was not well accepted due to the reason I stated above. > > > >We really should concentrate on libh as a complete and _clean_ solution. > > Sure, libh is a better solution. But, don't you think it's still good > to have something working until it will become available. Multilingual sysinstall project started when FreeBSD is 2.0.5, and maintained in PAO-like style, but it's very larger patch than PAO (especially, it replaces almost all messages in release/sysinstall/menus.c) and it makes that "keeping current" work very difficult. Almost all code of this project is written when FreeBSD is 2.x, and it's in "maintainance-only" phase for years. If it's on -current tree, our work can be easier, and many developpers other than us also can do this work. If this makes us the spare time, perhaps we can help libh work. I don't think sysinstall is better solution, but it's available now. I'll glad to cvs delete this code entirely, if we can use better solution. > >In addition, the purpose of putting localized sysinstall in -CURRENT > >is rather dubious. -CURRENT/HEAD is a developers' branch, people > >who use this branch should be able to read English and the system > >error messages. If they cannot install the system with English > >sysinstall, I would have doubts on their programming and testing ability. > > > >People who run -CURRENT should be able to read and write English to > >understand the code comments, report bugs, and post to the lists in English. > > I think you are missing the point here. As you point out, the -current > is for developers; it's for development and for testing. I don't > think Tatsumi wants -current users to use I18N sysinstall to install > -current, but, rather wants them to have a look at the code and test > it. My main target is RELENG_4 and I hope this won't live until 5.x-RELEASE. It's in -current for only testing purpose. > >I would have no objections to L10N'ized sysinstall being maintained in > >the same way that PAO is maintained. The boot floppies and iso images > >can be put up somewhere for download, and maintained in RELENG_4. > > Why should it be in RELENG_4? If it's maintained in -current and > regularly MFCed to RELENG_4, it is exposed to wide audience of > -current developers and -stable users. That will attract more > comments and bug reports, and will also minimize the delay between > regular releases of FreeBSD and I18N/L10N sysinstall for them; the > delay normally associated with L10N sysinstall (and PAO) after regular > FreeBSD releases. And the delay has been prolonged sometimes because only a few developper was busy :-). > >Normally, I would welcome any I18N/L10N efforts in FreeBSD. > >However, the FreeBSD Project's official position paraphrased is > >"If you don't know what to do with -CURRENT, don't install it." > > See my comments above. > > >Combined with the point that we should not divert efforts from libh, > >I hold the opinion that we should not import this. > > I don't think importing multilingual sysinstall will detract effort > from libh. You see, even if it is maintained separately from the > -current, it has its own maintainers and developers. I expect they > are the same people who will maintain and develop I18N sysinstall when > it is imported to the -current. They may or may not be libh > developers at the same time. But, I don't think I18N sysinstall is > suddenly needing a large army of developers and will steal them from > the libh developer base. Yes. Programmers are needed when some change in source tree break this code and we can find it easier if it's in -current tree. Otherwise, only translators are needed for maintainance of *.TXT, *.hlp, and catalog files. > >Finally, still many thanks and applause to Tatsumi and others > >for this work. > > The same from me to them too. Thank you ! hosokawa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 8:27: 4 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 08:27:01 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [206.162.201.61]) by hub.freebsd.org (Postfix) with SMTP id C3AFA37B400 for ; Wed, 6 Dec 2000 08:27:00 -0800 (PST) Received: (qmail 45134 invoked by uid 1000); 6 Dec 2000 16:27:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Dec 2000 16:27:09 -0000 Date: Wed, 6 Dec 2000 11:27:09 -0500 (EST) From: Valentin Chopov To: freebsd-current@freebsd.org Subject: asm error in compiling SMP kernel 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 got this one this time. Val cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -march=i686 -mpreferred-stack-boundary=2 ../../cam/cam_periph.c ../../cam/cam_periph.c: In function `cam_periph_unmapmem': ../../cam/cam_periph.c:687: internal error--unrecognizable insn: (insn/i 287 1124 288 (parallel[ (set (mem/s/v:SI (plus:SI (reg:SI 0 %eax) (const_int 284 [0x11c])) 0) (asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl %2; pushl %3; call mtx_exit_hard; addl $8,%%esp;1:# exitlock_norecurse") ("=m") 0[ (const_int 0 [0x0]) (reg/v:SI 4 %esi) (reg:SI 5 %edi) (mem/s/v:SI (plus:SI (reg:SI 3 %ebx) (const_int 284 [0x11c])) 0) (reg:SI 0 %eax) ] [ (asm_input:SI ("gi")) (asm_input:SI ("g")) (asm_input:SI ("r")) (asm_input:SI ("0")) (asm_input:SI ("1")) ] ("../../sys/mutex.h") 601)) (set (reg:SI 0 %eax) (asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl %2; pushl %3; call mtx_exit_hard; addl $8,%%esp;1:# exitlock_norecurse") ("=a") 1[ (const_int 0 [0x0]) (reg/v:SI 4 %esi) (reg:SI 5 %edi) (mem/s/v:SI (plus:SI (reg:SI 3 %ebx) (const_int 284 [0x11c])) 0) (reg:SI 0 %eax) ] [ (asm_input:SI ("gi")) (asm_input:SI ("g")) (asm_input:SI ("r")) (asm_input:SI ("0")) (asm_input:SI ("1")) ] ("../../sys/mutex.h") 601)) (clobber (reg:QI 1 %dl)) (clobber (reg:QI 2 %cl)) (clobber (mem:BLK (scratch) 0)) ] ) -1 (insn_list 286 (nil)) (nil)) *** Error code 1 Stop in /usr/src/sys/compile/SQUID. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 9: 1: 3 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 09:01:01 2000 Return-Path: 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 8C20537B400 for ; Wed, 6 Dec 2000 09:01:01 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA24252; Wed, 6 Dec 2000 09:01:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eB6H0xY02309; Wed, 6 Dec 2000 09:00:59 -0800 (PST) (envelope-from obrien) Date: Wed, 6 Dec 2000 09:00:59 -0800 From: "David O'Brien" To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001206090059.C2205@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> <20001206023020.X8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001206023020.X8051@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Dec 06, 2000 at 02:30:21AM -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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 02:30:21AM -0800, Alfred Perlstein wrote: > magnitude better than internationalized sysinstall, but at the > current time libh is as much vapourware as KSEs are. No, KSE has paid developers working on it. When was the last cycle spent on libh? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 9:44:29 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 09:44:25 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from daemon.kr.freebsd.org (unknown [211.176.62.31]) by hub.freebsd.org (Postfix) with ESMTP id 78C5037B400; Wed, 6 Dec 2000 09:44:24 -0800 (PST) Received: from gnomaniac.myhome ([211.178.105.187]) by daemon.kr.freebsd.org (8.11.1/8.11.0) with ESMTP id eB6HhlF09072; Thu, 7 Dec 2000 02:43:47 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) Received: (from cjh@localhost) by gnomaniac.myhome (8.11.1/8.11.1) id eB6HgCO02202; Thu, 7 Dec 2000 02:42:13 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) X-Authentication-Warning: gnomaniac.myhome: cjh set sender to cjh@kr.FreeBSD.org using -f Sender: cjh@kr.FreeBSD.ORG To: Tatsumi Hosokawa Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, keichii@peorth.iteration.net, hosokawa@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Progress report: Multilingual sysinstall for -current References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp> <86zoi91sgg.wl@ringo.FromTo.Cc> From: CHOI Junho Date: 07 Dec 2000 02:42:11 +0900 In-Reply-To: Tatsumi Hosokawa's message of "Thu, 07 Dec 2000 00:26:39 +0900" Message-ID: <86lmttzbt8.fsf@gnomaniac.myhome> Lines: 40 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "TH" == Tatsumi Hosokawa writes: TH> Multilingual sysinstall project started when FreeBSD is 2.0.5, and TH> maintained in PAO-like style, but it's very larger patch than PAO TH> (especially, it replaces almost all messages in TH> release/sysinstall/menus.c) and it makes that "keeping current" work TH> very difficult. Almost all code of this project is written when TH> FreeBSD is 2.x, and it's in "maintainance-only" phase for years. I am working for translating sysinstall messages, release notes and help files to Korean for 4 years, from 2.2.1-RELEASE. I would be very happy if it will be included in -current and RELENG_4 system. Sometimes the release of I18N sysinstall(and former PAO) was delayed until next release, so if we can release I18N sysinstall timely for each release, it would help non-english users for FreeBSD very much. No other linux or BSD distribution(except localized ones) has such installer. It is very attractive thing for novice FreeBSD users to install in their mother tongue, even if he can understand English. And until libh is really working(hopefully 5.0-RELEASE?), I18N sysinstall is a good alternative. If we have it in -current, it would be relatively easy for debug and improve. I18N sysinstall still have a few bugs to be fixed although Tatsumi and other some CJK developers work. > Finally, still many thanks and applause to Tatsumi and others > for this work. > > The same from me to them too. Me too! TH> Thank you ! -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [now sleeping] [when sleeping] Korea FreeBSD Users Group/www.kr.FreeBSD.org Web Data Bank/www.wdb.co.kr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 10: 3:38 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 10:03:36 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 0FF5F37B400; Wed, 6 Dec 2000 10:03:32 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.10.0) with ESMTP id eB6I3TL07569; Wed, 6 Dec 2000 13:03:29 -0500 (EST) Date: Wed, 6 Dec 2000 13:03:29 -0500 (EST) From: Trevor Johnson To: "Michael C . Wu" Cc: Tatsumi Hosokawa , Subject: Re: Progress report: Multilingual sysinstall for -current In-Reply-To: <20001206034625.A40075@peorth.iteration.net> 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 > People who run -CURRENT should be able to read and write English to > understand the code comments, report bugs, and post to the lists in English. > "If you don't know what to do with -CURRENT, don't install it." You seem to be working from the assumption that people who understand English can't understand any other language. I don't know anything about the design question you raise, except that code which has not yet been written always seems more perfect than that which has. :-) -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 10: 9:54 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 10:09:46 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from nsv1005.zaq.ne.jp (nsv1005.zaq.ne.jp [210.224.35.10]) by hub.freebsd.org (Postfix) with SMTP id A28B737B401 for ; Wed, 6 Dec 2000 10:09:43 -0800 (PST) Received: (qmail 14065 invoked from network); 7 Dec 2000 02:41:40 +0900 Received: from zaqd3877995.zaq.ne.jp (HELO afaoe604) (211.135.121.149) by nsvm02.zaq.ne.jp with SMTP; 7 Dec 2000 02:41:40 +0900 From: MATUYA To: freebsd-current@freebsd.org Subject: =?ISO-2022-JP?B?g1iDSoNwgVuDYIOFgVuDaYFbgsyDToOKg1iDfYNYg3aDjINbg5ODZ47AjnuShg==?= X-Mailer: MultiSneder1.2 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Message-Id: <20001206180943.A28B737B401@hub.freebsd.org> Date: Wed, 6 Dec 2000 10:09:43 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ‚±‚ñ‚É‚¿‚íB “Ë‘R‚̃[ƒ‹‚Å‚·‚Ý‚Ü‚¹‚ñB ‚Ü‚½ŠÔˆá‚Á‚Äd•¡‚µ‚ă[ƒ‹‚ª“Í‚¢‚½•ûA–{“–‚É‚²‚ß‚ñ‚È‚³‚¢B ‚²‹»–¡‚Ì‚È‚¢•û‚ÍA[‚­‚¨˜l‚Ñ\‚µã‚°‚Ü‚·‚Æ‚Æ‚à‚ÉA ‚¨Žè”‚Å‚·‚ªA‚±‚Ì‚Ü‚Ü휂µ‚ĉº‚³‚é‚悤‚¨Šè‚¢\‚µã‚°‚Ü‚·B ‘ü¡AƒXƒJƒp[ƒ`ƒ…[ƒi[‚̃NƒŠƒXƒ}ƒXƒvƒŒƒ[ƒ“ƒgŽÀŽ{’†I ’Š‘I‚Å‚P–¼—l‚ɃXƒJƒCƒp[ƒtƒFƒN‚s‚uI‚b‚rƒfƒWƒ^ƒ‹•ú‘—ŽóMƒZƒbƒg sSU-CS5SETt‚ðƒvƒŒƒ[ƒ“ƒg‚¢‚½‚µ‚Ü‚·B ‚Ç‚µ‚Ç‚µ‚²‰ž•å‚­‚¾‚³‚¢B ’÷‚ßØ‚èF‚P‚QŒŽ‚Q‚O“ú‚P‚UŽž‚Ü‚Å “–‘IŽÒ‚Ì”­•\F‚P‚QŒŽ‚Q‚Q“ú ‚P‚QŒŽ‚Q‚S“ú‚É‚¨“Í‚¯‚·‚é—\’è‚Å‚·B ƒvƒŒƒ[ƒ“ƒg‚̉ž•å‚Í‚±‚¿‚ç‚©‚ç @http://www.rakuten.co.jp/matuya/421062/427982/ „¬™–ÚŽŸ™„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„­ E‚¨Î•éƒR[ƒi[E‚¨ŽŽ‚µƒZƒbƒg‚Í‘——¿–³—¿ E‹IB”~Š±‚µAç–‡’Ђ̋¤“¯w“ü EƒNƒŠƒXƒ}ƒXƒvƒŒƒ[ƒ“ƒg @E‹ž‚Ì–¡Šo ç–‡’Ð @E‹ž’Е¨‚̉¤—l ‹ž‚·‚®‚« @E‚Ê‚©’Ð „¯„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„ª„®  ¡ ¡ ‚¨Î•éƒR[ƒi[E‚¨ŽŽ‚µƒZƒbƒg‚Í‘——¿–³—¿  ¡ ¡ @‚P‚QŒŽ‚R‚P“ú‚Ü‚Å‚Í‚¨Î•éE‚¨ŽŽ‚µ’Е¨ƒZƒbƒg‚Ì‘——¿‚Í–³—¿‚Å‚·B @@‚¨Î•éƒR[ƒi[@http://www.rakuten.co.jp/matuya/410527/ @@‚¨ŽŽ‚µƒZƒbƒg@@@http://www.rakuten.co.jp/matuya/413025/  ¡ ¡ ‹¤“¯w“ü  ¡ ¡ @ w“ü‡Œv”‚ª‘‚¦‚é‚قǃvƒ‰ƒCƒXƒ_ƒEƒ“‚µ‚Ä‚¢‚­‚¨”ƒ‚¢•¨•ûŽ® @uŠy“V‹¤“¯w“üv‚ðŽÀŽ{’†IIŒƒˆÀ‰¿Ši‚Åw“ü‚·‚邽‚߂Ɉê’v’cŒ‹‚Å‚·I @Ÿ‹IB”~Š±‚µ ‚Q‡s–¡”~i‚Í‚¿‚݂“üj ’Êí”Ì”„‰¿Ši ‚W‚T‚O‚O‰~(Á”ïÅ•Ê) @@Œµ‘I‚µ‚½‹IB”~‚ð“ÆŽ©‚Ì»–@‚É‚æ‚èA‚Í‚¿‚݂‚ƃŠƒ“ƒS|‚ð‰Á‚¦ @@‚¶‚Á‚­‚è‚ÆŽžŠÔ‚ð‚©‚¯‚ĒЂ¯‚ ‚°‚½A‚Ü‚ë‚â‚©‚È–¡‚É‚È‚Á‚Ä‚¢‚Ü‚·B @@‰–•ªF–ñ‚W“ @@”Ì”„ŠúŠÔ 12ŒŽ01“ú00Žž00•ª`12ŒŽ15“ú23Žž00•ª @“üŽDŽÒ‚ª‘½‚¢‚قLjÀ‚­‚È‚é @‚Ý‚ñ‚È‚Å‹¦—Í‚·‚ê‚ÎÅ‚‚Å‚Q‚O‚O‚O‰~‚ÌŠ„ˆøI @‘——¿‚͉½ŒÂ”ƒ‚Á‚Ä‚à‘S‘ˆê—¥‚Ì‚U‚O‚O‰~‚Å‚·B @@“üŽD‚Í‚±‚¿‚ç‚©‚ç@http://www.rakuten.co.jp/matuya/422498/429304/ @Ÿç–‡’Ð ‚P‚T‚O‚‡ ’Êí”Ì”„‰¿Ši ‚V‚O‚O‰~(Á”ïÅ•Ê) @@Œµ‘I‚³‚ꂽ¹Œì‰@‚©‚Ô‚ç‚ð”–‚­Ø‚èAÅ‚‚Ì©•z‚ðŽg‚Á‚ĒЂ¯ž‚Ý‚Ü‚µ‚½B @@”Ì”„ŠúŠÔ 12ŒŽ01“ú00Žž00•ª`12ŒŽ15“ú23Žž00•ª @“üŽDŽÒ‚ª‘½‚¢‚قLjÀ‚­‚È‚é @‚Ý‚ñ‚È‚Å‹¦—Í‚·‚ê‚ÎÅ‚‚Å”¼Šz‚ÉI @‘——¿‚͉½ŒÂ”ƒ‚Á‚Ä‚à‘S‘ˆê—¥‚Ì‚U‚O‚O‰~‚Å‚·B @@“üŽD‚Í‚±‚¿‚ç‚©‚ç@http://www.rakuten.co.jp/matuya/422498/429504/  ¡ ¡ ƒNƒŠƒXƒ}ƒXƒvƒŒƒ[ƒ“ƒg  ¡ ¡ ‚܂‚₩‚ç‚̃NƒŠƒXƒ}ƒXƒvƒŒƒ[ƒ“ƒg‚̓XƒJƒp[ƒ`ƒ…[ƒi[ƒZƒbƒgB ‰ž•å‚³‚ꂽ’†‚©‚ç’Š‘I‚Å‚P–¼—l‚ɃNƒŠƒXƒ}ƒXƒvƒŒƒ[ƒ“ƒg‚¢‚½‚µ‚Ü‚·B ƒvƒŒƒ[ƒ“ƒg‚̉ž•å‚Í‚±‚¿‚ç‚©‚ç http://www.rakuten.co.jp/matuya/421062/427982/  ¡ ¡ ‹ž‚Ì–¡Šo ç–‡’Ð  ¡ ¡ ‹ž‚Ì“~‚Ì•—•¨Ž‚Æ‚¢‚¦‚ÎAç–‡’ÐBˆê–‡ˆê–‡‚±‚±‚ë‚ð‚±‚ß‚Ä’Ð‚¯ ‚½A‹ž‚‚¯‚à‚Ì‚Ì‘ã•\“I‚ÈŠç‚Å‚·B ©•zç–‡’Ð@@‚P‚T‚O‚‡ ‚V‚O‚O‰~ —Mç–‡’Ð@@@‚P‚T‚O‚‡ ‚V‚O‚O‰~ ƒsƒŠhç–‡’Ð@‚P‚T‚O‚‡ ‚V‚O‚O‰~ ©•zç–‡’Ð@@‚P‚T‚O‚‡ ‚V‚O‚O‰~ http://www.rakuten.co.jp/matuya/414998/427884/  ¡ ¡ ‹¤“¯w“ü‚Æ’Êí¤•i‚𓯎žw“üŽž‚Ì‘——¿  ¡ ¡ ’Êí“–“X‚Ŕ̔„‚µ‚Ä‚¢‚餕i‚Æ‹¤“¯w“ü‚Å—ŽŽD‚µ‚½¤•i‚𓯎ž‚Éw“ü‚µ‚½ ê‡A”z‘—悪“¯‚¶‚Å‚ ‚ê‚Î’Êíw“ü‚Ì‘——¿‚ª—D悳‚ê‚Ü‚·B ‚È‚¨A‚P”z‘—æ‚ɂ‚«‚¨”ƒ‚¢‚ ‚°‡Œv‚ª5000‰~ˆÈã‚Í‘——¿–³—¿‚Å‚·B E’Êí¤•i{‹¤“¯w“ü ¨ ’Êíw“ü‚̤•i‚Ì‘——¿‚Ì‚Ý‚¢‚½‚¾‚«‚Ü‚· E‹¤“¯w“ü{‹¤“¯w“ü ¨ ‘S‘ˆê—¥‚Ì‚U‚O‚O‰~i‚PŒÂ•ª‚Ì‘——¿j E’Êí¤•i{ƒI[ƒNƒVƒ‡ƒ“ ¨ ’Êíw“ü‚̤•i‚Ì‘——¿‚Ì‚Ý‚¢‚½‚¾‚«‚Ü‚· ã‹L‚É‹LÚ‚µ‚Ä‚¢‚éðŒ‚ͤ•i‚ª‚PŒÂŒû‚Æ‚µ‚Ä‚¨“Í‚¯‚Å‚«‚éꇂ݂̂ł·B ¤•i‚ª‚Ç‚¤‚µ‚Ä‚à‚QŒÂŒû‚É‚È‚éꇂ͗¼•û‚É‘——¿‚ª‚©‚©‚è‚Ü‚·B “¯Žžw“ü‚µ‚½ê‡‚ÍAƒRƒƒ“ƒg—“‚â”õl—“‚É‚»‚Ì‚±‚Ƃ𖾋L‚µ‚ĉº‚³‚ê‚Î ‚Å‚«‚邾‚¯‘——¿‚ª—]•ª‚É‚©‚©‚ç‚È‚¢‚悤‚É“w—Í‚µ‚Ü‚·B  ¡ ¡ ‹ž’Е¨‚̉¤—l ‹ž‚·‚®‚«  ¡ ¡ u‚·‚®‚«v‚Íç–‡’Ђ¯‚Æ•À‚ÔA‹ž‚‚¯‚à‚Ì‚Ì‘ã•\‚Å‚·B Žè‚­‚è‹Z–@‚ÅŽž @ŠÔ‚ð‚©‚¯‚ĒЂ¯ž‚ÝAŽ©‘R‚Ì–¡‚í‚¢‚ð³Šm‚É“`‚¦‚Ä‚¢‚Ü‚·B @‹ž“sã‰ê–Î’n•û‚É‚Æ‚ê‚é‚·‚®‚«‚©‚Ô‚ç‚ðÞ—¿‚ÉAÌ‚È‚ª‚ç‚ÌŽè–@‚ðŽg‚¢A @‚½‚ñ‚Ë‚ñ‚É‚Ä‚¢‚Ë‚¢‚ÉS‚ð‚±‚ß‚Ä’Ð‚¯‚±‚ñ‚Å‚¢‚«‚Ü‚·B ‹ž‚·‚®‚«@‚S‚O‚O‚‡ ‚P‚O‚O‚O‰~ http://www.rakuten.co.jp/matuya/414998/414999/  ¡ ¡ ‚Ê‚©’Ð  ¡ ¡ @“–“XŽ©–‚Ìu…‰ÖŽq‚Ê‚©’Ðv‚ÌŽžŠú‚à‚à‚¤I‚í‚Á‚Ä‚µ‚Ü‚¢‚Ü‚µ‚½‚ªA‚±‚ç‚© @‚ç‚Í–{’ЂÌ{‚Ì–ìØ‚ðЉ‚Ä‚¢‚­—\’è‚Å‚·B’è”Ԃ̌ӉZE‰ÖŽq‚©‚çŒÃ’ÐD @‚«‚Ì•û‚Ì‚½‚ß‚É”’Ø‚¢‚è‚Ê‚©’ЂâƒLƒƒƒxƒc‚¢‚è‚Ê‚©’Ђ܂ł¢‚ë‚¢‚ë‚ ‚è‚Ü‚·B ‚Ê‚©’ЃR[ƒi[ http://www.rakuten.co.jp/matuya/410530/ ™š™š™š™š™š™š™š™š™š™š™š™š @ ‚¨’Е¨‚̂܂‚â URLFhttp://www.rakuten.co.jp/matuya/ E-mailFmatuya@vm01.vaio.ne.jp ™š™š™š™š™š™š™š™š™š™š™š™š To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 11:17:54 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 11:17:52 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 5F60A37B400; Wed, 6 Dec 2000 11:17:51 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 143k4a-0002xK-00; Wed, 06 Dec 2000 19:17:48 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eB6JHN301854; Wed, 6 Dec 2000 20:17:23 +0100 (CET) (envelope-from wkb) Date: Wed, 6 Dec 2000 20:17:23 +0100 From: Wilko Bulte To: Trevor Johnson Cc: "Michael C . Wu" , Tatsumi Hosokawa , current@freebsd.org Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001206201723.G497@freebie.demon.nl> References: <20001206034625.A40075@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from trevor@jpj.net on Wed, Dec 06, 2000 at 01:03:29PM -0500 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 01:03:29PM -0500, Trevor Johnson wrote: > > People who run -CURRENT should be able to read and write English to > > understand the code comments, report bugs, and post to the lists in English. > > > "If you don't know what to do with -CURRENT, don't install it." > > You seem to be working from the assumption that people who understand > English can't understand any other language. The reverse is generally true: native speakers of the English/American language often don't understand any other language :-P -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 11:23:15 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 11:23:13 2000 Return-Path: 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 A46FF37B402; Wed, 6 Dec 2000 11:23:12 -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 eB6JMtw03384; Wed, 6 Dec 2000 11:22:55 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Tatsumi Hosokawa Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, keichii@peorth.iteration.net, hosokawa@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Progress report: Multilingual sysinstall for -current In-Reply-To: Message from Tatsumi Hosokawa of "Thu, 07 Dec 2000 00:26:39 +0900." <86zoi91sgg.wl@ringo.FromTo.Cc> Date: Wed, 06 Dec 2000 11:22:55 -0800 Message-ID: <3380.976130575@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My feeling on this is that sysinstall is (and always has been :-) at the end of its life and adding multi-lingual capabilities to it is a reasonable part of its retirement. The libh project is promising but suffers from a lack of volunteers, volunteers who aren't working on sysinstall either so I'm not worried about it somehow sucking the necessary time and attention away from libh. Hacking on sysinstall I18N in -current gives the developers the current.freebsd.org snapshot machine as a testing vehicle (why should the SMP people get all the benefit?) and is entirely reasonable as a staging area for -stable, which is also what -current is supposed to be. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 11:38:40 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 11:38:37 2000 Return-Path: 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 45A5137B400; Wed, 6 Dec 2000 11:38:36 -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 eB6JcXw03536; Wed, 6 Dec 2000 11:38:34 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: obrien@freebsd.org Cc: current@freebsd.org, Alfred Perlstein Subject: Re: Progress report: Multilingual sysinstall for -current In-Reply-To: Message from "David O'Brien" of "Wed, 06 Dec 2000 09:00:59 PST." <20001206090059.C2205@dragon.nuxi.com> Date: Wed, 06 Dec 2000 11:38:33 -0800 Message-ID: <3533.976131513@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, KSE has paid developers working on it. When was the last cycle spent > on libh? I'm glad you brought that up - I've been trying to find more things for you to do. I'll bring it up during the engineering staff meeting today. ;-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 12: 7:42 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 12:07:40 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from reliant.nielsenmedia.com (reliant.nielsenmedia.com [205.129.32.15]) by hub.freebsd.org (Postfix) with ESMTP id 7925637B400 for ; Wed, 6 Dec 2000 12:07:39 -0800 (PST) Received: from nmrusdunsxg2.nielsenmedia.com (nmrusdunsxg2.nielsenmedia.com [10.9.11.121]) by reliant.nielsenmedia.com (8.9.3/8.9.3) with ESMTP id PAA16499 for ; Wed, 6 Dec 2000 15:07:38 -0500 (EST) Received: by nmrusdunsxg2.nielsenmedia.com with Internet Mail Service (5.5.2651.58) id ; Wed, 6 Dec 2000 15:07:38 -0500 Message-ID: <01D4D419B1A4D111A30400805FE65B13070AC10D@nmrusdunsx1.nielsenmedia.com> From: "Gray, David W." To: "'FreeBSD Current list'" Subject: PNA? Date: Wed, 6 Dec 2000 15:07:36 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 12:31:54 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 12:31:53 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 24F8637B401 for ; Wed, 6 Dec 2000 12:31:53 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB6KeqF52183; Wed, 6 Dec 2000 12:40:58 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012062040.eB6KeqF52183@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Gray, David W." Cc: "'FreeBSD Current list'" Subject: Re: PNA? In-reply-to: Your message of "Wed, 06 Dec 2000 15:07:36 EST." <01D4D419B1A4D111A30400805FE65B13070AC10D@nmrusdunsx1.nielsenmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 12:40:52 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. > 3com 3c410, or D-Link DHN-520? No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom refuse to give us documentation. -- ... 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 Dec 6 13:20:25 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 13:20:24 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from sm10.texas.rr.com (sm10.texas.rr.com [24.93.35.222]) by hub.freebsd.org (Postfix) with ESMTP id D529E37B400 for ; Wed, 6 Dec 2000 13:20:23 -0800 (PST) Received: from bleep.craftncomp.com (cs2777-167.houston.rr.com [24.27.77.167]) by sm10.texas.rr.com (8.11.0/8.11.1) with ESMTP id eB6LI9109081 for ; Wed, 6 Dec 2000 15:18:09 -0600 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id eB6LKHG13370 for ; Wed, 6 Dec 2000 15:20:17 -0600 (CST) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id eB6LKNG31523 for ; Wed, 6 Dec 2000 15:20:23 -0600 (CST) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200012062120.eB6LKNG31523@bloop.craftncomp.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: current@freebsd.org Subject: cvs-cur.6925.gz appears to be corrupt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 15:20:23 -0600 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With # ctm -b /cvs cvs-cur.6925.gz I get FR: /cvs/CVSROOT/history md5 mismatch. cvs-cur.6925.gz Fatal error: Corrupt patch. Expected "\n" but didn't find it {20}. ctm: exit(96) Anybody like to comment? -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 13:30:18 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 13:30:16 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (unknown [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 76C0037B400; Wed, 6 Dec 2000 13:30:15 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.10.0) with ESMTP id eB6LUES13640; Wed, 6 Dec 2000 16:30:14 -0500 (EST) Date: Wed, 6 Dec 2000 16:30:14 -0500 (EST) From: Trevor Johnson To: Mike Smith Cc: "Gray, David W." , Subject: Re: PNA? In-Reply-To: <200012062040.eB6KeqF52183@mass.osd.bsdi.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 Mike Smith wrote: > > Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. > > 3com 3c410, or D-Link DHN-520? > > No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom > refuse to give us documentation. I don't know whether their chips support version 2.0 of the standard (how important is this?) but Davicom Semiconductor is listed at http://www.freebsd.org/commercial/hardware.html . -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 13:48:10 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 13:48:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 59EBD37B400; Wed, 6 Dec 2000 13:48:07 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.10.0) with ESMTP id eB6LiGT14087; Wed, 6 Dec 2000 16:44:16 -0500 (EST) Date: Wed, 6 Dec 2000 16:44:15 -0500 (EST) From: Trevor Johnson To: Marcel Moolenaar Cc: Marc van Kempen , , , , Subject: Re: Other Linux stuff... In-Reply-To: <3A25466D.1EDB4C0D@cup.hp.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 > For trivial cases, the simplest solution would be to just remove > /compat/linux/usr/bin/ldd and have our native ldd do the work. If > something depends on the switches, this won't work. At http://huizen.dds.nl/~frodol/glibc/problems.html it says: * ldd gives real strange output, sometimes... The ldd script that comes with glibc-2.0.6 handles libc5 executables incorrectly, resulting in strange output. You are probably better off if you always use the ldd that comes with ld.so-1.9.9. Implement this by deleting or renaming /usr/i486-linux-libc6/bin/ldd I've done this under Linux itself, and it worked well. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 15:14: 7 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:14:06 2000 Return-Path: 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 1317D37B400; Wed, 6 Dec 2000 15:13:52 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eB6NDoL55033; Thu, 7 Dec 2000 00:13:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, nsayer@freebsd.org Subject: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS From: Poul-Henning Kamp Date: Thu, 07 Dec 2000 00:13:50 +0100 Message-ID: <55031.976144430@critter> Sender: phk@critter.freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In my bios I have PnPOS=NO, USB-IRQ=Disabled. The commit below results in a PCI interrupt storm and a terminally wedged system right after interrupts are enabled. Poul-Henning | nsayer 2000/12/03 09:07:24 PST | | Modified files: | sys/pci ohci_pci.c uhci_pci.c | Log: | We now have the ability to assign the correct IRQ when PNP-OS is turned | on. So stop failing the attach if the IRQ is unassigned. With this | patch, I can now boot with PNP-OS YES in my BIOS no differently than | PNP-OS NO (which is a good thing since Windows hangs with PNP-OS NO). | | Obtained from: msmith | | Revision Changes Path | 1.21 +1 -11 src/sys/pci/ohci_pci.c | 1.32 +1 -11 src/sys/pci/uhci_pci.c -- 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 Wed Dec 6 15:26:35 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:26:31 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp245.osd.bsdi.com [204.216.28.245]) by hub.freebsd.org (Postfix) with ESMTP id F40CB37B6A3; Wed, 6 Dec 2000 15:26:29 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB6NZgF00739; Wed, 6 Dec 2000 15:35:43 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012062335.eB6NZgF00739@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: current@freebsd.org, nsayer@freebsd.org Subject: Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS In-reply-to: Your message of "Thu, 07 Dec 2000 00:13:50 +0100." <55031.976144430@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 15:35:42 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In my bios I have PnPOS=NO, USB-IRQ=Disabled. > > The commit below results in a PCI interrupt storm and a terminally > wedged system right after interrupts are enabled. This would be a bug in the UHCI or OHCI driver then. You can avoid it by not running the driver. > Poul-Henning > > | nsayer 2000/12/03 09:07:24 PST > | > | Modified files: > | sys/pci ohci_pci.c uhci_pci.c > | Log: > | We now have the ability to assign the correct IRQ when PNP-OS is turned > | on. So stop failing the attach if the IRQ is unassigned. With this > | patch, I can now boot with PNP-OS YES in my BIOS no differently than > | PNP-OS NO (which is a good thing since Windows hangs with PNP-OS NO). > | > | Obtained from: msmith > | > | Revision Changes Path > | 1.21 +1 -11 src/sys/pci/ohci_pci.c > | 1.32 +1 -11 src/sys/pci/uhci_pci.c > > -- > 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 > -- ... 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 Dec 6 15:37:17 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:37:16 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id B3A0837B401 for ; Wed, 6 Dec 2000 15:37:15 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eB6NbFC09671; Wed, 6 Dec 2000 17:37:15 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f Sender: mdharnois@home.com To: freebsd-current@FreeBSD.ORG Subject: Re: -current kernel hangs machine solid ... References: From: Michael Harnois Date: 06 Dec 2000 17:37:14 -0600 In-Reply-To: Message-ID: <86wvddcead.fsf@mharnois.workgroup.net> Lines: 8 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Peisino,Ak(B) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just checking in ... I haven't had one of these random hangs in the last week or so. Anyone else? -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 15:37:23 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:37:20 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp245.osd.bsdi.com [204.216.28.245]) by hub.freebsd.org (Postfix) with ESMTP id 416C937B402; Wed, 6 Dec 2000 15:37:18 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB6NkVF00891; Wed, 6 Dec 2000 15:46:31 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012062346.eB6NkVF00891@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Poul-Henning Kamp , current@freebsd.org, nsayer@freebsd.org Subject: Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS In-reply-to: Your message of "Wed, 06 Dec 2000 15:35:42 PST." <200012062335.eB6NZgF00739@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 15:46:31 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > In my bios I have PnPOS=NO, USB-IRQ=Disabled. > > > > The commit below results in a PCI interrupt storm and a terminally > > wedged system right after interrupts are enabled. > > This would be a bug in the UHCI or OHCI driver then. You can avoid it by > not running the driver. I should have mentioned; you can probably also avoid it by letting your BIOS give the USB controller an IRQ, since it'll almost certainly also perform whatever initialisation the driver is currently missing out on. -- ... 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 Dec 6 15:44:10 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:44:08 2000 Return-Path: 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 8AB7A37B401; Wed, 6 Dec 2000 15:44:07 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eB6Ni6L55310; Thu, 7 Dec 2000 00:44:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: current@freebsd.org, nsayer@freebsd.org Subject: Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS In-Reply-To: Your message of "Wed, 06 Dec 2000 15:46:31 PST." <200012062346.eB6NkVF00891@mass.osd.bsdi.com> Date: Thu, 07 Dec 2000 00:44:06 +0100 Message-ID: <55308.976146246@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012062346.eB6NkVF00891@mass.osd.bsdi.com>, Mike Smith writes: >> > >> > In my bios I have PnPOS=NO, USB-IRQ=Disabled. >> > >> > The commit below results in a PCI interrupt storm and a terminally >> > wedged system right after interrupts are enabled. >> >> This would be a bug in the UHCI or OHCI driver then. You can avoid it by >> not running the driver. > >I should have mentioned; you can probably also avoid it by letting your >BIOS give the USB controller an IRQ, since it'll almost certainly also >perform whatever initialisation the driver is currently missing out on. Right, that is what I did once I realized that this particular commit was the culprit. -- 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 Wed Dec 6 15:52:20 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:52:19 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 94D3537B400; Wed, 6 Dec 2000 15:52:18 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eB6NqGs37837; Wed, 6 Dec 2000 16:52:17 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA82633; Wed, 6 Dec 2000 16:52:14 -0700 (MST) Message-Id: <200012062352.QAA82633@harmony.village.org> To: Wilko Bulte Subject: Re: Progress report: Multilingual sysinstall for -current Cc: Trevor Johnson , "Michael C . Wu" , Tatsumi Hosokawa , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Dec 2000 20:17:23 +0100." <20001206201723.G497@freebie.demon.nl> References: <20001206201723.G497@freebie.demon.nl> <20001206034625.A40075@peorth.iteration.net> Date: Wed, 06 Dec 2000 16:52:14 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001206201723.G497@freebie.demon.nl> Wilko Bulte writes: : > You seem to be working from the assumption that people who understand : > English can't understand any other language. : : The reverse is generally true: native speakers of the English/American : language often don't understand any other language hai! so desu. americanjin wa nihongo wakarimasen. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 15:52:37 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:52:35 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp245.osd.bsdi.com [204.216.28.245]) by hub.freebsd.org (Postfix) with ESMTP id D708637B401; Wed, 6 Dec 2000 15:52:33 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB6NxCF01051; Wed, 6 Dec 2000 15:59:12 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012062359.eB6NxCF01051@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Mike Smith , current@freebsd.org, nsayer@freebsd.org Subject: Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS In-reply-to: Your message of "Thu, 07 Dec 2000 00:44:06 +0100." <55308.976146246@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 15:59:12 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I should have mentioned; you can probably also avoid it by letting your > >BIOS give the USB controller an IRQ, since it'll almost certainly also > >perform whatever initialisation the driver is currently missing out on. > > Right, that is what I did once I realized that this particular commit > was the culprit. The commit isn't (really) the culprit; it's just exposed a bug in the USB chipset driver in question. (I'm mostly just making this point so that other people don't go blaming 'correct' PCI behaviour for their problems 8). -- ... 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 Dec 6 16:18:33 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 16:18:32 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 5AF0B37B400; Wed, 6 Dec 2000 16:18:31 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 1D493573EA; Wed, 6 Dec 2000 18:18:50 -0600 (CST) Date: Wed, 6 Dec 2000 18:18:50 -0600 From: "Michael C . Wu" To: Tatsumi Hosokawa Cc: current@FreeBSD.org Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001206181850.A47732@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <86g0k2q7gz.wl@ringo.FromTo.Cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <86g0k2q7gz.wl@ringo.FromTo.Cc>; from hosokawa@FreeBSD.org on Wed, Dec 06, 2000 at 05:28:28PM +0900 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | I've ported Multilingual sysinstall to -current. I put the latest | source and binaries (Japanese/Englush only) is at | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | (please note that non-English docuemnt files are based on 4.2-RELEASE) Just an idea. :) Do you have Alpha boot floppies? Does kons25/big5con/korean compile on Alpha? Would this fit on our ever growing mfsroot.flp and kern.flp? I recall seeing the release engineers struggling with fitting the kernel. It would be hard to make OpenBOOT and SRM do what we do in kons25. (Doable, but someone has to do it.) I also know that Alpha SRM+vidcontrol+sc0 can only have one video mode, 80x25. Can Mr. Yokota clarify this for me? If this makes into the normal sysinstall, can we simply have several versions of the boot floppies built during make release? Thanks, -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 16:37: 1 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 16:36:59 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id B379F37B400 for ; Wed, 6 Dec 2000 16:36:57 -0800 (PST) Received: (from steve@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id eB70aqU35607; Wed, 6 Dec 2000 19:36:52 -0500 (EST) (envelope-from steve) Date: Wed, 6 Dec 2000 19:36:52 -0500 From: Steve Ames To: Michael Harnois Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current kernel hangs machine solid ... Message-ID: <20001206193652.A90262@virtual-voodoo.com> References: <86wvddcead.fsf@mharnois.workgroup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <86wvddcead.fsf@mharnois.workgroup.net>; from mdharnois@home.com on Wed, Dec 06, 2000 at 05:37:14PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually... I just noticed that my hanging machine had been up for 5 days. I started it doing 'make -j8 world' in a continual loop a couple hours ago before leaving work... I'll see tomorrow. -Steve On Wed, Dec 06, 2000 at 05:37:14PM -0600, Michael Harnois wrote: > Just checking in ... I haven't had one of these random hangs in the > last week or so. Anyone else? > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > No man knows how bad he is > till he has tried very hard to be good. -- C.S. Lewis > > > 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 Dec 6 17: 8:17 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 17:08:14 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id D15C237B401 for ; Wed, 6 Dec 2000 17:08:09 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id eB7187006280 for ; Wed, 6 Dec 2000 19:08:07 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.0/8.9.3) id eB7187J02573 for current@freebsd.org; Wed, 6 Dec 2000 19:08:07 -0600 (CST) (envelope-from steve) Date: Wed, 6 Dec 2000 19:08:06 -0600 From: Steve Price To: current@freebsd.org Subject: SMP kernel builds borked Message-ID: <20001206190806.B27156@bonsai.knology.net> 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 i386 Sender: steve@hiwaay.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Builds are failing for SMP kernels with sources CVSup'd a couple of hours ago using the GENERIC config file with the following diffs. Index: GENERIC =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v retrieving revision 1.291 diff -u -r1.291 GENERIC --- GENERIC 2000/11/15 18:36:24 1.291 +++ GENERIC 2000/12/07 00:43:09 @@ -18,7 +18,7 @@ # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.291 2000/11/15 18:36:24 imp Exp $ machine i386 -cpu I386_CPU +#cpu I386_CPU cpu I486_CPU cpu I586_CPU cpu I686_CPU @@ -59,8 +59,8 @@ options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed -#options SMP # Symmetric MultiProcessor Kernel -#options APIC_IO # Symmetric (APIC) I/O +options SMP # Symmetric MultiProcessor Kernel +options APIC_IO # Symmetric (APIC) I/O device isa device eisa It looks like revision 1.132 of src/sys/sys/proc.h might be the culprit. I'll look deeper right after dinner. Here's the output of the build. steve@bsd(/usr/src/sys/compile/GENERIC)$ make cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../cam/cam_periph.c ../../cam/cam_periph.c: In function `cam_periph_unmapmem': ../../cam/cam_periph.c:687: internal error--unrecognizable insn: (insn/i 287 1112 288 (parallel[ (set (mem/s/v:SI (plus:SI (reg:SI 0 %eax) (const_int 284 [0x11c])) 0) (asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl %2; pushl %3; call mtx_exit_hard; addl $8,%%esp;1:# exitlock_norecurse") ("=m") 0[ (const_int 0 [0x0]) (reg/v:SI 4 %esi) (reg:SI 5 %edi) (mem/s/v:SI (plus:SI (reg:SI 3 %ebx) (const_int 284 [0x11c])) 0) (reg:SI 0 %eax) ] [ (asm_input:SI ("gi")) (asm_input:SI ("g")) (asm_input:SI ("r")) (asm_input:SI ("0")) (asm_input:SI ("1")) ] ("../../sys/mutex.h") 601)) (set (reg:SI 0 %eax) (asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl %2; pushl %3; call mtx_exit_hard; addl $8,%%esp;1:# exitlock_norecurse") ("=a") 1[ (const_int 0 [0x0]) (reg/v:SI 4 %esi) (reg:SI 5 %edi) (mem/s/v:SI (plus:SI (reg:SI 3 %ebx) (const_int 284 [0x11c])) 0) (reg:SI 0 %eax) ] [ (asm_input:SI ("gi")) (asm_input:SI ("g")) (asm_input:SI ("r")) (asm_input:SI ("0")) (asm_input:SI ("1")) ] ("../../sys/mutex.h") 601)) (clobber (reg:QI 1 %dl)) (clobber (reg:QI 2 %cl)) (clobber (mem:BLK (scratch) 0)) ] ) -1 (insn_list 286 (nil)) (nil)) *** Error code 1 Stop in /b/src/sys/compile/GENERIC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 17:33:33 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 17:33:29 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id BDA6237B402 for ; Wed, 6 Dec 2000 17:33:25 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.1/8.11.1) with ESMTP id eB71XPx06336 for ; Wed, 6 Dec 2000 17:33:25 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20001206172932.00a8eea8@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 06 Dec 2000 17:33:24 -0800 To: current@freebsd.org From: Manfred Antar Subject: Current kernel build failure -- >>cam_periph.c Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to build a current kernel from current sources for a day now and I keep getting this: cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/locore.s cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../cam/cam_periph.c ../../cam/cam_periph.c: In function `cam_periph_unmapmem': ../../cam/cam_periph.c:687: internal error--unrecognizable insn: (insn/i 376 1397 377 (parallel[ (set (mem/s/v:SI (plus:SI (reg:SI 0 %eax) (const_int 284 [0x11c])) 0) (asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f;pushl %2; pushl %3; call mtx_exit_hard; addl $8,%%esp;1:# exitlock_norecurse") ("=m") 0[ (const_int 0 [0x0]) (reg/v:SI 4 %esi) (reg:SI 5 %edi) (mem/s/v:SI (plus:SI (reg:SI 3 %ebx) (const_int 284 [0x11c])) 0) (reg:SI 0 %eax) ] [ (asm_input:SI ("gi")) (asm_input:SI ("g")) (asm_input:SI ("r")) (asm_input:SI ("0")) (asm_input:SI ("1")) ] ("../../sys/mutex.h") 601)) (set (reg:SI 0 %eax) (asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f;pushl %2; pushl %3; call mtx_exit_hard; addl $8,%%esp;1:# exitlock_norecurse") ("=a") 1[ (const_int 0 [0x0]) (reg/v:SI 4 %esi) (reg:SI 5 %edi) (mem/s/v:SI (plus:SI (reg:SI 3 %ebx) (const_int 284 [0x11c])) 0) (reg:SI 0 %eax) ] [ (asm_input:SI ("gi")) (asm_input:SI ("g")) (asm_input:SI ("r")) (asm_input:SI ("0")) (asm_input:SI ("1")) ] ("../../sys/mutex.h") 601)) (clobber (reg:QI 1 %dl)) (clobber (reg:QI 2 %cl)) (clobber (mem:BLK (scratch) 0)) ] ) -1 (insn_list 375 (nil)) (nil)) *** Error code 1 Stop in /usr/src/sys/compile/pro2 I did a make world last night from current sources and still no go Thanks Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 17:49:18 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 17:49:17 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 3FA4A37B400 for ; Wed, 6 Dec 2000 17:49:14 -0800 (PST) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id eB71n2H28832; Thu, 7 Dec 2000 12:19:02 +1030 (CST) (envelope-from grog) Date: Thu, 7 Dec 2000 12:19:02 +1030 From: Greg Lehey To: Michael Harnois Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current kernel hangs machine solid ... Message-ID: <20001207121902.S27667@wantadilla.lemis.com> References: <86wvddcead.fsf@mharnois.workgroup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <86wvddcead.fsf@mharnois.workgroup.net>; from mdharnois@home.com on Wed, Dec 06, 2000 at 05:37:14PM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: grog@wantadilla.lemis.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 6 December 2000 at 17:37:14 -0600, Michael Harnois wrote: > Just checking in ... I haven't had one of these random hangs in the > last week or so. Anyone else? Yup. My freshly installed machine has hung up again. Completely dead, apparently during a make world. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 17:49:44 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 17:49:43 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E4D8F37B401 for ; Wed, 6 Dec 2000 17:49:42 -0800 (PST) Received: from laptop.baldwin.cx (root@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB71n6799721; Wed, 6 Dec 2000 17:49:06 -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: <5.0.2.1.2.20001206172932.00a8eea8@pozo.com> Date: Wed, 06 Dec 2000 17:49:48 -0800 (PST) From: John Baldwin To: Manfred Antar Subject: RE: Current kernel build failure -- >>cam_periph.c Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-00 Manfred Antar wrote: > > > I've been trying to build a current kernel from current sources for a day now > and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). -- 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 Dec 6 18: 1:39 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 18:01:38 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR22-166.accesscable.net [24.138.22.166]) by hub.freebsd.org (Postfix) with ESMTP id 71A6737B400; Wed, 6 Dec 2000 18:01:37 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id eB7210Y66002; Wed, 6 Dec 2000 22:01:00 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 6 Dec 2000 22:00:59 -0400 (AST) From: The Hermit Hacker To: John Baldwin Cc: Manfred Antar , current@FreeBSD.ORG Subject: RE: Current kernel build failure -- >>cam_periph.c 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 Wed, 6 Dec 2000, John Baldwin wrote: > > On 07-Dec-00 Manfred Antar wrote: > > > > > > I've been trying to build a current kernel from current sources for a day now > > and I keep getting this: > > I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() > compiles in dozens of other places just fine (and has for months now). ah, so I take it a 'make buildworld' doesn't fix thsi one :) ah well, had to do it anyway ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 18:13:54 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 18:13:51 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 6610337B400; Wed, 6 Dec 2000 18:13:51 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.1/8.11.1) with ESMTP id eB72Dpx09304; Wed, 6 Dec 2000 18:13:51 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20001206175838.00a92500@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 06 Dec 2000 18:13:50 -0800 To: John Baldwin From: Manfred Antar Subject: RE: Current kernel build failure -- >>cam_periph.c Cc: current@FreeBSD.ORG In-Reply-To: References: <5.0.2.1.2.20001206172932.00a8eea8@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:49 PM 12/6/2000 -0800, you wrote: >On 07-Dec-00 Manfred Antar wrote: >> >> >> I've been trying to build a current kernel from current sources for a day now >> and I keep getting this: > >I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() >compiles in dozens of other places just fine (and has for months now). > >-- > >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 Yes It's a different kind of error. I've never seen this building a kernel before. The same kernel config without SMP enabled builds fine ! ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 18:23: 0 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 18:22:59 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 575BB37B400; Wed, 6 Dec 2000 18:22:58 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id eB72Mt009132; Wed, 6 Dec 2000 20:22:55 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.1/8.9.3) id eB72MsK10197; Wed, 6 Dec 2000 20:22:54 -0600 (CST) (envelope-from steve) Date: Wed, 6 Dec 2000 20:22:54 -0600 From: Steve Price To: Manfred Antar Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: Current kernel build failure -- >>cam_periph.c Message-ID: <20001206202254.E27156@bonsai.knology.net> References: <5.0.2.1.2.20001206172932.00a8eea8@pozo.com> <5.0.2.1.2.20001206175838.00a92500@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.2.20001206175838.00a92500@pozo.com>; from null@pozo.com on Wed, Dec 06, 2000 at 06:13:50PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: steve@hiwaay.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 06:13:50PM -0800, Manfred Antar wrote: # At 05:49 PM 12/6/2000 -0800, you wrote: # # >I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() # >compiles in dozens of other places just fine (and has for months now). # # Yes # It's a different kind of error. # I've never seen this building a kernel before. # The same kernel config without SMP enabled builds fine ! At least according to my tests thus far it appears it occurs when 'cpu I386_CPU' is not in your config file. It isn't really an SMP issue as far as I can tell, except that you must remove 'cpu I386_CPU' to build an SMP kernel. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 18:28:11 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 18:28:07 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2260D37B400 for ; Wed, 6 Dec 2000 18:28:07 -0800 (PST) Received: from laptop.baldwin.cx (root@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB72Ra700858; Wed, 6 Dec 2000 18:27:36 -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: Wed, 06 Dec 2000 18:28:18 -0800 (PST) From: John Baldwin To: current@FreeBSD.org Subject: RE: Current kernel build failure -- >>cam_periph.c Cc: Manfred Antar Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-00 John Baldwin wrote: > > On 07-Dec-00 Manfred Antar wrote: >> >> >> I've been trying to build a current kernel from current sources for a day >> now >> and I keep getting this: > > I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() > compiles in dozens of other places just fine (and has for months now). Nope, it was a sublte bug in the 486 optimized mutex operations, which had invalid register constraints probably dating back to several older revisions in BSD/OS before we got the code. It should be fixed now. -- 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 Dec 6 18:38:49 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 18:38:45 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp245.osd.bsdi.com [204.216.28.245]) by hub.freebsd.org (Postfix) with ESMTP id 7D35837B400 for ; Wed, 6 Dec 2000 18:38:45 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB72lrF06520; Wed, 6 Dec 2000 18:47:53 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012070247.eB72lrF06520@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Trevor Johnson Cc: "David W." , FreeBSD-current@FreeBSD.ORG Subject: Re: PNA? In-reply-to: Your message of "Wed, 06 Dec 2000 16:30:14 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 18:47:53 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. > > > 3com 3c410, or D-Link DHN-520? > > > > No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom > > refuse to give us documentation. > > I don't know whether their chips support version 2.0 of the standard (how > important is this?) but Davicom Semiconductor is listed at > http://www.freebsd.org/commercial/hardware.html . 10 seconds with their site confirms that they only support the 1Mbps standard. 2.0 is the standard revision which covers 10Mbps operation. -- ... 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 Dec 6 19:24: 2 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 19:24:00 2000 Return-Path: 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 A6D1E37B400 for ; Wed, 6 Dec 2000 19:23:59 -0800 (PST) Received: from MexComUSA.Net (adsl-63-205-16-202.dsl.mtry01.pacbell.net [63.205.16.202]) by dsl.MexComUSA.net (8.11.1/8.11.1) with ESMTP id eB73Jjl75148; Wed, 6 Dec 2000 19:19:45 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Sender: root@dsl.MexComUSA.net Message-ID: <3A2F02BB.2882A98A@MexComUSA.Net> Date: Wed, 06 Dec 2000 19:23:40 -0800 From: Charlie Root Organization: MexComUSA.Net/EnContacto.Net/CafeMania.Net X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Ambrisko Cc: Warner Losh , Wes Peters , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: <200012052105.NAA19124@whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is definately a trend to lower prices. I just found this. A new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia cards for $699. The access point sounds interesting. I personally would like to use it as a repeater and network bridge. http://www.intel.com/network/products/wireless.htm https://merchant.hibbertco.com/servlet/InteComServlet?SessionID=319728709221315074&OrderID=71803&ItemCnt=1&Adapters=yes ed Doug Ambrisko wrote: > Warner Losh writes: > | In message <200012051932.LAA23532@whistle.com> Doug Ambrisko writes: > | : Well this is what I'm doing with the Aironet stuff. I have a script > | : to flip between modes until it sync's up. I bought the PCMCIA ISA > | : adapter for $25 from a local surplus place. > | > | Does this mean that the an driver can operate in "base station" mode? > > No, just ad-hoc (atleast that's what is published). So on my laptop my > script flips between modes (ad-hoc & infrastructure) until it sync's up > with whatever it can find. I start it out of pccard.conf so it is automatic > on card insertion, reboot or wakeup. > > | : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around > | : $220 that can do 128 bit encryption, has an antenna and is Web administered. > | : I haven't used it but it looks interesting. > | > | I'll have to check this out as well. > > Let us know what you find out. > > Doug A. > > 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 Dec 6 19:28:31 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 19:28:29 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hub.lovett.com (hub.lovett.com [216.60.121.161]) by hub.freebsd.org (Postfix) with ESMTP id 2B80737B400 for ; Wed, 6 Dec 2000 19:28:29 -0800 (PST) Received: from ade by hub.lovett.com with local (Exim 3.16 #1) id 143rjO-000D0Y-00; Wed, 06 Dec 2000 21:28:26 -0600 Date: Wed, 6 Dec 2000 21:28:25 -0600 From: Ade Lovett To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? Message-ID: <20001206212825.W46011@FreeBSD.org> References: <200012051932.LAA23532@whistle.com> <200012052046.NAA72980@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: <200012052046.NAA72980@harmony.village.org>; from imp@village.org on Tue, Dec 05, 2000 at 01:46:51PM -0700 Sender: ade@lovett.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 05, 2000 at 01:46:51PM -0700, Warner Losh wrote: > In message <200012051932.LAA23532@whistle.com> Doug Ambrisko writes: > : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around > : $220 that can do 128 bit encryption, has an antenna and is Web administered. > : I haven't used it but it looks interesting. > > I'll have to check this out as well. FWIW, I ordered one of these today.. I'll pass on my discoveries with my various wireless cards (mostly Lucent) if y'all are interested.. -aDe [today's toy is powered by the letters 'I', 'R' and 'S'] -- Ade Lovett, Austin, TX. ade@FreeBSD.org FreeBSD: 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 Dec 6 21:10:43 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 21:10:40 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 25D9337B400; Wed, 6 Dec 2000 21:10:40 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.1/8.11.1) with ESMTP id eB75AYE00341; Wed, 6 Dec 2000 21:10:35 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20001206210835.00ada270@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 06 Dec 2000 21:10:34 -0800 To: John Baldwin , current@FreeBSD.ORG From: Manfred Antar Subject: RE: Current kernel build failure -- >>cam_periph.c In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: >On 07-Dec-00 John Baldwin wrote: >> >> On 07-Dec-00 Manfred Antar wrote: >>> >>> >>> I've been trying to build a current kernel from current sources for a day >>> now >>> and I keep getting this: >> >> I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() >> compiles in dozens of other places just fine (and has for months now). > >Nope, it was a sublte bug in the 486 optimized mutex operations, which had >invalid register constraints probably dating back to several older revisions in >BSD/OS before we got the code. It should be fixed now. > John It compiles now fine but panics on booting: Doing initial network setup: hostname. panic: mutex sched lock owned at ../../kern/kern_mutex.c:322 cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 syncing disks... Fatal double fault: eip = 0xc02b0e7d esp = 0xcafce000 ebp = 0xcafce020 cpuid = 0; lapic.id = 00000000 I built another one and got a different panic: Initial rc.i386 panic: spin lock sched lock held by 0x0xc0390a01 for > 5 seconds cpuid = 1; lapic.id = 0c000000 boot() called on cpu#1 syncing disks... Just frozen at this point Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 6 22: 8:27 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 22:08:25 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 0473D37B401 for ; Wed, 6 Dec 2000 22:08:25 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 143uHH-0000DL-00; Wed, 06 Dec 2000 23:11:35 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A2F2A17.E848A06@softweyr.com> Date: Wed, 06 Dec 2000 23:11:35 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Doug Ambrisko , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: <200012051932.LAA23532@whistle.com> <200012052046.NAA72980@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <200012051932.LAA23532@whistle.com> Doug Ambrisko writes: > : Well this is what I'm doing with the Aironet stuff. I have a script > : to flip between modes until it sync's up. I bought the PCMCIA ISA > : adapter for $25 from a local surplus place. > > Does this mean that the an driver can operate in "base station" mode? > > : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around > : $220 that can do 128 bit encryption, has an antenna and is Web administered. > : I haven't used it but it looks interesting. Linksys has a new one, WAP-11, that has all of the above and dual antennas (should be much better for signal diversity) for about $240, but nobody really has it in stock yet. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 0:57:49 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 00:57:47 2000 Return-Path: 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 9EA0F37B400; Thu, 7 Dec 2000 00:57:46 -0800 (PST) Received: from newsguy.com (p31-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.96]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id RAA29642; Thu, 7 Dec 2000 17:57:35 +0900 (JST) Message-ID: <3A2F3D22.C31E6CBF@newsguy.com> Date: Thu, 07 Dec 2000 16:32:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: "Michael C . Wu" , Tatsumi Hosokawa , current@FreeBSD.ORG Subject: Re: Progress report: Multilingual sysinstall for -current References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > > I don't think importing multilingual sysinstall will detract effort > from libh. You see, even if it is maintained separately from the > -current, it has its own maintainers and developers. I expect they > are the same people who will maintain and develop I18N sysinstall when > it is imported to the -current. They may or may not be libh > developers at the same time. But, I don't think I18N sysinstall is > suddenly needing a large army of developers and will steal them from > the libh developer base. Moreover, libh is a coding effort, while i18n sysinstall by and large is not. And even where code comes into play with i18n sysinstall, it is of a very different kind than libh code. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 5:22:29 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 05:22:27 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (hades.cybercity.dk [212.242.42.118]) by hub.freebsd.org (Postfix) with ESMTP id B407A37B400 for ; Thu, 7 Dec 2000 05:22:26 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eB7A3eL82701 for ; Thu, 7 Dec 2000 11:03:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: LINT broken From: Poul-Henning Kamp Date: Thu, 07 Dec 2000 11:03:40 +0100 Message-ID: <82699.976183420@critter> Sender: phk@critter.freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensio ns -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -DGPROF -D_KERNEL -include opt_global.h -elf - malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg ../../dev/ichsmb/ichsmb_pci.c In file included from ../../dev/ichsmb/ichsmb_pci.c:63: ../../dev/ichsmb/ichsmb_var.h:67: field `mutex' has incomplete type *** 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 Thu Dec 7 10:34:49 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 10:34:44 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 870) id 9741D37B400; Thu, 7 Dec 2000 10:34:44 -0800 (PST) Date: Thu, 7 Dec 2000 10:34:44 -0800 From: Christoph Herrmann To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: growfs(8) for FreeBSD Message-ID: <20001207103444.B25381@freebsd.org> Reply-To: growfs@tomsoft.com 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, Due to vinum it is no problem to add disks and grow your volumes but up to now you couldn't easily make use of that new space for a file system, except using sequence of ufsdump/newfs/ufsrestore or something similar. Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8) for FreeBSD. Currently we can only grow unmounted file systems (in a clean state) without any active snapshots inside. It is foreseen to enhance growfs to grow mounted file systems as well, and handle active snapshots correctly. This requires some infrastructure which is then only available in FreeBSD-5, whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3 (tested) and possibly even on FreeBSD-2 (untested). To help us gathering the needed data for fixing bugs in growfs we additionally wrote ffsinfo(8), a (very) extended version of dumpfs. We've sent a couple of snapshots of our code to Kirk McKusick and to Greg Lehey. Greg also volunteered :-) for reviewing the code. We also maintain some sort of (for some contractual reasons unilaterally) contact with Don Coleman who is doing the same thing for BSD/OS. -- Ciao Christoph &:-) M$: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys comming, or what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 10:34:54 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 10:34:50 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id B1FDA37B401 for ; Thu, 7 Dec 2000 10:34:45 -0800 (PST) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.1+3.4W/3.7W-light) with UUCP id eB7IYhK29325 for current@FreeBSD.ORG; Fri, 8 Dec 2000 03:34:43 +0900 (JST) (envelope-from ume@FreeBSD.org) Received: from localhost (IDENT:1s0MdIDPZQoNIAa4b3d1LFFSql1mcOkmU6yDWVQk7Xh6IvTgf4HO+ZixxJ9PEZFC@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.1/8.11.1/chaos) with ESMTP/inet6 id eB7IWTn10103 for ; Fri, 8 Dec 2000 03:32:29 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Fri, 08 Dec 2000 03:32:28 +0900 (JST) Message-Id: <20001208.033228.74681168.ume@FreeBSD.org> To: current@FreeBSD.ORG Subject: [CFR] IPv6 support for lpd, syslogd and logger From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 Hi, I'd like to add IPv6 support for lpd, syslogd and logger. You can find the patches from: http://www.imasy.or.jp/~ume/ipv6/FreeBSD/logger-ipv6-20001201.diff http://www.imasy.or.jp/~ume/ipv6/FreeBSD/lpr-ipv6-20001206.diff http://www.imasy.or.jp/~ume/ipv6/FreeBSD/syslogd-ipv6-20001201.diff Please review. If there is no objection, I'll commit it at next weekend. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 12:37:33 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 12:37:30 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn144.dh.casema.net [212.64.31.144]) by hub.freebsd.org (Postfix) with ESMTP id 53B2F37B400 for ; Thu, 7 Dec 2000 12:37:28 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id eB7KsTl01199; Thu, 7 Dec 2000 21:54:50 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20001207213006.00be4600@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 07 Dec 2000 21:36:46 +0100 To: growfs@tomsoft.com From: "Rogier R. Mulhuijzen" Subject: Re: growfs(8) for FreeBSD Cc: freebsd-current@freebsd.org In-Reply-To: <20001207103444.B25381@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it also capable of shrinking filesystems? I've sometimes wanted to grow my /var or / slice using space freed by shrinking /usr (on a default partitioned disk). Up to now I've solved it through symlinks, but that doesn't really deserve the beauty award. I'd imagine a lot of new users wouldn't mind being able to change partition size on a fully configured machine without having to resort to backup, reslice, restore.... Anyways, sounds like a very handy tool already! Just my $0,02 DocWilco At 10:34 7-12-00 -0800, you wrote: >Hi, > >Due to vinum it is no problem to add disks and grow your volumes but up to >now you couldn't easily make use of that new space for a file system, except >using sequence of ufsdump/newfs/ufsrestore or something similar. > >Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8) >for FreeBSD. Currently we can only grow unmounted file systems (in a clean >state) without any active snapshots inside. It is foreseen to enhance >growfs to >grow mounted file systems as well, and handle active snapshots correctly. >This requires some infrastructure which is then only available in FreeBSD-5, >whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3 >(tested) and possibly even on FreeBSD-2 (untested). > >To help us gathering the needed data for fixing bugs in growfs we additionally >wrote ffsinfo(8), a (very) extended version of dumpfs. > >We've sent a couple of snapshots of our code to Kirk McKusick and to Greg >Lehey. Greg also volunteered :-) for reviewing the code. We also maintain >some sort of (for some contractual reasons unilaterally) contact with Don >Coleman who is doing the same thing for BSD/OS. > >-- >Ciao > > > Christoph &:-) > > > >M$: Where do you want to go today? >Linux: Where do you want to go tomorrow? >FreeBSD: Are you guys comming, or what? > > >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 Thu Dec 7 12:43:21 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 12:43:17 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4968737B400; Thu, 7 Dec 2000 12:43:16 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA68959; Thu, 7 Dec 2000 21:45:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200012072045.VAA68959@freebsd.dk> Subject: Re: growfs(8) for FreeBSD In-Reply-To: <20001207103444.B25381@freebsd.org> from Christoph Herrmann at "Dec 7, 2000 10:34:44 am" To: growfs@tomsoft.com Date: Thu, 7 Dec 2000 21:45:40 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG 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 It seems Christoph Herrmann wrote: Sounds very cool, but there is no URL :) > Due to vinum it is no problem to add disks and grow your volumes but up to > now you couldn't easily make use of that new space for a file system, except > using sequence of ufsdump/newfs/ufsrestore or something similar. > > Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8) > for FreeBSD. Currently we can only grow unmounted file systems (in a clean > state) without any active snapshots inside. It is foreseen to enhance growfs to > grow mounted file systems as well, and handle active snapshots correctly. > This requires some infrastructure which is then only available in FreeBSD-5, > whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3 > (tested) and possibly even on FreeBSD-2 (untested). > > To help us gathering the needed data for fixing bugs in growfs we additionally > wrote ffsinfo(8), a (very) extended version of dumpfs. > > We've sent a couple of snapshots of our code to Kirk McKusick and to Greg > Lehey. Greg also volunteered :-) for reviewing the code. We also maintain > some sort of (for some contractual reasons unilaterally) contact with Don > Coleman who is doing the same thing for BSD/OS. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 14:18:56 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 14:18:50 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id E3E5E37B400 for ; Thu, 7 Dec 2000 14:18:47 -0800 (PST) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id eB7MJ9Q24277 for ; Fri, 8 Dec 2000 08:49:09 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Fri, 8 Dec 2000 08:48:06 +1030 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id IAA16807; Fri, 8 Dec 2000 08:43:08 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id WZWR8PHQ; Fri, 8 Dec 2000 08:43:07 +1030 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id IAA20529; Fri, 8 Dec 2000 08:43:07 +1030 (CST) Sender: thyerm@dsto.defence.gov.au Message-ID: <3A300B90.F20A6120@dsto.defence.gov.au> Date: Fri, 08 Dec 2000 08:43:36 +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: "John W. De Boskey" Cc: freebsd-current@freebsd.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition References: <3A2EE6B8.69624B48@dsto.defence.gov.au> <20001207012231.A4194@bsdwins.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CC: to -current as that's what I'm running. "John W. De Boskey" wrote: > > Hi, > > I can't answer your questions directly, but you might want > to checkout the sources to newfs (/usr/src/sbin/newfs/newfs.c or > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/newfs/newfs.c?annotate=1.31 > line 417). > > I'll be glad to review your program if you would like. I'm not after a review, I'd like FreeBSD-CURRENT fixed. The program works on Compaq True64 UNIX v 4.0d It also works on Solaris 7 (only tested sparc). So it seems FreeBSD is broken here. > -john > jwd@FreeBSD.org > > ----- Matthew Thyer's Original Message ----- > > Attached is scrub.c used to scrub a hard disk. > > > > Examine the lines: > > > > /* if ( (fd = open("/dev/da12s1c",O_RDWR)) < 0 ) { */ > > if ( (fd = open("/mnt/foo",O_RDWR)) < 0 ) { > > > > > > If I newfs the 'a' partition of da12s1 (a is the same as 'c'), mount > > it as /mnt, touch the file foo and then run the program it works fine. > > > > If instead I open the c partition (as in the commented out line), > > the open succeeds, the lseek succeeds but the writes fail with an > > error saying read only filesystem. > > > > Why ?? > > > > I want to scrub the whole disk, not just write to a file. > > > > -- > > Matthew Thyer Phone: +61 8 8259 7249 > > Science Corporate Information Systems Fax: +61 8 8259 5537 > > Defence Science and Technology Organisation, Salisbury > > PO Box 1500 Salisbury South Australia 5108 > > > > #include > > #include > > #include > > > > #include > > #include > > > > #define BUFSIZE 8192 > > > > > > main() > > { > > /* program to write 1's and 0's to disk */ > > > > off_t result; > > long int i; > > long int nwrite; > > long int count; > > int passes; > > int fd; > > char buf0[BUFSIZE], buf1[BUFSIZE]; > > > > /* initialize write buffers */ > > > > for (i=0; i < BUFSIZE; i++) { > > buf0[i] = 0; > > buf1[i] = 1; > > } > > > > /* if ( (fd = open("/dev/da12s1c",O_RDWR)) < 0 ) { */ > > if ( (fd = open("/mnt/foo",O_RDWR)) < 0 ) { > > perror("open"); > > exit(1); > > } > > > > /* write alternating 1s and zeros to disk */ > > > > for (i = 1; i <= 5; i++) { > > > > /* rewind to start file partition */ > > if ((result = lseek(fd, 0L, SEEK_SET)) != 0) { > > perror("lseek"); > > exit(1); > > } > > count = 0L; > > do { > > > > if ( (nwrite = write(fd, buf0, BUFSIZE)) != BUFSIZE) { > > printf("wrote last %ld bytes to disk\n",nwrite); > > printf("Total bytes written were %ld bytes\n", > > BUFSIZE*count + nwrite); > > perror("write"); > > } > > else { > > ++count; > > if ( count % 1000 == 0) > > printf("overwrote %ld bytes w/ 0s\n", > > BUFSIZE*count); > > } > > > > } while ( nwrite == BUFSIZE && nwrite > 0 ); > > > > /* rewind to start file partition */ > > if ((result = lseek(fd, 0L, SEEK_SET)) != 0) { > > perror("lseek"); > > exit(1); > > } > > count = 0L; > > > > do { > > if ( (nwrite = write(fd, buf1, BUFSIZE)) != BUFSIZE) { > > printf("wrote last %ld bytes to disk\n",nwrite); > > printf("Total bytes written were %ld bytes\n", > > BUFSIZE*count + nwrite); > > perror("write"); > > } > > else { > > ++count; > > if ( count % 1000 == 0) > > printf("overwrote %ld bytes w/ 1s\n", > > BUFSIZE*count); > > } > > > > } while ( nwrite == BUFSIZE && nwrite > 0 ); > > > > printf("Pass %d complete\n",i); > > } > > printf("All passes complete\n"); > > } -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 14:55:41 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 14:55:40 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id B99E737B400 for ; Thu, 7 Dec 2000 14:55:39 -0800 (PST) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA24379; Thu, 7 Dec 2000 17:55:30 -0500 (EST) Message-ID: <20001207175530.A23355@netmonger.net> Date: Thu, 7 Dec 2000 17:55:30 -0500 From: Christopher Masto To: Charlie Root , Doug Ambrisko Cc: Warner Losh , Wes Peters , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <3A2F02BB.2882A98A@MexComUSA.Net>; from Charlie Root on Wed, Dec 06, 2000 at 07:23:40PM -0800 Sender: chris@cheddar.netmonger.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 07:23:40PM -0800, Charlie Root wrote: > There is definately a trend to lower prices. I just found this. A > new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia > cards for $699. The access point sounds interesting. I personally > would like to use it as a repeater and network bridge. I am told that the Apple "AirPort Base Station", which is $399, works well and can be configured with the Java-based thing in the ports collection. I am further told that the Lucent/ORiNOCO RG-1000 base station is virtually identical, although more expensive and somehow inferior, although I don't understand the exact inferiorities. I am thinking of getting one of these things, despite my strong desire to avoid owning such a stupid looking piece of hardware. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Dec 7 15:20:32 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 15:20:29 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id D5C6437B400 for ; Thu, 7 Dec 2000 15:20:28 -0800 (PST) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.11.0/8.11.0) with ESMTP id eB7NKQq75847 for ; Thu, 7 Dec 2000 15:20:27 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.11.1/8.11.1) with ESMTP id eB7NKQs10420 for ; Thu, 7 Dec 2000 15:20:26 -0800 (PST) (envelope-from nsayer@sftw.com) Sender: nsayer@sftw.com Message-ID: <3A301B3A.BAE367AA@sftw.com> Date: Thu, 07 Dec 2000 15:20:26 -0800 From: Nick Sayer Reply-To: nsayer@kfu.com X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Lucent Orinoco Gold PCCard? References: <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > > On Wed, Dec 06, 2000 at 07:23:40PM -0800, Charlie Root wrote: > > There is definately a trend to lower prices. I just found this. A > > new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia > > cards for $699. The access point sounds interesting. I personally > > would like to use it as a repeater and network bridge. > > I am told that the Apple "AirPort Base Station", which is $399, works > well and can be configured with the Java-based thing in the ports > collection. I am further told that the Lucent/ORiNOCO RG-1000 base > station is virtually identical, although more expensive and somehow > inferior, although I don't understand the exact inferiorities. It is inferior in two ways: 1. If you change the location string from "Lucent ORiNOCCO RG-1000", the Lucent configurator will no longer find it. 2. You can't change the network name. If you try, the first few characters will be overwritten with the hex number on the sticker next time you start it up. 3. You can't change the community name (that is, the configuration password) with the Lucent software. They count on the encryption to keep naughty folks from reconfiguring it, but they took no steps to prevent reconfiguration from the wired side. #3 is particularly damning. I look forward to the CERT advisories that talk about script kiddies changing the encryption key and community name as a DOS attack on these things. If I had one of these, the first thing I would do is ditch their crappy software and set it up with the Java one in the ports, changing the community name in the process. > I am thinking of getting one of these things, despite my strong desire > to avoid owning such a stupid looking piece of hardware. Get an Airport instead. There's certainly no good reason not to, so long as Apple takes no steps to invalidate the Java configurator. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 16: 5:54 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 16:05:52 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 26CDF37B400 for ; Thu, 7 Dec 2000 16:05:52 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB80Ew900494; Thu, 7 Dec 2000 16:14:58 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012080014.eB80Ew900494@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Thyer Cc: "John W. De Boskey" , freebsd-current@freebsd.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition In-reply-to: Your message of "Fri, 08 Dec 2000 08:43:36 +1030." <3A300B90.F20A6120@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Dec 2000 16:14:58 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > CC: to -current as that's what I'm running. > > "John W. De Boskey" wrote: > > > > Hi, > > > > I can't answer your questions directly, but you might want > > to checkout the sources to newfs (/usr/src/sbin/newfs/newfs.c or > > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/newfs/newfs.c?annotate=1.31 > > line 417). > > > > I'll be glad to review your program if you would like. > > I'm not after a review, I'd like FreeBSD-CURRENT fixed. > > The program works on Compaq True64 UNIX v 4.0d > It also works on Solaris 7 (only tested sparc). > > So it seems FreeBSD is broken here. FreeBSD just behaves differently. If you want to write to the whole disk, open the whole-disk device, not the 'c' partition. -- ... 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 Thu Dec 7 16: 9:23 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 16:09:21 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id E192E37B400 for ; Thu, 7 Dec 2000 16:09:19 -0800 (PST) Received: by kbtfw.kubota.co.jp; id JAA06843; Fri, 8 Dec 2000 09:09:07 +0900 (JST) Received: from unknown(133.253.122.4) by kbtfw.kubota.co.jp via smap (V4.2) id xma006779; Fri, 8 Dec 00 09:08:37 +0900 Received: from ktkl129.tk.kubota.co.jp (IDENT:root@kbtgk.eto.kubota.co.jp [133.253.122.3]) by kbtmk.eto.kubota.co.jp (8.11.1/8.11.1) with ESMTP id eB808bl20401; Fri, 8 Dec 2000 09:08:37 +0900 (JST) Received: from jkpc15.tk.kubota.co.jp by ktkl129.tk.kubota.co.jp (8.6.13+2.4W/3.4W3-97053016) id JAA01835; Fri, 8 Dec 2000 09:07:10 +0900 Received: from localhost (localhost.tk.kubota.co.jp [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.11.1/3.7W-02/21/99) with ESMTP id eB8074h10697; Fri, 8 Dec 2000 09:07:04 +0900 (JST) To: shocking@houston.rr.com Cc: current@freebsd.org Subject: Re: cvs-cur.6925.gz appears to be corrupt In-Reply-To: <200012062120.eB6LKNG31523@bloop.craftncomp.com> References: <200012062120.eB6LKNG31523@bloop.craftncomp.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001208090704L.haro@tk.kubota.co.jp> Date: Fri, 08 Dec 2000 09:07:04 +0900 From: Munehiro Matsuda X-Dispatcher: imput version 20000228(IM140) Lines: 33 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Stephen Hocking Date: Wed, 06 Dec 2000 15:20:23 -0600 ::With ::# ctm -b /cvs cvs-cur.6925.gz :: ::I get :: :: FR: /cvs/CVSROOT/history md5 mismatch. ::cvs-cur.6925.gz Fatal error: Corrupt patch. ::Expected "\n" but didn't find it {20}. ::ctm: exit(96) :: :: Anybody like to comment? It's fine with me. BTW, I got my cvs delta through ctm-cvs-cur mailing list, and here's the check sum for it. $ ls -l cvs-cur.6925.gz -rw-r--r-- 1 daemon wheel 24114 Dec 6 19:34 cvs-cur.6925.gz $ md5 cvs-cur.6925.gz MD5 (cvs-cur.6925.gz) = 7751af95fb0821338f3bcc948348dd8d $ You may have a corrupted delta? =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 16:19:48 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 16:19:46 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from sm10.texas.rr.com (sm10.texas.rr.com [24.93.35.222]) by hub.freebsd.org (Postfix) with ESMTP id 9B27B37B400 for ; Thu, 7 Dec 2000 16:19:45 -0800 (PST) Received: from bleep.craftncomp.com (cs2777-167.houston.rr.com [24.27.77.167]) by sm10.texas.rr.com (8.11.0/8.11.1) with ESMTP id eB80HA101495; Thu, 7 Dec 2000 18:17:10 -0600 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id eB80JWG15038; Thu, 7 Dec 2000 18:19:32 -0600 (CST) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id eB80JhG46504; Thu, 7 Dec 2000 18:19:43 -0600 (CST) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200012080019.eB80JhG46504@bloop.craftncomp.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Munehiro Matsuda Cc: current@freebsd.org Subject: Re: cvs-cur.6925.gz appears to be corrupt In-Reply-To: Message from Munehiro Matsuda of "Fri, 08 Dec 2000 09:07:04 +0900." <20001208090704L.haro@tk.kubota.co.jp> Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Dec 2000 18:19:43 -0600 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's fine with me. > BTW, I got my cvs delta through ctm-cvs-cur mailing list, and here's > the check sum for it. > > $ ls -l cvs-cur.6925.gz > -rw-r--r-- 1 daemon wheel 24114 Dec 6 19:34 cvs-cur.6925.gz > $ md5 cvs-cur.6925.gz > MD5 (cvs-cur.6925.gz) = 7751af95fb0821338f3bcc948348dd8d > $ > > You may have a corrupted delta? > What it was from was that my history file's checksum didn't match what the ctm file thought it was supposed to be. I managed to force it through using "ctm -F ..." I'd done some weird stuff checking out files before, which caused the history file to be splattered. As it was only going to be removed, I figured that it didn't matter what was in it. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 16:40: 8 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 16:40:01 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D708837B401 for ; Thu, 7 Dec 2000 16:39:57 -0800 (PST) Received: from laptop.baldwin.cx (root@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB80dD735111; Thu, 7 Dec 2000 16:39: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: <5.0.2.1.2.20001206210835.00ada270@pozo.com> Date: Thu, 07 Dec 2000 16:40:02 -0800 (PST) From: John Baldwin To: Manfred Antar Subject: RE: Current kernel build failure -- >>cam_periph.c Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-00 Manfred Antar wrote: > At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: > >>On 07-Dec-00 John Baldwin wrote: >>> >>> On 07-Dec-00 Manfred Antar wrote: >>>> >>>> >>>> I've been trying to build a current kernel from current sources for a day >>>> now >>>> and I keep getting this: >>> >>> I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() >>> compiles in dozens of other places just fine (and has for months now). >> >>Nope, it was a sublte bug in the 486 optimized mutex operations, which had >>invalid register constraints probably dating back to several older revisions >>in >>BSD/OS before we got the code. It should be fixed now. >> > > John > It compiles now fine but panics on booting: > Doing initial network setup: hostname. > panic: mutex sched lock owned at ../../kern/kern_mutex.c:322 > cpuid = 0; lapic.id = 00000000 > boot() called on cpu#0 Hmmmmmm. I haven't reproduced this here. Let me play with it some more. -- 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 Dec 7 16:44: 3 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 16:43:58 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR22-166.accesscable.net [24.138.22.166]) by hub.freebsd.org (Postfix) with ESMTP id A91F037B400 for ; Thu, 7 Dec 2000 16:43:57 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id eB80gdw40312; Thu, 7 Dec 2000 20:42:39 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Dec 2000 20:42:33 -0400 (AST) From: The Hermit Hacker To: "Rogier R. Mulhuijzen" Cc: growfs@tomsoft.com, freebsd-current@FreeBSD.ORG Subject: Re: growfs(8) for FreeBSD In-Reply-To: <4.3.2.7.0.20001207213006.00be4600@mail.drwilco.net> 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 Erk, I fear you mis-understand ... FreeBSD has a feature called 'VINUM', which is a volume manager ... basically, it allows you to create RAID or Stripe'd file systems (or concat ones) ... what growfs allows is someone to add an n+1 drive to their RAID/Stripe and increase the size of the file system by that drive, without having to backup the drive, re-format and then restore ... I've used Solaris' version and have been much waiting for it to become available under FreeBSD ... On Thu, 7 Dec 2000, Rogier R. Mulhuijzen wrote: > Is it also capable of shrinking filesystems? I've sometimes wanted to grow > my /var or / slice using space freed by shrinking /usr (on a default > partitioned disk). Up to now I've solved it through symlinks, but that > doesn't really deserve the beauty award. I'd imagine a lot of new users > wouldn't mind being able to change partition size on a fully configured > machine without having to resort to backup, reslice, restore.... > > Anyways, sounds like a very handy tool already! > > Just my $0,02 > > DocWilco > > At 10:34 7-12-00 -0800, you wrote: > >Hi, > > > >Due to vinum it is no problem to add disks and grow your volumes but up to > >now you couldn't easily make use of that new space for a file system, except > >using sequence of ufsdump/newfs/ufsrestore or something similar. > > > >Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8) > >for FreeBSD. Currently we can only grow unmounted file systems (in a clean > >state) without any active snapshots inside. It is foreseen to enhance > >growfs to > >grow mounted file systems as well, and handle active snapshots correctly. > >This requires some infrastructure which is then only available in FreeBSD-5, > >whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3 > >(tested) and possibly even on FreeBSD-2 (untested). > > > >To help us gathering the needed data for fixing bugs in growfs we additionally > >wrote ffsinfo(8), a (very) extended version of dumpfs. > > > >We've sent a couple of snapshots of our code to Kirk McKusick and to Greg > >Lehey. Greg also volunteered :-) for reviewing the code. We also maintain > >some sort of (for some contractual reasons unilaterally) contact with Don > >Coleman who is doing the same thing for BSD/OS. > > > >-- > >Ciao > > > > > > Christoph &:-) > > > > > > > >M$: Where do you want to go today? > >Linux: Where do you want to go tomorrow? > >FreeBSD: Are you guys comming, or what? > > > > > >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 > 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 Thu Dec 7 16:55:12 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 16:55:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id BE50737B400; Thu, 7 Dec 2000 16:55:07 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 0B076573F5; Thu, 7 Dec 2000 18:55:30 -0600 (CST) Date: Thu, 7 Dec 2000 18:55:29 -0600 From: "Michael C . Wu" To: growfs@tomsoft.com Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: growfs(8) for FreeBSD Message-ID: <20001207185529.A59719@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , growfs@tomsoft.com, freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG References: <20001207103444.B25381@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: <20001207103444.B25381@freebsd.org>; from chm@freebsd.org on Thu, Dec 07, 2000 at 10:34:44AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 07, 2000 at 10:34:44AM -0800, Christoph Herrmann scribbled: | Due to vinum it is no problem to add disks and grow your volumes but up to | now you couldn't easily make use of that new space for a file system, except | using sequence of ufsdump/newfs/ufsrestore or something similar. | | Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8) | for FreeBSD. Currently we can only grow unmounted file systems (in a clean | state) without any active snapshots inside. It is foreseen to enhance growfs to | grow mounted file systems as well, and handle active snapshots correctly. | This requires some infrastructure which is then only available in FreeBSD-5, | whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3 | (tested) and possibly even on FreeBSD-2 (untested). | | To help us gathering the needed data for fixing bugs in growfs we additionally | wrote ffsinfo(8), a (very) extended version of dumpfs. Could you please put the code up somewhere that we can also look at? -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 17:13:54 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 17:13:52 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id B8B6137B400; Thu, 7 Dec 2000 17:13:48 -0800 (PST) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id eB81EBQ07011; Fri, 8 Dec 2000 11:44:11 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Fri, 8 Dec 2000 11:43:06 +1030 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id LAA05282; Fri, 8 Dec 2000 11:39:10 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id WZWR8S5Y; Fri, 8 Dec 2000 11:39:09 +1030 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id LAA22415; Fri, 8 Dec 2000 11:39:09 +1030 (CST) Sender: thyerm@dsto.defence.gov.au Message-ID: <3A3034D2.B57C2692@dsto.defence.gov.au> Date: Fri, 08 Dec 2000 11:39:38 +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 Smith Cc: "John W. De Boskey" , freebsd-current@freebsd.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition References: <200012080014.eB80Ew900494@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > The program works on Compaq True64 UNIX v 4.0d > > It also works on Solaris 7 (only tested sparc). > > > > So it seems FreeBSD is broken here. > > FreeBSD just behaves differently. If you want to write to the whole > disk, open the whole-disk device, not the 'c' partition. Thanks Mike, /dev/da18 works fine for me although I notice that /dev/da18s1 does not. There seems to be some inconcistencies in this area. Please tell me (and for the benefit of the list) as to why I cant use /dev/da18s1c ? Note that the disk has been set up with "fdisk -I da18" and then "disklabel -wr da18s1". -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 17:44:41 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 17:44:39 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id AB77D37B401 for ; Thu, 7 Dec 2000 17:44:38 -0800 (PST) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA10754 for ; Thu, 7 Dec 2000 17:44:37 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id DAA06871; Fri, 8 Dec 2000 03:44:30 +0200 (EET) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id DAA17656; Fri, 8 Dec 2000 03:44:29 +0200 (EET) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> Date: Fri, 8 Dec 2000 03:44:28 +0200 To: freebsd-stable@freebsd.or, freebsd-current@freebsd.org Subject: ffs_valloc: dup alloc panics with stable/current X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: Tomi.Vainio@finland.sun.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System is working quite well but under heavier load we start to get scsi errors from luns. sense = 4 asc = 3 asq = 0 sense = 1 asc = 3 asq = 0 sense = 3 asc = 12 asq = 0 sense = 3 asc = 11 asq = 0 This is not so bad but 5-30 minutes after this command system will always panic. cd /uu ; dump 0buf 126 - /w | restore xbf 126 - mode = 0100644, inum = 720391, fs = /uu panic: ffs_valloc: dup alloc syncing disks... 82 40 16 2 2 1 1 1 done Uptime: 29m30s mlx0: flushing cache...done mlxd0: detached mlxd1: detached mlxd2: detached -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 17:45: 7 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 17:45:05 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id E82F737B400 for ; Thu, 7 Dec 2000 17:45:01 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB81sFN00538; Thu, 7 Dec 2000 17:54:15 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012080154.eB81sFN00538@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Thyer Cc: "John W. De Boskey" , freebsd-current@freebsd.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition In-reply-to: Your message of "Fri, 08 Dec 2000 11:39:38 +1030." <3A3034D2.B57C2692@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Dec 2000 17:54:15 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > The program works on Compaq True64 UNIX v 4.0d > > > It also works on Solaris 7 (only tested sparc). > > > > > > So it seems FreeBSD is broken here. > > > > FreeBSD just behaves differently. If you want to write to the whole > > disk, open the whole-disk device, not the 'c' partition. > > Thanks Mike, /dev/da18 works fine for me although I notice that > /dev/da18s1 does not. There seems to be some inconcistencies > in this area. That would be something of an understatement... > Please tell me (and for the benefit of the list) as to why > I cant use /dev/da18s1c ? The 'c' device won't let you overwrite the beginning of the slice/disk, since that's where the partition information is kept. -- ... 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 Thu Dec 7 17:50:30 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 17:50:28 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id EC5E437B401 for ; Thu, 7 Dec 2000 17:50:25 -0800 (PST) Received: (from newton@localhost) by gizmo.internode.com.au (8.11.0/8.9.3) id eB81n9V81115; Fri, 8 Dec 2000 12:19:09 +1030 (CST) (envelope-from newton) Date: Fri, 8 Dec 2000 12:19:09 +1030 From: Mark Newton To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: ffs_valloc: dup alloc panics with stable/current Message-ID: <20001208121909.D80963@internode.com.au> References: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: newton@gizmo.internode.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 03:44:28AM +0200, Tomi Vainio - Sun Finland - wrote: > sense = 3 asc = 11 asq = 0 > This is not so bad but 5-30 minutes after this command system will > always panic. Are you surprised? The system is complaining that it's having intermittent difficulty accessing the disk, so it shouldn't be at all surprising that you'd have disk corruption problems as a result. Start by checking your SCSI cabling and termination. Almost all SCSI problems boil down to that eventually. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 18: 8:17 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 18:08:15 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id 6327837B400 for ; Thu, 7 Dec 2000 18:08:15 -0800 (PST) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA19862; Thu, 7 Dec 2000 18:08:07 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id EAA07021; Fri, 8 Dec 2000 04:08:04 +0200 (EET) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id EAA17675; Fri, 8 Dec 2000 04:08:03 +0200 (EET) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14896.17027.235917.443139@ultrahot.Finland.Sun.COM> Date: Fri, 8 Dec 2000 04:08:03 +0200 To: Mark Newton Cc: freebsd-current@freebsd.org Subject: Re: ffs_valloc: dup alloc panics with stable/current In-Reply-To: <20001208121909.D80963@internode.com.au> References: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> <20001208121909.D80963@internode.com.au> X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: Tomi.Vainio@finland.sun.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton writes: > > > sense = 3 asc = 11 asq = 0 > > This is not so bad but 5-30 minutes after this command system will > > always panic. > > Are you surprised? The system is complaining that it's having intermittent > difficulty accessing the disk, so it shouldn't be at all surprising that > you'd have disk corruption problems as a result. > > Start by checking your SCSI cabling and termination. Almost all SCSI > problems boil down to that eventually. > Sorry, but done that already. Mylex manual says this and this is how we did it. We also use force perfect terminators just to be sure evetrything works smoothly. System has complained a lot of drives 0:0 0:1 0:2 and these we had replaced twice also used low level formatting. ---clip clip--- Setting Device Termination Power All of the SCSI drives connected to the DAC960P Series should be shunted to apply power on the SCSI TERMPWR line, as well as having any of their builtin terminators disabled or removed. It is important that all drives supply termination power, so that power is applied to the SCSI bus even if drives are removed or replaced. The same rules also apply to non disk SCSI devices connected to any of the DAC960P Series SCSI channels. -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 18:13:41 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 18:13:37 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 4870B37B400; Thu, 7 Dec 2000 18:13:34 -0800 (PST) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id eB82DUX37145; Fri, 8 Dec 2000 12:43:30 +1030 (CST) (envelope-from grog) Date: Fri, 8 Dec 2000 12:43:30 +1030 From: Greg Lehey To: FreeBSD current users Cc: FreeBSD SMP list Subject: Hangs during 'make world -j4' on recent current Message-ID: <20001208124330.Z27667@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: grog@wantadilla.lemis.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For over a week now, I have been unable to complete a 'make world' on my -CURRENT box if I specify -j4. The system hangs and is completely unresponsive. This is a dual Celeron and an Abit BP6 motherboard. As far as I can tell, nobody knows what's causing this, nor even how to attack the problem. I'd like to solicit feedback about the extent of the problem, the possible causes, and how to debug it. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 19:18:59 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 19:18:57 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id E4DCC37B400; Thu, 7 Dec 2000 19:18:54 -0800 (PST) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id eB83JBQ14451; Fri, 8 Dec 2000 13:49:11 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Fri, 8 Dec 2000 13:48:10 +1030 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id NAA30998; Fri, 8 Dec 2000 13:44:19 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id WZWR848Y; Fri, 8 Dec 2000 13:44:19 +1030 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id NAA23269; Fri, 8 Dec 2000 13:44:18 +1030 (CST) Sender: thyerm@dsto.defence.gov.au Message-ID: <3A305227.D74011C4@dsto.defence.gov.au> Date: Fri, 08 Dec 2000 13:44:47 +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 Smith Cc: "John W. De Boskey" , freebsd-current@freebsd.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition References: <200012080154.eB81sFN00538@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Mike Smith wrote: > > > > The program works on Compaq True64 UNIX v 4.0d > > > > It also works on Solaris 7 (only tested sparc). > > > > > > > > So it seems FreeBSD is broken here. > > > > > > FreeBSD just behaves differently. If you want to write to the whole > > > disk, open the whole-disk device, not the 'c' partition. > > > > Thanks Mike, /dev/da18 works fine for me although I notice that > > /dev/da18s1 does not. There seems to be some inconcistencies > > in this area. > > That would be something of an understatement... > > > Please tell me (and for the benefit of the list) as to why > > I cant use /dev/da18s1c ? > > The 'c' device won't let you overwrite the beginning of the slice/disk, > since that's where the partition information is kept. > In the grand tradition of being allowed to shoot yourself in the foot, I would like to be able to do such things as this is clearly what I intend. Since we dont normally hold peoples hands for other things, why cant we allow big holes in my feet for this too ? Regardless /dev/da18s1 should work as for /dev/da18 I know... send patches... unfortunately my day job hasn't seen the light yet so I cant work on FreeBSD at work. -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 19:25:10 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 19:25:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR22-166.accesscable.net [24.138.22.166]) by hub.freebsd.org (Postfix) with ESMTP id 480B837B400 for ; Thu, 7 Dec 2000 19:25:07 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id eB83OHa00452 for ; Thu, 7 Dec 2000 23:24:17 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Dec 2000 23:24:17 -0400 (AST) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: Current CVS kernel panic ... 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 Just upgraded the kernel, rebooted and it hung/panic'd with: panic: spin lock sched lock held by 0x0xc02a73el for > 5 seconds cpuid = 1; lapic.id = 01000000 Debugger("panic") I have DDB enabled, and ctl-alt-esc doesn't break to the debugger, so its totally hung here ... dual-cpu celeron, smp enabled ... 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 Thu Dec 7 19:39:34 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 19:39:32 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id EF55C37B400 for ; Thu, 7 Dec 2000 19:39:31 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB83cp739981; Thu, 7 Dec 2000 19:38:51 -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: Thu, 07 Dec 2000 19:39:41 -0800 (PST) From: John Baldwin To: The Hermit Hacker Subject: Current Broken! Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-00 The Hermit Hacker wrote: > > Just upgraded the kernel, rebooted and it hung/panic'd with: > > panic: spin lock sched lock held by 0x0xc02a73el for > 5 seconds > cpuid = 1; lapic.id = 01000000 > Debugger("panic") > > I have DDB enabled, and ctl-alt-esc doesn't break to the debugger, so its > totally hung here ... > > dual-cpu celeron, smp enabled ... > > Marc G. Fournier ICQ#7615664 IRC Nick: > Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: > scrappy@{freebsd|postgresql}.org Yes. Something is broken with mutexes for the non-I386_CPU (and thus for SMP) case in -current with the latest commit to i386/include/mutex.h. Of course, you can revert that commit and then your kernel won't compile.... In the code I've looked at so far, it looks like possibly a weird register allocation bug in gcc and/or another weird nuance in the register constraints. In the specific case I am looking at, the mtx_exit() of Giant in STOPEVENT in syscall2() failed to properly release an unrecursed, uncontested Giant in mtx_exit() and fell through to mtx_exit_hard(), which assumes that Giant is either recursed or contested. When I disassembled the kernel and looked at the code, gcc assumed that when it looked up curproc for the mtx_enter() operation (which executed ok as far as I can tell), it could leave the value of curproc cached in %edi _across_ the call to the stopevent() function. My only guess is that %edi was clobbered during stopevent(), causing the cmpxchgl to fail, and throwing the code into mtx_exit_hard() when it shouldn't have. :( If anyone is an expert at register constraints, etc., please feel free to look at the macros in src/sys/i386/include/mutex.h -- 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 Dec 7 21: 7:35 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 21:07:29 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hcarp00g.ca.nortel.com (unknown [47.248.128.170]) by hub.freebsd.org (Postfix) with ESMTP id 4028237B400; Thu, 7 Dec 2000 21:07:28 -0800 (PST) Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.11.1/8.11.1) with ESMTP id eB848c835502; Thu, 7 Dec 2000 23:08:39 -0500 (EST) (envelope-from atrens@nortel.ca) Date: Thu, 7 Dec 2000 23:08:38 -0500 (EST) From: X-Sender: Reply-To: To: John Baldwin Cc: Subject: possibly related data point - (was) Re: Current Broken! 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 John, I'm not a constraints expert either, but I noticed that when I try to build a kernel WITHOUT any optimization, I get a failure in /usr/src/sys/i386/atomic.h . # make atomic.o cc -c -O0 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer /usr/src/sys/i386/i386/atomic.c In file included from /usr/src/sys/i386/i386/atomic.c:48: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:178: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_char': machine/atomic.h:179: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_char': machine/atomic.h:180: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_char': machine/atomic.h:181: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_short': machine/atomic.h:183: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_short': machine/atomic.h:184: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_short': machine/atomic.h:185: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_short': machine/atomic.h:186: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_int': machine/atomic.h:188: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_int': machine/atomic.h:189: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_int': machine/atomic.h:190: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_int': machine/atomic.h:191: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_long': machine/atomic.h:193: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_long': machine/atomic.h:194: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_long': machine/atomic.h:195: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_long': machine/atomic.h:196: inconsistent operand constraints in an `asm' *** Error code 1 with any optimization, eg -O, there is _NO_ error. Makes me think the optimizer is optimizing out the offending contraints. Ouch. Probably not what was intended. Maybe this is what's biting you ? I cut and pasted the cc command, inserted a -E, removed the #line directives, and captured the offending lines - since my mailer doesn't like really long lines, I've folded them - each function previously occupied a single line. void atomic_set_char (volatile u_char *p, u_char v){ __asm volatile ( "orb %b2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_clear_char (volatile u_char *p, u_char v){ __asm volatile ( "andb %b2,%0" : "=m" (*p) : "0" (*p), "ir" ( ~v )); } void atomic_add_char (volatile u_char *p, u_char v){ __asm volatile ( "addb %b2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_subtract_char (volatile u_char *p, u_char v){ __asm volatile ("subb %b2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_set_short (volatile u_short *p, u_short v){ __asm volatile ("orw %w2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_clear_short (volatile u_short *p, u_short v){ __asm volatile ("andw %w2,%0" : "=m" (*p) : "0" (*p), "ir" ( ~v )); } void atomic_add_short (volatile u_short *p, u_short v){ __asm volatile ("addw %w2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_subtract_short (volatile u_short *p, u_short v){ __asm volatile ("subw %w2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_set_int (volatile u_int *p, u_int v){ __asm volatile ("orl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_clear_int (volatile u_int *p, u_int v){ __asm volatile ("andl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( ~v )); } void atomic_add_int (volatile u_int *p, u_int v){ __asm volatile ("addl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_subtract_int (volatile u_int *p, u_int v){ __asm volatile ("subl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_set_long (volatile u_long *p, u_long v){ __asm volatile ("orl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_clear_long (volatile u_long *p, u_long v){ __asm volatile ("andl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( ~v )); } void atomic_add_long (volatile u_long *p, u_long v){ __asm volatile ("addl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } void atomic_subtract_long (volatile u_long *p, u_long v){ __asm volatile ("subl %2,%0" : "=m" (*p) : "0" (*p), "ir" ( v )); } So there you have it. I'll step back now since I haven't done any x86 assembly since 1986 ... and this is readily reproduceable in -current. Hope this helps, Cheers, Andrew. On Thu, 7 Dec 2000, John Baldwin wrote: > Date: Thu, 07 Dec 2000 19:39:41 -0800 (PST) > From: John Baldwin > To: The Hermit Hacker > Cc: freebsd-current@FreeBSD.ORG > Subject: Current Broken! > > > On 08-Dec-00 The Hermit Hacker wrote: > > > > Just upgraded the kernel, rebooted and it hung/panic'd with: > > > > panic: spin lock sched lock held by 0x0xc02a73el for > 5 seconds > > cpuid = 1; lapic.id = 01000000 > > Debugger("panic") > > > > I have DDB enabled, and ctl-alt-esc doesn't break to the debugger, so its > > totally hung here ... > > > > dual-cpu celeron, smp enabled ... > > > > Marc G. Fournier ICQ#7615664 IRC Nick: > > Scrappy > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: > > scrappy@{freebsd|postgresql}.org > > Yes. Something is broken with mutexes for the non-I386_CPU (and thus for SMP) > case in -current with the latest commit to i386/include/mutex.h. Of course, > you can revert that commit and then your kernel won't compile.... In the code > I've looked at so far, it looks like possibly a weird register allocation bug > in gcc and/or another weird nuance in the register constraints. In the > specific case I am looking at, the mtx_exit() of Giant in STOPEVENT in > syscall2() failed to properly release an unrecursed, uncontested Giant in > mtx_exit() and fell through to mtx_exit_hard(), which assumes that Giant is > either recursed or contested. When I disassembled the kernel and looked at the > code, gcc assumed that when it looked up curproc for the mtx_enter() operation > (which executed ok as far as I can tell), it could leave the value of curproc > cached in %edi _across_ the call to the stopevent() function. My only guess is > that %edi was clobbered during stopevent(), causing the cmpxchgl to fail, and > throwing the code into mtx_exit_hard() when it shouldn't have. :( > > If anyone is an expert at register constraints, etc., please feel free to look > at the macros in src/sys/i386/include/mutex.h > > -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Berkeley had what we called "copycenter", which is "take it down to the copy center and make as many copies as you want". -- Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 7 22:14:14 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 22:14:12 2000 Return-Path: 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 0BE1737B400 for ; Thu, 7 Dec 2000 22:14:12 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA35909; Thu, 7 Dec 2000 22:14:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eB86E8T29100; Thu, 7 Dec 2000 22:14:08 -0800 (PST) (envelope-from obrien) Date: Thu, 7 Dec 2000 22:14:08 -0800 From: "David O'Brien" To: Matthew Thyer Cc: freebsd-current@freebsd.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition Message-ID: <20001207221408.A29041@dragon.nuxi.com> Reply-To: current@freebsd.org References: <200012080154.eB81sFN00538@mass.osd.bsdi.com> <3A305227.D74011C4@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A305227.D74011C4@dsto.defence.gov.au>; from Matthew.Thyer@dsto.defence.gov.au on Fri, Dec 08, 2000 at 01:44:47PM +1030 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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 01:44:47PM +1030, Matthew Thyer wrote: > Regardless /dev/da18s1 should work as for /dev/da18 Correct me if I'm wrong, but /dev/da18s1 would only work if you installed a true slice vs. a dedicated configuaation of the disk something like ``disklabel da18 auto''. -- -- 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 Dec 8 2:34:13 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 02:34:10 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 155EF37B400 for ; Fri, 8 Dec 2000 02:34:10 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8AhSF09030; Fri, 8 Dec 2000 02:43:28 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012081043.eB8AhSF09030@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Newton Cc: Tomi Vainio - Sun Finland - , freebsd-current@FreeBSD.ORG Subject: Re: ffs_valloc: dup alloc panics with stable/current In-reply-to: Your message of "Fri, 08 Dec 2000 12:19:09 +1030." <20001208121909.D80963@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 02:43:28 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Dec 08, 2000 at 03:44:28AM +0200, Tomi Vainio - Sun Finland - wrote: > > > sense = 3 asc = 11 asq = 0 > > This is not so bad but 5-30 minutes after this command system will > > always panic. > > Are you surprised? The system is complaining that it's having intermittent > difficulty accessing the disk, so it shouldn't be at all surprising that > you'd have disk corruption problems as a result. Actually, it's upstream from the RAID controller. There don't appear to be any actual complaints from the controller about read errors, so I'm a little skeptical that this is actually the "real" problem. > Start by checking your SCSI cabling and termination. Almost all SCSI > problems boil down to that eventually. The entire system; disks, controller, etc. is all pretty skanky by the sound of it. It wouldn't surprise me too much if the system is suffering eg. multiple-master data corruption, or straight out memory/cache errors. -- ... 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 Fri Dec 8 2:35:40 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 02:35:38 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 56F1637B400 for ; Fri, 8 Dec 2000 02:35:38 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8Aj0F10483; Fri, 8 Dec 2000 02:45:00 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012081045.eB8Aj0F10483@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tomi.Vainio@Sun.COM Cc: freebsd-stable@freebsd.or, freebsd-current@freebsd.org Subject: Re: ffs_valloc: dup alloc panics with stable/current In-reply-to: Your message of "Fri, 08 Dec 2000 03:44:28 +0200." <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 02:45:00 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it > with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with > three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). > All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System > is working quite well but under heavier load we start to get scsi > errors from luns. > sense = 4 asc = 3 asq = 0 > sense = 1 asc = 3 asq = 0 > sense = 3 asc = 12 asq = 0 > sense = 3 asc = 11 asq = 0 Your disks just aren't up to this sort of workload. > This is not so bad but 5-30 minutes after this command system will > always panic. > cd /uu ; dump 0buf 126 - /w | restore xbf 126 - > > mode = 0100644, inum = 720391, fs = /uu > panic: ffs_valloc: dup alloc This looks like memory or PCI data corruption. You don't say how you're generating this load, or what the motherboard is, but I suspect that you may have hardware issues here. One question - I assume you're not seeing any read error diagnostics from the Mylex driver (other than the disk errors?) -- ... 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 Fri Dec 8 2:39:20 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 02:39:17 2000 Return-Path: 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 E869F37B401 for ; Fri, 8 Dec 2000 02:39:16 -0800 (PST) Received: from fwd06.sul.t-online.com by mailout05.sul.t-online.com with smtp id 144Kvl-0002Wm-0D; Fri, 08 Dec 2000 11:39:09 +0100 Received: from neutron.cichlids.com (520050424122-0001@[62.225.193.28]) by fmrl06.sul.t-online.com with esmtp id 144Kvi-1gadKiC; Fri, 8 Dec 2000 11:39:06 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 4DECFAB12; Fri, 8 Dec 2000 11:39:09 +0100 (CET) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 685DE14A86; Fri, 8 Dec 2000 11:38:36 +0100 (CET) Date: Fri, 8 Dec 2000 11:38:36 +0100 To: The Hermit Hacker Cc: "Rogier R. Mulhuijzen" , growfs@tomsoft.com, freebsd-current@FreeBSD.ORG Subject: Re: growfs(8) for FreeBSD Message-ID: <20001208113836.B32113@cichlids.cichlids.com> Mail-Followup-To: alex@cichlids.cichlids.com, The Hermit Hacker , "Rogier R. Mulhuijzen" , growfs@tomsoft.com, freebsd-current@FreeBSD.ORG References: <4.3.2.7.0.20001207213006.00be4600@mail.drwilco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Thu, Dec 07, 2000 at 08:42:33PM -0400 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 Thus spake The Hermit Hacker (scrappy@hub.org): > > Stripe'd file systems (or concat ones) ... what growfs allows is someone > to add an n+1 drive to their RAID/Stripe and increase the size of the file No, vinum can do this alone. But you couldn't grow the _fs_ after that, so there was no use for this vinum feature. Now you can, not only on vinum volumes but also on usual harddisks and ccd devices. At least this is, what Christoph told me. A shrinking utility would be VERY nice, too. I would have use for this :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 3:20:42 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 03:20:41 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id A9BC037B400 for ; Fri, 8 Dec 2000 03:20:40 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id MAA21763 for freebsd-current@freebsd.org; Fri, 8 Dec 2000 12:20:33 +0100 (CET) (envelope-from kuku) Date: Fri, 8 Dec 2000 12:20:33 +0100 (CET) From: Christoph Kukulies Message-Id: <200012081120.MAA21763@gilberto.physik.rwth-aachen.de> To: freebsd-current@freebsd.org Subject: sys/mutex.h - compilation errors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsuped src , built world and tried to compile a new kernel. Presently compilation fails with error in ASM line 601 in ../../sys/mutex.h. Any ideas? (that code seems to be used by i4b sppp routines) -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 3:31:57 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 03:31:54 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id 3568337B402 for ; Fri, 8 Dec 2000 03:31:49 -0800 (PST) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id OAA79801; Fri, 8 Dec 2000 14:31:44 +0300 (MSK) From: Igor Timkin Message-Id: <200012081131.OAA79801@logger.gamma.ru> Subject: Re: Current CVS kernel panic ... In-Reply-To: "from The Hermit Hacker at Dec 7, 2000 11:24:17 pm" To: The Hermit Hacker Date: Fri, 8 Dec 2000 14:31:44 +0300 (MSK) Cc: 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 The same with 2xPIII-800: Booting [/boot/kernel/kernel]... Copyright (c) 1992-2000 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: Fri Dec 8 00:46:58 MSK 2000 ivt@newsfeed.gamma.ru:/usr/obj/usr/src/sys/NEWSFEED Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (801.82-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 [...] da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) SMP: AP CPU #1 Launched! Using /entropy as an entropy file vinum: loaded [*** system freeze and I try call ddb ***] ~[gw-msu]%break panic: spin lock sched lock held by 0x0xdb8f4840 for > 5 seconds [another reboot: panic: spin lock sched lock held by 0x0xdb8f4a60 for > 5 seconds] cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... done Uptime: 50s The Hermit Hacker writes: > > Just upgraded the kernel, rebooted and it hung/panic'd with: > > panic: spin lock sched lock held by 0x0xc02a73el for > 5 seconds > cpuid = 1; lapic.id = 01000000 > Debugger("panic") > > I have DDB enabled, and ctl-alt-esc doesn't break to the debugger, so its > totally hung here ... > > dual-cpu celeron, smp enabled ... > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 3:37:46 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 03:37:44 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (unknown [24.70.218.157]) by hub.freebsd.org (Postfix) with ESMTP id 835D737B400 for ; Fri, 8 Dec 2000 03:37:44 -0800 (PST) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 0E023BA7D; Fri, 8 Dec 2000 03:37:47 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: Christoph Kukulies Cc: freebsd-current@FreeBSD.ORG Subject: Re: sys/mutex.h - compilation errors In-Reply-To: Message from Christoph Kukulies of "Fri, 08 Dec 2000 12:20:33 +0100." <200012081120.MAA21763@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 03:37:46 -0800 From: Jake Burkholder Message-Id: <20001208113747.0E023BA7D@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I cvsuped src , built world and tried to compile a new kernel. > Presently compilation fails with error in ASM line 601 in ../../sys/mutex.h. > > Any ideas? > > (that code seems to be used by i4b sppp routines) This should be fixed, or at least worked around for a while. Re-cvsup and try again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 3:49:44 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 03:49:42 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id E514837B400 for ; Fri, 8 Dec 2000 03:49:41 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id MAA21894; Fri, 8 Dec 2000 12:49:37 +0100 (CET) (envelope-from kuku) Date: Fri, 8 Dec 2000 12:49:37 +0100 From: Christoph Kukulies To: Jake Burkholder Cc: Christoph Kukulies , freebsd-current@FreeBSD.ORG Subject: Re: sys/mutex.h - compilation errors Message-ID: <20001208124937.A21874@gil.physik.rwth-aachen.de> References: <20001208113747.0E023BA7D@io.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001208113747.0E023BA7D@io.yi.org>; from jburkhol@home.com on Fri, Dec 08, 2000 at 03:37:46AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 03:37:46AM -0800, Jake Burkholder wrote: > > > > I cvsuped src , built world and tried to compile a new kernel. > > Presently compilation fails with error in ASM line 601 in ../../sys/mutex.h. > > > > Any ideas? > > > > (that code seems to be used by i4b sppp routines) > > This should be fixed, or at least worked around for a while. > Re-cvsup and try again. Easier said than done with a broken isdn link (due to a system running an old kernel with new system binaries :) Could you tell me which files were related to that fix? mutex.h itself doesn't seem to be upgraded since Dec 1, so it may be some other essential header files? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 3:56:12 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 03:56:10 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (unknown [24.70.218.157]) by hub.freebsd.org (Postfix) with ESMTP id A50B837B400 for ; Fri, 8 Dec 2000 03:56:09 -0800 (PST) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 562F9BA7D; Fri, 8 Dec 2000 03:56:12 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: Christoph Kukulies Cc: freebsd-current@FreeBSD.ORG Subject: Re: sys/mutex.h - compilation errors In-Reply-To: Message from Christoph Kukulies of "Fri, 08 Dec 2000 12:49:37 +0100." <20001208124937.A21874@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 03:56:12 -0800 From: Jake Burkholder Message-Id: <20001208115612.562F9BA7D@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Dec 08, 2000 at 03:37:46AM -0800, Jake Burkholder wrote: > > > > > > I cvsuped src , built world and tried to compile a new kernel. > > > Presently compilation fails with error in ASM line 601 in ../../sys/mutex.h. > > > > > > Any ideas? > > > > > > (that code seems to be used by i4b sppp routines) > > > > This should be fixed, or at least worked around for a while. > > Re-cvsup and try again. > > Easier said than done with a broken isdn link (due to a system running an > old kernel with new system binaries :) oh joy :) > > Could you tell me which files were related to that fix? mutex.h itself doesn't > seem to be upgraded since Dec 1, so it may be some other essential > header files? Yeah, its pretty simple. We're having trouble with gcc generating bad code for inline asm in the mutexes, the fix is to use the un-optimized c versions of the mutex routines for now. This should get things compiling again: =================================================================== RCS file: /home/ncvs/src/sys/i386/include/mutex.h,v retrieving revision 1.15 retrieving revision 1.16 diff -u -p -r1.15 -r1.16 --- src/sys/i386/include/mutex.h 2000/12/07 02:23:16 1.15 +++ src/sys/i386/include/mutex.h 2000/12/08 05:03:34 1.16 @@ -26,7 +26,7 @@ * SUCH DAMAGE. * * from BSDI $Id: mutex.h,v 2.7.2.35 2000/04/27 03:10:26 cp Exp $ - * $FreeBSD: src/sys/i386/include/mutex.h,v 1.15 2000/12/07 02:23:16 jhb Exp $ + * $FreeBSD: src/sys/i386/include/mutex.h,v 1.16 2000/12/08 05:03:34 jhb Exp $ */ #ifndef _MACHINE_MUTEX_H_ @@ -69,7 +69,8 @@ extern char STR_SIEN[]; #define _V(x) __STRING(x) -#ifndef I386_CPU +#if 0 +/* #ifndef I386_CPU */ /* * For 486 and newer processors. > > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 5: 0: 4 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 05:00:01 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR22-166.accesscable.net [24.138.22.166]) by hub.freebsd.org (Postfix) with ESMTP id 4BD5337B400 for ; Fri, 8 Dec 2000 05:00:00 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id eB8CwWx06235; Fri, 8 Dec 2000 08:58:32 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Dec 2000 08:58:32 -0400 (AST) From: The Hermit Hacker To: Alexander Langer Cc: "Rogier R. Mulhuijzen" , growfs@tomsoft.com, freebsd-current@FreeBSD.ORG Subject: Re: growfs(8) for FreeBSD In-Reply-To: <20001208113836.B32113@cichlids.cichlids.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 Fri, 8 Dec 2000, Alexander Langer wrote: > Thus spake The Hermit Hacker (scrappy@hub.org): > > > > > Stripe'd file systems (or concat ones) ... what growfs allows is someone > > to add an n+1 drive to their RAID/Stripe and increase the size of the file > > No, vinum can do this alone. > > But you couldn't grow the _fs_ after that, so there was no use for > this vinum feature. Okay, that is what I said ... "add an n+1 drive to ... and increase the size of the file system" ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 5:29:25 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 05:29:23 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from oreise01.orkide.no (unknown [193.215.14.196]) by hub.freebsd.org (Postfix) with ESMTP id E1CA037B400 for ; Fri, 8 Dec 2000 05:29:22 -0800 (PST) Received: from 63.20.241.182 (1Cust182.tnt1.madison.wi.da.uu.net [63.20.241.182]) by oreise01.orkide.no with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id YHSL6FBJ; Fri, 8 Dec 2000 14:27:41 +0100 Message-ID: <00001d271697$000079da$00001dc6@> To: From: Martin@demokritos.cc.duth.gr Subject: Nothing on TV? Surf your way through 500 Channels! Date: Fri, 08 Dec 2000 20:32:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FREE Satellite T.V. System and FREE Installation For a limited time we'll give you this top of the line Digital Satellite System for FREE! We'll even include Free installation. Enjoy over 500 Channels of crystal clear digital picture and cd stereo sound on your FREE Satellite TV System. Why pay for these items in a retail store, when we're giving you the same satellite package for free. Call 888-514-6881 to be Guaranteed Your FREE Satellite Today This Innovative 20" Satellite includes a stereo receiver and an infrared remote. With this FREE offer you will have both Interactive Television Capability and an On Screen Program Guide. This limited time FREE offer is much less than the monthly cost of cable tv. All you have to do is call us to arrange delivery. If you call today, we'll throw in a second receiver for your second T.V. free. Call 888-514-6881 to Begin Surfing through 500 Channels Today! To be removed send email to zedspine@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 6:57:10 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 06:57:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id CB1DF37B400; Fri, 8 Dec 2000 06:57:07 -0800 (PST) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id XAA78320; Fri, 8 Dec 2000 23:57:39 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200012081457.XAA78320@shidahara1.planet.sci.kobe-u.ac.jp> To: Mike Smith Cc: acpi-jp@jp.freebsd.org, current@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi.c acpi_button.c acpi_ec.c acpi_isa.c acpi_lid.c acpi_pcib.c acpi_processor.c acpi_resource.c acpi_thermal.c acpi_timer.c acpiio.h acpivar.h In-reply-to: Your message of "Fri, 08 Dec 2000 01:16:21 PST." <200012080916.eB89GLa03357@freefall.freebsd.org> Date: Fri, 08 Dec 2000 23:57:39 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012080916.eB89GLa03357@freefall.freebsd.org>, Mike Smith $B$5$s$$(B $B$o$/(B: >msmith 2000/12/08 01:16:21 PST > > Modified files: > sys/dev/acpica acpi.c acpi_button.c acpi_ec.c acpi_isa.c > acpi_lid.c acpi_pcib.c acpi_processor.c > acpi_resource.c acpi_thermal.c > acpi_timer.c acpiio.h acpivar.h > Log: > - Convert a lot of homebrew debugging output to use the ACPI CA debugging > infrastructure. It's not perfect, but it's a lot better than what > we've been using so far. The following rules apply to this: > o BSD component names should be capitalised > o Layer names should be taken from the non-CA set for now. We > may elect to add some new BSD-specific layers later. I don't think this "infrastructure" is useful. As far as I experienced, the message is too noisy or too few infomation. $BEOJUB:5*(B $B?@8MBg3XBg3X1!<+A32J3X8&5f2J(BD3$B>pJs%a%G%#%"2J3X@l96(B Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 7: 9:50 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 07:09:46 2000 Return-Path: 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 1A27137B402; Fri, 8 Dec 2000 07:09:46 -0800 (PST) Received: from newsguy.com (p60-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.61]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA26149; Sat, 9 Dec 2000 00:09:35 +0900 (JST) Message-ID: <3A30F7FD.A6FA069D@newsguy.com> Date: Sat, 09 Dec 2000 00:02:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Matthew Thyer Cc: Mike Smith , "John W. De Boskey" , freebsd-current@FreeBSD.ORG Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition References: <200012080154.eB81sFN00538@mass.osd.bsdi.com> <3A305227.D74011C4@dsto.defence.gov.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > > > In the grand tradition of being allowed to shoot yourself in the foot, > I would like to be able to do such things as this is clearly what I > intend. Since we dont normally hold peoples hands for other things, > why cant we allow big holes in my feet for this too ? > > Regardless /dev/da18s1 should work as for /dev/da18 > > I know... send patches... unfortunately my day job hasn't seen the > light yet so I cant work on FreeBSD at work. No, and no. You misunderstand the problem. A disk on IBM PC compatible computers has the following format: | Partition table | Data | | Slice 1 | Slice 2 | Slice 3 | Slice 4 | | Disklabel | Data | | c | |a|b|f|g| The partition table divides the data in up to four slices. Each slice may have, under FreeBSD, a disklabel and have the rest of it divided into up to seven partitions, with one partition, c, representing the total data space. So da1 represents the whole disk, including partition table. da1s1 may or may not represent the whole data part of the disk (ie, whole disk minus partition table), because that's what da1s1 *is*, etc, etc, etc. This has nothing to do with preventing the user from shooting himself in the foot. This is just how the disk is, as a matter of fact, organized. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 7:20:32 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 07:20:31 2000 Return-Path: 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 6F60C37B400; Fri, 8 Dec 2000 07:20:30 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id E8CF42CE82; Fri, 8 Dec 2000 17:17:10 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id eB8FHID20279; Fri, 8 Dec 2000 17:17:18 +0200 (EET) (envelope-from vallo) Date: Fri, 8 Dec 2000 17:17:18 +0200 From: Vallo Kallaste To: "Daniel C. Sobral" Cc: Matthew Thyer , Mike Smith , "John W. De Boskey" , freebsd-current@FreeBSD.ORG Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition Message-ID: <20001208171718.A20246@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <200012080154.eB81sFN00538@mass.osd.bsdi.com> <3A305227.D74011C4@dsto.defence.gov.au> <3A30F7FD.A6FA069D@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A30F7FD.A6FA069D@newsguy.com>; from dcs@newsguy.com on Sat, Dec 09, 2000 at 12:02:21AM +0900 Sender: vallo@myhakas.matti.ee Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 12:02:21AM +0900, "Daniel C. Sobral" wrote: > No, and no. You misunderstand the problem. > > A disk on IBM PC compatible computers has the following format: > > | Partition table | Data | > | Slice 1 | Slice 2 | Slice 3 | Slice 4 | > | Disklabel | Data | > | c | > |a|b|f|g| [snip] Nice graph. I haven't looked at handbook and FAQ documents for a while, but I'll think it fits well into appropriate section. Any -doc takers please? -- 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 Fri Dec 8 7:56:43 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 07:56:41 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.6.9.33]) by hub.freebsd.org (Postfix) with ESMTP id 4E57137B400 for ; Fri, 8 Dec 2000 07:56:41 -0800 (PST) Received: from msgrel1.and.agilent.com (msgrel1.and.agilent.com [130.30.33.104]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 1090E5DB for ; Fri, 8 Dec 2000 08:56:37 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.and.agilent.com (Postfix) with ESMTP id 1441E18F for ; Fri, 8 Dec 2000 10:56:36 -0500 (EST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id HAA26344 for ; Fri, 8 Dec 2000 07:56:34 -0800 (PST) Message-Id: <200012081556.HAA26344@mina.soco.agilent.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? Reply-To: Darryl Okahata In-Reply-To: Your message of "Thu, 07 Dec 2000 15:20:26 PST." <3A301B3A.BAE367AA@sftw.com> Mime-Version: 1.0 (generated by tm-edit 1.6) Content-Type: text/plain; charset=US-ASCII Date: Fri, 08 Dec 2000 07:56:33 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Sayer wrote: > Christopher Masto wrote: > > > I am told that the Apple "AirPort Base Station", which is $399, works > > well and can be configured with the Java-based thing in the ports > > collection. I am further told that the Lucent/ORiNOCO RG-1000 base > > station is virtually identical, although more expensive and somehow > > inferior, although I don't understand the exact inferiorities. > > It is inferior in two ways: Also, there are other alternatives to the AirPort (which is closer to $299 than $399). One is the Buffalo AirStation (around $280-$340, depending on options -- see http://www.melcoinc.com/english/network/air.html). Other, cheaper, access points have been mentioned here in earlier messages. The AirStation is sold in the US by TechWorks (http://www.techworks.com) among possibly others. I've got an AirStation, and it's not bad. Like most access points, it has only 40-bit encryption, though. It's configurable via a web browser, using password-protected web pages. However, because of this, the configuration needs to be done via a secure, wired lan, as the web passwords are transmitted in plain text. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 8: 5:22 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 08:05:20 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from msgbas1t.cos.agilent.com (msgbas1tx.cos.agilent.com [192.6.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 62C9737B400 for ; Fri, 8 Dec 2000 08:05:20 -0800 (PST) Received: from msgrel1.and.agilent.com (msgrel1.and.agilent.com [130.30.33.104]) by msgbas1t.cos.agilent.com (Postfix) with ESMTP id CDBF020D for ; Fri, 8 Dec 2000 09:05:19 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.and.agilent.com (Postfix) with ESMTP id 6E9C2196 for ; Fri, 8 Dec 2000 11:05:18 -0500 (EST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id IAA26450 for ; Fri, 8 Dec 2000 08:05:17 -0800 (PST) Message-Id: <200012081605.IAA26450@mina.soco.agilent.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? In-Reply-To: Message from Darryl Okahata of "Fri, 08 Dec 2000 07:56:33 PST." <200012081556.HAA26344@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 08:05:16 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Also, there are other alternatives to the AirPort (which is closer > to $299 than $399). One is the Buffalo AirStation (around $280-$340, I forgot to mention that the AirStation supposedly supports roaming between access points. I haven't tried it, though. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 8:15:32 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 08:15:30 2000 Return-Path: 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 0A5A637B401; Fri, 8 Dec 2000 08:15:28 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA25143; Sat, 9 Dec 2000 03:15:22 +1100 Date: Sat, 9 Dec 2000 03:15:07 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Matthew Thyer Cc: Mike Smith , "John W. De Boskey" , freebsd-current@FreeBSD.ORG Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition In-Reply-To: <3A3034D2.B57C2692@dsto.defence.gov.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 On Fri, 8 Dec 2000, Matthew Thyer wrote: > Mike Smith wrote: > > > The program works on Compaq True64 UNIX v 4.0d > > > It also works on Solaris 7 (only tested sparc). > > > > > > So it seems FreeBSD is broken here. > > > > FreeBSD just behaves differently. If you want to write to the whole > > disk, open the whole-disk device, not the 'c' partition. > > Thanks Mike, /dev/da18 works fine for me although I notice that > /dev/da18s1 does not. There seems to be some inconcistencies > in this area. > > Please tell me (and for the benefit of the list) as to why > I cant use /dev/da18s1c ? Because metadata (i.e,. label) write protection actually works on /dev/da18s1c. It is supposed to be possible to turn off write protection using the DIOCWLABEL ioctl, but IIRC this only works if the data written over the label area is a valid label (if there is already a label there, as there must be for /dev/da18s1c to exist), so labels can't be cleared by writing zeros to them (zeros don't give a valid label). Labels can be cleared by zeroing them using the whole-disk device. All subdevices of the device should be closed before starting, and none except the whole-disk device should be opened before finishing, to ensure that the old in-core copy of the label isn't used. Someone broke dd(1) to always turn off write protection of labels, to hack around a bug in the alpha disklabel code (someone broke the label for the whole-disk device by making it a real label to hack around a non-understood bug that is said to break sysinstall; real labels are write protected, so the whole-disk device can't be used to bypass the write protection). Since overwriting labels doesn't work quite right even when write protection is turned off, I'm not sure how the breakage helps. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 8:19:54 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 08:19:49 2000 Return-Path: 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 1EEFD37B400; Fri, 8 Dec 2000 08:19:13 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eB8GJ8R13775; Fri, 8 Dec 2000 18:19:08 +0200 (EET) (envelope-from ru) Date: Fri, 8 Dec 2000 18:19:08 +0200 From: Ruslan Ermilov To: marcel@FreeBSD.org, Bruce Evans Cc: current@FreeBSD.org Subject: Bootstrapping issues with groff(1) Message-ID: <20001208181908.A12716@sunbay.com> Mail-Followup-To: marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: ru@whale.sunbay.crimea.ua Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! I have recently upgraded groff(1) to the latest released version. Groff(1) provides two kind of data files: device files (ones that installed into /usr/share/groff_font), and macro package files (ones that installed into /usr/share/tmac). New groff(1) versions are likely to supply new files of both types. The typical world build uses groff(1) to build documentation (which is later installed into /usr/share/doc). The attached patches (p4 and p5) try to solve this bootstrapping problem with groff(1). I have lightly tested this on my -stable box, and would appreciate a feedback on them. The p5 patch is for -current, and p4 is for -stable. There is still at least one issue not resolved with this patch. One can specify MANBUILDCAT=YES (does anyone have this?) to ask the system to build preformatted manual pages (see bsd.man.mk for details). This will use mdoc(7) and man(7) macro packages from /usr/share/tmac while they should be taken from ${WORLDTMP}/usr/share/tmac. 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 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p5 Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.179 diff -u -r1.179 Makefile.inc1 --- Makefile.inc1 2000/12/03 20:29:31 1.179 +++ Makefile.inc1 2000/12/08 16:02:05 @@ -168,6 +168,7 @@ COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \ LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \ OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \ + TRFLAGS="-F${WORLDTMP}/usr/share/groff_font -M${WORLDTMP}/usr/share/tmac" \ PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.6.0 # bootstrap-tool stage @@ -200,16 +201,6 @@ PATH=${STRICTTMPPATH}:${INSTALLTMP} IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1 -USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \ - usr/libexec/${OBJFORMAT} usr/sbin usr/share/misc - -.if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98" -USRDIRS+= usr/libexec/aout -.endif - -INCDIRS= arpa g++/std objc protocols readline rpc rpcsvc openssl \ - security ss - # # buildworld # @@ -224,7 +215,7 @@ .if !defined(NOCLEAN) rm -rf ${WORLDTMP} .else - for dir in bin games include lib sbin; do \ + for dir in bin games include lib sbin share; do \ rm -rf ${WORLDTMP}/usr/$$dir; \ done rm -f ${WORLDTMP}/sys @@ -232,12 +223,7 @@ # This is beyond dirty... rm -f ${OBJTREE}${.CURDIR}/gnu/usr.bin/cc/cc_tools/.depend .endif -.for _dir in ${USRDIRS} - mkdir -p ${WORLDTMP}/${_dir} -.endfor -.for _dir in ${INCDIRS} - mkdir -p ${WORLDTMP}/usr/include/${_dir} -.endfor + cd ${.CURDIR}; ${BMAKE} hierarchy ln -sf ${.CURDIR}/sys ${WORLDTMP}/sys @echo @echo "--------------------------------------------------------------" @@ -528,7 +514,7 @@ bootstrap-tools: .for _tool in ${_strfile} usr.bin/yacc usr.bin/colldef usr.sbin/config \ - gnu/usr.bin/gperf gnu/usr.bin/texinfo + gnu/usr.bin/gperf gnu/usr.bin/groff gnu/usr.bin/texinfo cd ${.CURDIR}/${_tool}; \ ${MAKE} obj; \ ${MAKE} depend; \ --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p4 Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.141.2.18 diff -u -r1.141.2.18 Makefile.inc1 --- Makefile.inc1 2000/12/01 21:58:09 1.141.2.18 +++ Makefile.inc1 2000/12/08 16:02:16 @@ -168,6 +168,7 @@ COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \ LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \ OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \ + TRFLAGS="-F${WORLDTMP}/usr/share/groff_font -M${WORLDTMP}/usr/share/tmac" \ PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.00503 # bootstrap-tool stage @@ -198,16 +199,6 @@ PATH=${STRICTTMPPATH}:${INSTALLTMP} IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1 -USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \ - usr/libexec/${OBJFORMAT} usr/sbin usr/share/misc - -.if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98" -USRDIRS+= usr/libexec/aout -.endif - -INCDIRS= arpa g++/std objc protocols readline rpc rpcsvc openssl \ - security ss - # # buildworld # @@ -222,7 +213,7 @@ .if !defined(NOCLEAN) rm -rf ${WORLDTMP} .else - for dir in bin games include lib sbin; do \ + for dir in bin games include lib sbin share; do \ rm -rf ${WORLDTMP}/usr/$$dir; \ done rm -f ${WORLDTMP}/sys @@ -230,12 +221,7 @@ # This is beyond dirty... rm -f ${OBJTREE}${.CURDIR}/gnu/usr.bin/cc/cc_tools/.depend .endif -.for _dir in ${USRDIRS} - mkdir -p ${WORLDTMP}/${_dir} -.endfor -.for _dir in ${INCDIRS} - mkdir -p ${WORLDTMP}/usr/include/${_dir} -.endfor + cd ${.CURDIR}; ${BMAKE} hierarchy ln -sf ${.CURDIR}/sys ${WORLDTMP}/sys @echo @echo "--------------------------------------------------------------" @@ -509,7 +495,7 @@ bootstrap-tools: .for _tool in ${_strfile} usr.bin/yacc usr.bin/colldef usr.sbin/config \ - gnu/usr.bin/gperf gnu/usr.bin/texinfo + gnu/usr.bin/gperf gnu/usr.bin/groff gnu/usr.bin/texinfo cd ${.CURDIR}/${_tool}; \ ${MAKE} obj; \ ${MAKE} depend; \ --EVF5PPMfhYS0aIcm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 8:21:27 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 08:21:25 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mgate04.so-net.ne.jp (mgate04.so-net.ne.jp [210.139.254.151]) by hub.freebsd.org (Postfix) with ESMTP id CBD2937B400 for ; Fri, 8 Dec 2000 08:21:24 -0800 (PST) Received: from mail.ta3.so-net.ne.jp (mspool07.so-net.ne.jp [210.139.254.186]) by mgate04.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W00120719) with ESMTP id BAA16446 for ; Sat, 9 Dec 2000 01:21:23 +0900 (JST) Received: from mail.ta3.so-net.ne.jp (pfa6ff0.tokynt01.ap.so-net.ne.jp [210.250.111.240]) by mail.ta3.so-net.ne.jp (8.9.3/3.7W99092111) with SMTP id BAA23128 for ; Sat, 9 Dec 2000 01:21:22 +0900 (JST) Date: Sat, 9 Dec 2000 01:21:22 +0900 (JST) Message-Id: <200012081621.BAA23128@mail.ta3.so-net.ne.jp> To: current@freebsd.org Subject: =?ISO-2022-JP?B?GyRCOiNMayRPJDMkQSRpJEcbKEI=?= From: Delivery Boy Mime-Version: 1.0 Content-Type: text/plain; Charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B$$$D$b$N7G<(HD!&=P2q$$!&%a!<%k%U%l%s%I%5%$%H$r$4MxMQBW$-(B $BM-$jFq$&$4$6$$$^$9!#(B $BK\F|$O?7$7$$%5%$%H$N$40FFb$r$5$;$FBW$-$^$9!#(B http://homepage2.nifty.com/degedock/mori/ $B$b$7!"$4ITMW$G$7$?$i:o=|$7$F2<$5$$!#(B $B:#8e!"$3$N$40FFb%a!<%k$4ITMW$N>l9g$O!"(B $B$*l9g$,$4$6$$$^$9!!$=$N:]$O$4MF!&$446A[$J$I!"$41sN8$J$/$3$A$i$^$G(B emd@ta3.so-net.ne.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 8:45:44 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 08:45:42 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 5E04737B401 for ; Fri, 8 Dec 2000 08:45:41 -0800 (PST) Received: by arg1.demon.co.uk (Postfix, from userid 300) id C6AB69B16; Fri, 8 Dec 2000 16:45:31 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id BE9205D0E; Fri, 8 Dec 2000 16:45:31 +0000 (GMT) Date: Fri, 8 Dec 2000 16:45:31 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Darryl Okahata Cc: freebsd-current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? In-Reply-To: <200012081605.IAA26450@mina.soco.agilent.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 Fri, 8 Dec 2000, Darryl Okahata wrote: > I wrote: > > > Also, there are other alternatives to the AirPort (which is closer > > to $299 than $399). One is the Buffalo AirStation (around $280-$340, > > I forgot to mention that the AirStation supposedly supports roaming > between access points. I haven't tried it, though. Almost all APs support roaming, because they'd have to go out of their way to prevent it: roaming is controlled from the client end. Most clients seem to just implement the "wait until contact is lost with the current AP then scan for a new one" scheme, though cleverer approaches are possible. Roaming between AirPort and AirStation APs certainly works. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 9:17:11 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 09:17:09 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id AA57037B400; Fri, 8 Dec 2000 09:17:08 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 144R8s-0001sS-00; Fri, 08 Dec 2000 17:17:06 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eB8HGjv07306; Fri, 8 Dec 2000 18:16:45 +0100 (CET) (envelope-from wkb) Date: Fri, 8 Dec 2000 18:16:45 +0100 From: Wilko Bulte To: Mike Smith Cc: Tomi.Vainio@Sun.COM, freebsd-stable@freebsd.or, freebsd-current@freebsd.org Subject: Re: ffs_valloc: dup alloc panics with stable/current Message-ID: <20001208181645.E6118@freebie.demon.nl> References: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> <200012081045.eB8Aj0F10483@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200012081045.eB8Aj0F10483@mass.osd.bsdi.com>; from msmith@freebsd.org on Fri, Dec 08, 2000 at 02:45:00AM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 02:45:00AM -0800, Mike Smith wrote: > > We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it > > with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with > > three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). > > All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System > > is working quite well but under heavier load we start to get scsi > > errors from luns. > > sense = 4 asc = 3 asq = 0 > > sense = 1 asc = 3 asq = 0 > > sense = 3 asc = 12 asq = 0 > > sense = 3 asc = 11 asq = 0 > > Your disks just aren't up to this sort of workload. > > > This is not so bad but 5-30 minutes after this command system will > > always panic. > > cd /uu ; dump 0buf 126 - /w | restore xbf 126 - > > > > mode = 0100644, inum = 720391, fs = /uu > > panic: ffs_valloc: dup alloc > > This looks like memory or PCI data corruption. You don't say how you're > generating this load, or what the motherboard is, but I suspect that you > may have hardware issues here. PCI bus clock is at the nominal speed? Can be a source of interesting effects. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 9:24:24 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 09:24:22 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0F35637B400 for ; Fri, 8 Dec 2000 09:24:22 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB8HNh756713; Fri, 8 Dec 2000 09:23:43 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eB8HNjw74497; Fri, 8 Dec 2000 09:23:45 -0800 (PST) (envelope-from jhb) 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: Fri, 08 Dec 2000 09:23:45 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: atrens@nortel.ca Subject: RE: possibly related data point - (was) Re: Current Broken! Cc: current@FreeBSD.ORG Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-00 atrens@nortel.ca wrote: > > John, > > I'm not a constraints expert either, but I noticed that when I try to > build a kernel WITHOUT any optimization, I get a failure in > > /usr/src/sys/i386/atomic.h . Compiling a kernel with anything but -O for optimization is not supported. gcc has produced buggy code for the -O0 case in the past. -- 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 Dec 8 10: 8:15 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 10:08:12 2000 Return-Path: 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 E46EC37B401 for ; Fri, 8 Dec 2000 10:08:11 -0800 (PST) Received: from nairobi-22.budapest.interware.hu ([195.70.50.214] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 144RwH-0006V5-00 for ; Fri, 08 Dec 2000 19:08:10 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A31236B.23501A47@elischer.org> Date: Fri, 08 Dec 2000 10:07:39 -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: current@freebsd.org Subject: __asm help.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to write some experimental mutex operations similar to those in -current, but to do differnt things (e.g. a read/write lock) however, I am having some problems with the __asm stuff. What I want to do is to define some operations that will assemble down to: pushfl cli [stuff] popfl I can generate the code, but it seems to me that there should be a way of telling gcc that you have just pushed an item onto the stack, so that if you were to have some C code between the push and po (of the flags reg) the compiler has a correct idea of where the SP is. I can imagine that it doesn't matter so it may be that there is no constaint for that purpose (I read the gcc asm info pages) but I wanted to make sure that that is the case because if it does turn out to be important, it may manifest itself as a wierd bug sometime in 2002. The current pushfl code in the kernel has the following: __asm __volatile("pushfl; popl %0" : "=r" (ef)); which has no long term effect on the stack pointer so I cannot use it as a guide. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ 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 Dec 8 10:20: 8 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 10:20:05 2000 Return-Path: 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 BCCC837B401 for ; Fri, 8 Dec 2000 10:20:05 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB8IJYH20561; Fri, 8 Dec 2000 10:19:34 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Dec 2000 10:19:34 -0800 (PST) From: Matt Dillon Message-Id: <200012081819.eB8IJYH20561@earth.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: __asm help.. References: <3A31236B.23501A47@elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm trying to write some experimental mutex operations similar to those :in -current, but to do differnt things (e.g. a read/write lock) :however, I am having some problems with the __asm stuff. : :What I want to do is to define some operations that will :assemble down to: : pushfl : cli : [stuff] : popfl : :I can generate the code, but it seems to me that there should be :a way of telling gcc that you have just pushed an item onto the stack, :so that if you were to have some C code between the push and po :(of the flags reg) the compiler has a correct idea of where the :SP is. I can imagine that it doesn't matter so it may be that there :is no constaint for that purpose (I read the gcc asm info pages) :but I wanted to make sure that that is the case because if it does turn :out to be important, it may manifest itself as a wierd bug sometime :in 2002. : :The current pushfl code in the kernel has the following: : __asm __volatile("pushfl; popl %0" : "=r" (ef)); :which has no long term effect on the stack pointer so I cannot :use it as a guide. : :-- : __--_|\ Julian Elischer I think all you can do is move the addresses and data used by 'stuff' into registers prior to the push, then manipulate the registers between the push and the pop. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 10:42:21 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 10:42:19 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hcarp00g.ca.nortel.com (unknown [47.248.133.243]) by hub.freebsd.org (Postfix) with ESMTP id 1322A37B401; Fri, 8 Dec 2000 10:42:19 -0800 (PST) Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.11.1/8.11.1) with ESMTP id eB8HhX875995; Fri, 8 Dec 2000 12:43:35 -0500 (EST) (envelope-from atrens@nortel.ca) Date: Fri, 8 Dec 2000 12:43:33 -0500 (EST) From: X-Sender: Reply-To: To: John Baldwin Cc: "Atrens, Andrew [SKY:ET95:EXCH]" , Subject: RE: possibly related data point - (was) Re: Current Broken! 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 I hit on it by accident (I normally compile with -O). That said, your claim that gcc with no optimization generates incorrect code is kind of counter-intuitive, wouldn't you say ? I think you missed my point, I was just illustrating that optimizer seems to affect (in my case apparently negate) the processing of constraints. What you take from that is up to you - I was just trying to be helpful :) Cheers, A. +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Berkeley had what we called "copycenter", which is "take it down to the copy center and make as many copies as you want". -- Kirk McKusick +-- --+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 10:46:54 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 10:46:52 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4D1EC37B400 for ; Fri, 8 Dec 2000 10:46:52 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB8IkG759676; Fri, 8 Dec 2000 10:46:16 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eB8IkJv75081; Fri, 8 Dec 2000 10:46:19 -0800 (PST) (envelope-from jhb) 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: <3A31236B.23501A47@elischer.org> Date: Fri, 08 Dec 2000 10:46:18 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Julian Elischer Subject: RE: __asm help.. Cc: current@FreeBSD.ORG Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-00 Julian Elischer wrote: > I'm trying to write some experimental mutex operations similar to those > in -current, but to do differnt things (e.g. a read/write lock) > however, I am having some problems with the __asm stuff. > > What I want to do is to define some operations that will > assemble down to: > pushfl > cli > [stuff] > popfl > > I can generate the code, but it seems to me that there should be > a way of telling gcc that you have just pushed an item onto the stack, > so that if you were to have some C code between the push and po > (of the flags reg) the compiler has a correct idea of where the > SP is. I can imagine that it doesn't matter so it may be that there > is no constaint for that purpose (I read the gcc asm info pages) > but I wanted to make sure that that is the case because if it does turn > out to be important, it may manifest itself as a wierd bug sometime > in 2002. As long as gcc uses %ebp to address local variables and functoin parameters rather than %esp you should be fine. %esp will be preserved, but if %esp is for some odd reason used to address a variable during the C code, you are hosed. Just use foo = save_intr(); disable_intr(); .. restore_intr() for now. If you want to save the 2 instructions so badly, then you should probably be writing the whole chunk in assembly. Getting it correct first and optimizing later is more sane than getting correctness and optimization at the same time and not knowing which one your bugs are coming from. -- 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 Dec 8 10:51:14 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 10:51:12 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0662D37B400 for ; Fri, 8 Dec 2000 10:51:12 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB8InL759722; Fri, 8 Dec 2000 10:49:21 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eB8InN775114; Fri, 8 Dec 2000 10:49:23 -0800 (PST) (envelope-from jhb) 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: Fri, 08 Dec 2000 10:49:23 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: atrens@nortel.ca Subject: RE: possibly related data point - (was) Re: Current Broken! Cc: current@FreeBSD.ORG, Atrens@foo.osd.bsdi.com, "Andrew [SKY:ET95:EXCH]" Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-00 atrens@nortel.ca wrote: > > I hit on it by accident (I normally compile with -O). That said, your > claim that gcc with no optimization generates incorrect code is > kind of counter-intuitive, wouldn't you say ? I've seen it do weird things with -O0 (mostly with C++). :) It's just another program. Nothing is keeping it from having bugs. :) > I think you missed my point, I was just illustrating that optimizer seems > to affect (in my case apparently negate) the processing of constraints. I am back now to thinking that it is a gcc bug in the -O case now as well. The constraings I removed were in fact valid, so I've put them back in, but just disabled the macros for now until gcc is fixed. > What you take from that is up to you - I was just trying to be helpful :) Sorry if I came across as if I was biting your head off, that was not the intent. > Cheers, > > A. -- 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 Dec 8 11:23:10 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 11:23:07 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from vic.cioe.com (vic.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 2738B37B400 for ; Fri, 8 Dec 2000 11:23:07 -0800 (PST) Received: from ny1wsh031 (blackhole.cioe.com [204.120.165.44]) by vic.cioe.com (8.11.1/8.11.1) with SMTP id eB8JN6j68457 for ; Fri, 8 Dec 2000 14:23:06 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <02fc01c0614c$4a789880$8a1a050a@winstar.com> From: "Steven E. Ames" To: References: Subject: Current Locking up... Re: possibly related data point - (was) Re: Current Broken! Date: Fri, 8 Dec 2000 14:23:05 -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.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 -CURRENT as of yesterday was still causing my system to lock (with 'make -j8 world'). Lock=no possibility of debugger. I have two of these systems and they behave identically. If someone with lots more debugging experience would benefit from borrowing one of the machines I'd happily send it to you. I'd really like to be use SMP stabily. -Steve ----- Original Message ----- From: "John Baldwin" To: Cc: ; ; "Andrew [SKY:ET95:EXCH]" Sent: Friday, December 08, 2000 1:49 PM Subject: RE: possibly related data point - (was) Re: Current Broken! > > On 08-Dec-00 atrens@nortel.ca wrote: > > > > I hit on it by accident (I normally compile with -O). That said, your > > claim that gcc with no optimization generates incorrect code is > > kind of counter-intuitive, wouldn't you say ? > > I've seen it do weird things with -O0 (mostly with C++). :) It's just another > program. Nothing is keeping it from having bugs. :) > > > I think you missed my point, I was just illustrating that optimizer seems > > to affect (in my case apparently negate) the processing of constraints. > > I am back now to thinking that it is a gcc bug in the -O case now as well. The > constraings I removed were in fact valid, so I've put them back in, but just > disabled the macros for now until gcc is fixed. > > > What you take from that is up to you - I was just trying to be helpful :) > > Sorry if I came across as if I was biting your head off, that was not the > intent. > > > Cheers, > > > > A. > > -- > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 11:46:25 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 11:46:23 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn230.dh.casema.net [212.64.31.230]) by hub.freebsd.org (Postfix) with ESMTP id 62AD837B400 for ; Fri, 8 Dec 2000 11:46:21 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id eB8K3cl04122; Fri, 8 Dec 2000 21:03:44 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 08 Dec 2000 20:45:54 +0100 To: The Hermit Hacker From: "Rogier R. Mulhuijzen" Subject: Re: growfs(8) for FreeBSD Cc: freebsd-current@freebsd.org, growfs@tomsoft.com In-Reply-To: References: <20001208113836.B32113@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Stripe'd file systems (or concat ones) ... what growfs allows is someone > > > to add an n+1 drive to their RAID/Stripe and increase the size of the > file > > > > No, vinum can do this alone. > > > > But you couldn't grow the _fs_ after that, so there was no use for > > this vinum feature. > >Okay, that is what I said ... "add an n+1 drive to ... and increase the >size of the file system" ... I still don't see why growfs wouldn't work on a non-vinum volume. It's just a manipulation of the FS, not of the underlying device. But let's leave this for the makers of growfs to answer shall we =) And yes I know about Vinum, and I know what it can do. =) DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 12:20:52 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 12:20:49 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guru.cit-ua.net (office.radio.vostok.net [194.44.7.187]) by hub.freebsd.org (Postfix) with SMTP id B531A37B400 for ; Fri, 8 Dec 2000 12:20:45 -0800 (PST) Received: (qmail 18985 invoked by uid 107); 8 Dec 2000 22:20:39 +0200 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Dec 2000 22:20:39 +0200 Date: Fri, 8 Dec 2000 22:20:39 +0200 (EET) From: Sergey Vishnevetskiy To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Cc: serg@guru.cit-ua.net Subject: SkyStar driver 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 Hello! There were rumors about such driver in CURRENT. Is it true? Please keep CC, cause I'm not subscribed to these lists. Thanks in advance for an answer. Sergiy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 12:33: 6 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 12:33:04 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id D5ACD37B400 for ; Fri, 8 Dec 2000 12:33:03 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8KgKF01901; Fri, 8 Dec 2000 12:42:20 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012082042.eB8KgKF01901@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Takanori Watanabe Cc: acpi-jp@jp.freebsd.org, current@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi.c acpi_button.c acpi_ec.c acpi_isa.c acpi_lid.c acpi_pcib.c acpi_processor.c acpi_resource.c acpi_thermal.c acpi_timer.c acpiio.h acpivar.h In-reply-to: Your message of "Fri, 08 Dec 2000 23:57:39 +0900." <200012081457.XAA78320@shidahara1.planet.sci.kobe-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 12:42:20 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Modified files: > > sys/dev/acpica acpi.c acpi_button.c acpi_ec.c acpi_isa.c > > acpi_lid.c acpi_pcib.c acpi_processor.c > > acpi_resource.c acpi_thermal.c > > acpi_timer.c acpiio.h acpivar.h > > Log: > > - Convert a lot of homebrew debugging output to use the ACPI CA debugging > > infrastructure. It's not perfect, but it's a lot better than what > > we've been using so far. The following rules apply to this: > > o BSD component names should be capitalised > > o Layer names should be taken from the non-CA set for now. We > > may elect to add some new BSD-specific layers later. > > I don't think this "infrastructure" is useful. As far as I experienced, > the message is too noisy or too few infomation. I've been very slowly coming around to like it. It's important to pick your debugging options carefully, and to be prepared to wade through thousands of lines of output (a serial console is mandatory). However, I've been careful to keep the BSD parts separate from the ACPI CA parts, so you can just turn on the BSD-related debugging without getting the eleven bazillion mutex operations, etc logged. I also added the ! support *specifically* so that I can turn lots of stuff on, and then turn the really noisy and useless stuff off again. But most importantly, I didn't have anything better up my sleeve. If you've got a better integrated debugging infrastructure, I'm all ears. 8) -- ... 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 Fri Dec 8 12:43:25 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 12:43:24 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id B102A37B400 for ; Fri, 8 Dec 2000 12:43:23 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8KqiF01972; Fri, 8 Dec 2000 12:52:44 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012082052.eB8KqiF01972@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: current@freebsd.org Subject: Re: __asm help.. In-reply-to: Your message of "Fri, 08 Dec 2000 10:07:39 PST." <3A31236B.23501A47@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 12:52:44 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to write some experimental mutex operations similar to those > in -current, but to do differnt things (e.g. a read/write lock) > however, I am having some problems with the __asm stuff. Julian; Wheels were invented around 1500BC. We don't need to go through all that again. -- ... 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 Fri Dec 8 13: 4: 4 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 13:04:02 2000 Return-Path: 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 4397737B400; Fri, 8 Dec 2000 13:04:01 -0800 (PST) Received: from gaborone-59.budapest.interware.hu ([195.70.52.187] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 144UgQ-0004wW-00; Fri, 08 Dec 2000 22:03:58 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A314CA3.6B5A8FA1@elischer.org> Date: Fri, 08 Dec 2000 13:03:31 -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: Mike Smith Cc: current@freebsd.org Subject: Re: __asm help.. References: <200012082052.eB8KqiF01972@mass.osd.bsdi.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > I'm trying to write some experimental mutex operations similar to those > > in -current, but to do differnt things (e.g. a read/write lock) > > however, I am having some problems with the __asm stuff. > > Julian; Wheels were invented around 1500BC. We don't need to go through > all that again. I'm doing it not for inclusion but for education. And in any case they may have been invented already but we don't HAVE suitable read/write locks in FreeBSD.. only the 'lock mangler' which is certainly not going to su[[ly me with locks for netgraph. > > -- > ... 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 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ 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 Dec 8 13:29:24 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 13:29:23 2000 Return-Path: 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 4350937B400; Fri, 8 Dec 2000 13:29:23 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB8LTMM22955; Fri, 8 Dec 2000 13:29:22 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Dec 2000 13:29:22 -0800 (PST) From: Matt Dillon Message-Id: <200012082129.eB8LTMM22955@earth.backplane.com> To: John Baldwin Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: RE: __asm help.. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :As long as gcc uses %ebp to address local variables and functoin parameters :rather than %esp you should be fine. %esp will be preserved, but if %esp is :for some odd reason used to address a variable during the C code, you are hosed. I strongly recommend against making assumptions about GCC's use of %ebp vs %esp... not if you want the __asm code to survive the GCC optimizer! :Just use foo = save_intr(); disable_intr(); .. restore_intr() for now. If you :want to save the 2 instructions so badly, then you should probably be writing :the whole chunk in assembly. Getting it correct first and optimizing later is :more sane than getting correctness and optimization at the same time and not :knowing which one your bugs are coming from. : :John Baldwin -- http://www.FreeBSD.org/~jhb/ Yah, gotta agree there. The only thing that matters, Julian, are memory accesses. The number of instructions you use is irrelevant. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 13:40:44 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 13:40:43 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from msp-65-25-230-128.mn.rr.com (msp-65-25-230-128.mn.rr.com [65.25.230.128]) by hub.freebsd.org (Postfix) with ESMTP id 9878637B400 for ; Fri, 8 Dec 2000 13:40:42 -0800 (PST) Received: by msp-65-25-230-128.mn.rr.com (Postfix, from userid 501) id 89D9B2667C; Fri, 8 Dec 2000 15:40:36 -0600 (CST) Date: Fri, 8 Dec 2000 15:40:36 -0600 From: Goblin To: "Rogier R. Mulhuijzen" Cc: freebsd-current@freebsd.org, growfs@tomsoft.com Subject: Re: growfs(8) for FreeBSD Message-ID: <20001208154036.A645@msp-65-25-230-128.yahoo.com> References: <20001208113836.B32113@cichlids.cichlids.com> <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net>; from drwilco@drwilco.nl on Fri, Dec 08, 2000 at 08:45:54PM +0100 Sender: z3rk@msp-65-25-230-128.mn.rr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can certainly see where "cat /dev/<1GBdevice> > /dev/<10GBdevice>" situations would make a growfs useful w/out vinum... And, removing a failing disk from the end of a a vinum concat volume would make shrinkfs really nice. On 12/08, Rogier R. Mulhuijzen rearranged the electrons to read: > > > > > Stripe'd file systems (or concat ones) ... what growfs allows is someone > > > > to add an n+1 drive to their RAID/Stripe and increase the size of the > > file > > > > > > No, vinum can do this alone. > > > > > > But you couldn't grow the _fs_ after that, so there was no use for > > > this vinum feature. > > > >Okay, that is what I said ... "add an n+1 drive to ... and increase the > >size of the file system" ... > > I still don't see why growfs wouldn't work on a non-vinum volume. It's just > a manipulation of the FS, not of the underlying device. But let's leave > this for the makers of growfs to answer shall we =) > > And yes I know about Vinum, and I know what it can do. =) > > DocWilco > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 14:39:43 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 14:39:42 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id D30F037B400 for ; Fri, 8 Dec 2000 14:39:41 -0800 (PST) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA78955; Fri, 8 Dec 2000 17:39:32 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Fri, 8 Dec 2000 17:39:32 -0500 (EST) From: "Brandon D. Valentine" To: "Daniel C. Sobral" Cc: FreeBSD-CURRENT Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition In-Reply-To: <3A30F7FD.A6FA069D@newsguy.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 Sat, 9 Dec 2000, Daniel C. Sobral wrote: >No, and no. You misunderstand the problem. > >A disk on IBM PC compatible computers has the following format: > >| Partition table | Data | > | Slice 1 | Slice 2 | Slice 3 | Slice 4 | > | Disklabel | Data | > | c | > |a|b|f|g| That is really an excellent diagram. That should be in an FAQ somewhere. Doc committers? -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 14:44:24 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 14:44:22 2000 Return-Path: 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 9A2C237B400 for ; Fri, 8 Dec 2000 14:44:21 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eB8MiEL81428; Fri, 8 Dec 2000 23:44:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Brandon D. Valentine" Cc: "Daniel C. Sobral" , FreeBSD-CURRENT Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition In-Reply-To: Your message of "Fri, 08 Dec 2000 17:39:32 EST." Date: Fri, 08 Dec 2000 23:44:14 +0100 Message-ID: <81426.976315454@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Br andon D. Valentine" writes: >On Sat, 9 Dec 2000, Daniel C. Sobral wrote: > >>No, and no. You misunderstand the problem. >> >>A disk on IBM PC compatible computers has the following format: >> >>| Partition table | Data | >> | Slice 1 | Slice 2 | Slice 3 | Slice 4 | >> | Disklabel | Data | >> | c | >> |a|b|f|g| > >That is really an excellent diagram. That should be in an FAQ >somewhere. Doc committers? Except it is not actually correct. The BSD disklabel is usually inside the 'a' partition and certainly inside the 'c' -- 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 Fri Dec 8 14:59:12 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 14:59:08 2000 Return-Path: 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 911E937B6AA for ; Fri, 8 Dec 2000 14:57:13 -0800 (PST) Received: (qmail 18750 invoked from network); 8 Dec 2000 22:52:00 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 8 Dec 2000 22:52:00 -0000 Received: (qmail 13002 invoked from network); 8 Dec 2000 22:57:07 -0000 Received: from unknown (HELO dsl081-020-229-sea1.dsl-isp.net) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 8 Dec 2000 22:57:07 -0000 Received: (from tomdean@localhost) by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.9.3) id eB8Mv6G02715; Fri, 8 Dec 2000 14:57:06 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Fri, 8 Dec 2000 14:57:06 -0800 (PST) Message-Id: <200012082257.eB8Mv6G02715@dsl081-020-229-sea1.dsl-isp.net> X-Authentication-Warning: dsl081-020-229-sea1.dsl-isp.net: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: current@FreeBSD.ORG Subject: Problem With Man Formatting Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since a 12/6 cvsup and 'make world', I notice a problem with the output of man. The output consists of one block of justified text. The headers, etc., are missing. Have I missed something? tomdean # man man formats and displays the on-line manual pages. This version knows about the and environment variables, so you can have your own set(s) of personal man pages and choose whatever program you like to display the formatted pages. If section is specified, man only looks in that section of the manual. You may also spec- ify the order to search the sections for entries and which pre- processors to run on the source files via command line options or ... sor before nroff. If is set, its value is used to determine which manual sections to search. If is set, its value is used as the name of the program to use to display the man page. By default, is used. Normally, to look at the relevant manpage information for getopt, one would use: However, when referring to a specific section of the manual, such as one would use: The option only works if a troff-like program is installed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 15: 8:14 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:08:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 469EC37B6FC for ; Fri, 8 Dec 2000 15:05:04 -0800 (PST) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA79208; Fri, 8 Dec 2000 18:05:01 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Fri, 8 Dec 2000 18:05:01 -0500 (EST) From: "Brandon D. Valentine" To: "Thomas D. Dean" Cc: current@FreeBSD.ORG Subject: Re: Problem With Man Formatting In-Reply-To: <200012082257.eB8Mv6G02715@dsl081-020-229-sea1.dsl-isp.net> 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 Fri, 8 Dec 2000, Thomas D. Dean wrote: >Since a 12/6 cvsup and 'make world', I notice a problem with the >output of man. The output consists of one block of justified text. >The headers, etc., are missing. Could this be a result of the recent groff upgrade? -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 15:28:31 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:28:28 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.Netz-Werker.NET (SRV1.Netz-Werker.NET [195.122.150.66]) by hub.freebsd.org (Postfix) with ESMTP id D7B2B37B400 for ; Fri, 8 Dec 2000 15:28:27 -0800 (PST) Received: (from tomsoft@localhost) by mail.Netz-Werker.NET (8.8.8/8.8.8) id AAA18025; Sat, 9 Dec 2000 00:28:22 +0100 (CET) (envelope-from tomsoft) Message-ID: <20001209002821.58836@Netz-Werker.NET> Date: Sat, 9 Dec 2000 00:28:21 +0100 From: Thomas To: "Rogier R. Mulhuijzen" Cc: scrappy@hub.org, freebsd-current@freebsd.org, growfs@tomsoft.com Subject: Re: growfs(8) for FreeBSD References: <20001208113836.B32113@cichlids.cichlids.com> <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net>; from Rogier R. Mulhuijzen on Fri, Dec 08, 2000 at 08:45:54PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, In an attempt to resolve that discussion: > > > No, vinum can do this alone. > > > But you couldn't grow the _fs_ after that, so there was no use for > > > this vinum feature. Exactly that was the motivation for writing that utility > >Okay, that is what I said ... "add an n+1 drive to ... and increase the > >size of the file system" ... ... which means basically the same :-) > I still don't see why growfs wouldn't work on a non-vinum volume. It's just > a manipulation of the FS, not of the underlying device. But let's leave > this for the makers of growfs to answer shall we =) again correct, technically it is possible to use growfs on ANY object which has a ufs filesystem structure: vinum volume, a partition on a disk, ccd device, even a flat file provided, that there is some space on the end(!) of that medium which is not yet taken by the ufs structures. So you can use it either with hardware RAID controllers which allow for non destructive extending of the size of existing volumes at the end(!). As well you can use it for vinum volumes. Currently this is only possible for mirrored plexes of any kind, or unmirrored concatenated plexes. All other devices cant be changed without destroying the contents. And you can just give some space in the partition table (disklabel) to an existing partition (at its end) and let the filesystem grow within that bound. A shrinkfs is NOT written. The design allows for writing it, but we currently consider other features much more important, like * growing a mounted filesystem * handling file systems with active snapshots is in * grow in a way that we are always safe to loose the power during the growing (softdep concept) * handle byteorder correct on non intel platform (we don't have any alpha hardware but think ufs on alpha is not ufs on intel) * provide the current funktionality on FreeBSD-4 at least, maybe FreeBSD-3 Thomas -- Th.-H.v.Kamptz Die Netz-Werker GmbH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 15:34: 8 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:34:06 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id EB83137B400; Fri, 8 Dec 2000 15:34:05 -0800 (PST) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA26680; Fri, 8 Dec 2000 15:34:02 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id BAA23742; Sat, 9 Dec 2000 01:33:59 +0200 (EET) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id BAA00961; Sat, 9 Dec 2000 01:33:58 +0200 (EET) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14897.28646.3200.459030@ultrahot.Finland.Sun.COM> Date: Sat, 9 Dec 2000 01:33:58 +0200 To: freebsd-current@FreeBSD.ORG Cc: msmith@FreeBSD.ORG, wkb@freebie.demon.nl Subject: Re: ffs_valloc: dup alloc panics with stable/current In-Reply-To: <200012081045.eB8Aj0F10483@mass.osd.bsdi.com> References: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> <200012081045.eB8Aj0F10483@mass.osd.bsdi.com> X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: Tomi.Vainio@finland.sun.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > This is not so bad but 5-30 minutes after this command system will > > always panic. > > cd /uu ; dump 0buf 126 - /w | restore xbf 126 - > > > > mode = 0100644, inum = 720391, fs = /uu > > panic: ffs_valloc: dup alloc > > This looks like memory or PCI data corruption. You don't say how you're > generating this load, or what the motherboard is, but I suspect that you > may have hardware issues here. > /w fs contains cvsupped FreeBSD source, objs and ports alltogether 1G of data. Load test is this simple "cd /uu ; dump 0buf 126 - /w | restore xbf 126 -" between two partitions. First motherboard we tried was Intel PPro 200Mhz (FX440 based I think/Natoma?). Second one is newer 633MHz Celeron system but I don't know manufacturer. > One question - I assume you're not seeing any read error diagnostics from > the Mylex driver (other than the disk errors?) > Sometimes we have got more those scsi errors before fs panic. Wilko Bulte writes: > > PCI bus clock is at the nominal speed? Can be a source of interesting > effects. > Both motherboards are used with standard settings and older Intel PPro system don't support overclocking or other kludge stuff. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 15:34:55 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:34:54 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101]) by hub.freebsd.org (Postfix) with ESMTP id 97F1D37B400 for ; Fri, 8 Dec 2000 15:34:53 -0800 (PST) Received: (from dmaddox@localhost) by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eB8NZJi01291; Fri, 8 Dec 2000 18:35:19 -0500 (EST) (envelope-from dmaddox) Date: Fri, 8 Dec 2000 18:35:19 -0500 From: "Donald J . Maddox" To: "Brandon D. Valentine" Cc: "Thomas D. Dean" , current@FreeBSD.ORG Subject: Re: Problem With Man Formatting Message-ID: <20001208183519.B1210@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: "Brandon D. Valentine" , "Thomas D. Dean" , current@FreeBSD.ORG References: <200012082257.eB8Mv6G02715@dsl081-020-229-sea1.dsl-isp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bandix@looksharp.net on Fri, Dec 08, 2000 at 06:05:01PM -0500 Return-Receipt-To: dmaddox@sc.rr.com Sender: dmaddox@cae88-102-101.sc.rr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think so... I am -current as of yesterday and my manpages are displaying just fine, headers and all. On Fri, Dec 08, 2000 at 06:05:01PM -0500, Brandon D. Valentine wrote: > On Fri, 8 Dec 2000, Thomas D. Dean wrote: > > >Since a 12/6 cvsup and 'make world', I notice a problem with the > >output of man. The output consists of one block of justified text. > >The headers, etc., are missing. > > Could this be a result of the recent groff upgrade? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 15:42:50 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:42:48 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id F2E6637B400 for ; Fri, 8 Dec 2000 15:42:47 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8NpWF02835; Fri, 8 Dec 2000 15:51:37 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012082351.eB8NpWF02835@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas Cc: "Rogier R. Mulhuijzen" , scrappy@hub.org, freebsd-current@freebsd.org, growfs@tomsoft.com Subject: Re: growfs(8) for FreeBSD In-reply-to: Your message of "Sat, 09 Dec 2000 00:28:21 +0100." <20001209002821.58836@Netz-Werker.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 15:51:32 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So you can use it either with hardware RAID controllers which allow for > non destructive extending of the size of existing volumes at the end(!). Cool. We support the FlexRAID Virtual Sizing stuff on the AMI controllers already, and I bet that the Mylex MORE stuff would work too. > * handle byteorder correct on non intel platform (we don't have any > alpha hardware but think ufs on alpha is not ufs on intel) Actually, I believe they're the same; as long as you have used explicitly-sized types everywhere, you should be fine. -- ... 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 Fri Dec 8 15:43:44 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:43:41 2000 Return-Path: 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 575F037B400; Fri, 8 Dec 2000 15:43:40 -0800 (PST) Received: from mogadishu-35.budapest.interware.hu ([195.70.52.99] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 144XAv-0001yr-00; Sat, 09 Dec 2000 00:43:37 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A31720D.9A6CFF63@elischer.org> Date: Fri, 08 Dec 2000 15:43:09 -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: Matt Dillon Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: __asm help.. References: <200012082129.eB8LTMM22955@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > :As long as gcc uses %ebp to address local variables and functoin parameters > :rather than %esp you should be fine. %esp will be preserved, but if %esp is > :for some odd reason used to address a variable during the C code, you are hosed. > > I strongly recommend against making assumptions about GCC's use of %ebp vs > %esp... not if you want the __asm code to survive the GCC optimizer! > > :Just use foo = save_intr(); disable_intr(); .. restore_intr() for now. If you > :want to save the 2 instructions so badly, then you should probably be writing > :the whole chunk in assembly. Getting it correct first and optimizing later is > :more sane than getting correctness and optimization at the same time and not > :knowing which one your bugs are coming from. > : > :John Baldwin -- http://www.FreeBSD.org/~jhb/ > > Yah, gotta agree there. The only thing that matters, Julian, are memory > accesses. The number of instructions you use is irrelevant. foo = save_intr(); disable_intr(); .. restore_intr() has 4 extra memory accesses. pushf (the only way to save interrupt state) save to stack. save_intr() reads it back off the stack (ok a cache hit I suppose) and writes it to a memory location specied as an argument. (Not a cache hit..)(though maybe defered) After some processing, restore_intr() then reads it from the nominated address (probably a cache hit) and puts it on the stack. (not a cache hit). (though maybe defered) it is then read off the stack by popf (a cache hit). Since all I WANT to do is pushf disable intr fiddle popf (chache hit) I am annoyed by the fact that I have all those extra bus cycles going on. I can live with it for development but it still annoys me. > > -Matt > > 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_.---._/ 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 Dec 8 15:47:29 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 15:47:26 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id DCC0C37B401; Fri, 8 Dec 2000 15:47:25 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8NukF02878; Fri, 8 Dec 2000 15:56:46 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012082356.eB8NukF02878@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: Matt Dillon , John Baldwin , current@FreeBSD.ORG Subject: Re: __asm help.. In-reply-to: Your message of "Fri, 08 Dec 2000 15:43:09 PST." <3A31720D.9A6CFF63@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 15:56:46 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Since all I WANT to do is > pushf > disable intr > fiddle > popf (chache hit) > > I am annoyed by the fact that I have all those extra bus cycles going on. > I can live with it for development but it still annoys me. You haven't yet explained how you plan to disable interrupts on the other CPUs... -- ... 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 Fri Dec 8 16:34:50 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 16:34:48 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 1039037B400 for ; Fri, 8 Dec 2000 16:34:48 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB90i9F03062; Fri, 8 Dec 2000 16:44:09 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012090044.eB90i9F03062@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tomi.Vainio@Sun.COM Cc: freebsd-current@FreeBSD.ORG, wkb@freebie.demon.nl Subject: Re: ffs_valloc: dup alloc panics with stable/current In-reply-to: Your message of "Sat, 09 Dec 2000 01:33:58 +0200." <14897.28646.3200.459030@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 16:44:09 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This is not so bad but 5-30 minutes after this command system will > > > always panic. > > > cd /uu ; dump 0buf 126 - /w | restore xbf 126 - > > > > > > mode = 0100644, inum = 720391, fs = /uu > > > panic: ffs_valloc: dup alloc > > > > This looks like memory or PCI data corruption. You don't say how you're > > generating this load, or what the motherboard is, but I suspect that you > > may have hardware issues here. > > > /w fs contains cvsupped FreeBSD source, objs and ports alltogether 1G > of data. Load test is this simple "cd /uu ; dump 0buf 126 - /w | > restore xbf 126 -" between two partitions. Ok, so there's no major traffic anywhere else. That's irritating. > First motherboard we tried was Intel PPro 200Mhz (FX440 based I > think/Natoma?). Second one is newer 633MHz Celeron system but I don't > know manufacturer. But the same symptoms? Have you tried replacing the controller (or even just the onboard RAM)? I don't currently have one of these old controllers that I can use in a PC; the only one I do have is working fine under heavy load in an Alpha. > > One question - I assume you're not seeing any read error diagnostics from > > the Mylex driver (other than the disk errors?) > > > Sometimes we have got more those scsi errors before fs panic. But no other errors? In particular, nothing that looks like a "real" I/O error? The problem that you're seeing looks like filesystem metadata corruption. If it's not memory/system related, it has to be in the datapath from the disks through the driver. I'm not aware of any bugs in the driver that could cause this. 8( -- ... 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 Fri Dec 8 17:14:39 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 17:14:37 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by hub.freebsd.org (Postfix) with ESMTP id 803A037B400; Fri, 8 Dec 2000 17:14:37 -0800 (PST) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA06263; Fri, 8 Dec 2000 17:14:35 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id DAA24617; Sat, 9 Dec 2000 03:14:32 +0200 (EET) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id DAA00975; Sat, 9 Dec 2000 03:14:31 +0200 (EET) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14897.34679.98975.812334@ultrahot.Finland.Sun.COM> Date: Sat, 9 Dec 2000 03:14:31 +0200 To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: ffs_valloc: dup alloc panics with stable/current In-Reply-To: <200012090044.eB90i9F03062@mass.osd.bsdi.com> References: <14897.28646.3200.459030@ultrahot.Finland.Sun.COM> <200012090044.eB90i9F03062@mass.osd.bsdi.com> X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: Tomi.Vainio@finland.sun.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > First motherboard we tried was Intel PPro 200Mhz (FX440 based I > > think/Natoma?). Second one is newer 633MHz Celeron system but I don't > > know manufacturer. > > But the same symptoms? Have you tried replacing the controller (or even > just the onboard RAM)? > All but raid controller was replaced (RAM, video, net). We also have another raid controller and we are going to test it also. Also tried with and without soft updates and async io. > > But no other errors? In particular, nothing that looks like a "real" I/O > error? > This we have to double check because normally we don't stare at the console when we test this system. > The problem that you're seeing looks like filesystem metadata corruption. > If it's not memory/system related, it has to be in the datapath from the > disks through the driver. I'm not aware of any bugs in the driver that > could cause this. 8( > I think old PPro system even supported ECC memory. We are getting out ideas. Maybe small 3 disk raid5 with little newer disks than we use now. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 17:37: 5 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 17:37:03 2000 Return-Path: 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 481FA37B400; Fri, 8 Dec 2000 17:37:02 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB91b2w25635; Fri, 8 Dec 2000 17:37:02 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Dec 2000 17:37:02 -0800 (PST) From: Matt Dillon Message-Id: <200012090137.eB91b2w25635@earth.backplane.com> To: Mike Smith Cc: Julian Elischer , John Baldwin , current@FreeBSD.ORG Subject: Re: __asm help.. References: <200012082356.eB8NukF02878@mass.osd.bsdi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> :> Since all I WANT to do is :> pushf :> disable intr :> fiddle :> popf (chache hit) :> :> I am annoyed by the fact that I have all those extra bus cycles going on. :> I can live with it for development but it still annoys me. : :You haven't yet explained how you plan to disable interrupts on the other :CPUs... : :-- :... every activity meets with opposition, everyone who acts has his Julian, I would recommend using the cmpxchgl instruction to implement atomic operations. Look at /usr/src/sys/i386/i386/mplock.s for an example. You will be in much better shape if you can avoid cli/sti (as Mike points out, it doesn't work across cpu's). mplock.s already has basic MP-compatible lock recursion and should provide a ready example on how you need to do the locking. There is a serious issue you need to consider when implementing an SMP-capable lock, and that is cpu-cpu synchronization. In order to synchronize an operation across multiple cpu's on IA32 you have to use the 'lock;' instruction prefix. Typically, the cmpxchgl must be locked. However, you only need to lock it when there is possible contention.. when you are aquiring the lock. You do not need to lock it when you are releasing the lock. If your assembly gets too complex, just make the assembly a subroutine call. Believe me, subroutine overhead is *nothing* compared to bus locking overhead. For that matter, the cli/sti alone will have more overhead then a subroutine call. Just write it in assembly and forget about trying to use the C __asm() directive. You'll be happier. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 17:39:20 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 17:39:18 2000 Return-Path: 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 956F537B400; Fri, 8 Dec 2000 17:39:18 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB91clw25657; Fri, 8 Dec 2000 17:38:47 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Dec 2000 17:38:47 -0800 (PST) From: Matt Dillon Message-Id: <200012090138.eB91clw25657@earth.backplane.com> To: Julian Elischer Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: __asm help.. References: <200012082129.eB8LTMM22955@earth.backplane.com> <3A31720D.9A6CFF63@elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :foo = save_intr(); disable_intr(); .. restore_intr() :has 4 extra memory accesses. UGh. I put my foot in it. Let me qualify my remark... memory accesses that cause an L1 cache miss are a problem. Memory accesses to locations written to by other cpu's are a problem. Memory accesses that are L1 cached are NOT a problem. Memory accesses to the first few words of the stack are almost guarenteed to be in the L1 cache. Just don't worry about it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 18:17:56 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 18:17:54 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 6E44637B400; Fri, 8 Dec 2000 18:17:54 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id BC8B0F9; Fri, 8 Dec 2000 18:17:53 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id SAA14409; Fri, 8 Dec 2000 18:17:53 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A319650.90FE8EAE@cup.hp.com> Date: Fri, 08 Dec 2000 18:17:52 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > The attached patches (p4 and p5) try to solve this bootstrapping > problem with groff(1). I have lightly tested this on my -stable > box, and would appreciate a feedback on them. Do not remove the USRDIRS and INCDIRS and replace it with mtree (ie make hierarchy). There's no need to duplicate the complete hierarchy inthe object tree. Also, mtree fiddles with ownership and mods, which is not appropriate when building. Which additional directories do you need? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 18:22:13 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 18:22:11 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 7FD8D37B400; Fri, 8 Dec 2000 18:22:11 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 9D79CE91; Fri, 8 Dec 2000 18:22:10 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id SAA14522; Fri, 8 Dec 2000 18:22:10 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A319751.D2C9E5AB@cup.hp.com> Date: Fri, 08 Dec 2000 18:22:09 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > The attached patches (p4 and p5) try to solve this bootstrapping > problem with groff(1). Sorry, I missed this statement before. What exactly are the bootstrapping problems you're seeing? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 18:36:30 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 18:36:28 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 03CE937B400; Fri, 8 Dec 2000 18:36:28 -0800 (PST) Received: from mail2.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id LAA20791; Sat, 9 Dec 2000 11:36:26 +0900 (JST) Received: from localhost.FromTo.Cc (shell [202.247.191.98]) by mail2.rim.or.jp (8.9.3/3.7W) id LAA29663; Sat, 9 Dec 2000 11:36:25 +0900 (JST) Date: Sat, 09 Dec 2000 11:36:26 +0900 Message-ID: <861yviz5g5.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: current@FreeBSD.org Cc: hosokawa@FreeBSD.org Subject: Re: Progress report: Multilingual sysinstall for -current In-Reply-To: In your message of "Wed, 6 Dec 2000 18:18:50 -0600" <20001206181850.A47732@peorth.iteration.net> References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206181850.A47732@peorth.iteration.net> User-Agent: Wanderlust/1.1.0 (Overjoyed) 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: hosokawa@itc.keio.ac.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 6 Dec 2000 18:18:50 -0600, Michael C . Wu wrote: > > Do you have Alpha boot floppies? Does kons25/big5con/korean compile > on Alpha? Would this fit on our ever growing mfsroot.flp and kern.flp? I don't have alpha machine and my knowledge about Alpha architecture is very limited. But kons25 currently can't be compiled on Alpha machine, and is disabled if ARCH==alpha (perhaps release/localization/kon2 should be release/localization/i386/kon2). > I recall seeing the release engineers struggling with fitting the kernel. I have committed to move *.ko modules to mfsroot.flp (and I think it's easily extended to the third floppy or CD-ROM) last month. This is not enabled on Alpha currently, but I think it can be also used on alpha architecture. I've not put it to alpha floppy only because I dont have alpha testbed. If you copy release/i386/drivers.conf to release/alpha and edit it to fit the alpha architecture, drivers will be moved to mfsroot.flp easily. > It would be hard to make OpenBOOT and SRM do what we do in kons25. > (Doable, but someone has to do it.) I also know that Alpha > SRM+vidcontrol+sc0 can only have one video mode, 80x25. Can > Mr. Yokota clarify this for me? Does vidcontrol on Alpha support loadable font option? Russian support uses only this function and does not use graphics console. Other European languages can be supported in this way. hosokawa -- Tatsumi Hosokawa http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 18:36:49 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 18:36:46 2000 Return-Path: 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 E41AB37B400; Fri, 8 Dec 2000 18:36:45 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB92Y5P77769; Fri, 8 Dec 2000 18:34:05 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Dec 2000 18:34:05 -0800 (PST) From: Matt Dillon Message-Id: <200012090234.eB92Y5P77769@earth.backplane.com> To: Marcel Moolenaar Cc: Ruslan Ermilov , marcel@FreeBSD.ORG, Bruce Evans , current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Ruslan Ermilov wrote: :> :> The attached patches (p4 and p5) try to solve this bootstrapping :> problem with groff(1). : :Sorry, I missed this statement before. What exactly are the :bootstrapping problems you're seeing? : :-- :Marcel Moolenaar : mail: marcel@cup.hp.com / marcel@FreeBSD.org : tel: (408) 447-4222 I just ran into this problem trying to build the world: -Matt /usr/src/gnu/usr.bin/groff# make ===> libgroff ===> libdriver ===> libbib ===> addftinfo ===> afmtodit ===> doc ===> eqn c++ -O -pipe -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/include -I/usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn -I. -fno-for-scope -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:22: eqn_tab.h: No such file or directory /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:57: `OVER' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:58: `SMALLOVER' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:59: `SQRT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:60: `SUB' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:61: `SUP' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:62: `LPILE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:63: `RPILE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:64: `CPILE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:65: `PILE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:66: `LEFT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:67: `RIGHT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:68: `TO' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:69: `FROM' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:70: `SIZE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:71: `FONT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:72: `ROMAN' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:73: `BOLD' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:74: `ITALIC' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:75: `FAT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:76: `BAR' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:77: `UNDER' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:78: `ACCENT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:79: `UACCENT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:80: `ABOVE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:81: `FWD' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:82: `BACK' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:83: `DOWN' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:84: `UP' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:85: `MATRIX' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:86: `COL' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:87: `LCOL' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:88: `RCOL' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:89: `CCOL' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:90: `MARK' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:91: `LINEUP' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:92: `SPACE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:93: `GFONT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:94: `GSIZE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:95: `DEFINE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:96: `SDEFINE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:97: `NDEFINE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:98: `TDEFINE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:99: `UNDEF' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:100: `IFDEF' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:101: `INCLUDE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:102: `INCLUDE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:103: `DELIM' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:104: `CHARTYPE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:105: `TYPE' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:106: `VCENTER' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:107: `SET' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:108: `PRIME' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:109: `GRFONT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:110: `GBFONT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:111: `SPLIT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:112: `NOSPLIT' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:113: `SPECIAL' was not declared in this scope /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc: In function `int get_token(int = 0)': /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:768: `QUOTED_TEXT' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:768: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:768: for each function it appears in.) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:867: `TEXT' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc: In function `int yylex()': /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1080: `UNDEF' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1083: `SDEFINE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1086: `DEFINE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1089: `TDEFINE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1095: `NDEFINE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1101: `GSIZE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1104: `GFONT' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1107: `GRFONT' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1110: `GBFONT' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1113: `SPACE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1116: `INCLUDE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1119: `IFDEF' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1122: `DELIM' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1125: `CHARTYPE' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1128: `SET' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1134: `yylval' undeclared (first use this function) /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:1081: warning: unreachable code at beginning of switch statement *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff/eqn. *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 18:43:16 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 18:43:13 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 0B3A037B400 for ; Fri, 8 Dec 2000 18:43:13 -0800 (PST) Received: from cerberus.uchicago.edu (broad-173-147.rh.uchicago.edu [128.135.173.147]) by midway.uchicago.edu (8.10.1/8.10.1) with ESMTP id eB92hBK15312 for ; Fri, 8 Dec 2000 20:43:11 -0600 (CST) Message-Id: <4.3.2.7.2.20001208140130.00c5e1a0@nsit-popmail.uchicago.edu> X-Sender: dbsypher@nsit-popmail.uchicago.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 08 Dec 2000 20:42:55 -0600 To: current@freebsd.org From: David Syphers Subject: problems configuring cardbus card Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a FreeBSD 5-CURRENT snapshot from Dec. 5, and trying to configure an AmbiCom Cardbus ethernet card (a DEC Tulip base). I've included cardbus, pccbb, miibus, and dc in my kernel, and enabled use of DHCP. Since I haven't tracked -current since 4.x split off from it, I had a great deal of FM to R before I realized things like there's a file called /boot/device.hints that's very important. Putting hint.dc.0.at="isa" hint.dc.0.port="0x300" hint.dc.0.irq="10" into /boot/device.hints made the "watchdog timeout" errors I had been getting on boot go away, but the card still didn't work. Do I need to specify drq or maddr, and how would I determine if 0x300 is the right port? This may be due to the fact that it looks like my graphics card and my ethernet card are both assigned IRQ 11 (see clip from dmesg below). But I really have no idea how to use device.hints or even how to set up an ethernet card under FreeBSD (I know, I should have picked something other than cardbus on -current for my first experience), so any help would be appreciated. Thanks! [part of dmesg output] pci0: at 2.0 irq 11 ... pccbb0: at device 10.0 on pci0 pccbb0: PCI Memory allocated: 18020000 pci_cfgintr_unique: hard-routed to irq 11 pci_cfgintr: 0:10 INTA routed to irq 11 cardbus0: on pccbb0 pccbb0: WARNING: cannot attach pccard bus. pccbb1: at device 10.1 on pci0 pccbb1: PCI Memory allocated: 18021000 pci_cfgintr_unique: hard-routed to irq 11 pci_cfgintr: 0:10 INTB routed to irq 11 cardbus1: on pccbb1 pccbb1: WARNING: cannot attach pccard bus. ... pccbb0: card inserted: event=0x00000009, state=30000b20 pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb0: bad Vcc request. ctrl=0x0, status=0x30000b20 pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] pccbb0: bad Vcc request. ctrl=0x33, status=0x30000b20 pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] TUPLE: LINKTARGET [3]: 43 49 53 Product version: 5.0 Product name: AmbiCom, Inc. | AMB8100 | Fast Ethernet CardBus PC Card | 1.00 | Manufacturer ID: 13958100 Functions: Network Adaptor, Multi-Functioned Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 cardbus0: Opening BAR: type=IO, bar=10, len=0080 TUPLE: CONFIG_CB [7]: 03 01 00 00 00 00 ff TUPLE: CFTABLE_ENTRY_CB [5]: 41 80 fb 00 ff dc1: port 0x3000-0x307f mem 0x18040000-0x1807ffff,0x18022000-0x180223ff irq 11 at device 0.0 on cardbus0 dc1: Ethernet address: 00:80:00:80:00:80 miibus0: on dc1 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pccbb1: removal of nonexistant card! Note: "dc1" used to be "dc0" before I put the lines in device.hints, but then I got "watchdog timeout" errors. -David Syphers Charon@freethought.org http://www.seektruth.org/ Cannibalism is a small price to pay for popularity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 19: 4:23 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 19:04:20 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 9FE7237B402; Fri, 8 Dec 2000 19:04:20 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 43DDC165; Fri, 8 Dec 2000 19:04:19 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id TAA15420; Fri, 8 Dec 2000 19:04:18 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A31A12E.1EE1ADBD@cup.hp.com> Date: Fri, 08 Dec 2000 19:04:14 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matt Dillon Cc: Ruslan Ermilov , marcel@FreeBSD.ORG, Bruce Evans , current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <200012090234.eB92Y5P77769@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > /usr/src/gnu/usr.bin/groff# make > > ===> libgroff > ===> libdriver > ===> libbib > ===> addftinfo > ===> afmtodit > ===> doc > ===> eqn > c++ -O -pipe -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/include -I/usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn -I. -fno-for-scope -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc > /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:22: eqn_tab.h: No such file or directory > /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:57: `OVER' was not declared in this scope Hmmm... I don't see this. This is more a build problem than a bootstrapping problem. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 19:44:44 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 19:44:42 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (dyna225-091.nada.kth.se [130.237.225.91]) by hub.freebsd.org (Postfix) with ESMTP id 1149137B400; Fri, 8 Dec 2000 19:44:41 -0800 (PST) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id EAA38446; Sat, 9 Dec 2000 04:44:43 +0100 (CET) (envelope-from assar) Sender: assar@assaris.sics.se From: assar@FreeBSD.ORG To: Matt Dillon Cc: Marcel Moolenaar , Ruslan Ermilov , marcel@FreeBSD.ORG, Bruce Evans , current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <200012090234.eB92Y5P77769@earth.backplane.com> Date: 09 Dec 2000 04:44:43 +0100 In-Reply-To: Matt Dillon's message of "Fri, 8 Dec 2000 18:34:05 -0800 (PST)" Message-ID: <5lbsumdzro.fsf@assaris.sics.se> Lines: 8 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > c++ -O -pipe -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/include -I/usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn -I. -fno-for-scope -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc > /usr/src/gnu/usr.bin/groff/eqn/../../../../contrib/groff/eqn/lex.cc:22: eqn_tab.h: No such file or directory I got rid of that with 'rm *' in /usr/obj/usr/src/gnu/usr.bin/groff/eqn. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 20:22:45 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 20:22:44 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2A98937B400 for ; Fri, 8 Dec 2000 20:22:43 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eB94MRs54206; Fri, 8 Dec 2000 21:22:27 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA17719; Fri, 8 Dec 2000 21:22:26 -0700 (MST) Message-Id: <200012090422.VAA17719@harmony.village.org> To: Goblin Subject: Re: growfs(8) for FreeBSD Cc: "Rogier R. Mulhuijzen" , freebsd-current@FreeBSD.ORG, growfs@tomsoft.com In-reply-to: Your message of "Fri, 08 Dec 2000 15:40:36 CST." <20001208154036.A645@msp-65-25-230-128.yahoo.com> References: <20001208154036.A645@msp-65-25-230-128.yahoo.com> <20001208113836.B32113@cichlids.cichlids.com> <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net> Date: Fri, 08 Dec 2000 21:22:26 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001208154036.A645@msp-65-25-230-128.yahoo.com> Goblin writes: : I can certainly see where "cat /dev/<1GBdevice> > /dev/<10GBdevice>" : situations would make a growfs useful w/out vinum... : : And, removing a failing disk from the end of a a vinum concat volume : would make shrinkfs really nice. I recently did that to "upgrade" my laptop hard disk. Execpt I had to also do dump/restore for the FreeBSD partitions. growfs would have been sweet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 20:36:42 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 20:36:41 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 0F28537B400 for ; Fri, 8 Dec 2000 20:36:41 -0800 (PST) Received: from symmetric.net (216-80-54-139.d.enteract.com [216.80.54.139]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id WAA00413; Fri, 8 Dec 2000 22:36:18 -0600 (CST) (envelope-from presence@symmetric.net) Message-ID: <3A31B6CC.60EBFDC@symmetric.net> Date: Fri, 08 Dec 2000 22:36:28 -0600 From: "Ken \\" Escape Meta Alt Control Shift\ " Kanno" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Goblin , "Rogier R. Mulhuijzen" , freebsd-current@FreeBSD.ORG Subject: mfs size limits? References: <20001208154036.A645@msp-65-25-230-128.yahoo.com> <20001208113836.B32113@cichlids.cichlids.com> <4.3.2.7.0.20001208204155.00cbee40@mail.drwilco.net> <200012090422.VAA17719@harmony.village.org> 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 reason I cannot create a ramdisk larger than 507627 1kB blocks? I create them using the syntax of mount_mfs -s [any numer] -T minimum /dev/null /ramdisk It never errors, but never creates anything larger than the 507627 blocks. My computer has 768MB of RAM. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 22: 8: 7 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 22:08:04 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 996AF37B400; Fri, 8 Dec 2000 22:08:00 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id eB967Yr06047; Sat, 9 Dec 2000 08:07:34 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200012090607.eB967Yr06047@zibbi.icomtek.csir.co.za> Subject: Re: Hangs during 'make world -j4' on recent current In-Reply-To: <20001208124330.Z27667@wantadilla.lemis.com> from Greg Lehey at "Dec 8, 2000 12:43:30 pm" To: grog@lemis.com (Greg Lehey) Date: Sat, 9 Dec 2000 08:07:34 +0200 (SAT) Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users), FreeBSD-smp@FreeBSD.ORG (FreeBSD SMP list) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: jhay@zibbi.icomtek.csir.co.za Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For over a week now, I have been unable to complete a 'make world' on > my -CURRENT box if I specify -j4. The system hangs and is completely > unresponsive. This is a dual Celeron and an Abit BP6 motherboard. As > far as I can tell, nobody knows what's causing this, nor even how to > attack the problem. I'd like to solicit feedback about the extent of > the problem, the possible causes, and how to debug it. I have been building releases with WORLD_FLAGS=-j4 successfully on my SMP box with a Dec 1 kernel for the past week. Yesterday I upgraded the kernel and with the new kernel did a make world -j4 which completed with no problems. And afterwards a make release with WORLD_FLAGS=-j4 also finished with no problems. So -current isn't totally broken. It might be timing related. My machine is an old dual 266MHz PII. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 22:19:59 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 22:19:58 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id A9BFB37B400 for ; Fri, 8 Dec 2000 22:19:50 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 144dPQ-0000Cj-00; Fri, 08 Dec 2000 23:23:00 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A31CFC4.281CBCE2@softweyr.com> Date: Fri, 08 Dec 2000 23:23:00 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Masto Cc: Charlie Root , Doug Ambrisko , Warner Losh , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > > On Wed, Dec 06, 2000 at 07:23:40PM -0800, Charlie Root wrote: > > There is definately a trend to lower prices. I just found this. A > > new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia > > cards for $699. The access point sounds interesting. I personally > > would like to use it as a repeater and network bridge. > > I am told that the Apple "AirPort Base Station", which is $399, works > well and can be configured with the Java-based thing in the ports > collection. I am further told that the Lucent/ORiNOCO RG-1000 base > station is virtually identical, although more expensive and somehow > inferior, although I don't understand the exact inferiorities. They're the same thing in different cases, it's hard to see how one can be superior in any way other than price. > I am thinking of getting one of these things, despite my strong desire > to avoid owning such a stupid looking piece of hardware. Wait for the LinkSys; the dual antennas and price differential will be worth the wait. If the plethora of 802.11b equipment at BSDCon 2k is any indication, interoperability should be pretty good. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 22:21: 0 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 22:20:57 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id EEC6F37B400 for ; Fri, 8 Dec 2000 22:20:56 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eB96Kts54536; Fri, 8 Dec 2000 23:20:55 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA18838; Fri, 8 Dec 2000 23:20:55 -0700 (MST) Message-Id: <200012090620.XAA18838@harmony.village.org> To: Wes Peters Subject: Re: Lucent Orinoco Gold PCCard? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Dec 2000 23:23:00 MST." <3A31CFC4.281CBCE2@softweyr.com> References: <3A31CFC4.281CBCE2@softweyr.com> <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> Date: Fri, 08 Dec 2000 23:20:55 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A31CFC4.281CBCE2@softweyr.com> Wes Peters writes: : worth the wait. If the plethora of 802.11b equipment at BSDCon 2k is : any indication, interoperability should be pretty good. YAMAMOTO shigeru-san's collection of wireless cards was proof of that 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 Fri Dec 8 22:25:13 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 22:25:10 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from lion-around.at.yiff.net (lion-around.at.yiff.net [209.54.21.199]) by hub.freebsd.org (Postfix) with ESMTP id EC48937B400 for ; Fri, 8 Dec 2000 22:25:09 -0800 (PST) Received: (from chris@localhost) by lion-around.at.yiff.net (8.11.0/8.11.0) id eB96OV402146; Sat, 9 Dec 2000 01:24:31 -0500 (EST) (envelope-from chris@netmonger.net) X-Authentication-Warning: lion-around.at.yiff.net: chris set sender to chris@netmonger.net using -f Date: Sat, 9 Dec 2000 01:24:30 -0500 From: Christopher Masto To: Wes Peters Cc: Charlie Root , Doug Ambrisko , Warner Losh , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? Message-ID: <20001209012429.A673@netmonger.net> References: <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> <3A31CFC4.281CBCE2@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A31CFC4.281CBCE2@softweyr.com>; from wes@softweyr.com on Fri, Dec 08, 2000 at 11:23:00PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 11:23:00PM -0700, Wes Peters wrote: > > I am told that the Apple "AirPort Base Station", which is $399, works > > well and can be configured with the Java-based thing in the ports > > collection. I am further told that the Lucent/ORiNOCO RG-1000 base > > station is virtually identical, although more expensive and somehow > > inferior, although I don't understand the exact inferiorities. > > They're the same thing in different cases, it's hard to see how one can > be superior in any way other than price. "The most stupid thing was that you couldn't set its network name to anything other than its serial number because on bootup, it copies its serial number over the first five bytes of the network name. It also can't be fully configured without the Windows software -- which is a bit misleading for me to say because even with the Windows software, you can only set it up to use the modem or provide NAT routing via Ethernet, and not set it up to do bridging." > > I am thinking of getting one of these things, despite my strong desire > > to avoid owning such a stupid looking piece of hardware. > > Wait for the LinkSys; the dual antennas and price differential will be > worth the wait. If the plethora of 802.11b equipment at BSDCon 2k is > any indication, interoperability should be pretty good. But will I be able to configure the LinkSys? That's my primary concern. I only have FreeBSD, so if it requires any proprietary software at all, I can't use it. Besides that, I'll only be using this 10 feet away from the base. :-) -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Dec 8 23:12: 6 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 23:12:02 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C1AF637B400; Fri, 8 Dec 2000 23:12:00 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 043EC6AB68; Sat, 9 Dec 2000 17:41:54 +1030 (CST) Date: Sat, 9 Dec 2000 17:41:53 +1030 From: Greg Lehey To: John Hay Cc: FreeBSD current users , FreeBSD SMP list Subject: Re: Hangs during 'make world -j4' on recent current Message-ID: <20001209174153.V53111@wantadilla.lemis.com> References: <20001208124330.Z27667@wantadilla.lemis.com> <200012090607.eB967Yr06047@zibbi.icomtek.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: <200012090607.eB967Yr06047@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Sat, Dec 09, 2000 at 08:07:34AM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 9 December 2000 at 8:07:34 +0200, John Hay wrote: >> For over a week now, I have been unable to complete a 'make world' on >> my -CURRENT box if I specify -j4. The system hangs and is completely >> unresponsive. This is a dual Celeron and an Abit BP6 motherboard. As >> far as I can tell, nobody knows what's causing this, nor even how to >> attack the problem. I'd like to solicit feedback about the extent of >> the problem, the possible causes, and how to debug it. > > I have been building releases with WORLD_FLAGS=-j4 successfully on my > SMP box with a Dec 1 kernel for the past week. Yesterday I upgraded the > kernel and with the new kernel did a make world -j4 which completed with > no problems. And afterwards a make release with WORLD_FLAGS=-j4 also > finished with no problems. So -current isn't totally broken. It might > be timing related. My machine is an old dual 266MHz PII. How many processors does your machine have? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 8 23:44:21 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 23:44:18 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id D640237B400; Fri, 8 Dec 2000 23:44:14 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id eB97hwW08236; Sat, 9 Dec 2000 09:43:58 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200012090743.eB97hwW08236@zibbi.icomtek.csir.co.za> Subject: Re: Hangs during 'make world -j4' on recent current In-Reply-To: <20001209174153.V53111@wantadilla.lemis.com> from Greg Lehey at "Dec 9, 2000 05:41:53 pm" To: grog@lemis.com (Greg Lehey) Date: Sat, 9 Dec 2000 09:43:58 +0200 (SAT) Cc: jhay@icomtek.csir.co.za (John Hay), FreeBSD-current@FreeBSD.ORG (FreeBSD current users), FreeBSD-smp@FreeBSD.ORG (FreeBSD SMP list) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: jhay@zibbi.icomtek.csir.co.za Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> For over a week now, I have been unable to complete a 'make world' on > >> my -CURRENT box if I specify -j4. The system hangs and is completely > >> unresponsive. This is a dual Celeron and an Abit BP6 motherboard. As > >> far as I can tell, nobody knows what's causing this, nor even how to > >> attack the problem. I'd like to solicit feedback about the extent of > >> the problem, the possible causes, and how to debug it. > > > > I have been building releases with WORLD_FLAGS=-j4 successfully on my > > SMP box with a Dec 1 kernel for the past week. Yesterday I upgraded the > > kernel and with the new kernel did a make world -j4 which completed with > > no problems. And afterwards a make release with WORLD_FLAGS=-j4 also > > finished with no problems. So -current isn't totally broken. It might > > be timing related. My machine is an old dual 266MHz PII. ^^^^ > > How many processors does your machine have? 2 John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 0:56:18 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 00:56:16 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id A149F37B400; Sat, 9 Dec 2000 00:56:15 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 4BD5A5740D; Sat, 9 Dec 2000 02:56:18 -0600 (CST) Date: Sat, 9 Dec 2000 02:56:18 -0600 From: "Michael C . Wu" To: Tatsumi Hosokawa Cc: current@FreeBSD.org Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <20001209025618.A11802@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206181850.A47732@peorth.iteration.net> <861yviz5g5.wl@ringo.FromTo.Cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <861yviz5g5.wl@ringo.FromTo.Cc>; from hosokawa@FreeBSD.org on Sat, Dec 09, 2000 at 11:36:26AM +0900 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 11:36:26AM +0900, Tatsumi Hosokawa scribbled: | At Wed, 6 Dec 2000 18:18:50 -0600, | Michael C . Wu wrote: | > | > Do you have Alpha boot floppies? Does kons25/big5con/korean compile | > on Alpha? Would this fit on our ever growing mfsroot.flp and kern.flp? | | I don't have alpha machine and my knowledge about Alpha architecture | is very limited. But kons25 currently can't be compiled on Alpha | machine, and is disabled if ARCH==alpha (perhaps | release/localization/kon2 should be release/localization/i386/kon2). | | > I recall seeing the release engineers struggling with fitting the kernel. | | I have committed to move *.ko modules to mfsroot.flp (and I think it's | easily extended to the third floppy or CD-ROM) last month. This is | not enabled on Alpha currently, but I think it can be also used on | alpha architecture. I've not put it to alpha floppy only because I | dont have alpha testbed. | | If you copy release/i386/drivers.conf to release/alpha and edit it to | fit the alpha architecture, drivers will be moved to mfsroot.flp | easily. | | > It would be hard to make OpenBOOT and SRM do what we do in kons25. | > (Doable, but someone has to do it.) I also know that Alpha | > SRM+vidcontrol+sc0 can only have one video mode, 80x25. Can | > Mr. Yokota clarify this for me? | | Does vidcontrol on Alpha support loadable font option? Russian | support uses only this function and does not use graphics console. | Other European languages can be supported in this way. Yes, vidcontrol on Alpha supports loadable fonts. But foxfair told me that he and vanilla looked into kons/big5con for Alpha. Their conclusion was that it is pretty impossible, but not too impossible. :) DECUnix/Tru64 has support for CJK and many other languages in SRM. However, FreeBSD's vidcontrol cannot do what SRM does, for some reason. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 5:46:54 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 05:46:52 2000 Return-Path: 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 F1B5137B400; Sat, 9 Dec 2000 05:46:39 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eB9Dhlq78430; Sat, 9 Dec 2000 15:43:48 +0200 (EET) (envelope-from ru) Date: Sat, 9 Dec 2000 15:43:47 +0200 From: Ruslan Ermilov To: Marcel Moolenaar Cc: marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) Message-ID: <20001209154347.A78374@sunbay.com> Mail-Followup-To: Marcel Moolenaar , marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A319751.D2C9E5AB@cup.hp.com>; from marcel@cup.hp.com on Fri, Dec 08, 2000 at 06:22:09PM -0800 Sender: ru@whale.sunbay.crimea.ua Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 06:22:09PM -0800, Marcel Moolenaar wrote: > Ruslan Ermilov wrote: > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > problem with groff(1). > > Sorry, I missed this statement before. What exactly are the > bootstrapping problems you're seeing? > New groff(1) provides new versions of macro packages and device files. When building, we should use THEM rather than installed (obsolete) ones. -- 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 Sat Dec 9 5:51:49 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 05:51:46 2000 Return-Path: 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 8C6E037B400; Sat, 9 Dec 2000 05:51:41 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eB9Dn1m78887; Sat, 9 Dec 2000 15:49:01 +0200 (EET) (envelope-from ru) Date: Sat, 9 Dec 2000 15:49:01 +0200 From: Ruslan Ermilov To: Marcel Moolenaar Cc: marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) Message-ID: <20001209154901.B78374@sunbay.com> Mail-Followup-To: Marcel Moolenaar , marcel@FreeBSD.org, Bruce Evans , current@FreeBSD.org References: <20001208181908.A12716@sunbay.com> <3A319650.90FE8EAE@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5i In-Reply-To: <3A319650.90FE8EAE@cup.hp.com>; from marcel@cup.hp.com on Fri, Dec 08, 2000 at 06:17:52PM -0800 Sender: ru@whale.sunbay.crimea.ua Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 06:17:52PM -0800, Marcel Moolenaar wrote: > Ruslan Ermilov wrote: > >=20 > > The attached patches (p4 and p5) try to solve this bootstrapping > > problem with groff(1). I have lightly tested this on my -stable > > box, and would appreciate a feedback on them. >=20 > Do not remove the USRDIRS and INCDIRS and replace it with mtree (ie make > hierarchy). There's no need to duplicate the complete hierarchy in=03the > object tree. Also, mtree fiddles with ownership and mods, which is not > appropriate when building. >=20 The -U flag to mtree(8) could be eliminated for this case... > Which additional directories do you need? >=20 Everyting below /usr/share/tmac and /usr/share/groff_font: /usr/share/tmac /usr/share/tmac/locale /usr/share/tmac/mdoc /usr/share/tmac/mdoc/locale /usr/share/tmac/mm /usr/share/groff_font /usr/share/groff_font/devX100 /usr/share/groff_font/devX100-12 /usr/share/groff_font/devX75 /usr/share/groff_font/devX75-12 /usr/share/groff_font/devascii /usr/share/groff_font/devcp1047 /usr/share/groff_font/devdvi /usr/share/groff_font/devhtml /usr/share/groff_font/devkoi8-r /usr/share/groff_font/devlatin1 /usr/share/groff_font/devlbp /usr/share/groff_font/devlj4 /usr/share/groff_font/devps /usr/share/groff_font/devutf8 The new groff(1) release is likely to provide new groff_font subdirectories, so we would need to update USRDIRS every time we upgrade groff(1). Does it look reasonable? --=20 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 Sat Dec 9 5:57:45 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 05:57:39 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from CUTE2000.sun-planning.co.jp (unknown [203.181.121.178]) by hub.freebsd.org (Postfix) with ESMTP id E283037B401; Sat, 9 Dec 2000 05:57:32 -0800 (PST) Received: from hp2 (LOCAL101 [192.168.0.101]) by CUTE2000.sun-planning.co.jp (8.9.3/3.7W) with SMTP id RAA17847; Sat, 9 Dec 2000 17:38:30 +0900 From: mailtest Message-ID: <000901c061ba$a5d3b3e0$6500a8c0@sunplanning.co.jp> To: Subject: =?iso-2022-jp?B?GyRCJVElQSVzJTNFOSROPVA2TDRJTX0kTkhrTCkkRyQ5GyhC?= Date: Sat, 9 Dec 2000 17:23:40 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C06205.911365E0" 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_0005_01C06205.911365E0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit $B%Q%A%s%3E9$N=P6L4IM}$NHkL)$G$9(B $B%Q%A%s%3E9$G$N!VBgEv$?$j!W$O%7%^$NItJ,ItJ,$K=8CDH/@8$7$^$9!#!JK\Ev$G$9!#!K(B $B$"$J$?$O$=$N;v

=1B$B%Q%A%s%3E9$N=3DP6L4IM}$NHkL)$G$9=1B(B
=1B$B%Q%A%s%3E9$G$= N!VBgEv$?$j!W$O%7%^$NItJ,ItJ,$K=3D8CDH/@8$7$^$9!#!JK\Ev$G$9!#!K=1B(B
=1B= $B$"$J$?$O$=3D$N;v=1B$B$J$
 
=1B$B%Q%A%s%3$r$5$l$kJ}$O@'Hs!"$3$N%[!<%`%Z!<%8$r$4Mw$/$@$5$$!#=1B= (B
=1B$B!VBgEv$?$j$N;EAH$_!W$d!"%Q%A%s%3E9$N!V=3DP6L4IM}$N;EAH$_!W$NHk= L)$rH=3D$j$d$9$/@b=1B(B
=1B$BL@$7$F$*$j!"I,$:Lr$KN)$A$^$9!#=1B(B
 
=1B$B!!"*"*!!!!=1B(Bhttp://www.m-net.ne.jp/~p= kr/index.html=1B$B!!=1B(B
 

=1B$B#P#K%j%5!<%A!!=1B(B
------=_NextPart_000_0005_01C06205.911365E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 10: 7: 4 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 10:07:02 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 0A7D537B400 for ; Sat, 9 Dec 2000 10:07:02 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 144oRh-00007g-00; Sat, 09 Dec 2000 11:10:05 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A32757D.20B44C64@softweyr.com> Date: Sat, 09 Dec 2000 11:10:05 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Masto Cc: Charlie Root , Doug Ambrisko , Warner Losh , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? References: <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> <3A31CFC4.281CBCE2@softweyr.com> <20001209012429.A673@netmonger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > > On Fri, Dec 08, 2000 at 11:23:00PM -0700, Wes Peters wrote: > > > I am told that the Apple "AirPort Base Station", which is $399, works > > > well and can be configured with the Java-based thing in the ports > > > collection. I am further told that the Lucent/ORiNOCO RG-1000 base > > > station is virtually identical, although more expensive and somehow > > > inferior, although I don't understand the exact inferiorities. > > > > They're the same thing in different cases, it's hard to see how one can > > be superior in any way other than price. > > "The most stupid thing was that you couldn't set its network name to > anything other than its serial number because on bootup, it copies its > serial number over the first five bytes of the network name. It also > can't be fully configured without the Windows software -- which is a > bit misleading for me to say because even with the Windows software, > you can only set it up to use the modem or provide NAT routing via > Ethernet, and not set it up to do bridging." The "Windows software" is actually a Java applet that I saw running on FreeBSD at BSDCon. Don't believe everything you read, try to verify it first. > > > I am thinking of getting one of these things, despite my strong desire > > > to avoid owning such a stupid looking piece of hardware. > > > > Wait for the LinkSys; the dual antennas and price differential will be > > worth the wait. If the plethora of 802.11b equipment at BSDCon 2k is > > any indication, interoperability should be pretty good. > > But will I be able to configure the LinkSys? That's my primary > concern. I only have FreeBSD, so if it requires any proprietary > software at all, I can't use it. Besides that, I'll only be using > this 10 feet away from the base. :-) If you're only 10 feet from the base, save several hundred dollars and buy a 4 meter patch cable. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 10:32: 3 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 10:32:00 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from habanero.netmonger.net (ool-18bd4893.dyn.optonline.net [24.189.72.147]) by hub.freebsd.org (Postfix) with ESMTP id 482AA37B400 for ; Sat, 9 Dec 2000 10:32:00 -0800 (PST) Received: (from chris@localhost) by habanero.netmonger.net (8.11.0/8.11.0) id eB9Ieq801913; Sat, 9 Dec 2000 13:40:52 -0500 (EST) (envelope-from chris@netmonger.net) X-Authentication-Warning: habanero.netmonger.net: chris set sender to chris@netmonger.net using -f Date: Sat, 9 Dec 2000 13:40:51 -0500 From: Christopher Masto To: Wes Peters Cc: Charlie Root , Doug Ambrisko , Warner Losh , Sascha Luck , current@FreeBSD.ORG Subject: Re: Lucent Orinoco Gold PCCard? Message-ID: <20001209134051.A391@netmonger.net> References: <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> <3A31CFC4.281CBCE2@softweyr.com> <20001209012429.A673@netmonger.net> <3A32757D.20B44C64@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A32757D.20B44C64@softweyr.com>; from wes@softweyr.com on Sat, Dec 09, 2000 at 11:10:05AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 11:10:05AM -0700, Wes Peters wrote: > > > They're the same thing in different cases, it's hard to see how one can > > > be superior in any way other than price. > > > > "The most stupid thing was that you couldn't set its network name to > > anything other than its serial number because on bootup, it copies its > > serial number over the first five bytes of the network name. It also > > can't be fully configured without the Windows software -- which is a > > bit misleading for me to say because even with the Windows software, > > you can only set it up to use the modem or provide NAT routing via > > Ethernet, and not set it up to do bridging." > > The "Windows software" is actually a Java applet that I saw running on > FreeBSD at BSDCon. Don't believe everything you read, try to verify it > first. I got that quote by asking a friend of mine who owns both products. > If you're only 10 feet from the base, save several hundred dollars and buy > a 4 meter patch cable. Thanks, that hadn't occurred to me. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Dec 9 10:32: 5 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 10:32:02 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id B708837B401 for ; Sat, 9 Dec 2000 10:32:01 -0800 (PST) Received: (qmail 22075 invoked by uid 100); 9 Dec 2000 18:32:01 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14898.31393.228926.763711@guru.mired.org> Date: Sat, 9 Dec 2000 12:32:01 -0600 (CST) To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: <200011241948.OAA64331@khavrinen.lcs.mit.edu> References: <14876.48112.785320.465213@guru.mired.org> <20001123110828.V18037@fw.wintelcom.net> <14877.65275.744127.863828@guru.mired.org> <200011241948.OAA64331@khavrinen.lcs.mit.edu> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman types: > < said: > > Um - compliance with what, exactly? > IEEE Std.1003.1-1990 et seq. Since no one has bothered to close this PR with a note that this noncompliance is unacceptable, I'm assuming that no one considers it so. Further, it's not clear that FreeBSD can't stay in compliance with an appropriate note in the compliance document. There are other places where FreeBSD doesn't comply with the appropriate standard - packages vs. FHS, for instance. I claim that the benefits of no longer providing grossly inaccurate error message outweigh the relatively minor conformance loss in this case. So would someone commit the thing so that others can share those benefits? Thanks, Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 398F337B400 for ; Sat, 9 Dec 2000 10:40:10 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eB9Ie7s58634; Sat, 9 Dec 2000 11:40:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA24454; Sat, 9 Dec 2000 11:40:07 -0700 (MST) Message-Id: <200012091840.LAA24454@harmony.village.org> To: Christopher Masto Subject: Re: Lucent Orinoco Gold PCCard? Cc: Wes Peters , Charlie Root , Doug Ambrisko , Sascha Luck , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 09 Dec 2000 13:40:51 EST." <20001209134051.A391@netmonger.net> References: <20001209134051.A391@netmonger.net> <200012052105.NAA19124@whistle.com> <3A2F02BB.2882A98A@MexComUSA.Net> <20001207175530.A23355@netmonger.net> <3A31CFC4.281CBCE2@softweyr.com> <20001209012429.A673@netmonger.net> <3A32757D.20B44C64@softweyr.com> Date: Sat, 09 Dec 2000 11:40:07 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001209134051.A391@netmonger.net> Christopher Masto writes: : > If you're only 10 feet from the base, save several hundred dollars and buy : > a 4 meter patch cable. : : Thanks, that hadn't occurred to me. It depends on the 10' :-) My laptop roams between 3' and 75' of my closest outlet. Usually 5-10'. Patch cables are cheaper and faster (when was the last time you got 100Mbps over wireless?). Wireless cards are easier to expand the net with and easier to take to a slightly different place :-) Warner -- Seen on the door of an egineer at sun: "We're the dot in vm.core" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 10:48: 1 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 10:48:00 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 134FA37B400 for ; Sat, 9 Dec 2000 10:48:00 -0800 (PST) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id NAA89008; Sat, 9 Dec 2000 13:47:59 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sat, 9 Dec 2000 13:47:59 -0500 (EST) From: "Brandon D. Valentine" To: Mike Meyer Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: <14898.31393.228926.763711@guru.mired.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 Sat, 9 Dec 2000, Mike Meyer wrote: >There are other places where FreeBSD doesn't comply with the >appropriate standard - packages vs. FHS, for instance. I claim that We don't seek to comply with the arbitrarily devised linux filesystem standard. We comply with hier(5), a standard steeped in decades of tradition. -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 10:50:20 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 10:50:18 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 5AED037B400 for ; Sat, 9 Dec 2000 10:50:18 -0800 (PST) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id NAA89035; Sat, 9 Dec 2000 13:50:18 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sat, 9 Dec 2000 13:50:18 -0500 (EST) From: "Brandon D. Valentine" To: Mike Meyer Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation 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 Sat, 9 Dec 2000, Brandon D. Valentine wrote: >On Sat, 9 Dec 2000, Mike Meyer wrote: > >>There are other places where FreeBSD doesn't comply with the >>appropriate standard - packages vs. FHS, for instance. I claim that > >We don't seek to comply with the arbitrarily devised linux filesystem >standard. We comply with hier(5), a standard steeped in decades of >tradition. And before somebody else jumps in, yes I fat-fingered the numpad. That's hier(7), not 5. -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11: 5:36 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:05:33 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 6326737B401 for ; Sat, 9 Dec 2000 11:05:33 -0800 (PST) Received: (qmail 23209 invoked by uid 100); 9 Dec 2000 19:05:32 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14898.33404.356173.963351@guru.mired.org> Date: Sat, 9 Dec 2000 13:05:32 -0600 (CST) To: "Brandon D. Valentine" Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: References: <14898.31393.228926.763711@guru.mired.org> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brandon D. Valentine types: > >There are other places where FreeBSD doesn't comply with the > >appropriate standard - packages vs. FHS, for instance. I claim that > We don't seek to comply with the arbitrarily devised linux filesystem > standard. We comply with hier(5), a standard steeped in decades of > tradition. Corrections first: The only place where FreeBSD fails to follow FHS (in my quick perusal of it) is in putting packages in /usr/local instead of /opt. You can't blame that part of FHS on Linux - I have as yet to see a Linux distro or package do it that way. No, this bit comes from commercial vendors, where it's also steeped in years of tradition. Rant second: FreeBSD *violates* years of traditions with it's treatment of /usr/local. /usr/local is for *local* things, not add-on software packages! Coopting /usr/local for non-local software creates needless complexity and confusion, which of course leads to needless pain. All of which has nothing to do with the question of whether we want to continue giving error messages that are wrong, or commit this patch and provide ones that are actually informative. Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id EAFAF37B400 for ; Sat, 9 Dec 2000 11:21:30 -0800 (PST) Received: (qmail 75250 invoked by uid 1001); 9 Dec 2000 19:21:28 +0000 (GMT) To: mwm@mired.org Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 9 Dec 2000 13:05:32 -0600 (CST)" References: <14898.33404.356173.963351@guru.mired.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 09 Dec 2000 20:21:28 +0100 Message-ID: <75248.976389688@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rant second: FreeBSD *violates* years of traditions with it's > treatment of /usr/local. /usr/local is for *local* things, not add-on > software packages! Coopting /usr/local for non-local software creates > needless complexity and confusion, which of course leads to needless > pain. Agreed. It would be nice if FreeBSD could use the same system as NetBSD, storing the packages/ports under /usr/pkg. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11:24:34 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:24:32 2000 Return-Path: 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 103A237B400 for ; Sat, 9 Dec 2000 11:24:31 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 8C2B718AC; Sat, 9 Dec 2000 14:24:30 -0500 (EST) Date: Sat, 9 Dec 2000 14:24:30 -0500 From: Will Andrews To: sthaug@nethelp.no Cc: mwm@mired.org, current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation Message-ID: <20001209142430.B671@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , sthaug@nethelp.no, mwm@mired.org, current@FreeBSD.ORG References: <14898.33404.356173.963351@guru.mired.org> <75248.976389688@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <75248.976389688@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Dec 09, 2000 at 08:21:28PM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: will@puck.firepipe.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 08:21:28PM +0100, sthaug@nethelp.no wrote: > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > storing the packages/ports under /usr/pkg. That's why PREFIX exists. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11:28:10 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:28:09 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id B48F137B400 for ; Sat, 9 Dec 2000 11:28:08 -0800 (PST) Received: (qmail 75353 invoked by uid 1001); 9 Dec 2000 19:28:07 +0000 (GMT) To: will@physics.purdue.edu Cc: mwm@mired.org, current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 9 Dec 2000 14:24:30 -0500" References: <20001209142430.B671@puck.firepipe.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 09 Dec 2000 20:28:07 +0100 Message-ID: <75351.976390087@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > > storing the packages/ports under /usr/pkg. > > That's why PREFIX exists. Okay, let me rephrase: It would be nice if FreeBSD *by default* stored the packages/ports under /usr/pkg, like NetBSD (and the corresponding sources under /usr/pkgsrc). Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11:30: 6 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:30:02 2000 Return-Path: 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 DBAFD37B400 for ; Sat, 9 Dec 2000 11:30:01 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 4D44418AC; Sat, 9 Dec 2000 14:30:01 -0500 (EST) Date: Sat, 9 Dec 2000 14:30:01 -0500 From: Will Andrews To: sthaug@nethelp.no Cc: will@physics.purdue.edu, mwm@mired.org, current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation Message-ID: <20001209143001.C671@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , sthaug@nethelp.no, mwm@mired.org, current@FreeBSD.ORG References: <20001209142430.B671@puck.firepipe.net> <75351.976390087@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <75351.976390087@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Dec 09, 2000 at 08:28:07PM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: will@puck.firepipe.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 08:28:07PM +0100, sthaug@nethelp.no wrote: > Okay, let me rephrase: It would be nice if FreeBSD *by default* stored > the packages/ports under /usr/pkg, like NetBSD (and the corresponding > sources under /usr/pkgsrc). Well, that is one tradition that we'll be breaking if openpackages gains momoentum. I'm planning to hack on it most of my x-mas break (and a lot of other stuff too). -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11:37:18 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:37:16 2000 Return-Path: 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 572CE37B400 for ; Sat, 9 Dec 2000 11:37:16 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA47546; Sat, 9 Dec 2000 11:37:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eB9JbDI23668; Sat, 9 Dec 2000 11:37:13 -0800 (PST) (envelope-from obrien) Date: Sat, 9 Dec 2000 11:37:12 -0800 From: "David O'Brien" To: sthaug@nethelp.no Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation Message-ID: <20001209113712.C23244@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <20001209142430.B671@puck.firepipe.net> <75351.976390087@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <75351.976390087@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Dec 09, 2000 at 08:28:07PM +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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 08:28:07PM +0100, sthaug@nethelp.no wrote: > like NetBSD (and the corresponding sources under /usr/pkgsrc). Please stick to reasonable ideas. To move the CVS repo from ports/ to pkgsrc/ would be totally unreasonable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11:43:16 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:43:14 2000 Return-Path: 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 B355C37B400 for ; Sat, 9 Dec 2000 11:43:13 -0800 (PST) Received: (qmail 30035 invoked from network); 9 Dec 2000 19:38:02 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 9 Dec 2000 19:38:02 -0000 Received: (qmail 13249 invoked from network); 9 Dec 2000 19:43:12 -0000 Received: from unknown (HELO dsl081-020-229-sea1.dsl-isp.net) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 9 Dec 2000 19:43:12 -0000 Received: (from tomdean@localhost) by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.9.3) id eB9JhCo07826; Sat, 9 Dec 2000 11:43:12 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Sat, 9 Dec 2000 11:43:12 -0800 (PST) Message-Id: <200012091943.eB9JhCo07826@dsl081-020-229-sea1.dsl-isp.net> X-Authentication-Warning: dsl081-020-229-sea1.dsl-isp.net: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: current@FreeBSD.ORG In-reply-to: <20001208183519.B1210@cae88-102-101.sc.rr.com> (dmaddox@sc.rr.com) Subject: Re: Problem With Man Formatting References: <200012082257.eB8Mv6G02715@dsl081-020-229-sea1.dsl-isp.net> <20001208183519.B1210@cae88-102-101.sc.rr.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dropped off the list for a day, or so, during an ISP change. Did I miss a resolution? # ls -l `which groff` -r-xr-xr-x 1 root wheel 62860 Dec 7 00:01 /usr/bin/groff* # groff -v GNU troff version 1.16.1 #ls -l `which man` -r-sr-xr-x 1 man wheel 28576 Dec 7 00:01 /usr/bin/man* # man -d zzz ctype locale env: Invalid argument using more as pager ... status from is_newer() = -2 ... Formatting page, please wait... trying command: (cd /usr/share/man ; /usr/bin/zcat /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | /usr/bin/groff -S -Wall -mtty-char -man -Tascii | /usr/bin/col | /usr/bin/gzip -c) No output, debug mode. using default preprocessor sequence Couldn't open /usr/share/man/cat8/zzz.8.gz.tmpiYU0us for writing. using default preprocessor sequence trying command: (cd /usr/share/man ; /usr/bin/zcat /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | /usr/bin/groff -S -Wall -mtty-char -man -Tascii | /usr/bin/col | more) tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 11:59:55 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:59:53 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 30A0837B400 for ; Sat, 9 Dec 2000 11:59:53 -0800 (PST) Received: (qmail 53610 invoked by uid 100); 9 Dec 2000 19:59:52 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14898.36663.855320.410475@guru.mired.org> Date: Sat, 9 Dec 2000 13:59:51 -0600 (CST) To: Will Andrews Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: /usr/local misuse (Was: Confusing error messages from shell image activation) In-Reply-To: <20001209142430.B671@puck.firepipe.net> References: <14898.33404.356173.963351@guru.mired.org> <75248.976389688@verdi.nethelp.no> <20001209142430.B671@puck.firepipe.net> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews types: > On Sat, Dec 09, 2000 at 08:21:28PM +0100, sthaug@nethelp.no wrote: > > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > > storing the packages/ports under /usr/pkg. > That's why PREFIX exists. I know. Unfortunately, support for PREFIX seems to draw more lip service than actual service. I've urged a number of times that portlint should test for this, or that the porters handbook should include instructions for checking this (it's actually pretty easy), all to no avail. Last time I checked, Perl modules installed by the standard perl module installer always go to /usr/local. Other may go to ${PREFIX}, but the Perl interpreter doesn't know to search there for modules, so the port generally winds up broken anyway. On the upside, I regularly pr (with patches as often as possible) ports that aren't PREFIX-clean, and they do get fixed. http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 12:29:58 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 12:29:57 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 1CF8637B400; Sat, 9 Dec 2000 12:29:57 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 4C2098BB; Sat, 9 Dec 2000 12:29:53 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id MAA02619; Sat, 9 Dec 2000 12:29:52 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A329641.CC6D8447@cup.hp.com> Date: Sat, 09 Dec 2000 12:29:54 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > On Fri, Dec 08, 2000 at 06:22:09PM -0800, Marcel Moolenaar wrote: > > Ruslan Ermilov wrote: > > > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > > problem with groff(1). > > > > Sorry, I missed this statement before. What exactly are the > > bootstrapping problems you're seeing? > > > New groff(1) provides new versions of macro packages and device > files. When building, we should use THEM rather than installed > (obsolete) ones. Is the old groff(1) incompatible with the new groff(1) in the sense that manpages created with the old groff(1) are visibly different from the manpages created with the new groff(1)? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 12:43:26 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 12:43:24 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 7050337B400; Sat, 9 Dec 2000 12:43:24 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 84B18A2E; Sat, 9 Dec 2000 12:43:23 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id MAA02853; Sat, 9 Dec 2000 12:43:22 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A32996C.1BE57FCE@cup.hp.com> Date: Sat, 09 Dec 2000 12:43:24 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319650.90FE8EAE@cup.hp.com> <20001209154901.B78374@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > On Fri, Dec 08, 2000 at 06:17:52PM -0800, Marcel Moolenaar wrote: > > Ruslan Ermilov wrote: > > > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > > problem with groff(1). I have lightly tested this on my -stable > > > box, and would appreciate a feedback on them. > > > > Do not remove the USRDIRS and INCDIRS and replace it with mtree (ie make > > hierarchy). There's no need to duplicate the complete hierarchy inthe > > object tree. Also, mtree fiddles with ownership and mods, which is not > > appropriate when building. > > > The -U flag to mtree(8) could be eliminated for this case... According to the manpage, if you remove -U it doesn't create new directories or symlinks. At least that's how I interpret it. The whole purpose of running mtree is the creation of directories, so it's a minor discomfort when it doesn't do that :-) > > Which additional directories do you need? > > > Everyting below /usr/share/tmac and /usr/share/groff_font: [snip] > The new groff(1) release is likely to provide new groff_font > subdirectories, so we would need to update USRDIRS every time > we upgrade groff(1). Does it look reasonable? If we intend to upgrade groff(1) once a week, no. If we do it once a year, yes. It's is a long list of directories and I prefer we do not need to sum them up in src/Makefile.inc1. On the other hand, I also don't want to use mtree. This is what I'm thinking about: 1. Determine if there's a real bootstrapping problem 2. If there's no bootstrapping issue, goto pub :-) 3. Add list of directories to src/Makefile.inc1 4. Write script to parse mtree files for use in build 5. If not possible, reconsider using mtree 6. else, replace lists by running the script. Thoughts? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 13:38:34 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 13:38:33 2000 Return-Path: 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 3F68D37B401 for ; Sat, 9 Dec 2000 13:38:33 -0800 (PST) Received: (qmail 32251 invoked from network); 9 Dec 2000 21:33:21 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 9 Dec 2000 21:33:21 -0000 Received: (qmail 5292 invoked from network); 9 Dec 2000 21:38:31 -0000 Received: from unknown (HELO dsl081-020-229-sea1.dsl-isp.net) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 9 Dec 2000 21:38:31 -0000 Received: (from tomdean@localhost) by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.9.3) id eB9LcVW08042; Sat, 9 Dec 2000 13:38:31 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Sat, 9 Dec 2000 13:38:31 -0800 (PST) Message-Id: <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> X-Authentication-Warning: dsl081-020-229-sea1.dsl-isp.net: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: marcel@cup.hp.com Cc: ru@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <3A329641.CC6D8447@cup.hp.com> (message from Marcel Moolenaar on Sat, 09 Dec 2000 12:29:54 -0800) Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this the problem I see with mal-formatted man pages? The pages appear as 1 block with no headers, tities, etc. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 13:48:25 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 13:48:23 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id C998437B401; Sat, 9 Dec 2000 13:48:23 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 69A64246; Sat, 9 Dec 2000 13:48:23 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA03698; Sat, 9 Dec 2000 13:48:21 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A32A8A5.65C69B94@cup.hp.com> Date: Sat, 09 Dec 2000 13:48:21 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas D. Dean" Cc: ru@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas D. Dean" wrote: > > Is this the problem I see with mal-formatted man pages? Possibly. I don't know if we changed files to get our sources working with the new groff(1). If we did, we definitely have a bootstrapping problem, because that would mean that we can't reliably create manpages with the old groff(1). If this is the case for you, then remaking the manpages with the new groff(1) should solve your problem. If that doesn't help, then you have to give us more information to work on. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 14:33:47 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 14:33:44 2000 Return-Path: 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 38BDF37B400 for ; Sat, 9 Dec 2000 14:33:44 -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 eB9MWsw54607; Sat, 9 Dec 2000 14:32:54 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: sthaug@nethelp.no Cc: will@physics.purdue.edu, mwm@mired.org, current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: Message from sthaug@nethelp.no of "Sat, 09 Dec 2000 20:28:07 +0100." <75351.976390087@verdi.nethelp.no> Date: Sat, 09 Dec 2000 14:32:54 -0800 Message-ID: <54603.976401174@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not likely to happen - people have an investment in the current scheme and it would certainly mess with their heads if one day FreeBSD suddenly started doing something entirely different than what it's been doing for the last 7 years. For those who really want to track the NetBSD way of doing things, it can be set according to their own tastes. - Jordan > > > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > > > storing the packages/ports under /usr/pkg. > > > > That's why PREFIX exists. > > Okay, let me rephrase: It would be nice if FreeBSD *by default* stored > the packages/ports under /usr/pkg, like NetBSD (and the corresponding > sources under /usr/pkgsrc). > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > 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 Dec 9 17:21:12 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 17:21:11 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D5E537B400 for ; Sat, 9 Dec 2000 17:21:11 -0800 (PST) Received: (from pete@localhost) by ns.altadena.net (8.11.1/8.8.8) id eBA1JKo89665 for current@freebsd.org; Sat, 9 Dec 2000 17:19:20 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200012100119.eBA1JKo89665@ns.altadena.net> Subject: Re: Lucent Orinoco Gold PCCard? To: current@freebsd.org Date: Sat, 9 Dec 2000 17:19:20 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is also a new access point (either just available or "RSN") from Zyxel (316); it is a combination of a 310 (cable modem/bridged DSL/PPPOE router) and single-card bridged access point. I'm using one at work (overkill since I'm not using the router) as a bridged access point; it works just fine in that role (plug the ethernet into the "LAN" (10/100!) port and leave the "WAN" port empty). Stock it only comes with 40 bit but maybe could be used with a gold (or equivalent) card (haven't tried it, though). The card it comes with is OEM'd by someone (Melco?) and does have an antenna jack. At home I'm currently using a Lucent card in a FBSD machine as a base; IBSS create does work; it gets a hybrid between BSS and ad-hoc mode (at least the client connects in infrastructure mode). In this mode the client is transmitting a lot, though; makes the laptop power supply get pretty warm. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 18:25:40 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 18:25:34 2000 Return-Path: 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 5D01E37B401 for ; Sat, 9 Dec 2000 18:25:34 -0800 (PST) Received: (qmail 4287 invoked from network); 10 Dec 2000 02:20:21 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 10 Dec 2000 02:20:21 -0000 Received: (qmail 29213 invoked from network); 10 Dec 2000 02:25:32 -0000 Received: from unknown (HELO dsl081-020-229-sea1.dsl-isp.net) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 10 Dec 2000 02:25:32 -0000 Received: (from tomdean@localhost) by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.9.3) id eBA2PVH08442; Sat, 9 Dec 2000 18:25:31 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Sat, 9 Dec 2000 18:25:31 -0800 (PST) Message-Id: <200012100225.eBA2PVH08442@dsl081-020-229-sea1.dsl-isp.net> X-Authentication-Warning: dsl081-020-229-sea1.dsl-isp.net: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: marcel@cup.hp.com Cc: ru@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <3A32A8A5.65C69B94@cup.hp.com> (message from Marcel Moolenaar on Sat, 09 Dec 2000 13:48:21 -0800) Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> <3A32A8A5.65C69B94@cup.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # ls /usr/share/man/man*/zzz* /usr/share/man/man8/zzz.8.gz # ls /usr/share/man/cat*/zzz* ls: No match. Ok, so, man zzz should reformat the man page. I have attached the output of 'man -d zzz' and 'man zzz' After 'man zzz', I see # ls /usr/share/man/cat*/zzz* /usr/share/man/cat8/zzz.8.gz So, the man page was reformatted with the new groff. tomdean ======================= # man -d zzz ctype locale env: Invalid argument using more as pager found mandatory man directory /usr/share/man found mandatory man directory /usr/share/perl/man found optional man directory /usr/local/lib/perl5/5.00503/man found manpath map /bin --> /usr/share/man found manpath map /usr/bin --> /usr/share/man found manpath map /usr/local/bin --> /usr/local/man found manpath map /usr/X11R6/bin --> /usr/X11R6/man search path for pages determined by manpath is /usr/home/tomdean/man:/usr/local/man:/usr/share/man:/usr/X11R6/man:/usr/local/LessTif/doc/man:/usr/local/pgsql/man adding /usr/home/tomdean/man to manpathlist adding /usr/local/man to manpathlist adding /usr/share/man to manpathlist adding /usr/X11R6/man to manpathlist Warning: couldn't stat file /usr/local/LessTif/doc/man! adding /usr/local/pgsql/man to manpathlist searching in /usr/home/tomdean/man trying section 1 with globbing globbing /usr/home/tomdean/man/man1/zzz.1* globbing /usr/home/tomdean/man/man1/zzz.0* globbing /usr/home/tomdean/man/cat1/zzz.1* globbing /usr/home/tomdean/man/cat1/zzz.0* searching in /usr/local/man trying section 1 with globbing globbing /usr/local/man/man1/zzz.1* globbing /usr/local/man/man1/zzz.0* globbing /usr/local/man/cat1/zzz.1* globbing /usr/local/man/cat1/zzz.0* searching in /usr/share/man trying section 1 with globbing globbing /usr/share/man/man1/zzz.1* globbing /usr/share/man/man1/zzz.0* globbing /usr/share/man/cat1/zzz.1* globbing /usr/share/man/cat1/zzz.0* searching in /usr/X11R6/man trying section 1 with globbing globbing /usr/X11R6/man/man1/zzz.1* globbing /usr/X11R6/man/man1/zzz.0* globbing /usr/X11R6/man/cat1/zzz.1* globbing /usr/X11R6/man/cat1/zzz.0* searching in /usr/local/pgsql/man trying section 1 with globbing globbing /usr/local/pgsql/man/man1/zzz.1* globbing /usr/local/pgsql/man/man1/zzz.0* globbing /usr/local/pgsql/man/cat1/zzz.1* globbing /usr/local/pgsql/man/cat1/zzz.0* searching in /usr/home/tomdean/man trying section 1aout with globbing globbing /usr/home/tomdean/man/man1aout/zzz.1aout* globbing /usr/home/tomdean/man/man1aout/zzz.0* globbing /usr/home/tomdean/man/cat1aout/zzz.1aout* globbing /usr/home/tomdean/man/cat1aout/zzz.0* searching in /usr/local/man trying section 1aout with globbing globbing /usr/local/man/man1aout/zzz.1aout* globbing /usr/local/man/man1aout/zzz.0* globbing /usr/local/man/cat1aout/zzz.1aout* globbing /usr/local/man/cat1aout/zzz.0* searching in /usr/share/man trying section 1aout with globbing globbing /usr/share/man/man1aout/zzz.1aout* globbing /usr/share/man/man1aout/zzz.0* globbing /usr/share/man/cat1aout/zzz.1aout* globbing /usr/share/man/cat1aout/zzz.0* searching in /usr/X11R6/man trying section 1aout with globbing globbing /usr/X11R6/man/man1aout/zzz.1aout* globbing /usr/X11R6/man/man1aout/zzz.0* globbing /usr/X11R6/man/cat1aout/zzz.1aout* globbing /usr/X11R6/man/cat1aout/zzz.0* searching in /usr/local/pgsql/man trying section 1aout with globbing globbing /usr/local/pgsql/man/man1aout/zzz.1aout* globbing /usr/local/pgsql/man/man1aout/zzz.0* globbing /usr/local/pgsql/man/cat1aout/zzz.1aout* globbing /usr/local/pgsql/man/cat1aout/zzz.0* searching in /usr/home/tomdean/man trying section 8 with globbing globbing /usr/home/tomdean/man/man8/zzz.8* globbing /usr/home/tomdean/man/man8/zzz.0* globbing /usr/home/tomdean/man/cat8/zzz.8* globbing /usr/home/tomdean/man/cat8/zzz.0* searching in /usr/local/man trying section 8 with globbing globbing /usr/local/man/man8/zzz.8* globbing /usr/local/man/man8/zzz.0* globbing /usr/local/man/cat8/zzz.8* globbing /usr/local/man/cat8/zzz.0* searching in /usr/share/man trying section 8 with globbing globbing /usr/share/man/man8/zzz.8* to_name in convert_name () is: /usr/share/man/cat8/zzz.8.gz will try to write /usr/share/man/cat8/zzz.8.gz if needed status from is_newer() = -2 using default preprocessor sequence mode of /usr/share/man/cat8/zzz.8.gz.tmpwUNTCA is now 644 Formatting page, please wait... trying command: (cd /usr/share/man ; /usr/bin/zcat /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | /usr/bin/groff -S -Wall -mtty-char -man -Tascii | /usr/bin/col | /usr/bin/gzip -c) No output, debug mode. using default preprocessor sequence Couldn't open /usr/share/man/cat8/zzz.8.gz.tmpB0cdyZ for writing. using default preprocessor sequence trying command: (cd /usr/share/man ; /usr/bin/zcat /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | /usr/bin/groff -S -Wall -mtty-char -man -Tascii | /usr/bin/col | more) ========================================= # man zzz Formatting page, please wait...Done. controls the Intel / Microsoft APM (Advanced Power Management) BIOS and displays the current status of APM on laptop PCs. sus- pends the system by controlling APM. The following options are available for (no options are available for ). If no options are specified, displays information and current status of APM in ver- bose mode. If multiple display options are given, the values are displayed one per line in the order given here. Display the cur- rent AC-line status as an integer value. The values 0 and 1 cor- respond to the state or state, respectively. Display an integer value reflecting the current battery status. The values 0, 1, 2, 3, correspond to the status, status, status, status respectively. Disable/enable suspending of the display separately from a normal suspend using the boolean value for This feature seems to not work on many different laptops, including the Libretto 30CT and 50CT. Enable or disable APM functions of the computer, depending on the boolean argument. Depending on the boolean value of enable or disable the HLT instruction in the kernel context switch routine. These options are not necessary for almost all APM implementations, but for some implementations whose call exe- cutes both CPU clock slowdown and HLT instruction, is necessary to prevent the system from reducing its peak performance. See for details. Display the remaining battery percentage. If your laptop does not support this function, 255 is displayed. Enable the resume wakeup timer, if the laptop supports it. This doesn't actually suspend the laptop, but if the laptop is suspended, and it supports resume from suspend, then it will be resume after seconds (from when you run this command, not from when you sus- pend). Display the status of the APM support as an integer value. The values 0 and 1 correspond to the state or state respectively. Display the estimated remaining battery lifetime in seconds. If it is unknown, -1 is displayed. Transition the system into standby mode. This mode uses less power than full power mode, but more than suspend mode. Some laptops support resuming from this state on timer or Ring Indicator events. The output of apm tells what your laptop claims to support. Suspend the system. It is equivalent to Some APM implementations do not support parameters needed by On such systems, displays them as unknown. Some APM implementations cannot handle events such as pushing the power button or closing the cover. On such implemen- tations, the system be suspended by using or has been merged in and thus replaces all of its functionality. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 18:37:18 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 18:37:17 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id E4CD437B400; Sat, 9 Dec 2000 18:37:16 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 3758315FD; Sat, 9 Dec 2000 18:37:16 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id SAA07489; Sat, 9 Dec 2000 18:37:15 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A32EC5A.6953D817@cup.hp.com> Date: Sat, 09 Dec 2000 18:37:14 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas D. Dean" Cc: ru@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> <3A32A8A5.65C69B94@cup.hp.com> <200012100225.eBA2PVH08442@dsl081-020-229-sea1.dsl-isp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas D. Dean" wrote: > > trying command: (cd /usr/share/man ; /usr/bin/zcat > /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | > /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... ^^^^ should be -mandoc > trying command: (cd /usr/share/man ; /usr/bin/zcat > /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | > /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... ^^^^ should be -mandoc -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 18:45:58 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 18:45:57 2000 Return-Path: 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 DB93737B401 for ; Sat, 9 Dec 2000 18:45:56 -0800 (PST) Received: (qmail 19870 invoked from network); 10 Dec 2000 02:40:43 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 10 Dec 2000 02:40:43 -0000 Received: (qmail 3427 invoked from network); 10 Dec 2000 02:45:55 -0000 Received: from unknown (HELO dsl081-020-229-sea1.dsl-isp.net) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 10 Dec 2000 02:45:55 -0000 Received: (from tomdean@localhost) by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.11.1) id eBA2js708522; Sat, 9 Dec 2000 18:45:54 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Sat, 9 Dec 2000 18:45:54 -0800 (PST) Message-Id: <200012100245.eBA2js708522@dsl081-020-229-sea1.dsl-isp.net> From: "Thomas D. Dean" To: marcel@cup.hp.com Cc: ru@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <3A32EC5A.6953D817@cup.hp.com> (message from Marcel Moolenaar on Sat, 09 Dec 2000 18:37:14 -0800) Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> <3A32A8A5.65C69B94@cup.hp.com> <200012100225.eBA2PVH08442@dsl081-020-229-sea1.dsl-isp.net> <3A32EC5A.6953D817@cup.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... > ^^^^ > should be -mandoc This was generated by 'man', not me. There appears to be a problem in man. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 19:24:34 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 19:24:32 2000 Return-Path: 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 8691937B400 for ; Sat, 9 Dec 2000 19:24:32 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA49389; Sat, 9 Dec 2000 19:24:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBA3OUj32272; Sat, 9 Dec 2000 19:24:30 -0800 (PST) (envelope-from obrien) Date: Sat, 9 Dec 2000 19:24:29 -0800 From: "David O'Brien" To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) Message-ID: <20001209192429.A32252@dragon.nuxi.com> Reply-To: current@FreeBSD.org References: <20001208181908.A12716@sunbay.com> <3A319650.90FE8EAE@cup.hp.com> <20001209154901.B78374@sunbay.com> <3A32996C.1BE57FCE@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A32996C.1BE57FCE@cup.hp.com>; from marcel@cup.hp.com on Sat, Dec 09, 2000 at 12:43:24PM -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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 12:43:24PM -0800, Marcel Moolenaar wrote: > On the other hand, I also don't want to use mtree. The only thing you don't like about mtree is it changing ownership + modes, right? If so, what about a new flag to mtree to make it only create directories and nothing else? -- -- 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 Dec 9 19:26:50 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 19:26:49 2000 Return-Path: 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 1C85837B400 for ; Sat, 9 Dec 2000 19:26:49 -0800 (PST) Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA49396; Sat, 9 Dec 2000 19:26:48 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eBA3QkG32295; Sat, 9 Dec 2000 19:26:46 -0800 (PST) (envelope-from obrien) Date: Sat, 9 Dec 2000 19:26:46 -0800 From: "David O'Brien" To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: /usr/local misuse (Was: Confusing error messages from shell image activation) Message-ID: <20001209192646.B32252@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <14898.33404.356173.963351@guru.mired.org> <75248.976389688@verdi.nethelp.no> <20001209142430.B671@puck.firepipe.net> <14898.36663.855320.410475@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14898.36663.855320.410475@guru.mired.org>; from mwm@mired.org on Sat, Dec 09, 2000 at 01:59:51PM -0600 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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote: > I know. Unfortunately, support for PREFIX seems to draw more lip > service than actual service. I disagree. If one of the ports I maintain isn't PREFIX-clean, let me know and it _will_ be fixed. If you know others, please open a PR, let me know and I'll assign it to the maintainer. > or that the porters handbook should include instructions for checking > this (it's actually pretty easy), I always thought ``make PREFIX=/tmp/foo package'' is pretty obvious.. but maybe not... -- -- 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 Dec 9 19:40:36 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 19:40:33 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 0CA3037B400 for ; Sat, 9 Dec 2000 19:40:33 -0800 (PST) Received: (qmail 81998 invoked by uid 100); 10 Dec 2000 03:40:31 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14898.64303.432525.619458@guru.mired.org> Date: Sat, 9 Dec 2000 21:40:31 -0600 (CST) To: current@FreeBSD.ORG Subject: Re: /usr/local misuse (Was: Confusing error messages from shell image activation) In-Reply-To: <20001209192646.B32252@dragon.nuxi.com> References: <14898.33404.356173.963351@guru.mired.org> <75248.976389688@verdi.nethelp.no> <20001209142430.B671@puck.firepipe.net> <14898.36663.855320.410475@guru.mired.org> <20001209192646.B32252@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien types: > On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote: > > I know. Unfortunately, support for PREFIX seems to draw more lip > > service than actual service. > I disagree. If one of the ports I maintain isn't PREFIX-clean, let me > know and it _will_ be fixed. If you know others, please open a PR, let > me know and I'll assign it to the maintainer. Like I said, I do report them when I find them. However, things like ports with perl modules being either PREFIX dirty or broken tend to be pretty damning. But my comment is based on the experience of running a system with LOCALBASE set to something other than /usr/local. If you run systems that way and have a different experience, I'd be interested in hearing about it. > > or that the porters handbook should include instructions for checking > > this (it's actually pretty easy), > I always thought ``make PREFIX=/tmp/foo package'' is pretty obvious.. but > maybe not... It's not obvious to me. It's also not mentioned in the handbook anywhere. I suspect that most people are like me, and seldomp build packages - which would explain why it's not obvious. What does the above command do if the port isn't PREFIX clean? My personal test is "make PREFIX=/tmp/foo install && make deinstall". If something in the plist is installed outside of /tmp/foo, the deinstall will complain when it can't find it. Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 8F44937B400 for ; Sat, 9 Dec 2000 19:59:48 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id D719613DC for ; Sat, 9 Dec 2000 19:59:47 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id TAA08552 for ; Sat, 9 Dec 2000 19:59:47 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A32FFB2.BCCC5140@cup.hp.com> Date: Sat, 09 Dec 2000 19:59:46 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319650.90FE8EAE@cup.hp.com> <20001209154901.B78374@sunbay.com> <3A32996C.1BE57FCE@cup.hp.com> <20001209192429.A32252@dragon.nuxi.com> 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 Sat, Dec 09, 2000 at 12:43:24PM -0800, Marcel Moolenaar wrote: > > On the other hand, I also don't want to use mtree. > > The only thing you don't like about mtree is it changing ownership + > modes, right? Not only that. Using mtree(1) creates busloads of unnecessary directories. It's too brute-force in my book. If there's a clean way to create selective subtrees and do that without setting ownership and file mods, then I'm happy. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 20: 5:59 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 20:05:57 2000 Return-Path: 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 F368137B400 for ; Sat, 9 Dec 2000 20:05:56 -0800 (PST) Received: from newsguy.com (p23-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.24]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id NAA16585; Sun, 10 Dec 2000 13:03:21 +0900 (JST) Message-ID: <3A330010.37F216E4@newsguy.com> Date: Sun, 10 Dec 2000 13:01:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Poul-Henning Kamp Cc: "Brandon D. Valentine" , FreeBSD-CURRENT Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition References: <81426.976315454@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > >>| Partition table | Data | > >> | Slice 1 | Slice 2 | Slice 3 | Slice 4 | > >> | Disklabel | Data | > >> | c | > >> |a|b|f|g| > > > >That is really an excellent diagram. That should be in an FAQ > >somewhere. Doc committers? > > Except it is not actually correct. The BSD disklabel is usually > inside the 'a' partition and certainly inside the 'c' Is that so? Mea culpa, then. At least I knew what I was talking about wrt partition table and the actual slices. This diagram is just an example. There can be less slices, it doesn't show extended partitions (extended slices??? :), it suggests an ordering that is not necessary. If this is going to the FAQ or the handbook, a number of notes should be made to point out these (and possibly others I'm overlooking right now) issues. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 20:10: 3 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 20:09:59 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 8E3DC37B400; Sat, 9 Dec 2000 20:09:59 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id D2FBF167C; Sat, 9 Dec 2000 20:09:58 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id UAA08724; Sat, 9 Dec 2000 20:09:58 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A330215.A981B3CA@cup.hp.com> Date: Sat, 09 Dec 2000 20:09:57 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas D. Dean" Cc: ru@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> <3A32A8A5.65C69B94@cup.hp.com> <200012100225.eBA2PVH08442@dsl081-020-229-sea1.dsl-isp.net> <3A32EC5A.6953D817@cup.hp.com> <200012100245.eBA2js708522@dsl081-020-229-sea1.dsl-isp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas D. Dean" wrote: > > >> /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... > > ^^^^ > > should be -mandoc > > This was generated by 'man', not me. I understand that. > There appears to be a problem in man. Not that I'm aware of. Did you verify your settings? ie build options env.vars and local modifications? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 20:11:22 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 20:11:15 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (mailgate.rz.uni-karlsruhe.de [129.13.64.97]) by hub.freebsd.org (Postfix) with ESMTP id 0325437B400; Sat, 9 Dec 2000 20:11:14 -0800 (PST) Received: from rzstud1.rz.uni-karlsruhe.de (rzstud1.rz.uni-karlsruhe.de [129.13.197.1]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.16 #1) id 144wKQ-00044R-00; Sun, 10 Dec 2000 03:35:06 +0100 Received: from un1i by rzstud1.rz.uni-karlsruhe.de with local (Exim 2.12 #1) id 144wL4-0002Sr-00; Sun, 10 Dec 2000 03:35:46 +0100 Date: Sun, 10 Dec 2000 03:35:46 +0100 From: Philipp Mergenthaler To: dillon@FreeBSD.ORG Cc: freebsd-current@freebsd.org Subject: panic: vm_pageout_flush: partially dirty page Message-ID: <20001210033546.A13896@rz.uni-karlsruhe.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, ever since this commit: ... dillon 2000/11/18 15:06:27 PST =20 Modified files: sys/kern vfs_bio.c vfs_cluster.c vfs_subr.c vfs_vnops.c sys/sys buf.h vnode.h sys/ufs/ffs ffs_inode.c ffs_softdep.c sys/ufs/ufs ufs_readwrite.c sys/vm swap_pager.c vm_page.c vm_page.h vm_pageout.c Log: Implement a low-memory deadlock solution. =20 =2E.. I can very reliable reproduce this panic. I have INN running here (inn-2.3.0 straight from /usr/ports) and feed it articles with suck. Actually suck is run twice in a row (for different news servers) and as soon as the second run starts feeding articles to innd, the panic occurs. (In a few cases the panic occured a bit later, maybe 30 seconds.) I've appended some output from gdb and put a crash dump (96 MB / 17MB gzipped) and a debug kernel on http://ltilx150.etec.uni-karlsruhe.de/p/ (This is with sources from today.) Some additional observations: -The INN is compiled with mmap(). The history file has about 11 MBytes, the active file has just 23 lines :-). -The output from "trace" in ddb has one line more than gdb's "backtrace": [...] sync_fsyc(c76e1f7c) at sync_fsync + 0xcf sched_sync at sched_sync + 0x13a fork_trampoline at fork_trampoline + 0x1c -Apart from this situation, I haven't seen this (or any other) panic. Please let me know if I should provide additional information. Bye, Philipp --=20 http://www.uni-karlsruhe.de/~un1i/ (,.) \\\00 ) \=3D ) cc_|\_,^ gdb -k kernel.73.debug vmcore.73 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 4055040 initial pcb at 32e6c0 panicstr: from debugger panic messages: --- panic: vm_pageout_flush page 0xc04eacd0 index 0/1: partially dirty page panic: from debugger Uptime: 4m2s dumping to dev da0s1b, offset 26624 dump 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 7= 3 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 4= 8 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 2= 3 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1=20 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:477 477 if (dumping++) { (kgdb) bt #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:477 #1 0xc0178080 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 20 #2 0xc01784d9 in panic (fmt=3D0xc02b70d4 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:570 #3 0xc0132c01 in db_panic (addr=3D-1071064268, have_addr=3D0, count=3D-1,= =20 modif=3D0xc70e1c4c "") at /usr/src/sys/ddb/db_command.c:433 #4 0xc0132ba1 in db_command (last_cmdp=3D0xc02f81d4, cmd_table=3D0xc02f803= 4,=20 aux_cmd_tablep=3D0xc031acb8) at /usr/src/sys/ddb/db_command.c:333 #5 0xc0132c66 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 #6 0xc0134e2b in db_trap (type=3D3, code=3D0) at /usr/src/sys/ddb/db_trap.= c:71 #7 0xc028d8c6 in kdb_trap (type=3D3, code=3D0, regs=3D0xc70e1d4c) at /usr/src/sys/i386/i386/db_interface.c:163 #8 0xc029989c in trap (frame=3D{tf_fs =3D 16, tf_es =3D 16, tf_ds =3D 16, = tf_edi =3D 0,=20 tf_esi =3D 256, tf_ebp =3D -955376232, tf_isp =3D -955376264,=20 tf_ebx =3D 2097666, tf_edx =3D -1072980320, tf_ecx =3D 32, tf_eax =3D= 18,=20 tf_trapno =3D 3, tf_err =3D 0, tf_eip =3D -1071064268, tf_cs =3D 8,= =20 tf_eflags =3D 2097222, tf_esp =3D -1070695009, tf_ss =3D -1070848829}) at /usr/src/sys/i386/i386/trap.c:589 #9 0xc028db34 in Debugger (msg=3D0xc02c24c3 "panic") at machine/cpufunc.h:= 60 #10 0xc01784d0 in panic ( fmt=3D0xc02e2580 "vm_pageout_flush page %p index %d/%d: partially dirty= page") at /usr/src/sys/kern/kern_shutdown.c:568 #11 0xc027798f in vm_pageout_flush (mc=3D0xc70e1df4, count=3D1, flags=3D0) at /usr/src/sys/vm/vm_pageout.c:378 #12 0xc0274902 in vm_object_page_clean (object=3D0xc78754e0, start=3D0, end= =3D0,=20 flags=3D4) at /usr/src/sys/vm/vm_object.c:655 #13 0xc01ae696 in vfs_msync (mp=3D0xc0aa1200, flags=3D2) at /usr/src/sys/kern/vfs_subr.c:2597 #14 0xc01aea73 in sync_fsync (ap=3D0xc70e1f7c) at /usr/src/sys/kern/vfs_subr.c:2866 #15 0xc01ac9e6 in sched_sync () at vnode_if.h:423 (kgdb) frame 15 #15 0xc01ac9e6 in sched_sync () at vnode_if.h:423 423 rc =3D VCALL(vp, VOFFSET(vop_fsync), &a); (kgdb) print a $1 =3D {a_desc =3D 0xc02f2a40, a_vp =3D 0xc781bd00, a_cred =3D 0xc0699e00,= =20 a_waitfor =3D 3, a_p =3D 0xc6a0cfe0} (kgdb) print vp $2 =3D (struct vnode *) 0xc781bd00 (kgdb) print *((struct vnode *) 0xc781bd00) $3 =3D {v_flag =3D 2097152, v_usecount =3D 1, v_writecount =3D 0, v_holdcnt= =3D 0,=20 v_id =3D 92, v_mount =3D 0xc0aa1200, v_op =3D 0xc0a56600, v_freelist =3D { tqe_next =3D 0x0, tqe_prev =3D 0x0}, v_mntvnodes =3D {le_next =3D 0x0,= =20 le_prev =3D 0xc7819524}, v_cleanblkhd =3D {tqh_first =3D 0x0,=20 tqh_last =3D 0xc781bd2c}, v_dirtyblkhd =3D {tqh_first =3D 0x0,=20 tqh_last =3D 0xc781bd34}, v_synclist =3D {le_next =3D 0x0,=20 le_prev =3D 0xc0a4a798}, v_numoutput =3D 0, v_type =3D VNON, v_un =3D { vu_mountedhere =3D 0x0, vu_socket =3D 0x0, vu_spec =3D {vu_specinfo =3D= 0x0,=20 vu_specnext =3D {sle_next =3D 0x0}}, vu_fifoinfo =3D 0x0}, v_lease = =3D 0x0,=20 v_lastw =3D 0, v_cstart =3D 0, v_lasta =3D 0, v_clen =3D 0, v_object =3D = 0x0,=20 v_interlock =3D {mtx_lock =3D 8, mtx_recurse =3D 0, mtx_saveintr =3D 0,= =20 mtx_description =3D 0xc02c82e5 "vnode interlock", mtx_blocked =3D { tqh_first =3D 0x0, tqh_last =3D 0xc781bd7c}, mtx_contested =3D {le_ne= xt =3D 0x0,=20 le_prev =3D 0x0}, mtx_next =3D 0xc781bc6c, mtx_prev =3D 0xc781be6c}, = v_lock =3D { lk_interlock =3D 0xc0692e28, lk_flags =3D 16777216, lk_sharecount =3D 0= ,=20 lk_waitcount =3D 0, lk_exclusivecount =3D 0, lk_prio =3D 20,=20 lk_wmesg =3D 0xc02c82f5 "vnlock", lk_timo =3D 0, lk_lockholder =3D -1},= =20 v_vnlock =3D 0x0, v_tag =3D VT_VFS, v_data =3D 0x0, v_cache_src =3D { lh_first =3D 0x0}, v_cache_dst =3D {tqh_first =3D 0x0, tqh_last =3D 0xc= 781bdc4},=20 v_dd =3D 0xc781bd00, v_ddid =3D 0, v_pollinfo =3D {vpi_lock =3D {lock_dat= a =3D 0},=20 vpi_selinfo =3D {si_pid =3D 0, si_note =3D {slh_first =3D 0x0}, si_flag= s =3D 0},=20 vpi_events =3D 0, vpi_revents =3D 0}, v_vxproc =3D 0x0} (kgdb) down #14 0xc01aea73 in sync_fsync (ap=3D0xc70e1f7c) at /usr/src/sys/kern/vfs_subr.c:2866 2866 vfs_msync(mp, MNT_NOWAIT); (kgdb) print mp $4 =3D (struct mount *) 0xc0aa1200 (kgdb) print *((struct mount *) 0xc0aa1200) $5 =3D {mnt_list =3D {tqe_next =3D 0xc0ad9400, tqe_prev =3D 0xc0aa1a00},=20 mnt_op =3D 0xc030df20, mnt_vfc =3D 0xc030df60, mnt_vnodecovered =3D 0xc70= d8200,=20 mnt_syncer =3D 0xc781bd00, mnt_vnodelist =3D {lh_first =3D 0xc7828e00},= =20 mnt_lock =3D {lk_interlock =3D 0xc0692e00, lk_flags =3D 17825792,=20 lk_sharecount =3D 1, lk_waitcount =3D 0, lk_exclusivecount =3D 0, lk_pr= io =3D 20,=20 lk_wmesg =3D 0xc02c88a1 "vfslock", lk_timo =3D 0, lk_lockholder =3D -1}= ,=20 mnt_writeopcount =3D 1, mnt_flag =3D 4096, mnt_kern_flag =3D 0,=20 mnt_maxsymlinklen =3D 60, mnt_stat =3D {f_spare2 =3D 0, f_bsize =3D 1024,= =20 f_iosize =3D 8192, f_blocks =3D 1817777, f_bfree =3D 201403, f_bavail = =3D 55981,=20 f_files =3D 445438, f_ffree =3D 309929, f_fsid =3D {val =3D {901998103,= =20 703157984}}, f_owner =3D 0, f_type =3D 6, f_flags =3D 4096,=20 f_syncwrites =3D 110, f_asyncwrites =3D 256,=20 f_fstypename =3D "ufs", '\000' ,=20 f_mntonname =3D "/usr", '\000' , f_syncreads =3D 727,= =20 f_asyncreads =3D 213, f_spares1 =3D 0,=20 f_mntfromname =3D "/dev/da0s1f", '\000' , f_spares2 = =3D 0,=20 f_spare =3D {0, 0}}, mnt_data =3D 0xc0aa1000, mnt_time =3D 0,=20 mnt_iosize_max =3D 65536} (kgdb) down #13 0xc01ae696 in vfs_msync (mp=3D0xc0aa1200, flags=3D2) at /usr/src/sys/kern/vfs_subr.c:2597 2597 vm_object_page_clean(obj, 0, 0, flags =3D=3D MNT_WAIT ? OBJPC_SYN= C : OBJPC_NOSYNC); (kgdb) print obj $6 =3D (struct vm_object *) 0xc78754e0 (kgdb) print *((struct vm_object *) 0xc78754e0) $7 =3D {object_list =3D {tqe_next =3D 0xc787fa20, tqe_prev =3D 0xc7875420},= =20 shadow_head =3D {tqh_first =3D 0x0, tqh_last =3D 0xc78754e8}, shadow_list= =3D { tqe_next =3D 0x0, tqe_prev =3D 0xc787fc10}, memq =3D {tqh_first =3D 0xc= 04eacd0,=20 tqh_last =3D 0xc04eacdc}, generation =3D 31, size =3D 1, ref_count =3D = 1,=20 shadow_count =3D 0, hash_rand =3D -767679, type =3D 2 '\002', flags =3D 5= 12,=20 pg_color =3D 13, paging_in_progress =3D 0, resident_page_count =3D 1,=20 backing_object =3D 0x0, backing_object_offset =3D 0, pager_object_list = =3D { tqe_next =3D 0x0, tqe_prev =3D 0x0}, handle =3D 0xc70d6900, un_pager = =3D {vnp =3D { vnp_size =3D 932}, devp =3D {devp_pglist =3D {tqh_first =3D 0x3a4,=20 tqh_last =3D 0x0}}, swp =3D {swp_bcount =3D 932}}} (kgdb) down #12 0xc0274902 in vm_object_page_clean (object=3D0xc78754e0, start=3D0, end= =3D0,=20 flags=3D4) at /usr/src/sys/vm/vm_object.c:655 655 vm_pageout_flush(ma, runlen, pagerflags); (kgdb) print runlen $8 =3D 1 (kgdb) print pagerflags $9 =3D 0 (kgdb) print ma $10 =3D (vm_page_t (*)[0]) 0xc70e1df4 (kgdb) print *(struct vm_page *)ma[0] $14 =3D {pageq =3D {tqe_next =3D 0xc04eacd0, tqe_prev =3D 0xc70e1e28},=20 hnext =3D 0xc01a4bc0, listq =3D {tqe_next =3D 0x0, tqe_prev =3D 0xc28590e= 4},=20 object =3D 0xc70e1e28, pindex =3D 3222948849, phys_addr =3D 0, md =3D { pv_list_count =3D -1031434144, pv_list =3D {tqh_first =3D 0x1, tqh_last= =3D 0x0}},=20 queue =3D 37092, flags =3D 49797, pc =3D 0, wire_count =3D 0, hold_count = =3D 7780,=20 act_count =3D 14 '\016', busy =3D 199 '=C7', valid =3D 97 'a', dirty =3D = 64 '@'} (kgdb) print *((struct vm_page *)ma[1]) $15 =3D {pageq =3D {tqe_next =3D 0x28c04eac, tqe_prev =3D 0xc0c70e1e},=20 hnext =3D 0xc01a4b, listq =3D {tqe_next =3D 0xe4000000, tqe_prev =3D 0x28= c28590},=20 object =3D 0xf1c70e1e, pindex =3D 12589643, phys_addr =3D 1610612736, md = =3D { pv_list_count =3D 29525392, pv_list =3D {tqh_first =3D 0x0,=20 tqh_last =3D 0xe4000000}}, queue =3D 34192, flags =3D 194, pc =3D 0,= =20 wire_count =3D 25600, hold_count =3D 3614, act_count =3D 199 '=C7', busy = =3D 97 'a',=20 valid =3D 64 '@', dirty =3D 26 '\032'} (kgdb) down #11 0xc027798f in vm_pageout_flush (mc=3D0xc70e1df4, count=3D1, flags=3D0) at /usr/src/sys/vm/vm_pageout.c:378 378 KASSERT(mc[i]->valid =3D=3D VM_PAGE_BITS_ALL && mc[i]->dirty =3D=3D V= M_PAGE_BITS_ALL, ("vm_pageout_flush page %p index %d/%d: partially dirty pa= ge", mc[i], i, count)); (kgdb) print i $16 =3D 0 (kgdb) print count $17 =3D 1 (kgdb) print mc[0] $18 =3D 0xc04eacd0 (kgdb) print *mc[0] $19 =3D {pageq =3D {tqe_next =3D 0xc04baa6c, tqe_prev =3D 0xc0500af8}, hnex= t =3D 0x0,=20 listq =3D {tqe_next =3D 0x0, tqe_prev =3D 0xc78754f8}, object =3D 0xc7875= 4e0,=20 pindex =3D 0, phys_addr =3D 39374848, md =3D {pv_list_count =3D 1, pv_lis= t =3D { tqh_first =3D 0xc0635e40, tqh_last =3D 0xc0635e48}}, queue =3D 33,=20 flags =3D 160, pc =3D 13, wire_count =3D 0, hold_count =3D 0, act_count = =3D 5 '\005',=20 busy =3D 0 '\000', valid =3D 255 '=FF', dirty =3D 252 '=FC'} (kgdb) quit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 20:38:14 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 20:38:13 2000 Return-Path: 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 DC65737B400 for ; Sat, 9 Dec 2000 20:38:11 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id XAA25886; Sat, 9 Dec 2000 23:38:07 -0500 (EST) (envelope-from wollman) Date: Sat, 9 Dec 2000 23:38:07 -0500 (EST) From: Garrett Wollman Message-Id: <200012100438.XAA25886@khavrinen.lcs.mit.edu> To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: <14898.31393.228926.763711@guru.mired.org> References: <14876.48112.785320.465213@guru.mired.org> <20001123110828.V18037@fw.wintelcom.net> <14877.65275.744127.863828@guru.mired.org> <200011241948.OAA64331@khavrinen.lcs.mit.edu> <14898.31393.228926.763711@guru.mired.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > There are other places where FreeBSD doesn't comply with the > appropriate standard - packages vs. FHS I have never heard of ``FHS''. What is its ANSI, FIPS, IEEE, IEC, or ISO number? -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 21:31:27 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 21:31:24 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2117637B400; Sat, 9 Dec 2000 21:31:21 -0800 (PST) Received: from localhost (4xm8p0@localhost [127.0.0.1]) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id eBA5UwD14791; Sun, 10 Dec 2000 00:31:09 -0500 (EST) (envelope-from green@FreeBSD.org) Message-Id: <200012100531.eBA5UwD14791@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Bruce Evans Cc: Matthew Thyer , Mike Smith , "John W. De Boskey" , freebsd-current@FreeBSD.org Subject: Re: write(2) returns error saying read only filesystem when trying to write to a partition In-Reply-To: Message from Bruce Evans of "Sat, 09 Dec 2000 03:15:07 +1100." From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Dec 2000 00:30:58 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Fri, 8 Dec 2000, Matthew Thyer wrote: > > > Mike Smith wrote: > > > > The program works on Compaq True64 UNIX v 4.0d > > > > It also works on Solaris 7 (only tested sparc). > > > > > > > > So it seems FreeBSD is broken here. > > > > > > FreeBSD just behaves differently. If you want to write to the whole > > > disk, open the whole-disk device, not the 'c' partition. > > > > Thanks Mike, /dev/da18 works fine for me although I notice that > > /dev/da18s1 does not. There seems to be some inconcistencies > > in this area. > > > > Please tell me (and for the benefit of the list) as to why > > I cant use /dev/da18s1c ? > > Because metadata (i.e,. label) write protection actually works on > /dev/da18s1c. > > It is supposed to be possible to turn off write protection using the > DIOCWLABEL ioctl, but IIRC this only works if the data written over > the label area is a valid label (if there is already a label there, > as there must be for /dev/da18s1c to exist), so labels can't be > cleared by writing zeros to them (zeros don't give a valid label). > > Labels can be cleared by zeroing them using the whole-disk device. > All subdevices of the device should be closed before starting, and none > except the whole-disk device should be opened before finishing, to > ensure that the old in-core copy of the label isn't used. > > Someone broke dd(1) to always turn off write protection of labels, to > hack around a bug in the alpha disklabel code (someone broke the label > for the whole-disk device by making it a real label to hack around a > non-understood bug that is said to break sysinstall; real labels are > write protected, so the whole-disk device can't be used to bypass the > write protection). Since overwriting labels doesn't work quite right > even when write protection is turned off, I'm not sure how the breakage > helps. O'Brien said that it was totally necessary to be able to do it. If it's the hack that the alpha users need, it's not really my place to try to analyze the how and why of alpha breakage to determine whether it's proper or not if I have no alpha systems. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Dec 9 22: 7:56 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 22:07:55 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 2840F37B400 for ; Sat, 9 Dec 2000 22:07:55 -0800 (PST) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA93252; Sun, 10 Dec 2000 01:08:04 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sun, 10 Dec 2000 01:08:04 -0500 (EST) From: "Brandon D. Valentine" To: current@FreeBSD.ORG Cc: sthaug@nethelp.no Subject: Re: Confusing error messages from shell image activation In-Reply-To: <20001209113712.C23244@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 Sat, 9 Dec 2000, David O'Brien wrote: >On Sat, Dec 09, 2000 at 08:28:07PM +0100, sthaug@nethelp.no wrote: > >> like NetBSD (and the corresponding sources under /usr/pkgsrc). > >Please stick to reasonable ideas. To move the CVS repo from ports/ to >pkgsrc/ would be totally unreasonable. I've always thought /usr/pkg/src a logical place to put it. -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 22:11:34 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 22:11:31 2000 Return-Path: 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 1488E37B400 for ; Sat, 9 Dec 2000 22:11:31 -0800 (PST) Received: (qmail 17641 invoked from network); 10 Dec 2000 06:06:17 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 10 Dec 2000 06:06:17 -0000 Received: (qmail 30842 invoked from network); 10 Dec 2000 06:11:29 -0000 Received: from unknown (HELO dsl081-020-229-sea1.dsl-isp.net) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 10 Dec 2000 06:11:29 -0000 Received: (from tomdean@localhost) by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.9.3) id eBA6BSX49312; Sat, 9 Dec 2000 22:11:28 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Sat, 9 Dec 2000 22:11:28 -0800 (PST) Message-Id: <200012100611.eBA6BSX49312@dsl081-020-229-sea1.dsl-isp.net> X-Authentication-Warning: dsl081-020-229-sea1.dsl-isp.net: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: current@FreeBSD.ORG In-reply-to: <3A330215.A981B3CA@cup.hp.com> (message from Marcel Moolenaar on Sat, 09 Dec 2000 20:09:57 -0800) Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> <3A32A8A5.65C69B94@cup.hp.com> <200012100225.eBA2PVH08442@dsl081-020-229-sea1.dsl-isp.net> <3A32EC5A.6953D817@cup.hp.com> <200012100245.eBA2js708522@dsl081-020-229-sea1.dsl-isp.net> <3A330215.A981B3CA@cup.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have no environment settings that relate to groff and only MANPATH that relates to man. There are no local modifications. etc/make.conf only has CFLAGS= -O -pipe HAVE_MOTIF= yes MOTIF_STATIC= yes USA_RESIDENT= YES WRKDIRPREFIX= /usr/obj/ports NO_MODULES= NO I have always done cvsup followed by 'make world'. # cd /usr/src/gnu/usr.bin # make clean # cd /usr/src # make -DNOCLEAN world fixed the problem. Before, I used 'make -j36 -DNOCLEAN world'. Could it be a problem with the Makefile in man? Next week, I will do a cvsup, etc. I will use -j36 and see if it changes anything. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 9 22:56:30 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 22:56:28 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 35B1037B400 for ; Sat, 9 Dec 2000 22:56:28 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 9C052B69; Sat, 9 Dec 2000 22:56:27 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id WAA11354; Sat, 9 Dec 2000 22:56:26 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A332915.E370B736@cup.hp.com> Date: Sat, 09 Dec 2000 22:56:21 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas D. Dean" Cc: current@FreeBSD.ORG Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <200012092138.eB9LcVW08042@dsl081-020-229-sea1.dsl-isp.net> <3A32A8A5.65C69B94@cup.hp.com> <200012100225.eBA2PVH08442@dsl081-020-229-sea1.dsl-isp.net> <3A32EC5A.6953D817@cup.hp.com> <200012100245.eBA2js708522@dsl081-020-229-sea1.dsl-isp.net> <3A330215.A981B3CA@cup.hp.com> <200012100611.eBA6BSX49312@dsl081-020-229-sea1.dsl-isp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas D. Dean" wrote: > > # cd /usr/src/gnu/usr.bin > # make clean > # cd /usr/src > # make -DNOCLEAN world > > fixed the problem. Before, I used 'make -j36 -DNOCLEAN world'. Could > it be a problem with the Makefile in man? -DNOCLEAN is not guaranteed to work. Especially when makefiles change. Use with care! -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message