From owner-freebsd-hackers Sun Sep 21 00:02:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18211 for hackers-outgoing; Sun, 21 Sep 1997 00:02:01 -0700 (PDT) Received: from dfw-ix3.ix.netcom.com (dfw-ix3.ix.netcom.com [206.214.98.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18206 for ; Sun, 21 Sep 1997 00:01:59 -0700 (PDT) Received: (from smap@localhost) by dfw-ix3.ix.netcom.com (8.8.4/8.8.4) id CAA18355 for ; Sun, 21 Sep 1997 02:01:26 -0500 (CDT) Received: from col-oh1-02.ix.netcom.com(199.183.200.34) by dfw-ix3.ix.netcom.com via smap (V1.3) id rma018347; Sun Sep 21 02:01:01 1997 Message-ID: <3424C5A5.3D17@ix.netcom.com> Date: Sun, 21 Sep 1997 02:58:45 -0400 From: Richard Scranton Reply-To: scrantr@ix.netcom.com Organization: LDA Systems, Columbus X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: hackers-digest V3 #357 References: <199709201738.KAA17609@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > *All* the SVR4 systems I know deviate elsewhere than the drivers. > > > Seems kind of a petty reason to page huge royalties... > > Yes, that's the impression that Tandem had too. But how can you ship > a product that's full of bugs? Call it Windows? -- =================================================================== Richard Scranton - LDA Systems - Information Management Consulting scrantr@ix.netcom.com Columbus Cincinnati Cleveland Toledo Atlanta From owner-freebsd-hackers Sun Sep 21 00:06:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18372 for hackers-outgoing; Sun, 21 Sep 1997 00:06:19 -0700 (PDT) Received: from counterintelligence.ml.org ([209.76.130.180]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18362 for ; Sun, 21 Sep 1997 00:06:12 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA00269; Sat, 20 Sep 1997 23:50:04 -0700 (PDT) Date: Sat, 20 Sep 1997 23:50:04 -0700 (PDT) From: "Jamil J. Weatherbee" To: Wm Brian McCane cc: gjennejohn@frt.dec.com, hackers@FreeBSD.ORG Subject: Re: ISDN Modems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Always test bandwidth by transferring some .zip or .gz files of 500k or more via ftp -- that is the only really consistent test I know of. Because in general compression is really worthless, except with web page text. On Sat, 20 Sep 1997, Wm Brian McCane wrote: > > On Fri, 19 Sep 1997, Gary Jennejohn wrote: > > > > > Luigi Rizzo writes: > > > Now if ISDN cards were sold in volumes and priced reasonably (i.e. > > > as much as an NE2000, since they are actually simpler!) and accessed > > > through a dedicated device driver, then things would certainly be > > > different. > > > > > > > well, ISDN cards aren't as cheap as the NE2000 clones, I have to admit > > that. But then again, the volume is a lot smaller. I can get a Teles > > clone here in Germany for about 140 DM, which is ~$75. > > > > And, with bisdn, the cards _are_ accessed using a dedicated driver. > > I can get (depending on the quality of the connection) the maximum > > throughput of ~8kB/sec (well, actually ~7.5kB/s with overhead). > > > > --- > > Gary Jennejohn (work) gjennejohn@frt.dec.com > > (home) garyj@muc.de > > (play) gj@freebsd.org > > Only 7.5kB/sec? I am now very confused. I get 6kB/s throughput from my > 33.6 most of the time. Of course I am usually transferring news/mail so they > are highly compressible. Do any of the plug-in cards do LZ compression, > or anything similar? > > brian > > +-------------------------------------+----------------------------------------+ > He rides a cycle of mighty days, and \ Wm Brian and Lori McCane > he represents the last great schizm \ McCane Consulting > among the gods. Evil though he obviously \ root@bmccane.uit.net > is, he is a mighty figure, this father of \ http://bmccane.uit.net/ > my spirit, and I respect him as the sons \ http://bmccane.uit.net/~pictures/ > of old did the fathers of their bodies. \ http://bmccane.uit.net/~bmccane/ > Roger Zelazny - "Lord of Light" \ http://bmccane.uit.net/~bbs/ > +---------------------------------------------+--------------------------------+ > > From owner-freebsd-hackers Sun Sep 21 00:20:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA19011 for hackers-outgoing; Sun, 21 Sep 1997 00:20:35 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA19006 for ; Sun, 21 Sep 1997 00:20:31 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22338 for hackers@FreeBSD.ORG; Sun, 21 Sep 1997 09:20:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA07587; Sun, 21 Sep 1997 08:52:33 +0200 (MET DST) Message-ID: <19970921085233.JH45420@uriah.heep.sax.de> Date: Sun, 21 Sep 1997 08:52:33 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Is there a way to prompt for boot device? References: <199709200219.WAA13122@smoke.marlboro.vt.us> <19970920130551.DB36336@uriah.heep.sax.de> <199709202124.XAA18194@bitbox.follo.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709202124.XAA18194@bitbox.follo.net>; from Eivind Eklund on Sep 20, 1997 23:24:25 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Eivind Eklund wrote: > > What the heck would break if we started shipping GENERIC in 3.0 with > > `swap generic'? What might break if we allowed -a for other kernels > > as well? I assume the answer to both questions is just ``nothing''. > > It is a minor security breach - it would e.g. allow somebody with > physical access to boot from a floppy[1] even if the machine isn't > set up to do so from the BIOS. As Nate also pointed out, you can do this already right now. Say ``fd(0,a)kernel'' at the boot prompt, and away you go. Also, i assume your answer was for question #2? So this still leaves question #1: what would break if we shipped `swap generic' kernels as GENERIC? The root file system is being adjusted automatically anyway, swap and dump spaces are configured at /etc/rc time. Except of allowing -a, there's IMHO not much more difference to a `swap generic' kernel then. -- 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-hackers Sun Sep 21 02:30:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23622 for hackers-outgoing; Sun, 21 Sep 1997 02:30:31 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23617 for ; Sun, 21 Sep 1997 02:30:29 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id JAA21529 for ; Sun, 21 Sep 1997 09:30:44 GMT Date: Sun, 21 Sep 1997 09:30:44 +0000 (GMT) From: Alfred Perlstein To: hackers@FreeBSD.ORG Subject: restore? In-Reply-To: <19970921085233.JH45420@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i'm about to do something i'm really nervous about. I have a tar/gzip'd file of a whole freebsd drive i made that i would like to restore OVER a freshly installed system. everything is backed up, password file, configuration files, user home directories, X server... etc. etc. etc... what would be the best way for me to do this without fubarring my system? i'm temped to reboot the freshly installed system, become root, and just untar the file to / then reboot again... good idea? dumb idea? help? :) thank you, Alfred From owner-freebsd-hackers Sun Sep 21 02:56:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA24196 for hackers-outgoing; Sun, 21 Sep 1997 02:56:02 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA24166 for ; Sun, 21 Sep 1997 02:55:55 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id JAA21607 for ; Sun, 21 Sep 1997 09:56:10 GMT Date: Sun, 21 Sep 1997 09:56:10 +0000 (GMT) From: Alfred Perlstein To: hackers@FreeBSD.ORG Subject: dammit! :) In-Reply-To: <19970921085233.JH45420@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk sorry for this, but that system i was talking about in the previous message is giving me a heck of a hard time. The BIOS in it doesn't support large harddrives and i have a 4.3 gig IDE in it. after rebooting after the install (i didn't do the untar yet of the backup) the machine will not boot. is there anyway to save the installation i did? sorry for flooding with dumb questions but the install procedure especially switching disks with FreeBSD has always been difficult for me. Thanks again, Alfred From owner-freebsd-hackers Sun Sep 21 05:00:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA27697 for hackers-outgoing; Sun, 21 Sep 1997 05:00:44 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA27683 for ; Sun, 21 Sep 1997 05:00:37 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id IAA21345; Sun, 21 Sep 1997 08:00:15 -0400 (EDT) Date: Sun, 21 Sep 1997 08:00:15 -0400 (EDT) Message-Id: <199709211200.IAA21345@smoke.marlboro.vt.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: cgull+usenet-876052587@smoke.marlboro.vt.us (john hood) To: Mike Smith Cc: nik@iii.co.uk, hackers@FreeBSD.ORG Subject: Re: Different kernels for the bindist and boot.flp? In-Reply-To: <199709181124.UAA00465@word.smith.net.au> References: <19970918121246.52480@strand.iii.co.uk> <199709181124.UAA00465@word.smith.net.au> X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith writes: > No, it's actually quite hard. Due to the way the boot floppy works, > you have to build a custom image with your new kernel, and then hack > sysinstall to splat a new kernel image down after it's extracted the > bindist. You could alternatively specify a different kernel to go in > the bindist, which is relatively straightforward but slow (you have to > build a release to do it). As I've said before, a way around this is to copy the contents of that MFS onto a floppy, put your custom keeno kernel on another floppy, and swap them at the prompt. Perhaps this could be documented or made more accessible? --jh -- Mr. Belliveau said, "the difference was the wise, John Hood, cgull intelligent look on the face of the cow." He was @ *so* right. --Ofer Inbar smoke.marlboro.vt.us From owner-freebsd-hackers Sun Sep 21 08:15:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03751 for hackers-outgoing; Sun, 21 Sep 1997 08:15:19 -0700 (PDT) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03746 for ; Sun, 21 Sep 1997 08:15:16 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id LAA07754 for ; Sun, 21 Sep 1997 11:15:39 -0400 (EDT) Date: Sun, 21 Sep 1997 11:15:39 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: isa_dmastart: chanel 2 busy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got the kernel message isa_dmastart: channel 2 busy.... What is controlled by DMA chanel 2 normally (if anything)? I can find anything that I have set to DMA chanel 2. -- David Cross From owner-freebsd-hackers Sun Sep 21 09:03:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA05236 for hackers-outgoing; Sun, 21 Sep 1997 09:03:00 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA05229 for ; Sun, 21 Sep 1997 09:02:56 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id JAA13164; Sun, 21 Sep 1997 09:02:47 -0700 (PDT) Message-Id: <199709211602.JAA13164@rah.star-gate.com> To: "David E. Cross" cc: hackers@FreeBSD.ORG Subject: Re: isa_dmastart: chanel 2 busy In-reply-to: Your message of "Sun, 21 Sep 1997 11:15:39 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Sep 1997 09:02:47 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Do you have a sound driver installed? Tnks, Amancio >From The Desk Of "David E. Cross" : > I got the kernel message isa_dmastart: channel 2 busy.... > > What is controlled by DMA chanel 2 normally (if anything)? I can find > anything that I have set to DMA chanel 2. > > -- > David Cross > > > From owner-freebsd-hackers Sun Sep 21 09:21:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06110 for hackers-outgoing; Sun, 21 Sep 1997 09:21:37 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA06103 for ; Sun, 21 Sep 1997 09:21:31 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA20155; Sun, 21 Sep 1997 18:18:23 +0200 (MET DST) Date: Sun, 21 Sep 1997 18:18:23 +0200 (MET DST) Message-Id: <199709211618.SAA20155@bitbox.follo.net> From: Eivind Eklund To: Poul-Henning Kamp CC: gram@cdsec.com, hackers@FreeBSD.ORG In-reply-to: Poul-Henning Kamp's message of Thu, 18 Sep 1997 20:51:13 +0200 Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <199709181811.MAA13376@rocky.mt.sri.com> <10897.874608673@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In message <199709181811.MAA13376@rocky.mt.sri.com>, Nate Williams writes: > >Poul-Henning Kamp writes: > No, all you have to do is to make each allocation have it's own set of > pages, munmap them when free is called and never use those pages again. > > You run out of address space really fast, and it is slow, but it works. efence does this, if you use the correct option. I produced an URL in an earlier message in this thread. BTW: Would it be an idea to add some form of optional loop checking (or possibly even a full invariant) to phkmalloc, if it isn't there already? Both double-linked and single-linked lists are trivial to check for loops, at least. Eivind. From owner-freebsd-hackers Sun Sep 21 09:40:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07019 for hackers-outgoing; Sun, 21 Sep 1997 09:40:06 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA06997 for ; Sun, 21 Sep 1997 09:40:01 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA26732; Sun, 21 Sep 1997 18:40:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id SAA09230; Sun, 21 Sep 1997 18:33:27 +0200 (MET DST) Message-ID: <19970921183327.AN13858@uriah.heep.sax.de> Date: Sun, 21 Sep 1997 18:33:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: dec@phoenix.its.rpi.edu (David E. Cross) Subject: Re: isa_dmastart: chanel 2 busy References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from David E. Cross on Sep 21, 1997 11:15:39 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As David E. Cross wrote: > I got the kernel message isa_dmastart: channel 2 busy.... > > What is controlled by DMA chanel 2 normally (if anything)? I can find > anything that I have set to DMA chanel 2. j@uriah 123% /sbin/dmesg | fgrep drq fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa -- 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-hackers Sun Sep 21 10:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09020 for hackers-outgoing; Sun, 21 Sep 1997 10:35:22 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09011 for ; Sun, 21 Sep 1997 10:35:14 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA20824; Sun, 21 Sep 1997 19:35:04 +0200 (MET DST) Date: Sun, 21 Sep 1997 19:35:04 +0200 (MET DST) Message-Id: <199709211735.TAA20824@bitbox.follo.net> From: Eivind Eklund To: Terry Lambert CC: nate@mt.sri.com, phk@critter.freebsd.dk, nate@mt.sri.com, gram@cdsec.com, hackers@FreeBSD.ORG In-reply-to: Terry Lambert's message of Thu, 18 Sep 1997 21:40:26 +0000 (GMT) Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <199709181912.NAA13699@rocky.mt.sri.com> <199709182140.OAA15537@usr03.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > Anyway, if you think so: do like so many others have done, look at the > > > source for phkmalloc.c and try to spot the error. I can't. > > > > I know, and I don't expect you to find any. But, it doesn't mean there > > isn't one. :) > > > > [ 'hangs' in malloc due to memory over-write causing circular lists ] > > Actually, I was thinking of this, too. > > You could determine that a list is circular by maintaining a count of > the number of objects that are supposed to be on the freelist. Then > you count the number of "next" traversals which occur, and when it > excceeds the count of how many are supposed to be there, then you > know you have a problem. Why make it this hard, and subject to trashing of the list count? The following code will check for a circular loop (no knowledge of length required) for a single-linked list: /* Traverse with single and half-speed pointers. If the single-speed pointer intercept the half-speed pointer, we have a loop. */ struct node *p1; struct node *p2; p1 = p2 = list; while (p1) { p1 = p1->next; if (p1 == p2) abort() p1 = p1->next; if (p1 == p2) abort(); p2 = p2->next; if (p1 == p2) abort(); } I believe either the last or the middle check can be dropped, but I've never taken the time to actually work this out. Checking for loops is something I only do in debug-conditionalized code, anyway. To find the more info on the loop, follow your (Terry's) suggestions. For a double-linked list it is even more trivial - just check that the back-links always are correct. (I've got code to find just how a list is corrupted, if that is of interest. It is based on having a head and a tail pointer and a special list format (head, NULL, tail - the head and tail nodes have a NULL next and prev pointer, and are not part of the list proper) but that should be readily modifiable) Eivind. From owner-freebsd-hackers Sun Sep 21 10:37:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09136 for hackers-outgoing; Sun, 21 Sep 1997 10:37:24 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09130; Sun, 21 Sep 1997 10:37:20 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA20833; Sun, 21 Sep 1997 19:37:02 +0200 (MET DST) Date: Sun, 21 Sep 1997 19:37:02 +0200 (MET DST) Message-Id: <199709211737.TAA20833@bitbox.follo.net> From: Eivind Eklund To: "Andrew Atrens" CC: phk@critter.freebsd.dk, hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG In-reply-to: "Andrew Atrens"'s message of 18 Sep 1997 17:59 EDT Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <199709182202.PAA10664@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Andrew Atrens] > >From what I can tell Poul your free() actually gives the memory back to the > OS ( at least some of the time ). If this is correct, it breaks ANSI C behaviour. (Yes, I hate this ANSI C requirement as much as the next guy - but still thought I should inform about it.) Eivind. From owner-freebsd-hackers Sun Sep 21 10:49:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09892 for hackers-outgoing; Sun, 21 Sep 1997 10:49:06 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09886 for ; Sun, 21 Sep 1997 10:49:02 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA20869; Sun, 21 Sep 1997 19:48:59 +0200 (MET DST) Date: Sun, 21 Sep 1997 19:48:59 +0200 (MET DST) Message-Id: <199709211748.TAA20869@bitbox.follo.net> From: Eivind Eklund To: freebsd-hackers@freebsd.org Subject: kernel config, spl*() and interrupt masks Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk With the switch from processor interrupt levels to masks, is it still useful to be able to specify the interrupt level (now mask) in the kernel config file? Doesn't this just give the user one more way to blow his foot off? For something e.g. config'ed as a tty in the config file per default, spltty() will be used in the top half of that driver anyway, and the user has no way to force it to still be blocked by this call. And while we're at it - I've had to have a device driver blocked by both spltty() and splimp() - is there a better/more correct way to do this than having the driver call INTRMASK() on both tty_imask and net_imask? This method seem like quite a nasty hack, relying on things it shouldn't - but the driver has to be in both masks, as it rely on structures in the generic parts of the kernel protected by both spltty() and splimp(). Eivind. From owner-freebsd-hackers Sun Sep 21 12:04:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12779 for hackers-outgoing; Sun, 21 Sep 1997 12:04:10 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA12743; Sun, 21 Sep 1997 12:03:57 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA07812; Sun, 21 Sep 1997 21:03:05 +0200 (CEST) To: Eivind Eklund cc: "Andrew Atrens" , hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-reply-to: Your message of "Sun, 21 Sep 1997 19:37:02 +0200." <199709211737.TAA20833@bitbox.follo.net> Date: Sun, 21 Sep 1997 21:03:04 +0200 Message-ID: <7810.874868584@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199709211737.TAA20833@bitbox.follo.net>, Eivind Eklund writes: >[Andrew Atrens] >> >From what I can tell Poul your free() actually gives the memory back to the >> OS ( at least some of the time ). > >If this is correct, it breaks ANSI C behaviour. (Yes, I hate this >ANSI C requirement as much as the next guy - but still thought I >should inform about it.) Bugger off :-) We merely tell the OS that we're not interested in the contents of the page. It's cheaper to zero-fill than to page out and back in. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hackers Sun Sep 21 12:59:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14120 for hackers-outgoing; Sun, 21 Sep 1997 12:59:01 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA14115 for ; Sun, 21 Sep 1997 12:58:58 -0700 (PDT) Received: (qmail 8825 invoked by uid 1000); 21 Sep 1997 19:59:20 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-091897 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709211748.TAA20869@bitbox.follo.net> Date: Sun, 21 Sep 1997 12:59:19 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Eivind Eklund Subject: RE: kernel config, spl*() and interrupt masks Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Eivind Eklund; On 21-Sep-97 you wrote: > > With the switch from processor interrupt levels to masks, is it still > useful to be able to specify the interrupt level (now mask) in the > kernel config file? Doesn't this just give the user one more way to > blow his foot off? For something e.g. config'ed as a tty in the config > file per default, spltty() will be used in the top half of that driver > anyway, and the user has no way to force it to still be blocked by > this call. > > And while we're at it - I've had to have a device driver blocked by > both spltty() and splimp() - is there a better/more correct way to do > this than having the driver call INTRMASK() on both tty_imask and > net_imask? This method seem like quite a nasty hack, relying on > things it shouldn't - but the driver has to be in both masks, as it > rely on structures in the generic parts of the kernel protected by > both spltty() and splimp(). > > Eivind. Yeah! I second that! Very annoying indeed. --- Sincerely Yours, (Sent on 21-Sep-97, 12:57:10 by XF-Mail) Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313 From owner-freebsd-hackers Sun Sep 21 13:37:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA15844 for hackers-outgoing; Sun, 21 Sep 1997 13:37:34 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA15839 for ; Sun, 21 Sep 1997 13:37:32 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id QAA02654; Sun, 21 Sep 1997 16:37:30 -0400 (EDT) Message-ID: <19970921163729.47395@crh.cl.msu.edu> Date: Sun, 21 Sep 1997 16:37:29 -0400 From: Charles Henrich To: freebsd-hackers@freebsd.org Subject: SCSI Nastiness (bad Quantum?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 X-Operating-System: FreeBSD 2.2.2-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay I have this Quantum XP32150W (last time I *ever* buy Quantum, 4 of the 12 drives I bought in January have so far gone bad.. 5 is working real hard at it right now). Its part of a CCD array, so I would like to if possible bring this disk back alive enough to get its data copied off to another disk. When its active I see this (2.2.2-RELEASE): Sep 21 14:36:32 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4,7f,7,48 asc:11,0 Unrecovered read error sks:80,70 Sep 21 14:36:32 msunews /kernel: , retries:4 Sep 21 14:36:34 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4, 7f,7,48 asc:11,0 Unrecovered read error sks:80,70 Sep 21 14:36:34 msunews /kernel: , retries:3 Sep 21 14:36:36 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4, 7f,7,48 asc:11,0 Unrecovered read error sks:80,70 Sep 21 14:36:36 msunews /kernel: , retries:2 Sep 21 14:36:39 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4, 7f,7,48 asc:11,0 Unrecovered read error sks:80,70 Sep 21 14:36:39 msunews /kernel: , retries:1 Sep 21 14:36:41 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4, 7f,7,48 asc:11,0 Unrecovered read error sks:80,70 Sep 21 14:36:41 msunews /kernel: , FAILURE Sep 21 14:40:14 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4, 7f,7,48 asc:11,0 Unrecovered read error sks:80,e0 Sep 21 14:40:14 msunews /kernel: , retries:4 Sep 21 14:40:17 msunews /kernel: sd23(ahc0:3:0): MEDIUM ERROR info:16bb11 csi:4, 7f,7,48 asc:11,0 Unrecovered read error sks:80,e0 Sep 21 14:40:17 msunews /kernel: , retries:3 Sep 21 14:44:49 msunews /kernel: sd23(ahc0:3:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Sep 21 14:44:49 msunews /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT 1 = 0xa Sep 21 14:44:49 msunews /kernel: Ordered Tag queued Sep 21 14:44:49 msunews /kernel: sd23(ahc0:3:0): SCB 0x3 timedout while recovery in progress Sep 21 14:44:49 msunews /kernel: sd23(ahc0:3:0): SCB 0xe timedout while recovery in progress Sep 21 14:44:54 msunews /kernel: sd23(ahc0:3:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Sep 21 14:44:54 msunews /kernel: SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT 1 = 0xa Sep 21 14:44:54 msunews /kernel: sd23(ahc0:3:0): Queueing an Abort SCB Sep 21 14:44:54 msunews /kernel: sd23(ahc0:3:0): Abort Message Sent Sep 21 14:44:54 msunews /kernel: sd23(ahc0:3:0): SCB 13 - Abort Tag Completed. Sep 21 14:44:54 msunews /kernel: sd23(ahc0:3:0): no longer in timeout Sep 21 14:44:54 msunews /kernel: Ordered Tag sent Sep 21 14:44:56 msunews /kernel: sd23(ahc0:3:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Sep 21 14:44:56 msunews /kernel: SEQADDR = 0x9 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT 1 = 0xa Sep 21 14:44:56 msunews /kernel: Ordered Tag queued ... Ad Nausem. I've run Adaptec's verify tool, and it happily reports several bad sectors, and asks if I wish to remap. When I say yes, it appears to do nothing, and a re-verify pass pops up the "remap?" requestor on the same sectors, so obviously the quantum is ignoring those remap requests. I also have AWRE/ARRE on that drive. Any ideas? Thanks a bunch! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sun Sep 21 14:26:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17586 for hackers-outgoing; Sun, 21 Sep 1997 14:26:33 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA17578 for ; Sun, 21 Sep 1997 14:26:22 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xCtW3-0002P2-00; Sun, 21 Sep 1997 14:26:07 -0700 Date: Sun, 21 Sep 1997 14:26:06 -0700 (PDT) From: Tom To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: SCSI Nastiness (bad Quantum?) In-Reply-To: <19970921163729.47395@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Charles Henrich wrote: > nothing, and a re-verify pass pops up the "remap?" requestor on the same > sectors, so obviously the quantum is ignoring those remap requests. I also > have AWRE/ARRE on that drive. Any ideas? The "spare" is full, so there is no place to remap sectors to. When AWRE/AREE are on, sectors can be getting remapped all the time, slowly filling the "spare" area. It seems the media on your drive is slowly degrading. > Thanks a bunch! > > -Crh > > Charles Henrich Michigan State University henrich@msu.edu > > http://pilot.msu.edu/~henrich > > Tom From owner-freebsd-hackers Sun Sep 21 14:50:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19704 for hackers-outgoing; Sun, 21 Sep 1997 14:50:10 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust54.tnt1.manassas.va.da.uu.net [153.37.113.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19695 for ; Sun, 21 Sep 1997 14:50:03 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id RAA01345; Sun, 21 Sep 1997 17:49:24 -0400 (EDT) Message-ID: <19970921174923.42957@wakky.dyn.ml.org> Date: Sun, 21 Sep 1997 17:49:23 -0400 From: Lee Cremeans To: Charles Henrich <'@wakky.dyn.ml.org> Cc: hackers@freebsd.org Subject: Re: SCSI Nastiness (bad Quantum?) Reply-To: hcremean@vt.edu References: <19970921163729.47395@crh.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970921163729.47395@crh.cl.msu.edu>; from Charles Henrich on Sun, Sep 21, 1997 at 04:37:29PM -0400 X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 21, 1997 at 04:37:29PM -0400, Charles Henrich wrote: > Okay I have this Quantum XP32150W (last time I *ever* buy Quantum, 4 of the 12 > drives I bought in January have so far gone bad.. 5 is working real hard at it I wouldn't judge Quantum by this particular drive; the Grand Prix drives are known to be bogus. Quantum's other drives are fine, though. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD++^i WK+++r P&B++ SL++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi Ay77 M | hcremean (at) vt.edu FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://wakky.dyn.ml.org/~lee | finger me for geek code From owner-freebsd-hackers Sun Sep 21 15:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22548 for hackers-outgoing; Sun, 21 Sep 1997 15:45:16 -0700 (PDT) Received: from rrzs2.rz.uni-regensburg.de (rrzs2.rz.uni-regensburg.de [132.199.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA22540 for ; Sun, 21 Sep 1997 15:45:11 -0700 (PDT) From: 00542229@mailexcite.com Received: from rpssg3.psychologie.uni-regensburg.de (rpssg3.psychologie.uni-regensburg.de [132.199.136.103]) by rrzs2.rz.uni-regensburg.de (8.8.5/8.8.5) with SMTP id AAA24208; Mon, 22 Sep 1997 00:44:18 +0200 (MET DST) Received: from postmaster2434522@mailexcite.com by aol.com (8.8.5/8.6.5) with SMTP id GAA03555 for ; Wed, 28 May 1997 15:44:46 -0600 (EST) Date: Wed, 28 May 97 15:44:46 EST To: postmaster223423222@mailexcite.com Subject: New 101 sex channel free.,.,.,.,.,., Message-Id: <812312373463182736128736.com> Reply-To: 12312312322341222122@rrzs2.rz.uni-regensburg.de Comments: Authenticated sender is <13212312321324222222> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk http://www.schoolgirlz.com This is the newest and most comprehensive Adult Site Offer Available on the net.... 110 WILD XXX RATED LIVE CHANNELS - 2 ALL BLONDE CHANNELS 2 MULTIPLE GIRL CHANNELS - 2 CHANNELS OF REDHEADS AND BRUNNETTES 1 ALL BLACK CHANNEL - 1 INTERNATIONAL GIRLS FROM AROUND THE W0RLD 2 TEEN CHANNELS (18 AND 19 YR OLD BABES) - 4 CHANNELS REAL SEX SHOWS-MALE/FEMALE-LESBIAN) http://www.schoolgirlz.com From owner-freebsd-hackers Sun Sep 21 15:49:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22692 for hackers-outgoing; Sun, 21 Sep 1997 15:49:00 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA22684 for ; Sun, 21 Sep 1997 15:48:54 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id QAA07199; Sun, 21 Sep 1997 16:47:21 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA28054; Sun, 21 Sep 1997 16:47:19 -0600 (MDT) Date: Sun, 21 Sep 1997 16:47:19 -0600 (MDT) Message-Id: <199709212247.QAA28054@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: phk@critter.freebsd.dk, hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <199709211737.TAA20833@bitbox.follo.net> References: <199709182202.PAA10664@hub.freebsd.org> <199709211737.TAA20833@bitbox.follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eivind Eklund writes: > [Andrew Atrens] > > >From what I can tell Poul your free() actually gives the memory back to the > > OS ( at least some of the time ). > > If this is correct, it breaks ANSI C behaviour. Huh? I didn't realize ANSI mandated OS support. Can you quote chapter and verse that says this? Nate From owner-freebsd-hackers Sun Sep 21 16:06:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA23618 for hackers-outgoing; Sun, 21 Sep 1997 16:06:05 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA23600 for ; Sun, 21 Sep 1997 16:05:57 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id RAA07320; Sun, 21 Sep 1997 17:05:47 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA28148; Sun, 21 Sep 1997 17:05:46 -0600 (MDT) Date: Sun, 21 Sep 1997 17:05:46 -0600 (MDT) Message-Id: <199709212305.RAA28148@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Nate Williams , Eivind Eklund , phk@critter.freebsd.dk, hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <19970922005506.48602@bitbox.follo.net> References: <199709182202.PAA10664@hub.freebsd.org> <199709211737.TAA20833@bitbox.follo.net> <199709212247.QAA28054@rocky.mt.sri.com> <19970922005506.48602@bitbox.follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > >From what I can tell Poul your free() actually gives the memory back to the > > > > OS ( at least some of the time ). > > > > > > If this is correct, it breaks ANSI C behaviour. > > > > Huh? I didn't realize ANSI mandated OS support. Can you quote chapter > > and verse that says this? > > It doesn't. However, it has a formulation that IMHO is too > restrictive - that free() 'makes the memory available for further use > by the program' (from memory). Thus, an implementation of > malloc()/free() that give memory back to the OS is in violation of the > standard. Depends on how you interpret the standard. If you give it back to the OS, you can always(*) get it back at a later time. So, the 'memory' is still available by the program. :) Nate * - It's possible, but highly improbably that if the system is very low on memory that the program won't get the memory it once had if some other program 'took' the memory that was given back to the OS. FreeBSD's current scheme is to kill a program that asks for more memory in an out-of-memory/VM situation, but I don't think those kinds of problems are within the scope of ANSI-C. From owner-freebsd-hackers Sun Sep 21 16:09:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA23800 for hackers-outgoing; Sun, 21 Sep 1997 16:09:27 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA23791 for ; Sun, 21 Sep 1997 16:09:20 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA23834; Mon, 22 Sep 1997 00:55:06 +0200 (MET DST) Message-ID: <19970922005506.48602@bitbox.follo.net> Date: Mon, 22 Sep 1997 00:55:06 +0200 From: Eivind Eklund To: Nate Williams Cc: Eivind Eklund , phk@critter.freebsd.dk, hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <199709182202.PAA10664@hub.freebsd.org> <199709211737.TAA20833@bitbox.follo.net> <199709212247.QAA28054@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199709212247.QAA28054@rocky.mt.sri.com>; from Nate Williams on Sun, Sep 21, 1997 at 04:47:19PM -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 21, 1997 at 04:47:19PM -0600, Nate Williams wrote: > Eivind Eklund writes: > > [Andrew Atrens] > > > >From what I can tell Poul your free() actually gives the memory back to the > > > OS ( at least some of the time ). > > > > If this is correct, it breaks ANSI C behaviour. > > Huh? I didn't realize ANSI mandated OS support. Can you quote chapter > and verse that says this? It doesn't. However, it has a formulation that IMHO is too restrictive - that free() 'makes the memory available for further use by the program' (from memory). Thus, an implementation of malloc()/free() that give memory back to the OS is in violation of the standard. (Not that I'm certain how a program would detect this - at least I personally would consider a program that relies on being able to re-allocate memory that it has freed buggy.) Eivind. From owner-freebsd-hackers Sun Sep 21 16:40:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25171 for hackers-outgoing; Sun, 21 Sep 1997 16:40:36 -0700 (PDT) Received: from dublin.iona.ie (root@operation.dublin.iona.ie [192.122.221.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25152; Sun, 21 Sep 1997 16:40:30 -0700 (PDT) Received: from ultra (ultra [192.122.221.136]) by dublin.iona.ie (8.7.5/jm-1.01) with SMTP id AAA00984; Mon, 22 Sep 1997 00:40:06 +0100 (BST) Date: Mon, 22 Sep 1997 00:39:42 +0100 (BST) From: Niall Smart X-Sender: nsmart@ultra To: Terry Lambert cc: Don.Lewis@tsc.tdk.com, hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in malloc/free In-Reply-To: <199709192002.NAA29627@usr03.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Terry Lambert wrote: > > > > Which is why I save and restore errno in signal handlers. > > > Perhaps this should be done by the trampoline code on the user's > > > behalf... > > Perhaps that would encourage people to write non-portable code. > > When a read or write fault occurs on page zero in a program running > on SVR4, rather than crashing, the map the page and note the effect. > > There is a kernel tunable that can turn this off, but a great many > legacy programs dereference NULL pointers, expecting a NULL pointer > to be identical to a NULL string. > > The default for SVR4 is arguably incorrect, but it follows the principle > of least astonishment, and allows legacy code to run. I don't mind, as long as it isn't documented. :) Transparent support for legacy/bad code is acceptable, documented unportable behaviourisms aren't, IMO. Even if you note that they are unportable (some) people will still rely on them, I would prefer to see the documentation advising people that they should save and restore errno in signal handlers regardless of the actual behaviour. -- Niall Smart Customer Engineering, IONA Technologies. (www.iona.com) > From owner-freebsd-hackers Sun Sep 21 16:51:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25515 for hackers-outgoing; Sun, 21 Sep 1997 16:51:07 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25507 for ; Sun, 21 Sep 1997 16:50:58 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id QAA24213; Sun, 21 Sep 1997 16:50:40 -0700 (PDT) To: Eivind Eklund cc: Nate Williams , Eivind Eklund , phk@critter.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-reply-to: Your message of "Mon, 22 Sep 1997 00:55:06 +0200." <19970922005506.48602@bitbox.follo.net> Date: Sun, 21 Sep 1997 16:50:38 -0700 Message-ID: <24205.874885838@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It doesn't. However, it has a formulation that IMHO is too > restrictive - that free() 'makes the memory available for further use > by the program' (from memory). Thus, an implementation of Bizarre, are you sure? That's exactly 180 degrees counter to what I've always learned about storage allocators: If you count on free() to not corrupt the data you pass to it, you deserve to lose and lose big. Jordan From owner-freebsd-hackers Sun Sep 21 16:51:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25545 for hackers-outgoing; Sun, 21 Sep 1997 16:51:46 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25535 for ; Sun, 21 Sep 1997 16:51:37 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA24215; Mon, 22 Sep 1997 01:51:29 +0200 (MET DST) Message-ID: <19970922015128.32876@bitbox.follo.net> Date: Mon, 22 Sep 1997 01:51:28 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: Nate Williams , Eivind Eklund , phk@critter.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <19970922005506.48602@bitbox.follo.net> <24205.874885838@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <24205.874885838@time.cdrom.com>; from Jordan K. Hubbard on Sun, Sep 21, 1997 at 04:50:38PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 21, 1997 at 04:50:38PM -0700, Jordan K. Hubbard wrote: > > It doesn't. However, it has a formulation that IMHO is too > > restrictive - that free() 'makes the memory available for further use > > by the program' (from memory). Thus, an implementation of > > Bizarre, are you sure? That's exactly 180 degrees counter to what > I've always learned about storage allocators: If you count on free() > to not corrupt the data you pass to it, you deserve to lose and lose > big. My typo. I mean 'further allocation'. Eivind. From owner-freebsd-hackers Sun Sep 21 17:34:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA27757 for hackers-outgoing; Sun, 21 Sep 1997 17:34:26 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA27712; Sun, 21 Sep 1997 17:34:13 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id CAA24672; Mon, 22 Sep 1997 02:34:10 +0200 (MET DST) Date: Mon, 22 Sep 1997 02:34:10 +0200 (MET DST) Message-Id: <199709220034.CAA24672@bitbox.follo.net> From: Eivind Eklund To: Brian Somers CC: hackers@FreeBSD.ORG In-reply-to: Brian Somers's message of Sun, 21 Sep 1997 16:02:39 -0700 (PDT) Subject: Re: cvs commit: src/usr.sbin/ppp lcp.c References: <199709212302.QAA14109@freefall.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > brian 1997/09/21 16:02:38 PDT > > Modified files: (Branch: RELENG_2_2) > usr.sbin/ppp lcp.c > Log: > MFC: Sleep for a second before sending the first LCP > config request. This stops us from squirting stuff > down a line that still has ECHO turned on because the > peer hasn't had a chance to start yet. > Lead to the cause by: Greg Lehey Isn't detecting this what the magic number more-or-less was introduced for? You can catch looping LCP-negotiation by looking for the same magic number, and it really seems a pity to waste a second on connection, as this could be running on really fast links (like TCP or ISDN links). Besides, if the other end is slow, 1 second might not be enough. Eivind. From owner-freebsd-hackers Sun Sep 21 18:29:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA00457 for hackers-outgoing; Sun, 21 Sep 1997 18:29:14 -0700 (PDT) Received: from goliath.airnet.net ([207.120.51.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA00449 for ; Sun, 21 Sep 1997 18:29:09 -0700 (PDT) Date: Sun, 21 Sep 1997 18:29:09 -0700 (PDT) Received: from pm6-203.airnet.net (207.120.51.203) by goliath.airnet.net (WorldMail 1.3.122); 21 Sep 1997 20:28:51 -0500 Message-ID: <341D37C00000B74D@goliath.airnet.net> (added by goliath.airnet.net) X-Sender: kirbykb@airnet.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Alfred Perlstein From: Kris Kirby Subject: Re: dammit! :) Cc: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alfred: >sorry for this, but that system i was talking about in the previous >message is giving me a heck of a hard time. The BIOS in it doesn't >support large harddrives and i have a 4.3 gig IDE in it. Here's what I did on my machine [722MB, no LBA/etc]. Make a 32 or 33 Mbyte primary partition below the 500 MB limit, assuming that you only want / to be 32Mbytes. Make that your / filesystem. Then put /usr, etc. on the remaining chunk. When FreeBSD is installed/restored, your kernel will boot from the smaller partition, and when in comes out of "real" mode, it can access the whole 4.3 GB. BTW, "real" mode ends when the kernel stops spewing out bright text. >is there anyway to save the installation i did? My solution presents a problem because the / filesystem is tarred in there too. Anyone else? Regards, Kris From owner-freebsd-hackers Sun Sep 21 18:29:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA00475 for hackers-outgoing; Sun, 21 Sep 1997 18:29:31 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA00470 for ; Sun, 21 Sep 1997 18:29:28 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id SAA24046; Sun, 21 Sep 1997 18:29:27 -0700 (PDT) Date: Sun, 21 Sep 1997 18:29:27 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199709220129.SAA24046@kithrup.com> To: hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <19970922015128.32876.kithrup.freebsd.hackers@bitbox.follo.net> References: <24205.874885838@time.cdrom.com>; from Jordan K. Hubbard on Sun, Sep 21, 1997 at 04:50:38PM -0700 Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19970922015128.32876.kithrup.freebsd.hackers@bitbox.follo.net> you write: >On Sun, Sep 21, 1997 at 04:50:38PM -0700, Jordan K. Hubbard wrote: >> > It doesn't. However, it has a formulation that IMHO is too >> > restrictive - that free() 'makes the memory available for further use >> > by the program' (from memory). Thus, an implementation of >> Bizarre, are you sure? That's exactly 180 degrees counter to what >> I've always learned about storage allocators: If you count on free() >> to not corrupt the data you pass to it, you deserve to lose and lose >> big. >My typo. I mean 'further allocation'. With either wording, eivind, fortunately, is wrong ;). malloc() is constrained to not return the same memory block twice unless it has been free()'d first. ANSI C also makes no distinction between OS and standard library code -- that is, malloc() could be a system call, as far as ANSI C is concerned. The requirement there is simply that free() makes the memory available for further allocation (that being the only way an ANSI C conformant application can get at such memory). The wording for malloc() and free() was chosen very carefully, to allow embedded applications to work -- in such applications, there is no dynamic allocation of memory from the OS (since there isn't one); instead, many of them have a chunk of memory that is part of the program's address space, and malloc() and free() simply parcel it up. Lastly, the wording for free() is, as I understood it when I last read it, meant to convey the requirement that: char *cp = malloc(100); if (cp) { free(cp); cp = malloc(100); } always result in a non-NULL cp. So, in conclusion: yes, the OS is perfectly free to have free() return the memory back to the OS, even though traditional systems did not do this most of the time. (It is a quality of implementation issue, and I think may be referenced as such in the X3J11 notes/comments/explanation that are not officially part of the standard.) From owner-freebsd-hackers Sun Sep 21 19:01:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA02086 for hackers-outgoing; Sun, 21 Sep 1997 19:01:00 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA02068; Sun, 21 Sep 1997 19:00:42 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id CAA05366; Mon, 22 Sep 1997 02:09:08 +0100 (BST) Message-Id: <199709220109.CAA05366@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Brian Somers , hackers@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp lcp.c In-reply-to: Your message of "Mon, 22 Sep 1997 02:34:10 +0200." <199709220034.CAA24672@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 02:09:08 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > brian 1997/09/21 16:02:38 PDT > > > > Modified files: (Branch: RELENG_2_2) > > usr.sbin/ppp lcp.c > > Log: > > MFC: Sleep for a second before sending the first LCP > > config request. This stops us from squirting stuff > > down a line that still has ECHO turned on because the > > peer hasn't had a chance to start yet. > > Lead to the cause by: Greg Lehey > > Isn't detecting this what the magic number more-or-less was introduced > for? You can catch looping LCP-negotiation by looking for the same > magic number, and it really seems a pity to waste a second on > connection, as this could be running on really fast links (like TCP or > ISDN links). Besides, if the other end is slow, 1 second might not be > enough. When we connect to a machine that is running a bit slow, the client-side ppp manages to send 6 LCPs, receive the same 6 back (due to echo being on) and give up - all before the server-side ppp gets to turn ECHO off. Maybe I should incrementally "back out" when receiving config requests w/ the same magic - ie, wait .2 seconds after the first dup magic, .4 after the second etc. > Eivind. > > Sleep for a second before sending the first LCP > > config request. This stops us from squirting stuff > > Don't forget that some boxes, if you wait a second or more, will fall > back into ``terminal server'' mode, and then the user gets hosed. The > Shiva LanRover Access Switch is one such box in wide circulation. Hmm, looks like the incremental backout may be a better idea. > -GAWollman -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Sep 21 19:37:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA03939 for hackers-outgoing; Sun, 21 Sep 1997 19:37:15 -0700 (PDT) Received: from ppp6431.on.sympatico.ca (ppp6431.on.sympatico.ca [206.172.208.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA03925 for ; Sun, 21 Sep 1997 19:37:05 -0700 (PDT) Received: from localhost (tim@localhost) by ppp6431.on.sympatico.ca (8.8.7/8.8.7) with SMTP id WAA00222; Sun, 21 Sep 1997 22:35:53 -0400 (EDT) Date: Sun, 21 Sep 1997 22:35:52 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: Sean Eric Fagan cc: hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <199709220129.SAA24046@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Sean Eric Fagan wrote: > Lastly, the wording for free() is, as I understood it when I last read it, > meant to convey the requirement that: > > char *cp = malloc(100); > if (cp) { > free(cp); > cp = malloc(100); > } > > always result in a non-NULL cp. > > So, in conclusion: yes, the OS is perfectly free to have free() return the > memory back to the OS, even though traditional systems did not do this most No, if you want the above code to always result in a non-NULL cp, free() cannot ever return the memory back to the OS. However, I believe the actual wording is sufficiently ambigous that this debate has been fought long and hard in other forums. Anything which is this controversial can be implemented either way and be right. Besides, there ain't no standard which can tell me that free() can't return memory to the OS. -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. From owner-freebsd-hackers Sun Sep 21 19:37:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA03946 for hackers-outgoing; Sun, 21 Sep 1997 19:37:15 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA03928 for ; Sun, 21 Sep 1997 19:37:12 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id WAA02676; Sun, 21 Sep 1997 22:42:22 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sun, 21 Sep 1997 22:42:22 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Kris Kirby cc: Alfred Perlstein , hackers@freebsd.org Subject: Re: dammit! :) In-Reply-To: <341D37C00000B74D@goliath.airnet.net> (added by goliath.airnet.net) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well i actually suceeded in doing the forced untar over the whole thingy, i needed to re-make my /dev and i wouldn't recommend doing it if you have user accounts on your system, someone suggested the "--unlink" option to tar which seemed to help (don't know what woulda happended without it) if you do have accounts make sure you untar the system files FIRST as it gets confused for some reason... ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" On Mon, 22 Sep 1997, Kris Kirby wrote: > Alfred: > > >sorry for this, but that system i was talking about in the previous > >message is giving me a heck of a hard time. The BIOS in it doesn't > >support large harddrives and i have a 4.3 gig IDE in it. > > Here's what I did on my machine [722MB, no LBA/etc]. Make a 32 or 33 Mbyte > primary partition below the 500 MB limit, assuming that you only want / to > be 32Mbytes. Make that your / filesystem. Then put /usr, etc. on the > remaining chunk. When FreeBSD is installed/restored, your kernel will boot > from the smaller partition, and when in comes out of "real" mode, it can > access the whole 4.3 GB. BTW, "real" mode ends when the kernel stops spewing > out bright text. > > >is there anyway to save the installation i did? > My solution presents a problem because the / filesystem is tarred in there too. > Anyone else? > > Regards, > > Kris > > From owner-freebsd-hackers Sun Sep 21 19:58:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA04812 for hackers-outgoing; Sun, 21 Sep 1997 19:58:07 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA04806 for ; Sun, 21 Sep 1997 19:58:04 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id TAA27605; Sun, 21 Sep 1997 19:58:03 -0700 (PDT) Date: Sun, 21 Sep 1997 19:58:03 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199709220258.TAA27605@kithrup.com> To: tim@ppp6431.on.sympatico.ca Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> char *cp = malloc(100); >> if (cp) { >> free(cp); >> cp = malloc(100); >> } >No, if you want the above code to always result in a non-NULL cp, >free() cannot ever return the memory back to the OS. Really? Would you like to explain that idiotic statement? Back it up with some facts, explanations, or justifications? There is only one situation in which that code fragment can have cp set to NULL -- when the first malloc() fails. That is the char *cp = malloc(100); I did not point that out because I thought it was obvious. And it doesn't change my position: if the first malloc() succeeded, then, even if there is no more space available after that first malloc(), the free() and subsequent malloc() are required to work. You can believe whatever you want, but it is contrary to what the intent and wording of X3J11 came to. Or so say the seven or eight members of the committee that I've known since it was first formed. From owner-freebsd-hackers Sun Sep 21 20:00:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA04970 for hackers-outgoing; Sun, 21 Sep 1997 20:00:55 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA04964 for ; Sun, 21 Sep 1997 20:00:45 -0700 (PDT) Received: from nospam.hiwaay.net (tnt1-138.HiWAAY.net [208.147.147.138]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id WAA22179 for ; Sun, 21 Sep 1997 22:00:42 -0500 (CDT) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id WAA02213 for ; Sun, 21 Sep 1997 22:00:40 -0500 (CDT) Message-Id: <199709220300.WAA02213@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@FreeBSD.ORG From: dkelly@hiwaay.net Subject: "Load Defaults" was my cure! (Was: Re: Do *you* have problems with floppies?) In-reply-to: Message from j@uriah.heep.sax.de (J Wunsch) of "Tue, 16 Sep 1997 09:14:55 +0200." <19970916091455.RH14318@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Sep 1997 22:00:39 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As dkelly@hiwaay.net wrote: > > > > p.s.: Does your mainboard also have a Winbond chip for the FDC? Quite > > > possible that this is the actual culprit. I think my board has an SMC > > > chip. > > > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > fdc0: NEC 72065B > > As i've stated earlier, this is just non-information only. You gotta > open the case of your machine to learn what FDC you're using. The > above information is wrong anyway, and it's impossible to get the > actual FDC make by (documented) electronic means. Arrrg. I've been meaning to open the cases. Rebooted today and forgot. > I should drop the above message from the floppy driver, it's less than > useless. > > Tor Egge seems to have traced his problem down to the Winbond chip, > and the best guess one can make out of his test data is that the bus > interface of the chip (*not* the floppy interface) is broken. Perhaps > it's not noticing DMA overruns. This is really why I'm replying to this older thread: Selecting "Load Defaults" in the BIOS setup cured my floppy problem. Am quite sure I have all the other parameters (that are settable) back to the way I've always had them but I'm guessing there are values in the BBRAM for the BIOS that are used for setup but are not accessable from the provided user interface via any other means than "Load Defaults". I was using the settings as shipped from Atipa, plus a few little things such as selection of parity memory and reserving IRQ 5 and 10 for ISA cards. MB above is an Asus P6NP5. > > Also have access to a Gateway P133 with a VX chipset and same FDC but > > Really the same FDC? Again, verify visually. > > > have not had any problems with it. Nor with my $100 5x86/133 CPU & MB > > which "only" has a NEC 765. > > A real NE765? I.e., the 40-pin chip? Am certian it is not 40 pins. Again, was in a friend's system that has the same cheapo MB this weekend and forgot to look. He purchased a 2.0G Ditto internal floppy tape drive and couldn't get it to work under DOS or Win95. Checking Iomega's web site I guessed his floppy controller on the MB wasn't "1 MHz or faster". Scrounged around here for cards with floppy controllers and the only thing that worked was the floppy port on an Adaptec 1542CF. He's borrowed it for now, but if I think too much about my 1542 spending the rest of its life as his floppy controller, I'd have to cry. Local dealers want $75 for Iomega's special floppy controller card. Ouch. WalMart's online shopper has it for $50.11, still "ouch". -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Sun Sep 21 20:07:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA05283 for hackers-outgoing; Sun, 21 Sep 1997 20:07:23 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA05275; Sun, 21 Sep 1997 20:07:12 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id EAA07211; Mon, 22 Sep 1997 04:05:54 +0100 (BST) Message-Id: <199709220305.EAA07211@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: Eivind Eklund , Brian Somers , hackers@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp lcp.c In-reply-to: Your message of "Mon, 22 Sep 1997 02:09:08 BST." <199709220109.CAA05366@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 04:05:54 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hmm, looks like the incremental backout may be a better idea. It now waits for .8 of a second after receiving a dup magic number. The second dup will cause a wait of 1.2 seconds and things increment thereafter by .4 of a second. The real problem here is that if the client side decides on a new magic number, it also NAKs the received Req. It then receives the NAK and changes magic again, sending another Req..... which bounces due to ECHO etc etc etc. If we send more than two Reqs, by the time the other side starts, it's got a huge stream of magic changes waiting in the tty queue and gets hopelessly confused. This normally means a fast exit by the server. -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Sep 21 21:07:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA08327 for hackers-outgoing; Sun, 21 Sep 1997 21:07:12 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA08316 for ; Sun, 21 Sep 1997 21:07:08 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id GAA08834; Mon, 22 Sep 1997 06:12:37 +0200 (CEST) From: Mikael Karpberg Message-Id: <199709220412.GAA08834@ocean.campus.luth.se> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <199709220258.TAA27605@kithrup.com> from Sean Eric Fagan at "Sep 21, 97 07:58:03 pm" To: sef@Kithrup.COM (Sean Eric Fagan) Date: Mon, 22 Sep 1997 06:12:36 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Sean Eric Fagan: > >> char *cp = malloc(100); > >> if (cp) { > >> free(cp); > >> cp = malloc(100); > >> } > >No, if you want the above code to always result in a non-NULL cp, > >free() cannot ever return the memory back to the OS. > [...] if the first malloc() succeeded, then, even if there is > no more space available after that first malloc(), the free() and subsequent > malloc() are required to work. But if you do that allocation, and by doing so steals the last available page in the system (swap and memory are exausted after your alloc succeeds) and you free() it, system gets it back, and something else requests it, when you don't have anywhere to take memory from for the second malloc(). All the pages are taken, and you can't swap anything out. Malloc() would have to fail. No? However, if I understand everything right, phkmalloc doesn't shrink the program's space, but simply tells the OS that the page's contents are not important and can be disregarded. The program still has enough space allocated on the swap to write the page to, but there is no need to write it to that space, and read it back when the memory is accessed. Instead the page is not reclaimed until the OS needs a free page, and if the program wants to use the page later, it gets a zeroed page from the system. This can be guaranteed since there is space on the swap for this page, so another program can have an idle page be swapped out to there, and the program can then get that page, after it has been zeroed. Then it would indeed be guaranteed that the second malloc() would succeed. Am I right? Maybe I'm completely off instead? :-) /Mikael From owner-freebsd-hackers Sun Sep 21 21:12:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA08628 for hackers-outgoing; Sun, 21 Sep 1997 21:12:00 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA08620 for ; Sun, 21 Sep 1997 21:11:54 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id VAA01246; Sun, 21 Sep 1997 21:11:53 -0700 (PDT) Date: Sun, 21 Sep 1997 21:11:53 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199709220411.VAA01246@kithrup.com> To: karpen@ocean.campus.luth.se Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >But if you do that allocation, and by doing so steals the last available >page in the system (swap and memory are exausted after your alloc succeeds) >and you free() it, system gets it back, and something else requests it, when >you don't have anywhere to take memory from for the second malloc(). All the >pages are taken, and you can't swap anything out. Malloc() would have to fail. >No? Hm. Good question :). The intent, as I said, was for the code fragment I gave to work. And yet the committee wanted free() to be able to return memory back to the OS. In that circumstance... the latter is "more important." Since it's, you know, actually written in the standard :). I retract my statement, and offer an apology. Sorry. Sean. From owner-freebsd-hackers Sun Sep 21 21:46:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA10985 for hackers-outgoing; Sun, 21 Sep 1997 21:46:41 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA10978 for ; Sun, 21 Sep 1997 21:46:36 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id WAA09216; Sun, 21 Sep 1997 22:46:27 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA29021; Sun, 21 Sep 1997 22:46:26 -0600 (MDT) Date: Sun, 21 Sep 1997 22:46:26 -0600 (MDT) Message-Id: <199709220446.WAA29021@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Sean Eric Fagan Cc: tim@ppp6431.on.sympatico.ca, hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <199709220258.TAA27605@kithrup.com> References: <199709220258.TAA27605@kithrup.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> char *cp = malloc(100); > >> if (cp) { > >> free(cp); > >> cp = malloc(100); > >> } > >No, if you want the above code to always result in a non-NULL cp, > >free() cannot ever return the memory back to the OS. > > Really? Would you like to explain that idiotic statement? Back it up with > some facts, explanations, or justifications? If between the lines of free(cp) you get a context switch, another application allocates enough memory to completely use up the VM in the system, and then the process is switched to again, the second malloc could fail due to lack of VM. Again, this is a *very* rare case, but could happen if free() returns memory to the OS. > I did not point that out because I thought it was obvious. And it doesn't > change my position: if the first malloc() succeeded, then, even if there is > no more space available after that first malloc(), the free() and subsequent > malloc() are required to work. How can they work if there is no more space after the first malloc()? There is no guarantee that once you get one byte, you're guaranteed as many as you want, be it 100 bytes or 100000 bytes. Nate From owner-freebsd-hackers Sun Sep 21 22:12:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA12936 for hackers-outgoing; Sun, 21 Sep 1997 22:12:33 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA12930 for ; Sun, 21 Sep 1997 22:12:30 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xD0nM-0000HA-00; Sun, 21 Sep 1997 23:12:28 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id XAA21951 for ; Sun, 21 Sep 1997 23:12:25 -0600 (MDT) Message-Id: <199709220512.XAA21951@harmony.village.org> To: hackers@freebsd.org Subject: mtree vs /usr/src Date: Sun, 21 Sep 1997 23:12:25 -0600 From: Warner Losh Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why is /usr/src owned bin.bin? Why does make installworld insist on resetting it back to bin.bin, even after I've chown'd it to imp? Just wondering if there is a good reason for this... Warner From owner-freebsd-hackers Sun Sep 21 22:13:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA13037 for hackers-outgoing; Sun, 21 Sep 1997 22:13:29 -0700 (PDT) Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA13010; Sun, 21 Sep 1997 22:13:21 -0700 (PDT) Received: (from joes@localhost) by shasta.wstein.com (8.8.7/8.8.7) id WAA00814; Sun, 21 Sep 1997 22:13:18 -0700 (PDT) From: Joseph Stein Message-Id: <199709220513.WAA00814@shasta.wstein.com> Subject: Help... Unexplained crashes under RELENG_2_2 (last message in syslog is from atrun) To: hackers@freebsd.org, stable@freebsd.org Date: Sun, 21 Sep 1997 22:13:18 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Over the course of the last four to six weeks, my system has been crashing unexpectedly (and of course, when I'm not home to coax it back to life). Today, it died, and rebooted itself, though not a soft reboot (like it used to do occasionally) -- it was a hard reboot... The last thing that is written to syslog() when it happens is messages like: Sep 21 17:00:00 shasta CRON[925]: (root) CMD (/usr/libexec/atrun) This system runs a plethora of daemons -- xntpd, named, sshd, httpd, ftpd, rwhod -- am I merely overloading it? Or is there some bug in at/atrun? I have coredumps enabled but have not yet seen anything in /var/run/crash from it. Should I just rebuild the world? (I'm going to anyway, and see if that helps). And, no, the power has not been out here today. (Other system is running just fine, and is identical except runs stock 2.1.7.) More information on request; not sure exactly what to send along with this. Here is some syslog() info; it has been edited to exclude the xntpd, named, and sendmail stuff. If you wish to examine the whole chunk from today, I'll have it available at ftp://shasta.wstein.com/pub/system/log.970921 (it's a *.* log so it's huge.) in short order (by the time you read this message.) Thanks for any help! Joe Stein ------------------- Syslog() stuff: Sep 21 17:00:00 shasta CRON[925]: (root) CMD (/usr/libexec/atrun) Sep 21 17:05:00 shasta CRON[931]: (root) CMD (/usr/libexec/atrun) Sep 21 17:10:00 shasta CRON[946]: (root) CMD (/usr/libexec/atrun) Sep 21 17:16:06 shasta /kernel: FreeBSD 2.2-STABLE #0: Sat Aug 23 20:00:30 PDT 1997 Sep 21 17:16:06 shasta /kernel: Features=0x1 Sep 21 17:16:07 shasta /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Sep 21 17:16:07 shasta /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Sep 21 17:16:08 shasta /kernel: sio1 not found at 0x3e8 Sep 21 17:16:08 shasta /kernel: sio2 at 0x2f8-0x2ff irq 3 on isa Sep 21 17:16:08 shasta /kernel: sio3 not found at 0x300 Sep 21 17:16:08 shasta /kernel: lpt0 at 0x378-0x37f irq 7 on isa Sep 21 17:16:09 shasta /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Sep 21 17:16:09 shasta /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Sep 21 17:16:09 shasta /kernel: nca0 at 0x350-0x35f irq 5 on isa ... various CRON[xxx]: (root) CMD (/usr/libexec/atrun) every 5 minutes until I got home... Sep 21 21:51:52 shasta /kernel: FreeBSD 2.2-STABLE #0: Sat Aug 23 20:00:30 PDT 1997 Sep 21 21:51:53 shasta /kernel: Features=0x1 Sep 21 21:51:54 shasta /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Sep 21 21:51:54 shasta /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Sep 21 21:51:54 shasta /kernel: sio1 at 0x3e8-0x3ef irq 12 on isa Sep 21 21:51:55 shasta /kernel: sio2 at 0x2f8-0x2ff irq 3 on isa Sep 21 21:51:55 shasta /kernel: sio3 not found at 0x300 Sep 21 21:51:55 shasta /kernel: lpt0 at 0x378-0x37f irq 7 on isa Sep 21 21:51:55 shasta /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Sep 21 21:51:56 shasta /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Sep 21 21:51:56 shasta /kernel: nca0 at 0x350-0x35f irq 5 on isa Output from dmesg(8): Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE #0: Sat Aug 23 20:00:30 PDT 1997 root@shasta.wstein.com:/usr/src/sys/compile/S_ISDN CPU: AMD Enhanced Am486DX4 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x494 Stepping=4 Features=0x1 real memory = 16777216 (16384K bytes) avail memory = 14848000 (14500K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:16 chip1 rev 13 on pci0:18:0 pci0:18:1: UMC, device=0x673a, class=storage (ide) [no driver assigned] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x3e8-0x3ef irq 12 on isa sio1: type 16550A sio2 at 0x2f8-0x2ff irq 3 on isa sio2: type 16550A sio3 not found at 0x300 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S nca0 at 0x350-0x35f irq 5 on isa nca0: type NCR-53C400 nca0 waiting for scsi devices to settle (nca0:2:0): "SANYO CRD-400I 1.32" type 5 removable SCSI 2 cd0(nca0:2:0): CD-ROM cd present [400000 x 2048 byte records] npx0 flags 0x1 on motherboard npx0: INT 16 interface From owner-freebsd-hackers Sun Sep 21 22:41:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14744 for hackers-outgoing; Sun, 21 Sep 1997 22:41:21 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA14735 for ; Sun, 21 Sep 1997 22:41:17 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id HAA08860; Mon, 22 Sep 1997 07:40:15 +0200 (CEST) To: "Jordan K. Hubbard" cc: Eivind Eklund , Nate Williams , Eivind Eklund , hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-reply-to: Your message of "Sun, 21 Sep 1997 16:50:38 PDT." <24205.874885838@time.cdrom.com> Date: Mon, 22 Sep 1997 07:40:15 +0200 Message-ID: <8858.874906815@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <24205.874885838@time.cdrom.com>, "Jordan K. Hubbard" writes: >> It doesn't. However, it has a formulation that IMHO is too >> restrictive - that free() 'makes the memory available for further use >> by the program' (from memory). Thus, an implementation of > >Bizarre, are you sure? That's exactly 180 degrees counter to what >I've always learned about storage allocators: If you count on free() >to not corrupt the data you pass to it, you deserve to lose and lose >big. Look, it's really very simple. In other text it says that you cannot know what's in the storage you get with malloc, so the only way to know if you got the same storage back would be to compare the pointer. Second, I think the above wording is intended to avoid implementations of this kind: static u_char *malloc_ptr = end; void * malloc(int n) { void *p; p = malloc_ptr; malloc_ptr += n; return p; } void free(void *) { } -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hackers Sun Sep 21 22:41:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14830 for hackers-outgoing; Sun, 21 Sep 1997 22:41:53 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA14815 for ; Sun, 21 Sep 1997 22:41:48 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id AAA00431; Mon, 22 Sep 1997 00:40:18 -0500 (EST) From: "John S. Dyson" Message-Id: <199709220540.AAA00431@dyson.iquest.net> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <199709220446.WAA29021@rocky.mt.sri.com> from Nate Williams at "Sep 21, 97 10:46:26 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 22 Sep 1997 00:40:18 -0500 (EST) Cc: sef@kithrup.com, tim@ppp6431.on.sympatico.ca, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams said: > > >> char *cp = malloc(100); > > >> if (cp) { > > >> free(cp); > > >> cp = malloc(100); > > >> } > > >No, if you want the above code to always result in a non-NULL cp, > > >free() cannot ever return the memory back to the OS. > > > > Really? Would you like to explain that idiotic statement? Back it up with > > some facts, explanations, or justifications? > > If between the lines of free(cp) you get a context switch, another > application allocates enough memory to completely use up the VM in the > system, and then the process is switched to again, the second malloc > could fail due to lack of VM. Again, this is a *very* rare case, but > could happen if free() returns memory to the OS. > Actually, the problem can occur after a successful malloc, with the type of swap allocation that we have. Since we don't reserve swap space, there can be a program failure at fault time due to VM limits. I think that this whole discussion handles only an end-case, that if it continues on, will have a possibility of us making a decision towards some mediocre compromise. IMO, allowing malloc to return memory to the system, either by address space modification, or through hints to the OS, shouldn't cause any reasonable portability problems. It is only in the case of the system being in "sorry shape" that there is any difference in behavior between malloc proactively freeing memory or not. Just my 2p or 2 cents or whatever. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Sun Sep 21 22:42:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14898 for hackers-outgoing; Sun, 21 Sep 1997 22:42:22 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA14891 for ; Sun, 21 Sep 1997 22:42:20 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id WAA05813; Sun, 21 Sep 1997 22:42:18 -0700 (PDT) Date: Sun, 21 Sep 1997 22:42:18 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199709220542.WAA05813@kithrup.com> To: toor@dyson.iquest.net Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk yes, yes, yes, I admit I'm wrong. I'm wrong wrong wrong. Someone just go out and shoot me. End my miserable existence. Oh, the shame of it all! :) Sean. From owner-freebsd-hackers Sun Sep 21 22:59:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16091 for hackers-outgoing; Sun, 21 Sep 1997 22:59:34 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16084 for ; Sun, 21 Sep 1997 22:59:29 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA15014; Sun, 21 Sep 1997 22:55:10 -0700 (MST) From: Terry Lambert Message-Id: <199709220555.WAA15014@usr07.primenet.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: perhaps@yes.no (Eivind Eklund) Date: Mon, 22 Sep 1997 05:55:09 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, phk@critter.freebsd.dk, gram@cdsec.com, hackers@FreeBSD.ORG In-Reply-To: <199709211735.TAA20824@bitbox.follo.net> from "Eivind Eklund" at Sep 21, 97 07:35:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > You could determine that a list is circular by maintaining a count of > > the number of objects that are supposed to be on the freelist. Then > > you count the number of "next" traversals which occur, and when it > > excceeds the count of how many are supposed to be there, then you > > know you have a problem. > > Why make it this hard, and subject to trashing of the list count? The > following code will check for a circular loop (no knowledge of length > required) for a single-linked list: Because we want to locate the erroneous entries, and the entries most likely to have been trashed to create the loop in the first place, in order to report them (and hopefully get the probem corrected). This whole thread has really been about finding problems in code using the memory allocation code. Simply aborting is not useful, either. It assumes that the debugger has knowledge of the malloc library list structure. This structure is internal (ie: never exported, and thus unavailable to the debugger for this use). 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-hackers Sun Sep 21 23:09:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA16917 for hackers-outgoing; Sun, 21 Sep 1997 23:09:46 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA16909 for ; Sun, 21 Sep 1997 23:09:43 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id XAA15857; Sun, 21 Sep 1997 23:09:38 -0700 (MST) From: Terry Lambert Message-Id: <199709220609.XAA15857@usr07.primenet.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: ac199@hwcn.org Date: Mon, 22 Sep 1997 06:09:37 +0000 (GMT) Cc: sef@kithrup.com, hackers@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at Sep 21, 97 10:35:52 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > No, if you want the above code to always result in a non-NULL cp, > free() cannot ever return the memory back to the OS. ...with the caveat that the OS is a memory overcommit OS, such that the next call may fail because of another process. > However, I believe the actual wording is sufficiently ambigous that > this debate has been fought long and hard in other forums. Including this one, about 7 months ago... > Anything which is this controversial can be implemented either way > and be right. > > Besides, there ain't no standard which can tell me that free() can't > return memory to the OS. Wrong. Technically, the reallocation does not have to check its return value, and may assume the allocation never fails, according to the standard. The question to ask of the code is whether it *needs* the memory, or merely *wants* the memory. If it merely *wants* the memory, then a failed allocation is a recoverable condition, since it checks the return value of the function. If you want to be entirely technical about it, a malloc only has to return a pointer that becomes valid when used. That means that it can return a pointer to an unmapped page, and map the page in when the allocated area is actually written (or read -- though that's not too useful). The allocation of backing store for the allocated region could fail at that time, as well, technically. So a malloc can return a non-failure indicator, yet have failed. Ah, the mysteries of memory overcommit! 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 21 23:18:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA17732 for hackers-outgoing; Sun, 21 Sep 1997 23:18:51 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA17724 for ; Sun, 21 Sep 1997 23:18:49 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id XAA16127; Sun, 21 Sep 1997 23:17:30 -0700 (MST) From: Terry Lambert Message-Id: <199709220617.XAA16127@usr07.primenet.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: sef@Kithrup.COM (Sean Eric Fagan) Date: Mon, 22 Sep 1997 06:17:30 +0000 (GMT) Cc: tim@ppp6431.on.sympatico.ca, hackers@FreeBSD.ORG In-Reply-To: <199709220258.TAA27605@kithrup.com> from "Sean Eric Fagan" at Sep 21, 97 07:58:03 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> char *cp = malloc(100); > >> if (cp) { > >> free(cp); > >> cp = malloc(100); > >> } > >No, if you want the above code to always result in a non-NULL cp, > >free() cannot ever return the memory back to the OS. > > Really? Would you like to explain that idiotic statement? Back it up with > some facts, explanations, or justifications? The program may be context-switched between the free and the second malloc. If the implementation returns freed memory to the system, then it is possible for another process to allocate the freed memory (this assumes that the free occurs on a page boundry). When this happens, the next malloc may fail, if that was the last unallocated page in the system. Unlikely as hell, but possible, and technically in violation of the standard, at that point. > I did not point that out because I thought it was obvious. And it doesn't > change my position: if the first malloc() succeeded, then, even if there is > no more space available after that first malloc(), the free() and subsequent > malloc() are required to work. Right. But because a process competes with other processes for resources, it may very well lose, right at this critical point. This is a known (and accepted) danger of memory overcommit systems. 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-hackers Sun Sep 21 23:23:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18061 for hackers-outgoing; Sun, 21 Sep 1997 23:23:58 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18056 for ; Sun, 21 Sep 1997 23:23:57 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id XAA16366; Sun, 21 Sep 1997 23:23:55 -0700 (MST) From: Terry Lambert Message-Id: <199709220623.XAA16366@usr07.primenet.com> Subject: Re: "Load Defaults" was my cure! (Was: Re: Do *you* have problems with To: dkelly@hiwaay.net Date: Mon, 22 Sep 1997 06:23:54 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709220300.WAA02213@nospam.hiwaay.net> from "dkelly@hiwaay.net" at Sep 21, 97 10:00:39 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > > fdc0: NEC 72065B > > > > As i've stated earlier, this is just non-information only. You gotta > > open the case of your machine to learn what FDC you're using. The > > above information is wrong anyway, and it's impossible to get the > > actual FDC make by (documented) electronic means. > > Arrrg. I've been meaning to open the cases. Rebooted today and forgot. I have revised probe code which I can send you. It is a kind of half-way transition to a seperation of the controller and floppy device attaches into seperate drivers. It can probe 12 different controllers (one more than Linux 8-)) before it gets confused. > > I should drop the above message from the floppy driver, it's less than > > useless. > > > > Tor Egge seems to have traced his problem down to the Winbond chip, > > and the best guess one can make out of his test data is that the bus > > interface of the chip (*not* the floppy interface) is broken. Perhaps > > it's not noticing DMA overruns. I can't probe this particular chip, because I don't have a feature list that distinguishes it... sorry. I probably recognize it as a different chipset. 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-hackers Sun Sep 21 23:27:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18264 for hackers-outgoing; Sun, 21 Sep 1997 23:27:51 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18255 for ; Sun, 21 Sep 1997 23:27:48 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id XAA16498; Sun, 21 Sep 1997 23:27:34 -0700 (MST) From: Terry Lambert Message-Id: <199709220627.XAA16498@usr07.primenet.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Mon, 22 Sep 1997 06:27:34 +0000 (GMT) Cc: sef@Kithrup.COM, hackers@FreeBSD.ORG In-Reply-To: <199709220412.GAA08834@ocean.campus.luth.se> from "Mikael Karpberg" at Sep 22, 97 06:12:36 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > However, if I understand everything right, phkmalloc doesn't shrink the > program's space, but simply tells the OS that the page's contents are not > important and can be disregarded. The program still has enough space > allocated on the swap to write the page to, but there is no need to write > it to that space, and read it back when the memory is accessed. Instead > the page is not reclaimed until the OS needs a free page, and if the program > wants to use the page later, it gets a zeroed page from the system. This > can be guaranteed since there is space on the swap for this page, so another > program can have an idle page be swapped out to there, and the program can > then get that page, after it has been zeroed. > > Then it would indeed be guaranteed that the second malloc() would succeed. > > Am I right? Maybe I'm completely off instead? :-) You're wrong. Memory is overcommited. This means that there is no guarantee that a backing page exists for the kernel to be able to associate it with the process as a result of the fault. 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-hackers Mon Sep 22 00:12:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA20989 for hackers-outgoing; Mon, 22 Sep 1997 00:12:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA20970 for ; Mon, 22 Sep 1997 00:12:04 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA16569; Mon, 22 Sep 1997 00:12:27 -0700 (PDT) To: Warner Losh cc: hackers@FreeBSD.ORG Subject: Re: mtree vs /usr/src In-reply-to: Your message of "Sun, 21 Sep 1997 23:12:25 MDT." <199709220512.XAA21951@harmony.village.org> Date: Mon, 22 Sep 1997 00:12:26 -0700 Message-ID: <16553.874912346@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Why is /usr/src owned bin.bin? Why does make installworld insist on > resetting it back to bin.bin, even after I've chown'd it to imp? > > Just wondering if there is a good reason for this... Hmmm. Frankly, I don't even see how it can happen. The make hierarchy should have DESTDIR set correctly to point into /usr/obj as a result of Satoshi's patches, and a quick review of my own make world log shows this to be the case. Maybe your source tree needs a kick in the pants. :) Jordan From owner-freebsd-hackers Mon Sep 22 01:03:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA23953 for hackers-outgoing; Mon, 22 Sep 1997 01:03:08 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA23945 for ; Mon, 22 Sep 1997 01:03:03 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id DAA00175; Mon, 22 Sep 1997 03:02:40 -0500 (EST) From: "John S. Dyson" Message-Id: <199709220802.DAA00175@dyson.iquest.net> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-Reply-To: <199709220627.XAA16498@usr07.primenet.com> from Terry Lambert at "Sep 22, 97 06:27:34 am" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 22 Sep 1997 03:02:40 -0500 (EST) Cc: karpen@ocean.campus.luth.se, sef@Kithrup.COM, hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert said: > > > Then it would indeed be guaranteed that the second malloc() would succeed. > > > > Am I right? Maybe I'm completely off instead? :-) > > You're wrong. Memory is overcommited. This means that there is no > guarantee that a backing page exists for the kernel to be able to > associate it with the process as a result of the fault. > > I would tend to use softer language, but there is no guarantee that memory exists immediately after a 400K malloc, for example. Those pages aren't faulted until needed. There is some attempt to avoid the most obvious problems, but no guarantees. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Mon Sep 22 02:24:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA28501 for hackers-outgoing; Mon, 22 Sep 1997 02:24:26 -0700 (PDT) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA28493 for ; Mon, 22 Sep 1997 02:24:19 -0700 (PDT) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id LAA00951 for ; Mon, 22 Sep 1997 11:15:28 +0200 (SAT) Received: by citadel via recvmail id 949; Mon Sep 22 11:15:26 1997 by gram.cdsec.com (8.8.5/8.8.5) id KAA07518 for hackers@freebsd.org; Mon, 22 Sep 1997 10:56:11 +0200 (SAT) From: Graham Wheeler Message-Id: <199709220856.KAA07518@cdsec.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: hackers@freebsd.org Date: Mon, 22 Sep 1997 10:56:10 +0200 (SAT) In-Reply-To: <199709220555.WAA15014@usr07.primenet.com> from "Terry Lambert" at Sep 22, 97 05:55:09 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just an update on the original problem I had - on Friday we restarted the gateway process, this time linked with the non-debug version of the libmalloc library (the version linked with the debug version had been running for about 30 hours with no problems). As of this (Monday) morning, the process is still running happily. I will still try get the client to run a version linked against the GNU malloc library sometime this week, and see how that goes. And I will also try the efence approach, although the libmalloc_d should have caught overruns if there are any (and I'm pretty sure there aren't, having checked every new/delete/memcpy/memset/strcpy/strcat and looping pointer iteration with a fine tooth comb by now, and having added about 100 more asserts to the code). So maybe there is a bug in pkhmalloc after all...(sorry Poul). For those who missed the start of this thread, when linked with pkhmalloc, the gateway process was running for at most thirty minutes at a time before ending in an infinite loop in the malloc code. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ From owner-freebsd-hackers Mon Sep 22 02:33:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA28951 for hackers-outgoing; Mon, 22 Sep 1997 02:33:17 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA28946 for ; Mon, 22 Sep 1997 02:33:12 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id LAA27367; Mon, 22 Sep 1997 11:33:06 +0200 (MET DST) Message-ID: <19970922113306.60050@bitbox.follo.net> Date: Mon, 22 Sep 1997 11:33:06 +0200 From: Eivind Eklund To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <199709211735.TAA20824@bitbox.follo.net> <199709220555.WAA15014@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199709220555.WAA15014@usr07.primenet.com>; from Terry Lambert on Mon, Sep 22, 1997 at 05:55:09AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 22, 1997 at 05:55:09AM +0000, Terry Lambert wrote: > > > You could determine that a list is circular by maintaining a count of > > > the number of objects that are supposed to be on the freelist. Then > > > you count the number of "next" traversals which occur, and when it > > > excceeds the count of how many are supposed to be there, then you > > > know you have a problem. > > > > Why make it this hard, and subject to trashing of the list count? The > > following code will check for a circular loop (no knowledge of length > > required) for a single-linked list: > > Because we want to locate the erroneous entries, and the entries most > likely to have been trashed to create the loop in the first place, in > order to report them (and hopefully get the probem corrected). > > This whole thread has really been about finding problems in code using > the memory allocation code. So? I can't see that you need to count to do this. The list itself is enough, even though the counter in itself might be information you would like to have. You just don't need it for actually finding the loop, the loop length or where the loop start; you cut the part which actually described this, the code was just a better way of implementing the list verificiation itself, and not to be taken verbatim. abort() was just to make it obvious where you saw that the list had looped. Eivind. From owner-freebsd-hackers Mon Sep 22 04:15:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06462 for hackers-outgoing; Mon, 22 Sep 1997 04:15:07 -0700 (PDT) Received: from haywire.dialix.com.au (news@haywire.dialix.com.au [202.12.86.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06449 for ; Mon, 22 Sep 1997 04:15:00 -0700 (PDT) Received: (from news@localhost) by haywire.dialix.com.au id TAA28624 for freebsd-hackers@freebsd.org; Mon, 22 Sep 1997 19:14:54 +0800 (WST) X-Authentication-Warning: haywire.dialix.com.au: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.dialix.com.au with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 22 Sep 1997 11:14:53 GMT From: peter@netplex.com.au (Peter Wemm) Message-ID: <874926893.273098@haywire.dialix.com.au> Organization: DIALix Internet Services References: <199709220512.XAA21951@harmony.village.org> Subject: Re: mtree vs /usr/src Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <16553.874912346@time.cdrom.com>, jkh@time.cdrom.com (Jordan K. Hubbard) writes: >> Why is /usr/src owned bin.bin? Why does make installworld insist on >> resetting it back to bin.bin, even after I've chown'd it to imp? >> >> Just wondering if there is a good reason for this... > > Hmmm. Frankly, I don't even see how it can happen. The make > hierarchy should have DESTDIR set correctly to point into /usr/obj as > a result of Satoshi's patches, and a quick review of my own make world > log shows this to be the case. Maybe your source tree needs a kick > in the pants. :) I've been toying with the idea of a 'nochange' attribute for the mtree specs. ie: it'll create the file/directory if it is missing, but will not touch it if it's already there. > Jordan From owner-freebsd-hackers Mon Sep 22 04:29:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06895 for hackers-outgoing; Mon, 22 Sep 1997 04:29:11 -0700 (PDT) Received: from haywire.dialix.com.au (news@haywire.dialix.com.au [202.12.86.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06889 for ; Mon, 22 Sep 1997 04:29:04 -0700 (PDT) Received: (from news@localhost) by haywire.dialix.com.au id TAA28791 for freebsd-hackers@freebsd.org; Mon, 22 Sep 1997 19:28:57 +0800 (WST) X-Authentication-Warning: haywire.dialix.com.au: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.dialix.com.au with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 22 Sep 1997 11:28:57 GMT From: peter@spinner.netplex.com.au (Peter Wemm) Message-ID: <874927737.27738@haywire.dialix.com.au> Organization: DIALix Internet Services References: <199709182330.BAA07105@bitbox.follo.net> Subject: Re: cvs pserver mode Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , marcs@znep.com (Marc Slemko) writes: > On Fri, 19 Sep 1997, Eivind Eklund wrote: > >> > >> > >> does any of you have trouble using pserver mode of cvs? >> > >First, don't use pserver. It sucks. Badly. It stores unencrypted >> > >passwords on the clients disk and anyone with a shell on the server an >> > >steal connections (and hence passwords) from users connecting. Bad. >> > >Secondly, you need the --allow-root option to tell it what repositories to >> > >use. This is new in 1.9.10 or something like that. >> > >> > [option list deleted] >> > - give an account (say, "mygroup") to them and use rsh/ssh >> >> I consider this the only sensible thing. Give them an account with >> the shell pointing at a text file containing >> #!/bin/sh >> /usr/bin/cvs server >> >> and set permissions so they can't write to the cvs repository. Little > > To do this, you need to hack cvs to allow read-only respositories and be > sure that you have _no_ way that anyone can upload arbitrary files that > will be readable by the user running the above. If you have something No need to hack if you are using the FreeBSD version, it's got a '-R' option to allow readonly operation (A CD-ROM cvs tree was the original intended use of this). > like anonymous ftp uploads which are world readable, then they can > trivially get a shell as the uid cvs runs as. Hmm, wonder if the > --allow-root option works with cvs "server"... > >> security risk (except that they can exploit bugs in cvs) - even less >> if you go for a chrooted environment (which will probably need some >> hacking to get set up) > > From owner-freebsd-hackers Mon Sep 22 04:29:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06924 for hackers-outgoing; Mon, 22 Sep 1997 04:29:20 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06902 for ; Mon, 22 Sep 1997 04:29:13 -0700 (PDT) Received: from ws6303-f (root@firix [10.1.143.100]) by zwei.siemens.at with ESMTP id NAA10989; Mon, 22 Sep 1997 13:28:25 +0200 (MET DST) Received: from ws6423.gud.siemens.at (ws6423-f) by ws6303-f with ESMTP (1.40.112.8/16.2) id AA068557676; Mon, 22 Sep 1997 13:27:56 +0200 Received: by ws6423.gud.siemens.at (SMI-8.6/SMI-SVR4) id NAA25447; Mon, 22 Sep 1997 13:27:08 +0200 Date: Mon, 22 Sep 1997 13:27:08 +0200 From: lada@ws6303.gud.siemens.at (marino.ladavac@siemens.at) Message-Id: <199709221127.NAA25447@ws6423.gud.siemens.at> To: hackers@FreeBSD.ORG, sef@Kithrup.COM Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Md5: yIFTgeQCbmosY3/MoPSKgw== Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 04:00:14 MET 1997 > Date: Sun, 21 Sep 1997 18:29:27 -0700 (PDT) > From: Sean Eric Fagan > To: hackers@FreeBSD.ORG > Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) > X-Loop: FreeBSD.org > > In article <19970922015128.32876.kithrup.freebsd.hackers@bitbox.follo.net> you write: > >On Sun, Sep 21, 1997 at 04:50:38PM -0700, Jordan K. Hubbard wrote: > >> > It doesn't. However, it has a formulation that IMHO is too > >> > restrictive - that free() 'makes the memory available for further use > >> > by the program' (from memory). Thus, an implementation of > >> Bizarre, are you sure? That's exactly 180 degrees counter to what > >> I've always learned about storage allocators: If you count on free() > >> to not corrupt the data you pass to it, you deserve to lose and lose > >> big. > >My typo. I mean 'further allocation'. > > With either wording, eivind, fortunately, is wrong ;). > > malloc() is constrained to not return the same memory block twice unless it > has been free()'d first. > > ANSI C also makes no distinction between OS and standard library code -- > that is, malloc() could be a system call, as far as ANSI C is concerned. > > The requirement there is simply that free() makes the memory available for > further allocation (that being the only way an ANSI C conformant application > can get at such memory). > > The wording for malloc() and free() was chosen very carefully, to allow > embedded applications to work -- in such applications, there is no dynamic > allocation of memory from the OS (since there isn't one); instead, many of > them have a chunk of memory that is part of the program's address space, and > malloc() and free() simply parcel it up. > > Lastly, the wording for free() is, as I understood it when I last read it, > meant to convey the requirement that: > > char *cp = malloc(100); > if (cp) { > free(cp); > cp = malloc(100); > } > > always result in a non-NULL cp. Eivind is unfortunately correct, as the above requirement need not be fulfilled on a modern OS which is very low on swap and just cannot reserve enough swap space for the program (because some other program reserved it for himself between free() and malloc() again). Thus, to achieve strict ISO C conformance on the hosted system the pages, once allocated to the process, must not be released to the OS except on the process rundown. Bummer. /Marino > > So, in conclusion: yes, the OS is perfectly free to have free() return the > memory back to the OS, even though traditional systems did not do this most > of the time. (It is a quality of implementation issue, and I think may be > referenced as such in the X3J11 notes/comments/explanation that are not > officially part of the standard.) > From owner-freebsd-hackers Mon Sep 22 07:07:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14420 for hackers-outgoing; Mon, 22 Sep 1997 07:07:49 -0700 (PDT) Received: from gvr.gvr.org (root@gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14414 for ; Mon, 22 Sep 1997 07:07:45 -0700 (PDT) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id QAA16408 for FreeBSD-hackers@freebsd.org; Mon, 22 Sep 1997 16:07:29 +0200 (MET DST) From: Guido van Rooij Message-Id: <199709221407.QAA16408@gvr.gvr.org> Subject: undump for perl dumps To: FreeBSD-hackers@freebsd.org (FreeBSD-hackers) Date: Mon, 22 Sep 1997 16:07:29 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone have a working undump fro perl5 dumps? -Guido -- Guido van Rooij | guido@gvr.org <--- NOTE NEW ADDRESS Herman heijermanslaan 21 | Phone: ++31.40.2127794 5644 TG Eindhoven | The Netherlands | FreeBSD core-team member From owner-freebsd-hackers Mon Sep 22 07:10:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14703 for hackers-outgoing; Mon, 22 Sep 1997 07:10:36 -0700 (PDT) Received: from ingenieria ([168.176.15.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA14678 for ; Mon, 22 Sep 1997 07:10:18 -0700 (PDT) Received: by ingenieria (SMI-8.6/SMI-SVR4) id JAA25740; Mon, 22 Sep 1997 09:05:00 -0400 Date: Mon, 22 Sep 1997 09:04:59 -0400 (EDT) From: Yonny Cardenas To: hackers@freebsd.org Subject: RIPv2, Routed and gated in FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Vernon schryver wrote: Date: Fri, 19 Sep 1997 16:27:32 -0600 From: Vernon Schryver Subject: RIPv2, gated, and routed } > Add interface ppp0 200.20.30.1 --> 9.30.20.200/32 } } }If this RouteD - you have the wrong list. Agreed. Since the topic has not gone away, and some incorrect statements have been made, I'll answer. }If this RouteD - you have the wrong list. Since it is ICMP router }discovery - I suspect you have Vernon Schryver's updated version. It looks likely. } > Why 9.30.20.200/32 ?. It=B4s 200.20.30.9.=20 } } I was going to tell you that not only do you have the wrong list } but you also are using an address in IBM's class A block. However, } this is obviously a case of a missing htonl() or ntohl() invocation } on an Intel processor (which stores fullwords and halfwords with the } least significant byte in lowest addressable byte). People outside SGI found a bunch of htonl()/ntohl() bugs (I think) last year. The most current source is in ftp.sgi.com:sgi/src/routed.tar.Z ] >the ppp interface supports multicast: ] ] >ppp0: flags=3D8051 mtu 1500 ] >(on my system) As long as your PPP interface just stuffs multicast packets into the PPP pipe, and your kernel does the right things with multicast packets that come out of the PPP pipe, the right things should happen. However, since PPP is a point-to-pint interface (as indicated by common sense and IFF_POINTOPOINT bit in your struct if_net as shown by your system), it is just as well for a RIPv2 implementation to send RIPv2 using unicast addresses. ] Is OK, I am usig FreeBSD 2.2.1 and gated 3.5Beta3. I do not know how recent that is. ] >Try gated; it can support RIPv2 better. I beg to differ. From what I saw of both 3.5 and 3.6, RIPv2 is not the favorite protocol of `gated`. When last I ported 3.5, some of the gated RIPv2 bugs were still there, a year or more after I reported them, and some of the implementation holes still existed (e.g. support for RIPv2 authentication). ] >it looks to me that routed's support of RIP2 is broken. ] >I can be wrong. Which OS version you are using? what is your ] >network configuration? RIPv2 in `routed` works fine on a bunch of systems in the internal Silicon Graphics network, including over PPP links. There is a total of about 10,000 systems on 1,500 IP networks using the 100s of class-Cs and several class-Bs SGI has been allocated over the years. A few 100 systems are using RIPv2. OSPF and IGRP are also in use. The PPP code invovled is almost but not entirely the standard IRIX code (i.e. mine). ] I have two box how routers, one run gated (A) and other run routed (B), ] conected with link ethernet, the router (A) anounnce OK to ] other neighbor EGP, all its paths. ] ] ------ EGP -------9 RIP 1-------- RIP ] | |----... --------| A |**************| B |-------- ] ------ ------- -------- 200.20.30 ] >> Need configuration especial in file /etc/gateways ? How ? ] ] >you need it for routed; try gated, and I have seen you can write ] >gated.conf ;-) Nonsense! In general, you do not need /etc/gateways either with the 4.*BSD code based on Sam Leffler's primordial implementation nor with my code. In the old version of `routed`, /etc/gateways was needed only for some odd cases, such as telling `routed` to ignore an interface. In the FreeBSD version, you can tell `routed` to ignore an interface on the command line. Please read the fine (or perhaps not so fine) man page. In this case, I probably would run `gated` on system "A", doing EGP on the link to the left system "A" and RIPv2 on the PPP link. I would run either `gated` or `routed`, whichever I was comfortable with, on system "B". Depending on what is to the right of the PPP link, it might be possible to use static default routes on systems to the right, not use any routig protocol on the PPP link, and use a suitable gated.conf file to cause `gated` to advertise the network(s) on the right into EGP on the left. Vernon Schryver, vjs@sgi.com ------------------------------------------------------------------------- YONNY CARDENAS B. Systems Engineer || || ||| || Universidad Nacional de Colombia || || || | || Email : yonny@ingenieria.ingsala.unal.edu.co ||||||| || ||| From owner-freebsd-hackers Mon Sep 22 07:47:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA16935 for hackers-outgoing; Mon, 22 Sep 1997 07:47:32 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA16930 for ; Mon, 22 Sep 1997 07:47:27 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xD9ll-0000WX-00; Mon, 22 Sep 1997 08:47:25 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id IAA13197; Mon, 22 Sep 1997 08:47:17 -0600 (MDT) Message-Id: <199709221447.IAA13197@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: mtree vs /usr/src Cc: hackers@freebsd.org In-reply-to: Your message of "Mon, 22 Sep 1997 00:12:26 PDT." <16553.874912346@time.cdrom.com> References: <16553.874912346@time.cdrom.com> Date: Mon, 22 Sep 1997 08:47:17 -0600 From: Warner Losh Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <16553.874912346@time.cdrom.com> "Jordan K. Hubbard" writes: : Hmmm. Frankly, I don't even see how it can happen. The make : hierarchy should have DESTDIR set correctly to point into /usr/obj as : a result of Satoshi's patches, and a quick review of my own make world : log shows this to be the case. Maybe your source tree needs a kick : in the pants. :) Ummm, this is the installworld part of the make world, not the buildworld part of the make world. This is with the latest Makefile, on the main branch. When installworld is done, DESTDIR isn't set (or is /, I forget which). I've seen this happen three times now, so I'm sure I'm not imagining things. Warner From owner-freebsd-hackers Mon Sep 22 08:49:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21063 for hackers-outgoing; Mon, 22 Sep 1997 08:49:18 -0700 (PDT) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21058 for ; Mon, 22 Sep 1997 08:49:15 -0700 (PDT) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id LAA05007 for ; Mon, 22 Sep 1997 11:49:03 -0400 (EDT) Date: Mon, 22 Sep 1997 11:49:02 -0400 (EDT) From: Charles Owens To: hackers list FreeBSD Subject: LISA'97: how about a BOF session? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I'm planning on attending LISA'97, (Systems and Network Admin conference, put on by USENIX). It's the last week of October and is being held in San Diego. Has a FreeBSD Birds-Of-a-Feather session been scheduled? Are enough FreeBSD users going to warrant one? I see that Walnut Creek is amongst the vendors that will be in attendance. Who from the FreeBSD camp will at that booth waving the FreeBSD banner? Thanks, --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-hackers Mon Sep 22 08:54:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21498 for hackers-outgoing; Mon, 22 Sep 1997 08:54:34 -0700 (PDT) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21487; Mon, 22 Sep 1997 08:54:18 -0700 (PDT) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id RAA14375; Mon, 22 Sep 1997 17:57:32 +0200 (SAT) Received: by citadel via recvmail id 14342; Mon Sep 22 17:57:14 1997 by gram.cdsec.com (8.8.5/8.8.5) id RAA09859; Mon, 22 Sep 1997 17:37:32 +0200 (SAT) From: Graham Wheeler Message-Id: <199709221537.RAA09859@cdsec.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Mon, 22 Sep 1997 17:37:31 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709221528.IAA19479@hub.freebsd.org> from "Jonathan M. Bresler" at Sep 22, 97 08:28:41 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Graham, > have you been able to create a minimal program that tickles > the bug? if i remember correctly, one suspicion is that > the links that malloc uses to track memory allocations > are being corrupted....creating a circular list. > > jmb Unfortunately not. At present most of our clients are still running the firewall software on FreeBSD 2.1.0, and have no problem (with at least one site of about 2000 users having run the gateway process for about four months without a restart or reboot). We recently upgraded a couple of sites to FreeBSD 2.2.2, mostly to allow Adaptec 2940 support. Of these sites, most are either running proxies only or have fairly low traffic. Only one site has been affected by the bug, with the main distinguishing characteristic being a very heavy network load (there are approximately 5000 users behind this firewall, with quite heavy WWW browser useage taking place). As the loop can occur anywhere where there is a call to malloc, directly or indirectly, we have not been able to isolate it at all. Most of the C++ classes that are used have their own test programs to test them in isolation, but no problems have been found with these. Also, many of the classes used by the gateway program are used in other modules in the firewall; none of these modules have shown any problems. One thing that can be said about the gateway program is that it performs far more dynamic memory allocations and frees than any other module in the firewall (every packet that passes through the gateway, for starters). -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ From owner-freebsd-hackers Mon Sep 22 10:53:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04252 for hackers-outgoing; Mon, 22 Sep 1997 10:53:37 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04247 for ; Mon, 22 Sep 1997 10:53:34 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA00947; Mon, 22 Sep 1997 10:53:55 -0700 (PDT) To: Charles Owens cc: hackers list FreeBSD Subject: Re: LISA'97: how about a BOF session? In-reply-to: Your message of "Mon, 22 Sep 1997 11:49:02 EDT." Date: Mon, 22 Sep 1997 10:53:54 -0700 Message-ID: <943.874950834@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm planning on attending LISA'97, (Systems and Network Admin conference, > put on by USENIX). It's the last week of October and is being held in San > Diego. Has a FreeBSD Birds-Of-a-Feather session been scheduled? Are > enough FreeBSD users going to warrant one? If David Greenman follows up on his plan to attend, I'd say yes, there will be a BOF. If he doesn't then would you like to schedule one? :) > I see that Walnut Creek is amongst the vendors that will be in attendance. > Who from the FreeBSD camp will at that booth waving the FreeBSD banner? I believe that David is the only person slated to attend. I've got a trip to Japan coming up, followed immediately thereafter by Comdex, so I'm trying to keep my own frequent flier miles to a minimum. :) Jordan From owner-freebsd-hackers Mon Sep 22 11:10:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05405 for hackers-outgoing; Mon, 22 Sep 1997 11:10:17 -0700 (PDT) Received: from kerouac.hepcat.org (kerouac.hepcat.org [207.155.93.61]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA05399 for ; Mon, 22 Sep 1997 11:10:14 -0700 (PDT) Received: (from cosmos@localhost) by kerouac.hepcat.org (8.8.5/8.8.5) id LAA08383 for hackers@freebsd.org; Mon, 22 Sep 1997 11:17:46 GMT Message-Id: <199709221117.LAA08383@kerouac.hepcat.org> Subject: cons25 to solaris? To: hackers@freebsd.org Date: Mon, 22 Sep 1997 11:17:45 +0000 (GMT) From: Daniel Leeds Reply-to: dleeds@dfacades.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk im having trouble with term stuff when telnetting from my freebsd laptop to our solaris hosts. is there a way to add the cons25 terminal to solaris terminfo? i tried to make it use /etc/termcap and add the entries, but it didnt work. From owner-freebsd-hackers Mon Sep 22 12:00:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09360 for hackers-outgoing; Mon, 22 Sep 1997 12:00:09 -0700 (PDT) Received: from marlin.exis.net (root@marlin.exis.net [205.252.72.102]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09317 for ; Mon, 22 Sep 1997 12:00:04 -0700 (PDT) Received: from sailfish.exis.net (sailfish.exis.net [205.252.72.104]) by marlin.exis.net (8.8.4/8.8.5) with SMTP id PAA09726; Mon, 22 Sep 1997 15:00:48 -0400 Date: Mon, 22 Sep 1997 14:58:01 -0400 (EDT) From: Stefan Molnar To: Daniel Leeds cc: hackers@FreeBSD.ORG Subject: Re: cons25 to solaris? In-Reply-To: <199709221117.LAA08383@kerouac.hepcat.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > im having trouble with term stuff when telnetting from my freebsd laptop > to our solaris hosts. > > is there a way to add the cons25 terminal to solaris terminfo? > > i tried to make it use /etc/termcap and add the entries, but it didnt > work. here at work I just added a line in my .login to see if I cam coming from console or not, and if not to setenv TERM vt100. After that it work with no problems. Stefan From owner-freebsd-hackers Mon Sep 22 12:35:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12224 for hackers-outgoing; Mon, 22 Sep 1997 12:35:33 -0700 (PDT) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA12219 for ; Mon, 22 Sep 1997 12:35:28 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id UAA28417; Mon, 22 Sep 1997 20:35:24 +0100 (BST) Date: Mon, 22 Sep 1997 20:35:24 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: hackers@freebsd.org Subject: lpr/lpd and HP networked printers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For a long time (at several different sites) I have been using HP laserjets with the 'jetdirect' internal ethernet option, spooling on a FreeBSD box and driving the printer via the lpr protocol. This works fine, but the HP prints a fairly useless 'banner' page after each job; since people are mostly printing documents of only a couple of pages, this is a considerable waste of paper, but I had been unable to discover any way to switch it off. In particular, it is not affected by the "sh" capability in /etc/printcap. Having recently discovered that printing direct to the HP from an old 4.3BSD system did _not_ produce the cover page, I investigated more closely, and discovered that FreeBSD's lpr/lpd do not process the "sh" capability except when printing to a local printer. This is easy enough to fix, though it is not obvious which is the correct way. There are a number of possibilities: 1) Do nothing. I suspect the authors of this code would say that this is how it's meant to be, and that the HP ought to implement its own equivalent of /etc/printcap for this purpose. However, it doesn't, and getting HP to change their code is probably impossible. 2) Change lpr so that it takes into account the "sh" capability when constructing the control file ("sh" would override any -h, -C, -J, -U options on the command line). This is the easiest to do, but in the situation where you have multiple workstations printing through a central server, it requires that the administrator's policy (headers or not) be replicated on all the workstations that access the printer. 3) Change the network output side of lpd to take account of "sh", as it already does when printing to a local printer (ie. modify the control file before sending). 4) As 3), but introduce a new capability to control this behaviour rather than using "sh". 5) Modify both lpr and lpd as above. Any comments? If there is consensus on a change, I will contribute patches. From owner-freebsd-hackers Mon Sep 22 12:42:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12845 for hackers-outgoing; Mon, 22 Sep 1997 12:42:14 -0700 (PDT) Received: from usr06.primenet.com (tlambert@usr06.primenet.com [206.165.6.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA12832 for ; Mon, 22 Sep 1997 12:42:10 -0700 (PDT) Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA18135; Mon, 22 Sep 1997 12:41:56 -0700 (MST) From: Terry Lambert Message-Id: <199709221941.MAA18135@usr06.primenet.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: eivind@bitbox.follo.net (Eivind Eklund) Date: Mon, 22 Sep 1997 19:41:55 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <19970922113306.60050@bitbox.follo.net> from "Eivind Eklund" at Sep 22, 97 11:33:06 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Why make it this hard, and subject to trashing of the list count? The > > > following code will check for a circular loop (no knowledge of length > > > required) for a single-linked list: > > > > Because we want to locate the erroneous entries, and the entries most > > likely to have been trashed to create the loop in the first place, in > > order to report them (and hopefully get the probem corrected). > > > > This whole thread has really been about finding problems in code using > > the memory allocation code. > > So? I can't see that you need to count to do this. The list itself > is enough, even though the counter in itself might be information you > would like to have. You just don't need it for actually finding the > loop, the loop length or where the loop start; you cut the part which > actually described this, the code was just a better way of > implementing the list verificiation itself, and not to be taken > verbatim. abort() was just to make it obvious where you saw that the > list had looped. Seeing that the list has looped does not guarantee that you know where the last valid entry, or first invalid entry, exists. I don't even agree that your method actually finds the list loop, unless you somhow guarantee that the loop goes back to the had such that your pointer comparison is valid. If I have a loop: ,-------------------------. head v | orphan tail (may not exist) >---------------------------------------------'-----------> (3) (1)(2) The problem is that I don't know where the corruption occurred. I don't know if there is an orphan tail (as shown) because the corruption occurred at the point where it upturned (1), or if there is *no* tail, and the corruption occurred because the previous to last entry overwrote the last entries NULL pointer (2), or if there was corruption of the next pointer early in the list (3), causing it to point to a record later in the list than it should. I would like to identify all 4 of these user addresses (which are not equal to the malloc() structure addressses, but instead the user data offset following them, so that I can definitively say "one of these addresses which malloc() returned to you is being overrun by you, and this is resulting in a pointer corruption". 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-hackers Mon Sep 22 12:44:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13111 for hackers-outgoing; Mon, 22 Sep 1997 12:44:06 -0700 (PDT) Received: from usr06.primenet.com (tlambert@usr06.primenet.com [206.165.6.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13100 for ; Mon, 22 Sep 1997 12:44:02 -0700 (PDT) Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA18257; Mon, 22 Sep 1997 12:43:43 -0700 (MST) From: Terry Lambert Message-Id: <199709221943.MAA18257@usr06.primenet.com> Subject: Re: mtree vs /usr/src To: peter@netplex.com.au (Peter Wemm) Date: Mon, 22 Sep 1997 19:43:43 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <874926893.273098@haywire.dialix.com.au> from "Peter Wemm" at Sep 22, 97 11:14:53 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been toying with the idea of a 'nochange' attribute for the mtree > specs. ie: it'll create the file/directory if it is missing, but will not > touch it if it's already there. If you do this, it should warn about differences. If you want to get rid of the warnings, then you would modify the data it is using. This would also be useful for detecting some security problems, either malicious, or in the making. 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-hackers Mon Sep 22 12:51:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13628 for hackers-outgoing; Mon, 22 Sep 1997 12:51:16 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA13618; Mon, 22 Sep 1997 12:51:11 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA12343; Mon, 22 Sep 1997 21:51:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id VAA15384; Mon, 22 Sep 1997 21:47:27 +0200 (MET DST) Message-ID: <19970922214727.WW10801@uriah.heep.sax.de> Date: Mon, 22 Sep 1997 21:47:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Cc: joes@seaport.net (Joseph Stein) Subject: Re: Help... Unexplained crashes under RELENG_2_2 (last message in syslog is from atrun) References: <199709220513.WAA00814@shasta.wstein.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709220513.WAA00814@shasta.wstein.com>; from Joseph Stein on Sep 21, 1997 22:13:18 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Joseph Stein wrote: > This system runs a plethora of daemons -- xntpd, named, sshd, httpd, ftpd, > rwhod -- am I merely overloading it? Or is there some bug in at/atrun? > > I have coredumps enabled but have not yet seen anything in /var/run/crash > from it. Do you have a dumpdev, too? The `savecore_enable' knob is history now (it was a bandaid only against savecore(8) not obeying its minfree file), but dumpdev remains a prerequisite for kernel core dumps. Can you run it on a serial console, with DDB enabled? (Maybe even over a modem line.) Does the machine provide NFS services, or act as a NFS client? I've seen a number of crashes on RELENG_2_2 lately that might be related to NFS. Is the CD-ROM regularly being used? I've seen another couple of crashes that might be related to a bug or two in the cd9660 f/s. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Sep 22 13:02:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA14653 for hackers-outgoing; Mon, 22 Sep 1997 13:02:44 -0700 (PDT) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA14643 for ; Mon, 22 Sep 1997 13:02:37 -0700 (PDT) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id QAA15018; Mon, 22 Sep 1997 16:00:55 -0400 (EDT) Date: Mon, 22 Sep 1997 16:00:55 -0400 (EDT) From: Charles Owens To: "Jordan K. Hubbard" cc: hackers list FreeBSD Subject: Re: LISA'97: how about a BOF session? In-Reply-To: <943.874950834@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997, Jordan K. Hubbard wrote: > > I'm planning on attending LISA'97, (Systems and Network Admin conference, > > put on by USENIX). It's the last week of October and is being held in San > > Diego. Has a FreeBSD Birds-Of-a-Feather session been scheduled? Are > > enough FreeBSD users going to warrant one? > > If David Greenman follows up on his plan to attend, I'd say yes, > there will be a BOF. If he doesn't then would you like to schedule > one? :) Ummm... yeah... though I'll feel a bit silly doing so given that this is my first time at a conference of this sort... I don't really know what to expect from a BOF. If I scheduled one would I then suddenly find myself being expected to set an agenda and lead a discussion... or do folks just show up and chat? I'd certainly perfer if this role was filled by DG... I expect he has much more FreeBSD-specific things to say, though I suppose I'm amiable to whatever... ;-) > > I see that Walnut Creek is amongst the vendors that will be in attendance. > > Who from the FreeBSD camp will at that booth waving the FreeBSD banner? > > I believe that David is the only person slated to attend. I've got a > trip to Japan coming up, followed immediately thereafter by Comdex, so > I'm trying to keep my own frequent flier miles to a minimum. :) > > Jordan --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-hackers Mon Sep 22 13:08:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA15269 for hackers-outgoing; Mon, 22 Sep 1997 13:08:17 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA15230 for ; Mon, 22 Sep 1997 13:08:09 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA05206; Mon, 22 Sep 1997 22:07:58 +0200 (MET DST) Message-ID: <19970922220757.30317@bitbox.follo.net> Date: Mon, 22 Sep 1997 22:07:57 +0200 From: Eivind Eklund To: Terry Lambert Cc: hackers@freebsd.org Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <19970922113306.60050@bitbox.follo.net> <199709221941.MAA18135@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199709221941.MAA18135@usr06.primenet.com>; from Terry Lambert on Mon, Sep 22, 1997 at 07:41:55PM +0000 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 22, 1997 at 07:41:55PM +0000, Terry Lambert wrote: > Seeing that the list has looped does not guarantee that you know > where the last valid entry, or first invalid entry, exists. Agreed. And neither do anything else, except storing extra copies of all pointers somewhere where they can't be overwritten. > I don't even agree that your method actually finds the list loop, unless > you somhow guarantee that the loop goes back to the had such that your > pointer comparison is valid. (I assume you mean 'head' where you write 'had') Read the code again. It work by having two pointers walking the list, one fast and one slow. When the slow pointer intersect with the fast pointer, you know that you have a loop. And the slow pointer _will_ intersect the fast one if you have a loop and the datastructure isn't modified during the execution of your code - it follow the exact same set of links as the fast one, just at half the speed. As for the advanced diagonstics you want - sure, they look nice. However, I've implemented this kind of diagnostics before, and as long as I've exposed the invariant routine so it can be run at any point in the program, I've never needed or had benefit from them. I've found sprinkling the program with invariant checks at strategic points to be much more effective at exposing problems. Eivind. From owner-freebsd-hackers Mon Sep 22 13:42:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA18121 for hackers-outgoing; Mon, 22 Sep 1997 13:42:08 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA18101 for ; Mon, 22 Sep 1997 13:41:58 -0700 (PDT) Received: from argus.tfs.net (pm3-p18.tfs.net [206.154.183.210]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id OAA00105 for ; Mon, 22 Sep 1997 14:40:03 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id PAA03275 for freebsd-hackers@freebsd.org; Mon, 22 Sep 1997 15:41:30 -0500 (CDT) From: Jim Bryant Message-Id: <199709222041.PAA03275@argus.tfs.net> Subject: vt420 termcap needed To: freebsd-hackers@freebsd.org Date: Mon, 22 Sep 1997 15:41:24 -0500 (CDT) Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk does anyone have a termcap entry for the vt420? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Mon Sep 22 14:05:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19821 for hackers-outgoing; Mon, 22 Sep 1997 14:05:13 -0700 (PDT) Received: from usr06.primenet.com (tlambert@usr06.primenet.com [206.165.6.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19804 for ; Mon, 22 Sep 1997 14:05:05 -0700 (PDT) Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id OAA24114; Mon, 22 Sep 1997 14:05:00 -0700 (MST) From: Terry Lambert Message-Id: <199709222105.OAA24114@usr06.primenet.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: eivind@bitbox.follo.net (Eivind Eklund) Date: Mon, 22 Sep 1997 21:05:00 +0000 (GMT) Cc: tlambert@primenet.com, hackers@freebsd.org In-Reply-To: <19970922220757.30317@bitbox.follo.net> from "Eivind Eklund" at Sep 22, 97 10:07:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As for the advanced diagonstics you want - sure, they look nice. > However, I've implemented this kind of diagnostics before, and as long > as I've exposed the invariant routine so it can be run at any point in > the program, I've never needed or had benefit from them. I've found > sprinkling the program with invariant checks at strategic points to be > much more effective at exposing problems. I'd rather it was a debugging option in the malloc library. I would prefer to not have to alter my code to get the checks. It's probably just a stylistic disagreement at this point. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Sep 22 14:17:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20961 for hackers-outgoing; Mon, 22 Sep 1997 14:17:23 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20949 for ; Mon, 22 Sep 1997 14:17:18 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id RAA09334 for ; Mon, 22 Sep 1997 17:17:08 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id RAA00241 for ; Mon, 22 Sep 1997 17:30:30 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id RAA02406 for freebsd-hackers@freefall.cdrom.com; Mon, 22 Sep 1997 17:22:28 -0400 (EDT) Date: Mon, 22 Sep 1997 17:22:28 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709222122.RAA02406@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org Subject: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - I have a machine that is my gateway to the outside world (using natd.) This machine contacts my ISP every now-and-then to grab news and mail. So, this machine (and all of the others on my network) have a /etc/resolv.conf for pointing to the ISP's nameserver. But - at any given time, the gateway machine isn't likely to be connected to the network... This is completely fine, until I try to rlogin to the gateway machine (ponds.dignus.com). The rlogin's have to timeout doing the normal rhosts verification... which can take a long time, since I'm not running a resolver (bind) at my end. Of course, I'm using an internal (10.0.0.xx) network... so the ISP shouldn't be able to resolve this anyway... Now - the typical answer is, of course, "You need to set your /etc/host.conf to use the /etc/hosts file first, then use bind. Well - I have that set up - my /etc/host.conf looks like: # $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $ # For our situation, use /etc/hosts first... hosts # Then, use the nameserver bind # If you have YP/NIS configured, uncomment the next line # nis My entries are present in my host file... What's strange is that things on the gateway machine seem to access the local network (presumably using /etc/hosts) just fine. It's only rlogin's to the gateway machine from the internal network that are causing the problem... Also, if I don't ifconfig the external slip connection, I don't have this timeout behaviour... I guess, what I'm hinting at here, is that /etc/host.conf doesn't seem to be working for the r-cmds... Has anyone seen this behaviour? Are the r-cmds using their own resolver? And thus "by-passing" /etc/host.conf? Is something else going on? - Thanks - - Dave Rivers - From owner-freebsd-hackers Mon Sep 22 14:40:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22996 for hackers-outgoing; Mon, 22 Sep 1997 14:40:57 -0700 (PDT) Received: from plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA22988 for ; Mon, 22 Sep 1997 14:40:53 -0700 (PDT) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by plaut.de (8.6.12/8.6.12) with ESMTP id XAA22378; Mon, 22 Sep 1997 23:40:42 +0200 Received: from localhost (root@localhost) by totum.plaut.de (8.8.7/8.7.3) with SMTP id XAA08444; Mon, 22 Sep 1997 23:40:43 +0200 (MET DST) Date: Mon, 22 Sep 1997 23:40:43 +0200 (MET DST) From: Michael Reifenberger To: Andrew Gordon cc: hackers@FreeBSD.ORG Subject: Re: lpr/lpd and HP networked printers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997, Andrew Gordon wrote: ... > HP prints a fairly useless 'banner' page after each job; since people Or telnet to the printer and disable that damn banner-page once and for all. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis From owner-freebsd-hackers Mon Sep 22 15:20:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25291 for hackers-outgoing; Mon, 22 Sep 1997 15:20:53 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA25284 for ; Mon, 22 Sep 1997 15:20:48 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14074; Tue, 23 Sep 1997 00:20:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA25520; Tue, 23 Sep 1997 00:05:54 +0200 (MET DST) Message-ID: <19970923000551.VJ48519@uriah.heep.sax.de> Date: Tue, 23 Sep 1997 00:05:51 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: dkelly@hiwaay.net Subject: Re: "Load Defaults" was my cure! (Was: Re: Do *you* have problems with floppies?) References: <19970916091455.RH14318@uriah.heep.sax.de> <199709220300.WAA02213@nospam.hiwaay.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709220300.WAA02213@nospam.hiwaay.net>; from dkelly@hiwaay.net on Sep 21, 1997 22:00:39 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As dkelly@hiwaay.net wrote: > This is really why I'm replying to this older thread: Selecting "Load > Defaults" in the BIOS setup cured my floppy problem. Tor Egge tracked it down to an apparently broken floppy chip (most likely, the chip doesn't report DMA overruns correctly), and submitted a workaround that enables the FIFO on chips where this seems to be applicable. This hides the error well enough, and is also a good explanation why other operating systems on the same hardware didn't experience problems. Try the most recent -current, and see how it comes out. If it doesn't break for anyone, this might be a 2.2.5 candidate as well. (I tried it on an actual NE765-compatible 40-pin chip, and it doesn't break there either.) Terry submitted me a larger patch that is supposed to classify a good deal of FDC chips by feature categories, but i have yet to find an hour silent enough to test this. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Sep 22 15:21:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25325 for hackers-outgoing; Mon, 22 Sep 1997 15:21:03 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA25301 for ; Mon, 22 Sep 1997 15:20:55 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14075; Tue, 23 Sep 1997 00:20:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA26533; Tue, 23 Sep 1997 00:08:22 +0200 (MET DST) Message-ID: <19970923000821.DS46585@uriah.heep.sax.de> Date: Tue, 23 Sep 1997 00:08:21 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: dleeds@dfacades.com Subject: Re: cons25 to solaris? References: <199709221117.LAA08383@kerouac.hepcat.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709221117.LAA08383@kerouac.hepcat.org>; from Daniel Leeds on Sep 22, 1997 11:17:45 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Daniel Leeds wrote: > is there a way to add the cons25 terminal to solaris terminfo? My SysV memories seem to remember a program named `captoinfo'. Did you try running this on a cons25 termcap entry? -- 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-hackers Mon Sep 22 15:21:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25366 for hackers-outgoing; Mon, 22 Sep 1997 15:21:14 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA25349 for ; Mon, 22 Sep 1997 15:21:10 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14078; Tue, 23 Sep 1997 00:21:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA27581; Tue, 23 Sep 1997 00:14:31 +0200 (MET DST) Message-ID: <19970923001428.WC40669@uriah.heep.sax.de> Date: Tue, 23 Sep 1997 00:14:28 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: arg@arg1.demon.co.uk (Andrew Gordon) Subject: Re: lpr/lpd and HP networked printers References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Andrew Gordon on Sep 22, 1997 20:35:24 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrew Gordon wrote: > This is easy enough to fix, though it is not obvious which is the > correct way. There are a number of possibilities: 6) Telnet to your JetDirect, and turn off banner pages. That's how i always did it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Sep 22 15:28:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25940 for hackers-outgoing; Mon, 22 Sep 1997 15:28:29 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA25928 for ; Mon, 22 Sep 1997 15:28:22 -0700 (PDT) Received: (from root@localhost) by bmccane.uit.net (8.8.7/8.8.5) id RAA09065; Mon, 22 Sep 1997 17:27:51 -0500 (CDT) Date: Mon, 22 Sep 1997 17:27:49 -0500 (CDT) From: Wm Brian McCane To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: ISDN Modems In-Reply-To: <19970920185623.YM44251@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, J Wunsch wrote: > As Wm Brian McCane wrote: > > > Only 7.5kB/sec? I am now very confused. I get 6kB/s throughput > > from my 33.6 most of the time. Of course I am usually transferring > > news/mail so they are highly compressible. Do any of the plug-in > > cards do LZ compression, or anything similar? > > You are comparing apples and oranges. A 33.6 kbps modem can at best > transfer 4.2 KB/s raw data (a little less due to the required protocol > overhead). The remainder is done by on-the-fly compression. Use the > data rate when getting a .tar.gz file as a base for your comparisions. > > ISDN itself doesn't provide for on-the-fly compression, so the raw > data rate is close to 8 KB/s. The 7.5 KB/s is the common data rate > for IP traffic. > > PPP provides for potential link-level compression. One of the options > is ``BSD compression'' which should be close to the typical modem > compression ratios. > > -- > 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. ;-) > I intentionally compared apples to oranges. I don't transfer very many compressed binary files, but I do transfer a LOT of UseNet news and e-mail. (Not the binary groups, so don't put uuencode in the conversation). I am targetting MY needs. I have decided on the Pipeline 50's partially because their documentation says that they will compress data received on the 10BaseT port at rates "up to" 512K/second 8-P. (Yeah, like I'll believe that when I see it 8). I have looked at the iijppp, and the "new" ppp changes to support BSD Comp in Kernel, it looks nice, but my ISP uses LPM3's and Windows NT, so I don't think it will help. brian +-------------------------------------+----------------------------------------+ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane he represents the last great schizm \ McCane Consulting among the gods. Evil though he obviously \ root@bmccane.uit.net is, he is a mighty figure, this father of \ http://bmccane.uit.net/ my spirit, and I respect him as the sons \ http://bmccane.uit.net/~pictures/ of old did the fathers of their bodies. \ http://bmccane.uit.net/~bmccane/ Roger Zelazny - "Lord of Light" \ http://bmccane.uit.net/~bbs/ +---------------------------------------------+--------------------------------+ From owner-freebsd-hackers Mon Sep 22 16:26:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29881 for hackers-outgoing; Mon, 22 Sep 1997 16:26:41 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29872; Mon, 22 Sep 1997 16:26:34 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id QAA01075; Mon, 22 Sep 1997 16:26:17 -0700 (PDT) Date: Mon, 22 Sep 1997 16:26:17 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Diskless Workstation -- Problems needing to be addressed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I myself, am sold on the idea of diskless freebsd workstations, for my applications they greatly reduce the amount of maintenance that needs to be done aon a machine plus when stupid people panic and fluip the power switch there aren't any problems with drives being spammed -- one thing I have learned is that 100 base T networking is something you will definetely want to have for this --- with it there is no real difference in feeling between a machine with a hard drive and one without, I was able to set up a pentium 100 and a couple of nexgens 110s as some very suitable freebsd fully featured workstations/X stations (32MB) for about $800 a piece, and also by burning some eproms I dont need a floppy either, hell the only moving parts in the whole machine is the power supply which could be eliminated by using a centralized dc 12/5 power supply plus probably some filter capacitors at the endpointd due to the distance. Anyway having three of these disklesss workstations and one master server I just wanted to make my environment available for testing related things related to this, I have written some scripts that after a make world on a master server automatically mirror over things like /lkm /bin , and a kernel to each machines deirectory. I think there should be an option for easily setting up diskless workstations in the installation, because there are a different set of things that need to be done on the master server, also since a root directory is not as critical (in terms of having all the binaries needed to repair the system on a diskless machine I think a significant amount of reorganizing could be done to the diskless workstation directory structure there are other problems too for instance I have yet to figure out why when I have the /usr partition mounted read only from the master server and I run finger on the diskless machines as a regular user I get a finger: permission denied message? Are there some restrictions on things like running suid binaries on mounted volumes because of the obvious security hole if a user mounts a suid binary that would allow him to gain root priveledges etc. From owner-freebsd-hackers Mon Sep 22 16:29:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00262 for hackers-outgoing; Mon, 22 Sep 1997 16:29:39 -0700 (PDT) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA00249 for ; Mon, 22 Sep 1997 16:29:32 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id AAA29081; Tue, 23 Sep 1997 00:29:21 +0100 (BST) Date: Tue, 23 Sep 1997 00:29:20 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Joerg Wunsch cc: hackers@FreeBSD.ORG, Troy Curtiss , Michael Reifenberger Subject: Re: lpr/lpd and HP networked printers In-Reply-To: <19970923001428.WC40669@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, J Wunsch [and others!] wrote: > As Andrew Gordon wrote: > > > This is easy enough to fix, though it is not obvious which is the > > correct way. There are a number of possibilities: > > 6) Telnet to your JetDirect, and turn off banner pages. That's > how i always did it. Well, I have now tried the three printers that I can access remotely, and none of them support this (they support the telnet prompt for configuration, but banners are not one of the available options; I tried typing the suggested "banner:0" in case it was an undocumented feature, but that gave me an error). These three machines are various different models of laserjet 4 (4M, 4M+ etc.), aged between 2 and 4 years old. Maybe there has been a firmware upgrade since; I certainly spent plenty of effort (including talking to HP support) trying to find a way to disable it at the time the first one was installed, but to no avail. Also, I have since spoken to someone with an Intel NetPort Express (an external ethernet interface for ordinary parallel/serial printers), and he has the exact same problem, again with no obvious means to turn off the banner in the configuration. In both that case and the HP, it responds correctly to the banner controls in the lpr protocol. So, I still think a change to lpr/lpd would be useful, though so far it looks like I am in a minority of 1.... From owner-freebsd-hackers Mon Sep 22 16:30:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00365 for hackers-outgoing; Mon, 22 Sep 1997 16:30:19 -0700 (PDT) Received: from coconut.itojun.org (root@coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA00345; Mon, 22 Sep 1997 16:30:08 -0700 (PDT) From: itojun@itojun.org Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.5/3.6Wbeta6) with ESMTP id IAA03298; Tue, 23 Sep 1997 08:29:47 +0900 (JST) To: Wolfram Schneider , abial@warman.org.pl cc: hackers@freebsd.org In-reply-to: wosch's message of Mon, 22 Sep 1997 16:14:39 MST. <199709222314.QAA12048@freefall.freebsd.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: cvs commit: src/contrib/nvi/catalog polish polish.base polish.check polish.owner Makefile src/usr.bin/vi Makefile Date: Tue, 23 Sep 1997 08:29:46 +0900 Message-ID: <3294.874970986@coconut.itojun.org> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >wosch 1997/09/22 16:14:38 PDT > Modified files: > contrib/nvi/catalog Makefile > usr.bin/vi Makefile > Added files: > contrib/nvi/catalog polish polish.base polish.check > polish.owner > Log: > Polish message catalogs for vi. have you submitted this to Keith Bostic? (bostic@bostic.com) he maintains nvi. itojun From owner-freebsd-hackers Mon Sep 22 17:10:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02619 for hackers-outgoing; Mon, 22 Sep 1997 17:10:10 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA02610; Mon, 22 Sep 1997 17:10:07 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA20140; Mon, 22 Sep 1997 16:26:33 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020138; Mon Sep 22 23:26:27 1997 Message-ID: <342706D7.794BDF32@whistle.com> Date: Mon, 22 Sep 1997 17:01:27 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Graham Wheeler CC: "Jonathan M. Bresler" , hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <199709221537.RAA09859@cdsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Graham Wheeler wrote: > > > > > Graham, > > have you been able to create a minimal program that tickles > > the bug? if i remember correctly, one suspicion is that > > the links that malloc uses to track memory allocations > > are being corrupted....creating a circular list. > > > > jmb > > Unfortunately not. At present most of our clients are still running the > firewall software on FreeBSD 2.1.0, and have no problem (with at least > one site of about 2000 users having run the gateway process for about > four months without a restart or reboot). We recently upgraded a couple > of sites to FreeBSD 2.2.2, mostly to allow Adaptec 2940 support. Of these > sites, most are either running proxies only or have fairly low traffic. > Only one site has been affected by the bug, with the main distinguishing > characteristic being a very heavy network load (there are approximately > 5000 users behind this firewall, with quite heavy WWW browser useage taking > place). > > As the loop can occur anywhere where there is a call to malloc, directly > or indirectly, we have not been able to isolate it at all. Most of the C++ > classes that are used have their own test programs to test them in isolation, > but no problems have been found with these. Also, many of the classes used > by the gateway program are used in other modules in the firewall; none of > these modules have shown any problems. One thing that can be said about the > gateway program is that it performs far more dynamic memory allocations and > frees than any other module in the firewall (every packet that passes through > the gateway, for starters). sounds like it might be a candidate for a buffer cache... i.e. keep 100 pre-allocated buffers or similar, so that malloc is not called nearly as much.. yeah I know it doesn't solve the problem, but.... > > -- > Dr Graham Wheeler E-mail: gram@cdsec.com > Citadel Data Security Phone: +27(21)23-6065/6/7 > Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 > Firewalls/Virtual Private Networks Fax: +27(21)24-3656 > Data Security Products WWW: http://www.cdsec.com/ From owner-freebsd-hackers Mon Sep 22 18:40:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06844 for hackers-outgoing; Mon, 22 Sep 1997 18:40:05 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06783 for ; Mon, 22 Sep 1997 18:40:00 -0700 (PDT) Received: from localhost (root@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id SAA01409; Mon, 22 Sep 1997 18:38:17 -0700 (PDT) Date: Mon, 22 Sep 1997 18:38:17 -0700 (PDT) From: 0000-Administrator To: dufault@hda.com cc: freebsd-hackers@freebsd.org Subject: Re: LABPC Driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997, 0000-Administrator wrote: > > What capacity are you using this board in, in particular is it possible > with the labpc to have it scan the 8 analog channels at a high freq (like > 1000hz) and interrupt after each scan then if you open a /dev/ad7 or what > not you will just get more or less continuos output so you can sit > blocked at a select() call with no timeout and basically get stuff run at > the freq of input (more or less) or are you still limited to the 100hz > scheduling clock (what if you are running under realtime priorities). > > HACKERS? ---------\ > | > \/ > > In particular what happens when you are stopped (such as at a select() > call) in a rtprioed process, when interrupts occur and I/O comes in that > would unblock you if you are the highest (actually lowest numbered) > rtprioed process do you pretty much immediately get unblocked and excuted > or do you have to wait until the next scheduling clock tick? > > > > From owner-freebsd-hackers Mon Sep 22 18:47:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07100 for hackers-outgoing; Mon, 22 Sep 1997 18:47:23 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA07093 for ; Mon, 22 Sep 1997 18:47:16 -0700 (PDT) Received: (qmail 4829 invoked by uid 1000); 23 Sep 1997 01:47:37 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-091897 [p0] on FreeBSD X-Priority: 1 (High) Priority: urgent Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Mon, 22 Sep 1997 18:47:37 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.ORG Subject: HDLC on FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Y'll, I need the following, urgently: A way of connecting a FreeBSD box to an HDLC line, running, 56Kbps-256Kbps. The faster, the better. What will be on the otehr side is a Cisco router. I have some ideas of my own but would like, very much to hear from thos who have done it already. I need to have 8-16 ports per system and have 3 ISA or 3 PCi slots available. ANY input will be appreciated! --- Sincerely Yours, (Sent on 22-Sep-97, 18:31:35 by XF-Mail) Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313 From owner-freebsd-hackers Mon Sep 22 18:49:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07253 for hackers-outgoing; Mon, 22 Sep 1997 18:49:29 -0700 (PDT) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA07240 for ; Mon, 22 Sep 1997 18:49:23 -0700 (PDT) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id SAA28071; Mon, 22 Sep 1997 18:47:51 -0700 (MST) From: Terry Lambert Message-Id: <199709230147.SAA28071@usr01.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: rivers@dignus.com (Thomas David Rivers) Date: Tue, 23 Sep 1997 01:47:50 +0000 (GMT) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199709222122.RAA02406@lakes.dignus.com> from "Thomas David Rivers" at Sep 22, 97 05:22:28 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I guess, what I'm hinting at here, is that /etc/host.conf doesn't > seem to be working for the r-cmds... > > Has anyone seen this behaviour? > > Are the r-cmds using their own resolver? And thus "by-passing" > /etc/host.conf? It's something to do with gethostbyaddr(). I reported exactly this problem about 3 weeks ago. You may notice it's the daemon. It might be something specific to the way ruserok() is coded. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Sep 22 19:10:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08150 for hackers-outgoing; Mon, 22 Sep 1997 19:10:37 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08143 for ; Mon, 22 Sep 1997 19:10:34 -0700 (PDT) Received: from nospam.hiwaay.net (tnt1-130.HiWAAY.net [208.147.147.130]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id VAA11465; Mon, 22 Sep 1997 21:10:21 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id UAA06031; Mon, 22 Sep 1997 20:31:19 -0500 (CDT) Message-Id: <199709230131.UAA06031@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrew Gordon Cc: hackers@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: lpr/lpd and HP networked printers In-reply-to: Message from Andrew Gordon of "Tue, 23 Sep 1997 00:29:20 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 20:31:19 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andrew Gordon writes: > > So, I still think a change to lpr/lpd would be useful, though so far > it looks like I am in a minority of 1.... I don't think the banner page you are seeing originated in your FreeBSD box, so there is no way lpr/lpd could be changed to delete it. You didn't say what printer name you were printing to on the HP. As I remember there are two names HP supports, "text" and "raw". Forgot which was considered default. But if you had an old Sun that was able to print without this banner page then maybe one of these devices doesn't include the banner? Another idea about the Sun was that it might not have been printing via lpd. HP has downloadable software for printing on JetDirect printers that provides GUI control and status of the printer. By that backdoor one might disable banner printing on a job by job basis. "Modern" Solaris is such a pain to set up standalone networked printers that HP's JetDirect software is a real blessing. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Mon Sep 22 19:26:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09004 for hackers-outgoing; Mon, 22 Sep 1997 19:26:38 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08989 for ; Mon, 22 Sep 1997 19:26:06 -0700 (PDT) Received: from lab321.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru (8.8.7/8.8.5) with ESMTP id JAA10873; Tue, 23 Sep 1997 09:26:31 +0700 (OSD) Message-ID: <342728AA.7F47DF0@lab321.ru> Date: Tue, 23 Sep 1997 09:25:46 +0700 From: Eugeny Kuzakov Organization: Powered by FreeBSD. X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970807-SNAP i386) MIME-Version: 1.0 To: Simon Shapiro CC: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: HDLC on FreeBSD References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > Hi Y'll, > > I need the following, urgently: > > A way of connecting a FreeBSD box to an HDLC line, running, 56Kbps-256Kbps. > The faster, the better. What will be on the otehr side is a Cisco router. > > I have some ideas of my own but would like, very much to hear from thos who > have done it already. > > I need to have 8-16 ports per system and have 3 ISA or 3 PCi slots > available. Ok. You need Cronyx Sigma board. Features: - master dma mode - 16650A - any port can setup as sync/async personally - onboard support ppp/hdlc - maximum rates: async - 115200, sync - 384000 - if you uses BSDI, you can setup load balance ONBOARD !!! - drivers FreeBSD,BSDI,Windows NT. Look at http://www.cronyx.ru, mailto://vak@cromyx.ru, Segrey Vakulenko. Eugeny. From owner-freebsd-hackers Mon Sep 22 19:43:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09913 for hackers-outgoing; Mon, 22 Sep 1997 19:43:08 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09908 for ; Mon, 22 Sep 1997 19:43:04 -0700 (PDT) Received: from localhost (root@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id SAA01388; Mon, 22 Sep 1997 18:31:38 -0700 (PDT) Date: Mon, 22 Sep 1997 18:31:38 -0700 (PDT) From: 0000-Administrator Reply-To: 0000-Administrator To: dufalt@hda.com cc: freebsd-hackers@freebsd.org Subject: LABPC Driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What capacity are you using this board in, in particular is it possible with the labpc to have it scan the 8 analog channels at a high freq (like 1000hz) and interrupt after each scan then if you open a /dev/ad7 or what not you will just get more or less continuos output so you can sit blocked at a select() call with no timeout and basically get stuff run at the freq of input (more or less) or are you still limited to the 100hz scheduling clock (what if you are running under realtime priorities). HACKERS? ---------\ | \/ In particular what happens when you are stopped (such as at a select() call) in a rtprioed process, when interrupts occur and I/O comes in that would unblock you if you are the highest (actually lowest numbered) rtprioed process do you pretty much immediately get unblocked and excuted or do you have to wait until the next scheduling clock tick? From owner-freebsd-hackers Mon Sep 22 19:57:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10544 for hackers-outgoing; Mon, 22 Sep 1997 19:57:04 -0700 (PDT) Received: from kerouac.hepcat.org (kerouac.hepcat.org [207.155.93.61]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10539 for ; Mon, 22 Sep 1997 19:56:58 -0700 (PDT) Received: (from cosmos@localhost) by kerouac.hepcat.org (8.8.5/8.8.5) id UAA09014; Mon, 22 Sep 1997 20:04:28 GMT Message-Id: <199709222004.UAA09014@kerouac.hepcat.org> Subject: Re: cons25 to solaris? In-Reply-To: <19970923000821.DS46585@uriah.heep.sax.de> from J Wunsch at "Sep 23, 97 00:08:21 am" To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 22 Sep 1997 20:04:27 +0000 (GMT) Cc: hackers@freebsd.org From: Daniel Leeds Reply-to: dleeds@dfacades.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Daniel Leeds wrote: > > > is there a way to add the cons25 terminal to solaris terminfo? > > My SysV memories seem to remember a program named `captoinfo'. Did > you try running this on a cons25 termcap entry? > this worked, or so it seems. here is the quick method of adding the freebsd cons25 termcap to solaris terminfo. 1) cut out the cons25 entries from /etc/termcap and save into file. 2) move file over to solaris machine 3) captoinfo cons25.file > cons25.src 4) tic cons25.src voila. cons25 is now a proper terminal under my solaris box, and editing, shell history, etc seem to function proper now! danke. From owner-freebsd-hackers Mon Sep 22 19:58:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10642 for hackers-outgoing; Mon, 22 Sep 1997 19:58:49 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10615 for ; Mon, 22 Sep 1997 19:58:17 -0700 (PDT) Received: from lab321.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru (8.8.7/8.8.5) with ESMTP id JAA13012; Tue, 23 Sep 1997 09:58:01 +0700 (OSD) Message-ID: <3427300C.7889A7A0@lab321.ru> Date: Tue, 23 Sep 1997 09:57:16 +0700 From: Eugeny Kuzakov Organization: Powered by FreeBSD. X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970807-SNAP i386) MIME-Version: 1.0 To: Simon Shapiro , FreeBSD-Hackers@FreeBSD.ORG Subject: Re: HDLC on FreeBSD References: <342728AA.7F47DF0@lab321.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Eugeny Kuzakov wrote: > > Simon Shapiro wrote: > ? > ? Hi Y'll, > ? > ? I need the following, urgently: > ? > ? A way of connecting a FreeBSD box to an HDLC line, running, 56Kbps-256Kbps. > ? The faster, the better. What will be on the otehr side is a Cisco router. > ? > ? I have some ideas of my own but would like, very much to hear from thos who > ? have done it already. > ? > ? I need to have 8-16 ports per system and have 3 ISA or 3 PCi slots > ? available. > Ok. > You need Cronyx Sigma board. > Features: > - master dma mode > - 16650A > - any port can setup as sync/async personally > - onboard support ppp/hdlc > - maximum rates: async - 115200, sync - 384000 > - if you uses BSDI, you can setup load balance ONBOARD !!! > - drivers FreeBSD,BSDI,Windows NT. > Look at http://www.cronyx.ru, mailto://vak@cromyx.ru, Segrey Vakulenko. ^^^^^^^^^ Sorry, .. mailto://vak@cronyx.ru Eugeny. From owner-freebsd-hackers Mon Sep 22 22:20:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18299 for hackers-outgoing; Mon, 22 Sep 1997 22:20:56 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA18292 for ; Mon, 22 Sep 1997 22:20:52 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA18153; Tue, 23 Sep 1997 07:20:44 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA20945; Tue, 23 Sep 1997 07:19:57 +0200 (MET DST) Message-ID: <19970923071956.SC32042@uriah.heep.sax.de> Date: Tue, 23 Sep 1997 07:19:56 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: arg@arg1.demon.co.uk (Andrew Gordon) Cc: hackers@FreeBSD.ORG Subject: Re: lpr/lpd and HP networked printers References: <19970923001428.WC40669@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Andrew Gordon on Sep 23, 1997 00:29:20 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrew Gordon wrote: > > 6) Telnet to your JetDirect, and turn off banner pages. That's > > how i always did it. > > Well, I have now tried the three printers that I can access remotely, > and none of them support this (they support the telnet prompt for > configuration, but banners are not one of the available options; I tried > typing the suggested "banner:0" in case it was an undocumented feature, > but that gave me an error). Upgrade the JetDirect's firmware then. Alas, this requires a Windows machine. (HP provides the `JetAdmin' software for Solaris and HP-UX, too, but not for any other Unix. Firmware upgrading is impossible without this crap, and last time i've tried it under Solaris, the program behaved like a typical Windows program: ``Firmware download failed'' was the only thing i could get out of this.) > In both that case and the > HP, it responds correctly to the banner controls in the lpr protocol. HP was never very good in understanding the lpd protocol. This is no big surprise, since the lpd protocol was only `documented' in the BSD source code. They've botched a number of things where they've transferred responsibility to the client where it's actually in the server. They can't print multiple copies of one file for a similar reason (lpr -# option). Until very recently, they couldn't even print multiple jobs in a single TCP connection -- but this only became apparent once you've turned off banners, since they otherwise closed the TCP link after each (sub)job. ;-) If you upgrade your firmware, you've got this bug fixed as well... -- 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-hackers Mon Sep 22 22:51:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19929 for hackers-outgoing; Mon, 22 Sep 1997 22:51:58 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA19917 for ; Mon, 22 Sep 1997 22:51:52 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA18272; Tue, 23 Sep 1997 07:51:45 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA24534; Tue, 23 Sep 1997 07:25:36 +0200 (MET DST) Message-ID: <19970923072533.UX58086@uriah.heep.sax.de> Date: Tue, 23 Sep 1997 07:25:33 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: arg@arg1.demon.co.uk (Andrew Gordon) Subject: Re: lpr/lpd and HP networked printers References: <199709230131.UAA06031@nospam.hiwaay.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709230131.UAA06031@nospam.hiwaay.net>; from dkelly@hiwaay.net on Sep 22, 1997 20:31:19 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As dkelly@hiwaay.net wrote: > You didn't say what printer name you were printing to on the HP. As I > remember there are two names HP supports, "text" and "raw". Forgot > which was considered default. But if you had an old Sun that was able > to print without this banner page then maybe one of these devices > doesn't include the banner? No, both print the d*mned banner page. But, some HP proprietary protocol on a weird port predates the use of lpd in JetDirects. I forgot the port number, i think the protocol itself was fairly simple (just open a TCP connection, and dump your data down to the printer). Maybe the Sun was using this method. -- 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-hackers Mon Sep 22 22:52:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA20000 for hackers-outgoing; Mon, 22 Sep 1997 22:52:10 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19995 for ; Mon, 22 Sep 1997 22:52:06 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA05902; Mon, 22 Sep 1997 22:54:08 -0700 (PDT) Message-Id: <199709230554.WAA05902@implode.root.com> To: "Jordan K. Hubbard" cc: Charles Owens , hackers list FreeBSD Subject: Re: LISA'97: how about a BOF session? In-reply-to: Your message of "Mon, 22 Sep 1997 10:53:54 PDT." <943.874950834@time.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Sep 1997 22:54:08 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I'm planning on attending LISA'97, (Systems and Network Admin conference, >> put on by USENIX). It's the last week of October and is being held in San >> Diego. Has a FreeBSD Birds-Of-a-Feather session been scheduled? Are >> enough FreeBSD users going to warrant one? > >If David Greenman follows up on his plan to attend, I'd say yes, >there will be a BOF. If he doesn't then would you like to schedule >one? :) > >> I see that Walnut Creek is amongst the vendors that will be in attendance. >> Who from the FreeBSD camp will at that booth waving the FreeBSD banner? > >I believe that David is the only person slated to attend. I've got a >trip to Japan coming up, followed immediately thereafter by Comdex, so >I'm trying to keep my own frequent flier miles to a minimum. :) I wanted to attend, but Len turned down my offer. Perhaps I should bring the issue up with Bob? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Sep 22 22:59:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA20286 for hackers-outgoing; Mon, 22 Sep 1997 22:59:54 -0700 (PDT) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA20280; Mon, 22 Sep 1997 22:59:47 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.7/8.8.5) with SMTP id IAA15018; Tue, 23 Sep 1997 08:01:22 +0200 (CEST) Date: Tue, 23 Sep 1997 08:01:22 +0200 (CEST) From: Andrzej Bialecki To: itojun@itojun.org cc: Wolfram Schneider , hackers@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/nvi/catalog polish polish.base polish.check polish.owner Makefile src/usr.bin/vi Makefile In-Reply-To: <3294.874970986@coconut.itojun.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997 itojun@itojun.org wrote: > > >wosch 1997/09/22 16:14:38 PDT > > Modified files: > > contrib/nvi/catalog Makefile > > usr.bin/vi Makefile > > Added files: > > contrib/nvi/catalog polish polish.base polish.check > > polish.owner > > Log: > > Polish message catalogs for vi. > > have you submitted this to Keith Bostic? (bostic@bostic.com) > he maintains nvi. > > itojun > Not yet.. Thanks for reminder! I'll do it. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-hackers Mon Sep 22 23:02:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20540 for hackers-outgoing; Mon, 22 Sep 1997 23:02:55 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA20535; Mon, 22 Sep 1997 23:02:48 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA18356; Tue, 23 Sep 1997 06:49:18 +0200 From: Luigi Rizzo Message-Id: <199709230449.GAA18356@labinfo.iet.unipi.it> Subject: Re: Diskless Workstation -- Problems needing to be addressed To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Tue, 23 Sep 1997 06:49:18 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 22, 97 04:25:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just curious, did you manage to boot from an eprom with 100Mbit cards ? Last time I tried this was only possible with 10Mbit cards, except the obvious option (one 10-mbit card with the boot rom, one 100-mbit which supports the real traffic). > easily setting up diskless workstations in the installation, because there > are a different set of things that need to be done on the master server, what I have is a script which clones the root partition by making a small set of changes and symlinks where needed. Cheers Luigi From owner-freebsd-hackers Mon Sep 22 23:23:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21844 for hackers-outgoing; Mon, 22 Sep 1997 23:23:53 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21810; Mon, 22 Sep 1997 23:23:30 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA01385; Mon, 22 Sep 1997 23:18:29 -0700 (PDT) Date: Mon, 22 Sep 1997 23:18:29 -0700 (PDT) From: "Jamil J. Weatherbee" To: Luigi Rizzo cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709230449.GAA18356@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk No only 10 megabit but I am going to get a linksys LNE100TX because I have a suspicion I may be able to hack it up and get it to work. There is some pci code in the netboot stuff (and also the boot rom sockets on other cards I've seen weren't the standard type I have the rom burner for) On Tue, 23 Sep 1997, Luigi Rizzo wrote: > Just curious, did you manage to boot from an eprom with 100Mbit > cards ? Last time I tried this was only possible with 10Mbit cards, > except the obvious option (one 10-mbit card with the boot rom, one > 100-mbit which supports the real traffic). > > > easily setting up diskless workstations in the installation, because there > > are a different set of things that need to be done on the master server, > > what I have is a script which clones the root partition by making a > small set of changes and symlinks where needed. > > Cheers > Luigi > From owner-freebsd-hackers Mon Sep 22 23:26:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22135 for hackers-outgoing; Mon, 22 Sep 1997 23:26:55 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22119 for ; Mon, 22 Sep 1997 23:26:40 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA01406 for ; Mon, 22 Sep 1997 23:26:03 -0700 (PDT) Date: Mon, 22 Sep 1997 23:26:03 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@freebsd.org Subject: Netscape Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone seen a native (or BSDOS) netscape 4 binary with 128 bit (US) encryption. There is a BSDOS binary for 3.0 but not for 4.0? What happened there. From owner-freebsd-hackers Tue Sep 23 00:48:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA26923 for hackers-outgoing; Tue, 23 Sep 1997 00:48:35 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA26430; Tue, 23 Sep 1997 00:41:58 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA18576; Tue, 23 Sep 1997 08:27:05 +0200 From: Luigi Rizzo Message-Id: <199709230627.IAA18576@labinfo.iet.unipi.it> Subject: Re: Diskless Workstation -- Problems needing to be addressed To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Tue, 23 Sep 1997 08:27:05 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 22, 97 11:18:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > No only 10 megabit but I am going to get a linksys LNE100TX because I have > a suspicion I may be able to hack it up and get it to work. There is some what is this suspicion based on, may I ask ? > pci code in the netboot stuff (and also the boot rom sockets on other I know, I wrote it :) but notices that different NE2000 clones behave differently with the PCI ROM (probably it is a property of the bios, not of the card). CHeers Luigi From owner-freebsd-hackers Tue Sep 23 01:27:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28596 for hackers-outgoing; Tue, 23 Sep 1997 01:27:59 -0700 (PDT) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA28590; Tue, 23 Sep 1997 01:27:53 -0700 (PDT) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id KAA22108; Tue, 23 Sep 1997 10:33:42 +0200 (SAT) Received: by citadel via recvmail id 22075; Tue Sep 23 10:33:02 1997 by gram.cdsec.com (8.8.5/8.8.5) id KAA11350; Tue, 23 Sep 1997 10:11:48 +0200 (SAT) From: Graham Wheeler Message-Id: <199709230811.KAA11350@cdsec.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Tue, 23 Sep 1997 10:11:47 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709221826.LAA06521@hub.freebsd.org> from "Jonathan M. Bresler" at Sep 22, 97 11:26:34 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Graham Wheeler wrote: > > > > Unfortunately not. At present most of our clients are still running the > > firewall software on FreeBSD 2.1.0, and have no problem (with at least > > one site of about 2000 users having run the gateway process for about > > four months without a restart or reboot). We recently upgraded a couple > > of sites to FreeBSD 2.2.2, mostly to allow Adaptec 2940 support. Of these > > good to hear that 2.1.0 is working well for you. ;) > what hardware are you using to support 2000 users? Pentium 166MHz, 64Mb RAM. Note that the users don't have accounts on the machine - the machine is just the firewall gateway for the users. > > Only one site has been affected by the bug, with the main distinguishing > > characteristic being a very heavy network load (there are approximately > > 5000 users behind this firewall, with quite heavy WWW browser useage taking > > place). > > does it crash them often, or only rarely...(rather inexact question) About every half hour. > > As the loop can occur anywhere where there is a call to malloc, directly > > or indirectly, we have not been able to isolate it at all. Most of the C++ > > classes that are used have their own test programs to test them in isolation, > did you replace new() in any of these classes? No. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ From owner-freebsd-hackers Tue Sep 23 02:39:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA01688 for hackers-outgoing; Tue, 23 Sep 1997 02:39:20 -0700 (PDT) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA01681 for ; Tue, 23 Sep 1997 02:39:16 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.7/8.8.5) with SMTP id LAA22200 for ; Tue, 23 Sep 1997 11:40:56 +0200 (CEST) Date: Tue, 23 Sep 1997 11:40:56 +0200 (CEST) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: libc, scanf and quads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! I'm developing certain application which should run either on FreeBSD or SunOS. I'm getting a bit tired of continuous editing in order to make the conversion strings right on both platforms. The problem is that we have the "%qu" whereas SunOS has "%llu". Is it possible/desirable to implement this second form in our libc? Or should I look for another solution? OTOH, I may be missing something (as often is the case... :-) Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-hackers Tue Sep 23 02:42:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA01857 for hackers-outgoing; Tue, 23 Sep 1997 02:42:24 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA01852 for ; Tue, 23 Sep 1997 02:42:21 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA08452 for ; Tue, 23 Sep 1997 02:44:47 -0700 (PDT) Message-Id: <199709230944.CAA08452@implode.root.com> To: hackers list FreeBSD Subject: Re: LISA'97: how about a BOF session? In-reply-to: Your message of "Mon, 22 Sep 1997 22:54:08 PDT." <199709230554.WAA05902@implode.root.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 23 Sep 1997 02:44:47 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>I believe that David is the only person slated to attend. I've got a >>trip to Japan coming up, followed immediately thereafter by Comdex, so >>I'm trying to keep my own frequent flier miles to a minimum. :) > > I wanted to attend, but Len turned down my offer. Perhaps I should bring >the issue up with Bob? Oops, I didn't intend for that to go out to the list. Anyway, if there is a FreeBSD BoF, I'm interested in any opinions on what you'd like to hear about at it (FreeBSD, of course, but specifics?). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Sep 23 03:22:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA03016 for hackers-outgoing; Tue, 23 Sep 1997 03:22:37 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA03009 for ; Tue, 23 Sep 1997 03:22:33 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id GAA10439; Tue, 23 Sep 1997 06:22:29 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id GAA09263; Tue, 23 Sep 1997 06:30:06 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id GAA03801; Tue, 23 Sep 1997 06:21:46 -0400 (EDT) Date: Tue, 23 Sep 1997 06:21:46 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709231021.GAA03801@lakes.dignus.com> To: rivers@dignus.com, tlambert@primenet.com Subject: Re: r-cmds and DNS and /etc/host.conf Cc: freebsd-hackers@freefall.freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I guess, what I'm hinting at here, is that /etc/host.conf doesn't > > seem to be working for the r-cmds... > > > > Has anyone seen this behaviour? > > > > Are the r-cmds using their own resolver? And thus "by-passing" > > /etc/host.conf? > > It's something to do with gethostbyaddr(). I reported exactly this > problem about 3 weeks ago. > > You may notice it's the daemon. It might be something specific to the > way ruserok() is coded. 8-(. > My guess as well (particularly the ruserok() part...) I had discussed this in the 2.2.1 timeframe; but it wasn't bothering me as much then. Now that I'm "better connected" - it occurs much more frequently... so, I was bothered enough to mention it again. - Dave R. - From owner-freebsd-hackers Tue Sep 23 03:22:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA03032 for hackers-outgoing; Tue, 23 Sep 1997 03:22:41 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA03015 for ; Tue, 23 Sep 1997 03:22:36 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id GAA10443; Tue, 23 Sep 1997 06:22:32 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id GAA09331; Tue, 23 Sep 1997 06:33:37 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id GAA03822; Tue, 23 Sep 1997 06:25:16 -0400 (EDT) Date: Tue, 23 Sep 1997 06:25:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709231025.GAA03822@lakes.dignus.com> To: rivers@dignus.com, sef@Kithrup.COM Subject: Re: r-cmds and DNS and /etc/host.conf Cc: freebsd-hackers@freefall.FreeBSD.org, tlambert@primenet.com Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In article <199709222122.RAA02406.kithrup.freebsd.hackers@lakes.dignus.com> you write: > > What's strange is that things on the gateway machine seem to access > >the local network (presumably using /etc/hosts) just fine. It's > >only rlogin's to the gateway machine from the internal network > >that are causing the problem... > > Hm. Both you and Terry report essentially the same thing, which I haven't > been able to reproduce. > > But I did not set my machine up to be a gateway -- yet both you and Terry > have. > > If you do > > netstat -f inet -n > > on the gateway, when it's not connected, what does it look like? In > particular, does it have two or more entries towards the end that are > listening for '*.*'? > > I can't think why it would be unique to a gateway, but... > > Sean. > I'm experiencing the problem now, here's the info (this is all done on the 'gateway' machine) The result of netstat -f inet -n: [ponds.dignus.com]$ netstat -f inet -n Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 10.0.0.1.23 10.0.0.3.3358 ESTABLISHED tcp 0 0 10.0.0.1.513 10.0.0.3.977 ESTABLISHED tcp 0 0 166.82.177.48.1200 166.82.1.5.25 SYN_SENT udp 0 0 10.0.0.1.1027 10.0.0.3.2049 udp 0 0 10.0.0.1.1026 10.0.0.3.2049 udp 0 0 10.0.0.1.1025 10.0.0.3.2049 udp 0 0 10.0.0.1.1024 10.0.0.3.2049 My /etc/resolv.conf looks like: domain vnet.net nameserver 166.82.1.3 nameserver 166.82.1.8 And, my /etc/host.conf looks like: # $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $ # For our situation, use /etc/hosts first... hosts # Then, use the nameserver bind # If you have YP/NIS configured, uncomment the next line # nis Just for completeness, here's the result of ifconfig -a: ed0: flags=8843 mtu 1500 inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 ether 66:66:77:00:0b:31 lp0: flags=8810 mtu 1500 tun0: flags=8010 mtu 1500 sl0: flags=9010 mtu 552 inet 166.82.177.48 --> 166.82.100.202 netmask 0xffffff00 sl1: flags=c010 mtu 552 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 - Dave Rivers - From owner-freebsd-hackers Tue Sep 23 04:47:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06111 for hackers-outgoing; Tue, 23 Sep 1997 04:47:05 -0700 (PDT) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06095 for ; Tue, 23 Sep 1997 04:46:58 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id MAA00361; Tue, 23 Sep 1997 12:46:14 +0100 (BST) Date: Tue, 23 Sep 1997 12:46:13 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: lpr/lpd and HP networked printers In-Reply-To: <19970923072533.UX58086@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, J Wunsch wrote: > As dkelly@hiwaay.net wrote: > > You didn't say what printer name you were printing to on the HP. As I > > remember there are two names HP supports, "text" and "raw". Forgot > > which was considered default. But if you had an old Sun that was able > > to print without this banner page then maybe one of these devices > > doesn't include the banner? > > No, both print the d*mned banner page. > > But, some HP proprietary protocol on a weird port predates the use of > lpd in JetDirects. I forgot the port number, i think the protocol > itself was fairly simple (just open a TCP connection, and dump your > data down to the printer). Maybe the Sun was using this method. No, it was using lpr (and it wasn't a Sun, it was an Acorn RiscIX machine!). Maybe I didn't make this clear: having looked at the protocol, I find I can suppress the banner page when printing from a FreeBSD machine too, so long as I use "lpr -h". The printer is obeying the "L" command code in the print job control file (both the HP and Intel devices do so). The problem is that with hundreds of users, printing via many different methods (manual lpr, from netscape, via Samba, via PC-NFS etc.) getting the "-h" into all the applicable config files/user's brains is impractical. If lpd is printing locally to a printer, it observes the "sh" capability and overrides the "L" command. However, if it is printing to a remote printer, it just transfers the control file unchanged and "sh" has no affect whatever. From owner-freebsd-hackers Tue Sep 23 05:25:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA07869 for hackers-outgoing; Tue, 23 Sep 1997 05:25:31 -0700 (PDT) Received: from spoon.beta.com (root@spoon.beta.com [199.165.180.33] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA07862 for ; Tue, 23 Sep 1997 05:25:25 -0700 (PDT) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.5/8.8.5) with ESMTP id IAA14497; Tue, 23 Sep 1997 08:12:12 -0400 (EDT) Message-Id: <199709231212.IAA14497@spoon.beta.com> To: jacques@wired.ctech.ac.za cc: hackers@freebsd.org Subject: RE: Quota Date: Tue, 23 Sep 1997 08:12:11 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk First, make sure you have quotas on the system that you want. Its a kernel config option. Next, kick all the users off the system. I've had problems with writes to supposedly quota'ed disks during this point, and haven't pinned them down yet. I've blown away a couple of drives at this step. Add the userquota flag to the /etc/fstab file, and create the quota.user file in the root of the parition where you want quotas. Run quotacheck. Then, reboot. Run edquota on one of the users, and set "defaults". Then, use can use -p with edquota to use them as the default. For instance, if I set up user foo's quotas, I can say: edquota -p foo bar and it will pull up bar's quota list, using foo's defaults. -Brian From owner-freebsd-hackers Tue Sep 23 05:49:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA08978 for hackers-outgoing; Tue, 23 Sep 1997 05:49:39 -0700 (PDT) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA08972 for ; Tue, 23 Sep 1997 05:49:36 -0700 (PDT) Message-Id: <199709231241.IAA08760@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Tue, 23 Sep 1997 08:51:52 -0400 (EDT) From: Jamie Bowden To: Andrew Gordon cc: Joerg Wunsch , hackers@freebsd.org, Troy Curtiss , Michael Reifenberger Subject: Re: lpr/lpd and HP networked printers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes you need a firmware upgrade. I have a 4mv here that I had to upgrade to turn off the banners. On Tue, 23 Sep 1997, Andrew Gordon wrote: > On Tue, 23 Sep 1997, J Wunsch [and others!] wrote: > > As Andrew Gordon wrote: > > > > > This is easy enough to fix, though it is not obvious which is the > > > correct way. There are a number of possibilities: > > > > 6) Telnet to your JetDirect, and turn off banner pages. That's > > how i always did it. > > Well, I have now tried the three printers that I can access remotely, > and none of them support this (they support the telnet prompt for > configuration, but banners are not one of the available options; I tried > typing the suggested "banner:0" in case it was an undocumented feature, > but that gave me an error). These three machines are various different > models of laserjet 4 (4M, 4M+ etc.), aged between 2 and 4 years old. > Maybe there has been a firmware upgrade since; I certainly spent plenty > of effort (including talking to HP support) trying to find a way to > disable it at the time the first one was installed, but to no avail. > > Also, I have since spoken to someone with an Intel NetPort Express > (an external ethernet interface for ordinary parallel/serial printers), > and he has the exact same problem, again with no obvious means to > turn off the banner in the configuration. In both that case and the > HP, it responds correctly to the banner controls in the lpr protocol. > > So, I still think a change to lpr/lpd would be useful, though so far > it looks like I am in a minority of 1.... > Jamie Bowden System Administrator, iTRiBE.net Abusenet: The Misinformation Superhighway From owner-freebsd-hackers Tue Sep 23 05:59:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA09451 for hackers-outgoing; Tue, 23 Sep 1997 05:59:36 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA09432; Tue, 23 Sep 1997 05:59:29 -0700 (PDT) Received: from panke.panke.de (anonymous214.ppp.cs.tu-berlin.de [130.149.17.214]) by mail.cs.tu-berlin.de (8.8.6/8.8.6) with ESMTP id OAA14856; Tue, 23 Sep 1997 14:50:38 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id NAA00518; Tue, 23 Sep 1997 13:18:30 +0200 (MET DST) To: itojun@itojun.org Cc: Wolfram Schneider , abial@warman.org.pl, hackers@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/nvi/catalog polish polish.base polish.check polish.owner Makefile src/usr.bin/vi Makefile References: <3294.874970986@coconut.itojun.org> From: Wolfram Schneider Date: 23 Sep 1997 13:18:28 +0200 In-Reply-To: itojun@itojun.org's message of Tue, 23 Sep 1997 08:29:46 +0900 Message-ID: Lines: 18 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk itojun@itojun.org writes: > >wosch 1997/09/22 16:14:38 PDT > > Modified files: > > contrib/nvi/catalog Makefile > > usr.bin/vi Makefile > > Added files: > > contrib/nvi/catalog polish polish.base polish.check > > polish.owner > > Log: > > Polish message catalogs for vi. > > have you submitted this to Keith Bostic? (bostic@bostic.com) > he maintains nvi. I forwared the commit mail to Keith. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Tue Sep 23 06:20:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10430 for hackers-outgoing; Tue, 23 Sep 1997 06:20:15 -0700 (PDT) Received: from p60.global2000.net (315-dialup-11.global2000.net [208.133.142.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10424 for ; Tue, 23 Sep 1997 06:20:09 -0700 (PDT) Received: (from eagriff@localhost) by p60.global2000.net (8.8.7/8.8.7) id QAA01002 for hackers@freebsd.org; Sun, 21 Sep 1997 16:27:20 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 21 Sep 1997 16:08:25 -0400 (EDT) Organization: Griff Enterprises From: "Eric A. Griff" To: hackers@freebsd.org Subject: sendmail configuration - living w/spam :( Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Will this work with the changes to the FreeBSD list filtering? divert(-1) # # eagriff.mc -- main goal is to have all message headers correct and # resolvable. In hopes that mail go's through, in a world where so # dammed much work has to go into filtering it due to abusers.. # THAT'S IT! Abusers! M$ and Spammers.. All to put food on their # own tables, not thinking of the most important people in the # the formula... The customer.. Aren't they supposed to be # happy too? # # Since I connect only Tuesday, about 8 hrs, warns after the 1st & 2nd weeks # and returns into the third week, a couple of days after the second warning. divert(0)dnl define(`confTO_QUEUERETURN',`18d')dnl define(`confTO_QUEUEWARN',`8d')dnl VERSIONID(`$Id: eagriff.mc,v 1.3 1997/09/21 20:07:49 eagriff Exp $')dnl OSTYPE(bsd4.4)dnl divert(-1) # Domain is global2000.net, mail is actually handled by # mail{,1}.global2000.net . Since the connection is dynamic, and to # avoid a script that changes the hostname at connection time, a # nonexistant hostname of p60 is used.. divert(0)dnl MASQUERADE_AS(global2000.net)dnl FEATURE(allmasquerade)dnl FEATURE(masquerade_envelope)dnl FEATURE(nouucp)dnl MAILER(local)dnl MAILER(smtp)dnl Any thing I forgot? Any suggested improvements? Thanks in advance -------- Eric A. Griff RD#1 Box 372 Oneida, NY 13421 USA -- Home phone- (315) 495-2385 -- http://members.global2000.net/~eagriff For a solid OS that makes sense, see http://www.freebsd.org From owner-freebsd-hackers Tue Sep 23 06:25:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10674 for hackers-outgoing; Tue, 23 Sep 1997 06:25:42 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10655 for ; Tue, 23 Sep 1997 06:25:35 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id PAA15850 for ; Tue, 23 Sep 1997 15:24:53 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id PAA01519 for freebsd-hackers@freefall.cdrom.com; Tue, 23 Sep 1997 15:31:22 +0200 (MEST) Date: Tue, 23 Sep 1997 15:31:22 +0200 (MEST) From: Christoph Kukulies Message-Id: <199709231331.PAA01519@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: strangeness with acroread and linux emu Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk With some March 97 -current and linux emu I'm having problems. I downloaded a large .PDF file. I have two other .pdf files in my home dir. I started acroread and want to open a file. The file selector box pops up with all fields empty. No Selection, no filter, no files, nor dirs. When I then go into another xterm and do an ls *.PDF the process hangs. Logging in over the network and doing an ls (only) also hangs the process. Anyone seen this problem? I think it could have to do something with linux emu in that it doesn't release the file/directory or what. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Tue Sep 23 10:21:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA22220 for hackers-outgoing; Tue, 23 Sep 1997 10:21:24 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA22209 for ; Tue, 23 Sep 1997 10:21:17 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA25582; Tue, 23 Sep 1997 19:20:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id TAA01757; Tue, 23 Sep 1997 19:04:12 +0200 (MET DST) Message-ID: <19970923190412.GM59568@uriah.heep.sax.de> Date: Tue, 23 Sep 1997 19:04:12 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: arg@arg1.demon.co.uk (Andrew Gordon) Subject: Re: lpr/lpd and HP networked printers References: <19970923072533.UX58086@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Andrew Gordon on Sep 23, 1997 12:46:13 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrew Gordon wrote: > If lpd is printing locally to a printer, it observes the "sh" capability > and overrides the "L" command. However, if it is printing to a remote > printer, it just transfers the control file unchanged and "sh" has > no affect whatever. Sure, lpd is not supposed to forward the sh capability across the net. (Actually, it doesn't forward many things.) Get a firmware upgrade, and you've got rid of them once and for all. -- 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-hackers Tue Sep 23 10:38:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23119 for hackers-outgoing; Tue, 23 Sep 1997 10:38:39 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23111 for ; Tue, 23 Sep 1997 10:38:35 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id NAA00286 for ; Tue, 23 Sep 1997 13:43:54 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Tue, 23 Sep 1997 13:43:53 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: quickcam? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i'm a little fuzzy on how to configure my kernel to use a quickcam, i know it's very straight forward in the LINT file, however i would like to be able to configure my kernel to use ANY LPT port instead of hardwiring it to LPT1 LPT0 or whatever. do i need to include multiple qcam drivers, each set to a different LPT? or can someone show me what line i would have to put in my kernel config file to allow the visual kernel boot editor to select which LPT port to attach to? thank you, ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" From owner-freebsd-hackers Tue Sep 23 11:21:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25382 for hackers-outgoing; Tue, 23 Sep 1997 11:21:42 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25376 for ; Tue, 23 Sep 1997 11:21:36 -0700 (PDT) Received: from argus.tfs.net (pm3-p37.tfs.net [206.154.183.229]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id MAA06209 for ; Tue, 23 Sep 1997 12:20:07 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id NAA01912 for freebsd-hackers@freebsd.org; Tue, 23 Sep 1997 13:21:25 -0500 (CDT) From: Jim Bryant Message-Id: <199709231821.NAA01912@argus.tfs.net> Subject: vt420 termcap needed (fwd) To: freebsd-hackers@freebsd.org Date: Tue, 23 Sep 1997 13:21:24 -0500 (CDT) Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk does anyone have a termcap entry for the vt420? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Tue Sep 23 11:27:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25656 for hackers-outgoing; Tue, 23 Sep 1997 11:27:54 -0700 (PDT) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25649 for ; Tue, 23 Sep 1997 11:27:51 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id LAA32342; Tue, 23 Sep 1997 11:35:31 -0700 Date: Tue, 23 Sep 1997 11:35:30 -0700 (PDT) From: Alex Belits To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: quickcam? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, Alfred Perlstein wrote: > i'm a little fuzzy on how to configure my kernel to use a quickcam, i know > it's very straight forward in the LINT file, however i would like to be > able to configure my kernel to use ANY LPT port instead of hardwiring it > to LPT1 LPT0 or whatever. > > do i need to include multiple qcam drivers, each set to a different LPT? > or can someone show me what line i would have to put in my kernel config > file to allow the visual kernel boot editor to select which LPT port to > attach to? I don't use quickcam kernel driver -- camera has braindead polling-only interface, and userland programs handle this device better. My program is at phobos.illtel.denver.co.us /pub/qcread, and I currently use it to take 1 fps "video" from color quickcam. -- Alex From owner-freebsd-hackers Tue Sep 23 11:44:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26718 for hackers-outgoing; Tue, 23 Sep 1997 11:44:45 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA26705 for ; Tue, 23 Sep 1997 11:44:31 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id OAA00357; Tue, 23 Sep 1997 14:47:41 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Tue, 23 Sep 1997 14:47:41 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Alex Belits cc: hackers@FreeBSD.ORG Subject: Re: quickcam? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I don't use quickcam kernel driver -- camera has braindead > polling-only interface, and userland programs handle this device > better. My program is at phobos.illtel.denver.co.us /pub/qcread, and I > currently use it to take 1 fps "video" from color quickcam. hmmm, how many input formats does it support and at what speeds? From owner-freebsd-hackers Tue Sep 23 12:43:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA29950 for hackers-outgoing; Tue, 23 Sep 1997 12:43:25 -0700 (PDT) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA29943 for ; Tue, 23 Sep 1997 12:43:20 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id MAA32678; Tue, 23 Sep 1997 12:51:30 -0700 Date: Tue, 23 Sep 1997 12:51:29 -0700 (PDT) From: Alex Belits To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: quickcam? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, Alfred Perlstein wrote: > > currently use it to take 1 fps "video" from color quickcam. > > hmmm, how many input formats does it support and at what speeds? color quickcam "millions of colors" (24bpp) mode, b&w quickcam 4bpp and 6bpp with unidirectional or bidirectional parallel port, reduced image size, 1/2 and 1/4 resolutions are supported in all modes. Color quickcam "billions of colors" (pseudo-double resolution) mode isn't supported (working on it), "thousands of colors" compressed mode isn't supported (Connectix doesn't provide documentation or libraries) and bidirectional ports, configured to pretend to be unidirectional confuse the autodetection. Frame rate is 0.8-1 fps in color mode 320x240 or 3-4 fps in 6bpp b&w mode, it's hardware limitation of the camera intrface. Long exposure values cause frame rate to decrease further. Program takes a lot of processor time while grabbing the image, so lower frame rates may be more reasonable. -- Alex From owner-freebsd-hackers Tue Sep 23 12:48:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA00397 for hackers-outgoing; Tue, 23 Sep 1997 12:48:32 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00385; Tue, 23 Sep 1997 12:48:26 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id MAA00183; Tue, 23 Sep 1997 12:48:00 -0700 (PDT) Date: Tue, 23 Sep 1997 12:48:00 -0700 (PDT) From: "Jamil J. Weatherbee" To: Luigi Rizzo cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709230627.IAA18576@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Last time I called Linksys they were reluctantly willing to give me some unusual info about the NE2000 cards we have, and possibly I could buy a boot rom off them and take a look at it :>) On Tue, 23 Sep 1997, Luigi Rizzo wrote: > > No only 10 megabit but I am going to get a linksys LNE100TX because I have > > a suspicion I may be able to hack it up and get it to work. There is some > > what is this suspicion based on, may I ask ? > > > pci code in the netboot stuff (and also the boot rom sockets on other > > I know, I wrote it :) but notices that different NE2000 clones behave > differently with the PCI ROM (probably it is a property of the bios, > not of the card). > > CHeers > Luigi > From owner-freebsd-hackers Tue Sep 23 12:53:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA00758 for hackers-outgoing; Tue, 23 Sep 1997 12:53:44 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00744 for ; Tue, 23 Sep 1997 12:53:34 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id MAA00190; Tue, 23 Sep 1997 12:52:23 -0700 (PDT) Date: Tue, 23 Sep 1997 12:52:23 -0700 (PDT) From: "Jamil J. Weatherbee" To: Wm Brian McCane cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: ISDN Modems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I can verify that the Pipelines do have this ability however make sure that the other end is using ascend hardware -- otherwise things like STAC compression etc. won't work. > I intentionally compared apples to oranges. I don't transfer very many > compressed binary files, but I do transfer a LOT of UseNet news and > e-mail. (Not the binary groups, so don't put uuencode in the > conversation). I am targetting MY needs. I have decided on the Pipeline > 50's partially because their documentation says that they will compress > data received on the 10BaseT port at rates "up to" 512K/second 8-P. > (Yeah, like I'll believe that when I see it 8). I have looked at the > iijppp, and the "new" ppp changes to support BSD Comp in Kernel, it looks > nice, but my ISP uses LPM3's and Windows NT, so I don't think it will help. > > brian > > +-------------------------------------+----------------------------------------+ > He rides a cycle of mighty days, and \ Wm Brian and Lori McCane > he represents the last great schizm \ McCane Consulting > among the gods. Evil though he obviously \ root@bmccane.uit.net > is, he is a mighty figure, this father of \ http://bmccane.uit.net/ > my spirit, and I respect him as the sons \ http://bmccane.uit.net/~pictures/ > of old did the fathers of their bodies. \ http://bmccane.uit.net/~bmccane/ > Roger Zelazny - "Lord of Light" \ http://bmccane.uit.net/~bbs/ > +---------------------------------------------+--------------------------------+ > > From owner-freebsd-hackers Tue Sep 23 13:21:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA02731 for hackers-outgoing; Tue, 23 Sep 1997 13:21:42 -0700 (PDT) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA02717 for ; Tue, 23 Sep 1997 13:21:15 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.7/8.8.7) id VAA01098; Tue, 23 Sep 1997 21:20:06 +0100 (BST) Message-ID: <19970923212006.58866@pavilion.net> Date: Tue, 23 Sep 1997 21:20:06 +0100 From: Josef Karthauser To: dkelly@hiwaay.net Cc: Andrew Gordon , hackers@FreeBSD.ORG Subject: Re: lpr/lpd and HP networked printers References: <199709230131.UAA06031@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199709230131.UAA06031@nospam.hiwaay.net>; from dkelly@hiwaay.net on Mon, Sep 22, 1997 at 08:31:19PM -0500 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 22, 1997 at 08:31:19PM -0500, dkelly@hiwaay.net wrote: > Andrew Gordon writes: > > > Another idea about the Sun was that it might not have been printing via > lpd. HP has downloadable software for printing on JetDirect printers > that provides GUI control and status of the printer. By that backdoor > one might disable banner printing on a job by job basis. > > "Modern" Solaris is such a pain to set up standalone networked printers > that HP's JetDirect software is a real blessing. > Talking of HP laserjets... has anyone had any success in configuring a printcap to enable paper tray selection? Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Tue Sep 23 15:19:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA08893 for hackers-outgoing; Tue, 23 Sep 1997 15:19:17 -0700 (PDT) Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [207.155.21.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA08872; Tue, 23 Sep 1997 15:19:12 -0700 (PDT) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.5/8.8.5) with ESMTP id PAA18505; Tue, 23 Sep 1997 15:18:16 -0700 (PDT) Message-Id: <199709232218.PAA18505@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.0delta 6/3/97 To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , Graham Wheeler , hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Sep 1997 15:18:16 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K Hubbard writes: >> This would indicate a bug of the class where memory is written to >> after being free()'ed, a kind of bug which phkmalloc makes no >> attempt to catch. > Man, I sure wish there was a copy of purify available for FreeBSD. > It's great at catching stuff like this! :( So was "leak", which was a DBM style wrapper to malloc/free. It would keep track of what you'd free'd and malloc'd and warn you when you were screwing up. Leak was public domain, but I have no idea where to get it. I have a hacked copy if anyone wants want. ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet Enjoyment is not a goal, it is a feeling that accompanies important ongoing activity From owner-freebsd-hackers Tue Sep 23 15:56:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA11024 for hackers-outgoing; Tue, 23 Sep 1997 15:56:10 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA10979 for ; Tue, 23 Sep 1997 15:55:54 -0700 (PDT) Received: (qmail 2128 invoked by uid 1000); 23 Sep 1997 22:56:16 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-091897 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Tue, 23 Sep 1997 15:56:16 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: DPT Firmware Problem Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Again, apologies for the cross posting. We have discovered a serious bug in the DPT firmware, Version 7L0. It manifests itself in the following manner (at least): * On Single Ended controllers; The ``Shelf Good'' signal reaches the DPT from the disk bay, but the HBA equivalent (HBA Good) does not reach the disk bay. As a result, the fault light remains on, and the disk cassettes will erratically display the fault light. * On differential controllers connected via Diff-SE adaptor; A whole bus will seem to have disappeared. If you struggle with the cables, you MAY see it for a while, but it will not survive a re-boot. Solution: Roll back to (ar stay at) the 7H firmware. I have posted 7H3 firmware in ftp://sendero-ppp.i-connect.net/crash/476d07h3.fwi There are no restrictions on downloading it. We know of this problem with several StorageWorks disk bays, ours included. We have not tested it with other disk bays, and drives which are directly connected are NOT effected. We will post a new firmware once we get it from DPT and veify proper operation. Hope this helps. --- Sincerely Yours, (Sent on 23-Sep-97, 15:12:42 by XF-Mail) Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313 From owner-freebsd-hackers Tue Sep 23 17:04:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14906 for hackers-outgoing; Tue, 23 Sep 1997 17:04:27 -0700 (PDT) Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14897 for ; Tue, 23 Sep 1997 17:04:21 -0700 (PDT) Received: from caught.inna.net (tom@caught.inna.net [206.151.66.7]) by tyger.inna.net (8.8.5/8.7.3) with SMTP id UAA28125; Tue, 23 Sep 1997 20:04:22 -0400 (EDT) Date: Tue, 23 Sep 1997 20:04:16 -0400 (EDT) From: Thomas Arnold To: David Greenman cc: hackers list FreeBSD Subject: Re: LISA'97: how about a BOF session? In-Reply-To: <199709230944.CAA08452@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, David Greenman wrote: > >>I believe that David is the only person slated to attend. I've got a > >>trip to Japan coming up, followed immediately thereafter by Comdex, so > >>I'm trying to keep my own frequent flier miles to a minimum. :) > > > > I wanted to attend, but Len turned down my offer. Perhaps I should bring > >the issue up with Bob? > > Oops, I didn't intend for that to go out to the list. > Anyway, if there is a FreeBSD BoF, I'm interested in any opinions on > what you'd like to hear about at it (FreeBSD, of course, but specifics?). Dont worry, none of us saw it. ------------------------------------------------------------------------ - Tom Arnold - And Lycius' arms were empty of delight, - - SysAdmin - As were his limbs of life, from that same night. - - TBI, Ltd - On the high couch he lay!--his friends came round-- -------------------- Supported him--no pulse, or breath they found, - - Keats, Lamia II : And, in its marriage robe, the heavy body wound. - From owner-freebsd-hackers Tue Sep 23 17:05:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA15030 for hackers-outgoing; Tue, 23 Sep 1997 17:05:52 -0700 (PDT) Received: from monk.via.net (monk.via.net [140.174.204.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA15024 for ; Tue, 23 Sep 1997 17:05:47 -0700 (PDT) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id QAA14397 for hackers@freebsd.org; Tue, 23 Sep 1997 16:55:47 -0700 Date: Tue, 23 Sep 1997 16:55:47 -0700 From: Joe McGuckin Message-Id: <199709232355.QAA14397@monk.via.net> To: hackers@freebsd.org Subject: ns /kernel: rtfree X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What does this mean? This is from the ns:/var/log/messages file: Sep 22 18:57:26 ns /kernel: rtfree: 0xf4088100 not freed (neg refs) Sep 22 18:59:14 ns /kernel: rtfree: 0xf4088100 not freed (neg refs) From owner-freebsd-hackers Tue Sep 23 17:30:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA16537 for hackers-outgoing; Tue, 23 Sep 1997 17:30:16 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA16523 for ; Tue, 23 Sep 1997 17:30:09 -0700 (PDT) Received: from nospam.hiwaay.net (max2-148.HiWAAY.net [208.147.145.148]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id TAA12457; Tue, 23 Sep 1997 19:22:32 -0500 (CDT) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id TAA10018; Tue, 23 Sep 1997 19:22:06 -0500 (CDT) Message-Id: <199709240022.TAA10018@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@FreeBSD.ORG, arg@arg1.demon.co.uk (Andrew Gordon) From: dkelly@hiwaay.net Subject: Re: lpr/lpd and HP networked printers In-reply-to: Message from j@uriah.heep.sax.de (J Wunsch) of "Tue, 23 Sep 1997 19:04:12 +0200." <19970923190412.GM59568@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Sep 1997 19:22:02 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Joerg Wunsch writes: > > As Andrew Gordon wrote: > > > If lpd is printing locally to a printer, it observes the "sh" capability > > and overrides the "L" command. However, if it is printing to a remote > > printer, it just transfers the control file unchanged and "sh" has > > no affect whatever. > > Sure, lpd is not supposed to forward the sh capability across the net. > (Actually, it doesn't forward many things.) Well, that doesn't mean it can't or shouldn't be changed. Seems to me if one puts sh in a printcap entry for a remote printer, then that's what one wants and it shouldn't be ignored if there is any way to implement. Wasn't the if filter recently enabled for remote printing? There is a program floating around the net that implements the lpd network connection itself but fits into printcap as an if or of filter. Tell printcap its a local printer on a copy of /dev/null, then push it out thru this program. I'll remember it tomorrow when I'm and work and have my notes. > Get a firmware upgrade, and you've got rid of them once and for all. Yeah, that too. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Tue Sep 23 19:07:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA21390 for hackers-outgoing; Tue, 23 Sep 1997 19:07:04 -0700 (PDT) Received: from ptway.com ([199.176.148.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA21380 for ; Tue, 23 Sep 1997 19:06:50 -0700 (PDT) Received: from brianjr.haskin.org (220R1.ptway.com [199.176.148.87]) by ptway.com (8.7.1/3.4W4-PTWAY-sco-ODT3.0) with ESMTP id VAA18134 for ; Tue, 23 Sep 1997 21:58:27 -0400 (EDT) Message-ID: <34287531.FB18FE1F@ptway.com> Date: Tue, 23 Sep 1997 22:04:33 -0400 From: Brian Haskin X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: FreeBSD-Hackers Subject: Re: r-cmds and DNS and /etc/host.conf X-Priority: 3 (Normal) References: <199709231025.GAA03822@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thomas David Rivers wrote: > > > > > In article > <199709222122.RAA02406.kithrup.freebsd.hackers@lakes.dignus.com> you > write: > > > What's strange is that things on the gateway machine seem to > access > > >the local network (presumably using /etc/hosts) just fine. It's > > >only rlogin's to the gateway machine from the internal network > > >that are causing the problem... > > > > Hm. Both you and Terry report essentially the same thing, which I > haven't > > been able to reproduce. > > > > But I did not set my machine up to be a gateway -- yet both you and > Terry > > have. > > I have also seen this going to a gateway. Both machines are running 2.2.2-RELEASE. Sorry I don't have any more info right now. Brian Haskin From owner-freebsd-hackers Tue Sep 23 19:09:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA21561 for hackers-outgoing; Tue, 23 Sep 1997 19:09:41 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA21554 for ; Tue, 23 Sep 1997 19:09:39 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA23447 for ; Tue, 23 Sep 1997 19:09:08 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma023445; Tue Sep 23 19:08:54 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id TAA04263 for freebsd-hackers@freebsd.org; Tue, 23 Sep 1997 19:08:53 -0700 (PDT) From: Archie Cobbs Message-Id: <199709240208.TAA04263@bubba.whistle.com> Subject: is this a bug? To: freebsd-hackers@freebsd.org Date: Tue, 23 Sep 1997 19:08:53 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're trying to track down a very elusive bug that involves processes ending up on two queues at once, or having runnable state SRUN and being on a sleep queue, ... etc.. Question: is there a bug in this code from tsleep() ? The code does this: 1. Puts process on a sleep queue 2. Calls CURSIG(), which can result in a context switch 3. Sets p->p_stat to SSLEEP It seems steps #2 and #3 are out of order... couldn't this result in a process being on a sleep queue yet having state SRUN? > #ifdef DIAGNOSTIC > if( p == NULL ) > panic("tsleep1"); > if (ident == NULL || p->p_stat != SRUN) > panic("tsleep"); > /* XXX This is not exhaustive, just the most common case */ > if ((p->p_procq.tqe_prev != NULL) && (*p->p_procq.tqe_prev == p)) > panic("sleeping process on run queue"); > #endif > p->p_wchan = ident; > p->p_wmesg = wmesg; > p->p_slptime = 0; > p->p_priority = priority & PRIMASK; > TAILQ_INSERT_TAIL(&slpque[LOOKUP(ident)], p, p_procq); > if (timo) > timeout(endtsleep, (void *)p, timo); > /* > * We put ourselves on the sleep queue and start our timeout > * before calling CURSIG, as we could stop there, and a wakeup > * or a SIGCONT (or both) could occur while we were stopped. > * A SIGCONT would cause us to be marked as SSLEEP > * without resuming us, thus we must be ready for sleep > * when CURSIG is called. If the wakeup happens while we're > * stopped, p->p_wchan will be 0 upon return from CURSIG. > */ > if (catch) { > p->p_flag |= P_SINTR; > if ((sig = CURSIG(p))) { > if (p->p_wchan) > unsleep(p); > p->p_stat = SRUN; > goto resume; > } > if (p->p_wchan == 0) { > catch = 0; > goto resume; > } > } else > sig = 0; > p->p_stat = SSLEEP; > p->p_stats->p_ru.ru_nvcsw++; > mi_switch(); > resume: > curpriority = p->p_usrpri; > splx(s); In fact, one panic() we got was the "wakeup_one" panic, where this test failed: > qp = &slpque[LOOKUP(ident)]; > > for (p = qp->tqh_first; p != NULL; p = p->p_procq.tqe_next) { > #ifdef DIAGNOSTIC > if (p->p_stat != SSLEEP && p->p_stat != SSTOP) > panic("wakeup_one"); > #endif Also: would there be any problems moving the "p->p_stat = SSLEEP" statement to before the "if (catch)" statement? We've tried it, and things seem to work, except for an occasional: calcru: negative time: -1318 usec which may or may not be related... Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Tue Sep 23 19:14:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA21853 for hackers-outgoing; Tue, 23 Sep 1997 19:14:27 -0700 (PDT) Received: from saturn.darmstadt.gmd.de (saturn.darmstadt.gmd.de [141.12.62.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA21848; Tue, 23 Sep 1997 19:14:25 -0700 (PDT) From: 27351108@aol.com Received: from www.darmstadt.gmd.de (78.new-york-17.ny.dial-access.att.net [12.68.126.78]) by saturn.darmstadt.gmd.de (8.8.5/8.8.5) with SMTP id DAA27545; Wed, 24 Sep 1997 03:45:57 +0200 (MET DST) Received: from postmaster232432422@mailexcite.com by aol.com (8.8.5/8.6.5) with SMTP id GAA08285 for <>; Fri, 30 May 1997 18:19:13 -0600 (EST) Date: Fri, 30 May 97 18:19:13 EST To: Friend@public.com Subject: 101 Very Wild xxxx Rated Channels Free When U Join Message-ID: <8123123234237736128736.com> Reply-To: 12314231232432234122122@darmstadt.gmd.de Comments: Authenticated sender is <1321232312543232132222222> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk http://www.schoolgirlz.com All This FREE When You Join! View 6 Channels At Once! 101 WILD XXX RATED LIVE CHANNELS - 2 ALL BLONDE CHANNELS 2 MULTIPLE GIRL CHANNELS - 2 CHANNELS OF REDHEADS AND BRUNNETTES 1 ALL BLACK CHANNEL - 1 INTERNATIONAL GIRLS FROM AROUND THE W0RLD 2 TEEN CHANNELS (18 AND 19 YR OLD BABES) - 4 CHANNELS REAL SEX SHOWS-MALE/FEMALE-LESBIAN) 2 MUCH 2 List...Check It Out http://www.schoolgirlz.com From owner-freebsd-hackers Tue Sep 23 19:49:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23911 for hackers-outgoing; Tue, 23 Sep 1997 19:49:54 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA23905 for ; Tue, 23 Sep 1997 19:49:46 -0700 (PDT) Received: from nospam.hiwaay.net (tnt2-52.HiWAAY.net [208.147.148.52]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id VAA25939 for ; Tue, 23 Sep 1997 21:49:08 -0500 (CDT) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id VAA28533 for ; Tue, 23 Sep 1997 21:49:07 -0500 (CDT) Message-Id: <199709240249.VAA28533@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@freebsd.org Subject: NGROUPS in include file(s) From: dkelly@HiWAAY.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Sep 1997 21:49:04 -0500 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ran across a little gotcha while porting to FreeBSD 2.2.2 where the didn't have the #ifdef __FreeBSD__ shown below but needed it in order to get a definition of NGROUPS. Take out my #include and get: /usr/include/sys/ucred.h:47: `NGROUPS' undeclared here (not in a function) This mess starts in Am wondering if the include tree is supposed to include other include files when making references to external items? Or am I supposed to hunt them down and include them all myself? This is the really tough demo program: #include #include #ifdef __FreeBSD__ #include #endif #include void main (void) { printf ("Hello World!\n"); } -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Tue Sep 23 21:45:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA29901 for hackers-outgoing; Tue, 23 Sep 1997 21:45:58 -0700 (PDT) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA29894 for ; Tue, 23 Sep 1997 21:45:53 -0700 (PDT) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id AAA05932; Wed, 24 Sep 1997 00:45:23 -0400 (EDT) Date: Wed, 24 Sep 1997 00:45:23 -0400 (EDT) From: Charles Owens To: hackers list FreeBSD cc: Andrew Gordon Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andrew Gordon wrote: > On Tue, 23 Sep 1997, J Wunsch [and others!] wrote: > > As Andrew Gordon wrote: > > > > > This is easy enough to fix, though it is not obvious which is the > > > correct way. There are a number of possibilities: > > > > > 6) Telnet to your JetDirect, and turn off banner pages. That's > > how i always did it. > Well, I have now tried the three printers that I can access remotely, > and none of them support this (they support the telnet prompt for > configuration, but banners are not one of the available options; I tried > typing the suggested "banner:0" in case it was an undocumented feature, > but that gave me an error). These three machines are various different > models of laserjet 4 (4M, 4M+ etc.), aged between 2 and 4 years old. > Maybe there has been a firmware upgrade since; I certainly spent plenty > of effort (including talking to HP support) trying to find a way to > disable it at the time the first one was installed, but to no avail. You're getting warmer. A firmware upgrade is what you're looking for. Go to: http://hpcc923.external.hp.com/cposupport/indexes1/firmwars.html This page has the firmware upgrade images, plus the HP Download Manager tool that you use to actually install it. Once you upgrade to the latest firmware you'll find that the banner command (and some other new stuff) is available. It's not, however, quite so simple. In order for this process to work, you must have configured the SNMP-Set community string. To do this, you must create a tftp'able configuration file that contains at least this setting. Then, you must configure your bootp server (you _are_ using bootp, right!?!) so that the entry for the printer has the vendor extended option T144 set to the tftp path of the file. As an example, my config file looks like this # HP LJ config file location: Young, Math/CS Dept., PC Lab contact: Information Technology Services, x3803, its-help@enc.edu # get-community-name: fooBar set-community-name: fooBar old-idle-mode: off banner: 0 # telnet-disable: 1 Note, I have the get-community-name setting commented out. This is necessary because the Download Manager program allows you to specify the set-community-name that it should use, but not the get-community-name. Leaving its commented out as shown causes the printer to respond to any and all SNMP get requests, which is the only way that I could get the download process to happen. Once you're done with the upgrade, you can, of course, set the get-string to something specific. Here's a snippet from my dhcpd.conf file (I use the ISC's dhcpd for dhcpd _and_ bootp service) that shows the needed parameters to load the config file: host mtcslj4a.ac.enc.edu { hardware ethernet 08:00:09:77:1A:A8; next-server delta.enc.edu; option option-144 "hplj.cfg"; fixed-address mtcslj4a.ac.enc.edu; } This can be done just as easily with the "standard" bootp/bootptab. You should know that the config file can contain a number of other settings. For somewhat useful docs on this (but without proper syntax), see ftp://ftp.hp.com/pub/networking/support_doc/bpj02835.asc and ftp://ftp.hp.com/pub/networking/support_doc/bpj02836.asc To see the true syntax of the config file options, download the HP Jetadmin software package for HP-UX and look for the file */examples/tftp.conf See also the file bootptab in the same dir. It's pretty nifty stuff, though one shouldn't have to dig quite so hard to find these details, and the HP engineer should have known that you needed to upgrade your firmware. Ah well... :-) --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-hackers Tue Sep 23 22:24:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA01774 for hackers-outgoing; Tue, 23 Sep 1997 22:24:21 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA01768; Tue, 23 Sep 1997 22:24:16 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA20679; Wed, 24 Sep 1997 06:11:32 +0200 From: Luigi Rizzo Message-Id: <199709240411.GAA20679@labinfo.iet.unipi.it> Subject: Re: Diskless Workstation -- Problems needing to be addressed To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Wed, 24 Sep 1997 06:11:32 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 23, 97 12:47:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Last time I called Linksys they were reluctantly willing to give me some > unusual info about the NE2000 cards we have, and possibly I could buy a > boot rom off them and take a look at it :>) my experience on this: I looked at a boot rom for some other PCI ne200 clone. They only had code for novell, and internally the rom looked much different from what "PCI system architecture" says... My experience is that some BIOSes work fine with a normal ISA boot rom such as the one produced by netboot, and others (presumably old ones) seem not to like boot roms on PCI cards (the same card+rom on another system works fine) even if build the way PCI system architecture says. So my advice is to try the standard rom first... As a quick and dirty alternative, since I have some broken ISA network cards, at times I put there the card with the only purpose of acting as a boot rom socket. One more advanced option could be to update the flash bios to include the boot room, but this is a bit risky... As for 100 Mbit/s cards, remember they are quite different from ne2000, and that you will probably have to import a lot of code the controller (DEC 21x4x ?) they use. Unfortunately you cannot just link in say if_de.c , probably a lot of hand editing would be necessary (and a copy of the controller's data sheets). Luckily PCI cards tend to have only one chip so if you have those docs (often available from the manufacturer, e.g. www.dec.com or www.intel.com) you are in good shape... Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Tue Sep 23 22:45:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA02969 for hackers-outgoing; Tue, 23 Sep 1997 22:45:27 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA02962 for ; Tue, 23 Sep 1997 22:45:25 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA03538; Tue, 23 Sep 1997 22:45:23 -0700 (MST) From: Terry Lambert Message-Id: <199709240545.WAA03538@usr07.primenet.com> Subject: Re: vt420 termcap needed (fwd) To: jbryant@tfs.net Date: Wed, 24 Sep 1997 05:45:22 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199709231821.NAA01912@argus.tfs.net> from "Jim Bryant" at Sep 23, 97 01:21:24 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > does anyone have a termcap entry for the vt420? A VT420 is functionally identical, for everything but graphic modes, to a VT320, which is functionally identical to a VT220, except because of the softROM is a hell of a lot slower than a VT220, and supports 9 bit instead of 8-bit-with-9th-bit-the-same-as-8th sixel graphics (which you will never use, in practice, because the termiinals support ISO8859-1 character sets (and the less useful DEC techinical character sets), as well as 7-bit NRCS's (National replacement Character Set). Are you expecting to program graphics or sixels via termcap? ...Didn't think so. 8-). VT4xx and VT3xx series terminals also support LAT-based session switching; however, since this is not documented anywhere publically, nor does FreeBSD have drivers for it, this particular feature is useless to you unless your terminal is connecting through a DEC-Server 2xx or better which is being booted via MOP-MOM off a VMS box (in which case the only way you're getting into your FreeBSD box is telnet, rlogin, or the undocumented X-on-TCP-to-X-on-DECNet gateway on Ultrix boxes). So tell FreeBSD it's a "vt220"; preferrably a "vt220am", assuming you have line wrap turned on (the factory default for the 2xx, 3xx, and 4xx terminals). 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-hackers Tue Sep 23 22:45:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA02992 for hackers-outgoing; Tue, 23 Sep 1997 22:45:43 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA02987 for ; Tue, 23 Sep 1997 22:45:40 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA20450; Tue, 23 Sep 1997 22:47:53 -0700 (PDT) Message-Id: <199709240547.WAA20450@implode.root.com> To: Archie Cobbs cc: freebsd-hackers@FreeBSD.ORG Subject: Re: is this a bug? In-reply-to: Your message of "Tue, 23 Sep 1997 19:08:53 PDT." <199709240208.TAA04263@bubba.whistle.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 23 Sep 1997 22:47:53 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >We're trying to track down a very elusive bug that involves processes >ending up on two queues at once, or having runnable state SRUN and >being on a sleep queue, ... etc.. > >Question: is there a bug in this code from tsleep() ? The code does this: > > 1. Puts process on a sleep queue > 2. Calls CURSIG(), which can result in a context switch > 3. Sets p->p_stat to SSLEEP > >It seems steps #2 and #3 are out of order... couldn't this result >in a process being on a sleep queue yet having state SRUN? After a quick look at this, the code does look like it could contain some bugs, although I don't yet see a path that could explain the panic. There are a couple possible causes of something like this...one of them is a driver or kernel routine calling tsleep() while in an interrupt routine (a no no), perhaps due to a malloc with M_WAITOK - this is the most common cause. There might also be some hidden recursion in tsleep or children of it that could cause this; I don't see that in the code, however. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Sep 23 22:52:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03532 for hackers-outgoing; Tue, 23 Sep 1997 22:52:01 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03514 for ; Tue, 23 Sep 1997 22:51:58 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA03740; Tue, 23 Sep 1997 22:51:44 -0700 (MST) From: Terry Lambert Message-Id: <199709240551.WAA03740@usr07.primenet.com> Subject: Re: lpr/lpd and HP networked printers To: joe@pavilion.net (Josef Karthauser) Date: Wed, 24 Sep 1997 05:51:43 +0000 (GMT) Cc: dkelly@hiwaay.net, arg@arg1.demon.co.uk, hackers@FreeBSD.ORG In-Reply-To: <19970923212006.58866@pavilion.net> from "Josef Karthauser" at Sep 23, 97 09:20:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Talking of HP laserjets... has anyone had any success in configuring > a printcap to enable paper tray selection? A long time ago. I used a "banner page" that output a tray select; I also did a "banner page" that would do a "Postscript select" or an "HPGL select". We actually got rid of user selectable paper trays, and loaded yellow paper into one (the smaller) tray and white into the other. Then we selected the yellow tray, output a real banner, selected the white tray, and output the print job. So we ended up with a banner anyway (it was for a student lab, and it made seperating jobs into alphabetic bins easier for the lab aides). Anyway, lie about your banner, and define multiple printers that use different "banners" to reference the same physical printer. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Sep 23 22:57:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03865 for hackers-outgoing; Tue, 23 Sep 1997 22:57:27 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03853 for ; Tue, 23 Sep 1997 22:57:16 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id XAA18257; Tue, 23 Sep 1997 23:02:47 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id WAA02858; Tue, 23 Sep 1997 22:52:35 -0700 (PDT) Date: Tue, 23 Sep 1997 22:52:35 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199709240552.WAA02858@dog.farm.org> To: haskin@ptway.com (Brian Haskin) Cc: freebsd-hackers@freebsd.org Subject: Re: r-cmds and DNS and /etc/host.conf Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <34287531.FB18FE1F@ptway.com> you wrote: > > > In article > > <199709222122.RAA02406.kithrup.freebsd.hackers@lakes.dignus.com> you > > write: > > > > What's strange is that things on the gateway machine seem to > > access > > > >the local network (presumably using /etc/hosts) just fine. It's > > > >only rlogin's to the gateway machine from the internal network > > > >that are causing the problem... > > > > I have also seen this going to a gateway. Both machines are running > 2.2.2-RELEASE. Sorry I don't have any more info right now. I have just tested this on two machines, client running 2.2-old and server running 2.2.2-R. The bug is there, in rlogind or libraries it uses. How to test: on server machine, put 127.0.0.1 into resolv.conf; start named; run tcpdump -l -i lo0 -s 512 now rlogin from your client. see queries going to local nameserver on server machine. in my case, these are: # tcpdump -l -i lo0 -s 512 tcpdump: listening on lo0 22:53:50.569483 localhost.1319 > localhost.domain: 31153+ A? dog.stranger.com. (34) 22:53:50.570916 localhost.domain > localhost.1319: 31153 NXDomain* 0/1/0 (87) 22:53:50.572942 localhost.1320 > localhost.domain: 31154+ A? dog. (21) 22:53:50.573687 localhost.domain > localhost.1320: 31154 NXDomain* 0/0/0 (21) so, server tried to resolve names `dog.stranger.com.' - note the trailing dot - and then `dog.' (dog is client machine; stranger.com is domain). None of those are in hosts, of course. -- /earth is 98% full ... please delete anyone you can. From owner-freebsd-hackers Tue Sep 23 23:21:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA05540 for hackers-outgoing; Tue, 23 Sep 1997 23:21:53 -0700 (PDT) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA05530 for ; Tue, 23 Sep 1997 23:21:49 -0700 (PDT) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.7/8.8.6) with ESMTP id IAA26118; Wed, 24 Sep 1997 08:21:41 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.7/8.8.5) id IAA02696; Wed, 24 Sep 1997 08:21:40 +0200 (CEST) To: jbryant@tfs.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vt420 termcap needed (fwd) References: <199709231821.NAA01912@argus.tfs.net> From: Thomas Gellekum Date: 24 Sep 1997 08:21:39 +0200 In-Reply-To: Jim Bryant's message of Tue, 23 Sep 1997 13:21:24 -0500 (CDT) Message-ID: <87lo0n1bbg.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 12 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jim Bryant writes: > does anyone have a termcap entry for the vt420? See http://locke.ccil.org/~esr/terminfo.html. esr writes: The terminfo/termcap database -- In January 1995 I accepted the maintainership of the BSD terminal-type database from John Kunze. You can download it in either termcap or terminfo form from here. tg From owner-freebsd-hackers Tue Sep 23 23:44:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07359 for hackers-outgoing; Tue, 23 Sep 1997 23:44:19 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07347 for ; Tue, 23 Sep 1997 23:44:13 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA00989 for ; Tue, 23 Sep 1997 23:44:09 -0700 (PDT) Date: Tue, 23 Sep 1997 23:44:09 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@freebsd.org Subject: Raise your hand if you know how to make this work. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Personally, I don't care how much processor overhead it takes. I simply just want to be able to get a loop running at ~1000hz, because I've taken a look at the technical manuals for some of the hardware I am using. These boards can pass through an interupt on a rising edge to one of the digital input lines. This makes me think I could hook it up to one of the clocks on the included 8253 and make it generate a periodic interrupt (in fact I am quite sure of this). However, this is not how the board was intended to be used, it is designed as a polling device and if it was connected to an dedicated computer that is probably precisely how I would use it. What I refuse to believe is that freebsd is incapable of this task, there are plenty of devices in the world that are by nature polling type device even though this doesn't fit very well into the event driven picture of things. You see, there is really no difference between me making some physically external connections (and using another interrupt line that could be utilized for something better) patching in a device driver specifically for this purpose, or simply having a small piece of user code with SIGALRM delivered on a more timely basis (e.g. setitimer() that is more or less reliable to 1ms). I don't understand exactly why but I know that for instance in Linux, Alphas generally have a scheduling clock frequency of either 1 or 2khz (I'll have to check again) what Is so wrong with x86 that it cannot do this also? From owner-freebsd-hackers Tue Sep 23 23:45:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07444 for hackers-outgoing; Tue, 23 Sep 1997 23:45:38 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07431 for ; Tue, 23 Sep 1997 23:45:34 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id CAA00793 for ; Wed, 24 Sep 1997 02:50:55 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Wed, 24 Sep 1997 02:50:55 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: HD controller weirdness... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i have an old Acer P90 system, when doing the freebsd install for some reason it wouldn't detect the HD controller most of the time, then after moving some boards around inside it worked... just today i closed the machine up, and afterward same problem, the kernel kept freaking out about not being able to find the root device... now since it was booting off the hardrive i though that it wouldn't have a problem, so i reopend the machine and kinda checked all my ISA/PCI connctions and wha-la... it worked again. btw, what i mean about worked is that, when it's not working the kernel fails to detect the harddrive controller and therefore freaks out without a root filesystem... this has me confused, if the machine is booting off of the harddrive you'd think there wouldn't be a problem with it... ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" From owner-freebsd-hackers Tue Sep 23 23:50:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07929 for hackers-outgoing; Tue, 23 Sep 1997 23:50:47 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07923; Tue, 23 Sep 1997 23:50:44 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA00997; Tue, 23 Sep 1997 23:49:52 -0700 (PDT) Date: Tue, 23 Sep 1997 23:49:52 -0700 (PDT) From: "Jamil J. Weatherbee" To: Luigi Rizzo cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709240411.GAA20679@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think in my situation since I am slowly transitioning from 10 base T to 100 baseT I can just put Two cards in each (I don't know what function this really serves since the bootp server is also sits betweens the networks and acts as a router?) but I'd much rather look at the specs and work it out (that will be the long term solution --- perhaps also educational). On Wed, 24 Sep 1997, Luigi Rizzo wrote: > > Last time I called Linksys they were reluctantly willing to give me some > > unusual info about the NE2000 cards we have, and possibly I could buy a > > boot rom off them and take a look at it :>) > > my experience on this: I looked at a boot rom for some other PCI > ne200 clone. They only had code for novell, and internally the rom > looked much different from what "PCI system architecture" says... > My experience is that some BIOSes work fine with a normal ISA boot > rom such as the one produced by netboot, and others (presumably > old ones) seem not to like boot roms on PCI cards (the same card+rom > on another system works fine) even if build the way PCI system > architecture says. So my advice is to try the standard rom first... > > As a quick and dirty alternative, since I have some broken ISA > network cards, at times I put there the card with the only purpose > of acting as a boot rom socket. > > One more advanced option could be to update the flash bios to > include the boot room, but this is a bit risky... > > As for 100 Mbit/s cards, remember they are quite different from ne2000, > and that you will probably have to import a lot of code the controller > (DEC 21x4x ?) they use. Unfortunately you cannot just link in say > if_de.c , probably a lot of hand editing would be necessary (and a copy > of the controller's data sheets). Luckily PCI cards tend to have only > one chip so if you have those docs (often available from the > manufacturer, e.g. www.dec.com or www.intel.com) you are in good > shape... > > Cheers > Luigi > -----------------------------+-------------------------------------- > Luigi Rizzo | Dip. di Ingegneria dell'Informazione > email: luigi@iet.unipi.it | Universita' di Pisa > tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) > fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ > _____________________________|______________________________________ > From owner-freebsd-hackers Wed Sep 24 00:41:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA11808 for hackers-outgoing; Wed, 24 Sep 1997 00:41:24 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA11801 for ; Wed, 24 Sep 1997 00:41:21 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA03770 for hackers@FreeBSD.ORG; Wed, 24 Sep 1997 09:41:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA04407; Wed, 24 Sep 1997 09:29:10 +0200 (MET DST) Message-ID: <19970924092910.HV02996@uriah.heep.sax.de> Date: Wed, 24 Sep 1997 09:29:10 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: lpr/lpd and HP networked printers References: <19970923190412.GM59568@uriah.heep.sax.de> <199709240022.TAA10018@nospam.hiwaay.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709240022.TAA10018@nospam.hiwaay.net>; from dkelly@hiwaay.net on Sep 23, 1997 19:22:02 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As dkelly@hiwaay.net wrote: > Well, that doesn't mean it can't or shouldn't be changed. Seems to me if > one puts sh in a printcap entry for a remote printer, then that's what > one wants and it shouldn't be ignored if there is any way to implement. Well, i don't mind if somebody would do the deed... :) -- 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-hackers Wed Sep 24 01:40:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA15630 for hackers-outgoing; Wed, 24 Sep 1997 01:40:23 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA15624 for ; Wed, 24 Sep 1997 01:40:21 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA21456; Wed, 24 Sep 1997 01:15:32 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021454; Wed Sep 24 08:15:26 1997 Date: Wed, 24 Sep 1997 01:34:25 -0700 (PDT) From: Julian Elischer To: "Jamil J. Weatherbee" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Raise your hand if you know how to make this work. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk there is a function to do this for you it's rather trivial. check clock.c and see how the PCAUDIO device uses this to get itself called 16000 times per second.. On Tue, 23 Sep 1997, Jamil J. Weatherbee wrote: > > Personally, I don't care how much processor overhead it takes. I simply > just want to be able to get a loop running at ~1000hz, because I've taken > a look at the technical manuals for some of the hardware I am using. > These boards can pass through an interupt on a rising edge to one of the > digital input lines. This makes me think I could hook it up to one of the > clocks on the included 8253 and make it generate a periodic interrupt (in > fact I am quite sure of this). However, this is not how the board was > intended to be used, it is designed as a polling device and if it was > connected to an dedicated computer that is probably precisely how I would > use it. What I refuse to believe is that freebsd is incapable of this > task, there are plenty of devices in the world that are by nature polling > type device even though this doesn't fit very well into the event driven > picture of things. You see, there is really no difference between me > making some physically external connections (and using another interrupt > line that could be utilized for something better) patching in a device > driver specifically for this purpose, or simply having a small piece of > user code with SIGALRM delivered on a more timely basis (e.g. setitimer() > that is more or less reliable to 1ms). I don't understand exactly why but > I know that for instance in Linux, Alphas generally have a scheduling > clock frequency of either 1 or 2khz (I'll have to check again) what Is so > wrong with x86 that it cannot do this also? > > > From owner-freebsd-hackers Wed Sep 24 01:52:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA16564 for hackers-outgoing; Wed, 24 Sep 1997 01:52:10 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA16559 for ; Wed, 24 Sep 1997 01:52:07 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id BAA13893; Wed, 24 Sep 1997 01:51:58 -0700 (PDT) Date: Wed, 24 Sep 1997 01:51:58 -0700 (PDT) From: "Jamil J. Weatherbee" To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: HD controller weirdness... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Booting is generally done using the bios whereas mounting the root filesystem is done with the bsd hard drive drivers. > this has me confused, if the machine is booting off of the harddrive you'd > think there wouldn't be a problem with it... From owner-freebsd-hackers Wed Sep 24 02:41:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA19002 for hackers-outgoing; Wed, 24 Sep 1997 02:41:25 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA18996 for ; Wed, 24 Sep 1997 02:41:20 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id CAA18573; Wed, 24 Sep 1997 02:46:51 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id CAA05910; Wed, 24 Sep 1997 02:37:27 -0700 (PDT) Date: Wed, 24 Sep 1997 02:37:27 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199709240937.CAA05910@dog.farm.org> To: arg@arg1.demon.co.uk (Andrew Gordon) Cc: freebsd-hackers@freebsd.org Subject: Re: lpr/lpd and HP networked printers Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > Maybe I didn't make this clear: having looked at the protocol, I find I > can suppress the banner page when printing from a FreeBSD machine too, so > long as I use "lpr -h". The printer is obeying the "L" command code in > the print job control file (both the HP and Intel devices do so). > The problem is that with hundreds of users, printing via many different > methods (manual lpr, from netscape, via Samba, via PC-NFS etc.) getting > the "-h" into all the applicable config files/user's brains is impractical. > If lpd is printing locally to a printer, it observes the "sh" capability > and overrides the "L" command. However, if it is printing to a remote > printer, it just transfers the control file unchanged and "sh" has > no affect whatever. force them all to print to a proxy lpd on a Unix host. Patch the lpd on this host, add new capability (network-sh), and add it to definition of this printer. You get side advantages: accounting, possible filtering/quotas, and virtual printer (imagine adding new printer and asking everybody to change). Meanwhile, ask HP to give you an upgrade that works... ;-) -- "Books: You can't grep dead trees." -- Dion Favors(?) From owner-freebsd-hackers Wed Sep 24 03:09:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA20249 for hackers-outgoing; Wed, 24 Sep 1997 03:09:05 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA20239 for ; Wed, 24 Sep 1997 03:08:56 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id DAA18662 for ; Wed, 24 Sep 1997 03:14:46 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id DAA06292 for freebsd-hackers@freebsd.org; Wed, 24 Sep 1997 03:08:30 -0700 (PDT) Date: Wed, 24 Sep 1997 03:08:30 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199709241008.DAA06292@dog.farm.org> To: freebsd-hackers@freebsd.org Subject: Re: r-cmds and DNS and /etc/host.conf Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709240552.WAA02858@dog.farm.org> you wrote: > In article <34287531.FB18FE1F@ptway.com> you wrote: > > > > In article > > > <199709222122.RAA02406.kithrup.freebsd.hackers@lakes.dignus.com> you > > > write: > > > > > What's strange is that things on the gateway machine seem to > > > access > > > > >the local network (presumably using /etc/hosts) just fine. It's > > > > >only rlogin's to the gateway machine from the internal network > > > > >that are causing the problem... > I have just tested this on two machines, client running 2.2-old and > server running 2.2.2-R. The bug is there, in rlogind or libraries it uses. > # tcpdump -l -i lo0 -s 512 tcpdump: listening on lo0 > 22:53:50.569483 localhost.1319 > localhost.domain: 31153+ A? dog.stranger.com. (34) > 22:53:50.570916 localhost.domain > localhost.1319: 31153 NXDomain* 0/1/0 (87) > 22:53:50.572942 localhost.1320 > localhost.domain: 31154+ A? dog. (21) > 22:53:50.573687 localhost.domain > localhost.1320: 31154 NXDomain* 0/0/0 (21) > so, server tried to resolve names `dog.stranger.com.' - note the trailing > dot - and then `dog.' (dog is client machine; stranger.com is domain). > None of those are in hosts, of course. the lookups occur only if .rhosts is present. So, it's in /usr/src/lib/libc/net/rcmd.c:iruserok() or deeper (_not_ ruserok() - this one tests by IP address). -- >From the DOS/Windows95 perspective, memory management is one of the strong points of Nintendo cartridges. --Terry Lambert From owner-freebsd-hackers Wed Sep 24 07:57:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA03058 for hackers-outgoing; Wed, 24 Sep 1997 07:57:44 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA03048 for ; Wed, 24 Sep 1997 07:57:38 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA21711 for hackers@freebsd.org; Wed, 24 Sep 1997 15:41:37 +0200 From: Luigi Rizzo Message-Id: <199709241341.PAA21711@labinfo.iet.unipi.it> Subject: disk scheduling... To: hackers@freebsd.org Date: Wed, 24 Sep 1997 15:41:37 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I seem to remember this was debated some time ago but do not remember the status of the code. At any rate.. on a 2.2.1 system (SCSI for what matters), I am doing moving a large subtree from one position to another, and it turns out that during this operation interactive performance is awful for data which is not cached. I think to remember that the explaination was that there is no fair sharing of disk access, so a process queueing large blocks of io can eat almost all the resources. I am not sure if the problem can be solved easily (in that at some point transactions might have become anonymous...) Still if I wanted to look at possible solutions, can someone point me to the right place (documentation, sources, hints etc. ?) Perhaps some VM guru can help ? Thanks Luigi From owner-freebsd-hackers Wed Sep 24 08:44:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA05815 for hackers-outgoing; Wed, 24 Sep 1997 08:44:49 -0700 (PDT) Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA05809 for ; Wed, 24 Sep 1997 08:44:46 -0700 (PDT) Received: from cssmuc.frt.dec.com (cssmuc.frt.dec.com [16.186.96.161]) by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) with SMTP id LAA31982 for ; Wed, 24 Sep 1997 11:03:55 -0400 (EDT) Received: from mofo.frt.dec.com by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA09881; Wed, 24 Sep 1997 17:03:52 +0200 Received: from mofo.frt.dec.com (localhost [127.0.0.1]) by mofo.frt.dec.com (8.8.6/8.8.5) with ESMTP id RAA00383 for ; Wed, 24 Sep 1997 17:01:06 GMT Message-Id: <199709241701.RAA00383@mofo.frt.dec.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@freebsd.org In-Reply-To: Message from Alfred Perlstein of Wed, 24 Sep 1997 02:50:55 EST. Reply-To: gjennejohn@frt.dec.com Subject: Re: HD controller weirdness... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Sep 1997 17:01:05 +0000 From: Gary Jennejohn Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein writes: > this has me confused, if the machine is booting off of the harddrive you'd > think there wouldn't be a problem with it... > boot uses the BIOS, not a driver in FreeBSD. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) garyj@muc.de (play) gj@freebsd.org From owner-freebsd-hackers Wed Sep 24 10:14:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11455 for hackers-outgoing; Wed, 24 Sep 1997 10:14:35 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA11427 for ; Wed, 24 Sep 1997 10:14:14 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.7/8.8.5) with ESMTP id MAA27072; Wed, 24 Sep 1997 12:12:30 -0500 (CDT) Message-Id: <199709241712.MAA27072@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jamil J. Weatherbee" cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: ISDN Modems In-reply-to: Your message of "Tue, 23 Sep 1997 12:52:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Sep 1997 12:12:30 -0500 From: Wm Brian McCane Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I can verify that the Pipelines do have this ability however make sure > that the other end is using ascend hardware -- otherwise things like STAC > compression etc. won't work. > My ISP actually uses standalone P50's for supplying ISDN to their customers, so this is not a problem. I will be buying one from them for $550US, and they will have one at their end. I have also been talking to them about possibly helping them upgrade their system to use a Ascend 1800 or 4???, with a PRI coming in (they currently order a BRI for a new customer). I figured that based on the number of lines they currently support and the cost of a PRI ($425US), they could break even fairly quickly. brian From owner-freebsd-hackers Wed Sep 24 11:05:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14850 for hackers-outgoing; Wed, 24 Sep 1997 11:05:43 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14828 for ; Wed, 24 Sep 1997 11:05:35 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id MAA06117 for ; Wed, 24 Sep 1997 12:06:29 -0600 (MDT) Date: Wed, 24 Sep 1997 12:06:29 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: crypt() returning an error... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The man page on crypt() states that a NULL will be returned instead of a pointer to a string, if an error occurred. The MD5 crypt does not follow this, however DES crypt does. Furthermore, in the attempt to hunt out a 'standard' for handling error codes, I have checked how other crypt() implementations function. OpenBSD for some unknown reason returns the string: ":" Where Digital Unix also returns a NULL, as does Unixware--however their manual pages do not specify NULL as a valid return value. With this in mind, I think I will standardize this behaviour to 'crypt()' in that if an error occurs (there are more possibilities, with the additional $x$x$x.. possibilities) then a NULL will be returned. This means that what currently works with MD5 crypt will no longer be the case. For instance: crypt("", "") With MD5 will actually return an encrypted value, with a zero-length salt. After my changes, this will return a NULL instead. Anybody forsee any problems with this? I do not, but I figured I would bring it up... From owner-freebsd-hackers Wed Sep 24 12:00:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18313 for hackers-outgoing; Wed, 24 Sep 1997 12:00:06 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA18275; Wed, 24 Sep 1997 12:00:02 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA10662 (5.67b/IDA-1.5); Wed, 24 Sep 1997 21:00:03 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id UAA01561; Wed, 24 Sep 1997 20:55:19 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709241855.UAA01561@yedi.iaf.nl> Subject: Re: DPT Firmware Problem To: Shimon@i-Connect.Net (Simon Shapiro) Date: Wed, 24 Sep 1997 20:55:18 +0200 (MET DST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Sep 23, 97 03:56:16 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote... > Again, apologies for the cross posting. > > We have discovered a serious bug in the DPT firmware, Version 7L0. > > It manifests itself in the following manner (at least): > > * On Single Ended controllers; The ``Shelf Good'' signal reaches the DPT > from the disk bay, but the HBA equivalent (HBA Good) does not reach the > disk bay. As a result, the fault light remains on, and the disk > cassettes will erratically display the fault light. > > * On differential controllers connected via Diff-SE adaptor; A whole bus > will seem to have disappeared. If you struggle with the cables, you MAY > see it for a while, but it will not survive a re-boot. > > Solution: Roll back to (ar stay at) the 7H firmware. I have posted 7H3 > firmware in ftp://sendero-ppp.i-connect.net/crash/476d07h3.fwi > There are no restrictions on downloading it. > > We know of this problem with several StorageWorks disk bays, ours included. > We have not tested it with other disk bays, and drives which are directly > connected are NOT effected. Simon, Could you get me more info on the problems with the StorageWorks shelves? I work in DEC Storage engineering and might be able to help you with this problem. What shelves do you use? WHich disks? Revisions etc. I assume things like the Shelve OK jumpers are set correctly? Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Wed Sep 24 12:23:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA20026 for hackers-outgoing; Wed, 24 Sep 1997 12:23:15 -0700 (PDT) Received: from prometeo.prometeo.it (prometeo.prometeo.it [195.78.194.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA20006 for ; Wed, 24 Sep 1997 12:23:05 -0700 (PDT) Received: from goedel.prometeo.it (goedel.prometeo.it [195.78.194.3]) by prometeo.prometeo.it (8.8.6/8.8.6) with SMTP id VAA24695; Wed, 24 Sep 1997 21:32:54 +0200 (MET DST) Message-Id: <199709241932.VAA24695@prometeo.prometeo.it> Comments: Authenticated sender is From: "Coi Giovanni" Organization: Prometeo srl To: freebsd-hackers@freebsd.org Date: Wed, 24 Sep 1997 21:21:50 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: wd1: invalid primary partition table: no magic Reply-to: coi.giovanni@prometeo.it CC: dwhite@resnet.uoregon.edu X-Confirm-Reading-To: coi.giovanni@prometeo.it X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail for Win32 (v2.54) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I have read the tutorial on 'Formatting Media For Use With FreeBSD 2.2-RELEASE' and I tryed to add a second disk to my FreeBSD box. By the way it is a 2.1.7 release but I think will upgrading to 2.2.5 soon (when 2.2.5 will be release). I have a strange (for me) message when I execute some command like disklabel (or fsck) it display on console wd1: invalid primary partition table: no magic for example: dd if=/dev/zero of=/dev/rwd1 count=2 (this is ok) disklabel -e -r /dev/rwd1 (this rise the error/warning messages, then I edit the partition table and...) newfs /dev/rwd1a (this is ok) and all seem to work correctly! I may mount the partitions and copy some file (about 40 Mbyte) on them without apparently no problem. What does it means? ===================================================== Add the results of fsck and disklabel messages fdisk /dev/wd1c ----------------------------------------------------- ******* Working on device /dev/wd1c ******* parameters extracted from in-core disklabel are: cylinders=4092 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=4092 heads=16 sectors/track=63 (1008 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 1, size 4124735 (2014 Meg), flag 80 beg: cyl 0/ sector 2/ head 0; end: cyl 1020/ sector 1/ head 0 ===================================================== disklabel -r wd1 ----------------------------------------------------- # /dev/rwd1c: type: unknown disk: wd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 4092 sectors/unit: 4124736 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2000000 0 4.2BSD 0 0 0 # (Cyl. 0 - 1984*) b: 2124736 2000000 4.2BSD 0 0 0 # (Cyl. 1984*- 4091*) c: 4124736 0 unused 0 0 # (Cyl. 0 - 4091) Any suggestions? Thank you in advance. Giovanni Coi ---------------------------------------------------------- Prometeo srl - Progetti e Metodologie Informatiche Internet Services Provider Coi Giovanni Voice : +39 (041)5701366 Via Giudecca 15 Fax : +39 (041)5701005 30035 MIRANO (VE) - ITALY e-mail: coi@prometeo.it http://www.prometeo.it From owner-freebsd-hackers Wed Sep 24 14:00:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27204 for hackers-outgoing; Wed, 24 Sep 1997 14:00:03 -0700 (PDT) Received: from hammurabi.nh.ultra.net (hammurabi.nh.ultra.net [205.162.79.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA27100 for ; Wed, 24 Sep 1997 13:59:54 -0700 (PDT) Received: from lucy.portsmouth (paulg.nh.ultranet.com [207.41.158.58]) by hammurabi.nh.ultra.net (8.8.5/ult1.04) with SMTP id QAA01982 for ; Wed, 24 Sep 1997 16:59:45 -0400 (EDT) Received: (qmail 10641 invoked from network); 24 Sep 1997 20:59:02 -0000 Received: from unknown (HELO qosnet.com) (192.32.47.90) by 192.32.47.84 with SMTP; 24 Sep 1997 20:59:02 -0000 Message-ID: <34297EF1.937436D6@qosnet.com> Date: Wed, 24 Sep 1997 16:58:26 -0400 From: Michael Saal X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: SMC 9332BDT (DEC 21140-AE) doesn't work Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We are building several new systems with 2.2.2-RELEASE and are in a bit of a jam with our new SMC 9332BDT (DEC 21140-AE) interface cards. When the kernel boots the cards are recognized but do not work. I was wondering if anybody has a patch for if_de.c that will fix this particular variant of the 21140. Thanks Michael Saal Qosnetics msaal@qosnetics.com From owner-freebsd-hackers Wed Sep 24 14:51:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA00496 for hackers-outgoing; Wed, 24 Sep 1997 14:51:11 -0700 (PDT) Received: from mailout02.btx.dtag.de (mailout02.btx.dtag.de [194.25.2.150]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA00478 for ; Wed, 24 Sep 1997 14:51:04 -0700 (PDT) Received: from fwd04.btx.dtag.de [194.25.2.164] by mailout02.btx.dtag.de with smtp id 0xDyYh-00014R-00; Wed, 24 Sep 1997 23:01:23 +0200 Received: (053235370-0001(btxid)@[193.159.66.170]) by fwd04.btx.dtag.de with (S3.1.29.1) id ; Wed, 24 Sep 97 22:27 MET DST Message-Id: Date: Wed, 24 Sep 97 22:27 MET DST To: hackers@freebsd.org Subject: Bugfix games/atc X-Mailer: T-Online eMail 2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Sender: 053235370-0001@t-online.de (Klaus-Juergen Wolf) From: Yanestra@t-online.de (Klaus-J. Wolf) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear people, a small bugfix for games/atc. BUG DESCRIPTION: When a plane is heading to 315 degrees and you turn 'r' right, it will start to circle. When a plane is heading to 270 degrees and you turn 'R' right, it will start to circle. BUGFIX: File: /usr/src/games/atc/input.c --cut-here-- 413c413 < if (p.new_dir > MAXDIR) --- > if (p.new_dir >= MAXDIR) 431c431 < if (p.new_dir > MAXDIR) --- > if (p.new_dir >= MAXDIR) --cut-here-- Thanx a lot. Ciao jay From owner-freebsd-hackers Wed Sep 24 15:05:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA01511 for hackers-outgoing; Wed, 24 Sep 1997 15:05:37 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA01503 for ; Wed, 24 Sep 1997 15:05:32 -0700 (PDT) Received: (qmail 4564 invoked by uid 1000); 24 Sep 1997 22:05:53 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092397 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199709241855.UAA01561@yedi.iaf.nl> Date: Wed, 24 Sep 1997 15:05:53 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wilko Bulte Subject: Re: DPT Firmware Problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wilko Bulte; On 24-Sep-97 you wrote: ... > Simon, > > Could you get me more info on the problems with the StorageWorks > shelves? > I work in DEC Storage engineering and might be able to help you with > this > problem. What shelves do you use? WHich disks? Revisions etc. > > I assume things like the Shelve OK jumpers are set correctly? > > Wilko You are a godsend! We have two versions with two (related?) problems: The SE DPT 3334UW, with firmware 7L0, is connected to what DPT calls the 9W tower. It is a steel box with 7 slots and room above for two more 5.25" devices. It has two large power supplies shaped like a large wedge. The P/S each has a large handle made of rolled steel. In these, there are two enclosure light in the top-right corner; A green power light and a yellow fault light. With the 7L0 firmware, this light is ALWAYS on. Also, the disk modules (4GB Baracuda with 528 bytes sectors), will blink the amber light on the drive on and off constantly. Power on sequence makes no difference. This is the easy, less important one. The Differential cabinet is a different story. It is composed of a disk card cage which has 8 slots, for 8 drives, in an enclosue of our own design (please do not ask why :-). In the back there is an arrangement that takes three power supplies (DEC provided, in what appears a disk module enclosure). They are ganged together with a small power bus board that came from DEC. The bus is split into 2, 4 drives (each) busses. There is a SE terminator module on the back of this backplane. There is no jumper block in the other socket. Each bus goes, via 68 pin high density connector to a small (DEC provided) board that has a differential plug on the other side. The board is shaped like a 3.5" disk drive with a power + SE signal connectors on hte inside and 68 pin differential on the outside. These external connectors are connected to a 3334UWD DPT, one bus per channel. The symptoms are most annoying. The DPT will see only one half of the cabinet. Typically the right hand side. The only way to see the whole cabinet is to bypass the DIFF-SE boards and plug a SE controller directly into the backplane. This works perfectly. One more thing; the little board that generates the ``shelf good'' from the different inputs is missing. I really do not know how/what our hardware guys did. I asked for documentation and have seen none. If you have access to these douments, I will LOVE to have them. Thanx for any help you can render. --- Sincerely Yours, (Sent on 24-Sep-97, 12:19:22 by XF-Mail) Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313 From owner-freebsd-hackers Wed Sep 24 15:15:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02237 for hackers-outgoing; Wed, 24 Sep 1997 15:15:42 -0700 (PDT) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02217; Wed, 24 Sep 1997 15:15:38 -0700 (PDT) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id PAA17105; Wed, 24 Sep 1997 15:11:14 -0700 (PDT) Date: Wed, 24 Sep 1997 15:11:13 -0700 (PDT) From: Murray Stokely To: Luigi Rizzo cc: "Jamil J. Weatherbee" , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709230449.GAA18356@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk SMC EtherPower II cards (10/100bt) have optional boot eproms for about $25. (the cards themselves are about $70). On Tue, 23 Sep 1997, Luigi Rizzo wrote: % Just curious, did you manage to boot from an eprom with 100Mbit % cards ? Last time I tried this was only possible with 10Mbit cards, % except the obvious option (one 10-mbit card with the boot rom, one % 100-mbit which supports the real traffic). % % > easily setting up diskless workstations in the installation, because there % > are a different set of things that need to be done on the master server, % % what I have is a script which clones the root partition by making a % small set of changes and symlinks where needed. Murray Stokely From owner-freebsd-hackers Wed Sep 24 15:41:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA04035 for hackers-outgoing; Wed, 24 Sep 1997 15:41:50 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA04021; Wed, 24 Sep 1997 15:41:42 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA07796 (5.67b/IDA-1.5); Thu, 25 Sep 1997 00:41:49 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id AAA17890; Thu, 25 Sep 1997 00:31:04 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709242231.AAA17890@yedi.iaf.nl> Subject: Re: DPT Firmware Problem To: Shimon@i-Connect.Net (Simon Shapiro) Date: Thu, 25 Sep 1997 00:31:04 +0200 (MET DST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Sep 24, 97 03:05:53 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote... > > Hi Wilko Bulte; On 24-Sep-97 you wrote: > > ... > > > Simon, > > > > Could you get me more info on the problems with the StorageWorks > > shelves? > > I work in DEC Storage engineering and might be able to help you with > > this > > problem. What shelves do you use? WHich disks? Revisions etc. > > > > I assume things like the Shelve OK jumpers are set correctly? > > > > Wilko > > You are a godsend! [snip] For the list readers: we've taken the discussion offline, no need to flood the lists with this. A summary will be posted when appropriate Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Wed Sep 24 16:54:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA08587 for hackers-outgoing; Wed, 24 Sep 1997 16:54:41 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA08576 for ; Wed, 24 Sep 1997 16:54:37 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id QAA28723; Wed, 24 Sep 1997 16:54:21 -0700 (MST) From: Terry Lambert Message-Id: <199709242354.QAA28723@usr03.primenet.com> Subject: Re: Raise your hand if you know how to make this work. To: julian@whistle.com (Julian Elischer) Date: Wed, 24 Sep 1997 23:54:20 +0000 (GMT) Cc: jamil@counterintelligence.ml.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Sep 24, 97 01:34:25 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > there is a function to do this for you > it's rather trivial. > check clock.c > and see how the PCAUDIO device uses this to get itself > called 16000 times per second.. Note: this is about twice as fast as the standard clock can go; at the highest divider, it's only capable of 8192 interrupts a second. 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-hackers Wed Sep 24 16:58:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA08879 for hackers-outgoing; Wed, 24 Sep 1997 16:58:46 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA08854 for ; Wed, 24 Sep 1997 16:58:41 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id QAA29468; Wed, 24 Sep 1997 16:58:37 -0700 (MST) From: Terry Lambert Message-Id: <199709242358.QAA29468@usr03.primenet.com> Subject: Re: crypt() returning an error... To: brandon@roguetrader.com (Brandon Gillespie) Date: Wed, 24 Sep 1997 23:58:37 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Brandon Gillespie" at Sep 24, 97 12:06:29 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The man page on crypt() states that a NULL will be returned instead of a > pointer to a string, if an error occurred. The MD5 crypt does not follow > this, however DES crypt does. Furthermore, in the attempt to hunt out a > 'standard' for handling error codes, I have checked how other crypt() > implementations function. OpenBSD for some unknown reason returns the > string: > > ":" > > Where Digital Unix also returns a NULL, as does Unixware--however their > manual pages do not specify NULL as a valid return value. Forget that; we want to know how you are making a straight MD5 hash cause an error in the first place... 8-) 8-). > crypt("", "") > > With MD5 will actually return an encrypted value, with a zero-length salt. > After my changes, this will return a NULL instead. > > Anybody forsee any problems with this? I do not, but I figured I would > bring it up... You should wrapper this; I don't know if "crypt" is enough of a wrapper. 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-hackers Wed Sep 24 17:24:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10490 for hackers-outgoing; Wed, 24 Sep 1997 17:24:48 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10485 for ; Wed, 24 Sep 1997 17:24:44 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id SAA07530; Wed, 24 Sep 1997 18:25:43 -0600 (MDT) Date: Wed, 24 Sep 1997 18:25:42 -0600 (MDT) From: Brandon Gillespie To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: crypt() returning an error... In-Reply-To: <199709242358.QAA29468@usr03.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Sep 1997, Terry Lambert wrote: > > The man page on crypt() states that a NULL will be returned instead of a > > pointer to a string, if an error occurred. The MD5 crypt does not follow > > this, however DES crypt does. Furthermore, in the attempt to hunt out a > > 'standard' for handling error codes, I have checked how other crypt() > > implementations function. OpenBSD for some unknown reason returns the > > string: > > > > ":" > > > > Where Digital Unix also returns a NULL, as does Unixware--however their > > manual pages do not specify NULL as a valid return value. Actually, I mislead you here..both of these crypt implementations will always return a valid string--it simply may be zero-length if the salt is bogus.. > Forget that; we want to know how you are making a straight MD5 hash > cause an error in the first place... 8-) 8-). Well, what should... crypt("", "$MD5$$") return? (er, make that $1$ with the current crypt) > > With MD5 will actually return an encrypted value, with a zero-length salt. > > After my changes, this will return a NULL instead. > > > > Anybody forsee any problems with this? I do not, but I figured I would > > bring it up... > > You should wrapper this; I don't know if "crypt" is enough of a wrapper. hrm, wrapper for what purpose? The code I have now crypt is actually simply a wrapper for whichever algorithm is used.. it looks at the initial token and calls another function specific to that algorithm, so all of the following are valid results: $MD5$salt$passwd $SHS$salt$passwd $BLF$salt$XX$passwd (des style results are also possible) Some of the situations where an error should be raised is if somebody is explicitly trying to use an algorithm that is recognized, but is not enabled (such as using the Extended DES format). -Brandon From owner-freebsd-hackers Wed Sep 24 17:25:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10534 for hackers-outgoing; Wed, 24 Sep 1997 17:25:38 -0700 (PDT) Received: from aretha.informatik.uni-siegen.de (aretha.informatik.uni-siegen.de [141.99.92.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10526; Wed, 24 Sep 1997 17:25:34 -0700 (PDT) From: 12932736@31182.com Received: from paradox.informatik.uni-siegen.de (paradox.informatik.uni-siegen.de [141.99.216.12]) by aretha.informatik.uni-siegen.de (Mailhost) with ESMTP id CAA22475; Thu, 25 Sep 1997 02:14:02 +0200 (MET DST) Received: from www.informatik.uni-siegen.de (211.new-york-27.ny.dial-access.att.net [12.68.134.211]) by paradox.informatik.uni-siegen.de (8.8.5/8.8.5) with SMTP id CAA03583; Thu, 25 Sep 1997 02:04:46 +0200 (MET DST) Received: from postmaster232432422@mailexcite.com by aol.com (8.8.5/8.6.5) with SMTP id GAA00670 for <>; Sat, 31 May 1997 17:03:26 -0600 (EST) Date: Sat, 31 May 97 17:03:26 EST To: Friend@public.com Subject: 100 Free Sex Channels When U Join..... Message-ID: <8123123234237736128736.com> Reply-To: 12314231232432234122122@informatik.uni-siegen.de Comments: Authenticated sender is <1321232312543232132222222> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Click Here http://www.schoolgirlz.com All Free When U Join! Watch 6 Channels At Once!!! 110 WILD XXX RATED LIVE CHANNELS 2 ALL BLONDE CHANNELS 2 MULTIPLE GIRL CHANNELS 2 CHANNELS OF REDHEADS AND BRUNNETTES 1 ALL BLACK CHANNEL - 1 INTERNATIONAL GIRLS FROM AROUND THE W0RLD 2 TEEN CHANNELS (18 AND 19 YR OLD BABES) - 4 CHANNELS REAL SEX SHOWS-MALE/FEMALE-LESBIAN) http://www.schoolgirlz.com From owner-freebsd-hackers Wed Sep 24 17:35:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA11080 for hackers-outgoing; Wed, 24 Sep 1997 17:35:48 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA11075 for ; Wed, 24 Sep 1997 17:35:44 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id RAA04922; Wed, 24 Sep 1997 17:35:39 -0700 (MST) From: Terry Lambert Message-Id: <199709250035.RAA04922@usr03.primenet.com> Subject: Re: crypt() returning an error... To: brandon@roguetrader.com (Brandon Gillespie) Date: Thu, 25 Sep 1997 00:35:38 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Brandon Gillespie" at Sep 24, 97 06:25:42 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > You should wrapper this; I don't know if "crypt" is enough of a wrapper. > > hrm, wrapper for what purpose? The code I have now crypt is actually > simply a wrapper for whichever algorithm is used.. it looks at the initial > token and calls another function specific to that algorithm, so all of the > following are valid results: It's valid to MD5 hash a zer length string; if you make the MD5 hash unusable for that purpose with the change, then it's broken. The wrapper is the code that leaves the MD5 code otherwise usable for zero lenth strings. I'm not sure that I'd disallow hashing zero lenth passwords to non-NULL password values. It seems like a feture, to me, actually, so crypt() might not be where you want the wrapper. Certainly, you don't want the wrapper at the MD5 code in either case... that's all I meant to say. 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-hackers Wed Sep 24 17:52:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA12099 for hackers-outgoing; Wed, 24 Sep 1997 17:52:28 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA12087 for ; Wed, 24 Sep 1997 17:52:22 -0700 (PDT) Received: from argus.tfs.net (pm3-p42.tfs.net [206.154.183.234]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id SAA01794 for ; Wed, 24 Sep 1997 18:50:49 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id TAA00700 for freebsd-hackers@freebsd.org; Wed, 24 Sep 1997 19:52:10 -0500 (CDT) From: Jim Bryant Message-Id: <199709250052.TAA00700@argus.tfs.net> Subject: vt420 terminal To: freebsd-hackers@freebsd.org Date: Wed, 24 Sep 1997 19:52:09 -0500 (CDT) Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk excuse me if this is not the place to ask... i just got this terminal minutes ago, it does work, but it seems to not have a db-25 connector, but has two of the wierd DEC-style modular connectors, one for each session, or one for both sessions and the other for the printer... questions: 1). where can i obtain ready made DEC-modular <-> EIA DB-9/25 cables? 2). where can i obtain DEC-modular connectors for making my own cables? 3). most important: what is the pinout for the DEC-modular connector? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Wed Sep 24 18:43:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA14895 for hackers-outgoing; Wed, 24 Sep 1997 18:43:21 -0700 (PDT) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA14889 for ; Wed, 24 Sep 1997 18:43:18 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.7/8.8.7) with SMTP id VAA20197; Wed, 24 Sep 1997 21:41:37 -0400 (EDT) Date: Wed, 24 Sep 1997 21:41:36 -0400 (EDT) From: "Matthew N. Dodd" To: "Brian J. McGovern" cc: jacques@wired.ctech.ac.za, hackers@FreeBSD.ORG Subject: RE: Quota In-Reply-To: <199709231212.IAA14497@spoon.beta.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, Brian J. McGovern wrote: > set up user foo's quotas, I can say: > > edquota -p foo bar > > and it will pull up bar's quota list, using foo's defaults. I wrote a set of command line utils for quota manipulation that you may find useful. ftp://ftp.jurai.net/users/winter/setquota-0.1.tar.gz or in port format ftp://ftp.jurai.net/users/winter/setquota.portball.tgz Have fun. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Wed Sep 24 18:44:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA14990 for hackers-outgoing; Wed, 24 Sep 1997 18:44:40 -0700 (PDT) Received: from stadtbus.wuerzburg.de (root@stadtbus.wuerzburg.de [194.122.167.4]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA14982 for ; Wed, 24 Sep 1997 18:44:35 -0700 (PDT) From: 12932736@31182.com Received: from stadtbus.wuerzburg.de(really [12.68.134.211]) by stadtbus.wuerzburg.de via smail with smtp id for ; Thu, 25 Sep 1997 02:02:32 +0200 (MEST) (Smail-3.2 1996-Jul-4 #1 built 1996-Nov-18) Received: from postmaster232432422@mailexcite.com by aol.com (8.8.5/8.6.5) with SMTP id GAA00670 for <>; Sat, 31 May 1997 17:03:26 -0600 (EST) Date: Sat, 31 May 97 17:03:26 EST To: Friend@public.com Subject: 100 Free Sex Channels When U Join..... Message-ID: <8123123234237736128736.com> Reply-To: 12314231232432234122122 Comments: Authenticated sender is <1321232312543232132222222> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Click Here http://www.schoolgirlz.com All Free When U Join! Watch 6 Channels At Once!!! 110 WILD XXX RATED LIVE CHANNELS 2 ALL BLONDE CHANNELS 2 MULTIPLE GIRL CHANNELS 2 CHANNELS OF REDHEADS AND BRUNNETTES 1 ALL BLACK CHANNEL - 1 INTERNATIONAL GIRLS FROM AROUND THE W0RLD 2 TEEN CHANNELS (18 AND 19 YR OLD BABES) - 4 CHANNELS REAL SEX SHOWS-MALE/FEMALE-LESBIAN) http://www.schoolgirlz.com From owner-freebsd-hackers Wed Sep 24 18:44:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA15001 for hackers-outgoing; Wed, 24 Sep 1997 18:44:44 -0700 (PDT) Received: from stadtbus.wuerzburg.de (root@stadtbus.wuerzburg.de [194.122.167.4]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA14988; Wed, 24 Sep 1997 18:44:38 -0700 (PDT) From: 12932736@31182.com Received: from stadtbus.wuerzburg.de(really [12.68.134.211]) by stadtbus.wuerzburg.de via smail with smtp id for ; Thu, 25 Sep 1997 02:02:32 +0200 (MEST) (Smail-3.2 1996-Jul-4 #1 built 1996-Nov-18) Received: from postmaster232432422@mailexcite.com by aol.com (8.8.5/8.6.5) with SMTP id GAA00670 for <>; Sat, 31 May 1997 17:03:26 -0600 (EST) Date: Sat, 31 May 97 17:03:26 EST To: Friend@public.com Subject: 100 Free Sex Channels When U Join..... Message-ID: <8123123234237736128736.com> Reply-To: 12314231232432234122122 Comments: Authenticated sender is <1321232312543232132222222> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Click Here http://www.schoolgirlz.com All Free When U Join! Watch 6 Channels At Once!!! 110 WILD XXX RATED LIVE CHANNELS 2 ALL BLONDE CHANNELS 2 MULTIPLE GIRL CHANNELS 2 CHANNELS OF REDHEADS AND BRUNNETTES 1 ALL BLACK CHANNEL - 1 INTERNATIONAL GIRLS FROM AROUND THE W0RLD 2 TEEN CHANNELS (18 AND 19 YR OLD BABES) - 4 CHANNELS REAL SEX SHOWS-MALE/FEMALE-LESBIAN) http://www.schoolgirlz.com From owner-freebsd-hackers Wed Sep 24 18:59:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA15813 for hackers-outgoing; Wed, 24 Sep 1997 18:59:21 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA15801; Wed, 24 Sep 1997 18:59:14 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id SAA00759; Wed, 24 Sep 1997 18:56:36 -0700 (PDT) Date: Wed, 24 Sep 1997 18:56:36 -0700 (PDT) From: "Jamil J. Weatherbee" To: Murray Stokely cc: Luigi Rizzo , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Are these known to boot freebsd using bootp and tftp (i.e. have you tried it yourself or a close friend). I ask because most cards can do this just not with freebsd off the shelf. On Wed, 24 Sep 1997, Murray Stokely wrote: > SMC EtherPower II cards (10/100bt) have optional boot eproms for about > $25. (the cards themselves are about $70). > > On Tue, 23 Sep 1997, Luigi Rizzo wrote: > % Just curious, did you manage to boot from an eprom with 100Mbit > % cards ? Last time I tried this was only possible with 10Mbit cards, > % except the obvious option (one 10-mbit card with the boot rom, one > % 100-mbit which supports the real traffic). > % > % > easily setting up diskless workstations in the installation, because there > % > are a different set of things that need to be done on the master server, > % > % what I have is a script which clones the root partition by making a > % small set of changes and symlinks where needed. > > Murray Stokely > > From owner-freebsd-hackers Wed Sep 24 19:17:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA16678 for hackers-outgoing; Wed, 24 Sep 1997 19:17:14 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA16667 for ; Wed, 24 Sep 1997 19:17:09 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id TAA00780; Wed, 24 Sep 1997 19:15:44 -0700 (PDT) Date: Wed, 24 Sep 1997 19:15:43 -0700 (PDT) From: "Jamil J. Weatherbee" To: Terry Lambert cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: Raise your hand if you know how to make this work. In-Reply-To: <199709242354.QAA28723@usr03.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If we are still talking about an 8253 I know you to be wrong here, the frequency varies like 1.9MHz/(1-65535). On Wed, 24 Sep 1997, Terry Lambert wrote: > > there is a function to do this for you > > it's rather trivial. > > check clock.c > > and see how the PCAUDIO device uses this to get itself > > called 16000 times per second.. > > Note: this is about twice as fast as the standard clock can go; at > the highest divider, it's only capable of 8192 interrupts a second. > > > 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-hackers Wed Sep 24 19:17:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA16743 for hackers-outgoing; Wed, 24 Sep 1997 19:17:55 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA16734 for ; Wed, 24 Sep 1997 19:17:52 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id TAA00784; Wed, 24 Sep 1997 19:17:34 -0700 (PDT) Date: Wed, 24 Sep 1997 19:17:34 -0700 (PDT) From: "Jamil J. Weatherbee" To: jbryant@tfs.net cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vt420 terminal In-Reply-To: <199709250052.TAA00700@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk What the heck is a DEC-style modular connector (who manufactures the connector?) On Wed, 24 Sep 1997, Jim Bryant wrote: > excuse me if this is not the place to ask... > > i just got this terminal minutes ago, it does work, but it seems to > not have a db-25 connector, but has two of the wierd DEC-style modular > connectors, one for each session, or one for both sessions and the > other for the printer... > > questions: > > 1). where can i obtain ready made DEC-modular <-> EIA DB-9/25 > cables? > > 2). where can i obtain DEC-modular connectors for making my > own cables? > > 3). most important: what is the pinout for the DEC-modular > connector? > > jim > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > ------------------------------------------------------------------------------ > Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW > voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant > ------------------------------------------------------------------------------ > HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ > From owner-freebsd-hackers Wed Sep 24 19:39:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA18055 for hackers-outgoing; Wed, 24 Sep 1997 19:39:56 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18048 for ; Wed, 24 Sep 1997 19:39:53 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id TAA06463; Wed, 24 Sep 1997 19:39:46 -0700 (PDT) Date: Wed, 24 Sep 1997 19:39:46 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199709250239.TAA06463@kithrup.com> To: hackers@freebsd.org Subject: Re: r-cmds and DNS and /etc/host.conf In-Reply-To: <199709241008.DAA06292.kithrup.freebsd.hackers@dog.farm.org> Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709241008.DAA06292.kithrup.freebsd.hackers@dog.farm.org> you write: >the lookups occur only if .rhosts is present. So, it's in >/usr/src/lib/libc/net/rcmd.c:iruserok() or deeper (_not_ ruserok() - >this one tests by IP address). Okay, I tried this here, as well: garth: running 2.2-GAMMA No local nameserver /etc/hosts has LAN hosts, and localhost, and nothing else /etc/host.conf has "hosts" followed by "bind" /etc/hosts.equiv has "#kithrup.com" ~sef/.rhosts has "kithrup.com" and "kithrup" /etc/resolv.conf has "domain kithrup.com", and my ISP as nameservers kithrup: doesn't matter, I think I started up two tcpdump's on garth (one for lo0, and one for "host garth and not port login and not port klogin" on de0). Then, from kithrup, I did: rlogin -KL8 garth No traffic from either tcpdump. I verified that iruserok() is the same for -current and garth's version. So I'm afraid I still can't reproduce it, although I am trying. Any suggestions to changes to make to my setup (other than installing a newer version of the OS :))? From owner-freebsd-hackers Wed Sep 24 19:43:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA18279 for hackers-outgoing; Wed, 24 Sep 1997 19:43:33 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18271 for ; Wed, 24 Sep 1997 19:43:30 -0700 (PDT) Received: from default (user21.kincyb.com [206.17.159.21]) by netroplex.com (8.8.5/8.8.2) with ESMTP id TAA20024 for ; Wed, 24 Sep 1997 19:44:36 -0700 (PDT) Message-ID: <3429CEE3.97C55CD8@pagecreators.com> Date: Wed, 24 Sep 1997 19:39:32 -0700 From: Rod Ebrahimi X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Pentium II X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We are purchasing a Dell Server on a PentiumII 233 and plan to install 2.2.1, anyone know how well the new PIIs work with FreeBSD? Thank you From owner-freebsd-hackers Wed Sep 24 19:48:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA18613 for hackers-outgoing; Wed, 24 Sep 1997 19:48:08 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18608 for ; Wed, 24 Sep 1997 19:48:05 -0700 (PDT) Received: from default (user21.kincyb.com [206.17.159.21]) by netroplex.com (8.8.5/8.8.2) with ESMTP id TAA20102 for ; Wed, 24 Sep 1997 19:49:12 -0700 (PDT) Message-ID: <3429CFF6.30E9BB@pagecreators.com> Date: Wed, 24 Sep 1997 19:44:07 -0700 From: Rod Ebrahimi X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Pentium II X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please ignore my previous message... Sorry From owner-freebsd-hackers Wed Sep 24 20:23:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA20348 for hackers-outgoing; Wed, 24 Sep 1997 20:23:44 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA20341 for ; Wed, 24 Sep 1997 20:23:41 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA03035; Wed, 24 Sep 1997 20:24:03 -0700 (PDT) To: Rod Ebrahimi cc: hackers@FreeBSD.ORG Subject: Re: Pentium II In-reply-to: Your message of "Wed, 24 Sep 1997 19:39:32 PDT." <3429CEE3.97C55CD8@pagecreators.com> Date: Wed, 24 Sep 1997 20:24:02 -0700 Message-ID: <3032.875157842@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We are purchasing a Dell Server on a PentiumII 233 and plan to install > 2.2.1, anyone know how well the new PIIs work with FreeBSD? Just tested a dual PII system the other day (based on the Tyan SMP MB) and it worked just fine! Very fast. Jordan From owner-freebsd-hackers Wed Sep 24 21:37:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA24120 for hackers-outgoing; Wed, 24 Sep 1997 21:37:11 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA24115 for ; Wed, 24 Sep 1997 21:37:09 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id WAA08465; Wed, 24 Sep 1997 22:38:06 -0600 (MDT) Date: Wed, 24 Sep 1997 22:38:05 -0600 (MDT) From: Brandon Gillespie To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: crypt() returning an error... In-Reply-To: <199709250035.RAA04922@usr03.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Terry Lambert wrote: > > > > hrm, wrapper for what purpose? The code I have now crypt is actually > > simply a wrapper for whichever algorithm is used.. it looks at the initial > > token and calls another function specific to that algorithm, so all of the > > following are valid results: > > It's valid to MD5 hash a zer length string; if you make the MD5 hash > unusable for that purpose with the change, then it's broken. The > wrapper is the code that leaves the MD5 code otherwise usable for > zero lenth strings. Er, sorry, my example was bad--I was actually saying what would you do with a zero-length salt, not password... > I'm not sure that I'd disallow hashing zero lenth passwords to non-NULL > password values. It seems like a feture, to me, actually, so crypt() > might not be where you want the wrapper. Certainly, you don't want the > wrapper at the MD5 code in either case... that's all I meant to say. Ahh :) -Brandon From owner-freebsd-hackers Wed Sep 24 21:42:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA24352 for hackers-outgoing; Wed, 24 Sep 1997 21:42:53 -0700 (PDT) Received: from destiny.erols.com (root@destiny.erols.com [207.96.73.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA24342; Wed, 24 Sep 1997 21:42:46 -0700 (PDT) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.7/8.6.12) with SMTP id AAA27317; Thu, 25 Sep 1997 00:42:04 -0400 (EDT) Date: Thu, 25 Sep 1997 00:42:03 -0400 (EDT) From: John Dowdal To: "Jamil J. Weatherbee" cc: Murray Stokely , Luigi Rizzo , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Sep 1997, Jamil J. Weatherbee wrote: > > > Are these known to boot freebsd using bootp and tftp (i.e. have you tried > it yourself or a close friend). I ask because most cards can do this just > not with freebsd off the shelf. I'm currently doing this with a disposable NE2000 clone and the nb8390.com which is in /usr/mdec. There is also the .bin file which I haven't ever tried to burn into a rom; I'm netbooting this machine, because it has a 500MB hard drive which is dedicated to windoze. If you have specific quesitons I'll answer them. --------------------- John Dowdal jdowdal@destiny.erols.com I Want My/I Want My NetTV From owner-freebsd-hackers Wed Sep 24 21:48:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA24592 for hackers-outgoing; Wed, 24 Sep 1997 21:48:55 -0700 (PDT) Received: from silent.darkening.com (nonxstnt@iskh122.haninge.kth.se [130.237.83.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA24587 for ; Wed, 24 Sep 1997 21:48:48 -0700 (PDT) Received: from localhost (nonxstnt@localhost) by silent.darkening.com (8.8.7/8.8.7) with SMTP id GAA25467 for ; Thu, 25 Sep 1997 06:50:08 +0200 (CEST) X-Authentication-Warning: silent.darkening.com: nonxstnt owned process doing -bs Date: Thu, 25 Sep 1997 06:50:08 +0200 (CEST) From: nobody To: freebsd-hackers@freebsd.org Subject: ee taking up weird cpu amount. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id VAA24588 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 18863 99.1 1.2 388 732 p3- R 6:59PM 673:39.41 ee /etc/pw.018862 I've had this happen several times now, where I would login to my system and see ee taking up 99% CPU (on a P2/266). As you can see, this is some guy doing chfn I guess. This process has been on for 12 hours now though. Any known problems with ee? (besides the fact that Im about to rename it and put joe in its place). This is on a 2.2-STABLE system. (last CVSup'd about a week ago). --- thomas strömberg . system admin, royal institute of technology (stockholm) nobody@darkening.com . irc:nobody@EFnet . talk:nonxstnt@silent.darkening.com real coders don't use comments. It was hard to write; it should be hard to read From owner-freebsd-hackers Wed Sep 24 22:09:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA25467 for hackers-outgoing; Wed, 24 Sep 1997 22:09:54 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA25457 for ; Wed, 24 Sep 1997 22:09:45 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id WAA19928; Wed, 24 Sep 1997 22:15:49 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id WAA16196; Wed, 24 Sep 1997 22:05:02 -0700 (PDT) Date: Wed, 24 Sep 1997 22:05:02 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199709250505.WAA16196@dog.farm.org> To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Cc: freebsd-hackers@freebsd.org Subject: Re: ISDN Modems Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > To be honest with you I thought about this for a few months, If you in the > US the best solution is something like an Ascend Pipeline 50 router (no > firewall) ($599), with a crossover (included) to an inexpensive NE2000 > card ($40). This is about twice as expensive as a Motorola Bitsurfer > (~$300) and doesn't have the analog ports (but if you want isdn for making Actually, I got mine for $100 - some on-line auction had Mac version (refurbished) for this price. (what's the difference between Mac version and PC version? well, you got MacOS setup program (for those who can't type AT commands ;-) and MacOS terminal software. Plus a cable.) A friend has dedicated P50-to-P50 link to ISP. (both ends running the latest software revision from ftp.ascend.com). It shows some weird problems when doing some kinds of transfers (like outgoing scp) from his 2.2.2-R box. Turning off TCP extensions or fiddling with MTU helped, I think; but I am not very sure. So, it looks like Ascend still cannot get IP right. I played with Cisco 776, and I love it; it does all the voice stuff you can think about (it's mini-PBX), does ip filtering, NAT (actually PAT - you can have only 1 external address, but you can map different machines to different ports on it), DHCP, and has unbeatable amount of blinkenlights. You can config your router from DTMF phone. It's more expensive than Ascend, though (used P50 is ~$400). Don't buy 77x (with built-in 4-port hub), as it's arp table has 4 entries. Buy 76x. > voice calls your a wacko anyway). The reason I was willing to pay the > extra $300 were: A. ping time to peer with router = 30ms, B. ping time to > peer with Serial based internal card or external = 100ms (If youv'e ever my Ascend and Cisco ping times are 30ms, Bitsurfr (115200 FIFO) gives 75ms. -- "Books: You can't grep dead trees." -- Dion Favors(?) From owner-freebsd-hackers Wed Sep 24 23:28:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA28930 for hackers-outgoing; Wed, 24 Sep 1997 23:28:29 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA28922 for ; Wed, 24 Sep 1997 23:28:25 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id QAA11202; Thu, 25 Sep 1997 16:28:13 +1000 (EST) Date: Thu, 25 Sep 1997 16:28:12 +1000 (EST) From: "Daniel O'Callaghan" To: nobody cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, nobody wrote: > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 18863 99.1 1.2 388 732 p3- R 6:59PM 673:39.41 ee > /etc/pw.018862 > > I've had this happen several times now, where I would login to my system > and see ee taking up 99% CPU (on a P2/266). As you can see, this is some > guy doing chfn I guess. This process has been on for 12 hours now though. Kill the process. The vty has been disconnected without logging out, so ee goes into a loop. vi and pico do the same thing. Danny From owner-freebsd-hackers Thu Sep 25 00:20:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA01996 for hackers-outgoing; Thu, 25 Sep 1997 00:20:51 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA01989 for ; Thu, 25 Sep 1997 00:20:49 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id AAA09438; Thu, 25 Sep 1997 00:20:47 -0700 (MST) From: Terry Lambert Message-Id: <199709250720.AAA09438@usr03.primenet.com> Subject: Re: vt420 terminal To: jbryant@tfs.net Date: Thu, 25 Sep 1997 07:20:46 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199709250052.TAA00700@argus.tfs.net> from "Jim Bryant" at Sep 24, 97 07:52:09 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i just got this terminal minutes ago, it does work, but it seems to > not have a db-25 connector, but has two of the wierd DEC-style modular > connectors, one for each session, or one for both sessions and the > other for the printer... > > questions: > > 1). where can i obtain ready made DEC-modular <-> EIA DB-9/25 > cables? DEC. > 2). where can i obtain DEC-modular connectors for making my > own cables? You can either get them from Digikey, or you can break off the keying/locking piect from a normal (DB12) phone connector. We used Digikey parts for the CS lab at Weber State University. > 3). most important: what is the pinout for the DEC-modular > connector? It's in the manual for the terminal. But the multisession commands are not, so if you expect to use them, expect to have to use a line monitor between a DEC terminal server and the terminal itself. 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-hackers Thu Sep 25 00:27:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02321 for hackers-outgoing; Thu, 25 Sep 1997 00:27:05 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02309 for ; Thu, 25 Sep 1997 00:27:01 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id AAA09638; Thu, 25 Sep 1997 00:23:51 -0700 (MST) From: Terry Lambert Message-Id: <199709250723.AAA09638@usr03.primenet.com> Subject: Re: Raise your hand if you know how to make this work. To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Thu, 25 Sep 1997 07:23:49 +0000 (GMT) Cc: tlambert@primenet.com, julian@whistle.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 24, 97 07:15:43 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Note: this is about twice as fast as the standard clock can go; at > > the highest divider, it's only capable of 8192 interrupts a second. > > If we are still talking about an 8253 I know you to be wrong here, the > frequency varies like 1.9MHz/(1-65535). This information is from the Linux tier code and from the FreeBSD clock divider code for the PC audio driver, and not from the chipset documentation, so I'm prepared to be wrong (along with the comments in both these drivers). 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-hackers Thu Sep 25 00:30:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02491 for hackers-outgoing; Thu, 25 Sep 1997 00:30:55 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02483 for ; Thu, 25 Sep 1997 00:30:51 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id AAA09884; Thu, 25 Sep 1997 00:27:37 -0700 (MST) From: Terry Lambert Message-Id: <199709250727.AAA09884@usr03.primenet.com> Subject: Re: vt420 terminal To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Thu, 25 Sep 1997 07:27:36 +0000 (GMT) Cc: jbryant@tfs.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 24, 97 07:17:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What the heck is a DEC-style modular connector (who manufactures the > connector?) Instead of: ,-----. `-----' ,-------------. | | | | | | | | | | | | | | | | `-+-+-+-+-+-+-' It looks like: ,-----. `-----' ,-------------. | | | | | | | | | | | | | | | | `-+-+-+-+-+-+-' This change to the locking tab was made for: "no good reason". 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-hackers Thu Sep 25 00:32:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02585 for hackers-outgoing; Thu, 25 Sep 1997 00:32:47 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02578 for ; Thu, 25 Sep 1997 00:32:44 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id AAA10186; Thu, 25 Sep 1997 00:32:41 -0700 (MST) From: Terry Lambert Message-Id: <199709250732.AAA10186@usr03.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: sef@Kithrup.COM (Sean Eric Fagan) Date: Thu, 25 Sep 1997 07:32:40 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709250239.TAA06463@kithrup.com> from "Sean Eric Fagan" at Sep 24, 97 07:39:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I started up two tcpdump's on garth (one for lo0, and one for "host garth > and not port login and not port klogin" on de0). > > Then, from kithrup, I did: > > rlogin -KL8 garth > > No traffic from either tcpdump. > > I verified that iruserok() is the same for -current and garth's version. > > So I'm afraid I still can't reproduce it, although I am trying. Any > suggestions to changes to make to my setup (other than installing a newer > version of the OS :))? One thing that occurs to me is that I'm using the recommended: set ifaddr 10.10.10.10/0 10.10.11.11/0 0.0.0.0 0.0.0.0 in ppp.conf, but I'm using a class B (192.168.0.0 - 192.168.255.255) instead of a class A (10.0.0.0 - 10.255.255.255) non-routable network as my local network. This shouldn't have this effect, but ...who knows. 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-hackers Thu Sep 25 00:38:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02824 for hackers-outgoing; Thu, 25 Sep 1997 00:38:51 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02819 for ; Thu, 25 Sep 1997 00:38:46 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id AAA11071; Thu, 25 Sep 1997 00:38:45 -0700 (PDT) Message-ID: <19970925003845.29319@hydrogen.nike.efn.org> Date: Thu, 25 Sep 1997 00:38:45 -0700 From: John-Mark Gurney To: FreeBSD Hackers Subject: how to put to structures in one memory area... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well.. I was thinking about the design of the generic bus code.. and wanted to have the generic structure, and then the private bus data... what is the way that you guys suggest it be done? struct bothstructs{ struct generic; struct specific; }; or struct generic { union { struct busa *a; struct busb *b; }bus; }; or struct generic { }; ISAPRIVATE(generic)->specific) or would simply making two allocations be fine?? I don't like the idea of splitting the specific bus data so far away from the generic when it's likely that you will use both... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Thu Sep 25 00:47:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA03218 for hackers-outgoing; Thu, 25 Sep 1997 00:47:41 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA03201 for ; Thu, 25 Sep 1997 00:47:35 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id AAA10411; Thu, 25 Sep 1997 00:42:03 -0700 (MST) From: Terry Lambert Message-Id: <199709250742.AAA10411@usr03.primenet.com> Subject: Re: ee taking up weird cpu amount. To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Thu, 25 Sep 1997 07:41:59 +0000 (GMT) Cc: nonxstnt@darkening.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Daniel O'Callaghan" at Sep 25, 97 04:28:12 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > root 18863 99.1 1.2 388 732 p3- R 6:59PM 673:39.41 ee > > /etc/pw.018862 > > > > I've had this happen several times now, where I would login to my system > > and see ee taking up 99% CPU (on a P2/266). As you can see, this is some > > guy doing chfn I guess. This process has been on for 12 hours now though. > > Kill the process. The vty has been disconnected without logging out, so > ee goes into a loop. vi and pico do the same thing. IMO, this is a bug in HUP processing. I think that HUP should be sent to the process group members from the process group leaders before the tty is revoked, instead of simply erroring out the reads/writes. SVR4, SVR3, SCO Xenix, SCO UNIX, UnixWare, Solaris, SunOS, Fortune, Cubix, Huerikon, Arrete, Unisys UNIX, UNICOS, Linux, Cubix, Intel UNIX, Intel Xenix, PrimeOS, ISC UNIX, Ultrix, OSF/1, OSF/2, Microport UNIX v2, Microport UNIX v3, Altos Xenix and UNIX, Cogent, Coherent, and practically every other UNIX on the planet does this. But FreeBSD does not. Heck, who is to say my interpretaion of POSIX is right and FreeBSD's is wrong (apart from *everyone*else*on*the*planet*, that is...). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Sep 25 01:11:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA04447 for hackers-outgoing; Thu, 25 Sep 1997 01:11:50 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA04441 for ; Thu, 25 Sep 1997 01:11:47 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id BAA20144; Thu, 25 Sep 1997 01:18:02 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id BAA18397; Thu, 25 Sep 1997 01:07:52 -0700 (PDT) Date: Thu, 25 Sep 1997 01:07:52 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199709250807.BAA18397@dog.farm.org> To: sef@Kithrup.COM (Sean Eric Fagan) Cc: freebsd-hackers@freebsd.org Subject: Re: r-cmds and DNS and /etc/host.conf Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709250239.TAA06463@kithrup.com> you wrote: > In article <199709241008.DAA06292.kithrup.freebsd.hackers@dog.farm.org> you write: > >the lookups occur only if .rhosts is present. So, it's in > >/usr/src/lib/libc/net/rcmd.c:iruserok() or deeper (_not_ ruserok() - > >this one tests by IP address). > Okay, I tried this here, as well: > garth: > running 2.2-GAMMA > No local nameserver > /etc/hosts has LAN hosts, and localhost, and nothing else > /etc/host.conf has "hosts" followed by "bind" > /etc/hosts.equiv has "#kithrup.com" > ~sef/.rhosts has "kithrup.com" and "kithrup" > /etc/resolv.conf has "domain kithrup.com", and my ISP as > nameservers so DNS traffic should fo to your ISP... > I started up two tcpdump's on garth (one for lo0, and one for "host garth > and not port login and not port klogin" on de0). > Then, from kithrup, I did: > rlogin -KL8 garth > No traffic from either tcpdump. the traffic should go to your nameserver - so, please run tcpdump one the interface to your ISP (and have your link up, of course!), like ppp0 or tun0... > I verified that iruserok() is the same for -current and garth's version. I think that that code (both rlogin and resolv) hasn't been really touched for at least a year... -- To err is human; but to completely screw things up you have to be root. - Andrew.V.Kovalev@jet.msk.su From owner-freebsd-hackers Thu Sep 25 03:18:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA09687 for hackers-outgoing; Thu, 25 Sep 1997 03:18:05 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA09673 for ; Thu, 25 Sep 1997 03:17:48 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id TAA01162; Thu, 25 Sep 1997 19:45:06 +0930 (CST) Message-Id: <199709251015.TAA01162@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: FreeBSD Hackers Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sat, 20 Sep 1997 12:42:35 +0930." <19970920124235.58941@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Sep 1997 19:45:04 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have the CVS tree here on my system, and I know we've just done a > snap, but I see nothing in the tree to help me determine where, when > or what it is. What do I need to do? cvs co -D src, then build the release as usual. Snaps aren't tagged, as this'd fill the tree with more junk and greatly increase the CTM and CVSup traffic. mike From owner-freebsd-hackers Thu Sep 25 03:19:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA09744 for hackers-outgoing; Thu, 25 Sep 1997 03:19:36 -0700 (PDT) Received: from kerouac.hepcat.org (kerouac.hepcat.org [207.155.93.61]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA09734 for ; Thu, 25 Sep 1997 03:19:30 -0700 (PDT) Received: (from cosmos@localhost) by kerouac.hepcat.org (8.8.5/8.8.5) id DAA00905 for hackers@freebsd.org; Thu, 25 Sep 1997 03:25:33 GMT Message-Id: <199709250325.DAA00905@kerouac.hepcat.org> Subject: thinkpad mouse To: hackers@freebsd.org Date: Thu, 25 Sep 1997 03:25:32 +0000 (GMT) From: Daniel Leeds Reply-to: dleeds@dfacades.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk anyone have an ibm thinkpad 701cs? i cant get the red dot mouse on the keyboard to work under X... what kind of mouse is it... help!! From owner-freebsd-hackers Thu Sep 25 03:54:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA10879 for hackers-outgoing; Thu, 25 Sep 1997 03:54:05 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA10871 for ; Thu, 25 Sep 1997 03:53:49 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id MAA27115 for ; Thu, 25 Sep 1997 12:53:45 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id NAA00834 for freebsd-hackers@freefall.cdrom.com; Thu, 25 Sep 1997 13:00:23 +0200 (MEST) Date: Thu, 25 Sep 1997 13:00:23 +0200 (MEST) From: Christoph Kukulies Message-Id: <199709251100.NAA00834@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: mapping physical (ISA) memory Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Being new to device driver writing I'd like to obtain a few short hints on how to proceed mapping the physical region of a device into the driver's address space. Does the isa_device structure do this for me already? My device has a 16 K block at 0xc8000 (for example) and I want to read some location to verify that the device is there and second to download some data into that memory region. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Thu Sep 25 05:53:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14885 for hackers-outgoing; Thu, 25 Sep 1997 05:53:03 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA14875 for ; Thu, 25 Sep 1997 05:52:57 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id WAA05191; Thu, 25 Sep 1997 22:22:47 +0930 (CST) Message-ID: <19970925222246.03372@lemis.com> Date: Thu, 25 Sep 1997 22:22:46 +0930 From: Greg Lehey To: Mike Smith Cc: FreeBSD Hackers Subject: Re: How do I check out a snapshot? References: <19970920124235.58941@lemis.com> <199709251015.TAA01162@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709251015.TAA01162@word.smith.net.au>; from Mike Smith on Thu, Sep 25, 1997 at 07:45:04PM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 25, 1997 at 07:45:04PM +0930, Mike Smith wrote: >> I have the CVS tree here on my system, and I know we've just done a >> snap, but I see nothing in the tree to help me determine where, when >> or what it is. What do I need to do? > > cvs co -D src, then build the release as usual. Snaps aren't > tagged, as this'd fill the tree with more junk and greatly increase the > CTM and CVSup traffic. Sure. But to repeat the question: I see nothing in the tree to help me determine where, when or what it is. How do I find it out? Greg From owner-freebsd-hackers Thu Sep 25 06:16:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA15703 for hackers-outgoing; Thu, 25 Sep 1997 06:16:51 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA15691 for ; Thu, 25 Sep 1997 06:16:45 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id JAA22515; Thu, 25 Sep 1997 09:16:39 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id HAA05714; Thu, 25 Sep 1997 07:02:10 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id GAA08043; Thu, 25 Sep 1997 06:52:45 -0400 (EDT) Date: Thu, 25 Sep 1997 06:52:45 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709251052.GAA08043@lakes.dignus.com> To: hackers@FreeBSD.ORG, sef@kithrup.com Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In article <199709241008.DAA06292.kithrup.freebsd.hackers@dog.farm.org> you write: > >the lookups occur only if .rhosts is present. So, it's in > >/usr/src/lib/libc/net/rcmd.c:iruserok() or deeper (_not_ ruserok() - > >this one tests by IP address). > > Okay, I tried this here, as well: > > garth: > running 2.2-GAMMA > No local nameserver > /etc/hosts has LAN hosts, and localhost, and nothing else > /etc/host.conf has "hosts" followed by "bind" > /etc/hosts.equiv has "#kithrup.com" > ~sef/.rhosts has "kithrup.com" and "kithrup" > /etc/resolv.conf has "domain kithrup.com", and my ISP as > nameservers > > kithrup: > doesn't matter, I think > > I started up two tcpdump's on garth (one for lo0, and one for "host garth > and not port login and not port klogin" on de0). > > Then, from kithrup, I did: > > rlogin -KL8 garth > > No traffic from either tcpdump. > > I verified that iruserok() is the same for -current and garth's version. > > So I'm afraid I still can't reproduce it, although I am trying. Any > suggestions to changes to make to my setup (other than installing a newer > version of the OS :))? Hmmm... my /etc/resolv.conf on the gateway machine doesn't have my (local) domain name. That is, the gateway machine is named "ponds.dignus.com", but /etc/resolv.conf has: domain vnet.net nameserver 166.82.1.3 nameserver 166.82.1.8 (which is the domain of my ISP and it's two nameservers.) Just to get concrete here, my two machines are called: ponds.dignus.com (the gateway machine) lakes.dignus.com (the internal machine) Also, one difference is that I do have a hosts.equiv on the gateway (ponds): #localhost #my_very_good_friend.domain localhost ponds ponds.dignus.com puddles puddles.dignus.com rivulet rivulet.dignus.com But, I wouldn't expect that to matter... - Dave Rivers - From owner-freebsd-hackers Thu Sep 25 06:16:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA15713 for hackers-outgoing; Thu, 25 Sep 1997 06:16:53 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA15694 for ; Thu, 25 Sep 1997 06:16:47 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id JAA22526; Thu, 25 Sep 1997 09:16:42 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id HAA05727; Thu, 25 Sep 1997 07:09:07 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id GAA08069; Thu, 25 Sep 1997 06:59:41 -0400 (EDT) Date: Thu, 25 Sep 1997 06:59:41 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709251059.GAA08069@lakes.dignus.com> To: sef@Kithrup.COM, tlambert@primenet.com Subject: Re: r-cmds and DNS and /etc/host.conf Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > > I started up two tcpdump's on garth (one for lo0, and one for "host garth > > and not port login and not port klogin" on de0). > > > > Then, from kithrup, I did: > > > > rlogin -KL8 garth > > > > No traffic from either tcpdump. > > > > I verified that iruserok() is the same for -current and garth's version. > > > > So I'm afraid I still can't reproduce it, although I am trying. Any > > suggestions to changes to make to my setup (other than installing a newer > > version of the OS :))? > > One thing that occurs to me is that I'm using the recommended: > > set ifaddr 10.10.10.10/0 10.10.11.11/0 0.0.0.0 0.0.0.0 > > in ppp.conf, but I'm using a class B (192.168.0.0 - 192.168.255.255) > instead of a class A (10.0.0.0 - 10.255.255.255) non-routable network > as my local network. > > This shouldn't have this effect, but ...who knows. Just F.Y.I. I'm using class A (10.0.0.0 - 10.255.255.255) as my local network, and not ppp, but SL/IP with natd. - Dave R. - From owner-freebsd-hackers Thu Sep 25 06:17:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA15748 for hackers-outgoing; Thu, 25 Sep 1997 06:17:06 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA15737 for ; Thu, 25 Sep 1997 06:17:00 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id JAA22535; Thu, 25 Sep 1997 09:16:44 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id HAA05723; Thu, 25 Sep 1997 07:07:35 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id GAA08060; Thu, 25 Sep 1997 06:58:10 -0400 (EDT) Date: Thu, 25 Sep 1997 06:58:10 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709251058.GAA08060@lakes.dignus.com> To: dk+@ua.net, freebsd-hackers@freefall.FreeBSD.org, sef@kithrup.com Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dmitry Kohmanyuk writes: > In article <199709250239.TAA06463@kithrup.com> you wrote: > > In article <199709241008.DAA06292.kithrup.freebsd.hackers@dog.farm.org> you write: > > >the lookups occur only if .rhosts is present. So, it's in > > >/usr/src/lib/libc/net/rcmd.c:iruserok() or deeper (_not_ ruserok() - > > >this one tests by IP address). > > > Okay, I tried this here, as well: > > > garth: > > running 2.2-GAMMA > > No local nameserver > > /etc/hosts has LAN hosts, and localhost, and nothing else > > /etc/host.conf has "hosts" followed by "bind" > > /etc/hosts.equiv has "#kithrup.com" > > ~sef/.rhosts has "kithrup.com" and "kithrup" > > /etc/resolv.conf has "domain kithrup.com", and my ISP as > > nameservers > so DNS traffic should fo to your ISP... > > > I started up two tcpdump's on garth (one for lo0, and one for "host garth > > and not port login and not port klogin" on de0). > > > Then, from kithrup, I did: > > > rlogin -KL8 garth > > > No traffic from either tcpdump. > > the traffic should go to your nameserver - so, > please run tcpdump one the interface to your ISP (and have your link > up, of course!), like ppp0 or tun0... > > > I verified that iruserok() is the same for -current and garth's version. > > I think that that code (both rlogin and resolv) hasn't been really > touched for at least a year... > Well - I just scanned my records.. I originally reported this problem in version 2.1.5 of FreeBSD, on Aug. 16th, 1996. The subject of that message was "Nameserver and 'rlogin' in 2.1.5." it should be in the freebsd-hackers mail archives. But, at that time I thought it was a totally different problem and let it languish. Since it didn't get resolved; particularly when my network situation changed, I brought it back up... - Dave R. - From owner-freebsd-hackers Thu Sep 25 06:31:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA16372 for hackers-outgoing; Thu, 25 Sep 1997 06:31:13 -0700 (PDT) Received: from gdwest.gd.com (gdwest.gd.com [134.120.3.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA16364 for ; Thu, 25 Sep 1997 06:31:11 -0700 (PDT) Received: (from eyfarris@localhost) by gdwest.gd.com (8.6.10/8.6.10) id GAA04872; Thu, 25 Sep 1997 06:33:23 -0700 Date: Thu, 25 Sep 1997 06:33:23 -0700 From: Eblan Y Farris Message-Id: <199709251333.GAA04872@gdwest.gd.com> To: info@pagecreators.com, jkh@time.cdrom.com Subject: Re: Pentium II Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> We are purchasing a Dell Server on a PentiumII 233 and plan to install >> 2.2.1, anyone know how well the new PIIs work with FreeBSD? > >Just tested a dual PII system the other day (based on the Tyan SMP MB) >and it worked just fine! Very fast. > > Jordan Are we talking Intel 440FX chipset or 440LX chipset? The 440LX chipset is very new - ask Dell which chipset you are going to have on the system. There are major differences. Eb Farris, efarris@surfusa.com From owner-freebsd-hackers Thu Sep 25 07:04:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17919 for hackers-outgoing; Thu, 25 Sep 1997 07:04:27 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA17911 for ; Thu, 25 Sep 1997 07:04:22 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA31475; Thu, 25 Sep 1997 07:04:15 -0700 Date: Thu, 25 Sep 1997 07:04:15 -0700 (PDT) From: "Brian N. Handy" To: Daniel Leeds Cc: hackers@FreeBSD.ORG Subject: Re: thinkpad mouse In-Reply-To: <199709250325.DAA00905@kerouac.hepcat.org> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >anyone have an ibm thinkpad 701cs? > >what kind of mouse is it... Well, my TP560 thinks it's one of these: Section "Pointer" Protocol "PS/2" Device "/dev/psm0" Emulate3Buttons Emulate3Timeout 50 EndSection Note you have to enable psm0 in your kernel as well...is it disabled? This entry works well enough I can even use my external 3-button mouse too. happy trails, Brian From owner-freebsd-hackers Thu Sep 25 07:19:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA18822 for hackers-outgoing; Thu, 25 Sep 1997 07:19:17 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA18817 for ; Thu, 25 Sep 1997 07:19:11 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id XAA04104; Thu, 25 Sep 1997 23:46:20 +0930 (CST) Message-Id: <199709251416.XAA04104@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: Mike Smith , FreeBSD Hackers Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Thu, 25 Sep 1997 22:22:46 +0930." <19970925222246.03372@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Sep 1997 23:46:17 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Thu, Sep 25, 1997 at 07:45:04PM +0930, Mike Smith wrote: > >> I have the CVS tree here on my system, and I know we've just done a > >> snap, but I see nothing in the tree to help me determine where, when > >> or what it is. What do I need to do? > > > > cvs co -D src, then build the release as usual. Snaps aren't > > tagged, as this'd fill the tree with more junk and greatly increase the > > CTM and CVSup traffic. > > Sure. But to repeat the question: > > I see nothing in the tree to help me determine where, when or what > it is. > > How do I find it out? You don't. Due to the nature of the distributed CVS repository, there is a window where even the exact time of checkout for the snapshot build might leave you out of sync. The only way around this would be for the snap to be built from a tree directly checked out from the master repository. Jordan does this for the for-CDROM versions, I think. mike From owner-freebsd-hackers Thu Sep 25 07:54:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20397 for hackers-outgoing; Thu, 25 Sep 1997 07:54:14 -0700 (PDT) Received: from earth.nine.ionet.net (earth.nine.ionet.net [206.41.141.50]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20388; Thu, 25 Sep 1997 07:54:08 -0700 (PDT) Received: (from cyoder@localhost) by earth.nine.ionet.net (8.8.5/8.8.5) id JAA26143; Thu, 25 Sep 1997 09:54:06 -0500 (CDT) From: Christopher Yoder Message-Id: <199709251454.JAA26143@earth.nine.ionet.net> Subject: Telnet Questions To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Date: Thu, 25 Sep 1997 09:54:06 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here the problem: I'm trying to telnet from my laptop (FreeBSD-2.2.2) to my home machine (FreeBSD-2.2.2). The route through the network is this: laptop (10BaseT) -> router (Cisco 7513 100BT) -> Netserver (USR Terminal Server) -> Pipeline 50 (ISDN 2B) -> Home Machine (10BaseT). Now the weird stuff.. actually it's not.. If I telnet directly to my home box, the status of the telnet (ie: telnet> status) shows that it's in LINEMODE and Local Flow Control. If I type junk keys as fast as I can, the telnet shows them about 3-4sec's later.. This is very upsetting.. Basically it is, type a few chars, wait, type a few, wait, etc.. Now, if I telnet to a Ultra Sparc running Solaris 2.5 on the same network as the laptop, then telnet over to my home machine it is speedy.. I can type as fast as I want.. The network path is the same as before only it is laptop (10BT) -> Sun (100BT) -> Router -> etc.. I've noticed that when I telnet to the Sun, the status is now: character mode, and local flow control doesn't show up. I'm suspecting this is were the problem is. I'm not suggesting a bug. Is there a setting I'm missing, like a configuration setting? Termcaps perphaps? I've tried to manually set the mode to character when telneting directly to my home machine, and it doesn't seem to help.. By the way, this happens even to FreeBSD->FreeBSD boxes on the same segment of the network. 10BT and 100BT. Any ideas, suggestions or comments would be helpful. Thanks in advance, Christopher P.S. I got X working, just removed the PSM_CHECKSYNC from the kernel. =-------------------------------------------------------------------= Christopher D. Yoder ioNET, Inc. Sr. Systems Administrator/Lead Programmer Oklahoma's Largest ISP Oklahoma City, OK Phone: (405) 270-7015 iam@ionet.net Fax: (405) 270-7055 cyoder@ionet.net http://www.ionet.net/~cyoder/ programmer@ionet.net =-------------------------------------------------------------------= New Favorite Saying: "We only have one life, LIVE IT!" =-------------------------------------------------------------------= From owner-freebsd-hackers Thu Sep 25 08:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21968 for hackers-outgoing; Thu, 25 Sep 1997 08:22:08 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21946 for ; Thu, 25 Sep 1997 08:22:02 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA04359 for ; Fri, 26 Sep 1997 00:49:45 +0930 (CST) Message-Id: <199709251519.AAA04359@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@freebsd.org Subject: ATAPI Zip challenge : aftermath Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 00:49:43 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just to bring some continuity to this story; last week I arranged a loan drive, with which to experiment. After some fruitless initial tinkering, I sent it back as faulty. The replacement arrived today, and it exhibits the same basic behaviour; ie. it no longer looks like an IDE disk at all. It _does_ respond to the ATAPI probe, however they appear to have removed the IDE emulation in current models. This of course means that you can't _boot_ from them anymore, which is a royal pain. It'd still be good if someone were to come forward and offer to add the necessary ATAPI support, of course. 8) mike From owner-freebsd-hackers Thu Sep 25 08:25:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA22164 for hackers-outgoing; Thu, 25 Sep 1997 08:25:06 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA22157 for ; Thu, 25 Sep 1997 08:25:01 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA04395; Fri, 26 Sep 1997 00:52:28 +0930 (CST) Message-Id: <199709251522.AAA04395@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), sos@sos.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: INB question In-reply-to: Your message of "Fri, 19 Sep 1997 14:44:27 GMT." <199709191444.HAA06050@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 00:52:28 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This isn't the MCA configuration information; this is the BIOS > > hardware table. I mean the soft configuration information that you > > mung with the config disk. > > I have no idea where that lives; I haven't even gotten around to > building an EISA config under UNIX (I at least know where that > data lives, and the format of the .INF files). I doubt you will > be able to get rid of the DOS configuration tool for MCA any time > soon. The EISA config is actually the root of the ESCD storage, which I still have hopes of using at some stage. > > > Yeah; that's why I picked the extended MCA DMA ports for the detect; > > > that, and I can do the probe non-destructively, with the expectation of > > > a 0 bit in my data and no hardware configuratio changes resulting. > > > > Where is the port exactly? ie. is it likely to be sat on or masked > > over by an ISA device? > > Port 0x18 is the control, and port 0x1A is the data. Should be OK, from a cursory inspection. mike From owner-freebsd-hackers Thu Sep 25 10:29:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00444 for hackers-outgoing; Thu, 25 Sep 1997 10:29:51 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00437 for ; Thu, 25 Sep 1997 10:29:46 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id TAA24502; Thu, 25 Sep 1997 19:29:25 +0200 (MEST) From: Søren Schmidt Message-Id: <199709251729.TAA24502@sos.freebsd.dk> Subject: Re: ATAPI Zip challenge : aftermath In-Reply-To: <199709251519.AAA04359@word.smith.net.au> from Mike Smith at "Sep 26, 97 00:49:43 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 25 Sep 1997 19:29:25 +0200 (MEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Mike Smith who wrote: > > Just to bring some continuity to this story; last week I arranged a > loan drive, with which to experiment. After some fruitless initial > tinkering, I sent it back as faulty. > > The replacement arrived today, and it exhibits the same basic > behaviour; ie. it no longer looks like an IDE disk at all. It _does_ > respond to the ATAPI probe, however they appear to have removed the IDE > emulation in current models. Does it behave like an ATAPI device ?? Or is it some kind of proprietary protocol ?? > This of course means that you can't _boot_ from them anymore, which is > a royal pain. > > It'd still be good if someone were to come forward and offer to add the > necessary ATAPI support, of course. 8) Shouldn't be too difficult, IF it follows the ATAPI protocol... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Sep 25 10:32:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00699 for hackers-outgoing; Thu, 25 Sep 1997 10:32:56 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00694 for ; Thu, 25 Sep 1997 10:32:52 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id DAA04904; Fri, 26 Sep 1997 03:00:29 +0930 (CST) Message-Id: <199709251730.DAA04904@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: S ren Schmidt cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Thu, 25 Sep 1997 19:29:25 +0200." <199709251729.TAA24502@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 26 Sep 1997 03:00:26 +0930 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA00695 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The replacement arrived today, and it exhibits the same basic > > behaviour; ie. it no longer looks like an IDE disk at all. It _does_ > > respond to the ATAPI probe, however they appear to have removed the IDE > > emulation in current models. > > Does it behave like an ATAPI device ?? Or is it some kind of proprietary > protocol ?? It appears to behave like an ATAPI device. Jason Thorpe's anectdotal evidence suggests that Iomega are rampant ATAPI/SCSI fans. > > It'd still be good if someone were to come forward and offer to add the > > necessary ATAPI support, of course. 8) > > Shouldn't be too difficult, IF it follows the ATAPI protocol... Indeed. mike From owner-freebsd-hackers Thu Sep 25 10:45:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA01462 for hackers-outgoing; Thu, 25 Sep 1997 10:45:14 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA01453 for ; Thu, 25 Sep 1997 10:45:08 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id TAA24678; Thu, 25 Sep 1997 19:44:43 +0200 (MEST) From: Søren Schmidt Message-Id: <199709251744.TAA24678@sos.freebsd.dk> Subject: Re: ATAPI Zip challenge : aftermath In-Reply-To: <199709251730.DAA04904@word.smith.net.au> from Mike Smith at "Sep 26, 97 03:00:26 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 25 Sep 1997 19:44:43 +0200 (MEST) Cc: mike@smith.net.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Mike Smith who wrote: > > > The replacement arrived today, and it exhibits the same basic > > > behaviour; ie. it no longer looks like an IDE disk at all. It _does_ > > > respond to the ATAPI probe, however they appear to have removed the IDE > > > emulation in current models. > > > > Does it behave like an ATAPI device ?? Or is it some kind of proprietary > > protocol ?? > > It appears to behave like an ATAPI device. Jason Thorpe's anectdotal > evidence suggests that Iomega are rampant ATAPI/SCSI fans. OK, but isn't any proof :) > > > > It'd still be good if someone were to come forward and offer to add the > > > necessary ATAPI support, of course. 8) > > > > Shouldn't be too difficult, IF it follows the ATAPI protocol... > > Indeed. If anybody feels like throwing a drive in my direction, I could be persuaded to give it a try... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Sep 25 10:53:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA01843 for hackers-outgoing; Thu, 25 Sep 1997 10:53:20 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA01837 for ; Thu, 25 Sep 1997 10:53:15 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id DAA04984; Fri, 26 Sep 1997 03:18:56 +0930 (CST) Message-Id: <199709251748.DAA04984@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: S ren Schmidt cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Thu, 25 Sep 1997 19:44:43 +0200." <199709251744.TAA24678@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 26 Sep 1997 03:18:53 +0930 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA01839 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It appears to behave like an ATAPI device. Jason Thorpe's anectdotal > > evidence suggests that Iomega are rampant ATAPI/SCSI fans. > > OK, but isn't any proof :) Natch. Still, NetBSD treats it as a SCSI disk that just has the bad fortune to be attached to an IDE interface. That's gotta count for something 8) > If anybody feels like throwing a drive in my direction, I could be > persuaded to give it a try... Uh, a bit far away here. How about a login on a machine with one? 8) mike From owner-freebsd-hackers Thu Sep 25 11:15:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03074 for hackers-outgoing; Thu, 25 Sep 1997 11:15:50 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03067 for ; Thu, 25 Sep 1997 11:15:45 -0700 (PDT) Received: from dale.salk.edu (dale [198.202.70.112]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id LAA14088 for ; Thu, 25 Sep 1997 11:15:43 -0700 (PDT) Date: Thu, 25 Sep 1997 11:15:42 -0700 (PDT) From: Tom Bartol To: freebsd-hackers@freebsd.org Subject: problem compiling for linux under compat_linux Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, Can anyone confirm or refute the following anomalous behaviour of /compat/linux/usr/bin/gcc running under -current ?? If I use /compat/linux/usr/bin/gcc to compile anything other that very trivial c program sources located on an NFS mounted filesystem I get broken executables which seg fault. This same source code compiles correctly when located on a local filesystem. This problem does not occur when compiling trivial sources such as "Hello World". Thankyou very much for you help in this matter, Tom From owner-freebsd-hackers Thu Sep 25 11:24:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03519 for hackers-outgoing; Thu, 25 Sep 1997 11:24:18 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03514 for ; Thu, 25 Sep 1997 11:24:16 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA02907; Thu, 25 Sep 1997 11:23:40 -0700 (PDT) To: Mike Smith cc: Greg Lehey , FreeBSD Hackers Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Thu, 25 Sep 1997 23:46:17 +0930." <199709251416.XAA04104@word.smith.net.au> Date: Thu, 25 Sep 1997 11:23:40 -0700 Message-ID: <2904.875211820@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You don't. Due to the nature of the distributed CVS repository, there > is a window where even the exact time of checkout for the snapshot > build might leave you out of sync. The only way around this would be > for the snap to be built from a tree directly checked out from the > master repository. Jordan does this for the for-CDROM versions, I > think. Yes, I tag and then I build from that tag after resyncronizing my local repository. Unfortunately, tags are expensive and you don't just lay them down for fun. Jordan From owner-freebsd-hackers Thu Sep 25 12:02:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA05509 for hackers-outgoing; Thu, 25 Sep 1997 12:02:00 -0700 (PDT) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.219]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA05488; Thu, 25 Sep 1997 12:01:51 -0700 (PDT) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id MAA19530; Thu, 25 Sep 1997 12:00:24 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA022834023; Thu, 25 Sep 1997 12:00:23 -0700 Received: from mina.sr.hp.com by mina.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA223834022; Thu, 25 Sep 1997 12:00:22 -0700 Message-Id: <199709251900.AA223834022@mina.sr.hp.com> To: Dave Hayes Cc: hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Reply-To: darrylo@sr.hp.com In-Reply-To: Your message of "Tue, 23 Sep 1997 15:18:16 PDT." <199709232218.PAA18505@hokkshideh.jetcafe.org> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Thu, 25 Sep 1997 12:00:22 -0700 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So was "leak", which was a DBM style wrapper to malloc/free. It would > keep track of what you'd free'd and malloc'd and warn you when you > were screwing up. Leak was public domain, but I have no idea where to > get it. I have a hacked copy if anyone wants want. "Leak" appeared in comp.sources.unix, volume 27 (circa 1994): ------------------------------------------------------------------------------- Subject: Volume 27 (Ends March 29, 1994) leak (1 part, 2 patches) quick and dirty code to find memory leaks, efence (1 part, 1 patch) Electric Fence, a debugging malloc() library, ------------------------------------------------------------------------------- Note that "efence" also appeared there. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Thu Sep 25 12:13:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06442 for hackers-outgoing; Thu, 25 Sep 1997 12:13:14 -0700 (PDT) Received: from gta.gta.com (gta.gta.com [199.120.225.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA06399; Thu, 25 Sep 1997 12:12:40 -0700 (PDT) Message-Id: <199709251916.PAA23595@gta.gta.com> Received: forwarded by SMTP 1.6.0. Received: (from lab@localhost) by uno.gta.com (8.8.7/8.8.7) id PAA11132; Thu, 25 Sep 1997 15:08:34 -0400 (EDT) From: "Larry Baird" Date: Thu, 25 Sep 1997 15:08:33 -0400 X-Mailer: Z-Mail (3.0.1 04apr94) To: freebsd-hackers@freebsd.org Subject: adding token ring support Cc: freebsd-jobs@freebsd.org Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Our company is interested in funding someone to add token ring support to freeBSD. Anyone know anyone that might be interested? Thanks, Larry -- ----------------------------------------------------------------------------- Larry Baird | Global Technology Associates, Inc. Director, Software Development | Orlando, FL Email: lab@gta.com | Tel 407-380-0220 FAX 407-380-6080 From owner-freebsd-hackers Thu Sep 25 12:19:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06792 for hackers-outgoing; Thu, 25 Sep 1997 12:19:02 -0700 (PDT) Received: from monk.via.net (monk.via.net [140.174.204.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA06786 for ; Thu, 25 Sep 1997 12:18:57 -0700 (PDT) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id MAA04919 for hackers@freebsd.org; Thu, 25 Sep 1997 12:08:55 -0700 Date: Thu, 25 Sep 1997 12:08:55 -0700 From: Joe McGuckin Message-Id: <199709251908.MAA04919@monk.via.net> To: hackers@freebsd.org Subject: Truss/Trace? X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Any anyone implemented this for FreeBSD yet? From owner-freebsd-hackers Thu Sep 25 12:27:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA07264 for hackers-outgoing; Thu, 25 Sep 1997 12:27:08 -0700 (PDT) Received: from monk.via.net (monk.via.net [140.174.204.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA07258 for ; Thu, 25 Sep 1997 12:27:04 -0700 (PDT) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id MAA04978 for hackers@freebsd.org; Thu, 25 Sep 1997 12:17:13 -0700 Date: Thu, 25 Sep 1997 12:17:13 -0700 From: Joe McGuckin Message-Id: <199709251917.MAA04978@monk.via.net> To: hackers@freebsd.org Subject: iostat question X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why doesn't iostat report info for ccd devices? The kernel treats the ccd devive like a 'real' disk. I assume it must have the same data structures that a 'sd' device has that iostat examines. joe From owner-freebsd-hackers Thu Sep 25 12:39:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08139 for hackers-outgoing; Thu, 25 Sep 1997 12:39:49 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08134 for ; Thu, 25 Sep 1997 12:39:45 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id VAA00387; Thu, 25 Sep 1997 21:39:15 +0200 (MEST) From: Søren Schmidt Message-Id: <199709251939.VAA00387@sos.freebsd.dk> Subject: Re: ATAPI Zip challenge : aftermath In-Reply-To: <199709251748.DAA04984@word.smith.net.au> from Mike Smith at "Sep 26, 97 03:18:53 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 25 Sep 1997 21:39:15 +0200 (MEST) Cc: mike@smith.net.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Mike Smith who wrote: > > > It appears to behave like an ATAPI device. Jason Thorpe's anectdotal > > > evidence suggests that Iomega are rampant ATAPI/SCSI fans. > > > > OK, but isn't any proof :) > > Natch. Still, NetBSD treats it as a SCSI disk that just has the bad > fortune to be attached to an IDE interface. That's gotta count for > something 8) True.. > > If anybody feels like throwing a drive in my direction, I could be > > persuaded to give it a try... > > Uh, a bit far away here. How about a login on a machine with one? 8) Well it takes some of the motivation to do it, and there is nothing that beats watching the drive go "grrr bonk bonk" when you do something wrong :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Sep 25 12:53:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09050 for hackers-outgoing; Thu, 25 Sep 1997 12:53:20 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA09031 for ; Thu, 25 Sep 1997 12:53:15 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA24488 (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Thu, 25 Sep 1997 21:52:27 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id VAA02208; Thu, 25 Sep 1997 21:23:05 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709251923.VAA02208@yedi.iaf.nl> Subject: Re: vt420 terminal To: tlambert@primenet.com (Terry Lambert) Date: Thu, 25 Sep 1997 21:23:05 +0200 (MET DST) Cc: jamil@counterintelligence.ml.org, jbryant@tfs.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199709250727.AAA09884@usr03.primenet.com> from "Terry Lambert" at Sep 25, 97 07:27:36 am X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote... > > > What the heck is a DEC-style modular connector (who manufactures the > > connector?) > > Instead of: > > ,-----. > `-----' > ,-------------. > | | | | | | | | > | | | | | | | | > `-+-+-+-+-+-+-' > > It looks like: > > ,-----. > `-----' > ,-------------. > | | | | | | | | > | | | | | | | | > `-+-+-+-+-+-+-' Which is called the MMJ (modified MJ) To be found in DECconnect office cabling (among others) > This change to the locking tab was made for: "no good reason". Come on, we tremendously boost the sales of all sorts of weird adapters ;-) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Thu Sep 25 12:53:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09079 for hackers-outgoing; Thu, 25 Sep 1997 12:53:26 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA09066 for ; Thu, 25 Sep 1997 12:53:23 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA24499 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Thu, 25 Sep 1997 21:53:43 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id VAA02336 for FreeBSD-hackers@freebsd.org; Thu, 25 Sep 1997 21:35:07 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709251935.VAA02336@yedi.iaf.nl> Subject: Re: Known problems with async ufs? To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Thu, 25 Sep 1997 21:35:07 +0200 (MET DST) In-Reply-To: <199709242320.QAA12833@salsa.gv.tsc.tdk.com> from "Don Lewis" at Sep 24, 97 04:20:01 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Don Lewis wrote... > On Sep 24, 10:31am, Brandon Gillespie wrote: > } Subject: Re: Known problems with async ufs? > > } I personally am running off a smart-ups, and have a daemon monitoring it > } so it will shutdown properly, if need be. > > I've got four machines fed by an UPS. Within 48 hours of being switched > to UPS power, someone working on an adjacent rack accidentally kicked loose > the power cord on the output side of the UPS :-( Which means that apart from a smart UPS you need to get smart users/sysadmins/hardware guys ;-) > You're also not protected against power supply failures and failures on > the output side of the UPS (blow fuse, etc.). Who needs fuses? Use 0.5" nails instead... (I really saw things like that) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Thu Sep 25 13:03:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA09798 for hackers-outgoing; Thu, 25 Sep 1997 13:03:04 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA09771 for ; Thu, 25 Sep 1997 13:02:41 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA01235; Wed, 24 Sep 1997 23:28:36 -0700 (PDT) Date: Wed, 24 Sep 1997 23:28:36 -0700 (PDT) From: "Jamil J. Weatherbee" To: nobody cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id NAA09777 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jed is better, however the port has a flaw in that it does not correctly handle PageUp/PageDn, If that was fixed I wouldn't use anything else. On Thu, 25 Sep 1997, nobody wrote: > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 18863 99.1 1.2 388 732 p3- R 6:59PM 673:39.41 ee > /etc/pw.018862 > > I've had this happen several times now, where I would login to my system > and see ee taking up 99% CPU (on a P2/266). As you can see, this is some > guy doing chfn I guess. This process has been on for 12 hours now though. > > Any known problems with ee? (besides the fact that Im about to rename it > and put joe in its place). > > This is on a 2.2-STABLE system. (last CVSup'd about a week ago). > > > --- > thomas strömberg . system admin, royal institute of technology (stockholm) > nobody@darkening.com . irc:nobody@EFnet . talk:nonxstnt@silent.darkening.com > real coders don't use comments. It was hard to write; it should be hard to read > > > From owner-freebsd-hackers Thu Sep 25 13:05:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10009 for hackers-outgoing; Thu, 25 Sep 1997 13:05:03 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA09985 for ; Thu, 25 Sep 1997 13:04:52 -0700 (PDT) Received: from argus.tfs.net (pm3-p2.tfs.net [206.154.183.194]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id OAA28173; Thu, 25 Sep 1997 14:03:14 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id PAA00301; Thu, 25 Sep 1997 15:04:38 -0500 (CDT) From: Jim Bryant Message-Id: <199709252004.PAA00301@argus.tfs.net> Subject: Re: vt420 terminal In-Reply-To: <199709251923.VAA02208@yedi.iaf.nl> from Wilko Bulte at "Sep 25, 97 09:23:05 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Thu, 25 Sep 1997 15:04:37 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > Come on, we tremendously boost the sales of all sorts of weird adapters ;-) tell me about it... okay people, last night about 2am i was about to go to bed, and jumped on the local 442.250 MHz Amateur repeater, mentioned that i was looking for the info about the adapters and the pinouts for the MMJ/DEC-423... i got a call around noon today on the phone, and now have a copy of the pages of the manual with the MMJ pinout as well as two MMJ <-> DB-25 adapters... now all i need is two MMJ <-> MMJ cables... i'll probably have them in hand later today [or at least on order]... thanks anyway for the replies, but i think that my problem is now resolved... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Thu Sep 25 13:31:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11159 for hackers-outgoing; Thu, 25 Sep 1997 13:31:38 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA11146 for ; Thu, 25 Sep 1997 13:31:34 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id QAA23092; Thu, 25 Sep 1997 16:30:43 -0400 (EDT) Date: Thu, 25 Sep 1997 16:30:40 -0400 (EDT) From: Brian Mitchell To: Joe McGuckin cc: hackers@FreeBSD.ORG Subject: Re: Truss/Trace? In-Reply-To: <199709251908.MAA04919@monk.via.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Joe McGuckin wrote: > > > Any anyone implemented this for FreeBSD yet? > man ktrace;man kdump From owner-freebsd-hackers Thu Sep 25 13:38:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11538 for hackers-outgoing; Thu, 25 Sep 1997 13:38:41 -0700 (PDT) Received: from frodo.epigram.com ([199.2.31.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA11533 for ; Thu, 25 Sep 1997 13:38:28 -0700 (PDT) Received: from dalat (DALAT.epigram.com [10.100.100.211]) by frodo.epigram.com (8.7.5/8.7.3) with ESMTP id NAA00860 for ; Thu, 25 Sep 1997 13:24:26 -0700 (PDT) Message-ID: <342AC877.8E0C20CA@mail.epigram.com> Date: Thu, 25 Sep 1997 13:24:24 -0700 From: Brandon Huey Reply-To: brandon@epigram.com Organization: Epigram, Inc. X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: amd (wNFS/v2) sources X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there amd sources available, specifically those with NFSv2 support? Or, can anyone recommend a way to force amd under 2.2.2 to use NFS v2 only? Thanks. -bh -- Brandon Huey brandon@epigram.com Epigram, Inc. +1 415 843 4487 From owner-freebsd-hackers Thu Sep 25 13:57:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA13011 for hackers-outgoing; Thu, 25 Sep 1997 13:57:51 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA13003 for ; Thu, 25 Sep 1997 13:57:47 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xEKyi-0003FP-00; Thu, 25 Sep 1997 14:57:40 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id OAA17928; Thu, 25 Sep 1997 14:58:08 -0600 (MDT) Message-Id: <199709252058.OAA17928@harmony.village.org> To: Wilko Bulte Subject: Re: vt420 terminal Cc: tlambert@primenet.com (Terry Lambert), jamil@counterintelligence.ml.org, jbryant@tfs.net, freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 25 Sep 1997 21:23:05 +0200." <199709251923.VAA02208@yedi.iaf.nl> References: <199709251923.VAA02208@yedi.iaf.nl> Date: Thu, 25 Sep 1997 14:58:08 -0600 From: Warner Losh Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : Which is called the MMJ (modified MJ) : To be found in DECconnect office cabling (among others) : > This change to the locking tab was made for: "no good reason". : Come on, we tremendously boost the sales of all sorts of weird adapters ;-) Actually, being around at the time they were introduced (yow, has it really been 15 years) they were saying at the time the offset tab was to prevent you from plugging phones onto data ports and data cables into phone ports. Warner From owner-freebsd-hackers Thu Sep 25 14:03:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13343 for hackers-outgoing; Thu, 25 Sep 1997 14:03:51 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13336 for ; Thu, 25 Sep 1997 14:03:45 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id PAA12145; Thu, 25 Sep 1997 15:03:39 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA19692; Thu, 25 Sep 1997 15:03:37 -0600 (MDT) Date: Thu, 25 Sep 1997 15:03:37 -0600 (MDT) Message-Id: <199709252103.PAA19692@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Joe McGuckin Cc: hackers@freebsd.org Subject: Re: Truss/Trace? In-Reply-To: <199709251908.MAA04919@monk.via.net> References: <199709251908.MAA04919@monk.via.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Any anyone implemented this for FreeBSD yet? Send email to sef@FreeBSD.org. He's got code and an article that explains it that will hopefully be published RSN. Nate From owner-freebsd-hackers Thu Sep 25 14:10:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13737 for hackers-outgoing; Thu, 25 Sep 1997 14:10:26 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13732 for ; Thu, 25 Sep 1997 14:10:24 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id QAA28846 for ; Thu, 25 Sep 1997 16:10:23 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id QAA15043; Thu, 25 Sep 1997 16:10:22 -0500 (CDT) Message-ID: <19970925161021.36073@Mars.Mcs.Net> Date: Thu, 25 Sep 1997 16:10:21 -0500 From: Karl Denninger To: hackers@freebsd.org Subject: Hmmm... ok, who broke the kernel? :-) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -Current, re-supped to make sure it was complete as of about an hour ago: loading kernel isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment *** Error code 1 -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-hackers Thu Sep 25 14:42:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA15579 for hackers-outgoing; Thu, 25 Sep 1997 14:42:19 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA15572 for ; Thu, 25 Sep 1997 14:42:14 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA01381; Thu, 25 Sep 1997 14:41:32 -0700 (MST) From: Terry Lambert Message-Id: <199709252141.OAA01381@usr04.primenet.com> Subject: Re: vt420 terminal To: imp@village.org (Warner Losh) Date: Thu, 25 Sep 1997 21:41:32 +0000 (GMT) Cc: wilko@yedi.iaf.nl, tlambert@primenet.com, jamil@counterintelligence.ml.org, jbryant@tfs.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199709252058.OAA17928@harmony.village.org> from "Warner Losh" at Sep 25, 97 02:58:08 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > : Come on, we tremendously boost the sales of all sorts of weird adapters ;-) > > Actually, being around at the time they were introduced (yow, has it > really been 15 years) they were saying at the time the offset tab was > to prevent you from plugging phones onto data ports and data cables > into phone ports. Or using cheap off-the-shelf phone parts for data ports. ;-). I never met one person who went to plug their RS232 into a phone jack, was stopped by the tab, and muttered to themselves "Oh... yeah.". 8-) 8-). I hope the person who came up with "make the outlets orange" got a bigger bonus than the person who came up with "move the locking tab"... 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-hackers Thu Sep 25 14:48:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA15948 for hackers-outgoing; Thu, 25 Sep 1997 14:48:28 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA15943 for ; Thu, 25 Sep 1997 14:48:25 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA01744; Thu, 25 Sep 1997 14:47:44 -0700 (MST) From: Terry Lambert Message-Id: <199709252147.OAA01744@usr04.primenet.com> Subject: Re: How do I check out a snapshot? To: mike@smith.net.au (Mike Smith) Date: Thu, 25 Sep 1997 21:47:44 +0000 (GMT) Cc: grog@lemis.com, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199709251416.XAA04104@word.smith.net.au> from "Mike Smith" at Sep 25, 97 11:46:17 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Sure. But to repeat the question: > > > > I see nothing in the tree to help me determine where, when or what > > it is. > > > > How do I find it out? > > You don't. Due to the nature of the distributed CVS repository, there > is a window where even the exact time of checkout for the snapshot > build might leave you out of sync. The only way around this would be > for the snap to be built from a tree directly checked out from the > master repository. Jordan does this for the for-CDROM versions, I > think. This is not due to the nature of the CVS repository; this is due to the way it is being used. We've had the discussion about "how to use it to close the window" before. Enforcing reader/writer locks by making the repository group writable and the locking program SGID the caller into the group would fix the problem, pronto. 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-hackers Thu Sep 25 14:53:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA16310 for hackers-outgoing; Thu, 25 Sep 1997 14:53:23 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA16305 for ; Thu, 25 Sep 1997 14:53:21 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA01958; Thu, 25 Sep 1997 14:51:33 -0700 (MST) From: Terry Lambert Message-Id: <199709252151.OAA01958@usr04.primenet.com> Subject: Re: ATAPI Zip challenge : aftermath To: mike@smith.net.au (Mike Smith) Date: Thu, 25 Sep 1997 21:51:33 +0000 (GMT) Cc: sos@sos.freebsd.dk, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199709251730.DAA04904@word.smith.net.au> from "Mike Smith" at Sep 26, 97 03:00:26 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It appears to behave like an ATAPI device. Jason Thorpe's anectdotal > evidence suggests that Iomega are rampant ATAPI/SCSI fans. I can back this up with non-anecdotal evidence, if necessary. They were SCSI from day one. 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-hackers Thu Sep 25 15:08:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16905 for hackers-outgoing; Thu, 25 Sep 1997 15:08:51 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16871; Thu, 25 Sep 1997 15:08:40 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA03145; Thu, 25 Sep 1997 15:08:31 -0700 (MST) From: Terry Lambert Message-Id: <199709252208.PAA03145@usr04.primenet.com> Subject: Re: adding token ring support To: lab@gta.com (Larry Baird) Date: Thu, 25 Sep 1997 22:08:27 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-jobs@FreeBSD.ORG In-Reply-To: <199709251916.PAA23595@gta.gta.com> from "Larry Baird" at Sep 25, 97 03:08:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Our company is interested in funding someone to add token ring support to > freeBSD. Anyone know anyone that might be interested? The following have announced interest in this topic; some of them have stated that they've done work in this area (some even claiming to have a working driver), others were willing to donate equipment. I suggest you contact them all: MSX.GRACEFE Rob Batten Yaser K. Doleh Mike Smith Eric L. Hernes Eric Varsanyi Anton Horvath James Risner Ray Les Higger Joe McGuckin Nathan Denny kavitha Stefan Molnar Patrick Nadeau Larry Lile Julian H. Stacey You may also want to contact: Michael Rendell He has a working NetBEUI implementation for FreeBSD, and the LLC for token ring is very, very close. It would be nice if TR, NetBEUI, and the FDDI stuff already in FreeBSD could share code there. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Sep 25 15:15:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17241 for hackers-outgoing; Thu, 25 Sep 1997 15:15:20 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17220; Thu, 25 Sep 1997 15:15:07 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA03466; Thu, 25 Sep 1997 15:15:05 -0700 (MST) From: Terry Lambert Message-Id: <199709252215.PAA03466@usr04.primenet.com> Subject: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... To: karl@Mcs.Net (Karl Denninger) Date: Thu, 25 Sep 1997 22:15:05 +0000 (GMT) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <19970925161021.36073@Mars.Mcs.Net> from "Karl Denninger" at Sep 25, 97 04:10:21 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, no one with actual power over the tree has made the necessary announcement, so I will: If you are trying to build -current, and you get this error: > loading kernel > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment then you need to get the sources in /usr/src/usr.sbin/config, and rebuild "config". 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-hackers Thu Sep 25 15:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17357 for hackers-outgoing; Thu, 25 Sep 1997 15:16:39 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17327; Thu, 25 Sep 1997 15:16:30 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id RAA02150; Thu, 25 Sep 1997 17:16:21 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA17175; Thu, 25 Sep 1997 17:16:20 -0500 (CDT) Message-ID: <19970925171616.26390@Mars.Mcs.Net> Date: Thu, 25 Sep 1997 17:16:16 -0500 From: Karl Denninger To: Terry Lambert Cc: Karl Denninger , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... References: <19970925161021.36073@Mars.Mcs.Net> <199709252215.PAA03466@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <199709252215.PAA03466@usr04.primenet.com>; from Terry Lambert on Thu, Sep 25, 1997 at 10:15:05PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 25, 1997 at 10:15:05PM +0000, Terry Lambert wrote: > Well, no one with actual power over the tree has made the necessary > announcement, so I will: > > > > If you are trying to build -current, and you get this error: > > > loading kernel > > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > > then you need to get the sources in /usr/src/usr.sbin/config, and > rebuild "config". > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. Now you tell me :-) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-hackers Thu Sep 25 15:17:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17449 for hackers-outgoing; Thu, 25 Sep 1997 15:17:58 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17443 for ; Thu, 25 Sep 1997 15:17:53 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA03582; Thu, 25 Sep 1997 15:17:48 -0700 (MST) From: Terry Lambert Message-Id: <199709252217.PAA03582@usr04.primenet.com> Subject: Re: iostat question To: joe@via.net (Joe McGuckin) Date: Thu, 25 Sep 1997 22:17:48 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709251917.MAA04978@monk.via.net> from "Joe McGuckin" at Sep 25, 97 12:17:13 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Why doesn't iostat report info for ccd devices? The kernel treats the > ccd devive like a 'real' disk. I assume it must have the same data structures > that a 'sd' device has that iostat examines. Because iostat copies out device data, and to make it work for this use would require going to a functional rather than a data interface to get it's data. A functional interface could do the necessary work to agregate the information from the devices the ccd driver is spanning. 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-hackers Thu Sep 25 15:31:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18136 for hackers-outgoing; Thu, 25 Sep 1997 15:31:55 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18131 for ; Thu, 25 Sep 1997 15:31:47 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id RAA03490; Thu, 25 Sep 1997 17:31:30 -0500 (EST) From: "John S. Dyson" Message-Id: <199709252231.RAA03490@dyson.iquest.net> Subject: Re: Hmmm... ok, who broke the kernel? :-) In-Reply-To: <19970925161021.36073@Mars.Mcs.Net> from Karl Denninger at "Sep 25, 97 04:10:21 pm" To: karl@Mcs.Net (Karl Denninger) Date: Thu, 25 Sep 1997 17:31:29 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Karl Denninger said: > -Current, re-supped to make sure it was complete as of about an hour ago: > > loading kernel > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > *** Error code 1 > Config needs to be rebuilt. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Thu Sep 25 15:40:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18666 for hackers-outgoing; Thu, 25 Sep 1997 15:40:45 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18661 for ; Thu, 25 Sep 1997 15:40:41 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id RAA22910 for ; Thu, 25 Sep 1997 17:39:59 -0500 (CDT) Received: from newman.exu.ericsson.se (newman.exu.ericsson.se [138.85.10.50]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id RAA02086 for ; Thu, 25 Sep 1997 17:39:58 -0500 (CDT) Received: from b04h32.exu.ericsson.se (euswdwj@b04h32 [138.85.55.132]) by newman.exu.ericsson.se (8.7.5/8.7.3) with ESMTP id RAA27150 for ; Thu, 25 Sep 1997 17:39:54 -0500 (CDT) From: "William D. Ward" Received: (euswdwj@localhost) by b04h32.exu.ericsson.se (8.7.6/8.6.12) id RAA25926 for freebsd-hackers@freebsd.org; Thu, 25 Sep 1997 17:32:21 -0500 (CDT) Message-Id: <199709252232.RAA25926@b04h32.exu.ericsson.se> Subject: Compaq XL 590-PCNet Problem? (jkh sent me) To: freebsd-hackers@freebsd.org Date: Thu, 25 Sep 1997 17:32:21 -0500 (CDT) X-Mailer: ELM [version 2.4 PL0] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Perhaps it was some sort of devine province that Jordan decided post the mini-FAQ (ref. Q-2) shortly after I sent this question to comp.unix.- freebsd.misc. Or not. It would depend on your faith maybe. -- Hello, This message was originally posted to the freebsd-questions mailing list with minimal response. I have about 40 of these machines and it would be good if I could do something useful with them for a change. The FreeBSD installation boot floppy did not work for this system (this is definitely not the norm) so I roled my own using methods I found in the /usr/src/release directory. Please help. ---original message posted to freebsd-questions mailing list follows--- I'm having some difficulties getting the Ethernet interface to work on a Compaq Deskpro XL 590. Currently ifconfig on this machine results in a syslog message reporting 'lnc0: Initialisation failed' (which perhaps means that the initialization failed). The FreeBSD installation boot floppy did not work for this system so I roled my own using methods I found in the /usr/src/release directory. I have about 40 of these machines and it would be good if I could do something useful with them for a change. Please help. I am using 2.2.2-RELEASE. My procedure is as follows: 1. boot from custom boot floppy that does not go into /stand/sysinstall but instead starts /etc/rc script containing just /stand/sh. it also has ifconfig, mount, ping, route, and dmesg (crunched dmesg isn't working thus no verbose boot info in this note. i could use some help here too maybe. separate issue). 2. boot -c. set port for lnc0 to 0x7000 and continue boot. the hardware is probed. i see the following: a. pci0:0 is probed but no driver is assigned. (bad sign or not?) b. lnc1 shown to be detected even though there is only one interface. this is immediately after pci0:0 is probed. (hmmm) c. lnc0 is shown to be detected later on when the rest of the Ethernet interfaces are looked for. 3. /stand/sh is invoked. from command line issue: # ifconfig lnc0 161.76.4.7 lnc0: Initialisation failed ^ ^ ^ (note case and spelling.) 4. pinging 161.76.4.7 works but pinging another address that should go out the interface reports that 'network is down'. play with routing for a little bit to see if everything is ok there. same results. ifconfig -a reports that the interface is up. the interface is plugged into a hub. Other points: 1. another point that might be interesting (or not) is that ifconfig -a reports that there are two lnc interfaces (lnc0 and lnc1) yet there is only one adapter. configuring either interface yields the same result. 2. the hardware is as follows: Compaq XL 590 Pentium 100 32 MB RAM 512 MB SCSI IBM HD on board PCNet Ethernet/SCSI Host Adapter (see below) Chip Data: the chip labeling for the Ethernet adapter is as follows: PCNet (tm) - SCSI AM79C974KC 9434CP8 A4 1993 AMD here is what Compaq has to say about the PCNet-SCSI chip: Pcnet-scsi Chip The Compaq Deskpro XL series packs new levels of power through the PCneto-SCSI chip. Jointly developed by Compaq and Advanced Micro Devices (AMD), PCnet-SCSI is the first chip to fully integrate both the 32-bit Fast SCSI-2 controller and 32-bit Ethernet NIC on the PCI local bus on the system board, saving not only the expansion slots that would otherwise be needed for SCSI and Ethernet add-on boards, but also the cost of the controllers themselves which typically cost several hundred dollars each. PCnet-SCSI provides customers with a higher-performance network-ready solution that is compatible with all major operating systems. 3. in looking through the mailing list archive it appears that this has been a problem in the past for some Compaq platforms. in some cases resolution may have been obtained by setting the port for lnc0 to 0x7000. other cases appear to be unresolved faulting Compaq's PCI bus which may not conform to accepted standards on some models. 4. floppies/boot.flp does not work on this system. it appears to hang when sysinstall would normally display its UI. this is not a problem as it is possible for me to load the machine manually once the network interface is configured. it is only a problem in getting verbose boot messages as the fixit floppy which probably has a working dmesg is not accessible. ---original message ends--- Doug White (thanks, Doug) responded to my original post and pointed out that I did not mentioned that I tried booting without making changes to the port address. Thanks in advance. best regards, William From owner-freebsd-hackers Thu Sep 25 15:58:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19741 for hackers-outgoing; Thu, 25 Sep 1997 15:58:53 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [198.180.136.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19733 for ; Thu, 25 Sep 1997 15:58:46 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.7/8.8.3) id MAA00585; Thu, 25 Sep 1997 12:56:28 -1000 (HST) Message-Id: <199709252256.MAA00585@caliban.dihelix.com> Subject: Re: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... In-Reply-To: <199709252215.PAA03466@usr04.primenet.com> from Terry Lambert at "Sep 25, 97 10:15:05 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 25 Sep 1997 12:56:27 -1000 (HST) Cc: karl@Mcs.Net, hackers@FreeBSD.ORG From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk strangly enough I had to do this a couple of times before it helped. *shrug* -David Langford langfod@dihelix.com >If you are trying to build -current, and you get this error: > >> loading kernel >> isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >then you need to get the sources in /usr/src/usr.sbin/config, and >rebuild "config". > > Terry Lambert > terry@lambert.org From owner-freebsd-hackers Thu Sep 25 16:02:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20043 for hackers-outgoing; Thu, 25 Sep 1997 16:02:40 -0700 (PDT) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA20037 for ; Thu, 25 Sep 1997 16:02:36 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id AAA05282; Fri, 26 Sep 1997 00:02:31 +0100 (BST) Date: Fri, 26 Sep 1997 00:02:30 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Mike Smith cc: hackers@freebsd.org Subject: Re: ATAPI Zip challenge : aftermath In-Reply-To: <199709251519.AAA04359@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Mike Smith wrote: > The replacement arrived today, and it exhibits the same basic > behaviour; ie. it no longer looks like an IDE disk at all. It _does_ > respond to the ATAPI probe, however they appear to have removed the IDE > emulation in current models. > > This of course means that you can't _boot_ from them anymore, which is > a royal pain. Does it look enough like an ATAPI CD drive that a BIOS with boot-from-CD support would attempt to boot it? From owner-freebsd-hackers Thu Sep 25 16:13:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20682 for hackers-outgoing; Thu, 25 Sep 1997 16:13:54 -0700 (PDT) Received: from dcarmich.pr.mcs.net (dcarmich.pr.mcs.net [204.95.63.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA20676; Thu, 25 Sep 1997 16:13:47 -0700 (PDT) Received: (from dcarmich@localhost) by dcarmich.pr.mcs.net (8.8.5/8.8.5) id SAA00219; Thu, 25 Sep 1997 18:16:56 -0500 (CDT) From: Douglas Carmichael Message-Id: <199709252316.SAA00219@dcarmich.pr.mcs.net> Subject: Some ideas for accessibility in FreeBSD To: jkh@freebsd.org Date: Thu, 25 Sep 1997 18:16:55 -0500 (CDT) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (These are just ideas, I can't implement them because I have no access to any of these alternate devices). 1) Patching the syscons and pcvt drivers to accept *input* from a serially-connected alternate input device and display on the standard display (a sort of "hybrid console"). For the functions needing two keys (e.g. VT switching), there should be an option in the kernel config file to only require one key. 2) Patch the console drivers to display on the normal console and take input from either the keyboard or a user-specified device but also shunt all output to a serial port (for speech synthesizers) 2a) Utilize a speech synthesizing driver as an LKM which would utilize the user's existing sound card (preferably loaded in the 3rd stage boot) 3) Changing the X server to accept text from a non-keyboard input device (i.e. alternate keyboard, etc.) 4) Patching the console drivers to allow larger text for people with vision problems. 5) If the user selects it, use either simplified boot messages or sounds to signify which stage of the boot process has been reached. (Any more ideas?) From owner-freebsd-hackers Thu Sep 25 16:15:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20778 for hackers-outgoing; Thu, 25 Sep 1997 16:15:24 -0700 (PDT) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA20767 for ; Thu, 25 Sep 1997 16:15:17 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id IAA06848; Fri, 26 Sep 1997 08:44:55 +0930 (CST) Message-ID: <19970926084454.21580@lemis.com> Date: Fri, 26 Sep 1997 08:44:54 +0930 From: Greg Lehey To: Terry Lambert Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? References: <199709251416.XAA04104@word.smith.net.au> <199709252147.OAA01744@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709252147.OAA01744@usr04.primenet.com>; from Terry Lambert on Thu, Sep 25, 1997 at 09:47:44PM +0000 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 25, 1997 at 09:47:44PM +0000, Terry Lambert wrote: >>> Sure. But to repeat the question: >>> >>> I see nothing in the tree to help me determine where, when or what >>> it is. >>> >>> How do I find it out? >> >> You don't. Due to the nature of the distributed CVS repository, there >> is a window where even the exact time of checkout for the snapshot >> build might leave you out of sync. The only way around this would be >> for the snap to be built from a tree directly checked out from the >> master repository. Jordan does this for the for-CDROM versions, I >> think. > > This is not due to the nature of the CVS repository; this is due to the > way it is being used. We've had the discussion about "how to use it > to close the window" before. Enforcing reader/writer locks by making > the repository group writable and the locking program SGID the caller > into the group would fix the problem, pronto. This calls for something like the online snapshot capability of the Veritas Volume Mangler. More practically, wouldn't it be easy enough to defer updates on the tree for an hour or two? Greg From owner-freebsd-hackers Thu Sep 25 16:43:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22423 for hackers-outgoing; Thu, 25 Sep 1997 16:43:14 -0700 (PDT) Received: from thelab.hub.org (root@ppp-136.halifax-01.ican.net [206.231.248.136]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22401; Thu, 25 Sep 1997 16:43:03 -0700 (PDT) Received: from thelab.hub.org (scrappy@localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id UAA15817; Thu, 25 Sep 1997 20:41:59 -0300 (ADT) Date: Thu, 25 Sep 1997 20:41:59 -0300 (ADT) From: The Hermit Hacker To: Terry Lambert cc: Karl Denninger , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... In-Reply-To: <199709252215.PAA03466@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Terry Lambert wrote: > Well, no one with actual power over the tree has made the necessary > announcement, so I will: > > > > If you are trying to build -current, and you get this error: > > > loading kernel > > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > > then you need to get the sources in /usr/src/usr.sbin/config, and > rebuild "config". Hrmmm...I always considered this to be "standard operating procedure" when upgrading my kernel: check to make sure config sources haven't changed *Shrug* Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Thu Sep 25 17:07:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23722 for hackers-outgoing; Thu, 25 Sep 1997 17:07:28 -0700 (PDT) Received: from bob.scl.ameslab.gov (bob.scl.ameslab.gov [147.155.137.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23717 for ; Thu, 25 Sep 1997 17:07:26 -0700 (PDT) Received: (from ccsanady@localhost) by bob.scl.ameslab.gov (8.8.7/8.8.5) id TAA10113 for freebsd-hackers@freebsd.org; Thu, 25 Sep 1997 19:08:11 -0500 (CDT) Date: Thu, 25 Sep 1997 19:08:11 -0500 (CDT) From: Chris Csanady Message-Id: <199709260008.TAA10113@bob.scl.ameslab.gov> To: freebsd-hackers@freebsd.org Subject: CVS permissions after checkout Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have recently cvsuped a cvs tree, but am experiencing some interesting problems. I am not sure why, but after I cvsup, my entire repository is marked as executable. After I check out source, it is also executable. How do I make cvs or whatever do the right thing? Thanks, Chris From owner-freebsd-hackers Thu Sep 25 20:03:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02251 for hackers-outgoing; Thu, 25 Sep 1997 20:03:50 -0700 (PDT) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02243 for ; Thu, 25 Sep 1997 20:03:47 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id XAA25003 for ; Thu, 25 Sep 1997 23:04:40 -0400 (EDT) Date: Thu, 25 Sep 1997 23:04:39 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: bootpd[163]: bad addr len from from Ethernet address Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I keep getting this error message on my screen: > Sep 25 23:00:36 phoenix bootpd[163]: bad addr len from from Ethernet > address 52:41:53:20:10:0D Yet, when I do a 'tcpdump ether host 52:41:53:20:10:0D', I get *nothing*, even when these messages continue to come up while I have tcpdump running. I have verified tcpdump is working correctly as I have listened to the MAC address of the IBM X-Station running off of my machine. Where is the problem on this one? -- David Cross ACS Consultant From owner-freebsd-hackers Thu Sep 25 20:32:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03536 for hackers-outgoing; Thu, 25 Sep 1997 20:32:48 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03529 for ; Thu, 25 Sep 1997 20:32:35 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00428; Fri, 26 Sep 1997 12:59:30 +0930 (CST) Message-Id: <199709260329.MAA00428@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), grog@lemis.com, hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Thu, 25 Sep 1997 21:47:44 GMT." <199709252147.OAA01744@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 12:59:27 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > You don't. Due to the nature of the distributed CVS repository, there > > is a window where even the exact time of checkout for the snapshot > > build might leave you out of sync. The only way around this would be > > for the snap to be built from a tree directly checked out from the > > master repository. Jordan does this for the for-CDROM versions, I > > think. > > This is not due to the nature of the CVS repository; this is due to the > way it is being used. We've had the discussion about "how to use it > to close the window" before. Enforcing reader/writer locks by making > the repository group writable and the locking program SGID the caller > into the group would fix the problem, pronto. No, it wouldn't. Closer would be to claim the "checkout" time for a remotely-built SNAP matched the CVSup scan from which the remote repo was last updated, but unfortunately there isn't any such thing. mike From owner-freebsd-hackers Thu Sep 25 20:35:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03661 for hackers-outgoing; Thu, 25 Sep 1997 20:35:17 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03646 for ; Thu, 25 Sep 1997 20:35:08 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00484; Fri, 26 Sep 1997 13:00:49 +0930 (CST) Message-Id: <199709260330.NAA00484@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), sos@sos.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Thu, 25 Sep 1997 21:51:33 GMT." <199709252151.OAA01958@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 13:00:48 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It appears to behave like an ATAPI device. Jason Thorpe's anectdotal > > evidence suggests that Iomega are rampant ATAPI/SCSI fans. > > I can back this up with non-anecdotal evidence, if necessary. They > were SCSI from day one. I haven't had a chance to gut an ATAPI Zip yet (stupid warranty stickers), but I'd buy that. So how do you explain the IDE emulation mode on the older models? Any why the *^&%(*& did they discontinue it? mike From owner-freebsd-hackers Thu Sep 25 20:35:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03688 for hackers-outgoing; Thu, 25 Sep 1997 20:35:28 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03683 for ; Thu, 25 Sep 1997 20:35:21 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00500; Fri, 26 Sep 1997 13:02:45 +0930 (CST) Message-Id: <199709260332.NAA00500@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrew Gordon cc: Mike Smith , hackers@freebsd.org Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Fri, 26 Sep 1997 00:02:30 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 13:02:43 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Fri, 26 Sep 1997, Mike Smith wrote: > > The replacement arrived today, and it exhibits the same basic > > behaviour; ie. it no longer looks like an IDE disk at all. It _does_ > > respond to the ATAPI probe, however they appear to have removed the IDE > > emulation in current models. > > > > This of course means that you can't _boot_ from them anymore, which is > > a royal pain. > > Does it look enough like an ATAPI CD drive that a BIOS with boot-from-CD > support would attempt to boot it? Not enough for the AMI BIOS at any rate; it complains that it's "Atapi incompatible", which I think means "it's not a CDROM". mike From owner-freebsd-hackers Thu Sep 25 20:52:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA04560 for hackers-outgoing; Thu, 25 Sep 1997 20:52:51 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA04555 for ; Thu, 25 Sep 1997 20:52:49 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id UAA29332; Thu, 25 Sep 1997 20:52:20 -0700 (MST) From: Terry Lambert Message-Id: <199709260352.UAA29332@usr05.primenet.com> Subject: Re: How do I check out a snapshot? To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 03:52:20 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, grog@lemis.com, hackers@FreeBSD.ORG In-Reply-To: <199709260329.MAA00428@word.smith.net.au> from "Mike Smith" at Sep 26, 97 12:59:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > You don't. Due to the nature of the distributed CVS repository, there > > > is a window where even the exact time of checkout for the snapshot > > > build might leave you out of sync. The only way around this would be > > > for the snap to be built from a tree directly checked out from the > > > master repository. Jordan does this for the for-CDROM versions, I > > > think. > > > > This is not due to the nature of the CVS repository; this is due to the > > way it is being used. We've had the discussion about "how to use it > > to close the window" before. Enforcing reader/writer locks by making > > the repository group writable and the locking program SGID the caller > > into the group would fix the problem, pronto. > > No, it wouldn't. Why not? If the main CVS repository can't be non-atomically updated, and the CVSup for the CVS mirrors had to acquire a reader lock to do the mirroring so they can't be non-atomically mirrored from the main tree, and the user CVSup's had to acquire a reader lock to pull from the mirrors so a local tree can't be non-atomically mirrored by the users... then there is no such thing as an out of sync CVS tree. If you are worried about keeping regionally seperate builds in sync, you just pick a snap date sufficiently far in the past that it spans the propagation delay for the mirroring between you and the master repository. > Closer would be to claim the "checkout" time for a remotely-built SNAP > matched the CVSup scan from which the remote repo was last updated, but > unfortunately there isn't any such thing. If *all* readers had to get a lock, including the CVSup for the remote repository, then there would be. You could build it into the daemon to assert a reader lock on where you are mirroring from, and build it into the client to assert a writer lock on where you are mirroring to. 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-hackers Thu Sep 25 20:55:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA04649 for hackers-outgoing; Thu, 25 Sep 1997 20:55:01 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA04631 for ; Thu, 25 Sep 1997 20:54:55 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00608; Fri, 26 Sep 1997 13:22:11 +0930 (CST) Message-Id: <199709260352.NAA00608@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), grog@lemis.com, hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Fri, 26 Sep 1997 03:52:20 GMT." <199709260352.UAA29332@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 13:22:10 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If you are worried about keeping regionally seperate builds in sync, > you just pick a snap date sufficiently far in the past that it spans > the propagation delay for the mirroring between you and the master > repository. This is exactly the issue. In reality, building "yesterday's snap" is probably adequate, but yesterday's -current is _history_, man! 8) mike From owner-freebsd-hackers Thu Sep 25 21:04:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05023 for hackers-outgoing; Thu, 25 Sep 1997 21:04:32 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05016 for ; Thu, 25 Sep 1997 21:04:27 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA00183; Thu, 25 Sep 1997 21:02:57 -0700 (MST) From: Terry Lambert Message-Id: <199709260402.VAA00183@usr05.primenet.com> Subject: Re: ATAPI Zip challenge : aftermath To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 04:02:57 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, sos@sos.freebsd.dk, hackers@FreeBSD.ORG In-Reply-To: <199709260330.NAA00484@word.smith.net.au> from "Mike Smith" at Sep 26, 97 01:00:48 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So how do you explain the IDE emulation mode on the older models? Any > why the *^&%(*& did they discontinue it? Cheaper manufacturing for the daughterboard, I'm betting. And/or the people who are including them in their new machines don't want them bootable or swappable because of the Windows 95 bugs with removable media (the TSD for removable media devices silently corrupts pages obtained from it when FS_ReadWrite is called with R0_SWAPPER_CALL; you can't install most software from it if it runs from or opens a DLL on the device -- most InstallShield based installs have to). Bet you didn't know *that* dirty little secret... Luckily, miniport drivers can be written to be portable between NT and 95, so NT has the bug too. 8-p. 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-hackers Thu Sep 25 21:09:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05310 for hackers-outgoing; Thu, 25 Sep 1997 21:09:36 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05287; Thu, 25 Sep 1997 21:09:23 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA00555; Thu, 25 Sep 1997 21:09:09 -0700 (MST) From: Terry Lambert Message-Id: <199709260409.VAA00555@usr05.primenet.com> Subject: Re: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... To: scrappy@hub.org (The Hermit Hacker) Date: Fri, 26 Sep 1997 04:09:08 +0000 (GMT) Cc: tlambert@primenet.com, karl@Mcs.Net, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "The Hermit Hacker" at Sep 25, 97 08:41:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > then you need to get the sources in /usr/src/usr.sbin/config, and > > rebuild "config". > > Hrmmm...I always considered this to be "standard operating procedure" > when upgrading my kernel: check to make sure config sources haven't > changed *Shrug* I always considered config to be wasteful, now that it's possible to include or not include modules and have them dynamically register themselves via SYSINIT() simply by deciding that you will/won't link that particular object into the kernel. Once ELF is there, modules can go into different sections, and an ELF object archiver can configure/deconfigure modules without even needing to relink the darned things. *Shrug* 8-) Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Sep 25 21:12:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05557 for hackers-outgoing; Thu, 25 Sep 1997 21:12:39 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05549 for ; Thu, 25 Sep 1997 21:12:27 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00709; Fri, 26 Sep 1997 13:39:53 +0930 (CST) Message-Id: <199709260409.NAA00709@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Fri, 26 Sep 1997 04:02:57 GMT." <199709260402.VAA00183@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 13:39:51 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > So how do you explain the IDE emulation mode on the older models? Any > > why the *^&%(*& did they discontinue it? > > Cheaper manufacturing for the daughterboard, I'm betting. And/or the > people who are including them in their new machines don't want them > bootable or swappable because of the Windows 95 bugs with removable > media Hmm. I'd buy either of those I guess. It's a serious pain in the ass though. > (the TSD for removable media devices silently corrupts pages > obtained from it when FS_ReadWrite is called with R0_SWAPPER_CALL; > you can't install most software from it if it runs from or opens a > DLL on the device -- most InstallShield based installs have to). > > Bet you didn't know *that* dirty little secret... Not until you first blabbed about it months ago. 8) > Luckily, miniport drivers can be written to be portable between NT and > 95, so NT has the bug too. 8-p. Hmm. This is a reason not to adopt the miniport interface for FreeBSD? mike From owner-freebsd-hackers Thu Sep 25 21:13:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05599 for hackers-outgoing; Thu, 25 Sep 1997 21:13:19 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05591 for ; Thu, 25 Sep 1997 21:13:06 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA00754; Thu, 25 Sep 1997 21:12:44 -0700 (MST) From: Terry Lambert Message-Id: <199709260412.VAA00754@usr05.primenet.com> Subject: Re: ATAPI Zip challenge : aftermath To: arg@arg1.demon.co.uk (Andrew Gordon) Date: Fri, 26 Sep 1997 04:12:44 +0000 (GMT) Cc: mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: from "Andrew Gordon" at Sep 26, 97 00:02:30 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This of course means that you can't _boot_ from them anymore, which is > > a royal pain. > > Does it look enough like an ATAPI CD drive that a BIOS with boot-from-CD > support would attempt to boot it? Not really. It looked like a hard drive. As I said in my other message, it's probably intentional to keep down support calls, since MS OS's (other than DOS) can't safely run binaries or swap from removable media. 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-hackers Thu Sep 25 21:15:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05789 for hackers-outgoing; Thu, 25 Sep 1997 21:15:52 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05748 for ; Thu, 25 Sep 1997 21:15:35 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00737; Fri, 26 Sep 1997 13:42:43 +0930 (CST) Message-Id: <199709260412.NAA00737@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom Bartol cc: freebsd-hackers@FreeBSD.ORG Subject: Re: problem compiling for linux under compat_linux In-reply-to: Your message of "Thu, 25 Sep 1997 11:15:42 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 13:42:41 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If I use /compat/linux/usr/bin/gcc to compile anything other that very > trivial c program sources located on an NFS mounted filesystem I get > broken executables which seg fault. This same source code compiles > correctly when located on a local filesystem. This problem does not occur > when compiling trivial sources such as "Hello World". Can you build non-trivial FreeBSD programs on an NFS-mounted filesystem? It's not clear to me how this could be an emulation-related problem just yet. (Possibly an mmap() incompatability?) Could you compile the smallest non-trivial program that generates the undesired symptoms both on a local and non-local filesystem and compare the two? It would be very useful to know what was different between the two. mike From owner-freebsd-hackers Thu Sep 25 22:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA07996 for hackers-outgoing; Thu, 25 Sep 1997 22:00:28 -0700 (PDT) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA07990 for ; Thu, 25 Sep 1997 22:00:24 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.7/8.8.7) with SMTP id AAA10737; Fri, 26 Sep 1997 00:59:56 -0400 (EDT) Date: Fri, 26 Sep 1997 00:59:55 -0400 (EDT) From: "Matthew N. Dodd" To: Brian Mitchell cc: Joe McGuckin , hackers@FreeBSD.ORG Subject: Re: Truss/Trace? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Brian Mitchell wrote: > On Thu, 25 Sep 1997, Joe McGuckin wrote: > > Any anyone implemented this for FreeBSD yet? > man ktrace;man kdump As others have pointed out, ktrace/kdump are -not- truss. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Thu Sep 25 22:18:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA08585 for hackers-outgoing; Thu, 25 Sep 1997 22:18:00 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA08579 for ; Thu, 25 Sep 1997 22:17:57 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id WAA22309 for ; Thu, 25 Sep 1997 22:17:53 -0700 (PDT) Date: Thu, 25 Sep 1997 22:17:53 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: rc.sysctl? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anybody think of a good reason not to have something like /etc/rc.sysctl that contains any sysctl -w's that you want to have run before you start up a bunch of daemons? There doesn't seem to be any good place to put them. rc.local is too late, since things like keepalive, send/recvspace, and others may need to be set before things like sendmail start up. Seems trivial to add, and potentially useful. (Of course, run levels ala solaris would solve this problem as well, but that's another argument for another time and place). From owner-freebsd-hackers Thu Sep 25 23:35:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA13023 for hackers-outgoing; Thu, 25 Sep 1997 23:35:58 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA13018; Thu, 25 Sep 1997 23:35:52 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id IAA01227; Fri, 26 Sep 1997 08:35:39 +0200 (MEST) From: Søren Schmidt Message-Id: <199709260635.IAA01227@sos.freebsd.dk> Subject: Re: Some ideas for accessibility in FreeBSD In-Reply-To: <199709252316.SAA00219@dcarmich.pr.mcs.net> from Douglas Carmichael at "Sep 25, 97 06:16:55 pm" To: dcarmich@mcs.com (Douglas Carmichael) Date: Fri, 26 Sep 1997 08:35:39 +0200 (MEST) Cc: jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Douglas Carmichael who wrote: > (These are just ideas, I can't implement them because I have no access to > any of these alternate devices). > 1) Patching the syscons and pcvt drivers to accept *input* from a > serially-connected alternate input device and display on the standard > display (a sort of "hybrid console"). For the functions needing two keys > (e.g. VT switching), there should be an option in the kernel config file > to only require one key. That would be pretty easy, allthough some knowledge of the device will be nessesary to make prober use of it.. > 2) Patch the console drivers to display on the normal console and take > input from either the keyboard or a user-specified device but also > shunt all output to a serial port (for speech synthesizers) Looks more and more like normal & serial- console together, should be easy to do by hacking the lowlevel console rutines.. > 2a) Utilize a speech synthesizing driver as an LKM which > would utilize the user's existing sound card (preferably loaded in the 3rd > stage boot) I long ago looked at some code that could do this, but I had difficulty understanding the sounds that came out of it :), Its not impossible though, just not exactly easy... > 3) Changing the X server to accept text from a non-keyboard > input device (i.e. alternate keyboard, etc.) That could be arranged. > 4) Patching the console drivers to allow larger text for people with > vision problems. Syscons allready have a 40x25 mode, that produces larger text to some extent, for even bigger test, a little changes will have to be made to the drivers... > 5) If the user selects it, use either simplified boot messages or sounds > to signify which stage of the boot process has been reached. Thats easy to do, just put in a call to the beeping function in one of the console drivers and you're off... Are you into makeing computers for handicapped people ?? It would be nice to have functionality to help out there... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Sep 25 23:44:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA13629 for hackers-outgoing; Thu, 25 Sep 1997 23:44:14 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA13622 for ; Thu, 25 Sep 1997 23:44:10 -0700 (PDT) Received: from dale.salk.edu (dale [198.202.70.112]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id XAA27976; Thu, 25 Sep 1997 23:43:56 -0700 (PDT) Date: Thu, 25 Sep 1997 23:43:54 -0700 (PDT) From: Tom Bartol To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: problem compiling for linux under compat_linux In-Reply-To: <199709260412.NAA00737@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Mike Smith wrote: > > If I use /compat/linux/usr/bin/gcc to compile anything other that very > > trivial c program sources located on an NFS mounted filesystem I get > > broken executables which seg fault. This same source code compiles > > correctly when located on a local filesystem. This problem does not occur > > when compiling trivial sources such as "Hello World". > > Can you build non-trivial FreeBSD programs on an NFS-mounted filesystem? > Yes, I have no trouble building non-trivial native FreeBSD executables from NFS-mounted filesystems. > It's not clear to me how this could be an emulation-related problem > just yet. (Possibly an mmap() incompatability?) > > Could you compile the smallest non-trivial program that generates the > undesired symptoms both on a local and non-local filesystem and compare > the two? It would be very useful to know what was different between > the two. > > mike > I'll try to come up with the smallest possible program which presents the problem. I have been able to determine that the problem occurs in the "ld" step of the build process. The intermediate object files generated are just fine because I can build them on an NFS filesystem, copy them to local and link them there perfectly but when I link them on the NFS filesystem I get a broken executable which "file" interestingly identifies as a statically linked ELF instead of a dynmically linked ELF. A real linux system can also link the object files generated by compat_linux or by itself regardless of whether they are local or on an NFS filesystem. I've generated ktrace.out files of the "ld" step under compat_linux for the case which succeeds on local but fails on NFS. The ktrace.out files differ and are 1MB each. Unfortunately, I am not very versed in how to interpret them with kdump. If someone would like to help me out and have a look at them I would be happy to make them available at our ftp site. I agree with you in having touble seeing how this can be an emulation problem. I'm not trying to claim that it is, just that I've found evidence of something rotten in the state of Denmark. I do feel that I have been careful and diligent up to this point in narrowing down the problem to clear-cut cases of success and failure, the critical factor seeming to be the presence or absence of an NFS filesystem in the scenario. I'll be away from e-mail till Sept. 30 so I hope I can resurrect our useful discussion of this matter when I return. Thanks again, Tom From owner-freebsd-hackers Thu Sep 25 23:54:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA14397 for hackers-outgoing; Thu, 25 Sep 1997 23:54:59 -0700 (PDT) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA14362; Thu, 25 Sep 1997 23:54:44 -0700 (PDT) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id KAA06887; Fri, 26 Sep 1997 10:54:14 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id KAA06908; Fri, 26 Sep 1997 10:54:00 +0400 (MSD) Message-Id: <199709260654.KAA06908@asteroid.mgt.msk.ru> To: hackers@freebsd.org cc: stable@freebsd.org Reply-To: tarkhil@mgt.msk.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 10:53:59 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other computer can see me, and I can't see any others. Putting fxp0 in promiscous mode heals the trouble in several seconds, but shutdown (without reboot) doesn't help. Routing tables remains unchanged. It happened at both day and night, the only program that could receive something thry TCP/IP was sendmail. make world and kernel recompilatin didn't help. Any other suggestions? Alex. From owner-freebsd-hackers Fri Sep 26 00:01:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15026 for hackers-outgoing; Fri, 26 Sep 1997 00:01:56 -0700 (PDT) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA15008; Fri, 26 Sep 1997 00:01:50 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id QAA08062; Fri, 26 Sep 1997 16:31:04 +0930 (CST) Message-ID: <19970926163104.12375@lemis.com> Date: Fri, 26 Sep 1997 16:31:04 +0930 From: Greg Lehey To: Karl Denninger Cc: Terry Lambert , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... References: <19970925161021.36073@Mars.Mcs.Net> <199709252215.PAA03466@usr04.primenet.com> <19970925171616.26390@Mars.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970925171616.26390@Mars.Mcs.Net>; from Karl Denninger on Thu, Sep 25, 1997 at 05:16:16PM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 25, 1997 at 05:16:16PM -0500, Karl Denninger wrote: > On Thu, Sep 25, 1997 at 10:15:05PM +0000, Terry Lambert wrote: >> Well, no one with actual power over the tree has made the necessary >> announcement, so I will: >> >> >> >> If you are trying to build -current, and you get this error: >> >>> loading kernel >>> isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment >> >> then you need to get the sources in /usr/src/usr.sbin/config, and >> rebuild "config". > > Now you tell me :-) Sounds like the announcment had its value, then. Greg From owner-freebsd-hackers Fri Sep 26 00:11:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15608 for hackers-outgoing; Fri, 26 Sep 1997 00:11:20 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA15602 for ; Fri, 26 Sep 1997 00:11:13 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id QAA00259; Fri, 26 Sep 1997 16:38:39 +0930 (CST) Message-Id: <199709260708.QAA00259@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom Bartol cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: problem compiling for linux under compat_linux In-reply-to: Your message of "Thu, 25 Sep 1997 23:43:54 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 16:38:36 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Can you build non-trivial FreeBSD programs on an NFS-mounted filesystem? > > Yes, I have no trouble building non-trivial native FreeBSD executables > from NFS-mounted filesystems. OK. That prettymuch rules out lower-level NFS problems. > as a statically linked ELF instead of a dynmically linked ELF. A real > linux system can also link the object files generated by compat_linux or > by itself regardless of whether they are local or on an NFS filesystem. This is very helpful to know. > I've generated ktrace.out files of the "ld" step under compat_linux for > the case which succeeds on local but fails on NFS. The ktrace.out files > differ and are 1MB each. Unfortunately, I am not very versed in how to > interpret them with kdump. If someone would like to help me out and have > a look at them I would be happy to make them available at our ftp site. Ktrace is very bad at handling non-FreeBSD binaries; more exactly kdump doesn't get the system call names right. Interpreting such a dump is not a trivial chore. > I agree with you in having touble seeing how this can be an emulation > problem. I'm not trying to claim that it is, just that I've found > evidence of something rotten in the state of Denmark. I do feel that I > have been careful and diligent up to this point in narrowing down the > problem to clear-cut cases of success and failure, the critical factor > seeming to be the presence or absence of an NFS filesystem in the > scenario. It seems to me that you have narrowed the window very well; my current suspicion would have to be that this is related to mmap()ing of NFS files, and possibly a behavioural incompatability that's slipped by. > I'll be away from e-mail till Sept. 30 so I hope I can resurrect our > useful discussion of this matter when I return. Please do; if you could come back with details on which version of FreeBSD you're running etc. that'd be handy too. mike From owner-freebsd-hackers Fri Sep 26 00:32:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA16943 for hackers-outgoing; Fri, 26 Sep 1997 00:32:02 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA16890 for ; Fri, 26 Sep 1997 00:31:57 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id AAA15659; Fri, 26 Sep 1997 00:31:16 -0700 (MST) From: Terry Lambert Message-Id: <199709260731.AAA15659@usr04.primenet.com> Subject: Re: ATAPI Zip challenge : aftermath To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 07:31:16 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199709260409.NAA00709@word.smith.net.au> from "Mike Smith" at Sep 26, 97 01:39:51 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Luckily, miniport drivers can be written to be portable between NT and > > 95, so NT has the bug too. 8-p. > > Hmm. This is a reason not to adopt the miniport interface for FreeBSD? Naw. The TSD for removable media would have to be written; I really don't like the idea of replacing that particular level of BSD anyway; the place to use miniport support is for vendor supplied disk drivers. NDIS drivers would be good, too, but they shouldn't be relied upon, mostly because they can't really support IP aliases at this point. 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-hackers Fri Sep 26 00:35:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA17133 for hackers-outgoing; Fri, 26 Sep 1997 00:35:57 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA17127 for ; Fri, 26 Sep 1997 00:35:50 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA00370; Fri, 26 Sep 1997 17:03:25 +0930 (CST) Message-Id: <199709260733.RAA00370@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: rc.sysctl? In-reply-to: Your message of "Thu, 25 Sep 1997 22:17:53 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 17:03:25 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Can anybody think of a good reason not to have something like > /etc/rc.sysctl that contains any sysctl -w's that you want to have run > before you start up a bunch of daemons? Yes. Nothing other than rc.conf should contain parameters (with the dubious exception of rc.local). > There doesn't seem to be any good place to put them. rc.conf is where the values should go. > rc.local is too late, since things like keepalive, send/recvspace, and > others may need to be set before things like sendmail start up. These are network parameters, and thus should be set in rc.network. They should be keyed off the existence of variables set in rc.conf, which could be supplied as NO by default. > Seems trivial to add, and potentially useful. > > (Of course, run levels ala solaris would solve this problem as well, but > that's another argument for another time and place). No, they further distribute and obfuscate the configuration information. You might want to consider a more generalised sysctl tweaking mechanism , eg. one that consumed variables of the form 'sysctl_X' where X was a monotonically increasing value starting with 0. You could handle these early on in rc, just after rc.conf is sourced. This would still suffer from the "sysctl is not in /sbin" problem for people using NFS for /usr. mike From owner-freebsd-hackers Fri Sep 26 00:49:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18255 for hackers-outgoing; Fri, 26 Sep 1997 00:49:52 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA18192 for ; Fri, 26 Sep 1997 00:48:44 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA25944; Fri, 26 Sep 1997 08:35:58 +0200 From: Luigi Rizzo Message-Id: <199709260635.IAA25944@labinfo.iet.unipi.it> Subject: Re: bootpd[163]: bad addr len from from Ethernet address To: dec@phoenix.its.rpi.edu (David E. Cross) Date: Fri, 26 Sep 1997 08:35:58 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "David E. Cross" at Sep 25, 97 11:04:20 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I keep getting this error message on my screen: > > > Sep 25 23:00:36 phoenix bootpd[163]: bad addr len from from Ethernet > > address 52:41:53:20:10:0D these things look suspiciously like corrupt frames where a part of the payload is mistaken for the header. 52,41,53,20 are ascii codes for letters etc, 0D is a carriage return, etc. Cheers Luigi From owner-freebsd-hackers Fri Sep 26 00:51:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18342 for hackers-outgoing; Fri, 26 Sep 1997 00:51:02 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18335 for ; Fri, 26 Sep 1997 00:50:57 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA00456 for ; Fri, 26 Sep 1997 17:18:46 +0930 (CST) Message-Id: <199709260748.RAA00456@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@freebsd.org Subject: Timeout for sh(1) 'read' ?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 17:18:45 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiho folks, a question for the sh(1) studs amongst you : - I want to prompt for input using 'read', and have the read return in some fashion after a timeout. I'd like to do this just using sh, and I'm not too fussed about how hairy it is. Any ideas? (If sh has to be modified to achieve this, would it be a useful thing to bring back?) mike From owner-freebsd-hackers Fri Sep 26 00:57:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18715 for hackers-outgoing; Fri, 26 Sep 1997 00:57:21 -0700 (PDT) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18664; Fri, 26 Sep 1997 00:56:47 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.7/8.8.7) id KAA01057; Fri, 26 Sep 1997 10:53:42 +0300 (EEST) From: Ruslan Ermilov Message-Id: <199709260753.KAA01057@relay.ucb.crimea.ua> Subject: Re: your mail In-Reply-To: <199709260654.KAA06908@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at "Sep 26, 97 10:53:59 am" To: tarkhil@mgt.msk.ru Date: Fri, 26 Sep 1997 10:53:42 +0300 (EEST) Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-My-Interests: Unix,Oracle,Networking X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Once Alexander B. Povolotsky wrote: > Hello! > > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other computer can see me, and I can't see any others. > > Putting fxp0 in promiscous mode heals the trouble in several seconds, but shutdown (without reboot) doesn't help. Routing tables remains unchanged. It happened at both day and night, the only program that could receive something thry TCP/IP was sendmail. > > make world and kernel recompilatin didn't help. > > Any other suggestions? > > Alex. > The same problems. I'm using 3 EtherExpress cards: fxp0 rev 2 int a irq 10 on pci0:10 fxp0: Ethernet address 00:a0:c9:55:13:22 fxp1 rev 1 int a irq 9 on pci0:12 fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps fxp2 rev 1 int a irq 9 on pci0:14 fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes. When I `ifconfig down delete fxp0' and then ifconfig it up, the situation resolves. ;-( -- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN From owner-freebsd-hackers Fri Sep 26 01:01:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA18995 for hackers-outgoing; Fri, 26 Sep 1997 01:01:20 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA18990 for ; Fri, 26 Sep 1997 01:01:18 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id BAA17357; Fri, 26 Sep 1997 01:01:10 -0700 (MST) From: Terry Lambert Message-Id: <199709260801.BAA17357@usr04.primenet.com> Subject: Re: problem compiling for linux under compat_linux To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 08:01:09 +0000 (GMT) Cc: bartol@salk.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199709260412.NAA00737@word.smith.net.au> from "Mike Smith" at Sep 26, 97 01:42:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > If I use /compat/linux/usr/bin/gcc to compile anything other that very > > trivial c program sources located on an NFS mounted filesystem I get > > broken executables which seg fault. This same source code compiles > > correctly when located on a local filesystem. This problem does not occur > > when compiling trivial sources such as "Hello World". How do you make the compiler invoke the right linker in this case? Do you hack your path? I've never thought running a Linux compiler in a compat directory would work because it would invoke FreeBSD pieces for hidden components. Are they really all referenced off the user's path?!? Are they all branded Linux executables so the will go through compat first on their path lookups? > It's not clear to me how this could be an emulation-related problem > just yet. (Possibly an mmap() incompatability?) Maybe. Do they mmap() the objects in ld now? Editorial on cache thrashing by mmap() in ld: This was a big screwup when USL first did it, and if GNU ld now does it, it's a big screwup for them, too. On UnixWare, it thrashed the buffer cache to death, forcing all other inodes buffers out. The X server went to hell. It's a pretty trivial denial-of-service attack. The fix is pretty trivial too: set a per file "working set quota" and when you go over the quota on a particular vnode, you take pages from it (they have to be LRU'ed off the vnode) instead of getting them from the system. This could be a big pessimization, though, for say a standalone news server that isn't competing with other processes for cache, or a big executable with poor locality (like, oh, an X server?). A kludge for the exectuable is to not do it for programs with VEXEC set. A kludge for the news server is to enforce the working set restriction based on per process settings (ala login.conf). This doesn't fall down (far, anyway) if one process with a big quota and one with a small quota are hitting the same file, since you only take the last page on the LRU (neither process is likely to ask for it), and you only take it when the process wants a new page. So the in-core working set size will grow to the highest process quota, and the lowest quota process will still recycle pages. I suppose you could habe a low quota process that buzzes pages still, which would LRU off the higher quotas pages. The only way to really fix that is to chain the processes using the vnode off the vnode and have the vnode have a quota field it inherits from the highest quota'ed process. They wouldn't let me add another pointer to the proc struct in UnixWare. It's still succeptible to the problem, since my working set code was turned down in favor of giving the X server a new scheduling class ("fixed") and letting it swap pages back in when it needs them. Bah Humbug. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Sep 26 01:05:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19268 for hackers-outgoing; Fri, 26 Sep 1997 01:05:41 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19263 for ; Fri, 26 Sep 1997 01:05:38 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id BAA17565; Fri, 26 Sep 1997 01:05:36 -0700 (MST) From: Terry Lambert Message-Id: <199709260805.BAA17565@usr04.primenet.com> Subject: Re: rc.sysctl? To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Fri, 26 Sep 1997 08:05:36 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jaye Mathisen" at Sep 25, 97 10:17:53 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Can anybody think of a good reason not to have something like > /etc/rc.sysctl that contains any sysctl -w's that you want to have run > before you start up a bunch of daemons? > > There doesn't seem to be any good place to put them. > > rc.local is too late, since things like keepalive, send/recvspace, and > others may need to be set before things like sendmail start up. > > Seems trivial to add, and potentially useful. > > (Of course, run levels ala solaris would solve this problem as well, but > that's another argument for another time and place). Heh. And you are proposing a mechanism which is tantamount to /etc/conf on Solaris, only you can't drop in new configuration code by dropping in a new file, you have to instead modify a file that contains both instructions and the configuration data that they operate on. Sounds a hell of a lot like the BSD rc file vs. rc.d argument to me. ;-). 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-hackers Fri Sep 26 01:13:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19735 for hackers-outgoing; Fri, 26 Sep 1997 01:13:09 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19720 for ; Fri, 26 Sep 1997 01:12:32 -0700 (PDT) Received: from ws6303-f (root@firix [10.1.143.100]) by zwei.siemens.at with ESMTP id KAA20539; Fri, 26 Sep 1997 10:11:12 +0200 (MET DST) Received: from ws6423.gud.siemens.at (ws6423-f) by ws6303-f with ESMTP (1.40.112.8/16.2) id AA004101436; Fri, 26 Sep 1997 10:10:36 +0200 Received: by ws6423.gud.siemens.at (SMI-8.6/SMI-SVR4) id KAA10101; Fri, 26 Sep 1997 10:09:43 +0200 Date: Fri, 26 Sep 1997 10:09:43 +0200 From: lada@ws6303.gud.siemens.at (marino.ladavac@siemens.at) Message-Id: <199709260809.KAA10101@ws6423.gud.siemens.at> To: hackers@FreeBSD.ORG, joe@via.net Subject: Re: Truss/Trace? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Md5: zCcezTfLu71YMQ8TBfKdOw== Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 25 21:40:05 MET 1997 > Date: Thu, 25 Sep 1997 12:08:55 -0700 > From: Joe McGuckin > To: hackers@FreeBSD.ORG > Subject: Truss/Trace? > X-Loop: FreeBSD.org > > > > Any anyone implemented this for FreeBSD yet? > man ktrace. You'll need to rebuild the kernel /Marino From owner-freebsd-hackers Fri Sep 26 01:20:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA20156 for hackers-outgoing; Fri, 26 Sep 1997 01:20:37 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA20129; Fri, 26 Sep 1997 01:20:31 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id BAA18077; Fri, 26 Sep 1997 01:20:20 -0700 (MST) From: Terry Lambert Message-Id: <199709260820.BAA18077@usr04.primenet.com> Subject: Re: Alexander B. Povol's mail To: tarkhil@mgt.msk.ru Date: Fri, 26 Sep 1997 08:20:19 +0000 (GMT) Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709260654.KAA06908@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at Sep 26, 97 10:53:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card > (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting > troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, > but no other computer can see me, and I can't see any others. 127.0.0.1 is the loopback address. You aren't ifconfig'ing the card to actually have that address, are you? > Putting fxp0 in promiscous mode heals the trouble in several seconds, > but shutdown (without reboot) doesn't help. Routing tables remains > unchanged. The 127.0.0.1 is not normally something that has anything at all to do with the card driver. Instead, it is internally looped back; it is a simulated interface. I don't see how shoving the interface into promiscuous mode would help. Perhaps you are RIP'ing out that your address is 127.0.0.1? This should give the arp tables on all the machines that are listening a fit. If you ever get a RIP back, you are probably screwed. Also, all loopback traffic on those machines (depending on how their routing code is written) would be bounced through your machine. I truly hope you aren't using it for the card address. 8-). > It happened at both day and night, the only program that > could receive something thry TCP/IP was sendmail. Sendmail specifically avoids domain suffixing on lookup, among other things; many programs don't, so it's probably working because of that; that's what made me think you might be using 127.0.0.1 as a real interface address, above. PS: use a subject line so you can recognize a reply, and break your lines at 80 columns so it's easier break out relevent lines when someone sends you a reply. PPS: if you still have problems, it would be useful for you to provide the output of the following network control functions: netstat -r arp -a ifconfig -a If DNS is clobbered, you may need to use the '-n' option to get real output instead of hanging forever waiting on a host lookup. 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-hackers Fri Sep 26 01:20:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA20208 for hackers-outgoing; Fri, 26 Sep 1997 01:20:57 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA20201 for ; Fri, 26 Sep 1997 01:20:53 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA00553; Fri, 26 Sep 1997 17:48:02 +0930 (CST) Message-Id: <199709260818.RAA00553@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), bartol@salk.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: problem compiling for linux under compat_linux In-reply-to: Your message of "Fri, 26 Sep 1997 08:01:09 GMT." <199709260801.BAA17357@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 17:48:01 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > If I use /compat/linux/usr/bin/gcc to compile anything other that very > > > trivial c program sources located on an NFS mounted filesystem I get > > > broken executables which seg fault. This same source code compiles > > > correctly when located on a local filesystem. This problem does not occur > > > when compiling trivial sources such as "Hello World". > > How do you make the compiler invoke the right linker in this case? You don't "make" it. It just does. > Do > you hack your path? No. > I've never thought running a Linux compiler in > a compat directory would work because it would invoke FreeBSD pieces > for hidden components. It doesn't. About the only time you trip up is when something like autoconf goes looking for things (most especially ranlib) and finds the FreeBSD version because there isn't a Linux one. > Are they really all referenced off the user's > path?!? Are they all branded Linux executables so the will go through > compat first on their path lookups? Any exec() call made by a linux-mode process will attempt to locate the target in /compat/linux first. The compiler driver is no exception. > > It's not clear to me how this could be an emulation-related problem > > just yet. (Possibly an mmap() incompatability?) > > Maybe. Do they mmap() the objects in ld now? I have no idea. I'm attempting to envision something in the ABI emulation that could be sensitive to the underlying filesystem type. About all that comes to mind is mmap() and maybe the directory lookup code. I can't see how the latter could cause this effect though, so mmap() is about all that's left. > Editorial on cache thrashing by mmap() in ld: Elide! Elide! mike From owner-freebsd-hackers Fri Sep 26 01:42:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA21574 for hackers-outgoing; Fri, 26 Sep 1997 01:42:16 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA21541; Fri, 26 Sep 1997 01:42:03 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA22393; Fri, 26 Sep 1997 01:43:43 -0700 (PDT) Message-Id: <199709260843.BAA22393@implode.root.com> To: tarkhil@mgt.msk.ru cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 26 Sep 1997 10:53:59 +0400." <199709260654.KAA06908@asteroid.mgt.msk.ru> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 01:43:43 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 > interface). Sometimes (about 3-4 times per week) I'm getting troubles > with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other > computer can see me, and I can't see any others. > >Putting fxp0 in promiscous mode heals the trouble in several seconds, but > shutdown (without reboot) doesn't help. Routing tables remains unchanged. > It happened at both day and night, the only program that could receive > something thry TCP/IP was sendmail. Sounds like you have a "rev 1" chip on the board and the ethernet you're attaching it to has noise problems which are triggering a bug in the chip that causes the receiver to lock up. The problem is especially acute when the interface is in 10Mbps mode. The best solution: find out why your network has garbage on it and fix it. Some hubs will filter out the garbage, so using a different hub might also fix the problem. Another solution: replace the card with a newer one that has the fixed NIC ("rev 2"). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Sep 26 02:10:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23283 for hackers-outgoing; Fri, 26 Sep 1997 02:10:11 -0700 (PDT) Received: from public1.guangzhou.gd.cn (public1.gz.gd.cn [202.96.128.111]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23267 for ; Fri, 26 Sep 1997 02:10:00 -0700 (PDT) Received: from public.public.guangzhou.gd.cn (max3-187.guangzhou.gd.cn [202.96.185.187]) by public1.guangzhou.gd.cn (8.8.5/8.8.5) with SMTP id RAA11190 for ; Fri, 26 Sep 1997 17:07:40 +0900 (CDT) Message-Id: <199709260807.RAA11190@public1.guangzhou.gd.cn> From: "Yuan Jianshan" To: Date: Fri, 26 Sep 1997 17:10:44 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-hackers Fri Sep 26 02:17:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23697 for hackers-outgoing; Fri, 26 Sep 1997 02:17:31 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23670; Fri, 26 Sep 1997 02:17:20 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA00775; Fri, 26 Sep 1997 18:43:19 +0930 (CST) Message-Id: <199709260913.SAA00775@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 08:20:19 GMT." <199709260820.BAA18077@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 18:43:16 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card > > (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting > > troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, > > but no other computer can see me, and I can't see any others. > > 127.0.0.1 is the loopback address. You aren't ifconfig'ing the card > to actually have that address, are you? (I have removed the term "peanut" from the following response. Feel free to reinsert it at an appropriate point to achieve the original tone.) No. He's reporting the "fxp driver dies occasionally" problem that's been seen off and on for the last few months. Pinging the loopback address is a simple confidence test in at least a little of the network code. See the section in the above paragraph where he uses English well enough to make it clear that 127.0.0.1 is *not* the address attachd to fxp0. > The 127.0.0.1 is not normally something that has anything at all to > do with the card driver. Instead, it is internally looped back; it > is a simulated interface. I don't see how shoving the interface > into promiscuous mode would help. Putting the fxp driver into promiscuous mode involves poking at bits of the interface hardware. This appears to fix whatever it is that's going wrong. If this problem hasn't already been dealt with in the -current/-stable drivers, I hope DG is looking at it. mike From owner-freebsd-hackers Fri Sep 26 02:28:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA24300 for hackers-outgoing; Fri, 26 Sep 1997 02:28:04 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA24236; Fri, 26 Sep 1997 02:27:56 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA22718; Fri, 26 Sep 1997 02:28:52 -0700 (PDT) Message-Id: <199709260928.CAA22718@implode.root.com> To: Ruslan Ermilov cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: your mail In-reply-to: Your message of "Fri, 26 Sep 1997 10:53:42 +0300." <199709260753.KAA01057@relay.ucb.crimea.ua> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 02:28:52 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm using 3 EtherExpress cards: > >fxp0 rev 2 int a irq 10 on pci0:10 >fxp0: Ethernet address 00:a0:c9:55:13:22 >fxp1 rev 1 int a irq 9 on pci0:12 >fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps >fxp2 rev 1 int a irq 9 on pci0:14 >fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps > >Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes. >When I `ifconfig down delete fxp0' and then ifconfig it up, the situation >resolves. If this is true, then Intel has apparantly lied to me about fixing the problem in the "next stepping" of the chip. The lock up should only occur when garbage bits occur in the preamble of a packet. It's not supposed to happen in 100Mbps mode (only 10Mbps), but since I've personnally been able to get it to happen in 100Mbps, I don't believe it. I can reproduce the problem only under special circumstance like power-cycling the hub. You might try using the "link0 link1 -link2" flags on the 100Mbps link to force it to stay in 100/half...this might prevent the lock up from occuring (but I've not tested this myself). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Sep 26 02:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA25229 for hackers-outgoing; Fri, 26 Sep 1997 02:46:44 -0700 (PDT) Received: from docenti.ing.unipi.it (docenti.ing.unipi.it [131.114.28.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA25213 for ; Fri, 26 Sep 1997 02:46:23 -0700 (PDT) Received: (from gabriele@localhost) by docenti.ing.unipi.it (8.8.5/8.8.5) id LAA24047; Fri, 26 Sep 1997 11:43:56 +0200 (MET DST) Date: Fri, 26 Sep 1997 11:43:56 +0200 (MET DST) From: Gabriele Cecchetti To: Ruslan Ermilov cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199709260753.KAA01057@relay.ucb.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Ruslan Ermilov wrote: > Once Alexander B. Povolotsky wrote: > > Hello! > > > > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other computer can see me, and I can't see any others. > > > > Putting fxp0 in promiscous mode heals the trouble in several seconds, but shutdown (without reboot) doesn't help. Routing tables remains unchanged. It happened at both day and night, the only program that could receive something thry TCP/IP was sendmail. > > > > make world and kernel recompilatin didn't help. > > > > Any other suggestions? > > > > Alex. > > > > The same problems. > I'm using 3 EtherExpress cards: > > fxp0 rev 2 int a irq 10 on pci0:10 > fxp0: Ethernet address 00:a0:c9:55:13:22 > fxp1 rev 1 int a irq 9 on pci0:12 > fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps > fxp2 rev 1 int a irq 9 on pci0:14 > fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps > > Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes. > When I `ifconfig down delete fxp0' and then ifconfig it up, the situation > resolves. > > ;-( I use a simple 'trick' to avoid this problem (works with rev 1 too): add to your crontab entry: * * * * * root /sbin/ping -i 5 -c 12 router_ip > /dev/null or if you wish */5 * * * * root /sbin/ping -i 5 -c 60 router_ip > /dev/null where router_ip could be any machine or your router. Using this the fxp0 is 'almost always' active: the interface dont'freeze if you use it to send packet. I use it for 2 month and the problem is disappeared. The very little overhead can be acceptable. Gabriele ============================================================================ Ing. Gabriele Cecchetti Millennium Information Engineering email: gabriele@ing.unipi.it Via Lenin 127 http://www.ing.unipi.it/~gabriele 56010 Pappiana, PISA (Italy) Tel: +39-50-862316 ============================================================================= From owner-freebsd-hackers Fri Sep 26 02:49:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA25445 for hackers-outgoing; Fri, 26 Sep 1997 02:49:37 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA25423 for ; Fri, 26 Sep 1997 02:49:28 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id TAA00895; Fri, 26 Sep 1997 19:16:43 +0930 (CST) Message-Id: <199709260946.TAA00895@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: S ren Schmidt cc: hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Thu, 25 Sep 1997 21:39:15 +0200." <199709251939.VAA00387@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 26 Sep 1997 19:16:41 +0930 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA25434 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Natch. Still, NetBSD treats it as a SCSI disk that just has the bad > > fortune to be attached to an IDE interface. That's gotta count for > > something 8) > > True.. Heh. And of course you don't have the time to do it that way? 8) > > > If anybody feels like throwing a drive in my direction, I could be > > > persuaded to give it a try... > > > > Uh, a bit far away here. How about a login on a machine with one? 8) > > Well it takes some of the motivation to do it, and there is nothing > that beats watching the drive go "grrr bonk bonk" when you do something > wrong :) *chuckle* Yeah, there is that. Mechanical hardware can be _very_ satisfying to play with. 8) (Radar gear can be fun too, but you can't actually _see_ the radiation, only its effects...) mike From owner-freebsd-hackers Fri Sep 26 04:00:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA28491 for hackers-outgoing; Fri, 26 Sep 1997 04:00:38 -0700 (PDT) Received: from dublin.iona.ie (root@operation.dublin.iona.ie [192.122.221.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA28482 for ; Fri, 26 Sep 1997 04:00:30 -0700 (PDT) Received: from ultra (ultra [192.122.221.136]) by dublin.iona.ie (8.7.5/jm-1.01) with SMTP id LAA05473; Fri, 26 Sep 1997 11:59:57 +0100 (BST) Date: Fri, 26 Sep 1997 11:59:32 +0100 (BST) From: Niall Smart X-Sender: nsmart@ultra To: Mike Smith cc: S ren Schmidt , hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-Reply-To: <199709260946.TAA00895@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Mike Smith wrote: > > Well it takes some of the motivation to do it, and there is nothing > > that beats watching the drive go "grrr bonk bonk" when you do something > > wrong :) > > *chuckle* Yeah, there is that. Mechanical hardware can be _very_ > satisfying to play with. 8) > > (Radar gear can be fun too, but you can't actually _see_ the radiation, > only its effects...) Heh, this brings an image to mind of you ducking madly to avoid the death-ray from your radar gone mad. niall From owner-freebsd-hackers Fri Sep 26 04:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA28674 for hackers-outgoing; Fri, 26 Sep 1997 04:05:14 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA28660 for ; Fri, 26 Sep 1997 04:05:05 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id UAA01234; Fri, 26 Sep 1997 20:32:35 +0930 (CST) Message-Id: <199709261102.UAA01234@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Niall Smart cc: hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-reply-to: Your message of "Fri, 26 Sep 1997 11:59:32 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 20:32:34 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Fri, 26 Sep 1997, Mike Smith wrote: > > > > Well it takes some of the motivation to do it, and there is nothing > > > that beats watching the drive go "grrr bonk bonk" when you do something > > > wrong :) > > > > *chuckle* Yeah, there is that. Mechanical hardware can be _very_ > > satisfying to play with. 8) > > > > (Radar gear can be fun too, but you can't actually _see_ the radiation, > > only its effects...) > > Heh, this brings an image to mind of you ducking madly to avoid the death-ray > from your radar gone mad. *grin* I'll spoil the idea by mentioning that the radar I was thinking of at the time is a phased array of 144 3-metre Yagis, and you can't "avoid" the deathray, especially not at the local console which is in the middle of the array 8) mike From owner-freebsd-hackers Fri Sep 26 04:32:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA29592 for hackers-outgoing; Fri, 26 Sep 1997 04:32:40 -0700 (PDT) Received: from usr09.primenet.com (tlambert@usr09.primenet.com [206.165.6.209]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA29565; Fri, 26 Sep 1997 04:32:34 -0700 (PDT) Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id EAA19446; Fri, 26 Sep 1997 04:31:46 -0700 (MST) From: Terry Lambert Message-Id: <199709261131.EAA19446@usr09.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 11:31:45 +0000 (GMT) Cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709260913.SAA00775@word.smith.net.au> from "Mike Smith" at Sep 26, 97 06:43:16 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The 127.0.0.1 is not normally something that has anything at all to > > do with the card driver. Instead, it is internally looped back; it > > is a simulated interface. I don't see how shoving the interface > > into promiscuous mode would help. > > Putting the fxp driver into promiscuous mode involves poking at bits > of the interface hardware. This appears to fix whatever it is that's > going wrong. If this problem hasn't already been dealt with in the > -current/-stable drivers, I hope DG is looking at it. So how the heck can pinging the loopback *ever* fail because of an unrelated driver? The only think I can think of is a screwed routing table or a screwed arp table. Yet he says neither of these change when the problem is manifest. Or.... his ethernet card is denial-of-service attacking him?!? Maybe the mbufs are all allocated, so he can't get any for the loopback ping? This could point to a bad driver assumption, like you can transmit when a receive is pending, but the hardware has one queue for both sets of operations, or something eqully idiotic. Or it may be bad code. I still don't see how putting the card into a mode where it will see yet more packets could fix it. There is som suspicious code about preemptively freeing mbufs in som bad cases surrounded by #ifdef's for the BPF. But to trigger, the BPF would have to actually be in the process of being used (ifp->if_bpf != NULL). Hmmm. If this theory is true, then it's likely that what's holding the mbufs is fixed by the fxp_stop() at the top of fxp_init() when the mode is changed. Technically, the SIOCSIFFLAGS case in fxp_ioctl() should fix this with a standard ifconfig down then up. Let's see... This is an interesting problem... I'm going to provide some possible hacks. Normally I don't hack drivers for cards that I don't have available for test and have nop documentation for, but with the wedges you are seeing, these are what I'd try for myself. 8-). *DON'T* mix these patches!!! First, try this patch: ---------------------------------------------------------------------------- Index: if_fxp.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.39 diff -c -r1.39 if_fxp.c *** 1.39 1997/09/05 10:23:54 --- if_fxp.c 1997/09/26 10:24:47 *************** *** 1241,1247 **** cbp->tno_int = 0; /* (disable) tx not okay interrupt */ cbp->ci_int = 0; /* interrupt on CU not active */ cbp->save_bf = prm; /* save bad frames */ ! cbp->disc_short_rx = !prm; /* discard short packets */ cbp->underrun_retry = 1; /* retry mode (1) on DMA underrun */ cbp->mediatype = !sc->phy_10Mbps_only; /* interface mode */ cbp->nsai = 1; /* (don't) disable source addr insert */ --- 1241,1247 ---- cbp->tno_int = 0; /* (disable) tx not okay interrupt */ cbp->ci_int = 0; /* interrupt on CU not active */ cbp->save_bf = prm; /* save bad frames */ ! cbp->disc_short_rx = 0; /* discard short packets */ cbp->underrun_retry = 1; /* retry mode (1) on DMA underrun */ cbp->mediatype = !sc->phy_10Mbps_only; /* interface mode */ cbp->nsai = 1; /* (don't) disable source addr insert */ *************** *** 1253,1259 **** cbp->promiscuous = prm; /* promiscuous mode */ cbp->bcast_disable = 0; /* (don't) disable broadcasts */ cbp->crscdt = 0; /* (CRS only) */ ! cbp->stripping = !prm; /* truncate rx packet to byte count */ cbp->padding = 1; /* (do) pad short tx packets */ cbp->rcv_crc_xfer = 0; /* (don't) xfer CRC to host */ cbp->force_fdx = 0; /* (don't) force full duplex */ --- 1253,1259 ---- cbp->promiscuous = prm; /* promiscuous mode */ cbp->bcast_disable = 0; /* (don't) disable broadcasts */ cbp->crscdt = 0; /* (CRS only) */ ! cbp->stripping = 0; /* truncate rx packet to byte count */ cbp->padding = 1; /* (do) pad short tx packets */ cbp->rcv_crc_xfer = 0; /* (don't) xfer CRC to host */ cbp->force_fdx = 0; /* (don't) force full duplex */ ---------------------------------------------------------------------------- This patch will work if the hardware has a bug that depends on one of these two bits. If this doesn't fix the problem, and you can't reset it by ifconfiging it down and up, but promiscuous mode still works, then there is a bug in fxp_intr() that causes leaks. Most likely, it's an error condition that results in bad packets that's not being caught by the driver. This could be a hardware bug where non-local packets are "leaking", or it could be an otherwise unsignalled bad status. I believe this patch *may* catch these cases (I don't have a hardware manual to check it's correctness, or if the fields hold true out of promiscuous mode: ---------------------------------------------------------------------------- Index: if_fxp.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.39 diff -c -r1.39 if_fxp.c *** 1.39 1997/09/05 10:23:54 --- if_fxp.c 1997/09/26 11:22:40 *************** *** 989,1009 **** bpf_tap(FXP_BPFTAP_ARG(ifp), mtod(m, caddr_t), total_len); - /* - * Only pass this packet up - * if it is for us. - */ - if ((ifp->if_flags & - IFF_PROMISC) && - (rfa->rfa_status & - FXP_RFA_STATUS_IAMATCH) && - (eh->ether_dhost[0] & 1) - == 0) { - m_freem(m); - goto rcvloop; - } } #endif /* NBPFILTER > 0 */ m->m_data += sizeof(struct ether_header); ether_input(ifp, eh, m); --- 989,1013 ---- bpf_tap(FXP_BPFTAP_ARG(ifp), mtod(m, caddr_t), total_len); } #endif /* NBPFILTER > 0 */ + /* + * Only pass this packet up + * if it is for us. + */ + if ( + /* + * XXX remove the next two lines + * XXX and this comment if your + * XXX interface goes away entirely + * XXX with this patch + */ + (rfa->rfa_status & + FXP_RFA_STATUS_IAMATCH) && + (eh->ether_dhost[0] & 1) == 0) { + m_freem(m); + goto rcvloop; + } m->m_data += sizeof(struct ether_header); ether_input(ifp, eh, m); ---------------------------------------------------------------------------- Note the funny thing about this: the old code assumes PROMISC mode, so it *may* be the culprit, *IF* the BPF is present *AND* active, and thus the reason setting PROMISC fixes it. The FXP_RFA_STATUS_IAMATCH may not happen out of PROMISC mode (see comment). If all this fails, then you have an mbuf leak (this should cover the soft reset case, the transmit buffer release, and the realloc/reinit receive buffers, since fxp_stop() does all this and is called on a down then up. If you have an mbuf leak, then its a driver logic bug, and I don't know the hardware well enough to find one of those very easily. On the other hand, if a down-then-up fixes it, then one of the three stops is the unwedger. If it's the card reset, then the hardware is screwed. If it's one of the other, then the code is at fault. It may be that the thing has a single queue, and can't transmit while a recieve is outstanding, or vice versa. Maybe they studdied under the "multidrop" serial board vendors, or at the VMS academy of terminal driver writing both have the one queue problem). If the hardware is screwed, and it is truly pounding on the control bits that gets you back, then *maybe* this patch will fix you; it's a hell of a kludge, but... it pounds the control bits the same way you do manually: ---------------------------------------------------------------------------- Index: if_fxp.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.39 diff -c -r1.39 if_fxp.c *** 1.39 1997/09/05 10:23:54 --- if_fxp.c 1997/09/26 11:02:09 *************** *** 1167,1172 **** --- 1167,1176 ---- log(LOG_ERR, FXP_FORMAT ": device timeout\n", FXP_ARGS(sc)); ifp->if_oerrors++; + /* bletcherous hack to pound bits to unwedge card*/ + ifp->if_flags ^= IFF_PROMISC; /* toggle it*/ + fxp_init(sc); + ifp->if_flags ^= IFF_PROMISC; /* toggle it back*/ fxp_init(sc); } ---------------------------------------------------------------------------- The real pain with this is that (1) it assumes the watchdog is being called (ie: transmits are actually failing), (2) It's take a "long" time... maybe enough for you to feel the hiccup (but nothing you can do about that if the chip is broken), and (3) you're going to get some packets which aren't meant for you in a tiny (but annoying) window. A better fix would call the watchdog when you've been waiting a "long time" for an ACK, so it wouldn't depend on the transmit not functioning; for all I know, it is. 8-( Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Sep 26 04:59:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA00598 for hackers-outgoing; Fri, 26 Sep 1997 04:59:30 -0700 (PDT) Received: from usr09.primenet.com (tlambert@usr09.primenet.com [206.165.6.209]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA00592 for ; Fri, 26 Sep 1997 04:59:27 -0700 (PDT) Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id EAA20125; Fri, 26 Sep 1997 04:59:15 -0700 (MST) From: Terry Lambert Message-Id: <199709261159.EAA20125@usr09.primenet.com> Subject: Re: Timeout for sh(1) 'read' ?? To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 11:59:14 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709260748.RAA00456@word.smith.net.au> from "Mike Smith" at Sep 26, 97 05:18:45 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hiho folks, a question for the sh(1) studs amongst you : > > - I want to prompt for input using 'read', and have the read return in > some fashion after a timeout. > > I'd like to do this just using sh, and I'm not too fussed about how > hairy it is. Any ideas? > > (If sh has to be modified to achieve this, would it be a useful thing > to bring back?) Write a "timedread" program that returns "TIMEOUT" or "USERDATA xxxxx" and do "timedread | read x" and look at the front of x? 8-) 8-). Or you can do it the hard way... Do you have a "force" command? It makes things easier, but it's not an absolute requirement... A very ugly way to achieve this can be done with a command that can TIOCSTI input to yourself. Basically, you: 1) fork (command &) 2) start the read in the child process 3) ls -l the tty to check keyboard activity once a second 4) use an eval to keep a second counter. 5) When it hits the magic number of idle seconds, "force" a cr to the child process. 6) exit the original process and let the child finish it's job with the "default" input. There are several variations on this: o Do you need to keep the original process around instead of baton-relaying to one or more children? You may need to use multiple child processes so that you can use the "jobs" command and write the child PID of the first child to the first child so it can tell it to it's child (I don't know how else to get parent process ID's in sh; sorry). This will probably involve at least a sleep 2 in two processes. 8-(. o Do you want default input, or do you want to distinguish a timeout from anything a user can type? If the latter, then you need to communicate the failure to read to the child, probably using a temp file or a pipe that you've assigned descriptors on. o Do you want to quit counting when there is any activity, like the boot prompt does? You will need to modify the time comparison code accordingly, and exit the watchdog if you do. o Do you not have a "force"? You will need a third process; do the watchdog, and do the read in the third process. Use a pipe shared between both kids. If the watchdog fires, kill the child doing the read and write a "WATCHDOG\n" up the pipe. The original process should read the pipe for that, or if the read completes, kill the watchdog if it hasn't killed itself already (see above), and write the result of the read up, like "USERINPUT $x\n". Look for the "WATCHDOG" as input, and if not there, strip the "USERINPUT " off the read result. Ah, my misspent youth, writing complex installs in sh... 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-hackers Fri Sep 26 05:02:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA00772 for hackers-outgoing; Fri, 26 Sep 1997 05:02:22 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA00764 for ; Fri, 26 Sep 1997 05:02:14 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA24601 (5.67b/IDA-1.5 for ); Fri, 26 Sep 1997 14:02:06 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id NAA00775; Fri, 26 Sep 1997 13:38:25 +0200 (CEST) X-Face: " Date: Fri, 26 Sep 1997 13:38:24 +0200 From: Stefan Esser To: "William D. Ward" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Compaq XL 590-PCNet Problem? (jkh sent me) References: <199709252232.RAA25926@b04h32.exu.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199709252232.RAA25926@b04h32.exu.ericsson.se>; from William D. Ward on Thu, Sep 25, 1997 at 05:32:21PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 25, "William D. Ward" wrote: > Perhaps it was some sort of devine province that Jordan decided post the > mini-FAQ (ref. Q-2) shortly after I sent this question to comp.unix.- > freebsd.misc. Or not. It would depend on your faith maybe. > > -- > > Hello, > > This message was originally posted to the freebsd-questions mailing list > > with minimal response. > > I have about 40 of these machines and it would be good if I could > do something useful with them for a change. > > The FreeBSD installation boot floppy did not work for this system (this > is definitely not the norm) so I roled my own using methods I found in > the /usr/src/release directory. > > Please help. > > ---original message posted to freebsd-questions mailing list follows--- > > I'm having some difficulties getting the Ethernet interface to work on > a Compaq Deskpro XL 590. Currently ifconfig on this machine results > in a syslog message reporting 'lnc0: Initialisation failed' (which > perhaps means that the initialization failed). The FreeBSD > installation boot floppy did not work for this system so I roled my own > using methods I found in the /usr/src/release directory. I have about > 40 of these machines and it would be good if I could do something > useful with them for a change. Please help. > > > I am using 2.2.2-RELEASE. My procedure is as follows: > > 1. boot from custom boot floppy that does not go into > /stand/sysinstall but instead starts /etc/rc script containing just > /stand/sh. it also has ifconfig, mount, ping, route, and dmesg > (crunched dmesg isn't working thus no verbose boot info in this note. > i could use some help here too maybe. separate issue). > > 2. boot -c. set port for lnc0 to 0x7000 and continue boot. the > hardware is probed. i see the following: Wrong! This was a workaround to get the ISA Lance probe/attach code to find the PCI Ethernet chip, and is necessary in FreeBSD-2.1.x. I added the code to attach PCI versions of the Lance late last year, and you should no longer use that workaround because it will make the attach fail! > a. pci0:0 is probed but no driver is assigned. (bad sign or not?) That's OK. It is part of the chip set, which has been configured by the BIOS and will be used (of course :) but in no way reconfigured later. > b. lnc1 shown to be detected even though there is only one > interface. this is immediately after pci0:0 is probed. (hmmm) Yes, and you should be using that as the network interface ... > c. lnc0 is shown to be detected later on when the rest of the > Ethernet > interfaces are looked for. Well, and this is where it fails !!! You have attached the same device twice, and two drivers compete for it. > 3. /stand/sh is invoked. from command line issue: > > # ifconfig lnc0 161.76.4.7 > > lnc0: Initialisation failed > ^ ^ ^ > (note case and spelling.) Please do NOT configure lnc0 to probe port 0x7000. Use lnc1 as the name of the network interface. ISA devices are probed after PCI, and the PCI attach could not know whether or not the ISA attach might connect a real ISA Lance card as lnc0. I've prepared the PCI code to support "wired" devices, but since the code for the other bus types has to cooperate, I did not enable that feature, yet. > Other points: > > 1. another point that might be interesting (or not) is that ifconfig -a > reports that there are two lnc interfaces (lnc0 and lnc1) yet there is > only one adapter. configuring either interface yields the same result. Yes. And that's what's confusing both driver instances :) > 3. in looking through the mailing list archive it appears that this has > been a problem in the past for some Compaq platforms. in some cases > resolution may have been obtained by setting the port for lnc0 to 0x7000. > other cases appear to be unresolved faulting Compaq's PCI bus which may > not conform to accepted standards on some models. This was indeed the solution for 2.1.x (FreeBSD-stable as of one year ago). I can't prevent old articles from the mail-archive stating a no longer valid work-around :( > 4. floppies/boot.flp does not work on this system. it appears to hang > when sysinstall would normally display its UI. this is not a problem as > it is possible for me to load the machine manually once the network > interface is configured. it is only a problem in getting verbose boot > messages as the fixit floppy which probably has a working dmesg is not > accessible. Hmmm ? I don't understand what's wrong here. You should be able to complete the boot procedure, if you don't reconfigure lnc0 ... > ---original message ends--- > > Doug White (thanks, Doug) responded to my original post and pointed out > that I did not mentioned that I tried booting without making changes to > the port address. Well, what *exactly* happens if you just boot with "-v" ? Regards, STefan From owner-freebsd-hackers Fri Sep 26 05:04:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA00966 for hackers-outgoing; Fri, 26 Sep 1997 05:04:33 -0700 (PDT) Received: from usr09.primenet.com (tlambert@usr09.primenet.com [206.165.6.209]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA00957 for ; Fri, 26 Sep 1997 05:04:30 -0700 (PDT) Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id FAA20262; Fri, 26 Sep 1997 05:03:50 -0700 (MST) From: Terry Lambert Message-Id: <199709261203.FAA20262@usr09.primenet.com> Subject: Re: ATAPI Zip challenge : aftermath To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 12:03:49 +0000 (GMT) Cc: sos@sos.freebsd.dk, hackers@FreeBSD.ORG In-Reply-To: <199709260946.TAA00895@word.smith.net.au> from "Mike Smith" at Sep 26, 97 07:16:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > (Radar gear can be fun too, but you can't actually _see_ the radiation, > only its effects...) Like the paint peeling off your test van, or birds falling out of the air... 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-hackers Fri Sep 26 05:34:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA02296 for hackers-outgoing; Fri, 26 Sep 1997 05:34:23 -0700 (PDT) Received: from earth.colstate.edu (earth.ColState.EDU [168.26.193.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA02291 for ; Fri, 26 Sep 1997 05:34:20 -0700 (PDT) Received: from colstate.edu (mercury.ColState.EDU [168.26.193.32]) by earth.colstate.edu (8.8.5/8.7.3) with ESMTP id IAA11927 for ; Fri, 26 Sep 1997 08:34:32 -0400 (EDT) Received: from CCMAIN/SpoolDir by colstate.edu (Mercury 1.32); 26 Sep 97 08:32:55 EST Received: from SpoolDir by CCMAIN (Mercury 1.32); 26 Sep 97 08:32:44 EST From: "Christian" Organization: Columbus State Univ., Columbus, Ga. To: hackers@freebsd.org Date: Fri, 26 Sep 1997 08:32:36 EST MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: FreeBSD specialties Priority: normal X-mailer: Pegasus Mail for Windows (v2.52) Message-ID: <6B3545F67@colstate.edu> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, Please ignore this message if you've seen it on other lists, I think I may have posted to the wrong one initially. I have been using FreeBSD since 1994 on our campus to handle many of the internet related tasks for us. Our web server, dns server, dhcp server, etc. all run FreeBSD. All of the things we do are pretty basic, and do not really take particular advantage of some advanced FreeBSD features, such as CCD, etc. So I do not know much about the bleeding-edge FreeBSD stuff. Anyways, one of my questions is, Are there things/features/capabilities in FreeBSD that other Operating Systems do not have? I'm not asking if FreeBSD does something better (i.e. webserving) , but if it does something others do not. Maybe freebsd has this special network service called xyz that other OSs do not have (this is an example). Also, what can FreeBSD do that linux cannot? (I ask this because FreeBSD does everything I need so well, that I have never really had the need/desire to install linux for comparison) Another question I had was versions of BSDI, Linux, and SCO can the various versions of FreeBSD emulate. Does -current, for example, support a higher version of BSDI binaries than -release? And what particular versions do they support, respectively? Thanks in advance, C.P. ---------------------------------------------- Christian Plazas Columbus State University (706)568-2063 From owner-freebsd-hackers Fri Sep 26 05:59:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA03282 for hackers-outgoing; Fri, 26 Sep 1997 05:59:16 -0700 (PDT) Received: from pobox.com (bacrana-47.mdm.mke.execpc.com [169.207.66.51]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA03276 for ; Fri, 26 Sep 1997 05:59:12 -0700 (PDT) Message-Id: <199709261259.FAA03276@hub.freebsd.org> Received: (qmail 15468 invoked from network); 26 Sep 1997 07:58:02 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 26 Sep 1997 07:58:02 -0500 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? In-reply-to: Your message of "Fri, 26 Sep 1997 11:59:14 -0000." <199709261159.EAA20125@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 07:58:02 -0500 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199709261159.EAA20125@usr09.primenet.com>, Terry Lambert writes: } > Hiho folks, a question for the sh(1) studs amongst you : } > } > - I want to prompt for input using 'read', and have the read return in } > some fashion after a timeout. } > } > I'd like to do this just using sh, and I'm not too fussed about how } > hairy it is. Any ideas? } > } > (If sh has to be modified to achieve this, would it be a useful thing } > to bring back?) } } Write a "timedread" program that returns "TIMEOUT" or "USERDATA xxxxx" } and do "timedread | read x" and look at the front of x? 8-) 8-). Which will of course execute in a subshell because of the pipe and wind up doing you no good. You can do this kind of thing with background processes and trap, but it's not what you'd call pretty, and even that isn't as straightforward as it might sound. From owner-freebsd-hackers Fri Sep 26 06:33:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA04834 for hackers-outgoing; Fri, 26 Sep 1997 06:33:09 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA04828 for ; Fri, 26 Sep 1997 06:33:05 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id PAA26105 for ; Fri, 26 Sep 1997 15:33:06 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id PAA06145 for freebsd-hackers@freefall.cdrom.com; Fri, 26 Sep 1997 15:40:09 +0200 (MEST) Date: Fri, 26 Sep 1997 15:40:09 +0200 (MEST) From: Christoph Kukulies Message-Id: <199709261340.PAA06145@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: diskless 100 Mbit - IntelEtherexpress - Q Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Would it be possible with the present status of network drivers/netboot to build a diskless 100 MBit (Fast Ethernet) setup of workstations? Would the Intel Etherexpress card be appropriate HW? I see an empty socket on the board but it's unclear to me whether this is for an EPROM. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Fri Sep 26 07:02:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA05956 for hackers-outgoing; Fri, 26 Sep 1997 07:02:03 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA05885 for ; Fri, 26 Sep 1997 07:00:56 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA00131; Fri, 26 Sep 1997 14:43:46 +0200 From: Luigi Rizzo Message-Id: <199709261243.OAA00131@labinfo.iet.unipi.it> Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Fri, 26 Sep 1997 14:43:46 +0200 (MET DST) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199709261340.PAA06145@gil.physik.rwth-aachen.de> from "Christoph Kukulies" at Sep 26, 97 03:39:50 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Would it be possible with the present status of network drivers/netboot > to build a diskless 100 MBit (Fast Ethernet) setup of workstations? > > Would the Intel Etherexpress card be appropriate HW? I see an empty > socket on the board but it's unclear to me whether this is for an > EPROM. it could be for an eprom but we don't have eprom support for 100 mbit cards anyways. the way I do it now is to use a boot floppy with a kernel on it and the diskless stuff that Tor Egge wrote and recently (march-april ?) was committed. as an alternative you can boot off a 10mbit/s "ed"-like card and use an additional card for 100 mbit/s Luigi From owner-freebsd-hackers Fri Sep 26 07:25:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA06999 for hackers-outgoing; Fri, 26 Sep 1997 07:25:48 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA06980; Fri, 26 Sep 1997 07:25:38 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA25055; Fri, 26 Sep 1997 07:26:28 -0700 (PDT) Message-Id: <199709261426.HAA25055@implode.root.com> To: Mike Smith cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 18:43:16 +0930." <199709260913.SAA00775@word.smith.net.au> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 07:26:27 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Putting the fxp driver into promiscuous mode involves poking at bits >of the interface hardware. This appears to fix whatever it is that's >going wrong. If this problem hasn't already been dealt with in the >-current/-stable drivers, I hope DG is looking at it. The card doesn't need to be put into promiscuous mode. Doing that has the side effect of resetting the chip, which is all that is really needed. This can be accomplished by doing a simple "ifconfig fxp0 up". There isn't anything wrong with the driver and working around the bug in the hardware is difficult since there are no symptoms other than packets not coming in anymore. The problem is well known and is covered in the errata for the 82557 chip. Let me say again that this bug should only show itself when there is something wrong on the network and usually only when the card is in 10Mbps mode. I haven't seen a failure in the 9+ months that I've used the Pro/100B in wcarchive, it's never happened here locally under regular usage (I use these cards in about 5 machines), and in fact I've only seen it occur myself when I've killed the power on my hub. Yahoo was having this occur whenever the ISP power cycled the switch that the machines were connected to, and I think they worked around it with some sort of ping/ifconfig cron job. One of these days I'll conjure up some sort of hack to fix the problem. Intel recommends reprogramming the multicast filter (!) if no packets are received for some number of seconds. This is difficult to implement in the current design of the driver. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Sep 26 07:30:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07344 for hackers-outgoing; Fri, 26 Sep 1997 07:30:34 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07324; Fri, 26 Sep 1997 07:30:28 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA25105; Fri, 26 Sep 1997 07:31:43 -0700 (PDT) Message-Id: <199709261431.HAA25105@implode.root.com> To: Terry Lambert cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 11:31:45 -0000." <199709261131.EAA19446@usr09.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 07:31:43 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >This is an interesting problem... I'm going to provide some possible >hacks. Normally I don't hack drivers for cards that I don't have Wrong on all accounts. Let's not cloud the issue with irrelevant information and wrong patches. It's difficult enough for me to provide accurate information without having to battle misinformation. Thanks. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Sep 26 07:34:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07698 for hackers-outgoing; Fri, 26 Sep 1997 07:34:31 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07689 for ; Fri, 26 Sep 1997 07:34:25 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id QAA28365; Fri, 26 Sep 1997 16:34:13 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id QAA06311; Fri, 26 Sep 1997 16:41:24 +0200 (MEST) Message-ID: <19970926164123.16634@gil.physik.rwth-aachen.de> Date: Fri, 26 Sep 1997 16:41:23 +0200 From: Christoph Kukulies To: Luigi Rizzo Cc: Christoph Kukulies , freebsd-hackers@freefall.FreeBSD.org Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q References: <199709261340.PAA06145@gil.physik.rwth-aachen.de> <199709261243.OAA00131@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709261243.OAA00131@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Sep 26, 1997 at 02:43:46PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Sep 26, 1997 at 02:43:46PM +0200, Luigi Rizzo wrote: > > Would it be possible with the present status of network drivers/netboot > > to build a diskless 100 MBit (Fast Ethernet) setup of workstations? > > > > Would the Intel Etherexpress card be appropriate HW? I see an empty > > socket on the board but it's unclear to me whether this is for an > > EPROM. > > it could be for an eprom but we don't have eprom support for 100 > mbit cards anyways. > > the way I do it now is to use a boot floppy with a kernel on it and the > diskless stuff that Tor Egge wrote and recently (march-april ?) was > committed. > > as an alternative you can boot off a 10mbit/s "ed"-like card and use an > additional card for 100 mbit/s Yeah, but I'd like the raw speed of 100MBit at bootup time also. Would be very impressive to boot off the net in a few seconds. > > Luigi -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Fri Sep 26 07:57:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA08860 for hackers-outgoing; Fri, 26 Sep 1997 07:57:05 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA08611 for ; Fri, 26 Sep 1997 07:51:57 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA00303; Fri, 26 Sep 1997 15:21:28 +0200 From: Luigi Rizzo Message-Id: <199709261321.PAA00303@labinfo.iet.unipi.it> Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Fri, 26 Sep 1997 15:21:28 +0200 (MET DST) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19970926164123.16634@gil.physik.rwth-aachen.de> from "Christoph Kukulies" at Sep 26, 97 04:41:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Yeah, but I'd like the raw speed of 100MBit at bootup time also. > Would be very impressive to boot off the net in a few seconds. are you volunteering to write the code ? :) In any case even at 10 mbit/s your boot time is 2-4 seconds, most of the time is spent afterwards in probing non-existent devices. Cheers Luigi From owner-freebsd-hackers Fri Sep 26 08:07:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA09242 for hackers-outgoing; Fri, 26 Sep 1997 08:07:37 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA09227 for ; Fri, 26 Sep 1997 08:07:34 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [204.141.95.138]) by etinc.com (8.8.3/8.6.9) with SMTP id LAA04775; Fri, 26 Sep 1997 11:10:27 -0400 (EDT) Message-Id: <3.0.32.19970926110236.00abfa18@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 26 Sep 1997 11:02:37 -0400 To: Luigi Rizzo , kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) From: dennis Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q Cc: freebsd-hackers@freefall.FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 02:43 PM 9/26/97 +0200, Luigi Rizzo wrote: >> Would it be possible with the present status of network drivers/netboot >> to build a diskless 100 MBit (Fast Ethernet) setup of workstations? >> >> Would the Intel Etherexpress card be appropriate HW? I see an empty >> socket on the board but it's unclear to me whether this is for an >> EPROM. > >it could be for an eprom but we don't have eprom support for 100 >mbit cards anyways. > >the way I do it now is to use a boot floppy with a kernel on it and the >diskless stuff that Tor Egge wrote and recently (march-april ?) was >committed. > >as an alternative you can boot off a 10mbit/s "ed"-like card and use an >additional card for 100 mbit/s Is this in the 2.2 release? Is there a doc? Dennis From owner-freebsd-hackers Fri Sep 26 08:15:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA09801 for hackers-outgoing; Fri, 26 Sep 1997 08:15:14 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA09794 for ; Fri, 26 Sep 1997 08:15:10 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA01871; Sat, 27 Sep 1997 00:41:58 +0930 (CST) Message-Id: <199709261511.AAA01871@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jon Hamilton cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? In-reply-to: Your message of "Fri, 26 Sep 1997 07:58:02 EST." <199709261259.FAA03276@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Sep 1997 00:41:56 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > } > > } > - I want to prompt for input using 'read', and have the read return in > } > some fashion after a timeout. > } > > } > I'd like to do this just using sh, and I'm not too fussed about how > } > hairy it is. Any ideas? > } > > } > (If sh has to be modified to achieve this, would it be a useful thing > } > to bring back?) ... > You can do this kind of thing with background processes and trap, but > it's not what you'd call pretty, and even that isn't as straightforward > as it might sound. In other words, it would be a good thing for read to have a timeout option : correct? Any objections? mike From owner-freebsd-hackers Fri Sep 26 08:55:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA12186 for hackers-outgoing; Fri, 26 Sep 1997 08:55:39 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12165; Fri, 26 Sep 1997 08:55:34 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id IAA02046; Fri, 26 Sep 1997 08:56:42 -0700 (PDT) Date: Fri, 26 Sep 1997 08:56:42 -0700 (PDT) From: Jim Shankland Message-Id: <199709261556.IAA02046@biggusdiskus.flyingfox.com> To: tarkhil@mgt.msk.ru Subject: fxp driver problem? Cc: hackers@freebsd.org, stable@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Re Alex Povolotsky's problem (fxp driver becomes unresponsive, putting it into promiscuous mode briefly makes it work again): I am getting sporadic reports of a similar (or the same) problem with the fxp driver running on a hacked-up (by me) version of the 2.2.2-RELEASE kernel. In our case, the fxp driver becomes unresponsive, bringing the interface down and back up again with ifconfig brings it back to life. I will likely be putting some effort into tracking this one down. This is complicated by the fact that the failure happens only on a heavily used interface on a production system, and happens maybe once a month at most. If anyone (dg?) has ideas on what to instrument to figure out what's going on, I'm all ears :-). Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Fri Sep 26 09:16:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA13463 for hackers-outgoing; Fri, 26 Sep 1997 09:16:37 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA13447; Fri, 26 Sep 1997 09:16:29 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA02310; Fri, 26 Sep 1997 09:17:32 -0700 (PDT) Date: Fri, 26 Sep 1997 09:17:32 -0700 (PDT) From: Jim Shankland Message-Id: <199709261617.JAA02310@biggusdiskus.flyingfox.com> To: dg@root.com Subject: Re: fxp driver/chip problems Cc: hackers@freebsd.org, stable@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the information, David. OK, I won't go off hunting for a bug in the fxp driver :-). As another data point, in my case, it's the rev 1 card, and it's in 10 Mb mode. Unfortunately, I have no control over the hub being used, so I'll need to either upgrade to a rev 2 card, and hope that "Intel (rev 2) inside" fixes it, or (sigh) write a little "ping daemon" that resets the interface after several lost ping packets to the gateway on the wire. The things I stoop to :-)! Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Fri Sep 26 09:39:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA14940 for hackers-outgoing; Fri, 26 Sep 1997 09:39:33 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA14931 for ; Fri, 26 Sep 1997 09:39:27 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id MAA24189 for ; Fri, 26 Sep 1997 12:39:15 -0400 (EDT) Date: Fri, 26 Sep 1997 12:39:15 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: thickwisre<->thinwire Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm doing a bit of computer re-arrangement (keeps my life interesting) and I find I have to connect another computer to my existing home ethernet. Trouble is, the ethernet is thinwire, and the new computer (a DECStation 5000/120, which will be running NetBSD) is thickwire. I'm going to be connecting it to my two existing FreeBSD boxes. Does anyone know where I could go to get a thickwire to thinwire converter? I've not had any luck searching it out yet. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Sep 26 09:50:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA15543 for hackers-outgoing; Fri, 26 Sep 1997 09:50:54 -0700 (PDT) Received: from pluto.njcc.com (root@pluto.njcc.com [165.254.117.52]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA15537 for ; Fri, 26 Sep 1997 09:50:50 -0700 (PDT) Received: from khansen.cc.bellcore.com (khansen.cc.bellcore.com [128.96.164.203]) by pluto.njcc.com (8.8.7/8.8.3) with SMTP id MAA18549; Fri, 26 Sep 1997 12:45:25 -0400 (EDT) Message-ID: <342BE6B3.27A5@njcc.com> Date: Fri, 26 Sep 1997 12:45:39 -0400 From: Ken Hansen Reply-To: khansen@njcc.com Organization: Dis X-Mailer: Mozilla 3.01Gold (Win16; I) MIME-Version: 1.0 To: Christoph Kukulies CC: Luigi Rizzo , freebsd-hackers@freefall.FreeBSD.org Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q References: <199709261340.PAA06145@gil.physik.rwth-aachen.de> <199709261243.OAA00131@labinfo.iet.unipi.it> <19970926164123.16634@gil.physik.rwth-aachen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Christoph Kukulies wrote: > > On Fri, Sep 26, 1997 at 02:43:46PM +0200, Luigi Rizzo wrote: > > the way I do it now is to use a boot floppy with a kernel on it and the > > diskless stuff that Tor Egge wrote and recently (march-april ?) was > > committed. > > > > as an alternative you can boot off a 10mbit/s "ed"-like card and use an > > additional card for 100 mbit/s > > Yeah, but I'd like the raw speed of 100MBit at bootup time also. > Would be very impressive to boot off the net in a few seconds. Where I work we have many unix workstations that have 200-500 Meg HDs that only hold swap & /tmp, everything else is from a file server, very nice arrangement, making these workstations "nearly" diskless. They boot fairly quickly, and even a complete catasrophic HW failure (on the workstation) doesn't harm data. As a by product, a user can log in to any of the workstations and have their environment independent of which machine they are on. This is a fairly common arrangement, but true diskless WS are just one short hop from an X Terminal - I would think about adding a small drive to the PC (how much could a 100 Meg IDE drive cost?) and install the boot config there. BTW I believe Sun has droped support for true diskless workstations, in stead they have CacheFS clients, where the machine boots off the server, but keeps a cache of NFS files accessed on a local HD - that drive is cleared on reboot. Just wnated to throw in my .02 worth. Ken khansen@njcc.com From owner-freebsd-hackers Fri Sep 26 09:51:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA15615 for hackers-outgoing; Fri, 26 Sep 1997 09:51:55 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA15599 for ; Fri, 26 Sep 1997 09:51:43 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA00570; Fri, 26 Sep 1997 17:31:29 +0200 From: Luigi Rizzo Message-Id: <199709261531.RAA00570@labinfo.iet.unipi.it> Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q To: dennis@etinc.com (dennis) Date: Fri, 26 Sep 1997 17:31:29 +0200 (MET DST) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <3.0.32.19970926110236.00abfa18@etinc.com> from "dennis" at Sep 26, 97 11:02:18 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >the way I do it now is to use a boot floppy with a kernel on it and the > >diskless stuff that Tor Egge wrote and recently (march-april ?) was > >committed. > > > >as an alternative you can boot off a 10mbit/s "ed"-like card and use an > >additional card for 100 mbit/s > > Is this in the 2.2 release? Is there a doc? not sure. I am using backported versions in 2.1.X and 2.2.X . there is a minor differerence between 2.X and 3.X for some additional parameter in I forget which function. In any case the relevant files are /sys/nfs/boot_subr.c, /sys/nfs/krpc* and one minor modification to /sys/netinet/ip_input.c (I think) . MOre details in the CVS tree or my freebsd page http://www.iet.unipi.it/~luigi/FreeBSD.html Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Fri Sep 26 10:06:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16358 for hackers-outgoing; Fri, 26 Sep 1997 10:06:39 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16350 for ; Fri, 26 Sep 1997 10:06:34 -0700 (PDT) Received: from argus.tfs.net (pm3-p4.tfs.net [206.154.183.196]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id LAA00135 for ; Fri, 26 Sep 1997 11:05:01 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id MAA01486 for freebsd-hackers@freebsd.org; Fri, 26 Sep 1997 12:06:28 -0500 (CDT) From: Jim Bryant Message-Id: <199709261706.MAA01486@argus.tfs.net> Subject: comconsole To: freebsd-hackers@freebsd.org Date: Fri, 26 Sep 1997 12:06:26 -0500 (CDT) Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk how do you configure the comconsole on /dev/ttyd2 ??? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Fri Sep 26 10:25:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17183 for hackers-outgoing; Fri, 26 Sep 1997 10:25:19 -0700 (PDT) Received: from canario.fiscodata (tty816.netpar.com.br [200.255.244.88] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA17176 for ; Fri, 26 Sep 1997 10:25:13 -0700 (PDT) Received: from canario.fiscodata (canario.fiscodata [192.168.0.1]) by canario.fiscodata (8.8.7/8.8.5) with SMTP id OAA09134; Fri, 26 Sep 1997 14:23:46 GMT Date: Fri, 26 Sep 1997 14:23:46 +0000 (GMT) From: Paulo Cesar Pereira de Andrade X-Sender: paulo@canario.fiscodata Reply-To: Paulo Cesar Pereira de Andrade To: Jon Hamilton cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? In-Reply-To: <199709261259.FAA03276@hub.freebsd.org> Message-ID: X-FreeBSD: The Operating System X-Window-System: The Windowing System MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Jon Hamilton wrote: > In message <199709261159.EAA20125@usr09.primenet.com>, Terry Lambert writes: > } > Hiho folks, a question for the sh(1) studs amongst you : > } > > } > - I want to prompt for input using 'read', and have the read return in > } > some fashion after a timeout. > } > > } > I'd like to do this just using sh, and I'm not too fussed about how > } > hairy it is. Any ideas? > } > > } > (If sh has to be modified to achieve this, would it be a useful thing > } > to bring back?) > } > } Write a "timedread" program that returns "TIMEOUT" or "USERDATA xxxxx" > } and do "timedread | read x" and look at the front of x? 8-) 8-). > > Which will of course execute in a subshell because of the pipe and wind > up doing you no good. > > You can do this kind of thing with background processes and trap, but > it's not what you'd call pretty, and even that isn't as straightforward > as it might sound. What about dd if=/dev/stdin of=/dev/stdout skip=0 | read x I have been reading this list for time enough to know that Terry loves it. :) -- Paulo Cesar Pereira de Andrade - mailto:paulo@netpar.com.br FreeBSD - http://www.freebsd.org XFree86 - http://www.xfree86.org From owner-freebsd-hackers Fri Sep 26 10:35:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17815 for hackers-outgoing; Fri, 26 Sep 1997 10:35:58 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA17810 for ; Fri, 26 Sep 1997 10:35:54 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id DAA02346; Sat, 27 Sep 1997 03:03:19 +0930 (CST) Message-Id: <199709261733.DAA02346@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: FreeBSD-Hackers Subject: Re: thickwisre<->thinwire In-reply-to: Your message of "Fri, 26 Sep 1997 12:39:15 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Sep 1997 03:03:17 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > I find I have to connect another computer to my existing home ethernet. > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > connecting it to my two existing FreeBSD boxes. It's not "thickwire" as such; the Decstations have AUI connectors to which you can attach a thinwire transciever. > Does anyone know where I could go to get a thickwire to thinwire > converter? I've not had any luck searching it out yet. A 10b2 transciever shouldn't cost you more than a few bucks; if you were closer I'd give you a freebie (we have a boxful of them here). With any luck you should be able to find one at a decent surplus outlet. You're looking for a small box about the size of a large box of matches (though some are much larger) with a D15 on one end and a BNC on the other. Note that you may need a cable for it, depending on size and the amount of free space you have behind your DS. mike From owner-freebsd-hackers Fri Sep 26 10:38:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17912 for hackers-outgoing; Fri, 26 Sep 1997 10:38:07 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA17907 for ; Fri, 26 Sep 1997 10:38:04 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id TAA04140; Fri, 26 Sep 1997 19:37:50 +0200 (MEST) From: Søren Schmidt Message-Id: <199709261737.TAA04140@sos.freebsd.dk> Subject: Re: thickwisre<->thinwire In-Reply-To: from Chuck Robey at "Sep 26, 97 12:39:15 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 26 Sep 1997 19:37:50 +0200 (MEST) Cc: FreeBSD-Hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Chuck Robey who wrote: > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > I find I have to connect another computer to my existing home ethernet. > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > connecting it to my two existing FreeBSD boxes. > > Does anyone know where I could go to get a thickwire to thinwire > converter? I've not had any luck searching it out yet. Does the DECStation connect via an AUI cable ?? Then you just need one of those little gizmos that plug in to the AUI connector and has a BNC connector in the other end.... Or you could get nasty and get a connector that fits on the end of the think cable and a converter from that to BNC, both cables are 50 Ohms, so it works, just is a bit unusual :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Fri Sep 26 10:38:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17962 for hackers-outgoing; Fri, 26 Sep 1997 10:38:27 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA17937 for ; Fri, 26 Sep 1997 10:38:17 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <51911(1)>; Fri, 26 Sep 1997 10:36:30 PDT Received: by crevenia.parc.xerox.com id <177486>; Fri, 26 Sep 1997 10:36:20 -0700 From: Bill Fenner To: FreeBSD-Hackers@freebsd.org, chuckr@glue.umd.edu Subject: Re: thickwisre<->thinwire Message-Id: <97Sep26.103620pdt.177486@crevenia.parc.xerox.com> Date: Fri, 26 Sep 1997 10:36:13 PDT Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Does anyone know where I could go to get a thickwire to thinwire >converter? I've not had any luck searching it out yet. It's called a "transceiver" - you can get them for thinwire(BNC) or 10baseT. They're probably getting harder to find now that pretty much all new equipment is 10baseT, but you can surely find one somewhere. Bill From owner-freebsd-hackers Fri Sep 26 10:47:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18534 for hackers-outgoing; Fri, 26 Sep 1997 10:47:56 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18514 for ; Fri, 26 Sep 1997 10:47:46 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id NAA00891; Fri, 26 Sep 1997 13:46:59 -0400 (EDT) Date: Fri, 26 Sep 1997 13:46:59 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Mike Smith cc: FreeBSD-Hackers Subject: Re: thickwisre<->thinwire In-Reply-To: <199709261733.DAA02346@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Mike Smith wrote: > > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > > I find I have to connect another computer to my existing home ethernet. > > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > > connecting it to my two existing FreeBSD boxes. > > It's not "thickwire" as such; the Decstations have AUI connectors to > which you can attach a thinwire transciever. > > > Does anyone know where I could go to get a thickwire to thinwire > > converter? I've not had any luck searching it out yet. > > A 10b2 transciever shouldn't cost you more than a few bucks; if you > were closer I'd give you a freebie (we have a boxful of them here). > With any luck you should be able to find one at a decent surplus outlet. > > You're looking for a small box about the size of a large box of matches > (though some are much larger) with a D15 on one end and a BNC on the > other. Note that you may need a cable for it, depending on size and > the amount of free space you have behind your DS. I have one already, because one of my two SMC cards is thickwire. I had certainly ignored the fact that it's thick ... yeah, I'll need a short stub, thanks for pointing that out. I went thru several vendors looking for the converter. I guess I'll try a local hamfest. > > mike > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Sep 26 10:51:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18726 for hackers-outgoing; Fri, 26 Sep 1997 10:51:31 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18719 for ; Fri, 26 Sep 1997 10:51:26 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id NAA00985; Fri, 26 Sep 1997 13:48:45 -0400 (EDT) Date: Fri, 26 Sep 1997 13:48:45 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: thickwisre<->thinwire In-Reply-To: <199709261737.TAA04140@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA18720 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Søren Schmidt wrote: > In reply to Chuck Robey who wrote: > > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > > I find I have to connect another computer to my existing home ethernet. > > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > > connecting it to my two existing FreeBSD boxes. > > > > Does anyone know where I could go to get a thickwire to thinwire > > converter? I've not had any luck searching it out yet. > > Does the DECStation connect via an AUI cable ?? > Then you just need one of those little gizmos that plug in to the > AUI connector and has a BNC connector in the other end.... > Or you could get nasty and get a connector that fits on the end of > the think cable and a converter from that to BNC, both cables are > 50 Ohms, so it works, just is a bit unusual :) Oh, yeah? Didn't know that. If I get desperate in locating the converter, I'll try that as a backup. The DECStation has the AUI connector on the back. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Sep 26 10:53:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18850 for hackers-outgoing; Fri, 26 Sep 1997 10:53:31 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA18842 for ; Fri, 26 Sep 1997 10:53:27 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id NAA24094; Fri, 26 Sep 1997 13:52:06 -0400 Date: Fri, 26 Sep 1997 13:52:05 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Ken Hansen cc: Christoph Kukulies , Luigi Rizzo , freebsd-hackers@freefall.FreeBSD.org Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q In-Reply-To: <342BE6B3.27A5@njcc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Ken Hansen wrote: > > BTW I believe Sun has droped support for true diskless workstations, > in stead they have CacheFS clients, where the machine boots off the > server, but keeps a cache of NFS files accessed on a local HD - that > drive is cleared on reboot. well, time to dust off my autocacher mention once again. FWIW, there is a public domain cachefs equivalent I wrote in 1989 (i.e. pre-cachefs) which could be used to do this. It's based on amd. source and the paper on my web page at www.sarnoff.com:8000/metacomputing.html yes, the code needs work. But it did in fact work, six years ago ... if anyone has the time (I don't) it could be neat to have this going. ron From owner-freebsd-hackers Fri Sep 26 10:56:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA19033 for hackers-outgoing; Fri, 26 Sep 1997 10:56:32 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA19027 for ; Fri, 26 Sep 1997 10:56:29 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id MAA12265 for ; Fri, 26 Sep 1997 12:56:28 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA01462; Fri, 26 Sep 1997 12:56:28 -0500 (CDT) Message-ID: <19970926125627.23760@Mars.Mcs.Net> Date: Fri, 26 Sep 1997 12:56:27 -0500 From: Karl Denninger To: hackers@freebsd.org Subject: Instability between NFS v2 and v3 issues? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I have a question... Operating environment is -current. There are several NFS servers and clients involved. We have found that with the default options for the mount (which I presume defaults to NFS V3) the system will sometimes get into an odd state where a file which is removed on one client *NEVER* goes away on another. That is, the following is a dangerous thing to do: mv file1 file2 cp xxx file1 To replace a file. If you do that, on machine #2, which also mounts the same disk, you may NEVER see file1 go away and get replaced. This is obviously screwed up! I'm assuming that the client and server are negotiating NFS V3 by default (we are running FreeBSD on both client and server). If I force V2 protocol, then I get a different problem -- random hangs without any error message being displayed or otherwise made known. That is, I get a random hang of the transfer; it just stops in a "D" wait, is unkillable, and there is no fix other than a reboot. Anyone seen either of these and have any ideas? The hangs in protocol version 2 are against kernels all compiled within the last month; the odd V3 behavior is against servers which have a kernel that is 2-3 months old. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-hackers Fri Sep 26 11:15:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19946 for hackers-outgoing; Fri, 26 Sep 1997 11:15:34 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA19935 for ; Fri, 26 Sep 1997 11:15:27 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xEeuS-0003oR-00; Fri, 26 Sep 1997 11:14:36 -0700 Date: Fri, 26 Sep 1997 11:14:36 -0700 (PDT) From: Tom To: Bill Fenner cc: FreeBSD-Hackers@freebsd.org, chuckr@glue.umd.edu Subject: Re: thickwisre<->thinwire In-Reply-To: <97Sep26.103620pdt.177486@crevenia.parc.xerox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Bill Fenner wrote: > >Does anyone know where I could go to get a thickwire to thinwire > >converter? I've not had any luck searching it out yet. > > It's called a "transceiver" - you can get them for thinwire(BNC) or > 10baseT. They're probably getting harder to find now that pretty much > all new equipment is 10baseT, but you can surely find one somewhere. They are still pretty easy to find. A lot of common networking gear (ex. Cisco 2501) only have AUI interfaces, so it up to the user to add the appropriate transceiver to get the desired media type. > Bill Tom From owner-freebsd-hackers Fri Sep 26 11:25:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA20418 for hackers-outgoing; Fri, 26 Sep 1997 11:25:04 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA20408 for ; Fri, 26 Sep 1997 11:25:00 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id DAA04965 for ; Sat, 27 Sep 1997 03:52:45 +0930 (CST) Message-Id: <199709261822.DAA04965@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@freebsd.org Subject: More ATAPI Zip news (will he ever shut up?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Sep 1997 03:52:43 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just keeping people informed; the latest Award BIOS *does* appear to be able to boot from the ATAPI Zip. Curiouser and curiouser. mike From owner-freebsd-hackers Fri Sep 26 11:42:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA21313 for hackers-outgoing; Fri, 26 Sep 1997 11:42:44 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA21308 for ; Fri, 26 Sep 1997 11:42:40 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id UAA18585 for ; Fri, 26 Sep 1997 20:42:48 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id UAA16780 for freebsd-hackers@FreeBSD.ORG; Fri, 26 Sep 1997 20:42:20 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id UAA03932; Fri, 26 Sep 1997 20:41:53 +0200 (CEST) Message-ID: <19970926204152.11761@keltia.freenix.fr> Date: Fri, 26 Sep 1997 20:41:52 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: comconsole References: <199709261706.MAA01486@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199709261706.MAA01486@argus.tfs.net>; from Jim Bryant on Fri, Sep 26, 1997 at 12:06:26PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jim Bryant: > how do you configure the comconsole on /dev/ttyd2 ??? You go to /sys/i386/boot/biosboot and read README.serial. It has the following in it... - Using a port other than COM1 as the console requires some recompiling. Again, it's usually assumed that COM1 will be available for use as a console device on a dedicated file/compute/terminal server, so hopefully you'll never need to do this. But if you feel you must change the console to a different port, here's how: o Get the kernel source package. o Edit /etc/make.conf and set BOOT_COMCONSOLE_PORT to the address of the port you want to use (0x3F8, 0x2F8, 0x3E8 or 0x2E8). Only COM1 through COM4 can be used; multiport serial cards will not work. No interrupt setting is needed. o Create a custom kernel configuration file and add appropriate `flags' for the serial port you want to use. For example, if you want to make COM2 the console: device sio1 at isa? port "IO_COM2" tty flags 0x10 irq 3 vector siointr The console flags for the other serial ports should not be set. o Recompile both the boot blocks and the kernel. o Install the boot blocks with the disklabel command and boot from the new kernel. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-hackers Fri Sep 26 12:01:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22238 for hackers-outgoing; Fri, 26 Sep 1997 12:01:11 -0700 (PDT) Received: from ingenieria ([168.176.15.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA22227 for ; Fri, 26 Sep 1997 12:01:04 -0700 (PDT) Received: from unalmodem.usc.unal.edu.co by ingenieria (SMI-8.6/SMI-SVR4) id OAA05455; Fri, 26 Sep 1997 14:44:50 -0400 Message-ID: <342BF562.266B@asme.org> Date: Fri, 26 Sep 1997 10:48:18 -0700 From: "Pedro Giffuni S," Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.01Gold [it] (Win16; I) MIME-Version: 1.0 To: Mike Smith CC: Terry Lambert , bartol@salk.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: problem compiling for linux under compat_linux References: <199709260818.RAA00553@word.smith.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith wrote: > > > I've never thought running a Linux compiler in > > a compat directory would work because it would invoke FreeBSD pieces > > for hidden components. > > It doesn't. About the only time you trip up is when something like > autoconf goes looking for things (most especially ranlib) and finds the > FreeBSD version because there isn't a Linux one. > I've always thought we should use crosscompilers (like SCO's) and not emulated native compilers. It has the advantage of not requiring emulation and of handling better autoconf. I would like to hear some feedback if I should build a Linux crossgcc, like I did for SCO. Beware, the native Linux compiler has two advantages that I know of: 1) It comes out of the box with all the libraries required for X and network support, something that would require additional packages for a FreeBSD crosscompiler. 2) It behaves exactly like the original compiler and is always a good way of testing the emulator :^). Pedro. From owner-freebsd-hackers Fri Sep 26 12:17:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22874 for hackers-outgoing; Fri, 26 Sep 1997 12:17:48 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA22869 for ; Fri, 26 Sep 1997 12:17:44 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA13779 (5.67b/IDA-1.5 for FreeBSD-Hackers@FreeBSD.ORG); Fri, 26 Sep 1997 21:18:30 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id TAA01396; Fri, 26 Sep 1997 19:52:07 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709261752.TAA01396@yedi.iaf.nl> Subject: Re: thickwisre<->thinwire To: chuckr@Glue.umd.edu (Chuck Robey) Date: Fri, 26 Sep 1997 19:52:07 +0200 (MET DST) Cc: FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Sep 26, 97 12:39:15 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote... > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > I find I have to connect another computer to my existing home ethernet. > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > connecting it to my two existing FreeBSD boxes. It probably has an AUI 15 pin D connector. Just find a thinwire tranceiver, they are quite abundant. Or if you have an AUI-10base5 tranceiver, rewire it to use a BNC connector. The electronics are the same for 10base2 and 10base5 (at least they are not distinguishable in normal use) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Fri Sep 26 13:37:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26488 for hackers-outgoing; Fri, 26 Sep 1997 13:37:00 -0700 (PDT) Received: from iago.ienet.com (iago.ienet.com [207.78.32.53]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26483 for ; Fri, 26 Sep 1997 13:36:57 -0700 (PDT) Received: from iago.ienet.com (localhost.ienet.com [127.0.0.1]) by iago.ienet.com (8.8.5/8.8.5) with ESMTP id NAA09474 Fri, 26 Sep 1997 13:36:42 -0700 (PDT) Message-Id: <199709262036.NAA09474@iago.ienet.com> From: pius@ienet.com To: dg@root.com Cc: hackers@FreeBSD.ORG, terryl@ienet.com Subject: fxp driver/Intel EtherExpress Pro 10/100B problem (was Re: your mail) Date: Fri, 26 Sep 1997 13:36:42 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, dg@root.com wrote: >>I'm using 3 EtherExpress cards: >> >>fxp0 rev 2 int a irq 10 on pci0:10 >>fxp0: Ethernet address 00:a0:c9:55:13:22 >>fxp1 rev 1 int a irq 9 on pci0:12 >>fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps >>fxp2 rev 1 int a irq 9 on pci0:14 >>fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps >> >>Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently >>freezes. >>When I `ifconfig down delete fxp0' and then ifconfig it up, the situation >>resolves. > > If this is true, then Intel has apparantly lied to me about fixing the >problem in the "next stepping" of the chip. The lock up should only occur >when garbage bits occur in the preamble of a packet. It's not supposed to >happen in 100Mbps mode (only 10Mbps), but since I've personnally been able >to get it to happen in 100Mbps, I don't believe it. I can reproduce the >problem only under special circumstance like power-cycling the hub. > You might try using the "link0 link1 -link2" flags on the 100Mbps link >to force it to stay in 100/half...this might prevent the lock up from >occuring (but I've not tested this myself). For what it's worth, we also saw problems with the Intel EtherExpress Pro 10/100B card (rev 2) under not so good network conditions. We're using 4 such cards on a router: fxp0 rev 2 int a irq 9 on pci0:9 fxp0: Ethernet address 00:a0:c9:5f:f8:f9 fxp1 rev 2 int a irq 12 on pci0:10 fxp1: Ethernet address 00:a0:c9:5f:f9:0a fxp2 rev 2 int a irq 10 on pci0:11 fxp2: Ethernet address 00:a0:c9:6c:78:6d fxp3 rev 2 int a irq 11 on pci0:12 fxp3: Ethernet address 00:a0:c9:6c:a6:e7 fxp3 (running in 10Mbps) was connected on the other end to a cheap hub in a room 11 floors below our machine. So, it's a long haul and the wiring at certain places may be a little sketchy. The connection would freeze-up at least every two days (sometimes more frequently) and we'd get messages like the following in /var/log/messages: Sep 8 11:41:04 core5 routed[83]: interface fxp3 to 206.253.23.1 bad: in=0 ierr=511 out=0 oerr=0 Sep 8 11:41:39 core5 routed[83]: interface fxp3 to 206.253.23.1 restored These seem to indicate garbage on the connection. We don't have control over the hub - so I guess it's possible that the hub was power-cycled around the times that the connection froze. We then added a 5th card to the machine (running the FreeBSD 2.2-970618 snapshot, by the way) - an SMC card (ed0 driver) - and switched over to using that card for the connection that was freezing up. We haven't had any problems since we switched to the SMC card. Best regards, Pius From owner-freebsd-hackers Fri Sep 26 13:40:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26650 for hackers-outgoing; Fri, 26 Sep 1997 13:40:34 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26643 for ; Fri, 26 Sep 1997 13:40:31 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id QAA05199; Fri, 26 Sep 1997 16:41:05 -0400 (EDT) Message-ID: <19970926164104.57516@vinyl.quickweb.com> Date: Fri, 26 Sep 1997 16:41:04 -0400 From: Mark Mayo To: hackers@freebsd.org Subject: Changes since Lite2 NFS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm curious about how much code had changed in the FreeBSD NFS implementation since Rick Maclems's 4.4BSD-Lite code. How would I go about using CVS or whatever to contruct a comparison? I'm imagining that there have been quite a few changes due to the NFS 3.0 additions - but Rick claims that 99% of the code in all the *BSD's is his :-) TIA, -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-hackers Fri Sep 26 14:08:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27846 for hackers-outgoing; Fri, 26 Sep 1997 14:08:37 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA27811; Fri, 26 Sep 1997 14:08:21 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA13493; Fri, 26 Sep 1997 14:07:32 -0700 (MST) From: Terry Lambert Message-Id: <199709262107.OAA13493@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: dg@root.com Date: Fri, 26 Sep 1997 21:07:31 +0000 (GMT) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709261431.HAA25105@implode.root.com> from "David Greenman" at Sep 26, 97 07:31:43 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >This is an interesting problem... I'm going to provide some possible > >hacks. Normally I don't hack drivers for cards that I don't have > > Wrong on all accounts. Let's not cloud the issue with irrelevant > information and wrong patches. It's difficult enough for me to provide > accurate information without having to battle misinformation. Thanks. This seemed like an issue that simply hadn't been addresssed, but which was well known, according to early postings. Subsequent traffic (which occurred *after* my posting makes it clear that up/downing the interface will fix it as well. Clearly, the very last suggestion, coupled with the suggested receive idle timer, will work, though it is not pretty. Playing with the control bits, as well, may very well "resolve" the deadlock. As far as mbuf denial, it's clearly not the problem, but it could be *a* problem. I should have suggested "vmstat -m | grep mbuf" first, though. 8-). I'm not sure why that status bit is not checked in all cases, though if ether_input() isn't puked, all it should do is result in bogus packets coming further up the stack than they should. 8-(. Anyway, it's still an interesting problem: how to deal with broken hardware. Sounds like a job for a high resoloution timer... ;-). 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-hackers Fri Sep 26 14:11:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27980 for hackers-outgoing; Fri, 26 Sep 1997 14:11:41 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA27972 for ; Fri, 26 Sep 1997 14:11:37 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA13659; Fri, 26 Sep 1997 14:11:14 -0700 (MST) From: Terry Lambert Message-Id: <199709262111.OAA13659@usr08.primenet.com> Subject: Re: Timeout for sh(1) 'read' ?? To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 21:11:13 +0000 (GMT) Cc: hamilton@pobox.com, tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199709261511.AAA01871@word.smith.net.au> from "Mike Smith" at Sep 27, 97 00:41:56 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > You can do this kind of thing with background processes and trap, but > > it's not what you'd call pretty, and even that isn't as straightforward > > as it might sound. > > In other words, it would be a good thing for read to have a timeout > option : correct? Any objections? How about: timeout 30 -inactivity `tty` read x instead? Then it could be used on any command. 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-hackers Fri Sep 26 14:21:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA28600 for hackers-outgoing; Fri, 26 Sep 1997 14:21:11 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA28591 for ; Fri, 26 Sep 1997 14:21:04 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id VAA07379; Fri, 26 Sep 1997 21:18:17 GMT Date: Fri, 26 Sep 1997 14:18:16 -0700 (PDT) From: Dan Busarow To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: More ATAPI Zip news (will he ever shut up?) In-Reply-To: <199709261822.DAA04965@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Mike Smith wrote: > Just keeping people informed; the latest Award BIOS *does* appear to be > able to boot from the ATAPI Zip. Curiouser and curiouser. That's a bit of good news. I've based a new system on booting off of these puppies and the one I used for testing, picked up two weeks ago, works fine. I'm not looking forward to coming up with an alternative. The iomega web site is still refering to them as IDE Zip drives, has the packaging, part number or anything else changed? Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Fri Sep 26 14:34:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29390 for hackers-outgoing; Fri, 26 Sep 1997 14:34:59 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29370; Fri, 26 Sep 1997 14:34:51 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA14622; Fri, 26 Sep 1997 14:34:01 -0700 (MST) From: Terry Lambert Message-Id: <199709262134.OAA14622@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: dg@root.com Date: Fri, 26 Sep 1997 21:34:01 +0000 (GMT) Cc: mike@smith.net.au, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709261426.HAA25055@implode.root.com> from "David Greenman" at Sep 26, 97 07:26:27 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > One of these days I'll conjure up some sort of hack to fix the problem. > Intel recommends reprogramming the multicast filter (!) if no packets are > received for some number of seconds. This is difficult to implement in the > current design of the driver. Plus it leaves your butt hanging in the wind for several seconds on a *supposedly* 100Mbit card. Pretty frigging ugly. I guess the errata don't say what causes the bug (like a collision? That would explain the 100Mbit being more robust...), like the macrocell for the chip is actually mask programmed and the unused bit sets aren't specifically disallowed, or a header collision can't be dealt with because the header accumulation buffer isn't cleared, or something dumb like that? Do we know that the "cron ping soloution" actually works? If it does, can we set up a bogus gateway route to avoid getting a packet back for one sent to see if it's the packet out or the packet back that does it? I'm betting out at this point... If this works, then a timer set to bogusly send a packet to ourselves would not bother anyone else on the network who wasn't in promiscuous mode and running a network monitor, and it would be filterable there. 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-hackers Fri Sep 26 14:36:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29585 for hackers-outgoing; Fri, 26 Sep 1997 14:36:58 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29562 for ; Fri, 26 Sep 1997 14:36:55 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id OAA06018; Fri, 26 Sep 1997 14:38:00 -0700 (PDT) Date: Fri, 26 Sep 1997 14:38:00 -0700 (PDT) From: Jim Shankland Message-Id: <199709262138.OAA06018@biggusdiskus.flyingfox.com> To: chuckr@glue.umd.edu, mike@smith.net.au Subject: Re: thickwisre<->thinwire Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > I went thru several vendors looking for the converter. I guess I'll > try a local hamfest. DataComm Warehouse has these for $19.95. http://www.warehouse.com, (800) 328-2261, item number DET1094. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Fri Sep 26 14:39:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29737 for hackers-outgoing; Fri, 26 Sep 1997 14:39:12 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29713 for ; Fri, 26 Sep 1997 14:39:08 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA14801; Fri, 26 Sep 1997 14:39:01 -0700 (MST) From: Terry Lambert Message-Id: <199709262139.OAA14801@usr08.primenet.com> Subject: Re: thickwisre<->thinwire To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 26 Sep 1997 21:39:00 +0000 (GMT) Cc: FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Sep 26, 97 12:39:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > I find I have to connect another computer to my existing home ethernet. > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > connecting it to my two existing FreeBSD boxes. > > Does anyone know where I could go to get a thickwire to thinwire > converter? I've not had any luck searching it out yet. A couple of card vendors have them on their WWW sales pages for ~$15; you can get them for cheaper, but the best bet is there. If you go through PC Mall (or wherever), you will end up paying $50+. The place I've seen them for cheaper is on auction at www.onsale.com. 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-hackers Fri Sep 26 14:43:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA00222 for hackers-outgoing; Fri, 26 Sep 1997 14:43:32 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA00209 for ; Fri, 26 Sep 1997 14:43:27 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA15153; Fri, 26 Sep 1997 14:43:00 -0700 (MST) From: Terry Lambert Message-Id: <199709262143.OAA15153@usr08.primenet.com> Subject: Re: thickwisre<->thinwire To: sos@sos.freebsd.dk (Søren Schmidt) Date: Fri, 26 Sep 1997 21:43:00 +0000 (GMT) Cc: chuckr@glue.umd.edu, FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: <199709261737.TAA04140@sos.freebsd.dk> from "Søren Schmidt" at Sep 26, 97 07:37:50 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Does anyone know where I could go to get a thickwire to thinwire > > converter? I've not had any luck searching it out yet. > > Does the DECStation connect via an AUI cable ?? > Then you just need one of those little gizmos that plug in to the > AUI connector and has a BNC connector in the other end.... Note that much DEC equipment is such that you will either have to remove posts and the locking slide if you directly connect the little box, or you will need a 6-8 inch pig-tail cable to go between them (I have a couple of these as well, since HP equipment is pretty much in the same boat). > Or you could get nasty and get a connector that fits on the end of > the think cable and a converter from that to BNC, both cables are > 50 Ohms, so it works, just is a bit unusual :) Heh. 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-hackers Fri Sep 26 16:20:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06108 for hackers-outgoing; Fri, 26 Sep 1997 16:20:54 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA06101 for ; Fri, 26 Sep 1997 16:20:44 -0700 (PDT) Received: from sonata (sonata.hh.kew.com [192.195.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with ESMTP id TAA05679; Fri, 26 Sep 1997 19:18:44 -0400 (EDT) Message-ID: <342C42DD.7CAB7A7@kew.com> Date: Fri, 26 Sep 1997 19:18:53 -0400 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks X-Mailer: Mozilla 4.01 [en]C-MOENE (WinNT; U) MIME-Version: 1.0 To: Terry Lambert CC: hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath X-Priority: 3 (Normal) References: <199709260412.VAA00754@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > As I said in my other message, it's probably intentional to keep down > support calls, since MS OS's (other than DOS) can't safely run binaries > or swap from removable media. VM/370 could. :-) (Showing my age today ...) -- Internet: ahd@kew.com Voice: 781-279-9812 "There is much Obi-Wan did not tell you." From owner-freebsd-hackers Fri Sep 26 18:09:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA11908 for hackers-outgoing; Fri, 26 Sep 1997 18:09:10 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA11886; Fri, 26 Sep 1997 18:09:03 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA01062; Fri, 26 Sep 1997 18:10:48 -0700 (PDT) Message-Id: <199709270110.SAA01062@implode.root.com> To: Terry Lambert cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 21:34:01 -0000." <199709262134.OAA14622@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 18:10:48 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> One of these days I'll conjure up some sort of hack to fix the problem. >> Intel recommends reprogramming the multicast filter (!) if no packets are >> received for some number of seconds. This is difficult to implement in the >> current design of the driver. > >Plus it leaves your butt hanging in the wind for several seconds on >a *supposedly* 100Mbit card. Pretty frigging ugly. Uh, well, as far as I can tell, for 100Mbps, the problem only occurs when the link transitions to 10Mbps first and then sees garbage. Since the link speed is autodetected, it's easy to see how this might happen when someone power cycles a hub or something. It's less clear how it could occur in normal use at 10Mbps. Perhaps the problem doesn't occur with some hubs due to the hub/switch regeneration of the synch bits (which many hubs apparantly will do). >I guess the errata don't say what causes the bug (like a collision? >That would explain the 100Mbit being more robust...), It has something to do with the synchronization bits that preceed the packet data, but I can't find the errata right now (I recall that is was quite vague in any case). >Do we know that the "cron ping soloution" actually works? If it >does, can we set up a bogus gateway route to avoid getting a packet >back for one sent to see if it's the packet out or the packet back >that does it? I'm betting out at this point... The problem is that the receiver circuitry in the chip locks up, so you stop getting the echo response; the card continues to transmit, however. For whatever reason, reprogramming the multicast filter or resetting the entire chip corrects the condition. (The multicast filter is part of the receiver circuit, and it is apparantly selectively reset when the multicast filter is reprogrammed). >If this works, then a timer set to bogusly send a packet to ourselves >would not bother anyone else on the network who wasn't in promiscuous >mode and running a network monitor, and it would be filterable there. You can't send a packet to yourself under normal circumstances (ethernet is a simplex device). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Sep 26 19:53:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA18589 for hackers-outgoing; Fri, 26 Sep 1997 19:53:39 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18567; Fri, 26 Sep 1997 19:53:31 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA02076; Fri, 26 Sep 1997 19:53:12 -0700 (MST) From: Terry Lambert Message-Id: <199709270253.TAA02076@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: dg@root.com Date: Sat, 27 Sep 1997 02:53:12 +0000 (GMT) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709270110.SAA01062@implode.root.com> from "David Greenman" at Sep 26, 97 06:10:48 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >If this works, then a timer set to bogusly send a packet to ourselves > >would not bother anyone else on the network who wasn't in promiscuous > >mode and running a network monitor, and it would be filterable there. > > You can't send a packet to yourself under normal circumstances (ethernet > is a simplex device). I meant "send it addressed to my own address"... from what you say, though, the "ping soloutoin" probably is just a conicidence, so it's a non-starter. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Sep 26 22:23:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA27182 for hackers-outgoing; Fri, 26 Sep 1997 22:23:46 -0700 (PDT) Received: from singapore.eecs.umich.edu (singapore.eecs.umich.edu [141.213.8.39]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA27174 for ; Fri, 26 Sep 1997 22:23:41 -0700 (PDT) Received: (from weeteck@localhost) by singapore.eecs.umich.edu (8.8.7/8.8.7) id BAA07578; Sat, 27 Sep 1997 01:23:44 -0400 (EDT) From: Wee Teck Ng Message-Id: <199709270523.BAA07578@singapore.eecs.umich.edu> Subject: using vm_map_protect on Pentium PC To: freebsd-hackers@freebsd.org Date: Sat, 27 Sep 1997 01:23:44 -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-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi all, we are heavily utilising VM protection (vm_map_prot) on 2.2-stable, and found that it doesn't work well on Pentium processor. specifically, when using vm_map_prot to change a page's protection from VM_PROT_READ to VM_PROT_ALL, only the vm map is updated. pmap_protect does not reset the pte to writeable (i.e. PG_RW). this will not work on pentium processor, since page level protection is enforced by the processor (against kernel access) when WP flag of CR0 is set. i've noticed that FreeBSD-current has fixed this problem. my questions are: 1) is there a 2.x release with a Pentium-compatible VM system? 2) how stable is 3.0 is for non SMP machines? thanks! wee teck From owner-freebsd-hackers Fri Sep 26 22:52:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA29569 for hackers-outgoing; Fri, 26 Sep 1997 22:52:57 -0700 (PDT) Received: from pili.adn.edu.ph (pili.adn.edu.ph [165.220.57.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA29563 for ; Fri, 26 Sep 1997 22:52:51 -0700 (PDT) Received: from localhost (art@localhost) by pili.adn.edu.ph (8.8.5/8.8.5) with SMTP id OAA26973 for ; Sat, 27 Sep 1997 14:04:37 +0800 (PHT) Date: Sat, 27 Sep 1997 14:04:37 +0800 (PHT) From: Arthur Alacar cc: hackers@FreeBSD.ORG Subject: dosemu In-Reply-To: <199709270253.TAA02076@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk any dosemu for freebsd? wanna know where.... |art| From owner-freebsd-hackers Fri Sep 26 22:59:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA29901 for hackers-outgoing; Fri, 26 Sep 1997 22:59:43 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA29895 for ; Fri, 26 Sep 1997 22:59:38 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id PAA00415; Sat, 27 Sep 1997 15:27:05 +0930 (CST) Message-Id: <199709270557.PAA00415@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dan Busarow cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: More ATAPI Zip news (will he ever shut up?) In-reply-to: Your message of "Fri, 26 Sep 1997 14:18:16 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Sep 1997 15:27:03 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sat, 27 Sep 1997, Mike Smith wrote: > > Just keeping people informed; the latest Award BIOS *does* appear to be > > able to boot from the ATAPI Zip. Curiouser and curiouser. > > That's a bit of good news. > > I've based a new system on booting off of these puppies and the > one I used for testing, picked up two weeks ago, works fine. > I'm not looking forward to coming up with an alternative. It's not *too* good in that FreeBSD still can't use it as a drive; it comes up as a direct-access ATAPI disk but doesn't respond as a CDROM so it's ignored. > The iomega web site is still refering to them as IDE Zip drives, > has the packaging, part number or anything else changed? I believe so; I don't have access to any of the older IDE units at the moment, but if you have a part number on the IDE version I can compare it with that on the ATAPI-only one later today. mike From owner-freebsd-hackers Fri Sep 26 23:12:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00848 for hackers-outgoing; Fri, 26 Sep 1997 23:12:23 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA00826; Fri, 26 Sep 1997 23:12:17 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id XAA19592; Fri, 26 Sep 1997 23:10:25 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709270610.XAA19592@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709270110.SAA01062@implode.root.com> from David Greenman at "Sep 26, 97 06:10:48 pm" To: dg@root.com Date: Fri, 26 Sep 1997 23:10:25 -0700 (PDT) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You can't send a packet to yourself under normal circumstances (ethernet > is a simplex device). Only broken NIC chips are simplex, even the 82586 is actually capable of hering itself talk on the wire, though most drives do not set the chip into this mode. Either way ``ethernet is _not_ a simplex device''. Infact the 82586 has the ability to due cource grain TDR (Time Domain Reflectonmetry) for finding bad coax (thick or thin). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hackers Fri Sep 26 23:46:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA03121 for hackers-outgoing; Fri, 26 Sep 1997 23:46:03 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA03106 for ; Fri, 26 Sep 1997 23:45:56 -0700 (PDT) Received: from default (user26.kincyb.com [206.17.159.26]) by netroplex.com (8.8.5/8.8.2) with ESMTP id XAA17798 for ; Fri, 26 Sep 1997 23:47:06 -0700 (PDT) Message-ID: <342CAAAF.4F93CB47@pagecreators.com> Date: Fri, 26 Sep 1997 23:41:51 -0700 From: Rod Ebrahimi X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: PPro VS PII X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone provide me with more information about the Pentium II (233) vs Pentium Pro 200... is there an obvious performance difference when running FreeBSD for servers? Thank you, Rod From owner-freebsd-hackers Sat Sep 27 00:14:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA05437 for hackers-outgoing; Sat, 27 Sep 1997 00:14:33 -0700 (PDT) Received: from ingenieria ([168.176.15.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA05429 for ; Sat, 27 Sep 1997 00:14:30 -0700 (PDT) Received: from unalmodem.usc.unal.edu.co by ingenieria (SMI-8.6/SMI-SVR4) id DAA06311; Sat, 27 Sep 1997 03:00:35 -0400 Message-ID: <342CCD58.7842@asme.org> Date: Sat, 27 Sep 1997 02:09:44 -0700 From: "Pedro Giffuni S," Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.01Gold [it] (Win16; I) MIME-Version: 1.0 To: Arthur Alacar CC: hackers@freebsd.org Subject: Re: dosemu References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For upteenth time...DOSCMD :^)... You'll find it in: 1) The 2.2.x CDROMs under experimental 2) current (much better) Also a good idea to join the emulation list ! cheers, Pedro. Arthur Alacar wrote: > > any dosemu for freebsd? > > wanna know where.... > > |art| From owner-freebsd-hackers Sat Sep 27 00:23:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA06289 for hackers-outgoing; Sat, 27 Sep 1997 00:23:41 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA06272 for ; Sat, 27 Sep 1997 00:23:35 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id AAA16100; Sat, 27 Sep 1997 00:23:26 -0700 (PDT) Date: Sat, 27 Sep 1997 00:23:26 -0700 (PDT) From: Doug White Reply-To: Doug White To: Coi Giovanni cc: freebsd-hackers@freebsd.org Subject: Re: wd1: invalid primary partition table: no magic In-Reply-To: <199709241932.VAA24695@prometeo.prometeo.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if I was going to end up with this. It is my document after all :-) > I have a strange (for me) message when I execute > some command like disklabel (or fsck) > it display on console > > wd1: invalid primary partition table: no magic > > for example: > > dd if=/dev/zero of=/dev/rwd1 count=2 > (this is ok) > > disklabel -e -r /dev/rwd1 > (this rise the error/warning messages, then I edit the > partition table and...) The message is totally normal if it appears after running the above command. > What does it means? It means that the partition table doesn't contain the necessary identifying bits for the PC partition table. Which is true. By running the dd if=/dev/zero... command you effectively destroyed anything that may have been present. But it doesn't mean anything is wrong, it's for your information only. It's bad if your primary boot disk spits this out ;-) > Any suggestions? Enjoy your new 2GB filesystem. :-) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-hackers Sat Sep 27 00:51:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA07911 for hackers-outgoing; Sat, 27 Sep 1997 00:51:19 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA07905 for ; Sat, 27 Sep 1997 00:51:14 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id DAA28443; Sat, 27 Sep 1997 03:50:27 -0400 (EDT) Date: Sat, 27 Sep 1997 03:50:27 -0400 (EDT) From: Snob Art Genre To: Mike Smith cc: Terry Lambert , bartol@salk.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: problem compiling for linux under compat_linux In-Reply-To: <199709260818.RAA00553@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Mike Smith wrote: > > Editorial on cache thrashing by mmap() in ld: > > Elide! Elide! I found it interesting, and he did warn us first. > > mike > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Sat Sep 27 01:01:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA08337 for hackers-outgoing; Sat, 27 Sep 1997 01:01:58 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA08332 for ; Sat, 27 Sep 1997 01:01:52 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id BAA23823 for ; Sat, 27 Sep 1997 01:01:50 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA10710 for ; Sat, 27 Sep 1997 01:01:49 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA00388 for freebsd-hackers@freebsd.org; Sat, 27 Sep 1997 01:01:48 -0700 (PDT) Date: Sat, 27 Sep 1997 01:01:48 -0700 (PDT) From: Don Lewis Message-Id: <199709270801.BAA00388@salsa.gv.tsc.tdk.com> To: freebsd-hackers@freebsd.org Subject: F_SETOWN implementation redesign Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After hearing about the OpenBSD security fix for F_SETOWN, I went digging through the FreeBSD mail list archives and stumbled across a lot of complaints about the current F_SETOWN implementation dating back to the early part of 1996 (as well as mention of the security flaw). This inspired me to revamp the F_SETOWN implementation to address some of these issues. Security: I added credential checking which should work in a similar manner as the OpenBSD change. I added a restriction that only allows F_SETOWN to specify a process or process group in the same session as the caller. This change is somewhat debatable, but I can't think of a good use for allowing a process in another session to be specified and there is some potential for misuse as well as traps for the careless. When a process exits or a process group loses all it's members, any references to it specified by F_SETOWN are revoked even though the device or socket has not been closed (it may be held open by another process). The old implementation would start sending signals to a new process once the process IDs wrapped around. Funtionality: The old implementation used TIOCSPGRP when used on a tty device. This meant that you could only do async I/O on your controlling tty, which meant that you were limited to doing async I/O on at most one tty device. My new implementation separates the F_SETOWN functionality from TIOCSPGRP on tty devices, so you can do async I/O on multiple devices and still have a separate control tty. The only restriction is that these tty devices can't be the control ttys for another session. The new implementation always returns an error if you specify a non-existent process or process group. Performance: The old implemenation needed to search for the process group or process whenever it wanted to deliver a signal. The new implementation keeps a pointer, which should reduce the overhead for heavy users of async I/O. The attached patch is relative to my somewhat hacked copy of 2.1-stable, so it might not apply quite cleanly to a fresh copy. It'll require even more changes to make it work with 2.2 or later (for instance the appropriate changes will need to be made to kern_pipe.c). I've only done limited testing so far, but I thought this would be an appropriate time to share my work. One thing to consider is whether it is appropriate to remove the TIOCSPGRP/TIOCGPGRP code from the non-tty drivers. I left it in in case anyone is using these ioctl commands instead of F_SETOWN or F_GETOWN on non-ttys. Removing this code would reduce the bloat somewhat. --- Truck Index: lib/libc/sys/fcntl.2 =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/lib/libc/sys/fcntl.2,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 fcntl.2 --- fcntl.2 1997/05/09 09:31:04 1.1.1.1 +++ fcntl.2 1997/09/27 01:35:13 @@ -477,29 +477,23 @@ .Dv F_SETLKW , and satisfying the lock or unlock request would result in the number of locked regions in the system exceeding a system-imposed limit. +.It Bq Er ENOTTY +.Fa Cmd +is +.Dv F_GETOWN +or +.Dv F_SETOWN , +.Fa fd +refers to a descriptor open on a terminal device (as opposed to a +descriptor open on a socket), and the device is the controlling +terminal for a session other than the session of the calling process. .It Bq Er ESRCH .Fa Cmd is .Dv F_SETOWN and -the process ID given as argument is not in use. +the process ID or process group ID given as argument is not in use. .El -.Pp -In addition, if -.Fa fd -refers to a descriptor open on a terminal device (as opposed to a -descriptor open on a socket), a -.Fa cmd -of -.Dv F_SETOWN -can fail for the same reasons as in -.Xr tcsetpgrp 3 , -and a -.Fa cmd -of -.Dv F_GETOWN -for the reasons as stated in -.Xr tcgetpgrp 3 . .Sh SEE ALSO .Xr close 2 , .Xr execve 2 , @@ -507,8 +501,6 @@ .Xr getdtablesize 2 , .Xr open 2 , .Xr sigvec 2 , -.Xr tcgetpgrp 3 , -.Xr tcsetpgrp 3 .Sh HISTORY The .Nm Index: sys/kern/kern_descrip.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/kern_descrip.c,v retrieving revision 1.2 diff -u -r1.2 kern_descrip.c --- kern_descrip.c 1997/05/13 11:55:43 1.2 +++ kern_descrip.c 1997/09/26 23:24:36 @@ -226,30 +226,13 @@ return (error); case F_GETOWN: - if (fp->f_type == DTYPE_SOCKET) { - *retval = ((struct socket *)fp->f_data)->so_pgid; - return (0); - } error = (*fp->f_ops->fo_ioctl) - (fp, (int)TIOCGPGRP, (caddr_t)retval, p); - *retval = -*retval; + (fp, (int)FIOGETOWN, (caddr_t)retval, p); return (error); case F_SETOWN: - if (fp->f_type == DTYPE_SOCKET) { - ((struct socket *)fp->f_data)->so_pgid = uap->arg; - return (0); - } - if (uap->arg <= 0) { - uap->arg = -uap->arg; - } else { - struct proc *p1 = pfind(uap->arg); - if (p1 == 0) - return (ESRCH); - uap->arg = p1->p_pgrp->pg_id; - } return ((*fp->f_ops->fo_ioctl) - (fp, (int)TIOCSPGRP, (caddr_t)&uap->arg, p)); + (fp, (int)FIOSETOWN, (caddr_t)&uap->arg, p)); case F_SETLKW: flg |= F_WAIT; @@ -325,6 +308,94 @@ fdp->fd_lastfile = new; *retval = new; return (0); +} + +/* + * If sigio is on the list associated with a process or process group, + * remove it. + */ +void +funsetown(sigio) + register struct sigio *sigio; +{ + if (sigio->sio_pgid == 0) + return; + + if (sigio->sio_pgid < 0) { + SLIST_REMOVE(&(sigio->sio_pgrp->pg_sigiolst), sigio, sigio, + sio_pgsigio); + sigio->sio_pgrp = NULL; + } else if (sigio->sio_pgid > 0) { + SLIST_REMOVE(&(sigio->sio_proc->p_sigiolst), sigio, sigio, + sio_pgsigio); + sigio->sio_proc = NULL; + } + sigio->sio_pgid = 0; + crfree(sigio->sio_ucred); + sigio->sio_ucred = NULL; +} + +/* + * Common code for FIOSETOWN ioctl called by F_SETOWN + * + * After permission checking, add sigio structure to the sigio list for + * the process or process group. + */ +int +fsetown(pgid, sigio, funset) + register pid_t pgid; + register struct sigio *sigio; + void (*funset) __P((struct sigio *)); +{ + if (pgid == 0) { + funsetown(sigio); + return (0); + } else if (pgid > 0) { + register struct proc *proc = pfind(pgid); + + if (proc == NULL) + return (ESRCH); + else if (proc->p_session != curproc->p_session) + return (EPERM); + + funsetown(sigio); + + SLIST_INSERT_HEAD(&(proc->p_sigiolst), sigio, sio_pgsigio); + sigio->sio_proc = proc; + } else /* if (pgid < 0) */ { + register struct pgrp *pgrp = pgfind(-pgid); + + if (pgrp == NULL) + return (ESRCH); + else if (pgrp->pg_session != curproc->p_session) + return (EPERM); + + funsetown(sigio); + + SLIST_INSERT_HEAD(&(pgrp->pg_sigiolst), sigio, sio_pgsigio); + sigio->sio_pgrp = pgrp; + } + + sigio->sio_pgid = pgid; + + crhold(curproc->p_ucred); + sigio->sio_ucred = curproc->p_ucred; + sigio->sio_ruid = curproc->p_cred->p_ruid; /* wish this was in ucred */ + + sigio->sio_unsetown = funset; + + return (0); +} + +/* + * Common code for FIOGETOWN ioctl called by F_GETOWN + */ +pid_t +fgetown(sigio) + register struct sigio *sigio; +{ + /* we could also return sigio->sio_{proc->p_pid,pgrp->pg_id} */ + return (sigio->sio_pgid); } /* Index: sys/kern/kern_exit.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/kern_exit.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 kern_exit.c --- kern_exit.c 1997/05/09 09:34:33 1.1.1.1 +++ kern_exit.c 1997/09/26 23:25:32 @@ -131,6 +131,14 @@ untimeout(realitexpire, (caddr_t)p); /* + * Reset any sigio structures pointing to us as a result of + * F_SETOWN with our pid + */ + while (p->p_sigiolst.slh_first != NULL) + (*p->p_sigiolst.slh_first->sio_unsetown) + (p->p_sigiolst.slh_first); + + /* * Close open files and release open-file table. * This may block! */ Index: sys/kern/kern_proc.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/kern_proc.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 kern_proc.c --- kern_proc.c 1997/05/09 09:34:34 1.1.1.1 +++ kern_proc.c 1997/09/27 06:31:39 @@ -49,6 +49,7 @@ #include #include #include +#include struct prochd qs[NQS]; /* as good a place as any... */ struct prochd rtqs[NQS]; /* Space for REALTIME queues too */ @@ -246,6 +247,7 @@ pgrphash[n] = pgrp; pgrp->pg_jobc = 0; pgrp->pg_mem = NULL; + SLIST_INIT(&(pgrp->pg_sigiolst)); } else if (pgrp == p->p_pgrp) return (0); @@ -317,6 +319,14 @@ register struct pgrp *pgrp; { register struct pgrp **pgp = &pgrphash[PIDHASH(pgrp->pg_id)]; + + /* + * Reset any sigio structures pointing to us as a result of + * F_SETOWN with our pgid + */ + while (pgrp->pg_sigiolst.slh_first != NULL) + (*pgrp->pg_sigiolst.slh_first->sio_unsetown) + (pgrp->pg_sigiolst.slh_first); if (pgrp->pg_session->s_ttyp != NULL && pgrp->pg_session->s_ttyp->t_pgrp == pgrp) Index: sys/kern/kern_sig.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/kern_sig.c,v retrieving revision 1.2 diff -u -r1.2 kern_sig.c --- kern_sig.c 1997/05/13 11:58:02 1.2 +++ kern_sig.c 1997/09/26 13:02:08 @@ -93,6 +93,16 @@ ((signum) == SIGCONT && (q)->p_session == (p)->p_session)) #endif +/* + * Can real uid ruid with ucred uc send a signal to process q? + */ +#define CANSIGIO(ruid, uc, q) \ + ((uc)->cr_uid == 0 || \ + ruid == (q)->p_cred->p_ruid || \ + (uc)->cr_uid == (q)->p_cred->p_ruid || \ + ruid == (q)->p_ucred->cr_uid || \ + (uc)->cr_uid == (q)->p_ucred->cr_uid) + struct sigaction_args { int signum; struct sigaction *nsa; @@ -1241,4 +1251,27 @@ psignal(p, SIGSYS); return (EINVAL); +} + +/* + * Send a signal to a SIGIO or SIGURG to a process or process group using + * stored credentials rather than those of the current process + */ +void +sigio_p_or_pg(sigio, signum, checkctty) + register struct sigio *sigio; + int signum, checkctty; +{ + if (sigio->sio_pgid > 0) { + if (CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, + sigio->sio_proc)) + psignal(sigio->sio_proc, signum); + } else if (sigio->sio_pgid < 0) { + register struct proc *p; + + for (p = sigio->sio_pgrp->pg_mem; p != NULL; p = p->p_pgrpnxt) + if (CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, p) && + (checkctty == 0 || (p->p_flag & P_CONTROLT))) + psignal(p, signum); + } } Index: sys/kern/subr_log.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/subr_log.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 subr_log.c --- subr_log.c 1997/05/09 09:34:34 1.1.1.1 +++ subr_log.c 1997/09/26 22:45:58 @@ -46,6 +46,7 @@ #include #include #include +#include /* get fsetown, funsetown, fgetown */ #define LOG_RDPRI (PZERO + 1) @@ -55,7 +56,8 @@ struct logsoftc { int sc_state; /* see above for possibilities */ struct selinfo sc_selp; /* process waiting on select call */ - int sc_pgid; /* process/group for async I/O */ + struct sigio sc_sigio; /* credentials and pointer to proc + * or group for SIGIO */ } logsoftc; int log_open; /* also used in log() */ @@ -72,7 +74,8 @@ if (log_open) return (EBUSY); log_open = 1; - logsoftc.sc_pgid = p->p_pid; /* signal process only */ + /* signal process only */ + fsetown(p->p_pid, &logsoftc.sc_sigio, funsetown); return (0); } @@ -86,6 +89,7 @@ log_open = 0; logsoftc.sc_state = 0; + funsetown(&logsoftc.sc_sigio); return (0); } @@ -166,12 +170,8 @@ if (!log_open) return; selwakeup(&logsoftc.sc_selp); - if (logsoftc.sc_state & LOG_ASYNC) { - if (logsoftc.sc_pgid < 0) - gsignal(-logsoftc.sc_pgid, SIGIO); - else if ((p = pfind(logsoftc.sc_pgid))) - psignal(p, SIGIO); - } + if (logsoftc.sc_state & LOG_ASYNC) + sigio_p_or_pg(&(logsoftc.sc_sigio), SIGIO, 0); if (logsoftc.sc_state & LOG_RDWAIT) { wakeup((caddr_t)msgbufp); logsoftc.sc_state &= ~LOG_RDWAIT; @@ -188,7 +188,7 @@ struct proc *p; { long l; - int s; + int s, error; switch (com) { @@ -212,12 +212,25 @@ logsoftc.sc_state &= ~LOG_ASYNC; break; + case FIOSETOWN: + error = fsetown(*(int *)data, &(logsoftc.sc_sigio), funsetown); + if (error) + return (error); + break; + + case FIOGETOWN: + *(int *)data = fgetown(&(logsoftc.sc_sigio)); + break; + case TIOCSPGRP: - logsoftc.sc_pgid = *(int *)data; + error = fsetown(-(*(int *)data), &(logsoftc.sc_sigio), + funsetown); + if (error) + return (error); break; case TIOCGPGRP: - *(int *)data = logsoftc.sc_pgid; + *(int *)data = -fgetown(&(logsoftc.sc_sigio)); break; default: Index: sys/kern/sys_generic.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/sys_generic.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 sys_generic.c --- sys_generic.c 1997/05/09 09:34:34 1.1.1.1 +++ sys_generic.c 1997/09/26 10:54:41 @@ -472,36 +472,8 @@ break; case FIOSETOWN: - tmp = *(int *)data; - if (fp->f_type == DTYPE_SOCKET) { - ((struct socket *)fp->f_data)->so_pgid = tmp; - error = 0; - break; - } - if (tmp <= 0) { - tmp = -tmp; - } else { - struct proc *p1 = pfind(tmp); - if (p1 == 0) { - error = ESRCH; - break; - } - tmp = p1->p_pgrp->pg_id; - } - error = (*fp->f_ops->fo_ioctl) - (fp, (int)TIOCSPGRP, (caddr_t)&tmp, p); - break; - case FIOGETOWN: - if (fp->f_type == DTYPE_SOCKET) { - error = 0; - *(int *)data = ((struct socket *)fp->f_data)->so_pgid; - break; - } - error = (*fp->f_ops->fo_ioctl)(fp, (int)TIOCGPGRP, data, p); - *(int *)data = -*(int *)data; - break; - + /* fall through */ default: error = (*fp->f_ops->fo_ioctl)(fp, com, data, p); /* Index: sys/kern/sys_socket.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/sys_socket.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 sys_socket.c --- sys_socket.c 1997/05/09 09:34:35 1.1.1.1 +++ sys_socket.c 1997/09/26 23:14:42 @@ -76,6 +76,19 @@ uio, (struct mbuf *)0, (struct mbuf *)0, 0)); } +/* + * Callback to undo FIOSETOWN on process or process group death + */ +void +soo_unsetown(sigio) + struct sigio *sigio; +{ + register int s = splnet(); + + funsetown(sigio); + splx(s); +} + int soo_ioctl(fp, cmd, data, p) struct file *fp; @@ -84,6 +97,7 @@ struct proc *p; { register struct socket *so = (struct socket *)fp->f_data; + register int s, error; switch (cmd) { @@ -110,12 +124,28 @@ *(int *)data = so->so_rcv.sb_cc; return (0); - case SIOCSPGRP: - so->so_pgid = *(int *)data; + case FIOSETOWN: + s = splnet(); + error = fsetown(*(int *)data, &(so->so_sigio), soo_unsetown); + splx(s); + return(error); + + case FIOGETOWN: + s = splnet(); + *(int *)data = fgetown(&(so->so_sigio)); + splx(s); return (0); + case SIOCSPGRP: + s = splnet(); + error = fsetown(-(*(int *)data), &(so->so_sigio), soo_unsetown); + splx(s); + return(error); + case SIOCGPGRP: - *(int *)data = so->so_pgid; + s = splnet(); + *(int *)data = -fgetown(&(so->so_sigio)); + splx(s); return (0); case SIOCATMARK: Index: sys/kern/tty.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/tty.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 tty.c --- tty.c 1997/05/09 09:34:33 1.1.1.1 +++ tty.c 1997/09/26 23:28:11 @@ -86,6 +86,7 @@ #include #include #include +#include /* get fsetown, funsetown, fgetown */ #if NSNP > 0 #include #endif @@ -237,10 +238,13 @@ { int s; + s = spltty(); if (constty == tp) constty = NULL; + funsetown(&tp->t_sigio); + ttyflush(tp, FREAD | FWRITE); clist_free_cblocks(&tp->t_canq); clist_free_cblocks(&tp->t_outq); @@ -690,6 +694,19 @@ } /* + * Callback to undo FIOSETOWN on process or process group death + */ +void +tty_unsetown(sigio) + struct sigio *sigio; +{ + register int s = spltty(); + + funsetown(sigio); + splx(s); +} + +/* * Ioctls for all tty devices. Called after line-discipline specific ioctl * has been called to do discipline-specific functions and/or reject any * of these ioctl commands. @@ -758,6 +775,21 @@ *(int *)data = ttnread(tp); splx(s); break; + case FIOSETOWN: + if (tp->t_session != NULL && !isctty(p, tp)) + return (ENOTTY); + s = spltty(); + error = fsetown(*(int *)data, &(tp->t_sigio), tty_unsetown); + splx(s); + if (error) + return (error); + break; + case FIOGETOWN: + if (tp->t_session != NULL && !isctty(p, tp)) + return (ENOTTY); + *(int *)data = fgetown(&(tp->t_sigio)); + break; + case TIOCEXCL: /* set exclusive use of tty */ s = spltty(); SET(tp->t_state, TS_XCLUDE); @@ -2077,7 +2109,7 @@ if (tp->t_rsel.si_pid != 0) selwakeup(&tp->t_rsel); if (ISSET(tp->t_state, TS_ASYNC)) - pgsignal(tp->t_pgrp, SIGIO, 1); + sigio_p_or_pg(&(tp->t_sigio), SIGIO, (tp->t_session != NULL)); wakeup(TSA_HUP_OR_INPUT(tp)); } Index: sys/kern/uipc_socket.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/uipc_socket.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 uipc_socket.c --- uipc_socket.c 1997/05/09 09:34:35 1.1.1.1 +++ uipc_socket.c 1997/09/26 11:43:25 @@ -166,6 +166,8 @@ int s = splnet(); /* conservative */ int error = 0; + funsetown(&(so->so_sigio)); + if (so->so_options & SO_ACCEPTCONN) { while (so->so_q0) (void) soabort(so->so_q0); @@ -1052,9 +1054,6 @@ { struct proc *p; - if (so->so_pgid < 0) - gsignal(-so->so_pgid, SIGURG); - else if (so->so_pgid > 0 && (p = pfind(so->so_pgid)) != 0) - psignal(p, SIGURG); + sigio_p_or_pg(&(so->so_sigio), SIGURG, 0); selwakeup(&so->so_rcv.sb_sel); } Index: sys/kern/uipc_socket2.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/kern/uipc_socket2.c,v retrieving revision 1.1.1.2 diff -u -r1.1.1.2 uipc_socket2.c --- uipc_socket2.c 1997/05/10 08:30:30 1.1.1.2 +++ uipc_socket2.c 1997/09/26 22:50:38 @@ -177,7 +177,7 @@ so->so_state = head->so_state | SS_NOFDREF; so->so_proto = head->so_proto; so->so_timeo = head->so_timeo; - so->so_pgid = head->so_pgid; + fsetown(fgetown(&(head->so_sigio)), &(so->so_sigio), soo_unsetown); (void) soreserve(so, head->so_snd.sb_hiwat, head->so_rcv.sb_hiwat); soqinsque(head, so, soqueue); if ((*so->so_proto->pr_usrreq)(so, PRU_ATTACH, @@ -328,10 +328,7 @@ wakeup((caddr_t)&sb->sb_cc); } if (so->so_state & SS_ASYNC) { - if (so->so_pgid < 0) - gsignal(-so->so_pgid, SIGIO); - else if (so->so_pgid > 0 && (p = pfind(so->so_pgid)) != 0) - psignal(p, SIGIO); + sigio_p_or_pg(&(so->so_sigio), SIGIO, 0); } } Index: sys/net/bpf.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/net/bpf.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 bpf.c --- bpf.c 1997/05/09 09:34:44 1.1.1.1 +++ bpf.c 1997/09/27 00:11:57 @@ -59,6 +59,7 @@ #include #include #include +#include /* get fsetown, funsetown, fgetown */ #include #if defined(sparc) && BSD < 199103 @@ -352,6 +353,7 @@ register int s; s = splimp(); + funsetown(&d->bd_sigio); if (d->bd_bif) bpf_detachd(d); splx(s); @@ -510,10 +512,7 @@ wakeup((caddr_t)d); if (d->bd_async && d->bd_sig) - if (d->bd_pgid > 0) - gsignal (d->bd_pgid, d->bd_sig); - else if (p = pfind (-d->bd_pgid)) - psignal (p, d->bd_sig); + sigio_p_or_pg(&(d->bd_sigio), d->bd_sig, 0); #if BSD >= 199103 selwakeup(&d->bd_sel); @@ -589,6 +588,19 @@ } /* + * Callback to undo FIOSETOWN on process or process group death + */ +static void +bpfunsetown(sigio) + struct sigio *sigio; +{ + register int s = splimp(); + + funsetown(sigio); + splx(s); +} + +/* * FIONREAD Check for read packet available. * SIOCGIFADDR Get interface address - convenient hook to driver. * BIOCGBLEN Get buffer len [for read()]. @@ -815,18 +827,28 @@ d->bd_async = *(int *)addr; break; -/* N.B. ioctl (FIOSETOWN) and fcntl (F_SETOWN) both end up doing the - equivalent of a TIOCSPGRP and hence end up here. *However* TIOCSPGRP's arg - is a process group if it's positive and a process id if it's negative. This - is exactly the opposite of what the other two functions want! Therefore - there is code in ioctl and fcntl to negate the arg before calling here. */ + case FIOSETOWN: + s = splimp(); + error = fsetown(*(int *)addr, &(d->bd_sigio), bpfunsetown); + splx(s); + break; - case TIOCSPGRP: /* Process or group to send signals to */ - d->bd_pgid = *(int *)addr; + case FIOGETOWN: + s = splimp(); + *(int *)addr = fgetown(&(d->bd_sigio)); + splx(s); + break; + + case TIOCSPGRP: + s = splimp(); + error = fsetown(-(*(int *)addr), &(d->bd_sigio), bpfunsetown); + splx(s); break; case TIOCGPGRP: - *(int *)addr = d->bd_pgid; + s = splimp(); + *(int *)addr = -fgetown(&(d->bd_sigio)); + splx(s); break; case BIOCSRSIG: /* Set receive signal */ Index: sys/net/bpfdesc.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/net/bpfdesc.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 bpfdesc.h --- bpfdesc.h 1997/05/09 09:34:45 1.1.1.1 +++ bpfdesc.h 1997/09/26 14:06:51 @@ -44,6 +44,7 @@ #define _NET_BPFDESC_H_ #include +#include /* pick up sigio */ /* * Descriptor associated with each open bpf file. @@ -78,7 +79,8 @@ u_char bd_immediate; /* true to return on packet arrival */ int bd_async; /* non-zero if packet reception should generate signal */ int bd_sig; /* signal to send upon packet reception */ - pid_t bd_pgid; /* process or group id for signal */ + struct sigio bd_sigio; /* credentials and pointer to proc + * or group for SIGIO */ #if BSD < 199103 u_char bd_selcoll; /* true if selects collide */ int bd_timedout; Index: sys/net/if_tun.c =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/net/if_tun.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 if_tun.c --- if_tun.c 1997/05/09 09:34:46 1.1.1.1 +++ if_tun.c 1997/09/27 00:18:39 @@ -30,6 +30,7 @@ #include #include #include +#include #ifdef __FreeBSD__ #include #endif @@ -194,7 +195,7 @@ } splx(s); } - tp->tun_pgrp = 0; + funsetown(&tp->tun_sigio); selwakeup(&tp->tun_rsel); TUNDEBUG ("%s%d: closed\n", ifp->if_name, ifp->if_unit); @@ -359,11 +360,8 @@ tp->tun_flags &= ~TUN_RWAIT; wakeup((caddr_t)tp); } - if (tp->tun_flags & TUN_ASYNC && tp->tun_pgrp) { - if (tp->tun_pgrp > 0) - gsignal(tp->tun_pgrp, SIGIO); - else if (p = pfind(-tp->tun_pgrp)) - psignal(p, SIGIO); + if (tp->tun_flags & TUN_ASYNC) { + sigio_p_or_pg(&(tp->tun_sigio), SIGIO, 0); } selwakeup(&tp->tun_rsel); return 0; @@ -423,12 +421,20 @@ *(int *)data = 0; splx(s); break; + case FIOSETOWN: + return (fsetown(*(int *)data, &(tp->tun_sigio), funsetown)); + + case FIOGETOWN: + *(int *)data = fgetown(&(tp->tun_sigio)); + return (0); + case TIOCSPGRP: - tp->tun_pgrp = *(int *)data; - break; + return (fsetown(-(*(int *)data), &(tp->tun_sigio), funsetown)); + case TIOCGPGRP: - *(int *)data = tp->tun_pgrp; - break; + *(int *)data = -fgetown(&(tp->tun_sigio)); + return (0); + default: return (ENOTTY); } Index: sys/net/if_tun.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/net/if_tun.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 if_tun.h --- if_tun.h 1997/05/09 09:34:46 1.1.1.1 +++ if_tun.h 1997/09/26 12:25:04 @@ -33,7 +33,8 @@ #define TUN_READY (TUN_OPEN | TUN_INITED | TUN_IASET) struct ifnet tun_if; /* the interface */ - int tun_pgrp; /* the process group - if any */ + struct sigio tun_sigio; /* credentials and pointer to proc + * or group for SIGIO */ struct selinfo tun_rsel; /* read select */ struct selinfo tun_wsel; /* write select (not used) */ #if NBPFILTER > 0 Index: sys/sys/filedesc.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/sys/filedesc.h,v retrieving revision 1.2 diff -u -r1.2 filedesc.h --- filedesc.h 1997/05/13 12:05:40 1.2 +++ filedesc.h 1997/09/26 22:39:20 @@ -96,6 +96,9 @@ /* * Kernel global variables and routines. */ +void funsetown __P((struct sigio *)); +int fsetown __P((pid_t, struct sigio *, void (*) (struct sigio *) )); +pid_t fgetown __P((struct sigio *)); int dupfdopen __P((struct filedesc *, int, int, int, int)); int fdalloc __P((struct proc *p, int want, int *result)); int fdavail __P((struct proc *p, int n)); Index: sys/sys/proc.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/sys/proc.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 proc.h --- proc.h 1997/05/09 09:35:08 1.1.1.1 +++ proc.h 1997/09/26 22:37:25 @@ -46,6 +46,7 @@ #include /* For struct rtprio. */ #include /* For struct selinfo. */ #include /* For structs itimerval, timeval. */ +#include /* For SLIST_HEAD, SLIST_ENTRY. */ /* * One structure allocated per session. @@ -58,6 +59,8 @@ char s_login[MAXLOGNAME]; /* Setlogin() name. */ }; +SLIST_HEAD(sigiolst, sigio); + /* * One structure allocated per process group. */ @@ -65,6 +68,7 @@ struct pgrp *pg_hforw; /* Forward link in hash bucket. */ struct proc *pg_mem; /* Pointer to pgrp members. */ struct session *pg_session; /* Pointer to session. */ + struct sigiolst pg_sigiolst; /* List of sigio sources */ pid_t pg_id; /* Pgrp id. */ int pg_jobc; /* # procs qualifying pgrp for job control */ }; @@ -136,9 +140,11 @@ struct vnode *p_textvp; /* Vnode of executable. */ + struct sigiolst p_sigiolst; /* List of sigio sources */ + char p_lock; /* Process lock count. */ char p_pad2[3]; /* alignment */ - long p_spare[2]; /* Pad to 256, avoid shifting eproc. XXX */ + long p_spare[1]; /* Pad to 256, avoid shifting eproc. XXX */ /* End area that is zeroed on creation. */ #define p_endzero p_startcopy @@ -221,6 +227,24 @@ gid_t p_svgid; /* Saved effective group id. */ int p_refcnt; /* Number of references. */ }; + +/* + * + */ +struct sigio { + struct ucred *sio_ucred; /* Current credentials. */ + uid_t sio_ruid; /* Real user id. */ + union { + struct proc *siu_proc; /* Process to receive SIGIO/SIGURG */ + struct pgrp *siu_pgrp; /* Process group to receive ... */ + } sio_u; + void (*sio_unsetown) __P((struct sigio *)); + SLIST_ENTRY(sigio) sio_pgsigio; /* sigio's for process or group */ + pid_t sio_pgid; /* pgid for signals */ +}; +#define sio_proc sio_u.siu_proc +#define sio_pgrp sio_u.siu_pgrp + #ifdef KERNEL /* Index: sys/sys/signalvar.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/sys/signalvar.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 signalvar.h --- signalvar.h 1997/05/09 09:35:09 1.1.1.1 +++ signalvar.h 1997/09/26 13:24:15 @@ -162,6 +162,7 @@ void sigexit __P((struct proc *, int)); void siginit __P((struct proc *p)); void trapsignal __P((struct proc *p, int sig, unsigned code)); +void sigio_p_or_pg __P((struct sigio *, int signum, int checkctty)); /* * Machine-dependent functions: Index: sys/sys/socketvar.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/sys/socketvar.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 socketvar.h --- socketvar.h 1997/05/09 09:35:09 1.1.1.1 +++ socketvar.h 1997/09/26 22:52:13 @@ -40,6 +40,7 @@ #include /* for struct stat */ #include /* for struct filedesc */ #include /* for struct selinfo */ +#include /* for struct sigio */ /* * Kernel structure per socket. @@ -73,7 +74,8 @@ short so_qlimit; /* max number queued connections */ short so_timeo; /* connection timeout */ u_short so_error; /* error affecting connection */ - pid_t so_pgid; /* pgid for signals */ + struct sigio so_sigio; /* credentials and pointer to proc + * or group for SIGIO/SIGURG */ u_long so_oobmark; /* chars to oob mark */ /* * Variables for socket buffering. @@ -211,6 +213,7 @@ int soo_select __P((struct file *fp, int which, struct proc *p)); int soo_close __P((struct file *fp, struct proc *p)); int soo_stat __P((struct socket *, struct stat *)); +void soo_unsetown __P((struct sigio *)); /* * From uipc_socket and friends Index: sys/sys/tty.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/sys/tty.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 tty.h --- tty.h 1997/05/09 09:35:10 1.1.1.1 +++ tty.h 1997/09/26 13:00:15 @@ -44,6 +44,7 @@ #include #include /* For struct selinfo. */ +#include /* For struct sigio */ /* * Clists are character lists, which is a variable length linked list @@ -79,6 +80,8 @@ int t_timeout; /* Timeout for ttywait() */ struct pgrp *t_pgrp; /* Foreground process group. */ struct session *t_session; /* Enclosing session. */ + struct sigio t_sigio; /* credentials and pointer to proc + * or group for SIGIO */ struct selinfo t_rsel; /* Tty read/oob select. */ struct selinfo t_wsel; /* Tty write select. */ struct termios t_termios; /* Termios state. */ Index: sys/sys/types.h =================================================================== RCS file: /usr/cvs/repository/FreeBSD-2.1/sys/sys/types.h,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 types.h --- types.h 1997/05/09 09:35:10 1.1.1.1 +++ types.h 1997/09/26 13:41:46 @@ -157,6 +157,7 @@ */ struct proc; struct pgrp; +struct sigio; struct ucred; struct rusage; struct file; From owner-freebsd-hackers Sat Sep 27 01:14:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA08802 for hackers-outgoing; Sat, 27 Sep 1997 01:14:41 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA08781; Sat, 27 Sep 1997 01:14:36 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id BAA23841; Sat, 27 Sep 1997 01:11:53 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA10855; Sat, 27 Sep 1997 01:11:52 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA00487; Sat, 27 Sep 1997 01:11:51 -0700 (PDT) From: Don Lewis Message-Id: <199709270811.BAA00487@salsa.gv.tsc.tdk.com> Date: Sat, 27 Sep 1997 01:11:51 -0700 In-Reply-To: "Rodney W. Grimes" "Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail)" (Sep 26, 11:10pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Rodney W. Grimes" , dg@root.com Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 26, 11:10pm, "Rodney W. Grimes" wrote: } Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's m } > You can't send a packet to yourself under normal circumstances (ethernet } > is a simplex device). } } Only broken NIC chips are simplex, even the 82586 is actually capable } of hering itself talk on the wire, though most drives do not set } the chip into this mode. Either way ``ethernet is _not_ a simplex } device''. That's only true of coaxial media. Over twisted pair, if you see data start arriving on the receive pair while your transmitting then you have to assume that the data is being sent by another station and you've got a collision situation. However, you may have the option to loop back your transmitted data to your receiver after the receiver stage where collision sensing is done. I believe this is known as natural loopback. I don't think it's commonly used. From owner-freebsd-hackers Sat Sep 27 01:20:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09191 for hackers-outgoing; Sat, 27 Sep 1997 01:20:57 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA09185 for ; Sat, 27 Sep 1997 01:20:54 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA17786; Sat, 27 Sep 1997 10:20:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA15909; Sat, 27 Sep 1997 09:51:38 +0200 (MET DST) Message-ID: <19970927095138.KZ52868@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 09:51:38 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: rivers@dignus.com (Thomas David Rivers) Subject: Re: r-cmds and DNS and /etc/host.conf References: <199709251052.GAA08043@lakes.dignus.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709251052.GAA08043@lakes.dignus.com>; from Thomas David Rivers on Sep 25, 1997 06:52:45 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > Hmmm... my /etc/resolv.conf on the gateway machine > doesn't have my (local) domain name. That is, the gateway machine > is named "ponds.dignus.com", but /etc/resolv.conf has: > > domain vnet.net > nameserver 166.82.1.3 > nameserver 166.82.1.8 > > (which is the domain of my ISP and it's two nameservers.) > > Just to get concrete here, my two machines are called: > ponds.dignus.com (the gateway machine) > lakes.dignus.com (the internal machine) > > Also, one difference is that I do have a hosts.equiv on the gateway (ponds): > > #localhost > #my_very_good_friend.domain > localhost > ponds > ponds.dignus.com > puddles > puddles.dignus.com > rivulet > rivulet.dignus.com > > But, I wouldn't expect that to matter... Some of this apparently does matter. Why don't you start a (cache-only) nameserver on ponds, and see what lakes is asking for? Remember, SIGUSR1 to named increases its debugging level. I just did this. With an /etc/hosts.equiv with non-FQDNs, and an /etc/hosts with non-FQDNs, no requests come from the rlogin server machine. So do you have all the above name combinations in your /etc/hosts? Besides, i don't understand why you aren't using a local nameserver anyway. -- 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-hackers Sat Sep 27 01:22:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09265 for hackers-outgoing; Sat, 27 Sep 1997 01:22:21 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA09259 for ; Sat, 27 Sep 1997 01:22:16 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA17797 for freebsd-hackers@freefall.FreeBSD.org; Sat, 27 Sep 1997 10:22:14 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id KAA15965; Sat, 27 Sep 1997 10:02:28 +0200 (MET DST) Message-ID: <19970927100228.BQ43995@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 10:02:28 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf References: <199709251058.GAA08060@lakes.dignus.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709251058.GAA08060@lakes.dignus.com>; from Thomas David Rivers on Sep 25, 1997 06:58:10 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > I originally reported this problem in version 2.1.5 of FreeBSD, on > Aug. 16th, 1996. The subject of that message was > > "Nameserver and 'rlogin' in 2.1.5." > > it should be in the freebsd-hackers mail archives. But, at that time > I thought it was a totally different problem and let it languish. > Since it didn't get resolved; particularly when my network situation > changed, I brought it back up... I still blame your setup. As well as Sean, i can't reproduce the problem in a way where i could not resolve it using /etc/hosts. One particular thing i've just noticed (by tracing the nameserver's requests, as mentioned in the other mail) was... but first the setup, so you can match it your situation: uncle.heep.sax.de uriah.heep.sax.de | | | +--------------------+ +--- . . . dialup link to Ethernet 192.168.0 Internet rlogin from uriah to uncle worked well, and generated no DNS queries. rlogin back from uncle to uriah caused one query from uriah for `localhost.heep.sax.de', which was not resolved by placing this name in /etc/hosts on uriah. I then found that i had to replace the line 127.1 localhost localhost.heep.sax.de by 127.0.0.1 localhost localhost.heep.sax.de and *bingo* it worked. Now, we've been discussing this before... (Ok, now fix the broken setup again to use DNS for everything. Heck, why should i rely on outdated /etc/hosts files? :-) -- 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-hackers Sat Sep 27 01:29:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09716 for hackers-outgoing; Sat, 27 Sep 1997 01:29:13 -0700 (PDT) Received: from ns1.ied-vorstu.ac.ru (ns1.IED-VorSTU.ac.ru [193.233.113.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA09689 for ; Sat, 27 Sep 1997 01:28:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns1.ied-vorstu.ac.ru (8.8.7/8.8.7) with SMTP id MAA02582 for ; Sat, 27 Sep 1997 12:22:56 +0400 (MSD) Date: Sat, 27 Sep 1997 12:22:56 +0400 (MSD) From: "Vasily V. Grechishnikov" X-Sender: bazilio@ns1 To: freebsd-hackers@freebsd.org Subject: Just curios: fd driver in -current broken ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! My FreeBSD box runs FreeBSD-current. And few days ago, after latest kernel remake, it begins to drops down while accessing to floppies: panic: timeout table is full. Hardware: Intel 430VX + 120 MHz P5. Thanks , Vasily . ***************[ FreeBSD it is coolest UNIX for PCs ! ]*************** * System admin/programmer, ftp/web/post master. * IM & PE of VorSTU * * Home Page: http://www.ied-vorstu.ac.ru/~bazilio * ********************************************************************** From owner-freebsd-hackers Sat Sep 27 01:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA11066 for hackers-outgoing; Sat, 27 Sep 1997 01:51:04 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA11061 for ; Sat, 27 Sep 1997 01:50:57 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA17912 for freebsd-hackers@FreeBSD.ORG; Sat, 27 Sep 1997 10:50:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id KAA16122; Sat, 27 Sep 1997 10:29:14 +0200 (MET DST) Message-ID: <19970927102914.WI52706@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 10:29:14 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. References: <199709250742.AAA10411@usr03.primenet.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709250742.AAA10411@usr03.primenet.com>; from Terry Lambert on Sep 25, 1997 07:41:59 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > IMO, this is a bug in HUP processing. I think that HUP should be sent to > the process group members from the process group leaders before the tty > is revoked, instead of simply erroring out the reads/writes. > > SVR4, SVR3, SCO Xenix, SCO UNIX, UnixWare, Solaris, SunOS, Fortune, > Cubix, Huerikon, Arrete, Unisys UNIX, UNICOS, Linux, Cubix, Intel > UNIX, Intel Xenix, PrimeOS, ISC UNIX, Ultrix, OSF/1, OSF/2, Microport > UNIX v2, Microport UNIX v3, Altos Xenix and UNIX, Cogent, Coherent, > and practically every other UNIX on the planet does this. > > But FreeBSD does not. I've seen this problem on Illtrix on an old Vax2000 as well. To what shell are your claims above related? ksh has a weird (mis-)feature to lead all its kids to death when it dies itself. You have to explicitly make it forget about some child in order to prevent it from doing so, even if the child was in a background process group (albeit i usually prefer `kill -9 $$' to logout instead of dealing with this cr*p, or rather, i quickly `exec csh' before starting to work). csh never did it this way, it always left running background jobs alone, which sounds logical to me (why did you put it into a running state in background at all, if not for keeping it running?). So, take out the SVR3's above (for not having job control at all), use csh, and retry your tests. (You probably need to take out SCO as well, since what they call a csh is anything else but a csh.) Alternatively, use ksh93 on FreeBSD, and you'll see the same behaviour, i'm convinced. Btw., nvi doesn't suffer from this behaviour. Ignoring an error return from the input device is always an error on the side of the program in question. -- 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-hackers Sat Sep 27 01:51:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA11108 for hackers-outgoing; Sat, 27 Sep 1997 01:51:37 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA11088 for ; Sat, 27 Sep 1997 01:51:10 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA17914 for freebsd-hackers@FreeBSD.ORG; Sat, 27 Sep 1997 10:51:07 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id KAA16209; Sat, 27 Sep 1997 10:40:08 +0200 (MET DST) Message-ID: <19970927104008.PZ43927@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 10:40:08 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Daniel O'Callaghan on Sep 25, 1997 16:28:12 +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Daniel O'Callaghan wrote: > Kill the process. The vty has been disconnected without logging out, so > ee goes into a loop. vi and pico do the same thing. Btw., it seems to be a bug in ncurses. ee correctly checks for an error return from wgetch() (albeit using -1, as opposed to the opaque macro ERR), but wgetch() is returning 0. (gdb) step Single stepping until exit from function wrefresh, which has no line number information. main (argc=2, argv=0xefbfd7e4) at /usr/src/usr.bin/ee/ee.c:608 608 in = wgetch(text_win); (gdb) 609 if (in == -1) (gdb) print in $2 = 0 (gdb) list 604 605 while(edit) 606 { 607 wrefresh(text_win); 608 in = wgetch(text_win); 609 if (in == -1) 610 exit(0); 611 612 resize_check(); 613 -- 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-hackers Sat Sep 27 02:03:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA11895 for hackers-outgoing; Sat, 27 Sep 1997 02:03:35 -0700 (PDT) Received: from ns1.ied-vorstu.ac.ru (ns1.IED-VorSTU.ac.ru [193.233.113.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA11852 for ; Sat, 27 Sep 1997 02:02:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns1.ied-vorstu.ac.ru (8.8.7/8.8.7) with SMTP id MAA03474 for ; Sat, 27 Sep 1997 12:57:41 +0400 (MSD) Date: Sat, 27 Sep 1997 12:57:41 +0400 (MSD) From: "Vasily V. Grechishnikov" X-Sender: bazilio@ns1 To: freebsd-hackers@freebsd.org Subject: Tulip IPX support in -current unimplemented, why ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I have the following problem: My FreeBSD box runs FreeBSD-current and it provides IP/IPX routing between the four newtwork interfaces ( 3 NE2000 + 1 Tulip). Sometime ago since the CVSup'ing of -current my tulip card couldn't assign IPX address to interface by the ifconfig. I seen at /pci/if_de.c and can't find implementation of IPX portion of code for ioctl requests ( SIOCSIFADDR). After patching I can work with IPX on tulip but, the next misteriuos thing is happen : IPX packets to one of my networks, connected to tulip card can't successfully forwards from the remote network : NET 0 NET 1 Broken IPX net. Good IPX net. *--------------- Tulip ( ) NE2000 ------------* ( FreeBSD box ) Good IPX net +--------( )NE2000--1'st if(*)2'nd if--+ | NetWare 3.12 | | NET 2 | | | | NetWare 4.1 | NET 3 | 1'st if ( FreeBSD box) 2'nd if NET 4 | +-------------NetWare 4.1 ( unreachable from tulip). But Netware 4.1 from unreachable network can see from a NET 1-3 :-( Thanks , Vasily . ***************[ FreeBSD it is coolest UNIX for PCs ! ]*************** * System admin/programmer, ftp/web/post master. * IM & PE of VorSTU * * Home Page: http://www.ied-vorstu.ac.ru/~bazilio * ********************************************************************** From owner-freebsd-hackers Sat Sep 27 02:16:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA13069 for hackers-outgoing; Sat, 27 Sep 1997 02:16:51 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA13060 for ; Sat, 27 Sep 1997 02:16:48 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id CAA01689; Sat, 27 Sep 1997 02:15:48 -0700 (PDT) Date: Sat, 27 Sep 1997 02:15:48 -0700 (PDT) From: "Jamil J. Weatherbee" To: Ken Hansen cc: Christoph Kukulies , Luigi Rizzo , freebsd-hackers@freefall.FreeBSD.org Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q In-Reply-To: <342BE6B3.27A5@njcc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Here is my two cents --- when you have users that decide to suddenly cycle the power anything with moving parts is in danger. I prefer the solution of 100 base T cards and running of boot eprom w large amounts of memory on the workstations (64MB - 128MB) this certainly has to be better than any harddrive as it is pretty hard to destroy and I can swap out a machine simply by moving in anothet cpu cabinet, and changing the MAC address in the bootptab it is seamless. > > BTW I believe Sun has droped support for true diskless workstations, > in stead they have CacheFS clients, where the machine boots off the > server, but keeps a cache of NFS files accessed on a local HD - that > drive is cleared on reboot. > > Just wnated to throw in my .02 worth. > > Ken > khansen@njcc.com > From owner-freebsd-hackers Sat Sep 27 03:23:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA15739 for hackers-outgoing; Sat, 27 Sep 1997 03:23:21 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA15734 for ; Sat, 27 Sep 1997 03:23:17 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.7/8.8.7) with ESMTP id DAA03335; Sat, 27 Sep 1997 03:23:15 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.7/8.8.7) with SMTP id DAA01288; Sat, 27 Sep 1997 03:23:15 -0700 (PDT) Date: Sat, 27 Sep 1997 03:23:15 -0700 (PDT) From: Chris Timmons To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709270110.SAA01062@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Are any of the folks who have "fxp driver" problems using aliases? I had an ip alias die on me the other day with a pile of arpresolve: can't allocate llinfo for n.n.n.n. where n.n.n.n was aliased on fxp0. 2.2-STABLE ~9/9/97 It probably just is a coincidence that this happened to me on fxp0; at about the same time i installed the pro/100b I started sending rip announcements up to the system through ppp0 from another box that has an ip address on the same network as fxp0's home via the miracle of proxyarp. This scenario has only happened once in about 6 weeks. To get things unconfused I had to say 'ifconfig fxp0 alias ...' again. Obviously this has nothing to do with the fxp driver per se, just that the symptoms were as these people described (at least as far as the ip alias was concerned.) Traffic through fxp0's true home network was not affected. -Chris From owner-freebsd-hackers Sat Sep 27 03:32:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA17269 for hackers-outgoing; Sat, 27 Sep 1997 03:32:45 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA17143 for ; Sat, 27 Sep 1997 03:32:36 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id FAA25079 for ; Sat, 27 Sep 1997 05:32:05 -0500 Message-Id: <3.0.2.32.19970927053159.006c81e8@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 27 Sep 1997 05:31:59 -0500 To: freebsd-hackers@FreeBSD.ORG From: Tony Overfield Subject: Re: Raise your hand if you know how to make this work. In-Reply-To: <199709250723.AAA09638@usr03.primenet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> there is a function to do this for you >> it's rather trivial. >> check clock.c >> and see how the PCAUDIO device uses this to get itself >> called 16000 times per second.. At 07:23 AM 9/25/97 +0000, Terry Lambert wrote: >> > Note: this is about twice as fast as the standard clock can go; at >> > the highest divider, it's only capable of 8192 interrupts a second. >> >Jamil J. Weatherbee wrote >> If we are still talking about an 8253 I know you to be wrong here, the >> frequency varies like 1.9MHz/(1-65535). > >This information is from the Linux tier code and from the FreeBSD >clock divider code for the PC audio driver, and not from the chipset >documentation, so I'm prepared to be wrong (along with the comments >in both these drivers). I think Terry has confused the two "standard" timers. The "standard clock" timer, on IRQ0, is a 1.193 MHz clock with a programmable 16-bit divisor that can interrupt as fast as you would ever want it to. The "CMOS real-time clock" has a periodic interrupt, on IRQ8, based on a 32768 Hz clock with a small set of divisors that support interrupt rates between 2 Hz and 8192 Hz, inclusive, in powers of two. From owner-freebsd-hackers Sat Sep 27 04:13:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19192 for hackers-outgoing; Sat, 27 Sep 1997 04:13:48 -0700 (PDT) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19184 for ; Sat, 27 Sep 1997 04:13:38 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id HAA16061 for ; Sat, 27 Sep 1997 07:14:46 -0400 (EDT) Date: Sat, 27 Sep 1997 07:14:46 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: cvs-crypto Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Have there been any updates to cvs-crypto since 2.2.2-RELEASE? I do a periodic cvsup to 2.2_RELENG and have *never* noticed any cvs-crypto updates, I am beginning to wonder if I misconfigured something. -- David Cross From owner-freebsd-hackers Sat Sep 27 04:14:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19223 for hackers-outgoing; Sat, 27 Sep 1997 04:14:14 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19214 for ; Sat, 27 Sep 1997 04:14:06 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id HAA15429 for ; Sat, 27 Sep 1997 07:18:50 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sat, 27 Sep 1997 07:18:50 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: protocol for CVSup? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i'm running NATd so i can have more than one machine operating on only one IP address, but i think it is causing breakage with CVSup... does anyone know what ports and what type of traffic i have to have tunneled to the machine running cvsup? From owner-freebsd-hackers Sat Sep 27 04:37:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19738 for hackers-outgoing; Sat, 27 Sep 1997 04:37:51 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19733 for ; Sat, 27 Sep 1997 04:37:43 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id EAA24201; Sat, 27 Sep 1997 04:37:40 -0700 (MST) From: Terry Lambert Message-Id: <199709271137.EAA24201@usr04.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 27 Sep 1997 11:37:40 +0000 (GMT) Cc: hackers@FreeBSD.ORG, rivers@dignus.com In-Reply-To: <19970927095138.KZ52868@uriah.heep.sax.de> from "J Wunsch" at Sep 27, 97 09:51:38 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Besides, i don't understand why you aren't using a local nameserver > anyway. The easy answer to this is that there isn't a Motif-based listbox setup for the nameserver code, where you just fill in the names you want, and it does the rest. The less easy answer is "it's hard enough to set up that it's not worth doing for most people". 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-hackers Sat Sep 27 04:41:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19841 for hackers-outgoing; Sat, 27 Sep 1997 04:41:01 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19836 for ; Sat, 27 Sep 1997 04:40:54 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id EAA24299; Sat, 27 Sep 1997 04:40:52 -0700 (MST) From: Terry Lambert Message-Id: <199709271140.EAA24299@usr04.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 27 Sep 1997 11:40:52 +0000 (GMT) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19970927100228.BQ43995@uriah.heep.sax.de> from "J Wunsch" at Sep 27, 97 10:02:28 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I originally reported this problem in version 2.1.5 of FreeBSD, on > > Aug. 16th, 1996. The subject of that message was > > > > "Nameserver and 'rlogin' in 2.1.5." > > > > it should be in the freebsd-hackers mail archives. But, at that time > > I thought it was a totally different problem and let it languish. > > Since it didn't get resolved; particularly when my network situation > > changed, I brought it back up... > > I still blame your setup. As well as Sean, i can't reproduce the > problem in a way where i could not resolve it using /etc/hosts. One > particular thing i've just noticed (by tracing the nameserver's > requests, as mentioned in the other mail) was... but first the setup, > so you can match it your situation: Of course, you should feel free to suggest to us any soloution which does not require us to run named to implement. And not feel free to suggest running named. 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-hackers Sat Sep 27 04:43:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19919 for hackers-outgoing; Sat, 27 Sep 1997 04:43:00 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19899; Sat, 27 Sep 1997 04:42:41 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id EAA24360; Sat, 27 Sep 1997 04:42:15 -0700 (MST) From: Terry Lambert Message-Id: <199709271142.EAA24360@usr04.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Sat, 27 Sep 1997 11:42:14 +0000 (GMT) Cc: rgrimes@GndRsh.aac.dev.com, dg@root.com, tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709270811.BAA00487@salsa.gv.tsc.tdk.com> from "Don Lewis" at Sep 27, 97 01:11:51 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > } Only broken NIC chips are simplex, even the 82586 is actually capable > } of hering itself talk on the wire, though most drives do not set > } the chip into this mode. Either way ``ethernet is _not_ a simplex > } device''. > > That's only true of coaxial media. Over twisted pair, if you see > data start arriving on the receive pair while your transmitting then > you have to assume that the data is being sent by another station > and you've got a collision situation. Isn't this the hub's responsibility to distinguish and prevent? 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-hackers Sat Sep 27 04:54:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20262 for hackers-outgoing; Sat, 27 Sep 1997 04:54:13 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA20251 for ; Sat, 27 Sep 1997 04:54:05 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id EAA24656; Sat, 27 Sep 1997 04:54:03 -0700 (MST) From: Terry Lambert Message-Id: <199709271154.EAA24656@usr04.primenet.com> Subject: Re: ee taking up weird cpu amount. To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 27 Sep 1997 11:54:02 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970927102914.WI52706@uriah.heep.sax.de> from "J Wunsch" at Sep 27, 97 10:29:14 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > IMO, this is a bug in HUP processing. I think that HUP should be sent to > > the process group members from the process group leaders before the tty > > is revoked, instead of simply erroring out the reads/writes. > > > > SVR4, SVR3, SCO Xenix, SCO UNIX, UnixWare, Solaris, SunOS, Fortune, > > Cubix, Huerikon, Arrete, Unisys UNIX, UNICOS, Linux, Cubix, Intel > > UNIX, Intel Xenix, PrimeOS, ISC UNIX, Ultrix, OSF/1, OSF/2, Microport > > UNIX v2, Microport UNIX v3, Altos Xenix and UNIX, Cogent, Coherent, > > and practically every other UNIX on the planet does this. > > > > But FreeBSD does not. > > I've seen this problem on Illtrix on an old Vax2000 as well. To what > shell are your claims above related? None of them, of course. This has only to do with ourder of revoke() processing when revoke() is a result of on-to-off-DCD transition. > ksh has a weird (mis-)feature to lead all its kids to death when it > dies itself. This, of course, has to do with ksh's method of backgrounding a process. A process which is in the background is a chikd of init, and not a child of a process whose tty is being revoked -- and therefore can not be affected, one way or the other, by a revoke -- now can it? > You have to explicitly make it forget about some child in order to > prevent it from doing so, even if the child was in a background > process group (albeit i usually prefer `kill -9 $$' to logout > instead of dealing with this cr*p, or rather, i quickly `exec csh' > before starting to work). csh never did it this way, it always left > running background jobs alone, which sounds logical to me (why did > you put it into a running state in background at all, if not for > keeping it running?). The issue is legacy code for management of CPU time charges, IMO. The Bourne shell specifically distinguished children this way via the "nohup" mechansim. The csh implies "nohup" for all subshells, and in fact has a hard time implying non-"nohup" for a subshell. > So, take out the SVR3's above (for not having job control at all), use > csh, and retry your tests. (You probably need to take out SCO as > well, since what they call a csh is anything else but a csh.) > Alternatively, use ksh93 on FreeBSD, and you'll see the same > behaviour, i'm convinced. SVR3 supported "nohup". > Btw., nvi doesn't suffer from this behaviour. Ignoring an error > return from the input device is always an error on the side of the > program in question. An error return is impossible in the normal signal propagation case, since a SIGHUP propagation will have occurred, and the shell will have exited, prior to the error case being present. Dealing with the error case is only a requirement of FreeBSD and several other "broken" systems. The only other one that springs to mind at present is the tty code for Heurikon systems (a fairly wierd off-brand system in any case). I have programmed serial I/O on over 140 UNIX implementations in my career, and only Heurikon and FreeBSD don't propagate SIGHUP as I would expect them to. Take that for what it's worth; if we are talking compatability with historical behaviour, it should be worth a lot. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Sep 27 04:59:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20420 for hackers-outgoing; Sat, 27 Sep 1997 04:59:45 -0700 (PDT) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA20414 for ; Sat, 27 Sep 1997 04:59:27 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.7/8.8.7) id OAA10787; Sat, 27 Sep 1997 14:58:56 +0300 (EEST) From: Ruslan Ermilov Message-Id: <199709271158.OAA10787@relay.ucb.crimea.ua> Subject: Re: protocol for CVSup? In-Reply-To: from Alfred Perlstein at "Sep 27, 97 07:18:50 am" To: perlsta@cs.sunyit.edu (Alfred Perlstein) Date: Sat, 27 Sep 1997 14:58:56 +0300 (EEST) Cc: hackers@FreeBSD.ORG X-My-Interests: Unix,Oracle,Networking X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Once Alfred Perlstein wrote: > > i'm running NATd so i can have more than one machine operating on only one > IP address, but i think it is causing breakage with CVSup... > > does anyone know what ports and what type of traffic i have to have > tunneled to the machine running cvsup? > CVSup can operate in four modes: active, passive, multiplexed and SOCKS. In your situation you can use either passive or multiplexed modes. See man cvsup (-P option). -- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN From owner-freebsd-hackers Sat Sep 27 05:39:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21526 for hackers-outgoing; Sat, 27 Sep 1997 05:39:56 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA21512 for ; Sat, 27 Sep 1997 05:39:49 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 17059 invoked by uid 1001); 27 Sep 1997 12:39:45 +0000 (GMT) To: tlambert@primenet.com Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Your message of "Sat, 27 Sep 1997 11:42:14 +0000 (GMT)" References: <199709271142.EAA24360@usr04.primenet.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Sep 1997 14:39:45 +0200 Message-ID: <17057.875363985@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > That's only true of coaxial media. Over twisted pair, if you see > > data start arriving on the receive pair while your transmitting then > > you have to assume that the data is being sent by another station > > and you've got a collision situation. > > Isn't this the hub's responsibility to distinguish and prevent? Nope. A hub doesn't do anything with collisions - it just propagates them bit by bit. The NICs sense the collision. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Sep 27 05:51:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21836 for hackers-outgoing; Sat, 27 Sep 1997 05:51:09 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA21830 for ; Sat, 27 Sep 1997 05:51:03 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA21269 for hackers@FreeBSD.ORG; Sat, 27 Sep 1997 14:50:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA16653; Sat, 27 Sep 1997 14:39:34 +0200 (MET DST) Message-ID: <19970927143934.ZN26834@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 14:39:34 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: r-cmds and DNS and /etc/host.conf References: <19970927095138.KZ52868@uriah.heep.sax.de> <199709271137.EAA24201@usr04.primenet.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709271137.EAA24201@usr04.primenet.com>; from Terry Lambert on Sep 27, 1997 11:37:40 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > Besides, i don't understand why you aren't using a local nameserver > > anyway. > > The easy answer to this is that there isn't a Motif-based listbox > setup for the nameserver code, where you just fill in the names you > want, and it does the rest. > > The less easy answer is "it's hard enough to set up that it's not > worth doing for most people". Writing a Motif-based program would take a tremenduous amount of time. Why do it if the basic nameserver setup takes about 10 minutes? (No, not the caching-only server, this one only takes a couple of minutes.) I've seen the listbox-style cr*p that ships with some M$ operating system. The listboxes look nice, are terrible to use (it's a pain in the rear to add all the same standard MX records to each host using this kind of `editor'), but the vendor of that cr*p didn't get the underlying nameserver working correctly at all. (For example, the server never hands out authoritative answers, even if it is for sure an authoritative server.) And finally, using the shicky-micky listbox interface usually screws the nameserver setup at all. No, thanks. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Sep 27 05:51:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21869 for hackers-outgoing; Sat, 27 Sep 1997 05:51:35 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA21837 for ; Sat, 27 Sep 1997 05:51:09 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA21273 for freebsd-hackers@freefall.FreeBSD.org; Sat, 27 Sep 1997 14:51:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA16669; Sat, 27 Sep 1997 14:41:33 +0200 (MET DST) Message-ID: <19970927144133.UH24533@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 14:41:33 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf References: <19970927100228.BQ43995@uriah.heep.sax.de> <199709271140.EAA24299@usr04.primenet.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709271140.EAA24299@usr04.primenet.com>; from Terry Lambert on Sep 27, 1997 11:40:52 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > Of course, you should feel free to suggest to us any soloution which > does not require us to run named to implement. And not feel free to > suggest running named. It doesn't require named to run. I have reconstructed your setup, and proven that my named doesn't get any request if the setup is done correctly. As i've mentioned, the only pitfall was specifying localhost without adding the local domain, and with 127.1 instead of 127.0.0.1 in /etc/hosts. -- 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-hackers Sat Sep 27 05:52:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21927 for hackers-outgoing; Sat, 27 Sep 1997 05:52:31 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA21920 for ; Sat, 27 Sep 1997 05:52:14 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA21280 for freebsd-hackers@FreeBSD.ORG; Sat, 27 Sep 1997 14:52:07 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA16691; Sat, 27 Sep 1997 14:50:07 +0200 (MET DST) Message-ID: <19970927145007.HB02894@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 14:50:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. References: <19970927102914.WI52706@uriah.heep.sax.de> <199709271154.EAA24656@usr04.primenet.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709271154.EAA24656@usr04.primenet.com>; from Terry Lambert on Sep 27, 1997 11:54:02 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > > But FreeBSD does not. > > > > I've seen this problem on Illtrix on an old Vax2000 as well. To what > > shell are your claims above related? > > None of them, of course. Huh? ``To what shell?'' -- ``None of them.'' Am i in the wrong movie? > This has only to do with ourder of revoke() > processing when revoke() is a result of on-to-off-DCD transition. The foreground process group gets properly signalled. I've been using a FreeBSD-based ISP for long enough to know that it works. > > ksh has a weird (mis-)feature to lead all its kids to death when it > > dies itself. > > This, of course, has to do with ksh's method of backgrounding a > process. No. It hasn't. ksh properly shuffles each job into a separate process group (unlike the non-jobcontrol prehistoric /bin/sh). It *purposely* kills all its children before dying. That's why you can achieve the csh's default behaviour by logging out with ``kill -9 $$'' -- the background process groups will then behave like they do in csh. > The Bourne shell specifically distinguished children this way via > the "nohup" mechansim. The csh implies "nohup" for all subshells, No. The children are still sensitive to a SIGHUP if you send it to them. The shell doesn't send it to them iff they are _running in background_ when the shell exits. (Stopped jobs will be reaped nevertheless.) This is why the manual says that running background jobs are ``effectively nohuped''. They are not really nohuped. > > So, take out the SVR3's above (for not having job control at all), use > > csh, and retry your tests. > SVR3 supported "nohup". Sure, but that's another game. See above. > > Btw., nvi doesn't suffer from this behaviour. Ignoring an error > > return from the input device is always an error on the side of the > > program in question. > > An error return is impossible in the normal signal propagation case, That's no reason for curses to never assume an error could not happen. Errors can happen for more reasons. Errors are to be caught. Anything else is sloppy programming. There used to be a Usenix paper titled: Can't happen or /* NOTREACHED */ or Real Programs dump Core. -- 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-hackers Sat Sep 27 06:15:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA22738 for hackers-outgoing; Sat, 27 Sep 1997 06:15:34 -0700 (PDT) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA22720; Sat, 27 Sep 1997 06:15:20 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id JAA25094; Sat, 27 Sep 1997 09:16:17 -0400 (EDT) Date: Sat, 27 Sep 1997 09:16:17 -0400 (EDT) From: "David E. Cross" To: sthaug@nethelp.no cc: tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <17057.875363985@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 sthaug@nethelp.no wrote: > > > That's only true of coaxial media. Over twisted pair, if you see > > > data start arriving on the receive pair while your transmitting then > > > you have to assume that the data is being sent by another station > > > and you've got a collision situation. > > > > Isn't this the hub's responsibility to distinguish and prevent? > > Nope. A hub doesn't do anything with collisions - it just propagates > them bit by bit. The NICs sense the collision. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no Technically this is not even a colission situation. Many new NICs and Hubs (both must support it to work) support full-duplex 10BaseT, allowing 20MBits/sec. I am not sure what happens when it gets into the hub and needs to be propogated to other ports though *shrug*. Anyway... multiple packets being transmitted at the same time is detected by the NIC, and the NIC then sends a jamming signal which stops all transmissions on the network for a random time (each card that was transmitting durring this time sets a ranom timer for how long to wait, and they all try to re-transmit, using exponential backoff if there are additional collisions). This jamming signal is the actual 'collision', and is what shows up as a colision light on hubs/external transcievers. Excellent and page-turning reading that 802.* ;) -- David Cross From owner-freebsd-hackers Sat Sep 27 07:21:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA24898 for hackers-outgoing; Sat, 27 Sep 1997 07:21:28 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA24893 for ; Sat, 27 Sep 1997 07:21:15 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA22213; Sat, 27 Sep 1997 16:21:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id QAA16929; Sat, 27 Sep 1997 16:18:53 +0200 (MET DST) Message-ID: <19970927161853.LJ64939@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 16:18:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: joe@via.net Subject: Re: Truss/Trace? References: <199709260809.KAA10101@ws6423.gud.siemens.at> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709260809.KAA10101@ws6423.gud.siemens.at>; from marino.ladavac@siemens.at on Sep 26, 1997 10:09:43 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As marino.ladavac@siemens.at wrote: > > Any anyone implemented this for FreeBSD yet? > man ktrace. You'll need to rebuild the kernel Not if your version of FreeBSD is at least 2.2. Ktrace is now a standard feature. -- 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-hackers Sat Sep 27 07:52:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA25700 for hackers-outgoing; Sat, 27 Sep 1997 07:52:13 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA25671 for ; Sat, 27 Sep 1997 07:51:56 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA22406; Sat, 27 Sep 1997 16:51:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id QAA17020; Sat, 27 Sep 1997 16:35:58 +0200 (MET DST) Message-ID: <19970927163558.WP09379@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 16:35:58 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: mike@smith.net.au (Mike Smith) Subject: Re: Timeout for sh(1) 'read' ?? References: <199709260748.RAA00456@word.smith.net.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709260748.RAA00456@word.smith.net.au>; from Mike Smith on Sep 26, 1997 17:18:45 +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mike Smith wrote: > Hiho folks, a question for the sh(1) studs amongst you : > > - I want to prompt for input using 'read', and have the read return in > some fashion after a timeout. A quick search for the word `timeout' in the ksh93 man page unveils: TMOUT If set to a value greater than zero, TMOUT will be the default timeout value for the read built-in command. The select compound command terminates after TMOUT seconds when input is from a terminal. Otherwise, the shell will terminate if a line is not entered within the prescribed number of sec- onds while reading from a terminal. (Note that the shell can be compiled with a maxi- mum bound for this value which cannot be exceeded.) and: read [ -Aprs ] [ -d delim] [ -t timeout] [ -u unit] [ vname?prompt ] [ vname ... ] The shell input mechanism. One line is read and is broken up into fields using the characters in IFS as separators. [...] Posix doesn't seem to have any opinion for this, so it looks like just creeping featurism on ksh's side. (Posix only mentions option -r.) -- 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-hackers Sat Sep 27 07:53:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA25812 for hackers-outgoing; Sat, 27 Sep 1997 07:53:03 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA25790 for ; Sat, 27 Sep 1997 07:52:53 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA22410 for hackers@FreeBSD.ORG; Sat, 27 Sep 1997 16:52:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id QAA17060; Sat, 27 Sep 1997 16:42:50 +0200 (MET DST) Message-ID: <19970927164250.YQ59393@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 16:42:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? References: <199709260748.RAA00456@word.smith.net.au> <19970927163558.WP09379@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970927163558.WP09379@uriah.heep.sax.de>; from J Wunsch on Sep 27, 1997 16:35:58 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I wrote: > TMOUT If set to a value greater than zero, TMOUT > will be the default timeout value for the > read built-in command. The select compound > command terminates after TMOUT seconds when > input is from a terminal. Otherwise, the > shell will terminate if a line is not > entered within the prescribed number of sec- > onds while reading from a terminal. NB: pdksh only implements the last of the three features (at least my version)... > read [ -Aprs ] [ -d delim] [ -t timeout] [ -u > unit] [ vname?prompt ] [ vname ... ] ...nor does it support -t timeout. Adding -t timeout seems to be the best way to me. ${TMOUT} is just confusing given the multitude of things it's going to do. Btw., if you're going to do this, please do also implement -r. It seems to be mandated by Posix.2: By default, unless the -r option is specified, backslash (\) shall act as an escape character, as described in 3.2.1. 3.2.1 Escape Character (Backslash) A backslash that is not quoted shall preserve the literal value of the following character, with the exception of a . If a follows the backslash, the shell shall interpret this as line continuation. The backslash and shall be removed before splitting the input into tokens. (That is, the backslash should act like ^V.) -- 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-hackers Sat Sep 27 08:12:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA26561 for hackers-outgoing; Sat, 27 Sep 1997 08:12:19 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA26556 for ; Sat, 27 Sep 1997 08:12:17 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id IAA10270; Sat, 27 Sep 1997 08:11:22 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Sat, 27 Sep 1997 08:11:21 -0700 (PDT) From: Curt Sampson To: Drew Derbyshire cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: ATAPI Zip challenge : aftermath In-Reply-To: <342C42DD.7CAB7A7@kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Drew Derbyshire wrote: > Terry Lambert wrote: > > As I said in my other message, it's probably intentional to keep down > > support calls, since MS OS's (other than DOS) can't safely run binaries > > or swap from removable media. > > VM/370 could. :-) > (Showing my age today ...) No kidding. VM/370 is not, and never was a Microsoft OS. Alzheimers, is it? :-) cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Sat Sep 27 08:30:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA27430 for hackers-outgoing; Sat, 27 Sep 1997 08:30:28 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA27418 for ; Sat, 27 Sep 1997 08:30:22 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id RAA11811; Sat, 27 Sep 1997 17:29:23 +0200 (MET DST) Date: Sat, 27 Sep 1997 17:29:23 +0200 (MET DST) Message-Id: <199709271529.RAA11811@bitbox.follo.net> From: Eivind Eklund To: "Jordan K. Hubbard" CC: hackers@FreeBSD.ORG In-reply-to: "Jordan K. Hubbard"'s message of Thu, 25 Sep 1997 11:23:40 -0700 Subject: Re: How do I check out a snapshot? References: <199709251416.XAA04104@word.smith.net.au> <2904.875211820@time.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Yes, I tag and then I build from that tag after resyncronizing my > local repository. > > Unfortunately, tags are expensive and you don't just lay them down > for fun. In what way are release tags expensive? I've been thinking of using tags to make a commit a single operation instead of a bunch of changes just connected by the commit-log, and for storing meta-information for merges. With this and some merge-related tags (for storing meta-information) syncing RELENG_* and -current the way we want should become quite a bit easier. Are the tags so expensive this would be non-feasible? I thought they would be a comparatively cheap way of storing minor amounts of meta-information. Eivind. From owner-freebsd-hackers Sat Sep 27 09:20:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29957 for hackers-outgoing; Sat, 27 Sep 1997 09:20:49 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29934; Sat, 27 Sep 1997 09:20:34 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id JAA20171; Sat, 27 Sep 1997 09:16:35 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709271616.JAA20171@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709270811.BAA00487@salsa.gv.tsc.tdk.com> from Don Lewis at "Sep 27, 97 01:11:51 am" To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Sat, 27 Sep 1997 09:16:35 -0700 (PDT) Cc: dg@root.com, tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sep 26, 11:10pm, "Rodney W. Grimes" wrote: > } Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's m > } > You can't send a packet to yourself under normal circumstances (ethernet > } > is a simplex device). > } > } Only broken NIC chips are simplex, even the 82586 is actually capable > } of hering itself talk on the wire, though most drives do not set > } the chip into this mode. Either way ``ethernet is _not_ a simplex > } device''. > > That's only true of coaxial media. Over twisted pair, if you see > data start arriving on the receive pair while your transmitting then > you have to assume that the data is being sent by another station > and you've got a collision situation. Add ``in half duplex mode'' and the above holds water. But not for full duplex mode. My statement still holds true ``ethernet is _NOT_ a simplex device''. Why do you the the driver flag ``SIMPLEX'' exists, to deal with the fact that some ethernet interfaces on some systems do infact actuall here them selves talk, infact that use to be pretty much the norm back in the days of VAXEN. Here is another one to think about.... ``If you see data arriving on the receive pair _AND_ the mac source address is not yours you have a collision, or if you are talking to a full duplex port in full duplex mode you are using it.'' These types of designs preclude the use of the cheap TP<->AUI converter chips that just trash a 10Mhz signal onto CD when they see RD go active with XMTD active. Does Intel buy chance use something as stupid as the old 82503 or 82506 for the 10Mb TP interface? > However, you may have the option > to loop back your transmitted data to your receiver after the receiver > stage where collision sensing is done. I believe this is known as > natural loopback. I don't think it's commonly used. More common that looping it after the TP interface chip, and often implemented right in the NIC chip itself. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hackers Sat Sep 27 09:24:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA00277 for hackers-outgoing; Sat, 27 Sep 1997 09:24:58 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA00270 for ; Sat, 27 Sep 1997 09:24:54 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id QAA12003; Sat, 27 Sep 1997 16:24:50 GMT Date: Sat, 27 Sep 1997 09:24:49 -0700 (PDT) From: Dan Busarow To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: More ATAPI Zip news (will he ever shut up?) In-Reply-To: <199709270557.PAA00415@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Mike Smith wrote: > It's not *too* good in that FreeBSD still can't use it as a drive; it > comes up as a direct-access ATAPI disk but doesn't respond as a CDROM > so it's ignored. Arrrrr... Anyone have a good source for small IDE hard drives? > > The iomega web site is still refering to them as IDE Zip drives, > > has the packaging, part number or anything else changed? > > I believe so; I don't have access to any of the older IDE units at the > moment, but if you have a part number on the IDE version I can compare > it with that on the ATAPI-only one later today. P/N 320056-01, Model Z100IDE ZIP What about the LS120 drives, anyone using (and booting) those? Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Sat Sep 27 09:35:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA00808 for hackers-outgoing; Sat, 27 Sep 1997 09:35:41 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA00790; Sat, 27 Sep 1997 09:35:33 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id MAA17779; Sat, 27 Sep 1997 12:13:14 -0400 (EDT) Date: Sat, 27 Sep 1997 12:13:14 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709271613.MAA17779@sabre.goldsword.com> To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG, tlambert@primenet.com Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) Cc: dg@root.com, jfarmer@goldsword.com, rgrimes@GndRsh.aac.dev.com, tarkhil@mgt.msk.ru Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 11:42:14 +0000 (GMT) Terry Lambert said: [somebody else...] >> } Only broken NIC chips are simplex, even the 82586 is actually capable >> } of hering itself talk on the wire, though most drives do not set >> } the chip into this mode. Either way ``ethernet is _not_ a simplex >> } device''. >> >> That's only true of coaxial media. Over twisted pair, if you see >> data start arriving on the receive pair while your transmitting then >> you have to assume that the data is being sent by another station >> and you've got a collision situation. > >Isn't this the hub's responsibility to distinguish and prevent? > A hub that does this is usually called a "switch" :^> However, a hub that supports full-duplex links _must_ deal with some of the collision issues but a simpler level than a switch does. John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-hackers Sat Sep 27 09:48:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01366 for hackers-outgoing; Sat, 27 Sep 1997 09:48:14 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01346; Sat, 27 Sep 1997 09:48:05 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id JAA20293; Sat, 27 Sep 1997 09:47:15 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709271647.JAA20293@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <17057.875363985@verdi.nethelp.no> from "sthaug@nethelp.no" at "Sep 27, 97 02:39:45 pm" To: sthaug@nethelp.no Date: Sat, 27 Sep 1997 09:47:15 -0700 (PDT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > That's only true of coaxial media. Over twisted pair, if you see > > > data start arriving on the receive pair while your transmitting then > > > you have to assume that the data is being sent by another station > > > and you've got a collision situation. > > > > Isn't this the hub's responsibility to distinguish and prevent? > > Nope. A hub doesn't do anything with collisions - it just propagates > them bit by bit. The NICs sense the collision. Better go think so more about that... it depends on the hub! Some hubs that have partitioning ability will automagically partition out someone who starts to transmit if the hub is sending data out that port, this is called autopartitioning and is used to stop baligerant (sp) mau's or Jabberers(sp). If you want something that really tries to ``prevent'' this you want a switch and not a hub, and you want full-duplex non-simplex NIC cards in every box connected to that switch, and no I'm not just talking about 100Base stuff here, it applies to both 10 and 100Base ethernet over TP. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hackers Sat Sep 27 09:53:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01651 for hackers-outgoing; Sat, 27 Sep 1997 09:53:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA01645 for ; Sat, 27 Sep 1997 09:53:48 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA23672 for hackers@FreeBSD.ORG; Sat, 27 Sep 1997 18:53:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id SAA19555; Sat, 27 Sep 1997 18:49:42 +0200 (MET DST) Message-ID: <19970927184942.UY26389@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 18:49:42 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? References: <199709251416.XAA04104@word.smith.net.au> <2904.875211820@time.cdrom.com> <199709271529.RAA11811@bitbox.follo.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709271529.RAA11811@bitbox.follo.net>; from Eivind Eklund on Sep 27, 1997 17:29:23 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Eivind Eklund wrote: > > Unfortunately, tags are expensive and you don't just lay them down > > for fun. > > In what way are release tags expensive? In terms of disk activity, and network traffic caused by them for CVSup and CTM mirror users. -- 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-hackers Sat Sep 27 10:01:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02056 for hackers-outgoing; Sat, 27 Sep 1997 10:01:18 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02049 for ; Sat, 27 Sep 1997 10:01:13 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id TAA20920 for ; Sat, 27 Sep 1997 19:01:41 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id TAA22327 for hackers@FreeBSD.ORG; Sat, 27 Sep 1997 19:00:42 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id SAA07806; Sat, 27 Sep 1997 18:41:18 +0200 (CEST) Message-ID: <19970927184118.14580@keltia.freenix.fr> Date: Sat, 27 Sep 1997 18:41:18 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? References: <199709251416.XAA04104@word.smith.net.au> <2904.875211820@time.cdrom.com> <199709271529.RAA11811@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199709271529.RAA11811@bitbox.follo.net>; from Eivind Eklund on Sat, Sep 27, 1997 at 05:29:23PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Eivind Eklund: > In what way are release tags expensive? I've been thinking of using Because you modify every file in the repository which is a slow operation and that will generate big CTM (usually about 800-900 KB) files. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-hackers Sat Sep 27 10:01:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02085 for hackers-outgoing; Sat, 27 Sep 1997 10:01:26 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02051 for ; Sat, 27 Sep 1997 10:01:16 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id TAA20923 for ; Sat, 27 Sep 1997 19:01:41 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id TAA22326 for freebsd-hackers@FreeBSD.ORG; Sat, 27 Sep 1997 19:00:42 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id SAA07790; Sat, 27 Sep 1997 18:39:08 +0200 (CEST) Message-ID: <19970927183907.29093@keltia.freenix.fr> Date: Sat, 27 Sep 1997 18:39:07 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. References: <19970927104008.PZ43927@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84 In-Reply-To: <19970927104008.PZ43927@uriah.heep.sax.de>; from J Wunsch on Sat, Sep 27, 1997 at 10:40:08AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > Btw., it seems to be a bug in ncurses. ee correctly checks for an Our ncurses is rather ancient BTW. I dunno the exact status of Dickey's version (now at 4.1 I think) now that Eric Raymond asked him to stop developping it (or something like this) but we should be able to use a more modern one. Many FreeBSD users got problems with it when compiling Mutt (for example). PS: you can upgrade your Mutt now Jörg, the 0.84 (with some patches of course) runs fine. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-hackers Sat Sep 27 10:05:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02379 for hackers-outgoing; Sat, 27 Sep 1997 10:05:12 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA02372 for ; Sat, 27 Sep 1997 10:05:06 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 18014 invoked by uid 1001); 27 Sep 1997 17:05:01 +0000 (GMT) To: rgrimes@GndRsh.aac.dev.com Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Your message of "Sat, 27 Sep 1997 09:47:15 -0700 (PDT)" References: <199709271647.JAA20293@GndRsh.aac.dev.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Sep 1997 19:05:01 +0200 Message-ID: <18012.875379901@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Nope. A hub doesn't do anything with collisions - it just propagates > > them bit by bit. The NICs sense the collision. > > Better go think so more about that... it depends on the hub! Some hubs > that have partitioning ability will automagically partition out someone > who starts to transmit if the hub is sending data out that port, this > is called autopartitioning and is used to stop baligerant (sp) mau's > or Jabberers(sp). Sure - I agree it depends on the hub. But the basic task of the hub is to propagate everything bit by bit - including collisions. And if you buy a noname cheapie hub, it won't do much more than that. > If you want something that really tries to ``prevent'' this you want > a switch and not a hub, and you want full-duplex non-simplex NIC cards > in every box connected to that switch, and no I'm not just talking > about 100Base stuff here, it applies to both 10 and 100Base ethernet > over TP. Yup. But for normal, half-duplex Ethernet you *don't* want to prevent collisions :-) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Sep 27 10:06:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02487 for hackers-outgoing; Sat, 27 Sep 1997 10:06:39 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA02478 for ; Sat, 27 Sep 1997 10:06:34 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 18026 invoked by uid 1001); 27 Sep 1997 17:06:31 +0000 (GMT) To: dec@phoenix.its.rpi.edu Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Your message of "Sat, 27 Sep 1997 09:16:17 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Sep 1997 19:06:31 +0200 Message-ID: <18024.875379991@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Nope. A hub doesn't do anything with collisions - it just propagates > > them bit by bit. The NICs sense the collision. > > Technically this is not even a colission situation. Many new NICs and > Hubs (both must support it to work) support full-duplex 10BaseT, allowing > 20MBits/sec. I am not sure what happens when it gets into the hub and > needs to be propogated to other ports though *shrug*. If a "hub" supports full duplex then it is by definition a switch - at least in my language. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Sep 27 10:11:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02752 for hackers-outgoing; Sat, 27 Sep 1997 10:11:50 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02745 for ; Sat, 27 Sep 1997 10:11:47 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id NAA28053; Sat, 27 Sep 1997 13:11:28 -0400 (EDT) Date: Sun, 28 Sep 1997 01:11:58 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Eivind Eklund cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-Reply-To: <199709271529.RAA11811@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Eivind Eklund wrote: > > Yes, I tag and then I build from that tag after resyncronizing my > > local repository. > > > > Unfortunately, tags are expensive and you don't just lay them down > > for fun. > > In what way are release tags expensive? I'm not sure exactly what Jordan was referring to, but I know that every time the tree gets tagged, a huge ctm delta is generated. I think this would mean a lot of net traffic also for folks using cvsup. In that way, it's very expensive and time consuming. I've been thinking of using > tags to make a commit a single operation instead of a bunch of changes > just connected by the commit-log, and for storing meta-information for > merges. With this and some merge-related tags (for storing > meta-information) syncing RELENG_* and -current the way we want should > become quite a bit easier. Are the tags so expensive this would be > non-feasible? I thought they would be a comparatively cheap way of > storing minor amounts of meta-information. > > Eivind. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 27 10:14:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02888 for hackers-outgoing; Sat, 27 Sep 1997 10:14:45 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02880 for ; Sat, 27 Sep 1997 10:14:42 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id NAA17245 for ; Sat, 27 Sep 1997 13:19:52 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sat, 27 Sep 1997 13:19:52 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: workaround for NATd + CVSup? In-Reply-To: <199709271158.OAA10787@relay.ucb.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I guess this is an RTFM, but i got it, if you are running NATd for IP aliasing on a private IP network the option: -P - will have CVSup working for you. ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" On Sat, 27 Sep 1997, Ruslan Ermilov wrote: > Once Alfred Perlstein wrote: > > > > i'm running NATd so i can have more than one machine operating on only one > > IP address, but i think it is causing breakage with CVSup... > > > > does anyone know what ports and what type of traffic i have to have > > tunneled to the machine running cvsup? > > > > CVSup can operate in four modes: active, passive, multiplexed and SOCKS. > In your situation you can use either passive or multiplexed modes. > See man cvsup (-P option). > > -- > Ruslan A. Ermilov System Administrator > ru@ucb.crimea.ua United Commercial Bank > +380-652-247647 Simferopol, Crimea > 2426679 ICQ Network, UIN > From owner-freebsd-hackers Sat Sep 27 10:15:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02979 for hackers-outgoing; Sat, 27 Sep 1997 10:15:58 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02967 for ; Sat, 27 Sep 1997 10:15:41 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA12084; Sat, 27 Sep 1997 19:15:24 +0200 (MET DST) Message-ID: <19970927191524.23340@bitbox.follo.net> Date: Sat, 27 Sep 1997 19:15:24 +0200 From: Eivind Eklund To: Chuck Robey Cc: Eivind Eklund , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? References: <199709271529.RAA11811@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: ; from Chuck Robey on Sun, Sep 28, 1997 at 01:11:58AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 28, 1997 at 01:11:58AM -0400, Chuck Robey wrote: > On Sat, 27 Sep 1997, Eivind Eklund wrote: > > > > Yes, I tag and then I build from that tag after resyncronizing my > > > local repository. > > > > > > Unfortunately, tags are expensive and you don't just lay them down > > > for fun. > > > > In what way are release tags expensive? > > I'm not sure exactly what Jordan was referring to, but I know that every > time the tree gets tagged, a huge ctm delta is generated. I think this > would mean a lot of net traffic also for folks using cvsup. In that way, > it's very expensive and time consuming. This should be irrelevant for adding CVS tags for each commit, I believe. It will increase the ctm delta size a little, but the ctm deltas would still only refer to files that are modified anyway. (At least that was an expense I knew about - I'm just wondering if there is some hidden expense I _don't_ know about, like files with a huge number of tags being excedingly slow to work with, or somesuch.) Eivind. From owner-freebsd-hackers Sat Sep 27 10:27:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03452 for hackers-outgoing; Sat, 27 Sep 1997 10:27:32 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03447 for ; Sat, 27 Sep 1997 10:27:16 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id NAA29295; Sat, 27 Sep 1997 13:26:59 -0400 (EDT) Date: Sun, 28 Sep 1997 01:27:28 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Eivind Eklund cc: Eivind Eklund , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-Reply-To: <19970927191524.23340@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Eivind Eklund wrote: > On Sun, Sep 28, 1997 at 01:11:58AM -0400, Chuck Robey wrote: > > On Sat, 27 Sep 1997, Eivind Eklund wrote: > > > > > > Yes, I tag and then I build from that tag after resyncronizing my > > > > local repository. > > > > > > > > Unfortunately, tags are expensive and you don't just lay them down > > > > for fun. > > > > > > In what way are release tags expensive? > > > > I'm not sure exactly what Jordan was referring to, but I know that every > > time the tree gets tagged, a huge ctm delta is generated. I think this > > would mean a lot of net traffic also for folks using cvsup. In that way, > > it's very expensive and time consuming. > > This should be irrelevant for adding CVS tags for each commit, I > believe. It will increase the ctm delta size a little, but the ctm > deltas would still only refer to files that are modified anyway. (At > least that was an expense I knew about - I'm just wondering if there > is some hidden expense I _don't_ know about, like files with a huge > number of tags being excedingly slow to work with, or somesuch.) You were talking about tagging the entire tree, right? Every file gets visited, and a tag added. One operation for every file in the tree == expensive. I know that's what happens when a new release comes out; can't possibly miss such a thing. Can't possibly mistake it, just look back in the archives of ctm deltas for 1 megabyte+ deltas. Alternatively, look in your cvs achive's commitlogs for huge commit messages, although I think that Jordan's gotten some trick for doing that without the gigantic message going out. I'll have to ask him about that one, I'm curious. > > Eivind. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 27 10:48:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04308 for hackers-outgoing; Sat, 27 Sep 1997 10:48:21 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04297 for ; Sat, 27 Sep 1997 10:48:16 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA12207; Sat, 27 Sep 1997 19:48:09 +0200 (MET DST) Message-ID: <19970927194809.02902@bitbox.follo.net> Date: Sat, 27 Sep 1997 19:48:09 +0200 From: Eivind Eklund To: Chuck Robey Cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? References: <19970927191524.23340@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: ; from Chuck Robey on Sun, Sep 28, 1997 at 01:27:28AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 28, 1997 at 01:27:28AM -0400, Chuck Robey wrote: > On Sat, 27 Sep 1997, Eivind Eklund wrote: > > This should be irrelevant for adding CVS tags for each commit, I > > believe. It will increase the ctm delta size a little, but the ctm > > deltas would still only refer to files that are modified anyway. (At > > least that was an expense I knew about - I'm just wondering if there > > is some hidden expense I _don't_ know about, like files with a huge > > number of tags being excedingly slow to work with, or somesuch.) > > You were talking about tagging the entire tree, right? No. I was talking about adding tags to each commit to serialize them (making a single commit share a property that is easy to manipulate, instead of just sharing the commit message), and using tags to indicate how merges have been done, to simplify (more-or-less automate) later merges. Merges should be possible to make as easy as this: # Merge commit #1498 to the RELENG_2_2 branch cvs merge COMMIT1498 to RELENG_2_2 # Merge all new commits to ppp from HEAD to RELENG_2_2, as a single # commit cvs merge all from HEAD to RELENG_2_2 block # Merge all commits to ppp from HEAD to RELENG_2_2, as a series of # commits with the same log messages with prefix "MFC: " cvs merge all from HEAD to RELENG_2_2 serialized prefix "MFC: " # Merge all changes from the HEAD to the present directory (have to be # as a block) cvs merge all from HEAD to . I'm not certain all of this is feasible within the CVS "database structure" but I've been toying with the idea of implementing some of this based on meta-information in non-moving tags, with cvs merge replaced by an external cvsmerge script. If tags to the files you're modifying anyway are cheap, serializing the commits is something that could be started more or less right away. If it is expensive - well, then I need to find another solution, possibly abandoning CVS in the process. This would have good and bad sides; the worst one is that this is such a large project that I'd be much less likely to implement it ;-) Eivind. From owner-freebsd-hackers Sat Sep 27 11:25:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05853 for hackers-outgoing; Sat, 27 Sep 1997 11:25:25 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA05830 for ; Sat, 27 Sep 1997 11:25:15 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA13926 for hackers@freebsd.org; Sat, 27 Sep 1997 14:25:28 -0400 From: Bill Paul Message-Id: <199709271825.OAA13926@skynet.ctr.columbia.edu> Subject: Idea for a software licensing scheme To: hackers@freebsd.org Date: Sat, 27 Sep 1997 14:25:26 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm hoping some of the more mathematically astute out there can answer a question for me. A while ago, there was a discussion on -hackers about possibly creating a software licensing system for FreeBSD as an incentive to commercial software vendors to port their code. Well, the Diffie-Hellman patent expired earlier this month, and that started me thinking about a way to possibly use D-H key pairs as part of a licensing scheme. I _think_ I've come up with a viable way to do this and have even written some code to show that it works. My main goal is to come up with a scheme that makes it next to impossible for an 'attacker' to generate his own license codes even knowing the algorithms and some of the values involved. But I'm rotten at math and I'm uncertain that my scheme is as foolproof as I think it is. Here's how it works. First of all, consider two parties that want to participate in D-H key-exchange. The first thing the two parties have to do is agree on two special values. The first value, p, is some large prime number. The second value, g, is some number larger than 2 and less than p. The value p is called the modulus and g is the root. Now each party independently chooses a number, X, to be their secret key. Each party keeps his secret key to himself and never reveals it to the anyone. We'll call the first party's secret key X1 and the second party's secret key X2. Finally, party one and party two derive public keys (Y1 and Y2) from their secret keys (X1 and X2) using the following computations: Y1 = g ^ X1 % p Y2 = g ^ X2 % p Now party one and party two can exchange their public keys (Y1 and Y2). The trick is that Y1 and Y2 are related to their corresponding secret keys X1 and X2 in such a way that the following holds true: s = Y1 ^ X2 % p s = Y2 ^ X1 % p In other words, each party is now able to compute a session key, s, which is essentially a shared secret. The magic is that both parties can arrive at the same shared secret value without having to exchange it over a possibly unsecured communications channel where it could be intercepted. For a third party to learn this shared secret, they would have to compute the other two parties' secret keys, which is very hard to do even if you know, p, g, and a set of public keys. Okay, that's how D-H works. Now here's my idea. Let's say I'm a software vendor. I choose two values, p and g. I keep 'g' a secret and never reveal it to anyone. Now let's say I have an application, 'a', that I want to protect. I choose a secret key for the application called Xa. This key can be anything really; in my scheme I use an MD5 hash of the program name, vendor name, program version, and some random string. From the applications' secret key, Xa, I derive the application's secret key, Ya using the following computation: Ya = g ^ Xa % p I then embed the values for Xa, Ya and the modulus, p, into the application. Now I want to make a license authorization file for this application so that some customer of mine can run it. The file contains certain pertinent information: name of the feature I want to activate, number of concurrent users, expiration date, hostid, and so forth. All of this information is hashed together to generate a value which becomes what I call the license secret key, Xl. (Again, I used an MD5 hash for this.) The authorization passcode is actually the license public key Yl, which is generated like this: Yl = g ^ Xl % p I then include Yl in the license file as the activation code and ship the whole thing off to the customer. Now for the verification part. When the application program runs, the license checking code reads the license file and regenerates the license secret key, Xl, by computing the MD5 hash of all the license information (feature name, number of users, etc...). It also reads the authorization passcode and considers that to be Yl. So now the code has 5 values: Xa, Ya, Xl, Yl and p. It performs the following computations: s1 = Ya ^ Xl % p s2 = Yl ^ Xa % p This yields two 'session keys,' s1 and s2. If s1 == s2, then the code considers the license to be valid and the program runs, otherwise it signals an error and bombs. The logic is this: the only way s1 and s2 can come out being the same is if the license public key, Yl, and the application public key, Ya, were both generated using the same Diffie-Hellman parameters, g and p. But I, the vendor, keep g a secret. (Unfortunately, you can't keep p a secret since the application needs it to compute the session keys.) This means that only I, the vendor, can derive a license public key (Yl) that will satisfy the equality. Now comes the part I'm not sure about. In theory, it is possible for an 'attacker' to obtain values for p, Xl and Yl. My question is: can the attacker use these values to compute g? In other words, is it very hard for someone to calculate g even knowing p, Xl and Yl, or is there some mathematical shortcut that I'm just too stupid to see? If an attacker can calculate g without too much trouble, then the whole scheme falls apart because the attacker will be able to generate his own authorization passcode for any license parameters he chooses. You might be wondering what there is to gain by using a system like this. The answer is that it avoids (I hope!) a problem present in certain other schemes that use what I call 'checksumming' to verify license passcodes. With certain kinds of license management software, the passcode is essentially a hash or checksum of the other information in the file which has been encryped using keys that only the vendor knows. The problem is that in order for the application to verify that the license is valid, it must contain the same keys. To verify the passcode, the license software embedded in the application will read the information from the license file, generate its own hash value and encrypt it using its own copies of the encryption keys. The result is its own version of the authorization passcode which it can check against the passcode in the license file. If the code in the file does not match the code computed by the application, the program bombs. The problem is that the entire security of the scheme relies on the assumption that nobody will be able to trick the application into revealing the code that it has computed internally. This is a big mistake. Say for example than an attacker changes the expiration date in his license file. The application will read the information from the file, compute what it believes should be the correct authorization code and then compare that the code supplied in the license file. The values won't match of course, but supposing the attacker is able to extract the computed (and correct!) authorization code from the program's address space. Now all he has to do is put this code in the license file in place of the old one, and presto! he has a perfectly valid license that expires whenever he wants. The irony here is that licensing software based on this kind of scheme may include all sorts of special hash algorithms, strong encryption, and any number of keys, yet the whole mess can be easily defeated without knowing anything about cryptography. In effect, you use the vendor's own software against him. With my scheme, you eliminate this vulnerability by giving the application enough information to verify that the authorization passcode is genuine, but not enough for it to generate passcodes of its own. Of course, any licensing software can be defeated by patching the application executable, and my scheme does nothing to defend against that. But that kind of attack requires a fair amount of OS-dependent and CPU-dependent knowledge which the ovwewhelming number of computer users in the world today are unlikely to have. Also, consider what happens when a vendor makes their software available for multuple platforms and uses the same licensing software for each one. This makes it convenient for the vendor since he only has to generate one license file, and the customer can use it on whatever platform he chooses. It also makes it very convenient for a software pirate: rather than have to generate patched binaries for every platform, all he has to do is coerce the application into generating a magic unlimited-use license on one platform, and he has automatically defeated the licensing scheme for all platforms in one stroke. Anyway, the question stands: does my idea have merit, or should I make a reservation for the conical hat. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Sat Sep 27 12:32:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08606 for hackers-outgoing; Sat, 27 Sep 1997 12:32:04 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08601 for ; Sat, 27 Sep 1997 12:32:01 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA29928; Sat, 27 Sep 1997 13:31:59 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA27321; Sat, 27 Sep 1997 13:31:57 -0600 (MDT) Date: Sat, 27 Sep 1997 13:31:57 -0600 (MDT) Message-Id: <199709271931.NAA27321@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: References: <19970927191524.23340@bitbox.follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Alternatively, look in > your cvs achive's commitlogs for huge commit messages, although I think > that Jordan's gotten some trick for doing that without the gigantic > message going out. CVS 'tagging' doesn't cause commit messages. Nate From owner-freebsd-hackers Sat Sep 27 12:32:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08627 for hackers-outgoing; Sat, 27 Sep 1997 12:32:13 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08622 for ; Sat, 27 Sep 1997 12:32:10 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA29923; Sat, 27 Sep 1997 13:30:55 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA27312; Sat, 27 Sep 1997 13:30:50 -0600 (MDT) Date: Sat, 27 Sep 1997 13:30:50 -0600 (MDT) Message-Id: <199709271930.NAA27312@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Chuck Robey , Eivind Eklund , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: <19970927191524.23340@bitbox.follo.net> References: <199709271529.RAA11811@bitbox.follo.net> <19970927191524.23340@bitbox.follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > In what way are release tags expensive? > > > > I'm not sure exactly what Jordan was referring to, but I know that every > > time the tree gets tagged, a huge ctm delta is generated. I think this > > would mean a lot of net traffic also for folks using cvsup. > This should be irrelevant for adding CVS tags for each commit, I > believe. It will increase the ctm delta size a little, but the ctm > deltas would still only refer to files that are modified anyway. All files are modified when tags are put down, so it means CTM deltas and CVS deltas are rather large, although the change for each file is rather small. Nate From owner-freebsd-hackers Sat Sep 27 13:06:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10538 for hackers-outgoing; Sat, 27 Sep 1997 13:06:08 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10533 for ; Sat, 27 Sep 1997 13:06:04 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA12623; Sat, 27 Sep 1997 22:05:51 +0200 (MET DST) Message-ID: <19970927220550.60658@bitbox.follo.net> Date: Sat, 27 Sep 1997 22:05:50 +0200 From: Eivind Eklund To: Nate Williams Cc: Chuck Robey , Eivind Eklund , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? References: <199709271529.RAA11811@bitbox.follo.net> <19970927191524.23340@bitbox.follo.net> <199709271930.NAA27312@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199709271930.NAA27312@rocky.mt.sri.com>; from Nate Williams on Sat, Sep 27, 1997 at 01:30:50PM -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 01:30:50PM -0600, Nate Williams wrote: > > > > In what way are release tags expensive? > > > > > > I'm not sure exactly what Jordan was referring to, but I know that every > > > time the tree gets tagged, a huge ctm delta is generated. I think this > > > would mean a lot of net traffic also for folks using cvsup. > > > This should be irrelevant for adding CVS tags for each commit, I > > believe. It will increase the ctm delta size a little, but the ctm > > deltas would still only refer to files that are modified anyway. > > All files are modified when tags are put down, so it means CTM deltas > and CVS deltas are rather large, although the change for each file is > rather small. This only happens if all files are tagged, AFAIK? I was referring to adding tags to those files that actually are modified, to tie each commit and each merge together so it can be viewed as a single change at a later point in time, instead of being viewed as one change for each file, with no usable way to automatically find out what other changes was done at the same time. This do not require modifying all untouched files unless I've totally misunderstood the way RCS tags work. Eivind. From owner-freebsd-hackers Sat Sep 27 13:19:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11268 for hackers-outgoing; Sat, 27 Sep 1997 13:19:11 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA11259 for ; Sat, 27 Sep 1997 13:19:08 -0700 (PDT) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id PAA21105; Sat, 27 Sep 1997 15:18:36 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199709271930.NAA27312@rocky.mt.sri.com> References: <19970927191524.23340@bitbox.follo.net> <199709271529.RAA11811@bitbox.follo.net> <19970927191524.23340@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Sep 1997 15:17:56 -0500 To: Nate Williams From: Richard Wackerbarth Subject: Re: How do I check out a snapshot? Cc: Eivind Eklund , Chuck Robey , Eivind Eklund , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 2:30 PM -0500 9/27/97, Nate Williams wrote: >> > > In what way are release tags expensive? >> > >> > I'm not sure exactly what Jordan was referring to, but I know that every >> > time the tree gets tagged, a huge ctm delta is generated. I think this >> > would mean a lot of net traffic also for folks using cvsup. > >> This should be irrelevant for adding CVS tags for each commit, I >> believe. It will increase the ctm delta size a little, but the ctm >> deltas would still only refer to files that are modified anyway. > >All files are modified when tags are put down, so it means CTM deltas >and CVS deltas are rather large, although the change for each file is >rather small. A suggestion to consider. -- Suppose that the snapshots are always generated by using a CVS checkout that never references the head directly. In other words, in a manner that others can reproduce at a later time. (For example, a checkout by date, using yesterday's date) Now this "key" can be placed in a file within the tree where interested parties can retrieve it. Since the key is only a line or two at most, and only affects one file, it will not impose the burden on CTM and CVSup that a full scale CVS Tag would create. Richard Wackerbarth From owner-freebsd-hackers Sat Sep 27 14:27:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13631 for hackers-outgoing; Sat, 27 Sep 1997 14:27:10 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13626 for ; Sat, 27 Sep 1997 14:27:08 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA11524; Sat, 27 Sep 1997 14:27:03 -0700 (MST) From: Terry Lambert Message-Id: <199709272127.OAA11524@usr08.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 27 Sep 1997 21:27:02 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970927143934.ZN26834@uriah.heep.sax.de> from "J Wunsch" at Sep 27, 97 02:39:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The easy answer to this is that there isn't a Motif-based listbox > > setup for the nameserver code, where you just fill in the names you > > want, and it does the rest. > > > > The less easy answer is "it's hard enough to set up that it's not > > worth doing for most people". > > Writing a Motif-based program would take a tremenduous amount of time. If you make it grammar-based, you write it once, and it works for a crudload of command line configurators that know how to be run over pipes. Like disk partition tools, install tools, etc.. So you can pretty much amortize the cost over a hell of a lot of code. > Why do it if the basic nameserver setup takes about 10 minutes? (No, > not the caching-only server, this one only takes a couple of minutes.) Each. Time. > I've seen the listbox-style cr*p that ships with some M$ operating > system. The listboxes look nice, are terrible to use Speak for yourself. 99.99% of the computer users in the world prefer that type of interface -- which is why they are MS users instead of UNIX users. UNIX users are, as a class, intellectual elitists who don't undertand that the average I.Q. is 100 because that is how a 100 I.Q. is defined. And as a class, they are unprepared to make the necessary allowances. There's a good reason a moron can run Microsoft OS's: so that that morons won't be too intimidated to buy them. > (it's a pain in the rear to add all the same standard MX records to > each host using this kind of `editor'), This is why you connect to www.microsoft.com, go to the download area, and pull down the configuration template mechanism, if you're an IS person who needs to set up a lot of machines. For non-MX (and other ancillary network configuration) type stuff, you use DHCP *OR* you use a non-TCP/IP protocol to avoid name-number data translation altogether. Normal mortals don't like TCP/IP because it bears no resemblance to reality. I don't have to name my car to remember where I parked it. > but the vendor of that cr*p didn't get the underlying nameserver > working correctly at all. (For example, the server never hands out > authoritative answers, even if it is for sure an authoritative server.) This may be intentional laxity. In their opinion, you are supposed to buy an NT server and configure WINS naming instead of DNS. > And finally, using the shicky-micky listbox interface usually screws > the nameserver setup at all. But it's easy. It's a hell of a lot easier than running an editor and shelling out to a man page every five minutes, or worse, shelling out money for an O'Reilly book, which is made necessary by all the bogus complexity associated with the task, and trying to balance the thing on your knees while typing in secret code words. For something designed by a bunch of bonifide computer scientists, you'd think they would be able to grasp the concept of putting configuration databases in third normal form. 8-|. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Sep 27 14:29:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13736 for hackers-outgoing; Sat, 27 Sep 1997 14:29:54 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13730 for ; Sat, 27 Sep 1997 14:29:52 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA11592; Sat, 27 Sep 1997 14:29:41 -0700 (MST) From: Terry Lambert Message-Id: <199709272129.OAA11592@usr08.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 27 Sep 1997 21:29:41 +0000 (GMT) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19970927144133.UH24533@uriah.heep.sax.de> from "J Wunsch" at Sep 27, 97 02:41:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Of course, you should feel free to suggest to us any soloution which > > does not require us to run named to implement. And not feel free to > > suggest running named. > > It doesn't require named to run. I have reconstructed your setup, and > proven that my named doesn't get any request if the setup is done > correctly. As i've mentioned, the only pitfall was specifying > localhost without adding the local domain, and with 127.1 instead of > 127.0.0.1 in /etc/hosts. I didn't see this. Perhaps this was the interval during which primenet had munged my MX record. I will give it a try. Technically 127.1 and 127.0.0.1 are synonymous; one would think the code should know this... 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-hackers Sat Sep 27 14:37:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14194 for hackers-outgoing; Sat, 27 Sep 1997 14:37:47 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA14186 for ; Sat, 27 Sep 1997 14:37:27 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id RAA10946; Sat, 27 Sep 1997 17:36:54 -0400 (EDT) Date: Sun, 28 Sep 1997 05:37:22 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Richard Wackerbarth cc: Nate Williams , Eivind Eklund , Eivind Eklund , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Richard Wackerbarth wrote: > At 2:30 PM -0500 9/27/97, Nate Williams wrote: > >> > > In what way are release tags expensive? > >> > > >> > I'm not sure exactly what Jordan was referring to, but I know that every > >> > time the tree gets tagged, a huge ctm delta is generated. I think this > >> > would mean a lot of net traffic also for folks using cvsup. > > > >> This should be irrelevant for adding CVS tags for each commit, I > >> believe. It will increase the ctm delta size a little, but the ctm > >> deltas would still only refer to files that are modified anyway. > > > >All files are modified when tags are put down, so it means CTM deltas > >and CVS deltas are rather large, although the change for each file is > >rather small. > > A suggestion to consider. -- > > Suppose that the snapshots are always generated by using a CVS checkout > that never references the head directly. In other words, in a manner > that others can reproduce at a later time. (For example, a checkout > by date, using yesterday's date) > > Now this "key" can be placed in a file within the tree where interested > parties can retrieve it. Since the key is only a line or two at most, > and only affects one file, it will not impose the burden on CTM and > CVSup that a full scale CVS Tag would create. Hmm. It not only saves a lot of net traffic, it makes it easily reproducible. Since every tag _also_ increases the size of the cvs archive, this is a win-win-win. Hey, what do we pay you, Richard? Put yourself down for a 10% increase! :-> > > Richard Wackerbarth > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 27 15:18:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15703 for hackers-outgoing; Sat, 27 Sep 1997 15:18:07 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15698 for ; Sat, 27 Sep 1997 15:18:02 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA13667; Sat, 27 Sep 1997 15:17:53 -0700 (MST) From: Terry Lambert Message-Id: <199709272217.PAA13667@usr08.primenet.com> Subject: Re: ee taking up weird cpu amount. To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 27 Sep 1997 22:17:52 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970927145007.HB02894@uriah.heep.sax.de> from "J Wunsch" at Sep 27, 97 02:50:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I've seen this problem on Illtrix on an old Vax2000 as well. To what > > > shell are your claims above related? > > > > None of them, of course. > > Huh? ``To what shell?'' -- ``None of them.'' Am i in the wrong > movie? > > > This has only to do with ourder of revoke() > > processing when revoke() is a result of on-to-off-DCD transition. > > The foreground process group gets properly signalled. I've been using > a FreeBSD-based ISP for long enough to know that it works. Then under what circumstances is it ever possible to get a process buzzing in a "read returns 0 bytes" loop? If your claim is true, that it works flawlessly, then the process will get a SIGHUP instead because it's in the foreground. And the error he was reporting didn't happen. So he must be hallucinating. ;-). > > > ksh has a weird (mis-)feature to lead all its kids to death when it > > > dies itself. > > > > This, of course, has to do with ksh's method of backgrounding a > > process. > > No. It hasn't. ksh properly shuffles each job into a separate > process group (unlike the non-jobcontrol prehistoric /bin/sh). It > *purposely* kills all its children before dying. That's why you can > achieve the csh's default behaviour by logging out with ``kill -9 $$'' > -- the background process groups will then behave like they do in csh. Uh... how does this differ from what I said? > > The Bourne shell specifically distinguished children this way via > > the "nohup" mechansim. The csh implies "nohup" for all subshells, > > No. The children are still sensitive to a SIGHUP if you send it to > them. The shell doesn't send it to them iff they are _running in > background_ when the shell exits. (Stopped jobs will be reaped > nevertheless.) This is why the manual says that running background > jobs are ``effectively nohuped''. They are not really nohuped. Which manual are you reading? DESCRIPTION The nohup utility invokes command with its arguments and at this time sets the signal SIGHUP to be ignored. The signal SIGQUIT may also be set to be ignored. 8-). > > > Btw., nvi doesn't suffer from this behaviour. Ignoring an error > > > return from the input device is always an error on the side of the > > > program in question. > > > > An error return is impossible in the normal signal propagation case, > > That's no reason for curses to never assume an error could not happen. Yes, it is. It's on the order of doing a select on an fd attached to a disk file to "see if it's readable". The answer is "YES" before you ask the question; why ask an inane question? Like "I'm not catching SIGHUP, so the default behaviour of terminating the program when the tty is revoked and I'm sent SIGHUP is in effect, so should I ask if that read from the tty failed because of EOF from the tty being revoked?" The answer is "NO" before you ask the question. > Errors can happen for more reasons. Errors are to be caught. "Never check for an error that you can't handle" -- Donald Knuth Though I admit, he probably meant that you should handle them. ;-). > Anything else is sloppy programming. > > There used to be a Usenix paper titled: > > Can't happen Then don't check for the condition. If you don't have a test for it, it truly cannot hit the code bounded by the test. > > or > > /* NOTREACHED */ This is a comment to make LINT shut up. How often does exit() return to the caller in your programs? 8-). > > or > > Real Programs dump Core. They do, and we look at the traceback and correct the code. And we catch this in our testing before it ever goes out the door, because our test cases are machine generated code coverage tests based on doing branch path analysis, because we know one support call will cost us most of our profit, and we're not one of those companies who erroneously looks at support as a profit center and uses 1-900 numbers instead of 1-800 numbers. Because we learn by example, and we saw Word Perfect turf it, and we're not morons who believe that "this time, when I let go of the brick, it won't fall". But that's irrelevent here... 8-). Here are the possible returns from read(2), and their real meaning in the current context: -1 You screwed up. Your code is broken. Look at errno in case you are too stupid to figure out how it's broken without someone holding your hand. 0 You screwed up. You are trapping SIGHUP and then not doing anything about it. You should probably not trap it, and the default behaviour will abort your program like most normal programs. To teach you to use better coding practices in the future, I'm going to buzz loop here forever , sucking CPU time until you notice me. >0 Hey, what do you know, it's not an error! Here are the possible errors from read(2), and their real meaning in the current context: EBADF Code needs to be corrected to be proactive in its decision to use a particular fd. Fix your code. EFAULT Code needs to allocate buffers before it uses them. Fix your code. EIO Terminals aren't file systems. The tty code should already be aware of this fact. Fix the stupid tty code. EINTR Some idiot changed the default BSD system call restart behaviour after signals are received. Needs to be changed back, and only set before specific calls, and then only when you are too frigging anal about anything that mildly resembles "goto" to use setjmp() before the call and longjmp() in the signal handler, like God intended. Fix the stupid signal code. EINVAL Hello! McFly! You're passing in bogus descriptors! Go back and read the system call manual again; you apparently don't grasp the concept of "you have to open it before you can read it". Fix your code. EAGAIN You are using non-blocking I/O, probably because you are too stupid to figure out the arguments to the select() system call, or too lazy to write an aioread/aiowrite/aiocancel and/or async call gate code to do it the right way. Fix your code. I don't see one case where the error return needs to be checked in a working program in this particular usage of read(2)... unless vi can have it's input redirected from a file in normal usage (EIO)? Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Sep 27 15:21:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15870 for hackers-outgoing; Sat, 27 Sep 1997 15:21:17 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA15862 for ; Sat, 27 Sep 1997 15:21:13 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA26195 for freebsd-hackers@FreeBSD.ORG; Sun, 28 Sep 1997 00:21:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA00589; Sun, 28 Sep 1997 00:08:38 +0200 (MET DST) Message-ID: <19970928000838.EW57067@uriah.heep.sax.de> Date: Sun, 28 Sep 1997 00:08:38 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. References: <19970927104008.PZ43927@uriah.heep.sax.de> <19970927183907.29093@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970927183907.29093@keltia.freenix.fr>; from Ollivier Robert on Sep 27, 1997 18:39:07 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > Many FreeBSD users got problems with it when compiling Mutt (for example). Is the resize bug fixed now? > PS: you can upgrade your Mutt now Jörg, the 0.84 (with some patches of > course) runs fine. Maybe. I'm too lazy to change my .muttrc. :) Never change a running system... -- 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-hackers Sat Sep 27 15:25:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16064 for hackers-outgoing; Sat, 27 Sep 1997 15:25:07 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16053 for ; Sat, 27 Sep 1997 15:25:01 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA13981; Sat, 27 Sep 1997 15:24:35 -0700 (MST) From: Terry Lambert Message-Id: <199709272224.PAA13981@usr08.primenet.com> Subject: Re: More ATAPI Zip news (will he ever shut up?) To: dan@dpcsys.com (Dan Busarow) Date: Sat, 27 Sep 1997 22:24:35 +0000 (GMT) Cc: mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: from "Dan Busarow" at Sep 27, 97 09:24:49 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Arrrrr... Anyone have a good source for small IDE hard drives? Why? Aren't you already saved by not using SCSI? From what I'm told, IDE drives grow on trees and fall freely, as mana from heaven... }B-). 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-hackers Sat Sep 27 15:26:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16165 for hackers-outgoing; Sat, 27 Sep 1997 15:26:50 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16157 for ; Sat, 27 Sep 1997 15:26:47 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA14081; Sat, 27 Sep 1997 15:26:38 -0700 (MST) From: Terry Lambert Message-Id: <199709272226.PAA14081@usr08.primenet.com> Subject: Re: ee taking up weird cpu amount. To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sat, 27 Sep 1997 22:26:37 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970927183907.29093@keltia.freenix.fr> from "Ollivier Robert" at Sep 27, 97 06:39:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Many FreeBSD users got problems with it when compiling Mutt (for example). > > PS: you can upgrade your Mutt now Jörg, the 0.84 (with some patches of > course) runs fine. But, apparently from your description, traps SIGHUP and ignores it so it can (also apparently) buzz forever on an fd for a revoked tty. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Sep 27 15:28:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16292 for hackers-outgoing; Sat, 27 Sep 1997 15:28:43 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16272; Sat, 27 Sep 1997 15:28:36 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA14163; Sat, 27 Sep 1997 15:28:24 -0700 (MST) From: Terry Lambert Message-Id: <199709272228.PAA14163@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 27 Sep 1997 22:28:24 +0000 (GMT) Cc: sthaug@nethelp.no, tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709271647.JAA20293@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 27, 97 09:47:15 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If you want something that really tries to ``prevent'' this you want > a switch and not a hub, and you want full-duplex non-simplex NIC cards > in every box connected to that switch, and no I'm not just talking > about 100Base stuff here, it applies to both 10 and 100Base ethernet > over TP. While you are in the process emptying your wallet into a fire, you may want to consider buying good cards instead, and avoiding the problem altogether... 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-hackers Sat Sep 27 15:31:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16495 for hackers-outgoing; Sat, 27 Sep 1997 15:31:16 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16490 for ; Sat, 27 Sep 1997 15:31:12 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id QAA01063; Sat, 27 Sep 1997 16:30:34 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA27837; Sat, 27 Sep 1997 16:30:30 -0600 (MDT) Date: Sat, 27 Sep 1997 16:30:30 -0600 (MDT) Message-Id: <199709272230.QAA27837@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Nate Williams , Chuck Robey , Eivind Eklund , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: <19970927220550.60658@bitbox.follo.net> References: <199709271529.RAA11811@bitbox.follo.net> <19970927191524.23340@bitbox.follo.net> <199709271930.NAA27312@rocky.mt.sri.com> <19970927220550.60658@bitbox.follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > In what way are release tags expensive? > > > > > > > > I'm not sure exactly what Jordan was referring to, but I know that every > > > > time the tree gets tagged, a huge ctm delta is generated. I think this > > > > would mean a lot of net traffic also for folks using cvsup. > > All files are modified when tags are put down, so it means CTM deltas > > and CVS deltas are rather large, although the change for each file is > > rather small. > > This only happens if all files are tagged, AFAIK? Yes. > I was referring to > adding tags to those files that actually are modified, to tie each > commit and each merge together so it can be viewed as a single change > at a later point in time, instead of being viewed as one change for > each file, with no usable way to automatically find out what other > changes was done at the same time. Well, this is supposed to be how it's done, but CVS doesn't keep track of a single 'commit' in this manner. Other VC software does (such as P3). > This do not require modifying all > untouched files unless I've totally misunderstood the way RCS tags work. But, it's the way CVS works. And, forcing people to install X different versions of the software (where A is the base revision, and you need to apply a number of 'delta' revisions to take you up to each SNAP/RELEASE') is not a workable solution either. Nate From owner-freebsd-hackers Sat Sep 27 15:34:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16686 for hackers-outgoing; Sat, 27 Sep 1997 15:34:27 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16678 for ; Sat, 27 Sep 1997 15:34:19 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id QAA01096; Sat, 27 Sep 1997 16:33:49 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA27878; Sat, 27 Sep 1997 16:33:46 -0600 (MDT) Date: Sat, 27 Sep 1997 16:33:46 -0600 (MDT) Message-Id: <199709272233.QAA27878@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Richard Wackerbarth Cc: Nate Williams , Eivind Eklund , Chuck Robey , Eivind Eklund , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: References: <19970927191524.23340@bitbox.follo.net> <199709271529.RAA11811@bitbox.follo.net> <199709271930.NAA27312@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >All files are modified when tags are put down, so it means CTM deltas > >and CVS deltas are rather large, although the change for each file is > >rather small. > > A suggestion to consider. -- > > Suppose that the snapshots are always generated by using a CVS checkout > that never references the head directly. In other words, in a manner > that others can reproduce at a later time. (For example, a checkout > by date, using yesterday's date) Except that means lots more work for the release engineer. The RE has enough problems just making a release, making sure that the code is 'synchronized' to a certain date would make it that much harder. I think it would be 'easier' to simply tag the tree. Nate From owner-freebsd-hackers Sat Sep 27 15:34:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16755 for hackers-outgoing; Sat, 27 Sep 1997 15:34:40 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16735 for ; Sat, 27 Sep 1997 15:34:34 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA14330; Sat, 27 Sep 1997 15:34:19 -0700 (MST) From: Terry Lambert Message-Id: <199709272234.PAA14330@usr08.primenet.com> Subject: Re: How do I check out a snapshot? To: perhaps@yes.no (Eivind Eklund) Date: Sat, 27 Sep 1997 22:34:18 +0000 (GMT) Cc: chuckr@glue.umd.edu, jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <19970927194809.02902@bitbox.follo.net> from "Eivind Eklund" at Sep 27, 97 07:48:09 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm not certain all of this is feasible within the CVS "database > structure" but I've been toying with the idea of implementing some of > this based on meta-information in non-moving tags, with cvs merge > replaced by an external cvsmerge script. If tags to the files you're > modifying anyway are cheap, serializing the commits is something that > could be started more or less right away. If it is expensive - well, > then I need to find another solution, possibly abandoning CVS in the > process. This would have good and bad sides; the worst one is that > this is such a large project that I'd be much less likely to implement > it ;-) For a maybe smaller project while you are in the external scripting for CVS mood, it would be wonderful if you could write something to "change history"... basically, move sections of the source tree around without ending up with attic files all over. The big pain here is correlating makefile changes so the new "old" code will still be able to build historically correct releases. Probably, there should be "path from repository root" information in the files so different revisions check out to different locations... 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-hackers Sat Sep 27 15:40:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17099 for hackers-outgoing; Sat, 27 Sep 1997 15:40:39 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA17091 for ; Sat, 27 Sep 1997 15:40:33 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA26297 for freebsd-hackers@FreeBSD.ORG; Sun, 28 Sep 1997 00:40:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA00665; Sun, 28 Sep 1997 00:24:50 +0200 (MET DST) Message-ID: <19970928002450.TG36648@uriah.heep.sax.de> Date: Sun, 28 Sep 1997 00:24:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. References: <19970927145007.HB02894@uriah.heep.sax.de> <199709272217.PAA13667@usr08.primenet.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709272217.PAA13667@usr08.primenet.com>; from Terry Lambert on Sep 27, 1997 22:17:52 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > The foreground process group gets properly signalled. I've been using > > a FreeBSD-based ISP for long enough to know that it works. > > Then under what circumstances is it ever possible to get a process > buzzing in a "read returns 0 bytes" loop? The process was in the background, thus in a different process group. > > This is why the manual says that running background > > jobs are ``effectively nohuped''. They are not really nohuped. > > Which manual are you reading? The csh manual. -- 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-hackers Sat Sep 27 15:44:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17292 for hackers-outgoing; Sat, 27 Sep 1997 15:44:00 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17282 for ; Sat, 27 Sep 1997 15:43:53 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id SAA14325; Sat, 27 Sep 1997 18:43:10 -0400 (EDT) Date: Sun, 28 Sep 1997 06:43:38 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Nate Williams cc: Richard Wackerbarth , Eivind Eklund , Eivind Eklund , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: <199709272233.QAA27878@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Nate Williams wrote: > > >All files are modified when tags are put down, so it means CTM deltas > > >and CVS deltas are rather large, although the change for each file is > > >rather small. > > > > A suggestion to consider. -- > > > > Suppose that the snapshots are always generated by using a CVS checkout > > that never references the head directly. In other words, in a manner > > that others can reproduce at a later time. (For example, a checkout > > by date, using yesterday's date) > > Except that means lots more work for the release engineer. The RE has > enough problems just making a release, making sure that the code is > 'synchronized' to a certain date would make it that much harder. I > think it would be 'easier' to simply tag the tree. I think you mistake his intent, Nate. I think he meant it this way. The RE updates his tree, writes down the date/time that it's updated to. He then builds/tests it. If it's successful, he commits to a single file that keeps track of release date/times that date time, and uses that date/time later, if he wants to get another copy of a tree at that time. The RE wouldn't be trying to hit a particular date/time, he'd just keep track of his attempts, and log the successful ones. Everyone else would read that file, and if they wanted a tree at the date indicated, use cvs to get it. No tagging involved, and the exact sources would be easily available anyhow. > > > > Nate > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 27 15:48:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17656 for hackers-outgoing; Sat, 27 Sep 1997 15:48:27 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17633 for ; Sat, 27 Sep 1997 15:48:16 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id QAA01188; Sat, 27 Sep 1997 16:48:00 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA28003; Sat, 27 Sep 1997 16:47:59 -0600 (MDT) Date: Sat, 27 Sep 1997 16:47:59 -0600 (MDT) Message-Id: <199709272247.QAA28003@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: Nate Williams , Richard Wackerbarth , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: References: <199709272233.QAA27878@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > > > Suppose that the snapshots are always generated by using a CVS checkout > > > that never references the head directly. In other words, in a manner > > > that others can reproduce at a later time. (For example, a checkout > > > by date, using yesterday's date) > > > > Except that means lots more work for the release engineer. The RE has > > enough problems just making a release, making sure that the code is > > 'synchronized' to a certain date would make it that much harder. I > > think it would be 'easier' to simply tag the tree. > > I think you mistake his intent, Nate. I think he meant it this way. The > RE updates his tree, writes down the date/time that it's updated to. But, the tree isn't exactly in sync. with the 'real' CVS tree, so the code may not be exactly the same. With 'real' releases, the actual CVS tree is locked down by the RE, so his tree will be the same, since no-one is allowed to modify it. This isn't the case with SNAPS. So, the time/date he uses in his private tree may have other changes that occur when people commit code to the 'real' tree. The whole FreeBSD process is a multi-threaded/SMP kind of thing, so you gotta think about race conditions and all those other OS kinds of things. :) Nate From owner-freebsd-hackers Sat Sep 27 15:55:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18220 for hackers-outgoing; Sat, 27 Sep 1997 15:55:23 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18215 for ; Sat, 27 Sep 1997 15:55:16 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id PAA13668; Sat, 27 Sep 1997 15:54:42 -0700 (MST) From: Terry Lambert Message-Id: <199709272254.PAA13668@usr03.primenet.com> Subject: Re: How do I check out a snapshot? To: eivind@bitbox.follo.net (Eivind Eklund) Date: Sat, 27 Sep 1997 22:54:41 +0000 (GMT) Cc: nate@mt.sri.com, chuckr@glue.umd.edu, perhaps@yes.no, jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <19970927220550.60658@bitbox.follo.net> from "Eivind Eklund" at Sep 27, 97 10:05:50 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This only happens if all files are tagged, AFAIK? I was referring to > adding tags to those files that actually are modified, to tie each > commit and each merge together so it can be viewed as a single change > at a later point in time, instead of being viewed as one change for > each file, with no usable way to automatically find out what other > changes was done at the same time. This do not require modifying all > untouched files unless I've totally misunderstood the way RCS tags work. Plus you could have a change comment to go with the tag. And you could put it all in "CVS unlock" after you are done with your writer lock. Just like we did at Novell with CVS starting in 1993. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Sep 27 16:03:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA18683 for hackers-outgoing; Sat, 27 Sep 1997 16:03:58 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA18672 for ; Sat, 27 Sep 1997 16:03:48 -0700 (PDT) Received: from argus.tfs.net (node25.tfs.net [207.2.220.25]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id RAA24104; Sat, 27 Sep 1997 17:02:12 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id SAA01306; Sat, 27 Sep 1997 18:03:42 -0500 (CDT) From: Jim Bryant Message-Id: <199709272303.SAA01306@argus.tfs.net> Subject: Re: More ATAPI Zip news (will he ever shut up?) In-Reply-To: <199709272224.PAA13981@usr08.primenet.com> from Terry Lambert at "Sep 27, 97 10:24:35 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 27 Sep 1997 18:03:41 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > > Arrrrr... Anyone have a good source for small IDE hard drives? > > Why? Aren't you already saved by not using SCSI? From what I'm told, > IDE drives grow on trees and fall freely, as mana from heaven... > > }B-). i'm confused now... i thought ide drives were excrement from hell... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Sat Sep 27 16:19:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19538 for hackers-outgoing; Sat, 27 Sep 1997 16:19:27 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19529 for ; Sat, 27 Sep 1997 16:19:10 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id SAA12614; Sat, 27 Sep 1997 18:19:02 -0500 (EST) From: "John S. Dyson" Message-Id: <199709272319.SAA12614@dyson.iquest.net> Subject: Re: using vm_map_protect on Pentium PC In-Reply-To: <199709270523.BAA07578@singapore.eecs.umich.edu> from Wee Teck Ng at "Sep 27, 97 01:23:44 am" To: weeteck@eecs.umich.edu (Wee Teck Ng) Date: Sat, 27 Sep 1997 18:19:02 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wee Teck Ng said: > hi all, > > we are heavily utilising VM protection (vm_map_prot) on 2.2-stable, > and found that it doesn't work well on Pentium processor. specifically, > when using vm_map_prot to change a page's protection from VM_PROT_READ > to VM_PROT_ALL, only the vm map is updated. > That should be okay. > > pmap_protect does not reset > the pte to writeable (i.e. PG_RW). this will not work on pentium processor, > since page level protection is enforced by the processor (against kernel > access) when WP flag of CR0 is set. > > i've noticed that FreeBSD-current has fixed this problem. my questions are: > 1) is there a 2.x release with a Pentium-compatible VM system? > 2) how stable is 3.0 is for non SMP machines? > Actually, the VM system uses lazy techniques. As soon as you cause a (write) fault, the page SHOULD have it's protections corrected. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Sat Sep 27 17:15:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22436 for hackers-outgoing; Sat, 27 Sep 1997 17:15:14 -0700 (PDT) Received: from polya.blah.org (slmel8p49.ozemail.com.au [203.22.156.209]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22431 for ; Sat, 27 Sep 1997 17:15:09 -0700 (PDT) Received: (from ada@localhost) by polya.blah.org (8.8.6/8.8.5) id KAA01982; Sun, 28 Sep 1997 10:14:58 +1000 (EST) From: Ada T Lim Message-Id: <199709280014.KAA01982@polya.blah.org> Subject: Re: Idea for a software licensing scheme In-Reply-To: <199709272231.PAA16504@hub.freebsd.org> from "owner-hackers-digest@FreeBSD.ORG" at "Sep 27, 97 03:31:19 pm" To: hackers@FreeBSD.ORG Date: Sun, 28 Sep 1997 10:14:58 +1000 (EST) Cc: wpaul@skynet.ctr.columbia.edu, ada@noether.blah.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Bill Paul > Date: Sat, 27 Sep 1997 14:25:26 -0400 (EDT) > Subject: Idea for a software licensing scheme > > I'm hoping some of the more mathematically astute out there can answer > a question for me. A while ago, there was a discussion on -hackers about > possibly creating a software licensing system for FreeBSD as an incentive > to commercial software vendors to port their code. Well, the > Diffie-Hellman patent expired earlier this month, and that started me > thinking about a way to possibly use D-H key pairs as part of a licensing > scheme. I _think_ I've come up with a viable way to do this and have even I'm not completely sure that utilising D-H in this way doesn't violate also RSA. [algorithm deleted] > Now for the verification part. When the application program runs, the > license checking code reads the license file and regenerates the license > secret key, Xl, by computing the MD5 hash of all the license information > (feature name, number of users, etc...). It also reads the authorization > passcode and considers that to be Yl. So now the code has 5 values: > Xa, Ya, Xl, Yl and p. It performs the following computations: > > s1 = Ya ^ Xl % p > > s2 = Yl ^ Xa % p > > This yields two 'session keys,' s1 and s2. If s1 == s2, then the code > considers the license to be valid and the program runs, otherwise it > signals an error and bombs. > > The logic is this: the only way s1 and s2 can come out being the same > is if the license public key, Yl, and the application public key, Ya, > were both generated using the same Diffie-Hellman parameters, g and p. > But I, the vendor, keep g a secret. (Unfortunately, you can't keep p > a secret since the application needs it to compute the session keys.) > This means that only I, the vendor, can derive a license public key (Yl) > that will satisfy the equality. > > Now comes the part I'm not sure about. In theory, it is possible for > an 'attacker' to obtain values for p, Xl and Yl. My question is: can Don't you mean p, Xl, Xa, which are stored in the application, and Yl, which is generated by the attacker? An attacker can then generate Yl values not-very-easily by bruteforcing Xl ^ Ya % p = Yl ^ Xa % p which equates to Xl ^ Ya % p = Yl ^ ( Xa % (p - 1) ) % p. Is there a further shortcut I have forgotten? > Of course, any licensing software can be defeated by patching the > application executable, and my scheme does nothing to defend against > that. But that kind of attack requires a fair amount of OS-dependent > and CPU-dependent knowledge which the ovwewhelming number of computer > users in the world today are unlikely to have. Also, consider what > happens when a vendor makes their software available for multuple > platforms and uses the same licensing software for each one. This makes > it convenient for the vendor since he only has to generate one license > file, and the customer can use it on whatever platform he chooses. It > also makes it very convenient for a software pirate: rather than have > to generate patched binaries for every platform, all he has to do is > coerce the application into generating a magic unlimited-use license on > one platform, and he has automatically defeated the licensing scheme for > all platforms in one stroke. > > Anyway, the question stands: does my idea have merit, or should I > make a reservation for the conical hat. It looks good, as long as D-H remains strong. Whether this has been proven I don't know. Have you seen how OSS distribute their license keys? They produce a license file which is plaintext readable, containing the license number and suchnot. Then they do a pgp sign of the license file. This signature is only creatable using their secret key, which isn't released. The application contains their public key, which can be used to verify the signature. Admittedly, this is based upon RSA, which is still patented. Does D-H have a method of signing documents? Ada From owner-freebsd-hackers Sat Sep 27 17:50:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23839 for hackers-outgoing; Sat, 27 Sep 1997 17:50:29 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23834 for ; Sat, 27 Sep 1997 17:50:26 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA26930; Sat, 27 Sep 1997 17:49:54 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma026928; Sat Sep 27 17:49:45 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id RAA03368; Sat, 27 Sep 1997 17:49:45 -0700 (PDT) From: Archie Cobbs Message-Id: <199709280049.RAA03368@bubba.whistle.com> Subject: Re: Raise your hand if you know how to make this work. In-Reply-To: <3.0.2.32.19970927053159.006c81e8@bugs.us.dell.com> from Tony Overfield at "Sep 27, 97 05:31:59 am" To: tony@dell.com (Tony Overfield) Date: Sat, 27 Sep 1997 17:49:45 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> there is a function to do this for you > >> it's rather trivial. > >> check clock.c > >> and see how the PCAUDIO device uses this to get itself > >> called 16000 times per second.. > > At 07:23 AM 9/25/97 +0000, Terry Lambert wrote: > >> > Note: this is about twice as fast as the standard clock can go; at > >> > the highest divider, it's only capable of 8192 interrupts a second. > >> > >Jamil J. Weatherbee wrote > >> If we are still talking about an 8253 I know you to be wrong here, the > >> frequency varies like 1.9MHz/(1-65535). > > > >This information is from the Linux tier code and from the FreeBSD > >clock divider code for the PC audio driver, and not from the chipset > >documentation, so I'm prepared to be wrong (along with the comments > >in both these drivers). > > I think Terry has confused the two "standard" timers. > > The "standard clock" timer, on IRQ0, is a 1.193 MHz clock with a > programmable 16-bit divisor that can interrupt as fast as you > would ever want it to. > > The "CMOS real-time clock" has a periodic interrupt, on IRQ8, based > on a 32768 Hz clock with a small set of divisors that support > interrupt rates between 2 Hz and 8192 Hz, inclusive, in powers of two. Here is a file you can add to your kernel which will create a new sysctl variable "kern.ticker". Setting this variable to any value between 100 and 20000 will set the standard clock rate to that value. Setting it to zero resets it back to what it was before. This comes in very handy when you're trying to reproduce certain types of bugs.... :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com begin 644 ticker.c.gz M'XL(`(&H+30"`XU4;6_:,!#^W/R*6RM5294!U:1M75^DC$(7#4$5PJI^BE+' M-%9-0FV'K>OZWW>V"6]ATI`"Y'SWW'//W=EIGSAP`HJ1)RI:!/_KUVXY?Q'L M,5?@=CTX/3O[!'^]2+\6A%<9A0L$:,]3DR`DEDW57GZ\?-QKUYJ@?>-@EJ(D!6T;$;=CZB/.9DS)G3CVX?/' M-I.I?K;#UB>D^M>)3).,+A@Q$CAV7L)AW(N&P0#ZDV$W#D?#L6T1@%0X&006 M)AX42KE2B(LI.R!2;2>'$_&S&(,Z!E2;1+4SL MW,+X?MR-!\FW8'@]Z$5)$-V,SQM4?P11&'P=]':I:DS-;15AT6`<3_I]Z[O$ MOXU&7=@@G_X/_^(+A)HCL?$]E/QP?)?M-R M:I3PH5F'#X?A(7X=>BLN32?7LYS6[)W_4\1Y12HXX%*9DDN>)68%+\%6#\9\ M4-"?>^TX[J4XU[JQ*;BN>46?9>X\+3).$_1TL:US'XYK'%\7+NBSYWE&"D%5 M)0H;;UJKX59)+R[AM-.QGAM,.K4C`KV_PH.Y$O#N$H:3P0".C]>N:*L+LR#K M&:Q]3-(=%F]:;S#-7_E[RPL)+:!O`-$!58(L<3`1"A8IK[`X%$%0;NXWIC3% M-6NDO=4J/?#.]DZL.)GFF.G6FLZYV0+76^E=%_2ZU-!D3"PMUU0$L*G5VZZP M*%)*GBLF5E'K!JV7T#.LO4VXVLULX9S_ Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA24850 for hackers-outgoing; Sat, 27 Sep 1997 18:12:35 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA24844 for ; Sat, 27 Sep 1997 18:12:31 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id DAA02142 for hackers@freebsd.org; Sun, 28 Sep 1997 03:12:33 +0200 (MESZ) From: Robert Eckardt Message-Id: <199709280112.DAA02142@ghost.mep.ruhr-uni-bochum.de> Subject: ? malloc Dump ? To: hackers@freebsd.org Date: Sun, 28 Sep 1997 03:12:33 +0200 (MESZ) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, after asking already on -questions, I now try -hackers. I'm trying to get malloc (2.2.2) to dump statistics in `malloc.out'. I used so far: 1. extern char *malloc_options; ... malloc_options = "D"; /* first line in main() */ 2. % echo $MALLOC_OPTIONS D 3. /etc/malloc.conf -> D I did touch malloc.out and main() returns with `return 0;' However, I don't get the statistics. -rw-rw-r-- 1 roberte work 0 23 Sep 23:36 malloc.out What am I doing wrong ? (Option `A' works, btw.) Robert -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-hackers Sat Sep 27 18:24:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25348 for hackers-outgoing; Sat, 27 Sep 1997 18:24:31 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25340 for ; Sat, 27 Sep 1997 18:24:25 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA05050; Sun, 28 Sep 1997 10:54:11 +0930 (CST) Message-ID: <19970928105411.00690@lemis.com> Date: Sun, 28 Sep 1997 10:54:11 +0930 From: Greg Lehey To: Nate Williams Cc: Chuck Robey , Richard Wackerbarth , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? References: <199709272233.QAA27878@rocky.mt.sri.com> <199709272247.QAA28003@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709272247.QAA28003@rocky.mt.sri.com>; from Nate Williams on Sat, Sep 27, 1997 at 04:47:59PM -0600 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 04:47:59PM -0600, Nate Williams wrote: > Chuck Robey writes: >>>> Suppose that the snapshots are always generated by using a CVS checkout >>>> that never references the head directly. In other words, in a manner >>>> that others can reproduce at a later time. (For example, a checkout >>>> by date, using yesterday's date) >>> >>> Except that means lots more work for the release engineer. The RE has >>> enough problems just making a release, making sure that the code is >>> 'synchronized' to a certain date would make it that much harder. I >>> think it would be 'easier' to simply tag the tree. >> >> I think you mistake his intent, Nate. I think he meant it this way. The >> RE updates his tree, writes down the date/time that it's updated to. > > But, the tree isn't exactly in sync. with the 'real' CVS tree, so the > code may not be exactly the same. With 'real' releases, the actual CVS > tree is locked down by the RE, so his tree will be the same, since > no-one is allowed to modify it. This isn't the case with SNAPS. > > So, the time/date he uses in his private tree may have other changes > that occur when people commit code to the 'real' tree. > > The whole FreeBSD process is a multi-threaded/SMP kind of thing, so you > gotta think about race conditions and all those other OS kinds of > things. :) I still don't see the problem. CVS already has the solution: the RE selects a certain date for the snap, basically whatever he wants. He waits for the time to pass, pulls a copy of the repository (though this is not really necessary), and then checks out -current as of the time he decided for the snap. Anybody else who has a tree at least that up-to-date can do exactly the same thing. Greg From owner-freebsd-hackers Sat Sep 27 18:44:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26175 for hackers-outgoing; Sat, 27 Sep 1997 18:44:49 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26163 for ; Sat, 27 Sep 1997 18:44:43 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id SAA27389; Sat, 27 Sep 1997 18:51:57 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id SAA28124; Sat, 27 Sep 1997 18:46:44 -0700 (PDT) Date: Sat, 27 Sep 1997 18:46:44 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199709280146.SAA28124@dog.farm.org> To: mike@smith.net.au (Mike Smith) Cc: freebsd-hackers@freebsd.org Subject: Re: rc.sysctl? Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709260733.RAA00370@word.smith.net.au> you wrote: > You might want to consider a more generalised sysctl tweaking mechanism > , eg. one that consumed variables of the form 'sysctl_X' where X was a > monotonically increasing value starting with 0. You could handle these > early on in rc, just after rc.conf is sourced. This would still suffer > from the "sysctl is not in /sbin" problem for people using NFS for /usr. How about committing this?? # /usr/src/sbin/sysctl/Makefile DIR=${.CURDIR}/../../usr.sbin/sysctl CFLAGS+=-static NOMAN=yes .PATH: ${DIR} .include "${DIR}/Makefile" (tested, works, used; patch for /usr/src/sbin/Makefile is obvious) There are many things which can be done with sysctl and are potentially useful from single-user... say, if I need special IP options for NFS mounts, etc.?? # ls -la /sbin/sysctl -r-xr-xr-x 1 bin bin 57344 27 ÓÅÎ 18:43 /sbin/sysctl # ls -la /usr/sbin/sysctl -r-xr-xr-x 1 bin bin 12288 27 ÉÀÎ 19:55 /usr/sbin/sysctl # Please, anybody who wants to make life easier for diskless boxes, do it! From owner-freebsd-hackers Sat Sep 27 18:53:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26687 for hackers-outgoing; Sat, 27 Sep 1997 18:53:34 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26681 for ; Sat, 27 Sep 1997 18:53:29 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id LAA05398; Sun, 28 Sep 1997 11:23:03 +0930 (CST) Message-ID: <19970928112303.32188@lemis.com> Date: Sun, 28 Sep 1997 11:23:03 +0930 From: Greg Lehey To: Joerg Wunsch Cc: hackers@FreeBSD.ORG, Mike Smith Subject: Re: Timeout for sh(1) 'read' ?? References: <199709260748.RAA00456@word.smith.net.au> <19970927163558.WP09379@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970927163558.WP09379@uriah.heep.sax.de>; from J Wunsch on Sat, Sep 27, 1997 at 04:35:58PM +0200 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 04:35:58PM +0200, J Wunsch wrote: > As Mike Smith wrote: > >> Hiho folks, a question for the sh(1) studs amongst you : >> >> - I want to prompt for input using 'read', and have the read return in >> some fashion after a timeout. > > A quick search for the word `timeout' in the ksh93 man page unveils: > > TMOUT If set to a value greater than zero, TMOUT > will be the default timeout value for the > read built-in command. The select compound > command terminates after TMOUT seconds when > input is from a terminal. Otherwise, the > shell will terminate if a line is not > entered within the prescribed number of sec- > onds while reading from a terminal. (Note > that the shell can be compiled with a maxi- > mum bound for this value which cannot be > exceeded.) > > and: > > read [ -Aprs ] [ -d delim] [ -t timeout] [ -u > unit] [ vname?prompt ] [ vname ... ] > The shell input mechanism. One line is read and is > broken up into fields using the characters in IFS > as separators. [...] > > Posix doesn't seem to have any opinion for this, so it looks like just > creeping featurism on ksh's side. (Posix only mentions option -r.) pdksh and bash both use this variable just for command line prompts. Try this: bash$ TMOUT=5 bash$ (wait 5 seconds) Then bash dies on you. It doesn't work for what Mike's looking for. Greg From owner-freebsd-hackers Sat Sep 27 19:07:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27531 for hackers-outgoing; Sat, 27 Sep 1997 19:07:48 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27521 for ; Sat, 27 Sep 1997 19:07:44 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA26964; Sat, 27 Sep 1997 19:07:25 -0700 (PDT) To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf In-reply-to: Your message of "Sat, 27 Sep 1997 11:40:52 -0000." <199709271140.EAA24299@usr04.primenet.com> Date: Sat, 27 Sep 1997 19:07:24 -0700 Message-ID: <26959.875412444@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Of course, you should feel free to suggest to us any soloution which > does not require us to run named to implement. And not feel free to > suggest running named. Maybe you should run named. Just a suggestion. ;) Jordan From owner-freebsd-hackers Sat Sep 27 19:14:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28082 for hackers-outgoing; Sat, 27 Sep 1997 19:14:54 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28070 for ; Sat, 27 Sep 1997 19:14:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA27017; Sat, 27 Sep 1997 19:13:32 -0700 (PDT) To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. In-reply-to: Your message of "Sat, 27 Sep 1997 11:54:02 -0000." <199709271154.EAA24656@usr04.primenet.com> Date: Sat, 27 Sep 1997 19:13:31 -0700 Message-ID: <27013.875412811@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This, of course, has to do with ksh's method of backgrounding a > process. A process which is in the background is a chikd of init, Say *what*? No it's not! Try again. :-) >Dealing with the error case is only a requirement of FreeBSD and >several other "broken" systems. The only other one that springs to Dealing with I/O errors on reading from the tty is the responsibilty of any reasonably well written program. Is that a genuine Stetson I see you talking out of there? Nice hat! ;-) Jordan From owner-freebsd-hackers Sat Sep 27 19:25:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28654 for hackers-outgoing; Sat, 27 Sep 1997 19:25:45 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28647 for ; Sat, 27 Sep 1997 19:25:40 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA03408; Sun, 28 Sep 1997 11:53:10 +0930 (CST) Message-Id: <199709280223.LAA03408@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? In-reply-to: Your message of "Sat, 27 Sep 1997 16:42:50 +0200." <19970927164250.YQ59393@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 11:53:06 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > NB: pdksh only implements the last of the three features (at least my > version)... > > > read [ -Aprs ] [ -d delim] [ -t timeout] [ -u > > unit] [ vname?prompt ] [ vname ... ] > > ....nor does it support -t timeout. > > Adding -t timeout seems to be the best way to me. ${TMOUT} is just > confusing given the multitude of things it's going to do. OK. To be added are : -t -d Such that if no input is received after seconds, will be returned, or the empty string if is not supplied. > Btw., if you're going to do this, please do also implement -r. It > seems to be mandated by Posix.2: > > By default, unless the -r option is specified, backslash (\) shall act as > an escape character, as described in 3.2.1. This is more complicated; our sh currently does not exhibit this behaviour unless -e is specified, ie. -r is its "normal" behaviour and -e specifies the POSIXish escaping. I could do with some guidance from people likely to be bitten by this; is such a major change in the name of POSIX worthwhile? mike From owner-freebsd-hackers Sat Sep 27 19:33:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA29692 for hackers-outgoing; Sat, 27 Sep 1997 19:33:22 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29687 for ; Sat, 27 Sep 1997 19:33:19 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA27234; Sat, 27 Sep 1997 19:33:00 -0700 (PDT) To: Eivind Eklund cc: hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sat, 27 Sep 1997 17:29:23 +0200." <199709271529.RAA11811@bitbox.follo.net> Date: Sat, 27 Sep 1997 19:33:00 -0700 Message-ID: <27230.875413980@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk An individual tag operation isn't expensive so much as is tagging *every single file* in the src/ hierarchy, essentially what we have to do at each major release. Adding "merge me" tags on a case by case basis would probably be a little different since you'd expect that to happen over a long period of time (the life of the branch you're merging into, basically) and to small collections of files in each instance. That'd make it much less of an impact on all those users out there who are cvsup'ing daily, and not quite what I was talking about below. I believe someone was asking why each SNAP couldn't be reproduced exactly by checking out a tree with the "snap tag", and to do that I'd essentially need to tag all the sources (and, if one wanted to be _really_ anal, the ports) once a day. That would be far too expensive and the lockdown time on the repository to create the tags would not be appreciated either. Jordan > > Yes, I tag and then I build from that tag after resyncronizing my > > local repository. > > > > Unfortunately, tags are expensive and you don't just lay them down > > for fun. > > In what way are release tags expensive? I've been thinking of using > tags to make a commit a single operation instead of a bunch of changes > just connected by the commit-log, and for storing meta-information for > merges. With this and some merge-related tags (for storing > meta-information) syncing RELENG_* and -current the way we want should > become quite a bit easier. Are the tags so expensive this would be > non-feasible? I thought they would be a comparatively cheap way of > storing minor amounts of meta-information. > > Eivind. From owner-freebsd-hackers Sat Sep 27 19:40:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA00346 for hackers-outgoing; Sat, 27 Sep 1997 19:40:14 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA00341 for ; Sat, 27 Sep 1997 19:40:09 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id UAA02500; Sat, 27 Sep 1997 20:39:49 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id UAA28656; Sat, 27 Sep 1997 20:39:46 -0600 (MDT) Date: Sat, 27 Sep 1997 20:39:46 -0600 (MDT) Message-Id: <199709280239.UAA28656@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Greg Lehey Cc: Nate Williams , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: <19970928105411.00690@lemis.com> References: <199709272233.QAA27878@rocky.mt.sri.com> <199709272247.QAA28003@rocky.mt.sri.com> <19970928105411.00690@lemis.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I still don't see the problem. CVS already has the solution: the RE > selects a certain date for the snap, basically whatever he wants. Yeah, right. "OK, on Saturday, everything must work right, caue that's when I'm building the SNAP." *sarcasm on* How about it Jordan, seems reasonable and should work fine, right? *sarcasm off* > He waits for the time to pass, pulls a copy of the repository (though > this is not really necessary), and then checks out -current as of the > time he decided for the snap. And if it doesn't work, then what? He fixes bugs, and whiles he fixing them someone else is introducing new ones. The idea behind SNAPS is they're supposed to be fairly easy to produce, so going through the same gyrations as what is required for RELEASES shouldn't have to be done. If the world were a perfect place it would work fine, but it isn't. Nate From owner-freebsd-hackers Sat Sep 27 19:49:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA00708 for hackers-outgoing; Sat, 27 Sep 1997 19:49:23 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA00702 for ; Sat, 27 Sep 1997 19:49:19 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA27361; Sat, 27 Sep 1997 19:48:25 -0700 (PDT) To: Richard Wackerbarth cc: Nate Williams , Eivind Eklund , Chuck Robey , Eivind Eklund , hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sat, 27 Sep 1997 15:17:56 CDT." Date: Sat, 27 Sep 1997 19:48:25 -0700 Message-ID: <27357.875414905@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > A suggestion to consider. -- It's a thought. Hmmm. Jordan From owner-freebsd-hackers Sat Sep 27 19:56:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA01072 for hackers-outgoing; Sat, 27 Sep 1997 19:56:50 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA01056 for ; Sat, 27 Sep 1997 19:56:48 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA27437; Sat, 27 Sep 1997 19:55:56 -0700 (PDT) To: Chuck Robey cc: Nate Williams , Richard Wackerbarth , Eivind Eklund , Eivind Eklund , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sun, 28 Sep 1997 06:43:38 EDT." Date: Sat, 27 Sep 1997 19:55:56 -0700 Message-ID: <27433.875415356@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think you mistake his intent, Nate. I think he meant it this way. The > RE updates his tree, writes down the date/time that it's updated to. He The RE in this case is a script. Just keep that in mind. :) Jordan From owner-freebsd-hackers Sat Sep 27 20:03:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA01359 for hackers-outgoing; Sat, 27 Sep 1997 20:03:14 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA01351 for ; Sat, 27 Sep 1997 20:03:10 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id MAA08380; Sun, 28 Sep 1997 12:33:00 +0930 (CST) Message-ID: <19970928123300.22669@lemis.com> Date: Sun, 28 Sep 1997 12:33:00 +0930 From: Greg Lehey To: Nate Williams Cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: How do I check out a snapshot? References: <199709272233.QAA27878@rocky.mt.sri.com> <199709272247.QAA28003@rocky.mt.sri.com> <19970928105411.00690@lemis.com> <199709280239.UAA28656@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709280239.UAA28656@rocky.mt.sri.com>; from Nate Williams on Sat, Sep 27, 1997 at 08:39:46PM -0600 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 08:39:46PM -0600, Nate Williams wrote: >> I still don't see the problem. CVS already has the solution: the RE >> selects a certain date for the snap, basically whatever he wants. > > Yeah, right. "OK, on Saturday, everything must work right, caue that's > when I'm building the SNAP." > > *sarcasm on* > How about it Jordan, seems reasonable and should work fine, right? > *sarcasm off* *reality on* So how do you decide when you're going to cut a snap? Or, given the current situation, how did you? At some point you made a decision. This is no different. *reality off^H^H^Hah what the hell, let's stay realistic* >> He waits for the time to pass, pulls a copy of the repository (though >> this is not really necessary), and then checks out -current as of the >> time he decided for the snap. > > And if it doesn't work, then what? He fixes bugs, and whiles he fixing > them someone else is introducing new ones. But this isn't a SNAP. > The idea behind SNAPS is they're supposed to be fairly easy to > produce, so going through the same gyrations as what is required for > RELEASES shouldn't have to be done. Nobody's saying it should be. It's just a snapshot. Somehow you're not understanding. Nobody's asking anybody to do extra work. The only think I was originally asking was to know the time of the snapshot. If I have understood you, the problem has been that a snapshot is a checkout of the main branch of the tree, and the "problem" is that the tree is changing during checkout, so there isn't a fixed time. Correct or not? 1. If this is correct, then you just have to check out the snap as of an arbitrary time in the not-too-distant past. Any updates which come in after this time won't affect the checkout. All anybody who wants to repeat the snap needs is the checkout time. 2. If this isn't correct, and you're not doing patchwork on the checked-out version, what is the situation? I certainly don't see any other possibility. > If the world were a perfect place it would work fine, but it isn't. If the world were a perfect place, we wouldn't need snaphots :-) Greg From owner-freebsd-hackers Sat Sep 27 20:15:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02179 for hackers-outgoing; Sat, 27 Sep 1997 20:15:41 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02171 for ; Sat, 27 Sep 1997 20:15:36 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id XAA25543; Sat, 27 Sep 1997 23:15:06 -0400 (EDT) Date: Sun, 28 Sep 1997 11:15:33 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Jordan K. Hubbard" cc: Nate Williams , Richard Wackerbarth , Eivind Eklund , Eivind Eklund , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-Reply-To: <27433.875415356@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Jordan K. Hubbard wrote: > > I think you mistake his intent, Nate. I think he meant it this way. The > > RE updates his tree, writes down the date/time that it's updated to. He > > The RE in this case is a script. Just keep that in mind. :) I thought everyone was agreed that "Jordan" was an AI program? > > Jordan > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 27 20:16:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02285 for hackers-outgoing; Sat, 27 Sep 1997 20:16:33 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02279 for ; Sat, 27 Sep 1997 20:16:30 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA27631; Sat, 27 Sep 1997 20:15:58 -0700 (PDT) To: Nate Williams cc: Greg Lehey , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sat, 27 Sep 1997 20:39:46 MDT." <199709280239.UAA28656@rocky.mt.sri.com> Date: Sat, 27 Sep 1997 20:15:58 -0700 Message-ID: <27628.875416558@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > *sarcasm on* > How about it Jordan, seems reasonable and should work fine, right? > *sarcasm off* Heh. Well, considering that I have no intention whatsoever of actually making any changes to the SNAP build mechanism at this time, it doesn't bother me at all to debate the topic here. ;-) Jordan From owner-freebsd-hackers Sat Sep 27 20:18:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02388 for hackers-outgoing; Sat, 27 Sep 1997 20:18:50 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02383 for ; Sat, 27 Sep 1997 20:18:46 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id MAA08753; Sun, 28 Sep 1997 12:48:38 +0930 (CST) Message-ID: <19970928124837.18033@lemis.com> Date: Sun, 28 Sep 1997 12:48:37 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: Nate Williams , hackers@freebsd.org Subject: Re: How do I check out a snapshot? References: <19970928123300.22669@lemis.com> <27659.875416652@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <27659.875416652@time.cdrom.com>; from Jordan K. Hubbard on Sat, Sep 27, 1997 at 08:17:32PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 08:17:32PM -0700, Jordan K. Hubbard wrote: >> So how do you decide when you're going to cut a snap? Or, given the > > It's run from cron. If it falls over, it tries again at the same time > the next morning (0200 EDT). No manual intervention in this process > is involved or desired. OK. So check out the tree as of 0100 EDT. What's the problem? Why EDT? Greg From owner-freebsd-hackers Sat Sep 27 20:19:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02422 for hackers-outgoing; Sat, 27 Sep 1997 20:19:09 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02417 for ; Sat, 27 Sep 1997 20:19:07 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA27662; Sat, 27 Sep 1997 20:17:32 -0700 (PDT) To: Greg Lehey cc: Nate Williams , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sun, 28 Sep 1997 12:33:00 +0930." <19970928123300.22669@lemis.com> Date: Sat, 27 Sep 1997 20:17:32 -0700 Message-ID: <27659.875416652@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > So how do you decide when you're going to cut a snap? Or, given the It's run from cron. If it falls over, it tries again at the same time the next morning (0200 EDT). No manual intervention in this process is involved or desired. Jordan From owner-freebsd-hackers Sat Sep 27 20:24:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02766 for hackers-outgoing; Sat, 27 Sep 1997 20:24:39 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02761 for ; Sat, 27 Sep 1997 20:24:36 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA27736; Sat, 27 Sep 1997 20:24:07 -0700 (PDT) To: Greg Lehey cc: Nate Williams , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sun, 28 Sep 1997 12:48:37 +0930." <19970928124837.18033@lemis.com> Date: Sat, 27 Sep 1997 20:24:07 -0700 Message-ID: <27732.875417047@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > OK. So check out the tree as of 0100 EDT. What's the problem? I don't know - that remains to be found out, eh? ;-) I'll try it on an experimental basis sometime next week. I'm not saying that the idea has no merit, I'm just not keen to mess with the SNAP server so soon after getting it back up again (KATO's patch worked to prevent the machine from crashing every 24 hours). > Why EDT? Why not? :-) Jordan From owner-freebsd-hackers Sat Sep 27 20:26:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02851 for hackers-outgoing; Sat, 27 Sep 1997 20:26:46 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02846 for ; Sat, 27 Sep 1997 20:26:42 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id MAA08782; Sun, 28 Sep 1997 12:56:33 +0930 (CST) Message-ID: <19970928125633.15675@lemis.com> Date: Sun, 28 Sep 1997 12:56:33 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: Nate Williams , hackers@freebsd.org Subject: Re: How do I check out a snapshot? References: <19970928124837.18033@lemis.com> <27732.875417047@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <27732.875417047@time.cdrom.com>; from Jordan K. Hubbard on Sat, Sep 27, 1997 at 08:24:07PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 08:24:07PM -0700, Jordan K. Hubbard wrote: >> OK. So check out the tree as of 0100 EDT. What's the problem? > > I don't know - that remains to be found out, eh? ;-) > > I'll try it on an experimental basis sometime next week. I'm > not saying that the idea has no merit, I'm just not keen to > mess with the SNAP server so soon after getting it back up again > (KATO's patch worked to prevent the machine from crashing every 24 > hours). OK, that sounds reasonable. >> Why EDT? > > Why not? :-) Well, I prefer CST: it's more universal. It could be the time in Austin, TX (UTC-6), the time in Beijing (UTC+8), or the time here in Adelaide (UTC+9.5). For one reason or another, I find myself in one of those places quite often :-) More seriously, I thought that the machine was in California. Greg From owner-freebsd-hackers Sat Sep 27 20:28:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02948 for hackers-outgoing; Sat, 27 Sep 1997 20:28:17 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02938 for ; Sat, 27 Sep 1997 20:28:15 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA27788; Sat, 27 Sep 1997 20:27:49 -0700 (PDT) To: Greg Lehey cc: Nate Williams , hackers@freebsd.org Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Sun, 28 Sep 1997 12:56:33 +0930." <19970928125633.15675@lemis.com> Date: Sat, 27 Sep 1997 20:27:49 -0700 Message-ID: <27784.875417269@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > More seriously, I thought that the machine was in California. No, it's in Canada. Jordan From owner-freebsd-hackers Sat Sep 27 21:36:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05923 for hackers-outgoing; Sat, 27 Sep 1997 21:36:42 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05914 for ; Sat, 27 Sep 1997 21:36:34 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id AAA18538 for ; Sun, 28 Sep 1997 00:41:50 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sun, 28 Sep 1997 00:41:50 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: arrrrgh! CVS is killing me :) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm having trouble with a 586/133 running 2.2.2-RELEASE, i want to upgrade it, however sysinstall keeps dumping core with signal 11 whenever it tried to log onto a FTP site to download files... i tried to CVSup to stable and got the "release" section and tried to re-compile sysinstall well it bombed out with resolv.h not finding a reference to a #define'd MAXDNAME that is included in the file maxdname.c i also CVSup'd my include and gnu sections... i have limited disk space, and the same error happens on a machine that i have where i did a total CVSup... any help would be appreciated, as well as any suggestions for helping to diagnose the problem i am having... thank you ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" From owner-freebsd-hackers Sat Sep 27 22:50:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA08871 for hackers-outgoing; Sat, 27 Sep 1997 22:50:44 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA08866 for ; Sat, 27 Sep 1997 22:50:41 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA29711 for hackers@FreeBSD.ORG; Sun, 28 Sep 1997 07:50:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA00205; Sun, 28 Sep 1997 07:34:31 +0200 (MET DST) Message-ID: <19970928073430.CC50911@uriah.heep.sax.de> Date: Sun, 28 Sep 1997 07:34:30 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? References: <19970927164250.YQ59393@uriah.heep.sax.de> <199709280223.LAA03408@word.smith.net.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709280223.LAA03408@word.smith.net.au>; from Mike Smith on Sep 28, 1997 11:53:06 +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mike Smith wrote: > > Adding -t timeout seems to be the best way to me. ${TMOUT} is just > > confusing given the multitude of things it's going to do. > > OK. To be added are : > > -t > -d > > Such that if no input is received after seconds, > will be returned, or the empty string if is not supplied. Oh no! Please don't introduce options with a different meaning than in ksh. ksh93 uses -d delim for an alternate line delimiter character than newline, and does not provide for a default value. I see a need for the -t timeout parameter, since it's basically not possible to catch it otherwise without going through major hoops (due to shell-internal variable assignments that are required, so you can't e.g. easily employ a subshell). However, assigning default values is something that is reasonably covered by things like: $foo=${foo:-default} (Implementing -r) > I could do with some guidance from people likely to be bitten by this; > is such a major change in the name of POSIX worthwhile? Well, it's hard to proclaim Posix conformance otherwise. I thought that was one of our goals. I doubt anybody would notice the change... (But if you wanna know my personal opinion: the Posix way is stupid. They should at least have made it the other way round. However, the LNEXT character is IMHO not standardized by Posix, so this explains the backslash mess they are proposing.) -- 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-hackers Sat Sep 27 23:07:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA09739 for hackers-outgoing; Sat, 27 Sep 1997 23:07:28 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA09726 for ; Sat, 27 Sep 1997 23:07:05 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id PAA04849; Sun, 28 Sep 1997 15:33:18 +0930 (CST) Message-Id: <199709280603.PAA04849@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? In-reply-to: Your message of "Sun, 28 Sep 1997 07:34:30 +0200." <19970928073430.CC50911@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 15:33:13 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Please don't introduce options with a different meaning than in ksh. > ksh93 uses -d delim for an alternate line delimiter character than > newline, and does not provide for a default value. Ok. > I see a need for the -t timeout parameter, since it's basically not > possible to catch it otherwise without going through major hoops (due > to shell-internal variable assignments that are required, so you can't > e.g. easily employ a subshell). However, assigning default values is > something that is reasonably covered by things like: > > $foo=${foo:-default} Hmm. Actually, you would get the desired behaviour with val=${default} read -t 5 val because read won't have had a chance to modify 'val' if it does time out. So should read return an error if it times out? What does ksh do? > (Implementing -r) > > > I could do with some guidance from people likely to be bitten by this; > > is such a major change in the name of POSIX worthwhile? > > Well, it's hard to proclaim Posix conformance otherwise. I thought > that was one of our goals. I doubt anybody would notice the change... This is where I'm not so sure. Naturally, POSIX is desirable (if stupid), I just don't want to get stomped for violating POLA. mike From owner-freebsd-hackers Sat Sep 27 23:17:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10210 for hackers-outgoing; Sat, 27 Sep 1997 23:17:20 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10204 for ; Sat, 27 Sep 1997 23:17:16 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA01596; Sat, 27 Sep 1997 23:16:43 -0700 (PDT) Date: Sat, 27 Sep 1997 23:16:43 -0700 (PDT) From: "Jamil J. Weatherbee" To: dennis cc: Luigi Rizzo , Christoph Kukulies , freebsd-hackers@freefall.FreeBSD.org Subject: Re: diskless 100 Mbit - IntelEtherexpress - Q In-Reply-To: <3.0.32.19970926110236.00abfa18@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >the way I do it now is to use a boot floppy with a kernel on it and the > >diskless stuff that Tor Egge wrote and recently (march-april ?) was > >committed. The problem with solution (which I have used with linux) is 1) the disk wears out rather quickly 2) if you write protect it then it is not possible to remotely alter the kernel and reboot 3) the floppy drive becomes pretty much useless From owner-freebsd-hackers Sat Sep 27 23:48:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA11948 for hackers-outgoing; Sat, 27 Sep 1997 23:48:25 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA11943 for ; Sat, 27 Sep 1997 23:48:19 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 21895 invoked by uid 1001); 28 Sep 1997 06:48:15 +0000 (GMT) To: tlambert@primenet.com Cc: hackers@FreeBSD.ORG Subject: Re: r-cmds and DNS and /etc/host.conf In-Reply-To: Your message of "Sat, 27 Sep 1997 21:27:02 +0000 (GMT)" References: <199709272127.OAA11524@usr08.primenet.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 28 Sep 1997 08:48:15 +0200 Message-ID: <21893.875429295@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > but the vendor of that cr*p didn't get the underlying nameserver > > working correctly at all. (For example, the server never hands out > > authoritative answers, even if it is for sure an authoritative server.) > > This may be intentional laxity. In their opinion, you are supposed > to buy an NT server and configure WINS naming instead of DNS. Not so sure about this - as far as I know WINS is going away in NT 5.0 (to be replaced by DNS dynamic updates). Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Sep 27 23:50:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA12065 for hackers-outgoing; Sat, 27 Sep 1997 23:50:42 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA12060 for ; Sat, 27 Sep 1997 23:50:38 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA00101 for hackers@FreeBSD.ORG; Sun, 28 Sep 1997 08:50:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA00579; Sun, 28 Sep 1997 08:36:20 +0200 (MET DST) Message-ID: <19970928083619.EN11505@uriah.heep.sax.de> Date: Sun, 28 Sep 1997 08:36:19 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? References: <19970928073430.CC50911@uriah.heep.sax.de> <199709280603.PAA04849@word.smith.net.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709280603.PAA04849@word.smith.net.au>; from Mike Smith on Sep 28, 1997 15:33:13 +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mike Smith wrote: > > $foo=${foo:-default} > > Hmm. Actually, you would get the desired behaviour with > > val=${default} Well, sure. I didn't see this. :) You need to assign a value in the first place anyway. > read -t 5 val > > because read won't have had a chance to modify 'val' if it does time > out. So should read return an error if it times out? What does ksh do? It does: j@uriah 66% ksh93 $ read -t 5 foo # and just wait $ echo $? 1 $ read -t 5 foo babble $ echo $? 0 $ exit -- 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-hackers Sat Sep 27 23:58:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA12509 for hackers-outgoing; Sat, 27 Sep 1997 23:58:15 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA12489; Sat, 27 Sep 1997 23:58:08 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id XAA20941; Sat, 27 Sep 1997 23:56:53 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709280656.XAA20941@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709272228.PAA14163@usr08.primenet.com> from Terry Lambert at "Sep 27, 97 10:28:24 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 27 Sep 1997 23:56:53 -0700 (PDT) Cc: sthaug@nethelp.no, tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > If you want something that really tries to ``prevent'' this you want > > a switch and not a hub, and you want full-duplex non-simplex NIC cards > > in every box connected to that switch, and no I'm not just talking > > about 100Base stuff here, it applies to both 10 and 100Base ethernet > > over TP. > > While you are in the process emptying your wallet into a fire, you > may want to consider buying good cards instead, and avoiding the > problem altogether... Ah, Terry, do you realize who you quoted above? Please reread what I wrote, I don't think you can find a NIC that meets my spec without getting a ``good one''. I was also ``preventing'' the collisions, something some major corps have paid me good money to go in and do. How about a 50 node HP7000/J200 cluster using Catalyst 5000 switches. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD