From owner-freebsd-current Sun Jun 9 03:46:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA16627 for current-outgoing; Sun, 9 Jun 1996 03:46:52 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA16402 for ; Sun, 9 Jun 1996 03:46:11 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id LAA07863; Sun, 9 Jun 1996 11:45:37 +0100 (BST) To: Peter Mutsaers cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: More on VM, swap leaks In-reply-to: Your message of "08 Jun 1996 07:54:57 +0200." <87d93ac026.fsf@plm.xs4all.nl> Date: Sun, 09 Jun 1996 11:45:36 +0100 Message-ID: <7861.834317136@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Peter Mutsaers wrote in message ID <87d93ac026.fsf@plm.xs4all.nl>: > But the FreeBSD man pages suggest that it is not ignored. *WHICH* FreeBSD man page, and I'll go correct it. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sun Jun 9 05:10:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA17561 for current-outgoing; Sun, 9 Jun 1996 05:10:29 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA17535 for ; Sun, 9 Jun 1996 05:10:25 -0700 (PDT) Received: from socrate.gea.org (ts1port4d.masternet.it [194.184.65.26]) by masternet.it (8.6.12/8.6.9) with SMTP id NAA20657; Sun, 9 Jun 1996 13:07:16 +0200 Message-ID: <31BAA984.167EB0E7@masternet.it> Date: Sun, 09 Jun 1996 12:37:56 +0200 From: Beck Peccoz Amedeo X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Aaron D. Gifford" CC: freebsd-current@FreeBSD.ORG Subject: Re: PONY UP! (was: The -stable problem: my view) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Aaron D. Gifford wrote: > Ideas: Why not add a web page or two on the www.freebsd.org site describing > how to contribute money, hardware, labor, etc? The page might suggest a > tiered donation scheme (perhaps something like $25, $50, $100, $200, $500, > $1000, etc. donations per install or upgrade) where donors are listed on How about requesting a fee to enter this mailing list? I've been really impressed on how FreeBSD is managed: people pay nothing (do you consider $14.95 more than nothing?) to receive at their homes a copy of a BSD Unix, and then they pay nothing (in the real meaning of "not a single dollar") to have FREE, QUICK and EASY assistance from THE CORE TEAM developing the system. Whoelse gives you such a service? Why we shouldn't pay for this? Where is it written that we have to be fully assisted for free? If we need/want the -stable not to die we have to pay. So let's pay and stop wasting bandwidth on the net with this subject. -- Beck-Peccoz Amedeo GEA Software S.r.l. Via Deffeyes, 1 11025 Gressoney Saint Jean (AO) ITALY Tel. ++39-125-366302 Fax. ++39-125-366415 From owner-freebsd-current Sun Jun 9 06:00:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07506 for current-outgoing; Sun, 9 Jun 1996 06:00:56 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07409; Sun, 9 Jun 1996 06:00:35 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id OAA09383; Sun, 9 Jun 1996 14:45:23 +0200 (MET DST) Received: from klemm.gtn.com (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id OAA00554; Sun, 9 Jun 1996 14:43:20 +0200 (MET DST) Message-ID: <31BAC6E7.41C67EA6@klemm.gtn.com> Date: Sun, 09 Jun 1996 14:43:19 +0200 From: Andreas Klemm Organization: Home X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: as@advasoft.com CC: current@FreeBSD.org, jkh@FreeBSD.org Subject: Linux binary Version of asWedit 2.5 fails to run on FreeBSD-current X-URL: http://sunsite.doc.ic.ac.uk/packages/www/asWedit/ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Well, I tried to download an evaluation version of asWedit, a HTML Editor, that is available for different platforms, even Linux and SCO, but it fails to run on FreeBSD-current. I compiled the kernel with the options COMPAT_LINUX and am able to run for example the Linux Netscape version without trouble. The message that I get in the console is: Jun 9 14:36:32 klemm /kernel: pid 521 (asWedit), uid 1000: exited on signal 11 and in the shell window Warning: locale not supported by C library, locale unchanged Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default Speicherschutzverletzung (core dumped) Changing the locale doesn't help. Would be nice if they could offer BSDI or even a FreeBSD version of the program. If you are interested in further informations about asWedit: http://sunsite.doc.ic.ac.uk/packages/www/asWedit/ To bad, looked like a smart program, that is free for private use and students... A commercial Version is available, too ... Could someone perhaps try convince the company, to offer FreeBSD or BSDI binaries, to get a chance, to look , what it can do ? Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sun Jun 9 07:14:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA02100 for current-outgoing; Sun, 9 Jun 1996 07:14:31 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA02073 for ; Sun, 9 Jun 1996 07:14:24 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.6.9) id JAA29772 for freebsd-current@freefall.cdrom.com; Sun, 9 Jun 1996 09:14:31 -0500 (CDT) From: Bob Willcox Message-Id: <199606091414.JAA29772@luke.pmr.com> Subject: Libc compatibility in -current?? To: freebsd-current@freefall.FreeBSD.org (freebsd-current) Date: Sun, 9 Jun 1996 09:14:31 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lately I have been having what appears to be compatibility problems with libc.so.3.0 when I do a make world on my systems running -current. Starting on June 3rd (my most recent make world prior to that was May 31st) any attempt to run make world crashes in a horrible way right after it has installed a newly built version of libc.so.3.0 in /usr/lib. After that no comand that uses libc.so.3.0 will work (i.e., I get core dumps at a frantic rate). To restore the system to an operational state I must boot up in single user mode and replace this library with the previous version. I have re-supped and retried this several days in a row (even tried it on a different system) with the same result. Is anybody else seeing this problem? Am I missing something that happened between May 31 and June 3 that I should have done and didn't? I am getting to my wits end here and don't know what to try next. Thanks, -- Bob Willcox bob@luke.pmr.com Austin, TX From owner-freebsd-current Sun Jun 9 07:23:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA05673 for current-outgoing; Sun, 9 Jun 1996 07:23:51 -0700 (PDT) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA05622; Sun, 9 Jun 1996 07:23:45 -0700 (PDT) Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id JAA07124; Sun, 9 Jun 1996 09:22:11 -0500 (CDT) Message-Id: <199606091422.JAA07124@sierra.zyzzyva.com> To: "Jordan K. Hubbard" cc: Terry Lambert , grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: The -stable problem: my view In-reply-to: jkh's message of Fri, 07 Jun 1996 16:40:55 -0700. <17086.834190855@time.cdrom.com> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Jun 1996 09:22:09 -0500 From: Randy Terbush Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Non-commercial break during clash of the titans...] Has anyone in this argument ever looked at Aegis as a project management tool? I've only read through the README, but it reportedly does most (all?) of the things that Terry is suggesting. I realize there is quite a legacy here with CVS, but this might still be worth a look. ARCHIVE SITE The latest version of Aegis is available by anonymous FTP from: Host: ftp.nau.edu (134.114.64.90) Dir: /pub/Aegis File: aegis.2.3.tar.Z # the complete source File: aegis.2.3.patch.Z # patch to take 2.2 to 2.3 File: aegis.2.3.ps.Z # PostScript of the User Guide File: aegis.2.3.faq # Frequently Asked Questions From owner-freebsd-current Sun Jun 9 07:56:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA15161 for current-outgoing; Sun, 9 Jun 1996 07:56:06 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA15122; Sun, 9 Jun 1996 07:56:01 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.6.9) id JAA29931; Sun, 9 Jun 1996 09:54:20 -0500 (CDT) From: Bob Willcox Message-Id: <199606091454.JAA29931@luke.pmr.com> Subject: Re: The -stable problem: my view To: randy@zyzzyva.com (Randy Terbush) Date: Sun, 9 Jun 1996 09:54:20 -0500 (CDT) Cc: jkh@time.cdrom.com, terry@lambert.org, grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199606091422.JAA07124@sierra.zyzzyva.com> from Randy Terbush at "Jun 9, 96 09:22:09 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Randy Terbush wrote: > > ARCHIVE SITE > The latest version of Aegis is available by anonymous FTP > from: > Host: ftp.nau.edu (134.114.64.90) > Dir: /pub/Aegis > File: aegis.2.3.tar.Z # the complete source > File: aegis.2.3.patch.Z # patch to take 2.2 to 2.3 > File: aegis.2.3.ps.Z # PostScript of the User Guide > File: aegis.2.3.faq # Frequently Asked Questions I did not find the version af aegis that you refer to above at ftp.nau.edu. The higest version number there seems to be 2.2. Is there somewhere else to get version 2.3? Thanks, -- Bob Willcox bob@luke.pmr.com Austin, TX From owner-freebsd-current Sun Jun 9 08:38:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28689 for current-outgoing; Sun, 9 Jun 1996 08:38:23 -0700 (PDT) Received: from distortion.eng.umd.edu (distortion.eng.umd.edu [129.2.98.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA28668; Sun, 9 Jun 1996 08:38:16 -0700 (PDT) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.98.208]) by distortion.eng.umd.edu (8.7.5/8.7.3) with ESMTP id LAA13989; Sun, 9 Jun 1996 11:35:27 -0400 (EDT) Received: (from chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) id LAA07186; Sun, 9 Jun 1996 11:35:16 -0400 (EDT) Date: Sun, 9 Jun 1996 11:35:16 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: Bob Willcox cc: Randy Terbush , jkh@time.cdrom.com, terry@lambert.org, grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: The -stable problem: my view In-Reply-To: <199606091454.JAA29931@luke.pmr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 9 Jun 1996, Bob Willcox wrote: > Randy Terbush wrote: > > > > ARCHIVE SITE > > The latest version of Aegis is available by anonymous FTP > > from: > > Host: ftp.nau.edu (134.114.64.90) > > Dir: /pub/Aegis > > File: aegis.2.3.tar.Z # the complete source > > File: aegis.2.3.patch.Z # patch to take 2.2 to 2.3 > > File: aegis.2.3.ps.Z # PostScript of the User Guide > > File: aegis.2.3.faq # Frequently Asked Questions > > I did not find the version af aegis that you refer to above at > ftp.nau.edu. The higest version number there seems to be 2.2. Is > there somewhere else to get version 2.3? I found it, go look at: ftp.agso.gov.au:/pub/Aegis There's something called "cook" there that is supposed to work with it, you might want to get the latest (1.9) version of that while you're looking (I did). > > Thanks, > -- > Bob Willcox > bob@luke.pmr.com > Austin, TX > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Jun 9 08:42:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA29933 for current-outgoing; Sun, 9 Jun 1996 08:42:47 -0700 (PDT) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA29908; Sun, 9 Jun 1996 08:42:41 -0700 (PDT) Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id KAA17621; Sun, 9 Jun 1996 10:41:00 -0500 (CDT) Message-Id: <199606091541.KAA17621@sierra.zyzzyva.com> To: Bob Willcox cc: jkh@time.cdrom.com, terry@lambert.org, grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: The -stable problem: my view In-reply-to: bob's message of Sun, 09 Jun 1996 09:54:20 -0500. <199606091454.JAA29931@luke.pmr.com> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Jun 1996 10:40:58 -0500 From: Randy Terbush Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try ftp.bmr.gov.au:/pub/Aegis Seems his README is a bit out of date. This is not a new project BTW. I seem to recall a 1.0 announcement a couple of years ago. > Randy Terbush wrote: > > > > ARCHIVE SITE > > The latest version of Aegis is available by anonymous FTP > > from: > > Host: ftp.nau.edu (134.114.64.90) > > Dir: /pub/Aegis > > File: aegis.2.3.tar.Z # the complete source > > File: aegis.2.3.patch.Z # patch to take 2.2 to 2.3 > > File: aegis.2.3.ps.Z # PostScript of the User Guide > > File: aegis.2.3.faq # Frequently Asked Questions > > I did not find the version af aegis that you refer to above at > ftp.nau.edu. The higest version number there seems to be 2.2. Is > there somewhere else to get version 2.3? > > Thanks, > -- > Bob Willcox > bob@luke.pmr.com > Austin, TX From owner-freebsd-current Sun Jun 9 10:40:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27791 for current-outgoing; Sun, 9 Jun 1996 10:40:18 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA27769 for ; Sun, 9 Jun 1996 10:40:08 -0700 (PDT) Received: from campa.panke.de (anonymous230.ppp.cs.tu-berlin.de [130.149.17.230]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id TAA09717; Sun, 9 Jun 1996 19:32:18 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id TAA01671; Sun, 9 Jun 1996 19:14:24 +0200 Date: Sun, 9 Jun 1996 19:14:24 +0200 From: Wolfram Schneider Message-Id: <199606091714.TAA01671@campa.panke.de> To: grog@lemis.de (Greg Lehey) Cc: FreeBSD-current@freebsd.org (FreeBSD current users) Subject: The -stable problem: my view In-Reply-To: <199606071015.MAA00708@allegro.lemis.de> References: <199606071015.MAA00708@allegro.lemis.de> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey writes: >My problem is simple: the build procedure is screwed up. It makes the >assumption that I really want to run the version I'm building on the >machine I'm building it on. It confuses the build environment with >the execution environment. It installs components of the new system >in the execution environment before the build is finished. As a >result, if anything goes wrong, you end up with a system in an >indeterminate state. This is a particular nuisance if header files >have changed, and I think this is the biggest problem so far. Run make world in a chroot enviroment. From my memory: # mkdir /a/chroot # cd /a/chroot # cat /a/2.1R/bin/bin.* | tar xfz - # unpack bin distribution # (cd usr; cvs co src) # chroot . /bin/sh # cd usr/src; time make world > mklog 2>&1 Wolfram From owner-freebsd-current Sun Jun 9 10:41:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27962 for current-outgoing; Sun, 9 Jun 1996 10:41:32 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA27929 for ; Sun, 9 Jun 1996 10:41:22 -0700 (PDT) Received: from campa.panke.de (anonymous230.ppp.cs.tu-berlin.de [130.149.17.230]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id TAA09735; Sun, 9 Jun 1996 19:32:38 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id RAA01126; Sun, 9 Jun 1996 17:32:25 +0200 Date: Sun, 9 Jun 1996 17:32:25 +0200 From: Wolfram Schneider Message-Id: <199606091532.RAA01126@campa.panke.de> To: "Eric J. Chet" Cc: current@freebsd.org Subject: VM holding with the latest pmap 960607 In-Reply-To: References: Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eric J. Chet writes: >Great work John, thank you. > >load averages: 8.46, 7.41, 4.29 >17:43:45 >72 processes: 9 running, 63 sleeping >Cpu states: 82.4% user, 0.0% nice, 14.5% system, 3.1% interrupt, 0.0% >idle >Mem: 15M Active, 2876K Inact, 15M Wired, 4068K Cache, 4290K Buf, 140K Free >Swap: 131M Total, 127M Used, 3716K Free, 97% Inuse, 2024K In, 772K Out ^^^^^^^^^^^^^^^^^^ You need more RAM or you should not start so many dr3d processes simultaneous. In normal cases you should never see 'K in' or 'K out'. Permanently paging kill the performance. Wolfram > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 368 ejc 86 0 12M 1460K RUN 1:02 10.57% 10.57% dr3d > 448 ejc 87 0 12M 1284K RUN 0:49 10.53% 10.53% dr3d > 193 ejc 87 0 12M 1280K RUN 1:49 10.53% 10.53% dr3d > 242 ejc 86 0 12M 1692K RUN 1:22 10.49% 10.49% dr3d > 380 ejc -18 0 12M 1464K swread 1:00 10.49% 10.49% dr3d > 335 ejc 86 0 12M 1300K RUN 1:07 10.49% 10.49% dr3d > 207 ejc 86 0 12M 1312K RUN 1:31 10.41% 10.41% dr3d > 425 ejc 86 0 12M 1452K RUN 0:53 10.38% 10.38% dr3d > 263 ejc 2 0 4584K 1920K select 0:17 3.93% 3.93% XF86_Mach64 > 621 ejc -18 0 6304K 888K vnread 0:06 1.26% 1.26% netscape.bin > 2 root -18 0 0K 12K psleep 0:11 0.99% 0.99% pagedaemon > 636 ejc 2 0 3664K 648K select 0:06 0.50% 0.50% xemacs-19.13 From owner-freebsd-current Sun Jun 9 11:32:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04582 for current-outgoing; Sun, 9 Jun 1996 11:32:09 -0700 (PDT) Received: from absolut-zero.winternet.com (root@absolut-zero.winternet.com [198.174.169.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA04563; Sun, 9 Jun 1996 11:32:02 -0700 (PDT) Received: from tundra.winternet.com (nordquis@tundra.winternet.com [198.174.169.11]) by absolut-zero.winternet.com (8.7.5/8.7.5) with ESMTP id NAA10603; Sun, 9 Jun 1996 13:31:50 -0500 (CDT) Received: (from nordquis@localhost) by tundra.winternet.com (8.7.4/8.6.12) id NAA07657; Sun, 9 Jun 1996 13:30:03 -0500 (CDT) From: Brent Nordquist Posted-Date: Sun, 9 Jun 1996 13:30:03 -0500 (CDT) Message-Id: <199606091830.NAA07657@tundra.winternet.com> Subject: Re: Adaptec 2940UW: OK in -SNAP, hangs in -current To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 9 Jun 1996 13:30:02 -0500 (CDT) Cc: aic7xxx@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <199606090324.UAA05678@freefall.freebsd.org> from "Justin T. Gibbs" at Jun 8, 96 08:24:34 pm Reply-to: nordquis@winternet.com (Brent J. Nordquist) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk | Can you tell me the revisions of the files from -current you | are using? There were some problems witha botched patch in | -current from a day or two ago, and I fixed it just last night. | I'm guessing you didn't get the latest version of the driver. They were included toward the bottom of my message; I'll repeat them here. "files.good" came from -SNAP; "files.bad" came from -current. =====Difference between -SNAP and -current driver files=================== *** files.good Sat Jun 8 21:30:29 1996 --- files.bad Sat Jun 8 21:32:54 1996 *************** *** 1,8 **** ! dev/aic7xxx/aic7xxx.seq: aic7xxx.seq,v 1.33 1996/04/20 21:20:29 gibbs ! dev/aic7xxx/aic7xxx_reg.h: aic7xxx_reg.h,v 1.8 1996/04/20 21:20:31 gibbs ! i386/eisa/aic7770.c: aic7770.c,v 1.27 1996/04/20 21:21:47 gibbs ! i386/scsi/93cx6.c: 93cx6.c,v 1.4 1995/11/20 12:14:02 phk ! i386/scsi/93cx6.h: 93cx6.h,v 1.2 1995/09/05 23:52:00 gibbs ! i386/scsi/aic7xxx.c: aic7xxx.c,v 1.65 1996/04/28 19:21:19 gibbs ! i386/scsi/aic7xxx.h: aic7xxx.h,v 1.26 1996/04/28 19:21:20 gibbs ! pci/aic7870.c: aic7870.c,v 1.29 1996/04/20 21:31:27 gibbs --- 1,8 ---- ! dev/aic7xxx/aic7xxx.seq: aic7xxx.seq,v 1.40 1996/05/31 06:30:15 gibbs ! dev/aic7xxx/aic7xxx_reg.h: aic7xxx_reg.h,v 1.11 1996/05/21 18:32:23 gibbs ! i386/eisa/aic7770.c: aic7770.c,v 1.29 1996/05/30 07:18:52 gibbs ! i386/scsi/93cx6.c: 93cx6.c,v 1.5 1996/05/30 07:19:54 gibbs ! i386/scsi/93cx6.h: 93cx6.h,v 1.3 1996/05/30 07:19:55 gibbs ! i386/scsi/aic7xxx.c: aic7xxx.c,v 1.72 1996/05/31 06:32:09 gibbs ! i386/scsi/aic7xxx.h: aic7xxx.h,v 1.28 1996/05/30 07:19:59 gibbs ! pci/aic7870.c: aic7870.c,v 1.36 1996/05/30 07:20:17 gibbs ========================================================================== -- Brent J. Nordquist Which is worse: ignorance or apathy? nordquis@winternet.com ...Who knows? +1 612 827-2747 ...Who cares? From owner-freebsd-current Sun Jun 9 12:16:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09407 for current-outgoing; Sun, 9 Jun 1996 12:16:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA09397 for ; Sun, 9 Jun 1996 12:16:34 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01285; Sun, 9 Jun 1996 12:16:10 -0700 From: Terry Lambert Message-Id: <199606091916.MAA01285@phaeton.artisoft.com> Subject: Re: does freebsd support SMP? To: nathan@netrail.net (Nathan Stratton) Date: Sun, 9 Jun 1996 12:16:10 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Nathan Stratton" at Jun 9, 96 01:48:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > DOes freebsd supoort SMP? Yes. There is a working SMP /usr/src/sys code tree that can be SUP'ed or CTM'ed. You do a normal CVS checkout, then you add: options SMP # enable SMP options NCPU=2 # or whatever max you want To your normal -current config file, config, makedepend, make, and install the SMP kernel. Then rebbot. You are running SMP. You should be running -current already, then join the SMP mailing list before doing this. You can join the list with the following shell command from the system where you want to get the mail: echo "subscribe freebsd-smp" | mail majordomo@freebsd.org (just like any other FreeBSD mailing list -- maybe we need shell scripts to ship with the system: "subscribe" and "unsubscribe". 8-)). You can ask about the SUP and CTM marker addresses on the SMP list, once you are on it. An alternate method, if you have a freefall account, is to FTP the CVS tree from /f/smp. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jun 9 12:24:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10307 for current-outgoing; Sun, 9 Jun 1996 12:24:01 -0700 (PDT) Received: from critter.tfs.com ([140.145.16.108]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10287; Sun, 9 Jun 1996 12:23:58 -0700 (PDT) Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id MAA00970; Sun, 9 Jun 1996 12:23:28 -0700 (PDT) To: Terry Lambert cc: nathan@netrail.net (Nathan Stratton), freebsd-current@FreeBSD.ORG Subject: Re: does freebsd support SMP? In-reply-to: Your message of "Sun, 09 Jun 1996 12:16:10 PDT." <199606091916.MAA01285@phaeton.artisoft.com> Date: Sun, 09 Jun 1996 12:23:27 -0700 Message-ID: <968.834348207@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> DOes freebsd supoort SMP? > >Yes. There is a working SMP /usr/src/sys code tree that can be SUP'ed >or CTM'ed. You do a normal CVS checkout, then you add: > >options SMP # enable SMP >options NCPU=2 # or whatever max you want > >To your normal -current config file, config, makedepend, make, and >install the SMP kernel. Then rebbot. You are running SMP. Well, you clearly havn't tried it Terry :-) Boot single user and then: sysctl -w kern.smp_active=2 to start the second CPU... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sun Jun 9 13:02:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15050 for current-outgoing; Sun, 9 Jun 1996 13:02:29 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA14952; Sun, 9 Jun 1996 13:02:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA01419; Sun, 9 Jun 1996 13:01:56 -0700 From: Terry Lambert Message-Id: <199606092001.NAA01419@phaeton.artisoft.com> Subject: Re: does freebsd support SMP? To: phk@FreeBSD.ORG (Poul-Henning Kamp) Date: Sun, 9 Jun 1996 13:01:55 -0700 (MST) Cc: terry@lambert.org, nathan@netrail.net, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG In-Reply-To: <968.834348207@critter.tfs.com> from "Poul-Henning Kamp" at Jun 9, 96 12:23:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> DOes freebsd supoort SMP? > > > >Yes. There is a working SMP /usr/src/sys code tree that can be SUP'ed > >or CTM'ed. You do a normal CVS checkout, then you add: > > > >options SMP # enable SMP > >options NCPU=2 # or whatever max you want > > > >To your normal -current config file, config, makedepend, make, and > >install the SMP kernel. Then rebbot. You are running SMP. > > Well, you clearly havn't tried it Terry :-) > > Boot single user and then: > sysctl -w kern.smp_active=2 > to start the second CPU... That didn't used to be in there... clearly, I haven't tried it recently. 8-). Thanks for telling me, though, since I just pulled down the sources yesterday, and the only reason I'm in today is to play with it. I would have figured it out eventually. 4 hours or so. 8-) 8-). It seems that smp_active wants to be cpu.active, and wants to default to 1 (not zero). Actually, looking at the code, the values are only allowed to be 0 or 2 -- and it looks like 2 will actually start 'n' (the loop in mp_begin in locore.s). The locking code (mplock.s) only checks for non-zero. The code in swtch.s -- is it ever hit in the smp_active zero case? It seems to be an error to have the old idle loop present at all... am I missing something in the UP case, where the kernel is still compiled with SMP set? Also, in the idle spin loop, re: processor power consumption and heating: any chance of integrating a Linux-style "halt instruction" test and using it in the case that it works? Anyway, the reason I went looking was for a kernel variable like cpu.count for number of available cpu's so I could put it in my rc file instead of booting single-user: CPUCOUNT=`sysctl -n kern.cpu.count` if test "$CPUCOUNT" != "1" then echo -n "Starting auxillary processors..." sysctl -w kern.cpu.active=$CPUCOUNT echo "$(CPUCOUNT) PROCESSORS ACTIVE" fi This code could go into the main line rc file with no adverse affect, assuming the cpu.count wasn't conditional on being compiled with the SMP flag (the active could be conditional, since the count will never be non-1 in the UP/non-SMP options case) Who is actively hacking where in the assembly code? This seems like an easy fix that wouldn't drag me down into dealing with page tables. ;-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jun 9 13:43:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19501 for current-outgoing; Sun, 9 Jun 1996 13:43:40 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-165.ut.nl.ibm.net [139.92.42.165]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA19467; Sun, 9 Jun 1996 13:43:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with SMTP id MAA00723; Sun, 9 Jun 1996 12:54:40 +0200 (MET DST) Message-Id: <199606091054.MAA00723@vector.jhs.no_domain> X-Authentication-Warning: vector.jhs.no_domain: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" Cc: nate@sri.MT.net (Nate Williams), hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org, Terry Lambert Subject: Re: The -stable problem: my view From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Web: http://www.freebsd.org/~jhs/ Mailer: EXMH version 1.6.5 95 12 11, PGP available In-reply-to: Your message of "Fri, 07 Jun 1996 17:59:42 PDT." <17510.834195582@time.cdrom.com> Date: Sun, 09 Jun 1996 12:54:39 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Reference: > From: "Jordan K. Hubbard" > > The question here seems to be "how can we give the users a tree which > always builds", right? Well, that's certainly not a new question. > Even crazed expatriate brits like Julian Stacey have been calling for > that sort of scheme for years! :-) You called ? :-) Re. CVS: I suggest, for future policy, (& not WRT past history :-) ... Anyone who wantonly breaks Current (& forces everyone to need make -i) for more than the duration of a single short commit session, should have his commits backed out, & CVS privelege suspended for 7 days, during which the person is free to meditate on the disruption caused, & to prepare new better tested diffs. After initial rigorous enforcement, only occasional later enforcement would be required. Only exception: After _prior_ posted permission from CVS master, where breaking the tree is certified as really unavoidable. Re. Stable: I suggest boring work is best left to those with a paid incentive. `Stable' is a quasi-professional service: ( A labour intensive mix of some `current' technology plus testing ), & is a burden on unpaid volunteers. So leave boring work to those with a financial incentive, who could be: - External support services that may set up, offering for FreeBSD, services similar to that which Cygnus offers for FSF. - Custom consultantcy & support people or firms. - A FreeBSD Inc. funded `stable' maintenance group if Jordan & co. drum up sufficient funds from commercial users. - If Walnut Creek Inc determine `Stable' to be of financial benefit to WC inc, then those people funded by WC. Serious@freebsd.org is (or was) available, for companies prepared to pay serious commercial amounts of money (upwards of hundreds of dollars I suggest) for commercial support. Such paid work could include Stable maintenance). Personal Disclosure: I am a Unix developer/supporter, with personal & business interests in Releases & Current, but no `Stable' paying customers or hosts. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sun Jun 9 14:35:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA24339 for current-outgoing; Sun, 9 Jun 1996 14:35:37 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA24334; Sun, 9 Jun 1996 14:35:26 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.6.9) id QAA03062; Sun, 9 Jun 1996 16:33:11 -0500 (CDT) From: Bob Willcox Message-Id: <199606092133.QAA03062@luke.pmr.com> Subject: Re: The -stable problem: my view To: randy@zyzzyva.com (Randy Terbush) Date: Sun, 9 Jun 1996 16:33:11 -0500 (CDT) Cc: jkh@time.cdrom.com, terry@lambert.org, grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199606091541.KAA17621@sierra.zyzzyva.com> from Randy Terbush at "Jun 9, 96 10:40:58 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Randy Terbush wrote: > Try ftp.bmr.gov.au:/pub/Aegis > > Seems his README is a bit out of date. Got it! Thanks to all who responded! -- Bob Willcox bob@luke.pmr.com Austin, TX From owner-freebsd-current Sun Jun 9 16:10:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA06419 for current-outgoing; Sun, 9 Jun 1996 16:10:09 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA06413 for ; Sun, 9 Jun 1996 16:10:07 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA03238 for current@FreeBSD.org; Sun, 9 Jun 1996 16:09:48 -0700 From: Terry Lambert Message-Id: <199606092309.QAA03238@phaeton.artisoft.com> Subject: Minor nit in build process plus fix To: current@FreeBSD.org Date: Sun, 9 Jun 1996 16:09:47 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi; My /usr/src is a directory containing a set of symbolic links to the real source locations for various components. This lets me mix-and-match components from multiple source trees pretty much at will using various /usr/src directory configurations. Recently, I had to rebuild ps. The /usr/include directory on my machine is the one from -release. The ps build builds a -I/sys include line, but since there is no /sys/machine, it finds the correct /usr/include/sys directory, but gets the old /usr/include/machine directory. There is a fix: ln -s i386/include /sys/machine I think this symlink should be in the default /usr/src/sys source tree. There are probably other dependent includes that are handled the same (wrong) way (I haven't hit any, but I'm sure the "net" stuff is in the same boat, etc.). The reason this is an issue is that the ps command includes sys/proc.h which includes files from the machine include directory, and while the sys directory is correctly redirected to the current /sys's includes, the machine directory is not. I would also like to see relative path dependencies disappear. The /bin/csh relative path dependency on usr.bin/printf is especially annoying, given the relative prioritization of the bin and usr/bin directories in a live system. In either case, the relative path dependencies want to disappear so that symlinks can be used; putting printf.c in the "right" place for the dependency (or moving csh to the "right" place) is only a kludge fix. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jun 9 16:19:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07793 for current-outgoing; Sun, 9 Jun 1996 16:19:10 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA07779; Sun, 9 Jun 1996 16:19:07 -0700 (PDT) Message-Id: <199606092319.QAA07779@freefall.freebsd.org> To: nordquis@winternet.com (Brent J. Nordquist) cc: freebsd-current@FreeBSD.org Subject: Re: Adaptec 2940UW: OK in -SNAP, hangs in -current In-reply-to: Your message of "Sun, 09 Jun 1996 13:30:02 CDT." <199606091830.NAA07657@tundra.winternet.com> Date: Sun, 09 Jun 1996 16:19:07 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Yup. You don't have the latest. Re-SUP and try again. >They were included toward the bottom of my message; I'll repeat them >here. "files.good" came from -SNAP; "files.bad" came from -current. > >=====Difference between -SNAP and -current driver files=================== > >*** files.good Sat Jun 8 21:30:29 1996 >--- files.bad Sat Jun 8 21:32:54 1996 >*************** >*** 1,8 **** >! dev/aic7xxx/aic7xxx.seq: aic7xxx.seq,v 1.33 1996/04/20 21:20:29 gibbs >! dev/aic7xxx/aic7xxx_reg.h: aic7xxx_reg.h,v 1.8 1996/04/20 21:20:31 gibbs >! i386/eisa/aic7770.c: aic7770.c,v 1.27 1996/04/20 21:21:47 gibbs >! i386/scsi/93cx6.c: 93cx6.c,v 1.4 1995/11/20 12:14:02 phk >! i386/scsi/93cx6.h: 93cx6.h,v 1.2 1995/09/05 23:52:00 gibbs >! i386/scsi/aic7xxx.c: aic7xxx.c,v 1.65 1996/04/28 19:21:19 gibbs >! i386/scsi/aic7xxx.h: aic7xxx.h,v 1.26 1996/04/28 19:21:20 gibbs >! pci/aic7870.c: aic7870.c,v 1.29 1996/04/20 21:31:27 gibbs >--- 1,8 ---- >! dev/aic7xxx/aic7xxx.seq: aic7xxx.seq,v 1.40 1996/05/31 06:30:15 gibbs >! dev/aic7xxx/aic7xxx_reg.h: aic7xxx_reg.h,v 1.11 1996/05/21 18:32:23 gibbs >! i386/eisa/aic7770.c: aic7770.c,v 1.29 1996/05/30 07:18:52 gibbs >! i386/scsi/93cx6.c: 93cx6.c,v 1.5 1996/05/30 07:19:54 gibbs >! i386/scsi/93cx6.h: 93cx6.h,v 1.3 1996/05/30 07:19:55 gibbs >! i386/scsi/aic7xxx.c: aic7xxx.c,v 1.72 1996/05/31 06:32:09 gibbs >! i386/scsi/aic7xxx.h: aic7xxx.h,v 1.28 1996/05/30 07:19:59 gibbs >! pci/aic7870.c: aic7870.c,v 1.36 1996/05/30 07:20:17 gibbs > >========================================================================== > >-- >Brent J. Nordquist Which is worse: ignorance or apathy? >nordquis@winternet.com ...Who knows? >+1 612 827-2747 ...Who cares? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Jun 9 16:47:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA14224 for current-outgoing; Sun, 9 Jun 1996 16:47:04 -0700 (PDT) Received: from gargoyle.bazzle.com ([206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA14205 for ; Sun, 9 Jun 1996 16:46:57 -0700 (PDT) Received: from localhost (ejc@localhost) by gargoyle.bazzle.com (8.7.5/8.6.12) with SMTP id TAA02633; Sun, 9 Jun 1996 19:48:16 -0400 (EDT) Date: Sun, 9 Jun 1996 19:48:16 -0400 (EDT) From: "Eric J. Chet" To: Wolfram Schneider cc: current@freebsd.org Subject: Re: VM holding with the latest pmap 960607 In-Reply-To: <199606091532.RAA01126@campa.panke.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 9 Jun 1996, Wolfram Schneider wrote: > Eric J. Chet writes: > >Great work John, thank you. > > > >load averages: 8.46, 7.41, 4.29 > >Swap: 131M Total, 127M Used, 3716K Free, 97% Inuse, 2024K In, 772K Out > ^^^^^^^^^^^^^^^^^^ > You need more RAM or you should not start so many dr3d processes > simultaneous. In normal cases you should never see 'K in' or > 'K out'. Permanently paging kill the performance. Wolfram I was just testing the latest VM fixes by John. As you can see it can take a beating. Peace, Eric J. Chet - ejc@bazzle.com - Powered by FreeBSD Lucent Technologies, Bell Labs Innovations - ejc@nasvr1.cb.att.com Columbus, Ohio 43213 RM 1E222 From owner-freebsd-current Sun Jun 9 17:15:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17604 for current-outgoing; Sun, 9 Jun 1996 17:15:09 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA17592 for ; Sun, 9 Jun 1996 17:15:05 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id RAA00899; Sun, 9 Jun 1996 17:14:51 -0700 (PDT) Date: Sun, 9 Jun 1996 17:14:51 -0700 (PDT) Message-Id: <199606100014.RAA00899@silvia.HIP.Berkeley.EDU> To: wosch@cs.tu-berlin.de CC: ejc@gargoyle.bazzle.com, current@freebsd.org In-reply-to: <199606091532.RAA01126@campa.panke.de> (message from Wolfram Schneider on Sun, 9 Jun 1996 17:32:25 +0200) Subject: Re: VM holding with the latest pmap 960607 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * You need more RAM or you should not start so many dr3d processes * simultaneous. In normal cases you should never see 'K in' or * 'K out'. Permanently paging kill the performance. I thought that was the point of his "test" (stress the VM system). ;) Satoshi From owner-freebsd-current Sun Jun 9 18:36:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01458 for current-outgoing; Sun, 9 Jun 1996 18:36:59 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA01373 for ; Sun, 9 Jun 1996 18:36:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA23798; Mon, 10 Jun 1996 11:34:59 +1000 Date: Mon, 10 Jun 1996 11:34:59 +1000 From: Bruce Evans Message-Id: <199606100134.LAA23798@godzilla.zeta.org.au> To: current@FreeBSD.org, terry@lambert.org Subject: Re: Minor nit in build process plus fix Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The ps build builds a -I/sys include line, but since there is no >/sys/machine, it finds the correct /usr/include/sys directory, >but gets the old /usr/include/machine directory. >There is a fix: > ln -s i386/include /sys/machine Better fix: remove `CFLAGS+=-I/sys' from ps/Makefile. Then whatever method you use to get the correct /usr/include/sys/* will work. The easiest method is for /usr/include/sys to be a symlink to /sys/sys. This is the default except in releases. /sys is wrong too (because only root can change it, and it can only point to one place at a time), but it's simpler than a maze of symlinks and -I options. >The reason this is an issue is that the ps command includes sys/proc.h >which includes files from the machine include directory, and while >the sys directory is correctly redirected to the current /sys's >includes, the machine directory is not. Almost all headers in /usr/include include at least from the machine directory, so mixing versions may break things. >I would also like to see relative path dependencies disappear. The >/bin/csh relative path dependency on usr.bin/printf is especially >annoying, given the relative prioritization of the bin and usr/bin >directories in a live system. Relative paths are used to avoid the problems with absolute paths :-]. usr.bin/printf is slightly less likely to be in the usual absolute place than in the usual relative place. Bruce From owner-freebsd-current Sun Jun 9 19:53:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA27306 for current-outgoing; Sun, 9 Jun 1996 19:53:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA27278 for ; Sun, 9 Jun 1996 19:52:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA02819; Sun, 9 Jun 1996 19:52:47 -0700 From: Terry Lambert Message-Id: <199606100252.TAA02819@phaeton.artisoft.com> Subject: Re: Minor nit in build process plus fix To: bde@zeta.org.au (Bruce Evans) Date: Sun, 9 Jun 1996 19:52:47 -0700 (MST) Cc: current@FreeBSD.org, terry@lambert.org In-Reply-To: <199606100134.LAA23798@godzilla.zeta.org.au> from "Bruce Evans" at Jun 10, 96 11:34:59 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >The ps build builds a -I/sys include line, but since there is no > >/sys/machine, it finds the correct /usr/include/sys directory, > >but gets the old /usr/include/machine directory. > > >There is a fix: > > > ln -s i386/include /sys/machine > > Better fix: remove `CFLAGS+=-I/sys' from ps/Makefile. Then whatever > method you use to get the correct /usr/include/sys/* will work. The > easiest method is for /usr/include/sys to be a symlink to /sys/sys. > This is the default except in releases. /sys is wrong too (because > only root can change it, and it can only point to one place at a time), > but it's simpler than a maze of symlinks and -I options. I want to build some portions of the tree with new code, and some with release code. The /usr/include/sys *CAN NOT* point at the kernel /sys directory... basically for anything other than the contents of /bin or the kernel build itself. I guess the real problem there is that installed headers are used at all in any build. Really, I want to be able to build pieces that are dependent on the kernel includes seperately from those which aren't. I suppose that ideally, ps would reference /proc instead of /dev/mem, then I could twiddle the size of the proc struct until I was blue in the face without breaking it. > >The reason this is an issue is that the ps command includes sys/proc.h > >which includes files from the machine include directory, and while > >the sys directory is correctly redirected to the current /sys's > >includes, the machine directory is not. > > Almost all headers in /usr/include include at least > from the machine directory, so mixing versions may break things. I want to mix versions, but not break things. 8-). More accurately, I want to modularize so I can decide to do a minimal build, leaving everything else to run in binary compatability for previous releases. It's recognized that "ps" and "w" are kernel dependent, whereas "ls" and "more" are not. I'd rather not build "more" if I'm building to hack kernel code. > >I would also like to see relative path dependencies disappear. The > >/bin/csh relative path dependency on usr.bin/printf is especially > >annoying, given the relative prioritization of the bin and usr/bin > >directories in a live system. > > Relative paths are used to avoid the problems with absolute paths :-]. > usr.bin/printf is slightly less likely to be in the usual absolute > place than in the usual relative place. I was thinking in terms of the top level make setting an environment variable. The problem is really "..", not "paths relative to the build root". The other issue here is the ability to build multiple shared library versions (which the library include file for make tends to damage beyond recognition). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jun 9 20:19:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08557 for current-outgoing; Sun, 9 Jun 1996 20:19:19 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08519; Sun, 9 Jun 1996 20:19:09 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id MAA25619; Mon, 10 Jun 1996 12:19:04 +0900 (JST) Date: Mon, 10 Jun 1996 12:19:04 +0900 (JST) From: Michael Hancock To: "Julian H. Stacey" , jkh@freebsd.org cc: freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org Subject: Re: The -stable problem: my view In-Reply-To: <199606091054.MAA00723@vector.jhs.no_domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 9 Jun 1996, Julian H. Stacey wrote: Regarding stable... > I suggest boring work is best left to those with a paid incentive. > `Stable' is a quasi-professional service: > ( A labour intensive mix of some `current' technology plus testing ), > & is a burden on unpaid volunteers. > So leave boring work to those with a financial incentive, who could be: > - External support services that may set up, offering for > FreeBSD, services similar to that which Cygnus offers for FSF. > - Custom consultantcy & support people or firms. > - A FreeBSD Inc. funded `stable' maintenance group if Jordan & co. > drum up sufficient funds from commercial users. > - If Walnut Creek Inc determine `Stable' to be of financial benefit to > WC inc, then those people funded by WC. Yes, definitely make stable an independently funded service. I think a stable sup subscription sold by WC would work. -mh From owner-freebsd-current Sun Jun 9 21:13:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01272 for current-outgoing; Sun, 9 Jun 1996 21:13:01 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA01248 for ; Sun, 9 Jun 1996 21:12:58 -0700 (PDT) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <22982-0@bunyip.cc.uq.oz.au>; Mon, 10 Jun 1996 14:12:46 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id OAA29028 for ; Mon, 10 Jun 1996 14:13:23 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id EAA06461 for ; Mon, 10 Jun 1996 04:14:15 GMT Message-Id: <199606100414.EAA06461@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: Compile errors in latest version of pmap_rmt.c X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jun 1996 14:14:14 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk # make cc -O2 -m486 -pipe -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MIST AKE -I/usr/src/lib/libc/locale -DYP -c /usr/src/lib/libc/rpc/pmap_rmt.c -o pmap_ rmt.o /usr/src/lib/libc/rpc/pmap_rmt.c:60: parse error before `+' *** Error code 1 Stop. Grrr. Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Sun Jun 9 22:42:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA07648 for current-outgoing; Sun, 9 Jun 1996 22:42:04 -0700 (PDT) Received: from spinner.DIALix.COM (spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA07420; Sun, 9 Jun 1996 22:41:36 -0700 (PDT) Received: from spinner.DIALix.COM (localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.7.5/8.7.3) with ESMTP id NAA02800; Mon, 10 Jun 1996 13:40:00 +0800 (WST) Message-Id: <199606100540.NAA02800@spinner.DIALix.COM> To: Terry Lambert cc: phk@FreeBSD.ORG (Poul-Henning Kamp), nathan@netrail.net, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: does freebsd support SMP? In-reply-to: Your message of "Sun, 09 Jun 1996 13:01:55 MST." <199606092001.NAA01419@phaeton.artisoft.com> Date: Mon, 10 Jun 1996 13:39:59 +0800 From: Peter Wemm Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >> DOes freebsd supoort SMP? >> > >> >Yes. There is a working SMP /usr/src/sys code tree that can be SUP'ed >> >or CTM'ed. You do a normal CVS checkout, then you add: >> > >> >options SMP # enable SMP >> >options NCPU=2 # or whatever max you want >> > >> >To your normal -current config file, config, makedepend, make, and >> >install the SMP kernel. Then rebbot. You are running SMP. >> >> Well, you clearly havn't tried it Terry :-) >> >> Boot single user and then: >> sysctl -w kern.smp_active=2 >> to start the second CPU... > > >That didn't used to be in there... clearly, I haven't tried it >recently. 8-). > >Thanks for telling me, though, since I just pulled down the sources >yesterday, and the only reason I'm in today is to play with it. I >would have figured it out eventually. 4 hours or so. 8-) 8-). > >It seems that smp_active wants to be cpu.active, and wants to >default to 1 (not zero). Actually, no, it's just a hack so that we can progressively unlock the cpu's and trace various stages of booting them. >The locking code (mplock.s) only checks for non-zero. Yes.. smp_active=1 means you can get the second cpu up in protected mode and running virtual, but not scheduling yet. >The code in swtch.s -- is it ever hit in the smp_active zero >case? It seems to be an error to have the old idle loop >present at all... am I missing something in the UP case, where >the kernel is still compiled with SMP set? > >Also, in the idle spin loop, re: processor power consumption and >heating: any chance of integrating a Linux-style "halt instruction" >test and using it in the case that it works? Yes, this is a 'work-in-progress'. The only reason it's spinning at all at the moment is because a) it works for the moment, and b) we've been busy on other things. A lack of documentation doesn't help, we have just about solved that problem, all we need is detail on the IO-APIC... >Who is actively hacking where in the assembly code? This seems like >an easy fix that wouldn't drag me down into dealing with page tables. >;-). I've got a whole mess of uncommitted stuff yet that I've not quite finished and debugged yet. I've mentioned some of this to phk so far.. - generic apic IPI message sender, eg: to send (say) an int 0x20 to a processor to snap it out of it's hlt loop and schedule a process. This also makes the boot more robust as there are are timeouts now - almost all special case code removed from locore.s and pmap.c. Instead of booting the second processor on _IdlePTD, and using the idle process's stacks and ptd's, a PTD is cloned from _idlePTD, and a stack and pcb allocated and initialised. The clone PTD has the temporary 4MB V==P mapping at 0 so that the kernel can turn on paging without getting killed by the new pipeline flushes on the P6. Since it has it's own pcb, it now has it's own mplock nesting count. This means that we can ressurect a real idle loop with a hlt. - sysctl string with handler function, rather than just an int variable. This means that simple commands can be written. (eg: sysctl -w cpu.smp=bootall) - Simple parsing of the MP config block, although I dont use it yet. - Support for 'N' cpus. Since all per-cpu state is allocated after boot now, booting the processors is somewhat simpler... int cpu_alive[NCPU]; /* cpu touches this when it wakes up, then waits */ ..... my_id = cpunumber(); for (i = 0; i < NCPU; i++) { if (i == my_id) continue; smp_cpu_startup(i); /* sleep a short while */ if (cpu_alive[i]) { smp_alloc(i); /* allocates and sets up ptd, stack, etc */ smp_cpu_unlock(i); /* releases it from lock, it sets up it's vm etc */ } else { /* in case the cpu is alive but didn't survive boot, halt it */ smp_cpu_halt(i); /* does an init ipi to make the cpu execute a cli;hlt*/ } } This is pretty trivial, and does not cope with apic id's outside 0..NCPU. I'd like to parse the MP block to find all the cpus, and reprogram the apic id's of the ones outside the range to make them sequential if needed. This means booting all cpus, keeping them locked, calculating a new mapping, leaving the boot cpu alone, letting all cpus reset their apic_id at once, then letting the boot cpu figure out the mess. - (on a sidetrack) I'm trying to eliminate the user area to allow vmspace sharing. This is somewhat complicated by each cpu needing a tss pointer in the gdt, so it may force dynamic allocation of the gdt. (or, reserve NCPU slots and initialise them manually rather than statically. For now, I've just left a 31 entry "hole" since the #if's were a nightmare to reserve the correct amount in the static structure). Once this is done, we can have real threaded programs executing multiple threads on both cpus at once. - Somebody mentioned NCPU vs. MAXCPU.. I use NCPU as "the maximum number of cpus that we can support", it's little more than a size of a couple of int arrays. It could quite reasonably be hardwired to a default of 32. - I'm sure I've forgotten something.. :-) Cheers, -Peter From owner-freebsd-current Mon Jun 10 00:37:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25132 for current-outgoing; Mon, 10 Jun 1996 00:37:15 -0700 (PDT) Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA25113 for ; Mon, 10 Jun 1996 00:37:12 -0700 (PDT) Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.7.1/8.6.4) with ESMTP id JAA22228 for ; Mon, 10 Jun 1996 09:37:06 +0200 (MET DST) Message-Id: <199606100737.JAA22228@lirmm.lirmm.fr> To: current@freebsd.org Subject: typo in lorder.1 Date: Mon, 10 Jun 1996 09:37:02 +0200 From: "Philippe Charnier" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Here is a typo in lorder.1 Index: lorder.1 =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/lorder/lorder.1,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 lorder.1 --- lorder.1 1994/05/27 12:32:05 1.1.1.1 +++ lorder.1 1996/06/08 10:06:54 @@ -58,7 +58,7 @@ pass of the loader. .Sh EXAMPLES .Bd -literal -offset indent -ar cr library.a `lorder ${OBJS} tsort` +ar cr library.a `lorder ${OBJS} | tsort` .Ed .Sh SEE ALSO .Xr ar 1 , -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Mon Jun 10 00:38:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25619 for current-outgoing; Mon, 10 Jun 1996 00:38:26 -0700 (PDT) Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA25596 for ; Mon, 10 Jun 1996 00:38:24 -0700 (PDT) Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.7.1/8.6.4) with ESMTP id JAA22246 for ; Mon, 10 Jun 1996 09:38:22 +0200 (MET DST) Message-Id: <199606100738.JAA22246@lirmm.lirmm.fr> To: current@freebsd.org Subject: missing include in sysctl.3 Date: Mon, 10 Jun 1996 09:38:18 +0200 From: "Philippe Charnier" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, The following program fails #include void main() { } The error is: /usr/include/sys/sysctl.h:385: parse error before `u_int' Functions that need sysctl.h to be included already ask to include sys/param.h as well (kvm_getprocs.3, kvm_getenvv.3, kvm_getargv.3). But sysctl.3 don't. Index: sysctl.3 =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/lib/libc/gen/sysctl.3,v retrieving revision 1.6 diff -u -r1.6 sysctl.3 --- sysctl.3 1996/03/11 03:08:51 1.6 +++ sysctl.3 1996/03/12 19:47:28 @@ -38,6 +38,7 @@ .Nm sysctl .Nd get or set system information .Sh SYNOPSIS +.Fd #include .Fd #include .Ft int .Fn sysctl "int *name" "u_int namelen" "void *oldp" "size_t *oldlenp" "void *newp" "size_t newlen" -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Mon Jun 10 00:40:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA26748 for current-outgoing; Mon, 10 Jun 1996 00:40:52 -0700 (PDT) Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA26724 for ; Mon, 10 Jun 1996 00:40:49 -0700 (PDT) Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.7.1/8.6.4) with ESMTP id JAA22288 for ; Mon, 10 Jun 1996 09:40:48 +0200 (MET DST) Message-Id: <199606100740.JAA22288@lirmm.lirmm.fr> To: current@freebsd.org Subject: enable debugging in tsort Date: Mon, 10 Jun 1996 09:40:44 +0200 From: "Philippe Charnier" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, The -d option was not in man page nor in usage string. Index: tsort.1 =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/tsort/tsort.1,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 tsort.1 --- tsort.1 1994/05/27 12:33:13 1.1.1.1 +++ tsort.1 1996/06/08 09:50:56 @@ -42,6 +42,7 @@ .Nd topological sort of a directed graph .Sh SYNOPSIS .Nm tsort +.Op Fl d .Op Fl l .Op Ar file .Sh DESCRIPTION @@ -66,6 +67,8 @@ .Pp The options are as follows: .Bl -tag -width Ds +.It Fl d +Turn on debugging. .It Fl l Search for and display the longest cycle. Can take a very long time. Index: tsort.c =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/tsort/tsort.c,v retrieving revision 1.2 diff -u -r1.2 tsort.c --- tsort.c 1995/05/30 06:35:36 1.2 +++ tsort.c 1996/06/08 09:55:37 @@ -32,6 +32,8 @@ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. + * + * $Id$ */ #ifndef lint @@ -61,7 +63,7 @@ * standard output in sorted order, one per line. * * usage: - * tsort [-l] [inputfile] + * tsort [-d][-l] [inputfile] * If no input file is specified, standard input is read. * * Should be compatable with AT&T tsort HOWEVER the output is not identical @@ -424,6 +426,6 @@ void usage() { - (void)fprintf(stderr, "usage: tsort [-l] [file]\n"); + (void)fprintf(stderr, "usage: tsort [-d][-l] [file]\n"); exit(1); } -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Mon Jun 10 01:46:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA22655 for current-outgoing; Mon, 10 Jun 1996 01:46:13 -0700 (PDT) Received: from d210.ndiasb.kiev.ua (d210.ndiasb.kiev.ua [194.44.4.27]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA22207; Mon, 10 Jun 1996 01:45:12 -0700 (PDT) Received: from uu.elvisti.kiev.ua (acc0.elvisti.kiev.ua [193.125.28.132]) by d210.ndiasb.kiev.ua (8.6.12/8.6.12) with ESMTP id LAA00390; Mon, 10 Jun 1996 11:46:02 +0300 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id LAA19216; Mon, 10 Jun 1996 11:45:29 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id LAA17470; Mon, 10 Jun 1996 11:45:29 +0300 From: "Andrew V. Stesin" Message-Id: <199606100845.LAA17470@office.elvisti.kiev.ua> Subject: Re: The -stable problem: my view To: narvi@haldjas.folklore.ee (Narvi) Date: Mon, 10 Jun 1996 11:45:24 +0300 (EET DST) Cc: jkh@time.cdrom.com, karl@mcs.com, grog@lemis.de, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: from "Narvi" at Jun 8, 96 12:53:38 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, # 2) Couldn't maintaining of stable look like: # a) The core team suggest that it would be nice if somebody would # bring feature x over to -stable. if the feature mentioned is "new" -- than -stable can't be officially called "stable" any more. If it isn't -- why waste time of those great guys who are making FreeBSD? Donate your own time to do testing if you want to get more features, isn't it Ok? -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-current Mon Jun 10 06:02:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA02891 for current-outgoing; Mon, 10 Jun 1996 06:02:45 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA02790 for ; Mon, 10 Jun 1996 06:02:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id WAA13623; Mon, 10 Jun 1996 22:59:50 +1000 Date: Mon, 10 Jun 1996 22:59:50 +1000 From: Bruce Evans Message-Id: <199606101259.WAA13623@godzilla.zeta.org.au> To: charnier@lirmm.fr, current@freebsd.org Subject: Re: missing include in sysctl.3 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Functions that need sysctl.h to be included already ask to >include sys/param.h as well (kvm_getprocs.3, kvm_getenvv.3, kvm_getargv.3). only needs . Bruce From owner-freebsd-current Mon Jun 10 07:18:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA17655 for current-outgoing; Mon, 10 Jun 1996 07:18:11 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA17596 for ; Mon, 10 Jun 1996 07:18:05 -0700 (PDT) Received: from gmarco.eclipse.org (ts1port15d.masternet.it [194.184.65.37]) by masternet.it (8.6.12/8.6.9) with SMTP id PAA31327 for ; Mon, 10 Jun 1996 15:14:53 +0200 Message-ID: <31BC9F44.41C67EA6@masternet.it> Date: Mon, 10 Jun 1996 22:18:44 +0000 From: Gianmarco Giovannelli X-Mailer: Mozilla 3.0b3 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: A2940uw doesn't find cdrom(s) with the boot floppy & more Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It is arrived my 2.2 snap (960501) form walnut creek... Tried to boot , it fails to find the cdroms and the tape (sigh). It is not a nice thing if you have only that CDrom and that tape and no other DOS partition to boot from ... :-) Btw now I solve everything and we are up and running again .... Other thing : It seems that sysinstall has some troubles with the refresh of the video, mixing togheter two video pages or not drawing some parts of the text... I am using an mga matrox millenium... Thanks for attention -- Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | http://www.masternet.it/dsc/gmarco | Gianmarco | +-------------------------------------+--------------------+ From owner-freebsd-current Mon Jun 10 08:08:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA12856 for current-outgoing; Mon, 10 Jun 1996 08:08:13 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA12847 for ; Mon, 10 Jun 1996 08:08:10 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA11944; Mon, 10 Jun 1996 11:06:41 -0400 Date: Mon, 10 Jun 1996 11:06:41 -0400 From: Garrett Wollman Message-Id: <9606101506.AA11944@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: current@FreeBSD.org Subject: Re: Minor nit in build process plus fix In-Reply-To: <199606100252.TAA02819@phaeton.artisoft.com> References: <199606100134.LAA23798@godzilla.zeta.org.au> <199606100252.TAA02819@phaeton.artisoft.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > I was thinking in terms of the top level make setting an environment > variable. The problem is really "..", not "paths relative to the > build root". This presupposes that there /is/ a ``top level make''. When I'm rebuilding `w', I don't start from /usr/src, I start from /usr/src/usr.bin/w (or, on my distribution-building box, from /usr/releng/src/usr.bin/w). -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jun 10 08:40:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA18153 for current-outgoing; Mon, 10 Jun 1996 08:40:53 -0700 (PDT) Received: from usa.nai.net (usa.nai.net [204.71.21.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA18086; Mon, 10 Jun 1996 08:40:40 -0700 (PDT) Received: from chris.nai.net (chris.nai.net [204.71.21.7]) by usa.nai.net (8.6.12/8.6.5) with SMTP id LAA21780; Mon, 10 Jun 1996 11:36:52 -0400 Message-ID: <31BC4136.2386@nai.net> Date: Mon, 10 Jun 1996 11:37:26 -0400 From: Chris Lukas Reply-To: chris@usa.nai.net Organization: NAI X-Mailer: Mozilla 3.0b4Gold (Win95; I) MIME-Version: 1.0 To: Jaye Mathisen CC: Paul Traina , freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: What about... was: Re: -Stable, credit card donations to FreeBSD, Inc. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > > I think Paul's analysis vastly oversimplifies the issue. Anybody could > take a CD, and offer it at a cheaper price. Doesn't mean they'll sell > enough of them to dent walnut creek. > > Perhaps WC could stick a sticker on the box that says "Some amount of > money from this sale goes to furthering development". > > Or a higher-priced subscription plan. > > Or how about selling access to an "exclusive" mailing list, that is shared > with the developers? > > I would pay money if my technical issue questions, as opposed to generic > "anybody seen a ...." questions were sent directly to the developers, and > I *knew* that it was followed by the developers. Even if not acted upon. > ... > Too many times, I see the hardcore developers talk about avoiding reading > the lists, because it consumes too much time... I'd pay to be on a list > that they would always attempt to read... > > Or tie the mailing list in with a higher priced FreeBSD subscription plan. > > The bean-counters here have a hard time with "donation", but wouldn't > blink 2x if it was called a "support list", or whatever. It would be no > different than purchasing a Mickey Soft Developer Network subscription. ... > Frankly, a paid subscription list may work better for the developers > anyway. Somebody's paying money to be on the list, the implication being > that they think enough of the product to pay for the list, so it would > behoove a developer to at least take a gander at the issue/problem, in > order to keep the $$$'s rolling in that would hopefully pay somebody else > to do menial work that the developer is currently having to do, instead of > hacking on FreeBSD. > I wholeheartedly agree. I actually find it difficult to base my business on a product that some is NOT making money on. Who is going to run the paid subscription list, and do the developers agree? (reverse order). Chris Lukas From owner-freebsd-current Mon Jun 10 09:42:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA23853 for current-outgoing; Mon, 10 Jun 1996 09:42:01 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA23846; Mon, 10 Jun 1996 09:41:58 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA16872 ; Mon, 10 Jun 1996 09:41:57 -0700 Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id JAA23011; Mon, 10 Jun 1996 09:38:19 -0700 (PDT) Message-Id: <199606101638.JAA23011@precipice.shockwave.com> To: chris@usa.nai.net cc: Jaye Mathisen , freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: What about... was: Re: -Stable, credit card donations to FreeBSD, Inc. In-reply-to: Your message of "Mon, 10 Jun 1996 11:37:26 EDT." <31BC4136.2386@nai.net> Date: Mon, 10 Jun 1996 09:38:18 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From: Chris Lukas Subject: Re: What about... was: Re: -Stable, credit card donations to FreeBSD >>, Inc. I wholeheartedly agree. I actually find it difficult to base my business on a product that some is NOT making money on. Who is going to run the paid subscription list, and do the developers agree? (reverse order). Chris Lukas http://www.bsdi.com/ We already have one paid-support BSD unix, and it happens to be a pretty good one at that. I don't see the need to make a "Not-So-Free-BSD". It's a pretty poor business model to support FreeBSD, because 85% of your potential revenue stream will try to screw you. BSDI controls this by selling licenses on a per-CPU basis. Cygnus controls this by incorporating fixes into FSF versions of code slower than they incorporate into their own code (which is, again, licensed). Paul From owner-freebsd-current Mon Jun 10 11:39:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01351 for current-outgoing; Mon, 10 Jun 1996 11:39:29 -0700 (PDT) Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA01324; Mon, 10 Jun 1996 11:39:18 -0700 (PDT) Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.5/XS4ALL) with ESMTP id UAA09619; Mon, 10 Jun 1996 20:38:35 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id UAA20985; Mon, 10 Jun 1996 20:24:57 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id HAA17707; Mon, 10 Jun 1996 07:33:14 +0200 (MET DST) Date: Mon, 10 Jun 1996 07:33:14 +0200 (MET DST) Message-Id: <199606100533.HAA17707@plm.xs4all.nl> From: Peter Mutsaers To: gpalmer@FreeBSD.ORG CC: freebsd-current@FreeBSD.ORG In-reply-to: <7861.834317136@palmer.demon.co.uk> (gpalmer@FreeBSD.ORG) Subject: Re: More on VM, swap leaks Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> On Sun, 09 Jun 1996 11:45:36 +0100, "Gary Palmer" said: GP> Peter Mutsaers wrote in message ID GP> <87d93ac026.fsf@plm.xs4all.nl>: >> But the FreeBSD man pages suggest that it is not ignored. GP> *WHICH* FreeBSD man page, and I'll go correct it. sticky(8), chmod(2) suggest that it does not have much effect, but still has some. -- ______________________________________________________________________ Peter Mutsaers | Abcoude (Utrecht), | "Quod licet bovis, plm@xs4all.nl | the Netherlands | non licet Jovi." From owner-freebsd-current Mon Jun 10 12:05:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA04768 for current-outgoing; Mon, 10 Jun 1996 12:05:30 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA04751 for ; Mon, 10 Jun 1996 12:05:23 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA09662; Mon, 10 Jun 1996 13:05:22 -0600 Date: Mon, 10 Jun 1996 13:05:22 -0600 From: Nate Williams Message-Id: <199606101905.NAA09662@rocky.sri.MT.net> To: current@FreeBSD.org Subject: Attention 3C5X9 owners Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Can you please test out this patch to /sys/i386/isa/if_ep.c to make sure this works? This changes the way the driver selects the different card ports (AUI/BNC), and is needed for the PCCARD support (not included). In order to get the BNC connector working on my 3C589 card, but since it's based on code that was originally for the 3C509 I suspect it should work. I need folks who have AUI connections, and folks who have BNC connections to test this to make sure it works, or even better folks who have both can test it to make sure it works fine with both. Thanks! Nate ----------- Index: if_ep.c =================================================================== RCS file: /home/CVS/src/sys/i386/isa/if_ep.c,v retrieving revision 1.44 diff -c -r1.44 if_ep.c *** if_ep.c 1996/05/24 15:22:36 1.44 --- if_ep.c 1996/06/10 19:02:33 *************** *** 644,651 **** if(ifp->if_flags & IFF_LINK0 && sc->ep_connectors & AUI) { /* nothing */ } else if(ifp->if_flags & IFF_LINK1 && sc->ep_connectors & BNC) { outw(BASE + EP_COMMAND, START_TRANSCEIVER); ! DELAY(1000); } else if(ifp->if_flags & IFF_LINK2 && sc->ep_connectors & UTP) { GO_WINDOW(4); outw(BASE + EP_W4_MEDIA_TYPE, ENABLE_UTP); --- 644,655 ---- if(ifp->if_flags & IFF_LINK0 && sc->ep_connectors & AUI) { /* nothing */ } else if(ifp->if_flags & IFF_LINK1 && sc->ep_connectors & BNC) { + GO_WINDOW(0); + /* set the xcvr */ + outw(BASE + EP_W0_ADDRESS_CFG, 3 << 14); + GO_WINDOW(2); outw(BASE + EP_COMMAND, START_TRANSCEIVER); ! GO_WINDOW(1); } else if(ifp->if_flags & IFF_LINK2 && sc->ep_connectors & UTP) { GO_WINDOW(4); outw(BASE + EP_W4_MEDIA_TYPE, ENABLE_UTP); From owner-freebsd-current Mon Jun 10 12:08:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05146 for current-outgoing; Mon, 10 Jun 1996 12:08:11 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA05137 for ; Mon, 10 Jun 1996 12:08:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA04055; Mon, 10 Jun 1996 12:07:49 -0700 From: Terry Lambert Message-Id: <199606101907.MAA04055@phaeton.artisoft.com> Subject: Re: Minor nit in build process plus fix To: wollman@lcs.mit.edu (Garrett Wollman) Date: Mon, 10 Jun 1996 12:07:49 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.org In-Reply-To: <9606101506.AA11944@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 10, 96 11:06:41 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I was thinking in terms of the top level make setting an environment > > variable. The problem is really "..", not "paths relative to the > > build root". > > This presupposes that there /is/ a ``top level make''. When I'm > rebuilding `w', I don't start from /usr/src, I start from > /usr/src/usr.bin/w (or, on my distribution-building box, from > /usr/releng/src/usr.bin/w). Or a top level environment variable, when you do that. Like having a CVSROOT around, you'd need a SRCROOT. I'd suggest a default of /usr/src, if none is specified. Then I can have a symlink tree: /usr/src -> /a/smp /a/current: COPYRIGHT CVS CVS-INFO Makefile README TODO TODO-2.1 bin -> /b/src-current/bin eBones -> /b/src-current/eBones etc -> /b/src-current/etc games -> /b/src-current/games gnu -> /b/src-current/gnu include -> /b/src-current/include lib -> /b/src-current/lib libexec -> /b/src-current/libexec lkm -> /b/src-current/lkm ports -> /b/src-current/ports release -> /b/src-current/release sbin -> /b/src-current/sbin secure -> /b/src-current/secure share -> /b/src-current/share sys -> /b/src-current/sys usr.bin -> /b/src-current/usr.bin usr.sbin -> /b/src-current/usr.sbin /a/smp: COPYRIGHT CVS CVS-INFO Makefile README TODO TODO-2.1 bin -> /b/src-current/bin eBones -> /b/src-current/eBones etc -> /b/src-current/etc games -> /b/src-current/games gnu -> /b/src-current/gnu include -> /b/src-current/include lib -> /b/src-current/lib libexec -> /b/src-current/libexec lkm -> /b/src-current/lkm ports -> /b/src-current/ports release -> /b/src-current/release sbin -> /b/src-current/sbin secure -> /b/src-current/secure share -> /b/src-current/share sys -> /b/src-smp/sys <-- *** usr.bin -> /b/src-current/usr.bin usr.sbin -> /b/src-current/usr.sbin If I don't want to change SRCROOT, I do the build in the top level source directory (which pulls it via pwd in the top Makefile *only*, or I change the symlink /usr/src. One problem with building from the top each time is that the dependencies don't necessarily work like they are supposed to for preventing rebuilds of some things. If that's a problem for you, you can always fix them. 8-). Maybe a k.bin/k.usr.bin for kernel header dependent build files that go in /bin or /usr/bin, to seperate out their build? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 10 12:16:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05981 for current-outgoing; Mon, 10 Jun 1996 12:16:57 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA05968; Mon, 10 Jun 1996 12:16:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA04084; Mon, 10 Jun 1996 12:15:53 -0700 From: Terry Lambert Message-Id: <199606101915.MAA04084@phaeton.artisoft.com> Subject: Re: does freebsd support SMP? To: peter@spinner.DIALix.COM (Peter Wemm) Date: Mon, 10 Jun 1996 12:15:53 -0700 (MST) Cc: terry@lambert.org, phk@FreeBSD.org, nathan@netrail.net, freebsd-current@FreeBSD.org, freebsd-smp@FreeBSD.org In-Reply-To: <199606100540.NAA02800@spinner.DIALix.COM> from "Peter Wemm" at Jun 10, 96 01:39:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >The locking code (mplock.s) only checks for non-zero. > > Yes.. smp_active=1 means you can get the second cpu up in protected mode > and running virtual, but not scheduling yet. ??? Not scheduling? I thought it was scheduling? Should I go back to my October 1994 kernel + hacks + Jack's patches + my patches to be able to work on kernel reentrancy at this time? I've been hacking FS code in this envirnment for some time already, without a lot of problems. When are you planning on committing your changes for APIC messaging, etc.? What can I do to help get scheduling up? I need multiple kernel entrances to test conflict resoloution and transitive closure calculation over the lock hierarchy code I've been pounding on... is the page containing the shared mutex tagged non-cacheable? Is there an allocation method for getting more of these pages, if I need them? Re: the NCPU vs. MAXCPU ... the reason I made a distinction is that you may not want all available CPU's active (I can only think of testing as wanting this, but it could happen). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 10 12:21:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA06626 for current-outgoing; Mon, 10 Jun 1996 12:21:33 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA06609 for ; Mon, 10 Jun 1996 12:21:30 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA09709; Mon, 10 Jun 1996 13:21:29 -0600 Date: Mon, 10 Jun 1996 13:21:29 -0600 From: Nate Williams Message-Id: <199606101921.NAA09709@rocky.sri.MT.net> To: current@FreeBSD.org Subject: CLOCK stuff at bootup Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk OK, I didn't pay alot of attention when this stuff went in because I was scared away from current. However, after the glowing reports from the weekend, I decided to upgrade my laptop to -current to try and work on some PCCARD stuff on the road. However, I'm not sure what I'm supposed to be doing re: the clock messages now. FreeBSD 2.2-CURRENT #2: Mon Jun 10 12:46:29 MDT 1996 root@nec.sri.MT.net:/usr/src/sys/compile/CARD Calibrating clock(s) relative to mc146818A clock ... i586 clock: 75171042 Hz, i8 254 clock: 1193196 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method i586 clock: 0 Hz CPU: Pentium (75.16-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping=4 Features=0x1bf I'm assuming I'm supposed to define one or both of the above, but why? How do I determine which one is the more accurate, since obviously the i854 clock is not running at the same frequency as my Pentium chip. :) Bruce, what do you want done here? Nate From owner-freebsd-current Mon Jun 10 12:26:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07362 for current-outgoing; Mon, 10 Jun 1996 12:26:02 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA07323; Mon, 10 Jun 1996 12:25:46 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA21662; Mon, 10 Jun 1996 21:24:33 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA27528; Mon, 10 Jun 1996 21:24:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA05113; Mon, 10 Jun 1996 21:01:33 +0200 (MET DST) From: J Wunsch Message-Id: <199606101901.VAA05113@uriah.heep.sax.de> Subject: Re: A2940uw doesn't find cdrom(s) with the boot floppy & more To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 10 Jun 1996 21:01:32 +0200 (MET DST) Cc: gmarco@masternet.it (Gianmarco Giovannelli), jkh@freefall.FreeBSD.org (Jordan K. Hubbard) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <31BC9F44.41C67EA6@masternet.it> from Gianmarco Giovannelli at "Jun 10, 96 10:18:44 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Gianmarco Giovannelli wrote: > Other thing : It seems that sysinstall has some troubles with the > refresh of the video, mixing togheter two video pages or not drawing > some parts of the text... I am using an mga matrox millenium... I can confirm this. Jordan -- the partition editor is sometimes called without clearing the screen first (not always). It works as expected if you know what is going on, and libdialog widgets popping up (``Do you want to do this the regular way...'') are displayed correctly, but the partition editor itself gets ``overshadowed'' by stale libdialog portitions. Upon quitting the partition editor everything continues to work normally. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jun 10 12:38:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09508 for current-outgoing; Mon, 10 Jun 1996 12:38:37 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09481 for ; Mon, 10 Jun 1996 12:38:33 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id PAA24180 for ; Mon, 10 Jun 1996 15:37:24 -0400 (EDT) Date: Mon, 10 Jun 1996 15:38:23 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Kernel panic in fsync, 2.2-960501-SNAP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Got this today (nm output follows): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xf012afc3 stack pointer = 0x10:0xefbfff2c frame pointer = 0x10:0xefbfff58 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 = 6732 (emacs) interrupt mask = panic: page fault syncing disks... 39 39 36 23 8 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... FreeBSD 2.2-960501-SNAP #0: Tue Jun 4 15:08:23 EDT 1996 taob@cabal.io.org:/usr/local/src/2.2-960501-SNAP/sys/compile/SHELL Calibrating clock(s) relative to mc146818A clock ... i586 clock: 132618376 Hz, i8254 clock: 1193066 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method i586 clock: 0 Hz CPU: Pentium (132.62-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping=11 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 129929216 (126884K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 pci0:7:1: Intel Corporation, device=0x1230, class=storage (ide) [no driver assigned] ncr0 rev 2 int a irq 11 on pci0:10 ncr0 waiting for scsi devices to settle (ncr0:0:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1042MB (2134305 512 byte sectors) sd0(ncr0:0:0): with 3835 cyls, 4 heads, and an average 139 sectors/track de0 rev 18 int a irq 14 on pci0:11 de0: DC21140 [10-100Mb/s] pass 1.2 Ethernet address 00:00:c0:84:46:c8 de0: enabling 10baseT UTP port vga0 rev 227 int a irq ?? on pci0:12 Probing for devices on the ISA bus: pcvt: doreset() - got KEYB_R_RESEND response ... [one time only msg] pcvt: doreset() - Caution - no PC keyboard detected! vt0 at 0x60-0x6f irq 1 on motherboard vt0: unknown trident, 80 col, color, 8 scr, unknown kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface WARNING: / was not properly dismounted. # nm -a /kernel | sort | fgrep -C f012af f012adc0 T _ftruncate f012aef0 T _otruncate f012af20 T _oftruncate f012af50 T _fsync f012b020 T _rename f012b31c T _mkdir -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Mon Jun 10 14:38:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA27631 for current-outgoing; Mon, 10 Jun 1996 14:38:35 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA27603 for ; Mon, 10 Jun 1996 14:38:30 -0700 (PDT) Received: from masternet.it (masternet.it [194.184.65.2]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with SMTP id OAA02651 for ; Mon, 10 Jun 1996 14:38:27 -0700 (PDT) Received: from socrate (ts1port4d.masternet.it [194.184.65.26]) by masternet.it (8.6.12/8.6.9) with SMTP id WAA03291 for ; Mon, 10 Jun 1996 22:35:05 +0200 Message-ID: <31BC9872.41C67EA6@masternet.it> Date: Mon, 10 Jun 1996 23:49:38 +0200 From: Beck Peccoz Amedeo X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: packeage not installing Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On both 962603 and latest Snapshot the package /cdrom/packages/All/ical-1.9.tgz gives a gzip: stdin: unexpected end of file tar: child returned status 1 when trying to decompressing it. Somebody forgot a piece? :-)) -- Beck-Peccoz Amedeo GEA Software S.r.l. Via Deffeyes, 1 11025 Gressoney Saint Jean (AO) ITALY Tel. ++39-125-366302 Fax. ++39-125-366415 From owner-freebsd-current Mon Jun 10 15:18:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05146 for current-outgoing; Mon, 10 Jun 1996 15:18:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA05136 for ; Mon, 10 Jun 1996 15:18:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id PAA20852; Mon, 10 Jun 1996 15:15:49 -0700 (PDT) To: Gianmarco Giovannelli cc: current@freebsd.org Subject: Re: A2940uw doesn't find cdrom(s) with the boot floppy & more In-reply-to: Your message of "Mon, 10 Jun 1996 22:18:44 -0000." <31BC9F44.41C67EA6@masternet.it> Date: Mon, 10 Jun 1996 15:15:49 -0700 Message-ID: <20850.834444949@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Tried to boot , it fails to find the cdroms and the tape (sigh). Erm, can you tell me more about what happened and your config? > Other thing : It seems that sysinstall has some troubles with the > refresh of the video, mixing togheter two video pages or not drawing > some parts of the text... I am using an mga matrox millenium... Under what circumstances? People, please, if you're going to report a problem don't just say "Well, it didn't work on my system. Couldn't find my hardware." Such "bug reports" are totally and utterly useless to me or anyone else on this list and you might as well just not say anything at all! :-( If FreeBSD fails to detect your hardware, I need to know _what_ hardware it fails to detect. If there's some weird bug where your screen gets messed up I need to know _where_ it gets messed up and what you were doing at the time. If it fails to install, I need to know _how_ you tried to install it. These are all important details that people routinely omit from their bug reports and I'm not a psychic! :-) Thanks! Jordan From owner-freebsd-current Mon Jun 10 16:56:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25516 for current-outgoing; Mon, 10 Jun 1996 16:56:53 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA25504 for ; Mon, 10 Jun 1996 16:56:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA01251; Tue, 11 Jun 1996 09:55:37 +1000 Date: Tue, 11 Jun 1996 09:55:37 +1000 From: Bruce Evans Message-Id: <199606102355.JAA01251@godzilla.zeta.org.au> To: current@freebsd.org, nate@sri.MT.net Subject: Re: CLOCK stuff at bootup Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >OK, I didn't pay alot of attention when this stuff went in because I was >scared away from current. However, after the glowing reports from the Pay attention or read old mail. >However, I'm not sure what I'm supposed to be doing re: the clock >messages now. >FreeBSD 2.2-CURRENT #2: Mon Jun 10 12:46:29 MDT 1996 > root@nec.sri.MT.net:/usr/src/sys/compile/CARD >Calibrating clock(s) relative to mc146818A clock ... i586 clock: 75171042 Hz, i8 >254 clock: 1193196 Hz >CLK_USE_I8254_CALIBRATION not specified - using default frequency >CLK_USE_I586_CALIBRATION not specified - using old calibration method >i586 clock: 0 Hz >CPU: Pentium (75.16-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x524 Stepping=4 > Features=0x1bf >I'm assuming I'm supposed to define one or both of the above, but why? Because defining one or both might work better. Using sysctl to set the actual (current) value might work better still. >How do I determine which one is the more accurate, since obviously the >i854 clock is not running at the same frequency as my Pentium chip. :) The i8254 clock determines long term accuracy. Run for a while and determine the drift and/or the time daemon adjustments. Use sysctl to specify the i8254 clock frequency that minimizes the drift and/or the adjustments or accept the default from calibration or accept the fixed default. The i586 clock determines intra-clock-interrupt times. Specify the i586 clock frequency that minimizes the jitter in getttimeofday(). Bruce From owner-freebsd-current Mon Jun 10 17:01:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26104 for current-outgoing; Mon, 10 Jun 1996 17:01:05 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA26099 for ; Mon, 10 Jun 1996 17:01:02 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id SAA10896; Mon, 10 Jun 1996 18:00:51 -0600 Date: Mon, 10 Jun 1996 18:00:51 -0600 From: Nate Williams Message-Id: <199606110000.SAA10896@rocky.sri.MT.net> To: Bruce Evans Cc: current@freebsd.org, nate@sri.MT.net Subject: Re: CLOCK stuff at bootup In-Reply-To: <199606102355.JAA01251@godzilla.zeta.org.au> References: <199606102355.JAA01251@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >CLK_USE_I8254_CALIBRATION not specified - using default frequency > >CLK_USE_I586_CALIBRATION not specified - using old calibration method > >i586 clock: 0 Hz > >CPU: Pentium (75.16-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x524 Stepping=4 > > Features=0x1bf > > >I'm assuming I'm supposed to define one or both of the above, but why? > > Because defining one or both might work better. Using sysctl to set the > actual (current) value might work better still. Umm, what am I supposed to set using sysctl? I don't remember ever seeing this kind of detail in old email. > >How do I determine which one is the more accurate, since obviously the > >i854 clock is not running at the same frequency as my Pentium chip. :) > > The i8254 clock determines long term accuracy. Run for a while and > determine the drift and/or the time daemon adjustments. How? > Use sysctl to > specify the i8254 clock frequency that minimizes the drift and/or the > adjustments or accept the default from calibration or accept the fixed > default. How? > The i586 clock determines intra-clock-interrupt times. Specify the i586 > clock frequency that minimizes the jitter in getttimeofday(). How? From owner-freebsd-current Mon Jun 10 17:07:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26705 for current-outgoing; Mon, 10 Jun 1996 17:07:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA26700 for ; Mon, 10 Jun 1996 17:07:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA05112 for current@freebsd.org; Mon, 10 Jun 1996 17:06:50 -0700 From: Terry Lambert Message-Id: <199606110006.RAA05112@phaeton.artisoft.com> Subject: New bug in de driver caused by recent changes? To: current@freebsd.org Date: Mon, 10 Jun 1996 17:06:50 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have recently updates a machine with a new kernel (it was running a snap following the last -release. I have gotten several errors of the type: de0: receiver: CRC error When this occurs, outbound rlogin sessions get dumped (the message is a timeout of some kind). Inbound telnet sessions are undisturbed. There may be intermittent routing failures to the remote host. Is it possible that we've implemented out own version of the NT "sniper" bug? The system in questions is running routed -q. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 10 17:28:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28865 for current-outgoing; Mon, 10 Jun 1996 17:28:18 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA28841 for ; Mon, 10 Jun 1996 17:28:08 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id KAA02186; Tue, 11 Jun 1996 10:18:21 +1000 Date: Tue, 11 Jun 1996 10:18:21 +1000 From: Bruce Evans Message-Id: <199606110018.KAA02186@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@sri.MT.net Subject: Re: CLOCK stuff at bootup Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Because defining one or both might work better. Using sysctl to set the >> actual (current) value might work better still. >Umm, what am I supposed to set using sysctl? I don't remember ever >seeing this kind of detail in old email. Clock nominal frequencies. >> The i8254 clock determines long term accuracy. Run for a while and >> determine the drift and/or the time daemon adjustments. >How? Compare the output of `date` with an accurate clock or look in the time deaemon log files. >> Use sysctl to >> specify the i8254 clock frequency that minimizes the drift and/or the >How? Look in the output of `sysctl -a` to find the relevant variable and set it as usual. >> The i586 clock determines intra-clock-interrupt times. Specify the i586 >> clock frequency that minimizes the jitter in getttimeofday(). >How? First find the frequency. Set it as above. Bruce From owner-freebsd-current Mon Jun 10 18:09:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA03783 for current-outgoing; Mon, 10 Jun 1996 18:09:56 -0700 (PDT) Received: from sting.artisoft.com (sting.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA03778 for ; Mon, 10 Jun 1996 18:09:55 -0700 (PDT) Received: (from mday@localhost) by sting.artisoft.com (8.6.12/8.6.12) id SAA22935; Mon, 10 Jun 1996 18:09:24 -0700 Date: Mon, 10 Jun 1996 18:09:24 -0700 From: Matt Day Message-Id: <199606110109.SAA22935@sting.artisoft.com> To: freebsd-current@FreeBSD.ORG, taob@io.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Tao wrote: > Got this today (nm output follows): > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x18 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf012afc3 > stack pointer = 0x10:0xefbfff2c > frame pointer = 0x10:0xefbfff58 > 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 = 6732 (emacs) > interrupt mask = > panic: page fault > > [..] > > # nm -a /kernel | sort | fgrep -C f012af > f012adc0 T _ftruncate > f012aef0 T _otruncate > f012af20 T _oftruncate > f012af50 T _fsync > f012b020 T _rename > f012b31c T _mkdir It looks like your panic could very well have been caused by a bug I reported several months ago. It has not been fixed yet in either tree. Here is my original bug report: > From mday Mon Feb 5 03:01:27 1996 > To: freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org > Subject: Bad bug in ffs_sync() & friends > > Hi, > > I think there is a very rare, yet fatal, bug in ffs_sync() in the > -CURRENT code (and the -STABLE code, and NetBSD 1.1, etc...). > This bug has occured twice on my system in the past 6 months. > > Consider this scenario: > ffs_vget() calls getnewvnode(), and then calls MALLOC() to allocate > memory for the incore inode. That MALLOC() blocks. > While that MALLOC() is blocked, ffs_sync() gets called. ffs_sync() > finds the vnode just set up by that getnewvnode() on the mnt_vnodelist > (because getnewvnode() put it there) and proceeds to dereference > vp->v_data by calling VOP_ISLOCKED(), but v_data is still zero because > that MALLOC() blocked. > > It looks like this bug is lurking in many other routines as well -- > pretty much any routine that runs down the mnt_vnodelist. > > What do you think? Please e-mail me directly, as I do not subscribe to > these mailing lists. > > Thanks, > > Matt Day Here is one possible bug fix to the -CURRENT FFS code (the same bug exists in some of the other file systems as well): *** sys/ufs/ffs/ffs_vfsops.c- Sat Mar 2 20:43:40 1996 --- sys/ufs/ffs/ffs_vfsops.c Mon Jun 10 17:49:30 1996 *************** *** 866,871 **** --- 866,881 ---- } ffs_inode_hash_lock = 1; + /* + * N.B.: If this MALLOC() is performed after the getnewvnode() + * it might block, leaving a vnode with a NULL v_data to be + * found by ffs_sync() if a sync happens to fire right then, + * which will cause a panic because ffs_sync() blindly + * dereferences vp->v_data (as well it should). + */ + type = ump->um_devvp->v_tag == VT_MFS ? M_MFSNODE : M_FFSNODE; /* XXX */ + MALLOC(ip, struct inode *, sizeof(struct inode), type, M_WAITOK); + /* Allocate a new vnode/inode. */ error = getnewvnode(VT_UFS, mp, ffs_vnodeop_p, &vp); if (error) { *************** *** 873,882 **** wakeup(&ffs_inode_hash_lock); ffs_inode_hash_lock = 0; *vpp = NULL; return (error); } - type = ump->um_devvp->v_tag == VT_MFS ? M_MFSNODE : M_FFSNODE; /* XXX */ - MALLOC(ip, struct inode *, sizeof(struct inode), type, M_WAITOK); bzero((caddr_t)ip, sizeof(struct inode)); vp->v_data = ip; ip->i_vnode = vp; --- 883,891 ---- wakeup(&ffs_inode_hash_lock); ffs_inode_hash_lock = 0; *vpp = NULL; + FREE(ip, type); return (error); } bzero((caddr_t)ip, sizeof(struct inode)); vp->v_data = ip; ip->i_vnode = vp; Another way to fix the bug would be to check for vp->v_data == NULL in ffs_sync(). But that way would not be very elegant, in my opinion. I think a good, safe policy would be "if a vnode can be found on the mnt_vnodelist list by a process, the process can assume that the vnode is fully initialized". Hope that helps, Matt Day From owner-freebsd-current Mon Jun 10 18:18:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05204 for current-outgoing; Mon, 10 Jun 1996 18:18:23 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA05186 for ; Mon, 10 Jun 1996 18:18:19 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id TAA11261; Mon, 10 Jun 1996 19:18:12 -0600 Date: Mon, 10 Jun 1996 19:18:12 -0600 From: Nate Williams Message-Id: <199606110118.TAA11261@rocky.sri.MT.net> To: Bruce Evans Cc: nate@sri.MT.net, current@freebsd.org Subject: Re: CLOCK stuff at bootup In-Reply-To: <199606110018.KAA02186@godzilla.zeta.org.au> References: <199606110018.KAA02186@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Because defining one or both might work better. Using sysctl to set the > >> actual (current) value might work better still. > > >Umm, what am I supposed to set using sysctl? I don't remember ever > >seeing this kind of detail in old email. > > Clock nominal frequencies. > > >> The i8254 clock determines long term accuracy. Run for a while and > >> determine the drift and/or the time daemon adjustments. > > >How? > > Compare the output of `date` with an accurate clock or look in the time > deaemon log files. And how would I do that? I'm not sure what kind of 'drift' I'm expecting. (Forgive me, but I'm not clock expert, nor do I understand what all of this buys me if I have to hand-set all of these variables.) If I have to hand-set everything and play with this on a per-machine basis, then it's not worth it. What does having all of this flexibility buy me? > >> Use sysctl to > >> specify the i8254 clock frequency that minimizes the drift and/or the > > >How? > > Look in the output of `sysctl -a` to find the relevant variable and set > it as usual. machdep.i8254_freq: 1193182 This was set at bootup time already, so how do I determine what to set it to except via trial and error. > > >> The i586 clock determines intra-clock-interrupt times. Specify the i586 > >> clock frequency that minimizes the jitter in getttimeofday(). > > >How? > > First find the frequency. Set it as above. machdep.i586_freq: 0 Set it to the stuff that was kicked out by the kernel? Why isn't aren't these values already set by default? Nate From owner-freebsd-current Mon Jun 10 18:42:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08733 for current-outgoing; Mon, 10 Jun 1996 18:42:42 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA08726 for ; Mon, 10 Jun 1996 18:42:39 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id SAA20186 for ; Mon, 10 Jun 1996 18:42:37 -0700 Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id SAA18915; Mon, 10 Jun 1996 18:41:53 -0700 (PDT) Message-Id: <199606110141.SAA18915@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: Matt Day cc: freebsd-current@freebsd.org, taob@io.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-reply-to: Your message of "Mon, 10 Jun 1996 18:09:24 PDT." <199606110109.SAA22935@sting.artisoft.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 10 Jun 1996 18:41:53 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It looks like your panic could very well have been caused by a bug >I reported several months ago. It has not been fixed yet in either >tree. Here is my original bug report: > >> From mday Mon Feb 5 03:01:27 1996 Thanks for the patch, Matt. It looks fine. Sorry your previous bug report didn't get the attention it deserved. It looks like the timing was probably bad - Feb 5 would have been right after Usenix, and I had about 3000 pieces of email to read and respond to when I got back. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jun 10 19:42:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA12781 for current-outgoing; Mon, 10 Jun 1996 19:42:17 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA12774 for ; Mon, 10 Jun 1996 19:42:13 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA08156; Tue, 11 Jun 1996 12:40:59 +1000 Date: Tue, 11 Jun 1996 12:40:59 +1000 From: Bruce Evans Message-Id: <199606110240.MAA08156@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@sri.MT.net Subject: Re: CLOCK stuff at bootup Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >> The i8254 clock determines long term accuracy. Run for a while and >> >> determine the drift and/or the time daemon adjustments. >> >> >How? >> >> Compare the output of `date` with an accurate clock or look in the time >> deaemon log files. >And how would I do that? I'm not sure what kind of 'drift' I'm >expecting. >(Forgive me, but I'm not clock expert, nor do I understand what all of >this buys me if I have to hand-set all of these variables.) Then don't ask. The defaults work the same as before. >> >> Use sysctl to >> >> specify the i8254 clock frequency that minimizes the drift and/or the >> >> >How? >> >> Look in the output of `sysctl -a` to find the relevant variable and set >> it as usual. >machdep.i8254_freq: 1193182 >This was set at bootup time already, so how do I determine what to set >it to except via trial and error. The boot messages give another possible values. Otherwise, use trial and error. >> >> The i586 clock determines intra-clock-interrupt times. Specify the i586 >> >> clock frequency that minimizes the jitter in getttimeofday(). >> >> >How? >> >> First find the frequency. Set it as above. >machdep.i586_freq: 0 Nothing set it, so it remains at 0. >Set it to the stuff that was kicked out by the kernel? Why isn't aren't >these values already set by default? Because they are relative to the mc146818A clock, which is not known to be a better reference point than the i8254 clock (it probably is, but a sample size of 3 or 4 systems is not enough to decide). Bruce From owner-freebsd-current Mon Jun 10 20:49:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA19315 for current-outgoing; Mon, 10 Jun 1996 20:49:29 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA19301 for ; Mon, 10 Jun 1996 20:49:19 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id VAA11592; Mon, 10 Jun 1996 21:49:12 -0600 Date: Mon, 10 Jun 1996 21:49:12 -0600 From: Nate Williams Message-Id: <199606110349.VAA11592@rocky.sri.MT.net> To: Bruce Evans Cc: nate@sri.MT.net, current@FreeBSD.ORG Subject: Re: CLOCK stuff at bootup In-Reply-To: <199606110240.MAA08156@godzilla.zeta.org.au> References: <199606110240.MAA08156@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> >> The i8254 clock determines long term accuracy. Run for a while and > >> >> determine the drift and/or the time daemon adjustments. > >> > >> >How? > >> > >> Compare the output of `date` with an accurate clock or look in the time > >> deaemon log files. > > >And how would I do that? I'm not sure what kind of 'drift' I'm > >expecting. > > >(Forgive me, but I'm not clock expert, nor do I understand what all of > >this buys me if I have to hand-set all of these variables.) > > Then don't ask. The defaults work the same as before. Don't stick stuff in the default kernel that don't make any sense. I just went back to your original email, and it doesn't make any more sense now than it did then. (No offense). It's too technical for the 'average' user, but you're making the default verbosity enough to peak the interest of the average user. Help me help you by making your instructions more clear please. Don't assume I have a clue, then I will be more able to help you do whatever it is you're trying to do. :) Nate From owner-freebsd-current Mon Jun 10 21:52:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23102 for current-outgoing; Mon, 10 Jun 1996 21:52:11 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22975; Mon, 10 Jun 1996 21:51:55 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.6.9) with SMTP id VAA05982; Mon, 10 Jun 1996 21:49:40 -0700 (PDT) Message-Id: <199606110449.VAA05982@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: peter@spinner.dialix.com (Peter Wemm), phk@freebsd.org, nathan@netrail.net, freebsd-current@freebsd.org, freebsd-smp@freebsd.org Subject: Re: does freebsd support SMP? In-reply-to: Your message of Mon, 10 Jun 96 12:15:53 -0700. <199606101915.MAA04084@phaeton.artisoft.com> Date: Mon, 10 Jun 1996 21:49:36 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Re: the NCPU vs. MAXCPU ... the reason I made a distinction is that >you may not want all available CPU's active (I can only think of >testing as wanting this, but it could happen). Maybe you'd want to reserve one of them for a game of Descent... ;-) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Mon Jun 10 22:16:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA24504 for current-outgoing; Mon, 10 Jun 1996 22:16:58 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA24472 for ; Mon, 10 Jun 1996 22:16:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA14272; Tue, 11 Jun 1996 15:14:57 +1000 Date: Tue, 11 Jun 1996 15:14:57 +1000 From: Bruce Evans Message-Id: <199606110514.PAA14272@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@sri.MT.net Subject: Re: CLOCK stuff at bootup Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >(Forgive me, but I'm not clock expert, nor do I understand what all of >> >this buys me if I have to hand-set all of these variables.) >> >> Then don't ask. The defaults work the same as before. >Don't stick stuff in the default kernel that don't make any sense. I It's not in the default kernel (GENERIC or 2.1). >It's too technical for the 'average' user, but you're making the default >verbosity enough to peak the interest of the average user. I hoped to pique the expertise of above-average users. >Help me help you by making your instructions more clear please. Don't >assume I have a clue, then I will be more able to help you do whatever >it is you're trying to do. :) What I'm trying to do is get feedback about working and broken clocks only from users who know what to look for. Bruce From owner-freebsd-current Tue Jun 11 00:24:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10556 for current-outgoing; Tue, 11 Jun 1996 00:24:39 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA10550 for ; Tue, 11 Jun 1996 00:24:37 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id AAA05151; Tue, 11 Jun 1996 00:26:21 -0700 Date: Tue, 11 Jun 1996 00:26:21 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Veggy Vinny cc: current@FreeBSD.org Subject: Re: console messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 8 Jun 1996, Veggy Vinny wrote: > I'm running the June 3rd, 1996 FreeBSD-current and it seems on a > machine with a Intel Neptune based Dual P5-100 system with 128 megs of > RAM and 300 megs of disk swap, we keep getting the following message and > then the machine reboots or just hangs there, any ideas what can be > causing this? > > /kernel: proc: table is full Increase MAXUSERS in the kernel config. > swap_pager: out of swap space Add some swap to the system. Sounds like you have a heavily used machine. I would guess to crank maxusers to 200 (? - check me !!) and have 250-300MB of swap. (2*memory) No doubt others will have different opinions. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Tue Jun 11 00:26:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10609 for current-outgoing; Tue, 11 Jun 1996 00:26:08 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA10604 for ; Tue, 11 Jun 1996 00:26:06 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id AAA10451; Tue, 11 Jun 1996 00:26:10 -0700 Date: Tue, 11 Jun 1996 00:26:09 -0700 (PDT) From: Veggy Vinny To: dwhite@resnet.uoregon.edu cc: current@FreeBSD.org Subject: Re: console messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 11 Jun 1996, Doug White wrote: > On Sat, 8 Jun 1996, Veggy Vinny wrote: > > > I'm running the June 3rd, 1996 FreeBSD-current and it seems on a > > machine with a Intel Neptune based Dual P5-100 system with 128 megs of > > RAM and 300 megs of disk swap, we keep getting the following message and > > then the machine reboots or just hangs there, any ideas what can be > > causing this? > > > > /kernel: proc: table is full > > Increase MAXUSERS in the kernel config. It's already at 128... > > swap_pager: out of swap space > > Add some swap to the system. There is already 300MB of swap and it does that when it's at 20%.. > Sounds like you have a heavily used machine. I would guess to crank > maxusers to 200 (? - check me !!) and have 250-300MB of swap. (2*memory) > > No doubt others will have different opinions. Well, that is already there... Vince From owner-freebsd-current Tue Jun 11 00:29:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10724 for current-outgoing; Tue, 11 Jun 1996 00:29:30 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA10719 for ; Tue, 11 Jun 1996 00:29:28 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id AAA05164; Tue, 11 Jun 1996 00:31:12 -0700 Date: Tue, 11 Jun 1996 00:31:12 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Veggy Vinny cc: current@FreeBSD.org Subject: Re: console messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 11 Jun 1996, Veggy Vinny wrote: Here I go answering questions without reading the question first :-) > > > I'm running the June 3rd, 1996 FreeBSD-current and it seems on a > > > machine with a Intel Neptune based Dual P5-100 system with 128 megs of > > > RAM and 300 megs of disk swap, we keep getting the following message and > > > then the machine reboots or just hangs there, any ideas what can be > > > causing this? > > > > > > /kernel: proc: table is full > > > > Increase MAXUSERS in the kernel config. > > It's already at 128... Maybe you have a runaway process then. I think I'll let the pros take it from here... this is not something I'm very familiar with. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Tue Jun 11 01:09:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12335 for current-outgoing; Tue, 11 Jun 1996 01:09:24 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA12330 for ; Tue, 11 Jun 1996 01:09:21 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id BAA13317; Tue, 11 Jun 1996 01:09:05 -0700 (PDT) Date: Tue, 11 Jun 1996 01:09:05 -0700 (PDT) Message-Id: <199606110809.BAA13317@silvia.HIP.Berkeley.EDU> To: gea@masternet.it CC: freebsd-current@freebsd.org In-reply-to: <31BC9872.41C67EA6@masternet.it> (message from Beck Peccoz Amedeo on Mon, 10 Jun 1996 23:49:38 +0200) Subject: Re: packeage not installing From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * On both 962603 and latest Snapshot the package * /cdrom/packages/All/ical-1.9.tgz gives a * * gzip: stdin: unexpected end of file * tar: child returned status 1 * * when trying to decompressing it. * * Somebody forgot a piece? :-)) I'm not exactly sure how it happened, but you're quite right. In fact, the whole piece is missing on the 0323 snap CDROM: === >> ls -lg /cdrom/packages/All/ical-1.9.tgz 0 -rw-r--r-- 1 root wheel 0 Mar 19 00:03 /cdrom/packages/All/ical-1.9.tgz === It seems to be ok on the ftp sites though, please go get it from there. By the way, I checked all the files on the 0323 snap CDROM, all other packages are ok. Satoshi From owner-freebsd-current Tue Jun 11 02:41:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17721 for current-outgoing; Tue, 11 Jun 1996 02:41:12 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA17715 for ; Tue, 11 Jun 1996 02:41:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id CAA24090; Tue, 11 Jun 1996 02:40:27 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: gea@masternet.it, freebsd-current@freebsd.org Subject: Re: packeage not installing In-reply-to: Your message of "Tue, 11 Jun 1996 01:09:05 PDT." <199606110809.BAA13317@silvia.HIP.Berkeley.EDU> Date: Tue, 11 Jun 1996 02:40:26 -0700 Message-ID: <24088.834486026@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm not exactly sure how it happened, but you're quite right. In > fact, the whole piece is missing on the 0323 snap CDROM: Sorry folks - I haven't been paying close attention until just now. Yes, this file was truncated on the CDROM for some reason (something to do with an aborted xfer, I think) and though my verification program spotted it on the master CD I was set to release, I didn't deem it important enough to remaster for. This was the very first snap CD, remember, and I didn't even know whether or not we'd sell more than 10 copies. :) The subsequent snap was done with better quality control, a tradition I hope to continue.. :-) Jordan From owner-freebsd-current Tue Jun 11 05:15:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA04120 for current-outgoing; Tue, 11 Jun 1996 05:15:21 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA04107 for ; Tue, 11 Jun 1996 05:15:18 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id GAA12409; Tue, 11 Jun 1996 06:15:00 -0600 Date: Tue, 11 Jun 1996 06:15:00 -0600 From: Nate Williams Message-Id: <199606111215.GAA12409@rocky.sri.MT.net> To: Bruce Evans Cc: nate@sri.MT.net, current@FreeBSD.ORG Subject: Re: CLOCK stuff at bootup In-Reply-To: <199606110514.PAA14272@godzilla.zeta.org.au> References: <199606110514.PAA14272@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > >> >(Forgive me, but I'm not clock expert, nor do I understand what all of > >> >this buys me if I have to hand-set all of these variables.) > >> > >> Then don't ask. The defaults work the same as before. > > >Don't stick stuff in the default kernel that don't make any sense. I > > It's not in the default kernel (GENERIC or 2.1). It's been in all the default kernels in -current since 5/1. > >It's too technical for the 'average' user, but you're making the default > >verbosity enough to peak the interest of the average user. > > I hoped to pique the expertise of above-average users. Please help me into an above average user regarding time-keeping information. Assuming I get xntpd running, what am I looking for when 'things are working better'? > >Help me help you by making your instructions more clear please. Don't > >assume I have a clue, then I will be more able to help you do whatever > >it is you're trying to do. :) > > What I'm trying to do is get feedback about working and broken clocks > only from users who know what to look for. Tell me what to look for. The only way average users will become above-average users is with information, and so far there has been a lack of both IMHO. Nate From owner-freebsd-current Tue Jun 11 06:53:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26337 for current-outgoing; Tue, 11 Jun 1996 06:53:26 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26310 for ; Tue, 11 Jun 1996 06:53:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id XAA00739; Tue, 11 Jun 1996 23:46:40 +1000 Date: Tue, 11 Jun 1996 23:46:40 +1000 From: Bruce Evans Message-Id: <199606111346.XAA00739@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@sri.MT.net Subject: Re: CLOCK stuff at bootup Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> It's not in the default kernel (GENERIC or 2.1). >It's been in all the default kernels in -current since 5/1. The debugging CLOCK options are in neither GENERIC nor LINT. >Tell me what to look for. The only way average users will become >above-average users is with information, and so far there has been a >lack of both IMHO. Look for clocks losing more than 5 seconds/day. I will ignore future mail about this. Bruce From owner-freebsd-current Tue Jun 11 07:32:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA03550 for current-outgoing; Tue, 11 Jun 1996 07:32:48 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA03539 for ; Tue, 11 Jun 1996 07:32:43 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id KAA03152; Tue, 11 Jun 1996 10:30:00 -0400 (EDT) Date: Tue, 11 Jun 1996 10:31:02 -0400 (EDT) From: Brian Tao To: David Greenman cc: Matt Day , freebsd-current@freebsd.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-Reply-To: <199606110141.SAA18915@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 10 Jun 1996, David Greenman wrote: > > Thanks for the patch, Matt. Any caveats to running a 2.2-960501-SNAP kernel with the patch? It applies cleanly enough. I've rebuilt emacs here anyway (didn't expect a patch so quickly!), in case it was tickling something in the 2.1 libraries on a 2.2 system. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Tue Jun 11 08:23:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA07070 for current-outgoing; Tue, 11 Jun 1996 08:23:34 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA06959 for ; Tue, 11 Jun 1996 08:22:36 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id WAA06298 for current@freebsd.org; Tue, 11 Jun 1996 22:21:46 +0700 Received: by itfs.nsk.su; Tue, 11 Jun 96 22:11:43 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.6.12/8.6.12) id WAA14182; Tue, 11 Jun 1996 22:07:34 +0700 From: nnd@itfs.nsk.su (Nickolay N. Dudorov) To: current@freebsd.org Subject: Re: CLOCK stuff at bootup Message-ID: References: <199606111346.XAA00739@godzilla.zeta.org.au> Date: Tue, 11 Jun 1996 15:07:25 GMT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans (bde@zeta.org.au) wrote: > >> It's not in the default kernel (GENERIC or 2.1). > > >It's been in all the default kernels in -current since 5/1. > > The debugging CLOCK options are in neither GENERIC nor LINT. I am very sorry, but call to 'calibrate_clocks' in i386/isa/clock.c is not conditionalized by any CLOCK options in CURRENT (and there is NO possibility to switch it off by ANY option ) - so we have this useless messages in each and every kernel configuration. N.Dudorov From owner-freebsd-current Tue Jun 11 09:01:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09325 for current-outgoing; Tue, 11 Jun 1996 09:01:34 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09317 for ; Tue, 11 Jun 1996 09:01:27 -0700 (PDT) Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with SMTP id JAA13586 for ; Tue, 11 Jun 1996 09:01:13 -0700 (PDT) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.6.11/8.6.12) with ESMTP id KAA25972; Tue, 11 Jun 1996 10:56:07 -0500 Received: from localhost by solaria.sol.net (8.5/8.5) id KAA05006; Tue, 11 Jun 1996 10:58:02 -0500 From: Joe Greco Message-Id: <199606111558.KAA05006@solaria.sol.net> Subject: Would somebody please...! To: current@freebsd.org Date: Tue, 11 Jun 96 10:57:59 CDT Cc: jkh@time.cdrom.com X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am getting a little tired of submitting this and having no one take any action. The following patches "fix" several system utilities to correctly report disk statistics for drives with "longer-than-usual" (4 char) names. It is mostly cosmetic. They should be relatively transparent. They are relative to 2.1R but it doesn't look like much has changed lately. Could somebody please take the lead on getting these committed so that I can rest assured that my hacking efforts have done the general population some good! Thanks, ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 *** usr.sbin/iostat/iostat.c.fcs Mon May 29 22:47:45 1995 --- usr.sbin/iostat/iostat.c Wed Nov 29 11:12:03 1995 *************** *** 334,340 **** (void)printf(" tty"); for (i = 0; i < dk_ndrive; i++) if (dr_select[i]) ! (void)printf(" %3.3s ", dr_name[i]); (void)printf(" cpu\n tin tout"); for (i = 0; i < dk_ndrive; i++) if (dr_select[i]) --- 334,340 ---- (void)printf(" tty"); for (i = 0; i < dk_ndrive; i++) if (dr_select[i]) ! (void)printf(" %4.4s ", dr_name[i]); (void)printf(" cpu\n tin tout"); for (i = 0; i < dk_ndrive; i++) if (dr_select[i]) *************** *** 351,357 **** for (dn = 0; dn < dk_ndrive; ++dn) { if (!dr_select[dn]) continue; ! words = cur.dk_wds[dn] * 32; /* words xfer'd */ (void)printf("%4.0f", /* sectors */ words / (DEV_BSIZE / 2) / etime); --- 351,357 ---- for (dn = 0; dn < dk_ndrive; ++dn) { if (!dr_select[dn]) continue; ! words = (double)cur.dk_wds[dn] * 32; /* words xfer'd */ (void)printf("%4.0f", /* sectors */ words / (DEV_BSIZE / 2) / etime); *** usr.bin/systat/systat.1.fcs Sat Dec 3 04:06:37 1994 --- usr.bin/systat/systat.1 Tue Nov 28 20:34:38 1995 *************** *** 229,235 **** of kilobyte blocks transferred per second averaged over the refresh period of the display (by default, five seconds). For some disks it also reports the average milliseconds per seek. ! Note that the system only keeps statistics on at most four disks. .Pp Below the disk display is a list of the average number of processes (over the last refresh interval) --- 229,237 ---- of kilobyte blocks transferred per second averaged over the refresh period of the display (by default, five seconds). For some disks it also reports the average milliseconds per seek. ! Note that the system only keeps statistics on at most eight disks ! (this is controlled by the constant DK_NDRIVE in /sys/dkstat.h as ! a kernel compile-time constant). .Pp Below the disk display is a list of the average number of processes (over the last refresh interval) *** usr.bin/systat/vmstat.c.fcs Sat Aug 26 05:10:23 1995 --- usr.bin/systat/vmstat.c Tue Nov 28 20:25:21 1995 *************** *** 325,331 **** for (i = 0; i < dk_ndrive && j < MAXDRIVES; i++) if (dk_select[i]) { mvprintw(DISKROW, DISKCOL + 5 + 5 * j, ! " %3.3s", dr_name[j]); j++; } for (i = 0; i < nintr; i++) { --- 325,331 ---- for (i = 0; i < dk_ndrive && j < MAXDRIVES; i++) if (dk_select[i]) { mvprintw(DISKROW, DISKCOL + 5 + 5 * j, ! " %4.4s", dr_name[j]); j++; } for (i = 0; i < nintr; i++) { *************** *** 471,477 **** for (i = 0, c = 0; i < dk_ndrive && c < MAXDRIVES; i++) if (dk_select[i]) { mvprintw(DISKROW, DISKCOL + 5 + 5 * c, ! " %3.3s", dr_name[i]); dinfo(i, ++c); } putint(s.nchcount, NAMEIROW + 2, NAMEICOL, 9); --- 471,477 ---- for (i = 0, c = 0; i < dk_ndrive && c < MAXDRIVES; i++) if (dk_select[i]) { mvprintw(DISKROW, DISKCOL + 5 + 5 * c, ! " %4.4s", dr_name[i]); dinfo(i, ++c); } putint(s.nchcount, NAMEIROW + 2, NAMEICOL, 9); *** usr.bin/systat/iostat.c.fcs Sat Dec 3 04:06:26 1994 --- usr.bin/systat/iostat.c Tue Nov 28 12:47:20 1995 *************** *** 199,209 **** */ if (linesperregion < 3) linesperregion = 3; ! col = 0; for (i = 0; i < dk_ndrive; i++) if (dk_select[i] && dk_mspw[i] != 0.0) { if (col + COLWIDTH >= wnd->maxx - INSET) { ! col = 0, row += linesperregion + 1; if (row > wnd->maxy - (linesperregion + 1)) break; } --- 199,209 ---- */ if (linesperregion < 3) linesperregion = 3; ! col = INSET; for (i = 0; i < dk_ndrive; i++) if (dk_select[i] && dk_mspw[i] != 0.0) { if (col + COLWIDTH >= wnd->maxx - INSET) { ! col = INSET, row += linesperregion + 1; if (row > wnd->maxy - (linesperregion + 1)) break; } *************** *** 229,235 **** if (dk_select[i] && dk_mspw[i] != 0.0) { if (row > wnd->maxy - linesperregion) break; ! mvwprintw(wnd, row++, 0, "%3.3s bps|", dr_name[i]); mvwaddstr(wnd, row++, 0, " tps|"); if (msps) mvwaddstr(wnd, row++, 0, " msps|"); --- 229,235 ---- if (dk_select[i] && dk_mspw[i] != 0.0) { if (row > wnd->maxy - linesperregion) break; ! mvwprintw(wnd, row++, 0, "%-4.4s bps|", dr_name[i]); mvwaddstr(wnd, row++, 0, " tps|"); if (msps) mvwaddstr(wnd, row++, 0, " msps|"); *************** *** 271,285 **** } return; } ! col = 0; wmove(wnd, row + linesperregion, 0); wdeleteln(wnd); wmove(wnd, row + 3, 0); winsertln(wnd); for (i = 0; i < dk_ndrive; i++) if (dk_select[i] && dk_mspw[i] != 0.0) { ! if (col + COLWIDTH >= wnd->maxx) { ! col = 0, row += linesperregion + 1; if (row > wnd->maxy - (linesperregion + 1)) break; wmove(wnd, row + linesperregion, 0); --- 271,285 ---- } return; } ! col = INSET; wmove(wnd, row + linesperregion, 0); wdeleteln(wnd); wmove(wnd, row + 3, 0); winsertln(wnd); for (i = 0; i < dk_ndrive; i++) if (dk_select[i] && dk_mspw[i] != 0.0) { ! if (col + COLWIDTH >= wnd->maxx - INSET) { ! col = INSET, row += linesperregion + 1; if (row > wnd->maxy - (linesperregion + 1)) break; wmove(wnd, row + linesperregion, 0); -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Tue Jun 11 09:55:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA11720 for current-outgoing; Tue, 11 Jun 1996 09:55:15 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA11715 for ; Tue, 11 Jun 1996 09:55:13 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA24889; Tue, 11 Jun 1996 12:53:41 -0400 Date: Tue, 11 Jun 1996 12:53:41 -0400 From: Garrett Wollman Message-Id: <9606111653.AA24889@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: current@freebsd.org Subject: New bug in de driver caused by recent changes? In-Reply-To: <199606110006.RAA05112@phaeton.artisoft.com> References: <199606110006.RAA05112@phaeton.artisoft.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I have gotten several errors of the type: > de0: receiver: CRC error I have had this happen when trying to receive at high rates on a machine connected over a crossover wire to an i82557 NIC in a router with a broken Orion chipset. That is to say: +-------+ hub +-----------------+ +-------+ |sender +-------+ de0 router fxp0 +-------+ rcvr + +-------+ +-----------------+ xover +-------+ ...when forwarding at high rates, the de0 interface in `rcvr' reports CRC errors. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Jun 11 11:05:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16198 for current-outgoing; Tue, 11 Jun 1996 11:05:53 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA16155 for ; Tue, 11 Jun 1996 11:05:20 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with SMTP id LAA16189 for ; Tue, 11 Jun 1996 11:05:18 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA13054; Tue, 11 Jun 1996 12:02:39 -0600 Date: Tue, 11 Jun 1996 12:02:39 -0600 From: Nate Williams Message-Id: <199606111802.MAA13054@rocky.sri.MT.net> To: Bruce Evans Cc: nate@sri.MT.net, current@FreeBSD.ORG Subject: Re: CLOCK stuff at bootup In-Reply-To: <199606111346.XAA00739@godzilla.zeta.org.au> References: <199606111346.XAA00739@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > >> It's not in the default kernel (GENERIC or 2.1). > > >It's been in all the default kernels in -current since 5/1. > > The debugging CLOCK options are in neither GENERIC nor LINT. Explain this to me then. FreeBSD 2.2-CURRENT #15: Fri Jun 7 23:00:27 MDT 1996 nate@moth.sri.MT.net:/usr/src/sys/compile/DMOTH Calibrating clock(s) relative to mc146818A clock ... i586 clock: 99467141 Hz, i8 254 clock: 1193106 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method i586 clock: 0 Hz Looks like it the default. Nate From owner-freebsd-current Tue Jun 11 13:13:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22823 for current-outgoing; Tue, 11 Jun 1996 13:13:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22806 for ; Tue, 11 Jun 1996 13:13:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA04375; Tue, 11 Jun 1996 13:13:11 -0700 From: Terry Lambert Message-Id: <199606112013.NAA04375@phaeton.artisoft.com> Subject: Re: New bug in de driver caused by recent changes? To: wollman@lcs.mit.edu (Garrett Wollman) Date: Tue, 11 Jun 1996 13:13:11 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <9606111653.AA24889@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jun 11, 96 12:53:41 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have gotten several errors of the type: > > > > de0: receiver: CRC error > > I have had this happen when trying to receive at high rates on a > machine connected over a crossover wire to an i82557 NIC in a router > with a broken Orion chipset. > > That is to say: > > +-------+ hub +-----------------+ +-------+ > |sender +-------+ de0 router fxp0 +-------+ rcvr + > +-------+ +-----------------+ xover +-------+ > > ...when forwarding at high rates, the de0 interface in `rcvr' reports > CRC errors. OK, more info: Windows95 Telnet -> FreeBSD Box rlogin -> SPARCStation 1+ ^ | errors on this box Upgrade was from January SNAP to -current. So there's no Orion chipset involved. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jun 11 14:05:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA27646 for current-outgoing; Tue, 11 Jun 1996 14:05:46 -0700 (PDT) Received: from DeepCore.dk (aalb21.pip.dknet.dk [194.192.0.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA27637; Tue, 11 Jun 1996 14:05:33 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.5/8.7.3) id XAA19193; Tue, 11 Jun 1996 23:04:17 +0200 (MET DST) Message-Id: <199606112104.XAA19193@DeepCore.dk> Subject: Re: As of 960608, routed now complains bitterly.. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 11 Jun 1996 23:04:16 +0200 (MET DST) Cc: wollman@lcs.mit.edu, jkh@freefall.freebsd.org, current@freefall.freebsd.org In-Reply-To: <1715.834275627@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 8, 96 04:13:47 pm" From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > This means that your netmasks are not configured correctly, either on > > the host, or a router to that network, or both. It happens when > > Hmmm. There are two hosts on this wire, one is the complaining host > and the other is the gateway. Here are the interfaces for each: I get funny messages from the new routed as well: ... interface ed0 to 10.0.0.3 restored allthough everything is working just fine :( Allso the kernel has begun to spit out: arpresolve: can't allocate llinfo for 10.0.0.3 But if I go back to the old routed everything still works fine, but I don't get these annoying complaints... > So now where's my problem? :-) And where is mine (execpt for the new routed)... This is rather irritating, and will propably cause a few /var's to fill up :( -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Tue Jun 11 15:38:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03654 for current-outgoing; Tue, 11 Jun 1996 15:38:06 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA03649 for ; Tue, 11 Jun 1996 15:38:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id PAA02361; Tue, 11 Jun 1996 15:36:49 -0700 (PDT) Message-Id: <199606112236.PAA02361@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: Brian Tao cc: Matt Day , freebsd-current@freebsd.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-reply-to: Your message of "Tue, 11 Jun 1996 10:31:02 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 11 Jun 1996 15:36:49 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Mon, 10 Jun 1996, David Greenman wrote: >> >> Thanks for the patch, Matt. > > Any caveats to running a 2.2-960501-SNAP kernel with the patch? >It applies cleanly enough. I've rebuilt emacs here anyway (didn't >expect a patch so quickly!), in case it was tickling something in the >2.1 libraries on a 2.2 system. The patch is okay, but it's incomplete. The same problem exists in the other filesystems, too. I spent some time last night making similar changes to the other filesystems and I should have this ready to commit in a day or so. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Jun 11 16:02:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA05123 for current-outgoing; Tue, 11 Jun 1996 16:02:56 -0700 (PDT) Received: from sting.artisoft.com (sting.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA05118 for ; Tue, 11 Jun 1996 16:02:52 -0700 (PDT) Received: (from mday@localhost) by sting.artisoft.com (8.6.12/8.6.12) id QAA28053; Tue, 11 Jun 1996 16:02:21 -0700 Date: Tue, 11 Jun 1996 16:02:21 -0700 From: Matt Day Message-Id: <199606112302.QAA28053@sting.artisoft.com> To: freebsd-current@FreeBSD.org, taob@io.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brian Tao wrote: > Any caveats to running a 2.2-960501-SNAP kernel with the patch? > It applies cleanly enough. [..] The patch should work fine on 2.2-960501-SNAP. But, out of curiousity I was just taking another closer look at your panic log and now I'm pretty sure that the patch I sent yesterday will not fix your panic (though I'm still convinced that it fixes another panic). >From what I can tell, your panic log says that your system was in fsync() when it tried to access memory address 0x18. This suggests that some structure pointer was NULL and it tried to access the element at offset 0x18 in that structure. In fsync() there are two places where this can occur: if vp was NULL then it would access address 0x18 when it fetched vp->v_mount, and if vp->v_mount was NULL then it would access address 0x18 when it fetched vp->v_mount->mnt_flag. Since other elements of vp are accessed before the vp->v_mount access in fsync(), I think what probably happened is vp->v_mount was NULL. (Line 1866 of kern/vfs_syscalls.c) So, it appears that there is some way for getvnode() to return a kernel file descriptor whose f_data is a vnode that has a NULL v_mount. Unfortunately, I can't come up with a scenario where the bug I reported yesterday can cause this to happen. I'll try to track down this different bug. Sorry for the false alarm on yesterday's patch. I saw "NULL dereference" and "fsync" and I immediately thought of that fsync dereferencing NULL bug... but that was ffs_fsync(), not plain old fsync()! I think appropriate punishment for my error would be to find this other bug. :-) Matt Day From owner-freebsd-current Tue Jun 11 16:44:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08145 for current-outgoing; Tue, 11 Jun 1996 16:44:20 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA08140 for ; Tue, 11 Jun 1996 16:44:17 -0700 (PDT) Received: from socrate (ts1port11d.masternet.it [194.184.65.33]) by masternet.it (8.6.12/8.6.9) with SMTP id AAA09160 for ; Wed, 12 Jun 1996 00:42:27 +0200 Message-ID: <31BE0AEB.41C67EA6@masternet.it> Date: Wed, 12 Jun 1996 02:10:19 +0200 From: Beck Peccoz Amedeo X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: 3Com 590 not seen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Today I've been trying to have a 3Com 590 pci ether adapter working on a newly installed FreeBSD server, but it didn't work and I had to put an old and SLOW NE2000 to let the server work. In the kernel config I added the line "options vx0" as suggested from the LINT, but when starting up, the kernel didn't notice the board, so I tried to contigure the kernel, i.e. type a "-c" at the boot prompt, but in the network section only the usual serial and parallel port drivers appeared. The hardware is known to work perfectly as I tried it as a client under DOS. I'm running Snapshot with ctm 1873. What's wrong? -- Beck-Peccoz Amedeo GEA Software S.r.l. Via Deffeyes, 1 11025 Gressoney Saint Jean (AO) ITALY Tel. ++39-125-366302 Fax. ++39-125-366415 From owner-freebsd-current Tue Jun 11 20:31:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22093 for current-outgoing; Tue, 11 Jun 1996 20:31:54 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22086 for ; Tue, 11 Jun 1996 20:31:51 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id UAA24737 for ; Tue, 11 Jun 1996 20:31:37 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id XAA10743; Tue, 11 Jun 1996 23:27:16 -0400 (EDT) Date: Tue, 11 Jun 1996 23:28:25 -0400 (EDT) From: Brian Tao To: Matt Day cc: freebsd-current@FreeBSD.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-Reply-To: <199606112302.QAA28053@sting.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 11 Jun 1996, Matt Day wrote: > > Sorry for the false alarm on yesterday's patch. I saw "NULL > dereference" and "fsync" and I immediately thought of that fsync > dereferencing NULL bug... but that was ffs_fsync(), not plain old > fsync()! I think appropriate punishment for my error would be to > find this other bug. :-) Could you, pretty please? ;-) I've built emacs 19.31 linked with the 2.2 libs to see if that was a problem, but I just saw one of the shell servers die again tonight. :( I'm going to try your patch anyway to see how it goes. Thanks. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xf012afc3 stack pointer = 0x10:0xefbfff2c frame pointer = 0x10:0xefbfff58 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 = 5894 (emacs) interrupt mask = panic: page fault syncing disks... 26 26 24 13 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Tue Jun 11 22:02:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA26932 for current-outgoing; Tue, 11 Jun 1996 22:02:15 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA26927 for ; Tue, 11 Jun 1996 22:02:12 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id BAA11563 for ; Wed, 12 Jun 1996 01:00:48 -0400 (EDT) Date: Wed, 12 Jun 1996 01:01:58 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L Subject: syslogd can't create /dev/log? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's another odd problem with 2.2-960501-SNAP... I can't seem to get syslogd to run: # syslogd -d syslogd: cannot create /dev/log: Address already in use logmsg: pri 53, flags 4, from zap, msg syslogd: cannot create /dev/log: Address already in use Logging to CONSOLE /dev/console cannot create /dev/log (0) One one machine, the mod date on /var/log/messages is 2:00 am one night ago. At the same time, newsyslog reported this via cron: > newsyslog: preposterous process number: 0 > newsyslog: preposterous process number: 0 > newsyslog: preposterous process number: 0 That was caused by /var/run/syslog.pid not being there (and syslog_pid is initialized to 0 in newsyslog.c). On another machine, the logs stopped at 8:13pm later that day (when newsyslog normally does not run). The last few messages recorded in each aren't very helpful (usual stuff about people logging in or sendmail-related stuff). I'm not sure what the first error line from syslogd means... fstat doesn't show anything holding that inode open, and netstat doesn't show anyone listening on port 514/udp. /dev/log is there, as is /dev/klog. The weird thing is that a reboot doesn't solve the problem, and it *was* running just fine for a little while. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Tue Jun 11 23:06:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA01217 for current-outgoing; Tue, 11 Jun 1996 23:06:28 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA01212 for ; Tue, 11 Jun 1996 23:06:26 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id CAA12121 for ; Wed, 12 Jun 1996 02:05:05 -0400 (EDT) Date: Wed, 12 Jun 1996 02:06:15 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Re: syslogd can't create /dev/log? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Jun 1996, Brian Tao wrote: > > Here's another odd problem with 2.2-960501-SNAP... I can't seem to > get syslogd to run: Someone shoot me or pass the dunce cap or something... chalk this one up to operator error. :( > syslogd: cannot create /dev/log: Address already in use Of course, syslogd creates the /dev/log socket when it starts up, and destroys it when it shuts down. /dev/log has been hanging around because /dev here is flagged sappnd. kern.securelevel is at 1, so I can't remove sappnd without dropping into single user first. Argh! I didn't think anything had to be deleted out of /dev... wouldn't /dev/log be better off in /var/run or something like that? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Tue Jun 11 23:22:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA01880 for current-outgoing; Tue, 11 Jun 1996 23:22:25 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA01853 for ; Tue, 11 Jun 1996 23:21:51 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA27600; Wed, 12 Jun 1996 08:20:45 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA09023; Wed, 12 Jun 1996 08:20:45 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA20602; Wed, 12 Jun 1996 08:00:54 +0200 (MET DST) From: J Wunsch Message-Id: <199606120600.IAA20602@uriah.heep.sax.de> Subject: Re: 3Com 590 not seen To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 12 Jun 1996 08:00:52 +0200 (MET DST) Cc: gea@masternet.it (Beck Peccoz Amedeo) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <31BE0AEB.41C67EA6@masternet.it> from Beck Peccoz Amedeo at "Jun 12, 96 02:10:19 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Beck Peccoz Amedeo wrote: > In the kernel config I added the line "options vx0" as suggested > from the LINT, but when starting up, the kernel didn't notice > the board, so I tried to contigure the kernel, i.e. type a "-c" > at the boot prompt, but in the network section only the usual > serial and parallel port drivers appeared. Only ISA drivers need to be configured with boot -c. > I'm running Snapshot with ctm 1873. What's wrong? Well, vx0 is a device, not an option. ;) device vx0 -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jun 12 00:08:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04414 for current-outgoing; Wed, 12 Jun 1996 00:08:15 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA04409 for ; Wed, 12 Jun 1996 00:08:13 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA28631 for ; Wed, 12 Jun 1996 00:08:10 -0700 Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id IAA29822; Wed, 12 Jun 1996 08:06:28 +0100 (BST) To: Brian Tao cc: FREEBSD-CURRENT-L From: "Gary Palmer" Subject: Re: syslogd can't create /dev/log? In-reply-to: Your message of "Wed, 12 Jun 1996 02:06:15 EDT." Date: Wed, 12 Jun 1996 08:06:27 +0100 Message-ID: <29820.834563187@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Tao wrote in message ID : > I didn't think anything had to be deleted out of /dev... wouldn't > /dev/log be better off in /var/run or something like that? Thats the general consensus these days ... we need a symlink from /dev/log to /var/run/log anyhow, so I think it's being delayed until after devfs is deployed (with symlink support). Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Wed Jun 12 03:17:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA18333 for current-outgoing; Wed, 12 Jun 1996 03:17:33 -0700 (PDT) Received: from shadows.aeon.net ([194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA18262 for ; Wed, 12 Jun 1996 03:17:20 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id NAA13715 for freebsd-current@freebsd.org; Wed, 12 Jun 1996 13:12:37 +0300 (EET DST) Message-Id: <199606121012.NAA13715@shadows.aeon.net> Subject: vm_fault.c probs To: freebsd-current@freebsd.org Date: Wed, 12 Jun 1996 13:12:37 +0300 (EET DST) From: freebsd@aeon.net (Mr Operating System) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=Latin-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi... =) since i just did subscribe, i might as something that's been answered... someone direct me to the right direction then... i runcurrent, and have been having probs with the vm/vm_fault.c or probably it's not that file, but there the compiling hangs... version is 1.49, dated 8th jun, 6:48 (same prob with 1.48 too) error: ../../vm/vm_fault.c: In function 'vm_fault': ../../vm/vm_fault.c:332: structure has no member named 'behaviour' ../../vm/vm_fault.c:332: 'OBJ_RANDOM' undeclared (first use this function) ../../vm/vm_fault.c:332: (Each undeclared identifiers is reported only once ../../vm/vm_fault.c:332: for eachfunction it appears in.) ../../vm/vm_fault.c:338: structure has no member named 'behaviour' ../../vm/vm_fault.c:338: 'OBJ_SEQUENTIAL' undeclared (first use this function) *** Error code 1 Stop. shadows# my slightly limited C knowledge hints me where the problem is, and i have attemted few times to get rid of that... but since i dont have time to read all the files needed to understand what the programmer were after, i found it more useful to ask if someone has done it right already... i believe i did 'make world' in three weeks ago, actually, last time i seem to have compiled kernel successfully were apr 30, oops... anyway, i have updated the /usr/share/mk files to match the latest, could the problem be in libraries? that would be my best guess... (yes, i'm lazy, i could 'make world', but since the machine's at work, and i cant compile overnite, it would take bit too long...) mickey From owner-freebsd-current Wed Jun 12 05:13:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA28440 for current-outgoing; Wed, 12 Jun 1996 05:13:03 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA28434 for ; Wed, 12 Jun 1996 05:13:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id FAA00941; Wed, 12 Jun 1996 05:13:06 -0700 (PDT) Message-Id: <199606121213.FAA00941@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: Brian Tao cc: Matt Day , freebsd-current@FreeBSD.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-reply-to: Your message of "Tue, 11 Jun 1996 23:28:25 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 12 Jun 1996 05:13:05 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >On Tue, 11 Jun 1996, Matt Day wrote: >> >> Sorry for the false alarm on yesterday's patch. I saw "NULL >> dereference" and "fsync" and I immediately thought of that fsync >> dereferencing NULL bug... but that was ffs_fsync(), not plain old >> fsync()! I think appropriate punishment for my error would be to >> find this other bug. :-) > > Could you, pretty please? ;-) I've built emacs 19.31 linked with >the 2.2 libs to see if that was a problem, but I just saw one of the >shell servers die again tonight. :( I'm going to try your patch >anyway to see how it goes. Thanks. > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x18 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xf012afc3 Since this is -current, I would strongly suggest SUPing the latest stuff. There were a great deal of serious VM system bugs in the 0501 snapshot that have just recently been worked out. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Jun 12 05:34:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA29036 for current-outgoing; Wed, 12 Jun 1996 05:34:01 -0700 (PDT) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA29029 for ; Wed, 12 Jun 1996 05:33:41 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de) by mail.rwth-aachen.de (PMDF V5.0-4 #13110) id <01I5TMPIEHKG001W5R@mail.rwth-aachen.de> for freebsd-current@freefall.FreeBSD.org; Wed, 12 Jun 1996 13:23:57 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA04885 for freebsd-current@freefall.cdrom.com; Wed, 12 Jun 1996 13:32:13 +0200 Date: Wed, 12 Jun 1996 13:32:13 +0200 From: "Christoph P. Kukulies" Subject: linux emu (libXpm problem) To: freebsd-current@freefall.FreeBSD.org Message-id: <199606121132.NAA04885@gilberto.physik.rwth-aachen.de> Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I tried to run a linux binary and I'm getting the following error: miles# /compat/linux/usr/bin/ldd Xfile Xfile: '/lib/libXpm.so.4' is not an ELF file libXpm.so.4 => not found libXt.so.6 => /usr/X11R6/lib/libXt.so.6.0 libXext.so.6 => /usr/X11R6/lib/libXext.so.6.0 libX11.so.6 => /usr/X11R6/lib/libX11.so.6.0 libm.so.5 => /lib/libm.so.5.0.0 libcursesX.so.1 => not found libc.so.5 => /lib/libc.so.5.0.9 libSM.so.6 => /usr/X11R6/lib/libSM.so.6.0 libICE.so.6 => /usr/X11R6/lib/libICE.so.6.0 miles# I installed linux_lib freshly from ports-current on a -current system. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Jun 12 13:05:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27357 for current-outgoing; Wed, 12 Jun 1996 13:05:46 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA27341 for ; Wed, 12 Jun 1996 13:05:39 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA13087 for current@freebsd.org; Wed, 12 Jun 1996 16:04:13 -0400 From: Bill Paul Message-Id: <199606122004.QAA13087@skynet.ctr.columbia.edu> Subject: Has anyone really tested NFS_NOSERVER? To: current@freebsd.org Date: Wed, 12 Jun 1996 16:04:11 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I finally got 2.2-current bootstrapped on my machine at work. (There's still a problem with the documentation section blowing up due to it not baing able to find /usr/share/dist/eign (whatever that is) but I got around this by disabling the 'doc' target for now.) Anyway. I built a GENERIC kernel and fired up the machine in diskless mode (this way I can boot either 2.1 from the internal disk or 2.2 via NFS). After a little bit of fiddling with the netboot configuration parameters, I got everything to work just fine. No worries: I even used this system to build another kernel, identical to GENERIC except with 'options NFS_NOSERVER' added. The new kernel with NFS_NOSERVER gives me nothing but grief, however. It will always eventually wedge, though not in the same place. Sometimes it will wedge before it finishes running the rc scripts. Sometimes it will finish booting sucessfully, but wedge just after I get logged in. Debugging is tricky: since the whole system is mounted via NFS, nothing will work once it gets stuck. Scanning with tcpdump from another machine on the same subnet shows that all NFS traffic between the FreeBSD machine and the server (which is a Sun SPARC IPX with SunOS 4.1.3) just stops. There aren't any retransmissions or anything. I can still ping the FreeBSD machine though. I haven't had a chance to make a kernel with DDB yet. Hardware is as follows: AMD 386DX/40 CPU (no math coprocessor) 8 MB RAM 3Com 3c503 (8-bit) ethernet adapter Diamond Speedstar 3.01 SVGA adapter (ET4000) 1 no-name IDE controller (primary) 1 Western Digital 40MB disk (master) 1 Quantum IDE 50 MB disk (slave) 2 serial ports (16450) 1 parallel port I'm using the entire WD disk for swap space. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= License error: The license for this .sig file has expired. You must obtain a new license key before any more witty phrases will appear in this space. ============================================================================= From owner-freebsd-current Wed Jun 12 13:38:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA01048 for current-outgoing; Wed, 12 Jun 1996 13:38:51 -0700 (PDT) Received: from critter.tfs.com ([140.145.16.108]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA01041; Wed, 12 Jun 1996 13:38:48 -0700 (PDT) Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id NAA02384; Wed, 12 Jun 1996 13:38:17 -0700 (PDT) To: Bill Paul cc: current@freebsd.org Subject: Re: Has anyone really tested NFS_NOSERVER? In-reply-to: Your message of "Wed, 12 Jun 1996 16:04:11 EDT." <199606122004.QAA13087@skynet.ctr.columbia.edu> Date: Wed, 12 Jun 1996 13:38:17 -0700 Message-ID: <2382.834611897@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes, I did. worked in my env, but as far as I can tell the problem seems to be timer related, and maybe I had too much luck in my test. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Jun 12 16:15:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA13440 for current-outgoing; Wed, 12 Jun 1996 16:15:17 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA13433 for ; Wed, 12 Jun 1996 16:15:13 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id SAA01188 for current@freebsd.org; Wed, 12 Jun 1996 18:15:09 -0500 (EST) From: "John S. Dyson" Message-Id: <199606122315.SAA01188@dyson.iquest.net> Subject: Suggestion to update your kernel To: current@freebsd.org Date: Wed, 12 Jun 1996 18:15:08 -0500 (EST) X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just FYI, I suggest that if you are running a -current kernel from between 2-3weeks ago to yesterday, upgrade it. There was a serious bug in the page stats that might cause very poor system performance or even system hangs on small memory configs. John From owner-freebsd-current Wed Jun 12 21:53:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12829 for current-outgoing; Wed, 12 Jun 1996 21:53:30 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA12820; Wed, 12 Jun 1996 21:53:28 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id AAA23221; Thu, 13 Jun 1996 00:51:59 -0400 (EDT) Date: Thu, 13 Jun 1996 00:53:10 -0400 (EDT) From: Brian Tao To: Gary Palmer cc: FREEBSD-CURRENT-L Subject: Re: syslogd can't create /dev/log? In-Reply-To: <29820.834563187@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Jun 1996, Gary Palmer wrote: > > Thats the general consensus these days ... we need a symlink from > /dev/log to /var/run/log anyhow, so I think it's being delayed until > after devfs is deployed (with symlink support). That would be good... I like to think of / and /usr as conceptually "read-only" filesystems (/var, /usr/local, /home and /tmp are on separate filesystems), so I didn't anticipate any problems making most of the important directories append-only. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Thu Jun 13 01:25:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA03357 for current-outgoing; Thu, 13 Jun 1996 01:25:43 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA03341 for ; Thu, 13 Jun 1996 01:25:38 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id RAA28555 for ; Thu, 13 Jun 1996 17:25:34 +0900 (JST) Date: Thu, 13 Jun 1996 17:25:34 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG Subject: opt_ipfw.h Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk make obj depend all fails on building the ip firewall stuff. ip_fw.c needs opt_ipfw.h From owner-freebsd-current Thu Jun 13 01:40:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04599 for current-outgoing; Thu, 13 Jun 1996 01:40:07 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA04518 for ; Thu, 13 Jun 1996 01:39:56 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id JAA21002; Thu, 13 Jun 1996 09:38:38 +0100 (BST) To: Michael Hancock cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: opt_ipfw.h In-reply-to: Your message of "Thu, 13 Jun 1996 17:25:34 +0900." Date: Thu, 13 Jun 1996 09:38:34 +0100 Message-ID: <21000.834655114@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Hancock wrote in message ID : > make obj depend all > > fails on building the ip firewall stuff. > > ip_fw.c needs opt_ipfw.h Did you re-run config? It was added to /sys/conf/options at the same time the #include was added to /sys/netinet/ip_fw.c (and /sys/netinet/ip_input.c). You should run `config -n CONFIGNAME' and see if that generates an opt_ipfw.h file for you... Certainly it worked here. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Thu Jun 13 02:03:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07527 for current-outgoing; Thu, 13 Jun 1996 02:03:40 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA07517 for ; Thu, 13 Jun 1996 02:03:35 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id LAA28416; Thu, 13 Jun 1996 11:03:32 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id LAA29289; Thu, 13 Jun 1996 11:02:54 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.4/keltia-uucp-2.8) id KAA08335; Thu, 13 Jun 1996 10:56:58 +0200 (MET DST) From: Ollivier Robert Message-Id: <199606130856.KAA08335@keltia.freenix.fr> Subject: Re: opt_ipfw.h To: michaelh@cet.co.jp (Michael Hancock) Date: Thu, 13 Jun 1996 10:56:57 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from Michael Hancock at "Jun 13, 96 05:25:34 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#2103 X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that Michael Hancock said: > fails on building the ip firewall stuff. > > ip_fw.c needs opt_ipfw.h Re-run config (and read cvs-all mailing list :-)) and make. The opt_ipfw.h should be created by config(8) now. gpalmer 96/06/12 12:34:35 Modified: sys/conf options sys/netinet ip_fw.c ip_input.c Log: Convert ipfw to use opt_ipfw.h Revision Changes Path 1.14 +4 -2 src/sys/conf/options 1.38 +4 -1 src/sys/netinet/ip_fw.c 1.44 +3 -1 src/sys/netinet/ip_input.c -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #10: Tue Jun 11 13:36:57 MET DST 1996 From owner-freebsd-current Thu Jun 13 02:30:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA09145 for current-outgoing; Thu, 13 Jun 1996 02:30:57 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA09139 for ; Thu, 13 Jun 1996 02:30:53 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id SAA28875 for ; Thu, 13 Jun 1996 18:30:49 +0900 (JST) Date: Thu, 13 Jun 1996 18:30:49 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG Subject: Re: opt_ipfw.h In-Reply-To: <21000.834655114@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 13 Jun 1996, Gary Palmer wrote: > > ip_fw.c needs opt_ipfw.h > > Did you re-run config? It was added to /sys/conf/options at the same > time the #include was added to /sys/netinet/ip_fw.c (and > /sys/netinet/ip_input.c). You should run `config -n CONFIGNAME' and > see if that generates an opt_ipfw.h file for you... Certainly it > worked here. Oops, I missed it in the cvs mailing. -mh From owner-freebsd-current Thu Jun 13 02:54:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA10553 for current-outgoing; Thu, 13 Jun 1996 02:54:10 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA10546 for ; Thu, 13 Jun 1996 02:54:06 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id LAA28600 for ; Thu, 13 Jun 1996 11:54:03 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id LAA30485 for freebsd-current@FreeBSD.ORG; Thu, 13 Jun 1996 11:53:13 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.4/keltia-uucp-2.8) id LAA15818 for freebsd-current@FreeBSD.ORG; Thu, 13 Jun 1996 11:50:50 +0200 (MET DST) From: Ollivier Robert Message-Id: <199606130950.LAA15818@keltia.freenix.fr> Subject: #include opt_ipfw.h problem for lkm To: freebsd-current@freebsd.org (FreeBSD Current Users' list) Date: Thu, 13 Jun 1996 11:50:49 +0200 (MET DST) X-Operating-System: FreeBSD 2.2-CURRENT ctm#2103 X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk sys/netinet/ip_fw.c includes "opt_ipfw.h" when compiling the kernel (which is fine) but includes it also when compiling as lkm (which is bad). That breaks "make depend" and "make world". Index: sys/netinet/ip_fw.c =================================================================== RCS file: /spare/FreeBSD-current/src/sys/netinet/ip_fw.c,v retrieving revision 1.38 diff -u -2 -u -r1.38 ip_fw.c --- ip_fw.c 1996/06/12 19:34:33 1.38 +++ ip_fw.c 1996/06/13 09:43:12 @@ -20,5 +20,7 @@ */ +#ifndef ACTUALLY_LKM_NOT_KERNEL #include "opt_ipfw.h" +#endif #include -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #10: Tue Jun 11 13:36:57 MET DST 1996 From owner-freebsd-current Thu Jun 13 08:54:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02400 for current-outgoing; Thu, 13 Jun 1996 08:54:12 -0700 (PDT) Received: from rapture.cyberflunk.com (pluvius@rapture.cyberflunk.com [199.242.19.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02395 for ; Thu, 13 Jun 1996 08:54:11 -0700 (PDT) Received: from localhost (pluvius@localhost) by rapture.cyberflunk.com (8.7.5/8.7.3) with SMTP id IAA07197 for ; Thu, 13 Jun 1996 08:48:16 -0700 (PDT) Date: Thu, 13 Jun 1996 08:48:16 -0700 (PDT) From: pluvius To: current@freefall.freebsd.org Subject: Re: 3Com 590 not seen In-Reply-To: <199606130954.CAA10575@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If it counts for anything, i had some pretty wierd behaviour with a 3c590 .. it was in the 960601-snap, when using the 3c590 (it was an asus mother board, with ide disabled, and a aha2940W) it worked fine, and infact well enough to do a network install via ftp from, but once the operating system was installed, i experienced VERY odd behaviour: o any outbound connections will hang after transfering approx 1K (ie: telnet from the box, ftp from the box) o all inbound (incoming telnet, incoming ftp) worked perfectly fine. I decided to yank the 590 and put in a 3c509 and everything works just fine. J Wunsch : > As Beck Peccoz Amedeo wrote: > > > In the kernel config I added the line "options vx0" as suggested > > from the LINT, but when starting up, the kernel didn't notice > > the board, so I tried to contigure the kernel, i.e. type a "-c" > > at the boot prompt, but in the network section only the usual > > serial and parallel port drivers appeared. > > Only ISA drivers need to be configured with boot -c. > > > I'm running Snapshot with ctm 1873. What's wrong? > > Well, vx0 is a device, not an option. ;) > > device vx0 > > - -- > cheers, J"org From owner-freebsd-current Thu Jun 13 09:08:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02849 for current-outgoing; Thu, 13 Jun 1996 09:08:13 -0700 (PDT) Received: from expresslane.ca (expresslane.ca [205.233.74.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA02843 for ; Thu, 13 Jun 1996 09:08:10 -0700 (PDT) Received: from localhost (james@localhost) by expresslane.ca (8.7.5/8.7.3) with SMTP id MAA05421 for ; Thu, 13 Jun 1996 12:08:08 -0400 (EDT) Date: Thu, 13 Jun 1996 12:08:05 -0400 (EDT) From: James FitzGibbon To: freebsd-current@freebsd.org Subject: UIDs greater than 65535 ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've noticed a slight discrepancy between the maxmium UID allowed in include/pwd.h, and that allowed in usr.sbin/pw_scan.c. The struct passwd uses : int pw_uid; /* user uid */ But pw_scan.c uses this check routine : if (id > USHRT_MAX) { warnx("%s > max uid value (%d)", p, USHRT_MAX); return (0); } So that although a userid can have a 32-bit value, the password scanning routines won't allow anything higher than 16 bit. Is this just an oversight (i.e. can we just change the constant in pw_scan.c? ) or are there other reasons why the UIDs are limited to 16-bit ? Please reply directly, I'm not on -current for fear of a mail explosion like -stable ... 8-) -- j. +--------------------------------------------------------------------------+ | James FitzGibbon james@expresslane.ca | | Internet Canada Corp. Voice/Fax: 416-363-8518/8713 | +--------------------------------------------------------------------------+ From owner-freebsd-current Thu Jun 13 10:09:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05423 for current-outgoing; Thu, 13 Jun 1996 10:09:01 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA05399 for ; Thu, 13 Jun 1996 10:08:48 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id OAA21413; Thu, 13 Jun 1996 14:52:24 +0100 (BST) To: Ollivier Robert cc: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) From: "Gary Palmer" Subject: Re: #include opt_ipfw.h problem for lkm In-reply-to: Your message of "Thu, 13 Jun 1996 11:50:49 +0200." <199606130950.LAA15818@keltia.freenix.fr> Date: Thu, 13 Jun 1996 14:52:23 +0100 Message-ID: <21410.834673943@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert wrote in message ID <199606130950.LAA15818@keltia.freenix.fr>: > sys/netinet/ip_fw.c includes "opt_ipfw.h" when compiling the kernel (which > is fine) but includes it also when compiling as lkm (which is bad). Phoey. You're right. On this subject, does anyone object to my REMOVAL of the option to have IPFW as an LKM? Having it as an LKM is (IMHO) stupid ... all a person breaking in needs to do to throw security WIDE open is modunload the module, and then the machine will fall back to being a simple router. Not my idea of a secure option. Will anyone seriously miss it if I remove the lkm? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Thu Jun 13 10:26:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06385 for current-outgoing; Thu, 13 Jun 1996 10:26:17 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA06377; Thu, 13 Jun 1996 10:26:14 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA09438; Thu, 13 Jun 1996 13:26:13 -0400 Date: Thu, 13 Jun 1996 13:26:13 -0400 From: Garrett Wollman Message-Id: <9606131726.AA09438@halloran-eldar.lcs.mit.edu> To: "Gary Palmer" Cc: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Subject: Re: #include opt_ipfw.h problem for lkm In-Reply-To: <21410.834673943@palmer.demon.co.uk> References: <199606130950.LAA15818@keltia.freenix.fr> <21410.834673943@palmer.demon.co.uk> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > On this subject, does anyone object to my REMOVAL of the option to > have IPFW as an LKM? Yes, yes, yes, please please please DO DO this! I have been arguing for this for a while now! -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Jun 13 10:31:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06772 for current-outgoing; Thu, 13 Jun 1996 10:31:58 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA06763; Thu, 13 Jun 1996 10:31:53 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id MAA01752; Thu, 13 Jun 1996 12:33:21 -0500 (CDT) Received: from orion.fa.tdktca.com ([163.49.131.130]) by shogun.tdktca.com (8.7.2/8.7.2) with SMTP id MAA01746; Thu, 13 Jun 1996 12:33:21 -0500 (CDT) Received: from orion (alex@localhost [127.0.0.1]) by orion.fa.tdktca.com (8.6.12/8.6.9) with SMTP id MAA01520; Thu, 13 Jun 1996 12:34:19 -0500 Message-ID: <31C0511A.279A7B71@fa.tdktca.com> Date: Thu, 13 Jun 1996 12:34:18 -0500 From: Alex Nash Organization: TDK Factory Automation X-Mailer: Mozilla 2.0 (X11; I; Linux 1.2.13 i586) MIME-Version: 1.0 To: Gary Palmer CC: Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: #include opt_ipfw.h problem for lkm References: <21410.834673943@palmer.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Gary Palmer wrote: > On this subject, does anyone object to my REMOVAL of the option to > have IPFW as an LKM? Having it as an LKM is (IMHO) stupid ... all a > person breaking in needs to do to throw security WIDE open is > modunload the module, and then the machine will fall back to being a > simple router. Not my idea of a secure option. > > Will anyone seriously miss it if I remove the lkm? I know at least one person who will... The following exchange resulted from PR 1192: From: Garrett Wollman To: nash@mcs.com Cc: FreeBSD-gnats-submit@freebsd.org, phk@freebsd.org Subject: kern/1192: Kernel IPFW Date: Sun, 12 May 1996 16:23:32 -0400 < said: > Moved the majority of code out of the ipfw_load (module load) > routine and instead issue a call to ipfw_init which does the same > thing (sans the splnet() issued at the beginning of ipfw_load). Actually, I would very much like to get rid of the dynamically-loadable IPFW module entirely. If you are running any sort of a reasonable router configuration (i.e., with multiple cards from the same vendor), you will have to reconfigure the kernel anyway, and I think there are probably good security reasons for wanting in that way. (What if the LKM fails to load because you are out of disk space in /tmp? Oops.) Perhaps more significantly, it puts extra hair in the IP input and output paths that doesn't need to be there in the common case (workstation or non-firewalling router), so I'd like to see it removed. (And yes, I do remember that I'm the one who suggested making it into an LKM in the first place!) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From: Poul-Henning Kamp To: Garrett Wollman Cc: nash@mcs.com, FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/1192: Kernel IPFW Date: Sun, 12 May 1996 20:57:43 +0000 > Actually, I would very much like to get rid of the > dynamically-loadable IPFW module entirely. I think that this makes sense from a security point of view, but people use it for a lot of things besides security. The hooks are very general and can be used for a bunch of other things as well, so I think this is all in all, not a good idea. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. Alex From owner-freebsd-current Thu Jun 13 11:54:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11865 for current-outgoing; Thu, 13 Jun 1996 11:54:16 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA11860; Thu, 13 Jun 1996 11:54:12 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA30645; Thu, 13 Jun 1996 20:54:04 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA10911; Thu, 13 Jun 1996 20:53:18 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.4/keltia-uucp-2.8) id TAA28914; Thu, 13 Jun 1996 19:53:08 +0200 (MET DST) From: Ollivier Robert Message-Id: <199606131753.TAA28914@keltia.freenix.fr> Subject: Re: #include opt_ipfw.h problem for lkm To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Thu, 13 Jun 1996 19:53:08 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <21410.834673943@palmer.demon.co.uk> from Gary Palmer at "Jun 13, 96 02:52:23 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#2111 X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that Gary Palmer said: > Will anyone seriously miss it if I remove the lkm? Not me. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #11: Thu Jun 13 11:01:47 MET DST 1996 From owner-freebsd-current Thu Jun 13 12:42:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA13926 for current-outgoing; Thu, 13 Jun 1996 12:42:34 -0700 (PDT) Received: from critter.tfs.com (critter.cdrom.com [204.216.27.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA13920 for ; Thu, 13 Jun 1996 12:42:28 -0700 (PDT) Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id MAA03323 for ; Thu, 13 Jun 1996 12:42:16 -0700 (PDT) To: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Subject: Re: #include opt_ipfw.h problem for lkm In-reply-to: Your message of "Thu, 13 Jun 1996 13:26:13 EDT." <9606131726.AA09438@halloran-eldar.lcs.mit.edu> Date: Thu, 13 Jun 1996 12:42:15 -0700 Message-ID: <3321.834694935@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I object STRONGLY to removing the ipfw LKM. What would we gain ? -- nothing. What would we loose ? -- a feature. You argument that an intruder just has to unload the lkm is bogus. If you used ipfw for sercurity purposes, you would NOT use the LKM in the first place. Second, if you did, you would surely be running with a secure-level that prevented the unloading of the lkm. "Doctor! doctor! It hurts when I do this!" -- "Don't do that then!" The point of having it as an LKM, is that you can use it to remove traffic that you don't want, ie. use it as a network tool not a security device as such. I have used it to do things like filter out RIP from a bogus router or merely logging of traffic from a particular host. Neither of these uses warranted a hyper-secure setup, and being able to load ipfw was just the thing to do the job. Why would we kill a feature like that ? I will conceede to Garretts argument of speed, and you can add: #ifdef INET_REALLY_FAST around the two function calls as long as you don't put it in GENERIC. According to your logic I expect you to advocate the removal of ufs-async, ext2fs, msdosfs not to mention rm features because they are dangerous if used wrong. :-) Remember that FreeBSD is not in the business of enforcing any policy but provide the tools for others to enforce their own chosen policies... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Jun 13 14:51:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20716 for current-outgoing; Thu, 13 Jun 1996 14:51:33 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA20710 for ; Thu, 13 Jun 1996 14:51:27 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA23207; Thu, 13 Jun 1996 23:50:59 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16994; Thu, 13 Jun 1996 23:50:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id XAA15255; Thu, 13 Jun 1996 23:24:46 +0200 (MET DST) From: J Wunsch Message-Id: <199606132124.XAA15255@uriah.heep.sax.de> Subject: Re: 3Com 590 not seen To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 13 Jun 1996 23:24:46 +0200 (MET DST) Cc: pluvius@cyberflunk.com (pluvius) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from pluvius at "Jun 13, 96 08:48:16 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As pluvius wrote: > o any outbound connections will hang after transfering approx 1K > (ie: telnet from the box, ftp from the box) > o all inbound (incoming telnet, incoming ftp) worked perfectly fine. This hackaround might help you. It has been posted here a couple of weeks ago (sorry, i forgot the name of the author). Index: sys/pci/if_vx.c =================================================================== RCS file: /usr/home/cvs/src/sys/pci/if_vx.c,v retrieving revision 1.9 diff -u -u -r1.9 if_vx.c --- if_vx.c 1996/02/06 18:51:26 1.9 +++ if_vx.c 1996/06/02 17:27:28 @@ -520,7 +520,7 @@ } IF_DEQUEUE(&sc->arpcom.ac_if.if_snd, m); - outw(BASE + VX_W1_TX_PIO_WR_1, len); + outw(BASE + VX_W1_TX_PIO_WR_1, len | 0x8000 /* XXX */); outw(BASE + VX_W1_TX_PIO_WR_1, 0x0); /* Second dword meaningless */ /* compute the Tx start threshold for this packet */ -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jun 13 15:06:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21660 for current-outgoing; Thu, 13 Jun 1996 15:06:24 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA21652 for ; Thu, 13 Jun 1996 15:06:17 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA15142 for current@freebsd.org; Thu, 13 Jun 1996 18:04:49 -0400 From: Bill Paul Message-Id: <199606132204.SAA15142@skynet.ctr.columbia.edu> Subject: Patch for NFS_NOSERVER -- please test To: current@freebsd.org Date: Thu, 13 Jun 1996 18:04:48 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Appended to this message is a set of patches for nfs_socket.c and nfs_subs.c which seems to cure the problem with NFS_NOSERVER wedging up the system, at least for me. If anyone else is having trouble with this, please test these patches and get back to me. If it cures the problem, I'll commit them to the tree. Note that I am _not_ an NFS expert by any stretch of the imagination, so I check this over carefullty. It seems to have fixed all my problems: I'm using the system right now with a completely diskless configuration (everything mounted over NFS) without any problems. I even have the automounter running. But as usual, YMMV. Poul mentioned that he thought this was some kind of timing problem, and that started me thinking. After a little poking around, I found that nfs_timer() was completely disabled when NFS_NOSERVER was #defined. But after looking at nfs_timer(), it seemed like it was something required by both the client and server code, and disabling it outright just didn't seem to make any sense. Parts of it relate only to the NFS server side code, so I disabled those, but I re-enabled the rest of the function and made sure that it would be called from nfs_init() (in nfs_subs.c). With nfs_timer() re-enabled, everything seems to work again. The only other changes I made were to #ifdef away some variable declarations in the NFS_NOSERVER case so that gcc would stop complaining about unused variables. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= License error: The license for this .sig file has expired. You must obtain a new license key before any more witty phrases will appear in this space. ============================================================================= *** nfs_socket.c.orig Thu Jun 13 17:40:04 1996 --- nfs_socket.c Thu Jun 13 17:31:13 1996 *************** *** 141,149 **** static int nfs_receive __P((struct nfsreq *rep, struct mbuf **aname, struct mbuf **mp)); static int nfs_reconnect __P((struct nfsreq *rep)); static int nfsrv_getstream __P((struct nfssvc_sock *,int)); - #ifndef NFS_NOSERVER int (*nfsrv3_procs[NFS_NPROCS]) __P((struct nfsrv_descript *nd, struct nfssvc_sock *slp, struct proc *procp, --- 141,149 ---- static int nfs_receive __P((struct nfsreq *rep, struct mbuf **aname, struct mbuf **mp)); static int nfs_reconnect __P((struct nfsreq *rep)); + #ifndef NFS_NOSERVER static int nfsrv_getstream __P((struct nfssvc_sock *,int)); int (*nfsrv3_procs[NFS_NPROCS]) __P((struct nfsrv_descript *nd, struct nfssvc_sock *slp, struct proc *procp, *************** *** 1267,1272 **** --- 1267,1273 ---- } + #endif /* NFS_NOSERVER */ /* * Nfs timer routine * Scan the nfsreq list and retranmit any requests that have timed out *************** *** 1282,1291 **** register struct socket *so; register struct nfsmount *nmp; register int timeo; - register struct nfssvc_sock *slp; - static long lasttime = 0; int s, error; u_quad_t cur_usec; s = splnet(); for (rep = nfs_reqq.tqh_first; rep != 0; rep = rep->r_chain.tqe_next) { --- 1283,1294 ---- register struct socket *so; register struct nfsmount *nmp; register int timeo; int s, error; + #ifndef NFS_NOSERVER + static long lasttime = 0; + register struct nfssvc_sock *slp; u_quad_t cur_usec; + #endif /* NFS_NOSERVER */ s = splnet(); for (rep = nfs_reqq.tqh_first; rep != 0; rep = rep->r_chain.tqe_next) { *************** *** 1374,1380 **** } } } ! /* * Call the nqnfs server timer once a second to handle leases. */ --- 1377,1383 ---- } } } ! #ifndef NFS_NOSERVER /* * Call the nqnfs server timer once a second to handle leases. */ *************** *** 1393,1403 **** if (slp->ns_tq.lh_first && slp->ns_tq.lh_first->nd_time<=cur_usec) nfsrv_wakenfsd(slp); } splx(s); timeout(nfs_timer, (void *)0, nfs_ticks); } - #endif /* NFS_NOSERVER */ /* * Test for a termination condition pending on the process. --- 1396,1406 ---- if (slp->ns_tq.lh_first && slp->ns_tq.lh_first->nd_time<=cur_usec) nfsrv_wakenfsd(slp); } + #endif /* NFS_NOSERVER */ splx(s); timeout(nfs_timer, (void *)0, nfs_ticks); } /* * Test for a termination condition pending on the process. *** nfs_subs.c.orig Thu Jun 13 17:39:58 1996 --- nfs_subs.c Thu Jun 13 17:37:11 1996 *************** *** 1147,1155 **** * Initialize reply list and start timer */ TAILQ_INIT(&nfs_reqq); ! #ifndef NFS_NOSERVER nfs_timer(0); ! #endif #ifdef __FreeBSD__ /* --- 1147,1155 ---- * Initialize reply list and start timer */ TAILQ_INIT(&nfs_reqq); ! nfs_timer(0); ! #ifdef __FreeBSD__ /* From owner-freebsd-current Thu Jun 13 17:03:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA13680 for current-outgoing; Thu, 13 Jun 1996 17:03:58 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA13648; Thu, 13 Jun 1996 17:03:48 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA32106; Fri, 14 Jun 1996 09:56:47 +1000 Date: Fri, 14 Jun 1996 09:56:47 +1000 From: Bruce Evans Message-Id: <199606132356.JAA32106@godzilla.zeta.org.au> To: gpalmer@FreeBSD.org, roberto@keltia.freenix.fr Subject: Re: #include opt_ipfw.h problem for lkm Cc: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> sys/netinet/ip_fw.c includes "opt_ipfw.h" when compiling the kernel (which >> is fine) but includes it also when compiling as lkm (which is bad). Including it conditionally is the wrong fix. lkms must not depend on any options, since their behaviour must be the same as the statically configured versions. I think the conditional include doesn't do much damage because option IPFIREWALL isn't used. Only the option IPFIREWALL_VERBOSE is used. Other bugs: option IPFIREWALL_VERBOSE_LIMIT isn't in the options file, and lkm ipfw and option file opt_ipfw.h have hard to remember names - `ip' is followed by `_' in all other ip file names. There is a potentially much more serious problem in the use of the option IPFIREWALL in ip_input.c. I think this isn't actually a problem, because the option is only used to control the initialization of ip_fw, and this initialization gets done in another way if ip_^Hfw is an lkm. Why isn't PSEUDO_SET() used to do the initialization transparently like it is for other lkm's? I guess there are ordering problems. Bruce From owner-freebsd-current Thu Jun 13 18:31:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23294 for current-outgoing; Thu, 13 Jun 1996 18:31:06 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA23287 for ; Thu, 13 Jun 1996 18:31:04 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with SMTP id AAA09581 for ; Tue, 11 Jun 1996 00:35:30 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id AAA10624; Tue, 11 Jun 1996 00:31:50 -0700 Date: Tue, 11 Jun 1996 00:31:48 -0700 (PDT) From: Veggy Vinny To: dwhite@resnet.uoregon.edu cc: current@freebsd.org Subject: Re: console messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 11 Jun 1996, Doug White wrote: > On Tue, 11 Jun 1996, Veggy Vinny wrote: > > Here I go answering questions without reading the question first :-) How'd you do that? :) > > > > I'm running the June 3rd, 1996 FreeBSD-current and it seems on a > > > > machine with a Intel Neptune based Dual P5-100 system with 128 megs of > > > > RAM and 300 megs of disk swap, we keep getting the following message and > > > > then the machine reboots or just hangs there, any ideas what can be > > > > causing this? > > > > > > > > /kernel: proc: table is full > > > > > > Increase MAXUSERS in the kernel config. > > > > It's already at 128... > > Maybe you have a runaway process then. Hmmm, I doubt it though since it wasn't a run away process since there weren't many processes on the machine and none of them forked... > I think I'll let the pros take it from here... this is not something I'm > very familiar with. Oh okay.... thanks anyways... -Vince- GaiaNet System Administration - http://www.gaianet.net From owner-freebsd-current Thu Jun 13 19:29:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA29204 for current-outgoing; Thu, 13 Jun 1996 19:29:52 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA29191 for ; Thu, 13 Jun 1996 19:29:47 -0700 (PDT) Received: from muggsy.lkg.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id WAA01158; Thu, 13 Jun 1996 22:15:41 -0400 (EDT) Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA24452; Thu, 13 Jun 1996 20:58:27 -0400 Received: from localhost (localhost [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id VAA11908 for ; Thu, 13 Jun 1996 21:02:48 GMT Message-Id: <199606132102.VAA11908@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: freebsd-current@freebsd.org Subject: 2.2-960612-SNAP impressions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Jun 1996 21:02:48 +0000 From: Matt Thomas Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried using a 3com 3C589C (zp0) to download the snap but the system keep hanging (eventually causing so much damage to the existing UFS paritions I had to newfs them), so I switched to the tried & true, but slow, PPP link. sysinstall claimed the install directory doesn't exist but proceeded to start installing anyways. Other than that, it seems to be loading fine. BTW, Yellow on Gray has horrible contrast and is hard to read on a Digital HiNote Ultra. ssys.?? has compile/BOOTMFS in it. Well, it's now up and running. So far, ok. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-current Thu Jun 13 21:56:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07137 for current-outgoing; Thu, 13 Jun 1996 21:56:18 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA07105; Thu, 13 Jun 1996 21:56:06 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with SMTP id NAA03998; Fri, 7 Jun 1996 13:03:53 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA03809; Fri, 7 Jun 1996 12:54:06 -0700 From: Terry Lambert Message-Id: <199606071954.MAA03809@phaeton.artisoft.com> Subject: Re: The -stable problem: my view To: nate@sri.MT.net (Nate Williams) Date: Fri, 7 Jun 1996 12:54:06 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD-current@freebsd.org In-Reply-To: <199606071953.NAA00238@rocky.sri.MT.net> from "Nate Williams" at Jun 7, 96 01:53:25 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Try using it _seriously_ someday and no explanation will be necessary. > > > Suffice it to say that it has absolutely nothing to do with the > > > documentation. > > > > The problem with CVS is access protocol. > > No, the problem is that CVS doesn't handle diverging source trees very > well. The access to the tree is *completely* and *utterly* irrelevant > to the problems at hand, and just because you want it changed doesn't > mean you should get on your soapbox and call for it's implentation. > > Stick the to *problem* that's being discussed, not one that you (and > only you) consider to be a real problem with CVS. > > You're tryin to break the model that CVS was designed for, and this part > of the model is *NOT* one of the problems FreeBSD is facing now. Nate: you're wrong. The main argument against "let's get rid of -stable" is that -stable is known to be buildable. If -current were known to be buildable, it would support the argument for getting rid of -stable. CVS can reconcile source trees (merge branch tags) just fine... we did that sort of thing at Novell with a CVS version of three years ago, no problems. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Jun 13 22:20:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08149 for current-outgoing; Thu, 13 Jun 1996 22:20:01 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08124 for ; Thu, 13 Jun 1996 22:19:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id WAA02552; Thu, 13 Jun 1996 22:17:24 -0700 (PDT) To: Matt Thomas cc: freebsd-current@freebsd.org Subject: Re: 2.2-960612-SNAP impressions In-reply-to: Your message of "Thu, 13 Jun 1996 21:02:48 -0000." <199606132102.VAA11908@whydos.lkg.dec.com> Date: Thu, 13 Jun 1996 22:17:23 -0700 Message-ID: <2550.834729443@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I tried using a 3com 3C589C (zp0) to download the snap but the system > keep hanging (eventually causing so much damage to the existing UFS > paritions I had to newfs them), so I switched to the tried & true, but > slow, PPP link. Never tried this card, so I can't say if this is new or old breakage. :-) My Nat Semi InfoMover (using the ze0 driver) still works fine. > sysinstall claimed the install directory doesn't exist but proceeded to > start installing anyways. Hmmmm. You mean the target 2.2-960612 directory? My own install seems to have worked fine from ftp.cdrom.com. Strange, I'll check again. > BTW, Yellow on Gray has horrible contrast and is hard to read > on a Digital HiNote Ultra. OK. This is a new addition and I sort of noticed the poor contrast also. I'll fix it. > ssys.?? has compile/BOOTMFS in it. Oh yuck. Something broken in the release makefile again. Thanks, I'll chase it down. Jordan From owner-freebsd-current Fri Jun 14 00:52:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA15442 for current-outgoing; Fri, 14 Jun 1996 00:52:06 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA15407 for ; Fri, 14 Jun 1996 00:52:01 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.5+2.6Wbeta6/950912) with ESMTP id QAA08097; Fri, 14 Jun 1996 16:51:49 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id QAA17540; Fri, 14 Jun 1996 16:51:47 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id QAA09655; Fri, 14 Jun 1996 16:51:41 +0900 (JST) Date: Fri, 14 Jun 1996 16:51:41 +0900 (JST) From: Naoki Hamada Message-Id: <199606140751.QAA09655@sirius.sbl.cl.nec.co.jp> References: <199606101905.NAA09662@rocky.sri.MT.net> To: nate@sri.MT.net CC: current@FreeBSD.ORG In-reply-to: Nate Williams's message of "Mon, 10 Jun 1996 13:05:22 -0600" <199606101905.NAA09662@rocky.sri.MT.net> Subject: Re: Attention 3C5X9 owners Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Can you please test out this patch to /sys/i386/isa/if_ep.c to make sure >this works? This changes the way the driver selects the different card >ports (AUI/BNC), and is needed for the PCCARD support (not included). >In order to get the BNC connector working on my 3C589 card, but since >it's based on code that was originally for the 3C509 I suspect it should >work. Nate, your patch still lacks some cases and breaks some important information. I carefully studied the logic and made the connector selection scheme a bit clearer and robuster, I hope. >I need folks who have AUI connections, and folks who have BNC >connections to test this to make sure it works, or even better folks who >have both can test it to make sure it works fine with both. My 3C509B-COMBO works fine with the following patch. Switching between UTP and BNC is quite easy. (Just type 'ifconfig ep0 link1 -link2' or 'ifconifg ep0 link2 -link1'.) I have no AUI equipment, and what is worse, my 3C589B is now under repair, so we need some other tests! -nao --- if_ep.c.orig Sat May 25 00:22:36 1996 +++ if_ep.c Fri Jun 14 16:23:40 1996 @@ -641,39 +641,40 @@ * */ + /* Set the xcvr. */ if(ifp->if_flags & IFF_LINK0 && sc->ep_connectors & AUI) { - /* nothing */ + i = ACF_CONNECTOR_AUI; } else if(ifp->if_flags & IFF_LINK1 && sc->ep_connectors & BNC) { - outw(BASE + EP_COMMAND, START_TRANSCEIVER); - DELAY(1000); + i = ACF_CONNECTOR_BNC; } else if(ifp->if_flags & IFF_LINK2 && sc->ep_connectors & UTP) { - GO_WINDOW(4); - outw(BASE + EP_W4_MEDIA_TYPE, ENABLE_UTP); - GO_WINDOW(1); + i = ACF_CONNECTOR_UTP; } else { - GO_WINDOW(1); - switch(sc->ep_connector) { - case ACF_CONNECTOR_UTP: - if(sc->ep_connectors & UTP) { - GO_WINDOW(4); - outw(BASE + EP_W4_MEDIA_TYPE, ENABLE_UTP); - GO_WINDOW(1); - } - break; - case ACF_CONNECTOR_BNC: - if(sc->ep_connectors & BNC) { - outw(BASE + EP_COMMAND, START_TRANSCEIVER); - DELAY(1000); - } - break; - case ACF_CONNECTOR_AUI: - /* nothing to do */ - break; - default: - printf("ep%d: strange connector type in EEPROM: assuming AUI\n", - sc->unit); - break; + i = sc->ep_connector; + } + GO_WINDOW(0); + j = inw(BASE + EP_W0_ADDRESS_CFG) & 0x3fff; + outw(BASE + EP_W0_ADDRESS_CFG, j | (i << ACF_CONNECTOR_BITS)); + + switch(i) { + case ACF_CONNECTOR_UTP: + if(sc->ep_connectors & UTP) { + GO_WINDOW(4); + outw(BASE + EP_W4_MEDIA_TYPE, ENABLE_UTP); + } + break; + case ACF_CONNECTOR_BNC: + if(sc->ep_connectors & BNC) { + outw(BASE + EP_COMMAND, START_TRANSCEIVER); + DELAY(1000); } + break; + case ACF_CONNECTOR_AUI: + /* nothing to do */ + break; + default: + printf("ep%d: strange connector type in EEPROM: assuming AUI\n", + sc->unit); + break; } outw(BASE + EP_COMMAND, RX_ENABLE); @@ -718,6 +719,7 @@ sc->next_mb = 0; epmbuffill((caddr_t) sc, 0); + GO_WINDOW(1); epstart(ifp); splx(s); From owner-freebsd-current Fri Jun 14 01:10:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA16581 for current-outgoing; Fri, 14 Jun 1996 01:10:53 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA16575 for ; Fri, 14 Jun 1996 01:10:50 -0700 (PDT) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <15003-0@bunyip.cc.uq.oz.au>; Fri, 14 Jun 1996 18:10:24 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id SAA01908 for ; Fri, 14 Jun 1996 18:10:58 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id IAA19478 for ; Fri, 14 Jun 1996 08:12:24 GMT Message-Id: <199606140812.IAA19478@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: SMP Pentium boards in Oz X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jun 1996 18:12:23 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Given the recent to-do about the SMP code, does any other Australian know of any vendors of SMP Pentium MBs in Oz? (Work is getting a dual Pentium-166MHz mb with 128Mb of memory via Fujitsu-ICL, but they charge like the proverbial wounded bovine) Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Fri Jun 14 02:01:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA19349 for current-outgoing; Fri, 14 Jun 1996 02:01:03 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA19340 for ; Fri, 14 Jun 1996 02:00:59 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA03267; Fri, 14 Jun 1996 18:59:30 +0930 From: Michael Smith Message-Id: <199606140929.SAA03267@genesis.atrad.adelaide.edu.au> Subject: Re: SMP Pentium boards in Oz To: sysseh@devetir.qld.gov.au (Stephen Hocking) Date: Fri, 14 Jun 1996 18:59:30 +0930 (CST) Cc: current@freebsd.org In-Reply-To: <199606140812.IAA19478@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at Jun 14, 96 06:12:23 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stephen Hocking stands accused of saying: > > Given the recent to-do about the SMP code, does any other Australian know of > any vendors of SMP Pentium MBs in Oz? (Work is getting a dual Pentium-166MHz > mb with 128Mb of memory via Fujitsu-ICL, but they charge like the proverbial > wounded bovine) Soyo have one; I believe it's a neptune (see www.soyo.com). Their stuff has been pretty good so far for us. > Stephen -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Jun 14 02:04:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA19625 for current-outgoing; Fri, 14 Jun 1996 02:04:40 -0700 (PDT) Received: from critter.tfs.com ([140.145.16.108]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA19620; Fri, 14 Jun 1996 02:04:37 -0700 (PDT) Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id CAA04143; Fri, 14 Jun 1996 02:03:46 -0700 (PDT) To: current@freebsd.org, smp@freebsd.org Subject: a data-point for SMP Reply-to: phk@freebsd.org Date: Fri, 14 Jun 1996 02:03:43 -0700 Message-ID: <4141.834743023@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk HP P6/250 x 2, 64M ram, 1 scsi disk on ahc0. make -j8 COPTFLAGS= -O2 -pipe time to make GENERIC kernel: 280.4u 53.0s 2:53.42 192.3% 484+645k 8+264io 0pf+0w ^^^^^^ not at all bad :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Jun 14 02:39:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA25623 for current-outgoing; Fri, 14 Jun 1996 02:39:40 -0700 (PDT) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA25530; Fri, 14 Jun 1996 02:39:15 -0700 (PDT) Received: (from robinson@localhost) by public.bta.net.cn (8.6.8.1/8.6.9) id RAA12045; Fri, 14 Jun 1996 17:39:10 +0800 Date: Fri, 14 Jun 1996 17:39:10 +0800 From: Michael Robinson Message-Id: <199606140939.RAA12045@public.bta.net.cn> To: nate@sri.MT.net, terry@lambert.org Subject: Re: The -stable problem: my view Cc: FreeBSD-current@FreeBSD.org, freebsd-stable@FreeBSD.org, hackers@FreeBSD.org, jkh@time.cdrom.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The main argument against "let's get rid of -stable" is that -stable >is known to be buildable. No. The main argument against "let's get rid of -stable" is that kernel panics are antagonistic to getting real work done. Some people (such as myself) depend on FreeBSD to do real work. Some people (so far, not myself) need bug fixes or new features as part of doing real work, and would rather not wait 15 months between releases. >If -current were known to be buildable, >it would support the argument for getting rid of -stable. If release-quality code could be packaged every three months, *that* would support the argument for getting rid of -stable. -Michael Robinson From owner-freebsd-current Fri Jun 14 04:00:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA06661 for current-outgoing; Fri, 14 Jun 1996 04:00:03 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA06616 for ; Fri, 14 Jun 1996 03:59:59 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id DAA01863; Fri, 14 Jun 1996 03:59:56 -0700 (PDT) Date: Fri, 14 Jun 1996 03:59:56 -0700 (PDT) Message-Id: <199606141059.DAA01863@silvia.HIP.Berkeley.EDU> To: current@freebsd.org CC: FreeBSD@center.nitech.ac.jp Subject: The Great PC98 Merge From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just committed the changes to make our -current sys tree compatible with the NEC PC98 series computers. All new files are in a separate tree (sys/pc98) or "#ifdef PC98"ed out so they should have no effect to non-PC98 users. I have no idea what the code does so please direct any questions/ suggestions/praises to the FreeBSD(98) developers. Open the champagne and celebrate this great day! :) Satoshi From owner-freebsd-current Fri Jun 14 07:58:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA20488 for current-outgoing; Fri, 14 Jun 1996 07:58:42 -0700 (PDT) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA20475 for ; Fri, 14 Jun 1996 07:58:37 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id JAA14024 for current@freebsd.org; Fri, 14 Jun 1996 09:58:36 -0500 Date: Fri, 14 Jun 1996 09:58:36 -0500 From: Jim Lowe Message-Id: <199606141458.JAA14024@miller.cs.uwm.edu> To: current@freebsd.org Subject: 6/14/96 kernel won't boot Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I picked up a new kernel this morning, remade it, and now my system won't boot with the new kernel. The system booted just fine with a new kernel a day or so ago (6/12/96). The system comes up to the point where is says: devfs ready to run and then panics with: Fatal trap12: page fault while in kernel mode fault virtual addr = 0x0 fault code = Supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xefbffea4 frame pointer = 0x10:0xefbffef8 code seg = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 proc eflags = interrupt enabled, resume, IOPL = 0 current process = 5 (sh) interrupt mask = -- The system configuration for the kernels is attached. Thanks for any help, -Jim ------------------ FreeBSD 2.2-CURRENT #0: Wed Jun 12 14:46:27 CDT 1996 james@miller-genuine-draft.cs.uwm.edu:/usr/src/sys/compile/MGD Calibrating clock(s) relative to mc146818A clock... i586 clock: 132621508 Hz, i8254 clock: 1193093 Hz CPU: Pentium (132.62-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping=11 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30183424 (29476K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 piix0 rev 2 on pci0:7:1 meteor0 rev 0 int a irq 12 on pci0:9:0 meteor0: rev 0x1 ncr0 rev 2 int a irq 10 on pci0:10 (ncr0:0:0): "HP C2247-300 0BA4" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1003MB (2054864 512 byte sectors) sd0(ncr0:0:0): with 2051 cyls, 13 heads, and an average 77 sectors/track (ncr0:2:0): "TOSHIBA CD-ROM XM-3401TA 2873" type 5 removable SCSI 2 cd0(ncr0:2:0): CD-ROM cd0(ncr0:2:0): 250ns (4 Mb/sec) offset 8. cd0(ncr0:2:0): NOT READY asc:3a,0 Medium not present can't get the size de0 rev 17 int a irq 11 on pci0:11 de0: DC21140 [10-100Mb/s] pass 1.1 Ethernet address 00:00:c0:b3:d0:9a de0: enabling 10baseT UTP port vga0 rev 0 on pci0:12 Probing for devices on the ISA bus: scprobe: keyboard RESET failed (result = 0xfa) sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> ed0 not found at 0x280 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface qcam0 at 0x378 flags 0x1 on isa qcam0: bidirectional parallel port pca0 on isa pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 not found at 0x1f0 aha0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface joy0 at 0x201 on isa joy0: joystick pas0 not found at 0x388 sb0 not found at 0x220 gus0 at 0x220 irq 15 drq 1 flags 0x3 on isa gus0: gus0: opl0 not found at 0x388 spigot0 at 0xad6 maddr 0xd0000 on isa devfs ready to run new masks: bio c0000440, tty c003189a, net c003189a From owner-freebsd-current Fri Jun 14 08:27:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22475 for current-outgoing; Fri, 14 Jun 1996 08:27:47 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA22470 for ; Fri, 14 Jun 1996 08:27:43 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id IAA12901; Fri, 14 Jun 1996 08:26:40 -0700 (PDT) To: Jim Lowe cc: current@freebsd.org Subject: Re: 6/14/96 kernel won't boot In-reply-to: Your message of "Fri, 14 Jun 1996 09:58:36 CDT." <199606141458.JAA14024@miller.cs.uwm.edu> Date: Fri, 14 Jun 1996 08:26:40 -0700 Message-ID: <12899.834766000@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I picked up a new kernel this morning, remade it, and now my system > won't boot with the new kernel. The system booted just fine with a > new kernel a day or so ago (6/12/96). Just out of curiousity, have you tried one without DEVFS? > scprobe: keyboard RESET failed (result = 0xfa) Grr. It seems practically _everyone's_ keyboard does this now. Is anyone even thinking about fixing this? :-( ache, phk and sos were the last to touch it. Jordan From owner-freebsd-current Fri Jun 14 08:43:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA23289 for current-outgoing; Fri, 14 Jun 1996 08:43:28 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA23284 for ; Fri, 14 Jun 1996 08:43:23 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA21708; Fri, 14 Jun 1996 09:43:11 -0600 Date: Fri, 14 Jun 1996 09:43:11 -0600 From: Nate Williams Message-Id: <199606141543.JAA21708@rocky.sri.MT.net> To: Naoki Hamada Cc: nate@sri.MT.net, current@FreeBSD.ORG Subject: Re: Attention 3C5X9 owners In-Reply-To: <199606140751.QAA09655@sirius.sbl.cl.nec.co.jp> References: <199606101905.NAA09662@rocky.sri.MT.net> <199606140751.QAA09655@sirius.sbl.cl.nec.co.jp> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Can you please test out this patch to /sys/i386/isa/if_ep.c to make sure > >this works? This changes the way the driver selects the different card > >ports (AUI/BNC), and is needed for the PCCARD support (not included). > >In order to get the BNC connector working on my 3C589 card, but since > >it's based on code that was originally for the 3C509 I suspect it should > >work. > > Nate, your patch still lacks some cases I noticed that *after* I sent it out and corrected them in my version, but since the response wasn't very overwhelming I decided to wait until someone else piped up. Thanks for doing this. > and breaks some important > information. I carefully studied the logic and made the connector > selection scheme a bit clearer and robuster, I hope. Great. > >I need folks who have AUI connections, and folks who have BNC > >connections to test this to make sure it works, or even better folks who > >have both can test it to make sure it works fine with both. > > My 3C509B-COMBO works fine with the following patch. Switching between > UTP and BNC is quite easy. (Just type 'ifconfig ep0 link1 -link2' or 'ifconifg > ep0 link2 -link1'.) > > I have no AUI equipment, and what is worse, my 3C589B is now under > repair, so we need some other tests! Is there anyone who can test the AUI stuff? In any case, I'll try out this version with my other PC-CARD patches and see if it works. Thanks! Nate From owner-freebsd-current Fri Jun 14 09:04:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA24930 for current-outgoing; Fri, 14 Jun 1996 09:04:58 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA24925 for ; Fri, 14 Jun 1996 09:04:55 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA21742; Fri, 14 Jun 1996 10:02:35 -0600 Date: Fri, 14 Jun 1996 10:02:35 -0600 From: Nate Williams Message-Id: <199606141602.KAA21742@rocky.sri.MT.net> To: Matt Thomas Cc: freebsd-current@freebsd.org Subject: Re: 2.2-960612-SNAP impressions In-Reply-To: <199606132102.VAA11908@whydos.lkg.dec.com> References: <199606132102.VAA11908@whydos.lkg.dec.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I tried using a 3com 3C589C (zp0) to download the snap but the system > keep hanging (eventually causing so much damage to the existing UFS > paritions I had to newfs them), so I switched to the tried & true, but > slow, PPP link. > > sysinstall claimed the install directory doesn't exist but proceeded to > start installing anyways. > > Other than that, it seems to be loading fine. Hmm, I've been running -current (ie; something very close to the SNAP) with a 3C589C without problems for a week or so. Nate From owner-freebsd-current Fri Jun 14 10:24:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28921 for current-outgoing; Fri, 14 Jun 1996 10:24:37 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28915 for ; Fri, 14 Jun 1996 10:24:35 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA09565 for ; Fri, 14 Jun 1996 10:14:26 -0700 Received: from muggsy.lkg.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id NAA05596; Fri, 14 Jun 1996 13:00:33 -0400 (EDT) Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA27885; Fri, 14 Jun 1996 13:00:32 -0400 Received: from localhost (localhost [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id NAA14522; Fri, 14 Jun 1996 13:04:51 GMT Message-Id: <199606141304.NAA14522@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: Nate Williams Cc: freebsd-current@freebsd.org Subject: Re: 2.2-960612-SNAP impressions In-Reply-To: Your message of "Fri, 14 Jun 1996 10:02:35 CST." <199606141602.KAA21742@rocky.sri.MT.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jun 1996 13:04:51 +0000 From: Matt Thomas Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I tried using a 3com 3C589C (zp0) to download the snap but the system > > keep hanging (eventually causing so much damage to the existing UFS > > paritions I had to newfs them), so I switched to the tried & true, but > > slow, PPP link. > > Hmm, I've been running -current (ie; something very close to the SNAP) > with a 3C589C without problems for a week or so. Which driver? Once I could bring the system far to use the PCCARD support and the if_ep.c, all was fine. It's the if_zp.c driver that causes problems. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-current Fri Jun 14 10:24:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28958 for current-outgoing; Fri, 14 Jun 1996 10:24:42 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28935 for ; Fri, 14 Jun 1996 10:24:38 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA21953; Fri, 14 Jun 1996 11:23:14 -0600 Date: Fri, 14 Jun 1996 11:23:14 -0600 From: Nate Williams Message-Id: <199606141723.LAA21953@rocky.sri.MT.net> To: Matt Thomas Cc: Nate Williams , freebsd-current@freebsd.org Subject: Re: 2.2-960612-SNAP impressions In-Reply-To: <199606141304.NAA14522@whydos.lkg.dec.com> References: <199606141602.KAA21742@rocky.sri.MT.net> <199606141304.NAA14522@whydos.lkg.dec.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I tried using a 3com 3C589C (zp0) to download the snap but the system > > > keep hanging (eventually causing so much damage to the existing UFS > > > paritions I had to newfs them), so I switched to the tried & true, but > > > slow, PPP link. > > > > Hmm, I've been running -current (ie; something very close to the SNAP) > > with a 3C589C without problems for a week or so. > > Which driver? Once I could bring the system far to use the PCCARD support > and the if_ep.c, all was fine. It's the if_zp.c driver that causes problems. if_zp.c. PCCARD support doesn't exist in -current, and until recently didn't work for the if_ep.c (patches were made to the most recent Nomad release, but they use if_nep anyway). Nate From owner-freebsd-current Fri Jun 14 10:46:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01881 for current-outgoing; Fri, 14 Jun 1996 10:46:17 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA01857 for ; Fri, 14 Jun 1996 10:46:14 -0700 (PDT) Received: from muggsy.lkg.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id NAA08439; Fri, 14 Jun 1996 13:32:47 -0400 (EDT) Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA28046; Fri, 14 Jun 1996 13:32:46 -0400 Received: from localhost (localhost [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id NAA14671; Fri, 14 Jun 1996 13:37:04 GMT Message-Id: <199606141337.NAA14671@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: Nate Williams Cc: freebsd-current@freebsd.org Subject: Re: 2.2-960612-SNAP impressions In-Reply-To: Your message of "Fri, 14 Jun 1996 11:23:14 CST." <199606141723.LAA21953@rocky.sri.MT.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jun 1996 13:37:04 +0000 From: Matt Thomas Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Which driver? Once I could bring the system far to use the PCCARD support > > and the if_ep.c, all was fine. It's the if_zp.c driver that causes problems. > > if_zp.c. PCCARD support doesn't exist in -current, and until recently > didn't work for the if_ep.c (patches were made to the most recent Nomad > release, but they use if_nep anyway). How busy is your network? I'm on a LAN with >40% utilization (peaking often at >80%) and a great of multicast / broadcast traffic. We refer to it as the LAN from Hell. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-current Fri Jun 14 11:06:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03646 for current-outgoing; Fri, 14 Jun 1996 11:06:07 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA03637 for ; Fri, 14 Jun 1996 11:06:05 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id LAA09845 for ; Fri, 14 Jun 1996 11:06:03 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA22022; Fri, 14 Jun 1996 12:03:23 -0600 Date: Fri, 14 Jun 1996 12:03:23 -0600 From: Nate Williams Message-Id: <199606141803.MAA22022@rocky.sri.MT.net> To: Matt Thomas Cc: Nate Williams , freebsd-current@freebsd.org Subject: Re: 2.2-960612-SNAP impressions In-Reply-To: <199606141337.NAA14671@whydos.lkg.dec.com> References: <199606141723.LAA21953@rocky.sri.MT.net> <199606141337.NAA14671@whydos.lkg.dec.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > if_zp.c. PCCARD support doesn't exist in -current, and until recently > > didn't work for the if_ep.c (patches were made to the most recent Nomad > > release, but they use if_nep anyway). > > How busy is your network? I'm on a LAN with >40% utilization (peaking > often at >80%) and a great of multicast / broadcast traffic. We refer to > it as the LAN from Hell. It sounds like a similar LAN. The one at the home office isn't that way (Montana), but the one at Menlo Park (I was there yesterday) is horrendous. The SCO boxes go nuts since they log every packet collision, so you have to clear out the logfiles often. Nate From owner-freebsd-current Fri Jun 14 11:45:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06551 for current-outgoing; Fri, 14 Jun 1996 11:45:51 -0700 (PDT) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA06544 for ; Fri, 14 Jun 1996 11:45:48 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id NAA17706; Fri, 14 Jun 1996 13:45:47 -0500 Date: Fri, 14 Jun 1996 13:45:47 -0500 From: Jim Lowe Message-Id: <199606141845.NAA17706@miller.cs.uwm.edu> To: jkh@time.cdrom.com Subject: Re: 6/14/96 kernel won't boot Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: "Jordan K. Hubbard" > > > I picked up a new kernel this morning, remade it, and now my system > > won't boot with the new kernel. The system booted just fine with a > > new kernel a day or so ago (6/12/96). > > Just out of curiousity, have you tried one without DEVFS? > Ok.. I tried on w/o devfs and booted with the -v option... result was: [...] bpf: ds0 attached sd0s1: type 0x6, start 32, end 204799, size 204768 : OK sd0s2: type 0xa5, start 204800, end 2054143, size 1849344 : OK Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xefbffea4 frame pointer = 0x10:0xefbffef8 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 = 5 (init) interrupt mask = kernel: type 12 trap, code=0 db> This is odd as there is nothing on the stack and it seems to die tyring to start init... Any ideas? -Jim From owner-freebsd-current Fri Jun 14 12:30:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09947 for current-outgoing; Fri, 14 Jun 1996 12:30:03 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09871 for ; Fri, 14 Jun 1996 12:29:45 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id MAA22825 for ; Fri, 14 Jun 1996 12:29:43 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.4+2.6Wbeta6/3.3W9) with ESMTP id EAA00370; Sat, 15 Jun 1996 04:27:04 +0900 (JST) Message-Id: <199606141927.EAA00370@marble.eps.nagoya-u.ac.jp> To: current@freebsd.org Cc: FreeBSD@center.nitech.ac.jp Subject: Re: The Great PC98 Merge In-Reply-To: Your message of "Fri, 14 Jun 1996 03:59:56 -0700 (PDT)" References: <199606141059.DAA01863@silvia.HIP.Berkeley.EDU> X-Mailer: Mew version 1.05+ on Emacs 19.28.1, Mule 2.3 X-PGP-Fingerprint: CA 87 00 60 BB BA 0C 81 A8 FB AA 6A 3A B0 38 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 15 Jun 1996 04:27:03 +0900 From: KATO Takenori Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To non-Japanese folks, I would say `What PC98 is?' NEC PC98 and its compatible machines are Intel based machine which are common in Japan. The word `PC98' stands for `PC-9801' and `PC-9821.' The word `PC98' also includes its compatible, which was made by SEIKO-EPSON. Some part of PC-9801 architecture is similar to that of IBM-PC (e.g., both of them have 640KB conventional RAM, Intel CPU, uPD 765 FDC, i8237 DMAC, and i8259 PIC). However, PC98 is different in many part of hardware stuff and BIOS I/F from IBM-PC (e.g., I/O port assign, graphic stuff, and wd33c93 based SCSI card). We, FreeBSD(98) developers, have ported FreeBSD to suit it to PC98 machines since a few years ago, and FreeBSD(98), which means `FreeBSD for PC98', may become most common free UNIX-like OS _for PC98_ in Japan. (Linux for PC98 has not been maintained for a few years, and it works only on some old computers.) We are pleased at merging our code into FreeBSD-current. We thank to FreeBSD core team for their decision for merging PC98 code. If you have any comment or question, please send an E-mail to: FreeBSD@center.nitech.ac.jp in Japanese or English. Any comments and questions are welcomed. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan Voice: +81-52-789-2529 Fax: +81-52-789-3033 From owner-freebsd-current Fri Jun 14 13:10:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12944 for current-outgoing; Fri, 14 Jun 1996 13:10:09 -0700 (PDT) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA12939 for ; Fri, 14 Jun 1996 13:10:06 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id PAA19410; Fri, 14 Jun 1996 15:10:04 -0500 Date: Fri, 14 Jun 1996 15:10:04 -0500 From: Jim Lowe Message-Id: <199606142010.PAA19410@miller.cs.uwm.edu> To: jkh@time.cdrom.com Subject: Re: 6/14/96 kernel won't boot Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: "Jordan K. Hubbard" > > > I picked up a new kernel this morning, remade it, and now my system > > won't boot with the new kernel. The system booted just fine with a > > new kernel a day or so ago (6/12/96). > > Just out of curiousity, have you tried one without DEVFS? > Hmm... I think I have it figured out. If you use the option NFS_NOSERVER, the system won't boot and dumps chow just as it is trying to start init. -Jim From owner-freebsd-current Fri Jun 14 13:12:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13194 for current-outgoing; Fri, 14 Jun 1996 13:12:37 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13188 for ; Fri, 14 Jun 1996 13:12:33 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA22613; Fri, 14 Jun 1996 14:12:32 -0600 Date: Fri, 14 Jun 1996 14:12:32 -0600 From: Nate Williams Message-Id: <199606142012.OAA22613@rocky.sri.MT.net> To: current@FreeBSD.org Subject: Add a special SUP/CTM target for the pc89 stuff? Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is there anyway we could leave the pc89 stuff out of the normal CVS/stable/current sys trees and instead add an additional distribution which would grab the pc89 stuff? We used to do this with the sys_i386 stuff and I suspect that for 99% of the users the pc89 stuff only takes up extra disk space. By adding an additional target *anyone* who wants the files can easily get them, but it's not a required part of the system. When we start adding additional architectures this will start to become a bigger problem, so we may as well start now. :) Thanks! Nate From owner-freebsd-current Fri Jun 14 13:12:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13227 for current-outgoing; Fri, 14 Jun 1996 13:12:59 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13221 for ; Fri, 14 Jun 1996 13:12:52 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA14962; Fri, 14 Jun 1996 13:11:33 -0700 (PDT) To: KATO Takenori cc: current@freebsd.org, FreeBSD@center.nitech.ac.jp Subject: Re: The Great PC98 Merge In-reply-to: Your message of "Sat, 15 Jun 1996 04:27:03 +0900." <199606141927.EAA00370@marble.eps.nagoya-u.ac.jp> Date: Fri, 14 Jun 1996 13:11:33 -0700 Message-ID: <14960.834783093@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > for PC98', may become most common free UNIX-like OS _for PC98_ in > Japan. (Linux for PC98 has not been maintained for a few years, and I notice that you emphasised "for PC98" above - may I ask you just one or two more questions about this machine? 1. How many PC98 machines would you say are being actively used in Japan today? 2. Balanced against the sales of "standard PCs" in Japan, how well has the PC98 marketplace done from 1993 through 1996? What state of affairs would you project for 1997? I'm just trying to get some feel for this machine and its market - we hear virtually nothing about this machine in the United States! :( Thank you! Jordan From owner-freebsd-current Fri Jun 14 15:38:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26810 for current-outgoing; Fri, 14 Jun 1996 15:38:44 -0700 (PDT) Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA26799 for ; Fri, 14 Jun 1996 15:38:38 -0700 (PDT) Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.5/XS4ALL) with ESMTP id AAA21985 for ; Sat, 15 Jun 1996 00:38:32 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id AAA15381 for freebsd-current@freebsd.org; Sat, 15 Jun 1996 00:32:58 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id UAA27101; Fri, 14 Jun 1996 20:05:19 +0200 (MET DST) To: freebsd-current@freebsd.org Subject: PC98?!? From: Peter Mutsaers Lines: 12 X-Newsreader: Gnus v5.2.15/Emacs 19.31 Date: 14 Jun 1996 20:05:17 +0200 Message-ID: <87u3wel0rm.fsf@plm.xs4all.nl> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, the last ctm from cvs-src-cur was quite large and unpacking made /usr/src increase by 4 MB. Almost everything was about PC98. What is PC98, and why do we need it in /usr/src? -- ______________________________________________________________________ Peter Mutsaers | Abcoude (Utrecht), | "Quod licet bovis, plm@xs4all.nl | the Netherlands | non licet Jovi." From owner-freebsd-current Fri Jun 14 15:54:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28382 for current-outgoing; Fri, 14 Jun 1996 15:54:52 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA28356 for ; Fri, 14 Jun 1996 15:54:48 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id PAA11482 for ; Fri, 14 Jun 1996 15:22:20 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA22932; Fri, 14 Jun 1996 16:22:15 -0600 Date: Fri, 14 Jun 1996 16:22:15 -0600 From: Nate Williams Message-Id: <199606142222.QAA22932@rocky.sri.MT.net> To: Naoki Hamada Cc: nate@sri.MT.net, current@freebsd.org Subject: Re: Attention 3C5X9 owners In-Reply-To: <199606140751.QAA09655@sirius.sbl.cl.nec.co.jp> References: <199606101905.NAA09662@rocky.sri.MT.net> <199606140751.QAA09655@sirius.sbl.cl.nec.co.jp> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Nate, your patch still lacks some cases and breaks some important > information. I carefully studied the logic and made the connector > selection scheme a bit clearer and robuster, I hope. IT works for me. I tested out this patch and it works. I guess I'll take the heat if it breaks other folks systems, although given that you've tested it it should work. Also, I want to express my thanks for the PC-CARD patches to if_ep.c. I got them via the Nomad's latest release and they are now part of FreeBSD-current. Thanks! Nate From owner-freebsd-current Fri Jun 14 16:39:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA02850 for current-outgoing; Fri, 14 Jun 1996 16:39:23 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA02838 for ; Fri, 14 Jun 1996 16:39:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id QAA05949; Fri, 14 Jun 1996 16:39:08 -0700 (PDT) Message-Id: <199606142339.QAA05949@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: Jim Lowe , current@freebsd.org Subject: Re: 6/14/96 kernel won't boot In-reply-to: Your message of "Fri, 14 Jun 1996 08:26:40 PDT." <12899.834766000@time.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 14 Jun 1996 16:39:08 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I picked up a new kernel this morning, remade it, and now my system >> won't boot with the new kernel. The system booted just fine with a >> new kernel a day or so ago (6/12/96). > >Just out of curiousity, have you tried one without DEVFS? > >> scprobe: keyboard RESET failed (result = 0xfa) > >Grr. It seems practically _everyone's_ keyboard does this now. Is >anyone even thinking about fixing this? :-( ache, phk and sos were the >last to touch it. Joerg was the one who broke it, however. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Jun 14 18:34:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA10402 for current-outgoing; Fri, 14 Jun 1996 18:34:43 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA10395 for ; Fri, 14 Jun 1996 18:34:39 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA17019; Fri, 14 Jun 1996 21:33:00 -0400 From: Bill Paul Message-Id: <199606150133.VAA17019@skynet.ctr.columbia.edu> Subject: Re: 6/14/96 kernel won't boot To: james@miller.cs.uwm.edu (Jim Lowe) Date: Fri, 14 Jun 1996 21:32:59 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199606142010.PAA19410@miller.cs.uwm.edu> from "Jim Lowe" at Jun 14, 96 03:10:04 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the world, Jim Lowe had to walk into mine and say: > > From: "Jordan K. Hubbard" > > > > > I picked up a new kernel this morning, remade it, and now my system > > > won't boot with the new kernel. The system booted just fine with a > > > new kernel a day or so ago (6/12/96). > > > > Just out of curiousity, have you tried one without DEVFS? > > > > Hmm... I think I have it figured out. If you use the option > NFS_NOSERVER, the system won't boot and dumps chow just as it > is trying to start init. Poul committed my patches to make NFS_NOSERVER work on my system -- I asked for people to test them for me first so that I could commit them later once I was sure they would work without making anything worse. They went in some time last night. You might try backing them out to see if the problem goes away. Look in nfs_socket.c for a function called nfs_timer() and #ifdef it away. Do the same for the call to nfs_timer() in the nfs_init() function, which appears in nfs_subs.c. (Basically, just take nfs_timer() and the reference to it out of the code.) This should negate the effect of my changes. If this makes your kernel work again with the NFS_NOSERVER option, then I screwed up somewhere. (Damned if I know where though.) This is confusing since NFS_NOSERVER doesn't work at all on my system without my hacks, and works perfectly with them. My configuration is different than yours though. - I don't use DEVFS. - I have only an ISA bus. - I have less RAM. - I have no SCSI devices. - I have only an 80386 CPU. - It's an AMD CPU, not Intel. - There's no hardware FPU. Lastly, I'm running the machine completely diskless. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= License error: The license for this .sig file has expired. You must obtain a new license key before any more witty phrases will appear in this space. ============================================================================= From owner-freebsd-current Fri Jun 14 19:43:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA14687 for current-outgoing; Fri, 14 Jun 1996 19:43:16 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA14674 for ; Fri, 14 Jun 1996 19:43:12 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id LAA13083; Sat, 15 Jun 1996 11:42:53 +0900 (JST) Date: Sat, 15 Jun 1996 11:42:52 +0900 (JST) From: Michael Hancock To: Peter Mutsaers cc: freebsd-current@freebsd.org Subject: Re: PC98?!? In-Reply-To: <87u3wel0rm.fsf@plm.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 14 Jun 1996, Peter Mutsaers wrote: > > Hello, > > the last ctm from cvs-src-cur was quite large and unpacking made > /usr/src increase by 4 MB. Almost everything was about PC98. > > What is PC98, and why do we need it in /usr/src? It's a proprietary PC that is used in Japan. Different BUS, different Video standards, etc. The MSDOS machines would always set the drive it booted from to A: even if it is the harddrive. -mh From owner-freebsd-current Fri Jun 14 19:55:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA15674 for current-outgoing; Fri, 14 Jun 1996 19:55:03 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA15664 for ; Fri, 14 Jun 1996 19:55:00 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id UAA23487; Fri, 14 Jun 1996 20:54:58 -0600 Date: Fri, 14 Jun 1996 20:54:58 -0600 From: Nate Williams Message-Id: <199606150254.UAA23487@rocky.sri.MT.net> To: current@FreeBSD.org Subject: NTP gurus Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk OK, I'm trying to actually us the information that Bruce setup to make my system 'more accurate'. (Thanks Paul for putting it under bootverbose though, it's much nicer now). I have a ntp server serving my domain, but it's on the end of a modem which has compression turned on which according to Garrett is a 'bad thing' for ntp. However, the compression does me more good than damage, so I'll leave it on. Understanding that my server may not be completely accurate, I am still using it to keep the rest of the machines in my domain in sync. At most they are a half a minute off from each other, vs. 10's of minutes in the past. Anyway, back to my question. How do I determine 'how accurage' my system's clock is based on /etc/ntp.drift? What are good numbers to have? On my ntp server box (a 486), it currently has a value of '-7.776 0' using the external ntp servers but on my Pentium box with the tweaked parameters using the values from -current, it's value using *only* the local server is '8.548 0'. Is this good? Is this bad? I don't know what is considered good, so can someone tell me a good goal to shoot for? Thanks! Nate From owner-freebsd-current Fri Jun 14 20:01:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA16244 for current-outgoing; Fri, 14 Jun 1996 20:01:01 -0700 (PDT) Received: from intercore.com ([199.181.243.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA16234 for ; Fri, 14 Jun 1996 20:00:57 -0700 (PDT) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id WAA24143 for current@freebsd.org; Fri, 14 Jun 1996 22:57:48 -0400 (EDT) From: Robin Cutshaw Message-Id: <199606150257.WAA24143@intercore.com> Subject: 2.2-960612-SNAP resolver problems To: current@freebsd.org Date: Fri, 14 Jun 1996 22:57:46 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just loaded 2.2-960612-SNAP on a Dell P75/8MB system. The name resolver code doesn't seem to be working correctly. I can see the name request packet going out to the name server and the response coming back but the system doesn't use the returned information. I just blew away the 2.1 release that was working fine on this same box to load the snapshot. It seems like all other networking services are working just fine (routed, rlogind, etc.), it just can't resolve any names. I noticed that the system sends out name queries for localhost as well (so it looks like it's not using /etc/hosts, either). I tried running ktrace but I guess the default kernel isn't configured for it (as I got ktrace: t]?o{]?o]?o]?o: Function not implemented.). robin -- ---- Robin Cutshaw internet: robin@interlabs.com robin@intercore.com Internet Labs, Inc. BellNet: 404-817-9787 "Time is just one damn thing after another" -- PBS/Nova ---- -- From owner-freebsd-current Fri Jun 14 21:42:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24793 for current-outgoing; Fri, 14 Jun 1996 21:42:31 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA24784 for ; Fri, 14 Jun 1996 21:42:28 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA23620; Fri, 14 Jun 1996 22:42:13 -0600 Date: Fri, 14 Jun 1996 22:42:13 -0600 From: Nate Williams Message-Id: <199606150442.WAA23620@rocky.sri.MT.net> To: Robin Cutshaw Cc: current@FreeBSD.org Subject: Re: 2.2-960612-SNAP resolver problems In-Reply-To: <199606150257.WAA24143@intercore.com> References: <199606150257.WAA24143@intercore.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I just loaded 2.2-960612-SNAP on a Dell P75/8MB system. The name resolver > code doesn't seem to be working correctly. I can see the name request > packet going out to the name server and the response coming back but > the system doesn't use the returned information. Hmm, it works for me. FreeBSD nec.sri.MT.net 2.2-CURRENT FreeBSD 2.2-CURRENT #13: Fri Jun 14 18:41:35 MDT 1996 The code is a *little* bit more up-to-date, but the resolver stuff hasn't been touched in months in -current. nec:~ % nslookup ftp.uu.net Server: gateway.sri.MT.net Address: 204.182.243.1 Non-authoritative answer: Name: ftp.uu.net Address: 192.48.96.9 nec:~ % ping ftp.uu.net PING ftp.uu.net (192.48.96.9): 56 data bytes 64 bytes from 192.48.96.9: icmp_seq=0 ttl=241 time=387.362 ms ^C --- ftp.uu.net ping statistics --- 2 packets transmitted, 1 packets received, 50% packet loss round-trip min/avg/max = 387.362/387.362/387.362 ms nec:~ % Looks like it's doing it fine! What does /etc/host.conf look like? Nate From owner-freebsd-current Fri Jun 14 22:00:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA25803 for current-outgoing; Fri, 14 Jun 1996 22:00:11 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA25798 for ; Fri, 14 Jun 1996 22:00:09 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id VAA16127; Fri, 14 Jun 1996 21:59:57 -0700 (PDT) To: Robin Cutshaw cc: current@FreeBSD.org Subject: Re: 2.2-960612-SNAP resolver problems In-reply-to: Your message of "Fri, 14 Jun 1996 22:57:46 EDT." <199606150257.WAA24143@intercore.com> Date: Fri, 14 Jun 1996 21:59:57 -0700 Message-ID: <16125.834814797@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I just loaded 2.2-960612-SNAP on a Dell P75/8MB system. The name resolver > code doesn't seem to be working correctly. I can see the name request > packet going out to the name server and the response coming back but > the system doesn't use the returned information. Anyone else seeing this? My freshly installed 2.2-9606120-SNAP box resolves names just fine and otherwise works as well as it always did (and it did work before :-). Jordan From owner-freebsd-current Sat Jun 15 00:41:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA06060 for current-outgoing; Sat, 15 Jun 1996 00:41:58 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA06051 for ; Sat, 15 Jun 1996 00:41:52 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id IAA13818 for ; Sat, 15 Jun 1996 08:41:43 +0100 (BST) To: current@FreeBSD.ORG From: "Gary Palmer" Subject: Sigh. make world isn't as good as it should be Date: Sat, 15 Jun 1996 08:41:42 +0100 Message-ID: <13816.834824502@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ===> share/doc/papers/memfs indxbib -o ref.bib /usr/src/share/doc/papers/memfs/ref.bib indxbib:fatal error: can't open `/usr/share/dict/eign': No such file or directory *** Error code 3 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. make world >SHOULD< work, even if you just have the bindist installed ... Assuming you have a fully populated /usr/share/dict too is bogus. Adding src/gnu/usr.bin/groff/indxbib to the build-tools target is against recent trends (in reducing make world times) but I think it should be done... comments? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sat Jun 15 01:52:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10220 for current-outgoing; Sat, 15 Jun 1996 01:52:07 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA10185 for ; Sat, 15 Jun 1996 01:52:00 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA05038 for current@freebsd.org; Sat, 15 Jun 1996 18:46:53 +1000 Date: Sat, 15 Jun 1996 18:46:53 +1000 From: Bruce Evans Message-Id: <199606150846.SAA05038@godzilla.zeta.org.au> To: current@freebsd.org Subject: kernel dependency bugs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 1. When an option is removed from conf/options or i386/conf/options.i386, the option isn't removed from the opt_xxx.h header even when other options in the header are changed. This is because config updates the headers in place and goes to a lot of trouble to preserve the parts of them that it doesn't understand. The simpler method of creating temporary headers and renaming the chanegd ones would work better. 2. Config always creates config.c. This breaks recent improvements in option procesing - config was careful not to touch anything if the configuration was unchanged. The more complicated method of creating a temporary config.c and renaming it if there was a change would work better. Bruce From owner-freebsd-current Sat Jun 15 03:35:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA15494 for current-outgoing; Sat, 15 Jun 1996 03:35:07 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15485 for ; Sat, 15 Jun 1996 03:35:01 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id DAA00791; Sat, 15 Jun 1996 03:34:39 -0700 (PDT) Date: Sat, 15 Jun 1996 03:34:39 -0700 (PDT) Message-Id: <199606151034.DAA00791@silvia.HIP.Berkeley.EDU> To: FreeBSD@center.nitech.ac.jp CC: kato@eclogite.eps.nagoya-u.ac.jp, current@FreeBSD.ORG, FreeBSD@center.nitech.ac.jp In-reply-to: <14960.834783093@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: (FreeBSD 4409) Re: The Great PC98 Merge From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (I'm just paraphrasing from the replies to the Japanese mailing list.) * 1. How many PC98 machines would you say are being actively used in * Japan today? * * 2. Balanced against the sales of "standard PCs" in Japan, how well * has the PC98 marketplace done from 1993 through 1996? What state * of affairs would you project for 1997? They're still looking for "hard" numbers, but their (consensus) guess seems to be something like half the PC's sold in Japan in 1995 were PC98's. Most of the rest are AT clones, and some Mac's etc. Satoshi From owner-freebsd-current Sat Jun 15 03:44:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA15671 for current-outgoing; Sat, 15 Jun 1996 03:44:34 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15666 for ; Sat, 15 Jun 1996 03:44:30 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id DAA00936; Sat, 15 Jun 1996 03:44:28 -0700 (PDT) Date: Sat, 15 Jun 1996 03:44:28 -0700 (PDT) Message-Id: <199606151044.DAA00936@silvia.HIP.Berkeley.EDU> To: current@freebsd.org Subject: how to find size of special file From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stupid question du jour: How do you find out a size of a raw or cooked disk partition? Neither the obvious int fd ; struct stat sb ; fd = open(filename, ...) ; stat(fd, &sb) ; size = sb.st_size ; nor the less obvious int fd ; struct stat sb ; fd = open(filename, ...) ; size = lseek(fd, 0, SEEK_END) ; work on special files, even if they are disk partitions. (They both work on regular files....) Satoshi From owner-freebsd-current Sat Jun 15 03:48:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA15783 for current-outgoing; Sat, 15 Jun 1996 03:48:58 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15776 for ; Sat, 15 Jun 1996 03:48:55 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id DAA19642; Sat, 15 Jun 1996 03:48:32 -0700 (PDT) To: Bruce Evans cc: current@freebsd.org Subject: Re: kernel dependency bugs In-reply-to: Your message of "Sat, 15 Jun 1996 18:46:53 +1000." <199606150846.SAA05038@godzilla.zeta.org.au> Date: Sat, 15 Jun 1996 03:48:31 -0700 Message-ID: <19640.834835711@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 2. Config always creates config.c. This breaks recent improvements in > option procesing - config was careful not to touch anything if the > configuration was unchanged. The more complicated method of creating I'll field this one (since I broke it) in the next couple of days if nobody beats me to it. I'm away from my machine at the moment. Jordan From owner-freebsd-current Sat Jun 15 04:34:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21154 for current-outgoing; Sat, 15 Jun 1996 04:34:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA21074 for ; Sat, 15 Jun 1996 04:33:58 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id VAA09411; Sat, 15 Jun 1996 21:28:25 +1000 Date: Sat, 15 Jun 1996 21:28:25 +1000 From: Bruce Evans Message-Id: <199606151128.VAA09411@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, current@FreeBSD.org Subject: Re: how to find size of special file Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >How do you find out a size of a raw or cooked disk partition? Neither There's nothing better than a disklabel ioctl (DIOCGDINFO). See the newfs sources. Bruce From owner-freebsd-current Sat Jun 15 05:21:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22615 for current-outgoing; Sat, 15 Jun 1996 05:21:21 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA22610 for ; Sat, 15 Jun 1996 05:21:06 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA04454 for ; Sat, 15 Jun 1996 14:20:57 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA09904 for freebsd-current@FreeBSD.org; Sat, 15 Jun 1996 14:20:57 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id OAA01643 for freebsd-current@FreeBSD.org; Sat, 15 Jun 1996 14:04:38 +0200 (MET DST) From: J Wunsch Message-Id: <199606151204.OAA01643@uriah.heep.sax.de> Subject: ktrace [Was: 2.2-960612-SNAP resolver problems] To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 15 Jun 1996 14:04:38 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199606150257.WAA24143@intercore.com> from Robin Cutshaw at "Jun 14, 96 10:57:46 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Robin Cutshaw wrote: > I tried running ktrace but I guess the default kernel isn't configured > for it (as I got ktrace: t]?o{]?o]?o]?o: Function not implemented.). I wonder whether we should turn on ktrace by default. It seems to do a fine job, and it might help many people to find out about spurious software troubles (namely about the configuration files that are being searched by programs). Right now, only hard-core hackers are using it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 15 05:24:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22723 for current-outgoing; Sat, 15 Jun 1996 05:24:18 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA22715 for ; Sat, 15 Jun 1996 05:24:12 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA04467; Sat, 15 Jun 1996 14:21:38 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA09923; Sat, 15 Jun 1996 14:21:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id OAA01706; Sat, 15 Jun 1996 14:12:47 +0200 (MET DST) From: J Wunsch Message-Id: <199606151212.OAA01706@uriah.heep.sax.de> Subject: Re: 6/14/96 kernel won't boot To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 15 Jun 1996 14:12:47 +0200 (MET DST) Cc: jkh@time.cdrom.com, davidg@Root.COM, bde@zeta.org.au (Bruce Evans) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199606142339.QAA05949@Root.COM> from David Greenman at "Jun 14, 96 04:39:08 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As David Greenman wrote: > >> scprobe: keyboard RESET failed (result = 0xfa) > > > >Grr. It seems practically _everyone's_ keyboard does this now. Is > >anyone even thinking about fixing this? :-( ache, phk and sos were the > >last to touch it. > > Joerg was the one who broke it, however. ...but Bruce did a good job in timing several keyboards. I was hoping for him... Bruce, should i bump the loop timeout to the latest values you've been mailing me? Shouldn't we better bump all these DELAY(10)'s (perhaps they are the initial source of the evil i've been fixing in rev 1.148)?. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 15 06:07:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA24089 for current-outgoing; Sat, 15 Jun 1996 06:07:36 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA24083; Sat, 15 Jun 1996 06:07:34 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA21718; Sat, 15 Jun 1996 08:07:02 -0500 From: Joe Greco Message-Id: <199606151307.IAA21718@brasil.moneng.mei.com> Subject: Re: Sigh. make world isn't as good as it should be To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Sat, 15 Jun 1996 08:07:02 -0500 (CDT) Cc: current@FreeBSD.ORG In-Reply-To: <13816.834824502@palmer.demon.co.uk> from "Gary Palmer" at Jun 15, 96 08:41:42 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > make world >SHOULD< work, even if you just have the bindist installed > ... Assuming you have a fully populated /usr/share/dict too is bogus. > > Adding src/gnu/usr.bin/groff/indxbib to the build-tools target is > against recent trends (in reducing make world times) but I think it > should be done... comments? Personal opinion: every half a year or so I try to make world on a box that doesn't have quite enough space for one reason or other (generally I let /usr/obj get put under the /usr partition) and so I get "clever" and go mv or rm a bunch of stuff like /usr/share/dict and /usr/share/man expecting everything to continue working.. this sort of unexpected behaviour bites, the world being buildable should have as little to do with the current box's environment as possible. Realizing that nobody is going to make this their continuing mission in life, I've grown to live with it, but I still think it bites. :-) ... JG From owner-freebsd-current Sat Jun 15 06:52:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25525 for current-outgoing; Sat, 15 Jun 1996 06:52:55 -0700 (PDT) Received: from intercore.com (num1sun.intercore.com [199.181.243.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA25519 for ; Sat, 15 Jun 1996 06:52:51 -0700 (PDT) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id JAA27416; Sat, 15 Jun 1996 09:49:35 -0400 (EDT) From: Robin Cutshaw Message-Id: <199606151349.JAA27416@intercore.com> Subject: Re: 2.2-960612-SNAP resolver problems To: nate@sri.MT.net (Nate Williams) Date: Sat, 15 Jun 1996 09:49:33 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199606150442.WAA23620@rocky.sri.MT.net> from "Nate Williams" at Jun 14, 96 10:42:13 pm X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hmm, it works for me. > Maybe I'll try a re-install. I've not seen a problem like this before. > > What does /etc/host.conf look like? > # $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $ # Default is to use the nameserver first bind # If that doesn't work, then try the /etc/hosts file hosts # If you have YP/NIS configured, uncomment the next line # nis It's obviously not using the hosts file as it can't resolve localhost. robin -- ---- Robin Cutshaw internet: robin@interlabs.com robin@intercore.com Internet Labs, Inc. BellNet: 404-817-9787 "Time is just one damn thing after another" -- PBS/Nova ---- -- From owner-freebsd-current Sat Jun 15 07:04:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA25950 for current-outgoing; Sat, 15 Jun 1996 07:04:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA25837 for ; Sat, 15 Jun 1996 07:03:09 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id XAA14170; Sat, 15 Jun 1996 23:58:44 +1000 Date: Sat, 15 Jun 1996 23:58:44 +1000 From: Bruce Evans Message-Id: <199606151358.XAA14170@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: 6/14/96 kernel won't boot Cc: bde@zeta.org.au, davidg@Root.COM, jkh@time.cdrom.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >> scprobe: keyboard RESET failed (result = 0xfa) >> ... >> Joerg was the one who broke it, however. >...but Bruce did a good job in timing several keyboards. I was hoping >for him... Bruce, should i bump the loop timeout to the latest values >you've been mailing me? Shouldn't we better bump all these >DELAY(10)'s (perhaps they are the initial source of the evil i've been >fixing in rev 1.148)?. At least one keyboard requires about 250 ms. This seems excessive already so I was going to try 1000 ms maximum. It wouldn't hurt to change the DELAY(10)'s to DELAY(1000)'s and reduce the counts proportionally, but this is only easy in part of the reset code - there are some DELAY(10)'s in kbd_wait(), and it's more important for the delays to be right in the main code. It wouldn't hurt to read the keyboad data buffer only when there is new data in it... Bruce From owner-freebsd-current Sat Jun 15 07:21:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA26479 for current-outgoing; Sat, 15 Jun 1996 07:21:18 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA26473 for ; Sat, 15 Jun 1996 07:21:12 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA07085; Sat, 15 Jun 1996 16:20:41 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA10720; Sat, 15 Jun 1996 16:20:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id PAA03498; Sat, 15 Jun 1996 15:50:57 +0200 (MET DST) From: J Wunsch Message-Id: <199606151350.PAA03498@uriah.heep.sax.de> Subject: Re: UIDs greater than 65535 ? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 15 Jun 1996 15:50:56 +0200 (MET DST) Cc: james@expresslane.ca (James FitzGibbon) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from James FitzGibbon at "Jun 13, 96 12:08:05 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As James FitzGibbon wrote: > But pw_scan.c uses this check routine : > > if (id > USHRT_MAX) { > warnx("%s > max uid value (%d)", p, USHRT_MAX); > return (0); > } > > So that although a userid can have a 32-bit value, the password scanning > routines won't allow anything higher than 16 bit. > > Is this just an oversight (i.e. can we just change the constant in > pw_scan.c? ) or are there other reasons why the UIDs are limited to 16-bit > ? I think that's for hysterical raisons. Perhaps older (unsupported) file systems like SYSVFS might break, as well as Yellow Plague. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 15 07:32:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA27073 for current-outgoing; Sat, 15 Jun 1996 07:32:41 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA27053 for ; Sat, 15 Jun 1996 07:32:27 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA07280; Sat, 15 Jun 1996 16:31:20 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA10771; Sat, 15 Jun 1996 16:31:20 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id QAA03774; Sat, 15 Jun 1996 16:27:28 +0200 (MET DST) From: J Wunsch Message-Id: <199606151427.QAA03774@uriah.heep.sax.de> Subject: Re: 6/14/96 kernel won't boot To: bde@zeta.org.au (Bruce Evans) Date: Sat, 15 Jun 1996 16:27:27 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org, bde@zeta.org.au, davidg@Root.COM, jkh@time.cdrom.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199606151358.XAA14170@godzilla.zeta.org.au> from Bruce Evans at "Jun 15, 96 11:58:44 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > At least one keyboard requires about 250 ms. This seems excessive > already so I was going to try 1000 ms maximum. It wouldn't hurt to > change the DELAY(10)'s to DELAY(1000)'s and reduce the counts > proportionally, but this is only easy in part of the reset code - > there are some DELAY(10)'s in kbd_wait(), and it's more important > for the delays to be right in the main code. Hmm, shouldn't they be at least DELAY(20)'s or so? I suspect one of the reasons why some of the keyboards broke with the old code (which was my main reason to change it) is that the new i586+ machines are too fast so the assumed overhead for small DELAY's turned almost into nop's. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 15 08:07:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28899 for current-outgoing; Sat, 15 Jun 1996 08:07:28 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA28894 for ; Sat, 15 Jun 1996 08:07:23 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id BAA16190; Sun, 16 Jun 1996 01:02:49 +1000 Date: Sun, 16 Jun 1996 01:02:49 +1000 From: Bruce Evans Message-Id: <199606151502.BAA16190@godzilla.zeta.org.au> To: bde@zeta.org.au, j@uriah.heep.sax.de Subject: Re: 6/14/96 kernel won't boot Cc: davidg@Root.COM, freebsd-current@FreeBSD.org, jkh@time.cdrom.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> change the DELAY(10)'s to DELAY(1000)'s and reduce the counts >> proportionally, but this is only easy in part of the reset code - >> there are some DELAY(10)'s in kbd_wait(), and it's more important >> for the delays to be right in the main code. >Hmm, shouldn't they be at least DELAY(20)'s or so? I suspect one of >the reasons why some of the keyboards broke with the old code (which >was my main reason to change it) is that the new i586+ machines are >too fast so the assumed overhead for small DELAY's turned almost into >nop's. The old code waited forever, and the main code is more vulnerable to too-short delays than the reset code. DELAY(n) only guarantees to delay for >= (n - 20)us, so expecting DELAY(10) to delay for 10us isn't good. In practice, the minumum delay is a few microseconds unless you have very fast i8254 registers. DELAY(10) takes about 4us on my ASUS P133, mostly for accessing the i8254. TImeouts are usually many times larger than necessary so no problems are caused by reducing them by a factor of < 10. Bruce From owner-freebsd-current Sat Jun 15 08:48:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA00858 for current-outgoing; Sat, 15 Jun 1996 08:48:08 -0700 (PDT) Received: from intercore.com (num1sun.intercore.com [199.181.243.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA00850 for ; Sat, 15 Jun 1996 08:48:06 -0700 (PDT) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id LAA27887; Sat, 15 Jun 1996 11:44:44 -0400 (EDT) From: Robin Cutshaw Message-Id: <199606151544.LAA27887@intercore.com> Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 15 Jun 1996 11:44:43 -0400 (EDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199606151204.OAA01643@uriah.heep.sax.de> from "J Wunsch" at Jun 15, 96 02:04:38 pm X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I wonder whether we should turn on ktrace by default. It seems to do > a fine job, and it might help many people to find out about spurious > software troubles (namely about the configuration files that are being > searched by programs). Right now, only hard-core hackers are using > it. > I'd vote yes. I can't count the number of times that truss has pointed out problems on solaris systems for me. robin From owner-freebsd-current Sat Jun 15 08:59:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01351 for current-outgoing; Sat, 15 Jun 1996 08:59:34 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01342 for ; Sat, 15 Jun 1996 08:59:31 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.4+2.6Wbeta6/3.3W9) with ESMTP id AAA00470; Sun, 16 Jun 1996 00:59:19 +0900 (JST) Message-Id: <199606151559.AAA00470@marble.eps.nagoya-u.ac.jp> To: current@freebsd.org Cc: FreeBSD@center.nitech.ac.jp, jkh@time.cdrom.com Subject: Re: The Great PC98 Merge In-Reply-To: Your message of "Fri, 14 Jun 1996 13:11:33 -0700" References: <14960.834783093@time.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.1, Mule 2.3 X-PGP-Fingerprint: CA 87 00 60 BB BA 0C 81 A8 FB AA 6A 3A B0 38 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 16 Jun 1996 00:59:17 +0900 From: KATO Takenori Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1. How many PC98 machines would you say are being actively used in > Japan today? > > 2. Balanced against the sales of "standard PCs" in Japan, how well > has the PC98 marketplace done from 1993 through 1996? What state > of affairs would you project for 1997? I apologize for showing only speculation. I have not yet found how many PC98 and IBM-PC clones were sold in Japan. I am looking for the information now. I speculate that: 1. Untile middle of 1994, much more than half of PC's were PC98 and its compatible machines in Japan. 2. Since then, IBM-PC clones have rapidly extended their market share. 3. 40 to 50% of the PC's sold in Japan were PC98 in 1995. 4. I still found many PC98 computers and many people bought them in this year in Japan. (I also found many IBM-PC clones.) > > for PC98', may become most common free UNIX-like OS _for PC98_ in > > Japan. (Linux for PC98 has not been maintained for a few years, and > > I notice that you emphasised "for PC98" above - may I ask you just one > or two more questions about this machine? Why I emphasised PC98 in the above sentence is that almost all of PC98 users can choice only *BSD, but IBM-PC clone users can choice not only *BSD but Linux. I think the number of Linux users is grater than that of *BSD users. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan Voice: +81-52-789-2529 Fax: +81-52-789-3033 From owner-freebsd-current Sat Jun 15 09:27:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02660 for current-outgoing; Sat, 15 Jun 1996 09:27:10 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA02655 for ; Sat, 15 Jun 1996 09:27:07 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA24720; Sat, 15 Jun 1996 10:26:57 -0600 Date: Sat, 15 Jun 1996 10:26:57 -0600 From: Nate Williams Message-Id: <199606151626.KAA24720@rocky.sri.MT.net> To: Robin Cutshaw Cc: nate@sri.MT.net (Nate Williams), current@freebsd.org Subject: Re: 2.2-960612-SNAP resolver problems In-Reply-To: <199606151349.JAA27416@intercore.com> References: <199606150442.WAA23620@rocky.sri.MT.net> <199606151349.JAA27416@intercore.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ DNS in -current ] > > > > Hmm, it works for me. > > > > Maybe I'll try a re-install. I've not seen a problem like this before. > > > > > What does /etc/host.conf look like? > > > > # $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $ > # Default is to use the nameserver first > bind > # If that doesn't work, then try the /etc/hosts file > hosts > # If you have YP/NIS configured, uncomment the next line > # nis > > It's obviously not using the hosts file as it can't resolve localhost. What does nslookup do? Nate From owner-freebsd-current Sat Jun 15 09:34:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02899 for current-outgoing; Sat, 15 Jun 1996 09:34:39 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA02894 for ; Sat, 15 Jun 1996 09:34:35 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA24752; Sat, 15 Jun 1996 10:33:59 -0600 Date: Sat, 15 Jun 1996 10:33:59 -0600 From: Nate Williams Message-Id: <199606151633.KAA24752@rocky.sri.MT.net> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users) Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] In-Reply-To: <199606151204.OAA01643@uriah.heep.sax.de> References: <199606150257.WAA24143@intercore.com> <199606151204.OAA01643@uriah.heep.sax.de> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I tried running ktrace but I guess the default kernel isn't configured > > for it (as I got ktrace: t]?o{]?o]?o]?o: Function not implemented.). > > I wonder whether we should turn on ktrace by default. Earlier on, people were having problems that were solved by removing KTRACE from their config file. I'd rather not, but I think fixing the error message to be more intuitive would be a win. In -stable it's much better. gateway:/usr/src/usr.bin/telnet # ktrace foo ktrace: ktrace not enabled in kernel,to use ktrace you need to add a line "options KTRACE" to your kernel Nate From owner-freebsd-current Sat Jun 15 10:09:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA04854 for current-outgoing; Sat, 15 Jun 1996 10:09:00 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA04849 for ; Sat, 15 Jun 1996 10:08:58 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id KAA21371; Sat, 15 Jun 1996 10:08:41 -0700 (PDT) To: KATO Takenori cc: current@freebsd.org, FreeBSD@center.nitech.ac.jp Subject: Re: The Great PC98 Merge In-reply-to: Your message of "Sun, 16 Jun 1996 00:59:17 +0900." <199606151559.AAA00470@marble.eps.nagoya-u.ac.jp> Date: Sat, 15 Jun 1996 10:08:41 -0700 Message-ID: <21369.834858521@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I apologize for showing only speculation. I have not yet found how > many PC98 and IBM-PC clones were sold in Japan. I am looking for the > information now. Your speculations were most valuable, thank you! > Why I emphasised PC98 in the above sentence is that almost all of PC98 > users can choice only *BSD, but IBM-PC clone users can choice not only > *BSD but Linux. I think the number of Linux users is grater than that Ah, understood! One final question, if you would be so kind - how do you currently do your releases? If there are reasonable changes we can make there to accomodate you, it might be arranged! Thanks.. Jordan From owner-freebsd-current Sat Jun 15 10:40:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06243 for current-outgoing; Sat, 15 Jun 1996 10:40:36 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA06232 for ; Sat, 15 Jun 1996 10:40:33 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA25187; Sat, 15 Jun 1996 13:40:24 -0400 Date: Sat, 15 Jun 1996 13:40:24 -0400 From: Garrett Wollman Message-Id: <9606151740.AA25187@halloran-eldar.lcs.mit.edu> To: Nate Williams Cc: current@FreeBSD.org Subject: NTP gurus In-Reply-To: <199606150254.UAA23487@rocky.sri.MT.net> References: <199606150254.UAA23487@rocky.sri.MT.net> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > Anyway, back to my question. How do I determine 'how accurage' my > system's clock is based on /etc/ntp.drift? What are good numbers to > have? Actually, the best thing to look at (because it's updated on an on-going basis) is the output of `ntpq -c rv'. For example, on my system: wollman@khavrinen(62)$ ntpq -c rv status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg system="FreeBSD", leap=00, stratum=3, rootdelay=27.08, rootdispersion=14.30, peer=61525, refid=amsterdam.lcs.mit.edu, reftime=b56d6d78.705ad000 Sat, Jun 15 1996 13:12:24.438, poll=6, clock=b56d6d7e.bf068000 Sat, Jun 15 1996 13:12:30.746, phase=4.362, freq=27394.97, error=3.20 The `freq=' number is the frequency error, although measured in odd units. Multiply by 86400/1024, and you have the error in microseconds per day. (As given, the `freq' is in 2^-10 us/s.) In my case, my clock is about two seconds per day fast (slow?). (I could use Greg Troxel's ``time surveying'' code over the course of a few months for a much more definite and accurate idea of the characteristics of my hardware oscillator, and of the quality of the servers I am using.) Some other useful things in this listing... `rootdelay' and `rootdispersion' give an estimate of the actual quality of time service relative to the authoritative time source(s) which are at the root of the distribution tree. `poll' is the polling interval, in log2 seconds. `phase' is the actual current estimated phase error between your system clock and what it thinks the current time is; `error' is an indication of how accurate the phase and frequency measurements are thought to be. `phase' and `poll' are also available in the `ntpq -p' display. The difference between the nominal and measured frequency of the timer (as determined by Bruce's code) is about 10 ns in the period of the oscillator (which is about 838.1 us); by my calculation, this could account for about one second per day. I suspect that there is enough hour-to-hour variation in the oscillator for this difference to make no matter. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Sat Jun 15 11:39:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08399 for current-outgoing; Sat, 15 Jun 1996 11:39:52 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA08394 for ; Sat, 15 Jun 1996 11:39:50 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA24995; Sat, 15 Jun 1996 12:39:35 -0600 Date: Sat, 15 Jun 1996 12:39:35 -0600 From: Nate Williams Message-Id: <199606151839.MAA24995@rocky.sri.MT.net> To: Garrett Wollman Cc: Nate Williams , current@FreeBSD.org Subject: Re: NTP gurus In-Reply-To: <9606151740.AA25187@halloran-eldar.lcs.mit.edu> References: <199606150254.UAA23487@rocky.sri.MT.net> <9606151740.AA25187@halloran-eldar.lcs.mit.edu> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Garrett Wollman writes: > < said: > > > Anyway, back to my question. How do I determine 'how accurage' my > > system's clock is based on /etc/ntp.drift? What are good numbers to > > have? > > Actually, the best thing to look at (because it's updated on an > on-going basis) is the output of `ntpq -c rv'. For example, on my > system: [ Excellent description deleted ] Wonderful! Thanks for the great description Garrett. > freq=27394.97, error=3.20 So does that mean that my box is pretty accurate then? freq=1636.28, error=0.08 I'm setting machdep.i8254_freq equal to the number kicked out by the clock stuff Bruce used, which implies to me (using the above numbers) that the clock is fairly accurate on this box. In any case, it's much more accurate than the clock on my 'ntp server' box. freq=-13014.10, error=6.74 Thanks! Nate From owner-freebsd-current Sat Jun 15 13:21:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13714 for current-outgoing; Sat, 15 Jun 1996 13:21:38 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13704 for ; Sat, 15 Jun 1996 13:21:26 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA14254 for ; Sat, 15 Jun 1996 22:21:17 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA14181 for freebsd-current@FreeBSD.org; Sat, 15 Jun 1996 22:21:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA20827 for freebsd-current@FreeBSD.org; Sat, 15 Jun 1996 22:05:12 +0200 (MET DST) From: J Wunsch Message-Id: <199606152005.WAA20827@uriah.heep.sax.de> Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 15 Jun 1996 22:05:12 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199606151633.KAA24752@rocky.sri.MT.net> from Nate Williams at "Jun 15, 96 10:33:59 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > > I wonder whether we should turn on ktrace by default. > > Earlier on, people were having problems that were solved by removing > KTRACE from their config file. Except of a recent brokeness in -current (that only affected people actually using it), i cannot remember such problems. I used to have it in my config file for several months if not years now. gzip used to be absolutely broken for quite a longer period of time, and nobody complained that it was still in the GENERIC config file. :) Does anybody seriously object against putting it into GENERIC? (I will see whether it causes problems for the BOOTMFS kernel, but it can always be avoided there without too much trouble.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 15 13:39:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15024 for current-outgoing; Sat, 15 Jun 1996 13:39:00 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA15013 for ; Sat, 15 Jun 1996 13:38:54 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA25158; Sat, 15 Jun 1996 14:35:07 -0600 Date: Sat, 15 Jun 1996 14:35:07 -0600 From: Nate Williams Message-Id: <199606152035.OAA25158@rocky.sri.MT.net> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] In-Reply-To: <199606152005.WAA20827@uriah.heep.sax.de> References: <199606151633.KAA24752@rocky.sri.MT.net> <199606152005.WAA20827@uriah.heep.sax.de> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > I wonder whether we should turn on ktrace by default. > > > > Earlier on, people were having problems that were solved by removing > > KTRACE from their config file. > > Except of a recent brokeness in -current (that only affected people > actually using it), i cannot remember such problems. I used to have > it in my config file for several months if not years now. Actually, it affected people *NOT* using it. Even if you didn't use ktrace things were broken because of it. > gzip used to be absolutely broken for quite a longer period of time, > and nobody complained that it was still in the GENERIC config file. :) That's because it was required in GENERIC for the install utils. > Does anybody seriously object against putting it into GENERIC? Yes. It's un-necessary bloat that 95% of the users don't know how to use and the other 5% know how to add it. Nate From owner-freebsd-current Sat Jun 15 15:53:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA20602 for current-outgoing; Sat, 15 Jun 1996 15:53:28 -0700 (PDT) Received: from centauro.isr.uc.pt ([193.136.205.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA20590 for ; Sat, 15 Jun 1996 15:53:14 -0700 (PDT) Received: by centauro.isr.uc.pt (4.1/SMI-4.1) id AA03037; Sat, 15 Jun 96 23:53:02 +0100 Date: Sat, 15 Jun 1996 23:53:01 +0100 (WET DST) From: Paulo Menezes To: current@FreeBSD.org Subject: Localtime for Portugal Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, The localtime for Portugal is not correct, the FreeBSD machines running current or stable are showing an error of -1 hour. I am not familiar with the format of the localtime files but I have tryed and a little modification and it corrects this error. I am not sure if it is going to be correct in winter time but here goes my patch. *** europe.old Sat Jun 15 23:31:26 1996 --- europe Sat Jun 15 23:30:11 1996 *************** *** 1720,1726 **** # Martin Bruckmann (1996-02-29) reports via Peter Ilieve # that Portugal is reverting to 0:00 by not moving its clocks this spring. # The new Prime Minister was fed up with getting up in the dark in the winter. ! 0:00 - "WET DST" 1996 Oct 27 1:00u 0:00 EC WET%s # We don't know what happened to Madeira or the Azores, # so we'll just use Shanks for now. --- 1720,1726 ---- # Martin Bruckmann (1996-02-29) reports via Peter Ilieve # that Portugal is reverting to 0:00 by not moving its clocks this spring. # The new Prime Minister was fed up with getting up in the dark in the winter. ! # 0:00 - "WET DST" 1996 Oct 27 1:00u 0:00 EC WET%s # We don't know what happened to Madeira or the Azores, # so we'll just use Shanks for now. Paulo Menezes From owner-freebsd-current Sat Jun 15 16:24:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24097 for current-outgoing; Sat, 15 Jun 1996 16:24:25 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA24089 for ; Sat, 15 Jun 1996 16:24:21 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA17989; Sun, 16 Jun 1996 01:23:19 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA16729; Sun, 16 Jun 1996 01:23:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id AAA01600; Sun, 16 Jun 1996 00:57:13 +0200 (MET DST) From: J Wunsch Message-Id: <199606152257.AAA01600@uriah.heep.sax.de> Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 16 Jun 1996 00:57:12 +0200 (MET DST) Cc: nate@sri.MT.net (Nate Williams) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199606152035.OAA25158@rocky.sri.MT.net> from Nate Williams at "Jun 15, 96 02:35:07 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > > Except of a recent brokeness in -current (that only affected people > > actually using it), i cannot remember such problems. I used to have > > it in my config file for several months if not years now. > > Actually, it affected people *NOT* using it. Even if you didn't use > ktrace things were broken because of it. Which brokeness? As i wrote, i've got the option in my own config files for months now, and have never observed any ill side-effects. (I don't neglect that it might have caused problems earlier, but not lately.) > > gzip used to be absolutely broken for quite a longer period of time, > > and nobody complained that it was still in the GENERIC config file. :) > > That's because it was required in GENERIC for the install utils. Nope. It was only used for the fixit floppy, and all 2.2 SNAPs before the May 1st one have an unusable fixit. The installation itself doesn't use it. (Hence the comment in GENERIC about sysinstall not being able to run without it is bogus.) > > Does anybody seriously object against putting it into GENERIC? > > Yes. It's un-necessary bloat that 95% of the users don't know how to > use and the other 5% know how to add it. That's not true. It's relatively easy to teach people about running their program with a prepended `ktrace'. It's much harder to demand from them to first recompile a new kernel. (And i can't answer their questions then why it's not in the default kernel. :) Many other systems around ship with it enabled and ready to run by default, including all SysV's (truss) and Linux (strace). The bloat is 4 KB, nothing i would consider undue: text data bss dec hex 1114112 69632 76312 1260056 133a18 kernel 1118208 69632 76312 1264152 134a18 kernel.ktrace (Both are GENERIC kernels.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 15 16:52:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24774 for current-outgoing; Sat, 15 Jun 1996 16:52:21 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA24769 for ; Sat, 15 Jun 1996 16:52:19 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA26961; Sat, 15 Jun 1996 19:51:31 -0400 Date: Sat, 15 Jun 1996 19:51:31 -0400 From: Garrett Wollman Message-Id: <9606152351.AA26961@halloran-eldar.lcs.mit.edu> To: Paulo Menezes Cc: current@FreeBSD.org Subject: Localtime for Portugal In-Reply-To: References: Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > The localtime for Portugal is not correct, the FreeBSD machines running > current or stable are showing an error of -1 hour. > I am not familiar with the format of the localtime files but I have tryed > and a little modification and it corrects this error. I am not sure if it > is going to be correct in winter time but here goes my patch. I am aware of this problem, and will update the timezone code soon (hopefully before the end of the month). -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Sat Jun 15 18:24:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28804 for current-outgoing; Sat, 15 Jun 1996 18:24:03 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA28765 for ; Sat, 15 Jun 1996 18:24:00 -0700 (PDT) Received: from socrate (ts1port12d.masternet.it [194.184.65.34]) by masternet.it (8.6.12/8.6.9) with SMTP id CAA24900; Sun, 16 Jun 1996 02:21:55 +0200 Message-ID: <31C36DEA.41C67EA6@masternet.it> Date: Sun, 16 Jun 1996 04:14:02 +0200 From: Beck Peccoz Amedeo X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: freebsd-current@FreeBSD.ORG Subject: ahc sincing questions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just a couple of silly doubts about the ahc driver... While starting up the kernel with the -v option the ahc driver reports the sinc speed for any attached scsi device in MHz. Shouldn't be in Mbytes/s? Why I see no difference when enable the ultra speed? My HD can sinc at 20 Mbytes/s, but it actually sincs only at 10... what's wrong? Cheers -- Beck-Peccoz Amedeo GEA Software S.r.l. Via Deffeyes, 1 11025 Gressoney Saint Jean (AO) ITALY Tel. ++39-125-366302 Fax. ++39-125-366415 From owner-freebsd-current Sat Jun 15 19:22:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01674 for current-outgoing; Sat, 15 Jun 1996 19:22:20 -0700 (PDT) Received: from intercore.com (num1sun.intercore.com [199.181.243.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01666 for ; Sat, 15 Jun 1996 19:22:13 -0700 (PDT) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id WAA02070; Sat, 15 Jun 1996 22:18:52 -0400 (EDT) From: Robin Cutshaw Message-Id: <199606160218.WAA02070@intercore.com> Subject: Re: 2.2-960612-SNAP resolver problems To: nate@sri.MT.net (Nate Williams) Date: Sat, 15 Jun 1996 22:18:50 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199606151626.KAA24720@rocky.sri.MT.net> from "Nate Williams" at Jun 15, 96 10:26:57 am X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > What does nslookup do? > It complains that it can't reverse resolve the nameserver's IP address and exits. I played with this for quite a while today. I re-installed after making a new boot image. The NFS-based install failed when trying to resolve the hostname to mount. I then used an FTP install and it failed trying to resolve the ftp host name. After the NFS failed again, I tried NFS back-to-back and it worked. After booting, I got the same name resolver problems. So, more playing. The box has a dec 21140 10/100 card running at 10 for the primary network interface. It also has a dual 21040 card for secondary networks. I pulled the 21140 and made one of the other interfaces the primary and noticed that is was enabled on boot but when the "uha0" was probed (and not found), the interface went down. After removing the uha0 entry, I rebooted with the original configuration and now everything works fine. How the uha0 probe would affect only the dns lookups via the 21140 board is beyond me. Well, it works now... robin From owner-freebsd-current Sat Jun 15 19:23:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01719 for current-outgoing; Sat, 15 Jun 1996 19:23:37 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA01713 for ; Sat, 15 Jun 1996 19:23:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id TAA18282 for ; Sat, 15 Jun 1996 19:23:30 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA00203; Sun, 16 Jun 1996 12:11:38 +1000 Date: Sun, 16 Jun 1996 12:11:38 +1000 From: Bruce Evans Message-Id: <199606160211.MAA00203@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] Cc: nate@sri.MT.net Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > Does anybody seriously object against putting it into GENERIC? >> >> Yes. It's un-necessary bloat that 95% of the users don't know how to >> use and the other 5% know how to add it. >That's not true. It's relatively easy to teach people about running >their program with a prepended `ktrace'. It's much harder to demand >from them to first recompile a new kernel. (And i can't answer their >questions then why it's not in the default kernel. :) Many other >systems around ship with it enabled and ready to run by default, >including all SysV's (truss) and Linux (strace). Strace seems to be more in the library. Its output is much better. >The bloat is 4 KB, nothing i would consider undue: >text data bss dec hex >1114112 69632 76312 1260056 133a18 kernel >1118208 69632 76312 1264152 134a18 kernel.ktrace 95% of the drivers in GENERIC are unused. Runtime bloat for calling the ktrace hooks for all syscalls is more of a concern, but the fix is the same: don't run GENERIC if you want a small and fast kernel. GENERIC has other options such as FAILSAFE that might eventually cost a lot of time and space to give more robustness. Bruce From owner-freebsd-current Sat Jun 15 19:25:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01844 for current-outgoing; Sat, 15 Jun 1996 19:25:25 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01825; Sat, 15 Jun 1996 19:25:18 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id WAA03849; Sat, 15 Jun 1996 22:25:20 -0400 (EDT) Date: Sat, 15 Jun 1996 22:25:19 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: multimedia@freebsd.org Subject: Audio control with an Gravis Ultrasound Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I just installed a friends Gravis Ultrasound into my -current machine, with a Mitsumi CDrom player, and I can get sound *through* the Gravis Ultrasound, but I can't seem to control volume. I've tried using 'xcd', which has volume control, and it starts up saying that volume == 0, when I can hear the sound no problem. I've done a "MAKEDEV snd0" in /dev, to create the appropriate devices... *What* am I missing? Everything is being recognized when the system boots as well... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sat Jun 15 19:52:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03393 for current-outgoing; Sat, 15 Jun 1996 19:52:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA03379 for ; Sat, 15 Jun 1996 19:52:26 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA01710; Sun, 16 Jun 1996 12:47:40 +1000 Date: Sun, 16 Jun 1996 12:47:40 +1000 From: Bruce Evans Message-Id: <199606160247.MAA01710@godzilla.zeta.org.au> To: nate@sri.MT.net, wollman@lcs.mit.edu Subject: Re: NTP gurus Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The difference between the nominal and measured frequency of the timer period >(as determined by Bruce's code) is about 10 ns in the period of the >oscillator (which is about 838.1 us); by my calculation, this could >account for about one second per day. The oscillator period is actually about 838.1 ns. The difference needs to be 10/1000 ns to be consistent with this and a drift of 1 second/day. On one of my systems, the difference between the periods is about 64 times as large - far too large. The (rtc) reference clock seems to be accurate to 1 second per day or better, so using the measured frequency reduces the drift from about 64 seconds/day to only a few seconds/day. >I suspect that there is enough >hour-to-hour variation in the oscillator for this difference to make >no matter. I hope the hour-to-hour variation is quite small and the long term variation is smaller. However, the current code has a builtin rounding error of between -0.5 and 0.5 parts per (timer_freq/hz), because the timer frequency has to be converted to a maximum count of approximately (timer_freq/hz) and the fractional part is discarded. For the usual timer_freq and hz, this translates to an error of up to 41 parts/million = 3.5 seconds/day. 1 second/day is already better than you should expect. (You could expect better if the nominal timer_freq is a multiple of hz, but it isn't.). Bruce From owner-freebsd-current Sat Jun 15 21:02:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA10448 for current-outgoing; Sat, 15 Jun 1996 21:02:58 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA10443 for ; Sat, 15 Jun 1996 21:02:56 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id VAA18829; Sat, 15 Jun 1996 21:02:24 -0700 (PDT) Message-Id: <199606160402.VAA18829@ref.tfs.com> Subject: Re: UIDs greater than 65535 ? To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 15 Jun 1996 21:02:24 -0700 (PDT) From: "JULIAN Elischer" Cc: freebsd-current@FreeBSD.org, james@expresslane.ca In-Reply-To: <199606151350.PAA03498@uriah.heep.sax.de> from "J Wunsch" at Jun 15, 96 03:50:56 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > As James FitzGibbon wrote: > > > But pw_scan.c uses this check routine : > > > > if (id > USHRT_MAX) { > > warnx("%s > max uid value (%d)", p, USHRT_MAX); > > return (0); > > } > > > > So that although a userid can have a 32-bit value, the password scanning > > routines won't allow anything higher than 16 bit. > > > > Is this just an oversight (i.e. can we just change the constant in > > pw_scan.c? ) or are there other reasons why the UIDs are limited to 16-bit > > ? > > I think that's for hysterical raisons. Perhaps older (unsupported) > file systems like SYSVFS might break, as well as Yellow Plague. We currently modify this to complain, but continue working at my present employer.. I think I would like to submit a patch to make thios standard because we need UIDs > 16 bits and it IS legal but sometimes undesirable.. therefore it should be possible but annoying.. i.e. complains but continues... julian(E) > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-current Sat Jun 15 23:35:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA19570 for current-outgoing; Sat, 15 Jun 1996 23:35:40 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA19559; Sat, 15 Jun 1996 23:35:37 -0700 (PDT) Message-Id: <199606160635.XAA19559@freefall.freebsd.org> To: Beck Peccoz Amedeo cc: freebsd-current@FreeBSD.ORG Subject: Re: ahc sincing questions In-reply-to: Your message of "Sun, 16 Jun 1996 04:14:02 +0200." <31C36DEA.41C67EA6@masternet.it> Date: Sat, 15 Jun 1996 23:35:36 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Just a couple of silly doubts about the ahc driver... > > While starting up the kernel with the -v option the ahc driver >reports the sinc speed for any attached scsi device in MHz. >Shouldn't be in Mbytes/s? MHz is correct. The sync rate is a measure of the clock rate at which data is transfered. Only when you multiply that by the bus width, do you get MBytes/s. > Why I see no difference when enable the ultra speed? My HD can >sinc at 20 Mbytes/s, but it actually sincs only at 10... what's >wrong? If you have a Wide drive, it does 10Mhz sync on a 16bit bus. If you have an 8bit device, it must do 20Mhz sync in order to do 20MB/s. What is your drive model? The only Ultra drive I know of on the market is a Seagate one, and the person who tried it said it refused to negotiate 20Mhz sync (looking from a SCSI bus analyzer) and that it was the device's fault and not the driver's. > Cheers > >-- > >Beck-Peccoz Amedeo >GEA Software S.r.l. >Via Deffeyes, 1 >11025 Gressoney Saint Jean (AO) >ITALY > >Tel. ++39-125-366302 Fax. ++39-125-366415 > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sat Jun 15 23:47:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA20607 for current-outgoing; Sat, 15 Jun 1996 23:47:31 -0700 (PDT) Received: from felix.antiquity.arts.su.edu.au (felix.antiquity.arts.su.edu.AU [129.78.16.135]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA20598 for ; Sat, 15 Jun 1996 23:47:28 -0700 (PDT) Received: (from patc@localhost) by felix.antiquity.arts.su.edu.au (8.7.4/8.7.3) id QAA19860; Sun, 16 Jun 1996 16:56:11 +1000 From: Pat Caldon Message-Id: <199606160656.QAA19860@felix.antiquity.arts.su.edu.au> Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 16 Jun 1996 16:56:09 +1000 (EST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199606151204.OAA01643@uriah.heep.sax.de> from "J Wunsch" at Jun 15, 96 02:04:38 pm Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I tried running ktrace but I guess the default kernel isn't configured > > for it (as I got ktrace: t]?o{]?o]?o]?o: Function not implemented.). > > I wonder whether we should turn on ktrace by default. It seems to do > a fine job, and it might help many people to find out about spurious > software troubles (namely about the configuration files that are being > searched by programs). Right now, only hard-core hackers are using Yes! as a recent convert to FreeBSD about a year ago I was trying to debug some wierdnesses in a httpd and ktrace was invaluable, after I got it working. Which only took hours as I had to build my first kernel. It should be in GENERIC like this: options KTRACE # Kernel Tracing; adds ~4k to kernel pat.