From owner-freebsd-current Sun Jul 7 01:21:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06379 for current-outgoing; Sun, 7 Jul 1996 01:21:36 -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 BAA06365 for ; Sun, 7 Jul 1996 01:21:30 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03534 for ; Sun, 7 Jul 1996 10:21:28 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA16894 for freebsd-current@FreeBSD.org; Sun, 7 Jul 1996 10:21:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA24626 for freebsd-current@FreeBSD.org; Sun, 7 Jul 1996 09:58:13 +0200 (MET DST) From: J Wunsch Message-Id: <199607070758.JAA24626@uriah.heep.sax.de> Subject: Re: Which tools can back up inodes with 32bit minor numbers ? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 7 Jul 1996 09:58:13 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607061414.QAA23586@vector.jhs.no_domain> from "Julian H. Stacey" at "Jul 6, 96 04:14:20 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: > > (You will get /dev into a separate file system anytime soon. But i > > doubt you will have any need to include it into a backup then. :-) > > One can run MAKEDEV to rebuild standard stuff, but after working away > at /dev & various other dirs. with various ports & private stuff, > EG fax + uucp + slip + getty etc, > it's nice to be able to make a complete backup of a working system. Well, as i wrote, the existing static /dev is about to be killed anytime soon. MAKEDEV as well -- shouldn't you have it already noticed. Persistency of the devfs entries across reboots was one major point of discussion, and good ideas are still sought. I tend to defend the idea of keeping this outside the kernel, so the device drivers do only create their generic device nodes, while some /etc/rc-started userland script creates the required links (and tweaks the permissions if necessary). Anyway, i'm biased, i have seen something to this avail working on DG/UX. Simply backing it up with cpio or dump and restoring later is *not* the way to go then. > Also, perhaps we should > s/GNU/GNU (& thus FreeBSD etc)/ > in the (formatted) chunk: > The new ASCII format > is portable between different machine architectures and > can be used on any size file system, but is not supported > by all versions of cpio; currently, it is only supported > by GNU and Unix System V R4. The crc format is like the > new ASCII format, but also contains a checksum No, there's no such thing like ``FreeBSD cpio''. We use GNU cpio. > > You forgot: > > pax: > ..... > > I'm conservative, I don't use pax ;-) (far as I know, it's just a new > wrapper, not on many commercial Unixes, for formats also available by tar > & cpio, & I have enough trouble remembering cpio parameters). It's the only archiver sanctioned by Posix.2. All platforms that claim support for Posix.2 should have it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 7 01:21:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06399 for current-outgoing; Sun, 7 Jul 1996 01:21:48 -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 BAA06392 for ; Sun, 7 Jul 1996 01:21:42 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03538; Sun, 7 Jul 1996 10:21:30 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA16895; Sun, 7 Jul 1996 10:21:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA24721; Sun, 7 Jul 1996 10:15:35 +0200 (MET DST) From: J Wunsch Message-Id: <199607070815.KAA24721@uriah.heep.sax.de> Subject: Re: New install using 2.2-SNAP ... To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 7 Jul 1996 10:15:34 +0200 (MET DST) Cc: scrappy@ki.net (Marc G. Fournier) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Marc G. Fournier" at "Jul 6, 96 10:58:25 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 Marc G. Fournier wrote: > The reason I never noticed this before is that when I normally > install, I allocate the whole drive to FreeBSD, since I'm never going > to co-locate Linux/DOS on the same box... > > For some reason, this time, I failed to do that :( I you know how to read an fdisk table, and you can re-compute the required entries, you don't need to reinstall. What you are suffering is basically that your start values for the FreeBSD slice don't agree in terms of C/H/S from a BIOS point of view. Anyway, the LBA offset for the partition start is right, and if you pick the BIOS' geometry idea, you can recalculate the required C/H/S values to enter there. (Don't forget that sectors are numbered base 1, while cylinders and heads are numbered base 0 -- historical baggage.) This will usually end up in ``odd'' numbers, i.e. not starting on what the BIOS believes were a track boundary, but don't care, it will work nevertheless. The reason why you don't see it in ``dangerously dedicated'' mode is that the starting offset LBA is 0 there, and you can hardly miscompute a 0 into the wrong C/H/S values. :-) -- 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 Sun Jul 7 01:49:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA07553 for current-outgoing; Sun, 7 Jul 1996 01:49: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 BAA07548 for ; Sun, 7 Jul 1996 01:49:22 -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 KAA19292; Sun, 7 Jul 1996 10:45:32 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA02927; Sun, 7 Jul 1996 10:59:32 +0200 From: "Christoph P. Kukulies" Message-Id: <199607070859.KAA02927@gilberto.physik.rwth-aachen.de> Subject: Re: Where is contrib/tcl? To: dmaddox@scsn.net (Donald J. Maddox) Date: Sun, 7 Jul 1996 10:59:31 +0200 (MET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <19960706202504001.AAA212@cola83.scsn.net> from "Donald J. Maddox" at "Jul 6, 96 04:25:05 pm" 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 > Ok, I give up... When I do a full sup (using the standard supfile), I > don't get contrib/tcl, and I can't find it any where on ftp.freebsd.org. If > -current won't build without tcl, why isn't it included in a full sup? > Donald J. Maddox A while ago phk announced (in this list) new handling of the contrib stuff. src-contrib release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-contrib release=stable host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sun Jul 7 01:51:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA07669 for current-outgoing; Sun, 7 Jul 1996 01:51:50 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA07664 for ; Sun, 7 Jul 1996 01:51:47 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.5/BSD4.4) id SAA29180 for current@freebsd.org; Sun, 7 Jul 1996 18:51:37 +1000 (EST) From: michael butler Message-Id: <199607070851.SAA29180@asstdc.scgt.oz.au> Subject: Thinkpad 560 + -current To: current@freebsd.org Date: Sun, 7 Jul 1996 18:51:36 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A few reports .. i) the TP560 dislikes apm in -current .. with or without the "broken stat clock" option it'll panic :-( ii) has anyone run X on this thing ? SuperProbe reports .. First video: Super-VGA Chipset: Trident GUI 9660 Memory: 1024 Kbytes RAMDAC: Sierra SC1148{2,3,4} 15-bit or SC1148{5,7,9} 15/16-bit HiColor (with 6-bit wide lookup tables (or in 6-bit mode)) .. which isn't in anything but 3.1.2E and that doesn't seem to switch to graphic mode (I'm left with the text-mode output). iii) if I enable the pccard support, the zp0 driver stops seeing the 3c589 and the system reports a "device allocation failure" (I assume that I'd need to either wire in the nep driver or redefine the stuff in /etc/pccard.conf to point at the zp driver) .. suggestions ? iv) if I revert to the 2.1R code + pccard-test package, apm will simply hang the machine (power-off by removing battery :-() and the nep0 driver pulls the "link OK" on my hub at unpredictable intervals. "ifconfig nep0 down" followed by "ifconfig nep0 up" restores normal operation .. for a while .. Other than this .. it's a nice, quick and light machine :-) michael From owner-freebsd-current Sun Jul 7 02:09:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08717 for current-outgoing; Sun, 7 Jul 1996 02:09:36 -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 CAA08705 for ; Sun, 7 Jul 1996 02:09:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id CAA04333; Sun, 7 Jul 1996 02:09:05 -0700 (PDT) Message-Id: <199607070909.CAA04333@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Christoph Kukulies cc: dmaddox@scsn.net (Donald J. Maddox), freebsd-current@freebsd.org Subject: Re: Where is contrib/tcl? In-reply-to: Your message of "Sun, 07 Jul 1996 10:59:31 +0200." <199607070859.KAA02927@gilberto.physik.rwth-aachen.de> From: David Greenman Reply-To: davidg@root.com Date: Sun, 07 Jul 1996 02:09:04 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Ok, I give up... When I do a full sup (using the standard supfile), I >> don't get contrib/tcl, and I can't find it any where on ftp.freebsd.org. If >> -current won't build without tcl, why isn't it included in a full sup? >> Donald J. Maddox > >A while ago phk announced (in this list) new handling of the contrib stuff. > >src-contrib release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix >src-contrib release=stable host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix Until just a few hours ago, *-contrib was only available from sup.freebsd.org. ftp.freebsd.org (wcarchive) was still using the now out of date supfiles and thus didn't have the contrib/ directory tree. I've fixed this, so it should now be available as expected. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Jul 7 05:54:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA06424 for current-outgoing; Sun, 7 Jul 1996 05:54:52 -0700 (PDT) Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA06309; Sun, 7 Jul 1996 05:54:22 -0700 (PDT) Received: from campa.panke.de (anonymous214.ppp.cs.tu-berlin.de [130.149.17.214]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id OAA02913; Sun, 7 Jul 1996 14:47:06 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id NAA02993; Sun, 7 Jul 1996 13:54:20 +0200 Date: Sun, 7 Jul 1996 13:54:20 +0200 From: Wolfram Schneider Message-Id: <199607071154.NAA02993@campa.panke.de> To: peter@freebsd.org CC: current@freebsd.org Subject: rcs keyword '$FreeBSD: $' disabled Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why is the keyword '$FreeBSD: $' (an alias for '$Id: $') disabled? Wolfram rcs/lib/rcskeys.c: char const *const Keyword[] = { /* This must be in the same order as rcsbase.h's enum markers type. */ 0, AUTHOR, DATE, HEADER, IDH, LOCKER, LOG, NAME, RCSFILE, REVISION, SOURCE, STATE, FREEBSD ^^^^^^^ }; /* Expand all keywords by default */ static int ExpandKeyword[] = { false, true, true, true, true, true, true, true, true, true, true, true, false ^^^^^ }; From owner-freebsd-current Sun Jul 7 07:01:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA08298 for current-outgoing; Sun, 7 Jul 1996 07:01:20 -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 HAA08230 for ; Sun, 7 Jul 1996 07:01:14 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id PAA16785 for current@freebsd.org; Sun, 7 Jul 1996 15:45:38 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id PAA01564 for ; Sun, 7 Jul 1996 15:53:25 +0200 (MET DST) Date: Sun, 7 Jul 1996 15:53:25 +0200 (MET DST) From: Andreas Klemm To: current@freebsd.org Subject: moused is responsible for my frozen cursor under X11 when using xv Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! It took me some work but now I know, that moused is the culprit ;-) moused was invoked with the following arguments from within rc.i386: mouseport=/dev/cuaa0 mousetype=mouseman moused -p ${mouseport} -t ${mousetype} X11R6 was started by me with xinit. The Numlock key is on. S3 Server. Try to startup the visual schnauzer. The mousepointer freezes ! Terminate X11, kill moused, and restart X11. Then everything is fine. X11 also uses cuaa0 as mouse port. Additionally I watched the mouse jumping from time to time when using it under X11 or it was as if I had clicked somewhere but I didn't. Regards Andreas /// andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sun Jul 7 07:16:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA13924 for current-outgoing; Sun, 7 Jul 1996 07:16:09 -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 HAA13864 for ; Sun, 7 Jul 1996 07:16:00 -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 WAA28208; Sun, 7 Jul 1996 22:14:28 +0800 (WST) Message-Id: <199607071414.WAA28208@spinner.DIALix.COM> X-Mailer: exmh version 1.6.6 3/24/96 To: Wolfram Schneider cc: current@freebsd.org Subject: Re: rcs keyword '$FreeBSD: $' disabled In-reply-to: Your message of "Sun, 07 Jul 1996 13:54:20 +0200." <199607071154.NAA02993@campa.panke.de> Date: Sun, 07 Jul 1996 22:14:27 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wolfram Schneider wrote: > > Why is the keyword '$FreeBSD: $' (an alias for '$Id: $') disabled? Because that was only part of the story.. There were corresponding modifications to CVS as well, but it turned out to be a problem that was more trouble that it was worth at the time, so it never was reimplemented. Consider: If we have $FreeBSD$ in the freefall sources, then every other freebsd user who sup's a copy of the cvs source must also run a hacked copy of the rcs/cvs binaries. The main "reason" for having an alternate keyword is so that $Id$, $Log$ etc are completely ignored so that there are no version conflicts when importing, so just turning on $FreeBSD$ isn't enough. All the others should be turned off at the same time (which is what the original #ifdef FREEBSD_DEVELOPER patches did). I implemented an alternative set of patches that were (IMHO) cleaner, and didn't interfere with the installed rcs binaries default behavior. What I did was implement a "keyword prefix" string. ie: if you did a "rcs -KFreeBSD- file,v", it would store that in the rcs file itself and our slightly-modified rcs would notice it and would then only expand $FreeBSD-Id$, $FreeBSD-Log$ etc and completely ignore $Id$, $Log$ and so on. Hardly any CVS changes were needed, I put in a hack when the initial import was happening to add in the keyword when CVS generates the ,v file, but that was it. The beauty of this approach is that you can still use /usr/bin/{ci,co,rcs,rcsdiff,...} in the normal fashion on *all* rcs files without unexpected behavior, the binaries adapt to the repository they are working on. Even the older RCS binaries could cope with the extension to the ,v file that I added, but naturally, they didn't know about the new keywords. Cheers, -Peter From owner-freebsd-current Sun Jul 7 10:46:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28620 for current-outgoing; Sun, 7 Jul 1996 10:46:01 -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 KAA28614 for ; Sun, 7 Jul 1996 10:45:54 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA15262; Sun, 7 Jul 1996 13:44:21 -0400 From: Bill Paul Message-Id: <199607071744.NAA15262@skynet.ctr.columbia.edu> Subject: Re: Which tools can back up inodes with 32bit minor numbers ? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 7 Jul 1996 13:44:20 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199607070758.JAA24626@uriah.heep.sax.de> from "J Wunsch" at Jul 7, 96 09:58:13 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, J Wunsch had to walk into mine and say: > As Julian H. Stacey wrote: > > > > (You will get /dev into a separate file system anytime soon. But i > > > doubt you will have any need to include it into a backup then. :-) > > > > One can run MAKEDEV to rebuild standard stuff, but after working away > > at /dev & various other dirs. with various ports & private stuff, > > EG fax + uucp + slip + getty etc, > > it's nice to be able to make a complete backup of a working system. > > Well, as i wrote, the existing static /dev is about to be killed > anytime soon. MAKEDEV as well -- shouldn't you have it already > noticed. Wrong. The existing /dev and MAKEDEV are _not_ going away any time soon. Not on any of the systems I maintain anyway (including my personal machines at home). You'll never catch me putting 'options DEVFS' in any of my kernel config files. And the day it changes from optional to mandatory is the day I stop running FreeBSD. Sun already burned me with their "we're giving you these new features whether you like them or not" attitude. I'm not letting anyone else force any unwanted innovation down my throat if I can avoid it, even if it doesn't cost me any money. Getting back to the subject at hand, dump and restore are supposed to preserve _everything_, including 32-bit major/minor values (we got 'em, we gotta deal with 'em). Ideally, tar and cpio should too. If they don't, they should be made to, but only if their archive formats allow it without breaking compatibility with all the other tar and cpio implementations on the planet. If dump and restore aren't doing it, they are broken and need to be fixed. DEVFS doesn't enter into it. -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 Sun Jul 7 11:15:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04682 for current-outgoing; Sun, 7 Jul 1996 11:15:05 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA04677 for ; Sun, 7 Jul 1996 11:15:01 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id OAA11715 for ; Sun, 7 Jul 1996 14:15:04 -0400 (EDT) Date: Sun, 7 Jul 1996 14:15:03 -0400 (EDT) From: "Marc G. Fournier" Reply-To: "Marc G. Fournier" To: current@freebsd.org Subject: Shared Memory Buffers ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Back again with another question... I'm running Postgres95 1.01 under FreeBSD 2.2-current pretty much problem free, except every once in a while I get a "backend crash" due to shared memory corruption (sorry, don't have the exact error message to include) Now, those on the Postgres95 mailing list suggestion starting up the postmaster daemon with -B 1024, which is: -B n_buffers n_buffers is the number of shared-memory buffers for the postmaster to allocate and manage for the backend server processes that it starts. This value defaults to 64. Except, if I try, I get: postgres@zeus> bin/postmaster -B 1024 -S IpcMemoryCreate: memKey=155356396 , size=8697560 , permission=384IpcMemoryCreate: shmget(..., create, ...) failed: Invalid argument If I do it as -B 64, it works, but then again, that's the default setting... As I know absolutely zilch about semaphores and shared memory, can someone tell me what is wrong here? Is it a coding problem inside of the postgres95 server (which I would assume would mean that -B 64 shouldn't work either)? Is it a setting I have to increase in my kernel? Or is it associated with the 'datasize' value that the limit command shows me? I've checked the handbook, FAQ and about every other resource I could find @ www.freebsd.org, but can't even find any references to shared memoryy/SYSV* related settings :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sun Jul 7 11:51:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06412 for current-outgoing; Sun, 7 Jul 1996 11:51:58 -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 LAA06402 for ; Sun, 7 Jul 1996 11:51:49 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA15452; Sun, 7 Jul 1996 20:51:38 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA21418; Sun, 7 Jul 1996 20:51:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA27228; Sun, 7 Jul 1996 20:38:43 +0200 (MET DST) From: J Wunsch Message-Id: <199607071838.UAA27228@uriah.heep.sax.de> Subject: Re: Which tools can back up inodes with 32bit minor numbers ? To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Sun, 7 Jul 1996 20:38:43 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607071744.NAA15262@skynet.ctr.columbia.edu> from Bill Paul at "Jul 7, 96 01:44:20 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 Bill Paul wrote: > > Well, as i wrote, the existing static /dev is about to be killed > > anytime soon. MAKEDEV as well -- shouldn't you have it already > > noticed. > > Wrong. > > The existing /dev and MAKEDEV are _not_ going away any time soon. You cannot generalize this case. If they won't go away for _you_, so that's your problem. I think there's consensus that they won't survive the end of the century for most other FreeBSD users. > Sun already burned me with their "we're giving you these new features > whether you like them or not" attitude. It's not really a new feature, and i've seen devfs-based systems (DG/UX, as i've already mentioned) where it took me about a year or so to realize that they are actually using such a thing. (Ok, my degree of Unix experience wasn't that high back in the old days.) It fit smothelessly into the entire environment. The static /dev tree has been a misconception in the first place, since it always tends to disagree between the actual device configuration and the existing device nodes. You know as well as me that this is a fatal discrepancy, either direction. Also, it requires a central authority to give out major device numbers, even for locally maintained drivers. This is not to say that we don't need a good methodology to allow for all kinds of valid requirements, e.g. some sort of ``persistency''. Anyway, i doubt people who are crying ``I wanna get my V7 back in FreeBSD-current!'' will influence the overall decision too much. ;-) (Funny, you didn't oppose to the merged VM/buffer cache changes, and that's far more into the direction of "we're giving you these new features...".) > Getting back to the subject at hand, dump and restore are > supposed to preserve _everything_, ... Nobody ever claimed the opposite. You're running into open doors here. > Ideally, tar and cpio > should too. If they don't, they should be made to, but only if their > archive formats allow it without breaking compatibility with all the They don't allow it (except for the newer cpio formats, but we support this, but^2 quite a bunch of other systems don't). > other tar and cpio implementations on the planet. If dump and restore > aren't doing it, they are broken and need to be fixed. DEVFS doesn't > enter into it. Devfs is not intended as a replacement for a broken backup tool. You must be confusing this some way. Having said this, remember: that's just my very personal opinion. It's in no way related to other people, neither of the FreeBSD core team or else. With the current buggy state of affairs, it doesn't look like a mandatory devfs would already happen next week... -- 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 Sun Jul 7 12:51:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10804 for current-outgoing; Sun, 7 Jul 1996 12:51:39 -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 MAA10795 for ; Sun, 7 Jul 1996 12:51:32 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA00113; Mon, 8 Jul 1996 05:47:38 +1000 Date: Mon, 8 Jul 1996 05:47:38 +1000 From: Bruce Evans Message-Id: <199607071947.FAA00113@godzilla.zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, wpaul@skynet.ctr.columbia.edu Subject: Re: Which tools can back up inodes with 32bit minor numbers ? Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Well, as i wrote, the existing static /dev is about to be killed >> anytime soon. MAKEDEV as well -- shouldn't you have it already >> noticed. >Wrong. >The existing /dev and MAKEDEV are _not_ going away any time soon. >Not on any of the systems I maintain anyway (including my personal >machines at home). You'll never catch me putting 'options DEVFS' in >any of my kernel config files. And the day it changes from optional >to mandatory is the day I stop running FreeBSD. Stop now before you become more attached to it :-). Devfs in some form is necessary for avoiding a limited fixed mapping of device names to drivers. >Getting back to the subject at hand, dump and restore are >supposed to preserve _everything_, including 32-bit major/minor >values (we got 'em, we gotta deal with 'em). Ideally, tar and cpio >should too. If they don't, they should be made to, but only if their >archive formats allow it without breaking compatibility with all the >other tar and cpio implementations on the planet. If dump and restore >Getting back to the subject at hand, dump and restore are >supposed to preserve _everything_, including 32-bit major/minor >values (we got 'em, we gotta deal with 'em). Ideally, tar and cpio >should too. If they don't, they should be made to, but only if their >archive formats allow it without breaking compatibility with all the >other tar and cpio implementations on the planet. If dump and restore They can't. E.g., tar format has 8-byte null-terminated strings with octal digits for the major and the minor numbers. This limits the number of bits to 21. Gnu tar has a bug that further limits the number of bits to 18 (it blank terminates as well as null terminates the strings). Gnu cpio has the same bug as gnu tar. `pax -x ustar' handles the full 21 bits. Gnu cpio seems to handle 21 bits minors correctly for input (it handles tar output from pax). Gnu tar can't handle tar output from pax or cpio (sio cpio/README) so I couldn't test it on pax's output. Bruce From owner-freebsd-current Sun Jul 7 22:49:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09086 for current-outgoing; Sun, 7 Jul 1996 22:49:51 -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 WAA09073; Sun, 7 Jul 1996 22:49:48 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id FAA11642; Mon, 8 Jul 1996 05:49:46 GMT Date: Mon, 8 Jul 1996 14:49:46 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: dyson@freebsd.org cc: current@freebsd.org Subject: Re: Is it just my imagination? In-Reply-To: <199607061915.OAA03156@dyson.iquest.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 Sat, 6 Jul 1996, John S. Dyson wrote: > I have just tried the latest version of Netscape, and it appears > to load much faster... Am I wrong, or did they do something? It does load much faster and they fixed the image bleed problem I was having on the first load. mike From owner-freebsd-current Sun Jul 7 23:12:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10505 for current-outgoing; Sun, 7 Jul 1996 23:12:25 -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 XAA10500 for ; Sun, 7 Jul 1996 23:12:21 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id AAA11219; Mon, 8 Jul 1996 00:11:49 -0600 (MDT) Date: Mon, 8 Jul 1996 00:11:49 -0600 (MDT) Message-Id: <199607080611.AAA11219@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: current@freebsd.org Subject: Re: Thinkpad 560 + -current In-Reply-To: <199607070851.SAA29180@asstdc.scgt.oz.au> References: <199607070851.SAA29180@asstdc.scgt.oz.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > i) the TP560 dislikes apm in -current .. with or without the "broken stat > clock" option it'll panic :-( Sigh. Is this with or without PC-CARDS inserted? (This makes a difference apparently). > iii) if I enable the pccard support, the zp0 driver stops seeing the 3c589 > and the system reports a "device allocation failure" (I assume that I'd need > to either wire in the nep driver or redefine the stuff in /etc/pccard.conf > to point at the zp driver) .. suggestions ? You can't mix/match if_zp.c and the PC-CARD stuff. They do the same thing but are implemented very differently. Either you use the 'dedicated' drivers (if_zp/if_ze) OR the generic drivers (if_ed, if_ep, sio etc..). > iv) if I revert to the 2.1R code + pccard-test package, apm will simply hang > the machine (power-off by removing battery :-() Yep, that's one of the bugs I fixed on my ThinkPad with the apm code. > and the nep0 driver pulls > the "link OK" on my hub at unpredictable intervals. "ifconfig nep0 down" > followed by "ifconfig nep0 up" restores normal operation .. for a while .. You should be able to bring in the if_ep.c driver from -current and use it instead of the if_nep.c driver from the pccard-test (now PAO) package. Also, you could *try* using the apm.c from -current as well as it contains virtually *all* of the features of the pccard-test code minus bugs. :) > Other than this .. it's a nice, quick and light machine :-) Glad to hear it works. Did you use the stock boot floppy, or did you need to use my special 'ThinkPad' floppy? Nate From owner-freebsd-current Mon Jul 8 01:29:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA16569 for current-outgoing; Mon, 8 Jul 1996 01:29:20 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA16564 for ; Mon, 8 Jul 1996 01:29:10 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id BAA12400 for ; Mon, 8 Jul 1996 01:29:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id BAA20716 for ; Mon, 8 Jul 1996 01:29:07 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: `file', BSD/i386 Date: Mon, 08 Jul 1996 01:29:06 PDT Message-ID: <20714.836814546@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, All my executables are being recognized as BSD/i386: ; file /bin/ls /bin/ls: BSD/i386 compact demand paged executable ; file /usr/local/bin/bash /usr/local/bin/bash: BSD/i386 compact demand paged dynamically linked executable ; file /usr/bin/man /usr/bin/man: BSD/i386 compact demand paged dynamically linked executable ; I last sup'd on Saturday, July 6th. faried. From owner-freebsd-current Mon Jul 8 02:06:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA18985 for current-outgoing; Mon, 8 Jul 1996 02:06:04 -0700 (PDT) Received: from zero-gravity.netlab.london.sco.com (zero-gravity.netlab.london.sco.com [150.126.252.16]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA18975 for ; Mon, 8 Jul 1996 02:05:59 -0700 (PDT) Received: (from davided@localhost) by zero-gravity.netlab.london.sco.com (8.7.5/dme/nice-1.1) id JAA00205; Mon, 8 Jul 1996 09:59:11 +0100 (BST) Date: Mon, 8 Jul 1996 09:59:11 +0100 (BST) Message-Id: <199607080859.JAA00205@zero-gravity.netlab.london.sco.com> To: michael butler Cc: current@freebsd.org Subject: re: Thinkpad 560 + -current In-Reply-To: <199607070851.SAA29180@asstdc.scgt.oz.au> References: <199607070851.SAA29180@asstdc.scgt.oz.au> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: dave edmondson X-Face: "?v.huY]?B[a4C|xid!Tx8TpwOQe6]C(I}h8Vo1z6'9soM_Xvq2f3u::[F~rW>GWj6;IfU,10H;B&1JDE/H8?``q4XH4~!\_z{n3RDmkC;9d!Yx3O7n?9,[CE;TWB! F8.e5fc0dJXikU'v1qFVTfptB7xe$y*t#jx4`I44n,ypMQg@.|Z^ycJ:G]{dR~E}_.T1^shwC%T4eRGVu%h+J7lBzb>m20==Q*OPAf^~@6Lj^)rI9Tb*m*L}}HC~{> /__Od\I=[|aP6s}B%BhqtE-9uGJ0J3jchjcyJz5fW[i0$RfPv7Zp=!a+0pR Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : i) the TP560 dislikes apm in -current .. with or without the "broken stat : clock" option it'll panic :-( similarly the 760. a short amount of time spent looking suggests that the panic actually occurs when the kernel first attempts to call into the apm bios (ie. through the selector generated as a result of the int15 call). power management seems to work fine in win95 (surprise !) and sco openserver 5.0 (surprise !!). i'm considering whether or not i should look at the 5.0 code to see what it does... i sent mail to hosakawa, but i've not heard anything back yet. : ii) has anyone run X on this thing ? SuperProbe reports .. 3.1.2E runs ok-ish on the 760, which is also a trident, but a 9320LCD. : iii) if I enable the pccard support, the zp0 driver stops seeing the 3c589 : and the system reports a "device allocation failure" (I assume that I'd need : to either wire in the nep driver or redefine the stuff in /etc/pccard.conf : to point at the zp driver) .. suggestions ? i used the nep driver. : iv) if I revert to the 2.1R code + pccard-test package, apm will simply hang : the machine (power-off by removing battery :-() and the nep0 driver pulls : the "link OK" on my hub at unpredictable intervals. "ifconfig nep0 down" : followed by "ifconfig nep0 up" restores normal operation .. for a while .. never tried the 2.1 code on this machine. From owner-freebsd-current Mon Jul 8 02:13:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA19607 for current-outgoing; Mon, 8 Jul 1996 02:13:30 -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 CAA19602 for ; Mon, 8 Jul 1996 02:13:27 -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 CAA20066; Mon, 8 Jul 1996 02:10:28 -0700 (PDT) To: faried nawaz cc: current@freebsd.org Subject: Re: `file', BSD/i386 In-reply-to: Your message of "Mon, 08 Jul 1996 01:29:06 PDT." <20714.836814546@waldrog.cs.uidaho.edu> Date: Mon, 08 Jul 1996 02:10:27 -0700 Message-ID: <20064.836817027@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk And this is correct. Since it's apparently hard to tell some of the various *BSD binaries apart, they're now lumped into a more generic category. Better than having them idenfied as NetBSD or PDP-11 execs/binaries now, I guess. :-) Jordan > > Hi, > > All my executables are being recognized as BSD/i386: > > ; file /bin/ls > /bin/ls: BSD/i386 compact demand paged executable > ; file /usr/local/bin/bash > /usr/local/bin/bash: BSD/i386 compact demand paged dynamically linked executa ble > ; file /usr/bin/man > /usr/bin/man: BSD/i386 compact demand paged dynamically linked executable > ; > > I last sup'd on Saturday, July 6th. > > > faried. From owner-freebsd-current Mon Jul 8 05:35:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA01112 for current-outgoing; Mon, 8 Jul 1996 05:35:34 -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 FAA01088; Mon, 8 Jul 1996 05:35:20 -0700 (PDT) Received: from fakir.india.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA226519307; Mon, 8 Jul 1996 05:35:12 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA012779468; Mon, 8 Jul 1996 18:07:48 +0530 Message-Id: <199607081237.AA012779468@fakir.india.hp.com> To: hackers@freebsd.org, current@freebsd.org Subject: HP PC Lan+ support for -current "ed" driver Date: Mon, 08 Jul 1996 18:07:47 +0530 From: A JOSEPH KOSHY Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've placed the following files comprising a `diff' to the -current "ed" driver sources that add support for the HP PC LAN Plus series of ISA ethernet cards in the incoming directory on `ftp.freebsd.org'. ftp://ftp.freebsd.org/pub/FreeBSD/incoming/ -rwxr-xr-x 1 201 1 26719 Jul 8 12:21 HP-PCLan-Plus-1.101.diff -rwxr-xr-x 1 201 1 4362 Jul 8 12:22 HP-PCLan-Plus.README Some excerpts from the README file: ---------------------------------------------------------------- HP PCLAN+ README ================ This diff adds support for the HP PC Lan+ cards (model numbers: 27247B and 27252A) in FreeBSD's `ed' driver. The diff has been placed on: ftp://ftp.freebsd.org/pub/FreeBSD/incoming/HP-PCLan-Plus-1.101.diff This diff is wrt -current as of 8th July 1996. Some information about the card ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The HP PCLan+ cards are based on the popular NSDP8390, with an ASIC core controlling access to the NIC. The card supports PIO data transfers and also has a memory-mapped I/O mode where the data register gets aliased into memory space at even addresses. This allows a `rep movsl' instruction to copy out data from card ram speedily. Performance of the cards is good --- I'm able to saturate ethernet bandwidth running on a P-90 ISA system. The performance difference between the PIO and MIO modes is not significant on my system, so I prefer the PIO modes as it lessens the chance of a conflict with other hardware on the machine. The driver has been stable for the past few months. I've tested it out against a number of variations of the HP cards; the AUI, and Cheapernet (but not the TP) interfaces have been tested. Most of the testing has been using the PIO transfer mode supported by the card. Memory mapped I/O mode has been used much less. ... Credits ======= I would like to thank Russell Nelson for making freely available his CRYNWR packet collection. I also would like to thank Gerald Talbott, for pointing me in the right direction when I got stuck. ... (Semi-)Legal Stuff ================== *) I'm submitting these mods as my individual effort. This work had no connection with my employer Hewlett-Packard at all. *) I'm submitting this code ``AS IS'' and cannot vouchsafe ANYTHING about its useability or fitness for any purpose. (#include ) ... ---------------------------------------------------------------- Joseph Koshy HP International Software Operation, Bangalore, India. Email: , Telnet: 847-1020, Phone: +91-80-2251554 ext 211 These are my personal opinions. From owner-freebsd-current Mon Jul 8 06:38:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04322 for current-outgoing; Mon, 8 Jul 1996 06:38:29 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA04315 for ; Mon, 8 Jul 1996 06:38:25 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id JAA18596; Mon, 8 Jul 1996 09:32:15 -0400 (EDT) Date: Mon, 8 Jul 1996 09:32:15 -0400 (EDT) From: Brian Tao To: "Andrew V. Stesin" cc: FREEBSD-CURRENT-L Subject: "ifconfig -arp" doesn't work? In-Reply-To: <199607080551.IAA05292@office.elvisti.kiev.ua> 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, 8 Jul 1996, Andrew V. Stesin wrote: > > Dear Brian, if this approach will work for you, > please, share your experience with us. (I didn't > think about a situation with an "untrusted inside host" before, > so I'm interested what the solution might be) Andrew is referring to the "-arp" switch to ifconfig. I had asked if it was possible for an Ethernet interface not to broadcast its MAC address in response to an ARP query. Unfortunately, it doesn't seem to work. :( slam.io.org is the name of the firewall from the outside, and zap.io.org is one of our public shell servers. Even with NOARP, another server is still able to record slam's MAC address. I was thinking of turning off broadcasts, but that would probably mess others things up even more. slam is 2.2-960612-SNAP, zap is 2.2-960501-SNAP. slam# ifconfig de0 de0: flags=88c3 mtu 1500 inet 198.133.36.2 netmask 0xffffff00 broadcast 198.133.36.255 ether 00:00:c0:53:c8:db zap# arp -a | grep slam zap# ping slam.io.org PING slam.io.org (198.133.36.2): 56 data bytes ^C --- slam.io.org ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss # arp -a | fgrep slam slam.io.org (198.133.36.2) at 0:0:c0:53:c8:db -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Mon Jul 8 07:56:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA09415 for current-outgoing; Mon, 8 Jul 1996 07:56:09 -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 HAA09377 for ; Mon, 8 Jul 1996 07:56:02 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA12763; Mon, 8 Jul 1996 08:55:46 -0600 (MDT) Date: Mon, 8 Jul 1996 08:55:46 -0600 (MDT) Message-Id: <199607081455.IAA12763@rocky.mt.sri.com> From: Nate Williams To: dave edmondson Cc: michael butler , current@freebsd.org Subject: re: Thinkpad 560 + -current In-Reply-To: <199607080859.JAA00205@zero-gravity.netlab.london.sco.com> References: <199607070851.SAA29180@asstdc.scgt.oz.au> <199607080859.JAA00205@zero-gravity.netlab.london.sco.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > : i) the TP560 dislikes apm in -current .. with or without the "broken stat > : clock" option it'll panic :-( > > similarly the 760. a short amount of time spent looking suggests that > the panic actually occurs when the kernel first attempts to call into > the apm bios (ie. through the selector generated as a result of the > int15 call). power management seems to work fine in win95 (surprise > !) and sco openserver 5.0 (surprise !!). i'm considering whether or > not i should look at the 5.0 code to see what it does... i sent mail > to hosakawa, but i've not heard anything back yet. I've been the 'new' keeper of the APM code recently and fixed numerous bugs in the -current driver, although I have a *very* limited amount of time to hack given that the Missouri river is now running about 6K CFM, which means that fly fishing is *prime* right now. :) > : iii) if I enable the pccard support, the zp0 driver stops seeing the 3c589 > : and the system reports a "device allocation failure" (I assume that I'd need > : to either wire in the nep driver or redefine the stuff in /etc/pccard.conf > : to point at the zp driver) .. suggestions ? > > i used the nep driver. Can you try the ep driver in -current? Nate From owner-freebsd-current Mon Jul 8 08:13:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA10851 for current-outgoing; Mon, 8 Jul 1996 08:13:12 -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 IAA10846 for ; Mon, 8 Jul 1996 08:13:10 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA04013; Mon, 8 Jul 1996 11:13:00 -0400 Date: Mon, 8 Jul 1996 11:13:00 -0400 From: Garrett Wollman Message-Id: <9607081513.AA04013@halloran-eldar.lcs.mit.edu> To: Peter Wemm Cc: Wolfram Schneider , current@freebsd.org Subject: Re: rcs keyword '$FreeBSD: $' disabled In-Reply-To: <199607071414.WAA28208@spinner.DIALix.COM> References: <199607071154.NAA02993@campa.panke.de> <199607071414.WAA28208@spinner.DIALix.COM> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > Because that was only part of the story.. There were corresponding > modifications to CVS as well, but it turned out to be a problem that was > more trouble that it was worth at the time, so it never was reimplemented. The way we (here) use this feature, no CVS modifications are necessary. In addition to enabling and renaming the `FreeBSD' keyword, I added the following two lines of code to `co''s `main': if (getenv("ANAKEYWORD")) setIncExc("-KiANA"); The developers supposedly know to set the ANAKEYWORD environment variable, and everyone else can just ignore it. I hope that this code isn't going away, or I'll have to hack it back in... -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jul 8 09:33:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA16429 for current-outgoing; Mon, 8 Jul 1996 09:33:24 -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 JAA16420 for ; Mon, 8 Jul 1996 09:33:22 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA02857; Mon, 8 Jul 1996 12:33:19 -0400 Date: Mon, 8 Jul 1996 12:33:19 -0400 From: Garrett Wollman Message-Id: <9607081633.AA02857@halloran-eldar.lcs.mit.edu> To: Brian Tao Cc: "Andrew V. Stesin" , FREEBSD-CURRENT-L Subject: "ifconfig -arp" doesn't work? In-Reply-To: References: <199607080551.IAA05292@office.elvisti.kiev.ua> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > Andrew is referring to the "-arp" switch to ifconfig. I had asked > if it was possible for an Ethernet interface not to broadcast its MAC > address in response to an ARP query. Unfortunately, it doesn't seem > to work. :( Well, you can add the following to the beginning of if_ether.c:in_arpinput(): if (ac->ac_if.if_flags & IFF_NOARP) { m_freem(m); return; } -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jul 8 09:41:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA16919 for current-outgoing; Mon, 8 Jul 1996 09:41:36 -0700 (PDT) Received: from rich.isdn.bcm.tmc.edu (root@RICH.ISDN.BCM.TMC.EDU [128.249.250.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA16913 for ; Mon, 8 Jul 1996 09:41:33 -0700 (PDT) Received: from richc.isdn.bcm.tmc.edu (root@richc.isdn.bcm.tmc.edu [128.249.250.37]) by rich.isdn.bcm.tmc.edu (8.7.5/8.6.12) with ESMTP id LAA03251 for ; Mon, 8 Jul 1996 11:41:32 -0500 (CDT) Received: (rich@localhost) by richc.isdn.bcm.tmc.edu (8.7.5/8.6.12) id LAA07885; Mon, 8 Jul 1996 11:41:31 -0500 (CDT) Date: Mon, 8 Jul 1996 11:41:31 -0500 (CDT) Message-Id: <199607081641.LAA07885@richc.isdn.bcm.tmc.edu> From: Rich Murphey To: current@freebsd.org In-reply-to: (message from Michael Hancock on Mon, 8 Jul 1996 14:49:46 +0900 (JST)) Subject: Re: Is it just my imagination? Reply-to: rich@rich.isdn.bcm.tmc.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Speaking of netscape, has anyone been able to use the editor? Both the old (5) and new (5a) bsdi binaries core when I select the editor and I'm wondering if it's just me. Ktrace showed syscalls repeatedly returning 'resource unavailable' before it cores, but it's not a stack or data size problem. Rich From owner-freebsd-current Mon Jul 8 10:03:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18134 for current-outgoing; Mon, 8 Jul 1996 10:03:29 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18129 for ; Mon, 8 Jul 1996 10:03:25 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id DAA00244 Tue, 9 Jul 1996 03:02:58 +1000 (EST) From: michael butler Message-Id: <199607081702.DAA00244@walkabout.asstdc.com.au> Subject: Re: Thinkpad 560 + -current To: nate@mt.sri.com (Nate Williams) Date: Tue, 9 Jul 1996 03:02:58 +1000 (EST) Cc: davided@sco.com, imb@scgt.oz.au, current@FreeBSD.ORG In-Reply-To: <199607081455.IAA12763@rocky.mt.sri.com> from Nate Williams at "Jul 8, 96 08:55:46 am" 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 > > : iii) if I enable the pccard support, the zp0 driver stops seeing the > > : 3c589 and the system reports a "device allocation failure" (I assume > > : that I'd need to either wire in the nep driver or redefine the stuff > > : in /etc/pccard.conf to point at the zp driver) .. suggestions ? > > i used the nep driver. > Can you try the ep driver in -current? I "tweaked" /etc/pccard.conf to point at the ep driver and, lo and behold, it works ! Promiscuous mode is much better than the zp driver BTW .. I can actually see traffic on my ether belonging to one of the other nets floating around on it (which I couldn't before), michael From owner-freebsd-current Mon Jul 8 10:05:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18382 for current-outgoing; Mon, 8 Jul 1996 10:05: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 KAA18371 for ; Mon, 8 Jul 1996 10:05:30 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA13563; Mon, 8 Jul 1996 11:05:19 -0600 (MDT) Date: Mon, 8 Jul 1996 11:05:19 -0600 (MDT) Message-Id: <199607081705.LAA13563@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Thinkpad 560 + -current In-Reply-To: <199607081702.DAA00244@walkabout.asstdc.com.au> References: <199607081455.IAA12763@rocky.mt.sri.com> <199607081702.DAA00244@walkabout.asstdc.com.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk michael butler writes: > > > : iii) if I enable the pccard support, the zp0 driver stops seeing the > > > : 3c589 and the system reports a "device allocation failure" (I assume > > > : that I'd need to either wire in the nep driver or redefine the stuff > > > : in /etc/pccard.conf to point at the zp driver) .. suggestions ? > > > > i used the nep driver. > > > Can you try the ep driver in -current? > > I "tweaked" /etc/pccard.conf to point at the ep driver and, lo and behold, > it works ! Promiscuous mode is much better than the zp driver BTW .. I can > actually see traffic on my ether belonging to one of the other nets floating > around on it (which I couldn't before), Hot diggity dog! Glad to hear it. The if_ep driver is generally 'better' than the if_zp driver since I've been the only one bringing over bug-fixes to the if_zp driver, and I haven't been very dedicated to the task. In any case, if_zp will be gone by the time 2.2 is released when we have the ability to install via the PC-CARD stuff. Nate From owner-freebsd-current Mon Jul 8 10:06:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18475 for current-outgoing; Mon, 8 Jul 1996 10:06:23 -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 KAA18456 for ; Mon, 8 Jul 1996 10:06:18 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA13585; Mon, 8 Jul 1996 11:06:10 -0600 (MDT) Date: Mon, 8 Jul 1996 11:06:10 -0600 (MDT) Message-Id: <199607081706.LAA13585@rocky.mt.sri.com> From: Nate Williams To: Garrett Wollman Cc: FREEBSD-CURRENT-L Subject: Re: "ifconfig -arp" doesn't work? In-Reply-To: <9607081633.AA02857@halloran-eldar.lcs.mit.edu> References: <199607080551.IAA05292@office.elvisti.kiev.ua> <9607081633.AA02857@halloran-eldar.lcs.mit.edu> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Andrew is referring to the "-arp" switch to ifconfig. I had asked > > if it was possible for an Ethernet interface not to broadcast its MAC > > address in response to an ARP query. Unfortunately, it doesn't seem > > to work. :( > > Well, you can add the following to the beginning of > if_ether.c:in_arpinput(): > > if (ac->ac_if.if_flags & IFF_NOARP) { > m_freem(m); > return; > } Should this code be committed to -current? Nate From owner-freebsd-current Mon Jul 8 10:49:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25180 for current-outgoing; Mon, 8 Jul 1996 10:49:41 -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 KAA25175 for ; Mon, 8 Jul 1996 10:49:39 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA00653; Mon, 8 Jul 1996 13:49:34 -0400 Date: Mon, 8 Jul 1996 13:49:34 -0400 From: Garrett Wollman Message-Id: <9607081749.AA00653@halloran-eldar.lcs.mit.edu> To: Nate Williams Cc: Garrett Wollman , FREEBSD-CURRENT-L Subject: Re: "ifconfig -arp" doesn't work? In-Reply-To: <199607081706.LAA13585@rocky.mt.sri.com> References: <199607080551.IAA05292@office.elvisti.kiev.ua> <9607081633.AA02857@halloran-eldar.lcs.mit.edu> <199607081706.LAA13585@rocky.mt.sri.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: >> if (ac->ac_if.if_flags & IFF_NOARP) { >> m_freem(m); >> return; >> } > Should this code be committed to -current? Well, that's problematic. There are a number of different meanings one could attribute to IFF_NOARP: 1) Ignore incoming ARP requests. 2) Do not send ARP requests. 3) Do not do any ARP processing at all. The fragment above only attempts to implement (1), and I have no idea whether it actually works or not. I don't know what other systems do. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jul 8 10:54:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25496 for current-outgoing; Mon, 8 Jul 1996 10:54:37 -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 KAA25491 for ; Mon, 8 Jul 1996 10:54:33 -0700 (PDT) Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id MAA05575; Mon, 8 Jul 1996 12:54:23 -0500 (CDT) Message-Id: <199607081754.MAA05575@sierra.zyzzyva.com> To: rich@rich.isdn.bcm.tmc.edu cc: current@freebsd.org Subject: Re: Is it just my imagination? In-reply-to: rich's message of Mon, 08 Jul 1996 11:41:31 -0500. <199607081641.LAA07885@richc.isdn.bcm.tmc.edu> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Jul 1996 12:54:23 -0500 From: Randy Terbush Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Speaking of netscape, has anyone been able to use the > editor? > > Both the old (5) and new (5a) bsdi binaries core when I > select the editor and I'm wondering if it's just me. > Ktrace showed syscalls repeatedly returning 'resource > unavailable' before it cores, but it's not a stack or > data size problem. Rich Both b4 and b5a have worked here with relatively few problems. I'm running -stable From owner-freebsd-current Mon Jul 8 15:29:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13409 for current-outgoing; Mon, 8 Jul 1996 15:29:57 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13404 for ; Mon, 8 Jul 1996 15:29:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA22643; Mon, 8 Jul 1996 15:24:52 -0700 From: Terry Lambert Message-Id: <199607082224.PAA22643@phaeton.artisoft.com> Subject: Re: Which tools can back up inodes with 32bit minor numbers ? To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Mon, 8 Jul 1996 15:24:52 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, current@freebsd.org In-Reply-To: <199607071744.NAA15262@skynet.ctr.columbia.edu> from "Bill Paul" at Jul 7, 96 01:44:20 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 > > Well, as i wrote, the existing static /dev is about to be killed > > anytime soon. MAKEDEV as well -- shouldn't you have it already > > noticed. > > Wrong. > > The existing /dev and MAKEDEV are _not_ going away any time soon. > Not on any of the systems I maintain anyway (including my personal > machines at home). You'll never catch me putting 'options DEVFS' in > any of my kernel config files. And the day it changes from optional > to mandatory is the day I stop running FreeBSD. What?!? Why?!? > Sun already burned me with their "we're giving you these new features > whether you like them or not" attitude. I'm not letting anyone else > force any unwanted innovation down my throat if I can avoid it, even > if it doesn't cost me any money. This is pure silliness... pointing to an ugly baby does not imply that all babies are ugly. For one thing, FreeBSD has already gone to 32 bit values. The known drawbacks are: 1) Archive tools have problems with 32 bit minors. 2) V3 NFS has problems with 32 bit minors. 3) You must use a FreeBSD system on the other end of the wire for a netboot. 4) ISOFS has problems with 32 bit minors (no bootable cdroms) 5) exports of /dev can be damaging/cryptic to remote systems other than FreeBSD systems, which are mounting FreeBSD exported resources. In general, the problems with /dev and MAKEDEV are: 1) /dev directory contents are synchronized with kernel configuration using a human and MAKEDEV, either of which (the human or the MAKEDEV) can fail to operate correctly. 2) You are required to have working disk drivers and FS mounts working to do a port to a new platform. 3) You can't support DOS partitioning in a consistent manner. 4) You can't support BSD partitioning (disklabel) in a consistent manner. 5) You can't support CCD partitioning (volume spanning) in a consistent manner. 6) You have to rebuild /dev each time you boot up a kernel with a different configuration. 7) There has to be a central authority for assigning major numbers (the main ammunition for "closed developement" arguments used by Linux fanatics). 8) Loadable device drivers have to be externally synchronized with a MAKEDEV at load time to produce valid devie nodes. 9) No support for transient device availability (PCMCIA cards, "docking", removable media, transportable devices (ZIP drives via parallel port, tape drives, etc.). 10) No support for "fail safe" recovery in face of device failure for a system-critical device. If you can propose a way around these 14 items (this is just off the top of my head; my engineering pad with nearly double this number is at home right now), we will be happy to listen to you. For what it's worth, I think Sun *did* screw up with their "hybrid" approach, which is what everyone is trying to force on us through the consideration of symlinks and user-provided hard links. There is nothing to say, however, that the "MAKEDEV" could not operate by creating symlinks in the "/dev" directory to the "/devfs", letting you keep your old hat without robbing the rest of us of the benefits. However, I have to say that static major and minor number assignment was a design error, and it needs to go away, one way or the other, no matter how we end up implementing it. > Getting back to the subject at hand, dump and restore are > supposed to preserve _everything_, including 32-bit major/minor > values (we got 'em, we gotta deal with 'em). Ideally, tar and cpio > should too. If they don't, they should be made to, but only if their > archive formats allow it without breaking compatibility with all the > other tar and cpio implementations on the planet. If dump and restore > aren't doing it, they are broken and need to be fixed. DEVFS doesn't > enter into it. DEVFS enters into it only in as much as a devfs's contents should be non-archivable. Since it is locally generated, it does not need to be expressed in an NFS export. One issue to consider: A devfs that does not operate by major/minor is useful for sharing device nodes over a network mount with no additional changes necessary. An NFS vnode is an alias for vnode operations to be transported to the remote system. For a devfs, since the device references are vnodes rather than major/minor pair, the operations on the device are transportable to a remote system. 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 Mon Jul 8 15:50:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14732 for current-outgoing; Mon, 8 Jul 1996 15:50:20 -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 PAA14725 for ; Mon, 8 Jul 1996 15:50:17 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14637(5)>; Mon, 8 Jul 1996 15:49:37 PDT Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177476>; Mon, 8 Jul 1996 15:49:29 -0700 X-Mailer: exmh version 1.6.7 5/3/96 To: Garrett Wollman cc: Nate Williams , FREEBSD-CURRENT-L Subject: Re: "ifconfig -arp" doesn't work? In-reply-to: Your message of "Mon, 08 Jul 1996 10:49:34 PDT." <9607081749.AA00653@halloran-eldar.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 8 Jul 1996 15:49:17 PDT From: Bill Fenner Message-Id: <96Jul8.154929pdt.177476@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <9607081749.AA00653@halloran-eldar.lcs.mit.edu>you write: >There are a number of different meanings >one could attribute to IFF_NOARP: > > 1) Ignore incoming ARP requests. > 2) Do not send ARP requests. > 3) Do not do any ARP processing at all. > >The fragment above only attempts to implement (1) It actually ignores both requests and replies, so the effect is more like (3) (although it does send ARP requests, it will ignore the replies so they're completely ineffective). To actually implement (1) you need to put the "if" after the "reply:" label (potentially combining it with the one that's already there). I would have added "and don't let incoming ARP's change my table" to (2). Bill From owner-freebsd-current Mon Jul 8 16:06:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA16357 for current-outgoing; Mon, 8 Jul 1996 16:06:13 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA16351 for ; Mon, 8 Jul 1996 16:06:08 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id AAA26053; Tue, 9 Jul 1996 00:03:31 +0100 (BST) To: Terry Lambert cc: wpaul@skynet.ctr.columbia.edu (Bill Paul), joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Which tools can back up inodes with 32bit minor numbers ? In-reply-to: Your message of "Mon, 08 Jul 1996 15:24:52 PDT." <199607082224.PAA22643@phaeton.artisoft.com> Date: Tue, 09 Jul 1996 00:03:30 +0100 Message-ID: <26051.836867010@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote in message ID <199607082224.PAA22643@phaeton.artisoft.com>: > 2) You are required to have working disk drivers and FS > mounts working to do a port to a new platform. I'm curious about this one. Having worked on a port of FreeBSD to another platform (which admitedly died, but that was due to lack of time, not entheusiasm), it seems working filesystems and disk drivers are a fairly major priority, as once you have reached the end of init_main(), you NEED to access a filesystem of some sort to load init and get booting. Ok, so I cheated a bit, and compiled in a 1Mb MFS root filesystem just to get going, but having a root FS in memory does NOT remove the requirement for having a disk-based filesystem, unless you plan to have a fairly large (say, enough to hold the bin dist :-) ) root filesystem in core! And having devfs doesn't really remove the need at all, as during the inital bootstrap stages when you are still working on getting the system tied together, you can use whatever major/minor number pairs you like, and just tweak them to be more sensible later... Ok, so devfs may make it a bit easier (maybe, it's another kernel interface to learn), but I can't see it as a plus in devfs's favour, nor particularly cut down on development time. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Mon Jul 8 17:01:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA23042 for current-outgoing; Mon, 8 Jul 1996 17:01:39 -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 RAA23024; Mon, 8 Jul 1996 17:01:36 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA23056; Mon, 8 Jul 1996 16:57:47 -0700 From: Terry Lambert Message-Id: <199607082357.QAA23056@phaeton.artisoft.com> Subject: Re: Which tools can back up inodes with 32bit minor numbers ? To: gpalmer@freebsd.org (Gary Palmer) Date: Mon, 8 Jul 1996 16:57:47 -0700 (MST) Cc: terry@lambert.org, wpaul@skynet.ctr.columbia.edu, joerg_wunsch@uriah.heep.sax.de, current@freebsd.org In-Reply-To: <26051.836867010@palmer.demon.co.uk> from "Gary Palmer" at Jul 9, 96 00:03:30 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 > > 2) You are required to have working disk drivers and FS > > mounts working to do a port to a new platform. > > I'm curious about this one. Having worked on a port of FreeBSD to > another platform (which admitedly died, but that was due to lack of > time, not entheusiasm), it seems working filesystems and disk drivers > are a fairly major priority, as once you have reached the end of > init_main(), you NEED to access a filesystem of some sort to load init > and get booting. > > Ok, so I cheated a bit, and compiled in a 1Mb MFS root filesystem just > to get going, but having a root FS in memory does NOT remove the > requirement for having a disk-based filesystem, unless you plan to > have a fairly large (say, enough to hold the bin dist :-) ) root > filesystem in core! And having devfs doesn't really remove the need at > all, as during the inital bootstrap stages when you are still working > on getting the system tied together, you can use whatever major/minor > number pairs you like, and just tweak them to be more sensible > later... > > Ok, so devfs may make it a bit easier (maybe, it's another kernel > interface to learn), but I can't see it as a plus in devfs's favour, > nor particularly cut down on development time. Try doing the port in a cross-environment, where you can't put 32 bit values as an argument for your mknod. 8-). The priorities are, in order: 1) Method of loading code in and jumping to it. This can be as a file in the root of another OS's fs (oh, for instance, AIX on the PPC). Generally bootp. 2) A working console (hello world), generally a polled UART driver. 3) A minimally working kernel... NOT including device drivers for anything but the console -- so devfs and an in-core image for sh to be executed (instead of init). [...] For most systems (non-Intel) that support netboot, you can load in any image via bootp and jump to it. I have to say in general it is easier to make a UART work in polled mode than practically anything else for console input/output. 8-). The devfs gives me the portable pseudo-devices (null, zero, etc.) without need to really support any real devices (besides tty/console). It's quite handy. I'd say the MFS and a real init were about #7 or #8 on the list. The bear is #3, since it includes a stupid VM (we should have a stupid VM in C that ignores most of the hardware to use in bootstrapping, don't you think? -- basically everything in /sys/i386 should have a nice generic C counterpart to aid rewriting. Save the assmebly crap for the no-other-way-to-do-it glue and later in the port as the system rides closer to the hardware where it can). 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 Jul 8 19:51:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA28190 for current-outgoing; Mon, 8 Jul 1996 19:51:15 -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 TAA28143; Mon, 8 Jul 1996 19:51:05 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id CAA19338; Tue, 9 Jul 1996 02:51:02 GMT Date: Tue, 9 Jul 1996 11:51:02 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: freebsd-current@FreeBSD.ORG cc: freebsd-scsi@FreeBSD.ORG Subject: Adding Jaz drive with sysinstall 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 managed to create a FreeBSD partition using sysinstall's custom install. But sysinstall wouldn't label it. After 'W'ing the partition changes and entering the label screen I kept getting a "You must partition the disk" error when trying to Write the label. I ended up creating a DOS partition and a FreeBSD partition on the Jaz cartridge using sysinstall and then running disklabel -r sd2 to see what raw device it reported. I then newfs'ed the device manually. It's a pretty fast device, I set MAKEOBJDIR to /jaz and did a make world on it and it wasn't that bad. dmesg tells me that the Jaz reports that its a removable SCSI 2. Is this the source of the ILLEGAL REQUEST message? FreeBSD 2.2-CURRENT #11: Wed Jul 3 12:45:46 JST 1996 (ncr0:5:0): "iomega jaz 1GB G.60" type 0 removable SCSI 2 sd2(ncr0:5:0): Direct-Access sd2(ncr0:5:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd2(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry 1021MB (2091050 512 byte sectors) From owner-freebsd-current Mon Jul 8 20:07:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA29966 for current-outgoing; Mon, 8 Jul 1996 20:07:40 -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 UAA29931; Mon, 8 Jul 1996 20:07:34 -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 UAA04582; Mon, 8 Jul 1996 20:06:51 -0700 (PDT) To: Michael Hancock cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Adding Jaz drive with sysinstall In-reply-to: Your message of "Tue, 09 Jul 1996 11:51:02 +0900." Date: Mon, 08 Jul 1996 20:06:51 -0700 Message-ID: <4580.836881611@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I managed to create a FreeBSD partition using sysinstall's custom install. > But sysinstall wouldn't label it. After 'W'ing the partition changes and > entering the label screen I kept getting a "You must partition the disk" > error when trying to Write the label. Ah, I think I just found and smashed that one - thanks for making me look again.. :-) Jordan From owner-freebsd-current Mon Jul 8 21:21:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA09948 for current-outgoing; Mon, 8 Jul 1996 21:21:17 -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 VAA09931; Mon, 8 Jul 1996 21:21:12 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id EAA19943; Tue, 9 Jul 1996 04:20:50 GMT Date: Tue, 9 Jul 1996 13:20:50 +0900 (JST) From: Michael Hancock To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.org, freebsd-scsi@FreeBSD.org Subject: Re: Adding Jaz drive with sysinstall In-Reply-To: <4580.836881611@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 Mon, 8 Jul 1996, Jordan K. Hubbard wrote: > > I managed to create a FreeBSD partition using sysinstall's custom install. > > But sysinstall wouldn't label it. After 'W'ing the partition changes and > > entering the label screen I kept getting a "You must partition the disk" > > error when trying to Write the label. > > Ah, I think I just found and smashed that one - thanks for making me look > again.. :-) Cool. One more observation. When I want to add a new drive the label option insists in making /, /usr/, and swap if I only have the new drive selected. Are you supposed to select all the drives and existing partitions when you use sysinstall to label? I guess it needs some way of differentiating between a new installation and a change of configuration. mike hancock From owner-freebsd-current Mon Jul 8 21:23:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA10163 for current-outgoing; Mon, 8 Jul 1996 21:23:53 -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 VAA10127; Mon, 8 Jul 1996 21:23:39 -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 VAA06320; Mon, 8 Jul 1996 21:22:51 -0700 (PDT) To: Michael Hancock cc: freebsd-current@FreeBSD.org, freebsd-scsi@FreeBSD.org Subject: Re: Adding Jaz drive with sysinstall In-reply-to: Your message of "Tue, 09 Jul 1996 13:20:50 +0900." Date: Mon, 08 Jul 1996 21:22:50 -0700 Message-ID: <6318.836886170@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Cool. One more observation. When I want to add a new drive the label > option insists in making /, /usr/, and swap if I only have the new drive > selected. Ah. Woog. That's a good point. I'll add something to disable the mandatory /, /usr and swap checks when you're adding a new drive. Jordan From owner-freebsd-current Tue Jul 9 01:47:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA19424 for current-outgoing; Tue, 9 Jul 1996 01:47:55 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA19407; Tue, 9 Jul 1996 01:47:50 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id SAA03375 Tue, 9 Jul 1996 18:47:43 +1000 (EST) From: michael butler Message-Id: <199607090847.SAA03375@walkabout.asstdc.com.au> Subject: RISCom/8 driver + NFS - experiences in Montreal To: stable@freebsd.org, current@freebsd.org Date: Tue, 9 Jul 1996 18:47:43 +1000 (EST) Cc: imb@scgt.oz.au 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 Just following up on some of the experiences from this year's ISOC developing country workshops in Montreal .. i) The RISCom/8 driver worked fine off the 2.1R CD but, when the kernel was upgraded to -stable, the kernel complained (lots!) about the mass depletion and subsequent non-availability of clists. This rendered it unusable for coursework. Unfortunately, I couldn't spend long enough to identify the actual cause of the problem (spl changes inviting race condition ?) in the 5 or so days available. ii) The upgrade to -stable was necessitated by a show-stopper in 2.1R's NFS and, even then, some serious performance problems persisted. Initially, we tried to load 30 machines concurrently over NFS (bootp then "tar xvf") and, despite a useful patch from Paul Traina, it was never actually possible to keep the ethernet saturated .. everything would back off .. long timeouts and a couple of very long nights :-(. Reducing the number of concurrent loads to the student machines helped slightly but did not cure the problem (nor did installing ether switches instead of hubs). Switching to NFS over TCP didn't help or reducing the read and write sizes to 1kb. The machine from which the loads were done was dual-homed for logistic reasons if that holds any clues. Also required for the classes (and now in -stable) was the multicast support for the 3C509 (thanks for the timing on this one!) .. OSPF with gated was taught in place of RIP (although it was mentioned in the context of "you don't want to do this" :-)). This could not have been done on 2.1R. Some "idiosyncracies" with gated were noted and taken on-board by the maintainers. Next year, it seems that we can dispense with BSDI totally now that John Hay's N2 driver is into -current and will hopefully propagate into the main distribution before next year. Overall, from my perspective, the whole exercise was successful and both students and instructors alike learned _lots_ from the experience .. Whilst only being a humble instructor, I'd also like to thank Jordon and his organisation publicly for their support in ensuring that each student (99 countries were represented amongst them) took home a FreeBSD CD. I'd like to use it again next year and have suggested so on the workshop admin list, Many, many thanks, michael From owner-freebsd-current Tue Jul 9 03:43:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA27096 for current-outgoing; Tue, 9 Jul 1996 03:43:27 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA27089 for ; Tue, 9 Jul 1996 03:43:16 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id LAA06167 for ; Tue, 9 Jul 1996 11:47:22 +0100 Date: Tue, 9 Jul 1996 11:47:22 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: A couple of problems!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ive just updated a freebsd system from V2.1 to freebsd-current (v2.2) and I'm having a few minor, but very annoying problems:- 1) Ive had to revert to an older termcap (From v2.0) because the ls command in xterms seems to think that the window is 1 character larger than it is and messes up all the formatting. 2) The man pages do not format correctly anymore.. I get some weird control stuff on screen instead of it showing up correctly.. it's like this:- to....so..uoe.temp.sO doc-syms NAME ls SYNOPSIS ls [FlACFLRTacdfiloqrstu1] [Arfile...] DESCRIPTION For each operand that names a file of a type other than directory, ls displays its name as well as any requested, associated information. For << SNIP >> 3) I can't compile the new version of flex.. I get this error:- lex -t -is scan.l > scan.tmp.c "scan.l", line 68: bad character: % "scan.l", line 69: unknown error processing section 1 "scan.l", line 69: bad character: % "scan.l", line 70: unknown error processing section 1 *** Error code 1 Stop. Other than that I think it's running really well:) Any answers on these problems would be very useful. Please could you reply by email. Thanks in Advance. Trefor S. From owner-freebsd-current Tue Jul 9 04:12:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29374 for current-outgoing; Tue, 9 Jul 1996 04:12:24 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA29367 for ; Tue, 9 Jul 1996 04:12:18 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id VAA00328 Tue, 9 Jul 1996 21:11:52 +1000 (EST) From: michael butler Message-Id: <199607091111.VAA00328@walkabout.asstdc.com.au> Subject: Re: Thinkpad 560 + -current To: nate@mt.sri.com (Nate Williams) Date: Tue, 9 Jul 1996 21:11:52 +1000 (EST) Cc: imb@scgt.oz.au, current@freebsd.org In-Reply-To: <199607081705.LAA13563@rocky.mt.sri.com> from Nate Williams at "Jul 8, 96 11:05:19 am" 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 > Hot diggity dog! Glad to hear it. The if_ep driver is generally > 'better' than the if_zp driver since I've been the only one bringing > over bug-fixes to the if_zp driver, and I haven't been very dedicated to > the task. In any case, if_zp will be gone by the time 2.2 is released > when we have the ability to install via the PC-CARD stuff. It "feels" much more solid too .. I've now done substantial ftp and NFS traffic across it and it's not complained or fallen over. A couple of outstanding concerns .. whilst "lsdev" lists the driver (and calls the card a 3C509 :-)) snmpd doesn't seem to be happy about it and dumps core. The actual message is .. pid 312 (snmpd), uid 0: exited on signal 8 .. when I try an snmpbulkwalk (this is UCD-SNMP). Back onto the apm stuff .. with APM_DEBUG defined, I get .. FreeBSD 2.2-CURRENT #0: Tue Jul 9 18:15:52 EST 1996 root@walkabout.asstdc.com.au:/usr/src/sys/compile/WALKABOUT Calibrating clock(s) relative to mc146818A clock... i586 clock: 99725720 Hz, i8254 clock: 1193300 Hz CPU: Pentium (99.71-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x570 Stepping=0 Features=0x1bf real memory = 16777216 (16384K bytes) avail memory = 14823424 (14476K bytes) PC-Card Cirrus Logic PD672X (5 mem & 2 I/O windows) Add hook "Cirrus Logic PD672X" Add hook "Cirrus Logic PD672X" pcic: controller irq 3 Add hook "Cirrus Logic PD672X" Add hook "Cirrus Logic PD672X" Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 2 on pci0:1 vga0 rev 211 int a irq ?? on pci0:3 chip2 rev 226 int a irq ?? on pci0:19 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> Add hook "system keyboard" pccard driver ed added ed0 not found at 0x280 pccard driver sio added sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 not found at 0x2f8 lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x63 irq 12 on motherboard fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B 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 pccard driver ep added ep0 not found at 0x300 ze: slot 0: no card in slot ze: slot 1: no card in slot ze0 not found at 0x300 zp: slot 0: no card in slot zp: slot 1: no card in slot zp0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: APM BIOS version 0101 apm: Code32 0xf00f85b0, Code16 0xf00f0000, Data 0xf009fc00 apm: Code entry 0x00000000, Idling CPU disabled, Management enabled apm: CS_limit=ffff, DS_limit=400 apm: Engaged control enabled apm: found APM BIOS version 1.1 apm: Slow Idling CPU disabled Add hook "default suspend" Add hook "default resume" called apm_event_enable() Card inserted, slot 0 ep0: utp/bnc[*UTP*] address 00:20:af:fa:df:f5 .. but when I run "apmconf -e", it prints "called apm_event_enable()" and panics. It will do so with or without PCMCIA cards inserted, michael From owner-freebsd-current Tue Jul 9 09:22:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19076 for current-outgoing; Tue, 9 Jul 1996 09:22:28 -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 JAA19071 for ; Tue, 9 Jul 1996 09:22:24 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA18241; Tue, 9 Jul 1996 10:15:02 -0600 (MDT) Date: Tue, 9 Jul 1996 10:15:02 -0600 (MDT) Message-Id: <199607091615.KAA18241@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: nate@mt.sri.com (Nate Williams), imb@scgt.oz.au, current@freebsd.org Subject: Re: Thinkpad 560 + -current In-Reply-To: <199607091111.VAA00328@walkabout.asstdc.com.au> References: <199607081705.LAA13563@rocky.mt.sri.com> <199607091111.VAA00328@walkabout.asstdc.com.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A couple of outstanding concerns .. whilst "lsdev" lists the driver (and > calls the card a 3C509 :-)) snmpd doesn't seem to be happy about it and > dumps core. The actual message is .. > > pid 312 (snmpd), uid 0: exited on signal 8 > > .. when I try an snmpbulkwalk (this is UCD-SNMP). Hmm, I can't help you there. > Back onto the apm stuff .. with APM_DEBUG defined, I get .. > pccard driver ep added > ep0 not found at 0x300 > ze: slot 0: no card in slot > ze: slot 1: no card in slot > ze0 not found at 0x300 > zp: slot 0: no card in slot > zp: slot 1: no card in slot > zp0 not found at 0x300 Whoops, I'm suprised that you aren't panic'ing the machine with both sets of drivers in it (if_zp and if_ep). Remove and/or disable the if_zp and if_ze drivers since they are no longer necessary. > apm0 on isa > apm: APM BIOS version 0101 > apm: Code32 0xf00f85b0, Code16 0xf00f0000, Data 0xf009fc00 > apm: Code entry 0x00000000, Idling CPU disabled, Management enabled > apm: CS_limit=ffff, DS_limit=400 > apm: Engaged control enabled > apm: found APM BIOS version 1.1 > apm: Slow Idling CPU disabled > Add hook "default suspend" > Add hook "default resume" > called apm_event_enable() > Card inserted, slot 0 > ep0: utp/bnc[*UTP*] address 00:20:af:fa:df:f5 > > .. but when I run "apmconf -e", it prints "called apm_event_enable()" and > panics. It will do so with or without PCMCIA cards inserted, Ok, can you try rebuilding apm.c with 'APM_DSVALUE_BUG' defined? Note, someone just pointed out a possible bug that may be affecting alot of folks but I need to track it down first, so I spent the night updating my 755C to -current. I'll be testing out a possible fix for the bug on both my NEC and works' ThinkPad. Nate From owner-freebsd-current Tue Jul 9 09:36:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19866 for current-outgoing; Tue, 9 Jul 1996 09:36: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 JAA19857 for ; Tue, 9 Jul 1996 09:36:40 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA18405; Tue, 9 Jul 1996 10:36:10 -0600 (MDT) Date: Tue, 9 Jul 1996 10:36:10 -0600 (MDT) Message-Id: <199607091636.KAA18405@rocky.mt.sri.com> From: Nate Williams To: Developer Cc: freebsd-current@freebsd.org Subject: Re: A couple of problems!! In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 3) I can't compile the new version of flex.. I get this error:- > > lex -t -is scan.l > scan.tmp.c > "scan.l", line 68: bad character: % > "scan.l", line 69: unknown error processing section 1 > "scan.l", line 69: bad character: % > "scan.l", line 70: unknown error processing section 1 > *** Error code 1 If you read the -current email, you'd know that you *must* first do a 'make bootstrap' in the lex diretory first. So # cd /usr/src/usr.bin/lex # make clean # make bootstrap # make # make install It'll work fine from then on. Nate From owner-freebsd-current Tue Jul 9 10:46:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA24280 for current-outgoing; Tue, 9 Jul 1996 10:46:43 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA24269 for ; Tue, 9 Jul 1996 10:46:37 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id DAA00936 Wed, 10 Jul 1996 03:46:03 +1000 (EST) From: michael butler Message-Id: <199607091746.DAA00936@walkabout.asstdc.com.au> Subject: Re: Thinkpad 560 + -current To: nate@mt.sri.com (Nate Williams) Date: Wed, 10 Jul 1996 03:46:02 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199607091615.KAA18241@rocky.mt.sri.com> from Nate Williams at "Jul 9, 96 10:15:02 am" 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 when I run "apmconf -e", it prints "called apm_event_enable()" > > and panics. It will do so with or without PCMCIA cards inserted, > Ok, can you try rebuilding apm.c with 'APM_DSVALUE_BUG' defined? Note, > someone just pointed out a possible bug that may be affecting alot of > folks but I need to track it down first, so I spent the night updating > my 755C to -current. I'll be testing out a possible fix for the bug on > both my NEC and works' ThinkPad. Now works (:-)) .. with APM_DEBUG still defined but superfluous devices removed .. I typed "apmconf -e" APM ioctl: cmd = 0x20005005 called apm_event_enable() Received APM Event: PMEV_NOEVENT Received APM Event: PMEV_POWERSTATECHANGE Received APM Event: PMEV_NOEVENT last message repeated 19 times Received APM Event: PMEV_POWERSTATECHANGE Received APM Event: PMEV_NOEVENT last message repeated 6 times I typed "apmconf -d" APM ioctl: cmd = 0x20005006 called apm_event_disable() YES !!!! .. thanks :-) michael From owner-freebsd-current Tue Jul 9 10:50:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA24497 for current-outgoing; Tue, 9 Jul 1996 10:50:22 -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 KAA24488 for ; Tue, 9 Jul 1996 10:50:18 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA18693; Tue, 9 Jul 1996 11:49:16 -0600 (MDT) Date: Tue, 9 Jul 1996 11:49:16 -0600 (MDT) Message-Id: <199607091749.LAA18693@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Thinkpad 560 + -current In-Reply-To: <199607091746.DAA00936@walkabout.asstdc.com.au> References: <199607091615.KAA18241@rocky.mt.sri.com> <199607091746.DAA00936@walkabout.asstdc.com.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > .. but when I run "apmconf -e", it prints "called apm_event_enable()" > > > and panics. It will do so with or without PCMCIA cards inserted, > > > Ok, can you try rebuilding apm.c with 'APM_DSVALUE_BUG' defined? Note, > > someone just pointed out a possible bug that may be affecting alot of > > folks but I need to track it down first, so I spent the night updating > > my 755C to -current. I'll be testing out a possible fix for the bug on > > both my NEC and works' ThinkPad. > > Now works (:-)) .. with APM_DEBUG still defined but superfluous devices > removed .. Hot diggity! You should be able to remove APM_DEBUG now, unless you want to debug *why* it panics when the PC-CARD stuff is enabled. We're getting there. :) Nate From owner-freebsd-current Tue Jul 9 12:02:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA28377 for current-outgoing; Tue, 9 Jul 1996 12:02:01 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA28358; Tue, 9 Jul 1996 12:01:56 -0700 (PDT) Received: by sequent.kiae.su id AA04585 (5.65.kiae-2 ); Tue, 9 Jul 1996 22:55:51 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 9 Jul 96 22:55:51 +0400 Received: (from ache@localhost) by nagual.ru (8.7.5/8.7.3) id WAA00325; Tue, 9 Jul 1996 22:52:40 +0400 (MSD) Message-Id: <199607091852.WAA00325@nagual.ru> Subject: It is impossible even for root to make core from [sg]uid process! To: current@freebsd.org (FreeBSD-current) Date: Tue, 9 Jul 1996 22:52:40 +0400 (MSD) Cc: security@freebsd.org From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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 As subject says, it is impossible even for root to debug [sg]uid program (especially daemon) without core from it. Following block from kern_sig.c stops core dump: /* * If we are setuid/setgid, or if we've changed uid's in the past, * we may be holding privileged information. We must not core! */ if (pcred->p_svuid != pcred->p_ruid || pcred->p_svgid != pcred->p_rgid) return (EFAULT); if (p->p_flag & P_SUGID) return (EFAULT); IMHO this code restricts too much: the only case it is needed for is uid 0 -> user_id transaction. It is NOT needed for user_id -> 0 transaction, because core file can be owned by root in this case with 0600 permissions. I want to frame this block: if (pcred->p_ruid) { /* non-root case */ [block] } else { /* root case */ euid = 0; /* to make program.core owned by root, 0600 */ } This fix allows core from most of daemons, because they usually started by root (ruid == 0). Any comments? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Tue Jul 9 12:19:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29300 for current-outgoing; Tue, 9 Jul 1996 12:19:16 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA29287 for ; Tue, 9 Jul 1996 12:19:11 -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 VAA21183; Tue, 9 Jul 1996 21:19:04 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA31712; Tue, 9 Jul 1996 21:18:28 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.5/keltia-uucp-2.8) id VAA03459; Tue, 9 Jul 1996 21:14:45 +0200 (MET DST) From: Ollivier Robert Message-Id: <199607091914.VAA03459@keltia.freenix.fr> Subject: Re: A couple of problems!! To: dev@fgate.flevel.co.uk (Developer) Date: Tue, 9 Jul 1996 21:14:45 +0200 (MET DST) Cc: freebsd-current@freebsd.org In-Reply-To: from Developer at "Jul 9, 96 11:47:22 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#2178 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 It seems that Developer said: > 3) I can't compile the new version of flex.. I get this error:- > > lex -t -is scan.l > scan.tmp.c > "scan.l", line 68: bad character: % > "scan.l", line 69: unknown error processing section 1 > "scan.l", line 69: bad character: % > "scan.l", line 70: unknown error processing section 1 > *** Error code 1 Do the following to bootstrap flex: make bootstrap make all install -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #12: Sun Jun 30 14:10:07 MET DST 1996 From owner-freebsd-current Tue Jul 9 12:22:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29510 for current-outgoing; Tue, 9 Jul 1996 12:22:17 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA29483; Tue, 9 Jul 1996 12:22:00 -0700 (PDT) Received: by Sisyphos id AA15665 (5.67b/IDA-1.5); Tue, 9 Jul 1996 21:20:25 +0200 Message-Id: <199607091920.AA15665@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 9 Jul 1996 21:20:25 +0200 In-Reply-To: Michael Hancock "Adding Jaz drive with sysinstall" (Jul 9, 11:51) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Michael Hancock Subject: Re: Adding Jaz drive with sysinstall Cc: current@freebsd.org, scsi@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 9, 11:51, Michael Hancock wrote: } Subject: Adding Jaz drive with sysinstall } dmesg tells me that the Jaz reports that its a removable SCSI 2. Is this } the source of the ILLEGAL REQUEST message? No, the JAZ seems not to like some field in a request sent to it and rejects the command. The command that caused this appears to have been the geometry query, which leads to the "fictious geometry" being used. A possible cause of this might be that there was no media loaded into the drive, I suppose ... } FreeBSD 2.2-CURRENT #11: Wed Jul 3 12:45:46 JST 1996 } } (ncr0:5:0): "iomega jaz 1GB G.60" type 0 removable SCSI 2 } sd2(ncr0:5:0): Direct-Access } sd2(ncr0:5:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } sd2(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB } sd2 could not mode sense (4). Using ficticious geometry } 1021MB (2091050 512 byte sectors) Regards, STefan From owner-freebsd-current Tue Jul 9 14:05:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07313 for current-outgoing; Tue, 9 Jul 1996 14:05:57 -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 OAA07012 for ; Tue, 9 Jul 1996 14:00:38 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id XAA18578 for freebsd-current@freebsd.org; Tue, 9 Jul 1996 23:57:58 +0300 (EET DST) From: Mr Operating System Message-Id: <199607092057.XAA18578@shadows.aeon.net> Subject: Re: A couple of problems!! To: freebsd-current@freebsd.org Date: Tue, 9 Jul 1996 23:57:58 +0300 (EET DST) In-Reply-To: <199607091636.KAA18405@rocky.mt.sri.com> from Nate Williams at "Jul 9, 96 10:36:10 am" 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 > If you read the -current email, you'd know that you *must* first do a > 'make bootstrap' in the lex diretory first. So > > # cd /usr/src/usr.bin/lex > # make clean > # make bootstrap > # make > # make install > > It'll work fine from then on. and when it doesnt? cd /usr/src/usr.bin/lex && make -DNOMAN -DNOPROFILE bootstrap && make -DNOMAN -DNOPROFILE all install make: don't know how to make bootstrap. Stop *** Error code 2 Stop. shadows# tried manually too, different things... no dice my machine just dont know how to 'make bootstrap' sup's about few hours old, from sup.de.freebsd.org (it has contrib now) > Nate mickey From owner-freebsd-current Tue Jul 9 14:21:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08565 for current-outgoing; Tue, 9 Jul 1996 14:21:09 -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 OAA08558 for ; Tue, 9 Jul 1996 14:21:04 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA19859; Tue, 9 Jul 1996 15:20:39 -0600 (MDT) Date: Tue, 9 Jul 1996 15:20:39 -0600 (MDT) Message-Id: <199607092120.PAA19859@rocky.mt.sri.com> From: Nate Williams To: Mr Operating System Cc: freebsd-current@freebsd.org Subject: Re: A couple of problems!! In-Reply-To: <199607092057.XAA18578@shadows.aeon.net> References: <199607091636.KAA18405@rocky.mt.sri.com> <199607092057.XAA18578@shadows.aeon.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > If you read the -current email, you'd know that you *must* first do a > > 'make bootstrap' in the lex diretory first. So > > > > # cd /usr/src/usr.bin/lex > > # make clean > > # make bootstrap > > # make > > # make install > > > > It'll work fine from then on. > > and when it doesnt? Then you aren't running current. > cd /usr/src/usr.bin/lex && make -DNOMAN -DNOPROFILE bootstrap && make -DNOMAN -DNOPROFILE all install > make: don't know how to make bootstrap. Stop > *** Error code 2 > > Stop. > shadows# > > tried manually too, different things... no dice > > my machine just dont know how to 'make bootstrap' > > sup's about few hours old, from sup.de.freebsd.org (it has contrib now) It must have an old version of lex then, but that also doesn't make sense given that it can't build w/out the bootstrap. Look at the Makefile, it should have an ID of: # $Id: Makefile,v 1.5 1996/06/19 20:46:57 nate Exp $ Nate From owner-freebsd-current Tue Jul 9 14:48:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10523 for current-outgoing; Tue, 9 Jul 1996 14:48:54 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA10515 for ; Tue, 9 Jul 1996 14:48:47 -0700 (PDT) Received: from rhiannon.scsn.net (cola43.scsn.net [206.25.247.43]) by rosie.scsn.net (post.office MTA v1.9.3b ID# 0-13529) with ESMTP id AAA178; Tue, 9 Jul 1996 17:50:21 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.7.5/8.6.12) id RAA00878; Tue, 9 Jul 1996 17:47:37 -0400 (EDT) From: Charlie Root Message-Id: <199607092147.RAA00878@rhiannon.scsn.net> Subject: ATAPI no longer works for me... To: freebsd-current@freebsd.org Date: Tue, 9 Jul 1996 17:47:36 -0400 (EDT) Cc: dmaddox@scsn.net X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently installed FreeBSD 2.1.0-RELEASE on my home PC, and was pleased to find that ALL of my hardware was worked with FBSD :-). I then proceeded to sup all of the -current source, compile it, and install it. The whole process went pretty smoothly; however, I find that my ATAPI IDE CD-ROM drive no longer works. Or, to be more specific, ATAPI_STATIC no longer works at all, the lkm will SOMETIMES work, if I try modload'ing it repeatedly. Usually, I just get a message like "ERROR: device not configured". In those cases when it DOES load, it seems to work ok. The drive in question is a 4x Vertos 400HTD ATAPI IDE. The rest of the system is: P100, ASUS P/I-P55T2P4 Triton-II MB, 32M RAM, Maxtor 71336AP 1.2G HD (/ and /usr) Adaptec 2940UW with Fujitsu M2684 507MB SCSI (/usr/local) Quantum LP52S (swap) Creative Labs SB16 Diamond Stealth 64 2M VRAM 3240XL Iomega Ditto 'floppy' Tape Drive 3.5" Floppy, etc. Here's my current config (I've tried with and without ATAPI_STATIC): machine "i386" cpu "I586_CPU" # aka Pentium(tm) ident RHIANNON maxusers 10 options CHILD_MAX=128 options OPEN_MAX=128 options "I586_FAST_BCOPY" config kernel root on wd0 options "COMPAT_43" options USER_LDT #allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options DDB options KTRACE #kernel tracing options PERFMON options UCONSOLE options INET #Internet communications protocols pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device sl 2 #Serial Line IP pseudo-device ppp 2 #Point-to-point protocol pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver(user process ppp) options FFS #Fast filesystem options NFS #Network File System options "CD9660" #ISO 9660 filesystem options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options MFS #Memory File System options MSDOSFS #MS DOS File System options NULLFS #NULL filesystem options PROCFS #Process filesystem options UMAPFS #UID map filesystem options UNION #Union filesystem options DEVFS #devices filesystem options NSWAPDEV=20 controller scbus0 #base SCSI code device sd0 #SCSI disks pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver controller isa0 options "AUTO_EOI_1" options BOUNCE_BUFFERS options "MAXMEM=(32*1024)" options XSERVER # include code for XFree86 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 tape ft0 at fdc0 drive 2 options FDSEEKWAIT=16 device lpt0 at isa? port? tty irq 7 vector lptintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device pca0 at isa? port IO_TIMER1 tty device joy0 at isa? port "IO_GAME" controller pci0 controller ahc1 options "IBCS2" options COMPAT_LINUX options "SCSI_2_DEF" From owner-freebsd-current Tue Jul 9 15:06:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA12118 for current-outgoing; Tue, 9 Jul 1996 15:06:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA12100; Tue, 9 Jul 1996 15:06:29 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA06894; Wed, 10 Jul 1996 08:04:01 +1000 Date: Wed, 10 Jul 1996 08:04:01 +1000 From: Bruce Evans Message-Id: <199607092204.IAA06894@godzilla.zeta.org.au> To: michaelh@cet.co.jp, se@ZPR.Uni-Koeln.DE Subject: Re: Adding Jaz drive with sysinstall Cc: current@freebsd.org, scsi@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >} dmesg tells me that the Jaz reports that its a removable SCSI 2. Is this >} the source of the ILLEGAL REQUEST message? >No, the JAZ seems not to like some field in a request >sent to it and rejects the command. The command that >caused this appears to have been the geometry query, >which leads to the "fictious geometry" being used. >A possible cause of this might be that there was no >media loaded into the drive, I suppose ... >} ... >} sd2(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB >} sd2 could not mode sense (4). Using ficticious geometry Iomega zip drives give the same message when media is present. I guess the problem is a low quality implementation of the SCSI spec. Bruce From owner-freebsd-current Tue Jul 9 18:59:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25755 for current-outgoing; Tue, 9 Jul 1996 18:59:25 -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 SAA25749 for ; Tue, 9 Jul 1996 18:59:15 -0700 (PDT) Received: (from ernie@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id LAA09159 for freebsd-current@freebsd.org; Wed, 10 Jul 1996 11:57:14 +1000 (EST) From: Ernie Elu Message-Id: <199607100157.LAA09159@spooky.eis.net.au> Subject: DES and current To: freebsd-current@freebsd.org Date: Wed, 10 Jul 1996 11:57:14 +1000 (EST) 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 I have a client who cross graded their web server from BSDI to FreeBSD-stable. In order to do so they had to use the international DES libraries so the old BSDI passwords would work. This all worked fine for quite a while, however I recently upgrade them to -current as they required the Stallion drivers for an 8 port board going in. The upgrade was done by suping the -current from ftp.au.freebsd.org then rebuilding make and doing a make world. That all went fine except now when you try and do an adduser you get Invalid /etc/master.passwd - cannot add any users! The 3 crypt libraries are still pointing to the DES versions that seemed to get recompiled during the make world. Any suggestions? - Ernie. From owner-freebsd-current Tue Jul 9 18:59:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25786 for current-outgoing; Tue, 9 Jul 1996 18:59:31 -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 SAA25775 for ; Tue, 9 Jul 1996 18:59:29 -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 SAA19825; Tue, 9 Jul 1996 18:58:29 -0700 (PDT) To: Mr Operating System cc: freebsd-current@freebsd.org Subject: Re: A couple of problems!! In-reply-to: Your message of "Tue, 09 Jul 1996 23:57:58 +0300." <199607092057.XAA18578@shadows.aeon.net> Date: Tue, 09 Jul 1996 18:58:29 -0700 Message-ID: <19823.836963909@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > If you read the -current email, you'd know that you *must* first do a > > 'make bootstrap' in the lex diretory first. So > > > > # cd /usr/src/usr.bin/lex > > # make clean > > # make bootstrap > > # make > > # make install > > > > It'll work fine from then on. > > and when it doesnt? Do it from the right directory.. :-) $ cd /usr/src $ make clean bootstrap install Jordan From owner-freebsd-current Tue Jul 9 19:03:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA26195 for current-outgoing; Tue, 9 Jul 1996 19:03:08 -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 TAA26190 for ; Tue, 9 Jul 1996 19:03:05 -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 TAA19867; Tue, 9 Jul 1996 19:02:41 -0700 (PDT) To: Nate Williams cc: Mr Operating System , freebsd-current@freebsd.org Subject: Re: A couple of problems!! In-reply-to: Your message of "Tue, 09 Jul 1996 15:20:39 MDT." <199607092120.PAA19859@rocky.mt.sri.com> Date: Tue, 09 Jul 1996 19:02:41 -0700 Message-ID: <19865.836964161@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > If you read the -current email, you'd know that you *must* first do a > > > 'make bootstrap' in the lex diretory first. So > > > > > > # cd /usr/src/usr.bin/lex > > > # make clean > > > # make bootstrap > > > # make > > > # make install > > > > > > It'll work fine from then on. > > > > and when it doesnt? > > Then you aren't running current. I wasn't aware that the lex Makefile directly supported the "bootstrap" target in any release of the OS, but right you are! I guess someone did add bootstrap to lex. :-) So ignore my previous advice - I guess the poster really isn't running -current and running the global bootstrap rule won't help him. That's it, I'm going to stop answering questions until I've actually got the time to research them again first. :-) Jordan From owner-freebsd-current Tue Jul 9 19:26:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA27501 for current-outgoing; Tue, 9 Jul 1996 19:26:48 -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 TAA27493; Tue, 9 Jul 1996 19:26:43 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id CAA29004; Wed, 10 Jul 1996 02:26:40 GMT Date: Wed, 10 Jul 1996 11:26:40 +0900 (JST) From: Michael Hancock To: freebsd-fs@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Fixing Union_mounts In-Reply-To: <199606251931.MAA00496@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 [Please trim off current and leave fs when replying] Terry posted this reply to the "making in /usr/src" thread. I'd like to see all this stackable fs stuff made usable. I have some questions on Terry's remedies items 2) and 4) below: 2) Moving vnode locking to the vnode from the per fs inode will fix the help fix the stacking problems, but what will it do for future advanced file systems that need to have special locking requirements? 4) Moving the vnodes from the global pool to a per fs pool to improve locality of reference. Won't this make it hard to manage memory? How will efficient reclaim operations be implemented? This stacked fs stuff is really cool. You can implement a simple undelete in the Union layer by making whiteout entries (See the 4.4 deamon book). This would only work for the duration of the mount unlike Novell's persistent transactional stuff, but still very useful. There are already crypto-fs implementation out there, but I'd like to see more; especially non ITAR restricted ones that can be used world-wide. Regards, Mike Hancock On Tue, 25 Jun 1996, Terry Lambert wrote: > This is the intrinsic "union" option. > > It does not work. > > It does not work because VOP_ADVLOCK does not veto. > > It does not work because VOP_LOCK can not be stacked because it is > stupidly referencing flags specific to the underlying vnode for lock > resoloution instead of the union vnode. > > It does not work because VOP_LOOKUP, VOP_RENAME, etc. can not > be stacked because they actually deallocate path structures that > were allocated by code in vfs_syscalls.c, instead of the buffers > being deallocated in vfs_syscalls.c as well, as you would expect > in a proper idempotent layering implementation. > > VOP_LOCK stupidly references these flags because vclean needs them. > > vclean is an abomination before God, and is a half-kludge to deal > with not having both vnode/offset and dev/offset based cache > references simultaneously. > > Use of vnode/offset cache entries is a result of the unified cache > implementation. It saves a bmap call when moving data to/from > user space. It's why FreeBSD has faster I/O than most other systems. > > The lack of a parallel dev/offset based caching allows us to be lazy, > and enlarges the bit limit on FS storage, though it does not help > the inherent limit on file size (due to mapping). > > The lack of a parallel dev/offset results in the need for > implementation of a "second chance cache" via ihash. Still, we > will discard perfectly good pages from cache as a side effect of > having no way to reassociate them with a vnode. > > The use of a global vnode pool instead of per FS mount instance vnode > allocations damages cache locality. Combined with vclean, it also > damages cache coherency. > > > To repair: > > 1) Fix the stackability issues with the VFS interface itself, > which will incidently cause the VFS to more closely conform > to the Heidemann Thesis design on which it is based. Currently > it only implements a subset of the specified functionality. > > 2) Migrate the vnode locking to the vnode instead of the per FS > inode; get rid of the second chance cache at the same time > (the Lite2 code does some of this). The pointer should have > been in the vnode, not the inode, from the very beginning. > > 3) Move the directory name cache out of the per FS code and > into the lookup code. > > 4) Move the vnodes from the global pool; establish a per-FS > vnode free routine. > > 5) Establish VOP_GETPAGE/VOP_PUTPAGE, etc... > > 6) Union mounts will then work without kludges in lookup, locking, > and other code. They *could* be made to work with great, gross > kludges and changes to at least 3 FS's (that I know of), but > that's a kludge I won't do. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F 2-5-12, Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 From owner-freebsd-current Tue Jul 9 22:32:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08884 for current-outgoing; Tue, 9 Jul 1996 22:32:41 -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 WAA08879 for ; Tue, 9 Jul 1996 22:32:38 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA21577; Tue, 9 Jul 1996 23:32:08 -0600 (MDT) Date: Tue, 9 Jul 1996 23:32:08 -0600 (MDT) Message-Id: <199607100532.XAA21577@rocky.mt.sri.com> From: Nate Williams To: Mr Operating System Cc: jkh@time.cdrom.com (Jordan K. Hubbard), nate@mt.sri.com, freebsd-current@freebsd.org Subject: Re: A couple of problems!! In-Reply-To: <199607100526.IAA24779@shadows.aeon.net> References: <19865.836964161@time.cdrom.com> <199607100526.IAA24779@shadows.aeon.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Then you aren't running current. > > So ignore my previous advice - I guess the poster really isn't running > > -current and running the global bootstrap rule won't help him. > > shadows# uname -a > FreeBSD shadows.aeon.net 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Sun Jul 7 20:59:27 EET DST 1996 mickey@shadows.aeon.net:/usr/src/sys/compile/SHADOWS i386 > shadows# > > i believe i _do_ run -current, it's just that my sources doesnt seem to > agree with me all the time... and i just dont know what i'd do wrong... > > oh, in the previous post, i mentioned the Makefile id i got from sup > the other day, now it seems i got _another_ one... (i started sup at the > moment i started to type this one) > > and i dont think it's any more right version... > > # $Id: Makefile,v 1.57.4.17 1996/06/26 22:48:47 nate Exp $ > > and again, so that no one forgets, the line that brought that, was: (havent > touched the supfile in the process after the day one) > > src-base release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix > > *sigh* Sounds like a mixup in the sup server. Also, the Makefile I was speaking about was the Makefile in the lex directory, not the Makefile in /usr/src. Nate From owner-freebsd-current Tue Jul 9 22:45:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA10807 for current-outgoing; Tue, 9 Jul 1996 22:45:21 -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 WAA10798 for ; Tue, 9 Jul 1996 22:45:16 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA21660; Tue, 9 Jul 1996 23:44:42 -0600 (MDT) Date: Tue, 9 Jul 1996 23:44:42 -0600 (MDT) Message-Id: <199607100544.XAA21660@rocky.mt.sri.com> From: Nate Williams To: Mr Operating System Cc: nate@mt.sri.com (Nate Williams), freebsd-current@freebsd.org Subject: Re: A couple of problems!! In-Reply-To: <199607100541.IAA24865@shadows.aeon.net> References: <199607100532.XAA21577@rocky.mt.sri.com> <199607100541.IAA24865@shadows.aeon.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > i wish i'd have enough diskspace and lot more bandwidth between me and the > freebsd.org so i could get all from there... ofcourse, then i should be > living in the country too which would mean automaticly more bandwidth... We need to get whomever is running the .de server to make things work. Fixing the problem is better than beating up freefall. > > speaking about was the Makefile in the lex directory, not the Makefile > > in /usr/src. > > # $Id: Makefile,v 1.5 1996/06/19 20:46:57 nate Exp $ > > that was the id you wanted, this is what i have: > > # $Id: Makefile,v 1.2 1994/08/27 09:52:30 csgr Exp $ > > no wonder... *blink* That won't work. > but did the last base Makefile i got few minutes ago look about right? like, > if i'd be finally getting the -current i've thought i've had earlier too... Umm, I don't remember but it looks like a -stable makefile if it's got an ID with 1.X.X.X. Normal ID's (-current) are of the form 1.X, and branches such as stable have two additional #'s. Nate From owner-freebsd-current Tue Jul 9 22:49:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11470 for current-outgoing; Tue, 9 Jul 1996 22:49:44 -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 WAA11358 for ; Tue, 9 Jul 1996 22:48:54 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id IAA20935; Wed, 10 Jul 1996 08:13:50 +0300 (EET DST) From: Mr Operating System Message-Id: <199607100513.IAA20935@shadows.aeon.net> Subject: Re: A couple of problems!! To: nate@mt.sri.com (Nate Williams) Date: Wed, 10 Jul 1996 08:13:50 +0300 (EET DST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199607092120.PAA19859@rocky.mt.sri.com> from Nate Williams at "Jul 9, 96 03:20:39 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 > > and when it doesnt? > Then you aren't running current. i run whatever this supfile hands me: (first time about a month and bit over ago i started from empty /usr/src, whatever i have, all came from there... src-base release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-bin release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-contrib release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix # Domestic users only please. If you are outside of the U.S.A and Canada, # use the collections in secure-supfile. src-eBones release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-etc release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix #src-games release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-gnu release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-include release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-lib release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-libexec release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-sbin release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix # Domestic users only please. If you are outside of the U.S.A and Canada, # use the collections in secure-supfile. src-secure release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-share release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-sys release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-usrbin release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-usrsbin release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix anyone can pick any errors? i would love to get compileable current asap, since tomorrow i would have pro200 for playing at work... but it's there only today and tomorrow, our customer takes it away at friday... > > sup's about few hours old, from sup.de.freebsd.org (it has contrib now) > It must have an old version of lex then, but that also doesn't make > sense given that it can't build w/out the bootstrap. last week i had the mysterious sys/i386/include/ansi.h from 2.1.whatever > Look at the Makefile, it should have an ID of: > # $Id: Makefile,v 1.5 1996/06/19 20:46:57 nate Exp $ uh oh :\ # $Id: Makefile,v 1.89 1996/07/01 06:13:31 jkh Exp $ dont tell me, it's 2.1.whatever? :& > Nate mickey From owner-freebsd-current Tue Jul 9 22:51:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11767 for current-outgoing; Tue, 9 Jul 1996 22:51:03 -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 WAA11695 for ; Tue, 9 Jul 1996 22:50:39 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id IAA24865; Wed, 10 Jul 1996 08:41:12 +0300 (EET DST) From: Mr Operating System Message-Id: <199607100541.IAA24865@shadows.aeon.net> Subject: Re: A couple of problems!! To: nate@mt.sri.com (Nate Williams) Date: Wed, 10 Jul 1996 08:41:11 +0300 (EET DST) Cc: jkh@time.cdrom.com, nate@mt.sri.com, freebsd-current@freebsd.org In-Reply-To: <199607100532.XAA21577@rocky.mt.sri.com> from Nate Williams at "Jul 9, 96 11:32:08 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 > Sounds like a mixup in the sup server. Also, the Makefile I was argh... *sigh* *scream* =( i wish i'd have enough diskspace and lot more bandwidth between me and the freebsd.org so i could get all from there... ofcourse, then i should be living in the country too which would mean automaticly more bandwidth... > speaking about was the Makefile in the lex directory, not the Makefile > in /usr/src. # $Id: Makefile,v 1.5 1996/06/19 20:46:57 nate Exp $ that was the id you wanted, this is what i have: # $Id: Makefile,v 1.2 1994/08/27 09:52:30 csgr Exp $ no wonder... *blink* but did the last base Makefile i got few minutes ago look about right? like, if i'd be finally getting the -current i've thought i've had earlier too... coz i just cant wait to 'make world' on ppro200 *grin* > Nate mickey From owner-freebsd-current Tue Jul 9 22:55:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12317 for current-outgoing; Tue, 9 Jul 1996 22:55:12 -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 WAA12163 for ; Tue, 9 Jul 1996 22:52:48 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id IAA24779; Wed, 10 Jul 1996 08:26:16 +0300 (EET DST) From: Mr Operating System Message-Id: <199607100526.IAA24779@shadows.aeon.net> Subject: Re: A couple of problems!! To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 10 Jul 1996 08:26:16 +0300 (EET DST) Cc: nate@mt.sri.com, freebsd-current@FreeBSD.ORG In-Reply-To: <19865.836964161@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 9, 96 07:02:41 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 > > Then you aren't running current. > So ignore my previous advice - I guess the poster really isn't running > -current and running the global bootstrap rule won't help him. shadows# uname -a FreeBSD shadows.aeon.net 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Sun Jul 7 20:59:27 EET DST 1996 mickey@shadows.aeon.net:/usr/src/sys/compile/SHADOWS i386 shadows# i believe i _do_ run -current, it's just that my sources doesnt seem to agree with me all the time... and i just dont know what i'd do wrong... oh, in the previous post, i mentioned the Makefile id i got from sup the other day, now it seems i got _another_ one... (i started sup at the moment i started to type this one) and i dont think it's any more right version... # $Id: Makefile,v 1.57.4.17 1996/06/26 22:48:47 nate Exp $ and again, so that no one forgets, the line that brought that, was: (havent touched the supfile in the process after the day one) src-base release=current host=sup.de.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix *sigh* > Jordan mickey From owner-freebsd-current Wed Jul 10 00:53:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19002 for current-outgoing; Wed, 10 Jul 1996 00:53:47 -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 AAA18997 for ; Wed, 10 Jul 1996 00:53:42 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA03607; Wed, 10 Jul 1996 09:52:58 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA27024; Wed, 10 Jul 1996 09:52:57 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA09442; Wed, 10 Jul 1996 09:41:46 +0200 (MET DST) From: J Wunsch Message-Id: <199607100741.JAA09442@uriah.heep.sax.de> Subject: Re: A couple of problems!! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 10 Jul 1996 09:41:46 +0200 (MET DST) Cc: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607100544.XAA21660@rocky.mt.sri.com> from Nate Williams at "Jul 9, 96 11:44:42 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > We need to get whomever is running the .de server to make things work. Chris? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jul 10 05:46:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA09572 for current-outgoing; Wed, 10 Jul 1996 05:46:45 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA09563 for ; Wed, 10 Jul 1996 05:46:34 -0700 (PDT) Received: from campa.panke.de (anonymous213.ppp.cs.tu-berlin.de [130.149.17.213]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id OAA23922; Wed, 10 Jul 1996 14:33:34 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id NAA02795; Wed, 10 Jul 1996 13:58:53 +0200 Date: Wed, 10 Jul 1996 13:58:53 +0200 From: Wolfram Schneider Message-Id: <199607101158.NAA02795@campa.panke.de> To: Ernie Elu Cc: freebsd-current@freebsd.org Subject: DES and current In-Reply-To: <199607100157.LAA09159@spooky.eis.net.au> References: <199607100157.LAA09159@spooky.eis.net.au> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ernie Elu writes: >The upgrade was done by suping the -current from ftp.au.freebsd.org then >rebuilding make and doing a make world. That all went fine except now when >you try and do an adduser you get > >Invalid /etc/master.passwd - cannot add any users! Adduser did at startup a simple check if your /etc/master.passwd is valid. Adduser recreate the password database with `pwd_mkdb -p /etc/master.passwd'. If that does not work adduser stoped. >The 3 crypt libraries are still pointing to the DES versions that seemed to >get recompiled during the make world. From owner-freebsd-current Wed Jul 10 06:52:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA12533 for current-outgoing; Wed, 10 Jul 1996 06:52:25 -0700 (PDT) Received: from pod.spirit.com.au (root@pod.spirit.com.au [203.8.218.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA12522 for ; Wed, 10 Jul 1996 06:52:19 -0700 (PDT) Received: from matte.spirit.net.au by pod.spirit.com.au (8.7.4/1.01SP) id XAA06387; Wed, 10 Jul 1996 23:52:34 +1000 (EST) Received: from matte.spirit.net.au (localhost [127.0.0.1]) by matte.spirit.net.au (8.7.5/8.7.3) with SMTP id XAA00582 for ; Wed, 10 Jul 1996 23:51:54 +1000 (EST) Message-ID: <31E3B578.15FB7483@spirit.com.au> Date: Wed, 10 Jul 1996 23:51:52 +1000 From: Matthew Thyer X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: How to make world ?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello all.. I hope someone can help me here as I cant see anything in the FAQ or Handbook relating to this problem. I started running 23 March 96 SNAP but then decided to compile the current sources. So I: 1) Got the base delta "src-cur.1900A.gz" 2) Got the src-cur deltas from 1901 to 1955 3) Created a new filesystem which I mounted as /usr/src 4) Unpacked the deltas with "ctm -v -v delta_file" 5) Confirmed that the base and the other 55 deltas worked OK 6) Did a "make world" in this /usr/src dir. All the above was done as the root user but the makefile fails very early with: [ snipped off the start............. ] -------------------------------------------------------------- Rebuilding /usr/share/mk -------------------------------------------------------------- cd /usr/src/share/mk && make install cd /usr/src/share/mk && install -c -o bin -g bin -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.info.mk bsd.kmod.mk bsd.obj.mk bsd.lib.mk bsd.man.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/share/mk -------------------------------------------------------------- Cleaning up the source tree, and rebuilding the obj tree -------------------------------------------------------------- cd /usr/src && make cleandir ===> include *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any ideas what I'm doing wrong ?? -- ----------------------------------------------------------------------- Matthew Thyer matt@spirit.com.au ----------------------------------------------------------------------- "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 ----------------------------------------------------------------------- From owner-freebsd-current Wed Jul 10 08:53:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21113 for current-outgoing; Wed, 10 Jul 1996 08:53:51 -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 IAA21097 for ; Wed, 10 Jul 1996 08:53:31 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id SAA27198; Wed, 10 Jul 1996 18:50:53 +0300 (EET DST) From: Mr Operating System Message-Id: <199607101550.SAA27198@shadows.aeon.net> Subject: Re: A couple of problems!! To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 10 Jul 1996 18:50:53 +0300 (EET DST) Cc: freebsd-current@freebsd.org, kuku@acds.physik.rwth-aachen.de In-Reply-To: <199607100741.JAA09442@uriah.heep.sax.de> from J Wunsch at "Jul 10, 96 09:41:46 am" 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 > > We need to get whomever is running the .de server to make things work. > Chris? just a general question, why dont anyone else have "my kind" of probs? since i assume there's many people using the site... > cheers, J"org mickey From owner-freebsd-current Wed Jul 10 08:54:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21155 for current-outgoing; Wed, 10 Jul 1996 08:54:39 -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 IAA21147 for ; Wed, 10 Jul 1996 08:54:19 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id SAA27206; Wed, 10 Jul 1996 18:53:25 +0300 (EET DST) From: Mr Operating System Message-Id: <199607101553.SAA27206@shadows.aeon.net> Subject: Re: A couple of problems!! To: nate@mt.sri.com (Nate Williams) Date: Wed, 10 Jul 1996 18:53:25 +0300 (EET DST) Cc: nate@mt.sri.com, freebsd-current@freebsd.org In-Reply-To: <199607100544.XAA21660@rocky.mt.sri.com> from Nate Williams at "Jul 9, 96 11:44:42 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 > We need to get whomever is running the .de server to make things work. > Fixing the problem is better than beating up freefall. please... *smile* i have to hand the ppro200 to the too lucky&rich customer at friday and before that i'd rather run freebsd on the machine... > That won't work. apparently > Umm, I don't remember but it looks like a -stable makefile if it's got > an ID with 1.X.X.X. Normal ID's (-current) are of the form 1.X, and > branches such as stable have two additional #'s. ack... =( well, i probably should look thru _all_ the id's i got and see what i'm having here... > Nate mickey From owner-freebsd-current Wed Jul 10 10:45:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA29170 for current-outgoing; Wed, 10 Jul 1996 10:45:29 -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 KAA29164; Wed, 10 Jul 1996 10:45:25 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id RAA04866; Wed, 10 Jul 1996 17:45:17 GMT Date: Thu, 11 Jul 1996 02:45:16 +0900 (JST) From: Michael Hancock To: freebsd-fs@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixing Union_mounts 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 Never mind. Mail search on "FS and Layering" on current makes for some good reading. I have some absorbing to do. -mike hancock From owner-freebsd-current Wed Jul 10 11:20:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02203 for current-outgoing; Wed, 10 Jul 1996 11:20:35 -0700 (PDT) Received: from ibmmail.COM (ibmmail.com [199.171.26.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA02195 for ; Wed, 10 Jul 1996 11:20:32 -0700 (PDT) Message-Id: <199607101820.LAA02195@freefall.freebsd.org> Received: from ibmmail by ibmmail.COM (IBM VM SMTP V2R3) with BSMTP id 8970; Wed, 10 Jul 96 14:20:35 EDT Date: Wed, 10 Jul 1996 14:19:59 EDT From: "Stephen Palmer" To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: file system full, and 2.1-RELEASE boot floppy problem. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has the problem with : /: write failed, file system is full lock write: No space left on device failed to open modem ... during ftp install been resolved yet? I am anxiously awwaiting a new boot image so that I can get a recent SNAP on my machine... Also, My Home machine, AMD 5x86 133mhz, IDE HD & CDROM, will at least boot the 2.1.5-SNAP, and the 2.2-SNAP boot disks, but freezes before the "boot:" message on the 2.1-RELEASE floppy.(both standatrd, and ATAPI boot disks) Any Ideas? Stephen L. Palmer uscgsynd@ibmmail.com - Columbia Gulf, Houston TX elrond@helix.xiii.com - Home From owner-freebsd-current Wed Jul 10 12:40:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07572 for current-outgoing; Wed, 10 Jul 1996 12:40:54 -0700 (PDT) Received: from ibmmail.COM (ibmmail.com [199.171.26.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA07566 for ; Wed, 10 Jul 1996 12:40:51 -0700 (PDT) Message-Id: <199607101940.MAA07566@freefall.freebsd.org> Received: from ibmmail by ibmmail.COM (IBM VM SMTP V2R3) with BSMTP id 1656; Wed, 10 Jul 96 15:40:55 EDT Date: Wed, 10 Jul 1996 15:40:19 EDT From: "Stephen Palmer" To: current@freefall.freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: file system full, and 2.1-RELEASE boot floppy problem. Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry if this is a duplicate, I'm not sure if the last attempt to post was successful.. Has the problem with : /: write failed, file system is full lock write: No space left on device failed to open modem ... during ftp install been resolved yet? I am anxiously awwaiting a new boot image so that I can get a recent SNAP on my machine... Also, My Home machine, AMD 5x86 133mhz, IDE HD & CDROM, will at least boot the 2.1.5-SNAP, and the 2.2-SNAP boot disks, but freezes before the "boot:" message on the 2.1-RELEASE floppy.(both standatrd, and ATAPI boot disks) Any Ideas? Stephen L. Palmer uscgsynd@ibmmail.com - Columbia Gulf, Houston TX elrond@helix.xiii.com - Home From owner-freebsd-current Wed Jul 10 13:14:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09580 for current-outgoing; Wed, 10 Jul 1996 13:14:49 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA09575 for ; Wed, 10 Jul 1996 13:14:45 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id NAA24820 for current@freebsd.org; Wed, 10 Jul 1996 13:14:06 -0700 (PDT) Message-Id: <199607102014.NAA24820@ref.tfs.com> Subject: IPFW changes require recompile To: current@freebsd.org Date: Wed, 10 Jul 1996 13:14:04 -0700 (PDT) From: "JULIAN Elischer" X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The next time you recompile the kernel, make sure that if you are using hte ipfw facility, that you also recompile ipfw. julian From owner-freebsd-current Wed Jul 10 13:26:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA10347 for current-outgoing; Wed, 10 Jul 1996 13:26:01 -0700 (PDT) Received: from hermes.algonet.se (mail.algonet.se [193.12.207.206]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA10335 for ; Wed, 10 Jul 1996 13:25:47 -0700 (PDT) Received: from (johang@aristotle.algonet.se [193.12.207.8]) by hermes.algonet.se (8.7.4/hdw.1.0) with SMTP id WAA10505; Wed, 10 Jul 1996 22:25:02 +0200 (MET DST) Message-Id: <199607102025.WAA10505@hermes.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: Matthew Thyer , freebsd-current@freebsd.org Date: Wed, 10 Jul 1996 23:20:28 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: How to make world ?? Priority: normal X-mailer: Pegasus Mail for Windows (v2.33) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hello all.. I hope someone can help me here as I cant see anything > in the FAQ or Handbook relating to this problem. > > I started running 23 March 96 SNAP but then decided to compile the I assume a 2.2-SNAP > current sources. So I: > > 1) Got the base delta "src-cur.1900A.gz" > 2) Got the src-cur deltas from 1901 to 1955 > 3) Created a new filesystem which I mounted as /usr/src > 4) Unpacked the deltas with "ctm -v -v delta_file" > 5) Confirmed that the base and the other 55 deltas worked OK > 6) Did a "make world" in this /usr/src dir. > > All the above was done as the root user but the makefile fails very > early with: > > [ snipped off the start............. ] > -------------------------------------------------------------- > Rebuilding /usr/share/mk > -------------------------------------------------------------- > cd /usr/src/share/mk && make install > cd /usr/src/share/mk && install -c -o bin -g bin -m 444 bsd.README > bsd.dep.mk bsd.doc.mk bsd.info.mk bsd.kmod.mk bsd.obj.mk bsd.lib.mk > bsd.man.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk bsd.prog.mk > bsd.sgml.mk bsd.subdir.mk sys.mk /usr/share/mk > -------------------------------------------------------------- > Cleaning up the source tree, and rebuilding the obj tree > -------------------------------------------------------------- > cd /usr/src && make cleandir > ===> include > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > Any ideas what I'm doing wrong ?? Saw the same when upgrading from -stable. Do a make -DNOCLEANDIR world. That got me thru. I also had to manually compile ld beqause it complained ower a '-O' parameter. I guess you don't have to do that as you are already at V2.2. Cheers /Johan > -- > -------------------------------------------------------------------- > -- Matthew Thyer matt@spirit.com.au > -------------------------------------------------------------------- > -- "If it is true that our Universe has a zero net value for all > conserved quantities, then it may simply be a fluctuation of the > vacuum of some larger space in which our Universe is imbedded. In > answer to the question of why it happened, I offer the modest > proposal that our Universe is simply one of those things which > happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > -------------------------------------------------------------------- > -- > ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Wed Jul 10 18:41:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04734 for current-outgoing; Wed, 10 Jul 1996 18:41:09 -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 SAA04726 for ; Wed, 10 Jul 1996 18:41:07 -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 SAA06204; Wed, 10 Jul 1996 18:40:56 -0700 (PDT) To: "Stephen Palmer" cc: current@freebsd.org Subject: Re: file system full, and 2.1-RELEASE boot floppy problem. In-reply-to: Your message of "Wed, 10 Jul 1996 14:19:59 EDT." <199607101820.LAA02195@freefall.freebsd.org> Date: Wed, 10 Jul 1996 18:40:55 -0700 Message-ID: <6202.837049255@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > ... during ftp install been resolved yet? I am anxiously awwaiting a new > boot image so that I can get a recent SNAP on my machine... Can you try 2.1.5-GAMMA, on the various FTP sites by now? Jordan From owner-freebsd-current Thu Jul 11 01:47:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26668 for current-outgoing; Thu, 11 Jul 1996 01:47:06 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA26663 for ; Thu, 11 Jul 1996 01:47:02 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id JAA09640 for ; Thu, 11 Jul 1996 09:50:36 +0100 Date: Thu, 11 Jul 1996 09:50:36 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Help with Manpages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Since Ive installed freebsd V2.2 my man pages do not format correctly anymore.. on some older bsd setup machines they still work fine.. it's not the pages themselves, as some are identical but something to do with the way they format.. Here is what man ls comes out like on my screen now:- ..........e...tempalo.sO doc-syms NAME ls SYNOPSIS ls [FlACFLRTacdfiloqrstu1] [Arfile...] DESCRIPTION For each operand that names a file of a type other than directory, ls displays its name as well as any requested, associated information. For each operand that names a file of type directory, ls displays the names of files contained within that directory, as well as any requested, asso- ciated information. If no operands are given, the contents of the cur- rent directory are displayed. If more than one operand is given, non- directory operands are displayed first; directory and non-directory operands are sorted separately and in lexicographical order. The follow- ing options are available: FlA List all entries except for `.' and `...' Always set for thesu- per-user. Please Please can someone help before I go crazy?? Regards, Trefor S. From owner-freebsd-current Thu Jul 11 08:00:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17090 for current-outgoing; Thu, 11 Jul 1996 08:00:20 -0700 (PDT) Received: from jagor.srce.hr (root@jagor.srce.hr [161.53.2.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA16073; Thu, 11 Jul 1996 07:56:40 -0700 (PDT) Received: from a8-p2-zg.tel.hr [205.219.255.145] by jagor.srce.hr (8.7.5/8.6.12.CI) id QAA06595; Thu, 11 Jul 1996 16:56:09 +0200 (MET DST) Message-ID: <31E51772.188D@jagor.srce.hr> Date: Thu, 11 Jul 1996 17:02:10 +0200 From: Sinisa Sehovic X-Mailer: Mozilla 3.0b3 (Win95; I) MIME-Version: 1.0 To: announce@freebsd.org CC: hackers@freebsd.org, questions@freebsd.org, bugs@freebsd.org, current@freebsd.org, security@freebsd.org, ports@freebsd.org Subject: unsubscribe Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-current Thu Jul 11 08:13:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20901 for current-outgoing; Thu, 11 Jul 1996 08:13:59 -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 IAA20874 for ; Thu, 11 Jul 1996 08:13:54 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA00950; Thu, 11 Jul 1996 09:13:51 -0600 (MDT) Date: Thu, 11 Jul 1996 09:13:51 -0600 (MDT) Message-Id: <199607111513.JAA00950@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org Subject: USB serial specification Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ------- start of forwarded message (RFC 934 encapsulation) ------- In case anyone wants to know about the new 'serial' specs, I scammed this off a mailing list I'm on: ------ >Does anybody know where the USB specification could be retrieved? > It's at: http://www.teleport.com/~usb/specinfo.htm ------- Nate From owner-freebsd-current Thu Jul 11 08:59:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01197 for current-outgoing; Thu, 11 Jul 1996 08:59:22 -0700 (PDT) Received: from dn1.hudsonnet.com ([38.251.166.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA00803 for ; Thu, 11 Jul 1996 08:57:57 -0700 (PDT) Received: from proteus ([205.232.92.98]) by dn1.hudsonnet.com (post.office MTA v1.9.3b evaluation license) with SMTP id AAA143 for ; Thu, 11 Jul 1996 11:57:55 -0400 Message-ID: <31E5264E.4057@hudsonnet.com> Date: Thu, 11 Jul 1996 12:05:34 -0400 From: tim@hudsonnet.com (Tim Palmer) X-Mailer: Mozilla 2.02 (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe X-URL: http://www.freebsd.org/handbook/handbook195.html#413 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-current From owner-freebsd-current Thu Jul 11 11:38:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24641 for current-outgoing; Thu, 11 Jul 1996 11:38:09 -0700 (PDT) Received: (from julian@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24634; Thu, 11 Jul 1996 11:38:08 -0700 (PDT) Date: Thu, 11 Jul 1996 11:38:08 -0700 (PDT) From: Julian Elischer Message-Id: <199607111838.LAA24634@freefall.freebsd.org> To: hackers@freebsd.org Subject: summary of changes my changes in current recently Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just so that people have some sort of idea what The folks here at whistle (including me) have been doing. (In -current). Thes have been put back in FreeBSD so they are now generally available. 1/ added kernel level support for appletalk-over-ethernet 2/ added support for the above in netstat, route, ifconfig 3/ added support to the bootblocks (rather crude but..) to allow the user to decide the default string for the next boot, and what to do should that next boot fail.. (try a differnt string?) (revert to the old one?) etc. etc. useful also for setting non-standard bootstrings as the default.. e.g 3:sd(0,f)/kernel.funky 4/ added support for an IP DIVERT capability in the ip-firewall code. this allows arbitrary packets to be diverted to a user-land daemon. such a daemin might impliment ip-address translation.. or packet encryption. Daemons for both these have been written, but it is unlikely that I can release them, however all the hard part has been added to freebsd, so the remaining work for someone to write the daemons again should be within the scope of a standard C programmer, looking for a project. apply within if you need ideas as to how to impliment these.. :) Note that using the IPDIVERT and IPX, an IP-over-IPX tunnel to allow a winsock library to tunnel out over an IPX crippled network would be a trivial matter. (another project for someone?) Re: Appletalk.. Whistle Communications has agreed to supply the netatalk crew with a freeBSD machine, so I hope that in the future, netatalk releases will be native-ports on FreeBSD-current. I expect that Wes will be supplying me with direct -current patches both for the kernel parts and for the daemons themselves. With luck the kernel support for appletalk will also be relevant to the CAP camp. As I don't have netnews here, could someone forward this to there as well? (just to keep people informed about what's going on in -current) (also I think it would be a good idea if everyone were to occasionally report to hackers and netnews what they are working on,. so that we don't duplicate so much and so we get a feeling of how much development is going on.. how about we did a quick roll-call? From owner-freebsd-current Thu Jul 11 11:49:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25284 for current-outgoing; Thu, 11 Jul 1996 11:49:53 -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 LAA25279; Thu, 11 Jul 1996 11:49:51 -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 LAA29228; Thu, 11 Jul 1996 11:48:05 -0700 (PDT) To: Paul Traina cc: jkh@freebsd.org, current@freebsd.org Subject: Re: news from the "make release" front... In-reply-to: Your message of "Thu, 11 Jul 1996 01:09:09 PDT." <199607110809.BAA07464@base.jnx.com> Date: Thu, 11 Jul 1996 11:48:05 -0700 Message-ID: <29226.837110885@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Jordan, > FYI, here are the kludges I made to release/Makefile to get make release > to work since the change to make. Please note, the objlink stuff really is > a kludge. We really need to fix crunchgen. OK, I'm going to hang back on this for now, however, as release/Makefile is actually sync'd in 2.2 and 2.1-stable and this fact makes certain things easier for me. Just as soon as 2.1.5R is out the door this Friday, I'll bring these changes across into -current. Jordan From owner-freebsd-current Thu Jul 11 12:23:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27155 for current-outgoing; Thu, 11 Jul 1996 12:23:57 -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 MAA27148 for ; Thu, 11 Jul 1996 12:23:42 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA25192; Thu, 11 Jul 1996 21:22:49 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA18524; Thu, 11 Jul 1996 21:22:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA15730; Thu, 11 Jul 1996 21:14:06 +0200 (MET DST) From: J Wunsch Message-Id: <199607111914.VAA15730@uriah.heep.sax.de> Subject: Re: Help with Manpages To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 11 Jul 1996 21:14:05 +0200 (MET DST) Cc: dev@fgate.flevel.co.uk (Developer) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Developer at "Jul 11, 96 09:50:36 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 Developer wrote: > Here is what man ls comes out like on my screen now:- > > ..........e...tempalo.sO doc-syms NAME I would suspect your troff macros under /usr/share/tmac/ are broken for some reasons. The above looks like an unresolved .so directive. (And yep, there's really a file called /usr/share/tmac/mdoc/doc-syms.) -- 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 Jul 11 14:14:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA05377 for current-outgoing; Thu, 11 Jul 1996 14:14:44 -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 OAA05358; Thu, 11 Jul 1996 14:14:36 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA02542; Thu, 11 Jul 1996 15:14:27 -0600 (MDT) Date: Thu, 11 Jul 1996 15:14:27 -0600 (MDT) Message-Id: <199607112114.PAA02542@rocky.mt.sri.com> From: Nate Williams To: Julian Elischer Cc: hackers@freebsd.org, current@freebsd.org Subject: Re: summary of changes my changes in current recently In-Reply-To: <199607111838.LAA24634@freefall.freebsd.org> References: <199607111838.LAA24634@freefall.freebsd.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Just so that people have some sort of idea what The folks here at whistle > (including me) have been doing. (In -current). > Thes have been put back in FreeBSD so they are now generally available. > > 1/ added kernel level support for appletalk-over-ethernet > > 2/ added support for the above in netstat, route, ifconfig .... > Re: Appletalk.. Whistle Communications has agreed to supply > the netatalk crew with a freeBSD machine, so I hope that in > the future, netatalk releases will be native-ports on FreeBSD-current. > I expect that Wes will be supplying me with direct -current patches > both for the kernel parts and for the daemons themselves. > With luck the kernel support for appletalk will also be relevant to > the CAP camp. Wonderful. How do I use it to talk with the Macs in the office, or is this another one of those 'enabling' technologies that's 90% of the way there. :) nate From owner-freebsd-current Fri Jul 12 00:15:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA09584 for current-outgoing; Fri, 12 Jul 1996 00:15:36 -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 AAA09575; Fri, 12 Jul 1996 00:15:31 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA23619; Fri, 12 Jul 1996 09:14:51 +0200 Message-Id: <199607120714.JAA23619@ra.dkuug.dk> Subject: Re: summary of changes my changes in current recently To: julian@freefall.freebsd.org (Julian Elischer) Date: Fri, 12 Jul 1996 09:14:51 +0200 (MET DST) Cc: hackers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199607111838.LAA24634@freefall.freebsd.org> from "Julian Elischer" at Jul 11, 96 11:38:08 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 Julian Elischer who wrote: > > > Just so that people have some sort of idea what The folks here at whistle > (including me) have been doing. (In -current). > Thes have been put back in FreeBSD so they are now generally available. ... > 4/ added support for an IP DIVERT capability in the ip-firewall > code. this allows arbitrary packets to be diverted to a user-land > daemon. such a daemin might impliment ip-address translation.. > or packet encryption. > Daemons for both these have been written, but it is unlikely that I can > release them, however all the hard part has been added to freebsd, > so the remaining work for someone to write the daemons again should be > within the scope of a standard C programmer, looking for a project. I have iptranslation almost done, but as a kernel level module hooked into the fw code. It's currently being testet at one of our local ISP's, infact they are the ones that kind of asked for it. The framework could be used to build an userlever daemon as well, so when its ready I'll commit it for reference :) (there are NO strings attached to that code).. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Fri Jul 12 03:13:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA24888 for current-outgoing; Fri, 12 Jul 1996 03:13:23 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA24877 for ; Fri, 12 Jul 1996 03:13:18 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id LAA25731; Fri, 12 Jul 1996 11:15:41 +0100 Date: Fri, 12 Jul 1996 11:15:40 +0100 (BST) From: Developer To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: Help with Manpages In-Reply-To: <199607111914.VAA15730@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Jul 1996, J Wunsch wrote: > As Developer wrote: > > > Here is what man ls comes out like on my screen now:- > > > > ..........e...tempalo.sO doc-syms NAME > > I would suspect your troff macros under /usr/share/tmac/ are broken > for some reasons. The above looks like an unresolved .so directive. > (And yep, there's really a file called /usr/share/tmac/mdoc/doc-syms.) Thanks for that, you are dead right.. I deleted /usr/share/tmac and then re-installed groff and it worked fine:) (Strange thing was it didn`t work when I just installed groff, I had to delete the old stuff first). Also it has solved the problem I had with the new termcap database:) Thanks again:) Regards, Trefor S. From owner-freebsd-current Fri Jul 12 06:24:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA11641 for current-outgoing; Fri, 12 Jul 1996 06:24:57 -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 GAA11606; Fri, 12 Jul 1996 06:24:43 -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 VAA20126; Fri, 12 Jul 1996 21:24:38 +0800 (WST) Message-Id: <199607121324.VAA20126@spinner.DIALix.COM> X-Mailer: exmh version 1.6.6 3/24/96 To: committers@freebsd.org cc: current@freebsd.org, stable@freebsd.org Subject: Tree tagging imminent for 2.1.5-RELEASE! Date: Fri, 12 Jul 1996 21:24:38 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As with the previous releases, there is a complete source tree 'cvs rtag' due soon, to mark the exact point that the release was built from on the -stable branch. The cvs tag will be RELENG_2_1_5_RELEASE. This has serious implications for the people getting a copy of the cvs tree via sup. The two plain-source trees will be unaffected though. The tag process modifies every single file under the src/ area, so sup will re-transmit *THE WHOLE FILE!*. CTM is not so badly affected, but it will be sending a large-ish delta out, from memory of the 2.1R tagging it should be between 10 and 15 parts (about 1 to 1.5MB). This is probably going to put a fair degree of strain on the sup servers, so if you have difficulty connecting or getting a complete transfer, please give it some time to settle down and get over the hump. Your patience will be appreciated. If you have a relatively up-to-date cvs tree that you get by sup, you may want to do an update *now* to get up to date before the servers get hit with the load. This should be the last time this happens, there is a replacement sup-like system nearing completion that is *far* more efficient than sup, and should be just about on-par with ctm's efficiency. When that is ready, only the changed lines will be sent, rather than the whole file. More on this when the time comes, please don't email and ask me about it as I can't say much more than that. (The author can jump in if he wishes, but I dont think he's ready to go public yet). -Peter (PS: watch the followup CC: list!) From owner-freebsd-current Fri Jul 12 07:15:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA13923 for current-outgoing; Fri, 12 Jul 1996 07:15:21 -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 HAA13916 for ; Fri, 12 Jul 1996 07:15:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id IAA10554 for ; Fri, 12 Jul 1996 08:15:10 -0600 (MDT) Message-Id: <199607121415.IAA10554@rover.village.org> To: current@freebsd.org Subject: Build problems with -current + solution Date: Fri, 12 Jul 1996 08:15:10 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK. Tried to do a make world last night with -current. I have found a problem and the solution. I've seen this before in this list. Since I don't recall seeing the solution to this problem posted here, I'm offering mine. I have my sources in ~/FreeBSD/current/src. I used to have my -stable sources in ~/FreeBSD/stable/src. When I went to do a make world I got the following errors (truncated): cc -O -c /other/imp/FreeBSD/current/src/usr.bin/xinstall/xinstall.c In file included from /other/imp/FreeBSD/current/src/usr.bin/xinstall/xinstall.c:66: /usr/include/ctype.h:121: warning: parameter names (without types) in function declaration /usr/include/ctype.h:122: parse error before `___tolower' /usr/include/ctype.h:122: warning: parameter names (without types) in function declaration ... The problem, it turns out, is the (*&*#(^&*# symbolic links. The wrong ansi.h was begin grabbed. /usr/include/machine is a symblic link to /sys/i386/include. /sys is a symbolic link to usr/src/sys. My /usr/src symbolic link still pointed to the -stable sources rather than the -current sources. Since machine.h is different and now defines _BSD_CT_RUNE_T_ where before it didn't, the compilation failed. Correting the symbolic link from /usr/src to point to ~/FreeBSD/current/src fixed this problem. At least I'm able to do a make lib-tools now, which is where it was failing before. I really don't like the requirement that this symbolic link be correct, but have no better ideas to offer. So I'll just let people know this may be a problem for them and to offer this solution to people that might be upgrading from -current and who also don't (or can't) put their sources directly in /usr/src. Warner P.S. With my luck, this is a FAQ, since I didn't look at the FAQ before building. From owner-freebsd-current Fri Jul 12 08:33:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA19444 for current-outgoing; Fri, 12 Jul 1996 08:33:14 -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 IAA19433; Fri, 12 Jul 1996 08:33:08 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA06397; Fri, 12 Jul 1996 09:16:19 -0600 (MDT) Date: Fri, 12 Jul 1996 09:16:19 -0600 (MDT) Message-Id: <199607121516.JAA06397@rocky.mt.sri.com> From: Nate Williams To: Peter Wemm Cc: committers@freebsd.org, current@freebsd.org, stable@freebsd.org Subject: Re: Tree tagging imminent for 2.1.5-RELEASE! In-Reply-To: <199607121324.VAA20126@spinner.DIALix.COM> References: <199607121324.VAA20126@spinner.DIALix.COM> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As with the previous releases, there is a complete source tree 'cvs rtag' > due soon, to mark the exact point that the release was built from on the > -stable branch. Can you send out a message when the tag is done? I'm going to disable SUP for now until everything blow over, and would like to know when I can re-enable it. Thanks! Nate From owner-freebsd-current Fri Jul 12 08:57:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21236 for current-outgoing; Fri, 12 Jul 1996 08:57:37 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA21231 for ; Fri, 12 Jul 1996 08:57:30 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id RAA28797 for ; Fri, 12 Jul 1996 17:01:32 +0100 Date: Fri, 12 Jul 1996 17:01:32 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: FreeBSD on dual pentium? 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 was just wondering if anyone has tried to run FreeBSD current on any dual pentium machines? We were wondering about ordering one to use as a BSD server. Thanks. Trefor S. From owner-freebsd-current Fri Jul 12 09:32:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA23925 for current-outgoing; Fri, 12 Jul 1996 09:32:58 -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 JAA23915 for ; Fri, 12 Jul 1996 09:32:53 -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 SAA03277 for ; Fri, 12 Jul 1996 18:32:48 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id SAA08272 for freebsd-current@FreeBSD.ORG; Fri, 12 Jul 1996 18:32:14 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.5/keltia-uucp-2.8) id GAA16226 for freebsd-current@FreeBSD.ORG; Fri, 12 Jul 1996 06:52:38 +0200 (MET DST) From: Ollivier Robert Message-Id: <199607120452.GAA16226@keltia.freenix.fr> Subject: removeuser not present in BSD.usr.dist -> make world fails. To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Date: Fri, 12 Jul 1996 06:52:37 +0200 (MET DST) X-Operating-System: FreeBSD 2.2-CURRENT ctm#2178 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, removeuser is installed in /usr/share/examples/removeuser but the directory is not in BSD.usr.dist so the install fails. Index: BSD.usr.dist =================================================================== RCS file: /spare/FreeBSD-current/src/etc/mtree/BSD.usr.dist,v retrieving revision 1.62 diff -u -2 -r1.62 BSD.usr.dist --- BSD.usr.dist 1996/06/30 13:06:50 1.62 +++ BSD.usr.dist 1996/07/12 04:49:55 @@ -168,4 +168,6 @@ perfmon .. + removeuser + .. slattach .. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #12: Sun Jun 30 14:10:07 MET DST 1996 From owner-freebsd-current Fri Jul 12 09:44:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA25191 for current-outgoing; Fri, 12 Jul 1996 09:44:12 -0700 (PDT) Received: from fastlane.net (fastlane.net [204.251.16.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA25185 for ; Fri, 12 Jul 1996 09:44:10 -0700 (PDT) Received: from richardw (11.ann1.dal.why.net [205.240.253.20]) by fastlane.net (8.7.3/8.7.3) with SMTP id LAA05897 for ; Fri, 12 Jul 1996 11:33:45 -0500 (CDT) Message-ID: <31E6811E.68BD@fastlane.net> Date: Fri, 12 Jul 1996 11:45:18 -0500 From: faubus@fastlane.net X-Mailer: Mozilla 2.01 (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: FreeBSD on dual pentium pro? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I was likewise just wondering about running FreeBSD on a SuperMicro p6DNF motherboard. Anyone tried it yet? What are FreeBSD's plans for SMP support? I seem to remember someone was working on it.... From owner-freebsd-current Fri Jul 12 14:12:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16637 for current-outgoing; Fri, 12 Jul 1996 14:12:33 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16630 for ; Fri, 12 Jul 1996 14:12:29 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id OAA17872; Fri, 12 Jul 1996 14:12:02 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id OAA04370; Fri, 12 Jul 1996 14:12:01 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: faubus@fastlane.net cc: freebsd-current@freebsd.org Subject: Re: FreeBSD on dual pentium pro? In-reply-to: Your message of "Fri, 12 Jul 1996 11:45:18 PDT." <31E6811E.68BD@fastlane.net> Date: Fri, 12 Jul 1996 14:12:00 PDT Message-ID: <4368.837205920@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk faubus@fastlane.net wrote... I was likewise just wondering about running FreeBSD on a SuperMicro p6DNF motherboard. Anyone tried it yet? What are FreeBSD's plans for SMP support? I seem to remember someone was working on it.... subscribe to the freebsd-smp list (on freebsd.org), and read its mail archives. From owner-freebsd-current Fri Jul 12 14:14:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16731 for current-outgoing; Fri, 12 Jul 1996 14:14:24 -0700 (PDT) Received: from hogw2.att.com ([204.179.186.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA16726 for ; Fri, 12 Jul 1996 14:14:21 -0700 (PDT) From: dob@naserver1.cb.lucent.com Received: from nasvr1.cb.att.com by hoig2.att.att.com (SMI-8.6/EMS-1.2 sol2) id HAA19178; Thu, 11 Jul 1996 07:24:40 -0400 Original-From: dob@naserver1.cb.lucent.com Received: from cbsky.cb.att.com by nasvr1.cb.att.com (5.x/EMS-L sol2) id AA14788; Thu, 11 Jul 1996 07:29:41 -0400 Received: by cbsky.cb.att.com (5.x/EMS-1.1 Sol2) id AA12874; Thu, 11 Jul 1996 07:29:13 -0400 Date: Thu, 11 Jul 1996 07:29:13 -0400 Message-Id: <9607111129.AA12874@cbsky.cb.att.com> To: freebsd-current@freebsd.org Subject: panic on reboot with current -current X-Sun-Charset: US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I hate to rain on anyone's parade, but my system panics with the current -current. I haven't been tracking all the changes since the last time we had VM problems, but my officemate suggested I sup and get current before they put in gcc 2.7.3 so I did, but now I panic during reboot after making the world (and making a kernel, reboot was to pick up the new kernel). (I did it twice since I didn't capture the panic string the first time, thus seems to be reproducible.) (Also panic's after making world without making new kernel. Just this AM I halted the system after making world all night -- Kids play with PC during day so I don't *dare* leave it up :-) panic: vm_page_free invalid wire count(2), pindex 0x6042 trace: _panic _vm_page_freechk_and_unqueue + 0x150 _vm_page_free + 0x2d _vm_object_terminate + 0x12d _vm_object_deallocate + 0x1af _vn_vmio_close + 0x30 _ffs_unmount + 0xac _dounmount + 0x90 _ufs_unmountall + 0x41 _boot + 0xf3 _reboot + 0x29 Sup which fails: 07/03/96 15:33 EDT Sup which fails: 07/10/96 ~19:00 EDT Sup which worked: 06/21/96 16:02 EDT System specs the same. 8MB P75. 0K L2 cache. Next week I'll move to 40MB of memory so these problems will probably disappear... Thanks, Dan O'Brien Lucent Technologies, Bell Labs Innovations Columbus, OH USA From owner-freebsd-current Fri Jul 12 14:15:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16816 for current-outgoing; Fri, 12 Jul 1996 14:15:56 -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 OAA16811 for ; Fri, 12 Jul 1996 14:15:51 -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 XAA14810 for ; Fri, 12 Jul 1996 23:15:05 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id XAA18539 for freebsd-current@FreeBSD.ORG; Fri, 12 Jul 1996 23:12:40 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id TAA03876; Fri, 12 Jul 1996 19:08:00 +0200 (MET DST) To: freebsd-current@FreeBSD.ORG Subject: javac_netscape updates From: Peter Mutsaers Date: 12 Jul 1996 19:08:00 +0200 Message-ID: <87pw612ydr.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 I still see some updates to javac_netscape, while (AFAIK) it doesn't work at all. Am I wrong in this assumption? The latest I heard is that it only works with older versions of netscape (not available anymore and unsafe). Is there a way to make javac_netscape work? -- ______________________________________________________________________ Peter Mutsaers | Abcoude (Utrecht), | "Memento Mori" plm@xs4all.nl | the Netherlands | From owner-freebsd-current Fri Jul 12 14:45:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20029 for current-outgoing; Fri, 12 Jul 1996 14:45:13 -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 OAA19968 for ; Fri, 12 Jul 1996 14:45:00 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id VAA05623 for freebsd-current@freebsd.org; Fri, 12 Jul 1996 21:26:37 +0300 (EET DST) From: Mr Operating System Message-Id: <199607121826.VAA05623@shadows.aeon.net> Subject: Re: FreeBSD on dual pentium? To: freebsd-current@freebsd.org Date: Fri, 12 Jul 1996 21:26:37 +0300 (EET DST) In-Reply-To: from Developer at "Jul 12, 96 05:01:32 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 > I was just wondering if anyone has tried to run FreeBSD current on any > dual pentium machines? We were wondering about ordering one to use as a > BSD server. i ran it today on dual p166, didnt have src's around to compile... and i used GigaByte Dual Pentium board, it has also AHA7880 onboard, i just loved it since having the UW on dual pentium board is more than anyone can ask... almost... only bad things were the ATX layout... since the board DOES eat power from same kind of connection than any general AT board... oh, and the board has also 512k cache, i had 128 megs ram on it... *smile* the machine felt extremely fast... > Trefor S. mickey From owner-freebsd-current Fri Jul 12 14:58:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21157 for current-outgoing; Fri, 12 Jul 1996 14:58:09 -0700 (PDT) Received: from silvia.hip.berkeley.edu (tip-mp4-ncs-2.Stanford.EDU [36.173.0.81]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA21138 for ; Fri, 12 Jul 1996 14:58:03 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.7.5/8.6.12) id OAA01235; Fri, 12 Jul 1996 14:57:48 -0700 (PDT) Date: Fri, 12 Jul 1996 14:57:48 -0700 (PDT) Message-Id: <199607122157.OAA01235@silvia.hip.berkeley.edu> To: plm@xs4all.nl CC: freebsd-current@FreeBSD.ORG In-reply-to: <87pw612ydr.fsf@localhost.xs4all.nl> (message from Peter Mutsaers on 12 Jul 1996 19:08:00 +0200) Subject: Re: javac_netscape updates From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I still see some updates to javac_netscape, while (AFAIK) it doesn't * work at all. Am I wrong in this assumption? As far as I know, you are correct. However, it should start working once the netscape guys fix their Java code. In other words, it isn't javac_netscape that is broken. Satoshi From owner-freebsd-current Fri Jul 12 15:23:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22524 for current-outgoing; Fri, 12 Jul 1996 15:23:36 -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 PAA22510 for ; Fri, 12 Jul 1996 15:23:33 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id PAA13044; Fri, 12 Jul 1996 15:22:05 -0700 From: "Rodney W. Grimes" Message-Id: <199607122222.PAA13044@GndRsh.aac.dev.com> Subject: Re: FreeBSD on dual pentium? To: freebsd@shadows.aeon.net (Mr Operating System) Date: Fri, 12 Jul 1996 15:22:05 -0700 (PDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199607121826.VAA05623@shadows.aeon.net> from Mr Operating System at "Jul 12, 96 09:26:37 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 was just wondering if anyone has tried to run FreeBSD current on any > > dual pentium machines? We were wondering about ordering one to use as a > > BSD server. > > i ran it today on dual p166, didnt have src's around to compile... FreeBSD-current does _not_ take any advantage of the second CPU on a dual CPU board. You where in effect running on a single P166. There is ongoing developement for SMP, subscribe to the freebsd-smp mailling list for more information. > > and i used GigaByte Dual Pentium board, it has also AHA7880 onboard, i > just loved it since having the UW on dual pentium board is more than anyone > can ask... almost... > > only bad things were the ATX layout... since the board DOES eat power from > same kind of connection than any general AT board... > > oh, and the board has also 512k cache, i had 128 megs ram on it... > > *smile* > > the machine felt extremely fast... Just as fast as any other Triton-II based P166 512K cache machine :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Fri Jul 12 17:29:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26876 for current-outgoing; Fri, 12 Jul 1996 17:29:32 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA26838; Fri, 12 Jul 1996 17:28:07 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id AAA07477; Sat, 13 Jul 1996 00:27:59 GMT From: Adam David Message-Id: <199607130027.AAA07477@veda.is> Subject: strangest weirdness To: freebsd-current@freebsd.org Date: Sat, 13 Jul 1996 00:27:54 +0000 (GMT) Cc: freebsd-fs@freebsd.org 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 Well I have just seen what seems to be an unusual filesystem glitch. I was doing 'make depend' in 2 kernel directories concurrently, and at the same time as another kernel 'make all' was getting towards the end of its processing. Both instances of 'make depend' broke by invoking the editor 'ex' on an empty temporary file, following the first invocation of 'mkdep'. No other instances of 'ex' were running at the time as far as I can tell. This was with an NFS /usr, and I believe that the 'make' executable was reinstalled after the 'make all' was started but before the 'make depend' was started. (yes, it's called stress testing. ;) I have also noticed that executables dump core often on client machines when the files on the fileserver have been updated "under their feet". Okay I know "if it hurts, don't do that", but why do these glitches occur? -- Adam David From owner-freebsd-current Fri Jul 12 21:09:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05174 for current-outgoing; Fri, 12 Jul 1996 21:09:46 -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 VAA05143 for ; Fri, 12 Jul 1996 21:08:17 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id WAA01060 for ; Fri, 12 Jul 1996 22:08:11 -0600 (MDT) Message-Id: <199607130408.WAA01060@rover.village.org> To: current@freebsd.org Subject: Another smiling face Date: Fri, 12 Jul 1996 22:08:10 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Looks like the make world finally finished, and I was able to do a level 0 dump of the system in single user mode after rebuilding the kernel and rebooting. Haven't seen a leak so far, but will keep my eyes open. Now all I need is more disk space to keep the built system online so make world (or make depend all install) is faster in the future. Warner From owner-freebsd-current Fri Jul 12 21:28:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06270 for current-outgoing; Fri, 12 Jul 1996 21:28:48 -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 VAA06265 for ; Fri, 12 Jul 1996 21:28:45 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id XAA04473; Fri, 12 Jul 1996 23:28:28 -0500 (EST) From: "John S. Dyson" Message-Id: <199607130428.XAA04473@dyson.iquest.net> Subject: Re: Another smiling face To: imp@village.org (Warner Losh) Date: Fri, 12 Jul 1996 23:28:28 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <199607130408.WAA01060@rover.village.org> from "Warner Losh" at Jul 12, 96 10:08:10 pm 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 > > Looks like the make world finally finished, and I was able to do a > level 0 dump of the system in single user mode after rebuilding the > kernel and rebooting. > > Haven't seen a leak so far, but will keep my eyes open. > > Now all I need is more disk space to keep the built system online so > make world (or make depend all install) is faster in the future. > How's performance seem so far? Y'know I am a bit of a performance freak :-). John From owner-freebsd-current Fri Jul 12 21:34:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06616 for current-outgoing; Fri, 12 Jul 1996 21:34:41 -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 VAA06610 for ; Fri, 12 Jul 1996 21:34:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id WAA01288; Fri, 12 Jul 1996 22:33:47 -0600 (MDT) Message-Id: <199607130433.WAA01288@rover.village.org> To: "John S. Dyson" Subject: Re: Another smiling face Cc: current@freebsd.org In-reply-to: Your message of Fri, 12 Jul 1996 23:28:28 CDT Date: Fri, 12 Jul 1996 22:33:47 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : How's performance seem so far? Feels faster for emacs. The dumps were tape speed bound, so they didn't take less time than before. It seems strange, but a lot of the mh stuff I do from emacs seems a little faster. I've not done anything that has huge VM things in it. I'll be updating the user stuff from time to time. I'll let you know how the next make world goes. This one took like 12 hours using an April 15ish -stable kernel. So far feels faster. Boots faster. X starts faster, but I have trouble telling exactly how much faster... : Y'know I am a bit of a performance freak :-). Hmmm. Never would have guessed. :-) Warner From owner-freebsd-current Sat Jul 13 02:10:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA25266 for current-outgoing; Sat, 13 Jul 1996 02:10:31 -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 CAA25259; Sat, 13 Jul 1996 02:10:27 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA26066; Sat, 13 Jul 1996 11:10:13 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA10257; Sat, 13 Jul 1996 11:10:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA22966; Sat, 13 Jul 1996 10:21:11 +0200 (MET DST) From: J Wunsch Message-Id: <199607130821.KAA22966@uriah.heep.sax.de> Subject: Re: strangest weirdness To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Date: Sat, 13 Jul 1996 10:21:11 +0200 (MET DST) Cc: adam@veda.is (Adam David) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607130027.AAA07477@veda.is> from Adam David at "Jul 13, 96 00:27:54 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 Adam David wrote: > I have also noticed that executables dump core often on client machines when > the files on the fileserver have been updated "under their feet". Okay I know > "if it hurts, don't do that", but why do these glitches occur? Terry will certainly jump in now and explain you that it would be better to move over the entire executable into local swap instead of relying on the ability to page it in from the NFS server. The latter is what we're doing right now -- so you are simply not expected to remove it on the server. The Unix semantics of ``a file will only be removed once the last reference to it disappeared'' don't work over NFS since the server simply doesn't know (and cannot know due to the statelessness of the protocol) which clients still hold references on some file. These semantics are being emulated in the case where you unlink a file on the client that has still other references, by renaming the file on the server first, and remove it later. -- 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 Jul 13 09:41:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19223 for current-outgoing; Sat, 13 Jul 1996 09:41:08 -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 JAA18966; Sat, 13 Jul 1996 09:40:38 -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 AAA26193; Sun, 14 Jul 1996 00:40:34 +0800 (WST) Message-Id: <199607131640.AAA26193@spinner.DIALix.COM> X-Mailer: exmh version 1.6.6 3/24/96 To: committers@freebsd.org, current@freebsd.org, stable@freebsd.org Subject: Re: Tree tagging imminent for 2.1.5-RELEASE! In-reply-to: Your message of "Fri, 12 Jul 1996 21:24:38 +0800." <199607121324.VAA20126@spinner.DIALix.COM> Date: Sun, 14 Jul 1996 00:40:33 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The tree tag has finished, about 20 minutes ago.... (~9AM freefall time). Cheers, -Peter Peter Wemm wrote: > As with the previous releases, there is a complete source tree 'cvs rtag' > due soon, to mark the exact point that the release was built from on the > -stable branch. > > The cvs tag will be RELENG_2_1_5_RELEASE. > > This has serious implications for the people getting a copy of the cvs > tree via sup. The two plain-source trees will be unaffected though. > > The tag process modifies every single file under the src/ area, so sup > will re-transmit *THE WHOLE FILE!*. CTM is not so badly affected, but it > will be sending a large-ish delta out, from memory of the 2.1R tagging it > should be between 10 and 15 parts (about 1 to 1.5MB). > > This is probably going to put a fair degree of strain on the sup servers, > so if you have difficulty connecting or getting a complete transfer, > please give it some time to settle down and get over the hump. Your > patience will be appreciated. > > If you have a relatively up-to-date cvs tree that you get by sup, you may > want to do an update *now* to get up to date before the servers get hit > with the load. > > -Peter > (PS: watch the followup CC: list!) From owner-freebsd-current Sat Jul 13 10:07:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA04827 for current-outgoing; Sat, 13 Jul 1996 10:07:51 -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 KAA04563; Sat, 13 Jul 1996 10:07:22 -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 TAA25022; Sat, 13 Jul 1996 19:06:52 +0200 (SAT) Message-Id: <199607131706.TAA25022@grumble.grondar.za> To: Peter Wemm cc: committers@freebsd.org, current@freebsd.org, stable@freebsd.org Subject: Re: Tree tagging imminent for 2.1.5-RELEASE! Date: Sat, 13 Jul 1996 19:06:49 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Wemm wrote: > The tree tag has finished, about 20 minutes ago.... (~9AM freefall time). ...and the international crypto repository is done as well! 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 Sat Jul 13 10:56:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00327 for current-outgoing; Sat, 13 Jul 1996 10:56:03 -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 KAA00284 for ; Sat, 13 Jul 1996 10:55:40 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id aa11261; 13 Jul 96 17:55 GMT Received: from nlsys.demon.co.uk ([158.152.125.33]) by relay-3.mail.demon.net id aa12356; 13 Jul 96 11:46 +0100 Message-ID: <31E77EA6.41C67EA6@nlsys.demon.co.uk> Date: Sat, 13 Jul 1996 11:47:02 +0100 From: Doug Rabson Organization: None X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org CC: dfr@render.com Subject: NFSv3 fixes for review Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have just integrated some fixes to the NFSv3 code from Frank van der Linden (frank@fwi.uva.nl). The first bug is the same one as the 'corrupt output from makesyscalls.sh on an nfsv3 mount' bug. I have verified this one by testing on a loopback mount (which is all I can do from my home machine). I have not tried to reproduce the second two problems but the fixes seem safe. While I was here, I also fixed the truncated 32bit minor numbers on nfsv3 mount bug. I believe that Bruce originally suggested the fix for this? Could someone please review these changes (diffs included) so that I can commit them. P.S. Is there a policy on using remote cvs to freefall? I don't have a cvs tree at home, so I used remote cvs to checkout the nfs source and produce diffs. What about commits via remote cvs? Date: Fri, 12 Jan 1996 02:17:04 +0100 (MET) From: frank@fwi.uva.nl (Frank van der Linden) Subject: Re: nfs v3 bug Thanks for the suggestions on the bug I reported. Too bad you don't have a machine around there anymore on which you run the code (well.. unless you get that VaxStation port going ;-)) Anyway, I think I found the bug. The scenario is as follows: - a process opens a file over NFS for writing, using v3 - at some point it calls nfs_write(), which partially fills a buffer with bdwrite - an nfsiod grabs it, because it was doing an operation anyway, and it checks if more buffers are available - nfssvc_iod calls nfs_doio, and the buffer gets written to the server, but not committed to the server. The buffer will now have B_DELWRI and B_NEEDCOMMIT set - the process does another nfs_write, resulting in another bdwrite() into the same buffer. - there is now a buffer which still has B_DELWRI and B_NEEDCOMMIT set, and thus is looked at as being 'written to the server but not committed'. This is wrong, because the buffer now contains more data than was originally written to the server. - when nfs_flush() is called, the buffer is only committed, the extra data never makes it to the server. The fix I applied was simply clearing B_NEEDCOMMIT in bdwrite(). Perhaps this was already done on the systems (BSDI, 4.4BSD?) you tested the code on. - Frank ---- Date: Mon, 1 Jul 1996 11:42:05 +0200 (MET DST) From: frank@fwi.uva.nl (Frank van der Linden) Subject: NFSv3 bugfix Hi, Here's an NFSv3 code bugfix I thought you should know about. The bug was, that whenever a server (for whatever reason) returned an answer to a write RPC that implied that fewer bytes than requested were written, bad things would happen. Following happened: - nfs_writerpc sees that not all data was written - it backs up the counter and pointer in the iov struct part of the uiop - the write loop is entered again - nfsm_uiotom is entered again (i.e. nfsm_uiotombuf()) - the first time that was called, uio_iov was incremented, because the iov had been completely 'emptied' into mbufs, so normally you'd move on to the next. however, iovcnt is always 1 in this case --> uio_iov is a bogus pointer now, pointing somewhere on the stack of nfs_doio(), where a local iov was used in the uio structure - bad things happen when the bogus pointer is referenced. Fix: make sure that iovcnt is always 1, and don't increment uio_iov, since this should never happen. I also added a comment noting that nfsm_uiotombuf() can only handle iovcnt == 1. The fix is appended at the end of this mail. --- Date: Wed, 10 Jul 1996 11:08:55 +0200 (MET DST) From: frank@fwi.uva.nl (Frank van der Linden) Subject: Some new fixes Hi, I know that you don't have the time currently to look at it, but i thought I'd mail you these patches for the NFSv3 code anyway. There were 2 problems: 1) The setattr operation passed on the atime in stead of the mtime to the server. The fix is trivial. 2) XIDs always started at 0, but this caused some servers (older DEC OSF/1 3.0 so I've been told) who had very long-lasting XID caches to get confused if, after a reboot of a BSD client, RPCs came in with a XID that had in the past been used before from that client. Patch is to use the current time in seconds as a starting point for XIDs. The patch below is not perfect, because it requires the root fs to be mounted first. This is because of the check BSD systems do, comparing FS time to system time. The patches are appended below. - Frank Index: nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_bio.c,v retrieving revision 1.23 diff -c -r1.23 nfs_bio.c *** nfs_bio.c 1996/06/08 05:59:04 1.23 --- nfs_bio.c 1996/07/13 10:35:53 *************** *** 584,589 **** --- 584,596 ---- bp->b_validoff = min(bp->b_validoff, bp->b_dirtyoff); bp->b_validend = max(bp->b_validend, bp->b_dirtyend); } + + /* + * Since this block is being modified, it must be written + * again and not just committed. + */ + bp->b_flags &= ~B_NEEDCOMMIT; + /* * If the lease is non-cachable or IO_SYNC do bwrite(). */ Index: nfs_subs.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_subs.c,v retrieving revision 1.30 diff -c -r1.30 nfs_subs.c *** nfs_subs.c 1996/06/23 17:19:25 1.30 --- nfs_subs.c 1996/07/13 10:37:48 *************** *** 53,58 **** --- 53,59 ---- #include #include #include + #include #ifdef VFS_LKM #include #include *************** *** 635,640 **** --- 636,643 ---- register int i; struct mbuf *mreq, *mb2; int siz, grpsiz, authsiz; + struct timeval tv; + static u_long base; authsiz = nfsm_rndup(auth_len); MGETHDR(mb, M_WAIT, MT_DATA); *************** *** 653,660 **** --- 656,677 ---- * First the RPC header. */ nfsm_build(tl, u_long *, 8 * NFSX_UNSIGNED); + + /* + * derive initial xid from system time + * XXX time is invalid if root not yet mounted + */ + if (!base && (rootvp)) { + microtime(&tv); + base = tv.tv_sec << 12; + nfs_xid = base; + } + /* + * Skip zero xid if it should ever happen. + */ if (++nfs_xid == 0) nfs_xid++; + *tl++ = *xidp = txdr_unsigned(nfs_xid); *tl++ = rpc_call; *tl++ = rpc_vers; *************** *** 834,840 **** } /* ! * copies a uio scatter/gather list to an mbuf chain... */ int nfsm_uiotombuf(uiop, mq, siz, bpos) --- 851,858 ---- } /* ! * copies a uio scatter/gather list to an mbuf chain. ! * NOTE: can ony handle iovcnt == 1 */ int nfsm_uiotombuf(uiop, mq, siz, bpos) *************** *** 849,854 **** --- 867,877 ---- int uiosiz, clflg, rem; char *cp; + #ifdef DIAGNOSTIC + if (uiop->uio_iovcnt != 1) + panic("nfsm_uiotombuf: iovcnt != 1"); + #endif + if (siz > MLEN) /* or should it >= MCLBYTES ?? */ clflg = 1; else *************** *** 856,863 **** rem = nfsm_rndup(siz)-siz; mp = mp2 = *mq; while (siz > 0) { - if (uiop->uio_iovcnt <= 0 || uiop->uio_iov == NULL) - return (EINVAL); left = uiop->uio_iov->iov_len; uiocp = uiop->uio_iov->iov_base; if (left > siz) --- 879,884 ---- *************** *** 892,904 **** uiop->uio_offset += xfer; uiop->uio_resid -= xfer; } ! if (uiop->uio_iov->iov_len <= siz) { ! uiop->uio_iovcnt--; ! uiop->uio_iov++; ! } else { ! uiop->uio_iov->iov_base += uiosiz; ! uiop->uio_iov->iov_len -= uiosiz; ! } siz -= uiosiz; } if (rem > 0) { --- 913,920 ---- uiop->uio_offset += xfer; uiop->uio_resid -= xfer; } ! uiop->uio_iov->iov_base += uiosiz; ! uiop->uio_iov->iov_len -= uiosiz; siz -= uiosiz; } if (rem > 0) { *************** *** 1218,1225 **** if (v3) { vtyp = nfsv3tov_type(fp->fa_type); vmode = fxdr_unsigned(u_short, fp->fa_mode); ! rdev = makedev(fxdr_unsigned(int, fp->fa3_rdev.specdata1), ! fxdr_unsigned(int, fp->fa3_rdev.specdata2)); fxdr_nfsv3time(&fp->fa3_mtime, &mtime); } else { vtyp = nfsv2tov_type(fp->fa_type); --- 1234,1241 ---- if (v3) { vtyp = nfsv3tov_type(fp->fa_type); vmode = fxdr_unsigned(u_short, fp->fa_mode); ! rdev = makedev(fxdr_unsigned(u_int, fp->fa3_rdev.specdata1), ! fxdr_unsigned(u_int, fp->fa3_rdev.specdata2)); fxdr_nfsv3time(&fp->fa3_mtime, &mtime); } else { vtyp = nfsv2tov_type(fp->fa_type); Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.33 diff -c -r1.33 nfs_vnops.c *** nfs_vnops.c 1996/01/25 00:45:37 1.33 --- nfs_vnops.c 1996/07/13 10:40:38 *************** *** 757,763 **** if (vap->va_mtime.ts_sec != time.tv_sec) { nfsm_build(tl, u_long *, 3 * NFSX_UNSIGNED); *tl++ = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); ! txdr_nfsv3time(&vap->va_atime, tl); } else { nfsm_build(tl, u_long *, NFSX_UNSIGNED); *tl = txdr_unsigned(NFSV3SATTRTIME_TOSERVER); --- 757,763 ---- if (vap->va_mtime.ts_sec != time.tv_sec) { nfsm_build(tl, u_long *, 3 * NFSX_UNSIGNED); *tl++ = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); ! txdr_nfsv3time(&vap->va_mtime, tl); } else { nfsm_build(tl, u_long *, NFSX_UNSIGNED); *tl = txdr_unsigned(NFSV3SATTRTIME_TOSERVER); -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891 From owner-freebsd-current Sat Jul 13 20:39:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA01989 for current-outgoing; Sat, 13 Jul 1996 20:39:51 -0700 (PDT) Received: from specgw.spec.co.jp (specgw.spec.co.jp [202.32.13.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA01975 for ; Sat, 13 Jul 1996 20:39:44 -0700 (PDT) Received: (from uucp@localhost) by specgw.spec.co.jp (8.7.5/3.3Wb-SPEC) with UUCP id MAA10661; Sun, 14 Jul 1996 12:39:12 +0900 (JST) Received: by tama.spec.co.jp (8.7.5/6.4J.5) id MAA01006; Sun, 14 Jul 1996 12:46:02 +0900 (JST) From: Atsushi Murai Message-Id: <199607140346.MAA01006@tama.spec.co.jp> Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 14 Jul 1996 12:46:02 +0900 (JST) Cc: amurai@spec.co.jp, nao@sbl.cl.nec.co.jp, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <199607030211.TAA27687@freefall.freebsd.org> from "Justin T. Gibbs" at Jul 2, 96 07:11:42 pm Reply-To: amurai@spec.co.jp X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I am attempt to let my 3com-3c579-TP (EISA) functional with several suggestion relating a configuration but unfortunatlly, there was no luck for me...But today I get spare time hack it due to be cancelling a business trip to U.S. X-(, and then finally get a luck by as follows !! ------------------- sys/eisa/3c5x9.c------------------------ *** 3c5x9.c Wed Jun 12 17:55:33 1996 --- 3c5x9.c.new Sun Jul 14 12:20:57 1996 *************** *** 292,299 **** --- 292,305 ---- GO_WINDOW(0); for(i = 0; i < 3; i++) sc->epb->eth_addr[i] = get_e(sc, i); + /* Even we get irq number from board, we should tell him.. + Otherwise we never get a H/W interrupt anymore...*/ + if ( irq == 9 ) + irq = 2; + outw(eisa_ioport->addr+ EP_W0_RESOURCE_CFG, SET_IRQ(irq)); + ep_attach(sc); if(eisa_enable_intr(e_dev, irq)) { ep_free(sc); ---------------- Snip Snip Snip Kiritorisen ----------------- ------------------- Configuration of Eisa part ------------- controller eisa0 controller bt0 controller scbus0 controller ep0 ------------------------------------------------------------- As you see, you can treat as bt driver and ep driver without problem! We should describe a 'LINT' config, shouldn't we? Thanks again, Atsushi. -- Atsushi Murai Internet: amurai@spec.co.jp System Planning and Engineering Co,.Ltd. Voice : +81-33833-5341 From owner-freebsd-current Sat Jul 13 21:09:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05412 for current-outgoing; Sat, 13 Jul 1996 21:09: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 VAA05378; Sat, 13 Jul 1996 21:09:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA06010; Sat, 13 Jul 1996 21:03:16 -0700 From: Terry Lambert Message-Id: <199607140403.VAA06010@phaeton.artisoft.com> Subject: Re: strangest weirdness To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 13 Jul 1996 21:03:16 -0700 (MST) Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, adam@veda.is In-Reply-To: <199607130821.KAA22966@uriah.heep.sax.de> from "J Wunsch" at Jul 13, 96 10:21:11 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 have also noticed that executables dump core often on client machines when > > the files on the fileserver have been updated "under their feet". Okay I know > > "if it hurts, don't do that", but why do these glitches occur? > > Terry will certainly jump in now and explain you that it would be > better to move over the entire executable into local swap instead of > relying on the ability to page it in from the NFS server. The latter > is what we're doing right now -- so you are simply not expected to > remove it on the server. The Unix semantics of ``a file will only be > removed once the last reference to it disappeared'' don't work over > NFS since the server simply doesn't know (and cannot know due to the > statelessness of the protocol) which clients still hold references on > some file. These semantics are being emulated in the case where you > unlink a file on the client that has still other references, by > renaming the file on the server first, and remove it later. Actually, you could implement a simple distributed cache coherency protocol for executables with a slight modification of the rpc.statd code in current and a minor change to the NFS client. It wouldn't be an NFS spec compliant implementation afterwards, but it would solve the problem. I would like to see a flag in the mount structure for FS's which is inherited from the FS type, so that the dev of an inode about to be exec'ed may be dereferenced through the mount struct to decide if the image is coming from local stable storage, local removable storage, or network storage. I would also like to se an option where an executable image could be forced into local memory. If swap is available, it would be considered to be local memory. I would like to see a default of the current behaviour, with sysctl based controls to cause the exec to force the image into local memory in the local removable media case or the network storage case, or both, under user configuration. To solve your problem (and for my personal defaults selection), you would set the flag for the exec from network storage case. Mach, Linux, SunOS, Solaris, SVR4, SCO Xenix, etc., all have the behaviour of using an image for swap store, and when the image is modified without notification (the image is modified on the NFS server case) or when the image is "deleted" without notification the CDROM/floppy removal case), the client system is the one that suffers. What makes this particularly onerous in NFS is that one NFS client can intentially crash another NFS client of the same server, given knowledge of what programs are running and a writable server store. In addition, this method can be used to hack an otherwise secure client, typically by rewriting the target page on the server so that when the accept completes on sendmail, it throws up a shell, or something similar. Sendmail is SUID root, so it is a bad example, but telnetd (/usr/libexec/telnetd) is a good candidate for this hack, since the ruserok() does not specifically block vouchsafe for "bin", only for "root", and telnetd is owned by "bin". Since this bin owned binary will be run by root (inetd) on a client connect, it is an ideal place to hack. Besides the security issues, it's just plain annoying to have the client quit functioning, or hang pending a pagin from the server when the server has gone down (diskless/dataless configurations of SunOS are frequently sworn at for this failing). 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 Sat Jul 13 21:15:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05874 for current-outgoing; Sat, 13 Jul 1996 21:15:49 -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 VAA05869 for ; Sat, 13 Jul 1996 21:15:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA06027; Sat, 13 Jul 1996 21:09:55 -0700 From: Terry Lambert Message-Id: <199607140409.VAA06027@phaeton.artisoft.com> Subject: Re: NFSv3 fixes for review To: dfr@nlsys.demon.co.uk (Doug Rabson) Date: Sat, 13 Jul 1996 21:09:55 -0700 (MST) Cc: current@FreeBSD.ORG, dfr@render.com In-Reply-To: <31E77EA6.41C67EA6@nlsys.demon.co.uk> from "Doug Rabson" at Jul 13, 96 11:47:02 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 have just integrated some fixes to the NFSv3 code from Frank van der > Linden (frank@fwi.uva.nl). The first bug is the same one as the > 'corrupt output from makesyscalls.sh on an nfsv3 mount' bug. I have > verified this one by testing on a loopback mount (which is all I can > do from my home machine). I have not tried to reproduce the second > two problems but the fixes seem safe. > > While I was here, I also fixed the truncated 32bit minor numbers on > nfsv3 mount bug. I believe that Bruce originally suggested the fix > for this? > > Could someone please review these changes (diffs included) so that I > can commit them. This fix seems to work right for me. I'm nervous about the use of the timeval, mostly because I'm not sure that it is monotonically increasing in the ntpd time synchronization case (and haven't looked deep enough to verify that the reported time from the microtime is not affected by adjustments. Is there a seperate monotonically increasing clock, which is not modified by time adjust? I guess this would be a factor only on a system with a relatively high drift rate (such that a reboot could occur such that the delay did not exceed the drift, causing the XID to go backward). 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 Sat Jul 13 21:26:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06547 for current-outgoing; Sat, 13 Jul 1996 21:26:49 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA06542 for ; Sat, 13 Jul 1996 21:26:47 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id VAA20099; Sat, 13 Jul 1996 21:27:16 -0700 Date: Sat, 13 Jul 1996 21:27:15 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: sound driver problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all, Just noticed that after a reboot, midi's and mod's won't play on my GUS Max w/1 meg for some reason.... Here is the output: dmesg |more gus0 at 0x220 irq 12 drq 1 on isa gus0: gus0: This is what I get on the console: Jul 13 19:26:16 bigbang /kernel: GUS: DMA Transfer timed out Jul 13 19:26:16 bigbang /kernel: isa_dmastart: channel 1 busy I am running July 4th -current with the same kernel build... Any ideas? Vince