From owner-freebsd-arch Mon Jul 31 11:38:40 2000 Delivered-To: freebsd-arch@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 97E0037B505 for ; Mon, 31 Jul 2000 11:38:36 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.10.1/8.10.1) id e6VIcJA26725; Mon, 31 Jul 2000 14:38:19 -0400 (EDT) Date: Mon, 31 Jul 2000 14:38:19 -0400 (EDT) From: Luoqi Chen Message-Id: <200007311838.e6VIcJA26725@lor.watermarkgroup.com> To: brdean@unx.sas.com Subject: Re: isatty() reports false results Cc: bde@zeta.org.au, freebsd-arch@FreeBSD.ORG Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The way this section of code gained my attention was when I was > setting up a VPN using ppp over ssh. For example, my setup gets > instantiated using something like this: > > % /usr/local/bin/pty-redir \ > /usr/bin/ssh -t -e none -o 'Batchmode yes' \ > -i $key -l $user $host > ~/vpndev > % /usr/sbin/pppd `cat ~/vpndev` $localip:$remoteip > > In the above, pty-redir allocates a pty, opens the master side of it, > prints out the name of the slave side, dup2()'s the master side as > stdin and stdout, forks off ssh, then exits. This leaves ssh using > the master side as stdin/stdout. On the remote host, the login shell > for $user is just /usr/sbin/pppd. > > The local invocation of pppd uses the slave side of the pty which > talks to the remote side and establishes the connection. > > [This, btw, shows some of the true elegance of Unix - the ability to > chain together several seemingly unrelated processes in order > instantiate a construct that the original authors of the individual > pieces did not necesarily intend or conceive.] > It is a good thing that our system doesn't deceive ssh into thinking that it has a tty and performs ioctls like setting line discipline to normal, which would interfere with pppd's operation. > Where the pty ioctl() code gets involved is with the '-t' option to > ssh. This options causes ssh to request that the remote sshd allocate > a pty for the remote pppd which it seems to need. Ssh wants to > validate that stdin is really a tty before making the request to the > remote side. To do this it calls 'isatty()', which ends up being > called on the master side of a pty pair in this case. > > Perhaps ssh is trying to be smarter than it should be? So based on > your statement above, about pilot error, should the validation check > be removed from 'ssh'? I have no problem with that, assuming we can > maintain this diff or get the contributors to make the same change. > I think ssh should force the acquisition of a pty when the '-t' option is specified (as described in the manual page) and check for isatty() when both '-t' and '-T' are absent. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 31 15:58:27 2000 Delivered-To: freebsd-arch@freebsd.org Received: from smtp.bsdhome.com (unknown [24.25.2.13]) by hub.freebsd.org (Postfix) with ESMTP id DEC6437B762; Mon, 31 Jul 2000 15:58:22 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from vger.bsdhome.com (vger [192.168.220.2]) by smtp.bsdhome.com (8.9.3/8.9.3) with ESMTP id SAA18937; Mon, 31 Jul 2000 18:57:54 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: from localhost (bsd@localhost) by vger.bsdhome.com (8.9.3/8.9.3) with ESMTP id SAA07621; Mon, 31 Jul 2000 18:57:33 -0400 (EDT) (envelope-from bsd@vger.bsdhome.com) Date: Mon, 31 Jul 2000 18:57:33 -0400 (EDT) From: Brian Dean To: Kris Kennaway Cc: "Jeroen C. van Gelderen" , markm@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: Estimating entropy In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jul 2000, Kris Kennaway wrote: > I've been looking for some good entropy estimation algorithms which are > suitable for running "online", i.e. at runtime to estimate the content of > a set of samples. I haven't had much success so far - the only two things > I can think of are to keep a pool of the last n samples from a source, and > then either: [snip] > Any thoughts? I'm not sure if this it is quite what you're after or applicable to your particular application, but have you looked at "correlation dimension"? Correlation dimension (a google search should turn up some information) is an algorithmic technique that can be utilized to "measure" the randomness of a set of data, and can be used to differentiate between deterministic chaos and pure noise (noise being highly random, but derministic chaos, while can appear random, is not). The only problem with this, keeping in mind your requirements, is that it can take quite a bit of data to reach confidence in the result. You can get pretty good results with about 10^4.5 data points, and much better results with 10^5.5 data points. I can send you a few references if you think it might be useful. -Brian -- Brian Dean bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 31 23: 7:30 2000 Delivered-To: freebsd-arch@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 5DCA737BD81 for ; Mon, 31 Jul 2000 23:07:19 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id IAA17163; Tue, 1 Aug 2000 08:07:15 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008010607.IAA17163@grimreaper.grondar.za> To: Brian Dean Cc: arch@FreeBSD.ORG Subject: Re: Estimating entropy References: In-Reply-To: ; from Brian Dean "Mon, 31 Jul 2000 18:57:33 -0400." Date: Tue, 01 Aug 2000 08:07:15 +0200 From: Mark Murray Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can send you a few references if you think it might be useful. Yes, please! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Aug 1 6:19: 8 2000 Delivered-To: freebsd-arch@freebsd.org Received: from smtp.bsdhome.com (unknown [24.25.2.13]) by hub.freebsd.org (Postfix) with ESMTP id A4C8A37B5C1 for ; Tue, 1 Aug 2000 06:18:58 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from vger.bsdhome.com (vger [192.168.220.2]) by smtp.bsdhome.com (8.9.3/8.9.3) with ESMTP id JAA20630 for ; Tue, 1 Aug 2000 09:18:31 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: from localhost (bsd@localhost) by vger.bsdhome.com (8.9.3/8.9.3) with ESMTP id JAA26854 for ; Tue, 1 Aug 2000 09:18:30 -0400 (EDT) (envelope-from bsd@vger.bsdhome.com) Date: Tue, 1 Aug 2000 09:18:30 -0400 (EDT) From: Brian Dean To: freebsd-arch@freebsd.org Subject: Re: Estimating entropy (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In case anyone else on the list might be interested as well. ---------- Forwarded message ---------- Date: Tue, 1 Aug 2000 00:34:38 -0400 (EDT) From: Brian Dean To: Kris Kennaway Cc: Jeroen C. van Gelderen , markm@FreeBSD.org Subject: Re: Estimating entropy On Mon, 31 Jul 2000, Kris Kennaway wrote: > It might indeed, for offline analysis of noise sources. Hi Guys, With regard to Correlation Dimension, Here's a couple of good old fashioned journal references (these are classics): P. Grassberger and I. Procaccia, Physica D, vol. 9, p. 189-208, 1983. P. Grassberger and I. Procaccia, Physical Review Letters, vol. 50, p. 346, 1983. C. W. Simm, M. L. Sawley, F. Skiff, and A. Pochelon, Helvetica Physica Acta, vol. 60. p. 510, 1987. Here are a few links I found with Google using "correlation dimension": http://sprott.physics.wisc.edu/chaos/henongp.htm http://eamusic.dartmouth.edu/~leslie/correlationdimension.html http://mathworld.wolfram.com/CorrelationDimension.html http://cnls.lanl.gov/People/nbt/Book/node94.html *** There's a C program with this next link (I haven't tried it so I can't comment on whether it works well or not): http://www.theorie.physik.uni-wuppertal.de/Chaos/schreiber/programs/TISEAN/dresden/docs/d2.html Good luck! -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Aug 1 12:21:24 2000 Delivered-To: freebsd-arch@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id BA8A737BA22 for ; Tue, 1 Aug 2000 12:21:21 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id NAA18418 for ; Tue, 1 Aug 2000 13:21:20 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200008011921.NAA18418@hunkular.glarp.com> To: freebsd-arch@freebsd.org Subject: IPv6 Default Address Selection Reply-To: huntting@glarp.com Date: Tue, 01 Aug 2000 13:21:20 -0600 From: Brad Huntting Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone given any thought on how one could implement Default Addr Selection (draft-ietf-ipngwg-default-addr-select-01.txt) in FreeBSD? Not only does this algorithm seem rather time consuming, it needs to be used by the kernel (for local address select on unbound() sockets), as well as by the resolver (for sorting the results of an address query). One obvious approach is to put the "Source(D)" part of the algorithm which picks the optimal local address for a destination D in the kernel and give user space access to it through a some system call. Unfortunately, the algorithm for choosing destination addresses requires several calls to this function in order to sort a list of destination addresses. So perhaps the best thing would be to put Destination address sorting in the kernel as well, and allow userland programs (usually the resolver) to make a single system call to sort them. brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Aug 1 12:47:26 2000 Delivered-To: freebsd-arch@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 3F84037B609 for ; Tue, 1 Aug 2000 12:47:19 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:RboHhi5P/crHOOiONXIGjp/HM/R8Jek1ve90ShGBc8bKJPB0BoCnrtEEGb+NPzBH@localhost [::1]) by peace.mahoroba.org (8.11.0/3.7W-peace) with ESMTP id e71Jjbh18410; Wed, 2 Aug 2000 04:45:37 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 02 Aug 2000 04:43:03 +0900 (JST) Message-Id: <20000802.044303.74740394.ume@mahoroba.org> To: huntting@glarp.com, huntting@hunkular.glarp.com Cc: freebsd-arch@freebsd.org Subject: Re: IPv6 Default Address Selection From: Hajimu UMEMOTO In-Reply-To: <200008011921.NAA18418@hunkular.glarp.com> References: <200008011921.NAA18418@hunkular.glarp.com> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 01 Aug 2000 13:21:20 -0600 >>>>> Brad Huntting said: huntting> Has anyone given any thought on how one could implement Default huntting> Addr Selection (draft-ietf-ipngwg-default-addr-select-01.txt) in huntting> FreeBSD? Please refer /usr/share/doc/IPv6/IMPLEMENTATION section 1.6. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Aug 1 12:57:20 2000 Delivered-To: freebsd-arch@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id 0B72337BC04 for ; Tue, 1 Aug 2000 12:57:18 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id NAA20984; Tue, 1 Aug 2000 13:57:07 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200008011957.NAA20984@hunkular.glarp.com> To: Hajimu UMEMOTO Cc: huntting@glarp.com, freebsd-arch@freebsd.org Subject: Re: IPv6 Default Address Selection In-Reply-To: Your message of "Wed, 02 Aug 2000 04:43:03 +0900." <20000802.044303.74740394.ume@mahoroba.org> Date: Tue, 01 Aug 2000 13:57:07 -0600 From: Brad Huntting Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So in the case where there are multiple global addresses on the outgoing interface (from multiple upstream ISPs) what mechanism could be used to select an optimal source address? (Where optimal means shortest AS path)? huntting> Has anyone given any thought on how one could implement Default huntting> Addr Selection (draft-ietf-ipngwg-default-addr-select-01.txt) in huntting> FreeBSD? > Please refer /usr/share/doc/IPv6/IMPLEMENTATION section 1.6. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Aug 1 13: 8:25 2000 Delivered-To: freebsd-arch@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 81F0B37B862 for ; Tue, 1 Aug 2000 13:08:20 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:/r0i8godQkxEmev9ps0kgAeyrey2VQL1F61jrr8kADAjVO/OsQQSuRBLHtArwOsY@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/3.7W-peace) with ESMTP id e71K6oh18498; Wed, 2 Aug 2000 05:06:50 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 02 Aug 2000 05:06:47 +0900 (JST) Message-Id: <20000802.050647.126587638.ume@mahoroba.org> To: huntting@hunkular.glarp.com Cc: huntting@glarp.com, freebsd-arch@freebsd.org Subject: Re: IPv6 Default Address Selection From: Hajimu UMEMOTO In-Reply-To: <200008011957.NAA20984@hunkular.glarp.com> References: <20000802.044303.74740394.ume@mahoroba.org> <200008011957.NAA20984@hunkular.glarp.com> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 01 Aug 2000 13:57:07 -0600 >>>>> Brad Huntting said: huntting> So in the case where there are multiple global addresses on the huntting> outgoing interface (from multiple upstream ISPs) what mechanism huntting> could be used to select an optimal source address? (Where optimal huntting> means shortest AS path)? A longest matching address against destination address should be choosen. Only scope and address are concerned. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Aug 1 13:21:49 2000 Delivered-To: freebsd-arch@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id B18BD37B862 for ; Tue, 1 Aug 2000 13:21:46 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id OAA23791; Tue, 1 Aug 2000 14:21:42 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200008012021.OAA23791@hunkular.glarp.com> To: Hajimu UMEMOTO Cc: huntting@glarp.com, freebsd-arch@freebsd.org Subject: Re: IPv6 Default Address Selection In-Reply-To: Your message of "Wed, 02 Aug 2000 05:06:47 +0900." <20000802.050647.126587638.ume@mahoroba.org> Date: Tue, 01 Aug 2000 14:21:42 -0600 From: Brad Huntting Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A longest matching address against destination address should be > choosen. Only scope and address are concerned. That will choose a common TLA (ISP) which is good, but failing (which will happen often) that it will choose a common registry (i.e. continent), and this is usually either meaningless or sub-optimal (especially outside North America). If we have a BGP RIB, we should be able to do better at picking both destination and and source addresses, no? And if we can do better w/o using portable address space, we can keep multihomed sites from cluttering the no default zone with portable address space. brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 13:22:42 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 962C537C0C4 for ; Wed, 2 Aug 2000 13:22:34 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id WAA75578; Wed, 2 Aug 2000 22:22:28 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id WAA34799; Wed, 2 Aug 2000 22:22:27 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 2 Aug 2000 22:22:27 +0200 (CEST) From: Marius Bendiksen To: Neil Blakey-Milner Cc: arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: <20000717152514.A2056@mithrandr.moria.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I were to do/start the work on the rest of the system, would this be > acceptable? Initial patch attached. (There seems to be "quirk" fixes > mixed in with the cosmetic stuff, so the patches aren't as clean as they > could be.) This sounds like a great idea to me. I've been pondering hacking up patches for BUILD_TINY/BUILD_SMALL options throughout various system utilities, but I just haven't had the time to look at it yet. Being able to tune various parts of the build process better (memory footprint vs speed etc..) would allow us to tailor PicoBSD to more uses than we're currently able to. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 13:27:16 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id EC5D437C0D6 for ; Wed, 2 Aug 2000 13:27:09 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13K56N-0009Xu-00; Wed, 02 Aug 2000 22:26:55 +0200 Date: Wed, 2 Aug 2000 22:26:55 +0200 From: Neil Blakey-Milner To: Marius Bendiksen Cc: arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). Message-ID: <20000802222655.A36653@mithrandr.moria.org> References: <20000717152514.A2056@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mbendiks@eunet.no on Wed, Aug 02, 2000 at 10:22:27PM +0200 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed 2000-08-02 (22:22), Marius Bendiksen wrote: > > If I were to do/start the work on the rest of the system, would this be > > acceptable? Initial patch attached. (There seems to be "quirk" fixes > > mixed in with the cosmetic stuff, so the patches aren't as clean as they > > could be.) > > This sounds like a great idea to me. I've been pondering hacking up > patches for BUILD_TINY/BUILD_SMALL options throughout various system > utilities, but I just haven't had the time to look at it yet. > > Being able to tune various parts of the build process better (memory > footprint vs speed etc..) would allow us to tailor PicoBSD to more uses > than we're currently able to. Oh, I nearly forgot about this. I sent phk a prototype patch which did this whole thing more sensibly for pcisupport.c. It's attached, is slightly old, but gives the general idea on how to do it. Feel free to suggest better names for the struct. The define should probably be against PCI_QUIET, not "PICOBSD". Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 13:39:22 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id A0C3537B5CB for ; Wed, 2 Aug 2000 13:39:13 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id WAA79830; Wed, 2 Aug 2000 22:39:07 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id WAA34841; Wed, 2 Aug 2000 22:39:07 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 2 Aug 2000 22:39:07 +0200 (CEST) From: Marius Bendiksen To: Boris Popov Cc: Neil Blakey-Milner , arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is also related to the identcpu.c and i686_mem.c files. While > building a very small kernel (nanobsd :) for i486 based system I've noted > that i686_mem.c compiled always regardless of 'cpu' keyword in the config > file (why one need it on 486...). Similarly, identcpu.c code can reduced > by excluding probes and corresponding messages for Pentiums if one needs > only i486 support. Along the same note, it seems a large portion of the UFS foo is built, even if you have no UFS (FFS,MFS,EXT2FS,NFS,...) in your kernel. I ran into this in connection with looking at a working MSDOSFS_ROOT. > A more general question: should we allow more options to exclude > optional and obsolete parts of the kernel ? For example, I've ripped out > aout, aio and jail related code without any effect on functionality for my > particular system. Yes, please. The more stuff we can cut from the system, the better. This will allow us to squeeze the system further in size (attobsd?) and yield precious pages of cache for low-memory systems. Not to mention the build time issue. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 13:53:13 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D731D37BF25 for ; Wed, 2 Aug 2000 13:53:09 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA31686; Wed, 2 Aug 2000 13:52:46 -0700 Date: Wed, 2 Aug 2000 13:51:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Marius Bendiksen Cc: Neil Blakey-Milner , arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a known define that can be used by kernel module writers so they know when they're on PicoBSD? On Wed, 2 Aug 2000, Marius Bendiksen wrote: > > If I were to do/start the work on the rest of the system, would this be > > acceptable? Initial patch attached. (There seems to be "quirk" fixes > > mixed in with the cosmetic stuff, so the patches aren't as clean as they > > could be.) > > This sounds like a great idea to me. I've been pondering hacking up > patches for BUILD_TINY/BUILD_SMALL options throughout various system > utilities, but I just haven't had the time to look at it yet. > > Being able to tune various parts of the build process better (memory > footprint vs speed etc..) would allow us to tailor PicoBSD to more uses > than we're currently able to. > > Marius > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 13:53:25 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0BF0A37C078 for ; Wed, 2 Aug 2000 13:53:22 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA31692; Wed, 2 Aug 2000 13:53:15 -0700 Date: Wed, 2 Aug 2000 13:51:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Neil Blakey-Milner Cc: Marius Bendiksen , arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: <20000802222655.A36653@mithrandr.moria.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > footprint vs speed etc..) would allow us to tailor PicoBSD to more uses > > than we're currently able to. > > Oh, I nearly forgot about this. I sent phk a prototype patch which did > this whole thing more sensibly for pcisupport.c. It's attached, is > slightly old, but gives the general idea on how to do it. > > Feel free to suggest better names for the struct. The define should > probably be against PCI_QUIET, not "PICOBSD". > But it's not just PCI cards. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 14:19:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 5EC8837B5E4 for ; Wed, 2 Aug 2000 14:19:13 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id XAA86119; Wed, 2 Aug 2000 23:19:09 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id XAA34962; Wed, 2 Aug 2000 23:19:09 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 2 Aug 2000 23:19:09 +0200 (CEST) From: Marius Bendiksen To: Matthew Jacob Cc: Neil Blakey-Milner , arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a known define that can be used by kernel module writers so they know > when they're on PicoBSD? I've no idea, but if such is missing, we could probably introduce it without too much trouble. marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 2 15:35:51 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D7E7C37C1E8 for ; Wed, 2 Aug 2000 15:35:47 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA32118; Wed, 2 Aug 2000 15:35:38 -0700 Date: Wed, 2 Aug 2000 15:35:40 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Marius Bendiksen Cc: Neil Blakey-Milner , arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, introduce one, put it into the NOTES file, and let us know. On Wed, 2 Aug 2000, Marius Bendiksen wrote: > > Is there a known define that can be used by kernel module writers so they know > > when they're on PicoBSD? > > I've no idea, but if such is missing, we could probably introduce it > without too much trouble. > > marius > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 3 9:23: 6 2000 Delivered-To: freebsd-arch@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id E1E0E37B61B for ; Thu, 3 Aug 2000 09:22:40 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13KNkT-000Paw-00 for arch@freebsd.org; Thu, 03 Aug 2000 17:21:33 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13KNkR-000PTM-00 for arch@FreeBSD.org; Thu, 03 Aug 2000 17:21:31 +0100 Date: Thu, 3 Aug 2000 17:21:30 +0100 From: Ben Smithurst To: arch@FreeBSD.org Subject: rc.syscons ? Message-ID: <20000803172130.L80822@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="R+My9LyyhiUvIEro" Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --R+My9LyyhiUvIEro Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Is there some reason we don't have an rc.syscons file? Much of rc.i386 and rc.alpha seems to be identical and it would seem appropriate to split that out into rc.syscons or something, both because it would be cleaner and would mean less chance of someone updating one and forgetting the other. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / --R+My9LyyhiUvIEro Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rc.syscons" #!/bin/sh - # # $FreeBSD$ # Configure the system console. # # stdin must be redirected because it might be for a serial console # kbddev=/dev/ttyv0 viddev=/dev/ttyv0 echo -n "configuring syscons:" # keymap # case ${keymap} in [Nn][Oo] | '') ;; *) echo -n ' keymap'; kbdcontrol < ${kbddev} -l ${keymap} ;; esac # keyrate # case ${keyrate} in [Nn][Oo] | '') ;; *) echo -n ' keyrate'; kbdcontrol < ${kbddev} -r ${keyrate} ;; esac # keybell # case ${keybell} in [Nn][Oo] | '') ;; *) echo -n ' keybell'; kbdcontrol < ${kbddev} -b ${keybell} ;; esac # change function keys # case ${keychange} in [Nn][Oo] | '') ;; *) echo -n " keychange" set - ${keychange} while [ $# -gt 0 ]; do kbdcontrol <${kbddev} -f "$1" "$2" shift; shift done ;; esac # cursor type # case ${cursor} in [Nn][Oo] | '') ;; *) echo -n ' cursor'; vidcontrol < ${viddev} -c ${cursor} ;; esac # screen mapping # case ${scrnmap} in [Nn][Oo] | '') ;; *) echo -n ' screen_map'; vidcontrol < ${viddev} -l ${scrnmap} ;; esac # font 8x16 # case ${font8x16} in [Nn][Oo] | '') ;; *) echo -n ' font8x16'; vidcontrol < ${viddev} -f 8x16 ${font8x16} ;; esac # font 8x14 # case ${font8x14} in [Nn][Oo] | '') ;; *) echo -n ' font8x14'; vidcontrol < ${viddev} -f 8x14 ${font8x14} ;; esac # font 8x8 # case ${font8x8} in [Nn][Oo] | '') ;; *) echo -n ' font8x8'; vidcontrol < ${viddev} -f 8x8 ${font8x8} ;; esac # blank time # case ${blanktime} in [Nn][Oo] | '') ;; *) echo -n ' blank_time'; vidcontrol < ${viddev} -t ${blanktime} ;; esac # screen saver # case ${saver} in [Nn][Oo] | '') ;; *) echo -n ' screensaver' for i in `kldstat | awk '$5 ~ "^splash_.*$" { print $5 }'`; do kldunload ${i} done kldstat -v | grep -q _saver || kldload ${saver}_saver ;; esac # mouse daemon # case ${moused_enable} in [Yy][Ee][Ss]) echo -n ' moused' moused ${moused_flags} -p ${moused_port} -t ${moused_type} vidcontrol < ${viddev} -m on ;; esac # set this mode for all virtual screens # if [ -n "${allscreens_flags}" ]; then echo -n ' allscreens' for ttyv in /dev/ttyv*; do vidcontrol ${allscreens_flags} < ${ttyv} > ${ttyv} 2>&1 done fi echo '.' --R+My9LyyhiUvIEro Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rc-syscons.diff" Index: rc =================================================================== RCS file: /usr/cvs/src/etc/rc,v retrieving revision 1.221 diff -u -r1.221 rc --- rc 2000/07/24 13:40:41 1.221 +++ rc 2000/08/03 09:43:22 @@ -510,6 +510,12 @@ . /etc/rc.${arch} fi +# Configure the system console +# +if [ -r /etc/rc.syscons ]; then + . /etc/rc.syscons +fi + # Run rc.devfs if readable to customize devfs # if [ -r /etc/rc.devfs ]; then Index: etc.alpha/rc.alpha =================================================================== RCS file: /usr/cvs/src/etc/etc.alpha/rc.alpha,v retrieving revision 1.7 diff -u -r1.7 rc.alpha --- rc.alpha 1999/12/15 14:27:59 1.7 +++ rc.alpha 2000/07/16 21:20:18 @@ -15,153 +15,3 @@ esac echo '.' - -########################################################################## -####### Syscons section ######## -########################################################################## - -# stdin must be redirected because it might be for a serial console -kbddev=/dev/ttyv0 -viddev=/dev/ttyv0 - -echo -n "rc.alpha configuring syscons:" - -# keymap -# -case ${keymap} in -[Nn][Oo] | '') - ;; -*) - echo -n ' keymap'; kbdcontrol <${kbddev} -l ${keymap} - ;; -esac - -# keyrate -# -case ${keyrate} in -[Nn][Oo] | '') - ;; -*) - echo -n ' keyrate'; kbdcontrol <${kbddev} -r ${keyrate} - ;; -esac - -# keybell -# -case ${keybell} in -[Nn][Oo] | '') - ;; -*) - echo -n ' keybell'; kbdcontrol <${kbddev} -b ${keybell} - ;; -esac - -# change function keys -# -case ${keychange} in -[Nn][Oo] | '') - ;; -*) - echo -n " keychange" - set - ${keychange} - while [ $# -gt 0 ]; do - kbdcontrol < ${kbddev} -f "$1" "$2" - shift; shift - done - ;; -esac - -# cursor type -# -case ${cursor} in -[Nn][Oo] | '') - ;; -*) - echo -n ' cursor'; vidcontrol < ${viddev} -c ${cursor} - ;; -esac - -# screen mapping -# -case ${scrnmap} in -[Nn][Oo] | '') - ;; -*) - echo -n ' screen_map'; vidcontrol < ${viddev} -l ${scrnmap} - ;; -esac - -# font 8x16 -# -case ${font8x16} in -[Nn][Oo] | '') - ;; -*) - echo -n ' font8x16'; vidcontrol < ${viddev} -f 8x16 ${font8x16} - ;; -esac - -# font 8x14 -# -case ${font8x14} in -[Nn][Oo] | '') - ;; -*) - echo -n ' font8x14'; vidcontrol < ${viddev} -f 8x14 ${font8x14} - ;; -esac - -# font 8x8 -# -case ${font8x8} in -[Nn][Oo] | '') - ;; -*) - echo -n ' font8x8'; vidcontrol < ${viddev} -f 8x8 ${font8x8} - ;; -esac - -# blank time -# -case ${blanktime} in -[Nn][Oo] | '') - ;; -*) - echo -n ' blank_time'; vidcontrol < ${viddev} -t ${blanktime} - ;; -esac - -# screen saver -# -case ${saver} in -[Nn][Oo] | '') - ;; -*) - echo -n ' screensaver' - for i in `kldstat | awk '$5 ~ "^splash_.*$" { print $5 }'`; do - kldunload $i - done - kldstat -v | grep -q _saver || kldload ${saver}_saver - ;; -esac - -# mouse daemon -# -case ${moused_enable} in -[Yy][Ee][Ss]) - echo -n ' moused' - moused ${moused_flags} -p ${moused_port} -t ${moused_type} - vidcontrol < ${viddev} -m on - ;; -esac - -# set this mode for all virtual screens -# -if [ -n "${allscreens_flags}" ] ; then - echo -n ' allscreens' - for ttyv in /dev/ttyv*; do - vidcontrol < ${ttyv} ${allscreens_flags} - done -fi - -echo '.' Index: etc.i386/rc.i386 =================================================================== RCS file: /usr/cvs/src/etc/etc.i386/rc.i386,v retrieving revision 1.52 diff -u -r1.52 rc.i386 --- rc.i386 2000/06/25 10:55:23 1.52 +++ rc.i386 2000/07/16 21:20:25 @@ -58,154 +58,3 @@ esac echo '.' - -########################################################################## -####### Syscons section ######## -########################################################################## - -# stdin must be redirected because it might be for a serial console -# -kbddev=/dev/ttyv0 -viddev=/dev/ttyv0 - -echo -n "rc.i386 configuring syscons:" - -# keymap -# -case ${keymap} in -[Nn][Oo] | '') - ;; -*) - echo -n ' keymap'; kbdcontrol < ${kbddev} -l ${keymap} - ;; -esac - -# keyrate -# -case ${keyrate} in -[Nn][Oo] | '') - ;; -*) - echo -n ' keyrate'; kbdcontrol < ${kbddev} -r ${keyrate} - ;; -esac - -# keybell -# -case ${keybell} in -[Nn][Oo] | '') - ;; -*) - echo -n ' keybell'; kbdcontrol < ${kbddev} -b ${keybell} - ;; -esac - -# change function keys -# -case ${keychange} in -[Nn][Oo] | '') - ;; -*) - echo -n " keychange" - set - ${keychange} - while [ $# -gt 0 ]; do - kbdcontrol <${kbddev} -f "$1" "$2" - shift; shift - done - ;; -esac - -# cursor type -# -case ${cursor} in -[Nn][Oo] | '') - ;; -*) - echo -n ' cursor'; vidcontrol < ${viddev} -c ${cursor} - ;; -esac - -# screen mapping -# -case ${scrnmap} in -[Nn][Oo] | '') - ;; -*) - echo -n ' screen_map'; vidcontrol < ${viddev} -l ${scrnmap} - ;; -esac - -# font 8x16 -# -case ${font8x16} in -[Nn][Oo] | '') - ;; -*) - echo -n ' font8x16'; vidcontrol < ${viddev} -f 8x16 ${font8x16} - ;; -esac - -# font 8x14 -# -case ${font8x14} in -[Nn][Oo] | '') - ;; -*) - echo -n ' font8x14'; vidcontrol < ${viddev} -f 8x14 ${font8x14} - ;; -esac - -# font 8x8 -# -case ${font8x8} in -[Nn][Oo] | '') - ;; -*) - echo -n ' font8x8'; vidcontrol < ${viddev} -f 8x8 ${font8x8} - ;; -esac - -# blank time -# -case ${blanktime} in -[Nn][Oo] | '') - ;; -*) - echo -n ' blank_time'; vidcontrol < ${viddev} -t ${blanktime} - ;; -esac - -# screen saver -# -case ${saver} in -[Nn][Oo] | '') - ;; -*) - echo -n ' screensaver' - for i in `kldstat | awk '$5 ~ "^splash_.*$" { print $5 }'`; do - kldunload ${i} - done - kldstat -v | grep -q _saver || kldload ${saver}_saver - ;; -esac - -# mouse daemon -# -case ${moused_enable} in -[Yy][Ee][Ss]) - echo -n ' moused' - moused ${moused_flags} -p ${moused_port} -t ${moused_type} - vidcontrol < ${viddev} -m on - ;; -esac - -# set this mode for all virtual screens -# -if [ -n "${allscreens_flags}" ]; then - echo -n ' allscreens' - for ttyv in /dev/ttyv*; do - vidcontrol ${allscreens_flags} < ${ttyv} > ${ttyv} 2>&1 - done -fi - -echo '.' --R+My9LyyhiUvIEro-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 3 17: 6: 6 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 94E4237B632 for ; Thu, 3 Aug 2000 17:05:59 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id CAA46665; Fri, 4 Aug 2000 02:05:56 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id CAA41879; Fri, 4 Aug 2000 02:05:56 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Fri, 4 Aug 2000 02:05:55 +0200 (CEST) From: Marius Bendiksen To: Matthew Jacob Cc: Neil Blakey-Milner , arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Is there a known define that can be used by kernel module writers so they know > > > when they're on PicoBSD? > > I've no idea, but if such is missing, we could probably introduce it > > without too much trouble. > Well, introduce one, put it into the NOTES file, and let us know. You would have to leave this to a committer; I'm not one. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 3 17: 9: 6 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 2309E37B7E7; Thu, 3 Aug 2000 17:09:01 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id CAA46796; Fri, 4 Aug 2000 02:08:56 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id CAA41891; Fri, 4 Aug 2000 02:08:56 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Fri, 4 Aug 2000 02:08:56 +0200 (CEST) From: Marius Bendiksen To: Ben Smithurst Cc: arch@FreeBSD.ORG Subject: Re: rc.syscons ? In-Reply-To: <20000803172130.L80822@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there some reason we don't have an rc.syscons file? Much of rc.i386 > and rc.alpha seems to be identical and it would seem appropriate to > split that out into rc.syscons or something, both because it would > be cleaner and would mean less chance of someone updating one and > forgetting the other. This sounds good to me; however, I'm getting somewhat concerned about the growing number of seperate rc files in the top level of /etc... Might the time be right to consider relocating these to a second level directory? On a side note, has the issue of replacing the current rc script mechanism been rehashed lately? Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 3 22:10:14 2000 Delivered-To: freebsd-arch@freebsd.org Received: from gateway.posi.net (c1096725-a.smateo1.sfba.home.com [24.20.139.104]) by hub.freebsd.org (Postfix) with ESMTP id 899AB37B938 for ; Thu, 3 Aug 2000 22:10:12 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id WAA01759; Thu, 3 Aug 2000 22:11:19 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Thu, 3 Aug 2000 22:11:18 -0700 (PDT) From: Kelly Yancey To: Boris Popov Cc: abial@webgiro.com, arch@FreeBSD.ORG Subject: Re: SysctlFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ trimmed the CC list ] On Fri, 28 Jul 2000, Boris Popov wrote: > Yes, I've wrote sysctlfs (scfs) just as an explorer for sysctl > name space and as very simple sample filesystem. Yesterday, it has been > modified to compile on recent -current. In addition, it demonstrates > (ab)use of VOP_GETEXTATTR(). > > For those who interested: ftp://ftp.butya.kz/misc/scfs.tar.gz > Cool. I was thinking that since the issue of a sysctl filesystem comes up every so often, it would be nice to include an implementation as a port. Would you be interested in making and maintaining a port of your implementation? If not, I'll probably finish polishing off the one I was writing and do it. Then, next time it comes up we can just say "see port XXX" :) Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 4 15: 3:42 2000 Delivered-To: freebsd-arch@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 90C7937BA64; Fri, 4 Aug 2000 15:03:30 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA54409; Fri, 4 Aug 2000 16:00:44 -0600 (MDT) (envelope-from ken) Date: Fri, 4 Aug 2000 16:00:44 -0600 From: "Kenneth D. Merry" To: net@FreeBSD.ORG Subject: new zero copy sockets and NFS snapshot Message-ID: <20000804160044.A54375@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -arch and -current BCC'ed for wider coverage, please direct followups to -net and/or me ] I have put a new copy of the zero copy sockets and NFS patches, against -current as of early August 3rd, 2000, here: http://people.FreeBSD.ORG/~ken/zero_copy/ Feedback would be very welcome, we haven't gotten much response on this yet. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - Support has been merged in from -current for Alteon and Netgear 1000baseT boards. Initial tests with Alteon boards indicate that their performance is identical to the 1000baseSX model. - The zero copy send support code has been renamed and moved to a new file, src/sys/kern/uipc_cow.c. - Drew Gallatin has made some performance enhancements in the ti(4) driver that decrease receive-side CPU utilization and increase performance somewhat. (CPU utilization changes are hard to quantify, but are probably in the 10-20% range. TCP performance on my test Pentium II 350's increased from about 746Mbps to about 763Mbps, as measured by netperf.) - Drew Gallatin submitted a fix to the IP fragmenting code to make sure that outgoing fragments are 8-byte aligned. - Incorporated Bill Paul's fixes to Alteon's 12.4.11 firmware that hopefully include most of the true bugfixes to their 12.4.13 firmware. Alteon's 12.4.13 firmware, when used with 1000BaseT boards, doesn't seem to autonegotiate anything other than 1000BaseT, and also doesn't like to be forced to a speed other than 1000Mbps. Alteon hasn't yet responded to queries about the problems with version 12.4.13 of their firmware, so we're using version 12.4.11 with some selected fixes from 12.4.13. This seems to properly negotiate at all supported speeds and duplex settings with 1000baseT boards. - Header splitting is now restricted to Tigon 2 boards only. We only have source for firmware for the Tigon 2, thus the reason header splitting is only supported for those chips. - Drew Gallatin's NFS read header splitting code is now included in the firmware. This can dramatically improve NFS read performance. - There is a new references section in the FAQ that includes pointers to some relevant papers and proposals. For those of you who missed the previous messages about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Two sets of zero copy send code, written by Drew Gallatin and Robert Picco . - Zero copy receive code, written by Drew Gallatin. - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Aug 5 12:39:17 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 23E7F37B713 for ; Sat, 5 Aug 2000 12:39:10 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13L9mm-0000LF-00 for freebsd-arch@freebsd.org; Sat, 05 Aug 2000 21:39:08 +0200 Received: from p3e9e266c.dip0.t-ipconnect.de ([62.158.38.108] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13L9mi-0007Fp-00 for freebsd-arch@freebsd.org; Sat, 05 Aug 2000 21:39:04 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 5CE51AB91 for ; Sat, 5 Aug 2000 21:39:08 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 21B2A14BB0; Sat, 5 Aug 2000 21:39:03 +0200 (CEST) Date: Sat, 5 Aug 2000 21:39:03 +0200 To: freebsd-arch@freebsd.org Subject: ln -i ? Message-ID: <20000805213903.A3285@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Linux's ln(1) has an -i option, which means "interactive" as rm/mv/cp etc have, too. I wonder if that could be an option for our ln(1) as well. Could be useful. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message