From owner-freebsd-hackers Sun Apr 21 00:01:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA00373 for hackers-outgoing; Sun, 21 Apr 1996 00:01:56 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA00364 for ; Sun, 21 Apr 1996 00:01:50 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id JAA15888; Sun, 21 Apr 1996 09:01:01 +0200 From: John Hay Message-Id: <199604210701.JAA15888@zibbi.mikom.csir.co.za> Subject: Re: IPX Netbios packets. To: wollman@lcs.mit.edu (Garrett Wollman) Date: Sun, 21 Apr 1996 09:01:01 +0200 (SAT) Cc: hackers@FreeBSD.ORG (FreeBSD-hackers) In-Reply-To: <9604202130.AA19649@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 20, 96 05:30:20 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > < said: > > > So I am looking for a nice generic way to be able to disable it per device. > > I thought of flags with ifconfig, but I don't like that idea too much. > > Another way might be with the sysctl interface, but I'm not sure how to > > do it for different interface without having to add code to every network > > interface in the kernel. > > An interface flag is almost certainly the right way to go. What you > need to do is to fix all the interface drivers to not abuse IFF_LINK* > for medium selection (there is already another field in the struct for > that purpose), and then use one of the newly-freed flags. Hmmm. It feels like I had this conversation a while back also. :-) This does not imply acceptance of the job. :-) I just want to figure out what must change, and how much work it will be. And hopefully what might break. The normal network drivers will have to use if_physical then I presume? This means that ifconfig will have to be taught new things. What should it be called? phys0 - phys32, or something more understandable? Is there any other user level programs that will have to be changed? What should happen with slip? It uses all three IFF_LINK flags for different things - compression, icmp suppression and auto enable compression. > > Or, if there is some sort of ``address'' associated with this service, > you might define a special sort of address which, when configured on > the interface, causes the special behavior to happen. > Maybe I should just explain how IPX type 20 packets work. It is mostly used by Netbios and other protocols that don't understand the idea of a router. A IPX protocol type 20 packet will be broadcast by all IPX routers for 8 hops far. It has a field with space for 8 IPX network addresses and every router add the network address of his receiving interface there. Before it transmits a packet it must check that the network address of the destination net is not in the list. That is how loops are controlled. Pretty ugly to your bandwidth. That is why you must be able to switch it of for certain interfaces. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Sun Apr 21 05:58:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA17001 for hackers-outgoing; Sun, 21 Apr 1996 05:58:17 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA16996 for ; Sun, 21 Apr 1996 05:58:15 -0700 (PDT) Received: from max7-137.HiWAAY.net by fly.HiWAAY.net; (5.65v3.0/1.1.8.2/21Sep95-1003PM) id AA20283; Sun, 21 Apr 1996 07:58:00 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 21 Apr 1996 07:58:08 -0500 To: "Jonathan M. Bresler" , peter@taronga.com (Peter da Silva) From: dkelly@hiwaay.net (David Kelly) Subject: Re: Archive Anaconda on 1540B -- waiting forever for tape to become ready Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:16 PM 4/20/96, Jonathan M. Bresler wrote: > is this a brand new blank tape? never before used? > if so you have to "force" the tape. try "mt -f /dev/rst0 fsf 1" > for me that results in > "st0(ncr1:4:0): HARDWARE FAILURE info:1 asc:80,8a" > but afterward mt operations work! I also just installed an Anaconda tape drive but haven't had any problems like the above. Am running -stable patched thru 0074. Put the tape on ID 6, my 2G Barracuda is on ID 0. Per Richard J Kuhns 's advice I jumped jp6 (documented as "reserved") without ever trying it unjumped. System is a NexGen PCI-90 with Adaptec 2940. What bugs me a little is the tape drive doesn't continuously spool during dump (or tar). Several times it stopped for a second or two. Eventually dump asked me to insert the next tape. No way, 1.35G tape, 500M fs, I aborted. Looks like I've got to teach dump how big the tape is, or figure out how to get dump to run until it reaches the end of tape, or maybe dump was using 512 byte blocks? So for fun I did: "tar -cv /usr /usr1" which is about 1G, and ran to completion. Then used dd to read the tape to /dev/null and got an outrageous data rate reported but a sane byte count. This needs more experimentation. -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net ============================================================= To invent, you need a good imagination and a pile of junk. - Thomas Edison From owner-freebsd-hackers Sun Apr 21 06:27:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA18311 for hackers-outgoing; Sun, 21 Apr 1996 06:27:06 -0700 (PDT) Received: from pancake.remcomp.fr (root@pancake.remcomp.fr [194.51.30.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA18302 for ; Sun, 21 Apr 1996 06:27:00 -0700 (PDT) Received: from aida (localhost [127.0.0.1]) by aida (8.6.11/8.6.9) with SMTP id KAA00395; Sat, 20 Apr 1996 10:26:52 +0200 Date: Sat, 20 Apr 1996 10:26:52 +0200 (MET DST) From: didier@aida.org To: Terry Lambert cc: dennis , hackers@FreeBSD.ORG Subject: Re: AMD '586 Any opinions? In-Reply-To: <199604192041.NAA08937@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Apr 1996, Terry Lambert wrote: > > > > Good, bad, ugly? > > > > Ugly (no math). what do you mean by "no math" > > A: "But you don't need math" > > B: "But you don't need JNE, if you have JEQ -- it's just bloody > convenient" > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Didier Derny | Microsoft Free Computer. | AM586-160 ASUS PVI 486SP3 didier@aida.org | Private FreeBSD 2.1-STABLE site. | aha2940 / 1Gb HAWK From owner-freebsd-hackers Sun Apr 21 06:51:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA19128 for hackers-outgoing; Sun, 21 Apr 1996 06:51:31 -0700 (PDT) Received: from ledoux.arbld.unimelb.EDU.AU (ledoux.arbld.unimelb.EDU.AU [128.250.133.13]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA19123 for ; Sun, 21 Apr 1996 06:51:28 -0700 (PDT) Received: (from uucp@localhost) by ledoux.arbld.unimelb.EDU.AU (8.6.12/8.6.12) id XAA26730 for ; Sun, 21 Apr 1996 23:51:26 +1000 Received: from vitruvius.arbld.unimelb.edu.au(128.250.136.1) by ledoux.arbld.unimelb.EDU.AU via smap (V1.3) id sma026726; Sun Apr 21 23:51:05 1996 Received: (from darrenr@localhost) by vitruvius.arbld.unimelb.EDU.AU (8.6.12/8.6.12) id XAA10529 for hackers@freebsd.org; Sun, 21 Apr 1996 23:51:03 +1000 From: Darren Reed Message-Id: <199604211351.XAA10529@vitruvius.arbld.unimelb.EDU.AU> Subject: one less checksum ? (fwd) To: hackers@freebsd.org Date: Sun, 21 Apr 1996 23:51:03 +1000 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there any reason why the result of in_cksum() is stored in ip_sum in ipintr() ? A small gain can be observed if this is not done, for forwarded packets, by altering the checksum in ip_output() if IP_FORWARDING is set rather than recalculating the entire header checksum. Is this worthwhile ? darren *** ip_input.c.orig Wed Sep 6 20:31:35 1995 --- ip_input.c Sun Apr 21 12:12:53 1996 *************** *** 197,204 **** } ip = mtod(m, struct ip *); } ! ip->ip_sum = in_cksum(m, hlen); ! if (ip->ip_sum) { ipstat.ips_badsum++; goto bad; } --- 201,207 ---- } ip = mtod(m, struct ip *); } ! if (in_cksum(m, hlen)) { ipstat.ips_badsum++; goto bad; } *** ip_output.c.orig Wed Sep 6 20:31:40 1995 --- ip_output.c Sun Apr 21 19:41:53 1996 *************** *** 319,326 **** if ((u_short)ip->ip_len <= ifp->if_mtu) { ip->ip_len = htons((u_short)ip->ip_len); ip->ip_off = htons((u_short)ip->ip_off); ! ip->ip_sum = 0; ! ip->ip_sum = in_cksum(m, hlen); error = (*ifp->if_output)(ifp, m, (struct sockaddr *)dst, ro->ro_rt); goto done; --- 338,352 ---- if ((u_short)ip->ip_len <= ifp->if_mtu) { ip->ip_len = htons((u_short)ip->ip_len); ip->ip_off = htons((u_short)ip->ip_off); ! if (flags & IP_FORWARDING) { ! u_long sum = (u_long)ip->ip_sum; ! sum++; ! sum += (sum >> 16); ! ip->ip_sum = (u_short)(sum & 0x0000ffff); ! } else { ! ip->ip_sum = 0; ! ip->ip_sum = in_cksum(m, hlen); ! } error = (*ifp->if_output)(ifp, m, (struct sockaddr *)dst, ro->ro_rt); goto done; From owner-freebsd-hackers Sun Apr 21 07:17:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA19962 for hackers-outgoing; Sun, 21 Apr 1996 07:17:14 -0700 (PDT) Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA19954 for ; Sun, 21 Apr 1996 07:17:11 -0700 (PDT) Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id IAA22518; Sun, 21 Apr 1996 08:17:15 -0500 (CDT) Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id IAA06194; Sun, 21 Apr 1996 08:15:38 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199604211315.IAA06194@bonkers.taronga.com> Subject: Re: Archive Anaconda To: dkelly@hiwaay.net (David Kelly) Date: Sun, 21 Apr 1996 08:15:37 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: from "David Kelly" at Apr 21, 96 07:58:08 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I rebooted and it's working now, at least on that cartridge. The problem now is that I did a "tar /" to it and only got 412057600 bytes before EOF, which bothers me. It reported an unrecovered error: Apr 21 03:42:39 bonkers /kernel: st0(aha0:5:0): MEDIUM ERROR info:2b8 asc:c,0 Write error Apr 21 03:42:39 bonkers /kernel: st0(aha0:5:0): MEDIUM ERROR asc:c,0 Write error David Kelly writes: > This needs more experimentation. Indeed. Maybe I'll see what it does with 525M cartridges. From owner-freebsd-hackers Sun Apr 21 08:18:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA22251 for hackers-outgoing; Sun, 21 Apr 1996 08:18:39 -0700 (PDT) Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA22241 for ; Sun, 21 Apr 1996 08:18:34 -0700 (PDT) Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id JAA27330 for hackers@freebsd.org; Sun, 21 Apr 1996 09:49:08 -0500 (CDT) Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id JAA07239; Sun, 21 Apr 1996 09:44:26 -0500 Date: Sun, 21 Apr 1996 09:44:26 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199604211444.JAA07239@bonkers.taronga.com> To: hackers@freebsd.org Subject: Re: Lesstif (motif compatible) package. Newsgroups: taronga.freebsd.hackers References: <9009.829270330@time.cdrom.com> Organization: none Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Marc Ramirez wrote: >GUI builders help interface design the same way WYSIWYG word processors >help document design: you can see mistakes as soon as you make them. I don't like "what you see is all you get" word processors either. You end up having to do a bunch of low level screwing around anyway, unless you want to implement your overall document style by doing a bunch of point and click stuff over and over again, and it's hard to share style sheets and the like. If I ever found a GUI builder that was good for more than "properties boxes" and a word processor that's good for more than memos maybe I'd change my tune. I'm still waiting. From owner-freebsd-hackers Sun Apr 21 08:24:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA22465 for hackers-outgoing; Sun, 21 Apr 1996 08:24:18 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA22459 for ; Sun, 21 Apr 1996 08:24:12 -0700 (PDT) Received: from max2-181.HiWAAY.net by fly.HiWAAY.net; (5.65v3.0/1.1.8.2/21Sep95-1003PM) id AA23796; Sun, 21 Apr 1996 10:24:04 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 21 Apr 1996 10:24:09 -0500 To: peter@taronga.com (Peter da Silva) From: dkelly@hiwaay.net (David Kelly) Subject: Re: Archive Anaconda Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I rebooted and it's working now, at least on that cartridge. > >The problem now is that I did a "tar /" to it and only got 412057600 bytes >before EOF, which bothers me. It reported an unrecovered error: > >Apr 21 03:42:39 bonkers /kernel: st0(aha0:5:0): MEDIUM ERROR info:2b8 >asc:c,0 Write error Apr 21 03:42:39 bonkers /kernel: st0(aha0:5:0): MEDIUM >ERROR asc:c,0 Write error > >David Kelly writes: >> This needs more experimentation. > >Indeed. Maybe I'll see what it does with 525M cartridges. I wonder if tar and/or dump and/or dd default to the 512 byte blocksize reported by mt? Tried a simple "dd if=/dev/tape of=/dev/null" and the tape hunted back and forth, back and forth. But when I added "bs=10k" is spooled all the way thru the tape. How do we determine what blocksize a tape was written with? -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net ============================================================= To invent, you need a good imagination and a pile of junk. - Thomas Edison From owner-freebsd-hackers Sun Apr 21 08:57:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23592 for hackers-outgoing; Sun, 21 Apr 1996 08:57:27 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23586 Sun, 21 Apr 1996 08:57:25 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199604211557.IAA23586@freefall.freebsd.org> Subject: Re: Archive Anaconda To: dkelly@hiwaay.net (David Kelly) Date: Sun, 21 Apr 1996 08:57:25 -0700 (PDT) Cc: peter@taronga.com, hackers@freebsd.org In-Reply-To: from "David Kelly" at Apr 21, 96 10:24:09 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Kelly wrote: > > I wonder if tar and/or dump and/or dd default to the 512 byte blocksize > reported by mt? Tried a simple "dd if=/dev/tape of=/dev/null" and the tape > hunted back and forth, back and forth. But when I added "bs=10k" is spooled > all the way thru the tape. > > How do we determine what blocksize a tape was written with? > tar uses the native blcksize of the device. dd defaults to 512 byte blocks dump defaults to 10240 bytes per record in 10 blocks ;) there is an interblock gap (ala interframe gap on the network-- no stones, please.) between the records/blocks. the gap is needed but its just dead tape. a larger block size minimizies this wastage. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ From owner-freebsd-hackers Sun Apr 21 09:22:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24570 for hackers-outgoing; Sun, 21 Apr 1996 09:22:51 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24563 Sun, 21 Apr 1996 09:22:50 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199604211622.JAA24563@freefall.freebsd.org> Subject: Re: Archive Anaconda on 1540B -- waiting forever for tape to become ready To: dkelly@hiwaay.net (David Kelly) Date: Sun, 21 Apr 1996 09:22:49 -0700 (PDT) Cc: peter@taronga.com, hackers@freebsd.org In-Reply-To: from "David Kelly" at Apr 21, 96 07:58:08 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Kelly wrote: > > At 10:16 PM 4/20/96, Jonathan M. Bresler wrote: > > is this a brand new blank tape? never before used? > > if so you have to "force" the tape. try "mt -f /dev/rst0 fsf 1" > > for me that results in > > "st0(ncr1:4:0): HARDWARE FAILURE info:1 asc:80,8a" > > but afterward mt operations work! > > I also just installed an Anaconda tape drive but haven't had any problems > like the above. Am running -stable patched thru 0074. Put the tape on ID 6, > my 2G Barracuda is on ID 0. Per Richard J Kuhns > 's advice I jumped jp6 (documented as "reserved") > without ever trying it unjumped. jumper 6 is the scsi-1 (open) vs scis-2 (shorted) jumper. > System is a NexGen PCI-90 with Adaptec 2940. > > What bugs me a little is the tape drive doesn't continuously spool during > dump (or tar). Several times it stopped for a second or two. Eventually > dump asked me to insert the next tape. No way, 1.35G tape, 500M fs, I > aborted. Looks like I've got to teach dump how big the tape is, or figure > out how to get dump to run until it reaches the end of tape, or maybe dump > was using 512 byte blocks? be sure to distinguish between the initial tape motions which do some sort of setup activity and the tape motion during data transfer. the drive seeks back and forth several times before it begins to move data. once the data starts moving the drive will stream till (the end of a block ??) and then seek back a couple times. between the seeks there may/will be a short pause. use dump with the 'B' arg for example "/sbin/dump 0unBbf 1200000 10 /dev/nrst0 /dev/sd1a" B - number of dump records per volume (unlimited: 32 bit signed) (a volume is the amount of data you choose to store on each tape, that is B == "number of blocks per file") b - number of kilobytes per dump record (1 - 1000) dump makes some guesses about tape size that date from the days of 9 track tapes. so you have to educate dump about the drive's capacity. > > So for fun I did: "tar -cv /usr /usr1" which is about 1G, and ran to > completion. Then used dd to read the tape to /dev/null and got an > outrageous data rate reported but a sane byte count. This needs more > experimentation. OUTPUT TEST: Aspen:[201] dd if=/dev/zero of=/dev/rst0 bs=1048576 count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2051 secs (523521 bytes/sec) -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ From owner-freebsd-hackers Sun Apr 21 09:43:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA25167 for hackers-outgoing; Sun, 21 Apr 1996 09:43:11 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA25162 for ; Sun, 21 Apr 1996 09:43:09 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id MAA00212; Sun, 21 Apr 1996 12:40:46 -0400 (EDT) Date: Sun, 21 Apr 1996 12:40:46 -0400 (EDT) From: Kim Culhan To: hackers@FreeBSD.org Subject: screen saver boot complaint fixed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Thanks to all responders, this -current machine doesn't complain about the screensaver on boot. In rc.i386 line 103: change: saver_init -q /lkm/${saver}_saver_mod.o to: ${saver}_saver_mod -q /lkm/${saver}_saver_mod.o kim -- kimc@w8hd.org From owner-freebsd-hackers Sun Apr 21 10:05:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA25865 for hackers-outgoing; Sun, 21 Apr 1996 10:05:49 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA25860 for ; Sun, 21 Apr 1996 10:05:47 -0700 (PDT) Received: from max7-201.HiWAAY.net by fly.HiWAAY.net; (5.65v3.0/1.1.8.2/21Sep95-1003PM) id AA30863; Sun, 21 Apr 1996 12:05:39 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 21 Apr 1996 12:05:44 -0500 To: "Jonathan M. Bresler" From: dkelly@hiwaay.net (David Kelly) Subject: Re: Archive Anaconda Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:57 AM 4/21/96, Jonathan M. Bresler wrote: > tar uses the native blcksize of the device. Is this the native block size the value reported by "mt stat"? > there is an interblock gap (ala interframe gap on the network-- > no stones, please.) between the records/blocks. the gap is > needed but its just dead tape. a larger block size minimizies > this wastage. Yes, and I understand this gap is larger if the tape can't spool. The rewind/restart process writes a longer gap, rewinds, then when it has data to write starts forward, reads the gap flags and resumes writing over the top of the tail of the gap. It bugs me that my 2940 and Barracuda don't seem to be able to keep the Anaconda completely busy. There are pauses while writing that are not due to the tape reversing to write the next track. The start of a tar write has many of these little starts and stops, then it seems to run about 20 seconds between instances but with no particular pattern. -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net ============================================================= To invent, you need a good imagination and a pile of junk. - Thomas Edison From owner-freebsd-hackers Sun Apr 21 12:51:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA02875 for hackers-outgoing; Sun, 21 Apr 1996 12:51:21 -0700 (PDT) Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA02861 for ; Sun, 21 Apr 1996 12:51:16 -0700 (PDT) Received: (from uucp@localhost) by perki.connect.com.au id FAA12254 (8.7.5/IDA-1.6); Mon, 22 Apr 1996 05:51:02 +1000 (EST) >Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id QAA11059; Sun, 21 Apr 1996 16:09:49 +1000 Message-Id: <199604210609.QAA11059@nemeton.com.au> To: John Fieber cc: hackers@freefall.freebsd.org Subject: Re: cvs commit: ports/net Makefile ports/net/dhcp Makefile ports/net/ivs Makefile ports/net/wais Makefile Date: Sun, 21 Apr 1996 16:09:48 +1000 From: Giles Lean Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Apr 1996 09:00:10 -0500 (EST) John Fieber wrote: > The other option is FreeWAIS-sf. Last version I used, which runs > the mailing list archives on http://www.freebsd.org, is a little > buggy. That was around patch level 40. I think it is around 65 > now. (I condolances to any porter who tries to follow this > package!) Version 65 is more than a little buggy. It core dumps on its test code, never mind serious data. Painful to build, too. Stay away! Let me know when/if the Isite package stabilises (or sing out for help :) and I'll see about plugging it into the revised mail robot. Regards, Giles From owner-freebsd-hackers Sun Apr 21 13:31:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05019 for hackers-outgoing; Sun, 21 Apr 1996 13:31:35 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05012 for ; Sun, 21 Apr 1996 13:31:28 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id WAA29029; Sun, 21 Apr 1996 22:26:10 +0200 From: Luigi Rizzo Message-Id: <199604212026.WAA29029@labinfo.iet.unipi.it> Subject: Re: one less checksum ? (fwd) To: darrenr@vitruvius.arbld.unimelb.edu.au (Darren Reed) Date: Sun, 21 Apr 1996 22:26:10 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199604211351.XAA10529@vitruvius.arbld.unimelb.EDU.AU> from "Darren Reed" at Apr 21, 96 11:50:44 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there any reason why the result of in_cksum() is stored in ip_sum in > ipintr() ? > > A small gain can be observed if this is not done, for forwarded packets, > by altering the checksum in ip_output() if IP_FORWARDING is set rather > than recalculating the entire header checksum. Is this worthwhile ? TCP/IP Illustrated vol.1 suggests something similar, so I'd say it is worthwhile. Garret Wollman should be looking after this code right in these days. But I don't understand how you relate your code (which looks correct) with the above comment. It looks like your code is computing the checksum in the same place, just with a more efficient algorithm. The same code fragments suggest some more optimizations when if_forwarding is enabled, e.g. don't convert header fields (ip_len and ip_off) for back and forth from network format. Luigi From owner-freebsd-hackers Sun Apr 21 13:37:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05475 for hackers-outgoing; Sun, 21 Apr 1996 13:37:37 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05442 for ; Sun, 21 Apr 1996 13:37:22 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26347; Sun, 21 Apr 1996 22:36:52 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00278; Sun, 21 Apr 1996 22:36:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA14779; Sun, 21 Apr 1996 20:24:08 +0200 (MET DST) From: J Wunsch Message-Id: <199604211824.UAA14779@uriah.heep.sax.de> Subject: Re: Archive Anaconda To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 21 Apr 1996 20:24:07 +0200 (MET DST) Cc: dkelly@hiwaay.net (David Kelly) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "David Kelly" at Apr 21, 96 10:24:09 am X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Kelly wrote: > How do we determine what blocksize a tape was written with? By reading one byte, and watching the error message on the console. j@uriah 161% dd if=/dev/rst0 ibs=1 count=1 of=/dev/null dd: /dev/rst0: Input/output error 0+0 records in 0+0 records out 0 bytes transferred in 2 secs (0 bytes/sec) Apr 21 20:23:10 uriah /kernel: st0: 32768-byte record too big Apr 21 20:23:10 uriah /kernel: st0: 32768-byte record too big :-) -- 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 Apr 21 13:37:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05516 for hackers-outgoing; Sun, 21 Apr 1996 13:37:43 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05476 for ; Sun, 21 Apr 1996 13:37:38 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26376 for ; Sun, 21 Apr 1996 22:37:27 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00298 for freebsd-hackers@freebsd.org; Sun, 21 Apr 1996 22:37:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA15201 for freebsd-hackers@freebsd.org; Sun, 21 Apr 1996 21:30:38 +0200 (MET DST) From: J Wunsch Message-Id: <199604211930.VAA15201@uriah.heep.sax.de> Subject: Re: fingerd To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 21 Apr 1996 21:30:38 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Peter Wemm" at Apr 21, 96 02:55:07 am X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Peter Wemm wrote: > Try this: env TZ=Australia/Perth date > Naturally, this assumes your local timezone is correctly set. :-) ...and your Peter's finger entry reporting that he lives in TZ=Australia/Perth. ;-) -- 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 Apr 21 13:37:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05596 for hackers-outgoing; Sun, 21 Apr 1996 13:37:55 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05493 Sun, 21 Apr 1996 13:37:40 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26388; Sun, 21 Apr 1996 22:37:37 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00302; Sun, 21 Apr 1996 22:37:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA15294; Sun, 21 Apr 1996 21:43:42 +0200 (MET DST) From: J Wunsch Message-Id: <199604211943.VAA15294@uriah.heep.sax.de> Subject: Re: ipcp loop To: fyeung@fyeung5.netific.com (francis yeung) Date: Sun, 21 Apr 1996 21:43:41 +0200 (MET DST) Cc: questions@freebsd.org, hackers@freebsd.org, fyeung@fyeung5.netific.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604192314.XAA10011@fyeung5.netific.com> from "francis yeung" at Apr 19, 96 11:14:37 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As francis yeung wrote: > 07-11 07:14:34 [154] IPCP: state change Initial --> Closed > 07-11 07:14:34 [154] IPCP Up event!! > 07-11 07:14:34 [154] IPCP: SendConfigReq > 07-11 07:14:34 [154] IPADDR [6] 192.0.0.1 > 07-11 07:14:34 [154] COMPPROTO [6] 002d0f00 > 07-11 07:14:34 [154] IPCP: state change Closed --> Req-Sent ... > 07-11 07:14:37 [154] IPCP: Received Configure Request (3) state = Req-Sent (6) > 07-11 07:14:37 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:37 [154] IPCP: SendConfigAck(Req-Sent) > 07-11 07:14:37 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:37 [154] IPCP: state change Req-Sent --> Ack-Sent > 07-11 07:14:40 [154] IPCP: Received Configure Request (4) state = Ack-Sent (8) > 07-11 07:14:40 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:40 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:40 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:43 [154] IPCP: Received Configure Request (5) state = Ack-Sent (8) > 07-11 07:14:43 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:43 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:43 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:46 [154] IPCP: Received Configure Request (6) state = Ack-Sent (8) > 07-11 07:14:46 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:46 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:46 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:49 [154] IPCP: Received Configure Request (7) state = Ack-Sent (8) > 07-11 07:14:49 [154] IPADDR[6] 168.95.127.222 > > ... > > It seems to me that there was an IPCP collision and Xylogics never ack'd > iijppp's SendConfigAck(Ack-sent). > > Is this a ijjppp problem or a Xylogics problem ? This looks like a Xylogics problem, but you cannot be sure until you've also seen the logs from the remote peer. The above looks like iijppp is flooded with config request that are properly acknowledged. The requested 192.0.0.1 address is arguably bogus (and we've been there with the author of iijppp, if i remember well), however the Xylogics should simply NAK it and come up with its own suggestion. -- 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 Apr 21 13:56:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA06872 for hackers-outgoing; Sun, 21 Apr 1996 13:56:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA06866 for ; Sun, 21 Apr 1996 13:56:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA15868; Sun, 21 Apr 1996 13:51:36 -0700 From: Terry Lambert Message-Id: <199604212051.NAA15868@phaeton.artisoft.com> Subject: Re: AMD '586 Any opinions? To: didier@aida.org Date: Sun, 21 Apr 1996 13:51:36 -0700 (MST) Cc: terry@lambert.org, dennis@etinc.com, hackers@FreeBSD.ORG In-Reply-To: from "didier@aida.org" at Apr 20, 96 10:26:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Ugly (no math). > > what do you mean by "no math" Never mind; apparently, there's a version that has a math coprocessor now; there didn't used to be. Just make sure you get the right 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 Sun Apr 21 14:46:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09035 for hackers-outgoing; Sun, 21 Apr 1996 14:46:32 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA09030 for ; Sun, 21 Apr 1996 14:46:30 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id RAA19927; Sun, 21 Apr 1996 17:44:06 -0400 (EDT) Date: Sun, 21 Apr 1996 17:44:06 -0400 (EDT) From: Kim Culhan To: hackers@freebsd.org Subject: -current build failure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Current from about 1600 UTC this date (4/21) failed: cc -O -D__BSD__ -c /usr/src/gnu/usr.bin/mkisofs/hash.c cc -O -D__BSD__ -c /usr/src/gnu/usr.bin/mkisofs/rock.c /usr/src/gnu/usr.bin/mkisofs/rock.c:531: parse error at null character *** Error code 1 Any help muchly appreciated. regards kim -- kimc@w8hd.org From owner-freebsd-hackers Sun Apr 21 14:51:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09367 for hackers-outgoing; Sun, 21 Apr 1996 14:51:54 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA09362 for ; Sun, 21 Apr 1996 14:51:52 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id RAA19957; Sun, 21 Apr 1996 17:49:28 -0400 (EDT) Date: Sun, 21 Apr 1996 17:49:28 -0400 (EDT) From: Kim Culhan To: hackers@FreeBSD.org Subject: more -current build failure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk /usr/src/gnu/usr.bin/mkisofs/rock.c looks like: pnt = (char *) e_malloc(SECTOR_SIZE); memset(pnt, 0, SECTOR_SIZE); memcpy(pnt, Rock, ipnt); *size = ipnt; return pnt; } ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ The above series of characters begins on line 531 and repeats a few hundred to the end of the file. kim -- kimc@w8hd.org From owner-freebsd-hackers Sun Apr 21 15:07:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA10427 for hackers-outgoing; Sun, 21 Apr 1996 15:07:26 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA10422 for ; Sun, 21 Apr 1996 15:07:23 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id SAA26261; Sun, 21 Apr 1996 18:04:59 -0400 (EDT) Date: Sun, 21 Apr 1996 18:04:59 -0400 (EDT) From: Kim Culhan To: hackers@FreeBSD.org Subject: -current has typo in makefile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk There is this typo: ===> usr.sbin/sendmail/shmrsh cd: can't cd to /usr/src/usr.sbin/sendmail/shmrsh regards kim -- kimc@w8hd.org From owner-freebsd-hackers Sun Apr 21 16:21:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA16672 for hackers-outgoing; Sun, 21 Apr 1996 16:21:51 -0700 (PDT) Received: from lenzi (calla.bsi.com.br [200.250.250.71]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA16648 for ; Sun, 21 Apr 1996 16:21:33 -0700 (PDT) Received: (from lenzi@localhost) by lenzi (8.6.12/8.6.12) id RAA00208; Sun, 21 Apr 1996 17:22:34 -0300 Date: Sun, 21 Apr 1996 17:22:33 -0300 (EST) From: "Lenzi, Sergio" X-Sender: lenzi@lenzi To: Lars Jonas Olsson cc: hackers@freebsd.org Subject: Re: 56kbps hardware? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Apr 1996, Lars Jonas Olsson wrote: > The company I work for needs Internet access. I have been looking at > 56kbps access using poinmt to point or frame relay. I use an (assyc) v34 microcom mnp10 modems attached to a leased line and at the com2 port (0x2f8) at 57.600bps. I use pppd for the sofware. I have been happy with this configuration. I have setup 4 instalations using this configuration > > What hardware is recommended when using a FreeBSD server? My > plan is to use a CSU/DSU connected to the PC, and the PC being > the firewall. Is an external router preferable? I use a 486DX2-66 or DX4-100 or DX2-80 using the modem on com2 and an ethernet ne2000 for local lan. I setup a static route and subnet mask according to the number of pc conected to the other side of the internet provider (I use 0xfffffff0 as netmask). Works fine (my ping time is 150ms) between the isp and the other peer. > > Jonas > > AccuMed International. > > From owner-freebsd-hackers Sun Apr 21 17:18:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23528 for hackers-outgoing; Sun, 21 Apr 1996 17:18:02 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA23515 Sun, 21 Apr 1996 17:17:58 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id LAA18166; Sun, 21 Apr 1996 11:02:12 -0700 (PDT) Message-Id: <199604211802.LAA18166@ref.tfs.com> Subject: Re: ipcp loop To: fyeung@fyeung5.netific.com (francis yeung) Date: Sun, 21 Apr 1996 11:02:12 -0700 (PDT) From: "JULIAN Elischer" Cc: questions@freebsd.org, hackers@freebsd.org, fyeung@fyeung5.netific.com In-Reply-To: <199604192314.XAA10011@fyeung5.netific.com> from "francis yeung" at Apr 19, 96 11:14:37 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get something similar also on a 2.1 machine connecting to a cisco terminal server.. > > > > 07-11 07:14:40 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:40 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:40 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:43 [154] IPCP: Received Configure Request (5) state = Ack-Sent (8) > 07-11 07:14:43 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:43 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:43 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:46 [154] IPCP: Received Configure Request (6) state = Ack-Sent (8) > 07-11 07:14:46 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:46 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:46 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:49 [154] IPCP: Received Configure Request (7) state = Ack-Sent (8) > 07-11 07:14:49 [154] IPADDR[6] 168.95.127.222 > +----------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / On assignment | / \ julian@tfs.com +------>x USA \ in a very strange | ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country ! +- X_.---._/ USA+(510) 645-3137(wk) \_/ \\ > v LL LL From owner-freebsd-hackers Sun Apr 21 18:11:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA27833 for hackers-outgoing; Sun, 21 Apr 1996 18:11:46 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA27828 for ; Sun, 21 Apr 1996 18:11:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA16322; Sun, 21 Apr 1996 18:08:28 -0700 From: Terry Lambert Message-Id: <199604220108.SAA16322@phaeton.artisoft.com> Subject: Re: HP Vectra VL Series 4 To: mihoko@sapphire.pa.yokogawa.co.jp (Mihoko Tanaka) Date: Sun, 21 Apr 1996 18:08:27 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199604210525.OAA25877@sapphire.pa.yokogawa.co.jp> from "Mihoko Tanaka" at Apr 21, 96 02:25:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I guess that the PCI bus isn't recognize if the number of function > is not equal 0 (in another words, if the PCI bridge is the > multi-function device). > > I tried to change the mask 'CONF1_ENABLE_MSK from '0x00ff0700ul' to > '0x00ff0000ul', and it works well. > But I'm worrying if my change is correct. > > Please give me some advices. [ ... ] You need to send this directly to Stefan Esser, se@zpr.uni-koeln.de who is the main PCI person; he said recently that he does not read this list. 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 Apr 21 20:20:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA04477 for hackers-outgoing; Sun, 21 Apr 1996 20:20:20 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA04471 for ; Sun, 21 Apr 1996 20:20:13 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.12/8.6.12) id XAA08263 for freebsd-hackers@freebsd.org; Sun, 21 Apr 1996 23:20:11 -0400 From: Charles Henrich Message-Id: <199604220320.XAA08263@crh.cl.msu.edu> Subject: .forward and sendmail? To: freebsd-hackers@freebsd.org Date: Sun, 21 Apr 1996 23:20:11 -0400 (EDT) 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Explain to me how exactly sendmail is supposed to read .forward's out of peoples directories, when it apparently runs as daemon? I have had zero luck with this unless the directories are world read, as well as the .forward, this is unusual! What am I missing here? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sun Apr 21 21:35:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA07469 for hackers-outgoing; Sun, 21 Apr 1996 21:35:37 -0700 (PDT) Received: from deimos.frii.com (deimos.frii.com [204.144.241.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA07462 for ; Sun, 21 Apr 1996 21:35:35 -0700 (PDT) Received: (from jfrancis@localhost) by deimos.frii.com (8.6.12/8.6.9) id WAA06308 for freebsd-hackers@FreeBSD.ORG; Sun, 21 Apr 1996 22:32:44 -0600 From: "G. Jeffrey Francis" Message-Id: <199604220432.WAA06308@deimos.frii.com> Subject: Device Driver ioctl() help To: freebsd-hackers@FreeBSD.ORG Date: Sun, 21 Apr 1996 22:32:43 -0600 (MDT) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've written a device driver to talk to a JDR experimenter's breadboard that works quite well, but now I want to add some more functionality to the driver, and I'm running into problems understanding BSD's ioctl() mechanism. I'll use the joy.c driver as an example of the problem I'm having. In /sys/i386/include/joystick.h is the following code: ... blah blah blah... #define JOY_SETTIMEOUT _IOW('J', 1, int) /* set timeout */ ... blah blah blah... In /sys/sys/ioccom.h is this code: ... blah blah blah... #define _IOC(inout,group,num,len) \ (inout | ((len & IOCPARM_MASK) << 16) | ((group) << 8) | (num)) ... blah blah blah... #define _IOW(g,n,t) _IOC(IOC_IN, (g), (n), sizeof(t)) ... blah blah blah... Ok, it looks like the 'J' has something to do with a "group", but what kind of group? How is this value chosen and what does it do? I can reliably open() my device, issue an ioctl(), and things happen (as confirmed by printf() statements in the driver), but I'm not able to actually pass any data to or from the driver's ioctl() function from my user-level code (the probe(), attach(), read(), write(), open(), and close() routines all work just dandy). In my user-level code, I can call `ioctl(fd,STUFF,0x69)'. In the driver, the `case STUFF:' code in the `switch(cmd)' statement gets executed (usually, but why not always?), but I can't get at the value passed (0x69 in this case). Obviously I'm missing something, but none of the kernel books I have tell me what, and I can't seem to sort it out. I'd be happy to post actual code fragments if it would help. +---------+------------------------------+--------------------------+---------+ | | Jeff Francis | | | | (__) | Network Specialist | We are smart. | (__) | | /( oo | Paranet - Denver, CO | | /( oo | | /\_| | jfrancis@mail.frii.com | We make things go. | /\_| | | | Powered by FreeBSD & Mtn Dew | | | +---------+------------------------------+--------------------------+---------+ From owner-freebsd-hackers Sun Apr 21 22:43:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA11974 for hackers-outgoing; Sun, 21 Apr 1996 22:43:12 -0700 (PDT) Received: from gateway.zeus.leitch.com (gateway.zeus.leitch.com [205.210.38.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA11965 for ; Sun, 21 Apr 1996 22:42:52 -0700 (PDT) Received: from tap.zeus.leitch.com (tap.zeus.leitch.com [204.187.60.10]) by gateway.zeus.leitch.com (8.6.12/8.6.9) with ESMTP id BAA16333; Mon, 22 Apr 1996 01:54:28 -0400 Received: (from dchapes@localhost) by tap.zeus.leitch.com (8.6.12/8.6.6) id BAA01869; Mon, 22 Apr 1996 01:43:03 -0400 From: Dave Chapeskie Message-Id: <199604220543.BAA01869@tap.zeus.leitch.com> Subject: Device Driver ioctl() help To: jfrancis@frii.com Date: Mon, 22 Apr 1996 01:43:03 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199604220432.WAA06308@deimos.frii.com> X-Mailer: ELM [version 2.4ME+ PL14 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199604220432.WAA06308@deimos.frii.com> jfrancis@frii.com writes: >#define JOY_SETTIMEOUT _IOW('J', 1, int) /* set timeout */ [...] > Ok, it looks like the 'J' has something to do with a "group", >but what kind of group? How is this value chosen and what does it do? Get a good book on writing device drivers. Typically you just use group 0 unless you know what you're doing. _IO is used when no data is needed; _IOR when you need data returned from the driver; _IOW when you want data passed into the driver; and _IOWR to pass the data both ways. > In my user-level code, I can call `ioctl(fd,STUFF,0x69)'. In Ack!! RTFM, ioctl's third argument is a pointer. ie: header: #define MYDEV_CMD1 _IOW(0,1,int) user code: int arg = 42; ioctl(fd,MYDEV_CMD1,&arg) driver code: int mydev_ioctl(dev_t dev, int cmd, caddr_t data, int flags, struct proc *p) { switch(cmd) { case MYDEV_CMD1: if( *(int*)data == 42 ) .... >Obviously I'm missing something, but none >of the kernel books I have tell me what, and I can't seem to sort it >out. I think you need a better book. I can't recommend one at the moment since I'm not at work where my bookshelf is. -- Dave Chapeskie Leitch Technology International Inc. Email: dchapes@zeus.leitch.com From owner-freebsd-hackers Sun Apr 21 23:08:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA13376 for hackers-outgoing; Sun, 21 Apr 1996 23:08:28 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA13370 for ; Sun, 21 Apr 1996 23:08:25 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA09416; Mon, 22 Apr 1996 08:08:11 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA04252; Mon, 22 Apr 1996 08:08:11 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA17747; Mon, 22 Apr 1996 07:34:59 +0200 (MET DST) From: J Wunsch Message-Id: <199604220534.HAA17747@uriah.heep.sax.de> Subject: Re: more -current build failure To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 22 Apr 1996 07:34:58 +0200 (MET DST) Cc: kimc@w8hd.org (Kim Culhan) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Kim Culhan" at Apr 21, 96 05:49:28 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Kim Culhan wrote: > > /usr/src/gnu/usr.bin/mkisofs/rock.c looks like: > > pnt = (char *) e_malloc(SECTOR_SIZE); > memset(pnt, 0, SECTOR_SIZE); > memcpy(pnt, Rock, ipnt); > *size = ipnt; > return pnt; > } > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ > > The above series of characters begins on line 531 and repeats a few hundred > to the end of the file. Your file is damaged. My CVS master is okay, it hasn't been touched for ages (October 1995). You might have serious disk/controller problems. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Apr 21 23:08:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA13396 for hackers-outgoing; Sun, 21 Apr 1996 23:08:46 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA13391 for ; Sun, 21 Apr 1996 23:08:41 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA09420; Mon, 22 Apr 1996 08:08:13 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA04254; Mon, 22 Apr 1996 08:08:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA18025; Mon, 22 Apr 1996 07:44:28 +0200 (MET DST) From: J Wunsch Message-Id: <199604220544.HAA18025@uriah.heep.sax.de> Subject: Re: .forward and sendmail? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 22 Apr 1996 07:44:27 +0200 (MET DST) Cc: henrich@crh.cl.msu.edu (Charles Henrich) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604220320.XAA08263@crh.cl.msu.edu> from "Charles Henrich" at Apr 21, 96 11:20:11 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > Explain to me how exactly sendmail is supposed to read .forward's > out of peoples directories, when it apparently runs as daemon? I > have had zero luck with this unless the directories are world read, > as well as the .forward, this is unusual! What am I missing here? I think it must be readable by `daemon' (and i would even call this a security feature, as opposed to reading the file with root privileges). Of course, your directory doesn't need to be readable by `daemon', it's sufficient if it is _search_able by him (e.g.., drwxr-x--x). -- 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 Apr 22 01:47:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA22598 for hackers-outgoing; Mon, 22 Apr 1996 01:47:42 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA22593 Mon, 22 Apr 1996 01:47:34 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA26914; Mon, 22 Apr 1996 18:44:16 +1000 Date: Mon, 22 Apr 1996 18:44:16 +1000 From: Bruce Evans Message-Id: <199604220844.SAA26914@godzilla.zeta.org.au> To: dchapes@zeus.leitch.com, jfrancis@frii.com Subject: Re: Device Driver ioctl() help Cc: hackers@FreeBSD.org, hsu@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> In my user-level code, I can call `ioctl(fd,STUFF,0x69)'. In > Ack!! RTFM, ioctl's third argument is a pointer. `man ioctl' says that it is a pointer of type `char *', but this is yet another bug in the man pages, or perhaps in the system headers. says that the third arg is `...'. Some ioctls don't require it. The system assumes that the arg is a `void *'. Most applications probably pass an `int *' or a `struct foo *' and the change from `char *' to `...' broke these on systems where `int *' and `struct foo *' aren't like `char *' (no conversions occur for `...'). >ie: header: > #define MYDEV_CMD1 _IOW(0,1,int) >user code: > int arg = 42; > ioctl(fd,MYDEV_CMD1,&arg) ^^^^ one of "most applications" :-) >int >mydev_ioctl(dev_t dev, int cmd, caddr_t data, int flags, struct proc *p) ^^^^^^^ The `int *' has become a caddr_t via one bogus conversion, one copy operation and one non-bogus conversion. This is all hidden in the upper layers of ioctl() - drivers don't have to worry about it. >{ > switch(cmd) { > case MYDEV_CMD1: > if( *(int*)data == 42 ) ^^^^^^^ Drivers do have to worry about converting back to the original type of the data. Bruce From owner-freebsd-hackers Mon Apr 22 05:41:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA02155 for hackers-outgoing; Mon, 22 Apr 1996 05:41:44 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA02144 for ; Mon, 22 Apr 1996 05:40:51 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id TAA03782 for hackers@freebsd.org; Mon, 22 Apr 1996 19:40:13 +0700 Received: by itfs.nsk.su; Mon, 22 Apr 96 19:29:45 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.6.12/8.6.12) id TAA27986; Mon, 22 Apr 1996 19:23:50 +0700 From: nnd@itfs.nsk.su (Nickolay N. Dudorov) To: hackers@freebsd.org Subject: Re: ip-in-ip tunnel Message-ID: References: Date: Mon, 22 Apr 1996 12:23:46 GMT Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dirk Froemberg (dirk@methan.chemie.fu-berlin.de) wrote: > Hello! > > We need to set up a ip-in-ip (protocol number 4) tunnel with FreeBSD > (i. e. tunnel entry should be on a FreeBSD machine). > > Unfortunaly there seems to be no easy way of doing so. > > mrouting has the functionality of tunneling being limited on multicast > addresses. Although this limitation may easily be removed there > is no way of adding routes manually (e. g. route add). > > Another approach might be to create a interface doing the encapsulation. > The implementation of the ip-in-ip-encapsulation itself is not very > difficult. At the moment we are a stucked "a little bit" in the > BSD-networking-code. > > Btw. Linux has such interface called "tunl". > > Is anyone working on this? > I've send 'a problem report' with send-pr with example of program which configure tunN device as a point-to-point interface between this host and target one. It uses ip-over-ip encapsulation (protocol 94) - the same which is used by CISCO-routers (among others, they named it NOS-encapsulation) and (may be) Linux. N. Dudorov From owner-freebsd-hackers Mon Apr 22 06:53:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA05895 for hackers-outgoing; Mon, 22 Apr 1996 06:53:09 -0700 (PDT) Received: from rich.isdn.bcm.tmc.edu (root@RICH.ISDN.BCM.TMC.EDU [128.249.250.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA05883 for ; Mon, 22 Apr 1996 06:53:06 -0700 (PDT) Received: from richc.isdn.bcm.tmc.edu (root@richc.isdn.bcm.tmc.edu [128.249.250.37]) by rich.isdn.bcm.tmc.edu (8.7.5/8.6.12) with ESMTP id IAA03326; Mon, 22 Apr 1996 08:53:03 -0500 (CDT) Received: (rich@localhost) by richc.isdn.bcm.tmc.edu (8.7.5/8.6.12) id IAA13436; Mon, 22 Apr 1996 08:53:03 -0500 (CDT) Date: Mon, 22 Apr 1996 08:53:03 -0500 (CDT) Message-Id: <199604221353.IAA13436@richc.isdn.bcm.tmc.edu> From: Rich Murphey To: imp@village.org CC: hackers@freebsd.org In-reply-to: <199604210612.AAA24062@rover.village.org> (message from Warner Losh on Sun, 21 Apr 1996 00:12:03 -0600) Subject: Re: This is sick... Reply-to: rich@lamprey.utmb.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk |From: Warner Losh | |... But I'm doing a | |diff -ur /4.4lite/v1/4.4BSD-Lite/usr/src /4.4lite/v2/4.4BSD-Lite2/usr/src | |where both of the trees are cds mounted from my Nakamichi NBR-7. This |is running -stable of a few days ago. I recall that others were |having problems with this drive, but I've lost their names. It seems |stable enough for me, and I've had to install no special patches. |This is with the usual 486DX2-66, UltraStor 34F, 32M of memory. I've had lots of problems mouting 4 or more CDs on -stable with the MBR-7. The system hangs nightly even though there isn't any intentional simultaneous access in any of the cron scripts. I've got crash dumps from simultaneous access to CDs, but they haven't revealed the root of the problem. I seem to be the only one, so I suspect it that my Nakamichi drive's at fault. I'm told that accessing 2 CDs simultaneously is also very hard on the drive mechanisms. If you hear the drive making grinding noises during rapid CD changes you'll know what they mean. Rich From owner-freebsd-hackers Mon Apr 22 06:54:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA06060 for hackers-outgoing; Mon, 22 Apr 1996 06:54:08 -0700 (PDT) Received: from suw3svr01.hisd.harris.com (suw3svr01.hisd.harris.com [158.147.19.67]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA06051 for ; Mon, 22 Apr 1996 06:54:06 -0700 (PDT) Received: from suw2k.hisd.harris.com by suw3svr01.hisd.harris.com (SMI-8.6/SMI-SVR4) id JAA16836; Mon, 22 Apr 1996 09:51:06 -0400 Received: by suw2k.hisd.harris.com (4.1/SMI-4.1) id AA06758; Mon, 22 Apr 96 09:50:45 EDT Date: Mon, 22 Apr 96 09:50:45 EDT From: jleppek@suw2k.hisd.harris.com (James Leppek) Message-Id: <9604221350.AA06758@suw2k.hisd.harris.com> To: freebsd-hackers@freefall.FreeBSD.org Subject: could tunnel device do this? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is really a 2 part question: part 1: what would be the best way to route all IP packets from a ethernet card to a process, I am guessing that the tun device could do this. part 2: what kind of thruput could be expected when doing this? If I had a pentium 166 could it saturate a 10Mbit line? What % of a 100Mbit link. Thanks, Jim Leppek From owner-freebsd-hackers Mon Apr 22 07:26:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA08068 for hackers-outgoing; Mon, 22 Apr 1996 07:26:03 -0700 (PDT) Received: from watson.grauel.com (watson.grauel.com [199.233.104.36]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA08063 Mon, 22 Apr 1996 07:25:59 -0700 (PDT) Received: from sparcmill.grauel.com (sparcmill.grauel.com [199.233.104.34]) by watson.grauel.com (8.7.5/8.7.3) with SMTP id JAA00350; Mon, 22 Apr 1996 09:28:15 -0500 (EST) Received: by sparcmill.grauel.com (SMI-8.6/SMI-SVR4) id JAA15252; Mon, 22 Apr 1996 09:25:37 -0500 Date: Mon, 22 Apr 1996 09:25:37 -0500 Message-Id: <199604221425.JAA15252@sparcmill.grauel.com> From: Richard J Kuhns To: dkelly@hiwaay.net (David Kelly) Cc: "Jonathan M. Bresler" , peter@taronga.com (Peter da Silva), hackers@freebsd.org Subject: Re: Archive Anaconda on 1540B -- waiting forever for tape to become ready In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Kelly writes: > At 10:16 PM 4/20/96, Jonathan M. Bresler wrote: > > is this a brand new blank tape? never before used? > > if so you have to "force" the tape. try "mt -f /dev/rst0 fsf 1" > > for me that results in > > "st0(ncr1:4:0): HARDWARE FAILURE info:1 asc:80,8a" > > but afterward mt operations work! > > I also just installed an Anaconda tape drive but haven't had any problems > like the above. Am running -stable patched thru 0074. Put the tape on ID 6, > my 2G Barracuda is on ID 0. Per Richard J Kuhns > 's advice I jumped jp6 (documented as "reserved") > without ever trying it unjumped. > Second-hand advice; I got it from Jonathan Bresler ;-). > System is a NexGen PCI-90 with Adaptec 2940. > > What bugs me a little is the tape drive doesn't continuously spool during > dump (or tar). Several times it stopped for a second or two. Eventually It doesn't spool well for me either, but it's still fast enough that I don't really care; it's worth the price. > dump asked me to insert the next tape. No way, 1.35G tape, 500M fs, I > aborted. Looks like I've got to teach dump how big the tape is, or figure > out how to get dump to run until it reaches the end of tape, or maybe dump > was using 512 byte blocks? > Try something like "dump 0uBbf 1300000 10 /dev/rst0"; if you don't tell dump how many blocks the tape will hold, it defaults to some (too low) number. -- Rich Kuhns rjk@grauel.com PO Box 6249 100 Sawmill Road Lafayette, IN 47903 (317)477-6000 x319 From owner-freebsd-hackers Mon Apr 22 09:26:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15492 for hackers-outgoing; Mon, 22 Apr 1996 09:26:38 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA15479 for ; Mon, 22 Apr 1996 09:26:34 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id LAA12431; Mon, 22 Apr 1996 11:19:58 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB303E.14D91FE0@webster.unety.net>; Mon, 22 Apr 1996 11:23:07 -0500 Message-ID: <01BB303E.14D91FE0@webster.unety.net> From: Jim Fleming To: Darren Reed , "'Luigi Rizzo'" Cc: "hackers@FreeBSD.ORG" Subject: RE: one less checksum ? (fwd) Date: Mon, 22 Apr 1996 11:23:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sunday, April 21, 1996 5:26 PM, Luigi Rizzo[SMTP:luigi@labinfo.iet.unipi.it] wrote: @> Is there any reason why the result of in_cksum() is stored in ip_sum in @> ipintr() ? @> @> A small gain can be observed if this is not done, for forwarded packets, @> by altering the checksum in ip_output() if IP_FORWARDING is set rather @> than recalculating the entire header checksum. Is this worthwhile ? @ @TCP/IP Illustrated vol.1 suggests something similar, so I'd say it is @worthwhile. Garret Wollman should be looking after this code right in @these days. @ @But I don't understand how you relate your code (which looks correct) @with the above comment. It looks like your code is computing the @checksum in the same place, just with a more efficient algorithm. @ @The same code fragments suggest some more optimizations when @if_forwarding is enabled, e.g. don't convert header fields (ip_len and @ip_off) for back and forth from network format. @ @ Luigi @ @ You will note that in IPv8.... ...that Checksums are not used in the IP header....this speeds things up a bit...if we can migrate Options out of the header, then we can really streamline this low level processing and at the same time create 2,047 new 32 bit address spaces. If you are using a closed system, you might try experimenting with the IPv8 format and using the "8 bit" in the version field to signify that the checksum processing has been disabled. The changes to the Free BSD code can be done in a few minutes. In this experimental scheme, your servers that feel like skipping the checksums can set the high bit to a 1 and when packets are received this bit can be reset to a 0 and checksum processing can be skipped. It would be interesting to see some large FTP benchmarks on local networks, with and without checksums enabled.... -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-hackers Mon Apr 22 09:41:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16388 for hackers-outgoing; Mon, 22 Apr 1996 09:41:52 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16380 Mon, 22 Apr 1996 09:41:50 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199604221641.JAA16380@freefall.freebsd.org> Subject: Re: .forward and sendmail? To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 22 Apr 1996 09:41:50 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199604220320.XAA08263@crh.cl.msu.edu> from "Charles Henrich" at Apr 21, 96 11:20:11 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Charles Henrich wrote: > > Explain to me how exactly sendmail is supposed to read .forward's out of > peoples directories, when it apparently runs as daemon? I have had zero luck > with this unless the directories are world read, as well as the .forward, this > is unusual! What am I missing here? check the permissions on your sendmail. sendmail needs to run as root for several reasons. it needs to read people's .forward file regardless of the permissions. it needs to append to people's mailboxes. it needs to bind port 25. any others? -r-sr-sr-x 3 root kmem 245760 Mar 10 18:25 /usr/sbin/sendmail -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ From owner-freebsd-hackers Mon Apr 22 09:46:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16629 for hackers-outgoing; Mon, 22 Apr 1996 09:46:45 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA16609 Mon, 22 Apr 1996 09:46:22 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.12/8.6.12) id MAA10587; Mon, 22 Apr 1996 12:46:09 -0400 From: Charles Henrich Message-Id: <199604221646.MAA10587@crh.cl.msu.edu> Subject: Re: .forward and sendmail? To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Mon, 22 Apr 1996 12:46:09 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199604221641.JAA16380@freefall.freebsd.org> from "Jonathan M. Bresler" at Apr 22, 96 09:41:50 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > check the permissions on your sendmail. sendmail needs to run as root > for several reasons. it needs to read people's .forward file > regardless of the permissions. it needs to append to people's > mailboxes. it needs to bind port 25. any others? > > -r-sr-sr-x 3 root kmem 245760 Mar 10 18:25 /usr/sbin/sendmail Those are the permissions on my sendmail. It just doesnt work! This is on a 2.1R system. ---- -r-sr-sr-x 3 root kmem 180224 Nov 16 04:59 /usr/sbin/sendmail* # ls -ld /root 2 drwx------ 8 root wheel 512 Apr 21 23:16 /root/ # more /root/.forward henrich ---- If I send mail to root@mymachine, it goes to /var/mail/root, instead of being forwarded. root's homedir is /root... This makes no sense! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Mon Apr 22 09:52:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA17134 for hackers-outgoing; Mon, 22 Apr 1996 09:52:16 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA17123 for ; Mon, 22 Apr 1996 09:52:13 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id PAA00388; Sun, 28 Apr 1996 15:51:41 -0700 (PDT) Message-Id: <199604282251.PAA00388@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@freebsd.org (FreeBSD hackers), henrich@crh.cl.msu.edu (Charles Henrich) Subject: Re: .forward and sendmail? In-reply-to: Your message of "Mon, 22 Apr 1996 07:44:27 +0200." <199604220544.HAA18025@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 28 Apr 1996 15:51:41 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Charles Henrich wrote: > >> Explain to me how exactly sendmail is supposed to read .forward's >> out of peoples directories, when it apparently runs as daemon? I >> have had zero luck with this unless the directories are world read, >> as well as the .forward, this is unusual! What am I missing here? > >I think it must be readable by `daemon' (and i would even call this a >security feature, as opposed to reading the file with root >privileges). Of course, your directory doesn't need to be readable by >`daemon', it's sufficient if it is _search_able by him (e.g.., >drwxr-x--x). sendmail is _supposed_ to run as suid root: -r-sr-xr-x 3 root bin 245760 Mar 28 23:02 /usr/sbin/sendmail -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Apr 22 11:31:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA24957 for hackers-outgoing; Mon, 22 Apr 1996 11:31:35 -0700 (PDT) Received: from Arizona.EDU (Penny.Telcom.Arizona.EDU [128.196.128.217]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA24948 for ; Mon, 22 Apr 1996 11:31:33 -0700 (PDT) Received: from sun1paztcn.wr.usgs.gov by Arizona.EDU (PMDF V5.0-5 #2381) id <01I3U9VUQKO0CDR0S7@Arizona.EDU>; Mon, 22 Apr 1996 11:31:02 -0700 (MST) Received: from localhost by sun1paztcn.wr.usgs.gov (4.1/SMI-4.1) id AA04018; Mon, 22 Apr 1996 11:29:51 -0700 (MST) Date: Mon, 22 Apr 1996 11:29:50 -0700 From: Doug Wellington Subject: Re: .forward and sendmail? In-reply-to: "Your message of Mon, 22 Apr 1996 12:46:09 -0400." <199604221646.MAA10587@crh.cl.msu.edu> To: Charles Henrich Cc: freebsd-hackers@FreeBSD.ORG, doug@sun1paztcn.wr.usgs.gov Message-id: <9604221829.AA04018@sun1paztcn.wr.usgs.gov> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Previously: ># more /root/.forward >henrich >---- > >If I send mail to root@mymachine, it goes to /var/mail/root, instead of being >forwarded. root's homedir is /root... This makes no sense! Might I suggest that you use an alias instead? Edit the file /etc/aliases and then run the newaliases command. For example, my aliases file looks like: MAILER-DAEMON: postmaster Postmaster: root root: doug nobody: /dev/null In theory this is more secure as well... BTW, did you mention which version of sendmail you were using? -Doug Doug Wellington doug@sun1paztcn.wr.usgs.gov System and Network Administrator US Geological Survey Tucson, AZ Project Office (602) 670-6821 x26 According to proposed Federal guidelines, this message is a "non-record". Hmm, I wonder if _everything_ I say is a "non-record"... The hardest thing in the world is to truly think for oneself. It is amazing how many people have let angst replace their self confidence. From owner-freebsd-hackers Mon Apr 22 11:34:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25200 for hackers-outgoing; Mon, 22 Apr 1996 11:34:40 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA25195 for ; Mon, 22 Apr 1996 11:34:39 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.12/8.6.12) id OAA00986; Mon, 22 Apr 1996 14:32:39 -0400 From: Charles Henrich Message-Id: <199604221832.OAA00986@crh.cl.msu.edu> Subject: Re: .forward and sendmail? To: doug@sun1paztcn.wr.usgs.gov (Doug Wellington) Date: Mon, 22 Apr 1996 14:32:39 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG, doug@sun1paztcn.wr.usgs.gov In-Reply-To: <9604221829.AA04018@sun1paztcn.wr.usgs.gov> from "Doug Wellington" at Apr 22, 96 11:29:50 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Might I suggest that you use an alias instead? Edit the file /etc/aliases and >then run the newaliases command. For example, my aliases file looks like: Thats just an example, the same problems occur with users .forwards, which is the real problem. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Mon Apr 22 13:56:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09017 for hackers-outgoing; Mon, 22 Apr 1996 13:56:42 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA08999 for ; Mon, 22 Apr 1996 13:56:36 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.6.9) id PAA09876 for freebsd-hackers@freefall.cdrom.com; Mon, 22 Apr 1996 15:55:59 -0500 (CDT) From: Bob Willcox Message-Id: <199604222055.PAA09876@luke.pmr.com> Subject: Help! I need info on pthreads. To: freebsd-hackers@freefall.FreeBSD.org (freebsd-hackers) Date: Mon, 22 Apr 1996 15:55:59 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have suddenly been informed that I must convert a significant piece of code to use pthreads. Since FreeBSD will be one of my test vehicles I need to know if the libc_r library under 2.1-stable and/or current is working. Also, I would greatly appreciate any pointers to documentation or books that describe how to use pthreads. Thanks a bunch, -- Bob Willcox bob@luke.pmr.com Austin, TX From owner-freebsd-hackers Mon Apr 22 15:14:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA18327 for hackers-outgoing; Mon, 22 Apr 1996 15:14:38 -0700 (PDT) Received: from vent.pipex.net (root@vent.pipex.net [158.43.128.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA18243 for ; Mon, 22 Apr 1996 15:13:30 -0700 (PDT) Received: from dial.pipex.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id XAA08352; Mon, 22 Apr 1996 23:12:23 +0100 Received: (from jraynard@localhost) by dial.pipex.com (8.6.12/8.6.12) id VAA00923; Mon, 22 Apr 1996 21:42:43 GMT Date: Mon, 22 Apr 1996 21:42:43 GMT From: James Raynard Message-Id: <199604222142.VAA00923@dial.pipex.com> To: freebsd-hackers@freebsd.org Subject: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Inspired by Rich Stevens' implementation of system() in his book "Advanced Programming in the Unix Environment", I've been looking at the FreeBSD implementation and was struck by the following points:- 1. Use of a wait union when an int would do. 2. Use of the soon-to-be-obsolescent vfork() instead of fork(). 3. Returns 0 if fork() fails, when -1 seems more appropriate. 4. The SIGINT and SIGQUIT are not ignored until after the fork(). If the child runs first, one of these signals could in theory be generated before the parent gets around to ignoring it. Hence the dispositions should be changed before the fork(). Here's an untested patch which addresses these points. Comments/corrections welcomed! (In /usr/src/lib/libc/stdlib) *** system.c~ Mon Apr 22 21:04:59 1996 --- system.c Mon Apr 22 21:20:18 1996 *************** *** 46,76 **** system(command) const char *command; { - union wait pstat; pid_t pid; ! int omask; sig_t intsave, quitsave; if (!command) /* just checking... */ return(1); omask = sigblock(sigmask(SIGCHLD)); ! switch(pid = vfork()) { case -1: /* error */ ! (void)sigsetmask(omask); ! pstat.w_status = 0; ! pstat.w_retcode = 127; ! return(pstat.w_status); case 0: /* child */ (void)sigsetmask(omask); execl(_PATH_BSHELL, "sh", "-c", command, (char *)NULL); _exit(127); } - intsave = signal(SIGINT, SIG_IGN); - quitsave = signal(SIGQUIT, SIG_IGN); - pid = waitpid(pid, (int *)&pstat, 0); (void)sigsetmask(omask); (void)signal(SIGINT, intsave); (void)signal(SIGQUIT, quitsave); ! return(pid == -1 ? -1 : pstat.w_status); } --- 46,77 ---- system(command) const char *command; { pid_t pid; ! int omask, pstat; sig_t intsave, quitsave; if (!command) /* just checking... */ return(1); + intsave = signal(SIGINT, SIG_IGN); + quitsave = signal(SIGQUIT, SIG_IGN); omask = sigblock(sigmask(SIGCHLD)); ! switch(pid = fork()) { case -1: /* error */ ! break; case 0: /* child */ (void)sigsetmask(omask); + (void)signal(SIGINT, intsave); + (void)signal(SIGQUIT, quitsave); execl(_PATH_BSHELL, "sh", "-c", command, (char *)NULL); _exit(127); + default: /* parent */ + pid = waitpid(pid, &pstat, 0); + break; } (void)sigsetmask(omask); (void)signal(SIGINT, intsave); (void)signal(SIGQUIT, quitsave); ! return(pid == -1 ? -1 : pstat); } From owner-freebsd-hackers Mon Apr 22 15:26:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA19599 for hackers-outgoing; Mon, 22 Apr 1996 15:26:04 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA19584 Mon, 22 Apr 1996 15:25:59 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id AAA18920; Tue, 23 Apr 1996 00:26:05 +0200 Received: by uni4nn.iaf.nl with UUCP id AA10157 (5.67b/IDA-1.5); Tue, 23 Apr 1996 00:25:38 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA03332 (5.67b/IDA-1.5); Mon, 22 Apr 1996 23:56:14 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id XAA02487; Mon, 22 Apr 1996 23:15:34 +0200 From: Wilko Bulte Message-Id: <199604222115.XAA02487@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: .forward and sendmail? To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 22 Apr 1996 23:15:34 +0200 (MET DST) Cc: jmb@freefall.freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <199604221646.MAA10587@crh.cl.msu.edu> from "Charles Henrich" at Apr 22, 96 12:46:09 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > for several reasons. it needs to read people's .forward file > > regardless of the permissions. it needs to append to people's > > mailboxes. it needs to bind port 25. any others? > > > > -r-sr-sr-x 3 root kmem 245760 Mar 10 18:25 /usr/sbin/sendmail > > Those are the permissions on my sendmail. It just doesnt work! This is on a > 2.1R system. > > ---- > -r-sr-sr-x 3 root kmem 180224 Nov 16 04:59 /usr/sbin/sendmail* > > # ls -ld /root > 2 drwx------ 8 root wheel 512 Apr 21 23:16 /root/ > > # more /root/.forward > henrich > ---- > > If I send mail to root@mymachine, it goes to /var/mail/root, instead of being > forwarded. root's homedir is /root... This makes no sense! > > -Crh > > Charles Henrich Michigan State University henrich@msu.edu What does your sendmail.cf look like for: # Forward file search path #OJ/var/forward/$u:$z/.forward.$w:$z/.forward Mine was like this: commented out. I also think sendmail can be compiled to not do .forwards (for security reasons). Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-hackers Mon Apr 22 16:13:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA25155 for hackers-outgoing; Mon, 22 Apr 1996 16:13:57 -0700 (PDT) Received: from vic.cioe.com (vic.cioe.com [204.120.165.37]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA25123 Mon, 22 Apr 1996 16:13:51 -0700 (PDT) Received: (from root@localhost) by vic.cioe.com (8.7.5/8.7.3) id SAA28204; Mon, 22 Apr 1996 18:14:17 -0500 (EST) Date: Mon, 22 Apr 1996 18:14:17 -0500 (EST) From: Charlie Root Message-Id: <199604222314.SAA28204@vic.cioe.com> To: freebsd-questions@freebsd.org Subject: Adaptec 3985 RAID controller Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone out there go this beastie? It supports Raid 5, 1, 0 and 0/1. Is anyone even considering writing a controller for FreeBSD to support the 3985? I'm definately considering buying one, but would like it on one of my FreeBSD machines... If anyone out there who has ever written a driver can occasionally hold our hand I can talk our development department into spending some time writing a driver... -Steve From owner-freebsd-hackers Mon Apr 22 16:14:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA25172 for hackers-outgoing; Mon, 22 Apr 1996 16:14:00 -0700 (PDT) Received: from bubba.tribe.com ([205.184.207.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA25152 for ; Mon, 22 Apr 1996 16:13:57 -0700 (PDT) Received: (from archie@localhost) by bubba.tribe.com (8.6.12/8.6.12) id QAA26291; Mon, 22 Apr 1996 16:13:47 -0700 From: Archie Cobbs Message-Id: <199604222313.QAA26291@bubba.tribe.com> Subject: ifconfig aliases To: freebsd-hackers@freebsd.org Date: Mon, 22 Apr 1996 16:13:46 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is with FreeBSD 2.2-CURRENT #0: Tue Apr 9 18:59:00 PDT 1996 Seems like the two commands marked below generate error messages backwards ... the second one should have the error message, not the first. Does anyone else see this? Seems to be coming from function in_ifinit() in netinet/in.c (but that's as far as I got). $ ifconfig ed0 ed0: flags=8843 mtu 1500 inet 192.168.0.22 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:00:e8:cd:1b:b8 =>$ ifconfig ed0 192.168.0.97 alias ifconfig: ioctl (SIOCAIFADDR): File exists $ ifconfig ed0 ed0: flags=8843 mtu 1500 inet 192.168.0.22 netmask 0xffffff00 broadcast 192.168.0.255 inet 192.168.0.97 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:00:e8:cd:1b:b8 =>$ ifconfig ed0 192.168.0.97 alias $ ifconfig ed0 ed0: flags=8843 mtu 1500 inet 192.168.0.22 netmask 0xffffff00 broadcast 192.168.0.255 inet 192.168.0.97 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:00:e8:cd:1b:b8 -Archie __________________________________________________________________________ Archie L. Cobbs, archie@tribe.com * Whistle Communications Corporation From owner-freebsd-hackers Mon Apr 22 16:24:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA26546 for hackers-outgoing; Mon, 22 Apr 1996 16:24:54 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA26541 Mon, 22 Apr 1996 16:24:50 -0700 (PDT) Received: from ole.cs.tu-berlin.de (wosch@ole.cs.tu-berlin.de [130.149.28.1]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id BAA14098; Tue, 23 Apr 1996 01:24:19 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id AAA09500; Tue, 23 Apr 1996 00:13:59 +0200 Date: Tue, 23 Apr 1996 00:13:59 +0200 From: Wolfram Schneider Message-Id: <199604222213.AAA09500@campa.panke.de> To: "Jonathan M. Bresler" Cc: henrich@crh.cl.msu.edu (Charles Henrich), freebsd-hackers@freebsd.org Subject: Re: .forward and sendmail? In-Reply-To: <199604221641.JAA16380@freefall.freebsd.org> References: <199604220320.XAA08263@crh.cl.msu.edu> <199604221641.JAA16380@freefall.freebsd.org> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan M. Bresler writes: > check the permissions on your sendmail. sendmail needs to run as root > for several reasons. it needs to read people's .forward file > regardless of the permissions. >it needs to append to people's mailboxes. No, this is the job of /usr/libexec/mail.local (also suid root). >it needs to bind port 25. Only first time like httpd in daemon mode. >any others? Automatically rebuilt of /etc/aliases.db and other databases, permissions of various directories in /var. Wolfram From owner-freebsd-hackers Mon Apr 22 18:06:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA08354 for hackers-outgoing; Mon, 22 Apr 1996 18:06:54 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA08294 for ; Mon, 22 Apr 1996 18:06:37 -0700 (PDT) Received: from cimaxp1.UUCP (uucp@localhost) by melb.werple.net.au (8.7.5/8.7.3) with UUCP id KAA18978 for mira!freefall.freebsd.org!freebsd-hackers; Tue, 23 Apr 1996 10:13:03 +1000 (EST) Message-Id: <199604230013.KAA18978@melb.werple.net.au> Received: by cimaxp1.cimlogic.com.au; (5.65/1.1.8.2/10Sep95-0953AM) id AA19036; Tue, 23 Apr 1996 10:13:43 +1000 From: John Birrell Subject: Re: Help! I need info on pthreads. To: luke.pmr.com!bob@melb.werple.net.au (Bob Willcox) Date: Tue, 23 Apr 1996 10:13:43 +1000 (EST) Cc: freefall.freebsd.org!freebsd-hackers@melb.werple.net.au In-Reply-To: <199604222055.PAA09876@luke.pmr.com> from "Bob Willcox" at Apr 22, 96 03:55:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have suddenly been informed that I must convert a significant > piece of code to use pthreads. Since FreeBSD will be one of my > test vehicles I need to know if the libc_r library under 2.1-stable > and/or current is working. 2.2-current only. It works for me. If it doesn't work for _you_, let me know. Watch out for libc functions that aren't re-entrant, though. > > Also, I would greatly appreciate any pointers to documentation or > books that describe how to use pthreads. IEEE P1003.1c, D10 September 1994 DS5314 is the draft amendment which still has not been published. For online docs (equivalent to man files), try www.mit.edu:8001/people/proven/pthreads.html (I think) I haven't looked for books on how to use pthreads. I'm from an OSF/1 environment where we used DEC's poor examples as a start. Their bookreader docs aren't too bad at describing the functions, but they are not good at describing how to design a threaded application. > > Thanks a bunch, > -- > Bob Willcox > bob@luke.pmr.com > Austin, TX > Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Mon Apr 22 18:32:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11343 for hackers-outgoing; Mon, 22 Apr 1996 18:32:02 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA11325 for ; Mon, 22 Apr 1996 18:31:58 -0700 (PDT) Received: from max4-146.HiWAAY.net by fly.HiWAAY.net; (5.65v3.0/1.1.8.2/21Sep95-1003PM) id AA30139; Mon, 22 Apr 1996 20:31:04 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 22 Apr 1996 20:31:33 -0500 To: Richard J Kuhns From: dkelly@hiwaay.net (David Kelly) Subject: Re: Archive Anaconda on 1540B -- waiting forever for tape to become ready Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 9:25 AM 4/22/96, Richard J Kuhns wrote: >David Kelly writes: > > What bugs me a little is the tape drive doesn't continuously spool during > > dump (or tar). Several times it stopped for a second or two. Eventually > >It doesn't spool well for me either, but it's still fast enough that I >don't really care; it's worth the price. I've run my 1.35G tape end to end about 10 times now and have a better idea whats going on. It takes just under 90 seconds for the tape to run from one end to the other. There is always an extra reversal on reversal where I'm guessing the mechanism is making sure it landed on the right track after turning around. Often it spools until the next reversal/track change. Sometimes it has to stop and resume in the middle several times (in different places). This reminds me of my Tandberg TDC-3660 (which the Anacoda replaced). Usually it spools right along but one day it hit something that gave it fits. It was writing a copy of the 2.1R ports directory(s) to disk. Apparently in 2.0.5R (or maybe I was running 2.1R at the time) creating a directory was an expensive task. Might have been writing to an IDE drive. dd if=/dev/zero of=/dev/tape bs=1M count=1024 produces interesting results. The tape spools the whole way. Reported data rate is about 30 MB/min, but "systat -v" shows the system running about 50% in sys. That was unexpected. Is somebody busy-waiting? Is my tape drive failing to disconnect from the SCSI bus? (I jumped the SCSI-2 jumper on the Anaconda.) Think I need to check my 2940's BIOS setup because there is some kind of option like that in there. Yup, but dontcha know how Murphy's Law works? My Anaconda arrived Friday. Then Saturday at the Birmingham (AL) Hamfest I picked up a 525MB Archive in Unisys external case for $10. Works great. Think it might stay on my Macintosh. Heck, I was just looking for a case to make my second Anaconda portable but found an entire working drive. -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net ============================================================= To invent, you need a good imagination and a pile of junk. - Thomas Edison From owner-freebsd-hackers Mon Apr 22 20:02:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA22658 for hackers-outgoing; Mon, 22 Apr 1996 20:02:51 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA22647 for ; Mon, 22 Apr 1996 20:02:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id VAA01127; Mon, 22 Apr 1996 21:02:29 -0600 (MDT) Message-Id: <199604230302.VAA01127@rover.village.org> To: rich@lamprey.utmb.edu Subject: Re: This is sick... Cc: hackers@freebsd.org In-reply-to: Your message of Mon, 22 Apr 1996 08:53:03 CDT Date: Mon, 22 Apr 1996 21:02:27 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : I'm told that accessing 2 CDs simultaneously is also : very hard on the drive mechanisms. If you hear the : drive making grinding noises during rapid CD changes : you'll know what they mean. Rich I have a couple of friends who have these things on their Linux boxes, and have hung the drive a few times by doing a simultaneous ls -R on two mounted disks, or diff -r on two different disks. The sounds are horrible, so it is no wonder that it is hard on the mechanism... Warner From owner-freebsd-hackers Mon Apr 22 20:10:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA23667 for hackers-outgoing; Mon, 22 Apr 1996 20:10:21 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA23650 for ; Mon, 22 Apr 1996 20:10:14 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id FAA19173; Tue, 23 Apr 1996 05:09:53 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id FAA05251; Tue, 23 Apr 1996 05:09:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id EAA20717; Tue, 23 Apr 1996 04:56:16 +0200 (MET DST) From: J Wunsch Message-Id: <199604230256.EAA20717@uriah.heep.sax.de> Subject: Re: Device Driver ioctl() help To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 23 Apr 1996 04:56:16 +0200 (MET DST) Cc: jfrancis@frii.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604220543.BAA01869@tap.zeus.leitch.com> from "Dave Chapeskie" at Apr 22, 96 01:43:03 am X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Dave Chapeskie wrote: > >#define JOY_SETTIMEOUT _IOW('J', 1, int) /* set timeout */ > [...] > > Ok, it looks like the 'J' has something to do with a "group", > >but what kind of group? How is this value chosen and what does it do? > > Get a good book on writing device drivers. Typically you just use > group 0 unless you know what you're doing. _IO is used when no data is Hmm, i think the idea behind the `group' (and partially the `cmd') value is to be semi-random, in order to reduce the probability of an accidental ioctl name space clash with the ioctl of a foreign driver. (Since BSD also encodes the lenth and IO direction of the third parameter into the actual CMD, name space collisions are seldom compared to V7 UNIX anyway.) The convention was to pick a letter that is roughly related to your driver as `group'. That's why the joystick driver is using `J'. > I think you need a better book. I can't recommend one at the moment > since I'm not at work where my bookshelf is. I think this is already covered well in the old ``Daemon book'' (The 4.3BSD Operating System. Design and Implementation.) Don't use a SysV book, SysV uses the old V7 UNIX algorithm where each and every driver is responsible to perform the copyin()/copyout() itself. Perhaps the easiest way is to pick several examples from existing BSD drivers (not just one only). -- 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 Apr 22 21:21:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01810 for hackers-outgoing; Mon, 22 Apr 1996 21:21:39 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA01800 for ; Mon, 22 Apr 1996 21:21:33 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA20173; Tue, 23 Apr 1996 06:21:00 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA06456; Tue, 23 Apr 1996 06:20:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id FAA21276; Tue, 23 Apr 1996 05:32:43 +0200 (MET DST) From: J Wunsch Message-Id: <199604230332.FAA21276@uriah.heep.sax.de> Subject: Re: .forward and sendmail? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 23 Apr 1996 05:32:42 +0200 (MET DST) Cc: davidg@Root.COM, henrich@crh.cl.msu.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604282251.PAA00388@Root.COM> from "David Greenman" at Apr 28, 96 03:51:41 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Greenman wrote: > >I think it must be readable by `daemon' (and i would even call this a > >security feature, as opposed to reading the file with root > >privileges). Of course, your directory doesn't need to be readable by > >`daemon', it's sufficient if it is _search_able by him (e.g.., > >drwxr-x--x). > > sendmail is _supposed_ to run as suid root: Yes, but think about it. It reads the .forward with the identity of `daemon', not `root'. Otherwise, any user could link his ~/.forward to a file read-only for root, and try to figure out the contents of this file by sending mail to himself, and analyzing the bounces. Not that this will compromise the entire file, but that's why i wrote: ``I would call it a security 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 Mon Apr 22 22:41:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA05936 for hackers-outgoing; Mon, 22 Apr 1996 22:41:58 -0700 (PDT) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA05929 Mon, 22 Apr 1996 22:41:54 -0700 (PDT) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id HAA27032 ; Tue, 23 Apr 1996 07:41:47 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id HAA13880 ; Tue, 23 Apr 1996 07:41:47 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.7) id BAA02230; Tue, 23 Apr 1996 01:37:10 +0200 (MET DST) From: Ollivier Robert Message-Id: <199604222337.BAA02230@keltia.freenix.fr> Subject: Re: .forward and sendmail? To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Tue, 23 Apr 1996 01:37:10 +0200 (MET DST) Cc: henrich@crh.cl.msu.edu, freebsd-hackers@FreeBSD.org In-Reply-To: <199604221641.JAA16380@freefall.freebsd.org> from "Jonathan M. Bresler" at "Apr 22, 96 09:41:50 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1916 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk It seems that Jonathan M. Bresler said: > regardless of the permissions. it needs to append to people's Appending messages is the work of the local mailer, not sendmail. > -r-sr-sr-x 3 root kmem 245760 Mar 10 18:25 /usr/sbin/sendmail The setgid is unnecessary as sendmail in -CURRENT has been patched to use another method than reading kmem for gettting the load average. -r-sr-xr-x 3 root bin 262144 Apr 1 11:15 /usr/sbin/sendmail -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #13: Sun Apr 21 18:14:54 MET DST 1996 From owner-freebsd-hackers Tue Apr 23 00:05:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09304 for hackers-outgoing; Tue, 23 Apr 1996 00:05:00 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA09218 for ; Tue, 23 Apr 1996 00:04:03 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id JAA07887 for hackers@freebsd.org; Tue, 23 Apr 1996 09:03:32 +0200 Message-Id: <199604230703.JAA07887@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Tue, 23 Apr 96 9:00:15 MDT From: Greg Lehey Cc: current@freebsd.org, hackers@freebsd.org (FreeBSD hackers) In-Reply-To: ; from "Sujal Patel" at Apr 22, 96 6:02 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 22 Apr 1996, Marc G. Fournier wrote: > >> I happened to be off of vt0 when it died, with no way to >> switch to vt0 and see what ddb was showing, and since I had to >> cold boot the machine as a result, couldn't even get a core dump :( >> >> So...any way of having an auto-switch to vt0 if the system >> crashes with DDB enabled? Good idea. I'll add it to my list. For those who don't know, I had planned to make some major changes to ddb Real Soon Now. > While we're talking about DDB, can't we have it timeout in 30s if you > don't hit a key (and then generate a core dump). Also a good idea. > What about making DDB a LKM also? Whenever I find myself using DDB, I > know that the system is going to panic, not everyone needs DDB loaded at > all times (and rebuilding kernels is such a pain). Yes, I had planned on that. Who can give me info on how to write LKMs? On the other subject, changing out of X into character mode: I believe that a debugger should have as little involvement with the subject being debugged (in this case, the kernel), as possible. I can't see why ddb shouldn't understand enough about generic VGA to be able to put it back in 25x80 mode. Somewhere I have a little program which I used to do this under BSD/386 0.3, where the X server wasn't always successful. It's only a few lines. I'm sure somebody's going to come up with "yes, but that's not completely generic", but I don't think this is an adequate argument. Make it a config option for ddb, and it'll handle 98% of all hardware. If somebody with the other 2% wants, they can do it for that hardware as well. I'm copying hackers on this, since that is where we discussed ddb before. Greg From owner-freebsd-hackers Tue Apr 23 01:13:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA15868 for hackers-outgoing; Tue, 23 Apr 1996 01:13:07 -0700 (PDT) Received: from isbalham (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA15733 for ; Tue, 23 Apr 1996 01:11:54 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham (8.6.12/8.6.12) with UUCP id JAA06645; Tue, 23 Apr 1996 09:07:18 +0100 Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 23 Apr 1996 09:01:47 +0100 X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Apr 1996 09:03:28 +0100 To: Bob Willcox From: rb@gid.co.uk (Bob Bishop) Subject: Re: Help! I need info on pthreads. Cc: freebsd-hackers@freefall.FreeBSD.org (freebsd-hackers) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 3:55 pm 22/4/96, Bob Willcox wrote: >[...] >Also, I would greatly appreciate any pointers to documentation or >books that describe how to use pthreads. Have a look at: Programming with Threads Kleiman, Shah, Smaalders SunSoft Press (Prentice Hall) 1996 ISBN 0-13-172389-8 (BTW, saw this misquoted in a review as "Programming with Threats". Now there's an interesting concept ;-) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Tue Apr 23 02:34:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA21184 for hackers-outgoing; Tue, 23 Apr 1996 02:34:44 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA21179 Tue, 23 Apr 1996 02:34:30 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA12645; Tue, 23 Apr 1996 19:28:35 +1000 Date: Tue, 23 Apr 1996 19:28:35 +1000 From: Bruce Evans Message-Id: <199604230928.TAA12645@godzilla.zeta.org.au> To: lehey.pad@sni.de, smpatel@umiacs.UMD.EDU Subject: Re: request for a new "feature" as regards DDB Cc: current@freebsd.org, hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> So...any way of having an auto-switch to vt0 if the system >>> crashes with DDB enabled? Use syscons. >Good idea. I'll add it to my list. For those who don't know, I had >planned to make some major changes to ddb Real Soon Now. >> While we're talking about DDB, can't we have it timeout in 30s if you >> don't hit a key (and then generate a core dump). >Also a good idea. Bad idea. You should make sure that ddb is never entered if you're not around to watch it. >> What about making DDB a LKM also? Whenever I find myself using DDB, I >Yes, I had planned on that. Who can give me info on how to write >LKMs? Begin with /usr/src/share/examples/lkm. >On the other subject, changing out of X into character mode: I believe >that a debugger should have as little involvement with the subject >being debugged (in this case, the kernel), as possible. I can't see Yes, it shouldn't touch anything that it doesn't fully understand or can't restore. >why ddb shouldn't understand enough about generic VGA to be able to >put it back in 25x80 mode. Somewhere I have a little program which I >used to do this under BSD/386 0.3, where the X server wasn't always >successful. It's only a few lines. I'm sure somebody's going to come >up with "yes, but that's not completely generic", but I don't think >this is an adequate argument. Make it a config option for ddb, and "yes, but that's not completely generic" :-). >it'll handle 98% of all hardware. If somebody with the other 2% >wants, they can do it for that hardware as well. It'll only handle 98% of all hardware that is running in a VGA compatible mode. I guess most X modes aren't VGA compatible. Bruce From owner-freebsd-hackers Tue Apr 23 02:50:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA21828 for hackers-outgoing; Tue, 23 Apr 1996 02:50:04 -0700 (PDT) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA21796 for ; Tue, 23 Apr 1996 02:49:47 -0700 (PDT) Received: from spase by ns.NL.net via EUnet id AA02208 (5.65b/CWI-3.3); Tue, 23 Apr 1996 11:19:09 +0200 Received: from phobos.spase.nl (phobos [192.9.200.238]) by mercurius.spase.nl (8.6.11/8.6.11) with ESMTP id LAA22650 for ; Tue, 23 Apr 1996 11:24:54 +0200 From: Kees Jan Koster Received: (dutchman@localhost) by phobos.spase.nl (8.6.12/8.6.11) id LAA01329 for freebsd-hackers@FreeBSD.ORG; Tue, 23 Apr 1996 11:26:08 +0200 Message-Id: <199604230926.LAA01329@phobos.spase.nl> Subject: Install via FTP failed. To: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers Mailing list) Date: Tue, 23 Apr 1996 11:26:08 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hoi Hackers, I've tried installing FreeBSD via FTP off a 2.1.0-release cdrom mounted on a linux machine. It seems that it can load the root image from but it cannot find the distributions. NFS install off the same cdrom mounted on the same linux box works OK. What did I do wrong? Another point: when I change the URL for installing the FTP connection is not restarted. Groetjes, Kees Jan ======================================================================v== Kees Jan Koster e-mail: dutchman@spase.nl Van Somerenstraat 50 tel: NL-24-3234708 6521 BS Nijmegen the Netherlands ========================================================================= Who is this general Failure and why is he reading my disk? (anonymous) ========================================================================= From owner-freebsd-hackers Tue Apr 23 03:01:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22117 for hackers-outgoing; Tue, 23 Apr 1996 03:01:58 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA22107 for ; Tue, 23 Apr 1996 03:01:34 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id MAA20823 for hackers@freebsd.org; Tue, 23 Apr 1996 12:00:50 +0200 Message-Id: <199604231000.MAA20823@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Tue, 23 Apr 96 12:00:43 MDT From: Greg Lehey Cc: lehey.pad@sni.de, smpatel@umiacs.UMD.EDU, current@freebsd.org, hackers@freebsd.org In-Reply-To: <199604230928.TAA12645@godzilla.zeta.org.au>; from "Bruce Evans" at Apr 23, 96 7:28 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> So...any way of having an auto-switch to vt0 if the system >>>> crashes with DDB enabled? > > Use syscons. I don't understand. Are you saying "syscons auto-switches to vt0 if the system crashes with DDB enabled", or are you saying "if you use syscons, you can still change after entering DDB", or are you saying something else? >> Good idea. I'll add it to my list. For those who don't know, I had >> planned to make some major changes to ddb Real Soon Now. > >>> While we're talking about DDB, can't we have it timeout in 30s if you >>> don't hit a key (and then generate a core dump). > >> Also a good idea. > > Bad idea. You should make sure that ddb is never entered if you're not > around to watch it. I disagree completely. If my machine dies in the middle of the night, I want to come in the next morning and be able to debug the live hardware, not a dump. YMMV, but we should have the option. >>> What about making DDB a LKM also? Whenever I find myself using DDB, I > >> Yes, I had planned on that. Who can give me info on how to write >> LKMs? > > Begin with /usr/src/share/examples/lkm. Thanks. >> On the other subject, changing out of X into character mode: I believe >> that a debugger should have as little involvement with the subject >> being debugged (in this case, the kernel), as possible. I can't see > > Yes, it shouldn't touch anything that it doesn't fully understand or > can't restore. > >> why ddb shouldn't understand enough about generic VGA to be able to >> put it back in 25x80 mode. Somewhere I have a little program which I >> used to do this under BSD/386 0.3, where the X server wasn't always >> successful. It's only a few lines. I'm sure somebody's going to come >> up with "yes, but that's not completely generic", but I don't think >> this is an adequate argument. Make it a config option for ddb, and > > "yes, but that's not completely generic" :-). > >> it'll handle 98% of all hardware. If somebody with the other 2% >> wants, they can do it for that hardware as well. > > It'll only handle 98% of all hardware that is running in a VGA compatible > mode. I guess most X modes aren't VGA compatible. Hmmm. I'd have to check that. We're not interested in the non-compatible modes, we're just interested in whether we can set a VGA compatible mode when we need it. My program ran on an ET4000, and it worked OK, but I suppose it's possible that more modern hardware might not have a simple way to set it back to character mode. I'll enquire. Greg From owner-freebsd-hackers Tue Apr 23 03:23:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22807 for hackers-outgoing; Tue, 23 Apr 1996 03:23:27 -0700 (PDT) Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA22802 for ; Tue, 23 Apr 1996 03:23:25 -0700 (PDT) Received: from exalt.x.org by expo.x.org id AA13960; Tue, 23 Apr 96 06:22:53 -0400 Received: from localhost by exalt.x.org id GAA03612; Tue, 23 Apr 1996 06:22:53 -0400 Message-Id: <199604231022.GAA03612@exalt.x.org> To: hackers@freefall.FreeBSD.org Subject: Re: Help! I need info on pthreads. In-Reply-To: Your message of Tue, 23 Apr 1996 10:13:43 EST. <199604230013.KAA18978@melb.werple.net.au> Organization: X Consortium Date: Tue, 23 Apr 1996 06:22:52 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have suddenly been informed that I must convert a significant > > piece of code to use pthreads. Since FreeBSD will be one of my > > test vehicles I need to know if the libc_r library under 2.1-stable > > and/or current is working. > > 2.2-current only. It works for me. If it doesn't work for _you_, let > me know. Watch out for libc functions that aren't re-entrant, though. You mean watch out for libc functions that aren't MT-safe. There's a big difference between being MT-safe and being reentrant. Reentrant means the function can be called in a signal handler, usually limited to system calls. MT-safe means the function can be called by more than one thread at a time. On other systems with threads there are MT-safe functions that aren't reentrant. -- Kaleb KEITHLEY From owner-freebsd-hackers Tue Apr 23 03:59:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA24195 for hackers-outgoing; Tue, 23 Apr 1996 03:59:48 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA24061 Tue, 23 Apr 1996 03:56:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA15838; Tue, 23 Apr 1996 20:45:26 +1000 Date: Tue, 23 Apr 1996 20:45:26 +1000 From: Bruce Evans Message-Id: <199604231045.UAA15838@godzilla.zeta.org.au> To: bde@zeta.org.au, lehey.pad@sni.de Subject: Re: request for a new "feature" as regards DDB Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, smpatel@umiacs.UMD.EDU Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> So...any way of having an auto-switch to vt0 if the system >>>>> crashes with DDB enabled? >> >> Use syscons. >I don't understand. Are you saying "syscons auto-switches to vt0 if >the system crashes with DDB enabled", or are you saying "if you use I meant that syscons auto-switches from ttyvn to ttyv0 when DDB is entered. It actually stays on the same ttyvn, just like pcvt, and you have to hit Alt-F1 to switch to it, not quite like in pcvt, where you have to hit Ctr-Alt-F1. Switching from graphics mode of course doesn't work for either syscons or pcvt. >> Bad idea. You should make sure that ddb is never entered if you're not >> around to watch it. >I disagree completely. If my machine dies in the middle of the night, >I want to come in the next morning and be able to debug the live >hardware, not a dump. YMMV, but we should have the option. OK, you should makesure that ddb is never entered if you don't want it to wait. Entering ddb decreases the chance of getting a clean dump and reboot. There is currently no simple way of returning from ddb to continue as if ddb wasn't configured except when ddb was entered via Debugger() (if it was entered via kdb_trap(), then you have to modify some ddb code or variables to get it to return 0). The normal way to quit ddb after a fatal trap is to use the builtin panic, but this complicates the trap frames. >> It'll only handle 98% of all hardware that is running in a VGA compatible >> mode. I guess most X modes aren't VGA compatible. >Hmmm. I'd have to check that. We're not interested in the >non-compatible modes, we're just interested in whether we can set a >VGA compatible mode when we need it. My program ran on an ET4000, and >it worked OK, but I suppose it's possible that more modern hardware >might not have a simple way to set it back to character mode. I'll >enquire. I'm most familiar with the ET400. It has locks to prevent inadvertent access to the special Tseng registers. Some of these locks must be opened to change the bits to enable fairly standard graphics features. E.g., there's one for interlace mode. To work on an ET400, you would have to use the keys for these locks or maybe depend on the X server leaving everything unlocked. I think there are no standards for the keys, and more modern graphics cards have more things to lock, so simply stuffing the VGA registers with standard values is unlikely to work. I've never had any success with using vidcontrol to fix up the state on Et4000/W32 or S3 cards after the X server has crashed. Bruce From owner-freebsd-hackers Tue Apr 23 04:24:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA25591 for hackers-outgoing; Tue, 23 Apr 1996 04:24:23 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA25586 for ; Tue, 23 Apr 1996 04:24:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id EAA04652; Tue, 23 Apr 1996 04:23:58 -0700 (PDT) To: Kees Jan Koster cc: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers Mailing list) Subject: Re: Install via FTP failed. In-reply-to: Your message of "Tue, 23 Apr 1996 11:26:08 +0200." <199604230926.LAA01329@phobos.spase.nl> Date: Tue, 23 Apr 1996 04:23:57 -0700 Message-ID: <4650.830258637@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've tried installing FreeBSD via FTP off a 2.1.0-release cdrom mounted > on a linux machine. It seems that it can load the root image from but it > cannot find the distributions. NFS install off the same cdrom mounted on > the same linux box works OK. What did I do wrong? Nothing, really - it's just a fault of the 2.1-RELEASE installer which has since been fixed. If you do this: mount -t isofs /dev/cd0a /cdrom_real cd /cdrom ln -s /cdrom_real/{floppies,packages,ports,dists/*} . assuming, of course, that both /cdrom and /cdrom_real are somewhere actually accessible by ftp, it will work. Jordan From owner-freebsd-hackers Tue Apr 23 04:30:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA25821 for hackers-outgoing; Tue, 23 Apr 1996 04:30:54 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA25816 Tue, 23 Apr 1996 04:30:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id EAA04676; Tue, 23 Apr 1996 04:28:43 -0700 (PDT) To: Greg Lehey cc: bde@zeta.org.au (Bruce Evans), smpatel@umiacs.UMD.EDU, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for a new "feature" as regards DDB In-reply-to: Your message of "Tue, 23 Apr 1996 12:00:43 MDT." <199604231000.MAA20823@nixpbe.pdb.sni.de> Date: Tue, 23 Apr 1996 04:28:43 -0700 Message-ID: <4674.830258923@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I disagree completely. If my machine dies in the middle of the night, > I want to come in the next morning and be able to debug the live > hardware, not a dump. YMMV, but we should have the option. However, there's a corrolary: If your machine dies in the middle of the night (or when you're in front of it, for that matter) and *you're sitting in the X server* then you should be given a dump if you're not configured for a serial console because we know that there's no way in hell you're going to be debugging any live hardware. A dump is the best you can ask for under those circumstances. Assuming that the same interface which the VT_GETACTIVE ioctl() uses is available for determining if "curvty = vty0", it seems you should be able to avoid going into DDB interaction mode if it's not possible to do anything else. You can simply call panic. Jordan From owner-freebsd-hackers Tue Apr 23 04:34:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA26079 for hackers-outgoing; Tue, 23 Apr 1996 04:34:09 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA25978 for ; Tue, 23 Apr 1996 04:33:53 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id NAA26239 for hackers@freebsd.org; Tue, 23 Apr 1996 13:33:39 +0200 Message-Id: <199604231133.NAA26239@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 23 Apr 96 13:33:29 MDT From: Greg Lehey Cc: current@freebsd.org, hackers@freebsd.org (FreeBSD hackers) In-Reply-To: <4674.830258923@time.cdrom.com>; from "Jordan K. Hubbard" at Apr 23, 96 4:28 am X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I disagree completely. If my machine dies in the middle of the night, >> I want to come in the next morning and be able to debug the live >> hardware, not a dump. YMMV, but we should have the option. > > However, there's a corrolary: > > If your machine dies in the middle of the night (or when you're in > front of it, for that matter) and *you're sitting in the X server* > then you should be given a dump if you're not configured for a serial > console because we know that there's no way in hell you're going to be > debugging any live hardware. We haven't done that one to death yet :-) > A dump is the best you can ask for under those circumstances. If a dump is the best you can hope for, then you shouldn't have to even ask. Even if we can only change back to character mode 98% of the time, the other 2% (at least) should give you a dump. Of course, if there's a timeout, that would handle it. > Assuming that the same interface which the VT_GETACTIVE ioctl() > uses is available for determining if "curvty = vty0", it seems you > should be able to avoid going into DDB interaction mode if it's > not possible to do anything else. You can simply call panic. Sounds reasonable. I'll take a look at it. Greg From owner-freebsd-hackers Tue Apr 23 04:38:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA26327 for hackers-outgoing; Tue, 23 Apr 1996 04:38:25 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA26304 for ; Tue, 23 Apr 1996 04:37:52 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id NAA26445 for hackers@freebsd.org; Tue, 23 Apr 1996 13:37:30 +0200 Message-Id: <199604231137.NAA26445@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Tue, 23 Apr 96 13:37:28 MDT From: Greg Lehey Cc: hackers@freebsd.org (FreeBSD hackers) In-Reply-To: <199604231045.UAA15838@godzilla.zeta.org.au>; from "Bruce Evans" at Apr 23, 96 8:45 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is not really a -current theme, so I'm just copying hackers. >>> Use syscons. > >> I don't understand. Are you saying "syscons auto-switches to vt0 if >> the system crashes with DDB enabled", or are you saying "if you use > > I meant that syscons auto-switches from ttyvn to ttyv0 when DDB is > entered. It actually stays on the same ttyvn, just like pcvt, and > you have to hit Alt-F1 to switch to it, not quite like in pcvt, where > you have to hit Ctr-Alt-F1. Switching from graphics mode of course > doesn't work for either syscons or pcvt. OK, if that's all it takes. >>> Bad idea. You should make sure that ddb is never entered if you're not >>> around to watch it. > >> I disagree completely. If my machine dies in the middle of the night, >> I want to come in the next morning and be able to debug the live >> hardware, not a dump. YMMV, but we should have the option. > > OK, you should makesure that ddb is never entered if you don't want it to > wait. Entering ddb decreases the chance of getting a clean dump and > reboot. There is currently no simple way of returning from ddb to continue > as if ddb wasn't configured except when ddb was entered via Debugger() > (if it was entered via kdb_trap(), then you have to modify some ddb code > or variables to get it to return 0). The normal way to quit ddb after a > fatal trap is to use the builtin panic, but this complicates the trap > frames. This looks like the wrong solution. The correct one would be either 1: Make it easier to return from ddb out of kdb_trap. Lowbug doesn't have any problems there, so it must be possible. 2: Make the panic exit tidy up the stack first, so you see what you want to see. >>> It'll only handle 98% of all hardware that is running in a VGA compatible >>> mode. I guess most X modes aren't VGA compatible. > >> Hmmm. I'd have to check that. We're not interested in the >> non-compatible modes, we're just interested in whether we can set a >> VGA compatible mode when we need it. My program ran on an ET4000, and >> it worked OK, but I suppose it's possible that more modern hardware >> might not have a simple way to set it back to character mode. I'll >> enquire. > > I'm most familiar with the ET400. It has locks to prevent inadvertent > access to the special Tseng registers. Some of these locks must be > opened to change the bits to enable fairly standard graphics features. > E.g., there's one for interlace mode. To work on an ET400, you would > have to use the keys for these locks or maybe depend on the X server > leaving everything unlocked. I think there are no standards for the > keys, and more modern graphics cards have more things to lock, so > simply stuffing the VGA registers with standard values is unlikely > to work. I've never had any success with using vidcontrol to fix up > the state on Et4000/W32 or S3 cards after the X server has crashed. Oh well. If it's really that bad, I suppose I would have to give in, but I'll check it out first. BSDI seem to bear you out: in 2.1, if you go into the kernel debugger in X, it plays pretty patterns in the keyboards LEDs. Any opinions on whether this is a good idea or not? Greg From owner-freebsd-hackers Tue Apr 23 05:48:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA29317 for hackers-outgoing; Tue, 23 Apr 1996 05:48:47 -0700 (PDT) Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA29312 for ; Tue, 23 Apr 1996 05:48:45 -0700 (PDT) Received: from fakir.india.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA288553681; Tue, 23 Apr 1996 05:48:23 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA203073634; Tue, 23 Apr 1996 18:17:14 +0530 Message-Id: <199604231247.AA203073634@fakir.india.hp.com> To: Greg Lehey Cc: jkh@time.cdrom.com, hackers@freebsd.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: Your message of "Tue, 23 Apr 1996 13:33:29 MDT." <199604231133.NAA26239@nixpbe.pdb.sni.de> Date: Tue, 23 Apr 1996 18:17:13 +0530 From: A JOSEPH KOSHY Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi >>>>> "gl" == "Greg Lehey" >>>>> gl> even ask. Even if we can only change back to character mode 98% of gl> the time, the other 2% (at least) should give you a dump. Of course, I would advise against trying to "force" a text mode when entering a kernel debugger from graphical mode. On most modern video cards (SVGA and better), you have absolutely no idea what this could do---blowing your monitor is possible as is frying your ramdac. Setting a mode on today's video cards typically have the following steps: a. Reprogramming the clock chip or the PLL's on the DAC for the correct clock speed (these could be > 220Mhz, contrast VGA's 25Mhz). On modern dacs 2-3 PLLS have to be programmed (video clock, system clock, pixel shift clock etc). This is clockchip/DAC specific. b. Reprogramming the CRT registers for the correct frame timings. On many chipsets, these registers are different from the regular VGA registers: eg- Mach8/32/64, P9000, etc. Even `VGA-like' implementations extend their registers differently to get the required number of bits to express functionality eg. Cirrus Logic GDXXXX vs S3 vs WD90XX vs ... This is chipset family and chipset revision specific. c. Programming the DAC from VGA standard (8 bit wide pixel buses) to whatever the board requires (32/64/128 bit connection from DAC to VRAM). This is DAC and board specific. d. On some boards we can have more than one way of programming the chipset/ramdac/clockchip depending on the resolution/depth of frame buffer etc. This depends on the combination of graphics chipset, RAMDAC, clockchip etc. e. Many other board and model specific details. You would have to undo all this in the correct order when you want to switch from a graphical mode to text mode. One possible solution to the problem could be invoke BIOS thru VM86 or some similar facility to force a text mode; I'm not sure whether this would work every time / for every card though. I wonder if BIOS has a "reinitialize hardware" call. Koshy From owner-freebsd-hackers Tue Apr 23 05:59:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA29881 for hackers-outgoing; Tue, 23 Apr 1996 05:59:17 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA29823 for ; Tue, 23 Apr 1996 05:57:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id WAA20624; Tue, 23 Apr 1996 22:31:20 +1000 Date: Tue, 23 Apr 1996 22:31:20 +1000 From: Bruce Evans Message-Id: <199604231231.WAA20624@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, jraynard@dial.pipex.com Subject: Re: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Inspired by Rich Stevens' implementation of system() in his book >"Advanced Programming in the Unix Environment", I've been looking at >the FreeBSD implementation and was struck by the following points:- The POSIX.2 draft has a lot to say about system(). It even gives a complete sample of an implementation. (The draft standard for system() is one of 2 or 3 sections of POSIX.2 that I've seen. Don't ask...) >1. Use of a wait union when an int would do. Good. >2. Use of the soon-to-be-obsolescent vfork() instead of fork(). Reports of its death seem to be premature :-). >3. Returns 0 if fork() fails, when -1 seems more appropriate. It actually returns (127 << 8): >! pstat.w_status = 0; >! pstat.w_retcode = 127; >! return(pstat.w_status); as if the fork had succeeded and the exec had failed. The POSIX sample implementation returns -1. This is better than (127 << 8). The FreeBSD manpage for system() mixes exit statuses with return values in a confusing way. system() never _returns_ 127, because there is no signal 127... >4. The SIGINT and SIGQUIT are not ignored until after the fork(). > If the child runs first, one of these signals could in theory be > generated before the parent gets around to ignoring it. Hence the > dispositions should be changed before the fork(). This is most important. More points: 5. Use of the crufty signal() and deprecated sigblock() and sigsetmask() instead of POSIX signal handling interfaces. It isn't clear whether the sa_mask and sa_flags used by signal() give the correct behaviour. 6. Missing EINTR handling for waitpid(). This might be OK if SA_RESTART was forced, but see point 5 - it is now clear that the sa_flags used by signal() don't give the correct behaviour if the application has used siginterrupt() to change the default of SA_RESTART. >Here's an untested patch which addresses these points. >Comments/corrections welcomed! It seems OK. Some of these points also apply to popen/pclose, but the FreeBSD already seems to be correct although unnecessarily unportable. E.g., it handles EINTR. Bruce From owner-freebsd-hackers Tue Apr 23 06:28:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02247 for hackers-outgoing; Tue, 23 Apr 1996 06:28:02 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA02207 for ; Tue, 23 Apr 1996 06:27:58 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA16986; Tue, 23 Apr 1996 08:25:59 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma016982; Tue Apr 23 08:25:45 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA28005; Tue, 23 Apr 1996 08:29:50 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id IAA18341; Tue, 23 Apr 1996 08:29:45 -0500 (CDT) Message-Id: <199604231329.IAA18341@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Greg Lehey cc: hackers@freebsd.org (FreeBSD hackers) Subject: Re: request for a new "feature" as regards DDB In-reply-to: Your message of "Tue, 23 Apr 1996 09:00:15 MDT." <199604230703.JAA07887@nixpbe.pdb.sni.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 08:29:45 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey writes: > >Good idea. I'll add it to my list. For those who don't know, I had >planned to make some major changes to ddb Real Soon Now. > I can't remember if it was mentioned before, but I'd like to see the hardware debug registers used for memory/io watchpoints. I'll probably whip up something rudimentary in the next couple days, but full blown support in ddb would be nice. BTW has anyone used the watchpoints claimed to be available in ddb? It looks like it goes through the vm system, does that make sense? The man page says that watchpoints on user space work best, what sense does it make to put a kernel watchpoint on a user address? > >On the other subject, changing out of X into character mode: I believe SCO uses dbtty(0|1) to switch from vt0 to sio0 on the fly, they also note that the serial line is not initialized in any way, so if you've got a mouse sitting there, it's now you're console. I'd say this is probably one of the better ways to handle this situation. > >Greg > > eric -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Apr 23 06:47:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03541 for hackers-outgoing; Tue, 23 Apr 1996 06:47:27 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA03513 Tue, 23 Apr 1996 06:47:20 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id JAA01208; Tue, 23 Apr 1996 09:47:15 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id JAA21002; Tue, 23 Apr 1996 09:47:29 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 09:47:28 -0400 (EDT) From: "Marc G. Fournier" To: Greg Lehey cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604231000.MAA20823@nixpbe.pdb.sni.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Greg Lehey wrote: > >>>> So...any way of having an auto-switch to vt0 if the system > >>>> crashes with DDB enabled? > > > > Use syscons. > > I don't understand. Are you saying "syscons auto-switches to vt0 if > the system crashes with DDB enabled", or are you saying "if you use > syscons, you can still change after entering DDB", or are you saying > something else? > Something I found out with this mornings system panic...even with pcvt, you can switch between vt's. I don't know why yesterday after I couldn't, but I would think that the hang yesterday was something more then just a system panic :( As far as the suggestion to use syscons is concerned...has it recently been modified to support vt100 nicely? Does cons50 have the same functionality? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 06:49:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03628 for hackers-outgoing; Tue, 23 Apr 1996 06:49:56 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA03611 for ; Tue, 23 Apr 1996 06:49:12 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id PAA05687 for hackers@freebsd.org; Tue, 23 Apr 1996 15:48:48 +0200 Message-Id: <199604231348.PAA05687@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 23 Apr 96 15:48:33 MDT From: Greg Lehey Cc: lehey.pad@sni.de, hackers@freebsd.org In-Reply-To: <199604231329.IAA18341@jake.lodgenet.com>; from "Eric L. Hernes" at Apr 23, 96 8:29 am X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Greg Lehey writes: >> >> Good idea. I'll add it to my list. For those who don't know, I had >> planned to make some major changes to ddb Real Soon Now. > > I can't remember if it was mentioned before, but I'd like to > see the hardware debug registers used for memory/io watchpoints. This is one of my definite plans. At the risk of repeating what I wrote a couple of months ago, I have already written a kernel debugger (lowbug), which has a number of features lacking in ddb (and vice versa). Hardware breakpointing is one of the lowbug features. > I'll probably whip up something rudimentary in the next couple > days, but full blown support in ddb would be nice. What are you planning to do? > BTW has anyone used the watchpoints claimed to be available in ddb? > It looks like it goes through the vm system, does that make sense? > The man page says that watchpoints on user space work best, what > sense does it make to put a kernel watchpoint on a user address? Why not? One of the things I don't like about ddb (and most other kernel debuggers, for that matter) is that they don't take the user environment into account. Maybe the problem is that the watchpoints slow the kernel down too much. In lowbug, you can set a condition for a breakpoint (or watchpoint, which I prefer to call memory access breakpoints) only to happen on behalf of a specific pid. >> On the other subject, changing out of X into character mode: I believe > > SCO uses dbtty(0|1) to switch from vt0 to sio0 on the fly, This would require appropriate support in the tty driver. I don't know if I like that. > they > also note that the serial line is not initialized in any way, so if > you've got a mouse sitting there, it's now you're console. I'd > say this is probably one of the better ways to handle this situation. Putting the console on the mouse is good? My mouse isn't that intelligent :-) But yes, going serial if the VGA is in X mode is probably a good idea. Greg From owner-freebsd-hackers Tue Apr 23 06:59:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03940 for hackers-outgoing; Tue, 23 Apr 1996 06:59:19 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA03935 for ; Tue, 23 Apr 1996 06:59:17 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.12/8.6.12) id JAA05012; Tue, 23 Apr 1996 09:58:33 -0400 From: Charles Henrich Message-Id: <199604231358.JAA05012@crh.cl.msu.edu> Subject: Re: .forward and sendmail? To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 23 Apr 1996 09:58:33 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, davidg@Root.COM In-Reply-To: <199604230332.FAA21276@uriah.heep.sax.de> from "J Wunsch" at Apr 23, 96 05:32:42 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yes, but think about it. It reads the .forward with the identity of > `daemon', not `root'. Otherwise, any user could link his ~/.forward > to a file read-only for root, and try to figure out the contents of > this file by sending mail to himself, and analyzing the bounces. Not > that this will compromise the entire file, but that's why i wrote: ``I > would call it a security feature.'' Yes but think about it, .forwards WILL NOT WORK USUALLY EVER if sendmail doesnt read .forward's as root! Most home directories are 700! This is a *bug* not a feature. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Tue Apr 23 07:14:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA04825 for hackers-outgoing; Tue, 23 Apr 1996 07:14:30 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA04819 for ; Tue, 23 Apr 1996 07:14:24 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA17685; Tue, 23 Apr 1996 09:12:14 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma017681; Tue Apr 23 09:11:56 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA29404; Tue, 23 Apr 1996 09:16:06 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id JAA20009; Tue, 23 Apr 1996 09:16:04 -0500 (CDT) Message-Id: <199604231416.JAA20009@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Greg Lehey cc: erich@lodgenet.com (Eric L. Hernes), hackers@freebsd.org Subject: Re: request for a new "feature" as regards DDB In-reply-to: Your message of "Tue, 23 Apr 1996 15:48:33 MDT." <199604231348.PAA05671@nixpbe.pdb.sni.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 09:16:04 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey writes: >> > >> I'll probably whip up something rudimentary in the next couple >> days, but full blown support in ddb would be nice. > >What are you planning to do? oh, probably just some simple functions like set_hw_bp(addr, type, size) and clear_hw_bp(addr) where type is as defined in chapter 17 of the pentium book, (0 == execution, 1 == data write, 2 == io read/write, 3 == data read/write) I'll have to enable DE in CR4 for the io port breakpoints, which'll break on anything less than a pentium, but I've only got pentiums here to test with. > >> BTW has anyone used the watchpoints claimed to be available in ddb? >> It looks like it goes through the vm system, does that make sense? >> The man page says that watchpoints on user space work best, what >> sense does it make to put a kernel watchpoint on a user address? > >Why not? One of the things I don't like about ddb (and most other >kernel debuggers, for that matter) is that they don't take the user >environment into account. Maybe the problem is that the watchpoints >slow the kernel down too much. In lowbug, you can set a condition for >a breakpoint (or watchpoint, which I prefer to call memory access >breakpoints) only to happen on behalf of a specific pid. so this is a typical debugging session: 1) run nm on the program to get the address of functions. 2) escape to ddb to set breakpoints 3) run the program 4) play around in ddb 5) continue I've found gdb much easier to debug user programs. Now days you can even attach gdb to the program and get much of the per-process stuff. I don't dispute that there may be times where using a kernel debugger to debug user-space would be useful, maybe even necessary, I just haven't run across them yet. ;) > >>> On the other subject, changing out of X into character mode: I believe >> >> SCO uses dbtty(0|1) to switch from vt0 to sio0 on the fly, > >This would require appropriate support in the tty driver. I don't >know if I like that. well, the tty driver already supports a full blown serial console, so it shouldn't be too tough. > >> they >> also note that the serial line is not initialized in any way, so if >> you've got a mouse sitting there, it's now you're console. I'd >> say this is probably one of the better ways to handle this situation. > >Putting the console on the mouse is good? My mouse isn't that >intelligent :-) But yes, going serial if the VGA is in X mode is >probably a good idea. well, no not on the mouse ;). I was thinking that you'd either set the debug serial port to sio1, or put the mouse there, we'd have source code so it wouldn't be that tough. > >Greg > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Apr 23 07:23:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA05499 for hackers-outgoing; Tue, 23 Apr 1996 07:23:47 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA05485 for ; Tue, 23 Apr 1996 07:23:33 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id QAA08117 for hackers@freebsd.org; Tue, 23 Apr 1996 16:23:22 +0200 Message-Id: <199604231423.QAA08117@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 23 Apr 96 16:23:20 MDT From: Greg Lehey Cc: hackers@freebsd.org (FreeBSD hackers) In-Reply-To: <199604231416.JAA20009@jake.lodgenet.com>; from "Eric L. Hernes" at Apr 23, 96 9:16 am X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> I'll probably whip up something rudimentary in the next couple >>> days, but full blown support in ddb would be nice. >> >> What are you planning to do? > > oh, probably just some simple functions like > set_hw_bp(addr, type, size) and clear_hw_bp(addr) > where type is as defined in chapter 17 of the pentium book, > (0 == execution, 1 == data write, 2 == io read/write, > 3 == data read/write) I'll have to enable DE in CR4 for the io port > breakpoints, which'll break on anything less than a pentium, > but I've only got pentiums here to test with. That's pretty much what lowbug does, except that there were no Pentiums when I wrote it, so no I/O access breakpoints. I suppose I should get hold of the Pentium book... I think that we should consider making these breakpoint forms more generally available (e.g. via ptrace ()). Do you feel like retrofitting gdb to use them? >>> BTW has anyone used the watchpoints claimed to be available in ddb? >>> It looks like it goes through the vm system, does that make sense? >>> The man page says that watchpoints on user space work best, what >>> sense does it make to put a kernel watchpoint on a user address? >> >> Why not? One of the things I don't like about ddb (and most other >> kernel debuggers, for that matter) is that they don't take the user >> environment into account. Maybe the problem is that the watchpoints >> slow the kernel down too much. In lowbug, you can set a condition for >> a breakpoint (or watchpoint, which I prefer to call memory access >> breakpoints) only to happen on behalf of a specific pid. > > so this is a typical debugging session: > 1) run nm on the program to get the address of functions. > 2) escape to ddb to set breakpoints > 3) run the program > 4) play around in ddb > 5) continue I wouldn't call that a typical debugging sesseion. First, one of my intentions is to have the addresses of the functions available to ddb (they are to lowbug at the moment, though the implementation is pretty kludgy). Secondly, the ptrace () interface should also be able to specify whether you want a user-level or system-level breakpoint (i.e. does hitting the breakpoint stop the process or the kernel?). Thirdly, you would never want to use a kernel debugger to do things which a user-level debugger can do. But if you're debugging a system call, it's nice to be able to follow it back to the user level. > I've found gdb much easier to debug user programs. Now days you > can even attach gdb to the program and get much of the per-process > stuff. Is this available on FreeBSD? I hadn't noticed... > I don't dispute that there may be times where using a kernel > debugger to debug user-space would be useful, maybe even necessary, > I just haven't run across them yet. ;) See above for one scenario. I think we're in agreement. >>>> On the other subject, changing out of X into character mode: I believe >>> >>> SCO uses dbtty(0|1) to switch from vt0 to sio0 on the fly, >> >> This would require appropriate support in the tty driver. I don't >> know if I like that. > > well, the tty driver already supports a full blown serial console, so > it shouldn't be too tough. Probably. Last time we talked about ddb, we were in agreement that we needed serial capability as well. >>> they also note that the serial line is not initialized in any way, >>> so if you've got a mouse sitting there, it's now you're console. >>> I'd say this is probably one of the better ways to handle this >>> situation. > >> Putting the console on the mouse is good? My mouse isn't that >> intelligent :-) But yes, going serial if the VGA is in X mode is >> probably a good idea. > > well, no not on the mouse ;). I was thinking that you'd either set > the debug serial port to sio1, or put the mouse there, we'd have > source code so it wouldn't be that tough. Sure. The idea would be to connect to another machine running gdb or a user-level version of ddb. Greg From owner-freebsd-hackers Tue Apr 23 07:45:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07479 for hackers-outgoing; Tue, 23 Apr 1996 07:45:57 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07460 for ; Tue, 23 Apr 1996 07:45:48 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA18144; Tue, 23 Apr 1996 09:43:54 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma018138; Tue Apr 23 09:43:51 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA30205; Tue, 23 Apr 1996 09:48:01 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id JAA21041; Tue, 23 Apr 1996 09:47:59 -0500 (CDT) Message-Id: <199604231447.JAA21041@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Greg Lehey cc: erich@lodgenet.com (Eric L. Hernes), hackers@freebsd.org (FreeBSD hackers) Subject: Re: request for a new "feature" as regards DDB In-reply-to: Your message of "Tue, 23 Apr 1996 16:23:20 MDT." <199604231423.QAA08113@nixpbe.pdb.sni.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 09:47:59 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey writes: > >I think that we should consider making these breakpoint forms more >generally available (e.g. via ptrace ()). Do you feel like >retrofitting gdb to use them? > Yea, that'd be ok. I was planning to prototype it as an lkm, but maybe a wart on ptrace() would be just as easy. >I wouldn't call that a typical debugging sesseion. First, one of my >intentions is to have the addresses of the functions available to ddb >(they are to lowbug at the moment, though the implementation is pretty >kludgy). Secondly, the ptrace () interface should also be able to >specify whether you want a user-level or system-level breakpoint >(i.e. does hitting the breakpoint stop the process or the kernel?). >Thirdly, you would never want to use a kernel debugger to do things >which a user-level debugger can do. But if you're debugging a system >call, it's nice to be able to follow it back to the user level. I understand now. I have traced user-space through to a system call and back, but it was kind of a pain. > >> I've found gdb much easier to debug user programs. Now days you >> can even attach gdb to the program and get much of the per-process >> stuff. > >Is this available on FreeBSD? I hadn't noticed... > yup, needs procfs though, usually not a problem. > >Greg > -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Apr 23 07:50:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07858 for hackers-outgoing; Tue, 23 Apr 1996 07:50:36 -0700 (PDT) Received: from haven.uchicago.edu (root@haven.uchicago.edu [128.135.12.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07851 Tue, 23 Apr 1996 07:50:33 -0700 (PDT) Received: from midway.uchicago.edu (root@midway.uchicago.edu [128.135.12.12]) by haven.uchicago.edu (8.6.12/8.6.4) with ESMTP id JAA18925; Tue, 23 Apr 1996 09:50:15 -0500 Received: from woodlawn.uchicago.edu (csdayton@woodlawn.uchicago.edu [128.135.12.9]) by midway.uchicago.edu (8.7.3/8.7.2) with ESMTP id JAA12880; Tue, 23 Apr 1996 09:50:22 -0500 (CDT) Message-Id: <199604231450.JAA12880@midway.uchicago.edu> In-reply-to: Ollivier Robert's message of Tue, 23 Apr 1996 01:37:10 +0200 (MET DST) To: Ollivier Robert cc: henrich@crh.cl.msu.edu, freebsd-hackers@freebsd.org, jmb@freefall.freebsd.org (Jonathan M. Bresler) Subject: Re: .forward and sendmail? Reply-To: csdayton@midway.uchicago.edu References: <199604222337.BAA02230@keltia.freenix.fr> Date: Tue, 23 Apr 1996 09:50:30 CDT From: Soren Dayton Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It seems that Jonathan M. Bresler said: > > regardless of the permissions. it needs to append to people's > > Appending messages is the work of the local mailer, not sendmail. > > > -r-sr-sr-x 3 root kmem 245760 Mar 10 18:25 /usr/sbin/sendmail > > The setgid is unnecessary as sendmail in -CURRENT has been patched to use > another method than reading kmem for gettting the load average. has this been sent to Eric Allman so that it can get incorporated into that sendmail? I would be much more comfortable running the latest from him rather than whatever is in a particular release Soren Dayton From owner-freebsd-hackers Tue Apr 23 08:03:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA08852 for hackers-outgoing; Tue, 23 Apr 1996 08:03:49 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA08321 for ; Tue, 23 Apr 1996 07:58:30 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id QAA10922 for hackers@freebsd.org; Tue, 23 Apr 1996 16:58:02 +0200 Message-Id: <199604231458.QAA10922@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 23 Apr 96 16:58:00 MDT From: Greg Lehey Cc: hackers@freebsd.org (FreeBSD hackers) In-Reply-To: <199604231447.JAA21041@jake.lodgenet.com>; from "Eric L. Hernes" at Apr 23, 96 9:47 am X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Greg Lehey writes: >> >> I think that we should consider making these breakpoint forms more >> generally available (e.g. via ptrace ()). Do you feel like >> retrofitting gdb to use them? > > Yea, that'd be ok. I was planning to prototype it as an lkm, but > maybe a wart on ptrace() would be just as easy. OK, let's take this offline. I'm copying hackers for the last time. If anybody else is interested in the discussion, please reply and I'll copy you. I don't see the need for an lkm (but then, I don't have much of a feel for lkms, so I could be completely wrong). There's not too much code involved on the kernel side, the way I see it: we need calls to: 1. Set different kinds of breakpoints (I/O read, I/O write, Instruction fetch, Memory read, Memory write). 2. Specify address space (kernel, user, which user?) for memory references. 3. Specify what to do when you hit a breakpoint (inform a process, or drop into ddb). 4. Perform a minimal set of conditional checks. Setting conditional breakpoints in gdb is very expensive, and if you have a breakpoint in kernel space, it could become significantly more expensive. 5. Perform some kind of recovery from recursive breakpoints hits (what happens if you hit a breakpoint while handling breakpoint code?). I have code like that in lowbug, and it's surprisingly simple. Any other ideas? On the user (gdb) side, there's more work. I looked at it a while ago, and it was more work than I was prepared to undertake at the time. Maybe you have better ideas about this aspect. Greg From owner-freebsd-hackers Tue Apr 23 08:23:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA10321 for hackers-outgoing; Tue, 23 Apr 1996 08:23:33 -0700 (PDT) Received: from gateway.zeus.leitch.com (gateway.zeus.leitch.com [205.210.38.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA10315 for ; Tue, 23 Apr 1996 08:23:29 -0700 (PDT) Received: from tap.zeus.leitch.com (tap.zeus.leitch.com [204.187.60.10]) by gateway.zeus.leitch.com (8.6.12/8.6.9) with ESMTP id LAA20457 for ; Tue, 23 Apr 1996 11:35:14 -0400 Received: from ale.zeus.leitch.com (ale.zeus.leitch.com [204.187.61.65]) by tap.zeus.leitch.com (8.6.12/8.6.6) with ESMTP id LAA10548 for ; Tue, 23 Apr 1996 11:23:55 -0400 From: Dave Chapeskie Received: (dchapes@localhost) by ale.zeus.leitch.com (8.6.12/8.6.9) id LAA03601 for hackers@freebsd.org; Tue, 23 Apr 1996 11:23:54 -0400 Message-Id: <199604231523.LAA03601@ale.zeus.leitch.com> Subject: Device Driver ioctl() help To: hackers@freebsd.org Date: Tue, 23 Apr 1996 11:23:54 -0400 (EDT) In-Reply-To: <199604230256.EAA20717@uriah.heep.sax.de> X-Mailer: ELM [version 2.4ME+ PL14 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199604230256.EAA20717@uriah.heep.sax.de> joerg_wunsch@uriah.heep.sax.de writes: >As Dave Chapeskie wrote: > >> >#define JOY_SETTIMEOUT _IOW('J', 1, int) /* set timeout */ >> [...] >> > Ok, it looks like the 'J' has something to do with a "group", >> >but what kind of group? How is this value chosen and what does it do? >> >> Get a good book on writing device drivers. Typically you just use >> group 0 unless you know what you're doing. _IO is used when no data is > >Hmm, i think the idea behind the `group' (and partially the `cmd') >value is to be semi-random, in order to reduce the probability of an >accidental ioctl name space clash with the ioctl of a foreign driver. >(Since BSD also encodes the lenth and IO direction of the third >parameter into the actual CMD, name space collisions are seldom >compared to V7 UNIX anyway.) The convention was to pick a letter that >is roughly related to your driver as `group'. That's why the joystick >driver is using `J'. Certainly there is nothing obviously wrong with choosing any value you like for the group. However one should never rely on this to produce a unique value for the ioctl request. You must still manually make sure you do not use any JOY_* requests on anything other than a file descriptor of the joystick device. Therefore using an arbitrary value in an attempt to generate a unique value, while not wrong, is not very useful. My understanding of the use of the group argument is if you have different types of ioctls in a single driver that you want to handle differently. For example I have a driver that has three different groups of ioctls and it does some generic processing based on the group before it looks at what specific request it is. Another use, and perhaps the only "correct" one, is if you have a group of ioctls that may be used by multiple drivers. For example group 't' is defined for TIOC* ioctls on tty devices. It may be that you want/need to support some of these in your device driver and you don't want to worry about possible conflicts in the ioctl request number between the TIOC* requests and your own requests. >I think this is already covered well in the old ``Daemon book'' (The >4.3BSD Operating System. Design and Implementation.) Don't use a I admit I've never read anything definitive on the use of ioctl group numbers, I'm just presenting my own opinions on the matter. >From "DEC OSF/1 Writing Device Drivers: Reference" (my closest BSDish reference book, regrettably I can't find any of my BSD books at the moment): "Specifies the group that this ioctl type belongs to. This argument must be a nonnegative 8-bit number (that is, in the range 0-255 inclusive). You can pass the value zero (0) to this argument if a new ioctl group is not being defined." "Specifies the specific ioctl type within the group. These should be sequentially assigned numbers for each different ioctl operation the driver supports. This argument must be a nonnegative 8-bit number (that is, in the range 0-255 inclusive)." -- Dave Chapeskie Leitch Technology International Inc. Email: dchapes@zeus.leitch.com From owner-freebsd-hackers Tue Apr 23 08:23:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA10357 for hackers-outgoing; Tue, 23 Apr 1996 08:23:54 -0700 (PDT) Received: from DeepCore.dk (aalb10.pip.dknet.dk [194.192.0.170]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA10343 for ; Tue, 23 Apr 1996 08:23:44 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.5/8.7.3) id RAA11669 for hackers@freebsd.org; Tue, 23 Apr 1996 17:22:46 +0200 (MET DST) Message-Id: <199604231522.RAA11669@DeepCore.dk> Subject: Novell Mail gateway - anyone ?? To: hackers@freebsd.org (FreeBSD hackers) Date: Tue, 23 Apr 1996 17:22:45 +0200 (MET DST) From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anybody know of a solution that can bridge between smtp & the mail protocoll used under Novell ?? It doesn't hurt if its free :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Tue Apr 23 09:05:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA13973 for hackers-outgoing; Tue, 23 Apr 1996 09:05:50 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA13968 Tue, 23 Apr 1996 09:05:48 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA29626; Tue, 23 Apr 1996 11:05:16 -0500 From: Joe Greco Message-Id: <199604231605.LAA29626@brasil.moneng.mei.com> Subject: Re: Novell Mail gateway - anyone ?? To: sos@freebsd.org Date: Tue, 23 Apr 1996 11:05:16 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199604231522.RAA11669@DeepCore.dk> from "sos@freebsd.org" at Apr 23, 96 05:22:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Anybody know of a solution that can bridge between smtp & the > mail protocoll used under Novell ?? It doesn't hurt if its free :) I don't know what the "mail protocol used under Novell" is, but I know a lot of people running Mercury Mail on the Novell server side to handle inbound SMTP, and running things like Pegasus to handle reading on the Novell clients. Works fine from what I can tell. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-hackers Tue Apr 23 10:15:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA19175 for hackers-outgoing; Tue, 23 Apr 1996 10:15:02 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA19157 for ; Tue, 23 Apr 1996 10:14:56 -0700 (PDT) Received: (from jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) id KAA17902; Tue, 23 Apr 1996 10:14:54 -0700 (PDT) To: freebsd-hackers@freebsd.org Path: not-for-mail From: jdp@polstra.com (John Polstra) Newsgroups: polstra.freebsd.hackers Subject: Re: Help! I need info on pthreads. Date: 23 Apr 1996 10:14:54 -0700 Organization: Polstra & Co., Seattle, WA Lines: 27 Distribution: local Message-ID: <4lj36e$hfb@austin.polstra.com> References: <199604230013.KAA18978@melb.werple.net.au> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199604230013.KAA18978@melb.werple.net.au>, John Birrell wrote: > > I haven't looked for books on how to use pthreads. I'm from an OSF/1 > environment where we used DEC's poor examples as a start. Their bookreader > docs aren't too bad at describing the functions, but they are not good > at describing how to design a threaded application. There's a really superb article on exactly that at: http://gatekeeper.dec.com/pub/DEC/SRC/research-reports/abstracts/src-rr-035.html It's by Andrew D. Birrell. (Who's he, John, your long lost brother? :-) Incidentally, it is a technical report from DEC's Systems Research Center. They have many excellent TRs on interesting topics. You can find an index of them at: http://www.research.digital.com/SRC/publications/src-rr.html Almost all of them are available in Postscript form. They'll also mail you paper copies and/or associated videos, for free. It's a great service! -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Tue Apr 23 10:46:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21084 for hackers-outgoing; Tue, 23 Apr 1996 10:46:22 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA21073 for ; Tue, 23 Apr 1996 10:46:16 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.5/BSD4.4) id DAA14481 Wed, 24 Apr 1996 03:43:25 +1000 (EST) From: michael butler Message-Id: <199604231743.DAA14481@asstdc.scgt.oz.au> Subject: Re: .forward and sendmail? To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 24 Apr 1996 03:43:23 +1000 (EST) Cc: hackers@freebsd.org In-Reply-To: <199604231358.JAA05012@crh.cl.msu.edu> from "Charles Henrich" at Apr 23, 96 09:58:33 am X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Henrich writes: > Yes but think about it, .forwards WILL NOT WORK USUALLY EVER if sendmail > doesnt read .forward's as root! Most home directories are 700! This is a > *bug* not a feature. sarah:~ % pwd /var/home/imb sarah:~ % cd .. sarah:/var/home % ls -ld imb drwx------ 18 imb staff 2048 Apr 21 05:35 imb sarah:/var/home % cd sarah:~ % ll .forward -rw-rw-r-- 1 imb staff 20 Feb 16 02:56 .forward sarah:~ % cat .forward \imb imb@scgt.oz.au .. works just fine for me on -stable with sendmail 8.7.5 and no overrides on where .forward files can be, i.e. default sendmail configuration, michael From owner-freebsd-hackers Tue Apr 23 11:01:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA21861 for hackers-outgoing; Tue, 23 Apr 1996 11:01:09 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA21856 for ; Tue, 23 Apr 1996 11:01:05 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.12/8.6.12) id OAA06040; Tue, 23 Apr 1996 14:00:47 -0400 From: Charles Henrich Message-Id: <199604231800.OAA06040@crh.cl.msu.edu> Subject: Re: .forward and sendmail? To: imb@scgt.oz.au (michael butler) Date: Tue, 23 Apr 1996 14:00:46 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199604231743.DAA14481@asstdc.scgt.oz.au> from "michael butler" at Apr 24, 96 03:43:23 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > sarah:~ % pwd > /var/home/imb > sarah:~ % cd .. > sarah:/var/home % ls -ld imb > drwx------ 18 imb staff 2048 Apr 21 05:35 imb > sarah:/var/home % cd > sarah:~ % ll .forward > -rw-rw-r-- 1 imb staff 20 Feb 16 02:56 .forward > sarah:~ % cat .forward > \imb > imb@scgt.oz.au > > .. works just fine for me on -stable with sendmail 8.7.5 and no overrides > on where .forward files can be, i.e. default sendmail configuration, Okay, sendmail is playing games, apparently if the file is owned by root, sendmail will ignore it, else it does read it regardless of permissions. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Tue Apr 23 11:44:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA24783 for hackers-outgoing; Tue, 23 Apr 1996 11:44:16 -0700 (PDT) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA24777 Tue, 23 Apr 1996 11:44:13 -0700 (PDT) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id UAA12390 ; Tue, 23 Apr 1996 20:44:11 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id UAA16345 ; Tue, 23 Apr 1996 20:44:10 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.7) id UAA16782; Tue, 23 Apr 1996 20:21:32 +0200 (MET DST) From: Ollivier Robert Message-Id: <199604231821.UAA16782@keltia.freenix.fr> Subject: Re: .forward and sendmail? To: csdayton@midway.uchicago.edu Date: Tue, 23 Apr 1996 20:21:31 +0200 (MET DST) Cc: henrich@crh.cl.msu.edu, freebsd-hackers@freebsd.org, jmb@freefall.freebsd.org In-Reply-To: <199604231450.JAA12880@midway.uchicago.edu> from Soren Dayton at "Apr 23, 96 09:50:30 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1916 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that Soren Dayton said: > has this been sent to Eric Allman so that it can get incorporated into > that sendmail? I would be much more comfortable running the latest from > him rather than whatever is in a particular release After reading the CVS log, it seems that nothing was done in sendmail "per se" as it is simply that it does not need the setgid anymore. The setgid was here to enable sendmail to get the load average (with reading /dev/kmem) and the current getloadavg(3) function is now using sysctl(2) which can be used without privilege for that purpose ------------------------------------------------------------ revision 1.8 date: 1996/01/29 13:19:49; author: mpp; state: Exp; lines: +1 -2 Don't install sendmail setgid kmem since it doesn't really require kmem access. It is currently configured to call getloadavg(3), which uses sysctl(2) to determine the load average, which is the only reason some sendmails require kmem access. ------------------------------------------------------------ -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #13: Sun Apr 21 18:14:54 MET DST 1996 From owner-freebsd-hackers Tue Apr 23 11:56:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25782 for hackers-outgoing; Tue, 23 Apr 1996 11:56:39 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA25774 for ; Tue, 23 Apr 1996 11:56:21 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA20596; Tue, 23 Apr 1996 20:33:56 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA13541; Tue, 23 Apr 1996 20:33:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA23187; Tue, 23 Apr 1996 19:28:54 +0200 (MET DST) From: J Wunsch Message-Id: <199604231728.TAA23187@uriah.heep.sax.de> Subject: Re: .forward and sendmail? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 23 Apr 1996 19:28:53 +0200 (MET DST) Cc: henrich@crh.cl.msu.edu (Charles Henrich) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604231358.JAA05012@crh.cl.msu.edu> from "Charles Henrich" at Apr 23, 96 09:58:33 am X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > Yes but think about it, .forwards WILL NOT WORK USUALLY EVER if > sendmail doesnt read .forward's as root! Most home directories are > 700! This is a *bug* not a feature. You might call it a bug. Make your home dirs 0711, or use a separate alias database, or make your sendmail vulnerable if you don't like it. Eric Allman's READ_ME makes it absolutely clear that he considers it a security feature: HASSETREUID Define this if you have setreuid(2) ***AND*** root can use setreuid to change to an arbitrary user. [...] [...] Setting this improves the security, since sendmail doesn't have to read .forward and :include: files as root. There are certain attacks that may be unpreventable without this call. I don't think you will find anybody here supporting your opinion. -- 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 Apr 23 12:37:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28665 for hackers-outgoing; Tue, 23 Apr 1996 12:37:59 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28642 Tue, 23 Apr 1996 12:37:50 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA22528; Tue, 23 Apr 1996 21:37:26 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA14151; Tue, 23 Apr 1996 21:37:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA23869; Tue, 23 Apr 1996 20:39:13 +0200 (MET DST) From: J Wunsch Message-Id: <199604231839.UAA23869@uriah.heep.sax.de> Subject: Mailer problem To: cstruble@quirk.com, kieber@sax.sax.de, freebsd-hackers@freebsd.org (FreeBSD hackers), freebsd-current@freebsd.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 20:39:12 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ick. ``How can you shoot in your foot?'' -- ``Create a bogus .forward.'' I've lost a dozen mails due to this that have been sent from the adressees of this message. If it's been something important, please resend 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 Tue Apr 23 12:41:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA29019 for hackers-outgoing; Tue, 23 Apr 1996 12:41:16 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29012 Tue, 23 Apr 1996 12:41:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA20121; Tue, 23 Apr 1996 12:36:03 -0700 From: Terry Lambert Message-Id: <199604231936.MAA20121@phaeton.artisoft.com> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Tue, 23 Apr 1996 12:36:03 -0700 (MST) Cc: lehey.pad@sni.de, smpatel@umiacs.UMD.EDU, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199604230928.TAA12645@godzilla.zeta.org.au> from "Bruce Evans" at Apr 23, 96 07:28:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >why ddb shouldn't understand enough about generic VGA to be able to > >put it back in 25x80 mode. Somewhere I have a little program which I > >used to do this under BSD/386 0.3, where the X server wasn't always > >successful. It's only a few lines. I'm sure somebody's going to come > >up with "yes, but that's not completely generic", but I don't think > >this is an adequate argument. Make it a config option for ddb, and > > "yes, but that's not completely generic" :-). I can't tell if Bruce is making fun of me or not. 8-). But that's not completely generic. > >it'll handle 98% of all hardware. If somebody with the other 2% > >wants, they can do it for that hardware as well. > > It'll only handle 98% of all hardware that is running in a VGA compatible > mode. I guess most X modes aren't VGA compatible. They aren't. Anything which programs the clocks not through a kernel model is not state-recoverable by kernel code (like DDB). The kernel debugger was almost the primary reason for suggesting a kernel DDX. Now that Plan 9 has abstracted the card specific drivers into the kernel (/dev/vga, /dev/bitblt, etc.) and the Linux community has a "GGI" project in the works, FreeBSD has less and less of an excuse. 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 Apr 23 12:43:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA29180 for hackers-outgoing; Tue, 23 Apr 1996 12:43:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29172 for ; Tue, 23 Apr 1996 12:43:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA20138; Tue, 23 Apr 1996 12:39:10 -0700 From: Terry Lambert Message-Id: <199604231939.MAA20138@phaeton.artisoft.com> Subject: Re: Help! I need info on pthreads. To: kaleb@x.org (Kaleb S. KEITHLEY) Date: Tue, 23 Apr 1996 12:39:09 -0700 (MST) Cc: hackers@freefall.freebsd.org In-Reply-To: <199604231022.GAA03612@exalt.x.org> from "Kaleb S. KEITHLEY" at Apr 23, 96 06:22:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I have suddenly been informed that I must convert a significant > > > piece of code to use pthreads. Since FreeBSD will be one of my > > > test vehicles I need to know if the libc_r library under 2.1-stable > > > and/or current is working. > > > > 2.2-current only. It works for me. If it doesn't work for _you_, let > > me know. Watch out for libc functions that aren't re-entrant, though. > > You mean watch out for libc functions that aren't MT-safe. There's a big > difference between being MT-safe and being reentrant. Reentrant means > the function can be called in a signal handler, usually limited to system > calls. MT-safe means the function can be called by more than one thread > at a time. On other systems with threads there are MT-safe functions that > aren't reentrant. Other systems have real threads instead of signal-based context switching. 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 Apr 23 13:02:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA00764 for hackers-outgoing; Tue, 23 Apr 1996 13:02:24 -0700 (PDT) Received: from ki.net (ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA00744 Tue, 23 Apr 1996 13:02:09 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA07218; Tue, 23 Apr 1996 16:01:40 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA23237; Tue, 23 Apr 1996 16:02:05 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 16:02:04 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: hackers@freebsd.org Subject: Intelligent Debugging Tools... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... What would it take to either create software for debugging hardware, and/or add appropriate debugging to the kernel that would improve debugging of hardware problems? Erk...as far as software is concerned, maybe something that you could run in single user mode that would completely thrash the RAM, doing read/writes to *all* the memory looking for any corruption? Or something else that could be turned on against /dev/rsd0b to totally thrash the swap space on a drive? As far as the kernel is concerned, I'm getting panics in VM and keep getting told its hardware problems...fine, but there *has* to be a better way of isolating the problem then replacing bits and pieces until the problem seems to go away. For instance, when I get a VM fault...what exactly *is* the problem? Is it a problem with the swap space (ie. hard drives) or RAM? My -stable machine is a 4 month old computer, and all the parts are new in her...last I've been asked is "when am I going to replace the machine"...replace it with what? its all new...if there was some way of narrowing down the offending parts and replacing those, that would be great...but just going out and buying a new machine is not the answer, cause the part that is wrong with *this* machine might exist in the next machine *shrug* Does this make any sense? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 13:22:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02334 for hackers-outgoing; Tue, 23 Apr 1996 13:22:00 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA02249 for ; Tue, 23 Apr 1996 13:20:57 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id LAA21817 for hackers@freebsd.org; Tue, 23 Apr 1996 11:52:37 -0700 (PDT) Date: Tue, 23 Apr 1996 11:52:37 -0700 (PDT) From: Julian Elischer Message-Id: <199604231852.LAA21817@ref.tfs.com> To: hackers@freebsd.org Subject: ps dies with FP exception. Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk anyone else getting this? under -current.. I will shortly recompile the kernel as well, but ps alx works ps aux dies julian (ps sources as of this morning)(but it did this last week already) From owner-freebsd-hackers Tue Apr 23 13:24:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02606 for hackers-outgoing; Tue, 23 Apr 1996 13:24:18 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA02447 for ; Tue, 23 Apr 1996 13:23:39 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id PAA20222; Mon, 22 Apr 1996 15:44:24 -0700 (PDT) Message-Id: <199604222244.PAA20222@ref.tfs.com> Subject: Re: Flaws in system() implementation? To: jraynard@dial.pipex.com (James Raynard) Date: Mon, 22 Apr 1996 15:44:24 -0700 (PDT) From: "JULIAN Elischer" Cc: hackers@freebsd.org In-Reply-To: <199604222142.VAA00923@dial.pipex.com> from "James Raynard" at Apr 22, 96 09:42:43 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Inspired by Rich Stevens' implementation of system() in his book > "Advanced Programming in the Unix Environment", I've been looking at > the FreeBSD implementation and was struck by the following points:- > > 1. Use of a wait union when an int would do. This is the correct POSIX thing to do.. check the man page for wait. > > > 3. Returns 0 if fork() fails, when -1 seems more appropriate. POSIX says: If "command" is a null pointer, the system() function returns non-zero only if a command processor is available. If "command" is a nin null pointer the system() function returnsa the termination status of the command language interpretter in the format specified by the waitpid() function. [...] If a child process cannot be created, or if the termination status of hte command interpretter cannot be obtained system() returns -1 and sets errno to indicate the error. > > 4. The SIGINT and SIGQUIT are not ignored until after the fork(). > If the child runs first, one of these signals could in theory be the child MUST run first in vfork() > generated before the parent gets around to ignoring it. Hence the > dispositions should be changed before the fork(). > > Here's an untested patch which addresses these points. > Comments/corrections welcomed! > > (In /usr/src/lib/libc/stdlib) > *** system.c~ Mon Apr 22 21:04:59 1996 > --- system.c Mon Apr 22 21:20:18 1996 > *************** > *** 46,76 **** > system(command) > const char *command; > { > - union wait pstat; > pid_t pid; > ! int omask; > sig_t intsave, quitsave; > > if (!command) /* just checking... */ > return(1); > > omask = sigblock(sigmask(SIGCHLD)); > ! switch(pid = vfork()) { > case -1: /* error */ > ! (void)sigsetmask(omask); > ! pstat.w_status = 0; > ! pstat.w_retcode = 127; > ! return(pstat.w_status); > case 0: /* child */ > (void)sigsetmask(omask); > execl(_PATH_BSHELL, "sh", "-c", command, (char *)NULL); > _exit(127); > } > - intsave = signal(SIGINT, SIG_IGN); > - quitsave = signal(SIGQUIT, SIG_IGN); > - pid = waitpid(pid, (int *)&pstat, 0); > (void)sigsetmask(omask); > (void)signal(SIGINT, intsave); > (void)signal(SIGQUIT, quitsave); > ! return(pid == -1 ? -1 : pstat.w_status); > } > --- 46,77 ---- > system(command) > const char *command; > { > pid_t pid; > ! int omask, pstat; > sig_t intsave, quitsave; > > if (!command) /* just checking... */ > return(1); > > + intsave = signal(SIGINT, SIG_IGN); > + quitsave = signal(SIGQUIT, SIG_IGN); > omask = sigblock(sigmask(SIGCHLD)); > ! switch(pid = fork()) { > case -1: /* error */ > ! break; > case 0: /* child */ > (void)sigsetmask(omask); > + (void)signal(SIGINT, intsave); > + (void)signal(SIGQUIT, quitsave); > execl(_PATH_BSHELL, "sh", "-c", command, (char *)NULL); > _exit(127); > + default: /* parent */ > + pid = waitpid(pid, &pstat, 0); > + break; > } > (void)sigsetmask(omask); > (void)signal(SIGINT, intsave); > (void)signal(SIGQUIT, quitsave); > ! return(pid == -1 ? -1 : pstat); > } > From owner-freebsd-hackers Tue Apr 23 14:45:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09376 for hackers-outgoing; Tue, 23 Apr 1996 14:45:07 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09364 Tue, 23 Apr 1996 14:45:00 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id OAA23611; Tue, 23 Apr 1996 14:43:25 -0700 Message-Id: <199604232143.OAA23611@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Marc G. Fournier" cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 16:02:04 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 14:43:25 -0700 From: "Amancio Hasty Jr." Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, It will help if you post your hardware configuration. A few months ago there was a nasty PCI interaction in the kernel which caused my system to crash so glad that whatever it was is gone 8) Cheers, Amancio >>> "Marc G. Fournier" said: > > Hi... > > What would it take to either create software for debugging > hardware, and/or add appropriate debugging to the kernel that would > improve debugging of hardware problems? > > Erk...as far as software is concerned, maybe something that > you could run in single user mode that would completely thrash the > RAM, doing read/writes to *all* the memory looking for any corruption? > Or something else that could be turned on against /dev/rsd0b to totally > thrash the swap space on a drive? > > As far as the kernel is concerned, I'm getting panics in VM > and keep getting told its hardware problems...fine, but there *has* > to be a better way of isolating the problem then replacing bits and > pieces until the problem seems to go away. For instance, when I get > a VM fault...what exactly *is* the problem? Is it a problem with > the swap space (ie. hard drives) or RAM? > > My -stable machine is a 4 month old computer, and all the > parts are new in her...last I've been asked is "when am I going to > replace the machine"...replace it with what? its all new...if there > was some way of narrowing down the offending parts and replacing > those, that would be great...but just going out and buying a new machine > is not the answer, cause the part that is wrong with *this* machine > might exist in the next machine *shrug* > > Does this make any sense? > > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org > > From owner-freebsd-hackers Tue Apr 23 15:00:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA10493 for hackers-outgoing; Tue, 23 Apr 1996 15:00:31 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA10444 Tue, 23 Apr 1996 15:00:17 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA01865; Tue, 23 Apr 1996 18:00:09 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA02308; Tue, 23 Apr 1996 18:00:07 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 18:00:06 -0400 (EDT) From: "Marc G. Fournier" To: "Amancio Hasty Jr." cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604232143.OAA23611@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Amancio Hasty Jr. wrote: > Hi, > > It will help if you post your hardware configuration. A few months > ago there was a nasty PCI interaction in the kernel which caused > my system to crash so glad that whatever it was is gone 8) > dmesg: FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 scrappy@ki.net:/usr/src/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14835712 (14488K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 12 on pci0:11 (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1222MB (2503872 512 byte sectors) (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 327MB (670506 512 byte sectors) (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 234MB (479350 512 byte sectors) (ncr0:3:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 sd3(ncr0:3:0): Direct-Access sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1013MB (2074880 512 byte sectors) vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 not probed due to I/O address conflict with sio0 at 0x3f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sctarg0(noadapter::): Processor Target The NCR controller is one of the ASUS SC-200 controllers, the vga0 device is an ATI Mach64 4MB PCI, and the sio1 conflict is a misconfiguration on my part in this newest kernel that I have to fix. Oh, the motherboard is an ACER AP43 with a 486DX4-100 CPU, and sio[01] are both onboard serial. The memory is one 16Meg SIMM, and pstat shows: Device 1K-blocks Used Avail Capacity Type /dev/sd0b 51200 6880 44256 13% Interleaved /dev/sd1b 32768 6936 25768 21% Interleaved /dev/sd2b 32768 6960 25744 21% Interleaved /dev/sd3b 102400 6904 95432 7% Interleaved Total 218880 27680 191200 13% Any other information that may be pertinent? helpful? I'm running just about everything on this machine...named, innd, YP, nfs-server and PPP: PID TT STAT TIME COMMAND 0 ?? DLs 0:00.00 (swapper) 1 ?? IWs 0:00.40 /sbin/init -- 2 ?? DL 0:17.60 (pagedaemon) 3 ?? DL 0:05.23 (vmdaemon) 4 ?? DL 0:12.49 (update) 78 ?? Ss 0:00.45 routed -q 102 ?? Ss 0:03.46 syslogd 105 ?? SWs 0:07.72 named 110 ?? IWs 0:00.14 portmap 113 ?? IWs 0:05.73 ypserv 116 ?? IWs 0:00.02 yppasswdd -s -f 120 ?? Ss 0:00.74 rwhod 124 ?? IWs 0:00.09 mountd 126 ?? IWs 0:00.02 nfsd: master (nfsd) 128 ?? S 0:47.11 nfsd: server (nfsd) 129 ?? IW 0:05.28 nfsd: server (nfsd) 130 ?? IW 0:00.85 nfsd: server (nfsd) 131 ?? IW 0:00.25 nfsd: server (nfsd) 138 ?? Ss 0:00.90 inetd 145 ?? Ss 0:00.62 cron 149 ?? IWs 0:00.82 (sendmail) 184 ?? Ss 0:06.29 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 187 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 188 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 208 ?? DNs 12:39.57 /news/admin/etc/innd -p4 -i0 218 ?? IWs 0:00.01 /usr/local/lib/pg95/bin/postmaster -S (postgres) 583 ?? IWN 0:00.91 -204.17.53.78 LIST 860 ?? IWs 0:01.28 SCREEN -R (screen-3.7.1) 999 ?? IW 0:00.09 rshd 1000 ?? IW 0:01.11 /etc/rimapd 1293 ?? IW 0:00.27 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 1495 ?? DN 0:09.59 /news/bin/overchan 1496 ?? SN 0:09.38 /usr/local/bin/perl /news/stats/bin/flowsum.channel 1551 ?? IW 0:00.18 (ftpd) 1553 ?? IW 0:00.20 (ftpd) 1686 ?? IWN 0:00.25 sh -c \n^IBATCHFILE=${HOST}.nntp\n^ILOCK=${LOCKS}/LOC 1719 ?? SN 0:06.78 innxmit -a -t300 -T1800 news.trends.ca /news/spool/ou 1792 ?? IW 0:00.10 (sendmail) 1808 ?? IW 0:00.06 (sendmail) 1824 ?? IW 0:00.22 (ftpd) 863 p0 IWs+ 0:00.58 -bin/tcsh 911 p1 IWs 0:00.65 -bin/tcsh 921 p1 IW+ 0:00.31 vi filter.c 220 v0 IWs 0:00.84 -tcsh (tcsh) 627 v0 IW+ 0:02.82 rlogin freebsd 628 v0 IW+ 0:04.03 rlogin freebsd 824 v1 IWs 0:00.62 -tcsh (tcsh) 859 v1 IW+ 0:00.06 screen -R (screen-3.7.1) 222 v2 IWs 0:00.66 -tcsh (tcsh) 1786 v2 S 0:01.69 -su (tcsh) 1826 v2 R+ 0:00.07 ps -ax 223 v3 IWs+ 0:00.04 /usr/libexec/getty Pc ttyv3 224 d0 IWs+ 0:00.23 /bin/sh /usr/local/lib/ppp/13 1647 d0 S+ 0:03.58 /usr/sbin/ppp -direct adrenlin My two most recent panics had to do with vm_page_alloc(), which I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of which I've been told no one else is experiencing (and I've gone through the GNaTs database for anything similar to no avail), which I believe. And I have no problems believing that it *may* be a hardware problem, but what would be nice is some non-"trial and error" method of narrowing down the problem. Some way of having the panic that vm_page_alloc() produces send out an error message that states *where* the panic occurred... ie. in RAM or in swap space, or as a result of either. Its difficult to go to the accounting department and ask for more RAM because "that might fix the problem" :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 15:07:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA11057 for hackers-outgoing; Tue, 23 Apr 1996 15:07:10 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA11052 for ; Tue, 23 Apr 1996 15:06:57 -0700 (PDT) Received: from cimaxp1.UUCP (uucp@localhost) by melb.werple.net.au (8.7.5/8.7.3) with UUCP id HAA16561 for mira!freebsd.org!freebsd-hackers; Wed, 24 Apr 1996 07:21:54 +1000 (EST) Message-Id: <199604232121.HAA16561@melb.werple.net.au> Received: by cimaxp1.cimlogic.com.au; (5.65/1.1.8.2/10Sep95-0953AM) id AA15283; Wed, 24 Apr 1996 07:22:48 +1000 From: John Birrell Subject: Re: Help! I need info on pthreads. To: polstra.com!jdp@melb.werple.net.au (John Polstra) Date: Wed, 24 Apr 1996 07:22:48 +1000 (EST) Cc: freebsd.org!freebsd-hackers@melb.werple.net.au In-Reply-To: <4lj36e$hfb@austin.polstra.com> from "John Polstra" at Apr 23, 96 10:14:54 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > There's a really superb article on exactly that at: > > http://gatekeeper.dec.com/pub/DEC/SRC/research-reports/abstracts/src-rr-035.html > > It's by Andrew D. Birrell. (Who's he, John, your long lost brother? :-) Ummm. Dunno. If the article is *really* that good, he must be. 8-) > > John Polstra jdp@polstra.com -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Tue Apr 23 16:27:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA16289 for hackers-outgoing; Tue, 23 Apr 1996 16:27:03 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA16274 Tue, 23 Apr 1996 16:26:50 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id QAA00460; Tue, 23 Apr 1996 16:25:20 -0700 Message-Id: <199604232325.QAA00460@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Marc G. Fournier" cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 18:00:06 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 16:25:19 -0700 From: "Amancio Hasty Jr." Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wow, A bunch of stuff to try out: 1. swap out the memory 2. try a different scsi controller 3. check out the scsi cables 4. if the scsi bus does not have an active terminator try to get one 5. make sure that one of the drives is sending the termination power 6. check termination on all drives 7. make sure that scsi drives are good --- this is a tough my last scsi drive loved to crashed my system very similar to your symptoms - to say the least it was a mess. Cured the problem by junking the drive. Since you mentioned swap out problems I would concentrate the drives in which you have a swap partition. 8. Compile a kernel with kgdb so that when the system crashes you can hopefelly pop into the debugger and send us a stack trace. 9. See if you can get hold of another vga card something like an ISA et4000 based. Phew, good luck, Amancio >>> "Marc G. Fournier" said: > On Tue, 23 Apr 1996, Amancio Hasty Jr. wrote: > > > Hi, > > > > It will help if you post your hardware configuration. A few months > > ago there was a nasty PCI interaction in the kernel which caused > > my system to crash so glad that whatever it was is gone 8) > > > > dmesg: > FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 > scrappy@ki.net:/usr/src/sys/compile/kinet > CPU: i486 DX4 (486-class CPU) > Origin = "GenuineIntel" Id = 0x480 Stepping=0 > Features=0x3 > real memory = 16777216 (16384K bytes) > avail memory = 14835712 (14488K bytes) > Probing for devices on PCI bus 0: > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 12 on pci0:11 > (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 1222MB (2503872 512 byte sectors) > (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 > sd1(ncr0:1:0): Direct-Access > sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 327MB (670506 512 byte sectors) > (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 > sd2(ncr0:2:0): Direct-Access > sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 234MB (479350 512 byte sectors) > (ncr0:3:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 > sd3(ncr0:3:0): Direct-Access > sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 1013MB (2074880 512 byte sectors) > vga0 rev 0 on pci0:15 > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa > ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 not probed due to I/O address conflict with sio0 at 0x3f8 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 72065B > fd0: 1.44MB 3.5in > npx0 on motherboard > npx0: INT 16 interface > sctarg0(noadapter::): Processor Target > > > The NCR controller is one of the ASUS SC-200 controllers, > the vga0 device is an ATI Mach64 4MB PCI, and the sio1 conflict is > a misconfiguration on my part in this newest kernel that I have to > fix. > > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > CPU, and sio[01] are both onboard serial. > > The memory is one 16Meg SIMM, and pstat shows: > > Device 1K-blocks Used Avail Capacity Type > /dev/sd0b 51200 6880 44256 13% Interleaved > /dev/sd1b 32768 6936 25768 21% Interleaved > /dev/sd2b 32768 6960 25744 21% Interleaved > /dev/sd3b 102400 6904 95432 7% Interleaved > Total 218880 27680 191200 13% > > Any other information that may be pertinent? helpful? > > I'm running just about everything on this machine...named, > innd, YP, nfs-server and PPP: > > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.00 (swapper) > 1 ?? IWs 0:00.40 /sbin/init -- > 2 ?? DL 0:17.60 (pagedaemon) > 3 ?? DL 0:05.23 (vmdaemon) > 4 ?? DL 0:12.49 (update) > 78 ?? Ss 0:00.45 routed -q > 102 ?? Ss 0:03.46 syslogd > 105 ?? SWs 0:07.72 named > 110 ?? IWs 0:00.14 portmap > 113 ?? IWs 0:05.73 ypserv > 116 ?? IWs 0:00.02 yppasswdd -s -f > 120 ?? Ss 0:00.74 rwhod > 124 ?? IWs 0:00.09 mountd > 126 ?? IWs 0:00.02 nfsd: master (nfsd) > 128 ?? S 0:47.11 nfsd: server (nfsd) > 129 ?? IW 0:05.28 nfsd: server (nfsd) > 130 ?? IW 0:00.85 nfsd: server (nfsd) > 131 ?? IW 0:00.25 nfsd: server (nfsd) > 138 ?? Ss 0:00.90 inetd > 145 ?? Ss 0:00.62 cron > 149 ?? IWs 0:00.82 (sendmail) > 184 ?? Ss 0:06.29 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 187 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 188 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 208 ?? DNs 12:39.57 /news/admin/etc/innd -p4 -i0 > 218 ?? IWs 0:00.01 /usr/local/lib/pg95/bin/postmaster -S (postgres) > 583 ?? IWN 0:00.91 -204.17.53.78 LIST > 860 ?? IWs 0:01.28 SCREEN -R (screen-3.7.1) > 999 ?? IW 0:00.09 rshd > 1000 ?? IW 0:01.11 /etc/rimapd > 1293 ?? IW 0:00.27 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 1495 ?? DN 0:09.59 /news/bin/overchan > 1496 ?? SN 0:09.38 /usr/local/bin/perl /news/stats/bin/flowsum.channe l > 1551 ?? IW 0:00.18 (ftpd) > 1553 ?? IW 0:00.20 (ftpd) > 1686 ?? IWN 0:00.25 sh -c \n^IBATCHFILE=${HOST}.nntp\n^ILOCK=${LOCKS}/ LOC > 1719 ?? SN 0:06.78 innxmit -a -t300 -T1800 news.trends.ca /news/spool /ou > 1792 ?? IW 0:00.10 (sendmail) > 1808 ?? IW 0:00.06 (sendmail) > 1824 ?? IW 0:00.22 (ftpd) > 863 p0 IWs+ 0:00.58 -bin/tcsh > 911 p1 IWs 0:00.65 -bin/tcsh > 921 p1 IW+ 0:00.31 vi filter.c > 220 v0 IWs 0:00.84 -tcsh (tcsh) > 627 v0 IW+ 0:02.82 rlogin freebsd > 628 v0 IW+ 0:04.03 rlogin freebsd > 824 v1 IWs 0:00.62 -tcsh (tcsh) > 859 v1 IW+ 0:00.06 screen -R (screen-3.7.1) > 222 v2 IWs 0:00.66 -tcsh (tcsh) > 1786 v2 S 0:01.69 -su (tcsh) > 1826 v2 R+ 0:00.07 ps -ax > 223 v3 IWs+ 0:00.04 /usr/libexec/getty Pc ttyv3 > 224 d0 IWs+ 0:00.23 /bin/sh /usr/local/lib/ppp/13 > 1647 d0 S+ 0:03.58 /usr/sbin/ppp -direct adrenlin > > > My two most recent panics had to do with vm_page_alloc(), which > I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of > which I've been told no one else is experiencing (and I've gone through > the GNaTs database for anything similar to no avail), which I believe. > > And I have no problems believing that it *may* be a hardware > problem, but what would be nice is some non-"trial and error" method of > narrowing down the problem. Some way of having the panic that vm_page_alloc () > produces send out an error message that states *where* the panic occurred... > ie. in RAM or in swap space, or as a result of either. > > Its difficult to go to the accounting department and ask for more > RAM because "that might fix the problem" :( > > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org > > From owner-freebsd-hackers Tue Apr 23 16:49:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA19184 for hackers-outgoing; Tue, 23 Apr 1996 16:49:57 -0700 (PDT) Received: from vent.pipex.net (root@vent.pipex.net [158.43.128.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA19166 for ; Tue, 23 Apr 1996 16:49:52 -0700 (PDT) Received: from dial.pipex.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id AAA16690; Wed, 24 Apr 1996 00:49:33 +0100 Received: (from jraynard@localhost) by dial.pipex.com (8.6.12/8.6.12) id AAA02030; Wed, 24 Apr 1996 00:20:25 GMT Date: Wed, 24 Apr 1996 00:20:25 GMT From: James Raynard Message-Id: <199604240020.AAA02030@dial.pipex.com> To: bde@zeta.org.au CC: freebsd-hackers@freebsd.org In-reply-to: <199604231231.WAA20624@godzilla.zeta.org.au> (message from Bruce Evans on Tue, 23 Apr 1996 22:31:20 +1000) Subject: Re: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Bruce Evans writes: > > >2. Use of the soon-to-be-obsolescent vfork() instead of fork(). > > Reports of its death seem to be premature :-). I actually meant to type "soon-to-be-obsolete", but maybe what I put is more appropriate. 8-) > More points: > > 5. Use of the crufty signal() and deprecated sigblock() and sigsetmask() > instead of POSIX signal handling interfaces. It isn't clear whether the > sa_mask and sa_flags used by signal() give the correct behaviour. Yes, I thought about this but thought it best to try and avoid too many changes to the original code. Actually I was thinking about a "project" that I can do on 2.1.0-R code (I don't think I can afford the phone bills involved in running -current) and trying to make things like signal-handling in libc more Posix-compliant seems like a good one to start with. Any objections and/or pitfalls if I do this? > 6. Missing EINTR handling for waitpid(). This might be OK if SA_RESTART > was forced, but see point 5 - it is now clear that the sa_flags used by > signal() don't give the correct behaviour if the application has used > siginterrupt() to change the default of SA_RESTART. Hmm, didn't see that one, but now you mention it... > Some of these points also apply to popen/pclose, but the FreeBSD already > seems to be correct although unnecessarily unportable. E.g., it handles > EINTR. Out of interest, why does handling EINTR make it unportable? Cheers James From owner-freebsd-hackers Tue Apr 23 16:50:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA19310 for hackers-outgoing; Tue, 23 Apr 1996 16:50:31 -0700 (PDT) Received: from vent.pipex.net (root@vent.pipex.net [158.43.128.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA19277 for ; Tue, 23 Apr 1996 16:50:20 -0700 (PDT) Received: from dial.pipex.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id AAA16731; Wed, 24 Apr 1996 00:49:38 +0100 Received: (from jraynard@localhost) by dial.pipex.com (8.6.12/8.6.12) id XAA01870; Tue, 23 Apr 1996 23:47:57 GMT Date: Tue, 23 Apr 1996 23:47:57 GMT From: James Raynard Message-Id: <199604232347.XAA01870@dial.pipex.com> To: julian@ref.tfs.com CC: hackers@freebsd.org In-reply-to: <199604222244.PAA20222@ref.tfs.com> (julian@ref.tfs.com) Subject: Re: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "JULIAN Elischer" writes: > > > Inspired by Rich Stevens' implementation of system() in his book > > "Advanced Programming in the Unix Environment", I've been looking at > > the FreeBSD implementation and was struck by the following points:- > > > > 1. Use of a wait union when an int would do. > This is the correct POSIX thing to do.. > check the man page for wait. According to the 2.1.0-RELEASE man page, wait and friends use an int* for the status variable. > > 3. Returns 0 if fork() fails, when -1 seems more appropriate. > POSIX says: Thanks for posting this, I don't have access to any POSIX specs (except the odd snippet in books). What's the best way of getting hold of them? > If "command" is a null pointer, the system() function returns non-zero > only if a command processor is available. OK (Out of interest, what kind of circumstances would result in a command processor not being available?) > If "command" is a nin null pointer the system() function returnsa > the termination status of the command language interpretter in the > format specified by the waitpid() function. OK > [...] > If a child process cannot be created, > or if the termination status of hte command interpretter cannot be obtained > system() returns -1 > and sets errno to indicate the error. Doesn't that imply that system() should return -1 if fork() fails? (Forgive me if I'm being obtuse, I'm not very experienced at reading standardese). > > 4. The SIGINT and SIGQUIT are not ignored until after the fork(). > > If the child runs first, one of these signals could in theory be > the child MUST run first in vfork() I know, but I'm trying not to use vfork(), in view of the recent discussion (in -current, I think) about replacing it with a call to fork(). Cheers James From owner-freebsd-hackers Tue Apr 23 17:03:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA20940 for hackers-outgoing; Tue, 23 Apr 1996 17:03:22 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA20924 Tue, 23 Apr 1996 17:03:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id RAA06541; Tue, 23 Apr 1996 17:02:34 -0700 (PDT) To: "Marc G. Fournier" cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 16:02:04 EDT." Date: Tue, 23 Apr 1996 17:02:34 -0700 Message-ID: <6539.830304154@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What would it take to either create software for debugging > hardware, and/or add appropriate debugging to the kernel that would > improve debugging of hardware problems? A lot. The best you can hope for right now is "CheckIt" from TouchStone software, it runs under DOS and no I haven't even the faintest idea whether or not it will detect your particular problem. Probably not, but it's the best attempt at a software hardware checker that I know of. > As far as the kernel is concerned, I'm getting panics in VM > and keep getting told its hardware problems...fine, but there *has* > to be a better way of isolating the problem then replacing bits and > pieces until the problem seems to go away. For instance, when I get Not really. This is, in fact, how the "big boys" do it. If you're in doubt, swap it out. One component at a time, if necessary, until you find the bad one. I would first target my cache, memory and motherboard, in that order, for replacement if I were in your shoes (and I have been - this is how I fixed it :-). Jordan From owner-freebsd-hackers Tue Apr 23 17:35:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23694 for hackers-outgoing; Tue, 23 Apr 1996 17:35:58 -0700 (PDT) Received: from distortion.eng.umd.edu (distortion.eng.umd.edu [129.2.98.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA23689 for ; Tue, 23 Apr 1996 17:35:56 -0700 (PDT) Received: from thurston.eng.umd.edu (thurston.eng.umd.edu [129.2.98.206]) by distortion.eng.umd.edu (8.7.5/8.7.3) with ESMTP id UAA19071; Tue, 23 Apr 1996 20:35:54 -0400 (EDT) Received: (from chuckr@localhost) by thurston.eng.umd.edu (8.7.5/8.7.3) id UAA00484; Tue, 23 Apr 1996 20:35:53 -0400 (EDT) Date: Tue, 23 Apr 1996 20:35:52 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@thurston.eng.umd.edu To: Julian Elischer cc: hackers@FreeBSD.org Subject: Re: ps dies with FP exception. In-Reply-To: <199604231852.LAA21817@ref.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Julian Elischer wrote: > anyone else getting this? > under -current.. > I will shortly recompile the kernel as well, but > ps alx works > ps aux dies > > julian > (ps sources as of this morning)(but it did this last week already) I rebuilt my kernel last Saturday (the 20th) and both ps -alx and ps -aux both work for me. Also rebuilt world at the same time, tho. > ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-hackers Tue Apr 23 18:26:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA27663 for hackers-outgoing; Tue, 23 Apr 1996 18:26:06 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA27593 Tue, 23 Apr 1996 18:25:31 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA13482; Wed, 24 Apr 1996 10:51:15 +0930 From: Michael Smith Message-Id: <199604240121.KAA13482@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 10:51:15 +0930 (CST) Cc: current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 04:02:04 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > What would it take to either create software for debugging > hardware, and/or add appropriate debugging to the kernel that would > improve debugging of hardware problems? Ah. As someone with a foot in both the hardware and software camps, all I can say is "forget it". Any software has to make a few assumptions about the hardware it runs on. If the hardware fails to meet those assumptions, (eg. random parts of memory change) there's no hope for the software. To answer your question absolutely, this sort of software does exist. You find it in board-level test equipment with price tags starting in the mid six figures. Configuring such software usually requires access to the manufacturer's specification for the DUT. (If such information actually exists in the first place - often it's easier for a board vendor to just throw a prototype together, and if it runs Windows, commit to manufacturing it.) > Erk...as far as software is concerned, maybe something that > you could run in single user mode that would completely thrash the > RAM, doing read/writes to *all* the memory looking for any corruption? "make world". The issue here is that it's not _just_ memory, but the interaction between processor memory accesses, busmastering activity, refresh, chipset timing and random system noise. Simulating such an environment is _impossible_. If the memory was legitimately altered in an incorrect fasion (eg. a bus latch was late and caught data from the master as it transited out of a valid state, and subsequently wrote it into memory), even ECC memory won't help you. > As far as the kernel is concerned, I'm getting panics in VM > and keep getting told its hardware problems...fine, but there *has* > to be a better way of isolating the problem then replacing bits and > pieces until the problem seems to go away. For instance, when I get > a VM fault...what exactly *is* the problem? Is it a problem with > the swap space (ie. hard drives) or RAM? Find a spare $10K or so and buy a _good_ DRAM tester. Discover, much to your surprise, that most of the DRAMs on the market fail to operate to spec. Become Enlightened. Purchase a pile of Triton-II motherboards, fork out _lots_ of money for fast ECC memory, and _maybe_ your problems will go away. What is worth bearing in mind is that other people are doing essentially the same things that you are doing, but aren't having the problems you are. They don't have access to any magical software fixes, it's just that their (our) hardware appears to work OK. > Does this make any sense? Yes. The problem is that PCs are built like toasters, and making a souffle' in a toaster is very difficult. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Apr 23 18:34:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA28508 for hackers-outgoing; Tue, 23 Apr 1996 18:34:58 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA28501 Tue, 23 Apr 1996 18:34:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id SAA02806; Tue, 23 Apr 1996 18:34:47 -0700 (PDT) Message-Id: <199604240134.SAA02806@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Amancio Hasty Jr." cc: "Marc G. Fournier" , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 16:25:19 PDT." <199604232325.QAA00460@rah.star-gate.com> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 23 Apr 1996 18:34:47 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >5. make sure that one of the drives is sending the termination power For external termination, this is normally done by the controller, not any of the drives. Most people terminate the last drive with the drive's termination and configure that drive to supply it's on termination power (which is usually the factory default). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Apr 23 18:48:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29909 for hackers-outgoing; Tue, 23 Apr 1996 18:48:54 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA29880 Tue, 23 Apr 1996 18:48:47 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id VAA00596; Tue, 23 Apr 1996 21:48:39 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id VAA03837; Tue, 23 Apr 1996 21:48:44 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 21:48:43 -0400 (EDT) From: "Marc G. Fournier" To: "Amancio Hasty Jr." cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604232325.QAA00460@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Amancio Hasty Jr. wrote: <1 thru 7 removed as I'm working on those ones> > > 8. Compile a kernel with kgdb so that when the system crashes you > can hopefelly pop into the debugger and send us a stack trace. > I have the kernel compiled with DDB & DODUMP enabled, so that I get dropped to ddb and can do a trace...I send them out and get told its a hardware problem and then they seem to drop off the face of the earth :( Is it also a hardware problem that prevents me from getting a coredump after issuing 2xpanic at the ddb> prompt to cause it to reboot? My -current machine reboots and drops core so that I can run kgdb against it, but my -stable machine won't :( > 9. See if you can get hold of another vga card something like an ISA > et4000 based. > Will add that to my "hardware wish list" for a new machine...if I can get *one* machine stable, then this won't be soooo frustrating. Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 18:56:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA00768 for hackers-outgoing; Tue, 23 Apr 1996 18:56:02 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA00715 Tue, 23 Apr 1996 18:55:55 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA13635; Wed, 24 Apr 1996 11:21:38 +0930 From: Michael Smith Message-Id: <199604240151.LAA13635@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 11:21:37 +0930 (CST) Cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 06:00:06 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 > scrappy@ki.net:/usr/src/sys/compile/kinet > CPU: i486 DX4 (486-class CPU) > Origin = "GenuineIntel" Id = 0x480 Stepping=0 > Features=0x3 > real memory = 16777216 (16384K bytes) > avail memory = 14835712 (14488K bytes) > Probing for devices on PCI bus 0: > chip0 rev 49 on pci0:5 Ok. This guy is known to work pretty well, as long as you avoid ISA busmasters. > sctarg0(noadapter::): Processor Target Wozzis? You have a scanner or something? > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > CPU, and sio[01] are both onboard serial. Jumpered for write-back or write-through? Which cache Tagram are you using? Is the board jumpered correctly for it? > The memory is one 16Meg SIMM, and pstat shows: Speed? Manufacturer? > My two most recent panics had to do with vm_page_alloc(), which > I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of > which I've been told no one else is experiencing (and I've gone through > the GNaTs database for anything similar to no avail), which I believe. The problem, such as it is, is that these pieces of code depend intimately on some _very_ heavily accessed parts of memory, and if there's anything wrong with these parts of memory, they cause a panic. > And I have no problems believing that it *may* be a hardware > problem, but what would be nice is some non-"trial and error" method of > narrowing down the problem. Some way of having the panic that vm_page_alloc() > produces send out an error message that states *where* the panic occurred... > ie. in RAM or in swap space, or as a result of either. Check the source of the panic in the code, and there you have it. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Apr 23 19:28:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA04304 for hackers-outgoing; Tue, 23 Apr 1996 19:28:44 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA04279 Tue, 23 Apr 1996 19:28:33 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id WAA01007; Tue, 23 Apr 1996 22:28:31 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id WAA04472; Tue, 23 Apr 1996 22:28:38 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 22:28:37 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240151.LAA13635@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Michael Smith wrote: > Ok. This guy is known to work pretty well, as long as you avoid ISA > busmasters. > Nope, only cards are the NCR SCSI, ATI video and SMC8013 Ethernet > > sctarg0(noadapter::): Processor Target > > Wozzis? You have a scanner or something? > *shrug* nothing else other then those three cards in the machine... > > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > > CPU, and sio[01] are both onboard serial. > > Jumpered for write-back or write-through? Which cache Tagram are you > using? Is the board jumpered correctly for it? > will check the wb/wt...what do you mean by cache Tagram? > > The memory is one 16Meg SIMM, and pstat shows: > > Speed? Manufacturer? > Unknown...will have to shut down to check, but will do so after I send this out... > > My two most recent panics had to do with vm_page_alloc(), which > > I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of > > which I've been told no one else is experiencing (and I've gone through > > the GNaTs database for anything similar to no avail), which I believe. > > The problem, such as it is, is that these pieces of code depend intimately > on some _very_ heavily accessed parts of memory, and if there's anything > wrong with these parts of memory, they cause a panic. > Okay, that part I don't have a problem with, but, if it detects that something is wrong, why doesn't it try (or does it?) to work around the problem? Map out the offending area of memory? As well, does this restrict the problem to cache/RAM vs swap space? I'm don't yet understand how swap space works (I know what it does, just not how), but I presume that the swap space is a psuedo-file system? Since I'm on SCSI, I would assume that it would auto-remap defective areas in the swap space, if my first assumption is correct? I can understand having bad luck with one machine, but I have three machines here, all with different hardware and they all have "hardware related" panics, two are -stable, one is -current (so I kind of expect problems with the third) After getting rid of that bad drive that cause the SCSI locks (which, mind you, is running great in another machine, solo on the SCSI bus...go figure), I've been able to get 7+days uptime on my machines. -current machine == 8+ days (rebooted to install new kernel) -stable machine 1 == 9+ days (panic'd...vm related) -stable machine 2 == 5+ days and still running) So I'm getting *somewhere*...just very slowly :( Will check the RAM/cache and get back to you... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 20:20:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08892 for hackers-outgoing; Tue, 23 Apr 1996 20:20:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA08876 Tue, 23 Apr 1996 20:20:34 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA14238; Wed, 24 Apr 1996 12:29:49 +0930 From: Michael Smith Message-Id: <199604240259.MAA14238@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 12:29:49 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 10:28:37 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > sctarg0(noadapter::): Processor Target > > > > Wozzis? You have a scanner or something? > > > *shrug* nothing else other then those three cards in the > machine... Hmm. Have you got a 'pt0' in your kernel config? > > Jumpered for write-back or write-through? Which cache Tagram are you > > using? Is the board jumpered correctly for it? > > > will check the wb/wt...what do you mean by cache Tagram? Cache SRAM comes in two parts, the cache itself and the tag ram that keeps track of what's in the cache. The SiS boards we use (Soyo) have jumpers for dealing with two different tag parts. I don't have, and have never used any Acer boards, so I don't know about them. > > The problem, such as it is, is that these pieces of code depend intimately > > on some _very_ heavily accessed parts of memory, and if there's anything > > wrong with these parts of memory, they cause a panic. > > Okay, that part I don't have a problem with, but, if it > detects that something is wrong, why doesn't it try (or does it?) to > work around the problem? Map out the offending area of memory? As How? Has the code followed a bad pointer to the area it's working on? Is the location it just read from bad, or is it comparing it with a bad value it picked up a while ago? Is it the RAM that's bad, or the cache? You can't just "map out" the bits of memory that the code is working with - all the critical data structures that the system depends on are in there - to "map them out" would mean total chaos. Simple by far is to say "this value is impossible" and tell the owner of the losing hardware that it lost. > well, does this restrict the problem to cache/RAM vs swap space? > I'm don't yet understand how swap space works (I know what it does, > just not how), but I presume that the swap space is a psuedo-file > system? Since I'm on SCSI, I would assume that it would auto-remap > defective areas in the swap space, if my first assumption is > correct? You should spend some time at night with the new daemon book, which should be out shortly - "The design and implementation of the 4.4 BSD Unix operating system" and perhaps also "The Magic Garden explained". Once you've digested those two, you'll have an appreciation (if not an understanding) of the issues involved. If they give you a headache, try "Operating systems, design and implementation" by Tanenbaum (the Minix book) first, and then come back. > I can understand having bad luck with one machine, but I have > three machines here, all with different hardware and they all have > "hardware related" panics, two are -stable, one is -current (so I kind > of expect problems with the third) We have anything from a few to about a dozen machines around here at any one time, a mix of 2.1R, -stable and -current. A few have known hardware bogons (old systems), but aside from that (and the machines running some of my less-than-wonderful device drivers), we don't see many problems. (Usually someone else runs across the really nasty ones and I hold off updating the kernel until its fixed.) Having said that, there _was_ a recent commit to the pmap code that could well have some bearing on your problem. Check it out 8) > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Apr 23 20:38:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA10443 for hackers-outgoing; Tue, 23 Apr 1996 20:38:48 -0700 (PDT) Received: from ki.net (ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA10408 Tue, 23 Apr 1996 20:38:30 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id XAA00682; Tue, 23 Apr 1996 23:37:55 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id XAA05458; Tue, 23 Apr 1996 23:38:05 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 23:38:05 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240259.MAA14238@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > sctarg0(noadapter::): Processor Target > > > > > > Wozzis? You have a scanner or something? > > > > > *shrug* nothing else other then those three cards in the > > machine... > > Hmm. Have you got a 'pt0' in your kernel config? > Yes > Simple by far is to say "this value is impossible" and tell the owner > of the losing hardware that it lost. > Okay, Understood... > You should spend some time at night with the new daemon book, which > should be out shortly - "The design and implementation of the 4.4 BSD > Unix operating system" and perhaps also "The Magic Garden explained". > I will *definitely* look for these books... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 20:43:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA10960 for hackers-outgoing; Tue, 23 Apr 1996 20:43:45 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA10943 Tue, 23 Apr 1996 20:43:33 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA14757; Wed, 24 Apr 1996 13:09:40 +0930 From: Michael Smith Message-Id: <199604240339.NAA14757@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 24 Apr 1996 13:09:39 +0930 (CST) Cc: scrappy@ki.net, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <6539.830304154@time.cdrom.com> from "Jordan K. Hubbard" at Apr 23, 96 05:02:34 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > The best you can hope for right now is "CheckIt" from TouchStone > software, it runs under DOS and no I haven't even the faintest idea > whether or not it will detect your particular problem. Probably not, > but it's the best attempt at a software hardware checker that I know > of. Don't waste any money on it. If you get it as a freebie, that's fine, but they're honest enough in the manual to point out that their tests aren't anything compared to the load a mutltitasking VM OS imposes. (We got it Real Cheap when we were having RAM trouble; it didn't find the problem, and this was a RAM error so bad that _Windows_ would barf.) > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Apr 23 20:47:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA11396 for hackers-outgoing; Tue, 23 Apr 1996 20:47:16 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA11383 Tue, 23 Apr 1996 20:47:12 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA14787; Wed, 24 Apr 1996 13:11:41 +0930 From: Michael Smith Message-Id: <199604240341.NAA14787@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 13:11:40 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 11:38:05 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > You should spend some time at night with the new daemon book, which > > should be out shortly - "The design and implementation of the 4.4 BSD > > Unix operating system" and perhaps also "The Magic Garden explained". > > > I will *definitely* look for these books... Check the handbook, as I think they're on the reading list. If not, check the -hackers archive for Terry Lambert talking about the 'magic garden' book - his reading list was pretty comprehensive. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Apr 23 20:47:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA11417 for hackers-outgoing; Tue, 23 Apr 1996 20:47:20 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA11379 Tue, 23 Apr 1996 20:47:07 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id XAA01669; Tue, 23 Apr 1996 23:46:57 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id XAA05619; Tue, 23 Apr 1996 23:47:01 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 23:46:57 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: "Jordan K. Hubbard" , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240339.NAA14757@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Michael Smith wrote: > Don't waste any money on it. If you get it as a freebie, that's fine, > but they're honest enough in the manual to point out that their tests > aren't anything compared to the load a mutltitasking VM OS imposes. > > (We got it Real Cheap when we were having RAM trouble; it didn't find the > problem, and this was a RAM error so bad that _Windows_ would barf.) > I've got 9 make processes running in /usr/src/lib right now, and will cycle those through for the next little while...that should give it a good test, shouldn't it? That with the rest of its normal load? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Tue Apr 23 21:05:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA13042 for hackers-outgoing; Tue, 23 Apr 1996 21:05:56 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA13010 Tue, 23 Apr 1996 21:05:50 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA15067; Wed, 24 Apr 1996 13:28:13 +0930 From: Michael Smith Message-Id: <199604240358.NAA15067@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 13:28:12 +0930 (CST) Cc: hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 09:48:43 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > Is it also a hardware problem that prevents me from getting > a coredump after issuing 2xpanic at the ddb> prompt to cause it to > reboot? My -current machine reboots and drops core so that I can > run kgdb against it, but my -stable machine won't :( This machines has an NCR controller in it IIRC. You should talk to Stefan about this - dumping requires the controller to run in polled mode, and it's possible that's not happening. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Apr 23 23:24:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA21982 for hackers-outgoing; Tue, 23 Apr 1996 23:24:15 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA21975 Tue, 23 Apr 1996 23:24:12 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA16847; Wed, 24 Apr 1996 15:49:04 +0930 From: Michael Smith Message-Id: <199604240619.PAA16847@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 15:49:03 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 11:38:05 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > > Hmm. Have you got a 'pt0' in your kernel config? > > > Yes Get rid of it, unless you have a 'processor'-type SCSI device. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Apr 24 00:15:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA23883 for hackers-outgoing; Wed, 24 Apr 1996 00:15:17 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA23843 for ; Wed, 24 Apr 1996 00:14:47 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA10221; Wed, 24 Apr 1996 09:13:48 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA20967; Wed, 24 Apr 1996 09:13:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA26285; Wed, 24 Apr 1996 08:55:47 +0200 (MET DST) From: J Wunsch Message-Id: <199604240655.IAA26285@uriah.heep.sax.de> Subject: Re: Intelligent Debugging Tools... To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 24 Apr 1996 08:55:46 +0200 (MET DST) Cc: scrappy@ki.net (Marc G. Fournier) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 09:48:43 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Marc G. Fournier wrote: (Please, restrict this to one list.) > > 8. Compile a kernel with kgdb so that when the system crashes you > > can hopefelly pop into the debugger and send us a stack trace. > > > I have the kernel compiled with DDB & DODUMP enabled, so that DODUMP is gone. Use dumpon(8) instead, or kernel root on ... swap on ... dumps on ... if you wanna get dumps before /etc/rc has been running. -- 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 Apr 24 01:34:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA28722 for hackers-outgoing; Wed, 24 Apr 1996 01:34:19 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA28713 Wed, 24 Apr 1996 01:34:15 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04088; Wed, 24 Apr 1996 01:32:35 -0700 From: "Rodney W. Grimes" Message-Id: <199604240832.BAA04088@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: davidg@Root.COM Date: Wed, 24 Apr 1996 01:32:35 -0700 (PDT) Cc: hasty@rah.star-gate.com, scrappy@ki.net, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199604240134.SAA02806@Root.COM> from David Greenman at "Apr 23, 96 06:34:47 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >5. make sure that one of the drives is sending the termination power > > For external termination, this is normally done by the controller, not any > of the drives. True. > Most people terminate the last drive with the drive's termination I would disagree with that, most people use an external terminator on an external chain. Turning terminators on inside of external scsi enclosures is a no no in my book, it often leads to multiple termination when someone not so informed adds something to a chain. Or middle termination with a floating end when a chain gets swapped around. > and configure that drive to supply it's on termination power ^^ own For external scsi chains of any length > 3 feet I would _strongly_ encourage the use of drive supplied termination power (preferably from the last drive on the chain) to the scsi bus. > (which is usually the factory default). With the advent of the SCSI PnP spec this and other defaults are rapidly changing, the SCSI PnP spec requires that drives ship with no termination enabled, the use of on drive termination is verboten, you are suppose to use cable end terminators both internally and externally. I don't seem to recally anything about term power though :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hackers Wed Apr 24 01:38:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA29096 for hackers-outgoing; Wed, 24 Apr 1996 01:38:21 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA29085 for ; Wed, 24 Apr 1996 01:38:16 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.6.11/8.6.9) with ESMTP id BAA19783; Wed, 24 Apr 1996 01:37:59 -0700 From: Josh MacDonald Message-Id: <199604240837.BAA19783@paris.CS.Berkeley.EDU> To: Bruce Evans Cc: freebsd-hackers@freebsd.org Subject: Re: GNU binutils port In-reply-to: Your message of "Fri, 12 Apr 1996 16:52:14 +1000." <199604120652.QAA00548@godzilla.zeta.org.au> Date: Wed, 24 Apr 1996 01:37:57 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > They are only warnings and many would go away if less warnings were enabled. > There would be many more if more were enabled. For the LINT kernel built on > Apr 6, the warning counts were: > > compiler warnings (lines) > -------- -------- > cc 74 > cc -Wall 2394 > gcc-2.7.2 4694 > Oh dear.... I can't beleive you're saying this, "They are only warnings". To me, it has, "My code sucks and I don't care." written all over it if you don't fix things so that they compile with no warnings and -Wall. Perhaps kernel code is a bit different, but with 4700 warnings, I'd be little scared. > Bruce From owner-freebsd-hackers Wed Apr 24 01:46:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA29673 for hackers-outgoing; Wed, 24 Apr 1996 01:46:42 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA29662 Wed, 24 Apr 1996 01:46:38 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id BAA00464; Wed, 24 Apr 1996 01:45:47 -0700 Message-Id: <199604240845.BAA00464@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: current@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Wed, 24 Apr 1996 01:32:35 PDT." <199604240832.BAA04088@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Apr 1996 01:45:47 -0700 From: "Amancio Hasty Jr." Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I hope that all this useful information about scsi goes into the FreeBSD Handbook 8) Cheers, Amancio >>> "Rodney W. Grimes" said: > > >5. make sure that one of the drives is sending the termination power > > > > For external termination, this is normally done by the controller, not any > > of the drives. > > True. > > > Most people terminate the last drive with the drive's termination > > I would disagree with that, most people use an external terminator on > an external chain. Turning terminators on inside of external scsi > enclosures is a no no in my book, it often leads to multiple termination > when someone not so informed adds something to a chain. Or middle > termination with a floating end when a chain gets swapped around. > > > and configure that drive to supply it's on termination power > ^^ own > For external scsi chains of any length > 3 feet I would _strongly_ encourage > the use of drive supplied termination power (preferably from the last > drive on the chain) to the scsi bus. > > > (which is usually the factory default). > > With the advent of the SCSI PnP spec this and other defaults are rapidly > changing, the SCSI PnP spec requires that drives ship with no termination > enabled, the use of on drive termination is verboten, you are suppose to > use cable end terminators both internally and externally. I don't seem > to recally anything about term power though :-(. > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hackers Wed Apr 24 01:53:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA00373 for hackers-outgoing; Wed, 24 Apr 1996 01:53:27 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA00361 Wed, 24 Apr 1996 01:53:23 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04106; Wed, 24 Apr 1996 01:51:11 -0700 From: "Rodney W. Grimes" Message-Id: <199604240851.BAA04106@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 01:51:11 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at "Apr 23, 96 11:38:05 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, 23 Apr 1996, Michael Smith wrote: > > > Marc G. Fournier stands accused of saying: > > > > > sctarg0(noadapter::): Processor Target > > > > > > > > Wozzis? You have a scanner or something? > > > > > > > *shrug* nothing else other then those three cards in the > > > machine... > > > > Hmm. Have you got a 'pt0' in your kernel config? > > > Yes Why? And how many changes are there in your kernel config file with respect to the GENERIC kernel? Did you make the fatal mistakes that others have made and started from the LINT config file instead of the GENERIC config? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hackers Wed Apr 24 01:53:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA00444 for hackers-outgoing; Wed, 24 Apr 1996 01:53:59 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA00430 Wed, 24 Apr 1996 01:53:54 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04097; Wed, 24 Apr 1996 01:49:05 -0700 From: "Rodney W. Grimes" Message-Id: <199604240849.BAA04097@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 01:49:05 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, jkh@time.cdrom.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at "Apr 23, 96 11:46:57 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 24 Apr 1996, Michael Smith wrote: > > > Don't waste any money on it. If you get it as a freebie, that's fine, > > but they're honest enough in the manual to point out that their tests > > aren't anything compared to the load a mutltitasking VM OS imposes. > > > > (We got it Real Cheap when we were having RAM trouble; it didn't find the > > problem, and this was a RAM error so bad that _Windows_ would barf.) > > > > I've got 9 make processes running in /usr/src/lib right now, > and will cycle those through for the next little while...that should give > it a good test, shouldn't it? That with the rest of its normal load? One of the bests tests I use for doing the divide and conquere (swap parts) in locating hardware related system failures (something I do as a weekly event) is simply repeated ``make worlds''. Unless you have _lots_ of memory (>32MB) multiple builds of /usr/src/lib are just going to thrash the paging/swap area to death. Besides library code compiles easily do to the small sizes of the source and produced object files, use a monster compile like gcc/g++. What you are looking for is signal 6's, 10's and 11's, which generally point to memory (cache or main) related system failures. Panics can be just about anything from the CPU chip to the I/O cards. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hackers Wed Apr 24 02:46:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA03912 for hackers-outgoing; Wed, 24 Apr 1996 02:46:59 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA03907 Wed, 24 Apr 1996 02:46:57 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.4/8.7.3) with SMTP id EAA21733; Wed, 24 Apr 1996 04:39:44 -0500 (CDT) Date: Wed, 24 Apr 1996 04:39:44 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: "Marc G. Fournier" cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Marc G. Fournier wrote: > FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 > scrappy@ki.net:/usr/src/sys/compile/kinet > CPU: i486 DX4 (486-class CPU) > Origin = "GenuineIntel" Id = 0x480 Stepping=0 > Features=0x3 This isn't an Asus SP3 or SP3G is it? > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 12 on pci0:11 Same contoller here... > ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa > ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) Heh, I've got an NE2000, but it uses the ed driver as well. > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > CPU, and sio[01] are both onboard serial. Ah, ok... But they both use the same SiS chipset. I'm seeing something I've classified as 'slightly weird' but due to the machine and the nature of problem, its a bit difficult to check the console for a panic. In any event, the machine can't stay up for more than 5 or 6 days. I'm going to re-enable crash dumps and make an up to date -stable kernel and see whats up. Due to the similarities between your hardware and mine, this problem MIGHT be hardware related. I've considered replacing the SC-200 with an ah2940 to see if that makes a difference. Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-hackers Wed Apr 24 04:55:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA11643 for hackers-outgoing; Wed, 24 Apr 1996 04:55:47 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA11638 for ; Wed, 24 Apr 1996 04:55:44 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uC3Ad-0003wXC; Wed, 24 Apr 96 04:55 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id LAA10994 for ; Wed, 24 Apr 1996 11:55:41 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: hackers@FreeBSD.org Subject: Good ISDN developer URL Date: Wed, 24 Apr 1996 11:55:40 +0000 Message-ID: <10992.830346940@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk http://www.cicat.com/isdndevl.htm Poul-Henning From owner-freebsd-hackers Wed Apr 24 05:00:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA11886 for hackers-outgoing; Wed, 24 Apr 1996 05:00:47 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA11881 for ; Wed, 24 Apr 1996 05:00:44 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id VAA19097; Wed, 24 Apr 1996 21:27:22 +0930 From: Michael Smith Message-Id: <199604241157.VAA19097@genesis.atrad.adelaide.edu.au> Subject: Re: GNU binutils port To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Date: Wed, 24 Apr 1996 21:27:21 +0930 (CST) Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <199604240837.BAA19783@paris.CS.Berkeley.EDU> from "Josh MacDonald" at Apr 24, 96 01:37:57 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Josh MacDonald stands accused of saying: > Oh dear.... I can't beleive you're saying this, "They are only warnings". > > To me, it has, "My code sucks and I don't care." written all over > it if you don't fix things so that they compile with no warnings > and -Wall. Perhaps kernel code is a bit different, but with 4700 > warnings, I'd be little scared. gcc -Wall is _pedantic_. Consider how many of the above are "Consider parentheses around assignment used as truth value", or "Integer used as pointer without a cast" (for use of '0' as a [legitimate] substitute for NULL. A pile more would be historic warts where unions were avoided and pointers to structures were passed around in a known context. > > Bruce -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Apr 24 07:21:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17441 for hackers-outgoing; Wed, 24 Apr 1996 07:21:00 -0700 (PDT) Received: from ghost.uunet.ca (ghost.uunet.ca [142.77.1.100]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA17434 Wed, 24 Apr 1996 07:20:52 -0700 (PDT) Received: by ghost.uunet.ca id <52814-3053>; Wed, 24 Apr 1996 10:20:30 -0400 Date: Wed, 24 Apr 1996 10:20:24 -0400 From: Cat Okita To: "Rodney W. Grimes" cc: davidg@Root.COM, hasty@rah.star-gate.com, scrappy@ki.net, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240832.BAA04088@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > I would disagree with that, most people use an external terminator on > an external chain. Turning terminators on inside of external scsi > enclosures is a no no in my book, it often leads to multiple termination > when someone not so informed adds something to a chain. Or middle > termination with a floating end when a chain gets swapped around. I'll second that one - I've had some really unpleasant times trying to find out which device *thinks* that it's terminated, if it's in the case, or on the drive. External termination is right out in front of your eyes. > With the advent of the SCSI PnP spec this and other defaults are rapidly > changing, the SCSI PnP spec requires that drives ship with no termination > enabled, the use of on drive termination is verboten, you are suppose to > use cable end terminators both internally and externally. I don't seem > to recally anything about term power though :-(. Being overly used to the world of unix-designed machines (ie: sun, dec...), it was a really nasty shock to discover that PC's *normally* terminate on the drives... cheers! cat From owner-freebsd-hackers Wed Apr 24 07:27:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17969 for hackers-outgoing; Wed, 24 Apr 1996 07:27:42 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA17962 Wed, 24 Apr 1996 07:27:38 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id HAA25084 ; Wed, 24 Apr 1996 07:27:20 -0700 Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id RAA19922; Wed, 24 Apr 1996 17:21:22 +0300 Date: Wed, 24 Apr 1996 17:21:22 +0300 (EET DST) From: Narvi To: "Rodney W. Grimes" cc: davidg@Root.COM, hasty@rah.star-gate.com, scrappy@ki.net, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240832.BAA04088@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > >5. make sure that one of the drives is sending the termination power > > > > For external termination, this is normally done by the controller, not any > > of the drives. > > True. > > > Most people terminate the last drive with the drive's termination > > I would disagree with that, most people use an external terminator on > an external chain. Turning terminators on inside of external scsi > enclosures is a no no in my book, it often leads to multiple termination > when someone not so informed adds something to a chain. Or middle > termination with a floating end when a chain gets swapped around. > > > and configure that drive to supply it's on termination power > ^^ own > For external scsi chains of any length > 3 feet I would _strongly_ encourage > the use of drive supplied termination power (preferably from the last > drive on the chain) to the scsi bus. > > > (which is usually the factory default). > > With the advent of the SCSI PnP spec this and other defaults are rapidly > changing, the SCSI PnP spec requires that drives ship with no termination > enabled, the use of on drive termination is verboten, you are suppose to > use cable end terminators both internally and externally. I don't seem > to recally anything about term power though :-(. There happen to be devices (at least my HP DAT is of that kind) which always supply termination power - you even can'tr turn it off. > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD > Sander Eat good food, preserve nature, be nice to all nice people :) From owner-freebsd-hackers Wed Apr 24 08:21:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA24349 for hackers-outgoing; Wed, 24 Apr 1996 08:21:08 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA24344 for ; Wed, 24 Apr 1996 08:21:00 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA23904; Wed, 24 Apr 1996 11:20:21 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 24 Apr 1996 11:20 EDT Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.12/8.6.5) with ESMTP id HAA27363; Wed, 24 Apr 1996 07:35:21 -0400 Received: (from rivers@localhost) by lakes (8.6.12/8.6.9) id HAA01815; Wed, 24 Apr 1996 07:34:06 -0400 Date: Wed, 24 Apr 1996 07:34:06 -0400 From: Thomas David Rivers Message-Id: <199604241134.HAA01815@lakes> To: lambert.org!terry@dg-rtp.dg.com, torvalds@cs.Helsinki.FI Subject: Re: Unices are created equal, but ... Cc: hackers@FreeBSD.ORG, julian@ref.tfs.com, linux-kernel@vger.rutgers.edu Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > If somebody wants to do benchmarking,I'd suggest using at least > > - lmbench (nice microbenchmark) > > - bonnie (reasonable disk performance benchmark) > > - webstone (or something similar. But use "apache" as the server, not > > some braindead horror like NCSA). > > - ??? > > > > (the three mentioned should cover different areas, all very reasonable, > > but have I missed some important area?) > > Ziff-Davis "netbench" for DOS, Windows, Windows95, and Macintosh > clients against SAMBA and/or NFS and/or Appletalk servers. > > Ziff-Davis "Winbench" in an emulation environment. Note that > "Winbench95" does not use Windows95 WIN32 interfaces -- it's > still mostly a 16 bit code benchmark, for what that's worth. > > I'd like to see Ziff-Davis port to UNIX, but I think it's unlikely. > > > Terry Lambert > terry@lambert.org Well - the leader of the Ziff-Davis Winbench project just happens to be a personal friend of mine! I'm usually either at his house on the weekends, or he's over here... He finds a *lot* of weirdness lying around in some of these graphics cards... it can get kinda ridiculous. He's always got _the latest_ of everything to benchmark. I will pass along any suggestions you'd like to make. Although, they are really a Windows/DOS-centric operation (less DOS now, even.) Also, I could easily pass along any 'netbench' suggestions, but I don't know if they'll make it all the way. However, I think the answer will be that Xstone is the comparable benchmark for us to use... - Dave R. - From owner-freebsd-hackers Wed Apr 24 08:29:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA24879 for hackers-outgoing; Wed, 24 Apr 1996 08:29:13 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA24869 for ; Wed, 24 Apr 1996 08:29:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id IAA11587; Wed, 24 Apr 1996 08:28:06 -0700 (PDT) To: Michael Smith cc: jmacd@CS.Berkeley.EDU (Josh MacDonald), bde@zeta.org.au, freebsd-hackers@FreeBSD.org Subject: Re: GNU binutils port In-reply-to: Your message of "Wed, 24 Apr 1996 21:27:21 +0930." <199604241157.VAA19097@genesis.atrad.adelaide.edu.au> Date: Wed, 24 Apr 1996 08:28:06 -0700 Message-ID: <11585.830359686@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > gcc -Wall is _pedantic_. Consider how many of the above are > "Consider parentheses around assignment used as truth value", or > "Integer used as pointer without a cast" (for use of '0' as a [legitimate] > substitute for NULL. Well, I think one needs to step back a bit at some point in any debate of this nature and ask a more fundamental question: "Just what are we trying to accomplish here?" With -Wall, I can only tell you what *I'm* trying to accomplish. What you may wish to accomplish may not jibe at all with this, and if a debate does nothing more than establish that early on then it's accomplished more than most debates. I use -Wall in order to help me find stupid bugs in my code. It's actually pretty good at this, and so I use it. In order to use it, I also add things like extra parentheses around assignment expressions (and, given that I also happen to *prefer* the: ``if ((blah = frob()) != bar)'' style, that's scarcely a hardship) and basically do whatever else I need to do to make the fool thing happy. That's just part of the price for using the tool, same as with any tool. Jordan From owner-freebsd-hackers Wed Apr 24 09:22:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA28414 for hackers-outgoing; Wed, 24 Apr 1996 09:22:20 -0700 (PDT) Received: from ntserv.webleicester.co.uk (ntserv.webleicester.co.uk [206.249.75.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA28409 for ; Wed, 24 Apr 1996 09:22:17 -0700 (PDT) Received: from [206.249.75.17] by ntserv.webleicester.co.uk (NTMail 3.01.00) id la003053; Wed, 24 Apr 1996 16:22:11 +0000 Received: from LANSYS/SpoolDir by lansys.webleicester.co.uk (Mercury 1.21); 24 Apr 96 17:22:43 +0000 Received: from SpoolDir by LANSYS (Mercury 1.21); 24 Apr 96 17:22:24 +0000 From: "Phil Taylor" Organization: Lan Systems To: hackers@freebsd.org Date: Wed, 24 Apr 1996 17:22:20 GMT Subject: vx driver (3c590) problems !!! Reply-to: phil@lansys.webleicester.co.uk Priority: normal X-mailer: Pegasus Mail for Windows (v2.31) Message-ID: X-Info: The Web Factory (Leicester) Electronic Mail System Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to use a 3c590 with the 0323 SNAP and I am having problems. The card is marked up as rev B but it is probed as an old 'faulty' card, I understand from previous postings that this is a problem with invalid probing so I ignored that. On power-up the card is detected properly but hangs on ifconfig, only a ctrl-c will allow the boot process to continue (it also hangs on sendmail not surprisingly). No network activity is then allowed. If I then reboot the machine everything works fine. Is there any additional configuration I need to do as I don't really want to scrap the card. Has the driver been improved since this snap, and if so should I be able to merge the newer driver into the kernel without any problems? Cheers /* Phil Taylor phil@webleicester.co.uk LAN Systems - LAN/WAN Specialists Tel: (Direct Line) 0116 223 0033 (Main Number) 0116 255 9961 (Facsimile) 0116 255 8861 */ From owner-freebsd-hackers Wed Apr 24 09:30:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA29037 for hackers-outgoing; Wed, 24 Apr 1996 09:30:48 -0700 (PDT) Received: from gateway.zeus.leitch.com (gateway.zeus.leitch.com [205.210.38.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA29032 for ; Wed, 24 Apr 1996 09:30:45 -0700 (PDT) Received: from tap.zeus.leitch.com (tap.zeus.leitch.com [204.187.60.10]) by gateway.zeus.leitch.com (8.6.12/8.6.9) with ESMTP id MAA23795 for ; Wed, 24 Apr 1996 12:42:36 -0400 Received: from ale.zeus.leitch.com (ale.zeus.leitch.com [204.187.61.65]) by tap.zeus.leitch.com (8.6.12/8.6.6) with ESMTP id MAA16773; Wed, 24 Apr 1996 12:31:19 -0400 From: Dave Chapeskie Received: (dchapes@localhost) by ale.zeus.leitch.com (8.6.12/8.6.9) id MAA06404; Wed, 24 Apr 1996 12:31:19 -0400 Message-Id: <199604241631.MAA06404@ale.zeus.leitch.com> Subject: Character device major numbers. To: FreeBSD-hackers@freebsd.org Date: Wed, 24 Apr 1996 12:31:19 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL14 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all, I have a problem I hope someone can help me with. The company I work for is using FreeBSD a new product. We've written three device drivers to support some custom cards that the product needs to use. The problem is that there is only one reserved cdev major number. IMHO, It doesn't make sense for my company to go through the effort of making the drivers loadable to sidestep the major number issue since the product is a complete system and we provide a prebuilt kernel and the drivers will be in constant use while the system is in use. It also doesn't make sense to request that multiple cdev major numbers be reserved just for these Leitch drivers since the cards are not widely available (two of the three will not be sold outside of this system at all). What I'd like to recommend is that several additional major numbers be reserved for local use. For example having eight reserved major numbers for use within any one organization should be sufficient for any current organizations and yet should not impact the size of the cdev/bdev switch tables very much. What do you think? Is there a better solution? -- Dave Chapeskie Leitch Technology International Inc. Email: dchapes@zeus.leitch.com From owner-freebsd-hackers Wed Apr 24 09:47:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA00372 for hackers-outgoing; Wed, 24 Apr 1996 09:47:52 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA00366 Wed, 24 Apr 1996 09:47:47 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id LAA19232; Wed, 24 Apr 1996 11:41:48 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB31D3.78BC7DE0@webster.unety.net>; Wed, 24 Apr 1996 11:45:01 -0500 Message-ID: <01BB31D3.78BC7DE0@webster.unety.net> From: Jim Fleming To: "'Cat Okita'" , "Rodney W. Grimes" Cc: "current@FreeBSD.org" , "davidg@Root.COM" , "hackers@FreeBSD.org" , "hasty@rah.star-gate.com" , "scrappy@ki.net" Subject: RE: Intelligent Debugging Tools... Date: Wed, 24 Apr 1996 11:45:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 9:20 AM, Cat Okita[SMTP:cat@ghost.uunet.ca] wrote: @On Wed, 24 Apr 1996, Rodney W. Grimes wrote: @or on the drive. External termination is right out in front of your eyes. @ @Being overly used to the world of unix-designed machines (ie: sun, dec...), @it was a really nasty shock to discover that PC's *normally* terminate @on the drives... @ @cheers! @cat @ @ Yes and vacuum tubes had little orange filaments that you could "see" through the glass and this told you they were working. There was a pin with filament voltage and you knew just where to wire it. Life was great. With Integrated Circuits the filament(s) are "hidden" inside. They are so tiny that you can not see them and to top that off, the designers were able to eliminate the pin. The miracles of modern science....;-) -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-hackers Wed Apr 24 10:09:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA01785 for hackers-outgoing; Wed, 24 Apr 1996 10:09:28 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA01779 Wed, 24 Apr 1996 10:09:24 -0700 (PDT) Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA28104 ; Wed, 24 Apr 1996 10:09:23 -0700 Received: from oscar.cc.gatech.edu (cau@oscar.cc.gatech.edu [130.207.107.12]) by burdell.cc.gatech.edu (8.7.5/8.6.9) with ESMTP id NAA08418; Wed, 24 Apr 1996 13:07:48 -0400 (EDT) Received: (from cau@localhost) by oscar.cc.gatech.edu (8.7.5/8.6.9) id NAA22678; Wed, 24 Apr 1996 13:07:46 -0400 (EDT) From: cau@cc.gatech.edu (Carlos Ugarte) Message-Id: <199604241707.NAA22678@oscar.cc.gatech.edu> Subject: Re: Intelligent Debugging Tools... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 24 Apr 1996 13:07:44 -0400 (EDT) Cc: scrappy@ki.net, msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: <199604240259.MAA14238@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 96 12:29:49 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You should spend some time at night with the new daemon book, which > should be out shortly - "The design and implementation of the 4.4 BSD > Unix operating system" and perhaps also "The Magic Garden explained". For those who are interested, Addison Wesley has a web page on the new book. The URL is http://heg-school.aw.com/cseng/authors/mckusick/4.4bsd/4.4bsd.html Two bookstores told me that it would take them about a month to get it, as it is so new. The cost would be comparable to that of the 4.3BSD book. It also mentions the BSD T-shirts ("old" models, and how to order the new ones) somewhere around there. I remember someone asked about this a couple of weeks back on one of the lists. Carlos -- Carlos A. Ugarte cau@cc.gatech.edu Author of PageMage, a virtual desktop util for OS/2 http://www.cc.gatech.edu/people/home/cau/ If you understand what you're doing, you are not learning anything From owner-freebsd-hackers Wed Apr 24 10:40:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03909 for hackers-outgoing; Wed, 24 Apr 1996 10:40:37 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03889 Wed, 24 Apr 1996 10:40:33 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199604241740.KAA03889@freefall.freebsd.org> Subject: Unix Books To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 24 Apr 1996 10:40:33 -0700 (PDT) Cc: scrappy@ki.net, msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: <199604240341.NAA14787@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 96 01:11:40 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > Marc G. Fournier stands accused of saying: > > > > > You should spend some time at night with the new daemon book, which > > > should be out shortly - "The design and implementation of the 4.4 BSD > > > Unix operating system" and perhaps also "The Magic Garden explained". > > > > > I will *definitely* look for these books... > > Check the handbook, as I think they're on the reading list. > > If not, check the -hackers archive for Terry Lambert talking about > the 'magic garden' book - his reading list was pretty comprehensive. it was the book by Uresh Vahalia "Unix Internals: The New Frontiers", ISBN 0131019082, rather than "The Magic Garden explained". look for terry's name in the acknowledgements section. -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ From owner-freebsd-hackers Wed Apr 24 10:46:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA04297 for hackers-outgoing; Wed, 24 Apr 1996 10:46:57 -0700 (PDT) Received: from kanto.cc.jyu.fi (root@kanto.cc.jyu.fi [130.234.1.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA04292 for ; Wed, 24 Apr 1996 10:46:54 -0700 (PDT) Received: from localhost (kallio@localhost [127.0.0.1]) by kanto.cc.jyu.fi (8.7.2/8.7.2) with SMTP id UAA12242; Wed, 24 Apr 1996 20:46:32 +0300 (EET DST) Date: Wed, 24 Apr 1996 20:46:30 +0300 (EET DST) From: Seppo Kallio Reply-To: Seppo Kallio To: "Jordan K. Hubbard" cc: hackers@freefall.FreeBSD.org Subject: BUG in FreeBSD 2.1R In-Reply-To: <561.815551994@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If I have /opt/ftp directory with permissions -rwx----- Then I mount /opt/ftp /dev/sd1a having -rwxr-xr-x The /opt/ftp directory is getting the real permissions from the original directory definition, but it is SHOWING the permissions the mounted disk directory has. It is very missleading, 1. it should show the poermissions /opt/ftp has or 2. it should not care about permissions /opt/ftp has and obey mounted filesystem permissions. Seppo Kallio U of Jyvaskyla Finland From owner-freebsd-hackers Wed Apr 24 11:40:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA07840 for hackers-outgoing; Wed, 24 Apr 1996 11:40:08 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA07795 for ; Wed, 24 Apr 1996 11:40:04 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id EAA19918; Thu, 25 Apr 1996 04:05:26 +0930 From: Michael Smith Message-Id: <199604241835.EAA19918@genesis.atrad.adelaide.edu.au> Subject: Re: GNU binutils port To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 25 Apr 1996 04:05:25 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, jmacd@CS.Berkeley.EDU, bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <11585.830359686@time.cdrom.com> from "Jordan K. Hubbard" at Apr 24, 96 08:28:06 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > I use -Wall in order to help me find stupid bugs in my code. It's > actually pretty good at this, and so I use it. In order to use it, I > also add things like extra parentheses around assignment expressions > (and, given that I also happen to *prefer* the: ``if ((blah = frob()) > != bar)'' style, that's scarcely a hardship) and basically do whatever > else I need to do to make the fool thing happy. That's just part of > the price for using the tool, same as with any tool. ...this is exactly why I use -Wall for my code, and follow similar conventions. However, not everyone does. Pointing at a (large) piece of software that generates a spastic number of warnings with -Wall and saying "this software is broken" isn't terribly valid. Having said that, I seem to remember that one of the oldest comments in the 'things for newcomers to do' file has been "make the kernel compile cleanly with -Wall" 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Apr 24 13:39:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20538 for hackers-outgoing; Wed, 24 Apr 1996 13:39:19 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20489 Wed, 24 Apr 1996 13:39:01 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA04680; Wed, 24 Apr 1996 16:38:44 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA00407; Wed, 24 Apr 1996 16:38:41 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 16:38:40 -0400 (EDT) From: "Marc G. Fournier" To: "Rodney W. Grimes" cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240851.BAA04106@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > Why? And how many changes are there in your kernel config file with > respect to the GENERIC kernel? Did you make the fatal mistakes that > others have made and started from the LINT config file instead of the > GENERIC config? > *groan* What's wrong with using the LINT config file and trimming it down to what you want? Here's my config file (pt0/sctarg0) removed...in case there is something else i shouldn't have configured in? :( ---- machine "i386" cpu "I486_CPU" ident kinet # # The `maxusers' parameter controls the static sizing of a number of # internal system tables by a complicated formula defined in param.c. # maxusers 32 # # Under some circumstances it is necessary to make the default max # number of processes per user and open files per user more than the # defaults on bootup. (an example is a large news server in which # the uid, news, can sometimes need > 100 simultaneous processes running, # or perhaps a user using lots of windows under X). options "CHILD_MAX=128" options "OPEN_MAX=128" config kernel root on sd0 options "COMPAT_43" options SYSVSHM options "SHMMAXPGS=512" # 2048Kb (?) of sharable memory options SYSVSEM options SYSVMSG options DDB options DODUMP options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device tun 1 #Tunnel driver(user process ppp) # One of these is mandatory: options FFS #Fast filesystem options NFS #Network File System options PROCFS #Process filesystem options QUOTA #enable disk quotas controller scbus0 #base SCSI code device sd0 #SCSI disks pseudo-device pty 64 #Pseudo ttys - can go as high as 64 pseudo-device log #Kernel syslog interface (/dev/klog) controller isa0 options BOUNCE_BUFFERS # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr controller pci0 device ncr0 Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Wed Apr 24 13:39:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20610 for hackers-outgoing; Wed, 24 Apr 1996 13:39:51 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20589 Wed, 24 Apr 1996 13:39:43 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA04767; Wed, 24 Apr 1996 16:39:45 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA00414; Wed, 24 Apr 1996 16:39:44 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 16:39:43 -0400 (EDT) From: "Marc G. Fournier" To: Cat Okita cc: "Rodney W. Grimes" , davidg@Root.COM, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Cat Okita wrote: > Being overly used to the world of unix-designed machines (ie: sun, dec...), > it was a really nasty shock to discover that PC's *normally* terminate > on the drives... > What? Sun/Dec don't use the same SCSI drives? Weird... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Wed Apr 24 13:45:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21909 for hackers-outgoing; Wed, 24 Apr 1996 13:45:51 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21900 for ; Wed, 24 Apr 1996 13:45:46 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA05198; Wed, 24 Apr 1996 16:45:11 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA00436; Wed, 24 Apr 1996 16:45:08 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 16:45:08 -0400 (EDT) From: "Marc G. Fournier" To: Joerg Wunsch cc: FreeBSD hackers Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240655.IAA26285@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, J Wunsch wrote: > DODUMP is gone. > Ah, okay, will take that out of my config file... > Use dumpon(8) instead, or > I do have this set in my sysconfig file, as well as the dumpdev... someone in -stable suggested it may be a problem wiht the NCR controller not doing polling (or something like that) which the dump requires (see -stable for exact message) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Wed Apr 24 13:46:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21982 for hackers-outgoing; Wed, 24 Apr 1996 13:46:07 -0700 (PDT) Received: from ghost.uunet.ca (ghost.uunet.ca [142.77.1.100]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21963 Wed, 24 Apr 1996 13:45:59 -0700 (PDT) Received: by ghost.uunet.ca id <52832-26041>; Wed, 24 Apr 1996 16:45:52 -0400 Date: Wed, 24 Apr 1996 16:45:48 -0400 From: Cat Okita To: "Marc G. Fournier" cc: "Rodney W. Grimes" , davidg@Root.COM, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Marc G. Fournier wrote: > What? Sun/Dec don't use the same SCSI drives? Weird... I think that you must have missed the start of this thread. The question wasn't if drives *could* be terminated on the drive, but rather whether it was a better option to terminate *internally* or *externally*. Typically, the drives which I've used in Sun/Dec machines don't arrive with termination set on the drive - it's set externally. In the PC world, drives usually arrive with termination set on the drive, which becomes an awkward and annoying problem when you start adding SCSI devices. If this still isn't clear, drop me a line in private email - no need to try the list with definitions of internal/external... Cat From owner-freebsd-hackers Wed Apr 24 13:51:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA22821 for hackers-outgoing; Wed, 24 Apr 1996 13:51:54 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA22809 for ; Wed, 24 Apr 1996 13:51:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with SMTP id VAA03853 ; Wed, 24 Apr 1996 21:43:48 +0100 (BST) To: Michael Smith cc: jmacd@CS.Berkeley.EDU (Josh MacDonald), bde@zeta.org.au, freebsd-hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: GNU binutils port In-reply-to: Your message of "Wed, 24 Apr 1996 21:27:21 +0930." <199604241157.VAA19097@genesis.atrad.adelaide.edu.au> Date: Wed, 24 Apr 1996 21:43:47 +0100 Message-ID: <3851.830378627@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote in message ID <199604241157.VAA19097@genesis.atrad.adelaide.edu.au>: > Josh MacDonald stands accused of saying: > > Oh dear.... I can't beleive you're saying this, "They are only warnings". > > > > To me, it has, "My code sucks and I don't care." written all over > > it if you don't fix things so that they compile with no warnings > > and -Wall. Perhaps kernel code is a bit different, but with 4700 > > warnings, I'd be little scared. I wouldn't be. I've got a development tree with over half those warnings fixed, and none of them (well, okay, one) could have done anything nasty. And from a quick glance through, most of the rest are printf() formatting warnings, as GCC can't understand some of the special printf contructs available in the kernel. > gcc -Wall is _pedantic_. Consider how many of the above are > "Consider parentheses around assignment used as truth value", or > "Integer used as pointer without a cast" (for use of '0' as a [legitimate] > substitute for NULL. Which is why I was using -Wall -Wno-parenthesis (or something, I can't find my makefile now) to shut up that warning. It bugs the hell out of me. Another thing: AFAIR, GCC 2.6.3 does NOT meet the ANSI standards for compiler warnings & errors. I could be wrong, but if someone gets a commercial C compiler which DOES, and throws our kernel sources at it, I'll bet there'll be several more warnings (and even an error or two), even after removing all the GCC/GAS/GLD dependancy that we have (and I don't like having). Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD - Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info. From owner-freebsd-hackers Wed Apr 24 14:10:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25377 for hackers-outgoing; Wed, 24 Apr 1996 14:10:43 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA25344 for ; Wed, 24 Apr 1996 14:10:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with SMTP id WAA04098 ; Wed, 24 Apr 1996 22:09:37 +0100 (BST) To: jleppek@suw2k.hisd.harris.com (James Leppek) cc: freebsd-hackers@freefall.freebsd.org From: "Gary Palmer" Subject: Re: could tunnel device do this? In-reply-to: Your message of "Mon, 22 Apr 1996 09:50:45 EDT." <9604221350.AA06758@suw2k.hisd.harris.com> Date: Wed, 24 Apr 1996 22:09:37 +0100 Message-ID: <4096.830380177@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk James Leppek wrote in message ID <9604221350.AA06758@suw2k.hisd.harris.com>: > This is really a 2 part question: > part 1: what would be the best way to route all IP packets from a > ethernet card to a process, I am guessing that the tun > device could do this. I don't think you can do this. The `tun' device acts like a normal network interface, and has it's own route, etc, so you couldn't just dump all the traffic from an ethernet onto it, the packet would have to be routed to the i/f. Perhaps the `bpf' device is what you're looking for? > part 2: what kind of thruput could be expected when doing this? If I had > a pentium 166 could it saturate a 10Mbit line? What % of a 100Mbit link Dunno ... you were asking in part one about dumping ether -> process, not vice versa! Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD - Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info. From owner-freebsd-hackers Wed Apr 24 14:16:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25921 for hackers-outgoing; Wed, 24 Apr 1996 14:16:21 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA25882 Wed, 24 Apr 1996 14:16:05 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA26948; Wed, 24 Apr 1996 23:16:16 +0200 Received: by uni4nn.iaf.nl with UUCP id AA29128 (5.67b/IDA-1.5); Wed, 24 Apr 1996 23:15:51 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA27881 (5.67b/IDA-1.5); Wed, 24 Apr 1996 23:01:32 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id UAA00617; Wed, 24 Apr 1996 20:15:57 +0200 From: Wilko Bulte Message-Id: <199604241815.UAA00617@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 20:15:57 +0200 (MET DST) Cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 06:00:06 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > real memory = 16777216 (16384K bytes) > avail memory = 14835712 (14488K bytes) > Probing for devices on PCI bus 0: > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 12 on pci0:11 > (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 It might also be interesting to disable tagged command queuing on the ncr. Something like '/usr/sbin/ncrcontrol -s tags=0' does this. I had mysterious lockups on my system (not even the mouse cursor or keyboard would do anything) and this TCQ disable made this go away (thanks Stefan for the suggestion). Admittedly it is not a panic but maybe it makes a difference (BTW I flashed new firmware on my drive and now TCQ enabled also works) Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-hackers Wed Apr 24 14:19:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA26277 for hackers-outgoing; Wed, 24 Apr 1996 14:19:52 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA26264 for ; Wed, 24 Apr 1996 14:19:43 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA16448; Wed, 24 Apr 1996 15:18:22 -0600 Date: Wed, 24 Apr 1996 15:18:22 -0600 From: Nate Williams Message-Id: <199604242118.PAA16448@rocky.sri.MT.net> To: "Marc G. Fournier" Cc: hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: References: <199604240851.BAA04106@GndRsh.aac.dev.com> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ Trimmed down the CC list ] Marc G. Fournier writes: > *groan* What's wrong with using the LINT config file and > trimming it down to what you want? LINT is meant to contain *ALL* of the available options, but is not meant to give you a runnable kernel. Start with GENERIC and ADD/REMOVE options from it based on LINT code is the best way. If you start with GENERIC, you'll be much less likely to get a hosed up kernel due to using some un-supported/un-tested feature. Try starting over with GENERIC and see what it buys you. Nate From owner-freebsd-hackers Wed Apr 24 14:21:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA26495 for hackers-outgoing; Wed, 24 Apr 1996 14:21:33 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA26481 for ; Wed, 24 Apr 1996 14:21:23 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA10985; Wed, 24 Apr 1996 23:19:49 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA28979; Wed, 24 Apr 1996 23:19:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA28082; Wed, 24 Apr 1996 22:46:16 +0200 (MET DST) From: J Wunsch Message-Id: <199604242046.WAA28082@uriah.heep.sax.de> Subject: Re: GNU binutils port To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 24 Apr 1996 22:46:15 +0200 (MET DST) Cc: msmith@atrad.adelaide.edu.au (Michael Smith) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604241157.VAA19097@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 96 09:27:21 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > gcc -Wall is _pedantic_. Consider how many of the above are > "Consider parentheses around assignment used as truth value", or This is something all good compilers warn, since it's perhaps one of the most common errors for C programmers to forget one `=' in a comparision. > "Integer used as pointer without a cast" (for use of '0' as a [legitimate] > substitute for NULL. Huh? j@uriah 114% cat > foo.c int foo(void) { char *bar; bar = 0; return 23 * *bar; } j@uriah 115% cc -c -Wall -pedantic foo.c j@uriah 116% No warning. -- 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 Apr 24 14:29:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA27218 for hackers-outgoing; Wed, 24 Apr 1996 14:29:26 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA27207 for ; Wed, 24 Apr 1996 14:29:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id OAA12619; Wed, 24 Apr 1996 14:27:18 -0700 (PDT) To: Dave Chapeskie cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: Character device major numbers. In-reply-to: Your message of "Wed, 24 Apr 1996 12:31:19 EDT." <199604241631.MAA06404@ale.zeus.leitch.com> Date: Wed, 24 Apr 1996 14:27:18 -0700 Message-ID: <12617.830381238@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > IMHO, It doesn't make sense for my company to go through the effort > of making the drivers loadable to sidestep the major number issue since > ... > > It also doesn't make sense to request that multiple cdev major > numbers be reserved just for these Leitch drivers since the cards are not > widely available (two of the three will not be sold outside of this > ... All perfectly reasonable. > > What I'd like to recommend is that several additional major numbers > be reserved for local use. For example having eight reserved major > ... > What do you think? Is there a better solution? I think it's called `devfs' :-) Seriously - /sys/i386/i386/conf.c no longer exists. It is gone. There are still wild assumptions being made about the validity of certain major/minors, mind you, given that just about everyone is still running off of a non-devfs /dev (Julian, when's this thing going to become safe enough to use by *default* in -current? :-) but that will change soon enough. Then you guys can stop worrying about the assignments at all - they'll be totally dynamic. :) Jordan From owner-freebsd-hackers Wed Apr 24 14:42:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28605 for hackers-outgoing; Wed, 24 Apr 1996 14:42:41 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA28581 Wed, 24 Apr 1996 14:42:28 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA05847; Wed, 24 Apr 1996 14:41:00 -0700 From: "Rodney W. Grimes" Message-Id: <199604242141.OAA05847@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 14:40:59 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at "Apr 24, 96 04:38:40 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > > Why? And how many changes are there in your kernel config file with > > respect to the GENERIC kernel? Did you make the fatal mistakes that > > others have made and started from the LINT config file instead of the > > GENERIC config? > > > *groan* What's wrong with using the LINT config file and > trimming it down to what you want? Many people don't trim it down enough and end up with strange problems, looks as if you did a good trim job though I really doubt your need for *_MAX=128 and SHMMAXPGS=512. I also thought you had an NCR scsi controller, which means you don't need BOUNCE_BUFFERS. > Here's my config file (pt0/sctarg0) removed...in case there > is something else i shouldn't have configured in? :( ... > # Under some circumstances it is necessary to make the default max > # number of processes per user and open files per user more than the > # defaults on bootup. (an example is a large news server in which > # the uid, news, can sometimes need > 100 simultaneous processes running, > # or perhaps a user using lots of windows under X). > options "CHILD_MAX=128" > options "OPEN_MAX=128" Do you _really_ need these? > config kernel root on sd0 > > options "COMPAT_43" > options SYSVSHM > options "SHMMAXPGS=512" # 2048Kb (?) of sharable memory The default is 1024, you trimming this on purpose? ... > options QUOTA #enable disk quotas Unless you are really using QUOTA's remove it. > > options BOUNCE_BUFFERS Hummmm PCI machine with NCR scsi controller, nope you do not need this, remove it! ... > controller pci0 > device ncr0 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hackers Wed Apr 24 14:44:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28852 for hackers-outgoing; Wed, 24 Apr 1996 14:44:50 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA28839 for ; Wed, 24 Apr 1996 14:44:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id OAA12692; Wed, 24 Apr 1996 14:43:59 -0700 (PDT) To: Michael Smith cc: jmacd@CS.Berkeley.EDU, bde@zeta.org.au, freebsd-hackers@FreeBSD.org Subject: Re: GNU binutils port In-reply-to: Your message of "Thu, 25 Apr 1996 04:05:25 +0930." <199604241835.EAA19918@genesis.atrad.adelaide.edu.au> Date: Wed, 24 Apr 1996 14:43:59 -0700 Message-ID: <12689.830382239@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > ...this is exactly why I use -Wall for my code, and follow similar > conventions. However, not everyone does. Pointing at a (large) > piece of software that generates a spastic number of warnings with > -Wall and saying "this software is broken" isn't terribly valid. No, no, Mike, you're still not grasping the essential point - it's *totally* valid to say this, just as it's a totally valid response to say: "By Jeves, you're right! Damn good eyes, man! Erm, be a good chap and send us the diffs once you've fixed this, won't you? A nasty business, we'll agree, and why if we didn't all have carpal-tunnel syndrome over here we'd certainly be right in there helping you, you can be most assured of that. Duffy used to be right on things like this, he was, but then there was his war wound and that unpleasant business with the gophers and the high explosive, and I myself just can't seem to move as fast as I once could given that ... [insert 4 pages of boilerplate text listing various physical ailments, both real and imagined]." You'll either get a fix or the complainer will never mention the matter again - either way, it's a win! :-) > Having said that, I seem to remember that one of the oldest comments > in the 'things for newcomers to do' file has been "make the > kernel compile cleanly with -Wall" 8) Yeah, and I was wondering why the supply of newcomers seemed to be drying up so! :) Jordan P.S. Actually, to be truly factual, the number of volunteers has been steadily increasing as of late! We've rarely had it so good. From owner-freebsd-hackers Wed Apr 24 14:52:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA29752 for hackers-outgoing; Wed, 24 Apr 1996 14:52:20 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA29743 for ; Wed, 24 Apr 1996 14:52:16 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA11787; Wed, 24 Apr 1996 23:52:01 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA29259; Wed, 24 Apr 1996 23:52:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id XAA28721; Wed, 24 Apr 1996 23:37:24 +0200 (MET DST) From: J Wunsch Message-Id: <199604242137.XAA28721@uriah.heep.sax.de> Subject: Re: BUG in FreeBSD 2.1R To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 24 Apr 1996 23:37:24 +0200 (MET DST) Cc: kallio@cc.jyu.fi Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Seppo Kallio" at Apr 24, 96 08:46:30 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Seppo Kallio wrote: > > If I have > > /opt/ftp directory with permissions -rwx----- > > Then I mount /opt/ftp /dev/sd1a having -rwxr-xr-x > > The /opt/ftp directory is getting the real permissions from the original > directory definition, but it is SHOWING the permissions the mounted disk > directory has. cd /opt/ftp pwd :-) This seems to be a bug with all Unix implementations i've seen so far. The simplest workaround: since mount points finally always use the permissions from the mounted resource, do always give them 555 or 755 permissions. -- 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 Apr 24 14:52:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA29820 for hackers-outgoing; Wed, 24 Apr 1996 14:52:58 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA29805 for ; Wed, 24 Apr 1996 14:52:49 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA11804; Wed, 24 Apr 1996 23:52:08 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA29263; Wed, 24 Apr 1996 23:52:08 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id XAA28850; Wed, 24 Apr 1996 23:51:26 +0200 (MET DST) From: J Wunsch Message-Id: <199604242151.XAA28850@uriah.heep.sax.de> Subject: Re: Character device major numbers. To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 24 Apr 1996 23:51:25 +0200 (MET DST) Cc: dchapes@zeus.leitch.com (Dave Chapeskie) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604241631.MAA06404@ale.zeus.leitch.com> from "Dave Chapeskie" at Apr 24, 96 12:31:19 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Dave Chapeskie wrote: > The company I work for is using FreeBSD a new product. We've written > three device drivers to support some custom cards that the product needs > to use. The problem is that there is only one reserved cdev major > number. > What do you think? Is there a better solution? Yes, ``devfs''. There's still a lot of work in front of us before it will be production level quality, but we are positive to have it running in 2.2R. With a few exceptions, fixed major number assignments should be past 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 Wed Apr 24 15:17:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03076 for hackers-outgoing; Wed, 24 Apr 1996 15:17:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA03065 for ; Wed, 24 Apr 1996 15:17:24 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23099; Wed, 24 Apr 1996 15:12:40 -0700 From: Terry Lambert Message-Id: <199604242212.PAA23099@phaeton.artisoft.com> Subject: Re: GNU binutils port To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Date: Wed, 24 Apr 1996 15:12:40 -0700 (MST) Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <199604240837.BAA19783@paris.CS.Berkeley.EDU> from "Josh MacDonald" at Apr 24, 96 01:37:57 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > They are only warnings and many would go away if less warnings were enabled. > > There would be many more if more were enabled. For the LINT kernel built on > > Apr 6, the warning counts were: > > > > compiler warnings (lines) > > -------- -------- > > cc 74 > > cc -Wall 2394 > > gcc-2.7.2 4694 > > > > Oh dear.... I can't beleive you're saying this, "They are only warnings". > > To me, it has, "My code sucks and I don't care." written all over > it if you don't fix things so that they compile with no warnings > and -Wall. Perhaps kernel code is a bit different, but with 4700 > warnings, I'd be little scared. I really doubt sizeof(void *) != sizeof(??? *) any time soon. Anyone here planning on porting to a platform with split I and D? Can you get 5M in a PDP8? The compiler is being unbearably anal for most of those 4694 warnings. The language didn't change to get those extra 2300 warnings, the compiler did. 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 Apr 24 15:21:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03605 for hackers-outgoing; Wed, 24 Apr 1996 15:21:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA03599 for ; Wed, 24 Apr 1996 15:21:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23109; Wed, 24 Apr 1996 15:14:31 -0700 From: Terry Lambert Message-Id: <199604242214.PAA23109@phaeton.artisoft.com> Subject: Re: GNU binutils port To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 24 Apr 1996 15:14:31 -0700 (MST) Cc: jmacd@CS.Berkeley.EDU, bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <199604241157.VAA19097@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 96 09:27:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Oh dear.... I can't beleive you're saying this, "They are only warnings". > > > > To me, it has, "My code sucks and I don't care." written all over > > it if you don't fix things so that they compile with no warnings > > and -Wall. Perhaps kernel code is a bit different, but with 4700 > > warnings, I'd be little scared. > > gcc -Wall is _pedantic_. Consider how many of the above are > "Consider parentheses around assignment used as truth value", or > "Integer used as pointer without a cast" (for use of '0' as a [legitimate] > substitute for NULL. > > A pile more would be historic warts where unions were avoided and pointers > to structures were passed around in a known context. Not to mention: if( ret = (x>>8)) "WARNING: ASSIGNMENT IN IF STATEMENT! I AM UNUTTERABLY ANAL!" 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 Apr 24 15:22:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03651 for hackers-outgoing; Wed, 24 Apr 1996 15:22:11 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA03643 Wed, 24 Apr 1996 15:21:53 -0700 (PDT) Received: by Sisyphos id AA05130 (5.67b/IDA-1.5); Thu, 25 Apr 1996 00:21:34 +0200 Message-Id: <199604242221.AA05130@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 25 Apr 1996 00:21:34 +0200 In-Reply-To: Ollivier Robert "Re: 82378ZB PCI ISA Bridge" (Apr 17, 23:34) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Ollivier Robert Subject: Re: 82378ZB PCI ISA Bridge Cc: hackers@freebsd.org, se@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry for the long delay, but I don't have easy access to mail, currently ... On Apr 17, 23:34, Ollivier Robert wrote: } Subject: Re: 82378ZB PCI ISA Bridge } It seems that Terry Lambert said: } > I believe the system should "run fine" without recognizing the bridge } > chips. } } Except it is hard to install an OS where the SVSI controller (NCR-based) is } not recognized at all by the system :-) The BIOS is responsible for initialization of all PCI bridge chips. If some PCI card is not detected by FreeBSD, there must be some other problem. It is NOT a problem in "pcisupport.c", which only prints some register dumps for debugging, but does not change the configuration of any bridge chip. } I've tried generating a floppy with the pcisupport.c file patched with the } 1.15->1.16 diff (which added the 82378ZB support in STABLE) but still no } luck. Many people completed an installation on a system with that chip. Please give detailed information, if the problem still exists. - is any PCI chip identified ? - where are those PCI chips mapped ? - is there any warning printed by the PCI probe ? Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hackers Wed Apr 24 15:25:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA04004 for hackers-outgoing; Wed, 24 Apr 1996 15:25:14 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA03963 Wed, 24 Apr 1996 15:25:06 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA04205; Wed, 24 Apr 1996 18:24:52 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA01890; Wed, 24 Apr 1996 18:24:54 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 18:24:54 -0400 (EDT) From: "Marc G. Fournier" To: "Rodney W. Grimes" cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604242141.OAA05847@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > Many people don't trim it down enough and end up with strange problems, > looks as if you did a good trim job though I really doubt your need > for *_MAX=128 and SHMMAXPGS=512. > The *_MAX are for my INND/Web servers...and the SHMMAXPGS is so that I can put in shared memory support in INND (one of these days *sigh*) > I also thought you had an NCR scsi controller, which means you don't > need BOUNCE_BUFFERS. > I had this in because of using an AHA controller in that machine, which I've put in intermediantly, but will take it out... > > options "COMPAT_43" > > options SYSVSHM > > options "SHMMAXPGS=512" # 2048Kb (?) of sharable memory > > The default is 1024, you trimming this on purpose? > Oh...that I *didn't* know :( Will remove this one too... > ... > > options QUOTA #enable disk quotas > > Unless you are really using QUOTA's remove it. > Am using it. Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-hackers Wed Apr 24 15:41:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05926 for hackers-outgoing; Wed, 24 Apr 1996 15:41:48 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA05870 for ; Wed, 24 Apr 1996 15:41:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23188; Wed, 24 Apr 1996 15:26:59 -0700 From: Terry Lambert Message-Id: <199604242226.PAA23188@phaeton.artisoft.com> Subject: Re: GNU binutils port To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 24 Apr 1996 15:26:59 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, jmacd@CS.Berkeley.EDU, bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <12689.830382239@time.cdrom.com> from "Jordan K. Hubbard" at Apr 24, 96 02:43:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Duffy used to be right on things like > this, he was, but then there was his war wound and that unpleasant > business with the gophers and the high explosive I thought we agreed not to talk about The Troubles... Poor old Duff'. 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 Apr 24 15:52:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA06721 for hackers-outgoing; Wed, 24 Apr 1996 15:52:01 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA06693 for ; Wed, 24 Apr 1996 15:51:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA24720; Thu, 25 Apr 1996 08:49:48 +1000 Date: Thu, 25 Apr 1996 08:49:48 +1000 From: Bruce Evans Message-Id: <199604242249.IAA24720@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, terry@lambert.org Subject: Re: GNU binutils port Cc: bde@zeta.org.au, freebsd-hackers@freebsd.org, jmacd@CS.Berkeley.EDU Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> gcc -Wall is _pedantic_. Consider how many of the above are Nah. It's not even pedantic. ``gcc \ -Wall -ansi -pedantic \ -Wbad-function-cast \ -Wcast-align \ -Wcast-qual \ -Wchar-subscripts \ -Wconversion \ -Werror \ -Winline \ -Wmissing-declarations \ -Wmissing-prototypes \ -Wnested-externs \ -Wpointer-arith \ -Wredundant-decls \ -Wshadow \ -Wstrict-prototypes \ -Wwrite-strings # Use these for code that has to be compilable with K&R compilers: # -Waggregate-return -Wid-clash-7 -Wtraditional'' is _pedantic_. I use something like the above in my gccw script. >> "Consider parentheses around assignment used as truth value", or I like this. OTOH, I hate the one about && vs || and always turn it off in my local cc1 binaries. >> "Integer used as pointer without a cast" (for use of '0' as a [legitimate] >> substitute for NULL. I haven't seen this. ANSI defines null pointer constants quite well and gcc implements them quite well. Bruce From owner-freebsd-hackers Wed Apr 24 15:52:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA06863 for hackers-outgoing; Wed, 24 Apr 1996 15:52:59 -0700 (PDT) Received: from gateway.zeus.leitch.com (gateway.zeus.leitch.com [205.210.38.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA06857 for ; Wed, 24 Apr 1996 15:52:55 -0700 (PDT) Received: from tap.zeus.leitch.com (tap.zeus.leitch.com [204.187.60.10]) by gateway.zeus.leitch.com (8.6.12/8.6.9) with ESMTP id TAA24856 for ; Wed, 24 Apr 1996 19:04:48 -0400 Received: from ale.zeus.leitch.com (ale.zeus.leitch.com [204.187.61.65]) by tap.zeus.leitch.com (8.6.12/8.6.6) with ESMTP id SAA20410 for ; Wed, 24 Apr 1996 18:53:32 -0400 From: Dave Chapeskie Received: (dchapes@localhost) by ale.zeus.leitch.com (8.6.12/8.6.9) id SAA07460 for FreeBSD-hackers@FreeBSD.ORG; Wed, 24 Apr 1996 18:53:32 -0400 Message-Id: <199604242253.SAA07460@ale.zeus.leitch.com> Subject: Re: Character device major numbers. To: FreeBSD-hackers@FreeBSD.ORG Date: Wed, 24 Apr 1996 18:53:31 -0400 (EDT) In-Reply-To: <12617.830381238@time.cdrom.com> from "Jordan K. Hubbard" at "Apr 24, 96 02:27:18 pm" X-Mailer: ELM [version 2.4ME+ PL14 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks to all that replied to my question. Jordan K. Hubbard wrote: > I think it's called `devfs' :-) > > Seriously - /sys/i386/i386/conf.c no longer exists. It is gone. Cool! I guess I should keep more informed on -current :-) With changes like this taking place is there anyplace that documents the correct way to install a new device driver into the system. For example for the dev_attach stuff I had to hunt through kernel source to find examples. It would be nice to have all the defvs and device registration routines documented somewhere. -- Dave Chapeskie Leitch Technology International Inc. Email: dchapes@zeus.leitch.com From owner-freebsd-hackers Wed Apr 24 16:11:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08268 for hackers-outgoing; Wed, 24 Apr 1996 16:11:41 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA08254 for ; Wed, 24 Apr 1996 16:11:36 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA25542; Thu, 25 Apr 1996 09:07:03 +1000 Date: Thu, 25 Apr 1996 09:07:03 +1000 From: Bruce Evans Message-Id: <199604242307.JAA25542@godzilla.zeta.org.au> To: jmacd@CS.Berkeley.EDU, terry@lambert.org Subject: Re: GNU binutils port Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> > They are only warnings and many would go away if less warnings were enabled. >> > There would be many more if more were enabled. For the LINT kernel built on >> > Apr 6, the warning counts were: >> > >> > compiler warnings (lines) >> > -------- -------- >> > cc 74 >> > cc -Wall 2394 >> > gcc-2.7.2 4694 >> > >> >> Oh dear.... I can't beleive you're saying this, "They are only warnings". >> >> To me, it has, "My code sucks and I don't care." written all over It's not my code :-). The point is that another 50000 or so lines of warnings could easily be produced by enabling enough warnings. I've already fixed 5000-10000 lines of warnings (10-20 of which were for real bugs on the i386) after enabling prototype warnings and don't feel like looking for more now. >I really doubt sizeof(void *) != sizeof(??? *) any time soon. It happens every day, but not on the i386. >Anyone here planning on porting to a platform with split I and D? The i386 supports it fine. >The compiler is being unbearably anal for most of those 4694 warnings. >The language didn't change to get those extra 2300 warnings, the compiler >did. Actually, only the compiler options changed. Bruce From owner-freebsd-hackers Wed Apr 24 16:13:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08468 for hackers-outgoing; Wed, 24 Apr 1996 16:13:59 -0700 (PDT) Received: (from mpp@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08462 for hackers; Wed, 24 Apr 1996 16:13:57 -0700 (PDT) From: Mike Pritchard Message-Id: <199604242313.QAA08462@freefall.freebsd.org> Subject: /etc/sysconfig & quotas/accounting (was Re: Intelligent Debugging Tools...) To: hackers Date: Wed, 24 Apr 1996 16:13:57 -0700 (PDT) In-Reply-To: from "Marc G. Fournier" at Apr 24, 96 06:24:54 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier wrote: > > On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > > > > options QUOTA #enable disk quotas > > > > Unless you are really using QUOTA's remove it. > > > Am using it. Does anyone object to my removing the comments in /etc/sysconfig that say that accounting and quotas probably dson't work and should not be enabled? I've been running with both those for something like 8 - 10 months without any problems. There is supposedly a problem with putting your quota files on the root file system (or maybe just having quotas on /), but I've never seen anyone file a PR with a system panic/hang mentioning this. As long as people follow the guidelines I put in the handbook, I think they should be just fine. BTW, when is the rest of the 4.4-lite2 integration going to take place? There are a couple of minor quota problems that would be fixed by that. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-hackers Wed Apr 24 16:15:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08570 for hackers-outgoing; Wed, 24 Apr 1996 16:15:28 -0700 (PDT) Received: from gateway.zeus.leitch.com (gateway.zeus.leitch.com [205.210.38.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA08532 for ; Wed, 24 Apr 1996 16:15:09 -0700 (PDT) Received: from tap.zeus.leitch.com (tap.zeus.leitch.com [204.187.60.10]) by gateway.zeus.leitch.com (8.6.12/8.6.9) with ESMTP id TAA24925 for ; Wed, 24 Apr 1996 19:26:59 -0400 Received: from ale.zeus.leitch.com (ale.zeus.leitch.com [204.187.61.65]) by tap.zeus.leitch.com (8.6.12/8.6.6) with ESMTP id TAA20540 for ; Wed, 24 Apr 1996 19:15:43 -0400 From: Dave Chapeskie Received: (dchapes@localhost) by ale.zeus.leitch.com (8.6.12/8.6.9) id TAA07530 for FreeBSD-hackers@FreeBSD.org; Wed, 24 Apr 1996 19:15:43 -0400 Message-Id: <199604242315.TAA07530@ale.zeus.leitch.com> Subject: BUG in FreeBSD 2.1R To: FreeBSD-hackers@FreeBSD.org Date: Wed, 24 Apr 1996 19:15:43 -0400 (EDT) In-Reply-To: <199604242137.XAA28721@uriah.heep.sax.de> X-Mailer: ELM [version 2.4ME+ PL14 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >As Seppo Kallio wrote: >> >> If I have >> >> /opt/ftp directory with permissions -rwx----- >> >> Then I mount /opt/ftp /dev/sd1a having -rwxr-xr-x >> >> The /opt/ftp directory is getting the real permissions from the original >> directory definition, but it is SHOWING the permissions the mounted disk >> directory has. > >cd /opt/ftp >pwd > >:-) > >This seems to be a bug with all Unix implementations i've seen so far. >The simplest workaround: since mount points finally always use the >permissions from the mounted resource, do always give them 555 or 755 >permissions. > >-- >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. ;-) This is not a bug. I asked this question a year and a half ago on comp.os.386bsd.questions when pwd started giving me errors and I got the following useful reply. The only thing the system uses the mount point's permissions for is in reading ".." >From: blymn@awadi.com.au (Brett Lymn) Newsgroups: comp.os.386bsd.questions Subject: Re: pwd problem with NFS Date: 05 Sep 1994 06:55:47 GMT Message-ID: At first I was going to just shrug my shoulders and say "I dunno" but after a bit of thought I think I have a theory (It's all mine!!!). The theory goes that though we are used to thinking that a file system "covers up" the underlying mount point. This cannot work for some things. Consider the concept of "..", from the file system point of view there is no ".." because it is the top of the tree. When that file system gets mounted under another one then I suppose some magic is done to point ".." of the mounted file system to the correct i-node of the mount point so that when you do something like "cd .." it works properly. Otherwise you would have the weird situation of doing a "cd .." from the mounted file system and staying where you are - just like you do in /. Now if the permissions of the mount point are such that you cannot read them then you cannot work out what you parent directory is hence the message from ls *but* the permissions you see for the mount point when something is mounted are those for "." of the mounted file system *not* the mount point. Getting everything to work so that you could see the underlying mount permissions without breaking the concept of just having something that looks like one big file system (anyone for VMS style sys$dsk0:[usr.blymn]? .... I thought not ;-) would be - ummmm - challenging. Managing disk storage on a unix system is made a lot easier by the fact you can do things like "hmmmm /var is filling up / a lot - I'll wack another disk on and mount it under /var to fix that" Dave> I wonder how many Dave> people get burned on this one. *Lots* I am on a Sun mailing list and see this problem turn up quite regularly. -- Brett Lymn -- Dave Chapeskie Leitch Technology International Inc. Email: dchapes@zeus.leitch.com From owner-freebsd-hackers Wed Apr 24 16:32:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA10145 for hackers-outgoing; Wed, 24 Apr 1996 16:32:27 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA10137 Wed, 24 Apr 1996 16:32:23 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA26281; Thu, 25 Apr 1996 09:30:03 +1000 Date: Thu, 25 Apr 1996 09:30:03 +1000 From: Bruce Evans Message-Id: <199604242330.JAA26281@godzilla.zeta.org.au> To: gpalmer@FreeBSD.ORG, msmith@atrad.adelaide.edu.au Subject: Re: GNU binutils port Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.ORG, jmacd@CS.Berkeley.EDU Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I wouldn't be. I've got a development tree with over half those >warnings fixed, and none of them (well, okay, one) could have done >anything nasty. And from a quick glance through, most of the rest are >printf() formatting warnings, as GCC can't understand some of the >special printf contructs available in the kernel. That's why fixing the warnings isn't a good project for beginners. The correct fix for some of the warnings may be to change the compiler. It _is_ the correct fix for %b format since this is a useful format. The correct fix for `printf("%d", long_variable);' may be to silently change the format to "%ld". The behaviour is undefined, so it is allowed to work. It works by accident when sizeof(int) == sizeof(long) but gcc issues a warning because it might not work on other systems or with other compilers. If gcc could guarantee that it worked on all systems when compiled by gcc, then it would be reasonable to suppress the warning unless the new flag -Wwarn_about_things_that_work_with_gcc_ but_may_not_work_with_other_compilers is used. The correct fix for other warnings may be to redesign some interfaces... >Another thing: AFAIR, GCC 2.6.3 does NOT meet the ANSI standards for >compiler warnings & errors. I could be wrong, but if someone gets a >commercial C compiler which DOES, and throws our kernel sources at it, >I'll bet there'll be several more warnings (and even an error or two), >even after removing all the GCC/GAS/GLD dependancy that we have (and I >don't like having). I hope there would only be a few errors detected. However, a compiler that does global optimizations at link time could probably detect that some of the thousands of bogus casts would cause undefined behaviour if they were executed, and the although it probably couldn't tell if they were executed, the nicest thing for it to do would be to warn about them all. There may be any number of nonfatal warnings since ANSI doesn't constrain warnings. Bruce From owner-freebsd-hackers Wed Apr 24 16:32:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA10181 for hackers-outgoing; Wed, 24 Apr 1996 16:32:34 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA10176 Wed, 24 Apr 1996 16:32:32 -0700 (PDT) Received: from toplink1.toplink.net (toplink1.toplink.net [194.163.120.1]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id QAA05270 ; Wed, 24 Apr 1996 16:32:29 -0700 Received: (from ck@localhost) by toplink1.toplink.net (8.6.9/8.6.9) id BAA26858; Thu, 25 Apr 1996 01:31:11 +0200 From: Christian Kratzer Message-Id: <199604242331.BAA26858@toplink1.toplink.net> Subject: Going gaga over Cyclades board To: hackers@freebsd.org, isp@freebsd.org Date: Thu, 25 Apr 1996 01:31:10 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Guys, we've been trying to wire up a cyclades 1400 based pccom 8 /port serial adapter under FreeBSD 2.1r. - I have compiled a kernel with the cy driver and used MAKEDEV ttyc0 ... ttyc7 to make the devices. - We have the board configured to irq 15 and d800. - The card is regcognized by the kernel on bootup. Apr 25 01:09:13 mail /kernel: cy0 irq 15 maddr 0xd8000 msize 8192 on isa - I have edited the modem part of rc.serial to initialize ttyc0 .. ttyc7 - We have 8 modems connected by DB25 connectors to the board - We use an ASUS P55 Tri Motherboard The problem is that using 'kermit -l /dev/cuac0' just hangs. No echo no nothing. Trying to exit kermit will leave it hanging around forever. We're at our wits end currently and would appreciate any pointers. Greetings Christian Kratzer -- TopLink GbR, Internet Services info@toplink.net Christian Kratzer http://www.toplink.net/ Phone: +49 7452 87174 Fax: +49 7452 87175 FreeBSD spoken here! From owner-freebsd-hackers Wed Apr 24 17:46:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA19705 for hackers-outgoing; Wed, 24 Apr 1996 17:46:58 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19629 for ; Wed, 24 Apr 1996 17:46:37 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id KAA29532; Thu, 25 Apr 1996 10:44:43 +1000 Date: Thu, 25 Apr 1996 10:44:43 +1000 From: Bruce Evans Message-Id: <199604250044.KAA29532@godzilla.zeta.org.au> To: jraynard@dial.pipex.com, julian@ref.tfs.com Subject: Re: Flaws in system() implementation? Cc: hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> > 1. Use of a wait union when an int would do. >> This is the correct POSIX thing to do.. >> check the man page for wait. >According to the 2.1.0-RELEASE man page, wait and friends use an int* >for the status variable. That is the correct POSIX thing. >> > 3. Returns 0 if fork() fails, when -1 seems more appropriate. >> POSIX says: >Thanks for posting this, I don't have access to any POSIX specs >(except the odd snippet in books). What's the best way of getting hold >of them? Joerg said that the draft POSIX spec is on the (old) WC Internet Info cdrom. I haven't got it. >> If "command" is a null pointer, the system() function returns non-zero >> only if a command processor is available. >OK (Out of interest, what kind of circumstances would result in a >command processor not being available?) Non-POSIX ones. system((char *)NULL) is about the only aspect of system() that is specified by ANSI. It returns 0 to tell you that system() is completely useless on the current system :-). >> If a child process cannot be created, >> or if the termination status of hte command interpretter cannot be obtained >> system() returns -1 >> and sets errno to indicate the error. >Doesn't that imply that system() should return -1 if fork() fails? >(Forgive me if I'm being obtuse, I'm not very experienced at reading >standardese). It's less ambiguous than julianese :-). It completely specifies the return value after a fork failure, at least in my copy, which says "shall return -1" instead of "returns -1". "shall" is standardese that means that the implementation is non-conforming if it does anything else. "should" would allow the implementation to screw up. Bruce From owner-freebsd-hackers Wed Apr 24 18:16:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23818 for hackers-outgoing; Wed, 24 Apr 1996 18:16:49 -0700 (PDT) Received: from mail.ca2.so-net.or.jp (mail.ca2.so-net.or.jp [202.238.95.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA23708 for ; Wed, 24 Apr 1996 18:15:32 -0700 (PDT) Received: from chiota (ppp6821.sng2.ap.so-net.or.jp [202.238.104.33]) by mail.ca2.so-net.or.jp (8.7.5/3.4W396011914) with SMTP id KAA19032; Thu, 25 Apr 1996 10:15:09 +0900 Received: from localhost (localhost [127.0.0.1]) by chiota (8.6.12/) with SMTP id KAA00305; Thu, 25 Apr 1996 10:14:06 +0900 Message-Id: <199604250114.KAA00305@chiota> To: hackers@freebsd.org Cc: shigio@ca2.so-net.or.jp Subject: ctags patch for global Date: Thu, 25 Apr 1996 10:13:55 +0900 From: Shigio Yamaguchi Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello this is Yamaguchi. I modified ctags for a new command GLOBAL. Following kit include a patch for ctags. Modified point is o -r option locate function references instead of function definitions. o -D option allow duplicate entries. o -e option force a function to end when a '}' appear at the first column. The detail is described as comment. Thank you. ............................................................. Global is a command which find the locations of specified function in C source files. It's for FreeBSD2.1R or 2.0.5R. Features o Global can find the locations of specified function quickly. o Global can locate not only function definitions but also function references. o Global can treat a source tree containing subdirectories and you can get relative path of objects from anywhere within the tree. o Global allow duplicate entries. o Global can understand perl's regular expression. I think these features are useful for a large project containing many subdirectories, many '#ifdef' and many main() functions like MH. Shigio Yamaguchi (shigio@ca2.so-net.or.jp) ------------------ C U T H E R E ------------------------ begin 644 global-1.0.tar.gz M'XL(`````````^P\_7?:R*[[J_U7*($62,!`OGH7-MTE0%+.)I`'I-V^)-L: M8\`WCLVQ33Y>F_>W/TDSQH:D[?;&S7U[;GS:8,^'1M)H)(VL\=AV![I=*&NE MXD\_ZH*MTJOM;?@)`,I;6PN_\BH![)0W=W8V-\H;6UA;WGRU\Q-L_S",8M?, M#W0/X"=_8HTM]VOM3,]_"H2>]AI'\R]N?X`8_.7YW]PI4T,H;^QLO7J>_Z>X M[L^_^-'*R8U1+I5VEN8]/O^O7KW:YOE_5=XIE7=H_6]MT/HO)8?"EZ__\/G7 MSE95_`]U=WKK6>-)`%DC!^6??]Z!'G,$WNN7^GAF3"P-:K8-W,@'ST1^7)E# M30TA=,VAY0>>-9@%ENN`[@P!>0:6`[X[\PR32P:6HWNW,'*]2S\/UU8P`=?C M7W<6,)A+=VB-+$,G('G0/1.FIG=I!8$YA*GG7EE#O`DF>H!_3`1DV^ZUY8S! M<)VA19U\!D,=+\V@P@]E;0D[']Q1B);A#K$IB@'2%.B(+L'5!^X554FF,!2\ M'#>P##./32P?;`1(<**1F<1%M'!4P]:M2]-C3L'&?51PR!A;0E20UN$,T?M! MV(`@-`0U=(W9I>D$>CAW19P6%QMX<*D'IF?IMA^QG^>-(,<)$?1M"BG1AU>F M%U@^#1H!H!&P)16.3#V8H1#1]).8(.9,AN^.@FNDT MGJ-?2NQP'F8HIQ[R/:IB2=*=6^1[`5DON.%Z_AQ_1'M@$HDX%RZ8SA`K3:(: MD;QT`S-$UD?!>_3>M M'O0Z^_UWM6X3\/ZXVWG;:C0;L/<>*YM0.^F_Z72AUFY`O=/N=UM[)_U.MP'EKM^N%)H]4^ MR`."@7:G#X>MHU8?F_4[>1J/(=WO"IU].&IVZV_PL;;7.FSUWS-*^ZU^F\;; M)Q3AN-;MM^HGA[4N')]TCSL]`8XH:[1Z]<-:ZZC9T`#1P*&A^;;9[D/O3>WP M,$XI_EL@=*^).-;V#@4L'@@);;2ZS7J?*(KNZL@W1.\P#[WC9KU%-\T_FDA+ MK?L^+^'VFO]U@HVPDL$U:D>U`R0O^PW.X*S43[K-(\(86=$[V>OU6_V3?A,. M.IU&CV'A`+UF]VVKWNQ5X;#38Z:=])IY'*5?8P00#'(,J_%^[Z378MZUVOUF MMWMRW&]UVCF&]*;S#IF#^-:P>X,9W6DSV\#SDX=V;)I9WB:W, MN1JQHX<MU:,&+3'T MN]I[0>8)LX!F#+$3MS$9SO.\0FL?:HVW+4)?-D9QZ+6DZ'3V&53OI/Y&3H%< M$8TAU*8V;)3S;..P(("#P\Y>[1#*JM;Q8:_7@"U5ZTV@73M"D6A?@G"(\)8, MD.4(PV.[PD0)2R+6(ZW=F6.P"D7U6@\MS,BR35]CH+WW[65*K"PR^"X$(BJ&C^O=0!X,>-L)'MB58 M9J%MUE'K>J:!NNQ6%$YT5$BS05AJF6Q@U.5!WKLS(.AC4S#*,VU$$\W75"=C M/P)W\$^3U!VK.=2Q;R-"AR:R1%H\U+V` MAL:-:CUSA.`=0V*KD_&`X6QJ6PS.)(V-=8'K(G^.IVK+(=NE8P?"=<8&C'6Q MX5Y>(H0\W"*!;)7,&].8!3A9?W@P#O2QCR(DW1+/=8,8_Z3YB#%:#-9?L&?N M5)IM9(=^I5NV/K!-M&I[-A00/!2NK2&RL(&VI16PQ*A?D,<'J-=@[Y98I<_L M("_E.&RFQEBHA[%B'@W[MH*=R%4DH^5@/RHXV[]#]6H\81U6M:3,VS?;;5K?3 M)N6]-*6F6`:V]2,AC/Q<*78Q`(V]XUK_S1((1$5`$2(]U`-]H/N$ M*?IZ&K!_=:7;,Y.&L<;H"YE#%=>P$R%%-;1.F;N\12`F_5%#2XFSI@*\`'0& M"_MX=Z1?F,1DQ?>,HF);@Z+"]3RXN&.FH!]E.?A,S>A6,^*5A9NPGGY@X2J7 M8IUD@ZSNC0W:7(ROV?O&T.7R)E/B3@E*=(4H;&[DJ@_UV]C8EOV6>^)E MC2`;`BCEX#64!%KWJ?BY].#H*"NX1+(147,0+\`8$N'?3:2F%?]5.N=='TOJ M%W#X$K7"8+=J!^T.^FWU7MQXX<)!:\=;)EVN'%R49<('%9[I>;33,HR9APLI M#R6QZ[JV?%-Z#$WT7`][G;B9@3P_#6A)NU/R7+"A<&][ZO*N!JGF$LW0-W[S MW8)C!IKK:?^64R2;JZ;4U"-B0=0[@3A0*HDH4"J*`:42B`"E2%0?%_]))1/]>30F M8>R'`242^4DE%_=AI+XGZI-Z9,PGE53$1V">2+R'07U'M(?674*1GE1"<9Y4 MDE&>5&(QGE22$9Y48O&=5$+1G522L9U4@I&=5%)QG=1B5`'M:.B?(Q3\+1>&C2B2P#T)'3V44 M5%6%'%I1A$T]:@EI;V3CGG$7RE6X6VIQ(UK&`(T4+,,(V".4. M3!L5ZE)3&I8J567F(+(^TLV$(=U<5Q3`AY:97:59J8!EV^88MR1S'+4S9S4G M8!@3G.ZL!)^#SY\AUC':*H?CTUYWY,Z<80@B0FS.UQ`F8I6+G@BUK\!G9MZ' M+GD\AWVGQH`O03-TAP"@8S/S'.!=AA,+34F8:=Y8L.';1=:Q%.7@5\B(8$@& M*B`F(E-E*?B-I!1V=\7N1[*5A5[`N^-6"[)\>GZ*Z^3/]/JOG[.Y3W=G9^L+PB5)+.2_W"I*@E6DX9DR-#*TN9[?@81AVEU*[` M7/"8Y8SUXHS(];>">U2(V"'$AD!(;A,MERM_%M,KM)J0<)",CK%P8<9X(,\K!9,R/@K9UIQ9=YG)4/3AYZHJ1L32/,@ M6>[-G/@"``3!31&SC)A^FBC<;,^F,+6F)H4!L2AM.=,9D9H934HE%*6TB"/* MDG*F&DVP:#JR;%29Q5^ATPHP9DOPH@PEK2$*"MC&4$T[:%/$3&?^J!H&B),>O,N`A%28,8VQ]IH8!A>?%`-L@+ZUDQ63 MBU(8\G)9$X5\E1J)(I]2^XC^84PY&FP9`HE2V)WZR.YRY?XB,'C-?,FF`^*0 M7!^XY`1QH<"E/X!0"U*]X#C40=@+.>=%ER79L%W?E-1A@7P40 MW3.]"],V;W,0.M'J4:U=W@T=[;*J#DRR$9:#S+/M"OIVX@X*!A1<2'_::[4[ M[]IW4!B+AX/N,3YC3J-Y!V>JPD[M)PUW1K@%NXLBCUC8:/;Z7,@]8M6J MJH4>PR\#?ZCA=GJL75Z\_KLNP'_S%5__9)A^1!;P=^1_;I1*M/XWMDN;S_F? M3W'=FW_^FV3VYS?U__;61BG,_RR7-RC^O_EJ9_-9_S_%]9S_^9S_F=1;@.?\ MS^?\S^?\S^?\S[];_B<%-K^2_LFI2)3]:5#"I"G:YV6>&*>(/9#:*3J)S$Z3 M;VH>B!C2P]F=W($"2?X#`_B M^/J5*+8<$7^BL)GE4'Z?/I8YG$`YG#YJ&GL8)CDNY$!"/,OQ2[F-K1%E2GIA M11351CAD8M#$Z4.1RHE*&>T86K`+$^J-;N)))\-F0Y+_?9.#M1%B29#C.[!+=BZ-Z;9.E9F(VL9N1!F^2T1Z1$_4==7]C_^9,$ MQ^#]7^F+^[^MS>TH_ZM?4K^?4K^?4K^?4K^?4 MK^?4K[]/ZI?T5N*97['4+W2]=S^:QL2%=`G$:^M,F*^5^4A)!.&6AC<9G,&R MNYB])?9LYZN\T(1?2V_?\=&DWUW5H-,Q:72C';5@YA11:E9EFE95-7W=0-^; M'5:NC/=87&9'*R@K0`K+4N>OY$^=A65 MNTKDB80?^U;XRFN:@?\G;!ZE$TVV6^%#A1KN76ZGJ'"AP"!7U[13`RF'@GAY M_ED>?^"-VTB,H`A:)`KX+(;/*<9&/4K3X/FD>M[V0.D_SK'_B]<]_S_Y MU__??O]/[_SF_O\.^_^;I6?__RFN[WO_+]X-_JC7_U*7?^'M/\?W_T]Q/3#_\E2O* M_]KB^,^KG>?O/SW)55Q38>T181_@_@D$?A!*`I$?A#(/_>#]XV,_".31P1^$ MD4CTY_&XA.$?`2F1^`^"2BP`)-#ZG@@0K#TR!(1#)A0#DL@G$@02L+XC"B26 M84)Q((243"`(`248"2*T$@H%(:@$8T$(+:E@$()*)AJ$@!(,!R&TY.)!1&,R M`2&$M!`1XE6@S/V7!X-"W*:HIN;["#\86JXV>;U89%N#Y3(/-=!BF4'QDJ5F MMWZ12OW%XN$2M)'A!/923VOLZ%RF&A-R20#6AH/PBSOAP935*I8KQ;7YIWCF M'VAAO864S3O3YH@*JXHB^\2#70M-AP-NR`7*8#8ZW3O9[[7^>[U\7E75*]<: MJG0,P\^)!FM^5?VD*B,."XVRR"W3\_*P^L*OP`O_S%GE#P.-Q?$5GPX\\2F) M,I^G$.`XQ,:?0%D&HRI*&(![X<-IH7Y^6O@=+LQ;_!W@?P,,W9B8OO4_)C[9 M^'\*4_$DJ#@G!!!*B,+R^"EQ%`Q0^:`X9:V2! M%2HD7F/U^OIY=-+,($PRD!$E7+0BD5U?1XCRH*0B$5E?QPGFR9TY`4CD<'*I M!1DHRYF9%&&C4V<*3RYB@@/2J:NS($-5\F10-#B6RT'"8W&+"##PZK?@,0#N M48V!$A@6"@+(8G_(W`=J,$156>0[%LA6YZ($9Y:^[1/_M`_EM2CT+`5[C4I/ MSWDBQ1R)]1!.V1I*&=XW]A1<$'BSU^\VFZWV?H>39>1D\[P2I[`QCNS1AYEN ML@RY=)Z'3#'#[`FE#YM0PW4ZOZ@05Q;K9#^&B6-H%.0D$KL?&B?'8EZ_],DR MFF+N,U\/V&^[1%=5UESJ-SCX5!Q*CDHMYX'2J80P+^"T%8^*VB>'A_-F'JZ> MFZ5"V_6&?)8,%7/_L/FAB;:TUB:BY)RSK(_-P)T&L0E"E5'_O3(P*O:TLHI2 MO;(+S*\U@/7R@HL<@_ULQ\::HE#]WM-8[VFWQQ)6@'N M(G6J7"ZX'A2A$.E(+YTV1Z;\0GPWZ&0O"YXH/8<*S`U-E7J1MAKPJ3P!(3^W M'*0Q]X M.>7A)9&6"U<1#2:$*79"6PP.(QV%9ZB%I[+G(B%P$6=XPZE7>*W418;>W":R M&AP.1.(>CL7,"9DWERG1]W?S%IUQW]0]'$1V1$G#7GE:P@M=0[:+GCWZ<)%:BP?-W@S5,&AX6/G]A#]JW^4I.+##J1,PPHV^U(ELKHKKJD*^?+AF5Q3 MGEVM49FH@O1`;-Y8_V?) MQM!VB@RD!K&.\F!HZ$]QZQ`P`XQ_7W"AMCW#N>,F!(#U+;\5XZF4&FR$VLLG MCX#\>O*-T.*CX^C(^6,['G@V+AGR&@IE896$?/#7):A8R`:]LPN-?Q76#'CY M$E9P(T?Y;MDU(U<%]`=RU-&_L*9L/I`+@;3I5>DEK!G285%"Z2$"N&%T_IP% M2#H5!1H/7L^G/^I)(P2N"[:+#J[H@K0XQO0V*R0C#_Q'PL@)N\1O)*FK\(P% M>E*29$MIFB7)(:WW29W3NN"]_`5*Z4.#.'D2ZG2@6#6%B]Y`;[$KGDH"79*U24Z MQ$Q:M]G_@%L8W.OU*O>-`=7BGJ[3K2RT%WO22L0/,7AE06THD=,K[8$B/@(A M%8DJ(G^LXRH+RD]NHRQZ$RUO?&RDT+V'DU6J4$#D4K>I0%'*E4C@>&LE5%2H M.JEKI*7D_H$=+:&Q%&:3\+S^K[UG[6[B6/*S]"L:6(XD:S32:"3Y%9,+&&PCKC*41UB(D19(QON#_OO7JU\Q(M@,ANUGU2?#,J+NZN[JZNKJJ MN\KE5F5W`+E`P>@1=!X-HC$[(EN(E47Z6WY(7I[`%OSX^4LA="YPX`X%S4BH MH?]^5M6MD)[L>\.^KI*?GOS\2KA#%3<5-6>C,\6+[G=EKZ2)3IA]B1<)OV%$ M!35WH8!:O?$6#Q_9T<5E:,]?H;+C>_,QU6M:9M%9/82W&).CIR^/7ZT>DC\> M[U^.]#];E_][4H']YZN?`+C._A]Y]A^R_W=[[8W]YUND&]K_7[Q\_L.!UJQM MC/!_G;3&_OO5[H!?Y_\UZL1R_QNF?:^%O_8V_C^^3=K<_][<_][<_][<_][< M_][<__[_% M^3;X8_WP=[P2#EM7_7ZJ'_KX0S]9L*5!?S6!@N@J^B25ZWO< MB]'[V3A%]WESB1<#BXZ]PZOBLNY9Z)5'!4(_HUW']84N`U1A7WR.O#T9(VYQN.9R^.-RIH\F'(X9+#$0D&+J ME).VM.F%_3#F'`G7[R)QX M??MF-VN;I6GO>(.'O@H5J3#Y(`=$WOWLX:ORJRE3JAG$P)N&1`TT?$2@I,4/ M)6X/&C7T8D]9))2.$3I"#%^#U@:=R)KQRV3EU]#\3[?SF?92C#?2F`Z'BW3I M1/8IW\S^X1M`=+EB\P?^NLKX@;^M,'V8R$8Z:,_C[+2@J"[VXDV9K$X1:@*3 MB%_:]-+V7AKR&M-K#"__=8B0RN5C?[KZ%0@,I1R(,;_%_F^Z@HC?(P;^%!E2 M.BB`K/AL2;L8BE/C_?)M_3Q0#>7"8SJK/358=OWU?#4(8T?7#.R.P5^6A'`P M/!&JUE%+;(7SH;U^UCNOTOVJ[8^)_][91_Q/W MNM%&__,MDJ__Q:$O[821JP/N-7O-W;A^'_Y)LD$%X%TCU.YI.Z93WB)_.8IE_V> M!:SAZ[I69K^G'^_Q'SG%K8!&37X!ENR+OA[A>#=8G['5V4W'S&[1MD] MW:9L7\VS_H+'1HY`>#L"B>K1\6$;>"V\M<-6V,6?K!H^IYU4WS&)_@TDK-"5 ML!Z4Z21MR9YQ+Y=_T*[B<`=C-L_B,2T30GAE$.-R00SA'^;;>PZ[E3EP)6C(FC"X6.PIJHDGY"X-#PUJJ1UWCL"NAN=CH500E_H@'7-\2A(+ON>_2>TIHUN MW.@2.+L41*C2ITF:#A9J<0;4&,"V'C;Y2O<-?1E"+T0+43`G0@<..2"<+,3. M89PA!NQLD9YD3X-T3U4DR_X9QHF1#`0-=_K>#PCX?`;-4;2#6XY.QZDV3<&$ MF^"P4#XD.XR"K:,BXVD990(Y-2CLL6H<\M@D-1A(V`^^8U7^N]&2/I_6)%3- M>$SOI?OT3H\F]`GAD7[NU[BMW`*8Z/%-9AH&UCC,JZN<1&852I9JGT76,5 M0E25'2.*TY1RZ3/\UT#;0]2$)Z4^\[\-XKX/PWXIQ*1*V2.W=Z0859D:(4O$GA:V^(N@K0%.OVTUR M"O&9_^5*'H=]M;H6G#90#W,J]3/64"HIKKB-%8_J]7UUI3_?PQL8I8)"-B+=_(L7%%I+B!:RZPGYN.1%I7!-02`Y-ZOX MD>8^10)73IQE:A]^(5+28T6D*$U'IB#&FY+`I@P M;.*P%D/B'YWFK038IJX"@V5>*T+"HGCY]RIK\-1N9^M[*/4)!2`V&(:87R6/ M-WAHIKYF02X>C0K6\CIJQ&\JV3&1]W932)T[^E%W='$&(@-KX&')'HMN?3%Z M/\+:=3"I"H:3RG3<]-J#KOQ0YR83/7B2N&I[)4N9";6B4&=5(9I?'C936$/% MMS'KI8F+YB5%YJ@@"9*L@6NI[NF'D?K5I:E?:40-7,1NN=P-U<,9B%SI0+-Q MMQ&TZ+T_'R]':!2S'I`M\U[#O4O%W-M>.LWS?N=":JZPPUR!V66@M==`:Q=` M<[DH0J,%?(H$FZ#]+]`BKK]\XSI+_0[<7M"B[+2#EO&'VE\R`D*!\R(9O\,A M!&9BR]KU,-!D)P*^D2%)A$))WRL8JG^N!PX-R8#4)"G;#A\D"I.*75*S[5$Z MBH(F?D.ARD2"1$A%,3!QPN'O*_M"1WFFP+AL1T@4]/"G''F'!^85,7K7.]/>\:"RV!*6/*L63"3WK_#T*=-Z&>3_:%=M[-MXH`?4X.+@@C`V-A,:%8 MZ,W]QE[C\N4=#E$NOSI+0'##`1_RP,\);8@*+=NED_^>@O3V9^MEOE5R]']V M7_"5ZUBO_XL[6O^'^O]N3/Z?.MWMC?[O6R0<;G+;-E^Q@VRB`![BO^6MK:TU MF4I'\Y%ZEERJ]K9J1WMQM-=JX1&;3AG$8(90.CZ?X/D;^%U%O;THWNO&?`IG MRT]4U4XOV(T4O2($>(VBMJ+KA23UX[T4>L";&XW&&(_VP3:W5>.O)?Y`-]#J M2G8(['R_KNAB'O_%*X`I^?1$IK`Z,("$!)C-TF1N2B8F+@"O+QH2ZJ^,,!.P M4=6L>*;P$`^XX/>'(()>4+R%4]2=+9:ASF0RZVR?S!?ITD/]@?"0.#E*N&^R MV>GVN9L7&KDN.VZ"S&]7Y@?SU.0'A$2N//'6%/1H/*Z.)L,:7J+!<*;TI1Z9 M>OQA(;<$=5T9C=O;*6-].7V'\;?I(U_5_652V2NDE"C>#J).EVD%\S?Y#[06 M6G>1JC.,>I&8\,<`.IT$>(40WO"\#,H+N@2W[]_I?(I',T:\T[`T$4J^IM.P M*K3KCL;%'08`R*!J.(!WB:YT+TO0`D2*Z1@76P(E9C4O]@/9>XX@+"Z%78#%_K44(1GK[D6[7-- M@]D!P")$^RN'B')0G93E5@-62(_=3A#U8LN[HIU.T(Y:#O/2@!7/DLETWP&/ M:#E!_?!EM6;IIU2O4[N+V1E=HM6!L!?G\S0T,U0Z/5K@]38Z*UW%IM3YL;"-TMMTB071X4%]!48MO%SG^2*RC@JNT;$&"W6W]ZL9UV*)T64,N32W MB@ED-PZBW1U+(.U.*VCWG-4-)I&^8@$KPWRP\/F.\?M@!N#1/WXX>OIS;FG# MP#YD_["J2G?JV[6%A3'TSN&N,:&[)!1Q?NVL!MTR>[YCS`ASR"%RQ\'?Y$;] M#T]>/:[>.0C8YP<,QPI89ES<\:2?L:#^D6]BZBQ\\?-\@B'5J_T`SQY:,L'; MP]"DPE'DX=O31#,A@JWVG5DHU'D@U"DS1^BB:*SC*`KBJ&?'.M[N!O'.KAEK MN1,]$V\!I^=#X(5J-L5SQ7,9<,H#%;Y^]O#G5\___N2G-WP)']N+>T4I1)F+ M:((IHI@>WB?]^324W]G<29^8%B1I0I#!_UUC2!A?-31V#`HY(]\D1A:`M5+W2OHRK/\5+=B%Z?*GM,`XX0DA76;>XKG3NW-2O>`V3` M.)!^^<4%928U$8"E\N,GKWY\^M.3?8^"K?,S'^)$0_1+6>+FANQ99O^`>+VI M+2>*:$S_ZXGY9(;!:Y+=@I6F1'L@`5&3""96>T4;!:C M<4DP[5=W]==+\KB MR'9&'"F21SR<'/@X\1A[#D&KB5-Y*,8U[C1]FZ\4(-;KKDR7GP$%DY`_,I?Q M6I"9"U343D=OI:&ML$+V-^<=DJ(%0FV5SI+)8(Q;4OCIO+\,U/D$=Y9H],#K M%I2Y?+VZ2Q^%5:%Y7*?X,IX3KM%^F7RW4H&U`V=-;`<[>CV$_]@C`Q_R4.KQ MT8^P]-4/&D]M0`5`F_E\R,%A&HKFR"#`B3^N0*UFNPZW.=BO4QKN! MU1@YT5T3&TL4?W`O\V&^]W(2YXZ2VWB/CI+!\OSBPT?\F3\-\?X2YM)`)(@I M6>(8IGM-C_8$U!H9W2]IS2$T)YU_68.*T-7;#K;;EA;QM6/:R[?"'L$CVLA/ MD_Z[BV2NW4FA=#1+\"X?&?O"%[^I'T?J>ZCZ>X5;"BE]"(_9(W)R((+N68>V MHB.I"`CVVGJ:4$^SL$<[D:]>CH-=,[_(O\!@.JG`QH).:\W?TO7X!^X,UX"SY,$)K&=Z' MFZH9PD;0[]>!89:ZES:(/.G9'Y*8P-8&(M1+2 MGKY:C9LE/,KDXJF%ILW+&8`;HA=?6CL6LGC`7[3=XOKATM]Y(3U%VW$0;>]J MEG*8H6(F"K0+T"'&`9TUH8M<"ST'S:TM>/T9;?443_<.O7P8J4BRT0TNI5ZF M_>E;1A"?B4-V8$W14)(UCZT@VMG6A/T'M,J\O)6@O[=LY4W7C+[A]&LM49+E M9FO&+2U2O5ZPW7688"_8:3M+,FT@6<`LV5T?$,\I;-#0-8>0*7TF5066(&V" M%&@,T/':I$'Z`]G&%JL1L&3JEDSW<).&,Z*E35)LSC(3"AD+@]+"%.UG72#+ MO95SPS;X@UOBPY[Z\!:=(,/4N203_@`H9'J^1%>AILB%6^1BCV+/X<$I!?P; M#R([T#^Z63]">SX"GQ#@%FPA/@[=HH=[A2>N+P6=F'_NYI_O%7"F#+Z0=;!7 MU/,Y\B)QO"W#.K+N4;6#=SSF664X1Y+*8[C9T(U[I#5 M3:``D.%>(0BCE&)=!L#0ZEO>?3V"W1?I;=UQ^;XB1@VS='\AA4N=87+HHX5HBR.`$,M8PE&DE$-:N<(';V+ M!O<.N\'^1((DQAHH\!5)P0C('JCC$?`M@-<-(_*_@9>A$9O>\-R'.7U7M*#& M`RLI/N_0E$.9AK6D1JV-V4X^)&-R:YK.2"_&3^RO>U_5Z_CJ6H>-\/T5NI@W MJ.9ZC%-VOK;/OTRPUYZI]=9XLS`,(611F&VK5:93GXW.J@_07SU9S^%#^XVQ=TG(@R(M>ZF4;74I M'Q/$'MJ&A6/T=C*=\X%S5#'PN%?_R3(`"^I,`KYAE;U'[_LVN(Q]1_EFP$)\ M=..@W76-KKO=(&YUG"'3XX-Z)M)WP)IF]6(659<95'U=W%#%-\2-'`U!T]U% MJKW7DR$*-T;Q?,".LO':CH5KBB!F'[NGYW'?!XT1KV47<_0(7HS,'B"SYR`S M;NT&<;3C(//R1*ZX::.0X%7T3!YJ!;=HONJS*,B]NMH-/N>G9'C&:`*.K[6!0- M:@X#:!&B:,XH12;CV5ERFHJD+%8FK>0^H>,$K]$W.ZES[^+O=^GHSMW!]/QT MG,K+<#Q-EOIYJK.,AOIAHG]$O_'RR(B0E\49M$@_C_Z=3G51ELODY7R"D8_2 M@;R2X$?/5_LBIX\3"IW#(*J9CM2:\ITDJZV:J-'1875=973[>-2G;BXK<`&V MYY792*@3'EN@OP)-)^)$(UXJ1K!.8,OV\4I$S2MNP*#W^BSB1V^@X%:N-3I9 M<>BFT!ZL@6;ZZJCAB^!J;^=Y\($$C!D$.QZD@A6BJ*[O6R^CE`O:(^51MI9,/]HT]2[UNXQY)[!'8^]FE MB79R-^2)3[.]BD?,:0\"#]6[-D(Y;#N,C91JF;%?^O[9',L$JK*G[?@(9R:L M*5-7O3Z33-8XF,D"P&K6,((_)DO;UB8Q@;N:\/TX0FQ@71DF2/^6#11DOF=" M!>GO3K`@`]Z$"W+SZ6A!SC<3"J>E6UP4<,:$D%&MHN`Q,C8/@!8:%DHM[GU/HF"O6!7Z>BVA_^!XKR44W\']: M$>;``Y'QAP\46AQ_`HDF%X`"9T,N`@7B1:)$1!CF@]850-1BJ4\C9,)2Y'E" M;@PR?O.+!R`7W$+J1LVD6[_VN-_RALUA""(T9_EY4=2=-10C/K$H>PCYZ:&V MGG9$2KBI.O/,*"'/2"A8G_EFZLRS6ZHS\S8=HRA./Z(AA?R=$?/%+;\^]0)R MU)R60JWY$KT(TG9V M@MV6H[:,@]W=#*5A/5JP5B[%=>(6MT@BIS1 MY`\]N_,3GGKW_@)#>-X?4$!..KVLT&GY(&T\H+D1R`ORC0"OH^#+>#)5==6+ M:ZJI>AW>.9IMXD>]Q2L\5"F+I5-#33TX@"[51D;CT?(R8V'(-"+7AC58 M7-L&0>(-Z$P.>X3RL([*.,=U1":Y;DECK2!J]8P:E_C=:*CU=\@76=2&+8N' M"E@13MSQW],%[M`^5W@2088B:SJ_XLP4J1$O7-H[L\@ MJGA1TRJ3XJ6-;I@X&E^#9^\^S?]-G/_9]S*_52KP__G5Z[C6_V=O6]__[70[ M$=[_C5KQYO[OMTC'_WAT^/3E@;XFSX9<[1HX$^B)?35M0CUMTB9MTB9MTB9M JTB9MTB9MTB9MTB9MTB9MTB9MTB9MTB9MTB9MTB;];TW_`R!IS^,`\``` ` end ------------------ C U T H E R E ------------------------ -- Shigio Yamaguchi E-Mail: shigio@ca2.so-net.or.jp From owner-freebsd-hackers Wed Apr 24 18:50:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29066 for hackers-outgoing; Wed, 24 Apr 1996 18:50:42 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA29055 for ; Wed, 24 Apr 1996 18:50:37 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA31600; Thu, 25 Apr 1996 11:35:03 +1000 Date: Thu, 25 Apr 1996 11:35:03 +1000 From: Bruce Evans Message-Id: <199604250135.LAA31600@godzilla.zeta.org.au> To: bde@zeta.org.au, jraynard@dial.pipex.com Subject: Re: Flaws in system() implementation? Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> 5. Use of the crufty signal() and deprecated sigblock() and sigsetmask() >> instead of POSIX signal handling interfaces. It isn't clear whether the >> sa_mask and sa_flags used by signal() give the correct behaviour. >Yes, I thought about this but thought it best to try and avoid too >many changes to the original code. Good. >Actually I was thinking about a "project" that I can do on 2.1.0-R >code (I don't think I can afford the phone bills involved in running >-current) and trying to make things like signal-handling in libc more >Posix-compliant seems like a good one to start with. >Any objections and/or pitfalls if I do this? Keep up with -current enough to avoid re-doing things (unless you're just doing them for educational purposes). I just checked the NetBSD version and found that -current would already have your changes if it kept up with NetBSD :-). The NetBSD version also replaces execl() by execve(), presumably to save a few cycles. >> Some of these points also apply to popen/pclose, but the FreeBSD already >> seems to be correct although unnecessarily unportable. E.g., it handles >> EINTR. >Out of interest, why does handling EINTR make it unportable? I meant that handling EINTR helped make it correct. The old signal handling functions make it unportable. Bruce From owner-freebsd-hackers Wed Apr 24 19:56:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA06438 for hackers-outgoing; Wed, 24 Apr 1996 19:56:16 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA06403 for ; Wed, 24 Apr 1996 19:56:03 -0700 (PDT) Received: (from scanner@localhost) by orion.webspan.net (8.6.12/8.6.12) id WAA12947; Wed, 24 Apr 1996 22:55:47 -0400 Date: Wed, 24 Apr 1996 22:55:47 -0400 (EDT) From: Scanner SOD To: freebsd-hackers@freebsd.org Subject: IPv6 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was just curious what if any the status is on incorporating IPv6 into FreeBSD. I know this has been debated recently on the NetBSD groups and wondered what discussion of it was taking place on the FreeBSd table? ===================================| Webspan Inc., ISP Division. FreeBSD 2.1.0 is available now! | Phone: 908-367-8030 ext. 126 -----------------------------------| 500 West Kennedy Blvd., Lakewood, NJ-94945 Turning PCs into Workstations | E-Mail: scanner@webspan.net ===================================| SysAdmin / Network Engineer / Consultant From owner-freebsd-hackers Wed Apr 24 20:39:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA09445 for hackers-outgoing; Wed, 24 Apr 1996 20:39:39 -0700 (PDT) Received: from geneva.visi.net (root@ns2.visi.net [204.71.248.4]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA09438 for ; Wed, 24 Apr 1996 20:39:31 -0700 (PDT) Received: from mb1.nhr.com (ppp-nhr-1-20.nhr.com [206.151.14.152]) by geneva.visi.net (8.7.1/8.7.1) with SMTP id XAA27912 for ; Wed, 24 Apr 1996 23:36:50 -0400 (EDT) Message-ID: <317EF3D8.6D67@nhr.com> Date: Wed, 24 Apr 1996 23:39:04 -0400 From: Mark Bernard X-Mailer: Mozilla 2.0 (Win95; I) MIME-Version: 1.0 To: hackers@Freebsd.org Subject: How do I setup up SMTP or using Eudora, ect... to access mail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@Freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have just installed Release 2.1 I would like to set up the systems to use the SMTP so I can set up users with Dos/Win boxes to access Mail without having to use telnet. Any help would be appreciated. Thanks. Mark From owner-freebsd-hackers Wed Apr 24 21:48:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA14711 for hackers-outgoing; Wed, 24 Apr 1996 21:48:11 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA14700 for ; Wed, 24 Apr 1996 21:48:07 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id OAA24000; Wed, 24 Apr 1996 14:44:14 -0700 (PDT) Message-Id: <199604242144.OAA24000@ref.tfs.com> Subject: Re: ps dies with FP exception. To: chuckr@Glue.umd.edu (Chuck Robey) Date: Wed, 24 Apr 1996 14:44:14 -0700 (PDT) From: "JULIAN Elischer" Cc: hackers@FreeBSD.org In-Reply-To: from "Chuck Robey" at Apr 23, 96 08:35:52 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > On Tue, 23 Apr 1996, Julian Elischer wrote: > > > anyone else getting this? > > under -current.. > > I will shortly recompile the kernel as well, but > > ps alx works > > ps aux dies > > > > julian > > (ps sources as of this morning)(but it did this last week already) > > I rebuilt my kernel last Saturday (the 20th) and both ps -alx and ps -aux > both work for me. Also rebuilt world at the same time, tho. > > > > a new kernel and ps fixed it yesterday.... julian From owner-freebsd-hackers Wed Apr 24 21:48:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA14710 for hackers-outgoing; Wed, 24 Apr 1996 21:48:11 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA14703 for ; Wed, 24 Apr 1996 21:48:08 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id OAA23932; Wed, 24 Apr 1996 14:22:52 -0700 (PDT) Message-Id: <199604242122.OAA23932@ref.tfs.com> Subject: Re: Character device major numbers. To: dchapes@zeus.leitch.com (Dave Chapeskie) Date: Wed, 24 Apr 1996 14:22:52 -0700 (PDT) From: "JULIAN Elischer" Cc: FreeBSD-hackers@FreeBSD.org In-Reply-To: <199604241631.MAA06404@ale.zeus.leitch.com> from "Dave Chapeskie" at Apr 24, 96 12:31:19 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk If you are using -current, things are differnt to -stable.. however You could safely assign yourself numbers after the end of those asssigned. Probably extending the array to past 128, and using 128,129,130 would be a good idea.. alternatively, you could use the 'dynamic' numbers assigned to LKMs. Under -current all Major numbers are dynamic in theory, though we have not yet the infrastructure to do that in practice.. > > Hello all, I have a problem I hope someone can help me with. > > The company I work for is using FreeBSD a new product. We've written > three device drivers to support some custom cards that the product needs > to use. The problem is that there is only one reserved cdev major > number. > > IMHO, It doesn't make sense for my company to go through the effort > of making the drivers loadable to sidestep the major number issue since > the product is a complete system and we provide a prebuilt kernel and the > drivers will be in constant use while the system is in use. > > It also doesn't make sense to request that multiple cdev major > numbers be reserved just for these Leitch drivers since the cards are not > widely available (two of the three will not be sold outside of this > system at all). > > What I'd like to recommend is that several additional major numbers > be reserved for local use. For example having eight reserved major > numbers for use within any one organization should be sufficient for any > current organizations and yet should not impact the size of the cdev/bdev > switch tables very much. > > What do you think? Is there a better solution? > > -- > Dave Chapeskie > Leitch Technology International Inc. > Email: dchapes@zeus.leitch.com > From owner-freebsd-hackers Wed Apr 24 22:00:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA15295 for hackers-outgoing; Wed, 24 Apr 1996 22:00:17 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA15173 Wed, 24 Apr 1996 21:59:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id OAA06594; Thu, 25 Apr 1996 14:46:19 +1000 Date: Thu, 25 Apr 1996 14:46:19 +1000 From: Bruce Evans Message-Id: <199604250446.OAA06594@godzilla.zeta.org.au> To: ck@toplink.net, hackers@freebsd.org, isp@freebsd.org Subject: Re: Going gaga over Cyclades board Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >we've been trying to wire up a cyclades 1400 based pccom 8 /port serial >adapter under FreeBSD 2.1r. Which model number exactly? Old 8Yo boards have problems on some PCI systems (the BIOS messes up their registers; Cyclades has hardware fixes for this in newer models). Some (all?) PCI boards are not supported by FreeBSD (the registers are mapped in a different way...). >The problem is that using 'kermit -l /dev/cuac0' just hangs. No echo >no nothing. Trying to exit kermit will leave it hanging around forever. This may be a configuration problem. Try using `cu -l /dev/cuac0'. Use `pstat -t' to look at the state of serial ports. Bruce From owner-freebsd-hackers Wed Apr 24 22:10:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA15898 for hackers-outgoing; Wed, 24 Apr 1996 22:10:38 -0700 (PDT) Received: from ns2.harborcom.net (root@[206.158.4.4]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA15893 for ; Wed, 24 Apr 1996 22:10:36 -0700 (PDT) Received: from bunghole.harborcom.net (bunghole.harborcom.net [206.158.7.243]) by ns2.harborcom.net (8.7.4/8.6.12) with SMTP id BAA18197 for ; Thu, 25 Apr 1996 01:10:33 -0400 (EDT) Message-Id: <199604250510.BAA18197@ns2.harborcom.net> Comments: Authenticated sender is From: "Bradley Dunn (Harbor)" To: hackers@freebsd.org Date: Thu, 25 Apr 1996 01:09:26 -0500 Subject: multiple ifconfig lo0 in /etc/netstart Reply-to: dunn@harborcom.net Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi everyone! I'm running 2.1R so feel free to flame me if this has already been addressed in -current or -stable. :) Many of us, I am sure, are using multiple ifconfigs on lo0 so as to set up virtual domains. Has there been any thought about just having a list in /etc/sysconfig that lists the virtual interfaces desired and have /etc/netstart read them into the ifconfig commands? I just thought this would be an idea since netstart says something in it about the fact that nothing should have to be altered in it. Bradley Dunn Harbor Communications dunn@harborcom.net http://www.harborcom.net/ -------->>>>>>>>>>>>>>>Faster than a speeding bullet!!! From owner-freebsd-hackers Wed Apr 24 22:29:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA16861 for hackers-outgoing; Wed, 24 Apr 1996 22:29:25 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA16856 for ; Wed, 24 Apr 1996 22:29:23 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id AAA20285; Thu, 25 Apr 1996 00:23:29 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB323D.E0E7C4A0@webster.unety.net>; Thu, 25 Apr 1996 00:26:43 -0500 Message-ID: <01BB323D.E0E7C4A0@webster.unety.net> From: Jim Fleming To: "freebsd-hackers@FreeBSD.org" , "'Scanner SOD'" Subject: RE: IPv6 Date: Thu, 25 Apr 1996 00:26:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 5:55 PM, Scanner = SOD[SMTP:scanner@webspan.net] wrote: @ @I was just curious what if any the status is on incorporating IPv6 into = @FreeBSD. I know this has been debated recently on the NetBSD groups and = @wondered what discussion of it was taking place on the FreeBSd table? @ One reference = is.... This will lead you to... Ipsilon Networks is implementing an IPv6 router based on FreeBSD. It = will include OSPFv6, flow-id support, and multicast routing. The source = code for this implementation will be freely available for = non-commercial/operational usage.=20 Contact Peter Grehan at grehan@ipsilon.com for additional information. @@@@@@@ -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-hackers Wed Apr 24 22:51:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA17709 for hackers-outgoing; Wed, 24 Apr 1996 22:51:33 -0700 (PDT) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA17690 for ; Wed, 24 Apr 1996 22:51:28 -0700 (PDT) Received: from sax.sax.de by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA13329; Thu, 25 Apr 1996 07:50:50 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id HAA03311; Thu, 25 Apr 1996 07:50:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA00972; Thu, 25 Apr 1996 07:12:39 +0200 (MET DST) From: J Wunsch Message-Id: <199604250512.HAA00972@uriah.heep.sax.de> Subject: Re: How do I setup up SMTP or using Eudora, ect... to access mail To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 25 Apr 1996 07:12:38 +0200 (MET DST) Cc: surfmwb@nhr.com (Mark Bernard) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <317EF3D8.6D67@nhr.com> from "Mark Bernard" at Apr 24, 96 11:39:04 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Mark Bernard wrote: > I would like to set up the systems to use the SMTP so I can set up users > with Dos/Win boxes to access Mail without having to use telnet. An SMTP server (sendmail) is part of the base system, but you might have to adapt /etc/sendmail.cf to your needs (or re-create it from the source files). You certainly want to install a pop3 server, there's one in the ports collection. (Please direct requests of this kind to freebsd-questions@freebsd.org.) -- 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 Apr 24 22:51:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA17730 for hackers-outgoing; Wed, 24 Apr 1996 22:51:38 -0700 (PDT) Received: from irz201.inf.tu-dresden.de (irz201.inf.tu-dresden.de [141.76.1.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA17691 for ; Wed, 24 Apr 1996 22:51:28 -0700 (PDT) Received: from sax.sax.de by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA24437; Thu, 25 Apr 1996 07:50:52 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id HAA03314; Thu, 25 Apr 1996 07:50:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA01005; Thu, 25 Apr 1996 07:16:32 +0200 (MET DST) From: J Wunsch Message-Id: <199604250516.HAA01005@uriah.heep.sax.de> Subject: Re: Character device major numbers. To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 25 Apr 1996 07:16:31 +0200 (MET DST) Cc: dchapes@zeus.leitch.com (Dave Chapeskie) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604242253.SAA07460@ale.zeus.leitch.com> from "Dave Chapeskie" at Apr 24, 96 06:53:31 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Dave Chapeskie wrote: > With changes like this taking place is there anyplace that documents > the correct way to install a new device driver into the system. For > example for the dev_attach stuff I had to hunt through kernel source to > find examples. It would be nice to have all the defvs and device > registration routines documented somewhere. The devfs functions (well, the publically interesting ones) are covered by section 9 of the manual (the kernel 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 Thu Apr 25 05:05:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA04427 for hackers-outgoing; Thu, 25 Apr 1996 05:05:21 -0700 (PDT) Received: from toplink1.toplink.net (toplink1.toplink.net [194.163.120.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA04410 Thu, 25 Apr 1996 05:05:14 -0700 (PDT) Received: (from ck@localhost) by toplink1.toplink.net (8.6.9/8.6.9) id OAA01652; Thu, 25 Apr 1996 14:04:25 +0200 From: Christian Kratzer Message-Id: <199604251204.OAA01652@toplink1.toplink.net> Subject: Re: Going gaga over Cyclades board To: bde@zeta.org.au (Bruce Evans) Date: Thu, 25 Apr 1996 14:04:24 +0200 (MET DST) Cc: hackers@freebsd.org, isp@freebsd.org In-Reply-To: <199604250446.OAA06594@godzilla.zeta.org.au> from "Bruce Evans" at Apr 25, 96 02:46:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi > >we've been trying to wire up a cyclades 1400 based pccom 8 /port serial > >adapter under FreeBSD 2.1r. > > Which model number exactly? Old 8Yo boards have problems on some PCI > systems (the BIOS messes up their registers; Cyclades has hardware fixes > for this in newer models). Some (all?) PCI boards are not supported by > FreeBSD (the registers are mapped in a different way...). It's not a genuine cyclom board. The board is an ISA 8 port (2 x CD1400, DB25 connectors) from a manufacturer called PCCom. The PC in question has an asus pentium/tri motherboard. Do you think I should try sticking the serial card into a plain ISA Mainboard ? > > >The problem is that using 'kermit -l /dev/cuac0' just hangs. No echo > >no nothing. Trying to exit kermit will leave it hanging around forever. > > This may be a configuration problem. Try using `cu -l /dev/cuac0'. Use > `pstat -t' to look at the state of serial ports. Thanks for the tip. This is what pstat gets when I cu to the ports cuac0 has a modem connected to it cuac1 does not (dangling cable). I have had the card at irq 12 and irq 15 and at d8000,da000,dc000 all with the same effect. Characters end up in the output queue but don't get sent out. 16 cy lines LINE RAW CAN OUT HWT LWT COL STATE SESS PGID DISC cuac0 0 0 14 1296 256 16 OCcB 0 0 term cuac1 0 0 7 1296 256 9 OCcB 0 0 term ttyc2 0 0 0 1296 256 0 l 0 0 term ttyc3 0 0 0 1296 256 0 l 0 0 term ttyc4 0 0 0 1296 256 0 l 0 0 term ttyc5 0 0 0 1296 256 0 l 0 0 term ttyc6 0 0 0 1296 256 0 l 0 0 term ttyc7 0 0 0 1296 256 0 l 0 0 term I have tried turning on and off the Polling mode in /usr/src/sys/i386/isa/cy.c with no difference. I am beginng to suspect that this card needs some special wiring on the cable. Greetings and thanks for the tips (didn't know about pstat before ;-) ) Christian -- TopLink GbR, Internet Services info@toplink.net Christian Kratzer http://www.toplink.net/ Phone: +49 7452 87174 Fax: +49 7452 87175 FreeBSD spoken here! From owner-freebsd-hackers Thu Apr 25 05:26:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA05412 for hackers-outgoing; Thu, 25 Apr 1996 05:26:45 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA05395 Thu, 25 Apr 1996 05:26:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id FAA19162; Thu, 25 Apr 1996 05:25:34 -0700 (PDT) To: Christian Kratzer cc: bde@zeta.org.au (Bruce Evans), hackers@freebsd.org, isp@freebsd.org Subject: Re: Going gaga over Cyclades board In-reply-to: Your message of "Thu, 25 Apr 1996 14:04:24 +0200." <199604251204.OAA01652@toplink1.toplink.net> Date: Thu, 25 Apr 1996 05:25:34 -0700 Message-ID: <19160.830435134@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It's not a genuine cyclom board. The board is an ISA 8 port (2 x CD1400, > DB25 connectors) from a manufacturer called PCCom. The PC in question > has an asus pentium/tri motherboard. Do you think I should try sticking > the serial card into a plain ISA Mainboard ? That might be interesting. It might also be interesting to try swapping this with a genuine Cyclades product.. :-) Jordan From owner-freebsd-hackers Thu Apr 25 05:48:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA06590 for hackers-outgoing; Thu, 25 Apr 1996 05:48:52 -0700 (PDT) Received: from toplink1.toplink.net (toplink1.toplink.net [194.163.120.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA06583 for ; Thu, 25 Apr 1996 05:48:35 -0700 (PDT) Received: (from ck@localhost) by toplink1.toplink.net (8.6.9/8.6.9) id OAA03720; Thu, 25 Apr 1996 14:49:15 +0200 From: Christian Kratzer Message-Id: <199604251249.OAA03720@toplink1.toplink.net> Subject: Re: Going gaga over Cyclades board To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 25 Apr 1996 14:49:15 +0200 (MET DST) Cc: hackers@freebsd.org In-Reply-To: <19160.830435134@time.cdrom.com> from "Jordan K. Hubbard" at Apr 25, 96 05:25:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi > > It's not a genuine cyclom board. The board is an ISA 8 port (2 x CD1400, > > DB25 connectors) from a manufacturer called PCCom. The PC in question > > has an asus pentium/tri motherboard. Do you think I should try sticking > > the serial card into a plain ISA Mainboard ? > > That might be interesting. It might also be interesting to try > swapping this with a genuine Cyclades product.. :-) Yup! We had one hell of a time finding a dealer for any kind of decent card here in Germany. We started out by ordering a 2 Riscom/8 port cards which on closer inspection turneded out to be a CD1400 boards. ;-) After initial hair pulling and a short "grep 1400 *" in /usr/src/sys/i386/isa we decided to go with the cy driver. ;-) Anyway should all else fail I will stick the thing into an isa board. I'll have to update the 2.0r installation on the machine to 2.1 before though. ;-( Looks like were in for more hair pulling tonight ;-( Greetings Christian -- TopLink GbR, Internet Services info@toplink.net Christian Kratzer http://www.toplink.net/ Phone: +49 7452 87174 Fax: +49 7452 87175 FreeBSD spoken here! From owner-freebsd-hackers Thu Apr 25 07:02:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA11157 for hackers-outgoing; Thu, 25 Apr 1996 07:02:30 -0700 (PDT) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA11151 for ; Thu, 25 Apr 1996 07:02:25 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.7.5/8.6.9) with SMTP id JAA03698 for ; Thu, 25 Apr 1996 09:02:24 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Thu, 25 Apr 96 09:02 CDT Received: by mars.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Thu, 25 Apr 96 09:02 CDT Message-Id: Subject: Win mail clients with MAPI To: hackers@freebsd.org Date: Thu, 25 Apr 1996 09:02:20 -0500 (CDT) From: "Lars Jonas Olsson" Cc: jonas@mcs.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to find an email solution with FreeBSD as mail server. The problem is that the mail clients (on WfWG) have to have full MAPI support. MAPI is some microsoft standard for manipulating, reading, and writing mail from other programs (We would use it to synchronize remote data bases for Commence package). My original idea was to use Eudora Pro that claims MAPI support. This doesn't have full support though and doesn't work well with Commence. Are there some other recommended mail clients for WfWG with MAPI support and that work with SMTP/POP? Any demo versions? Jonas (Trying to avoid MS Exchange on NT server) From owner-freebsd-hackers Thu Apr 25 07:22:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA12494 for hackers-outgoing; Thu, 25 Apr 1996 07:22:21 -0700 (PDT) Received: from suw3svr01.hisd.harris.com (suw3svr01.hisd.harris.com [158.147.19.67]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA12480 Thu, 25 Apr 1996 07:22:16 -0700 (PDT) Received: from suw2k.hisd.harris.com by suw3svr01.hisd.harris.com (SMI-8.6/SMI-SVR4) id KAA15194; Thu, 25 Apr 1996 10:15:58 -0400 Received: by suw2k.hisd.harris.com (4.1/SMI-4.1) id AA10683; Thu, 25 Apr 96 10:14:08 EDT Date: Thu, 25 Apr 96 10:14:08 EDT From: jleppek@suw2k.hisd.harris.com (James Leppek) Message-Id: <9604251414.AA10683@suw2k.hisd.harris.com> To: gpalmer@FreeBSD.ORG Subject: Re: could tunnel device do this? Cc: freebsd-hackers@freefall.freebsd.org Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I did not word my question and therefore my intent very well at all :-) I really wasn't looking for a tap but more like an intermediate route to a process. I would like to be able to provide IP security via a user process. Ideally I would like to be able to push (like streams) a new module into the network interface. I guess there is no clean way to do that. :-( Trying to generate some type of IP-in-IP scheme would still rely on application level knowledge of another network/packet type. Oh well.... Thanks Jim Leppek > From gary@palmer.demon.co.uk Wed Apr 24 17:07:27 1996 > To: jleppek@suw2k.hisd.harris.com (James Leppek) > Cc: freebsd-hackers@freefall.freebsd.org > From: "Gary Palmer" > Subject: Re: could tunnel device do this? > Date: Wed, 24 Apr 1996 22:09:37 +0100 > Sender: gary@palmer.demon.co.uk > > James Leppek wrote in message ID > <9604221350.AA06758@suw2k.hisd.harris.com>: > > This is really a 2 part question: > > > part 1: what would be the best way to route all IP packets from a > > ethernet card to a process, I am guessing that the tun > > device could do this. > > I don't think you can do this. The `tun' device acts like a normal > network interface, and has it's own route, etc, so you couldn't just > dump all the traffic from an ethernet onto it, the packet would have > to be routed to the i/f. Perhaps the `bpf' device is what you're > looking for? > > > part 2: what kind of thruput could be expected when doing this? If I had > > a pentium 166 could it saturate a 10Mbit line? What % of a 100Mbit link > > Dunno ... you were asking in part one about dumping ether -> process, > not vice versa! > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD - Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info. > From owner-freebsd-hackers Thu Apr 25 07:59:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA14771 for hackers-outgoing; Thu, 25 Apr 1996 07:59:04 -0700 (PDT) Received: from lenzi ([200.247.248.103]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA14759 for ; Thu, 25 Apr 1996 07:58:57 -0700 (PDT) Received: (from lenzi@localhost) by lenzi (8.6.12/8.6.12) id LAA02088; Thu, 25 Apr 1996 11:50:03 -0300 Date: Thu, 25 Apr 1996 11:50:03 -0300 (EST) From: "Lenzi, Sergio" X-Sender: lenzi@lenzi To: Mark Bernard cc: hackers@FreeBSD.org Subject: Re: How do I setup up SMTP or using Eudora, ect... to access mail In-Reply-To: <317EF3D8.6D67@nhr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Mark Bernard wrote: > I have just installed Release 2.1 > > I would like to set up the systems to use the SMTP so I can set up users > with Dos/Win boxes to access Mail without having to use telnet. > > Any help would be appreciated. Hello Mark. You must install the pop server (qpop on the packages/All) and edit the /etc/inetd.conf to enable pop. From owner-freebsd-hackers Thu Apr 25 08:46:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA17993 for hackers-outgoing; Thu, 25 Apr 1996 08:46:17 -0700 (PDT) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA17988 for ; Thu, 25 Apr 1996 08:46:15 -0700 (PDT) Received: (from chuck@localhost) by fang.cs.sunyit.edu (8.6.9/8.6.9) id LAA01369 for hackers@freebsd.org; Thu, 25 Apr 1996 11:46:14 -0400 Date: Thu, 25 Apr 1996 11:46:14 -0400 From: Charles Green Message-Id: <199604251546.LAA01369@fang.cs.sunyit.edu> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: hackers@freebsd.org Subject: USS Lite Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It appears Hannu Savolainen has `somewhat' changed his copywrite on USS Lite. It now says: "USS Lite is a freeware version of the full UNIX Sound System. In short it's exactly the same than current TASD 3.5 which is available for Linux, FreeBSD and BSD/OS 2.1. The only difference between TASD and USS Lite will be a minor change in copying conditions. USS Lite will be distributed under standard GPL. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ A bit different than what he previously was requesting. This is still restrictive though. -- Charles Green, PRC Inc. UN*X System Administration 22 Powell Ave. Apt. B UN*X Security & Whitesboro, NY 13492 Programming From owner-freebsd-hackers Thu Apr 25 09:13:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA19335 for hackers-outgoing; Thu, 25 Apr 1996 09:13:42 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA19257 for ; Thu, 25 Apr 1996 09:12:06 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id TAA24528; Thu, 25 Apr 1996 19:17:03 +0300 Date: Thu, 25 Apr 1996 19:17:02 +0300 (EET DST) From: Narvi To: Charles Green cc: hackers@FreeBSD.org Subject: Re: USS Lite In-Reply-To: <199604251546.LAA01369@fang.cs.sunyit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Eat good food, preserve nature, be nice to all nice people :) On Thu, 25 Apr 1996, Charles Green wrote: > > It appears Hannu Savolainen has `somewhat' changed his copywrite on > USS Lite. It now says: > > "USS Lite is a freeware version of the full UNIX Sound System. In short it's > exactly the same than current TASD 3.5 which is available for Linux, FreeBSD > and BSD/OS 2.1. The only difference between TASD and USS Lite will be a minor > change in copying conditions. USS Lite will be distributed under standard GPL. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > A bit different than what he previously was requesting. This is still > restrictive though. Ok, I didn't take part in the discussion the other time, but - aren't the conditions changing a bit too quickly? > > -- > Charles Green, PRC Inc. UN*X System Administration > 22 Powell Ave. Apt. B UN*X Security & > Whitesboro, NY 13492 Programming > Sander From owner-freebsd-hackers Thu Apr 25 09:55:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA21461 for hackers-outgoing; Thu, 25 Apr 1996 09:55:17 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA21439 Thu, 25 Apr 1996 09:55:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id CAA31691; Fri, 26 Apr 1996 02:39:50 +1000 Date: Fri, 26 Apr 1996 02:39:50 +1000 From: Bruce Evans Message-Id: <199604251639.CAA31691@godzilla.zeta.org.au> To: bde@zeta.org.au, ck@toplink.net Subject: Re: Going gaga over Cyclades board Cc: hackers@freebsd.org, isp@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >we've been trying to wire up a cyclades 1400 based pccom 8 /port serial >> >adapter under FreeBSD 2.1r. >> >> Which model number exactly? Old 8Yo boards have problems on some PCI >It's not a genuine cyclom board. The board is an ISA 8 port (2 x CD1400, >DB25 connectors) from a manufacturer called PCCom. The PC in question >has an asus pentium/tri motherboard. Do you think I should try sticking >the serial card into a plain ISA Mainboard ? The PCI problem is probably unique to the Cyclades board. A 1400-based board is unlikely to work if it doesn't claim compatibility with the Cyclades. Note that the 1400 is a Cirrus chip, not a Cyclades chip. It requires more off-chip support than an 8250..16550, and it isn't as standard, so a 1400-based board is unlikely to use exactly the same bus interface as the Cyclades. One of the Stallion boards uses cd1400's but has its own driver. >Thanks for the tip. This is what pstat gets when I cu to the ports >cuac0 has a modem connected to it cuac1 does not (dangling cable). >I have had the card at irq 12 and irq 15 and at d8000,da000,dc000 all >with the same effect. Characters end up in the output queue but don't >get sent out. > 16 cy lines > LINE RAW CAN OUT HWT LWT COL STATE SESS PGID DISC > cuac0 0 0 14 1296 256 16 OCcB 0 0 term > cuac1 0 0 7 1296 256 9 OCcB 0 0 term This is exactly what happens when I connect to a Cyclades port that isn't connected to anything. The board must be fairly compatible for you to get as far as open. Other things to try: - look at the interrupt counts using vmstat -i. - open the port in CLOCAL mode so that output should work even when nothing is connected. Then look at the interrupt counts. - attempt to open the dialout port and on a local line with carrier connected. If it gets past open then it must have detected carrier. Bruce From owner-freebsd-hackers Thu Apr 25 10:09:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22363 for hackers-outgoing; Thu, 25 Apr 1996 10:09:23 -0700 (PDT) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA22354 for ; Thu, 25 Apr 1996 10:09:17 -0700 (PDT) Received: from spase by ns.NL.net via EUnet id AA19384 (5.65b/CWI-3.3); Thu, 25 Apr 1996 16:26:03 +0200 Received: from phobos.spase.nl (phobos [192.9.200.238]) by mercurius.spase.nl (8.6.11/8.6.11) with ESMTP id PAA06490 for ; Thu, 25 Apr 1996 15:39:24 +0200 From: Kees Jan Koster Received: (dutchman@localhost) by phobos.spase.nl (8.6.12/8.6.11) id PAA05537 for freebsd-hackers@FreeBSD.ORG; Thu, 25 Apr 1996 15:39:26 +0200 Message-Id: <199604251339.PAA05537@phobos.spase.nl> Subject: ISBN of latest snapshot CD? To: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers Mailing list) Date: Thu, 25 Apr 1996 15:39:26 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hoi Hacker, What was the ISBN number of the latest snapshot cdrom? Groetjes, Kees Jan ======================================================================v== Kees Jan Koster e-mail: dutchman@spase.nl Van Somerenstraat 50 tel: NL-24-3234708 6521 BS Nijmegen the Netherlands ========================================================================= Who is this general Failure and why is he reading my disk? (anonymous) ========================================================================= From owner-freebsd-hackers Thu Apr 25 11:25:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA28083 for hackers-outgoing; Thu, 25 Apr 1996 11:25:59 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA28062 for ; Thu, 25 Apr 1996 11:25:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with SMTP id TAA01805 ; Thu, 25 Apr 1996 19:25:28 +0100 (BST) To: freebsd-hackers@FreeBSD.ORG CC: Michael Smith , Josh MacDonald , bde@zeta.org.au From: "Gary Palmer" Subject: Warnings in the kernel ( was Re: GNU binutils port ) In-reply-to: Your message of "Wed, 24 Apr 1996 21:43:47 BST." <3851.830378627@palmer.demon.co.uk> Date: Thu, 25 Apr 1996 19:25:28 +0100 Message-ID: <1803.830456728@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I wrote in message ID <3851.830378627@palmer.demon.co.uk>: > I wouldn't be. I've got a development tree with over half those > warnings fixed, and none of them (well, okay, one) could have done > anything nasty. And from a quick glance through, most of the rest are > printf() formatting warnings, as GCC can't understand some of the > special printf contructs available in the kernel. I just had a thought ... there are one HELL of a lot more errors that GCC -Wall **CAN'T** pick up on as they are just bad algorithms which can cause more serious problems than most of the problems that -Wall can pick up on... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD - Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info. From owner-freebsd-hackers Thu Apr 25 12:34:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA03656 for hackers-outgoing; Thu, 25 Apr 1996 12:34:37 -0700 (PDT) Received: from pancake.remcomp.fr (root@pancake.remcomp.fr [194.51.30.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA03641 for ; Thu, 25 Apr 1996 12:34:26 -0700 (PDT) Received: from aida (localhost [127.0.0.1]) by aida (8.6.11/8.6.9) with SMTP id UAA00528 for ; Tue, 23 Apr 1996 20:09:17 +0200 Date: Tue, 23 Apr 1996 20:09:17 +0200 (MET DST) From: didier@aida.org To: hackers@freebsd.org Subject: what is fvwm95 ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk where may I find it ? -- Didier Derny | Microsoft Free Computer. | AM586-160 ASUS PVI 486SP3 didier@aida.org | Private FreeBSD 2.1-STABLE site. | aha2940 / 1Gb HAWK From owner-freebsd-hackers Thu Apr 25 12:47:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04475 for hackers-outgoing; Thu, 25 Apr 1996 12:47:43 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA04470 for ; Thu, 25 Apr 1996 12:47:41 -0700 (PDT) Received: from toplink1.toplink.net (toplink1.toplink.net [194.163.120.1]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id MAA23968 for ; Thu, 25 Apr 1996 12:43:45 -0700 Received: (from ck@localhost) by toplink1.toplink.net (8.6.9/8.6.9) id VAA23682; Thu, 25 Apr 1996 21:34:38 +0200 From: Christian Kratzer Message-Id: <199604251934.VAA23682@toplink1.toplink.net> Subject: Re: PCCOM Cyclades clone (was Going gaga over ...) To: bde@zeta.org.au (Bruce Evans) Date: Thu, 25 Apr 1996 21:34:37 +0200 (MET DST) Cc: hackers@freebsd.org In-Reply-To: <199604251639.CAA31691@godzilla.zeta.org.au> from "Bruce Evans" at Apr 26, 96 02:39:50 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi > > 16 cy lines > > LINE RAW CAN OUT HWT LWT COL STATE SESS PGID DISC > > cuac0 0 0 14 1296 256 16 OCcB 0 0 term > > cuac1 0 0 7 1296 256 9 OCcB 0 0 term > > This is exactly what happens when I connect to a Cyclades port that > isn't connected to anything. > > The board must be fairly compatible for you to get as far as open. it looks like it's some kind of cyclades clone. The manual does not mention the cyclom board but it came with xeroxed instructions on how to use the card in linux with the cyclom driver. So it can't be too distant. There's propably some minor incompatibility somewhere. Anyway I'm determined to get this thing to work now. I'll check the linux driver source for any hints. > Other things to try: > - look at the interrupt counts using vmstat -i. > - open the port in CLOCAL mode so that output should work even when > nothing is connected. Then look at the interrupt counts. > - attempt to open the dialout port and on a local line with carrier > connected. If it gets past open then it must have detected carrier. Looks like the card is not throwing any interrupts. I'll let you know once I find out more. ck@toplink2: {49} vmstat -i interrupt total rate clk0 irq0 1185647 101 rtc0 irq8 1493333 128 sc0 irq1 22 0 ep0 irq10 104591 8 Total 2783593 238 Greetings and thanks for all the help Christian -- TopLink GbR, Internet Services info@toplink.net Christian Kratzer http://www.toplink.net/ Phone: +49 7452 87174 Fax: +49 7452 87175 FreeBSD spoken here! From owner-freebsd-hackers Thu Apr 25 13:10:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA06111 for hackers-outgoing; Thu, 25 Apr 1996 13:10:13 -0700 (PDT) Received: from iway.chartway.com (iway.chartway.com [199.3.227.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA06092 for ; Thu, 25 Apr 1996 13:10:02 -0700 (PDT) Received: (from markb@localhost) by iway.chartway.com (8.6.12/8.6.9) id QAA10625; Thu, 25 Apr 1996 16:10:58 -0400 Date: Thu, 25 Apr 1996 16:10:58 -0400 (EDT) From: Mark Bernard To: hackers@Freebsd.org Subject: Tape Backup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@Freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm looking for backup solutions for my 2.1 release. We have a Colorado Trakker 350 parallel tape backup. Are there any software packages out there or is there anything built in that I can use that tape backup. Any suggestions would be great. Thanks. Mark From owner-freebsd-hackers Thu Apr 25 13:31:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07704 for hackers-outgoing; Thu, 25 Apr 1996 13:31:43 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA07691 for ; Thu, 25 Apr 1996 13:31:41 -0700 (PDT) Received: from distortion.eng.umd.edu (distortion.eng.umd.edu [129.2.98.6]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id NAA20790 for ; Thu, 25 Apr 1996 13:31:10 -0700 (PDT) Received: from professor.eng.umd.edu (professor.eng.umd.edu [129.2.98.207]) by distortion.eng.umd.edu (8.7.5/8.7.3) with ESMTP id QAA27676; Thu, 25 Apr 1996 16:28:24 -0400 (EDT) Received: (from chuckr@localhost) by professor.eng.umd.edu (8.7.5/8.7.3) id QAA17745; Thu, 25 Apr 1996 16:28:23 -0400 (EDT) Date: Thu, 25 Apr 1996 16:28:23 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@professor.eng.umd.edu To: Kees Jan Koster cc: FreeBSD hackers Mailing list Subject: Re: ISBN of latest snapshot CD? In-Reply-To: <199604251339.PAA05537@phobos.spase.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Kees Jan Koster wrote: > Hoi Hacker, > > What was the ISBN number of the latest snapshot cdrom? ISBN 1-57176-158-6 > > Groetjes, > Kees Jan > > ======================================================================v== > Kees Jan Koster e-mail: dutchman@spase.nl > Van Somerenstraat 50 tel: NL-24-3234708 > 6521 BS Nijmegen > the Netherlands > ========================================================================= > Who is this general Failure and why is he reading my disk? (anonymous) > ========================================================================= > > ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-hackers Thu Apr 25 14:07:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA10203 for hackers-outgoing; Thu, 25 Apr 1996 14:07:50 -0700 (PDT) Received: from mail1.infinet.com (mail1.infinet.com [206.103.240.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA10194 for ; Thu, 25 Apr 1996 14:07:41 -0700 (PDT) Received: from skuld.cylatech.com (cmh-p106.infinet.com [206.103.242.112]) by mail1.infinet.com (8.7.3/8.7.3) with SMTP id RAA18601 for ; Thu, 25 Apr 1996 17:02:53 -0400 (EDT) Message-ID: <317FE9A0.481E@cylatech.com> Date: Thu, 25 Apr 1996 17:07:44 -0400 From: Wilson MacGyver Organization: CylaTech Inc. X-Mailer: Mozilla 2.01Gold (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: good press in InfoWorld Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There is some good press about FreeBSD in this week of InfoWorld, It's in Brett Glass's Help Desk Column. From owner-freebsd-hackers Thu Apr 25 17:19:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23104 for hackers-outgoing; Thu, 25 Apr 1996 17:19:34 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA23098 for ; Thu, 25 Apr 1996 17:19:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA25978; Thu, 25 Apr 1996 17:14:32 -0700 From: Terry Lambert Message-Id: <199604260014.RAA25978@phaeton.artisoft.com> Subject: Re: USS Lite To: green@fang.cs.sunyit.edu (Charles Green) Date: Thu, 25 Apr 1996 17:14:31 -0700 (MST) Cc: hackers@FreeBSD.org In-Reply-To: <199604251546.LAA01369@fang.cs.sunyit.edu> from "Charles Green" at Apr 25, 96 11:46:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It appears Hannu Savolainen has `somewhat' changed his copywrite on > USS Lite. It now says: > > "USS Lite is a freeware version of the full UNIX Sound System. In short it's > exactly the same than current TASD 3.5 which is available for Linux, FreeBSD > and BSD/OS 2.1. The only difference between TASD and USS Lite will be a minor > change in copying conditions. USS Lite will be distributed under standard GPL. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > A bit different than what he previously was requesting. This is still > restrictive though. Ask for LGPL. A kernel module will, by definition, meet the relink clause for the LGPL. Otherwise it will be impossible to distribute binaraies (the default sound code should operate without needing to recompile the kernel, IMO, so binaries are an absolute necessity -- GPL restrictions on distributed binaries preclude distributing binaraies that are not wholly GPL). 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 Apr 25 17:23:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23260 for hackers-outgoing; Thu, 25 Apr 1996 17:23:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA23254 for ; Thu, 25 Apr 1996 17:23:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA25990; Thu, 25 Apr 1996 17:18:13 -0700 From: Terry Lambert Message-Id: <199604260018.RAA25990@phaeton.artisoft.com> Subject: Re: Tape Backup To: markb@chartway.com (Mark Bernard) Date: Thu, 25 Apr 1996 17:18:13 -0700 (MST) Cc: hackers@FreeBSD.org In-Reply-To: from "Mark Bernard" at Apr 25, 96 04:10:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'm looking for backup solutions for my 2.1 release. We have a Colorado > Trakker 350 parallel tape backup. Are there any software packages out > there or is there anything built in that I can use that tape backup. I do not believe any parallel port devices, other than printers and PL/IP, are supported because of proprietary access methods. THere was a recent posting of a response from Xirxom -- Xircom, in quoted material in the post, said that freeware authors would be provided with information necessary to write drivers for their devices. No such information has been forthcoming from CMS regarding the PL devices... you would have to get the information from them. In addition, since this means that the device is currently unsopported, it is unlikely that anyone else in the BSD camps has one available for testing and/or deriver writing to help you out, which would pretty much put you on your own. 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 Apr 25 18:03:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA24886 for hackers-outgoing; Thu, 25 Apr 1996 18:03:23 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA24873 for ; Thu, 25 Apr 1996 18:03:05 -0700 (PDT) Received: from Early-Bird-1.Think.COM by mail.think.com; Thu, 25 Apr 96 21:02:56 -0400 Received: from compound.Think.COM (fergus-27.dialup.cfa.org) by Early-Bird.Think.COM; Thu, 25 Apr 96 21:02:53 EDT Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id VAA04749; Thu, 25 Apr 1996 21:02:51 -0500 (CDT) Date: Thu, 25 Apr 1996 21:02:51 -0500 (CDT) Message-Id: <199604260202.VAA04749@compound.Think.COM> From: Tony Kimball To: jonas@mcs.com Cc: hackers@freebsd.org Subject: Win mail clients with MAPI Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: "Lars Jonas Olsson" Date: Thu, 25 Apr 1996 09:02:20 -0500 (CDT) MAPI is some microsoft standard for manipulating, reading, and writing mail Umm, no it is not. MAPI is a proprietary API. It is not in any way, in any meaningful (i.e. un-debased) sense of the word, a standard. 'microsoft standard' is oxymoronic. From owner-freebsd-hackers Thu Apr 25 18:26:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA26118 for hackers-outgoing; Thu, 25 Apr 1996 18:26:11 -0700 (PDT) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA26113 for ; Thu, 25 Apr 1996 18:26:08 -0700 (PDT) Received: from localhost.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.6.12/8.6.12) with SMTP id VAA25217 for ; Thu, 25 Apr 1996 21:26:08 -0400 Message-Id: <199604260126.VAA25217@spooky.rwwa.com> X-Authentication-Warning: spooky.rwwa.com: Host localhost.rwwa.com didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: freebsd-hackers@FreeBSD.org Subject: Re: GNU binutils port In-reply-to: Your message of "Thu, 25 Apr 1996 09:07:03 +1000." <199604242307.JAA25542@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Apr 1996 21:26:08 -0400 From: Robert Withrow Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >I really doubt sizeof(void *) != sizeof(??? *) any time soon. > > It happens every day, but not on the i386. Especially with function pointers, which I didn't realize until recently even after decades of programming. Sigh. ----------------------------------------------------------------------------- Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM From owner-freebsd-hackers Thu Apr 25 19:45:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA02457 for hackers-outgoing; Thu, 25 Apr 1996 19:45:24 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA02450 for ; Thu, 25 Apr 1996 19:45:20 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id UAA22201; Thu, 25 Apr 1996 20:43:44 -0600 (MDT) Message-Id: <199604260243.UAA22201@rover.village.org> To: Robert Withrow Subject: Re: GNU binutils port Cc: freebsd-hackers@FreeBSD.org In-reply-to: Your message of Thu, 25 Apr 1996 21:26:08 EDT Date: Thu, 25 Apr 1996 20:43:44 -0600 From: Warner Losh Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : Especially with function pointers, which I didn't realize until : recently even after decades of programming. Sigh. At least in C++ you have this fact driven home by the member function pointer size usually being somewhere near 8... :-) Warner From owner-freebsd-hackers Thu Apr 25 19:57:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA03287 for hackers-outgoing; Thu, 25 Apr 1996 19:57:34 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA03280 Thu, 25 Apr 1996 19:57:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA21729; Fri, 26 Apr 1996 12:51:20 +1000 Date: Fri, 26 Apr 1996 12:51:20 +1000 From: Bruce Evans Message-Id: <199604260251.MAA21729@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.org, gpalmer@FreeBSD.org Subject: Re: Warnings in the kernel ( was Re: GNU binutils port ) Cc: bde@zeta.org.au, jmacd@cs.berkeley.edu, msmith@atrad.adelaide.edu.au Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I built some 2.1R kernels with the -current gcc and the -current CWARNFLAGS. The error output had the following number of lines: GENERIC-2.1R: 8760 LINT-2.1R: 14765 LINT-current: 73 Bruce From owner-freebsd-hackers Thu Apr 25 20:27:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA05027 for hackers-outgoing; Thu, 25 Apr 1996 20:27:26 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA05013 for ; Thu, 25 Apr 1996 20:27:22 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id XAA05172; Thu, 25 Apr 1996 23:27:03 -0400 (EDT) Date: Thu, 25 Apr 1996 23:27:02 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: Terry Lambert cc: Charles Green , hackers@FreeBSD.ORG Subject: Re: USS Lite In-Reply-To: <199604260014.RAA25978@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Terry Lambert wrote: > > It appears Hannu Savolainen has `somewhat' changed his copywrite on > > USS Lite. It now says: > > Otherwise it will be impossible to distribute binaraies (the default > sound code should operate without needing to recompile the kernel, > IMO, so binaries are an absolute necessity -- GPL restrictions on > distributed binaries preclude distributing binaraies that are not > wholly GPL). So you're saying that "technically", Hannu hasn't changed his license agreement- Just reworded it?? Damn, now we've gone from a one screen licence to a 6 page licence-- I'm so confused :) Sujal From owner-freebsd-hackers Thu Apr 25 21:48:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA08225 for hackers-outgoing; Thu, 25 Apr 1996 21:48:18 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA08218 for ; Thu, 25 Apr 1996 21:48:14 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id LAA25761; Thu, 25 Apr 1996 11:02:29 -0700 (PDT) Message-Id: <199604251802.LAA25761@ref.tfs.com> Subject: Re: Flaws in system() implementation? To: bde@zeta.org.au (Bruce Evans) Date: Thu, 25 Apr 1996 11:02:28 -0700 (PDT) From: "JULIAN Elischer" Cc: jraynard@dial.pipex.com, hackers@freebsd.org In-Reply-To: <199604250044.KAA29532@godzilla.zeta.org.au> from "Bruce Evans" at Apr 25, 96 10:44:43 am X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > >> > 1. Use of a wait union when an int would do. > >> This is the correct POSIX thing to do.. > >> check the man page for wait. > > >According to the 2.1.0-RELEASE man page, wait and friends use an int* > >for the status variable. > > That is the correct POSIX thing. I stand corrected LIBRARY Standard C Library (libc.a) SYNOPSIS #include #include pid_t wait( int *status_location); pid_t waitpid( pid_t process_id, int *status_location, int options); > > >> > 3. Returns 0 if fork() fails, when -1 seems more appropriate. > >> POSIX says: > > >Thanks for posting this, I don't have access to any POSIX specs > >(except the odd snippet in books). What's the best way of getting hold > >of them? > > Joerg said that the draft POSIX spec is on the (old) WC Internet Info > cdrom. I haven't got it. I have actually only got the x/open XPG4 spec which says that it is POSIX2 compliant > > It's less ambiguous than julianese :-). It completely specifies the gee thanks :) I copied it word for word from XPG4 > return value after a fork failure, at least in my copy, which says > "shall return -1" instead of "returns -1". "shall" is standardese that > means that the implementation is non-conforming if it does anything > else. "should" would allow the implementation to screw up. > > Bruce > From owner-freebsd-hackers Thu Apr 25 23:00:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA11644 for hackers-outgoing; Thu, 25 Apr 1996 23:00:58 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA11639 for ; Thu, 25 Apr 1996 23:00:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id WAA26674; Thu, 25 Apr 1996 22:54:53 -0700 From: Terry Lambert Message-Id: <199604260554.WAA26674@phaeton.artisoft.com> Subject: Re: USS Lite To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Thu, 25 Apr 1996 22:54:53 -0700 (MST) Cc: terry@lambert.org, green@fang.cs.sunyit.edu, hackers@FreeBSD.ORG In-Reply-To: from "Sujal Patel" at Apr 25, 96 11:27:02 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > It appears Hannu Savolainen has `somewhat' changed his copywrite on > > > USS Lite. It now says: > > > > Otherwise it will be impossible to distribute binaraies (the default > > sound code should operate without needing to recompile the kernel, > > IMO, so binaries are an absolute necessity -- GPL restrictions on > > distributed binaries preclude distributing binaraies that are not > > wholly GPL). > > So you're saying that "technically", Hannu hasn't changed his license > agreement- Just reworded it?? Damn, now we've gone from a one screen > licence to a 6 page licence-- I'm so confused :) Not at all. You could put the uncompiled drivers on a comercial CDROM -- you couldn't do that before, I think. 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 Apr 25 23:34:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA12967 for hackers-outgoing; Thu, 25 Apr 1996 23:34:39 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA12962 Thu, 25 Apr 1996 23:34:35 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA24211; Fri, 26 Apr 1996 08:25:56 +0200 Message-Id: <199604260625.IAA24211@ra.dkuug.dk> Subject: If you mailed me in the last 20 hours... To: hackers@freebsd.org (FreeBSD hackers), core@freebsd.org (FreeBSD core) Date: Fri, 26 Apr 1996 08:25:55 +0200 (MET DST) From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ... there is a good chance that the mail has benn lost :( (yeah, I know I shouldn't play with firewall code :)) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-hackers Fri Apr 26 00:46:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA20888 for hackers-outgoing; Fri, 26 Apr 1996 00:46:24 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA20883 for ; Fri, 26 Apr 1996 00:46:20 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA14987; Fri, 26 Apr 1996 09:44:17 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA15534; Fri, 26 Apr 1996 09:44:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA04946; Fri, 26 Apr 1996 09:38:32 +0200 (MET DST) From: J Wunsch Message-Id: <199604260738.JAA04946@uriah.heep.sax.de> Subject: Re: Tape Backup To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 26 Apr 1996 09:38:31 +0200 (MET DST) Cc: markb@chartway.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604260018.RAA25990@phaeton.artisoft.com> from "Terry Lambert" at Apr 25, 96 05:18:13 pm X-Phone: +49-351-2012 669 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > In addition, since this means that the device is currently > unsopported, it is unlikely that anyone else in the BSD camps > has one available for testing and/or deriver writing to help > you out, which would pretty much put you on your own. ...and given that even three developers by now have already been pissed of by the terrible floppy-tape handling _via the well- documented FDC_ (ok, comparably well-documented), i doubt anybody is going to burn his time and wrestle his brain in such a device. (People like me coming from a hardware background distrust anything hanging off a Centronics-style port that is not a printer anyway. This interface has not been designed with high-speed data communications in mind, at least not the ``classical'' Centronics port.) -- 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 Fri Apr 26 02:57:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA28546 for hackers-outgoing; Fri, 26 Apr 1996 02:57:52 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA28541 Fri, 26 Apr 1996 02:57:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id CAA29495; Fri, 26 Apr 1996 02:57:31 -0700 (PDT) To: sef@freebsd.org cc: hackers@freebsd.org Subject: Something fishy with our PT_ATTACH code! Date: Fri, 26 Apr 1996 02:57:31 -0700 Message-ID: <29493.830512651@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just got back from Kirk's usual Thursday-night OS class and while we were going through exit1(), I noticed something that looked a little odd in the ptrace "reattach" code. In following it (and it later turned out to be correct), I happened to notice the following weird behavior with attach and detach: Sequence: [d0] jkh-ttyp4@time-> cat [d1] jkh-ttyp5@time-> ps ax | grep cat [d2] jkh-ttyp5@time-> gdb (gdb) attach [d3] [d4] (gdb) detach [d5] [1]+ Suspended (signal) cat This is probably a bit hard to read, so I'll give you a synopsis: Start cat, attach cat from another tty with gdb, watch cat go to sleep, detach cat in gdb and watch cat erroneously suspend itself. It would seem to me that the far more correct behavior would be something like: Start cat, attach cat from another tty with gdb, watch cat go to sleep, detach cat in gdb and watch it return to its previous un-stopped state. Or am I off-base on this one somehow? Jordan From owner-freebsd-hackers Fri Apr 26 06:20:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA06631 for hackers-outgoing; Fri, 26 Apr 1996 06:20:48 -0700 (PDT) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA06621 for ; Fri, 26 Apr 1996 06:20:39 -0700 (PDT) Received: from spase by ns.NL.net via EUnet id AA07350 (5.65b/CWI-3.3); Fri, 26 Apr 1996 14:16:40 +0200 Received: (from dutchman@localhost) by mercurius.spase.nl (8.6.11/8.6.11) id OAA16455; Fri, 26 Apr 1996 14:13:55 +0200 From: Kees Jan Koster Message-Id: <199604261213.OAA16455@mercurius.spase.nl> Subject: Bonnie on Quantum 810MB disk. To: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers Mailing list) Date: Fri, 26 Apr 1996 14:13:55 +0200 (MET DST) Cc: .@spase.nl X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hoi Hackers, I now have two reasonably comparable machines. Again I've tried bonnie. The runs were made on a working day, with X11 up and running. Let me see... phobos is a pentium 90 Mhz, deimos is an i486DX2-66. Both have an on-board pci ide contoller and a single quantum 810Mb disk, mounted asynchonous (the difference between sync and async is practically nil for the results of bonnie, altough I don't have figures on that). I've run the test twice, once with the standard entries in the config file and once with the flags of the wdc set to 0x80ff80ff (that's the "(32)" results). Special thanks to Andrew Stesin, who pointed me to the wdc flags. (He practically had to rub my nose in them before I found them <:) ). -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU phobos 40 1179 38.5 1745 17.4 723 10.2 1237 35.5 1709 13.6 46.0 4.4 phobos 40 1158 38.5 1719 19.1 475 6.6 945 27.8 1744 15.2 47.6 4.7 phobos(32) 40 1248 42.5 1893 20.0 804 10.6 1574 45.5 2100 17.9 49.4 5.3 phobos(32) 40 1296 45.0 1913 18.9 832 10.7 1535 44.4 2065 17.1 48.3 5.3 deimos 40 703 49.9 1184 16.6 617 13.6 720 50.5 1244 14.6 45.6 6.2 deimos 40 703 49.9 1189 17.3 619 13.4 720 50.0 1248 13.8 45.4 6.1 deimos(32) 40 733 54.2 1305 21.9 671 14.5 758 52.4 1361 15.3 44.6 7.0 deimos(32) 40 744 55.5 1300 22.1 669 14.9 757 52.6 1338 15.6 42.1 6.6 Are these figures reasonable? Is there any way to squeeze a little extra performance out of these machines? (Without buying hardware :-) ) Groetjes, Kees Jan PS. I've appended the dmesgs to this mail. ======================================================================v== Kees Jan Koster e-mail: dutchman@spase.nl Van Somerenstraat 50 tel: NL-24-3234708 6521 BS Nijmegen the Netherlands ========================================================================= Who is this general Failure and why is he reading my disk? (anonymous) ========================================================================= dmesg for phobos: FreeBSD 2.1.0-RELEASE #8: Fri Apr 26 09:38:31 MET DST 1996 dutchman@phobos:/usr/src/sys/compile/PHOBOS CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 16777216 (16384K bytes) avail memory = 15089664 (14736K bytes) 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 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-8 wd0: 810MB (1660176 sectors), 1647 cyls, 16 heads, 63 S/T, 512 B/S 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 7 on isa ep0: aui/bnc/utp[*BNC*] address 00:a0:24:42:bf:b4 irq 7 npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: pci0:0: UMC, device=0x0891, class=bridge (host) [no driver assigned] vga0 rev 0 int a irq 10 on pci0:14 pci0:18: UMC, device=0x886a, class=bridge (isa) [no driver assigned] dmesg for deimos: FreeBSD 2.1.0-RELEASE #2: Fri Apr 26 13:10:22 MET DST 1996 dutchman@deimos:/usr/src/sys/compile/DEIMOS CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 15085568 (14732K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , multi-block-8 wd0: 810MB (1660176 sectors), 1647 cyls, 16 heads, 63 S/T, 512 B/S 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 7 on isa ep0: aui/bnc/utp[*BNC*] address 00:a0:24:42:bf:56 irq 7 npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: chip0 rev 2 on pci0:0 pci0:1: NCR/Symbios, device=0x0001, class=old (misc) [no driver assigned] chip1 rev 0 on pci0:2 vga0 rev 0 int a irq 5 on pci0:3 From owner-freebsd-hackers Fri Apr 26 07:07:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA09131 for hackers-outgoing; Fri, 26 Apr 1996 07:07:32 -0700 (PDT) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA09124 for ; Fri, 26 Apr 1996 07:07:27 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.7.5/8.6.9) with SMTP id JAA19837; Fri, 26 Apr 1996 09:07:15 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 26 Apr 96 09:07 CDT Received: by mars.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 26 Apr 96 09:07 CDT Message-Id: Subject: Re: Win mail clients with MAPI To: alk@Think.COM (Tony Kimball) Date: Fri, 26 Apr 1996 09:07:12 -0500 (CDT) From: "Lars Jonas Olsson" Cc: hackers@freebsd.org In-Reply-To: <199604260202.VAA04749@compound.Think.COM> from "Tony Kimball" at Apr 25, 96 09:02:51 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > From: "Lars Jonas Olsson" > Date: Thu, 25 Apr 1996 09:02:20 -0500 (CDT) > > MAPI is some microsoft standard for manipulating, reading, > and writing mail > > Umm, no it is not. MAPI is a proprietary API. It is > not in any way, in any meaningful (i.e. un-debased) > sense of the word, a standard. 'microsoft standard' > is oxymoronic. > OK, how about a winsock mail reader using pop3/smtp that has CMC support? CMC is similar to MAPI and is supposedly supported by some UNIX platforms also. (Any FreeBSD mail reader with CMC?) Jonas From owner-freebsd-hackers Fri Apr 26 09:03:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16070 for hackers-outgoing; Fri, 26 Apr 1996 09:03:43 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA16063 for ; Fri, 26 Apr 1996 09:03:41 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id JAA13098; Fri, 26 Apr 1996 09:03:40 -0700 Date: Fri, 26 Apr 1996 09:03:40 -0700 From: Sean Eric Fagan Message-Id: <199604261603.JAA13098@kithrup.com> To: jkh@time.cdrom.com Subject: Re: Something fishy with our PT_ATTACH code! Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Just got back from Kirk's usual Thursday-night OS class and while we >were going through exit1(), I noticed something that looked a little >odd in the ptrace "reattach" code. In following it (and it later >turned out to be correct), I happened to notice the following weird >behavior with attach and detach: Well, I didn't write the attach/detach code ;). >This is probably a bit hard to read, so I'll give you >a synopsis: Start cat, attach cat from another tty with >gdb, watch cat go to sleep, detach cat in gdb and watch >cat erroneously suspend itself. It doesn't seem that the detached process is suspending itself so much as it is simply renotifying the parent that it is still stopped. This could be wrong behaviour, however. To change that, in the PT_DETACH code, a psignal(p, SIGCONT); would do the trick. I think ;). Sean. From owner-freebsd-hackers Fri Apr 26 09:06:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16316 for hackers-outgoing; Fri, 26 Apr 1996 09:06:52 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA16309 for ; Fri, 26 Apr 1996 09:06:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA00231; Fri, 26 Apr 1996 09:06:37 -0700 (PDT) To: Sean Eric Fagan cc: hackers@freebsd.org Subject: Re: Something fishy with our PT_ATTACH code! In-reply-to: Your message of "Fri, 26 Apr 1996 09:03:40 PDT." <199604261603.JAA13098@kithrup.com> Date: Fri, 26 Apr 1996 09:06:37 -0700 Message-ID: <229.830534797@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It doesn't seem that the detached process is suspending itself so much as it > is simply renotifying the parent that it is still stopped. This could be > wrong behaviour, however. > > To change that, in the PT_DETACH code, a > > psignal(p, SIGCONT); > > would do the trick. I think ;). Well, it seems to me that we should really restore the process's previous state - what if it was suspended to start with? :-) Jordan From owner-freebsd-hackers Fri Apr 26 09:17:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16662 for hackers-outgoing; Fri, 26 Apr 1996 09:17:10 -0700 (PDT) Received: from mail1.digital.com (mail1.digital.com [204.123.2.50]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA16657 for ; Fri, 26 Apr 1996 09:17:09 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail1.digital.com (5.65 EXP 4/12/95 for V3.2/1.0/WV) id AA22718; Fri, 26 Apr 1996 09:12:14 -0700 Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA25159; Fri, 26 Apr 1996 18:12:10 +0200 Message-Id: <9604261612.AA25159@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: hackers%freebsd.org@inet-gw-1.pa.dec.com In-Reply-To: Message from "Jordan K. Hubbard" of Fri, 26 Apr 96 02:57:31 PDT. Reply-To: gjennejohn@frt.dec.com Subject: Re: Something fishy with our PT_ATTACH code! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Apr 96 18:12:10 +0200 X-Mts: smtp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk jkh@time.cdrom.com writes: > Just got back from Kirk's usual Thursday-night OS class and while we > were going through exit1(), I noticed something that looked a little > odd in the ptrace "reattach" code. In following it (and it later > turned out to be correct), I happened to notice the following weird > behavior with attach and detach: > > Sequence: > > [d0] jkh-ttyp4@time-> cat > > > [d1] jkh-ttyp5@time-> ps ax | grep cat > > > [d2] jkh-ttyp5@time-> gdb > (gdb) attach > > [d3] > > [d4] (gdb) detach > > [d5] [1]+ Suspended (signal) cat > > > This is probably a bit hard to read, so I'll give you > a synopsis: Start cat, attach cat from another tty with > gdb, watch cat go to sleep, detach cat in gdb and watch > cat erroneously suspend itself. > > It would seem to me that the far more correct behavior would > be something like: > > Start cat, attach cat from another tty with gdb, watch cat go to > sleep, detach cat in gdb and watch it return to its previous > un-stopped state. > > Or am I off-base on this one somehow? > I've noticed this behavior myself, but I wasn't sufficiently irritated by it to track it down. I guess I should take a look at it. Note that gdb doesn't use ptrace to do attach/detach (unless somebody changed it). It uses the procfs stuff. Could be an interesting experiment to change gdb to use ptrace now that there's support in there. This would have the added benefit of allowing those weird people who don't mount their procfs on /procfs to also use attach/detach :-) --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org From owner-freebsd-hackers Fri Apr 26 09:34:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA17319 for hackers-outgoing; Fri, 26 Apr 1996 09:34:20 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA17313 for ; Fri, 26 Apr 1996 09:34:17 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id KAA25506; Fri, 26 Apr 1996 10:28:41 -0600 (MDT) Message-Id: <199604261628.KAA25506@rover.village.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Tape Backup Cc: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers), markb@chartway.com In-reply-to: Your message of Fri, 26 Apr 1996 09:38:31 +0200 Date: Fri, 26 Apr 1996 10:28:40 -0600 From: Warner Losh Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk : ...and given that even three developers by now have already been : pissed of by the terrible floppy-tape handling _via the well- : documented FDC_ (ok, comparably well-documented), i doubt anybody is : going to burn his time and wrestle his brain in such a device. I know that the Linux folks have a driver for the parallel version of the zip drive. Basically, the parallel version of the zip drive has a parallel port -> scsi adapter built into it, but still costs the same or a little less than the pure scsi version. Go figure. If people are wanting something like this on FreeBSD, they might do well to take a look at the Linux drivers. I have no clude if they are sane, insane, documented or not. I just know that some Linux work that I've done prompts me for this interface now :-) Warner From owner-freebsd-hackers Fri Apr 26 15:15:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA08009 for hackers-outgoing; Fri, 26 Apr 1996 15:15:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA08004 for ; Fri, 26 Apr 1996 15:15:53 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28041; Fri, 26 Apr 1996 15:10:00 -0700 From: Terry Lambert Message-Id: <199604262210.PAA28041@phaeton.artisoft.com> Subject: Re: Something fishy with our PT_ATTACH code! To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 26 Apr 1996 15:10:00 -0700 (MST) Cc: sef@kithrup.com, hackers@FreeBSD.org In-Reply-To: <229.830534797@time.cdrom.com> from "Jordan K. Hubbard" at Apr 26, 96 09:06:37 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > It doesn't seem that the detached process is suspending itself so much as it > > is simply renotifying the parent that it is still stopped. This could be > > wrong behaviour, however. > > > > To change that, in the PT_DETACH code, a > > > > psignal(p, SIGCONT); > > > > would do the trick. I think ;). > > Well, it seems to me that we should really restore the process's > previous state - what if it was suspended to start with? :-) begin: initial_state attach_1: current_state -> save_state_1 (initial_state) suspend_state -> current_state attach_2: current_state -> save_state_2 (attach_1_suspend) suspend_state -> current_state detach_1: save_state_1 -> current_state (initial_state) detach_2: save_state_2 -> current_state (attach_1_syspend) end: attach_1_suspend You need to modify attack_2's save_state_2 based on entry order when you detach_1. You need an attach list back-pointer. Or you need to imply O_EXCL and prevent reeentrancy. 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 Apr 26 16:03:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA09884 for hackers-outgoing; Fri, 26 Apr 1996 16:03:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA09878 for ; Fri, 26 Apr 1996 16:03:10 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA30595; Sat, 27 Apr 1996 08:53:41 +1000 Date: Sat, 27 Apr 1996 08:53:41 +1000 From: Bruce Evans Message-Id: <199604262253.IAA30595@godzilla.zeta.org.au> To: imp@village.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: Tape Backup Cc: freebsd-hackers@FreeBSD.org, markb@chartway.com Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I know that the Linux folks have a driver for the parallel version of >the zip drive. Basically, the parallel version of the zip drive has a >parallel port -> scsi adapter built into it, but still costs the same >or a little less than the pure scsi version. Go figure. Be thankful that it doesn't cost twice as much for SCSI. SCSI cdroms seem to be twice as expensive as IDE cdroms here if you can find the SCSI version. I bought the external SCSI version of the zip drive. It cost about the same as a parallel version, except for 13% extra for an external cable, and about 50% extra in wasted time shopping for the cable. Bruce From owner-freebsd-hackers Fri Apr 26 17:46:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA14609 for hackers-outgoing; Fri, 26 Apr 1996 17:46:51 -0700 (PDT) Received: from vent.pipex.net (root@vent.pipex.net [158.43.128.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA14598 for ; Fri, 26 Apr 1996 17:46:47 -0700 (PDT) Received: from dial.pipex.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id BAA05925; Sat, 27 Apr 1996 01:46:37 +0100 Received: (from jraynard@localhost) by dial.pipex.com (8.6.12/8.6.12) id XAA01765; Fri, 26 Apr 1996 23:55:00 GMT Date: Fri, 26 Apr 1996 23:55:00 GMT From: James Raynard Message-Id: <199604262355.XAA01765@dial.pipex.com> To: bde@zeta.org.au CC: bde@zeta.org.au, freebsd-hackers@freebsd.org In-reply-to: <199604250135.LAA31600@godzilla.zeta.org.au> (message from Bruce Evans on Thu, 25 Apr 1996 11:35:03 +1000) Subject: Re: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Actually I was thinking about a "project" that I can do on 2.1.0-R > >code (I don't think I can afford the phone bills involved in running > >-current) and trying to make things like signal-handling in libc more > >Posix-compliant seems like a good one to start with. > > >Any objections and/or pitfalls if I do this? > > Keep up with -current enough to avoid re-doing things (unless you're > just doing them for educational purposes). I just checked the NetBSD Doing this certainly would be educational, but it would be nice if it could be useful to the FreeBSD project (giving something back and all that). I may yet give -current a shot, if I can get my system backed up properly... > version and found that -current would already have your changes if it > kept up with NetBSD :-). The NetBSD version also replaces execl() by > execve(), presumably to save a few cycles. To be honest, I was surprised no-one had thought of (or should that be got round to ?) it before. > >> Some of these points also apply to popen/pclose, but the FreeBSD already > >> seems to be correct although unnecessarily unportable. E.g., it handles > >> EINTR. > > >Out of interest, why does handling EINTR make it unportable? > > I meant that handling EINTR helped make it correct. The old signal > handling functions make it unportable. OK, I see what you mean now. Sorry for the misunderstanding. James -- James Raynard, Edinburgh, Scotland mail: jraynard@dial.pipex.com From owner-freebsd-hackers Fri Apr 26 17:47:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA14730 for hackers-outgoing; Fri, 26 Apr 1996 17:47:19 -0700 (PDT) Received: from vent.pipex.net (root@vent.pipex.net [158.43.128.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA14718 for ; Fri, 26 Apr 1996 17:47:17 -0700 (PDT) Received: from dial.pipex.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id BAA05933; Sat, 27 Apr 1996 01:46:50 +0100 Received: (from jraynard@localhost) by dial.pipex.com (8.6.12/8.6.12) id AAA01849; Sat, 27 Apr 1996 00:01:16 GMT Date: Sat, 27 Apr 1996 00:01:16 GMT From: James Raynard Message-Id: <199604270001.AAA01849@dial.pipex.com> To: julian@ref.tfs.com CC: bde@zeta.org.au, hackers@freebsd.org In-reply-to: <199604251802.LAA25761@ref.tfs.com> (julian@ref.tfs.com) Subject: Re: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Joerg said that the draft POSIX spec is on the (old) WC Internet Info > > cdrom. I haven't got it. > > I have actually only got the x/open XPG4 spec which says that it is POSIX2 > compliant Is this readily available anywhere? (I've got the CDROM on order - lots of other useful stuff like RFCs on there, apparently). > > It's less ambiguous than julianese :-). It completely specifies the > gee thanks :) Don't worry, I find your posts quite intelligible, which is more than you can say for most standards 8-) Cheers James -- James Raynard, Edinburgh, Scotland mail: jraynard@dial.pipex.com From owner-freebsd-hackers Fri Apr 26 17:47:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA14751 for hackers-outgoing; Fri, 26 Apr 1996 17:47:22 -0700 (PDT) Received: from vent.pipex.net (root@vent.pipex.net [158.43.128.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA14737 for ; Fri, 26 Apr 1996 17:47:20 -0700 (PDT) Received: from dial.pipex.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id BAA05937; Sat, 27 Apr 1996 01:46:54 +0100 Received: (from jraynard@localhost) by dial.pipex.com (8.6.12/8.6.12) id AAA01874; Sat, 27 Apr 1996 00:04:01 GMT Date: Sat, 27 Apr 1996 00:04:01 GMT From: James Raynard Message-Id: <199604270004.AAA01874@dial.pipex.com> To: bde@zeta.org.au CC: julian@ref.tfs.com, hackers@freebsd.org In-reply-to: <199604250044.KAA29532@godzilla.zeta.org.au> (message from Bruce Evans on Thu, 25 Apr 1996 10:44:43 +1000) Subject: Re: Flaws in system() implementation? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> If "command" is a null pointer, the system() function returns non-zero > >> only if a command processor is available. > > >OK (Out of interest, what kind of circumstances would result in a > >command processor not being available?) > > Non-POSIX ones. system((char *)NULL) is about the only aspect of system() > that is specified by ANSI. It returns 0 to tell you that system() is > completely useless on the current system :-). I see. 8-) > >> If a child process cannot be created, > >> or if the termination status of hte command interpretter cannot be obtained > >> system() returns -1 > >> and sets errno to indicate the error. > > >Doesn't that imply that system() should return -1 if fork() fails? > >(Forgive me if I'm being obtuse, I'm not very experienced at reading > >standardese). > > It's less ambiguous than julianese :-). It completely specifies the > return value after a fork failure, at least in my copy, which says > "shall return -1" instead of "returns -1". "shall" is standardese that > means that the implementation is non-conforming if it does anything > else. "should" would allow the implementation to screw up. OK, that was what I thought it meant - I was using "should" with its colloquial meaning rather than the standardese meaning (I did warn you I wasn't very experienced at this 8-) Thanks for answering all my questions, James -- James Raynard, Edinburgh, Scotland mail: jraynard@dial.pipex.com From owner-freebsd-hackers Fri Apr 26 17:48:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA14967 for hackers-outgoing; Fri, 26 Apr 1996 17:48:09 -0700 (PDT) Received: from gateway.net.hk (john@gateway.hk.linkage.net [202.76.7.50]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA14885 for ; Fri, 26 Apr 1996 17:48:04 -0700 (PDT) Received: (from john@localhost) by gateway.net.hk (8.7.4/8.7.3) id IAA12189; Sat, 27 Apr 1996 08:38:01 +0800 (HKT) Date: Sat, 27 Apr 1996 08:38:00 +0800 (HKT) From: John Beukema To: Robert Withrow cc: freebsd-hackers@FreeBSD.org Subject: Re: GNU binutils port In-Reply-To: <199604260126.VAA25217@spooky.rwwa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Robert Withrow wrote: > > >I really doubt sizeof(void *) != sizeof(??? *) any time soon. Besides it is not just the size of the pointer that must agree but how to increment it. *Char_ptr++ and *large_struct++ are different. jbeukema > > > > It happens every day, but not on the i386. > > Especially with function pointers, which I didn't realize until > recently even after decades of programming. Sigh. > > ----------------------------------------------------------------------------- > Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM > > > From owner-freebsd-hackers Fri Apr 26 18:33:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA16820 for hackers-outgoing; Fri, 26 Apr 1996 18:33:40 -0700 (PDT) Received: from jolt.eng.umd.edu (jolt.eng.umd.edu [129.2.102.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA16815 for ; Fri, 26 Apr 1996 18:33:38 -0700 (PDT) Received: from ginger.eng.umd.edu (ginger.eng.umd.edu [129.2.98.204]) by jolt.eng.umd.edu (8.7.5/8.7.3) with ESMTP id VAA27754; Fri, 26 Apr 1996 21:33:36 -0400 (EDT) Received: (from chuckr@localhost) by ginger.eng.umd.edu (8.7.5/8.7.3) id VAA22712; Fri, 26 Apr 1996 21:33:36 -0400 (EDT) Date: Fri, 26 Apr 1996 21:33:35 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: John Polstra cc: freebsd-hackers@freebsd.org Subject: Re: Help! I need info on pthreads. In-Reply-To: <4lj36e$hfb@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 23 Apr 1996, John Polstra wrote: > In article <199604230013.KAA18978@melb.werple.net.au>, > John Birrell wrote: > > > > I haven't looked for books on how to use pthreads. I'm from an OSF/1 > > environment where we used DEC's poor examples as a start. Their bookreader > > docs aren't too bad at describing the functions, but they are not good > > at describing how to design a threaded application. > > There's a really superb article on exactly that at: > > http://gatekeeper.dec.com/pub/DEC/SRC/research-reports/abstracts/src-rr-035.html John, I downloaded this one, as well as a couple others (great reference!) but I have a problem with this one in particular. For some reason, ghostview clips the last (rightmost) inch of text, no matter how I scroll this, or what papersize I use. Do you see this problem? Does anyone know of (even a junky) postscript to ascii converter, so I can at least read this paper? > > It's by Andrew D. Birrell. (Who's he, John, your long lost brother? :-) > > Incidentally, it is a technical report from DEC's Systems Research > Center. They have many excellent TRs on interesting topics. You can > find an index of them at: > > http://www.research.digital.com/SRC/publications/src-rr.html > > Almost all of them are available in Postscript form. They'll also mail > you paper copies and/or associated videos, for free. It's a great > service! ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-hackers Fri Apr 26 18:42:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA17414 for hackers-outgoing; Fri, 26 Apr 1996 18:42:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA17409 for ; Fri, 26 Apr 1996 18:42:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA28596; Fri, 26 Apr 1996 18:30:05 -0700 From: Terry Lambert Message-Id: <199604270130.SAA28596@phaeton.artisoft.com> Subject: Re: Flaws in system() implementation? To: jraynard@dial.pipex.com (James Raynard) Date: Fri, 26 Apr 1996 18:30:05 -0700 (MST) Cc: julian@ref.tfs.com, bde@zeta.org.au, hackers@FreeBSD.org In-Reply-To: <199604270001.AAA01849@dial.pipex.com> from "James Raynard" at Apr 27, 96 00:01:16 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I have actually only got the x/open XPG4 spec which says that it is POSIX2 > > compliant > > Is this readily available anywhere? (I've got the CDROM on order - > lots of other useful stuff like RFCs on there, apparently). ftp://ftp.dgii.com/pub/uiarchive Might have a copy... I saved most of UI's archive when UNIX International went under, and Digi International (formerly Digiboard) was kind enough to give it a home on the net. I know there is some advanced FS white papaers, some user asn system administration research, and DWARF and a draft copy of SPEC1170, among other things. 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 Apr 26 18:53:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA17939 for hackers-outgoing; Fri, 26 Apr 1996 18:53:30 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA17934 Fri, 26 Apr 1996 18:53:28 -0700 (PDT) Received: (from jmacd@localhost) by paris.CS.Berkeley.EDU (8.6.11/8.6.9) id SAA01303; Fri, 26 Apr 1996 18:53:26 -0700 Date: Fri, 26 Apr 1996 18:53:26 -0700 From: Josh MacDonald Message-Id: <199604270153.SAA01303@paris.CS.Berkeley.EDU> To: freebsd-doc@freebsd.org Subject: O_SYNC Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the open(2) man page, there is no mention of either O_FSYNC which I find on ULTRIX, or O_SYNC, which I seem to find everywhere else. Isn't O_SYNC the POSIX way to do things? Why does FreeBSD have O_FSYNC, and why isn't it documented? -josh From owner-freebsd-hackers Fri Apr 26 20:05:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA21681 for hackers-outgoing; Fri, 26 Apr 1996 20:05:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA21654 Fri, 26 Apr 1996 20:04:59 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA07041; Sat, 27 Apr 1996 12:58:55 +1000 Date: Sat, 27 Apr 1996 12:58:55 +1000 From: Bruce Evans Message-Id: <199604270258.MAA07041@godzilla.zeta.org.au> To: freebsd-doc@freebsd.org, jmacd@CS.Berkeley.EDU Subject: Re: O_SYNC Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Isn't O_SYNC the POSIX way to do things? Why does FreeBSD have >O_FSYNC, and why isn't it documented? POSIX.1 doesn't specify any way to sync files. Perhaps FreeBSD has O_FSYNC as a compatibility hack, and it isn't documented because it doesn't do anything. Bruce From owner-freebsd-hackers Sat Apr 27 01:00:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA04289 for hackers-outgoing; Sat, 27 Apr 1996 01:00:14 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA04271 for ; Sat, 27 Apr 1996 01:00:10 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id BAA03479 for ; Sat, 27 Apr 1996 01:00:07 -0700 Message-Id: <199604270800.BAA03479@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: hackers@freebsd.org Subject: locking user pages for dma access Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Apr 1996 01:00:06 -0700 From: "Amancio Hasty Jr." Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that scsi raw i/o must locked the user page space. Can anyone shed some light on this ? This is with respect to the mode which Jim is talking about in his e-mail. At any rate, tnks in advance ! Amancio ------- Forwarded Message Return-Path: james@miller.cs.uwm.edu Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id HAA00879 for ; Thu, 25 Apr 1996 07:10:20 -0700 Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id JAA19519; Thu, 25 Apr 1996 09:10:15 -0500 Date: Thu, 25 Apr 1996 09:10:15 -0500 From: Jim Lowe Message-Id: <199604251410.JAA19519@miller.cs.uwm.edu> To: hasty@rah.star-gate.com, tinguely@plains.nodak.edu Subject: Re: 30fps with vic? Cc: multimedia@freebsd.org > From: "Amancio Hasty Jr." > > My next question is: has anyone done a profile analysis on vic / h.261 to > see if vic's performance can be improved? > To answer to your question, no I have not done profiling of vic, but I have thought of ways to speed it and other algorithms like it up by making the device drivers we support for video capture a little smarter. One way vic/h.261 and other algorithms like it could be improved would be to eliminate the copying of data. I have thought of adding a ``vic'' capture mode to the meteor device driver to speed things up. Basically vic uses a buffer that looks like: xxxxxxxxxx .......... .......... .......... .......... .......... .......... xxxxxxxxxx The ``.''s are the actual video data and the ``x''s are scratch buffers for the encoding algorithm (h.261 or whatever). Vic's internal buffer is rows * cols + 2 * cols (see grabber.cc for details). If one used synchronous capture mode and could specify where the video capture driver was suppose to put the data, then one could create a buffer for vic, let the driver do the work (via dma) and avoid the copy from the mmaped area to a vic work area. This would save a fair amount of coping time and speed up the encoding rate. The time you would save is the time it takes to copy a 358x244x2x30fps from one memory location to another. Since the memory bandwidth of a Triton MB is about 40Meg/Sec (mem to mem), this copy alone would take up about 1/8 of total memory bandwidth. If you were going to create a user memory encoding capture mode, then you would want something that does 4:1:1 or 4:2:2 and dma's the data directly from the card into user space. A capture mode like this would come in handy for mpeg and jpeg encoders as well as a TV player :-). There is a bug with the Philips SAA7116 chip that would not allow range checking to work if you wanted to dma directly into user space. Also, the user memory would have to be locked into an actual physical location all the time. I am not certain if there is a FreeBSD kernel VM function that will allow one to do this. In any case, the source code is available :-). -Jim ------- End of Forwarded Message From owner-freebsd-hackers Sat Apr 27 11:37:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA28990 for hackers-outgoing; Sat, 27 Apr 1996 11:37:45 -0700 (PDT) Received: from zygorthian-space-raiders.MIT.EDU (ZYGORTHIAN-SPACE-RAIDERS.MIT.EDU [18.70.0.61]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA28970 Sat, 27 Apr 1996 11:37:39 -0700 (PDT) Received: (from mycroft@localhost) by zygorthian-space-raiders.MIT.EDU (8.7.4/8.6.11) id OAA10935; Sat, 27 Apr 1996 14:37:27 -0400 (EDT) To: "Jordan K. Hubbard" Cc: sef@freebsd.org, hackers@freebsd.org Subject: Re: Something fishy with our PT_ATTACH code! References: <29493.830512651@time.cdrom.com> From: mycroft@mit.edu (Charles M. Hannum) Date: 27 Apr 1996 14:37:24 -0400 In-Reply-To: "Jordan K. Hubbard"'s message of Fri, 26 Apr 1996 02:57:31 -0700 Message-ID: Lines: 25 X-Mailer: September Gnus v0.78/Emacs 19.30 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" writes: > > Start cat, attach cat from another tty with gdb, watch cat go to > sleep, detach cat in gdb and watch it return to its previous > un-stopped state. Yes; that's correct. One of the problems here is that PT_ATTACH sends a SIGSTOP to the process, expecting it to be trapped by the debugger, but it accidentally gets passed through when the process is resumed. In general, the signal handling in Sean's ptrace(2) implementation is fairly broken. Also, the only difference between PT_CONTINUE and PT_DETACH should be that the latter gives the process back to its original parent first (and turns off P_TRACED and P_WAITED, of course). In particular, PT_DETACH is allowed to specify an address and signal to continue with. You may want to look at the implementation in NetBSD, in which I've fixed these problems (and others). From owner-freebsd-hackers Sat Apr 27 12:12:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA00780 for hackers-outgoing; Sat, 27 Apr 1996 12:12:10 -0700 (PDT) Received: from hda.com (ip31-max1-fitch.zipnet.net [199.232.245.31]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA00774 Sat, 27 Apr 1996 12:12:07 -0700 (PDT) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id PAA09603; Sat, 27 Apr 1996 15:12:47 -0400 From: Peter Dufault Message-Id: <199604271912.PAA09603@hda.com> Subject: Re: O_SYNC To: bde@zeta.org.au (Bruce Evans) Date: Sat, 27 Apr 1996 15:12:46 -0400 (EDT) Cc: freebsd-doc@FreeBSD.org, jmacd@CS.Berkeley.EDU, freebsd-hackers@FreeBSD.org In-Reply-To: <199604270258.MAA07041@godzilla.zeta.org.au> from "Bruce Evans" at Apr 27, 96 12:58:55 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > >Isn't O_SYNC the POSIX way to do things? Why does FreeBSD have > >O_FSYNC, and why isn't it documented? > > POSIX.1 doesn't specify any way to sync files. Perhaps FreeBSD > has O_FSYNC as a compatibility hack, and it isn't documented because > it doesn't do anything. The new copy of POSIX.1 (P1003.1b-1993) adds O_DSYNC, O_RSYNC and O_SYNC in the open call. O_DSYNC versus O_SYNC permits data-only integrity versus full file info integrity (access stamps, etc). I haven't spent the time to puzzle out exactly what O_RSYNC means - that once you read it it better also be on the disk? There is a feature test macro "_POSIX_SYNCHRONIZED_IO" that has to be defined for these to be present. Anyone working off a new spec better keep an eye out for the change bars- I didn't realize this was new until this mail. -- Temporarily via "hdalog@zipnet.net"... Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-hackers Sat Apr 27 13:30:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05717 for hackers-outgoing; Sat, 27 Apr 1996 13:30:47 -0700 (PDT) Received: from suw3svr01.hisd.harris.com (suw3svr01.hisd.harris.com [158.147.19.67]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05712 for ; Sat, 27 Apr 1996 13:30:44 -0700 (PDT) Received: from suw2k.hisd.harris.com by suw3svr01.hisd.harris.com (SMI-8.6/SMI-SVR4) id QAA10360; Sat, 27 Apr 1996 16:27:33 -0400 Received: by suw2k.hisd.harris.com (4.1/SMI-4.1) id AA15610; Sat, 27 Apr 96 16:27:13 EDT Date: Sat, 27 Apr 96 16:27:13 EDT From: jleppek@suw2k.hisd.harris.com (James Leppek) Message-Id: <9604272027.AA15610@suw2k.hisd.harris.com> To: freebsd-hackers@freefall.FreeBSD.org Subject: posix timespec vs timeval Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk What are the correct member names in struct timespec? I just received another update of the MIT posix threads an they now use timespec but have the members as tv_sec and tv_nsec. In freebsd it is ts_sec and ts_nsec (makes more sense but that doesn't mean its right :-) )? I have got to change something so I was hoping someone would know the correct spec. Thanks Jim Leppek From owner-freebsd-hackers Sat Apr 27 19:36:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA27168 for hackers-outgoing; Sat, 27 Apr 1996 19:36:36 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA27127 for ; Sat, 27 Apr 1996 19:36:30 -0700 (PDT) Received: from cimaxp1.UUCP (uucp@localhost) by melb.werple.net.au (8.7.5/8.7.3) with UUCP id LAA04581 for mira!freefall.freebsd.org!freebsd-hackers; Sun, 28 Apr 1996 11:50:43 +1000 (EST) Message-Id: <199604280150.LAA04581@melb.werple.net.au> Received: by cimaxp1.cimlogic.com.au; (5.65/1.1.8.2/10Sep95-0953AM) id AA31484; Sun, 28 Apr 1996 11:50:56 +1000 From: John Birrell Subject: Re: posix timespec vs timeval To: suw2k.hisd.harris.com!jleppek@melb.werple.net.au (James Leppek) Date: Sun, 28 Apr 1996 11:50:56 +1000 (EST) Cc: freefall.freebsd.org!freebsd-hackers@melb.werple.net.au In-Reply-To: <9604272027.AA15610@suw2k.hisd.harris.com> from "James Leppek" at Apr 27, 96 04:27:13 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > What are the correct member names in struct timespec? time_t tv_sec long tv_nsec > I just received another update of the MIT posix threads an they > now use timespec but have the members as tv_sec and tv_nsec. > In freebsd it is ts_sec and ts_nsec (makes more sense but that doesn't > mean its right :-) )? FreeBSD is *WRONG*. I find #ifdef'ing things for FreeBSD really annoying. At least NetBSD made the change when it was pointed out to them... > I have got to change something so I was hoping someone > would know the correct spec. > > Thanks > Jim Leppek > -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Sat Apr 27 21:10:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA03073 for hackers-outgoing; Sat, 27 Apr 1996 21:10:33 -0700 (PDT) Received: from nike.efn.org (gurney_j@garcia.efn.org [198.68.17.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA03067 for ; Sat, 27 Apr 1996 21:10:30 -0700 (PDT) Received: (from gurney_j@localhost) by nike.efn.org (8.7.5/8.7.3) id VAA15580; Sat, 27 Apr 1996 21:13:29 -0700 (PDT) Date: Sat, 27 Apr 1996 21:13:28 -0700 (PDT) From: John-Mark Gurney Reply-To: John-Mark Gurney To: FreeBSD Hackers Subject: double fault upon running gzip binary... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well... I'm running FreeBSD 2.2-960323-SNAP on my Toshiba T1960CS notebook, 486/50dx2... I have pseudo-device gzip # Exec gzipped a.out's compiled into my kernel for my notebook plus pccard stuff from 0414... I would run tcsh gzipped under multiuser mode and it would just reboot.. no warning or anything.. imediate reboot... so I decided to run it under single user mode and got: Fatal double fault: eip = 0xf018c479 esp = 0xefbfdff8 ebp = 0xefbfe094 panic: double fault when I ran it... the machine has 12 megs of ram... the pcmcia control is an Intel 82365... plus I have nep0 driver compiled in... it has a 1.0 APM BIOS and Slow Idling CPU is disabled... my kernel config file is: machine "i386" cpu "I486_CPU" ident note maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=8" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG options LAPTOP options NEPPMHACK config kernel root on wd0 swap on wd0 and wd1 and sd0 and sd1 and vn0 dumps on wd0 controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 controller crd0 device pcic0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM3" tty irq 5 vector siointr device sio4 at isa? port "IO_COM3" tty irq 5 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device nep0 at isa? port 0x300 net irq 10 vector nepintr device pca0 at isa? tty device apm0 at isa? pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pif pseudo-device sl 1 pseudo-device ppp 1 pseudo-device pty 16 pseudo-device speaker pseudo-device gzip # Exec gzipped a.out's pseudo-device vn pseudo-device tun 1 I'm not sure how to procede from here... I have in the past (on for my other machine) tried to compile in KGDB, DDB, and DDB_UNATTENDED but the kernel didn't compile unless I removed those options... Thanks for the help... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)