From owner-freebsd-current Sun Oct 10 0:16:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id 7B28114CA1 for ; Sun, 10 Oct 1999 00:16:45 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 78596 invoked by uid 1016); 10 Oct 1999 07:16:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Oct 1999 07:16:44 -0000 Date: Sun, 10 Oct 1999 03:16:44 -0400 (EDT) From: Jason DiCioccio To: Doug Rabson Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old floppy, I could set the parameters for ed0 and it would find ed0.. now it doesn't find ed0 at all although it still finds 'unknown0' .. When you fixed this freezing, did this ruin some other detection or something to that effect? I told it to probe 0x240 @ IRQ 7 which is where it is.. all my bios settings etc have no changed since last time I used floppy (the one that froze but still found ed0) .. Thanks in advance, Jason DiCioccio On Sat, 9 Oct 1999, Doug Rabson wrote: > On Sat, 9 Oct 1999, Jason DiCioccio wrote: > > > > > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0 > > insists on detecting my ethernet card PnP at installation even though Id > > ont want it to.. When it does, it freezes up, and its much easier for me > > just to input the settings manually info the visual config.. I need to > > disable on install disk, or get a 4.0 floppy that doesn't freeze on > > 'unknown0', of course, not having it detected at all would be preferable > > :).. > > There was a problem with the pnp code which caused freezes like this which > I fixed. What date was the snap that you tried? > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 0:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3C9A215104 for ; Sun, 10 Oct 1999 00:50:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA13754; Sun, 10 Oct 1999 09:50:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Randy Bush , FreeBSD Current Subject: Re: breakage in libgcc? In-reply-to: Your message of "Sat, 09 Oct 1999 17:46:55 PDT." <199910100046.RAA02284@dingo.cdrom.com> Date: Sun, 10 Oct 1999 09:50:00 +0200 Message-ID: <13752.939541800@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like you havn't -current. In message <199910100046.RAA02284@dingo.cdrom.com>, Mike Smith writes: >> just cvsupped > >Your system; I just finished a world not five minutes ago. Suspect the >usual. > >> echo '#include ' >> config.h >> echo '#include "i386/xm-i386.h"' > tconfig.h >> echo '#include "i386/i386.h"' > tm.h >> echo '#include "i386/att.h"' >> tm.h >> echo '#include "i386/freebsd.h"' >> tm.h >> echo '#include "i386/perform.h"' >> tm.h >> cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c >> *** Signal 12 >> >> Stop in /usr/src/gnu/lib/libgcc. >> *** Error code 1 >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > >-- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 1:14:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id BD36F15228 for ; Sun, 10 Oct 1999 01:14:23 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id SAA02535 for ; Sun, 10 Oct 1999 18:14:12 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Sun, 10 Oct 1999 18:14:12 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: freebsd-current@FreeBSD.ORG Subject: scsi tape driver wants an update 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 a reminder I guess, # uname -v FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 # mt retension console emits (in bright white): WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 2:53:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D463615511 for ; Sun, 10 Oct 1999 02:52:49 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA70306; Sun, 10 Oct 1999 10:53:36 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 10 Oct 1999 10:53:36 +0100 (BST) From: Doug Rabson To: Jason DiCioccio Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sun, 10 Oct 1999, Jason DiCioccio wrote: > I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old > floppy, I could set the parameters for ed0 and it would find ed0.. now it > doesn't find ed0 at all although it still finds 'unknown0' .. When you > fixed this freezing, did this ruin some other detection or something to > that effect? I told it to probe 0x240 @ IRQ 7 which is where it is.. all > my bios settings etc have no changed since last time I used floppy (the > one that froze but still found ed0) .. To debug this, I need the output of dmesg and pnpinfo from a kernel which exhibits the problem. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 4:28:44 1999 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 C99B615535; Sun, 10 Oct 1999 04:28:32 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p09-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.138]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id UAA08215; Sun, 10 Oct 1999 20:28:24 +0900 (JST) Message-ID: <38007684.B28BA64D@newsguy.com> Date: Sun, 10 Oct 1999 20:20:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Poul-Henning Kamp Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: maxphys = 0?? References: <12459.939506425@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > Meanwhile the mystery has been solved. I was a miscommunication > between sos and me. He only committed one half of the fix for > this issue. > > He has now committed the rest along with the latest version of > his ata drivers (he claims :-) Things are fine here now. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 4:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 8723515125; Sun, 10 Oct 1999 04:58:55 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id NAA50542; Sun, 10 Oct 1999 13:58:53 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910101158.NAA50542@gratis.grondar.za> To: marcel@freebsd.org Cc: current@freebsd.org Subject: Signal breakage? Date: Sun, 10 Oct 1999 13:58:52 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi On line 72 of , there is a reference to 'union sigval', which is declared in , but inside #ifndef _POSIX_SOURCE. The X build heavily uses _POSIX_SOURCE, so this breaks. Should line 72 of not move a little further down into the #ifndef _POSIX_SOURCE block below it? M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 6:12:34 1999 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 906C614C37; Sun, 10 Oct 1999 06:11:58 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d209.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA05030; Sun, 10 Oct 1999 23:13:47 +1000 Date: Sun, 10 Oct 1999 23:11:29 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mark Murray Cc: marcel@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Signal breakage? In-Reply-To: <199910101158.NAA50542@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On line 72 of , there is a reference to 'union sigval', > which is declared in , but inside #ifndef _POSIX_SOURCE. > The X build heavily uses _POSIX_SOURCE, so this breaks. > > Should line 72 of not move a little further down into > the #ifndef _POSIX_SOURCE block below it? This is supposed to be handled by a _POSIX_1B_VISIBLE feature test, but the test is broken (nonexistent) in . Try changing the ifdef for sigval fom _POSIX_SOURCE to _POSIX_1B_VISIBLE. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 6:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 26AD31520E for ; Sun, 10 Oct 1999 06:59:19 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-147.skylink.it [194.185.55.147]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id PAA10663; Sun, 10 Oct 1999 15:59:41 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id JAA06329; Sun, 10 Oct 1999 09:13:49 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 10 Oct 1999 09:13:49 GMT Date: Sun, 10 Oct 1999 11:13:49 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Ollivier Robert Cc: FreeBSD Current Subject: Re: staroffice In-Reply-To: <19991009234834.A32126@keltia.freenix.fr> 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 > > o unzip setup.zip to someplace comfortable > > Don't both with that. > > use "export LD_LIBRARY_PATH=/tmp/sv001.tmp:." before running the setup binary. ^^^ That number changes, so you might have to go into /tmp and delete stale directories. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 8:29: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 21C92151F6; Sun, 10 Oct 1999 08:28:56 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11aKu1-0000av-00; Sun, 10 Oct 1999 08:28:49 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Brian F. Feldman" Cc: Mike Smith , FreeBSD Current Subject: Re: breakage in libgcc? References: <199910100046.RAA02284@dingo.cdrom.com> Message-Id: Date: Sun, 10 Oct 1999 08:28:49 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> *** Signal 12 >> Stop in /usr/src/gnu/lib/libgcc. >> *** Error code 1 > Suspect that you need a newer kernel before you can build the world. had to o make new config o make new kernel o reboot o make world o ... must have been an exciting time in current while i was on the road the last three weeks. :-) randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 9:12:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 303A414F8A for ; Sun, 10 Oct 1999 09:12:22 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 7DAC21CC6; Mon, 11 Oct 1999 00:12:21 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Randy Bush Cc: FreeBSD Current Subject: Re: breakage in libgcc? In-reply-to: Your message of "Sat, 09 Oct 1999 17:50:35 MST." Date: Mon, 11 Oct 1999 00:12:21 +0800 From: Peter Wemm Message-Id: <19991010161221.7DAC21CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > just cvsupped > > echo '#include ' >> config.h > echo '#include "i386/xm-i386.h"' > tconfig.h > echo '#include "i386/i386.h"' > tm.h > echo '#include "i386/att.h"' >> tm.h > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/ usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib /libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > > Stop in /usr/src/gnu/lib/libgcc. > *** Error code 1 You need to build a new kernel *before* you 'make world'. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 9:40:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id 1DE2F14F8A for ; Sun, 10 Oct 1999 09:40:37 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 93184 invoked by uid 1016); 10 Oct 1999 16:40:36 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Oct 1999 16:40:36 -0000 Date: Sun, 10 Oct 1999 12:40:36 -0400 (EDT) From: Jason DiCioccio To: Doug Rabson Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sorry I can't get pnpinfo, I can tell you though that dmesg does not even show ed0 being probed at all.. In other words, it does nto even say 'ed0 not found at 0x240' .. And I am not deleting the device :-).. Are there any conditions where this would happen? Thanks On Sun, 10 Oct 1999, Doug Rabson wrote: > On Sun, 10 Oct 1999, Jason DiCioccio wrote: > > > I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old > > floppy, I could set the parameters for ed0 and it would find ed0.. now it > > doesn't find ed0 at all although it still finds 'unknown0' .. When you > > fixed this freezing, did this ruin some other detection or something to > > that effect? I told it to probe 0x240 @ IRQ 7 which is where it is.. all > > my bios settings etc have no changed since last time I used floppy (the > > one that froze but still found ed0) .. > > To debug this, I need the output of dmesg and pnpinfo from a kernel which > exhibits the problem. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 9:48: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 3D7B7154E8 for ; Sun, 10 Oct 1999 09:47:43 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id MAA67098 for ; Sun, 10 Oct 1999 12:46:28 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sun, 10 Oct 1999 12:46:28 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: ATA 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 I finally got a chance to put the ata driver back in my kernel, and this is what happens: Whenever I am doing something that requires a lot of disk activity, (on the latest errors, I was recompiling the kernel with make -j8 and building gnomelibs): Oct 10 12:29:48 culverk /kernel: ata0-slave: ad_timeout: lost disk contact - res etting Oct 10 12:29:49 culverk /kernel: ata0: resetting devices .. DANGER active=3 Oct 10 12:29:49 culverk /kernel: done Oct 10 12:29:49 culverk /kernel: ad1: status=51 error=04 Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error Oct 10 12:29:51 culverk /kernel: ata0-slave: ad_timeout: lost disk contact - res etting Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. done Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04 Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error Oct 10 12:29:54 culverk /kernel: ata0-slave: ad_timeout: lost disk contact - res etting Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. DANGER active=3 Oct 10 12:29:54 culverk /kernel: done Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04 Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error Oct 10 12:29:57 culverk /kernel: ata0-slave: ad_timeout: lost disk contact - res etting Oct 10 12:29:57 culverk /kernel: ata0: resetting devices .. done Oct 10 12:32:03 culverk /kernel: sigreturn: eflags = 0x0 any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 9:58:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id CE81715216 for ; Sun, 10 Oct 1999 09:58:13 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA89111; Sun, 10 Oct 1999 18:00:08 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 10 Oct 1999 18:00:08 +0100 (BST) From: Doug Rabson To: Jason DiCioccio Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sun, 10 Oct 1999, Jason DiCioccio wrote: > Sorry I can't get pnpinfo, I can tell you though that dmesg does not even > show ed0 being probed at all.. In other words, it does nto even say 'ed0 > not found at 0x240' .. And I am not deleting the device :-).. Are there > any conditions where this would happen? Due to the nature of the pnp code, it might be probed as ed1 instead of ed0. If at all possible, could you put the card into a working FreeBSD box so that I can see the pnpinfo. If we are missing a pnp ID for the card, I need that information to fix it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10: 3:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D873414DDA for ; Sun, 10 Oct 1999 10:03:20 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA34736; Sun, 10 Oct 1999 19:03:11 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910101703.TAA34736@freebsd.dk> Subject: Re: ATA driver In-Reply-To: from Kenneth Culver at "Oct 10, 1999 12:46:28 pm" To: culverk@culverk.student.umd.edu (Kenneth Culver) Date: Sun, 10 Oct 1999 19:03:11 +0200 (CEST) Cc: freebsd-current@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 Kenneth Culver wrote: Is this with the latest that I committed yesterday ?? -Søren > I finally got a chance to put the ata driver back in my kernel, and this > is what happens: Whenever I am doing something that requires a lot of disk > activity, (on the latest errors, I was recompiling the kernel with make > -j8 and building gnomelibs): > > Oct 10 12:29:48 culverk /kernel: ata0-slave: ad_timeout: lost disk contact > - res > etting > Oct 10 12:29:49 culverk /kernel: ata0: resetting devices .. DANGER > active=3 > Oct 10 12:29:49 culverk /kernel: done > Oct 10 12:29:49 culverk /kernel: ad1: status=51 error=04 > Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error > Oct 10 12:29:51 culverk /kernel: ata0-slave: ad_timeout: lost disk contact > - res > etting > Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. done > Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04 > Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error > Oct 10 12:29:54 culverk /kernel: ata0-slave: ad_timeout: lost disk contact > - res > etting > Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. DANGER > active=3 > Oct 10 12:29:54 culverk /kernel: done > Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04 > Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error > Oct 10 12:29:57 culverk /kernel: ata0-slave: ad_timeout: lost disk contact > - res > etting > Oct 10 12:29:57 culverk /kernel: ata0: resetting devices .. done > Oct 10 12:32:03 culverk /kernel: sigreturn: eflags = 0x0 > > any ideas? > > > > 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 Sun Oct 10 10: 6:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id E15E514EFD for ; Sun, 10 Oct 1999 10:06:40 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 93571 invoked by uid 1016); 10 Oct 1999 17:06:39 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Oct 1999 17:06:39 -0000 Date: Sun, 10 Oct 1999 13:06:39 -0400 (EDT) From: Jason DiCioccio To: Doug Rabson Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while it should be on irq 7 On Sun, 10 Oct 1999, Doug Rabson wrote: > On Sun, 10 Oct 1999, Jason DiCioccio wrote: > > > Sorry I can't get pnpinfo, I can tell you though that dmesg does not even > > show ed0 being probed at all.. In other words, it does nto even say 'ed0 > > not found at 0x240' .. And I am not deleting the device :-).. Are there > > any conditions where this would happen? > > Due to the nature of the pnp code, it might be probed as ed1 instead of > ed0. If at all possible, could you put the card into a working FreeBSD box > so that I can see the pnpinfo. If we are missing a pnp ID for the card, > I need that information to fix it. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10:17: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 2BA8114DDA for ; Sun, 10 Oct 1999 10:16:56 -0700 (PDT) (envelope-from patrick@137.org) Received: from friley-161-13.res.iastate.edu (friley-161-13.res.iastate.edu [129.186.161.13]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id CB278119 for ; Sun, 10 Oct 1999 12:16:55 -0500 (CDT) Received: from friley-161-13.res.iastate.edu (localhost [127.0.0.1]) by friley-161-13.res.iastate.edu (Postfix) with ESMTP id 1FDC15D98 for ; Sun, 10 Oct 1999 12:16:55 -0500 (CDT) To: freebsd-current@freebsd.org Subject: X-related panic Date: Sun, 10 Oct 1999 12:16:54 -0500 From: Patrick Hartling Message-Id: <19991010171655.1FDC15D98@friley-161-13.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For quite some time, I've been having panics while running X and never saw the actual message. This time, I happened to be in console mode when the crash happened. Here is the panic message: kernel: type 12 trap, code=0 Stopped at pmap_remove_pages+0xd0: decl 0(%ecx) The stack trace I got was: pmap_remve_pages(c7bf1f28,0,bfbfe000,c7c42e6c,c7371034) at pmap_remove_pages+0xd0 exec_new_vmspace(c7c42e6c,c7bd7700,3,c02388fc,4e070840) at exec_elf_imgact+0x109 execve(c7bd7700,c7c42f80,80f740c,ffffffff,80f74c0) at execve+0x1fe syscall(2f,2f,2f,80f74c0,ffffffff) at syscall+0x199 Xint0x80_syscall() at Xint0x80_syscall()+0x31 Is this helpful? -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10:21: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 4989F154AA for ; Sun, 10 Oct 1999 10:20:52 -0700 (PDT) (envelope-from patrick@137.org) Received: from friley-161-13.res.iastate.edu (friley-161-13.res.iastate.edu [129.186.161.13]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id C89EE119 for ; Sun, 10 Oct 1999 12:20:51 -0500 (CDT) Received: from friley-161-13.res.iastate.edu (localhost [127.0.0.1]) by friley-161-13.res.iastate.edu (Postfix) with ESMTP id 13BF05D97 for ; Sun, 10 Oct 1999 12:20:51 -0500 (CDT) To: freebsd-current@freebsd.org Subject: Kerberized telnet not installed Date: Sun, 10 Oct 1999 12:20:50 -0500 From: Patrick Hartling Message-Id: <19991010172051.13BF05D97@friley-161-13.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built and installed sources cvsup'd at 17:45 CDT October 9 with ${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed. I looked over the recent changes to add SRA to telnet, but I am not familiar enough with the order in which things are built and installed to figure out what happened. I did notice that secure/usr.bin/telnet/Makefile was brought back to life after being dead for about 3 years, but this was the only change that really jumped out at me as being significant. Is there something new I need do to get a Kerberized telnet? Thanks. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10:35:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3702415566 for ; Sun, 10 Oct 1999 10:35:10 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA34806; Sun, 10 Oct 1999 19:35:00 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910101735.TAA34806@freebsd.dk> Subject: Re: ATA driver In-Reply-To: from Kenneth Culver at "Oct 10, 1999 12:46:28 pm" To: culverk@culverk.student.umd.edu (Kenneth Culver) Date: Sun, 10 Oct 1999 19:35:00 +0200 (CEST) Cc: freebsd-current@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 Kenneth Culver wrote: > Oct 10 12:29:48 culverk /kernel: ata0-slave: ad_timeout: lost disk contact > - res > etting > Oct 10 12:29:49 culverk /kernel: ata0: resetting devices .. DANGER > active=3 > Oct 10 12:29:49 culverk /kernel: done > Oct 10 12:29:49 culverk /kernel: ad1: status=51 error=04 > Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error OK, it suggests that you have bad sectors on your drive, could you mail me your dmesg from a boot -v ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 5B319155A3 for ; Sun, 10 Oct 1999 10:35:56 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id NAA03887; Sun, 10 Oct 1999 13:34:34 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sun, 10 Oct 1999 13:34:34 -0400 (EDT) From: Kenneth Culver To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver In-Reply-To: <199910101735.TAA34806@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sure, as soon as i get a chance, I'll do that for ya. Ken On Sun, 10 Oct 1999, Soren Schmidt wrote: > It seems Kenneth Culver wrote: > > Oct 10 12:29:48 culverk /kernel: ata0-slave: ad_timeout: lost disk cont= act > > - res > > etting > > Oct 10 12:29:49 culverk /kernel: ata0: resetting devices .. DANGER > > active=3D3 > > Oct 10 12:29:49 culverk /kernel: done > > Oct 10 12:29:49 culverk /kernel: ad1: status=3D51 error=3D04 > > Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error >=20 > OK, it suggests that you have bad sectors on your drive, could you mail > me your dmesg from a boot -v ? >=20 > -S=F8ren >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10:50:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 28BDB15567 for ; Sun, 10 Oct 1999 10:50:18 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id NAA00304; Sun, 10 Oct 1999 13:48:57 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sun, 10 Oct 1999 13:48:57 -0400 (EDT) From: Kenneth Culver To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver 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 It doesn't seem to have bad sectors... found-> vendor=0x109e, dev=0x036e, revid=0x02 class=04-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base ea002000, size 12 found-> vendor=0x109e, dev=0x0878, revid=0x02 class=04-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base ea000000, size 12 found-> vendor=0x1011, dev=0x0009, revid=0x22 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000e400, size 7 map[1]: type 1, range 32, base ea001000, size 7 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x8086, dev=0x7800, revid=0x21 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[0]: type 3, range 32, base e6000000, size 24 map[1]: type 1, range 32, base e5000000, size 19 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=50 status1=10 ata1: mask=03 status0=50 status1=10 ata1: devices = 0x9 ata1 at 0x0170 irq 15 on ata-pci0 chip1: irq 11 at device 7.2 on pci0 intpm0: at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 pci0: unknown card (vendor=0x121a, dev=0x0002) at 13.0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 15.0 bktr0: irq 9 at device 17.0 on pci0 using shared irq9. brooktree0: PCI bus latency is 64. bktr0: buffer size 3555328, addr 0x5000000 bktr: GPIO is 0x00fffffb subsytem 0x0070 0x13eb bktr0: Hauppauge Model 61291 D110 Hauppauge WinCast/TV, Philips NTSC tuner, remote control. pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 9 de0: irq 10 at device 19.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 bpf: de0 attached fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:c8, syncbits:08 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k vga0: vga: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 28 0b 10 ff ff 09 0f 00 0e eb 2d 27 28 90 2b 91 bf 1f c0 9c 0e 8f 28 96 b9 01 01 01 01 00 28 0e 10 ff ff 09 0f 00 0e eb 31 27 28 92 2c 90 05 3e c0 e9 0c df 28 e9 fc 02 01 01 01 00 32 11 10 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: EPP SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 vpo0: EPP 1.9 mode sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: isa_compat: didn't get drq for sbxvi sbxvi0 at port 0xffffffff drq 1 on isa0 isa_compat: didn't get ports for sbxvi isa_compat: didn't get drq for sbxvi snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] sbmidi0 at port 0x330 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] BIOS Geometries: 0:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors 1:03ff0e3f 0..1023=1024 cylinders, 0..14=15 heads, 1..63=63 sectors 2:03ff0e3f 0..1023=1024 cylinders, 0..14=15 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached bpf: ppp0 attached new masks: bio 4008c040, tty 4003109a, net 4007169a ata0: master: success setting up UDMA2 mode on PIIX4 chip ad0: piomode=4 dmamode=2 udmamode=2 ad0: ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ata0: slave: success setting up UDMA2 mode on PIIX4 chip ad1: piomode=4 dmamode=2 udmamode=2 ad1: ATA-3 disk at ata0 as slave ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 ata1: master: success setting up UDMA2 mode on PIIX4 chip ad2: piomode=4 dmamode=2 udmamode=2 ad2: ATA-3 disk at ata1 as master ad2: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad2 Creating DISK wd2 ata1-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata1 as slave , 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data/audio disc loaded, unlocked (probe6:vpo0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:vpo0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:vpo0:0:6:0): Invalid field in CDB Creating DISK da0 (da0:vpo0:0:6:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:vpo0:0:6:0): NOT READY asc:3a,0 (da0:vpo0:0:6:0): Medium not present da0 at vpo0 bus 0 target 6 lun 0 da0: Removable Direct Access SCSI-2 device da0: Attempt to query device size failed: NOT READY, Medium not present Considering FFS root f/s. changing root device to wd1s1a wd1s1: type 0xa5, start 63, end = 8438849, size 8438787 : OK start_init: trying /sbin/init de0: enabling 10baseT port wd2s1: type 0xa5, start 63, end = 12672449, size 12672387 : OK wd0s1: type 0xc, start 63, end = 16514063, size 16514001 : OK Linux-ELF exec handler installed splash: image decoder found: green_saver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 10:53:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 555FA1561C for ; Sun, 10 Oct 1999 10:51:00 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA89453; Sun, 10 Oct 1999 18:52:37 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 10 Oct 1999 18:52:36 +0100 (BST) From: Doug Rabson To: Jason DiCioccio Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sun, 10 Oct 1999, Jason DiCioccio wrote: > Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while > it should be on irq 7 Actually, we can put the card on any irq which it supports as long as there isn't a conflict. Unless you have a sio1 in that box (which normally uses irq 3), it is perfectly ok. Your card is an SMC EtherEZ (8416). I think that needs some special extra tricks to get it supported. Matt Dodd was working on this recently but I don't know if he has it working yet. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 11:17:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0988914FFF for ; Sun, 10 Oct 1999 11:17:15 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA34924; Sun, 10 Oct 1999 20:17:09 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910101817.UAA34924@freebsd.dk> Subject: Re: ATA driver In-Reply-To: from Kenneth Culver at "Oct 10, 1999 01:48:57 pm" To: culverk@culverk.student.umd.edu (Kenneth Culver) Date: Sun, 10 Oct 1999 20:17:09 +0200 (CEST) Cc: freebsd-current@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 Kenneth Culver wrote: > ata0: slave: success setting up UDMA2 mode on PIIX4 chip > ad1: piomode=4 dmamode=2 udmamode=2 > ad1: ATA-3 disk at ata0 as slave > ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 0 depth queue, UDMA33 Uh oh, I had one of those once, no end of trouble, have you ever had it working in any DMA mode reliably (mine wouldn't).. One possible solution is to tell the bios it is PIO3 only mode, the ATA driver will then run DMA on it but with relaxed timing... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 11:27: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id 5DAFC14DB9 for ; Sun, 10 Oct 1999 11:26:40 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf.eng.demon.net (fanf.eng.demon.net [195.11.55.89]) by internal.mail.demon.net with ESMTP id TAA28965; Sun, 10 Oct 1999 19:26:37 +0100 (BST) Received: from fanf by fanf.eng.demon.net with local (Exim 3.03 #2) id 11aNfb-000JMH-00 for current@freebsd.org; Sun, 10 Oct 1999 19:26:07 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: {a}sync updates (was Re: make install trick) In-Reply-To: <199910092134.BAA04136@tejblum.pp.ru> References: <000d01bf11b1$5bfca1f0$021d85d1@youwant.to> Message-Id: Date: Sun, 10 Oct 1999 19:26:07 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed similarly odd behaviour from softupdates during heavy IO load, where something is creating lots of little files or directories and not much else is happening. Using `vmstat 1` I can see that softupdates isn't very good at evening out the IO rate over time: there's a roughly sinusoidal back-and-forth between frantic disk thrashing (lots of TPS) and lots of syscall activity. Visible progress is correspondingly uneven. For example, the `vmstat 1` output while the script for i in `jot 256` do for j in `jot 256` do mkdir -p $i/$j done done is running is appended below. Behaviour is much smoother during an `rm -r *` of the resulting directory tree. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Apache Software Foundation Member procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 fd0 pa0 in sy cs us sy id 2 1 0 4183836 11172 3389 0 0 0 3188 0 273 0 0 512 6015 1210 71 29 0 1 1 0 4183836 11172 447 0 0 0 444 0 427 0 0 667 3198 1128 93 7 0 1 1 0 4183836 11172 411 0 0 0 408 0 459 0 0 699 3424 1039 89 11 0 1 1 0 4183836 11172 428 0 0 0 425 0 469 0 0 713 3430 1039 96 4 0 2 0 0 4183832 11112 3544 0 0 0 3285 0 296 0 0 535 6820 990 67 32 1 3 0 0 4184036 11084 10155 0 0 0 9427 0 60 0 0 298 14837 1026 45 55 0 2 0 0 4184044 11092 7856 0 0 0 7292 0 0 0 0 242 12077 1013 52 48 0 3 0 0 4183588 11216 13700 0 0 0 12718 0 0 0 0 239 18826 960 26 74 0 3 0 0 4184056 11116 12824 0 0 0 11880 0 5 0 0 245 17635 977 35 65 0 2 0 0 4183836 11164 8604 0 0 0 8011 0 1 0 0 242 12450 1008 55 45 0 2 1 0 4183900 11168 5770 0 0 0 5386 0 189 0 0 428 9073 1241 57 43 0 1 1 0 4183836 11168 497 0 0 0 489 0 472 0 0 712 3006 1107 91 9 0 1 2 0 4183496 11136 502 0 0 0 483 0 577 0 0 829 3449 1059 88 12 0 1 1 0 4183496 11156 1444 0 0 0 1365 0 538 0 0 779 4620 1049 86 14 0 3 0 0 4183248 11120 11937 0 0 0 11068 0 107 0 0 344 16580 892 22 78 0 2 0 0 4183308 11132 15356 0 0 0 14213 0 1 0 0 241 20742 979 18 82 0 3 0 0 4183704 11048 12665 0 0 0 11713 0 0 0 0 239 17461 990 28 72 0 2 0 0 4183492 11092 10878 0 0 0 10126 0 21 0 0 259 15238 986 45 55 0 2 0 0 4183496 11112 12151 0 0 0 11276 0 50 0 0 289 16767 982 28 72 0 2 1 0 4183496 11144 422 0 0 0 425 0 510 0 0 756 2444 1217 84 16 0 1 1 0 4183496 11100 475 0 0 0 462 0 575 0 0 820 3299 1131 87 13 0 1 1 0 4183496 11092 1024 0 0 0 976 0 550 0 0 792 4130 1049 88 12 0 3 0 0 4183648 11104 7254 0 0 0 6747 0 291 0 0 530 11196 949 53 47 0 2 1 0 4183768 11140 12570 0 0 0 11678 0 5 0 0 249 17381 1002 33 67 0 2 0 0 4183832 11028 13877 0 0 0 12846 0 7 0 0 249 18952 986 25 75 0 2 0 0 4183648 11028 12263 0 0 0 11400 0 16 0 0 259 16964 1015 38 62 0 3 0 0 4183768 11036 11108 0 0 0 10353 0 5 0 0 244 15567 1017 32 68 0 3 0 0 4183836 10952 5932 0 0 0 5539 0 190 0 0 429 9087 1153 55 45 0 2 1 0 4183836 10900 475 0 0 0 459 0 542 0 0 782 2865 1257 91 9 0 1 2 0 4183768 10936 766 0 0 0 749 0 562 0 0 809 3732 1219 87 13 0 1 1 0 4184312 10900 853 0 0 0 803 0 557 0 0 799 4189 1142 90 10 0 2 0 0 4184124 10812 11847 0 0 0 10971 0 101 0 0 340 16642 969 29 71 0 2 0 0 4184520 10720 8599 0 0 0 7976 0 6 0 0 244 13098 1065 48 52 0 2 0 0 4184312 10732 7968 0 0 0 7410 0 5 0 0 242 12228 1034 50 49 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 11:59:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E2DCB14A07 for ; Sun, 10 Oct 1999 11:58:45 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 534F21CCD; Mon, 11 Oct 1999 02:58:42 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: culverk@culverk.student.umd.edu (Kenneth Culver), freebsd-current@FreeBSD.ORG Subject: Re: ATA driver In-reply-to: Your message of "Sun, 10 Oct 1999 20:17:09 +0200." <199910101817.UAA34924@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Mon, 11 Oct 1999 02:58:42 +0800 From: Peter Wemm Message-Id: <19991010185842.534F21CCD@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Kenneth Culver wrote: > > ata0: slave: success setting up UDMA2 mode on PIIX4 chip > > ad1: piomode=4 dmamode=2 udmamode=2 > > ad1: ATA-3 disk at ata0 as slave > > ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S > > ad1: 16 secs/int, 0 depth queue, UDMA33 > > Uh oh, I had one of those once, no end of trouble, have you ever had > it working in any DMA mode reliably (mine wouldn't).. > One possible solution is to tell the bios it is PIO3 only mode, the > ATA driver will then run DMA on it but with relaxed timing... > Heh, Just looking at the linux ide driver: const char *bad_ata66_4[] = { "WDC AC310200R", NULL }; const char *bad_ata66_3[] = { "WDC AC310200R", NULL }; const char *bad_ata33[] = { "Maxtor 92720U8", "Maxtor 92040U6", "Maxtor 91360U4", "Maxtor 91020U3", "Maxtor 90845U3", "Maxtor 90650U2", "Maxtor 91360D8", "Maxtor 91190D7", "Maxtor 91020D6", "Maxtor 90845D5", "Maxtor 90680D4", "Maxtor 90510D3", "Maxtor 90340D2", "Maxtor 91152D8", "Maxtor 91008D7", "Maxtor 90845D6", "Maxtor 90840D6", "Maxtor 90720D5", "Maxtor 90648D5", "Maxtor 90576D4", "Maxtor 90510D4", "Maxtor 90432D3", "Maxtor 90288D2", "Maxtor 90256D2", "Maxtor 91000D8", "Maxtor 90910D8", "Maxtor 90875D7", "Maxtor 90840D7", "Maxtor 90750D6", "Maxtor 90625D5", "Maxtor 90500D4", "Maxtor 91728D8", "Maxtor 91512D7", "Maxtor 91303D6", "Maxtor 91080D5", "Maxtor 90845D4", "Maxtor 90680D4", "Maxtor 90648D3", "Maxtor 90432D2", NULL }; Looks like the Maxtor's have a bit of a track record... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 12:22: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id E194615915; Sun, 10 Oct 1999 12:20:44 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id VAA13715; Sun, 10 Oct 1999 21:21:27 +0200 (CEST) To: Poul-Henning Kamp Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Heads up! References: <5480.939038143@critter.freebsd.dk> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 10 Oct 1999 21:21:24 +0200 In-Reply-To: Poul-Henning Kamp's message of "Mon, 04 Oct 1999 13:55:43 +0200" Message-ID: <5loge7uimj.fsf@assaris.sics.se> Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > We have now come so far that we can start to kill cdevsw_add() > calls and rely on make_dev() for most of the device drivers. So how is this supposed to work for device kld's? Currently, cdevsw_add() gets called from the glue generated by DEV_MODULE. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 12:23:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 46B1E15940 for ; Sun, 10 Oct 1999 12:22:35 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id PAA22108; Sun, 10 Oct 1999 15:22:25 -0400 (EDT) Date: Sun, 10 Oct 1999 15:22:24 -0400 (EDT) From: "Matthew N. Dodd" To: Doug Rabson Cc: Jason DiCioccio , current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sun, 10 Oct 1999, Doug Rabson wrote: > Your card is an SMC EtherEZ (8416). I think that needs some special > extra tricks to get it supported. Matt Dodd was > working on this recently but I don't know if he has it working yet. I've got uncommitted patches that fix this I believe. I need to go back and test them before I commit but they should work. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 12:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 4B59B151BA for ; Sun, 10 Oct 1999 12:29:27 -0700 (PDT) (envelope-from patrick@137.org) Received: from friley-161-13.res.iastate.edu (friley-161-13.res.iastate.edu [129.186.161.13]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id A6626104 for ; Sun, 10 Oct 1999 14:29:26 -0500 (CDT) Received: from friley-161-13.res.iastate.edu (localhost [127.0.0.1]) by friley-161-13.res.iastate.edu (Postfix) with ESMTP id B9CF05D71 for ; Sun, 10 Oct 1999 14:29:25 -0500 (CDT) Cc: freebsd-current@freebsd.org Subject: Re: X-related panic In-reply-to: Message from Patrick Hartling of "Sun, 10 Oct 1999 12:16:54 CDT." <19991010171655.1FDC15D98@friley-161-13.res.iastate.edu> Date: Sun, 10 Oct 1999 14:29:25 -0500 From: Patrick Hartling Message-Id: <19991010192925.B9CF05D71@friley-161-13.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Hartling wrote: } For quite some time, I've been having panics while running X and never saw } the actual message. This time, I happened to be in console mode when the } crash happened. I meant to include that I'm using XFree86 3.3.5 built from the ports collection with a kernel and userland built from sources cvsup'd at 17:45 CDT October 9. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 12:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id AD65114FDC; Sun, 10 Oct 1999 12:39:50 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA16203; Sun, 10 Oct 1999 21:32:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Assar Westerlund Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Heads up! In-reply-to: Your message of "10 Oct 1999 21:21:24 +0200." <5loge7uimj.fsf@assaris.sics.se> Date: Sun, 10 Oct 1999 21:32:42 +0200 Message-ID: <16201.939583962@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5loge7uimj.fsf@assaris.sics.se>, Assar Westerlund writes: >Poul-Henning Kamp writes: >> We have now come so far that we can start to kill cdevsw_add() >> calls and rely on make_dev() for most of the device drivers. > >So how is this supposed to work for device kld's? Currently, >cdevsw_add() gets called from the glue generated by DEV_MODULE. The same as for any other driver, once you find your hardware you call make_dev() for it. Use the variant of MODULE macro which doesn't take a cdevsw agument. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 12:44:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 499A214BDB; Sun, 10 Oct 1999 12:44:49 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA16203; Sun, 10 Oct 1999 21:32:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Assar Westerlund Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Heads up! In-reply-to: Your message of "10 Oct 1999 21:21:24 +0200." <5loge7uimj.fsf@assaris.sics.se> Date: Sun, 10 Oct 1999 21:32:42 +0200 Message-ID: <16201.939583962@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5loge7uimj.fsf@assaris.sics.se>, Assar Westerlund writes: >Poul-Henning Kamp writes: >> We have now come so far that we can start to kill cdevsw_add() >> calls and rely on make_dev() for most of the device drivers. > >So how is this supposed to work for device kld's? Currently, >cdevsw_add() gets called from the glue generated by DEV_MODULE. The same as for any other driver, once you find your hardware you call make_dev() for it. Use the variant of MODULE macro which doesn't take a cdevsw agument. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 12:54:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 65F3514D58 for ; Sun, 10 Oct 1999 12:54:42 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id PAA22716; Sun, 10 Oct 1999 15:54:34 -0400 (EDT) Date: Sun, 10 Oct 1999 15:54:33 -0400 (EDT) From: "Matthew N. Dodd" To: Doug Rabson Cc: Jason DiCioccio , current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sun, 10 Oct 1999, Matthew N. Dodd wrote: > On Sun, 10 Oct 1999, Doug Rabson wrote: > > Your card is an SMC EtherEZ (8416). I think that needs some special > > extra tricks to get it supported. Matt Dodd was > > working on this recently but I don't know if he has it working yet. > > I've got uncommitted patches that fix this I believe. I need to go back > and test them before I commit but they should work. Ok, I've tested my patches and remembered why I didn't ever do anything with them. *** ISA_GET_RESOURCE(,,SYS_RES_MEMORY,...) failed (2) unknown0: at port 0x240-0x25f irq 9 on isa0 ed_probe_WD80x3() doesn't understand boards that have no shared memory. While these cards work just fine in softset mode, turning on their PnP features seems to disable the use of shared memory. mihoshi# pnpinfo Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID SMC8416 (0x1684a34d), Serial Number 0xbba8d5c1 PnP Version 1.0, Vendor Version 16 Device Description: SMC EtherEZ (8416) Logical Device ID: SMC8416 0x1684a34d #0 Device supports I/O Range Check IRQ: 3 5 7 9 10 11 IRQ: High true edge sensitive I/O Range 0x240 .. 0x3e0, alignment 0x20, len 0x20 [not 16-bit addr] End Tag Successfully got 5 resources, 1 logical fdevs -- card select # 0x0001 CSN SMC8416 (0x1684a34d), Serial Number 0xbba8d5c1 Logical device #0 IO: 0x0240 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 9 0 DMA 0 0 IO range check 0x00 activate 0x01 This output appears to agree with what Win95 finds. I'm investigating the possibility of making ed_probe_WD80x3() a bit more flexible. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:16:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.unacom.com (www.lockes.net [206.113.48.50]) by hub.freebsd.org (Postfix) with SMTP id 8601A15620 for ; Sun, 10 Oct 1999 13:15:23 -0700 (PDT) (envelope-from geniusj@phoenix.unacom.com) Received: (qmail 96104 invoked by uid 1016); 10 Oct 1999 20:15:20 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Oct 1999 20:15:20 -0000 Date: Sun, 10 Oct 1999 16:15:20 -0400 (EDT) From: Jason DiCioccio To: Doug Rabson Cc: current@freebsd.org Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 It worked when it was probed non-pnp :-).. As long as I set the params.. DId you get my email with pnpinfo and dmesg? On Sun, 10 Oct 1999, Doug Rabson wrote: > On Sun, 10 Oct 1999, Jason DiCioccio wrote: > > > Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while > > it should be on irq 7 > > Actually, we can put the card on any irq which it supports as long as > there isn't a conflict. Unless you have a sio1 in that box (which normally > uses irq 3), it is perfectly ok. > > Your card is an SMC EtherEZ (8416). I think that needs some special extra > tricks to get it supported. Matt Dodd was working on > this recently but I don't know if he has it working yet. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:21:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 92E96155F6 for ; Sun, 10 Oct 1999 13:20:50 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA00662; Sun, 10 Oct 1999 16:20:49 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA28261; Sun, 10 Oct 1999 16:20:18 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 10 Oct 1999 16:20:18 -0400 (EDT) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: installworld broken from R/O /usr/obj In-Reply-To: References: <14330.45971.639580.378954@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14336.62235.916517.53187@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > W`hile installworld is being discussed, I wanted to get this out there: > > > > Since rev 1.13 of usr.bin/make/arch.c, I've been seing a problem with > > ELF archive libraries being rebuilt unnecessarily. I believe that > > this problem can be traced to the RANLIBMAG string being set to "/". > > There's a PR about this now. The smaller fix in the PR seems to work. Ah yes, in bin/14167. The fix is much tighter & appears to work. ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:30:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 26A7714F32; Sun, 10 Oct 1999 13:30:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA73061; Sun, 10 Oct 1999 13:26:57 -0700 (PDT) Date: Sun, 10 Oct 1999 13:26:56 -0700 (PDT) From: Julian Elischer To: Bruce Evans Cc: freebsd-arch@freebsd.org, mckusick@mckusick.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: The eventual fate of BLOCK devices. 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 Can't believe this email only produced TWO responses! I would have thought that this wouldhav brought out the chainsaws! Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't work? (the only responders got it via 'core') julian On Sat, 9 Oct 1999, Bruce Evans wrote: > > PHK has been moving steadily in this direction to remove as many > > dependencies within the kernel on block devices as possible. > > The question is, When did the decision to do so become official? > > Never. > > > I don't believe it has been a stated official decision yet and so in order > > to put some clarity into the air over this I'd like to launch a PURELY > > TECHNICAL discussion on the topic. > > > > Here are some starters. > > > > 1/ block device writes have to be synchrnous or the user doesn't get > > write errors. > > Block devices should be implmented properly or the user doesn't get write > errors. > > A proper implementation is quite close. Write errors should be reported > on last-close and on fsync(). They already are as far as I can see, modulo > the bugs that (in -current) VOP_FSYNC() = ffs_fsync() sometimes hangs > instead of returning a write error and vinvalbuf() sometimes panics instead > of returning a write error. The bugs are different and worse in RELENG_3. > The bugs are different and more benign in RELENG_2_2 (write errors are > ignored). Note that the bugs have very little to do with specfs. All > specfs can reasonably do is kill the endless retries at a suitable time, > probably after calling vinvalbuf() in last-close. > > > 1A/ if they are not synchronous, errors need to be coped with in some > > other manner. > > Normal error handling suffices, modulo bugs. > > > 2/ People with old UNIX experience expect to be able to do unalligned > > transfers on block devices. > > 3/ DEVFS can cope just fine with block and char devices > > (I include this because DEVFS has been used as an argument for > > removing them) > > Correct. > > > 4/ Most of the block buffering code in the kernel will remain due to > > the VM and VFS systems. > > Well, if the Nth rewrite of vm wants to drop support for buffers in vfs, > then use of buffers for block devices shouldn't stop it. > > > 5/ New users don't tend to understand the rather strange distinctions > > between BLK and CHR devices. Some people consider having both POLA and > > This is an argument for removing character (disk) devices, since most > new users will be from Linux where block (disk) devices were the only > ones available until recently. Block devices have always worked better > in Linux. E.g., media change is detected for floppies, and buffers > remain valid across last-close, until media change. The latter behaviour > can be not what is wanted (extra ioctls are needed to discard the buffers), > but it is often useful. > > > others consider having only one POLA. Linux had til just recently, > > only BLK disk devices. They just aded CHR disk devices but I don't > > know if they created a whole second calss of device to do so. (I doubt it) > > 6/ It should be possible to make an overlay device (similar to the way > > ccd works), that supplies buffered characteristics to a disk. This may > > be a different minor number or a differnt major number.. but be a CHR > > type device. > > This would involve needless duplicatication of half of the buffer cache > implementation (maybe the simple half) unless the buffer cache goes away. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:50:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C26BE15333 for ; Sun, 10 Oct 1999 13:50:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA73421; Sun, 10 Oct 1999 13:45:04 -0700 (PDT) Date: Sun, 10 Oct 1999 13:45:04 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: installworld broken from R/O /usr/obj In-Reply-To: <14336.62235.916517.53187@grasshopper.cs.duke.edu> 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 that fix was applied by me about 5 minutes ago.. On Sun, 10 Oct 1999, Andrew Gallatin wrote: > > Bruce Evans writes: > > > W`hile installworld is being discussed, I wanted to get this out there: > > > > > > Since rev 1.13 of usr.bin/make/arch.c, I've been seing a problem with > > > ELF archive libraries being rebuilt unnecessarily. I believe that > > > this problem can be traced to the RANLIBMAG string being set to "/". > > > > There's a PR about this now. The smaller fix in the PR seems to work. > > Ah yes, in bin/14167. The fix is much tighter & appears to work. > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:52:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 89E8B15634 for ; Sun, 10 Oct 1999 13:52:18 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA01022; Sun, 10 Oct 1999 16:52:17 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA28327; Sun, 10 Oct 1999 16:51:46 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 10 Oct 1999 16:51:46 -0400 (EDT) To: Julian Elischer Cc: current@freebsd.org Subject: Re: installworld broken from R/O /usr/obj In-Reply-To: References: <14336.62235.916517.53187@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14336.64591.928985.130530@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > that fix was applied by me about 5 minutes ago.. > Thank you! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:53:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 94F7114D4F for ; Sun, 10 Oct 1999 13:52:30 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA01030; Sun, 10 Oct 1999 16:52:30 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA28327; Sun, 10 Oct 1999 16:51:46 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 10 Oct 1999 16:51:46 -0400 (EDT) To: Julian Elischer Cc: current@freebsd.org Subject: Re: installworld broken from R/O /usr/obj In-Reply-To: References: <14336.62235.916517.53187@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14336.64591.928985.130530@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > that fix was applied by me about 5 minutes ago.. > Thank you! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:55:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id CCA4E14D4F for ; Sun, 10 Oct 1999 13:55:10 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA24189 for current@freebsd.org; Sun, 10 Oct 1999 16:59:36 -0400 From: Bill Paul Message-Id: <199910102059.QAA24189@skynet.ctr.columbia.edu> Subject: Still waiting for xl driver reports To: current@freebsd.org Date: Sun, 10 Oct 1999 16:59:34 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3026 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while back I posted a message here saying that I'd changed the xl driver a bit to hopefully improve performance for 3c90xB and later adapters (i.e. the "cyclone," "hurricane" and "tornado" chipsets). I asked for people to report if the changes helped, hurt, made no difference or were totally broken. So far not one person has said so much as a word to me on this subject. I need feedback from people so that I know it's safe to merge this stuff into -stable, so let's hear it already. It's been several weeks since I made the changes. Surely there are people running -current with 3Com 3c90xB cards. To reiterate, this only concerns people with the following adapters: - 3c905B-TX 10/100 - 3c905B-FX/SC fiber optic - 3c905B-COMBO 10/100 plus BNC and AUI - 3c905C-TX 10/100 - 3c980-TX server adapter - 3c980B-TX server adapter - 3c980C-TX server adapter - 3cSOHO100-TX 10/100 To a lesser extent it also concerns people with these adapters (these are 10Mbps only so the change isn't likely to be as noticable): - 3c900B-TPO twisted pair only - 3c900B-TPC twisted paid and coax (BNC) - 3c900B-COMBO twisted pair, AUI and BNC - 3c900B-FL fiber optic Ideally, the changes should provide slightly faster performance with less CPU usage. Performance/CPU overhead comparisons with other cards (in the same machine!) would he helpful as well as comparisons with the same 3Com card using the older driver revision. Things that would not be helpful include: - Asking about an unrelated problem from 3.2-RELEASE, 3.3-RELEASE or 3.3-STABLE. - Telling me that your card isn't detected properly and not realizing that you have "plug and play OS" set to "yes" in your BIOS config. - Asking about a completely different card. From a completely different manufacturer. - Saying that you'll be happy to run some tests "as soon as you find some time." If you couldn't find the time by now, you never will. - Giving me an excuse for not sending me any feedback earlier. I don't care if your dog got run over, your house was invaded by giant ants, your entire family contracted the bubonic plague or aliens stole your computer. - Asking me how to set up a 3Com card in Linux. (Comparing the xl driver's performance with the Linux 3Com driver is acceptable, provided you run the comparison on the same hardware. Comparing a PIII 600Mhz host running Linux to a PII 300Mhz host running FreeBSD is not a fair comparison. Unless FreeBSD ends up being faster. :) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 13:58:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 1900915036; Sun, 10 Oct 1999 13:58:05 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id OAA06730; Sun, 10 Oct 1999 14:57:57 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA11530; Sun, 10 Oct 1999 14:57:55 -0600 Date: Sun, 10 Oct 1999 14:57:55 -0600 Message-Id: <199910102057.OAA11530@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: Bruce Evans , freebsd-arch@FreeBSD.org, mckusick@mckusick.com, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: The eventual fate of BLOCK devices. In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I Can't believe this email only produced TWO responses! > I would have thought that this wouldhav brought out the chainsaws! > Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't > work? (the only responders got it via 'core') Interesting. It appears that somehow I got 'unsubscribed' from arch. Not sure why, but in May I was subscribed, but I'm no longer subscribed. Did everyone get unsubscribed when it went idle? (I'm not commenting on the content as I haven't done enough research to agree/disagree with anything yet.) Nate > > julian > > On Sat, 9 Oct 1999, Bruce Evans wrote: > > > > PHK has been moving steadily in this direction to remove as many > > > dependencies within the kernel on block devices as possible. > > > The question is, When did the decision to do so become official? > > > > Never. > > > > > I don't believe it has been a stated official decision yet and so in order > > > to put some clarity into the air over this I'd like to launch a PURELY > > > TECHNICAL discussion on the topic. > > > > > > Here are some starters. > > > > > > 1/ block device writes have to be synchrnous or the user doesn't get > > > write errors. > > > > Block devices should be implmented properly or the user doesn't get write > > errors. > > > > A proper implementation is quite close. Write errors should be reported > > on last-close and on fsync(). They already are as far as I can see, modulo > > the bugs that (in -current) VOP_FSYNC() = ffs_fsync() sometimes hangs > > instead of returning a write error and vinvalbuf() sometimes panics instead > > of returning a write error. The bugs are different and worse in RELENG_3. > > The bugs are different and more benign in RELENG_2_2 (write errors are > > ignored). Note that the bugs have very little to do with specfs. All > > specfs can reasonably do is kill the endless retries at a suitable time, > > probably after calling vinvalbuf() in last-close. > > > > > 1A/ if they are not synchronous, errors need to be coped with in some > > > other manner. > > > > Normal error handling suffices, modulo bugs. > > > > > 2/ People with old UNIX experience expect to be able to do unalligned > > > transfers on block devices. > > > 3/ DEVFS can cope just fine with block and char devices > > > (I include this because DEVFS has been used as an argument for > > > removing them) > > > > Correct. > > > > > 4/ Most of the block buffering code in the kernel will remain due to > > > the VM and VFS systems. > > > > Well, if the Nth rewrite of vm wants to drop support for buffers in vfs, > > then use of buffers for block devices shouldn't stop it. > > > > > 5/ New users don't tend to understand the rather strange distinctions > > > between BLK and CHR devices. Some people consider having both POLA and > > > > This is an argument for removing character (disk) devices, since most > > new users will be from Linux where block (disk) devices were the only > > ones available until recently. Block devices have always worked better > > in Linux. E.g., media change is detected for floppies, and buffers > > remain valid across last-close, until media change. The latter behaviour > > can be not what is wanted (extra ioctls are needed to discard the buffers), > > but it is often useful. > > > > > others consider having only one POLA. Linux had til just recently, > > > only BLK disk devices. They just aded CHR disk devices but I don't > > > know if they created a whole second calss of device to do so. (I doubt it) > > > 6/ It should be possible to make an overlay device (similar to the way > > > ccd works), that supplies buffered characteristics to a disk. This may > > > be a different minor number or a differnt major number.. but be a CHR > > > type device. > > > > This would involve needless duplicatication of half of the buffer cache > > implementation (maybe the simple half) unless the buffer cache goes away. > > > > Bruce > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 14: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 7C45515333; Sun, 10 Oct 1999 14:02:38 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id XAA20923; Sun, 10 Oct 1999 23:02:37 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id XAA02056; Sun, 10 Oct 1999 23:02:37 +0200 (MET DST) Date: Sun, 10 Oct 1999 23:02:37 +0200 From: Eivind Eklund To: Nate Williams Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: People getting automatically unsub'ed from -arch Message-ID: <19991010230237.A777@bitbox.follo.net> References: <199910102057.OAA11530@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199910102057.OAA11530@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Mayhaps too many Cc:'s kept in order to reach relevant audience] On Sun, Oct 10, 1999 at 02:57:55PM -0600, Nate Williams wrote: > > I Can't believe this email only produced TWO responses! > > I would have thought that this wouldhav brought out the chainsaws! > > Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't > > work? (the only responders got it via 'core') > > Interesting. It appears that somehow I got 'unsubscribed' from arch. > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > Did everyone get unsubscribed when it went idle? Not *everybody*, at least - my subscription has kept. I do not know of any mass-unsubscription. Eivind, ex-moderator and now pseudo-moderator of -arch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 14: 9:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 3C49215605; Sun, 10 Oct 1999 14:09:12 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id PAA06832; Sun, 10 Oct 1999 15:09:11 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA11586; Sun, 10 Oct 1999 15:09:10 -0600 Date: Sun, 10 Oct 1999 15:09:10 -0600 Message-Id: <199910102109.PAA11586@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Nate Williams , committers@FreeBSD.org, current@FreeBSD.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991010230237.A777@bitbox.follo.net> References: <199910102057.OAA11530@mt.sri.com> <19991010230237.A777@bitbox.follo.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [Mayhaps too many Cc:'s kept in order to reach relevant audience] Thanks, sorry about the X-posting... > On Sun, Oct 10, 1999 at 02:57:55PM -0600, Nate Williams wrote: > > > I Can't believe this email only produced TWO responses! > > > I would have thought that this wouldhav brought out the chainsaws! > > > Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't > > > work? (the only responders got it via 'core') > > > > Interesting. It appears that somehow I got 'unsubscribed' from arch. > > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > > > Did everyone get unsubscribed when it went idle? > > Not *everybody*, at least - my subscription has kept. I do not know > of any mass-unsubscription. Hmm, weird. I can see that the 'old' list of people was saved on hub as 'freebsd-arch.19990501', of which I'm a member. However, I never received the email Simon Shapiro sent out in June that I just read, so I know I was removed then. I also note that freebsd-arch is the only 'list' that has a backup copy, so *something* happened, and someone knew about it. (I'm not implying that it was intentional to remove people, or what, but *something* happened and there was no mention of it...) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 14:12:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id B75171527B; Sun, 10 Oct 1999 14:12:05 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id PAA06860; Sun, 10 Oct 1999 15:12:04 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA11625; Sun, 10 Oct 1999 15:12:03 -0600 Date: Sun, 10 Oct 1999 15:12:03 -0600 Message-Id: <199910102112.PAA11625@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: nate@mt.sri.com (Nate Williams) Cc: Eivind Eklund , committers@FreeBSD.org, current@FreeBSD.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <199910102109.PAA11586@mt.sri.com> References: <199910102057.OAA11530@mt.sri.com> <19991010230237.A777@bitbox.follo.net> <199910102109.PAA11586@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't > > > > work? (the only responders got it via 'core') > > > > > > Interesting. It appears that somehow I got 'unsubscribed' from arch. > > > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > > > > > Did everyone get unsubscribed when it went idle? > > > > Not *everybody*, at least - my subscription has kept. I do not know > > of any mass-unsubscription. > > Hmm, weird. I can see that the 'old' list of people was saved on hub as > 'freebsd-arch.19990501', of which I'm a member. However, I never > received the email Simon Shapiro sent out in June that I just read, so I > know I was removed then. I note that David is no longer on the list (dg@root.com was 'unsubscribed, either accidentally or intentionally). Justin is gone, and many other folks I would have considered to be folks interested that were once subscribed... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 15:36:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 7522E150E4 for ; Sun, 10 Oct 1999 15:35:42 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA07769 for freebsd-current@freebsd.org; Mon, 11 Oct 1999 00:35:41 +0200 (CEST) (envelope-from olli) Date: Mon, 11 Oct 1999 00:35:41 +0200 (CEST) From: Oliver Fromme Message-Id: <199910102235.AAA07769@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Subject: Re: The eventual fate of BLOCK devices. Organization: Administration Heim 3 Reply-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote in list.freebsd-current: > Interesting. It appears that somehow I got 'unsubscribed' from arch. > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > Did everyone get unsubscribed when it went idle? FWIW, I got unsubscribed, too. While I were at it, I sent a "which" command to the majordomo, and the result did not list me as a member of freebsd-announce and freebsd-security- notifications. When I tried to re-subscribe, it told me that I am already subscribed... Seems like majordomo is major buggy. ;-) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 16: 5: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 447F01512B; Sun, 10 Oct 1999 16:05:03 -0700 (PDT) From: "Jonathan M. Bresler" To: freebsd-current@freebsd.org In-reply-to: <199910102235.AAA07769@dorifer.heim3.tu-clausthal.de> (message from Oliver Fromme on Mon, 11 Oct 1999 00:35:41 +0200 (CEST)) Subject: Re: The eventual fate of BLOCK devices. Message-Id: <19991010230503.447F01512B@hub.freebsd.org> Date: Sun, 10 Oct 1999 16:05:03 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FWIW, I got unsubscribed, too. While I were at it, I sent a > "which" command to the majordomo, and the result did not list > me as a member of freebsd-announce and freebsd-security- > notifications. When I tried to re-subscribe, it told me that > I am already subscribed... > > Seems like majordomo is major buggy. ;-) > > Regards > Oliver youare subscribed to freebsd-announce as oliver.fromme@heim3.tu-clausthal.de which oes not match the email address that you sent your which request from "olli@dorifer.heim3.tu-clausthal.de", therefore majordomo did not show your addresses as subscribed. i expect that you get the rest of the mail via newsgate. again you are not subscribed, so majordomo does not show your address in response to a which. this is not a majordomo bug. jmb > > -- > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 16:22:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1DF1E15676 for ; Sun, 10 Oct 1999 16:22:20 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40329>; Mon, 11 Oct 1999 09:18:26 +1000 Content-return: prohibited Date: Mon, 11 Oct 1999 09:12:31 +1000 From: Peter Jeremy Subject: Majordomo problems (Re: The eventual fate of BLOCK devices.) In-reply-to: <199910102235.AAA07769@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct11.091826est.40329@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199910102235.AAA07769@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-11 08:35:41 +1000, Oliver Fromme wrote: >Nate Williams wrote in list.freebsd-current: > > Interesting. It appears that somehow I got 'unsubscribed' from arch. > > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > > > Did everyone get unsubscribed when it went idle? > >FWIW, I got unsubscribed, too. Same here. > While I were at it, I sent a >"which" command to the majordomo, and the result did not list >me as a member of freebsd-announce and freebsd-security- >notifications. I did the same and also found significant differences between the mailing lists that I am receiving mail from and the ones that majordomo thinks I am subscribed to. I sent a note to Majordomo-Owner@FreeBSD.ORG last Friday, but haven't seen anything back yet (I'm not particularly fussed). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 16:41:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 356FC155FF for ; Sun, 10 Oct 1999 16:40:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id JAA49073; Mon, 11 Oct 1999 09:42:02 +1000 (EST) (envelope-from jb) Date: Mon, 11 Oct 1999 09:42:02 +1000 From: John Birrell To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Still waiting for xl driver reports Message-ID: <19991011094202.A48952@freebsd1.cimlogic.com.au> References: <199910102059.QAA24189@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910102059.QAA24189@skynet.ctr.columbia.edu>; from Bill Paul on Sun, Oct 10, 1999 at 04:59:34PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 10, 1999 at 04:59:34PM -0400, Bill Paul wrote: > I need feedback from people so that I know it's safe to merge this > stuff into -stable, so let's hear it already. It's been several weeks > since I made the changes. Surely there are people running -current > with 3Com 3c90xB cards. > > To reiterate, this only concerns people with the following adapters: > > - 3c905B-TX 10/100 I installed 3.2-RELEASE and upgraded to 4.0-CURRENT on a new machine last week. The machine came with NT installed - it is far more useful running FreeBSD. 8-) I can't comment about the relative performance, because I have nothing to compare it against. It works fine for me. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 17:18:49 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 9A540151F2; Sun, 10 Oct 1999 17:18:44 -0700 (PDT) From: "Jonathan M. Bresler" To: peter.jeremy@alcatel.com.au Cc: freebsd-current@FreeBSD.ORG In-reply-to: <99Oct11.091826est.40329@border.alcanet.com.au> (message from Peter Jeremy on Mon, 11 Oct 1999 09:12:31 +1000) Subject: Re: Majordomo problems (Re: The eventual fate of BLOCK devices.) Message-Id: <19991011001844.9A540151F2@hub.freebsd.org> Date: Sun, 10 Oct 1999 17:18:44 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG send it to postmaster instead. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 17:23:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 01F1414A11 for ; Sun, 10 Oct 1999 17:23:33 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id CAA13643 for freebsd-current@FreeBSD.ORG; Mon, 11 Oct 1999 02:23:32 +0200 (CEST) (envelope-from olli) Date: Mon, 11 Oct 1999 02:23:32 +0200 (CEST) From: Oliver Fromme Message-Id: <199910110023.CAA13643@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: The eventual fate of BLOCK devices. Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan M. Bresler wrote in list.freebsd-current: > > FWIW, I got unsubscribed, too. While I were at it, I sent a > > "which" command to the majordomo, and the result did not list > > me as a member of freebsd-announce and freebsd-security- > > notifications. When I tried to re-subscribe, it told me that > > I am already subscribed... > > > > Seems like majordomo is major buggy. ;-) > > youare subscribed to freebsd-announce as > oliver.fromme@heim3.tu-clausthal.de which oes not match the email > [...] Oh, I'm very sorry for the confusion. When I said "I", I really did not mean myself but the local newsgate (I prefer to read the lists via NNTP, which is very convenient). The newsgate is "newsgate@atlantis.rz.tu-clausthal.de". I sent both the "which" and the "subscribe" commands under that address, when the problem occured that I described in my previous mail (see above). I'm pretty sure that I didn't do anything wrong. Here's the whole story: - I sent a "which" command from the newsgate account. - Got a response with about 30 lists to which that account is subscribed. - Compared those lists to the lists that the newsgate is prepared to handle (and to which it was once subscribed). - Noticed that three lists were missing: announce, arch, and security-notifications. - Sent "subscribe" commands for those three lists to the majordomo, again using the newsgate account. - Re-subscription to the -arch list was successful. For the other two lists, I received a notice that I (the newsgate account) was already subscribed. > this is not a majordomo bug. It is. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 17:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 82962155C1 for ; Sun, 10 Oct 1999 17:38:16 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id SAA15816; Sun, 10 Oct 1999 18:38:58 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199910110038.SAA15816@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: gibbs@plutotech.com (Justin T. Gibbs), current@FreeBSD.ORG Subject: Re: How do I get a PCCARD modem to work? In-reply-to: Your message of "Fri, 08 Oct 1999 08:31:15 +0200." <199910080631.IAA27151@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Oct 1999 18:38:58 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It seems Justin T. Gibbs wrote: >> It looks like both nsio and sio have PCCARD support disabled at the >> moment. Is there any other way I can get the system to recognize my >> modem? > >Fix the broken sio, it might be KNF and all but it doesn't work... > >-Soren The pccard brokenness is not sio's fault. If I were following where our PCCARD support was going, I might take a stab at fixing this myself... Perhaps I'll learn more at FreeBSD-con. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 17:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id D847514ECA; Sun, 10 Oct 1999 17:48:55 -0700 (PDT) From: "Jonathan M. Bresler" To: freebsd-current@FreeBSD.ORG In-reply-to: <199910110023.CAA13643@dorifer.heim3.tu-clausthal.de> (message from Oliver Fromme on Mon, 11 Oct 1999 02:23:32 +0200 (CEST)) Subject: Re: The eventual fate of BLOCK devices. Message-Id: <19991011004855.D847514ECA@hub.freebsd.org> Date: Sun, 10 Oct 1999 17:48:55 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here's the whole story: > > - I sent a "which" command from the newsgate account. > > - Got a response with about 30 lists to which that account > is subscribed. > > - Compared those lists to the lists that the newsgate > is prepared to handle (and to which it was once subscribed). > > - Noticed that three lists were missing: announce, arch, and > security-notifications. arch and security-notifications do not honor which requests. > > - Sent "subscribe" commands for those three lists to the > majordomo, again using the newsgate account. > > - Re-subscription to the -arch list was successful. For the > other two lists, I received a notice that I (the newsgate > account) was already subscribed. correct. > > > this is not a majordomo bug. > > It is. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 18: 8:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id 5136214BF1 for ; Sun, 10 Oct 1999 18:07:32 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id SAA22856; Sun, 10 Oct 1999 18:07:31 -0700 (PDT) (envelope-from sef) Date: Sun, 10 Oct 1999 18:07:31 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199910110107.SAA22856@kithrup.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <199910102112.PAA11625.kithrup.freebsd.current@mt.sri.com> References: <199910102057.OAA11530@mt.sri.com> <19991010230237.A777@bitbox.follo.net> <199910102109.PAA11586@mt.sri.com> Organization: Kithrup Enterprises, Ltd. Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910102112.PAA11625.kithrup.freebsd.current@mt.sri.com> Nate writes: >I note that David is no longer on the list (dg@root.com was >'unsubscribed, either accidentally or intentionally). Justin is gone, >and many other folks I would have considered to be folks interested that >were once subscribed... "Accidental" removals from the lists are so common that I give up. I no longer even try to get back on them -- it's been happening for _years_ now, and I have made multiple complaints about it, and if it's not a problem for whoever runs the mailing lists, then I just don't care that much. I have a hard enough time remembering which lists I subscribed to that I do get traffic on to check every day to see which ones have removed me without informing me. And, yip, I was apparently removed from arch@freebsd.org, despite being subscribed to it within a few hours of it having been initially created. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 18:20:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id CE83114C03; Sun, 10 Oct 1999 18:20:04 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id SAA12141; Sun, 10 Oct 1999 18:20:01 -0700 (PDT) From: Archie Cobbs Message-Id: <199910110120.SAA12141@bubba.whistle.com> Subject: Re: The eventual fate of BLOCK devices. In-Reply-To: <19991011004855.D847514ECA@hub.freebsd.org> from "Jonathan M. Bresler" at "Oct 10, 1999 05:48:55 pm" To: jmb@hub.freebsd.org (Jonathan M. Bresler) Date: Sun, 10 Oct 1999 18:20:01 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan M. Bresler writes: > > Here's the whole story: > > > > - I sent a "which" command from the newsgate account. > > > > - Got a response with about 30 lists to which that account > > is subscribed. > > > > - Compared those lists to the lists that the newsgate > > is prepared to handle (and to which it was once subscribed). > > > > - Noticed that three lists were missing: announce, arch, and > > security-notifications. > > arch and security-notifications do not honor which requests. It sounds like it would be nice then to have majordomo add a note to its response indicating this. Is that possible to configure? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 18:21:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4FD8614BD3; Sun, 10 Oct 1999 18:21:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA18665; Sun, 10 Oct 1999 18:21:04 -0700 (PDT) (envelope-from dillon) Date: Sun, 10 Oct 1999 18:21:04 -0700 (PDT) From: Matthew Dillon Message-Id: <199910110121.SAA18665@apollo.backplane.com> To: Julian Elischer Cc: Bruce Evans , freebsd-arch@FreeBSD.ORG, mckusick@mckusick.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: The eventual fate of BLOCK devices. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > 6/ It should be possible to make an overlay device (similar to the way :> > ccd works), that supplies buffered characteristics to a disk. This may :> > be a different minor number or a differnt major number.. but be a CHR :> > type device. :> :> This would involve needless duplicatication of half of the buffer cache :> implementation (maybe the simple half) unless the buffer cache goes away. :> :> Bruce It should be noted that the current implementation of block devices is fairly trivial, only a few dozen lines of code. I agree with Bruce: it would be silly to throw that away and spend days rewriting it. There is nothing wrong with block device's that can't be trivially fixed other then the fact that Poul seems rabidly intent on destroying them, and there isn't anything wrong with using filesystem buffers either. It should also be noted that in order to maintain cache coherency between read/write and mmap() on a block device, you either have to go through the buffer cache or you have to rewrite considerably more then just specfs. There are several trivial ways to solve the write-error problem. First, implement writes as write-through so a synchronous error can be returned. Second, implement an error code on close. There are other possibilities as well, such as implementing a single buffer pipeline and returning a delayed error, which preserves some of the write pipelining performance, or implementing an intermediate backing layer (such as swap) to buffer errored blocks for later retrieval. There are also situations where errors can be assumed to not occur, such as when using buffered VN partition which is backed by a file or swap. It isn't inconceivable that the methodology could be selected with an ioctl(), with the write-through-synchronous-return for writes made the default. This is all of a dozen lines of code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 18:57:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id C7DEE14DF2 for ; Sun, 10 Oct 1999 18:57:50 -0700 (PDT) (envelope-from tom@embt.com) Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id VAA00314 for ; Sun, 10 Oct 1999 21:02:13 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19991010215737.00acd374@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 10 Oct 1999 21:57:37 -0400 To: freebsd-current@freebsd.org From: Tom Embt Subject: MajorDomo Problems 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 mysteriously unsubscribed from -questions sometime between Oct 7th and Oct 10th. My guess puts it at late morning/early afternoon EDT on the 7th. It would seem something is up... good thing somebody mentioned the 'which' command (I'd never heard of it), I was wondering why noone was responding to an earlier post ;) Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 20:50:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (Postfix) with ESMTP id D3C3C150F2 for ; Sun, 10 Oct 1999 20:50:34 -0700 (PDT) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (alister.w.easynet.co.uk [212.212.251.86]) by kiwi.mail.easynet.net (Postfix) with ESMTP id 195E9DAF1E for ; Mon, 11 Oct 1999 04:50:32 +0100 (BST) Message-ID: <38016E09.61B8A064@freenet.co.uk> Date: Mon, 11 Oct 1999 04:56:41 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: MajorDomo Problems References: <3.0.3.32.19991010215737.00acd374@mail.embt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Embt wrote: > > I've been mysteriously unsubscribed from -questions sometime between Oct > 7th and Oct 10th. My guess puts it at late morning/early afternoon EDT on > the 7th. > > It would seem something is up... good thing somebody mentioned the 'which' > command (I'd never heard of it), I was wondering why noone was responding > to an earlier post ;) Hey - I was unsubscribed from -cvs-all, -advocacy, -emulation, -hackers, -mobile, -multimedia, -new-bus, -announce and -stable! In other words, ALL mailing lists I was subscribed to except -current. This happened twice! The first time was a couple of weeks ago - I just ignored it and resubscribed - but having to do it again is just too much! Please do something about it, sort it out! It really sucks having to acknowledge every subscribe request and then receive a whole bunch of confirmation messages. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 10 21:36:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BA52A1516A for ; Sun, 10 Oct 1999 21:36:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA10018; Sun, 10 Oct 1999 21:36:24 -0700 Date: Sun, 10 Oct 1999 21:36:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andy Farkas Cc: freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update 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 Huh? I'll check it out.. On Sun, 10 Oct 1999, Andy Farkas wrote: > > Just a reminder I guess, > > # uname -v > FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 > > # mt retension > > console emits (in bright white): > > WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") > > > > -- > > :{ andyf@speednet.com.au > > Andy Farkas > System Administrator > Speednet Communications > http://www.speednet.com.au/ > > > > > > 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 Sun Oct 10 23:18:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id BFA0014DA2 for ; Sun, 10 Oct 1999 23:18:18 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA67453; Mon, 11 Oct 1999 08:18:05 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910110618.IAA67453@gratis.grondar.za> To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Kerberized telnet not installed Date: Mon, 11 Oct 1999 08:18:04 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just built and installed sources cvsup'd at 17:45 CDT October 9 with > ${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed. I > looked over the recent changes to add SRA to telnet, but I am not familiar > enough with the order in which things are built and installed to figure > out what happened. I did notice that secure/usr.bin/telnet/Makefile was > brought back to life after being dead for about 3 years, but this was the > only change that really jumped out at me as being significant. Is there > something new I need do to get a Kerberized telnet? Thanks. Please send me the output of # ldd /usr/bin/telnet Thanks! 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 Sun Oct 10 23:30: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 39B5714F98 for ; Sun, 10 Oct 1999 23:29:54 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA67648; Mon, 11 Oct 1999 08:29:45 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910110629.IAA67648@gratis.grondar.za> To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Kerberized telnet not installed Date: Mon, 11 Oct 1999 08:29:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just built and installed sources cvsup'd at 17:45 CDT October 9 with > ${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed. I > looked over the recent changes to add SRA to telnet, but I am not familiar > enough with the order in which things are built and installed to figure > out what happened. I did notice that secure/usr.bin/telnet/Makefile was > brought back to life after being dead for about 3 years, but this was the > only change that really jumped out at me as being significant. Is there > something new I need do to get a Kerberized telnet? Thanks. I found the problem. I'll commit later on today. 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 Sun Oct 10 23:39:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id DB01D14BB8 for ; Sun, 10 Oct 1999 23:39:40 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by MexComUSA.net (8.9.3/8.9.3) with ESMTP id XAA70302; Sun, 10 Oct 1999 23:39:10 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <38018644.FC20964C@MexComUSA.NET> Date: Sun, 10 Oct 1999 23:40:04 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nick Hibma Cc: Ollivier Robert , FreeBSD Current Subject: Re: staroffice References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed it out of curiosity. Everything went well until I try to execute it. It starts as if it were going to work and then it gives me a core dump with a message box that says, "An unrecoverable error has occurred. All modified files have been saved and probably can be recovered at reset" . My Linux emulation is working fine. I am using linux netscape 4.7 with glibc and many linux plugins with no problems. Anyone else seeing that. Thanks, ed Nick Hibma wrote: > > > o unzip setup.zip to someplace comfortable > > > > Don't both with that. > > > > use "export LD_LIBRARY_PATH=/tmp/sv001.tmp:." before running the setup binary. > ^^^ > > That number changes, so you might have to go into /tmp and delete stale > directories. > > Nick > -- > e-Mail: hibma@skylink.it > > 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 Sun Oct 10 23:54:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id B4E4F14BCE for ; Sun, 10 Oct 1999 23:54:38 -0700 (PDT) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id IAA02129; Mon, 11 Oct 1999 08:54:20 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <199910110654.IAA02129@numeri.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: Edwin Culp Cc: Nick Hibma , Ollivier Robert , FreeBSD Current Subject: Re: staroffice In-reply-to: Your message of "Sun, 10 Oct 1999 23:40:04 PDT." <38018644.FC20964C@MexComUSA.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 08:54:20 +0200 From: Johan Karlsson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 10 Oct 1999 23:40:04 PDT, Edwin Culp wrote: >I just installed it out of curiosity. Everything went well until I try to exe >cute >it. It starts as if it were going to work and then it gives me a core dump wi >th a >message box that says, "An unrecoverable error has occurred. All modified fil >es >have been saved and probably can be recovered at reset" . My Linux emulation >is >working fine. I am using linux netscape 4.7 with glibc and many linux plugins > with >no problems. > >Anyone else seeing that. > This happend to me, removing the dir Office51 in my home directory solved it. /K -- Johan Karlsson mailto:k@numeri.campus.luth.se SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 1: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id D79251504C; Mon, 11 Oct 1999 01:05:08 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id JAA92847; Mon, 11 Oct 1999 09:05:03 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00710; Mon, 11 Oct 1999 08:30:14 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910110730.IAA00710@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: Julian Elischer , Bruce Evans , freebsd-arch@FreeBSD.org, mckusick@mckusick.com, committers@FreeBSD.org, current@FreeBSD.org Subject: People getting automatically unsub'ed from -arch In-reply-to: Your message of "Sun, 10 Oct 1999 14:57:55 MDT." <199910102057.OAA11530@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 08:30:14 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I Can't believe this email only produced TWO responses! > > I would have thought that this wouldhav brought out the chainsaws! > > Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't > > work? (the only responders got it via 'core') > > Interesting. It appears that somehow I got 'unsubscribed' from arch. > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > Did everyone get unsubscribed when it went idle? I believe I did more than once. I've re-subscribed several times and got a ``you'll have to be approved manually'' message back. When I tried again a few days ago, it seemed to stick. Like you, I was subscribed at one point.... > Nate -- 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 Mon Oct 11 1:10:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1BA951533B for ; Mon, 11 Oct 1999 01:10:45 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id BAA03671 for ; Mon, 11 Oct 1999 01:10:41 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199910110810.BAA03671@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: 3dfx Driver? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 01:10:41 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone ported the linux 3DFx Driver to FreeBSD? Tnks! -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 1:30:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 52BE914A16 for ; Mon, 11 Oct 1999 01:29:49 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA20468; Mon, 11 Oct 1999 09:30:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 11 Oct 1999 09:30:35 +0100 (BST) From: Doug Rabson To: "Matthew N. Dodd" Cc: Jason DiCioccio , current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org 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 Sun, 10 Oct 1999, Matthew N. Dodd wrote: > On Sun, 10 Oct 1999, Matthew N. Dodd wrote: > > On Sun, 10 Oct 1999, Doug Rabson wrote: > > > Your card is an SMC EtherEZ (8416). I think that needs some special > > > extra tricks to get it supported. Matt Dodd was > > > working on this recently but I don't know if he has it working yet. > > > > I've got uncommitted patches that fix this I believe. I need to go back > > and test them before I commit but they should work. > > Ok, I've tested my patches and remembered why I didn't ever do anything > with them. > > *** ISA_GET_RESOURCE(,,SYS_RES_MEMORY,...) failed (2) > unknown0: at port 0x240-0x25f irq 9 on isa0 > > ed_probe_WD80x3() doesn't understand boards that have no shared memory. > > While these cards work just fine in softset mode, turning on their PnP > features seems to disable the use of shared memory. I was looking at the Linux driver and I don't think it would be hard to use their algorithm to set the memory resource appropriately. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 1:34:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7631C14A16 for ; Mon, 11 Oct 1999 01:34:18 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id EAA14114; Mon, 11 Oct 1999 04:34:13 -0400 (EDT) Date: Mon, 11 Oct 1999 04:34:12 -0400 (EDT) From: "Matthew N. Dodd" To: Doug Rabson Cc: Jason DiCioccio , current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Oct 1999, Doug Rabson wrote: > I was looking at the Linux driver and I don't think it would be hard to > use their algorithm to set the memory resource appropriately. Looks pretty simple. I'll take a crack at it tomorrow. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 2: 2:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 2557314D32 for ; Mon, 11 Oct 1999 02:02:26 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 43922 invoked from network); 11 Oct 1999 09:02:11 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 11 Oct 1999 09:02:11 -0000 Message-ID: <3801A777.7F31D00@pipeline.ch> Date: Mon, 11 Oct 1999 11:01:43 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Alex Cc: freebsd-current@freebsd.org Subject: Re: MajorDomo Problems References: <3.0.3.32.19991010215737.00acd374@mail.embt.com> <38016E09.61B8A064@freenet.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex wrote: > > Tom Embt wrote: > > > > I've been mysteriously unsubscribed from -questions sometime between Oct > > 7th and Oct 10th. My guess puts it at late morning/early afternoon EDT on > > the 7th. > > > > It would seem something is up... good thing somebody mentioned the 'which' > > command (I'd never heard of it), I was wondering why noone was responding > > to an earlier post ;) > > Hey - I was unsubscribed from -cvs-all, -advocacy, -emulation, -hackers, > -mobile, -multimedia, -new-bus, -announce and -stable! In other words, > ALL mailing lists I was subscribed to except -current. > > This happened twice! The first time was a couple of weeks ago - I just > ignored it and resubscribed - but having to do it again is just too > much! Please do something about it, sort it out! It really sucks > having to acknowledge every subscribe request and then receive a whole > bunch of confirmation messages. majordomo is crap it seems, the freebsd mailing lists should switch over to ezmlm-idx/qmail... *THAT* works 100% reliable. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 2:23:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 02ACC14C0A for ; Mon, 11 Oct 1999 02:23:04 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA14007; Mon, 11 Oct 1999 11:23:04 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id LAA12220; Mon, 11 Oct 1999 11:23:01 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <3801A777.7F31D00@pipeline.ch> References: <3.0.3.32.19991010215737.00acd374@mail.embt.com> <38016E09.61B8A064@freenet.co.uk> <3801A777.7F31D00@pipeline.ch> Date: Mon, 11 Oct 1999 11:22:11 +0200 To: Andre Oppermann , Alex From: Brad Knowles Subject: Re: MajorDomo Problems Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:01 AM +0200 1999/10/11, Andre Oppermann wrote: > majordomo is crap it seems, the freebsd mailing lists should switch > over to ezmlm-idx/qmail... *THAT* works 100% reliable. I think we can separate MLA issues from MTA issues. Myself, I've had no problems with Majordomo on the various lists I manage, but I confess that on the larger mailing lists I prefer to use tools more suited for the jobs (such as Listserv). MLA issues I would be willing to discuss relatively dispassionately. However, if you're going to get into MTA religious discussions, I would suggest that people take a long hard look at Postfix instead. Of course, none of these sorts of discussions are really relevant to -current, or for that matter, relevant to any other FreeBSD-related mailing list of which I am aware. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 3: 3: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 8960214CFB for ; Mon, 11 Oct 1999 03:02:58 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 44452 invoked from network); 11 Oct 1999 09:56:02 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 11 Oct 1999 09:56:02 -0000 Message-ID: <3801B415.A3392260@pipeline.ch> Date: Mon, 11 Oct 1999 11:55:33 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Brad Knowles Cc: Alex , freebsd-current@FreeBSD.ORG Subject: Re: MajorDomo Problems References: <3.0.3.32.19991010215737.00acd374@mail.embt.com> <38016E09.61B8A064@freenet.co.uk> <3801A777.7F31D00@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 11:01 AM +0200 1999/10/11, Andre Oppermann wrote: > > > majordomo is crap it seems, the freebsd mailing lists should switch > > over to ezmlm-idx/qmail... *THAT* works 100% reliable. > > I think we can separate MLA issues from MTA issues. Myself, I've > had no problems with Majordomo on the various lists I manage, but I > confess that on the larger mailing lists I prefer to use tools more > suited for the jobs (such as Listserv). MLA issues I would be > willing to discuss relatively dispassionately. Well, ezmlm works only with qmail because of it's superior VERP bounce system... otherwise I don't care as long as it is not sendmail. > However, if you're going to get into MTA religious discussions, I > would suggest that people take a long hard look at Postfix instead. And at qmail. But yes, that doesn't belong here. > Of course, none of these sorts of discussions are really relevant > to -current, or for that matter, relevant to any other > FreeBSD-related mailing list of which I am aware. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 3:15:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 34A0F14CF5 for ; Mon, 11 Oct 1999 03:15:34 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-50.iptelecom.net.ua [212.42.74.178]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA21911 for ; Mon, 11 Oct 1999 13:15:53 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA57138 for ; Mon, 11 Oct 1999 13:14:54 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3801B89C.5DDD29D9@altavista.net> Date: Mon, 11 Oct 1999 13:14:53 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: ATA related panic Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that ATA is broken - it paniced when kernel is booting. Following is diagnostic output: isa0: on motherboard pccard0: on motherboard Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ca927 stack pointer = 0x10:0xc032fe14 frame pointer = 0x10:0xc032fe28 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault First I think that this is pccard breakage, but look into "nm /kernel" gave me following symbols around 0xc01ca927: c01ca8b4 t ata_isaprobe c01ca8b4 t gcc2_compiled. c01ca9c0 t ata_isaattach c01caa58 t ata_pcimatch c01cabe0 t ata_pciprobe c01cac0c t ata_pciattach c01cb0a0 t ata_probe c01cb3a0 t ataintr c01cb42c T ata_start c01cb570 T ata_reset c01cb6b0 T ata_reinit c01cb79c T ata_wait So, I've recommpiled my kernel with wd0 instead and its working now. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 3:44: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B3AB314CD0 for ; Mon, 11 Oct 1999 03:43:56 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA36975; Mon, 11 Oct 1999 12:43:53 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910111043.MAA36975@freebsd.dk> Subject: Re: ATA related panic In-Reply-To: <3801B89C.5DDD29D9@altavista.net> from Maxim Sobolev at "Oct 11, 1999 01:14:53 pm" To: sobomax@altavista.net Date: Mon, 11 Oct 1999 12:43:53 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > It seems that ATA is broken - it paniced when kernel is booting. Following is > diagnostic output: > > isa0: on motherboard > pccard0: on motherboard > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xc > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01ca927 > stack pointer = 0x10:0xc032fe14 > frame pointer = 0x10:0xc032fe28 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault Oops, try this patch: Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.25 diff -u -r1.25 ata-all.c --- ata-all.c 1999/10/10 18:08:36 1.25 +++ ata-all.c 1999/10/11 10:42:36 @@ -115,7 +115,7 @@ /* check if allready in use by a PCI device */ for (ctlr = 0; ctlr < atanlun; ctlr++) { - if (atadevices[ctlr]->ioaddr == rman_get_start(port)) { + if (atadevices[ctlr] && atadevices[ctlr]->ioaddr==rman_get_start(port)){ printf("ata-isa%d: already registered as ata%d\n", device_get_unit(dev), ctlr); bus_release_resource(dev, SYS_RES_IOPORT, 0, port); -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 4: 2:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 82A5F14DC9 for ; Mon, 11 Oct 1999 04:02:15 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup1-39.iptelecom.net.ua [212.42.74.39]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id OAA27557; Mon, 11 Oct 1999 14:02:32 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id OAA57285; Mon, 11 Oct 1999 14:01:36 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3801C38F.D80B1342@altavista.net> Date: Mon, 11 Oct 1999 14:01:35 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATA related panic References: <199910111043.MAA36975@freebsd.dk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Maxim Sobolev wrote: > > It seems that ATA is broken - it paniced when kernel is booting. Following is > > diagnostic output: > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0xc > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc01ca927 > Oops, try this patch: Yes, it works! -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 4: 3:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 80BB314DDF for ; Mon, 11 Oct 1999 04:03:41 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA37021; Mon, 11 Oct 1999 13:03:39 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910111103.NAA37021@freebsd.dk> Subject: Re: ATA related panic In-Reply-To: <3801C38F.D80B1342@altavista.net> from Maxim Sobolev at "Oct 11, 1999 02:01:35 pm" To: sobomax@altavista.net Date: Mon, 11 Oct 1999 13:03:39 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: [Charset koi8-r unsupported, filtering to ASCII...] > Soren Schmidt wrote: > > > It seems Maxim Sobolev wrote: > > > It seems that ATA is broken - it paniced when kernel is booting. Following is > > > diagnostic output: > > > Fatal trap 12: page fault while in kernel mode > > > fault virtual address = 0xc > > > fault code = supervisor read, page not present > > > instruction pointer = 0x8:0xc01ca927 > > Oops, try this patch: > > Yes, it works! Roger, I'll commit it right away... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 4:45: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from infoteka.nsk.ru (infoteka.nsk.ru [212.20.32.40]) by hub.freebsd.org (Postfix) with SMTP id 3A27C14D8B for ; Mon, 11 Oct 1999 04:44:55 -0700 (PDT) (envelope-from nnd@infoteka.nsk.ru) Received: (qmail 7368 invoked by uid 0); 11 Oct 1999 11:44:50 -0000 Message-ID: <19991011184450.47021@mail.nsk.ru> Date: Mon, 11 Oct 1999 18:44:50 +0700 From: Nickolay Dudorov To: current@freebsd.org Subject: Abit's BP6 and 'lmmon' or 'chm' Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody successfully use ports/sysutils/{lmmon|chm} with the Abit's BP6 motherboard ? After 'make install'-ing ports and adding controller smbus0 controller iicbus0 controller iicbb0 controller intpm0 device smb0 at smbus? to kernel config file (and config, make depend, make, make install, reboot the new kernel) I only receive: IOCTL: device not configured from lmmon and chm. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 5:17:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id D65D414E3B for ; Mon, 11 Oct 1999 05:17:24 -0700 (PDT) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 9D7DF1DAE; Mon, 11 Oct 1999 14:17:27 +0200 (CEST) Date: Mon, 11 Oct 1999 14:17:27 +0200 From: "Dave J. Boers" To: Nickolay Dudorov Cc: current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' Message-ID: <19991011141727.A4120@relativity.student.utwente.nl> Reply-To: djb@wit389306.student.utwente.nl References: <19991011184450.47021@mail.nsk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991011184450.47021@mail.nsk.ru> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 11, 1999 at 06:44:50PM +0700, Nickolay Dudorov wrote: > Does anybody successfully use ports/sysutils/{lmmon|chm} > with the Abit's BP6 motherboard ? > II only receive: > IOCTL: device not configured > from lmmon and chm. I have the same problem with the 'wmhm' port. I also have Abit BP6 with two 450 Mhz Celerons. Dave. -- Dave J. Boers djb@relativity.student.utwente.nl I will *NOT* read email sent to Graduate student of Theoretical Physics d.j.boers@student.utwente.nl -> 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 Mon Oct 11 5:18:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 382A5151F5 for ; Mon, 11 Oct 1999 05:18:30 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 296C69B22; Mon, 11 Oct 1999 08:18:29 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 1FAB8BA1C; Mon, 11 Oct 1999 08:18:29 -0400 (EDT) Date: Mon, 11 Oct 1999 08:18:29 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Nickolay Dudorov Cc: current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' In-Reply-To: <19991011184450.47021@mail.nsk.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Oct 1999, Nickolay Dudorov wrote: > Does anybody successfully use ports/sysutils/{lmmon|chm} > with the Abit's BP6 motherboard ? > > After 'make install'-ing ports and adding > > controller smbus0 > controller iicbus0 > controller iicbb0 > controller intpm0 > device smb0 at smbus? > > to kernel config file (and config, make depend, make, make install, > reboot the new kernel) I only receive: > > IOCTL: device not configured > > from lmmon and chm. > This is due to the intpm controller not configuring the motherboards PM controller, not because the software. I emailed Takanori Watanabe a while back concerning this MB. His thoughts were that: 1) He hadn't heard of the driver working in an SMP environment; 2) It may be due to the controller using an unconfigured ISA interface. Anyone else wish to comment? ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 5:23:22 1999 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 A1EC814E39 for ; Mon, 11 Oct 1999 05:23:18 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 92388 invoked by uid 1001); 11 Oct 1999 12:23:14 +0000 (GMT) To: djb@wit389306.student.utwente.nl Cc: nnd@mail.nsk.ru, current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 11 Oct 1999 14:17:27 +0200" References: <19991011141727.A4120@relativity.student.utwente.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 11 Oct 1999 14:23:14 +0200 Message-ID: <92386.939644594@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Does anybody successfully use ports/sysutils/{lmmon|chm} > > with the Abit's BP6 motherboard ? > > > II only receive: > > IOCTL: device not configured > > from lmmon and chm. > > I have the same problem with the 'wmhm' port. I also have Abit BP6 with two > 450 Mhz Celerons. Ditto. BP6 with 2xCeleron 366, no overclocking. FreeBSD-current as of a couple of days ago. 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 Mon Oct 11 5:46:23 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id A3A0114BEB; Mon, 11 Oct 1999 05:46:21 -0700 (PDT) From: "Jonathan M. Bresler" To: current@freebsd.org Cc: current@freebsd.org In-reply-to: <199910110107.SAA22856@kithrup.com> (message from Sean Eric Fagan on Sun, 10 Oct 1999 18:07:31 -0700 (PDT)) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991011124621.A3A0114BEB@hub.freebsd.org> Date: Mon, 11 Oct 1999 05:46:21 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "Accidental" removals from the lists are so common that I give up. I no > longer even try to get back on them -- it's been happening for _years_ now, > and I have made multiple complaints about it, and if it's not a problem for > whoever runs the mailing lists, then I just don't care that much. only one comment. i remove people from the lists whenever their email bounces. the threshhold is approximately 30 messages in a 24 hour period. mail may bounce due to DNS problems, mail box full, MTA misconfiguration. i also remove people that send vacation messages to the list. oh, and spammers. i do NOT send the person mail to inform them that the are being removed from the mailing lists, because their email is bouncing. > > I have a hard enough time remembering which lists I subscribed to that I do > get traffic on to check every day to see which ones have removed me without > informing me. several people with recurring email delivery problems have written a script to monitor their subscriptions for them. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 6:10:24 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id B7DC214D27; Mon, 11 Oct 1999 06:10:22 -0700 (PDT) From: "Jonathan M. Bresler" To: ak@freenet.co.uk Cc: freebsd-current@freebsd.org In-reply-to: <38016E09.61B8A064@freenet.co.uk> (message from Alex on Mon, 11 Oct 1999 04:56:41 +0000) Subject: Re: MajorDomo Problems Message-Id: <19991011131022.B7DC214D27@hub.freebsd.org> Date: Mon, 11 Oct 1999 06:10:22 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes....you or your provider was bouncing your email. i unsubscribed you on Oct 07 05:40:22. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 7: 8: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 9657114EC0 for ; Mon, 11 Oct 1999 07:07:54 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA99925; Mon, 11 Oct 1999 07:07:15 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <3801EF4D.FDB9C5B4@MexComUSA.NET> Date: Mon, 11 Oct 1999 07:08:14 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Johan Karlsson Cc: Nick Hibma , Ollivier Robert , FreeBSD Current Subject: Re: staroffice51 An unrecoverable error has occurred References: <199910110654.IAA02129@numeri.campus.luth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Karlsson wrote: > At Sun, 10 Oct 1999 23:40:04 PDT, Edwin Culp wrote: > >I just installed it out of curiosity. Everything went well until I try to exe > >cute > >it. It starts as if it were going to work and then it gives me a core dump wi > >th a > >message box that says, "An unrecoverable error has occurred. All modified fil > >es > >have been saved and probably can be recovered at reset" . My Linux emulation > >is > >working fine. I am using linux netscape 4.7 with glibc and many linux plugins > > with > >no problems. > > > >Anyone else seeing that. > > > > This happend to me, removing the dir Office51 in my home directory solved it. I didn't install it there, to begin with;-) Still, I can't seem to find the problem. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 7:50:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 67B31150CD for ; Mon, 11 Oct 1999 07:50:00 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA00156; Mon, 11 Oct 1999 07:49:38 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <3801F93C.313FC74F@MexComUSA.NET> Date: Mon, 11 Oct 1999 07:50:37 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Sean O'Connell" Cc: "current@FreeBSD.ORG" Subject: Re: staroffice51 An unrecoverable error has occurred References: <199910110654.IAA02129@numeri.campus.luth.se> <3801EF4D.FDB9C5B4@MexComUSA.NET> <19991011101600.C1274@stat.Duke.EDU> <3801F6F7.579D3493@MexComUSA.NET> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > Sean O'Connell wrote: > > > On 1999 Oct 11, Edwin Culp (aka eculp@MexComUSA.NET) wrote: > > > I didn't install it there, to begin with;-) Still, I can't seem to find the > > > problem. > > > > Ed- > > > > I saw this problem with a user on a laptop running 3.2+PAO. It > > seems to mostly work under 3.3+PAO (other than the "unable to start > > plugin manager ... I thought I had that fixed, but now it doesn't > > work anymore ... sigh). > > > > I do my installs in /usr/local/Office51 with a net setup and then > > have the users do a workstation setup. StarOffice5.0 worked fine > > for me. > > I've installed in /var/Office51, but I don't think that should make a > difference. I'm running current on an ams laptop, that could make a > difference:-) I really don't have any problems with it. I'm going to play with > setup and see if that changes anything. > Sean, I can't really find that setup has any interesting options:-( I have played with ldconfig and LD_LIBRARY_PATH, even PATH with no avail. I'm getting this in my /var/log/messages. Oct 11 07:42:42 local-27 /kernel: pid 28851 (soffice.bin), uid 0: exited on signal 6 (core dumped) Oct 11 07:46:07 local-27 /kernel: pid 28874 (soffice.bin), uid 0: exited on signal 6 (core dumped) I'm going to keep looking. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 8:19:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2FB4415183; Mon, 11 Oct 1999 08:19:13 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA09884; Mon, 11 Oct 1999 11:19:12 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Mon, 11 Oct 1999 11:19:12 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: "Jonathan M. Bresler" Cc: ak@freenet.co.uk, freebsd-current@freebsd.org Subject: Re: MajorDomo Problems In-Reply-To: <19991011131022.B7DC214D27@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Love to know why my freebsd-arch subscription disappeared, although the rest appeared to stick around. I just resubscribed, but was subscribed before (but not sure about until when) as bb+lists.freebsd.arch@cyrus.watson.org What is strange is that if that was bouncing, I would have expected, say, my -current subscription to bounce just as much and be unsubscribed. From the files in the directory, maybe it is the case that a reboot/crash hit hub as a subscription request was being processed? (does it rewrite the file in place, or does it copy the file out with changes, then do a double rename to put it back in place over the old version?) Robert On Mon, 11 Oct 1999, Jonathan M. Bresler wrote: > > yes....you or your provider was bouncing your email. > > i unsubscribed you on Oct 07 05:40:22. > > jmb > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 8:34:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 1266314DAD; Mon, 11 Oct 1999 08:34:34 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id JAA15342; Mon, 11 Oct 1999 09:34:33 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA14592; Mon, 11 Oct 1999 09:34:33 -0600 Date: Mon, 11 Oct 1999 09:34:33 -0600 Message-Id: <199910111534.JAA14592@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jonathan M. Bresler" Cc: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991011124621.A3A0114BEB@hub.freebsd.org> References: <199910110107.SAA22856@kithrup.com> <19991011124621.A3A0114BEB@hub.freebsd.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "Accidental" removals from the lists are so common that I give up. I no > > longer even try to get back on them -- it's been happening for _years_ now, > > and I have made multiple complaints about it, and if it's not a problem for > > whoever runs the mailing lists, then I just don't care that much. > > only one comment. i remove people from the lists whenever > their email bounces. How long do you wait to determine 'bounced' email? I've bounced mail to hotmail recently, and it wasn't hotmail accounts problem. (No comments from the peanut gallery, it's an easy way for our folks on the road to get email simply.. :) > the threshhold is approximately 30 messages in a > 24 hour period. Or 5 minutes worth of emai on -hackers. :) > mail may bounce due to DNS problems, mail box full, > MTA misconfiguration. i also remove people that send vacation > messages to the list. oh, and spammers. How do you cause 'vacation' to not send messages to the list? Doesn't the stock 'vacation' program as shipped in FreeBSD send them to the list? > i do NOT send the person mail to inform them that the are > being removed from the mailing lists, because their email is bouncing. Sometimes.:) > > I have a hard enough time remembering which lists I subscribed to that I do > > get traffic on to check every day to see which ones have removed me without > > informing me. > > several people with recurring email delivery problems have > written a script to monitor their subscriptions for them. Some of the people (who apparently have problems) didn't even know they had problems.... Even so, do you have a copy of said scripts? Given that -arch and -security are not allowed to use the 'which' command, do they simply re-subscribe themselves on a weekly basis 'just in case'? Inquiring minds would like to know... Even a simple way of finding out (obviously not via email) *IF* I had been subscribed would be great. A 'unsubscribed' mailing list that I could run 'which' on that would tell me which lists I'm no longer on, however I can imagine that would be a lot of work. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 8:45: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9]) by hub.freebsd.org (Postfix) with SMTP id 937A9152EF for ; Mon, 11 Oct 1999 08:44:58 -0700 (PDT) (envelope-from spock@techfour.net) Received: (qmail 2904 invoked from network); 11 Oct 1999 15:44:57 -0000 Received: from cm-208-138-197-238.fredericksburg.mg.ispchannel.com (HELO enterprise.muriel.penguinpowered.com) (208.138.197.238) by mail001.mediacity.com with SMTP; 11 Oct 1999 15:44:57 -0000 Content-Length: 808 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-SENDERNAME: `Mike Heffner` Date: Mon, 11 Oct 1999 11:45:45 -0400 (EDT) From: Mike Heffner To: freebsd-current@freebsd.org Subject: make buildworld dies in usr.bin/kdump (fix) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A cvsup last night (Oct 10) of current dies when I do a make buildworld. It was dying in usr.bin/kdump with the error "sizeof of incomplete type" or something like that. It seems there was a header file missing, here's a patch which fixes it: --- usr.bin/kdump/mkioctls.old Mon Oct 11 11:41:27 1999 +++ usr.bin/kdump/mkioctls Mon Oct 11 10:46:17 1999 @@ -35,6 +35,7 @@ print "#include " print "#include " print "#include " + print "#include " print "#include " print "#include " print "" --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 11-Oct-99 Time: 11:42:43 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 9:44:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from web2106.mail.yahoo.com (web2106.mail.yahoo.com [128.11.68.250]) by hub.freebsd.org (Postfix) with SMTP id D031F14CAA for ; Mon, 11 Oct 1999 09:44:31 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19991011171340.7449.rocketmail@web2106.mail.yahoo.com> Received: from [147.226.112.101] by web2106.mail.yahoo.com; Mon, 11 Oct 1999 10:13:40 PDT Date: Mon, 11 Oct 1999 10:13:40 -0700 (PDT) From: "Valentin S. Chopov" Subject: ata changes & ATA_16BIT_ONLY To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How the ATA_16BIT_ONLY in ata-disk.c and atapi-all.c will be defined - kernel option, autodetection or device flag? Thanks, Val __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 9:53:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 75A8615348; Mon, 11 Oct 1999 09:53:14 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA57276; Mon, 11 Oct 1999 09:53:13 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199910111653.JAA57276@gndrsh.dnsmgr.net> Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991011124621.A3A0114BEB@hub.freebsd.org> from "Jonathan M. Bresler" at "Oct 11, 1999 05:46:21 am" To: jmb@hub.freebsd.org (Jonathan M. Bresler) Date: Mon, 11 Oct 1999 09:53:13 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > "Accidental" removals from the lists are so common that I give up. I no > > longer even try to get back on them -- it's been happening for _years_ now, > > and I have made multiple complaints about it, and if it's not a problem for > > whoever runs the mailing lists, then I just don't care that much. > > only one comment. i remove people from the lists whenever > their email bounces. the threshhold is approximately 30 messages in a > 24 hour period. mail may bounce due to DNS problems, mail box full, > MTA misconfiguration. i also remove people that send vacation > messages to the list. oh, and spammers. Perhaps these threshholds could use some minor adjustments, or perhaps my interpretation of the above policy is not quite what really happens. a) I don't think message count should be considered at all, as the this is highly dependent on the list one is on, and the current rate of messages going to it. As Nate pointed out 30 messages could be as short as 5 minutes on -hackers. And in my hay day of being on all lists it would have defanitly been in the 5 minute range almost any time of the day. b) The 24 hour time period is a bit on the short time, unless the messages are bouncing for being in the queue for at least 48 hours. Many mail configuration screw ups happen on a friday night, and may not get noticed until monday morning. Thus a 72 hour window is more reasonable for that type of mail problem. > > i do NOT send the person mail to inform them that the are > being removed from the mailing lists, because their email is bouncing. :-). Though I understand your reasoning, it really depends on for what reason they are bouncing. If it is queue time outs sending a message may just get to them, if they happen to get it fixed before the notice gets timed out and bounced. Infact that would be a really good threshold for removal due to mail bouncing due to queue timeout. In the case of immediate bounce due to mis configuration your current policy is probably the best policy. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 10:44:32 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 2B133153CB; Mon, 11 Oct 1999 10:44:30 -0700 (PDT) From: "Jonathan M. Bresler" To: nate@mt.sri.com Cc: current@FreeBSD.ORG In-reply-to: <199910111534.JAA14592@mt.sri.com> (message from Nate Williams on Mon, 11 Oct 1999 09:34:33 -0600) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991011174430.2B133153CB@hub.freebsd.org> Date: Mon, 11 Oct 1999 10:44:30 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Reply-To: nate@mt.sri.com (Nate Williams) > > > > "Accidental" removals from the lists are so common that I give up. I no > > > longer even try to get back on them -- it's been happening for _years_ now, > > > and I have made multiple complaints about it, and if it's not a problem for > > > whoever runs the mailing lists, then I just don't care that much. > > > > only one comment. i remove people from the lists whenever > > their email bounces. > > How long do you wait to determine 'bounced' email? I've bounced mail to > hotmail recently, and it wasn't hotmail accounts problem. (No comments > from the peanut gallery, it's an easy way for our folks on the road to > get email simply.. :) when the MTA gives up trying to deliver the mail, i call it bounced. so a 500 series error from the other MTA means the email has bounced. > > > the threshhold is approximately 30 messages in a > > 24 hour period. > > Or 5 minutes worth of emai on -hackers. :) > > > mail may bounce due to DNS problems, mail box full, > > MTA misconfiguration. i also remove people that send vacation > > messages to the list. oh, and spammers. > > How do you cause 'vacation' to not send messages to the list? Doesn't > the stock 'vacation' program as shipped in FreeBSD send them to the > list? dont know.....if i see them, i unsubscribe the person. [snip][ > Some of the people (who apparently have problems) didn't even know they > had problems.... > > Even so, do you have a copy of said scripts? Given that -arch and > -security are not allowed to use the 'which' command, do they simply > re-subscribe themselves on a weekly basis 'just in case'? no i dont....people have said that they use them....but its like my baseball coach said to me when i asked if i could steal second base: "okay, but dont get caught!" > > Inquiring minds would like to know... > > Even a simple way of finding out (obviously not via email) *IF* I had > been subscribed would be great. A 'unsubscribed' mailing list that I > could run 'which' on that would tell me which lists I'm no longer on, > however I can imagine that would be a lot of work. tried that....in majordomo its called the bounces list. remove people from teh regular list and subscribe them to bounces, then they get a note every week telling them about it.....no one every unsubscribed from bounces and ressubscribed to teh regular list. i ended up having to explain it to people. excessive overhead. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 11: 4:54 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id AA87414C94; Mon, 11 Oct 1999 11:04:51 -0700 (PDT) From: "Jonathan M. Bresler" To: freebsd@gndrsh.dnsmgr.net Cc: current@FreeBSD.ORG In-reply-to: <199910111653.JAA57276@gndrsh.dnsmgr.net> (freebsd@gndrsh.dnsmgr.net) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991011180451.AA87414C94@hub.freebsd.org> Date: Mon, 11 Oct 1999 11:04:51 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > > "Accidental" removals from the lists are so common that I give up. I no > > > longer even try to get back on them -- it's been happening for _years_ now, > > > and I have made multiple complaints about it, and if it's not a problem for > > > whoever runs the mailing lists, then I just don't care that much. > > > > only one comment. i remove people from the lists whenever > > their email bounces. the threshhold is approximately 30 messages in a > > 24 hour period. mail may bounce due to DNS problems, mail box full, > > MTA misconfiguration. i also remove people that send vacation > > messages to the list. oh, and spammers. > > Perhaps these threshholds could use some minor adjustments, or perhaps > my interpretation of the above policy is not quite what really happens. > > a) I don't think message count should be considered at all, as the this > is highly dependent on the list one is on, and the current rate of > messages going to it. As Nate pointed out 30 messages could be as > short as 5 minutes on -hackers. And in my hay day of being on all > lists it would have defanitly been in the 5 minute range almost any > time of the day. i said "approximately" because i do take into account the number of lists subscribe and the nature of the lists. an it gives me some wiggle room. > > b) The 24 hour time period is a bit on the short time, unless the messages > are bouncing for being in the queue for at least 48 hours. Many mail > configuration screw ups happen on a friday night, and may not get > noticed until monday morning. Thus a 72 hour window is more reasonable > for that type of mail problem. a message may remain in the queue for days....these are not bounces...these are queued emails. i dont count queued emails, but if i can reach your mail server and it give me back a series 500, thats a bounce. YOU, or your isp, controls this. so if our config if f*cked, go off the air (not a bounce..at least for several days) and fix it. dont leave a f*cked up mail server on the net while that server gives out series 500 responses. avoid 500 series unless you mean ;) a 500 series means "go away, and dont come back!" 5yz Permanent Negative Completion reply The command was not accepted and the requested action did not occur. The sender-SMTP is discouraged from repeating the exact request (in the same sequence). Even some "permanent" error conditions can be corrected, so the human user may want to direct the sender-SMTP to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling has been changed, or the user has altered the account status). > > > > > i do NOT send the person mail to inform them that the are > > being removed from the mailing lists, because their email is bouncing. > > :-). Though I understand your reasoning, it really depends on for what > reason they are bouncing. If it is queue time outs sending a message > may just get to them, if they happen to get it fixed before the notice > gets timed out and bounced. Infact that would be a really good threshold > for removal due to mail bouncing due to queue timeout. In the case of > immediate bounce due to mis configuration your current policy is probably > the best policy. > > -- > Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 11:21:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id A192015226 for ; Mon, 11 Oct 1999 11:21:52 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id LAA23832; Mon, 11 Oct 1999 11:21:52 -0700 (PDT) (envelope-from sef) Date: Mon, 11 Oct 1999 11:21:52 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199910111821.LAA23832@kithrup.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991011124621.A3A0114BEB.kithrup.freebsd.current@hub.freebsd.org> References: <199910110107.SAA22856@kithrup.com> (message from Sean Eric Fagan on Sun, 10 Oct 1999 18: 07:31 -0700 (PDT)) Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991011124621.A3A0114BEB.kithrup.freebsd.current@hub.freebsd.org> you write: > only one comment. i remove people from the lists whenever >their email bounces. the threshhold is approximately 30 messages in a >24 hour period. mail may bounce due to DNS problems, mail box full, >MTA misconfiguration. i also remove people that send vacation >messages to the list. oh, and spammers. My mail _has not bounced_. And yet I have been removed. > several people with recurring email delivery problems have >written a script to monitor their subscriptions for them. Goody for them. Since I do not have recurring email delivery problems, there is no reason why I should go out of my way. And, interestingly enough, I'm not the only person this has happened to, and all you can do is blame every single one of them for having "recurring email delivery problems." When are you going to realize there is a problem and admit it? When are you going to get it _fixed_? Or is your life easier if there is nobody on any of the lists? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 12: 6: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 4FB8C1573D for ; Mon, 11 Oct 1999 12:05:45 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id MAA05789; Mon, 11 Oct 1999 12:05:31 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 11 Oct 1999 12:05:31 -0700 Date: Mon, 11 Oct 1999 12:05:31 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: current@freebsd.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <199910111821.LAA23832@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: current@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know that this is not the place to hype one's own wares, but if your lists have fewer than 200 people, why not just use the free version of lyris. One of its many features is sophisticated bounce handling. -Kip On Mon, 11 Oct 1999, Sean Eric Fagan wrote: > In article <19991011124621.A3A0114BEB.kithrup.freebsd.current@hub.freebsd.org> you write: > > only one comment. i remove people from the lists whenever > >their email bounces. the threshhold is approximately 30 messages in a > >24 hour period. mail may bounce due to DNS problems, mail box full, > >MTA misconfiguration. i also remove people that send vacation > >messages to the list. oh, and spammers. > > My mail _has not bounced_. And yet I have been removed. > > > several people with recurring email delivery problems have > >written a script to monitor their subscriptions for them. > > Goody for them. Since I do not have recurring email delivery problems, there > is no reason why I should go out of my way. > > And, interestingly enough, I'm not the only person this has happened to, and > all you can do is blame every single one of them for having "recurring email > delivery problems." > > When are you going to realize there is a problem and admit it? When are you > going to get it _fixed_? > > Or is your life easier if there is nobody on any of the lists? > > > > 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 Oct 11 12:29:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 37C7F14CAA for ; Mon, 11 Oct 1999 12:29:05 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id IAA08439 for current@FreeBSD.ORG; Tue, 12 Oct 1999 08:29:04 +1300 (NZDT) Date: Tue, 12 Oct 1999 08:29:03 +1300 From: Joe Abley To: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991012082903.A4298@patho.gen.nz> References: <199910110107.SAA22856@kithrup.com> <19991011124621.A3A0114BEB.kithrup.freebsd.current@hub.freebsd.org> <199910111821.LAA23832@kithrup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910111821.LAA23832@kithrup.com>; from Sean Eric Fagan on Mon, Oct 11, 1999 at 11:21:52AM -0700 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 11, 1999 at 11:21:52AM -0700, Sean Eric Fagan wrote: > In article <19991011124621.A3A0114BEB.kithrup.freebsd.current@hub.freebsd.org> you write: > > only one comment. i remove people from the lists whenever > >their email bounces. the threshhold is approximately 30 messages in a > >24 hour period. mail may bounce due to DNS problems, mail box full, > >MTA misconfiguration. i also remove people that send vacation > >messages to the list. oh, and spammers. > > My mail _has not bounced_. And yet I have been removed. You have no way of knowing whether inbound mail to you has bounced, or not. Why are you so adamant that mail has not bounced? This discussion is a little one-sided, and is getting personal for some reason. Jmb: on behalf of the many people who have _not_ experienced problems (and those who have, but are not blaming you for them), thanks for your efforts. To those who _have_ experienced problems, remember this is a volunteer effort. Would you flame someone on a public list if you found a bug in the code they had contributed? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 12:34:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 533A814C8A for ; Mon, 11 Oct 1999 12:32:10 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id VAA6575842 for ; Mon, 11 Oct 1999 21:32:02 +0200 (CST) Received: from work.net.local (maxtnt-310.telip.uni-sb.de [134.96.71.181]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id VAA13316 for ; Mon, 11 Oct 1999 21:32:00 +0200 (CST) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id VAA52411 for ; Mon, 11 Oct 1999 21:31:45 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199910111931.VAA52411@work.net.local> Date: Mon, 11 Oct 1999 21:31:42 +0200 (CEST) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: kernel broken? (pcm) To: current@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-939670306=:52408" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-939670306=:52408 Content-Type: TEXT/plain; CHARSET=US-ASCII Hi, linking kernel.debug ac97.o: In function `ac97_setmixer': /usr/src/sys/compile/WORK/../../dev/pcm/ac97.c(.text+0x18d): undefined reference to `abs' channel.o: In function `chn_setblocksize': /usr/src/sys/compile/WORK/../../dev/pcm/channel.c:712: undefined reference to `abs' mss.o: In function `mss_speed': /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x182d): undefined reference to `abs' /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x183f): undefined reference to `abs' /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x1869): undefined reference to `abs' mss.o(.text+0x187b):/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c: more undefined references to `abs' follow *** Error code 1 1 error I tried several cvsups since the morning. Kernelconfig attached. Bye, Alexander. -- Am I supposed to be impressed? http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de --0-1804289383-939670306=:52408 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment ; filename="WORK" machine i386 ident WORK maxusers 32 makeoptions DEBUG=-g #makeoptions CONF_CFLAGS=-fno-builtin # # Allow user-mode programs to manipulate their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of). # #options USER_LDT #allow user-level control of i386 ldt # Options for the VM subsystem #options PQ_NOOPT # No coloring options PQ_LARGECACHE # color for 512k/16k cache #options PQ_HUGECACHE # color for 1024k/16k cache #cpu I586_CPU cpu I686_CPU # aka Pentium Pro(tm) options CPU_FASTER_5X86_FPU options CPU_SUSP_HLT options "NO_F00F_HACK" options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options MD5 options DDB options GDB_REMOTE_CHAT options KTRACE #kernel tracing #options PERFMON options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device bpf #Berkeley packet filter pseudo-device disc #Discard device pseudo-device streams options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPDIVERT #divert sockets options IPSTEALTH #support for stealth forwarding options TCP_RESTRICT_RST #restrict emission of TCP RST options ICMP_BANDLIM options FFS #Fast filesystem options CD9660 #ISO 9660 filesystem options KERNFS #Kernel filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options MFS #Memory File System options NFS #Network File System #options NFS_NOSERVER #Disable the NFS-server code. options FFS_ROOT #FFS usable as root device options SOFTUPDATES options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L controller scbus0 #base SCSI code #device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) #device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device pt0 at scbus? # SCSI processor type options CAM_MAX_HIGHPOWER=4 options SCSI_DELAY=5000# Be pessimistic about Joe SCSI device pseudo-device pty #Pseudo ttys pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) #pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. options MSGBUF_SIZE=40960 controller isa0 # Enable support for the kernel PLL to use an external PPS signal, # under supervision of [x]ntpd(8) # More info in ntpd documentation: http://www.eecis.udel.edu/~ntp #options PPS_SYNC controller pnp0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP="german.iso" #options KBD_DISABLE_KEYMAP_LOAD # refuse to load a keymap options KBD_INSTALL_CDEV # install a CDEV entry in /dev device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts options VESA pseudo-device splash device sc0 at isa? flags 0x06 options MAXCONS=16 # number of virtual consoles options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT="iso" options SC_HISTORY_SIZE=800 # number of history buffer lines #options SC_DISABLE_REBOOT # disable reboot key sequence device npx0 at nexus? port IO_NPX flags 0x0 irq 13 #controller ata0 #device atadisk0 # ATA disk drives ##device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives ##device atapist0 # ATAPI tape drives controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options IDE_DELAY=2000 # Be optimistic about Joe IDE device device wfd0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 device sio0 at isa? port IO_COM1 flags 0x20010 irq 4 device sio1 at isa? port 0x2e8 irq 10 flags 0x20000 device ed0 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 conflicts #device sbxvi0 at isa? port 0x220 irq 5 drq 5 conflicts #device sbmidi0 at isa? port 0x330 irq? #0x330 #device opl0 at isa? port 0x388 device pcm0 device joy0 at isa? port IO_GAME device pca0 at isa? port IO_TIMER1 device apm0 at nexus? #ACPI Experimental Driver #controller acpi0 controller pci0 controller ahc0 options AHC_ALLOW_MEMIO controller smbus0 controller intpm0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? options AVM_A1 device isic0 at isa? port 0x300 irq 3 flags 4 pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 2 pseudo-device "i4bctl" pseudo-device "i4brbch" 2 pseudo-device "i4btel" 1 pseudo-device "i4bipr" 2 options IPR_VJ pseudo-device "i4bisppp" 2 options PERIPH_1284 # Makes your computer act as a IEEE1284 # compliant peripheral controller ppbus0 device lpt0 at ppbus? #device plip0 at ppbus? device ppi0 at ppbus? #device pps0 at ppbus? device lpbb0 at ppbus? device ppc0 at isa? port? irq 7 #options CLK_CALIBRATION_LOOP #options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION controller uhci0 controller ohci0 controller usb0 device ums0 device ukbd0 device ulpt0 device uhid0 device ugen0 --0-1804289383-939670306=:52408-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 12:38:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id 7186014C31 for ; Mon, 11 Oct 1999 12:38:52 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id MAA00607; Mon, 11 Oct 1999 12:38:51 -0700 (PDT) (envelope-from sef) Date: Mon, 11 Oct 1999 12:38:51 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199910111938.MAA00607@kithrup.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991012082903.A4298.kithrup.freebsd.current@patho.gen.nz> References: <199910111821.LAA23832@kithrup.com>; from Sean Eric Fagan on Mon, Oct 11, 1999 at 11:21:52AM -0700 Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991012082903.A4298.kithrup.freebsd.current@patho.gen.nz> you write: >You have no way of knowing whether inbound mail to you has bounced, or >not. Why are you so adamant that mail has not bounced? Becuse I get lots of email, because I check it constantly, because any of a half dozen sources for it bouncing would result in my being notified on another system, because my secondary MX server has better network connectivity than the freebsd systems, because the only one who has ever made any accusations about bouncing mail has been jmb and he hasn't been able to provide any proof? >To those who _have_ experienced problems, remember this is a volunteer >effort. Would you flame someone on a public list if you found a bug >in the code they had contributed? If, after *FIVE YEARS* it hadn't been fixed, yes. That's how long this has been going on. Five years of people finding themselves mysteriously removed from lists, with no response other than, "Oh, I just remove people automatically without warning if I get too many bounces, and, no, I don't have any bounces from you but that must have been what happened." Except for one time when he admitted that he accidentally removed a bunch of people when editing a file by hand. Whatever method he is using is not working very well, and it has not worked very well for a very long time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 12:48:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 3FB3114D2F for ; Mon, 11 Oct 1999 12:48:33 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.246]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2A9B; Mon, 11 Oct 1999 21:48:25 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA10781; Mon, 11 Oct 1999 21:48:29 +0200 (CEST) (envelope-from asmodai) Date: Mon, 11 Oct 1999 21:48:28 +0200 From: Jeroen Ruigrok/Asmodai To: Amancio Hasty Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3dfx Driver? Message-ID: <19991011214828.F9737@daemon.ninth-circle.org> References: <199910110810.BAA03671@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199910110810.BAA03671@rah.star-gate.com> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On [19991011 12:00], Amancio Hasty (hasty@rah.star-gate.com) wrote: > >Has anyone ported the linux 3DFx Driver to FreeBSD? Don't think so. Why? You volunteering? =) -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best One from many. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 12:54:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 2570014A2E for ; Mon, 11 Oct 1999 12:54:36 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id IAA16062 for current@FreeBSD.ORG; Tue, 12 Oct 1999 08:54:33 +1300 (NZDT) Date: Tue, 12 Oct 1999 08:54:32 +1300 From: Joe Abley To: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991012085432.A23778@patho.gen.nz> References: <199910111821.LAA23832@kithrup.com>; <19991012082903.A4298.kithrup.freebsd.current@patho.gen.nz> <199910111938.MAA00607@kithrup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910111938.MAA00607@kithrup.com>; from Sean Eric Fagan on Mon, Oct 11, 1999 at 12:38:51PM -0700 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 11, 1999 at 12:38:51PM -0700, Sean Eric Fagan wrote: > >To those who _have_ experienced problems, remember this is a volunteer > >effort. Would you flame someone on a public list if you found a bug > >in the code they had contributed? > > If, after *FIVE YEARS* it hadn't been fixed, yes. No. It's a volunteer project. You don't flame people for bugs; you fix them, submit polite reports or keep quiet. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 12:55: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 64D0D1565C; Mon, 11 Oct 1999 12:55:08 -0700 (PDT) From: "Jonathan M. Bresler" To: kip@lyris.com Cc: current@freebsd.org In-reply-to: (message from Kip Macy on Mon, 11 Oct 1999 12:05:31 -0700 (PDT)) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991011195508.64D0D1565C@hub.freebsd.org> Date: Mon, 11 Oct 1999 12:55:08 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I know that this is not the place to hype one's own wares, but if your > lists have fewer than 200 people, why not just use the free version of > lyris. One of its many features is sophisticated bounce handling. > no problem.....but the lists have thousands of subscribers jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 13: 2:55 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 3EE3A1573D; Mon, 11 Oct 1999 13:02:54 -0700 (PDT) From: "Jonathan M. Bresler" To: current@freebsd.org Cc: current@freebsd.org In-reply-to: <199910111938.MAA00607@kithrup.com> (message from Sean Eric Fagan on Mon, 11 Oct 1999 12:38:51 -0700 (PDT)) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991011200254.3EE3A1573D@hub.freebsd.org> Date: Mon, 11 Oct 1999 13:02:54 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean, you are subscribed in different ways to different lists. cvs-all:freebsd-cvs-all@kithrup.com freebsd-alpha:freebsd-alpha@kithrup.com freebsd-bugs:freebsd-bugs@kithrup.com freebsd-chat:freebsd-chat@kithrup.com freebsd-config:freebsd-config@kithrup.com freebsd-current:freebsd-current@kithrup.com freebsd-emulation:sef@kithrup.com freebsd-fs:freebsd-fs@kithrup.com freebsd-hackers:sef@kithrup.com freebsd-hardware:freebsd-hardware@kithrup.com freebsd-mobile:freebsd-mobile@kithrup.com freebsd-platforms:freebsd-platforms@kithrup.com freebsd-ports:freebsd-ports@kithrup.com freebsd-questions:freebsd-questions-list@kithrup.com freebsd-security:freebsd-security@kithrup.com freebsd-smp:freebsd-smp@kithrup.com freebsd-stable:freebsd-stable@kithrup.com i dont see any other "kithrup.com" subscriptions. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 13: 6:41 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id F38DF156DA; Mon, 11 Oct 1999 13:06:38 -0700 (PDT) From: "Jonathan M. Bresler" To: current@freebsd.org Cc: current@freebsd.org In-reply-to: <199910111938.MAA00607@kithrup.com> (message from Sean Eric Fagan on Mon, 11 Oct 1999 12:38:51 -0700 (PDT)) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991011200638.F38DF156DA@hub.freebsd.org> Date: Mon, 11 Oct 1999 13:06:38 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Five years of people finding themselves mysteriously removed from lists, with > no response other than, "Oh, I just remove people automatically without > warning if I get too many bounces, and, no, I don't have any bounces from you > but that must have been what happened." some people have asked for copies of the bounced email. at times i have been able to provide these. more often i have not been able to because i delete bounced mail after i process it each day or couple days. i try to keep an key out for any bounced mail from "kithrup.com". no promises, but i will try. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 13:23:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D34F7156D8 for ; Mon, 11 Oct 1999 13:23:40 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA38024; Mon, 11 Oct 1999 22:23:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910112023.WAA38024@freebsd.dk> Subject: Re: ata changes & ATA_16BIT_ONLY In-Reply-To: <19991011171340.7449.rocketmail@web2106.mail.yahoo.com> from "Valentin S. Chopov" at "Oct 11, 1999 10:13:40 am" To: valsho@yahoo.com (Valentin S. Chopov) Date: Mon, 11 Oct 1999 22:23:33 +0200 (CEST) Cc: current@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 Valentin S. Chopov wrote: > > How the ATA_16BIT_ONLY in ata-disk.c and atapi-all.c > will be defined - kernel option, autodetection or > device flag? For now kernel options, later auto for ISA & 486 arch machines.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 13:55: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 8347114C92 for ; Mon, 11 Oct 1999 13:54:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id NAA08807; Mon, 11 Oct 1999 13:54:38 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199910112054.NAA08807@rah.star-gate.com> To: Jeroen Ruigrok/Asmodai Cc: Amancio Hasty , freebsd-current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: 3dfx Driver? In-reply-to: Your message of "Mon, 11 Oct 1999 21:48:28 +0200." <19991011214828.F9737@daemon.ninth-circle.org> Date: Mon, 11 Oct 1999 13:54:38 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't have much time now days to volunteer due to work overload. If I get a chance one of these nights I will port it. My focus is to provide decent X video support appropiate for h.261 , h.263 , and mpeg -- which basically entails yuv + scaling hardware assist. In other words 3dfx is a secondary issue. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 14:26:29 1999 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 4583E15A46 for ; Mon, 11 Oct 1999 14:26:17 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA86724; Mon, 11 Oct 1999 17:26:09 -0400 (EDT) (envelope-from wollman) Date: Mon, 11 Oct 1999 17:26:09 -0400 (EDT) From: Garrett Wollman Message-Id: <199910112126.RAA86724@khavrinen.lcs.mit.edu> To: Andre Oppermann Cc: Alex , freebsd-current@FreeBSD.ORG Subject: Re: MajorDomo Problems In-Reply-To: <3801A777.7F31D00@pipeline.ch> References: <3.0.3.32.19991010215737.00acd374@mail.embt.com> <38016E09.61B8A064@freenet.co.uk> <3801A777.7F31D00@pipeline.ch> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > majordomo is crap it seems, the freebsd mailing lists should switch > over to ezmlm-idx/qmail... *THAT* works 100% reliable. Bull$#!^. I run a couple of fairly large mailing-lists under majordomo, and nobody ever gets ``accidentally'' unsubscribed. On the other hand, quite a few people suddenly start bouncing their mail and get *intentionally* unsubscribed (by me). We have appointed jmb as postmaster, and so long as he has that job, the list management will be done using whatever mechanisms he deems appropriate. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 14:36:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1695A14C5A for ; Mon, 11 Oct 1999 14:36:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA22073; Mon, 11 Oct 1999 23:35:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: Andre Oppermann , Alex , freebsd-current@FreeBSD.ORG Subject: Re: MajorDomo Problems In-reply-to: Your message of "Mon, 11 Oct 1999 17:26:09 EDT." <199910112126.RAA86724@khavrinen.lcs.mit.edu> Date: Mon, 11 Oct 1999 23:35:08 +0200 Message-ID: <22071.939677708@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910112126.RAA86724@khavrinen.lcs.mit.edu>, Garrett Wollman writes: > >We have appointed jmb as postmaster, and so long as he has that job, >the list management will be done using whatever mechanisms he deems >appropriate. Amen! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 14:43:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id 1549215224 for ; Mon, 11 Oct 1999 14:43:55 -0700 (PDT) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id OAA08646 for freebsd-current@freebsd.org; Mon, 11 Oct 1999 14:43:36 -0700 (PDT) (envelope-from freebsd) Posted-Date: Mon, 11 Oct 1999 14:43:36 -0700 (PDT) Message-Id: <199910112143.OAA08646@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Mon, 11 Oct 1999 14:43:36 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: World fail + resulting cvsup failures Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After an attempt to build world failed early this morning after a cvsup, I can neither resolve the world problem, nor can I cvsup. World failure: ===> usr.bin/kdump cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c In file included from :45: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c In file included from ioctl.c:65: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition ioctl.c: In function `ioctlname': ioctl.c:353: sizeof applied to an incomplete type ioctl.c:617: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Now, certainly this is unrelated to cvsup failing, however something else in the build must have caused the following: mrynet# cvsup *** *** runtime error: *** Segmentation violation - possible attempt to dereference NIL *** pc = 0x2f *** Abort trap A reboot has effected no change in this behavior. An attempt to reinstall modula from ports results in: ---------------------- building m3core ---------------------- mkdir FreeBSD2 --- building in FreeBSD2 --- m3 -w1 -why -O -times -a libm3core.a -F/var/tmp/qkAK8630 *** *** runtime error: *** Segmentation violation - possible attempt to dereference NIL *** pc = 0x2f *** Abort trap *** error code 134 (ignored) So, the problem lies in Modula 3. I'm at a total stalemate now. Has anyone experienced this? All (constructive :P) suggestions hearily welcomed :D Cheers, -skots -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@mrynet.lv (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 15: 4:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from outreach.wolfnet.org (CBL-jkfritcher1.hs.earthlink.net [207.217.155.123]) by hub.freebsd.org (Postfix) with ESMTP id 8A7DE157B3 for ; Mon, 11 Oct 1999 15:04:27 -0700 (PDT) (envelope-from jkf@wolfnet.org) Received: from solaris.wolfnet.org ([10.0.0.3]) by outreach.wolfnet.org with esmtp (Exim 3.03 #1) id 11anYL-000B85-00 for current@freebsd.org; Mon, 11 Oct 1999 15:04:21 -0700 Date: Mon, 11 Oct 1999 15:04:21 -0700 (PDT) From: "Jason K. Fritcher" To: current@freebsd.org Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <199910111938.MAA00607@kithrup.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 Mon, 11 Oct 1999, Sean Eric Fagan wrote: > In article <19991012082903.A4298.kithrup.freebsd.current@patho.gen.nz> you write: > Whatever method he is using is not working very well, and it has not worked > very well for a very long time. I must say that Jonathan has been more than fair. About a year, maybe a year and a half ago, I didn't have a dedicated connection, and was doing smtp on demand, with my ISP spooling mail for me when I wasn't online. On average, I would get approximate, 20-30 messages during the night while I was offline, and twice a night, for each message, my ISP would send a message back to freebsd.org saying that the messages were still sitting in a queue waiting to be delivered. So for a period of a couple months, he put up with an average of ~50/day messages saying that my mail hadn't been delivered yet. Personally I was suprised I wasn't killed after the first week. Needless to say, I am happy now that my mail server is on a dedicated link. Great work Jonathan! -- Jason K. Fritcher jkf@wolfnet.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 18:40:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9]) by hub.freebsd.org (Postfix) with SMTP id 0B9A515810 for ; Mon, 11 Oct 1999 18:40:15 -0700 (PDT) (envelope-from spock@techfour.net) Received: (qmail 151 invoked from network); 12 Oct 1999 01:40:14 -0000 Received: from cm-208-138-197-238.fredericksburg.mg.ispchannel.com (HELO enterprise.muriel.penguinpowered.com) (208.138.197.238) by mail001.mediacity.com with SMTP; 12 Oct 1999 01:40:14 -0000 Content-Length: 2005 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910112143.OAA08646@mrynet.com> X-SENDERNAME: `Mike Heffner` Date: Mon, 11 Oct 1999 21:40:55 -0400 (EDT) From: Mike Heffner To: (FreeBSD mailing list) Subject: RE: World fail + resulting cvsup failures Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Oct-99 FreeBSD mailing list wrote: > After an attempt to build world failed early this morning after a > cvsup, I can neither resolve the world problem, nor can I cvsup. > > World failure: > > ===> usr.bin/kdump > cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. > -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c > /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c > In file included from :45: > /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' > redefined > /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the > location of the previous definition > cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. > -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c > In file included from ioctl.c:65: > /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' > redefined > /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the > location of the previous definition > ioctl.c: In function `ioctlname': > ioctl.c:353: sizeof applied to an incomplete type > ioctl.c:617: sizeof applied to an incomplete type > *** Error code 1 > > Stop in /usr/src/usr.bin/kdump. > *** Error code 1 > i just sent a message to the list about this, "make buildworld dies in usr.bin/kdump (fix)" here's the patch i included in that message: --- usr.bin/kdump/mkioctls.old Mon Oct 11 11:41:27 1999 +++ usr.bin/kdump/mkioctls Mon Oct 11 10:46:17 1999 @@ -35,6 +35,7 @@ print "#include " print "#include " print "#include " + print "#include " print "#include " print "#include " print "" the rest of your problems I don't know anything about ;) --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 11-Oct-99 Time: 21:38:32 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 19:36: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 2E9DD14D4D for ; Mon, 11 Oct 1999 19:35:58 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id JAA01281; Tue, 12 Oct 1999 09:35:42 +0700 (NOVST) (envelope-from nnd) Date: Tue, 12 Oct 1999 09:35:42 +0700 (NOVST) Message-Id: <199910120235.JAA01281@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: kernel broken? (pcm) In-Reply-To: <199910111931.VAA52411@work.net.local> User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199910111931.VAA52411@work.net.local> A.Leidinger@wjpserver.cs.uni-sb.de wrote: Such an errors results from (uncommented) kernel option #makeoptions CONF_CFLAGS=-fno-builtin because there is NO 'abs' function/macro in this files (ac97.c, channel.c and mss.c) and they can be only compiled using gcc's builtin 'abs' N.Dudorov > Hi, > > linking kernel.debug > ac97.o: In function `ac97_setmixer': > /usr/src/sys/compile/WORK/../../dev/pcm/ac97.c(.text+0x18d): undefined reference to `abs' > channel.o: In function `chn_setblocksize': > /usr/src/sys/compile/WORK/../../dev/pcm/channel.c:712: undefined reference to `abs' > mss.o: In function `mss_speed': > /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x182d): undefined reference to `abs' > /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x183f): undefined reference to `abs' > /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x1869): undefined reference to `abs' > mss.o(.text+0x187b):/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c: more undefined references to `abs' follow > *** Error code 1 > 1 error > > I tried several cvsups since the morning. > > Kernelconfig attached. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 19:38:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id BE9EA1532E for ; Mon, 11 Oct 1999 19:38:14 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 896B21C29; Mon, 11 Oct 1999 21:41:17 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 849603817; Mon, 11 Oct 1999 21:41:17 -0400 (EDT) Date: Mon, 11 Oct 1999 21:41:17 -0400 (EDT) From: Bill Fumerola To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: kernel broken? (pcm) In-Reply-To: <199910120235.JAA01281@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999 nnd@mail.nsk.ru wrote: > In <199910111931.VAA52411@work.net.local> A.Leidinger@wjpserver.cs.uni-sb.de wrote: > Such an errors results from (uncommented) kernel option > > #makeoptions CONF_CFLAGS=-fno-builtin We have enough breakages with the _documented_ kernel options that we don't need to go hunting down oddities. :> -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Oct 11 19:57:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id DEE5F14BF9 for ; Mon, 11 Oct 1999 19:57:32 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id JAA80657; Tue, 12 Oct 1999 09:57:14 +0700 (NOVST) (envelope-from nnd) Date: Tue, 12 Oct 1999 09:57:14 +0700 (NOVST) Message-Id: <199910120257.JAA80657@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: kernel broken? (pcm) In-Reply-To: User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Bill Fumerola wrote: > On Tue, 12 Oct 1999 nnd@mail.nsk.ru wrote: > >> In <199910111931.VAA52411@work.net.local> A.Leidinger@wjpserver.cs.uni-sb.de wrote: >> Such an errors results from (uncommented) kernel option >> >> #makeoptions CONF_CFLAGS=-fno-builtin > > We have enough breakages with the _documented_ kernel options that we > don't need to go hunting down oddities. :> Does it mean that I throw away my PR with patches to the 'newpcm' files which add 'abs' definition and therefore make it possible to make kernel with makeoptions CONF_CFLAGS=-fno-builtin ? P.S. It seems to me that this option (or its absent) can severely influence kernel run time efficience (not in the 'abs' case, of course ;-). N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 19:59:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id CDB7514BF9 for ; Mon, 11 Oct 1999 19:59:54 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id C5C2C1C29; Mon, 11 Oct 1999 22:02:57 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id C0EC13817; Mon, 11 Oct 1999 22:02:57 -0400 (EDT) Date: Mon, 11 Oct 1999 22:02:57 -0400 (EDT) From: Bill Fumerola To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: kernel broken? (pcm) In-Reply-To: <199910120257.JAA80657@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999 nnd@mail.nsk.ru wrote: > > We have enough breakages with the _documented_ kernel options that we > > don't need to go hunting down oddities. :> > > Does it mean that I throw away my PR with patches to > the 'newpcm' files which add 'abs' definition and therefore > make it possible to make kernel with > > makeoptions CONF_CFLAGS=-fno-builtin ? > > P.S. It seems to me that this option (or its absent) can > severely influence kernel run time efficience (not in the 'abs' > case, of course ;-). No. I was merely joking around. We welcome your patches. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Oct 11 20: 1: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2EA1F14BF9 for ; Mon, 11 Oct 1999 20:00:58 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11asBO-0005sN-00 for freebsd-current@freebsd.org; Mon, 11 Oct 1999 20:00:58 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: fpu_aux.c - new breakage? Message-Id: Date: Mon, 11 Oct 1999 20:00:58 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so i went to build yet again to see if i could get the three headed dog to walk again, and whammy! randy cc -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/gnufpu -I/usr/obj/usr/src/sys/modules/gnufpu/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/errors.c cc -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/gnufpu -I/usr/obj/usr/src/sys/modules/gnufpu/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_arith.c cc -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/gnufpu -I/usr/obj/usr/src/sys/modules/gnufpu/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_aux.c /usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_aux.c: In function `fstsw_ax': /usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_aux.c:118: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/src/sys/modules/gnufpu. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 20: 1:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from nwcst323.netaddress.usa.net (nwcst323.netaddress.usa.net [204.68.23.68]) by hub.freebsd.org (Postfix) with SMTP id 4476415778 for ; Mon, 11 Oct 1999 20:01:16 -0700 (PDT) (envelope-from mapacheco@usa.net) Received: (qmail 377 invoked by uid 60001); 6 Oct 1999 18:35:49 -0000 Message-ID: <19991006183549.376.qmail@nwcst323.netaddress.usa.net> Received: from 204.68.23.68 by nwcst323 for [24.218.36.165] via web-mailer(MaintM3.3.0.77) on Wed Oct 6 18:35:49 GMT 1999 Date: 6 Oct 99 14:35:49 EDT From: Michael A.Pacheco To: current@freebsd.org Subject: PCM Failure in 4.0-current X-Mailer: USANET web-mailer (MaintM3.3.0.77) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to get my sound card to work for some time now. After reading quite a few messages from the freebsd-current mailing list I got it to an= almost working condition, but it's still not working... --In the kernel I have--: controller pnp0 device pcm0 --dmesg--: pcm0: at port 0x220-0x22f,0x388-0x38b,0x100-0x10f irq 5 drq 1,0 on isa0 unknown0: at port 0x300-0x301 irq 9 on isa0 unknown1: at port 0x200-0x207 on isa0 ---------- --sndstat--: FreeBSD Audio Driver(newpcm) Oct 4 1999 22:09:04 Installed Devices: pcm0: at io 0x220 irq 5 drq 1:0 (1/1 channe= ls duplex) --------- When I try to play any type of sound (i.e.: cat whatever.au > /dev/audio)= I get this error: start dma, failed to set bit 0xfe 0xff Do you have any idea what could be causing this? It's also kinda strange = how it detects it as a Terratec Soundsystem when the card's an Analog Devices= AD1816. Any help would be appreciated, I still lack any freebsd machine with soun= d ;). -Thanks in Advance Michael A. Pacheco ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 20: 4:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id E7FD814BF9 for ; Mon, 11 Oct 1999 20:04:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA03678; Mon, 11 Oct 1999 19:56:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910120256.TAA03678@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randy Bush Cc: FreeBSD Current Subject: Re: fpu_aux.c - new breakage? In-reply-to: Your message of "Mon, 11 Oct 1999 20:00:58 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 19:56:49 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > so i went to build yet again to see if i could get the three headed dog to > walk again, and whammy! I just fixed some of it, Bruce found some more. Poul has been committing without testing again. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 20:18: 6 1999 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 A9897152C4 for ; Mon, 11 Oct 1999 20:17:49 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d191.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id NAA20390; Tue, 12 Oct 1999 13:19:42 +1000 Date: Tue, 12 Oct 1999 13:17:12 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: kernel broken? (pcm) In-Reply-To: <199910120235.JAA01281@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999 nnd@mail.nsk.ru wrote: > In <199910111931.VAA52411@work.net.local> A.Leidinger@wjpserver.cs.uni-sb.de wrote: > Such an errors results from (uncommented) kernel option > > #makeoptions CONF_CFLAGS=-fno-builtin This option is used in LINT to help expose such errors before they are committed. > because there is NO 'abs' function/macro in this files > (ac97.c, channel.c and mss.c) and they can be only compiled using > gcc's builtin 'abs' abs() doesn't exist in the kernel, so it shouldn't be used. > > linking kernel.debug > > ac97.o: In function `ac97_setmixer': > > /usr/src/sys/compile/WORK/../../dev/pcm/ac97.c(.text+0x18d): undefined reference to `abs' > > channel.o: In function `chn_setblocksize': Test coverage of pcm in LINT is broken by not configuring pcm because of conflicts with the old sound drivers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 20:39:47 1999 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 687AB155B5 for ; Mon, 11 Oct 1999 20:39:43 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d191.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id NAA22053; Tue, 12 Oct 1999 13:41:58 +1000 Date: Tue, 12 Oct 1999 13:39:28 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: kernel broken? (pcm) In-Reply-To: <199910120257.JAA80657@wint.itfs.nsk.su> 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 > >> Such an errors results from (uncommented) kernel option ^^^^^^^^^^^ > >> > >> #makeoptions CONF_CFLAGS=-fno-builtin > > > > We have enough breakages with the _documented_ kernel options that we ^^^^^^^^^^^^ > > don't need to go hunting down oddities. :> It's well documented. -fno-builtin is a standard gcc option, and CONF_FLAGS and its use of -fno-builtin is documented in 4 lines in LINT. > Does it mean that I throw away my PR with patches to > the 'newpcm' files which add 'abs' definition and therefore > make it possible to make kernel with > > makeoptions CONF_CFLAGS=-fno-builtin ? No, some patches are needed. I think pcm should use explicit code like (x < 0 : -x : x). It only calls abs() twice. > P.S. It seems to me that this option (or its absent) can > severely influence kernel run time efficience (not in the 'abs' > case, of course ;-). I used to use it for all kernels as a side effect of putting it in /etc/make.conf so that it gets used for LINT. Any efficiency effects seem to be limited to the +-0.1% range. The only place where it is likely to make much difference is for bcopy() vs memcpy() on some machines. The builtin memcpy() can be pessimal. This is supposed to be handled by using bcopy() for large copies and memcpy() (only) for small, fix-sized copies. The builtin memcpy() tends to be better for small copies. Since using memcpy() in the kernel is correct in some cases, it is backed up by a function to handle cases where there is no inline memcpy(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 11 21:31:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 601AB15087 for ; Mon, 11 Oct 1999 21:31:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA15648; Mon, 11 Oct 1999 21:31:42 -0700 Date: Mon, 11 Oct 1999 21:31:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andy Farkas Cc: freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update 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 This is a harmless message for the moment. I took a look at the new make_dev stuff- it's more than a no-brainer to add because there's a lot of stuff about supported device nodes, etc... I'll try and get back to this after FreeBSDcon. On Sun, 10 Oct 1999, Andy Farkas wrote: > > Just a reminder I guess, > > # uname -v > FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 > > # mt retension > > console emits (in bright white): > > WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") > > > > -- > > :{ andyf@speednet.com.au > > Andy Farkas > System Administrator > Speednet Communications > http://www.speednet.com.au/ > > > > > > 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 Oct 11 21:34:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 241061518F; Mon, 11 Oct 1999 21:34:45 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA88716; Tue, 12 Oct 1999 01:34:44 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 12 Oct 1999 01:34:44 -0300 (ADT) From: The Hermit Hacker To: "Jonathan M. Bresler" Cc: nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991011174430.2B133153CB@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Oct 1999, Jonathan M. Bresler wrote: > when the MTA gives up trying to deliver the mail, i call it > bounced. so a 500 series error from the other MTA means the email has > bounced. Have you considered using bouncefilter for this? I'm using it for the PostgreSQL mailnig lists, and find its really cut down on my requirement to intervene on 'dead addresses'... 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 Mon Oct 11 21:48:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1668415158 for ; Mon, 11 Oct 1999 21:48:52 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id VAA02093 for ; Mon, 11 Oct 1999 21:48:51 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199910120448.VAA02093@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: May 99 Snapshot and -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 21:48:50 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Got a new disk and I am trying to upgrade from the May 1999 snapshot to today's current. I recompiled the kernel , install it and reboot afterwards the boot loader fails to load the new kernel so should I upgrade my boot blocks with the latest sources? Tnks -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 0: 1:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from gwythaint.ntanet.net (c61096-a.almda1.sfba.home.com [24.0.81.208]) by hub.freebsd.org (Postfix) with ESMTP id 214CB14A2F; Tue, 12 Oct 1999 00:01:17 -0700 (PDT) (envelope-from daveh@ntanet.net) Received: from gwythaint.ntanet.net (localhost [127.0.0.1]) by gwythaint.ntanet.net (8.9.2/8.9.2) with ESMTP id AAA07476; Tue, 12 Oct 1999 00:01:16 -0700 (PDT) (envelope-from daveh@ntanet.net) Message-Id: <199910120701.AAA07476@gwythaint.ntanet.net> To: dg@freebsd.org From: David Holloway Cc: freebsd-current@freebsd.org, freebsd-hardware@freebsd.org, toddpw@wrs.com Subject: 82559 information Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Tue, 12 Oct 1999 00:01:16 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To David Greenman or.. whoever is maintaining if_fxp.c I picked up an 82559 card from compusa today... Guess what?! It's device id was 0x1030 instead of 0x1229. I adjusted my driver to match and it seems to work fine. Of course, I haven't tried it yet with FreeBSD. (I was using vxWorks.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 1:46:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id C5D9E15089 for ; Tue, 12 Oct 1999 01:46:35 -0700 (PDT) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999070600) with ESMTP id KAA13455; Tue, 12 Oct 1999 10:45:59 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id KAA04830; Tue, 12 Oct 1999 10:45:59 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:O3qJ2GZE+yI5rHIBSxqQLY6UYfGVg7hi@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/8.9.1/wjp-SVR4/1998063000) with ESMTP id KAA15936; Tue, 12 Oct 1999 10:45:54 +0200 (CEST) Message-Id: <199910120845.KAA15936@wurzelausix.cs.uni-sb.de> Date: Tue, 12 Oct 1999 10:45:52 +0200 (CEST) From: Alexander Leidinger Subject: Re: kernel broken? (pcm) To: billf@jade.chc-chimes.com Cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Oct, Bill Fumerola wrote: >> #makeoptions CONF_CFLAGS=-fno-builtin > > We have enough breakages with the _documented_ kernel options that we As Bruce Evans already said, It's documented. > don't need to go hunting down oddities. :> Have you seen the '#' in "#makeoptions"? I assume a '#' in the config file means: "Hey config, don't look at this!". Please correct me if I'm wrong. I've tested both variants with and without '#'. After editing the file I did a 'config -r CONFIG', 'cd ../../compile/CONFIG', 'make depend', 'make'. I get the error independently of CONF_FLAGS. Back at home I do it again if you want. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 2: 2:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.lndn.tensor.pgs.com (titan.lndn.tensor.pgs.com [157.147.162.51]) by hub.freebsd.org (Postfix) with ESMTP id E771315015 for ; Tue, 12 Oct 1999 02:02:35 -0700 (PDT) (envelope-from shocking@dhcp160-32.lndn.tensor.pgs.com) Received: from dhcp160-32.lndn.tensor.pgs.com (dhcp160-32 [157.147.160.32]) by titan.lndn.tensor.pgs.com (8.9.1a/8.9.1) with ESMTP id KAA29671; Tue, 12 Oct 1999 10:02:16 +0100 (BST) Received: from dhcp160-32.lndn.tensor.pgs.com (localhost [127.0.0.1]) by dhcp160-32.lndn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id KAA07973; Tue, 12 Oct 1999 10:04:25 +0100 Message-Id: <199910120904.KAA07973@dhcp160-32.lndn.tensor.pgs.com> X-Mailer: exmh version 2.0.2 To: current@freebsd.org Cc: asmodai@wxs.nl, hasty@rah.star-gate.com Subject: Re: 3dfx Driver? In-Reply-To: Your message of "Tue, 12 Oct 1999 01:47:01 PDT." Reply-To: shocking@prth.pgs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Oct 1999 10:04:24 +0100 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Has anyone ported the linux 3DFx Driver to FreeBSD? > >Don't think so. > >Why? You volunteering? =) I made a start on it earlier this year, but the final step (mapping the card memory) I got wrong, which then locked up the machine. The box the code is on is the other side of the world at the moment unfortunately. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 4:22:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id ED6BC14DD5 for ; Tue, 12 Oct 1999 04:22:14 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id SAA00271; Tue, 12 Oct 1999 18:21:52 +0700 (NOVST) (envelope-from nnd) Date: Tue, 12 Oct 1999 18:21:52 +0700 (NOVST) Message-Id: <199910121121.SAA00271@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: kernel broken? (pcm) In-Reply-To: <199910120845.KAA15936@wurzelausix.cs.uni-sb.de> User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199910120845.KAA15936@wurzelausix.cs.uni-sb.de> Alexander Leidinger wrote: > On 11 Oct, Bill Fumerola wrote: > >>> #makeoptions CONF_CFLAGS=-fno-builtin >> >> We have enough breakages with the _documented_ kernel options that we > > As Bruce Evans already said, It's documented. > >> don't need to go hunting down oddities. :> > > Have you seen the '#' in "#makeoptions"? I assume a '#' in the config > file means: "Hey config, don't look at this!". Please correct me if I'm > wrong. > > I've tested both variants with and without '#'. After editing the file I > did a 'config -r CONFIG', 'cd ../../compile/CONFIG', 'make depend', > 'make'. I get the error independently of CONF_FLAGS. > Back at home I do it again if you want. Yes, in your case the errors are independent from this "makeoptions ..." line. But you are linking kernel.debug, so the (undefined in kernel) 'abs' function shows itself. You can try the patch in (my) PR 'kern/14278'. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 6:56:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 6899415A8A for ; Tue, 12 Oct 1999 06:56:44 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id PAA29307; Tue, 12 Oct 1999 15:56:42 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id D5A3BD246; Tue, 12 Oct 1999 15:56:40 +0200 (CEST) Message-ID: <19991012155640.A448@enst.fr> Date: Tue, 12 Oct 1999 15:56:40 +0200 From: Pierre Beyssac To: Bill Paul , current@FreeBSD.ORG Subject: Re: Still waiting for xl driver reports References: <199910102059.QAA24189@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199910102059.QAA24189@skynet.ctr.columbia.edu>; from Bill Paul on Sun, Oct 10, 1999 at 04:59:34PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 10, 1999 at 04:59:34PM -0400, Bill Paul wrote: > A while back I posted a message here saying that I'd changed the xl driver > a bit to hopefully improve performance for 3c90xB and later adapters (i.e. > the "cyclone," "hurricane" and "tornado" chipsets). I asked for people > to report if the changes helped, hurt, made no difference or were totally > broken. > > So far not one person has said so much as a word to me on this subject. I use the xl device (two cards: xl0 and xl1) in my kernel (compiled on October 4th) and hadn't realized I was using the new driver. I only noticed weird things last Sunday when the interface hung while I was trying a tcpdump on it (I was loggued remotely, which explains why I saw the problem immediately)... Then there was a "xl1: watchdog timeout" and things went back to normal. I compiled today's kernel to see if it made any difference, and I can confirm I can repeat it easily you wish. The watchdog timeout seems to happen every time I get out of promiscuous mode, and (very seldom) at other random moments. > To reiterate, this only concerns people with the following adapters: Here's what I have: xl0: <3Com 3c900-COMBO Etherlink XL> irq 11 at device 10.0 on pci2 xl0: Ethernet address: 00:10:5a:bf:13:96 xl0: selecting 10baseT transceiver, half duplex xl1: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 17.0 on pci0 xl1: Ethernet address: 00:c0:4f:67:0b:82 It's on xl1 that I have problems, although I'm not sure this wouldn't happen on xl0 too (xl0 is configured down at the moment). Now regarding performance, I haven't made extensives tests. The closest thing to that that I have in mind is to stretch that 2*100Mbps trunking link we configured this morning between two of our ethernet switches :-) -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 7:25:23 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 57A98152AF; Tue, 12 Oct 1999 07:25:22 -0700 (PDT) From: "Jonathan M. Bresler" To: scrappy@hub.org Cc: nate@mt.sri.com, current@FreeBSD.ORG In-reply-to: (message from The Hermit Hacker on Tue, 12 Oct 1999 01:34:44 -0300 (ADT)) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991012142522.57A98152AF@hub.freebsd.org> Date: Tue, 12 Oct 1999 07:25:22 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for the note on bouncefilter. i'll take a look at it. may be just what i am looking for.. may be better than what i am using already. always interested in somethatngthat will help me do this better. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 7:31:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 5621C152AF for ; Tue, 12 Oct 1999 07:31:29 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id QAA6181304; Tue, 12 Oct 1999 16:30:59 +0200 (CST) Received: from work.net.local (maxtnt-065.telip.uni-sb.de [134.96.70.192]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id QAA14777; Tue, 12 Oct 1999 16:30:45 +0200 (CST) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id QAA00820; Tue, 12 Oct 1999 16:30:36 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199910121430.QAA00820@work.net.local> Date: Tue, 12 Oct 1999 16:30:35 +0200 (CEST) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: Re: kernel broken? (pcm) To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG In-Reply-To: <199910121121.SAA00271@wint.itfs.nsk.su> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Okt, nnd@mail.nsk.ru wrote: > You can try the patch in (my) PR 'kern/14278'. Works. Bye, Alexander. -- What do you mean, my birth certificate expired? http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 8: 3:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id A651E15A57 for ; Tue, 12 Oct 1999 08:03:35 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial12-174.netcologne.de [194.8.196.174]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id RAA16117; Tue, 12 Oct 1999 17:03:32 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id RAA02057; Tue, 12 Oct 1999 17:03:54 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Tue, 12 Oct 1999 17:03:54 +0200 (CEST) Message-Id: <199910121503.RAA02057@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-current@freebsd.org Subject: Proper Whacking & Weeding Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It took me some fiddling to get a -current system from begin of September to build present -current. To achieve this, among other things, I cleaned up. That box is building from source for over two years now, and there were quite a lot of old files in the directory hierarchy. From rotten headers in /usr/include and strange libs in /usr/lib (libtermcap.so.2?) to strange locale stuff in /usr/share/misc However I might have whacked a bit too much, as Emacs (both 19 and 20) display is messed up in textmode. vi and sysinstall however work. And under X emacs still works. Anyone has an idea what could be wrong? More systematically: Is there a way to ensure that /usr/include, /usr/share/.. and such are rebuilt properly? (No files missing, no old files messing things up) Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 8: 8:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 91E4715182 for ; Tue, 12 Oct 1999 08:08:50 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id LAA44474 for current@freebsd.org; Tue, 12 Oct 1999 11:08:50 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <199910121508.LAA44474@blackhelicopters.org> Subject: Request for Flames To: current@freebsd.org Date: Tue, 12 Oct 1999 11:08:50 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (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 Folks, I'm writing a series of web pages on how to ask for help on the FreeBSD mailing lists. From time to time, some innocent newbie wanders in here asking a question with far too little information. ("CVSup/pn0/sio.c doesn't work. Why not?") On occasion, you folks have taken the time to write detailed notes describing the exact information you need to solve these problems. (On other occasions, said newbie is seen around town: a little bit here, a little bit there... but that's another problem.) I'me searched the mail archives looking for these messages, and am having difficulty finding them. (It's difficult to search for "That message where Bill Paul told a newbie in excruciating detail what he needed to fix the problem, and what would happen to the next newbie who asked this question without providing this information.") Lots of questions, very few detailed answers. If any of you have copies of messages that you have previously sent, describing what information you need to solve a particular problem, I would appreciate it if you would forward these to me. I'll use this information to write another guide. For an example of what I'm trying to do, take a look at: http://www.blackhelicopters.org/~dispatch/report/nic.html My eventual goal is to have something like this for every troublesome part of the system. Hopefully newbies will either read these and give the proper information, or go away and leave us alone. ;) Thanks, ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 8:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id BCCCA15AF0; Tue, 12 Oct 1999 08:58:38 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt11.keycomp.net [207.44.1.13]) by www.keycomp.net (8.8.5/SCO5) with SMTP id MAA26516; Tue, 12 Oct 1999 12:05:15 -0400 (EDT) Message-ID: <000701bf14ca$9f666360$01010101@bopper> From: "Bill A. K." To: "FreeBSD Questions" , Subject: Linux X Server Date: Tue, 12 Oct 1999 11:58:25 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm trying to run the Voodoo Banshee server from Creative Labs. The reason I'm trying to do this is because when I run XFree86 3.3.5, it screws up my console display when I exit X. The Linux Server is looking to open /dev/tty9 and it can't. I tried putting a hard link from /dev/tty9 to /dev/ttyv9 but when i started X it paniced the kernel :) Is there any way first of all to fix 3.3.5 to work, and if not, to get the Linux server to work? Is there any way to somehow mimic /dev/tty9 for it? I'm running 4.0-CURRENT, and the console garble thing also happened on 3.2-RELEASE Thanks in advance for your help. Bill billieakay@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9: 0:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n66.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id E3E7015B7A; Tue, 12 Oct 1999 09:00:11 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n66.san.rr.com (8.9.3/8.8.8) with ESMTP id IAA24959; Tue, 12 Oct 1999 08:59:57 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <38035AFD.2C647063@gorean.org> Date: Tue, 12 Oct 1999 08:59:57 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch References: <199910111653.JAA57276@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > > > > > > > "Accidental" removals from the lists are so common that I give up. I no > > > longer even try to get back on them -- it's been happening for _years_ now, > > > and I have made multiple complaints about it, and if it's not a problem for > > > whoever runs the mailing lists, then I just don't care that much. > > > > only one comment. i remove people from the lists whenever > > their email bounces. the threshhold is approximately 30 messages in a > > 24 hour period. mail may bounce due to DNS problems, mail box full, > > MTA misconfiguration. i also remove people that send vacation > > messages to the list. oh, and spammers. > > Perhaps these threshholds could use some minor adjustments, or perhaps > my interpretation of the above policy is not quite what really happens. Having been in a situation similar to Jonathan's (managing a large site, many lists, thousands of users) I can only say that it's hard to appreciate the difficulty of the task without experiencing it. I think he does a fine job, extending people more patience than I used to. :) Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9: 3:38 1999 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 6B24C15D60 for ; Tue, 12 Oct 1999 09:03:33 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA13151; Wed, 13 Oct 1999 01:03:19 +0900 (JST) Message-ID: <38033450.D94530B4@newsguy.com> Date: Tue, 12 Oct 1999 22:14:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Jason K. Fritcher" Cc: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jason K. Fritcher" wrote: > > I must say that Jonathan has been more than fair. About a year, maybe a year > and a half ago, I didn't have a dedicated connection, and was doing smtp on > demand, with my ISP spooling mail for me when I wasn't online. On average, I > would get approximate, 20-30 messages during the night while I was offline, > and twice a night, for each message, my ISP would send a message back to > freebsd.org saying that the messages were still sitting in a queue waiting > to be delivered. So for a period of a couple months, he put up with an > average of ~50/day messages saying that my mail hadn't been delivered yet. > Personally I was suprised I wasn't killed after the first week. Interestingly, I used to have problems once. My provider had a problem in which it's users would stop being recognized at times, resulting in 5xx messages. It would last only a few minutes (well, it could last longer at night), but it would happen again and again throughout the day, which, I guess, generates the pattern that leads jmb to unsubscribe people. The funny thing is... the problem happened because of a bug on FreeBSD's nis. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9: 4:11 1999 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 ED85615E31 for ; Tue, 12 Oct 1999 09:04:01 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA13241; Wed, 13 Oct 1999 01:03:44 +0900 (JST) Message-ID: <380339AA.FB0D5719@newsguy.com> Date: Tue, 12 Oct 1999 22:37:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: mjacob@feral.com Cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > This is a harmless message for the moment. I took a look at the new > make_dev stuff- it's more than a no-brainer to add because there's a lot > of stuff about supported device nodes, etc... I'll try and get back to > this after FreeBSDcon. Funny, phk's comments led me to believe it's actually easier to use make_dev() (!= makedev(), btw -- maybe you looked up the wrong one?). And, talking about phk, it is also my impression that it is his intent to push these changes as fast as he can. He gets strange at this time of the year, y'know... I think Jordan once posted an interesting explanation for this phenomenum. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9:13:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 7236414FFB; Tue, 12 Oct 1999 09:13:28 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id JAA26544; Tue, 12 Oct 1999 09:13:13 -0700 (PDT) X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Tue, 12 Oct 1999 09:13:13 -0700 (PDT) From: Brooks Davis X-Sender: brdavis@orion.ac.hmc.edu To: David Holloway Cc: dg@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, toddpw@wrs.com Subject: Re: 82559 information In-Reply-To: <199910120701.AAA07476@gwythaint.ntanet.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 Tue, 12 Oct 1999, David Holloway wrote: > To David Greenman or.. whoever is maintaining if_fxp.c > I picked up an 82559 card from compusa today... > Guess what?! It's device id was 0x1030 instead of 0x1229. > > I adjusted my driver to match and it seems to work fine. Support was added in -current Sept 6. It appears that no one has back ported it yet. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9:47:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9A99614C35 for ; Tue, 12 Oct 1999 09:47:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA25234; Tue, 12 Oct 1999 18:45:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: mjacob@feral.com, Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-reply-to: Your message of "Tue, 12 Oct 1999 22:37:46 +0900." <380339AA.FB0D5719@newsguy.com> Date: Tue, 12 Oct 1999 18:45:48 +0200 Message-ID: <25232.939746748@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <380339AA.FB0D5719@newsguy.com>, "Daniel C. Sobral" writes: >Matthew Jacob wrote: >> >> This is a harmless message for the moment. I took a look at the new >> make_dev stuff- it's more than a no-brainer to add because there's a lot >> of stuff about supported device nodes, etc... I'll try and get back to >> this after FreeBSDcon. > >Funny, phk's comments led me to believe it's actually easier to use >make_dev() (!= makedev(), btw -- maybe you looked up the wrong >one?). > >And, talking about phk, it is also my impression that it is his >intent to push these changes as fast as he can. He gets strange at >this time of the year, y'know... I think Jordan once posted an >interesting explanation for this phenomenum. :-) "This time of the year" == "This time in the release cycle" If we want to have a somewhat clean line before 4.0 now is the time to push it through, not after the code freeze. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9:48:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B11E515AAF for ; Tue, 12 Oct 1999 09:47:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA18728; Tue, 12 Oct 1999 09:47:34 -0700 Date: Tue, 12 Oct 1999 09:47:34 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Daniel C. Sobral" Cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-Reply-To: <380339AA.FB0D5719@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 Tue, 12 Oct 1999, Daniel C. Sobral wrote: > Matthew Jacob wrote: > > > > This is a harmless message for the moment. I took a look at the new > > make_dev stuff- it's more than a no-brainer to add because there's a lot > > of stuff about supported device nodes, etc... I'll try and get back to > > this after FreeBSDcon. > > Funny, phk's comments led me to believe it's actually easier to use > make_dev() (!= makedev(), btw -- maybe you looked up the wrong > one?). No- it's easy to use but it requires thinking about all the minors you want to use and what max sizes, etc. I mean, yes, I could move it along and just delta the changes, but if it can wait a few weeks so I can actually finish off the media detection at open and the persistent density properties (which *would* have an impact about minors), I'd like to do it. The current D_NAG doesn't stop you from using the tape device, does it? > > And, talking about phk, it is also my impression that it is his > intent to push these changes as fast as he can. He gets strange at > this time of the year, y'know... I think Jordan once posted an > interesting explanation for this phenomenum. :-) > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "I always feel generous when I'm in the inner circle of a > conspiracy to subvert the world order and, with a small group of > allies, just defeated an alien invasion. Maybe I should value myself > a little more?" > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 9:54:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7FB0A15904 for ; Tue, 12 Oct 1999 09:54:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA18782; Tue, 12 Oct 1999 09:54:02 -0700 Date: Tue, 12 Oct 1999 09:54:02 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: "Daniel C. Sobral" , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-Reply-To: <25232.939746748@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "This time of the year" == "This time in the release cycle" > > If we want to have a somewhat clean line before 4.0 now is the time > to push it through, not after the code freeze. And could you mention when the code freeze might be so that some of us could plan our work? Perhaps I've missed something, but I hadn't heard when the freeze would be. I have a *lot* of things to consider changing before it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10: 5:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id BB3C515178 for ; Tue, 12 Oct 1999 10:05:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA25328; Tue, 12 Oct 1999 19:03:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "Daniel C. Sobral" , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-reply-to: Your message of "Tue, 12 Oct 1999 09:54:02 PDT." Date: Tue, 12 Oct 1999 19:03:37 +0200 Message-ID: <25326.939747817@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> "This time of the year" == "This time in the release cycle" >> >> If we want to have a somewhat clean line before 4.0 now is the time >> to push it through, not after the code freeze. > >And could you mention when the code freeze might be so that some of us >could plan our work? Perhaps I've missed something, but I hadn't heard >when the freeze would be. I have a *lot* of things to consider changing >before it. I have no idea when the code freeze happens, neither has anybody else. Looking at my complete collection of FreeBSD CDs on the shelf here I would put my money (but not too much) on january 2000. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10: 6:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C23C915BA9 for ; Tue, 12 Oct 1999 10:06:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA25328; Tue, 12 Oct 1999 19:03:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "Daniel C. Sobral" , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-reply-to: Your message of "Tue, 12 Oct 1999 09:54:02 PDT." Date: Tue, 12 Oct 1999 19:03:37 +0200 Message-ID: <25326.939747817@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> "This time of the year" == "This time in the release cycle" >> >> If we want to have a somewhat clean line before 4.0 now is the time >> to push it through, not after the code freeze. > >And could you mention when the code freeze might be so that some of us >could plan our work? Perhaps I've missed something, but I hadn't heard >when the freeze would be. I have a *lot* of things to consider changing >before it. I have no idea when the code freeze happens, neither has anybody else. Looking at my complete collection of FreeBSD CDs on the shelf here I would put my money (but not too much) on january 2000. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10:13:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0EDEB14FE8 for ; Tue, 12 Oct 1999 10:13:06 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA19020; Tue, 12 Oct 1999 10:12:54 -0700 Date: Tue, 12 Oct 1999 10:12:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: "Daniel C. Sobral" , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-Reply-To: <25326.939747817@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999, Poul-Henning Kamp wrote: > In message , Matthew Jacob writes: > >> "This time of the year" == "This time in the release cycle" > >> > >> If we want to have a somewhat clean line before 4.0 now is the time > >> to push it through, not after the code freeze. > > > >And could you mention when the code freeze might be so that some of us > >could plan our work? Perhaps I've missed something, but I hadn't heard > >when the freeze would be. I have a *lot* of things to consider changing > >before it. > > I have no idea when the code freeze happens, neither has anybody else. > > Looking at my complete collection of FreeBSD CDs on the shelf here > I would put my money (but not too much) on january 2000. Well, you scared me with the "not after the code freeze" statement. I would like the work I do for FreeBSD 4.0 not to be as incomplete as it was for FreeBSD 3.0, so making plans as to when new feature freeze is would be a "good thing (tm)". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10:18:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2382814C41 for ; Tue, 12 Oct 1999 10:18:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA25390; Tue, 12 Oct 1999 19:16:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "Daniel C. Sobral" , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-reply-to: Your message of "Tue, 12 Oct 1999 10:12:54 PDT." Date: Tue, 12 Oct 1999 19:16:26 +0200 Message-ID: <25388.939748586@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >> >And could you mention when the code freeze might be so that some of us >> >could plan our work? Perhaps I've missed something, but I hadn't heard >> >when the freeze would be. I have a *lot* of things to consider changing >> >before it. >> >> I have no idea when the code freeze happens, neither has anybody else. >> >> Looking at my complete collection of FreeBSD CDs on the shelf here >> I would put my money (but not too much) on january 2000. > >Well, you scared me with the "not after the code freeze" statement. I >would like the work I do for FreeBSD 4.0 not to be as incomplete as it was >for FreeBSD 3.0, so making plans as to when new feature freeze is would be >a "good thing (tm)". I'd say try to have the boat rocking done by dec 1st, but that is merely a guess. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10:23:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id F28B21585D; Tue, 12 Oct 1999 10:22:43 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA70522; Tue, 12 Oct 1999 10:22:29 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199910121722.KAA70522@gndrsh.dnsmgr.net> Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <38035AFD.2C647063@gorean.org> from Doug at "Oct 12, 1999 08:59:57 am" To: Doug@gorean.org (Doug) Date: Tue, 12 Oct 1999 10:22:29 -0700 (PDT) Cc: jmb@hub.freebsd.org (Jonathan M. Bresler), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Rodney W. Grimes" wrote: > > > > > > > > > > "Accidental" removals from the lists are so common that I give up. I no > > > > longer even try to get back on them -- it's been happening for _years_ now, > > > > and I have made multiple complaints about it, and if it's not a problem for > > > > whoever runs the mailing lists, then I just don't care that much. > > > > > > only one comment. i remove people from the lists whenever > > > their email bounces. the threshhold is approximately 30 messages in a > > > 24 hour period. mail may bounce due to DNS problems, mail box full, > > > MTA misconfiguration. i also remove people that send vacation > > > messages to the list. oh, and spammers. > > > > Perhaps these threshholds could use some minor adjustments, or perhaps > > my interpretation of the above policy is not quite what really happens. > > Having been in a situation similar to Jonathan's (managing a large > site, many lists, thousands of users) I can only say that it's hard to > appreciate the difficulty of the task without experiencing it. I think > he does a fine job, extending people more patience than I used to. :) And just who did you think passed the hat onto JMB? He is doing an outstanding job of postmaster, but it seems we have a small problem that perhaps can easily be fixed by some minor adjustments, perhaps not. The biggest part of my response was an attempt to more fully understand his current ``policy'', in that the original statements about it where lacking in detail. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10:27:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D588A14EE9 for ; Tue, 12 Oct 1999 10:27:46 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA19109; Tue, 12 Oct 1999 10:27:40 -0700 Date: Tue, 12 Oct 1999 10:27:40 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: freebsd-current@freebsd.org Subject: SMP stack faults... 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 a followup question on my question from a week ago or so.... ther was indeed a stack overflow I'd guess- I check the code path more carefully and there was a 2KB stack buffer there (oof)- and removing it seemed to make the problem go away....So the question here is "Shouldn't this have been a more obvious fault"? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10:32: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 2827F15B02 for ; Tue, 12 Oct 1999 10:31:55 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 61567 invoked from network); 12 Oct 1999 17:31:37 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 12 Oct 1999 17:31:37 -0000 Date: Tue, 12 Oct 1999 12:31:37 -0500 (CDT) From: David Scheidt To: "Bill A. K." Cc: FreeBSD Questions , freebsd-current@freebsd.org Subject: Re: Linux X Server In-Reply-To: <000701bf14ca$9f666360$01010101@bopper> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999, Bill A. K. wrote: > Hi, > Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm > trying to run the Voodoo Banshee server from Creative Labs. The reason I'm Yup. I run a Voodoo Banshee, with the Creative Labs Linux X server. This is on -CURRENT just before newpcm and newpnp, and XFree 3.3.3. I don't remember having to do anything too wild to get it working. The one problem I do remember is that it doesn't play nicely with /dev/sysmouse. I have to use the real mouse device, and can't run moused. I don't have access to the machine at the moment, so I cannot tell you much more than that. I will take a look at the machine when I get home, and see what else I might have done. I don't run xdm, which might be an issue. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 10:33:17 1999 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 21B35157D3 for ; Tue, 12 Oct 1999 10:33:09 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p05-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.134]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA25444; Wed, 13 Oct 1999 02:33:04 +0900 (JST) Message-ID: <38036D7A.287B2A8B@newsguy.com> Date: Wed, 13 Oct 1999 02:18:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Michael Lucas Cc: current@FreeBSD.ORG Subject: Re: Request for Flames References: <199910121508.LAA44474@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas wrote: > > If any of you have copies of messages that you have previously sent, > describing what information you need to solve a particular problem, I > would appreciate it if you would forward these to me. I'll use this > information to write another guide. I guess I ought to see what you already have, but... well, I'm lazy, and not connected right now. :-) Whatever you do, *please* make a mention of the sections in the handbook that deal precisely with this kind of stuff! -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 12:24:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id BBC411588F for ; Tue, 12 Oct 1999 12:24:00 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 57094 invoked from network); 12 Oct 1999 19:23:44 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 12 Oct 1999 19:23:44 -0000 Message-ID: <38038AA5.45796B87@pipeline.ch> Date: Tue, 12 Oct 1999 21:23:17 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: "Jonathan M. Bresler" Cc: scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch References: <19991012142522.57A98152AF@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan M. Bresler wrote: > > thanks for the note on bouncefilter. > i'll take a look at it. > may be just what i am looking for.. > may be better than what i am using already. > always interested in somethatngthat will help me > do this better. That is what I was talking about. With ezmlm there is no need to deal with bounces anymore, it does that completly automatically with VERP. At this time it only runs with qmail, but it might be possible to teach it to like postfix (should be even easy IMHO). I'll give it a shot if there is a chance that it will be used eventually. I know some guys with list's in the three digit k to one digit M range which don't have to deal with bounces at any time. I know it's hard to believe but it's true and I can provide you with names where one can ask for confirmation. More information about ezmlm can be found on ftp://koobera.math.uic.edu/www/ezmlm.html (Authors homepage) and http://www.ezmlm.org (extended version, ezmlm-idx) more info about VERP is here ftp://koobera.math.uic.edu/www/proto/verp.txt (very interesting) and about how it handles bounces perfectly automatic: http://www.ezmlm.org/faq-0.32/FAQ4.html#ss4.9 (ezmlm path for bounces) plus http://www.ezmlm.org/faq-0.32/FAQ4.html#ss4.33 (how bounces are handled) -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 12:33: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id DBDF814E65; Tue, 12 Oct 1999 12:32:48 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA09017; Tue, 12 Oct 1999 21:32:43 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id VAA19479; Tue, 12 Oct 1999 21:32:39 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <38038AA5.45796B87@pipeline.ch> References: <19991012142522.57A98152AF@hub.freebsd.org> <38038AA5.45796B87@pipeline.ch> Date: Tue, 12 Oct 1999 21:32:30 +0200 To: Andre Oppermann , "Jonathan M. Bresler" From: Brad Knowles Subject: Re: People getting automatically unsub'ed from -arch Cc: scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:23 PM +0200 1999/10/12, Andre Oppermann wrote: > I know some guys with list's in the three digit k to one digit M range > which don't have to deal with bounces at any time. I know it's hard > to believe but it's true and I can provide you with names where one > can ask for confirmation. And Bryan Costales & Eric Allman have hacked sendmail to support VERPs, and last I heard InfoBeat was handling on the order of several million customers per day. Of course, they're doing an e-mail merge operation so that each recipient gets a unique message, but that would just put an even heavier load on the system than a mailing list the same size. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 13: 6:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 55C7014C88 for ; Tue, 12 Oct 1999 13:06:20 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA38713; Tue, 12 Oct 1999 14:06:15 -0600 (MDT) (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 OAA98534; Tue, 12 Oct 1999 14:07:00 -0600 (MDT) Message-Id: <199910122007.OAA98534@harmony.village.org> To: FreeBSD Bob Subject: Re: Why Adaptec 1540 bombing? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 04 Oct 1999 10:39:00 EDT." <199910041439.KAA35683@weedcon1.cropsci.ncsu.edu> References: <199910041439.KAA35683@weedcon1.cropsci.ncsu.edu> Date: Tue, 12 Oct 1999 14:07:00 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910041439.KAA35683@weedcon1.cropsci.ncsu.edu> FreeBSD Bob writes: : It is a long shot, but I am curious if anyone knows of any problems in : using the Adaptec 1540A on 3.x or 4.x machines? The aha 1540 driver (me) didn't have access to the 1540A cards, so I made changes blind and never tested (nor did those folks that bugged me to make them). If you can send me this card, I can see what I can do about making it work with the aha driver. There are problems with CAM and this hardware's use of transfer residuals which might make it hard to get working. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 13:12: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id B9CEA15119 for ; Tue, 12 Oct 1999 13:12:02 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 57238 invoked from network); 12 Oct 1999 20:11:46 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 12 Oct 1999 20:11:46 -0000 Message-ID: <380395E7.2D38E200@pipeline.ch> Date: Tue, 12 Oct 1999 22:11:19 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Brad Knowles Cc: "Jonathan M. Bresler" , scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch References: <19991012142522.57A98152AF@hub.freebsd.org> <38038AA5.45796B87@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 9:23 PM +0200 1999/10/12, Andre Oppermann wrote: > > > I know some guys with list's in the three digit k to one digit M range > > which don't have to deal with bounces at any time. I know it's hard > > to believe but it's true and I can provide you with names where one > > can ask for confirmation. > > And Bryan Costales & Eric Allman have hacked sendmail to support > VERPs, and last I heard InfoBeat was handling on the order of several > million customers per day. Of course, they're doing an e-mail merge > operation so that each recipient gets a unique message, but that > would just put an even heavier load on the system than a mailing list > the same size. That is just how VERP works, every email is unique (at least the return-path). They must be crazy to run a several million recipients mailing list with sendmail... Do you remember the time when the FreeBSD lists were driven by sendmail? The lists were lagging several hours behind. And I don't think we have high two or three digit k subscribers on a single list. Maybe JMB can shed some light on how many people are subscribed to the lists (just ranges). -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 13:21:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A258314BD8 for ; Tue, 12 Oct 1999 13:21:34 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA04571; Tue, 12 Oct 1999 13:21:32 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA01959; Tue, 12 Oct 1999 13:21:32 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 12 Oct 1999 13:21:32 -0700 (PDT) Message-Id: <199910122021.NAA01959@vashon.polstra.com> To: freebsd@mrynet.com Subject: Re: World fail + resulting cvsup failures In-Reply-To: <199910112143.OAA08646@mrynet.com> References: <199910112143.OAA08646@mrynet.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > mrynet# cvsup > > > *** > *** runtime error: > *** Segmentation violation - possible attempt to dereference NIL > *** pc = 0x2f > *** > > Abort trap I sent a heads up about this to the list a while ago. There are people working on the kernel problem that causes it. For now, add "@M3novm" to the cvsup command line (anywhere) as a work-around. And don't try to build a new Modula-3 or CVSup on -current at the moment. It won't work. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 14:18:49 1999 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 3ECD314FD7 for ; Tue, 12 Oct 1999 14:18:39 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id OAA22773; Tue, 12 Oct 1999 14:18:25 -0700 (PDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id OAA09061; Tue, 12 Oct 1999 14:17:59 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id OAA06678; Tue, 12 Oct 1999 14:17:45 -0700 (PDT) Message-Id: <199910122117.OAA06678@mina.sr.hp.com> To: Warner Losh Cc: FreeBSD Bob , freebsd-current@FreeBSD.ORG Subject: Re: Why Adaptec 1540 bombing? Reply-To: Darryl Okahata In-reply-to: Your message of "Tue, 12 Oct 1999 14:07:00 MDT." <199910122007.OAA98534@harmony.village.org> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Tue, 12 Oct 1999 14:17:45 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > If you can send me this card, I can see what I can do about making it > work with the aha driver. There are problems with CAM and this > hardware's use of transfer residuals which might make it hard to get > working. If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be willing to lend out (if the address is in the US). It's been years since I've used it, and so I'm not 100% sure that it still works, though. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, 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 Tue Oct 12 14:25:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1204614DE9 for ; Tue, 12 Oct 1999 14:25:24 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA39025; Tue, 12 Oct 1999 15:25:20 -0600 (MDT) (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 PAA99015; Tue, 12 Oct 1999 15:26:07 -0600 (MDT) Message-Id: <199910122126.PAA99015@harmony.village.org> To: Darryl Okahata Subject: Re: Why Adaptec 1540 bombing? Cc: FreeBSD Bob , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 12 Oct 1999 14:17:45 PDT." <199910122117.OAA06678@mina.sr.hp.com> References: <199910122117.OAA06678@mina.sr.hp.com> Date: Tue, 12 Oct 1999 15:26:07 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910122117.OAA06678@mina.sr.hp.com> Darryl Okahata writes: : If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be : willing to lend out (if the address is in the US). It's been years : since I've used it, and so I'm not 100% sure that it still works, : though. Well, I could install 2.2.x onto a disk and see if that works there. Once I do that, I can then know if it works or not. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 14:29:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BAE1E14CE0 for ; Tue, 12 Oct 1999 14:28:58 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Wed, 13 Oct 1999 07:24:55 +1000 Content-return: prohibited Date: Wed, 13 Oct 1999 07:28:46 +1000 From: Peter Jeremy Subject: Re: Proper Whacking & Weeding In-reply-to: <199910121503.RAA02057@oranje.my.domain> To: Marc van Woerkom Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct13.072455est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199910121503.RAA02057@oranje.my.domain> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-13 01:03:54 +1000, Marc van Woerkom wrote: >It took me some fiddling to get a -current system from begin of September >to build present -current. It might be useful if you documented exactly what you did. This is likely to be a very popular topic for the next few months... >Is there a way to ensure that /usr/include, /usr/share/.. and such >are rebuilt properly? (No files missing, no old files messing things up) It shouldn't be possible to miss files during an installworld without the installworld bombing out, though I'm not sure how to actually confirm this. I have had a couple of occurrences where my checked-out source tree got out of step with my CVS tree (I'm not sure how this happened). My solution here is to occasionally do a checkout into a temporary tree and compare it with my active tree. (An alternative would be to squirrel away my local patches and blow away the active tree). As for obsolete cruft in the root and /usr filesystems, you could try "rm -fr /" :-). Seriously, since installworld installs everything with the current date, one way is to run "ls -ltr" on all all affected directories and delete all files older than the installworld. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 14:48:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from knecht.sendmail.org (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (Postfix) with ESMTP id 0842714DE9; Tue, 12 Oct 1999 14:48:07 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.sendmail.org (8.9.3/8.9.3) with ESMTP id OAA02290; Tue, 12 Oct 1999 14:48:04 -0700 (PDT) Received: from flamingo.McKusick.COM (mckusick@localhost.concentric.net [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id NAA15822; Tue, 12 Oct 1999 13:14:41 -0700 (PDT) Message-Id: <199910122014.NAA15822@flamingo.McKusick.COM> To: Julian Elischer Subject: Re: The eventual fate of BLOCK devices. Cc: Bruce Evans , Matthew Dillon , freebsd-arch@freebsd.org, committers@freebsd.org, current@freebsd.org In-reply-to: Your message of "Sun, 10 Oct 1999 18:21:04 PDT." <199910110121.SAA18665@apollo.backplane.com> Date: Tue, 12 Oct 1999 13:14:40 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to take a step back from the debate for a moment and ask the bigger question: How many real-world applications actually use the block device interface? I know of none whatsoever. All the filesystem utilities go out of their way to avoid the block device and use the raw interface. Does anyone on this list know of any programs that need/want the block interface? If there are none, or only very obscure ones, then it seems pointless to waste any kernel code supporting them. Indeed it will clean up a good deal of code to get rid of them. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 14:58:31 1999 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 10D1C151D5; Tue, 12 Oct 1999 14:58:12 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA18360; Tue, 12 Oct 1999 16:57:49 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Tue, 12 Oct 1999 16:57:49 -0500 (CDT) From: David Scheidt To: Kirk McKusick Cc: Julian Elischer , Bruce Evans , Matthew Dillon , freebsd-arch@freebsd.org, committers@freebsd.org, current@freebsd.org Subject: Re: The eventual fate of BLOCK devices. In-Reply-To: <199910122014.NAA15822@flamingo.McKusick.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 Tue, 12 Oct 1999, Kirk McKusick wrote: > I would like to take a step back from the debate for a moment and > ask the bigger question: How many real-world applications actually > use the block device interface? I know of none whatsoever. All the > filesystem utilities go out of their way to avoid the block device > and use the raw interface. Does anyone on this list know of any > programs that need/want the block interface? If there are none, or It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated disk devices. There may be other RDBMSes that do this. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 14:59:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EC5D8151F8 for ; Tue, 12 Oct 1999 14:59:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA39140; Tue, 12 Oct 1999 15:59:23 -0600 (MDT) (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 QAA99243; Tue, 12 Oct 1999 16:00:11 -0600 (MDT) Message-Id: <199910122200.QAA99243@harmony.village.org> To: Doug Rabson Subject: Re: Recent kernel hangs during boot with pnp sio. Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Oct 1999 10:45:42 BST." References: Date: Tue, 12 Oct 1999 16:00:11 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : If you find yourself with one of these and pnp is turned off, you can : download the DOS utility from 3com. I recently had to do this for a friend : (to turn pnp off). It was harder to find a DOS boot disk :-). Sometimes these programs work with doscmd with magic command line options... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15: 9:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1D59315573; Tue, 12 Oct 1999 15:08:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA39192; Tue, 12 Oct 1999 16:08:33 -0600 (MDT) (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 QAA99330; Tue, 12 Oct 1999 16:09:19 -0600 (MDT) Message-Id: <199910122209.QAA99330@harmony.village.org> To: Matthew Dillon Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... Cc: "Rodney W. Grimes" , dg@root.com, dwmalone@maths.tcd.ie (David Malone), ady@warpnet.ro (Adrian Penisoara), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Oct 1999 11:28:18 PDT." <199910081828.LAA03945@apollo.backplane.com> References: <199910081828.LAA03945@apollo.backplane.com> <199910081711.KAA49036@gndrsh.dnsmgr.net> Date: Tue, 12 Oct 1999 16:09:18 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910081828.LAA03945@apollo.backplane.com> Matthew Dillon writes: : Forget the drilling! Blood conducts electricity... simply *installing* : a motherboard in those fraggin sharp-edged sheet metal chassis is enough! I've had one or two cheapo mo-bos that haven't worked at 100MHz after spattering human blood on it from said sharp-edged sheet metal corners... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15:11: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F3C4D15387; Tue, 12 Oct 1999 15:10:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA39209; Tue, 12 Oct 1999 16:10:42 -0600 (MDT) (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 QAA99359; Tue, 12 Oct 1999 16:11:30 -0600 (MDT) Message-Id: <199910122211.QAA99359@harmony.village.org> To: David Scheidt Subject: Re: The eventual fate of BLOCK devices. Cc: Kirk McKusick , Julian Elischer , Bruce Evans , Matthew Dillon , freebsd-arch@FreeBSD.ORG, committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Tue, 12 Oct 1999 16:57:49 CDT." References: Date: Tue, 12 Oct 1999 16:11:30 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message David Scheidt writes: : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated : disk devices. There may be other RDBMSes that do this. EVERY RDBMS that I've ever seen or had to make work with my drivers has been on the raw partition. This is because the database writers DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic nature of disk writing. Are you sure that Sybase uses BLOCK devices and not CHAR devices? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15:13:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from lorien.odc.net (lorien.odc.net [207.137.42.14]) by hub.freebsd.org (Postfix) with ESMTP id 412A515576 for ; Tue, 12 Oct 1999 15:11:37 -0700 (PDT) (envelope-from nwestfal@lorien.odc.net) Received: from localhost (nwestfal@localhost) by lorien.odc.net (8.9.3/8.9.3) with ESMTP id PAA09343 for ; Tue, 12 Oct 1999 15:11:35 -0700 Date: Tue, 12 Oct 1999 15:11:35 -0700 (PDT) From: Neal Westfall To: current@freebsd.org Subject: ESS 1938 Soundcard 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 picked up a cheap PCI soundcard at Fry's for $17.99. The box has a picture of a card using the Trident 4DWAVE chip, but the card in the box had an ESS 1938S chip on it. Now I know there is no support for this card yet, but was wondering if there is any support planned for it in the near future? Anyone heard of this PCI sound chip? Didn't see anything on the OSS webpage about it either. Neal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15:30:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 845C614F64; Tue, 12 Oct 1999 15:30:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA58850; Tue, 12 Oct 1999 15:29:37 -0700 (PDT) Date: Tue, 12 Oct 1999 15:29:37 -0700 (PDT) From: Julian Elischer To: current@freebsd.org, committers@freebsd.org Subject: Re: The eventual fate of BLOCK devices. In-Reply-To: <199910122014.NAA15822@flamingo.McKusick.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 If you are going to respond to this. do it to 'freebsd-arch' only I've redirected my resonse there.. don't respond to this one.. On Tue, 12 Oct 1999, Kirk McKusick wrote: > I would like to take a step back from the debate for a moment and > ask the bigger question: How many real-world applications actually [...] julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15:53:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from satsuma.mail.easynet.net (satsuma.mail.easynet.net [195.40.1.44]) by hub.freebsd.org (Postfix) with ESMTP id CFE8A14DF1; Tue, 12 Oct 1999 15:52:52 -0700 (PDT) (envelope-from frankrj@netscape.net) Received: from netscape.net (alister.w.easynet.co.uk [212.212.251.86]) by satsuma.mail.easynet.net with ESMTP id 99CB77B08D; Tue, 12 Oct 1999 23:52:49 +0100 (BST) Message-ID: <3803BD43.F097500C@netscape.net> Date: Tue, 12 Oct 1999 23:59:15 +0100 From: Francis Jordan X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Bill A. K." Cc: FreeBSD Questions , freebsd-current@freebsd.org Subject: Re: Linux X Server References: <000701bf14ca$9f666360$01010101@bopper> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Bill A. K." wrote: > Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm > trying to run the Voodoo Banshee server from Creative Labs. The reason I'm > trying to do this is because when I run XFree86 3.3.5, it screws up my > console display when I exit X. The Linux Server is looking to open /dev/tty9 > and it can't. I tried putting a hard link from /dev/tty9 to /dev/ttyv9 but > when i started X it paniced the kernel :) > > Is there any way first of all to fix 3.3.5 to work, and if not, to get the > Linux server to work? Is there any way to somehow mimic /dev/tty9 for it? The Banshee only seems to have this problem when switching from a graphical mode to the _standard_ text mode (80x25). Adding the following line to /etc/rc.conf allscreens_flags="80x30" fixed it for me. Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15:54:59 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id E1DBB152BA; Tue, 12 Oct 1999 15:54:56 -0700 (PDT) From: "Jonathan M. Bresler" To: dscheidt@enteract.com Cc: mckusick@flamingo.McKusick.COM, julian@whistle.com, bde@zeta.org.au, dillon@apollo.backplane.com, freebsd-arch@freebsd.org, committers@freebsd.org, current@freebsd.org In-reply-to: (message from David Scheidt on Tue, 12 Oct 1999 16:57:49 -0500 (CDT)) Subject: Re: The eventual fate of BLOCK devices. Message-Id: <19991012225456.E1DBB152BA@hub.freebsd.org> Date: Tue, 12 Oct 1999 15:54:56 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sybase can use either block devices or raw disk. We run all our databases, Sybase, Oracle, etc. on raw disk. the database engineers here would kill me if i were to ask them to use a block device rather than raw disk. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 15:56:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from bd.mbn.or.jp (bd.mbn.or.jp [202.217.0.43]) by hub.freebsd.org (Postfix) with ESMTP id 20DBA14DF1 for ; Tue, 12 Oct 1999 15:56:45 -0700 (PDT) (envelope-from chi@bd.mbn.or.jp) Received: from chino.localhost (cse6-88.sapporo.mbn.or.jp [202.217.111.158]) by bd.mbn.or.jp (8.9.1/bd.mbn.or.jp-2.0) with ESMTP id HAA03120; Wed, 13 Oct 1999 07:56:41 +0900 (JST) Date: Wed, 13 Oct 1999 07:56:41 +0900 (JST) Message-Id: <199910122256.HAA03120@bd.mbn.or.jp> Posted-Date: Tue, 12 Oct 1999 13:18:09 JST To: freebsd-current@freebsd.org Cc: freebsd98-hackers@jp.freebsd.org Subject: non-512 msdosfs patch From: chi@bd.mbn.or.jp (Chiharu Shibata) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is Chiharu Shibata, who sent the PR(misc/12992) before. That PR's patch is to support non-512bytes/sector media for msdosfs. I have been checking the CVS repository, but the patch is not committed yet. I was hoping to be committed, before the patch is not available by another modification of msdosfs. The MO is very popular media in Japan, and 640MB/1.3GB MO are both 2048bytes/sector media. So, It is a FAQ that "How can I use DOS/Windows formatted 640MB MO?". In addition, NEC PC-98 uses non-512bytes/sector media generally. It is useless for PC-98 without the patch, not too much to say. I have reports that the patch works well, not only NEC PC-98, but also PC/AT's FreeBSD3.2-RELEASE. PS. I don't subscribe freebsd-current ML. About this theme, please send to me via freebsd98-hackers ML with Cc:. (See Cc: of this mail) -- Chiharu Shibata chi@bd.mbn.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 16:12:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 33B4114C16 for ; Tue, 12 Oct 1999 16:12:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA39461; Tue, 12 Oct 1999 17:12:10 -0600 (MDT) (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 RAA99894; Tue, 12 Oct 1999 17:12:58 -0600 (MDT) Message-Id: <199910122312.RAA99894@harmony.village.org> To: Doug Rabson Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org Cc: Jason DiCioccio , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 10 Oct 1999 18:00:08 BST." References: Date: Tue, 12 Oct 1999 17:12:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : Due to the nature of the pnp code, it might be probed as ed1 instead of : ed0. I have a SBC here that has an onboard PNP ne2000 chip on it. It comes up as ed1 because I have ed0 at a wired address. I don't see ed0 at all, and it just works, so I just hacked my rc.conf to use ed1 rather than ed0 like I did when it ran 3.3R. Now for the obligitory tangent: Does FreeBSD have the ability to reassign IRQs for PNP devices? I have one that is coming up at IRQ 5, but I have a non-PNP device that is at 5, but many other IRQs free. There is no way in the BIOS to set which IRQs are used for PNP and which ones are designated for legacy devices. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 16:16:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 79B5614E3D for ; Tue, 12 Oct 1999 16:16:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA39477; Tue, 12 Oct 1999 17:16:53 -0600 (MDT) (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 RAA99928; Tue, 12 Oct 1999 17:17:40 -0600 (MDT) Message-Id: <199910122317.RAA99928@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: How do I get a PCCARD modem to work? Cc: Soren Schmidt , gibbs@plutotech.com (Justin T. Gibbs), current@FreeBSD.ORG In-reply-to: Your message of "Sun, 10 Oct 1999 18:38:58 MDT." <199910110038.SAA15816@caspian.plutotech.com> References: <199910110038.SAA15816@caspian.plutotech.com> Date: Tue, 12 Oct 1999 17:17:40 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910110038.SAA15816@caspian.plutotech.com> "Justin T. Gibbs" writes: : The pccard brokenness is not sio's fault. If I were following where : our PCCARD support was going, I might take a stab at fixing this myself... Yes. Pccard brokennes *IS* sio's fault. It was written to only deal with ISA busses and cannot attach to other busses (yet). That's the issue. I did noticed that Doug submitted some changes that might change this... I'll have to look tonight after doing some consulting.. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 16:26: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.harrisburgacademy.org (2093702.harrisburgacademy.org [209.3.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 4F41B14BE5 for ; Tue, 12 Oct 1999 16:25:42 -0700 (PDT) (envelope-from i.think@harrisburgacademy.org) Received: from DESCARTES ([205.238.199.205]) by www.harrisburgacademy.org (Netscape Messaging Server 3.5) with SMTP id 571; Tue, 12 Oct 1999 19:20:44 -0400 Message-ID: <002301bf1508$dd5e2700$0300000a@tamm.local> From: "i think" To: "Jeroen Ruigrok/Asmodai" , "Amancio Hasty" Cc: References: <199910110810.BAA03671@rah.star-gate.com> <19991011214828.F9737@daemon.ninth-circle.org> Subject: Re: 3dfx Driver? Date: Tue, 12 Oct 1999 19:23:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there was a walkthrough on how to get the linux drivers running through the linux emulation. this is specifically for the quake3 test, i dont know how it will fare on any other programs ( havent tried) but q3test does work. if you want, check it out http://www.cybernet.com/~mtaylor/q3ahowto.html Andrew ----- Original Message ----- From: "Jeroen Ruigrok/Asmodai" To: "Amancio Hasty" Cc: Sent: Monday, October 11, 1999 15:48 Subject: Re: 3dfx Driver? > On [19991011 12:00], Amancio Hasty (hasty@rah.star-gate.com) wrote: > > > >Has anyone ported the linux 3DFx Driver to FreeBSD? > > Don't think so. > > Why? You volunteering? =) > > -- > Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl > The BSD Programmer's Documentation Project > Network/Security Specialist BSD: Technical excellence at its best > One from many. > > > 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 Oct 12 17:11:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 0620414D5C for ; Tue, 12 Oct 1999 17:11:25 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA40555; Wed, 13 Oct 1999 09:41:10 +0930 (CST) Date: Wed, 13 Oct 1999 09:41:10 +0930 From: Greg Lehey To: Michael Lucas Cc: current@FreeBSD.ORG Subject: How to report problems (was: Request for Flames) Message-ID: <19991013094110.T78191@freebie.lemis.com> References: <199910121508.LAA44474@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199910121508.LAA44474@blackhelicopters.org> 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 12 October 1999 at 11:08:50 -0400, Michael Lucas wrote: > Folks, > > I'm writing a series of web pages on how to ask for help on the > FreeBSD mailing lists. > > From time to time, some innocent newbie wanders in here asking a > question with far too little information. ("CVSup/pn0/sio.c doesn't > work. Why not?") That's a *good* one. Take a look at http://www.lemis.com/questions.html for some alternatives. > On occasion, you folks have taken the time to write detailed notes > describing the exact information you need to solve these problems. > (On other occasions, said newbie is seen around town: a little bit > here, a little bit there... but that's another problem.) > > I'me searched the mail archives looking for these messages, and am > having difficulty finding them. (It's difficult to search for "That > message where Bill Paul told a newbie in excruciating detail what he > needed to fix the problem, and what would happen to the next newbie > who asked this question without providing this information.") Lots of > questions, very few detailed answers. > > If any of you have copies of messages that you have previously sent, > describing what information you need to solve a particular problem, I > would appreciate it if you would forward these to me. I'll use this > information to write another guide. > > For an example of what I'm trying to do, take a look at: > > http://www.blackhelicopters.org/~dispatch/report/nic.html Looks good. You probably need to structure it differently (for example, have a link to things like OS revision and kernel config, which will be needed in most cases). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 17:36:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 9787714D5C for ; Tue, 12 Oct 1999 17:36:24 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial4-102.netcologne.de [195.14.233.102]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id CAA00114; Wed, 13 Oct 1999 02:36:20 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id CAA44765; Wed, 13 Oct 1999 02:36:42 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Wed, 13 Oct 1999 02:36:42 +0200 (CEST) Message-Id: <199910130036.CAA44765@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: peter.jeremy@alcatel.com.au Cc: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG In-reply-to: <99Oct13.072458est.40328@border.alcanet.com.au> (message from Peter Jeremy on Wed, 13 Oct 1999 07:28:46 +1000) Subject: Re: Proper Whacking & Weeding Reply-To: van.woerkom@netcologne.de References: <199910121503.RAA02057@oranje.my.domain> <99Oct13.072458est.40328@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It might be useful if you documented exactly what you did. This is > likely to be a very popular topic for the next few months... Not quite possible, because when things started to look foobar I was not cool enough to keep logging. :) But I know some highlights of my tour: o My Last successful -current build was Sun Sep 19 19:18:42 CEST 1999 o Then I tried to rebuild on Tue Oct 5 17:49:53 CEST 1999 and got this one: ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. So I decided to wait some times, in case this was related to changes to gcc. o Next try was Sun Oct 10 12:55:50 CEST 1999 This time I had a look into freebsd-current and src/UPDATING before and noticed that I had to build a new kernel before. No problems. Kernel compiled, installed and booted. o Later, Sun Oct 10 13:38:40 CEST 1999 during make buildworld, I got this one: cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/arch.c In file included from /usr/include/sys/stat.h:50, from /usr/src/usr.bin/make/arch.c:97: /usr/include/sys/time.h:289: time.h: No such file or directory /usr/src/usr.bin/make/arch.c:100: ctype.h: No such file or directory /usr/src/usr.bin/make/arch.c:101: ar.h: No such file or directory /usr/src/usr.bin/make/arch.c:102: utime.h: No such file or directory /usr/src/usr.bin/make/arch.c:104: stdlib.h: No such file or directory In file included from /usr/src/usr.bin/make/arch.c:105: /usr/src/usr.bin/make/make.h:53: ctype.h: No such file or directory /usr/src/usr.bin/make/make.h:76: stdlib.h: No such file or directory In file included from /usr/src/usr.bin/make/make.h:80, from /usr/src/usr.bin/make/arch.c:105: /usr/src/usr.bin/make/lst.h:51: stdlib.h: No such file or directory /usr/src/usr.bin/make/arch.c: In function `ArchStatMember': /usr/src/usr.bin/make/arch.c:464: `SARMAG' undeclared (first use in this function) /usr/src/usr.bin/make/arch.c:464: (Each undeclared identifier is reported only once /usr/src/usr.bin/make/arch.c:464: for each function it appears in.) /usr/src/usr.bin/make/arch.c:468: storage size of `arh' isn't known /usr/src/usr.bin/make/arch.c:514: storage size of `sarh' isn't known /usr/src/usr.bin/make/arch.c:540: `ARMAG' undeclared (first use in this function) /usr/src/usr.bin/make/arch.c:552: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c:553: `ARFMAG' undeclared (first use in this function) /usr/src/usr.bin/make/arch.c:621: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c:623: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c: In function `ArchFindMember': /usr/src/usr.bin/make/arch.c:785: `SARMAG' undeclared (first use in this function) /usr/src/usr.bin/make/arch.c:798: `ARMAG' undeclared (first use in this function) /usr/src/usr.bin/make/arch.c:814: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:815: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:818: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c:819: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:819: `ARFMAG' undeclared (first use in this function) /usr/src/usr.bin/make/arch.c:819: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:826: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:834: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:834: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:844: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c:890: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:890: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c:891: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c: In function `Arch_Touch': /usr/src/usr.bin/make/arch.c:924: storage size of `arh' isn't known /usr/src/usr.bin/make/arch.c:935: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c: In function `Arch_TouchLib': /usr/src/usr.bin/make/arch.c:961: storage size of `arh' isn't known /usr/src/usr.bin/make/arch.c:962: storage size of `times' isn't known /usr/src/usr.bin/make/arch.c:968: sizeof applied to an incomplete type /usr/src/usr.bin/make/arch.c: In function `Arch_MTime': /usr/src/usr.bin/make/arch.c:1006: dereferencing pointer to incomplete type /usr/src/usr.bin/make/arch.c: In function `Arch_LibOODate': /usr/src/usr.bin/make/arch.c:1170: dereferencing pointer to incomplete type *** Error code 1 o Next try was weeding out /usr/include and /usr/share/misc (with the occasional cd /usr/src/include; make install) and a make world -DCLOBBER on Sun Oct 10 16:38:03 CEST 1999 that ended here: cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/compat.c In file included from /usr/src/usr.bin/make/compat.c:67: /usr/include/signal.h:80: syntax error before `*' /usr/include/signal.h:84: syntax error before `*' *** Error code 1 o Then came a make world -DNOTOOLS -DCLOBBER on Sun Oct 10 16:39:35 CEST 1999 that stopped here Processing hints file hints/freebsd.pl Writing Makefile for POSIX mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto/POSIX cd ext/POSIX; make -B all PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl cp POSIX.pod /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/POSIX.pod cp POSIX.pm /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/POSIX.pm AutoSplitting /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/POSIX.pm (/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto/POSIX) /usr/bin/miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -noprototypes -typemap /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap -typemap typemap POSIX.xs >xstmp.c && mv xstmp.c POSIX.c cc -c -DSTRUCT_TM_HASZONE -DVERSION=\"1.02\" -DXS_VERSION=\"1.02\" -DPIC -fpic -I/usr/obj/usr/src/gnu/usr.bin/perl/perl POSIX.c In file included from POSIX.xs:31: /usr/include/signal.h:80: syntax error before `*' /usr/include/signal.h:84: syntax error before `*' *** Error code 1 o Can't remember what I did in what order exactly then, but it involved moving back to a tree that I believed to work (cvs update -D "14 Sep 1999"), diffing and copying headers in /usr/include and stuff in /usr/lib. Note that I kept the new kernel from Oct, 10th! Also some partial installs, when compilation hanged. Finally compilation went through. So I used that userland (that worked except for stuff like top and ps) to get the source tree from Oct, 11th and to finally compile that, after some obstacles. E.g. compilation broke off during build of kdump and ktrace. I finally hacked their makefiles to jump over them, to get a nearly complete Oct, 11th user land compiled. And it worked. Reboot and new kernel compilation worked too: -r-xr-xr-x 1 root wheel 1770088 Oct 11 22:51 kernel -r-xr-xr-x 1 root wheel 1770088 Oct 10 13:13 kernel.old -r-xr-xr-x 1 root wheel 1761443 Sep 19 21:11 kernel.ORANJE Same size, not bad. > As for obsolete cruft in the root and /usr filesystems, you could try > "rm -fr /" :-). Seriously, since installworld installs everything > with the current date, one way is to run "ls -ltr" on all all affected > directories and delete all files older than the installworld. In my case the old cruft had no effect during the last build, but then managed to sabotage the build of the latest system. Today, after a hint from Jörg Wunsch to use ktrace for resolving my trouble with emacs, I tried to recompile ktrace and kdump, ran again into trouble and then realized (after looking at the history with cd /usr/src/sys/netinet; cvs log ip_fil.h etc) ---------------------------- revision 1.8 date: 1999/10/10 15:09:53; author: peter; state: dead; lines: +1 -1 Nuke the old antique copy of ipfilter from the tree. This is old enough to be dangerous. It will better serve us as a port building a KLD, ala SKIP. The hooks are staying although it would be better to port and use the NetBSD pfil interface rather than have custom hooks. ---------------------------- that these headers ip_compat.h ip_fil.h ip_frag.h ip_nat.h ip_proxy.h ip_state.h ipl.h were obsolete and their existence prevented the kdump build. And you can't nuke /usr/include in advance, as you need it to build the new system. > I have had a couple of occurrences where my checked-out source tree > got out of step with my CVS tree (I'm not sure how this happened). > My solution here is to occasionally do a checkout into a temporary > tree and compare it with my active tree. > (An alternative would be to squirrel away my local patches and blow > away the active tree). I really wonder how our hardcore coders manage large sets of patches during their development phase. Sounds like a job for cvs, or? AFAIK, in cvs theory I would have my local cvs repository and would operate it with at least two branches. A vendor branch, were I would import the stuff I get from vendor FreeBSD.org and the main trunk, were I grow my version of the source tree. So I could use cvsup to checkout the latest tree from FreeBSD.org into some directory and import that one with a cvs import command. No clue how long that would take with such a large tree. If it is comparable to a cvs update, it will take 30min-1h for all stuff (doc,ports,src,www) on my box. I also can't say how many conflicts will arise, if that new stuff hits local modifications. If I would import on a daily base, would I need to resolve conflicts again and again? Anyway. That would give me the sources only. [Warning: long blurb - will get recycled see below :) ] One of the best things that happened to me in the last months regarding FreeBSD development was switching CVSup usage from mirroring the latest tree (thus having only the head revision for every source) to mirroring the CVS archives at FreeBSD.org This gives me access to a) all revisions of a file, and -also very important- b) access to the checkin comments of the commiters. The first case is what made me originally switch. I use Hellmuth Michaelis i4b package to connect to the Internet via ISDN. This is usually working so excellent that I never took the time to install ISDN drivers to that Windows 95 system that is also on my disks. However FreeBSD and i4b were changing in a way last year, that often, after updating a nice working source tree over the Internet and recompiling I ended up with a system that was (among other things) broken in a way that it was not able anymore to connect to the net. Bad situation because I had only the latest tree on my disk, and could not revert easily (= via the net) to a working tree. So I usually installed an older FreeBSD version from CD-ROM then and started over. That was quite an act sometimes (sd->da, aout->elf..) Then I realized that I need the CVS repository on my box, and with help from John Polstra I configured CVSup to mirror it. Since then I can use cvs log and cvs status to see the history and read the committer's comments. Very useful. Drawback is speed. While CVSup mirrors the CVS repository quite fast I now need an additional cvs update to sync my source tree with the CVS repository. And that is quite slow. (But I am working on a program that will speed up this process) [end of blurb - back to administering patches] So, how to get the comments into the cvs repository? Possible sources are - the commit messages from the cvs-all mailing list (local copy, or accessed from www.freebsd.org) - the FreeBSD CVS repository itself (local mirror as described above, or accessed from the anoncvs server at FreeBSD.org) It should be possible building such a system, with lots of duct tape. Question is -and that is the reason I went into such detail here- is this a too complicated solution for managing an individual tree while staying in contact with the main tree, or might it be useful? I hope for some criticism by the folks here, and will experiment further and hope to finally write it up. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 17:41: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4145B14E79; Tue, 12 Oct 1999 17:41:00 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CA0C41C6D; Wed, 13 Oct 1999 08:40:59 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: David Scheidt , Kirk McKusick , Julian Elischer , Bruce Evans , Matthew Dillon , freebsd-arch@FreeBSD.ORG, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: The eventual fate of BLOCK devices. In-reply-to: Your message of "Tue, 12 Oct 1999 16:11:30 CST." <199910122211.QAA99359@harmony.village.org> Date: Wed, 13 Oct 1999 08:40:59 +0800 From: Peter Wemm Message-Id: <19991013004059.CA0C41C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message Da vid Scheidt writes: > : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > : disk devices. There may be other RDBMSes that do this. > > EVERY RDBMS that I've ever seen or had to make work with my drivers > has been on the raw partition. This is because the database writers > DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic > nature of disk writing. Are you sure that Sybase uses BLOCK devices > and not CHAR devices? Sybase is supposed to be run on char devices. The Linux sybase release notes refer to "Unfortunately Linux does not have raw (char) disk devices so we have to make do". Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 18:31:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 21C7814E66 for ; Tue, 12 Oct 1999 18:31:50 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA23709; Tue, 12 Oct 1999 21:31:39 -0400 (EDT) Message-ID: <3803E08F.90021F01@acm.org> Date: Tue, 12 Oct 1999 21:29:51 -0400 From: Jim Bloom X-Mailer: Mozilla 4.61 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Still waiting for xl driver reports References: <199910102059.QAA24189@skynet.ctr.columbia.edu> <19991012155640.A448@enst.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I keep seeing a watchdog timeout with my 3c905B-TX every time the machine boots. It seems to occur after everything has been probed and /etc/rc has completed; around the time I get my login banner. I am running the dhcp client to get my IP address. I don't pound on the network very much so I can't tell you how performance is. Jim Bloom Pierre Beyssac wrote: > > On Sun, Oct 10, 1999 at 04:59:34PM -0400, Bill Paul wrote: > > A while back I posted a message here saying that I'd changed the xl driver > > a bit to hopefully improve performance for 3c90xB and later adapters (i.e. > > the "cyclone," "hurricane" and "tornado" chipsets). I asked for people > > to report if the changes helped, hurt, made no difference or were totally > > broken. > > > > So far not one person has said so much as a word to me on this subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 18:46: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E2FB514E64 for ; Tue, 12 Oct 1999 18:45:57 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA46193 for ; Tue, 12 Oct 1999 21:46:12 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 12 Oct 1999 21:46:12 -0400 (EDT) From: Chuck Robey To: current@FreeBSD.org Subject: COMMAND_SET ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, and I found something called a COMMAND_SET, and I can't figure out what it means. Any takers? ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 20:14:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (Postfix) with ESMTP id C0E1414E45 for ; Tue, 12 Oct 1999 20:14:33 -0700 (PDT) (envelope-from myself@conterra.com) Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48]) by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id XAA26947; Tue, 12 Oct 1999 23:14:32 -0400 (EDT) Received: (from myself@localhost) by dmaddox.conterra.com (8.9.3/8.9.1) id XAA26617; Tue, 12 Oct 1999 23:14:19 -0400 (EDT) (envelope-from myself) Date: Tue, 12 Oct 1999 23:14:18 -0400 From: "Donald J . Maddox" To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: COMMAND_SET ? Message-ID: <19991012231418.A26579@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's defined in sys/boot/common/bootstrap.h. I think all you want to know is in that file. On Tue, Oct 12, 1999 at 09:46:12PM -0400, Chuck Robey wrote: > I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, > and I found something called a COMMAND_SET, and I can't figure out what it > means. Any takers? > > ---------------------------------------------------------------------------- > Chuck Robey | Interests include C programming, Electronics, > 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. > Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and > (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) > ---------------------------------------------------------------------------- > > > > 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 Oct 12 20:59: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 3D00A14C18; Tue, 12 Oct 1999 20:58:55 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.032 #1) id 11bFYy-0009hp-00; Wed, 13 Oct 1999 04:58:52 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.032 #1) id 11bFYx-00014u-00; Wed, 13 Oct 1999 04:58:51 +0100 Date: Wed, 13 Oct 1999 04:58:51 +0100 From: Ben Smithurst To: "Jonathan M. Bresler" Cc: current@freebsd.org Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991013045850.A4025@strontium.scientia.demon.co.uk> References: <199910110107.SAA22856@kithrup.com> <19991011124621.A3A0114BEB@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991011124621.A3A0114BEB@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan M. Bresler wrote: > i do NOT send the person mail to inform them that the are > being removed from the mailing lists, because their email is bouncing. How about sending a message to them once every 24 hours for, say, a week? I imagine some of those bounces are due to temporary mis-configurations which will soon be fixed. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 21:37:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 20B4814C01; Tue, 12 Oct 1999 21:37:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA31455; Tue, 12 Oct 1999 22:37:32 -0600 (MDT) (envelope-from ken) Message-Id: <199910130437.WAA31455@panzer.kdm.org> Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991013045850.A4025@strontium.scientia.demon.co.uk> from Ben Smithurst at "Oct 13, 1999 04:58:51 am" To: ben@scientia.demon.co.uk (Ben Smithurst) Date: Tue, 12 Oct 1999 22:37:32 -0600 (MDT) Cc: jmb@hub.freebsd.org (Jonathan M. Bresler), current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote... > Jonathan M. Bresler wrote: > > > i do NOT send the person mail to inform them that the are > > being removed from the mailing lists, because their email is bouncing. > > How about sending a message to them once every 24 hours for, say, > a week? I imagine some of those bounces are due to temporary > mis-configurations which will soon be fixed. I dunno what jmb's general experience is, but my experience from the 15 or so lists that I manage is that most bounces are from people who switch ISPs, etc., and don't unsubscribe. (Quota violations are another popular cause nowadays.) It generally isn't worth the effort to send mail informing them of the fact that they've been unsubscribed, since it'll almost always keep bouncing. They'll figure it out when they stop getting mail, if they care about the list. Things might be different, of course, for the FreeBSD lists since people on these lists are generally much more clueful. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 12 23:46:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from bsd.kam.pl (bsd.kam.pl [195.205.77.13]) by hub.freebsd.org (Postfix) with ESMTP id A73D514C7F for ; Tue, 12 Oct 1999 23:45:43 -0700 (PDT) (envelope-from mariusz@kam.pl) Received: from localhost (mariusz@localhost) by bsd.kam.pl (8.9.3/8.9.3) with SMTP id IAA76773 for ; Wed, 13 Oct 1999 08:29:48 +0200 (CEST) Date: Wed, 13 Oct 1999 08:29:48 +0200 (CEST) From: mariusz To: current@freebsd.org Subject: Freebsd 4.0 and Linux 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 What depth of FreeBSD's support for Linux applications under FreeBSD 4.0? I can't seem to find adequate information online. Does the support comply with our current requirements for Linux?: minimum kernel version: 2.0.34 minimum glibc version: 2.0.7-19 Mariusz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 0:46:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 97A5014ECF for ; Wed, 13 Oct 1999 00:46:12 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA02826; Wed, 13 Oct 1999 03:45:40 -0400 Date: Wed, 13 Oct 1999 03:45:40 -0400 (EDT) From: Mike Nowlin To: mariusz Cc: current@FreeBSD.ORG Subject: Re: Freebsd 4.0 and Linux 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 > What depth of FreeBSD's support for Linux applications under > FreeBSD 4.0? I can't seem to find adequate information online. > Does the support comply with our current requirements for Linux?: > > minimum kernel version: 2.0.34 > minimum glibc version: 2.0.7-19 Depends on what you mean by "support"... As for binary compatibility, I can't say -- haven't tried it. If you're compiling from source, forget the version numbers - it all depends on exactly what you need, especially when it comes to glibc. FreeBSD (even 3.x) has had support for a long time for some of the functions that are "new" to recent versions of glibc. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 1:17: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1528514C2E for ; Wed, 13 Oct 1999 01:17:00 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA81066; Wed, 13 Oct 1999 09:19:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 13 Oct 1999 09:19:04 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: Jason DiCioccio , current@FreeBSD.ORG Subject: Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org In-Reply-To: <199910122312.RAA99894@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999, Warner Losh wrote: > In message Doug Rabson writes: > : Due to the nature of the pnp code, it might be probed as ed1 instead of > : ed0. > > I have a SBC here that has an onboard PNP ne2000 chip on it. It comes > up as ed1 because I have ed0 at a wired address. I don't see ed0 at > all, and it just works, so I just hacked my rc.conf to use ed1 rather > than ed0 like I did when it ran 3.3R. > > Now for the obligitory tangent: > Does FreeBSD have the ability to reassign IRQs for PNP devices? I > have one that is coming up at IRQ 5, but I have a non-PNP device that > is at 5, but many other IRQs free. There is no way in the BIOS to set > which IRQs are used for PNP and which ones are designated for legacy > devices. Right now, one can hack isa_find_irq() to restrict which interrupts it checks. I have been thinking about using a loader environment variable for this. One existing problem is that a pci device which doesn't match a driver does not reserve its irq resource. Fixing that still leaves the case of an unknown non-pnp isa device though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 1:26: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0632414A06 for ; Wed, 13 Oct 1999 01:26:05 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA92560; Wed, 13 Oct 1999 09:28:21 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 13 Oct 1999 09:28:21 +0100 (BST) From: Doug Rabson To: Chuck Robey Cc: current@freebsd.org Subject: Re: COMMAND_SET ? 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 Tue, 12 Oct 1999, Chuck Robey wrote: > I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, > and I found something called a COMMAND_SET, and I can't figure out what it > means. Any takers? COMMAND_SET is a macro which is used to build the list of commands supported by the loader. The in-kernel pnp code is in sys/isa/{pnp.c,pnpparse.c,isa_common.c}. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 4: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 6C30D14A21 for ; Wed, 13 Oct 1999 04:03:00 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id HAA48204; Wed, 13 Oct 1999 07:02:41 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <199910131102.HAA48204@blackhelicopters.org> Subject: Re: How to report problems (was: Request for Flames) In-Reply-To: <19991013094110.T78191@freebie.lemis.com> from Greg Lehey at "Oct 13, 1999 9:41:10 am" To: grog@lemis.com (Greg Lehey) Date: Wed, 13 Oct 1999 07:02:41 -0400 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Greg, Actually, I used your page (or its predecessor, it looks different now) back when I started. ;) I'd like to do something more detailed on each type of problem. Eventually, I'd like to turn this into a troubleshooting helper for the most common problems. But information gathering is the first step. Yes, "troubleshooting wizards" might be beneath FreeBSD's target market, but with the sort of questions we get on -questions -- or even -hackers -- I think it would be worthwhile. Anything to slow the growth of the mailing lists. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 4:20:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 4503E14EFF for ; Wed, 13 Oct 1999 04:20:36 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id SAA00298; Wed, 13 Oct 1999 18:20:12 +0700 (NOVST) (envelope-from nnd) Date: Wed, 13 Oct 1999 18:20:12 +0700 (NOVST) Message-Id: <199910131120.SAA00298@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' X-Newsgroups: itfs.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Chris D. Faulhaber wrote: > On Mon, 11 Oct 1999, Nickolay Dudorov wrote: > >> Does anybody successfully use ports/sysutils/{lmmon|chm} >> with the Abit's BP6 motherboard ? >> >> After 'make install'-ing ports and adding >> >> controller smbus0 >> controller iicbus0 >> controller iicbb0 >> controller intpm0 >> device smb0 at smbus? >> >> to kernel config file (and config, make depend, make, make install, >> reboot the new kernel) I only receive: >> >> IOCTL: device not configured >> >> from lmmon and chm. >> > > This is due to the intpm controller not configuring the motherboards PM > controller, not because the software. > > I emailed Takanori Watanabe a while back concerning this MB. His thoughts > were that: 1) He hadn't heard of the driver working in an SMP environment; > 2) It may be due to the controller using an unconfigured ISA interface. Additional information: When I remove one of the CPUs and boot UP kernel on the same motherboard both 'chm' and 'lmmon' starts to work (also showed values for -5V and -12V looks strange). So the problems is in driver not working in SMP system. Are there any (general) hints where to look for such UP/SMP problems ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 4:41:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id EA6F014A15 for ; Wed, 13 Oct 1999 04:41:36 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 67B2E9B22; Wed, 13 Oct 1999 07:41:35 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 5EDCFBA1C; Wed, 13 Oct 1999 07:41:35 -0400 (EDT) Date: Wed, 13 Oct 1999 07:41:35 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' In-Reply-To: <199910131120.SAA00298@wint.itfs.nsk.su> 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, 13 Oct 1999 nnd@mail.nsk.ru wrote: > Additional information: > > When I remove one of the CPUs and boot UP kernel on the same > motherboard both 'chm' and 'lmmon' starts to work (also showed > values for -5V and -12V looks strange). > That's due to the conversion factors for the chips on the BP6 being different than that of the LM78/79; simple fix if someone can test the results. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 4:53:54 1999 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 218621504B for ; Wed, 13 Oct 1999 04:53:44 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id UAA26064; Wed, 13 Oct 1999 20:53:11 +0900 (JST) Message-Id: <199910131153.UAA26064@shidahara1.planet.sci.kobe-u.ac.jp> To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' In-reply-to: Your message of "Wed, 13 Oct 1999 18:20:12 +0700" References: <199910131120.SAA00298@wint.itfs.nsk.su> Date: Wed, 13 Oct 1999 20:53:10 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910131120.SAA00298@wint.itfs.nsk.su>, nnd@mail.nsk.ru wrote: >In Chris D. >Faulhaber wrote: >When I remove one of the CPUs and boot UP kernel on the same >motherboard both 'chm' and 'lmmon' starts to work (also showed >values for -5V and -12V looks strange). Probably the Hardware sensor is not LM78/79 but W83781. > So the problems is in driver not working in SMP >system. Are there any (general) hints where to look for >such UP/SMP problems ? I know the problem,but I cannot find out how it could be solved. The reason is the driver does not catch intrrupt. Wait a few days. I'll make a patch so that you can use polling mode for 'intpm'. Takanori Watanabe 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 Wed Oct 13 5:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 50F9314CBB for ; Wed, 13 Oct 1999 05:29:41 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 63129 invoked from network); 13 Oct 1999 12:29:24 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 13 Oct 1999 12:29:24 -0000 Message-ID: <38047B0A.CC0C61BD@pipeline.ch> Date: Wed, 13 Oct 1999 14:28:58 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Brad Knowles Cc: "Jonathan M. Bresler" , scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch References: <19991012142522.57A98152AF@hub.freebsd.org> <38038AA5.45796B87@pipeline.ch> <380395E7.2D38E200@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 10:11 PM +0200 1999/10/12, Andre Oppermann wrote: > > They must be crazy to run a several million recipients > > mailing list with sendmail... > > You don't know all the hacks that they made to sendmail to make > it perform at previously unheard of levels. ;-) Preciously unheard levels for sendmail? Who want's spend weeks or days of sendmail tuning to get a peak performace of x when it takes ten minutes to download and install qmail or postfix which delivers that as sustained performance?? > If you want to see some of the ideas that I got from them (and > others), take a look at the paper I presented at SANE'98 entitled > "Sendmail Performance Tuning for Large Systems" at > . Nice paper! Most of the suggestions are already realized in qmail and postfix. The best is on page three, "handle at least tens of thousands messages per day per server"... About a year ago I tested qmail's performace with two old 486DX100/16MB/2GBIDE and 10BaseT ethernet. Guess what I was able to pump through them? 300'000 unique messages of about 3KB in 24 hours. Guess what my current production server can handle a day (PII-350/256MB/54GBSCSIRAID0+1)? About 2.5 million (too bad I don't have a T3). These numbers include the local deliveries to the maildir. > There > are a number of additional enhancements that they made that I still > can't talk about, however. As long as these additional performance enhancements are not public available I don't care. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 5:33:11 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 4F0CF14BF1; Wed, 13 Oct 1999 05:33:10 -0700 (PDT) From: "Jonathan M. Bresler" To: ben@scientia.demon.co.uk Cc: current@freebsd.org In-reply-to: <19991013045850.A4025@strontium.scientia.demon.co.uk> (message from Ben Smithurst on Wed, 13 Oct 1999 04:58:51 +0100) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991013123310.4F0CF14BF1@hub.freebsd.org> Date: Wed, 13 Oct 1999 05:33:10 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben, Majordomo has this facility, sending periodic reminder messages; it is the bounces mailing list . I used it for a couple months. The results were less than satisfactory. Most people stayed on the bounces mailing list indefinately. ;( jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 5:35:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 2BB5A14FEB for ; Wed, 13 Oct 1999 05:35:32 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from rtci.com (saoshyant@asho.zarathushtra.org [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3/8.9.3) with ESMTP id IAA19269 for ; Wed, 13 Oct 1999 08:36:38 -0400 (EDT) Message-ID: <38047C8E.C40D99BA@rtci.com> Date: Wed, 13 Oct 1999 08:35:26 -0400 From: Thomas Stromberg X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Still waiting for xl driver reports References: <199910102059.QAA24189@skynet.ctr.columbia.edu> <19991012155640.A448@enst.fr> <3803E08F.90021F01@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bloom wrote: > > I keep seeing a watchdog timeout with my 3c905B-TX every time the machine > boots. It seems to occur after everything has been probed and /etc/rc has > completed; around the time I get my login banner. I am running the dhcp client > to get my IP address. I don't pound on the network very much so I can't tell > you how performance is. > > Jim Bloom I get the same.. dmesg: ------ xl0: <3Com 3c905C-TX Fast Etherlink XL> irq 11 at device 14.0 on pci0 xl0: Ethernet address: 00:50:da:07:87:4c .. sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) changing root device to wd0s1a WARNING: / was not properly dismounted xl0: watchdog timeout xl0: promiscuous mode enabled xl0: watchdog timeout uname: ------ FreeBSD asho.zarathushtra.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Oct 12 14:23:39 EDT 1999 saoshyant@asho.zarathushtra.org:/usr/src/sys/compile/SPENTA_MAINYU i386 -- ======================================================================= Thomas Stromberg, Assistant IS Manager / Systems Guru smtp://tstromberg@rtci.com Research Triangle Commerce, Inc. pots://919.380.9771 x3210 ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 5:49: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 262FD14D0A; Wed, 13 Oct 1999 05:48:55 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from rtci.com (saoshyant@asho.zarathushtra.org [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3/8.9.3) with ESMTP id IAA19390; Wed, 13 Oct 1999 08:50:00 -0400 (EDT) Message-ID: <38047FB1.D7B282AD@rtci.com> Date: Wed, 13 Oct 1999 08:48:49 -0400 From: Thomas Stromberg X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-security@freebsd.org, peter@freebsd.org Subject: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile ------------------------------------------------------------------------ 1.2 Sun Oct 10 15:08:35 1999 UTC by peter CVS Tags: HEAD Diffs to 1.1 FILE REMOVED Nuke the old antique copy of ipfilter from the tree. This is old enough to be dangerous. It will better serve us as a port building a KLD, ala SKIP. ------------------------------------------------------------------------ Although a heads up in -CURRENT or -security about this would of been nice, ye old ipfilter is gone. I definitely cannot disagree with the fact that it is an antique copy, and it's a shame that no one seems to be taking care of it in the tree. At least in the past, ipfilter was for many a much better option then ipfw. Has ipfw improved to the point where it functions better as a company firewall then ipfilter? (Okay, so the group & user firewalling is neat, but not really applicable for a corporate border firewall) ipfilters website: http://coombs.anu.edu.au/~avalon/ip-filter.html For why I feel ipfilter is better then ipfw (this post was written back in December '98, ipfw may have changed greatly since): http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current (the big 'wanton atticizing discussion') A summary of it being: - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. - Better logging then ipfw (has ipfw improved? Thats why I switched to ipfilter in the first place) It's a shame that no one seems to want to maintain ipfilter in our tree. As far as a 'port building kld', I think this may not be the 'smartest' way, seeing as anyone who is running a serious firewall would disable kld's immediately anyhow. So my question is, what's the direction we're taking here? -- ======================================================================= Thomas Stromberg, Assistant IS Manager / Systems Guru smtp://tstromberg@rtci.com Research Triangle Commerce, Inc. pots://919.380.9771 x3210 ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 6: 1:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (Postfix) with ESMTP id 4E9C914BF1; Wed, 13 Oct 1999 06:01:05 -0700 (PDT) (envelope-from avalon@cheops.anu.edu.au) Received: (from avalon@localhost) by cheops.anu.edu.au (8.9.1/8.9.1) id XAA05892; Wed, 13 Oct 1999 23:02:54 +1000 (EST) From: Darren Reed Message-Id: <199910131302.XAA05892@cheops.anu.edu.au> Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) To: tstromberg@rtci.com (Thomas Stromberg) Date: Wed, 13 Oct 1999 23:02:53 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG, peter@FreeBSD.ORG In-Reply-To: <38047FB1.D7B282AD@rtci.com> from "Thomas Stromberg" at Oct 13, 99 08:48:49 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if someone had of answered my question (to cvs-committers) about getting an account fixed up on freefall(?) so I could use cvs again, it might not have been forgotten about for quite so long. Maybe I sent the question to the "wrong place", but I received no answer to even indicate that! hmpf! On a conspirital note, I think there are numerous ipfw advocates within freebsd who hate that ipfilter is better >;-) Both NetBSD and OpenBSD ship with it, and if you're serious about security, maybe you should be using OpenBSD anyway, rather than FreeBSD. Darren In some mail from Thomas Stromberg, sie said: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile > ------------------------------------------------------------------------ > 1.2 Sun Oct 10 15:08:35 1999 UTC by peter > CVS Tags: HEAD > Diffs to 1.1 > FILE REMOVED > > Nuke the old antique copy of ipfilter from the tree. This is old enough > to be dangerous. It will better serve us as a port building a KLD, > ala SKIP. > ------------------------------------------------------------------------ > > Although a heads up in -CURRENT or -security about this would of been > nice, ye old ipfilter is gone. I definitely cannot disagree with the > fact that it is an antique copy, and it's a shame that no one seems to > be taking care of it in the tree. At least in the past, ipfilter was for > many a much better option then ipfw. Has ipfw improved to the point > where it functions better as a company firewall then ipfilter? (Okay, so > the group & user firewalling is neat, but not really applicable for a > corporate border firewall) > > ipfilters website: http://coombs.anu.edu.au/~avalon/ip-filter.html > > For why I feel ipfilter is better then ipfw (this post was written back > in December '98, ipfw may have changed greatly since): > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current > (the big 'wanton atticizing discussion') > > A summary of it being: > > - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with > FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. > - Better logging then ipfw (has ipfw improved? Thats why I switched to > ipfilter in the first place) > > It's a shame that no one seems to want to maintain ipfilter in our tree. > As far as a 'port building kld', I think this may not be the 'smartest' > way, seeing as anyone who is running a serious firewall would disable > kld's immediately anyhow. > > So my question is, what's the direction we're taking here? > > -- > ======================================================================= > Thomas Stromberg, Assistant IS Manager / Systems Guru > smtp://tstromberg@rtci.com Research Triangle Commerce, Inc. > pots://919.380.9771 x3210 > ======================================================================= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" 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 Oct 13 6:45: 4 1999 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 2949614F62 for ; Wed, 13 Oct 1999 06:44:43 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id WAA26528; Wed, 13 Oct 1999 22:44:06 +0900 (JST) Message-Id: <199910131344.WAA26528@shidahara1.planet.sci.kobe-u.ac.jp> To: Kenneth Wayne Culver Cc: current@freebsd.org Subject: Re: Abit's BP6 and 'lmmon' or 'chm' In-reply-to: Your message of "Wed, 13 Oct 1999 09:24:58 -0400" References: Date: Wed, 13 Oct 1999 22:44:05 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kenneth Wayne Culver wrote: >Will this solve the problem that your xmbmon seems to solve? With xmbmon I >can look at the temps for my cpu, but with wmlmmon, it gives me the IOCTL >error. > It can use both ISA interface (by opening /dev/io and banging port 0x295 and 0x296) and SMBus interface. And the ISA interface will work . If you try to use SMBus interface, the same result will be there. But ,with SMBus or with ISA, these are dangerous application. So I think it should be treated with device driver. My experimental driver is http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/sys/lm-dist.tar.gz (May be for a bit older CURRENT) But I wonder how do I specify bus to attach,so that I can prevent a ttaching Hardware monitor to bktr i2c bus. Takanori Watanabe 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 Wed Oct 13 6:56: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 2253B14DBC; Wed, 13 Oct 1999 06:55:58 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id PAA03132; Wed, 13 Oct 1999 15:55:54 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id PAA23413; Wed, 13 Oct 1999 15:55:50 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <38047B0A.CC0C61BD@pipeline.ch> References: <19991012142522.57A98152AF@hub.freebsd.org> <38038AA5.45796B87@pipeline.ch> <380395E7.2D38E200@pipeline.ch> <38047B0A.CC0C61BD@pipeline.ch> Date: Wed, 13 Oct 1999 15:50:50 +0200 To: Andre Oppermann From: Brad Knowles Subject: Re: People getting automatically unsub'ed from -arch Cc: "Jonathan M. Bresler" , scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:28 PM +0200 1999/10/13, Andre Oppermann wrote: >> You don't know all the hacks that they made to sendmail to make >> it perform at previously unheard of levels. ;-) > > Preciously unheard levels for sendmail? No, previously unheard of levels -- period. > Nice paper! Most of the suggestions are already realized in qmail and > postfix. I realize that Postfix already addresses many of these issues. I was involved in the earlier stages of the beta testing for Postfix, and it (and private conversations with Wietse) figured very strongly in the development of the later stages of that paper. In fact, I like to be able to claim that the idea for using Van Jacobsen TCP-style slow-start/bounded exponential backoff for parallelism and queue retries was an idea that I contributed to the development of Postfix, and is one of the many factors that make it superior. Of course, that's starting down a rather religious path that I don't think we want to traverse. > The best is on page three, "handle at least tens of > thousands messages per day per server"... About a year ago I tested > qmail's performace with two old 486DX100/16MB/2GBIDE and 10BaseT > ethernet. And Wietse has done more with less. Again, more on that religious issue that I don't think we want to get started. > As long as these additional performance enhancements are not public > available I don't care. I'm very surprised to hear that, since there are some extensions they've made that I believe will materially change the face of delivering customized content via e-mail, and will change it to the point where it is virtually completely unrecognizable from where we are today. I'm sorry to learn that you don't want to learn about protocol enhancements of this kind of scale. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 7:19:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id A6BB714E24 for ; Wed, 13 Oct 1999 07:19:46 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 64427 invoked from network); 13 Oct 1999 14:19:29 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 13 Oct 1999 14:19:29 -0000 Message-ID: <380494D7.56B8E863@pipeline.ch> Date: Wed, 13 Oct 1999 16:19:03 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Brad Knowles Cc: "Jonathan M. Bresler" , scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch References: <19991012142522.57A98152AF@hub.freebsd.org> <38038AA5.45796B87@pipeline.ch> <380395E7.2D38E200@pipeline.ch> <38047B0A.CC0C61BD@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 2:28 PM +0200 1999/10/13, Andre Oppermann wrote: > > Nice paper! Most of the suggestions are already realized in qmail and > > postfix. > > I realize that Postfix already addresses many of these issues. I > was involved in the earlier stages of the beta testing for Postfix, > and it (and private conversations with Wietse) figured very strongly > in the development of the later stages of that paper. > > In fact, I like to be able to claim that the idea for using Van > Jacobsen TCP-style slow-start/bounded exponential backoff for > parallelism and queue retries was an idea that I contributed to the > development of Postfix, and is one of the many factors that make it > superior. That is something qmail has done since the beginning. > Of course, that's starting down a rather religious path > that I don't think we want to traverse. No. > > The best is on page three, "handle at least tens of > > thousands messages per day per server"... About a year ago I tested > > qmail's performace with two old 486DX100/16MB/2GBIDE and 10BaseT > > ethernet. > > And Wietse has done more with less. Again, more on that > religious issue that I don't think we want to get started. Well, the reason these numbers are so "low" is that qmail fsync()'s every message to the disk. Softupdates was not available at that time. But that's not the point. I was arguing against sendmail, not against postfix. I consider qmail and postfix equal, one is stronger in one direction whereas the other one is stronger in other aspects. I for myselfs choose qmail for reasons I can tell you in private email. I have no intend to "fight" religiously for qmail, the only thing I do is pointing out the strong aspects of qmail/ezmlm for big lists. > > As long as these additional performance enhancements are not public > > available I don't care. > > I'm very surprised to hear that, since there are some extensions > they've made that I believe will materially change the face of > delivering customized content via e-mail, and will change it to the > point where it is virtually completely unrecognizable from where we > are today. > > I'm sorry to learn that you don't want to learn about protocol > enhancements of this kind of scale. I would like, but you just said you would (can) not tell me about it... -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 7:21:19 1999 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 89BB314E24 for ; Wed, 13 Oct 1999 07:21:15 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id XAA53753 for current@freebsd.org; Wed, 13 Oct 1999 23:51:15 +0930 (CST) (envelope-from newton) Date: Wed, 13 Oct 1999 23:51:15 +0930 (CST) From: Mark Newton Message-Id: <199910131421.XAA53753@gizmo.internode.com.au> To: current@freebsd.org Subject: 4.0-CURRENT on Pentium 200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a P200 running -current (from about a week ago) which announces that Pentium Pro MTRR support is enabled at boot time. Is this something I should expect given that the machine isn't running a Pentium Pro? :-) - 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 Wed Oct 13 7:22:11 1999 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 EE4BA14F80 for ; Wed, 13 Oct 1999 07:22:08 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id XAA53769 for current@freebsd.org; Wed, 13 Oct 1999 23:52:07 +0930 (CST) (envelope-from newton) Date: Wed, 13 Oct 1999 23:52:07 +0930 (CST) From: Mark Newton Message-Id: <199910131422.XAA53769@gizmo.internode.com.au> To: current@freebsd.org Subject: Err - scratch that. Braino Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ignore that last message (for reasons which are too damaging to go into in any great depth :-) - mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 7:38:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id CE35A1526F; Wed, 13 Oct 1999 07:38:09 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id QAA21222; Wed, 13 Oct 1999 16:38:07 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id QAA03413; Wed, 13 Oct 1999 16:38:06 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <380494D7.56B8E863@pipeline.ch> References: <19991012142522.57A98152AF@hub.freebsd.org> <38038AA5.45796B87@pipeline.ch> <380395E7.2D38E200@pipeline.ch> <38047B0A.CC0C61BD@pipeline.ch> <380494D7.56B8E863@pipeline.ch> Date: Wed, 13 Oct 1999 16:32:38 +0200 To: Andre Oppermann From: Brad Knowles Subject: Re: People getting automatically unsub'ed from -arch Cc: "Jonathan M. Bresler" , scrappy@hub.org, nate@mt.sri.com, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:19 PM +0200 1999/10/13, Andre Oppermann wrote: > That is something qmail has done since the beginning. With respect to qmail, I have no knowledge of that. I do know that this feature was available in the first public beta of Postfix. It was introduced early in the "alpha" stage of Postfix, which from Wietse would be comparable to the late beta, gamma, or even "release" stages of software from many other authors. > I consider qmail and postfix equal, one is stronger > in one direction whereas the other one is stronger in other aspects. I am not aware of any advantages that qmail has over Postfix. However, I am aware of a number of advantages that I believe Postfix has over qmail. Of course, this is more of that religious issue that we should only get into on private e-mail. > I have no intend to "fight" religiously for qmail, the only > thing I do is pointing out the strong aspects of qmail/ezmlm for > big lists. Support for VERPs definitely has its advantages, and I believe that this has long since been incorporated into Postfix. Of course, I could be wrong -- it's been a very long time since I did much of anything with it, and I could be mis-remembering this feature. > I would like, but you just said you would (can) not tell me about it... At the moment, all I can say is that you should keep a very close eye on the releases of Sendmail Pro. I expect these features to be incorporated into that code first, then make their way into RFCs, and be released as part of the freely available version of sendmail shortly thereafter. Imagine orders of magnitude levels of reduction in the amount of traffic that would have to be transmitted to a remote MTA that serves more than one customer. In fact, you could have MTAs distributed all around the world that have their own portion of the world that they serve, with very small amounts of data (streamed, even) that must be transmitted in order to serve the set of customers. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 7:39:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 21123152FE for ; Wed, 13 Oct 1999 07:39:49 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11bPZF-000HFf-00 for freebsd-current@freebsd.org; Wed, 13 Oct 1999 07:39:49 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: k4 and pam Message-Id: Date: Wed, 13 Oct 1999 07:39:49 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it seems that, sans warning or UPDATE, pam is now used by k4. but the distributed pam.conf has not been hacked to make it obvious how to make all this work. is anyone working on this, or should i? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 8:12: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from jacuzzi.local.mindstep.com (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 679121517C for ; Wed, 13 Oct 1999 08:11:53 -0700 (PDT) (envelope-from patrick@mindstep.com) Received: (qmail 3193 invoked from network); 13 Oct 1999 15:11:43 -0000 Received: from unknown (HELO patrak) (192.168.10.25) by jacuzzi.local.mindstep.com with SMTP; 13 Oct 1999 15:11:43 -0000 Message-ID: <00a801bf158d$421afc20$190aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "David G Andersen" Cc: , , References: <199910131428.KAA11701@khavrinen.lcs.mit.edu> <199910131436.IAA02185@faith.cs.utah.edu> Subject: Re: FreeSSH Date: Wed, 13 Oct 1999 11:11:43 -0400 Organization: MindStep Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, > It strikes me that having the base system be slightly more decomposed > could be advantageous. It would be great to be able to do something like: > > pkg_delete lp > pkg_delete yp > > Has anyone done/tried this in the past, and if so, what was the > reaction? Or what do people think? I realize this sounds a bit like the > "everything is an rpm or dpkg" methodology from Linux, but as long as the > 'base' packages are handled automatically, then it shouldn't impose the > same inconvenience. I think that it would be the next best thing since the package/ports system (as well as a logical step forward). I would love to see most of the things that installed with a "make world" be also registered in the package database. This would make things like upgrading bind, removing sendmail etc a lot easier. However I think that this discussion goes beyond the scope of the "security" mailing list. I copied it to the "current" and "stable" lists as well. I guess the discussion should be held in "current"... Patrick. -- MindStep Corporation www.mindstep.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 8:59: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 196CF15012 for ; Wed, 13 Oct 1999 08:59:04 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA09501; Wed, 13 Oct 1999 08:59:02 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA04379; Wed, 13 Oct 1999 08:59:02 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Oct 1999 08:59:02 -0700 (PDT) Message-Id: <199910131559.IAA04379@vashon.polstra.com> To: tstromberg@rtci.com Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) In-Reply-To: <38047FB1.D7B282AD@rtci.com> References: <38047FB1.D7B282AD@rtci.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38047FB1.D7B282AD@rtci.com>, Thomas Stromberg wrote: > For why I feel ipfilter is better then ipfw (this post was written back > in December '98, ipfw may have changed greatly since): > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current > (the big 'wanton atticizing discussion') > > A summary of it being: > > - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with > FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. > - Better logging then ipfw (has ipfw improved? Thats why I switched to > ipfilter in the first place) And: - IP filter does NAT completely inside the kernel - IP filter has stateful filtering I'd like to see it come back. But that means it has to be brought up to date first. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 9: 9: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8506B14D9D for ; Wed, 13 Oct 1999 09:09:02 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA09563; Wed, 13 Oct 1999 09:09:01 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA04461; Wed, 13 Oct 1999 09:09:00 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Oct 1999 09:09:00 -0700 (PDT) Message-Id: <199910131609.JAA04461@vashon.polstra.com> To: avalon@coombs.anu.edu.au Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) In-Reply-To: <199910131302.XAA05892@cheops.anu.edu.au> References: <199910131302.XAA05892@cheops.anu.edu.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910131302.XAA05892@cheops.anu.edu.au>, Darren Reed wrote: > Well, if someone had of answered my question (to cvs-committers) > about getting an account fixed up on freefall(?) so I could use > cvs again, it might not have been forgotten about for quite so > long. Maybe I sent the question to the "wrong place", but I > received no answer to even indicate that! hmpf! You gave up too easily. Do you think we're some kind of finely tuned engine over here? Send your mail again to root@freebsd.org, and nag them every 3 days until your account is fixed. (Don't bother nagging next week, as everybody will be at FreeBSDCon.) > On a conspirital note, I think there are numerous ipfw advocates > within freebsd who hate that ipfilter is better >;-) I don't think that's it. The fact is, ipfilter was in terrible shape in our source tree. Nobody had done a thing with it since June of 1998. From what I heard, it didn't even work reliably under 3.x. (Did it even compile?) Some of its source files were duplicated in "src/contrib/ipfilter" and "src/sys/netinet", with different versions of the files in the two places. Working on it was basically a nightmare. I know because I did work on it for a client of mine. I'm a big proponent of ipfilter's features. I'd love to see it come back if it were really going to be cleaned up and kept maintained. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 9:12:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 37F1A152BA; Wed, 13 Oct 1999 09:12:22 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 2022C1C4D; Wed, 13 Oct 1999 11:15:22 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 1C8CF381A; Wed, 13 Oct 1999 11:15:22 -0400 (EDT) Date: Wed, 13 Oct 1999 11:15:22 -0400 (EDT) From: Bill Fumerola To: Thomas Stromberg Cc: freebsd-current@freebsd.org, freebsd-security@freebsd.org, peter@freebsd.org Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) In-Reply-To: <38047FB1.D7B282AD@rtci.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Oct 1999, Thomas Stromberg wrote: > So my question is, what's the direction we're taking here? The author was given commit privledges to maintain this in the tree, obviously this was not done. Peter encouraged a KLD port, and I hope someone steps up and makes one. Others have eluded to upgrading it, but I never see those imports. It's a shame, but I'm glad that Peter cleared the bitrot. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Oct 13 9:13:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from news.rdc1.tn.home.com (ha2.rdc1.tn.home.com [24.2.7.67]) by hub.freebsd.org (Postfix) with ESMTP id 0601A15406 for ; Wed, 13 Oct 1999 09:13:08 -0700 (PDT) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by news.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991013161308.RTCJ8996.news.rdc1.tn.home.com@windows> for ; Wed, 13 Oct 1999 09:13:08 -0700 Message-ID: <001a01bf1596$6b4dc600$29100218@micronetinfo.com> From: "Douglas Kuntz" To: References: <199910112143.OAA08646@mrynet.com> <199910122021.NAA01959@vashon.polstra.com> Subject: Iomega Ditto Max Parallel Date: Wed, 13 Oct 1999 12:17:17 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone had any success using the parallel version of the Iomega Ditto Max with current, or is there any support for it? Douglas Kuntz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 9:19:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 5455015289 for ; Wed, 13 Oct 1999 09:19:30 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA22793; Wed, 13 Oct 1999 09:18:23 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 13 Oct 1999 09:18:23 -0700 Date: Wed, 13 Oct 1999 09:18:23 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: mariusz Cc: current@freebsd.org Subject: Re: Freebsd 4.0 and Linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: mariusz@kam.pl,current@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This for -questions, but 3.3-STABLE does so presumably current does as well. -Kip On Wed, 13 Oct 1999, mariusz wrote: > Hi > > What depth of FreeBSD's support for Linux applications under > FreeBSD 4.0? I can't seem to find adequate information online. > Does the support comply with our current requirements for Linux?: > > minimum kernel version: 2.0.34 > minimum glibc version: 2.0.7-19 > > Mariusz > > > > 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 Oct 13 9:23:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from umd5.umd.edu (umd5.umd.edu [128.8.10.5]) by hub.freebsd.org (Postfix) with ESMTP id 217B615402 for ; Wed, 13 Oct 1999 09:23:07 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from poirot.umd.edu (poirot.umd.edu [128.8.10.129]) by umd5.umd.edu (8.9.1/8.9.1) with ESMTP id MAA11116; Wed, 13 Oct 1999 12:23:03 -0400 (EDT) Received: from localhost (howardjp@localhost) by poirot.umd.edu (8.9.1/8.9.1) with SMTP id MAA02624; Wed, 13 Oct 1999 12:23:03 -0400 (EDT) X-Authentication-Warning: poirot.umd.edu: howardjp owned process doing -bs Date: Wed, 13 Oct 1999 12:23:03 -0400 (EDT) From: James Howard X-Sender: howardjp@poirot.umd.edu To: Patrick Bihan-Faou Cc: David G Andersen , freebsd-current@FreeBSD.ORG Subject: Re: FreeSSH In-Reply-To: <00a801bf158d$421afc20$190aa8c0@local.mindstep.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Oct 1999, Patrick Bihan-Faou wrote: > Hi All, > > > It strikes me that having the base system be slightly more decomposed > > could be advantageous. It would be great to be able to do something like: > > > > pkg_delete lp > > pkg_delete yp > > > > Has anyone done/tried this in the past, and if so, what was the > > reaction? Or what do people think? I realize this sounds a bit like the > > "everything is an rpm or dpkg" methodology from Linux, but as long as the > > 'base' packages are handled automatically, then it shouldn't impose the > > same inconvenience. I just pulled -security and -stable from the CC. I was talking with a friend of mine the other day about making FreeBSD more modular. It would be great if the system were based on "packages" (not like the ports tree, architectually like the current tree, but organizationally like the ports tree). You could have a "net" package (telnet, tn3270, ftp, finger, etc), an "nw" package (which included all new Netware stuff), an xpg compatability package (which has lots of things need for XPG compatability), the yp and lp packages listed above are a good idea, and development package (gdb, lint, etc), a mail package (mail, vacation, biff, comsat, sendmail etc) a perl package, and anything else anyone else wants to abstract out. Then make the "base" anything absolutely required to have an operational system. This has the benefit of allowing the tree to grow and include new functionality and prevent software from being pulled out and stuck in ports (things like stat, tn3270, are much more convient when then are in the tree). A more or less randomly thought out email message. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 9:32:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from sivka.rdy.com (sivka.rdy.com [205.149.170.6]) by hub.freebsd.org (Postfix) with ESMTP id CB1D7151E3; Wed, 13 Oct 1999 09:31:07 -0700 (PDT) (envelope-from dima@sivka.rdy.com) Received: (from dima@localhost) by sivka.rdy.com (8.9.3/8.9.3) id JAA59143; Wed, 13 Oct 1999 09:29:19 -0700 (PDT) (envelope-from dima) Message-Id: <199910131629.JAA59143@sivka.rdy.com> Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) In-Reply-To: <199910131302.XAA05892@cheops.anu.edu.au> from Darren Reed at "Oct 13, 1999 11:02:53 pm" To: Darren Reed Date: Wed, 13 Oct 1999 09:29:19 -0700 (PDT) Cc: Thomas Stromberg , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG, peter@FreeBSD.ORG Organization: HackerDome Reply-To: dima@rdy.com From: dima@rdy.com (Dima Ruban) 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 Darren Reed writes: > Well, if someone had of answered my question (to cvs-committers) > about getting an account fixed up on freefall(?) so I could use > cvs again, it might not have been forgotten about for quite so > long. Maybe I sent the question to the "wrong place", but I > received no answer to even indicate that! hmpf! Well, Mark Murray sent heads up note quite a while ago about freebsd.org being converted to use krb5. Send him email and I'm sure he'll help you to fix things. > On a conspirital note, I think there are numerous ipfw advocates > within freebsd who hate that ipfilter is better >;-) Both NetBSD and > OpenBSD ship with it, and if you're serious about security, maybe > you should be using OpenBSD anyway, rather than FreeBSD. Let's not start a flame war here. You posted it to FreeBSD mailing list. I think it's fairly easy to imagine peoples reaction. > > Darren > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 9:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 7243F14BFA; Wed, 13 Oct 1999 09:34:09 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id SAA10521; Wed, 13 Oct 1999 18:33:46 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 8ED13D226; Wed, 13 Oct 1999 18:33:45 +0200 (CEST) Message-ID: <19991013183345.A24019@enst.fr> Date: Wed, 13 Oct 1999 18:33:45 +0200 From: Pierre Beyssac To: Patrick Bihan-Faou , David G Andersen Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: FreeSSH References: <199910131428.KAA11701@khavrinen.lcs.mit.edu> <199910131436.IAA02185@faith.cs.utah.edu> <00a801bf158d$421afc20$190aa8c0@local.mindstep.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <00a801bf158d$421afc20$190aa8c0@local.mindstep.com>; from Patrick Bihan-Faou on Wed, Oct 13, 1999 at 11:11:43AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -security trimmed from Cc: ] On Wed, Oct 13, 1999 at 11:11:43AM -0400, Patrick Bihan-Faou wrote: > > pkg_delete lp > > pkg_delete yp > > > > Has anyone done/tried this in the past, and if so, what was the > > reaction? Or what do people think? I realize this sounds a bit like the > > "everything is an rpm or dpkg" methodology from Linux, but as long as the > > 'base' packages are handled automatically, then it shouldn't impose the > > same inconvenience. > > I think that it would be the next best thing since the package/ports system > (as well as a logical step forward). I would love to see most of the things > that installed with a "make world" be also registered in the package > database. This would make things like upgrading bind, removing sendmail etc > a lot easier. There are a _lot_ of pitfalls to this kind of approach, as I have discovered using Linux Debian. This would probably open a can of worms you have no idea of. IMHO, the single biggest mistake in Debian is the all-encompassing package system which can make your life miserable in no time. I have found this the hard way, because I have to administer a network of Debian PCs. Any attempt to upgrade something, even a minor application, rapidly turns into a dependency nigthmare forcing you to update half of your system. This is made even worse by endless changes in the glibc, itself included in the package system: since you can code that dependency in the package system, many packages require such and such version of the glibc. In turn, frequent incompatible updates of the glibc are made by the developpers with the excuse that it's all handled by the package system anyway... To that, you can add several other flaws (broken stable vs unstable policy, no /usr/local, many installation scripts asking for interactive input...). The bottom line is: I'm much happier with FreeBSD's use of distributions for the base system than with a Debian-style package system. That is no to say there can be no good package system, but we have to think twice before we implement anything like that, first and foremost dependencies on system libraries. And, IMHO, package handling for general-purpose applications and package handling for the core system are a very different problem and should be handled in very different ways. The Solaris way, while far from perfect, is at least usable for the most past to handle choice at installation and (not too frequent) evolutions of system components. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 10: 4:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from jacuzzi.local.mindstep.com (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 71C2514F4B for ; Wed, 13 Oct 1999 10:04:12 -0700 (PDT) (envelope-from patrick@mindstep.com) Received: (qmail 3284 invoked from network); 13 Oct 1999 17:04:11 -0000 Received: from unknown (HELO patrak) (192.168.10.25) by jacuzzi.local.mindstep.com with SMTP; 13 Oct 1999 17:04:11 -0000 Message-ID: <011801bf159c$f80630e0$190aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Pierre Beyssac" , "David G Andersen" Cc: , References: <199910131428.KAA11701@khavrinen.lcs.mit.edu> <199910131436.IAA02185@faith.cs.utah.edu> <00a801bf158d$421afc20$190aa8c0@local.mindstep.com> <19991013183345.A24019@enst.fr> Subject: Re: package-like feature for the base distrib (was Re: FreeSSH) Date: Wed, 13 Oct 1999 13:04:10 -0400 Organization: MindStep Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, From: Pierre Beyssac > There are a _lot_ of pitfalls to this kind of approach, as I have > discovered using Linux Debian. This would probably open a can of > worms you have no idea of. IMHO, the single biggest mistake in > Debian is the all-encompassing package system which can make your > life miserable in no time. [...] I was not talking about things that constitute the "real" core of the distribution (kernel, basic libraries etc.). I was more thinking about "userland" stuff that is included in the distribution but might not be required by everybody. Sendmail for example is something I don't want since I user qmail. However I have to remove it by hand... Other examples are bind or perl. Basically I think anything that has an equivalent and/or an alternate installation method in/via the "ports" system should be registered with the rest of the packages. > And, IMHO, package handling for general-purpose applications and > package handling for the core system are a very different problem > and should be handled in very different ways. Agreed. This is the key. The package/ports system is really great as is. The split between the distribution and the packages/ports is sometime annoying. Again I think this mostly concerns "userland" features that are not required for the core of FreeBSD. Patrick. -- MindStep Corporation www.mindstep.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 10:34:57 1999 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 4DE4514D9D for ; Wed, 13 Oct 1999 10:34:49 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p21-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA07436; Thu, 14 Oct 1999 02:34:41 +0900 (JST) Message-ID: <3804B3D6.2601B8D6@newsguy.com> Date: Thu, 14 Oct 1999 01:31:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: van.woerkom@netcologne.de Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: Re: Proper Whacking & Weeding References: <199910121503.RAA02057@oranje.my.domain> <99Oct13.072458est.40328@border.alcanet.com.au> <199910130036.CAA44765@oranje.my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc van Woerkom wrote: > > Drawback is speed. While CVSup mirrors the CVS repository quite fast > I now need an additional cvs update to sync my source tree with the > CVS repository. And that is quite slow. (But I am working on a > program that will speed up this process) Use a local cvsup daemon, and cvsup the source tree from your cvs repository. Much faster than cvs update. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 10:35: 3 1999 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 26AF3152D3 for ; Wed, 13 Oct 1999 10:34:59 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p21-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA07464; Thu, 14 Oct 1999 02:34:50 +0900 (JST) Message-ID: <3804BA36.4F7FDB7@newsguy.com> Date: Thu, 14 Oct 1999 01:58:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: COMMAND_SET ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, > and I found something called a COMMAND_SET, and I can't figure out what it > means. Any takers? It's a macro. :-) I thought it was defined in that same directory, even. It makes a list that is used to define the so-called builtin commands of loader. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 10:35:23 1999 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 0CE4D153CE for ; Wed, 13 Oct 1999 10:35:15 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p21-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA07480; Thu, 14 Oct 1999 02:34:54 +0900 (JST) Message-ID: <3804BA84.3581A71D@newsguy.com> Date: Thu, 14 Oct 1999 01:59:48 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Doug Rabson Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: COMMAND_SET ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > On Tue, 12 Oct 1999, Chuck Robey wrote: > > > I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled, > > and I found something called a COMMAND_SET, and I can't figure out what it > > means. Any takers? > > COMMAND_SET is a macro which is used to build the list of commands > supported by the loader. The in-kernel pnp code is in > sys/isa/{pnp.c,pnpparse.c,isa_common.c}. Just to be obnoxiously pedantic, that is not strictly true. Loader supports commands not defined with COMMAND_SET. Though Doug might be refering to the alpha loader, of course. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 10:35:28 1999 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 0BDE8153D3; Wed, 13 Oct 1999 10:35:18 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p21-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA07517; Thu, 14 Oct 1999 02:35:00 +0900 (JST) Message-ID: <3804BF83.A3E8D3@newsguy.com> Date: Thu, 14 Oct 1999 02:21:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Thomas Stromberg Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) References: <38047FB1.D7B282AD@rtci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Stromberg wrote: > > It's a shame that no one seems to want to maintain ipfilter in our tree. > As far as a 'port building kld', I think this may not be the 'smartest' > way, seeing as anyone who is running a serious firewall would disable > kld's immediately anyhow. Your concerns notwithstanding, a kld is viable. A kld can be loaded by, well, the loader. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 11:27:40 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B294515289; Wed, 13 Oct 1999 11:27:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A48BC1CD584; Wed, 13 Oct 1999 11:27:33 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Wed, 13 Oct 1999 11:27:33 -0700 (PDT) From: Kris Kennaway To: mariusz Cc: current@freebsd.org Subject: Re: Freebsd 4.0 and Linux 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, 13 Oct 1999, mariusz wrote: > What depth of FreeBSD's support for Linux applications under > FreeBSD 4.0? Pretty good - most things run without problems. But, the only definitive answer is "try it and see". > Does the support comply with our current requirements for Linux?: > > minimum kernel version: 2.0.34 We don't implement the Linux kernel as a whole; it's the API which is implemented in FreeBSD's Linux mode (i.e. system calls). There aren't many differences in this regard between the linux kernel versions. > minimum glibc version: 2.0.7-19 The linux-base port currently installs glibc-2.0.7-29, but you're free to add/remove RPMs as you see fit, just as with linux :-) Kris ---- XOR for AES -- join the campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 11:47:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from weedcon1.cropsci.ncsu.edu (weedcon1.cropsci.ncsu.edu [152.1.207.51]) by hub.freebsd.org (Postfix) with ESMTP id 5295014E14 for ; Wed, 13 Oct 1999 11:45:07 -0700 (PDT) (envelope-from fbsdbob@weedcon1.cropsci.ncsu.edu) Received: (from fbsdbob@localhost) by weedcon1.cropsci.ncsu.edu (8.9.3/8.9.3) id OAA68071; Wed, 13 Oct 1999 14:45:34 -0400 (EDT) (envelope-from fbsdbob) From: FreeBSD Bob Message-Id: <199910131845.OAA68071@weedcon1.cropsci.ncsu.edu> Subject: Re: Why Adaptec 1540 bombing? In-Reply-To: <199910122126.PAA99015@harmony.village.org> from Warner Losh at "Oct 12, 1999 03:26:07 pm" To: imp@village.org (Warner Losh) Date: Wed, 13 Oct 1999 14:45:33 -0400 (EDT) Cc: darrylo@sr.hp.com (Darryl Okahata), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199910122117.OAA06678@mina.sr.hp.com> Darryl Okahata writes: > : If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be > : willing to lend out (if the address is in the US). It's been years > : since I've used it, and so I'm not 100% sure that it still works, > : though. > > Well, I could install 2.2.x onto a disk and see if that works there. > Once I do that, I can then know if it works or not. :-) > > Warner Warner and Darryl..... The 2.2.x series seems to work fine on it (what I am using on that machine now). I also have a 1542C controller that I could try. Would that one be expected to be any different from the 1540A? I also have a Future Domain 16xx controller, and a DPT 2012 series controller (the original dos EISA controller that was in the machine). My goal with the machine (a 1993ish Intel EISA board with 32M ram, Phoenix bios, and badged Groupe Bull) was to try the 3.3 and 4.x builds for some play. I have been running 3.2 or 3.3 on all my other boxes, just fine on IDE controllers. Since I ran across these scsi controllers I was thinking of trying them. The DPT did not run at all. The 1540A did not run the 3.3 or 3.2, but came up fine on 2.2.6 or 2.2.8. That got me to thinking that something had changed in the Adaptec driver and query what and why. Any insights are appreciated. If you need the board for testing, I could probably arrange that, or, if you have a test snapshot I could pick up, I could try that too. What specific info would you need from dmesg (assuming it will go far enough to get some messages) or elsewhere? From memory, I think it got as far as listing the controller and/or drives attached, then went off polling for devices and never came back. It did that from the 3.3-RELEASE and the 4.0-19990918 snap (if I have my numbers correct on the snap). I don't think I tried 3.0/3.1/3.2 on it. Thanks Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 12:24:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4287F14A25 for ; Wed, 13 Oct 1999 12:24:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00417; Wed, 13 Oct 1999 12:15:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910131915.MAA00417@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: Mike Smith , freebsd-current@freebsd.org Subject: Re: SMP stack faults... In-reply-to: Your message of "Tue, 12 Oct 1999 10:27:40 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Oct 1999 12:15:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just a followup question on my question from a week ago or so.... ther was > indeed a stack overflow I'd guess- I check the code path more carefully > and there was a 2KB stack buffer there (oof)- and removing it seemed to > make the problem go away....So the question here is "Shouldn't this have > been a more obvious fault"? There's probably an argument here for putting a guard page below the UP-mode kernel stack, yes. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 12:38:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 741FA14BED for ; Wed, 13 Oct 1999 12:37:57 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial11-147.netcologne.de [195.14.233.147]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id VAA02414; Wed, 13 Oct 1999 21:37:43 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id VAA31168; Wed, 13 Oct 1999 21:38:07 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Wed, 13 Oct 1999 21:38:07 +0200 (CEST) Message-Id: <199910131938.VAA31168@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-current@freebsd.org Cc: greg@lemis.com Subject: make buildworld breaks during vinum compilation Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got a stop here: root@oranje# date; make buildworld Wed Oct 13 15:34:04 CEST 1999 (...) cc -O -pipe -DVINUMDEBUG -g -O -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/vinum -I/usr/obj/usr/src/sys/modules/vinum/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c: In function `vinumioctl': /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:333: too few arguments to function `initsd' *** Error code 1 The verify argument seems missing: root@oranje# grep initsd ../../dev/vinum/* ../../dev/vinum/vinumext.h:int initsd(int, int); ../../dev/vinum/vinumio.h: int verify; /* verify (initsd) */ ../../dev/vinum/vinumioctl.c: return initsd(objno); ../../dev/vinum/vinumrevive.c:initsd(int sdno, int verify) ../../dev/vinum/vinumstate.c: ioctl_reply->error = initsd(objindex, data->verify); /* initialize another block */ Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 12:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id C322714BEF for ; Wed, 13 Oct 1999 12:58:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00582; Wed, 13 Oct 1999 12:50:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910131950.MAA00582@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mariusz Cc: current@freebsd.org Subject: Re: Freebsd 4.0 and Linux In-reply-to: Your message of "Wed, 13 Oct 1999 08:29:48 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Oct 1999 12:50:03 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > What depth of FreeBSD's support for Linux applications under > FreeBSD 4.0? I can't seem to find adequate information online. > Does the support comply with our current requirements for Linux?: > > minimum kernel version: 2.0.34 > minimum glibc version: 2.0.7-19 Current state of the art is somewhere between RedHat 5.2 and RedHat 6.0. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 13:11: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from sparc.sweb.com (ip-150-253.gw.total-web.net [209.186.150.253]) by hub.freebsd.org (Postfix) with ESMTP id 5E0DA1519C; Wed, 13 Oct 1999 13:10:52 -0700 (PDT) (envelope-from zaph0d@sparc.sweb.com) Received: from localhost by sparc.sweb.com (8.9.3/8.9.3) with SMTP id QAA12539; Wed, 13 Oct 1999 16:05:54 -0400 (EDT) Date: Wed, 13 Oct 1999 16:05:53 -0400 (EDT) From: To: Thomas Stromberg Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) In-Reply-To: <38047FB1.D7B282AD@rtci.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 I also must agree for many tasks, IP filter proves superior than IPFW and NATD for many things which I do. It seems much more straightforward, more configurable, and also in many respects more stable and reliable. It would not bother me in the least if they simply yanked ipfw and natd from the src tree, and included ipf/ipnat default (not in contrib). If no one else desires to doso, i'd be happy to maintain whatever communication or porting nessescary to keep it current and included in the standard FreeBSD distribution. On Wed, 13 Oct 1999, Thomas Stromberg wrote: > http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile > ------------------------------------------------------------------------ > 1.2 Sun Oct 10 15:08:35 1999 UTC by peter > CVS Tags: HEAD > Diffs to 1.1 > FILE REMOVED > > Nuke the old antique copy of ipfilter from the tree. This is old enough > to be dangerous. It will better serve us as a port building a KLD, > ala SKIP. > ------------------------------------------------------------------------ > > Although a heads up in -CURRENT or -security about this would of been > nice, ye old ipfilter is gone. I definitely cannot disagree with the > fact that it is an antique copy, and it's a shame that no one seems to > be taking care of it in the tree. At least in the past, ipfilter was for > many a much better option then ipfw. Has ipfw improved to the point > where it functions better as a company firewall then ipfilter? (Okay, so > the group & user firewalling is neat, but not really applicable for a > corporate border firewall) > > ipfilters website: http://coombs.anu.edu.au/~avalon/ip-filter.html > > For why I feel ipfilter is better then ipfw (this post was written back > in December '98, ipfw may have changed greatly since): > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current > (the big 'wanton atticizing discussion') > > A summary of it being: > > - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with > FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. > - Better logging then ipfw (has ipfw improved? Thats why I switched to > ipfilter in the first place) > > It's a shame that no one seems to want to maintain ipfilter in our tree. > As far as a 'port building kld', I think this may not be the 'smartest' > way, seeing as anyone who is running a serious firewall would disable > kld's immediately anyhow. > > So my question is, what's the direction we're taking here? > > -- > ======================================================================= > Thomas Stromberg, Assistant IS Manager / Systems Guru > smtp://tstromberg@rtci.com Research Triangle Commerce, Inc. > pots://919.380.9771 x3210 > ======================================================================= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" 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 Oct 13 13:47:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 907C515405 for ; Wed, 13 Oct 1999 13:47:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA42834; Wed, 13 Oct 1999 14:47:47 -0600 (MDT) (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 OAA45710; Wed, 13 Oct 1999 14:48:46 -0600 (MDT) Message-Id: <199910132048.OAA45710@harmony.village.org> To: FreeBSD Bob Subject: Re: Why Adaptec 1540 bombing? Cc: darrylo@sr.hp.com (Darryl Okahata), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Oct 1999 14:45:33 EDT." <199910131845.OAA68071@weedcon1.cropsci.ncsu.edu> References: <199910131845.OAA68071@weedcon1.cropsci.ncsu.edu> Date: Wed, 13 Oct 1999 14:48:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910131845.OAA68071@weedcon1.cropsci.ncsu.edu> FreeBSD Bob writes: : The DPT did not run at all. I do not have access to the DPT controllers, nor to a EISA system for testing. : The 1540A did not run the 3.3 or 3.2, : but came up fine on 2.2.6 or 2.2.8. That got me to thinking that : something had changed in the Adaptec driver and query what and why. Yes. CAM happened. :-) The 1540A card had some interesting problems with the setting of residuals which the 1540B and later do not have. CAM requires these transfer counts be accurate or it can get confused. I tried to cope as best I could, but without access to an actual card I couldn't verify that it worked. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 15: 5:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 394B414A04 for ; Wed, 13 Oct 1999 15:05:01 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem08.masternet.it [194.184.65.18]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id XAA29065; Wed, 13 Oct 1999 23:29:30 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19991013231839.009f5700@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 13 Oct 1999 23:19:11 +0200 To: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: make buildworld breaks during vinum compilation Cc: greg@lemis.com In-Reply-To: <199910131938.VAA31168@oranje.my.domain> 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 At 13/10/99, Marc van Woerkom wrote: > /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c: In function > `vinumioctl': > /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:333: too few > arguments to function `initsd' > *** Error code 1 Me too ... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 15: 8:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5679614C9A; Wed, 13 Oct 1999 15:08:35 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA10843; Wed, 13 Oct 1999 14:36:33 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA05438; Wed, 13 Oct 1999 14:36:33 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 13 Oct 1999 14:36:29 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: World breakage in libc_r? Cc: dfr@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm building world on an Alpha and have run into this: building shared library libc_r.so.4 sigpending.So: In function `sigpending': sigpending.S:2: multiple definition of `sigpending' uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigpending' changed from 68 to 36 in sigpending.So uthread_sigsuspend.So: In function `sigsuspend': uthread_sigsuspend.c(.text+0x0): multiple definition of `sigsuspend' sigsuspend.So:sigsuspend.S:2: first defined here /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigsuspend' changed from 36 to 236 in uthread_sigsuspend.So *** Error code 1 I know the cause of it and I know the fix. The cause is this: ------------------------------------------------------------------------------- dfr 1999/10/09 05:11:32 PDT Modified files: lib/libc/alpha/sys Makefile.inc Log: Remove old sig* wrappers. Revision Changes Path 1.6 +2 -3 src/lib/libc/alpha/sys/Makefile.inc ------------------------------------------------------------------------------- and the fix is to add sigpending.o and sigsuspend.o to the definition of HIDDEN_SYSCALLS in "src/lib/libc_r/Makefile". But there was a similar commit for the i386 a few hours later, and I haven't heard any complaints about this breakage on i386 systems. I'm reluctant to commit the fix for the Alpha until I understand why not, because it will affect the i386 too. Can any of you shed some light on this? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 16:23:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.utexas.edu (wb1-a.mail.utexas.edu [128.83.126.134]) by hub.freebsd.org (Postfix) with SMTP id 99F3614F8F for ; Wed, 13 Oct 1999 16:22:48 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: (qmail 18902 invoked from network); 13 Oct 1999 23:22:10 -0000 Received: from dial-47-70.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.251.70) by umbs-smtp-1 with SMTP; 13 Oct 1999 23:22:10 -0000 From: Richard Wackerbarth To: current@freebsd.org Subject: Fwd: RE: /dev/smb0 on Dell Latitude Date: Wed, 13 Oct 1999 18:17:20 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: ales@megared.net.mx MIME-Version: 1.0 Message-Id: <99101318203300.08863@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your suggestion. I haven't found anything in the archives that seems to apply. Any help from "current"? ---------- Forwarded Message ---------- Subject: RE: /dev/smb0 on Dell Latitude Date: Wed, 13 Oct 1999 17:53:06 -0500 From: "Alejandro Ramirez" Hi, You should write this question to freebsd-current@freebsd.org, there was some discusion about this. Ales ----- Original Message ----- From: Richard Wackerbarth To: Sent: Wednesday, October 13, 1999 5:09 PM Subject: /dev/smb0 on Dell Latitude > Help! Does anyone have any experience with the smbus on Dell laptops? > This is today's kernel. > > Selected entries in dmesg are below. > > When I attempt to find devices the ioctl returns "Device not configured" on > /dev/smb0. > > > FreeBSD 4.0-CURRENT #9: Wed Oct 13 08:21:53 CDT 1999 > > CPU: Pentium II/Xeon/Celeron (267.27-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x650 Stepping = 0 > Features=0x183f9ff > real memory = 67043328 (65472K bytes) > > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > vga-pci0: irq 11 at device 2.0 on pci0 > pcic0: irq 11 at device 3.0 on pci0 > pcic1: irq 11 at device 3.1 on pci0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ide_pci0: at device 7.1 on pci0 > chip1: irq 11 at device 7.2 on pci0 > intpm0: at device 7.3 on pci0 > intpm0: I/O mapped 840 > intpm0: intr IRQ 9 enabled revision 0 > smbus0: on intsmb0 > smb0: on smbus0 > intpm0: PM I/O mapped 800 > pcm0: at drq 1 flags 0x15 on isa0 > device_probe_and_attach: pcm0 attach returned 6 > devclass_alloc_unit: pcf0 already exists, using next available unit number > pcf0 at port 0x320 irq 5 on isa0 > pcic: pccard bridge VLSI 82C146 (5 mem & 2 I/O windows) > > WARNING: driver smb should register devices with make_dev() (dev_t = "#smb/0") > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Oct 13 17: 0:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 15DD515284 for ; Wed, 13 Oct 1999 17:00:18 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA88754; Thu, 14 Oct 1999 09:29:50 +0930 (CST) Date: Thu, 14 Oct 1999 09:29:50 +0930 From: Greg Lehey To: Marc van Woerkom , Gianmarco Giovannelli Cc: freebsd-current@freebsd.org, greg@lemis.com Subject: Re: make buildworld breaks during vinum compilation Message-ID: <19991014092949.M78191@freebie.lemis.com> References: <199910131938.VAA31168@oranje.my.domain> <4.2.0.58.19991013231839.009f5700@194.184.65.4> <199910131938.VAA31168@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199910131938.VAA31168@oranje.my.domain> 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 13 October 1999 at 21:38:07 +0200, Marc van Woerkom wrote: > I got a stop here: > > root@oranje# date; make buildworld > Wed Oct 13 15:34:04 CEST 1999 > (...) > cc -O -pipe -DVINUMDEBUG -g -O -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/vinum -I/usr/obj/usr/src/sys/modules/vinum/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c > /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c: In function `vinumioctl': > /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:333: too few arguments to function `initsd' > *** Error code 1 On Wednesday, 13 October 1999 at 23:19:11 +0200, Gianmarco Giovannelli wrote: > Me too ... Pass the pointy hat. I forgot to commit one of the files in the last change. I *did* cvsup and recompile after committing, but I didn't notice that there was an M flag for vinumioctl.c :-( It should all be OK now. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 18:13:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 89D3B14E6C; Wed, 13 Oct 1999 18:13:04 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA64179; Wed, 13 Oct 1999 21:12:36 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 13 Oct 1999 21:12:36 -0400 (EDT) From: Chuck Robey To: David Scheidt Cc: Kirk McKusick , Julian Elischer , Bruce Evans , Matthew Dillon , freebsd-arch@FreeBSD.ORG, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: The eventual fate of BLOCK devices. 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 Tue, 12 Oct 1999, David Scheidt wrote: > On Tue, 12 Oct 1999, Kirk McKusick wrote: > > > I would like to take a step back from the debate for a moment and > > ask the bigger question: How many real-world applications actually > > use the block device interface? I know of none whatsoever. All the > > filesystem utilities go out of their way to avoid the block device > > and use the raw interface. Does anyone on this list know of any > > programs that need/want the block interface? If there are none, or > > It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > disk devices. There may be other RDBMSes that do this. Informix, should a miracle occur and they decide to suport FreeBSD, definitely want the same. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 18:14:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B7E471528A; Wed, 13 Oct 1999 18:14:30 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA64183; Wed, 13 Oct 1999 21:14:10 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 13 Oct 1999 21:14:10 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: David Scheidt , Kirk McKusick , Julian Elischer , Bruce Evans , Matthew Dillon , freebsd-arch@FreeBSD.org, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: The eventual fate of BLOCK devices. In-Reply-To: <199910122211.QAA99359@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999, Warner Losh wrote: > In message David Scheidt writes: > : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated > : disk devices. There may be other RDBMSes that do this. > > EVERY RDBMS that I've ever seen or had to make work with my drivers > has been on the raw partition. This is because the database writers > DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic > nature of disk writing. Are you sure that Sybase uses BLOCK devices > and not CHAR devices? Gawd, now that I think of it, about my Informix post, you're right, they use a raw partition, and their own buffering. > > Warner > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 20:59: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id D046F14E56 for ; Wed, 13 Oct 1999 20:59:03 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-160-235.res.iastate.edu (friley-160-235.res.iastate.edu [129.186.160.235]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id D56DC104 for ; Wed, 13 Oct 1999 22:59:02 -0500 (CDT) Received: from friley-160-235.res.iastate.edu (localhost [127.0.0.1]) by friley-160-235.res.iastate.edu (Postfix) with ESMTP id D43D913732 for ; Wed, 13 Oct 1999 22:59:01 -0500 (CDT) To: freebsd-current@freebsd.org Subject: linux emulation broken.. Date: Wed, 13 Oct 1999 22:59:01 -0500 From: Chris Csanady Message-Id: <19991014035901.D43D913732@friley-160-235.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It has been getting worse and worse for me recently. The two applications where it is noticeable are netscape, and word (im)perfect. I was using the linux version of netscape, until recently when it began hanging for long periods of time during network or disk activity. For a while with WP, it was fairly useable, except I could not print with it. Now though, I can't even save files, it hangs at the Save As dialog. I'm sorry I can't be more specific, but with a kernel from today it is still broken. I don't have time to go into it any further right now, but I thought I would check if others are having similar difficulties. I have a lot to do, and it is just extremely irritating right now. I swear, nothing relating to linux ever works.. I have the pleasure of using at it work on a regular basis, and it has been nothing but a complete PITA. So much time wasted. Sorry, I couldn't help including my $0.02 wrt linux.. Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 13 22:28: 8 1999 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 E280415461 for ; Wed, 13 Oct 1999 22:27:59 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id OAA00501; Thu, 14 Oct 1999 14:08:13 +0900 (JST) Message-Id: <199910140508.OAA00501@shidahara1.planet.sci.kobe-u.ac.jp> To: nnd@mail.nsk.ru, cdf.lists@fxp.org, culverk@wam.umd.edu, rkw@dataplex.net Cc: current@freebsd.org Subject: intpm(4) polling patch Date: Thu, 14 Oct 1999 14:08:13 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you get "Device not configured" message, apply following patch and do 'sysctl -w hw.intpm_poll=1'.If your system is SMP, 'hw.intpm_poll' value is 1 as a default.(Not tested.) This is not *the right* solution,but it will work I think. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A --- /home/ctm/src/sys/pci/intpm.c Fri Sep 3 03:16:24 1999 +++ intpm.c Thu Oct 14 12:25:28 1999 @@ -43,9 +43,9 @@ #include #include #include - +#include #include "smbus_if.h" - +#include "smp.h" /*This should be removed if force_pci_map_int supported*/ #include @@ -90,6 +90,9 @@ static int intpm_attach (device_t dev); static devclass_t intsmb_devclass; +static int intpm_poll=0; +SYSCTL_INT(_hw, OID_AUTO, intpm_poll, CTLFLAG_RW, &intpm_poll, 1, ""); + static device_method_t intpm_methods[]={ DEVMETHOD(device_probe,intsmb_probe), DEVMETHOD(device_attach,intsmb_attach), @@ -379,7 +382,7 @@ int error; intrmask_t s; struct intsmb_softc *sc = (struct intsmb_softc *)device_get_softc(dev); - if(cold){ + if(cold||intpm_poll!=0){ /*So that it can use device during probing device on SMBus.*/ error=intsmb_stop_poll(dev); return error; @@ -656,7 +659,10 @@ device_t smbinterface; int rid; struct resource *res; - +#if NSMP>0 + device_printf(dev,"SMP system so polling mode is default\n"); + intpm_poll=1; +#endif sciic=device_get_softc(dev); if(sciic==NULL){ return ENOMEM; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 0:49: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from p.funk.org (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (Postfix) with ESMTP id C9C4014EF1 for ; Thu, 14 Oct 1999 00:49:00 -0700 (PDT) (envelope-from alexlh@p.funk.org) Received: (from alexlh@localhost) by p.funk.org (8.9.3/8.9.3) id JAA00340 for freebsd-current@freebsd.org; Thu, 14 Oct 1999 09:48:53 +0200 (CEST) (envelope-from alexlh) Date: Thu, 14 Oct 1999 09:48:53 +0200 From: Alex Le Heux To: freebsd-current@freebsd.org Subject: Can't make crashdump after panic Message-ID: <19991014094853.A323@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With a kernel from 07:00 (UTC) this morning I started to get a panic every time during the startup of Windowmaker. After configuring the system for making a crashdump, I get "panic: Timeout table full" halfway through the dump. This is on a stock PII system (weirdest hardware is a ZIP drive :), which I'm trying to upgrade from a -current from Sep 17. (install new kernel first, make world after, etc) Can anyone clue me in here? Alex -- +--------------------------------+-------------------+ | SMTP: | E-Gold: 101979 | | ICBM: N52 22.64'6 E4 51.54'1 | PGP: 0x1d512a3f | +--------------------------------+-------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 1: 6:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4F8DA14CD4; Thu, 14 Oct 1999 01:06:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA44117; Thu, 14 Oct 1999 09:09:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 14 Oct 1999 09:09:11 +0100 (BST) From: Doug Rabson To: John Polstra Cc: current@freebsd.org, dfr@freebsd.org Subject: Re: World breakage in libc_r? 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, 13 Oct 1999, John Polstra wrote: > I'm building world on an Alpha and have run into this: > > building shared library libc_r.so.4 > sigpending.So: In function `sigpending': > sigpending.S:2: multiple definition of `sigpending' > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigpending' changed from 68 to 36 in sigpending.So > uthread_sigsuspend.So: In function `sigsuspend': > uthread_sigsuspend.c(.text+0x0): multiple definition of `sigsuspend' > sigsuspend.So:sigsuspend.S:2: first defined here > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigsuspend' changed from 36 to 236 in uthread_sigsuspend.So > *** Error code 1 > > I know the cause of it and I know the fix. The cause is this: > > ------------------------------------------------------------------------------- > dfr 1999/10/09 05:11:32 PDT > > Modified files: > lib/libc/alpha/sys Makefile.inc > Log: > Remove old sig* wrappers. > > Revision Changes Path > 1.6 +2 -3 src/lib/libc/alpha/sys/Makefile.inc > ------------------------------------------------------------------------------- > > and the fix is to add sigpending.o and sigsuspend.o to the > definition of HIDDEN_SYSCALLS in "src/lib/libc_r/Makefile". > > But there was a similar commit for the i386 a few hours later, and I > haven't heard any complaints about this breakage on i386 systems. I'm > reluctant to commit the fix for the Alpha until I understand why not, > because it will affect the i386 too. Can any of you shed some light > on this? I'm pretty sure that this is the right fix. My guess as to why it didn't pop up on i386 is that the old and new implementations were sufficiently close in size that rounding up to 16bytes made them look identical. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 1:33:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 8BBCD14C27 for ; Thu, 14 Oct 1999 01:33:33 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-249.netcologne.de [195.14.235.249]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA00507; Thu, 14 Oct 1999 10:33:31 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id KAA01138; Thu, 14 Oct 1999 10:33:50 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Thu, 14 Oct 1999 10:33:50 +0200 (CEST) Message-Id: <199910140833.KAA01138@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: cc@137.org Cc: freebsd-current@FreeBSD.ORG In-reply-to: <19991014035901.D43D913732@friley-160-235.res.iastate.edu> (message from Chris Csanady on Wed, 13 Oct 1999 22:59:01 -0500) Subject: Re: linux emulation broken.. Reply-To: van.woerkom@netcologne.de References: <19991014035901.D43D913732@friley-160-235.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (im)perfect. I was using the linux version of netscape, until > recently when it began hanging for long periods of time during > network or disk activity. Calling up linux-netscape-4.61 causes my system to freeze for a couple of seconds, then it reboots. This is either related to some recent changes, or my system being not in a consistent state. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 1:46:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.2]) by hub.freebsd.org (Postfix) with ESMTP id 56C7314C27; Thu, 14 Oct 1999 01:45:47 -0700 (PDT) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.7]) by rnocserv.urc.ac.ru (8.9.3/8.9.3) with ESMTP id OAA38519; Thu, 14 Oct 1999 14:35:50 +0600 (ESS) (envelope-from joy@urc.ac.ru) Message-ID: <380595E5.B952B4A8@urc.ac.ru> Date: Thu, 14 Oct 1999 14:35:50 +0600 From: Konstantin Chuguev Organization: Southern Ural Regional Center of FREEnet X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Pierre Beyssac Cc: Patrick Bihan-Faou , David G Andersen , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: FreeSSH References: <199910131428.KAA11701@khavrinen.lcs.mit.edu> <199910131436.IAA02185@faith.cs.utah.edu> <00a801bf158d$421afc20$190aa8c0@local.mindstep.com> <19991013183345.A24019@enst.fr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac wrote: > [ -security trimmed from Cc: ] > > On Wed, Oct 13, 1999 at 11:11:43AM -0400, Patrick Bihan-Faou wrote: > > > pkg_delete lp > > > pkg_delete yp > > > > > > Has anyone done/tried this in the past, and if so, what was the > > > reaction? Or what do people think? I realize this sounds a bit like the > > > "everything is an rpm or dpkg" methodology from Linux, but as long as the > > > 'base' packages are handled automatically, then it shouldn't impose the > > > same inconvenience. > > > > I think that it would be the next best thing since the package/ports system > > (as well as a logical step forward). I would love to see most of the things > > that installed with a "make world" be also registered in the package > > database. This would make things like upgrading bind, removing sendmail etc > > a lot easier. > > There are a _lot_ of pitfalls to this kind of approach, as I have > discovered using Linux Debian. This would probably open a can of > worms you have no idea of. IMHO, the single biggest mistake in > Debian is the all-encompassing package system which can make your > life miserable in no time. > > I have found this the hard way, because I have to administer a > network of Debian PCs. Any attempt to upgrade something, even a > minor application, rapidly turns into a dependency nigthmare forcing > you to update half of your system. This is made even worse by > endless changes in the glibc, itself included in the package system: > since you can code that dependency in the package system, many > packages require such and such version of the glibc. In turn, > frequent incompatible updates of the glibc are made by the developpers > with the excuse that it's all handled by the package system anyway... > > To that, you can add several other flaws (broken stable vs unstable > policy, no /usr/local, many installation scripts asking for > interactive input...). > > The bottom line is: I'm much happier with FreeBSD's use of > distributions for the base system than with a Debian-style package > system. > Well, what about having just the extended set of makefile variables in /etc/make.conf? We already have NOPROFILE, NOPERL, NOSUIDPERL, NOGAMES, NODOC. I would prefer to have two sets of such variables: one is something like BUILD_*, another is INSTALL_*; both for *_LP, *_YP, *_DEVEL, *_PERL etc. Of course there should be BUILD_ALL and INSTALL_ALL. And of course, some of the variables would define other ones implicitly. Then, you will still need to cvs the entire tree (and thus properly synchronized), but won't need to build or install all the stuff every time. And you will have just to choose the necessary subset for each your server, router and/or workstation. If it is done by making targets like build_* and install_* in the source tree, then there is an opportunity to make also the uninstall_* targets for removing unnecessary parts of the distribution. > > That is no to say there can be no good package system, but we have > to think twice before we implement anything like that, first and > foremost dependencies on system libraries. > > And, IMHO, package handling for general-purpose applications and > package handling for the core system are a very different problem > and should be handled in very different ways. > > The Solaris way, while far from perfect, is at least usable for > the most past to handle choice at installation and (not too frequent) > evolutions of system components. > -- > Pierre Beyssac pb@enst.fr > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 2:23:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 93F4F14DB3 for ; Thu, 14 Oct 1999 02:23:42 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA04928 for current@FreeBSD.org; Thu, 14 Oct 1999 11:17:27 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 14 Oct 1999 11:17:18 +0200 From: Marcel Moolenaar Message-ID: <38059F9E.E35DBD6A@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991014035901.D43D913732@friley-160-235.res.iastate.edu> Subject: Re: linux emulation broken.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Csanady wrote: [snip] > it is still broken. I don't have time to go into it any further > right now, but I thought I would check if others are having > similar difficulties. No. > I have a lot to do, and it is just extremely irritating right > now. I swear, nothing relating to linux ever works.. So why do you think the Linuxulator is broken then? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Oct 14 3:20:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 036A714C97; Thu, 14 Oct 1999 03:20:29 -0700 (PDT) (envelope-from kooij@pc47.mpn.cp.philips.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id MAA01958; Thu, 14 Oct 1999 12:20:28 +0200 (MEST) (envelope-from kooij@pc47.mpn.cp.philips.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma001953; Thu, 14 Oct 99 12:20:28 +0200 Received: from pc47.mpn.cp.philips.com (pc47.mpn.cp.philips.com [130.139.64.47]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id MAA13695; Thu, 14 Oct 1999 12:20:27 +0200 (MET DST) Received: from localhost [127.0.0.1] (kooij) by pc47.mpn.cp.philips.com with esmtp (Exim 3.03 #1 (Debian)) id 11bhzm-0002q7-00; Thu, 14 Oct 1999 12:20:26 +0200 Date: Thu, 14 Oct 1999 12:20:26 +0200 (CEST) From: Joost Kooij To: Pierre Beyssac Cc: Patrick Bihan-Faou , David G Andersen , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, jos@hal.mpn.cp.philips.com, Joost van Baal Subject: Debian (was: FreeSSH) In-Reply-To: <19991013183345.A24019@enst.fr> 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 Wed, 13 Oct 1999, Pierre Beyssac wrote: > There are a _lot_ of pitfalls to this kind of approach, as I have > discovered using Linux Debian. This would probably open a can of > worms you have no idea of. IMHO, the single biggest mistake in > Debian is the all-encompassing package system which can make your > life miserable in no time. IMHO this highly depends on your point of view. If you want to to stay in absolute control (and assume all responsibilities for the smooth cooperation for the different parts of your systems), then yes, I agree that the "glue" that Debian adds gets in your way a lot of the time. > I have found this the hard way, because I have to administer a > network of Debian PCs. Any attempt to upgrade something, even a > minor application, rapidly turns into a dependency nigthmare forcing > you to update half of your system. This is made even worse by > endless changes in the glibc, itself included in the package system: > since you can code that dependency in the package system, many > packages require such and such version of the glibc. In turn, > frequent incompatible updates of the glibc are made by the developpers > with the excuse that it's all handled by the package system anyway... Please let's get the terms of this discussion clear first. You are running "stable" Debian aren't you? Debian puts in a lot of effort to make upgrades from one version of "stable" to the next version of "stable" as smooth as possible. If you use tools like apt-get and dselect, this should in practice be painless and mostly flawless. As ever, RTFM and YMMV accordingly. Sometimes people insist on using the dpkg backend in the wrong situations, like when upgrading a whole slew of packages at once. Many times this arises from not understanding or not appreciating tools like dselect and apt-get. Anyway, the bottom line is: keep with "stable" and any signs of dependency problems usually indicate that you are doing something wrong, not Debian. > To that, you can add several other flaws (broken stable vs unstable > policy, no /usr/local, many installation scripts asking for > interactive input...). 1. Debian is very slow to release new "stable" versions. This can be called a "broken release policy", not a "broken stable vs unstable policy". That is a big difference. 2. There is actually a /usr/local. It is reserved to the local admin. No Debian package shall touch what the local admin puts in /usr/local. From Debian's point of view, this makes a lot of sense. To consider this broken is to consider Debian's goals broken. There's little sense in argueing about this IMHO. 3. Installation scripts asking questions is intimately related to the strive to have packages really configuring themselves to be "ready to run" upon installation. In many cases, Debian actually does a fine job here. The problem is now, that Debian is so big and there are a lot of questions asked. There is some work being done, making it possible for packages to ask the questions before or after installation. Still, trying to configure packages means requiring user input at some stage. Again, this is a design goals issue. > The bottom line is: I'm much happier with FreeBSD's use of > distributions for the base system than with a Debian-style package > system. Great. Use whatever works best for you. If you find yourself forced (by the suits of course, because Linux is hype) to work with Debian, here's some tips to make things easier for you: - Stay with "stable". Especially if you're managing a whole network of machines and "reproducible" is a key value to your operation. - Build local versions of packages if stable can't satisfy your needs. This is actually remarkably easy with newer versions[1] of the apt-get tool: apt-get source somepackage fetches and unpacks sources for a package. Then make your mods/patches and type[2]: debian/rules binary in the top-level source directory. You now have a localized version of the package that you can install manually with dpkg. Don't forget to put the package on hold[3], if you want to stop it from being upgraded automatically. [1] If this doesn't work for you, you can always get the .orig.tar.gz, diff.gz and .dsc files by hand and use "dpkg-source -x *.dsc" to achieve the same result. [2] Actually, it's better to type "fakeroot debian/rules binary". Tar needs to create and archive with files owned by root. Fakeroot (from the fakeroot package) tricks tar into thinking you're root when you're not, thus allowing a normal user to build the .deb. [3] echo "hold" | dpkg --set-selections "somepackage" or use dselect. - Use the Debian Bug Tracking system (http://bugs.debian.org) > That is no to say there can be no good package system, but we have > to think twice before we implement anything like that, first and > foremost dependencies on system libraries. I agree again. This sort of decision is made at a very deep level and relates to fundamental design goals. > And, IMHO, package handling for general-purpose applications and > package handling for the core system are a very different problem > and should be handled in very different ways. In this respect, the differences between Debian and FreeBSD are quite revealing: Debian draws the line between kernel- and user-space and completely delegates the former, working on integration of the latter. FreeBSD draws the line at a point in userspace and delegates the user-space-only part, concentrating on the other part. Considering the above, the Debian packaging system may not be the optimal solution to FreeBSD's needs (whatever those may be.) Conversely, FreeBSD's great cvs-based system that allows things like "cvsup" and "make world" are very hard to transpose on Debian as it is. > The Solaris way, while far from perfect, is at least usable for > the most past to handle choice at installation and (not too frequent) > evolutions of system components. Please pass me too that tube of glue you're sniffing. Maybe that'll help me to better reconciliate with default Solaris. Cheers, Joost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 3:23:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id E54D014EEA for ; Thu, 14 Oct 1999 03:23:42 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA19515 for current@FreeBSD.org; Thu, 14 Oct 1999 12:16:47 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 14 Oct 1999 12:16:38 +0200 From: Marcel Moolenaar Message-ID: <3805AD86.B6D2608E@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , Subject: Re: World breakage in libc_r? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > On Wed, 13 Oct 1999, John Polstra wrote: > > > building shared library libc_r.so.4 > > sigpending.So: In function `sigpending': > > sigpending.S:2: multiple definition of `sigpending' > > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here > > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigpending' changed from 68 to 36 in sigpending.So > > uthread_sigsuspend.So: In function `sigsuspend': > > uthread_sigsuspend.c(.text+0x0): multiple definition of `sigsuspend' > > sigsuspend.So:sigsuspend.S:2: first defined here > > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigsuspend' changed from 36 to 236 in uthread_sigsuspend.So > > *** Error code 1 > > > > and the fix is to add sigpending.o and sigsuspend.o to the > > definition of HIDDEN_SYSCALLS in "src/lib/libc_r/Makefile". > > > > I'm pretty sure that this is the right fix. My guess as to why it didn't > pop up on i386 is that the old and new implementations were sufficiently > close in size that rounding up to 16bytes made them look identical. > I've just committed this. I'm also pretty sure this is the right fix. I don't know why ld/i386 doesn't complain. It may be a bug, because the difference in size is probably more than 16 bytes. Compare for example sigprocmask, it originally also wasn't added to HIDDEN_SYSCALLS and therefore was also defined twice. I'm very much surprised if both versions end op being the same size... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Oct 14 4:25:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 85CFF14D18 for ; Thu, 14 Oct 1999 04:25:33 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-38.netcologne.de [195.14.250.38]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA16373; Thu, 14 Oct 1999 13:25:27 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id NAA32566; Thu, 14 Oct 1999 13:25:44 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Thu, 14 Oct 1999 13:25:44 +0200 (CEST) Message-Id: <199910141125.NAA32566@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-current@freebsd.org Subject: make buildworld break @ kdump Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It keeps interesting. root@oranje# date; make buildworld; date Thu Oct 14 10:39:45 CEST 1999 (..) ===> usr.bin/kdump cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c In file included from :46: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c In file included from ioctl.c:67: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition In file included from /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs.h:38, from ioctl.c:53: /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs_mount.h:61: `NCP_VOLNAME_LEN' undeclared here (not in a function) /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs_mount.h:61: size of array `mounted_vol' has non-integer type ioctl.c: In function `ioctlname': ioctl.c:1479: sizeof applied to an incomplete type *** Error code 1 (..) Thu Oct 14 12:56:03 CEST 1999 I reported a similiar case yesterday, when compilation stopped at that same position due to some old headers in my /usr/include ip_compat.h ip_fil.h ip_frag.h ip_nat.h ip_proxy.h ip_state.h ipl.h that led to a uncompilable ioctl.c /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c So maybe the break is caused by now obsolete headers again. I don't know yet. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 5: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 7C47714E3A for ; Thu, 14 Oct 1999 05:05:01 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11bjcz-000NQC-00; Thu, 14 Oct 1999 19:05:01 +0700 Date: Thu, 14 Oct 1999 19:05:01 +0700 (ALMST) From: Boris Popov To: Marc van Woerkom Cc: freebsd-current@freebsd.org Subject: Re: make buildworld break @ kdump In-Reply-To: <199910141125.NAA32566@oranje.my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Oct 1999, Marc van Woerkom wrote: > It keeps interesting. > > /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs_mount.h:61: `NCP_VOLNAME_LEN' undeclared here (not in a function) > /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs_mount.h:61: size of array `mounted_vol' has non-integer type That was caused by my commits. Probably they should be done in one transaction and you was 'lucky' enough to catch it :). Now it builds fine. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 5:15:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 625E414C19 for ; Thu, 14 Oct 1999 05:15:26 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-38.netcologne.de [195.14.250.38]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id OAA19536; Thu, 14 Oct 1999 14:15:21 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id OAA33817; Thu, 14 Oct 1999 14:15:41 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Thu, 14 Oct 1999 14:15:41 +0200 (CEST) Message-Id: <199910141215.OAA33817@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: bp@butya.kz Cc: van.woerkom@netcologne.de, freebsd-current@freebsd.org In-reply-to: (message from Boris Popov on Thu, 14 Oct 1999 19:05:01 +0700 (ALMST)) Subject: Re: make buildworld break @ kdump Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That was caused by my commits. Probably they should be done in one > transaction and you was 'lucky' enough to catch it :). Now it builds fine. No problem. I'll try again. :) Thanks, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 6:49:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 9C08F14C16 for ; Thu, 14 Oct 1999 06:49:28 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA24014; Thu, 14 Oct 1999 09:48:19 -0400 (EDT) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id JAA13501; Thu, 14 Oct 1999 09:48:02 -0400 (EDT) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA13496; Thu, 14 Oct 1999 09:48:01 -0400 (EDT) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Thu, 14 Oct 1999 09:48:01 -0400 (EDT) From: Kenneth Wayne Culver To: Marc van Woerkom Cc: cc@137.org, freebsd-current@FreeBSD.ORG Subject: Re: linux emulation broken.. In-Reply-To: <199910140833.KAA01138@oranje.my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is weird, I use linux netscape and word perfect all the time, and the only problems I see are memory leaks I knew were there (in the applications, not FreeBSD) ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 14 Oct 1999, Marc van Woerkom wrote: > > (im)perfect. I was using the linux version of netscape, until > > recently when it began hanging for long periods of time during > > network or disk activity. > > Calling up linux-netscape-4.61 causes my system to freeze for a > couple of seconds, then it reboots. > > This is either related to some recent changes, or my system being > not in a consistent state. > > Regards, > Marc > > > 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 Oct 14 7:19:42 1999 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 B29DD14C32 for ; Thu, 14 Oct 1999 07:19:39 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id JAA57081; Thu, 14 Oct 1999 09:19:33 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 14 Oct 1999 09:19:33 -0500 (CDT) From: David Scheidt To: Alex Le Heux Cc: freebsd-current@freebsd.org Subject: Re: Can't make crashdump after panic In-Reply-To: <19991014094853.A323@funk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Oct 1999, Alex Le Heux wrote: > After configuring the system for making a crashdump, I get "panic: Timeout > table full" halfway through the dump. I had a panic tuesday, due to trying to load a broken module. I got the same panic: Timeout table full message. Interestingly, savecore seems to have recovered the full dump, at least by filesize. I didn't look at it since I knew what had caused the crash. My old kernel, from late august or early september (just pre NewPNP.) was unable to get savecore to save the core, though. > > This is on a stock PII system (weirdest hardware is a ZIP drive :), which > I'm trying to upgrade from a -current from Sep 17. (install new kernel > first, make world after, etc) > Sounds like your modules are out of date? That bit me. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 7:23:56 1999 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 9C85D14FDB for ; Thu, 14 Oct 1999 07:23:53 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id JAA59351; Thu, 14 Oct 1999 09:23:42 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 14 Oct 1999 09:23:42 -0500 (CDT) From: David Scheidt To: Marc van Woerkom Cc: cc@137.org, freebsd-current@FreeBSD.ORG Subject: Re: linux emulation broken.. In-Reply-To: <199910140833.KAA01138@oranje.my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Oct 1999, Marc van Woerkom wrote: > > (im)perfect. I was using the linux version of netscape, until > > recently when it began hanging for long periods of time during > > network or disk activity. > > Calling up linux-netscape-4.61 causes my system to freeze for a > couple of seconds, then it reboots. Is your linux emulation module out of date? I got bit by this the other day. It will causee quite a nice panic. Fixed that (options COMPAT_LINUX). David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 7:55:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 112A415025 for ; Thu, 14 Oct 1999 07:53:24 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id RAA14739 for current@FreeBSD.org; Thu, 14 Oct 1999 17:56:00 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id RAA11599; Thu, 14 Oct 1999 17:46:42 +0400 (MSD) Date: Thu, 14 Oct 1999 17:46:42 +0400 From: Alexey Zelkin To: current@FreeBSD.org Subject: MSGBUF_SIZE Message-ID: <19991014174642.A11517@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I propose to increase default value of MSGBUF_SIZE. Yes, I know that current size is 8k, but today I saw that my machine (PII-300/IDE HDD 4Gb/IDE CD/PnP sound card) started in VERBOSE mode generated about 10k of bootstrap messages. I not sure that I want to specify "options MSGBUF_SIZE=16384" in my kernel to see complete output of dmesg(8). Anyway it's not problem for me, but what about other people ? -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Oct 14 7:58: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 2350E150C9 for ; Thu, 14 Oct 1999 07:55:41 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id RAA14767 for current@FreeBSD.org; Thu, 14 Oct 1999 17:58:48 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id RAA11406; Thu, 14 Oct 1999 17:17:47 +0400 (MSD) Date: Thu, 14 Oct 1999 17:17:47 +0400 From: Alexey Zelkin To: current@FreeBSD.org Subject: boot2 problem Message-ID: <19991014171747.A11382@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, Just found problem with boot loader. Attached "FAQ" will describe problem :) Q: What I want? A: Boot in verbose mode Q: What I do ? A: On boot prompt type "-v" Q: So ? A: Nothing (system is booting in normal mode) Q: What I do then ? A: On boot prompt type "kernel -v" Q: So ? A: All works fine (system is booting in verbose mode) Appendix: FreeBSD spider.scorpion.crimea.ua 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Thu Oct 14 13:41:11 MSD 1999 phantom@spider.scorpion.crimea.ua:/usr/src/HEAD/src/sys/compile/SPIDER i386 -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Oct 14 8:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BBC8014C27 for ; Thu, 14 Oct 1999 08:33:43 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id LAA95111; Thu, 14 Oct 1999 11:24:20 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Thu, 14 Oct 1999 11:23:50 -0400 (EDT) From: Chuck Robey To: Kenneth Wayne Culver Cc: Marc van Woerkom , cc@137.org, freebsd-current@FreeBSD.ORG Subject: Re: linux emulation 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 On Thu, 14 Oct 1999, Kenneth Wayne Culver wrote: > This is weird, I use linux netscape and word perfect all the time, and the > only problems I see are memory leaks I knew were there (in the > applications, not FreeBSD) > I had equal problems a little while back. Make sure you have the linux_base port installed, it has a far more up to date set of libs. > > On Thu, 14 Oct 1999, Marc van Woerkom wrote: > > > > (im)perfect. I was using the linux version of netscape, until > > > recently when it began hanging for long periods of time during > > > network or disk activity. > > > > Calling up linux-netscape-4.61 causes my system to freeze for a > > couple of seconds, then it reboots. > > > > This is either related to some recent changes, or my system being > > not in a consistent state. > > > > Regards, > > Marc > > > > > > 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 > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 9:14:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 88CEB14E41 for ; Thu, 14 Oct 1999 09:14:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA00322; Thu, 14 Oct 1999 09:10:58 -0700 Date: Thu, 14 Oct 1999 09:10:58 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alexey Zelkin Cc: current@FreeBSD.ORG Subject: Re: MSGBUF_SIZE In-Reply-To: <19991014174642.A11517@scorpion.crimea.ua> 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 Uh, no, don't do that. There are still a lot of 386/486 machines out there. And perhaps stronger enforcement (and I'm a culprit at this) of drivers being quite unless bootverbose is set would be better. On Thu, 14 Oct 1999, Alexey Zelkin wrote: > hi, > > I propose to increase default value of MSGBUF_SIZE. Yes, I know > that current size is 8k, but today I saw that my machine > (PII-300/IDE HDD 4Gb/IDE CD/PnP sound card) started in VERBOSE mode > generated about 10k of bootstrap messages. I not sure that I want to specify > "options MSGBUF_SIZE=16384" in my kernel to see complete output > of dmesg(8). Anyway it's not problem for me, but what about other people ? > > -- > /* Alexey Zelkin && phantom@cris.net */ > /* Tavric National University && phantom@crimea.edu */ > /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Thu Oct 14 10: 8:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 13869150C9 for ; Thu, 14 Oct 1999 10:08:04 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA11757 for current@FreeBSD.ORG; Thu, 14 Oct 1999 19:08:02 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 745FB878D; Thu, 14 Oct 1999 18:41:45 +0200 (CEST) Date: Thu, 14 Oct 1999 18:41:45 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991014184145.A70485@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199910110107.SAA22856@kithrup.com> <19991011124621.A3A0114BEB@hub.freebsd.org> <199910111534.JAA14592@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199910111534.JAA14592@mt.sri.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > How do you cause 'vacation' to not send messages to the list? Doesn't > the stock 'vacation' program as shipped in FreeBSD send them to the > list? It is supposed to notice that the mail has a Precedence: header and not send any vacation notice to any mail with one. -=-=- case 'P': /* "Precedence:" */ cont = 0; if (strncasecmp(buf, "Precedence", 10) || (buf[10] != ':' && buf[10] != ' ' && buf[10] != '\t')) break; if (!(p = index(buf, ':'))) break; while (*++p && isspace(*p)); if (!*p) break; if (!strncasecmp(p, "junk", 4) || !strncasecmp(p, "bulk", 4) || !strncasecmp(p, "list", 4)) exit(0); break; -=-=- The standard configuration for Majordomo is to add "Precedence: junk" to all mails. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10: 8:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 982FD1516E for ; Thu, 14 Oct 1999 10:08:41 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA11777 for current@FreeBSD.ORG; Thu, 14 Oct 1999 19:08:35 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 21FEE878D; Thu, 14 Oct 1999 18:46:15 +0200 (CEST) Date: Thu, 14 Oct 1999 18:46:15 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991014184615.B70485@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19991012142522.57A98152AF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991012142522.57A98152AF@hub.freebsd.org> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jonathan M. Bresler: > thanks for the note on bouncefilter. > i'll take a look at it. Someday, when you have 5 minutes free (aha!) have a look at Listar. It is a small, fast and feature-full list manager written in C with automatic bounce handling (among other things). www.listar.org -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10:22:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from news.rdc1.tn.home.com (ha2.rdc1.tn.home.com [24.2.7.67]) by hub.freebsd.org (Postfix) with ESMTP id A1E98150C4 for ; Thu, 14 Oct 1999 10:22:37 -0700 (PDT) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by news.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991014172236.GIBG8996.news.rdc1.tn.home.com@windows> for ; Thu, 14 Oct 1999 10:22:36 -0700 Message-ID: <002c01bf1669$4d296980$29100218@micronetinfo.com> From: "Douglas Kuntz" To: Subject: Ditto Max Date: Thu, 14 Oct 1999 13:26:47 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I dont think my other mail made it through...(since I didnt see it, or any replys) Has anyone gotten an Iomega Ditto Max drive to work on 4.0? I have both types, Floppy/ditto dash card and Parallel port, and would like to use it to back up my drive every week or so. Thanks Douglas Kuntz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10:29: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from news.rdc1.tn.home.com (ha2.rdc1.tn.home.com [24.2.7.67]) by hub.freebsd.org (Postfix) with ESMTP id 4A3391515B for ; Thu, 14 Oct 1999 10:28:57 -0700 (PDT) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by news.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991014172856.GJRA8996.news.rdc1.tn.home.com@windows> for ; Thu, 14 Oct 1999 10:28:56 -0700 Message-ID: <007501bf166a$2fad6360$29100218@micronetinfo.com> From: "Douglas Kuntz" To: Subject: oops Date: Thu, 14 Oct 1999 13:33:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok..disregard my 2nd mail...damn @home takes forever to send out mail *goes to a corner* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10:30:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 640AF156AA for ; Thu, 14 Oct 1999 10:30:17 -0700 (PDT) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id TAA84824; Thu, 14 Oct 1999 19:30:55 +0200 (CEST) (envelope-from tobez) Date: Thu, 14 Oct 1999 19:30:54 +0200 From: Anton Berezin To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991014193054.D74224@plab.ku.dk> References: <19991012142522.57A98152AF@hub.freebsd.org> <19991014184615.B70485@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991014184615.B70485@keltia.freenix.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 14, 1999 at 06:46:15PM +0200, Ollivier Robert wrote: > Someday, when you have 5 minutes free (aha!) have a look at Listar. It > is a small, fast and feature-full list manager written in C with > automatic bounce handling (among other things). Hmm, it sends mails itself. I doubt it can do this more effectively than postfix does. Am I wrong? Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10:34: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id D362C1538E for ; Thu, 14 Oct 1999 10:33:46 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA12951 for current@FreeBSD.org; Thu, 14 Oct 1999 19:33:44 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 56814878D; Thu, 14 Oct 1999 19:27:05 +0200 (CEST) Date: Thu, 14 Oct 1999 19:27:05 +0200 From: Ollivier Robert To: current@FreeBSD.org Subject: Re: boot2 problem Message-ID: <19991014192705.A71278@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.org References: <19991014171747.A11382@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991014171747.A11382@scorpion.crimea.ua> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alexey Zelkin: > Q: What I do then ? > A: On boot prompt type "kernel -v" Try "set boot_verbose" at the boot loader prompt then "boot". -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10:34: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id B2FE0153A4; Thu, 14 Oct 1999 10:34:00 -0700 (PDT) From: "Jonathan M. Bresler" To: roberto@keltia.freenix.fr Cc: current@FreeBSD.ORG In-reply-to: <19991014184615.B70485@keltia.freenix.fr> (message from Ollivier Robert on Thu, 14 Oct 1999 18:46:15 +0200) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991014173400.B2FE0153A4@hub.freebsd.org> Date: Thu, 14 Oct 1999 10:34:00 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG listar.org....i'll take a look. thanks for the pointer. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 10:39:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E3B3915109; Thu, 14 Oct 1999 10:39:24 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA01696; Thu, 14 Oct 1999 19:15:16 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id SAA00746; Thu, 14 Oct 1999 18:45:41 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910141645.SAA00746@yedi.iaf.nl> Subject: Re: World breakage in libc_r? In-Reply-To: from John Polstra at "Oct 13, 1999 2:36:29 pm" To: jdp@polstra.com (John Polstra) Date: Thu, 14 Oct 1999 18:45:41 +0200 (CEST) Cc: current@FreeBSD.ORG, dfr@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (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 As John Polstra wrote ... > I'm building world on an Alpha and have run into this: > > building shared library libc_r.so.4 > sigpending.So: In function `sigpending': > sigpending.S:2: multiple definition of `sigpending' > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigpending' changed from 68 to 36 in sigpending.So > uthread_sigsuspend.So: In function `sigsuspend': > uthread_sigsuspend.c(.text+0x0): multiple definition of `sigsuspend' > sigsuspend.So:sigsuspend.S:2: first defined here > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigsuspend' changed from 36 to 236 in uthread_sigsuspend.So > *** Error code 1 You are not alone... I've already been in contact with Marcel (Moolenaar) and he'll fix it. He really wants to, because he can borrow one of my Alpha's as soon as it can build it's own -current ;-) ;-) Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Oct 14 11: 9:46 1999 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 0EF5714C1E for ; Thu, 14 Oct 1999 11:09:44 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA68820; Thu, 14 Oct 1999 13:04:11 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 14 Oct 1999 13:04:11 -0500 (CDT) From: David Scheidt To: Ollivier Robert Cc: jt traub , current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991014184615.B70485@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Oct 1999, Ollivier Robert wrote: > According to Jonathan M. Bresler: > > thanks for the note on bouncefilter. > > i'll take a look at it. > > Someday, when you have 5 minutes free (aha!) have a look at Listar. It is a > small, fast and feature-full list manager written in C with automatic bounce > handling (among other things). It also builds almost out of the box on FreeBSD. You have to define BSDMOD, build it, install it, and add a listar user. I have a port that is nearly finished, pending acquistion of a round tuit. > > www.listar.org David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 11:12:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 3513414C1E for ; Thu, 14 Oct 1999 11:12:30 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id UAA14982 for current@FreeBSD.ORG; Thu, 14 Oct 1999 20:12:21 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 6B45C878D; Thu, 14 Oct 1999 19:36:34 +0200 (CEST) Date: Thu, 14 Oct 1999 19:36:34 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991014193634.A71455@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19991012142522.57A98152AF@hub.freebsd.org> <19991014184615.B70485@keltia.freenix.fr> <19991014193054.D74224@plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991014193054.D74224@plab.ku.dk> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Anton Berezin: > Hmm, it sends mails itself. I doubt it can do this more effectively than > postfix does. Am I wrong? Yes :-) Postfix, as discussion with Wietse showed recently, is more optimized to mail flowing through the SMTP port (like Listar does) than through the sendmail frontend (because it create a file in incoming/, the file is moved by pickup then given to qmgr). That is, you can achieve a better throughput that way. Another point is that, with a patch recently posted to the postfix mailing list that add VERP capability to Postfix, you can tune Listar to enable VERP mail for your lists... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 11:25:24 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id AB67F14F70; Thu, 14 Oct 1999 11:25:23 -0700 (PDT) From: "Jonathan M. Bresler" To: dscheidt@enteract.com Cc: roberto@keltia.freenix.fr, jtraub@dragoncat.net, current@FreeBSD.ORG In-reply-to: (message from David Scheidt on Thu, 14 Oct 1999 13:04:11 -0500 (CDT)) Subject: Re: People getting automatically unsub'ed from -arch Message-Id: <19991014182523.AB67F14F70@hub.freebsd.org> Date: Thu, 14 Oct 1999 11:25:23 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > finished, pending acquistion of a round tuit. Olliver Robert should be able to get on in France and bring it to the FreeBSDCon. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 11:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 60E1815116 for ; Thu, 14 Oct 1999 11:39:39 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id UAA03085; Thu, 14 Oct 1999 20:39:33 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id UAA10827; Thu, 14 Oct 1999 20:39:32 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991014193054.D74224@plab.ku.dk> References: <19991012142522.57A98152AF@hub.freebsd.org> <19991014184615.B70485@keltia.freenix.fr> <19991014193054.D74224@plab.ku.dk> Date: Thu, 14 Oct 1999 20:38:54 +0200 To: Anton Berezin , Ollivier Robert From: Brad Knowles Subject: Re: People getting automatically unsub'ed from -arch Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:30 PM +0200 1999/10/14, Anton Berezin wrote: > Hmm, it sends mails itself. I doubt it can do this more effectively than > postfix does. Am I wrong? I quote from the README file: >> You probably want to create a listar user/group so that the program >> runs as an unpriveledged user. Chmod the listar executable to this >> user and make sure this user is a trusted user of your sendmail >> program. Also make sure all the list directories and the >> newlist.pl script have the correct permissions and can be read/written >> by the listar user/group. [ ... deletia ... ] >> Create lists using the newlist.pl script. This script will create all the >> initial list files for your list. Further documentation will be >> forthcoming at a later date (any volunteers?) The newlist.pl script >> will output some aliases which should be added to a valid aliases file >> for sendmail. After adding them, run 'newaliases' (or the equivalent >> for your machine). I've just downloaded the package and haven't yet had a chance to actually try it out, but it looks to me like it uses the standard sendmail & SMTP interfaces. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 12:11:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 387F114E08 for ; Thu, 14 Oct 1999 12:11:00 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA20904; Thu, 14 Oct 1999 15:10:17 -0400 (EDT) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA08825; Thu, 14 Oct 1999 15:10:10 -0400 (EDT) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA08821; Thu, 14 Oct 1999 15:10:10 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Thu, 14 Oct 1999 15:10:10 -0400 (EDT) From: Kenneth Wayne Culver To: Wilko Bulte Cc: freebsd-current@freebsd.org Subject: Re: World breakage in libc_r? In-Reply-To: <199910141645.SAA00746@yedi.iaf.nl> 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 Speaking of libc_r, (this is unrelated sort of) I was wondering if anyone was planning on adding the pthread_setcancel and other pthread cancel stuff to -CURRENT. I was trying to use it the other day when I realized it wasn't there... :-) Just a question, I'm not demanding anything. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 14 Oct 1999, Wilko Bulte wrote: > As John Polstra wrote ... > > I'm building world on an Alpha and have run into this: > > > > building shared library libc_r.so.4 > > sigpending.So: In function `sigpending': > > sigpending.S:2: multiple definition of `sigpending' > > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here > > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigpending' changed from 68 to 36 in sigpending.So > > uthread_sigsuspend.So: In function `sigsuspend': > > uthread_sigsuspend.c(.text+0x0): multiple definition of `sigsuspend' > > sigsuspend.So:sigsuspend.S:2: first defined here > > /usr/obj/a/src/tmp/usr/libexec/elf/ld: Warning: size of symbol `sigsuspend' changed from 36 to 236 in uthread_sigsuspend.So > > *** Error code 1 > > You are not alone... I've already been in contact with Marcel (Moolenaar) > and he'll fix it. He really wants to, because he can borrow one of my > Alpha's as soon as it can build it's own -current ;-) ;-) > > Wilko > -- > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Thu Oct 14 12:21:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 764DC14BDE for ; Thu, 14 Oct 1999 12:21:52 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id PAA12060; Thu, 14 Oct 1999 15:20:35 -0400 (EDT) Date: Thu, 14 Oct 1999 15:20:35 -0400 (EDT) From: Daniel Eischen Message-Id: <199910141920.PAA12060@pcnet1.pcnet.com> To: culverk@wam.umd.edu, wilko@yedi.iaf.nl Subject: Re: World breakage in libc_r? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > Speaking of libc_r, (this is unrelated sort of) I was wondering if anyone > was planning on adding the pthread_setcancel and other pthread cancel > stuff to -CURRENT. I was trying to use it the other day when I realized it > wasn't there... :-) Just a question, I'm not demanding anything. Alfred Perlstein has some patches to add OpenBSDs pthread_cancel support to our libc_r. I'll be reviewing the changes soon, hopefully this weekend. As long as JB OKs the change too, you might get your wish. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 12:22:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 29C5D15149 for ; Thu, 14 Oct 1999 12:21:06 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id WAA17773; Thu, 14 Oct 1999 22:22:34 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id SAA15401; Thu, 14 Oct 1999 18:40:02 +0400 (MSD) Date: Thu, 14 Oct 1999 18:40:02 +0400 From: Alexey Zelkin To: "Sean O'Connell" , current@freebsd.org Subject: Re: boot2 problem Message-ID: <19991014184002.A15375@scorpion.crimea.ua> References: <19991014171747.A11382@scorpion.crimea.ua> <19991014110651.T2598@stat.Duke.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991014110651.T2598@stat.Duke.EDU> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, On Thu, Oct 14, 1999 at 11:06:51AM -0400, Sean O'Connell wrote: > > Just found problem with boot loader. Attached "FAQ" will describe problem :) [dd] > Alternatively, you can interrupt the boot process and enter > set boot_verbose > at the disk0> prompt (or whatever it is). Thanks :) I know. PS: Can someone with more or less fresh -current repeat this ? If so, I'll file PR. -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Oct 14 13:41:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id 3A8C31514D for ; Thu, 14 Oct 1999 13:41:17 -0700 (PDT) (envelope-from ron@zappa.demon.nl) Received: (from ron@localhost) by zappa.demon.nl (8.9.3/8.9.3) id WAA13344 for freebsd-current@freebsd.org; Thu, 14 Oct 1999 22:42:46 +0200 (CEST) (envelope-from ron) Date: Thu, 14 Oct 1999 22:42:46 +0200 (CEST) From: Ron Klinkien Message-Id: <199910142042.WAA13344@zappa.demon.nl> To: freebsd-current@freebsd.org Subject: QIC ft0 driver support in 4.0-CURRENT gone? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if I ask a FAQ, But where is ft0 support gone? There are some small traces in /dev/MAKEDEV and LINT but it seems it's not supported anymore in 4.0-CURRENT. I'm I correct? I have a Conner drive connected to the floppy cable. Regards, Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 14: 6:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E8B15151A8 for ; Thu, 14 Oct 1999 14:06:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA17100; Thu, 14 Oct 1999 14:06:41 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA07367; Thu, 14 Oct 1999 14:06:40 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Oct 1999 14:06:40 -0700 (PDT) Message-Id: <199910142106.OAA07367@vashon.polstra.com> To: marcel@scc.nl Subject: Re: World breakage in libc_r? In-Reply-To: <3805AD86.B6D2608E@scc.nl> References: <3805AD86.B6D2608E@scc.nl> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3805AD86.B6D2608E@scc.nl>, Marcel Moolenaar wrote: > Doug Rabson wrote: > > On Wed, 13 Oct 1999, John Polstra wrote: > > > > > and the fix is to add sigpending.o and sigsuspend.o to the > > > definition of HIDDEN_SYSCALLS in "src/lib/libc_r/Makefile". > > > > > > > I'm pretty sure that this is the right fix. My guess as to why it didn't > > pop up on i386 is that the old and new implementations were sufficiently > > close in size that rounding up to 16bytes made them look identical. > > > > I've just committed this. Thanks. > I'm also pretty sure this is the right fix. I don't know why ld/i386 > doesn't complain. It may be a bug, because the difference in size > is probably more than 16 bytes. Compare for example sigprocmask, it > originally also wasn't added to HIDDEN_SYSCALLS and therefore was > also defined twice. I'm very much surprised if both versions end op > being the same size... I know now why it worked on the i386 but not on the Alpha. On the i386 a system call "read", for example, produces a strong (normal global) symbol "_read" and a weak alias "read". Because the symbols were weak, the linker didn't complain about the multiple definitions. But on the Alpha, only a strong symbol "read" is emitted. So multiple definitions caused a diagnostic there. On a related topic, we should fix the Alpha to emit the weak alias like the i386 does. That's for ANSI/ISO C compliance, so that if a user defines his own version of read(), it won't affect the behavior of, say, getc(). We need a lot more of this throughout the C library for both target platforms. And we need to fix the calls inside there to use the "_xxx" symbols rather than the "xxx" versions. Don't ya just love people who say "we" need to do stuff? :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 14:17: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 1B055151A8 for ; Thu, 14 Oct 1999 14:16:56 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id HAA70359; Fri, 15 Oct 1999 07:19:26 +1000 (EST) (envelope-from jb) Date: Fri, 15 Oct 1999 07:19:26 +1000 From: John Birrell To: John Polstra Cc: marcel@scc.nl, current@FreeBSD.ORG Subject: Re: World breakage in libc_r? Message-ID: <19991015071925.A67481@freebsd1.cimlogic.com.au> References: <3805AD86.B6D2608E@scc.nl> <199910142106.OAA07367@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910142106.OAA07367@vashon.polstra.com>; from John Polstra on Thu, Oct 14, 1999 at 02:06:40PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 14, 1999 at 02:06:40PM -0700, John Polstra wrote: > On a related topic, we should fix the Alpha to emit the weak alias > like the i386 does. That's for ANSI/ISO C compliance, so that if a > user defines his own version of read(), it won't affect the behavior > of, say, getc(). We need a lot more of this throughout the C library > for both target platforms. And we need to fix the calls inside there > to use the "_xxx" symbols rather than the "xxx" versions. When I put the weak symbol stuff in, it did work on the alpha. Must have got lost in the version upgrades. > > Don't ya just love people who say "we" need to do stuff? :-) "Don't ya just love tools people who say "we" need to do stuff to tools?" 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 14:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 05C9C151BF for ; Thu, 14 Oct 1999 14:36:17 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA00099; Thu, 14 Oct 1999 17:35:05 -0400 (EDT) Date: Thu, 14 Oct 1999 17:35:05 -0400 (EDT) From: Daniel Eischen Message-Id: <199910142135.RAA00099@pcnet1.pcnet.com> To: jdp@polstra.com, marcel@scc.nl Subject: Re: World breakage in libc_r? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > I know now why it worked on the i386 but not on the Alpha. On the > i386 a system call "read", for example, produces a strong (normal > global) symbol "_read" and a weak alias "read". Because the symbols > were weak, the linker didn't complain about the multiple definitions. > But on the Alpha, only a strong symbol "read" is emitted. So multiple > definitions caused a diagnostic there. > > On a related topic, we should fix the Alpha to emit the weak alias > like the i386 does. That's for ANSI/ISO C compliance, so that if a > user defines his own version of read(), it won't affect the behavior > of, say, getc(). We need a lot more of this throughout the C library > for both target platforms. And we need to fix the calls inside there > to use the "_xxx" symbols rather than the "xxx" versions. > > Don't ya just love people who say "we" need to do stuff? :-) One of the things on my wish list is a libpthread that can be linked with libc. So the way to accomplish this is to have null hooks with weak symbols in libc, and provide the same (non-null) functions in libpthread but with strong symbols? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 14:45:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CC95414BDC for ; Thu, 14 Oct 1999 14:45:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA17233; Thu, 14 Oct 1999 14:45:08 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA07475; Thu, 14 Oct 1999 14:45:07 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910142135.RAA00099@pcnet1.pcnet.com> Date: Thu, 14 Oct 1999 14:45:07 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Daniel Eischen Subject: Re: World breakage in libc_r? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John Polstra wrote: > > One of the things on my wish list is a libpthread that can be linked > with libc. So the way to accomplish this is to have null hooks with > weak symbols in libc, and provide the same (non-null) functions in > libpthread but with strong symbols? Oh, maybe, but be careful. Weak symbols don't solve very many kinds of problems, but they can sure cause a lot of trouble. I don't have time to work through this case in detail right now. But think about whether a call to read() from inside libc will get the correct version in all cases. Consider both static and dynamic linking too -- they don't behave quite the same. There are lots of potential gotchas. Sorry to be so brief. I can help more with this after FreeBSDCon. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 14:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 018B6150F8 for ; Thu, 14 Oct 1999 14:51:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id HAA70535; Fri, 15 Oct 1999 07:53:47 +1000 (EST) (envelope-from jb) Date: Fri, 15 Oct 1999 07:53:47 +1000 From: John Birrell To: Daniel Eischen Cc: jdp@polstra.com, marcel@scc.nl, current@FreeBSD.ORG Subject: Re: World breakage in libc_r? Message-ID: <19991015075346.B67481@freebsd1.cimlogic.com.au> References: <199910142135.RAA00099@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910142135.RAA00099@pcnet1.pcnet.com>; from Daniel Eischen on Thu, Oct 14, 1999 at 05:35:05PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 14, 1999 at 05:35:05PM -0400, Daniel Eischen wrote: > One of the things on my wish list is a libpthread that can be linked > with libc. So the way to accomplish this is to have null hooks with > weak symbols in libc, and provide the same (non-null) functions in > libpthread but with strong symbols? Weak symbols don't work too well _between_ libraries. If libc is linked before libpthread, any unresolved references when libc is searched will use the weak symbols from there, regardless of the fact that a strong symbol exists in libpthread. If libc is linked after libpthread, then you can have libc internal references to things that should been resolved to things in libpthread, but end up using the weak symbols in libc because that is all there is left. 8-( Not a simple problem to solve. The current tools don't help at all. A second library pass to resolve weak symbols would have been better. It's too late for that now, though, since you can change the semantics on the shared loader. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 15:26:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5FD5015109 for ; Thu, 14 Oct 1999 15:26:54 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA06440; Thu, 14 Oct 1999 18:25:41 -0400 (EDT) Date: Thu, 14 Oct 1999 18:25:41 -0400 (EDT) From: Daniel Eischen Message-Id: <199910142225.SAA06440@pcnet1.pcnet.com> To: eischen@vigrid.com, jb@cimlogic.com.au Subject: Re: World breakage in libc_r? Cc: current@FreeBSD.ORG, jdp@polstra.com, marcel@scc.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > Weak symbols don't work too well _between_ libraries. If libc is linked > before libpthread, any unresolved references when libc is searched will > use the weak symbols from there, regardless of the fact that a strong > symbol exists in libpthread. If libc is linked after libpthread, then > you can have libc internal references to things that should been resolved > to things in libpthread, but end up using the weak symbols in libc > because that is all there is left. 8-( > > Not a simple problem to solve. The current tools don't help at all. A > second library pass to resolve weak symbols would have been better. It's > too late for that now, though, since you can change the semantics on the > shared loader. It'd be interesting to know how Solaris does this. I see they don't supply a static libpthread, just the dynamic. It seems they do use a strong symbol in libpthread, and a weak one in libc: vfr [80] $ nm /usr/lib/libc.so.1 | grep pthread_mutex_lock [4394] | 596188| 44|FUNC |WEAK |0 |12 |_pthread_mutex_lock [2980] | 596188| 44|FUNC |WEAK |0 |12 |pthread_mutex_lock vfr [81] $ nm /usr/lib/libpthread.so.1 | grep pthread_mutex_lock [333] | 20704| 8|FUNC |GLOB |0 |8 |_pthread_mutex_lock [107] | 20704| 8|FUNC |WEAK |0 |8 |pthread_mutex_lock Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 15:37:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id F2AF6150BF for ; Thu, 14 Oct 1999 15:37:40 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA26588 for current@FreeBSD.ORG; Fri, 15 Oct 1999 00:37:39 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 44491878D; Thu, 14 Oct 1999 23:47:01 +0200 (CEST) Date: Thu, 14 Oct 1999 23:47:01 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch Message-ID: <19991014234701.A74166@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19991012142522.57A98152AF@hub.freebsd.org> <19991014184615.B70485@keltia.freenix.fr> <19991014193054.D74224@plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brad Knowles: > I've just downloaded the package and haven't yet had a chance to > actually try it out, but it looks to me like it uses the standard > sendmail & SMTP interfaces. It does. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 14 20:53:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from imap.ncsa.es (imap.ncsa.es [194.179.50.6]) by hub.freebsd.org (Postfix) with ESMTP id 7E54514C86 for ; Thu, 14 Oct 1999 20:53:23 -0700 (PDT) (envelope-from jesusr@chuck.jerocu.net) Received: from chuck.jerocu.net (chuck.jerocu.net [194.224.235.59]) by imap.ncsa.es (8.9.3/8.9.1) with ESMTP id FAA96924; Fri, 15 Oct 1999 05:53:11 +0200 (CEST) Received: (from jesusr@localhost) by chuck.jerocu.net (8.9.3/8.9.3) id FAA05991; Fri, 15 Oct 1999 05:53:48 +0200 (CEST) Message-ID: X-Mailer: XFMail 1.3 [p0] 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, 15 Oct 1999 05:53:48 +0200 (CEST) Reply-To: jesusr@ncsa.es Organization: Nexus Comunicaciones, S.A. From: Jesus Rodriguez To: Nick Hibma Subject: Re: staroffice Cc: FreeBSD Current , Ollivier Robert Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Oct-99 Nick Hibma wrote: >> > o unzip setup.zip to someplace comfortable >> >> Don't both with that. >> >> use "export LD_LIBRARY_PATH=/tmp/sv001.tmp:." before running the setup >> binary. Hello... I've installed Staroffice 5.1 (spanish version) on: FreeBSD chuck.jerocu.net 4.0-CURRENT FreeBSD 4.0-CURRENT #6: Fri Oct 15 04:36:15 CEST 1999 root@chuck.jerocu.net:/usr/src/sys/compile/CHUCK i386 following the steps described in http://www.serv.net/~mcglk/staroffice-install.html Installation process has worked ok, but when i try to run /usr/local/Office51/bin/soffice or /usr/local/bin/soffice always get a screen that says: StarOffice 5.1 Installation Program Staroffice is already installed on: /usr/local/Office51 And i can select between Modify, Uninstall and Repair... every time i run soffice i get the Setup program. I can run the printer setup program without problems. I don't really know where is the problem :( Thanks in advance. JesusR. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 0:31:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id B35F414C83 for ; Fri, 15 Oct 1999 00:31:28 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-as58-rs1-173.netcologne.de [195.14.226.173]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id JAA25814; Fri, 15 Oct 1999 09:31:01 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id JAA01175; Fri, 15 Oct 1999 09:31:18 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Fri, 15 Oct 1999 09:31:18 +0200 (CEST) Message-Id: <199910150731.JAA01175@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: culverk@wam.umd.edu Cc: van.woerkom@netcologne.de, cc@137.org, freebsd-current@FreeBSD.ORG In-reply-to: (message from Kenneth Wayne Culver on Thu, 14 Oct 1999 09:48:01 -0400 (EDT)) Subject: Re: linux emulation broken.. Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is weird, I use linux netscape and word perfect all the time, and the > only problems I see are memory leaks I knew were there (in the > applications, not FreeBSD) Indeed. The Linux version was more stable than the FreeBSD version (that one can't digest the Slashdot site for some strange reason). But since Monday it tears my box down. I won't blame the emulation however until I have recompiled the system successfully and recompiled XFree86 and this behaviour continues to happen. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 1: 6:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id B8A7D14CE5 for ; Fri, 15 Oct 1999 01:06:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00979; Fri, 15 Oct 1999 00:57:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910150757.AAA00979@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alexey Zelkin Cc: current@FreeBSD.org Subject: Re: boot2 problem In-reply-to: Your message of "Thu, 14 Oct 1999 17:17:47 +0400." <19991014171747.A11382@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 00:57:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi, > > Just found problem with boot loader. Attached "FAQ" will describe problem :) This is not a problem. > Q: What I want? > A: Boot in verbose mode > > Q: What I do ? > A: On boot prompt type "-v" > > Q: So ? > A: Nothing (system is booting in normal mode) That's correct. '-v' at the boot: prompt does nothing. > Q: What I do then ? > A: On boot prompt type "kernel -v" > > Q: So ? > A: All works fine (system is booting in verbose mode) '-v' is an argument to the kernel. Specify it as such. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 1: 9:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id E708C14F9F for ; Fri, 15 Oct 1999 01:09:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA01009; Fri, 15 Oct 1999 01:00:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910150800.BAA01009@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Douglas Kuntz" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Ditto Max In-reply-to: Your message of "Thu, 14 Oct 1999 13:26:47 EDT." <002c01bf1669$4d296980$29100218@micronetinfo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 01:00:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since I dont think my other mail made it through...(since I didnt see it, or > any replys) > > Has anyone gotten an Iomega Ditto Max drive to work on 4.0? I have both > types, Floppy/ditto dash card and Parallel port, and would like to use it to > back up my drive every week or so. It's not supported, and it's a disgusting device. Stuff it in the bin and buy something better. You could have found this information by searching the list archives, BTW. You should do that first as a matter of course to avoid messages like this that may seem to be flames. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 1:12:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id A30EC14F9F for ; Fri, 15 Oct 1999 01:12:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA01041; Fri, 15 Oct 1999 01:04:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910150804.BAA01041@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ron Klinkien Cc: freebsd-current@freebsd.org Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? In-reply-to: Your message of "Thu, 14 Oct 1999 22:42:46 +0200." <199910142042.WAA13344@zappa.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 01:04:06 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sorry if I ask a FAQ, Don't be sorry, don't do it. Search the mailing list archives. > But where is ft0 support gone? Into the bitbucket. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 2:35:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 8568914E63; Fri, 15 Oct 1999 02:35:19 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem15.masternet.it [194.184.65.25]) by kirk.giovannelli.it (8.9.3/8.9.3) with ESMTP id LAA01714; Fri, 15 Oct 1999 11:35:10 +0200 (CEST) (envelope-from gmarco@giovannelli.it) Message-Id: <4.2.0.58.19991015112205.009ce710@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 15 Oct 1999 11:25:14 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: XFree build fine but don't install Cc: ports@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 I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box. It compile well, but when it's the time of the install I receive this error : rm -f FSConnServ.o cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. -I../../ex ports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_N ULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKE TS FSConnServ.c In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:212: syntax error before `siginfo_t' In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc/lib/FS. *** Error code 1 I am sorry if this is a well known problem, but I couldn't read the mailing lists in the past days ... Thanks... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 2:56:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 5A8C014BE9 for ; Fri, 15 Oct 1999 02:52:21 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id MAA05806; Fri, 15 Oct 1999 12:52:17 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id LAA12243; Fri, 15 Oct 1999 11:45:56 +0400 (MSD) Date: Fri, 15 Oct 1999 11:45:56 +0400 From: Alexey Zelkin To: Mike Smith Cc: current@FreeBSD.org Subject: Re: boot2 problem Message-ID: <19991015114556.A7776@scorpion.crimea.ua> References: <19991014171747.A11382@scorpion.crimea.ua> <199910150757.AAA00979@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <199910150757.AAA00979@dingo.cdrom.com> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote: > That's correct. '-v' at the boot: prompt does nothing. But '/kernel' is default kernel name, so "-v" will be option to default kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ). > > Q: What I do then ? > > A: On boot prompt type "kernel -v" > > > > Q: So ? > > A: All works fine (system is booting in verbose mode) > > '-v' is an argument to the kernel. Specify it as such. 8) If we have default kernel name then why I can't pass parameters there and have to excplicitly type kernel name ? -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Oct 15 3: 9:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id C60BB14D7F for ; Fri, 15 Oct 1999 03:09:45 -0700 (PDT) (envelope-from unfurl@magnesium.net) Received: (qmail 94508 invoked by uid 1001); 15 Oct 1999 10:09:44 -0000 Date: 15 Oct 1999 03:09:44 -0700 Date: Fri, 15 Oct 1999 03:09:44 -0700 From: Bill Swingle To: Alexey Zelkin Cc: current@FreeBSD.org Subject: Re: boot2 problem Message-ID: <19991015030944.A93974@dub.net> References: <19991014171747.A11382@scorpion.crimea.ua> <199910150757.AAA00979@dingo.cdrom.com> <19991015114556.A7776@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991015114556.A7776@scorpion.crimea.ua> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 15, 1999 at 11:45:56AM +0400, Alexey Zelkin wrote: > hi, > > On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote: > > > That's correct. '-v' at the boot: prompt does nothing. > > But '/kernel' is default kernel name, so "-v" will be option to default > kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ). The boot loader was completly rewritten for the 3.x series. > > > Q: What I do then ? > > > A: On boot prompt type "kernel -v" > > > > > > Q: So ? > > > A: All works fine (system is booting in verbose mode) > > > > '-v' is an argument to the kernel. Specify it as such. 8) > > If we have default kernel name then why I can't pass parameters there > and have to excplicitly type kernel name ? You don't have to explicitly specify the kernel name. If the default kernel has already been loaded you just have to tell it what to do. 'boot -v' It's pretty consistant with other OS's boot prompt. -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 3:19:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from ints.ru (ints.ru [194.67.173.1]) by hub.freebsd.org (Postfix) with ESMTP id B69ED14FE1 for ; Fri, 15 Oct 1999 03:19:20 -0700 (PDT) (envelope-from ilmar@ws-ilmar.ints.ru) Received: (from uucp@localhost) by ints.ru (8.9.2/8.9.2) id OAA02150 for ; Fri, 15 Oct 1999 14:19:17 +0400 (MSD) Received: from ws-ilmar.ints.ru(194.67.173.16) via SMTP by ints.ru, id smtpdGI2148; Fri Oct 15 14:19:17 1999 Received: (from ilmar@localhost) by ws-ilmar.ints.ru (8.9.3/8.9.3) id OAA23486 for freebsd-current@freebsd.org; Fri, 15 Oct 1999 14:19:16 +0400 (MSD) Date: Fri, 15 Oct 1999 14:19:16 +0400 (MSD) From: "Ilmar S. Habibulin" Message-Id: <199910151019.OAA23486@ws-ilmar.ints.ru> To: freebsd-current@freebsd.org Subject: jumping from 3.1 to 4.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade it to current. I read mail-archives and knew, that i had to compile kernel first. So i made new config and configured and build kernel. While booting loader prints the next error message and boot fails: /kernel text=0x202b9d elf_loadexec:archsw.readin failed can't load kernel What hould i do to upgrade to current? PS. answer to email please. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 5:54:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 8262214D71; Fri, 15 Oct 1999 05:54:04 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id OAA17164; Fri, 15 Oct 1999 14:54:03 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910151254.OAA17164@gratis.grondar.za> To: marcel@freebsd.org Cc: current@freebsd.org Subject: still broken? Date: Fri, 15 Oct 1999 14:54:01 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am getting this breakage when I try to compile XFree86 on a really current system: cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKETS FSConnServ.c In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:212: syntax error before `siginfo_t' In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type *** Error code 1 FYI. M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 6: 2:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 11B3A14D71 for ; Fri, 15 Oct 1999 06:02:30 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id PAA17280; Fri, 15 Oct 1999 15:02:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910151302.PAA17280@gratis.grondar.za> To: "Ilmar S. Habibulin" Cc: freebsd-current@FreeBSD.ORG Subject: Re: jumping from 3.1 to 4.0 Date: Fri, 15 Oct 1999 15:02:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What hould i do to upgrade to current? Rebuild and reinstall all your modules. Keep the ols ones "just in case". 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 Fri Oct 15 6:17:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 34B4D14CA3; Fri, 15 Oct 1999 06:17:37 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem02.masternet.it [194.184.65.12]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id PAA11598; Fri, 15 Oct 1999 15:16:59 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19991015145355.00a25100@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 15 Oct 1999 15:06:56 +0200 To: Mark Murray , marcel@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: still broken? Cc: current@FreeBSD.ORG In-Reply-To: <199910151254.OAA17164@gratis.grondar.za> 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 At 15/10/99, Mark Murray wrote: >Hi > >I am getting this breakage when I try to compile XFree86 on a really >current system: > >cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. >-I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 >-DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN >-DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKETS FSConnServ.c >In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: >/usr/include/sys/signal.h:212: syntax error before `siginfo_t' >In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: >/usr/include/sys/signal.h:285: field `sigev_value' has incomplete type >*** Error code 1 Hi , I have the same problems right now... and it not a kind think if it happens in this way : # cd /usr/ports/x11/XFree # make compilation is ok # pkg_delete -f XFree-3.3.1 # make install and the make install hangs :-) Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 6:20: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 94AAC1507B for ; Fri, 15 Oct 1999 06:19:46 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11c7Gq-000HK8-00 for current@freebsd.org; Fri, 15 Oct 1999 15:19:44 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Timeframe on XFree86 signal fix Date: Fri, 15 Oct 1999 15:19:43 +0200 Message-ID: <66595.939993583@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, A sequence of silly mistakes and circumstances have conspired against me to make it impossible for me to run XFree86. I understand that the XFree86 build is broken in the face of recent signal-related changes. I want to know how long I can expect to wait for XFree86 to build on CURRENT again. I'm not pushing, I just want to know whether I'm in for a wait of less than a week (in which case I'll do without XFree86) or whether I can expect to wait longer (in which case I'll bite the bullet and undo my silly mistakes). Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 6:33:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id CA8341507B for ; Fri, 15 Oct 1999 06:33:08 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id JAA33432; Fri, 15 Oct 1999 09:32:57 -0400 (EDT) Date: Fri, 15 Oct 1999 09:32:57 -0400 (EDT) From: jack To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? In-Reply-To: <199910150804.BAA01041@dingo.cdrom.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 Today Mike Smith wrote: > > > > Sorry if I ask a FAQ, > > Don't be sorry, don't do it. Search the mailing list archives. It might help if HARDWARE.TXT (both -current and -stable) didn't list floppy tapes. It refers to the driver as "stale" rather than gone. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 6:53:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 46CE814CA3 for ; Fri, 15 Oct 1999 06:53:47 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id PAA28641 for current@FreeBSD.org; Fri, 15 Oct 1999 15:51:06 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Fri, 15 Oct 1999 15:50:52 +0200 From: Marcel Moolenaar Message-ID: <3807313C.4B9D40B6@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <66595.939993583@axl.noc.iafrica.com> Subject: Re: Timeframe on XFree86 signal fix Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > I want to know how long I can expect to wait for XFree86 to build on > CURRENT again. I'm not pushing, I just want to know whether I'm in for a > wait of less than a week (in which case I'll do without XFree86) or > whether I can expect to wait longer (in which case I'll bite the bullet > and undo my silly mistakes). Building X... Please hold on :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Oct 15 6:56:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-us1.philips.com (gw-us1.philips.com [205.167.14.34]) by hub.freebsd.org (Postfix) with ESMTP id 7581614CA3 for ; Fri, 15 Oct 1999 06:56:28 -0700 (PDT) (envelope-from walter.oostendorp@philips.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-us1.philips.com with ESMTP id JAA00467; Fri, 15 Oct 1999 09:56:25 -0400 (EDT) (envelope-from walter.oostendorp@philips.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-us1.philips.com via mwrap (4.0a) id xma000463; Fri, 15 Oct 99 09:56:26 -0400 Received: from philce2.ehv.ce.philips.com (philce2.ehv-s.nl.philips.com [130.144.120.102]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id PAA23332; Fri, 15 Oct 1999 15:50:04 +0200 (MET DST) Received: from presley.asa.ehv.ce.philips.com (presley.ce.philips.nl [130.144.129.12]) by philce2.ehv.ce.philips.com (8.6.10/8.6.10-1.2.2a-980718) with ESMTP id PAA21301; Fri, 15 Oct 1999 15:50:49 +0200 Received: from philips.com (tvlcpc214 [130.144.130.214]) by presley.asa.ehv.ce.philips.com (8.8.5/8.6.10-1.2.2a-990417) with ESMTP id PAA02085; Fri, 15 Oct 1999 15:50:02 +0200 (MET DST) Message-ID: <380730F5.15D0C4FF@philips.com> Date: Fri, 15 Oct 1999 15:49:41 +0200 From: Walter Oostendorp Reply-To: oostendw@worldonline.nl X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Jesus Rodriguez Cc: FreeBSD Current Subject: Re: staroffice Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 15 Oct 1999 Jesus Rodriguez wrote: >>Installation process has worked ok, but when i try to run >>/usr/local/Office51/bin/soffice or /usr/local/bin/soffice always get a screen >>that says: >> >>Staroffice is already installed on: >>/usr/local/Office51 >> >>And i can select between Modify, Uninstall and Repair... every time i run >>soffice i get the Setup program. I can run the printer setup program without >>problems. >> >>I don't really know where is the problem :( Hello, Did you execute the 'sed' on the library libosl517li.so and did you check the change? In my case (similar problem) it turned out I had to redo this step. So I took the hex editor and changed the path manually. Regards, Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 8:15:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id C5AD515255 for ; Fri, 15 Oct 1999 08:08:13 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11c8yU-000NYf-00; Fri, 15 Oct 1999 15:08:54 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id RAA52102; Fri, 15 Oct 1999 17:07:39 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <38074339.CCAF4B5F@scc.nl> Date: Fri, 15 Oct 1999 17:07:37 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: current@freebsd.org, Sheldon Hearn , gmarco@giovannelli.it Subject: Re: still broken? References: <199910151254.OAA17164@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > Hi > > I am getting this breakage when I try to compile XFree86 on a really > current system: > > cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKETS FSConnServ.c > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:212: syntax error before `siginfo_t' > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type > *** Error code 1 Apply the following patch to /usr/include/sys/signal.h. I want to make sure it doesn't break a kernel or world or adds namespace pollution or whatever before I commit this. In case of problems, yell! --- /sys/sys/signal.h Fri Oct 15 16:58:52 1999 +++ /usr/include/sys/signal.h Fri Oct 15 16:55:55 1999 @@ -131,6 +131,15 @@ void *sigval_ptr; }; +struct sigevent { + int sigev_notify; /* Notification type */ + int sigev_signo; /* Signal number */ + union sigval sigev_value; /* Signal value */ +}; + +#define SIGEV_NONE 0 /* No async notification */ +#define SIGEV_SIGNAL 1 /* Generate a queued signal */ + typedef struct __siginfo { int si_signo; /* signal number */ int si_errno; /* errno association */ @@ -209,7 +218,7 @@ /* Additional FreeBSD values. */ #define SI_UNDEFINED 0 -typedef void __siginfohandler_t __P((int, siginfo_t *, void *)); +typedef void __siginfohandler_t __P((int, struct __siginfo *, void *)); typedef __sighandler_t *sig_t; /* type of pointer to a signal function */ @@ -277,17 +286,6 @@ #define SIG_BLOCK 1 /* block specified signal set */ #define SIG_UNBLOCK 2 /* unblock specified signal set */ #define SIG_SETMASK 3 /* set specified signal set */ - -#ifndef _POSIX_SOURCE -struct sigevent { - int sigev_notify; /* Notification type */ - int sigev_signo; /* Signal number */ - union sigval sigev_value; /* Signal value */ -}; - -#define SIGEV_NONE 0 /* No async notification */ -#define SIGEV_SIGNAL 1 /* Generate a queued signal */ -#endif #endif /* !_ANSI_SOURCE */ -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Oct 15 8:20:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 916A2152E0 for ; Fri, 15 Oct 1999 08:15:07 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11c93r-00025Z-00; Fri, 15 Oct 1999 17:14:27 +0200 From: Sheldon Hearn To: Marcel Moolenaar Cc: Mark Murray , current@freebsd.org, gmarco@giovannelli.it Subject: Re: still broken? In-reply-to: Your message of "Fri, 15 Oct 1999 17:07:37 +0200." <38074339.CCAF4B5F@scc.nl> Date: Fri, 15 Oct 1999 17:14:26 +0200 Message-ID: <8032.940000466@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yech, malformed patch. This one applies. :-) Thanks, Marcel. Ciao, Sheldon. Index: signal.h =================================================================== RCS file: /home/ncvs/src/sys/sys/signal.h,v retrieving revision 1.21 diff -u -d -r1.21 signal.h --- signal.h 1999/10/12 13:58:15 1.21 +++ signal.h 1999/10/15 15:13:39 @@ -131,6 +131,15 @@ void *sigval_ptr; }; +struct sigevent { + int sigev_notify; /* Notification type */ + int sigev_signo; /* Signal number */ + union sigval sigev_value; /* Signal value */ +}; + +#define SIGEV_NONE 0 /* No async notification */ +#define SIGEV_SIGNAL 1 /* Generate a queued signal */ + typedef struct __siginfo { int si_signo; /* signal number */ int si_errno; /* errno association */ @@ -209,7 +218,7 @@ /* Additional FreeBSD values. */ #define SI_UNDEFINED 0 -typedef void __siginfohandler_t __P((int, siginfo_t *, void *)); +typedef void __siginfohandler_t __P((int, struct __siginfo *, void *)); typedef __sighandler_t *sig_t; /* type of pointer to a signal function */ @@ -277,17 +286,6 @@ #define SIG_BLOCK 1 /* block specified signal set */ #define SIG_UNBLOCK 2 /* unblock specified signal set */ #define SIG_SETMASK 3 /* set specified signal set */ - -#ifndef _POSIX_SOURCE -struct sigevent { - int sigev_notify; /* Notification type */ - int sigev_signo; /* Signal number */ - union sigval sigev_value; /* Signal value */ -}; - -#define SIGEV_NONE 0 /* No async notification */ -#define SIGEV_SIGNAL 1 /* Generate a queued signal */ -#endif #endif /* !_ANSI_SOURCE */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 8:33:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from kg.ops.uunet.co.za (kg.ops.uunet.co.za [196.31.1.31]) by hub.freebsd.org (Postfix) with ESMTP id BFE531528D for ; Fri, 15 Oct 1999 08:30:22 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) Received: from chain.freebsd.os.org.za (IDENT:root@chain.freebsd.os.org.za [196.7.74.174]) by kg.ops.uunet.co.za (8.9.3/8.9.3) with ESMTP id RAA81889 for ; Fri, 15 Oct 1999 17:29:51 +0200 (SAST) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.3/8.9.3) with ESMTP id RAA00572; Fri, 15 Oct 1999 17:27:59 +0200 (SAST) (envelope-from khetan@chain.freebsd.os.org.za) Date: Fri, 15 Oct 1999 17:27:59 +0200 (SAST) From: Khetan Gajjar Reply-To: Khetan Gajjar To: David Scheidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Can't make crashdump after panic In-Reply-To: Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around Yesterday, "David Scheidt" wrote : DS> I had a panic tuesday, due to trying to load a broken module. I got the DS> same panic: Timeout table full message. Interestingly, savecore seems to I've been getting these really odd panics as well (which I reported but no-one seemed interested), with that error. In the one case where I provoked it (by loading a kld that was out of sync with the kernel), I also got that error. I'm using the "experimental" ATA code though; are you using IDE disks with the ATA or old WD driver, or are you using SCSI disks ? --- Khetan Gajjar (!kg1779) * khetan@os.org.za http://khetan.os.org.za/ * Talk/Finger khetan@khetan.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ /dev/random output : I am under the influence of sugar, caffeine, and lack of sleep, and should not be held responsible for my behavior. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 8:36: 8 1999 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 9E63515562 for ; Fri, 15 Oct 1999 08:36:02 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id KAA17183; Fri, 15 Oct 1999 10:35:36 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 15 Oct 1999 10:35:36 -0500 (CDT) From: David Scheidt To: Khetan Gajjar Cc: freebsd-current@FreeBSD.ORG Subject: Re: Can't make crashdump after panic 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 Fri, 15 Oct 1999, Khetan Gajjar wrote: > I've been getting these really odd panics as well (which I reported > but no-one seemed interested), with that error. I had only the panics caused by loading an out of date KLD. > I'm using the "experimental" ATA code though; are you using IDE > disks with the ATA or old WD driver, or are you using SCSI disks ? I have both IDE and SCSI disks, I am dumping to an ide disk controlled by the ATA driver. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 8:38:41 1999 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 6428814CDE for ; Fri, 15 Oct 1999 08:38:40 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA39162; Fri, 15 Oct 1999 08:38:35 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA60210; Fri, 15 Oct 1999 08:38:35 -0700 (PDT) (envelope-from obrien) Date: Fri, 15 Oct 1999 08:38:35 -0700 From: "David O'Brien" To: John Polstra Cc: current@freebsd.org Subject: Re: World breakage in libc_r? Message-ID: <19991015083834.A60177@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <3805AD86.B6D2608E@scc.nl> <199910142106.OAA07367@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199910142106.OAA07367@vashon.polstra.com> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On a related topic, we should fix the Alpha to emit the weak alias > like the i386 does. We should do what ever is reasonably possible to keep these two archs operating the same. IMHO, people will expect their FreeBSD platform knowledge to hold on the Alpha. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 8:48:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrew.cmu.edu (ANDREW.CMU.EDU [128.2.10.101]) by hub.freebsd.org (Postfix) with ESMTP id 458091542D; Fri, 15 Oct 1999 08:48:06 -0700 (PDT) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by andrew.cmu.edu (8.9.3/8.9.3) id LAA23705; Fri, 15 Oct 1999 11:48:00 -0400 (EDT) Received: via switchmail; Fri, 15 Oct 1999 11:48:00 -0400 (EDT) Received: from unix14.andrew.cmu.edu via qmail ID ; Fri, 15 Oct 1999 11:47:09 -0400 (EDT) Received: from unix14.andrew.cmu.edu via qmail ID ; Fri, 15 Oct 1999 11:47:09 -0400 (EDT) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix14.andrew.cmu.edu.sun4m.54 via MS.5.6.unix14.andrew.cmu.edu.sun4_51; Fri, 15 Oct 1999 11:47:09 -0400 (EDT) Message-ID: Date: Fri, 15 Oct 1999 11:47:09 -0400 (EDT) From: Thomas Valentino Crimi To: current@freebsd.org, Gianmarco Giovannelli Subject: Re: XFree build fine but don't install Cc: ports@freebsd.org In-Reply-To: <4.2.0.58.19991015112205.009ce710@194.184.65.4> References: <4.2.0.58.19991015112205.009ce710@194.184.65.4> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I managed to fix this problem temporarily for myself, but was hoping the tree would fix itself soon enough. At the top of FSConServ.c add the line #define _P1003_1B_VISIBLE I believe (I deleeted the X source tree), and it'll build fine. Excerpts from FreeBSD-Current: 15-Oct-99 XFree build fine but don't .. by G. Giovannelli@giovannel > I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box. > It compile well, but when it's the time of the install I receive this error : > > rm -f FSConnServ.o > cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. > -I../../ex > ports/include -DCSRG_BASED -DFUNCPROTO=15 > -DNARROWPROTO -DMALLOC_0_RETURNS_N > ULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT > -DBSD44SOCKE > TS FSConnServ.c > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:212: syntax error before `siginfo_t' > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type > *** Error code 1 > Stop in /usr/ports/x11/XFree86/work/xc/lib/FS. > *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 8:51:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id 3F8F41532F for ; Fri, 15 Oct 1999 08:51:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA03279; Fri, 15 Oct 1999 08:42:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910151542.IAA03279@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alexey Zelkin Cc: Mike Smith , current@FreeBSD.org Subject: Re: boot2 problem In-reply-to: Your message of "Fri, 15 Oct 1999 11:45:56 +0400." <19991015114556.A7776@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 08:42:24 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi, > > On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote: > > > That's correct. '-v' at the boot: prompt does nothing. > > But '/kernel' is default kernel name, so "-v" will be option to default > kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ). However, FreeBSD 3.x and 4.x do not. /boot/loader is the default object loaded by boot2. > > > Q: What I do then ? > > > A: On boot prompt type "kernel -v" > > > > > > Q: So ? > > > A: All works fine (system is booting in verbose mode) > > > > '-v' is an argument to the kernel. Specify it as such. 8) > If we have default kernel name then why I can't pass parameters there > and have to excplicitly type kernel name ? You can. Don't interrupt boot2, wait for the loader, and use 'boot -v'. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 10:25:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3424F14F50 for ; Fri, 15 Oct 1999 10:25:36 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA67504; Fri, 15 Oct 1999 10:20:54 -0700 (PDT) Date: Fri, 15 Oct 1999 10:20:54 -0700 (PDT) From: Julian Elischer To: jack Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? 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 the driver could come back if someone who HAD such a device were to adopt it.. On Fri, 15 Oct 1999, jack wrote: > Today Mike Smith wrote: > > > > > > > Sorry if I ask a FAQ, > > > > Don't be sorry, don't do it. Search the mailing list archives. > > It might help if HARDWARE.TXT (both -current and -stable) didn't > list floppy tapes. It refers to the driver as "stale" rather > than gone. > > -------------------------------------------------------------------------- > Jack O'Neill Systems Administrator / Systems Analyst > jack@germanium.xtalwind.net Crystal Wind Communications, Inc. > Finger jack@germanium.xtalwind.net for my PGP key. > PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD > enriched, vcard, HTML messages > /dev/null > -------------------------------------------------------------------------- > > > > > 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 Oct 15 10:42:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3424514C20; Fri, 15 Oct 1999 10:42:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA34836; Fri, 15 Oct 1999 11:42:42 -0600 (MDT) (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 LAA64644; Fri, 15 Oct 1999 11:44:03 -0600 (MDT) Message-Id: <199910151744.LAA64644@harmony.village.org> To: current@freebsd.org, mobile@freebsd.org Subject: HEADS UP: pccard kernel config file changes Date: Fri, 15 Oct 1999 11:44:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've changed the attachment topography for pccard/pcic devices. Now pcic attaches to the isa bus to act as a bridge to the pccard device. For historical reasons, I've left the pccard device name as "card" but this may change to pccard in the future, but there are too many legacy drivers to do that right now. The upshot of all of this is that you need to change your kernel config to controller pcic0 at isa? controller pcic1 at isa? controller card0 in order for thing to work. I've tested this on my laptop, but I only have one pccard slot. I'm interested to hear from others that have more than one slot. I've also tested only on systems that have one pcic, so I'd be interested to hear from those that have more than one pcic in their system. Finally, no pc98 testing has been done. I'm trying to get things to the point where I can attach my slightly rewritten sio code to attach by the end of FreeBSD CON. The next rats nest that I have to sort out is interrupts and bus resources in general given the recent hoisting of resource allocation to the the bus interface. While I'm at it, I'll be trying to untangle the morass of interconnectedness between pcic and pccard. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 10:59:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 87768151A1 for ; Fri, 15 Oct 1999 10:59:45 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id KAA24276; Fri, 15 Oct 1999 10:59:13 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199910151759.KAA24276@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: Timeframe on XFree86 signal fix In-reply-to: Your message of "Fri, 15 Oct 1999 15:19:43 +0200." <66595.939993583@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 10:59:13 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi folks, > > A sequence of silly mistakes and circumstances have conspired against me > to make it impossible for me to run XFree86. I understand that the > XFree86 build is broken in the face of recent signal-related changes. > > I want to know how long I can expect to wait for XFree86 to build on > CURRENT again. I'm not pushing, I just want to know whether I'm in for a > wait of less than a week (in which case I'll do without XFree86) or > whether I can expect to wait longer (in which case I'll bite the bullet > and undo my silly mistakes). > I too was pressed for time and what I did was to dig up the source for a program which uses signals and cut paste the include files to FSConServ.c . I played a little with gcc -E which displays the processing of the include files and took a brief look at signa.h and saw the check for _P1003_1B_VISIBLE... This is all academic since the proper fix was posted to the list. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 11:15: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 7FB0B15325 for ; Fri, 15 Oct 1999 11:14:50 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (local-27.local.net [192.168.1.27]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id LAA09727 for ; Fri, 15 Oct 1999 11:14:42 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <38076F71.C87D36E8@MexComUSA.NET> Date: Fri, 15 Oct 1999 11:16:17 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: kernel compile problem at ed0 References: <199910151749.KAA51327@local-27.local.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have a problem compiling a kernel on my laptop with the ed0 driver that I use for my D-link 660 pcmcia card. Running current, cvsup this morning. Make world finished with no problems but my attempt at kernel compilation yielded: > if_ed_isa.o: In function `ed_isa_attach': > if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' > if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' > if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' > if_ed_isa.o(.text+0x127): undefined reference to `edintr' > if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' > if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' > *** Error code 1 > > Stop in /usr/src/sys/compile/LAPTOP. From my cvsup of this morning Edit src/sys/dev/ed/if_ed.c Add delta 1.164 99.10.15.03.12.46 mdodd Edit src/sys/dev/ed/if_ed_isa.c Add delta 1.2 99.10.15.03.12.47 mdodd Edit src/sys/dev/ed/if_ed_pci.c Add delta 1.22 99.10.15.03.12.47 mdodd Edit src/sys/dev/ed/if_edvar.h Add delta 1.3 99.10.15.03.12.47 mdodd Maybe I just need to wait for the rest of the changes. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 11:26:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 245531515C for ; Fri, 15 Oct 1999 11:26:36 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA08731; Fri, 15 Oct 1999 20:14:56 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA63994; Fri, 15 Oct 1999 20:09:57 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910151809.UAA63994@yedi.iaf.nl> Subject: Re: World breakage in libc_r? In-Reply-To: <199910142225.SAA06440@pcnet1.pcnet.com> from Daniel Eischen at "Oct 14, 1999 6:25:41 pm" To: eischen@vigrid.com (Daniel Eischen) Date: Fri, 15 Oct 1999 20:09:57 +0200 (CEST) Cc: eischen@vigrid.com, jb@cimlogic.com.au, current@FreeBSD.ORG, jdp@polstra.com, marcel@scc.nl X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (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 As Daniel Eischen wrote ... Sheer curiosity and most likely a somewhat dim question: what the h* is a weak versus a strong symbol? Thanks, Wilko > John Birrell wrote: > > Weak symbols don't work too well _between_ libraries. If libc is linked > > before libpthread, any unresolved references when libc is searched will > > use the weak symbols from there, regardless of the fact that a strong > > symbol exists in libpthread. If libc is linked after libpthread, then > > you can have libc internal references to things that should been resolved > > to things in libpthread, but end up using the weak symbols in libc > > because that is all there is left. 8-( > > > > Not a simple problem to solve. The current tools don't help at all. A > > second library pass to resolve weak symbols would have been better. It's > > too late for that now, though, since you can change the semantics on the > > shared loader. > > It'd be interesting to know how Solaris does this. I see they don't > supply a static libpthread, just the dynamic. It seems they do use > a strong symbol in libpthread, and a weak one in libc: > > vfr [80] $ nm /usr/lib/libc.so.1 | grep pthread_mutex_lock > [4394] | 596188| 44|FUNC |WEAK |0 |12 |_pthread_mutex_lock > [2980] | 596188| 44|FUNC |WEAK |0 |12 |pthread_mutex_lock > vfr [81] $ nm /usr/lib/libpthread.so.1 | grep pthread_mutex_lock > [333] | 20704| 8|FUNC |GLOB |0 |8 |_pthread_mutex_lock > [107] | 20704| 8|FUNC |WEAK |0 |8 |pthread_mutex_lock -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Oct 15 11:55: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 278FB14A28 for ; Fri, 15 Oct 1999 11:54:51 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA02615; Fri, 15 Oct 1999 14:53:24 -0400 (EDT) Date: Fri, 15 Oct 1999 14:53:24 -0400 (EDT) From: "Matthew N. Dodd" To: Edwin Culp Cc: "current@FreeBSD.ORG" Subject: Re: kernel compile problem at ed0 In-Reply-To: <38076F71.C87D36E8@MexComUSA.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 Argh. I know whats wrong but I don't have a good idea on how to cleanly fix it. Comment out: sys/dev/ed/if_ed_isa.c ... in sys/i386/conf/files.i386 and reconfig/make etc. Warner? You mind taking a peek at sys/dev/ed/if_ed_pccard.c and telling me how to fix it so we can get rid of the sys/i386/isa/if_ed.c hackery? AFAIK all that is needed is some way to get the softc struct and to tell the PCCARD system to reserve a softc of ed_softc size. On Fri, 15 Oct 1999, Edwin Culp wrote: > I seem to have a problem compiling a kernel on my laptop with the ed0 > driver that I use for my D-link 660 pcmcia card. > > Running current, cvsup this morning. Make world finished with no problems > but my attempt at kernel compilation yielded: > > > if_ed_isa.o: In function `ed_isa_attach': > > if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' > > if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' > > if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' > > if_ed_isa.o(.text+0x127): undefined reference to `edintr' > > if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' > > if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' > > *** Error code 1 > > > > Stop in /usr/src/sys/compile/LAPTOP. > > >From my cvsup of this morning > > Edit src/sys/dev/ed/if_ed.c > Add delta 1.164 99.10.15.03.12.46 mdodd > Edit src/sys/dev/ed/if_ed_isa.c > Add delta 1.2 99.10.15.03.12.47 mdodd > Edit src/sys/dev/ed/if_ed_pci.c > Add delta 1.22 99.10.15.03.12.47 mdodd > Edit src/sys/dev/ed/if_edvar.h > Add delta 1.3 99.10.15.03.12.47 mdodd > > Maybe I just need to wait for the rest of the changes. > > Thanks, > > ed > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 12:11: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 10E7E15192 for ; Fri, 15 Oct 1999 12:10:22 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-59.netcologne.de [195.14.250.59]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id VAA26264; Fri, 15 Oct 1999 21:10:19 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id VAA02550; Fri, 15 Oct 1999 21:10:37 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Fri, 15 Oct 1999 21:10:37 +0200 (CEST) Message-Id: <199910151910.VAA02550@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-current@freebsd.org Subject: pcm/ES1370 PCI soundcard problem Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So the system builds nice again - thanks. I haven't tried the XFree86 fix yet. However there is a problem with the pcm driver: pcm0: irq 11 at device 15.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 Any idea? I used device pcm0 at pci0 in the kernel configuration file. Regards, Marc PS start of verbose dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #18: Fri Oct 15 18:53:15 CEST 1999 marc@oranje.my.domain:/usr/src/sys/compile/ORANJE Calibrating clock(s) ... TSC clock: 300730129 Hz, i8254 clock: 1193374 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 300684315 Hz CPU: AMD-K6tm w/ multimedia extensions (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 192M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 201326592 (196608K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x002e6000 - 0x0bff5fff, 198246400 bytes (48400 pages) avail memory = 192286720 (187780K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf50 bios32: Entry = 0xfb410 (c00fb410) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb440 pnpbios: Found PnP BIOS data at 0xc00fbfb0 pnpbios: Entry = f0000:bfd8 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02cd000. VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 40 00 02 03 07 01 00 01 0e 01 00 01 17 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 44 mode(s) found VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc027a9c2 (1000022) VESA: NVidia VESA: NVidia Riva TNT A0 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000074 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=55971039) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 58186896 bytes/sec bzero() bandwidth = 58305638 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=55971039) pcib0: on motherboard found-> vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=0 found-> vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[0]: type 1, range 32, base 00006300, size 8 map[1]: type 1, range 32, base e2001000, size 8 found-> vendor=0x1274, dev=0x5000, revid=0x00 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 found-> vendor=0x10de, dev=0x0020, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base e0000000, size 24 map[1]: type 1, range 32, base e1000000, size 24 pci0: on pcib0 i4b_pci_probe: unknown PCI type 1435963449l! isab0: at device 1.0 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa0: on isab0 i4b_pci_probe: unknown PCI type 1427312697l! chip1: irq 0 at device 1.1 on pci0 i4b_pci_probe: unknown PCI type 69632l! ncr0: irq 15 at device 13.0 on pci0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver pcm0: irq 11 at device 15.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 i4b_pci_probe: unknown PCI type 2101470l! vga-pci0: irq 10 at device 17.0 on pci0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 12:48:39 1999 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 974F314ED1 for ; Fri, 15 Oct 1999 12:48:30 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p28-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.157]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id EAA13956; Sat, 16 Oct 1999 04:48:23 +0900 (JST) Message-ID: <38077D51.13BBF13D@newsguy.com> Date: Sat, 16 Oct 1999 04:15:29 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Ilmar S. Habibulin" Cc: freebsd-current@FreeBSD.ORG Subject: Re: jumping from 3.1 to 4.0 References: <199910151019.OAA23486@ws-ilmar.ints.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [And this is one more reason why the default procedure was "world before kernel" -- I have nothing against changing the procedure, as long as people unbreak the new procedure... ] "Ilmar S. Habibulin" wrote: > > I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade > it to current. I read mail-archives and knew, that i had to compile kernel > first. So i made new config and configured and build kernel. While booting > loader prints the next error message and boot fails: > > /kernel text=0x202b9d > elf_loadexec:archsw.readin failed > can't load kernel > > What hould i do to upgrade to current? You need to install a new loader. cd /sys/boot; make depend && make all install. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 13:12:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 2755814D7F for ; Fri, 15 Oct 1999 13:09:34 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id XAA12032; Fri, 15 Oct 1999 23:09:40 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id NAA19240; Fri, 15 Oct 1999 13:20:17 +0400 (MSD) Date: Fri, 15 Oct 1999 13:20:17 +0400 From: Alexey Zelkin To: Bill Swingle Cc: current@FreeBSD.org Subject: Re: boot2 problem Message-ID: <19991015132017.A19180@scorpion.crimea.ua> References: <19991014171747.A11382@scorpion.crimea.ua> <199910150757.AAA00979@dingo.cdrom.com> <19991015114556.A7776@scorpion.crimea.ua> <19991015030944.A93974@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991015030944.A93974@dub.net> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, On Fri, Oct 15, 1999 at 03:09:44AM -0700, Bill Swingle wrote: > > > > Q: What I do then ? > > > > A: On boot prompt type "kernel -v" > > > > > > > > Q: So ? > > > > A: All works fine (system is booting in verbose mode) > > > > > > '-v' is an argument to the kernel. Specify it as such. 8) > > > > If we have default kernel name then why I can't pass parameters there > > and have to excplicitly type kernel name ? > > You don't have to explicitly specify the kernel name. If the default > kernel has already been loaded you just have to tell it what to do. > > 'boot -v' You're talking about loader(8) boot stage and I about boot2 stage (before loader(8) execution) > It's pretty consistant with other OS's boot prompt. Ok, I see that I'll not get answer to my question except "do it otherwise". Sorry. -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Oct 15 13:49:21 1999 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 748AD15169 for ; Fri, 15 Oct 1999 13:49:12 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA32690; Fri, 15 Oct 1999 16:49:07 -0400 (EDT) (envelope-from wollman) Date: Fri, 15 Oct 1999 16:49:07 -0400 (EDT) From: Garrett Wollman Message-Id: <199910152049.QAA32690@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: jack , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > the driver could come back if someone who HAD such a device were to adopt > it.. Probably not. The hardware is just so transcendently evil that it's unlikely it could be made to work reliably for more than one or two people at a time. At some point we need to stop supporting antique hardware since it places a significant burden on the advancement of the rest of the system. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 14: 7: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from p.funk.org (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (Postfix) with ESMTP id A552B15370 for ; Fri, 15 Oct 1999 14:06:54 -0700 (PDT) (envelope-from alexlh@p.funk.org) Received: (from alexlh@localhost) by p.funk.org (8.9.3/8.9.3) id XAA04016; Fri, 15 Oct 1999 23:06:46 +0200 (CEST) (envelope-from alexlh) Date: Fri, 15 Oct 1999 23:06:46 +0200 From: Alex Le Heux To: David Scheidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Can't make crashdump after panic Message-ID: <19991015230646.B3807@funk.org> References: <19991014094853.A323@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from David Scheidt on Thu, Oct 14, 1999 at 09:19:33AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 14, 1999 at 09:19:33AM -0500, David Scheidt wrote: > On Thu, 14 Oct 1999, Alex Le Heux wrote: > > > After configuring the system for making a crashdump, I get "panic: Timeout > > table full" halfway through the dump. > [snip] > > Sounds like your modules are out of date? That bit me. > The panic happened well after the boot. After X had come up. It happened when I logged in and Windowmaker was busy firing up all the crap that I have running in the various places on my screen. I'd love to make a crashdump and poke it, but I've got no idea why it doesn't finish de dump. Alex -- +--------------------------------+-------------------+ | SMTP: | E-Gold: 101979 | | ICBM: N52 22.64'6 E4 51.54'1 | PGP: 0x1d512a3f | +--------------------------------+-------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 14:10:30 1999 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 B205D15319 for ; Fri, 15 Oct 1999 14:10:28 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA09965; Fri, 15 Oct 1999 14:30:52 -0700 (PDT) Date: Fri, 15 Oct 1999 14:30:52 -0700 (PDT) From: Alfred Perlstein To: Alex Le Heux Cc: David Scheidt , freebsd-current@FreeBSD.ORG Subject: Re: Can't make crashdump after panic In-Reply-To: <19991015230646.B3807@funk.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 Fri, 15 Oct 1999, Alex Le Heux wrote: > On Thu, Oct 14, 1999 at 09:19:33AM -0500, David Scheidt wrote: > > On Thu, 14 Oct 1999, Alex Le Heux wrote: > > > > > After configuring the system for making a crashdump, I get "panic: Timeout > > > table full" halfway through the dump. > > > [snip] > > > > Sounds like your modules are out of date? That bit me. > > > > The panic happened well after the boot. After X had come up. It happened > when I logged in and Windowmaker was busy firing up all the crap that I > have running in the various places on my screen. > > I'd love to make a crashdump and poke it, but I've got no idea why it > doesn't finish de dump. What is your memory size? what is your swap device size? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 14:18: 6 1999 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 9260A14D5D for ; Fri, 15 Oct 1999 14:18:05 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA73907; Fri, 15 Oct 1999 16:17:49 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 15 Oct 1999 16:17:49 -0500 (CDT) From: David Scheidt To: Alfred Perlstein Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Can't make crashdump after panic 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 Fri, 15 Oct 1999, Alfred Perlstein wrote: > > What is your memory size? what is your swap device size? 256MB. 512MB. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 14:59:19 1999 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 1639615294 for ; Fri, 15 Oct 1999 14:59:15 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA80319 for ; Fri, 15 Oct 1999 16:59:15 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 15 Oct 1999 16:58:15 -0500 (CDT) From: David Scheidt To: Khetan Gajjar Subject: Re: Can't make crashdump after panic 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 Fri, 15 Oct 1999, Khetan Gajjar wrote: > > Looks like we have our problem; it's the ATA driver. I don't recall > seeing this error when using the wd driver. Yup. When I force a panic from DDB, I get panic: timeout table full and a message about "Dump already in progress, bailing". I haven't yet looked at them dump, to see whats in it. This doesn't happen with wd driver. Relevent bits of my dmesg: SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 DANGER wait_intr active=ATA_IGNORE_INTR ad1: ATA-? disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, DMA Creating DISK ad1 Creating DISK wd1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM unknown medium, unlocked Waiting 15 seconds for SCSI devices to settle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 15: 4: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id E1957153BF for ; Fri, 15 Oct 1999 15:04:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id IAA78446; Sat, 16 Oct 1999 08:07:23 +1000 (EST) (envelope-from jb) Date: Sat, 16 Oct 1999 08:07:23 +1000 From: John Birrell To: Wilko Bulte Cc: current@freebsd.org Subject: Weak symbols (Was: World breakage in libc_r?) Message-ID: <19991016080722.E67481@freebsd1.cimlogic.com.au> References: <199910142225.SAA06440@pcnet1.pcnet.com> <199910151809.UAA63994@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199910151809.UAA63994@yedi.iaf.nl>; from Wilko Bulte on Fri, Oct 15, 1999 at 08:09:57PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote: > Sheer curiosity and most likely a somewhat dim question: > > what the h* is a weak versus a strong symbol? A weak symbol is like an alias for another (strong) symbol. The linker will link to strong symbols first, then, for any unresolved references, it will try to resolve against the weak symbols before going on to the next library. Weak symbols are a good way to hide things in order to stop polluting the name space. But they can cause problems too. Our use of weak symbols in libc is incomplete. Although syscalls like read() have _read() as the strong symbol and read() as the weak one, we continue to call read() in other areas of libc. This means that a user can create their own read() function and they won't get a clash when they link against libc, but other functions in libc that really want to call the _read() syscall will call the user's read() function instead. That's broken. We really need to change libc in the way that NetBSD did with their namespace.h stuff. This ensures that the internals of libc call the hidden names, not the weakly exported ones. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 15:24:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 072FF153D1 for ; Fri, 15 Oct 1999 15:24:18 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 11cFlp-0000jG-00; Fri, 15 Oct 1999 15:24:17 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id PAA02999; Fri, 15 Oct 1999 15:24:12 -0700 Date: Fri, 15 Oct 1999 15:24:12 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: Weak symbols (Was: World breakage in libc_r?) To: John Birrell Cc: current@freebsd.org In-Reply-To: <19991016080722.E67481@freebsd1.cimlogic.com.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 15-Oct-99 at 15:05, John Birrell (jb@cimlogic.com.au) wrote: > On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote: > > Sheer curiosity and most likely a somewhat dim question: > > > > what the h* is a weak versus a strong symbol? > > A weak symbol is like an alias for another (strong) symbol. The linker > will link to strong symbols first, then, for any unresolved references, > it will try to resolve against the weak symbols before going on to > the next library. Weak symbols are a good way to hide things in order > to stop polluting the name space. But they can cause problems too. If so, then the definition has changed since they were first invented. (Around 20 years ago, IIRC.) Weak symbols were/are used to refer to external objects that may or may not actually be linked in. The difference between a weak and a strong symbol is/was that a strong symbol would cause the appropriate library to be loaded to ensure that it would be defined (and generate errors if still unresolved at the end of the link) whereas a weak symbol would not cause a library module to be loaded and would not cause an error if left unresolved. I don't recall any consistant name for the behavour you describe, but it was traditionally handled by the linker control file. (Of course, this was on systems which had somewhat smarter linkers than unix's.) -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 15:32:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id A5A0515133; Fri, 15 Oct 1999 15:32:16 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt03.keycomp.net [207.44.1.5]) by www.keycomp.net (8.8.5/SCO5) with SMTP id SAA29740; Fri, 15 Oct 1999 18:38:54 -0400 (EDT) Message-ID: <001801bf175d$1a9a9940$05012ccf@bopper> From: "Bill A. K." To: "FreeBSD Questions" , Subject: PCI Hardware Modem (Really) Date: Fri, 15 Oct 1999 18:32:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've got a Rockwell PCI Modem thats full hardware, and I was wondering if anybody has written a driver for this kind yet. I saw somebody posted something about they were going to write a driver for such a hardware class. Thanks Bill billieakay@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 Oct 15 15:39:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 00D3E14DA8 for ; Fri, 15 Oct 1999 15:39:40 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA12122; Fri, 15 Oct 1999 15:39:26 -0700 (PDT) Date: Fri, 15 Oct 1999 15:39:26 -0700 (PDT) From: Julian Elischer To: Garrett Wollman Cc: jack , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? In-Reply-To: <199910152049.QAA32690@khavrinen.lcs.mit.edu> 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 hey If someone did adopt it then it wouldn't be a problem.. if no-on edoes then it can remain 'unsupported' On Fri, 15 Oct 1999, Garrett Wollman wrote: > < said: > > > the driver could come back if someone who HAD such a device were to adopt > > it.. > > Probably not. The hardware is just so transcendently evil that it's > unlikely it could be made to work reliably for more than one or two > people at a time. > > At some point we need to stop supporting antique hardware since it > places a significant burden on the advancement of the rest of the > system. > > -GAWollman > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 15:45:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id 251D6153A0 for ; Fri, 15 Oct 1999 15:45:54 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from bone.nectar.com (bone.nectar.com [10.0.0.105]) by gw.nectar.com (Postfix) with ESMTP id 6D381C009; Fri, 15 Oct 1999 17:46:08 -0500 (CDT) Received: from bone.nectar.com (localhost [127.0.0.1]) by bone.nectar.com (Postfix) with ESMTP id 5494A1D65; Fri, 15 Oct 1999 17:45:53 -0500 (CDT) X-Mailer: exmh version 2.1.0 09/18/1999 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG In-reply-to: References: Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 17:45:53 -0500 Message-Id: <19991015224553.5494A1D65@bone.nectar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 October 1999 at 10:20, Julian Elischer wrote: > the driver could come back if someone who HAD such a device were to adopt > it.. I have one (colorado thing). I _will not_ adopt it :-) but I'd happily send it to a committer that wanted to support it. I haven't used it in years, but AFAIK it still works. If no one volunteers (as I suspect), then RIP ft0... -- Jacques Vidrine / n@nectar.com / nectar@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 Oct 15 16: 9:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id D028114BC8 for ; Fri, 15 Oct 1999 16:09:52 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (local-27.local.net [192.168.1.27]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id QAA10730; Fri, 15 Oct 1999 16:08:17 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <3807B443.5BF072DF@MexComUSA.NET> Date: Fri, 15 Oct 1999 16:09:55 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: "current@FreeBSD.ORG" Subject: Re: kernel compile problem at ed0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Clean compile. I haven't rebooted yet, but it should be fine. Thank you, ed "Matthew N. Dodd" wrote: > Argh. I know whats wrong but I don't have a good idea on how to cleanly > fix it. > > Comment out: > > sys/dev/ed/if_ed_isa.c ... > > in sys/i386/conf/files.i386 and reconfig/make etc. > > Warner? You mind taking a peek at sys/dev/ed/if_ed_pccard.c and telling > me how to fix it so we can get rid of the sys/i386/isa/if_ed.c hackery? > AFAIK all that is needed is some way to get the softc struct and to tell > the PCCARD system to reserve a softc of ed_softc size. > > On Fri, 15 Oct 1999, Edwin Culp wrote: > > I seem to have a problem compiling a kernel on my laptop with the ed0 > > driver that I use for my D-link 660 pcmcia card. > > > > Running current, cvsup this morning. Make world finished with no problems > > but my attempt at kernel compilation yielded: > > > > > if_ed_isa.o: In function `ed_isa_attach': > > > if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' > > > if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' > > > if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' > > > if_ed_isa.o(.text+0x127): undefined reference to `edintr' > > > if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' > > > if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' > > > *** Error code 1 > > > > > > Stop in /usr/src/sys/compile/LAPTOP. > > > > >From my cvsup of this morning > > > > Edit src/sys/dev/ed/if_ed.c > > Add delta 1.164 99.10.15.03.12.46 mdodd > > Edit src/sys/dev/ed/if_ed_isa.c > > Add delta 1.2 99.10.15.03.12.47 mdodd > > Edit src/sys/dev/ed/if_ed_pci.c > > Add delta 1.22 99.10.15.03.12.47 mdodd > > Edit src/sys/dev/ed/if_edvar.h > > Add delta 1.3 99.10.15.03.12.47 mdodd > > > > Maybe I just need to wait for the rest of the changes. > > > > Thanks, > > > > ed > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > 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 Oct 15 16:33:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 3FD8614BC8 for ; Fri, 15 Oct 1999 16:33:06 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id TAA59018; Fri, 15 Oct 1999 19:32:48 -0400 (EDT) Date: Fri, 15 Oct 1999 19:32:48 -0400 (EDT) From: jack To: Julian Elischer Cc: Garrett Wollman , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? 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 Today Julian Elischer wrote: > hey If someone did adopt it then it wouldn't be a problem.. > if no-on edoes then it can remain 'unsupported' unsupported != tucked away in the attic, out of reach of many/most users. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 15 17:45:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 0FC7D14D7F for ; Fri, 15 Oct 1999 17:45:26 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id UAA15229 for ; Fri, 15 Oct 1999 20:44:02 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Fri, 15 Oct 1999 20:44:02 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: temperature monitor for windowmaker 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 all those who mailed this list about the temperature monitor apps saying that the device wasn't configured, I have a preliminary version of an app that should work for you. I just finished writing it about 10 minutes ago, and it only shows temperatures, and only shows them in degrees C right now. In about 20 mins from now (9:00 PM EDT) you will be able to get this app from www.wam.umd.edu/~culverk/ Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 0:48:30 1999 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 8A74614D11 for ; Sat, 16 Oct 1999 00:48:24 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p15-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.112]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA18356; Sat, 16 Oct 1999 16:47:03 +0900 (JST) Message-ID: <38082D09.93BC86A6@newsguy.com> Date: Sat, 16 Oct 1999 16:45:13 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexey Zelkin Cc: Bill Swingle , current@FreeBSD.ORG Subject: Re: boot2 problem References: <19991014171747.A11382@scorpion.crimea.ua> <199910150757.AAA00979@dingo.cdrom.com> <19991015114556.A7776@scorpion.crimea.ua> <19991015030944.A93974@dub.net> <19991015132017.A19180@scorpion.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexey Zelkin wrote: > > > It's pretty consistant with other OS's boot prompt. > Ok, I see that I'll not get answer to my question except "do it otherwise". Actually, you got an answer, though you might have missed it. Boot2 does not have "/kernel" as default, but "/boot/loader". Thus, even if we did identify -v as a "parameter" and passed it to what is being loaded, it would be the loader that receives it. Alas, we just don't have a lot of space for boot2, and we'd rather not spend it on things like that. Rather, we decided to keep boot2 simple, and transfer all niceties to a new stage, the loader. Loader is fully featured, has an extended help, and includes a complete structured programming language. We can't fit all of this into boot2, obviously. And if we decided to add "just this feature" to boot2, where would we draw the line? As the requirements for the boot stage increase, so will boot2. It happened before, and that's why we now have a three stage loader. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 1:57:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 71EB114A19 for ; Sat, 16 Oct 1999 01:57:29 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id EAA25342; Sat, 16 Oct 1999 04:57:18 -0400 Date: Sat, 16 Oct 1999 04:57:18 -0400 (EDT) From: Mike Nowlin To: "Ilmar S. Habibulin" Cc: freebsd-current@FreeBSD.ORG Subject: Re: jumping from 3.1 to 4.0 In-Reply-To: <199910151019.OAA23486@ws-ilmar.ints.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade > it to current. I read mail-archives and knew, that i had to compile kernel > first. So i made new config and configured and build kernel. While booting > loader prints the next error message and boot fails: > > /kernel text=0x202b9d > elf_loadexec:archsw.readin failed > can't load kernel > > > What hould i do to upgrade to current? > > PS. answer to email please. > I ran into a similar problem going from 3.1 to 3.3 -- don't remember the exact problem, and my notes are 40 miles away, but I ended up fixing it by cd'ing into the boot code section of the source tree and doing a "make ; make install"...... The archive probably describes this in detail. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 2:57:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id F14701543D for ; Sat, 16 Oct 1999 02:57:45 -0700 (PDT) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@freebsd.org; Sat, 16 Oct 1999 11:57:44 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id LAA01409 for freebsd-current@freebsd.org; Sat, 16 Oct 1999 11:55:11 +0200 (CEST) (envelope-from tanis) Date: Sat, 16 Oct 1999 11:55:11 +0200 From: German Tischler To: freebsd-current@freebsd.org Subject: negative offset for bus_space_read ? Message-ID: <19991016115511.A1156@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I'm in the processing of converting i4b to use newbus calls. The Teles S0/16.3 card has strange way to spread it's io adresses. For example if it is configured for 0xd80 it will use adresses at 0x960, 0x160 and 0x560. So using for example bus_space_read_1 to read from adress 0x160 will not work because the offset parameter is unsigned. Is there a more elegant way than to get the real adress and use inb ? -- German Tischler tanis@gaspode.franken.de tanis@cip.informatik.uni-wuerzburg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 3:42:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 6960D14D31 for ; Sat, 16 Oct 1999 03:42:06 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.90]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA151B; Sat, 16 Oct 1999 12:42:05 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA31558; Sat, 16 Oct 1999 12:41:57 +0200 (CEST) (envelope-from asmodai) Date: Sat, 16 Oct 1999 12:41:57 +0200 From: Jeroen Ruigrok/Asmodai To: jack Cc: Julian Elischer , Garrett Wollman , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? Message-ID: <19991016124157.A31200@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On [19991016 04:00], jack (jack@germanium.xtalwind.net) wrote: >Today Julian Elischer wrote: > >> hey If someone did adopt it then it wouldn't be a problem.. >> if no-on edoes then it can remain 'unsupported' > >unsupported != tucked away in the attic, out of reach of >many/most users. Current != platform for users. Anyone tracking CURRENT should know how to use Attic. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Millions for defence but not one cent for tribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 6:23:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-49.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.49]) by hub.freebsd.org (Postfix) with ESMTP id 5699114C93 for ; Sat, 16 Oct 1999 06:21:43 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA04288 for ; Sat, 16 Oct 1999 14:21:41 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA25422 for ; Sat, 16 Oct 1999 14:23:15 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910161323.OAA25422@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@FreeBSD.org Subject: ftp client Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Oct 1999 14:23:14 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone know what this is all about ? I'm using ``ftp -pV'' as my fetch command. Is ftpd on *all* these systems really stupid enough to time out the control channel when the data channels busy ? Should ftp be changed so that it does the occasional NOOP ? >> Attempting to fetch from ftp://sunsite.informatik.rwth-aachen.de/pub/comp/tex/teTeX/1.0/distrib/sources/. Retrieving pub/comp/tex/teTeX/1.0/distrib/sources/teTeX-texmf-1.0.tar.gz 100% |**************************************************| 31442 KB 00:00 ETA ftp: No control connection for command. >> Attempting to fetch from ftp://ftp.cdrom.com/pub/tex/ctan/systems/unix/teTeX/1.0/distrib/sources//. Retrieving pub/tex/ctan/systems/unix/teTeX/1.0/distrib/sources//teTeX-texmf-1.0.tar.gz 100% |**************************************************| 31442 KB 00:00 ETA ftp: No control connection for command. >> Attempting to fetch from ftp://wuarchive.wustl.edu/packages/TeX/systems/unix/teTeX/1.0/distrib/sources//. Retrieving packages/TeX/systems/unix/teTeX/1.0/distrib/sources//teTeX-texmf-1.0.tar.gz 100% |**************************************************| 31442 KB 00:00 ETA ftp: No control connection for command. >> Attempting to fetch from ftp://ftp.funet.fi/pub/TeX/CTAN/systems/unix/teTeX/1.0/distrib/sources//. Retrieving pub/TeX/CTAN/systems/unix/teTeX/1.0/distrib/sources//teTeX-texmf-1.0.tar.gz -- 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 Sat Oct 16 7:54:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 6174F14EB6; Sat, 16 Oct 1999 07:54:19 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA25576; Sat, 16 Oct 1999 07:54:18 -0700 Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda25574; Sat Oct 16 07:54:09 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id HAA46310; Sat, 16 Oct 1999 07:54:05 -0700 (PDT) Message-Id: <199910161454.HAA46310@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdi46305; Sat Oct 16 07:53:40 1999 X-Mailer: exmh version 2.1.0 09/18/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.3-RELEASE X-Sender: cy To: "Patrick Bihan-Faou" Cc: "Pierre Beyssac" , "David G Andersen" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH)) In-reply-to: Your message of "Wed, 13 Oct 1999 13:04:10 EDT." <011801bf159c$f80630e0$190aa8c0@local.mindstep.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Oct 1999 07:53:39 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <011801bf159c$f80630e0$190aa8c0@local.mindstep.com>, "Patrick Bihan- Faou" writes: > Hi, > > From: Pierre Beyssac > > > There are a _lot_ of pitfalls to this kind of approach, as I have > > discovered using Linux Debian. This would probably open a can of > > worms you have no idea of. IMHO, the single biggest mistake in > > Debian is the all-encompassing package system which can make your > > life miserable in no time. > > [...] > > I was not talking about things that constitute the "real" core of the > distribution (kernel, basic libraries etc.). I was more thinking about > "userland" stuff that is included in the distribution but might not be > required by everybody. Sendmail for example is something I don't want since > I user qmail. However I have to remove it by hand... Other examples are bind > or perl. You don't need to install them. Just put these in make.conf. NO_SENDMAIL= true NOPERL= true NOGAMES= true It might be a good idea to support NONAMED, NOUUCP, and NONFS, defines in make.conf. Since some like to use Qmail, Postfix, SSH, and Kerberos V, like BUILD_PORTS='postfix ssh krb5 XFree86' in make.conf would fetch new copies of distfiles (if you don't have them), de-install old versions, build and install the listed ports each time a make world is performed. We could so far as having a INSTALL_SUID_root='su passwd ...', INSTALL_SUID_man='man', INSTALL_SUID_uucp='uuname uustat uux ...' options, just to name three, which would list all of the setuid binaries in FreeBSD. You would remove the ones you don't need from the list when you secure your system. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 8: 1:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 42C9D14EB6 for ; Sat, 16 Oct 1999 08:01:28 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup4-55.iptelecom.net.ua [212.42.74.247]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA27249 for ; Sat, 16 Oct 1999 18:02:13 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id SAA96737 for ; Sat, 16 Oct 1999 18:00:26 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38089309.9ED02F18@altavista.net> Date: Sat, 16 Oct 1999 18:00:26 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: ed0 broken Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that ed0 is broken. At least two days kernel compilation bombs with following messages: linking kernel if_ed_isa.o: In function `ed_isa_probe': if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x84): undefined reference to `ed_probe_HP_pclanp' if_ed_isa.o(.text+0x93): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0xa4): undefined reference to `ed_alloc_irq' if_ed_isa.o(.text+0xaf): undefined reference to `ed_release_resources' if_ed_isa.o: In function `ed_isa_attach': if_ed_isa.o(.text+0xf4): undefined reference to `ed_alloc_port' if_ed_isa.o(.text+0x10f): undefined reference to `ed_alloc_memory' if_ed_isa.o(.text+0x121): undefined reference to `ed_alloc_irq' if_ed_isa.o(.text+0x12e): undefined reference to `edintr' if_ed_isa.o(.text+0x15a): undefined reference to `ed_attach' if_ed_isa.o(.text+0x162): undefined reference to `ed_release_resources' *** Error code 1 1 error machine i386 cpu I586_CPU ident GENERIC maxusers 10 options FFS options FFS_ROOT options NFS options NFS_NOSERVER #Disable the NFS-server code. options MSDOSFS options CD9660 options INET #InterNETworking options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options NSWAPDEV=1 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION controller isa0 controller pci0 device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ata0 at isa0 port IO_WD1 irq 14 controller ata1 at isa? port IO_WD2 irq 15 device atadisk0 device atapicd0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 options PSM_HOOKAPM device vga0 at isa? port ? conflicts options VESA options SC_PIXEL_MODE device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device apm0 at nexus? controller card0 controller pcic0 at isa? controller pcic1 at isa? device ed0 options PCIC_RESUME_RESET options POWERFAIL_NMI device ppc0 at isa? port ? irq 7 controller ppbus0 controller plip0 at ppbus? # Various Pseudo-Devices pseudo-device loop pseudo-device ether pseudo-device pty 8 pseudo-device gzip pseudo-device splash options SYSVSHM options SYSVSEM options SYSVMSG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 8:36:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id B040F1506C for ; Sat, 16 Oct 1999 08:36:25 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup4-55.iptelecom.net.ua [212.42.74.247]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA29273; Sat, 16 Oct 1999 18:37:22 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id SAA96825; Sat, 16 Oct 1999 18:35:49 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38089B55.F3F5EDED@altavista.net> Date: Sat, 16 Oct 1999 18:35:49 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: temperature monitor for windowmaker References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Culver wrote: > For all those who mailed this list about the temperature monitor apps > saying that the device wasn't configured, I have a preliminary version of > an app that should work for you. I just finished writing it about 10 > minutes ago, and it only shows temperatures, and only shows them in > degrees C right now. In about 20 mins from now (9:00 PM EDT) you will be > able to get this app from www.wam.umd.edu/~culverk/ Hm, is it only mine problem or that archive is really only 63 bytes long? wget -Y off http://www.wam.umd.edu/~culverk/wmtempmon-0.1.tar.gz --18:31:42-- http://www.wam.umd.edu:80/%7Eculverk/wmtempmon-0.1.tar.gz => `wmtempmon-0.1.tar.gz' Connecting to www.wam.umd.edu:80... connected! HTTP request sent, awaiting response... 200 OK Length: 63 [application/x-gzip] 0K -> [100%] 18:32:17 (5.59 KB/s) - `wmtempmon-0.1.tar.gz' saved [63/63] -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 9:30:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 5004114CCB for ; Sat, 16 Oct 1999 09:30:25 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id JAA72675; Sat, 16 Oct 1999 09:30:13 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <3808A824.DA7AD078@MexComUSA.NET> Date: Sat, 16 Oct 1999 09:30:28 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: sobomax@altavista.net Cc: current@FreeBSD.ORG Subject: Re: ed0 broken References: <38089309.9ED02F18@altavista.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > It seems that ed0 is broken. At least two days kernel compilation bombs with > following messages: > > linking kernel > if_ed_isa.o: In function `ed_isa_probe': > if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' > if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' I had the same problem yesterday and Matthew Dodd sent me the following fix that worked fine. I recompiled the kernel and am now using it with ed0. Just comment out the following line in /usr/src/sys/i386/conf/files.i386 sys/dev/ed/if_ed_isa.c run config again and make depend , etc. provecho and thanks again to Matthew, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 9:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 186AE14CCB for ; Sat, 16 Oct 1999 09:32:41 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id JAA72684; Sat, 16 Oct 1999 09:32:26 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <3808A8A9.93DE3716@MexComUSA.NET> Date: Sat, 16 Oct 1999 09:32:42 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: sobomax@altavista.net Cc: Kenneth Culver , freebsd-current@FreeBSD.ORG Subject: Re: temperature monitor for windowmaker References: <38089B55.F3F5EDED@altavista.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got 63 bytes also. ed Maxim Sobolev wrote: > Kenneth Culver wrote: > > > For all those who mailed this list about the temperature monitor apps > > saying that the device wasn't configured, I have a preliminary version of > > an app that should work for you. I just finished writing it about 10 > > minutes ago, and it only shows temperatures, and only shows them in > > degrees C right now. In about 20 mins from now (9:00 PM EDT) you will be > > able to get this app from www.wam.umd.edu/~culverk/ > > Hm, is it only mine problem or that archive is really only 63 bytes long? > > wget -Y off http://www.wam.umd.edu/~culverk/wmtempmon-0.1.tar.gz > --18:31:42-- http://www.wam.umd.edu:80/%7Eculverk/wmtempmon-0.1.tar.gz > => `wmtempmon-0.1.tar.gz' > Connecting to www.wam.umd.edu:80... connected! > HTTP request sent, awaiting response... 200 OK > Length: 63 [application/x-gzip] > > 0K -> [100%] > > 18:32:17 (5.59 KB/s) - `wmtempmon-0.1.tar.gz' saved [63/63] > > -Maxim > > 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 Oct 16 10:10:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 8FB6B15059 for ; Sat, 16 Oct 1999 10:10:06 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id NAA05718; Sat, 16 Oct 1999 13:09:41 -0400 (EDT) Date: Sat, 16 Oct 1999 13:09:40 -0400 (EDT) From: jack To: Jeroen Ruigrok/Asmodai Cc: Julian Elischer , Garrett Wollman , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? In-Reply-To: <19991016124157.A31200@daemon.ninth-circle.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 Today Jeroen Ruigrok/Asmodai wrote: > On [19991016 04:00], jack (jack@germanium.xtalwind.net) wrote: > >Today Julian Elischer wrote: > > > >> hey If someone did adopt it then it wouldn't be a problem.. > >> if no-on edoes then it can remain 'unsupported' > > > >unsupported != tucked away in the attic, out of reach of > >many/most users. > > Current != platform for users. > > Anyone tracking CURRENT should know how to use Attic. Agreed, but my original statement was: It might help if HARDWARE.TXT (both -current and -stable) didn't list floppy tapes. It refers to the driver as "stale" rather than gone. The driver has been listed that way through all of the 3.x releases, which is the platform for users, and will probably still be listed the same way when 4.0 is released. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 10:25: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ints.ru (ints.ru [194.67.173.1]) by hub.freebsd.org (Postfix) with ESMTP id 0766714FA8 for ; Sat, 16 Oct 1999 10:24:53 -0700 (PDT) (envelope-from ilmar@ints.ru) Received: (from uucp@localhost) by ints.ru (8.9.2/8.9.2) id VAA13695; Sat, 16 Oct 1999 21:24:51 +0400 (MSD) Received: from ws-ilmar.ints.ru(194.67.173.16) via SMTP by ints.ru, id smtpdP13693; Sat Oct 16 21:24:50 1999 Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id VAA02128; Sat, 16 Oct 1999 21:24:49 +0400 (MSD) Date: Sat, 16 Oct 1999 21:24:48 +0400 (MSD) From: "Ilmar S. Habibulin" To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: jumping from 3.1 to 4.0 In-Reply-To: <38077D51.13BBF13D@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, 16 Oct 1999, Daniel C. Sobral wrote: > > What hould i do to upgrade to current? > You need to install a new loader. cd /sys/boot; make depend && make > all install. I tried to so, but making new boot loader failedwith an error like 'use of undefined type in line 46' in ucontext.h. I do not remember the exact error message. It is far away from me right now. Maybe i should take already compiled loader? And would it boot freebsd 3.x kernel, if my upgrade fails again? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 10:29:44 1999 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 8E3B214BEB for ; Sat, 16 Oct 1999 10:29:33 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 38977 invoked by uid 1001); 16 Oct 1999 17:29:31 +0000 (GMT) To: freebsd-current@freebsd.org Subject: current unable to attach USB, Power Mgmt, sound From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 16 Oct 1999 19:29:31 +0200 Message-ID: <38975.940094971@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current as of 8. october attached USB, Power Mgmt, sound just fine. Current as of today no longer does. Here are the relevant bits of a dmesg diff: < usb0: on uhci0 < uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 < uhub0: 2 ports with 2 removable, self powered --- > uhci0: could not map ports > device_probe_and_attach: uhci0 attach returned 6 < intpm0: I/O mapped 5000 < intpm0: intr IRQ 9 enabled revision 0 < smbus0: on intsmb0 < smb0: on smbus0 < intpm0: PM I/O mapped 4000 --- > intpm0: Could not allocate Bus space > device_probe_and_attach: intpm0 attach returned 6 > pcm0: unable to map register space > device_probe_and_attach: pcm0 attach returned 6 This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is the complete dmesg from today's current, and the kernel config. (The "pci0: unknown card" is the HPT ATA-66 controller on the BP6 board.) It may be relevant that fxp0, pcm0 and uhci0 all use IRQ 19. However, fxp0 works just fine - I can login the machine across the net. Any ideas? Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Oct 16 13:57:17 CEST 1999 sthaug@bp6.nethelp.no:/local/freebsd-current/src/sys/compile/BP6_MP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (367.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 257048576 (251024K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 uhci0: irq 19 at device 7.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 Timecounter "PIIX" frequency 3579545 Hz intpm0: at device 7.3 on pci0 intpm0: Could not allocate Bus space device_probe_and_attach: intpm0 attach returned 6 pcm0: irq 19 at device 9.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 ti0: irq 18 at device 11.0 on pci0 ti0: Ethernet address: 00:a0:cc:73:32:dd ncr0: irq 17 at device 13.0 on pci0 pcm1: irq 16 at device 15.0 on pci0 fxp0: irq 19 at device 17.0 on pci0 fxp0: Ethernet address 00:a0:c9:b6:df:4b pci0: unknown card (vendor=0x1103, dev=0x0004) at 19.0 irq 18 pci0: unknown card (vendor=0x1103, dev=0x0004) at 19.1 irq 18 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 3 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK cd0 changing root device to wd0s1d cd0 at ncr0 bus 0 target 3 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 ---------------------------------------------------------------------- # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.195 1999/10/16 05:24:12 wpaul Exp $ machine i386 cpu I686_CPU ident BP6_MP maxusers 32 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES options MSGBUF_SIZE=32768 options INCLUDE_CONFIG_FILE # Include this file in kernel options DDB options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O controller isa0 controller pnp0 # PnP support for ISA controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 #device wcd0 #IDE CD-ROM controller ncr0 # NCR/Symbios Logic controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 device pcm0 controller smbus0 controller iicbus0 controller iicbb0 controller intpm0 device smb0 at smbus? device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device ti0 # Alteon Tigon based cards (Netgear GA620 etc) pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf #Berkeley packet filter controller uhci0 # UHCI PCI->USB interface controller ohci0 # OHCI PCI->USB interface controller usb0 # USB Bus (required) device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 10:35:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 333A414BEB for ; Sat, 16 Oct 1999 10:35:31 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id NAA29560; Sat, 16 Oct 1999 13:35:30 -0400 (EDT) Date: Sat, 16 Oct 1999 13:35:30 -0400 (EDT) From: "Matthew N. Dodd" To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: ed0 broken In-Reply-To: <38089309.9ED02F18@altavista.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 Sat, 16 Oct 1999, Maxim Sobolev wrote: > It seems that ed0 is broken. At least two days kernel compilation > bombs with following messages: Comment out sys/dev/ed/if_ed_isa.c in sys/i386/conf/files.i386 if you're going to make a kernel that uses PCCARD. Hopefully the recent changes to the PCCARD system will allow us to start using the newbus front end instead of the current hack that is in place. If people using laptops with -current aren't going to read their email then they should run -current. I suppose I could wrap if_ed_isa.c in the same nonesense that if_ed.c uses but I'd rather not as I suspect a fix is in the near term future. > linking kernel > if_ed_isa.o: In function `ed_isa_probe': > if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' > if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' > if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' > if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x84): undefined reference to `ed_probe_HP_pclanp' > if_ed_isa.o(.text+0x93): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0xa4): undefined reference to `ed_alloc_irq' > if_ed_isa.o(.text+0xaf): undefined reference to `ed_release_resources' > if_ed_isa.o: In function `ed_isa_attach': > if_ed_isa.o(.text+0xf4): undefined reference to `ed_alloc_port' > if_ed_isa.o(.text+0x10f): undefined reference to `ed_alloc_memory' > if_ed_isa.o(.text+0x121): undefined reference to `ed_alloc_irq' > if_ed_isa.o(.text+0x12e): undefined reference to `edintr' > if_ed_isa.o(.text+0x15a): undefined reference to `ed_attach' > if_ed_isa.o(.text+0x162): undefined reference to `ed_release_resources' > *** Error code 1 > 1 error > > machine i386 > cpu I586_CPU > ident GENERIC > maxusers 10 > > options FFS > options FFS_ROOT > options NFS > options NFS_NOSERVER #Disable the NFS-server code. > options MSDOSFS > options CD9660 > options INET #InterNETworking > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options NSWAPDEV=1 > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L > options CLK_USE_I8254_CALIBRATION > options CLK_USE_TSC_CALIBRATION > > controller isa0 > controller pci0 > > device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 > > controller fdc0 at isa? port IO_FD1 irq 6 drq 2 > disk fd0 at fdc0 drive 0 > > controller ata0 at isa0 port IO_WD1 irq 14 > controller ata1 at isa? port IO_WD2 irq 15 > device atadisk0 > device atapicd0 > > controller atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > device psm0 at atkbdc? irq 12 > options PSM_HOOKAPM > > device vga0 at isa? port ? conflicts > options VESA > options SC_PIXEL_MODE > device sc0 at isa? > > device npx0 at nexus? port IO_NPX irq 13 > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > > device apm0 at nexus? > > controller card0 > controller pcic0 at isa? > controller pcic1 at isa? > device ed0 > options PCIC_RESUME_RESET > options POWERFAIL_NMI > > device ppc0 at isa? port ? irq 7 > controller ppbus0 > controller plip0 at ppbus? > > # Various Pseudo-Devices > pseudo-device loop > pseudo-device ether > pseudo-device pty 8 > pseudo-device gzip > pseudo-device splash > > options SYSVSHM > options SYSVSEM > options SYSVMSG > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 10:53:31 1999 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 5F18F14BEB for ; Sat, 16 Oct 1999 10:53:25 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA45007 for ; Sat, 16 Oct 1999 10:53:25 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA10331 for current@FreeBSD.ORG; Sat, 16 Oct 1999 10:53:25 -0700 (PDT) (envelope-from obrien) Date: Sat, 16 Oct 1999 10:53:25 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: ed0 broken Message-ID: <19991016105325.A10230@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <38089309.9ED02F18@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If people using laptops with -current aren't going to read their email > then they should run -current. I suppose I could wrap if_ed_isa.c in the > same nonesense that if_ed.c uses but I'd rather not as I suspect a fix is > in the near term future. NO! Committers shouldn't commit code that is known not to compile. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 11:21: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B6626151F5 for ; Sat, 16 Oct 1999 11:21:05 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA00463; Sat, 16 Oct 1999 14:19:49 -0400 (EDT) Date: Sat, 16 Oct 1999 14:19:48 -0400 (EDT) From: "Matthew N. Dodd" To: Edwin Culp Cc: sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: ed0 broken In-Reply-To: <3808A824.DA7AD078@MexComUSA.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 Sat, 16 Oct 1999, Edwin Culp wrote: > I had the same problem yesterday and Matthew Dodd sent me the > following fix that worked fine. I recompiled the kernel and am now > using it with ed0. Ok, if someone could test the following patch: ftp://ftp.jurai.net/users/winter/patches/if_ed_pccard.diff I'd appriciate it. download the patch, apply it in sys/dev/ed, edit files.i386 and uncomment sys/dev/ed/if_ed_pccard.c. Re-config & make. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 11:45:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop3.dnvr.uswest.net (dnvrpop3.dnvr.uswest.net [206.196.128.5]) by hub.freebsd.org (Postfix) with SMTP id BCF2415227 for ; Sat, 16 Oct 1999 11:45:19 -0700 (PDT) (envelope-from sitongia@uswest.net) Received: (qmail 11707 invoked by alias); 16 Oct 1999 18:45:19 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 11683 invoked by uid 0); 16 Oct 1999 18:45:18 -0000 Received: from oodialup242.dnvr.uswest.net (HELO ?204.107.134.7?) (63.225.124.242) by dnvrpop3.dnvr.uswest.net with SMTP; 16 Oct 1999 18:45:18 -0000 X-Sender: sitongia@pop.dnvr.uswest.net Message-Id: In-Reply-To: References: <3808A824.DA7AD078@MexComUSA.NET> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 16 Oct 1999 12:47:22 -0600 To: "Matthew N. Dodd" , Edwin Culp From: Leonard Sitongia Subject: Re: ed0 broken Cc: sobomax@altavista.net, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:19 PM -0400 10/16/99, Matthew N. Dodd wrote: >On Sat, 16 Oct 1999, Edwin Culp wrote: >> I had the same problem yesterday and Matthew Dodd sent me the >> following fix that worked fine. I recompiled the kernel and am now >> using it with ed0. > >Ok, if someone could test the following patch: > >ftp://ftp.jurai.net/users/winter/patches/if_ed_pccard.diff > >I'd appriciate it. > >download the patch, apply it in sys/dev/ed, edit files.i386 and uncomment >sys/dev/ed/if_ed_pccard.c. Re-config & make. I've tried it, and if_ed_pccard.c compiles now (Warner, that addresses the error messages that I recently sent you mail about). ==Leonard Sitongia sitongia@uswest.net http://www.users.uswest.net/~sitongia/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 11:45:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id A5C2F154E2 for ; Sat, 16 Oct 1999 11:45:24 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA73247; Sat, 16 Oct 1999 19:47:30 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 16 Oct 1999 19:47:30 +0100 (BST) From: Doug Rabson To: sthaug@nethelp.no Cc: freebsd-current@freebsd.org Subject: Re: current unable to attach USB, Power Mgmt, sound In-Reply-To: <38975.940094971@verdi.nethelp.no> 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, 16 Oct 1999 sthaug@nethelp.no wrote: > Current as of 8. october attached USB, Power Mgmt, sound just fine. > Current as of today no longer does. Here are the relevant bits of a > dmesg diff: I think I broke something with my last change to pci. Could you send me a verbose dmesg. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 11:49: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 958C715227 for ; Sat, 16 Oct 1999 11:49:06 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA01062; Sat, 16 Oct 1999 14:47:49 -0400 (EDT) Date: Sat, 16 Oct 1999 14:47:49 -0400 (EDT) From: "Matthew N. Dodd" To: Leonard Sitongia Cc: Edwin Culp , sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: ed0 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 On Sat, 16 Oct 1999, Leonard Sitongia wrote: > >download the patch, apply it in sys/dev/ed, edit files.i386 and uncomment > >sys/dev/ed/if_ed_pccard.c. Re-config & make. > > I've tried it, and if_ed_pccard.c compiles now (Warner, that addresses > the error messages that I recently sent you mail about). But does it work? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 12:16:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 23A5E14C3C for ; Sat, 16 Oct 1999 12:16:05 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id PAA04051; Sat, 16 Oct 1999 15:14:36 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 16 Oct 1999 15:14:36 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Cc: ppjmao@wam.umd.edu Subject: wmtempmon temperature monitor app 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 Sorry for the inconvenience, it must have gotten corrupted somehow. It is fixed now, I just fixed it. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 13:14:50 1999 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 E8007154BE for ; Sat, 16 Oct 1999 13:14:38 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA39426; Sat, 16 Oct 1999 16:13:21 -0400 (EDT) (envelope-from wollman) Date: Sat, 16 Oct 1999 16:13:21 -0400 (EDT) From: Garrett Wollman Message-Id: <199910162013.QAA39426@khavrinen.lcs.mit.edu> To: German Tischler Cc: freebsd-current@FreeBSD.ORG Subject: negative offset for bus_space_read ? In-Reply-To: <19991016115511.A1156@gaspode.franken.de> References: <19991016115511.A1156@gaspode.franken.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Is there a more elegant way than to get the real adress and > use inb ? You need to allocate resources for each distinct, non-contiguous range of ports separately. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 14: 0:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop3.dnvr.uswest.net (dnvrpop3.dnvr.uswest.net [206.196.128.5]) by hub.freebsd.org (Postfix) with SMTP id 24422154F4 for ; Sat, 16 Oct 1999 14:00:32 -0700 (PDT) (envelope-from sitongia@uswest.net) Received: (qmail 5561 invoked by alias); 16 Oct 1999 21:00:32 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 5548 invoked by uid 0); 16 Oct 1999 21:00:31 -0000 Received: from oodialup242.dnvr.uswest.net (HELO ?204.107.134.7?) (63.225.124.242) by dnvrpop3.dnvr.uswest.net with SMTP; 16 Oct 1999 21:00:31 -0000 X-Sender: sitongia@pop.dnvr.uswest.net Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 16 Oct 1999 15:02:36 -0600 To: "Matthew N. Dodd" From: Leonard Sitongia Subject: Re: ed0 broken Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:47 PM -0400 10/16/99, Matthew N. Dodd wrote: >On Sat, 16 Oct 1999, Leonard Sitongia wrote: >> >download the patch, apply it in sys/dev/ed, edit files.i386 and uncomment >> >sys/dev/ed/if_ed_pccard.c. Re-config & make. >> >> I've tried it, and if_ed_pccard.c compiles now (Warner, that addresses >> the error messages that I recently sent you mail about). > >But does it work? No, but then I haven't ever gotten it working in the month or so that I've been running current on this Toshiba Portege 3110. Here's what happens: Oct 16 14:56:48 becker /kernel: pcic0: at irq 15 on isa0 Oct 16 14:56:48 becker /kernel: pccard1: on pcic 0 ... Oct 16 14:56:48 becker /kernel: pccard: initalizing drivers: ep fe ... (plug a Linksys Ethernet card in:) Oct 16 14:58:37 becker /kernel: pccard: card inserted, slot 0 Oct 16 14:58:48 becker pccardd[42]: driver allocation failed for LINKSYS(E-CARD) : Device not configured This is the PCCARD kernel with no changes. All pccard stuff is enabled in rc.conf. ==Leonard Sitongia sitongia@uswest.net http://www.users.uswest.net/~sitongia/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 14:38:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 7AE4014DFF for ; Sat, 16 Oct 1999 14:38:54 -0700 (PDT) (envelope-from eculp@EnContacto.NET) Received: from EnContacto.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id OAA74383; Sat, 16 Oct 1999 14:37:21 -0700 (PDT) (envelope-from eculp@EnContacto.NET) Message-ID: <3808F023.47448973@EnContacto.NET> Date: Sat, 16 Oct 1999 14:37:39 -0700 From: Edwin Culp Organization: EnContacto.NET X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Leonard Sitongia Cc: "Matthew N. Dodd" , current@FreeBSD.ORG Subject: Re: ed0 broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leonard Sitongia wrote: > At 2:47 PM -0400 10/16/99, Matthew N. Dodd wrote: > >On Sat, 16 Oct 1999, Leonard Sitongia wrote: > >> >download the patch, apply it in sys/dev/ed, edit files.i386 and uncomment > >> >sys/dev/ed/if_ed_pccard.c. Re-config & make. > >> > >> I've tried it, and if_ed_pccard.c compiles now (Warner, that addresses > >> the error messages that I recently sent you mail about). > > > >But does it work? > > No, but then I haven't ever gotten it working in the month or so that > I've been running current on this Toshiba Portege 3110. Here's what > happens: > > Oct 16 14:56:48 becker /kernel: pcic0: at irq 15 on isa0 > Oct 16 14:56:48 becker /kernel: pccard1: on > pcic > 0 > ... > Oct 16 14:56:48 becker /kernel: pccard: initalizing drivers: ep fe I don't see your ed driver. Is it in your kernel configuration file? You don't really need ep IMHO and I don't know what fe is :-) Mine says: pcic: pccard bridge VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 9 pccard: initalizing drivers: ed Kernel config es device ed0 no more > > ... > (plug a Linksys Ethernet card in:) I always bring it up with the card in, cowards way out. > > > Oct 16 14:58:37 becker /kernel: pccard: card inserted, slot 0 > Oct 16 14:58:48 becker pccardd[42]: driver allocation failed for > LINKSYS(E-CARD) > : Device not configured > > This is the PCCARD kernel with no changes. All pccard stuff is enabled I've always had a problem with that and have resorted to configuring it in rc.local. sleep 10 ifconfig ed0 inet 192.168.1.27 netmask 255.255.255.0 route add default 192.168.1.1 Again cowards way out but works fine:-) Hope that helps, ed pccard.conf is io 0x240-0x360 irq 9 11 memory 0xd4000 96k # D-Link DE-660 NE2000 clone card "D-Link" "DE-660" config 0x20 "ed0" 11 # ether 0x81 insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete > > in rc.conf. > > ==Leonard Sitongia > sitongia@uswest.net > http://www.users.uswest.net/~sitongia/ > > 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 Oct 16 15:56:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 8285314C4A for ; Sat, 16 Oct 1999 15:55:57 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id AAA29042 for ; Sun, 17 Oct 1999 00:55:51 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id AAA01004 for current@FreeBSD.ORG; Sun, 17 Oct 1999 00:55:45 +0200 (CEST) (envelope-from andreas) Date: Sun, 17 Oct 1999 00:55:45 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Subject: -current problem: Network cards doesn't run Message-ID: <19991017005544.B973@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See ed0.... When running a current kernel of some days ago, no problems. Were there perhaps changes in the last days that introduce this, that some NICs doesn't run ? Even the xl0 interface didn't run (DMZ). Ping to hosts in internet didn't succeed. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Oct 17 00:40:49 CEST 1999 root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 159383552 (155648K bytes) avail memory = 151044096 (147504K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc030c000. Pentium Pro MTRR support enabled ccd0-3: Concatenated disk drivers npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.1 on pci0 vga-pci0: at device 10.0 on pci0 xl0: <3Com 3c900-COMBO Etherlink XL> irq 19 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: selecting 10baseT transceiver, half duplex pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 18 pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 ahc0: irq 17 at device 13.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: irq 16 at device 14.0 on pci0 ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 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: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default DUMMYNET initialized (990811) Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 sa0 at ahc1 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) Creating DISK cd0 Creating DISK cd1 changing root device to da0s2a cd1 at ahc1 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: Attempt to query device size failed: NOT READY, Medium not present cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ed0: remote transmit DMA failed to complete ^^^^ ed0: NIC memory corrupt - invalid packet length 11564 ^^^^ xl0: promiscuous mode enabled -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 20: 6:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 9923314CF6 for ; Sat, 16 Oct 1999 20:06:40 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Received: from MexComUSA.NET (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id UAA75990; Sat, 16 Oct 1999 20:05:00 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <38093CE5.6CDA842E@MexComUSA.NET> Date: Sat, 16 Oct 1999 20:05:09 -0700 From: Edwin Culp Organization: EnContacto.NET X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: ed0 broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > On Sat, 16 Oct 1999, Edwin Culp wrote: > > I had the same problem yesterday and Matthew Dodd sent me the > > following fix that worked fine. I recompiled the kernel and am now > > using it with ed0. > > Ok, if someone could test the following patch: > > ftp://ftp.jurai.net/users/winter/patches/if_ed_pccard.diff > > I'd appriciate it. > > download the patch, apply it in sys/dev/ed, edit files.i386 and uncomment > sys/dev/ed/if_ed_pccard.c. Re-config & make. I tested it and it didn't quite work. It compiled clean and looked as if it were going to work, but a cut of the message when booting starting local daemons:Oct 16 19:02:28 local-27 pccardd[56]: driver allocation f ailed for D-Link(DE-660): Device not configured Oct 16 19:02:28 local-27 pccardd[56]: pccardd started ifconfig: interface ed0 does not exist route: writing to routing socket: Network is unreachable add net default: gateway 192.168.1.1: Network is unreachable This is a difference between the two dmesg's that I don't understand. This is from todays world and kernel. Oct 16 19:12:12 local-27 /kernel: pcic: polling, can't alloc 0 Oct 16 19:12:12 local-27 /kernel: pcic: polling, can't alloc 0 Oct 16 19:12:12 local-27 /kernel: pcic0: on isa0 Oct 16 19:12:12 local-27 /kernel: pccard1: on pc ic0 Oct 16 19:12:12 local-27 /kernel: pccard2: on pc ic0 This is the kernel that works from yesterday. Oct 16 19:42:19 local-27 /kernel.old.safe: pcic: pccard bridge VLSI 82C146 (5 me m & 2 I/O windows) Oct 16 19:42:19 local-27 /kernel.old.safe: pcic: controller irq 9 Oct 16 19:42:19 local-27 /kernel.old.safe: pccard: initalizing drivers: ed Hope that helps. I don't understand but will try to look it tomorrow morning when I'm fresh. I'll build a new world and two kernels and test them. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 16 23:43:25 1999 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 4DA2C14F21 for ; Sat, 16 Oct 1999 23:43:12 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p26-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.123]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA16417; Sun, 17 Oct 1999 15:42:57 +0900 (JST) Message-ID: <38096F7E.3065767E@newsguy.com> Date: Sun, 17 Oct 1999 15:41:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Ilmar S. Habibulin" Cc: freebsd-current@FreeBSD.ORG Subject: Re: jumping from 3.1 to 4.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ilmar S. Habibulin" wrote: > > On Sat, 16 Oct 1999, Daniel C. Sobral wrote: > > > > What hould i do to upgrade to current? > > You need to install a new loader. cd /sys/boot; make depend && make > > all install. > I tried to so, but making new boot loader failedwith an error like 'use of > undefined type in line 46' in ucontext.h. I do not remember the exact > error message. It is far away from me right now. Maybe i should take > already compiled loader? And would it boot freebsd 3.x kernel, if my > upgrade fails again? You could do that, and it would load your kernel. Your best option, though, it's to jump first to 3.3-stable. But before you do that, could you please give me the error log? Loader should have *not* been affected by the signal changes! -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message