From owner-freebsd-hackers Sun Aug 30 02:32:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01525 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 02:32:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freedomnet.com (freedomnet.com [198.240.104.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01516 for ; Sun, 30 Aug 1998 02:32:02 -0700 (PDT) (envelope-from kbyanc@freedomnet.com) Received: (from kbyanc@localhost) by freedomnet.com (8.8.7/8.8.7/antispam) id FAA11055; Sun, 30 Aug 1998 05:26:20 -0400 (EDT) X-Envelope-To: freebsd-hackers@FreeBSD.ORG Date: Sun, 30 Aug 1998 05:26:19 -0400 (EDT) From: Kelly Yancey To: Joel Ray Holveck cc: freebsd-hackers@FreeBSD.ORG Subject: Re: determining an X window ID? In-Reply-To: <199808300355.WAA05971@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Aug 1998, Joel Ray Holveck wrote: > > I have written a fairly short shell script to launch xmcd which first > > checks to see if any other cd player is already running and if so, does > > not launch another instance of xmcd (for when I click on the wrong thing > > :) ) > > How does it do this check? > The old fashioned way...it checks for each of them in the output of ps :) Actually it's not too bad. I broke it into two loops: the first checks for all the X-based cd players (xmcd, xcdplayer, etc), with the hope that one day I'll be able to set focus on them. And the second checks for command-line cd players (cdplay, cda, etc.)...I don't know what I could do if they are running, but it definately isn't to try and start another cd player :). Below is a copy of the script. Kelly Yancey ~kbyanc@freedomnet.com~ #!/bin/sh # This is a script to start xmcd sanely... # There is no advantage to running multiple copies of xmcd (even if you # have multiple CD-ROM's and multiple speakers, you only have one set of # ears. This script checks to see if xmcd is already running and if not, # then starts a new instance of it. It also checks for cda (the # command-line version of xmcd). Ideally, one day it will check for more # cd players too. # # - kbyanc, 8/28/98 # first, we'll check for X-based CD-players with the hopes that one day we # will be able to set focus to the other CD-player for check in "xmcd" "workman" "xcdplayer" do if [ `ps -cawx | grep -c -w $check` = 1 ]; then exit; fi done # check for command-line CD-players... for check in "cda" "cdplay" do if [ `ps -cawx | grep -c -w $check` = 1 ]; then exit; fi done xmcd $@ & To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 04:17:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14615 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 04:17:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14610 for ; Sun, 30 Aug 1998 04:17:53 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id UAA06445; Sun, 30 Aug 1998 20:16:27 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id UAA04968; Sun, 30 Aug 1998 20:16:27 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id UAA21238; Sun, 30 Aug 1998 20:10:35 +0900 (JST) To: mike@smith.net.au Cc: max@wide.ad.jp, freebsd-hackers@FreeBSD.ORG Cc: max@wide.ad.jp Subject: Re: question From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Sat, 29 Aug 1998 22:33:18 +0000" <199808292233.WAA10825@word.smith.net.au> References: <199808292233.WAA10825@word.smith.net.au> X-Mailer: Mew version 1.92.4 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980830201035X.masafumi@aslm.rim.or.jp> Date: Sun, 30 Aug 1998 20:10:35 +0900 X-Dispatcher: imput version 971024 Lines: 17 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Down towards the bottom of the doMFSKERN target, the boot.help > file is copied into the boot images. Just do > @echo \07\07 >> ${RD}/boot.${FSIMAGE}/boot.help Ok, thanks. Since echo doesn't handle \07 unless I put literal ^G, I'll use printf \a instead, though. > (And if you were reading that entire makefile with a braille > screen reader, or a speech synth, I think you deserve some > serious compliments.) Well, looking at it using Braille output isn't too difficult, but I wouldn't care to use speech output to do the task. :) Cheers, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 04:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA15447 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 04:32:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA15415 for ; Sun, 30 Aug 1998 04:31:25 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from (ragnet.demon.co.uk) [158.152.46.40] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0zD5ge-0007Cy-00; Sun, 30 Aug 1998 11:30:25 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0zD51s-00068x-00; Sun, 30 Aug 1998 11:48:16 +0100 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 30 Aug 1998 11:48:15 +0100 (BST) From: Duncan Barclay To: Alex Belits Subject: Re: Help with passing fd on FreeBSD Cc: brhall@timing.com, freebsd-hackers@FreeBSD.ORG, Craig Anderson , Luigi Rizzo Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Aug-98 Alex Belits wrote: > On Fri, 28 Aug 1998, Luigi Rizzo wrote: > >> still, this looks to me one of the most obscure interfaces in the OS. >> Does any real application use that ? > > fhttpd uses it (and this is how mysterious kern/4345 was found). > If I remmeber right the portal file system uses it too. The user land process uses a socket to pass the open'd fd back into the kernel. Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 06:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21218 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 06:38:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from kmtts.kuban.ru (kmtts.kuban.ru [194.87.150.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA21203 for ; Sun, 30 Aug 1998 06:38:37 -0700 (PDT) (envelope-from sky.mednet.ru!phkras.mednet.ru!oma@kmtts.kuban.ru) Received: from pp-11.kuban.ru [195.161.47.234] by kmtts.kuban.ru with ESMTP id RAA09544; (8.6.12/K) Sun, 30 Aug 1998 17:30:41 +0400 Received: from uucp@localhost by sky.mednet.ru with UUCP id RAA00981; (8.8.5/K) Sun, 30 Aug 1998 17:30:05 +0400 (MSD) Received: by phkras.mednet.ru id RAA02269; (8.8.5/vak/1.8e) Sun, 30 Aug 1998 17:27:47 +0400 (MSD) To: freebsd-hackers@FreeBSD.ORG Message-ID: Organization: GOMU,KMIVC_Krasnodar Ltd From: "Michael-Ostapenko" Date: Sun, 30 Aug 98 17:27:47 +0400 X-Mailer: BML [UNIX Beauty Mail v.1.39] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From postmaster Sun Aug 30 17:26:07 1998 Status: R Dear sirs! We have the following problem with tuning PPP server under FreeBSD 2.2.2 for "Recieving incoming PPP connections" mode - client cannot connect using PPP. File PPP.TUN0.LOG contains the following line: ioctl.error (inappropriate ioctl for device)! Could we have more information about the tuning the PPP server. Sincerily, Michael Ostapenko Network Engineer, IVC GOMU, Krasnodar, Russia +7 (8612) 67-62-47 +7 (8612) 67-56-96 (fax/voice) e-mail: oma@phkras.mednet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 06:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22300 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 06:50:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from a486n1.znh.org (dialup3.gaffaneys.com [208.155.161.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22294 for ; Sun, 30 Aug 1998 06:50:13 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by a486n1.znh.org (8.9.1/8.9.1) id NAA04190; Sun, 30 Aug 1998 13:49:18 GMT (envelope-from zach) Message-ID: <19980830084917.A4163@znh.org.> Date: Sun, 30 Aug 1998 08:49:17 -0500 From: Zach Heilig To: Kelly Yancey , Joel Ray Holveck Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: determining an X window ID? References: <199808300355.WAA05971@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kelly Yancey on Sun, Aug 30, 1998 at 05:26:19AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 30, 1998 at 05:26:19AM -0400, Kelly Yancey wrote: > The old fashioned way...it checks for each of them in the output of ps > :) > Actually it's not too bad. I broke it into two loops: the first checks > for all the X-based cd players (xmcd, xcdplayer, etc), with the hope that > one day I'll be able to set focus on them. And the second checks for > command-line cd players (cdplay, cda, etc.)...I don't know what I could > do if they are running, but it definately isn't to try and start another > cd player :). You could use 'egrep' instead of a for loop and grep: #!/bin/sh ps -cawx | egrep -w "xmcd|workman|xcdplayer|cda|cdplay" > /dev/null 2>&1 if [ $? -ne 0 ]; then xmcd $@ & fi /usr/sbin/cdcontrol can play cd's as well. -- Zach Heilig -- zach@gaffaneys.com Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 08:03:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27548 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 08:03:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27542 for ; Sun, 30 Aug 1998 08:03:48 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-80.camalott.com [208.229.74.80]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id KAA08844; Sun, 30 Aug 1998 10:04:26 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id KAA07242; Sun, 30 Aug 1998 10:02:34 -0500 (CDT) (envelope-from joelh) Date: Sun, 30 Aug 1998 10:02:34 -0500 (CDT) Message-Id: <199808301502.KAA07242@detlev.UUCP> To: mike@smith.net.au CC: avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG In-reply-to: <199808292159.VAA10620@word.smith.net.au> (message from Mike Smith on Sat, 29 Aug 1998 21:59:08 +0000) Subject: Re: duplicating cd's with dd. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808292159.VAA10620@word.smith.net.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> does anyone know if there are "preferred" parameters for using dd to >> copy cd's with ? > You can improve performance slightly with a larger block size (fewer > syscalls), but that's about it. I use 64K as an arbitrary figure; it > seems to run about as fast as the drive will go. I wrote a small script that tests each blocksize (with the laser off), and plots the number of blocks transferred before a buffer underrun, and the BPS rate. Since this is a slow system (Am486DX/4-100, AHA-1542, CDD-2600), then the timing is quite critical to me, and most block sizes would cause an underrun. I got a pretty clear pattern, indicating the optimal blocksize as 32k. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 08:08:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27967 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 08:08:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27962 for ; Sun, 30 Aug 1998 08:08:07 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id LAA05097; Sun, 30 Aug 1998 11:04:54 -0400 (EDT) Date: Sun, 30 Aug 1998 11:04:53 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Alex Belits cc: Craig Anderson , freebsd-hackers@FreeBSD.ORG, brhall@timing.com Subject: Re: Help with passing fd on FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a set of patches that try to clean up the fd-passing behavior in 3.0-CURRENT. I originally wrote them to allow the passing of kernel authorization tokens (http://www.watson.org/fbsd-hardening/tokens/). These patches allow lkm's to hook the externalize, internalize, and gc functions. However, in the process of writing this, I have fixed at least a few potential problems. A few were just coding issues (like some underlying assumptions about the size of mbufs and so on). I have not fixed the bug described in the BSD4.4 book (sorry, don't have it with me so don't have a page number) w.r.t. garbage collecting fd's in listening sockets. Passing tokens seems to work quite well for me. Is the mbuf problem you reported fixable by adding a sleep waiting for an mbuf? On Sat, 29 Aug 1998, Alex Belits wrote: > On Fri, 28 Aug 1998, Craig Anderson wrote: > > > Can someone give me pointers on passing open file descriptors on FreeBSD? > > This is covered in W. Richard Stevens Advanced programming book, but > > See R. Stevens "TCP/IP Illustrated", volume 3, chapter 18.3 > or R. Stevens "Unix Network Programming", second edition (1997), volume 1, > chapter 14.7. > > Previous books describe 4.3BSD and SVR4 fd passing that is more than > slightly different. > > > the structs in FreeBSD are slightly different, and I've never done this. > > In FreeBSD CMSG_DATA(cm) macro is the equivalent to cm->cmsg_data that is > commented out in include files in 4.4BSD-derived, but exists in > other compatible systems. > > Beware of the known bug in FreeBSD kernel (PR kern/4345). > > -- > Alex > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 08:11:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28298 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 08:11:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28293 for ; Sun, 30 Aug 1998 08:11:28 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-80.camalott.com [208.229.74.80]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id KAA09024; Sun, 30 Aug 1998 10:09:08 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id KAA07248; Sun, 30 Aug 1998 10:07:16 -0500 (CDT) (envelope-from joelh) Date: Sun, 30 Aug 1998 10:07:16 -0500 (CDT) Message-Id: <199808301507.KAA07248@detlev.UUCP> To: abelits@phobos.illtel.denver.co.us CC: chanders@timing.com, freebsd-hackers@FreeBSD.ORG, brhall@timing.com In-reply-to: (message from Alex Belits on Sat, 29 Aug 1998 22:24:42 -0700 (PDT)) Subject: Re: Help with passing fd on FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> the structs in FreeBSD are slightly different, and I've never done >> this. > In FreeBSD CMSG_DATA(cm) macro is the equivalent to cm->cmsg_data > that is commented out in include files in 4.4BSD-derived, but exists > in other compatible systems. For instance, I had to do the following in Emacs 20.4 (I think mostly for Linux, but I don't remember now): (configure defines HAVE_SCM_RIGHTS if SOL_SOCKET and SCM_RIGHTS are defined; HAVE_CMSG_DATA if said macro is defined, and CMSG_HAS_CMSG_DATA if cmsg_data is a structure member.) #ifdef HAVE_SCM_RIGHTS # ifndef HAVE_CMSG_DATA # ifdef CMSG_HAS_CMSG_DATA # define CMSG_DATA(x) ((x)->cmsg_data) # else # define CMSG_DATA(x) ((char*)(x)+sizeof(*(x))) # endif # endif #endif Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 11:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20646 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 11:47:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gateway.whtech.com (user33.usr1.accesscom.com [205.226.158.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20627 for ; Sun, 30 Aug 1998 11:47:28 -0700 (PDT) (envelope-from don@whtech.com) Received: from digerati (digerati.whtech.com [10.1.0.2]) by gateway.whtech.com (8.8.7/8.8.7) with SMTP id LAA18818 for ; Sun, 30 Aug 1998 11:52:58 -0700 (PDT) (envelope-from don@whtech.com) From: "Don O'Neil" To: Subject: SAR Like preformance monitor? Date: Sun, 30 Aug 1998 11:47:49 -0700 Message-ID: <000f01bdd446$afb64840$0200010a@digerati.whtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a performance monitor for BSD similar to SAR on Solaris/Irix/HP-UX? If not... are there sources for SAR out there that can be built for FreeBSD? What do you use for monitoring performance under FBSD? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 13:50:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04249 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 13:50:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04216; Sun, 30 Aug 1998 13:49:52 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA07446; Sun, 30 Aug 1998 22:52:49 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 30 Aug 1998 22:52:49 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Chuck Robey cc: FreeBSD-Hackers@FreeBSD.ORG, FreeBSD Ports Team Subject: Re: ButtFace In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Chuck Robey wrote: > I'm still laughing at this, but it's real. > > I was trying to get a package called mpsql to port, and couldn't get it > to link. It kept on wanting a symbol called _XmCreatePixmapPushButton, > and I couldn't find what library it was in. > > Finally found it in /usr/X11R6/lib/libButtFace.a. Nearly fell over > laughing at the name. > > That's the one, all right, but in trying to figure out what mpsql wants > to depend on, I need to find out where this ButtFace thing came from. > Its on a pixmap thing (not from the xpm port), and I just can't locate > it. Anyone remember this odd fella? Isn't it something related to Motif? This _Xm* prefix... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 14:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09921 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 14:34:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09880; Sun, 30 Aug 1998 14:34:27 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id QAA03752; Sun, 30 Aug 1998 16:31:43 -0400 (EDT) Date: Sun, 30 Aug 1998 16:31:42 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Andrzej Bialecki cc: FreeBSD-Hackers@FreeBSD.ORG, FreeBSD Ports Team Subject: Re: ButtFace In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Aug 1998, Andrzej Bialecki wrote: > > On Fri, 28 Aug 1998, Chuck Robey wrote: > > > I'm still laughing at this, but it's real. > > > > I was trying to get a package called mpsql to port, and couldn't get it > > to link. It kept on wanting a symbol called _XmCreatePixmapPushButton, > > and I couldn't find what library it was in. > > > > Finally found it in /usr/X11R6/lib/libButtFace.a. Nearly fell over > > laughing at the name. > > > > That's the one, all right, but in trying to figure out what mpsql wants > > to depend on, I need to find out where this ButtFace thing came from. > > Its on a pixmap thing (not from the xpm port), and I just can't locate > > it. Anyone remember this odd fella? > > Isn't it something related to Motif? This _Xm* prefix... You're a little tardy. Tim Vanderhoek found it in libhelp (it's a port, x11-toolkits/libhelp). I have to admit _I_ first guessed Motif. > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 30 23:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00590 for freebsd-hackers-outgoing; Sun, 30 Aug 1998 23:25:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA00582 for ; Sun, 30 Aug 1998 23:25:25 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zDNO0-00064M-00; Mon, 31 Aug 1998 00:24:20 -0600 Received: (from imp@localhost) by harmony.village.org (8.9.1/8.8.3) id AAA01070 for hackers@freebsd.org; Mon, 31 Aug 1998 00:23:26 -0600 (MDT) Date: Mon, 31 Aug 1998 00:23:26 -0600 (MDT) From: Warner Losh Message-Id: <199808310623.AAA01070@harmony.village.org> To: hackers@FreeBSD.ORG Subject: 64k physio limit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to get a larger I/O to happen than 64k? I have a tape drive that would be happiest if I could do 256kish writes to it at a time, rather than only 64k. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 00:37:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07777 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 00:37:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07759 for ; Mon, 31 Aug 1998 00:37:31 -0700 (PDT) (envelope-from dirk.vangulik@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with ESMTP id JAA28600; Mon, 31 Aug 1998 09:33:07 +0200 (MET DST) Received: (from dirkx@localhost) by elpc36.jrc.it (8.8.8/8.8.7) id JAA09325; Mon, 31 Aug 1998 09:34:15 +0200 (CEST) (envelope-from dirkx) Date: Mon, 31 Aug 1998 09:34:15 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@elpc36.jrc.it To: Joel Ray Holveck cc: dirk.vangulik@jrc.it, chanders@timing.com, wpaul@skynet.ctr.columbia.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Help with passing fd on FreeBSD In-Reply-To: <199808300412.XAA06019@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Aug 1998, Joel Ray Holveck wrote: > > I struggeled with the same, in particular as the most recent book of > > Stevens uses the API as described in RFC2292. And two of the macro's > > are not quite part of socket.h. (why is this actually?) > Well, my best guess is that the RFC (entitled "Advanced Sockets API > for IPv6") is based on IPv6, which we have not integrated into > -current. (What's the story on that, anyway?) > The feature I thought you were referring to is passing an fd through a > local domain socket, not an inet socket. To the best of my knowledge, > BSD does not support the latter operation. (It would be nontrivial.) No sorry; it was just that the RFC describes a more general Socket API which covers more than just inet connections. Most, but not all of the proposed CMSG_ macro's are in socket.h on BSD. For people, like me, this means that we cannod blindly follow the guidance and advice; and worst of all, that we cannot copy the examples without thinking. :-) It should be noted that the CMSG_SPACE() and CMSG_LEN() macro's amounth to exactly nothing really when a file descriptor is passed. Dw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 02:12:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16290 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 02:12:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16284 for ; Mon, 31 Aug 1998 02:12:25 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id CAA03894 for ; Mon, 31 Aug 1998 02:12:18 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id LAA04109 for freebsd-hackers@freefall.cdrom.com; Mon, 31 Aug 1998 11:11:03 +0200 (MEST) (envelope-from kuku) Date: Mon, 31 Aug 1998 11:11:03 +0200 (MEST) From: Christoph Kukulies Message-Id: <199808310911.LAA04109@gilberto.physik.RWTH-Aachen.DE> To: freebsd-hackers@freefall.cdrom.com Subject: 2.2.7 install overwrites bootsect Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I gave a 2.2.7 dist kit to a (sceptic?) colleague. I was hoping him coming back as a missionaire. Grrm, he told me, FreeBSD install had overwritten his bootsector (NT) although he explicitly clicked the option that was promising to leave the bootsector intact. Well, I gave him the tip to reinstall the NT bootsector from the NT repair disk or otherwise use FDISK/MBR + some freeware utility called bootpart or something IIRC. Anyway, not a good start to gain FreeBSD followers :-( -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 02:27:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18533 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 02:27:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18526 for ; Mon, 31 Aug 1998 02:27:34 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id FAA13727; Mon, 31 Aug 1998 05:26:35 -0400 (EDT) (envelope-from luoqi) Date: Mon, 31 Aug 1998 05:26:35 -0400 (EDT) From: Luoqi Chen Message-Id: <199808310926.FAA13727@lor.watermarkgroup.com> To: hackers@FreeBSD.ORG, imp@village.org Subject: Re: 64k physio limit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any way to get a larger I/O to happen than 64k? I have a tape > drive that would be happiest if I could do 256kish writes to it at a time, > rather than only 64k. > > Warner > Set the device driver's cdevsw:d_maxio to 256k? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 03:16:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24034 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 03:16:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.224.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24028 for ; Mon, 31 Aug 1998 03:16:28 -0700 (PDT) (envelope-from avalon@coombs.anu.edu.au) Message-Id: <199808311016.DAA24028@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA253598523; Mon, 31 Aug 1998 20:15:23 +1000 From: Darren Reed Subject: TCP performance. To: hackers@FreeBSD.ORG Date: Mon, 31 Aug 1998 20:15:23 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, FreeBSD TCP performance sucks or it does some things which can make it suck badly. >From simple observations (hub leds, ftp's meter), ftp'ing from a laptop (3c589d) running 2.2.6 to SunOS4 (LX) is considerably worse than in the other direction. Although I do suspect the 3c589d (or its driver - zp ?) do not handle ethernet collisions at all in a good way to be a possible cause. I've never known ethernet ftp performance so bad as with the equipment just mentioned. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 03:35:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25881 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 03:35:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sol.telerjcelular.com.br ([200.222.4.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA25873 for ; Mon, 31 Aug 1998 03:35:30 -0700 (PDT) (envelope-from fabiok@telerjcelular.com.br) Received: by sol.telerjcelular.com.br; (5.65v3.2/1.3/10May95) id AA06313; Mon, 31 Aug 1998 07:33:23 -0300 Received: from somewhere by smtpxd Message-Id: <35EA7BFE.B44AA0FB@telerjcelular.com.br> Date: Mon, 31 Aug 1998 07:33:34 -0300 From: Fabio Augusto Koreeda X-Mailer: Mozilla 4.03 [pt] (WinNT; I) Mime-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: (sem assunto) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 04:30:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05008 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 04:30:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04996 for ; Mon, 31 Aug 1998 04:30:51 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id NAA00798 for ; Mon, 31 Aug 1998 13:29:47 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id NAA14923 for ; Mon, 31 Aug 1998 13:29:47 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id NAA05786 for ; Mon, 31 Aug 1998 13:29:44 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808311129.NAA02414@internal> Subject: Re: TCP performance. In-Reply-To: <199808311016.DAA24028@hub.freebsd.org> from Darren Reed at "Aug 31, 98 08:15:23 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Mon, 31 Aug 1998 13:29:39 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, FreeBSD TCP performance sucks or it does some things which can > make it suck badly. > > >From simple observations (hub leds, ftp's meter), ftp'ing from a laptop > (3c589d) running 2.2.6 to SunOS4 (LX) is considerably worse than in the > other direction. Although I do suspect the 3c589d (or its driver - zp ?) I get about 1MB in both directions on 10Base2 and about 9MB on a 100BaseTx. I am using Intel Etherexpress cards so I assume that it only can be the driver for your card or the card or your hardware. > do not handle ethernet collisions at all in a good way to be a possible > cause. I've never known ethernet ftp performance so bad as with the > equipment just mentioned. I have never seen better TCP performance than by using FreeBSD. So it really might be something depending on your hardware. I will have to setup a FreeBSD laptop with a 3c589 (:-() in about three weeks so maybe then I will have more infos. > > Darren -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 05:20:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10822 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 05:20:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10796 for ; Mon, 31 Aug 1998 05:20:35 -0700 (PDT) (envelope-from rvb@sicily.odyssey.cs.cmu.edu) From: rvb@sicily.odyssey.cs.cmu.edu Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id FAA10864 for ; Mon, 31 Aug 1998 05:20:27 -0700 (PDT) To: Christoph Kukulies Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.7 install overwrites bootsect References: <199808310911.LAA04109@gilberto.physik.RWTH-Aachen.DE> Date: 31 Aug 1998 08:18:54 -0400 In-Reply-To: Christoph Kukulies's message of Mon, 31 Aug 1998 11:11:03 +0200 (MEST) Message-ID: Lines: 13 X-Mailer: Gnus v5.4.46/Emacs 19.34 Source-Info: Sender is really rvb@sicily.odyssey.cs.cmu.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Kukulies writes: > I gave a 2.2.7 dist kit to a (sceptic?) colleague. I was hoping > him coming back as a missionaire. Grrm, he told me, FreeBSD install > had overwritten his bootsector (NT) although he explicitly clicked > the option that was promising to leave the bootsector intact. I tend to make this mistake too. You move to the line to say leave the bootsectors alone. But you must then type space to move the "X" to that line. Otherwise, it will take the default -- install the FreeBSD boot. Maybe there should be no X on that menu at all? ... But then you get no boot, but if you set the active bit this may be good enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 06:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18758 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 06:25:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18552 for ; Mon, 31 Aug 1998 06:23:42 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id QAA20826 for hackers@FreeBSD.org; Mon, 31 Aug 1998 16:22:29 +0300 (EEST) (envelope-from ru) Message-ID: <19980831162228.A20318@ucb.crimea.ua> Date: Mon, 31 Aug 1998 16:22:28 +0300 From: Ruslan Ermilov To: hackers@FreeBSD.ORG Subject: PMTU discovery, Firewalls and Sendmail Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Recently I had problems receiving mail from hub.FreeBSD.org. The logs were full of sendmail's timeout errors. Now I finally discovered the problem and want to share my experience with you ;-) As you know (if you don't, please refer to RFC1191) today almost every host uses ``Path MTU Discovery''. The ICMP participates in it too. What happens if some router along the path is blocking ICMP? Let's start from an example. As you know, hub.FreeBSD.org is a mailhub that serves all mailing lists dedicated to FreeBSD. I'll call it just HUB, OK? Somewhere on CRL.NET (the Walnut Creek CDROM's ISP) along the path from my mail machine to the HUB the ICMP blocked. This was made to protect HUB from ICMP DoS attacks. Well, HUB is trying to send mail to me . The host route to RELAY.UCB.CRIMEA.UA is cloned, and its MTU (by default) is equal to 1500. More exactly, it will be equal to MTU of its first hop. In case of Ethernet it is equal to 1500. All following SMTP packets have the DF flag set. While the packet size is small (at EHLO, MAIL and RCPT stages) all goes smooth. After that, the message itself is transferred at DATA stage. The size of TCP packets increases. Somewhere (I don't know exactly where) along the path from HUB.FREEBSD.ORG to RELAY.UCB.CRIMEA.UA a router can't forward the packet due to its lower next-hop MTU (at least, my site is connected to the Internet via SLIP with MTU equal to 552). This router, following RFC1191 rules, constructs and sends ``Datagram Too Big'' ICMP message to the HUB. Router at CRL.NET blocks ICMP and doesn't let it to come through and reach the HUB. The connection hangs at DATA stage. Then, after a certain period of time, the standard timeout-driven retransmit procedure takes place. HUB then re-transmits the same packet (of the same large size), router that can't forward it sends back ICMP ``too big'', and CRL.NET blocks it. This scenario will take place until HUB's sendmail drops the connection by timeout. So, HUB will never adjust the MTU. My conclusion is: ~~~~~~~~~~~~~~~~ Don't block ICMP, because blocking breaks PMTU discovery. At least, don't block ICMP type 3 code 4 messages (fragmentation needed and DF set). P.S. Now, when ICMP to HUB is not anymore blocked, everything is OK. With best Regards, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 06:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20477 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 06:40:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20472 for ; Mon, 31 Aug 1998 06:40:06 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from bright.fx.genx.net (thirdeye@bright.fx.genx.net [206.64.4.154]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA26651 for ; Mon, 31 Aug 1998 06:40:00 -0700 (PDT) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id JAA17309; Mon, 31 Aug 1998 09:39:47 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 31 Aug 1998 09:39:47 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Christoph Kukulies cc: freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.7 install overwrites bootsect In-Reply-To: <199808310911.LAA04109@gilberto.physik.RWTH-Aachen.DE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I gave a 2.2.7 dist kit to a (sceptic?) colleague. I was hoping > him coming back as a missionaire. Grrm, he told me, FreeBSD install > had overwritten his bootsector (NT) although he explicitly clicked > the option that was promising to leave the bootsector intact. "clicked" ? :) *giggle* he most probably experianced PEBCAK. i've seen people who were told to try freebsd just breeze through the install not really reading _any_ of the prompts then swear when it misbehaves. i've never had the freebsd util not do what it says it's going to do. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 06:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22852 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 06:55:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22846 for ; Mon, 31 Aug 1998 06:55:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA27143 for ; Mon, 31 Aug 1998 06:55:18 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA12308; Mon, 31 Aug 1998 06:54:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: Christoph Kukulies , freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.7 install overwrites bootsect In-reply-to: Your message of "Mon, 31 Aug 1998 09:39:47 CDT." Date: Mon, 31 Aug 1998 06:54:04 -0700 Message-ID: <12303.904571644@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I can almost predict what he did (and the blame falls more on the key binding scheme in libdialog than the user because I see it all the time). He saw the boot manager menu with (*) Boot Manager selected by default, and then he used the arrow key to go down to ( ) None but then hit return (for OK) rather than SPACE to toggle the radio menu's state. It wants a space. The docs say in several places that it wants a space. Doesn't matter. People still move the cursor to the option and then just hit return because they're used to that model with other interfaces, and with libdialog what it does is drop you six feet with a rope around your neck instead. Slightly different way of doing things, our little libdialog, and it's a PITA. Just one more reason to hate libdialog, but probably still not enough motivation to write a replacement. :) - Jordan > > I gave a 2.2.7 dist kit to a (sceptic?) colleague. I was hoping > > him coming back as a missionaire. Grrm, he told me, FreeBSD install > > had overwritten his bootsector (NT) although he explicitly clicked > > the option that was promising to leave the bootsector intact. > > "clicked" ? :) *giggle* > > he most probably experianced PEBCAK. > i've seen people who were told to try freebsd just breeze through the > install not really reading _any_ of the prompts then swear when it > misbehaves. > > i've never had the freebsd util not do what it says it's going to do. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 07:17:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25759 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 07:17:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25726 for ; Mon, 31 Aug 1998 07:17:28 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA09889; Mon, 31 Aug 1998 16:07:28 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id KAA06304; Mon, 31 Aug 1998 10:18:03 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808310818.KAA06304@semyam.dinoco.de> To: Luigi Rizzo cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: lpt port scanners (was: Re: What options for BW quickcam on 2.2.7 ? ) In-reply-to: Your message of "Sat, 22 Aug 1998 13:59:02 +0200." <199808221159.NAA29591@labinfo.iet.unipi.it> Date: Mon, 31 Aug 1998 10:18:03 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the effort, but for scanners etc it would be a very nice thing to do > given that a lot of scanners on the market now seem to use the parallel > port). If I knew a company which manufactures them and gives out detailed information about the protocol used I'd probably have one already as a scanner would be a nice addition to my machine. Anybody knowing one who does have documentation and gives them out w/o NDA or other silly things preventing real use in FreeBSD? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 07:18:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25985 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 07:18:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25905 for ; Mon, 31 Aug 1998 07:18:09 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from bright.fx.genx.net (thirdeye@bright.fx.genx.net [206.64.4.154]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA28431 for ; Mon, 31 Aug 1998 07:18:03 -0700 (PDT) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id KAA17615; Mon, 31 Aug 1998 10:18:16 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 31 Aug 1998 10:18:16 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Jordan K. Hubbard" cc: freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.7 install overwrites bootsect In-Reply-To: <12303.904571644@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG perhaps this is a good place for an "Are you sure" dialog, yucky, but they are in other places in sysinstall. (espec if NT partitions are detected) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 31 Aug 1998, Jordan K. Hubbard wrote: > Actually, I can almost predict what he did (and the blame falls more > on the key binding scheme in libdialog than the user because I see it > all the time). He saw the boot manager menu with (*) Boot Manager > selected by default, and then he used the arrow key to go down to ( ) > None but then hit return (for OK) rather than SPACE to toggle the > radio menu's state. It wants a space. The docs say in several places > that it wants a space. Doesn't matter. People still move the cursor > to the option and then just hit return because they're used to that > model with other interfaces, and with libdialog what it does is drop > you six feet with a rope around your neck instead. Slightly different > way of doing things, our little libdialog, and it's a PITA. > > Just one more reason to hate libdialog, but probably still not enough > motivation to write a replacement. :) > > - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 09:16:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11371 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 09:16:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA11366 for ; Mon, 31 Aug 1998 09:16:52 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id QAA07836; Mon, 31 Aug 1998 16:20:30 +0200 From: Luigi Rizzo Message-Id: <199808311420.QAA07836@labinfo.iet.unipi.it> Subject: Re: lpt port scanners (was: Re: What options for BW quickcam on 2.2.7 ? ) To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Mon, 31 Aug 1998 16:20:30 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de In-Reply-To: <199808310818.KAA06304@semyam.dinoco.de> from "Stefan Eggers" at Aug 31, 98 10:17:44 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > the effort, but for scanners etc it would be a very nice thing to do > > given that a lot of scanners on the market now seem to use the parallel > > port). > > If I knew a company which manufactures them and gives out detailed > information about the protocol used I'd probably have one already as a > scanner would be a nice addition to my machine. Anybody knowing one > who does have documentation and gives them out w/o NDA or other silly > things preventing real use in FreeBSD? i think we are not going to have any help from manufacturers. The only viable approach i think is if someone happens to have the hardware and either there is some scsi stuff implemented on top of the lpt interface, or there is some linux driver that one can use as a source. The only nice thing is that scanners have generally a simple logical interface cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 09:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17865 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 09:56:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles346.castles.com [208.214.167.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17841 for ; Mon, 31 Aug 1998 09:56:24 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id JAA20742; Mon, 31 Aug 1998 09:53:01 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808310953.JAA20742@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Darren Reed cc: hackers@FreeBSD.ORG Subject: Re: TCP performance. In-reply-to: Your message of "Mon, 31 Aug 1998 20:15:23 +1000." <199808311016.DAA24028@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 09:53:00 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, FreeBSD TCP performance sucks or it does some things which can > make it suck badly. It might be more fair to say "FreeBSD 2.2.6 using 3c589d and 'zp' driver suffers slow FTP send? receive? performance with Sun LX running SunOS 4.1.x over with and " > >From simple observations (hub leds, ftp's meter), ftp'ing from a laptop > (3c589d) running 2.2.6 to SunOS4 (LX) is considerably worse than in the > other direction. > > Although I do suspect the 3c589d (or its driver - zp ?) > do not handle ethernet collisions at all in a good way to be a possible > cause. The '589 handles collisions correctly; there's no other way to handle them and work. The driver isn't involved in handling collisions; it gives a packet to the card, and waits for the card to report results. Having said that, bear in mind that the 'zp' driver is a bandaid that only exists to aid installation, and you may well be better off using the 'ep' driver inside the pccard framework. If it counts for anything, I regularly move data in and out of both a '589 and an NE2000 clone pccard at around the 1MB/sec rate, so I have a direct counter-example if you feel that's the way to go. Please, if you want to complain about FreeBSD's performance, consider investigating the problem a little to give some substance to your complaint. Without it, all you're doing is abusing the product; with it, you may help us improve, and hopefully reduce your need to complain in the future. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 10:17:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21630 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 10:17:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA21621 for ; Mon, 31 Aug 1998 10:16:59 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zDXDA-0006Lt-00; Mon, 31 Aug 1998 10:53:48 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id KAA04074; Mon, 31 Aug 1998 10:51:44 -0600 (MDT) Message-Id: <199808311651.KAA04074@harmony.village.org> To: Luoqi Chen Subject: Re: 64k physio limit Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 31 Aug 1998 05:26:35 EDT." <199808310926.FAA13727@lor.watermarkgroup.com> References: <199808310926.FAA13727@lor.watermarkgroup.com> Date: Mon, 31 Aug 1998 10:51:44 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808310926.FAA13727@lor.watermarkgroup.com> Luoqi Chen writes: : Set the device driver's cdevsw:d_maxio to 256k? Should we then remove the hack in dump that limits the write size to 64k? Would a 256k write make it to the tape in one record? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 10:26:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22879 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 10:26:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22870 for ; Mon, 31 Aug 1998 10:26:11 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA04332 for hackers@freebsd.org; Mon, 31 Aug 1998 13:28:08 -0400 From: Bill Paul Message-Id: <199808311728.NAA04332@skynet.ctr.columbia.edu> Subject: Call for testers for new ThunderLAN driver To: hackers@FreeBSD.ORG Date: Mon, 31 Aug 1998 13:28:06 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've rewritten the TI ThunderLAN driver in preparation for integrating it into the 2.2 branch. The major changes are as follows: - Rewrote the multicast support to use the three spare entries in the perfect filter table before rolling over to the hash table. This means the first three groups are always filtered perfectly (which means we save a bit from the hash table that would normally be used by the 224.0.0.1 entry, which is always present). - Did a major overhaul of the register access macros. Hopefully things are somewhat less grotty now. - Did away with the notion of attaching each PHY as a separate interface. This doesn't really apply; this being the first driver I ever wrote, I got a few concepts wrong, and this was one of them. This simplifys the interface attach somewhat. - Cleaned up the PHY autonegotiation code based on what I learned with the XL driver. - Added support for newer versions of the Olicom 2326 10/100 adapter with the Micro Linear ML6692 100baseTX PHY. This is a sort of oddball component in that it provides autonegotiation for all modes (100Mbps, 10Mbps, full duplex, half duplex) but relies on the ThunderLAN's internal PHY for actual 10Mbps support. It also does not have vendor/device ID registers, which makes it a little tricky to detect. Older versions of the 2326 have a NatSemi NS83840A; using the ML 6692 is probably more cost effective since using the NS83840A means the ThunderLAN's internal PHY goes unused. - Tried to fix support the BNC port on those adapters that have them. This is untested as I don't have access to a device with a BNC connector. - Added code to raise the PCI latency timer value all the way up, as recommended by the manual. - Added new routine tl_hardreset() to attempt to insure that the internal PHY is brought online correctly, again as specified by the manual. The internal PHY is now always activated by default, although it may be kept isolated and unused in certain configurations. The driver code can be obtained from the following URLs: http://www.freebsd.org/~wpaul/ThunderLAN/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/ThunderLAN/2.2 source for FreeBSD 2.2.x If you have a recent 3.0 snapshot that already has the older ThunderLAN driver, you can simply copy if_tl.c and if_tlreg.h over the existing copies in /sys/pci and recompile, otherwise follow the instructions at http://www.freebsd.org/~wpaul/ThunderLAN for adding the driver to an existing system. This driver supports the following list of Compaq and Olicom network adapters and integrated NICs: Compaq Netelligent 10 Compaq Netelligent 10/100 Compaq Netelligent 10/100 Proliant Compaq Netelligent 10/100 Dual Port Compaq NetFlex-3/P Integrated Compaq NetFlex-3/P Compaq NetFlex 3/P w/ BNC Compaq Netelligent 10/100 TX Embedded UTP Compaq Netelligent 10 T/2 PCI UTP/Coax Compaq Netelligent 10/100 TX UTP Olicom OC-2183/2185 Olicom OC-2325 Olicom OC-2326 10/100 TX UTP Compaq machines with built-in ThunderLAN NICs include the Compaq Deskpro 4000 series and the Compaq Proliant servers. If you have one of these adapters or integrated controllers, please give this driver a try and report on the results. Also, if anyone happens to know of any other ethernet adapters that use the ThunderLAN chip, I'd be interested to hear about it. PCI vendor and device IDs would also be greatly appreciated. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 10:41:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24961 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 10:41:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24956 for ; Mon, 31 Aug 1998 10:41:41 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id KAA19361; Mon, 31 Aug 1998 10:42:37 -0700 (PDT) Date: Mon, 31 Aug 1998 10:42:37 -0700 (PDT) From: Jim Shankland Message-Id: <199808311742.KAA19361@biggusdiskus.flyingfox.com> To: hackers@FreeBSD.ORG, ru@ucb.crimea.ua Subject: Re: PMTU discovery, Firewalls and Sendmail In-Reply-To: <19980831162228.A20318@ucb.crimea.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [PMTU discovery fails due to dropped/filtered ICMP messages, causing SMTP timeouts in DATA phase.] Yes, PMTU discovery doesn't work all that well in practice: too often, the ICMP "fragmentation required" packet evaporates. I'll bet the most common cause is miconfigured firewalls; however, in one case I investigated, the ICMP packet seemed to be disappearing in an ISP's backbone transit, where one wouldn't expect to see filtering. (Never did figure out how the ICMP packet came to grief in that case.) Most of the time, PMTU discovery doesn't get a chance to fail because much of the Internet can handle 1500 bytes packets, which is the starting MTU when the originating host is on Ethernet. But try setting up a system on a PPP link with an MRU of, say, 2048, and browse the Web for a few days. A surprising number of Web sites will disappear until you lower your MRU to 1500. One possible way to address this would be for the TCP retransmit code to drop the MSS back if PMTU discovery is being done, and the MSS has not yet been reduced. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 11:01:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27617 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 11:01:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27612 for ; Mon, 31 Aug 1998 11:01:06 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA02843 for ; Mon, 31 Aug 1998 11:00:05 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002837; Mon Aug 31 11:00:03 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA06751 for freebsd-hackers@freebsd.org; Mon, 31 Aug 1998 11:00:03 -0700 (PDT) From: Archie Cobbs Message-Id: <199808311800.LAA06751@bubba.whistle.com> Subject: Re: FreeBSD's RST validation In-Reply-To: <199808311306.GAA27281@salsa.gv.tsc.tdk.com> from Don Lewis at "Aug 31, 98 06:06:36 am" To: freebsd-hackers@FreeBSD.ORG Date: Mon, 31 Aug 1998 11:00:03 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would some -hackers comment on this bug (posted to freebsd-security)? Thanks, -Archie Don Lewis writes: > On Aug 30, 5:21pm, Tristan Horn wrote: > } Subject: FreeBSD's RST validation > } --ZRyEpB+iJ+qUx0kp > } Content-Type: multipart/mixed; boundary=qGV0fN9tzfkG3CxV > } > } > } --qGV0fN9tzfkG3CxV > } Content-Type: text/plain; charset=us-ascii > } > } RFC 793, pages 36-39 (chapter 3.5) describes closing connections with > } TCP. Page 37 is of particular interest: > } > } Reset Processing > } > } In all states except SYN-SENT, all reset (RST) segments are validated > } by checking their SEQ-fields. A reset is valid if its sequence number > } is in the window. In the SYN-SENT state (a RST received in response > } to an initial SYN), the RST is acceptable if the ACK field > } acknowledges the SYN. > } > } Unfortunately, FreeBSD (2.2.5, 2.2.6, 2.2.7, 3.0) does not appear to > } validate RST segments to this extent. In other words, only the packets' > } IP/port pairs are checked. > > Back in December 1997, I posted the following patch for the LAND attack > and also implemented stricter RST validation. The variation of the > LAND fix in the first two chunks of this patch was implemented (you'll > have to look carefully at the code to find the second chunk), but I don't > believe the rest of the fixes in this patch were applied. > > I've been running a version of this patch altered for 2.1.x since December > without problems. If you remove the first two chunks of this patch, it > will apply cleanly to the 2.2-stable version of tcp_input.c, though I have > no idea if it will work ... > > ----------------- Cut Here -------------------------- > --- tcp_input.c.2_2 Mon Dec 1 16:49:21 1997 > +++ tcp_input.c Wed Dec 3 02:21:45 1997 > @@ -318,19 +318,6 @@ > #endif /* TUBA_INCLUDE */ > > /* > - * Reject attempted self-connects. XXX This actually masks > - * a bug elsewhere, since self-connect should work. > - * However, a urrently-active DoS attack in the Internet > - * sends a phony self-connect request which causes an infinite > - * loop. > - */ > - if (ti->ti_src.s_addr == ti->ti_dst.s_addr > - && ti->ti_sport == ti->ti_dport) { > - tcpstat.tcps_badsyn++; > - goto drop; > - } > - > - /* > * Check that TCP offset makes sense, > * pull out TCP options and adjust length. XXX > */ > @@ -654,6 +641,24 @@ > if (m->m_flags & (M_BCAST|M_MCAST) || > IN_MULTICAST(ntohl(ti->ti_dst.s_addr))) > goto drop; > + > + /* > + * Reject attempted self-connects. > + * > + * Doing the test here should prevent the "LAND" DoS > + * attack without affecting legitimate self-connects > + * which will occur in the SYN-SENT state. > + * > + * In the dropafterack code below we'll also fix the real > + * bug in the SYN-RECEIVED state that causes the infinite > + * loop since it can also be used to generate ACK storms. > + */ > + if (ti->ti_src.s_addr == ti->ti_dst.s_addr > + && ti->ti_sport == ti->ti_dport) { > + tcpstat.tcps_badsyn++; > + goto drop; > + } > + > am = m_get(M_DONTWAIT, MT_SONAME); /* XXX */ > if (am == NULL) > goto drop; > @@ -962,17 +967,99 @@ > > /* > * States other than LISTEN or SYN_SENT. > - * First check timestamp, if present. > + * First check the RST flag and sequence number since reset segments > + * are exempt from the timestamp and connection count tests. This > + * fixes a bug introduced by the Stevens, vol. 2, p. 960 bugfix > + * below which allowed reset segments in half the sequence space > + * to fall though and be processed (which gives forged reset > + * segments with a random sequence number a 50 percent chance of > + * killing a connection). > + * Then check timestamp, if present. > * Then check the connection count, if present. > * Then check that at least some bytes of segment are within > * receive window. If segment begins before rcv_nxt, > * drop leading data (and SYN); if nothing left, just ack. > * > + * > + * If the RST bit is set, check the sequence number to see > + * if this is a valid reset segment. > + * RFC 793 page 37: > + * In all states except SYN-SENT, all reset (RST) segments > + * are validated by checking their SEQ-fields. A reset is > + * valid if its sequence number is in the window. > + * Note: this does not take into account delayed ACKs, so > + * we should test against last_ack_sent instead of rcv_nxt. > + * Also, it does not make sense to allow reset segments with > + * sequence numbers greater than last_ack_sent to be processed > + * since these sequence numbers are just the acknowledgement > + * numbers in our outgoing packets being echoed back at us, > + * and these acknowledgement numbers are monotonically > + * increasing. > + * If we have multiple segments in flight, the intial reset > + * segment sequence numbers will be to the left of last_ack_sent, > + * but they will eventually catch up. > + * In any case, it never made sense to trim reset segments to > + * fit the receive window since RFC 1122 says: > + * 4.2.2.12 RST Segment: RFC-793 Section 3.4 > + * > + * A TCP SHOULD allow a received RST segment to include data. > + * > + * DISCUSSION > + * It has been suggested that a RST segment could contain > + * ASCII text that encoded and explained the cause of the > + * RST. No standard has yet been established for such > + * data. > + * > + * If the reset segment passes the sequence number test examine > + * the state: > + * SYN_RECEIVED STATE: > + * If passive open, return to LISTEN state. > + * If active open, inform user that connection was refused. > + * ESTABLISHED, FIN_WAIT_1, FIN_WAIT2, CLOSE_WAIT STATES: > + * Inform user that connection was reset, and close tcb. > + * CLOSING, LAST_ACK, TIME_WAIT STATES > + * Close the tcb. > + * TIME_WAIT state: > + * Drop the segment - see Stevens, vol. 2, p. 964 and > + * RFC 1337. > + */ > + if (tiflags&TH_RST) { > + if (tp->last_ack_sent == ti->ti_seq) { > + switch (tp->t_state) { > + > + case TCPS_SYN_RECEIVED: > + so->so_error = ECONNREFUSED; > + goto close; > + > + case TCPS_ESTABLISHED: > + case TCPS_FIN_WAIT_1: > + case TCPS_FIN_WAIT_2: > + case TCPS_CLOSE_WAIT: > + so->so_error = ECONNRESET; > + close: > + tp->t_state = TCPS_CLOSED; > + tcpstat.tcps_drops++; > + tp = tcp_close(tp); > + break; > + > + case TCPS_CLOSING: > + case TCPS_LAST_ACK: > + tp = tcp_close(tp); > + break; > + > + case TCPS_TIME_WAIT: > + break; > + } > + } > + goto drop; > + } > + > + /* > * RFC 1323 PAWS: If we have a timestamp reply on this segment > * and it's less than ts_recent, drop it. > */ > - if ((to.to_flag & TOF_TS) != 0 && (tiflags & TH_RST) == 0 && > - tp->ts_recent && TSTMP_LT(to.to_tsval, tp->ts_recent)) { > + if ((to.to_flag & TOF_TS) != 0 && tp->ts_recent && > + TSTMP_LT(to.to_tsval, tp->ts_recent)) { > > /* Check to see if ts_recent is over 24 days old. */ > if ((int)(tcp_now - tp->ts_recent_age) > TCP_PAWS_IDLE) { > @@ -1003,10 +1090,19 @@ > * RST segments do not have to comply with this. > */ > if ((tp->t_flags & (TF_REQ_CC|TF_RCVD_CC)) == (TF_REQ_CC|TF_RCVD_CC) && > - ((to.to_flag & TOF_CC) == 0 || tp->cc_recv != to.to_cc) && > - (tiflags & TH_RST) == 0) > + ((to.to_flag & TOF_CC) == 0 || tp->cc_recv != to.to_cc)) > goto dropafterack; > > + /* > + * In the SYN-RECEIVED state, validate that the packet belongs to > + * this connection before trimming the data to fit the receive > + * window. Check the sequence number versus IRS since we know > + * the sequence numbers haven't wrapped. This is a partial fix > + * for the "LAND" DoS attack. > + */ > + if (tp->t_state == TCPS_SYN_RECEIVED && SEQ_LT(ti->ti_seq, tp->irs)) > + goto dropwithreset; > + > todrop = tp->rcv_nxt - ti->ti_seq; > if (todrop > 0) { > if (tiflags & TH_SYN) { > @@ -1118,40 +1214,6 @@ > } > > /* > - * If the RST bit is set examine the state: > - * SYN_RECEIVED STATE: > - * If passive open, return to LISTEN state. > - * If active open, inform user that connection was refused. > - * ESTABLISHED, FIN_WAIT_1, FIN_WAIT2, CLOSE_WAIT STATES: > - * Inform user that connection was reset, and close tcb. > - * CLOSING, LAST_ACK, TIME_WAIT STATES > - * Close the tcb. > - */ > - if (tiflags&TH_RST) switch (tp->t_state) { > - > - case TCPS_SYN_RECEIVED: > - so->so_error = ECONNREFUSED; > - goto close; > - > - case TCPS_ESTABLISHED: > - case TCPS_FIN_WAIT_1: > - case TCPS_FIN_WAIT_2: > - case TCPS_CLOSE_WAIT: > - so->so_error = ECONNRESET; > - close: > - tp->t_state = TCPS_CLOSED; > - tcpstat.tcps_drops++; > - tp = tcp_close(tp); > - goto drop; > - > - case TCPS_CLOSING: > - case TCPS_LAST_ACK: > - case TCPS_TIME_WAIT: > - tp = tcp_close(tp); > - goto drop; > - } > - > - /* > * If a SYN is in the window, then this is an > * error and we send an RST and drop the connection. > */ > @@ -1660,9 +1722,22 @@ > /* > * Generate an ACK dropping incoming segment if it occupies > * sequence space, where the ACK reflects our state. > - */ > - if (tiflags & TH_RST) > - goto drop; > + * > + * We can now skip the test for the RST flag since all > + * paths to this code happen after packets containing > + * RST have been dropped. > + * > + * In the SYN-RECEIVED state, don't send an ACK unless the > + * segment we received passes the SYN-RECEIVED ACK test. > + * If it fails send a RST. This breaks the loop in the > + * "LAND" DoS attack, and also prevents an ACK storm > + * between two listening ports that have been sent forged > + * SYN segments, each with the source address of the other. > + */ > + if (tp->t_state == TCPS_SYN_RECEIVED && (tiflags & TH_ACK) && > + (SEQ_GT(tp->snd_una, ti->ti_ack) || > + SEQ_GT(ti->ti_ack, tp->snd_max)) ) > + goto dropwithreset; > #ifdef TCPDEBUG > if (so->so_options & SO_DEBUG) > tcp_trace(TA_DROP, ostate, tp, &tcp_saveti, 0); > ----------------- Cut Here -------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 11:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04898 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 11:36:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04871 for ; Mon, 31 Aug 1998 11:36:35 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id PAA17561; Mon, 31 Aug 1998 15:34:22 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199808311834.PAA17561@roma.coe.ufrj.br> Subject: Re: 64k physio limit In-Reply-To: <199808310926.FAA13727@lor.watermarkgroup.com> from Luoqi Chen at "Aug 31, 98 05:26:35 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Mon, 31 Aug 1998 15:34:22 -0300 (EST) Cc: hackers@FreeBSD.ORG, imp@village.org X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Luoqi Chen) // > Is there any way to get a larger I/O to happen than 64k? I have a tape // > drive that would be happiest if I could do 256kish writes to it at a time, // > rather than only 64k. // > // > Warner // > // Set the device driver's cdevsw:d_maxio to 256k? Which problems arise from making this the default ? Memory waste ? Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 11:57:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10015 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 11:57:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from firebat.wolfepub.com (firebat.wolfepub.com [206.250.193.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10001 for ; Mon, 31 Aug 1998 11:57:26 -0700 (PDT) (envelope-from matthew@wolfepub.com) Received: from ricecake.fastnet0.net (niu-ppp202.triton.net [209.172.4.202]) by firebat.wolfepub.com (8.9.0/8.9.0) with SMTP id OAA02163 for ; Mon, 31 Aug 1998 14:55:48 -0400 (EDT) Message-Id: <3.0.3.32.19980831150336.007233bc@wolfepub.com> X-Sender: matthew@wolfepub.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 31 Aug 1998 15:03:36 -0400 To: hackers@FreeBSD.ORG From: Matthew Hagerty Subject: Environment of a process Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Where does a process get its environment if it is not executed from the command line? I have a program that connects to a database and relies on several ENV VARS to be set. I solved the problem with a shell script that wraps the program like this: #!/bin/sh set var;export set var;export set var;export call program exit There has to be a more efficient way to do this?! This particular program is run as a CGI and wrapping it in a shell adds overhead that I'm trying to cut down on. Any insight would be greatly appreciated. Thanks, Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 12:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11205 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 12:05:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dmog10.bell.ca (dmog10.bell.ca [198.235.69.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11200 for ; Mon, 31 Aug 1998 12:05:00 -0700 (PDT) (envelope-from YVLEPAGE@post.bell.ca) Received: from POST.BELL.CA ([142.126.132.38]) by dmog10.bell.ca with SMTP id PAA20305 for ; Mon, 31 Aug 1998 15:04:01 -0400 (EDT) Received: by POST.BELL.CA (Soft-Switch LMS 2.0) with snapi via NOTES id 0010510008284696; Mon, 31 Aug 1998 15:06:12 -0400 From: Yves Lepage To: "freebsd-hackers(a)freebsd.org" Subject: subscribe freebsd-hackers Message-ID: <0010510008284696000002L162*@MHS> Date: Mon, 31 Aug 1998 15:06:12 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 12:11:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11680 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 12:11:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11675 for ; Mon, 31 Aug 1998 12:11:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00438; Mon, 31 Aug 1998 12:07:24 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808311207.MAA00438@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joao Carlos Mendes Luis cc: luoqi@watermarkgroup.com (Luoqi Chen), hackers@FreeBSD.ORG, imp@village.org Subject: Re: 64k physio limit In-reply-to: Your message of "Mon, 31 Aug 1998 15:34:22 -0300." <199808311834.PAA17561@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 12:07:24 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #define quoting(Luoqi Chen) > // > Is there any way to get a larger I/O to happen than 64k? I have a tape > // > drive that would be happiest if I could do 256kish writes to it at a time, > // > rather than only 64k. > // > > // > Warner > // > > // Set the device driver's cdevsw:d_maxio to 256k? > > Which problems arise from making this the default ? Memory waste ? Drivers may expect not to be called with more than 64k of work at a given time. Having a single limit anywhere is bogus; the d_maxio field should be used and fragmentation managed at a higher level. I don't recall whether this is now being done correctly; it wasn't working properly when I had to fix the 'wfd' driver to deal with the Zip not supporting > 32k transfers. I don't know of any driver that maintains a maximum-transfer sized buffer, no. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 12:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12602 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 12:19:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12595 for ; Mon, 31 Aug 1998 12:19:35 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA07483; Mon, 31 Aug 1998 13:18:16 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808311918.NAA07483@panzer.plutotech.com> Subject: Re: 64k physio limit In-Reply-To: <199808310926.FAA13727@lor.watermarkgroup.com> from Luoqi Chen at "Aug 31, 98 05:26:35 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Mon, 31 Aug 1998 13:18:16 -0600 (MDT) Cc: hackers@FreeBSD.ORG, imp@village.org X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote... > > Is there any way to get a larger I/O to happen than 64k? I have a tape > > drive that would be happiest if I could do 256kish writes to it at a time, > > rather than only 64k. > > > > Warner > > > Set the device driver's cdevsw:d_maxio to 256k? > > -lq I'm not so sure that will work. physio currently restricts I/O size by using minphys(). minphys() looks at the buffer kva size (b_kvasize), which I think it currently set to MAXPHYS, which is 128K. I think that at least in CAM, you should be able to do 256K writes to a tape drive, assuming: 1. you can get the transactions through to the tape driver's strategy routine in that size and 2. your controller can handle things that size. The first one probably requires changing MAXPHYS, or a buffer chaining scheme. I'm not quite sure what happens if a controller can't handle I/O requests of a particular size. I guess it's handled in the driver, but I've never looked, so I don't know. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 12:41:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15558 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 12:41:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15552 for ; Mon, 31 Aug 1998 12:41:35 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id PAA19225; Mon, 31 Aug 1998 15:41:29 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 31 Aug 1998 15:41:29 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Matthew Hagerty cc: hackers@FreeBSD.ORG Subject: Re: Environment of a process In-Reply-To: <3.0.3.32.19980831150336.007233bc@wolfepub.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man exec, look at: int exect(const char *path, char *const argv[], char *const envp[]) also note getenv(3), man 3 getenv good luck, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 31 Aug 1998, Matthew Hagerty wrote: > Greetings, > > Where does a process get its environment if it is not executed from the > command line? I have a program that connects to a database and relies on > several ENV VARS to be set. > > I solved the problem with a shell script that wraps the program like this: > > #!/bin/sh > > set var;export > set var;export > set var;export > > call program > exit > > There has to be a more efficient way to do this?! This particular program > is run as a CGI and wrapping it in a shell adds overhead that I'm trying to > cut down on. > > Any insight would be greatly appreciated. > > Thanks, > Matthew > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 13:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22292 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 13:18:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA22261 for ; Mon, 31 Aug 1998 13:18:43 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0zDaMv-00062Q-00; Mon, 31 Aug 1998 13:16:05 -0700 Date: Mon, 31 Aug 1998 13:16:05 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: Matthew Hagerty cc: hackers@FreeBSD.ORG Subject: Re: Environment of a process In-Reply-To: <3.0.3.32.19980831150336.007233bc@wolfepub.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Aug 1998, Matthew Hagerty wrote: > Greetings, > > Where does a process get its environment if it is not executed from the > command line? I have a program that connects to a database and relies on > several ENV VARS to be set. Wherever it is executed from. If it is a web server, then consult your web server vendor to find out how that happens. With Apache, for example, there are directives in mod_env that you can use to explicitly set various environment variables. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 14:14:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03297 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 14:14:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03291 for ; Mon, 31 Aug 1998 14:14:47 -0700 (PDT) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:beattie@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id OAA11165; Mon, 31 Aug 1998 14:11:54 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id OAA19930; Mon, 31 Aug 1998 14:13:09 -0700 Date: Mon, 31 Aug 1998 14:13:09 -0700 (PDT) From: Brian Beattie To: Stefan Eggers cc: Luigi Rizzo , freebsd-hackers@FreeBSD.ORG Subject: Re: lpt port scanners (was: Re: What options for BW quickcam on 2.2.7 ? ) In-Reply-To: <199808310818.KAA06304@semyam.dinoco.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Aug 1998, Stefan Eggers wrote: > > the effort, but for scanners etc it would be a very nice thing to do > > given that a lot of scanners on the market now seem to use the parallel > > port). > > If I knew a company which manufactures them and gives out detailed > information about the protocol used I'd probably have one already as a > scanner would be a nice addition to my machine. Anybody knowing one > who does have documentation and gives them out w/o NDA or other silly > things preventing real use in FreeBSD? > Microtek has them on it's ftp site. I think UMAX has them on it's webpage. I'm currently trying to get it out of adara. Brian Beattie | If my corporate life has taught me anything, beattie@aracnet.com | it was that running multi-million dollar www.aracnet.com/~beattie | projects in no way implied managerial competence. | Tony Porczyk ( in comp.unix.bsd.freebsd.misc ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 14:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07446 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 14:38:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07420 for ; Mon, 31 Aug 1998 14:38:10 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id RAA20955; Mon, 31 Aug 1998 17:36:42 -0400 (EDT) Date: Mon, 31 Aug 1998 17:36:41 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: Mike Smith cc: hackers Subject: Re: FFS questions In-Reply-To: <199808271532.PAA00757@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, Mike Smith wrote: > > The comment says it is the number of cylinders per *cycle* in position > > table. What does the "cycle" mean? > > It's the size of the rotational offset table. Starting from position 0 > on the disk, there are N cycles of fastest-next-block locations as you > move across the disk. You only need to store one cycle in the offset > table. > >From your explanation, it seems that the table is for entire disk (not constrained to one cylinder) and according to comment in mkfs.c, each cycle is a rotational pattern. So I guess that each pattern covers fs_cpc cylinders, or after fs_cpc cylinders the pattern will repeat (on the next cylinder boundary or immediately?) So how is the pattern represented anyway? Is there any relationship between fs_cpc and fs_nrpos (should be number of rotational positions *per cylinder*). I guess that in a pattern (cycle), there are fs_cpc * fs_nrpos different positions. How are these positions represented, by block numbers or by increments? The macro cbtorpos() converts a block number to a rotational position in a single cylinder. This position is used to index position table to get another block number. This block number is in turn used to index the rotational table to get an increase of it. After increase, the block number is used again to index the positional table until a free file block is found.... The use of fs_postbl() and fs_rotbl() seems to construct a list of blocks available at each rotational position. But they confuses me. I hope someone can clarify for me on how those blocks for one rotational position are organized. Any help is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 15:08:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12718 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 15:08:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12697 for ; Mon, 31 Aug 1998 15:08:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01368; Mon, 31 Aug 1998 15:03:27 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808311503.PAA01368@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: Mike Smith , hackers Subject: Re: FFS questions In-reply-to: Your message of "Mon, 31 Aug 1998 17:36:41 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 15:03:27 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Again, bear in mind that the techniques we're discussing here are deprecated, that is, they are no longer useful and we do our best to avoid using them whenever possible. > > > The comment says it is the number of cylinders per *cycle* in position > > > table. What does the "cycle" mean? > > > > It's the size of the rotational offset table. Starting from position 0 > > on the disk, there are N cycles of fastest-next-block locations as you > > move across the disk. You only need to store one cycle in the offset > > table. > > >From your explanation, it seems that the table is for entire disk (not > constrained to one cylinder) and according to comment in mkfs.c, each > cycle is a rotational pattern. So I guess that each pattern covers fs_cpc > cylinders, or after fs_cpc cylinders the pattern will repeat (on the next > cylinder boundary or immediately?) The pattern repeats every fs_cpc cylinders, which is why you only store that much of it. The pattern always covers a whole number of cylinders, so the repeat is always on a cylinder boundary. > So how is the pattern represented anyway? Is there any relationship > between fs_cpc and fs_nrpos (should be number of rotational positions *per > cylinder*). I guess that in a pattern (cycle), there are fs_cpc * > fs_nrpos different positions. How are these positions represented, by > block numbers or by increments? Each entry in the pattern gives an offset to the next optimally located rotational position, ie. allowing for head/track switch delays, skipping over spares at the end of the track/cylinder, etc. > The macro cbtorpos() converts a block number to a rotational position in a > single cylinder. This position is used to index position table to get > another block number. This block number is in turn used to index the > rotational table to get an increase of it. After increase, the block > number is used again to index the positional table until a free file block > is found.... The use of fs_postbl() and fs_rotbl() seems to construct a > list of blocks available at each rotational position. But they confuses > me. If you have allocated a block, and wish to allocate another to follow it, the ideal case is to find a block that can be read as quickly as possible. This block will be located somewhere after the block that you have just allocated; it may be on the same track, on another track on the same cylinder, or on another cylinder. In each case, you need to consider different factors when calculating this block. The position table contains a precalculated set of block offsets, rather than repeating the calculations each time. When trying to understand why these calculations were necessary, understand that the disk drives being used when this code was developed had no "intelligence" as such; all optimisations for disk behaviour had to be embedded into the filesystem. It is difficult to explain the justification for these optimisations without a lengthy explanation of: - sector interleave - track interleave - command overhead - head switch time - track-to-track time and a number of other subtle factors which modify these and related parameters. Modern disks do not behave like these old disks, which is why we disable these old "optimisations" where possible. > I hope someone can clarify for me on how those blocks for one rotational > position are organized. Blocks in each rotational position are logically contiguous. By default, there were 8 rotational positions on the disk, so for a disk with 32 sectors per track, there would be 4 blocks in each rotational position, 0-3 in #0, 4-7 in #1, etc. These sectors might not be arranged contigously on the disk however. > Any help is appreciated. In studying this code, it's important to remember what I've tried to point out above; it was designed to optimise performance on old hardware, and only worked well if *all* parameters were correct. Modern disk hardware attempts to second-guess the operating system, and usually does a better job. We improve performance by allocating contigous space on the disk wherever possible (no interleave, only one rotational position); this takes advantage of the read-ahead/write behind performed by most modern disks rather than wasting space in the disk cache with intervening blocks that we will not use. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 15:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15955 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 15:22:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15940 for ; Mon, 31 Aug 1998 15:22:19 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA06366; Mon, 31 Aug 1998 23:14:07 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <199808312214.XAA06366@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG cc: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Subject: Re: Help with passing fd on FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 23:14:07 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > Oops, I turned the page and the BSD4.3+ example looks like the FreeBSD : > struct. The Stevens book appears to have a good example. : > : > > Can someone give me pointers on passing open file descriptors on FreeBSD? : : still, this looks to me one of the most obscure interfaces in the OS. : Does any real application use that ? User-ppp in -current does. When it negotiates multi-link with a peer, it creates a local domain socket based on that peers id. If the socket already exists, it passes the link to the other ppp invocation that's already running multi-link with the same peer. Effectively, it allows a machine to open up several connections to us and we bundle the links up into one logical link. This of course can be extremely confusing if you aren't in -direct mode - I ``dial'' the peer, connect successfully, do the LCP stuff, get the auth stuff right and then all of a sudden I get my shell prompt back. Reading the log reveals that the link was passed to another ppp instance. A word of caution - be *very* careful when passing a descriptor for your ctty. If you subsequently close the ctty, the descriptor that's been passed to the other process gets revoked ! This is why ppp must sometimes leave pause()d ``session leader'' processes lying around ;-I : cheers : luigi : -----------------------------+-------------------------------------- : Luigi Rizzo | Dip. di Ingegneria dell'Informazione : email: luigi@iet.unipi.it | Universita' di Pisa : tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) : fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ : _____________________________|______________________________________ -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 15:22:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16003 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 15:22:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15998 for ; Mon, 31 Aug 1998 15:22:52 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA05687; Mon, 31 Aug 1998 22:54:49 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <199808312154.WAA05687@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Dru Nelson cc: "Pitcairn, Duncan" , freebsd-hackers@FreeBSD.ORG Subject: Re: I added Microsoft VPN / PPTP for NATD In-reply-to: Your message of "Tue, 28 Jul 1998 23:26:08 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 22:54:49 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Have you contacted anyone yet ? Do you want to send the patches to me ? Cheers. > Hi, > > I needed to VPN to work from a machine on my network so I added the code > to the NATD today. It works great. (The natd and libalias code is very > good, so it wasn't hard) > > Essentially, I added a command line paramater called 'pptpalias' with > an argument of the ip address of the machine on the inside that is to > be used for the pptp service (client or server). The firewall should > then pass PPTP (IP GRE packets) traffic directly to that machine after > translation. > > I read on one of the posts to this list > that the linux version acts similarly. Apparently, there isn't a port > number to translate (or the microsoft implmentation doesn't implement it > correctly). So, this works for a single machine on the inside to any > machine on the outside. This should work fine for telecommuters or a > single server behind the firewall. > > I will be contacting someone who maintains the nat stuff to see if they > want it. I'm running on > 2.2.5-RELEASE. The changes are to the libalias files and the natd.c. > > I'm not on this list, so please reply to me in email directly... > > Take it easy, > > Dru Nelson > Redwood City, California -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 15:43:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19560 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 15:43:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19553 for ; Mon, 31 Aug 1998 15:43:52 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id SAA12584 for ; Mon, 31 Aug 1998 18:44:14 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <199808312244.SAA12584@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG Subject: Has anyone gotten the Netgear FA410TX pccard to work? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 18:44:14 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've fiddled and failed. PAO is silent on this card. The tech-support people say it should look like a NE2000, but it autoconfigs as a NE1000 and claims its NIC memory is invalid. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 16:03:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24370 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 16:03:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sv01.cet.co.jp ([210.171.56.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24321 for ; Mon, 31 Aug 1998 16:03:23 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by sv01.cet.co.jp (8.8.8/8.8.8) with SMTP id XAA00516 for ; Mon, 31 Aug 1998 23:02:16 GMT (envelope-from michaelh@cet.co.jp) Date: Tue, 1 Sep 1998 08:02:16 +0900 (JST) From: Michael Hancock To: FreeBSD-Hackers@FreeBSD.ORG Subject: Cable modem service in the Boston area Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSDers using cable modems in Boston, I'm going to balance my time between Tokyo and Boston starting this month and one of the requirements in Boston is cable modem service. Anyone out there using @Home? I'd like to hear experiences from anyone out there using the service and in what area of Boston. BTW, I'm a Boston newbie so I won't recognize a lot of city names, but I'll figure these out when I get there. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 16:17:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27077 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 16:17:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27070 for ; Mon, 31 Aug 1998 16:17:09 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA28903; Mon, 31 Aug 1998 16:16:06 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd028863; Mon Aug 31 16:16:03 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA11244; Mon, 31 Aug 1998 16:15:58 -0700 (MST) From: Terry Lambert Message-Id: <199808312315.QAA11244@usr01.primenet.com> Subject: Re: Weird sendmail/pop problem To: fullermd@futuresouth.com (Matthew D. Fuller) Date: Mon, 31 Aug 1998 23:15:58 +0000 (GMT) Cc: tlambert@primenet.com, don@whtech.com, hackers@FreeBSD.ORG In-Reply-To: <19980829012108.51411@futuresouth.com> from "Matthew D. Fuller" at Aug 29, 98 01:21:08 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You can't send mail over a POP3 connection, you can only retrieve it; > > you use SMTP to *send* mail. > > Before anyone else chimes in, there's some funky POP3 interface to send > mail to the server via it. Yes; that would be the expired ietf-draft which failed to be ratified, mostly because it was an abomination, and the rebirth of a similar draft, to wit: draft-hansen-pop3-xtndext-00.txt. This draft will, likewise, be struck down by all right-thinking IETF voters, because it fails to provide a mechanism for passing envelope-to and envelope-from information to the server, except in message headers, and messages headers are *DATA*. This draft seems to describe a sending interface better suited to sending SPAM than anoy other interface currently available today. Perhaps Aegis will implement this when they reinstate Sanford Wallace's Internet connection... > That said, it's still being DELIVERED through SMTP, so your point stands. > Here's my bet: > Try sending from the local box, not though POP3 > mail -s 'test msg' forwarduser < /dev/null > > See if that gets there (both theres). > Try (perhaps long shot, but *shrug*) killing sendmail and restarting it. Most likely, either the forward is incorrect, or the address refers to the same mailbox, and they are seen different behaviour based on either ruleset 4/5 differences and/or they are seeing that two connections are made for a virtual host when seen as a seperate MX via external DNS, but as local delivery by the internal. The information request I made stands; it is the minimum amount of information required to guarantee that someone can tell them what is going on. PS: If they are using draft-hansen-pop3-xtndext-00.txt or the earlier (expored) draft to send mail via POP, then they are being about as unconstructive as draft-myers-smtp-auth-11.txt and the draft that uses it for etrn: draft-gellens-on-demand-05.txt, which ignores the Best Known Practice of using Dynamic DNS and Split DNS so that standard ETRN will function with Dynamic IP. Balkanizing the Internet is not going to solve th SPAM problem, and Dynamic IP isn't going to solve the IPv4 address space problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 16:28:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29772 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 16:28:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29767 for ; Mon, 31 Aug 1998 16:28:24 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA22113; Mon, 31 Aug 1998 16:27:26 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd022095; Mon Aug 31 16:27:22 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA11677; Mon, 31 Aug 1998 16:27:20 -0700 (MST) From: Terry Lambert Message-Id: <199808312327.QAA11677@usr01.primenet.com> Subject: Re: Weird sendmail/pop problem To: don@whtech.com (Don O'Neil) Date: Mon, 31 Aug 1998 23:27:20 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <000101bdd379$abe29a20$0200010a@digerati.whtech.com> from "Don O'Neil" at Aug 29, 98 11:20:16 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, To correct my mis-statement, I do realize that SMTP is how the mail is > delivered, I was intending to point out that I was using a "standard" POP3 > type client for recieving, not something like IMAP.... Anyway... I've > checked the SMTP (sendmail) logs and the delivery is only made to one of the > two recipents, no matter what order the names are in the .forward file, my > name is allways skipped.... Now, my name is of course the one sending the > message... is there something in sendmail that knows I was the originator > and doesn't bother to send the message back to me? Now if I send a message > using mail or elm, or pine, or sendmail directly from the box (not using the > PC client) then both recipients get the message (I did this a root). Sendmail does not know you are the originator. The questions that would have been answered for me by the information I requested are: 1) What are the "MAIL FROM:" and "RCPT TO:" linces actually being sent to sendmail? 2) Are any of the addresses aliases for each other? If so, sendmail will realize this, and send only a single copy of the message to any one local maildrop. 3) Are you attempting to use "popclient" or "fetchmail" in "multidrop mode"? A) Fetchmail is broken, in that it searches for "any header" instead of "best header". B) You should use "X-Envelope-To". If you are using "qmail", you should use "Delivered-To" and "-qvirtual" to remove the domain prefix that qmail stupidly prepends to the "Delivered-To" name. C) If you can not use (A) or (B), then you should remove the "m" flag in the mailer doing delivery. This will result in a "Recieved ... by ... for ..." line, where "by ..." is by your MX, and "for ..." is for the addressee 4) If you are using the same mail client to donload from one or mor addresses, make sure you have not told it to get rid of mail you have "already seen". This is done by "Message-ID" in many instances, and will result in your mail client "hiding" the "duplicate" message. Of course, there is a hell of a lot more detail than this, and a hell of a lot more branch paths possible, depending on the other questions I didn't tell you that the data would answer, and varying by the mail clients, etc., that you are using. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 16:50:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03714 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 16:50:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from garbo.lodgenet.com (garbo.lodgenet.com [204.124.122.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA03709 for ; Mon, 31 Aug 1998 16:50:24 -0700 (PDT) (envelope-from johnp@lodgenet.com) Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.122.42]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id SAA04058; Mon, 31 Aug 1998 18:41:58 -0500 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.8.7/8.8.5) with ESMTP id SAA08131; Mon, 31 Aug 1998 18:48:38 -0500 (CDT) Message-Id: <199808312348.SAA08131@milo.lodgenet.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: don@whtech.com (Don O'Neil), freebsd-hackers@FreeBSD.ORG Subject: Re: Weird sendmail/pop problem In-reply-to: Your message of "Mon, 31 Aug 1998 23:27:20 -0000." <199808312327.QAA11677@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 18:48:37 -0500 From: John Prince Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all.. How about removing the comment from the following in the sendmail.cf file?? #O MeToo --John Prince Terry Lambert writes: > > Well, To correct my mis-statement, I do realize that SMTP is how the mail i s > > delivered, I was intending to point out that I was using a "standard" POP3 > > type client for recieving, not something like IMAP.... Anyway... I've > > checked the SMTP (sendmail) logs and the delivery is only made to one of th e > > two recipents, no matter what order the names are in the .forward file, my > > name is allways skipped.... Now, my name is of course the one sending the > > message... is there something in sendmail that knows I was the originator > > and doesn't bother to send the message back to me? Now if I send a message > > using mail or elm, or pine, or sendmail directly from the box (not using th e > > PC client) then both recipients get the message (I did this a root). > > Sendmail does not know you are the originator. > > The questions that would have been answered for me by the information > I requested are: > > 1) What are the "MAIL FROM:" and "RCPT TO:" linces actually > being sent to sendmail? > > 2) Are any of the addresses aliases for each other? If so, > sendmail will realize this, and send only a single copy > of the message to any one local maildrop. > > 3) Are you attempting to use "popclient" or "fetchmail" in > "multidrop mode"? > > A) Fetchmail is broken, in that it searches for > "any header" instead of "best header". > > B) You should use "X-Envelope-To". If you are > using "qmail", you should use "Delivered-To" > and "-qvirtual" to remove the domain prefix > that qmail stupidly prepends to the "Delivered-To" > name. > > C) If you can not use (A) or (B), then you should > remove the "m" flag in the mailer doing delivery. > This will result in a "Recieved ... by ... for ..." > line, where "by ..." is by your MX, and "for ..." > is for the addressee > > 4) If you are using the same mail client to donload from > one or mor addresses, make sure you have not told it to > get rid of mail you have "already seen". This is done > by "Message-ID" in many instances, and will result in > your mail client "hiding" the "duplicate" message. > > Of course, there is a hell of a lot more detail than this, and a > hell of a lot more branch paths possible, depending on the other > questions I didn't tell you that the data would answer, and varying > by the mail clients, etc., that you are using. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 17:05:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05978 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 17:05:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05973 for ; Mon, 31 Aug 1998 17:05:34 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-119.camalott.com [208.229.74.119]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id TAA04098; Mon, 31 Aug 1998 19:06:15 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id TAA11451; Mon, 31 Aug 1998 19:04:23 -0500 (CDT) (envelope-from joelh) Date: Mon, 31 Aug 1998 19:04:23 -0500 (CDT) Message-Id: <199809010004.TAA11451@detlev.UUCP> To: mike@smith.net.au CC: avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG In-reply-to: <199808310953.JAA20742@word.smith.net.au> (message from Mike Smith on Mon, 31 Aug 1998 09:53:00 +0000) Subject: Re: TCP performance. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808310953.JAA20742@word.smith.net.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Having said that, bear in mind that the 'zp' driver is a bandaid > that only exists to aid installation, and you may well be better off > using the 'ep' driver inside the pccard framework. The ep driver still leaks like a sieve, or did two weeks ago or so. I haven't gotten to work on it yet. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 17:11:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06836 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 17:11:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06830 for ; Mon, 31 Aug 1998 17:11:06 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-119.camalott.com [208.229.74.119]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id TAA04450; Mon, 31 Aug 1998 19:11:26 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id TAA11460; Mon, 31 Aug 1998 19:08:58 -0500 (CDT) (envelope-from joelh) Date: Mon, 31 Aug 1998 19:08:58 -0500 (CDT) Message-Id: <199809010008.TAA11460@detlev.UUCP> To: bright@hotjobs.com CC: matthew@wolfepub.com, hackers@FreeBSD.ORG In-reply-to: (message from Alfred Perlstein on Mon, 31 Aug 1998 15:41:29 -0500 (EST)) Subject: Re: Environment of a process From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Where does a process get its environment if it is not executed from the >> command line? I have a program that connects to a database and relies on >> several ENV VARS to be set. > man exec, look at: > int exect(const char *path, char *const argv[], char *const envp[]) > also note getenv(3), man 3 getenv You can also use setenv, preferably between the fork and exec. (There was recently a thread about a memory leak if this is done frequently, tho. I don't know the details.) Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 17:17:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08314 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 17:17:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08295 for ; Mon, 31 Aug 1998 17:17:51 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id RAA23825; Mon, 31 Aug 1998 17:15:46 -0700 (PDT) (envelope-from dhw) Date: Mon, 31 Aug 1998 17:15:46 -0700 (PDT) From: David Wolfskill Message-Id: <199809010015.RAA23825@pau-amma.whistle.com> To: johnp@lodgenet.com, tlambert@primenet.com Subject: Re: Weird sendmail/pop problem Cc: don@whtech.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808312348.SAA08131@milo.lodgenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 31 Aug 1998 18:48:37 -0500 >From: John Prince >How about removing the comment from the following in the sendmail.cf file?? >#O MeToo For your own installation? Sure, do as you please (though I encourage you to read below). As a default? I don't recommend it, for POLA, if nothing else (at least, it would be POLA for those of us who have been using UNIX & sendmail for... well, a while...). That said, even the admittedly primitive MUA called "mail" allows an individual invoker to override the system default "MeToo" setting -- from "man mail": metoo Usually, when a group is expanded that contains the sender, the sender is removed from the expansion. Setting this option causes the sender to be included in the group. If other MUAs fail to implement the feature, and it's wanted, either change the MUAs in question or switch to MUAs that more nearly meet your needs. Or go ahead and switch your installation default, but you might want to let your anyone who might be using the machines in question know ahead of time. (You may note that I'm looking at this from a perspective that assumes that such changes may well affect a number of people, typically >>1.) And please note that sendmail provides a way to turn the "metoo" feature *on* via the command line, but does not (as far as I know) provide a way to turn it *off* via the command line. Another reason for not changing it (which may well be a borderline religious issue, but life's like that sometimes) is that changing the sendmail.cf isn't something I'll recommend, period. I would recommend changing the .mc file & re-generating the sendmail.cf, if there's a reasonable change that's wanted in the sendmail.cf. There's a way to accomplish the stated objective via the .mc files; it's documented iin the 2nd ed. Bat book. (BTW, that documentation also mentions some additional reasons to leave the option turned off by default.) Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 17:21:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09223 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 17:21:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from moebius.space.net (moebius.Space.Net [195.30.1.25]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA09203 for ; Mon, 31 Aug 1998 17:21:01 -0700 (PDT) (envelope-from maex@Space.Net) Received: (qmail 551 invoked by uid 1013); 1 Sep 1998 00:20:01 -0000 Message-ID: <19980901022000.V26849@space.net> Date: Tue, 1 Sep 1998 02:20:00 +0200 From: Markus Stumpf To: Kelly Yancey , freebsd-hackers@FreeBSD.ORG Subject: Re: determining an X window ID? References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW" X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kelly Yancey on Sat, Aug 29, 1998 at 03:55:41AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii On Sat, Aug 29, 1998 at 03:55:41AM -0400, Kelly Yancey wrote: > I have written a fairly short shell script to launch xmcd which first > checks to see if any other cd player is already running and if so, does > not launch another instance of xmcd (for when I click on the wrong thing > :) ) > Anyway, I'm running fvwm2 and thought it would sure be nice if I could > somehow have the script bring the already running cd player to the > foreground...kind of a "Here it dummy" response. It's starting to look > like this seemingly simple task is anything but. 2 things: 1) there is a programm called "xlsclients" which shows you all the clients currently using your X Server (even remote ones). This may be a better way to check for the xmcd. 2) I'll attach a small programm (xselraise.c) and a Imakefile (use xmkmf to create a Makefile). Hope that is ok with the charter of the list, as it is only about 80 lines. The program take a CLASS name (i.e. 'XMcd' for xmcd) and raises it. Note: as it raises all windows with that class, it will also raise all the popups (if mapped). You can easily modify it to take names instead of classes (wrote this a while back to raise all "xload"s) by changing the code at line 30 from if (strcmp(to_raise, class_hint.res_class) == 0) { to if (strcmp(to_raise, class_hint.res_name) == 0) { You could aso play with the return code to keep track whether it found a window to raise or not und thus get rid of xlsclients/ps. Hope thats helps! \Maex Mit freundlichen Gruessen Markus Stumpf -- SpaceNet GmbH | http://www.Space.Net/ | In a world whithout Research & Development | mailto:research@Space.Net | walls and fences, Frankfurter Ring 193a | Tel: +49 (89) 32356-0 | who needs D-80807 Muenchen | Fax: +49 (89) 32356-299 | Windows and Gates? --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=Imakefile SRCS = xselraise.c OBJS = xselraise.o # DEPLIBS = XawClientDepLibs LOCAL_LIBRARIES = XawClientLibs ComplexProgramTarget(xselraise) --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xselraise.c" #include #include #include #include Atom _XA_WM_PROTOCOLS; char *to_raise; void RaiseIt(dpy, window) Display *dpy; Window window; { XRaiseWindow(dpy, window); XFlush(dpy); } void ParseTree(dpy, parent) Display *dpy; Window parent; { Window *children, root_return, parent_return; unsigned int num_children, i; char *win_name; XClassHint class_hint; if(XGetClassHint(dpy, parent, &class_hint)) { if (strcmp(to_raise, class_hint.res_class) == 0) { printf("raising %s \n", class_hint.res_name); RaiseIt(dpy, parent); } XFree(class_hint.res_class); XFree(class_hint.res_name); } else { XQueryTree(dpy, parent, &root_return, &parent_return, &children , &num_children); for(i = 0; i < num_children; i++) ParseTree(dpy, children[i]); } } main(argc, argv) int argc; char **argv; { Display *dpy ; if( ( dpy = XOpenDisplay(NULL) ) == NULL ) { fprintf( stderr, "Can't open display !\n" ); exit(1); } if (argc != 2) { fprintf(stderr, "%s: class to raise expected\n", argv[0]); exit(1); } to_raise = argv[1]; _XA_WM_PROTOCOLS = XInternAtom (dpy, "WM_PROTOCOLS", False); ParseTree(dpy, DefaultRootWindow(dpy)); exit(0); } --0F1p//8PRICkK4MW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 17:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11388 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 17:31:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11378 for ; Mon, 31 Aug 1998 17:31:38 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id SAA05448; Mon, 31 Aug 1998 18:24:19 -0600 (MDT) Date: Mon, 31 Aug 1998 18:24:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809010024.SAA05448@narnia.plutotech.com> To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: Call for testers for new ThunderLAN driver Newsgroups: pluto.freebsd.hackers In-Reply-To: <199808311728.NAA04332@skynet.ctr.columbia.edu> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - Added code to raise the PCI latency timer value all the way up, as > recommended by the manual. Please don't do this (at least not by default). If the PCI bus is idle, the card will be able to burst as long as it wants. If the PCI bus isn't very idle, the other devices on the bus will experience un-fair latency because your driver has unilaterally decide that it deserves more bus time than everyone else. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 18:04:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18622 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 18:04:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from garbo.lodgenet.com (garbo.lodgenet.com [204.124.122.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA18603 for ; Mon, 31 Aug 1998 18:04:22 -0700 (PDT) (envelope-from johnp@lodgenet.com) Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.122.42]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id TAA04676; Mon, 31 Aug 1998 19:55:51 -0500 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.8.7/8.8.5) with ESMTP id UAA22256; Mon, 31 Aug 1998 20:02:32 -0500 (CDT) Message-Id: <199809010102.UAA22256@milo.lodgenet.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: David Wolfskill cc: johnp@lodgenet.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Weird sendmail/pop problem In-reply-to: Your message of "Mon, 31 Aug 1998 17:15:46 PDT." <199809010015.RAA23825@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 20:02:31 -0500 From: John Prince Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thats Understandable. and I do mostly agree.. however I feel your general reply was a bit Pretentious. Not knowing the full situation, only the problem as described, it appears to me the mail is not created during an alias expansion for the original sender. If there is a better way I am "humbly" all ears.. How would you suggest it be corrected? --John Prince David Wolfskill writes: > >Date: Mon, 31 Aug 1998 18:48:37 -0500 > >From: John Prince > > >How about removing the comment from the following in the sendmail.cf file?? > >#O MeToo > > For your own installation? Sure, do as you please (though I encourage > you to read below). > > As a default? I don't recommend it, for POLA, if nothing else (at > least, it would be POLA for those of us who have been using UNIX & > sendmail for... well, a while...). > > That said, even the admittedly primitive MUA called "mail" allows an > individual invoker to override the system default "MeToo" setting -- > from "man mail": > > metoo Usually, when a group is expanded that contains the sender, the > sender is removed from the expansion. Setting this option cause s > the sender to be included in the group. > > > If other MUAs fail to implement the feature, and it's wanted, either > change the MUAs in question or switch to MUAs that more nearly meet your > needs. Or go ahead and switch your installation default, but you might > want to let your anyone who might be using the machines in question > know ahead of time. (You may note that I'm looking at this from a > perspective that assumes that such changes may well affect a number of > people, typically >>1.) > > And please note that sendmail provides a way to turn the "metoo" feature > *on* via the command line, but does not (as far as I know) provide a way > to turn it *off* via the command line. > > Another reason for not changing it (which may well be a borderline > religious issue, but life's like that sometimes) is that changing the > sendmail.cf isn't something I'll recommend, period. I would recommend > changing the .mc file & re-generating the sendmail.cf, if there's a > reasonable change that's wanted in the sendmail.cf. There's a way to > accomplish the stated objective via the .mc files; it's documented iin > the 2nd ed. Bat book. (BTW, that documentation also mentions some > additional reasons to leave the option turned off by default.) > > Cheers, > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 18:10:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19892 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 18:10:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19868 for ; Mon, 31 Aug 1998 18:10:39 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-119.camalott.com [208.229.74.119]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id UAA08536; Mon, 31 Aug 1998 20:11:08 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id UAA11696; Mon, 31 Aug 1998 20:09:07 -0500 (CDT) (envelope-from joelh) Date: Mon, 31 Aug 1998 20:09:07 -0500 (CDT) Message-Id: <199809010109.UAA11696@detlev.UUCP> To: freebsd-hackers@FreeBSD.ORG Subject: Use of metric From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do I remember hearing some caveats about the use of ifconfig's metric under FreeBSD? Another question: Is there a reason that the following sequence: ifconfig ep0 inet 192.168.13.3 netmask 255.255.255.0 down ifconfig ed0 inet 192.168.13.1 netmask 255.255.255.0 configures ep0 to be the selected interface? More to the point, would it be useful if I made the changes to cause interfaces configured as down to not go into the routing table at configuration time? Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 19:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03229 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 19:47:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jazz.snu.ac.kr (jazz.snu.ac.kr [147.46.59.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03218 for ; Mon, 31 Aug 1998 19:46:59 -0700 (PDT) (envelope-from junker@jazz.snu.ac.kr) Received: (from junker@localhost) by jazz.snu.ac.kr (8.9.0/8.9.0) id LAA06371; Tue, 1 Sep 1998 11:46:05 +0900 (KST) To: freebsd-hackers@FreeBSD.ORG Subject: Aladdin Ghostscript License and FreeBSD CD? From: CHOI Junho Date: 01 Sep 1998 11:46:04 +0900 Message-ID: Lines: 61 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Recently I investigated versions of ghostscript in free Unix. All Linux distributions I found(Redhat, Debian, Slackware) have GNU ghostscript(4.03), but BSD variants(FreeBSD, OpenBSD, NetBSD) have Aladdin ghostscript(5.10) and other GNU ghostscripts sometimes. Is there a special reason to this? What reason prevents Linux from distributing Aladdin ghostscripts? So I read Aladdin Licenses(doc/PUBLIC in Aladdin ghostscript distribution). Here is part of the file(PUBLIC): 2. Restrictions. This license is subject to the following restrictions: (a) Distribution of the Program or any work based on the Program by a commercial organization to any third party is prohibited if any payment is made in connection with such distribution, whether directly (as in payment for a copy of the Program) or indirectly (as in payment for some service related to the Program, or payment for some product or service that includes a copy of the Program "without charge"; these are only examples, and not an exhaustive enumeration of prohibited activities). The following methods of distribution involving payment shall not in and of themselves be a violation of this restriction: (i) Posting the Program on a public access information storage and retrieval service for which a fee is received for retrieving information (such as an on-line service), provided that the fee is not content-dependent (i.e., the fee would be the same for retrieving the same volume of information consisting of random data) and that access to the service and to the Program is available independent of any other product or service. An example of a service that does not fall under this section is an on-line service that is operated by a company and that is only available to customers of that company. (This is not an exhaustive enumeration.) (ii) Distributing the Program on removable computer-readable media, provided that the files containing the Program are reproduced entirely and verbatim on such media, that all information on such media be redistributable for non-commercial purposes without charge, and that such media are distributed by themselves (except for accompanying documentation) independent of any other product or service. Examples of such media include CD-ROM, magnetic tape, and optical storage media. (This is not intended to be an exhaustive list.) An example of a distribution that does not fall under this section is a CD-ROM included in a book or magazine. (This is not an exhaustive enumeration.) According to 2-(a)-(i), I think Aladdin ghostscript on FreeBSD FTP mirrors are ok. (it is public access), but according to 2-(a)-(ii), FreeBSD CD-ROM may have a problem. Walnet Creek CDROM is not a product of Walnet Creek? And "The Complete FreeBSD"(with books) doesn't violate 2-(a)-(ii)? I have WC CDROM(2.2.1, 2.2.5), but it has all the gs5.10 variants on the CD. -- ----Cool FreeBSD!----MSX Forever!---J.U.N.K.E.R/Beat Snatchers!---- CHOI Junho http://jazz.snu.ac.kr/~junker Distributed Computing System Lab,CS Dept.,Seoul National Univ., ROK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 20:49:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08992 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 20:49:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08981 for ; Mon, 31 Aug 1998 20:49:15 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for freebsd-hackers@freebsd.org id 0zDhQg-0000td-00; Mon, 31 Aug 1998 22:48:26 -0500 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: disk going bad? To: freebsd-hackers@FreeBSD.ORG Date: Mon, 31 Aug 1998 22:48:26 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I don't suppose I can just mark a sector as bad on a SCSI drive, can I? (da1:ahc1:0:0:0): READ(10). CDB: 28 0 0 95 c0 20 0 0 e 0 (da1:ahc1:0:0:0): MEDIUM ERROR info:95c02b asc:11,0 (da1:ahc1:0:0:0): Unrecovered read error Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNetuijeRhT8JRySpAQFaNgQArrmwKXHF17Y6K08FkfzO+5OEJX4tg9AJ VGZ2z4zNzYBpqs45o2PkfQf93OibevSRjI8Jdw9u1cADfFWOKa3tr0gJ7KDlJPNT jrrTkQ7xu1p1MpozlMWO6tbE+hTiRWD+GEdorAWgRruR2ctn8fGOHUE/+b3M/7gg sCLrDe27oFE= =hEfY -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 21:16:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12447 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 21:16:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12438 for ; Mon, 31 Aug 1998 21:16:33 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt1-58.HiWAAY.net [208.147.147.58]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id XAA11449 for ; Mon, 31 Aug 1998 23:15:33 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id TAA04928 for ; Mon, 31 Aug 1998 19:07:37 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199809010007.TAA04928@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG From: David Kelly Subject: Re: 64k physio limit In-reply-to: Message from Warner Losh of "Mon, 31 Aug 1998 00:23:26 MDT." <199808310623.AAA01070@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 19:07:37 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > Is there any way to get a larger I/O to happen than 64k? I have a tape > drive that would be happiest if I could do 256kish writes to it at a time, > rather than only 64k. I'd like to see this also too. People keep handing me 4mm DDS tapes from SGI systems written in 256k blocks. Even 8mm defaults to 128k on SGI. Then there is another user who thinks writting 1024k (megabyte) blocksize is fun. Well there's little hope for that last guy, but support for 256k tape blocks would let me place FreeBSD machines where none are currently. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 21:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16390 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 21:44:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16375 for ; Mon, 31 Aug 1998 21:44:06 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id VAA00572; Mon, 31 Aug 1998 21:41:06 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808312141.VAA00572@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Jacques Vidrine cc: freebsd-hackers@FreeBSD.ORG Subject: Re: disk going bad? In-reply-to: Your message of "Mon, 31 Aug 1998 22:48:26 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Aug 1998 21:41:05 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----BEGIN PGP SIGNED MESSAGE----- > > I don't suppose I can just mark a sector as bad on a SCSI > drive, can I? > > (da1:ahc1:0:0:0): READ(10). CDB: 28 0 0 95 c0 20 0 0 e 0 > (da1:ahc1:0:0:0): MEDIUM ERROR info:95c02b asc:11,0 > (da1:ahc1:0:0:0): Unrecovered read error Yup. It's a bit convoluted, but start by using the 'camcontrol' command to set ARRE and AWRE to 1. Use the syntax as for the example editing the read-write error control page in the scsi(8) manpage, and harrass Ken Merry to write a manpage for camcontrol. 8) Then you need to arrange to write to the sector; you can do this a number of ways, depending on the disk in question. If you can back everything up and dd over the entire disk or partition, that's the simplest way to go. Failing that, if the defect is in the data area of a file, delete it. When the block is reused, the drive will spare it out. You can use 'badsect' to work out where the block is; give it the 'fsbn' value from the console error message. If it's willing to spare the block, then it's in a file, and when you fsck the filesystem, you can decide if you want to keep it. (See badsect(8) for more details.) If the block is in a critical area, then you really do have to rebuild the filesystem from scratch. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 22:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22438 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 22:35:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22432 for ; Mon, 31 Aug 1998 22:35:47 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA21891; Mon, 31 Aug 1998 22:34:30 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: CHOI Junho cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Aladdin Ghostscript License and FreeBSD CD? In-reply-to: Your message of "01 Sep 1998 11:46:04 +0900." Date: Mon, 31 Aug 1998 22:34:29 -0700 Message-ID: <21888.904628069@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > exhaustive enumeration of prohibited activities). The following methods of > distribution involving payment shall not in and of themselves be a violation > of this restriction: > > (ii) Distributing the Program on removable computer-readable media, > provided that the files containing the Program are reproduced entirely and > verbatim on such media, that all information on such media be > redistributable for non-commercial purposes without charge, and that such > media are distributed by themselves (except for accompanying documentation) > independent of any other product or service. Examples of such media includ Sounds like a FreeBSD CD to me. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 31 23:20:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27222 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 23:20:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27217 for ; Mon, 31 Aug 1998 23:20:44 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA08618 for ; Tue, 1 Sep 1998 15:49:42 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 01 Sep 1998 15:49:42 +0930 (CST) From: "Daniel O'Connor" To: freebsd-hackers@FreeBSD.ORG Subject: Thread calls Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is anyone working on the threads stuff at the moment? I am porting eMusic (a very nice wav, mp3, etc player) but it wants some thread calls. It wants the following - pthread_setcancelstate() pthread_setcanceltype() pthread_testcancel() I think that's all the ones I commented out to get it to compile.. (I'd do a diff, but the HD the source is on is now dying.. a tale of woe ;) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 00:26:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04533 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 00:26:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jazz.snu.ac.kr (jazz.snu.ac.kr [147.46.59.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04522 for ; Tue, 1 Sep 1998 00:26:13 -0700 (PDT) (envelope-from junker@jazz.snu.ac.kr) Received: (from junker@localhost) by jazz.snu.ac.kr (8.9.0/8.9.0) id QAA07986; Tue, 1 Sep 1998 16:25:04 +0900 (KST) To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Aladdin Ghostscript License and FreeBSD CD? References: <21888.904628069@time.cdrom.com> From: CHOI Junho Date: 01 Sep 1998 16:25:04 +0900 In-Reply-To: "Jordan K. Hubbard"'s message of "Mon, 31 Aug 1998 22:34:29 -0700" Message-ID: Lines: 28 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Jordan" == Jordan K Hubbard writes: > (ii) Distributing the Program on removable > computer-readable media, provided that the files containing the > Program are reproduced entirely and verbatim on such media, that > all information on such media be redistributable for > non-commercial purposes without charge, and that such media are > distributed by themselves (except for accompanying > documentation) independent of any other product or service. > Examples of such media include CD-ROM, magnetic tape, and Jordan> Sounds like a FreeBSD CD to me. How about this? (after your quotation of my original mail) > optical storage media. (This is not intended to be an > exhaustive list.) An example of a distribution that does not > fall under this section is a CD-ROM included in a book or > magazine. (This is not an exhaustive enumeration.) I agree on WC FreeBSD CDROM set. But CD with books("The Complete FreeBSD") or some FreeBSD cover CD of magazines in the world may have a problem I think. Do I misunderstand? -- ----Cool FreeBSD!----MSX Forever!---J.U.N.K.E.R/Beat Snatchers!---- CHOI Junho http://jazz.snu.ac.kr/~junker Distributed Computing System Lab,CS Dept.,Seoul National Univ., ROK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 00:47:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06776 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 00:47:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06771 for ; Tue, 1 Sep 1998 00:47:08 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA01330; Tue, 1 Sep 1998 00:46:06 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: CHOI Junho cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Aladdin Ghostscript License and FreeBSD CD? In-reply-to: Your message of "01 Sep 1998 16:25:04 +0900." Date: Tue, 01 Sep 1998 00:46:06 -0700 Message-ID: <1326.904635966@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > exhaustive list.) An example of a distribution that does not > > fall under this section is a CD-ROM included in a book or > > magazine. (This is not an exhaustive enumeration.) > > I agree on WC FreeBSD CDROM set. But CD with books("The Complete > FreeBSD") or some FreeBSD cover CD of magazines in the world may have > a problem I think. Do I misunderstand? I still think that "The Complete FreeBSD" still falls squarely under the category of "accompanying docs" rather than the context in which I believe Aladdin meant it. They don't want publishers like SAMS just slipping a "Ghoscript CD!" into one of their generic books on publishing as an add-on bonus, but they don't mind it going into legitimate, self-sufficient CD products which may (optionally) also have some printed documentation available. The case where it's a cover disk for some magazine is, indeed, specifically excluded I see now and I'd say that's reason alone to just mark Ghostcript 5x as "NO_CDROM" from this point onwards, my reasoning being that we *like* FreeBSD going out on people's magazine covers and it's frequently the easiest thing for Walnut Creek CDROM to do to give them CD #1 of whatever FreeBSD product they currently have and suggest that as the cover disc. I'd hate to lose that flexibility over one package. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 01:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11956 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 01:30:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11950 for ; Tue, 1 Sep 1998 01:30:43 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA08835; Tue, 1 Sep 1998 08:34:11 +0200 From: Luigi Rizzo Message-Id: <199809010634.IAA08835@labinfo.iet.unipi.it> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 1 Sep 1998 08:34:10 +0200 (MET DST) Cc: junker@jazz.snu.ac.kr, freebsd-hackers@FreeBSD.ORG In-Reply-To: <1326.904635966@time.cdrom.com> from "Jordan K. Hubbard" at Sep 1, 98 00:45:47 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > exhaustive list.) An example of a distribution that does not > > > fall under this section is a CD-ROM included in a book or > > > magazine. (This is not an exhaustive enumeration.) ... Perhaps a word of clarification from Aladdin would be useful. In fact i see two clauses (in bold down) which i think are relevant to the magazine case: > (ii) Distributing the Program on removable computer-readable media, > provided that the files containing the Program are reproduced entirely and > verbatim on such media, THAT ALL INFORMATION ON SUCH MEDIA BE > REDISTRIBUTABLE FOR NON-COMMERCIAL PURPOSES WITHOUT CHARGE, and that SUCH > MEDIA ARE DISTRIBUTED BY THEMSELVES (EXCEPT FOR ACCOMPANYING DOCUMENTATION) > INDEPENDENT OF ANY OTHER PRODUCT OR SERVICE. Examples of such media include > CD-ROM, magnetic tape, and optical storage media. (This is not intended to > be an exhaustive list.) An example of a distribution that does not fall > under this section is a CD-ROM included in a book or magazine. (This is not > an exhaustive enumeration.) now the first one is no problem for the FreeBSD CD#1 and i think it is there just because people tend to stick a restrictive copyright on everything. E.g. one of the think i have to make clear to the libraries i send the 2.2.6 CDs that WC generously donated (thanks again!) is that people _CAN_ copy the content of the disks. The second one is a bit more critical i agree, but killing 5.10 from the CD set is a bit overkill. Can you make it go into another disk (not #1) of the set instead ? I think a time will come (if not already there) when all packages will just not fit into disk#1. > The case where it's a cover disk for some magazine is, indeed, > specifically excluded I see now and I'd say that's reason alone to > just mark Ghostcript 5x as "NO_CDROM" from this point onwards, my > reasoning being that we *like* FreeBSD going out on people's magazine > covers and it's frequently the easiest thing for Walnut Creek CDROM to > do to give them CD #1 of whatever FreeBSD product they currently have > and suggest that as the cover disc. I'd hate to lose that flexibility > over one package. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 01:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13156 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 01:41:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13149 for ; Tue, 1 Sep 1998 01:41:46 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA26056; Tue, 1 Sep 1998 10:40:41 +0200 (MET DST) Date: Tue, 1 Sep 1998 10:40:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: "Jordan K. Hubbard" cc: FreeBSD hackers mailing list Subject: Re: Aladdin Ghostscript License and FreeBSD CD? In-Reply-To: <1326.904635966@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The case where it's a cover disk for some magazine is, indeed, > specifically excluded I see now and I'd say that's reason alone to > just mark Ghostcript 5x as "NO_CDROM" from this point onwards, my > reasoning being that we *like* FreeBSD going out on people's magazine > covers and it's frequently the easiest thing for Walnut Creek CDROM to > do to give them CD #1 of whatever FreeBSD product they currently have > and suggest that as the cover disc. I'd hate to lose that flexibility > over one package. This last remark is an eye opener. I fully agree. Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 02:53:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19985 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 02:53:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA19977 for ; Tue, 1 Sep 1998 02:53:25 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA08942 for hackers@freebsd.org; Tue, 1 Sep 1998 09:57:21 +0200 From: Luigi Rizzo Message-Id: <199809010757.JAA08942@labinfo.iet.unipi.it> Subject: kernel sysctl interface question... To: hackers@FreeBSD.ORG Date: Tue, 1 Sep 1998 09:57:20 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i notice that some (static) kernel data structures are exported to user space using the sysctl interface, and that makes life easy for programs that want to access these things -- examples are statistics etc. Now, i wonder if (and then how) i can use the same interface for exporting dynamic data structures, e.g. things like "struct ifnet" which are allocated more or less dynamically. thanks luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 05:49:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07933 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 05:49:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07926 for ; Tue, 1 Sep 1998 05:49:41 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-120.camalott.com [208.229.74.120]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id HAA06529; Tue, 1 Sep 1998 07:50:23 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id HAA02001; Tue, 1 Sep 1998 07:48:30 -0500 (CDT) (envelope-from joelh) Date: Tue, 1 Sep 1998 07:48:30 -0500 (CDT) Message-Id: <199809011248.HAA02001@detlev.UUCP> To: jkh@time.cdrom.com CC: junker@jazz.snu.ac.kr, freebsd-hackers@FreeBSD.ORG In-reply-to: <21888.904628069@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Aladdin Ghostscript License and FreeBSD CD? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <21888.904628069@time.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> (ii) Distributing the Program on removable computer-readable media, >> provided that the files containing the Program are reproduced >> entirely and verbatim on such media, that all information on such >> media be redistributable for non-commercial purposes without >> charge, and that such media are distributed by themselves (except >> for accompanying documentation) independent of any other product or >> service. Examples of such media includ > Sounds like a FreeBSD CD to me. Would the "other product or service" clause refer to FreeBSD? That is, is this a "no bundling" bit? -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 06:13:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10416 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 06:13:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10405; Tue, 1 Sep 1998 06:13:11 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id PAA04090; Tue, 1 Sep 1998 15:11:16 +0200 (CEST) (envelope-from sos) Message-Id: <199809011311.PAA04090@sos.freebsd.dk> Subject: Test dont read! To: current@FreeBSD.ORG (FreeBSD current), hackers@FreeBSD.ORG (FreeBSD hackers) Date: Tue, 1 Sep 1998 15:11:16 +0200 (CEST) From: Sřren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Sřren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 06:24:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11660 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 06:24:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11655 for ; Tue, 1 Sep 1998 06:24:52 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id IAA31017; Tue, 1 Sep 1998 08:23:42 -0500 (CDT) Date: Tue, 1 Sep 1998 08:23:42 -0500 (CDT) From: Mark Tinguely Message-Id: <199809011323.IAA31017@plains.NoDak.edu> To: doconnor@gsoft.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: Thread calls Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the PMPTHREADS package (http://www.humanfactor.com/pthreads/) has the pthread_setcancelstate(), pthread_setcanceltype(), and pthread_testcancel() routines you require. --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 06:42:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14110 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 06:42:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14081 for ; Tue, 1 Sep 1998 06:42:31 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id PAA05777 for hackers@freebsd.org; Tue, 1 Sep 1998 15:40:35 +0200 (CEST) (envelope-from sos) Message-Id: <199809011340.PAA05777@sos.freebsd.dk> Subject: Test, ignore! To: hackers@FreeBSD.ORG (FreeBSD hackers) Date: Tue, 1 Sep 1998 15:40:35 +0200 (CEST) From: Sřren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Sřren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 07:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18570 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 07:14:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18561 for ; Tue, 1 Sep 1998 07:14:27 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA13741; Tue, 1 Sep 1998 16:06:40 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id KAA06341; Tue, 1 Sep 1998 10:17:49 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199809010817.KAA06341@semyam.dinoco.de> To: joelh@gnu.org cc: bright@hotjobs.com, matthew@wolfepub.com, hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Environment of a process In-reply-to: Your message of "Mon, 31 Aug 1998 19:08:58 CDT." <199809010008.TAA11460@detlev.UUCP> Date: Tue, 01 Sep 1998 10:17:49 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You can also use setenv, preferably between the fork and exec. (There > was recently a thread about a memory leak if this is done frequently, > tho. I don't know the details.) It was in freebsd-current where you might have seen this lately. The problem is that setenv doesn't free the memory used by the old value. Done between fork and exec it is of no importance as due to the exec the VM of the process where it leaked goes away. It then just leaks in the child process and that only lasts till exec. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 09:14:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03284 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 09:14:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03272 for ; Tue, 1 Sep 1998 09:14:29 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id JAA26728; Tue, 1 Sep 1998 09:12:19 -0700 (PDT) (envelope-from dhw) Date: Tue, 1 Sep 1998 09:12:19 -0700 (PDT) From: David Wolfskill Message-Id: <199809011612.JAA26728@pau-amma.whistle.com> To: dhw@whistle.com, johnp@lodgenet.com Subject: Re: Weird sendmail/pop problem Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809010102.UAA22256@milo.lodgenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 31 Aug 1998 20:02:31 -0500 >From: John Prince >Not knowing the full situation, only the problem as described, it >appears to me the mail is not created during an alias expansion for >the original sender. >If there is a better way I am "humbly" all ears.. >How would you suggest it be corrected? First, it's not clear that "mail not created during alias expansion" is, in and of itself, a problem. Second, if that *is* perceived to be a problem in a particular set of circumstances, sendmail provides a way to override the default behavior: ensure that the agent that invokes sendmail does so with the "-m" command-line flag. [I'll grant you that this doesn't seem to be documented in the sendmail man page. It's in the source, which is available, and it's alluded to in the man page for "mail". That might be fixed in sendmail 8.9.1; I'm currently running 8.8.8 internally. If it's not fixed in 8.9.1, perhaps someone might want to suggest a patch for the man page to the folks at sendmail.org.] Further, it would appear that the basic issue is that in this case, someone is injecting mail into a system in such a way that sendmail is being told (by the "-f" flag, if I recall correctly) what the sender's identity is. Since the alias expansion includes an address that matches this address (the one specified by "-f"), sendmail is, as usual, suppressing the generation of a likely superfluous copy, as the sender is presumed to be able to make copies, or specifically request (via Cc: or Bcc:, for example) a copy. And in the more general case, it's possible to use a tool such as majordomo, in which case the usual arrangement is that the "sender" name is set to the name of the list (administrator), so all messages to the list would get sent to all members of the list -- even the originator. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 09:20:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04562 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 09:20:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from garbo.lodgenet.com (garbo.lodgenet.com [204.124.122.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA04556 for ; Tue, 1 Sep 1998 09:20:29 -0700 (PDT) (envelope-from johnp@lodgenet.com) Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.122.42]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id LAA11257; Tue, 1 Sep 1998 11:11:54 -0500 Received: from milo.lodgenet.com (localhost [127.0.0.1]) by milo.lodgenet.com (8.8.7/8.8.5) with ESMTP id LAA20272; Tue, 1 Sep 1998 11:18:37 -0500 (CDT) Message-Id: <199809011618.LAA20272@milo.lodgenet.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: David Wolfskill cc: johnp@lodgenet.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Weird sendmail/pop problem In-reply-to: Your message of "Tue, 01 Sep 1998 09:12:19 PDT." <199809011612.JAA26728@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 11:18:36 -0500 From: John Prince Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I Agree... --john David Wolfskill writes: > >Date: Mon, 31 Aug 1998 20:02:31 -0500 > >From: John Prince > > >Not knowing the full situation, only the problem as described, it > >appears to me the mail is not created during an alias expansion for > >the original sender. > > >If there is a better way I am "humbly" all ears.. > > >How would you suggest it be corrected? > > First, it's not clear that "mail not created during alias expansion" is, > in and of itself, a problem. > > Second, if that *is* perceived to be a problem in a particular set of > circumstances, sendmail provides a way to override the default > behavior: ensure that the agent that invokes sendmail does so with the > "-m" command-line flag. [I'll grant you that this doesn't seem to be > documented in the sendmail man page. It's in the source, which is > available, and it's alluded to in the man page for "mail". That might > be fixed in sendmail 8.9.1; I'm currently running 8.8.8 internally. If > it's not fixed in 8.9.1, perhaps someone might want to suggest a patch > for the man page to the folks at sendmail.org.] > > Further, it would appear that the basic issue is that in this case, > someone is injecting mail into a system in such a way that sendmail is > being told (by the "-f" flag, if I recall correctly) what the sender's > identity is. Since the alias expansion includes an address that matches > this address (the one specified by "-f"), sendmail is, as usual, > suppressing the generation of a likely superfluous copy, as the sender > is presumed to be able to make copies, or specifically request (via Cc: > or Bcc:, for example) a copy. > > And in the more general case, it's possible to use a tool such as > majordomo, in which case the usual arrangement is that the "sender" name > is set to the name of the list (administrator), so all messages to the > list would get sent to all members of the list -- even the originator. > > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 09:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09577 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 09:54:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net (gw.sparks.net [209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09563 for ; Tue, 1 Sep 1998 09:54:27 -0700 (PDT) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0zDtgL-0002eF-00; Tue, 1 Sep 1998 12:53:25 -0400 Date: Tue, 1 Sep 1998 12:53:23 -0400 (EDT) From: To: hackers@FreeBSD.ORG Subject: AMD K6-2/300? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone using this with X successfully? I've got a new FIC 503+ mobo with teh 100 MHz FSB, K6-2/300 and a scsi controller. It loads 2.2.7R fine, boots OK, but fails to run AccelleratedX or Xfree. Both end up with a locked screen, and AcceleratedX won't even let me ctl-alt-backspace out:( XIG says they only support the Intel processors. Confirmation or suggestions welcome:) --- David Miller ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 10:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16767 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 10:31:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA16677; Tue, 1 Sep 1998 10:31:32 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09416; Tue, 1 Sep 1998 17:35:33 +0200 From: Luigi Rizzo Message-Id: <199809011535.RAA09416@labinfo.iet.unipi.it> Subject: Announce: BRIDGE/IPFW/DUMMYNET PicoBSD stuff... To: net@FreeBSD.ORG Date: Tue, 1 Sep 1998 17:35:32 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, lot of stuff to announce... (Bcc to -hackers and -committers...) My dear committers: is there anyone out there who is willing to revise the code and import it into -current and/or -stable ??? http://www.iet.unipi.it/~luigi/ip_dummynet/bridge.html i have mostly finished and tested the bridging patches for FreeBSD, a diff file for 2.2.x (and might even work on -current if someone wants to try...) is available. http://www.iet.unipi.it/~luigi/ip_dummynet/ I have also cleaned up dummynet for 2.2.7 (lots of people asking...) removing the last few bugs (now it works with natd, thanks to Philippe Regnauld who tested it extensively). This code includes a significant performance improvement in SKIPTO instructions. Patches and docs available at the above URL. http://www.iet.unipi.it/~luigi/ip_dummynet/bridge.html And since i was at it... i decided to build a PicoBSD floppy with BRIDGING, IPFW, and DUMMYNET on it... on 2.2.6 At the above URL you can find both the diffs to make PicoBSD compile on 2.2.6/2.2.7 (small enough) and a floppy image with the above. Want to know more ? Check the URLs... cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 11:01:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24084 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 11:01:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24075; Tue, 1 Sep 1998 11:01:49 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id MAA27022; Tue, 1 Sep 1998 12:00:25 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Tue, 1 Sep 1998 12:00:25 -0600 (MDT) From: Brett Taylor To: freebsd-advocacy@FreeBSD.ORG cc: freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Subject: first issue of Daemon News, a BSD ezine Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm proud to announce the first issue of Daemon News, an ezine based on all of the free BSDs; FreeBSD, NetBSD, and OpenBSD. The staff has worked very hard to get this first issue out on our self-imposed deadline of the 1st of September. This first issue contains articles over a broad range of topics; from a newbie's guide to using chmod and umask to network driver programming in NetBSD and everything in between. We hope you'll take a look at us and, if you're interested, join our team to produce future issues. We have the main site and 2 mirrors set up right now - if the main site seems slow, please try one of the mirrors. http://www.daemonnews.org/ http://www2.daemonnews.org/ http://www3.daemonnews.org/ On behalf of all of the staff here at Daemon News, thanks! ************************************************************* Brett Taylor brett@www.daemonnews.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 11:28:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28862 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 11:28:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bbcc.ctc.edu (bbcc.ctc.edu [134.39.180.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28857 for ; Tue, 1 Sep 1998 11:28:38 -0700 (PDT) (envelope-from chris@bbcc.ctc.edu) Received: from localhost (chris@localhost) by bbcc.ctc.edu (8.8.8/8.6.12) with SMTP id LAA03607; Tue, 1 Sep 1998 11:26:17 -0700 (PDT) Date: Tue, 1 Sep 1998 11:26:17 -0700 (PDT) From: Chris Coleman To: david@sparks.net cc: hackers@FreeBSD.ORG Subject: Re: AMD K6-2/300? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had that problem with a new Intel PII locking up like that with an onboard AGP card. I installed a PCI card and it has been running great. -Chris On Tue, 1 Sep 1998 david@sparks.net wrote: > Anyone using this with X successfully? > > I've got a new FIC 503+ mobo with teh 100 MHz FSB, K6-2/300 and a scsi > controller. > > It loads 2.2.7R fine, boots OK, but fails to run AccelleratedX or Xfree. > Both end up with a locked screen, and AcceleratedX won't even let me > ctl-alt-backspace out:( XIG says they only support the Intel processors. > > Confirmation or suggestions welcome:) > > --- David Miller > > > > ---------------------------------------------------------------------------- > It's *amazing* what one can accomplish when > one doesn't know what one can't do! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 12:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08193 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 12:27:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08187 for ; Tue, 1 Sep 1998 12:27:53 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id PAA17951; Tue, 1 Sep 1998 15:26:49 -0400 (EDT) Date: Tue, 1 Sep 1998 15:26:48 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 Reply-To: zhihuizhang To: bf20761@binghamton.edu cc: hackers Subject: Re: FFS questions (rotational/positional table) In-Reply-To: <199808311503.PAA01368@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks very much for your help. I have gained pretty much understanding of the related code. Below I will summarize what I have understood. If I make mistakes, please correct me. [positional/rotational table] Logically contiguous blocks should be assigned with blocks of neighboring rotational positions. Blocks belonging to each rotational position are linked together via two tables. I call them positional table and rotational table. The positional table gives the first blocks belonging to each rotational position within each cylinder in a cycle. There are fs_nrpos * fs_cpc entries in the positional table. The rotational table links the rest blocks together via block offsets. The number of entries in the rotational table is equal to the number of blocks in a cycle. There can be more than one blocks belonging to a rotational position in the same cylinder. All these blocks are recorded in the above two tables. The number of free blocks at each position for each cylinder is recorded in individual cylinder groups that the cylinder belongs to. When we need a block at a certain rotational position, we first check if the free count is greater than zero. If so, we can scan through those blocks belonging to the rotational position until a free block is find. This is a two step search process. The macro cbtorpos() only gives us the rotational positions within one cylinder (There are a total of fs_nrpos such positions in a cylinder.) So the offset pattern recorded in the rotational table is the same for every cylinder. We do not let the offset pattern repeat itself. We just calculate the pattern and reuse it for every fs_cpc cylinders (this way we can control the size of the above two tables). If we let the pattern repeat itself, it will not neccessary happen at a cylinder boundary and can take very long. [hardware - interleave/disk skew] The disk is revolving at a constant speed. The old disk controllers are slower compared with disk revolution speed. So when it have finished reading a sector, the disk has moved beyond the next contiguous sector. This is the reason for interleaving. When the disk head moves from track to track, the disk continues to revolve. This is the reason we use the disk skew factor. Any help is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 12:45:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11545 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 12:45:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from the.oneinsane.net (gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11530; Tue, 1 Sep 1998 12:45:00 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id MAA09082; Tue, 1 Sep 1998 12:43:46 -0700 (PDT) Message-ID: <19980901124346.A9002@oneinsane.net> Date: Tue, 1 Sep 1998 12:43:46 -0700 From: "Ron 'The Insane One' Rosson" To: Brett Taylor , freebsd-advocacy@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Subject: Re: first issue of Daemon News, a BSD ezine Reply-To: insane@oneinsane.net Mail-Followup-To: Brett Taylor , freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Brett Taylor on Tue, Sep 01, 1998 at 12:00:25PM -0600 X-Operating-System: FreeBSD the.oneinsane.net 2.2.6-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking at the site with Netscape 4.05 for FreeBSD and the left column is cut off for the links. Is anyone else seeing this or is it all my fault. ;-) TIA Ron On Tue, Sep 01, 1998 at 12:00:25PM -0600, Brett Taylor wrote: > Hi, > > I'm proud to announce the first issue of Daemon News, an ezine based > on all of the free BSDs; FreeBSD, NetBSD, and OpenBSD. The staff > has worked very hard to get this first issue out on our self-imposed > deadline of the 1st of September. > > This first issue contains articles over a broad range of topics; from > a newbie's guide to using chmod and umask to network driver programming > in NetBSD and everything in between. We hope you'll take a look at us > and, if you're interested, join our team to produce future issues. > > We have the main site and 2 mirrors set up right now - if the main site > seems slow, please try one of the mirrors. > > http://www.daemonnews.org/ > http://www2.daemonnews.org/ > http://www3.daemonnews.org/ > > On behalf of all of the staff here at Daemon News, thanks! > > ************************************************************* > Brett Taylor > brett@www.daemonnews.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- -------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void -------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 13:00:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14261 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 13:00:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14234; Tue, 1 Sep 1998 13:00:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00811; Tue, 1 Sep 1998 12:56:04 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809011256.MAA00811@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: insane@oneinsane.net cc: Brett Taylor , freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Subject: Re: first issue of Daemon News, a BSD ezine In-reply-to: Your message of "Tue, 01 Sep 1998 12:43:46 MST." <19980901124346.A9002@oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 12:56:04 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am looking at the site with Netscape 4.05 for FreeBSD and the left > column is cut off for the links. Is anyone else seeing this or is it > all my fault. ;-) Definitely your fault; looks OK here (there are some other layout problems, but that's not one of them). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 13:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19200 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 13:36:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19189; Tue, 1 Sep 1998 13:36:20 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.1/8.9.1) with SMTP id NAA13633; Tue, 1 Sep 1998 13:35:13 -0700 (PDT) Date: Tue, 1 Sep 1998 13:35:13 -0700 (PDT) From: "Eric J. Schwertfeger" To: insane@oneinsane.net cc: Brett Taylor , freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Subject: Re: first issue of Daemon News, a BSD ezine In-Reply-To: <199809011256.MAA00811@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Sep 1998, Mike Smith wrote: > > I am looking at the site with Netscape 4.05 for FreeBSD and the left > > column is cut off for the links. Is anyone else seeing this or is it > > all my fault. ;-) > > Definitely your fault; looks OK here (there are some other layout > problems, but that's not one of them). Same problem here. What window size are you using for netscape? 560x540 here, and what is happening is that the right column of the table is right justified, the left column appears immediately to the left of the right column, and if that comes out to be wider than the current window, no scroll bar appears. I've never seen this happen anywhere else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 13:41:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20313 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 13:41:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA20294 for ; Tue, 1 Sep 1998 13:40:57 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 2925 invoked by uid 1000); 1 Sep 1998 20:40:01 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980901124346.A9002@oneinsane.net> Date: Tue, 01 Sep 1998 16:40:00 -0400 (EDT) From: Vince Vielhaber To: "Ron 'The Insane One' Rosson" Subject: Re: first issue of Daemon News, a BSD ezine Cc: announce@openbsd.org, netbsd-users@netbsd.org, freebsd-hackers@FreeBSD.ORG, freebsd-advocacy@FreeBSD.ORG, Brett Taylor Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Sep-98 Ron 'The Insane One' Rosson wrote: > I am looking at the site with Netscape 4.05 for FreeBSD and the left > column is cut off for the links. Is anyone else seeing this or is it > all my fault. ;-) Your own fault, I hate to say. Looks perfect here. I'm using 4.06 on FreeBSD. Can you make Netscape any wider? Just guessing but it looks like it'd take up the full screen in 800*600 mode, I'm set up wider than that. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 13:47:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21510 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 13:47:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21495; Tue, 1 Sep 1998 13:47:09 -0700 (PDT) (envelope-from howardjp@dragon.ham.muohio.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.8.5/8.8.5) with SMTP id QAA22392; Tue, 1 Sep 1998 16:45:47 -0400 Date: Tue, 1 Sep 1998 16:45:47 -0400 (EDT) From: Jamie Howard To: "Ron 'The Insane One' Rosson" cc: Brett Taylor , freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Subject: Re: first issue of Daemon News, a BSD ezine In-Reply-To: <19980901124346.A9002@oneinsane.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Sep 1998, Ron 'The Insane One' Rosson wrote: > I am looking at the site with Netscape 4.05 for FreeBSD and the left > column is cut off for the links. Is anyone else seeing this or is it > all my fault. ;-) > TIA > Ron I saw this, but only for a few of the pages, not all of them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 14:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26177 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 14:15:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hebe.or.intel.com (hebe.or.intel.com [134.134.248.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26172; Tue, 1 Sep 1998 14:15:12 -0700 (PDT) (envelope-from cwood@ichips.intel.com) Received: from ichips-ra.pdx.intel.com (ichips-ra.pdx.intel.com [137.102.192.31]) by hebe.or.intel.com (8.8.6/8.8.5) with ESMTP id OAA11242; Tue, 1 Sep 1998 14:23:06 -0700 (PDT) Received: from pdxcs199.pdx.intel.com (pdxcs199.pdx.intel.com [137.102.196.139]) by ichips-ra.pdx.intel.com (8.8.8/8.8.7) with ESMTP id OAA21795; Tue, 1 Sep 1998 14:13:54 -0700 (PDT) From: Colin Wood Received: by pdxcs199.pdx.intel.com (8.8.8/WW2.2 (Ronler Acres)) id OAA132692; Tue, 1 Sep 1998 14:13:54 -0700 Message-Id: <199809012113.OAA132692@pdxcs199.pdx.intel.com> Subject: Re: first issue of Daemon News, a BSD ezine In-Reply-To: <199809011256.MAA00811@dingo.cdrom.com> from Mike Smith at "Sep 1, 98 12:56:04 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 1 Sep 1998 14:13:54 -0700 (PDT) Cc: insane@oneinsane.net, brett@peloton.physics.montana.edu, freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I am looking at the site with Netscape 4.05 for FreeBSD and the left > > column is cut off for the links. Is anyone else seeing this or is it > > all my fault. ;-) > > Definitely your fault; looks OK here (there are some other layout > problems, but that's not one of them). Same thing for the Answer Man columns from here using Netscape 4.06 for NT. Later. -- Colin Wood cwood@ichips.intel.com Component Design Engineer - PMD Intel Corporation ----------------------------------------------------------------- I speak only on my own behalf, not for my employer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 14:22:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27581 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 14:22:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27517 for ; Tue, 1 Sep 1998 14:22:15 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA140 for ; Tue, 1 Sep 1998 15:03:47 -0600 Received: from count.timing.com (localhost.timing.com [127.0.0.1]) by count.timing.com (8.8.7/8.8.7) with ESMTP id PAA11043 for ; Tue, 1 Sep 1998 15:03:02 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199809012103.PAA11043@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG Subject: pthread_cancel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 15:03:02 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am starting to use threads on a FreeBSD 2.2.6 system. Is there a pthread_cancel() function? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 14:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00358 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 14:43:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00343; Tue, 1 Sep 1998 14:43:13 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (fermion [10.0.1.2]) by quark.ChrisBowman.com (8.8.8/8.8.8) with SMTP id SAA21713; Tue, 1 Sep 1998 18:07:17 -0500 (EST) (envelope-from crb@ChrisBowman.com) Message-Id: <199809012307.SAA21713@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 01 Sep 1998 17:38:49 -0400 To: Mike Smith From: "Christopher R. Bowman" Subject: Re: first issue of Daemon News, a BSD ezine Cc: insane@oneinsane.net, Brett Taylor , freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org In-Reply-To: <199809011256.MAA00811@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA00346 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:56 PM 9/1/98 +0000, Mike Smith wrote: >> I am looking at the site with Netscape 4.05 for FreeBSD and the left >> column is cut off for the links. Is anyone else seeing this or is it >> all my fault. ;-) > >Definitely your fault; looks OK here (there are some other layout >problems, but that's not one of them). I don't think so, I am running NetscapeŽ Communicator 4.04 on an NT Box here, and I also have the left edge cut off. But I have no problems with any other site. >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/~crb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 15:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05021 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 15:11:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05009; Tue, 1 Sep 1998 15:11:36 -0700 (PDT) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id SAA06974; Tue, 1 Sep 1998 18:06:09 -0400 (EDT) (envelope-from adrian@lorax.ubergeeks.com) Date: Tue, 1 Sep 1998 18:06:08 -0400 (EDT) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Colin Wood cc: Mike Smith , insane@oneinsane.net, brett@peloton.physics.montana.edu, freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Subject: Re: first issue of Daemon News, a BSD ezine In-Reply-To: <199809012113.OAA132692@pdxcs199.pdx.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Sep 1998, Colin Wood wrote: > Mike Smith wrote: > > > I am looking at the site with Netscape 4.05 for FreeBSD and the left > > > column is cut off for the links. Is anyone else seeing this or is it > > > all my fault. ;-) > > > > Definitely your fault; looks OK here (there are some other layout > > problems, but that's not one of them). > > Same thing for the Answer Man columns from here using Netscape 4.06 for > NT. I think the problem is that the left column has a hard size specification, i.e. pixels instead of a percent. I too had the messed up left margin, but widening my window fixed this. Pretty nice other wise. I can wait to sshow it to some friends. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 15:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06679 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 15:22:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA06674 for ; Tue, 1 Sep 1998 15:22:53 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA09940 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Wed, 2 Sep 1998 00:14:25 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id AAA29093 for FreeBSD-hackers@freebsd.org; Wed, 2 Sep 1998 00:05:05 +0200 (CEST) From: Wilko Bulte Message-Id: <199809012205.AAA29093@yedi.iaf.nl> Subject: pci memory mapping To: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Date: Wed, 2 Sep 1998 00:05:04 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I'm trying to get a Mylex DAC960PD to work with a driver skeleton Ulf wrote. As I have a different Mylex board than Ulf (a PD iso a PG) I need to make some changes. For some reason the followin code in attach() fails: if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, &mp->pbase)) { printf("myx%d: couldn't map memory\n", unit); goto fail; } >From a previous post by Bill Paul I get the impression (...) that I might need to enable memory mapping by doing a pci_conf_write(). But what params do I feed pci_conf_write()? This is all new to me, I could really use some advise here. Interestingly enough for Ulf's board things work OK. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 15:25:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07066 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 15:25:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07037 for ; Tue, 1 Sep 1998 15:25:09 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA18423 for ; Tue, 1 Sep 1998 15:24:08 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma018419; Tue Sep 1 15:23:56 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA17824 for freebsd-hackers@freebsd.org; Tue, 1 Sep 1998 15:23:56 -0700 (PDT) From: Archie Cobbs Message-Id: <199809012223.PAA17824@bubba.whistle.com> Subject: default syslog priority for kernel messages To: freebsd-hackers@FreeBSD.ORG Date: Tue, 1 Sep 1998 15:23:56 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In syslogd.c, the default priority for messages from the kernel is "critical": #define DEFSPRI (LOG_KERN|LOG_CRIT) It seems that in practice, this is not really appropriate. Only rarely are kernel-generated messages truly critical. Would anyone object if this were changed to be NOTICE instead? [ It seems like the real solution is to change all the kernel code that uses "printf(...)" to use "log(LOG_XXX, ...)" instead, where XXX is the appropriate priority for that particular message (anyone interested in a mini-project?? :-) IMHO, printf() in the kernel should be deprecated in favor of log(). ] -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 15:34:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08033 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 15:34:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08028 for ; Tue, 1 Sep 1998 15:34:29 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id SAA03754; Tue, 1 Sep 1998 18:33:19 -0400 (EDT) Date: Tue, 1 Sep 1998 18:33:18 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: Mike Smith cc: hackers Subject: Re: FFS questions In-Reply-To: <199808311503.PAA01368@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks very much for your help. This morning I though I had pretty well understood the subject and began to write the following summary. However, when I finished it in the late afternoon, I find I am still have some confusions. [positional/rotational table] Logically contiguous blocks should be assigned with blocks of neighboring rotational positions. Blocks belonging to each rotational position are linked together via two tables. I call them positional table and rotational table. The positional table gives the first blocks belonging to each rotational position within each cylinder in a cycle. There are fs_nrpos * fs_cpc entries in the positional table. The rotational table links the rest blocks together via block offsets. The number of entries in the rotational table is equal to the number of blocks in a cycle. There can be more than one physical blocks belonging to a rotational position in the same cylinder. All these blocks are recorded in the above two tables. The number of free blocks at each position for each cylinder is recorded in individual cylinder groups that the cylinder belongs to. When we need a block at a certain rotational position, we first check if the free count is greater than zero. If so, we can scan through those blocks belonging to the rotational position until a free block is find. This is a two step search process. The macro cbtorpos() only gives us the rotational positions within one cylinder (There are a total of fs_nrpos such positions in a cylinder.) So the offset pattern recorded in the rotational table is the same for every cylinder. Why we need fs_cpc cylinders? We do not let the offset pattern repeat itself. We just calculate the pattern and reuse it for every fs_cpc cylinders (this way we can control the size of the above two tables). If we let the pattern repeat itself, it will not neccessary happen at a cylinder boundary and can take very long. [hardware - interleave/disk skew] The disk is revolving at a constant speed. The old disk controllers are slower compared with disk revolution speed. So when it have finished reading a sector, the disk has moved beyond the next contiguous sector. This is the reason for interleaving. This is already done by hardware (the hardware automatically converts logical sector numbers to physical sector numbers - relocation or mapping). The hardware only takes care of sequential reading, FFS has to take acount of interrupt handling and I/O initiation. When the disk head moves from track to track, the disk continues to revolve. This is the reason we have the disk skew (sector skew per track). This setting is to be used by software (FFS in our case). >From the definition of cbtorpos(), FFS has take account of the above two factors. It converts a block number to a logical sector number and then to physical sector number and finally to rotational position. #define cbtorpos(fs, bno) \ (((bno) * NSPF(fs) % (fs)->fs_spc / (fs)->fs_nsect * (fs)->fs_trackskew + \ (bno) * NSPF(fs) % (fs)->fs_spc % (fs)->fs_nsect * (fs)->fs_interleave) % \ (fs)->fs_nsect * (fs)->fs_nrpos / (fs)->fs_npsect) Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:01:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21982 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:01:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21977 for ; Tue, 1 Sep 1998 17:01:04 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA20786; Tue, 1 Sep 1998 16:59:59 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd020710; Tue Sep 1 16:59:53 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA07448; Tue, 1 Sep 1998 16:59:50 -0700 (MST) From: Terry Lambert Message-Id: <199809012359.QAA07448@usr01.primenet.com> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: junker@jazz.snu.ac.kr (CHOI Junho) Date: Tue, 1 Sep 1998 23:59:50 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "CHOI Junho" at Sep 1, 98 11:46:04 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (ii) Distributing the Program on removable computer-readable media, > provided that the files containing the Program are reproduced entirely and > verbatim on such media, that all information on such media be > redistributable for non-commercial purposes without charge, and that such > media are distributed by themselves (except for accompanying documentation) > independent of any other product or service. Examples of such media include > CD-ROM, magnetic tape, and optical storage media. (This is not intended to > be an exhaustive list.) An example of a distribution that does not fall > under this section is a CD-ROM included in a book or magazine. (This is not > an exhaustive enumeration.) > > > According to 2-(a)-(i), I think Aladdin ghostscript on FreeBSD FTP > mirrors are ok. (it is public access), but according to 2-(a)-(ii), > FreeBSD CD-ROM may have a problem. Walnet Creek CDROM is not a product > of Walnet Creek? And "The Complete FreeBSD"(with books) doesn't > violate 2-(a)-(ii)? Feel free to consult a lawyer, but here's my educated opinion... No, it does not. This is because the CDROM purchaser is not required to purchase a copy of the book, and the FTP site is an "alternate source from the same supplier". Further, even were this not the case, "The Complete FreeBSD" book then falls under the "except for accompanying documentation" clause. If you research this further, I believe you will find that Aladdin was consulted on the distribution terms prior to the inclusion of the code. In any case, the CDROM is not "The Alladin ghostscript CDROM", and thus constitutes what is legally called a "mere agregation", so any attempt to apply the license terms to it in situ to determine violation of 2-(a)-(ii) would be incorrect anyway. The main error you are making here is that the book is sold with the CDROM, rather than the CDROM being sold with the book (since the CDROM is available seperately). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:07:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23431 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:07:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23426 for ; Tue, 1 Sep 1998 17:07:51 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA01799; Tue, 1 Sep 1998 17:06:50 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd001709; Tue Sep 1 17:06:40 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA07809; Tue, 1 Sep 1998 17:06:34 -0700 (MST) From: Terry Lambert Message-Id: <199809020006.RAA07809@usr01.primenet.com> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: junker@jazz.snu.ac.kr (CHOI Junho) Date: Wed, 2 Sep 1998 00:06:34 +0000 (GMT) Cc: jkh@time.cdrom.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "CHOI Junho" at Sep 1, 98 04:25:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about this? (after your quotation of my original mail) > > > optical storage media. (This is not intended to be an > > exhaustive list.) An example of a distribution that does not > > fall under this section is a CD-ROM included in a book or > > magazine. (This is not an exhaustive enumeration.) > > I agree on WC FreeBSD CDROM set. But CD with books("The Complete > FreeBSD") or some FreeBSD cover CD of magazines in the world may have > a problem I think. Do I misunderstand? See what Luigi said: ] now the first one is no problem for the FreeBSD CD#1 and i think it is ] there just because people tend to stick a restrictive copyright on ] everything. E.g. one of the think i have to make clear to the libraries ] i send the 2.2.6 CDs that WC generously donated (thanks again!) is that ] people _CAN_ copy the content of the disks. It's a case of "the book is included with the CDROM", not "the CDROM is included with the book". Since it is available seperately, it's not a problem. The Alladin license, from their rationale, was to prohibit a company requiring a purchase of a book to get the CDROM containing the code. Per my other posting, I don't believe this section is applicable, in any case, until you have proven that the other three interpretations aren't applicable first. What problem do you have with the Alladin license that makes you prefer the inclusion of the other (inferior) ghostscript? This sounds more like a political brow-beating to encourage the use of GPL'ed code... please tell me I'm wrong. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24170 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:11:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24165 for ; Tue, 1 Sep 1998 17:11:24 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA03247; Tue, 1 Sep 1998 17:10:23 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd003211; Tue Sep 1 17:10:17 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA07985; Tue, 1 Sep 1998 17:10:13 -0700 (MST) From: Terry Lambert Message-Id: <199809020010.RAA07985@usr01.primenet.com> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: joelh@gnu.org Date: Wed, 2 Sep 1998 00:10:13 +0000 (GMT) Cc: jkh@time.cdrom.com, junker@jazz.snu.ac.kr, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809011248.HAA02001@detlev.UUCP> from "Joel Ray Holveck" at Sep 1, 98 07:48:30 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> (ii) Distributing the Program on removable computer-readable media, > >> provided that the files containing the Program are reproduced > >> entirely and verbatim on such media, that all information on such > >> media be redistributable for non-commercial purposes without > >> charge, and that such media are distributed by themselves (except > >> for accompanying documentation) independent of any other product or > >> service. Examples of such media includ > > Sounds like a FreeBSD CD to me. > > Would the "other product or service" clause refer to FreeBSD? That > is, is this a "no bundling" bit? No. This is the "no incorporation/masking" clause. This is similar to the LGPL restriction on anything other than "mere agregation". The code is "independent of any other product", in that it is seperable without loss of function. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24450 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:13:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24431 for ; Tue, 1 Sep 1998 17:13:19 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA25684; Tue, 1 Sep 1998 17:12:11 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd025649; Tue Sep 1 17:12:04 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA08077; Tue, 1 Sep 1998 17:12:00 -0700 (MST) From: Terry Lambert Message-Id: <199809020012.RAA08077@usr01.primenet.com> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: nick.hibma@jrc.it Date: Wed, 2 Sep 1998 00:12:00 +0000 (GMT) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: from "Nick Hibma" at Sep 1, 98 10:40:37 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The case where it's a cover disk for some magazine is, indeed, > > specifically excluded I see now and I'd say that's reason alone to > > just mark Ghostcript 5x as "NO_CDROM" from this point onwards, my > > reasoning being that we *like* FreeBSD going out on people's magazine > > covers and it's frequently the easiest thing for Walnut Creek CDROM to > > do to give them CD #1 of whatever FreeBSD product they currently have > > and suggest that as the cover disc. I'd hate to lose that flexibility > > over one package. > > This last remark is an eye opener. I fully agree. Put it on a CD other than #1, so long as the CD is seperately available from the magazine, and you don't "cost" CD #1 seperately as a SKU from the other CD. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25213 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:16:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25204 for ; Tue, 1 Sep 1998 17:16:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA04464; Tue, 1 Sep 1998 17:15:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: junker@jazz.snu.ac.kr (CHOI Junho), freebsd-hackers@FreeBSD.ORG Subject: Re: Aladdin Ghostscript License and FreeBSD CD? In-reply-to: Your message of "Wed, 02 Sep 1998 00:06:34 -0000." <199809020006.RAA07809@usr01.primenet.com> Date: Tue, 01 Sep 1998 17:15:44 -0700 Message-ID: <4460.904695344@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This sounds more like a political brow-beating to encourage the use of > GPL'ed code... Not unless you're also prepared to dismiss the cover disk requirements as lightly. See my other posting. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25310 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:17:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25305 for ; Tue, 1 Sep 1998 17:17:12 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA25837; Tue, 1 Sep 1998 17:16:11 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd025800; Tue Sep 1 17:16:07 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA08412; Tue, 1 Sep 1998 17:16:03 -0700 (MST) From: Terry Lambert Message-Id: <199809020016.RAA08412@usr01.primenet.com> Subject: Re: Thread calls To: tinguely@plains.NoDak.edu (Mark Tinguely) Date: Wed, 2 Sep 1998 00:16:03 +0000 (GMT) Cc: doconnor@gsoft.com.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809011323.IAA31017@plains.NoDak.edu> from "Mark Tinguely" at Sep 1, 98 08:23:42 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the PMPTHREADS package (http://www.humanfactor.com/pthreads/) has > the pthread_setcancelstate(), pthread_setcanceltype(), and > pthread_testcancel() routines you require. But will require hacking to integrate into libc_r such that system call reentrancy is handled correctly. This is the problem with third party user space threading packages. Better to just add the code to FreeBSD. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:37:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28061 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:37:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28056 for ; Tue, 1 Sep 1998 17:37:24 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA08738; Tue, 1 Sep 1998 17:36:23 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd008711; Tue Sep 1 17:36:16 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA09470; Tue, 1 Sep 1998 17:36:14 -0700 (MST) From: Terry Lambert Message-Id: <199809020036.RAA09470@usr01.primenet.com> Subject: Re: pthread_cancel To: chanders@timing.com (Craig Anderson) Date: Wed, 2 Sep 1998 00:36:13 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809012103.PAA11043@count.timing.com> from "Craig Anderson" at Sep 1, 98 03:03:02 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am starting to use threads on a FreeBSD 2.2.6 system. > Is there a pthread_cancel() function? No. FreeBSD provides Draft 4 pthreads, not the Draft 10 (Standard). FreeBSD -current is, right now, a bastard child of Draft 4 and Standard, with the only way to tell them apart being one of the few things that was braought up to Standard. 8-(. Use Draft 4 programming techniques, and you will be fine. See the O'Reilly Pthreads book for exmaples of how to substitute code; there is an appendix dedicated to the differences. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:41:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28608 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:41:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28597 for ; Tue, 1 Sep 1998 17:41:54 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA06448; Tue, 1 Sep 1998 17:40:53 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd006410; Tue Sep 1 17:40:46 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA09710; Tue, 1 Sep 1998 17:40:44 -0700 (MST) From: Terry Lambert Message-Id: <199809020040.RAA09710@usr01.primenet.com> Subject: Re: default syslog priority for kernel messages To: archie@whistle.com (Archie Cobbs) Date: Wed, 2 Sep 1998 00:40:44 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809012223.PAA17824@bubba.whistle.com> from "Archie Cobbs" at Sep 1, 98 03:23:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In syslogd.c, the default priority for messages from the kernel is > "critical": > > #define DEFSPRI (LOG_KERN|LOG_CRIT) > > It seems that in practice, this is not really appropriate. > Only rarely are kernel-generated messages truly critical. > > Would anyone object if this were changed to be NOTICE instead? > > [ It seems like the real solution is to change all the kernel code > that uses "printf(...)" to use "log(LOG_XXX, ...)" instead, where > XXX is the appropriate priority for that particular message (anyone > interested in a mini-project?? :-) > > IMHO, printf() in the kernel should be deprecated in favor of log(). ] The only problem is that it's possible to printf from the kernel without logging, and it may frequently be desirable to send a message to the console without logging it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 17:43:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28921 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 17:43:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28916 for ; Tue, 1 Sep 1998 17:43:05 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA10692; Tue, 1 Sep 1998 17:42:04 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd010633; Tue Sep 1 17:41:56 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA09827; Tue, 1 Sep 1998 17:41:51 -0700 (MST) From: Terry Lambert Message-Id: <199809020041.RAA09827@usr01.primenet.com> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 2 Sep 1998 00:41:51 +0000 (GMT) Cc: tlambert@primenet.com, junker@jazz.snu.ac.kr, freebsd-hackers@FreeBSD.ORG In-Reply-To: <4460.904695344@time.cdrom.com> from "Jordan K. Hubbard" at Sep 1, 98 05:15:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This sounds more like a political brow-beating to encourage the use of > > GPL'ed code... > > Not unless you're also prepared to dismiss the cover disk requirements > as lightly. See my other posting. Don't put the code on CD #1. See *my* other posting. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 18:44:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10036 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 18:44:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10012 for ; Tue, 1 Sep 1998 18:44:51 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA14876; Wed, 2 Sep 1998 11:13:38 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809020016.RAA08412@usr01.primenet.com> Date: Wed, 02 Sep 1998 11:13:38 +0930 (CST) From: "Daniel O'Connor" To: Terry Lambert Subject: Re: Thread calls Cc: freebsd-hackers@FreeBSD.ORG, (Mark Tinguely) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Sep-98 Terry Lambert wrote: > > the PMPTHREADS package (http://www.humanfactor.com/pthreads/) has > > the pthread_setcancelstate(), pthread_setcanceltype(), and > > pthread_testcancel() routines you require. > > But will require hacking to integrate into libc_r such that system > call reentrancy is handled correctly. > > This is the problem with third party user space threading packages. > > Better to just add the code to FreeBSD. Well.. I was just asking if anyone was actually doing this or not =) I did try the thrid party pthreads thing but it doesn't like -current, and then I realised I'd have to recompile a few things (like X.. again) to use it. So, from what I hear, noone is implementing these calls in FreeBSD's libc_r? --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 19:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13010 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 19:01:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12995 for ; Tue, 1 Sep 1998 19:01:03 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.rad.cc.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.6W) with ESMTP id KAA23712; Wed, 2 Sep 1998 10:59:56 +0900 (JST) Received: (from sanpei@localhost) by lavender.rad.cc.keio.ac.jp (8.8.8/3.6W) id KAA02323; Wed, 2 Sep 1998 10:59:56 +0900 (JST) Message-Id: <199809020159.KAA02323@lavender.rad.cc.keio.ac.jp> To: michaelh@cet.co.jp Cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Cable modem service in the Boston area In-Reply-To: Your message of "Wed, 2 Sep 1998 09:54:58 +0900 (JST)" References: X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 02 Sep 1998 10:59:55 +0900 From: MIHIRA "Sanpei" Yoshiro Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>I'm going to balance my time between Tokyo and Boston starting this month >>and one of the requirements in Boston is cable modem service. Anyone out >>there using @Home? I'd like to hear experiences from anyone out there >>using the service and in what area of Boston. >> >>BTW, I'm a Boston newbie so I won't recognize a lot of city names, but >>I'll figure these out when I get there. > > I use Cable modem at Yokohama-Kanazawa with FreeBSD box :-)> > >Cool! I heard there was cable modem service in Japan but I wasn't sure >where. How does it work? I heard in Boston, Media One sets you up with >DHCP so you need to get ISC or WIDE working. I use cable modem at My home, Kanazawa-Yokohama[1] and Tokyu Cable TV[2] with FreeBSD box. Both service use DHCP for IP address assignment. I use WIDE-DHCP, because I was maintaner of WIDE-DHCP. It's fine. If you can read japanese, let's to go my home page about FreeBSD and CATV page [3]. Yours. ---------- Yoshiro MIHIRA sanpei@sanpei.org sanpei@jp.freebsd.org sanpei@yy.cs.keio.ac.jp [1] Seaple CATV http://www.seaple.icc.ne.jp/ [2] Tokyu CATV http://www.catv.ne.jp/ [3] FreeBSD and CATV page http://www.seaple.icc.ne.jp/~sanpei/home-lan.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 19:16:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15380 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 19:16:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15373 for ; Tue, 1 Sep 1998 19:16:44 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA20791; Tue, 1 Sep 1998 19:15:43 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma020789; Tue Sep 1 19:15:31 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA00488; Tue, 1 Sep 1998 19:15:31 -0700 (PDT) From: Archie Cobbs Message-Id: <199809020215.TAA00488@bubba.whistle.com> Subject: Re: default syslog priority for kernel messages In-Reply-To: <199809020040.RAA09710@usr01.primenet.com> from Terry Lambert at "Sep 2, 98 00:40:44 am" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 1 Sep 1998 19:15:31 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > IMHO, printf() in the kernel should be deprecated in favor of log(). > > The only problem is that it's possible to printf from the kernel > without logging, and it may frequently be desirable to send a message > to the console without logging it. So then kill syslogd. Here is the comment in the code: /* * Log writes to the log buffer, and guarantees not to sleep (so can be * called by interrupt routines). If there is no process reading the * log yet, it writes to the console also. */ -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 20:46:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26457 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 20:46:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26441 for ; Tue, 1 Sep 1998 20:46:41 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-127.camalott.com [208.229.74.127]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA31785; Tue, 1 Sep 1998 22:47:00 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA03114; Tue, 1 Sep 1998 22:18:56 -0500 (CDT) (envelope-from joelh) Date: Tue, 1 Sep 1998 22:18:56 -0500 (CDT) Message-Id: <199809020318.WAA03114@detlev.UUCP> To: nick.hibma@jrc.it CC: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-reply-to: (message from Nick Hibma on Tue, 1 Sep 1998 10:40:37 +0200 (MET DST)) Subject: Re: Aladdin Ghostscript License and FreeBSD CD? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The case where it's a cover disk for some magazine is, indeed, >> specifically excluded I see now and I'd say that's reason alone to >> just mark Ghostcript 5x as "NO_CDROM" from this point onwards, my >> reasoning being that we *like* FreeBSD going out on people's >> magazine covers and it's frequently the easiest thing for Walnut >> Creek CDROM to do to give them CD #1 of whatever FreeBSD product >> they currently have and suggest that as the cover disc. I'd hate >> to lose that flexibility over one package. > This last remark is an eye opener. I fully agree. Why don't we ask Aladdin? I think that finding out what they want done is probably the best way to go, to make sure that no toes are trampled either legally or ethically. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 21:49:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06655 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 21:49:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06647 for ; Tue, 1 Sep 1998 21:49:38 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id AAA29814 for ; Wed, 2 Sep 1998 00:48:30 -0400 (EDT) Date: Wed, 2 Sep 1998 00:48:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-hackers@FreeBSD.ORG Subject: Writing lkms that use vnode.h Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Under FreeBSD 3.0-CURRENT, I wish to write an lkm that calls namei (followed afterwards by a vput() of the vnode to return the reference/lock). However, I am having problems as vnode.h includes vnode_if.h with KERNEL is defined. vnode_if.h appears to be assembled auto-magically by config for specific kernels. I believe that this occurs so as to construct the table of possible vfs calls out of the union of the calls supported by various vfs providers (correct me if I'm wrong). If the information necessary to make vnode calls is only available when a specific kernel is built, does this mean an lkm cannot make direct use of these calls? This conclusion seems silly, and probably wrong. The existing /lkm tree (built as part of buildworld?) contains several pieces of code that reference vnode.h, with apparent success. Any advice here would be welcomed. Also, is there a reference for those playing with lkm's under FreeBSD? I have read through the material in /usr/share/example/lkm and written a number of modules, but am starting to run into some holes in the easily accessible knowledge base :) Thanks, Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 22:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08517 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 22:00:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA08495 for ; Tue, 1 Sep 1998 22:00:53 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA10281; Wed, 2 Sep 1998 05:05:01 +0200 Date: Wed, 2 Sep 1998 05:04:59 +0200 (MET DST) From: Luigi Rizzo To: hackers@FreeBSD.ORG cc: cmascott@world.std.com Subject: Re: Reading/writing /usr/ports is VERY slow (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, some of you might have seen this, some not, but there was a kind of interesting thread on the newsgroup about /usr/ports access speed, and the author of the message below (who is Cc:) found out that creating a partition with only one cylinder group (instead of more using the same exact disk and partition size and location) speeds up disk access for /usr/ports by a factor of 3. If i remember well the reason was, the FS code moves to a new Cylinder group to create the next directory, and this causes a lot of seeks. I am not sure where this happens, but perhaps an easy fix could be to stay in the same CG if its (CG) occupation is low enough ? Before you mention softupdates... the author also experimented with "noatime" and softupdates and the results were that using 1 CG is much faster. cheers luigi ---------- Forwarded message ---------- Date: Tue, 1 SEP 1998 01:20:50 GMT From: Carl Mascott Newgroups: comp.unix.bsd.freebsd.misc Subject: Re: Reading/writing /usr/ports is VERY slow On 31 Aug 1998 10:21:01 -0700, dillon@best.net (Matt Dillon) wrote: > :In article , > :Carl Mascott wrote: > :>Thanks to all who confirmed that the slow filesystem throughput > :.. > :>To improve the read and write throughput from poor to > :>fair, which is the best you'll ever do with something > :>like /usr/ports, the seeks have got to be reduced a lot. > :> > :>Where to go from here? A tree like /usr/ports is really > :>atypical (2.6 small files per directory). One wouldn't > :>want to speed up FFS on /usr/ports if the result was to > > Well, everything has tradeoffs. As far as /usr/ports goes... I wouldn't > worry about /usr/ports at all. It's essentially a one-time thing, and > it doesn't make much sense to try to optimize the filesystem to handle > something that you only do a few times a year (if that, even). Softupdates > takes care of most of the problem any, so it will be a doubly-non-problem > when -current becomes -release. I'm not too worried about writing /usr/ports, which I do only when I get a new set of FBSD CD-ROMs. However, the read throughput hurts every time I back up /usr to QIC-525 tape (200 KB/s). The read throughput on /usr/ports is too slow to keep the tape streaming, even without compression, and I'd like to be able to use compression. If I could keep the tape streaming through /usr/ports it would cut the time for a compressed backup of /usr almost in half (from actual measurement). Softupdates mainly benefits write throughput because that's where most of the metadata updates occur. In my noatime read tests there were no metadata updates at all (even better than softupdates) and the read throughput was still <200 KB/s in /usr/ports. Take a look at my numbers again. The benefits of confining a directory tree to one cylinder group are about twice as great as the benefits of eliminating (not just reducing) metadata updates for the read case. As I mentioned, the directory placement policy makes "find" slow as well. That's more significant than performance in /usr/ports. I fully expect softupdates to have a significant impact on write throughput. If some 3.0 user is feeling ambitious perhaps he can measure write throughput on /usr/ports with and without softupdates. Be sure to "rm -rf /usr/ports/*" before each test, so that all of the subdirectories have to be created each time. And don't use tape as the source. Use either a different physical disk or the CD-ROM. Softupdates sounds nice. I look forward to it in -stable. But it won't make my tape stream reading /usr/ports (I think I've proven that) and it won't speed up "find" much. In short, I think that there are more long inter-group seeks on FFS than there need be, due to the directory placement policy. I consider it undesirable to spread directories out as much as possible all over the filesystem. -- Carl Mascott cmascott@world.std.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 22:40:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16156 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 22:40:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tome.pantheon.org (user-38ld8d3.dialup.mindspring.com [209.86.161.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16151; Tue, 1 Sep 1998 22:40:37 -0700 (PDT) (envelope-from kpneal@pobox.com) Received: from kpneal.users.mindspring.com (darkwalker.pantheon.org [10.0.0.4]) by tome.pantheon.org (8.8.8/8.8.8) with SMTP id XAA18411; Tue, 1 Sep 1998 23:19:02 -0400 (EDT) Message-Id: <1.5.4.32.19980902030327.0092fc54@[10.0.0.9]> X-Sender: kpn@[10.0.0.9] X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 01 Sep 1998 23:03:27 -0400 To: Jamie Howard From: "Kevin P. Neal" Subject: Re: first issue of Daemon News, a BSD ezine Cc: "Ron 'The Insane One' Rosson" , Brett Taylor , freebsd-advocacy@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, netbsd-users@netbsd.org, announce@openbsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:45 PM 9/1/98 -0400, Jamie Howard wrote: >On Tue, 1 Sep 1998, Ron 'The Insane One' Rosson wrote: > >> I am looking at the site with Netscape 4.05 for FreeBSD and the left >> column is cut off for the links. Is anyone else seeing this or is it >> all my fault. ;-) >> TIA >> Ron > >I saw this, but only for a few of the pages, not all of them. Ummmm, "me too!" *sigh* Aside from that one nit, the site looks nice. -- Kevin P. Neal http://www.pobox.com/~kpn/ 'You know, I think I can hear the machine screaming from here... \ "help me! hellpp meeeee!"' - Heather Flanagan, 14:52:23 Wed Jun 10 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 22:48:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17214 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 22:48:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17205 for ; Tue, 1 Sep 1998 22:48:19 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA00740; Wed, 2 Sep 1998 15:17:03 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id PAA09987; Wed, 2 Sep 1998 15:16:54 +0930 (CST) Message-ID: <19980902151654.A606@freebie.lemis.com> Date: Wed, 2 Sep 1998 15:16:54 +0930 From: Greg Lehey To: david@sparks.net, hackers@FreeBSD.ORG Subject: Re: AMD K6-2/300? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from david@sparks.net on Tue, Sep 01, 1998 at 12:53:23PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 1 September 1998 at 12:53:23 -0400, david@sparks.net wrote: > Anyone using this with X successfully? > > I've got a new FIC 503+ mobo with teh 100 MHz FSB, K6-2/300 and a scsi > controller. > > It loads 2.2.7R fine, boots OK, but fails to run AccelleratedX or Xfree. > Both end up with a locked screen, and AcceleratedX won't even let me > ctl-alt-backspace out:( XIG says they only support the Intel processors. This sounds like an excuse. I've been running AcceleratedX for 9 months on a K6-233. I'd guess it's not the processor that's causing your problems--look at the display board first. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 23:16:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21369 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 23:16:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21354 for ; Tue, 1 Sep 1998 23:16:08 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA01133; Tue, 1 Sep 1998 23:12:51 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809012312.XAA01133@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: hackers@FreeBSD.ORG, cmascott@world.std.com, mckusick@mckusick.com Subject: Re: Reading/writing /usr/ports is VERY slow (fwd) In-reply-to: Your message of "Wed, 02 Sep 1998 05:04:59 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 23:12:49 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Kirk, please forgive me for copying you on this; if you have a moment or three to comment on the issues being raised here, I think we'd all benefit.) > Well, some of you might have seen this, some not, but there was a kind > of interesting thread on the newsgroup about /usr/ports access speed, > and the author of the message below (who is Cc:) found out that > creating a partition with only one cylinder group (instead of more > using the same exact disk and partition size and location) speeds > up disk access for /usr/ports by a factor of 3. This would definitely be the case for such a relatively static layout, at least for the traversal case (locality of reference). I think it might be quite suboptimal in the case where the directories were likely to shrink/grow on a regular basis, simply because it would encourage fragmentation. > I am not sure where this happens, but perhaps an easy fix could be to > stay in the same CG if its (CG) occupation is low enough ? The problem actually seems to stem from the code balancing directory allocations "too well". See below. > Before you mention softupdates... the author also experimented with > "noatime" and softupdates and the results were that using 1 CG > is much faster. The issue here is more the layout of actual data blocks, and the author's principal complaint is with reading, not writing, so lazy metadata isn't going to change all that much. > ---------- Forwarded message ---------- > Date: Tue, 1 SEP 1998 01:20:50 GMT > From: Carl Mascott > Newgroups: comp.unix.bsd.freebsd.misc > Subject: Re: Reading/writing /usr/ports is VERY slow ... > Take a look at my numbers again. The benefits of confining a > directory tree to one cylinder group are about twice as great as the > benefits of eliminating (not just reducing) metadata updates for the > read case. > > As I mentioned, the directory placement policy makes "find" slow as > well. That's more significant than performance in /usr/ports. The directory placement policy selects the cg with the fewest directories, and adds the directory there. If you're in the process of creating the ~5,000 directories in the ports collection, this is going to balance out the allocation of directories across your cg's and put you into a round-robin situation quite quickly. The code in question is pretty succinct, from ufs/ffs/ffs_alloc.c: /* * Find a cylinder to place a directory. * * The policy implemented by this algorithm is to select from * among those cylinder groups with above the average number of * free inodes, the one with the smallest number of directories. */ static ino_t ffs_dirpref(fs) register struct fs *fs; { int cg, minndir, mincg, avgifree; avgifree = fs->fs_cstotal.cs_nifree / fs->fs_ncg; minndir = fs->fs_ipg; mincg = 0; for (cg = 0; cg < fs->fs_ncg; cg++) if (fs->fs_cs(fs, cg).cs_ndir < minndir && fs->fs_cs(fs, cg).cs_nifree >= avgifree) { mincg = cg; minndir = fs->fs_cs(fs, cg).cs_ndir; } return ((ino_t)(fs->fs_ipg * mincg)); } You might improve this by stealing the fs_cgrotor field (which is set but never used by fs_blkpref) to apply a bias to the above selection; if the cg referenced by the rotor is within some threshold above the "best" cg, use the one referred to by the rotor instead. This threshold could probably be fairly small (eg. 8 or 16) with good results in this case; it would tend to cluster the allocation of directory inodes and thus their directories. In fact, it might make sense to recycle the rotor in a more general fashion; use it as a hint as to where allocation was performed last in order to cluster your allocation somewhat. static ino_t ffs_dirpref(fs) register struct fs *fs; { int cg, minndir, mincg, avgifree; avgifree = fs->fs_cstotal.cs_nifree / fs->fs_ncg; minndir = fs->fs_ipg; mincg = 0; for (cg = 0; cg < fs->fs_ncg; cg++) if (fs->fs_cs(fs, cg).cs_ndir < minndir && fs->fs_cs(fs, cg).cs_nifree >= avgifree) { mincg = cg; minndir = fs->fs_cs(fs, cg).cs_ndir; } /* Attempt to cluster allocations within reasonable thresholds */ if ((fs->fs_cs(fs, fs->fs_cgrotor).cs_nidir < (minndir + DIRDCLUSTER)) && (fs->fs_cs(fs, fs->fs_cgrotor).cs_nifree > (fs->fs_cs(fs, mincg).cs_nifree - DIRICLUSTER)) && (fs->fs_cs(fs, fs->fs_cgrotor).cs_nifree > 0)) { mincg = fs->fs_cgrotor; /* use previous allocation instead */ } else { fs->fs_cgrotor = mincg; /* remember new allocation area */ } return ((ino_t)(fs->fs_ipg * mincg)); } If someone were to take this and run with it, the results might be interesting. It would be worthwhile using fs_cgrotor as a hint in ffs_blkpref() as well (which currently sets it but never reads it). I don't have the time to experiment with this, but I'd certainly like to know where I'm wrong. > In short, I think that there are more long inter-group seeks on FFS > than there need be, due to the directory placement policy. I consider > it undesirable to spread directories out as much as possible all over > the filesystem. One of the substantial contributors to this problem has been the FreeBSD policy of limiting the number of cg's by faking the disk layout. The intention here was to reduce the amount of space wasted in administrative overhead, as well as increase the likelihood of contiguous allocation. Unfortunately one of the less wonderful consequences has been the substantial increase in inter-cg distances. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 1 23:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26666 for freebsd-hackers-outgoing; Tue, 1 Sep 1998 23:46:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26659 for ; Tue, 1 Sep 1998 23:46:25 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA01336; Tue, 1 Sep 1998 23:43:09 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809012343.XAA01336@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: Mike Smith , hackers Subject: Re: FFS questions In-reply-to: Your message of "Tue, 01 Sep 1998 18:33:18 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 23:43:08 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Thanks very much for your help. This morning I though I had pretty well > understood the subject and began to write the following summary. However, > when I finished it in the late afternoon, I find I am still have some > confusions. > > [positional/rotational table] > > Logically contiguous blocks should be assigned with blocks of neighboring > rotational positions. No; logically contiguous blocks are ideally assigned from optimally located rotational positions. > Blocks belonging to each rotational position are > linked together via two tables. I call them positional table and > rotational table. The positional table gives the first blocks belonging to > each rotational position within each cylinder in a cycle. There are > fs_nrpos * fs_cpc entries in the positional table. The rotational table > links the rest blocks together via block offsets. The number of entries in > the rotational table is equal to the number of blocks in a cycle. ... > There can be more than one physical blocks belonging to a rotational position > in the same cylinder. All these blocks are recorded in the above two tables. > The number of free blocks at each position for each cylinder is recorded > in individual cylinder groups that the cylinder belongs to. When we need a > block at a certain rotational position, we first check if the free count > is greater than zero. If so, we can scan through those blocks belonging > to the rotational position until a free block is find. This is a two step > search process. This seems to be correct. > The macro cbtorpos() only gives us the rotational positions within one > cylinder (There are a total of fs_nrpos such positions in a cylinder.) > So the offset pattern recorded in the rotational table is the same > for every cylinder. Why we need fs_cpc cylinders? There is no guarantee that the offset pattern will be the same for every cylinder. Consider the case where fs_nrpos is odd and the optimal offset between one rotational position and the next is 2. eg., allocating blocks starting with 'A': Rotational position: 0 1 2 +---+---+---+ Cylinder 0: | A | - | B | +---+---+---+ 1: | - | C | - | +---+---+---+ Note that I've ignored the track interleave, etc. here. In this case, fs_cpc is 2, and cannot be made less. To understand why a pattern is required, consider this layout: Rotational position: 0 1 2 3 (spare) +---+---+---+---+---+ Cylinder 0: | A | - | - | B | | +---+---+---+---+---+ 1: | - | C | - | - | | +---+---+---+---+---+ 2: | D | - | - | E | | +---+---+---+---+---+ Again, ignoring track interleave, you can see that the goal is to keep the gap from one rotational position to the next constant, but that's not always possible. > We do not let the offset pattern repeat itself. We just calculate the > pattern and reuse it for every fs_cpc cylinders (this way we can control > the size of the above two tables). If we let the pattern repeat itself, it > will not neccessary happen at a cylinder boundary and can take very long. More the issue is that it might be very large. With the standard 8 rotational groups per cylinder, you have 32 bytes per cylinder. For a modern IDE disk where > 10,000 cylinders is not uncommon in some modes, this would be unacceptable. > [hardware - interleave/disk skew] > > The disk is revolving at a constant speed. The old disk controllers are > slower compared with disk revolution speed. So when it have finished > reading a sector, the disk has moved beyond the next contiguous sector. > This is the reason for interleaving. This is already done by hardware (the > hardware automatically converts logical sector numbers to physical sector > numbers - relocation or mapping). The hardware only takes care of sequential > reading, FFS has to take acount of interrupt handling and I/O initiation. Generally correct; ffs doesn't directly handle interrupts or I/O, it passes these through device drivers and the block cache. > When the disk head moves from track to track, the disk continues to > revolve. This is the reason we have the disk skew (sector skew per > track). This setting is to be used by software (FFS in our case). Yes, although the track-to-track interleave may also be compensated for in hardware (by offsetting the location of sector 0 on the physical media). > From the definition of cbtorpos(), FFS has take account of the above two > factors. It converts a block number to a logical sector number and then > to physical sector number and finally to rotational position. > > #define cbtorpos(fs, bno) \ > (((bno) * NSPF(fs) % (fs)->fs_spc / (fs)->fs_nsect * (fs)->fs_trackskew + \ > (bno) * NSPF(fs) % (fs)->fs_spc % (fs)->fs_nsect * (fs)->fs_interleave) % \ > (fs)->fs_nsect * (fs)->fs_nrpos / (fs)->fs_npsect) That appears to be correct, yes. I am curious as to why you're so interested in this extremely obscure set of calculations. I've certainly had to think hard to remember half of this stuff, and I can't imagine any modern application for it... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 00:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29203 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 00:02:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29176 for ; Wed, 2 Sep 1998 00:02:06 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA01477; Tue, 1 Sep 1998 23:58:31 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809012358.XAA01477@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte cc: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Subject: Re: pci memory mapping In-reply-to: Your message of "Wed, 02 Sep 1998 00:05:04 +0200." <199809012205.AAA29093@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 23:58:30 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi there, > > I'm trying to get a Mylex DAC960PD to work with a driver skeleton Ulf > wrote. As I have a different Mylex board than Ulf (a PD iso a PG) I need > to make some changes. > > For some reason the followin code in attach() fails: > > if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, > &mp->pbase)) { > printf("myx%d: couldn't map memory\n", unit); > goto fail; > } Is PCI_MAP_REG_START the correct configuration register index for the memory-mapped region? It might help seeing the 'boot -v' output for this device from your system. > >From a previous post by Bill Paul I get the impression (...) that I might need > to enable memory mapping by doing a pci_conf_write(). But what params > do I feed pci_conf_write()? The config id, the register you want to write, and its value. You can determine these from the documentation for the PCI device you're talking to, or in some cases the PCI spec itself. > Interestingly enough for Ulf's board things work OK. Sounds like it defaults to enabling the memory-mapped region, where yours doesn't. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 00:03:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29516 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 00:03:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29491 for ; Wed, 2 Sep 1998 00:03:36 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA27439; Wed, 2 Sep 1998 00:02:33 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd027420; Wed Sep 2 00:02:28 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA21352; Wed, 2 Sep 1998 00:02:25 -0700 (MST) From: Terry Lambert Message-Id: <199809020702.AAA21352@usr02.primenet.com> Subject: Re: Thread calls To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 2 Sep 1998 07:02:25 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG, tinguely@plains.NoDak.edu In-Reply-To: from "Daniel O'Connor" at Sep 2, 98 11:13:38 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > the PMPTHREADS package (http://www.humanfactor.com/pthreads/) has > > > the pthread_setcancelstate(), pthread_setcanceltype(), and > > > pthread_testcancel() routines you require. > > > > But will require hacking to integrate into libc_r such that system > > call reentrancy is handled correctly. > > > > This is the problem with third party user space threading packages. > > > > Better to just add the code to FreeBSD. > > Well.. I was just asking if anyone was actually doing this or not =) > I did try the thrid party pthreads thing but it doesn't like -current, and then > I realised I'd have to recompile a few things (like X.. again) to use it. > > So, from what I hear, noone is implementing these calls in FreeBSD's libc_r? There is an OpenLDAP effort, which will necessitate these calls being implemented and/or the PTHREAD_MUTEX_INITIALIZER going away until FreeBSD complies with Draft 10 (Standard) pthreads. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 00:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00393 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 00:06:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00366 for ; Wed, 2 Sep 1998 00:06:28 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA04497; Wed, 2 Sep 1998 00:05:27 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd004450; Wed Sep 2 00:05:17 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA21597; Wed, 2 Sep 1998 00:05:15 -0700 (MST) From: Terry Lambert Message-Id: <199809020705.AAA21597@usr02.primenet.com> Subject: Re: Aladdin Ghostscript License and FreeBSD CD? To: joelh@gnu.org Date: Wed, 2 Sep 1998 07:05:15 +0000 (GMT) Cc: nick.hibma@jrc.it, jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <199809020318.WAA03114@detlev.UUCP> from "Joel Ray Holveck" at Sep 1, 98 10:18:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why don't we ask Aladdin? I think that finding out what they want > done is probably the best way to go, to make sure that no toes are > trampled either legally or ethically. You mean "why don't we ask them again?"... check the archives; this is nothing more than GPL vs. non-GPL advocacy, as far as I'm able to determine. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 00:08:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00887 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 00:08:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00872 for ; Wed, 2 Sep 1998 00:08:29 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA17325; Wed, 2 Sep 1998 16:36:19 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809020702.AAA21352@usr02.primenet.com> Date: Wed, 02 Sep 1998 16:36:17 +0930 (CST) From: "Daniel O'Connor" To: Terry Lambert Subject: Re: Thread calls Cc: tinguely@plains.NoDak.edu, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Sep-98 Terry Lambert wrote: > > So, from what I hear, noone is implementing these calls in FreeBSD's > > libc_r? > There is an OpenLDAP effort, which will necessitate these calls being > implemented and/or the PTHREAD_MUTEX_INITIALIZER going away until FreeBSD > complies with Draft 10 (Standard) pthreads. So, why was the PTHREAD_MUTEX_INITIALIZER thing implemented if it broke the ability to easily check between standards? ie is there a good reason to not back that change out until a more comprehensive set of patches comes along? --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 01:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11148 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 01:12:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11142 for ; Wed, 2 Sep 1998 01:12:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA28063; Wed, 2 Sep 1998 18:24:17 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199809020824.SAA28063@cimlogic.com.au> Subject: Re: Thread calls In-Reply-To: from Daniel O'Connor at "Sep 2, 98 04:36:17 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 2 Sep 1998 18:24:16 +1000 (EST) Cc: tlambert@primenet.com, tinguely@plains.NoDak.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > On 02-Sep-98 Terry Lambert wrote: > > > So, from what I hear, noone is implementing these calls in FreeBSD's > > > libc_r? > > There is an OpenLDAP effort, which will necessitate these calls being > > implemented and/or the PTHREAD_MUTEX_INITIALIZER going away until FreeBSD > > complies with Draft 10 (Standard) pthreads. > So, why was the PTHREAD_MUTEX_INITIALIZER thing implemented if it broke the > ability to easily check between standards? ie is there a good reason to not > back that change out until a more comprehensive set of patches comes along? I don't agree with Terry's assessment of Draft 10 vs Draft 4 issues in libc_r. AFAIK, the interfaces there are 1003.1c, and they exercise the POSIX standard clause: "either it shall be implemented like this or not implemented". Too many threaded programs assume that all the optional functions are supposed to be implemented. Just because you read it in a message on a mailing list doesn't make it true. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 01:17:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11829 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 01:17:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11824 for ; Wed, 2 Sep 1998 01:17:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA22949; Wed, 2 Sep 1998 17:46:09 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809020824.SAA28063@cimlogic.com.au> Date: Wed, 02 Sep 1998 17:46:09 +0930 (CST) From: "Daniel O'Connor" To: John Birrell Subject: Re: Thread calls Cc: freebsd-hackers@FreeBSD.ORG, tinguely@plains.NoDak.edu, tlambert@primenet.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Sep-98 John Birrell wrote: > > ability to easily check between standards? ie is there a good reason to not > > back that change out until a more comprehensive set of patches comes along? > I don't agree with Terry's assessment of Draft 10 vs Draft 4 issues > in libc_r. AFAIK, the interfaces there are 1003.1c, and they exercise > the POSIX standard clause: "either it shall be implemented like this or > not implemented". Too many threaded programs assume that all the optional > functions are supposed to be implemented. OK, I did not know this. (yeah yeah.. I didn't do any research on it :) It sounds like it has turned into a defacto standard for determining the thread version on the system though :( > Just because you read it in a message on a mailing list doesn't make it > true. Thats true, but my experience with threaded programs is kind of limited, so I am forced to take advice from other people :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 01:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12544 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 01:20:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12526 for ; Wed, 2 Sep 1998 01:20:52 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA28105; Wed, 2 Sep 1998 18:32:41 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199809020832.SAA28105@cimlogic.com.au> Subject: Re: Thread calls In-Reply-To: from Daniel O'Connor at "Sep 2, 98 05:46:09 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 2 Sep 1998 18:32:40 +1000 (EST) Cc: jb@cimlogic.com.au, freebsd-hackers@FreeBSD.ORG, tinguely@plains.NoDak.edu, tlambert@primenet.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > It sounds like it has turned into a defacto standard for determining the thread > version on the system though :( It's a Terry standard. Doh! > > Just because you read it in a message on a mailing list doesn't make it > > true. > Thats true, but my experience with threaded programs is kind of limited, so I > am forced to take advice from other people :) It would be helpful for people to contribute the parts they need support for. I don't work on thread cancellation issues because not all the systems I have to support have them. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 01:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13551 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 01:25:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13546 for ; Wed, 2 Sep 1998 01:25:26 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA23007; Wed, 2 Sep 1998 17:54:08 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809020832.SAA28105@cimlogic.com.au> Date: Wed, 02 Sep 1998 17:54:07 +0930 (CST) From: "Daniel O'Connor" To: John Birrell Subject: Re: Thread calls Cc: tlambert@primenet.com, tinguely@plains.NoDak.edu, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Sep-98 John Birrell wrote: > > version on the system though :( > It's a Terry standard. Doh! Heh :) > It would be helpful for people to contribute the parts they need support > for. I don't work on thread cancellation issues because not all the > systems I have to support have them. Hmm.. Ok :) I would like them because I want this program running :) I'll see what I can do =) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 01:33:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14667 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 01:33:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14657 for ; Wed, 2 Sep 1998 01:32:58 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id KAA05431; Wed, 2 Sep 1998 10:31:54 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id KAA08769; Wed, 2 Sep 1998 10:31:54 +0200 (MET DST) Date: Wed, 2 Sep 1998 10:31:54 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199809020831.KAA08769@surf.IAE.nl> To: luigi@labinfo.iet.unipi.it Subject: Re: kernel sysctl interface question... X-Newsgroups: list.freebsd.hackers In-Reply-To: <199809010757.JAA08942@labinfo.iet.unipi.it> Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199809010757.JAA08942@labinfo.iet.unipi.it> you write: >Hi, > >i notice that some (static) kernel data structures are exported to user >space using the sysctl interface, and that makes life easy for programs >that want to access these things -- examples are statistics etc. > >Now, i wonder if (and then how) i can use the same interface for >exporting dynamic data structures, e.g. things like "struct ifnet" >which are allocated more or less dynamically. In the current structure you can do certain things by creating a static node which "expands" on request through a function-call which mimics certain behaviour. I'm in the process of wanting to rewrite most of the internals, but given my current payload of work. I'm going to settle for less and first try to swap-out the static allocation and repalce with dynamic allocation. Leaving almost all else in place. As such I'm now really delving into the code to stay "compatible". What you want is doable, and from what I'va seen thus far, is also done for getting the routing tables through sysctl. Check the sources of: /usr/sbin/netstat Which will give you the idea on how a sysctl call is made for a dynamic structure /sys/kern/sysctl.c See how it is handled. to start with. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 01:38:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15539 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 01:38:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15521 for ; Wed, 2 Sep 1998 01:38:21 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA393; Wed, 2 Sep 1998 10:35:50 +0200 Message-ID: <35ED0377.B148C651@pipeline.ch> Date: Wed, 02 Sep 1998 10:36:07 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Terry Lambert CC: "Daniel O'Connor" , freebsd-hackers@FreeBSD.ORG, tinguely@plains.NoDak.edu Subject: Re: Thread calls References: <199809020702.AAA21352@usr02.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: -snip- > > > Better to just add the code to FreeBSD. > > > > Well.. I was just asking if anyone was actually doing this or not =) > > I did try the thrid party pthreads thing but it doesn't like -current, and then > > I realised I'd have to recompile a few things (like X.. again) to use it. > > > > So, from what I hear, noone is implementing these calls in FreeBSD's libc_r? > > There is an OpenLDAP effort, which will necessitate these calls being > implemented and/or the PTHREAD_MUTEX_INITIALIZER going away until FreeBSD > complies with Draft 10 (Standard) pthreads. The openldap-stable stuff compiles fine on 3.0-current (not yet testet on 2.2.7) and even the "make test" succeeds!! So I assume that there are some work-arounds and/or changes in that code... -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 05:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07842 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 05:20:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07816; Wed, 2 Sep 1998 05:20:56 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199809021220.FAA07816@hub.freebsd.org> Subject: Re: Test dont read! In-Reply-To: <199809011311.PAA04090@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Sep 1, 98 03:11:16 pm" To: sos@FreeBSD.ORG Date: Wed, 2 Sep 1998 05:20:56 -0700 (PDT) Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please never do this. if you need to test, send your message to test@freebsd.org. you may want to subscribe to test first jmb Sřren Schmidt wrote: > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Sřren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 05:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11160 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 05:45:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA11153 for ; Wed, 2 Sep 1998 05:45:08 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA10604; Wed, 2 Sep 1998 12:46:59 +0200 From: Luigi Rizzo Message-Id: <199809021046.MAA10604@labinfo.iet.unipi.it> Subject: Re: Reading/writing /usr/ports is VERY slow (fwd) To: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Date: Wed, 2 Sep 1998 12:46:58 +0200 (MET DST) In-Reply-To: <199809012312.XAA01133@word.smith.net.au> from "Mike Smith" at Sep 1, 98 11:12:30 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, thanks a lot for the very detailed reply. just a stupid question, but is there any obvious problem in using like a 400MB partition only for ports with just 1 CG. And another one... your suggestion works as long as there is only one writer, if there is concurrent activity you are not going to get any advantage ? > One of the substantial contributors to this problem has been the > FreeBSD policy of limiting the number of cg's by faking the disk > layout. The intention here was to reduce the amount of space wasted in and because of this and big disks, CGs tend to be large so perhaps the hysteresis to be used in allocations (isn't that what you proposed ?) should be computed as a percentage of the CG (or whole partition ?) size rather than a fixed constant. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 05:52:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12375 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 05:52:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wph.bbs.edu.cn (dialuser118.gb.com.cn [203.93.18.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12364 for ; Wed, 2 Sep 1998 05:52:09 -0700 (PDT) (envelope-from peihanw@mx.cei.gov.cn) Received: from mx.cei.gov.cn (localhost [127.0.0.1]) by wph.bbs.edu.cn (8.8.8/8.8.7) with ESMTP id UAA00497 for ; Wed, 2 Sep 1998 20:44:29 +0800 (CST) (envelope-from peihanw@mx.cei.gov.cn) Message-ID: <35ED3DA0.9F510F5A@mx.cei.gov.cn> Date: Wed, 02 Sep 1998 20:44:16 +0800 From: Peihan Wang X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: man page about inet_pton(...) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this question should be send here. I am learning UNIX network programming on my 2.2.6 box. I just bought a book "UNIX Network Programming Volum I 2nd ed. --- Networking APIs: Sockets and XTI" by W.Richard Stevens. There is a simple example in chapter 1 which uses function "int inet_pton(int, const char *, void *)". In the comments of the program, the author explained that inet_pton() is an IPv6 function, and inet_addr() can be used to substitute it. I tried 'man inet_pton' but thereis no man page for it, but when I browse /usr/include/arpa/inet.h it is declared. Although I have tested inet_pton() and there is nothing wrong about it, I still feel uncomfortable for I can not find man pages about IPv6 functions. Who can tell me where to get documents about IPv6 functions and why there is no man pages about it on FreeBSD. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 06:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17366 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 06:21:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA17312 for ; Wed, 2 Sep 1998 06:20:55 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA08429; Wed, 2 Sep 1998 09:22:49 -0400 From: Bill Paul Message-Id: <199809021322.JAA08429@skynet.ctr.columbia.edu> Subject: Re: pci memory mapping To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 2 Sep 1998 09:22:48 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809012205.AAA29093@yedi.iaf.nl> from "Wilko Bulte" at Sep 2, 98 00:05:04 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Wilko Bulte had to walk into mine and say: > Hi there, > > I'm trying to get a Mylex DAC960PD to work with a driver skeleton Ulf > wrote. As I have a different Mylex board than Ulf (a PD iso a PG) I need > to make some changes. > > For some reason the followin code in attach() fails: > > if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, > &mp->pbase)) { > printf("myx%d: couldn't map memory\n", unit); > goto fail; > } > > From a previous post by Bill Paul I get the impression (...) that I might need > to enable memory mapping by doing a pci_conf_write(). But what params > do I feed pci_conf_write()? Given that you learned this from a posting by Bill Paul, would it not then make sense to read the driver code that Bill Paul has recently written to see how he did it? :) > This is all new to me, I could really use some advise here. First of all, bear in mind that not every PCI device supports memory mapping of its registers. To find out if yours does or not, you need to check the device's manual or datasheet. It's also possible that the device does support memory mapped access but the 'memory map enable' bit in the command register is off. To turn it on, you need to do something like the following: u_int32_t command; /* read the PCI command register */ command = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); /* set the memory map enable bit */ command |= PCIM_CMD_MEMEN; /* write it back to the register */ pci_conf_write(config_id, PCI_COMMAND_STATUS_REG, command); /* check that it worked */ command = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); if (!(command & PCIM_CMD_MEMEN)) printf("failed to enable memory mapped access!\n"); Note that this is for -current. The constant PCIM_CMD_MEMEN has a different name in 2.2.x. If you compare the XL driver from 3.0 and 2.2.x, you can see the differences. The constants are defined in /sys/pci/pcireg.h. This code should be used in the PCI attach routine: the PCI support code passes the attach function a PCI ID handle as the first argument, which is called config_id here. Ulf may have used a different variable name. If the bit doesn't come on after you write to the command register, it probably means the device doesn't actually support memory mapped access. In this case, the driver must use PIO access (inb/outb). For this, you must make sure the PCIM_CMD_PORTEN bit is set. Lastly, if the device is a bus master (and being a disk controller I suppose it would make sense that it would be) you should check that the PCIM_CMD_BUSMASTEREN bit is set too. I'm not certain why these bits are not always on, however I've heard nebulous statements that this has something to do with Windows turning them off and the PCI BIOS leaving that way. I decided to always try forcing them on just to cover myself. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 07:31:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27598 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 07:31:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27579 for ; Wed, 2 Sep 1998 07:31:01 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id KAA23663 for ; Wed, 2 Sep 1998 10:43:21 -0400 (EDT) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.8.7/8.8.7) with ESMTP id KAA04745 for ; Wed, 2 Sep 1998 10:29:51 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Message-Id: <199809021429.KAA04745@stiegl.niksun.com> X-Mailer: exmh version 2.0zeta 7/24/97 From: Andrew Heybey To: freebsd-hackers@FreeBSD.ORG Subject: cvsup questions Date: Wed, 02 Sep 1998 10:29:51 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to be able to make local changes to the FreeBSD source tree, check them in on a branch into a local copy of the repository, and then merge FreeBSD updates with my changes as necessary. I have cvsup'd the repository, but after reading the documentation I have a couple of questions: The "Blurb" file that comes with cvsup says: - A client who uses CVSup to maintain a CVS repository can check in local modifications, without interference from CVSup. CVSup will bring in new revisions, tags, and branches from the server, without disturbing revisions, tags, and branches that were created locally. This is possible because CVSup parses and understands RCS files. Of course, for this to work, the revision numbers must not collide. This (above) is exactly what I want to do. However, the "Announce" file says: > CVSup is able to merge new deltas and tags from the server with deltas > and tags added locally on the client machine. This makes it possible > for the client to check local modifications into his repository > without their being obliterated by subsequent updates from the server. > Note: Although this feature is fully implemented in CVSup, it will > probably not be practical to use it until some small changes have been > made to CVS. which seems to contradict the above paragraph. Is the second paragraph out of date, or does it mean something slightly different (maybe the second paragraph is talking about merging changes made locally on the *same* branch as the deltas coming from the server?), or am I otherwise confused? Second question: The cvsup man page says about the "delete" keyword: In exact mode, CVSup verifies every edited file with a checksum, to ensure that the edits have produced a file identical to the master copy on the server. If the checksum test fails for a file, then CVSup falls back upon transferring the entire file. This seems to imply to me that I *don't* want to set the "delete" keyword because if I make local changes that cvsup will at best get confused and at worst copy the server's file on top of my version. But the handbook says about the "delete" keyword: You should always specify this, so that CVSup can keep your source tree fully up to date. without any exceptions such as "unless you are making local changes". Is cvsup smart enough to deal with local changes even when in exact mode? thanks, andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 08:36:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07800 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 08:36:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07776; Wed, 2 Sep 1998 08:36:02 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.8/8.8.5) with SMTP id LAA07880; Wed, 2 Sep 1998 11:37:29 -0400 (EDT) Date: Wed, 2 Sep 1998 11:37:29 -0400 (EDT) From: Mark turpin To: FreeBSD hackers , FreeBSD Current Subject: make world problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I do a make world I get the followind error after about 2 1/2 hours install - -o bin -g bin -m 644 /lkm/misc/module/@/arpa/ftp.h /usr/share/examples/lkm/module/@/arpa/ftp.h install: /usr/share/examples/lkm/module/@/arpa/ftp.h : No such file or directory *** Error code 71 Stop. It's cvsup'd as of Sept 1 1998 12:30 EDT Is there something wrong or is my brain fried... Thanks Mark Turpin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 08:54:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11183 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 08:54:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11170 for ; Wed, 2 Sep 1998 08:54:54 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id PAA13386 for ; Wed, 2 Sep 1998 15:53:52 GMT (envelope-from didier@omnix.net) Date: Wed, 2 Sep 1998 17:53:52 +0200 (CEST) From: Didier Derny To: freebsd-hackers@FreeBSD.ORG Subject: motif Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there and which is the best Motif distribution working with FreeBSD 3.0 ? thanks for your help -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 08:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11711 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 08:57:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11706 for ; Wed, 2 Sep 1998 08:57:26 -0700 (PDT) (envelope-from rvb@sicily.odyssey.cs.cmu.edu) From: rvb@sicily.odyssey.cs.cmu.edu To: joelh@gnu.org Cc: mike@smith.net.au, avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG Subject: Re: TCP performance. (& pccard) References: <199808310953.JAA20742@word.smith.net.au> <199809010004.TAA11451@detlev.UUCP> Date: 02 Sep 1998 11:55:53 -0400 In-Reply-To: Joel Ray Holveck's message of Mon, 31 Aug 1998 19:04:23 -0500 (CDT) Message-ID: Lines: 23 X-Mailer: Gnus v5.4.46/Emacs 19.34 Source-Info: Sender is really rvb@sicily.odyssey.cs.cmu.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck writes: > > Having said that, bear in mind that the 'zp' driver is a bandaid > > that only exists to aid installation, and you may well be better off > > using the 'ep' driver inside the pccard framework. On the otherhand, I'm using a 3c589c (and 3c589d) on a 560X and I gave up on the zp driver because it would hand. I've not had that problem with the ep. > > The ep driver still leaks like a sieve, or did two weeks ago or so. I > haven't gotten to work on it yet. ---- This should probably be a different thread, but how do people use pccard with -current. I had to add a sleep 30 to the end of the rc.pccard otherwise rc.network tries to start the network before pccardd has found it. Also, does (or why doesn't) apm -z work when cards are in. Finally, I remap the cntl and caps lock keys. Should this mapping be done earlier in /etc/rc. When I have to ^C sendmail because the network is not there, I have to use the old/original keyboard bindings. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 09:18:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16580 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 09:18:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16571 for ; Wed, 2 Sep 1998 09:18:40 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA22885; Wed, 2 Sep 1998 09:17:32 -0700 (PDT) (envelope-from jdp) Message-Id: <199809021617.JAA22885@austin.polstra.com> To: ath@niksun.com Subject: Re: cvsup questions In-Reply-To: <199809021429.KAA04745@stiegl.niksun.com> References: <199809021429.KAA04745@stiegl.niksun.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Wed, 02 Sep 1998 09:17:32 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199809021429.KAA04745@stiegl.niksun.com>, Andrew Heybey wrote: > I want to be able to make local changes to the FreeBSD source tree, > check them in on a branch into a local copy of the repository, and > then merge FreeBSD updates with my changes as necessary. There's a whole section on this topic in the CVSup FAQ: http://www.polstra.com/projects/freeware/CVSup/ John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 09:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17541 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 09:23:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17533 for ; Wed, 2 Sep 1998 09:23:41 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA358; Wed, 2 Sep 1998 09:58:16 -0600 Received: from count.timing.com (localhost.timing.com [127.0.0.1]) by count.timing.com (8.8.7/8.8.7) with ESMTP id JAA12876; Wed, 2 Sep 1998 09:58:04 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199809021558.JAA12876@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: chanders@timing.com (Craig Anderson), freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_cancel In-reply-to: Your message of "Wed, 02 Sep 1998 00:36:13 -0000." <199809020036.RAA09470@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 09:58:03 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking at Appendix B of the O'Reilly book, Pthreads Programming. The section on cancellation mentions a change in setting cancellation state. A change in pthread_cancel() is not mentioned. Can someone suggest an alternative to pthread_cancel()? > > I am starting to use threads on a FreeBSD 2.2.6 system. > > Is there a pthread_cancel() function? > > No. FreeBSD provides Draft 4 pthreads, not the Draft 10 (Standard). > > FreeBSD -current is, right now, a bastard child of Draft 4 and > Standard, with the only way to tell them apart being one of the > few things that was braought up to Standard. 8-(. > > Use Draft 4 programming techniques, and you will be fine. See > the O'Reilly Pthreads book for exmaples of how to substitute code; > there is an appendix dedicated to the differences. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 09:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20072 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 09:40:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles248.castles.com [208.214.165.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20067 for ; Wed, 2 Sep 1998 09:40:35 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id JAA03759; Wed, 2 Sep 1998 09:36:40 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809020936.JAA03759@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: rvb@sicily.odyssey.cs.cmu.edu cc: joelh@gnu.org, mike@smith.net.au, avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG Subject: Re: TCP performance. (& pccard) In-reply-to: Your message of "02 Sep 1998 11:55:53 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 09:36:38 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ---- > This should probably be a different thread, but how do people use > pccard with -current. I had to add a sleep 30 to the end of the > rc.pccard otherwise rc.network tries to start the network before > pccardd has found it. This is because you're trying to use an ifconfig_foo line, where you should be using the pccard_ifconfig in /etc/rc.conf. > Also, does (or why doesn't) apm -z work when > cards are in. Your APM BIOS may refuse the shutdown; there's nothing in the system which prevents it from working (I use 'zzz' here regularly). > Finally, I remap the cntl and caps lock keys. Should > this mapping be done earlier in /etc/rc. When I have to ^C sendmail > because the network is not there, I have to use the old/original > keyboard bindings. You shouldn't do it at all; use the keyboard you have. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 10:03:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23645 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 10:03:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA23640 for ; Wed, 2 Sep 1998 10:02:59 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA10910; Wed, 2 Sep 1998 17:06:30 +0200 From: Luigi Rizzo Message-Id: <199809021506.RAA10910@labinfo.iet.unipi.it> Subject: bcmp abuse in networking code ? To: hackers@FreeBSD.ORG Date: Wed, 2 Sep 1998 17:06:30 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG poking around in /sys/net and /sys/netinet, i frequently see bcmp() being used to compare ethernet addresses (but not only those). In some cases, even against the ethernet broadcast address. In my revised bridge code i have the following macros #define ETH_MATCH(a,b) ( \ ((unsigned short *)(a))[2] == ((unsigned short *)(b))[2] && \ *((unsigned int *)(a)) == *((unsigned int *)(b)) ) #define IS_ETHER_BROADCAST(a) ( \ *((unsigned int *)(a)) == 0xffffffff && \ ((unsigned short *)(a))[2] == 0xffff ) which seem to do a decent job in terms of performance. On a Pentium90, they save about 40-50 ticks per call, which is not bad considering how frequently they are used on a bridge or on a multicast router. I suppose the macros as above might have some alignment problems on the Alpha, but one could always make them conditionals and resort to the old method for the Alpha. How about putting something similar in, say, sys/net/ethernet.h (and BTW eliminate the useless etherbroadcastaddr[] variable from /sys/net/if_ethersubr.c, whose prototype is in /sys/netinet/if_ether.h where i am not really sure it belongs to!) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 11:23:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07129 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 11:23:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA07124 for ; Wed, 2 Sep 1998 11:23:16 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA03384 (5.67b/IDA-1.5); Wed, 2 Sep 1998 20:19:15 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA10258; Wed, 2 Sep 1998 19:34:00 +0200 (CEST) From: Wilko Bulte Message-Id: <199809021734.TAA10258@yedi.iaf.nl> Subject: Re: pci memory mapping In-Reply-To: <199809021322.JAA08429@skynet.ctr.columbia.edu> from Bill Paul at "Sep 2, 98 09:22:48 am" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Wed, 2 Sep 1998 19:34:00 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bill Paul wrote... > Of all the gin joints in all the towns in all the world, Wilko Bulte had > to walk into mine and say: > > > Hi there, > > > > I'm trying to get a Mylex DAC960PD to work with a driver skeleton Ulf > > wrote. As I have a different Mylex board than Ulf (a PD iso a PG) I need > > to make some changes. > > > > For some reason the followin code in attach() fails: > > > > if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, > > &mp->pbase)) { > > printf("myx%d: couldn't map memory\n", unit); > > goto fail; > > } > > > > From a previous post by Bill Paul I get the impression (...) that I might need > > to enable memory mapping by doing a pci_conf_write(). But what params > > do I feed pci_conf_write()? > > Given that you learned this from a posting by Bill Paul, would it not then > make sense to read the driver code that Bill Paul has recently written to > see how he did it? :) "Guilty your Honor" %-) > > This is all new to me, I could really use some advise here. > > First of all, bear in mind that not every PCI device supports memory > mapping of its registers. To find out if yours does or not, you need > to check the device's manual or datasheet. Right.... manual...... I'm still trying to convince Mylex that handing me a copy of the DAC960 V2.xx programming manual will not wipe all life from Planet Earth. Sigh. Sample code from Linux and Ulf's driver are based on firmware V4.xx which is different in it's interface to the OS. > It's also possible that the device does support memory mapped access > but the 'memory map enable' bit in the command register is off. To turn > it on, you need to do something like the following: > > u_int32_t command; > > /* read the PCI command register */ > command = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); > /* set the memory map enable bit */ > command |= PCIM_CMD_MEMEN; > /* write it back to the register */ > pci_conf_write(config_id, PCI_COMMAND_STATUS_REG, command); > /* check that it worked */ > command = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); > if (!(command & PCIM_CMD_MEMEN)) > printf("failed to enable memory mapped access!\n"); > > Note that this is for -current. The constant PCIM_CMD_MEMEN has a > different name in 2.2.x. If you compare the XL driver from 3.0 and > 2.2.x, you can see the differences. The constants are defined in > /sys/pci/pcireg.h. OK, I followed your advise, and unfortunately still no-go. It is quite possible that the DAC960 old firmware does not do memory mapped access. > If the bit doesn't come on after you write to the command register, it > probably means the device doesn't actually support memory mapped access. Well, the bit comes on because the printf() is not triggered. But still I get the 'cannot map memory' from the code sample at the top of this mail. > In this case, the driver must use PIO access (inb/outb). For this, you > must make sure the PCIM_CMD_PORTEN bit is set. Lastly, if the device is > a bus master (and being a disk controller I suppose it would make sense > that it would be) you should check that the PCIM_CMD_BUSMASTEREN bit is > set too. I'll check, maybe some kind soul at Mylex can at least tell me if V2.x firmware supports memory mapping or not. > I'm not certain why these bits are not always on, however I've heard > nebulous statements that this has something to do with Windows turning > them off and the PCI BIOS leaving that way. I decided to always try > forcing them on just to cover myself. Sounds like a reasonable idea ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 12:59:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23570 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 12:59:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23562 for ; Wed, 2 Sep 1998 12:59:24 -0700 (PDT) (envelope-from jsalas@citi.com.mx) Received: from intra.citi.com.mx (intra.citi.com.mx [200.34.113.90]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id MAA15056 for ; Wed, 2 Sep 1998 12:59:04 -0700 (PDT) X-Internal-ID: 35EBE6F7000003C8 Received: from citi.com.mx (200.34.113.90) by intra.citi.com.mx (NPlex 2.0.098) for freebsd-hackers@freefall.cdrom.com; 3 Sep 1998 08:58:56 -0000 Message-ID: <35EE5A50.97C8C5FF@citi.com.mx> Date: Thu, 03 Sep 1998 02:58:56 -0600 From: "Julio César Salas García" Reply-To: jsalas@citi.com.mx Organization: CITI X-Mailer: Mozilla 4.06 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-hackers@freefall.cdrom.com Subject: why the crontab doesnt works... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG can you help me, i have a freebsd system and the crontab is not working properly, the daemon is working, but it doesnt make anything...can you send me examples or the steps to make it work? thanks a lot....seeya. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 13:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00354 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 13:40:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00316 for ; Wed, 2 Sep 1998 13:40:31 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id PAA05750; Wed, 2 Sep 1998 15:37:39 -0400 (EDT) Date: Wed, 2 Sep 1998 15:37:38 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Didier Derny cc: freebsd-hackers@FreeBSD.ORG Subject: Re: motif In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Sep 1998, Didier Derny wrote: > > Is there and which is the best Motif distribution working > with FreeBSD 3.0 ? > I've been using Xig's Motif 2.0 ... it's aout, but that has worked just fine for me. Warning, tho, because I really hate mwm, and never use it (I bought Motif for the libs) and if there's bugs in mwm, I wouldn't know about it. It costs $100, and I've been pleased with their tech support. For $100, not having to wonder if you're stumbling over a Lesstif bug or not has been pretty nice, money well spent. It works just fine with the XFree86 server, too. > thanks for your help > > -- > Didier Derny > didier@omnix.net > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 14:54:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11946 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 14:54:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA11937 for ; Wed, 2 Sep 1998 14:54:32 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA09174; Wed, 2 Sep 1998 17:56:22 -0400 From: Bill Paul Message-Id: <199809022156.RAA09174@skynet.ctr.columbia.edu> Subject: Re: pci memory mapping To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 2 Sep 1998 17:56:21 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809021734.TAA10258@yedi.iaf.nl> from "Wilko Bulte" at Sep 2, 98 07:34:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Wilko Bulte had to walk into mine and say: > > > I'm trying to get a Mylex DAC960PD to work with a driver skeleton Ulf > > > wrote. As I have a different Mylex board than Ulf (a PD iso a PG) I need > > > to make some changes. > > > > > > For some reason the followin code in attach() fails: > > > > > > if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, > > > &mp->pbase)) { > > > printf("myx%d: couldn't map memory\n", unit); > > > goto fail; > > > } Okay, Ulf has sent me a copy of his source code so I could look at it. This doesn't seem quite right somehow. The constant PCI_MAP_REG_START is #define in /sys/pci/pcireg.h: #define PCI_MAP_REG_START 0x10 On the two devices that I've fiddled with so far, namely the ThunderLAN chip and the 3Com chip, 0x10 has always been the I/O base address, i.e. the address used for inb/outb PIO access, and 0x14 is the memory base address used for memory mapped access. My impression is that these two registers are standar, so it's unlikely that their meanings would be reversed unless the chip designer is up to no good. In any case, I would try to use 0x14 instead of PCI_MAP_REG_START and see if that makes a difference. > > First of all, bear in mind that not every PCI device supports memory > > mapping of its registers. To find out if yours does or not, you need > > to check the device's manual or datasheet. > > Right.... manual...... I'm still trying to convince Mylex that handing me > a copy of the DAC960 V2.xx programming manual will not wipe all life from > Planet Earth. Sigh. Sample code from Linux and Ulf's driver are based on > firmware V4.xx which is different in it's interface to the OS. Do not read sample Linux code without a barf bag nearby. > > If the bit doesn't come on after you write to the command register, it > > probably means the device doesn't actually support memory mapped access. > > Well, the bit comes on because the printf() is not triggered. But still I > get the 'cannot map memory' from the code sample at the top of this mail. Then I'm probably right about the register that you need to supply to pci_map_mep(). This is just idle speculation, but maybe the other cards only support memory mapped mode, and the I/O base and mem base registers have the same values in them. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 15:54:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21075 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 15:54:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21064 for ; Wed, 2 Sep 1998 15:54:09 -0700 (PDT) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id SAA27283; Wed, 2 Sep 1998 18:53:05 -0400 (EDT) Received: from europa.local (world-f.std.com) by world.std.com (TheWorld/Spike-2.0) id AA06328; Wed, 2 Sep 1998 18:53:03 -0400 Received: (from cmascott@localhost) by europa.local (8.8.8/8.8.8) id SAA00872 for hackers@freebsd.org; Wed, 2 Sep 1998 18:52:59 -0400 (EDT) (envelope-from cmascott) Date: Wed, 2 Sep 1998 18:52:59 -0400 (EDT) From: Carl Mascott Message-Id: <199809022252.SAA00872@europa.local> To: hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > > Well, some of you might have seen this, some not, but there was a kind > > of interesting thread on the newsgroup about /usr/ports access speed, > > and the author of the message below (who is Cc:) found out that > > creating a partition with only one cylinder group (instead of more > > using the same exact disk and partition size and location) speeds > > up disk access for /usr/ports by a factor of 3. > Mike Smith wrote: > This would definitely be the case for such a relatively static layout, > at least for the traversal case (locality of reference). I think it > might be quite suboptimal in the case where the directories were likely > to shrink/grow on a regular basis, simply because it would encourage > fragmentation. Agreed. I don't suggest abandoning cylinder groups, or allowing a cylinder group to fill up while there's still plenty of space in the filesystem. Carl Mascott wrote: > > In short, I think that there are more long inter-group seeks on FFS > > than there need be, due to the directory placement policy. I consider > > it undesirable to spread directories out as much as possible all over > > the filesystem. > Mike Smith wrote: > One of the substantial contributors to this problem has been the > FreeBSD policy of limiting the number of cg's by faking the disk > layout. The intention here was to reduce the amount of space wasted in > administrative overhead, as well as increase the likelihood of > contiguous allocation. Unfortunately one of the less wonderful > consequences has been the substantial increase in inter-cg distances. For a filesystem of any given size the number of cg's is not a factor, at least not as long as there are more than a couple of them. As long as new directories get distributed pseudo-randomly over the filesystem, which is what happens in /usr/ports, it doesn't matter how many cg's the filesystem is subdivided into. The disk arm will still be covering the same distance. However, if a cg proximity criterion were added to the new-cg-chooser, then the size of a cg would become a factor, although I don't know how important a factor. For what it's worth, vxfs also uses 32 MB cg's ("allocation units" in vxfs-speak). Hopefully someone who knows the history of FFS development will chime in at this point. It would be nice to know if any other directory placement policies were ever tried and rejected. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 15:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21086 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 15:54:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21070 for ; Wed, 2 Sep 1998 15:54:13 -0700 (PDT) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id SAA27281; Wed, 2 Sep 1998 18:53:05 -0400 (EDT) Received: from europa.local (world-f.std.com) by world.std.com (TheWorld/Spike-2.0) id AA06327; Wed, 2 Sep 1998 18:53:03 -0400 Received: (from cmascott@localhost) by europa.local (8.8.8/8.8.8) id SAA00868 for hackers@freebsd.org; Wed, 2 Sep 1998 18:52:35 -0400 (EDT) (envelope-from cmascott) Date: Wed, 2 Sep 1998 18:52:35 -0400 (EDT) From: Carl Mascott Message-Id: <199809022252.SAA00868@europa.local> To: hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To go along with the discussion of FFS directory allocation policy and its effect on performance, here is my posting to comp.unix.bsd.freebsd.misc prior to the one that Luigi Rizzo quoted from on this list. This earlier posting of mine contains my test data, which people might want to look at. Most of my discussion of softupdates isn't relevant here. I was refuting another posting to the newsgroup that was trying to suggest that softupdates was the cure for this performance problem. I have subscribed to hackers@freebsd.org to follow this, so it's no longer necessary to Cc me. ------------- Thanks to all who confirmed that the slow filesystem throughput on /usr/ports is a generic problem. I performed some experiments to try to pin down the cause of the slow read throughput, and I think I succeeded. I measured read throughput on /usr/ports and /var/tmp/ports, a subset of the ports collection that I constructed for these tests. (I didn't have room on /var for the whole collection.) The test consisted of tarring the directory tree to stdout and redirecting stdout to /dev/null. The reason for testing read throughput rather than write throughput is that reading is a simpler case: there are no allocations, and, with noatime, there are no metadata updates. /usr/ports /var/tmp/ports ---------- -------------- disk usage (du) 58243 8753 files 32575 4328 directories 12361 1647 avg files per directory 2.64 2.63 /usr filesystem: 512 MB, 8K/1K, 16 x 32 MB cylinder groups, 50% full, Seagate Barracuda 2LP /var filesystem: 30 MB, 8K/1K, 1 x 30 MB cylinder group, 46% full, Seagate Hawk 2LP FILESYSTEM READ THROUGHPUT, KB/S /usr/ports 142.4 /usr/ports, noatime 192.2 /var/tmp/ports 336.7 /var/tmp/ports, noatime 564.7 The throughput on /var/tmp/ports is 2.36x or 2.94x (noatime) greater than on /usr/ports. The composition of the two trees is similar. The difference is that /var/tmp/ports is contained entirely in one cylinder group (because that's all the filesystem has), while /usr/ports is spread over 16 cylinder groups. Remember, FFS places every new directory in a different cylinder group than that of its parent. This test actually understates the performance advantage of having the entire tree in one cylinder group because /var is on a slower disk than is /usr. This test shows that metadata updates are not the main performance problem when reading /usr/ports. Eliminating them entirely gives a read speedup of only 1.35x. This is an upper bound on the improvement that softupdates could make in read throughput. I don't have a feeling for the effect of metadata updates or the efficacy of the softupdates modifications where write throughput is concerned. I see write throughput of 9 KB/s in /usr/ports. Perhaps the softupdates mods would help to get the write throughput closer to the read throughput (i.e., improve it from abysmal to poor). In any event softupdates is not an option for me until it appears in -stable. To improve the read and write throughput from poor to fair, which is the best you'll ever do with something like /usr/ports, the seeks have got to be reduced a lot. Where to go from here? A tree like /usr/ports is really atypical (2.6 small files per directory). One wouldn't want to speed up FFS on /usr/ports if the result was to slow it down on more typical file I/O. That said, I still have to wonder if FFS's directory placement policy can't be improved upon. One definitely doesn't want to let a cylinder group fill up while there is still plenty of space in the filesystem. But it might be possible to accomplish this without spreading new directories all over the filesystem. By the way, another thing that suffers from FFS's directory placement policy is the find command, and not just when it is run in /usr/ports. Try running it in /usr/src if you have a moderate amount of source installed and just listen to your disk drive. I'm really curious about the directory placement policy in vxfs (Veritas), which also has cylinder groups (called allocation units). Does anybody happen to know what it is? ------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 16:21:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25318 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 16:21:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from singapore.eecs.umich.edu (singapore.eecs.umich.edu [141.213.8.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25310 for ; Wed, 2 Sep 1998 16:21:05 -0700 (PDT) (envelope-from weeteck@eecs.umich.edu) Received: (from weeteck@localhost) by singapore.eecs.umich.edu (8.8.8/8.8.7) id TAA01630 for freebsd-hackers@FreeBSD.ORG; Wed, 2 Sep 1998 19:20:00 -0400 (EDT) From: Wee Teck Ng Message-Id: <199809022320.TAA01630@singapore.eecs.umich.edu> Subject: switching to real-address mode To: freebsd-hackers@FreeBSD.ORG Date: Wed, 2 Sep 1998 19:20:00 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm trying to switch to real-address mode from protected mode in the kernel (freebsd 2.2.7), but without success. i had followed the instructions in the intel manual (p8-14 of system prog guide), but my code always hung after clearing PE flag in CR0. i would appreciate comments from anyone who have done this before. thanks wee teck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 16:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00486 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 16:49:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00481 for ; Wed, 2 Sep 1998 16:49:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00897; Wed, 2 Sep 1998 16:45:37 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809021645.QAA00897@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wee Teck Ng cc: freebsd-hackers@FreeBSD.ORG Subject: Re: switching to real-address mode In-reply-to: Your message of "Wed, 02 Sep 1998 19:20:00 -0400." <199809022320.TAA01630@singapore.eecs.umich.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 16:45:37 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i'm trying to switch to real-address mode from protected mode in > the kernel (freebsd 2.2.7), but without success. i had followed > the instructions in the intel manual (p8-14 of system prog guide), > but my code always hung after clearing PE flag in CR0. i would > appreciate comments from anyone who have done this before. You can't do this without throwing most of the kernel away, and you probably don't want to do that. What are you actually trying to do? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 17:37:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08521 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 17:37:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08512 for ; Wed, 2 Sep 1998 17:37:33 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA24361; Wed, 2 Sep 1998 17:36:25 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd024335; Wed Sep 2 17:36:17 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA00192; Wed, 2 Sep 1998 17:36:14 -0700 (MST) From: Terry Lambert Message-Id: <199809030036.RAA00192@usr07.primenet.com> Subject: Re: default syslog priority for kernel messages To: archie@whistle.com (Archie Cobbs) Date: Thu, 3 Sep 1998 00:36:14 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809020215.TAA00488@bubba.whistle.com> from "Archie Cobbs" at Sep 1, 98 07:15:31 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > IMHO, printf() in the kernel should be deprecated in favor of log(). > > > > The only problem is that it's possible to printf from the kernel > > without logging, and it may frequently be desirable to send a message > > to the console without logging it. > > So then kill syslogd. > > Here is the comment in the code: > > /* > * Log writes to the log buffer, and guarantees not to sleep (so can be > * called by interrupt routines). If there is no process reading the > * log yet, it writes to the console also. > */ The printf calls are special-use calls. They are not merely the "printf" that you think should be "log". The "printf" is merely a wrapper for "kvprintf". Instead of putting "log" in those places, if you got rid of "printf", the correct thing to do would be to call "kvprintf" (not "log"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 17:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08773 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 17:38:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08768 for ; Wed, 2 Sep 1998 17:38:45 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA24842; Wed, 2 Sep 1998 17:37:41 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd024749; Wed Sep 2 17:37:31 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA00272; Wed, 2 Sep 1998 17:37:22 -0700 (MST) From: Terry Lambert Message-Id: <199809030037.RAA00272@usr07.primenet.com> Subject: Re: Thread calls To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Thu, 3 Sep 1998 00:37:22 +0000 (GMT) Cc: tlambert@primenet.com, tinguely@plains.NoDak.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Daniel O'Connor" at Sep 2, 98 04:36:17 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, why was the PTHREAD_MUTEX_INITIALIZER thing implemented if it broke the > ability to easily check between standards? ie is there a good reason to not > back that change out until a more comprehensive set of patches comes along? The pat answer? "-current is not -stable". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 17:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09720 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 17:44:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09710 for ; Wed, 2 Sep 1998 17:44:28 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA10675; Wed, 2 Sep 1998 17:43:22 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd010660; Wed Sep 2 17:43:18 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA00700; Wed, 2 Sep 1998 17:43:12 -0700 (MST) From: Terry Lambert Message-Id: <199809030043.RAA00700@usr07.primenet.com> Subject: Re: Thread calls To: jb@cimlogic.com.au (John Birrell) Date: Thu, 3 Sep 1998 00:43:12 +0000 (GMT) Cc: doconnor@gsoft.com.au, jb@cimlogic.com.au, freebsd-hackers@FreeBSD.ORG, tinguely@plains.NoDak.edu, tlambert@primenet.com In-Reply-To: <199809020832.SAA28105@cimlogic.com.au> from "John Birrell" at Sep 2, 98 06:32:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It sounds like it has turned into a defacto standard for determining > > the thread version on the system though :( > > It's a Terry standard. Doh! So long as all of the differences or none of the differences between Draft 4 and Draft 10 are addressed, atomically, I would agree. What's the status of the "attr" argument to pthread_create in -current? Is it Draft 4, or is it Standard? Etc.? I think if something is documented as existing in Standard, but not in Draft 4, then it can be used as a test to determine which one prevails on a given platform. Using this test, along with the select and several other changes, resulted in my patches making LDAP run on 7 platforms where before it limped in an infinite CPU buzz-loop. IRIX, for example, shipped with a Draft 4 compliant implementation, and works via this test. So it's not just me... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 17:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10337 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 17:49:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10332 for ; Wed, 2 Sep 1998 17:49:28 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA13404; Wed, 2 Sep 1998 17:48:25 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd013379; Wed Sep 2 17:48:19 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA01032; Wed, 2 Sep 1998 17:48:16 -0700 (MST) From: Terry Lambert Message-Id: <199809030048.RAA01032@usr07.primenet.com> Subject: Re: bcmp abuse in networking code ? To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 3 Sep 1998 00:48:16 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809021506.RAA10910@labinfo.iet.unipi.it> from "Luigi Rizzo" at Sep 2, 98 05:06:30 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > poking around in /sys/net and /sys/netinet, i frequently see bcmp() being > used to compare ethernet addresses (but not only those). In some cases, > even against the ethernet broadcast address. > > In my revised bridge code i have the following macros > > #define ETH_MATCH(a,b) ( \ > ((unsigned short *)(a))[2] == ((unsigned short *)(b))[2] && \ > *((unsigned int *)(a)) == *((unsigned int *)(b)) ) > #define IS_ETHER_BROADCAST(a) ( \ > *((unsigned int *)(a)) == 0xffffffff && \ > ((unsigned short *)(a))[2] == 0xffff ) > > which seem to do a decent job in terms of performance. On a Pentium90, > they save about 40-50 ticks per call, which is not bad considering how > frequently they are used on a bridge or on a multicast router. As you noted, alignment is one issue. Another issue is the use of arbitrary length addresses in the ARP code. See www.daemonnews.org, in the "under the hood" column, where they talk about implementing precisely this for FDDI and AX.25 support in the NetBSD kernel. Assumptions about the entry length are bad (IMO), in that they break future compatability. Consider the IPv6 code from WIDE and INRIA, and make sure this change does not damage the ability to use IPv6 on FreeBSD (for one concrete case of current, working code, for all you X.25-haters...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 17:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10885 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 17:54:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10880 for ; Wed, 2 Sep 1998 17:54:40 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA03916; Wed, 2 Sep 1998 17:53:37 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma003914; Wed Sep 2 17:53:33 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA20948; Wed, 2 Sep 1998 17:53:33 -0700 (PDT) From: Archie Cobbs Message-Id: <199809030053.RAA20948@bubba.whistle.com> Subject: Re: bcmp abuse in networking code ? In-Reply-To: <199809021506.RAA10910@labinfo.iet.unipi.it> from Luigi Rizzo at "Sep 2, 98 05:06:30 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 2 Sep 1998 17:53:33 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo writes: > poking around in /sys/net and /sys/netinet, i frequently see bcmp() being > used to compare ethernet addresses (but not only those). In some cases, > even against the ethernet broadcast address. > > In my revised bridge code i have the following macros > > #define ETH_MATCH(a,b) ( \ > ((unsigned short *)(a))[2] == ((unsigned short *)(b))[2] && \ > *((unsigned int *)(a)) == *((unsigned int *)(b)) ) > #define IS_ETHER_BROADCAST(a) ( \ > *((unsigned int *)(a)) == 0xffffffff && \ > ((unsigned short *)(a))[2] == 0xffff ) Cool...! A minor nit, though: use u_int16_t and u_int32_t instead. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12343 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:09:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12338 for ; Wed, 2 Sep 1998 18:09:29 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA19298; Wed, 2 Sep 1998 18:08:27 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd019259; Wed Sep 2 18:08:18 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA02367; Wed, 2 Sep 1998 18:08:16 -0700 (MST) From: Terry Lambert Message-Id: <199809030108.SAA02367@usr07.primenet.com> Subject: Re: Reading/writing /usr/ports is VERY slow To: cmascott@world.std.com (Carl Mascott) Date: Thu, 3 Sep 1998 01:08:15 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809022252.SAA00868@europa.local> from "Carl Mascott" at Sep 2, 98 06:52:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This test actually understates the performance advantage of > having the entire tree in one cylinder group because /var > is on a slower disk than is /usr. Note that this performance advantage is rather ethereal, and depends on a number of factor in the existing code which I personally do not care for, starting with the way the directory name cache precache works for a partial traversal of a directory, and the fact that the inodes referenced into the cache are not faulted-ahead so that they will be there when they are looked up. This gives the cache the false impression that it will get an ihash hit if it gets a dcache hit. In addition, there are some pessimizations in the cache code which damage coherency (but were made to work around bugs in the way the code is used). Finally, given the precache policy, on directories like the ones where you will see the performance issues you are reporting, the precache will result in hash bucket collisions that would not have occurred otherwise. In other words, the ports tree is a worst-case for the code. > I don't have a feeling for the effect of metadata updates > or the efficacy of the softupdates modifications where > write throughput is concerned. I see write throughput > of 9 KB/s in /usr/ports. Perhaps the softupdates mods > would help to get the write throughput closer to the > read throughput (i.e., improve it from abysmal to poor). This is unlikely to help. One thing to consider here is that you will most likely engage in partial track read-caching in the controller, and perhaps on the disk itself. Specifically, most modern disks record tracks in reverse sector order, and as soon as you seek to the track, they start reading (and buffering data) until they hit the sector in the track that you were actually seeking to find. > Where to go from here? A tree like /usr/ports is really > atypical (2.6 small files per directory). One wouldn't > want to speed up FFS on /usr/ports if the result was to > slow it down on more typical file I/O. That said, I still > have to wonder if FFS's directory placement policy can't > be improved upon. One definitely doesn't want to let a > cylinder group fill up while there is still plenty of > space in the filesystem. But it might be possible to > accomplish this without spreading new directories all > over the filesystem. In fact, directory locality is loosely assureed. I suspect that you are using a disk that either does not support tagged command queues, or supports them, but they are not enabled. Most E/IDE controllers support them (as does FreeBSD's driver), but most E/IDE devices themselves, lamentably, do not. What you may seeing is the limit of the drive to engage in elevator sorting of requests. FreeBSD used to support this, but it was diked out on the (valid) assumption that modern disk hardware would do a better job, and that implementing the code in the face of the cache unification would be prohibatively expensive. > By the way, another thing that suffers from FFS's > directory placement policy is the find command, and not > just when it is run in /usr/ports. Try running it in > /usr/src if you have a moderate amount of source > installed and just listen to your disk drive. > > I'm really curious about the directory placement policy in > vxfs (Veritas), which also has cylinder groups (called > allocation units). Does anybody happen to know what it is? The VXFS directory hierarchy management code is derived from USL's UFS (BSD FFS) implementation. There are, in fact, USL copyrights all over the source code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12963 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:13:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12958 for ; Wed, 2 Sep 1998 18:13:37 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA21641; Wed, 2 Sep 1998 18:12:35 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd021620; Wed Sep 2 18:12:28 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA02792; Wed, 2 Sep 1998 18:12:26 -0700 (MST) From: Terry Lambert Message-Id: <199809030112.SAA02792@usr07.primenet.com> Subject: Re: Reading/writing /usr/ports is VERY slow To: cmascott@world.std.com (Carl Mascott) Date: Thu, 3 Sep 1998 01:12:26 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809022252.SAA00872@europa.local> from "Carl Mascott" at Sep 2, 98 06:52:59 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, > if a cg proximity criterion were added to the new-cg-chooser, > then the size of a cg would become a factor, although I don't > know how important a factor. Very important. It would result in FFS finally adding "support" for fragmenting the bejesus out of a disk drive. This would be a *very* bad thing. > Hopefully someone who knows the history of FFS development > will chime in at this point. It would be nice to know if > any other directory placement policies were ever tried and > rejected. The original "free reserve" values were set to 10% for a reason; it was a compromise between people who wanted to use every byte, and the actual 15% value required for a "perfect hash". In effect, when the FS picks a block (or, more correctly, a cluster), it is hashing the filespace onto the disk. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13693 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:16:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13688 for ; Wed, 2 Sep 1998 18:16:51 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA08901; Wed, 2 Sep 1998 18:15:48 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd008873; Wed Sep 2 18:15:42 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA03007; Wed, 2 Sep 1998 18:15:39 -0700 (MST) From: Terry Lambert Message-Id: <199809030115.SAA03007@usr07.primenet.com> Subject: Re: bcmp abuse in networking code ? To: archie@whistle.com (Archie Cobbs) Date: Thu, 3 Sep 1998 01:15:39 +0000 (GMT) Cc: luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-Reply-To: <199809030053.RAA20948@bubba.whistle.com> from "Archie Cobbs" at Sep 2, 98 05:53:33 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In my revised bridge code i have the following macros > > > > #define ETH_MATCH(a,b) ( \ > > ((unsigned short *)(a))[2] == ((unsigned short *)(b))[2] && \ > > *((unsigned int *)(a)) == *((unsigned int *)(b)) ) > > #define IS_ETHER_BROADCAST(a) ( \ > > *((unsigned int *)(a)) == 0xffffffff && \ > > ((unsigned short *)(a))[2] == 0xffff ) > > Cool...! > > A minor nit, though: use u_int16_t and u_int32_t instead. No, not cool. See http://www.daemonnews.org/underhood.html The New Link-Level Independent ARP Subsystem of NetBSD Ignatios Souvatis The NetBSD Project Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:27:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15396 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:27:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15382 for ; Wed, 2 Sep 1998 18:27:14 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA04220; Wed, 2 Sep 1998 18:26:10 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma004218; Wed Sep 2 18:26:06 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA07413; Wed, 2 Sep 1998 18:26:05 -0700 (PDT) From: Archie Cobbs Message-Id: <199809030126.SAA07413@bubba.whistle.com> Subject: Re: default syslog priority for kernel messages In-Reply-To: <199809030036.RAA00192@usr07.primenet.com> from Terry Lambert at "Sep 3, 98 00:36:14 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 2 Sep 1998 18:26:05 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > > The only problem is that it's possible to printf from the kernel > > > without logging, and it may frequently be desirable to send a message > > > to the console without logging it. > > > > So then kill syslogd. > > > > Here is the comment in the code: > > > > /* > > * Log writes to the log buffer, and guarantees not to sleep (so can be > > * called by interrupt routines). If there is no process reading the > > * log yet, it writes to the console also. > > */ > > The printf calls are special-use calls. They are not merely the "printf" > that you think should be "log". The "printf" is merely a wrapper for > "kvprintf". > > Instead of putting "log" in those places, if you got rid of "printf", > the correct thing to do would be to call "kvprintf" (not "log"). It depends on what the code writer wanted. I'd say in 99% of the cases, they want to spit out a normal kernel logging message and have it go to syslogd. That's exactly what log() does. The only time I can imagine when you would want kprintf() is if you're doing some debugging with tons & tons of output, or something like that. So in the common case, the right thing to do is replace printf with log. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:51:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19265 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:51:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19245 for ; Wed, 2 Sep 1998 18:51:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01527; Wed, 2 Sep 1998 18:48:21 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809021848.SAA01527@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: cmascott@world.std.com (Carl Mascott), hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow In-reply-to: Your message of "Thu, 03 Sep 1998 01:12:26 GMT." <199809030112.SAA02792@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 18:48:21 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > However, > > if a cg proximity criterion were added to the new-cg-chooser, > > then the size of a cg would become a factor, although I don't > > know how important a factor. > > Very important. It would result in FFS finally adding "support" > for fragmenting the bejesus out of a disk drive. > > This would be a *very* bad thing. Could you explain how the proposed change would do this? It's no worse than the current case if there is one cg with substantially fewer directories than any other. In fact, you could simplify the code somewhat just by lying about the number of directories in the cg referenced by the rotor. > > Hopefully someone who knows the history of FFS development > > will chime in at this point. It would be nice to know if > > any other directory placement policies were ever tried and > > rejected. > > The original "free reserve" values were set to 10% for a reason; it > was a compromise between people who wanted to use every byte, and > the actual 15% value required for a "perfect hash". The change I proposed honours the reserve. Now I *know* you didn't look at it. 8) > In effect, when the FS picks a block (or, more correctly, a cluster), > it is hashing the filespace onto the disk. Unfortunately, in the case of directories this results in them being scattered all over the disk. If you're creating a pile of them all at once in a hierarchy, the net result is very poor locality of reference. Associating locality and time of creation is not a wonderful algorithm, I freely admit. However, I think that it has some merit over the current approach (forcibly minimise locality under some circumstances). If you have the stuff set up to test, I'd really be interested to see if the clustering I proposed demonstrated any effects. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20249 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:56:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20239 for ; Wed, 2 Sep 1998 18:56:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01561; Wed, 2 Sep 1998 18:53:31 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809021853.SAA01561@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: cmascott@world.std.com (Carl Mascott), hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow In-reply-to: Your message of "Thu, 03 Sep 1998 01:08:15 GMT." <199809030108.SAA02367@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 18:53:31 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One thing to consider here is that you will most likely engage > in partial track read-caching in the controller, and perhaps > on the disk itself. > > Specifically, most modern disks record tracks in reverse sector > order, and as soon as you seek to the track, they start reading > (and buffering data) until they hit the sector in the track that > you were actually seeking to find. This is only useful if the layout has clustered related directories on the disk. The current code does a good job of keeping them a long way apart. > In fact, directory locality is loosely assureed. Almost the opposite is true, especially if you don't make a common practice of deleting lots of directories. > I suspect that you are using a disk that either does not support > tagged command queues, or supports them, but they are not enabled. Multiple device openings are unuseful in this case, as you previously noted the lookup code doesn't (can't) attempt to read-ahead (it can't know where /a/b is until it has read /a, etc.) If you are performing a set of directory recursions, I/O (modulo the cache) will be performed strictly sequentially. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 18:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20905 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:59:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20900 for ; Wed, 2 Sep 1998 18:59:40 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id UAA16855 for hackers@freebsd.org; Wed, 2 Sep 1998 20:58:38 -0500 (CDT) From: Kevin Day Message-Id: <199809030158.UAA16855@home.dragondata.com> Subject: Memory Mapped IO To: hackers@FreeBSD.ORG Date: Wed, 2 Sep 1998 20:58:37 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Suppose from userland I want to access a chunk of physical ram directly..... I have a device that maps some ram at 0x40000000 through 0x40010000. I know I can talk to it directly through /dev/mem, but is there an easier way? (i.e. I'd like to be able to directly access that piece of ram, somehow) Can this be done? If so, what am I missing? (as a side note, would mmap'ing the appropriate section of /dev/mem even work?) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 19:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21408 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 19:02:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21403 for ; Wed, 2 Sep 1998 19:02:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01595; Wed, 2 Sep 1998 18:59:23 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809021859.SAA01595@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG cc: mckusick@mckusick.com Subject: Re: Reading/writing /usr/ports is VERY slow In-reply-to: Your message of "Wed, 02 Sep 1998 18:52:59 -0400." <199809022252.SAA00872@europa.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 18:59:23 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Carl Mascott wrote: > > > In short, I think that there are more long inter-group seeks on FFS > > > than there need be, due to the directory placement policy. I consider > > > it undesirable to spread directories out as much as possible all over > > > the filesystem. > > > Mike Smith wrote: > > One of the substantial contributors to this problem has been the > > FreeBSD policy of limiting the number of cg's by faking the disk > > layout. The intention here was to reduce the amount of space wasted in > > administrative overhead, as well as increase the likelihood of > > contiguous allocation. Unfortunately one of the less wonderful > > consequences has been the substantial increase in inter-cg distances. > > For a filesystem of any given size the number of cg's is not a > factor, at least not as long as there are more than a couple of > them. The number of cg, or more to the point their layout *is* somewhat significant, simply because they can still consume moderately substantial amounts of space. They also seem to be less efficient if you have zillions of them. > As long as new directories get distributed pseudo-randomly > over the filesystem, which is what happens in /usr/ports, it > doesn't matter how many cg's the filesystem is subdivided into. > The disk arm will still be covering the same distance. Effectively, yes, particularly if the creation order and traversal order were related. > However, > if a cg proximity criterion were added to the new-cg-chooser, > then the size of a cg would become a factor, although I don't > know how important a factor. For what it's worth, vxfs also > uses 32 MB cg's ("allocation units" in vxfs-speak). I don't actually think that the cg size would be an issue; what we're talking about here is allocating the directory inode, and the data blocks for the directory will follow. In most cases, the data for these directories will move around as they're extended anyway, as they accumulate frags and move into whole blocks. > Hopefully someone who knows the history of FFS development > will chime in at this point. It would be nice to know if > any other directory placement policies were ever tried and > rejected. It seems that Kirk is on holidays; at any rate, I've copied him back on this and hopefully he'll have something enlightening to offer. Meanwhile, do you have the courage to try the code snippet I included? I'd be interested to know if it had any affect on your pathalogical case... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 19:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26845 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 19:36:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26839 for ; Wed, 2 Sep 1998 19:36:51 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA05813; Wed, 2 Sep 1998 19:35:46 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd005741; Wed Sep 2 19:35:36 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id TAA07404; Wed, 2 Sep 1998 19:35:32 -0700 (MST) From: Terry Lambert Message-Id: <199809030235.TAA07404@usr07.primenet.com> Subject: Re: Reading/writing /usr/ports is VERY slow To: mike@smith.net.au (Mike Smith) Date: Thu, 3 Sep 1998 02:35:32 +0000 (GMT) Cc: tlambert@primenet.com, cmascott@world.std.com, hackers@FreeBSD.ORG In-Reply-To: <199809021853.SAA01561@dingo.cdrom.com> from "Mike Smith" at Sep 2, 98 06:53:31 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is only useful if the layout has clustered related directories on > the disk. The current code does a good job of keeping them a long way > apart. > > > In fact, directory locality is loosely assureed. > > Almost the opposite is true, especially if you don't make a common > practice of deleting lots of directories. I think we are miscommunicating here. Directory *contents* are loosely assured locality. Directory *heirarchies* are loosely assured near-perfect random non-locality. Per the "find" command argument, this issue is "breadth-first" vs. "depth-first". > > I suspect that you are using a disk that either does not support > > tagged command queues, or supports them, but they are not enabled. > > Multiple device openings are unuseful in this case, as you previously > noted the lookup code doesn't (can't) attempt to read-ahead (it can't > know where /a/b is until it has read /a, etc.) If you are performing a > set of directory recursions, I/O (modulo the cache) will be performed > strictly sequentially. OK. Yes, this breaks down quickly. Either reimplement the directory code as a btree, or, better, "avoid writing code that results in diretory recursions". I think the ports problem in this respect is that the directory entry cache is too small for the traversal being done. Basically, "some idiot is using the FS directory hierarchy as if it were a database index". 8-). The correct thing to do here would probably be to create a "fast find" index, and have find use this (SunOS 4.1 has this; you create the index at 3 am from cron -- 3am because that's when you break to go to Naugles for egg-and-bean burritos 8-)). Alternately, a "portfinder" port would help... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 19:48:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28325 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 19:48:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28309 for ; Wed, 2 Sep 1998 19:48:21 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA23436; Wed, 2 Sep 1998 19:47:16 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd023328; Wed Sep 2 19:47:07 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id TAA08033; Wed, 2 Sep 1998 19:47:02 -0700 (MST) From: Terry Lambert Message-Id: <199809030247.TAA08033@usr07.primenet.com> Subject: Re: Reading/writing /usr/ports is VERY slow To: mike@smith.net.au (Mike Smith) Date: Thu, 3 Sep 1998 02:47:02 +0000 (GMT) Cc: tlambert@primenet.com, cmascott@world.std.com, hackers@FreeBSD.ORG In-Reply-To: <199809021848.SAA01527@dingo.cdrom.com> from "Mike Smith" at Sep 2, 98 06:48:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could you explain how the proposed change would do this? It's no worse > than the current case if there is one cg with substantially fewer > directories than any other. In fact, you could simplify the code > somewhat just by lying about the number of directories in the cg > referenced by the rotor. [ ... ] > > The original "free reserve" values were set to 10% for a reason; it > > was a compromise between people who wanted to use every byte, and > > the actual 15% value required for a "perfect hash". > > The change I proposed honours the reserve. Now I *know* you didn't > look at it. 8) You aren't proposing to damage the free reserve, you are proposing to damage the distribution of the block allocation hash. A disk becomes "fragmented" when you have hash collisions in the block allocation hash. > > In effect, when the FS picks a block (or, more correctly, a cluster), > > it is hashing the filespace onto the disk. > > Unfortunately, in the case of directories this results in them being > scattered all over the disk. If you're creating a pile of them all at > once in a hierarchy, the net result is very poor locality of reference. Yes. Agreed. But the locality is *intentionally* horizontal, by design. > Associating locality and time of creation is not a wonderful algorithm, > I freely admit. However, I think that it has some merit over the > current approach (forcibly minimise locality under some circumstances). I think changing the ports to populate directory hierarchies breadth-first would result in better performance for this particular use. The problem with preturbing the hash is that you will pessimize the case where you are creating files in a single directory over time. In the general case, you tend to use all files in a given directory at a time, regardless of their creation date. Maybe we should note the way that directories do block I/O is not the same as the way files do block I/O. According to the comments, this behaviour is an intentional "play it safe" move on the part of the author. > If you have the stuff set up to test, I'd really be interested to see > if the clustering I proposed demonstrated any effects. I don't have the equipment at this point to be able to do a reasonable job of testing. Certainly nothing I'd hang the outcome of an "is this a good idea?" question... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 20:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03636 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 20:24:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03631 for ; Wed, 2 Sep 1998 20:24:50 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id UAA26884 for ; Wed, 2 Sep 1998 20:24:44 -0700 (PDT) Received: from detlev.UUCP (tex-141.camalott.com [208.229.74.141]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA07526; Wed, 2 Sep 1998 22:25:24 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA10488; Wed, 2 Sep 1998 22:23:29 -0500 (CDT) (envelope-from joelh) Date: Wed, 2 Sep 1998 22:23:29 -0500 (CDT) Message-Id: <199809030323.WAA10488@detlev.UUCP> To: jsalas@citi.com.mx CC: freebsd-hackers@freefall.cdrom.com In-reply-to: <35EE5A50.97C8C5FF@citi.com.mx> (jsalas@citi.com.mx) Subject: Re: why the crontab doesnt works... From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <35EE5A50.97C8C5FF@citi.com.mx> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > can you help me, i have a freebsd system and the crontab is not > working properly, the daemon is working, but it doesnt make > anything...can you send me examples or the steps to make it work? I would suggest posting to freebsd-questions with a copy of your crontab and the steps you took to install it. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 20:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04881 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 20:34:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04876 for ; Wed, 2 Sep 1998 20:34:38 -0700 (PDT) (envelope-from stuart@junior.apk.net) Received: from smok.apk.net (root@mail.apk.net [207.54.158.15]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id UAA27152 for ; Wed, 2 Sep 1998 20:34:32 -0700 (PDT) Received: from junior.apk.net (stuart@junior.apk.net [207.54.158.20]) by smok.apk.net (8.9.1/8.9.1/ts-apk-rel.980722) with ESMTP id XAA16129; Wed, 2 Sep 1998 23:20:53 -0400 (EDT) Received: from localhost by junior.apk.net (8.9.1/8.9.1) with SMTP id XAA20072; Wed, 2 Sep 1998 23:20:49 -0400 (EDT) Date: Wed, 2 Sep 1998 23:20:49 -0400 (EDT) From: Stuart Krivis To: rvb@sicily.odyssey.cs.cmu.edu cc: Christoph Kukulies , freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.7 install overwrites bootsect In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31 Aug 1998 rvb@sicily.odyssey.cs.cmu.edu wrote: > Christoph Kukulies writes: > > > I gave a 2.2.7 dist kit to a (sceptic?) colleague. I was hoping > > him coming back as a missionaire. Grrm, he told me, FreeBSD install > > had overwritten his bootsector (NT) although he explicitly clicked > > the option that was promising to leave the bootsector intact. > > I tend to make this mistake too. You move to the line to say leave > the bootsectors alone. But you must then type space to move the I still have a FreeBSD Booteasy boot sector on my NT disk. It just boots NT these days since I installed a new disk for FreeBSD. I have no problems with NT not booting; it doesn't even know booteasy is there. -- Stuart Krivis stuart@krivis.com Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 21:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13721 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 21:49:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA13713 for ; Wed, 2 Sep 1998 21:49:48 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA11546; Thu, 3 Sep 1998 04:54:07 +0200 From: Luigi Rizzo Message-Id: <199809030254.EAA11546@labinfo.iet.unipi.it> Subject: Re: bcmp abuse in networking code ? To: tlambert@primenet.com (Terry Lambert) Date: Thu, 3 Sep 1998 04:54:07 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809030048.RAA01032@usr07.primenet.com> from "Terry Lambert" at Sep 3, 98 00:47:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In my revised bridge code i have the following macros > > #define ETH_MATCH(a,b) ( \ ... > > #define IS_ETHER_BROADCAST(a) ( \ ... > As you noted, alignment is one issue. > > Another issue is the use of arbitrary length addresses in the ARP code. > > See www.daemonnews.org, in the "under the hood" column, where they > talk about implementing precisely this for FDDI and AX.25 support Alignment apart, this time it seems to me that you are mentioning a few not relevant things. The macros above have a clear ETH in the name, they are not meant for some generic link layer of the future which i cannot foresee (and for ARCNET and AX25... can we talk about them when we have support for them ?) If i am not mistaken FDDI has 6-byte addresses so it is not an issue. And i don't understand how ipv6 code could change the ethernet MAC addresses... > in the NetBSD kernel. > > Assumptions about the entry length are bad (IMO), in that they break > future compatability. ok, right now the code uses something like !bcmp(a, b, ETHER_ADDR_LEN) in place of the above macros. i guess they fall into the same category... cheers luigi > > Consider the IPv6 code from WIDE and INRIA, and make sure this change > does not damage the ability to use IPv6 on FreeBSD (for one concrete > case of current, working code, for all you X.25-haters...). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 22:48:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19957 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 22:48:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from csmd2.cs.uni-magdeburg.de (prinz-atm.CS.Uni-Magdeburg.De [141.44.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19946 for ; Wed, 2 Sep 1998 22:48:26 -0700 (PDT) (envelope-from jesse@prinz-atm.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.8.8/8.8.8) with SMTP id HAA00024 for ; Thu, 3 Sep 1998 07:47:21 +0200 (MET DST) Received: by knecht.cs.uni-magdeburg.de (SMI-8.6/SMI-SVR4) id HAA26846; Thu, 3 Sep 1998 07:47:20 +0200 Message-ID: <19980903074720.B26829@cs.uni-magdeburg.de> Date: Thu, 3 Sep 1998 07:47:20 +0200 From: Roland Jesse To: freebsd-hackers@FreeBSD.ORG Subject: gcc fails to compile jesred-1.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I posted the question to the questions list but to no avail. When trying to compile http://ivs.cs.uni-magdeburg.de/~elkner/webtools/src/jesred-1.2.tar.gz, gcc fails with the following messages: j.wh4-422 ~/jesred-1.2 % make cc -O3 -s -I. -c ip_list.c In file included from ip_list.c:99: /usr/include/netinet/in.h:212: parse error before `u_long' /usr/include/netinet/in.h:212: warning: no semicolon at end of struct or union /usr/include/netinet/in.h:263: parse error before `u_char' /usr/include/netinet/in.h:263: warning: no semicolon at end of struct or union [...] Honestly - I do not know why the compiler fails here. The source code seems to be ok and the include does, too. I would very much appreciate it if somebody else could try to build this small package and would provide a hint or two of what I am missing here. BTW: The machine is running FreeBSD 2.2.7-STABLE and therefore a gcc 2..7.2.1. Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 23:39:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29029 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 23:39:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles138.castles.com [208.214.165.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29022 for ; Wed, 2 Sep 1998 23:39:01 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA00706; Wed, 2 Sep 1998 23:35:08 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809022335.XAA00706@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), cmascott@world.std.com, hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow In-reply-to: Your message of "Thu, 03 Sep 1998 02:35:32 GMT." <199809030235.TAA07404@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 23:35:07 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is only useful if the layout has clustered related directories on > > the disk. The current code does a good job of keeping them a long way > > apart. > > > > > In fact, directory locality is loosely assureed. > > > > Almost the opposite is true, especially if you don't make a common > > practice of deleting lots of directories. > > I think we are miscommunicating here. > > Directory *contents* are loosely assured locality. > > Directory *heirarchies* are loosely assured near-perfect random > non-locality. I seem to recall that's what I said last time. > Per the "find" command argument, this issue is "breadth-first" vs. > "depth-first". You need three dimensions; breadth is distance across siblings, depth is distance from parent through children, and width is individual directory size. Directories are associated width-first, not breadth-first or depth-first. Both breadth and depth are pessimised. > Either reimplement the directory code as a btree, or, better, "avoid > writing code that results in diretory recursions". The first has the effect of clustering directory data. Funnily enough, that's what I was attempting to achieve. > I think the ports problem in this respect is that the directory > entry cache is too small for the traversal being done. No, the ports problem is that all directories in the hierarchy will be visited, and you have to seek a long way from any one entry to almost any other entry. > Basically, "some idiot is using the FS directory hierarchy as if it > were a database index". 8-). Feel free to suggest an alternative. Code complete, of course. > The correct thing to do here would probably be to create a "fast find" > index, and have find use this (SunOS 4.1 has this; you create the > index at 3 am from cron -- 3am because that's when you break to go > to Naugles for egg-and-bean burritos 8-)). > > Alternately, a "portfinder" port would help... You're still only reading what you want to see. This sort of search is already trivialised; we keep an index (ports/INDEX), and have both a commandline ('make search key=') and graphical (sysutils/pib) search tool. With the ports collection, the issue is creation and backups. The same problem hits other applications though (anything involving the CVS repository, for example). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 23:41:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29513 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 23:41:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29506 for ; Wed, 2 Sep 1998 23:41:27 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id XAA01274 for ; Wed, 2 Sep 1998 23:41:14 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id IAA18348; Thu, 3 Sep 1998 08:39:01 +0200 (MEST) (envelope-from kuku) Message-ID: <19980903083900.A18254@gil.physik.rwth-aachen.de> Date: Thu, 3 Sep 1998 08:39:00 +0200 From: Christoph Kukulies To: Stuart Krivis , rvb@sicily.odyssey.cs.cmu.edu Cc: Christoph Kukulies , freebsd-hackers@freefall.cdrom.com Subject: Re: 2.2.7 install overwrites bootsect References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: ; from Stuart Krivis on Wed, Sep 02, 1998 at 11:20:49PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 02, 1998 at 11:20:49PM -0400, Stuart Krivis wrote: > On 31 Aug 1998 rvb@sicily.odyssey.cs.cmu.edu wrote: > > > Christoph Kukulies writes: > > > > > I gave a 2.2.7 dist kit to a (sceptic?) colleague. I was hoping > > > him coming back as a missionaire. Grrm, he told me, FreeBSD install > > > had overwritten his bootsector (NT) although he explicitly clicked > > > the option that was promising to leave the bootsector intact. > > > > I tend to make this mistake too. You move to the line to say leave > > the bootsectors alone. But you must then type space to move the > > I still have a FreeBSD Booteasy boot sector on my NT disk. It just boots > NT these days since I installed a new disk for FreeBSD. I have no problems > with NT not booting; it doesn't even know booteasy is there. I tend to install FreeBSD into the NT bootloader these days. It is some kind of defensive measure against all kinds of woes that can be caused by installing Win95,NT etc. later. [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation, Version 4.0" multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation, Version 4.0 [ VGA-Modus]" /basevideo /sos C:\="MS-DOS" c:\tools\bat\bootsect.bsd="FreeBSD" With bootsect.bsd being /usr/mdec/boot1 > > > > -- > > Stuart Krivis stuart@krivis.com > > > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 2 23:58:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01453 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 23:58:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles138.castles.com [208.214.165.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01448 for ; Wed, 2 Sep 1998 23:58:08 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA00818; Wed, 2 Sep 1998 23:54:31 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809022354.XAA00818@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow In-reply-to: Your message of "Thu, 03 Sep 1998 02:47:02 GMT." <199809030247.TAA08033@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Sep 1998 23:54:30 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could you explain how the proposed change would do this? It's no worse > > than the current case if there is one cg with substantially fewer > > directories than any other. In fact, you could simplify the code > > somewhat just by lying about the number of directories in the cg > > referenced by the rotor. > > [ ... ] > > > > The original "free reserve" values were set to 10% for a reason; it > > > was a compromise between people who wanted to use every byte, and > > > the actual 15% value required for a "perfect hash". > > > > The change I proposed honours the reserve. Now I *know* you didn't > > look at it. 8) > > You aren't proposing to damage the free reserve, you are proposing to > damage the distribution of the block allocation hash. I'd say "damage" is a bit of an overstatement. If you have 16MB cg's on say a 1GB partition you have 64 of them. Split across these 64 groups you allocate your 5,000 directories, giving you about 80 directories per cg. Now, if we cluster the allocations so that you do 8 at a time, your worst case will be one cg has 8 more directories than the fewest. This is about like carefully picking 8 directories and then deleting them; it strikes me as so close to "noise" that it'd be irrelevant. > A disk becomes "fragmented" when you have hash collisions in the > block allocation hash. Calling the directory inode allocation a "hash" is a joke. It's a brute-force levelling function. It's not hashed either on creation (linear search) or on lookup (direct reference). > > > In effect, when the FS picks a block (or, more correctly, a cluster), > > > it is hashing the filespace onto the disk. > > > > Unfortunately, in the case of directories this results in them being > > scattered all over the disk. If you're creating a pile of them all at > > once in a hierarchy, the net result is very poor locality of reference. > > Yes. Agreed. But the locality is *intentionally* horizontal, by > design. That's clear from the code. The point here is that the intention may not necessarily have been quite so golden; there's certainly no indication that any attempt was made to optimise for any particular behaviour. The disabled rotor code in ffs_blkpref seems to indicate in fact that the rotating distribution (a linear hash of time) was abandoned in favour of the levelling function. All I'm suggesting is a tradeoff between the levelling function and the philosophy that's embodied in the cluster:block relationship and the policy that puts direct blocks in the same cg as the file's inode. > > Associating locality and time of creation is not a wonderful algorithm, > > I freely admit. However, I think that it has some merit over the > > current approach (forcibly minimise locality under some circumstances). > > I think changing the ports to populate directory hierarchies breadth-first > would result in better performance for this particular use. Almost certainly not; see the breadth/depth/width discussion. Moving from any directory to any other directory will almost guarantee a large disk traversal. The block/directory cache hit rate might be slightly better, but it's a finite resource. > The problem with preturbing the hash is that you will pessimize the > case where you are creating files in a single directory over time. The change I proposed does nothing of the sort; *all* it does is slightly weight the locality of reference of directory inodes (and thus associated direct blocks) towards the time of their creation. The pathalogical case for this optimisation is to create a small number of directories very rapidly, and then consume all their direct blocks. This would leave the cg in question *slightly* starved for blocks. You could then repeat the operation and cluster into the next cg. But this would *still* have the levelling effect, as when the cg is abandoned, the most-free candidate is chosen. You could think of it as simply multiplying the disk block size by the clustering factor, or shrinking the CG correspondingly. Given that our cg's are already much larger than they used to be, this is unlikely to be a problem. > In the general case, you tend to use all files in a given directory > at a time, regardless of their creation date. This is irrelevant; the existing optimisations still apply. > Maybe we should note the way that directories do block I/O is not > the same as the way files do block I/O. According to the comments, > this behaviour is an intentional "play it safe" move on the part of > the author. I don't see how this has any significance; all we're talking about is block allocation for the directory inode. > > If you have the stuff set up to test, I'd really be interested to see > > if the clustering I proposed demonstrated any effects. > > I don't have the equipment at this point to be able to do a reasonable > job of testing. Certainly nothing I'd hang the outcome of an "is this > a good idea?" question... 8-(. 8( None of the other guinea-pigs seem interested either. *sigh* -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 00:12:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03388 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 00:12:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles138.castles.com [208.214.165.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03368 for ; Thu, 3 Sep 1998 00:12:22 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id AAA00939; Thu, 3 Sep 1998 00:07:25 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809030007.AAA00939@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Roland Jesse cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gcc fails to compile jesred-1.2 In-reply-to: Your message of "Thu, 03 Sep 1998 07:47:20 +0200." <19980903074720.B26829@cs.uni-magdeburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 00:07:06 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I posted the question to the questions list but to no avail. > > When trying to compile > http://ivs.cs.uni-magdeburg.de/~elkner/webtools/src/jesred-1.2.tar.gz, gcc > fails with the following messages: > > j.wh4-422 ~/jesred-1.2 % make > cc -O3 -s -I. -c ip_list.c > In file included from ip_list.c:99: > /usr/include/netinet/in.h:212: parse error before `u_long' > /usr/include/netinet/in.h:212: warning: no semicolon at end of struct or > union > /usr/include/netinet/in.h:263: parse error before `u_char' > /usr/include/netinet/in.h:263: warning: no semicolon at end of struct or > union > [...] > > Honestly - I do not know why the compiler fails here. The source code > seems to be ok and the include does, too. The compiler's not failing - it's working properly. What it's telling you is that the code is bogus. > I would very much appreciate it if somebody else could try to build this > small package and would provide a hint or two of what I am missing here. You need and probably before you can include . You'll also want to include , because they use NULL. And take -O3 out of the Makefile, at least to start with. -O is about all that's reliable. The fact that it's supposed to build at all makes me wonder what platform it was developed on. The Makefile discourages the immediate "Linux" response, but I still need a barf bag. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 01:19:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10604 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 01:19:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from csmd2.cs.uni-magdeburg.de (prinz-atm.CS.Uni-Magdeburg.De [141.44.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10594 for ; Thu, 3 Sep 1998 01:19:39 -0700 (PDT) (envelope-from jesse@prinz-atm.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.8.8/8.8.8) with SMTP id KAA01631 for ; Thu, 3 Sep 1998 10:18:28 +0200 (MET DST) Received: by knecht.cs.uni-magdeburg.de (SMI-8.6/SMI-SVR4) id KAA27086; Thu, 3 Sep 1998 10:18:28 +0200 Message-ID: <19980903101828.A27073@cs.uni-magdeburg.de> Date: Thu, 3 Sep 1998 10:18:28 +0200 From: Roland Jesse To: freebsd-hackers@FreeBSD.ORG Subject: Re: gcc fails to compile jesred-1.2 References: <19980903074720.B26829@cs.uni-magdeburg.de> <199809030007.AAA00939@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.2i In-Reply-To: <199809030007.AAA00939@word.smith.net.au>; from Mike Smith on Thu, Sep 03, 1998 at 12:07:06AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > You need and probably before you can > include . > > You'll also want to include , because they use NULL. Well, thanks. and works fine (I did the NULL define on my own before). > And take -O3 out of the Makefile, at least to start with. -O is about > all that's reliable. I tried of course without any optimization. The author of the package strongly recommends -O5 - but that's for gcc 2.8.x. > The fact that it's supposed to build at all makes me wonder what > platform it was developed on. The Makefile discourages the immediate > "Linux" response, but I still need a barf bag. It was developed for Solaris 2.6 and successfully testet on AIX, HP-UX, and the author's private Linux machine. (I am not really sure about the HP-UX.) I will tell him what he is missing so that he can include the necessary includes. ;-) Thanks again for all your immediate responses. They are very much appreciated. Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 01:52:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14548 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 01:52:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.nobreak.com (ns.nobreak.com [210.105.79.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14527; Thu, 3 Sep 1998 01:52:27 -0700 (PDT) (envelope-from nobreak@nobreak.com) Received: from nobreak.com (nobreak.nobreak.com [210.105.79.103]) by ns.nobreak.com (8.8.7/8.8.7) with ESMTP id RAA01652; Thu, 3 Sep 1998 17:55:00 +0900 Message-ID: <35EE58A8.1A91A027@nobreak.com> Date: Thu, 03 Sep 1998 17:51:52 +0900 From: "ąč˝Âżľ (Seung-young Kim)" Reply-To: nobreak@nobreak.com Organization: Nobreak Technologies(ÁÖ) X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr Subject: Dear, FreeBSD.... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD.. (Jordan K.Hubbard & Other stuffs) Let me introduce myself. My name is 'Seung-young Kim' working for 'KR.FreeBSD.org' as a new domain manager. I'm crazy in FreeBSD and a member of 'Korea FreeBSD User Group'. We, 'Korea FreeBSD User Group' are so sorry that many Korean do not know FreeBSD because of foreign language, english and poor promotion. So we are planning to give technical support so as to increase users of FreeBSD. For this objective we made 'Korea FreeBSD User Group'. So we want to join you in spreading FreeBSD. We are now in beginning stage, there is not much activities. But we will do good job with 'Junho Choi', 'HyunSeog Ryu' , 'Sanghyun Park', me and the other wise mens.. We need your continuing attention and advice.... Best Regards. >From beautiful Korea. -- * R&D/Captain: Seung-young, Kim * Tel: +82-42-828-7887 , Fax: +82-42-828-7888 * Homepage: http://nobreak.nobreak.ne.kr __________________________________________________ Nobreak Technologies, Inc. http://www.nobreak.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 02:11:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16526 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 02:11:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16494; Thu, 3 Sep 1998 02:10:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA10517; Thu, 3 Sep 1998 02:09:36 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: nobreak@nobreak.com cc: jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr, hostmaster@kr.freebsd.org Subject: Re: Dear, FreeBSD.... In-reply-to: Your message of "Thu, 03 Sep 1998 17:51:52 +0900." <35EE58A8.1A91A027@nobreak.com> Date: Thu, 03 Sep 1998 02:09:34 -0700 Message-ID: <10513.904813774@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We, 'Korea FreeBSD User Group' are so sorry that many Korean > do not know FreeBSD because of foreign language, english and > poor promotion. That's definitely something that you yourselves are probably in the best position to address through www.kr.freebsd.org, which certainly has the potential to be every bit as much a focal point as www.jp.freebsd.org has been for the Japanese FreeBSD project (I cannot get to www.kr.freebsd.org right now, so I don't know how much this may already be the case - sorry). Simply make sure that it remains an up to date and fully "localized" for the Korean market and you're off to a very good start. > So we are planning to give technical support so as to increase > users of FreeBSD. For this objective we made 'Korea FreeBSD User > Group'. So we want to join you in spreading FreeBSD. This is again something which you probably want to work through the existing kr.freebsd.org hostmaster(s) and web admins since they've certainly been tasked with the job of providing a good rallying point for such efforts. You should also attempt to get FreeBSD mentioned in the Korean press, perhaps even getting some of your computer-oriented publications to make FreeBSD available on cover disks and such (this is also something which the Japanese FreeBSD user groups have had considerable success with, they being very worthy models to emulate in this and many other respects). Good luck, and welcome to our world-wide FreeBSD community! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 03:07:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22246 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 03:07:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22226; Thu, 3 Sep 1998 03:06:38 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id MAA20640; Thu, 3 Sep 1998 12:06:44 +0200 (MET DST) Message-ID: <19980903120643.A20537@cons.org> Date: Thu, 3 Sep 1998 12:06:43 +0200 From: BSD User Group Hamburg To: freebsd-core@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: An Open Letter To The FreeBSD Core Team Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An Open Letter To The FreeBSD Core Team --------------------------------------- Because of several events happened during the last 6 months we - the BSD Users Group Hamburg - are concerned about the continuing future success of the FreeBSD operating system. Our concerns are technical as well as organizational in nature and they are in detail: We see a linuxization of FreeBSD happen. FreeBSD development seems to become event-driven rather than driven by careful design. Rather than providing technical arguments, people try to gain influence by formal status. While we believe that a very good technical background is required for being a core team member, we feel that communicational and organizational management skills are a conditio sine qua non. While being a wise core team member is an invaluable contribution, worthful contributions can be supplied along other ways as well. Almost no substantial technical discussion takes place anymore on -hackers; some of the core team members doing architectural work in the deeper kernel areas seem not even being subscribed anymore. No other adequate place for such discussions seems to exist. We feel that the core team neither takes nor defends a clear technical position. Because of this, several people seem to run against rubber walls. Source code policy is not consistent. We are very upset about persons leaving and the circumstances which led to their leave and which accompanied it. Our point is that currently no clear direction is set (or at least not visible to anyone outside core) and that random events cause damage in all directions and trigger people to leave. We fear that the current situation will drive away as many people as possible directions exist. System organizing decisions are in any case better than to thermalize and being killed by entropy. We ask the core team to reconsider what they think the purpose of the core team is, and what the best way is to achieve it. The Founders of the BSD User Group Hamburg Stefan Bethke Martin Cracauer Lars Gerhard Kuehl Hellmuth Michaelis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 04:55:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06167 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 04:55:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA06161 for ; Thu, 3 Sep 1998 04:55:27 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA19548 (5.67b/IDA-1.5); Thu, 3 Sep 1998 13:35:40 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id MAA00970; Thu, 3 Sep 1998 12:37:54 +0200 (CEST) From: Wilko Bulte Message-Id: <199809031037.MAA00970@yedi.iaf.nl> Subject: Re: pci memory mapping In-Reply-To: <199809022156.RAA09174@skynet.ctr.columbia.edu> from Bill Paul at "Sep 2, 98 05:56:21 pm" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Thu, 3 Sep 1998 12:37:54 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bill Paul wrote... > Of all the gin joints in all the towns in all the world, Wilko Bulte had > to walk into mine and say: > > > > > For some reason the followin code in attach() fails: > > > > > > > > if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, > > > > &mp->pbase)) { > > > > printf("myx%d: couldn't map memory\n", unit); > > > > goto fail; > > > > } > > Okay, Ulf has sent me a copy of his source code so I could look at it. > > This doesn't seem quite right somehow. The constant PCI_MAP_REG_START > is #define in /sys/pci/pcireg.h: > > #define PCI_MAP_REG_START 0x10 > > On the two devices that I've fiddled with so far, namely the ThunderLAN > chip and the 3Com chip, 0x10 has always been the I/O base address, i.e. > the address used for inb/outb PIO access, and 0x14 is the memory base > address used for memory mapped access. My impression is that these two > registers are standar, so it's unlikely that their meanings would be > reversed unless the chip designer is up to no good. > > In any case, I would try to use 0x14 instead of PCI_MAP_REG_START and > see if that makes a difference. It makes a difference allright: I now get a trap12 panic ;-) No 'cannot map mem' anymore. Suppose this is a strong indication of the kernel telling me "you get that *manual* before experimenting" 8) > > Right.... manual...... I'm still trying to convince Mylex that handing me > > a copy of the DAC960 V2.xx programming manual will not wipe all life from > > Planet Earth. Sigh. Sample code from Linux and Ulf's driver are based on > > firmware V4.xx which is different in it's interface to the OS. > > Do not read sample Linux code without a barf bag nearby. This code is not bad as far as I can tell. > > > If the bit doesn't come on after you write to the command register, it > > > probably means the device doesn't actually support memory mapped access. > > > > Well, the bit comes on because the printf() is not triggered. But still I > > get the 'cannot map memory' from the code sample at the top of this mail. > > Then I'm probably right about the register that you need to supply > to pci_map_mep(). This is just idle speculation, but maybe the other > cards only support memory mapped mode, and the I/O base and mem base > registers have the same values in them. Let's hope I can get programming docs somehow. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 06:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12581 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 06:05:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12576 for ; Thu, 3 Sep 1998 06:05:25 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA11251; Thu, 3 Sep 1998 06:03:54 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: BSD User Group Hamburg cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-reply-to: Your message of "Thu, 03 Sep 1998 12:06:43 +0200." <19980903120643.A20537@cons.org> Date: Thu, 03 Sep 1998 06:03:53 -0700 Message-ID: <11246.904827833@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Because of several events happened during the last 6 months we - the I can appreciate that things can sometimes look worse than they are (or very different, at the least) from a distance, and I can only say that neither I nor anyone else in core sees the events of the last 6 months as particularly disastrous or even negative. Yes, the one "big" event was that we lost a core team member, one who's also hardly gone away in terms of communications and general offers of assistance (thank you John), but then anyone who's ever read the FreeBSD 1.1 release notes will quickly realize that personnel turnover in the core team is hardly a new thing at all. Of the original 13 member core team present in May of 1994, only 5 are still with us as core members today. We also have 16 core team members today, showing that membership numbers have remained more or less constant, a good thing when you're trying to keep a "management body" at that proper mid-point between being too large to get any useful work done and too small to get any useful work done. The core team of today is also every bit as productive, if not considerably more so, than the core team of 1993 and if we dug this project's grave every time a core team member left or was added, we'd be halfway to China by now! :-) > We see a linuxization of FreeBSD happen. FreeBSD development > seems to become event-driven rather than driven by careful > design. Then I'm afraid you're somewhat confused about how things have worked in this project from the very first day of its existence (and having been here since the very first day, I think I can speak with a certain authority on this topic :). We have never had even the slightest desire to see FreeBSD become yet another academic relic, pursuing some elusive, fuzzy goal of architectural purity in a rapidly changing marketplace that very quickly puts such projects in a large pile labeled "interesting scrap." It's a sad thing indeed, and some such projects of the past deserved a far kinder fate than they got, but that's just the way this process works. If software isn't relevant to someone, and hopefully more than just a couple of someones, its life expectancy is quite seriously truncated. This had already come very close to happening to the BSD code base at Berkeley at least once, and none of us there at the beginning of what eventually became the FreeBSD project wanted to make the same mistake twice so we sought to seek a better balance the second time around, something which preserved BSD's essential cleanliness but was also responsive to the needs of its user base and actively participated in the process of encouraging its acceptance (and increasing its very acceptability). It's one thing, you see, to produce a pile of interesting bits and say "here world, feed!" and yet another thing to try and actually become part of your user base's need-fulfillment loop, actively working on things that might not personally strike you as all that technically amazing but nonetheless greatly enhance your product's general usability for someone who's *not* like yourself. Life is full of trade-offs like that, not all of them necessarily pretty (or it wouldn't be a trade-off then, would it? :), and the key is knowing where to strike the balance. We happen to feel, and a number of people seem to agree with us, that we've struck a pretty good balance so far with the FreeBSD project and we're going to keep on going pretty much the way we have been, modulo any course-corrections that our users may administer along the way. We have ALWAYS been user-driven and I would personally rate this as one of the project's major strengths. Sure, we've made a mistake or two along the way as well, and if we were absolutely perfect in our judgment at all times then I doubt we'd be doing free software at all - we'd be making a fortune investing in the stock market. :-) In summary, you can't please everyone all the time and clearly we haven't entirely pleased some members of the Hamburg FreeBSD User's group, but I think we're pleasing the majority of our users and that's all that really counts. You can't make everyone happy, but if you can make *most* people happy then you're doing a better job than several major world religions. :) > While we believe that a very good technical background is > required for being a core team member, we feel that communicational > and organizational management skills are a conditio sine qua non. A quick word about core team members here: If someone ever invents the perfect core team member, I'll be first in line for as many as they let me take away, but in the meanwhile I have to live in the real world and the real world poses some significant constraints. Some of those constraints for a core member is that they have to be someone who: 1. Is willing to spend a significant amount of time, without pay or even thanks, working on the project on an ongoing basis and not quitting the minute somebody angers them or things get difficult. 2. Is willing to potentially do many things for FreeBSD that they probably wouldn't actually do for money, like stand in front of hundreds of strangers and give presentations or work for hours on a driver for some obscure card they don't even *like* or want, but some number of users really need support for. 3. Is technically proficient enough to understand most of what's going on most of the time and be able to comment semi-authoritatively on almost any aspect of FreeBSD when cornered in the hallway by some FreeBSD fan who's got a million questions. 4. Can be said, when all else fails, to truly have FreeBSD's best interests at heart, even when they're no longer personally involved with it. I think it's telling that the great majority of ex-core members still care deeply about FreeBSD and continue to help out from time to time. There have been very few "messy divorces", even ones which might have seemed so at the time. 5. Has a certain "je ne sais qua", but I don't know what it is. [rim shot :)] Finding someone who embodies all those qualities, especially #1, is difficult as it is without finding people who are also models of decorum and emotional stability. In fact, there's something about free software which seems to attract a lot of people who define "stable" as "didn't wake up in bed with an axe again this morning" :-) Speaking as a general rule, it's also a really bad idea to judge the project by the conduct of any one of its members. We all have our good days and bad days and, as I pointed out before, the project itself goes on, frequently under the guidance of different people as the core team turnover stats I cited earlier also prove. What's the point of getting all upset over the antics of somebody that may be no more than a footnote in the handbook in another year's time? Just so long as the project itself is being well taken care of and there is a constant supply of fresh and enthusiastic new people stepping in to take up the slack, you're probably doing as well as any free software project can. Let's not lose context here folks - this is free software and you simply don't have all the nifty artificial "enticements" of a steady salary and other factors which keep commercial software groups together. It's pure fallacy to directly compare commercial development organizations with their analogous free software groups, even those who are starting to make money as individual members, and you have to adjust your standards just a bit to compensate for the differences in operating model or forever suffer from perceptual problems about just what you should and should not expect. It's hardly a *worse* way of operating, and I'd say that the FreeBSD project is doing exceedingly well with its operational model at the moment, it's just a different one. > Almost no substantial technical discussion takes place anymore > on -hackers; some of the core team members doing architectural That's probably more a product of our success than anything else, I hate to say. The erosion of forums like this, frequently accompanied by various people pining publically for "the good old days", is a simple fact of life as the users flood in and begin dramatically affecting the signal-to-noise ratio - I've seen it in the Linux groups for some time and now I'm starting to see it here. Oh, I do what I can with my little form letters which redirect users to the right mailing lists, but it's really just an attempt to hold back the tide at this point. We're still growing, a process which is nowhere close to finished yet, and the influx of new and admittedly often lazy users who just post to the first forum they come to ("charters? what charters? Handbook? Huh?!") is only going to increase and drive more people out of the various "tech" lists. I regret this as much as anyone, of course, but short of going to a very "expensive" moderation scheme or something yet to be invented, I don't see many alternatives. We can either work on FreeBSD or we can read mail - which would most of you prefer? :-) > We ask the core team to reconsider what they think the purpose of the > core team is, and what the best way is to achieve it. Having discussed your mail and considered it as you request, I think we really have to say that we're quite pleased with how things have been going for FreeBSD these last couple of years, it certainly being time of many significant gains across a very wide front (including many developments of interest which none of us could have anticipated). All of us are also more than ready to admit that things have not gone absolutely perfectly the whole time, and in many ways we're sort of learning this as we go along (not many good books on starting your own free OS project :-), but I think things have gone very well indeed nonetheless - certainly better than most of us ever expected. In any case, since there are obviously going to be many sides to an issue like this, it probably wouldn't help the already low SNR of groups like -hackers (which was one of the complaints raised, after all) to debate this back and forth ad-infinitum. About the best you could hope for is that some number will agree that there are problems, some number will feel that things are perfectly fine, both sides will feel very strongly about their point of view and, in the process of proving this, we'll generate a lot of heat with probably little (or no) light which would be of actual use to anyone. - Jordan (speaking, by arrangement, for the freebsd core team). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 06:54:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18004 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 06:54:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17985; Thu, 3 Sep 1998 06:54:53 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.8/8.8.5) with SMTP id JAA10109; Thu, 3 Sep 1998 09:56:31 -0400 (EDT) Date: Thu, 3 Sep 1998 09:56:30 -0400 (EDT) From: Mark turpin To: FreeBSD hackers , FreeBSD Current Subject: Build -Current Problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG install -c -o bin -g bin -m 644 /lkm/misc/module/@/arpa/ftp.h /usr/share/examples/lkm/module/@/arpa/ftp.h install: /usr/share/examples/lkm/misc/@/arpa/ftp : No such file or directory *** Error code 71 This is -current as of Sept 2 10:00pm EDT It compiles for a couple of hours and then during an installworld it stops with this error.. Any clues? Thanks Mark Turpin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 07:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19511 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 07:10:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19498 for ; Thu, 3 Sep 1998 07:10:14 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id QAA20294 for ; Thu, 3 Sep 1998 16:16:26 +0200 (SAT) Received: by citadel via recvmail id 20251; Thu Sep 3 16:15:40 1998 From: Graham Wheeler Message-Id: <199809031414.QAA03611@cdsec.com> Subject: Re: An Open Letter To The FreeBSD Core Team To: freebsd-hackers@FreeBSD.ORG Date: Thu, 3 Sep 1998 16:14:28 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just my $0.02 worth: FreeBSD is open source and free to use, so anyone who wants to take it and test out their research ideas on it is free to do so - and if they pan out, they can always submit them and perhaps have them included. If there are enough people who feel that they can do a better job and who have `long term architectural vision', they can alsways take the existing code base, give it a new name, and go for it - and time will tell whether their vision is so great after all. I think the FreeBSD team are doing a brilliant job. They have provided, and continue to provide, an operating system that is highly functional, performs like greased lightning, and is more stable than any other I know of. It not only makes a great desktop platform (especially with the Linux compatability), but it is an ideal server platform on which to base complex third party products such as those manufactured by my company. Without FreeBSD, we wouldn't be in business. With FreeBSD, our company was able to start three years ago on about US$20 and a couple of PCs. As Jordan points out, a development effort as large as FreeBSDs can only run on one or both of two things - money, or sufficient enthusiastic demand from users. As FreeBSD is free, it relies on the latter, and for that to happen, it has to be useful - whether that be in academic, home, or business environments. One final point - for us living in Africa, commercial UNIXes are often prohibitively expensive for many small organisations, NGOs, academic departments, and so on. FreeBSD and Linux are real blessings to those in emerging economies. Believe me, we need FreeBSD far more than people in Hamburg do. I say `thank you' to the FreeBSD core team - your efforts are very much appreciated. gram -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 07:14:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20236 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 07:14:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from inner.cortx.com (inner.cortx.com [207.207.221.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20231 for ; Thu, 3 Sep 1998 07:14:56 -0700 (PDT) (envelope-from costa@cortx.com) Received: from cman (cman.cortx.com [207.207.221.12]) by inner.cortx.com (8.8.8/8.8.8 NO RELAY NO SPAM) with SMTP id KAA02873 for ; Thu, 3 Sep 1998 10:15:43 -0400 (EDT) From: "Costa Morris" To: Subject: FW: suexec error Date: Thu, 3 Sep 1998 10:18:15 -0400 Message-ID: <004301bdd745$b0f73c30$0cddcfcf@cman.cortx.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i installed suexec on my 2.2.7 box running apache 1.2.6. anytime i add the user/group info to a virtual host, all the cgi scripts associated with that domain don't work. i receive 500 internal server errors. here is the suexec log excerpt: [13:46:35 01-09-98]: uid: (costa/costa) gid: (staff/staff) formmail [13:46:35 01-09-98]: cannot run as forbidden gid (20/formmail) any ideas? THanks! _________________________________ CONSTANTINE J. MORRIS Cortex Communications, LLC. Managing Director costa@cortx.com Tel 201.567.2297 _________________________________ Join Our Web Partners Program!! http://www.worktheweb.com/ _________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 07:49:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24876 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 07:49:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24841; Thu, 3 Sep 1998 07:49:07 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA08704; Thu, 3 Sep 1998 16:47:51 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA06632; Thu, 3 Sep 1998 16:47:49 +0200 (MET DST) Message-ID: <19980903164748.25255@follo.net> Date: Thu, 3 Sep 1998 16:47:48 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , BSD User Group Hamburg Cc: freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team References: <19980903120643.A20537@cons.org> <11246.904827833@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <11246.904827833@time.cdrom.com>; from Jordan K. Hubbard on Thu, Sep 03, 1998 at 06:03:53AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 03, 1998 at 06:03:53AM -0700, Jordan K. Hubbard wrote: > charters? Handbook? Huh?!") is only going to increase and drive more > people out of the various "tech" lists. I regret this as much as > anyone, of course, but short of going to a very "expensive" moderation > scheme or something yet to be invented, I don't see many alternatives. > We can either work on FreeBSD or we can read mail - which would most > of you prefer? :-) Code. However, in order to have a place for discussion architecture, we need at least one non-noisy list. I hereby volunteer to moderate a freebsd-architecture list (given that the one we have now is dead, we might as well re-use the name, I guess). I'd be happy if there also was a freebsd-kernel for non-moderated discussion (to take some of the non-fitting load off -hackers and -current), but I don't put that as a requirement. I'd also be happy to have a backup-moderator (yes, I remember who volunteered before, but I won't hold you to it unless you still want to), but it isn't a requirement - it would just mean that things will go quicker in the periods where I'm not available. Eivind, who is very well aware that there are people that probably are more competent to do this, but hasn't seen any of them volunteering. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 08:35:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01768 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 08:35:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from trem.cnt.org.br (trem.cnt.org.br [200.19.123.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01750 for ; Thu, 3 Sep 1998 08:35:03 -0700 (PDT) (envelope-from ormonde@aker.com.br) Received: from creq157.cipea.ipea.gov.br (cipea.ipea.gov.br [200.130.48.11]) by trem.cnt.org.br (8.8.7/8.8.7) with SMTP id MAA16802 for ; Thu, 3 Sep 1998 12:36:36 -0300 (EST) (envelope-from ormonde@aker.com.br) Message-Id: <3.0.3.32.19980903123603.0068c6f4@cnt.org.br> X-Sender: ormonde@cnt.org.br X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Thu, 03 Sep 1998 12:36:03 -0300 To: hackers@FreeBSD.ORG From: Rodrigo Ormonde Subject: Assembler with FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I have to write a few high speed routines in assembler to run on a FreeBSD box. I used to program in assembler to DOS, so I think I have the necessary knowledge to do it on FreeBSD. The problem is that I realized that the mnemonics that gcc understands are different from the ones I'm used to. I'd like to know if there is a paper (or book, or something) that describes the gcc assembler mnemonics, or better, compares them to the ones used by TASM or MASM. Please send a copy of the answer directly to me, I'm not on the list. Thanks in advance, -- Rodrigo de La Rocque Ormonde e-mail: ormonde@aker.com.br Aker Consultoria e Informatica LTDA - http://www.aker.com.br --> Turn your PC into a workstation. Use FreeBSD <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 08:42:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02485 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 08:42:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02468 for ; Thu, 3 Sep 1998 08:42:05 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id IAA02021; Thu, 3 Sep 1998 08:40:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199809031540.IAA02021@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: BSD User Group Hamburg cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-reply-to: Your message of "Thu, 03 Sep 1998 12:06:43 +0200." <19980903120643.A20537@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 08:40:55 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps , a mediation panel or court consisting of a small odd number of members can help address some of your concerns. The primary requirement to be a panel member is mentally balance , good listening skills and technically competent. In the past , I suggested that we should have a web area to keep track of important projects to help bring focus and direction however we got nowhere mostly due to lack of time and lack of volunteers. Perhaps the Hamburg group can step forward and help in this area Best Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 08:47:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03246 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 08:47:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03239; Thu, 3 Sep 1998 08:47:43 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id LAA21704; Thu, 3 Sep 1998 11:48:29 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <199809031548.LAA21704@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: "Jordan K. Hubbard" , BSD User Group Hamburg , freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-reply-to: Your message of "Thu, 03 Sep 1998 16:47:48 +0200." <19980903164748.25255@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 11:48:29 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And here's a vote for a "freebsd-yappers" list, for non-technical crap like this thread. Signed, Grumpy Bob (...heads for the coffie machine). --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 08:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05285 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 08:58:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05270; Thu, 3 Sep 1998 08:58:22 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id IAA02087; Thu, 3 Sep 1998 08:56:41 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199809031556.IAA02087@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Withrow cc: Eivind Eklund , "Jordan K. Hubbard" , BSD User Group Hamburg , freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-reply-to: Your message of "Thu, 03 Sep 1998 11:48:29 EDT." <199809031548.LAA21704@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 08:56:41 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Careful here, this group started by being good nature and that *was* one of its strongest points . Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 09:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06683 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 09:09:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06660; Thu, 3 Sep 1998 09:08:59 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id MAA21827; Thu, 3 Sep 1998 12:09:42 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <199809031609.MAA21827@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Robert Withrow , Eivind Eklund , "Jordan K. Hubbard" , BSD User Group Hamburg , freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-reply-to: Your message of "Thu, 03 Sep 1998 08:56:41 PDT." <199809031556.IAA02087@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 12:09:42 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (I'm only replying to "hackers" because *this* was placed on hackers.) hasty@rah.star-gate.com said: :- Careful here, this group started by being good nature and that *was* :- one of its strongest points . Am I the *only* person who reads the charter for the maillists here? Here is the charter: Technical discussions This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. This is a technical mailing list for which strictly technical content is expected. As far as I can tell, "An Open Letter" like this is not even *remotely* on topic, which is intended to be "strictly technical"! --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 09:35:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09915 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 09:35:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tidal.oneway.com (tidal.oneway.com [205.177.9.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09906; Thu, 3 Sep 1998 09:35:17 -0700 (PDT) (envelope-from jay@oneway.com) Received: from localhost (jay@localhost) by tidal.oneway.com (8.8.8/8.8.3) with SMTP id MAA16732; Thu, 3 Sep 1998 12:34:15 -0400 (EDT) Date: Thu, 3 Sep 1998 12:34:15 -0400 (EDT) From: Jay To: questions@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: .nfs files, what causes them and why do they hang around? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good Afternoon, I have a fairly high-traffic NFS server running FreeBSD 2.2.6 using nfsv3 to all FreeBSD 2.2.6 clients. One of the things that I notice on it is that there are hundreds of .nfsA3d7a4.4 files hanging around. I know that these are some type of nfs temporary files, and that they are normally supposed to be removed, but I have some on there from August 17th. I have removed them without problem before, but I am curious as to what is causing them, and wondering if it is related to another problem we are having. These .nfs files often contain all the information that certain lockfiles are supposed to contain. Since the lockfiles should only exist for a second or two, I don't know if the lockfiles are actually being created or not, and that scares me a bit. Can anyone shed some light on this for me? Also, The NFS network is isolated and used only for NFS... are there any options (NFSv2, udp/tcp, etc) that would be beneficial to use? Thanks in advance, Jay K. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 09:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13176 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 09:54:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA13169 for ; Thu, 3 Sep 1998 09:54:29 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0zEcbk-0006v2-00; Thu, 3 Sep 1998 09:51:40 -0700 Date: Thu, 3 Sep 1998 09:51:40 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: Costa Morris cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FW: suexec error In-Reply-To: <004301bdd745$b0f73c30$0cddcfcf@cman.cortx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is offtopic for freebsd-hackers; please take any followups or future questions of this nature to freebsd-questions. On Thu, 3 Sep 1998, Costa Morris wrote: > > i installed suexec on my 2.2.7 box running apache 1.2.6. anytime i add the > user/group info to a virtual host, all the cgi scripts associated with that > domain don't work. i receive 500 internal server errors. > > here is the suexec log excerpt: > > [13:46:35 01-09-98]: uid: (costa/costa) gid: (staff/staff) formmail > [13:46:35 01-09-98]: cannot run as forbidden gid (20/formmail) It means exactly what it says. If you would look at the manual to see why the gid could be forbidden, you would quickly find: 10. Is the target groupid ABOVE the minimum ID number? The minimum group ID number is specified during configuration. This allows you to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. This is useful to block out "system" groups. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 09:55:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13266 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 09:55:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13259 for ; Thu, 3 Sep 1998 09:55:48 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA04130; Thu, 3 Sep 1998 18:54:26 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Thu, 3 Sep 1998 18:54:26 +0200 (MET DST) Mime-Version: 1.0 To: Rodrigo Ormonde Cc: hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD References: <3.0.3.32.19980903123603.0068c6f4@cnt.org.br> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 03 Sep 1998 18:54:25 +0200 In-Reply-To: Rodrigo Ormonde's message of "Thu, 03 Sep 1998 12:36:03 -0300" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA13262 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rodrigo Ormonde writes: > I have to write a few high speed routines in assembler to run on a > FreeBSD box. I used to program in assembler to DOS, so I think I have the > necessary knowledge to do it on FreeBSD. Why do you want to do that? FreeBSD isn't DOS. Your assembler routine is unlikely to be significantly faster than the corresponding C code compiled with 'gcc -O3'. DES -- Dag-Erling Smřrgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 09:58:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13771 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 09:58:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sockratte.schell.de ([195.20.238.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13758 for ; Thu, 3 Sep 1998 09:58:27 -0700 (PDT) (envelope-from sas@schell.de) Received: from guerilla.foo.bar (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by sockratte.schell.de (8.9.1/8.9.1) with ESMTP id SAA11489 for ; Thu, 3 Sep 1998 18:56:36 +0200 Received: from localhost (localhost.foo.bar [127.0.0.1]) by guerilla.foo.bar (8.9.1/8.9.1) with SMTP id SAA01951 for ; Thu, 3 Sep 1998 18:52:13 +0200 (CEST) Date: Thu, 3 Sep 1998 18:52:13 +0200 (CEST) From: Sascha Schumann To: freebsd-hackers@FreeBSD.ORG Subject: threads again/cancellation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It was stated more than once that FreeBSD would conform to pthreads draft 4. However, while `back'porting a program from draft 10 to 4 I had to deal with cancellation of threads. pthread.h in -current defines the D10 functions pthread_setcanceltype and pthread_setcancelstate but lacks the proper #define's for PTHREAD_CANCEL_* So, according to Appendix B of O'Reilly's pthreads book I shall use pthread_setcancel respective pthread_setasynccancel. But they are not declared (anymore?)... I will stick to pmpthreads until this issue is solved. -- Sascha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 10:04:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15044 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 10:04:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14984 for ; Thu, 3 Sep 1998 10:04:06 -0700 (PDT) (envelope-from bkelly@cloud9.net) Received: from earl-grey.cloud9.net (IDENT:LaYt++kURXcx7XiQKbrbiSQUw2iUJgkQ@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.9.1a/8.9.0/rc-19980602) with SMTP id NAA14403 for ; Thu, 3 Sep 1998 13:02:59 -0400 (EDT) Date: Thu, 3 Sep 1998 13:02:58 -0400 (EDT) From: Brian Kelly To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD & WinGate Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Win98 machine (runnign WinGate) and a FreeBSD machine (2.2.7) sitting on a LAN. Win98 = 192.168.0.1 FreeBSD = 192.168.0.2 The two can talk to each other just dandy but my FreeBSD machine cannot access the internet through my Win98 ISDN Dialup. I've tried setting my Gateway to NO (wingate's recommendation) as well as the Win98 LAN IP. Either way my FreeBSD machine can't find a route anything on the the net. .......................................................................... Brian Kelly bkelly@cloud9.net Cloud 9 Consulting, Inc. (914) 696-4000 White Plains, New York http://www.cloud9.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 10:08:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15895 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 10:08:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA15869; Thu, 3 Sep 1998 10:08:20 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id NAA20344; Thu, 3 Sep 1998 13:05:46 -0400 Date: Thu, 3 Sep 1998 13:05:45 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Jay cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: .nfs files, what causes them and why do they hang around? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The infamous .nfs files. An artifact of stateless servers: you can't do a remove over nfs, since it is impossible to ever know that a file is not used, since there is no server state that could tell you such a thing. In fact you're not really safe removing .nfsxxxx files unless they're pretty old, since again you can't know that there is not some client out there that may not have accessed it for a few days, but may still be paging code from it at some point (think: /usr/local/bin/whatever). So check in the nfs client-side code for the silly rename that redirects the unlink operations to renaming a file to .nfsxxxxx, so that it is not found the next time it is looked up. There you can see how it works. Sometimes you see funny things like people removing .nfs files from a client, which of course results in different .nfsxxxx files. You have to remove these clunkers via (typically) cron jobs on the server. Lock files would certainly create these. run NFS over tcp if you possibly can. ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 10:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17127 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 10:14:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17023 for ; Thu, 3 Sep 1998 10:14:10 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id MAA18689; Thu, 3 Sep 1998 12:09:54 -0400 (EDT) Date: Thu, 3 Sep 1998 12:09:54 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Rodrigo Ormonde cc: hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-Reply-To: <3.0.3.32.19980903123603.0068c6f4@cnt.org.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Rodrigo Ormonde wrote: > Hello. > > I have to write a few high speed routines in assembler to run on a > FreeBSD box. I used to program in assembler to DOS, so I think I have the > necessary knowledge to do it on FreeBSD. > > The problem is that I realized that the mnemonics that gcc understands > are different from the ones I'm used to. I'd like to know if there is a > paper (or book, or something) that describes the gcc assembler mnemonics, > or better, compares them to the ones used by TASM or MASM. > > Please send a copy of the answer directly to me, I'm not on the list. Use nasm in ports. The syntax is closer to what you're used to, and much nicer than gas'. On top of that, nasm actually has a very nice manual with it, it's extremely readable, and you may find (like me) that nasm's syntax is in fact superior to tasm's or masm's. You don't really want to use gas, because it was never made for human use, just as a back end for gcc, and it's reactions to errors stink. > > Thanks in advance, > > -- > Rodrigo de La Rocque Ormonde > e-mail: ormonde@aker.com.br > Aker Consultoria e Informatica LTDA - http://www.aker.com.br > > --> Turn your PC into a workstation. Use FreeBSD <-- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 10:16:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17470 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 10:16:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17455; Thu, 3 Sep 1998 10:16:23 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id MAA18701; Thu, 3 Sep 1998 12:13:00 -0400 (EDT) Date: Thu, 3 Sep 1998 12:13:00 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Robert Withrow cc: Eivind Eklund , "Jordan K. Hubbard" , BSD User Group Hamburg , freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-Reply-To: <199809031548.LAA21704@spooky.rwwa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Robert Withrow wrote: > And here's a vote for a "freebsd-yappers" list, for non-technical crap > like this thread. It already exists (FreeBSD-chat). You're quite right, tho, the post should have gone there. > > Signed, Grumpy Bob (...heads for the coffie machine). > > --------------------------------------------------------------------- > Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 10:48:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21576 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 10:48:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw2.att.com [192.128.133.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA21570 for ; Thu, 3 Sep 1998 10:48:44 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from kcig2.fw.att.com by kcgw2.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Thu Sep 3 12:26 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig2.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id MAA01420 for ; Thu, 3 Sep 1998 12:47:13 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Thu, 3 Sep 1998 13:46:52 -0400 Message-ID: To: ormonde@aker.com.br, hackers@FreeBSD.ORG Subject: RE: Assembler with FreeBSD Date: Thu, 3 Sep 1998 13:46:51 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > -----Original Message----- > From: Rodrigo Ormonde [SMTP:ormonde@aker.com.br] > > I have to write a few high speed routines in assembler to run on a > FreeBSD box. I used to program in assembler to DOS, so I think I have > the > necessary knowledge to do it on FreeBSD. > > The problem is that I realized that the mnemonics that gcc > understands > are different from the ones I'm used to. I'd like to know if there is > a > paper (or book, or something) that describes the gcc assembler > mnemonics, > or better, compares them to the ones used by TASM or MASM. > The mnemonics used by GASM are modeled after VAX/Motorola, so their most important differences from MASM are: 1. The destination operand is on the right side (the common rule is that operands are in such case in reverse order compared to MASM). This brings an issue of CMP instructions, because even on VAX they are in MASM-like order, so you can look at the existing code to understand which way is right, I can't remember it now :-) 2. The length of operands is specified explicitly, like MOVL for 4-byte operands, MOVS for 2-byte operands, MOVB for 1-byte operands instead of one common MOV with strange additions like BYTE PTR. 3. The register names always have prefix '%', just like very old Intel ASM. 4. The constants have prefix '$', the numbers without that prefix are addresses. 5. Notation for hexadecimal and octal numbers is just like C. There are also some other minor differences. -Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 11:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25571 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 11:27:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25562; Thu, 3 Sep 1998 11:27:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00428; Thu, 3 Sep 1998 11:24:03 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809031124.LAA00428@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jay cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: .nfs files, what causes them and why do they hang around? In-reply-to: Your message of "Thu, 03 Sep 1998 12:34:15 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 11:24:03 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Good Afternoon, > > I have a fairly high-traffic NFS server running FreeBSD 2.2.6 > using nfsv3 to all FreeBSD 2.2.6 clients. One of the things that I notice > on it is that there are hundreds of .nfsA3d7a4.4 files hanging around. I > know that these are some type of nfs temporary files, and that they are > normally supposed to be removed, but I have some on there from August > 17th. I have removed them without problem before, but I am curious as to > what is causing them, and wondering if it is related to another problem we > are having. They're files that have been unlinked but not closed on the client; because NFS is stateless they can't be unlinked on the server (there's no indication that the client has the file open, because there's no state...). You'll normally get these if the client goes down unexpectedly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 11:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26182 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 11:31:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26153; Thu, 3 Sep 1998 11:31:00 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id OAA16402; Thu, 3 Sep 1998 14:39:33 -0400 (EDT) Date: Thu, 3 Sep 1998 14:39:33 -0400 (EDT) From: Charles Youse To: Robert Withrow cc: Amancio Hasty , Eivind Eklund , "Jordan K. Hubbard" , BSD User Group Hamburg , freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-Reply-To: <199809031609.MAA21827@spooky.rwwa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Robert Withrow wrote: > As far as I can tell, "An Open Letter" like this is not even *remotely* > on topic, which is intended to be "strictly technical"! I think the intention was to reach the largest audience. Have you overlooked the fact that a core member posted his reply to this mailing list, too? Chuck Youse cyouse@syncom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 12:02:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00741 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 12:02:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from firebat.wolfepub.com (firebat.wolfepub.com [206.250.193.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00727 for ; Thu, 3 Sep 1998 12:02:11 -0700 (PDT) (envelope-from matthew@wolfepub.com) Received: from ricecake.fastnet0.net (niu-ppp214.triton.net [209.172.4.214]) by firebat.wolfepub.com (8.9.0/8.9.0) with SMTP id PAA29597; Thu, 3 Sep 1998 15:00:20 -0400 (EDT) Message-Id: <3.0.3.32.19980903150806.007628b4@wolfepub.com> X-Sender: matthew@wolfepub.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 03 Sep 1998 15:08:06 -0400 To: Brian Kelly , freebsd-hackers@FreeBSD.ORG From: Matthew Hagerty Subject: Re: FreeBSD & WinGate In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why don't you turn it around? Make the FreeBSD box the gateway. It is much easier and you can do so much more with FreeBSD than Windoz. see: man natd Also, this question should have been posted in -questions, not -hackers. Matthew At 01:02 PM 9/3/98 -0400, Brian Kelly wrote: >I have a Win98 machine (runnign WinGate) and a FreeBSD machine >(2.2.7) sitting on a LAN. > > Win98 = 192.168.0.1 > FreeBSD = 192.168.0.2 > >The two can talk to each other just dandy but my FreeBSD machine cannot >access the internet through my Win98 ISDN Dialup. I've tried setting my >Gateway to NO (wingate's recommendation) as well as the Win98 LAN IP. > >Either way my FreeBSD machine can't find a route anything on the the net. > >.......................................................................... >Brian Kelly bkelly@cloud9.net >Cloud 9 Consulting, Inc. (914) 696-4000 >White Plains, New York http://www.cloud9.net > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 12:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01006 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 12:05:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01000 for ; Thu, 3 Sep 1998 12:05:31 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA03195 for ; Thu, 3 Sep 1998 12:04:25 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <35EEE839.D3169E59@dal.net> Date: Thu, 03 Sep 1998 12:04:25 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE-0827 i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Response to RST validation problem? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I'm sure everyone is aware, there was a post on bugtraq Sunday regarding a vulnerability in our TCP code which leaves the system open to attack via RST packets. In the past the project has always responded within a few days to such problems, either with a fix or a progress report on a fix. I have not seen such a response, therefore I'm asking what progress is being made on this problem. This bug is being used against some of our servers, although it's far from our biggest problem. Basically I'd like to be able to tell the 20 or so sysadmins on our network that use FreeBSD, "Please plan to upgrade your kernel sometime in the next N days," where N is a reasonable approximation of when a patch will be ready. According to Darren Reed the appropriate fix is already available in NetBSD's code, so that might be a good place to start looking. :) Thanks in advance, Doug -- *** Chief Operations Officer, DALnet IRC network *** At Barry (a small town in south Wales) hidden cameras have had to be installed to keep watch on the town's CCTV [Closed Circuit Television] to record acts of vandalism against the CCTV. - Privacy Forum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 12:30:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05218 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 12:30:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05198 for ; Thu, 3 Sep 1998 12:30:23 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:ixCrXna0OHXYVBe0n/nL0PyY+P7EPyWV@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA10889; Thu, 3 Sep 1998 21:27:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809031927.VAA10889@gratis.grondar.za> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-Reply-To: Your message of " 03 Sep 1998 18:54:25 +0200." References: <3.0.3.32.19980903123603.0068c6f4@cnt.org.br> Date: Thu, 03 Sep 1998 21:27:14 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why do you want to do that? FreeBSD isn't DOS. Your assembler routine > is unlikely to be significantly faster than the corresponding C code > compiled with 'gcc -O3'. Disagree. Anyone who has seen Phil Karn's(?) DES-in-N-clock-cycles will recognise that a talented assembler programmer can beat the crap out of a C compiler if he recodes his algorithm specifically for _*1*_ processor type. To answer the original question, get the GNU sources (they are in src/contrib/... or a ftp site near you) for GAS (gnu Assembler). That will include the Texinfo source for the stuff you want. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 12:37:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06177 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 12:37:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06170 for ; Thu, 3 Sep 1998 12:37:31 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:0JBVF4gVWUsN10QOnasoW0fCEI7JHOj7@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA10927; Thu, 3 Sep 1998 21:34:05 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809031934.VAA10927@gratis.grondar.za> To: Chuck Robey cc: Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-Reply-To: Your message of " Thu, 03 Sep 1998 12:09:54 -0400." References: Date: Thu, 03 Sep 1998 21:34:03 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Delete this if unprepared to deal with religious issues!! ] Chuck Robey wrote: > Use nasm in ports. The syntax is closer to what you're used to, and > much nicer than gas'. On top of that, nasm actually has a very nice > manual with it, it's extremely readable, and you may find (like me) that > nasm's syntax is in fact superior to tasm's or masm's. Strong disagreement!! :-) (Manual and readability excluded from disagreement) > You don't really want to use gas, because it was never made for human > use, just as a back end for gcc, and it's reactions to errors stink. No way! GAS fixed the arse-about-face assembler that intel created!! They made the assembler language user-drool-friendly! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 12:50:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08157 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 12:50:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw2.att.com [192.128.133.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08146 for ; Thu, 3 Sep 1998 12:50:48 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from kcig2.fw.att.com by kcgw2.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Thu Sep 3 14:28 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig2.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id OAA12119 for ; Thu, 3 Sep 1998 14:49:32 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Thu, 3 Sep 1998 15:49:12 -0400 Message-ID: To: weeteck@eecs.umich.edu, freebsd-hackers@FreeBSD.ORG Subject: RE: switching to real-address mode Date: Thu, 3 Sep 1998 15:49:10 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > -----Original Message----- > From: Wee Teck Ng [SMTP:weeteck@eecs.umich.edu] > Sent: Wednesday, September 02, 1998 7:20 PM > To: freebsd-hackers@FreeBSD.ORG > Subject: switching to real-address mode > > i'm trying to switch to real-address mode from protected mode in > the kernel (freebsd 2.2.7), but without success. i had followed > the instructions in the intel manual (p8-14 of system prog guide), > but my code always hung after clearing PE flag in CR0. i would > appreciate comments from anyone who have done this before. > I have tried to this thing once, but only during system boot-up time because later the interrupt handling gets too complicated. May be I still can find this code if you are interested in it. First, you need to allocate a page that has the same physical and virtual address, I have just modified slightly the VM code to reserve such a page during boot-up. Second, you have to disable the interrupts until you set up proper interrupt handlers in real mode. My code switched well to real mode and back, but the support of interrupts was very and very limited, not enough to run the BIOS calls (for what all this code intended). -Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 12:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08210 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 12:51:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08205 for ; Thu, 3 Sep 1998 12:51:17 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id MAA07438; Thu, 3 Sep 1998 12:49:57 -0700 (PDT) Message-ID: <19980903124956.D198@Alameda.net> Date: Thu, 3 Sep 1998 12:49:56 -0700 From: Ulf Zimmermann To: Wilko Bulte , Bill Paul Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pci memory mapping Reply-To: ulf@Alameda.net References: <199809022156.RAA09174@skynet.ctr.columbia.edu> <199809031037.MAA00970@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199809031037.MAA00970@yedi.iaf.nl>; from Wilko Bulte on Thu, Sep 03, 1998 at 12:37:54PM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take a look at the pseudo code at the end of the manual. It says use detection method 1, if fails, use 2. But this manual is only for firmware 4.x On Thu, Sep 03, 1998 at 12:37:54PM +0200, Wilko Bulte wrote: > As Bill Paul wrote... > > Of all the gin joints in all the towns in all the world, Wilko Bulte had > > to walk into mine and say: > > > > > > > For some reason the followin code in attach() fails: > > > > > > > > > > if (!pci_map_mem(config_id, PCI_MAP_REG_START, &mp->vbase, > > > > > &mp->pbase)) { > > > > > printf("myx%d: couldn't map memory\n", unit); > > > > > goto fail; > > > > > } > > > > Okay, Ulf has sent me a copy of his source code so I could look at it. > > > > This doesn't seem quite right somehow. The constant PCI_MAP_REG_START > > is #define in /sys/pci/pcireg.h: > > > > #define PCI_MAP_REG_START 0x10 > > > > On the two devices that I've fiddled with so far, namely the ThunderLAN > > chip and the 3Com chip, 0x10 has always been the I/O base address, i.e. > > the address used for inb/outb PIO access, and 0x14 is the memory base > > address used for memory mapped access. My impression is that these two > > registers are standar, so it's unlikely that their meanings would be > > reversed unless the chip designer is up to no good. > > > > In any case, I would try to use 0x14 instead of PCI_MAP_REG_START and > > see if that makes a difference. > > It makes a difference allright: I now get a trap12 panic ;-) No 'cannot > map mem' anymore. > > Suppose this is a strong indication of the kernel telling me > "you get that *manual* before experimenting" 8) > > > > Right.... manual...... I'm still trying to convince Mylex that handing me > > > a copy of the DAC960 V2.xx programming manual will not wipe all life from > > > Planet Earth. Sigh. Sample code from Linux and Ulf's driver are based on > > > firmware V4.xx which is different in it's interface to the OS. > > > > Do not read sample Linux code without a barf bag nearby. > > This code is not bad as far as I can tell. > > > > > If the bit doesn't come on after you write to the command register, it > > > > probably means the device doesn't actually support memory mapped access. > > > > > > Well, the bit comes on because the printf() is not triggered. But still I > > > get the 'cannot map memory' from the code sample at the top of this mail. > > > > Then I'm probably right about the register that you need to supply > > to pci_map_mep(). This is just idle speculation, but maybe the other > > cards only support memory mapped mode, and the I/O base and mem base > > registers have the same values in them. > > Let's hope I can get programming docs somehow. > > Wilko > _ ______________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl > |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl > ______________________________________________ Powered by FreeBSD __________ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 13:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17296 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 13:46:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17290 for ; Thu, 3 Sep 1998 13:46:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01183; Thu, 3 Sep 1998 13:40:37 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809031340.NAA01183@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: Chuck Robey , Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-reply-to: Your message of "Thu, 03 Sep 1998 21:34:03 +0200." <199809031934.VAA10927@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 13:40:36 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You don't really want to use gas, because it was never made for human > > use, just as a back end for gcc, and it's reactions to errors stink. > > No way! GAS fixed the arse-about-face assembler that intel created!! > They made the assembler language user-drool-friendly! The syntax is fine. It's error handling, however, sucks. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 13:50:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18063 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 13:50:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17970 for ; Thu, 3 Sep 1998 13:49:54 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with ESMTP id VAA09579; Thu, 3 Sep 1998 21:48:14 +0100 (BST) Date: Thu, 3 Sep 1998 21:48:14 +0100 (BST) From: Doug Rabson To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Sep 1998, Dag-Erling Coidan [iso-8859-1] Smřrgrav wrote: > Rodrigo Ormonde writes: > > I have to write a few high speed routines in assembler to run on a > > FreeBSD box. I used to program in assembler to DOS, so I think I have the > > necessary knowledge to do it on FreeBSD. > > Why do you want to do that? FreeBSD isn't DOS. Your assembler routine > is unlikely to be significantly faster than the corresponding C code > compiled with 'gcc -O3'. I don't see gcc -O3 producing hand pipelined MMX 3D renderers anytime soon. Assembler has its niche and it will never disappear. The niche might get smaller but it will still be there. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 14:15:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23676 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 14:15:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from localhost.my.domain (ppp6486.on.bellglobal.com [206.172.208.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23667 for ; Thu, 3 Sep 1998 14:15:48 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id RAA00232; Thu, 3 Sep 1998 17:12:56 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Thu, 3 Sep 1998 17:12:55 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Mark Murray cc: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= , Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-Reply-To: <199809031927.VAA10889@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Mark Murray wrote: > To answer the original question, get the GNU sources (they are in > src/contrib/... or a ftp site near you) for GAS (gnu Assembler). > That will include the Texinfo source for the stuff you want. Just to clarify this for the original poster: "Texinfo source" == documentation that you are looking for. :) -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 14:17:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23943 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 14:17:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23937 for ; Thu, 3 Sep 1998 14:17:01 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA12329; Thu, 3 Sep 1998 21:17:59 +0200 From: Luigi Rizzo Message-Id: <199809031917.VAA12329@labinfo.iet.unipi.it> Subject: Re: Assembler with FreeBSD To: mark@grondar.za (Mark Murray) Date: Thu, 3 Sep 1998 21:17:58 +0200 (MET DST) Cc: dag-erli@ifi.uio.no, ormonde@aker.com.br, hackers@FreeBSD.ORG In-Reply-To: <199809031927.VAA10889@gratis.grondar.za> from "Mark Murray" at Sep 3, 98 09:26:55 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why do you want to do that? FreeBSD isn't DOS. Your assembler routine > > is unlikely to be significantly faster than the corresponding C code > > compiled with 'gcc -O3'. > > Disagree. > > Anyone who has seen Phil Karn's(?) DES-in-N-clock-cycles will > recognise that a talented assembler programmer can beat the crap > out of a C compiler if he recodes his algorithm specifically for > _*1*_ processor type. It is very CPU and algorithm-dependent, and not always true. I did something similar with an FEC code (see my web page for more) and while i could almost double performance by recoding the core loop in assembler _on an old Pentium_, things were completely different on a PentiumII/PentiumPro, were the C code were actually much faster than my Pentium-optimized assembler, and the obvious asm optimizations did not gain anything over the C code. For processors with multiple execution units and hw scheduling, sometimes there is more parallelism in the CPU than in your algorithm, and it is not obvious that optimizing the assembler will run faster than an apparently worse compiler-generated output. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 14:30:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26508 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 14:30:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26499 for ; Thu, 3 Sep 1998 14:30:48 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id OAA18627; Thu, 3 Sep 1998 14:29:43 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id OAA06278; Thu, 3 Sep 1998 14:29:41 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id OAA04951; Thu, 3 Sep 1998 14:29:40 -0700 (PDT) From: Don Lewis Message-Id: <199809032129.OAA04951@salsa.gv.tsc.tdk.com> Date: Thu, 3 Sep 1998 14:29:40 -0700 In-Reply-To: Studded "Response to RST validation problem?" (Sep 3, 12:04pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Studded , freebsd-hackers@FreeBSD.ORG Subject: Re: Response to RST validation problem? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 3, 12:04pm, Studded wrote: } Subject: Response to RST validation problem? } As I'm sure everyone is aware, there was a post on bugtraq Sunday } regarding a vulnerability in our TCP code which leaves the system open } to attack via RST packets. In the past the project has always responded } within a few days to such problems, either with a fix or a progress } report on a fix. I have not seen such a response, therefore I'm asking } what progress is being made on this problem. There have been some patches posted to security. One was a mega-patch from me that fixes this as well as a few other problems. } According to Darren Reed the appropriate fix is already available in } NetBSD's code, so that might be a good place to start looking. :) The NetBSD code looks vulnerable to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 14:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28159 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 14:42:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28146 for ; Thu, 3 Sep 1998 14:42:38 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id XAA14593; Thu, 3 Sep 1998 23:37:25 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199809032137.XAA14593@ocean.campus.luth.se> Subject: Re: Response to RST validation problem? In-Reply-To: <35EEE839.D3169E59@dal.net> from Studded at "Sep 3, 98 12:04:25 pm" To: Studded@dal.net (Studded) Date: Thu, 3 Sep 1998 23:37:25 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Studded: > As I'm sure everyone is aware, there was a post on bugtraq Sunday > regarding a vulnerability in our TCP code which leaves the system open > to attack via RST packets. In the past the project has always responded Umm... For those of us that don't have time to read Yet Another Mailing List and are therefor not subscribed to bugtraq... What is the effect of this attack? I assume you can send some form of packet to the a FreeBSD machine from a remote computer and get something to happen. What? Crash, DoS, or rootprompt? Personally I'm not too worried if it's not the latter. I'll just reboot my server is something happens. :-) I'll upgrade when there is a patch... But if there's a breakin bug I kinda need to stop it. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 15:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09206 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 15:40:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09185 for ; Thu, 3 Sep 1998 15:40:18 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id SAA12808; Thu, 3 Sep 1998 18:40:14 -0400 (EDT) Date: Thu, 3 Sep 1998 18:40:14 -0400 (EDT) From: Mike To: Mikael Karpberg cc: Studded , freebsd-hackers@FreeBSD.ORG Subject: Re: Response to RST validation problem? In-Reply-To: <199809032137.XAA14593@ocean.campus.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Mikael Karpberg wrote: > machine from a remote computer and get something to happen. What? > Crash, DoS, or rootprompt? Any serious admin should subscribe to Bugtraq. If you are not subscribed, use http://www.geek-girl.com/bugtraq to search for specifics of exploits. > I'll just reboot my server is something happens. :-) Not a pleasant alternative for mission-critical servers, which brings us back to Studded's initial point, "When will a fix be available?". -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 15:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09286 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 15:40:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09280 for ; Thu, 3 Sep 1998 15:40:52 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id PAA06134; Thu, 3 Sep 1998 15:39:37 -0700 (PDT) Date: Thu, 3 Sep 1998 15:39:37 -0700 (PDT) From: Dan Busarow To: Mikael Karpberg cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Response to RST validation problem? In-Reply-To: <199809032137.XAA14593@ocean.campus.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Mikael Karpberg wrote: > of this attack? I assume you can send some form of packet to the a FreeBSD > machine from a remote computer and get something to happen. What? > Crash, DoS, or rootprompt? It's a DoS attack. Dan -- Dan Busarow 949 443 4172 Dana Point Communications, a California corporation dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 16:26:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16484 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 16:26:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16435; Thu, 3 Sep 1998 16:26:13 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA01833; Thu, 3 Sep 1998 16:24:19 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd001775; Thu Sep 3 16:24:13 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA04803; Thu, 3 Sep 1998 16:23:59 -0700 (MST) From: Terry Lambert Message-Id: <199809032323.QAA04803@usr09.primenet.com> Subject: Re: Dear, FreeBSD.... To: nobreak@nobreak.com Date: Thu, 3 Sep 1998 23:23:59 +0000 (GMT) Cc: jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr In-Reply-To: <35EE58A8.1A91A027@nobreak.com> from "??????" at Sep 3, 98 05:51:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We, 'Korea FreeBSD User Group' are so sorry that many Korean > do not know FreeBSD because of foreign language, english and > poor promotion. Actually, OCI sells FreeBSD boxes in Korea ("Interjets"). 8-). Something for your WWW page, anyway... > So we are planning to give technical support so as to increase > users of FreeBSD. For this objective we made 'Korea FreeBSD User > Group'. So we want to join you in spreading FreeBSD. > > We are now in beginning stage, there is not much activities. > But we will do good job with 'Junho Choi', 'HyunSeog Ryu' , > 'Sanghyun Park', me and the other wise mens.. > We need your continuing attention and advice.... Good goals. You may want to consider joining the "advocacy" mailing list, as well, to allow you to ask for advice in advocating FreeBSD. I think a good start would be a Hangul locale... at least a keyboard map. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 16:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16884 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 16:29:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16852; Thu, 3 Sep 1998 16:29:29 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA16333; Thu, 3 Sep 1998 16:28:20 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd016306; Thu Sep 3 16:28:18 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA05167; Thu, 3 Sep 1998 16:28:08 -0700 (MST) From: Terry Lambert Message-Id: <199809032328.QAA05167@usr09.primenet.com> Subject: Re: .nfs files, what causes them and why do they hang around? To: mike@smith.net.au (Mike Smith) Date: Thu, 3 Sep 1998 23:28:08 +0000 (GMT) Cc: jay@oneway.com, questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199809031124.LAA00428@dingo.cdrom.com> from "Mike Smith" at Sep 3, 98 11:24:03 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a fairly high-traffic NFS server running FreeBSD 2.2.6 > > using nfsv3 to all FreeBSD 2.2.6 clients. One of the things that I notice > > on it is that there are hundreds of .nfsA3d7a4.4 files hanging around. I > > know that these are some type of nfs temporary files, and that they are > > normally supposed to be removed, but I have some on there from August > > 17th. I have removed them without problem before, but I am curious as to > > what is causing them, and wondering if it is related to another problem we > > are having. > > They're files that have been unlinked but not closed on the client; > because NFS is stateless they can't be unlinked on the server (there's > no indication that the client has the file open, because there's no > state...). > > You'll normally get these if the client goes down unexpectedly. Note that if the server goes down *and* the client goes down, you may be left with "stale" versions of these files, which you then have to manually remove. As a general rule, you should "find" files matching this name format and older than twice the longest reasonable expected use of an unlinked file by a client to delete them. The others may still be in use. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 16:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18724 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 16:40:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18719 for ; Thu, 3 Sep 1998 16:40:22 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA06490; Thu, 3 Sep 1998 16:39:18 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd006407; Thu Sep 3 16:39:08 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA05561; Thu, 3 Sep 1998 16:38:50 -0700 (MST) From: Terry Lambert Message-Id: <199809032338.QAA05561@usr09.primenet.com> Subject: Re: An Open Letter To The FreeBSD Core Team To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 3 Sep 1998 23:38:50 +0000 (GMT) Cc: bsdhh@bsdhh.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809031540.IAA02021@rah.star-gate.com> from "Amancio Hasty" at Sep 3, 98 08:40:55 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps , a mediation panel or court consisting of a small odd number > of members can help address some of your concerns. > The primary requirement to be a panel member is mentally balance , > good listening skills and technically competent. Any voting body in a small organization should *never* consist of an odd number of members. In the event of a tie, the result should be treated as a vote for the status quo. Anything else quickly oscillates out of control, since it's overdriven by political in-fighting. I'm not speaking for or against the idea, at this time; just that an implementation with an odd number of voters models very quickly into factionalism. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 17:05:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21918 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 17:05:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA21906 for ; Thu, 3 Sep 1998 17:05:05 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 5462 invoked by uid 1000); 4 Sep 1998 00:04:25 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 03 Sep 1998 20:04:25 -0400 (EDT) From: Vince Vielhaber To: freebsd-hackers@FreeBSD.ORG Subject: msgrcv, msgsnd, msgctl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is/has anyone done anything with message queues? I'm porting an in house application - nothing special, listen to a port for info on turning on a fan, passing a message via msgsnd to the app that handles all requests and updating a memory map so that another app can update a PLC to change the register settings in our HVAC system. All three routines are rather small and appear to be functioning with the exception of the msg* functions. After trying a few different things, I tried to kill the queue with msgctl and got a surprise. Msgsnd appears to send the message and reports no problems; msgrcv hangs (unless in NOWAIT mode) waiting for a message that never comes no matter how many times it was sent; and msgctl returns the error code ENOENT which according to the man page and source code should not be possible. This is with 2.2.6-RELEASE. Does anyone have any idea what could be going on? Yes I have 'options SYSVMSG' in the kernel. And since this is technical, I figure it belongs on this list! Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 17:08:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22593 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 17:08:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22570 for ; Thu, 3 Sep 1998 17:08:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id KAA04174; Fri, 4 Sep 1998 10:19:28 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199809040019.KAA04174@cimlogic.com.au> Subject: Re: An Open Letter To The FreeBSD Core Team In-Reply-To: <199809032338.QAA05561@usr09.primenet.com> from Terry Lambert at "Sep 3, 98 11:38:50 pm" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 4 Sep 1998 10:19:28 +1000 (EST) Cc: hasty@rah.star-gate.com, bsdhh@bsdhh.org, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > I'm not speaking for or against the idea, at this time; just that > an implementation with an odd number of voters models very quickly > into factionalism. You can probably offset that by choosing a number of particularly odd voters. 8-) FWIW, I was surprised by the content of the original message. I must have my head in the sand. Just a matter of perspective, I suppose. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 17:08:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22625 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 17:08:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22480; Thu, 3 Sep 1998 17:07:45 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id RAA18299; Thu, 3 Sep 1998 17:06:23 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id RAA14700; Thu, 3 Sep 1998 17:06:11 -0700 (PDT) From: Gary Kline Message-Id: <199809040006.RAA14700@tao.thought.org> Subject: Re: Dear, FreeBSD.... In-Reply-To: <199809032323.QAA04803@usr09.primenet.com> from Terry Lambert at "Sep 3, 98 11:23:59 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 3 Sep 1998 17:06:11 -0700 (PDT) Cc: nobreak@nobreak.com, jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Terry Lambert: > > We, 'Korea FreeBSD User Group' are so sorry that many Korean > > do not know FreeBSD because of foreign language, english and > > poor promotion. > > Actually, OCI sells FreeBSD boxes in Korea ("Interjets"). 8-). > Something for your WWW page, anyway... > > > > So we are planning to give technical support so as to increase > > users of FreeBSD. For this objective we made 'Korea FreeBSD User > > Group'. So we want to join you in spreading FreeBSD. > > > > We are now in beginning stage, there is not much activities. > > But we will do good job with 'Junho Choi', 'HyunSeog Ryu' , > > 'Sanghyun Park', me and the other wise mens.. > > We need your continuing attention and advice.... > > Good goals. > > You may want to consider joining the "advocacy" mailing list, as > well, to allow you to ask for advice in advocating FreeBSD. > > I think a good start would be a Hangul locale... at least a > keyboard map. 8-). > Yes, on the Hangul locale! And if the Korean FreeBSD User Group is interested in creating Korean LANG *.msg files for the FreeBSD utilities, please let me know. Thanks to the help of some good people in the French and German LANG locales, I am working on the internationalization of the utilities. Every LANG locale is welcome and encouraged to join in. gary > -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 17:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28338 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 17:46:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28333 for ; Thu, 3 Sep 1998 17:46:37 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA07524; Fri, 4 Sep 1998 10:15:24 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 04 Sep 1998 10:15:24 +0930 (CST) From: "Daniel O'Connor" To: Brian Kelly Subject: RE: FreeBSD & WinGate Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Sep-98 Brian Kelly wrote: > I have a Win98 machine (runnign WinGate) and a FreeBSD machine > (2.2.7) sitting on a LAN. > > Win98 = 192.168.0.1 > FreeBSD = 192.168.0.2 > > The two can talk to each other just dandy but my FreeBSD machine cannot > access the internet through my Win98 ISDN Dialup. I've tried setting my > Gateway to NO (wingate's recommendation) as well as the Win98 LAN IP. It won't be able to talk to the internet except if you tell freebsd apps to work through win gate (which IMHO is only a proxy), so you'll have to tell your freebsd apps to use the windows machine as a proxy for web etc.. Of you could turn it around, and make the freebsd box the dialup box, and use natd for nearly transparent access for most applications to the internet. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 17:57:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01001 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 17:57:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00990 for ; Thu, 3 Sep 1998 17:57:07 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0zEkAV-0005RP-00; Thu, 3 Sep 1998 17:56:03 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id RAA19244; Thu, 3 Sep 1998 17:55:59 -0700 Date: Thu, 3 Sep 1998 17:55:59 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Imap4 (unix clients) To: "Daniel O'Connor" cc: jdp@polstra.com, lyndon@esys.ca, hackers@FreeBSD.ORG In-Reply-To: <199808270205.LAA01167@cain.gsoft.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 26 Aug, John Polstra wrote: > > What I want is a reasonable IMAP4 _client_ that runs under FreeBSD. > > "Reasonable" in my book means that the client fully supports > > disconnected operation, a requirement not met by any of the Unix > > clients I'm aware of. (Maybe pine supports it, but it's unreasonable > > for other reasons. :-) > Its not like there are many IMAP clients anyway.. > The only ones I know of are Pine, TkRat, and fetchmail :) None of the responses mentioned ml, which I've been fairly happy with for a couple of years now. It does have a couple of irritating implementation decisions; but so far, the model seems to fit my usage pretty well. Note, however, that development of ml stopped when, or soon after, the author joined Netscape... (In many ways, I still prefer the ml model over the Netscape model; although Messanger does have a few superior features, and it looks a lot nicer...) -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 20:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15432 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 20:24:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (hobbes.saturn-tech.com [207.229.19.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15416; Thu, 3 Sep 1998 20:24:35 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id VAA09720; Thu, 3 Sep 1998 21:21:17 -0600 (MDT) Date: Thu, 3 Sep 1998 21:21:17 -0600 (MDT) From: Doug Russell To: Chuck Robey cc: Robert Withrow , Eivind Eklund , "Jordan K. Hubbard" , BSD User Group Hamburg , freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Sep 1998, Chuck Robey wrote: > On Thu, 3 Sep 1998, Robert Withrow wrote: > > > And here's a vote for a "freebsd-yappers" list, for non-technical crap > > like this thread. > > It already exists (FreeBSD-chat). You're quite right, tho, the post > should have gone there. On the other hand, I, for example, don't subscribe to chat, as I already wade though current, stable, hackers, hardware, isp, smp, advocacy (plus mozilla and announce, but those don't generate much mail) each day. What happens when you want to say something to people who aren't listening? :) Perhaps we need two levels of FreeBSD-chat type lists, one for things closer related to FreeBSD, or more technical, or one where you post the first message(s) in a thread, and then move to the other, giving an introduction without the extra cruft that always seems to come as a thread gets older..... Just thinking out loud here.... Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 20:33:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16518 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 20:33:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sv10.batelco.com.bh (sv10.batelco.com.bh [193.188.97.227]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16506 for ; Thu, 3 Sep 1998 20:33:49 -0700 (PDT) (envelope-from gc9773@batelco.com.bh) Received: from batelco.com.bh ([193.188.111.31]) by sv10.batelco.com.bh (Post.Office MTA v3.5 release 215 ID# 589-54461U20000L20000S0V35) with ESMTP id bh for ; Fri, 4 Sep 1998 06:32:41 +0300 Message-ID: <35EF5F40.66D76833@batelco.com.bh> Date: Fri, 04 Sep 1998 06:32:17 +0300 From: Garry Paul Cramins X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: SMP Compliant Kernel? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To whom it may concern, I am currently running FreeBSD 2.2.6 on my Tyan Dual 120 MHZ system and am curious as to when the "Stable" release will incorporate SMP. It is my understanding that the 3.0-SNAP supports this but as I would like to stick with the stable version this is not an option for me. I have been running FreeBSD for a little over a year and love it, having switched over from Linux "just to try it out". Any info would be greatly appreciated. Sincerely, Garry P. Cramins gc9773@batelco.com.bh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 21:41:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24047 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 21:41:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24042 for ; Thu, 3 Sep 1998 21:41:37 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA02808; Thu, 3 Sep 1998 21:40:15 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Garry Paul Cramins cc: hackers@FreeBSD.ORG Subject: Re: SMP Compliant Kernel? In-reply-to: Your message of "Fri, 04 Sep 1998 06:32:17 +0300." <35EF5F40.66D76833@batelco.com.bh> Date: Thu, 03 Sep 1998 21:40:15 -0700 Message-ID: <2805.904884015@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am currently running FreeBSD 2.2.6 on my Tyan Dual 120 MHZ system > and am curious as to when the "Stable" release will incorporate SMP. It SMP will never be in -stable. It would represent far too much of an architectural change and is not in keeping with -stable's charter of relatively small, incremental features (evolution rather than revolution). I'm afraid that if SMP is what you want, you're going to have to wait until 3.0 enters it's own -stable phase in Q1 99. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 22:07:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27890 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 22:07:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jazz.snu.ac.kr (jazz.snu.ac.kr [147.46.59.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27882; Thu, 3 Sep 1998 22:07:44 -0700 (PDT) (envelope-from junker@jazz.snu.ac.kr) Received: (from junker@localhost) by jazz.snu.ac.kr (8.9.0/8.9.0) id OAA20516; Fri, 4 Sep 1998 14:06:28 +0900 (KST) To: Terry Lambert Cc: nobreak@nobreak.com, jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr Subject: Re: Dear, FreeBSD.... References: <199809032323.QAA04803@usr09.primenet.com> From: CHOI Junho Date: 04 Sep 1998 14:06:28 +0900 In-Reply-To: Terry Lambert's message of "Thu, 3 Sep 1998 23:23:59 +0000 (GMT)" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "tlambert" == Terry Lambert writes: tlambert> Actually, OCI sells FreeBSD boxes in Korea ("Interjets"). 8-). tlambert> Something for your WWW page, anyway... Interesting. What is OCI?(Oriental Chemical Industries(DongYang HwaHak)). tlambert> I think a good start would be a Hangul locale... at least a tlambert> keyboard map. 8-). Hmm. I contributed ko_KR.EUC definition file a years ago. But xpg4 locales are still be separated. I hope this situation will be solved a near future... (of course xpg4 lib should be more stable...) Unless we don't have some input method system for console application(and CJK-enabled console), keyboard map for Korean is needless. We should combine 2-5 key hits to one character. -- ----Cool FreeBSD!----MSX Forever!---J.U.N.K.E.R/Beat Snatchers!---- CHOI Junho http://jazz.snu.ac.kr/~junker Distributed Computing System Lab,CS Dept.,Seoul National Univ., ROK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 22:12:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28432 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 22:12:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jazz.snu.ac.kr (jazz.snu.ac.kr [147.46.59.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28420; Thu, 3 Sep 1998 22:12:08 -0700 (PDT) (envelope-from junker@jazz.snu.ac.kr) Received: (from junker@localhost) by jazz.snu.ac.kr (8.9.0/8.9.0) id OAA24393; Fri, 4 Sep 1998 14:09:41 +0900 (KST) To: Gary Kline Cc: tlambert@primenet.com (Terry Lambert), nobreak@nobreak.com, jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr Subject: Re: Dear, FreeBSD.... References: <199809040006.RAA14700@tao.thought.org> From: CHOI Junho Date: 04 Sep 1998 14:09:40 +0900 In-Reply-To: Gary Kline's message of "Thu, 3 Sep 1998 17:06:11 -0700 (PDT)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "kline" == Gary Kline writes: kline> Yes, on the Hangul locale! And if the Korean FreeBSD kline> User Group is interested in creating Korean LANG *.msg kline> files for the FreeBSD utilities, please let me know. kline> Thanks to the help of some good people in the French and kline> German LANG locales, I am working on the internationalization kline> of the utilities. Every LANG locale is welcome and kline> encouraged to join in. Good! But currently we have no hands to help. If we have more people to work on FreeBSD i18n and L10n jobs, we should help you. -- ----Cool FreeBSD!----MSX Forever!---J.U.N.K.E.R/Beat Snatchers!---- CHOI Junho http://jazz.snu.ac.kr/~junker Distributed Computing System Lab,CS Dept.,Seoul National Univ., ROK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 22:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29367 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 22:17:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29323; Thu, 3 Sep 1998 22:17:41 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id WAA26398; Thu, 3 Sep 1998 22:16:21 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id WAA15338; Thu, 3 Sep 1998 22:16:06 -0700 (PDT) From: Gary Kline Message-Id: <199809040516.WAA15338@tao.thought.org> Subject: Re: Dear, FreeBSD.... In-Reply-To: from CHOI Junho at "Sep 4, 98 02:09:40 pm" To: junker@jazz.snu.ac.kr (CHOI Junho) Date: Thu, 3 Sep 1998 22:16:06 -0700 (PDT) Cc: tlambert@primenet.com, nobreak@nobreak.com, jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to CHOI Junho: > >>>>> "kline" == Gary Kline writes: > > kline> Yes, on the Hangul locale! And if the Korean FreeBSD > kline> User Group is interested in creating Korean LANG *.msg > kline> files for the FreeBSD utilities, please let me know. > > kline> Thanks to the help of some good people in the French and > kline> German LANG locales, I am working on the internationalization > kline> of the utilities. Every LANG locale is welcome and > kline> encouraged to join in. > > Good! But currently we have no hands to help. If we have more people > to work on FreeBSD i18n and L10n jobs, we should help you. > Well, thank you for being willing and interested. Eventually you will have more people in your group. Perhaps then we can join forces! gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 22:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29769 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 22:21:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jazz.snu.ac.kr (jazz.snu.ac.kr [147.46.59.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29723; Thu, 3 Sep 1998 22:21:31 -0700 (PDT) (envelope-from junker@jazz.snu.ac.kr) Received: (from junker@localhost) by jazz.snu.ac.kr (8.9.0/8.9.0) id OAA23383; Fri, 4 Sep 1998 14:19:45 +0900 (KST) To: "Jordan K. Hubbard" Cc: nobreak@nobreak.com, jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr, hostmaster@kr.freebsd.org Subject: Re: Dear, FreeBSD.... References: <10513.904813774@time.cdrom.com> From: CHOI Junho Date: 04 Sep 1998 14:19:44 +0900 In-Reply-To: "Jordan K. Hubbard"'s message of "Thu, 03 Sep 1998 02:09:34 -0700" Message-ID: Lines: 29 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "jkh" == Jordan K Hubbard writes: jkh> This is again something which you probably want to work through the jkh> existing kr.freebsd.org hostmaster(s) and web admins since they've jkh> certainly been tasked with the job of providing a good rallying point jkh> for such efforts. You should also attempt to get FreeBSD mentioned in jkh> the Korean press, perhaps even getting some of your computer-oriented jkh> publications to make FreeBSD available on cover disks and such (this jkh> is also something which the Japanese FreeBSD user groups have had jkh> considerable success with, they being very worthy models to emulate in jkh> this and many other respects). FYI, in September, FreeBSD(2.2.7) is one of the cover cd of "Program World" magazine(the other one localized Redhat 5.1) of our country. I'll submit newly updated Korean packages to -ports, but it is delayed now due to recent ports system changing. jkh> Good luck, and welcome to our world-wide FreeBSD community! I want to know how to do site mirroring jobs(WWW, FTP, CVS tree, etc..). Should admin of kr.freebsd.org subscribe freebsd-hubs mailing list? Is there good documents or people to help? We should determine how many spaces to hold the mirroring data, sources, and other things for us. -- ----Cool FreeBSD!----MSX Forever!---J.U.N.K.E.R/Beat Snatchers!---- CHOI Junho http://jazz.snu.ac.kr/~junker Distributed Computing System Lab,CS Dept.,Seoul National Univ., ROK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 22:26:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00513 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 22:26:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00505; Thu, 3 Sep 1998 22:26:52 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA03080; Thu, 3 Sep 1998 22:25:25 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: CHOI Junho cc: nobreak@nobreak.com, jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, hostmaster@FreeBSD.ORG, admin@freebsd.or.kr, hostmaster@kr.freebsd.org Subject: Re: Dear, FreeBSD.... In-reply-to: Your message of "04 Sep 1998 14:19:44 +0900." Date: Thu, 03 Sep 1998 22:25:25 -0700 Message-ID: <3076.904886725@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FYI, in September, FreeBSD(2.2.7) is one of the cover cd of "Program > World" magazine(the other one localized Redhat 5.1) of our > country. I'll submit newly updated Korean packages to -ports, but it > is delayed now due to recent ports system changing. Great news! I'm always happy to see us offered in "competetive" bundles like this since it gives the users a chance to make up their own minds. > jkh> Good luck, and welcome to our world-wide FreeBSD community! > > I want to know how to do site mirroring jobs(WWW, FTP, CVS tree, See ftp://ftp.freebsd.org/pub/FreeBSD/index.html for such instructions. > etc..). Should admin of kr.freebsd.org subscribe freebsd-hubs mailing Yes, most definitely! > list? Is there good documents or people to help? We should determine > how many spaces to hold the mirroring data, sources, and other things > for us. If you have around 4GB available, you should be able to get the most basic stuff. The entire collection is currently around 7GB and will probably grow to 12GB or so in the next 6 months, as soon as we have some more space on ftp.freebsd.org. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 23:30:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08202 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 23:30:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08193 for ; Thu, 3 Sep 1998 23:30:44 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA01974; Thu, 3 Sep 1998 23:29:40 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd001952; Thu Sep 3 23:29:37 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id XAA04710; Thu, 3 Sep 1998 23:29:32 -0700 (MST) From: Terry Lambert Message-Id: <199809040629.XAA04710@usr05.primenet.com> Subject: Re: SMP Compliant Kernel? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 4 Sep 1998 06:29:32 +0000 (GMT) Cc: gc9773@batelco.com.bh, hackers@FreeBSD.ORG In-Reply-To: <2805.904884015@time.cdrom.com> from "Jordan K. Hubbard" at Sep 3, 98 09:40:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am currently running FreeBSD 2.2.6 on my Tyan Dual 120 MHZ system > > and am curious as to when the "Stable" release will incorporate SMP. It > > SMP will never be in -stable. It would represent far too much of an > architectural change and is not in keeping with -stable's charter of > relatively small, incremental features (evolution rather than > revolution). I'm afraid that if SMP is what you want, you're going to > have to wait until 3.0 enters it's own -stable phase in Q1 99. Right -- when 3.x is -stable, then -stable will be SMP. In other words, SMP support requires -stable. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 3 23:33:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08792 for freebsd-hackers-outgoing; Thu, 3 Sep 1998 23:33:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08773 for ; Thu, 3 Sep 1998 23:33:55 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA03424; Thu, 3 Sep 1998 23:32:32 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: gc9773@batelco.com.bh, hackers@FreeBSD.ORG Subject: Re: SMP Compliant Kernel? In-reply-to: Your message of "Fri, 04 Sep 1998 06:29:32 -0000." <199809040629.XAA04710@usr05.primenet.com> Date: Thu, 03 Sep 1998 23:32:32 -0700 Message-ID: <3420.904890752@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right -- when 3.x is -stable, then -stable will be SMP. > > In other words, SMP support requires -stable. Geeze, don't confuse the users any more than they already are! :) If you're going to say things like that, then at least qualify it by saying "3.0-stable" to disambiguate the reference. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 00:16:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14008 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 00:16:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA13984 for ; Fri, 4 Sep 1998 00:16:56 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id HYJMPIFJ; Fri, 04 Sep 98 07:15:50 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980904091209.009355e0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 04 Sep 1998 09:12:09 +0200 To: Doug Russell From: Marius Bendiksen Subject: Re: An Open Letter To The FreeBSD Core Team Cc: witr@rwwa.com, eivind@yes.no, jkh@time.cdrom.com, bsdhh@bsdhh.org, freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On the other hand, I, for example, don't subscribe to chat, as I already Me neither >listening? :) Perhaps we need two levels of FreeBSD-chat type lists, one >for things closer related to FreeBSD, or more technical, or one where you >post the first message(s) in a thread, and then move to the other, giving >an introduction without the extra cruft that always seems to come as a >thread gets older..... I think this is a good idea. A low-volume -chat list with more on-topic discussions is something I could subscribe to. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 00:24:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15410 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 00:24:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15405 for ; Fri, 4 Sep 1998 00:24:19 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) with SMTP id AAA14647; Fri, 4 Sep 1998 00:23:12 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Fri, 4 Sep 1998 00:23:11 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: Terry Lambert cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: SMP Compliant Kernel? In-Reply-To: <199809040629.XAA04710@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If this does not belong to -hackers, excuse me then. What is the future of FreeBSD in term of after 3.0? Will there be concurrent 4.0 development with a lot of radical and non mission critical code? Or will releases just stay around 3.x for a year or so? If there will be 4.0 as soon as 3.0 is out, what are some of the cool features that 4.0 will have - merced port? Alpha? -- Yan (just curios) Koum I don't have the password + Jan Koum But the path is chainlinked | Spelled Jan, pronounced Yan. There. So if you've got the time | Web: http://www.best.com/~jkb Set the tone to sync + OS: http://www.FreeBSD.org On Fri, 4 Sep 1998, Terry Lambert wrote: >> > I am currently running FreeBSD 2.2.6 on my Tyan Dual 120 MHZ system >> > and am curious as to when the "Stable" release will incorporate SMP. It >> >> SMP will never be in -stable. It would represent far too much of an >> architectural change and is not in keeping with -stable's charter of >> relatively small, incremental features (evolution rather than >> revolution). I'm afraid that if SMP is what you want, you're going to >> have to wait until 3.0 enters it's own -stable phase in Q1 99. > >Right -- when 3.x is -stable, then -stable will be SMP. > >In other words, SMP support requires -stable. > > > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 00:51:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18378 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 00:51:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bfl9000.telemation.de (bfl9000.telemation.de [192.54.47.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18353; Fri, 4 Sep 1998 00:51:28 -0700 (PDT) (envelope-from aklemm@telemation.de) Received: from TelemationZ2.telemation.de ([10.16.4.82]) by bfl9000.telemation.de (8.8.8/8.8.8) with SMTP id JAA21303; Fri, 4 Sep 1998 09:53:54 +0200 Received: by TelemationZ2.telemation.de with VINES-ISMTP; Fri, 4 Sep 98 9:48:42 +0200 Date: Fri, 4 Sep 98 9:44:00 MEZ Message-ID: X-Priority: 3 (Normal) To: Cc: From: (Andreas Klemm) Reply-To: Subject: =?iso-8859-1?q?fips doesn=B4t seem to work on a 32 Bit DOS filesystem (type 0Bh)?= X-Incognito-SN: 1304 X-Incognito-Version: 4.11.23 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA18354 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wanted to make a FreeBSD test installation on my Win95 machine which has lot´s of disksspace available to install a squid proxy server. Too bad, that my collegue installed a 2.6 GB "C "Partition for Win95. Is there any other tool available, that can repartition a 32 bit DOS FAT ? Best regards Andreas Klemm Please Reply to: aklemm@banyan.telemation.de as well. Can´t currently set a valid Reply-To: in the mail composer :-/ -- Andreas Klemm - System Engineer phone : +49 2131 9171-0 Telemation AG & Co. Netzwerke fax : +49 2131 9171-33 Geschäftsstelle Düsseldorf Forumstraße 24, D-41468 Neuss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 01:48:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25319 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 01:48:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25301 for ; Fri, 4 Sep 1998 01:48:27 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id KAA01882; Fri, 4 Sep 1998 10:47:17 +0200 (CEST) Message-ID: <19980904104717.A1868@cons.org> Date: Fri, 4 Sep 1998 10:47:17 +0200 From: Martin Cracauer To: Marius Bendiksen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team References: <3.0.5.32.19980904091209.009355e0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <3.0.5.32.19980904091209.009355e0@mail.scancall.no>; from Marius Bendiksen on Fri, Sep 04, 1998 at 09:12:09AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <3.0.5.32.19980904091209.009355e0@mail.scancall.no>, Marius Bendiksen wrote: > >On the other hand, I, for example, don't subscribe to chat, as I already > > Me neither Oh come on guy, I can't stand this any longer. Could you guys please stop using this thread to discuss mailing list purposes and even spamming the postmaster? There are enough open lists already. We chose -hackers because it's "the" FreeBSD community list. > >listening? :) Perhaps we need two levels of FreeBSD-chat type lists, one > >for things closer related to FreeBSD, or more technical, or one where you > >post the first message(s) in a thread, and then move to the other, giving > >an introduction without the extra cruft that always seems to come as a > >thread gets older..... > > I think this is a good idea. A low-volume -chat list with more on-topic > discussions is something I could subscribe to. You do. -hackers should be exactly that. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 01:49:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25782 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 01:49:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from grape.carrier.kiev.ua (grape.carrier.kiev.ua [193.193.193.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25751 for ; Fri, 4 Sep 1998 01:49:46 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.9.1/8.8.8) id LAA15557; Fri, 4 Sep 1998 11:47:31 +0300 (EEST) (envelope-from archer) Date: Fri, 4 Sep 1998 11:47:31 +0300 (EEST) From: Alexander Litvin Message-Id: <199809040847.LAA15557@grape.carrier.kiev.ua> To: Mikael Karpberg Cc: hackers@FreeBSD.ORG Subject: Re: Response to RST validation problem? X-Newsgroups: grape.freebsd.hackers In-Reply-To: <199809032137.XAA14593@ocean.campus.luth.se> Organization: Lucky Grape User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199809032137.XAA14593@ocean.campus.luth.se> you wrote: MK> According to Studded: >> As I'm sure everyone is aware, there was a post on bugtraq Sunday >> regarding a vulnerability in our TCP code which leaves the system open >> to attack via RST packets. In the past the project has always responded MK> Umm... For those of us that don't have time to read Yet Another Mailing MK> List and are therefor not subscribed to bugtraq... What is the effect MK> of this attack? I assume you can send some form of packet to the a FreeBSD MK> machine from a remote computer and get something to happen. What? MK> Crash, DoS, or rootprompt? It's DoS. There was an exploit posted, which allows you to reset any TCP connection, if you know its parameters: two addresses and two ports. MK> Personally I'm not too worried if it's not the latter. MK> I'll just reboot my server is something happens. :-) MK> I'll upgrade when there is a patch... But if there's a breakin bug MK> I kinda need to stop it. MK> /Mikael --- In the first place, God made idiots; this was for practice; then he made school boards. -- Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 03:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03798 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 03:19:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03782 for ; Fri, 4 Sep 1998 03:19:15 -0700 (PDT) (envelope-from w@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id MAA10449; Fri, 4 Sep 1998 12:18:06 +0200 (CEST) (envelope-from w@panke.de.freebsd.org) Received: (from w@localhost) by campa.panke.de (8.8.8/8.8.8) id WAA01099; Thu, 3 Sep 1998 22:25:39 +0200 (MET DST) (envelope-from w) Message-ID: <19980903222538.A1092@panke.de> Date: Thu, 3 Sep 1998 22:25:38 +0200 From: Wolfram Schneider To: Amancio Hasty Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team References: <19980903120643.A20537@cons.org> <199809031540.IAA02021@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199809031540.IAA02021@rah.star-gate.com>; from Amancio Hasty on Thu, Sep 03, 1998 at 08:40:55AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-09-03 08:40:55 -0700, Amancio Hasty wrote: > In the past , I suggested that we should have a web area to keep track > of important projects to help bring focus and direction however we > got nowhere mostly due to lack of time and lack of volunteers. > Perhaps the Hamburg group can step forward and help in this area We have a projects page http://www.freebsd.org/projects/ If you miss an entry or want setup a new project please sent a paragraph to www@freebsd.org Wolfram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 05:39:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15941 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 05:39:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15932 for ; Fri, 4 Sep 1998 05:39:54 -0700 (PDT) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id IAA24983; Fri, 4 Sep 1998 08:38:43 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA00816; Fri, 4 Sep 1998 08:38:43 -0400 Date: Fri, 4 Sep 1998 08:38:43 -0400 From: cmascott@world.std.com (Carl Mascott) Message-Id: <199809041238.AA00816@world.std.com> To: hackers@FreeBSD.ORG Subject: Re: Reading/writing /usr/ports is VERY slow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Carl Mascott wrote: >>>In short, I think that there are more long inter-group seeks on FFS >>>than there need be, due to the directory placement policy. I consider >>>it undesirable to spread directories out as much as possible all over >>>the filesystem. >> >Mike Smith wrote: >>One of the substantial contributors to this problem has been the >>FreeBSD policy of limiting the number of cg's by faking the disk >>layout. The intention here was to reduce the amount of space wasted in >>administrative overhead, as well as increase the likelihood of >>contiguous allocation. Unfortunately one of the less wonderful >>consequences has been the substantial increase in inter-cg distances. > Carl Mascott wrote: >For a filesystem of any given size the number of cg's is not a >factor, at least not as long as there are more than a couple of >them. Mike Smith wrote: >The number of cg, or more to the point their layout *is* somewhat >significant, simply because they can still consume moderately >substantial amounts of space. They also seem to be less efficient if >you have zillions of them. Clarification: For a filesystem of any given size the number of cg's is not a factor affecting throughput in /usr/ports. Carl Mascott wrote: >> However, >> if a cg proximity criterion were added to the new-cg-chooser, >> then the size of a cg would become a factor, although I don't >> know how important a factor. For what it's worth, vxfs also >> uses 32 MB cg's ("allocation units" in vxfs-speak). > Mike Smith wrote: >I don't actually think that the cg size would be an issue; what we're >talking about here is allocating the directory inode, and the data >blocks for the directory will follow. In most cases, the data for >these directories will move around as they're extended anyway, as they >accumulate frags and move into whole blocks. I think it would be an issue. Suppose for the sake of argument that 50% of the new directories were within 1 cg of their parent. If cg's were 4 MB instead of 32 MB, then 50% of the seeks would be approximately 1/8 as long. Even if you grant this, though, this is not a sufficient reason to change the cg size. To keep this in perspective I think this is a minor side issue to the main issue of how or whether to introduce some lumpiness into the directory allocation policy. > Meanwhile, do you have the courage to try the code snippet I included? > I'd be interested to know if it had any affect on your pathalogical > case... Maybe, but I want to let the dust settle first, and see if Kirk McKusick weighs in with anything interesting. I would also want to become familiar with the FFS source code before I did anything to it. One problem with my trying it is that it will never get a good workout on my box, a single-user workstation with ~50% full filesystems. I could certainly see any improvement in the /usr/ports throughput, but behavior with a nearly full filesystem would never get tested. -- Carl Mascott cmascott@world.std.com uunet!world!cmascott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 05:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17258 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 05:57:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17252 for ; Fri, 4 Sep 1998 05:57:24 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.8/8.8.8) id NAA16434; Fri, 4 Sep 1998 13:54:48 +0100 (BST) (envelope-from joe) Message-ID: <19980904135447.A23942@pavilion.net> Date: Fri, 4 Sep 1998 13:54:47 +0100 From: Josef Karthauser To: Matthew Hagerty , Brian Kelly , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD & WinGate Mail-Followup-To: Matthew Hagerty , Brian Kelly , freebsd-hackers@FreeBSD.ORG References: <3.0.3.32.19980903150806.007628b4@wolfepub.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3.0.3.32.19980903150806.007628b4@wolfepub.com>; from Matthew Hagerty on Thu, Sep 03, 1998 at 03:08:06PM -0400 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 03, 1998 at 03:08:06PM -0400, Matthew Hagerty wrote: > Why don't you turn it around? Make the FreeBSD box the gateway. It is > much easier and you can do so much more with FreeBSD than Windoz. > > see: man natd and also 'ppp -alias'. Joe -- Josef Karthauser Technical Manager FreeBSD: The power to serve (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 08:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07616 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 08:42:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07611 for ; Fri, 4 Sep 1998 08:42:21 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0zExzA-0004mf-00; Fri, 4 Sep 1998 08:41:16 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id IAA19937; Fri, 4 Sep 1998 08:41:13 -0700 Date: Fri, 4 Sep 1998 08:41:13 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: SMP Compliant Kernel? To: "Jan B. Koum " cc: hackers@FreeBSD.ORG In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If this does not belong to -hackers, excuse me then. > > What is the future of FreeBSD in term of after 3.0? Will there be > concurrent 4.0 development with a lot of radical and non mission critical > code? Or will releases just stay around 3.x for a year or so? If there > will be 4.0 as soon as 3.0 is out, what are some of the cool features that > 4.0 will have - merced port? Alpha? A port is not sufficient reason, in itself, to bump the major number. I'm not sure what the FreeBSD project's criteria are; but most companies reserve major number increments for changes which break backwards compatability. (For some definition of breakage. For FreeBSD, the need to use a 'compat*' library to run binaries built on systems with a lower major number would be considered a break.) Sometimes this rule will be relaxed to include major additions to functionality or extensive internal re-writes or re-design. 3.0 is adding ELF support and switching to it as the primary format, adding SMP, switching the SCSI architecture to use CAM, etc.; so it clearly qualifies for a new major number. But it will probably take several releases for all of the fallout of these changes to be handled so that 3.x becomes a truely stable system. (E.g., I don't expect the first 3.x/CAM release to support all of the devices that 2.2.7 does.) -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 08:42:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07699 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 08:42:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07663; Fri, 4 Sep 1998 08:42:44 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id KAA08344; Fri, 4 Sep 1998 10:41:31 -0500 (CDT) Message-ID: <19980904104131.B7658@emsphone.com> Date: Fri, 4 Sep 1998 10:41:31 -0500 From: Dan Nelson To: aklemm@telemation.de, hackers@FreeBSD.ORG, aklemm@banyan.telemation.de Cc: joerg@FreeBSD.ORG Subject: Re: fips doesn4t seem to work on a 32 Bit DOS filesystem (type 0Bh) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: ; from "Andreas Klemm" on Fri Sep 4 09:44:00 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Sep 04), Andreas Klemm said: > Wanted to make a FreeBSD test installation on my Win95 machine which > has lot4s of disksspace available to install a squid proxy server. > > Too bad, that my collegue installed a 2.6 GB "C "Partition for Win95. > Is there any other tool available, that can repartition a 32 bit DOS > FAT ? > > Best regards > > Andreas Klemm The latest copies of fips15c.tar.gz and presizer.exe should both be able to resize FAT32 partitions. Download them from ftp.freebsd.org/pub/FreeBSD/tools -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 10:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24989 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 10:31:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24967; Fri, 4 Sep 1998 10:31:05 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id MAA20791; Fri, 4 Sep 1998 12:26:19 -0400 (EDT) Date: Fri, 4 Sep 1998 12:26:19 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Marius Bendiksen cc: Doug Russell , witr@rwwa.com, eivind@yes.no, jkh@time.cdrom.com, bsdhh@bsdhh.org, freebsd-hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team In-Reply-To: <3.0.5.32.19980904091209.009355e0@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Sep 1998, Marius Bendiksen wrote: > >On the other hand, I, for example, don't subscribe to chat, as I already > > Me neither > > >listening? :) Perhaps we need two levels of FreeBSD-chat type lists, one > >for things closer related to FreeBSD, or more technical, or one where you > >post the first message(s) in a thread, and then move to the other, giving > >an introduction without the extra cruft that always seems to come as a > >thread gets older..... > > I think this is a good idea. A low-volume -chat list with more on-topic > discussions is something I could subscribe to. Are you guys new to mailing lists? There's no possible way you could adequately define a charter for such a mailing list, in a way that it would be clearly obvious to users which list to pick. In effect, you'd get 2 duplicate lists, which then everyone would crosspost to. Might as well wish for goodwill to man, while you at this. > > --- > Marius Bendiksen, IT-Trainee, ScanCall AS > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 10:42:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27076 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 10:42:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27064 for ; Fri, 4 Sep 1998 10:42:07 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id OAA20958; Fri, 4 Sep 1998 14:39:46 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199809041739.OAA20958@roma.coe.ufrj.br> Subject: Re: bcmp abuse in networking code ? In-Reply-To: <199809021506.RAA10910@labinfo.iet.unipi.it> from Luigi Rizzo at "Sep 2, 98 05:06:30 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Fri, 4 Sep 1998 14:39:46 -0300 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Luigi Rizzo) // poking around in /sys/net and /sys/netinet, i frequently see bcmp() being // used to compare ethernet addresses (but not only those). In some cases, // even against the ethernet broadcast address. // // In my revised bridge code i have the following macros // // #define ETH_MATCH(a,b) ( \ // ((unsigned short *)(a))[2] == ((unsigned short *)(b))[2] && \ // *((unsigned int *)(a)) == *((unsigned int *)(b)) ) Indeed very good, but why not adhere to older interfaces ? SunOS and Solaris have defined this as ether_cmp() for a long time. Here's a extract from Solaris 2.4's /usr/include/netinet/if_ether.h: ... /* * Compare two Ethernet addresses - assumes that the two given * pointers can be referenced as shorts. On architectures * where this is not the case, use bcmp instead. Note that like * bcmp, we return zero if they are the SAME. */ #if defined(mc68000) /* * On 680x0 machines, we can do a longword compare that is NOT * longword aligned, as long as it is even aligned. */ #define ether_cmp(a, b) (((short *)a)[2] != ((short *)b)[2] || \ *((long *)a) != *((long *)b)) #endif #if defined(sparc) #define ether_cmp(a, b) (((short *)b)[2] != ((short *)a)[2] || \ ((short *)b)[1] != ((short *)a)[1] || \ ((short *)b)[0] != ((short *)a)[0]) #endif #ifndef ether_cmp #define ether_cmp(a, b) (bcmp((caddr_t)a, (caddr_t)b, 6)) #endif ... There are similars for ether_copy() also. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 10:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28396 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 10:46:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28383 for ; Fri, 4 Sep 1998 10:46:51 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id JAA13413; Fri, 4 Sep 1998 09:50:44 -0700 (PDT) Message-Id: <199809041650.JAA13413@flamingo.McKusick.COM> To: Carl Mascott Subject: Re: Reading/writing /usr/ports is VERY slow cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 02 Sep 1998 18:52:35 EDT." <199809022252.SAA00868@europa.local> Date: Fri, 04 Sep 1998 09:50:43 -0700 From: Kirk McKusick Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In answer to the question of alternative layout policies for directories, the scheme that is currently in use is unchanged from what I wrote in 1983. I wrote that policy for the original fast filesystem, and never revisited it. It works well at keeping cylinder groups from filling up. As several of you have noted, it works poorly for find. Most filesystems are created from archives that were created by a depth first search (aka ftw). These directories end up being striped across the cylinder groups thus creating a worst possible senario for future depth first searches. If one knew the total number of directories to be created, the solution would be to create (total / fs_ncg) per cylinder group before moving on. Obviously, one would have to create some heuristic to guess at this number. Even using a small fixed number like say 10 would make an order of magnitude improvement. To differentiate restores from normal operation (when the current algorithm is probably more sensible), you could use the clustering of up to 10 if they were all done within a ten second window. Anyway, my conclusion is that this is an area ripe for experimentation. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 12:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15877 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 12:18:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from P1 (p1.isdn.net.il [192.115.104.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15847 for ; Fri, 4 Sep 1998 12:18:14 -0700 (PDT) (envelope-from mazal@netvision.net.il) From: mazal@netvision.net.il Received: from default - 192.115.106.68 by isdn.net.il with Microsoft SMTPSVC; Fri, 4 Sep 1998 22:03:33 +0300 Date: Fri, 04 Sep 1998 22:05:47 +0300 Subject: US$ 120.000.000 de Dolares To: freebsd-hackers@FreeBSD.ORG X-Mailer: Message-ID: <029423303190498P1@isdn.net.il> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Estimado navegante: US$ 120.000.000 lo esperan en: http://209.75.79.87/mazal y un tentador regalo para el espiritu en: http://209.75.79.87/tierra Nunca su bolsillo y su espiritu estuvieron tan cerca de enriquecerse. Gracias por su atencion.- R.M. Srul Mazal Israel Ltd mazal7@aquanet.co.il To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 13:06:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24617 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 13:06:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24561 for ; Fri, 4 Sep 1998 13:06:41 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA13475; Fri, 4 Sep 1998 20:10:52 +0200 From: Luigi Rizzo Message-Id: <199809041810.UAA13475@labinfo.iet.unipi.it> Subject: Re: bcmp abuse in networking code ? To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Date: Fri, 4 Sep 1998 20:10:52 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809041739.OAA20958@roma.coe.ufrj.br> from "Joao Carlos Mendes Luis" at Sep 4, 98 02:39:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > // In my revised bridge code i have the following macros > // > // #define ETH_MATCH(a,b) ( \ ... > Indeed very good, but why not adhere to older interfaces ? SunOS and > Solaris have defined this as ether_cmp() for a long time. in principle no problem, provided they are sufficiently common... but i have two objections in practice, #1 i want it to return 1 in case of a match because it is different from bcmp and doesn't return what address is "greater", and #2 (maybe a personal preference) i would like it uppercase to make it clear that it is a macro. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 13:12:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25847 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 13:12:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from matrix.42.org (matrix.42.org [194.246.250.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25838 for ; Fri, 4 Sep 1998 13:12:14 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id WAA07767 (sender ); Fri, 4 Sep 1998 22:10:46 +0200 (CEST) Message-ID: <19980904221045.A7670@matrix.42.org> Date: Fri, 4 Sep 1998 22:10:45 +0200 From: Stefan `Sec` Zehl To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Open Letter To The FreeBSD Core Team X-Current-Backlog: 331 messages References: <19980903120643.A20537@cons.org> <11246.904827833@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.94.2i In-Reply-To: <11246.904827833@time.cdrom.com>; from Jordan K. Hubbard on Thu, Sep 03, 1998 at 03:34:30PM +0200 I-love-doing-this: really Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 03, 1998 at 03:34:30PM +0200, Jordan K. Hubbard wrote: > > Almost no substantial technical discussion takes place anymore > > on -hackers; some of the core team members doing architectural > > That's probably more a product of our success than anything else, I > hate to say. The erosion of forums like this, frequently accompanied > by various people pining publically for "the good old days", is a > simple fact of life as the users flood in and begin dramatically > affecting the signal-to-noise ratio - I've seen it in the Linux groups > for some time and now I'm starting to see it here. [...] > I regret this as much as > anyone, of course, but short of going to a very "expensive" moderation > scheme or something yet to be invented, I don't see many alternatives. Maybe an list where only people with commit-privileges are alowed to post (but anyone is allowed to read) could serve as the 'architectural discussion' forum. I don't expect to be able to post there, but i'd like to know whats going on. More people could be allowed to post, if they are 'known' to any of the people already on the list. Just an idea, CU, Sec -- Wir sind grad beim Testen der News und haben leider noch nichts sinnvolles gefunden. Eine Antwort auf Ihre Frage können wir aus Kompetenzgründen leider auch nicht geben. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 15:09:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14110 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 15:09:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14100 for ; Fri, 4 Sep 1998 15:09:41 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-57.camalott.com [208.229.74.57]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA06287; Fri, 4 Sep 1998 17:09:30 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA15514; Fri, 4 Sep 1998 17:07:34 -0500 (CDT) (envelope-from joelh) Date: Fri, 4 Sep 1998 17:07:34 -0500 (CDT) Message-Id: <199809042207.RAA15514@detlev.UUCP> To: dag-erli@ifi.uio.no CC: ormonde@aker.com.br, hackers@FreeBSD.ORG In-reply-to: (dag-erli@ifi.uio.no) Subject: Re: Assembler with FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <3.0.3.32.19980903123603.0068c6f4@cnt.org.br> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have to write a few high speed routines in assembler to run on a >> FreeBSD box. I used to program in assembler to DOS, so I think I have the >> necessary knowledge to do it on FreeBSD. > Why do you want to do that? FreeBSD isn't DOS. Your assembler routine > is unlikely to be significantly faster than the corresponding C code > compiled with 'gcc -O3'. More specifically, many things that were best done in assembler on DOS are better done in C on Unix. I am going to write a web page later tonight that addresses the differences between DOS and Unix assembler codes, and will be sure to post the URL. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 16:25:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23617 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 16:25:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA23602 for ; Fri, 4 Sep 1998 16:24:57 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA13218 for hackers@freebsd.org; Fri, 4 Sep 1998 19:26:55 -0400 From: Bill Paul Message-Id: <199809042326.TAA13218@skynet.ctr.columbia.edu> Subject: Questions for networking gurus To: hackers@FreeBSD.ORG Date: Fri, 4 Sep 1998 19:26:53 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to work out a packet reception strategy for the RealTek ethernet controller. The RealTek chip is a bus master, which normally is a good thing because with the right sort of interface you can eliminate buffer copies within the driver code. Unfortunately, the RealTek is designed in such a way that it's almost impossible to avoid buffer copies even with bus master capability. I think there is a way to do it, but I'm not sure if it will work correctly as it depends a lot on how the higher protocol layers work, and I'm a bit fuzzy on some of the details. The RealTek chip works roughly as follows. The driver allocates a buffer area of 8K, 16K, 32K or 64K in size, depending on the setting of certain bits in the receive config register. This buffer resides in system memory, independent of the chip's packer FIFO memory. The driver then gives the chip the base address of this buffer area and activates the receiver. When the chip receives a packet, it writes a 32-bit header value into the driver's buffer area and then copies the packet immediately after the header. (The header contains the packet length and some status bits). The chip rounds up its address pointer to a 32-bit boundary and then writes the next header and packet, and so on until it hits the end of the buffer area. The driver is supposed to pass the packets along to the higher level protocols and advance a special register to indicate how much of the receive buffer has been processed. It is possible for the chip to wrap a packet from the end of the receive area back to the beginning again assuming the driver has freed up space at the beginning of the buffer area. This is sort of an oddball mechanism given the way other devices work. With most bus master chips, you have a descriptor mechanism that allows the driver to pre-allocate individual packet buffers (in our case mbuf clusters) and provide the buffer addresses to the chip. The chip can then DMA incoming packets straight into the mbufs, and the driver can just pass them along. This completely eliminates the need for buffer copies, in exchange for some wasted space since an mbuf cluster buffer is 2048 bytes in size and an ethernet frame is never larger than about 1500 bytes. You can't do that with the RealTek chip though. Here, you have only one contiguous receive buffer, and you can't predict the sizes or offsets of the packets within the buffer. The simplest way to deal with this is to use m_devget() to copy packet data out of the receive buffer and into mbufs and hand those off to the upper layers. This is silly though, because it defeats the purpose of the bus master capability, which is to avoid having the CPU perform buffer copies. One possibly alternative was proposed to me recently by Matthew Dodd, which is to use the external data pointers in mbufs. The idea works like this: - The chip receives a packet and copies it into the RX buffer region. - The driver allocates a single mbuf and sets the M_EXT flag in its header. - The driver determines the start address of the packet within the buffer region and puts that address into the external data pointer of the mbuf. - The driver sets the mbuf's data length to the length of the packet and specifies a free() routine to use to deallocate the external storage when the mbuf is released. (We don't want to actually free the buffer space though, so the free routine can be a no-op.) - Lastly, the driver passes the mbuf to ether_input() for processing. This avoids a buffer copy by using an mbuf to 'encapsulate' the packet data as an external data region, but it creates a problem: once the driver ties a portion of the receive buffer to an mbuf, it can't allow that portion of the buffer to be overwritten by the chip's DMA engine until the mbuf has been released. Otherwise, the packet data will be corrupted while another part of the kernel is fiddling with it. It may be possible to get around this by pre-allocating several receive buffer areas: if all of the space in the first region has been tied to mbufs and remains unreleased, the driver can reload the chip's receive buffer address register with ther address of another buffer. Assuming that all of the space in the first region will be released eventually, it should be possible to provide room for the chip to DMA new frames while allowing the protocols time to process existing frames in previous buffers. However this brings up the following questions: 1) Does using external data regions with mbufs like this actually work? I know it works with mbuf clusters, but that's sort of a special case. I remember reading somewhere, possibly in TCP/IP Illustrated Vol. 2, that there were bugs that prevented this from working correctly 100% of the time except for the mbuf cluster case. Has this been fixed, or are there still pitfalls? 2) What's the longtest time than an mbuf chain with received packet data will survive inside the kernel? The driver has to allocate enough memory so that it can continue handling data from the chip while waiting for previous buffers to be freed by the protocols, but if an mbuf can get hung up inside the protocols for a very long time (or worse, be locked indefinitely), then the buffer allocation would be ridiculously large. This would outweight the benefit of avoiding copies. So, does this scheme sound sensible or should I just swallow my pride and settle for using m_devget(). It would be nice to find a way to actually squeeze some decent performance out of this gawdawful device just to spite the designers. If anybody has tried to do something like this before, or is familiar with the guts of the BSD networking code, I'd appreciate any insights. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 17:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08076 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 17:49:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08071 for ; Fri, 4 Sep 1998 17:49:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA02105; Sat, 5 Sep 1998 00:41:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809050741.AAA02105@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: Questions for networking gurus In-reply-to: Your message of "Fri, 04 Sep 1998 19:26:53 EDT." <199809042326.TAA13218@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Sep 1998 00:41:31 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [... describes ethernet hardware designed by idiots, and possible workaround ...] > 2) What's the longtest time than an mbuf chain with received packet data > will survive inside the kernel? The driver has to allocate enough > memory so that it can continue handling data from the chip while > waiting for previous buffers to be freed by the protocols, but if > an mbuf can get hung up inside the protocols for a very long time > (or worse, be locked indefinitely), then the buffer allocation > would be ridiculously large. This would outweight the benefit of > avoiding copies. I would have to worry about an mbuf that gets routed into the outbound queue for a slow (eg. ppp) interface. I'd expect that such a sucker would lie around for far longer than you might want. > So, does this scheme sound sensible or should I just swallow my pride > and settle for using m_devget(). It would be nice to find a way to > actually squeeze some decent performance out of this gawdawful device > just to spite the designers. If anybody has tried to do something like > this before, or is familiar with the guts of the BSD networking code, > I'd appreciate any insights. I think that their rationalisation for using busmaster DMA was simply to avoid the need for SRAM on the card, thus lowering manufacturing costs. I fear that pride-swallowing may be in order. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 17:51:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08494 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 17:51:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from softhome.net (charleston.SoftHome.net [204.144.231.13]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA08489 for ; Fri, 4 Sep 1998 17:51:00 -0700 (PDT) (envelope-from dmarkov@softhome.net) Received: (qmail 5515 invoked by uid 417); 5 Sep 1998 01:03:18 -0000 Received: from unknown (HELO markov) (195.230.8.6) by smtp.softhome.net with SMTP; 5 Sep 1998 01:03:18 -0000 Message-ID: <000701bdd867$0f537240$0a010a0a@markov> From: "Dimitar Markov" To: "freebsd-hackers" Date: Sat, 5 Sep 1998 03:49:22 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01BDD880.2B438260" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0004_01BDD880.2B438260 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Subscribe ------=_NextPart_000_0004_01BDD880.2B438260 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
Subscribe
------=_NextPart_000_0004_01BDD880.2B438260-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 19:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26503 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 19:48:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tidal.oneway.com (tidal.oneway.com [205.177.9.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26494; Fri, 4 Sep 1998 19:48:28 -0700 (PDT) (envelope-from jay@oneway.com) Received: from localhost (jay@localhost) by tidal.oneway.com (8.8.8/8.8.3) with SMTP id WAA20922; Fri, 4 Sep 1998 22:47:53 -0400 (EDT) Date: Fri, 4 Sep 1998 22:47:52 -0400 (EDT) From: Jay To: Terry Lambert cc: Mike Smith , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: .nfs files, what causes them and why do they hang around? In-Reply-To: <199809032328.QAA05167@usr09.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Note that if the server goes down *and* the client goes down, you > may be left with "stale" versions of these files, which you then > have to manually remove. > As a general rule, you should "find" files matching this name format > and older than twice the longest reasonable expected use of an unlinked > file by a client to delete them. The others may still be in use. So what is _supposed_ to happen to these files? is the nfs server supposed to remove them automatically? Or are they just supposed to hang around till I kill them on the server? Also, I read in a couple mailing list archive messages that the nfsv3 in 2.2.x is not stable, is this true? should I be using nfsv2? Cheers, Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 20:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04764 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 20:49:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04758; Fri, 4 Sep 1998 20:49:19 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id UAA03748; Fri, 4 Sep 1998 20:48:11 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980904204811.A3167@mooseriver.com> Date: Fri, 4 Sep 1998 20:48:11 -0700 From: Josef Grosch To: freebsd-chat@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Bay Area FreeBSD Users Group (BAFUG) Sept. Meeting Reply-To: jgrosch@mooseriver.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bay Area FreeBSD Users Group -- BAFUG -- The Bay Area FreeBSD Users Group (BAFUG) will be holding it's monthly meeting on Thursday, September 10. This months meeting will be held at The Silicon Reef in the Mission district of San Francisco. The meeting will start at 7:30 pm. Agenda: ==> Nicole Harrington and David Lowe will tag-team on the topic of qmail. Nicole's experience is using qmail in an ISP environment where David's is using qmail for huge mailing list servers. Among the topics to be covered are: * integrating qmail into a user environment * MUA patching * maildir format * advantages & disadvantages of qmail in that context * spam handling with qmail ==> Jordan Hubbard will give a short talk about the recent 2.2.7 and the upcoming 2.2.8 and 3.0 (Yeah!) release. ==> Nicole Harrington and Josef Grosch will talk about their plans for the upcoming Install-A-Thon to be held on September 12 at the Robert Austin Computer show at the Cow Palace in Daly City. See http://www.freebsd-support.com/install.html for more details including directions on how to get to the Cow Palace. ==> Donations of hardware are needed to build BAFUG a test machine for use at the Install-a-thons. ==> Pizza and Soda will be ordered and the hat will be passed `round. ==> Of course, we will have the usually kvetchen about sundry topics Location: This months meeting will be held at the Silicon Reef in San Francisco. The Silicon Reef is located at 3057 17th St, between Folsom & Harrison Streets. There is plenty parking on the street. Time: The meeting starts at 7:30ish with pizza showing up around 8:00ish. We generally get kicked out around 11:00 pm. Directions: By Muni: Routes 12 Folsom, 22 Fillmore, 33 Stanyan, and 53 Southern Heights stop nearby. By BART: Exit at 16th Street Mission, walk south to 17th Street, turning left (east) and proceeding 4 1/2 short blocks to 3057 17th Street, on the right (south) side. By Car: From the South Bay and Peninsula Take 101 North to San Francisco, Get off at Vermont Ave. exit. Turn left twice on to Mariposa westbound under the freeway. Proceed eight blocks to a right (north) turn onto Harrison where Mariposa dead-ends. Go one block to a left (west) turn onto 17th Street. Proceed about one full block, and park where you can. From the East Bay: Come across the Bay bridge (I-80 westbound) and get off at the 8th street exit, bearing half-left onto Harrison, proceeding nine blocks (curving half-left as Harrison turns southbound and goes under US-101) to a right (west) turn onto 17th Street. Proceed about one full block, and park where you can. From the North Bay: Come across the Golden Gate bridge. Follow 101 which turns into Lombard Stree. At Van Ness Ave. turn right. Continue south on Van Ness until 17th st. Take a left on to 17th. Park where you can. WWW info: More info can be found at the following URLs http://www.arachna.com/freebsd/freebsd-sf.html http://www.reef.com http://www.freebsd-support.com Contact: Please contact either Ian Kallen, Nicole Harrington, or Josef Grosch on or before September 10th so we can have a basic idea of how much pizza, soda, and coffee we will need. Ian Kallen can be reached at ian@gamespot.com Nicole Harrington can be reached at nicole@mediacity.com Josef Grosch can be reached at jgrosch@MooseRiver.com $Id: Sept98Announce.txt,v 1.2 1998/09/05 01:34:17 jgrosch Exp $ -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 4 23:58:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21522 for freebsd-hackers-outgoing; Fri, 4 Sep 1998 23:58:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21470; Fri, 4 Sep 1998 23:57:54 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA13562; Fri, 4 Sep 1998 23:56:47 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd013533; Fri Sep 4 23:56:39 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id XAA29059; Fri, 4 Sep 1998 23:56:33 -0700 (MST) From: Terry Lambert Message-Id: <199809050656.XAA29059@usr08.primenet.com> Subject: Re: fips doesn4t seem to work on a 32 Bit DOS filesystem (type 0Bh) To: dnelson@emsphone.com (Dan Nelson) Date: Sat, 5 Sep 1998 06:56:33 +0000 (GMT) Cc: aklemm@telemation.de, hackers@FreeBSD.ORG, aklemm@banyan.telemation.de, joerg@FreeBSD.ORG In-Reply-To: <19980904104131.B7658@emsphone.com> from "Dan Nelson" at Sep 4, 98 10:41:31 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The latest copies of fips15c.tar.gz and presizer.exe should both be > able to resize FAT32 partitions. Download them from > ftp.freebsd.org/pub/FreeBSD/tools DANGER. The VFAT32 layout is significantly different. It is, effectively, using a stacker-type layout for block allocation to resolve the fragmentation issues, and a number of changes to the way the partition itself is laid out. A number of people have reported munging their Windows98 partitions to death using these tools on their systems. The only product that I know gets this right is a commercial one (Partition Magic). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 00:00:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21860 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 00:00:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21848 for ; Sat, 5 Sep 1998 00:00:14 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id XAA05089; Fri, 4 Sep 1998 23:59:07 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980904235906.B5046@mooseriver.com> Date: Fri, 4 Sep 1998 23:59:06 -0700 From: Josef Grosch To: freebsd-hackers@FreeBSD.ORG Subject: -stable build is broken Reply-To: jgrosch@mooseriver.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to build stable for 2 days now. There appears to be a problem with lkm/cd9660. Like so... >--- cd9660_bmap.o --- >/usr/src/lkm/cd9660/../../sys/sys/vnode.h: In function `VOP_FSYNC': >In file included from /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c:48: >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:383: `VDE' undeclared (first use this function) >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:383: (Each undeclared identifier is reported only once >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:383: for each function it appears in.) >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:383: parse error before `struct' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:395: warning: nested extern declaration of `bdevvp' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:398: warning: nested extern declaration of `cache_enter' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:400: warning: nested extern declaration of `cache_lookup' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:401: warning: nested extern declaration of `cache_purge' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:402: warning: nested extern declaration of `cache_purgevfs' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:404: warning: nested extern declaration of `checkalias' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:406: warning: nested extern declaration of `getnewvnode' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:407: warning: nested extern declaration of `insmntque' >/usr/src/lkm/cd9660/../../sys/sys/vnode.h:408: warning: nested extern declaration of `vattr_null' Yadda, yadda, ya. You get the picture. Anyone looking at this? Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 00:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26392 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 00:40:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA26381 for ; Sat, 5 Sep 1998 00:40:22 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA13946; Sat, 5 Sep 1998 07:45:08 +0200 From: Luigi Rizzo Message-Id: <199809050545.HAA13946@labinfo.iet.unipi.it> Subject: Re: Questions for networking gurus To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Sat, 5 Sep 1998 07:45:07 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809042326.TAA13218@skynet.ctr.columbia.edu> from "Bill Paul" at Sep 4, 98 07:26:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to work out a packet reception strategy for the RealTek > ethernet controller. The RealTek chip is a bus master, which normally are you talking about some 100Mbit card ? > is a good thing because with the right sort of interface you can eliminate > buffer copies within the driver code. Unfortunately, the RealTek is designed > in such a way that it's almost impossible to avoid buffer copies even with ... > The RealTek chip works roughly as follows. The driver allocates a buffer > area of 8K, 16K, 32K or 64K in size, depending on the setting of certain to summarise, a circular buffer with variable block sizes much like the one used in the audio driver :) > One possibly alternative was proposed to me recently by Matthew Dodd, > which is to use the external data pointers in mbufs. The idea works right, although i'd do it somewhat differently, i.e. before the buffer wraps around, reallocate a buffer area using a fresh set of clusters. I see only one problem in case the mbuf cluster allocator cannot return you a contiguous area of the desired size (8..64K) -- but there are several ways to possible fix this: * modify the mbuf allocator to make its granularity at least 8K * depending on how the controller works, you might be able to tell the controller that you cannot really start at the beginning, or you have to stop before the end; * if everything else fails, you can still resort to a static buffer when the contiguous allocation fails and copy data back to mbufs in that case. > 1) Does using external data regions with mbufs like this actually work? > I know it works with mbuf clusters, but that's sort of a special case. > I remember reading somewhere, possibly in TCP/IP Illustrated Vol. 2, > that there were bugs that prevented this from working correctly 100% > of the time except for the mbuf cluster case. Has this been fixed, or > are there still pitfalls? i dont know much on the above, but for sure clusters have a reference count at least which is held externally to the cluster, and the pointer to the reference count is derived by playing tricks on the cluster pointer. So, it doesn't work well if the external pointer is not to a cluster. > 2) What's the longtest time than an mbuf chain with received packet data > will survive inside the kernel? The driver has to allocate enough impossible to know. Could be several minutes e.g. if the buffer remains trapped in the socket layer. > So, does this scheme sound sensible or should I just swallow my pride > and settle for using m_devget(). It would be nice to find a way to see above. I think the CPU savings are worthwhile, and the memory waste by changing the allocator granularity is not that terrible. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 02:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08077 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 02:50:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tig.com.au (mail.tig.com.au [209.76.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08072 for ; Sat, 5 Sep 1998 02:50:35 -0700 (PDT) (envelope-from z2172268@student.unsw.edu.au) Received: from student.unsw.edu.au (p44-max8.syd.ihug.com.au [209.79.138.108]) by tig.com.au (8.8.8/8.7.3) with ESMTP id UAA26275; Sat, 5 Sep 1998 20:47:15 +1000 (EST) Message-ID: <35F107A4.F617A64E@student.unsw.edu.au> Date: Sat, 05 Sep 1998 19:43:00 +1000 From: chris/reman X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: Mike Smith CC: Mark Murray , Chuck Robey , Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD References: <199809031340.NAA01183@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > You don't really want to use gas, because it was never made for human > > > use, just as a back end for gcc, and it's reactions to errors stink. > > > > No way! GAS fixed the arse-about-face assembler that intel created!! > > They made the assembler language user-drool-friendly! > > The syntax is fine. It's error handling, however, sucks. I think the AT&T syntax used in gas really sux, considering that most x86 assemblers (MASM, TASM, A86, NASM) all use standard Intel syntax I don't see why I should bother trying to learn a new way of expressing an already hard to use language, it's like someone decided to release a version of gcc with a ; at the start of statements, and the logic was x + y = z, just because thats how we normally write it andn not the arse-around way that ansi c uses. just my $0.02 regards, chris -- Christopher Day E-Mail the_reman@hotmail.com Homepage http://www.geocities.com/TimesSquare/Lair/1218 when the rain/when the children reign/keep your conscience in the dark melt the statues in the park - Fall On Me, REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 03:12:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09702 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 03:12:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA09697; Sat, 5 Sep 1998 03:12:03 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA14166; Sat, 5 Sep 1998 10:16:50 +0200 Newsgroups: comp.unix.bsd.freebsd.misc Date: Sat, 5 Sep 1998 10:16:48 +0200 (MET DST) From: Luigi Rizzo cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: DEC NIC fixes for 2.2.x Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few days ago there was a thread on the "de" driver not putting the link back up in case of a network problem. I think i have found the fix, which is already in -current, and seems to work fine here on a -stable system. The following patch to if_de.c seems to work... @@ -447,8 +448,8 @@ * No reason to change media if we have the right media. */ tulip_reset(sc); - tulip_init(sc); } + tulip_init(sc); } it is one of the changes done between 1.81 and 1.82 of the driver. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 07:16:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26632 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 07:16:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from penmax.com (cc595093-a.mdltwn1.nj.home.com [24.3.192.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26625 for ; Sat, 5 Sep 1998 07:16:49 -0700 (PDT) (envelope-from vincef@penmax.com) Received: from penmax.com (rembrandt.penmax.com [10.1.3.2]) by penmax.com (8.8.8/8.8.8) with ESMTP id KAA05537; Sat, 5 Sep 1998 10:00:30 -0400 (EDT) (envelope-from vincef@penmax.com) Message-ID: <35F14846.96A419F8@penmax.com> Date: Sat, 05 Sep 1998 10:18:46 -0400 From: Vincent Fleming Reply-To: vincef@penmax.com Organization: Penmax Grafix, Inc. X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: joelh@gnu.org CC: dag-erli@ifi.uio.no, ormonde@aker.com.br, hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD References: <3.0.3.32.19980903123603.0068c6f4@cnt.org.br> <199809042207.RAA15514@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > >> I have to write a few high speed routines in assembler to run on a > >> FreeBSD box. I used to program in assembler to DOS, so I think I have the > >> necessary knowledge to do it on FreeBSD. > > Why do you want to do that? FreeBSD isn't DOS. Your assembler routine > > is unlikely to be significantly faster than the corresponding C code > > compiled with 'gcc -O3'. > > More specifically, many things that were best done in assembler on DOS > are better done in C on Unix. I am going to write a web page later > tonight that addresses the differences between DOS and Unix assembler > codes, and will be sure to post the URL. I've found that although it's MUCH easier in C, it isn't faster. A human can optimize much better than an automated compiler. Well, that is IF they know what they're doing... The easiest way of working with assembler routines on new platforms I've found is to actually write the function in C, and have the compiler spit out assembler code (see the man page for the compiler for the switch - I forget what FreeBSD uses). You can then edit the assembler, and use either the assember or even the C compiler to assemble the code (most C compilers are smart enough to handle .s files.) This way, the platform-specific preambles and whatnot are generated by the C compiler, and you don't have to research how to write them! Good luck! Vince Fleming To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 08:57:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06334 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 08:57:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06328 for ; Sat, 5 Sep 1998 08:57:21 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-54.camalott.com [208.229.74.54]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id KAA16389; Sat, 5 Sep 1998 10:57:35 -0500 Received: from detlev.UUCP (localhost.UUCP [127.0.0.1]) by detlev.UUCP (8.9.1/8.9.1) with ESMTP id KAA26672; Sat, 5 Sep 1998 10:55:34 -0500 (CDT) (envelope-from detlev!joelh) Message-Id: <199809051555.KAA26672@detlev.UUCP> To: chris/reman cc: Mike Smith , Mark Murray , Chuck Robey , Rodrigo Ormonde , hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-reply-to: Your message of "Sat, 05 Sep 1998 19:43:00 +1000." <35F107A4.F617A64E@student.unsw.edu.au> From: Joel Ray Holveck Date: Sat, 05 Sep 1998 10:55:31 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> You don't really want to use gas, because it was never made for human >>>> use, just as a back end for gcc, and it's reactions to errors stink. >>> No way! GAS fixed the arse-about-face assembler that intel created!! >>> They made the assembler language user-drool-friendly! >> The syntax is fine. It's error handling, however, sucks. > I think the AT&T syntax used in gas really sux, considering that > most x86 assemblers (MASM, TASM, A86, NASM) all use standard Intel > syntax I don't see why I should bother trying to learn a new way of > expressing an already hard to use language, it's like someone > decided to release a version of gcc with a ; at the start of > statements, and the logic was x + y = z, just because thats how we > normally write it andn not the arse-around way that ansi c uses. The syntax was designed to be Unix-based. Remember that gas uses the standard Unix assembler syntax, most as-based tools are designed to emit Unix syntax, etc. It would be silly for as to make an exception in Intel's case. Recall that the assemblers you named are all DOS assemblers, with the exception of NASM, which was designed to emulate one. This isn't lossage that the Unix community created. It's something that Intel did and we chose to ignore because of its drain bramage. (I really can't blame Intel that much. The 8086 was released in 1979, before there was a lot of standardization in assemblers anyway. I can't be sure, but it could have happened starting with the 4004 even.) Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 08:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06657 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 08:59:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06652 for ; Sat, 5 Sep 1998 08:59:26 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-54.camalott.com [208.229.74.54]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA16516; Sat, 5 Sep 1998 11:00:07 -0500 Received: from detlev.UUCP (localhost.UUCP [127.0.0.1]) by detlev.UUCP (8.9.1/8.9.1) with ESMTP id KAA26686; Sat, 5 Sep 1998 10:58:05 -0500 (CDT) (envelope-from detlev!joelh) Message-Id: <199809051558.KAA26686@detlev.UUCP> To: vincef@penmax.com cc: dag-erli@ifi.uio.no, ormonde@aker.com.br, hackers@FreeBSD.ORG Subject: Re: Assembler with FreeBSD In-reply-to: Your message of "Sat, 05 Sep 1998 10:18:46 EDT." <35F14846.96A419F8@penmax.com> From: Joel Ray Holveck Date: Sat, 05 Sep 1998 10:58:03 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> More specifically, many things that were best done in assembler on DOS >> are better done in C on Unix. I am going to write a web page later >> tonight that addresses the differences between DOS and Unix assembler >> codes, and will be sure to post the URL. > I've found that although it's MUCH easier in C, it isn't faster. A > human can optimize much better than an automated compiler. Well, > that is IF they know what they're doing... And IF they take the time to examine peepholes, and IF they chose to work out the times that instructions will lock registers and break piplining, and IF... It is nice to examine your assembler code. To consider it when you write your C. But instruction ordering alone is difficult enough to work out by hand, I'd rather use the assembler. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 10:03:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15163 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 10:03:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tidal.oneway.com (tidal.oneway.com [205.177.9.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15149; Sat, 5 Sep 1998 10:03:49 -0700 (PDT) (envelope-from jay@oneway.com) Received: from localhost (jay@localhost) by tidal.oneway.com (8.8.8/8.8.3) with SMTP id NAA24698; Sat, 5 Sep 1998 13:03:32 -0400 (EDT) Date: Sat, 5 Sep 1998 13:03:31 -0400 (EDT) From: Jay To: Terry Lambert cc: mike@smith.net.au, questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: .nfs files, what causes them and why do they hang around? In-Reply-To: <199809050647.XAA28867@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You are supposed to never crash. So they _shouldn't_ exist unless the server (or client) crashes? > > Also, I read in a couple mailing list archive messages that the nfsv3 > > in 2.2.x is not stable, is this true? should I be using nfsv2? > > Apply my LEASE patches, and apply David Greenman's (or was it PHK's) > NFS vnode locking patches, both posted to -current and -hackers, > and you should see a much more stable system. > I don't know if the not-my-patches have been applied to -current, > but I'd be surprised if they were in 2,2,7-stable. I've been combing through the mailing lists and have found related material, but I'm not sure if what I am finding is correct. I found a patch called 'DIFF.LEASE', are these the LEASE patches you refer to? And if they are, I did not notice any version information, Can I apply these to a 2.2.6 system? or should I upgrade the system to 2.2.7 first? Also, I can't find the vnode locking patches at all, save a reference to something done in '95. Are these problems fixed in the 3.0 branch? Thanks for your assistance so far, and for any additional help you can give. Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 10:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18425 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 10:22:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18417 for ; Sat, 5 Sep 1998 10:22:39 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA15549 for ; Sat, 5 Sep 1998 11:21:32 -0600 (MDT) Message-Id: <199809051721.LAA15549@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Slow rewrite speed in Bonnie Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Sep 1998 11:15:24 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone explain this? # bonnie -s 1024 File './Bonnie.3449', size: 1073741824 Writing with putc()...done Rewriting...done Writing intelligently...done Reading with getc()...done Reading intelligently...done Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... -------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 1024 18766 96.6 55157 89.3 8921 18.2 16883 97.4 62554 70.7 337.9 5.3 ^^^^^^^^^ -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 23:10:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12803 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 20:37:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12798 for ; Sat, 5 Sep 1998 20:36:57 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sat, 5 Sep 1998 23:35:47 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 5 Sep 1998 20:35:46 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 5 Sep 1998 23:35:45 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Cc: harlan@pfcs.com Subject: "disaster" floppy? X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Sep 1998 23:35:44 -0400 Message-ID: <2730.905052944@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was reading "backups.sgml" bacause I want to figure out how to write a script to DTRT regarding preparation for basic disaster recovery (disk partition info and a boot floppy). In particular: - Getting the partition information and fstab stuff (trivial) - Creating the right MINI kernel and building the disaster disk - Whatever else seems useful One of the things I'd like to do is to see if I can automate the production of a MINI kernel config file, based on either the dmesg output or the original kernel config file. So what *does not* belong in a MINI kernel? I'll start sniffing around, but some feedback would be helpful. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 5 23:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07987 for freebsd-hackers-outgoing; Sat, 5 Sep 1998 23:39:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07967; Sat, 5 Sep 1998 23:39:48 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA10251; Sat, 5 Sep 1998 23:39:47 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd010243; Sat Sep 5 23:39:44 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id XAA13097; Sat, 5 Sep 1998 23:39:35 -0700 (MST) From: Terry Lambert Message-Id: <199809060639.XAA13097@usr01.primenet.com> Subject: Re: .nfs files, what causes them and why do they hang around? To: jay@oneway.com (Jay) Date: Sun, 6 Sep 1998 06:39:35 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Jay" at Sep 5, 98 01:03:31 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You are supposed to never crash. > > So they _shouldn't_ exist unless the server (or client) crashes? No. They *should* exist as a means of keeping state. Basically, if you delete something that is in use by you ("you" being an NFS client (you rename it instead of deleting it. This allows you to continue to access the object. It helps here to know what an "open file" is. On a local FS, an open file is an entry in a per process open file table that points to a vnode in a local FS. On a remote FS, an open file is an entry in a per process open file table that points to an nfsnode that proxies a vnode from a remote FS. Consider the case where you open, then unlink a file. On a local FS, the vnode reference count is the count of directory references plus the count of open file references. On a remote FS, the count is *only* the number of directory references. Now say I open a file on an NFS server. The open references are not incremented (that would be state). Each time I access the file, I pass in the NFS "cookie" that tells me the device and the inode on the device to get a vnode, and thereby access the file. Now say I delete the file on the client. If I really deleted it on the server while it was open, I would no longer be able to access the file contents. This is because, when the reference count goes to zero, the vnode is freed. So as a client with a file open, instead of really deleting it, I mark it for deferred delete, and then rename it, such that someone else is unlikely to open it, and thus hols a local reference which doesn't result in a remote reference really being there (being as it's stateless). So I trade an in-core vnode refernce for a rename + an nfsnode reference with a deferred delete. Now say the client dies, and the deferred delete state, which existed as a flag on the NFSnode, was lost. The .nfs file is now there with no deferred delete referring to it. As a result, it is left hanging around. There are other (obvious) circumstances under which it can be left hanging around, as well. In any case, someone needs to clean up after the lost implied state. This is generally a cron job that remove .nfs files after they are "too old". The definition of "too old" is site dependent, and based on may expected usage of deleted-but-open files, generally multiplied by 2. Does this make sense now? > > Apply my LEASE patches, and apply David Greenman's (or was it PHK's) > > NFS vnode locking patches, both posted to -current and -hackers, > > and you should see a much more stable system. > > I don't know if the not-my-patches have been applied to -current, > > but I'd be surprised if they were in 2,2,7-stable. > > I've been combing through the mailing lists and have found related > material, but I'm not sure if what I am finding is correct. I found a > patch called 'DIFF.LEASE', are these the LEASE patches you refer to? And > if they are, I did not notice any version information, Can I apply these > to a 2.2.6 system? or should I upgrade the system to 2.2.7 first? These are expected to be applied to a 3.0 system prior to February of 1998. After that, the patch for the execution class loader is no longer applicable, Basically, the LEASE code is "opportunity locking". For this to work, it has to be obeyed on every read or write. In the -current (and the 2.2.x code), it's not obeyed. This means that there may be stale VM objects. The idea is that you must obtain a read lease for every read and a write lease for every write. If you don't do this, NFSv3, which depends on lease notifications, will be flakey, and you sould use NFSv2 instead. > Also, I can't find the vnode locking patches at all, save a reference to > something done in '95. See David Greenman's patches for mmap'ed NFS files. This *is* in the -hackers archive for 2.2.6. Basically, the vnode is not locked before areference that requires locking to be reliable. > Are these problems fixed in the 3.0 branch? I don't know. You will have to ask David Greenman. I'm pretty sure my LEASE patches were considered low priority in light of other more serious problems in the code. > Thanks for your assistance so far, and for any additional help you can > give. No problem... I'd like to see FreeBSD be as reliable as possible. It doesn't suit my purpose for participation, otherwise. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message