From owner-freebsd-current Sun Jul 14 01:06:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA01281 for current-outgoing; Sun, 14 Jul 1996 01:06:20 -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 BAA01274 for ; Sun, 14 Jul 1996 01:06:14 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA20603; Sun, 14 Jul 1996 18:05:15 +1000 Date: Sun, 14 Jul 1996 18:05:15 +1000 From: Bruce Evans Message-Id: <199607140805.SAA20603@godzilla.zeta.org.au> To: dfr@nlsys.demon.co.uk, terry@lambert.org Subject: Re: NFSv3 fixes for review Cc: current@freebsd.org, dfr@render.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >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. xntpd only does tiny adjustments which can't possibly make the clock go backwards. OTOH, ntpdate or ordinary `date' can set the clock back by years. >Is there a seperate monotonically increasing clock, which is not >modified by time adjust? I guess this would be a factor only on a mono_time. >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). Oops, mono_time isn't monotonic across reboots. I think it is reset by reboot so it is very unsuitable. Bruce From owner-freebsd-current Sun Jul 14 02:43:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA15980 for current-outgoing; Sun, 14 Jul 1996 02:43: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 CAA15971 for ; Sun, 14 Jul 1996 02:43:27 -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 CAA22132 for ; Sun, 14 Jul 1996 02:43:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id CAA05482 for ; Sun, 14 Jul 1996 02:43:25 -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: keyboard/console problems? Date: Sun, 14 Jul 1996 02:43:25 PDT Message-ID: <5480.837337405@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm FreeBSD LISP-READER.csrv.uidaho.edu 2.2-CURRENT FreeBSD 2.2-CURRENT #1: Fri Jul 12 22:09:17 PDT 1996 fn@LISP-READER.csrv.uidaho.edu:/disk0/src/sys/compile/lisp-reader i386 p133, 32mb ram, #9-771 video, xfree86-312s, serial mouse, syscons, 9wm, xdm. Sometimes my keyboard ends up in a weird state: I can't switch console ttys; no keyboard input is accepted (even under X with "secure keyboard turned on"); and it appears that the control key is "stuck" (clicking on any window appears as if i'd held down the control key before clicking). I've seen this happen once on the console, when I wasn't running X at all, but I can't remember if it was before or after I upgraded from July 3rd sources. I certainly did not see this problem under X with my July 3rd kernel. Any ideas on where to look for solutions? thanks, faried. From owner-freebsd-current Sun Jul 14 07:10:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA13009 for current-outgoing; Sun, 14 Jul 1996 07:10:06 -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 HAA12976 for ; Sun, 14 Jul 1996 07:10:02 -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 HAA22488 for ; Sun, 14 Jul 1996 07:10:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id HAA05601 for ; Sun, 14 Jul 1996 07:09:59 -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: Re: keyboard/console problems? In-reply-to: Your message of "Sun, 14 Jul 1996 02:43:25 PDT." <5480.837337405@waldrog.cs.uidaho.edu> Date: Sun, 14 Jul 1996 07:09:58 PDT Message-ID: <5599.837353398@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i wrote... Sometimes my keyboard ends up in a weird state: I can't switch console ttys; no keyboard input is accepted (even under X with "secure keyboard turned on"); and it appears that the control key is "stuck" (clicking on any window appears as if i'd held down the control key before clicking). I got a lot of them last night and decided to switch to the july 3rd kernel. I got "stuck" again within minutes of booting off the older kernel. I have checked all the cables; nothing seems wrong. I did a sup & make world on Friday. I've noticed that the control key doesn't stick always; once it was the meta key, and a few times the mouse worked normally (could cut & paste). I'm now running xev to observe this problem if it reoccurs. One thing I forgot to mention was that I can "cure" this problem when under X by just killing my Xsession and logging in again via xdm. faried. From owner-freebsd-current Sun Jul 14 08:05:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA29197 for current-outgoing; Sun, 14 Jul 1996 08:05:40 -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 IAA29115 for ; Sun, 14 Jul 1996 08:05:28 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id aa13053; 14 Jul 96 15:05 GMT Received: from nlsys.demon.co.uk ([158.152.125.33]) by relay-3.mail.demon.net id aa16650; 14 Jul 96 15:01 +0100 Message-ID: <31E8FDC8.167EB0E7@nlsys.demon.co.uk> Date: Sun, 14 Jul 1996 15:01:44 +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 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here is a second attempt at these NFSv3 fixes, based on some feedback from Bruce Evans. I will commit these tomorrow unless anyone else has some comments. 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/14 13:46:05 *************** *** 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/14 13:46:18 *************** *** 635,640 **** --- 635,642 ---- 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 **** --- 655,676 ---- * 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) --- 850,857 ---- } /* ! * 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 **** --- 866,874 ---- int uiosiz, clflg, rem; char *cp; + if (uiop->uio_iovcnt != 1) + panic("nfsm_uiotombuf: iovcnt != 1"); + 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) --- 876,881 ---- *************** *** 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) { --- 910,917 ---- 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) { 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/14 13:46:52 *************** *** 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 Sun Jul 14 09:29:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21671 for current-outgoing; Sun, 14 Jul 1996 09:29:45 -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 JAA21660 for ; Sun, 14 Jul 1996 09:29:37 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id CAA00572 Mon, 15 Jul 1996 02:29:34 +1000 (EST) From: michael butler Message-Id: <199607141629.CAA00572@walkabout.asstdc.com.au> Subject: ep driver now unstable .. To: current@freebsd.org Date: Mon, 15 Jul 1996 02:29:34 +1000 (EST) Cc: nate@mt.sri.com X-Comment: InterNIC: IMB, AUNIC: MB11-AU X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Whatever changed in the last day or so in the ep driver has now resulted in the same symptoms as I had with the nep driver on my laptop. Intermittently, it'll just stop working and I have to use "ifconfig ep0 down; ifconfig ep0 up" to make it go again, michael From owner-freebsd-current Sun Jul 14 10:02:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01324 for current-outgoing; Sun, 14 Jul 1996 10:02:35 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA01217; Sun, 14 Jul 1996 10:02:23 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id MAA08234; Sun, 14 Jul 1996 12:02:03 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sun, 14 Jul 96 12:02 CDT Date: Sun, 14 Jul 1996 12:02:02 -0500 (CDT) From: Alex Nash X-Sender: nash@Venus.mcs.com To: michael butler cc: current@freebsd.org, nate@mt.sri.com, stable@freebsd.org Subject: Re: ep driver now unstable .. In-Reply-To: <199607141629.CAA00572@walkabout.asstdc.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Crossposted from current, please direct followups back to current ] On Mon, 15 Jul 1996, michael butler wrote: > Whatever changed in the last day or so in the ep driver has now resulted in > the same symptoms as I had with the nep driver on my laptop. Intermittently, > it'll just stop working and I have to use "ifconfig ep0 down; ifconfig ep0 > up" to make it go again, Yep, ep is broken (and unfortunately it's in 2.1.5). If you have the CVS archive, checkout rev 1.28.4.5 of if_ep.c for -stable, or rev 1.49 for -current. If you don't have the CVS archive, change: outw(BASE + EP_W1_TX_PIO_WR_1, len | 0x8000); /* XXX */ to outw(BASE + EP_W1_TX_PIO_WR_1, len); (line 775 for 2.1.5, line 967 for -current) Alex From owner-freebsd-current Sun Jul 14 10:47:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14586 for current-outgoing; Sun, 14 Jul 1996 10:47:45 -0700 (PDT) Received: from scrooge.ee.swin.oz.au (scrooge.ee.swin.oz.au [136.186.4.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA14565 for ; Sun, 14 Jul 1996 10:47:41 -0700 (PDT) Received: (from dtc@localhost) by scrooge.ee.swin.oz.au (8.6.9/8.6.9) id DAA21600 for current@freebsd.org; Mon, 15 Jul 1996 03:48:57 +1000 From: Douglas Thomas Crosher Message-Id: <199607141748.DAA21600@scrooge.ee.swin.oz.au> Subject: Re: ep driver now unstable .. To: current@freebsd.org Date: Mon, 15 Jul 1996 03:48:57 +1000 (EST) In-Reply-To: <199607141629.CAA00572@walkabout.asstdc.com.au> from "michael butler" at Jul 15, 96 02:29:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Whatever changed in the last day or so in the ep driver has now resulted in > the same symptoms as I had with the nep driver on my laptop. Intermittently, > it'll just stop working and I have to use "ifconfig ep0 down; ifconfig ep0 > up" to make it go again, I can confirm a similar experience. The card is a 3C509 early model. I did notice a patch to if_ep.c from 1.49 to 1.50. Douglas Crosher From owner-freebsd-current Sun Jul 14 11:15:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19872 for current-outgoing; Sun, 14 Jul 1996 11:15:53 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA19857 for ; Sun, 14 Jul 1996 11:15:48 -0700 (PDT) Received: from fiber.eng.umd.edu (fiber.eng.umd.edu [129.2.98.185]) by po1.glue.umd.edu (8.7.5/8.7.3) with ESMTP id OAA24239 for ; Sun, 14 Jul 1996 14:15:45 -0400 (EDT) Received: (from chuckr@localhost) by fiber.eng.umd.edu (8.7.5/8.7.3) id OAA28451; Sun, 14 Jul 1996 14:15:45 -0400 (EDT) Date: Sun, 14 Jul 1996 14:15:44 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@fiber.eng.umd.edu To: FreeBSD current Subject: sbin/route Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Make world doesn't survive this: cc -O2 -m486 -pipe -I. -c /usr/src/sbin/route/route.c /usr/src/sbin/route/route.c: In function `flushroutes': /usr/src/sbin/route/route.c:240: `K_ATALK' undeclared (first use this function) /usr/src/sbin/route/route.c:240: (Each undeclared identifier is reported only once /usr/src/sbin/route/route.c:240: for each function it appears in.) /usr/src/sbin/route/route.c: In function `newroute': /usr/src/sbin/route/route.c:572: `K_ATALK' undeclared (first use this function) *** Error code 1 I took a look into /usr/include/netatalk, but couldn't grep any mention of this K_ATALK ... ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Jul 14 12:26:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01887 for current-outgoing; Sun, 14 Jul 1996 12:26:35 -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 MAA01859 for ; Sun, 14 Jul 1996 12:25:55 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA22570; Sun, 14 Jul 1996 21:20:57 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA25582; Sun, 14 Jul 1996 21:20:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA12136; Sun, 14 Jul 1996 20:06:12 +0200 (MET DST) From: J Wunsch Message-Id: <199607141806.UAA12136@uriah.heep.sax.de> Subject: Re: ep driver now unstable .. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 14 Jul 1996 20:06:12 +0200 (MET DST) Cc: nate@mt.sri.com, mevans@candle.com (Mike Evans), imb@asstdc.com.au (michael butler) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607141629.CAA00572@walkabout.asstdc.com.au> from michael butler at "Jul 15, 96 02:29:34 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 michael butler wrote: > Whatever changed in the last day or so in the ep driver has now resulted in > the same symptoms as I had with the nep driver on my laptop. Intermittently, > it'll just stop working and I have to use "ifconfig ep0 down; ifconfig ep0 > up" to make it go again, Erm. Sh*t. :-(( Several people have reported in Usenet that their driver works much better with the flag set, and according to the author of the patch, it wasn't supposed to cause any additional harm. That's why i have asked David to bring this fix into 2.1.5 (i think it's been the last change before the tree was tagged). revision 1.50 date: 1996/07/13 10:49:53; author: davidg; state: Exp; lines: +2 -2 Enable transmit complete interrupt... (author's explaination): Bit 15 is the flag to request a transmit complete interrupt. The driver was apparently written to minimize interrupts, and if not for a 3-COM design quirk, everything would be just ducky. Prior to loading the outbound packet into the FIFO, the driver checks to see if there's enough space to contain the packet. If not, the driver requests a transmit-available interrupt when there is sufficient room. Unfortunately, the card is continuing to process the prior FIFO, and by the time the driver sets the threshold for a transmit available interrupt, the space is already available. When this occurs, the 3COM card ignores the interrupt request, and the driver is hung waiting for an interrupt that will never occur. There's probably a more elegant solution, but requesting the transmit complete interrupt was the easiest to implement. An alternative fix might be to check free FIFO space again, after requesting the transmit available interrupt, but I haven't bothered pursuing this. Since the patch, my 3C590 (PCI, same FIFO interface as 3C509) has been rock solid. Submitted by: mevans@candle.com (Mike Evans) OTOH, i've got exactly the same behaviour as you, Michael, with my 3C590, which was the main reason to hold the change back until i could get a better understanding. (Anyway, neither did it work *withou* the change.) Now, it seems that we've got two entirely different stories about this. For quite some people, setting this flag seems to be the ultimate solution, while it makes the driver instable for others. Sigh. -- 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 14 13:10:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09653 for current-outgoing; Sun, 14 Jul 1996 13:10:13 -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 NAA09642 for ; Sun, 14 Jul 1996 13:10:09 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA13776; Sun, 14 Jul 1996 13:04:13 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users), nate@mt.sri.com, mevans@candle.com (Mike Evans), imb@asstdc.com.au (michael butler) Subject: Re: ep driver now unstable .. In-reply-to: Your message of "Sun, 14 Jul 1996 20:06:12 +0200." <199607141806.UAA12136@uriah.heep.sax.de> Date: Sun, 14 Jul 1996 13:04:13 -0700 Message-ID: <13773.837374653@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Now, it seems that we've got two entirely different stories about > this. For quite some people, setting this flag seems to be the > ultimate solution, while it makes the driver instable for others. That's why it's generally a good idea to pass this stuff through -current for awhile first.. :-) Ah well, I think we'll live. Jordan From owner-freebsd-current Sun Jul 14 13:26:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13048 for current-outgoing; Sun, 14 Jul 1996 13:26:58 -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 NAA12919 for ; Sun, 14 Jul 1996 13:26:23 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id VAA24082 for ; Sun, 14 Jul 1996 21:31:13 +0100 Date: Sun, 14 Jul 1996 21:31:13 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: FreeBSD with 100Mbit ethernet card? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Another quick question, does FreeBSD current work with any 100Mbit ethernet cards? If so which one should we buy? Regards, Trefor S. From owner-freebsd-current Sun Jul 14 15:43:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA06759 for current-outgoing; Sun, 14 Jul 1996 15:43:06 -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 PAA06741 for ; Sun, 14 Jul 1996 15:42:59 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id PAA04414; Sun, 14 Jul 1996 15:42:45 -0700 From: "Rodney W. Grimes" Message-Id: <199607142242.PAA04414@GndRsh.aac.dev.com> Subject: Re: FreeBSD with 100Mbit ethernet card? To: dev@fgate.flevel.co.uk (Developer) Date: Sun, 14 Jul 1996 15:42:45 -0700 (PDT) Cc: freebsd-current@freebsd.org In-Reply-To: from Developer at "Jul 14, 96 09:31:13 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 > > Another quick question, does FreeBSD current work with any 100Mbit > ethernet cards? Yes, most, but not all, of the Dec DC21140 based cards work (the Compex ENET100TX-PCI does _NOT_ work in 100Mbs mode for some reason, I haven't had time to track the problem down with it. There is also support for the Intel EtherExpress Pro/100B, make sure it is a ``B'' model. > If so which one should we buy? I highly recommend this one: XX. TMG SMC9332DST SMC 10/100MB DEC 21140 ethernet $ 145.00 > Regards, > Trefor S. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sun Jul 14 16:01:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07807 for current-outgoing; Sun, 14 Jul 1996 16:01:18 -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 QAA07799 for ; Sun, 14 Jul 1996 16:01:15 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id QAA26313; Sun, 14 Jul 1996 16:01:44 -0700 Date: Sun, 14 Jul 1996 16:01:43 -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 14 14:26:16 bigbang /kernel: GUS: DMA Transfer timed out Jul 14 14:26:16 bigbang /kernel: isa_dmastart: channel 1 busy I am running July 14th -current with the same kernel build... Any ideas? Vince From owner-freebsd-current Sun Jul 14 21:41:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24092 for current-outgoing; Sun, 14 Jul 1996 21:41:59 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.186.250]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA24072 for ; Sun, 14 Jul 1996 21:41:57 -0700 (PDT) Received: (from dwhite@localhost) by gdi.uoregon.edu (8.6.12/8.6.12) id VAA00276; Sun, 14 Jul 1996 21:41:55 -0700 Date: Sun, 14 Jul 1996 21:41:55 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: faried nawaz cc: current@freebsd.org Subject: Re: keyboard/console problems? In-Reply-To: <5599.837353398@waldrog.cs.uidaho.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Jul 1996, faried nawaz wrote: > Sometimes my keyboard ends up in a weird state: I can't switch console ttys; > no keyboard input is accepted (even under X with "secure keyboard turned on"); > and it appears that the control key is "stuck" (clicking on any window appears > as if i'd held down the control key before clicking). > > I got a lot of them last night and decided to switch to the july 3rd kernel. > I got "stuck" again within minutes of booting off the older kernel. My computer (in general under any OS) has a fried keyboard controller that will lock up the keyboard. I wonder if yours just developed one. Sometimes switching terminals from X will stick the Cntrl key, just hit it and it should unlock. This is 2.1-R. > One thing I forgot to mention was that I can "cure" this problem when under > X by just killing my Xsession and logging in again via xdm. I have to cold boot the machine :( Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Sun Jul 14 22:30:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA00514 for current-outgoing; Sun, 14 Jul 1996 22:30:48 -0700 (PDT) Received: from localhost.my.domain (root@morrison-c18.aa.net [204.157.220.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA00505 for ; Sun, 14 Jul 1996 22:30:45 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by localhost.my.domain (8.7.5/8.6.12) with SMTP id WAA01474; Sun, 14 Jul 1996 22:30:29 -0700 (PDT) Date: Sun, 14 Jul 1996 22:30:29 -0700 (PDT) From: Sujal Patel X-Sender: smpatel@localhost To: Veggy Vinny cc: current@FreeBSD.ORG Subject: Re: sound driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 13 Jul 1996, Veggy Vinny wrote: > gus0 at 0x220 irq 12 drq 1 on isa > > Jul 13 19:26:16 bigbang /kernel: GUS: DMA Transfer timed out > Jul 13 19:26:16 bigbang /kernel: isa_dmastart: channel 1 busy Is your DRQ correct and not conflicting with another device? Sujal From owner-freebsd-current Sun Jul 14 22:34:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA00791 for current-outgoing; Sun, 14 Jul 1996 22:34:16 -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 WAA00786 for ; Sun, 14 Jul 1996 22:34:14 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id WAA19258; Sun, 14 Jul 1996 22:34:41 -0700 Date: Sun, 14 Jul 1996 22:34:40 -0700 (PDT) From: Veggy Vinny To: Sujal Patel cc: current@FreeBSD.ORG Subject: Re: sound driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Jul 1996, Sujal Patel wrote: > On Sat, 13 Jul 1996, Veggy Vinny wrote: > > > gus0 at 0x220 irq 12 drq 1 on isa > > > > Jul 13 19:26:16 bigbang /kernel: GUS: DMA Transfer timed out > > Jul 13 19:26:16 bigbang /kernel: isa_dmastart: channel 1 busy > > Is your DRQ correct and not conflicting with another device? Yes, it is..... Because nothing else in my system has that DRQ, or DMA.... Vince From owner-freebsd-current Mon Jul 15 00:01:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07541 for current-outgoing; Mon, 15 Jul 1996 00:01:30 -0700 (PDT) Received: from neptune.tadiran.co.il (neptune.telecomm.tadiran.co.il [194.90.74.66]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA07529 for ; Mon, 15 Jul 1996 00:01:24 -0700 (PDT) Received: (from yoav@localhost) by neptune.tadiran.co.il (8.7.5/8.7.3) id JAA26525 for current@freebsd.org; Mon, 15 Jul 1996 09:59:12 +0300 (IDT) Date: Mon, 15 Jul 1996 09:59:12 +0300 (IDT) From: Yoav Newman (1822) Message-Id: <199607150659.JAA26525@neptune.tadiran.co.il> To: current@freebsd.org Subject: Going on Vacation :) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Mon Jul 15 00:02:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07602 for current-outgoing; Mon, 15 Jul 1996 00:02:12 -0700 (PDT) Received: from neptune.tadiran.co.il (neptune.telecomm.tadiran.co.il [194.90.74.66]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA07592 for ; Mon, 15 Jul 1996 00:02:06 -0700 (PDT) Received: (from yoav@localhost) by neptune.tadiran.co.il (8.7.5/8.7.3) id JAA26548 for freebsd-current@freebsd.org; Mon, 15 Jul 1996 09:59:54 +0300 (IDT) Date: Mon, 15 Jul 1996 09:59:54 +0300 (IDT) From: Yoav Newman (1822) Message-Id: <199607150659.JAA26548@neptune.tadiran.co.il> To: freebsd-current@freebsd.org Subject: Going on Vacation :) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Mon Jul 15 00:16:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA08974 for current-outgoing; Mon, 15 Jul 1996 00:16:09 -0700 (PDT) Received: from neptune.tadiran.co.il (neptune.telecomm.tadiran.co.il [194.90.74.66]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA08891; Mon, 15 Jul 1996 00:15:42 -0700 (PDT) Received: (from yoav@localhost) by neptune.tadiran.co.il (8.7.5/8.7.3) id KAA26982; Mon, 15 Jul 1996 10:13:22 +0300 (IDT) Date: Mon, 15 Jul 1996 10:13:22 +0300 (IDT) From: Yoav Newman X-Sender: yoav@neptune 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 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk _/ _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/ _/_/ _/ _/_/ _/ _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/_/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/_/ _/ _/ _/_/ _/_/ _/ _/ _/ _/ _/_/_/ _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/ _/ _/_/ -/_/ _/ _/ _/_/_/_/ _/ _/_/ _/ _/ _/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/_/ _/ _/_/_/_/ _/_/_/ _/_/_/_/ _/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/_/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ _/ _/ _/_/_/_/ _/ _/ _/ _/ _/ _/_/_/_/ _/ _/_/ _/ _/ _/ _/_/_/_/ _/_/_/ _/ _/ _/ _/ _/ _/ From owner-freebsd-current Mon Jul 15 02:13:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA19888 for current-outgoing; Mon, 15 Jul 1996 02:13:12 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA19877 for ; Mon, 15 Jul 1996 02:13:06 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA28863 (5.67a/IDA-1.5 for ); Mon, 15 Jul 1996 12:13:02 +0300 Received: (from count@localhost) by key.hole.fi (8.7.5/8.6.12) id MAA08595; Mon, 15 Jul 1996 12:13:01 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199607150913.MAA08595@key.hole.fi> Subject: Re: FreeBSD with 100Mbit ethernet card? To: dev@fgate.flevel.co.uk (Developer) Date: Mon, 15 Jul 1996 12:13:00 +0300 (EET DST) Cc: current@freebsd.org In-Reply-To: from "Developer" at Jul 14, 96 09:31:13 pm X-Mailer: ELM [version 2.4 PL24alpha5] 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 Developer taisi sanoa: > Another quick question, does FreeBSD current work with any 100Mbit > ethernet cards? If so which one should we buy? I'm using an Allied Telesyn AT-2560TX 10/100Mbit card under 2.1.5-RELEASE. It works, gets recognized as Intel Pro/100B but for unknown reason it can't transmit very fast. I'd think that -current has the same driver or perhaps a newer revision of the same. -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Pengerkatu 13b A5 % IRC: Count NIC: BH271 % FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Mon Jul 15 02:21:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20784 for current-outgoing; Mon, 15 Jul 1996 02:21:51 -0700 (PDT) Received: from proxy.siemens.at (proxy.siemens.at [192.138.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA20750; Mon, 15 Jul 1996 02:21:31 -0700 (PDT) Received: from sol1.gud.siemens.co.at (sol-f.gud.siemens-austria) by proxy.siemens.at with SMTP id AA28633 (5.67a/IDA-1.5); Mon, 15 Jul 1996 11:20:51 +0200 Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0ufjpi-00021UC; Mon, 15 Jul 96 11:20 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA254952338; Mon, 15 Jul 1996 11:18:58 +0200 From: "Hr.Ladavac" Message-Id: <199607150918.AA254952338@ws2301.gud.siemens.co.at> Subject: Re: strangest weirdness To: adam@veda.is (Adam David) Date: Mon, 15 Jul 1996 11:18:58 +0200 (MESZ) Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org In-Reply-To: <199607130027.AAA07477@veda.is> from "Adam David" at Jul 13, 96 00:27:54 am X-Mailer: ELM [version 2.4 PL24 ME8a] 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 In his e-mail Adam David wrote: > 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? Well, to cut the long story short, that's sadly the way NFS works. Namely, executable is being paged in from the server. If you change the executable file between (or during) pages, who knows what will be read. Nonsense, most likely :( This does not happen on non-NFS mounted volumes (read: local) since then the ETXTBUSY is returned to the potential writer. Alas, NFS server does not know what is being done to the file it serves (i.e. it does not know that it's actually being executed, rather than just randomly read.) A possible workaround would be commiting all nfs mounted executables to swap, but to the best of my knowledge nobody does that (yes, the big commercial boys suffer from the same illness.) Terry will probably correct me :) /Marino > > -- > Adam David > From owner-freebsd-current Mon Jul 15 03:07:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA25101 for current-outgoing; Mon, 15 Jul 1996 03:07:13 -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 DAA25094 for ; Mon, 15 Jul 1996 03:07:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id DAA02830; Mon, 15 Jul 1996 03:05:42 -0700 (PDT) Message-Id: <199607151005.DAA02830@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Bror 'Count' Heinola" cc: dev@fgate.flevel.co.uk (Developer), current@FreeBSD.ORG Subject: Re: FreeBSD with 100Mbit ethernet card? In-reply-to: Your message of "Mon, 15 Jul 1996 12:13:00 +0300." <199607150913.MAA08595@key.hole.fi> From: David Greenman Reply-To: davidg@root.com Date: Mon, 15 Jul 1996 03:05:42 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Developer taisi sanoa: > >> Another quick question, does FreeBSD current work with any 100Mbit >> ethernet cards? If so which one should we buy? > > I'm using an Allied Telesyn AT-2560TX 10/100Mbit card under > 2.1.5-RELEASE. It works, gets recognized as Intel Pro/100B > but for unknown reason it can't transmit very fast. Can you clarify about "can't transmit very fast"? I get excellent performance with the card myself - I'm using them in all of the machines I have here. > I'd think that -current has the same driver or perhaps a newer > revision of the same. Right, it's the same driver. The only known problem is that I don't have a work-around for a bug in the chip that causes it to lock up if it receives garbage (can happen when you unplug the cable from the card). There's no way to detect the hang except to notice that nothing is being received for awhile. Newer revs of the chip don't have this problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 15 03:11:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA25584 for current-outgoing; Mon, 15 Jul 1996 03:11:58 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA25578 for ; Mon, 15 Jul 1996 03:11:55 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA02627 (5.67a/IDA-1.5 for ); Mon, 15 Jul 1996 13:11:52 +0300 Received: (from count@localhost) by key.hole.fi (8.7.5/8.6.12) id NAA08751; Mon, 15 Jul 1996 13:11:51 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199607151011.NAA08751@key.hole.fi> Subject: Re: FreeBSD with 100Mbit ethernet card? To: davidg@root.com Date: Mon, 15 Jul 1996 13:11:51 +0300 (EET DST) Cc: current@freebsd.org In-Reply-To: <199607151005.DAA02830@root.com> from "David Greenman" at Jul 15, 96 03:05:42 am X-Mailer: ELM [version 2.4 PL24alpha5] 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 David Greenman taisi sanoa: > > Can you clarify about "can't transmit very fast"? I get excellent > performance with the card myself - I'm using them in all of the machines > I have here. Well, when I transfer files from an Ultra 1 with fast ethernet I can 'put' them at over 5Mbytes/sec but when I 'get' them from the BSD box they don't come faster than about 1.5Mbytes/sec. Did you see my mail about it in freebsd-hardware? I'm forwarding it to you anyway... > Right, it's the same driver. The only known problem is that I don't have a > work-around for a bug in the chip that causes it to lock up if it receives > garbage (can happen when you unplug the cable from the card). There's no > way to detect the hang except to notice that nothing is being received for > awhile. Newer revs of the chip don't have this problem. That's a nasty bug :( -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Pengerkatu 13b A5 % IRC: Count NIC: BH271 % FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Mon Jul 15 03:13:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA25671 for current-outgoing; Mon, 15 Jul 1996 03:13:43 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA25666 for ; Mon, 15 Jul 1996 03:13:39 -0700 (PDT) Received: (from dfr@localhost) by minnow.render.com (8.6.12/8.6.9) id KAA07653; Mon, 15 Jul 1996 10:17:51 +0100 Date: Mon, 15 Jul 1996 10:17:51 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: NFSv3 fixes for review In-Reply-To: <199607140409.VAA06027@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 13 Jul 1996, Terry Lambert wrote: > > 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). I think that the time is only used to specify the first xid used. Subsequent ids just increment the first one. The fix was needed because some servers noticed xids for a client going back to zero when the client rebooted and complained. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Mon Jul 15 03:31:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26950 for current-outgoing; Mon, 15 Jul 1996 03:31:01 -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 DAA26938 for ; Mon, 15 Jul 1996 03:30:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id DAA02944; Mon, 15 Jul 1996 03:29:44 -0700 (PDT) Message-Id: <199607151029.DAA02944@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Bror 'Count' Heinola" cc: current@freebsd.org Subject: Re: FreeBSD with 100Mbit ethernet card? In-reply-to: Your message of "Mon, 15 Jul 1996 13:11:51 +0300." <199607151011.NAA08751@key.hole.fi> From: David Greenman Reply-To: davidg@root.com Date: Mon, 15 Jul 1996 03:29:43 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >David Greenman taisi sanoa: >> >> Can you clarify about "can't transmit very fast"? I get excellent >> performance with the card myself - I'm using them in all of the machines >> I have here. > > Well, when I transfer files from an Ultra 1 with fast ethernet I > can 'put' them at over 5Mbytes/sec but when I 'get' them from > the BSD box they don't come faster than about 1.5Mbytes/sec. > > Did you see my mail about it in freebsd-hardware? I'm forwarding > it to you anyway... Just finished reading it. It's really hard to say where the performance problem is coming from. ping isn't a very good benchmark utility for a variety of reasons. For one, it tends to cause an excessively large number of collisions. ping -f is also sort of synchronous - from the manual page: -f Flood ping. Outputs packets as fast as they come back or one hundred times per second, whichever is more. For every This will likely defeat any streaming that could otherwise occur. I usually use 'ttcp' for benchmarking, but other TCP/UDP benchmarks utilities are also available (I think 'tcpblast' is in the ports tree). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 15 04:40:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA01629 for current-outgoing; Mon, 15 Jul 1996 04:40:42 -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 EAA01623 for ; Mon, 15 Jul 1996 04:40:35 -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 EAA25899; Mon, 15 Jul 1996 04:40:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id EAA06124; Mon, 15 Jul 1996 04:40:18 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: dwhite@resnet.uoregon.edu cc: current@freebsd.org Subject: Re: keyboard/console problems? In-reply-to: Your message of "Sun, 14 Jul 1996 21:41:55 PDT." Date: Mon, 15 Jul 1996 04:40:17 PDT Message-ID: <6122.837430817@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Doug White wrote... My computer (in general under any OS) has a fried keyboard controller that will lock up the keyboard. I wonder if yours just developed one. I switched keyboards, and I haven't had it lock up all night. If it happens again, I'll try checking the computer. From owner-freebsd-current Mon Jul 15 05:29:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA03412 for current-outgoing; Mon, 15 Jul 1996 05:29:36 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA03405 for ; Mon, 15 Jul 1996 05:29:19 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail-queue invoked from smtpd); 15 Jul 1996 12:28:34 +0000 (GMT) Received: from localhost (HELO verdi.nethelp.no) (@127.0.0.1) by localhost with SMTP; 15 Jul 1996 12:28:34 +0000 (GMT) To: bde@zeta.org.au Cc: current@freebsd.org Subject: xntpd stepping clock backwards? (was: Re: NFSv3 fixes for review) In-Reply-To: Your message of "Sun, 14 Jul 1996 18:05:15 +1000" References: <199607140805.SAA20603@godzilla.zeta.org.au> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 15 Jul 1996 14:28:34 +0200 Message-ID: <20426.837433714@verdi.nethelp.no> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >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. > > xntpd only does tiny adjustments which can't possibly make the clock > go backwards. OTOH, ntpdate or ordinary `date' can set the clock back > by years. Then why does my syslog show the following? It sure looks to me like xntpd sometimes steps the clock backwards. This is on 2.2-960612-SNAP. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Jul 7 14:57:36 verdi xntpd[84]: time reset (step) 0.151413 s Jul 7 21:34:16 verdi xntpd[84]: time reset (step) 0.133152 s Jul 9 17:32:48 verdi xntpd[84]: time reset (step) -0.135963 s Jul 9 17:37:49 verdi xntpd[84]: time reset (step) 0.133687 s Jul 10 00:15:54 verdi xntpd[87]: time reset (step) -0.321460 s Jul 11 00:12:52 verdi xntpd[84]: time reset (step) -2.264120 s Jul 11 03:24:08 verdi xntpd[84]: time reset (step) -0.211536 s Jul 11 13:28:57 verdi xntpd[84]: time reset (step) -0.146236 s Jul 11 22:45:37 verdi xntpd[83]: time reset (step) -0.669474 s Jul 14 17:28:57 verdi xntpd[83]: time reset (step) 0.159320 s Jul 15 05:24:55 verdi xntpd[83]: time reset (step) 0.128810 s From owner-freebsd-current Mon Jul 15 08:21:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17154 for current-outgoing; Mon, 15 Jul 1996 08:21:12 -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 IAA17142 for ; Mon, 15 Jul 1996 08:21:00 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA21718 for ; Mon, 15 Jul 1996 17:20:46 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA05445 for freebsd-current@FreeBSD.org; Mon, 15 Jul 1996 17:20:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id RAA16886 for freebsd-current@FreeBSD.org; Mon, 15 Jul 1996 17:19:17 +0200 (MET DST) From: J Wunsch Message-Id: <199607151519.RAA16886@uriah.heep.sax.de> Subject: Question regarding device mmap()ing To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 15 Jul 1996 17:19:17 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk While writing a device driver, i've included a foommap() function, since i thought this was an ideal test environment. (The device communicates with the driver using a shared memory region in the ISA hole anyway.) Well, everything works fine, the stub that's required in the driver is funny small. The only thing that doesn't work is to mmap() the memory region into a user program, and then try accessing it with a debugger. The entire system stalls with a quickly growing number of processes sleeping on "lockrd". Is this the way it is supposed to be? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jul 15 08:38:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA18031 for current-outgoing; Mon, 15 Jul 1996 08:38: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 IAA18024 for ; Mon, 15 Jul 1996 08:38:32 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA11824; Mon, 15 Jul 1996 11:38:02 -0400 Date: Mon, 15 Jul 1996 11:38:02 -0400 From: Garrett Wollman Message-Id: <9607151538.AA11824@halloran-eldar.lcs.mit.edu> To: sthaug@nethelp.no Cc: bde@zeta.org.au, current@freebsd.org Subject: xntpd stepping clock backwards? (was: Re: NFSv3 fixes for review) In-Reply-To: <20426.837433714@verdi.nethelp.no> References: <199607140805.SAA20603@godzilla.zeta.org.au> <20426.837433714@verdi.nethelp.no> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk <> xntpd only does tiny adjustments which can't possibly make the clock >> go backwards. OTOH, ntpdate or ordinary `date' can set the clock back >> by years. > Then why does my syslog show the following? It sure looks to me like xntpd > sometimes steps the clock backwards. This is on 2.2-960612-SNAP. > Jul 7 14:57:36 verdi xntpd[84]: time reset (step) 0.151413 s > Jul 7 21:34:16 verdi xntpd[84]: time reset (step) 0.133152 s > Jul 9 17:32:48 verdi xntpd[84]: time reset (step) -0.135963 s > Jul 9 17:37:49 verdi xntpd[84]: time reset (step) 0.133687 s xntpd will fall back to stepping the clock if the difference is too great for adjtime(2) or adjtime doesn't appear to be working (which means the same thing). In your case, it looks very much like your machine is clock-hopping, a problem to which xntpd is extremely prone if you have lots of clocks and bad network connections to them. You can probably solve this problem by deleting the extra clocks from your ntp.conf file, or by choosing ones that are closer to you. -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 15 09:40:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22109 for current-outgoing; Mon, 15 Jul 1996 09:40:45 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.186.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22104 for ; Mon, 15 Jul 1996 09:40:42 -0700 (PDT) Received: (from dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) id JAA00999; Mon, 15 Jul 1996 09:40:09 -0700 (PDT) Date: Mon, 15 Jul 1996 09:40:09 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: sthaug@nethelp.no cc: bde@zeta.org.au, current@freebsd.org Subject: Re: xntpd stepping clock backwards? (was: Re: NFSv3 fixes for review) In-Reply-To: <20426.837433714@verdi.nethelp.no> 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, 15 Jul 1996 sthaug@nethelp.no wrote: > > xntpd only does tiny adjustments which can't possibly make the clock > > go backwards. OTOH, ntpdate or ordinary `date' can set the clock back > > by years. > > Then why does my syslog show the following? It sure looks to me like xntpd > sometimes steps the clock backwards. This is on 2.2-960612-SNAP. I think you are misinterpeting the log entry. xtnpd works by adjusting the length of a 'tick' so the clock 'speeds up' or 'slows down' as necessary. This adjustment is called 'slew' and is inserted in very, very small increments. But time continues to move forward, even if it means slewing the ticks for quite a while. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Mon Jul 15 13:12:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07126 for current-outgoing; Mon, 15 Jul 1996 13:12:22 -0700 (PDT) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07017 for ; Mon, 15 Jul 1996 13:11:55 -0700 (PDT) Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.6.12/8.6.9) with SMTP id QAA11293; Mon, 15 Jul 1996 16:11:25 -0400 Received: from localhost by mumps.pfcs.com with SMTP id AA00110 (5.67b/IDA-1.5); Mon, 15 Jul 1996 16:11:24 -0400 To: sthaug@nethelp.no Cc: bde@zeta.org.au, current@freebsd.org Subject: Re: xntpd stepping clock backwards? (was: Re: NFSv3 fixes for review) In-Reply-To: sthaug@nethelp.no's message dated Mon, 15 Jul 1996 14:28:34. <20426.837433714@verdi.nethelp.no> Date: Mon, 15 Jul 1996 16:11:22 -0300 Message-Id: <108.837461482@mumps.pfcs.com> From: Harlan Stenn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How stable is the reference you're syncing with? If it's not being stable, that's one possibilty. More likely is that the clock in your machine is a bit off. How big is the drift value in /etc/ntp.drift (check for the "driftfile /wherever" line in ntp.conf)? The first number should be between -105.xxx and 105.xxx. If it's not, you'll need to run tickadj -t (once when you decide to change it, and at boot time). Here's a script I've used that usually does the right thing. Note that if you change the "base" value of tick using "tickadj -t " then this script will show you the size and amount of change, not the actual value to put in. H #! /usr/bin/perl # # drift of 104.8576 -> -1 tick. Base of 10000 ticks. # $df="/etc/ntp.drift"; $base=10000; $cvt=104.8576; $v1=0.; $v2=0; if (open(DF, $df)) { if ($_=) { ($v1, $v2) = split; } while ($v1 gt $cvt) { $v1 -= $cvt; $base--; } while ($v1 lt 0) { $v1 += $cvt; $base++; } } printf("%.3f %d\n", $v1,$v2); print("$base\n"); From owner-freebsd-current Mon Jul 15 13:19:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07436 for current-outgoing; Mon, 15 Jul 1996 13:19:21 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07396; Mon, 15 Jul 1996 13:19:11 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id NAA19469 ; Mon, 15 Jul 1996 13:18:35 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA13806; Mon, 15 Jul 1996 16:17:08 -0400 Date: Mon, 15 Jul 1996 16:17:08 -0400 From: Garrett Wollman Message-Id: <9607152017.AA13806@halloran-eldar.lcs.mit.edu> To: current@freebsd.org Cc: hackers@freebsd.org, core@freebsd.org Subject: [John Wroclawski: Job] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I hope the other readers of these lists don't mind my posting this. It seemed like the smallest spanning set of people in the FreeBSD community who might also have the necessary technical expertise and cluefulness. Apologies to those who receive multiple copies. Replies via paper mail to the address given below; for further information, e-mail John at the address below. -GAWollman ------- start of forwarded message (RFC 934 encapsulation) ------- Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" From: John Wroclawski To: girod@lcs.mit.edu, wollman@lcs.mit.edu Subject: Job Date: Fri, 12 Jul 1996 17:40:25 -0400 [personal note deleted] Network Software Engineer Develop software to support research in next-generation computer networks: high performance TCP/IP, ATM, audio and video Internet services, new security, policy, and pricing mechanisms, network simulation and modeling, operating system support for high-performance protocols, and related areas. Work with research staff members and students to carry projects from rough ideas to publicly available programs. This position requires a strong background in network protocol and operating system kernel programming. Candidates should have detailed knowledge of one or more of the following areas: IP and TCP protocol implementation, IP multicast, RSVP, fast packet routing, BSD 4.3 or 4.4 kernel programming, virtual memory system design, embedded system programming. Familiarity with hardware design and hardware-related programming, such as high-performance device driver or microcoding experience, is a plus. Applicants should hold a Bachelor's degree in Computer Science or equivalent, and have experience which demonstrates specific ability to develop and optimize performance-critical code. A project-oriented Master's degree is desirable. The successful candidate will have time and personal management skills needed to work independently on several projects at once, and will have the communication skills needed to document their work and explain it to others both verbally and in writing. Please send hardcopy and refer to the job number, 96-0222R. Send two copies of a cover letter and your resume to: Massachusetts Institute of Technology Personnel Office E19-239 77 Massachusetts Ave. Cambridge, MA 02139-4307 617/253-4251 URL: ____________________ EMPLOYMENT POLICY: MIT is an equal opportunity/affirmative action employer. The Massachusetts Institute of Technology does not discriminate against any employee or applicant for employment on the basis of race, color, gender, sexual orientation, religion, disability, veteran status, age, or national or ethnic origin in the administration of its employment policies and practices. ------- end ------- From owner-freebsd-current Mon Jul 15 14:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16931 for current-outgoing; Mon, 15 Jul 1996 14:18:51 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16921 for ; Mon, 15 Jul 1996 14:18:46 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id RAA00715 for freebsd-current@freebsd.org; Mon, 15 Jul 1996 17:29:18 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607152129.RAA00715@prozac.neuron.net> Subject: [2.2-960612-SNAP] panic: vm_page_free To: freebsd-current@freebsd.org Date: Mon, 15 Jul 1996 17:29:18 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been running 2.2-960612-SNAP without a problem for the better part of a month now and the machine just spontaneously rebooted itself out of nowhere. It was't experiencing heavy load or running anything particularly strange. I had recompiled the kernel last week to trim some stuff out and I *might* have accidentally removed something important but even so, it's been running fine with this kernel for 4 or 5 days now. I got the following in my /var/log/messages file: Jul 15 17:00:18 prozac /kernel: vm_page_free: pindex(0), busy(0), PG_BUSY(0), ho ld(1) Jul 15 17:00:18 prozac /kernel: panic: vm_page_free: freeing busy page The Machine is an Intel P120 with an ASUS motherboard, 64 meg of RAM, a 2940UW SCSI card, a pair of Baraccudas, an HP C1533A DAT drive, and an ATI Mach64 video card. Any suggestions? -Amir From owner-freebsd-current Mon Jul 15 16:04:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26664 for current-outgoing; Mon, 15 Jul 1996 16:04:07 -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 QAA26616 for ; Mon, 15 Jul 1996 16:04:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id RAA29506 for ; Mon, 15 Jul 1996 17:03:57 -0600 (MDT) Message-Id: <199607152303.RAA29506@rover.village.org> To: current@freebsd.org Subject: Nits Date: Mon, 15 Jul 1996 17:03:56 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I do a make depend all install, it seems to be rebuilding ALL of the binaries. Is this normal expected behavior, or just the result of the make world changing the times of the libraries when it installed them? Also, A couple of warnings in -current when building. Not a big deal, but I thought I'd point them out in case this is something broken. This is as of ctm 2238. The warnings from handbook are new between this and my last build with July 11ish sources. ===> lib/libss cc -O -I. -I/other/imp/FreeBSD/current/src/lib/libss -DPOSIX -DIN_LIBSS -c /other/imp/FreeBSD/current/src/lib/libss/error.c -o error.o /other/imp/FreeBSD/current/src/lib/libss/error.c: In function `ss_error': /other/imp/FreeBSD/current/src/lib/libss/error.c:91: warning: passing arg 1 of `free' discards `const' from pointer target type ===> share/doc/handbook sgmlfmt -f ascii /other/imp/FreeBSD/current/src/share/doc/handbook/handbook.sgml :95: warning: `SN' not defined :633: warning: can't break line :6788: warning: numeric expression expected (got `I') :26726: warning: space required between `LP' and argument :33769: warning: `LH' not defined :33769: warning: `RH' not defined generating handbook.ascii... ===> share/examples "Makefile", line 1: warning: Couldn't read shell's output ===> usr.bin/mk_cmds cc -O -I. -I/other/imp/FreeBSD/current/src/usr.bin/mk_cmds/../../lib/libss -DIN_MK_CMDS -c /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c: In function `generate_rqte': /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c:71: warning: assignment makes pointer from integer without a cast /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c: In function `gensym': /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c:90: warning: assignment makes pointer from integer without a cast /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c: In function `str_concat3': /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c:105: warning: assignment makes pointer from integer without a cast /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c: In function `quote': /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c:119: warning: assignment makes pointer from integer without a cast /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c: In function `ds': /other/imp/FreeBSD/current/src/usr.bin/mk_cmds/utils.c:133: warning: assignment makes pointer from integer without a cast Warner From owner-freebsd-current Mon Jul 15 17:03:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA01378 for current-outgoing; Mon, 15 Jul 1996 17:03:00 -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 RAA01359 for ; Mon, 15 Jul 1996 17:02:53 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id KAA24680; Tue, 16 Jul 1996 10:00:03 +1000 Date: Tue, 16 Jul 1996 10:00:03 +1000 From: Bruce Evans Message-Id: <199607160000.KAA24680@godzilla.zeta.org.au> To: dwhite@resnet.uoregon.edu, sthaug@nethelp.no Subject: Re: xntpd stepping clock backwards? (was: Re: NFSv3 fixes for review) Cc: bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > xntpd only does tiny adjustments which can't possibly make the clock >> > go backwards. OTOH, ntpdate or ordinary `date' can set the clock back >> > by years. >> >> Then why does my syslog show the following? It sure looks to me like xntpd >> sometimes steps the clock backwards. This is on 2.2-960612-SNAP. >I think you are misinterpeting the log entry. xtnpd works by adjusting >the length of a 'tick' so the clock 'speeds up' or 'slows down' as >necessary. This adjustment is called 'slew' and is inserted in very, >very small increments. But time continues to move forward, even if it >means slewing the ticks for quite a while. That's what I thought. Unfortunately, xntpd really does step the clock in some cases, unless SLEWALWAYS is defined. Bruce From owner-freebsd-current Mon Jul 15 18:11:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08577 for current-outgoing; Mon, 15 Jul 1996 18:11: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 SAA08548 for ; Mon, 15 Jul 1996 18:11:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA26911; Tue, 16 Jul 1996 11:11:15 +1000 Date: Tue, 16 Jul 1996 11:11:15 +1000 From: Bruce Evans Message-Id: <199607160111.LAA26911@godzilla.zeta.org.au> To: current@freebsd.org, imp@village.org Subject: Re: Nits Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >When I do a make depend all install, it seems to be rebuilding >ALL of the binaries. Is this normal expected behavior, or just the >result of the make world changing the times of the libraries when it >installed them? Both. Unless you define INSTALL as `INSTALL -C' to avoid clobbering the times of unchanged installed files. The libraries change a lot anyway, but relinking all the binaries doesn't take long, so no one has been annoyed enough to fix this or the bogon that dynamically linked executables don't actually depend on the static libraries. >Also, A couple of warnings in -current when building. Not a big deal, >but I thought I'd point them out in case this is something broken. >This is as of ctm 2238. The warnings from handbook are new between >this and my last build with July 11ish sources. Only the ones for line 6788 and 26767 are actuall new. The others are in my May 5 log which wasn't much different from my October log. The libss and mk_cmds warnings are new. The ones for mk_cmds are caused by cleaning up libss. ss_internal.h no longer declares malloc(), but mk_cmds depends on it being declared there. Bruce From owner-freebsd-current Mon Jul 15 18:41:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA11632 for current-outgoing; Mon, 15 Jul 1996 18:41:06 -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 SAA11617 for ; Mon, 15 Jul 1996 18:40:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id TAA09168; Mon, 15 Jul 1996 19:40:27 -0600 (MDT) Message-Id: <199607160140.TAA09168@rover.village.org> To: Bruce Evans Subject: Re: Nits Cc: current@freebsd.org In-reply-to: Your message of Tue, 16 Jul 1996 11:11:15 +1000 Date: Mon, 15 Jul 1996 19:40:26 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : Both. Unless you define INSTALL as `INSTALL -C' to avoid clobbering the : times of unchanged installed files. The libraries change a lot anyway, : but relinking all the binaries doesn't take long, so no one has been : annoyed enough to fix this or the bogon that dynamically linked : executables don't actually depend on the static libraries. Cool. So setenv INSTALL "install -C" should do the trick for me before I build, right? I should also be able to put this in /etc/make.conf, if I read sys.mk correctly. Without that hack, it took 1:11:35 to do a make all install. I'll have to see what delta that has on the build time. Also, should I bother with make depend? It takes another hour on my machine. It seems that there should be an easy way to tell if the .depend file is out of date or not. Will have to think about this because I want to use the feature, but not pay so high a price when 20 files in the whole system have changed. Or does this fall into the category of "always do a make depend, or we'll not help you if you get an odd failure" category? Warner From owner-freebsd-current Mon Jul 15 18:41:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA11696 for current-outgoing; Mon, 15 Jul 1996 18:41:55 -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 SAA11690 for ; Mon, 15 Jul 1996 18:41:52 -0700 (PDT) Received: (from uucp@localhost) by specgw.spec.co.jp (8.7.5/3.3Wb-SPEC) with UUCP id KAA15738; Tue, 16 Jul 1996 10:40:54 +0900 (JST) Received: from amuraim.spec.co.jp by tama.spec.co.jp (8.7.5/6.4J.5) id KAA00225; Tue, 16 Jul 1996 10:44:55 +0900 (JST) Message-ID: <31EAF446.2D93@spec.co.jp> Date: Tue, 16 Jul 1996 10:45:42 +0900 From: Atsushi Murai Reply-To: amurai@spec.co.jp Organization: System Planning and Engineering Co,.Ltd X-Mailer: Mozilla 3.0b4 (Win95; I) MIME-Version: 1.0 To: "Justin T. Gibbs" , 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 Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) References: <199607140346.MAA01006@tama.spec.co.jp> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Should I commit this to -current unless nobody has problem? > ------------------- 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 ----------------- Atsushi. From owner-freebsd-current Mon Jul 15 18:43:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA11900 for current-outgoing; Mon, 15 Jul 1996 18:43:36 -0700 (PDT) Received: from crow.csrv.uidaho.edu (root@crow.csrv.uidaho.edu [129.101.119.223]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA11891 for ; Mon, 15 Jul 1996 18:43:34 -0700 (PDT) Received: from goshawk.csrv.uidaho.edu (goshawk.csrv.uidaho.edu [129.101.119.224]) by crow.csrv.uidaho.edu (8.7.5/8.7.3) with ESMTP id SAA13281; Mon, 15 Jul 1996 18:43:26 -0700 (PDT) Received: from localhost (harsh882@localhost) by goshawk.csrv.uidaho.edu (8.7.5/8.7.3) with SMTP id SAA21781; Mon, 15 Jul 1996 18:43:25 -0700 (PDT) Date: Mon, 15 Jul 1996 18:43:25 -0700 (PDT) From: Mike Harshbarger X-Sender: harsh882@goshawk.csrv.uidaho.edu To: freebsd-current@freebsd.org cc: Veggy Vinny Subject: Re: sound driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Jul 1996, Veggy Vinny wrote: > On Sun, 14 Jul 1996, Sujal Patel wrote: > > > On Sat, 13 Jul 1996, Veggy Vinny wrote: > > > > > gus0 at 0x220 irq 12 drq 1 on isa > > > > > > Jul 13 19:26:16 bigbang /kernel: GUS: DMA Transfer timed out > > > Jul 13 19:26:16 bigbang /kernel: isa_dmastart: channel 1 busy > > > > Is your DRQ correct and not conflicting with another device? > > Yes, it is..... Because nothing else in my system has that DRQ, > or DMA.... I've seen the same type of problem with my GUS-MAX when running s3mod. MODs *do* play, but I get tons of Jul 15 18:06:42 inertia /kernel: isa_dmastart: channel 1 busy Jul 15 18:06:45 inertia last message repeated 39 times which, right now, is just a minor annoyance to have fly by on the console. I see most of them occur when the sound samples are being written to the GUS' memory (512K on board). I've seen these errors for about a month now... from May 16th or so (the first occurance I have in my logs). 486/80 VLB, 8 megs, current as of Jun 26th. options "GUS_IRQ=11" #gus. device gus0 at isa? port 0x220 irq 11 drq 1 vector gusintr -- Mike 'axly' Harshbarger | OOPS! Adjustment fire, harsh882@uidaho.edu <*> | 1000 meters left!... axly@kuoi.asui.uidaho.edu | NO, NO, THE OTHER LEFT!!! http://www.cs.uidaho.edu/~harsh882/ | -- Forward Observer Axly From owner-freebsd-current Mon Jul 15 18:56:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA13184 for current-outgoing; Mon, 15 Jul 1996 18:56:48 -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 SAA13173 for ; Mon, 15 Jul 1996 18:56:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA28339; Tue, 16 Jul 1996 11:55:34 +1000 Date: Tue, 16 Jul 1996 11:55:34 +1000 From: Bruce Evans Message-Id: <199607160155.LAA28339@godzilla.zeta.org.au> To: bde@zeta.org.au, imp@village.org Subject: Re: Nits Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Cool. So setenv INSTALL "install -C" should do the trick for me >before I build, right? I should also be able to put this in >/etc/make.conf, if I read sys.mk correctly. >Without that hack, it took 1:11:35 to do a make all install. I'll >have to see what delta that has on the build time. It will probably take longer :-). The main benefits of not clobbering the timestamps are that you and dump(8) can tell what has really changed simply by looking at the timestamps. >Also, should I bother with make depend? It takes another hour on my >machine. It seems that there should be an easy way to tell if the Yes. It shouldn't take long to redo it, especially if you don't run `make depend' separately (`make depend all' sometimes uses out of date dependencies). >.depend file is out of date or not. Will have to think about this I don't think there is an easy way. To be complete, it is necessary to check the timestamps of all the source files, including all the headers referenced in .depend. `make depend' now only checks the timestamps of the primary sources. >because I want to use the feature, but not pay so high a price when 20 >files in the whole system have changed. Or does this fall into the >category of "always do a make depend, or we'll not help you if you get >an odd failure" category? Yes. Bruce From owner-freebsd-current Mon Jul 15 19:21:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA17046 for current-outgoing; Mon, 15 Jul 1996 19:21:04 -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 TAA17036 for ; Mon, 15 Jul 1996 19:21:02 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id TAA07190; Mon, 15 Jul 1996 19:21:31 -0700 Date: Mon, 15 Jul 1996 19:21:30 -0700 (PDT) From: Veggy Vinny To: current@FreeBSD.ORG Subject: /usr/bin/passwd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that the latest -current's /usr/bin/passwd will say: passwd: Permission denied if you run it from any user not in the wheel group, I have seen the same thing happen on 4 machines. Any ideas how to get passwd to work for users not in group wheel? Vince From owner-freebsd-current Mon Jul 15 19:28:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA18419 for current-outgoing; Mon, 15 Jul 1996 19:28:28 -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 TAA18402 for ; Mon, 15 Jul 1996 19:28:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id UAA11327; Mon, 15 Jul 1996 20:28:09 -0600 (MDT) Message-Id: <199607160228.UAA11327@rover.village.org> To: Bruce Evans Subject: Re: Nits Cc: current@freebsd.org In-reply-to: Your message of Tue, 16 Jul 1996 11:55:34 +1000 Date: Mon, 15 Jul 1996 20:28:08 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : Yes. It shouldn't take long to redo it, especially if you don't run : `make depend' separately (`make depend all' sometimes uses out of date : dependencies). Then shouldn't the make world target do 'make depend && make all install' rather than 'make depend all install'? Or is there a reason why make world doesn't that? Warner From owner-freebsd-current Mon Jul 15 19:31:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA18716 for current-outgoing; Mon, 15 Jul 1996 19:31:02 -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 TAA18709 for ; Mon, 15 Jul 1996 19:30:59 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id TAA08347; Mon, 15 Jul 1996 19:31:26 -0700 Date: Mon, 15 Jul 1996 19:31:24 -0700 (PDT) From: Veggy Vinny To: Mike Harshbarger cc: freebsd-current@freebsd.org Subject: Re: sound driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996, Mike Harshbarger wrote: > On Sun, 14 Jul 1996, Veggy Vinny wrote: > > > On Sun, 14 Jul 1996, Sujal Patel wrote: > > > > > On Sat, 13 Jul 1996, Veggy Vinny wrote: > > > > > > > gus0 at 0x220 irq 12 drq 1 on isa > > > > > > > > Jul 13 19:26:16 bigbang /kernel: GUS: DMA Transfer timed out > > > > Jul 13 19:26:16 bigbang /kernel: isa_dmastart: channel 1 busy > > > > > > Is your DRQ correct and not conflicting with another device? > > > > Yes, it is..... Because nothing else in my system has that DRQ, > > or DMA.... > > I've seen the same type of problem with my GUS-MAX when running s3mod. > MODs *do* play, but I get tons of > > Jul 15 18:06:42 inertia /kernel: isa_dmastart: channel 1 busy > Jul 15 18:06:45 inertia last message repeated 39 times > > which, right now, is just a minor annoyance to have fly by on the console. > I see most of them occur when the sound samples are being written to the > GUS' memory (512K on board). I've seen these errors for about a month > now... from May 16th or so (the first occurance I have in my logs). Hmmm, my GUSMax has 1 meg on board... It worked until I used the xcdplayer to play a CD through my NCR810 SCSI controller, then after that, even reboots doesn't allow the card to work under gusmod or playmidi... > 486/80 VLB, 8 megs, current as of Jun 26th. > > options "GUS_IRQ=11" #gus. > device gus0 at isa? port 0x220 irq 11 drq 1 vector gusintr Hmmmm, it seems like the kernel defaults to irq 12 it seems and it worked before... I think in DOS, my card is set to IRQ 11, DMA 5,6 and DMA Channels 1.... Where did you get the options line from? Vince From owner-freebsd-current Mon Jul 15 19:41:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA19796 for current-outgoing; Mon, 15 Jul 1996 19:41:02 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA19790; Mon, 15 Jul 1996 19:40:58 -0700 (PDT) Message-Id: <199607160240.TAA19790@freefall.freebsd.org> To: amurai@spec.co.jp cc: nao@sbl.cl.nec.co.jp, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) In-reply-to: Your message of "Tue, 16 Jul 1996 10:45:42 +0900." <31EAF446.2D93@spec.co.jp> Date: Mon, 15 Jul 1996 19:40:57 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Should I commit this to -current unless nobody has problem? Yes, please do. I though that the code already did this and it must simply be a difference between the 3c509 in EISA mode and the 3c579 that caused me to miss this. >Atsushi. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Jul 15 20:02:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA21809 for current-outgoing; Mon, 15 Jul 1996 20:02:01 -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 UAA21782 for ; Mon, 15 Jul 1996 20:01:53 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA30766; Tue, 16 Jul 1996 12:57:05 +1000 Date: Tue, 16 Jul 1996 12:57:05 +1000 From: Bruce Evans Message-Id: <199607160257.MAA30766@godzilla.zeta.org.au> To: bde@zeta.org.au, imp@village.org Subject: Re: Nits Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >: Yes. It shouldn't take long to redo it, especially if you don't run >: `make depend' separately (`make depend all' sometimes uses out of date >: dependencies). >Then shouldn't the make world target do 'make depend && make all >install' rather than 'make depend all install'? Or is there a reason >why make world doesn't that? It should do something like that if necessary. It usually isn't necessary because of an intended(?) side effect of the subdirectory handling: the `depend' target for each subdirectory gets done before any `all' targets, so the `all' targets for subdirectories get handled by different `make' processes, so there is no problem. However this is reported to not work in some cases. It certainly doesn't work if you cd to a leaf directory and run `make depend all install' there. Note that the subdirectory handling stops make `make depend all' from being an optimization for the same reason that it makes it work. Bruce From owner-freebsd-current Mon Jul 15 21:06:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA28592 for current-outgoing; Mon, 15 Jul 1996 21:06:30 -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 VAA28585; Mon, 15 Jul 1996 21:06:28 -0700 (PDT) Received: from fakir.india.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA152549954; Mon, 15 Jul 1996 21:06:03 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA224560056; Tue, 16 Jul 1996 09:37:36 +0530 Message-Id: <199607160407.AA224560056@fakir.india.hp.com> To: count@key.hole.fi Cc: davidg@freebsd.org, current@freebsd.org Subject: Re: FreeBSD with 100Mbit ethernet card? Date: Tue, 16 Jul 1996 09:37:35 +0530 From: A JOSEPH KOSHY Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> "c" == "Bror 'Count' Heinola" >>>> "dg" == "David Greenman" c> Well, when I transfer files from an Ultra 1 with fast ethernet I c> can 'put' them at over 5Mbytes/sec but when I 'get' them from c> the BSD box they don't come faster than about 1.5Mbytes/sec. On 2.1.0-RELEASE: I noticed this behaviour too when debugging my driver for the HP PC Lan Plus card. To cut a long story short, I took dumps of the TCP traffic while transferring a large (2MB) file between machines. m/c 1 <---------------------------> m/c 2 | | v m/c 3 To cross check I took simultaneous dump from a third machine. In summary, it seemed that when FreeBSD is the recipient, sometimes packets are received but acknowledgements aren't sent out i.e. they get `lost'. This causes a timeout and subsequent slow-start. This behaviour was noticed when there are lots of packets flowing in, but not when the FreeBSD box was the sender. I haven't found time to investigate further yet. Indeed I have to check if the latest -current has this behaviour. Koshy My Personal Opinions Only. From owner-freebsd-current Mon Jul 15 22:55:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08174 for current-outgoing; Mon, 15 Jul 1996 22:55:26 -0700 (PDT) Received: from afrodita.adam.es (root@afrodita.adam.es [194.133.59.16]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA08166 for ; Mon, 15 Jul 1996 22:55:22 -0700 (PDT) Received: from omnibook (pppAA.adam.es [194.133.59.74]) by afrodita.adam.es (8.6.12/8.6.9) with SMTP id IAA17390 for ; Tue, 16 Jul 1996 08:00:34 +0100 Message-Id: <199607160700.IAA17390@afrodita.adam.es> Comments: Authenticated sender is From: "Domingo Siliceo" To: freebsd-current@FreeBSD.org Date: Tue, 16 Jul 1996 07:55:03 +0200 Subject: Opinions? Priority: normal X-mailer: Pegasus Mail for Win32 (v2.41) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, first of all, if this is not the list for such a posting please get my apologies; second, it is not my intention to begin a SO war, I *only* want some opinions. I'm planning to switch one machine from NT to FreeBSD without any special reason. What I'd like to know is your opinions. Is it hard to configure a mode (US Robotics) under COM1 in order to connect with our ISP? How many HD will I need to install XWindow system? Best wishes Domingo Siliceo Telf.: 93/4201567 Barcelona From owner-freebsd-current Mon Jul 15 22:58:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08738 for current-outgoing; Mon, 15 Jul 1996 22:58:05 -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 WAA08713; Mon, 15 Jul 1996 22:57:57 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA22922; Mon, 15 Jul 1996 23:57:46 -0600 (MDT) Date: Mon, 15 Jul 1996 23:57:46 -0600 (MDT) Message-Id: <199607160557.XAA22922@rocky.mt.sri.com> From: Nate Williams To: freebsd-mobile@freebsd.org, current@freebsd.org CC: davidg@freebsd.org Subject: Cause of APM_DSVALUE_BUG found (but not completely fixed yet) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got some email from John Kohl from the NetBSD project, and during our discussions I mentioned that on the IBM ThinkPad's I needed a hack because the APM data segment was getting corrupted. He mentioned that this used to be a problem in NetBSD until recently when they changed the way they determine the base and extended memory sizes. Both FreeBSD and previously NetBSD use the BIOS values stored in the RTC CMOS RAM (instead of probing). This is normally a 'good thing, except that these values are apparently stored *before* such niceties as the APM BIOS have a whack at things. Apparently the APM bios 'steals' the last page of base-memory for itself, and then subtracts this from the BIOS's value of base memory. But, since this is called after the data is stored in RTC we have no way of finding out using the RTC interface. However, our bootblocks read the BIOS information after ever everything else has run, and they provide the (correct!) amount of base and extended memory to the kernel. Currently, the kernel prints out a warning message if the RTC value and the bootblock value doesn't match, but it still uses the RTC value. Now, if this space is taken up by DOS-like things we may as well re-take that space back, but in this case it's a bad thing since it doesn't allow us to use the APM bios w/out significant hacks (which also uses up an additional 42K of memory on my box). The following patch fixes the BIOS problem, but it brings up another problem that I don't yet have a 'acceptable' solution for. On bootup, all of the memory is mapped read-only, and then specific parts are mapped read/write/no-cacheable etc.. The 'normal' ISA memory hole starting at 640K and continuing for the next 384K is mapped differently. Then, in machdep.c, the 'basemem' is mapped into the kernel for general use (read/write, etc.) However, with the below patch, the kernel only maps the 'actual' basemem the BIOS reports into 'general' memory. This leaves the 'stolen' memory mapped read-only (the default unless specified otherwise) which doesn't work for a data-segment that gets written to. The NetBSD kernel has a function to map the page read/write, but their kernel is *vastly* different from ours. I'm in contact with some of the kernel gurus on how best to solve this, but I wanted to give everyone the heads up before I go on a mini-vacation, in case anyone gets a wild hair and decides to fix this the 'correct' way. In my opinion, the proper solution would be to either: a) Map the memory read-write in machdep.c when we determine that the BIOS reported by the RTC and the bootblocks doesn't match. OR b) Map the memory read-write in the APM driver. The former assumes that *something* will use it later on, and the latter implies that any driver which has a use for that memory will do it's own mapping, since the driver may not have to do any modification. I'm not sure which one I prefer, but given my lack of experience with the pmap() functions and no success with the couple of attempts I did today, I probably won't get the 'correct' solution done this week. Finally, the patch below hasn't been reviewed and may not go into the FreeBSD as it stands, but it is provided to show the bug and part of the solution. It has been tested and doesn't cause anything bad to happen though, so you should feel safe in applying it to a -current system. (It may also apply to 2.1.5, but I haven't checked). Nate -------- Index: machdep.c =================================================================== RCS file: /home/CVS/src/sys/i386/i386/machdep.c,v retrieving revision 1.194 diff -u -r1.194 machdep.c --- machdep.c 1996/07/08 19:44:39 1.194 +++ machdep.c 1996/07/11 19:19:07 @@ -1239,12 +1239,16 @@ * the official interface should be used. */ if (bootinfo.bi_memsizes_valid) { - if (bootinfo.bi_basemem != biosbasemem) + if (bootinfo.bi_basemem != biosbasemem) { printf("BIOS basemem (%ldK) != RTC basemem (%dK)\n", bootinfo.bi_basemem, biosbasemem); - if (bootinfo.bi_extmem != biosextmem) + biosbasemem = bootinfo.bi_basemem; + } + if (bootinfo.bi_extmem != biosextmem) { printf("BIOS extmem (%ldK) != RTC extmem (%dK)\n", bootinfo.bi_extmem, biosextmem); + biosextmem = bootinfo.bi_extmem; + } } /* From owner-freebsd-current Mon Jul 15 23:12:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10073 for current-outgoing; Mon, 15 Jul 1996 23:12:49 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10066 for ; Mon, 15 Jul 1996 23:12:47 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.5+2.6Wbeta6/950912) with ESMTP id PAA25532; Tue, 16 Jul 1996 15:12:39 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id PAA27715; Tue, 16 Jul 1996 15:12:37 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id PAA06367; Tue, 16 Jul 1996 15:12:35 +0900 (JST) Date: Tue, 16 Jul 1996 15:12:35 +0900 (JST) From: Naoki Hamada Message-Id: <199607160612.PAA06367@sirius.sbl.cl.nec.co.jp> References: <199607140346.MAA01006@tama.spec.co.jp> <31EAF446.2D93@spec.co.jp> To: amurai@spec.co.jp CC: gibbs@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org In-reply-to: Atsushi Murai's message of "Tue, 16 Jul 1996 10:45:42 +0900" <31EAF446.2D93@spec.co.jp> Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Atsushi wrote: >Should I commit this to -current unless nobody has problem? I made it more robust. Not enough test yet, but this should work. -nao diff -ur sys-960612/i386/eisa/3c5x9.c sys/i386/eisa/3c5x9.c --- sys-960612/i386/eisa/3c5x9.c Wed Jun 12 14:02:39 1996 +++ sys/i386/eisa/3c5x9.c Tue Jul 16 11:18:44 1996 @@ -293,6 +293,13 @@ 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; + i = inw(eisa_ioport->addr+ EP_W0_RESOURCE_CFG) & 0x0fff; + outw(eisa_ioport->addr+ EP_W0_RESOURCE_CFG, SET_IRQ(irq) | i); + ep_attach(sc); if(eisa_enable_intr(e_dev, irq)) { diff -ur sys-960612/i386/isa/if_ep.c sys/i386/isa/if_ep.c --- sys-960612/i386/isa/if_ep.c Wed Jun 12 14:03:38 1996 +++ sys/i386/isa/if_ep.c Tue Jul 16 11:20:30 1996 @@ -422,7 +422,7 @@ { struct ep_softc *sc = ep_softc[is->id_unit]; u_short config; - int irq; + int irq, i; sc->ep_connectors = 0; config = inw(IS_BASE + EP_W0_CONFIG_CTRL); @@ -451,7 +451,8 @@ GO_WINDOW(0); if(irq == 9) irq = 2; - outw(BASE + EP_W0_RESOURCE_CFG, SET_IRQ(irq)); + i = inw(BASE + EP_W0_RESOURCE_CFG) & 0x0fff; + outw(BASE + EP_W0_RESOURCE_CFG, SET_IRQ(irq) | i); ep_attach(sc); return 1; diff -ur sys-960612/i386/isa/if_epreg.h sys/i386/isa/if_epreg.h --- sys-960612/i386/isa/if_epreg.h Thu Feb 29 02:19:04 1996 +++ sys/i386/isa/if_epreg.h Tue Jul 16 11:20:45 1996 @@ -363,7 +363,7 @@ * */ -#define SET_IRQ(i) (((i)<<12) | 0xF00) /* set IRQ i */ +#define SET_IRQ(i) ((i)<<12) /* set IRQ i */ /* * FIFO Registers. From owner-freebsd-current Mon Jul 15 23:26:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA11446 for current-outgoing; Mon, 15 Jul 1996 23:26:30 -0700 (PDT) Received: from crow.csrv.uidaho.edu (root@crow.csrv.uidaho.edu [129.101.119.223]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA11439 for ; Mon, 15 Jul 1996 23:26:28 -0700 (PDT) Received: from goshawk.csrv.uidaho.edu (goshawk.csrv.uidaho.edu [129.101.119.224]) by crow.csrv.uidaho.edu (8.7.5/8.7.3) with ESMTP id XAA28986; Mon, 15 Jul 1996 23:26:24 -0700 (PDT) Received: from localhost (harsh882@localhost) by goshawk.csrv.uidaho.edu (8.7.5/8.7.3) with SMTP id XAA02214; Mon, 15 Jul 1996 23:26:23 -0700 (PDT) Date: Mon, 15 Jul 1996 23:26:22 -0700 (PDT) From: Mike Harshbarger X-Sender: harsh882@goshawk.csrv.uidaho.edu To: freebsd-current@freebsd.org cc: Veggy Vinny Subject: Re: sound driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996, Veggy Vinny wrote: > On Mon, 15 Jul 1996, Mike Harshbarger wrote: > > > options "GUS_IRQ=11" #gus. > > device gus0 at isa? port 0x220 irq 11 drq 1 vector gusintr > > Hmmmm, it seems like the kernel defaults to irq 12 it seems and > it worked before... I think in DOS, my card is set to IRQ 11, DMA 5,6 and > DMA Channels 1.... Where did you get the options line from? I don't remember when I set these up... probably when either 2.1-RELEASE came out or voxware was integrated. Anyway, looking though /usr/src/sys/i386/isa/sound/sound_config.h, I can see this: /* ****** IO-address, DMA and IRQ settings **** If your card has nonstandard I/O address or IRQ number, change defines for the following settings in your kernel Makefile */ [...] #ifndef GUS_IRQ #define GUS_IRQ 15 #endif So, I guess I had and did. Looking through this file, I see some other things we can tinker with. -- Mike 'axly' Harshbarger | OOPS! Adjustment fire, harsh882@uidaho.edu <*> | 1000 meters left!... axly@kuoi.asui.uidaho.edu | NO, NO, THE OTHER LEFT!!! http://www.cs.uidaho.edu/~harsh882/ | -- Forward Observer Axly From owner-freebsd-current Mon Jul 15 23:55:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14021 for current-outgoing; Mon, 15 Jul 1996 23:55:10 -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 XAA14016 for ; Mon, 15 Jul 1996 23:55:08 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id XAA29021; Mon, 15 Jul 1996 23:55:36 -0700 Date: Mon, 15 Jul 1996 23:55:34 -0700 (PDT) From: Veggy Vinny To: Mike Harshbarger cc: freebsd-current@freebsd.org Subject: Re: sound driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996, Mike Harshbarger wrote: > On Mon, 15 Jul 1996, Veggy Vinny wrote: > > > On Mon, 15 Jul 1996, Mike Harshbarger wrote: > > > > > options "GUS_IRQ=11" #gus. > > > device gus0 at isa? port 0x220 irq 11 drq 1 vector gusintr > > > > Hmmmm, it seems like the kernel defaults to irq 12 it seems and > > it worked before... I think in DOS, my card is set to IRQ 11, DMA 5,6 and > > DMA Channels 1.... Where did you get the options line from? > > I don't remember when I set these up... probably when either 2.1-RELEASE > came out or voxware was integrated. Anyway, looking though > /usr/src/sys/i386/isa/sound/sound_config.h, I can see this: > > /* ****** IO-address, DMA and IRQ settings **** > If your card has nonstandard I/O address or IRQ number, change defines > for the following settings in your kernel Makefile */ > > [...] > > #ifndef GUS_IRQ > #define GUS_IRQ 15 > #endif > > So, I guess I had and did. Looking through this file, I see some other > things we can tinker with. Hmmm, I think the GUS defaults to irq 11 even when you take it out of the box... Maybe the GUSMax just doesn't work too well with the Triton based P5-90's or something since it seems like a bus timing problem or the card has to be in a certain position in the slot for it to work since sometimes SBOS in DOS won't load and I had to slightly move the card before it will work... Vince From owner-freebsd-current Tue Jul 16 00:21:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA16214 for current-outgoing; Tue, 16 Jul 1996 00:21:34 -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 AAA16201 for ; Tue, 16 Jul 1996 00:21:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id AAA05093; Tue, 16 Jul 1996 00:21:28 -0700 (PDT) Message-Id: <199607160721.AAA05093@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Domingo Siliceo" cc: freebsd-current@FreeBSD.org Subject: Re: Opinions? In-reply-to: Your message of "Tue, 16 Jul 1996 07:55:03 +0200." <199607160700.IAA17390@afrodita.adam.es> From: David Greenman Reply-To: davidg@root.com Date: Tue, 16 Jul 1996 00:21:28 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >first of all, if this is not the list for such a posting please get >my apologies; second, it is not my intention to begin a SO war, I >*only* want some opinions. freebsd-questions is the correct list. >I'm planning to switch one machine from NT to FreeBSD without any >special reason. What I'd like to know is your opinions. Is it hard to >configure a mode (US Robotics) under COM1 in order to connect with >our ISP? How many HD will I need to install XWindow system? It's not difficult to set up. FreeBSD+X11 takes about 100MB, but you'll want more space for other freeware utilities and for your own files. I'd recommend about 200MB minimum. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Jul 16 02:09:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28036 for current-outgoing; Tue, 16 Jul 1996 02:09:33 -0700 (PDT) Received: from al.imforei.apana.org.au (root@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28029 for ; Tue, 16 Jul 1996 02:09:18 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.5/8.7.3) id SAA06126 for freebsd-current@freebsd.org; Tue, 16 Jul 1996 18:39:08 +0930 (CST) Date: Tue, 16 Jul 1996 18:39:08 +0930 (CST) From: Peter Childs Message-Id: <199607160909.SAA06126@al.imforei.apana.org.au> To: freebsd-current@freebsd.org Subject: Re: Opinions? X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : >our ISP? How many HD will I need to install XWindow system? : It's not difficult to set up. FreeBSD+X11 takes about 100MB, but you'll : want more space for other freeware utilities and for your own files. I'd : recommend about 200MB minimum. I'd recommend a good hard look at the Handbook, and some of the recommended books that accompany it. Putting a unix system on the internet without some understanding of the underlying concepts sets you up as easy prey. Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds The internet is full, please try again in half an hour... From owner-freebsd-current Tue Jul 16 02:55:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03089 for current-outgoing; Tue, 16 Jul 1996 02:55:41 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA03068; Tue, 16 Jul 1996 02:55:35 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id CAA20811 ; Tue, 16 Jul 1996 02:55:24 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA23561; Tue, 16 Jul 1996 11:52:39 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA16285; Tue, 16 Jul 1996 11:52:39 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA22837; Tue, 16 Jul 1996 10:39:47 +0200 (MET DST) From: J Wunsch Message-Id: <199607160839.KAA22837@uriah.heep.sax.de> Subject: Re: Cause of APM_DSVALUE_BUG found (but not completely fixed yet) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 16 Jul 1996 10:39:46 +0200 (MET DST) Cc: freebsd-mobile@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607160557.XAA22922@rocky.mt.sri.com> from Nate Williams at "Jul 15, 96 11:57:46 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > However, our bootblocks read the BIOS information after ever everything > else has run, and they provide the (correct!) amount of base and > extended memory to the kernel. Currently, the kernel prints out a > warning message if the RTC value and the bootblock value doesn't match, > but it still uses the RTC value. Alas, there are other system ``niceties'' that also subtract some amount from the BIOS basemem, like hard disk parameter tables for the custom-selectable hard disk type. (BIOS vendors should really use the BIOS stack for this, but only AMI seems to offer this as an option.) I'm not sure whether we are very interested in preserving this information. Anyway, i don't think the wasted at most one page would hurt very much. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 16 03:05:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA04299 for current-outgoing; Tue, 16 Jul 1996 03:05:07 -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 ESMTP id DAA04275 for ; Tue, 16 Jul 1996 03:05:03 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id LAA01117 for ; Tue, 16 Jul 1996 11:09:34 +0100 (BST) Date: Tue, 16 Jul 1996 11:09:32 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Nasty Bug in PPP :( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While using freebsd-current V2.2 I found a nasty bug:( If you do: ifconfig ppp0 mtu 576 The kernel crashes with a page fault:( Maybe it's just my kernel, can others try this one.. beware of long fsck sessions afterwards! Thanks for your help. Cheers, Trefor S. From owner-freebsd-current Tue Jul 16 08:20:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01877 for current-outgoing; Tue, 16 Jul 1996 08:20:00 -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 IAA01867; Tue, 16 Jul 1996 08:19:55 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA24381; Tue, 16 Jul 1996 09:19:07 -0600 (MDT) Date: Tue, 16 Jul 1996 09:19:07 -0600 (MDT) Message-Id: <199607161519.JAA24381@rocky.mt.sri.com> From: Nate Williams To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org (FreeBSD-current users), freebsd-mobile@freebsd.org Subject: Re: Cause of APM_DSVALUE_BUG found (but not completely fixed yet) In-Reply-To: <199607160839.KAA22837@uriah.heep.sax.de> References: <199607160557.XAA22922@rocky.mt.sri.com> <199607160839.KAA22837@uriah.heep.sax.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > However, our bootblocks read the BIOS information after ever everything > > else has run, and they provide the (correct!) amount of base and > > extended memory to the kernel. Currently, the kernel prints out a > > warning message if the RTC value and the bootblock value doesn't match, > > but it still uses the RTC value. > > Alas, there are other system ``niceties'' that also subtract some > amount from the BIOS basemem, like hard disk parameter tables for the > custom-selectable hard disk type. (BIOS vendors should really use the > BIOS stack for this, but only AMI seems to offer this as an option.) > I'm not sure whether we are very interested in preserving this > information. It certainly couldn't hurt to preserve this and... > Anyway, i don't think the wasted at most one page would hurt very > much. *grin* Nate From owner-freebsd-current Tue Jul 16 11:15:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19396 for current-outgoing; Tue, 16 Jul 1996 11:15:17 -0700 (PDT) Received: from neworder.cc.uky.edu (neworder.cc.uky.edu [128.163.18.198]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA19391 for ; Tue, 16 Jul 1996 11:15:12 -0700 (PDT) Received: (from soward@localhost) by neworder.cc.uky.edu (8.7/Soward0.1) id OAA04251 for freebsd-current@freebsd.org; Tue, 16 Jul 1996 14:15:13 -0500 (GMT-0500) Message-Id: <199607161915.OAA04251@neworder.cc.uky.edu> MIME-Version: 1.0 (NeXT Mail 4.0 v141) Content-Type: text/plain Received: by NeXT.Mailer (1.141) From: John Soward Date: Tue, 16 Jul 96 14:15:12 -0500 To: freebsd-current@freebsd.org Subject: ahc controller Reply-To: soward@service1.uky.edu Organization: University of Kentucky Technical Services X-URL: "http://neworder.cc.uky.edu/" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried to sup the current stuff and load it on an HP Pentium-Pro (XU 6/150). Things went mostly okay, until I made the kernel and rebooted... The kernel didn't seem to have the ahc driver for the 7880 controller (or the extra 2940 in a PCI slot). I was able to boot it with the old (2.2 current kernel (from about may)), but that's not really what I had in mind ;^> Anyone have an suggestions? thanx in advance, --- John Soward JpS Systems Programmer 'The Midnight sun will burn you up.' University of Kentucky (NeXT and MIME mail OK) -R. Smith :::I'm not speaking for UK. I may not even be speaking for myself::: From owner-freebsd-current Tue Jul 16 11:51:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22598 for current-outgoing; Tue, 16 Jul 1996 11:51:38 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA22591; Tue, 16 Jul 1996 11:51:37 -0700 (PDT) Message-Id: <199607161851.LAA22591@freefall.freebsd.org> To: soward@service1.uky.edu cc: freebsd-current@freebsd.org Subject: Re: ahc controller In-reply-to: Your message of "Tue, 16 Jul 1996 14:15:12 CDT." <199607161915.OAA04251@neworder.cc.uky.edu> Date: Tue, 16 Jul 1996 11:51:36 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Anyone have an suggestions? We'd need to see your kernel config file. >thanx in advance, >--- >John Soward JpS >Systems Programmer 'The Midnight sun will burn you up.' >University of Kentucky (NeXT and MIME mail OK) -R. Smith >:::I'm not speaking for UK. I may not even be speaking for myself::: -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Jul 16 11:51:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22646 for current-outgoing; Tue, 16 Jul 1996 11:51:53 -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 LAA22631 for ; Tue, 16 Jul 1996 11:51:50 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA12223; Tue, 16 Jul 1996 20:50:52 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA21947; Tue, 16 Jul 1996 20:50:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA24399; Tue, 16 Jul 1996 20:45:11 +0200 (MET DST) From: J Wunsch Message-Id: <199607161845.UAA24399@uriah.heep.sax.de> Subject: Re: Nasty Bug in PPP :( To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 16 Jul 1996 20:45:11 +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 16, 96 11:09:32 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: > The kernel crashes with a page fault:( > > Maybe it's just my kernel, can others try this one.. beware of long fsck > sessions afterwards! There's a simple recipe for it: compile your kernel with DDB, and reboot into single-user (with the disks read/only). Then, try the offending command and see whether it also crashes here. If so, your debugger has been called, and you can analyze the bug. (Or what do you think how others analyze the problems? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 16 12:27:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA28576 for current-outgoing; Tue, 16 Jul 1996 12:27:25 -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 MAA28570 for ; Tue, 16 Jul 1996 12:27:22 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA22321 (5.67b/IDA-1.5 for ); Tue, 16 Jul 1996 21:27:12 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00908; Tue, 16 Jul 1996 21:26:59 +0200 (MET DST) Date: Tue, 16 Jul 1996 21:26:59 +0200 (MET DST) Message-Id: <199607161926.VAA00908@x14.mi.uni-koeln.de> From: Stefan Esser To: soward@service1.uky.edu Cc: freebsd-current@freebsd.org Subject: ahc controller In-Reply-To: <199607161915.OAA04251@neworder.cc.uky.edu> References: <199607161915.OAA04251@neworder.cc.uky.edu> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Soward writes: > > I tried to sup the current stuff and load it on an HP Pentium-Pro (XU 6/150). > Things went mostly okay, until I made the kernel and rebooted... The kernel > didn't seem to have the ahc driver for the 7880 controller (or the extra 2940 > in a PCI slot). I was able to boot it with the old (2.2 current kernel (from > about may)), but that's not really what I had in mind ;^> > > Anyone have an suggestions? What chip set is being used in that PPro machine ? Did the current kernel see ANY PCI devices at all ? Please boot with "-v" and send me all numbers on lines that start with pcibus_setup or pcibus_check. Regards, STefan PS: I'd really like to have a VERBOSE boot message log from the working kernel, too ... From owner-freebsd-current Tue Jul 16 12:55:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05475 for current-outgoing; Tue, 16 Jul 1996 12:55:41 -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 MAA05429 for ; Tue, 16 Jul 1996 12:55:26 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA22390 (5.67b/IDA-1.5 for ); Tue, 16 Jul 1996 21:55:14 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00934; Tue, 16 Jul 1996 21:55:11 +0200 (MET DST) Date: Tue, 16 Jul 1996 21:55:11 +0200 (MET DST) Message-Id: <199607161955.VAA00934@x14.mi.uni-koeln.de> From: Stefan Esser To: current@freebsd.org Subject: Lance PCI driver (please test) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I've finished my patches to the FreeBSD Lance driver (lnc) some time ago, but it seems I have no way of verifying that they do not break support of the non-PCI cards, nor that they do indeed work with the PCI versions ... (since I don't have access to any Lance controller at all) I sent the diffs to Paul Richards (the author of the lnc driver) for review, but he couldn't test them on a -current system. (They are not compatible with -stable, since some kernel conventions changed and the code requires the new interface. If the driver works under -current and there is sufficient interest, then I'll finish the nearly complete back-port to -stable.) Paul Richards gave me permission to check them in, if they seem to work on other people's systems. Now, I'm asking you all, who are running FreeBSD-current and who use the lnc driver, to let me know if it breaks on your system. Please give it a try, whether you have the ISA or or PCI version, since I'll commit the changes after waiting a few more days, if I do not get a single negative reply within that time! If you are the owner of a PCI Lance: The PCI card will be detected as "lnc1" (if all goes well :), since "lnc0" is reserved for the ISA version, and the ISA probe occurs after the PCI probe. Please give these patches a try! Regards, STefan Index: /sys/conf/files =================================================================== RCS file: /usr/cvs/src/sys/conf/files,v retrieving revision 1.71 diff -C2 -r1.71 files *** files 1996/06/18 05:19:45 1.71 --- files 1996/07/01 11:23:57 *************** *** 297,300 **** --- 297,301 ---- pci/if_ed_p.c optional ed device-driver pci/if_fxp.c optional fxp device-driver + pci/if_lnc_p.c optional lnc device-driver pci/if_vx.c optional vx device-driver pci/ncr.c optional ncr device-driver Index: /sys/i386/isa/if_lnc.c =================================================================== RCS file: /usr/cvs/src/sys/i386/isa/if_lnc.c,v retrieving revision 1.23 diff -C2 -r1.23 if_lnc.c *** if_lnc.c 1996/06/25 20:30:25 1.23 --- if_lnc.c 1996/07/01 12:27:10 *************** *** 61,64 **** --- 61,65 ---- */ + #include "pci.h" #include "lnc.h" #if NLNC > 0 *************** *** 132,143 **** static void lnc_setladrf __P((struct lnc_softc *sc)); #endif ! static void lnc_stop __P((int unit)); ! static void lnc_reset __P((int unit)); static void lnc_free_mbufs __P((struct lnc_softc *sc)); static int alloc_mbuf_cluster __P((struct lnc_softc *sc, struct host_ring_entry *desc)); static struct mbuf *chain_mbufs __P((struct lnc_softc *sc, int start_of_packet, int pkt_len)); static struct mbuf *mbuf_packet __P((struct lnc_softc *sc, int start_of_packet, int pkt_len)); ! static void lnc_rint __P((int unit)); ! static void lnc_tint __P((int unit)); static int lnc_probe __P((struct isa_device *isa_dev)); static int ne2100_probe __P((struct isa_device *isa_dev)); --- 133,144 ---- static void lnc_setladrf __P((struct lnc_softc *sc)); #endif ! static void lnc_stop __P((struct lnc_softc *sc)); ! static void lnc_reset __P((struct lnc_softc *sc)); static void lnc_free_mbufs __P((struct lnc_softc *sc)); static int alloc_mbuf_cluster __P((struct lnc_softc *sc, struct host_ring_entry *desc)); static struct mbuf *chain_mbufs __P((struct lnc_softc *sc, int start_of_packet, int pkt_len)); static struct mbuf *mbuf_packet __P((struct lnc_softc *sc, int start_of_packet, int pkt_len)); ! static void lnc_rint __P((struct lnc_softc *sc)); ! static void lnc_tint __P((struct lnc_softc *sc)); static int lnc_probe __P((struct isa_device *isa_dev)); static int ne2100_probe __P((struct isa_device *isa_dev)); *************** *** 147,152 **** static int lance_probe __P((int unit)); static int pcnet_probe __P((int unit)); ! static int lnc_attach __P((struct isa_device *isa_dev)); ! static void lnc_init __P((int unit)); static int mbuf_to_buffer __P((struct mbuf *m, char *buffer)); static struct mbuf *chain_to_cluster __P((struct mbuf *m)); --- 148,154 ---- static int lance_probe __P((int unit)); static int pcnet_probe __P((int unit)); ! static int lnc_attach __P((struct lnc_softc *sc, int unit)); ! static int lnc_attach_isa __P((struct isa_device *isa_dev)); ! static void lnc_init __P((struct lnc_softc *sc)); static int mbuf_to_buffer __P((struct mbuf *m, char *buffer)); static struct mbuf *chain_to_cluster __P((struct mbuf *m)); *************** *** 155,163 **** static void lnc_watchdog __P((struct ifnet *ifp)); #ifdef DEBUG ! static void lnc_dump_state __P((int unit)); static void mbuf_dump_chain __P((struct mbuf *m)); #endif ! struct isa_driver lncdriver = {lnc_probe, lnc_attach, "lnc"}; static struct kern_devconf kdc_lnc = { --- 157,170 ---- static void lnc_watchdog __P((struct ifnet *ifp)); #ifdef DEBUG ! static void lnc_dump_state __P((struct lnc_softc *sc)); static void mbuf_dump_chain __P((struct mbuf *m)); #endif ! #if NPCI > 0 ! void *lnc_attach_ne2100_pci __P((int unit, unsigned iobase)); ! #endif ! void lncintr_sc __P((struct lnc_softc *sc)); ! ! struct isa_driver lncdriver = {lnc_probe, lnc_attach_isa, "lnc"}; static struct kern_devconf kdc_lnc = { *************** *** 173,187 **** static inline void ! write_csr(int unit, u_short port, u_short val) { ! outw(lnc_softc[unit].rap, port); ! outw(lnc_softc[unit].rdp, val); } static inline u_short ! read_csr(int unit, u_short port) { ! outw(lnc_softc[unit].rap, port); ! return (inw(lnc_softc[unit].rdp)); } --- 180,194 ---- static inline void ! write_csr(struct lnc_softc *sc, u_short port, u_short val) { ! outw(sc->rap, port); ! outw(sc->rdp, val); } static inline u_short ! read_csr(struct lnc_softc *sc, u_short port) { ! outw(sc->rap, port); ! return (inw(sc->rdp)); } *************** *** 222,225 **** --- 229,235 ---- break; case PCnet_PCI: + /* + * XXX - This should never be the case ... + */ kdc->kdc_description = "PCnet-PCI Ethernet controller"; break; *************** *** 306,318 **** static void ! lnc_stop(int unit) { ! write_csr(unit, CSR0, STOP); } static void ! lnc_reset(int unit) { ! lnc_init(unit); } --- 316,328 ---- static void ! lnc_stop(struct lnc_softc *sc) { ! write_csr(sc, CSR0, STOP); } static void ! lnc_reset(struct lnc_softc *sc) { ! lnc_init(sc); } *************** *** 482,488 **** static inline void ! lnc_rint(int unit) { ! register struct lnc_softc *sc = &lnc_softc[unit]; struct host_ring_entry *next, *start; int start_of_packet; --- 492,498 ---- static inline void ! lnc_rint(struct lnc_softc *sc) { ! int unit = sc->arpcom.ac_if.if_unit; struct host_ring_entry *next, *start; int start_of_packet; *************** *** 541,545 **** if (flags & STP) { log(LOG_ERR, "lnc%d: Start of packet found before end of previous in receive ring -- Resetting\n", unit); ! lnc_reset(unit); return; } --- 551,555 ---- if (flags & STP) { log(LOG_ERR, "lnc%d: Start of packet found before end of previous in receive ring -- Resetting\n", unit); ! lnc_reset(sc); return; } *************** *** 554,558 **** } else { log(LOG_ERR, "lnc%d: End of received packet not found-- Resetting\n", unit); ! lnc_reset(unit); return; } --- 564,568 ---- } else { log(LOG_ERR, "lnc%d: End of received packet not found-- Resetting\n", unit); ! lnc_reset(sc); return; } *************** *** 672,678 **** static inline void ! lnc_tint(int unit) { ! register struct lnc_softc *sc = &lnc_softc[unit]; struct host_ring_entry *next, *start; int start_of_packet; --- 682,688 ---- static inline void ! lnc_tint(struct lnc_softc *sc) { ! int unit = sc->arpcom.ac_if.if_unit; struct host_ring_entry *next, *start; int start_of_packet; *************** *** 743,747 **** if (next->md->md1 & STP) { log(LOG_ERR, "lnc%d: Start of packet found before end of previous in transmit ring -- Resetting\n", unit); ! lnc_reset(unit); return; } --- 753,757 ---- if (next->md->md1 & STP) { log(LOG_ERR, "lnc%d: Start of packet found before end of previous in transmit ring -- Resetting\n", unit); ! lnc_reset(sc); return; } *************** *** 756,760 **** } else { log(LOG_ERR, "lnc%d: End of transmitted packet not found -- Resetting\n", unit); ! lnc_reset(unit); return; } --- 766,770 ---- } else { log(LOG_ERR, "lnc%d: End of transmitted packet not found -- Resetting\n", unit); ! lnc_reset(sc); return; } *************** *** 815,819 **** } else log(LOG_ERR, "lnc%d: Transmit underflow error -- Resetting\n", unit); ! lnc_reset(unit); return; } --- 825,829 ---- } else log(LOG_ERR, "lnc%d: Transmit underflow error -- Resetting\n", unit); ! lnc_reset(sc); return; } *************** *** 1058,1064 **** lance_probe(int unit) { ! write_csr(unit, CSR0, STOP); ! if ((inw(lnc_softc[unit].rdp) & STOP) && !(read_csr(unit, CSR3))) { /* * Check to see if it's a C-LANCE. For the LANCE the INEA bit --- 1068,1076 ---- lance_probe(int unit) { ! struct lnc_softc *sc = &lnc_softc[unit]; ! ! write_csr(sc, CSR0, STOP); ! if ((inw(sc->rdp) & STOP) && !(read_csr(sc, CSR3))) { /* * Check to see if it's a C-LANCE. For the LANCE the INEA bit *************** *** 1066,1071 **** * removed for the C-LANCE. */ ! write_csr(unit, CSR0, INEA); ! if (read_csr(unit, CSR0) & INEA) return (C_LANCE); else --- 1078,1083 ---- * removed for the C-LANCE. */ ! write_csr(sc, CSR0, INEA); ! if (read_csr(sc, CSR0) & INEA) return (C_LANCE); else *************** *** 1078,1081 **** --- 1090,1095 ---- pcnet_probe(int unit) { + struct lnc_softc *sc = &lnc_softc[unit]; + u_long chip_id; int type; *************** *** 1089,1095 **** if (type = lance_probe(unit)) { ! chip_id = read_csr(unit, CSR89); chip_id <<= 16; ! chip_id |= read_csr(unit, CSR88); if (chip_id & AMD_MASK) { chip_id >>= 12; --- 1103,1109 ---- if (type = lance_probe(unit)) { ! chip_id = read_csr(sc, CSR89); chip_id <<= 16; ! chip_id |= read_csr(sc, CSR88); if (chip_id & AMD_MASK) { chip_id >>= 12; *************** *** 1102,1106 **** return (PCnet_32); case Am79C970: ! return (PCnet_PCI); default: break; --- 1116,1120 ---- return (PCnet_32); case Am79C970: ! return (0); default: break; *************** *** 1112,1118 **** static int ! lnc_attach(struct isa_device * isa_dev) { - struct lnc_softc *sc = &lnc_softc[isa_dev->id_unit]; int lnc_mem_size; --- 1126,1131 ---- static int ! lnc_attach(struct lnc_softc *sc, int unit) { int lnc_mem_size; *************** *** 1145,1162 **** if (!sc->recv_ring) { ! log(LOG_ERR, "lnc%d: Couldn't allocate memory for NIC\n", isa_dev->id_unit); return (0); /* XXX -- attach failed -- not tested in * calling routines */ } if ((sc->nic.mem_mode != SHMEM) && (kvtop(sc->recv_ring) > 0x1000000)) { ! log(LOG_ERR, "lnc%d: Memory allocated above 16Mb limit\n", isa_dev->id_unit); ! return (0); } - if ((sc->nic.mem_mode != SHMEM) && - (sc->nic.ic != PCnet_32) && - (sc->nic.ic != PCnet_PCI)) - isa_dmacascade(isa_dev->id_drq); - /* Set default mode */ sc->nic.mode = NORMAL; --- 1158,1175 ---- if (!sc->recv_ring) { ! log(LOG_ERR, "lnc%d: Couldn't allocate memory for NIC\n", unit); return (0); /* XXX -- attach failed -- not tested in * calling routines */ } + /* + * XXX - Shouldn't this be skipped for the EISA and PCI versions ??? + * Print the message but do not return for the PCnet_PCI ! + */ if ((sc->nic.mem_mode != SHMEM) && (kvtop(sc->recv_ring) > 0x1000000)) { ! log(LOG_ERR, "lnc%d: Memory allocated above 16Mb limit\n", unit); ! if (sc->nic.ic != PCnet_PCI) ! return (0); } /* Set default mode */ sc->nic.mode = NORMAL; *************** *** 1166,1170 **** sc->arpcom.ac_if.if_softc = sc; sc->arpcom.ac_if.if_name = lncdriver.name; ! sc->arpcom.ac_if.if_unit = isa_dev->id_unit; sc->arpcom.ac_if.if_mtu = ETHERMTU; sc->arpcom.ac_if.if_flags = IFF_BROADCAST | IFF_SIMPLEX; --- 1179,1183 ---- sc->arpcom.ac_if.if_softc = sc; sc->arpcom.ac_if.if_name = lncdriver.name; ! sc->arpcom.ac_if.if_unit = unit; sc->arpcom.ac_if.if_mtu = ETHERMTU; sc->arpcom.ac_if.if_flags = IFF_BROADCAST | IFF_SIMPLEX; *************** *** 1186,1192 **** sc->kdc.kdc_state = DC_IDLE; printf("lnc%d: %s, address %6D\n", ! isa_dev->id_unit, ! sc->kdc.kdc_description, sc->arpcom.ac_enaddr, ":"); --- 1199,1208 ---- sc->kdc.kdc_state = DC_IDLE; + if (sc->kdc.kdc_description == NULL) + sc->kdc.kdc_description = "Lance Ethernet controller"; + printf("lnc%d: %s, address %6D\n", ! unit, ! sc->kdc.kdc_description, sc->arpcom.ac_enaddr, ":"); *************** *** 1198,1205 **** } ! static void ! lnc_init(int unit) { struct lnc_softc *sc = &lnc_softc[unit]; int s, i; char *lnc_mem; --- 1214,1281 ---- } ! static int ! lnc_attach_isa(struct isa_device * isa_dev) { + int unit = isa_dev->id_unit; struct lnc_softc *sc = &lnc_softc[unit]; + + int result = lnc_attach (sc, unit); + if (result == 0) + return (0); + /* + * XXX - is it safe to call isa_dmacascade() after if_attach() + * and ether_ifattach() have been called in lnc_attach() ??? + */ + if ((sc->nic.mem_mode != SHMEM) && + (sc->nic.ic != PCnet_32) && + (sc->nic.ic != PCnet_PCI)) + isa_dmacascade(isa_dev->id_drq); + + return result; + } + + #if NPCI > 0 + void * + lnc_attach_ne2100_pci(int unit, unsigned iobase) + { + struct lnc_softc *sc = malloc(sizeof *sc, M_DEVBUF, M_NOWAIT); + + if (!sc) + return sc; + + bzero (sc, sizeof *sc); + + /* + * Copied from ne2100_probe() + */ + sc->rap = iobase + PCNET_RAP; + sc->rdp = iobase + PCNET_RDP; + + sc->nic.ic = PCnet_PCI; + sc->nic.ident = NE2100; + sc->nic.mem_mode = DMA_FIXED; + + /* XXX - For now just use the defines */ + sc->nrdre = NRDRE; + sc->ntdre = NTDRE; + + /* Extract MAC address from PROM */ + { + int i; + for (i = 0; i < ETHER_ADDR_LEN; i++) + sc->arpcom.ac_enaddr[i] = inb(iobase + i); + } + + if (lnc_attach(sc, unit) == 0) { + free(sc, M_DEVBUF); + return NULL; + } + return sc; + } + #endif + + static void + lnc_init(struct lnc_softc *sc) + { int s, i; char *lnc_mem; *************** *** 1213,1217 **** s = splimp(); ! lnc_stop(unit); sc->arpcom.ac_if.if_flags |= IFF_BROADCAST | IFF_SIMPLEX; /* XXX??? */ --- 1289,1293 ---- s = splimp(); ! lnc_stop(sc); sc->arpcom.ac_if.if_flags |= IFF_BROADCAST | IFF_SIMPLEX; /* XXX??? */ *************** *** 1327,1332 **** /* Give the LANCE the physical address of the initialisation block */ ! write_csr(unit, CSR1, kvtop(sc->init_block)); ! write_csr(unit, CSR2, (kvtop(sc->init_block) >> 16) & 0xff); /* --- 1403,1408 ---- /* Give the LANCE the physical address of the initialisation block */ ! write_csr(sc, CSR1, kvtop(sc->init_block)); ! write_csr(sc, CSR2, (kvtop(sc->init_block) >> 16) & 0xff); /* *************** *** 1338,1348 **** */ ! write_csr(unit, CSR3, 0); /* Let's see if it starts */ ! write_csr(unit, CSR0, INIT); for (i = 0; i < 1000; i++) ! if (read_csr(unit, CSR0) & IDON) break; --- 1414,1424 ---- */ ! write_csr(sc, CSR3, 0); /* Let's see if it starts */ ! write_csr(sc, CSR0, INIT); for (i = 0; i < 1000; i++) ! if (read_csr(sc, CSR0) & IDON) break; *************** *** 1354,1368 **** */ ! if (read_csr(unit, CSR0) & IDON) { /* * Enable interrupts, start the LANCE, mark the interface as * running and transmit any pending packets. */ ! write_csr(unit, CSR0, STRT | INEA); sc->arpcom.ac_if.if_flags |= IFF_RUNNING; sc->arpcom.ac_if.if_flags &= ~IFF_OACTIVE; lnc_start(&sc->arpcom.ac_if); } else ! log(LOG_ERR, "lnc%d: Initialisation failed\n", unit); splx(s); --- 1430,1445 ---- */ ! if (read_csr(sc, CSR0) & IDON) { /* * Enable interrupts, start the LANCE, mark the interface as * running and transmit any pending packets. */ ! write_csr(sc, CSR0, STRT | INEA); sc->arpcom.ac_if.if_flags |= IFF_RUNNING; sc->arpcom.ac_if.if_flags &= ~IFF_OACTIVE; lnc_start(&sc->arpcom.ac_if); } else ! log(LOG_ERR, "lnc%d: Initialisation failed\n", ! sc->arpcom.ac_if.if_unit); splx(s); *************** *** 1391,1397 **** void ! lncintr(int unit) { ! struct lnc_softc *sc = &lnc_softc[unit]; u_short csr0; --- 1468,1474 ---- void ! lncintr_sc(struct lnc_softc *sc) { ! int unit = sc->arpcom.ac_if.if_unit; u_short csr0; *************** *** 1433,1437 **** log(LOG_ERR, "lnc%d: Memory error -- Resetting\n", unit); LNCSTATS(merr) ! lnc_reset(unit); continue; } --- 1510,1514 ---- log(LOG_ERR, "lnc%d: Memory error -- Resetting\n", unit); LNCSTATS(merr) ! lnc_reset(sc); continue; } *************** *** 1439,1448 **** if (csr0 & RINT) { LNCSTATS(rint) ! lnc_rint(unit); } if (csr0 & TINT) { LNCSTATS(tint) sc->arpcom.ac_if.if_timer = 0; ! lnc_tint(unit); } --- 1516,1525 ---- if (csr0 & RINT) { LNCSTATS(rint) ! lnc_rint(sc); } if (csr0 & TINT) { LNCSTATS(tint) sc->arpcom.ac_if.if_timer = 0; ! lnc_tint(sc); } *************** *** 1457,1460 **** --- 1534,1544 ---- } + void + lncintr(int unit) + { + struct lnc_softc *sc = &lnc_softc[unit]; + lncintr_sc (sc); + } + *************** *** 1543,1547 **** if (!(head = chain_to_cluster(head))) { log(LOG_ERR, "lnc%d: Couldn't get mbuf for transmit packet -- Resetting \n ",ifp->if_unit); ! lnc_reset(ifp->if_unit); return; } --- 1627,1631 ---- if (!(head = chain_to_cluster(head))) { log(LOG_ERR, "lnc%d: Couldn't get mbuf for transmit packet -- Resetting \n ",ifp->if_unit); ! lnc_reset(sc); return; } *************** *** 1677,1686 **** #ifdef INET case AF_INET: ! lnc_init(ifp->if_unit); arp_ifinit((struct arpcom *)ifp, ifa); break; #endif default: ! lnc_init(ifp->if_unit); break; } --- 1761,1770 ---- #ifdef INET case AF_INET: ! lnc_init(sc); arp_ifinit((struct arpcom *)ifp, ifa); break; #endif default: ! lnc_init(sc); break; } *************** *** 1697,1705 **** if (!(sc->nic.mode & PROM)) { sc->nic.mode |= PROM; ! lnc_init(ifp->if_unit); } } else if (sc->nic.mode & PROM) { sc->nic.mode &= ~PROM; ! lnc_init(ifp->if_unit); } if ((ifp->if_flags & IFF_UP) == 0 && --- 1781,1789 ---- if (!(sc->nic.mode & PROM)) { sc->nic.mode |= PROM; ! lnc_init(sc); } } else if (sc->nic.mode & PROM) { sc->nic.mode &= ~PROM; ! lnc_init(sc); } if ((ifp->if_flags & IFF_UP) == 0 && *************** *** 1709,1713 **** * then stop it. */ ! lnc_stop(ifp->if_unit); ifp->if_flags &= ~IFF_RUNNING; } else if ((ifp->if_flags & IFF_UP) != 0 && --- 1793,1797 ---- * then stop it. */ ! lnc_stop(sc); ifp->if_flags &= ~IFF_RUNNING; } else if ((ifp->if_flags & IFF_UP) != 0 && *************** *** 1717,1721 **** * start it. */ ! lnc_init(ifp->if_unit); } sc->kdc.kdc_state = --- 1801,1805 ---- * start it. */ ! lnc_init(sc); } sc->kdc.kdc_state = *************** *** 1757,1768 **** log(LOG_ERR, "lnc%d: Device timeout -- Resetting\n", ifp->if_unit); ifp->if_oerrors++; ! lnc_reset(ifp->if_unit); } #ifdef DEBUG static void ! lnc_dump_state(int unit) { - struct lnc_softc *sc = &lnc_softc[unit]; int i; --- 1841,1851 ---- log(LOG_ERR, "lnc%d: Device timeout -- Resetting\n", ifp->if_unit); ifp->if_oerrors++; ! lnc_reset(ifp->if_softc); } #ifdef DEBUG static void ! lnc_dump_state( struct lnc_softc *sc) { int i; *** /dev/null Sat Jun 29 02:05:26 1996 --- /sys/pci/if_lnc_p.c Mon Jul 1 13:31:53 1996 *************** *** 0 **** --- 1,97 ---- + /* + * + * Copyright (c) 1996 Stefan Esser + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice immediately at the beginning of the file, without modification, + * this list of conditions, and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Absolutely no warranty of function or purpose is made by the author + * Stefan Esser. + * 4. Modifications may be freely made to this file if the above conditions + * are met. + * + * $Id:$ + */ + + #include "pci.h" + #if NPCI > 0 + + #include + #include + #include + #include + #include + #include + #ifdef PC98 + #include + #else + #include + #endif + + #include "lnc.h" + + #define PCI_DEVICE_ID_PCNet_PCI 0x20001022 + + extern void *lnc_attach_ne2100_pci __P((int unit, unsigned iobase)); + + static char* lnc_pci_probe __P((pcici_t tag, pcidi_t type)); + static void lnc_pci_attach __P((pcici_t config_id, int unit)); + + static u_long lnc_pci_count = NLNC; + + static struct pci_device lnc_pci_driver = { + "lnc", + lnc_pci_probe, + lnc_pci_attach, + &lnc_pci_count, + NULL + }; + + DATA_SET (pcidevice_set, lnc_pci_driver); + + static char* + lnc_pci_probe (pcici_t tag, pcidi_t type) + { + switch(type) { + case PCI_DEVICE_ID_PCNet_PCI: + return ("PCNet/PCI Ethernet adapter"); + break; + default: + break; + } + return (0); + } + + void lncintr_sc (void*); + + static void + lnc_pci_attach(config_id, unit) + pcici_t config_id; + int unit; + { + unsigned iobase; + void *lnc; /* device specific data for interrupt handler ... */ + + iobase = pci_conf_read(config_id, PCI_MAP_REG_START) & ~PCI_MAP_IO; + + lnc = lnc_attach_ne2100_pci(unit, iobase); + if (!lnc) + return; + + if(!(pci_map_int(config_id, lncintr_sc, (void *)lnc, &net_imask))) { + free (lnc, M_DEVBUF); + return; + } + + return; + } + + #endif /* NPCI > 0 */ + From owner-freebsd-current Tue Jul 16 15:26:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01786 for current-outgoing; Tue, 16 Jul 1996 15:26:46 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA01778 for ; Tue, 16 Jul 1996 15:26:42 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail-queue invoked from smtpd); 16 Jul 1996 22:26:14 +0000 (GMT) Received: from localhost (HELO verdi.nethelp.no) (@127.0.0.1) by localhost with SMTP; 16 Jul 1996 22:26:14 +0000 (GMT) To: current@freebsd.org Subject: panic when ls /kern without KERNFS X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 17 Jul 1996 00:26:14 +0200 Message-ID: <6182.837555974@verdi.nethelp.no> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is this a known bug? # mount_kernfs /kern /kern # ls /kern when the kernel in question is compiled *without* the KERNFS option. It's quite reproducible. This is with 2.2-960612-SNAP on AMD 5x86-133, ASUS PVI-486SP3 board. With KERNFS, everything works just fine. I certainly agree that one shouldn't do mount_kernfs without KERNFS in the kernel - but I'd expect an error message from mount_kernfs, not a panic from the following ls. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Tue Jul 16 17:40:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24679 for current-outgoing; Tue, 16 Jul 1996 17:40:06 -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 RAA24658 for ; Tue, 16 Jul 1996 17:40:02 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id KAA16445; Wed, 17 Jul 1996 10:32:33 +1000 Date: Wed, 17 Jul 1996 10:32:33 +1000 From: Bruce Evans Message-Id: <199607170032.KAA16445@godzilla.zeta.org.au> To: dev@fgate.flevel.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: Nasty Bug in PPP :( Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >While using freebsd-current V2.2 I found a nasty bug:( >If you do: ifconfig ppp0 mtu 576 >The kernel crashes with a page fault:( It calls a null function pointer (sc->sc_setmtu) if the PPP line discipline has never been opened and uses a deallocated softc if the PPP line discipline isn't open. Another bug suite: ddb crashes early in the stack trace so the stack trace gives no useful information; calling printf for trap messages may destroy reentrancy. ddb crashes late for `show registers' while attempting to disassemble the instruction at address 0 and the trap message scrolls some of the registers off the screen; scrollback doesn't work while ddb is running. Bruce From owner-freebsd-current Tue Jul 16 18:14:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28585 for current-outgoing; Tue, 16 Jul 1996 18:14:55 -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 SAA28572 for ; Tue, 16 Jul 1996 18:14:52 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA18225; Wed, 17 Jul 1996 11:12:19 +1000 Date: Wed, 17 Jul 1996 11:12:19 +1000 From: Bruce Evans Message-Id: <199607170112.LAA18225@godzilla.zeta.org.au> To: current@freebsd.org, sthaug@nethelp.no Subject: Re: panic when ls /kern without KERNFS Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ># mount_kernfs /kern /kern ># ls /kern > >when the kernel in question is compiled *without* the KERNFS option. >It's quite reproducible. This is with 2.2-960612-SNAP on AMD 5x86-133, >ASUS PVI-486SP3 board. There was a fix on 1996/07/02 for ls -l panicing, but plain ls still panics here with yesterday's kernel. >I certainly agree that one shouldn't do mount_kernfs without KERNFS >in the kernel - but I'd expect an error message from mount_kernfs, not >a panic from the following ls. No, it should work. kernfs is an lkm. Bruce From owner-freebsd-current Tue Jul 16 18:24:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29424 for current-outgoing; Tue, 16 Jul 1996 18:24:42 -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 SAA29419 for ; Tue, 16 Jul 1996 18:24:39 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA18615; Wed, 17 Jul 1996 11:19:38 +1000 Date: Wed, 17 Jul 1996 11:19:38 +1000 From: Bruce Evans Message-Id: <199607170119.LAA18615@godzilla.zeta.org.au> To: current@freebsd.org, sthaug@nethelp.no Subject: Re: panic when ls /kern without KERNFS Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ># mount_kernfs /kern /kern ># ls /kern > >when the kernel in question is compiled *without* the KERNFS option. >It's quite reproducible. This is with 2.2-960612-SNAP on AMD 5x86-133, >ASUS PVI-486SP3 board. Oops. I said that it is still broken. It works better with a version of lkm/kernfs_mod.o that has the fix in it :-). Bruce From owner-freebsd-current Tue Jul 16 18:31:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29996 for current-outgoing; Tue, 16 Jul 1996 18:31:00 -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 SAA29987 for ; Tue, 16 Jul 1996 18:30:57 -0700 (PDT) Received: from tama3.spec.co.jp ([202.32.13.219]) by specgw.spec.co.jp (8.7.5/3.3Wb-SPEC) with SMTP id KAA23270; Wed, 17 Jul 1996 10:30:25 +0900 (JST) From: Atsushi MURAI Message-Id: <9607170133.AA00383@tama3.spec.co.jp.spec.co.jp> Date: Wed, 17 Jul 1996 10:33:43 +0900 To: nao@sbl.cl.nec.co.jp Cc: gibbs@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) In-Reply-To: <199607160612.PAA06367@sirius.sbl.cl.nec.co.jp> X-Mailer: AL-Mail 0.94Beta Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Naoki Hamada wrote: :I made it more robust. Not enough test yet, but this should :work. : :-nao OK. Nao, But I just have only 3c579 EISA not others and no technical manual. So, how can we certify all other hardware ? Because your code is also patching common if_ep.c, right ? Atsushi. -- Atsushi Murai E-Mail: amurai@spec.co.jp SPEC Voice : +81-3-3833-5341 System Planning and Engineering Corp. From owner-freebsd-current Tue Jul 16 19:14:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA04018 for current-outgoing; Tue, 16 Jul 1996 19:14:58 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA04000 for ; Tue, 16 Jul 1996 19:14:52 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.5+2.6Wbeta6/950912) with ESMTP id LAA23518; Wed, 17 Jul 1996 11:14:14 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id LAA07051; Wed, 17 Jul 1996 11:14:12 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id LAA13675; Wed, 17 Jul 1996 11:14:10 +0900 (JST) Date: Wed, 17 Jul 1996 11:14:10 +0900 (JST) From: Naoki Hamada Message-Id: <199607170214.LAA13675@sirius.sbl.cl.nec.co.jp> References: <9607170133.AA00383@tama3.spec.co.jp.spec.co.jp> To: amurai@spec.co.jp CC: gibbs@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org In-reply-to: Atsushi MURAI's message of "Wed, 17 Jul 1996 10:33:43 +0900" <9607170133.AA00383@tama3.spec.co.jp.spec.co.jp> Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Atsushi wrote: >OK. Nao, But I just have only 3c579 EISA not others and no technical >manual. So, how can we certify all other hardware ? Because your code >is also patching common if_ep.c, right ? `EtherLink III Parallel Tasking ISA, EISA, Micro Channel, and PCMCIA Adapter Drivers Technical Reference' from 3COM describes the resource configuration register: |For 3C509, 3C579, 3C589, 3C589B: | |bits 0-7: Reserved |bits 8-11: Reserved, must be all 1 |bits 12-15: IRQ | |For 3C509B: | |bits 0-5: Reserved |bit 6: Synchronous Ready |bits 7-11: Reserved |bits 12-15: IRQ | |Synchronous Ready: |Normal I/O cycles if clear. If set, the adapter will assert I/OCHRDY |on every I/O access. This may allow the board to work in a |noncompliant bus that would otherwise not be supported (for example, |an ISA bus running faster than spec). This bit defaults to 0 on |power-up, but is overwritten from the EEPROM. When the ep driver sets the IRQ of the resouce configuration register, it overwrites bits 0-11 with 0xf00. (So if an user sets 'Synchronous Ready' with the DOS utility, it is cancelled by the ep driver.) We have to be more preservative, so my revised driver reads the current value and writes it back. My patch affects only ISA and EISA attach routines. For now, my 3C509B works well. -nao From owner-freebsd-current Tue Jul 16 19:27:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA04953 for current-outgoing; Tue, 16 Jul 1996 19:27:10 -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 TAA04941 for ; Tue, 16 Jul 1996 19:27:05 -0700 (PDT) Received: from tama3.spec.co.jp ([202.32.13.219]) by specgw.spec.co.jp (8.7.5/3.3Wb-SPEC) with SMTP id LAA24692; Wed, 17 Jul 1996 11:26:43 +0900 (JST) From: Atsushi MURAI Message-Id: <9607170230.AA00385@tama3.spec.co.jp.spec.co.jp> Date: Wed, 17 Jul 1996 11:30:02 +0900 To: nao@sbl.cl.nec.co.jp Cc: gibbs@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) In-Reply-To: <199607170214.LAA13675@sirius.sbl.cl.nec.co.jp> X-Mailer: AL-Mail 0.94Beta Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Naoki Hamada wrote: :Atsushi wrote: :My patch affects only ISA and EISA attach routines. For now, my 3C509B :works well. :-nao OK. Whenever I can certify EISA side by my 3C579, we can assume all borad certified. So I will try this to evening and commiting. By the way, How can you get a technical manual ? I just ask to 3com for getting technical manual for 3C597(?) 100base TX...But no response yet. Atsushi. -- Atsushi Murai E-Mail: amurai@spec.co.jp SPEC Voice : +81-3-3833-5341 System Planning and Engineering Corp. From owner-freebsd-current Tue Jul 16 21:21:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA16958 for current-outgoing; Tue, 16 Jul 1996 21:21:24 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA16949 for ; Tue, 16 Jul 1996 21:21:21 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.5+2.6Wbeta6/950912) with ESMTP id NAA28571; Wed, 17 Jul 1996 13:21:13 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id NAA11879; Wed, 17 Jul 1996 13:21:12 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id NAA14690; Wed, 17 Jul 1996 13:21:10 +0900 (JST) Date: Wed, 17 Jul 1996 13:21:10 +0900 (JST) From: Naoki Hamada Message-Id: <199607170421.NAA14690@sirius.sbl.cl.nec.co.jp> References: <9607170230.AA00385@tama3.spec.co.jp.spec.co.jp> To: amurai@spec.co.jp CC: gibbs@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de, freebsd-current@freebsd.org In-reply-to: Atsushi MURAI's message of "Wed, 17 Jul 1996 11:30:02 +0900" <9607170230.AA00385@tama3.spec.co.jp.spec.co.jp> Subject: Re: Ethernet 3c579(EISA) is functional? (FIXED!) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Atsushi wrote: >By the way, How can you get a technical manual ? I just ask to 3com for >getting technical manual for 3C597(?) 100base TX...But no response yet. See section 8.6 of Ethernet-HOWTO from Linux. There is a good instruction which describes how to obtain technical documents from 3COM. You can contact 3COM with WWW. See http://infodeli.3com.com/infodeli/tools/3cfacts/3cfacts.htm and select 'new search database'. Search for 'Developer's Order Form' by keyward 'developer'. Select this form. 3COM sends you the form via FAX. Fill out the form and send it back to 3COM. 3COM will send you a reference in several days. I purchased a 3C597-TX (10Base-T and 100Base-TX adapter for EISA bus) last week, and asked 3COM for its technical reference. I am now waiting for its arrival. -nao From owner-freebsd-current Tue Jul 16 22:15:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA27284 for current-outgoing; Tue, 16 Jul 1996 22:15:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA27271 for ; Tue, 16 Jul 1996 22:15:05 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA26904; Wed, 17 Jul 1996 15:11:47 +1000 Date: Wed, 17 Jul 1996 15:11:47 +1000 From: Bruce Evans Message-Id: <199607170511.PAA26904@godzilla.zeta.org.au> To: current@freebsd.org Subject: sed broken Cc: mark@linus.demon.co.uk Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Making init_sysent.c in /sys/kern no longer works. sed looped and grew to 50MB before I killed it. I backed out to rounds of attempted fixes to sed/compile.c (to rev.1.4) and the make worked again. Bruce From owner-freebsd-current Tue Jul 16 22:38:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA00179 for current-outgoing; Tue, 16 Jul 1996 22:38:32 -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 WAA00168 for ; Tue, 16 Jul 1996 22:38:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id WAA09329; Tue, 16 Jul 1996 22:38:07 -0700 (PDT) Message-Id: <199607170538.WAA09329@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Bruce Evans cc: current@freebsd.org, mark@linus.demon.co.uk Subject: Re: sed broken In-reply-to: Your message of "Wed, 17 Jul 1996 15:11:47 +1000." <199607170511.PAA26904@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@root.com Date: Tue, 16 Jul 1996 22:38:07 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Making init_sysent.c in /sys/kern no longer works. sed looped and grew to >50MB before I killed it. I backed out to rounds of attempted fixes to >sed/compile.c (to rev.1.4) and the make worked again. Try Keith Bostic's final version (you'll have to dig it out of PR#1350) and see if it works. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Jul 16 22:46:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA00909 for current-outgoing; Tue, 16 Jul 1996 22:46:35 -0700 (PDT) Received: from woody.eis.net.au (woody.eis.net.au [203.12.171.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA00882 for ; Tue, 16 Jul 1996 22:46:27 -0700 (PDT) Received: (from root@localhost) by woody.eis.net.au (8.6.12/8.6.12) id PAA02171 for freebsd-current@freebsd.org; Wed, 17 Jul 1996 15:44:26 +1000 From: Charlie Root Message-Id: <199607170544.PAA02171@woody.eis.net.au> Subject: Make world stops on hierarchy To: freebsd-current@freebsd.org Date: Wed, 17 Jul 1996 15:44:25 +1000 (EST) 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 am having trouble with make world in -current the following error occurs pretty much immediatley. -------------------------------------------------------------- Making hierarchy -------------------------------------------------------------- cd /usr/src/etc && make distrib-dirs make: don't know how to make distrib-dirs. Stop *** Error code 2 Stop. This has only started over the last week or so, I seached the mail list archives for all recent articles on hierarchy or distrib-dirs but no refernce to this problem came up. I have tried rebuilding make but that had no effect. Any suggestions? - Ernie. From owner-freebsd-current Tue Jul 16 23:44:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA03881 for current-outgoing; Tue, 16 Jul 1996 23:44:04 -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 XAA03858 for ; Tue, 16 Jul 1996 23:44:02 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id XAA01990; Tue, 16 Jul 1996 23:44:32 -0700 Date: Tue, 16 Jul 1996 23:44:30 -0700 (PDT) From: Veggy Vinny To: current@freebsd.org Subject: /usr/bin/passwd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that the latest -current's /usr/bin/passwd will say: passwd: Permission denied if you run it from any user not in the wheel group, I have seen the same thing happen on 4 machines. Any ideas how to get passwd to work for users not in group wheel? Vince From owner-freebsd-current Tue Jul 16 23:45:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA03960 for current-outgoing; Tue, 16 Jul 1996 23:45:35 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts12-line6.uoregon.edu [128.223.150.138]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA03948 for ; Tue, 16 Jul 1996 23:45:26 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id XAA00462; Tue, 16 Jul 1996 23:45:20 -0700 (PDT) Date: Tue, 16 Jul 1996 23:45:19 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Domingo Siliceo cc: freebsd-current@freebsd.org Subject: Re: Opinions? In-Reply-To: <199607160700.IAA17390@afrodita.adam.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Jul 1996, Domingo Siliceo wrote: > I'm planning to switch one machine from NT to FreeBSD without any > special reason. What I'd like to know is your opinions. Is it hard to > configure a mode (US Robotics) under COM1 in order to connect with > our ISP? How many HD will I need to install XWindow system? Hooking the modem up should be a breeze if your ISP supports PPP. All you'll need to do is confirm the settings for ijppp in /etc/ppp.conf. Full instructions are in the Handbook. For X, you should have better than 50 megs free. A quick du on my system gives: gdi,ttyp1,/usr,29>du -sk X11R6 du: X11R6/lib/X11/xdm/authdir: Permission denied 45628 X11R6 ^^^^^ 1k blocks. That is with Netscape and other X junk in there. I'm still trying to understand why people think they have to run NT. There are other options, like FreeBSD and OS/2. A lot cheaper and not made by Microsoft. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Wed Jul 17 00:56:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07150 for current-outgoing; Wed, 17 Jul 1996 00:56:58 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA07145 for ; Wed, 17 Jul 1996 00:56:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA00019; Wed, 17 Jul 1996 17:54:01 +1000 Date: Wed, 17 Jul 1996 17:54:01 +1000 From: Bruce Evans Message-Id: <199607170754.RAA00019@godzilla.zeta.org.au> To: bde@zeta.org.au, davidg@root.com Subject: Re: sed broken Cc: bostic@bsdi.com, current@FreeBSD.org, mark@linus.demon.co.uk Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>Making init_sysent.c in /sys/kern no longer works. sed looped and grew to >>50MB before I killed it. I backed out to rounds of attempted fixes to >>sed/compile.c (to rev.1.4) and the make worked again. > Try Keith Bostic's final version (you'll have to dig it out of PR#1350) and >see if it works. Our PR's seem to be tangled up: some followups to #1350 are in #1353, #1354 and #1356 with Keith's final version in #1356. I fixed it independently before locating all the PR's. My version is the same as Keith's except it loses more gracefully for lines not terminated by a newline. Bruce Index: compile.c =================================================================== RCS file: /a/ncvs/src/usr.bin/sed/compile.c,v retrieving revision 1.4 diff -c -2 -r1.4 compile.c *** compile.c 1995/08/16 05:56:42 1.4 --- compile.c 1996/07/17 07:08:56 *************** *** 616,620 **** compile_text() { ! int asize, size; char *text, *p, *op, *s; char lbuf[_POSIX2_LINE_MAX + 1]; --- 616,620 ---- compile_text() { ! int asize, esc_nl, size; char *text, *p, *op, *s; char lbuf[_POSIX2_LINE_MAX + 1]; *************** *** 627,637 **** p = lbuf; EATSPACE(); ! for (; *p; p++) { ! if (*p == '\\') ! p++; *s++ = *p; } size += s - op; ! if (p[-2] != '\\') { *s = '\0'; break; --- 627,637 ---- p = lbuf; EATSPACE(); ! for (esc_nl = 0; *p != '\0'; p++) { ! if (*p == '\\' && p[1] != '\0' && *++p == '\n') ! esc_nl = 1; *s++ = *p; } size += s - op; ! if (!esc_nl) { *s = '\0'; break; From owner-freebsd-current Wed Jul 17 01:27:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA08852 for current-outgoing; Wed, 17 Jul 1996 01:27:02 -0700 (PDT) Received: from silvia.hip.berkeley.edu (sjx-ca51-01.ix.netcom.com [206.214.103.161]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA08843; Wed, 17 Jul 1996 01:26:59 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.7.5/8.6.12) id BAA02778; Wed, 17 Jul 1996 01:26:51 -0700 (PDT) Date: Wed, 17 Jul 1996 01:26:51 -0700 (PDT) Message-Id: <199607170826.BAA02778@silvia.hip.berkeley.edu> To: jkh@time.cdrom.com CC: ache@nagual.ru, jkh@freebsd.org, current@freebsd.org In-reply-to: <16966.835774823@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: various 'fetch' errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Hmmm. Well, I thought Andrey's request was a reasonable one (it makes * mirroring actually work, for one thing) so I added it as the default * behavior. I'll add a flag for making it do what you want as well. Have you ever got around to this? :) Satoshi From owner-freebsd-current Wed Jul 17 03:53:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA29630 for current-outgoing; Wed, 17 Jul 1996 03:53:59 -0700 (PDT) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA29621 for ; Wed, 17 Jul 1996 03:53:49 -0700 (PDT) Received: from cantina.clinet.fi (root@cantina.clinet.fi [194.100.0.15]) by hauki.clinet.fi (8.7.5/8.6.4) with ESMTP id NAA16299 for ; Wed, 17 Jul 1996 13:53:39 +0300 (EET DST) Received: (hsu@localhost) by cantina.clinet.fi (8.7.5/8.6.4) id NAA12835; Wed, 17 Jul 1996 13:53:39 +0300 (EET DST) Date: Wed, 17 Jul 1996 13:53:39 +0300 (EET DST) Message-Id: <199607171053.NAA12835@cantina.clinet.fi> From: Heikki Suonsivu To: freebsd-current@freebsd.org Subject: vm work helps Organization: Clinet Ltd, Espoo, Finland Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that John Dyson and David Greenman also managed to kill bugs crashing and deadlocking my machines while fixing freefall problems. I have still had one panic but I have 7 days of uptime on our news server, which, sadly, is an all-time record for us running FreeBSD 2 on a full-feed news server. I will see how it goes for couple of weeks more. (5 minutes after I mail this the machine will crash, 100% sure :-) -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121 From owner-freebsd-current Wed Jul 17 04:14:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA00838 for current-outgoing; Wed, 17 Jul 1996 04:14:39 -0700 (PDT) Received: from al.imforei.apana.org.au (root@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA00809 for ; Wed, 17 Jul 1996 04:14:01 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.5/8.7.3) id UAA20709; Wed, 17 Jul 1996 20:43:15 +0930 (CST) Date: Wed, 17 Jul 1996 20:43:15 +0930 (CST) From: Peter Childs Message-Id: <199607171113.UAA20709@al.imforei.apana.org.au> To: dwhite@resnet.uoregon.edu, freebsd-current@freebsd.org Subject: Re: Opinions? X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: : : I'm still trying to understand why people think they have to run NT. : There are other options, like FreeBSD and OS/2. A lot cheaper and not : made by Microsoft. : If your confident enough in your ability then FreeBSD is great, but if you aren't too confident, then NT is great. If it doesn't work and you can't figure out why you can just blame MS if your boss starts frying your ass. If you've gone FreeBSD and your boss starts frying your ass and you made the push to go FreeBSD instead of NT then you have to be able to stand up for yourself again and again against people that are highly opinionated, base all their technical decisions on rumour, press releases, or marketing lunches, and think that the more you pay for something the better it has to be. Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds The internet is full, please try again in half an hour... From owner-freebsd-current Wed Jul 17 04:25:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA01617 for current-outgoing; Wed, 17 Jul 1996 04:25:03 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA01611 for ; Wed, 17 Jul 1996 04:25:01 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.5/8.7.3) id VAA13284 for current@freebsd.org; Wed, 17 Jul 1996 21:24:57 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id VAA12907 for ; Wed, 17 Jul 1996 21:26:07 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id LAA19805 for ; Wed, 17 Jul 1996 11:28:36 GMT Message-Id: <199607171128.LAA19805@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: OK, now that 2.1.5 is out, let's have gcc-2.7.2! X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jul 1996 21:28:35 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm wondering when Peter Wemm is going to import gcc-2.7.2 (+ patches) & libg++-2.7.1, as discussed a few weeks back. There's a few (unrelated) changes in store for libc_r, as I recall as well. Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Wed Jul 17 04:41:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA02628 for current-outgoing; Wed, 17 Jul 1996 04:41:57 -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 EAA02623; Wed, 17 Jul 1996 04:41:55 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id EAA23974; Wed, 17 Jul 1996 04:41:28 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: ache@nagual.ru, jkh@freebsd.org, current@freebsd.org Subject: Re: various 'fetch' errors In-reply-to: Your message of "Wed, 17 Jul 1996 01:26:51 PDT." <199607170826.BAA02778@silvia.hip.berkeley.edu> Date: Wed, 17 Jul 1996 04:41:28 -0700 Message-ID: <23972.837603688@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Uh, no. Remind me what I promised to implement again? :-) Jordan > * Hmmm. Well, I thought Andrey's request was a reasonable one (it makes > * mirroring actually work, for one thing) so I added it as the default > * behavior. I'll add a flag for making it do what you want as well. > > Have you ever got around to this? :) > > Satoshi From owner-freebsd-current Wed Jul 17 07:21:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA08901 for current-outgoing; Wed, 17 Jul 1996 07:21:29 -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 HAA08895 for ; Wed, 17 Jul 1996 07:21:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id HAA10162; Wed, 17 Jul 1996 07:20:04 -0700 (PDT) Message-Id: <199607171420.HAA10162@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Heikki Suonsivu cc: freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of "Wed, 17 Jul 1996 13:53:39 +0300." <199607171053.NAA12835@cantina.clinet.fi> From: David Greenman Reply-To: davidg@root.com Date: Wed, 17 Jul 1996 07:20:04 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It seems that John Dyson and David Greenman also managed to kill bugs >crashing and deadlocking my machines while fixing freefall problems. I ^^^^^^^^ Actually, freefall has been quite stable...it's wcarchive I've been having problems with, and now it appears that the problems were caused by defective hardware all along...but hey, at least we fixed a bunch of bugs along the way to discovering this. :-) >have still had one panic but I have 7 days of uptime on our news server, >which, sadly, is an all-time record for us running FreeBSD 2 on a full-feed >news server. I will see how it goes for couple of weeks more. ...I'm interested in hearing about the panic. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Jul 17 08:07:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA13770 for current-outgoing; Wed, 17 Jul 1996 08:07:30 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA13763 for ; Wed, 17 Jul 1996 08:07:22 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id QAA20911 for ; Wed, 17 Jul 1996 16:08:37 +0100 Date: Wed, 17 Jul 1996 16:08:36 +0100 (BST) From: Doug Rabson To: freebsd-current@freebsd.org Subject: DDB problems Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2063988803-837616116=:19927" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2063988803-837616116=:19927 Content-Type: TEXT/PLAIN; charset=US-ASCII I was just trying to use ddb in a current kernel and my keyboard locks up after continuing from a ctl-alt-esc break into the debugger. Does anyone else get this? I have attached my kernel config if that helps. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 --0-2063988803-837616116=:19927 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=TROUT Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: kernel config file Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIwkkSWQ6IEdFTkVSSUMsdiAxLjcz IDE5OTYvMDcvMTAgMDM6MzU6NTkgamtoIEV4cCAkDQojDQoNCm1hY2hpbmUJ CSJpMzg2Ig0KY3B1CQkiSTM4Nl9DUFUiDQpjcHUJCSJJNDg2X0NQVSINCmNw dQkJIkk1ODZfQ1BVIg0KY3B1CQkiSTY4Nl9DUFUiDQppZGVudAkJR0VORVJJ Qw0KbWF4dXNlcnMJMTANCg0Kb3B0aW9ucwkJTUFUSF9FTVVMQVRFCQkjU3Vw cG9ydCBmb3IgeDg3IGVtdWxhdGlvbg0Kb3B0aW9ucwkJSU5FVAkJCSNJbnRl ck5FVHdvcmtpbmcNCm9wdGlvbnMJCUZGUwkJCSNCZXJrZWxleSBGYXN0IEZp bGVzeXN0ZW0NCm9wdGlvbnMJCU5GUwkJCSNOZXR3b3JrIEZpbGVzeXN0ZW0N Cm9wdGlvbnMJCU1TRE9TRlMJCQkjTVNET1MgRmlsZXN5c3RlbQ0Kb3B0aW9u cwkJIkNEOTY2MCIJCSNJU08gOTY2MCBGaWxlc3lzdGVtDQpvcHRpb25zCQlQ Uk9DRlMJCQkjUHJvY2VzcyBmaWxlc3lzdGVtDQpvcHRpb25zCQkiQ09NUEFU XzQzIgkJI0NvbXBhdGlibGUgd2l0aCBCU0QgNC4zIFtLRUVQIFRISVMhXQ0K b3B0aW9ucwkJU0NTSV9ERUxBWT0xNQkJI0JlIHBlc3NpbWlzdGljIGFib3V0 IEpvZSBTQ1NJIGRldmljZQ0Kb3B0aW9ucwkJQk9VTkNFX0JVRkZFUlMJCSNp bmNsdWRlIHN1cHBvcnQgZm9yIERNQSBib3VuY2UgYnVmZmVycw0Kb3B0aW9u cwkJVUNPTlNPTEUJCSNBbGxvdyB1c2VycyB0byBncmFiIHRoZSBjb25zb2xl DQpvcHRpb25zCQlGQUlMU0FGRQkJI0JlIGNvbnNlcnZhdGl2ZQ0Kb3B0aW9u cwkJRERCDQoNCmNvbmZpZwkJa2VybmVsCXJvb3Qgb24gd2QwDQoNCmNvbnRy b2xsZXIJaXNhMA0KI2NvbnRyb2xsZXIJZWlzYTANCmNvbnRyb2xsZXIJcGNp MA0KDQpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19GRDEiIGJp byBpcnEgNiBkcnEgMiB2ZWN0b3IgZmRpbnRyDQpkaXNrCQlmZDAJYXQgZmRj MCBkcml2ZSAwDQojZGlzawkJZmQxCWF0IGZkYzAgZHJpdmUgMQ0KI3RhcGUJ CWZ0MAlhdCBmZGMwIGRyaXZlIDINCg0KI2NvbnRyb2xsZXIJd2RjMAlhdCBp c2E/IHBvcnQgIklPX1dEMSIgYmlvIGlycSAxNCB2ZWN0b3Igd2RpbnRyDQoj ZGlzawkJd2QwCWF0IHdkYzAgZHJpdmUgMA0KI2Rpc2sJCXdkMQlhdCB3ZGMw IGRyaXZlIDENCg0KI2NvbnRyb2xsZXIJd2RjMQlhdCBpc2E/IHBvcnQgIklP X1dEMiIgYmlvIGlycSAxNSB2ZWN0b3Igd2RpbnRyDQojZGlzawkJd2QyCWF0 IHdkYzEgZHJpdmUgMA0KI2Rpc2sJCXdkMwlhdCB3ZGMxIGRyaXZlIDENCg0K I29wdGlvbnMJCUFUQVBJCQkjRW5hYmxlIEFUQVBJIHN1cHBvcnQgZm9yIElE RSBidXMNCiNvcHRpb25zCQlBVEFQSV9TVEFUSUMJI0Rvbid0IGRvIGl0IGFz IGFuIExLTQ0KI2RldmljZQkJd2NkMAkjSURFIENELVJPTQ0KDQojIEEgc2lu Z2xlIGVudHJ5IGZvciBhbnkgb2YgdGhlc2UgY29udHJvbGxlcnMgKG5jciwg YWhiLCBhaGMpIGlzIHN1ZmZpY2llbnQNCiMgZm9yIGFueSBudW1iZXIgb2Yg aW5zdGFsbGVkIGRldmljZXMuDQojY29udHJvbGxlcgluY3IwDQojY29udHJv bGxlcglhaGIwDQpjb250cm9sbGVyCWFoYzANCg0KI2NvbnRyb2xsZXIJYnQw CWF0IGlzYT8gcG9ydCAiSU9fQlQwIiBiaW8gaXJxID8gdmVjdG9yIGJ0X2lz YV9pbnRyDQojY29udHJvbGxlcgl1aGEwCWF0IGlzYT8gcG9ydCAiSU9fVUhB MCIgYmlvIGlycSA/IGRycSA1IHZlY3RvciB1aGFpbnRyDQojY29udHJvbGxl cglhaGEwCWF0IGlzYT8gcG9ydCAiSU9fQUhBMCIgYmlvIGlycSA/IGRycSA1 IHZlY3RvciBhaGFpbnRyDQojY29udHJvbGxlcglhaWMwCWF0IGlzYT8gcG9y dCAweDM0MCBiaW8gaXJxIDExIHZlY3RvciBhaWNpbnRyDQojY29udHJvbGxl cgluY2EwCWF0IGlzYT8gcG9ydCAweDFmODggYmlvIGlycSAxMCB2ZWN0b3Ig bmNhaW50cg0KI2NvbnRyb2xsZXIJbmNhMQlhdCBpc2E/IHBvcnQgMHgzNTAg YmlvIGlycSA1IHZlY3RvciBuY2FpbnRyDQojY29udHJvbGxlcglzZWEwCWF0 IGlzYT8gYmlvIGlycSA1IGlvbWVtIDB4YzgwMDAgaW9zaXogMHgyMDAwIHZl Y3RvciBzZWFpbnRyDQoNCmNvbnRyb2xsZXIJc2NidXMwDQoNCmRldmljZQkJ c2QwDQoNCmRldmljZQkJb2QwCSNTZWUgTElOVCBmb3IgcG9zc2libGUgYG9k JyBvcHRpb25zLg0KDQpkZXZpY2UJCXN0MA0KDQpkZXZpY2UJCWNkMAkjT25s eSBuZWVkIG9uZSBvZiB0aGVzZSwgdGhlIGNvZGUgZHluYW1pY2FsbHkgZ3Jv d3MNCg0KI2RldmljZQkJd3QwCWF0IGlzYT8gcG9ydCAweDMwMCBiaW8gaXJx IDUgZHJxIDEgdmVjdG9yIHd0aW50cg0KI2RldmljZQkJbWNkMAlhdCBpc2E/ IHBvcnQgMHgzMDAgYmlvIGlycSAxMCB2ZWN0b3IgbWNkaW50cg0KDQojY29u dHJvbGxlcgltYXRjZDAJYXQgaXNhPyBwb3J0IDB4MjMwIGJpbw0KDQojZGV2 aWNlCQlzY2QwCWF0IGlzYT8gcG9ydCAweDIzMCBiaW8NCg0KIyBzeXNjb25z IGlzIHRoZSBkZWZhdWx0IGNvbnNvbGUgZHJpdmVyLCByZXNlbWJsaW5nIGFu IFNDTyBjb25zb2xlDQpkZXZpY2UJCXNjMAlhdCBpc2E/IHBvcnQgIklPX0tC RCIgdHR5IGlycSAxIHZlY3RvciBzY2ludHINCiMgRW5hYmxlIHRoaXMgYW5k IFBDVlRfRlJFRUJTRCBmb3IgcGN2dCB2dDIyMCBjb21wYXRpYmxlIGNvbnNv bGUgZHJpdmVyDQojZGV2aWNlCQl2dDAJYXQgaXNhPyBwb3J0ICJJT19LQkQi IHR0eSBpcnEgMSB2ZWN0b3IgcGNyaW50DQojb3B0aW9ucwkJUENWVF9GUkVF QlNEPTIxMAkjIHBjdnQgcnVubmluZyBvbiBGcmVlQlNEID49IDIuMC41DQoj b3B0aW9ucwkJWFNFUlZFUgkJCSMgaW5jbHVkZSBjb2RlIGZvciBYRnJlZTg2 DQojb3B0aW9ucwkJRkFUX0NVUlNPUgkJIyBzdGFydCB3aXRoIGJsb2NrIGN1 cnNvcg0KIyBJZiB5b3UgaGF2ZSBhIFRoaW5rUEFELCB1bmNvbW1lbnQgdGhp cyBhbG9uZyB3aXRoIHRoZSByZXN0IG9mIHRoZSBQQ1ZUIGxpbmVzDQojb3B0 aW9ucwkJUENWVF9TQ0FOU0VUPTIJCSMgSUJNIGtleWJvYXJkcyBhcmUgbm9u LXN0ZA0KDQojIE1hbmRhdG9yeSwgZG9uJ3QgcmVtb3ZlDQpkZXZpY2UJCW5w eDAJYXQgaXNhPyBwb3J0ICJJT19OUFgiIGlycSAxMyB2ZWN0b3IgbnB4aW50 cg0KDQojDQojIExhcHRvcCBzdXBwb3J0IChzZWUgTElOVCBmb3IgbW9yZSBv cHRpb25zKQ0KIw0KI2RldmljZQkJYXBtMCAgICBhdCBpc2E/CWRpc2FibGUJ IyBBZHZhbmNlZCBQb3dlciBNYW5hZ2VtZW50DQojb3B0aW9ucwkJQVBNX0JS T0tFTl9TVEFUQ0xPQ0sJIyBXb3JrYXJvdW5kIHNvbWUgYnVnZ3kgQVBNIEJJ T1MNCiMgUENDQVJEIChQQ01DSUEpIHN1cHBvcnQNCiNjb250cm9sbGVyCWNy ZDANCiNkZXZpY2UJCXBjaWMwCWF0IGNyZD8NCiNkZXZpY2UJCXBjaWMxCWF0 IGNyZD8NCg0KZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIg dHR5IGlycSA0IHZlY3RvciBzaW9pbnRyDQpkZXZpY2UJCXNpbzEJYXQgaXNh PyBwb3J0ICJJT19DT00yIiB0dHkgaXJxIDMgdmVjdG9yIHNpb2ludHINCg0K ZGV2aWNlCQlscHQwCWF0IGlzYT8gcG9ydD8gdHR5IGlycSA3IHZlY3RvciBs cHRpbnRyDQojZGV2aWNlCQlscHQxCWF0IGlzYT8gcG9ydD8gdHR5DQojZGV2 aWNlCQltc2UwCWF0IGlzYT8gcG9ydCAweDIzYyB0dHkgaXJxIDUgdmVjdG9y IG1zZWludHINCg0KI2RldmljZQkJcHNtMAlhdCBpc2E/IGRpc2FibGUgcG9y dCAiSU9fS0JEIiBjb25mbGljdHMgdHR5IGlycSAxMiB2ZWN0b3IgcHNtaW50 cg0KDQojIE9yZGVyIGlzIGltcG9ydGFudCBoZXJlIGR1ZSB0byBpbnRydXNp dmUgcHJvYmVzLCBkbyAqbm90KiBhbHBoYWJldGl6ZQ0KIyB0aGlzIGxpc3Qg b2YgbmV0d29yayBpbnRlcmZhY2VzIHVudGlsIHRoZSBwcm9iZXMgaGF2ZSBi ZWVuIGZpeGVkLg0KIyBSaWdodCBub3cgaXQgYXBwZWFycyB0aGF0IHRoZSBp ZTAgbXVzdCBiZSBwcm9iZWQgYmVmb3JlIGVwMC4gU2VlDQojIHJldmlzaW9u IDEuMjAgb2YgdGhpcyBmaWxlLg0KZGV2aWNlIGRlMA0KI2RldmljZSBmeHAw DQojZGV2aWNlIHZ4MA0KDQojZGV2aWNlIGVkMCBhdCBpc2E/IHBvcnQgMHgy ODAgbmV0IGlycSAgNSBpb21lbSAweGQ4MDAwIHZlY3RvciBlZGludHINCiNk ZXZpY2UgZWQxIGF0IGlzYT8gcG9ydCAweDMwMCBuZXQgaXJxICA1IGlvbWVt IDB4ZDgwMDAgdmVjdG9yIGVkaW50cg0KI2RldmljZSBpZTAgYXQgaXNhPyBw b3J0IDB4MzYwIG5ldCBpcnEgIDcgaW9tZW0gMHhkMDAwMCB2ZWN0b3IgaWVp bnRyDQojZGV2aWNlIGVwMCBhdCBpc2E/IHBvcnQgMHgzMDAgbmV0IGlycSAx MCB2ZWN0b3IgZXBpbnRyDQojZGV2aWNlIGZlMCBhdCBpc2E/IHBvcnQgMHgz MDAgbmV0IGlycSA/IHZlY3RvciBmZWludHINCiNkZXZpY2UgaXgwIGF0IGlz YT8gcG9ydCAweDMwMCBuZXQgaXJxIDEwIGlvbWVtIDB4ZDAwMDAgaW9zaXog MzI3NjggdmVjdG9yIGl4aW50cg0KI2RldmljZSBsZTAgYXQgaXNhPyBwb3J0 IDB4MzAwIG5ldCBpcnEgNSBpb21lbSAweGQwMDAwIHZlY3RvciBsZV9pbnRy DQojZGV2aWNlIGxuYzAgYXQgaXNhPyBwb3J0IDB4MjgwIG5ldCBpcnEgMTAg ZHJxIDAgdmVjdG9yIGxuY2ludHINCiNkZXZpY2UgemUwIGF0IGlzYT8gcG9y dCAweDMwMCBuZXQgaXJxIDUgaW9tZW0gMHhkODAwMCB2ZWN0b3IgemVpbnRy DQojZGV2aWNlIHpwMCBhdCBpc2E/IHBvcnQgMHgzMDAgbmV0IGlycSAxMCBp b21lbSAweGQ4MDAwIHZlY3RvciB6cGludHINCg0KcHNldWRvLWRldmljZQls b29wDQpwc2V1ZG8tZGV2aWNlCWV0aGVyDQpwc2V1ZG8tZGV2aWNlCWxvZw0K cHNldWRvLWRldmljZQlzbAkxDQojIGlqcHBwIHVzZXMgdHVuIGluc3RlYWQg b2YgcHBwIGRldmljZQ0KI3BzZXVkby1kZXZpY2UJcHBwCTENCnBzZXVkby1k ZXZpY2UJdHVuCTENCnBzZXVkby1kZXZpY2UJcHR5CTE2DQpwc2V1ZG8tZGV2 aWNlCWd6aXAJCSMgRXhlYyBnemlwcGVkIGEub3V0J3MNCg0KIyBLVFJBQ0Ug ZW5hYmxlcyB0aGUgc3lzdGVtLWNhbGwgdHJhY2luZyBmYWNpbGl0eSBrdHJh Y2UoMikuDQojIFRoaXMgYWRkcyA0IEtCIGJsb2F0IHRvIHlvdXIga2VybmVs LCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzDQojIHRoZSBjb3N0cyBvZiBlYWNo IHN5c2NhbGwuDQpvcHRpb25zCQlLVFJBQ0UJCSNrZXJuZWwgdHJhY2luZw0K cHNldWRvLWRldmljZQlicGZpbHRlcgk0CSNCZXJrZWxleSBwYWNrZXQgZmls dGVyDQo= --0-2063988803-837616116=:19927-- From owner-freebsd-current Wed Jul 17 09:03:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00367 for current-outgoing; Wed, 17 Jul 1996 09:03:26 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA00342 for ; Wed, 17 Jul 1996 09:03:20 -0700 (PDT) Received: from acc0.elvisti.kiev.ua (acc0.elvisti.kiev.ua [193.125.28.132]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id IAA23317 for ; Wed, 17 Jul 1996 08:45:54 -0700 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by acc0.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id SAA09574 for ; Wed, 17 Jul 1996 18:46:42 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id SAA22225 for current@freebsd.org; Wed, 17 Jul 1996 18:46:41 +0300 From: "Andrew V. Stesin" Message-Id: <199607171546.SAA22225@office.elvisti.kiev.ua> Subject: 'info info' doesn't work To: current@freebsd.org Date: Wed, 17 Jul 1996 18:46:40 +0300 (EET DST) X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, the system is 960612-SNAP of -current with zero modifications. It seems that a big part of GNUish Fine Manuals aren't installed... am I the only one seeing this? Even 'info info' doesn't work, not to mention 'info gcc' or whatever. -- With best regards -- Andrew Stesin. Phones/fax: +380 (44) { 244-0122, 276-0188, 271-3457, 271-3560 } "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-current Wed Jul 17 09:11:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00980 for current-outgoing; Wed, 17 Jul 1996 09:11:56 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA00957; Wed, 17 Jul 1996 09:11:50 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id JAA05923; Wed, 17 Jul 1996 09:10:55 -0700 (PDT) Message-Id: <199607171610.JAA05923@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: dwhite@resnet.uoregon.edu cc: Domingo Siliceo , freebsd-current@freebsd.org, freebsd-chat@freebsd.org Reply-To: freebsd-chat@freebsd.org Followup-To: freebsd-chat@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of Tue, 16 Jul 96 23:45:19 -0700. Date: Wed, 17 Jul 1996 09:10:54 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I'm still trying to understand why people think they have to run NT. >There are other options, like FreeBSD and OS/2. A lot cheaper and not >made by Microsoft. > Because NT is a very solid server OS. It is tightly integrated with the most popular application server software, Microsoft BackOffice. It is *the* most stable OS I have run. It scales well across multiple CPUs, and has a very solid multi-processor and multi-threaded kernel. NT 4.0 will have not only dynamically scheduled threads, but user- scheduled threads called fibers (that are like Sun LWPs). It runs on Intel, MIPS, DEC Alpha and PowerPC architectures. It is a lot easier to administer than a Unix box. It is more secure than OS/2 (certified C2). It runs on more hardware than OS/2 (it runs on the PowerPC chip -- an IBM processor -- that OS/2 won't even run on). It scales higher than OS/2. It has a more flexible, more stable, more secure filesystem than OS/2 (NTFS vs. HPFS). NT will run Windows 95 software. It has OpenGL 3D rendering libraries built in. It comes bundled with a very capable web browser. It comes bundled with a decent web server. It comes bundled with complete networking, including multi-protocol routing. NT 4.0 will come with Point-To-Point tunneling protocol. NT 4.0 will come with a very cool and solid CERN-compatible caching firewall and proxy server. I could go on, but this could get monotonous.... NT is not Windows 95. You asked. Sure, *I* love Unix the best, and I'll be running a version of BSD until they pry it out of my cold, dead fingers. But it's pretty unrealistic to expect someone who's main job is to run a business, to learn all the quirkiness of Unix. NT and OS/2 are just better solutions than Unix for many of these people. And NT is a better server product in so many ways than OS/2. Plus, NT is a better business "workstation" OS than Unix because of all the business applications it runs. I don't understand why people want to shoot themselves in the foot, just because they have some religious problem with Microsoft. If Microsoft makes the best keyboard, and you choose something worse with a mushy feel or a wrist-crippling legacy design, just because you can't look at the logo, your loss. If Microsoft makes the best software product for a certain use, and you insist on using something inferior just because you just because it says Microsoft on the box, your loss. What's more, I don't see why people think IBM is so much better than Microsoft. If you're against big, market-dominating companies, you might be surprised to learn that IBM is more than five times the size of Microsoft, by the number of employees. Just because their marketing sucks doesn't mean they have any less of a desire to foist their own agenda on the industry. Just look who gave us the crappy PC architecture to begin with. Sure, DOS sucks. Sure, Win16 was a model of mediocrity. Sure, Microsoft doesn't make everything the best. Sure there are many other alternatives to several of their products out there. But, specifically, OS/2 vs. NT, OS/2 has already lost the war. And that keyboard debate: buy what you want; I want the keyboard that is going to give me the most comfortable touch-typing feel, and by coincidence, it also happens to have a Microsoft logo on it. This is clearly outside the focus for freebsd-current. Please direct followups to freebsd-chat, and/or private mail. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Wed Jul 17 10:43:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06043 for current-outgoing; Wed, 17 Jul 1996 10:43:16 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA06038 for ; Wed, 17 Jul 1996 10:43:14 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA23540 for ; Wed, 17 Jul 1996 10:41:13 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA19518; Wed, 17 Jul 1996 19:21:00 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA07635; Wed, 17 Jul 1996 19:21:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id SAA00306; Wed, 17 Jul 1996 18:59:15 +0200 (MET DST) From: J Wunsch Message-Id: <199607171659.SAA00306@uriah.heep.sax.de> Subject: Re: 'info info' doesn't work To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 17 Jul 1996 18:59:15 +0200 (MET DST) Cc: stesin@elvisti.kiev.ua (Andrew V. Stesin) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607171546.SAA22225@office.elvisti.kiev.ua> from "Andrew V. Stesin" at "Jul 17, 96 06:46:40 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 Andrew V. Stesin wrote: > It seems that a big part of GNUish Fine Manuals aren't > installed... am I the only one seeing this? > Even 'info info' doesn't work, not to mention 'info gcc' > or whatever. Both work for me. I've re-installed yesterday, but cannot remember that it was broken at any time (but haven't looked very often either). -- 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 17 11:13:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA07936 for current-outgoing; Wed, 17 Jul 1996 11:13:08 -0700 (PDT) Received: from wireless.Stanford.EDU (wireless.Stanford.EDU [36.10.0.102]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA07930 for ; Wed, 17 Jul 1996 11:13:06 -0700 (PDT) Received: from localhost (akyol@localhost) by wireless.Stanford.EDU (8.7.5/8.7.1) with ESMTP id LAA27989 for ; Wed, 17 Jul 1996 11:13:04 -0700 (PDT) Message-Id: <199607171813.LAA27989@wireless.Stanford.EDU> X-Mailer: exmh version 1.6.7 5/3/96 To: freebsd-current@freebsd.org Subject: New Voxware Sound Driver Code and Perl script for kernel config Mime-Version: 1.0 Content-Type: application/pgp; format=mime; x-action=signclear; x-originator=372744A1 Content-Transfer-Encoding: 7bit Date: Wed, 17 Jul 1996 11:13:04 -0700 From: Bora Akyol Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Content-Type: text/plain; charset=us-ascii Does anyone know if the 3.5 version of the Voxware sound drivers will be incorporated into the new kernel source. Also on that note I am thinking about hacking a perl script that will configure the kernel and generate a configuration file etc. . First, is there such a script already, second, is there need for such a script? I am thinking of something like Linux;s "make config". Thanks - -- - ------------------------------------------------------------ Bora Aydin Akyol akyol@leland.stanford.edu - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMe0tLcF/lRw3J0ShAQGsDwQAuhmwdutSf3mHdjcQtGQa0kTHhuUw4yzF e0DCdZatGT8GOUQL/T4zXM3oHRh1xTLMTlijfxf6K2pGYy+vX+VDKR9f+J505UrU XpTPv6GJVwdyP1hQSnsOFWX75jqugCl8F7gWnVPJF8pje6sywhLiPQ3a9C3iFUkn FgaN+p2rvWk= =UnYb -----END PGP SIGNATURE----- From owner-freebsd-current Wed Jul 17 11:24:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08468 for current-outgoing; Wed, 17 Jul 1996 11:24:20 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA08462 for ; Wed, 17 Jul 1996 11:24:16 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id NAA00713 for current@freefall.cdrom.com; Wed, 17 Jul 1996 13:25:03 -0459 (CDT) Message-Id: <199607171824.NAA00713@utgard.bga.com> Subject: Floating point errors in povray on current To: current@freefall.FreeBSD.org Date: Wed, 17 Jul 1996 13:25:03 -0459 (CDT) From: "Boyd R. Faulkner" X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am having a problem with povray, which I have mentioned before, concerning core dumps in povray for certain source files. They only occur under current. I have run it on 2 other machines (all are P100 ASUS machines) running 2.1 and there is no problem. In ~faulkner/povray on freefall, there is a source file ballbox1.pov and the script I run, do_pov, and the core file. Could someone please verify that this fails on current. I cannot upgrade the two P100's running 2.1 at this time. Thanks, Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Wed Jul 17 12:02:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10299 for current-outgoing; Wed, 17 Jul 1996 12:02: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 MAA10292; Wed, 17 Jul 1996 12:02:37 -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 MAA01075; Wed, 17 Jul 1996 12:02:33 -0700 (PDT) To: freebsd-chat@freebsd.org cc: dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of "Wed, 17 Jul 1996 09:10:54 PDT." <199607171610.JAA05923@MindBender.HeadCandy.com> Date: Wed, 17 Jul 1996 12:02:32 -0700 Message-ID: <1073.837630152@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > learn all the quirkiness of Unix. NT and OS/2 are just better > solutions than Unix for many of these people. And NT is a better > server product in so many ways than OS/2. Plus, NT is a better > business "workstation" OS than Unix because of all the business > applications it runs. While I don't disagree with any of your major points, and agree that NT is *definitely* something we should be afraid (very afraid) of, I think you missed one important point about it which Microsoft will be the last to mention in their sales hype: Cost. Task: Create a small ISP using 3 or 4 PCs which will provide web service, POP email accounts, News, DNS, dial-in SLIP/PPP and general routing. Say we're also projecting between 500-1000 users as our target customer base within a 6 month timeframe (and, assuming we live in an area where coverage is still somewhat spotty, that's not an unrealistic expectation at all) so we need to make sure we can grow into that without too much pain since we'll already be going insane trying to get the billing set up, the tech support hotline staffed, etc. The last thing we need is for our tech to run out of steam halfway down the line. Now, go price 3 copies of NT Server plus the 1000 user commercial pop package you'll have to buy along with the relevant DNS, News and SLIP/PPP software (also throw in NFS so that you can eventually share filesystems with that SGI Challenge machine you've got your lustful eyes on and will buy once you hit 500 users to take some of the load off). See the total you're quoted. Suffer heart failure. Be revived by paramedics. Send $39.95 from your hospital bed to Walnut Creek CDROM for *one* copy of FreeBSD and swear off Microsoft forever. :-) Seriously, NT looks attractive from a single-user standpoint, I'll give it full marks for that, but once you try and put together even half of the packages you get for free under UNIX to create a small ISP or business server application, you're talking some serious bucks and, from everything I've heard, you won't even get close to the performance of a well-tuned *BSD box doing the same thing once you're done. Eventually I suppose that Microsoft will catch on to this and/or the free software community will provide some of the missing pieces, but that doesn't help today's customers very much. Jordan From owner-freebsd-current Wed Jul 17 12:28:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11631 for current-outgoing; Wed, 17 Jul 1996 12:28:10 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA11625; Wed, 17 Jul 1996 12:28:08 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id MAA00328; Wed, 17 Jul 1996 12:28:03 -0700 (PDT) Message-Id: <199607171928.MAA00328@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Jordan K. Hubbard" cc: freebsd-chat@freebsd.org, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of "Wed, 17 Jul 1996 12:02:32 PDT." <1073.837630152@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jul 1996 12:28:03 -0700 From: Amancio Hasty Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Jordan K. Hubbard" : > > Now, go price 3 copies of NT Server plus the 1000 user commercial pop > package you'll have to buy along with the relevant DNS, News and > SLIP/PPP software (also throw in NFS so that you can eventually share > filesystems with that SGI Challenge machine you've got your lustful > eyes on and will buy once you hit 500 users to take some of the load > off). See the total you're quoted. Suffer heart failure. Be revived Do you know how much the above setup would cost? Tnks, Amancio From owner-freebsd-current Wed Jul 17 12:42:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12543 for current-outgoing; Wed, 17 Jul 1996 12:42:58 -0700 (PDT) Received: from wireless.Stanford.EDU (wireless.Stanford.EDU [36.10.0.102]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA12503; Wed, 17 Jul 1996 12:42:49 -0700 (PDT) Received: from localhost (akyol@localhost) by wireless.Stanford.EDU (8.7.5/8.7.1) with ESMTP id MAA28449; Wed, 17 Jul 1996 12:42:46 -0700 (PDT) Message-Id: <199607171942.MAA28449@wireless.Stanford.EDU> X-Mailer: exmh version 1.6.7 5/3/96 To: freebsd-current@freebsd.org cc: freebsd-chat@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of "Wed, 17 Jul 1996 12:02:32 MST." <1073.837630152@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jul 1996 12:42:46 -0700 From: Bora Akyol Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > While I don't disagree with any of your major points, and agree that > NT is *definitely* something we should be afraid (very afraid) of, I > think you missed one important point about it which Microsoft will be > the last to mention in their sales hype: Cost. > > Task: Create a small ISP using 3 or 4 PCs which will provide web > service, POP email accounts, News, DNS, dial-in SLIP/PPP and general > routing. Say we're also projecting between 500-1000 users as our > target customer base within a 6 month timeframe (and, assuming we live > in an area where coverage is still somewhat spotty, that's not an > unrealistic expectation at all) so we need to make sure we can grow > into that without too much pain since we'll already be going insane > trying to get the billing set up, the tech support hotline staffed, > etc. The last thing we need is for our tech to run out of steam > halfway down the line. > > Now, go price 3 copies of NT Server plus the 1000 user commercial pop > package you'll have to buy along with the relevant DNS, News and > SLIP/PPP software (also throw in NFS so that you can eventually share > filesystems with that SGI Challenge machine you've got your lustful > eyes on and will buy once you hit 500 users to take some of the load > off). See the total you're quoted. Suffer heart failure. Be revived > by paramedics. Send $39.95 from your hospital bed to Walnut Creek > CDROM for *one* copy of FreeBSD and swear off Microsoft forever. :-) > > Seriously, NT looks attractive from a single-user standpoint, I'll > give it full marks for that, but once you try and put together even > half of the packages you get for free under UNIX to create a small ISP > or business server application, you're talking some serious bucks and, > from everything I've heard, you won't even get close to the > performance of a well-tuned *BSD box doing the same thing once you're > done. > > Eventually I suppose that Microsoft will catch on to this and/or the > free software community will provide some of the missing pieces, but > that doesn't help today's customers very much. > > Jordan > I agree with this, even as a single, technical user NT was not viable for me. I needed NFS, mail service, X windows, Tex/Latex/Xdvi. Here is the prices: 1_ NT student version 99.00 2. XServer+NFS = $400.00 3. Mail Server= DOn't know 4. Latex/Tex/Xdvi = Free Cost = 499.00 plus 100.00 for tolerating the .INI files, using \ instead of / probably. FreeBSD cost me nothing and came with all the stuff that I needed. Of course if you are a novice user, the learning curve for UNIX is much steeper than NT since we don't have graphical user interface. But hacking a tk interface should not be that hard. RedHat software has a good GUI for system management that pretty much does everything so it is possible. Bora From owner-freebsd-current Wed Jul 17 12:43:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12558 for current-outgoing; Wed, 17 Jul 1996 12:43:01 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA12521; Wed, 17 Jul 1996 12:42:53 -0700 (PDT) Message-Id: <199607171942.MAA12521@freefall.freebsd.org> To: Amancio Hasty cc: "Jordan K. Hubbard" , freebsd-chat@freebsd.org, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of "Wed, 17 Jul 1996 12:28:03 PDT." <199607171928.MAA00328@rah.star-gate.com> Date: Wed, 17 Jul 1996 12:42:53 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>From The Desk Of "Jordan K. Hubbard" : >> >> Now, go price 3 copies of NT Server plus the 1000 user commercial pop >> package you'll have to buy along with the relevant DNS, News and >> SLIP/PPP software (also throw in NFS so that you can eventually share >> filesystems with that SGI Challenge machine you've got your lustful >> eyes on and will buy once you hit 500 users to take some of the load >> off). See the total you're quoted. Suffer heart failure. Be revived > >Do you know how much the above setup would cost? > >Tnks, > Amancio It's actually not the important figure to look at. Initial hardware and software costs are a miniscule portion of the cost of deploying any system on this scale. If you can show that solution X takes less time to install, is easier to configure, is easier to upgrade, and requires minimal staff training time to use, (along with being robust and fast, etc) you'll get people to listen. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Jul 17 12:46:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12867 for current-outgoing; Wed, 17 Jul 1996 12:46:00 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA12862; Wed, 17 Jul 1996 12:45:57 -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 MAA01365; Wed, 17 Jul 1996 12:45:48 -0700 (PDT) To: Amancio Hasty cc: freebsd-chat@freebsd.org, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of "Wed, 17 Jul 1996 12:28:03 PDT." <199607171928.MAA00328@rah.star-gate.com> Date: Wed, 17 Jul 1996 12:45:47 -0700 Message-ID: <1363.837632747@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Now, go price 3 copies of NT Server plus the 1000 user commercial pop > > package you'll have to buy along with the relevant DNS, News and > > SLIP/PPP software (also throw in NFS so that you can eventually share > > filesystems with that SGI Challenge machine you've got your lustful > > eyes on and will buy once you hit 500 users to take some of the load > > off). See the total you're quoted. Suffer heart failure. Be revived > > Do you know how much the above setup would cost? With or without the SGI Challenge? :-) I've been told that the POP server is actually the most expensive component and, while I've never priced all of this stuff down to the last dime myself, I've been told that starting with $20,000 and diving into the NT ISP market will leave you enough to go for a McDonald's hamburger afterwards. If someone wanted to do an actual study on this, using the current crop of NT products (which has almost certainly been added to since I got this figure), it's be quite an interesting exercise. Any takers who are more familiar with the current state of the NT market than I? Jordan From owner-freebsd-current Wed Jul 17 13:47:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18772 for current-outgoing; Wed, 17 Jul 1996 13:47:33 -0700 (PDT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18758 for ; Wed, 17 Jul 1996 13:47:26 -0700 (PDT) Received: (from uucp@localhost) by frmug.org (8.6.8/8.6.9) with UUCP id WAA10837 for current@FreeBSD.org; Wed, 17 Jul 1996 22:47:12 +0200 Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.7.5/8.7.3/xp11-uucp-1.1) with ESMTP id VAA00247 for ; Wed, 17 Jul 1996 21:30:42 +0200 (MET DST) Message-Id: <199607171930.VAA00247@xp11.frmug.org> To: current@FreeBSD.org Subject: ugly output of /etc/rc Date: Wed, 17 Jul 1996 21:30:40 +0200 From: "Philippe Charnier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, With the last change of /etc/rc, the ouput on console is ugly a little. This one is nicer for me. Index: rc =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/etc/rc,v retrieving revision 1.94 diff -u -r1.94 rc --- rc 1996/07/13 17:27:39 1.94 +++ rc 1996/07/17 19:21:38 @@ -150,7 +150,7 @@ # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. if [ "X${savecore}" = X"YES" -a -d /var/crash ]; then - echo -n checking for core dump... + echo -n 'checking for core dump... ' savecore /var/crash fi @@ -294,6 +294,8 @@ echo -n ' printer'; lpd fi +echo '.' + # Make shared lib searching a little faster. Leave /usr/lib first if you # add your own entries or you may come to grief. if [ -x /sbin/ldconfig ]; then @@ -308,10 +310,8 @@ # $sendmail_flags is imported from /etc/sysconfig; # if $sendmail_flags is something other than NO, sendmail is run. if [ "X${sendmail_flags}" != X"NO" -a -r /etc/sendmail.cf ]; then - echo -n ' sendmail'; /usr/sbin/sendmail ${sendmail_flags} + echo 'starting sendmail.'; /usr/sbin/sendmail ${sendmail_flags} fi - -echo '.' # configure implementation specific stuff arch=`uname -m` ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-current Wed Jul 17 14:20:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21209 for current-outgoing; Wed, 17 Jul 1996 14:20:29 -0700 (PDT) Received: from neworder.cc.uky.edu (neworder.cc.uky.edu [128.163.18.198]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA21201; Wed, 17 Jul 1996 14:20:25 -0700 (PDT) Received: (from soward@localhost) by neworder.cc.uky.edu (8.7/Soward0.1) id RAA07178; Wed, 17 Jul 1996 17:20:36 -0500 (GMT-0500) Message-Id: <199607172220.RAA07178@neworder.cc.uky.edu> MIME-Version: 1.0 (NeXT Mail 4.0 v141) Content-Type: text/plain Received: by NeXT.Mailer (1.141) From: John Soward Date: Wed, 17 Jul 96 17:20:35 -0500 To: "Justin T. Gibbs" Subject: Re: Opinions? cc: Amancio Hasty , "Jordan K. Hubbard" , freebsd-chat@FreeBSD.ORG, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@FreeBSD.ORG Reply-To: soward@service1.uky.edu References: <199607171942.MAA12521@freefall.freebsd.org> Organization: University of Kentucky Technical Services X-URL: "http://neworder.cc.uky.edu/" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It's actually not the important figure to look at. Initial hardware and > software costs are a miniscule portion of the cost of deploying any system > on this scale. If you can show that solution X takes less time to install, > is easier to configure, is easier to upgrade, and requires minimal staff > training time to use, (along with being robust and fast, etc) you'll get > people to listen. > Here, Here. I deployed a POP server serving > 25,000 users, pusing well over 1G of mail/week...I hardly touch it now, I'd say < 5 hours/week and most of that is not nec needed enhancements. I fiddled with a toy one on NT with just a few dummy users, and spent more time than that with it...Aside from the POP and other mail related stuff, I'd hate to have to manage 25,000+ users under an NT system...Probably 100 users a day are added/deleted/changed, all handled elsewhere on a Sybase database and processed with a bunch of Perl scripts.. PS: I didn't use FreeBSD, but HPUX, however every indication is that a P-Pro with similar disk/RAM/Fddi would perform just as well as the K200 I'm using. --- John Soward JpS Systems Programmer 'The Midnight sun will burn you up.' University of Kentucky (NeXT and MIME mail OK) -R. Smith :::I'm not speaking for UK. I may not even be speaking for myself::: From owner-freebsd-current Wed Jul 17 16:48:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA01947 for current-outgoing; Wed, 17 Jul 1996 16:48:51 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca9-15.ix.netcom.com [204.31.231.111]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA01940; Wed, 17 Jul 1996 16:48:48 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id QAA26355; Wed, 17 Jul 1996 16:48:38 -0700 (PDT) Date: Wed, 17 Jul 1996 16:48:38 -0700 (PDT) Message-Id: <199607172348.QAA26355@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: ache@nagual.ru, jkh@freebsd.org, current@freebsd.org In-reply-to: <23972.837603688@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: various 'fetch' errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Uh, no. Remind me what I promised to implement again? :-) You said you'll add a flag to make fetch not preserve the timestamp of files (like it used to). Oh, and I remember you also said you'll implement a "dummy mode" that will let fetch do all the jobs of the ports manager while he's sleeping. Satoshi From owner-freebsd-current Wed Jul 17 17:19:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04112 for current-outgoing; Wed, 17 Jul 1996 17:19:36 -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 RAA04107; Wed, 17 Jul 1996 17:19:33 -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 RAA00786; Wed, 17 Jul 1996 17:19:23 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: ache@nagual.ru, jkh@freebsd.org, current@freebsd.org Subject: Re: various 'fetch' errors In-reply-to: Your message of "Wed, 17 Jul 1996 16:48:38 PDT." <199607172348.QAA26355@silvia.HIP.Berkeley.EDU> Date: Wed, 17 Jul 1996 17:19:23 -0700 Message-ID: <784.837649163@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You said you'll add a flag to make fetch not preserve the timestamp of > files (like it used to). Done. > Oh, and I remember you also said you'll implement a "dummy mode" that > will let fetch do all the jobs of the ports manager while he's > sleeping. Ooooh, that's a slippery slope, Satoshi - pretty soon it's doing the job of the ports manager while he's awake, too, and doing it better and faster. Before you know it, you've been replaced by a button. :-) Jordan From owner-freebsd-current Wed Jul 17 18:09:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05705 for current-outgoing; Wed, 17 Jul 1996 18:09:33 -0700 (PDT) Received: from saba.kuentos.guam.net (root@saba.kuentos.guam.net [198.81.233.14]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA05700; Wed, 17 Jul 1996 18:09:30 -0700 (PDT) Received: by saba.kuentos.guam.net (Smail3.1.29.1 #9) id m0ughaT-002F0FC; Thu, 18 Jul 96 11:09 GST Date: Thu, 18 Jul 1996 11:09:05 +1000 (GST) From: Meltedice To: Amancio Hasty cc: "Jordan K. Hubbard" , freebsd-chat@FreeBSD.ORG, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@FreeBSD.ORG Subject: Re: Opinions? In-Reply-To: <199607171928.MAA00328@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Jul 1996, Amancio Hasty wrote: > >From The Desk Of "Jordan K. Hubbard" : > > > > Now, go price 3 copies of NT Server plus the 1000 user commercial pop > > package you'll have to buy along with the relevant DNS, News and > > SLIP/PPP software (also throw in NFS so that you can eventually share > > filesystems with that SGI Challenge machine you've got your lustful > > eyes on and will buy once you hit 500 users to take some of the load > > off). See the total you're quoted. Suffer heart failure. Be revived > > Do you know how much the above setup would cost? > > Tnks, > Amancio > I don't know the exact cost, but for the $40.00 you send Walnut Creek, your best choice would be FreeBSD, that is undisbutable. And if you are serious about setting up an ISP and MAKING MONEY, then you would be aware of the cost and invest your time in FreeBSD and not your money in NT. Leave all of the "nice pretty" point and click to your users PC's and Mac's at home. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ : _ | | /"\ | " I am the Gecko! " | /o o\ | | _\/ \ / \/_ | meltedice@kuentos.guam.net | \\._/ /_.// | | `--, ,----' | http://www.guam.net/home/bhshaw2 | / / | | ^ / \ | KUENTOS CAFE... An IFORMS based Chat | /| ( ) | | / | ,__\ /__, | telnet buri.kuentos.guam.net 3000 | \ \ _//---, ,--\\_ | | \ \ /\ / / /\ | "Come on in and visit me" | \ \.___,/ / | | \.______,/ | | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-current Wed Jul 17 18:18:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06217 for current-outgoing; Wed, 17 Jul 1996 18:18:28 -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 SAA06209; Wed, 17 Jul 1996 18:18:26 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA06059; Wed, 17 Jul 1996 18:17:04 -0700 From: Terry Lambert Message-Id: <199607180117.SAA06059@phaeton.artisoft.com> Subject: Re: various 'fetch' errors To: asami@cs.berkeley.edu (Satoshi Asami) Date: Wed, 17 Jul 1996 18:17:03 -0700 (MST) Cc: jkh@time.cdrom.com, ache@nagual.ru, jkh@freebsd.org, current@freebsd.org In-Reply-To: <199607172348.QAA26355@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Jul 17, 96 04:48:38 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 > * Uh, no. Remind me what I promised to implement again? :-) > > You said you'll add a flag to make fetch not preserve the timestamp of > files (like it used to). > > Oh, and I remember you also said you'll implement a "dummy mode" that > will let fetch do all the jobs of the ports manager while he's > sleeping. And VM86(). I think I distinctly heard VM86(). And a 1MB footprint. Yeah, yeah, THAT'S the ticket! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 17 18:22:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06450 for current-outgoing; Wed, 17 Jul 1996 18:22:13 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06442; Wed, 17 Jul 1996 18:22:11 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id SAA02091; Wed, 17 Jul 1996 18:16:02 -0700 (PDT) Message-Id: <199607180116.SAA02091@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: Meltedice cc: "Jordan K. Hubbard" , freebsd-chat@FreeBSD.ORG, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@FreeBSD.ORG Subject: Re: Opinions? In-reply-to: Your message of "Thu, 18 Jul 1996 11:09:05 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jul 1996 18:16:02 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Meltedice : > I don't know the exact cost, but for the $40.00 you send Walnut > Creek, your best choice would be FreeBSD, that is undisbutable. And if > you are serious about setting up an ISP and MAKING MONEY, then you would > be aware of the cost and invest your time in FreeBSD and not your > money in NT. Leave all of the "nice pretty" point and click to your users > PC's and Mac's at home. > We are not debating how much FreeBSD costs we know that. The question is how much does it cost to setup an NT ISP server? ISP server having NFS, POP Mail, NFS, http server, ftp... all the nice basic things we take for granted on a Unix box. Oh, in my favorited, mrouted 8) BTW: I am FreeBSD hacker... Amancio From owner-freebsd-current Wed Jul 17 18:31:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06821 for current-outgoing; Wed, 17 Jul 1996 18:31:33 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06815 for ; Wed, 17 Jul 1996 18:31:30 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id VAA26675; Wed, 17 Jul 1996 21:29:59 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: current@freebsd.org From: "Gary Palmer" Subject: Re: various 'fetch' errors In-reply-to: Your message of "Wed, 17 Jul 1996 18:17:03 PDT." <199607180117.SAA06059@phaeton.artisoft.com> Date: Wed, 17 Jul 1996 21:29:59 -0400 Message-ID: <26671.837653399@orion.webspan.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote in message ID <199607180117.SAA06059@phaeton.artisoft.com>: > And VM86(). I think I distinctly heard VM86(). > > And a 1MB footprint. > > Yeah, yeah, THAT'S the ticket! You forgot binary compatability with VMS :-) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Wed Jul 17 19:42:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA10997 for current-outgoing; Wed, 17 Jul 1996 19:42:17 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-170.ut.nl.ibm.net [139.92.42.170]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA10991 for ; Wed, 17 Jul 1996 19:42:09 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id CAA19608; Thu, 18 Jul 1996 02:31:09 +0200 (MET DST) Date: Thu, 18 Jul 1996 02:31:09 +0200 (MET DST) Message-Id: <199607180031.CAA19608@vector.jhs.no_domain> To: current@freebsd.org Subject: cvs-cur.2229.gz is 723 K bytes, is another monster lurking ? From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (later) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems when tag RELENG_2_1_5_RELEASE:1.1.1.1 was added, a monster cvs-cur.2229.gz of 723 K bytes was generated. Perhaps when the new fixed release is tagged it'll create a 2nd monster, again consuming modems & local ctm application time ... Forewarned is forarmed, or perhaps just `fore-scared' :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Jul 17 20:00:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12066 for current-outgoing; Wed, 17 Jul 1996 20:00:53 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA12039; Wed, 17 Jul 1996 20:00:38 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id GAA10618; Fri, 19 Jul 1996 06:10:59 -0400 (EDT) Date: Fri, 19 Jul 1996 06:10:55 -0400 (EDT) From: "Charles C. Figueiredo" To: current@freebsd.org cc: hackers@freebsd.org Subject: IP Masquerading Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there an IP Masquerading module/kernel option/ or daemon I could run in FreeBSD that would provide a service transparent proxy to another machine behind it. I don't want to have to grab CERN httpd, and steal modules out of fwtk, and all those hassles, is there a seemeless way to do it. I only have one IP. I don't want to resort to running Linux ;-) Charles ------------------------------------------------------------------------------ Charles C. Figueiredo CCF13 marxx@doomsday.org ------------------------------------------------------------------------------ From owner-freebsd-current Wed Jul 17 20:04:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12245 for current-outgoing; Wed, 17 Jul 1996 20:04:20 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA12239 for ; Wed, 17 Jul 1996 20:04:18 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Wed, 17 Jul 1996 22:04:07 -0600 Message-ID: Date: 17 Jul 1996 22:03:40 -0500 From: "Richard Wackerbarth" Subject: Re: cvs-cur.2229.gz is 723 K bytes, is another monster lurking ? To: "current@freebsd.org" , "Julian H. Stacey" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It seems when tag > RELENG_2_1_5_RELEASE:1.1.1.1 > was added, a monster > cvs-cur.2229.gz > of 723 K bytes was generated. > > Perhaps when the new fixed release is tagged it'll create a 2nd monster, > again consuming modems & local ctm application time > ... Forewarned is forarmed, or perhaps just `fore-scared' :-) Actually not. The new update simply modifies a few files. It does not retag routines that did not change. -- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Wed Jul 17 20:10:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12571 for current-outgoing; Wed, 17 Jul 1996 20:10:13 -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 UAA12564; Wed, 17 Jul 1996 20:10:10 -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 UAA01231; Wed, 17 Jul 1996 20:10:07 -0700 (PDT) To: "Julian H. Stacey" cc: current@FreeBSD.org Subject: Re: cvs-cur.2229.gz is 723 K bytes, is another monster lurking ? In-reply-to: Your message of "Thu, 18 Jul 1996 02:31:09 +0200." <199607180031.CAA19608@vector.jhs.no_domain> Date: Wed, 17 Jul 1996 20:10:07 -0700 Message-ID: <1229.837659407@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Perhaps when the new fixed release is tagged it'll create a 2nd monster, Nope. Only a few tags were slid forward - we're not so silly as to tag the entire tree again just because 4 or 5 files changed! :-) Jordan From owner-freebsd-current Wed Jul 17 20:15:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12847 for current-outgoing; Wed, 17 Jul 1996 20:15:25 -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 UAA12842 for ; Wed, 17 Jul 1996 20:15:19 -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 FAA12331 for ; Thu, 18 Jul 1996 05:15:16 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id FAA18543 for freebsd-current@FreeBSD.ORG; Thu, 18 Jul 1996 05:03:48 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.7.5/8.7.3) id VAA08334; Wed, 17 Jul 1996 21:44:46 +0200 (MET DST) To: freebsd-current@FreeBSD.ORG Subject: ISDN support? From: Peter Mutsaers Date: 17 Jul 1996 21:44:45 +0200 Message-ID: <87pw5u1x76.fsf@localhost.xs4all.nl> Lines: 11 X-Mailer: Gnus v5.2.26/Emacs 19.31 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, what ISDN support (which ISDN router/modem) exists for FreeBSD? The section in the FAQ on ISDN is still blank. (I hope that doesn't mean that no such support really exists; I'll buy a Seles ISDN board soon and must use it under Unix (FreeBSD or Linux)). -- ______________________________________________________________________ Peter Mutsaers | Abcoude (Utrecht), | "Memento Mori" plm@xs4all.nl | the Netherlands | From owner-freebsd-current Wed Jul 17 22:02:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA23225 for current-outgoing; Wed, 17 Jul 1996 22:02:55 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA23214; Wed, 17 Jul 1996 22:02:49 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAA09210; Wed, 17 Jul 1996 22:02:38 -0700 (PDT) Message-Id: <199607180502.WAA09210@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: freebsd-chat@freebsd.org, dwhite@resnet.uoregon.edu, Domingo Siliceo , freebsd-current@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of Wed, 17 Jul 96 12:02:32 -0700. <1073.837630152@time.cdrom.com> Date: Wed, 17 Jul 1996 22:02:36 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> learn all the quirkiness of Unix. NT and OS/2 are just better >> solutions than Unix for many of these people. And NT is a better >> server product in so many ways than OS/2. Plus, NT is a better >> business "workstation" OS than Unix because of all the business >> applications it runs. >While I don't disagree with any of your major points, and agree that >NT is *definitely* something we should be afraid (very afraid) of, I >think you missed one important point about it which Microsoft will be >the last to mention in their sales hype: Cost. Actually, corporate cost of ownership is measured in some very strange ways that can sometimes make some really odd choices the least expensive. Support costs alone can make something free cost a lot more than something "expensive". Not speaking of anything specific here, just in general. >Task: Create a small ISP using 3 or 4 PCs which will provide web >service, POP email accounts, News, DNS, dial-in SLIP/PPP and general >routing. Say we're also projecting between 500-1000 users as our [...] I can see we're already going off in different directions here. I was *not* speaking of a server OS specifically for an ISP. That is a very small share of the market server OS's are purchased for. The original poster said he was "still trying to understand why people think they have to run NT." He also added "there are other options, like FreeBSD and OS/2," which leads me to believe he indeed intended to include markets not traditionally Unix-like. I was speaking of the broader market in general. Corporations that do a lot of "office work". Where they need to do a lot of application serving and sharing, print sharing, file sharing, secure access control to all that, an easy admin model, etc. Maybe deal out a few dial-in lines for their sales people out in the fields with laptops. >Now, go price 3 copies of NT Server plus the 1000 user commercial pop [...] >off). See the total you're quoted. Suffer heart failure. Be revived >by paramedics. Send $39.95 from your hospital bed to Walnut Creek >CDROM for *one* copy of FreeBSD and swear off Microsoft forever. :-) I agree completely. A small two or three-man-shop ISP is the very definition of a good application for FreeBSD or NetBSD. Of course, *we* know that they are even a great candidate for *any* size ISP. though some are more skeptical. I couldn't agree more. There isn't a market better suited for a solid free Unix, IMHO. Especially when they have a networking code base as excellent as the free BSDs. There are lots of other related areas where a free Unix, or even a commercial Unix, might be the best choice. Maybe some kind of network provider. Maybe a heavy-hit monster database server (although Microsoft has been getting lots of good press on their database performance). Maybe a huge simulation engine. Maybe just a monster compute server. However, I wasn't talking specifically about ISPs. I agree with you on ISPs. I was speaking of the entire server OS market as a whole. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Wed Jul 17 22:11:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA23789 for current-outgoing; Wed, 17 Jul 1996 22:11:59 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA23760; Wed, 17 Jul 1996 22:11:53 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAA09274; Wed, 17 Jul 1996 22:11:44 -0700 (PDT) Message-Id: <199607180511.WAA09274@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Bora Akyol cc: freebsd-current@freebsd.org, freebsd-chat@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of Wed, 17 Jul 96 12:42:46 -0700. <199607171942.MAA28449@wireless.Stanford.EDU> Date: Wed, 17 Jul 1996 22:11:43 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I agree with this, even as a single, technical user NT was not viable for me. >I needed NFS, mail service, X windows, Tex/Latex/Xdvi. [...] >FreeBSD cost me nothing and came with all the stuff that I needed. Well, *OBVIOUSLY* NT wasn't the right choice for you. I don't know why you even proposed it as an option. If you specifically spec'd a Unix system, how can anything else fit the spec. If I specifically asked for a system that runs Windows 95 software, can be remotely administered with the same UI as the rest of my MS BackOffice server apps, and is multi-processor and multi- threaded, would you try to sell me FreeBSD + XFree86? Of course not. That would be absurd. NetBSD served me for several years in exactly the same way you just described for yourself, above. But if someone came to me with the list I just presented, I wouldn't try to get them to run NetBSD. Of course, I'd probably work on them and try to get them to accept that The Unix Way was better. :-) But that would be irrespective of what they originally asked for. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Wed Jul 17 22:48:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA27476 for current-outgoing; Wed, 17 Jul 1996 22:48:50 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA27463; Wed, 17 Jul 1996 22:48:47 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAA09514; Wed, 17 Jul 1996 22:48:23 -0700 (PDT) Message-Id: <199607180548.WAA09514@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: asami@cs.berkeley.edu (Satoshi Asami), ache@nagual.ru, jkh@freebsd.org, current@freebsd.org Subject: Re: various 'fetch' errors In-reply-to: Your message of Wed, 17 Jul 96 17:19:23 -0700. <784.837649163@time.cdrom.com> Date: Wed, 17 Jul 1996 22:48:22 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Oh, and I remember you also said you'll implement a "dummy mode" that >> will let fetch do all the jobs of the ports manager while he's >> sleeping. >Ooooh, that's a slippery slope, Satoshi - pretty soon it's doing the >job of the ports manager while he's awake, too, and doing it better >and faster. Before you know it, you've been replaced by a button. :-) I think that's actually an internal Microsoft slogan somewhere... ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Wed Jul 17 23:23:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA29658 for current-outgoing; Wed, 17 Jul 1996 23:23:52 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA29627; Wed, 17 Jul 1996 23:23:44 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id XAA09725; Wed, 17 Jul 1996 23:23:41 -0700 (PDT) Message-Id: <199607180623.XAA09725@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: freebsd-current@freebsd.org, freebsd-chat@freebsd.org cc: Matthew Jason White Subject: Re: Opinions? Date: Wed, 17 Jul 1996 23:23:41 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk He sent me a followup letter lamenting that he forgot to include the lists in his response. Being the kind person that I am, I'm forwarding this on. I had hoped the thread wouldn't continue on freebsd-current, but unfortunately, it did. So I'm including that group. I'll add that I pretty much agree with everything he says. ------- Forwarded Message Date: Thu, 18 Jul 96 02:08:36 -0400 From: Matthew Jason White To: "Michael L. VanLoon -- HeadCandy.com" Subject: Re: Opinions? Excerpts from internet.computing.freebsd-current: 17-Jul-96 Re: Opinions? by M. HeadCandy.com@HeadCan > There are lots of other related areas where a free Unix, or even a > commercial Unix, might be the best choice. Maybe some kind of network > provider. Maybe a heavy-hit monster database server (although > Microsoft has been getting lots of good press on their database > performance). Maybe a huge simulation engine. Maybe just a monster > compute server. Don't forget research boxes. Most research I know of uses software running on Unix boxes of some sort. There are a number of reasons for this ranging from simple tradition to the expressiveness of Unix compared to other OSes. When you're writing a reference version of a program, you don't want to be burdened with also writing a GUI for it at the same time, which NT all but forces you to do (you *can* associate a console with a program, but this is not the default). Further, I think it's also safe to assume that Unix will remain a favorite among hackers everywhere just because it behaves the way we expect an OS to behave and emphasizes the things that a hacker generally wants emphasized. There's something about eighteen command pipelines that appeal to almost every hacker I know. Obscure command lines also seem aestheticly pleasing at times. So as long as hackers are valued people in research and industry, Unix will most likely have a secure home. I think this is an important thing to consider. As we expand FreeBSD (and NetBSD and Linux and OpenBSD...), we have to consider who our audience is and who we want it to be. I personally feel that it's fine to start to encroach on Win95 and NT territory by developing GUI apps and admin tools, as long as we don't alienate our history in the process. Hmmpf...you can tell that it's late 'cause I'm rambling on. I suppose I'll be happy with FreeBSD as long as I can pull up an xterm to do stuff in and I never have to prefix a pathname 'c:'. - -Matt - ----- Matt White Email: mwhite+@cmu.edu http://www.cs.cmu.edu/afs/cs/user/mwhite/www/ ------- End of Forwarded Message From owner-freebsd-current Thu Jul 18 03:13:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA09612 for current-outgoing; Thu, 18 Jul 1996 03:13:14 -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 DAA09595 for ; Thu, 18 Jul 1996 03:12:53 -0700 (PDT) Received: (from ernie@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id UAA02876 for freebsd-current@freebsd.org; Thu, 18 Jul 1996 20:12:03 +1000 (EST) From: Ernie Elu Message-Id: <199607181012.UAA02876@spooky.eis.net.au> Subject: Make world stops on hierarchy To: freebsd-current@freebsd.org Date: Thu, 18 Jul 1996 20:12:02 +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 poster this message to the list a couple of days ago but it did not appear for some reason so I will ask the question again. For a bit over a week I have been getting the following error when I do a make world: spooky.ROOT # make world -------------------------------------------------------------- Making hierarchy -------------------------------------------------------------- cd /usr/src/etc && make distrib-dirs make: don't know how to make distrib-dirs. Stop *** Error code 2 Stop. It only seems to be make hierarchy that is causing it I can run the other make routines seperately o.k. I have recompiled make, run the current supfile that picks up the contrib dir etc., done a make mk, bootstrap etc. but no luck so far. I searched through the freebsd-current mail list archives on www.freebsd.org on the key word hierarchy and then on distrib-dirs but could not find any mention of this problem. I presume it is due to some change I have missed. If it were a bug the list would have been flooded by after a week. Can some one tell me the missing step to get back in sync? - Ernie. From owner-freebsd-current Thu Jul 18 03:59:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11081 for current-outgoing; Thu, 18 Jul 1996 03:59:37 -0700 (PDT) Received: from meno.uchicago.edu (meno.uchicago.edu [128.135.21.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA11073 for ; Thu, 18 Jul 1996 03:59:32 -0700 (PDT) Received: from meno.uchicago.edu (localhost [127.0.0.1]) by meno.uchicago.edu (8.7.5/8.7.3) with ESMTP id GAA22703 for ; Thu, 18 Jul 1996 06:01:43 -0500 (CDT) Message-Id: <199607181101.GAA22703@meno.uchicago.edu> To: current@freebsd.org Subject: netatalk MIME-Version: 1.0 Content-Type: text/plain; charset="x-unknown" Content-ID: <22699.837687702.1@meno.uchicago.edu> Content-Transfer-Encoding: quoted-printable Date: Thu, 18 Jul 1996 06:01:43 -0500 From: steve farrell Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk anyone know the status of netatalk in the -current kernel? i tried enabling options NETATALK and i got a patched version of netatalk compiled, but when i try to run it, i get: starting appletalk daemons:=CF: Device not configured despite the fact that something appears to be working since this pops up after netstat -r: ATALK: Destination Gateway Flags Refs Use Netif Ex= pire as per the instructions that came with the patch (it was against 1.3.3b2/for 2.0.5 kernel), i tried enabling CCITT and LPC, but -current doesn't seem to finish compiling with these enabled. (problems with if_ethersubr.c, or similar). is anyone still working on this, or just holding out for netatalk 1.4? (for which umich has promised freebsd support). thanks, --steve farrell From owner-freebsd-current Thu Jul 18 04:27:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA12959 for current-outgoing; Thu, 18 Jul 1996 04:27: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 EAA12954 for ; Thu, 18 Jul 1996 04:27:54 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA17476; Thu, 18 Jul 1996 12:41:19 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA20525; Thu, 18 Jul 1996 12:41:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA04574; Thu, 18 Jul 1996 11:19:55 +0200 (MET DST) From: J Wunsch Message-Id: <199607180919.LAA04574@uriah.heep.sax.de> Subject: Re: ISDN support? To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Thu, 18 Jul 1996 11:19:55 +0200 (MET DST) Cc: plm@xs4all.nl (Peter Mutsaers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <87pw5u1x76.fsf@localhost.xs4all.nl> from Peter Mutsaers at "Jul 17, 96 09:44:45 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Peter Mutsaers wrote: > what ISDN support (which ISDN router/modem) exists for FreeBSD? The > section in the FAQ on ISDN is still blank. (I hope that doesn't mean > that no such support really exists; I'll buy a Seles ISDN board soon > and must use it under Unix (FreeBSD or Linux)). Well, you're from .nl, so under the assumption that your local telco runs the E-DSS1 switch protocol, the BISDN package, together with the relatively cheap `Teles' boards might be relevant to you. It is about to be integrated into 2.2-current soon, and it's also available as a standalone package (by Hellmuth Michaelis and a few other contributors) for 2.1R. -- 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 18 09:03:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28809 for current-outgoing; Thu, 18 Jul 1996 09:03:36 -0700 (PDT) Received: from main.gbdata.com (dial172.phoenix.net [205.241.121.186]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA28782 for ; Thu, 18 Jul 1996 09:03:28 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.7.5/8.6.9) id LAA14560 for freebsd-current@freebsd.org; Thu, 18 Jul 1996 11:04:10 -0500 (CDT) From: Gary Clark II Message-Id: <199607181604.LAA14560@main.gbdata.com> Subject: kernel ppp and default route To: freebsd-current@freebsd.org Date: Thu, 18 Jul 1996 11:04:09 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all, I just upgraded to current a couple of days ago and now have run into a strange problem. My PPP setup is supposed to install a default route for me and did so before the upgrade. Now it will install one, but after a very short while the default will vanish and I have to install on manualy. Any ideas? thanks Gary -- Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company gclarkii@GBData.COM | Member of the FreeBSD Doc Team Providing Internet and ISP startups mail info@GBData.COM for information FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/freebsd-faq.ascii From owner-freebsd-current Thu Jul 18 09:24:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29731 for current-outgoing; Thu, 18 Jul 1996 09:24:32 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29726 for ; Thu, 18 Jul 1996 09:24:29 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id RAA07075 for ; Thu, 18 Jul 1996 17:30:13 +0100 (BST) Date: Thu, 18 Jul 1996 17:30:13 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Help on setting up yp/nis Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could someone please help me, what do I need to do to make one machine a yp server and then have the other bsd machines use passwd database from the server? Ive got the ypserver running and done ypbind on the client but when I telnet to the client and try to log in under a user name from the server it just doesn't find the user??? Thanks in Advance. Regards, Trefor S. From owner-freebsd-current Thu Jul 18 09:24:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29755 for current-outgoing; Thu, 18 Jul 1996 09:24:44 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29747; Thu, 18 Jul 1996 09:24:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id KAA00775; Thu, 18 Jul 1996 10:22:59 -0600 (MDT) Message-Id: <199607181622.KAA00775@rover.village.org> To: Nate Williams Subject: Re: Cause of APM_DSVALUE_BUG found (but not completely fixed yet) Cc: freebsd-mobile@freebsd.org, current@freebsd.org, davidg@freebsd.org In-reply-to: Your message of Mon, 15 Jul 1996 23:57:46 MDT Date: Thu, 18 Jul 1996 10:22:58 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : + biosbasemem = bootinfo.bi_basemem; : + biosextmem = bootinfo.bi_extmem; Hmmm. The linux folks are running into machines that this would be bad for. Evidentally, they claim, a nontrivial number of machines will cap the returned value at 16M of memory. It might be best to do this as an option. Warner From owner-freebsd-current Thu Jul 18 09:31:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00442 for current-outgoing; Thu, 18 Jul 1996 09:31:57 -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 JAA00436; Thu, 18 Jul 1996 09:31:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id KAA00809; Thu, 18 Jul 1996 10:31:51 -0600 (MDT) Message-Id: <199607181631.KAA00809@rover.village.org> To: "Gary Palmer" Subject: Re: various 'fetch' errors Cc: current@freebsd.org In-reply-to: Your message of Wed, 17 Jul 1996 21:29:59 EDT Date: Thu, 18 Jul 1996 10:31:50 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : You forgot binary compatability with VMS : : :-) Hmmm, if you look at the message that I just sent, you might notice a resemblance between it and the BATCH system on VMS. :-) Warner From owner-freebsd-current Thu Jul 18 09:33:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00564 for current-outgoing; Thu, 18 Jul 1996 09:33:04 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA00559; Thu, 18 Jul 1996 09:33:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id KAA00797; Thu, 18 Jul 1996 10:30:51 -0600 (MDT) Message-Id: <199607181630.KAA00797@rover.village.org> To: "Jordan K. Hubbard" Subject: Re: various 'fetch' errors Cc: asami@cs.berkeley.edu (Satoshi Asami), ache@nagual.ru, jkh@freebsd.org, current@freebsd.org In-reply-to: Your message of Wed, 17 Jul 1996 17:19:23 PDT Date: Thu, 18 Jul 1996 10:30:51 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : > Oh, and I remember you also said you'll implement a "dummy mode" that : > will let fetch do all the jobs of the ports manager while he's : > sleeping. : : Ooooh, that's a slippery slope, Satoshi - pretty soon it's doing the : job of the ports manager while he's awake, too, and doing it better : and faster. Before you know it, you've been replaced by a button. :-) Heck, I'd be happy with a lpr-like interface to fetch. If there was a fetchd running in the background, and I said "fetch --background ftp://ftp.x.org/pub/R6.1/tars/xc-1.tar.gz --after tomorrow" it would queue the file for fetching and let me knwo when it is done. That way I could queue up 20-30 things to get and then go to sleep. I've wanted this feature in an FTP program for a long time and have *NEVER* seen one with it.[*] Warner [*] Well, sort of doing some sort of at kludge. I want it automatic! From owner-freebsd-current Thu Jul 18 09:40:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA01009 for current-outgoing; Thu, 18 Jul 1996 09:40:03 -0700 (PDT) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA00759 for ; Thu, 18 Jul 1996 09:37:06 -0700 (PDT) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.5/8.6.4) with ESMTP id TAA07815; Thu, 18 Jul 1996 19:36:21 +0300 (EET DST) Received: (hsu@localhost) by katiska.clinet.fi (8.7.5/8.6.4) id TAA21248; Thu, 18 Jul 1996 19:36:20 +0300 (EET DST) Date: Thu, 18 Jul 1996 19:36:20 +0300 (EET DST) Message-Id: <199607181636.TAA21248@katiska.clinet.fi> From: Heikki Suonsivu To: davidg@root.com Cc: Heikki Suonsivu , freebsd-current@freebsd.org Subject: Re: vm work helps In-Reply-To: <199607171420.HAA10162@root.com> References: <199607171053.NAA12835@cantina.clinet.fi> <199607171420.HAA10162@root.com> Organization: Clinet Ltd, Espoo, Finland Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > problems with, and now it appears that the problems were caused by defective > hardware all along...but hey, at least we fixed a bunch of bugs along the way > to discovering this. :-) Apparently you hit one of mine. > >have still had one panic but I have 7 days of uptime on our news server, > >which, sadly, is an all-time record for us running FreeBSD 2 on a full-feed > >news server. I will see how it goes for couple of weeks more. > > ...I'm interested in hearing about the panic. I did not get a dump, short of space on /var, it just had rebooted. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121 From owner-freebsd-current Thu Jul 18 10:10:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03003 for current-outgoing; Thu, 18 Jul 1996 10:10:30 -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 KAA02998 for ; Thu, 18 Jul 1996 10:10:27 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id MAA00332; Thu, 18 Jul 1996 12:09:26 -0500 (EST) From: John Dyson Message-Id: <199607181709.MAA00332@dyson.iquest.net> Subject: Re: vm work helps To: hsu@clinet.fi (Heikki Suonsivu) Date: Thu, 18 Jul 1996 12:09:26 -0500 (EST) Cc: davidg@Root.COM, hsu@clinet.fi, freebsd-current@freebsd.org In-Reply-To: <199607181636.TAA21248@katiska.clinet.fi> from "Heikki Suonsivu" at Jul 18, 96 07:36:20 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 > > >> >have still had one panic but I have 7 days of uptime on our news server, >> >which, sadly, is an all-time record for us running FreeBSD 2 on a full-feed >> >news server. I will see how it goes for couple of weeks more. >> >> ...I'm interested in hearing about the panic. > > I did not get a dump, short of space on /var, it just had rebooted. > Chiming in here: David, do you think that this could be a kernel stack space problem? John From owner-freebsd-current Thu Jul 18 10:51:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05294 for current-outgoing; Thu, 18 Jul 1996 10:51:38 -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 KAA05289 for ; Thu, 18 Jul 1996 10:51:34 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA14490; Thu, 18 Jul 1996 13:47:00 -0400 From: Bill Paul Message-Id: <199607181747.NAA14490@skynet.ctr.columbia.edu> Subject: Re: Help on setting up yp/nis To: dev@fgate.flevel.co.uk (Developer) Date: Thu, 18 Jul 1996 13:46:59 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: from "Developer" at Jul 18, 96 05:30:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Developer had to walk into mine and say: > Could someone please help me, what do I need to do to make one machine a > yp server and then have the other bsd machines use passwd database from > the server? > > Ive got the ypserver running and done ypbind on the client but when I > telnet to the client and try to log in under a user name from the server > it just doesn't find the user??? For the umpity-umpth time: read the passwd(5) man page. (That's passwd(5), not passwd(1); 'man 5 passwd'.) It explains quite clearly how to set up a client to use the NIS passwd maps (and how not to do it). If, after reading this man page, you still have specific questions, come back and ask them and I'll try to help. -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 Thu Jul 18 10:53:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05382 for current-outgoing; Thu, 18 Jul 1996 10:53:06 -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 KAA05377 for ; Thu, 18 Jul 1996 10:53:03 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id DAA01101 Fri, 19 Jul 1996 03:52:29 +1000 (EST) From: michael butler Message-Id: <199607181752.DAA01101@walkabout.asstdc.com.au> Subject: Re: kernel ppp and default route To: gclarkii@main.gbdata.com (Gary Clark II) Date: Fri, 19 Jul 1996 03:52:29 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199607181604.LAA14560@main.gbdata.com> from Gary Clark II at "Jul 18, 96 11:04:09 am" X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just upgraded to current a couple of days ago and now have run into a > strange problem. > My PPP setup is supposed to install a default route for me and did so before > the upgrade. Now it will install one, but after a very short while the > default will vanish and I have to install on manualy. > Any ideas? You're running "routed" and your upstream link isn't exporting a default route to you. Disable it or, if your forwarding to other hosts, use "gated" in preference, michael From owner-freebsd-current Thu Jul 18 11:04:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05960 for current-outgoing; Thu, 18 Jul 1996 11:04:02 -0700 (PDT) Received: from fullfeed.msn.fullfeed.com (fullfeed.msn.fullfeed.com [199.184.182.42]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA05942 for ; Thu, 18 Jul 1996 11:03:58 -0700 (PDT) Received: from sumatra.americantv.com by fullfeed.msn.fullfeed.com (8.6.9/FF-1.1) id NAA03653; Thu, 18 Jul 1996 13:03:46 -0500 Received: (from uucp@localhost) by sumatra.americantv.com (8.6.12/8.6.12) with UUCP id MAA15086; Thu, 18 Jul 1996 12:41:40 -0500 Received: (jlemon@localhost) by right.PCS (8.6.12/8.6.4) id NAA09388; Thu, 18 Jul 1996 13:01:40 -0500 From: Jonathan Lemon Message-Id: <199607181801.NAA09388@right.PCS> Subject: Re: various 'fetch' errors To: imp@village.org (Warner Losh) Date: Thu, 18 Jul 1996 13:01:39 -0500 (CDT) Cc: current@freebsd.org In-Reply-To: <199607181630.KAA00797@rover.village.org> from "Warner Losh" at Jul 18, 96 10:30:51 am X-Mailer: ELM [version 2.4 PL21] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Heck, I'd be happy with a lpr-like interface to fetch. If there was a > fetchd running in the background, and I said "fetch --background > ftp://ftp.x.org/pub/R6.1/tars/xc-1.tar.gz --after tomorrow" it would > queue the file for fetching and let me knwo when it is done. That way > I could queue up 20-30 things to get and then go to sleep. I've > wanted this feature in an FTP program for a long time and have *NEVER* > seen one with it.[*] Maybe I'm being naive, but wouldn't "at 1am + 2 days fetch ftp://...." do what you want? -- Jonathan From owner-freebsd-current Thu Jul 18 12:40:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11473 for current-outgoing; Thu, 18 Jul 1996 12:40:17 -0700 (PDT) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA11464; Thu, 18 Jul 1996 12:40:14 -0700 (PDT) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id PAA29647; Thu, 18 Jul 1996 15:39:44 -0400 for Date: Thu, 18 Jul 1996 15:39:44 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199607181939.PAA29647@robin.mcnc.org.mcnc.org> To: imp@village.org, jkh@time.cdrom.com Subject: was: various 'fetch' errors, now backround fetch Cc: ache@nagual.ru, asami@cs.berkeley.edu, current@freebsd.org, jkh@freebsd.org X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There WAS an implementation of "ftp" that did this. I believe it was done by the San Diego Supercomputer Center on Cray/UNICOS many years ago. I'll try to remember details and search to see if it still lives on .. - Frank >To: "Jordan K. Hubbard" >Subject: Re: various 'fetch' errors >Cc: asami@cs.berkeley.edu (Satoshi Asami), ache@nagual.ru, jkh@freebsd.org, > current@freebsd.org >Date: Thu, 18 Jul 1996 10:30:51 -0600 >From: Warner Losh > >: > Oh, and I remember you also said you'll implement a "dummy mode" that >: > will let fetch do all the jobs of the ports manager while he's >: > sleeping. >: >: Ooooh, that's a slippery slope, Satoshi - pretty soon it's doing the >: job of the ports manager while he's awake, too, and doing it better >: and faster. Before you know it, you've been replaced by a button. :-) > >Heck, I'd be happy with a lpr-like interface to fetch. If there was a >fetchd running in the background, and I said "fetch --background >ftp://ftp.x.org/pub/R6.1/tars/xc-1.tar.gz --after tomorrow" it would >queue the file for fetching and let me knwo when it is done. That way >I could queue up 20-30 things to get and then go to sleep. I've >wanted this feature in an FTP program for a long time and have *NEVER* >seen one with it.[*] > >Warner > >[*] Well, sort of doing some sort of at kludge. I want it automatic! > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Thu Jul 18 13:04:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13200 for current-outgoing; Thu, 18 Jul 1996 13:04:56 -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 NAA13193 for ; Thu, 18 Jul 1996 13:04:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id OAA02779; Thu, 18 Jul 1996 14:04:24 -0600 (MDT) Message-Id: <199607182004.OAA02779@rover.village.org> To: Jonathan Lemon Subject: Re: various 'fetch' errors Cc: current@freebsd.org In-reply-to: Your message of Thu, 18 Jul 1996 13:01:39 CDT Date: Thu, 18 Jul 1996 14:04:24 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : > Heck, I'd be happy with a lpr-like interface to fetch. If there was a : > fetchd running in the background, and I said "fetch --background : > ftp://ftp.x.org/pub/R6.1/tars/xc-1.tar.gz --after tomorrow" it would : > queue the file for fetching and let me knwo when it is done. That way : > I could queue up 20-30 things to get and then go to sleep. I've : > wanted this feature in an FTP program for a long time and have *NEVER* : > seen one with it.[*] : : Maybe I'm being naive, but wouldn't "at 1am + 2 days fetch ftp://...." do : what you want? Yes. You are being naive. :-) Let's say I wanted to fetch 10-20 things. And I have microbandwidth to the rest of the world. I want them to happen sequentially rather than in parallel. Let's also say I have multiple users that want to do this (say 1-2 each and there are 5 of them), then the savings really kicks in because the files will then get transferred and there will be some chance at getting some bandwidth for interactive jobs. Warner From owner-freebsd-current Thu Jul 18 13:06:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13407 for current-outgoing; Thu, 18 Jul 1996 13:06:44 -0700 (PDT) Received: from ihgw1.att.com (ihgw1.att.com [207.19.48.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13375 for ; Thu, 18 Jul 1996 13:06:37 -0700 (PDT) From: dob@naserver1.cb.lucent.com Received: from nasvr1.cb.att.com by ihig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id OAA01499; Thu, 18 Jul 1996 14:31:46 -0500 Original-From: dob@naserver1.cb.lucent.com Received: from cbsky.cb.att.com by nasvr1.cb.att.com (5.x/EMS-L sol2) id AA17899; Thu, 18 Jul 1996 15:20:01 -0400 Received: by cbsky.cb.att.com (5.x/EMS-1.1 Sol2) id AA02888; Thu, 18 Jul 1996 15:19:29 -0400 Date: Thu, 18 Jul 1996 15:19:29 -0400 Message-Id: <9607181919.AA02888@cbsky.cb.att.com> To: freebsd-current@freebsd.org Subject: Re: panic on reboot with current -current - FOLLOWUP EMAIL 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. A follow up report to my previous report... > 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... Just added 32MB of memory (now at 40MB) and this problem has ``poof'' disappeared! Sorry, John, but I'm no longer a valid VM code beta tester :-( Thanks, Dan From owner-freebsd-current Thu Jul 18 13:14:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13922 for current-outgoing; Thu, 18 Jul 1996 13:14:13 -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 NAA13917 for ; Thu, 18 Jul 1996 13:14:11 -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 NAA00586; Thu, 18 Jul 1996 13:13:42 -0700 (PDT) To: Warner Losh cc: Jonathan Lemon , current@FreeBSD.org Subject: Re: various 'fetch' errors In-reply-to: Your message of "Thu, 18 Jul 1996 14:04:24 MDT." <199607182004.OAA02779@rover.village.org> Date: Thu, 18 Jul 1996 13:13:42 -0700 Message-ID: <584.837720822@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Yes. You are being naive. :-) Let's say I wanted to fetch 10-20 > things. And I have microbandwidth to the rest of the world. I want > them to happen sequentially rather than in parallel. Let's also say I > have multiple users that want to do this (say 1-2 each and there are 5 One of the nice things about UNIX is that you can string existing tools together. Putting all of the above into fetch strikes me as overkill in the extreme and you'll never see me add anything as ludicrous as this to it! :-) Jordna From owner-freebsd-current Thu Jul 18 13:14:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13954 for current-outgoing; Thu, 18 Jul 1996 13:14:26 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13948 for ; Thu, 18 Jul 1996 13:14:24 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id NAA19317; Thu, 18 Jul 1996 13:14:22 -0700 (PDT) Message-Id: <199607182014.NAA19317@ref.tfs.com> Subject: Re: netatalk To: spfarrel@midway.uchicago.edu (steve farrell) Date: Thu, 18 Jul 1996 13:14:21 -0700 (PDT) From: "JULIAN Elischer" Cc: current@freebsd.org In-Reply-To: <199607181101.GAA22703@meno.uchicago.edu> from "steve farrell" at Jul 18, 96 06:01:43 am 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 netatalk daemon atalkd needs a patch.. I'll send it later.. to avoid hte broken code, you can supply a configuration file.. the broken code is in teh auto-config code, so if it is controlled by a config file, this doesn't happen.. julian From owner-freebsd-current Thu Jul 18 13:39:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15637 for current-outgoing; Thu, 18 Jul 1996 13:39:56 -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 NAA15613 for ; Thu, 18 Jul 1996 13:39:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id OAA03731; Thu, 18 Jul 1996 14:38:16 -0600 (MDT) Message-Id: <199607182038.OAA03731@rover.village.org> To: "Jordan K. Hubbard" Subject: Re: various 'fetch' errors Cc: Jonathan Lemon , current@FreeBSD.org In-reply-to: Your message of Thu, 18 Jul 1996 13:13:42 PDT Date: Thu, 18 Jul 1996 14:38:15 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : One of the nice things about UNIX is that you can string existing : tools together. Putting all of the above into fetch strikes me as : overkill in the extreme and you'll never see me add anything as : ludicrous as this to it! :-) What facilities of unix can you use to string together multiple FTPs by multiple users? lpr might be able to do it, which makes me think I need to have my head checked, since that would likely do it. I'll have to check. However, that's as close as it gets with the stock tools. If I can't get the "at midnight" stuff, that's cool since I can do that with "at" and have it queued at midnight. Warner From owner-freebsd-current Thu Jul 18 14:04:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17555 for current-outgoing; Thu, 18 Jul 1996 14:04:34 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17546 for ; Thu, 18 Jul 1996 14:04:31 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id QAA08043; Thu, 18 Jul 1996 16:02:49 -0500 From: Joe Greco Message-Id: <199607182102.QAA08043@brasil.moneng.mei.com> Subject: Re: various 'fetch' errors To: imp@village.org (Warner Losh) Date: Thu, 18 Jul 1996 16:02:49 -0500 (CDT) Cc: jlemon@americantv.com, current@FreeBSD.org In-Reply-To: <199607182004.OAA02779@rover.village.org> from "Warner Losh" at Jul 18, 96 02:04:24 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > : Maybe I'm being naive, but wouldn't "at 1am + 2 days fetch ftp://...." do > : what you want? > > Yes. You are being naive. :-) Let's say I wanted to fetch 10-20 > things. And I have microbandwidth to the rest of the world. I want > them to happen sequentially rather than in parallel. Let's also say I In reality, one might want the ability to specify a "max concurrent xfers" limit. Old SunOS cron did this (I think Solaris does too), one could specify how many jobs of a given grade would be run simultaneously. (see man 5 queuedefs). Probably long forgotten except by us old Sun3 performance tuning freaks. a.4j1n b.2j2n90w n.1j10n60w Ah, the old days. Anyways, that sort of functionality would allow those of us with high speed connectivity to live happy, while still allowing for the slow 14.4K link folks who are interested in scheduling transfers while they are not using their machines. ... JG From owner-freebsd-current Thu Jul 18 14:13:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17992 for current-outgoing; Thu, 18 Jul 1996 14:13:54 -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 OAA17985 for ; Thu, 18 Jul 1996 14:13:49 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA07077; Thu, 18 Jul 1996 17:12:28 -0400 Date: Thu, 18 Jul 1996 17:12:28 -0400 From: Garrett Wollman Message-Id: <9607182112.AA07077@halloran-eldar.lcs.mit.edu> To: Joe Greco Cc: imp@village.org (Warner Losh), jlemon@americantv.com, current@FreeBSD.org Subject: Re: various 'fetch' errors In-Reply-To: <199607182102.QAA08043@brasil.moneng.mei.com> References: <199607182004.OAA02779@rover.village.org> <199607182102.QAA08043@brasil.moneng.mei.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > In reality, one might want the ability to specify a "max concurrent xfers" > limit. Old SunOS cron did this (I think Solaris does too), one could specify > how many jobs of a given grade would be run simultaneously. (see man 5 > queuedefs). Of course, you can still do this with modern batch systems like NQS. That's probably overkill for ftp jobs.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Jul 18 14:44:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20373 for current-outgoing; Thu, 18 Jul 1996 14:44:49 -0700 (PDT) Received: from midway.evtech.com (midway.evtech.com [204.96.163.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA20347 for ; Thu, 18 Jul 1996 14:44:34 -0700 (PDT) Received: from tahiti.evtech.com (tahiti.evtech.com [192.35.179.19]) by midway.evtech.com (8.7.3/8.6.9) with ESMTP id QAA16578; Thu, 18 Jul 1996 16:42:55 -0500 (CDT) Received: from borneo.evtech.com (borneo.evtech.com [192.35.179.29]) by tahiti.evtech.com (8.6.12/8.6.12) with ESMTP id QAA19123; Thu, 18 Jul 1996 16:42:47 -0500 Message-Id: <199607182142.QAA19123@tahiti.evtech.com> To: bugtraq@netspace.org cc: freebsd-current@freebsd.org, current-users@NetBSD.ORG, cross@math.psu.edu Subject: Re: BSD mail.local has race condition - fix Date: Thu, 18 Jul 1996 16:42:43 -0500 From: Travis Hassloch x231 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This fix is relative to: static char sccsid[] = "from: @(#)mail.local.c 5.6 (Berkeley) 6/19/91"; as modified into: "$Id: mail.local.c,v 1.1.1.1 1995/10/18 08:43:19 deraadt Exp $" The problem I described does _not_ occur in BSD/OS. I have cc'ed everyone I think might want to integrate it ('cept OpenBSD, Theo already has a copy); the rest is up to you. I believe it to fix the problem but have not even compiled it as I lack a BSD environment here. --- mail.local.c~ Tue Jul 16 19:00:07 1996 +++ mail.local.c Tue Jul 16 21:02:15 1996 @@ -168,9 +168,9 @@ char *name; int lockfile; { - struct stat sb; + struct stat sb, fsb; struct passwd *pw; - int created, mbfd, nr, nw, off, rval=0, lfd=-1; + int mbfd=-1, nr, nw, off, rval=1, lfd=-1; char biffmsg[100], buf[8*1024], path[MAXPATHLEN], lpath[MAXPATHLEN]; off_t curoff; @@ -194,59 +194,94 @@ return(1); } } - - if (!(created = lstat(path, &sb)) && - (sb.st_nlink != 1 || S_ISLNK(sb.st_mode))) { - err(NOTFATAL, "%s: linked file", path); - return(1); - } - if((mbfd = open(path, O_APPEND|O_WRONLY|O_EXLOCK, - S_IRUSR|S_IWUSR)) < 0) { + /* after this point, always exit via bad to remove lockfile */ +retry: + if (lstat(path, &sb)) { + if (errno != ENOENT) { + err(NOTFATAL, "%s: %s", path, strerror(errno)); + goto bad; + } if ((mbfd = open(path, O_APPEND|O_CREAT|O_WRONLY|O_EXLOCK, - S_IRUSR|S_IWUSR)) < 0) { - err(NOTFATAL, "%s: %s", path, strerror(errno)); - return(1); + S_IRUSR|S_IWUSR)) < 0) { + if (errno == EEXIST) { + /* file appeared since lstat */ + goto retry; + } + else { + err(NOTFATAL, "%s: %s", path, strerror(errno)); + goto bad; + } + } + /* + * Set the owner and group. Historically, binmail repeated this at + * each mail delivery. We no longer do this, assuming that if the + * ownership or permissions were changed there was a reason for doing + * so. + */ + if (fchown(mbfd, pw->pw_uid, pw->pw_gid) < 0) { + err(NOTFATAL, "chown %u:%u: %s", + pw->pw_uid, pw->pw_gid, name); + goto bad; + } } + else { + if (sb.st_nlink != 1 || S_ISLNK(sb.st_mode)) { + err(NOTFATAL, "%s: linked file", path); + goto bad; + } + if ((mbfd = open(path, O_APPEND|O_WRONLY|O_EXLOCK, + S_IRUSR|S_IWUSR)) < 0) { + err(NOTFATAL, "%s: %s", path, strerror(errno)); + goto bad; + } + if (fstat(mbfd, &fsb)) { + /* relating error to path may be bad style */ + err(NOTFATAL, "%s: %s", path, strerror(errno)); + goto bad; + } + if (sb.st_dev != fsb.st_dev || sb.st_ino != fsb.st_ino) { + err(NOTFATAL, "%s: changed after open", path); + goto bad; + } + /* paranoia? */ + if (fsb.st_nlink != 1 || S_ISLNK(fsb.st_mode)) { + err(NOTFATAL, "%s: linked file", path); + goto bad; + } } curoff = lseek(mbfd, 0, SEEK_END); (void)sprintf(biffmsg, "%s@%qd\n", name, curoff); if (lseek(fd, 0, SEEK_SET) == (off_t)-1) { err(FATAL, "temporary file: %s", strerror(errno)); - rval = 1; goto bad; } + /* This section (to trunc) is ugly */ while ((nr = read(fd, buf, sizeof(buf))) > 0) for (off = 0; off < nr; off += nw) if ((nw = write(mbfd, buf + off, nr - off)) < 0) { err(NOTFATAL, "%s: %s", path, strerror(errno)); goto trunc; } - if (nr < 0) { + if (!nr) { + rval = 0; + } + else { err(FATAL, "temporary file: %s", strerror(errno)); trunc: (void)ftruncate(mbfd, curoff); - rval = 1; } - /* - * Set the owner and group. Historically, binmail repeated this at - * each mail delivery. We no longer do this, assuming that if the - * ownership or permissions were changed there was a reason for doing - * so. - */ bad: - if(lockfile) { - if(lfd >= 0) { - unlink(lpath); - close(lfd); - } + if(lfd >= 0) { + unlink(lpath); + close(lfd); } - if (created) - (void)fchown(mbfd, pw->pw_uid, pw->pw_gid); - (void)fsync(mbfd); /* Don't wait for update. */ - (void)close(mbfd); /* Implicit unlock. */ + if (mbfd >= 0) { + (void)fsync(mbfd); /* Don't wait for update. */ + (void)close(mbfd); /* Implicit unlock. */ + } if (!rval) notifybiff(biffmsg); -- Travis Hassloch, Electronic Blacksmith | P=NP if (P=0 or N=1) There is a fine line between an email message and it's signature. From owner-freebsd-current Thu Jul 18 15:15:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23106 for current-outgoing; Thu, 18 Jul 1996 15:15:10 -0700 (PDT) Received: from axp5.physik.fu-berlin.de (axp5.fddi5B.fu-berlin.de [160.45.5.75]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA23097 for ; Thu, 18 Jul 1996 15:15:02 -0700 (PDT) Received: from mordillo (lislip.physik.fu-berlin.de [160.45.33.82]) by axp5.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id AAA24529 for ; Fri, 19 Jul 1996 00:14:52 +0200 (MET DST) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id WAA03200 for current@FreeBSD.org; Thu, 18 Jul 1996 22:53:04 +0200 From: Thomas Graichen Message-Id: <199607182053.WAA03200@mordillo> Subject: eeprom To: current@FreeBSD.org Date: Thu, 18 Jul 1996 22:53:03 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk do we need this in the tree ? :-) (usr.sbin/eeprom) EEPROM(8) FreeBSD System Manager's Manual EEPROM(8) NAME eeprom - openprom control utility SYNOPSIS eeprom [name ...] [name=value ...] DESCRIPTION The eeprom utility is used to display and modify options fields in the SPARCstation openprom. When invoked with no arguments, eeprom display the values of all options. Otherwise, fields are displayed or set (in the order specified on the command line). FILES /dev/openprom the openprom device SEE ALSO openprom(4) HISTORY The eeprom utility first appeared in 4.4BSD. 4.4BSD June 9, 1993 1 can someone remove it from the tree ? (... or tell me where the openprom is in my pc ...) t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-current Thu Jul 18 15:27:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA24001 for current-outgoing; Thu, 18 Jul 1996 15:27:55 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA23996 for ; Thu, 18 Jul 1996 15:27:53 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id SAA16106; Thu, 18 Jul 1996 18:27:38 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Thomas Graichen cc: current@FreeBSD.org From: "Gary Palmer" Subject: Re: eeprom In-reply-to: Your message of "Thu, 18 Jul 1996 22:53:03 +0200." <199607182053.WAA03200@mordillo> Date: Thu, 18 Jul 1996 18:27:38 -0400 Message-ID: <16102.837728858@orion.webspan.net> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Thomas Graichen wrote in message ID <199607182053.WAA03200@mordillo>: > do we need this in the tree ? :-) (usr.sbin/eeprom) Thanks :) Done. BTW: axp5? Alpha AXP? Bah. *turns green*. So when are you finishing the FreeBSD/Alpha port? :-) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Thu Jul 18 16:17:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26966 for current-outgoing; Thu, 18 Jul 1996 16:17:19 -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 QAA26961 for ; Thu, 18 Jul 1996 16:17:15 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA12464 for ; Fri, 19 Jul 1996 01:17:12 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA01367 for freebsd-current@FreeBSD.org; Fri, 19 Jul 1996 01:17:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id BAA00651 for freebsd-current@FreeBSD.org; Fri, 19 Jul 1996 01:03:01 +0200 (MET DST) From: J Wunsch Message-Id: <199607182303.BAA00651@uriah.heep.sax.de> Subject: Re: eeprom To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 19 Jul 1996 01:03:01 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607182053.WAA03200@mordillo> from Thomas Graichen at "Jul 18, 96 10:53:03 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 Thomas Graichen wrote: > do we need this in the tree ? :-) (usr.sbin/eeprom) > > EEPROM(8) FreeBSD System Manager's Manual EEPROM(8) > > NAME > eeprom - openprom control utility We might replace it by this one: EEPROM(1) FreeBSD Reference Manual EEPROM(1) NAME eeprom - read/write/erase 9346 industry-standard EEPROM SYNOPSIS eeprom [-q] [-p port] -R | -W | -E | -P pattern :-)) -- 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 18 19:09:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA11509 for current-outgoing; Thu, 18 Jul 1996 19:09:25 -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 TAA11498 for ; Thu, 18 Jul 1996 19:09:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA13338; Thu, 18 Jul 1996 19:08:51 -0700 (PDT) Message-Id: <199607190208.TAA13338@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: John Dyson cc: hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of "Thu, 18 Jul 1996 12:09:26 CDT." <199607181709.MAA00332@dyson.iquest.net> From: David Greenman Reply-To: davidg@root.com Date: Thu, 18 Jul 1996 19:08:51 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> >>> >have still had one panic but I have 7 days of uptime on our news server, >>> >which, sadly, is an all-time record for us running FreeBSD 2 on a full-feed >>> >news server. I will see how it goes for couple of weeks more. >>> >>> ...I'm interested in hearing about the panic. >> >> I did not get a dump, short of space on /var, it just had rebooted. >> >Chiming in here: David, do you think that this could be a kernel >stack space problem? No. My analysis of wcarchive showed that stack growth never exceeds 2.6KB. I'm guessing that Heikki is using the "MMAP" option(s) in innd and is stumbling over (kernel) bugs because of it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Jul 18 20:31:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA20495 for current-outgoing; Thu, 18 Jul 1996 20:31:34 -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 UAA20459; Thu, 18 Jul 1996 20:31:17 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id NAA32464; Fri, 19 Jul 1996 13:25:39 +1000 Date: Fri, 19 Jul 1996 13:25:39 +1000 From: Bruce Evans Message-Id: <199607190325.NAA32464@godzilla.zeta.org.au> To: imp@village.org, nate@mt.sri.com Subject: Re: Cause of APM_DSVALUE_BUG found (but not completely fixed yet) Cc: current@freebsd.org, davidg@freebsd.org, freebsd-mobile@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >: + biosbasemem = bootinfo.bi_basemem; >: + biosextmem = bootinfo.bi_extmem; >Hmmm. The linux folks are running into machines that this would be >bad for. Evidentally, they claim, a nontrivial number of machines >will cap the returned value at 16M of memory. A number of machines alreay cap the value in the CMOS at 16M, and all machines cap it at 64M, while there's nothing to stop the bootstrap getting it right and going up to 4096GB (1024 back switched segments of 4GB each ;-). >It might be best to do >this as an option. Nope. Bruce From owner-freebsd-current Thu Jul 18 21:52:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA28273 for current-outgoing; Thu, 18 Jul 1996 21:52:19 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA28259 for ; Thu, 18 Jul 1996 21:52:17 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id WAA08396; Thu, 18 Jul 1996 22:47:27 -0500 From: Joe Greco Message-Id: <199607190347.WAA08396@brasil.moneng.mei.com> Subject: Re: various 'fetch' errors To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 18 Jul 1996 22:47:27 -0500 (CDT) Cc: imp@village.org, jlemon@americantv.com, current@FreeBSD.ORG In-Reply-To: <584.837720822@time.cdrom.com> from "Jordan K. Hubbard" at Jul 18, 96 01:13:42 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Yes. You are being naive. :-) Let's say I wanted to fetch 10-20 > > things. And I have microbandwidth to the rest of the world. I want > > them to happen sequentially rather than in parallel. Let's also say I > > have multiple users that want to do this (say 1-2 each and there are 5 > > One of the nice things about UNIX is that you can string existing > tools together. Putting all of the above into fetch strikes me as > overkill in the extreme and you'll never see me add anything as > ludicrous as this to it! :-) Ludicrous? I see. While I might disagree with that description of the feature request, I would agree that it would be better to leverage off of another tool rather than embedding "cron/at/queue" functionality in the tool. Except... we don't have one. Well, I suppose you could cobble one together with enough shell or perl programming... but maybe that shouldn't count. I do think that cron is a good paradigm for this sort of thing. With extensions similar to SunOS's queuedefs, it would be adequate to fill this need. It also goes a long way to handling resource contention on slower machines... because I limit "disk" intensive crontabs to a queue with one job allowed on Solaria, my disks don't go totally wacko when a maintenance chore takes longer than I anticipated... indeed I don't even have to worry about it. ... JG From owner-freebsd-current Fri Jul 19 01:54:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA15688 for current-outgoing; Fri, 19 Jul 1996 01:54:13 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-134.ut.nl.ibm.net [139.92.42.134]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA15679; Fri, 19 Jul 1996 01:54:06 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id BAA26326; Fri, 19 Jul 1996 01:18:01 +0200 (MET DST) Message-Id: <199607182318.BAA26326@vector.jhs.no_domain> To: "Michael L. VanLoon -- HeadCandy.com" cc: isp@freebsd.org, current@freebsd.org Subject: Re: Opinions? From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (later) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Wed, 17 Jul 1996 22:02:36 PDT." <199607180502.WAA09210@MindBender.HeadCandy.com> Date: Fri, 19 Jul 1996 01:18:00 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: "Michael L. VanLoon -- HeadCandy.com" > Subject: Re: Opinions? Before current gets swamped with non current related stuff, arising from Michael's original post (NT as an OS for ISP's etc) .... As we have a mail list called isp@freebsd.org please follow up ISP stuff there, not to current@, Thanks. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Fri Jul 19 05:48:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA24088 for current-outgoing; Fri, 19 Jul 1996 05:48:19 -0700 (PDT) Received: from uucp.DK.net (uucp@uucp.DK.net [193.88.44.47]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA24082 for ; Fri, 19 Jul 1996 05:48:12 -0700 (PDT) Received: from pingnet (uucp@localhost) by uucp.DK.net (8.6.12/8.6.12) with UUCP id OAA22212; Fri, 19 Jul 1996 14:47:43 +0200 Received: from kyklopen by ic1.ic.dk with UUCP id AA20528 (5.65c8/IDA-1.4.4j); Fri, 19 Jul 1996 13:50:03 +0200 Received: (from staff@localhost) by kyklopen.ping.dk (8.7.5/8.7.3) id UAA03296; Thu, 18 Jul 1996 20:52:48 +0200 (MET DST) Date: Thu, 18 Jul 1996 20:52:48 +0200 (MET DST) From: Thomas Sparrevohn To: Gary Clark II Cc: freebsd-current@freebsd.org Subject: Re: kernel ppp and default route In-Reply-To: <199607181604.LAA14560@main.gbdata.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Charset: ISO_8859-1 X-Char-Esc: 29 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 18 Jul 1996, Gary Clark II wrote: > Hello all, > > I just upgraded to current a couple of days ago and now have run into a strange > problem. > > My PPP setup is supposed to install a default route for me and did so before > the upgrade. Now it will install one, but after a very short while the > default will vanish and I have to install on manualy. > > Any ideas? Well it seems to be some kind of timeout problem. I was in the middle of writing a response when i decided to check it out. The problem is that the first few, 2 - 3 connections works allright then if there is no traffic on the line for some time you get "hostname name lookup failure". The default route does'nt change in the netstat data and routed does'nt log additional data. But if you then add the default route by hand everything starts working as it should again. Regards Thomas From owner-freebsd-current Fri Jul 19 07:59:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00485 for current-outgoing; Fri, 19 Jul 1996 07:59:15 -0700 (PDT) Received: from DeepCore.dk (aalb2.pip.dknet.dk [194.192.0.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA00478 for ; Fri, 19 Jul 1996 07:59:08 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.5/8.7.3) id QAA01461 for current@freebsd.org; Fri, 19 Jul 1996 16:42:47 +0200 (MET DST) Message-Id: <199607191442.QAA01461@DeepCore.dk> Subject: dato format changes ?? To: current@freebsd.org (FreeBSD current) Date: Fri, 19 Jul 1996 16:42:47 +0200 (MET DST) From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just did a make world, and now good old ls prints garbage like: -rw-r--r-- 1 sos wheel 7617 0/96 11:31:1 print.c which should have been: -rw-r--r-- 1 sos wheel 7617 Jan 20 11:31 print.c I think the toture is somewhere in the lib/libc/stdtime functions last touched by wollmann, whats up ???? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Fri Jul 19 08:04:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA00825 for current-outgoing; Fri, 19 Jul 1996 08:04:28 -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 IAA00819; Fri, 19 Jul 1996 08:04:24 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id LAA01242; Fri, 19 Jul 1996 11:04:15 -0400 (EDT) Date: Fri, 19 Jul 1996 11:04:13 -0400 (EDT) From: "Marc G. Fournier" To: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: ls ~userid no longer works... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I realize that this is a really vague question, but for some reason or another, last night, my -current machine stopped being able to deal with a simple command such as 'ls ~userid'...it comes back with Unknonw User... I'm running the -current machine as an NIS client off of a -stable achine, neither of which have been upgrded in over a week.. So far as I can tell, there is nothing that I've changed on either of my machines in that time, as I haven't had much time to work on either... All the appropriate NIS softare is running, my password file on the NIS machine is fine (I can telnet/rlogin into the machine)... Only ~ resolution seems to be broken... And I have tried to reboot the machine to see if that clears it up, to no avail... I'm at a lose for where to look further, so am hoping someone else can shed some light on the problem :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Fri Jul 19 08:09:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01121 for current-outgoing; Fri, 19 Jul 1996 08:09:52 -0700 (PDT) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01114; Fri, 19 Jul 1996 08:09:50 -0700 (PDT) Received: from localhost by troll.uunet.ca with SMTP id <21007-1788>; Fri, 19 Jul 1996 11:09:41 -0400 Date: Fri, 19 Jul 1996 11:09:37 -0400 From: Cat Okita To: "Marc G. Fournier" cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: ls ~userid no longer works... 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 Further to Marc's message, when logged into that machine, trying to run screen (which was working prior to whatever happened...) I get the error: > screen -R getpwuid() can't identify your account! > id uid=11(cat) gid=0(wheel) groups=0(wheel), 20(staff), 99(www) The ~userid error only appears in tcsh, but the getpwuid() error seems to be shell independant. Cat On Fri, 19 Jul 1996, Marc G. Fournier wrote: > I realize that this is a really vague question, but for > some reason or another, last night, my -current machine stopped being > able to deal with a simple command such as 'ls ~userid'...it comes > back with Unknonw User... > > I'm running the -current machine as an NIS client off of > a -stable achine, neither of which have been upgrded in over a week.. > > So far as I can tell, there is nothing that I've changed on > either of my machines in that time, as I haven't had much time to > work on either... > > All the appropriate NIS softare is running, my password > file on the NIS machine is fine (I can telnet/rlogin into the > machine)... > > Only ~ resolution seems to be broken... > > And I have tried to reboot the machine to see if that clears it > up, to no avail... > > I'm at a lose for where to look further, so am hoping someone > else can shed some light on the problem :( From owner-freebsd-current Fri Jul 19 08:12:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01355 for current-outgoing; Fri, 19 Jul 1996 08:12: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 IAA01348; Fri, 19 Jul 1996 08:12:20 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA13279; Fri, 19 Jul 1996 11:12:17 -0400 Date: Fri, 19 Jul 1996 11:12:17 -0400 From: Garrett Wollman Message-Id: <9607191512.AA13279@halloran-eldar.lcs.mit.edu> To: sos@FreeBSD.org Cc: current@FreeBSD.org (FreeBSD current) Subject: dato format changes ?? In-Reply-To: <199607191442.QAA01461@DeepCore.dk> References: <199607191442.QAA01461@DeepCore.dk> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < I think the toture is somewhere in the lib/libc/stdtime functions > last touched by wollmann, whats up ???? You're right, something bad appears to have happened here that didn't make itself apparent in the `date' command. I will back this out until I can figure out the problem. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Fri Jul 19 08:48:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04103 for current-outgoing; Fri, 19 Jul 1996 08:48:11 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04089; Fri, 19 Jul 1996 08:48:07 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id IAA18260; Fri, 19 Jul 1996 08:48:05 -0700 (PDT) Message-Id: <199607191548.IAA18260@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Julian H. Stacey" cc: isp@freebsd.org, current@freebsd.org Subject: Re: Opinions? In-reply-to: Your message of Fri, 19 Jul 96 01:18:00 +0200. <199607182318.BAA26326@vector.jhs.no_domain> Date: Fri, 19 Jul 1996 08:48:05 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi, Reference: >> From: "Michael L. VanLoon -- HeadCandy.com" >> Subject: Re: Opinions? >Before current gets swamped with non current related stuff, >arising from Michael's original post (NT as an OS for ISP's etc) .... >As we have a mail list called isp@freebsd.org >please follow up ISP stuff there, not to current@, Thanks. I already posted a correction once -- I was *NOT* replying about NT as an OS for ISPs! I was posting about NT as an OS in the overall server OS market. Again: I was NOT speaking specifically about ISPs. In addition, I tried to direct all followup posts to freebsd-chat, but it didn't stick. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Fri Jul 19 08:55:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04557 for current-outgoing; Fri, 19 Jul 1996 08:55:55 -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 IAA04552 for ; Fri, 19 Jul 1996 08:55:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id JAA12161; Fri, 19 Jul 1996 09:52:28 -0600 (MDT) Message-Id: <199607191552.JAA12161@rover.village.org> To: Joe Greco Subject: Re: various 'fetch' errors Cc: jkh@time.cdrom.com (Jordan K. Hubbard), jlemon@americantv.com, current@FreeBSD.org In-reply-to: Your message of Thu, 18 Jul 1996 22:47:27 CDT Date: Fri, 19 Jul 1996 09:52:28 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : While I might disagree with that description of the feature request, I : would agree that it would be better to leverage off of another tool : rather than embedding "cron/at/queue" functionality in the tool. : : Except... we don't have one. Well, I suppose you could cobble one : together with enough shell or perl programming... but maybe that : shouldn't count. There is no current tool that is easy to use that I could leverage off of to do what I want. Otherwise I would have gone out and just used that. : extensions similar to SunOS's queuedefs, it would be adequate to fill Would people be open to a queuedefs facility in at/cron? I think that would get me what I wanted and would be a useful tool for others. Warner From owner-freebsd-current Fri Jul 19 09:23:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06061 for current-outgoing; Fri, 19 Jul 1996 09:23:47 -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 JAA06047; Fri, 19 Jul 1996 09:23:42 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA16523; Fri, 19 Jul 1996 12:20:12 -0400 From: Bill Paul Message-Id: <199607191620.MAA16523@skynet.ctr.columbia.edu> Subject: Re: ls ~userid no longer works... To: scrappy@ki.net (Marc G. Fournier) Date: Fri, 19 Jul 1996 12:20:10 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Jul 19, 96 11:04: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, Marc G. Fournier had to walk into mine and say: > Hi... > > I realize that this is a really vague question, but for > some reason or another, last night, my -current machine stopped being > able to deal with a simple command such as 'ls ~userid'...it comes > back with Unknonw User... None of the code NIS code in libc has changed since before 2.1.5 was frozen (in either branch). Last bit of hacking I did was on the database cache code in ypserv. I can't see how that could cause this kind of problem (it could cause problems if I screwed up, but they'd be a bit more severe than this, I think :). > I'm running the -current machine as an NIS client off of > a -stable achine, neither of which have been upgrded in over a week.. Ah, nevermind then. I didn't change the -stable ypserv. > So far as I can tell, there is nothing that I've changed on > either of my machines in that time, as I haven't had much time to > work on either... Then maybe somebody else changed something for you. Or maybe you changed something which you think is totally unrelated but that really isn't (this is usually the case -- it's happened to me many times). Have you added any new users lately? If so, are you absitively, posolutely sure their NIS passwd entries are formatted correctly? What about group entries? Is /var/yp/; Fri, 19 Jul 1996 11:37:09 -0700 (PDT) Received: from quark.cns.ucla.edu (quark.cns.ucla.edu [164.67.62.18]) by kodiak.ucla.edu (8.7.4/8.6.9) with SMTP id LAA32042; Fri, 19 Jul 1996 11:36:34 -0700 Date: Fri, 19 Jul 1996 11:36:34 -0700 (PDT) From: Mike Tsirulnikov To: freebsd-current@freebsd.org cc: scott@cns.ucla.edu, "Scott A. Harvey" , marc@cns.ucla.edu, Mike Tsirulnikov Subject: Fatal trap 12: page fault while in kernel mode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We have been running FreeBSD 2.1 on Pentium 200 MHz machine for a while now and this is the first time it died like this. Below is what kernel logged to the screen: fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0110580 code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32, gran 1 processor e-flags = interrupt enabled, resume, IOPL=0 current process = 13320 (top) interrupt mask = panic: page fault Any help regarding how to avoid this type of crash is greatly appreciated. Thanks. --- Mike Tsirulnikov mt@cns.ucla.edu From owner-freebsd-current Fri Jul 19 13:53:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18700 for current-outgoing; Fri, 19 Jul 1996 13:53:12 -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 NAA18691 for ; Fri, 19 Jul 1996 13:53:07 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id NAA19861; Fri, 19 Jul 1996 13:53:38 -0700 Date: Fri, 19 Jul 1996 13:53:34 -0700 (PDT) From: Veggy Vinny To: current@freebsd.org Subject: /usr/bin/passwd and finger output Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A few days ago, I reported that the latest -current's /usr/bin/passwd won't work for people not in the wheel group. Today with the latest -current build, the same thing still happens: dennis@mercury [1:45pm][~] >> passwd passwd: Permission denied dennis@mercury [1:45pm][~] >> dir /usr/bin/passwd -r-sr-xr-x 2 root bin 32768 Jul 19 12:45 /usr/bin/passwd dennis@mercury [1:45pm][~] >> This is happening on 4 different machines so it's not a configuration issue. Is there a work around this? Also, the finger output seems to be really different than the previous one atleast for the date and time. Login: dennis Name: Dennis Pang Directory: /home/dennis Shell: /usr/local/bin/tcsh Last login 07/16/96 10:01:1 (PDT) on ttyp3 from 206.28.134.6 New mail received 07/17/96 21:54:4 (PDT) Unread since 07/16/96 10:01:2 (PDT) No Plan. Vince From owner-freebsd-current Fri Jul 19 13:53:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18732 for current-outgoing; Fri, 19 Jul 1996 13:53:37 -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 NAA18720; Fri, 19 Jul 1996 13:53:25 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id QAA01547; Fri, 19 Jul 1996 16:52:06 -0400 (EDT) Date: Fri, 19 Jul 1996 16:52:04 -0400 (EDT) From: "Marc G. Fournier" To: Bill Paul cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ls ~userid no longer works... In-Reply-To: <199607191620.MAA16523@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Bill Paul wrote: > None of the code NIS code in libc has changed since before 2.1.5 was > frozen (in either branch). Last bit of hacking I did was on the database > cache code in ypserv. I can't see how that could cause this kind of problem > (it could cause problems if I screwed up, but they'd be a bit more > severe than this, I think :). > Okay, from what I can tell, something changed in libc C thta changed the behavoiur of such functions as getpwuid()...for the longest time, I could use my shared binary of bash/tcsh that was compiled under 2.1-STABLE under 2.2-CURRENT... Since they were working fine, I didn't think of checking sh/csh under -current to see if they exhibited the same behavoiur, which Cat pointed out they didn't, so I recompiled bash/tcsh out of ports and they run fine... So, chock it up to operator error...or anything else you'd like to chock it up to :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Fri Jul 19 14:32:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20748 for current-outgoing; Fri, 19 Jul 1996 14:32:12 -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 OAA20736 for ; Fri, 19 Jul 1996 14:32:05 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA27338; Fri, 19 Jul 1996 23:31:51 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA18449; Fri, 19 Jul 1996 23:31:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id XAA00672; Fri, 19 Jul 1996 23:28:55 +0200 (MET DST) From: J Wunsch Message-Id: <199607192128.XAA00672@uriah.heep.sax.de> Subject: Re: Fatal trap 12: page fault while in kernel mode To: freebsd-current@freebsd.org Date: Fri, 19 Jul 1996 23:28:55 +0200 (MET DST) Cc: freebsd-current@freebsd.org, scott@cns.ucla.edu, sharvey@cns.ucla.edu, marc@cns.ucla.edu, mt@cns.ucla.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Mike Tsirulnikov at "Jul 19, 96 11:36:34 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 Mike Tsirulnikov wrote: > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf0110580 > code segment = base 0x0, limit 0xfffff, type 0x1b > DPL 0, pres 1, def32, gran 1 > processor e-flags = interrupt enabled, resume, IOPL=0 > current process = 13320 (top) > interrupt mask = > > panic: page fault (You should normally report this kind of problems accompanied by an excerpt of the command output for "nm /kernel | sort | more", around the instruction pointer where the fault happened [0xf0110580]. Luckily, you are running the GENERIC kernel, so i could do this for you. :) The fault happens inside sys/kern/kern_sysctl.c, in function fill_eproc(), here: if (SESS_LEADER(p)) ^^^^^^^^^^^^^^ ep->e_flag |= EPROC_SLEADER; SESS_LEADER() is defined in sys/sys/proc.h as: #define SESS_LEADER(p) ((p)->p_session->s_leader == (p)) Apparently, (p)->p_session is 0, this process doesn't have a session associated with it. I think that's a ``Can't happen'' case... maybe there's somebody around with better knowledge about how sessions are being allocated. -- 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 Fri Jul 19 14:33:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20813 for current-outgoing; Fri, 19 Jul 1996 14:33:00 -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 OAA20805 for ; Fri, 19 Jul 1996 14:32:54 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA16896; Fri, 19 Jul 1996 17:29:29 -0400 From: Bill Paul Message-Id: <199607192129.RAA16896@skynet.ctr.columbia.edu> Subject: Re: /usr/bin/passwd and finger output To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Fri, 19 Jul 1996 17:29:28 -0400 (EDT) Cc: current@FreeBSD.org In-Reply-To: from "Veggy Vinny" at Jul 19, 96 01:53:34 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Veggy Vinny had to walk into mine and say: > A few days ago, I reported that the latest -current's > /usr/bin/passwd won't work for people not in the wheel group. Today > with the latest -current build, the same thing still happens: > > dennis@mercury [1:45pm][~] >> passwd > passwd: Permission denied > dennis@mercury [1:45pm][~] >> dir /usr/bin/passwd > -r-sr-xr-x 2 root bin 32768 Jul 19 12:45 /usr/bin/passwd > dennis@mercury [1:45pm][~] >> How about trying 'which passwd' and seeing what it returns? How about trying to run /usr/bin/passwd explicitly (with the full path)? You sure you don't have a /usr/local/bin/passwd or a cutsey alias hidden away somewhere? > This is happening on 4 different machines so it's not a configuration > issue. Is there a work around this? Somebody else out there please test this. I don't have a -current box handy with which to test it myself (I'll try it on my 2.1 box tonight). I strongly suspect that it is some sort of configuration error, albeit a bizarre one. I suspect this mainly because nobody else has reported having the same trouble. > Also, the finger output seems to be really different than the > previous one atleast for the date and time. > > Login: dennis Name: Dennis Pang > Directory: /home/dennis Shell: /usr/local/bin/tcsh > Last login 07/16/96 10:01:1 (PDT) on ttyp3 from 206.28.134.6 > New mail received 07/17/96 21:54:4 (PDT) > Unread since 07/16/96 10:01:2 (PDT) > No Plan. > > Vince Somebody hacked a bit on the stdtime stuff in libc recently and I think there were some problems (times reported by ls were a little busted too, apparently). You may have to sup again and rebuild libc. -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 Fri Jul 19 15:10:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22615 for current-outgoing; Fri, 19 Jul 1996 15:10:16 -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 PAA22610 for ; Fri, 19 Jul 1996 15:10:15 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id PAA26236; Fri, 19 Jul 1996 15:10:31 -0700 Date: Fri, 19 Jul 1996 15:10:29 -0700 (PDT) From: Veggy Vinny To: Bill Paul cc: current@FreeBSD.org Subject: Re: /usr/bin/passwd and finger output In-Reply-To: <199607192129.RAA16896@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Veggy Vinny had > to walk into mine and say: > > > A few days ago, I reported that the latest -current's > > /usr/bin/passwd won't work for people not in the wheel group. Today > > with the latest -current build, the same thing still happens: > > > > dennis@mercury [1:45pm][~] >> passwd > > passwd: Permission denied > > dennis@mercury [1:45pm][~] >> dir /usr/bin/passwd > > -r-sr-xr-x 2 root bin 32768 Jul 19 12:45 /usr/bin/passwd > > dennis@mercury [1:45pm][~] >> > > How about trying 'which passwd' and seeing what it returns? How > about trying to run /usr/bin/passwd explicitly (with the full path)? > You sure you don't have a /usr/local/bin/passwd or a cutsey alias > hidden away somewhere? yep, because this is what I got: dennis@mercury [2:57pm][~] >> which passwd /usr/bin/passwd dennis@mercury [2:57pm][~] >> dir /usr/local/bin/passwd colorls: /usr/local/bin/passwd: No such file or directory dennis@mercury [2:58pm][~] >> but when I do it from a account that's in group wheel: vince@mercury [2:55pm][~] >> passwd Changing local password for vince. Old password: (I hit CTRL-D here) passwd: Permission denied passwd: /etc/master.passwd: unchanged vince@mercury [3:08pm][~] >> which passwd /usr/bin/passwd vince@mercury [3:08pm][~] >> It works fine... > > This is happening on 4 different machines so it's not a configuration > > issue. Is there a work around this? > > Somebody else out there please test this. I don't have a -current box > handy with which to test it myself (I'll try it on my 2.1 box tonight). I > strongly suspect that it is some sort of configuration error, albeit a > bizarre one. I suspect this mainly because nobody else has reported > having the same trouble. Hmmm, this happened after the code change to chpass and passwd for the sources a week or so ago. > > Also, the finger output seems to be really different than the > > previous one atleast for the date and time. > > > > Login: dennis Name: Dennis Pang > > Directory: /home/dennis Shell: /usr/local/bin/tcsh > > Last login 07/16/96 10:01:1 (PDT) on ttyp3 from 206.28.134.6 > > New mail received 07/17/96 21:54:4 (PDT) > > Unread since 07/16/96 10:01:2 (PDT) > > No Plan. > > > > Vince > > Somebody hacked a bit on the stdtime stuff in libc recently and I > think there were some problems (times reported by ls were a little > busted too, apparently). You may have to sup again and rebuild libc. Oh okay, will do that... Vince From owner-freebsd-current Fri Jul 19 15:19:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23097 for current-outgoing; Fri, 19 Jul 1996 15:19:32 -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 PAA23086 for ; Fri, 19 Jul 1996 15:19:28 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA28394; Sat, 20 Jul 1996 00:17:19 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA18902; Sat, 20 Jul 1996 00:17:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id AAA01154; Sat, 20 Jul 1996 00:11:18 +0200 (MET DST) From: J Wunsch Message-Id: <199607192211.AAA01154@uriah.heep.sax.de> Subject: Re: /usr/bin/passwd and finger output To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 20 Jul 1996 00:11:18 +0200 (MET DST) Cc: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Veggy Vinny at "Jul 19, 96 01:53:34 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Veggy Vinny wrote: > A few days ago, I reported that the latest -current's > /usr/bin/passwd won't work for people not in the wheel group. Today > with the latest -current build, the same thing still happens: > > dennis@mercury [1:45pm][~] >> passwd > passwd: Permission denied I cannot confirm this. The only bogosity (but not a new one actually, i've verified the logs) is that passwd(1) defaults to the user as obtained by getlogin(), so if you su(1) to another user, passwd without an argument would still attempt to set the passwd for the logged in user (and will not allow this unless the calling user is root). Everything else works well. Btw., chpass(1) seems to default to the user as obtained by getuid(), which looks more rational. -- 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 Fri Jul 19 15:23:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23303 for current-outgoing; Fri, 19 Jul 1996 15:23:30 -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 PAA23298 for ; Fri, 19 Jul 1996 15:23:29 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id PAA27391; Fri, 19 Jul 1996 15:23:24 -0700 Date: Fri, 19 Jul 1996 15:23:22 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: /usr/bin/passwd and finger output In-Reply-To: <199607192211.AAA01154@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 Sat, 20 Jul 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > A few days ago, I reported that the latest -current's > > /usr/bin/passwd won't work for people not in the wheel group. Today > > with the latest -current build, the same thing still happens: > > > > dennis@mercury [1:45pm][~] >> passwd > > passwd: Permission denied > > I cannot confirm this. The only bogosity (but not a new one actually, > i've verified the logs) is that passwd(1) defaults to the user as > obtained by getlogin(), so if you su(1) to another user, passwd > without an argument would still attempt to set the passwd for the > logged in user (and will not allow this unless the calling user is > root). > > Everything else works well. > > Btw., chpass(1) seems to default to the user as obtained by getuid(), > which looks more rational. Actually, you're right about this one.... What I did was su to root from vince and then su -l dennis since he said that it didn't let him change his password but before this used to work... Any ideas why it doesn't any more? Vince From owner-freebsd-current Fri Jul 19 15:39:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA24043 for current-outgoing; Fri, 19 Jul 1996 15:39:52 -0700 (PDT) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA24038; Fri, 19 Jul 1996 15:39:50 -0700 (PDT) Received: (from craig@localhost) by seabass.progroup.com (8.7.5/8.6.12) id PAA06649; Fri, 19 Jul 1996 15:40:44 -0700 (PDT) Message-Id: <199607192240.PAA06649@seabass.progroup.com> Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES To: freebsd-chat@freebsd.org, current@freebsd.org Date: Fri, 19 Jul 1996 15:40:44 -0700 (PDT) From: "Craig Shaver" In-Reply-To: <199607171610.JAA05923@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jul 17, 96 09:10:54 am 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 > > > > > > >I'm still trying to understand why people think they have to run NT. > >There are other options, like FreeBSD and OS/2. A lot cheaper and not > >made by Microsoft. > > > > Because NT is a very solid server OS. It is tightly integrated with > the most popular application server software, Microsoft BackOffice. > It is *the* most stable OS I have run. It scales well across multiple > CPUs, and has a very solid multi-processor and multi-threaded kernel. > NT 4.0 will have not only dynamically scheduled threads, but user- blah, blah, blah, on and on .... del ...... Ok, NT is better than windog 3.1 and wingding95. I am working on a project that uses NT 3.51 backends for a proprietary database that was built for use on win95/NT. These backends are connected to a Sparcstation 5 running Solaris 2.5. You can see this in action by going to the home page at http://www.familytreemaker.com/. About half way down is something called "Family Finder Index". This is a cgi program that gets data from the NT's and puts it into a web page. The NT's work ok until something unforseen happens. Back in April we had a power outage. The Sparc rebooted automatically and all of the rc scripts started all of the background daemons and everything worked. No humans needed. The NT's sat there and refused to run anything until some user logged in! Apparently there is no way to have a program automatically run unless you log in and then you have something in that little "start" window. Nice design for a *server*! I guess if someone uses NT for a server and the power goes down in the middle of the night, then *someone* will have to be there to log in and start all of the server processes. (snort, snicker, guffaw, ;^) (There may be a fix for this in service pak 4! :^) -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-current Fri Jul 19 17:10:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA27940 for current-outgoing; Fri, 19 Jul 1996 17:10:23 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA27935 for ; Fri, 19 Jul 1996 17:10:20 -0700 (PDT) Received: from socrate (ts1port8d.masternet.it [194.184.65.30]) by masternet.it (8.6.12/8.6.9) with SMTP id BAA13301 for ; Sat, 20 Jul 1996 01:07:59 +0200 Message-ID: <31F03193.41C67EA6@masternet.it> Date: Sat, 20 Jul 1996 03:08:35 +0200 From: Beck Peccoz Amedeo X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: optical fiber PCI Ethernet adapter Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm looking for a supported pci ethernet card with optical fiber connectors. Has anyone ever used one? I know Allied Telesys makes one (model 17xx), are there drivers for FreeBSD? Thanks in advance -- Beck-Peccoz Amedeo GEA Software S.r.l. Via Deffeyes, 1 11025 Gressoney Saint Jean (AO) ITALY Tel. ++39-125-366302 Fax. ++39-125-366415 From owner-freebsd-current Fri Jul 19 17:28:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28856 for current-outgoing; Fri, 19 Jul 1996 17:28:17 -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 RAA28839; Fri, 19 Jul 1996 17:28:13 -0700 (PDT) Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <14732(1)>; Fri, 19 Jul 1996 17:27:37 PDT Received: by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1-TB) id AA14374; Fri, 19 Jul 96 20:27:42 EDT Message-Id: <9607200027.AA14374@gemini.sdsp.mc.xerox.com> To: "Craig Shaver" Cc: freebsd-chat@freebsd.org, current@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-Reply-To: Your message of "Fri, 19 Jul 1996 15:40:44 PDT." <199607192240.PAA06649@seabass.progroup.com> Date: Fri, 19 Jul 1996 17:27:41 PDT From: "Marty Leisner" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199607192240.PAA06649@seabass.progroup.com>, you write: >> >> >> >> > >> >I'm still trying to understand why people think they have to run NT. >> >There are other options, like FreeBSD and OS/2. A lot cheaper and not >> >made by Microsoft. >> > >> >> Because NT is a very solid server OS. It is tightly integrated with >> the most popular application server software, Microsoft BackOffice. >> It is *the* most stable OS I have run. It scales well across multiple >> CPUs, and has a very solid multi-processor and multi-threaded kernel. >> NT 4.0 will have not only dynamically scheduled threads, but user- >blah, blah, blah, on and on .... del ...... > I've had very negative experiences with OS/2. I've installed it multiple times (I got OS/2 warp/ warp connect and NE2000 boards). I've installed it several times in the last year on different machines configured differently...I don't do any serous work on them, OS/2 warp eventually came up with a useless message "file system corrupt--please call for support...right, sure, like, someone will come to my house and fix my machine? pretty useless... NT is fine in many regards...but I just have an NT 3.51 installation go south, and the "repair" mode can't seem to find my CD-ROM... I also was writing some netbios/lanserver emulation code on another machine (a sun) running TCP/IP. I obviously had a bug in my program (; -)) and it seems I bought NT (3.51) to its knees with my bug (a panic). Any OS where a buggy remote application can crash the machine is suspect (yes, it can happen, but it points to architectural problems). I found win95 pretty reasonable in many ways (I use it somewhat, mainly to run win32 applications...and I need to network with it...) In many cases installation was pretty plug and chug and it seems much more reliable than windows 3.1... Just MHO. I really get miffed hearing people laud the robustness of NT and OS/2...I found both pale to current copies of linux and FreeBSD. thank you, marty From owner-freebsd-current Fri Jul 19 17:52:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA29623 for current-outgoing; Fri, 19 Jul 1996 17:52:37 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA29604; Fri, 19 Jul 1996 17:52:35 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id RAA04766; Fri, 19 Jul 1996 17:51:11 -0700 (PDT) Message-Id: <199607200051.RAA04766@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Marty Leisner" cc: "Craig Shaver" , freebsd-chat@freebsd.org, current@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-reply-to: Your message of "Fri, 19 Jul 1996 17:27:41 PDT." <9607200027.AA14374@gemini.sdsp.mc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Jul 1996 17:51:11 -0700 From: Amancio Hasty Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While working at M/Cast a couple of months ago, Win95 tended to crash oh about 5 to 10 times a day during development of the multimedia apps. A bad transceiver brought to its knees all the Win95 PCs. The sun boxes and the FreeBSD seemed to happily continue working. I guess if you don't use Win95 for development is an okay platform. Amancio From owner-freebsd-current Fri Jul 19 17:55:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA00283 for current-outgoing; Fri, 19 Jul 1996 17:55:13 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA00278; Fri, 19 Jul 1996 17:55:11 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id RAA04779; Fri, 19 Jul 1996 17:53:46 -0700 (PDT) Message-Id: <199607200053.RAA04779@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Marty Leisner" cc: "Craig Shaver" , freebsd-chat@freebsd.org, current@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-reply-to: Your message of "Fri, 19 Jul 1996 17:27:41 PDT." <9607200027.AA14374@gemini.sdsp.mc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Jul 1996 17:53:45 -0700 From: Amancio Hasty Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Marty Leisner" : > I really get miffed hearing people laud the robustness of NT and OS/2...I fou nd > both pale to current copies of linux and FreeBSD. > Well, it depends on your point of view. Yes Linux and FreeBSD are probably more robust than NT or OS/2 however from a DOS and Win3.1 point of view NT is rock solid 8) Regards, Amancio From owner-freebsd-current Fri Jul 19 18:09:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA00975 for current-outgoing; Fri, 19 Jul 1996 18:09:38 -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 SAA00969 for ; Fri, 19 Jul 1996 18:09:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id SAA15375; Fri, 19 Jul 1996 18:09:26 -0700 (PDT) Message-Id: <199607200109.SAA15375@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Mike Tsirulnikov cc: freebsd-current@freebsd.org, scott@cns.ucla.edu, "Scott A. Harvey" , marc@cns.ucla.edu Subject: Re: Fatal trap 12: page fault while in kernel mode In-reply-to: Your message of "Fri, 19 Jul 1996 11:36:34 PDT." From: David Greenman Reply-To: davidg@root.com Date: Fri, 19 Jul 1996 18:09:26 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >We have been running FreeBSD 2.1 on Pentium 200 MHz machine for >a while now and this is the first time it died like this. >Below is what kernel logged to the screen: > >fault virtual address = 0x8 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xf0110580 >code segment = base 0x0, limit 0xfffff, type 0x1b > DPL 0, pres 1, def32, gran 1 >processor e-flags = interrupt enabled, resume, IOPL=0 >current process = 13320 (top) >interrupt mask = > >panic: page fault > >Any help regarding how to avoid this type of crash is greatly >appreciated. This appears to be identical to a bug/panic that I fixed just prior to the 2.1.5 release. I suggest upgrading to 2.1.5. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Jul 19 18:25:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01686 for current-outgoing; Fri, 19 Jul 1996 18:25:42 -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 SAA01681 for ; Fri, 19 Jul 1996 18:25:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id SAA15452; Fri, 19 Jul 1996 18:25:17 -0700 (PDT) Message-Id: <199607200125.SAA15452@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org, scott@cns.ucla.edu, sharvey@cns.ucla.edu, marc@cns.ucla.edu, mt@cns.ucla.edu Subject: Re: Fatal trap 12: page fault while in kernel mode In-reply-to: Your message of "Fri, 19 Jul 1996 23:28:55 +0200." <199607192128.XAA00672@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@root.com Date: Fri, 19 Jul 1996 18:25:17 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The fault happens inside sys/kern/kern_sysctl.c, in function >fill_eproc(), here: > > if (SESS_LEADER(p)) > ^^^^^^^^^^^^^^ > ep->e_flag |= EPROC_SLEADER; Like I said in a previous message, I already fixed this prior to 2.1.5. All you need to do is upgrade. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Jul 19 19:05:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03983 for current-outgoing; Fri, 19 Jul 1996 19:05:41 -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 TAA03976 for ; Fri, 19 Jul 1996 19:05:35 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id WAA17886; Fri, 19 Jul 1996 22:02:12 -0400 From: Bill Paul Message-Id: <199607200202.WAA17886@skynet.ctr.columbia.edu> Subject: Re: /usr/bin/passwd and finger output To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Fri, 19 Jul 1996 22:02:10 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: from "Veggy Vinny" at Jul 19, 96 03:10:29 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Veggy Vinny had to walk into mine and say: [chop] > > > dennis@mercury [1:45pm][~] >> passwd > > > passwd: Permission denied > > > dennis@mercury [1:45pm][~] >> dir /usr/bin/passwd > > > -r-sr-xr-x 2 root bin 32768 Jul 19 12:45 /usr/bin/passwd > > > dennis@mercury [1:45pm][~] >> > > > > How about trying 'which passwd' and seeing what it returns? How > > about trying to run /usr/bin/passwd explicitly (with the full path)? > > You sure you don't have a /usr/local/bin/passwd or a cutsey alias > > hidden away somewhere? > > yep, because this is what I got: > > dennis@mercury [2:57pm][~] >> which passwd > /usr/bin/passwd > dennis@mercury [2:57pm][~] >> dir /usr/local/bin/passwd > colorls: /usr/local/bin/passwd: No such file or directory > dennis@mercury [2:58pm][~] >> How about echo $USER? Okay, after playing around a bit, I could only find set of circumstances where passwd(1) would say 'Permission denied' persistently. Unfortunately, I don't think this is the cause of your problem. Here's the deal: - When passwd starts up, it does a getlogin() in order to determine the username of the user that invoked the command. (This can be overriden by the superuser, who is allowed to specify a username on the command line.) - Since passwd is compiled with YP support, it later calls use_yp() with the name of the user to do an exhaustive check to figure out if the user is local, YP or both. This also fills in a passwd struct called local_passwd. - Since the user is local, local_passwd() is called. The first thing local_passwd() does it call getuid(), and then it compares the UID that getuid() returns against the UID in the local_password struct. Now here's the problem. Let's say I log in as user wpaul. If I then run a program that calls getlogin(), the result will be "wpaul". Now let's say I su to some other user. If I again run a program that calls getlogin(), the result will still be "wpaul". So here's what happens with passwd: - I log in as wpaul and su to user foo. - passwd calls getlogin() and gets back 'wpaul'. use_yp() fills in local_password with the info for user 'wpaul'. - local_passwd() calls getuid() and it gets back the UID for user 'foo'. - local_passwd then compares the UID returned by getuid() and local_password.pw_uid and sees that they don't match (getuid() returns the UID for user 'foo' while local_password.pw_uid contains the UID of user 'wpaul'). - Since the UIDs don't match, and the user is not root, passwd exits with EACCES ("permission denied"). I'm not sure if this is the cause of your problem or not. If you actually log in as a user rather than using su, passwd works correctly because getlogin() and getuid() agree. > Hmmm, this happened after the code change to chpass and passwd for > the sources a week or so ago. Hurm. Not sure if that's related. I really need to test this on a -current box. -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 Fri Jul 19 20:06:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA06332 for current-outgoing; Fri, 19 Jul 1996 20:06:53 -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 UAA06326 for ; Fri, 19 Jul 1996 20:06:50 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id UAA15049; Fri, 19 Jul 1996 20:07:11 -0700 Date: Fri, 19 Jul 1996 20:07:09 -0700 (PDT) From: Veggy Vinny To: Bill Paul cc: current@freebsd.org Subject: Re: /usr/bin/passwd and finger output In-Reply-To: <199607200202.WAA17886@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Veggy Vinny had > to walk into mine and say: > > [chop] > > > > dennis@mercury [1:45pm][~] >> passwd > > > > passwd: Permission denied > > > > dennis@mercury [1:45pm][~] >> dir /usr/bin/passwd > > > > -r-sr-xr-x 2 root bin 32768 Jul 19 12:45 /usr/bin/passwd > > > > dennis@mercury [1:45pm][~] >> > > > > > > How about trying 'which passwd' and seeing what it returns? How > > > about trying to run /usr/bin/passwd explicitly (with the full path)? > > > You sure you don't have a /usr/local/bin/passwd or a cutsey alias > > > hidden away somewhere? > > > > yep, because this is what I got: > > > > dennis@mercury [2:57pm][~] >> which passwd > > /usr/bin/passwd > > dennis@mercury [2:57pm][~] >> dir /usr/local/bin/passwd > > colorls: /usr/local/bin/passwd: No such file or directory > > dennis@mercury [2:58pm][~] >> > > How about echo $USER? > > Okay, after playing around a bit, I could only find set of circumstances > where passwd(1) would say 'Permission denied' persistently. Unfortunately, > I don't think this is the cause of your problem. Here's the deal: > > - When passwd starts up, it does a getlogin() in order to determine > the username of the user that invoked the command. (This can be > overriden by the superuser, who is allowed to specify a username > on the command line.) > > - Since passwd is compiled with YP support, it later calls use_yp() > with the name of the user to do an exhaustive check to figure out > if the user is local, YP or both. This also fills in a passwd struct > called local_passwd. > > - Since the user is local, local_passwd() is called. The first thing > local_passwd() does it call getuid(), and then it compares the > UID that getuid() returns against the UID in the local_password > struct. > > Now here's the problem. Let's say I log in as user wpaul. If I then > run a program that calls getlogin(), the result will be "wpaul". > Now let's say I su to some other user. If I again run a program > that calls getlogin(), the result will still be "wpaul". So here's > what happens with passwd: > > - I log in as wpaul and su to user foo. > > - passwd calls getlogin() and gets back 'wpaul'. use_yp() fills in > local_password with the info for user 'wpaul'. > > - local_passwd() calls getuid() and it gets back the UID for user > 'foo'. > > - local_passwd then compares the UID returned by getuid() and > local_password.pw_uid and sees that they don't match (getuid() > returns the UID for user 'foo' while local_password.pw_uid > contains the UID of user 'wpaul'). > > - Since the UIDs don't match, and the user is not root, passwd > exits with EACCES ("permission denied"). > > I'm not sure if this is the cause of your problem or not. If you > actually log in as a user rather than using su, passwd works correctly > because getlogin() and getuid() agree. > > > Hmmm, this happened after the code change to chpass and passwd for > > the sources a week or so ago. > > Hurm. Not sure if that's related. I really need to test this on > a -current box. You're right about this one except I logged in as user vince then su to root so then I su -l dennis and then did the passwd, this used to work in -current as of 1.5 weeks ago but is there anyway around this? Vince From owner-freebsd-current Fri Jul 19 21:12:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA11477 for current-outgoing; Fri, 19 Jul 1996 21:12:25 -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 VAA11466 for ; Fri, 19 Jul 1996 21:12:18 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA18109; Sat, 20 Jul 1996 00:08:51 -0400 From: Bill Paul Message-Id: <199607200408.AAA18109@skynet.ctr.columbia.edu> Subject: Re: /usr/bin/passwd and finger output To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Sat, 20 Jul 1996 00:08:50 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: from "Veggy Vinny" at Jul 19, 96 08:07:09 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Veggy Vinny had to walk into mine and say: [passwd mysteriously exits with 'permission denied'] > > Now here's the problem. Let's say I log in as user wpaul. If I then > > run a program that calls getlogin(), the result will be "wpaul". > > Now let's say I su to some other user. If I again run a program > > that calls getlogin(), the result will still be "wpaul". So here's > > what happens with passwd: > > > > - I log in as wpaul and su to user foo. > > > > - passwd calls getlogin() and gets back 'wpaul'. use_yp() fills in > > local_password with the info for user 'wpaul'. > > > > - local_passwd() calls getuid() and it gets back the UID for user > > 'foo'. > > > > - local_passwd then compares the UID returned by getuid() and > > local_password.pw_uid and sees that they don't match (getuid() > > returns the UID for user 'foo' while local_password.pw_uid > > contains the UID of user 'wpaul'). > > > > - Since the UIDs don't match, and the user is not root, passwd > > exits with EACCES ("permission denied"). > > > > I'm not sure if this is the cause of your problem or not. If you > > actually log in as a user rather than using su, passwd works correctly > > because getlogin() and getuid() agree. > > > > > Hmmm, this happened after the code change to chpass and passwd for > > > the sources a week or so ago. > > > > Hurm. Not sure if that's related. I really need to test this on > > a -current box. > > You're right about this one Yes, but magically extracting the information from your brain from such a great distance cost me dearly in terms of spells and power. I may have to sacrifice you to the shub internet now in order to make up for it. (Being a sysadmin requires you to also be part detective; nobody ever gives you the full story in an initial problem report. Consequently, I often interrogate people at length before I even begin any troubleshooting. This helps me avoid situations like the following: user: "Help! I turned on my PC today and all my files are gone!" me : (spend several fruitless hours going over the disk with data recovery tools and generally pulling my hair out) user: "Oh, by the way, I swapped the hard drive last night. Does that matter?" me : [CENSORED]) > except I logged in as user vince then > su to root so then I su -l dennis and then did the passwd, this used to > work in -current as of 1.5 weeks ago but is there anyway around this? I don't think the behavior manifested itself 1.5 weeks ago. I think it's been there all along and you just didn't notice it until 1.5 weeks ago. This behavior has been inherent in passwd(1) for a long time (well before NIS support was added, in case anyone's wondering). It even makes a twisted kind of sense: since you logged in as user vince this implies that you know user vince's password, not user dennis's password. (And if you're going to cheat by (ab)using the root account to become user dennis, you should probably just change the password as root anyway and save a step.) To answer your question, there are couple of 'workarounds': 1) Don't su to user 'dennis': log in as user 'dennis' directly. It should work correctly then. (This implies that you know this user's password. Basically this means that user dennis should not have any trouble changing his password when he logs in as normal.) 2) If you must su to 'dennis,' invoke passwd with that username as an argument: % passwd dennis Specifying a username should override the value returned by getlogin() and then everything should agree. (Kick yourself if you didn't think to try this until now. :) Note that if run 'passwd dennis' as user vince, you will once again get a 'permission denied' error, this time for the right reason. 3) Log in as 'vince,' then su to root, then change the password for user 'dennis' as root: # passwd dennis As an added bonus, you'll be able to set a new password without knowing the old one. 4) If you really dislike the behavior, edit local_passwd.c: find the test where it compares uid to pw->pw_uid and comment it out. Then recompile and reinstall passwd. (Isn't source code fun?) -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 Fri Jul 19 21:19:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12160 for current-outgoing; Fri, 19 Jul 1996 21:19:46 -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 VAA12149 for ; Fri, 19 Jul 1996 21:19:44 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id VAA18094; Fri, 19 Jul 1996 21:19:32 -0700 Date: Fri, 19 Jul 1996 21:19:30 -0700 (PDT) From: Veggy Vinny To: Bill Paul cc: current@freebsd.org Subject: Re: /usr/bin/passwd and finger output In-Reply-To: <199607200408.AAA18109@skynet.ctr.columbia.edu> 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, 20 Jul 1996, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Veggy Vinny had > to walk into mine and say: > > [passwd mysteriously exits with 'permission denied'] > > > > Now here's the problem. Let's say I log in as user wpaul. If I then > > > run a program that calls getlogin(), the result will be "wpaul". > > > Now let's say I su to some other user. If I again run a program > > > that calls getlogin(), the result will still be "wpaul". So here's > > > what happens with passwd: > > > > > > - I log in as wpaul and su to user foo. > > > > > > - passwd calls getlogin() and gets back 'wpaul'. use_yp() fills in > > > local_password with the info for user 'wpaul'. > > > > > > - local_passwd() calls getuid() and it gets back the UID for user > > > 'foo'. > > > > > > - local_passwd then compares the UID returned by getuid() and > > > local_password.pw_uid and sees that they don't match (getuid() > > > returns the UID for user 'foo' while local_password.pw_uid > > > contains the UID of user 'wpaul'). > > > > > > - Since the UIDs don't match, and the user is not root, passwd > > > exits with EACCES ("permission denied"). > > > > > > I'm not sure if this is the cause of your problem or not. If you > > > actually log in as a user rather than using su, passwd works correctly > > > because getlogin() and getuid() agree. > > > > > > > Hmmm, this happened after the code change to chpass and passwd for > > > > the sources a week or so ago. > > > > > > Hurm. Not sure if that's related. I really need to test this on > > > a -current box. > > > > You're right about this one > > Yes, but magically extracting the information from your brain from > such a great distance cost me dearly in terms of spells and power. > I may have to sacrifice you to the shub internet now in order to make > up for it. > > (Being a sysadmin requires you to also be part detective; nobody > ever gives you the full story in an initial problem report. Consequently, > I often interrogate people at length before I even begin any > troubleshooting. This helps me avoid situations like the following: > > user: "Help! I turned on my PC today and all my files are gone!" > me : (spend several fruitless hours going over the disk with > data recovery tools and generally pulling my hair out) > user: "Oh, by the way, I swapped the hard drive last night. Does > that matter?" > me : [CENSORED]) > > > except I logged in as user vince then > > su to root so then I su -l dennis and then did the passwd, this used to > > work in -current as of 1.5 weeks ago but is there anyway around this? > > I don't think the behavior manifested itself 1.5 weeks ago. I think > it's been there all along and you just didn't notice it until 1.5 > weeks ago. This behavior has been inherent in passwd(1) for a long > time (well before NIS support was added, in case anyone's wondering). > It even makes a twisted kind of sense: since you logged in as user > vince this implies that you know user vince's password, not user > dennis's password. (And if you're going to cheat by (ab)using the > root account to become user dennis, you should probably just change > the password as root anyway and save a step.) > > To answer your question, there are couple of 'workarounds': > > 1) Don't su to user 'dennis': log in as user 'dennis' directly. It > should work correctly then. (This implies that you know this > user's password. Basically this means that user dennis should > not have any trouble changing his password when he logs in > as normal.) I did this a few days ago since Dennis was visiting me so he was trying to change his password and it didn't work.... I did use passwd dennis from root to do it anyways. > 2) If you must su to 'dennis,' invoke passwd with that username as > an argument: > > % passwd dennis > > Specifying a username should override the value returned by > getlogin() and then everything should agree. (Kick yourself > if you didn't think to try this until now. :) Note that if > run 'passwd dennis' as user vince, you will once again get > a 'permission denied' error, this time for the right reason. Hmmm, but if I su -l dennis from root, I thought passwd dennis isn't supposed to work. > 3) Log in as 'vince,' then su to root, then change the password for > user 'dennis' as root: > > # passwd dennis This is what I did but it was just weird that it didn't work when he logged in directly to his account and passwd returns permission denied. > As an added bonus, you'll be able to set a new password without > knowing the old one. > > 4) If you really dislike the behavior, edit local_passwd.c: find > the test where it compares uid to pw->pw_uid and comment it out. > Then recompile and reinstall passwd. (Isn't source code fun?) Oh well, it's not that big of a deal. I just remember doing a passwd from a su -l username from root as it used to work.... Vince From owner-freebsd-current Fri Jul 19 21:33:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12737 for current-outgoing; Fri, 19 Jul 1996 21:33:43 -0700 (PDT) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA12732; Fri, 19 Jul 1996 21:33:40 -0700 (PDT) Received: from localhost by troll.uunet.ca with SMTP id <21012-4511>; Sat, 20 Jul 1996 00:33:29 -0400 Date: Sat, 20 Jul 1996 00:33:26 -0400 From: Cat Okita To: Marty Leisner cc: Craig Shaver , freebsd-chat@freebsd.org, current@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-Reply-To: <9607200027.AA14374@gemini.sdsp.mc.xerox.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 Fri, 19 Jul 1996, Marty Leisner wrote: > NT is fine in many regards...but I just have an NT 3.51 installation go south, > and the "repair" mode can't seem to find my CD-ROM... (...) > I found win95 pretty reasonable in many ways (I use it somewhat, mainly to > run win32 applications...and I need to network with it...) In many cases > installation was pretty plug and chug and it seems much more reliable than > windows 3.1... ...except Win95 isn't reliable on a network at all, has no concept of user or file level secrity, and a spectacularly useless debug mode... Personally, I'm miles happier with the 'hybrid' network we have, which includes PC's running NT, BSDi, FreeBSD and Solaris x86, together with a variety of servers running IRIX, SunOS, Solaris and OSF/1. The only thing we use Win95 for is laptops, since they're often required to run standalone. This takes care of the sales/marketing/admin folk, who think that unix is scary, and aren't too sure about PC's at all, as well as the techies who'd die if they didn't have unix... Both NT and Unix have appropriate places for use...and appropriate users... Cat From owner-freebsd-current Fri Jul 19 21:41:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA13360 for current-outgoing; Fri, 19 Jul 1996 21:41:51 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA13352; Fri, 19 Jul 1996 21:41:47 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id VAA20333; Fri, 19 Jul 1996 21:41:12 -0700 (PDT) Message-Id: <199607200441.VAA20333@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Craig Shaver" cc: freebsd-chat@freebsd.org, current@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-reply-to: Your message of Fri, 19 Jul 96 15:40:44 -0700. <199607192240.PAA06649@seabass.progroup.com> Date: Fri, 19 Jul 1996 21:41:12 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > >> >I'm still trying to understand why people think they have to run NT. >> >There are other options, like FreeBSD and OS/2. A lot cheaper and not >> >made by Microsoft. >> > >> Because NT is a very solid server OS. It is tightly integrated with >> the most popular application server software, Microsoft BackOffice. >> It is *the* most stable OS I have run. It scales well across multiple >> CPUs, and has a very solid multi-processor and multi-threaded kernel. >> NT 4.0 will have not only dynamically scheduled threads, but user- >blah, blah, blah, on and on .... del ...... >Ok, NT is better than windog 3.1 and wingding95. I am working on a >project that uses NT 3.51 backends for a proprietary database that was [...] >The NT's work ok until something unforseen happens. Back in April we Everything can potentially have problems when something unforseen happens. It would be hard to anticipate something you can't forsee. >had a power outage. The Sparc rebooted automatically and all of the rc >scripts started all of the background daemons and everything worked. No >humans needed. The NT's sat there and refused to run anything until >some user logged in! Apparently there is no way to have a program >automatically run unless you log in and then you have something in that >little "start" window. Apparently you can spout a lot of nonsense about a subject you don't understand. Creating "services" (NT's version of "daemons") is a very well documented topic on the Microsoft Developer's Network. That's like telling you I don't think Unix can create processes because I never bothered to find the "fork" man page. >Nice design for a *server*! I guess if someone >uses NT for a server and the power goes down in the middle of the night, >then *someone* will have to be there to log in and start all of the server >processes. (snort, snicker, guffaw, ;^) Doubtful, since it would be totally unnecessary for a properly written and properly installed NT service. >(There may be a fix for this in service pak 4! :^) Generally, yes, that would be my first suggestion if you found a bug in NT. Microsoft releases publicly available fixes. Gee, I wonder if applying them would help at all. Of course, they wouldn't help your software restart if it wasn't written as a service, because that isn't a bug. For what it's worth, a large number of fixes in SP1 - SP4 were found while stress-testing Exchange server. I can indeed verify that the NT guys take stability as serious as a heart attack. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Fri Jul 19 22:10:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA14153 for current-outgoing; Fri, 19 Jul 1996 22:10:24 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA14147 for ; Fri, 19 Jul 1996 22:10:17 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAC20472 for ; Fri, 19 Jul 1996 22:10:07 -0700 (PDT) Message-Id: <199607200510.WAC20472@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol Date: Fri, 19 Jul 1996 22:10:02 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- Blind-Carbon-Copy To: "Marty Leisner" cc: "Craig Shaver" , freebsd-chat@freebsd.org Reply-To: freebsd-chat@freebsd.org Followup-To: freebsd-chat@FreeBSD.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-reply-to: Your message of Fri, 19 Jul 96 17:27:41 -0700. <9607200027.AA14374@gemini.sdsp.mc.xerox.com> Date: Fri, 19 Jul 1996 22:10:02 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Really, I don't see how this is very relevant to FreeBSD anymore, however. Further followups should really be done in private email, or to FreeBSD-chat. >>> > >>> >I'm still trying to understand why people think they have to run NT. >>> >There are other options, like FreeBSD and OS/2. A lot cheaper and not >>> >made by Microsoft. >>> > >>> Because NT is a very solid server OS. It is tightly integrated with [etc....] >>blah, blah, blah, on and on .... del ...... >I've had very negative experiences with OS/2. [...] >NT is fine in many regards...but I just have an NT 3.51 installation go south, >and the "repair" mode can't seem to find my CD-ROM... Yes, if you toast an NT system the recover process can sometimes bite. I have had to do clean installs occasionally. I sent email to the NT guys about it, they loved some of my suggestions, but suggested I write them because they have too many higher-priority things to worry about, first. Bummer, but such is life... >I also was writing some netbios/lanserver emulation code on another machine >(a sun) running TCP/IP. I obviously had a bug in my program (; -)) and it >seems I bought NT (3.51) to its knees with my bug (a panic). >Any OS where a buggy remote application can crash the machine is suspect >(yes, it can happen, but it points to architectural problems). Uh, if I nuked NetBSD and FreeBSD the first time they panic'd, I'd certainly be running something less exciting in their place. NT is software. Software has bugs. Period. NetBSD and FreeBSD also fall into this category. Personally, I think NetBSD and FreeBSD are really kick-ass gotta-have- it software. But, they're still software, and they still have bugs. Just like NT. I still stand by my statement that NT is the most reliable OS I have run. And I have developed an enormous amount of respect for it, after seeing some of the hell I've seen it run through. In our stress labs, we beat the crap out of Exchange. NT gets the crap beat out of it in the process. I've seen some pretty huge iron (4 processor 300MHz DEC Alphas with a couple hundred megabytes of RAM) pounded by and dishing out a hellish amount of RPC traffic, while a whole rack of RAID drives are going non-stop. (We're talking about hundreds of client machines running stress apps against a set of servers, who are also inter-communicating and replicating data at the same time.) And I have seen *very* few crashes. What's more, every OS crash has had an NT guy down there debugging it shortly after it happened. Understand that the NT guys do not take a single crash lightly. Incidentally, this very environment is where the majority of the fixes in NT 3.51 SP1 - SP4 where generated. Out of curiosity, did you have any of the service packs (preferably SP4) applied to that system you crashed? Were you able to reproduce the crash consistenly? >I found win95 pretty reasonable in many ways (I use it somewhat, mainly to >run win32 applications...and I need to network with it...) In many cases >installation was pretty plug and chug and it seems much more reliable than >windows 3.1... Well, yes, but Windows 95 is a multimedia home OS. We're talking about server OS's. >I really get miffed hearing people laud the robustness of NT and >OS/2... I found both pale to current copies of linux and FreeBSD. I really get miffed when I hear people dismiss NT off the cuff because they crashed Win 3.1 or Win 95, and/or they really haven't spent any time with NT. But, ignorance is bliss, I guess. I also would assert that NT doesn't belong in the same category with Windows 95 (a home multimedia OS), or OS/2 (a nice try, but... as you noted above). Though I love NetBSD and FreeBSD dearly, and I really get sick of some of the dumbed-down UI on Windows, I respect NT tremendously when it comes to running a reliable, industrial-strength OS. And I have developed that respect solely from watching the abuse it takes without incident, both on my test and development machines at work, and in the environments described above. - ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. - ----------------------------------------------------------------------------- ------- End of Blind-Carbon-Copy From owner-freebsd-current Fri Jul 19 22:15:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA14333 for current-outgoing; Fri, 19 Jul 1996 22:15:50 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA14328 for ; Fri, 19 Jul 1996 22:15:47 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAC20513 for ; Fri, 19 Jul 1996 22:15:45 -0700 (PDT) Message-Id: <199607200515.WAC20513@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol Date: Fri, 19 Jul 1996 22:15:44 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- Blind-Carbon-Copy To: Amancio Hasty cc: "Marty Leisner" , "Craig Shaver" , freebsd-chat@freebsd.org Followup-To: freebsd-chat@freebsd.org Reply-To: freebsd-chat@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES In-reply-to: Your message of Fri, 19 Jul 96 17:51:11 -0700. <199607200051.RAA04766@rah.star-gate.com> Date: Fri, 19 Jul 1996 22:15:44 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Once again, let's move this off current.... >While working at M/Cast a couple of months ago, Win95 tended to >crash oh about 5 to 10 times a day during development of the >multimedia apps. > >A bad transceiver brought to its knees all the Win95 PCs. The sun >boxes and the FreeBSD seemed to happily continue working. > >I guess if you don't use Win95 for development is an okay platform. Who asked you to? Windows 95 is a multimedia home OS. It is not supposed to be a serious development platform. It crashes, sometimes often. Everybody knows it crashes. (In case it isn't clear, you can develop Windows 95 apps on Windows NT. You only need Windows 95 to test them.) We were talking about server OS's. We were talking about Windows NT. We were not discussing home gaming platforms. Windows 95 is not Windows NT. - ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. - ----------------------------------------------------------------------------- ------- End of Blind-Carbon-Copy From owner-freebsd-current Fri Jul 19 23:07:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA17190 for current-outgoing; Fri, 19 Jul 1996 23:07:43 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA17185 for ; Fri, 19 Jul 1996 23:07:40 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA06336 (5.67a/IDA-1.5 for ); Sat, 20 Jul 1996 09:07:37 +0300 Received: (from count@localhost) by key.hole.fi (8.7.5/8.6.12) id JAA20284; Sat, 20 Jul 1996 09:07:36 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199607200607.JAA20284@key.hole.fi> Subject: Re: optical fiber PCI Ethernet adapter To: gea@masternet.it (Beck Peccoz Amedeo) Date: Sat, 20 Jul 1996 09:07:36 +0300 (EET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <31F03193.41C67EA6@masternet.it> from "Beck Peccoz Amedeo" at Jul 20, 96 03:08:35 am X-Mailer: ELM [version 2.4 PL24alpha5] 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 Beck Peccoz Amedeo taisi sanoa: > > I'm looking for a supported pci ethernet card with optical fiber > connectors. Has anyone ever used one? I know Allied Telesys makes > one (model 17xx), are there drivers for FreeBSD? The AT-1700 series cards are ISA cards, supported by fe driver. I have one on this box, works quite nicely. Allied Telesyn AT-2560TX is a 10/100Mbit PCI adapter, it works with fxp driver but there are some mysterious problems with high amount of input errors. I don't remember if there's also a fiber version of that PCI card, but I suppose that their web pages (at http://www.alliedtelesyn.com/) would tell that to you. -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Pengerkatu 13b A5 % IRC: Count NIC: BH271 % FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Sat Jul 20 00:21:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA21801 for current-outgoing; Sat, 20 Jul 1996 00:21:37 -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 AAA21786 for ; Sat, 20 Jul 1996 00:21:32 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA12091 for ; Sat, 20 Jul 1996 09:21:30 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA25705 for freebsd-current@FreeBSD.org; Sat, 20 Jul 1996 09:21:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA03329 for freebsd-current@FreeBSD.org; Sat, 20 Jul 1996 09:20:42 +0200 (MET DST) From: J Wunsch Message-Id: <199607200720.JAA03329@uriah.heep.sax.de> Subject: Re: /usr/bin/passwd and finger output To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 20 Jul 1996 09:20:41 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Veggy Vinny at "Jul 19, 96 08:07:09 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 Veggy Vinny wrote: > You're right about this one except I logged in as user vince then > su to root so then I su -l dennis and then did the passwd, this used to > work in -current as of 1.5 weeks ago but is there anyway around this? It should never have worked this way. If you verify the CVS file, you'll notice that it used getlogin() all the time to obtain the identity of the login user. As i wrote, i think this is in error, and it should use getuid. This has other ill side-effects however, for cases where you've got more than one user with the same UID. The optimal way would be perhaps to use getlogin(), but fall back to getuid() in case the login user has a different UID than the current user. -- 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 20 02:40:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA00213 for current-outgoing; Sat, 20 Jul 1996 02:40:05 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA00162; Sat, 20 Jul 1996 02:39:57 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id KAA00607; Sat, 20 Jul 1996 10:37:24 +0200 (MET DST) To: davidg@Root.COM cc: John Dyson , hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of "Thu, 18 Jul 1996 19:08:51 PDT." <199607190208.TAA13338@root.com> Date: Sat, 20 Jul 1996 10:37:23 +0200 Message-ID: <605.837851843@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> I did not get a dump, short of space on /var, it just had rebooted. >>> >>Chiming in here: David, do you think that this could be a kernel >>stack space problem? > > No. My analysis of wcarchive showed that stack growth never exceeds >2.6KB. I'm guessing that Heikki is using the "MMAP" option(s) in innd and is >stumbling over (kernel) bugs because of it. I have repeatedly hit another problem, CCD seems to screw up if you use shared libraries stored on a striped partition. This would maybe also affect other kinds of access with or without mmap in the loop. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sat Jul 20 10:38:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28522 for current-outgoing; Sat, 20 Jul 1996 10:38:36 -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 KAA28505 for ; Sat, 20 Jul 1996 10:38:32 -0700 (PDT) Received: (from root@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id DAA02511 for freebsd-current@freebsd.org; Sun, 21 Jul 1996 03:38:07 +1000 (EST) From: Ernie Elu Message-Id: <199607201738.DAA02511@spooky.eis.net.au> Subject: Make hierarchy stops To: freebsd-current@freebsd.org Date: Sun, 21 Jul 1996 03:38:06 +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 been trying to solve a problem with make hierarchy in -current failing for the last couple of weeks. I tracked it down to the copy of /usr/src/etc/Makefile on sup.au.freebsd.org being broken, it is only 2048 bytes long whereas the one on ftp.freebsd.org is 6156 bytes long. The real problem is for some reason sup does not try and replace the incomplete file with the proper one unless I delete the broken file first. It that correct behaviour for sup or nasty bug? I wonder how many other short files it had missed? - Ernie. From owner-freebsd-current Sat Jul 20 11:09:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA00760 for current-outgoing; Sat, 20 Jul 1996 11:09:57 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00747 for ; Sat, 20 Jul 1996 11:09:52 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id RAA06481; Sat, 20 Jul 1996 17:32:06 +0100 (BST) Date: Sat, 20 Jul 1996 17:32:05 +0100 (BST) From: Developer To: Bill Paul cc: freebsd-current@freebsd.org Subject: Re: Help on setting up yp/nis In-Reply-To: <199607181747.NAA14490@skynet.ctr.columbia.edu> 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, 18 Jul 1996, Bill Paul wrote: > For the umpity-umpth time: read the passwd(5) man page. (That's passwd(5), > not passwd(1); 'man 5 passwd'.) It explains quite clearly how to set up a > client to use the NIS passwd maps (and how not to do it). > > If, after reading this man page, you still have specific questions, > come back and ask them and I'll try to help. Thanks for the information, I didn't know there was a mention in the passwd man page - Ive just about got things sorted now after spending ages altering user id's so they don't clash *sigh* A couple of quick question.. what is the recommended way of handling users email? Does the NIS server always update the password database (/etc/passwd) as well as the yp version or can those be seperate? Thanks again. Trefor S. From owner-freebsd-current Sat Jul 20 11:16:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01583 for current-outgoing; Sat, 20 Jul 1996 11:16:26 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA01570 for ; Sat, 20 Jul 1996 11:16:23 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id LAA24104; Sat, 20 Jul 1996 11:15:17 -0700 (PDT) Message-Id: <199607201815.LAA24104@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Poul-Henning Kamp cc: davidg@root.com, John Dyson , hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of Sat, 20 Jul 96 10:37:23 +0200. <605.837851843@critter.tfs.com> Date: Sat, 20 Jul 1996 11:15:15 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> I did not get a dump, short of space on /var, it just had rebooted. >>>Chiming in here: David, do you think that this could be a kernel >>>stack space problem? >> No. My analysis of wcarchive showed that stack growth never exceeds >>2.6KB. I'm guessing that Heikki is using the "MMAP" option(s) in innd and is >>stumbling over (kernel) bugs because of it. >I have repeatedly hit another problem, CCD seems to screw up if you use >shared libraries stored on a striped partition. This would maybe also >affect other kinds of access with or without mmap in the loop. Could you be more specific about how and when ccd screws up in this situation? I've been running my entire /usr (shared libraries, bins, and all) on ccd for almost a year. Granted, it's NetBSD, but they're not *that* different, are they? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Sat Jul 20 11:49:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05438 for current-outgoing; Sat, 20 Jul 1996 11:49:15 -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 LAA05413 for ; Sat, 20 Jul 1996 11:49:06 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA20691; Sat, 20 Jul 1996 14:45:33 -0400 From: Bill Paul Message-Id: <199607201845.OAA20691@skynet.ctr.columbia.edu> Subject: Re: Help on setting up yp/nis To: dev@fgate.flevel.co.uk (Developer) Date: Sat, 20 Jul 1996 14:45:32 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: from "Developer" at Jul 20, 96 05:32:05 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Developer had to walk into mine and say: > On Thu, 18 Jul 1996, Bill Paul wrote: > > > For the umpity-umpth time: read the passwd(5) man page. (That's passwd(5), > > not passwd(1); 'man 5 passwd'.) It explains quite clearly how to set up a > > client to use the NIS passwd maps (and how not to do it). > > > > If, after reading this man page, you still have specific questions, > > come back and ask them and I'll try to help. > > Thanks for the information, I didn't know there was a mention in the > passwd man page - Ive just about got things sorted now after spending ages > altering user id's so they don't clash *sigh* > > A couple of quick question.. what is the recommended way of handling users > email? Does the NIS server always update the password database > (/etc/passwd) as well as the yp version or can those be seperate? I'm not sure I understand what you mean. You seem to be asking two different questions here. If you have a multi-machine environment with a shared user database (i.e. NIS), it's usually best to set up one machine as the mail server and use MX records to forward mail sent to other machines in your network to the mail server rather than letting them handle mail themselves. One my network, I have a single machine designated as the mail host (you could do more to spread out the load, if your network is very large) and all the 'client' machines mount its /var/spool/mail directory via NFS (and the automounter). Each 'client' is also set up as a sendmail 'null client': if you send mail from one of them, it gets forwarded first to the mail host, and then the mail host forwards it to its final destination. The mail host also strips out the hostname of the 'client' machine from the header so that all outgoing mail appears to come from 'user@ctr.columbia.edu' rather than 'user@host.ctr.columbia.edu'. This means that all replies will automatically be sent back to the mail host rather than the 'clients.' Each 'client' also has an MX record that points to the mail host, so any mail sent to 'user@host.ctr.columbia.edu' is re-routed to 'user@mailhost.ctr.columbia.edu'. The mail host is the only machine on the network that runs sendmail in daemon mode, thus only it can accept inbound mail anyway. (The other machines do run sendmail in the background, but only with the -q30m flag. This allows them to flush their queue directories every so often, just in case.) To read mail, all a user has to do is log into any 'client' host and run their favorite mailer. As for your second question, the NIS password database and the local database (/etc/master.passwd) are seperate. By adding the +::::::::: entry to the end of /etc/master.passwd, you tell the system to augment the local password database with the information in the NIS maps. You are allowed to have users that exist in the local database only, but obviously these users will only be able to log into the one machine where their password database entries exist. They will also be unable to receive any mail except on the machine where their local entry exists. (For example, if your NIS master server and mailhost is called 'mailhost' and you define a user 'foo' on a machine called 'mailclient' and 'mailclient' has an MX record that sends all its mail to 'mailhost,' mailhost will not know that user 'foo' exists and reject all mail for user 'foo' with a "user unknown" error.) It's probably a good idea to have locally defined users appear before the +::::::::: entry; this will cause the local entry to take precedence over an entry in the NIS maps that happens to have the same username. (You want to avoid having both local and NIS users with the same username, however.) -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 Sat Jul 20 13:35:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13760 for current-outgoing; Sat, 20 Jul 1996 13:35:48 -0700 (PDT) Received: from relay-5.mail.demon.net (relay-5.mail.demon.net [158.152.1.48]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13749 for ; Sat, 20 Jul 1996 13:35:43 -0700 (PDT) Received: from post.demon.co.uk by relay-5.mail.demon.net id ac13256; 20 Jul 96 20:51 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa20701; 20 Jul 96 20:25 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id RAA03510; Sat, 20 Jul 1996 17:39:03 GMT From: James Raynard Message-Id: <199607201739.RAA03510@jraynard.demon.co.uk> Subject: Typo in /usr/src/Makefile? To: freebsd-current@freebsd.org Date: Sat, 20 Jul 1996 17:39:02 +0000 () X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Am I missing something here? --- Makefile.orig Sat Jul 20 17:34:17 1996 +++ Makefile Sat Jul 20 17:34:41 1996 @@ -312,7 +312,7 @@ cd ${.CURDIR}/lib && \ ${MAKE} ${MK_FLAGS} depend all install ${CLEANDIR} ${OBJDIR} .endif -.if exists(usr.sbin/lex/lib) +.if exists(usr.bin/lex/lib) cd ${.CURDIR}/usr.bin/lex/lib && \ ${MAKE} ${MK_FLAGS} depend all install ${CLEANDIR} ${OBJDIR} .endif From owner-freebsd-current Sat Jul 20 13:51:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15293 for current-outgoing; Sat, 20 Jul 1996 13:51:45 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA15268; Sat, 20 Jul 1996 13:51:37 -0700 (PDT) Received: from critter.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA00658; Sat, 20 Jul 1996 22:51:19 +0200 (MET DST) To: "Michael L. VanLoon -- HeadCandy.com" cc: davidg@root.com, John Dyson , hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of "Sat, 20 Jul 1996 11:15:15 PDT." <199607201815.LAA24104@MindBender.HeadCandy.com> Date: Sat, 20 Jul 1996 22:51:17 +0200 Message-ID: <656.837895877@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I have repeatedly hit another problem, CCD seems to screw up if you use >>shared libraries stored on a striped partition. This would maybe also >>affect other kinds of access with or without mmap in the loop. > >Could you be more specific about how and when ccd screws up in this >situation? I've been running my entire /usr (shared libraries, bins, >and all) on ccd for almost a year. Granted, it's NetBSD, but they're >not *that* different, are they? Well, it's absolutely reproducible for me. I stripe a partition over some disks (2 & 3 have been tried) and run a cd /usr/src/release make release which points over there. It will usually get all the way through the "make world" in the chrooted env and then die when the tar-balls are rolled. I usually can find some of the shlibs have some number of corrupt/ wrong pages in them, and sometimes these will persist over reboot. This only happens when CCD is used. I hope John and David will find time to look over this some time. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sat Jul 20 16:48:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24778 for current-outgoing; Sat, 20 Jul 1996 16:48:43 -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 QAA24771 for ; Sat, 20 Jul 1996 16:48:39 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id XAA06918 for freebsd-current@freebsd.org; Sat, 20 Jul 1996 23:48:24 GMT From: Adam David Message-Id: <199607202348.XAA06918@veda.is> Subject: missed SIGALRM To: freebsd-current@freebsd.org Date: Sat, 20 Jul 1996 23:48:22 +0000 (GMT) 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 have noticed that a SIGALRM can sometimes be missed altogether under certain conditions, perhaps as a side-effect of heavy machine load. I am looking into this problem, and any other datapoints/suggestions are welcome. The following program (in its more complete version) stops doing its stuff once in a while (typically once a day or more often) and needs to be restarted as a result. The likelihood of this occuring seems related to periods of heavy system load. int tick; handler() { tick = 1; } set_tick() { tick = 0; signal(SIGALRM, handler); alarm(1); } get_tick() { return tick; } main() { set_tick(); for (;;) { if (get_tick()) { /* do stuff */ set_tick(); } } } -- Adam David From owner-freebsd-current Sat Jul 20 16:53:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA25123 for current-outgoing; Sat, 20 Jul 1996 16:53:57 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA24946 for ; Sat, 20 Jul 1996 16:50:41 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id QAA24961; Sat, 20 Jul 1996 16:47:37 -0700 (PDT) Message-Id: <199607202347.QAA24961@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Bill Paul cc: dev@fgate.flevel.co.uk (Developer), current@freebsd.org Subject: Re: Help on setting up yp/nis In-reply-to: Your message of Sat, 20 Jul 96 14:45:32 -0400. <199607201845.OAA20691@skynet.ctr.columbia.edu> Date: Sat, 20 Jul 1996 16:47:36 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On my network, I have a single machine designated as the mail host >(you could do more to spread out the load, if your network is very >large) and all the 'client' machines mount its /var/spool/mail >directory via NFS (and the automounter). Each 'client' is also set >up as a sendmail 'null client': if you send mail from one of them, >it gets forwarded first to the mail host, and then the mail host >forwards it to its final destination. The mail host also strips out >the hostname of the 'client' machine from the header so that all >outgoing mail appears to come from 'user@ctr.columbia.edu' rather >than 'user@host.ctr.columbia.edu'. This means that all replies will >automatically be sent back to the mail host rather than the 'clients.' This is a lot of extra work for the "mail hub". You can configure it so that all the client machines send mail directly to its destination, without bogging down the mail hub, and still masquarade, so the mail appears to come from user@ctr.columbia.edu. When I worked at Iowa State, we did it just like that. We had a single mail hub that received all mail destined for iastate.edu, with backups in case it failed. It then distributed the mail to several internal pop servers. This works better than NFS mounting /var/mail. All user accounts were mounted over AFS, so it didn't matter which host were were logged into when you retrieved your mail (we used mh, with kerberos authentication). There were roughly 850 workstations. All of them were configured to send mail directly out, and masquarade it as coming from user@iastate.edu. This would have been an enourmous amount of unecessary load if we had funneled all that traffic into, and back out our mail hub. And it wouldn't have bought us any extra functionality. >Each 'client' also has an MX record that points to the mail host, >so any mail sent to 'user@host.ctr.columbia.edu' is re-routed to >'user@mailhost.ctr.columbia.edu'. The mail host is the only machine >on the network that runs sendmail in daemon mode, thus only it >can accept inbound mail anyway. (The other machines do run sendmail >in the background, but only with the -q30m flag. This allows them >to flush their queue directories every so often, just in case.) We didn't do this. Since all outgoing mail was, by default, masquaraded as coming from user@iastate.edu, it would come back to our mail hub, automatically, if replied to. We did not have MX records for *.iastate.edu. The reason was that by default, the workstations wouldn't receive mail, and would bounce it back (best anyway -- it would let people know they mis-addressed the mail, rather than silently letting them continue doing so). And, if the admin of a particular machine, or subnet of machines, *wanted* to receive email locally, they could do so without having to involve the adminstration of the Computation Center. For what it's worth, we didn't use NIS. We used Athena based distributed adminstration (hesiod, kerberos, moira, etc.). IMHO, NIS would have been a nightmare for that large of an environment. The Athena stuff worked really well, for the most part. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Sat Jul 20 19:27:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03724 for current-outgoing; Sat, 20 Jul 1996 19:27:47 -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 TAA03715 for ; Sat, 20 Jul 1996 19:27:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA16881; Sat, 20 Jul 1996 19:24:47 -0700 (PDT) Message-Id: <199607210224.TAA16881@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Poul-Henning Kamp cc: "Michael L. VanLoon -- HeadCandy.com" , John Dyson , hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of "Sat, 20 Jul 1996 22:51:17 +0200." <656.837895877@critter.tfs.com> From: David Greenman Reply-To: davidg@root.com Date: Sat, 20 Jul 1996 19:24:47 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>I have repeatedly hit another problem, CCD seems to screw up if you use >>>shared libraries stored on a striped partition. This would maybe also >>>affect other kinds of access with or without mmap in the loop. >> >>Could you be more specific about how and when ccd screws up in this >>situation? I've been running my entire /usr (shared libraries, bins, >>and all) on ccd for almost a year. Granted, it's NetBSD, but they're >>not *that* different, are they? > >Well, it's absolutely reproducible for me. I stripe a partition over >some disks (2 & 3 have been tried) and run a > cd /usr/src/release > make release >which points over there. >It will usually get all the way through the "make world" in the >chrooted env and then die when the tar-balls are rolled. > >I usually can find some of the shlibs have some number of corrupt/ >wrong pages in them, and sometimes these will persist over reboot. > >This only happens when CCD is used. > >I hope John and David will find time to look over this some time. Just a wild guess: The vop_bmap() code in it is probably broken. We rely heavily on this and if it's broken, the filesystem will be corrupted. NetBSD won't suffer from this because they have much more limited use of the vop_bmap function. Further guessing, I'd guess that the problem is that CCD doesn't limit the forward/behind contiguousness to be within the underlying device's cluster, or something of this nature. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sat Jul 20 21:02:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA10021 for current-outgoing; Sat, 20 Jul 1996 21:02:35 -0700 (PDT) Received: from mixer.visi.com (root@mixer.visi.com [204.73.178.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA10003 for ; Sat, 20 Jul 1996 21:02:32 -0700 (PDT) Received: from undquirt.visi.com (undquirt.visi.com [206.11.194.26]) by mixer.visi.com (8.7.4/8.7.5) with SMTP id XAA20220 for ; Sat, 20 Jul 1996 23:02:29 -0500 (CDT) Posted-Date: Sat, 20 Jul 1996 23:02:29 -0500 (CDT) Received: by undquirt.visi.com with Microsoft Mail id <01BB768F.78EB2D60@undquirt.visi.com>; Sat, 20 Jul 1996 23:02:06 -0500 Message-ID: <01BB768F.78EB2D60@undquirt.visi.com> From: "Brent J. Nordquist" To: "'freebsd-current@freebsd.org'" Subject: cu(1) stopped working? Date: Sat, 20 Jul 1996 23:01:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Suddenly in the latest sup of -current (Jul. 18) cu reports "Device not = configured" and that it's locked, but there are no lock files (I can't = believe it's really in use). Snooping around in /etc, I found that = /etc/uucp was changed by the make world. Has cu always been part of = Taylor UUCP (as noted in the man page), or have we suddenly switched = cu's? Or, has something else changed very recently having to do with = cu? And yes, I have been meaning to switch to tip anyway... looks like now = is the time. Just wanted everyone to have my one data point on this. -- Brent J. Nordquist nordquis@visi.com +1 612 827-2747 -- Brent J. Nordquist nordquis@visi.com +1 612 827-2747