From owner-freebsd-current Sun Aug 4 00:23:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA18475 for current-outgoing; Sun, 4 Aug 1996 00:23:10 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA18458 for ; Sun, 4 Aug 1996 00:22:54 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id JAA04625; Sun, 4 Aug 1996 09:22:20 +0200 (SAT) Message-Id: <199608040722.JAA04625@grumble.grondar.za> To: Bill Paul cc: current@freebsd.org Subject: Re: NIS Setup Question Date: Sun, 04 Aug 1996 09:22:19 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bill Paul wrote: > > > Problem with the SNAP? Dunno. I run -current, and I have that man page. > > > What does man -k nis give? > > It should give nothing. Man -k nis will only be of interest if and > when I finish NIS+. Pardon? :-) $ man -k nis divert(4) - kernel packet diversion mechanism domainname(1) - set or print name of current YP/NIS domain kadmin(8) - network utility for Kerberos database administration kadmind(8) - network daemon for Kerberos database administration rpc.yppasswdd(8) - server for updating NIS passwords rpc.ypxfrd(8) - NIS map transfer server yp(4) - description of the YP/NIS system yp_mkdb(8) - generate the NIS databases ypbind(8) - NIS domain binding daemon yppush(8) - force propagation of updated NIS databases ypserv(8) - NIS database server ypxfr(8) - transfer NIS database from remote server to local host M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sun Aug 4 00:35:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19013 for current-outgoing; Sun, 4 Aug 1996 00:35:18 -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 AAA19003 for ; Sun, 4 Aug 1996 00:35:16 -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 AAA00564 for ; Sun, 4 Aug 1996 00:34:33 -0700 (PDT) To: current@freebsd.org Subject: New 2.2-960801-SNAP boot floppy Date: Sun, 04 Aug 1996 00:34:33 -0700 Message-ID: <561.839144073@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Given the severity of the disk labelling bug, I re-rolled the installation boot floppy and updated the bin and src dists to reflect the binaries/sources which were changed. The CDROM version of this SNAP will have the updated bits. Jordan From owner-freebsd-current Sun Aug 4 00:45:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19378 for current-outgoing; Sun, 4 Aug 1996 00:45:31 -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 AAA19367 for ; Sun, 4 Aug 1996 00:45:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id AAA13305; Sun, 4 Aug 1996 00:44:46 -0700 (PDT) Message-Id: <199608040744.AAA13305@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: current@freebsd.org Subject: Re: problem with -current system grinding to a halt... In-reply-to: Your message of "Sun, 04 Aug 1996 12:52:44 +0930." <199608040322.MAA06694@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Sun, 04 Aug 1996 00:44:46 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I commented about this a day or few ago, but at that point I was still >chasing other possibilities, so here I go again 8) > >I have a reasonably -curent system that, under moderate load is dying >after about 18-20 hours of uptime. The system itself is a P120 on a >Triton board with 64M and an NCR PCI controller : > >FreeBSD mstradar.esrange.ssc.se 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Mon Jul 15 13:16:26 MET DST 1996 msmith@spore.atrad.adelaide.edu.au:/usr/work/radarsys/compile/MSTRADAR i386 > >The system is being pushed fairly lightly, although there are some long-lived >processes that accumulate a lot of CPU (and have largeish swap footprints). >These large processes are all Linux a.out binaries (IDL). > >Symptoms are that the system remains pingable, and you can often get >through the telnet login sequence to the point where /usr/bin/login >is invoked but no further. As I type, the system just died under me again; >I was watching the output of 'systat -vmstat', quit and typed 'w' to check >the load. I got this : > >mstradar:/home/radar>w > 5:04AM up 19:28, 2 users, load averages: 0.00, 0.00, 0.00 >USER TTY FROM LOGIN@ IDLE WHAT > >and then nothing more. > >There have been no console or syslog messages to date from any of the >times that this has happened. Any suggestions as to where to start >looking would be appreciated; unfortunately due to the rather remote >location of the system I can't play DDB with it 8( This can happen if your nameserver isn't reachable. Have you tried "w -n" ? This disables the nameserver lookups and is useful for this specific problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Aug 4 01:48:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA22813 for current-outgoing; Sun, 4 Aug 1996 01:48:05 -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 BAA22807 for ; Sun, 4 Aug 1996 01:48:02 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA07448; Sun, 4 Aug 1996 18:29:04 +0930 From: Michael Smith Message-Id: <199608040859.SAA07448@genesis.atrad.adelaide.edu.au> Subject: Re: problem with -current system grinding to a halt... To: dg@root.com Date: Sun, 4 Aug 1996 18:29:03 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@freebsd.org In-Reply-To: <199608040744.AAA13305@root.com> from "David Greenman" at Aug 4, 96 00:44:46 am 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 David Greenman stands accused of saying: > > This can happen if your nameserver isn't reachable. Have you tried "w -n" ? > This disables the nameserver lookups and is useful for this specific problem. Nameserver lookup failures cause the whole system to grind to a halt, forcing a hard reset? Sorry, I know what nameserver timeouts look like, and that's not the problem. I wish it was. I should have been clearer I guess; the 'w' freeze was coincidental - the system dies _consistently_ after about 18 hours of uptime, with no console messages. Regardless of whether I'm logged in or not, and apparently unrelated to any specific system activity. I say 'apparently' because it's not easy to see exactly what the system is doing. We doubled the system's memory when it looked like heavy paging was a problem (it was), and now the system hardly pages at all. At the times when the hangs usually occur (around 6am) the system is as unloaded as it gets - there are no interactive users, and the background load which has been running nonstop since the system was booted. If there are any thoughts on possible resource leaks in the Linux emulation code, that'd give me somewhere to look. Other systems running the same load less the heavy IDL sessions have run happily for weeks with no signs of stress. > David Greenman -- ]] 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 Sun Aug 4 03:45:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA28178 for current-outgoing; Sun, 4 Aug 1996 03:45:57 -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 DAA28172 for ; Sun, 4 Aug 1996 03:45:54 -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 MAA04482 for ; Sun, 4 Aug 1996 12:45:51 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id MAA21703 for freebsd-current@FreeBSD.ORG; Sun, 4 Aug 1996 12:42:59 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id IAA11627; Sun, 4 Aug 1996 08:26:28 +0200 (MET DST) To: freebsd-current@FreeBSD.ORG Subject: BISDN, when will it be integrated? From: Peter Mutsaers Date: 04 Aug 1996 08:26:26 +0200 Message-ID: <87pw578y25.fsf@localhost.xs4all.nl> Lines: 12 X-Mailer: Gnus v5.2.26/Emacs 19.31 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, Should I still go through the trouble of patching the current kernel myself from BISDN, or will it be integrated very soon (i.e. within a few days). Tuesday I get my ISDN connection and I want to use my Teles board from that day on. Thanks, -- Peter Mutsaers | Abcoude (Utrecht), plm@xs4all.nl | the Netherlands From owner-freebsd-current Sun Aug 4 03:48:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA28271 for current-outgoing; Sun, 4 Aug 1996 03:48:36 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-133.ut.nl.ibm.net [139.92.42.133]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA28264 for ; Sun, 4 Aug 1996 03:48:31 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id LAA21154; Sun, 4 Aug 1996 11:20:31 +0200 (MET DST) Date: Sun, 4 Aug 1996 11:20:31 +0200 (MET DST) Message-Id: <199608040920.LAA21154@vector.jhs.no_domain> To: current@freebsd.org Subject: Suggestion for RELNOTES.TXT From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ref. ftp://ftp.freebsd.org/pub/FreeBSD/2.2-960801-SNAP/RELNOTES.TXT Suggestion (1) for RELNOTES.TXT line 439 s/The FreeBSD Development Team/The FreeBSD Code Control Team/ There's many more active contributing developers than that short list implies. No point making the FreeBSD effort seem under-manned compared with it's true strength. Suggestion (2) for RELNOTES.TXT for next snap: As "Releases != Snaps", shouldn't we logically have SNAPNOTES.TXT ? but perhaps better: a name equally applicable to releases & snaps; Perhaps { READ_ME, INTRODUCTION, INTRO, SUMMARY, CONTENTS, PREFACE } ? Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sun Aug 4 04:13:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29755 for current-outgoing; Sun, 4 Aug 1996 04:13:41 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA29748 for ; Sun, 4 Aug 1996 04:13:37 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id ac12344; 4 Aug 96 11:12 GMT Received: from nlsys.demon.co.uk ([158.152.125.33]) by relay-3.mail.demon.net id aa10311; 4 Aug 96 12:09 +0100 Received: from localhost (dfr@localhost) by nlsys.demon.co.uk (8.7.5/8.6.9) with SMTP id MAA01315; Sun, 4 Aug 1996 12:08:03 +0100 (BST) Date: Sun, 4 Aug 1996 12:08:02 +0100 (BST) From: Doug Rabson Reply-To: Doug Rabson To: John Dyson cc: dfr@render.com, terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... In-Reply-To: <199608031914.MAA01882@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 On Sat, 3 Aug 1996, John Dyson wrote: > > > > I just grepped for uses of VOP_LOCK in the kernel and there seem to be a > > few places in the vm system which appear to be using the vnode lock to > > protect critical sections of code. Have a look at vm_object_terminate() > > and vm_object_page_clean() and tell me what would happen if the VOP_LOCK > > is not exclusive. > > > Don't do a vm_object_page_clean if VOP_LOCK is not exclusive :-). Don't > even think about it... I sure don't want to :-). Well NFS' VOP_LOCK is certainly not exclusive, so is that going to be a possible cause of nfs's instability? > > > > > You have to start reusing vnodes sometime. Whether it means reusing them > > within a filesystem or across a global pool, it has to happen. Even > > reusing a vnode within a filesystem would involve something similar to > > vclean() surely. I don't understand the VM system well enough to judge > > whether dropping a few valid pages from old vnodes is a real problem in > > performance terms. > > > If the vnode is on the free queue, there had better not be any processes > using it at the time (the vm_object holds a reference.) If you need to > get a free vnode, you should probably first check the vnode free list > and then perhaps try to check the cached VM objects. Vnode backed > cached VM objects should be able to be terminated at any time (in > process context.) A side-effect of the object termination is that the > vnode will be pretty much available for re-use. I think everything in the system is pretty clean in that respect. Everyone calls vget() to reactivate cached vnodes and checks the return value to make sure it is still ok. I am pretty sure nothing tries to use a vnode with a zero v_usecount. -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891 From owner-freebsd-current Sun Aug 4 06:01:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA02917 for current-outgoing; Sun, 4 Aug 1996 06:01:00 -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 GAA02910 for ; Sun, 4 Aug 1996 06:00:55 -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 PAA13317 for ; Sun, 4 Aug 1996 15:00:52 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id OAA29686 for freebsd-current@FreeBSD.ORG; Sun, 4 Aug 1996 14:54:40 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id NAA12177; Sun, 4 Aug 1996 13:21:08 +0200 (MET DST) To: freebsd-current@FreeBSD.ORG Subject: Questions about the CVS and CTM From: Peter Mutsaers Date: 04 Aug 1996 13:21:05 +0200 Message-ID: <87686zv1i6.fsf@localhost.xs4all.nl> Lines: 32 X-Mailer: Gnus v5.2.39/Emacs 19.31 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I consider to switch from folliwing src-current to cvs-current. I now have the CVS version of the sources unpacked. Now if I want to do make world, what is the normal thing to do? What I did was 'cvs checkout src'. Then I get a copy of src, and I can do a 'make world' in it. I can do 'cvs update' in the future, right? This does cost lots and lots of diskspace, since I have to have both the CVS source and the checked-out source on disk (together with the objects). Is there a more efficient way? Another question: how do I make local modifications? If I do this and cvs commit them to my local cvs repository (maybe as a branch) then I have a problem since ctm's md5 checksums won't match anymore, thus ctm will fail. (I need to have ISDN support within two days, thus I'll patch bisdn in). Yet another ctm question: Is it possible to omit a certain branch, for example src/games or ports/japanese? I could just remove it from disk since I don't need it and don't like to waste diskspace on it, but then also ctm updates will fail when they try to patch something in these directories. Or will ctm just skip them and continue? Thanks in advance, -- Peter Mutsaers | Abcoude (Utrecht), plm@xs4all.nl | the Netherlands From owner-freebsd-current Sun Aug 4 06:55:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04573 for current-outgoing; Sun, 4 Aug 1996 06:55:40 -0700 (PDT) Received: from arl-img-2.compuserve.com (arl-img-2.compuserve.com [149.174.217.132]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA04568 for ; Sun, 4 Aug 1996 06:55:38 -0700 (PDT) Received: by arl-img-2.compuserve.com (8.6.10/5.950515) id JAA00552; Sun, 4 Aug 1996 09:55:03 -0400 Date: 04 Aug 96 09:53:59 EDT From: Jan Knepper <100626.3506@CompuServe.COM> To: "[FreeBSD current]" Subject: 2.1.5 v.s. 2.2-960801-SNAP Message-ID: <960804135358_100626.3506_BHL52-1@CompuServe.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I am new to these mailing list, so I am sorry if I send this to the wrong list. Yesterday I downloaded 2.1.5 STABLE. I already have 2.1.0 running on a system with NCR SCSI. Version 2.1.5 refuses to access the NCR SCSI. I get the following message when booting from flop. (boot.flp) ncr0: aborting job ncr0:2: ERROR (90:0) (8-0-0) (0/13) @ (c8c:50000000) script cmd = 740a8700 reg : de 00 00 13 47 00 06 0f 35 08 00 00 90 00 0f 02 ncr0: restart (fatal erro) sd0(ncr0:0:0) COMMAND FAILED (9/f) @ f0e71a00 I tried the 2.2-960801-SNAP kernel and that one seems to work. However once the system is installed there is an other kernel in the root which causes the exact same problem. Of course I could also download the complete SNAP distribution, but there might be an other way around this?! Thanks in advance, Enjoy! Jan From owner-freebsd-current Sun Aug 4 06:58:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04645 for current-outgoing; Sun, 4 Aug 1996 06:58:09 -0700 (PDT) Received: from inga.augusta.de (inga.augusta.de [193.175.23.65]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA04640 for ; Sun, 4 Aug 1996 06:58:04 -0700 (PDT) Received: from rabbit by inga.augusta.de with uucp (Smail3.1.29.1 #1) id m0un2Th-004cocC; Sun, 4 Aug 96 14:40 MET DST Received: by rabbit.augusta.de (Smail3.1.29.1 #1) id m0un1Ep-0009zSC; Sun, 4 Aug 96 13:20 MET DST Message-Id: Date: Sun, 4 Aug 96 13:20 MET DST X-Newsreader: knews 0.9.6 Organization: Privat Site running FreeBSD References: From: shanee@rabbit.augusta.de (Andreas Kohout) Subject: Re: compile time X-Original-Newsgroups: muc.lists.freebsd.current In-Reply-To: To: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , hernanw@FSL.ORST.EDU (Wayne Hernandez) writes: > How long is a "make world" supposed to take? I have seen that it should > take 3 hours on a P5-166, but on a P5-133 with 32 megs of ram the other > day I got the following: > > 1938.277u 466.434s 59.38.84 67.1% 846+774k 11312+8744/io 2642pf +0w > > Started: 10:18 pm > Finished: 11:18 pm this is not normal, on my P133, 32MByte it takes about tree and a half hour. -- Greeting, Andy running FreeBSD-current --------------------------------------------------------------------------- From owner-freebsd-current Sun Aug 4 12:10:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA18657 for current-outgoing; Sun, 4 Aug 1996 12:10:51 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA18648 for ; Sun, 4 Aug 1996 12:10:48 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id PAA06359; Sun, 4 Aug 1996 15:10:25 -0400 (EDT) Date: Sun, 4 Aug 1996 15:10:24 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: dg@root.com, current@freebsd.org Subject: Re: problem with -current system grinding to a halt... In-Reply-To: <199608040859.SAA07448@genesis.atrad.adelaide.edu.au> 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, 4 Aug 1996, Michael Smith wrote: > David Greenman stands accused of saying: > > > > This can happen if your nameserver isn't reachable. Have you tried "w -n" ? > > This disables the nameserver lookups and is useful for this specific problem. > > Nameserver lookup failures cause the whole system to grind to a halt, > forcing a hard reset? Sorry, I know what nameserver timeouts look like, > and that's not the problem. I wish it was. > > I should have been clearer I guess; the 'w' freeze was coincidental - > the system dies _consistently_ after about 18 hours of uptime, with no > console messages. Regardless of whether I'm logged in or not, and > apparently unrelated to any specific system activity. I say 'apparently' > because it's not easy to see exactly what the system is doing. > This sounds like the SCSI bus hangs I used to get with one of my systems...where everything seemed to be running until you tried to deal with somethin gthat had to go to the drive (ie. login, w, df, etc) When this happens, check your drive...does the hard drive light come on and stay on? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sun Aug 4 13:10:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20997 for current-outgoing; Sun, 4 Aug 1996 13:10:30 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA20992 for ; Sun, 4 Aug 1996 13:10:27 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id NAA10207 for ; Sun, 4 Aug 1996 13:10:26 -0700 (PDT) Message-Id: <199608042010.NAA10207@austin.polstra.com> To: freebsd-current@freebsd.org Subject: Bug: Signal handler won't stay installed Date: Sun, 04 Aug 1996 13:10:26 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've run into what looks like a kernel bug in a -current system from around July 20th. My program (the CVSup server daemon) sets up a signal handler for the SIGCHLD signal, using sigaction(). The signal handler does the usual thing to reap child processes that have exited. Namely, it loops calling wait3() with the WNOHANG flag set, until -1 is returned. The handler function gets called the first time a SIGCHLD happens, but subsequent SIGCHLDs are ignored. The signals don't show up in ktrace output at all, and the child processes stick around in the zombie state. This happens only on my -current system; it works fine on several -stable systems I've tried. The signal handler that was installed by sigaction should remain installed after the handler function has returned. I.e., it should be able to catch repeated signals without having to call sigaction each time. As a work-around, I tried calling sigaction() from within the handler function each time, just before it returns. That fixed the problem. But it should not be necessary. My struct sigaction has sa_mask=0 and sa_flags=SA_NOCLDSTOP. Do any of you have any ideas about this? I can put together a stand-alone test case, if necessary. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sun Aug 4 14:18:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA24351 for current-outgoing; Sun, 4 Aug 1996 14:18:23 -0700 (PDT) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA24346; Sun, 4 Aug 1996 14:18:20 -0700 (PDT) Received: from dima@localhost by burka.rdy.com id OAA27436; (8.7.5/RDY) Sun, 4 Aug 1996 14:22:09 -0700 (PDT) Message-Id: <199608042122.OAA27436@burka.rdy.com> Subject: sup5.freebsd.org To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Date: Sun, 4 Aug 1996 14:22:08 -0700 (PDT) X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) 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 Hi there! sup5.freebsd.org is gonna be down for tonight from 8pm PDT to aprox. 8am. (12 hours). -- dima From owner-freebsd-current Sun Aug 4 14:21:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA24582 for current-outgoing; Sun, 4 Aug 1996 14:21:36 -0700 (PDT) Received: from snake.hut.fi (snake.hut.fi [193.167.6.99]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA24572 for ; Sun, 4 Aug 1996 14:21:29 -0700 (PDT) Received: from lk-hp-1.hut.fi (inkari@lk-hp-1.hut.fi [130.233.244.32]) by snake.hut.fi (8.7.5/8.7.3) with ESMTP id AAA34498 for ; Mon, 5 Aug 1996 00:21:19 +0300 From: Juha Inkari Received: (inkari@localhost) by lk-hp-1.hut.fi (8.6.12/8.6.7) id AAA15889 for current@freebsd.org; Mon, 5 Aug 1996 00:21:21 +0300 Message-Id: <199608042121.AAA15889@lk-hp-1.hut.fi> Subject: IPX ppp To: current@freebsd.org Date: Mon, 5 Aug 1996 00:21:20 +0300 (EETDST) X-Mailer: ELM [version 2.4 PL25] 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 Has anyone tried serving IPX ppp (Netware) clients via pppd ? There seems to be a IPX control protocol implemented in a 2.2.0f ppp release by Al Longyear , that should not be too difficult to incorporate, but are there other known problems to be solved in the way ? From owner-freebsd-current Sun Aug 4 15:01:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26805 for current-outgoing; Sun, 4 Aug 1996 15:01:10 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA26787 for ; Sun, 4 Aug 1996 15:01:04 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id AAA09586 for freebsd-current@freebsd.org; Mon, 5 Aug 1996 00:58:48 +0300 (EET DST) From: Mr Operating System Message-Id: <199608042158.AAA09586@shadows.aeon.net> Subject: make world To: freebsd-current@freebsd.org Date: Mon, 5 Aug 1996 00:58:48 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL22 (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 ===> lib cc -O2 -m486 -pipe -c /usr/src/usr.bin/lex/lib/libmain.c -o libmain.o ld: invalid command option `-O' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. shadows# i tried to look thru makefiles where the typo is, didnt find, not even with the egrep... mickey From owner-freebsd-current Sun Aug 4 15:23:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA27806 for current-outgoing; Sun, 4 Aug 1996 15:23:41 -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 PAA27801 for ; Sun, 4 Aug 1996 15:23:38 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id IAA09424; Mon, 5 Aug 1996 08:04:45 +0930 From: Michael Smith Message-Id: <199608042234.IAA09424@genesis.atrad.adelaide.edu.au> Subject: Re: problem with -current system grinding to a halt... To: scrappy@ki.net (Marc G. Fournier) Date: Mon, 5 Aug 1996 08:04:45 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, dg@root.com, current@freebsd.org In-Reply-To: from "Marc G. Fournier" at Aug 4, 96 03:10:24 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 Marc G. Fournier stands accused of saying: > > > > I should have been clearer I guess; the 'w' freeze was coincidental - > > the system dies _consistently_ after about 18 hours of uptime, with no > > console messages. Regardless of whether I'm logged in or not, and > > apparently unrelated to any specific system activity. I say 'apparently' > > because it's not easy to see exactly what the system is doing. > > > > This sounds like the SCSI bus hangs I used to get with one of > my systems...where everything seemed to be running until you tried to > deal with somethin gthat had to go to the drive (ie. login, w, df, etc) > > When this happens, check your drive...does the hard drive light > come on and stay on? I can't tell. It's in Sweden and I'm not. 8( How did you eventually resolve your problem? > Marc G. Fournier scrappy@ki.net -- ]] 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 Sun Aug 4 16:37:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA02210 for current-outgoing; Sun, 4 Aug 1996 16:37:21 -0700 (PDT) Received: from ice.fit.qut.edu.au (tony@ice.fit.qut.edu.au [131.181.2.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA02205; Sun, 4 Aug 1996 16:37:17 -0700 (PDT) Received: (from tony@localhost) by ice.fit.qut.edu.au (8.7.5/8.7.3) id JAA17183; Mon, 5 Aug 1996 09:38:02 +1000 (EST) Date: Mon, 5 Aug 1996 09:37:59 +1000 (EST) From: Tony Jago Reply-To: Tony Jago To: Doug Rabson cc: "Jordan K. Hubbard" , freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare - More details In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: T.Jago@fit.qut.edu.au Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Exactly which files have permission problems? Try creating a file (as > root) on those filesystems and make sure that the new file is owned by > root and not nobody. > > If I could see some kind of log of the system booting, I might be able to > see more of what is happening. Is that possible? > When the system has booted correctly everything works just fine. If you create a file in / as root it is owned by root and root can change things like /etc/printcap etc etc. When the machine boots, if there are problems then typically when fails is "[" (ie. test) in the /etc/rc scripts. Alternatly, the system sometimes fails after it has mounted the new root file system (rw) under /mnt and then does a chroot. Sometimes the chroot binary is not available and the system fails to boot and the user is dumped into a root shell. Another point I forgot to mention that may have a bearing on things is that as additional hosts are added to the active client list, a line is added to /etc/exports and then kill -1 is sent to mountd on the server. This could be happening quite often if alot of clients are booting at once. I don't know if this could be a problem. --- Tony Jago, System Administrator, E-Mail: T.Jago@fit.qut.edu.au Faculty of Information Technology, Web: http://www.fit.qut.edu.au/staff/~tony Queensland University of Technology. Box 2434, Brisbane 4001, AUSTRALIA. "We need more horsepower!" Phone: +61 7 3864-2573 Fax: +61 7 3864-1959 From owner-freebsd-current Sun Aug 4 16:55:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA03220 for current-outgoing; Sun, 4 Aug 1996 16:55:44 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA03215 for ; Sun, 4 Aug 1996 16:55:41 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA13769; Sun, 4 Aug 1996 16:55:10 -0700 (PDT) Received: from shrimp.whistle.com(207.76.205.74) by whistle.com via smap (V1.3) id sma013767; Sun Aug 4 16:55:06 1996 Received: (from julian@localhost) by shrimp.whistle.com (8.6.12/8.6.12) id QAA06353; Sun, 4 Aug 1996 16:55:06 -0700 From: Julian Elischer Message-Id: <199608042355.QAA06353@shrimp.whistle.com> Subject: Re: problem with -current system grinding to a halt... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sun, 4 Aug 1996 16:55:06 -0700 (PDT) Cc: scrappy@ki.net, msmith@atrad.adelaide.edu.au, dg@root.com, current@FreeBSD.org In-Reply-To: <199608042234.IAA09424@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 5, 96 08:04:45 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 do you have cmomconsole? if so, you should drop into ddb and do a ps.. that'll tell you what everything is hanging on.. alternatively, set the default tty mode to include stty status ^T and then if s process hangs, and you are logger into it, you can do a ^T and see what it's waiting for..... > > Marc G. Fournier stands accused of saying: > > > > > > I should have been clearer I guess; the 'w' freeze was coincidental - > > > the system dies _consistently_ after about 18 hours of uptime, with no > > > console messages. Regardless of whether I'm logged in or not, and > > > apparently unrelated to any specific system activity. I say 'apparently' > > > because it's not easy to see exactly what the system is doing. > > > > > > > This sounds like the SCSI bus hangs I used to get with one of > > my systems...where everything seemed to be running until you tried to > > deal with somethin gthat had to go to the drive (ie. login, w, df, etc) > > > > When this happens, check your drive...does the hard drive light > > come on and stay on? > > I can't tell. It's in Sweden and I'm not. 8( > > How did you eventually resolve your problem? > > > Marc G. Fournier scrappy@ki.net > > -- > ]] 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 Sun Aug 4 17:07:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03734 for current-outgoing; Sun, 4 Aug 1996 17:07:05 -0700 (PDT) Received: from lear35.cytex.com (root@lear35.cytex.com [38.252.97.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA03729 for ; Sun, 4 Aug 1996 17:07:03 -0700 (PDT) Received: (from mbartley@localhost) by lear35.cytex.com (8.7.5/8.7.3) id QAA02052 for current@freebsd.org; Sun, 4 Aug 1996 16:52:59 -0700 (PDT) From: Matt Bartley Message-Id: <199608042352.QAA02052@lear35.cytex.com> Subject: kernel compile fails at if_ethersubr.c To: current@freebsd.org Date: Sun, 4 Aug 1996 16:52:58 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL22 (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 I'm running -current, CTM level src-cur 2059. This happened at CTM level 2058 as well. Here is what happens when I try to compile the kernel. This example is an attempt to compile GENERIC: # time make depend all [etc, etc] cc -c -O1 -m486 -pipe -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wunused -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DAPM_BROKEN_STATCLOCK -DATAPI_STATIC -DATAPI -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../net/if.c cc -c -O1 -m486 -pipe -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wunused -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DAPM_BROKEN_STATCLOCK -DATAPI_STATIC -DATAPI -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../net/if_ethersubr.c ../../net/if_ethersubr.c: In function `ether_ioctl': ../../net/if_ethersubr.c:869: `ETHER_ADDR_LEN' undeclared (first use this function) ../../net/if_ethersubr.c:869: (Each undeclared identifier is reported only once ../../net/if_ethersubr.c:869: for each function it appears in.) *** Error code 1 Stop. 364.81 real 256.29 user 34.20 sys # My custom kernel, which is essentially GENERIC with unused drivers removed, also does this. If it matters, I use a wd8003 ethernet card. From owner-freebsd-current Sun Aug 4 17:28:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04697 for current-outgoing; Sun, 4 Aug 1996 17:28:46 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA04690 for ; Sun, 4 Aug 1996 17:28:43 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id UAA11581; Sun, 4 Aug 1996 20:28:59 -0400 (EDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.3) with SMTP id UAA24775; Sun, 4 Aug 1996 20:28:53 -0400 (EDT) X-Authentication-Warning: ki.net: scrappy owned process doing -bs Date: Sun, 4 Aug 1996 20:28:52 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: dg@root.com, current@freebsd.org Subject: Re: problem with -current system grinding to a halt... In-Reply-To: <199608042234.IAA09424@genesis.atrad.adelaide.edu.au> 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, 5 Aug 1996, Michael Smith wrote: > I can't tell. It's in Sweden and I'm not. 8( > > How did you eventually resolve your problem? > Picked up a new drive, removed the bad one and put in a new one...I have the old drive running alone in another box that wasn't as "mission critical", and the main server has been reasonably stable since... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sun Aug 4 17:29:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04771 for current-outgoing; Sun, 4 Aug 1996 17:29:47 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA04765 for ; Sun, 4 Aug 1996 17:29:44 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ad07447; 5 Aug 96 1:29 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa16875; 5 Aug 96 1:26 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id AAA03985; Mon, 5 Aug 1996 00:01:44 GMT From: James Raynard Message-Id: <199608050001.AAA03985@jraynard.demon.co.uk> Subject: Panic: vm_page_free: invalid wire count To: freebsd-current@freebsd.org Date: Mon, 5 Aug 1996 00:01:43 +0000 () X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kernel as of 31st July, two simultaneous compilations going on while I was reading Usenet. System panicked with panic: vm_page_free: invalid wire count (2), pindex: 0x6 The DDB trace was:- _panic(f016d193, 2, 6, f02462f0, efbffe18) at _panic + 0x5a _vm_page_freechk_and_unqueue(f02462f0) at _vm_page_freechk_and_unqueue + 0x150 _vm_page_free(f02462f0, f0bf3580, 0, f0c11700, f01a3578) at vm_page_free + 0x2d _vm_object_terminate(f0b3580,f0c41908,f0bba500,f0c11700,efbffe5c) at vm_object_terminate + 0x12d _vm_object_deallocate(f0bf3580, efbffe6c, f016b2ed, f0bf3580) at vm_object_deallocate + 0x1af _pager_cache(f0bf3580,0) at pager_cache + 0x2a _vm_object_cache_timer(f0c41900, 0, 0, 1, 1) at _pager_cache + 0x5d _vm_object_deallocate(f0c41900, 0, efbffecc, f01315b3, f0bba500) at _vm_object_deallocate + 0x174 _vn_vmio_close(f0bba500, f0c11700, f0cb66c0, f01a316c, f0bba500) at _vn_vmio_close + 0x30 _vn_close(f0bba500, 2, f037f00, f0c11700, efbfff30) at _vn_close + 0x4b _vn_closefile(f0cb66c0, f0c11700, f0cb7900, 0, f0c11700) at _vn_closefile + 0x19 _closef(f0cb66c0, f0c11700, f01a3e40, f0c11700,0) at _closef + 0x12c _close(f0c11700, efbfff94, efbfff84, 8093060, 1e55c) at _closefile + 0x83 _syscall(27, 27, 0, 1e55c, 26da8) at _syscall + 0x183 _Xsyscall() at _Xsyscall + 0x35 syscall 6, eip = 0x8087901, ebp = 0x26da8 From owner-freebsd-current Sun Aug 4 18:15:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08480 for current-outgoing; Sun, 4 Aug 1996 18:15:28 -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 SAA08475 for ; Sun, 4 Aug 1996 18:15:25 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA16636; Mon, 5 Aug 1996 01:15:10 GMT Date: Mon, 5 Aug 1996 10:15:10 +0900 (JST) From: Michael Hancock To: Andreas Kohout cc: current@freebsd.org Subject: Re: compile time 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 Sun, 4 Aug 1996, Andreas Kohout wrote: > In article , > hernanw@FSL.ORST.EDU (Wayne Hernandez) writes: > > > How long is a "make world" supposed to take? I have seen that it should > > take 3 hours on a P5-166, but on a P5-133 with 32 megs of ram the other > > day I got the following: > > > > 1938.277u 466.434s 59.38.84 67.1% 846+774k 11312+8744/io 2642pf +0w > > > > Started: 10:18 pm > > Finished: 11:18 pm > > this is not normal, on my P133, 32MByte it takes about tree and a half hour. In his original post he mentioned that he used make -k to get past tcl or something. The make probably skipped more than he thinks. Mike Hancock From owner-freebsd-current Sun Aug 4 18:34:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA09335 for current-outgoing; Sun, 4 Aug 1996 18:34:14 -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 SAA09329 for ; Sun, 4 Aug 1996 18:34:11 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA16726; Mon, 5 Aug 1996 01:33:45 GMT Date: Mon, 5 Aug 1996 10:33:45 +0900 (JST) From: Michael Hancock To: Doug Rabson cc: Terry Lambert , jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... 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, 3 Aug 1996, Doug Rabson wrote: > > The vclean code is evil and redundant and redundant, but without moving > > the vnode allocation to per FS vnodes (I've mentioned this before), there > > is very little you can do. It's a buffer cache lose to say "no" to a > > page that's in core, but which does not have a vnode referencing it, > > so you have to reload it from disk even though a perectly good copy > > is already in memory. 8-(. > > You have to start reusing vnodes sometime. Whether it means reusing them > within a filesystem or across a global pool, it has to happen. Even > reusing a vnode within a filesystem would involve something similar to > vclean() surely. I don't understand the VM system well enough to judge > whether dropping a few valid pages from old vnodes is a real problem in > performance terms. I think what he's is saying is that when the vnodes are in the global pool the chances of reusing a vnode that was used previously by a particular fs is less than having a per fs vnode pool. The problem with the per fs vnode pool is the management overhead. When you need to start reusing vnodes you need to search through all the different fs pools to find a vnode. I don't know which is a better trade-off. Mike Hancock From owner-freebsd-current Sun Aug 4 20:16:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA13928 for current-outgoing; Sun, 4 Aug 1996 20:16:48 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA13915; Sun, 4 Aug 1996 20:16:31 -0700 (PDT) Received: from fakir.india.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA242454982; Sun, 4 Aug 1996 20:16:27 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA280805117; Mon, 5 Aug 1996 08:48:38 +0530 Message-Id: <199608050318.AA280805117@fakir.india.hp.com> To: freebsd-current@freebsd.org Cc: committers@freebsd.org Subject: Patch to recognize AMD 5x86 cpus Date: Mon, 05 Aug 1996 08:48:37 +0530 From: A JOSEPH KOSHY Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Enclosed is a patch to recognize and print the kind of AMD 5x86 cpu on-board at boot time. This is per AMD's application note on CPU recognition. Sample boot time output from my machine: FreeBSD 2.2-CURRENT #1: Sat Aug 3 10:06:03 1996 koshy@orthanc:/usr/src/sys/compile/ORTHANC Calibrating clock(s) relative to mc146818A clock... i8254 clock: 1193604 Hz CPU: AMD Am5x86 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x4f4 real memory = 16777216 (16384K bytes) avail memory = 15036416 (14684K bytes) ...etc... The patch is wrt -current as of Fri 2nd Aug 1996. Can someone review // commit these changes please? Koshy My Personal Opinions Only. -------------------------------PATCH---------------------------------- --- identcpu.c.ctm Fri Jul 12 19:40:58 1996 +++ identcpu.c Tue Jul 16 20:47:57 1996 @@ -148,6 +148,20 @@ break; } } + } else if (!strcmp(cpu_vendor,"AuthenticAMD")) { + cpu_model[0] = '\0'; + strcpy(cpu_model, "AMD "); + switch (cpu_id & 0xF0) { + case 0xE0: + strcat(cpu_model, "Am5x86 Write-Through"); + break; + case 0xF0: + strcat(cpu_model, "Am5x86 Write-Back"); + break; + default: + strcat(cpu_model, "Unknown"); + break; + } } #endif printf("%s (", cpu_model); From owner-freebsd-current Sun Aug 4 21:32:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA17885 for current-outgoing; Sun, 4 Aug 1996 21:32:30 -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 VAA17878 for ; Sun, 4 Aug 1996 21:32:27 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA10882 for current@freebsd.org; Mon, 5 Aug 1996 14:14:02 +0930 From: Michael Smith Message-Id: <199608050444.OAA10882@genesis.atrad.adelaide.edu.au> Subject: question about grinding system (Linux guru attn. reqd) To: current@freebsd.org Date: Mon, 5 Aug 1996 14:14:02 +0930 (CST) 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've just been watching this slowly-dying -current system trying to find something that looks wrong, and I think I have something. Watching the output of vmstat -m, I notice that the numbers for the 'temp' category keep growing, and that there's about 8M allocated to it at this point in time. Following this and the suspicion that the problem is linux-emulation related I went looking for M_TEMP allocations in i386/linux, and I'd like someone who's better qualified than I to look over the exit conditions in linux_emul_find() in linux_util.c because I'm fairly sure that it's possible for this function to return without freeing its buffer, and this would lead to the sort of leak that I'm seeing. Naturally, I'll try to test this as soon as I get a chance, but I'd appreciate any comments. -- ]] 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 Sun Aug 4 23:02:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23592 for current-outgoing; Sun, 4 Aug 1996 23:02:47 -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 XAA23585 for ; Sun, 4 Aug 1996 23:02:44 -0700 (PDT) Message-Id: <199608050602.XAA23585@freefall.freebsd.org> To: current Subject: Instability in current Date: Sun, 04 Aug 1996 23:02:43 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just rebuilt my kernel today and have encountered quite a few hangs. I am running a heavily modified SCSI system, but I've been using these same changes for more than a week now (supping and rebuilding my kernel all through the week) without seeing these hangs. The processes are sleeping either in "wait" or "biowait". Has anyone else seen this? I'm going to try a clean sys tree to ensure that my changes aren't the culpret. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Aug 4 23:39:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA25059 for current-outgoing; Sun, 4 Aug 1996 23:39:26 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA25052; Sun, 4 Aug 1996 23:39:22 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id XAA10271; Sun, 4 Aug 1996 23:36:46 -0700 (PDT) Message-Id: <199608050636.XAA10271@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: A JOSEPH KOSHY cc: freebsd-current@freebsd.org, committers@freebsd.org Subject: Re: Patch to recognize AMD 5x86 cpus In-reply-to: Your message of Mon, 05 Aug 96 08:48:37 +0530. <199608050318.AA280805117@fakir.india.hp.com> Date: Sun, 04 Aug 1996 23:36:34 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Enclosed is a patch to recognize and print the kind of AMD 5x86 cpu >on-board at boot time. This is per AMD's application note on CPU >recognition. If you wanted to do this The "Correct" Way, you might be better off rewriting the CPU identification code in locore.s to a more general, better abstracted design, so you could add CPU types easily, rather than making a longer and longer string of special case code. You'd also want to start with an identification mechanism for all current CPU types. A good place to find the information necessary is http://www.x86.org/. ----------------------------------------------------------------------------- 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 Aug 5 03:09:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA06278 for current-outgoing; Mon, 5 Aug 1996 03:09:43 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA06269 for ; Mon, 5 Aug 1996 03:09:40 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id LAA10099; Mon, 5 Aug 1996 11:10:02 +0100 Date: Mon, 5 Aug 1996 11:10:00 +0100 (BST) From: Doug Rabson To: Michael Hancock cc: Terry Lambert , jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... 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 Mon, 5 Aug 1996, Michael Hancock wrote: > On Sat, 3 Aug 1996, Doug Rabson wrote: > > > > The vclean code is evil and redundant and redundant, but without moving > > > the vnode allocation to per FS vnodes (I've mentioned this before), there > > > is very little you can do. It's a buffer cache lose to say "no" to a > > > page that's in core, but which does not have a vnode referencing it, > > > so you have to reload it from disk even though a perectly good copy > > > is already in memory. 8-(. > > > > You have to start reusing vnodes sometime. Whether it means reusing them > > within a filesystem or across a global pool, it has to happen. Even > > reusing a vnode within a filesystem would involve something similar to > > vclean() surely. I don't understand the VM system well enough to judge > > whether dropping a few valid pages from old vnodes is a real problem in > > performance terms. > > I think what he's is saying is that when the vnodes are in the global pool > the chances of reusing a vnode that was used previously by a particular fs > is less than having a per fs vnode pool. > > The problem with the per fs vnode pool is the management overhead. When > you need to start reusing vnodes you need to search through all the > different fs pools to find a vnode. > > I don't know which is a better trade-off. But surely, even if you find a vnode from the same filesystem, you still need to 'clean' it, i.e. invalidate buffers and re-associate with a different inode+dev/filehandle/whatever. I don't see what the gain for per-fs vnode pools is. I expect Terry will explain it to me now :-) -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Mon Aug 5 03:43:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA08044 for current-outgoing; Mon, 5 Aug 1996 03:43:31 -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 DAA08035 for ; Mon, 5 Aug 1996 03:43:26 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id KAA19813; Mon, 5 Aug 1996 10:42:20 GMT Date: Mon, 5 Aug 1996 19:42:19 +0900 (JST) From: Michael Hancock To: Doug Rabson cc: Terry Lambert , jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... 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 Mon, 5 Aug 1996, Doug Rabson wrote: > On Mon, 5 Aug 1996, Michael Hancock wrote: > > > I think what he's is saying is that when the vnodes are in the global pool > > the chances of reusing a vnode that was used previously by a particular fs > > is less than having a per fs vnode pool. > > > > The problem with the per fs vnode pool is the management overhead. When > > you need to start reusing vnodes you need to search through all the > > different fs pools to find a vnode. > > > > I don't know which is a better trade-off. > > But surely, even if you find a vnode from the same filesystem, you still > need to 'clean' it, i.e. invalidate buffers and re-associate with a > different inode+dev/filehandle/whatever. I don't see what the gain for > per-fs vnode pools is. I expect Terry will explain it to me now :-) I think the gain is the potential processor data caching of the vnode object itself. Having a global vnode pool breaks this locality of reference. But then again since the caching effects are very temporal and the Intel cache is small it's hard to say how much of an effect the per fs pools would have. Mike Hancock From owner-freebsd-current Mon Aug 5 07:05:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19410 for current-outgoing; Mon, 5 Aug 1996 07:05:10 -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 HAA19400; Mon, 5 Aug 1996 07:05:05 -0700 (PDT) Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id JAA16614; Mon, 5 Aug 1996 09:05:02 -0500 (CDT) Message-Id: <199608051405.JAA16614@sierra.zyzzyva.com> To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: ep0 problems and the stable tree In-reply-to: randy's message of Sat, 03 Aug 1996 16:38:33 -0500. <199608032138.QAA11489@sierra.zyzzyva.com> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Aug 1996 09:05:02 -0500 From: Randy Terbush Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm would like to add the following to my previous post and bring this on to the current list, since the -stable list appears to be deserted... I can further pin this behavior down to TCP NFS connections. UDP does not seem to be aflicted, but it is easily recreated over a TCP NFS connection. Is there any chance that the "grinding to a halt" reports on -current are network related? > I've seen a lot of discussion about the ep driver getting broken late > in the 2.1.5 release. Should I still be seeing this from sources dated > > sierra:/sys/i386/isa > #> ll if_ep* > -rw-r--r-- 1 root wheel 36464 Jul 15 23:10 if_ep.c > -rw-r--r-- 1 root wheel 36457 May 26 14:54 if_ep.c.orig > -rw-r--r-- 1 root wheel 13946 Mar 31 23:08 if_epreg.h > > Aug 3 16:11:25 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > Aug 3 16:13:49 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > Aug 3 16:13:52 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > > The net result is that a new NFS client on the net is suddenly freezing > quite frequently. Killing and restarting the 'nfsd' processes on the > server fix the problem. > > Secondly, do I dare sup the -stable tree at this point? What was decided? > > > > From owner-freebsd-current Mon Aug 5 08:11:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA24071 for current-outgoing; Mon, 5 Aug 1996 08:11:43 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA24015 for ; Mon, 5 Aug 1996 08:11:16 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id RAA14447; Mon, 5 Aug 1996 17:06:37 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id RAA06208; Mon, 5 Aug 1996 17:19:46 +0200 Date: Mon, 5 Aug 1996 17:19:46 +0200 From: "Christoph P. Kukulies" Message-Id: <199608051519.RAA06208@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org, multimedia@freebsd.org Subject: snd into -current Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there any reasons to not integrate snd01041996-2.2-current.tgz into -current given that -current is experimental anyway and there are no stringent stability considerations? Recent augmentations in the linux_ioctl area (sound ioctls) make it a pain to keep up with -current while still using the newer sounddriver. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Aug 5 10:18:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03233 for current-outgoing; Mon, 5 Aug 1996 10:18:15 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03225; Mon, 5 Aug 1996 10:18:12 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id KAA15750; Mon, 5 Aug 1996 10:18:05 -0700 (PDT) Message-Id: <199608051718.KAA15750@austin.polstra.com> To: freebsd-current@freebsd.org Cc: bde@zeta.org.au, xaa@xaa.stack.urc.tue.nl, nate@freebsd.org Subject: Re: Bug: Signal handler won't stay installed (SOLVED) In-reply-to: <199608042010.NAA10207@austin.polstra.com> Date: Mon, 05 Aug 1996 10:18:05 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In <199608042010.NAA10207@austin.polstra.com>, I wrote: > I've run into what looks like a kernel bug in a -current system > from around July 20th. > ... > The handler function gets called the first time a SIGCHLD happens, > but subsequent SIGCHLDs are ignored. The signals don't show up in > ktrace output at all, and the child processes stick around in the > zombie state. This happens only on my -current system; it works > fine on several -stable systems I've tried. This turned out NOT to be a kernel bug. It's pretty interesting, though. My program that failed is written in Modula-3. The runtime library's interface to the signal functions, roughly equivalent to C's , had a bug in it. I (thought I) was setting the flag SA_NOCLDSTOP in my call to sigaction, but the flag's value was defined wrong in the interface file. The correct value for this flag is 0x0008, but the interface file had it defined as 0x0004. So, why did it work under -stable, but not under -current? Because the meaning of the 0x0004 flag changed sometime between those two versions. In -stable, it is: #define SA_DISABLE 0x0004 /* disable taking signals on alternate stack */ but in -current it is: #define SA_RESETHAND 0x0004 /* reset to SIG_DFL when taking signal */ Sorry for the false alarm. Ya gotta admit, it's a nasty combination of, er, missed connections. Thanks to Bruce Evans for sending me a C program that should have failed under my original hypothesis, but didn't. -- John From owner-freebsd-current Mon Aug 5 10:40:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05229 for current-outgoing; Mon, 5 Aug 1996 10:40:54 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA05012 for ; Mon, 5 Aug 1996 10:39:07 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA16057 (5.67b/IDA-1.5 for ); Mon, 5 Aug 1996 19:38:53 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id TAA27351; Mon, 5 Aug 1996 19:38:33 +0200 (MET DST) Date: Mon, 5 Aug 1996 19:38:33 +0200 (MET DST) Message-Id: <199608051738.TAA27351@x14.mi.uni-koeln.de> From: Stefan Esser To: Jan Knepper <100626.3506@CompuServe.COM> Cc: "[FreeBSD current]" Subject: Re: 2.1.5 v.s. 2.2-960801-SNAP In-Reply-To: <960804135358_100626.3506_BHL52-1@CompuServe.COM> References: <960804135358_100626.3506_BHL52-1@CompuServe.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jan Knepper writes: > Hi, > > > I am new to these mailing list, so I am sorry if I send this to the wrong list. No, you are perfectly right (since you mention the 2.2-SNAP, else freebsd-stable would have been more appropriate :) > Yesterday I downloaded 2.1.5 STABLE. I already have 2.1.0 running on a system > with NCR SCSI. Version 2.1.5 refuses to access the NCR SCSI. I get the following > message when booting from flop. (boot.flp) > > ncr0: aborting job > ncr0:2: ERROR (90:0) (8-0-0) (0/13) @ (c8c:50000000) > script cmd = 740a8700 > reg : de 00 00 13 47 00 06 0f 35 08 00 00 90 00 0f 02 > ncr0: restart (fatal erro) > sd0(ncr0:0:0) COMMAND FAILED (9/f) @ f0e71a00 Hmmm, sorry. This is most probably related to your drive, and there was a work-around in 2.1R and is in the 2.2 install kernel. (It should have been in the GENERIC 2.2 kernel, too, but I'll have to check!) What drive causes this problem ? (Best if you sent a complete log of boot messages from your 2.1R kernel). > I tried the 2.2-960801-SNAP kernel and that one seems to work. However once the > system is installed there is an other kernel in the root which causes the exact > same problem. Hmm, that shouldn't be the case ... The kernel on the boot floppy and the GENERIC kernel should both be configured with the option FAILSAFE, which disables some performance options (most notably tagged commands for the NCR, which has them enabled by default, else). Seems I forgot to bring over FAILSAFE into the -stable tree before the 2.1.5 release was made ... :( > Of course I could also download the complete SNAP distribution, but there might > be an other way around this?! It depends on whether you can boot the 2.1R kernel to build a customized kernel. Add options "NCR_MAX_TAGS=0" to your kernel config file, configure (using the 2.1.5 "config" program !!!) and build the kernel. Please send e-mail, if you need further help. Regards, STefan From owner-freebsd-current Mon Aug 5 11:44:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA10534 for current-outgoing; Mon, 5 Aug 1996 11:44: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 LAA10523 for ; Mon, 5 Aug 1996 11:44:28 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA00556; Mon, 5 Aug 1996 20:44:20 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA29739; Mon, 5 Aug 1996 20:44:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA05781; Mon, 5 Aug 1996 20:13:43 +0200 (MET DST) From: J Wunsch Message-Id: <199608051813.UAA05781@uriah.heep.sax.de> Subject: Re: Questions about the CVS and CTM To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 5 Aug 1996 20:13:43 +0200 (MET DST) Cc: plm@xs4all.nl (Peter Mutsaers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <87686zv1i6.fsf@localhost.xs4all.nl> from Peter Mutsaers at "Aug 4, 96 01:21: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 Peter Mutsaers wrote: > I now have the CVS version of the sources unpacked. Now if I want to > do make world, what is the normal thing to do? > > What I did was 'cvs checkout src'. Then I get a copy of src, and I can > do a 'make world' in it. I can do 'cvs update' in the future, right? Right. > This does cost lots and lots of diskspace, since I have to have both > the CVS source and the checked-out source on disk (together with the > objects). Is there a more efficient way? Sorry, no. That's the price. The advantage is that you can have local modifications (see below), or can go back to some ``secure'' version in your checked out copy if you find the -current one too unstable but don't have the time or energy to debug that piece of code right now. It's merely a fine developer's tool, but nothing for the ``final customer''. > Another question: how do I make local modifications? If I do this and > cvs commit them to my local cvs repository (maybe as a branch) then I > have a problem since ctm's md5 checksums won't match anymore, thus ctm > will fail. (I need to have ISDN support within two days, thus I'll > patch bisdn in). You can't commit them to the CVS repository, but your checked out copy will retain them even with future `cvs update's. (As long as they don't conflict with changes that have been made to the master repository, of course.) John Polstra's recently announced CVSup is supposed to also handle local repository modifications. > Yet another ctm question: Is it possible to omit a certain branch, for > example src/games or ports/japanese? I could just remove it from disk > since I don't need it and don't like to waste diskspace on it, but > then also ctm updates will fail when they try to patch something in > these directories. Or will ctm just skip them and continue? I think you will have to keep them in the repository, but you don't necessarily have to checkout everything. Btw., for ports, it's not worth a mention. Only the deltas are stored, so the `japanese' and `russian' ports are checked out 2 MB alltogether. -- 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 Aug 5 11:46:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA10696 for current-outgoing; Mon, 5 Aug 1996 11:46:43 -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 LAA10689 for ; Mon, 5 Aug 1996 11:46:37 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA00500; Mon, 5 Aug 1996 20:43:27 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA29689; Mon, 5 Aug 1996 20:43:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA05659; Mon, 5 Aug 1996 20:01:12 +0200 (MET DST) From: J Wunsch Message-Id: <199608051801.UAA05659@uriah.heep.sax.de> Subject: Re: Patch to recognize AMD 5x86 cpus To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 5 Aug 1996 20:01:12 +0200 (MET DST) Cc: koshy@india.hp.com, michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608050636.XAA10271@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at "Aug 4, 96 11:36:34 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 Michael L. VanLoon -- HeadCandy.com wrote: > If you wanted to do this The "Correct" Way, you might be better off > rewriting the CPU identification code in locore.s to a more general, identcpu.c (It has been divorced from locore.s some time ago.) -- 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 Aug 5 11:47:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA10741 for current-outgoing; Mon, 5 Aug 1996 11:47:27 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA10727 for ; Mon, 5 Aug 1996 11:47:21 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id OAA15675 for current@freebsd.org; Mon, 5 Aug 1996 14:57:37 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199608051857.OAA15675@prozac.neuron.net> Subject: How much space for CVS tree? To: current@freebsd.org Date: Mon, 5 Aug 1996 14:57:37 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] 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've been tracking -current for a few months now (pretty much since the demise of 2.1-stable) and would like to start tracking the full CVS tree as well. How much space should I allocate for the CVS tree? Thanks in advance, -Amir From owner-freebsd-current Mon Aug 5 12:03:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11608 for current-outgoing; Mon, 5 Aug 1996 12:03: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 MAA11602 for ; Mon, 5 Aug 1996 12:03:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA11723; Mon, 5 Aug 1996 11:59:06 -0700 From: Terry Lambert Message-Id: <199608051859.LAA11723@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: michaelh@cet.co.jp (Michael Hancock) Date: Mon, 5 Aug 1996 11:59:06 -0700 (MST) Cc: dfr@render.com, terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org In-Reply-To: from "Michael Hancock" at Aug 5, 96 10:33:45 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 think what he's is saying is that when the vnodes are in the global pool > the chances of reusing a vnode that was used previously by a particular fs > is less than having a per fs vnode pool. No, it's not. > The problem with the per fs vnode pool is the management overhead. When > you need to start reusing vnodes you need to search through all the > different fs pools to find a vnode. > > I don't know which is a better trade-off. This isn't how per FS vnode pools should work. When you want a vnode, you call the generic "getnewvnode()" from the XXX_vget routine via VFS_VGET (sys/mount.h). This function returns a vnode with an FS specific inode. In reality, you never care to have a vnode without an FS specific inode, since there is no way to access or write buffers hung off the critter because of the way vclean works. What I'm suggesting is that there needs to be both a VFS_VGET and a VFS_VPUT (or VFS_VRELE). With the additional per fs release mechanism, each FS instance can allocate an inode pool at its instantiation (or do it on a per instance basis, the current method which makes inode allocation so slow...). Consider UFS: the in core inode struct consists of a bunch of in core data elements (which should probably be in their own structure) and a "struct dinode i_din" for the on disk inode. You could modify this as: struct inode { struct icinode i_ic; /* in core inode*/ struct vnode i_iv; /* vnode for inode*/ struct dinode i_din; /* on disk inode*/ }; Essentially, allocation of an inode would allocate a vnode. There would never be an inode without a vnode. The VFS_VPUT would put the vnode into a pool maintained by the FS per fs instance (the in core fs structure would need an additional structure element to point to the maintenance data). The FS itself would use generic maintenance routines shared by all FS's... and capable of taking a structure size for i_ic and i_din element size variations between FS types. This would maintain all common code in the common interface. The use of the vget to associate naked vnodes with the FS's would go away; in no case is a naked vnode ever useful, since using vnode buffer elements requires an FS context. In effect, the ihash would become a vnhash and LRU for use in reclaiming vnode/inode pairs. This would be much more efficient than the current dual allocation sequence. This would allow the discard of the vclean interface, and of the lock used to ensure it operates (a lock which has to be reimplemented and reimplemented correctly on a per FS basis in the XXX_LOCK and XXX_UNLOCK FS specific routines). The vnode locking could then be done in common code: vn_lock( vp, flags, p) struct vnode *vp; int flags; struct proc *p; { /* actual lock*/ if( ( st = ...) == SUCCESS) { if( ( st = VOP_LOCK( vp, flags, p)) != SUCCESS) { /* lock was vetoed, undo actual lock*/ ... } } return( st); } The point here is that the lock contention (if any) can be resolved without ever hitting the FS itsef in the failure case. The generic case of the per FS lock is now: int XXX_lock(ap) struct vop_lock_args /* { struct vnode *a_vp; int a_flags; struct proc *a_p; } */ *ap; { return( SUCCESS); } This is much harder to screw up when writing a new FS, and makes for much smaller intermediate layers. For NFS and unions, there isn't an i_din... but they also require data hung off the vnode, so the same allocation rules apply. It's a win either way, and has the side benefit of unmunging the vn. I believe that John Heidemann's thesis had this in mind when it refers to using an RPC layer to use remote file system layers as intermediates in a local VFS stack. 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 Aug 5 12:04:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11723 for current-outgoing; Mon, 5 Aug 1996 12:04:33 -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 MAA11716 for ; Mon, 5 Aug 1996 12:04:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA11737; Mon, 5 Aug 1996 12:00:51 -0700 From: Terry Lambert Message-Id: <199608051900.MAA11737@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: dfr@render.com (Doug Rabson) Date: Mon, 5 Aug 1996 12:00:51 -0700 (MST) Cc: michaelh@cet.co.jp, terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org In-Reply-To: from "Doug Rabson" at Aug 5, 96 11:10:00 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 > But surely, even if you find a vnode from the same filesystem, you still > need to 'clean' it, i.e. invalidate buffers and re-associate with a > different inode+dev/filehandle/whatever. I don't see what the gain for > per-fs vnode pools is. I expect Terry will explain it to me now :-) See previous message. 8-). Basically, it gets rid of the case of valid buffers in core being unreclaimable because of the inode/vnode disassociation for the vclean interface to work. The vclean interface is an abomination before Dennis Ritchie (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 Mon Aug 5 12:13:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12262 for current-outgoing; Mon, 5 Aug 1996 12:13:08 -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 MAA12256 for ; Mon, 5 Aug 1996 12:13:06 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA11762; Mon, 5 Aug 1996 12:08:27 -0700 From: Terry Lambert Message-Id: <199608051908.MAA11762@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: michaelh@cet.co.jp (Michael Hancock) Date: Mon, 5 Aug 1996 12:08:27 -0700 (MST) Cc: dfr@render.com, terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org In-Reply-To: from "Michael Hancock" at Aug 5, 96 07:42:19 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 > > But surely, even if you find a vnode from the same filesystem, you still > > need to 'clean' it, i.e. invalidate buffers and re-associate with a > > different inode+dev/filehandle/whatever. I don't see what the gain for > > per-fs vnode pools is. I expect Terry will explain it to me now :-) > > I think the gain is the potential processor data caching of the vnode > object itself. Having a global vnode pool breaks this locality of > reference. But then again since the caching effects are very temporal and > the Intel cache is small it's hard to say how much of an effect the per fs > pools would have. It's not the Intel cache being saved, it's the buffer cache in the "valid buffers are in core but not reclaimable without a disk I/O because of the vnode being diassociated from the underlying inode" case. The locality of reference issue is a good point. That is why I was suggesting that a directory name cache entry be treated as a reference instance on the counting semaphore. Since the graphs are complexly connected (sparse linear graph for buffer cache vs. top-fill hierarchical traversal graph for the directory structure), there is need for a second cache; the ihash is bad for this because it is FS specific, and because it is a linear locality model, just like the buffer cache; the only difference is the hash deals with the sparseness. I think this fixes your temporal argument applied to the buffer cache (instead of the processor cache, which I was not considering). You want to avoid the reassociation penalty. Since the buffers are hung off the vnode, the ihash savings are minimal following a hit (which will only occur after a dissociation. In both cases, the good data in core has had its references invalidated, and can't be recovered without a disk I/O (hence my remarks about the ihash about four weeks ago). 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 Aug 5 13:06:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15731 for current-outgoing; Mon, 5 Aug 1996 13:06:53 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA15710 for ; Mon, 5 Aug 1996 13:06:45 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.7.5/8.6.9) with ESMTP id WAA00720; Mon, 5 Aug 1996 22:05:14 GMT Message-Id: <199608052205.WAA00720@peedub.gj.org> X-Mailer: exmh version 1.6.7 5/3/96 To: Michael Smith Cc: freebsd-current@freebsd.org Subject: Re: question about grinding system (Linux guru attn. reqd) Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 05 Aug 1996 14:14:02 +0930." <199608050444.OAA10882@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Aug 1996 22:05:14 +0000 From: Gary Jennejohn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > >I've just been watching this slowly-dying -current system trying to find >something that looks wrong, and I think I have something. > >Watching the output of vmstat -m, I notice that the numbers for the >'temp' category keep growing, and that there's about 8M allocated to it >at this point in time. > >Following this and the suspicion that the problem is linux-emulation related >I went looking for M_TEMP allocations in i386/linux, and I'd like someone >who's better qualified than I to look over the exit conditions in >linux_emul_find() in linux_util.c because I'm fairly sure that it's >possible for this function to return without freeing its buffer, >and this would lead to the sort of leak that I'm seeing. > >Naturally, I'll try to test this as soon as I get a chance, but I'd >appreciate any comments. > sure looks like the places where a "goto done" happens fail to free the buffer. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-current Mon Aug 5 13:42:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18348 for current-outgoing; Mon, 5 Aug 1996 13:42:04 -0700 (PDT) Received: from pcnet1.pcnet.com (eischen@pcnet1.pcnet.com [204.213.232.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18343 for ; Mon, 5 Aug 1996 13:42:01 -0700 (PDT) Received: by pcnet1.pcnet.com (4.1/SMI-4.1) id AA08267; Mon, 5 Aug 96 16:37:56 EDT Date: Mon, 5 Aug 96 16:37:56 EDT From: eischen@vigrid.com (Daniel Eischen) Message-Id: <9608052037.AA08267@pcnet1.pcnet.com> To: freebsd-current@FreeBSD.org Subject: CD-R compatiblities Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I've got to write a purchase order for a CD-ROM burner (to be used under FreeBSD). I know that the HP SureStore works with FreeBSD, but how about any 4x recorders? Anyone get the wormcontrol in -current to work with the Yamaha line of CD-Rs? wormcontrol doesn't seem to be available in -stable (from late June). I have to wait for the 2.1.5R CD to come before trying that. Has anyone ported the -current wormcontrol back to 2.1.5R or thereabouts? Thanks for any info, Dan Eischen eischen@pcnet.com From owner-freebsd-current Mon Aug 5 13:52:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19132 for current-outgoing; Mon, 5 Aug 1996 13:52:10 -0700 (PDT) Received: from hil-img-4.compuserve.com (hil-img-4.compuserve.com [149.174.177.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA19112; Mon, 5 Aug 1996 13:52:03 -0700 (PDT) Received: by hil-img-4.compuserve.com (8.6.10/5.950515) id QAA20327; Mon, 5 Aug 1996 16:50:48 -0400 Date: 05 Aug 96 16:47:01 EDT From: Jan Knepper <100626.3506@CompuServe.COM> To: Stefan Esser , "[FreeBSD current]" , "[FreeBSD Hackers]" Subject: Re: 2.1.5 v.s. 2.2-960801-SNAP Message-ID: <960805204701_100626.3506_BHL185-1@CompuServe.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Esser wrote: /* No, you are perfectly right (since you mention the 2.2-SNAP, else freebsd-stable would have been more appropriate :) */ Well, I was having the problem with RELEASE 2.1.5, I guess that is stable right? /* > Yesterday I downloaded 2.1.5 STABLE. I already have 2.1.0 running on a system > with NCR SCSI. Version 2.1.5 refuses to access the NCR SCSI. I get the following > message when booting from flop. (boot.flp) > > ncr0: aborting job > ncr0:2: ERROR (90:0) (8-0-0) (0/13) @ (c8c:50000000) > script cmd = 740a8700 > reg : de 00 00 13 47 00 06 0f 35 08 00 00 90 00 0f 02 > ncr0: restart (fatal erro) > sd0(ncr0:0:0) COMMAND FAILED (9/f) @ f0e71a00 Hmmm, sorry. This is most probably related to your drive, and there was a work-around in 2.1R and is in the 2.2 install kernel. (It should have been in the GENERIC 2.2 kernel, too, but I'll have to check!) What drive causes this problem ? */ Well there is only one NCR SCSI in the system with a HP Harddisk and and CD-ROM. There is no IDE or EIDE drive. So I guess it is the NCR SCSI that is causing the problem. However yesterday I downloaded 2.2-CURRENT completely and installed that. That worked so far. When I rebooted at the line with "changing root device to ..." kinda like error occured, but the system started and I could get on. Today I reconfigured the 2.2 kernel a couple of times. At a certain moment the "error" message disappeard. Right at this moment I even have the "wdc0" and "wdc1" devices removed from the kernel and it runs like a charm! /* (Best if you sent a complete log of boot messages from your 2.1R kernel). */ Well, let me see what I can do to figure out what is causing the problem since is disappeared after I removed a couple of unused drivers from the kernel. But first I will check if I can get the HP100VG Ethernet Adapters to work... /* > I tried the 2.2-960801-SNAP kernel and that one seems to work. However once the > system is installed there is an other kernel in the root which causes the exact > same problem. Hmm, that shouldn't be the case ... */ I think it should. I used the 2.2-960801-SNAP boot.flp to install a 2.1.5 system! /* options "NCR_MAX_TAGS=0" */ OK, I will try that one later... /* to your kernel config file, configure (using the 2.1.5 "config" program !!!) and build the kernel. */ Well, right now I am on 2.2-960801-SNAP. I guess that is the version to be on when 'contributing' to the system right? I am thinking about devoting part of my weekends to 'contribute' FreeBSD! I however might need some pointers to find out where to start or what is *urgent*. /* Please send e-mail, if you need further help. */ Thanks for the help so far. Don't worry, be Kneppie, Jan From owner-freebsd-current Mon Aug 5 13:59:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19738 for current-outgoing; Mon, 5 Aug 1996 13:59:25 -0700 (PDT) Received: from chain.iafrica.com (root@chain.iafrica.com [196.7.74.174]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA19728 for ; Mon, 5 Aug 1996 13:59:18 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by chain.iafrica.com (8.7.5/8.6.12) with SMTP id WAA04108; Mon, 5 Aug 1996 22:35:08 +0200 (SAT) Date: Mon, 5 Aug 1996 22:35:08 +0200 (SAT) From: Khetan Gajjar To: A JOSEPH KOSHY cc: freebsd-current@FreeBSD.ORG Subject: Re: Patch to recognize AMD 5x86 cpus In-Reply-To: <199608050318.AA280805117@fakir.india.hp.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, 5 Aug 1996, A JOSEPH KOSHY wrote: >Enclosed is a patch to recognize and print the kind of AMD 5x86 cpu >on-board at boot time. This is per AMD's application note on CPU >recognition. Is anyone working on Cyrix-patches/changes ? I know they won't compile with I586_CPU in the kernel, because they don't implement the full Pentium instruction set. --- Khetan Gajjar [ http://www.iafrica.com/~khetan ] UUNet Internet Africa [ 0800-030-002 & help@iafrica.com ] Get rid of Telkom.... [ http://www.ispa.org.za ] I'm a FreeBSD User! [ http://www.freebsd.org ] Any opinions stated in this message are personal. UIA's official policy may not be reflected in this message. From owner-freebsd-current Mon Aug 5 14:00:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19947 for current-outgoing; Mon, 5 Aug 1996 14:00:45 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA19939 for ; Mon, 5 Aug 1996 14:00:42 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA23721; Mon, 5 Aug 1996 15:00:05 -0600 (MDT) Date: Mon, 5 Aug 1996 15:00:05 -0600 (MDT) Message-Id: <199608052100.PAA23721@rocky.mt.sri.com> From: Nate Williams To: Gary Jennejohn Cc: Michael Smith , freebsd-current@freebsd.org Subject: Re: question about grinding system (Linux guru attn. reqd) In-Reply-To: <199608052205.WAA00720@peedub.gj.org> References: <199608050444.OAA10882@genesis.atrad.adelaide.edu.au> <199608052205.WAA00720@peedub.gj.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Watching the output of vmstat -m, I notice that the numbers for the > >'temp' category keep growing, and that there's about 8M allocated to it > >at this point in time. > > > >Following this and the suspicion that the problem is linux-emulation related > >I went looking for M_TEMP allocations in i386/linux, and I'd like someone > >who's better qualified than I to look over the exit conditions in > >linux_emul_find() in linux_util.c because I'm fairly sure that it's > >possible for this function to return without freeing its buffer, > >and this would lead to the sort of leak that I'm seeing. > sure looks like the places where a "goto done" happens fail to free the > buffer. I concur. And, if you look at the sources from the NetBSD OS emulation code in /sys/compat/common/compat_util.c, it's even more apparent. The FreeBSD code now reads: vrele(nd.ni_vp); if (!cflag) vrele(ndroot.ni_vp); return error; Where the code in NetBSD reads: vrele(nd.ni_vp); if (!cflag) vrele(ndroot.ni_vp); return error; bad3: vrele(ndroot.ni_vp); bad2: vrele(nd.ni_vp); bad: free(buf, M_TEMP); return error; Note that we must release the buffer in an error condition, and that things are handled differently if everything succeeds vs. a failure. I chose to solve it the same way the NetBSD sources did, just to be consistant with them, so our sources are almost exactly the same again. The context diff is appended below, which is at least a partial solution to Michael's problem, if not the entire thing. Nate ------ Index: linux_util.c =================================================================== RCS file: /home/ncvs/src/sys/i386/linux/linux_util.c,v retrieving revision 1.1 retrieving revision 1.2 diff -c -r1.1 -r1.2 *** linux_util.c 1996/03/02 19:38:02 1.1 --- linux_util.c 1996/08/05 20:52:30 1.2 *************** *** 27,33 **** * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * from: svr4_util.c,v 1.5 1995/01/22 23:44:50 christos Exp ! * $Id: linux_util.c,v 1.1 1996/03/02 19:38:02 peter Exp $ */ #include --- 27,33 ---- * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * from: svr4_util.c,v 1.5 1995/01/22 23:44:50 christos Exp ! * $Id: linux_util.c,v 1.2 1996/08/05 20:52:30 nate Exp $ */ #include *************** *** 146,163 **** } if ((error = VOP_GETATTR(nd.ni_vp, &vat, p->p_ucred, p)) != 0) { ! goto done; } if ((error = VOP_GETATTR(ndroot.ni_vp, &vatroot, p->p_ucred, p)) != 0) { ! goto done; } if (vat.va_fsid == vatroot.va_fsid && vat.va_fileid == vatroot.va_fileid) { error = ENOENT; ! goto done; } } --- 146,163 ---- } if ((error = VOP_GETATTR(nd.ni_vp, &vat, p->p_ucred, p)) != 0) { ! goto bad; } if ((error = VOP_GETATTR(ndroot.ni_vp, &vatroot, p->p_ucred, p)) != 0) { ! goto bad; } if (vat.va_fsid == vatroot.va_fsid && vat.va_fileid == vatroot.va_fileid) { error = ENOENT; ! goto bad; } } *************** *** 170,179 **** free(buf, M_TEMP); } - - done: vrele(nd.ni_vp); if (!cflag) vrele(ndroot.ni_vp); return error; } --- 170,183 ---- free(buf, M_TEMP); } vrele(nd.ni_vp); if (!cflag) vrele(ndroot.ni_vp); + return error; + + bad: + vrele(ndroot.ni_vp); + vrele(nd.ni_vp); + free(buf, M_TEMP); return error; } From owner-freebsd-current Mon Aug 5 14:05:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20496 for current-outgoing; Mon, 5 Aug 1996 14:05:40 -0700 (PDT) Received: from chain.iafrica.com (root@chain.iafrica.com [196.7.74.174]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA20487 for ; Mon, 5 Aug 1996 14:05:34 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by chain.iafrica.com (8.7.5/8.6.12) with SMTP id WAA04098; Mon, 5 Aug 1996 22:33:01 +0200 (SAT) Date: Mon, 5 Aug 1996 22:33:01 +0200 (SAT) From: Khetan Gajjar Reply-To: Khetan Gajjar To: Andreas Kohout cc: current@FreeBSD.ORG Subject: Re: compile time 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 Sun, 4 Aug 1996, Andreas Kohout wrote: >this is not normal, on my P133, 32MByte it takes about tree and a half hour. It takes me 514 seconds for a kernel compile, and below speaks for itself. The PC is a Cyrix 6x86 P150+ with 32 mb RAM, on a board with 512kb pipe-line burst cache. make world completed on Sun Aug 4 01:25:03 SAT 1996 11162.37 real 6775.63 user 1383.49 sys [==3 hours, 6 minutes] --- Khetan Gajjar [ http://www.iafrica.com/~khetan ] UUNet Internet Africa [ 0800-030-002 & help@iafrica.com ] Get rid of Telkom.... [ http://www.ispa.org.za ] I'm a FreeBSD User! [ http://www.freebsd.org ] Any opinions stated in this message are personal. UIA's official policy may not be reflected in this message. From owner-freebsd-current Mon Aug 5 14:21:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21307 for current-outgoing; Mon, 5 Aug 1996 14:21:32 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA21297; Mon, 5 Aug 1996 14:21:17 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id XAA01011; Mon, 5 Aug 1996 23:20:20 +0200 (MET DST) To: Khetan Gajjar cc: Andreas Kohout , current@freebsd.org Subject: Re: compile time In-reply-to: Your message of "Sat, 05 Aug 1996 22:33:01 +0200." Date: Mon, 05 Aug 1996 23:20:20 +0200 Message-ID: <1009.839280020@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , Khetan G ajjar writes: >On Sun, 4 Aug 1996, Andreas Kohout wrote: > >>this is not normal, on my P133, 32MByte it takes about tree and a half hour. > >It takes me 514 seconds for a kernel compile, and below speaks for itself. >The PC is a Cyrix 6x86 P150+ with 32 mb RAM, on a board with 512kb >pipe-line burst cache. > >make world completed on Sun Aug 4 01:25:03 SAT 1996 > 11162.37 real 6775.63 user 1383.49 sys > >[==3 hours, 6 minutes] My P5/133 does a little better in pretty much the same config... -- 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 Mon Aug 5 15:41:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28515 for current-outgoing; Mon, 5 Aug 1996 15:41:16 -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 PAA28510 for ; Mon, 5 Aug 1996 15:41:13 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12141; Mon, 5 Aug 1996 15:38:14 -0700 From: Terry Lambert Message-Id: <199608052238.PAA12141@phaeton.artisoft.com> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Mon, 5 Aug 1996 15:38:13 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Developer" at Aug 3, 96 06:04:00 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 > Could someone explain what Linux Willow is and where to get a copy of it > from? Willows Software ( http://www.willows.com/ ) produces a product called "The Willows Toolkit"; it used to be called "TWIN". The purpose of this toolkit is to allow you to compile Windows apps for UNIX, Mac, and other systems (apparently they are doing conversion to JAVA now?!?). In addition, they have a program that comes with the toolkit that allows you to run Windows Apps on your UNIX/Mac system. It has two modes: one with an emulated 386, and one using LDT/GDT ops to run on a local 386 in protected mode. Willows Software has made the toolkit and emulation module available to the free UNIX community, not just Linux. There was a list for people who had agreed to their non-disclosure and obtained the software for porting to FreeBSD. Sujal Patel was the primary source of FreeBSD fixes (I am also on the list). I haven't seen any traffic on the list for quite some time now. There was at least a beta version (their code, plus our patches) up for FTP on their site for FreeBSD. I believe that the changes have been sufficiently radical in -current that the code needs some work, but it was running Windows apps sufficiently to run MSWord on the 386 emulator under FreeBSD, and Sujal was working on some stack problems for running using the native processor in protected mode... 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 Aug 5 15:45:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28821 for current-outgoing; Mon, 5 Aug 1996 15:45:17 -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 PAA28815 for ; Mon, 5 Aug 1996 15:45:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12154; Mon, 5 Aug 1996 15:41:19 -0700 From: Terry Lambert Message-Id: <199608052241.PAA12154@phaeton.artisoft.com> Subject: Re: NIS Setup Question To: mark@grondar.za (Mark Murray) Date: Mon, 5 Aug 1996 15:41:19 -0700 (MST) Cc: scrappy@ki.net, mark@grondar.za, current@freebsd.org In-Reply-To: <199608032055.WAA01311@grumble.grondar.za> from "Mark Murray" at Aug 3, 96 10:55:42 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 > > > What does your "+" entry in your passwd file look like? > > > > +:+:::::::: > ^ > > WTF is this? It's a "plus" sign. 8^). It's also an error... 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 Aug 5 15:46:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29067 for current-outgoing; Mon, 5 Aug 1996 15:46:40 -0700 (PDT) Received: from arl-img-4.compuserve.com (arl-img-4.compuserve.com [149.174.217.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA29057 for ; Mon, 5 Aug 1996 15:46:38 -0700 (PDT) Received: by arl-img-4.compuserve.com (8.6.10/5.950515) id SAA01306; Mon, 5 Aug 1996 18:40:55 -0400 Date: 05 Aug 96 18:38:59 EDT From: Jan Knepper <100626.3506@CompuServe.COM> To: Khetan Gajjar , "[FreeBSD current]" Subject: Re: compile time Message-ID: <960805223859_100626.3506_BHL118-1@CompuServe.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Khetan Gajjar wrote: /* >this is not normal, on my P133, 32MByte it takes about tree and a half hour. It takes me 514 seconds for a kernel compile, and below speaks for itself. The PC is a Cyrix 6x86 P150+ with 32 mb RAM, on a board with 512kb pipe-line burst cache. make world completed on Sun Aug 4 01:25:03 SAT 1996 11162.37 real 6775.63 user 1383.49 sys */ Yes that is more like it. Is seems that some are mixing up with compiling a kernel or compiling the complete system.... A kernel recompile on 2.1.0 takes for me: text data bss dec hex 954368 61440 74356 1090164 10a274 257.32 real 162.45 user 18.24 sys Don't want to try a make world now Don't worry, be Kneppie, Jan From owner-freebsd-current Mon Aug 5 18:42:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04730 for current-outgoing; Mon, 5 Aug 1996 18:42:15 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA04688 for ; Mon, 5 Aug 1996 18:42:10 -0700 (PDT) Received: from irz301.inf.tu-dresden.de by mail.crl.com with SMTP id AA06087 (5.65c/IDA-1.5 for ); Mon, 5 Aug 1996 16:28:27 -0700 Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA09586; Tue, 6 Aug 1996 01:21:13 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA05924; Tue, 6 Aug 1996 01:21:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA06658; Mon, 5 Aug 1996 22:56:47 +0200 (MET DST) From: J Wunsch Message-Id: <199608052056.WAA06658@uriah.heep.sax.de> Subject: Re: How much space for CVS tree? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 5 Aug 1996 22:56:47 +0200 (MET DST) Cc: amir@neuron.net (Amir Y. Rosenblatt) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608051857.OAA15675@prozac.neuron.net> from "Amir Y. Rosenblatt" at "Aug 5, 96 02:57:37 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 Amir Y. Rosenblatt wrote: > I've been tracking -current for a few months now (pretty much since the > demise of 2.1-stable) and would like to start tracking the full CVS tree > as well. How much space should I allocate for the CVS tree? j@uriah 93% du -sk ~cvs 235400 /home/cvs This includes the ports and the (international) crypto CVS tree. -- 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 Aug 5 18:42:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04951 for current-outgoing; Mon, 5 Aug 1996 18:42:50 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA04927 for ; Mon, 5 Aug 1996 18:42:46 -0700 (PDT) Received: from phaeton.Artisoft.COM by mail.crl.com with SMTP id AA03282 (5.65c/IDA-1.5 for ); Mon, 5 Aug 1996 16:14:48 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA12258; Mon, 5 Aug 1996 16:09:20 -0700 From: Terry Lambert Message-Id: <199608052309.QAA12258@phaeton.artisoft.com> Subject: Re: How much space for CVS tree? To: amir@neuron.net (Amir Y. Rosenblatt) Date: Mon, 5 Aug 1996 16:09:19 -0700 (MST) Cc: current@freebsd.org In-Reply-To: <199608051857.OAA15675@prozac.neuron.net> from "Amir Y. Rosenblatt" at Aug 5, 96 02:57:37 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've been tracking -current for a few months now (pretty much since the > demise of 2.1-stable) and would like to start tracking the full CVS tree > as well. How much space should I allocate for the CVS tree? I am currently using 131M for: Attic etc release CLEAR-1.1.5.1-PATCHES games sbin COPYRIGHT,v gnu secure Makefile,v include share TODO-2.1 kerberosIV sys bin lib tools contrib libexec usr.bin eBones lkm usr.sbin I would say 300M or so for a full tree + checkout to make it buildable with local obj storage. 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 Aug 5 18:43:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05034 for current-outgoing; Mon, 5 Aug 1996 18:43:00 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA04995 for ; Mon, 5 Aug 1996 18:42:55 -0700 (PDT) Received: from moonpie.w8hd.org by mail.crl.com with SMTP id AA09174 (5.65c/IDA-1.5 for ); Mon, 5 Aug 1996 16:43:02 -0700 Received: from localhost (kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) with SMTP id TAA02166 for ; Mon, 5 Aug 1996 19:41:21 -0400 (EDT) X-Authentication-Warning: moonpie.w8hd.org: kimc owned process doing -bs Date: Mon, 5 Aug 1996 19:41:21 -0400 (EDT) From: Kim Culhan To: current@FreeBSD.org Subject: -current kernel build fails Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This was mentioned about 24 hrs ago on the list yet a sup from ~0800 UTC this date still has this kernel build failure: -DNFS -DFFS -DINET -DKERNEL ../../net/if_ethersubr.c ../../net/if_ethersubr.c: In function `ether_ioctl': ../../net/if_ethersubr.c:869: `ETHER_ADDR_LEN' undeclared (first use this function) ../../net/if_ethersubr.c:869: (Each undeclared identifier is reported only once ../../net/if_ethersubr.c:869: for each function it appears in.) Any help greatly appreciated, the sup server is very busy so if this is fixed 'manually' here it could happen much sooner.. regards kim -- kimc@w8hd.org From owner-freebsd-current Mon Aug 5 18:43:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05118 for current-outgoing; Mon, 5 Aug 1996 18:43:13 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA05098 for ; Mon, 5 Aug 1996 18:43:09 -0700 (PDT) Received: from phaeton.Artisoft.COM by mail.crl.com with SMTP id AA00660 (5.65c/IDA-1.5 for ); Mon, 5 Aug 1996 16:00:28 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12200; Mon, 5 Aug 1996 15:55:33 -0700 From: Terry Lambert Message-Id: <199608052255.PAA12200@phaeton.artisoft.com> Subject: Re: Questions about the CVS and CTM To: plm@xs4all.nl (Peter Mutsaers) Date: Mon, 5 Aug 1996 15:55:33 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <87686zv1i6.fsf@localhost.xs4all.nl> from "Peter Mutsaers" at Aug 4, 96 01:21:05 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 > What I did was 'cvs checkout src'. Then I get a copy of src, and I can > do a 'make world' in it. I can do 'cvs update' in the future, right? > > This does cost lots and lots of diskspace, since I have to have both > the CVS source and the checked-out source on disk (together with the > objects). Is there a more efficient way? I have been thinking about this, though not specifically in tthis context. I'd like to be able to build from a CD to the local machine without requiring me to copy the CD or keep anything but the objects for the source I'm currently compiling on the system. The idea of having the build process check out the most recent sources (or a specific tag from an environment variable) and build, with a remove-behind for after it's installed, would be a good idea. > Another question: how do I make local modifications? If I do this and > cvs commit them to my local cvs repository (maybe as a branch) then I > have a problem since ctm's md5 checksums won't match anymore, thus ctm > will fail. (I need to have ISDN support within two days, thus I'll > patch bisdn in). CVSup. Follow the answer to my -hackers question on the announcement by John Polstra... if he replies, it should tell you exactly how to do what you want (and what I want, in fact). > Yet another ctm question: Is it possible to omit a certain branch, for > example src/games or ports/japanese? I could just remove it from disk > since I don't need it and don't like to waste diskspace on it, but > then also ctm updates will fail when they try to patch something in > these directories. Or will ctm just skip them and continue? I believe you can process only the deltas for the collections you are interested in and throw the others away. I don't know if you can tell it not to send you all of them, though... 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 Aug 5 19:18:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA09223 for current-outgoing; Mon, 5 Aug 1996 19:18:17 -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 TAA09207 for ; Mon, 5 Aug 1996 19:18:10 -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 QAA18526 for ; Mon, 5 Aug 1996 16:11:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA12220; Mon, 5 Aug 1996 16:01:49 -0700 From: Terry Lambert Message-Id: <199608052301.QAA12220@phaeton.artisoft.com> Subject: Re: snd into -current To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Mon, 5 Aug 1996 16:01:49 -0700 (MST) Cc: freebsd-current@freefall.freebsd.org, multimedia@freebsd.org In-Reply-To: <199608051519.RAA06208@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Aug 5, 96 05:19:46 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 > Are there any reasons to not integrate snd01041996-2.2-current.tgz > into -current given that -current is experimental anyway and there > are no stringent stability considerations? > > Recent augmentations in the linux_ioctl area (sound ioctls) > make it a pain to keep up with -current while still using > the newer sounddriver. Is this the new sound code with the GPL license, or the old sound code with the more lenient license? There was a big discussion on the license change, and the consensus seemed to be to not update the code, since a GPL code in the kernel makes the kernel non-distributable because of the conflicts between the GPL "no additional conditions" clause and the BSD "give credit" clause. 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 Aug 5 20:24:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA14045 for current-outgoing; Mon, 5 Aug 1996 20:24:35 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA14031 for ; Mon, 5 Aug 1996 20:24:28 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id VAA06564; Mon, 5 Aug 1996 21:23:56 -0600 (MDT) Message-Id: <199608060323.VAA06564@rover.village.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Questions about the CVS and CTM Cc: freebsd-current@freebsd.org (FreeBSD-current users), plm@xs4all.nl (Peter Mutsaers) In-reply-to: Your message of Mon, 05 Aug 1996 20:13:43 +0200 Date: Mon, 05 Aug 1996 21:23:55 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : As Peter Mutsaers wrote: : : > I now have the CVS version of the sources unpacked. Now if I want to : > do make world, what is the normal thing to do? : > : > What I did was 'cvs checkout src'. Then I get a copy of src, and I can : > do a 'make world' in it. I can do 'cvs update' in the future, right? : : Right. cvs update won't grab new directories that appear from time to time. You'll need to do cvs checkout src for that from time to time still. However, it is effectively an update on an already checked out tree, so it isn't as expensive as the original checkout. BTW, I've found that keeping the CVS tree on a slow, possibly removable disk helps me keep the number of system utilities installed to a maximum :-). JAZ drive is what I use, since anything else couldn't hold the CVS tree (since the others are all < 250M that I've seen). I also hold my OpenBSD sources and my NetBSD reference sources as well on this JAZ drive, in addition to a couple of Linux versions and X11R6.1 sources and build tree (second disk cart for these, however). A handy device to have around when you want to hack at a lot of different things, but not all at once... On the second cart I also keep the old CTM diffs too, since they otherwise take up 50Mish somewhere (or I have to FTP a 35M file, which is somewhat painful to do). Nice drives for $400 with carts ~100 in quantity. Warner From owner-freebsd-current Mon Aug 5 20:30:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA14426 for current-outgoing; Mon, 5 Aug 1996 20:30:04 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA14372 for ; Mon, 5 Aug 1996 20:29:37 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id VAA06597; Mon, 5 Aug 1996 21:28:55 -0600 (MDT) Message-Id: <199608060328.VAA06597@rover.village.org> To: "Amir Y. Rosenblatt" Subject: Re: How much space for CVS tree? Cc: current@freebsd.org In-reply-to: Your message of Mon, 05 Aug 1996 14:57:37 EDT Date: Mon, 05 Aug 1996 21:28:54 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : I've been tracking -current for a few months now (pretty much since the : demise of 2.1-stable) and would like to start tracking the full CVS tree : as well. How much space should I allocate for the CVS tree? I have a whole JAZ drive dedicated to this purpose. Well, I sometimes cheat and also put OpenBSD and Linux sources on there as well. I'd say you'll want to have about 600M of space that you can dedicate to these purposes before starting down this path. The only problem with my JAZ drive is that it slower than the new, cool SCSI disks which makes build times longer (on an overnight build for me, however, the difference between 8hr and 12hr isn't a big deal). The CVS tree is about 230M. The sources checked out are about 210M. The obj tree escapes me at the moment, but either 100M or 150M sticks in my head. Warner From owner-freebsd-current Mon Aug 5 21:20:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA17354 for current-outgoing; Mon, 5 Aug 1996 21:20:48 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA17346 for ; Mon, 5 Aug 1996 21:20:44 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id VAA15503; Mon, 5 Aug 1996 21:20:13 -0700 (PDT) Message-Id: <199608060420.VAA15503@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Khetan Gajjar cc: A JOSEPH KOSHY , freebsd-current@freebsd.org Subject: Re: Patch to recognize AMD 5x86 cpus In-reply-to: Your message of Sat, 05 Aug 96 22:35:08 +0200. Date: Mon, 05 Aug 1996 21:20:01 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Mon, 5 Aug 1996, A JOSEPH KOSHY wrote: > >>Enclosed is a patch to recognize and print the kind of AMD 5x86 cpu >>on-board at boot time. This is per AMD's application note on CPU >>recognition. > >Is anyone working on Cyrix-patches/changes ? > >I know they won't compile with I586_CPU in the kernel, because they don't >implement the full Pentium instruction set. I assume you mean with *only* I586_CPU in the kernel. And, it shouldn't (at least for the AMD), because the AMD 5x86 is in reality just a souped-up 486. I haven't looked closely enough at the Cyrix 5x86 to see if it has any programmable enhancements above a 486. I know it's still for a 486 socket, and in spirit, it's more a 486 than a Pentium. Furthermore, the Cyrix 6x86 is just a souped-up Pentium, in spite of what their marketing department wants to call it. If there is only an I686_CPU target in the kernel, I would expect that not to run on a Cyrix 6x86. ----------------------------------------------------------------------------- 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 Aug 5 21:35:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA19448 for current-outgoing; Mon, 5 Aug 1996 21:35:31 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA19434 for ; Mon, 5 Aug 1996 21:35:26 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id VAA02381; Mon, 5 Aug 1996 21:33:54 -0700 From: "Rodney W. Grimes" Message-Id: <199608060433.VAA02381@GndRsh.aac.dev.com> Subject: Re: Questions about the CVS and CTM To: imp@village.org (Warner Losh) Date: Mon, 5 Aug 1996 21:33:53 -0700 (PDT) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org, plm@xs4all.nl In-Reply-To: <199608060323.VAA06564@rover.village.org> from Warner Losh at "Aug 5, 96 09:23:55 pm" 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 > > : As Peter Mutsaers wrote: > : > : > I now have the CVS version of the sources unpacked. Now if I want to > : > do make world, what is the normal thing to do? > : > > : > What I did was 'cvs checkout src'. Then I get a copy of src, and I can > : > do a 'make world' in it. I can do 'cvs update' in the future, right? > : > : Right. > > cvs update won't grab new directories that appear from time to time. > You'll need to do cvs checkout src for that from time to time still. > However, it is effectively an update on an already checked out tree, > so it isn't as expensive as the original checkout. ``cvs update -d'' _will_ grab new directories. And if you want it to prune away the old ones add a ``-P''. The normal and correct way to keep a checked out tree up to date is with: cvs update -P -d if you want to cut down on the noise level: cvs -q update -P -d The correct way to check out an initial tree is cvs co -P module The -P option keeps the initial checkout from getting stuff that has been removed from the active part of the branch or head via cvs remove. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Aug 5 21:41:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA21187 for current-outgoing; Mon, 5 Aug 1996 21:41:38 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA21162 for ; Mon, 5 Aug 1996 21:41:34 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id VAA02401; Mon, 5 Aug 1996 21:41:10 -0700 From: "Rodney W. Grimes" Message-Id: <199608060441.VAA02401@GndRsh.aac.dev.com> Subject: Re: How much space for CVS tree? To: imp@village.org (Warner Losh) Date: Mon, 5 Aug 1996 21:41:10 -0700 (PDT) Cc: amir@neuron.net, current@freebsd.org In-Reply-To: <199608060328.VAA06597@rover.village.org> from Warner Losh at "Aug 5, 96 09:28:54 pm" 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 > : I've been tracking -current for a few months now (pretty much since the > : demise of 2.1-stable) and would like to start tracking the full CVS tree > : as well. How much space should I allocate for the CVS tree? > > I have a whole JAZ drive dedicated to this purpose. Well, I sometimes > cheat and also put OpenBSD and Linux sources on there as well. I'd > say you'll want to have about 600M of space that you can dedicate to > these purposes before starting down this path. The only problem with > my JAZ drive is that it slower than the new, cool SCSI disks which > makes build times longer (on an overnight build for me, however, the > difference between 8hr and 12hr isn't a big deal). > > The CVS tree is about 230M. 242MB by last count, and some growth history (You'd have to scale this for gzip/tar vs expanded.): -rw-rw-r-- 1 root wheel 50707911 Mar 7 22:18 ncvs_960308_0343.tgz -rw-rw-r-- 1 root wheel 51409677 Mar 25 04:32 ncvs_960325_0228.tgz -rw-rw-r-- 1 root wheel 51820568 Apr 12 02:16 ncvs_960411_2122.tgz -rw-rw-r-- 1 root wheel 51975918 Apr 20 18:39 ncvs_960420_1725.tgz -rw-rw-r-- 1 root wheel 52605421 May 12 12:27 ncvs_960512_1003.tgz -rw-rw-r-- 1 root wheel 52648121 May 17 19:26 ncvs_960517_1731.tgz -rw-rw-r-- 1 root wheel 52851675 May 27 15:41 ncvs_960527_1352.tgz -rw-rw-r-- 1 root wheel 53686222 Jun 10 04:10 ncvs_960610_0124.tgz -rw-rw-r-- 1 root wheel 53795112 Jun 15 11:55 ncvs_960615_1022.tgz -rw-rw-r-- 1 root wheel 55980807 Jun 24 12:19 ncvs_960623_0850.tgz -rw-rw-r-- 1 root wheel 55963158 Jun 29 23:52 ncvs_960629_1943.tgz -rw-rw-r-- 1 root wheel 56013616 Jul 3 18:09 ncvs_960703_1501.tgz -rw-rw-r-- 1 root wheel 56312931 Jul 12 11:31 ncvs_960712_0851.tgz -rw-rw-r-- 1 root wheel 56412963 Jul 14 11:13 ncvs_960713_2155.tgz -rw-rw-r-- 1 root wheel 56608153 Jul 22 15:08 ncvs_960722_1107.tgz -rw-rw-r-- 1 root wheel 56977897 Aug 3 05:49 ncvs_960803_0112.tgz > The sources checked out are about 210M. Ahh... /dev/sd0g 158863 124735 21418 85% /usr/src #2.1-stable /dev/sd0g 158863 135216 10938 93% /usr/src #2.2-current And the later is slightly bloated as I have Justin expermental patches for the scsi system applied. Also you'll need about 5MB or so to compile a kernel in. > The obj tree escapes me at the moment, but either 100M or 150M sticks > in my head. More like 88MB. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Aug 5 22:23:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA29558 for current-outgoing; Mon, 5 Aug 1996 22:23:58 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA29538 for ; Mon, 5 Aug 1996 22:23:55 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA25666; Mon, 5 Aug 1996 23:23:12 -0600 (MDT) Date: Mon, 5 Aug 1996 23:23:12 -0600 (MDT) Message-Id: <199608060523.XAA25666@rocky.mt.sri.com> From: Nate Williams To: Warner Losh Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freebsd.org (FreeBSD-current users), plm@xs4all.nl (Peter Mutsaers) Subject: Re: Questions about the CVS and CTM In-Reply-To: <199608060323.VAA06564@rover.village.org> References: <199608060323.VAA06564@rover.village.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > : > I now have the CVS version of the sources unpacked. Now if I want to > : > do make world, what is the normal thing to do? > : > > : > What I did was 'cvs checkout src'. Then I get a copy of src, and I can > : > do a 'make world' in it. I can do 'cvs update' in the future, right? > : > : Right. > > cvs update won't grab new directories that appear from time to time. Sure it will. You just need to tell it to. trout:~ % cvs -H update Usage: cvs update [-APdflRp] [-k kopt] [-r rev|-D date] [-j rev] [-I ign] [-W spec] [files...] -A Reset any sticky tags/date/kopts. -P Prune empty directories. -d Build directories, like checkout does. .... Note '-d', which will allow it to 'build' new directories. Also note '-P', which causes it to remove directories that become emtpy as they occur. Why this isn't the default behavior has been subject to much discussion on the CVS mailing lists. :( Nate From owner-freebsd-current Mon Aug 5 23:26:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA24826 for current-outgoing; Mon, 5 Aug 1996 23:26:52 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA24724 for ; Mon, 5 Aug 1996 23:26:42 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id IAA12761; Tue, 6 Aug 1996 08:22:43 +0200 (SAT) Message-Id: <199608060622.IAA12761@grumble.grondar.za> To: Warner Losh cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freebsd.org (FreeBSD-current users), plm@xs4all.nl (Peter Mutsaers) Subject: Re: Questions about the CVS and CTM Date: Tue, 06 Aug 1996 08:22:42 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Warner Losh wrote: > : > What I did was 'cvs checkout src'. Then I get a copy of src, and I can > : > do a 'make world' in it. I can do 'cvs update' in the future, right? > : > : Right. > > cvs update won't grab new directories that appear from time to time. > You'll need to do cvs checkout src for that from time to time still. > However, it is effectively an update on an already checked out tree, > so it isn't as expensive as the original checkout. cvs update -Pd will do this. -P prunes empty directories. -d creates new ones. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Aug 6 00:19:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA21830 for current-outgoing; Tue, 6 Aug 1996 00:19:06 -0700 (PDT) Received: from ian.iafrica.com (root@ian.iafrica.com [196.31.1.15]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA21779 for ; Tue, 6 Aug 1996 00:18:53 -0700 (PDT) Received: from ian.iafrica.com (khetan@ian.iafrica.com [196.31.1.15]) by ian.iafrica.com (8.7.5/8.6.12) with SMTP id JAA22896; Tue, 6 Aug 1996 09:17:02 +0200 (SAT) Date: Tue, 6 Aug 1996 09:17:02 +0200 (SAT) From: Khetan Gajjar To: "Michael L. VanLoon -- HeadCandy.com" cc: freebsd-current@freebsd.org Subject: Re: Patch to recognize AMD 5x86 cpus In-Reply-To: <199608060420.VAA15503@MindBender.HeadCandy.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, 5 Aug 1996, Michael L. VanLoon -- HeadCandy.com wrote: > I assume you mean with *only* I586_CPU in the kernel. Yes - i.e. the only CPU-type identifier. > reality just a souped-up 486. Yup - but they're pretty fast. > I haven't looked closely enough at the Cyrix 5x86 to see if it has any > programmable enhancements above a 486. I know it's still for a 486 > socket, and in spirit, it's more a 486 than a Pentium. Was aware of this. > Furthermore, the Cyrix 6x86 is just a souped-up Pentium, in spite of > what their marketing department wants to call it. If there is only an > I686_CPU target in the kernel, I would expect that not to run on a > Cyrix 6x86. No, with only a I586_CPU target in the kernel, the machine won't boot - can't determine CPU type or something to that effect. --- Khetan Gajjar [ http://www.iafrica.com/~khetan ] UUNet Internet Africa [ 0800-030-002 & help@iafrica.com ] Get rid of Telkom.... [ http://www.ispa.org.za ] I'm a FreeBSD User! [ http://www.freebsd.org ] Any opinions stated in this message are personal. UIA's official policy may not be reflected in this message. From owner-freebsd-current Tue Aug 6 00:26:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24118 for current-outgoing; Tue, 6 Aug 1996 00:26:36 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23375 for ; Tue, 6 Aug 1996 00:24:01 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id AAA15897; Tue, 6 Aug 1996 00:23:14 -0700 (PDT) Message-Id: <199608060723.AAA15897@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Khetan Gajjar cc: freebsd-current@freebsd.org Subject: Re: Patch to recognize AMD 5x86 cpus In-reply-to: Your message of Sat, 06 Aug 96 09:17:02 +0200. Date: Tue, 06 Aug 1996 00:23:12 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Furthermore, the Cyrix 6x86 is just a souped-up Pentium, in spite of >> what their marketing department wants to call it. If there is only an >> I686_CPU target in the kernel, I would expect that not to run on a >> Cyrix 6x86. >No, with only a I586_CPU target in the kernel, the machine won't boot - >can't determine CPU type or something to that effect. Then this is a "bug" (or more accurately, an unhandled case). I _WOULD_ expect it to run a Cyrix 6x86 with only I586_CPU, and to _NOT_ run with only I486_CPU. As I stated above (and I think you also asserted), it also should _NOT_ work with only I686_CPU, which at this point, would only cover the "Pentium Pro". I take it we're saying the same thing in different ways. :-) ----------------------------------------------------------------------------- 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 Tue Aug 6 00:50:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA00887 for current-outgoing; Tue, 6 Aug 1996 00:50:29 -0700 (PDT) Received: from ian.iafrica.com (ian.iafrica.com [196.31.1.15]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA00803 for ; Tue, 6 Aug 1996 00:50:15 -0700 (PDT) Received: from ian.iafrica.com (khetan@ian.iafrica.com [196.31.1.15]) by ian.iafrica.com (8.7.5/8.6.12) with SMTP id JAA23408; Tue, 6 Aug 1996 09:49:20 +0200 (SAT) Date: Tue, 6 Aug 1996 09:49:15 +0200 (SAT) From: Khetan Gajjar To: "Michael L. VanLoon -- HeadCandy.com" cc: freebsd-current@freebsd.org Subject: Re: Patch to recognize AMD 5x86 cpus In-Reply-To: <199608060723.AAA15897@MindBender.HeadCandy.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, 6 Aug 1996, Michael L. VanLoon -- HeadCandy.com wrote: > Then this is a "bug" (or more accurately, an unhandled case). I > _WOULD_ expect it to run a Cyrix 6x86 with only I586_CPU, and to _NOT_ > run with only I486_CPU. To re-iterate : it works with I486_CPU, and doesn't with I586_CPU. I didn't bother with I686_CPU - that will definitely not work. --- Khetan Gajjar [ http://www.iafrica.com/~khetan ] UUNet Internet Africa [ 0800-030-002 & help@iafrica.com ] Get rid of Telkom.... [ http://www.ispa.org.za ] I'm a FreeBSD User! [ http://www.freebsd.org ] Any opinions stated in this message are personal. UIA's official policy may not be reflected in this message. From owner-freebsd-current Tue Aug 6 01:14:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04309 for current-outgoing; Tue, 6 Aug 1996 01:14:49 -0700 (PDT) Received: from voltimand.csd.wwwi.com (voltimand.csd.wwwi.com [199.1.92.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA04304 for ; Tue, 6 Aug 1996 01:14:46 -0700 (PDT) Received: from cornelius.csd.wwwi.com (cornelius.csd.wwwi.com [199.1.92.20]) by voltimand.csd.wwwi.com (8.7.5/8.7.3) with SMTP id BAA27815; Tue, 6 Aug 1996 01:13:25 -0700 (MST) Message-Id: <199608060813.BAA27815@voltimand.csd.wwwi.com> X-Sender: jdw@pop.wwwi.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 06 Aug 1996 01:14:25 -0700 To: "Michael L. VanLoon -- HeadCandy.com" From: "Jeffrey D. Wheelhouse" Subject: Re: Patch to recognize AMD 5x86 cpus Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:20 PM 8/5/96 -0700, Michael L. VanLoon -- HeadCandy.com wrote: >Furthermore, the Cyrix 6x86 is just a souped-up Pentium, in spite of >what their marketing department wants to call it. If there is only an >I686_CPU target in the kernel, I would expect that not to run on a >Cyrix 6x86. Is I686_CPU valid/useful in 2.1.5? Later, Jeff From owner-freebsd-current Tue Aug 6 02:43:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08302 for current-outgoing; Tue, 6 Aug 1996 02:43:53 -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 CAA08293 for ; Tue, 6 Aug 1996 02:43:47 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id FAA00106; Tue, 6 Aug 1996 05:35:30 -0400 (EDT) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA28931; Tue, 6 Aug 1996 11:35:19 +0200 Message-Id: <9608060935.AA28931@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: current@freebsd.org In-Reply-To: Message from Terry Lambert of Mon, 05 Aug 96 15:38:13 PDT. Reply-To: gjennejohn@frt.dec.com Subject: Re: Linux Willows? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Aug 96 11:35:18 +0200 X-Mts: smtp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk terry@lambert.org writes: > > Could someone explain what Linux Willow is and where to get a copy of it > > from? > There was a list for people who had agreed to their non-disclosure and > obtained the software for porting to FreeBSD. Sujal Patel was the > primary source of FreeBSD fixes (I am also on the list). I haven't > seen any traffic on the list for quite some time now. > > There was at least a beta version (their code, plus our patches) up for > FTP on their site for FreeBSD. I believe that the changes have been > sufficiently radical in -current that the code needs some work, but > it was running Windows apps sufficiently to run MSWord on the 386 > emulator under FreeBSD, and Sujal was working on some stack problems > for running using the native processor in protected mode... > unfortunately, the only source tarball on the server is still 1.5.2 from February. I doubt that this corresponds to the new 2.0 binaries available now. Some time ago Jordan sent Willows a CD and supposedly they were planning to set up a development machine. Doesn't look like this ever happened :( --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org From owner-freebsd-current Tue Aug 6 03:00:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA09057 for current-outgoing; Tue, 6 Aug 1996 03:00:48 -0700 (PDT) Received: from dub-img-1.compuserve.com (dub-img-1.compuserve.com [149.174.206.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA09045 for ; Tue, 6 Aug 1996 03:00:44 -0700 (PDT) Received: by dub-img-1.compuserve.com (8.6.10/5.950515) id FAA19959; Tue, 6 Aug 1996 05:58:37 -0400 Date: 06 Aug 96 05:57:33 EDT From: Jan Knepper <100626.3506@CompuServe.COM> To: Khetan Gajjar , "[FreeBSD current]" Subject: Re: compile time Message-ID: <960806095732_100626.3506_BHL105-1@CompuServe.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kheten Gajjar wrote: /* > A kernel recompile on 2.1.0 takes for me: > text data bss dec hex > 954368 61440 74356 1090164 10a274 > 257.32 real 162.45 user 18.24 sys Wow! What machine have you got ? */ A Pentium Pro 200, 64 MB RAM, NCR SCSI-2 2.1 GB HD, 6x SCSI CD-ROM... I am running my own company and have a couple of machine's. Only P's though. The PP200 is the latest toy. I think it is in for almost 2 months now, may be longer already. I usually develop in C++ for Window NT/95, 3.1x, OS/2 Warp, Novell NetWare. Header files and other stuff is getting so *huge* that a faster machines really pays off these days... I used a P120 before. The compile time turned out to be LESS than half what is was before! That is what I call improvement. Don't worry, be Kneppie, Jan From owner-freebsd-current Tue Aug 6 03:17:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA10038 for current-outgoing; Tue, 6 Aug 1996 03:17:59 -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 DAA09852 for ; Tue, 6 Aug 1996 03:14:44 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA19255; Tue, 6 Aug 1996 08:53:12 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA10438; Tue, 6 Aug 1996 08:51:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA08921; Tue, 6 Aug 1996 08:30:44 +0200 (MET DST) From: J Wunsch Message-Id: <199608060630.IAA08921@uriah.heep.sax.de> Subject: Re: Questions about the CVS and CTM To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Tue, 6 Aug 1996 08:30:44 +0200 (MET DST) Cc: imp@village.org (Warner Losh), plm@xs4all.nl Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608060323.VAA06564@rover.village.org> from Warner Losh at "Aug 5, 96 09:23:55 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 Warner Losh wrote: > : > What I did was 'cvs checkout src'. Then I get a copy of src, and I can > : > do a 'make world' in it. I can do 'cvs update' in the future, right? > : > : Right. > > cvs update won't grab new directories that appear from time to time. cvs update -P -d -A -- 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 Tue Aug 6 03:21:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA10291 for current-outgoing; Tue, 6 Aug 1996 03:21:28 -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 DAA10281 for ; Tue, 6 Aug 1996 03:21:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA19207; Tue, 6 Aug 1996 08:50:49 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA10434; Tue, 6 Aug 1996 08:50:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA08889; Tue, 6 Aug 1996 08:27:29 +0200 (MET DST) From: J Wunsch Message-Id: <199608060627.IAA08889@uriah.heep.sax.de> Subject: Re: CD-R compatiblities To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Tue, 6 Aug 1996 08:27:29 +0200 (MET DST) Cc: eischen@vigrid.com (Daniel Eischen) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9608052037.AA08267@pcnet1.pcnet.com> from Daniel Eischen at "Aug 5, 96 04:37:56 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 Daniel Eischen wrote: > I've got to write a purchase order for a CD-ROM burner (to be used > under FreeBSD). I know that the HP SureStore works with FreeBSD, > but how about any 4x recorders? Anyone get the wormcontrol in > -current to work with the Yamaha line of CD-Rs? Well, it's not ``getting wormcontrol to work''. ;) Wormcontrol is a simple hook to the ioctl's of the driver, 169 lines of C code, including the copyright notice. The mere problem is to convince Yamaha to get you their SCSI documentation. Last time i've checked, they required me to fax them a sheet with figures about ``expected sales next year'' and other crap. Somebody should point them out that all their competitors have realized that providing technical specifications to their users on request is a good thing. Writing the kernel hooks should not be too difficult. If i remember right from the Linux cdwrite command, the Yamaha needs a coupld of MODE SELECTs to prepare it for writing. However, trial&error with a CD-R is like fishing in the dark... > wormcontrol doesn't seem to be available in -stable (from late > June). I have to wait for the 2.1.5R CD to come before trying > that. Has anyone ported the -current wormcontrol back to 2.1.5R > or thereabouts? The worm driver has been backported from 2.2-current to 2.1.5R, and wormcontrol(8) is also there. HOWEVER: if you want to play with an unmodified 2.1.5, get a Plasmon burner, and never boot it with a CD-ROM or fixated CD-R in the drive. Otherwise, it will announce itself as a CD-ROM (the HP 4020i will always do it this way), and be assigned to the `cd' driver. The SCSI code in 2.1.5 lacks the `type override' feature of -current, where a drive that is lying about its device type can be forcibly assigned to a `foreign' driver. -- 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 Tue Aug 6 03:21:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA10320 for current-outgoing; Tue, 6 Aug 1996 03:21:40 -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 DAA10305; Tue, 6 Aug 1996 03:21:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA19277; Tue, 6 Aug 1996 08:53:23 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA10439; Tue, 6 Aug 1996 08:53:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA08949; Tue, 6 Aug 1996 08:32:49 +0200 (MET DST) From: J Wunsch Message-Id: <199608060632.IAA08949@uriah.heep.sax.de> Subject: Re: -current kernel build fails To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Tue, 6 Aug 1996 08:32:49 +0200 (MET DST) Cc: kimc@w8hd.org (Kim Culhan), phk@freebsd.org (Poul-Henning Kamp) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Kim Culhan at "Aug 5, 96 07:41:21 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 Kim Culhan wrote: > ../../net/if_ethersubr.c:869: `ETHER_ADDR_LEN' undeclared (first use this > function) Ask phk for this. -- 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 Tue Aug 6 04:13:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13182 for current-outgoing; Tue, 6 Aug 1996 04:13:26 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA13167 for ; Tue, 6 Aug 1996 04:13:03 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id NAA25847 for ; Tue, 6 Aug 1996 13:08:06 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA09546 for freebsd-current@freefall.cdrom.com; Tue, 6 Aug 1996 13:21:20 +0200 Date: Tue, 6 Aug 1996 13:21:20 +0200 From: "Christoph P. Kukulies" Message-Id: <199608061121.NAA09546@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: ncr dead message Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I found this in my /var/log/messages: (2.2-current of Aug 1st) Aug 2 10:29:13 isdn /kernel: ncr0:0: ERROR (80:4) (8-0-0) (8/13) @ (b30:c0000001). Aug 2 10:29:26 isdn /kernel: script cmd = 800c0006 Aug 2 10:29:26 isdn /kernel: reg: da 00 80 13 47 08 00 1f 01 08 80 00 80 00 0e 02. Aug 2 10:29:26 isdn /kernel: ncr0: restart (ncr dead ?). Aug 2 10:29:26 isdn /kernel: ncr0: restart (ncr dead ?). Aug 2 10:29:26 isdn /kernel: swap_pager: I/O error - async pageout failed; blkno 9984, size 8192, error 5 Aug 2 10:29:26 isdn /kernel: swap_pager_finish: I/O error, clean of page 916000 failed Aug 2 10:29:26 isdn /kernel: swap_pager_finish: I/O error, clean of page 913000 failed Aug 2 10:29:26 isdn /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Aug 2 10:29:26 isdn /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Aug 2 10:29:26 isdn /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred Aug 2 10:29:26 isdn /kernel: , retries:4 Aug 2 10:37:55 isdn /kernel: sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Aug 2 10:37:55 isdn /kernel: sd1(ncr0:1:0): UNIT ATTENTION asc:29,0 Aug 2 10:37:55 isdn /kernel: sd1(ncr0:1:0): Power on, reset, or bus device reset occurred Aug 2 10:37:55 isdn /kernel: , retries:4 It was a single occurance and maybe a transient failure. Anyway, I'm reporting it here just fyi. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Aug 6 04:19:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13551 for current-outgoing; Tue, 6 Aug 1996 04:19:16 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA13456 for ; Tue, 6 Aug 1996 04:18:11 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id NAA25897 for ; Tue, 6 Aug 1996 13:13:47 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA09560 for freebsd-current@freefall.cdrom.com; Tue, 6 Aug 1996 13:27:02 +0200 Date: Tue, 6 Aug 1996 13:27:02 +0200 From: "Christoph P. Kukulies" Message-Id: <199608061127.NAA09560@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: boot screen flashes - why? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk When booting my machine (Amd5x86, ASUS SP3G, ELSA Winner 1000 PCI) The screen flashes (blanked out black) two times. Once right after ther fdc/fd0 probe, second some time later - don't know exactly where at the moment. Today it happened that (with a today's kernel) during that screen flash the screen remained black and the machine was frozen - had to power cycle. Where do these screen flashes come from? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Aug 6 04:19:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13576 for current-outgoing; Tue, 6 Aug 1996 04:19:20 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA13218 for ; Tue, 6 Aug 1996 04:14:42 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id NAA25878 for ; Tue, 6 Aug 1996 13:10:12 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA09551 for freebsd-current@freefall.cdrom.com; Tue, 6 Aug 1996 13:23:27 +0200 Date: Tue, 6 Aug 1996 13:23:27 +0200 From: "Christoph P. Kukulies" Message-Id: <199608061123.NAA09551@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: time calibration messages - to worry about? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm getting these kernel messages during boot: Jul 27 16:00:14 isdn /kernel: Calibrating clock(s) relative to mc146818 A clock... Jul 27 16:00:14 isdn /kernel: i8254 clock: 1217043 Hz Jul 27 16:00:14 isdn /kernel: 1217043 Hz differs from default of 119318 2 Hz by more than 1% CPU is a Amd5x86 DX4/133. Board is an ASUS SP3G. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Aug 6 06:18:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA18235 for current-outgoing; Tue, 6 Aug 1996 06:18:55 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA18228 for ; Tue, 6 Aug 1996 06:18:53 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id NAA03181; Tue, 6 Aug 1996 13:15:56 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma003177; Tue Aug 6 13:15:35 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id GAA25825; Tue, 6 Aug 1996 06:15:34 -0700 Date: Tue, 6 Aug 1996 06:15:34 -0700 From: "M.R.Murphy" Message-Id: <199608061315.GAA25825@meerkat.mole.org> To: khetan@iafrica.com, michaelv@HeadCandy.com Subject: Re: Patch to recognize AMD 5x86 cpus Cc: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Furthermore, the Cyrix 6x86 is just a souped-up Pentium, in spite of > > what their marketing department wants to call it. If there is only an > > I686_CPU target in the kernel, I would expect that not to run on a > > Cyrix 6x86. > > No, with only a I586_CPU target in the kernel, the machine won't boot - > can't determine CPU type or something to that effect. That's because a Cyrix 6x86 identifies as (from dmesg) CPU: i486DX (486-class CPU) That's a Cyrix 6x86 running at 120MHz true clock. An AMD 586/133 identifies as CPU: i486DX (486-class CPU) also. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Tue Aug 6 07:03:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19936 for current-outgoing; Tue, 6 Aug 1996 07:03:33 -0700 (PDT) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA19925 for ; Tue, 6 Aug 1996 07:03:26 -0700 (PDT) Received: (from chuck@localhost) by fang.cs.sunyit.edu (8.6.9/8.6.9) id KAA28193; Tue, 6 Aug 1996 10:01:33 -0400 Date: Tue, 6 Aug 1996 10:01:33 -0400 From: Charles Green Message-Id: <199608061401.KAA28193@fang.cs.sunyit.edu> In-Reply-To: garyj@frt.dec.com "Re: Linux Willows?" (Aug 6, 11:35) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: gjennejohn@frt.dec.com Subject: Re: Linux Willows? Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk garyj@frt.dec.com stands accused of saying: } Date: Aug 6, 11:35 } Subject: Re: Linux Willows? } } terry@lambert.org writes: } > > Could someone explain what Linux Willow is and where to get a copy of it } > > from? } > There was a list for people who had agreed to their non-disclosure and } > obtained the software for porting to FreeBSD. Sujal Patel was the } > primary source of FreeBSD fixes (I am also on the list). I haven't } > seen any traffic on the list for quite some time now. } > } > There was at least a beta version (their code, plus our patches) up for } > FTP on their site for FreeBSD. I believe that the changes have been } > sufficiently radical in -current that the code needs some work, but } > it was running Windows apps sufficiently to run MSWord on the 386 } > emulator under FreeBSD, and Sujal was working on some stack problems } > for running using the native processor in protected mode... } > } } unfortunately, the only source tarball on the server is still 1.5.2 } from February. I doubt that this corresponds to the new 2.0 binaries } available now. } } Some time ago Jordan sent Willows a CD and supposedly they were } planning to set up a development machine. Doesn't look like this } ever happened :( } Well, last week I dropped them some e-mail and asked them about the once promised FreeBSD port. (I also asked for permission to publish their response) } --- } Gary Jennejohn (work) gjennejohn@frt.dec.com } (home) Gary.Jennejohn@munich.netsurf.de } (play) gj@freebsd.org } } }-- End of excerpt from garyj@frt.dec.com Hello Charles, Thanks for your interest in the 32-bit Willows Toolkit (formerly known as TWIN APIW)! We just posted beta versions of Linux and Solaris, with Mac and the other UNIX versions coming soon. And no, there is no FreeBSD version planned available right now. HOWEVER, a significant amount of work went into it in the past (with the 16 bit version), which means that we could introduce a 32-bit version cross-platform toolkit (no xwin emulator for now) with a few more weeks of work. We have now gone to a commercial model (we charge for our products and services, since no one paid us for our products before) and can no longer expend engineering resources unless there is a return on our investment. I am sure you appreciate the problem! The Willows Toolkit for UNIX (includes source for the libraries for 9 different UNIX platforms) costs $4,995 per named developer (with sharp quantity discounts) + 20% per year for support. Not only is this price much lower than the other commercial alternatives, but we charge no royalties (others charge from $75 to $100 per shipped copy of the application you build), we provide the source to the libraries and we have a Macintosh version (so we're much more of a true cross-platform solution, we're not just UNIX). We could very well introduce a FreeBSD version within weeks if we had just 3 or 4 orders (to cover our costs). If you feel the availability of a cross-platform toolkit would make a difference toward a broader acceptance of FreeBSD, can you help drum up interest in it so we can justify finishing the work (and yes, it's OK to post this on the mailing lists)? We would very much like to introduce such a version, but we need help! I look forward to hearing from you, Charles! Best regards, Laurent -- Charles Green, PRC Inc. Rome Laboratory, NY From owner-freebsd-current Tue Aug 6 08:26:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA24666 for current-outgoing; Tue, 6 Aug 1996 08:26:13 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA24661 for ; Tue, 6 Aug 1996 08:26:09 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id QAA18007; Tue, 6 Aug 1996 16:29:38 +0100 (BST) Date: Tue, 6 Aug 1996 16:29:37 +0100 (BST) From: Developer To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: Linux Willows? In-Reply-To: <199608052238.PAA12141@phaeton.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 Mon, 5 Aug 1996, Terry Lambert wrote: > There was at least a beta version (their code, plus our patches) up for > FTP on their site for FreeBSD. I believe that the changes have been > sufficiently radical in -current that the code needs some work, but > it was running Windows apps sufficiently to run MSWord on the 386 > emulator under FreeBSD, and Sujal was working on some stack problems > for running using the native processor in protected mode... Thanks very much for the information - do you know the address of the ftp site that I might be able to get the freebsd version of xwin from? Regards, Trefor S. From owner-freebsd-current Tue Aug 6 08:38:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25120 for current-outgoing; Tue, 6 Aug 1996 08:38:15 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25114 for ; Tue, 6 Aug 1996 08:38:09 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id IAA18695; Tue, 6 Aug 1996 08:37:52 -0700 (PDT) Message-Id: <199608061537.IAA18695@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Jeffrey D. Wheelhouse" cc: freebsd-current@freebsd.org Subject: Re: Patch to recognize AMD 5x86 cpus In-reply-to: Your message of Tue, 06 Aug 96 01:14:25 -0700. <199608060813.BAA27815@voltimand.csd.wwwi.com> Date: Tue, 06 Aug 1996 08:37:51 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >At 09:20 PM 8/5/96 -0700, Michael L. VanLoon -- HeadCandy.com wrote: >>Furthermore, the Cyrix 6x86 is just a souped-up Pentium, in spite of >>what their marketing department wants to call it. If there is only an >>I686_CPU target in the kernel, I would expect that not to run on a >>Cyrix 6x86. >Is I686_CPU valid/useful in 2.1.5? I have no idea. I doubt GCC/GAS has any P6-specific code, yet. There is a conditional store that would be a very useful optimization (helps prevent pipeline stalls as opposed to conditional branch and store), if you were building specifically for a P6. See the Intel web site for more info. ----------------------------------------------------------------------------- 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 Tue Aug 6 08:39:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25154 for current-outgoing; Tue, 6 Aug 1996 08:39:04 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25137 for ; Tue, 6 Aug 1996 08:38:37 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id QAA18204; Tue, 6 Aug 1996 16:42:14 +0100 (BST) Date: Tue, 6 Aug 1996 16:42:13 +0100 (BST) From: Developer To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: Linux Willows? In-Reply-To: <199608052238.PAA12141@phaeton.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 Mon, 5 Aug 1996, Terry Lambert wrote: Ive just tried to run the linux version of the willows windows emulator (xwin) and run into an error:- Windows Directory: /fnews/sources/linux/willow/windows System Directory: /fnews/sources/linux/willow/windows/system X11 Configuration -------------------- Display: :0.0 Vendor: The XFree86 Project, Inc Mode: Asynchronous Hostname: fgate.flevel.co.uk XDOS Configuration ------------------ A: /dev/fd0 (FAT floppy) C: /var/news/sources/dos (native file system) D: /var/news/tmp (native file system) E: / (native file system) LASTDRIVE = E DRIVES = 4 BOOTDRIVE = E ROOTDRIVE = 5 MEMORY = 640Kb EXTENDED = 15360Kb FILES = 100 FatalAppExit: DPMI failure FatalAppExit: DPMI failure FatalAppExit: DPMI failure I did a ktrace on the program and it seems this error has occured:- 18720 xwin CALL fchown(0x1,0xefbfd6a4,0x10) 18720 xwin RET fchown -1 errno -38 Unknown error: -38 18720 xwin CALL write(0x2,0x81428f4,0x1c) 18720 xwin GIO fd 2 wrote 28 bytes "FatalAppExit: DPMI failure " Has anyone any idea why this might be? Regards, Trefor S. From owner-freebsd-current Tue Aug 6 08:51:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25958 for current-outgoing; Tue, 6 Aug 1996 08:51:11 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25951 for ; Tue, 6 Aug 1996 08:51:05 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id IAA18751; Tue, 6 Aug 1996 08:47:34 -0700 (PDT) Message-Id: <199608061547.IAA18751@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users), koshy@india.hp.com Subject: Re: Patch to recognize AMD 5x86 cpus In-reply-to: Your message of Mon, 05 Aug 96 20:01:12 +0200. <199608051801.UAA05659@uriah.heep.sax.de> Date: Tue, 06 Aug 1996 08:47:33 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Michael L. VanLoon -- HeadCandy.com wrote: >> If you wanted to do this The "Correct" Way, you might be better off >> rewriting the CPU identification code in locore.s to a more general, > identcpu.c >(It has been divorced from locore.s some time ago.) Not in 2.1.0, the system I had easy reference access to. Glad to see it has its own module now, though. Is it modular, well abstracted, comprehensive and all encompassing? I recommended looking through http://www.x86.org/ because that guy has pretty much all the info you need to identify *every* Intel-ish CPU. ----------------------------------------------------------------------------- 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 Tue Aug 6 09:04:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26970 for current-outgoing; Tue, 6 Aug 1996 09:04:39 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA26961 for ; Tue, 6 Aug 1996 09:04:34 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id MAA03056 for ; Tue, 6 Aug 1996 12:04:32 -0400 (EDT) Date: Tue, 6 Aug 1996 12:04:32 -0400 (EDT) From: Gary Roberts To: freebsd-current@freebsd.org Subject: locking up Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all. At first I thought it might have been me. But now after going to CURRENT, and also talking a friend of mine, I believe I may have found a bug? Sometimes, at no predetermined time, without warning, when switching VC's, I'll lock up. FreeBSD doesn't lockup just the keyboard, and I can only fix it by rebooting. Is this a bug everyone knows about, and doesn't really care to fix, or what. It's getting _VERY_ annonying. Me switching vc's, then locking up, and having to take it down(thus kicking off users) etc. Please let me know if there is a fix for this. Thanks Gary From owner-freebsd-current Tue Aug 6 09:28:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28138 for current-outgoing; Tue, 6 Aug 1996 09:28:45 -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 JAA28133 for ; Tue, 6 Aug 1996 09:28:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA13474; Tue, 6 Aug 1996 09:25:27 -0700 From: Terry Lambert Message-Id: <199608061625.JAA13474@phaeton.artisoft.com> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Tue, 6 Aug 1996 09:25:27 -0700 (MST) Cc: terry@lambert.org, freebsd-current@freebsd.org In-Reply-To: from "Developer" at Aug 6, 96 04:29:37 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 > > There was at least a beta version (their code, plus our patches) up for > > FTP on their site for FreeBSD. I believe that the changes have been > > sufficiently radical in -current that the code needs some work, but > > it was running Windows apps sufficiently to run MSWord on the 386 > > emulator under FreeBSD, and Sujal was working on some stack problems > > for running using the native processor in protected mode... > > Thanks very much for the information - do you know the address of the ftp > site that I might be able to get the freebsd version of xwin from? You should contact the mail address on the http://www.willows.com page; I'm not sure of their requirements for download. I believe you have to register, even if you don't have to pay anything. 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 Aug 6 09:31:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28246 for current-outgoing; Tue, 6 Aug 1996 09:31:02 -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 JAA28241 for ; Tue, 6 Aug 1996 09:31:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA13485; Tue, 6 Aug 1996 09:27:43 -0700 From: Terry Lambert Message-Id: <199608061627.JAA13485@phaeton.artisoft.com> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Tue, 6 Aug 1996 09:27:43 -0700 (MST) Cc: terry@lambert.org, freebsd-current@freebsd.org In-Reply-To: from "Developer" at Aug 6, 96 04:42:13 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 > Ive just tried to run the linux version of the willows windows emulator > (xwin) and run into an error:- [ ... ] > FatalAppExit: DPMI failure [ ... ] > Has anyone any idea why this might be? DOS Protected Mode Interface failure. It means that the VM86() call failed in the Linux emulator. This is probably understandable, since it has never been implemented. The patches for the BSD version of a DPMI for the BSD version of Willows is available as part of the BSD Willows distribution. You will have to use that instead. 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 Aug 6 10:21:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01308 for current-outgoing; Tue, 6 Aug 1996 10:21:16 -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 KAA01303 for ; Tue, 6 Aug 1996 10:21:14 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id MAA23320; Tue, 6 Aug 1996 12:21:12 -0500 Date: Tue, 6 Aug 1996 12:21:12 -0500 From: Jim Lowe Message-Id: <199608061721.MAA23320@miller.cs.uwm.edu> To: freebsd-current@freebsd.org, wangel@wgrobez1.remote.louisville.edu Subject: Re: locking up Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: Gary Roberts > To: freebsd-current@freebsd.org > Subject: locking up > > Sometimes, at no predetermined time, without warning, when switching VC's, > I'll lock up. FreeBSD doesn't lockup just the keyboard, and I can only fix > it by rebooting. > A while ago Bruce Evans had posted this, if you run it, it unlocks the keyboard. I don't know why this happens or why it hasn't been fixed. The way I run it is to remote login from some other machine. -Jim > Date: Tue, 20 Feb 1996 23:52:48 +1100 > From: Bruce Evans > Message-Id: <199602201252.XAA23329@godzilla.zeta.org.au> > To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de > Subject: Re: Keyboard lockout on 2.x.x > > To fix it if you can log in as root from another host, try > > echo "set ipending=2" | gdb -k -w /kernel /dev/mem > > This fakes a keyboard interrupt. > > Bruce > From owner-freebsd-current Tue Aug 6 10:46:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03250 for current-outgoing; Tue, 6 Aug 1996 10:46:15 -0700 (PDT) Received: from walkabout.asstdc.com.au (imb@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03239 for ; Tue, 6 Aug 1996 10:46:03 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id DAA07819 for current@freebsd.org; Wed, 7 Aug 1996 03:45:46 +1000 (EST) From: michael butler Message-Id: <199608061745.DAA07819@walkabout.asstdc.com.au> Subject: 3c589b troubles To: current@freebsd.org Date: Wed, 7 Aug 1996 03:45:44 +1000 (EST) X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (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 I'm continuing to have the 'link ok' light on my hub go out and the machine itself goes "deaf". This is with -current as of August 7th on an IBM ThinkPad 560 (16 meg). I can reliably prompt this behaviour by running "scp somehost:somelargefile ." where the "somelargefile" happens to be my last source-tree backup (about 33 megs of it). It'll fail inside the first 5 :-( "ifconfig ep0 up" is enough to restart the interface, michael From owner-freebsd-current Tue Aug 6 11:39:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA07905 for current-outgoing; Tue, 6 Aug 1996 11:39:40 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA07900 for ; Tue, 6 Aug 1996 11:39:38 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA28410; Tue, 6 Aug 1996 12:39:27 -0600 (MDT) Date: Tue, 6 Aug 1996 12:39:27 -0600 (MDT) Message-Id: <199608061839.MAA28410@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: current@freebsd.org Subject: Re: 3c589b troubles In-Reply-To: <199608061745.DAA07819@walkabout.asstdc.com.au> References: <199608061745.DAA07819@walkabout.asstdc.com.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk michael butler writes: > I'm continuing to have the 'link ok' light on my hub go out and the machine > itself goes "deaf". This is with -current as of August 7th on an IBM ThinkPad > 560 (16 meg). > > I can reliably prompt this behaviour by running "scp somehost:somelargefile > ." where the "somelargefile" happens to be my last source-tree backup (about > 33 megs of it). It'll fail inside the first 5 :-( > > "ifconfig ep0 up" is enough to restart the interface, This was a 'bug' that got introduced by the following commit: revision 1.50 date: 1996/07/13 10:49:53; author: davidg; state: Exp; lines: +2 -2 Enable transmit complete interrupt... .. But was fixed with this commit, made on the 7th. revision 1.52 date: 1996/07/27 12:40:31; author: amurai; state: Exp; lines: +2 -2 Under the heavy load for transmiting condition, it will be write error and then never accept for sending packet from upper layer anymore (i.e. ping -f ) Reviewed by: David Greenman Submitted by: amurai@spec.co.jp So, try getting your sources again and it should be fixed. Nate From owner-freebsd-current Tue Aug 6 11:50:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08935 for current-outgoing; Tue, 6 Aug 1996 11:50:12 -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 LAA08927 for ; Tue, 6 Aug 1996 11:50:10 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA13716; Tue, 6 Aug 1996 11:45:32 -0700 From: Terry Lambert Message-Id: <199608061845.LAA13716@phaeton.artisoft.com> Subject: Re: CD-R compatiblities To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 6 Aug 1996 11:45:32 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG, eischen@vigrid.com In-Reply-To: <199608060627.IAA08889@uriah.heep.sax.de> from "J Wunsch" at Aug 6, 96 08:27:29 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 mere problem is to convince Yamaha to get you their SCSI > documentation. Last time i've checked, they required me to fax them a > sheet with figures about ``expected sales next year'' and other crap. Expected sales impact: With documentation: 0 Without documentation: -100 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 Aug 6 11:54:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA09273 for current-outgoing; Tue, 6 Aug 1996 11:54:40 -0700 (PDT) Received: from walkabout.asstdc.com.au (imb@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA09257 for ; Tue, 6 Aug 1996 11:54:34 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id EAA07642 Wed, 7 Aug 1996 04:54:12 +1000 (EST) From: michael butler Message-Id: <199608061854.EAA07642@walkabout.asstdc.com.au> Subject: Re: 3c589b troubles To: nate@mt.sri.com (Nate Williams) Date: Wed, 7 Aug 1996 04:54:11 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199608061839.MAA28410@rocky.mt.sri.com> from Nate Williams at "Aug 6, 96 12:39:27 pm" X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (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 > But was fixed with this commit, made on the 7th. > revision 1.52 > date: 1996/07/27 12:40:31; author: amurai; state: Exp; lines: +2 -2 > Under the heavy load for transmiting condition, it will be write error > and then never accept for sending packet from upper layer anymore > So, try getting your sources again and it should be fixed. Nope .. the version I'm running (presuming we are talking about /sys/i386/isa/if_ep.c) .. * $Id: if_ep.c,v 1.52 1996/07/27 12:40:31 amurai Exp $ I should add that the failures are only observed under heavy _receive_ conditions or when promiscuous mode is enabled on a reasonably busy ether. It restarts OK as soon as you drop out of trafshow. Transmit is OK as far as I can test, michael From owner-freebsd-current Tue Aug 6 12:32:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA14403 for current-outgoing; Tue, 6 Aug 1996 12:32:30 -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 MAA14398 for ; Tue, 6 Aug 1996 12:32:25 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA16470; Wed, 7 Aug 1996 05:19:33 +1000 Date: Wed, 7 Aug 1996 05:19:33 +1000 From: Bruce Evans Message-Id: <199608061919.FAA16470@godzilla.zeta.org.au> To: freebsd-current@freefall.freebsd.org, kuku@gilberto.physik.rwth-aachen.de Subject: Re: time calibration messages - to worry about? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm getting these kernel messages during boot: >Jul 27 16:00:14 isdn /kernel: Calibrating clock(s) relative to mc146818 >A clock... >Jul 27 16:00:14 isdn /kernel: i8254 clock: 1217043 Hz >Jul 27 16:00:14 isdn /kernel: 1217043 Hz differs from default of 119318 >2 Hz by more than 1% This means that one of your clocks, or the clock calibration method, is inaccurate by more than 1% (15 minutes/day). Bruce From owner-freebsd-current Tue Aug 6 12:37:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA14743 for current-outgoing; Tue, 6 Aug 1996 12:37:07 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA14728 for ; Tue, 6 Aug 1996 12:37:03 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA28624; Tue, 6 Aug 1996 13:36:47 -0600 (MDT) Date: Tue, 6 Aug 1996 13:36:47 -0600 (MDT) Message-Id: <199608061936.NAA28624@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: 3c589b troubles In-Reply-To: <199608061854.EAA07642@walkabout.asstdc.com.au> References: <199608061839.MAA28410@rocky.mt.sri.com> <199608061854.EAA07642@walkabout.asstdc.com.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > revision 1.52 > > date: 1996/07/27 12:40:31; author: amurai; state: Exp; lines: +2 -2 > > Under the heavy load for transmiting condition, it will be write error > > and then never accept for sending packet from upper layer anymore > > > So, try getting your sources again and it should be fixed. > > Nope .. the version I'm running (presuming we are talking about > /sys/i386/isa/if_ep.c) .. Yep. > * $Id: if_ep.c,v 1.52 1996/07/27 12:40:31 amurai Exp $ *sigh* I don't know then. It may be the 'infamous' crappy driver we have, but I doubt anything new made it worse than it was before, or is it worse now than it used to be? Nate From owner-freebsd-current Tue Aug 6 14:13:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25726 for current-outgoing; Tue, 6 Aug 1996 14:13:08 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25714 for ; Tue, 6 Aug 1996 14:13:04 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id QAA00352 for current@freebsd.org; Tue, 6 Aug 1996 16:12:56 -0500 (CDT) Message-Id: <199608062112.QAA00352@utgard.bga.com> Subject: /etc/daily bogon with NIS To: current@freebsd.org Date: Tue, 6 Aug 1996 16:12:56 -0459 (CDT) From: "Boyd R. Faulkner" X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had an interesting call this morning. Apparently, my FreeBSD work box which is connected to the intranet with NIS and AMD mounts has been runing calendar -a and sending out calendar messages for the entire site. Someone finally complained. It would be better if this option were not the default, at least not in the case where NIS is being used. We turned it off. Thanks, Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Tue Aug 6 14:32:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28382 for current-outgoing; Tue, 6 Aug 1996 14:32:25 -0700 (PDT) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28371 for ; Tue, 6 Aug 1996 14:32:20 -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 XAA29574; Tue, 6 Aug 1996 23:31:39 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id XAA03094; Tue, 6 Aug 1996 23:31:08 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id XAA17603; Tue, 6 Aug 1996 23:15:47 +0200 (MET DST) Message-Id: <199608062115.XAA17603@keltia.freenix.fr> Date: Tue, 6 Aug 1996 23:15:47 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: amir@neuron.net (Amir Y. Rosenblatt) Cc: current@freebsd.org Subject: Re: How much space for CVS tree? In-Reply-To: <199608051857.OAA15675@prozac.neuron.net>; from Amir Y. Rosenblatt on Aug 5, 1996 14:57:37 -0400 References: <199608051857.OAA15675@prozac.neuron.net> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Amir Y. Rosenblatt: > I've been tracking -current for a few months now (pretty much since the > demise of 2.1-stable) and would like to start tracking the full CVS tree > as well. How much space should I allocate for the CVS tree? Here a df on my partition with both /usr/src and /usr/src/secure CVS trees (secure from South Africa of course). Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd12g 279647 239719 17557 93% /spare Hmmm, it's getting crowded here... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Tue Aug 6 17:44:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA18653 for current-outgoing; Tue, 6 Aug 1996 17:44:58 -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 RAA18642 for ; Tue, 6 Aug 1996 17:44:54 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA18980; Wed, 7 Aug 1996 10:26:06 +0930 From: Michael Smith Message-Id: <199608070056.KAA18980@genesis.atrad.adelaide.edu.au> Subject: Re: Linux Willows? To: terry@lambert.org (Terry Lambert) Date: Wed, 7 Aug 1996 10:26:06 +0930 (CST) Cc: dev@fgate.flevel.co.uk, terry@lambert.org, freebsd-current@FreeBSD.org In-Reply-To: <199608061625.JAA13474@phaeton.artisoft.com> from "Terry Lambert" at Aug 6, 96 09:25:27 am 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 Terry Lambert stands accused of saying: > > > > Thanks very much for the information - do you know the address of the ftp > > site that I might be able to get the freebsd version of xwin from? There isn't one. _Please_ also note that the TWIN XPDK is _NOT_ a windows emulator. It is a cross-development platform for porting Windows applications to Unices. > You should contact the mail address on the http://www.willows.com page; > I'm not sure of their requirements for download. I believe you have to > register, even if you don't have to pay anything. This is correct. The original poster should look at http:/www.willows.com/ and read about what TWIN is and more importantly is not. > Terry Lambert -- ]] 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 Tue Aug 6 18:58:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22257 for current-outgoing; Tue, 6 Aug 1996 18:58:55 -0700 (PDT) Received: (from grog@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22243; Tue, 6 Aug 1996 18:58:53 -0700 (PDT) From: Greg Lehey Message-Id: <199608070158.SAA22243@freefall.freebsd.org> Subject: Re: Linux Willows? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 6 Aug 1996 18:58:52 -0700 (PDT) Cc: current In-Reply-To: <199608070056.KAA18980@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 7, 96 10:26:06 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Terry Lambert stands accused of saying: > > > > > > Thanks very much for the information - do you know the address of the ftp > > > site that I might be able to get the freebsd version of xwin from? > > There isn't one. _Please_ also note that the TWIN XPDK is _NOT_ a > windows emulator. It is a cross-development platform for porting > Windows applications to Unices. Well, part of it emulates Windoze, specifically the xwin program. > > You should contact the mail address on the http://www.willows.com page; > > I'm not sure of their requirements for download. I believe you have to > > register, even if you don't have to pay anything. > > This is correct. The original poster should look at http:/www.willows.com/ > and read about what TWIN is and more importantly is not. Willows are trying to position twin as a cross-development platform, but I see it as being equally important as a Windoze emulator. Recent mail on the mailing list suggests that they're gradually realizing that too. Greg From owner-freebsd-current Tue Aug 6 19:24:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA23467 for current-outgoing; Tue, 6 Aug 1996 19:24:37 -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 TAA23462; Tue, 6 Aug 1996 19:24:31 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA19277; Wed, 7 Aug 1996 12:07:10 +0930 From: Michael Smith Message-Id: <199608070237.MAA19277@genesis.atrad.adelaide.edu.au> Subject: Re: Linux Willows? To: grog@freefall.freebsd.org (Greg Lehey) Date: Wed, 7 Aug 1996 12:07:09 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@freefall.freebsd.org In-Reply-To: <199608070158.SAA22243@freefall.freebsd.org> from "Greg Lehey" at Aug 6, 96 06:58:52 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 Greg Lehey stands accused of saying: > > > > There isn't one. _Please_ also note that the TWIN XPDK is _NOT_ a > > windows emulator. It is a cross-development platform for porting > > Windows applications to Unices. > > Well, part of it emulates Windoze, specifically the xwin program. Correct. You'll note that it's a development tool though, not a Windows emulator. > Willows are trying to position twin as a cross-development platform, > but I see it as being equally important as a Windoze emulator. Recent > mail on the mailing list suggests that they're gradually realizing > that too. Err, I'm on that list too; last I heard on the topic was Rod agreeing vehemently with me that trying to be a Windows emulator was pointless, and enumerating just exactly why from his point of view. > Greg -- ]] 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 Tue Aug 6 19:50:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA25826 for current-outgoing; Tue, 6 Aug 1996 19:50:59 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA25820 for ; Tue, 6 Aug 1996 19:50:47 -0700 (PDT) Received: from fakir.india.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA254646237; Tue, 6 Aug 1996 19:50:41 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA276586370; Wed, 7 Aug 1996 08:22:50 +0530 Message-Id: <199608070252.AA276586370@fakir.india.hp.com> To: "Michael L. VanLoon -- HeadCandy.com" Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Patch to recognize AMD 5x86 cpus In-Reply-To: Your message of "Tue, 06 Aug 1996 08:47:33 MST." <199608061547.IAA18751@MindBender.HeadCandy.com> Date: Wed, 07 Aug 1996 08:22:49 +0530 From: A JOSEPH KOSHY Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> ""Michael L. VanLoon -- HeadCandy.com"" writes > > >As Michael L. VanLoon -- HeadCandy.com wrote: > >> If you wanted to do this The "Correct" Way, you might be better off > >> rewriting the CPU identification code in locore.s to a more general, > > > identcpu.c > >(It has been divorced from locore.s some time ago.) > > Is it modular, well abstracted, comprehensive and all encompassing? I Well from my (possibly inadequate) understanding, we now have a new instruction `CPUID', which returns information about the CPU in the register. Sub-functions are requested using a sub-function code specified in %eax. In order to detect if the CPUID instruction exists, the documented approach is to check the writability of a bit in EFLAGS. If the instruction exists, we call it with %eax = 0 and 1 to extract the standard information about the chip. >From this point the CPU implementations are allowed to diverge. AMD for example, specifies that their K5 series of chips return more information about internal organization etc when %eax = 0x80000000-0x80000005. Other vendors support different subfunction codes. The code in -current retrieves the `basic' CPUID information in locore.s and updates some globals. identcpu.c then looks at this information to determine the exact type/model of CPU and takes the appropriate action specific to the chip. To the best of my understanding, the -current code confirms to the `standard' intel recommended processor identification method and my code confirms to AMD's published processor identification procedure. For more information you could look at intels processor recognition app-note in the developers corner of their web-site. AMD's documents on this are similarly available on the web. Koshy My Personal Opinions Only From owner-freebsd-current Tue Aug 6 21:10:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04095 for current-outgoing; Tue, 6 Aug 1996 21:10:34 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04071 for ; Tue, 6 Aug 1996 21:10:26 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id WAA13076 for ; Tue, 6 Aug 1996 22:10:23 -0600 (MDT) Message-Id: <199608070410.WAA13076@rover.village.org> To: current@freebsd.org Subject: socks? Date: Tue, 06 Aug 1996 22:10:22 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a socks5 port for freebsd-current? I thought I saw talk about one going into the tree or in as a port, yet I can't find it now. Have I missed something? Warner From owner-freebsd-current Tue Aug 6 21:52:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA09835 for current-outgoing; Tue, 6 Aug 1996 21:52:49 -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 VAA09826 for ; Tue, 6 Aug 1996 21:52:40 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA19884; Wed, 7 Aug 1996 14:35:06 +0930 From: Michael Smith Message-Id: <199608070505.OAA19884@genesis.atrad.adelaide.edu.au> Subject: Re: question about grinding system (Linux guru attn. reqd) To: nate@mt.sri.com (Nate Williams) Date: Wed, 7 Aug 1996 14:35:05 +0930 (CST) Cc: Gary.Jennejohn@munich.netsurf.de, msmith@atrad.adelaide.edu.au, freebsd-current@freebsd.org In-Reply-To: <199608052100.PAA23721@rocky.mt.sri.com> from "Nate Williams" at Aug 5, 96 03:00:05 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 Nate Williams stands accused of saying: > > >I went looking for M_TEMP allocations in i386/linux, and I'd like someone > > >who's better qualified than I to look over the exit conditions in > > >linux_emul_find() in linux_util.c because I'm fairly sure that it's > > >possible for this function to return without freeing its buffer, > > >and this would lead to the sort of leak that I'm seeing. > > > sure looks like the places where a "goto done" happens fail to free the > > buffer. > > I concur. And, if you look at the sources from the NetBSD OS emulation > code in /sys/compat/common/compat_util.c, it's even more apparent. The I managed to get the new code in yesterday evening, and I'm happy to report that the leak appears to have been plugged : 6:48AM up 19:04, 4 users, load averages: 0.51, 0.42, 0.47 ... Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) namei 0 0K 8K 19661K 6200524 0 0 1K VM object 707 89K 104K 19661K 7346037 0 0 128 file 81 6K 8K 19661K 1206620 0 0 64 temp 260 221K 431K 19661K 39226630 0 0 16,32,64,128,256,512,1K,2K,8K I included a couple of the other types above just for comparison's sake; that class is really getting a pounding 8) (Note that the load average is down because some of the bacground stuff is also leaking and was killed off a little while back, it's normally a little over 1) Thanks for the patch, Nate. -- ]] 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 Tue Aug 6 22:09:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11799 for current-outgoing; Tue, 6 Aug 1996 22:09:37 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA11788; Tue, 6 Aug 1996 22:09:34 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA00307; Tue, 6 Aug 1996 23:09:31 -0600 (MDT) Date: Tue, 6 Aug 1996 23:09:31 -0600 (MDT) Message-Id: <199608070509.XAA00307@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org CC: peter@freebsd.org Subject: Whither gcc 2.7? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk GCC 2.7 doesn't seem to be happening anytime soon, so is there any reason Peter can't update our sources to 2.7.2, and then we can get the x86 patches and apply them locally until 2.7.2.1 or whatever is released? It would be nice to get the new compiler in the tree so folks can start fixing all the bugs/warnings it now shows us, and the longer we wait on it the less time we'll have to do it. I understand a developer could install it on their local box, but it would be nicer to have a long shakeout time with the new compiler. Nate From owner-freebsd-current Tue Aug 6 22:12:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12286 for current-outgoing; Tue, 6 Aug 1996 22:12:39 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12271 for ; Tue, 6 Aug 1996 22:12:34 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id XAA24059 for ; Tue, 6 Aug 1996 23:12:32 -0600 (MDT) Message-Id: <199608070512.XAA24059@rover.village.org> Subject: Re: socks? To: current@FreeBSD.org In-reply-to: Your message of Tue, 06 Aug 1996 22:10:22 MDT Date: Tue, 06 Aug 1996 23:12:32 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : Is there a socks5 port for freebsd-current? Never mind. I've found it with the help of Chris Layne. Warner From owner-freebsd-current Wed Aug 7 01:34:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25054 for current-outgoing; Wed, 7 Aug 1996 01:34:40 -0700 (PDT) Received: from walkabout.asstdc.com.au (imb@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25045 for ; Wed, 7 Aug 1996 01:34:35 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id SAA00217 for current@freebsd.org; Wed, 7 Aug 1996 18:34:25 +1000 (EST) From: michael butler Message-Id: <199608070834.SAA00217@walkabout.asstdc.com.au> Subject: multi-block transfers To: current@freebsd.org Date: Wed, 7 Aug 1996 18:34:24 +1000 (EST) X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (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 Between versions 1.110 and 1.113 the multi-block transfer mode was changed with IDE controllers .. On my ThinkPad (the only machine I have with IDE :-)), I used to get .. wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 775MB (1587600 sectors), 1575 cyls, 16 heads, 63 S/T, 512 B/S .. now, I get .. wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa wdc0: unit 0 (wd0): , 32-bit wd0: 775MB (1587600 sectors), 1575 cyls, 16 heads, 63 S/T, 512 B/S .. is it now broken ? michael From owner-freebsd-current Wed Aug 7 01:47:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25899 for current-outgoing; Wed, 7 Aug 1996 01:47:03 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-147.ut.nl.ibm.net [139.92.42.147]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25861; Wed, 7 Aug 1996 01:46:19 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id PAA12398; Mon, 5 Aug 1996 15:58:36 +0200 (MET DST) Message-Id: <199608051358.PAA12398@vector.jhs.no_domain> To: "Jordan K. Hubbard" cc: roberto@keltia.freenix.fr (Ollivier Robert), ernie@spooky.eis.net.au (Ernie Elu), freebsd-current@FreeBSD.org Subject: Re: Sup failing for sup.freebsd.org From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Sat, 03 Aug 1996 21:44:35 PDT." <29831.839133875@time.cdrom.com> Date: Mon, 05 Aug 1996 15:58:35 +0200 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: "Jordan K. Hubbard" > Subject: Re: Sup failing for sup.freebsd.org > Date: Sat, 03 Aug 1996 21:44:35 -0700 > Message-id: <29831.839133875@time.cdrom.com> > > > One way to possibly solve this is not to use SUP but try RSYNC. Instead of > > just looking at the file's date, it looks at the file itself and only send > > the diffs. It may be more relieable than SUP. I don't know about the load > > on the server though. > > Or use cvsup. > > Jordan ? man cvsup No manual entry for cvsup apropos cvsup cvsup: nothing appropriate cd /usr/ports/*/cvsup */cvsup: No match. Personally I use ctm, (available for src/ ports/ cvs/ & gnats ) I used to use sup, but ctm saves pain, I reckon credit for that goes to the md5 checksums (& credit for ctm to Poul-Henning). Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Aug 7 02:00:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA26848 for current-outgoing; Wed, 7 Aug 1996 02:00:32 -0700 (PDT) Received: from walkabout.asstdc.com.au (imb@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA26822 for ; Wed, 7 Aug 1996 02:00:25 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id TAA00513 for current@freebsd.org; Wed, 7 Aug 1996 19:00:20 +1000 (EST) From: michael butler Message-Id: <199608070900.TAA00513@walkabout.asstdc.com.au> Subject: patch for consideration .. multi-block IDE To: current@freebsd.org Date: Wed, 7 Aug 1996 19:00:18 +1000 (EST) X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (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 I noted that multi-block transfers had been broken .. the following patch corrects the problem (a line missed in the rearrange, I suspect) .. *** /sys/i386/isa/wd.c.orig Sun Jul 28 06:52:04 1996 --- /sys/i386/isa/wd.c Wed Aug 7 18:59:08 1996 *************** *** 1665,1670 **** --- 1665,1671 ---- du->dk_dd.d_type = DTYPE_ESDI; du->dk_dd.d_subtype |= DSTYPE_GEOMETRY; #endif + du->dk_multi = wp->wdp_nsecperint & 0xff; return (0); } From owner-freebsd-current Wed Aug 7 02:04:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27113 for current-outgoing; Wed, 7 Aug 1996 02:04:09 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27086 for ; Wed, 7 Aug 1996 02:03:59 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id KAA03640; Wed, 7 Aug 1996 10:07:54 +0100 (BST) Date: Wed, 7 Aug 1996 10:07:53 +0100 (BST) From: Developer To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: Linux Willows? In-Reply-To: <199608061627.JAA13485@phaeton.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, 6 Aug 1996, Terry Lambert wrote: > > Ive just tried to run the linux version of the willows windows emulator > > (xwin) and run into an error:- > > [ ... ] > > > FatalAppExit: DPMI failure > > [ ... ] > > > Has anyone any idea why this might be? > > DOS Protected Mode Interface failure. It means that the VM86() call > failed in the Linux emulator. This is probably understandable, since > it has never been implemented. The patches for the BSD version of a How hard would this be to implement? Is anyone working on this one? > DPMI for the BSD version of Willows is available as part of the BSD > Willows distribution. You will have to use that instead. Ah, I understand.. Ive emailed Willows regarding this - do I get the freebsd patches from them? Regards, Trefor S. From owner-freebsd-current Wed Aug 7 03:09:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA01283 for current-outgoing; Wed, 7 Aug 1996 03:09:02 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA01277 for ; Wed, 7 Aug 1996 03:08:51 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA12354; Wed, 7 Aug 1996 12:03:56 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA13085; Wed, 7 Aug 1996 12:16:34 +0200 From: "Christoph P. Kukulies" Message-Id: <199608071016.MAA13085@gilberto.physik.rwth-aachen.de> Subject: Re: time calibration messages - to worry about? To: bde@zeta.org.au (Bruce Evans) Date: Wed, 7 Aug 1996 12:16:33 +0200 (MET DST) Cc: freebsd-current@freefall.freebsd.org, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199608061919.FAA16470@godzilla.zeta.org.au> from Bruce Evans at "Aug 7, 96 05:19:33 am" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (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 > >I'm getting these kernel messages during boot: > > >Jul 27 16:00:14 isdn /kernel: Calibrating clock(s) relative to mc146818 > >A clock... > >Jul 27 16:00:14 isdn /kernel: i8254 clock: 1217043 Hz > >Jul 27 16:00:14 isdn /kernel: 1217043 Hz differs from default of 119318 > >2 Hz by more than 1% > > This means that one of your clocks, or the clock calibration method, is > inaccurate by more than 1% (15 minutes/day). Fine, but why? :-) > > Bruce > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Aug 7 03:47:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA03841 for current-outgoing; Wed, 7 Aug 1996 03:47:44 -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 DAA03832 for ; Wed, 7 Aug 1996 03:47:37 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA16929; Wed, 7 Aug 1996 20:44:34 +1000 Date: Wed, 7 Aug 1996 20:44:34 +1000 From: Bruce Evans Message-Id: <199608071044.UAA16929@godzilla.zeta.org.au> To: bde@zeta.org.au, kuku@gilberto.physik.rwth-aachen.de Subject: Re: time calibration messages - to worry about? Cc: freebsd-current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >Jul 27 16:00:14 isdn /kernel: i8254 clock: 1217043 Hz >> >Jul 27 16:00:14 isdn /kernel: 1217043 Hz differs from default of 119318 >> >2 Hz by more than 1% >> >> This means that one of your clocks, or the clock calibration method, is >> inaccurate by more than 1% (15 minutes/day). >Fine, but why? :-) Don't know. Local space-time warps? :-) Bruce From owner-freebsd-current Wed Aug 7 03:54:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA04056 for current-outgoing; Wed, 7 Aug 1996 03:54:40 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA04051 for ; Wed, 7 Aug 1996 03:54:36 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id LAA20489; Wed, 7 Aug 1996 11:58:44 +0100 (BST) Date: Wed, 7 Aug 1996 11:58:43 +0100 (BST) From: Developer To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: Linux Willows? In-Reply-To: <199608061627.JAA13485@phaeton.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, 6 Aug 1996, Terry Lambert wrote: > > Ive just tried to run the linux version of the willows windows emulator > > (xwin) and run into an error:- > > [ ... ] > > > FatalAppExit: DPMI failure > > [ ... ] > > > Has anyone any idea why this might be? > > DOS Protected Mode Interface failure. It means that the VM86() call > failed in the Linux emulator. This is probably understandable, since > it has never been implemented. The patches for the BSD version of a > DPMI for the BSD version of Willows is available as part of the BSD > Willows distribution. You will have to use that instead. I just found some more information, in /var/log/messages I have:- Linux-emul(18075): modify_ldt() not supported Seems like the linux ldt`s doesn`t work - is this easy to fix? Regards, Trefor S. From owner-freebsd-current Wed Aug 7 03:57:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA04164 for current-outgoing; Wed, 7 Aug 1996 03:57: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 DAA04159 for ; Wed, 7 Aug 1996 03:57:48 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA17094; Wed, 7 Aug 1996 20:51:07 +1000 Date: Wed, 7 Aug 1996 20:51:07 +1000 From: Bruce Evans Message-Id: <199608071051.UAA17094@godzilla.zeta.org.au> To: current@FreeBSD.ORG, imb@asstdc.com.au Subject: Re: multi-block transfers Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > .. now, I get .. >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa >wdc0: unit 0 (wd0): , 32-bit >wd0: 775MB (1587600 sectors), 1575 cyls, 16 heads, 63 S/T, 512 B/S > .. is it now broken ? du->dk_multi is now used in the probe before it is set. Bruce From owner-freebsd-current Wed Aug 7 04:02:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA04502 for current-outgoing; Wed, 7 Aug 1996 04:02:58 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA04489 for ; Wed, 7 Aug 1996 04:02:46 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.7.5/8.7.3) with ESMTP id TAA11374; Wed, 7 Aug 1996 19:02:31 +0800 (WST) Message-Id: <199608071102.TAA11374@spinner.DIALix.COM> X-Mailer: exmh version 1.6.6 3/24/96 To: Nate Williams cc: current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Tue, 06 Aug 1996 23:09:31 CST." <199608070509.XAA00307@rocky.mt.sri.com> Date: Wed, 07 Aug 1996 19:02:31 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > GCC 2.7 doesn't seem to be happening anytime soon, so is there any > reason Peter can't update our sources to 2.7.2, and then we can get the > x86 patches and apply them locally until 2.7.2.1 or whatever is > released? Probably the better question would be: "Whither Peter Wemm?" :-/ A couple of things have been happening here that have drastically impacted on the time I've been spending on FreeBSD lately... My family still has the Flu for starters (it's going onto the 8th week or so now :-( ), and something terrible has happened at work... (like, I've actually been having quite good *fun* on my paying job. I've been spending a lot of extra time on that.) The gcc-2.7.[23]{.X} code has kinda been on hold as I was told that 2.7.3 (or now 2.7.2.1 as I hear it's going to be called) was going to be released "real soon now, probably next week" way back when I first put the suggestion on the table. I've not heard anything fo a few weeks from guy that was supposed to be keeping me up to date on the gcc-2.7.x happenings, and the most recent patch that he could get me was from June-6. When I read over the patch, there were no x86 fixes.. It was mostly risc system definition stuff and a real fix for the -fstrength-reduce bug. Neither of which were all that useful as we currently dont suffer from the -fstrength-reduce/-O2 bug (a small part of the optimization is disabled on our version(s)). The later snapshots of the 2.7.whatever would probably be worth using, but that one seems hardly worth the effort. So, I'm pretty tempted to just give up and do 2.7.2 and update it to 2.7.3/2.7.2.1/whatever when it's finally ready. There were some other interesting suggestions too. One user stongly hinted that he'd like me to use the src/contrib mechanism, this is not out of the question. I had kinda promised to the CTM users that I wasn't going to make a huge delta when I imported gcc-2.7.2, but it seems that the src/contrib system has been reasonably well accepted by most parties, so perhaps I should consider doing that.. This does have merits, as I could actually use John Polstra's elfkit patches to allow an elf version to be built as well. It makes no real difference to me time-wise as to which form is imported, as I have both versions (bmake style and "native" style) working and in sync here already, under P3's multiple-view control. Also, out of interest, it would not be difficult to have a real gcc-style build using a driver makefile under src/gnu/usr.bin/cc, including obj dir support, running configure --srcdir=... and so on. Perhaps it should be done that way anyway, as it would be trivial to have both compilers in the system for a limited time, and allow people to easily opt to use the old one if there's a major problem for them. Thoughts? Is it worth abandoning the plans to do do a bmake import this late in the game and switch to src/contrib (minus the non-x86 arch stuff).. The more I think about it, the more I'm changing my mind and coming to the opinion that we can do a lot more with it if the parts that we need go into src/contrib with the bmake build points in the correct part of the tree as usual. I have other things on the agenda: - libncurses - cvs - libz (cvs now uses it) > It would be nice to get the new compiler in the tree so folks can start > fixing all the bugs/warnings it now shows us, and the longer we wait on > it the less time we'll have to do it. > > I understand a developer could install it on their local box, but it > would be nicer to have a long shakeout time with the new compiler. > > Nate There is a snapshot of the bmake'd version on freefall somewhere, but I think it's a little old. I'll build a new one and put it somewhere that everybody can get to for the time being. Cheers, -Peter From owner-freebsd-current Wed Aug 7 04:17:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA05702 for current-outgoing; Wed, 7 Aug 1996 04:17:24 -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 EAA05697 for ; Wed, 7 Aug 1996 04:17:16 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id VAA17880; Wed, 7 Aug 1996 21:15:43 +1000 Date: Wed, 7 Aug 1996 21:15:43 +1000 From: Bruce Evans Message-Id: <199608071115.VAA17880@godzilla.zeta.org.au> To: current@FreeBSD.ORG, imb@asstdc.com.au Subject: Re: patch for consideration .. multi-block IDE Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I noted that multi-block transfers had been broken .. the following patch >corrects the problem (a line missed in the rearrange, I suspect) .. >*** /sys/i386/isa/wd.c.orig Sun Jul 28 06:52:04 1996 >--- /sys/i386/isa/wd.c Wed Aug 7 18:59:08 1996 >*************** >*** 1665,1670 **** >--- 1665,1671 ---- > du->dk_dd.d_type = DTYPE_ESDI; > du->dk_dd.d_subtype |= DSTYPE_GEOMETRY; > #endif >+ du->dk_multi = wp->wdp_nsecperint & 0xff; > > return (0); > } This is wrong too. du->dk_multi is actually the number of sectors transferred per interrupt (not a multi-mode flag or count) and should be set to 1 unless multi-mode will actually be used, i.e., unless 1) The drive claims to support it, i.e., the above du->dk_multi > 1. 2) It is configured, i.e., (du->cfg_flags & WDOPT_MULTIMASK) > 1. 3) The configured count is <= the supported count. This restriction probably shouldn't exist (use min(configured, supported)). 4) Issuing of the command to program multi-mode succeeds. 5) The command to program multi-mode succeeds. Currently, the exit status of the command is thrown away. It is inconvenient to do all this at probe time. Bruce From owner-freebsd-current Wed Aug 7 04:36:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA06917 for current-outgoing; Wed, 7 Aug 1996 04:36:33 -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 EAA06906 for ; Wed, 7 Aug 1996 04:36:30 -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 EAA10359; Wed, 7 Aug 1996 04:36:02 -0700 (PDT) To: Peter Wemm cc: Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 19:02:31 +0800." <199608071102.TAA11374@spinner.DIALix.COM> Date: Wed, 07 Aug 1996 04:36:01 -0700 Message-ID: <10357.839417761@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The more I think about it, the more I'm changing my mind and coming to the > opinion that we can do a lot more with it if the parts that we need go > into src/contrib with the bmake build points in the correct part of the > tree as usual. And I believe that's even the politically correct method these days, too! :-) One gripe somebody had with Poul's TCL import was that he didn't also check in the script, be it ever so simple, that "created" the importable sources. NetBSD does this, a good example being in freefall:/c/NetBSD/NetBSD-current/src/gnu/usr.bin/gcc/gcc2netbsd, and I figure we should too. > I have other things on the agenda: > - libncurses Yay! I'd like to hack on the panel code until it's more usable, myself, but it's still waiting on whomever said they had libncurses last (thought it was Andrey). Weren't we also going to replace curses with it, as BSDI and NetBSD both agreed to do? > - cvs It'd be nice if we could get the read-only repository changes with this. I think anoncvs is worth making available, for one thing. Jordan From owner-freebsd-current Wed Aug 7 04:43:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA07259 for current-outgoing; Wed, 7 Aug 1996 04:43:16 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA07239 for ; Wed, 7 Aug 1996 04:43:10 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id NAA18814; Wed, 7 Aug 1996 13:41:34 +0200 Message-Id: <199608071141.NAA18814@ra.dkuug.dk> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Wed, 7 Aug 1996 13:41:33 +0200 (MET DST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: from "Developer" at Aug 7, 96 11:58:43 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Developer who wrote: > > > > Ive just tried to run the linux version of the willows windows emulator > > > (xwin) and run into an error:- > > > > [ ... ] > > > > > FatalAppExit: DPMI failure > > > > [ ... ] > > > > > Has anyone any idea why this might be? > > > > DOS Protected Mode Interface failure. It means that the VM86() call > > failed in the Linux emulator. This is probably understandable, since > > it has never been implemented. The patches for the BSD version of a > > DPMI for the BSD version of Willows is available as part of the BSD > > Willows distribution. You will have to use that instead. > > I just found some more information, in /var/log/messages I have:- > > Linux-emul(18075): modify_ldt() not supported > > Seems like the linux ldt`s doesn`t work - is this easy to fix? No. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Aug 7 04:59:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08940 for current-outgoing; Wed, 7 Aug 1996 04:59:10 -0700 (PDT) Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA08931 for ; Wed, 7 Aug 1996 04:59:04 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id TAA27507 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 19:58:59 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 7 Aug 1996 11:58:58 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <4ua0e2$p3n$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199608040322.MAA06694@genesis.atrad.adelaide.edu.au> Subject: Re: problem with -current system grinding to a halt... Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199608040744.AAA13305@root.com>, dg@Root.COM (David Greenman) writes: > > This can happen if your nameserver isn't reachable. Have you tried "w -n" ? > This disables the nameserver lookups and is useful for this specific problem. > > -DG Not any more.. Now it causes an extra DNS lookup if the ut_host field isn't a numeric IP address... :-( Sigh. -Peter > David Greenman > Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Aug 7 05:03:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA09421 for current-outgoing; Wed, 7 Aug 1996 05:03:46 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA09402; Wed, 7 Aug 1996 05:03:41 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id NAA06694; Wed, 7 Aug 1996 13:57:33 +0200 (MET DST) To: Peter Wemm cc: Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 19:02:31 +0800." <199608071102.TAA11374@spinner.DIALix.COM> Date: Wed, 07 Aug 1996 13:57:32 +0200 Message-ID: <6692.839419052@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Thoughts? Is it worth abandoning the plans to do do a bmake import this >late in the game and switch to src/contrib (minus the non-x86 arch stuff).. Yes, src/contrib! >I have other things on the agenda: > - libncurses > - cvs > - libz (cvs now uses it) - smp ! :-) -- 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 Aug 7 05:59:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15587 for current-outgoing; Wed, 7 Aug 1996 05:59:41 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA15555 for ; Wed, 7 Aug 1996 05:59:24 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id OAA02175; Wed, 7 Aug 1996 14:57:56 +0200 (SAT) Message-Id: <199608071257.OAA02175@grumble.grondar.za> To: Peter Wemm cc: Nate Williams , current@FreeBSD.ORG Subject: Re: Whither gcc 2.7? Date: Wed, 07 Aug 1996 14:57:56 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Peter Wemm wrote: > A couple of things have been happening here that have drastically impacted > on the time I've been spending on FreeBSD lately... My family still has > the Flu for starters (it's going onto the 8th week or so now :-( ), and > something terrible has happened at work... (like, I've actually been > having quite good *fun* on my paying job. I've been spending a lot of > extra time on that.) Ah yes, the bane of FreeBSD development - a fun job! > So, I'm pretty tempted to just give up and do 2.7.2 and update it to > 2.7.3/2.7.2.1/whatever when it's finally ready. Please do that! > This does have merits, as I > could actually use John Polstra's elfkit patches to allow an elf version > to be built as well. > > It makes no real difference to me time-wise as to which form is imported, > as I have both versions (bmake style and "native" style) working and in > sync here already, under P3's multiple-view control. > > Also, out of interest, it would not be difficult to have a real gcc-style > build using a driver makefile under src/gnu/usr.bin/cc, including obj dir > support, running configure --srcdir=... and so on. > > Perhaps it should be done that way anyway, as it would be trivial to have > both compilers in the system for a limited time, and allow people to > easily opt to use the old one if there's a major problem for them. This make far too much sense _not_ to be used. The src/contrib system is nice. Please use that. > The more I think about it, the more I'm changing my mind and coming to the > opinion that we can do a lot more with it if the parts that we need go > into src/contrib with the bmake build points in the correct part of the > tree as usual. Win, Win, Win. > I have other things on the agenda: > - libncurses > - cvs > - libz (cvs now uses it) Win, Win, Win. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Aug 7 06:05:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16433 for current-outgoing; Wed, 7 Aug 1996 06:05:00 -0700 (PDT) Received: from filitov.isf.rl.af.mil (FILITOV.ISF.RL.AF.MIL [128.132.64.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16408; Wed, 7 Aug 1996 06:04:48 -0700 (PDT) Received: (from green@localhost) by filitov.isf.rl.af.mil (8.7.3/8.7.3) id JAA04106; Wed, 7 Aug 1996 09:04:27 -0400 (EDT) Message-Id: <199608071304.JAA04106@filitov.isf.rl.af.mil> From: green@filitov.isf.rl.af.mil (Charles Green) Date: Wed, 7 Aug 1996 09:04:26 +1000 X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: hackers@freebsd.org, current@freebsd.org Subject: Willows support for freebsd Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk With all the talk about willows on the mailing lists I thought I'd post a letter from willows I recieved from them last week. (I had permission to post the letter) "Laurent Gharda" stands accused of saying: } Hello Charles, } } Thanks for your interest in the 32-bit Willows Toolkit (formerly known } as TWIN APIW)! We just posted beta versions of Linux and Solaris, with } Mac and the other UNIX versions coming soon. } } And no, there is no FreeBSD version planned available right now. } } HOWEVER, a significant amount of work went into it in the past (with the } 16 bit version), which means that we could introduce a 32-bit version } cross-platform toolkit (no xwin emulator for now) with a few more weeks } of work. } } We have now gone to a commercial model (we charge for our products and } services, since no one paid us for our products before) and can no } longer expend engineering resources unless there is a return on our } investment. I am sure you appreciate the problem! } } The Willows Toolkit for UNIX (includes source for the libraries for 9 } different UNIX platforms) costs $4,995 per named developer (with sharp } quantity discounts) + 20% per year for support. } } Not only is this price much lower than the other commercial } alternatives, but we charge no royalties (others charge from $75 to $100 } per shipped copy of the application you build), we provide the source to } the libraries and we have a Macintosh version (so we're much more of a } true cross-platform solution, we're not just UNIX). } } We could very well introduce a FreeBSD version within weeks if we had } just 3 or 4 orders (to cover our costs). If you feel the availability } of a cross-platform toolkit would make a difference toward a broader } acceptance of FreeBSD, can you help drum up interest in it so we can } justify finishing the work (and yes, it's OK to post this on the mailing } lists)? } } We would very much like to introduce such a version, but we need help! } } I look forward to hearing from you, Charles! } } Best regards, } } Laurent } } -- } } } Laurent Gharda Tel: (408) 777-1825 } Willows Software Fax: (408) 777-1827 } 12950 Saratoga Avenue, Suite A e-mail: laurent@willows.com } Saratoga, CA 95070 URL: www.willows.com }-- End of excerpt from "Laurent Gharda" -- Charles Green, PRC, Inc. Rome Laboratory, NY From owner-freebsd-current Wed Aug 7 06:57:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA22735 for current-outgoing; Wed, 7 Aug 1996 06:57:27 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA22722 for ; Wed, 7 Aug 1996 06:57:22 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id PAA01818 for ; Wed, 7 Aug 1996 15:00:42 +0100 (BST) Date: Wed, 7 Aug 1996 15:00:41 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Re: Linux Willows? In-Reply-To: <9608071245.AA12992@cssmuc.frt.dec.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 I`m trying to use the linux version of the development kit on freebsd to see how it runs, Ive found that the link libraries are linux version.. so I need to use the linux gcc/ld and produce linux executables - unless someone knows how to convert linux library to freebsd? The problem I`m having now is ld can`t find crt1.o and crti.o .. any ideas where to get these from - I have crt0.o but I guess that isn`t the same thing.. Cheers, Trefor S. From owner-freebsd-current Wed Aug 7 07:09:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA24264 for current-outgoing; Wed, 7 Aug 1996 07:09: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 HAA24255 for ; Wed, 7 Aug 1996 07:09:15 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA17055; Wed, 7 Aug 1996 10:09:02 -0400 Date: Wed, 7 Aug 1996 10:09:02 -0400 From: Garrett Wollman Message-Id: <9608071409.AA17055@halloran-eldar.lcs.mit.edu> To: "Boyd R. Faulkner" Cc: current@FreeBSD.org Subject: /etc/daily bogon with NIS In-Reply-To: <199608062112.QAA00352@utgard.bga.com> References: <199608062112.QAA00352@utgard.bga.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > It would be better if this option were not the default, at least not in the > case where NIS is being used. I have believed for some time that this function ought to be completely removed from `calendar'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Wed Aug 7 07:52:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00710 for current-outgoing; Wed, 7 Aug 1996 07:52:59 -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 HAA00697 for ; Wed, 7 Aug 1996 07:52:53 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA03444; Wed, 7 Aug 1996 09:52:13 -0500 (EST) From: John Dyson Message-Id: <199608071452.JAA03444@dyson.iquest.net> Subject: Re: multi-block transfers To: bde@zeta.org.au (Bruce Evans) Date: Wed, 7 Aug 1996 09:52:13 -0500 (EST) Cc: current@FreeBSD.ORG, imb@asstdc.com.au In-Reply-To: <199608071051.UAA17094@godzilla.zeta.org.au> from "Bruce Evans" at Aug 7, 96 08:51:07 pm Reply-To: dyson@FreeBSD.ORG 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 > > > .. now, I get .. > > >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa > >wdc0: unit 0 (wd0): , 32-bit > >wd0: 775MB (1587600 sectors), 1575 cyls, 16 heads, 63 S/T, 512 B/S > > > .. is it now broken ? > > du->dk_multi is now used in the probe before it is set. > I think that I broke it. PHK has been reminding me of the problem, but my net connectivity has been spotty. Hope to clean up my messes this weekend. John From owner-freebsd-current Wed Aug 7 08:06:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02909 for current-outgoing; Wed, 7 Aug 1996 08:06:25 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02873; Wed, 7 Aug 1996 08:06:20 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id OAA06736; Wed, 7 Aug 1996 14:05:25 +0200 (MET DST) To: "Jordan K. Hubbard" cc: Peter Wemm , Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 04:36:01 PDT." <10357.839417761@time.cdrom.com> Date: Wed, 07 Aug 1996 14:05:25 +0200 Message-ID: <6734.839419525@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <10357.839417761@time.cdrom.com>, "Jordan K. Hubbard" writes: >> The more I think about it, the more I'm changing my mind and coming to the >> opinion that we can do a lot more with it if the parts that we need go >> into src/contrib with the bmake build points in the correct part of the >> tree as usual. > >And I believe that's even the politically correct method these days, >too! :-) One gripe somebody had with Poul's TCL import was that he >didn't also check in the script, be it ever so simple, that "created" >the importable sources. NetBSD does this, a good example being in >freefall:/c/NetBSD/NetBSD-current/src/gnu/usr.bin/gcc/gcc2netbsd, and >I figure we should too. Hey a "gripe" ? I saw it as a very good suggestion :-) -- 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 Aug 7 09:01:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10233 for current-outgoing; Wed, 7 Aug 1996 09:01:18 -0700 (PDT) Received: from localhost.my.domain (root@morrison-c13.aa.net [204.157.220.145]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10222 for ; Wed, 7 Aug 1996 09:01:13 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by localhost.my.domain (8.7.5/8.6.12) with SMTP id JAA00705; Wed, 7 Aug 1996 09:00:34 -0700 (PDT) Date: Wed, 7 Aug 1996 09:00:33 -0700 (PDT) From: Sujal Patel X-Sender: smpatel@localhost To: Charles Green cc: current@FreeBSD.org Subject: Re: Willows support for freebsd In-Reply-To: <199608071304.JAA04106@filitov.isf.rl.af.mil> 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, 7 Aug 1996, Charles Green wrote: > } HOWEVER, a significant amount of work went into it in the past (with the > } 16 bit version), which means that we could introduce a 32-bit version > } cross-platform toolkit (no xwin emulator for now) with a few more weeks > } of work. AFAIK, the port should of everything (including xwin) should not be very difficult for their programmers. It seems to me that support for FreeBSD just isn't on their agenda. Anyone want to take a crack at getting the Linux version working on -current? I don't think it will be easy, but it should be possible. Sujal From owner-freebsd-current Wed Aug 7 09:02:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10342 for current-outgoing; Wed, 7 Aug 1996 09:02:04 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA10335 for ; Wed, 7 Aug 1996 09:02:00 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA05628; Wed, 7 Aug 1996 09:01:34 -0700 From: "Rodney W. Grimes" Message-Id: <199608071601.JAA05628@GndRsh.aac.dev.com> Subject: Re: Whither gcc 2.7? To: peter@spinner.DIALix.COM (Peter Wemm) Date: Wed, 7 Aug 1996 09:01:34 -0700 (PDT) Cc: nate@mt.sri.com, current@freebsd.org In-Reply-To: <199608071102.TAA11374@spinner.DIALix.COM> from Peter Wemm at "Aug 7, 96 07:02:31 pm" 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 ... > Thoughts? Is it worth abandoning the plans to do do a bmake import this > late in the game and switch to src/contrib (minus the non-x86 arch stuff).. Yes, it is worth it, but don't drop the non-x86 arch stuff, as then a few of us out here can play with makeing this work in a cross platform, otherhost, etc type of environment without a lot of hassle. > The more I think about it, the more I'm changing my mind and coming to the > opinion that we can do a lot more with it if the parts that we need go > into src/contrib with the bmake build points in the correct part of the > tree as usual. Remeber, what goes into src/contrib should be the _complete_ sources, with _no_ changes at all, otherwise we might as well go back to what we have been doing. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Aug 7 09:53:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA17391 for current-outgoing; Wed, 7 Aug 1996 09:53:07 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA17375; Wed, 7 Aug 1996 09:53:02 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id SAA07096; Wed, 7 Aug 1996 18:50:46 +0200 (MET DST) To: "Rodney W. Grimes" cc: peter@spinner.DIALix.COM (Peter Wemm), nate@mt.sri.com, current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 09:01:34 PDT." <199608071601.JAA05628@GndRsh.aac.dev.com> Date: Wed, 07 Aug 1996 18:50:46 +0200 Message-ID: <7094.839436646@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199608071601.JAA05628@GndRsh.aac.dev.com>, "Rodney W. Grimes" write s: >Remeber, what goes into src/contrib should be the _complete_ sources, with >_no_ changes at all, otherwise we might as well go back to what we have >been doing. no. I disagree here. It is legal and required to remove stuff that qualifies as "bloat". The gcc support for any cpu but i386 qualifies for that. -- 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 Aug 7 09:58:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18146 for current-outgoing; Wed, 7 Aug 1996 09:58:26 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA18134; Wed, 7 Aug 1996 09:58:21 -0700 (PDT) Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <16448(5)>; Wed, 7 Aug 1996 09:57:22 PDT Received: from gnu.mc.xerox.com (gnu.sdsp.mc.xerox.com) by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1-TB) id AA23151; Wed, 7 Aug 96 12:57:31 EDT Received: by gnu.mc.xerox.com (4.1/SMI-4.1) id AA22903; Wed, 7 Aug 96 12:57:30 EDT Message-Id: <9608071657.AA22903@gnu.mc.xerox.com> X-Mailer: exmh version 1.6.7 5/3/96 To: Nate Williams Cc: current@freebsd.org, peter@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: Your message of "Tue, 06 Aug 1996 22:09:31 PDT." <199608070509.XAA00307@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 7 Aug 1996 09:57:28 PDT From: "Marty Leisner" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm somewhat confused... I've compiled hoards of stuff with gcc 2.7.2 (no shared libraries) and haven't seen a problem... I'm also interested in getting some commonality with binutils so I can do cross-development work and the native commands have the write feel. -- marty leisner@sdsp.mc.xerox.com Member of the League for Programming Freedom From owner-freebsd-current Wed Aug 7 09:59:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18285 for current-outgoing; Wed, 7 Aug 1996 09:59:10 -0700 (PDT) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [193.100.176.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA18269; Wed, 7 Aug 1996 09:59:06 -0700 (PDT) Received: by mail.ruhrgebiet.individual.net (8.7.1/8.6.12) with UUCP id RAA26680; Wed, 7 Aug 1996 17:52:16 +0200 (MET DST) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Wed, 7 Aug 96 17:48 MET DST Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: Sup failing for sup.freebsd.org To: jhs@freebsd.org Date: Wed, 7 Aug 1996 17:48:34 +0200 (MET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <199608051358.PAA12398@vector.jhs.no_domain> from "Julian H. Stacey" at Aug 5, 96 03:58:35 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Personally I use ctm, (available for src/ ports/ cvs/ & gnats ) > I used to use sup, but ctm saves pain, I reckon credit for that goes to > the md5 checksums (& credit for ctm to Poul-Henning). > > Julian > -- > Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ > Is it possible to find a sync point to go to ctm from sup? Or do I have to download the 30MB A-ctm file from freefall? sup is a pain with slow internet connections. Robert From owner-freebsd-current Wed Aug 7 10:11:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA19976 for current-outgoing; Wed, 7 Aug 1996 10:11:14 -0700 (PDT) Received: from nervosa.vendetta.com (coredump@nervosa.vendetta.com [192.187.167.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA19969 for ; Wed, 7 Aug 1996 10:11:12 -0700 (PDT) Received: from localhost (coredump@localhost) by nervosa.vendetta.com (8.7.5/8.7.3) with SMTP id KAA07443; Wed, 7 Aug 1996 10:09:56 -0700 (PDT) Date: Wed, 7 Aug 1996 10:09:55 -0700 (PDT) From: Chris Layne To: Peter Wemm cc: Nate Williams , current@Freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <199608071102.TAA11374@spinner.DIALix.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 Wed, 7 Aug 1996, Peter Wemm wrote: > having quite good *fun* on my paying job. I've been spending a lot of > extra time on that.) Heh. What kinda fun? ;) > So, I'm pretty tempted to just give up and do 2.7.2 and update it to > 2.7.3/2.7.2.1/whatever when it's finally ready. I would wait a little longer just incase. > I have other things on the agenda: > - libncurses Yes, finally, it's up to 1.9.9 now. Also, is it just me, or does the format of coordinates (y, x) ncurses requires seem just a little nonstandard? I thought in math and everything else, coordinates were expected in (x, y) form? > Cheers, > -Peter == Chris Layne ======================================== Nervosa Computing == == coredump@nervosa.vendetta.com == http://nervosa.vendetta.com/~coredump == From owner-freebsd-current Wed Aug 7 10:28:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22746 for current-outgoing; Wed, 7 Aug 1996 10:28:08 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22724 for ; Wed, 7 Aug 1996 10:28:02 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA01936; Wed, 7 Aug 1996 11:27:53 -0600 (MDT) Date: Wed, 7 Aug 1996 11:27:53 -0600 (MDT) Message-Id: <199608071727.LAA01936@rocky.mt.sri.com> From: Nate Williams To: Poul-Henning Kamp Cc: "Rodney W. Grimes" , peter@spinner.dialix.com (Peter Wemm), nate@mt.sri.com, current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <7094.839436646@critter.tfs.com> References: <199608071601.JAA05628@GndRsh.aac.dev.com> <7094.839436646@critter.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > In message <199608071601.JAA05628@GndRsh.aac.dev.com>, "Rodney W. Grimes" write > s: > >Remeber, what goes into src/contrib should be the _complete_ sources, with > >_no_ changes at all, otherwise we might as well go back to what we have > >been doing. > > no. I disagree here. It is legal and required to remove stuff that > qualifies as "bloat". I agree with both of you, although I will state that the reason the 'ports' tree doesn't work as well as the current 'Bmake' paradigm is because of the above problem. By using a subset of the tree, you are still requiring that the importer 'hack' the sources to fit into our tree, otherwise the size involved becomes so great as to make it necessary to unbundle the compiler. And, you have to 'build' the converted Makefile, which is at least as difficult as doing the BMake makefile. The arguements put forth about 'not sending changes' back are specious. If it was important to send the FreeBSD changes back to the FSF they could be done 'trivially'. Almost all of the changes merged in after an import are FreeBSD specific, since we don't import the Makefiles as part of the import. Also, the FSF tend to re-organize their directory structures on major releases, which will cause a huge amount of grief in the CVS repository and lots of work for the importer, so I still don't see a benefit. I still fail to see the advantage of building things in /src/contrib, but I've given up arguing since it does not good. *None* of the reasons brought up against the current Bmake setup were in any way valid, but since we've got a big hammer all the world looks like a nail. 'Ports is successful, so everything should be in the ports paradigm that isn't supplied by CSRG'. *sigh* In any case, if we bring in gcc, bringing in the *entire* distribution would be a big mistake IMHO. The usefulness of other parts is minimal at best, and the cost is spectacularly large in terms of disk space. Heck, the entire gcc 2.7.2 distribution is bigger than bin, include, libexec, sbin, and usr.bin combined. :( > The gcc support for any cpu but i386 qualifies for that. If we move over to the new setup, we should be careful not to make the same mistakes we did before and ship sources that we can generate (yacc/lex) instead of generating them. This was a problem in the last version that I should have fixed in my subsequent updates, but I was too lazy. :( The only subdir tree larger than *just* the gcc 2.7 sources is the GNU tree, which includes gcc 2.6.3. Nate From owner-freebsd-current Wed Aug 7 10:32:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23461 for current-outgoing; Wed, 7 Aug 1996 10:32:45 -0700 (PDT) Received: from fullfeed.msn.fullfeed.com (fullfeed.msn.fullfeed.com [199.184.182.42]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA23443 for ; Wed, 7 Aug 1996 10:32:38 -0700 (PDT) Received: from sumatra.americantv.com by fullfeed.msn.fullfeed.com (8.6.9/FF-1.1) id MAA22946; Wed, 7 Aug 1996 12:32:19 -0500 Received: (from uucp@localhost) by sumatra.americantv.com (8.6.12/8.6.12) with UUCP id MAA03249 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 12:03:48 -0500 Received: (jlemon@localhost) by right.PCS (8.6.12/8.6.4) id MAA00250 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 12:29:56 -0500 From: Jonathan Lemon Message-Id: <199608071729.MAA00250@right.PCS> Subject: Re: locking up To: freebsd-current@freebsd.org Date: Wed, 7 Aug 1996 12:29:55 -0500 (CDT) In-Reply-To: <199608061721.MAA23320@miller.cs.uwm.edu> from "Jim Lowe" at Aug 6, 96 12:21:12 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Sometimes, at no predetermined time, without warning, when switching VC's, > > I'll lock up. FreeBSD doesn't lockup just the keyboard, and I can only fix > > it by rebooting. > > A while ago Bruce Evans had posted this, if you run it, it > unlocks the keyboard. I don't know why this happens or why > it hasn't been fixed. The way I run it is to remote login > from some other machine. > > echo "set ipending=2" | gdb -k -w /kernel /dev/mem I have the same problem - I'm running 2.1.0R CD distribution, and at random times during an X session, the keyboard just freezes up. Executing 'kbd_mode' doesn't fix the problem either. Logging in remotely and killing the X server clears up the difficulty though, or executing the above commandline. -- Jonathan From owner-freebsd-current Wed Aug 7 11:13:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26260 for current-outgoing; Wed, 7 Aug 1996 11:13:12 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA26252 for ; Wed, 7 Aug 1996 11:13:09 -0700 (PDT) Received: from thurston.eng.umd.edu (thurston.eng.umd.edu [129.2.103.25]) by po1.glue.umd.edu (8.7.5/8.7.3) with ESMTP id OAA02981; Wed, 7 Aug 1996 14:13:06 -0400 (EDT) Received: from localhost (chuckr@localhost) by thurston.eng.umd.edu (8.7.5/8.7.3) with SMTP id OAA11597; Wed, 7 Aug 1996 14:13:05 -0400 (EDT) X-Authentication-Warning: thurston.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 7 Aug 1996 14:13:05 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@thurston.eng.umd.edu To: Nate Williams cc: Poul-Henning Kamp , "Rodney W. Grimes" , Peter Wemm , current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <199608071727.LAA01936@rocky.mt.sri.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 Wed, 7 Aug 1996, Nate Williams wrote: > Poul-Henning Kamp writes: > > In message <199608071601.JAA05628@GndRsh.aac.dev.com>, "Rodney W. Grimes" write > > I still fail to see the advantage of building things in /src/contrib, > but I've given up arguing since it does not good. *None* of the reasons > brought up against the current Bmake setup were in any way valid, but > since we've got a big hammer all the world looks like a nail. 'Ports is > successful, so everything should be in the ports paradigm that isn't > supplied by CSRG'. *sigh* > > In any case, if we bring in gcc, bringing in the *entire* distribution > would be a big mistake IMHO. The usefulness of other parts is minimal > at best, and the cost is spectacularly large in terms of disk space. > Heck, the entire gcc 2.7.2 distribution is bigger than bin, include, > libexec, sbin, and usr.bin combined. :( I have to agree, on bringing in the whole thing. Some of us may need it, baut the size is enormous (comparatively and absolutely) and the number of us that would need it small. > > > The gcc support for any cpu but i386 qualifies for that. > > If we move over to the new setup, we should be careful not to make the > same mistakes we did before and ship sources that we can generate > (yacc/lex) instead of generating them. This was a problem in the last > version that I should have fixed in my subsequent updates, but I was too > lazy. :( > > The only subdir tree larger than *just* the gcc 2.7 sources is the GNU > tree, which includes gcc 2.6.3. > > > > Nate > ----------------------------+----------------------------------------------- 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 Wed Aug 7 11:21:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26739 for current-outgoing; Wed, 7 Aug 1996 11:21:56 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA26734 for ; Wed, 7 Aug 1996 11:21:54 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA32101; Wed, 7 Aug 1996 11:21:44 -0700 Date: Wed, 7 Aug 1996 11:21:44 -0700 (PDT) From: "Brian N. Handy" To: Nate Williams Cc: current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <199608071727.LAA01936@rocky.mt.sri.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 [trimmed up the cc: list a bit] On Wed, 7 Aug 1996, Nate Williams wrote: >[...] > >In any case, if we bring in gcc, bringing in the *entire* distribution >would be a big mistake IMHO. The usefulness of other parts is minimal >at best, and the cost is spectacularly large in terms of disk space. >Heck, the entire gcc 2.7.2 distribution is bigger than bin, include, >libexec, sbin, and usr.bin combined. :( I concur with Nate here. I surmise that only a handful of people want to fiddle with the other platform stuff. If it was *me* doing that I suspect I would be willing to go download my own bloat. (Though I'm not using this other stuff, so keep my reply in context.) I guess another thing I wonder about...has anyone thought about the future plans of tracking gcc? We've been running 2.6.3 for a loong time, are we going to move to 2.7.# and stay with it or is FreeBSD going to start tracking gcc more closely? Brian From owner-freebsd-current Wed Aug 7 11:50:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28706 for current-outgoing; Wed, 7 Aug 1996 11:50:18 -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 LAA28695; Wed, 7 Aug 1996 11:50:15 -0700 (PDT) Message-Id: <199608071850.LAA28695@freefall.freebsd.org> To: Nate Williams cc: Poul-Henning Kamp , "Rodney W. Grimes" , peter@spinner.dialix.com (Peter Wemm), current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 11:27:53 MDT." <199608071727.LAA01936@rocky.mt.sri.com> Date: Wed, 07 Aug 1996 11:50:14 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In any case, if we bring in gcc, bringing in the *entire* distribution >would be a big mistake IMHO. The usefulness of other parts is minimal >at best, and the cost is spectacularly large in terms of disk space. >Heck, the entire gcc 2.7.2 distribution is bigger than bin, include, >libexec, sbin, and usr.bin combined. :( Why not import the whole thing but only distribute the i386 code by default? We can easily setup additional CVSup targets for the non i386 portions of the compiler for people interested in cross compiling or working on a new port. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Aug 7 11:59:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29313 for current-outgoing; Wed, 7 Aug 1996 11:59:46 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA29304; Wed, 7 Aug 1996 11:59:40 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id UAA07381; Wed, 7 Aug 1996 20:59:18 +0200 (MET DST) To: "Justin T. Gibbs" cc: Nate Williams , "Rodney W. Grimes" , peter@spinner.dialix.com (Peter Wemm), current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 11:50:14 PDT." <199608071850.LAA28695@freefall.freebsd.org> Date: Wed, 07 Aug 1996 20:59:17 +0200 Message-ID: <7379.839444357@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199608071850.LAA28695@freefall.freebsd.org>, "Justin T. Gibbs" writ es: >>In any case, if we bring in gcc, bringing in the *entire* distribution >>would be a big mistake IMHO. The usefulness of other parts is minimal >>at best, and the cost is spectacularly large in terms of disk space. >>Heck, the entire gcc 2.7.2 distribution is bigger than bin, include, >>libexec, sbin, and usr.bin combined. :( > >Why not import the whole thing but only distribute the i386 code by >default? We can easily setup additional CVSup targets for the non >i386 portions of the compiler for people interested in cross compiling >or working on a new port. Justin, Justin, this is earth, come in Justin, we have a negative on that trajectory-thingie... So what about sup, ftp & ctm ? -- 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 Aug 7 12:01:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29522 for current-outgoing; Wed, 7 Aug 1996 12:01:38 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA29513 for ; Wed, 7 Aug 1996 12:01:35 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA07406 for ; Wed, 7 Aug 1996 21:01:16 +0200 (MET DST) To: current@freebsd.org Subject: make world botch Reply-to: phk@freebsd.org Date: Wed, 07 Aug 1996 21:01:16 +0200 Message-ID: <7404.839444476@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "/usr/src/Makefile", line 150: if-less endif "/usr/src/Makefile", line 150: Need an operator Fatal errors encountered -- cannot continue -- 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 Aug 7 12:05:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29726 for current-outgoing; Wed, 7 Aug 1996 12:05:05 -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 MAA29718 for ; Wed, 7 Aug 1996 12:05:03 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA15504; Wed, 7 Aug 1996 12:00:46 -0700 From: Terry Lambert Message-Id: <199608071900.MAA15504@phaeton.artisoft.com> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Wed, 7 Aug 1996 12:00:46 -0700 (MST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: from "Developer" at Aug 7, 96 10:07:53 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 > > DPMI for the BSD version of Willows is available as part of the BSD > > Willows distribution. You will have to use that instead. > > Ah, I understand.. Ive emailed Willows regarding this - do I get the > freebsd patches from them? Yes. They also maintain a BSD porting mailing list. You will need to contact Willows directly for access to either of them. 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 Wed Aug 7 12:08:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29927 for current-outgoing; Wed, 7 Aug 1996 12:08:01 -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 MAA29910 for ; Wed, 7 Aug 1996 12:07:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA15524; Wed, 7 Aug 1996 12:04:18 -0700 From: Terry Lambert Message-Id: <199608071904.MAA15524@phaeton.artisoft.com> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Wed, 7 Aug 1996 12:04:18 -0700 (MST) Cc: terry@lambert.org, freebsd-current@freebsd.org In-Reply-To: from "Developer" at Aug 7, 96 11:58:43 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 just found some more information, in /var/log/messages I have:- > > Linux-emul(18075): modify_ldt() not supported > > Seems like the linux ldt`s doesn`t work - is this easy to fix? Not without making it necessary to rewrite the VM system for each new platform you port to. It requires very Intel-specific hooks in the VM. 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 Wed Aug 7 12:12:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00391 for current-outgoing; Wed, 7 Aug 1996 12:12:35 -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 MAA00385; Wed, 7 Aug 1996 12:12:32 -0700 (PDT) Message-Id: <199608071912.MAA00385@freefall.freebsd.org> To: Poul-Henning Kamp cc: Nate Williams , "Rodney W. Grimes" , peter@spinner.dialix.com (Peter Wemm), current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 20:59:17 +0200." <7379.839444357@critter.tfs.com> Date: Wed, 07 Aug 1996 12:12:31 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Justin, Justin, this is earth, come in Justin, we have a negative >on that trajectory-thingie... > >So what about sup, ftp & ctm ? Sup collections are exactly the same as CVSup collections, but I'm expecting Sup to go away as soon as we have a CVSup port in the tree. As for ftp, are there a lot of people using this method for geting the sources? Perhaps an i386 file list would be sufficient??? Having never used CTM, I have no idea whats involved with making it exclude files. Any way you slice it, we'll have to deal with this issue as soon as we start supporting more than one arch. In fact, as Nate pointed out, the PC98 stuff has already made this a problem we need to solve. >-- >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. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Aug 7 12:21:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00831 for current-outgoing; Wed, 7 Aug 1996 12:21:04 -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 ESMTP id MAA00826 for ; Wed, 7 Aug 1996 12:21:03 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id MAA01384 for ; Wed, 7 Aug 1996 12:21:01 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA02626; Wed, 7 Aug 1996 13:16:22 -0600 (MDT) Date: Wed, 7 Aug 1996 13:16:22 -0600 (MDT) Message-Id: <199608071916.NAA02626@rocky.mt.sri.com> From: Nate Williams To: "Justin T. Gibbs" Cc: Poul-Henning Kamp , Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <199608071912.MAA00385@freefall.freebsd.org> References: <7379.839444357@critter.tfs.com> <199608071912.MAA00385@freefall.freebsd.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > >Justin, Justin, this is earth, come in Justin, we have a negative > >on that trajectory-thingie... > > > >So what about sup, ftp & ctm ? > > Sup collections are exactly the same as CVSup collections, but I'm > expecting Sup to go away as soon as we have a CVSup port in the tree. I *really* want to keep SUP around until the next major release, just to make sure CVSup gets shaken out better. No offense to John, but I trust SUP and although CVSup is great and all, I still do a SUP once/week to 'make sure' everything is hunky-dorey. Nate From owner-freebsd-current Wed Aug 7 12:21:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00939 for current-outgoing; Wed, 7 Aug 1996 12:21:52 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00927; Wed, 7 Aug 1996 12:21:47 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id NAA03022; Wed, 7 Aug 1996 13:20:49 -0600 (MDT) Message-Id: <199608071920.NAA03022@rover.village.org> To: Nate Williams Subject: Re: Whither gcc 2.7? Cc: current@FreeBSD.org, peter@FreeBSD.org In-reply-to: Your message of Tue, 06 Aug 1996 23:09:31 MDT Date: Wed, 07 Aug 1996 13:20:48 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : GCC 2.7 doesn't seem to be happening anytime soon, so is there any : reason Peter can't update our sources to 2.7.2, and then we can get the : x86 patches and apply them locally until 2.7.2.1 or whatever is : released? I can get you the 2.7.2.1 patches before they are released, and today I can pass along patches that are within a gnat's whisker of the release. I've also been given permission to have the FreeBSD team put it in the source tree as well, so there is no bug-a-boo about that. Warner From owner-freebsd-current Wed Aug 7 12:29:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01444 for current-outgoing; Wed, 7 Aug 1996 12:29:01 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01425; Wed, 7 Aug 1996 12:28:53 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA02767; Wed, 7 Aug 1996 13:28:48 -0600 (MDT) Date: Wed, 7 Aug 1996 13:28:48 -0600 (MDT) Message-Id: <199608071928.NAA02767@rocky.mt.sri.com> From: Nate Williams To: phk@freebsd.org Cc: current@freebsd.org Subject: Re: make world botch In-Reply-To: <7404.839444476@critter.tfs.com> References: <7404.839444476@critter.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > "/usr/src/Makefile", line 150: if-less endif > "/usr/src/Makefile", line 150: Need an operator > Fatal errors encountered -- cannot continue Fixed, thanks for pointing it out! From owner-freebsd-current Wed Aug 7 12:37:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02105 for current-outgoing; Wed, 7 Aug 1996 12:37:00 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02095 for ; Wed, 7 Aug 1996 12:36:55 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id NAA03803 for ; Wed, 7 Aug 1996 13:36:53 -0600 (MDT) Message-Id: <199608071936.NAA03803@rover.village.org> To: current@FreeBSD.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of Wed, 07 Aug 1996 20:59:17 +0200 Date: Wed, 07 Aug 1996 13:36:52 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk du of config on my OpenBSD tree says it is 8229 blocks. That's with about 150 blocks of CVS directories. The config/i386 directory is 601 blocks in size. That's a savings of about 7M of sources, which is just under 3% of the source tree. As much as I'd *LOVE* to see all of that in the tree, I must admit that is starting to be large enough to be on the radar screens of people :-(. It sure is nice to be able to go to the OpenBSD tree and do a configure --target x-x-x, but I understand that it is of a more primary goal in that environment and is not a goal of FreeBSD. If it wasn't so central a part of the OS, I think it would be great if there was a "port" of gcc and not bother with including it in the core system. That would enable patches to propigate back to FSF more quickly, since they would have to be more contained. Sadly, this is not an option because you can't have an OS w/o a compiler, and gcc is currently the only compiler that is known to build all of FreeBSD. I've just seen the pain that we go through every time gcc is upgraded and would like to see the vendor supplied parts segragated out from the FreeBSD fixes. If that was the case, it would be easier to upgrade the compiler from rev to rev. I also wish FSF would get on the ball and release 2.7.2.1... They haven't done any additional work on it that I've seen in the mailing lists since we talked about this back in June... I'm not sure what to do here :-(. Warner From owner-freebsd-current Wed Aug 7 12:42:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02444 for current-outgoing; Wed, 7 Aug 1996 12:42:29 -0700 (PDT) Received: from shell.monmouth.com (pechter@shell.monmouth.com [205.164.220.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02439 for ; Wed, 7 Aug 1996 12:42:27 -0700 (PDT) Received: (from pechter@localhost) by shell.monmouth.com (8.7.4/8.7.3) id PAA09338 for FreeBSD-current@freebsd.org; Wed, 7 Aug 1996 15:39:07 -0400 (EDT) From: Bill/Carolyn Pechter Message-Id: <199608071939.PAA09338@shell.monmouth.com> Subject: make bootstrap problem To: FreeBSD-current@freebsd.org (FreeBSD-current) Date: Wed, 7 Aug 1996 15:39:07 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] 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 Anyone else ever see this on make bootstrap... (while building make . . .) Last.o lstMember.o lstNext.o lstOpen.o lstRemove.o lstReplace.o lstSucc.o install -c -s -o bin -g bin -m 555 make /usr/bin cd: can't cd to . *** Error code 2 Stop. *** Error code 1 Stop. --Bill ------------------------------------------------------------------------------- Bill Pechter/Carolyn Pechter | 17 Meredith Drive, Tinton Falls, NJ 07724, 908-389-3592 | pechter@shell.monmouth.com I'll run Win95 on my box when you pry the keyboard from my cold, dead hands. FreeBSD, OS/2, CP/M, RT11, spoken here. From owner-freebsd-current Wed Aug 7 12:43:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02518 for current-outgoing; Wed, 7 Aug 1996 12:43:12 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02513 for ; Wed, 7 Aug 1996 12:43:09 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA02426; Wed, 7 Aug 1996 12:54:08 -0600 (MDT) Date: Wed, 7 Aug 1996 12:54:08 -0600 (MDT) Message-Id: <199608071854.MAA02426@rocky.mt.sri.com> From: Nate Williams To: "Justin T. Gibbs" Cc: Nate Williams , Poul-Henning Kamp , "Rodney W. Grimes" , peter@spinner.dialix.com (Peter Wemm), current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <199608071850.LAA28695@freefall.freebsd.org> References: <199608071727.LAA01936@rocky.mt.sri.com> <199608071850.LAA28695@freefall.freebsd.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > >In any case, if we bring in gcc, bringing in the *entire* distribution > >would be a big mistake IMHO. The usefulness of other parts is minimal > >at best, and the cost is spectacularly large in terms of disk space. > >Heck, the entire gcc 2.7.2 distribution is bigger than bin, include, > >libexec, sbin, and usr.bin combined. :( > > Why not import the whole thing but only distribute the i386 code by > default? We can easily setup additional CVSup targets for the non > i386 portions of the compiler for people interested in cross compiling > or working on a new port. This is a workable solution, as long as all the distribution methods allow for it. (I'm still waiting to get a PC98 target distribution, which has the same complexity as what you just suggested.) Nate From owner-freebsd-current Wed Aug 7 12:45:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02725 for current-outgoing; Wed, 7 Aug 1996 12:45:26 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02710 for ; Wed, 7 Aug 1996 12:45:20 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id PAA01562; Wed, 7 Aug 1996 15:45:02 -0400 (EDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.3) with SMTP id PAA09727; Wed, 7 Aug 1996 15:45:17 -0400 (EDT) X-Authentication-Warning: ki.net: scrappy owned process doing -bs Date: Wed, 7 Aug 1996 15:45:16 -0400 (EDT) From: "Marc G. Fournier" To: "Jordan K. Hubbard" cc: Peter Wemm , Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <10357.839417761@time.cdrom.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 Wed, 7 Aug 1996, Jordan K. Hubbard wrote: > > Yay! I'd like to hack on the panel code until it's more usable, > myself, but it's still waiting on whomever said they had libncurses > last (thought it was Andrey). Weren't we also going to replace curses > with it, as BSDI and NetBSD both agreed to do? > Me, actually... the ideas was that since ncurses supported curses, termcap *and* mytinfo, it allowed us to replace it all with one, central library... Still waiting for Peter to import the 1.9.9e tree though, or to receive instructions on how to do it propoerly (my knowledge of cvs isn't strongnough *yet* to feel confident with just going in and doin git...) If someone wants to tell me how to import it properly, I'll spend thi scoming weekend bringing it in and getting it up to speed with the current patches... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Aug 7 12:53:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03365 for current-outgoing; Wed, 7 Aug 1996 12:53:14 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA03355; Wed, 7 Aug 1996 12:53:09 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA07506; Wed, 7 Aug 1996 21:52:47 +0200 (MET DST) To: "Justin T. Gibbs" cc: Nate Williams , "Rodney W. Grimes" , peter@spinner.dialix.com (Peter Wemm), current@freebsd.org Subject: Re: Whither gcc 2.7? In-reply-to: Your message of "Wed, 07 Aug 1996 12:12:31 PDT." <199608071912.MAA00385@freefall.freebsd.org> Date: Wed, 07 Aug 1996 21:52:46 +0200 Message-ID: <7504.839447566@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199608071912.MAA00385@freefall.freebsd.org>, "Justin T. Gibbs" writ >Any way you slice it, we'll have to deal with this issue as soon as we >start supporting more than one arch. In fact, as Nate pointed out, the >PC98 stuff has already made this a problem we need to solve. I still think that we need to sit down and think VERY carefully before we import >all< of gcc. I will be against it all the way. If people want to play with other archs, they can go pick up the original gcc sources, and extract the bits they need. -- 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 Aug 7 12:53:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03407 for current-outgoing; Wed, 7 Aug 1996 12:53:31 -0700 (PDT) Received: from tarpit.thrush.com (rd@tarpit.magicnet.net [206.104.206.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA03400 for ; Wed, 7 Aug 1996 12:53:26 -0700 (PDT) Received: (from rd@localhost) by tarpit.thrush.com (8.7.4/8.7.3) id PAA11197; Wed, 7 Aug 1996 15:53:23 -0400 (EDT) Date: Wed, 7 Aug 1996 15:53:23 -0400 (EDT) From: "R.D. Thrush" Message-Id: <199608071953.PAA11197@tarpit.thrush.com> To: freebsd-current@freebsd.org Subject: SCSI Multiple LUN support - 2.2-960801-SNAP Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 2.2-960801-SNAP is unable to recognize multiple LUNs on a wide scsi target connected to either a BusLogic 956C or an Adaptec 2940UW. Is there some additional kernel configuration required to enable detection of multiple LUNs? FWIW, on the same hardware, bsd/os 2.1 locates all 5 LUNs on the one target when connected to either of the above 2 adapters. From owner-freebsd-current Wed Aug 7 13:45:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07104 for current-outgoing; Wed, 7 Aug 1996 13:45:27 -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 NAA07091 for ; Wed, 7 Aug 1996 13:45:22 -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 WAA30605 for ; Wed, 7 Aug 1996 22:45:15 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id WAA16961 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 22:45:02 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id VAA21539; Wed, 7 Aug 1996 21:59:21 +0200 (MET DST) Message-Id: <199608071959.VAA21539@keltia.freenix.fr> Date: Wed, 7 Aug 1996 21:59:21 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Questions about the CVS and CTM In-Reply-To: <199608060323.VAA06564@rover.village.org>; from Warner Losh on Aug 5, 1996 21:23:55 -0600 References: <199608060323.VAA06564@rover.village.org> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Warner Losh: > cvs update won't grab new directories that appear from time to time. > You'll need to do cvs checkout src for that from time to time still. Use "cvs update -d -P" to get new directories and wipe out old ones. You can also use "~/.cvsrc" and put update -d -P -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Wed Aug 7 13:45:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07112 for current-outgoing; Wed, 7 Aug 1996 13:45:29 -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 NAA07089 for ; Wed, 7 Aug 1996 13:45:21 -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 WAA30609 for ; Wed, 7 Aug 1996 22:45:16 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id WAA16963 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 22:45:02 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id WAA21569; Wed, 7 Aug 1996 22:03:22 +0200 (MET DST) Message-Id: <199608072003.WAA21569@keltia.freenix.fr> Date: Wed, 7 Aug 1996 22:03:22 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Questions about the CVS and CTM In-Reply-To: <199608060523.XAA25666@rocky.mt.sri.com>; from Nate Williams on Aug 5, 1996 23:23:12 -0600 References: <199608060523.XAA25666@rocky.mt.sri.com> <199608060323.VAA06564@rover.village.org> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Nate Williams: > '-P', which causes it to remove directories that become emtpy as they > occur. Why this isn't the default behavior has been subject to much > discussion on the CVS mailing lists. :( Speaking of which, do you intent to import CVS 1.8.1 (whichever release is last, I use the snapshots myself...) ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Wed Aug 7 13:45:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07131 for current-outgoing; Wed, 7 Aug 1996 13:45:31 -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 NAA07103 for ; Wed, 7 Aug 1996 13:45:26 -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 WAA30603 for ; Wed, 7 Aug 1996 22:45:14 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id WAA16962 for current@freebsd.org; Wed, 7 Aug 1996 22:45:02 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id VAA21546; Wed, 7 Aug 1996 21:59:53 +0200 (MET DST) Message-Id: <199608071959.VAA21546@keltia.freenix.fr> Date: Wed, 7 Aug 1996 21:59:53 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: current@freebsd.org Subject: Re: How much space for CVS tree? In-Reply-To: <199608060328.VAA06597@rover.village.org>; from Warner Losh on Aug 5, 1996 21:28:54 -0600 References: <199608060328.VAA06597@rover.village.org> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Warner Losh: > The CVS tree is about 230M. The sources checked out are about 210M. > The obj tree escapes me at the moment, but either 100M or 150M sticks > in my head. About 93 MB now without profiled libs. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Wed Aug 7 13:46:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07276 for current-outgoing; Wed, 7 Aug 1996 13:46:07 -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 NAA07250 for ; Wed, 7 Aug 1996 13:45:59 -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 WAA30607 for ; Wed, 7 Aug 1996 22:45:15 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id WAA16960 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 22:45:02 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id VAA21532; Wed, 7 Aug 1996 21:57:50 +0200 (MET DST) Message-Id: <199608071957.VAA21532@keltia.freenix.fr> Date: Wed, 7 Aug 1996 21:57:50 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org Subject: Re: Questions about the CVS and CTM In-Reply-To: <199608052255.PAA12200@phaeton.artisoft.com>; from Terry Lambert on Aug 5, 1996 15:55:33 -0700 References: <199608052255.PAA12200@phaeton.artisoft.com> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Terry Lambert: > The idea of having the build process check out the most recent sources > (or a specific tag from an environment variable) and build, with a > remove-behind for after it's installed, would be a good idea. This is more or less what /usr/src/release/Makefile does, except the /usr/src is not removed. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Wed Aug 7 13:57:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08170 for current-outgoing; Wed, 7 Aug 1996 13:57:33 -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 NAA08165; Wed, 7 Aug 1996 13:57:31 -0700 (PDT) Message-Id: <199608072057.NAA08165@freefall.freebsd.org> To: "R.D. Thrush" cc: freebsd-current@freebsd.org Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP In-reply-to: Your message of "Wed, 07 Aug 1996 15:53:23 EDT." <199608071953.PAA11197@tarpit.thrush.com> Date: Wed, 07 Aug 1996 13:57:31 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 2.2-960801-SNAP is unable to recognize multiple LUNs on a wide scsi >target connected to either a BusLogic 956C or an Adaptec 2940UW. Is >there some additional kernel configuration required to enable >detection of multiple LUNs? > > FWIW, on the same hardware, bsd/os 2.1 locates all 5 LUNs on the one >target when connected to either of the above 2 adapters. You need to add a quirk for your device that says that it is a multi-lun device. The FreeBSD SCSI code defaults to *not* probing for additional luns, but the logic will be reversed as soon as I find the time to import the NetBSD quirk table entries for devices that can't handle multi-lun probing. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Aug 7 14:08:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08879 for current-outgoing; Wed, 7 Aug 1996 14:08:20 -0700 (PDT) Received: from DeepCore.dk (dial217.cybercity.dk [194.16.56.217]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA08829 for ; Wed, 7 Aug 1996 14:08:01 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.5/8.7.3) id XAA00469; Wed, 7 Aug 1996 23:05:47 +0200 (MET DST) Message-Id: <199608072105.XAA00469@DeepCore.dk> Subject: Re: Whither gcc 2.7? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Wed, 7 Aug 1996 23:05:47 +0200 (MET DST) Cc: gibbs@freefall.freebsd.org, nate@mt.sri.com, rgrimes@gndrsh.aac.dev.com, peter@spinner.dialix.com, current@FreeBSD.org In-Reply-To: <7504.839447566@critter.tfs.com> from Poul-Henning Kamp at "Aug 7, 96 09:52:46 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 Poul-Henning Kamp who wrote: > In message <199608071912.MAA00385@freefall.freebsd.org>, "Justin T. Gibbs" writ > > >Any way you slice it, we'll have to deal with this issue as soon as we > >start supporting more than one arch. In fact, as Nate pointed out, the > >PC98 stuff has already made this a problem we need to solve. > > I still think that we need to sit down and think VERY carefully before > we import >all< of gcc. > > I will be against it all the way. So, we should make a bmaked version, put it in the tree as usual, and let the original (and pgcc and xxgcc..) be in ports... No need for that contrib mess... My 0.02 Dkr. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- S鷨en Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Wed Aug 7 14:09:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09003 for current-outgoing; Wed, 7 Aug 1996 14:09:42 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA08997 for ; Wed, 7 Aug 1996 14:09:38 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA03370; Wed, 7 Aug 1996 15:09:17 -0600 (MDT) Date: Wed, 7 Aug 1996 15:09:17 -0600 (MDT) Message-Id: <199608072109.PAA03370@rocky.mt.sri.com> From: Nate Williams To: roberto@keltia.freenix.fr (Ollivier Robert) Cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Questions about the CVS and CTM In-Reply-To: <199608072003.WAA21569@keltia.freenix.fr> References: <199608060523.XAA25666@rocky.mt.sri.com> <199608060323.VAA06564@rover.village.org> <199608072003.WAA21569@keltia.freenix.fr> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert writes: > According to Nate Williams: > > '-P', which causes it to remove directories that become emtpy as they > > occur. Why this isn't the default behavior has been subject to much > > discussion on the CVS mailing lists. :( > > Speaking of which, do you intent to import CVS 1.8.1 (whichever release is > last, I use the snapshots myself...) ? Peter's the CVS-meister, and I believe he answered that question already. Basically, I read it as 'when he quits having fun at work'. :) (Then we'll get gcc, cvs, and his SMP stuff all at once. :) Nate From owner-freebsd-current Wed Aug 7 14:20:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09710 for current-outgoing; Wed, 7 Aug 1996 14:20:08 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09692 for ; Wed, 7 Aug 1996 14:20:02 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA27826; Wed, 7 Aug 1996 14:18:54 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma027824; Wed Aug 7 14:18:45 1996 Message-ID: <3209080D.446B9B3D@whistle.com> Date: Wed, 07 Aug 1996 14:18:05 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "R.D. Thrush" CC: freebsd-current@freebsd.org Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP References: <199608071953.PAA11197@tarpit.thrush.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk R.D. Thrush wrote: > > 2.2-960801-SNAP is unable to recognize multiple LUNs on a wide scsi > target connected to either a BusLogic 956C or an Adaptec 2940UW. Is > there some additional kernel configuration required to enable > detection of multiple LUNs? > > FWIW, on the same hardware, bsd/os 2.1 locates all 5 LUNs on the one > target when connected to either of the above 2 adapters. we found so many devices that erroneously responded to all LUNS that we disabled it by default. see /sys/scsi/scsiconf.c look for SC_ALL_LUNS (or something like that) you may need to put a recognition entry in for your device. From owner-freebsd-current Wed Aug 7 14:23:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09870 for current-outgoing; Wed, 7 Aug 1996 14:23:03 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09863 for ; Wed, 7 Aug 1996 14:22:59 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id VAA14379; Wed, 7 Aug 1996 21:22:44 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma014376; Wed Aug 7 21:22:40 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id OAA01004; Wed, 7 Aug 1996 14:22:40 -0700 Date: Wed, 7 Aug 1996 14:22:40 -0700 From: "M.R.Murphy" Message-Id: <199608072122.OAA01004@meerkat.mole.org> To: gibbs@freefall.freebsd.org, rd@thrush.com Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP Cc: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > 2.2-960801-SNAP is unable to recognize multiple LUNs on a wide scsi > >target connected to either a BusLogic 956C or an Adaptec 2940UW. Is > >there some additional kernel configuration required to enable > >detection of multiple LUNs? > > > > FWIW, on the same hardware, bsd/os 2.1 locates all 5 LUNs on the one > >target when connected to either of the above 2 adapters. > > You need to add a quirk for your device that says that it is a multi-lun > device. The FreeBSD SCSI code defaults to *not* probing for additional > luns, but the logic will be reversed as soon as I find the time to import > the NetBSD quirk table entries for devices that can't handle multi-lun > probing. > Make sure you get all the quirk table entries for _all_ the quirky devices, then. If you miss one, it'll crash and burn. And maybe destroy valuable(tm) data. Might it be better to make it an option rather than just changing a know behavior? Maybe with some documentation on the option, like in LINT? -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Wed Aug 7 14:39:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10685 for current-outgoing; Wed, 7 Aug 1996 14:39:33 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA10678 for ; Wed, 7 Aug 1996 14:39:28 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id VAA14507; Wed, 7 Aug 1996 21:39:14 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma014505; Wed Aug 7 21:39:00 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id OAA01075; Wed, 7 Aug 1996 14:39:00 -0700 Date: Wed, 7 Aug 1996 14:39:00 -0700 From: "M.R.Murphy" Message-Id: <199608072139.OAA01075@meerkat.mole.org> To: julian@whistle.com, rd@thrush.com Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP Cc: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > R.D. Thrush wrote: > > > > 2.2-960801-SNAP is unable to recognize multiple LUNs on a wide scsi > > target connected to either a BusLogic 956C or an Adaptec 2940UW. Is > > there some additional kernel configuration required to enable > > detection of multiple LUNs? > > > > FWIW, on the same hardware, bsd/os 2.1 locates all 5 LUNs on the one > > target when connected to either of the above 2 adapters. > we found so many devices that erroneously responded to > all LUNS that we disabled it by default. A fine reason for leaving it disabled :-) > > see /sys/scsi/scsiconf.c > > look for SC_ALL_LUNS (or something like that) > you may need to put a recognition entry in for your device. > There is also some ctrl-A setup stuff in the 2940 that refers to multiple LUN support. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Wed Aug 7 15:07:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA12708 for current-outgoing; Wed, 7 Aug 1996 15:07:37 -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 PAA12702 for ; Wed, 7 Aug 1996 15:07:33 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA05942; Thu, 8 Aug 1996 08:04:31 +1000 Date: Thu, 8 Aug 1996 08:04:31 +1000 From: Bruce Evans Message-Id: <199608072204.IAA05942@godzilla.zeta.org.au> To: gibbs@freefall.freebsd.org, nate@mt.sri.com Subject: Re: Whither gcc 2.7? Cc: current@FreeBSD.org, peter@spinner.dialix.com, phk@critter.tfs.com, rgrimes@gndrsh.aac.dev.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Why not import the whole thing but only distribute the i386 code by >default? We can easily setup additional CVSup targets for the non >i386 portions of the compiler for people interested in cross compiling >or working on a new port. To begin with, the non-i386 parts of gcc-2.7.2 are less than 1/3 of the total: config/i386 597 K config/other 7494 ChangeLog* 3792 gcc.info* 1209 cpp.info* 113 texinfo.tex 152 # we have only 1 copy of this (in amd/doc :-() ginclude 85 objc 202 cp 3066 *.texi 1295 *.1 137 *.[chy] 8771 # not counting subdirectories other 1406 ----- total 28319 Bruce From owner-freebsd-current Wed Aug 7 15:34:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14340 for current-outgoing; Wed, 7 Aug 1996 15:34:57 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA14327 for ; Wed, 7 Aug 1996 15:34:52 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id SAA29796; Wed, 7 Aug 1996 18:34:22 -0400 Date: Wed, 7 Aug 1996 18:34:22 -0400 Message-Id: <199608072234.SAA29796@kropotkin.gnu.ai.mit.edu> To: coredump@nervosa.vendetta.com CC: peter@spinner.DIALix.COM, nate@mt.sri.com, current@FreeBSD.org In-reply-to: (message from Chris Layne on Wed, 7 Aug 1996 10:09:55 -0700 (PDT)) Subject: Re: Whither gcc 2.7? From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> I have other things on the agenda: - libncurses > Yes, finally, it's up to 1.9.9 now. Also, is it just me, or does > the format of coordinates (y, x) ncurses requires seem just a > little nonstandard? I thought in math and everything else, > coordinates were expected in (x, y) form? In terminal control libraries, it is traditional to specify coordinates in y,x (alias row,column) form. This may be from addressing screen_array[y][x]. I have seen very few terminal control libraries that use x,y addressing. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu The number you have reached is an imaginary number. Please rotate your phone 90 degrees and try again. From owner-freebsd-current Wed Aug 7 15:35:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14388 for current-outgoing; Wed, 7 Aug 1996 15:35:06 -0700 (PDT) Received: from tarpit.thrush.com (rd@tarpit.magicnet.net [206.104.206.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14375 for ; Wed, 7 Aug 1996 15:35:03 -0700 (PDT) Received: (from rd@localhost) by tarpit.thrush.com (8.7.4/8.7.3) id SAA15701; Wed, 7 Aug 1996 18:34:27 -0400 (EDT) Date: Wed, 7 Aug 1996 18:34:27 -0400 (EDT) From: "R.D. Thrush" Message-Id: <199608072234.SAA15701@tarpit.thrush.com> To: mrm@Mole.ORG (M.R.Murphy) CC: freebsd-current@freebsd.org In-reply-to: mrm@Mole.ORG's message of 7 Aug 96 21:39:00 GMT Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP References: <199608072139.OAA01075@meerkat.mole.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "M" == M R Murphy writes: >> see /sys/scsi/scsiconf.c >> >> look for SC_ALL_LUNS (or something like that) >> you may need to put a recognition entry in for your device. M> There is also some ctrl-A setup stuff in the 2940 that refers to M> multiple LUN support. That makes no difference to bsd/os. It also adds an additional almost 2 minutes before the boot is started. I'll soon know whether it makes any difference to FreeBSD. From owner-freebsd-current Wed Aug 7 15:43:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15147 for current-outgoing; Wed, 7 Aug 1996 15:43:49 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15142 for ; Wed, 7 Aug 1996 15:43:46 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id WAA14863; Wed, 7 Aug 1996 22:43:13 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma014861; Wed Aug 7 22:42:55 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id PAA01231; Wed, 7 Aug 1996 15:42:55 -0700 Date: Wed, 7 Aug 1996 15:42:55 -0700 From: "M.R.Murphy" Message-Id: <199608072242.PAA01231@meerkat.mole.org> To: mrm@mole.mole.org, rd@thrush.com Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > M> There is also some ctrl-A setup stuff in the 2940 that refers to > M> multiple LUN support. > > That makes no difference to bsd/os. It also adds an additional > almost 2 minutes before the boot is started. I'll soon know whether > it makes any difference to FreeBSD. > Fair enough. Turning off the ctrl-A selection by ID for multiple LUN support made a quirky device work. Otherwise it answered to all LUNS and wouldn't come up. I only have a real multiple-LUN device on a 1542 and so can't say about good devices on 2940. I can say about bad :-) -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Wed Aug 7 16:52:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA18240 for current-outgoing; Wed, 7 Aug 1996 16:52:54 -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 QAA18235 for ; Wed, 7 Aug 1996 16:52:48 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id JAA23323; Thu, 8 Aug 1996 09:35:56 +0930 From: Michael Smith Message-Id: <199608080005.JAA23323@genesis.atrad.adelaide.edu.au> Subject: Re: Linux Willows? To: dev@fgate.flevel.co.uk (Developer) Date: Thu, 8 Aug 1996 09:35:55 +0930 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Developer" at Aug 7, 96 03:00:41 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 Developer stands accused of saying: > > I`m trying to use the linux version of the development kit on freebsd to > see how it runs, Ive found that the link libraries are linux version.. so > I need to use the linux gcc/ld and produce linux executables - unless > someone knows how to convert linux library to freebsd? > > The problem I`m having now is ld can`t find crt1.o and crti.o .. any ideas > where to get these from - I have crt0.o but I guess that isn`t the same > thing.. > LINUX WILLOWS DOES NOT RUN ON FREEBSD, and CAN NOT BE USED TO BUILD APPLICATIONS UNDER FREEBSD. How many times does it have to be said? Willows have just recently gone to a commercial model, and whilst they are capable of producing a FreeBSD version, they want a few orders (at ~$5k a seat) to justify it. > Trefor S. -- ]] 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 Wed Aug 7 17:24:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA19912 for current-outgoing; Wed, 7 Aug 1996 17:24:01 -0700 (PDT) Received: (from grog@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA19893; Wed, 7 Aug 1996 17:23:59 -0700 (PDT) From: Greg Lehey Message-Id: <199608080023.RAA19893@freefall.freebsd.org> Subject: Re: Linux Willows? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 7 Aug 1996 17:23:59 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, current@freefall.freebsd.org In-Reply-To: <199608070237.MAA19277@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 7, 96 12:07:09 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Greg Lehey stands accused of saying: > > > > > > There isn't one. _Please_ also note that the TWIN XPDK is _NOT_ a > > > windows emulator. It is a cross-development platform for porting > > > Windows applications to Unices. > > > > Well, part of it emulates Windoze, specifically the xwin program. > > Correct. You'll note that it's a development tool though, not a Windows > emulator. What's in a name? That which we call a rose and all that. > > Willows are trying to position twin as a cross-development platform, > > but I see it as being equally important as a Windoze emulator. Recent > > mail on the mailing list suggests that they're gradually realizing > > that too. > > Err, I'm on that list too; last I heard on the topic was Rod agreeing > vehemently with me that trying to be a Windows emulator was pointless, > and enumerating just exactly why from his point of view. Why don't you summarize? I'm on vacation and have only been skimming the newsgroup, and I'm sure that a lot of other people would benefit too. In any case, with twin now costing $5,000, it's not really viable as a Windoze emulator. *sigh* Greg From owner-freebsd-current Wed Aug 7 18:28:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23113 for current-outgoing; Wed, 7 Aug 1996 18:28:47 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA23104 for ; Wed, 7 Aug 1996 18:28:42 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id RAA16244; Wed, 7 Aug 1996 17:39:52 -0400 (EDT) Date: Wed, 7 Aug 1996 17:39:51 -0400 (EDT) From: "Charles C. Figueiredo" To: current@freebsd.org Subject: exploitable security risk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /usr/src/usr.bin/modstat/modstat.c does a blind strcpy from a char pointer into a 32 byte buffer. What makes this worse is that strcpy does not check len, and what's being copied into the 32 byte buffer is specified via argv. If it were a bigger buffer it'd be easier to exploit, but anyone proficient in x86 asm could probably handle 32 bytes. It's quite obvious that this is a very possible buffer overflow. I've prepared a diff from the latest modstat.c to a more secure modstat.c ;-) -- 48a49,50 > #define MNLEN 32 > 75,76c77,78 < if (modname != NULL) < strcpy(sbuf.name, modname); --- > if ( modname != NULL) > strncpy(sbuf.name, modname, MNLEN); -- ------------------------------------------------------------------------------ Charles C. Figueiredo CCF13 marxx@doomsday.org ------------------------------------------------------------------------------ From owner-freebsd-current Wed Aug 7 18:47:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23655 for current-outgoing; Wed, 7 Aug 1996 18:47:51 -0700 (PDT) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA23650; Wed, 7 Aug 1996 18:47:48 -0700 (PDT) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id UAA01699; Wed, 7 Aug 1996 20:47:46 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 7 Aug 1996 20:47:46 -0500 To: Greg Lehey From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Linux Willows? Cc: current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Greg Lehey stands accused of saying: >> > > >> > > There isn't one. _Please_ also note that the TWIN XPDK is _NOT_ a >> > > windows emulator. It is a cross-development platform for porting >> > > Windows applications to Unices. >> > >> > Well, part of it emulates Windoze, specifically the xwin program. >> >> Correct. You'll note that it's a development tool though, not a Windows >> emulator. > > >What's in a name? That which we call a rose and all that. There is a big difference in a cross platform system and an emulator. In the former case, you are effectively defining a new system that is emulated on each of the platforms. In this case, the emulation has to handle only those constructs which are used by the development language. To be a general emulator of another system, the emulator must handle ALL of the constructs of that system. In general, that is a much larger set. From owner-freebsd-current Wed Aug 7 19:38:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA27652 for current-outgoing; Wed, 7 Aug 1996 19:38:50 -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 TAA27645 for ; Wed, 7 Aug 1996 19:38:44 -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 TAA14326; Wed, 7 Aug 1996 19:38:18 -0700 (PDT) To: Jonathan Lemon cc: freebsd-current@FreeBSD.org Subject: Re: locking up In-reply-to: Your message of "Wed, 07 Aug 1996 12:29:55 CDT." <199608071729.MAA00250@right.PCS> Date: Wed, 07 Aug 1996 19:38:18 -0700 Message-ID: <14324.839471898@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > echo "set ipending=2" | gdb -k -w /kernel /dev/mem > > I have the same problem - I'm running 2.1.0R CD distribution, and at random > times during an X session, the keyboard just freezes up. Executing 'kbd_mode ' > doesn't fix the problem either. Logging in remotely and killing the X server > clears up the difficulty though, or executing the above commandline. I never had this problem until I started using xmodmap with Xaccel to swap the caps lock and control keys on my new Microsoft natural keyboard (the Northgate I had before let me do this directly on the keyboard with a switch). Now, every once in awhile (usually when I'm using the control key :-), the keyboard will lock up. In the past I could clear it only by restartarting the X server, now it appears that this same gdb trick works for me in getting my keyboard back. I've made a button for it in my fvwm menu. :-) Still, it'd be nice to know how/why this trick rescues the keyboard for Xaccel. Anyone see this same kind of problem with XFree86? Jordan From owner-freebsd-current Wed Aug 7 21:09:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04393 for current-outgoing; Wed, 7 Aug 1996 21:09:09 -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 VAA04374 for ; Wed, 7 Aug 1996 21:08:59 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA20007 for current@freebsd.org; Thu, 8 Aug 1996 00:08:49 -0400 From: Bill Paul Message-Id: <199608080408.AAA20007@skynet.ctr.columbia.edu> Subject: ATAPI CD-ROM fun To: current@freebsd.org Date: Thu, 8 Aug 1996 00:08:47 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We recently got in a batch of Gateway 2000 200Mhz Pentium machines with IDE CD-ROMs (Toshiba 8x). These are apparently slated to become dual-boot Windoze NT and Linux (*spit*) machines, though I'm doing my best to campaign for FreeBSD (there are unusual circumstances: they have plans to do some work with wireless network devices which have sample drivers only for Linux (and which aren't freely available) -- I've offered to port them to FreeBSD myself just so I won't have to deal with Linux). Anyway. I did some tests with FreeBSD on these machines and I ran across some interesting things: - FreeBSD 2.1.5-RELEASE doesn't seem to want anything to do with the CD-ROM though FreeBSD 2.2-SNAP (most recent one) likes it just fine (though see below for caveats). - The 3c509B UTP-only ethernet cards wedge up after a few seconds of activity with FreeBSD 2.1.5-RELEASE but work find with 2.2-SNAP. But that's neither here nor there. - The machines came with the IDE CD-ROMs jumpered as master devices on the secondary IDE controller. 2.2-SNAP failed to recognize the CD-ROM in this case, however if I rejumpered the drives to slaves, they were detected and worked perfectly once I put together a custom kernel with the right configuration. - The GENERIC kernel (and the kernel on the boot floppy) in the SNAP causes sysinstall to get mightily confused due to the following peculiar behavior: with the CD-ROM jumpered as a slave, the wd driver falsely detects an IDE hard drive at unit 0 on the secondary controller in addition to the ATAPI CD-ROM drive. This means you have a fictional wd2 with bogus geometry values (in my case they were the BIOS values for the real IDE drive at unit 0 on the primary controller). Curiously enough, the system will continue to function in this state and the CD-ROM will even work. However, sysinstall wedges when it goes looking for devices because attempting to access the fictitious wd2 device doesn't work. It's not really fair to blame sysinstall for this bug since it has no easy way to tell that the device is bogus. Unfortunately, userconfig doesn't offer a way to disable individual drives so you have to disable the whole controller in order to get to the install menu. The wd driver should be smarter about this. - After some tinkering I was finally able to get the 2.2-SNAP kernel to recognize the CD-ROM when it was jumpered as a master device. The problem seems to be tha wdprobe() is erroring out unnecessarily. I did a gross hack wherein I forced the probe to return success if the check for an ATAPI master device succeeded. It seems that the probe can detect the ATAPI signature of the master device, but a later part of wdprobe() fails which causes the device to be incorrectly skipped. I think that part that's failing is immediately after the ATAPI signature checks, where it tries to send a WDC_DIAGNOSE command to the controller. I need to play with this a bit more though. As if I don't already have enough to do. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-current Wed Aug 7 22:31:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.FreeBSD.org (8.7.5/8.7.3) id WAA08723 for current-outgoing; Wed, 7 Aug 1996 22:31:12 -0700 (PDT) Received: from parkplace.cet.co.jp ([202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08646 for ; Wed, 7 Aug 1996 22:28:28 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id FAA11968; Thu, 8 Aug 1996 05:27:52 GMT Date: Thu, 8 Aug 1996 14:27:51 +0900 (JST) From: Michael Hancock To: "Brian N. Handy" cc: Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? 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, 7 Aug 1996, Brian N. Handy wrote: > I guess another thing I wonder about...has anyone thought about the future > plans of tracking gcc? We've been running 2.6.3 for a loong time, are we > going to move to 2.7.# and stay with it or is FreeBSD going to start > tracking gcc more closely? Since we're using gcc to compile the kernel we need to identify stable releases of gcc and stick with it for a while. Closely tracking and incorporating all gcc releases (including unstable releases) is not a high priority. Regards, Mike Hancock From owner-freebsd-current Wed Aug 7 23:02:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA12945 for current-outgoing; Wed, 7 Aug 1996 23:02:35 -0700 (PDT) Received: from parkplace.cet.co.jp ([202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08646 for ; Wed, 7 Aug 1996 22:28:28 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id FAA11968; Thu, 8 Aug 1996 05:27:52 GMT Date: Thu, 8 Aug 1996 14:27:51 +0900 (JST) From: Michael Hancock To: "Brian N. Handy" cc: Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? 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, 7 Aug 1996, Brian N. Handy wrote: > I guess another thing I wonder about...has anyone thought about the future > plans of tracking gcc? We've been running 2.6.3 for a loong time, are we > going to move to 2.7.# and stay with it or is FreeBSD going to start > tracking gcc more closely? Since we're using gcc to compile the kernel we need to identify stable releases of gcc and stick with it for a while. Closely tracking and incorporating all gcc releases (including unstable releases) is not a high priority. Regards, Mike Hancock From owner-freebsd-current Wed Aug 7 23:40:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14883 for current-outgoing; Wed, 7 Aug 1996 23:40:24 -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 XAA14877; Wed, 7 Aug 1996 23:40:22 -0700 (PDT) Message-Id: <199608080640.XAA14877@freefall.freebsd.org> To: "M.R.Murphy" cc: julian@whistle.com, rd@thrush.com, freebsd-current@FreeBSD.org Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP In-reply-to: Your message of "Wed, 07 Aug 1996 14:39:00 PDT." <199608072139.OAA01075@meerkat.mole.org> Date: Wed, 07 Aug 1996 23:40:21 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> we found so many devices that erroneously responded to >> all LUNS that we disabled it by default. > >A fine reason for leaving it disabled :-) I think that this approach was appropriate in the early days of SCSI when a large majority of the devices out there were non-compliant and simply ignored the lun field. Very few modern devices suffer from this problem (the Chinnon 525 is the last one I know of) and more and more devices require multi-lun support to function fully. Since NetBSD already has a full quirk list of the bogus devices, I don't see any reason not to enable Lun support by default. >There is also some ctrl-A setup stuff in the 2940 that refers to >multiple LUN support. That only affects the BIOS. It may be recorded in the SEEPROM on the card so that FreeBSD could honor it, but I'd rather see it become a userconfig type of option. >-- >Mike Murphy mrm@Mole.ORG +1 619 598 5874 >Better is the enemy of Good -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Aug 8 00:57:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19396 for current-outgoing; Thu, 8 Aug 1996 00:57:15 -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 AAA19381 for ; Thu, 8 Aug 1996 00:57:10 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA10663; Thu, 8 Aug 1996 09:56:02 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22333; Thu, 8 Aug 1996 09:56:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA16028; Thu, 8 Aug 1996 07:54:58 +0200 (MET DST) From: J Wunsch Message-Id: <199608080554.HAA16028@uriah.heep.sax.de> Subject: Re: boot screen flashes - why? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 8 Aug 1996 07:54:58 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608061127.NAA09560@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at "Aug 6, 96 01:27:02 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 Christoph P. Kukulies wrote: > When booting my machine (Amd5x86, ASUS SP3G, ELSA Winner 1000 PCI) > The screen flashes (blanked out black) two times. Once right after > ther fdc/fd0 probe, second some time later - don't know exactly > where at the moment. Today it happened that (with a today's kernel) > during that screen flash the screen remained black and the machine > was frozen - had to power cycle. What is being probed right after fdc0 in your kernel? I've only seen flashes while the graphics console driver(s) touch the adapter. (The flash while probing syscons seems to last a little longer than that for pcvt.) The second flash is perhaps from loading a font down to the VGA? -- 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 Aug 8 01:02:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA19940 for current-outgoing; Thu, 8 Aug 1996 01:02:13 -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 BAA19921 for ; Thu, 8 Aug 1996 01:01:57 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA10646; Thu, 8 Aug 1996 09:55:49 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22318; Thu, 8 Aug 1996 09:55:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA16390; Thu, 8 Aug 1996 08:19:40 +0200 (MET DST) From: J Wunsch Message-Id: <199608080619.IAA16390@uriah.heep.sax.de> Subject: Re: exploitable security risk To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 8 Aug 1996 08:19:40 +0200 (MET DST) Cc: marxx@doomsday.org (Charles C. Figueiredo) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Charles C. Figueiredo" at "Aug 7, 96 05:39:51 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 Charles C. Figueiredo wrote: > /usr/src/usr.bin/modstat/modstat.c does a blind strcpy from a char > pointer into a 32 byte buffer. [...] Thansk for pointing this out. However: > 48a49,50 > > #define MNLEN 32 > > > 75,76c77,78 > < if (modname != NULL) > < strcpy(sbuf.name, modname); > --- > > if ( modname != NULL) > > strncpy(sbuf.name, modname, MNLEN); . the name of the constant is MAXLKMNAME (now?) . the string should be '\0'-terminated even in case strncpy() trims it . a context diff would have been more appreciated ;) I'm going to commit a fix based on your suggestion, thanks! -- 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 Aug 8 01:17:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA20988 for current-outgoing; Thu, 8 Aug 1996 01:17:18 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA20980 for ; Thu, 8 Aug 1996 01:17:13 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA14910; Thu, 8 Aug 1996 09:20:30 +0100 (BST) Date: Thu, 8 Aug 1996 09:20:30 +0100 (BST) From: Developer To: Sujal Patel cc: Charles Green , current@FreeBSD.org Subject: Re: Willows support for freebsd 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 > AFAIK, the port should of everything (including xwin) should not be very > difficult for their programmers. It seems to me that support for FreeBSD > just isn't on their agenda. > > Anyone want to take a crack at getting the Linux version working on > -current? I don't think it will be easy, but it should be possible. I would be interested in this - but I really don't have the knowledge to handle the linux ldt's myself.. but as far as testing and co-ordination goes you can count me in. Regards, Trefor S. From owner-freebsd-current Thu Aug 8 03:48:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA29053 for current-outgoing; Thu, 8 Aug 1996 03:48:08 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA29018 for ; Thu, 8 Aug 1996 03:47:56 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA05379; Thu, 8 Aug 1996 12:42:32 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA18156; Thu, 8 Aug 1996 12:55:42 +0200 From: "Christoph P. Kukulies" Message-Id: <199608081055.MAA18156@gilberto.physik.rwth-aachen.de> Subject: Re: boot screen flashes - why? To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 8 Aug 1996 12:55:41 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199608080554.HAA16028@uriah.heep.sax.de> from J Wunsch at "Aug 8, 96 07:54:58 am" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (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 Christoph P. Kukulies wrote: > > > When booting my machine (Amd5x86, ASUS SP3G, ELSA Winner 1000 PCI) > > The screen flashes (blanked out black) two times. Once right after > > ther fdc/fd0 probe, second some time later - don't know exactly > > where at the moment. Today it happened that (with a today's kernel) > > during that screen flash the screen remained black and the machine > > was frozen - had to power cycle. > > What is being probed right after fdc0 in your kernel? I've only seen > flashes while the graphics console driver(s) touch the adapter. (The > flash while probing syscons seems to last a little longer than that > for pcvt.) > > The second flash is perhaps from loading a font down to the VGA? Hmm - no I don't load other fonts - I tried it today with a new kernel and now I'm only seeing one flash right during the vga probe which seems to make sense. So what. > > -- > 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. ;-) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Thu Aug 8 07:27:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA10277 for current-outgoing; Thu, 8 Aug 1996 07:27:08 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA10270 for ; Thu, 8 Aug 1996 07:27:04 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id OAA20178; Thu, 8 Aug 1996 14:26:37 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma020175; Thu Aug 8 14:26:10 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id HAA03826; Thu, 8 Aug 1996 07:26:10 -0700 Date: Thu, 8 Aug 1996 07:26:10 -0700 From: "M.R.Murphy" Message-Id: <199608081426.HAA03826@meerkat.mole.org> To: gibbs@freefall.freebsd.org, mrm@mole.mole.org Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP Cc: freebsd-current@FreeBSD.org, julian@whistle.com, rd@thrush.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > has a full quirk list of the bogus devices, I don't see any reason not > to enable Lun support by default. The key word here is "full". -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Thu Aug 8 07:36:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA11001 for current-outgoing; Thu, 8 Aug 1996 07:36:39 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA10988 for ; Thu, 8 Aug 1996 07:36:36 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id OAA20234; Thu, 8 Aug 1996 14:36:07 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma020228; Thu Aug 8 14:35:38 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id HAA03855; Thu, 8 Aug 1996 07:35:38 -0700 Date: Thu, 8 Aug 1996 07:35:38 -0700 From: "M.R.Murphy" Message-Id: <199608081435.HAA03855@meerkat.mole.org> To: gibbs@freefall.freebsd.org, mrm@mole.mole.org Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP Cc: freebsd-current@FreeBSD.org, julian@whistle.com, rd@thrush.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > >There is also some ctrl-A setup stuff in the 2940 that refers to > >multiple LUN support. > > That only affects the BIOS. It may be recorded in the SEEPROM on the > card so that FreeBSD could honor it, but I'd rather see it become a > userconfig type of option. With some devices turning on LUN support in the BIOS on a 2940 keeps the system from booting at all. Sure I can disconnect the device, build the system, turn off the new default behavior, and continue on my way. No big deal. However, changing the default behavior from "my multi-lun device doesn't work, enable it" to "my system doesn't work, take it apart" might generate some questions. Questions that are the equivalent of "my Mach64 doesn't work, the screen goes blank, what should I do?" I know that the behavior will be changed when Justin gets some time. I'll live with it, again, no big deal. But the direction of change is, I think, ill-considered. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Thu Aug 8 08:41:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA14703 for current-outgoing; Thu, 8 Aug 1996 08:41:01 -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 IAA14698; Thu, 8 Aug 1996 08:40:58 -0700 (PDT) Message-Id: <199608081540.IAA14698@freefall.freebsd.org> To: "M.R.Murphy" cc: mrm@mole.mole.org, freebsd-current@FreeBSD.org, julian@whistle.com, rd@thrush.com Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP In-reply-to: Your message of "Thu, 08 Aug 1996 07:35:38 PDT." <199608081435.HAA03855@meerkat.mole.org> Date: Thu, 08 Aug 1996 08:40:57 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >With some devices turning on LUN support in the BIOS on a 2940 >keeps the system from booting at all. Tell me what the devices are. I'm sure they are already in the table. >Sure I can disconnect the device, build the system, turn off the new >default behavior, and continue on my way. No big deal. 2.2 is a ways off. The plan is to export information about the scsi system in a generic way through userconfig before we ship. You'll be able to at least disable tagged queuing and multi-lun probing from there if not sync/async settings as well. We may even ship the installation kernel with these two options turned off by default. >However, changing the default behavior from "my multi-lun device >doesn't work, enable it" to "my system doesn't work, take it apart" >might generate some questions. Questions that are the equivalent >of "my Mach64 doesn't work, the screen goes blank, what should I >do?" This has not been the case for BSD/OS or NetBSD and neither have a way to change this at boot time as FreeBSD will. >I know that the behavior will be changed when Justin gets some time. >I'll live with it, again, no big deal. But the direction of change >is, I think, ill-considered. I've actually considered it quite a bit. Point me to some devices that show this behavior that aren't in the NetBSD quirk table and I might think otherwise. >-- >Mike Murphy mrm@Mole.ORG +1 619 598 5874 >Better is the enemy of Good -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Aug 8 09:14:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA17135 for current-outgoing; Thu, 8 Aug 1996 09:14:18 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA17125 for ; Thu, 8 Aug 1996 09:14:11 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA04608 (5.67b/IDA-1.5 for ); Thu, 8 Aug 1996 18:13:35 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id SAA03186; Thu, 8 Aug 1996 18:13:08 +0200 (MET DST) Date: Thu, 8 Aug 1996 18:13:08 +0200 (MET DST) Message-Id: <199608081613.SAA03186@x14.mi.uni-koeln.de> From: Stefan Esser To: "Christoph P. Kukulies" Cc: freebsd-current@freefall.freebsd.org Subject: Re: ncr dead message In-Reply-To: <199608061121.NAA09546@gilberto.physik.rwth-aachen.de> References: <199608061121.NAA09546@gilberto.physik.rwth-aachen.de> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Christoph P. Kukulies writes: > I found this in my /var/log/messages: (2.2-current of Aug 1st) > > Aug 2 10:29:13 isdn /kernel: ncr0:0: ERROR (80:4) (8-0-0) (8/13) @ (b30:c0000001). This is most probably a transient problem: dstat=0x80: DMA FIFO empty (that's ok) sist =0x04: Unexpected Disconnect (but that's a problem ...) The ATN line is asserted, and the last bus phase appears to have been a DATA OUT. > Aug 2 10:29:26 isdn /kernel: script cmd = 800c0006 > Aug 2 10:29:26 isdn /kernel: reg: da 00 80 13 47 08 00 1f 01 08 80 00 80 00 0e 02. > Aug 2 10:29:26 isdn /kernel: ncr0: restart (ncr dead ?). I'm not sure why this hung the system, but it might have been due to a lost strobe ... > Aug 2 10:29:26 isdn /kernel: ncr0: restart (ncr dead ?). > Aug 2 10:29:26 isdn /kernel: swap_pager: I/O error - async pageout failed; blkno 9984, size 8192, error 5 > Aug 2 10:29:26 isdn /kernel: swap_pager_finish: I/O error, clean of page 916000 failed > Aug 2 10:29:26 isdn /kernel: swap_pager_finish: I/O error, clean of page 913000 failed I'm not sure what the swap pager does in that case. Is it fatal, or will the operation just be retried next time the page is found eligible for page out ? > It was a single occurance and maybe a transient failure. Anyway, I'm > reporting it here just fyi. Well, it doesn't look like a driver problem. Regards, STefan From owner-freebsd-current Thu Aug 8 09:32:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19085 for current-outgoing; Thu, 8 Aug 1996 09:32:31 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-187.ut.nl.ibm.net [139.92.42.187]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA18985; Thu, 8 Aug 1996 09:32:04 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id SAA07123; Wed, 7 Aug 1996 18:07:33 +0200 (MET DST) Message-Id: <199608071607.SAA07123@vector.jhs.no_domain> To: "Christoph P. Kukulies" cc: freebsd-current@freefall.freebsd.org Subject: Automatic maintenance of local variants of FreeBSD sources From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Mon, 05 Aug 1996 17:19:46 +0200." <199608051519.RAA06208@gilberto.physik.rwth-aachen.de> Date: Wed, 07 Aug 1996 18:07:31 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: "Christoph P. Kukulies" > Subject: Re: snd into -current > > Recent augmentations in the linux_ioctl area (sound ioctls) > make it a pain to keep up with -current while still using > the newer sounddriver. Ref. Automatic maintenance of local variants of distribution sources: I have many local patches, so I automated local maintenance, Here's how: I keep 2 copies of Src/ & Ports/ trees: Ref/ & Work/ . Ref/ (but not Work/) is maintained by automatically applying CTM deltas received via mail & diverted by my .procmailrc, viewable as: http://www.freebsd.org/~jhs/dots/.procmailrc CTMs pass via /etc/aliases to: http://www.freebsd.org/~jhs/src/bsd/ournix/bin/local/mail/\ ctm-src-cur-incoming which also archives the deltas, so I can also manually apply them to Work/ using cut & paste from output of: http://www.freebsd.org/~jhs/bin/ctms When I occasionally want to start afresh, I copy Ref/ to Work/, & run http://www.freebsd.org/~jhs/bin/customise This applies my tree of patches & new files: http://www.freebsd.org/~jhs/src/bsd/fixes/FreeBSD/\ {src & ports}/{generic & jhs}/..... All of which are indexed at: http://www.freebsd.org/~jhs/src_index.html My http://www.freebsd.org/~jhs/ web directory is usually maintained by daily manual use of rdist (which being slow, usually isn't finished by the time I hang up the modem, so is not guaranteed synchronous ). Grab whatever methods / scripts / patches you fancy. "Share & Enjoy" :-) PS Though I post diffs & new files to the lists, naturally not all get committed, some aren't even in my opinion of generic applicability, hence an ever increasing stockpile, now auto maintained :-). PPS I've converted this mail item to a new http://www.freebsd.org/~jhs/src_automatic.html Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Thu Aug 8 09:50:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA20903 for current-outgoing; Thu, 8 Aug 1996 09:50:40 -0700 (PDT) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA20870 for ; Thu, 8 Aug 1996 09:50:22 -0700 (PDT) Received: (from chuck@localhost) by fang.cs.sunyit.edu (8.6.9/8.6.9) id MAA06950; Thu, 8 Aug 1996 12:50:13 -0400 Date: Thu, 8 Aug 1996 12:50:13 -0400 From: Charles Green Message-Id: <199608081650.MAA06950@fang.cs.sunyit.edu> In-Reply-To: Greg Lehey "Re: Linux Willows?" (Aug 7, 17:23) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Greg Lehey Subject: Re: Linux Willows? Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Lehey stands accused of saying: } Date: Aug 7, 17:23 } Subject: Re: Linux Willows? } } > Err, I'm on that list too; last I heard on the topic was Rod agreeing } > vehemently with me that trying to be a Windows emulator was pointless, } > and enumerating just exactly why from his point of view. } } Why don't you summarize? I'm on vacation and have only been skimming } the newsgroup, and I'm sure that a lot of other people would benefit } too. In any case, with twin now costing $5,000, it's not really } viable as a Windoze emulator. *sigh* } } Greg } }-- End of excerpt from Greg Lehey What would be nice, is for willows to take a subset of their work (xwin) and market it *as* a windows emulator and sell it for something like $99.00 (binary only). I'd buy it. -- Charles Green, PRC Inc. Rome Laboratory, NY From owner-freebsd-current Thu Aug 8 11:03:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03024 for current-outgoing; Thu, 8 Aug 1996 11:03:31 -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 LAA03017 for ; Thu, 8 Aug 1996 11:03:28 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA26515; Thu, 8 Aug 1996 14:02:14 -0400 Date: Thu, 8 Aug 1996 14:02:14 -0400 From: Garrett Wollman Message-Id: <9608081802.AA26515@halloran-eldar.lcs.mit.edu> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users), marxx@doomsday.org (Charles C. Figueiredo) Subject: Re: exploitable security risk In-Reply-To: <199608080619.IAA16390@uriah.heep.sax.de> References: <199608080619.IAA16390@uriah.heep.sax.de> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: >> > if ( modname != NULL) >> > strncpy(sbuf.name, modname, MNLEN); > . the name of the constant is MAXLKMNAME (now?) Actually, the name of the constant is `sizeof sbuf.name'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Aug 8 13:39:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA10588 for current-outgoing; Thu, 8 Aug 1996 13:39:18 -0700 (PDT) Received: from hil-img-3.compuserve.com (hil-img-3.compuserve.com [149.174.177.133]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA10581 for ; Thu, 8 Aug 1996 13:39:15 -0700 (PDT) Received: by hil-img-3.compuserve.com (8.6.10/5.950515) id QAA14188; Thu, 8 Aug 1996 16:38:43 -0400 Date: 08 Aug 96 16:37:49 EDT From: Jan Knepper <100626.3506@CompuServe.COM> To: "[FreeBSD current]" Subject: Matrox Millennium Message-ID: <960808203748_100626.3506_BHL159-1@CompuServe.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I tried to setup XFree86 on FreeBSd 2.1.0 and got into a few problems because my system has a Matrox Video adapter. SuperProbe returns an Oak chipset with 64K. Since there is 2 MB on the card I don't think that is a good choice. Thanks in advance for any help. Don't worry, be Kneppie, Jan From owner-freebsd-current Thu Aug 8 13:46:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11102 for current-outgoing; Thu, 8 Aug 1996 13:46:07 -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 NAA11089 for ; Thu, 8 Aug 1996 13:46:03 -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 NAA26472; Thu, 8 Aug 1996 13:45:36 -0700 (PDT) To: Jan Knepper <100626.3506@CompuServe.COM> cc: "[FreeBSD current]" Subject: Re: Matrox Millennium In-reply-to: Your message of "08 Aug 1996 16:37:49 EDT." <960808203748_100626.3506_BHL159-1@CompuServe.COM> Date: Thu, 08 Aug 1996 13:45:36 -0700 Message-ID: <26469.839537136@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Buy AccelleratedX. http://www.xinside.com Jordan > Hi, > > > I tried to setup XFree86 on FreeBSd 2.1.0 and got into a few problems because my > system has a Matrox Video adapter. > SuperProbe returns an Oak chipset with 64K. Since there is 2 MB on the card I > don't think that is a good choice. > > Thanks in advance for any help. > > Don't worry, be Kneppie, > Jan > From owner-freebsd-current Thu Aug 8 14:10:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13109 for current-outgoing; Thu, 8 Aug 1996 14:10:50 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA13099 for ; Thu, 8 Aug 1996 14:10:44 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id RAA05060; Thu, 8 Aug 1996 17:10:13 -0400 (EDT) Date: Thu, 8 Aug 1996 17:10:13 -0400 (EDT) From: Gary Roberts To: Jan Knepper <100626.3506@CompuServe.COM> cc: "[FreeBSD current]" Subject: Re: Matrox Millennium In-Reply-To: <960808203748_100626.3506_BHL159-1@CompuServe.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 8 Aug 1996, Jan Knepper wrote: > Hi, > > > I tried to setup XFree86 on FreeBSd 2.1.0 and got into a few problems because my > system has a Matrox Video adapter. > SuperProbe returns an Oak chipset with 64K. Since there is 2 MB on the card I > don't think that is a good choice. > > Thanks in advance for any help. > > Don't worry, be Kneppie, > Jan > > I might be wrong, but the Matrox Millieum uses WRAM, meaning Windows Ram. It's not a stadard card that uses the orignal DRAM etc. That may be a problem, I dunno. Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages ------------------------------------------------------------------------------ This email message is copyrighted and is not allowed to be duplicated, reproduced, or even seen on the MSN network. From owner-freebsd-current Thu Aug 8 15:02:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18119 for current-outgoing; Thu, 8 Aug 1996 15:02:13 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18097 for ; Thu, 8 Aug 1996 15:02:02 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id QAA05596 for ; Thu, 8 Aug 1996 16:01:14 -0600 (MDT) Message-Id: <199608082201.QAA05596@rover.village.org> Subject: Re: How much space for CVS tree? To: current@FreeBSD.org In-reply-to: Your message of Wed, 07 Aug 1996 21:59:53 +0200 Date: Thu, 08 Aug 1996 16:01:14 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Ollivier ROBERT writes: : According to Warner Losh: : > The CVS tree is about 230M. The sources checked out are about 210M. : > The obj tree escapes me at the moment, but either 100M or 150M sticks : > in my head. : : About 93 MB now without profiled libs. I must have done the du with profiled libs then :-(. Warner From owner-freebsd-current Thu Aug 8 15:07:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18862 for current-outgoing; Thu, 8 Aug 1996 15:07:44 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18856 for ; Thu, 8 Aug 1996 15:07:40 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id QAA05623; Thu, 8 Aug 1996 16:05:30 -0600 (MDT) Message-Id: <199608082205.QAA05623@rover.village.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: exploitable security risk Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users) In-reply-to: Your message of Thu, 08 Aug 1996 08:19:40 +0200 Date: Thu, 08 Aug 1996 16:05:29 -0600 From: Warner Losh Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You might want to look at the OpenBSD CVS tree. They have been fixing a whole boatload of "oflow" cases in the BSD sources. I don't know if all of them are exploitable security holes or not, but they are likely bugs and should likely be looked at. Warner From owner-freebsd-current Thu Aug 8 16:33:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24025 for current-outgoing; Thu, 8 Aug 1996 16:33:03 -0700 (PDT) Received: from Gatekeeper.Lamb.net (root@Gatekeeper.Lamb.net [206.169.44.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA24020 for ; Thu, 8 Aug 1996 16:33:01 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.Lamb.net (8.7.5/8.7.3) id QAA07478; Thu, 8 Aug 1996 16:33:14 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199608082333.QAA07478@Gatekeeper.Lamb.net> Subject: Re: Matrox Millennium To: 100626.3506@CompuServe.COM (Jan Knepper) Date: Thu, 8 Aug 1996 16:33:14 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <960808203748_100626.3506_BHL159-1@CompuServe.COM> from Jan Knepper at "Aug 8, 96 04:37:49 pm" X-Mailer: ELM [version 2.4ME+ PL22 (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 > Hi, > > > I tried to setup XFree86 on FreeBSd 2.1.0 and got into a few problems because my > system has a Matrox Video adapter. > SuperProbe returns an Oak chipset with 64K. Since there is 2 MB on the card I > don't think that is a good choice. > > Thanks in advance for any help. > > Don't worry, be Kneppie, > Jan > > Matrox doesn't give programming information without NDA (Non Disclosure Aggrement). Because of this XFree86 can't support the Matrox Millenium card. You will need to get a different card or AcceleratedX from Xinside (http://www.xinside.com). Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 Lamb Art Internet Services || http://www.Lamb.net/ From owner-freebsd-current Thu Aug 8 16:55:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25624 for current-outgoing; Thu, 8 Aug 1996 16:55:21 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA25614 for ; Thu, 8 Aug 1996 16:55:18 -0700 (PDT) Received: from localhost (kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) with SMTP id TAA05318; Thu, 8 Aug 1996 19:55:17 -0400 (EDT) X-Authentication-Warning: moonpie.w8hd.org: kimc owned process doing -bs Date: Thu, 8 Aug 1996 19:55:16 -0400 (EDT) From: Kim Culhan To: current@FreeBSD.org cc: Jan Knepper <100626.3506@CompuServe.COM> Subject: Re: Matrox Millennium In-Reply-To: <199608082333.QAA07478@Gatekeeper.Lamb.net> 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, 8 Aug 1996, Ulf Zimmermann wrote: > Matrox doesn't give programming information without NDA > (Non Disclosure Aggrement). Because of this XFree86 can't support the > Matrox Millenium card. You will > need to get a different card or AcceleratedX from Xinside > (http://www.xinside.com). The Millenium + Xinside on FreeBSD is an excellent combination, no problems. kim -- kimc@w8hd.org From owner-freebsd-current Thu Aug 8 18:20:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29224 for current-outgoing; Thu, 8 Aug 1996 18:20:55 -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 SAA29212 for ; Thu, 8 Aug 1996 18:20:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id DAA16687 for ; Fri, 9 Aug 1996 03:20:49 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id DAA13080 for freebsd-current@FreeBSD.org; Fri, 9 Aug 1996 03:20:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA02152 for freebsd-current@FreeBSD.org; Thu, 8 Aug 1996 22:25:21 +0200 (MET DST) From: J Wunsch Message-Id: <199608082025.WAA02152@uriah.heep.sax.de> Subject: Re: Automatic maintenance of local variants of FreeBSD sources To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 8 Aug 1996 22:25:21 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608071607.SAA07123@vector.jhs.no_domain> from "Julian H. Stacey" at "Aug 7, 96 06:07:31 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 Julian H. Stacey wrote: > Ref. Automatic maintenance of local variants of distribution sources: > > I have many local patches, so I automated local maintenance, Here's how: I have many local patches, so I automated local maintenance, here's how: cvs -q update -Pd :-) -- 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 Aug 8 21:53:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07028 for current-outgoing; Thu, 8 Aug 1996 21:53:17 -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 VAA07021 for ; Thu, 8 Aug 1996 21:53:10 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA21823 for current@freebsd.org; Fri, 9 Aug 1996 00:53:06 -0400 From: Bill Paul Message-Id: <199608090453.AAA21823@skynet.ctr.columbia.edu> Subject: wd.c/ATAPI patch -- testers wanted To: current@freebsd.org Date: Fri, 9 Aug 1996 00:53:05 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tonight I blew a few hours playing with the ATAPI support. The result was the small patch appended to this message, which seems to make the detection of ATAPI devices happen much more reliably. This patch is for 2.2-current. The machine I used for testing is a Gateway 2000 Pentium 200 Mhz with 64MB or RAM, 2.5GB Western Digital IDE disk drive, Toshiba 8x ATAPI/IDE CD-ROM drive, primary and secondary PCI-based on-board IDE controllers. (Default configuration is IDE hard disk as only disk on primary controller and CD-ROM as master on secondary controller.) The problems I had with this system were as follows: - The kernel fails to find the ATAPI CD-ROM drive when it's jumpered as the master device on the secondary controller. Windoze NT is able to handle this configuration with no trouble. - With the GENERIC configuration and the drive jumpered as the slave on the secondary controller, the kernel finds the drive but it also finds a phantom wd2. This hoses sysinstall when booting from the installation floppy (it attempts to open the phantom drive and wedges). In the first case, the problem is that wdprobe() decides that there is no wdc1 controller because the code near the end which checks the error status of the drives bails out incorrectly. The comments say that some controllers return 0x81 and then, when the DRV bit is set, they return 0x01 later. In my case, the check returns 0x81 both times. The comments also say that 0x81 means drive 0 okay and drive 1 failed. This is more or less correct (we have a master drive and no slave), but the code bails out unless it gets 0x01 again. My fix was to honor the second 0x81 as a valid response. This was a one line change. In the second case, the problem is in the wgetctlr(). It checks wd_status (among other things) in search of a WDSC_READY state. It turns out that with my hardware, the controller will bogusly return WDSC_READY on the empty master slot when the CD-ROM is jumpered as a slave. If you check wd_status a second time, a different value is returned. My fix was to read the wd_status location once and discard the value before reading it again as part of the actual test. I'm not really sure about this one but it seems to do the job. With these two small changes, I was able to get the CD-ROM detected reliably in a number of different hardware configurations: - master on secondary controller with another IDE disk as slave - slave as secondary controller with another IDE disk as master - master on secondary controller alone - slave on second controller alone - only drive on secondary controller (no jumper in either master or slave position) - slave on primary controller with another IDE disk as master - master on primary controller with another IDE disk as slave I couldn't really check the CD-ROM on the primary controller alone since then I wouldn't have a boot disk. I would also have liked to test the drive with a different controller, but I didn't have one handy that I could configure for the secondary address and IRQ. I'd like some people who have IDE/ATAPI CD-ROMs exhibiting similar problems to test this patch to see if it makes any difference. Since I need this to make my machines work right, I'll be committing this to -current eventually if nobody offers any objections. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= *** wd.c.old Sat Jul 27 15:01:10 1996 --- wd.c Thu Aug 8 23:01:00 1996 *************** *** 410,417 **** /* Get status for drive 1 */ du->dk_error = inb(du->dk_port + wd_error); /* printf("Error (drv 1) : %x\n", du->dk_error); */ ! ! if(du->dk_error != 0x01) goto nodevice; } else /* drive 0 fail */ goto nodevice; --- 410,421 ---- /* Get status for drive 1 */ du->dk_error = inb(du->dk_port + wd_error); /* printf("Error (drv 1) : %x\n", du->dk_error); */ ! /* ! * Sometimes (apparently mostly with ATAPI ! * drives involved) 0x81 really means 0x81 ! * (drive 0 OK, drive 1 failed). ! */ ! if(du->dk_error != 0x01 && du->dk_error != 0x81) goto nodevice; } else /* drive 0 fail */ goto nodevice; *************** *** 1520,1525 **** --- 1524,1533 ---- return (1); outb(du->dk_port + wd_sdh, WDSD_IBM | (du->dk_unit << 4)); DELAY(5000); /* usually unnecessary; drive select is fast */ + /* + * Do this twice: may get a false WDCS_READY the first time. + */ + inb(du->dk_port + wd_status); if ((inb(du->dk_port + wd_status) & (WDCS_BUSY | WDCS_READY)) != WDCS_READY || wdcommand(du, 0, 0, 0, 0, WDCC_RESTORE | WD_STEP) != 0 From owner-freebsd-current Thu Aug 8 22:06:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08201 for current-outgoing; Thu, 8 Aug 1996 22:06:41 -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 WAA08159 for ; Thu, 8 Aug 1996 22:06:33 -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 HAA32288 for ; Fri, 9 Aug 1996 07:06:22 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id HAA01893 for freebsd-current@freebsd.org; Fri, 9 Aug 1996 07:05:56 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id GAA00939; Fri, 9 Aug 1996 06:54:43 +0200 (MET DST) Message-Id: <199608090454.GAA00939@keltia.freenix.fr> Date: Fri, 9 Aug 1996 06:54:43 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: exploitable security risk In-Reply-To: <199608082205.QAA05623@rover.village.org>; from Warner Losh on Aug 8, 1996 16:05:29 -0600 References: <199608082205.QAA05623@rover.village.org> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Warner Losh: > You might want to look at the OpenBSD CVS tree. They have been fixing > a whole boatload of "oflow" cases in the BSD sources. I don't know if > all of them are exploitable security holes or not, but they are likely > bugs and should likely be looked at. It is a pity Theo doesn't want to talk about precisely what he fixed. ONe has to go digging in the CVS tree to find the fixes... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Thu Aug 8 22:48:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12922 for current-outgoing; Thu, 8 Aug 1996 22:48:36 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12917 for ; Thu, 8 Aug 1996 22:48:30 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id WAA02145; Thu, 8 Aug 1996 22:00:21 -0400 (EDT) Date: Thu, 8 Aug 1996 22:00:19 -0400 (EDT) From: "Charles C. Figueiredo" To: Ollivier Robert cc: FreeBSD-current users Subject: Re: exploitable security risk In-Reply-To: <199608090454.GAA00939@keltia.freenix.fr> 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 Fri, 9 Aug 1996, Ollivier Robert wrote: > According to Warner Losh: > > You might want to look at the OpenBSD CVS tree. They have been fixing > > a whole boatload of "oflow" cases in the BSD sources. I don't know if > > all of them are exploitable security holes or not, but they are likely > > bugs and should likely be looked at. > > It is a pity Theo doesn't want to talk about precisely what he fixed. ONe > has to go digging in the CVS tree to find the fixes... > -- > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 > To my knowledge, Theo hasn't been the one mainly doing a lot of security patches, a few others I know have. As for finding assorted bugs like these and other types, I have scripts that run through the source tree and produce 50MB and bigger files of stuff that needs to be cleaned up. :) Charles ------------------------------------------------------------------------------ Charles C. Figueiredo CCF13 marxx@doomsday.org ------------------------------------------------------------------------------ From owner-freebsd-current Thu Aug 8 23:39:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA15771 for current-outgoing; Thu, 8 Aug 1996 23:39: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 ESMTP id XAA15758 for ; Thu, 8 Aug 1996 23:39:05 -0700 (PDT) Received: from tippy2.vnet.net (tippy2.vnet.net [166.82.197.240]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id XAA03243 for ; Thu, 8 Aug 1996 23:39:02 -0700 (PDT) Received: from localhost (cmadison@localhost) by tippy2.vnet.net (8.7.5/8.6.9) with SMTP id CAA04067 for ; Fri, 9 Aug 1996 02:37:51 -0400 (EDT) Date: Fri, 9 Aug 1996 02:37:51 -0400 (EDT) From: Chris Madison To: current@freebsd.org Subject: ftpd won't allow login Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm running -current with 2065 as the latest delta applied. I had a user tell me that he could not login via ftp, but could telnet in just fine. So I tried it with my account....I can telnet in fine, but when I ftp in, ftp chokes on the password saying: Password: 530 Login incorrect. ftp: Login failed. I know for sure I typed in the correct password....I tried it many times. I'm not running anything special in the way of ftpds, just the plain vanilla one that comes with fbsd. Is this a known problem and corrected with a new delta???????? Or is my system about to die some strange death:'( Thanx Chris From owner-freebsd-current Fri Aug 9 00:41:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA20063 for current-outgoing; Fri, 9 Aug 1996 00:41:39 -0700 (PDT) Received: from orion.stationsoft.fr ([194.133.26.37]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA20056 for ; Fri, 9 Aug 1996 00:41:34 -0700 (PDT) Received: (from bob2@localhost) by orion.stationsoft.fr (8.7.5/8.7.3) id JAA11298; Fri, 9 Aug 1996 09:47:07 GMT Date: Fri, 9 Aug 1996 09:47:07 GMT Message-Id: <199608090947.JAA11298@orion.stationsoft.fr> From: Jean-Pierre Forcioli To: cmadison@tippy2.vnet.net CC: current@freebsd.org In-reply-to: (message from Chris Madison on Fri, 9 Aug 1996 02:37:51 -0400 (EDT)) Subject: Re: ftpd won't allow login Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does your login shell belong to the file "/etc/shells" ? For further detail see ftpd(8) and getusershell(3). Chris Madison wrotes : >> Hello, >> >> I'm running -current with 2065 as the latest delta applied. >> >> I had a user tell me that he could not login via ftp, but could >> telnet in just fine. So I tried it with my account....I can telnet >> in fine, but when I ftp in, ftp chokes on the password saying: >> >> Password: >> 530 Login incorrect. >> ftp: Login failed. >> >> I know for sure I typed in the correct password....I tried it >> many times. >> >> I'm not running anything special in the way of ftpds, just the >> plain vanilla one that comes with fbsd. >> >> Is this a known problem and corrected with a new delta???????? >> Or is my system about to die some strange death:'( >> >> Thanx >> Chris -- +---------------------------------------------------+ Jean-Pierre Forcioli bob2@orion.stationsoft.fr bob2@bocal.cs.univ-paris8.fr +---------------------------------------------------+ From owner-freebsd-current Fri Aug 9 00:49:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA20303 for current-outgoing; Fri, 9 Aug 1996 00:49:24 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA20298; Fri, 9 Aug 1996 00:49:22 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id JAA10586; Fri, 9 Aug 1996 09:48:34 +0200 (MET DST) To: Chris Madison cc: current@freebsd.org Subject: Re: ftpd won't allow login In-reply-to: Your message of "Fri, 09 Aug 1996 02:37:51 EDT." Date: Fri, 09 Aug 1996 09:48:34 +0200 Message-ID: <10584.839576914@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , Chris Mad ison writes: > >Hello, > >I'm running -current with 2065 as the latest delta applied. > >I had a user tell me that he could not login via ftp, but could >telnet in just fine. So I tried it with my account....I can telnet >in fine, but when I ftp in, ftp chokes on the password saying: > >Password: >530 Login incorrect. >ftp: Login failed. This was fixed a couple of days ago. -- 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 Aug 9 01:11:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21334 for current-outgoing; Fri, 9 Aug 1996 01:11:37 -0700 (PDT) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA21329 for ; Fri, 9 Aug 1996 01:11:34 -0700 (PDT) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id RAA24106; Fri, 9 Aug 1996 17:11:09 +0900 Date: Fri, 9 Aug 1996 17:11:09 +0900 Message-Id: <199608090811.RAA24106@frig.mt.cs.keio.ac.jp> To: cmadison@tippy2.vnet.net Cc: current@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: ftpd won't allow login In-Reply-To: Your message of Fri, 9 Aug 1996 02:37:51 -0400 (EDT). From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article cmadison@tippy2.vnet.net writes: >> I had a user tell me that he could not login via ftp, but could >> telnet in just fine. So I tried it with my account....I can telnet >> in fine, but when I ftp in, ftp chokes on the password saying: Allowing 'ftp' user's telnet login can be security hole in some cases. For example, if somebody can put .rhost in your ~ftp directory, the intruders can login your machine without password authentication. It can't be a security hole when the host is configured carefully, but it turns to be security hole when the host is carelessly misconfugred. Were not for special reasons, I don't recommend you to allow ftp user's login. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-current Fri Aug 9 01:14:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21483 for current-outgoing; Fri, 9 Aug 1996 01:14:53 -0700 (PDT) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA21477 for ; Fri, 9 Aug 1996 01:14:49 -0700 (PDT) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id RAA24138; Fri, 9 Aug 1996 17:14:43 +0900 Date: Fri, 9 Aug 1996 17:14:43 +0900 Message-Id: <199608090814.RAA24138@frig.mt.cs.keio.ac.jp> To: hosokawa@mt.cs.keio.ac.jp Cc: cmadison@tippy2.vnet.net, current@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: ftpd won't allow login In-Reply-To: Your message of Fri, 9 Aug 1996 17:11:09 +0900. <199608090811.RAA24106@frig.mt.cs.keio.ac.jp> From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry I misunderstood your question! Add your shells to /etc/shells. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-current Fri Aug 9 02:33:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA26872 for current-outgoing; Fri, 9 Aug 1996 02:33:08 -0700 (PDT) Received: from lespoir.apana.org.au (lespoir.apana.org.au [202.12.87.57]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA26848; Fri, 9 Aug 1996 02:32:56 -0700 (PDT) Received: (from wongm@localhost) by lespoir.apana.org.au (8.6.12/8.6.6) id TAA11947; Fri, 9 Aug 1996 19:09:25 GMT Date: Fri, 9 Aug 1996 19:09:19 +0000 () From: "M.C Wong" To: Charles Green cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Willows support for freebsd In-Reply-To: <199608071304.JAA04106@filitov.isf.rl.af.mil> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know if the Linux version of the Willows toolkit works under FreeBSD running Linux emulation ? From owner-freebsd-current Fri Aug 9 02:40:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27285 for current-outgoing; Fri, 9 Aug 1996 02:40:55 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA27278; Fri, 9 Aug 1996 02:40:46 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA09985; Fri, 9 Aug 1996 11:39:13 +0200 Message-Id: <199608090939.LAA09985@ra.dkuug.dk> Subject: Re: Willows support for freebsd To: wongm@lespoir.apana.org.au (M.C Wong) Date: Fri, 9 Aug 1996 11:39:12 +0200 (MET DST) Cc: green@filitov.isf.rl.af.mil, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "M.C Wong" at Aug 9, 96 07:09:19 pm From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to M.C Wong who wrote: > > Does anyone know if the Linux version of the Willows toolkit works under > FreeBSD running Linux emulation ? > For the ten'th time this week, NO, and it is not trivial to make it work, belive me. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Fri Aug 9 03:43:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA01114 for current-outgoing; Fri, 9 Aug 1996 03:43:11 -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 DAA01108; Fri, 9 Aug 1996 03:43:06 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id UAA03351; Fri, 9 Aug 1996 20:25:48 +0930 From: Michael Smith Message-Id: <199608091055.UAA03351@genesis.atrad.adelaide.edu.au> Subject: Re: Willows support for freebsd To: wongm@lespoir.apana.org.au (M.C Wong) Date: Fri, 9 Aug 1996 20:25:48 +0930 (CST) Cc: green@filitov.isf.rl.af.mil, hackers@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "M.C Wong" at Aug 9, 96 07:09:19 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 M.C Wong stands accused of saying: > > > Does anyone know if the Linux version of the Willows toolkit works under > FreeBSD running Linux emulation ? For the Nth time, No. It does not, cannot, and will not. -- ]] 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 Aug 9 05:57:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA06689 for current-outgoing; Fri, 9 Aug 1996 05:57:29 -0700 (PDT) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA06684; Fri, 9 Aug 1996 05:57:27 -0700 (PDT) Received: (from chuck@localhost) by fang.cs.sunyit.edu (8.6.9/8.6.9) id IAA27184; Fri, 9 Aug 1996 08:57:25 -0400 Date: Fri, 9 Aug 1996 08:57:25 -0400 From: Charles Green Message-Id: <199608091257.IAA27184@fang.cs.sunyit.edu> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: hackers@freebsd.org, current@freebsd.org Subject: Willows xwin for FreeBSD Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk With all the talk of willows on the list and their recent price hike I e-mailed Willows and asked them about just marketing the windows emulator (at a reasonable price, less than $100), here's what they had to say... "While MANY people are using a component of our developer's toolkit as a binary emulator, we feel it falls short of being considered of commercial grade (no 32-bit support, slower performance than we'd like), so we have not decided to release the binary emulator (xwin) as a standalone product. We make it available freely from www.willows.com, with a built in 30-45 day license key. As we solidify our plans for releasing it as a product, we may remove the free version from our web site, and may make the next generation available as a stand-alone product." It could happen... -- Charles Green, PRC Inc. Rome Laboratory, NY From owner-freebsd-current Fri Aug 9 08:07:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA18259 for current-outgoing; Fri, 9 Aug 1996 08:07:41 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA18253 for ; Fri, 9 Aug 1996 08:07:37 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id LAA04187 for freebsd-current@freebsd.org; Fri, 9 Aug 1996 11:07:28 -0400 (EDT) From: Charles Henrich Message-Id: <199608091507.LAA04187@crh.cl.msu.edu> Subject: 2.2-960801-SNAP vs 2-2.960612-SNAP To: freebsd-current@freebsd.org Date: Fri, 9 Aug 1996 11:07:28 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL22 (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 Okay, here's the situation, I run maplay1.3 (yes I know I should make a port of it), continously in the background playing tunes that I've mpeg'd. Anyway, on my PP200 w/ 0612-SNAP the maplay process would never be starved for I/O (Adaptec 2940) or processor time, and as such could play songs without any glitches or interuptions. On 0801-SNAP I get constant glitches whenever something else starts up (such as netscape, or a xloadimage fires off). Any ideas what could have changed that would be doing this effect, and what I could change back to fix it? :) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Fri Aug 9 10:44:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26405 for current-outgoing; Fri, 9 Aug 1996 10:44:50 -0700 (PDT) Received: from tippy2.vnet.net (tippy2.vnet.net [166.82.197.240]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26397 for ; Fri, 9 Aug 1996 10:44:46 -0700 (PDT) Received: from localhost (cmadison@localhost) by tippy2.vnet.net (8.7.5/8.6.9) with SMTP id NAA00672 for ; Fri, 9 Aug 1996 13:45:10 -0400 (EDT) Date: Fri, 9 Aug 1996 13:45:10 -0400 (EDT) From: Chris Madison To: current@freebsd.org Subject: Re: ftpd won't allow login In-Reply-To: <10584.839576914@critter.tfs.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 Thanks for all the answers! Problem was resolved:-) l8r chris From owner-freebsd-current Fri Aug 9 13:24:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA01764 for current-outgoing; Fri, 9 Aug 1996 13:24:32 -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 ESMTP id NAA01712 for ; Fri, 9 Aug 1996 13:24:22 -0700 (PDT) From: sthaug@nethelp.no Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id MAA01047 for ; Fri, 9 Aug 1996 12:49:09 -0700 (PDT) Received: (qmail-queue invoked from smtpd); 9 Aug 1996 19:47:21 +0000 (GMT) Received: from localhost (HELO verdi.nethelp.no) (@127.0.0.1) by localhost with SMTP; 9 Aug 1996 19:47:21 +0000 (GMT) To: wpaul@skynet.ctr.columbia.edu Cc: current@freebsd.org Subject: Re: wd.c/ATAPI patch -- testers wanted In-Reply-To: Your message of "Fri, 9 Aug 1996 00:53:05 -0400 (EDT)" References: <199608090453.AAA21823@skynet.ctr.columbia.edu> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 09 Aug 1996 21:47:21 +0200 Message-ID: <9885.839620041@verdi.nethelp.no> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'd like some people who have IDE/ATAPI CD-ROMs exhibiting similar > problems to test this patch to see if it makes any difference. Since > I need this to make my machines work right, I'll be committing this > to -current eventually if nobody offers any objections. I can confirm that this patch made my CDROM player (Toshiba XM-5302TA/0305, according to the bootup message) work again. It was not recognized at all in the 960612 SNAP (but had worked in an earlier SNAP). I applied this patch to the 960612 SNAP, and now the CDROM player is recog- nized, and things work just fine. Thanks! Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Fri Aug 9 13:24:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA01818 for current-outgoing; Fri, 9 Aug 1996 13:24:44 -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 ESMTP id NAA01786 for ; Fri, 9 Aug 1996 13:24:36 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id MAA01051 for ; Fri, 9 Aug 1996 12:49:54 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA28537; Fri, 9 Aug 1996 12:47:27 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma028535; Fri Aug 9 12:47:14 1996 Message-ID: <320B9598.31DFF4F5@whistle.com> Date: Fri, 09 Aug 1996 12:46:32 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Chris Madison CC: current@freebsd.org Subject: Re: ftpd won't allow login References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Madison wrote: > I had the same problem... ftpd was looking for DES passwords but everything else was using MD5 > Hello > > I'm running -current with 2065 as the latest delta applied. > > I had a user tell me that he could not login via ftp, but could > telnet in just fine. So I tried it with my account....I can telnet > in fine, but when I ftp in, ftp chokes on the password saying: > > Password: > 530 Login incorrect. > ftp: Login failed. > > I know for sure I typed in the correct password....I tried it > many times. > > I'm not running anything special in the way of ftpds, just the > plain vanilla one that comes with fbsd. > > Is this a known problem and corrected with a new delta???????? > Or is my system about to die some strange death:'( > > Thanx > Chris From owner-freebsd-current Fri Aug 9 13:27:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA02664 for current-outgoing; Fri, 9 Aug 1996 13:27:55 -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 ESMTP id NAA02637 for ; Fri, 9 Aug 1996 13:27:50 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id LAA00455 for ; Fri, 9 Aug 1996 11:06:04 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA19122; Fri, 9 Aug 1996 11:00:59 -0700 From: Terry Lambert Message-Id: <199608091800.LAA19122@phaeton.artisoft.com> Subject: Re: exploitable security risk To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Fri, 9 Aug 1996 11:00:58 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <199608090454.GAA00939@keltia.freenix.fr> from "Ollivier Robert" at Aug 9, 96 06:54:43 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 > > You might want to look at the OpenBSD CVS tree. They have been fixing > > a whole boatload of "oflow" cases in the BSD sources. I don't know if > > all of them are exploitable security holes or not, but they are likely > > bugs and should likely be looked at. > > It is a pity Theo doesn't want to talk about precisely what he fixed. ONe > has to go digging in the CVS tree to find the fixes... With respect, it is my impression that talking about (and being put in the position of having to justify) the patches would seriously detract from the amount of time he could spend on forward progress. I'm sure it has been tempting for many of us to come out with something like "OllivierBSD" or "TerryBSD" for similar reasons. OpenBSD seems to have a sufficient critical mass of people that they can hack enough code that they wouldn't fall behind by actually going off on their own. I think this is one of several obvious (and unvoiced) reasons for the split. The blame is given to the events which are reactions to the frustrations; the causes of the frustrations were/are never discussed. 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 Fri Aug 9 13:42:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04691 for current-outgoing; Fri, 9 Aug 1996 13:42:34 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA04681 for ; Fri, 9 Aug 1996 13:42:29 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id PAA11458 for current@freebsd.org; Fri, 9 Aug 1996 15:42:23 -0500 (CDT) Message-Id: <199608092042.PAA11458@utgard.bga.com> Subject: Praise for CVSup To: current@freebsd.org Date: Fri, 9 Aug 1996 15:42:23 -0459 (CDT) From: "Boyd R. Faulkner" X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Blessed be CVSup. Verily, I have used it and my povray problem hath fled in haste. It is much faster, of course, and I can make pretty pictures again. Thanks, Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Fri Aug 9 14:21:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08306 for current-outgoing; Fri, 9 Aug 1996 14:21:11 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA08295 for ; Fri, 9 Aug 1996 14:21:08 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id OAA22859; Fri, 9 Aug 1996 14:20:58 -0700 (PDT) Message-Id: <199608092120.OAA22859@austin.polstra.com> To: nate@mt.sri.com Cc: freebsd-current@freebsd.org, phk@critter.tfs.com Subject: Re: Whither gcc 2.7? In-reply-to: <199608071916.NAA02626@rocky.mt.sri.com> Date: Fri, 09 Aug 1996 14:20:58 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate wrote: > I *really* want to keep SUP around until the next major release, > just to make sure CVSup gets shaken out better. No offense to John ... Don't worry, John feels the same way! CVSup is only in beta release. I am not worried about it giving anybody corrupted files. It verifies the MD5 checksum of each edited file before moving it into place on the client. But there still could be bugs that could cause, say, some files to be omitted incorrectly. (I don't think there are such bugs. I'm just giving an example of the kind of problem that checksums wouldn't detect.) Also, as we saw this week when the RCS files in src/bin/ed/test got totally spammed (by a bad disk controller, apparently), there are still a few really pathological conditions that can cause the server to give up rather ungracefully. That sort of thing doesn't corrupt anybody's files, but it does interrupt service until the server bug or the repository problem is fixed. I would dearly love to see CVSup replace sup, ultimately. But it's not time for that yet. > ... but I trust SUP and although CVSup is great and all, I still do a > SUP once/week to 'make sure' everything is hunky-dorey. Wimp! ;-) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Fri Aug 9 14:31:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09152 for current-outgoing; Fri, 9 Aug 1996 14:31:02 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09141 for ; Fri, 9 Aug 1996 14:30:57 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id PAA11120 for ; Fri, 9 Aug 1996 15:30:53 -0600 (MDT) Message-Id: <199608092130.PAA11120@rover.village.org> Subject: Re: exploitable security risk To: freebsd-current@freebsd.org (FreeBSD-current users) In-reply-to: Your message of Fri, 09 Aug 1996 06:54:43 +0200 Date: Fri, 09 Aug 1996 15:30:53 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ollivier ROBERT writes: : It is a pity Theo doesn't want to talk about precisely what he : fixed. ONe has to go digging in the CVS tree to find the fixes... The audit trail is in the CVS files, available via anoncvs for those that have the time to follow. Since FreeBSD and OpenBSD have not merged is better than what the situtation could be, but less than what would be in an ideal world. Warner From owner-freebsd-current Fri Aug 9 15:55:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15467 for current-outgoing; Fri, 9 Aug 1996 15:55:47 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA15460 for ; Fri, 9 Aug 1996 15:55:43 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id RAA11770; Fri, 9 Aug 1996 17:55:18 -0500 (CDT) Message-Id: <199608092255.RAA11770@utgard.bga.com> Subject: Re: Whither gcc 2.7? To: jdp@polstra.com (John Polstra) Date: Fri, 9 Aug 1996 17:55:18 -0459 (CDT) From: "Boyd R. Faulkner" Cc: nate@mt.sri.com, freebsd-current@FreeBSD.org, phk@critter.tfs.com In-Reply-To: <199608092120.OAA22859@austin.polstra.com> from "John Polstra" at Aug 9, 96 02:20:41 pm X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to John Polstra: > > > Nate wrote: > > > I *really* want to keep SUP around until the next major release, > > just to make sure CVSup gets shaken out better. No offense to John ... > > Don't worry, John feels the same way! CVSup is only in beta release. > Stuff omitted. > I would dearly love to see CVSup replace sup, ultimately. But it's not > time for that yet. > > > ... but I trust SUP and although CVSup is great and all, I still do a > > SUP once/week to 'make sure' everything is hunky-dorey. Maybe, but CVSup fixed something in my tree that sup wouldn't fix. I'm not sure that sup assures joy. Perhaps a combination does. I figure I will hang with it until it proves itself false. > > Wimp! ;-) > > -- > John Polstra jdp@polstra.com Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Fri Aug 9 17:57:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21944 for current-outgoing; Fri, 9 Aug 1996 17:57:11 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21935 for ; Fri, 9 Aug 1996 17:57:08 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id RAA24189; Fri, 9 Aug 1996 17:56:56 -0700 (PDT) Message-Id: <199608100056.RAA24189@austin.polstra.com> To: faulkner@asgard.bga.com Cc: current@FreeBSD.org Subject: Re: Praise for CVSup In-reply-to: <199608092255.RAA11770@utgard.bga.com> Date: Fri, 09 Aug 1996 17:56:55 -0700 From: John Polstra Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Blessed be CVSup. Verily, I have used it and my povray problem > hath fled in haste. Praise is always welcome, of course, but ... I don't understand. You're not implying that CVSup fixed povray, are you? I was just _sure_ I had taken out the experimental "auto-fix-bugs" feature before I made the public release. :-) I wouldn't even ask this, but you said in a different posting that CVSup had "fixed something in my tree that sup wouldn't fix." It's sort of hard for me to imagine what that might be. If you ignore the details, they both do the same thing. Namely, they find files that are different on the client and server, and make them the same. Can you give us some details about what you're referring to? Thanks, John From owner-freebsd-current Fri Aug 9 18:12:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22642 for current-outgoing; Fri, 9 Aug 1996 18:12:21 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22637 for ; Fri, 9 Aug 1996 18:12:16 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id UAA14116; Fri, 9 Aug 1996 20:12:05 -0459 (CDT) Message-Id: <199608100111.UAA14116@utgard.bga.com> Subject: Re: Praise for CVSup To: jdp@polstra.com (John Polstra) Date: Fri, 9 Aug 1996 20:12:05 -0459 (CDT) From: "Boyd R. Faulkner" Cc: current@FreeBSD.org In-Reply-To: <199608100056.RAA24189@austin.polstra.com> from "John Polstra" at Aug 9, 96 05:56:38 pm X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to John Polstra: > > > > Blessed be CVSup. Verily, I have used it and my povray problem > > hath fled in haste. > > Praise is always welcome, of course, but ... I don't understand. > You're not implying that CVSup fixed povray, are you? I was just > _sure_ I had taken out the experimental "auto-fix-bugs" feature > before I made the public release. :-) Check again. > > I wouldn't even ask this, but you said in a different posting that > CVSup had "fixed something in my tree that sup wouldn't fix." It's > sort of hard for me to imagine what that might be. If you ignore > the details, they both do the same thing. Namely, they find files > that are different on the client and server, and make them the > same. > > Can you give us some details about what you're referring to? > Actually, I am. CVSup does more file checking than sup does. You can end up with files with the right date and size but not the right contents and, while I may be wrong, sup will not detect this. Since CVSup uses MD5 (yes?) to ID the files, you are gurarnteed the correct contents. I was blowing my tree away and resupping pieces but I hadn't got very far. Whatever was bad is gone now. I can run povray without getting Floating point errors. I knew it was my tree because I had installed 2.1.5 on another drive in this box and povray had worked. Maybe I am wrong about how little checking sup does but I don't think so. Either way, it didn't work. Then it did. CVSup was the step inbetween. Thanks. Boyd > Thanks, > John > -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Fri Aug 9 19:00:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24077 for current-outgoing; Fri, 9 Aug 1996 19:00:25 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24072 for ; Fri, 9 Aug 1996 19:00:21 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id SAA24389; Fri, 9 Aug 1996 18:59:59 -0700 (PDT) Message-Id: <199608100159.SAA24389@austin.polstra.com> To: "Boyd R. Faulkner" cc: current@FreeBSD.org Subject: Re: Praise for CVSup In-reply-to: Your message of "Fri, 09 Aug 1996 20:12:05 -0459." <199608100111.UAA14116@utgard.bga.com> Date: Fri, 09 Aug 1996 18:59:59 -0700 From: John Polstra Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > CVSup does more file checking than sup does. You can end up with > files with the right date and size but not the right contents and, > while I may be wrong, sup will not detect this. Since CVSup uses > MD5 (yes?) to ID the files, you are gurarnteed the correct contents. Well ... yes and no. It depends on the situation. In general, CVSup does _not_ ID the files via MD5 checksums. It compares the time stamps between the client and the server, and if they are identical, it assumes that the files are identical too. In that case, it doesn't examine the files further. (There is an exception which, I conjecture, applies to your particular case. I'll explain that in a minute.) The reason it doesn't compare MD5 checksums for every file on the client and the server is that it would be too slow, too compute intensive, and too disk intensive. No real-time network file update package could do that, without bringing the server to its knees. It has to cull the unchanged files from the list using just the information that it can get from a call to stat(). The exception is when you are using CVSup's checkout mode the very first time. In that case, CVSup cannot ID your existing checked-out files via the time stamps, because the time stamps of the checked-out files are not the same as the time stamps of the corresponding RCS files on the server machine. So it really has no choice. On the client, it checksums each file. On the server, it parses each RCS file, and checksums each revision on the selected branch, from most recent to least recent. This is the worst situation, in terms of server load, but it's not as bad as it sounds. First, it's computing the checksums on the fly as it generates revisions -- not doing some gross thing like calling "co" to emit them to temporary files. So its main activity involves crunching through a memory-mapped RCS file, computing the checksums as it goes. Second, if the client already has files, they're probably fairly recent. So the server won't have to checksum very many revisions before it finds the right one. Third, this situation only happens the first time a given client uses CVSup in checkout mode. After that, the so-called "list files" remember which revisions the client possesses. The other place where MD5 checksums are used is to verify each file that CVSup has updated by editing in new deltas and so forth. That was inspired by CTM, with a few gentle prods from Justin Gibbs, and it has turned out to be a really good thing. Besides instilling confidence in CVSup, it permits it to be imperfect and incomplete in the way it deals with RCS files. I learned during the alpha test period that there is an enormous variety of truly sick things that people can and _will_ do to the RCS files in a CVS repository. If CVSup had to be perfect in anticipating every one of them, well, I wouldn't trust it myself. But with the checksum verification, it doesn't even have to handle the rarest kinds of changes properly at all. When those kinds of changes happen, it edits the file incorrectly, but finds out about it when it verifies the checksums. Then it says, "Checksum mismatch for foo -- will transfer entire file". At that point it leaves the file untouched, and it arranges to transfer the whole thing at the end of the run. It works well, and it helps keep people from getting mad at me. You may even see this happen the next time you run CVSup. Today I (needlessly, it turns out) changed the default RCS keyword expansion on one of the repository files for the "net/cvsup" port. That is one of the two or three kinds of very rare changes that CVSup's RCS file analysis currently does not cover. (The other one that comes to mind is changes in the list of locked revisions. Since CVS never locks its RCS files, it's not much of an issue.) -- John From owner-freebsd-current Fri Aug 9 19:09:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24390 for current-outgoing; Fri, 9 Aug 1996 19:09:54 -0700 (PDT) Received: from spooky.eis.net.au (root@spooky.eis.net.au [203.12.171.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24385 for ; Fri, 9 Aug 1996 19:09:45 -0700 (PDT) Received: (from ernie@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id MAA27674; Sat, 10 Aug 1996 12:07:14 +1000 (EST) From: Ernie Elu Message-Id: <199608100207.MAA27674@spooky.eis.net.au> Subject: Re: Praise for CVSup To: faulkner@asgard.bga.com (Boyd R. Faulkner) Date: Sat, 10 Aug 1996 12:07:13 +1000 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199608100111.UAA14116@utgard.bga.com> from "Boyd R. Faulkner" at "Aug 9, 96 08:12:05 pm" X-Mailer: ELM [version 2.4ME+ PL15 (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 > According to John Polstra: > > > > > > > Blessed be CVSup. Verily, I have used it and my povray problem > > > hath fled in haste. Well I thought I would install cvsup and after the port script downloaded 15MB of Modula-3 compiler across my 28.8K modem link it gave a checksum error :-( - Ernie. From owner-freebsd-current Fri Aug 9 19:37:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA25744 for current-outgoing; Fri, 9 Aug 1996 19:37:40 -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 TAA25738 for ; Fri, 9 Aug 1996 19:37:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA19886; Fri, 9 Aug 1996 19:32:23 -0700 From: Terry Lambert Message-Id: <199608100232.TAA19886@phaeton.artisoft.com> Subject: Re: Praise for CVSup To: jdp@polstra.com (John Polstra) Date: Fri, 9 Aug 1996 19:32:23 -0700 (MST) Cc: faulkner@asgard.bga.com, current@FreeBSD.org In-Reply-To: <199608100159.SAA24389@austin.polstra.com> from "John Polstra" at Aug 9, 96 06:59: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 > > CVSup does more file checking than sup does. You can end up with > > files with the right date and size but not the right contents and, > > while I may be wrong, sup will not detect this. Since CVSup uses > > MD5 (yes?) to ID the files, you are gurarnteed the correct contents. [ ... ] > The reason it doesn't compare MD5 checksums for every file on the client > and the server is that it would be too slow, too compute intensive, and > too disk intensive. No real-time network file update package could do > that, without bringing the server to its knees. It has to cull the > unchanged files from the list using just the information that it can get > from a call to stat(). [ ... ] > The exception is when you are using CVSup's checkout mode the very > first time. In that case, CVSup cannot ID your existing checked-out > files via the time stamps, because the time stamps of the checked-out > files are not the same as the time stamps of the corresponding RCS > files on the server machine. So it really has no choice. One operational difference is that the files on the local file system seem to get the server file system timestamp on them after a data transfer instead of a local modification time time stamp. Sup apparently is using the local time stamping implied by POSIX. The implication here is that if your local clock is skewed relative to the SUP server by more than the amount of time between the CVS time stamp and the SUP time local to the SUP server... then using SUP you could very well get screwed. I believe CVSup has the capability to screw you this way if you do local checkins, which would modify the time stamp to the local time. If you had a negative skew, even if CVSup were checking for equality instead of later than, then you could get screwed. The window there is teeny. If the CVSup looks for a "greater than" time stamp, and your modification in local time took place after the last modification in server time, and both you and the server side made modifications to the file, then you could also be really screwed (with a big window). I think it checks equality, doesn't it? In any case, that could explain the difference, and you could still have a race condition waiting to bite you on the butt. 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 Fri Aug 9 21:03:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA00381 for current-outgoing; Fri, 9 Aug 1996 21:03:08 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA00376 for ; Fri, 9 Aug 1996 21:03:06 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id VAA24795; Fri, 9 Aug 1996 21:01:37 -0700 (PDT) Message-Id: <199608100401.VAA24795@austin.polstra.com> To: Terry Lambert cc: faulkner@asgard.bga.com, current@FreeBSD.org Subject: Re: Praise for CVSup In-reply-to: Your message of "Fri, 09 Aug 1996 19:32:23 PDT." <199608100232.TAA19886@phaeton.artisoft.com> Date: Fri, 09 Aug 1996 21:01:36 -0700 From: John Polstra Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Terry wrote: > One operational difference is that the files on the local file > system seem to get the server file system timestamp on them after > a data transfer instead of a local modification time time stamp. > > Sup apparently is using the local time stamping implied by POSIX. I am a little hazy about what sup does, but it definitely seems to preserve the time stamps of the files it updates. I.e., it does a stat() on the server's version, and passes that time stamp to a utimes() call on the client side. Any possible client-server clock skew won't affect that. Where clock skew might be an issue for sup is in the "when.cvs" file. A single time stamp is stored there, representing the time when the last update for the collection occurred. They call it the "scan time", so I assume it is a time representing when the tree was examined. (The beginning of the scan? The end of the scan?) I looked into enough to know that the time stamp comes from the server's clock, but I don't know much more about it. > If the CVSup looks for a "greater than" time stamp, and your > modification in local time took place after the last modification > in server time, and both you and the server side made modifications > to the file, then you could also be really screwed (with a big > window). > > I think it checks equality, doesn't it? Yes, it checks for equality, for exactly the reason you described. I have thought about comparing file sizes, too. (In fact, I'm still thinking about it.) That would give a large added degree of safety. The disadvantage is the extra bytes needed to send the size for each file. I measured it recently. For a normal src + ports CVS tree, about 520 Kbytes (before compression) are sent from the client to the server to convey the filenames plus their time stamps. When I sent the file sizes too, it changed to around 620 K. (N.B., this is before the gzip compression; that reduces both numbers by about 65%.) Now, it turns out that, typically, the time for a CVSup run is dominated by exactly this transfer of file names and modification times. Normally, very few files need to be updated; most of the time and most of the bytes are spent in discovering that this is the case. Interestingly though, when I experimentally added the file sizes to the protocol, it didn't seem to change the elapsed time for doing a typical run. The time to do the tree walk on the server apparently was a bit greater than the time to send the information across the wire. (It was close, though.) However, this was with a 56 Kbit frame relay link. I worried that it would in fact make a noticeable difference over a slower link. What I think I might do is make it an option. Then the user can decide how to trade off paranoia against speed. -- John From owner-freebsd-current Fri Aug 9 21:24:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01789 for current-outgoing; Fri, 9 Aug 1996 21:24:28 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01783 for ; Fri, 9 Aug 1996 21:24:25 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id VAA24889; Fri, 9 Aug 1996 21:23:58 -0700 (PDT) Message-Id: <199608100423.VAA24889@austin.polstra.com> To: ernie@spooky.eis.net.au Cc: freebsd-current@freebsd.org Subject: Re: Praise for CVSup Date: Fri, 09 Aug 1996 21:23:58 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ernie Elu wrote: > Well I thought I would install cvsup and after the port script > downloaded 15MB of Modula-3 compiler across my 28.8K modem link it > gave a checksum error :-( Could you please run "md5" on the files you got, and send me the checksums? Somebody else recently reported the same problem to me. But I re-downloaded the files myself, and double-checked them, and their checksums were OK. I am wondering whether the new "fetch" program has some sort of problem with them, and is corrupting them. Meanwhile, you could either use the CVSup binaries, or grab the Modula-3 package and install that. -- John From owner-freebsd-current Sat Aug 10 01:48:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA23102 for current-outgoing; Sat, 10 Aug 1996 01:48:39 -0700 (PDT) Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA23094 for ; Sat, 10 Aug 1996 01:48:34 -0700 (PDT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.7.5/8.7.5) with ESMTP id QAA17221 for ; Sat, 10 Aug 1996 16:49:18 +0800 (CST) Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.5/8.7.3) id QAA24705 for freebsd-current@FreeBSD.ORG.; Sat, 10 Aug 1996 16:47:19 +0800 (CST) From: Jian-Da Li Message-Id: <199608100847.QAA24705@FreeBSD.csie.NCTU.edu.tw> Subject: Changes since Aug-3 causes 2.2C unstable To: freebsd-current@FreeBSD.ORG Date: Sat, 10 Aug 1996 16:47:19 +0800 (CST) X-Mailer: ELM [version 2.4ME+ PL11 (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 Hi : I just upgraded my kernel (and only kernel) from Aug-3 to Aug-10, and the new kernel will automatically reboot while making world. (The old kernel is able to make world under X-windows plus very heavy NFS loading) I checked the cvs changes related to kernel: - Suspecting Changes : sys/kern/kern_ktrace.c sys/kern/kern_malloc.c sys/kern/vfs_bio.c sys/sys/malloc.h - Non-related(?) network changes sys/i386/isa/if_ed.c sys/i386/isa/if_eg.c sys/i386/isa/if_egreg.h sys/net/if.h sys/net/if_ethersubr.c sys/i386/isa/b004.c sys/i386/isa/if_eg.c sys/conf/newvers.sh sys/netinet/ip_fw.c sys/net/if_ethersubr.c sys/i386/linux/linux_util.c sys/pci/ncr.c sys/i386/boot/netboot/3c509.c sys/i386/boot/netboot/3c509.h sys/i386/boot/netboot/main.c sys/i386/boot/netboot/netboot.h sys/i386/boot/netboot/ns8390.c sys/i386/boot/netboot/rpc.c sys/netinet/ip_fw.c sys/net/if_ethersubr.c sys/i386/linux/linux_util.c sys/pci/ncr.c sys/i386/boot/netboot/3c509.c sys/i386/boot/netboot/3c509.h sys/i386/boot/netboot/main.c sys/i386/boot/netboot/netboot.h sys/i386/boot/netboot/ns8390.c sys/i386/boot/netboot/rpc.c sys/i386/isa/if_ed.c sys/i386/isa/if_eg.c sys/i386/isa/if_el.c sys/i386/isa/if_elreg.h sys/i386/isa/if_epreg.h sys/i386/isa/if_fe.c sys/i386/isa/if_ix.c sys/i386/isa/if_ixreg.h sys/i386/isa/if_lnc.c sys/i386/isa/if_ze.c sys/i386/isa/if_zp.c sys/i386/isa/if_zpreg.h sys/net/ethernet.h sys/i386/boot/netboot/netboot.h sys/i386/boot/netboot/ns8390.c sys/i386/boot/netboot/rpc.c sys/i386/isa/if_ed.c sys/i386/isa/if_eg.c sys/i386/isa/if_el.c sys/i386/isa/if_elreg.h sys/i386/isa/if_epreg.h sys/i386/isa/if_fe.c sys/i386/isa/if_ix.c sys/i386/isa/if_ixreg.h sys/i386/isa/if_lnc.c sys/i386/isa/if_ze.c sys/i386/isa/if_zp.c sys/i386/isa/if_zpreg.h sys/net/ethernet.h sys/netinet/if_ether.h sys/pci/if_de.c sys/pci/if_vxreg.h sys/net/if.c sys/i386/isa/if_ed.c sys/i386/isa/if_edreg.h - My kernel config file: machine "i386" cpu "I586_CPU" ident GENERIC maxusers 32 #options DDB #Kernel Debugger options KTRACE #System-call tracing options CHILD_MAX=128 options OPEN_MAX=128 #options "I586_FAST_BCOPY" options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options NFS, "NFS_ASYNC" #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem #options "EXT2FS" #Ext2fs filesystem #options DEVFS #Devices filesystem options "COMPAT_43" #Compatible with BSD 4.3 #options LINUX #Linux emulator options "SCSI_DELAY=5" #Be pessimistic about Joe SCSI device options UCONSOLE options USER_LDT options QUOTA options SYSVMSG,SYSVSEM,SYSVSHM options LKM #options IPFIREWALL #firewall code #options IPFIREWALL_VERBOSE #print information about dropped packets config kernel root on sd0 dumps on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller ahc0 options AHC_TAGENABLE, AHC_SCBPAGING_ENABLE controller scbus0 device sd0 device cd0 #Only need one of these, the code dynamically grows device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device de0 controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 6 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 pseudo-device loop pseudo-device ether pseudo-device bpfilter 4 pseudo-device log pseudo-device pty 64 pseudo-device speaker pseudo-device gzip # Exec gzipped a.out's pseudo-device snp 4 #Snoop device - to look at pty/vty/etc.. pseudo-device vn 4 #Vnode driver (turns a file into a device) # Modem #pseudo-device ppp 1 #Point-to-point protocol #pseudo-device tun 1 #Tunnel driver(user process ppp) - My Aug-3 (old) kernel dmesg FreeBSD 2.2-CURRENT #0: Sat Aug 3 21:24:25 CST 1996 Calibrating clock(s) relative to mc146818A clock... i586 clock: 179618353 Hz, i8254 clock: 1193118 Hz CPU: Pentium (179.62-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping=11 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31248384 (30516K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 0 on pci0:7:0 pci0:7:1: Intel Corporation, device=0x7010, class=storage (ide) [no driver assigned] vga0 rev 83 int a irq 12 on pci0:10 ahc0 rev 0 int a irq 11 on pci0:11 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "IBM DPES-31080 S80E" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1034MB (2118144 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "IBM OEM DFHSS2F 4141" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2150MB (4404489 512 byte sectors) (ahc0:6:0): "MATSHITA CD-ROM CR-504 ST23" type 5 removable SCSI 2 cd0(ahc0:6:0): CD-ROM cd0(ahc0:6:0): NOT READY asc:3a,0 Medium not present can't get the size de0 rev 35 int a irq 10 on pci0:12 de0: DC21040 [10Mb/s] pass 2.3 de0: address 00:80:c8:0c:e0:77 de0: enabling 10baseT port Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> 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 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 sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 6 on isa sbxvo0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: changing root device to sd1a -- 李 建 達 (Jian-Da Li) 交 大 資 工 E-Mail : http://www.csie.nctu.edu.tw/~jdli From owner-freebsd-current Sat Aug 10 06:41:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA21656 for current-outgoing; Sat, 10 Aug 1996 06:41:27 -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 GAA21651; Sat, 10 Aug 1996 06:41:24 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA00829; Sat, 10 Aug 1996 15:41:22 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA10438; Sat, 10 Aug 1996 15:41:21 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA00327; Sat, 10 Aug 1996 11:51:32 +0200 (MET DST) From: J Wunsch Message-Id: <199608100951.LAA00327@uriah.heep.sax.de> Subject: Crash in rtrequest() To: freebsd-current@FreeBSD.org (FreeBSD-current users), wollman@FreeBSD.org Date: Sat, 10 Aug 1996 11:51:32 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) 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 -current kernel as of about 2 weeks old, dialup PPP session active over tun0, the system crashed at the first use of the line (the panic message noted named_xfer to be the current process). Here's the debugger analysis: uriah # gdb -k kernel /tmp/crash/vmcore.1 IdlePTD 240000 current pcb at 1feb60 panic: from debugger #0 boot (howto=256) at ../../i386/i386/machdep.c:750 750 dumppcb.pcb_cr3 = rcr3(); (kgdb) backtrace [...] #10 0xf01bab61 in calltrap () #11 0xf0143967 in rt_setgate (rt0=0xf0f39800, dst=0xf0f3a730, gate=0xf0e17450) at ../../net/route.c:682 #12 0xf01435be in rtrequest (req=11, dst=0xf0f3a730, gateway=0x0, netmask=0x0, flags=0, ret_nrt=0xefbffe68) at ../../net/route.c:468 #13 0xf0142f21 in rtalloc1 (dst=0xf0f3a730, report=1, ignflags=0) at ../../net/route.c:130 #14 0xf0142e6b in rtalloc (ro=0xf0f3a72c) at ../../net/route.c:98 #15 0xf01490fd in in_pcbladdr () #16 0xf015197e in tcp_connect () #17 0xf0151363 in tcp_usr_connect () #18 0xf012458f in soconnect () #19 0xf01270ef in connect () [...] (kgdb) up 9 #9 0xf01c5853 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 0, tf_ebp = -272630356, tf_isp = -272630420, tf_ebx = 131079, tf_edx = 16, tf_ecx = 0, tf_eax = -1073610752, tf_trapno = 12, tf_err = 0, tf_eip = -267111553, tf_cs = 8, tf_eflags = 66182, tf_esp = -252471296, tf_ss = -252471296}) at ../../i386/i386/trap.c:310 310 (void) trap_pfault(&frame, FALSE); (kgdb) frame frame->tf_ebp frame->tf_eip #0 0xf014337f in rtrequest (req=2, dst=0x0, gateway=0x0, netmask=0x0, flags=131079, ret_nrt=0x0) at ../../net/route.c:388 388 if ((rnh = rt_tables[dst->sa_family]) == 0) ^^^ dst is 0 (kgdb) l 383 register struct radix_node_head *rnh; 384 struct ifaddr *ifa; 385 struct sockaddr *ndst; 386 #define senderr(x) { error = x ; goto bad; } 387 388 if ((rnh = rt_tables[dst->sa_family]) == 0) 389 senderr(ESRCH); 390 if (flags & RTF_HOST) 391 netmask = 0; 392 switch (req) { (kgdb) up #1 0xf0143967 in rt_setgate (rt0=0xf0f39800, dst=0xf0f3a730, gate=0xf0e17450) at ../../net/route.c:682 682 rtrequest(RTM_DELETE, (struct sockaddr *)rt_key(rt0), (kgdb) l 677 (bcmp(dst, gate, dst->sa_len) == 0)) { 678 /* 679 * The route might already exist if this is an RTM_CHANGE 680 * or a routing redirect, so try to delete it. 681 */ 682 rtrequest(RTM_DELETE, (struct sockaddr *)rt_key(rt0), 683 rt0->rt_gateway, rt_mask(rt0), rt0->rt_flags, 0); 684 return EADDRNOTAVAIL; 685 } 686 (kgdb) quit uriah # exit exit Here's my suggested fix (workaround?), if nobody objects, i'm going to commit this within some days: Index: net/route.c =================================================================== RCS file: /usr/home/cvs/src/sys/net/route.c,v retrieving revision 1.34 diff -u -u -r1.34 route.c --- route.c 1996/07/10 01:34:35 1.34 +++ route.c 1996/08/10 09:38:06 @@ -385,7 +385,7 @@ struct sockaddr *ndst; #define senderr(x) { error = x ; goto bad; } - if ((rnh = rt_tables[dst->sa_family]) == 0) + if (dst == 0 || (rnh = rt_tables[dst->sa_family]) == 0) senderr(ESRCH); if (flags & RTF_HOST) netmask = 0; -- 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 Aug 10 09:45:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07724 for current-outgoing; Sat, 10 Aug 1996 09:45:19 -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 JAA07718 for ; Sat, 10 Aug 1996 09:45:14 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id SAA19594; Sat, 10 Aug 1996 18:30:39 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id QAA00499; Sat, 10 Aug 1996 16:41:25 +0200 (MET DST) Date: Sat, 10 Aug 1996 16:41:25 +0200 (MET DST) From: Andreas Klemm To: Michael Hancock cc: "Brian N. Handy" , Nate Williams , current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 8 Aug 1996, Michael Hancock wrote: > On Wed, 7 Aug 1996, Brian N. Handy wrote: > > > I guess another thing I wonder about...has anyone thought about the future > > plans of tracking gcc? We've been running 2.6.3 for a loong time, are we > > going to move to 2.7.# and stay with it or is FreeBSD going to start > > tracking gcc more closely? > > Since we're using gcc to compile the kernel we need to identify stable > releases of gcc and stick with it for a while. > > Closely tracking and incorporating all gcc releases (including unstable > releases) is not a high priority. Would it be a good compromise with respect to kernel stability, to call the old stable cc 'cc' and the new 2.7.2.x one 'gcc' ?! Everybody could choose between cc and gcc via /etc/make.conf. So we should perhaps add a contrib section with a bmaked contrib/gcc, so that the stable cc could stay where he is ?! 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 Sat Aug 10 09:45:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07784 for current-outgoing; Sat, 10 Aug 1996 09:45:53 -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 JAA07777; Sat, 10 Aug 1996 09:45:45 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id SAA19516; Sat, 10 Aug 1996 18:30:22 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id QAA00466; Sat, 10 Aug 1996 16:37:57 +0200 (MET DST) Date: Sat, 10 Aug 1996 16:37:56 +0200 (MET DST) From: Andreas Klemm To: sos@freebsd.org cc: Poul-Henning Kamp , gibbs@freefall.freebsd.org, nate@mt.sri.com, rgrimes@gndrsh.aac.dev.com, peter@spinner.dialix.com, current@freebsd.org Subject: Re: Whither gcc 2.7? In-Reply-To: <199608072105.XAA00469@DeepCore.dk> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 7 Aug 1996 sos@FreeBSD.org wrote: > In reply to Poul-Henning Kamp who wrote: > > I will be against it all the way. > > So, we should make a bmaked version, put it in the tree as usual, and > let the original (and pgcc and xxgcc..) be in ports... > No need for that contrib mess... Yeah ! -- 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 Sat Aug 10 11:43:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14083 for current-outgoing; Sat, 10 Aug 1996 11:43:57 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA14078; Sat, 10 Aug 1996 11:43:54 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14988(6)>; Sat, 10 Aug 1996 11:43:18 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177517>; Sat, 10 Aug 1996 11:43:11 -0700 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users), wollman@freebsd.org, fenner@parc.xerox.com Subject: Re: Crash in rtrequest() In-reply-to: Your message of "Sat, 10 Aug 96 02:51:32 PDT." <199608100951.LAA00327@uriah.heep.sax.de> Date: Sat, 10 Aug 1996 11:43:08 PDT From: Bill Fenner Message-Id: <96Aug10.114311pdt.177517@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Do you think I could have access to this core dump? I'd like to see exactly what rt0 looks like, and who actually called rt_setgate. Your fix only hides the problem, and this is code that I wrote in route.c , so I'd like to get to the bottom of it. Bill From owner-freebsd-current Sat Aug 10 12:09:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA14864 for current-outgoing; Sat, 10 Aug 1996 12:09:40 -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 MAA14858 for ; Sat, 10 Aug 1996 12:09:36 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA06700; Sat, 10 Aug 1996 21:09:29 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14451; Sat, 10 Aug 1996 21:09:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA02585; Sat, 10 Aug 1996 21:05:23 +0200 (MET DST) From: J Wunsch Message-Id: <199608101905.VAA02585@uriah.heep.sax.de> Subject: Re: Crash in rtrequest() To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 10 Aug 1996 21:05:21 +0200 (MET DST) Cc: fenner@parc.xerox.com (Bill Fenner) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <96Aug10.114311pdt.177517@crevenia.parc.xerox.com> from Bill Fenner at "Aug 10, 96 11:43:08 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 Bill Fenner wrote: > Do you think I could have access to this core dump? I'd like to see exactly > what rt0 looks like, and who actually called rt_setgate. Your fix only hides > the problem, and this is code that I wrote in route.c , so I'd like to get to > the bottom of it. D*mn, i've already removed the coredump. :-( Anyway, the stacktrace i've been quoting was fairly complete: (kgdb) backtrace [...] #10 0xf01bab61 in calltrap () #11 0xf0143967 in rt_setgate (rt0=0xf0f39800, dst=0xf0f3a730, gate=0xf0e17450) at ../../net/route.c:682 #12 0xf01435be in rtrequest (req=11, dst=0xf0f3a730, gateway=0x0, netmask=0x0, flags=0, ret_nrt=0xefbffe68) at ../../net/route.c:468 #13 0xf0142f21 in rtalloc1 (dst=0xf0f3a730, report=1, ignflags=0) at ../../net/route.c:130 #14 0xf0142e6b in rtalloc (ro=0xf0f3a72c) at ../../net/route.c:98 #15 0xf01490fd in in_pcbladdr () #16 0xf015197e in tcp_connect () #17 0xf0151363 in tcp_usr_connect () #18 0xf012458f in soconnect () #19 0xf01270ef in connect () [...] The ``calltrap'' is actually the crashing instance of rtrequest(), but rt_setgate() has been called by another instance of rtrequest: makeroute: R_Malloc(rt, struct rtentry *, sizeof(*rt)); if (rt == 0) senderr(ENOBUFS); Bzero(rt, sizeof(*rt)); rt->rt_flags = RTF_UP | flags; if (rt_setgate(rt, dst, gateway)) { <<=== here Free(rt); senderr(ENOBUFS); } I've been analyzing rt0 (but forgot to quote _this_), it was almost entirely zero except of the rt_flags field 131079 = RTF_WASCLONED | RTF_UP | RTF_GATEWAY | RTF_HOST. Maybe one of the pointers also was nonempty, i eventually forgot this detail. rtrequest (req=11, dst=0xf0f3a730, gateway=0x0, netmask=0x0, flags=0, ...) RTM_RESOLVE? ^^^^^^^ This looks suspicous since there's RTF_GATEWAY set?! -- 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 Aug 10 12:27:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15661 for current-outgoing; Sat, 10 Aug 1996 12:27:11 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA15633 for ; Sat, 10 Aug 1996 12:27:10 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA298345221; Sat, 10 Aug 1996 12:27:01 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA185105220; Sat, 10 Aug 1996 12:27:00 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA249845219; Sat, 10 Aug 1996 12:26:59 -0700 Message-Id: <199608101926.AA249845219@hpnmhjw.sr.hp.com> To: John Polstra Cc: current@freefall.freebsd.org Subject: Re: Praise for CVSup In-Reply-To: Your message of "Fri, 09 Aug 1996 21:23:58 PDT." Date: Sat, 10 Aug 1996 12:26:59 -0700 From: Darryl Okahata Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Could you please run "md5" on the files you got, and send me the > checksums? Somebody else recently reported the same problem to me. But > I re-downloaded the files myself, and double-checked them, and their > checksums were OK. I am wondering whether the new "fetch" program has > some sort of problem with them, and is corrupting them. Just as a data point, I used the Modula-3 port from 2.1.5, and I didn't have any problems. [ Well, I didn't have any problems initially downloading and building it, but I had lots of "fun" bashing Modula-3 into getting outside our firewall ... (cvsup isn't useful unless I can get outside ;-(). I also found a small bug in the FreeBSD portion of Modula-3 -- where should I send the report? ] -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-current Sat Aug 10 12:59:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17158 for current-outgoing; Sat, 10 Aug 1996 12:59:01 -0700 (PDT) Received: from nwnexus.wa.com (nwnexus.wa.com [192.135.191.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA17151 for ; Sat, 10 Aug 1996 12:58:59 -0700 (PDT) Received: from main.statsci.com (ns1.statsci.com) by nwnexus.wa.com with SMTP id AA22715 (5.65c/IDA-1.4.4 for ); Sat, 10 Aug 1996 12:58:56 -0700 Received: from statsci.com [206.63.206.4] with smtp by main.statsci.com with smtp (/\oo/\ Smail3.1.29.1 #29.3 #3) id m0upKBT-000QYDC; Sat, 10 Aug 96 12:58 PDT Message-Id: To: John Polstra Cc: ernie@spooky.eis.net.au, freebsd-current@freebsd.org Subject: Re: Praise for CVSup References: <199608100423.VAA24889@austin.polstra.com> In-Reply-To: Your message of "Fri, 09 Aug 1996 21:23:58 -0700." <199608100423.VAA24889@austin.polstra.com> Reply-To: scott@statsci.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Id: <3627.839707134.1@statsci.com> Date: Sat, 10 Aug 1996 12:58:54 -0700 From: Scott Blachowicz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Polstra wrote: > Ernie Elu wrote: > > > Well I thought I would install cvsup and after the port script > > downloaded 15MB of Modula-3 compiler across my 28.8K modem link it > > gave a checksum error :-( > > Could you please run "md5" on the files you got, and send me the > checksums? Somebody else recently reported the same problem to me. But > I re-downloaded the files myself, and double-checked them, and their > checksums were OK. I am wondering whether the new "fetch" program has > some sort of problem with them, and is corrupting them. I'd tried doing it on a 2.1.0R system and it downloaded all the stuff just fine - then I ran out of disk space in the Modula-3 build... > Meanwhile, you could either use the CVSup binaries, or grab the Modula-3 > package and install that. There doesn't appear to be a Modula-3 package in my 2.1.0R CDROM, but my 2.1.5R CD should be here "any day now" (tm)... Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div) 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org From owner-freebsd-current Sat Aug 10 13:27:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18386 for current-outgoing; Sat, 10 Aug 1996 13:27:02 -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 NAA18381 for ; Sat, 10 Aug 1996 13:26:56 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id GAA07492; Sun, 11 Aug 1996 06:22:30 +1000 Date: Sun, 11 Aug 1996 06:22:30 +1000 From: Bruce Evans Message-Id: <199608102022.GAA07492@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: Crash in rtrequest() Cc: fenner@parc.xerox.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Anyway, the stacktrace i've been quoting was fairly complete: >(kgdb) backtrace >[...] >#10 0xf01bab61 in calltrap () >#11 0xf0143967 in rt_setgate (rt0=0xf0f39800, dst=0xf0f3a730, gate=0xf0e17450) > at ../../net/route.c:682 >#12 0xf01435be in rtrequest (req=11, dst=0xf0f3a730, gateway=0x0, netmask=0x0, > flags=0, ret_nrt=0xefbffe68) at ../../net/route.c:468 >#13 0xf0142f21 in rtalloc1 (dst=0xf0f3a730, report=1, ignflags=0) > at ../../net/route.c:130 >#14 0xf0142e6b in rtalloc (ro=0xf0f3a72c) at ../../net/route.c:98 >#15 0xf01490fd in in_pcbladdr () >#16 0xf015197e in tcp_connect () >#17 0xf0151363 in tcp_usr_connect () >#18 0xf012458f in soconnect () >#19 0xf01270ef in connect () >[...] >The ``calltrap'' is actually the crashing instance of rtrequest(), but The bogus backtrace was supposed to be fixed in rev.1.10 of i386/exception.s, but the fix got deleted in rev.1.14. Backtraces for NULL pointers and the like will always show `calltrap' instead of the routine where the fault occurred until this is fixed. >rt_setgate() has been called by another instance of rtrequest: > makeroute: > R_Malloc(rt, struct rtentry *, sizeof(*rt)); > if (rt == 0) > senderr(ENOBUFS); > Bzero(rt, sizeof(*rt)); > rt->rt_flags = RTF_UP | flags; > if (rt_setgate(rt, dst, gateway)) { <<=== here > Free(rt); > senderr(ENOBUFS); > } Apparently rt_key(rt0) is NULL in rt_setgate(). Bruce