From owner-freebsd-hackers Sun Jun 6 3:42: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4B4A014FE4 for ; Sun, 6 Jun 1999 03:40:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA16524 for FreeBSD-hackers@freebsd.org; Sun, 6 Jun 1999 11:55:03 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA37793 for FreeBSD-hackers@freebsd.org; Sun, 6 Jun 1999 11:52:50 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906060952.LAA37793@yedi.iaf.nl> Subject: sgmlformat & making release To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Sun, 6 Jun 1999 11:52:50 +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+ PL43 (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 I'm tryingeto do a "make release" via time make release CHROOTDIR=/local/GenRelease BUILDNAME=3.2.0.-rel-wkb RELEASETAG=RELENG_3_2_0_RELEASE Making docs... ===> Extracting for docproj-1.0 >> No MD5 checksum file. ===> Patching for docproj-1.0 ===> Configuring for docproj-1.0 ===> Installing for docproj-1.0 ===> docproj-1.0 depends on executable: instant - not found ===> Verifying install for instant in /usr/ports/textproc/sgmlformat >> sgmlformat-1.7.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from http://fallout.campusview.indiana.edu/ports/distfiles/. fetch: reading reply from fallout.campusview.indiana.edu: Operation timed out >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/. fetch: ftp.freebsd.org: Host name lookup failure >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop. *** Error code 1 But: yedi#ls /usr/ports/distfiles docbk241.tar.Z isoENTS.zip linuxdoc-1.1.tar.gz docbk30.tar.Z jade-1.2.1.tar.gz sgmlformat-1.7.tar.gz yedi# I'm probably missing something obvious here, but I can't figure out what. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 6:35:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with SMTP id 1B47714F12 for ; Sun, 6 Jun 1999 06:35:03 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: (qmail 7750 invoked by uid 1003); 6 Jun 1999 13:35:02 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Jun 1999 13:35:02 -0000 Date: Sun, 6 Jun 1999 09:35:02 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: hackers@freebsd.org Subject: wfd.c and ATAPI Zip 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 two boxes with ATAPI Zip Drives: Box1: wdc1: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) Box2: wdc1: unit 0 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set The drive on Box1 gets timeouts when reading/writing; the drive on Box2 works fine. After checking out /sys/i386/isa/wfd.c, I changed the block transfer limit to that of buggy drives (64) and the timeouts disappeared. I tried setting the block transfer limit to unlimited (0) as is used with non-buggy hardware, no timeouts occurred on Box2. Comparing the model names with wfd.c's comparison, I see that any model different that Box2's is *not* buggy: if (!strcmp(ap->model, "IOMEGA ZIP 100 ATAPI")) { since strcmp returns 0 if the strings match. On my drives, however, the opposite seems the case. My thoughts now are: 1) My two drive are somewhat 'rogue' in that they don't conform to the driver's expectations. 2) When the driver was written, the '!strcmp' should be 'strcmp' since strcmp returns 0 when equal (-1 or 1 when < or >), in which case my patch makes sense: --- /sys/i386/isa/wfd.c.orig Thu Feb 18 17:06:08 1999 +++ /sys/i386/isa/wfd.c Tue Jun 6 08:59:59 1999 @@ -247,7 +247,7 @@ * is known to lock up if transfers > 64 blocks are * requested. */ - if (!strcmp(ap->model, "IOMEGA ZIP 100 ATAPI")) { + if (strcmp(ap->model, "IOMEGA ZIP 100 ATAPI")) { printf("wfd%d: buggy Zip drive, 64-block transfer limit set\n", t->lun); t->maxblks = 64; 3) I've just plain lost it :) Can anyone else with an ATAPI Zip Drive confirm this? Regards, Chris ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 7:52:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 32ECA14EDF for ; Sun, 6 Jun 1999 07:52:27 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id KAA08566; Sun, 6 Jun 1999 10:40:02 -0400 Date: Sun, 6 Jun 1999 10:40:01 -0400 (EDT) From: Zhihui Zhang To: Farshid Eslami Cc: freebsd-hackers@freebsd.org Subject: Re: allocate file blocks contiguously 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 > > For more info about maxcontig, you can refer to the well-known > paper of McKusic et al about Fast File System. It is a parameter > that is hardware dependent. You can't get performance just by > increasing its value. Unfortunately, I don't have on-line version > of that paper. > > > --Farshid > > On Wed, 2 Jun 1999, Zhihui Zhang wrote: > > > > > In FFS, there is a parameter called maxcontig (default to 16) that > > determines the number of blocks we can allocate contiguously for a single > > file. What is its optimal value? I mean, if we allocate ALL the data > > blocks of a very big file contiguously, will its I/O performance be > > improved greatly? It seems to me this number may also be limited by > > system buffering capability (MAXPHYS?) and underlying hardware controller. > > Can anyone give me some hints on the choice of the value of maxcontig? > > I read the paper at http://docs.FreeBSD.org/44doc/, which is basically the same as in the 4.4 BSD book (p276). My feeling is that if we allocate ALL the data blocks of a big file contiguously, this will lead to "too much localization" as described in the paper (or the book). However, this may be good for this big file if the system buffering capability and hardware allow it (at the cost of other files?) Regards, Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 9:41:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from detlev.UUCP (tex-33.camalott.com [208.229.74.33]) by hub.freebsd.org (Postfix) with ESMTP id 383231548A for ; Sun, 6 Jun 1999 09:41:30 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id LAA57957; Sun, 6 Jun 1999 11:41:37 -0500 (CDT) (envelope-from joelh) To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Word processor distractions (was Re: Kernel config script:) References: <99Jun4.082139est.40325@border.alcanet.com.au> From: Joel Ray Holveck Date: 06 Jun 1999 11:41:29 -0500 In-Reply-To: Peter Jeremy's message of "Fri, 4 Jun 1999 08:37:34 +1000" Message-ID: <863e05cmdi.fsf@detlev.UUCP> Lines: 110 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've seen references to people writing Towers of Hanoi in troff, but > I don't have a pointer to the actual code. Can't help you there, but here's something for you: /hanoi{/x{{exit}}def /e{exch}def /d{dup}def /l{loop}def /n exch def /m 2 n 1 sub exp cvi def[m{d 0 eq x if d[e d 0{1 add e 2 div cvi d 0 eq x if e}l pop d 1 sub 2 e exp cvi 2 index e sub 1 add e d n e sub 3 1 roll 1 and 0 eq{0 e sub}if 3 mod 3 add 3 mod]e d m ge{{d 1 and 0 eq x if 2 div cvi}l 2 div cvi}{2 mul 1 add{d m and 0 ne x if 2 mul}l}ifelse}l pop]}def It's an iterative implementation of Towers of Hanoi in PostScript. I'm quite proud of it, in a twisted sort of way. If you ever come across that troff code, let me know! > Of course, it doesn't come close to emacs' capabilities - check out > 'info emacs Amusements' :-). When running under X, you can play with > the fonts and colours as well. There's more than just the docs show. I do suggest looking around in the Lisp directories now and then; there's lots of stuff that's not documented, games and otherwise. Have you ever tried M-x tetris? It's in there, at least as of GNU Emacs 20.3. I suppose that if we consider Towers of Hanoi to be a useful distraction, then we'll also add in Life (M-x life) as well; I suspect that Life distracted Bill Gosper more than Towers of Hanoi has distracted any single hacker. If you want a bit more modern of a distraction, a neural net bot that uses landmarks to find the center of a box is in the 20.3 distribution too; try M-x landmark. There's also some tools to help you analyze games. For instance, a mode to help you document decision trees in chess is included; see /usr/local/share/emacs/20.3/lisp/play/gametree.el. There's also a mode for helping you with monoalphabetic substitution ciphers that the games mags love so much has been. It has frequency analysis for characters and digrams, can bring up adjacency lists, has the ability to push and pop mappings, and of course keeps your plaintext up-to-date as you change the mappings. Take a look in decipher.el. If you're tired of playing with fonts, try something a bit more substantial: get a handwritten printout of the buffer with M-x handwrite. Be sure to enable PostScript support on your printer first if you want a hard copy. We have the more advanced /usr/games/morse, but Emacs does include M-x morse-region and M-x unmorse-region for your continued enjoyment. It's not autoloaded, so do M-x load-library RET morse RET or include (require 'morse) in your .emacs file first. I've started another version with prosigns, ISO-8859-1 and KOI8R support, and the ability to use /dev/speaker, but it's not done yet and may never be. For those who are into frustration, the peg solitaire game (jump pegs, try to leave just one) is in M-x solitaire. If you're interested in that game, then you'll probably also want to look at HAKMEM item 75, in which Bill Gosper, Steve Brown, and Malcolm Rayfield briefly analyze the game, and present a winning solution. (Item 76 covers the triangular Hi-Q game.) If you don't have a copy of HAKMEM, email me for one. The Emacs docs discuss Dissociated Press, but don't mention the StuDlYCApSiFIer, which provides studlify-word, -region, and -buffer. You'll need to either M-x load-library RET studly RET first, or add (require 'studly) to your .emacs if you want to use this. Sure to be a winner for LaTeX fans! :-) If you want to fnord overload the NSA's email scanners (Just what do you mean by paranoid?) by randomly including hot words like Waco, Texas cryptographic Delta Force strategic Panama Rule Psix security quiche colonel SDI jihad spy AK-47 Treasury terrorist then try M-x spook. If you prefer to use your own phrase file, then create a /usr/local/share/emacs/20.3/etc/bruce.lines with null-terminated strings (use C-q C-@ to insert a NUL), and run M-x bruce. For instance, if you believe there are CDA scanners that you want to trigger, then you could fill this data file with George Carlin's latest list and let 'er rip. On the other hand, if you're a fan of the CDA, then you may be concerned your children discovering the existance of the sex(6) manpage installed in /usr/local/share/emacs/20.3/etc/sex.6 without your supervision. In this case, you'll want to add (require 'meese) to your site-init.el file. Finally, what distraction suite would be complete without the traditional move-snake-eat-points game? If you're into that sort of thing, try M-x snake sometime. Well, I hope I haven't brought FreeBSD development to its knees now by introducing all these games. I don't think it's coincidence that everybody who has ported Quake to FreeBSD has been too distracted to make a port of it. > Emacs has also had the ability to embed viruses in documents for far > longer than M$-Word has been around - but the defaults are somewhat > more sensible and there don't seem to be as many virii floating > around. I haven't seen any, have you? The fact that it actually *shows* you the code before asking for confirmation probably helps, as well as the fact that anybody can see it in the document. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org 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 Jun 6 9:56:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9128D1548A for ; Sun, 6 Jun 1999 09:56:26 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id SAA27889; Sun, 6 Jun 1999 18:56:23 +0200 (CEST) (envelope-from des) To: Wilko Bulte Cc: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Subject: Re: sgmlformat & making release References: <199906060952.LAA37793@yedi.iaf.nl> From: Dag-Erling Smorgrav Date: 06 Jun 1999 18:56:23 +0200 In-Reply-To: Wilko Bulte's message of "Sun, 6 Jun 1999 11:52:50 +0200 (CEST)" Message-ID: Lines: 29 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte writes: > >> sgmlformat-1.7.tar.gz doesn't seem to exist on this system. > >> Attempting to fetch from > http://fallout.campusview.indiana.edu/ports/distfiles/. > fetch: reading reply from fallout.campusview.indiana.edu: Operation timed > out > >> Attempting to fetch from > ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/. > fetch: ftp.freebsd.org: Host name lookup failure > >> Couldn't fetch it - please try to retrieve this > >> port manually into /usr/ports/distfiles/ and try again. > *** Error code 1 > > Stop. > *** Error code 1 > The build is running in a chroot tree which does not have a valid /etc/resolv.conf. > yedi#ls /usr/ports/distfiles > docbk241.tar.Z isoENTS.zip linuxdoc-1.1.tar.gz > docbk30.tar.Z jade-1.2.1.tar.gz sgmlformat-1.7.tar.gz This is outside the chroot tree. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 12:13:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Hydro.CAM.ORG (Hydro.CAM.ORG [198.168.100.7]) by hub.freebsd.org (Postfix) with ESMTP id E1509150F5 for ; Sun, 6 Jun 1999 12:13:08 -0700 (PDT) (envelope-from intmktg@CAM.ORG) Received: from Ocean.CAM.ORG (Ocean.CAM.ORG [198.168.100.5]) by Hydro.CAM.ORG (8.8.8/8.8.4) with ESMTP id PAA17954 for ; Sun, 6 Jun 1999 15:13:01 -0400 (EDT) Date: Sun, 6 Jun 1999 15:13:07 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: a.out behavior 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 following code should obviously segfault: #include #include char buffer[4028]; void main() { int i; for (i=0; i<=4028; i++) buffer[i]='A'; syslog(LOG_ERR, buffer); } Now here's the problem: When compiling with "gcc file.c", the program segfaults. When compiling with "gcc -o file file.c", the program doesn't segfault. Both files are nevertheless identical, apart from the name of the temporary object file name which could be made the same (search for cc00, perhaps). I'm using freebsd 2.2.5, gcc 2.7.2.1. Someone please let me know what's so special about a.out. Thanks in advance, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 12:18:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (Postfix) with ESMTP id 03B32150F5 for ; Sun, 6 Jun 1999 12:18:46 -0700 (PDT) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id MAA01459; Sun, 6 Jun 1999 12:25:04 -0700 (PDT) (envelope-from marcs@znep.com) Date: Sun, 6 Jun 1999 12:25:04 -0700 (PDT) From: Marc Slemko To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: a.out behavior 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, 6 Jun 1999, Marc Tardif wrote: > The following code should obviously segfault: Nope. There is no requirement that code segfault. C does not make any promises that accessing memory that you have not allocated will do anything. > #include > #include > > char buffer[4028]; > > void main() { > int i; > for (i=0; i<=4028; i++) > buffer[i]='A'; > syslog(LOG_ERR, buffer); > } > > Now here's the problem: > When compiling with "gcc file.c", the program segfaults. > When compiling with "gcc -o file file.c", the program doesn't segfault. Try renaming a.out to file. You will probably find it is due to the length of the filename, since ARGV[0] is used by syslog. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 12:55:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from laser.1sourcesolutions.com (1sourcesolutions.com [209.63.182.72]) by hub.freebsd.org (Postfix) with ESMTP id CD93B14F25 for ; Sun, 6 Jun 1999 12:55:31 -0700 (PDT) (envelope-from ecotechusa@yahoo.com) Received: from alserrenu (1SSPRES [195.105.15.8]) by laser.1sourcesolutions.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id LGM288N8; Sun, 6 Jun 1999 12:42:56 -0700 To: freebsd-hackers@FreeBSD.ORG From: "Ecotech Technologies, L.L.C." Date: Sun, 6 Jun 99 12:50:36 -0700 Subject: International Business Opportunities X-Mailer: WM - alserrenu Message-Id: <19990606195531.CD93B14F25@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ECOTECH TECHNOLOGIES, L.L.C. 4001 E., Broadway Road, Suite 7, Phoenix, AZ 85040, USA Tel: (602) 437 8000, Fax: (602) 437 4033 E-mail: ecotechusa@yahoo.com http://www.ecotechindia.com Dear Sir, Sub: Your Partner for Development of International Business Ecotech Technologies, L.L.C., Phoenix, USA is a subsidiary of principal company Ecotech Marketing who has been established for 7 years in International Business Development and committed to promote cleaner technologies and projects. It promotes technologies, projects, products and equipments/machinery. Our business network covers India, Oman, UAE and Egypt. To promote your products we developed a team of professionals. The team is unique mix of technical and commercial personnel from various institutes and industries. Whether you are interested in licensing your technology or looking for establishing a joint venture or your own subsidiary or offering a turnkey project, we can provide you complete services from concept to implementation level. We provide services like market research and opportunity assessment study, feasibility study, project analysis, statutory services and supervision of implementation of project. We have been trying to promote more and more sustainable and eco-friendly technologies and we are committed to it. India is one of the fastest growing and largest economy, a democratic country with very optimistic program to implement sustainable manufacturing projects and one of the leading countries who has implemented largest number of projects. You have a concept, technology or product, and we have the professional experiences to take you to international. Sincerely Bimal Das To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 14:24:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E53E614FD6 for ; Sun, 6 Jun 1999 14:24:43 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA72019 for ; Sun, 6 Jun 1999 17:24:41 -0400 (EDT) Date: Sun, 6 Jun 1999 17:24:41 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.org Subject: problem for the VM gurus 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 In the long-standing tradition of deadlocks, I present to you all a new one. This one locks in getblk, and causes other processes to lock in inode. It's easy to induce, but I have no idea how I'd go about fixing it myself (being very new to that part of the kernel.) Here's the program which induces the deadlock: #include #include #include #include #include int main(int argc, char **argv) { int psize = getpagesize() * 2; void *tmp; char name[] = "m.XXXXXX"; int fd = mkstemp(name); if (fd == -1) { perror("open"); exit(1); } tmp = mmap(NULL, psize, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); if (tmp == MAP_FAILED) { perror("mmap"); exit(1); } printf("write retval == %lld", write(fd, tmp, psize)); unlink(name); exit(0); } Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 14:36:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5839714FD6 for ; Sun, 6 Jun 1999 14:36:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA21351; Sun, 6 Jun 1999 15:36:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA01201; Sun, 6 Jun 1999 15:35:12 -0600 (MDT) Message-Id: <199906062135.PAA01201@harmony.village.org> To: Doug Ambrisko Subject: Re: PCMCIA "sio" problem with current Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 28 May 1999 09:15:41 PDT." <199905281615.JAA32866@whistle.com> References: <199905281615.JAA32866@whistle.com> Date: Sun, 06 Jun 1999 15:35:11 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905281615.JAA32866@whistle.com> Doug Ambrisko writes: : I wondering if I'm missing something here. I had PCMCIA stuff working : for a NE2000 ethernet card but not for serial ports. That is correct, at least for -current. : Does anyone have : serial ports working (ie. modems or serial cards)? I had this laptop : working with 3.1 and just upgraded it to current and the serial port : stopped working. That is expected. -current doesn't support sio yet. Work is in progress by me to rework the pccard code to clean it up and to make new style drivers work with it. Until that work is done, you are likely SOL when it comes to using new drivers. This means that sio, ata and fdc won't work. : So to me this looks like work to be done, ie. convert the pccard stuff to : call new-bus drivers or some capatibility layer needs to be done or I'm : smoking dope. Work needs to be done. That doesn't necessarily mean you aren't smoking dope, btw :-) If you are interested in helping out on the pccard rewrite, drop me a line in private mail. The latest snapshot can be found at: http://www.freebsd.org/~imp/pccard.patch.990605.gz but it hasn't been well tested and likely is non-functional for a significant number of systems. If you have a ISA based system, then the chances of it working are high. However, I've not done the SIO conversion yet, so that would be your first step... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 15:25:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id D214D150BA for ; Sun, 6 Jun 1999 15:25:22 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id HAA36050; Mon, 7 Jun 1999 07:54:16 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906062224.HAA36050@gizmo.internode.com.au> Subject: Re: allocate file blocks contiguously To: zzhang@cs.binghamton.edu (Zhihui Zhang) Date: Mon, 7 Jun 1999 07:54:16 +0930 (CST) Cc: farshid@bol.sharif.ac.ir, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Zhihui Zhang" at Jun 6, 99 10:40:01 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 Zhihui Zhang wrote: > My feeling is that if we allocate ALL the data blocks of a big file > contiguously, this will lead to "too much localization" as described in > the paper (or the book). However, this may be good for this big file if > the system buffering capability and hardware allow it (at the cost of > other files?) Maybe this is something we could get if XFS is ported: XFS's guaranteed rate I/O (partly) works by putting guaranteed-rate files on distinct positions on the disk, or different "subvolumes" in the case of GRIO on XLV logical volumes. So when preparing a filesystem you could build a logical volume out of twenty 9 Gbyte disks plus another five 9 Gbyte disks for guaranteed-rate files. [ in practice you'd probably be building such a filesystem for a specific application, though, so you'd probably really use 25 9 Gbyte disks for GRIO :-) ] You decide which subvolume a file is allocated to immediately after file creation: There's an ioctl() which can be used before the first write to a new file which sets the "please make me fast" flag. One thing that helps to make this possible is an I/O scheduler which supports prioritization. Hmm... - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 20:14:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 7B3AB14C40 for ; Sun, 6 Jun 1999 20:14:12 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990607031412.HNZM8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Sun, 6 Jun 1999 20:14:12 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id UAA10308; Sun, 6 Jun 1999 20:14:11 -0700 To: Brian Feldman Cc: hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus References: From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 06 Jun 1999 20:14:11 -0700 In-Reply-To: Brian Feldman's message of "Sun, 6 Jun 1999 17:24:41 -0400 (EDT)" Message-ID: Lines: 32 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > In the long-standing tradition of deadlocks, I present to you all > a new one. This one locks in getblk, and causes other processes to > lock in inode. It's easy to induce, but I have no idea how I'd go > about fixing it myself (being very new to that part of the > kernel.) Here's the program which induces the deadlock: I could reproduce it with 4.0-current. The stack trace was: tsleep getblk bread ffs_read ffs_getpages vnode_pager_getpages vm_fault --- slow_copyin ffs_write vn_write dofilewrite write syscall getblk finds that the buffer is marked B_BUSY and sleeps on it. But I can't figure out who marked it busy. -Arun PS: Does anyone know how to get the stack trace by pid in ddb ? I can manually type trace p_addr>. But is there an easier way ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 21:44:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id B174414BD5 for ; Sun, 6 Jun 1999 21:44:20 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA00600; Sun, 6 Jun 1999 22:44:15 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <375B4E1E.1C78700C@softweyr.com> Date: Sun, 06 Jun 1999 22:44:14 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Sedore , hackers@freebsd.org Cc: terry@whistle.com Subject: Re: Man pages for review References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Sedore wrote: > > One other thing which should be noted in the docs, or fixed in the kernel. > The aiocb struct should be bzeroed before an aio_read or aio_write because > if you happen to have garbage in the private part of the structure, the io > can be synchronous (look at the first few lines of aio_read in > src/kern/vfs_aio.c for the code). I think this is a probably a standards > violation, but have not done the legwork to find out. In any case, its a > pain in the neck until you root around in the kernel source to find out > why some io ops run synchronously... > > I'd be happy to generate a patch for the kernel code to fix this, if > desired. OK, I've added a warning to zero the iocb in the RESTRICTIONS subheading and a warning about bugs context in iocb->_aiocb_private in the BUGS subheading. Anyone reviewing these should probably refresh. I guess you're proposing bzeroing iocb->_aiocb_private near the start of aio_read and aio_write? It looks to me like this would solve the problem neatly, but since these are pretty much bare syscalls I don't know how to add this. Doing it inside the kernel seems unnecessary; this should be done in userland. A lesson on how to do so would be a great learning experience for me. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 6 23: 0:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id 0582D14FC4 for ; Sun, 6 Jun 1999 23:00:48 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id BAA63817; Mon, 7 Jun 1999 01:00:25 -0500 (EST) (envelope-from toor) Message-Id: <199906070600.BAA63817@dyson.iquest.net.> Subject: Re: problem for the VM gurus In-Reply-To: from Arun Sharma at "Jun 6, 1999 08:14:11 pm" To: adsharma@home.com (Arun Sharma) Date: Mon, 7 Jun 1999 01:00:25 -0500 (EST) Cc: green@unixhelp.org (Brian Feldman), hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Arun Sharma said: > bread > ffs_read > ffs_getpages > vnode_pager_getpages > vm_fault > --- > slow_copyin > ffs_write > vn_write > dofilewrite > write > syscall > > getblk finds that the buffer is marked B_BUSY and sleeps on it. But I > can't figure out who marked it busy. > This looks like the historical problem of doing I/O to an mmap'ed region. There are two facets to the problem: One where the I/O is to the same vn, and the other is where the I/O is to a different vn. The case where the I/O is to the same vn had a (short term) fix previously in the code, by allowing for recursive usage of a vn under certain circumstances. The problem of different vn's can be fixed by proper resource handling in vfs_bio (and perhaps other places.) (My memory isn't 100% clear on the code anymore, but you have shown alot of info with your backtrace.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 0:33:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C8DB01518D for ; Mon, 7 Jun 1999 00:33:11 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id DAA81096; Mon, 7 Jun 1999 03:33:13 -0400 (EDT) Date: Mon, 7 Jun 1999 03:33:12 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "John S. Dyson" Cc: Arun Sharma , hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus In-Reply-To: <199906070600.BAA63817@dyson.iquest.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 One of the problems that would make it sensible to do a complete rewrite of vfs_bio.c is this? Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 2:30:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freenix.no (freenix.no [195.139.70.52]) by hub.freebsd.org (Postfix) with ESMTP id 247FE14C96 for ; Mon, 7 Jun 1999 02:30:14 -0700 (PDT) (envelope-from morten@freenix.no) Received: from localhost (localhost [127.0.0.1]) by freenix.no (8.9.3/8.9.3) with SMTP id LAA05773; Mon, 7 Jun 1999 11:33:56 +0200 (CEST) Date: Mon, 7 Jun 1999 11:33:56 +0200 (CEST) From: "Morten A. Middelthon" To: Jake Burkholder Cc: hackers@FreeBSD.ORG Subject: Re: [Fwd: Good news from NVIDIA] In-Reply-To: <19990603231429.B308DCF@io.checker.org> 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 Jun 1999, Jake Burkholder wrote: > I spent most of the day recompiling X and what not. > All the patches applied cleanly, there are some rejects with MESA, > but I think that has to do with tags and comments at the beginning of > files. > > Everything compiled fine, and the module loads, now I just need to > get my hands on quake2 :) > > my video card is a RIVA 128, pci. > Seems like they've improved 2d accel quite a bit. > > Here are the steps I took: [SNIP] > Most Cool. I'd appreciate if someone with quake 2 handy could let me know > if it works... I haven't tried with Quake2 or 3 yet, but with the GL-modes in xlockmore (gears, pipes, superquadrics, moebius, etc) it went as smooth as cream when 3D-accelerated by my TNT card. -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 2:31:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 8F9CB14C96 for ; Mon, 7 Jun 1999 02:31:19 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 7546 invoked from network); 7 Jun 1999 09:31:16 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 7 Jun 1999 09:31:16 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id EAA11499; Mon, 7 Jun 1999 04:31:14 -0500 (EST) From: "John S. Dyson" Message-Id: <199906070931.EAA11499@dyson.iquest.net> Subject: Re: problem for the VM gurus In-Reply-To: from Brian Feldman at "Jun 7, 99 03:33:12 am" To: green@unixhelp.org (Brian Feldman) Date: Mon, 7 Jun 1999 04:31:14 -0500 (EST) Cc: dyson@iquest.net, adsharma@home.com, 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 > > One of the problems that would make it sensible to do a complete rewrite > of vfs_bio.c is this? > Specifically for that reason, probably not. However, if the effort was taken as an entire and encompassing effort, with the understanding of what is really happening in the code regarding policy (and there is alot more than the original vfs_bio type things), then it would certainly be best. Note that some of the policy might even be marginalized given a restructuring by eliminating the conventional struct buf's for everything except for I/O. In the case of I/O, it would be good to talk to those who work on block drivers, and collect info on what they need. The new definition could replace the struct bufs for the block I/O subsystems, but in many ways could be similar to struct bufs (for backwards compat.) In the current vfs_bio, the continual remapping is problematical, and was one of the very negative side-effects of the backwards compatibility choice. The original vfs_bio merged cache design actually (mostly) eliminated the struct bufs for the buffer cache interfacing, and the temporary mappings thrashed much less often. It would also be good to design in the ability to use physical addressing (for those architectures that don't incur significant additional cost for physically mapping all of memory.) Along with proper design, the fully mapped physical memory would eliminate the need for remapping entirely. Uiomove in this case wouldn't need virtually mapped I/O buffers, and this would be ideal. However, it is unlikely that X86 machines would ever support this option. PPC's, RXXXX(X) and Alpha can support mapping all of memory by their various means though. In a sense, the deadlock issue is an example of the initially unforseen problems when hacking on that part of the code. I suggest a carefully orchestrated and organized migration towards the more efficient and perhaps architecturally cleaner approach. The deadlock was an after the fact bug that we found very early on, and there was a "temporary" fix for part of it, and a mitigation of the other part. Issues like that can be very, very nasty to deal with. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 4: 4:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id EC73E14DA6 for ; Mon, 7 Jun 1999 04:04:30 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id GAA64050; Mon, 7 Jun 1999 06:04:26 -0500 (EST) (envelope-from toor) Message-Id: <199906071104.GAA64050@dyson.iquest.net.> Subject: Re: problem for the VM gurus In-Reply-To: from Brian Feldman at "Jun 6, 1999 05:24:41 pm" To: green@unixhelp.org (Brian Feldman) Date: Mon, 7 Jun 1999 06:04:26 -0500 (EST) Cc: hackers@FreeBSD.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Brian Feldman said: > In the long-standing tradition of deadlocks, I present to you all a new one. > This one locks in getblk, and causes other processes to lock in inode. It's > easy to induce, but I have no idea how I'd go about fixing it myself > (being very new to that part of the kernel.) > Here's the program which induces the deadlock: > > > tmp = mmap(NULL, psize, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); > if (tmp == MAP_FAILED) { > perror("mmap"); > exit(1); > } > printf("write retval == %lld", write(fd, tmp, psize)); > I responded earlier to a reply to this message :-). This did work about the time that I left, and it appears that it is likely that code has been removed that mitigated this as a problem. It is important to either modify the way that read or write operations occur (perhaps prefault before letting the uiomove operation occur (yuck, and it also still doesn't close all windows), or reinstate the handling of recursive operations on a vnode by the same process.) Handling the vnode locking in a more sophistcated way would be better, but reinstating (or fixing) the already existant code that used to handle this would be a good fix that will mitigate the problem for now. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 5: 7:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.axis.de (hermes.axis.de [194.163.241.7]) by hub.freebsd.org (Postfix) with SMTP id 1AEC115179 for ; Mon, 7 Jun 1999 05:07:33 -0700 (PDT) (envelope-from maret@axis.de) Received: from erlangen01.axis.de by hermes.axis.de via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 7 Jun 1999 12:07:34 UT Received: (private information removed) Message-ID: <91DA20EC3C3DD211833400A0245A4EA9BA0EB6@erlangen01.axis.de> From: Alexander Maret To: freebsd-hackers@FreeBSD.ORG Subject: Strange kernel messages Date: Mon, 7 Jun 1999 14:07:32 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I got the following kernel messages. Does anybody know what caused this messages? Is this the first sign of upcoming problems? Jun 5 21:05:01 mail /kernel: 128 v_inactive_target R *Handler Int Jun 5 21:05:01 mail /kernel: 129 v_inactive_count R *Handler Int Jun 5 21:05:01 mail /kernel: 130 v_cache_count R *Handler Int Jun 5 21:05:01 mail /kernel: 131 v_cache_min R *Handler Int Jun 5 21:05:01 mail /kernel: 132 v_cache_max R *Handler Int Jun 5 21:05:01 mail /kernel: 133 v_pageout_free_min R *Handler Int Jun 5 21:05:01 mail /kernel: 134 v_interrupt_free_min R *Handler Int Jun 5 21:05:02 mail /kernel: 102 misc RW Node Jun 5 21:05:02 mail /kernel: 100 zero_page_count R *Handler Int Jun 5 21:05:02 mail /kernel: 101 cnt_prezero R *Handler Int Jun 5 21:05:02 mail /kernel: 114 pageout_stats_max RW *Handler Int Jun 5 21:05:02 mail /kernel: 115 pageout_full_stats_interval RW *Handler Int Jun 5 21:05:02 mail /kernel: 116 pageout_stats_interval RW *Handler Int Jun 5 21:05:02 mail /kernel: 117 pageout_stats_free_max RW *Handler Int Jun 5 21:05:02 mail /kernel: 118 swap_idle_enabled RW *Handler Int Jun 5 21:05:02 mail /kernel: 119 defer_swapspace_pageouts RW *Handler Int Jun 5 21:05:02 mail /kernel: 120 disable_swapspace_pageouts RW *Handler Int Jun 5 21:05:02 mail /kernel: 121 max_page_launder RW *Handler Int Jun 5 21:05:02 mail /kernel: 122 zone R *Handler String Jun 5 21:05:02 mail /kernel: 123 zone_kmem_pages R *Handler Int Jun 5 21:05:02 mail /kernel: 124 zone_kmem_kvaspace R *Handler Int Jun 5 21:05:02 mail /kernel: 125 zone_kern_pages R *Handler Int Jun 5 21:05:02 mail /kernel: 3 vfs RW Node Jun 5 21:05:02 mail /kernel: 0 generic R *Handler Node Jun 5 21:05:02 mail /kernel: 100 numdirtybuffers R *Handler Int Jun 5 21:05:02 mail /kernel: 101 lodirtybuffers RW *Handler Int Jun 5 21:05:02 mail /kernel: 10 Jun 5 21:05:02 mail /kernel: 2 hidirtybuffers RW *Handler Int Jun 5 21:05:02 mail /kernel: 103 numfreebuffers R *Handler Int Jun 5 21:05:02 mail /kernel: 104 lofreebuffers RW *Handler Int Jun 5 21:05:02 mail /kernel: 105 hifreebuffers RW *Handler Int Jun 5 21:05:02 mail /kernel: 106 maxbufspace RW *Handler Int Jun 5 21:05:02 mail /kernel: 107 bufspace R *Handler Int Jun 5 21:05:02 mail /kernel: 108 maxvmiobufspace RW *Handler Int Jun 5 21:05:02 mail /kernel: 109 vmiospace R *Handler Int Jun 5 21:05:02 mail /kernel: 110 maxmallocbufspace RW *Handler Int Jun 5 21:05:02 mail /kernel: 111 bufmallocspace R *Handler Int Jun 5 21:05:02 mail /kernel: 112 kvafreespace R *Handler Int Jun 5 21:05:02 mail /kernel: 113 cache RW Node Jun 5 21:05:02 mail /kernel: 100 numneg R *Handler Int Jun 5 21:05:02 mail /kernel: 101 numcache R *Handler Int Jun 5 21:05:02 mail /kernel: 102 numcalls R *Handler Int Jun 5 21:05:02 mail /kernel: 103 dothits R *Handler Int Jun 5 21:05:02 mail /kernel: 104 dotdothits R *Handler Int Jun 5 21:05:02 mail /kernel: 105 numchecks R *Handler Int Jun 5 21:05:02 mail /kernel: 106 nummiss R *Handler Int Jun 5 21:05:02 mail /kernel: 107 nummisszap R *Handler Int Jun 5 21:05:02 mail /kernel: 108 numposzaps R *Handler Int Jun 5 21:05:02 mail /kernel: 109 numposhits R *Handler Int Jun 5 21:05:02 mail /kernel: 110 numnegzaps R *Handler Int Jun 5 21:05:02 mail /kernel: 111 numneghits R *Handler Int Jun 5 21:05:02 mail /kernel: 112 numcwdcalls R *Handler Int Jun 5 21:05:03 mail /kernel: 113 numcwdfail1 R *Handler Int Jun 5 21:05:03 mail /kernel: 114 numcwdfail2 R *Handler Int Jun 5 21:05:03 mail /kernel: 115 numcwdfail3 R *Handler Int Jun 5 21:05:03 mail /kernel: 116 numcwdfail4 R *Handler Int Jun 5 21:05:03 mail /kernel: 117 numcwdfound R *Handl Jun 5 21:05:03 mail /kernel: er Int Jun 5 21:05:03 mail /kernel: 114 mod0 R *Handler Int Jun 5 21:05:03 mail /kernel: 115 mod1 R *Handler Int Jun 5 21:05:03 mail /kernel: 116 usermount RW *Handler Int Jun 5 21:05:03 mail /kernel: 117 aio RW Node Jun 5 21:05:03 mail /kernel: 100 max_aio_per_proc RW *Handler Int Jun 5 21:05:03 mail /kernel: 101 max_aio_queue_per_proc RW *Handler Int Jun 5 21:05:03 mail /kernel: 102 max_aio_procs RW *Handler Int Jun 5 21:05:03 mail /kernel: 103 num_aio_procs R *Handler Int Jun 5 21:05:03 mail /kernel: 104 num_queue_count R *Handler Int Jun 5 21:05:03 mail /kernel: 105 max_aio_queue RW *Handler Int Jun 5 21:05:03 mail /kernel: 106 target_aio_procs RW *Handler Int Jun 5 21:05:03 mail /kernel: 107 max_buf_aio RW *Handler Int Jun 5 21:05:03 mail /kernel: 108 num_buf_aio R *Handler Int Jun 5 21:05:03 mail /kernel: 109 aiod_lifetime RW *Handler Int Jun 5 21:05:03 mail /kernel: 110 aiod_timeout RW *Handler Int Jun 5 21:05:03 mail /kernel: 118 ffs RW Node Jun 5 21:05:03 mail /kernel: 3 doreallocblks RW *Handler Int Jun 5 21:05:03 mail /kernel: 4 doasyncfree RW *Handler Int Jun 5 21:05:03 mail /kernel: 4 net RW Node Jun 5 21:05:03 mail /kernel: 1 local RW Node Jun 5 21:05:03 mail /kernel: 1 stream RW Node Jun 5 21:05:03 mail /kernel: 100 sendspace RW *Handler Int Jun 5 21:05:03 mail /kernel: 101 recvspace RW *Handler Int Jun 5 21:05:03 mail /kernel: 102 pcblist R *Handler Jun 5 21:05:03 mail /kernel: 2 dgram RW Node Jun 5 21:05:03 mail /kernel: 100 maxdgram RW *Handler Int Jun 5 21:05:03 mail /kernel: 101 recvspace RW *Handler Int Jun 5 21:05:03 mail /kernel: 102 pcblist R *Handler Jun 5 21:05:03 mail /kernel: 102 inflight R *Handler Int Jun 5 21:05:03 mail /kernel: 2 inet RW Node Jun 5 21:05:03 mail /kernel: 0 ip RW Node Jun 5 21:05:03 mail /kernel: 0 portrange RW Node Jun 5 21:05:04 mail /kernel: 100 lowfirst RW * Jun 5 21:05:04 mail /kernel: Handler Int Jun 5 21:05:04 mail /kernel: 101 lowlast RW *Handler Int Jun 5 21:05:04 mail /kernel: 102 first RW *Handler Int Jun 5 21:05:04 mail /kernel: 103 last RW *Handler Int Jun 5 21:05:04 mail /kernel: 104 hifirst RW *Handler Int Jun 5 21:05:04 mail /kernel: 105 hilast RW *Handler Int Jun 5 21:05:04 mail /kernel: 1 forwarding RW *Handler Int Jun 5 21:05:04 mail /kernel: 2 redirect RW *Handler Int Jun 5 21:05:04 mail /kernel: 3 ttl RW *Handler Int Jun 5 21:05:04 mail /kernel: 5 rtexpire RW *Handler Int Jun 5 21:05:04 mail /kernel: 6 rtminexpire RW *Handler Int Jun 5 21:05:04 mail /kernel: 7 rtmaxcache RW *Handler Int Jun 5 21:05:04 mail /kernel: 8 sourceroute RW *Handler Int Jun 5 21:05:04 mail /kernel: 10 intr_queue_maxlen R *Handler Int Jun 5 21:05:04 mail /kernel: 11 intr_queue_drops R *Handler Int Jun 5 21:05:04 mail /kernel: 12 stats R *Handler Opaque/struct Jun 5 21:05:04 mail /kernel: 13 accept_sourceroute RW *Handler Int Jun 5 21:05:04 mail /kernel: 14 fastforwarding RW *Handler Int Jun 5 21:05:04 mail /kernel: 114 subnets_are_local RW *Handler Int Jun 5 21:05:04 mail /kernel: 1 icmp RW Node Jun 5 21:05:04 mail /kernel: 1 maskrepl RW *Handler Int Jun 5 21:05:04 mail /kernel: 2 stats R *Handler Opaque/struct Jun 5 21:05:04 mail /kernel: 3 icmplim R *Handler Int Jun 5 21:05:04 mail /kernel: 103 bmcastecho RW *Handler Int Jun 5 21:05:04 mail /kernel: 2 igmp RW Node Jun 5 21:05:04 mail /kernel: 1 stats R *Handler Opaque/struct Jun 5 21:05:04 mail /kernel: 6 tcp RW Node Jun 5 21:05:04 mail /kernel: 1 rfc1323 RW *Handler Int Jun 5 21:05:04 mail /kernel: 2 rfc1644 RW *Handler Int Jun 5 21:05:04 mail /kernel: 3 mssdflt RW *Handler Int Jun 5 21:05:04 mail /kernel: 4 stats Jun 5 21:05:04 mail /kernel: R *Handler Opaque/struct Jun 5 21:05:04 mail /kernel: 5 rttdflt RW *Handler Int Jun 5 21:05:04 mail /kernel: 6 keepidle RW *Handler Int Jun 5 21:05:04 mail /kernel: 7 keepintvl RW *Handler Int Jun 5 21:05:04 mail /kernel: 8 sendspace RW *Handler Int Jun 5 21:05:04 mail /kernel: 9 recvspace RW *Handler Int Jun 5 21:05:05 mail /kernel: 10 keepinit RW *Handler Int Jun 5 21:05:05 mail /kernel: 11 pcblist R *Handler Jun 5 21:05:05 mail /kernel: 111 log_in_vain RW *Handler Int Jun 5 21:05:05 mail /kernel: 112 delayed_ack RW *Handler Int Jun 5 21:05:05 mail /kernel: 113 pcbcount R *Handler Int Jun 5 21:05:05 mail /kernel: 114 always_keepalive RW *Handler Int Jun 5 21:05:05 mail /kernel: 17 udp RW Node Jun 5 21:05:05 mail /kernel: 1 checksum RW *Handler Int Jun 5 21:05:05 mail /kernel: 2 stats R *Handler Opaque/struct Jun 5 21:05:05 mail /kernel: 3 maxdgram RW *Handler Int Jun 5 21:05:05 mail /kernel: 4 recvspace RW *Handler Int Jun 5 21:05:05 mail /kernel: 5 pcblist R *Handler Jun 5 21:05:05 mail /kernel: 105 log_in_vain RW *Handler Int Jun 5 21:05:05 mail /kernel: 255 raw RW Node Jun 5 21:05:05 mail /kernel: 100 maxdgram RW *Handler Int Jun 5 21:05:05 mail /kernel: 101 recvspace RW *Handler Int Jun 5 21:05:05 mail /kernel: 102 pcblist R *Handler Jun 5 21:05:05 mail /kernel: 17 routetable R *Handler Node Jun 5 21:05:05 mail /kernel: 18 link RW Node Jun 5 21:05:05 mail /kernel: 0 generic RW Node Jun 5 21:05:05 mail /kernel: 1 system RW Node Jun 5 21:05:05 mail /kernel: 1 ifcount R *Handler Int Jun 5 21:05:05 mail /kernel: 2 ifdata RW *Handler Node Jun 5 21:05:05 mail /kernel: 6 ether RW Node Jun 5 21:05:05 mail /kernel: 2 inet RW Node Jun 5 21:05:05 mail /kernel: 100 prune_intvl RW *Handler Int Jun 5 21:05:05 mail /kernel: 101 max_age RW Jun 5 21:05:05 mail /kernel: *Handler Int Jun 5 21:05:05 mail /kernel: 102 host_down_time RW *Handler Int Jun 5 21:05:05 mail /kernel: 103 maxtries RW *Handler Int Jun 5 21:05:05 mail /kernel: 104 useloopback RW *Handler Int Jun 5 21:05:05 mail /kernel: 105 proxyall RW *Handler Int Jun 5 21:05:05 mail /kernel: 5 debug RW Node Jun 5 21:05:05 mail /kernel: 100 elf_trace RW *Handler Int Jun 5 21:05:05 mail /kernel: 101 fdexpand R *Handler Int Jun 5 21:05:05 mail /kernel: 102 ttydebug RW *Handler Int Jun 5 21:05:05 mail /kernel: 103 nchash R *Handler Int Jun 5 21:05:05 mail /kernel: 104 ncnegfactor RW *Handler Int Jun 5 21:05:05 mail /kernel: 105 numneg R *Handler Int Jun 5 21:05:05 mail /kernel: 106 numcache R *Handler Int Jun 5 21:05:05 mail /kernel: 107 vfscache RW *Handler Int Jun 5 21:05:05 mail /kernel: 108 vnsize R *Handler Int Jun 5 21:05:05 mail /kernel: 109 ncsize R *Handler Int Jun 5 21:05:05 mail /kernel: 110 numvnodes R *Handler Int Jun 5 21:05:05 mail /kernel: 111 wantfreevnodes RW *Handler Int Jun 5 21:05:06 mail /kernel: 112 freevnodes R *Handler Int Jun 5 21:05:06 mail /kernel: 113 disablecwd RW *Handler Int Jun 5 21:05:06 mail /kernel: 114 tsc_timecounter R *Handler Opaque/struct Jun 5 21:05:06 mail /kernel: 115 i8254_timecounter R *Handler Opaque/struct Jun 5 21:05:06 mail /kernel: 6 hw RW Node Jun 5 21:05:06 mail /kernel: 1 machine R *Handler String Jun 5 21:05:06 mail /kernel: 2 model R *Handler String Jun 5 21:05:06 mail /kernel: 3 ncpu R *Handler Int Jun 5 21:05:06 mail /kernel: 4 byteorder R *Handler Int Jun 5 21:05:06 mail /kernel: 5 physmem R *Handler Int Jun 5 21:05:06 mail /kernel: 6 usermem R *Handler Int Jun 5 21:05:06 mail /kernel: 7 pagesize R *Handler Int Jun 5 21:05:06 mail /kernel: 10 floatingpoint R *Handler Int Jun 5 21:05:06 mail /kernel: 11 machine_arch R *Handler String Jun 5 21:05:06 mail /kernel: 111 availpa Jun 5 21:05:06 mail /kernel: ges R *Handler Int Jun 5 21:05:06 mail /kernel: 7 machdep RW Node Jun 5 21:05:06 mail /kernel: 1 consdev R *Handler Opaque/struct Jun 5 21:05:06 mail /kernel: 2 adjkerntz RW *Handler Int Jun 5 21:05:06 mail /kernel: 3 disable_rtc_set RW *Handler Int Jun 5 21:05:06 mail /kernel: 4 bootinfo R *Handler Opaque/struct Jun 5 21:05:06 mail /kernel: 5 wall_cmos_clock RW *Handler Int Jun 5 21:05:06 mail /kernel: 105 do_dump RW *Handler Int Jun 5 21:05:06 mail /kernel: 106 ispc98 R *Handler Int Jun 5 21:05:06 mail /kernel: 107 msgbuf R *Handler String Jun 5 21:05:06 mail /kernel: 108 msgbuf_clear RW *Handler Int Jun 5 21:05:06 mail /kernel: 109 uc_devlist R *Handler Jun 5 21:05:06 mail /kernel: 110 i8254_freq RW *Handler Int Jun 5 21:05:06 mail /kernel: 111 tsc_freq RW *Handler Int Jun 5 21:05:06 mail /kernel: 112 conspeed RW *Handler Int Jun 5 21:05:06 mail /kernel: 8 user RW Node Jun 5 21:05:06 mail /kernel: 1 cs_path R *Handler String Jun 5 21:05:06 mail /kernel: 2 bc_base_max R *Handler Int Jun 5 21:05:06 mail /kernel: 3 bc_dim_max R *Handler Int Jun 5 21:05:06 mail /kernel: 4 bc_scale_max R *Handler Int Jun 5 21:05:06 mail /kernel: 5 bc_string_max R *Handler Int Jun 5 21:05:06 mail /kernel: 6 coll_weights_max R *Handler Int Jun 5 21:05:06 mail /kernel: 7 expr_nest_max R *Handler Int Jun 5 21:05:06 mail /kernel: 8 line_max R *Handler Int Jun 5 21:05:06 mail /kernel: 9 re_dup_max R *Handler Int Jun 5 21:05:06 mail /kernel: 10 posix2_version R *Handler Int Jun 5 21:05:06 mail /kernel: 11 posix2_c_bind R *Handler Int Jun 5 21:05:06 mail /kernel: 12 posix2_c_dev R *Handler Int Jun 5 21:05:06 mail /kernel: 13 posix2_char_term R *Handler Int Jun 5 21:05:06 mail /kernel: 14 posix2_fort_dev R *Handler Int Jun 5 21:05:07 mail /kernel: 15 posix2_fort_run R *Handler Int Jun 5 21:05:07 mail /kernel: 16 posix2_localedef R *Handle Jun 5 21:05:07 mail /kernel: r Int Jun 5 21:05:07 mail /kernel: 17 posix2_sw_dev R *Handler Int Jun 5 21:05:07 mail /kernel: 18 posix2_upe R *Handler Int Jun 5 21:05:07 mail /kernel: 19 stream_max R *Handler Int Jun 5 21:05:07 mail /kernel: 20 tzname_max R *Handler Int Jun 5 21:05:07 mail /kernel: 9 p1003_1b RW Node Jun 5 21:05:07 mail /kernel: 1 asynchronous_io R *Handler Int Jun 5 21:05:07 mail /kernel: 2 mapped_files R *Handler Int Jun 5 21:05:07 mail /kernel: 3 memlock R *Handler Int Jun 5 21:05:07 mail /kernel: 4 memlock_range R *Handler Int Jun 5 21:05:07 mail /kernel: 5 memory_protection R *Handler Int Jun 5 21:05:07 mail /kernel: 6 message_passing R *Handler Int Jun 5 21:05:07 mail /kernel: 7 prioritized_io R *Handler Int Jun 5 21:05:07 mail /kernel: 8 priority_scheduling R *Handler Int Jun 5 21:05:07 mail /kernel: 9 realtime_signals R *Handler Int Jun 5 21:05:07 mail /kernel: 10 semaphores R *Handler Int Jun 5 21:05:07 mail /kernel: 11 fsync R *Handler Int Jun 5 21:05:07 mail /kernel: 12 shared_memory_objects R *Handler Int Jun 5 21:05:07 mail /kernel: 13 synchronized_io R *Handler Int Jun 5 21:05:07 mail /kernel: 14 timers R *Handler Int Jun 5 21:05:07 mail /kernel: 15 aio_listio_max R *Handler Int Jun 5 21:05:07 mail /kernel: 16 aio_max R *Handler Int Jun 5 21:05:07 mail /kernel: 17 aio_prio_delta_max R *Handler Int Jun 5 21:05:07 mail /kernel: 18 delaytimer_max R *Handler Int Jun 5 21:05:07 mail /kernel: 19 mq_open_max R *Handler Int Jun 5 21:05:07 mail /kernel: 20 pagesize R *Handler Int Jun 5 21:05:07 mail /kernel: 21 rtsig_max R *Handler Int Jun 5 21:05:07 mail /kernel: 22 sem_nsems_max R *Handler Int Jun 5 21:05:07 mail /kernel: 23 sem_value_max R *Handler Int Jun 5 21:05:07 mail /kernel: 24 sigqueue_max R *Handler Int Jun 5 21:05:07 mail /kernel: 25 timer_max R *Handler Int Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 6:22:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bbs.kitel.co.kr (bbs.kitel.co.kr [210.102.35.84]) by hub.freebsd.org (Postfix) with ESMTP id 0D64E14BD7 for ; Mon, 7 Jun 1999 06:22:15 -0700 (PDT) (envelope-from swjeong@bbs.kitel.co.kr) Received: (from swjeong@localhost) by bbs.kitel.co.kr (8.9.1/8.9.1) id WAA17370 for freebsd-hackers@FreeBSD.ORG; Mon, 7 Jun 1999 22:26:08 +0900 (KST) (envelope-from swjeong) Date: Mon, 7 Jun 1999 22:26:08 +0900 (KST) From: swjeong Message-Id: <199906071326.WAA17370@bbs.kitel.co.kr> To: freebsd-hackers@FreeBSD.ORG Subject: panic at FIONREAD ioctl() may be due to syscall() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using FreeBSD-3.1-RELEASE I met panic. Panic occured at FIONREAD ioctl(). I found it was called at rdchk() at rbsb.c in lrzsz 0.12.16 packages. Before panic, there was kernel warning message --- "b_to_q to a clist with no reserved cblocks". Is it related ? Following is gdb output for core dump. --------- gdb output -------- # gdb -k /sys/compile/MYRI.19990430 vmcore.4 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 3792896 initial pcb at 2e598c panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5480345f fault code = supervisor read, page not present instruction pointer = 0x8:0xf016d01d stack pointer = 0x10:0xfd69bec4 frame pointer = 0x10:0xfd69bf60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 69172 (IMP-lsz-0.12.16) interrupt mask = panic: from debugger panic: from debugger dumping to dev 20401, offset 1572864 dump 256 255 254 253 252 251 250 249 248 ... 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xf016209d in panic (fmt=0xf0277128 "from debugger") at ../../kern/kern_shutdown.c:446 #2 0xf012b3c5 in db_panic (addr=-266940387, have_addr=0, count=1, modif=0xfd69bd48 "") at ../../ddb/db_command.c:432 #3 0xf012b365 in db_command (last_cmdp=0xf02b3920, cmd_table=0xf02b3780, aux_cmd_tablep=0xf02e317c) at ../../ddb/db_command.c:332 #4 0xf012b42a in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf012d77b in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xf023f55e in kdb_trap (type=12, code=0, regs=0xfd69be88) at ../../i386/i386/db_interface.c:157 #7 0xf02497d8 in trap_fatal (frame=0xfd69be88, eva=1417688159) at ../../i386/i386/trap.c:937 #8 0xf02494b7 in trap_pfault (frame=0xfd69be88, usermode=0, eva=1417688159) at ../../i386/i386/trap.c:835 #9 0xf02490ea in trap (frame={tf_es = -31850480, tf_ds = -43843568, tf_edi = 4, tf_esi = -238539008, tf_ebp = -43401376, tf_isp = -43401552, tf_ebx = -238632704, tf_edx = 0, tf_ecx = 1074030207, tf_eax = -238658276, tf_trapno = 12, tf_err = 0, tf_eip = -266940387, tf_cs = 8, tf_eflags = 66050, tf_esp = -43804224, tf_ss = -265588232}) at ../../i386/i386/trap.c:437 #10 0xf016d01d in ioctl (p=0xfd6399c0, uap=0xfd69bf94) at ../../kern/sys_generic.c:445 #11 0xf0249a47 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639696, tf_esi = 84992, tf_ebp = -272642208, tf_isp = -43401244, tf_ebx = 105, tf_edx = 85380, tf_ecx = 38099, tf_eax = 54, tf_trapno = 7, tf_err = 7, tf_eip = 537363601, tf_cs = 31, tf_eflags = 646, tf_esp = -272642224, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #12 0x20078491 in ?? () #13 0x7193 in ?? () #14 0x69f7 in ?? () #15 0x49bd in ?? () #16 0x4450 in ?? () #17 0x3afe in ?? () #18 0x38f8 in ?? () #19 0x1095 in ?? () (kgdb) up 10 #10 0xf016d01d in ioctl (p=0xfd6399c0, uap=0xfd69bf94) at ../../kern/sys_generic.c:445 445 } else if ((com&IOC_OUT) && size) (kgdb) l ioctl 389 /* ARGSUSED */ 390 int 391 ioctl(p, uap) 392 struct proc *p; 393 register struct ioctl_args *uap; 394 { 395 register struct file *fp; 396 register struct filedesc *fdp; 397 register u_long com; 398 int error; (kgdb) p *uap $1 = {Segmentation fault (core dumped) (kgdb) up #11 0xf0249a47 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639696, tf_esi = 84992, tf_ebp = -272642208, tf_isp = -43401244, tf_ebx = 105, tf_edx = 85380, tf_ecx = 38099, tf_eax = 54, tf_trapno = 7, tf_err = 7, tf_eip = 537363601, tf_cs = 31, tf_eflags = 646, tf_esp = -272642224, tf_ss = 39}) at ../../i386/i386/trap.c:1100 1100 error = (*callp->sy_call)(p, args); (kgdb) l syscall ... 1032 void 1033 syscall(frame) 1034 struct trapframe frame; 1035 { 1036 caddr_t params; 1037 int i; ... 1083 if (params && (i = callp->sy_narg * sizeof(int)) && 1084 (error = copyin(params, (caddr_t)args, (u_int)i))) { ... 1089 goto bad; (kgdb) l 1090 } .... 1095 p->p_retval[0] = 0; 1096 p->p_retval[1] = frame.tf_edx; 1097 1098 STOPEVENT(p, S_SCE, callp->sy_narg); 1099 (kgdb) l 1100 error = (*callp->sy_call)(p, args); 1101 ... (kgdb) i No symbol "i" in current context. (kgdb) ---------- end of gdb output --------- What's the reason of the panic ? VM problem ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 6:50: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (Postfix) with ESMTP id E162B14D3D for ; Mon, 7 Jun 1999 06:50:00 -0700 (PDT) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.3/8.9.3) id JAA12852; Mon, 7 Jun 1999 09:46:08 -0400 (EDT) (envelope-from dervish) Date: Mon, 7 Jun 1999 09:46:08 -0400 From: bush doctor To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: Re: Extra text modes via vidcontrol... Message-ID: <19990607094608.A12741@bantu.cl.msu.edu> References: <199906020524.OAA17278@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906020524.OAA17278@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Wed, Jun 02, 1999 at 02:24:17PM +0900 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51 8F A9 AC 3C B4 74 F3 BA WWW-Home-Page: http://www.msu.edu/~ikhala Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Kazutaka YOKOTA (yokota@zodiac.mech.utsunomiya-u.ac.jp): [snip, snip] > Are you sure you enabled "options VM86" in the kernel configuration > file and loaded the vesa module by the boot loader? Hmmm ... When I added "options VM86" to my kernel config file I get: su-2.02# config BANTU BANTU:135: unknown option "VM86" Unknown option used - it is VERY important that you do make clean && make depend before recompiling Kernel build directory is ../../compile/BANTU bantu.cl.msu.edu:dervish> uname -a FreeBSD bantu.cl.msu.edu 4.0-CURRENT FreeBSD 4.0-CURRENT #19: Thu Jun 3 13:54:15 EDT 1999 root@bantu.cl.msu.edu:/usr/src/sys/compile/BANTU i386 I did get splash screen to work with the default 320x200 bmp files ... The files I'm working with are from http://advocacy.freebsd.org/ammunition/splash.html #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 7:45:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 425A8156A4 for ; Mon, 7 Jun 1999 07:45:28 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:ec8+2/E7OH+8Tu3d/c4Oixypc4kIucUA@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA13411; Mon, 7 Jun 1999 23:45:09 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA29492; Mon, 7 Jun 1999 23:49:00 +0900 (JST) Message-Id: <199906071449.XAA29492@zodiac.mech.utsunomiya-u.ac.jp> To: bush doctor Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Extra text modes via vidcontrol... In-reply-to: Your message of "Mon, 07 Jun 1999 09:46:08 -0400." <19990607094608.A12741@bantu.cl.msu.edu> References: <199906020524.OAA17278@zodiac.mech.utsunomiya-u.ac.jp> <19990607094608.A12741@bantu.cl.msu.edu> Date: Mon, 07 Jun 1999 23:48:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Are you sure you enabled "options VM86" in the kernel configuration >> file and loaded the vesa module by the boot loader? >Hmmm ... >When I added "options VM86" to my kernel config file I get: > >su-2.02# config BANTU >BANTU:135: unknown option "VM86" >Unknown option used - it is VERY important that you do > make clean && make depend > before recompiling > Kernel build directory is ../../compile/BANTU Umm, this means that your source tree is not as current as it should be, in order to be called "4.0-CURRENT". The VM86 option was added to the -CURRENT branch long before 3.0-RELEASE! How are you updating your source tree in /usr/src? >bantu.cl.msu.edu:dervish> uname -a >FreeBSD bantu.cl.msu.edu 4.0-CURRENT FreeBSD 4.0-CURRENT #19: Thu Jun 3 13:54 >:15 EDT 1999 root@bantu.cl.msu.edu:/usr/src/sys/compile/BANTU i386 > >I did get splash screen to work with the default 320x200 bmp files ... >The files I'm working with are from > http://advocacy.freebsd.org/ammunition/splash.html Good! Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 8: 2:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from niseko.junichi.org (niseko.junichi.org [210.238.191.91]) by hub.freebsd.org (Postfix) with ESMTP id 7E01B1506A for ; Mon, 7 Jun 1999 08:02:10 -0700 (PDT) (envelope-from junichi@junichi.org) Received: from norn.junichi.org (norn.pn.junichi.org [192.168.31.2]) by niseko.junichi.org (8.9.2+3.1W/3.7W-MQH-3.0) with ESMTP id AAA18443; Tue, 8 Jun 1999 00:02:02 +0900 (JST) Received: (from junichi@localhost) by norn.junichi.org (8.9.3/3.7W-client1.0) id AAA00351; Tue, 8 Jun 1999 00:02:02 +0900 (JST) Date: Tue, 8 Jun 1999 00:02:02 +0900 (JST) Message-Id: <199906071502.AAA00351@norn.junichi.org> To: jedgar@fxp.org Cc: hackers@freebsd.org, junichi@junichi.org Subject: Re: wfd.c and ATAPI Zip In-Reply-To: Your message of "Sun, 6 Jun 1999 22:35:02 JST". From: junichi@junichi.org (Junichi Satoh) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> My thoughts now are: >> 1) My two drive are somewhat 'rogue' in that they don't conform to the >> driver's expectations. >> 2) When the driver was written, the '!strcmp' should be 'strcmp' since >> strcmp returns 0 when equal (-1 or 1 when < or >), in which case my patch >> makes sense: >> >> --- /sys/i386/isa/wfd.c.orig Thu Feb 18 17:06:08 1999 >> +++ /sys/i386/isa/wfd.c Tue Jun 6 08:59:59 1999 >> @@ -247,7 +247,7 @@ >> * is known to lock up if transfers > 64 blocks are >> * requested. >> */ >> - if (!strcmp(ap->model, "IOMEGA ZIP 100 ATAPI")) { >> + if (strcmp(ap->model, "IOMEGA ZIP 100 ATAPI")) { >> printf("wfd%d: buggy Zip drive, 64-block transfer limit >> set\n", >> t->lun); >> t->maxblks = 64; >> >> 3) I've just plain lost it :) >> >> Can anyone else with an ATAPI Zip Drive confirm this? Hmm... I have an ATAPI ZIP drive: ======================================================================== wdc0: unit 1 (atapi): , removable, intr, iordis wfd1: medium type unknown (no disk) wfd1: buggy Zip drive, 64-block transfer limit set ======================================================================== It does not work with your patch. It's a buggy drive. Probably, using only strcmp() is not enough. We shoud distinguish buggy or not using revision number. #I don't know how many revisions are available. :-) --- Junichi Satoh junichi@junichi.org junichi@jp.FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 8:19:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5FD0A15046 for ; Mon, 7 Jun 1999 08:19:26 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id RAA34633; Mon, 7 Jun 1999 17:19:21 +0200 (CEST) (envelope-from des) To: Kazutaka YOKOTA Cc: bush doctor , freebsd-hackers@FreeBSD.ORG Subject: Re: Extra text modes via vidcontrol... References: <199906020524.OAA17278@zodiac.mech.utsunomiya-u.ac.jp> <19990607094608.A12741@bantu.cl.msu.edu> <199906071449.XAA29492@zodiac.mech.utsunomiya-u.ac.jp> From: Dag-Erling Smorgrav Date: 07 Jun 1999 17:19:21 +0200 In-Reply-To: Kazutaka YOKOTA's message of "Mon, 07 Jun 1999 23:48:59 +0900" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA writes: > >su-2.02# config BANTU > >BANTU:135: unknown option "VM86" > >Unknown option used - it is VERY important that you do > > make clean && make depend > > before recompiling > > Kernel build directory is ../../compile/BANTU > > Umm, this means that your source tree is not as current as it should > be, in order to be called "4.0-CURRENT". The VM86 option was added to > the -CURRENT branch long before 3.0-RELEASE! How are you updating > your source tree in /usr/src? VM86 is no longer an option. Remove it, and everything will be fine. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 8:20: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with SMTP id BA3FC15781 for ; Mon, 7 Jun 1999 08:19:58 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: (qmail 10735 invoked by uid 1003); 7 Jun 1999 15:19:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jun 1999 15:19:55 -0000 Date: Mon, 7 Jun 1999 11:19:55 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Junichi Satoh Cc: hackers@freebsd.org Subject: Re: wfd.c and ATAPI Zip In-Reply-To: <199906071502.AAA00351@norn.junichi.org> 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, 8 Jun 1999, Junichi Satoh wrote: > Hmm... > > I have an ATAPI ZIP drive: > ======================================================================== > wdc0: unit 1 (atapi): , removable, intr, iordis > wfd1: medium type unknown (no disk) > wfd1: buggy Zip drive, 64-block transfer limit set > ======================================================================== > > It does not work with your patch. It's a buggy drive. > > Probably, using only strcmp() is not enough. > We shoud distinguish buggy or not using revision number. > > #I don't know how many revisions are available. :-) > --- > Junichi Satoh junichi@junichi.org > junichi@jp.FreeBSD.ORG > 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. Since the current method of sorting out the revisions doesn't seem to be perfect, would it be acceptible to consider them all buggy unless known not to be (i.e. compare ap->revision instead of ap->model)? ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 8:45:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (Postfix) with ESMTP id C63CA15298 for ; Mon, 7 Jun 1999 08:44:48 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id RAA18350 for ; Mon, 7 Jun 1999 17:44:43 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.2/8.6.9) id RAA17029 for hackers@freebsd.org; Mon, 7 Jun 1999 17:44:50 +0200 (CEST) Date: Mon, 7 Jun 1999 17:44:50 +0200 (CEST) From: Christoph Kukulies Message-Id: <199906071544.RAA17029@gil.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: egcs - kernel? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the status of the EGCS compiler WRT kernel build? (And world build in general?) -- 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 Jun 7 8:49:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 08E4C14EEC for ; Mon, 7 Jun 1999 08:49:26 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip94.houston22.tx.pub-ip.psi.net [38.31.97.94]) by leap.innerx.net (Postfix) with ESMTP id 7299637088; Mon, 7 Jun 1999 11:49:19 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id KAA78423; Mon, 7 Jun 1999 10:48:23 -0500 (CDT) (envelope-from chris) Date: Mon, 7 Jun 1999 10:48:15 -0500 From: Chris Costello To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: egcs - kernel? Message-ID: <19990607104815.K57174@holly.dyndns.org> Reply-To: chris@calldei.com References: <199906071544.RAA17029@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199906071544.RAA17029@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Mon, Jun 07, 1999 at 05:44:50PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 7, 1999, Christoph Kukulies wrote: > What is the status of the EGCS compiler WRT kernel build? > (And world build in general?) It's been working great for ages in -CURRENT. I don't know how it may handle in -STABLE, though. -- Chris Costello It said, "Insert disk #3," but only two will fit! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 8:52: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (Postfix) with ESMTP id 426DB14C02 for ; Mon, 7 Jun 1999 08:51:58 -0700 (PDT) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.3/8.9.3) id LAA13169 for hackers@freebsd.org; Mon, 7 Jun 1999 11:48:09 -0400 (EDT) (envelope-from dervish) Date: Mon, 7 Jun 1999 11:48:09 -0400 From: bush doctor To: hackers@freebsd.org Subject: Re: Extra text modes via vidcontrol... Message-ID: <19990607114809.E12741@bantu.cl.msu.edu> References: <199906020524.OAA17278@zodiac.mech.utsunomiya-u.ac.jp> <19990607094608.A12741@bantu.cl.msu.edu> <199906071449.XAA29492@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dag-Erling Smorgrav on Mon, Jun 07, 1999 at 05:19:21PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51 8F A9 AC 3C B4 74 F3 BA WWW-Home-Page: http://www.msu.edu/~ikhala Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Dag-Erling Smorgrav (des@flood.ping.uio.no): > Kazutaka YOKOTA writes: > > >su-2.02# config BANTU > > >BANTU:135: unknown option "VM86" > > >Unknown option used - it is VERY important that you do > > > make clean && make depend > > > before recompiling > > > Kernel build directory is ../../compile/BANTU > > > > Umm, this means that your source tree is not as current as it should > > be, in order to be called "4.0-CURRENT". The VM86 option was added to > > the -CURRENT branch long before 3.0-RELEASE! How are you updating > > your source tree in /usr/src? > > VM86 is no longer an option. Remove it, and everything will be fine. Noted. thanxs ... > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 8:58:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (Postfix) with ESMTP id 55CB814DB8 for ; Mon, 7 Jun 1999 08:58:43 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id RAA19624 for ; Mon, 7 Jun 1999 17:58:41 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.2/8.6.9) id RAA17138 for hackers@freebsd.org; Mon, 7 Jun 1999 17:58:47 +0200 (CEST) Date: Mon, 7 Jun 1999 17:58:47 +0200 (CEST) From: Christoph Kukulies Message-Id: <199906071558.RAA17138@gil.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: linux and freebsd kernels conceptually different? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could one say that Linux vs. FreeBSD kernels are conceptually different what task scheduling, queueing, interrupt handling, driver architecture, buffer caching, vm etc. is concerned? -- 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 Jun 7 9: 0:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 3B61614D04 for ; Mon, 7 Jun 1999 09:00:51 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id BAA09552; Tue, 8 Jun 1999 01:00:44 +0900 (JST) Date: Tue, 8 Jun 1999 01:00:44 +0900 (JST) Message-Id: <199906071600.BAA09552@afs.ntc.mita.keio.ac.jp> To: junker@jazz.snu.ac.kr, foxfair@news.ks.edu.tw, freebsd-hackers@FreeBSD.org Cc: hosokawa@itc.keio.ac.jp Subject: Multilingual Installer for 3.2-RELEASE (Re: pccard boot.flp...) In-Reply-To: Your message of "Sun, 6 Jun 1999 14:53:03 JST". <199906060553.OAA24289@afs.ntc.mita.keio.ac.jp> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199906060553.OAA24289@afs.ntc.mita.keio.ac.jp> I wrote, >> Thank you. Now I'm working on updated sysinstall messages. >> I'll send the URL of message.lt_EN, *.TXT, *.hlp files to translate >> when I finished this work. >> I want translators to other languages. I finished updating indices of messages, and complied the first public test version. Currently, following binary package is compiled with English, Japanese and Korean support. As a result of increased size of boot.flp, Japanese and Korean support is now merged again into the same boot.flp image. http://wing-yee.ntc.keio.ac.jp/hosokawa/32flp/floppies-19990608.tar.gz (Compiled boot.flp, kern.flp, and mfsroot.flp binaries) http://wing-yee.ntc.keio.ac.jp/hosokawa/32flp/release-19990608.tar.gz (Patched source tree of /usr/src/release) http://wing-yee.ntc.keio.ac.jp/hosokawa/32flp/translation-kit-19990608.tar.gz (All you have to translate is this tarball) Current Translation Status: ------------------------------------------------------------------- Japanese Korean ------------------------------------------------------------------- sysinstall messages: almost okay NG help files: NG almost okay ------------------------------------------------------------------- -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 9:12: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with SMTP id 0E55E157C1 for ; Mon, 7 Jun 1999 09:10:44 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: (qmail 10903 invoked by uid 1003); 7 Jun 1999 16:10:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jun 1999 16:10:44 -0000 Date: Mon, 7 Jun 1999 12:10:44 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Junichi Satoh Cc: hackers@freebsd.org Subject: Re: wfd.c and ATAPI Zip In-Reply-To: <199906071502.AAA00351@norn.junichi.org> 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 Here is a patch that checks for the revision numbers instead of simply the inquiry string (and adds my buggy revision): --- wfd.c.orig Thu Feb 18 17:06:08 1999 +++ wfd.c Mon Jun 7 12:02:25 1999 @@ -243,17 +243,21 @@ return -1; /* - * The IOMEGA ZIP 100, at firmware 21.* and 23.* at least + * The IOMEGA ZIP 100, at firmware 12.A, 21.* and 23.* at least * is known to lock up if transfers > 64 blocks are * requested. */ - if (!strcmp(ap->model, "IOMEGA ZIP 100 ATAPI")) { - printf("wfd%d: buggy Zip drive, 64-block transfer limit set\n", - t->lun); - t->maxblks = 64; - } else { - t->maxblks = 0; /* no limit */ - } + + if (!strncmp(ap->model, "IOMEGA ZIP 100 ATAPI", 27)) + if ((!strncmp(ap->revision, "12", 2)) || + (!strncmp(ap->revision, "21", 2)) || + (!strncmp(ap->revision, "23", 2))) { + printf("wfd%d: buggy Zip drive, 64-block transfer limit set\n", + t->lun); + t->maxblks = 64; + } else { + t->maxblks = 0; /* no limit */ + } ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 9:16:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (Postfix) with SMTP id C687215061 for ; Mon, 7 Jun 1999 09:16:07 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id LAA02306; Mon, 7 Jun 1999 11:17:50 -0500 Received: from stlabcexg006.anheuser-busch.com(unknown 151.145.101.161) by gatewaya via smap (V2.1) id xma002265; Mon, 7 Jun 99 11:17:36 -0500 Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.2448.0) id ; Mon, 7 Jun 1999 11:15:09 -0500 Message-ID: From: "Alton, Matthew" To: "'Christoph Kukulies'" , hackers@freebsd.org Subject: RE: linux and freebsd kernels conceptually different? Date: Mon, 7 Jun 1999 11:14:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, quite. > -----Original Message----- > From: Christoph Kukulies [SMTP:kuku@gilberto.physik.RWTH-Aachen.DE] > Sent: Monday, June 07, 1999 10:59 AM > To: hackers@freebsd.org > Subject: linux and freebsd kernels conceptually different? > > Could one say that Linux vs. FreeBSD kernels are conceptually > different what task scheduling, queueing, interrupt handling, > driver architecture, buffer caching, vm etc. is concerned? > > -- > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 9:23:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tofu.alt.net (tofu.alt.net [207.14.113.2]) by hub.freebsd.org (Postfix) with ESMTP id 21A2014E10 for ; Mon, 7 Jun 1999 09:23:30 -0700 (PDT) (envelope-from abourov@alt.net) Received: from comp3.addr.com ([209.152.191.146]) by tofu.alt.net (8.9.3/8.8.5) with ESMTP id JAA18862 for ; Mon, 7 Jun 1999 09:23:28 -0700 (PDT) Message-Id: <4.2.0.56.19990607091352.030eb820@mail.addr.com> X-Sender: abourov@mail.alt.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Mon, 07 Jun 1999 09:22:58 -0700 To: hackers@FreeBSD.org From: Anthony Bourov Subject: Q: xl0: no memory for rx list -- packet dropped! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am running a FreeBSD server, and I am running into this problem very often. The machine stops responding and instead outputs 1000s of xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! messages. The machine is usually pulling about 4-5 megabits but there is usually a traffic spike right before this happens so an attack is not out of the question, but I was wondering if there was any way I can raise the threshold for this (would more BUFFERs do the trick?). Thanks in advance, Anthony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 9:56:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 2E9D614CC9 for ; Mon, 7 Jun 1999 09:56:28 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id BAA10124; Tue, 8 Jun 1999 01:55:50 +0900 (JST) Date: Tue, 8 Jun 1999 01:55:50 +0900 (JST) Message-Id: <199906071655.BAA10124@afs.ntc.mita.keio.ac.jp> To: junker@jazz.snu.ac.kr, foxfair@news.ks.edu.tw Cc: freebsd-hackers@FreeBSD.org, hosokawa@itc.keio.ac.jp Subject: Re: Multilingual Installer for 3.2-RELEASE (Re: pccard boot.flp...) In-Reply-To: Your message of "Tue, 8 Jun 1999 01:00:44 JST". <199906071600.BAA09552@afs.ntc.mita.keio.ac.jp> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199906071600.BAA09552@afs.ntc.mita.keio.ac.jp> hosokawa@itc.keio.ac.jp writes: >> Currently, following binary package is compiled with English, Japanese >> and Korean support. As a result of increased size of boot.flp, >> Japanese and Korean support is now merged again into the same boot.flp >> image. I recieved translated Japanese document files just after I sent last mail. I recompiled these files again and replaced with the old ones. >> http://wing-yee.ntc.keio.ac.jp/hosokawa/32flp/floppies-19990608.tar.gz >> (Compiled boot.flp, kern.flp, and mfsroot.flp binaries) >> >> http://wing-yee.ntc.keio.ac.jp/hosokawa/32flp/release-19990608.tar.gz >> (Patched source tree of /usr/src/release) >> >> http://wing-yee.ntc.keio.ac.jp/hosokawa/32flp/translation-kit-19990608.tar.gz >> (All you have to translate is this tarball) >> >> Current Translation Status: >> ------------------------------------------------------------------- >> Japanese Korean >> ------------------------------------------------------------------- >> sysinstall messages: almost okay NG >> help files: NG almost okay >> ------------------------------------------------------------------- Now, the Current Translation Status is: ------------------------------------------------------------------- Japanese Korean ------------------------------------------------------------------- sysinstall messages: almost okay NG help files: almost okay almost okay ------------------------------------------------------------------- -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 10:54:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mobil.surnet.ru (mobil.surnet.ru [195.54.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 0016514BDC for ; Mon, 7 Jun 1999 10:54:10 -0700 (PDT) (envelope-from ilia@cgilh.chel.su) Received: (from uucgilh@localhost) by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id XAA23199 for hackers@FreeBSD.ORG; Mon, 7 Jun 1999 23:54:20 +0600 (UDT) Received: (from uucp@localhost) by cgilh.chel.su (8.8.7/8.8.7) with UUCP id XAA00968 for hackers@FreeBSD.ORG; Mon, 7 Jun 1999 23:21:29 +0600 Received: from localhost (ilia@localhost) by localhost.cgu.chel.su (8.9.2/8.9.2) with ESMTP id XAA00620 for ; Mon, 7 Jun 1999 23:21:35 +0600 (ESS) (envelope-from ilia@cgilh.chel.su) X-Authentication-Warning: localhost.cgu.chel.su: ilia owned process doing -bs Date: Mon, 7 Jun 1999 23:21:35 +0600 (ESS) From: Ilia Chipitsine X-Sender: ilia@localhost.cgu.chel.su To: hackers@FreeBSD.ORG Subject: question about Pacific Sierra HPF In-Reply-To: <4.2.0.56.19990607091352.030eb820@mail.addr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, anybody here knows what is it about ? /usr/home/ilia/test-hpf > hpf hello.f90 Pacific-Sierra Research VAST-HPF V5.1C 23:17:54 6/ 7/99 HPF program hello /home/ilia/fortran-cd/vast/vhpf_linux/lib//libvhpf_pvm.a(envnproc.o): In function `envnproc_': envnproc.o(.text+0xe2): undefined reference to `__ctype_b' collect2: ld returned 1 exit status /usr/home/ilia/test-hpf > Regards, (îÁÉÌÕÞÛÉÅ ÐÏÖÅÌÁÎÉÑ) Ilia Chipitsine (éÌØÑ ûÉÐÉÃÉÎ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 11: 1:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 60824157B7 for ; Mon, 7 Jun 1999 11:01:01 -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 OAA18098; Mon, 7 Jun 1999 14:00:53 -0400 From: Bill Paul Message-Id: <199906071800.OAA18098@skynet.ctr.columbia.edu> Subject: Re: Q: xl0: no memory for rx list -- packet dropped! To: abourov@alt.net (Anthony Bourov) Date: Mon, 7 Jun 1999 14:00:50 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <4.2.0.56.19990607091352.030eb820@mail.addr.com> from "Anthony Bourov" at Jun 7, 99 09:22:58 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2443 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, Anthony Bourov had to walk into mine and say: > Hi, > > I am running a FreeBSD server, and I am running into this problem very > often. The machine stops responding and instead outputs 1000s of > xl0: no memory for rx list -- packet dropped! > xl0: no memory for rx list -- packet dropped! > xl0: no memory for rx list -- packet dropped! > xl0: no memory for rx list -- packet dropped! > messages. The machine is usually pulling about 4-5 megabits but there is > usually a traffic spike right before this happens so an attack is not out > of the question, but I was wondering if there was any way I can raise the > threshold for this (would more BUFFERs do the trick?). You don't say what version of FreeBSD this is, or what driver version you have. Sorry, but my mind reading helmet is in the shop this week. If you're running something older than 3.2-RELEASE, try the latest driver from http://www.freebsd.org/~wpaul/3Com. The newer version has a larger RX and TX ring sizes. If you are running 3.2-RELEASE or later or changing the ring sizes doesn't help, then try compiling a new kernel with a larger value for NMBCLUSTERS, i.e.: options "NMBCLUSTERS=20000" Actually, for newer versions of FreeBSD, you may have to do: options NMBCLUSTERS="20000" If config(8) complains about the first syntax, try the second. This will greatly increase the size of the mbuf cluster pool, which should at least hold off the starvation condition for a while longer. You might want to check the traffic on the line with tcpdump. I would look for lots of ICMP or UDP traffic, or maybe lots of TCP segments directed at ports where there's nothing listening. Note: each mbuf cluster is 2K in size. 20000 * 2048 == 40MB of RAM, so you better have a lot of memory in this server. If not, try something smaller. -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 Jun 7 11:44:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 8186014BCF for ; Mon, 7 Jun 1999 11:44:33 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id OAA12367 for ; Mon, 7 Jun 1999 14:33:07 -0400 Date: Mon, 7 Jun 1999 14:33:07 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: help with I/O optimization with object 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 While studying the file ufs_readwrite.c, I see routines like uiomoveco() that calls vm_uiomove() in vm_map.c. I am almost sure that these are new in FreeBSD 3.x. The comment in ffs_read() says "not a VM based I/O requests" == "not headed for the buffer cache". This does not make sense to me although I understand something about VMIO buffers and non-VMIO buffers. I hope someone can explain the basic ideas of I/O optimization with VM object (relating to the OBJ_OPT flag and the global variable vfs_ioopt) so that I can understand the code easier. Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 11:54:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (unknown [209.179.127.11]) by hub.freebsd.org (Postfix) with ESMTP id 4B62C14C57 for ; Mon, 7 Jun 1999 11:54:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.conference.usenix.org [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00571; Mon, 7 Jun 1999 11:51:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906071851.LAA00571@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Chris D. Faulhaber" Cc: Junichi Satoh , hackers@freebsd.org Subject: Re: wfd.c and ATAPI Zip In-reply-to: Your message of "Mon, 07 Jun 1999 11:19:55 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Jun 1999 11:51:43 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 8 Jun 1999, Junichi Satoh wrote: > > > Hmm... > > > > I have an ATAPI ZIP drive: > > ======================================================================== > > wdc0: unit 1 (atapi): , removable, intr, iordis > > wfd1: medium type unknown (no disk) > > wfd1: buggy Zip drive, 64-block transfer limit set > > ======================================================================== > > > > It does not work with your patch. It's a buggy drive. > > > > Probably, using only strcmp() is not enough. > > We shoud distinguish buggy or not using revision number. > > > > #I don't know how many revisions are available. :-) > > --- > > Junichi Satoh junichi@junichi.org > > junichi@jp.FreeBSD.ORG > > > > 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. > Since the current method of sorting out the revisions doesn't seem to > be perfect, would it be acceptible to consider them all buggy unless known > not to be (i.e. compare ap->revision instead of ap->model)? Uh, that's what the code does; if it's a Zip drive, it's considered to be buggy regardless of revision. If the string compare isn't matching a drive in the field, it means that Iomega have changed the string and we need to know what the new drives are calling themselves. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Jun 7 12: 4:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with SMTP id A65C5157E1 for ; Mon, 7 Jun 1999 12:04:38 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: (qmail 15531 invoked by uid 1003); 7 Jun 1999 19:04:33 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jun 1999 19:04:33 -0000 Date: Mon, 7 Jun 1999 15:04:33 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Mike Smith Cc: Junichi Satoh , hackers@freebsd.org Subject: Re: wfd.c and ATAPI Zip In-Reply-To: <199906071851.LAA00571@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 Mon, 7 Jun 1999, Mike Smith wrote: > > 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. > > Since the current method of sorting out the revisions doesn't seem to > > be perfect, would it be acceptible to consider them all buggy unless known > > not to be (i.e. compare ap->revision instead of ap->model)? > > Uh, that's what the code does; if it's a Zip drive, it's considered to > be buggy regardless of revision. If the string compare isn't matching > a drive in the field, it means that Iomega have changed the string and > we need to know what the new drives are calling themselves. > I have an off-brand (NEC) Zip Drive with: which does have buggy firmware; I also have another one with: that has no problem when I remove the 64 block limitation. In this case, I would use strncmp instead of strcmp to test the first 27 characters. So what you are saying is that we are limiting all Zip drives instead of being based solely on firmware revision? Any reason for that? ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 12:21: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id EA4D5157A1 for ; Mon, 7 Jun 1999 12:20:57 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990607192056.NKJJ8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Mon, 7 Jun 1999 12:20:56 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id MAA12933; Mon, 7 Jun 1999 12:20:56 -0700 To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: linux and freebsd kernels conceptually different? References: <199906071558.RAA17138@gil.physik.rwth-aachen.de> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 07 Jun 1999 12:20:56 -0700 In-Reply-To: Christoph Kukulies's message of "Mon, 7 Jun 1999 17:58:47 +0200 (CEST)" Message-ID: Lines: 52 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Kukulies writes: Comments from someone who's studied Linux for a while and has started studying FreeBSD only recently. > Could one say that Linux vs. FreeBSD kernels are conceptually > different what task scheduling, queueing, interrupt handling, > driver architecture, buffer caching, vm etc. is concerned? - task scheduling - Linux uses a linear linked list of runnable processes and recalculates priorities on every reschedule. - FreeBSD uses multilevel runqueues - Buffer caching - Linux hasn't achieved the perfect integration between the page cache and the buffer cache yet. write(2) goes through the buffer cache, read(2) goes through the page cache. Also, buffers are cached based on basis. But an IOlite style buffer caching scheme is in the works. - FreeBSD seems to avoid data replication by a better integration of the page and buffer caches. Also, buffers are cached based on basis - VM - Linux uses a 3 level page table as a generic data structure at the low level and data structures similar to SVR4 for high level mapping info. Also, Linux avoids chaining of ptes mapping the same data completely. - FreeBSD separates machine dependent and independent data using the pmap abstraction. FreeBSD also uses pv_table to keep track of multiple ptes mapping same data. FreeBSD VM is based on Mach. But for the most part, they are based on the same principles documented in early UNIX internals text books. So it would be unfair to say they are conceptually very different. I'd say most of the differences are in implementation and development methodology. Linux camp seems to be proud of breaking traditions and concepts invented after lengthy research. I haven't seen that many iconoclasts in my short encounter with FreeBSD. Hope that helps, -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 12:32:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (unknown [209.179.127.11]) by hub.freebsd.org (Postfix) with ESMTP id 99D39152FF for ; Mon, 7 Jun 1999 12:32:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.conference.usenix.org [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01207; Mon, 7 Jun 1999 12:28:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906071928.MAA01207@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Chris D. Faulhaber" Cc: Mike Smith , Junichi Satoh , hackers@freebsd.org Subject: Re: wfd.c and ATAPI Zip In-reply-to: Your message of "Mon, 07 Jun 1999 15:04:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Jun 1999 12:28:54 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 7 Jun 1999, Mike Smith wrote: > > > > 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. > > > Since the current method of sorting out the revisions doesn't seem to > > > be perfect, would it be acceptible to consider them all buggy unless known > > > not to be (i.e. compare ap->revision instead of ap->model)? > > > > Uh, that's what the code does; if it's a Zip drive, it's considered to > > be buggy regardless of revision. If the string compare isn't matching > > a drive in the field, it means that Iomega have changed the string and > > we need to know what the new drives are calling themselves. > > > > I have an off-brand (NEC) Zip Drive with: > > which does have buggy firmware; I also have another one with: > > that has no problem when I remove the 64 block limitation. > > In this case, I would use strncmp instead of strcmp to test the first 27 > characters. Gotcha, and that's definitely a good idea. > So what you are saying is that we are limiting all Zip drives instead of > being based solely on firmware revision? Any reason for that? No evidence suggesting that any revision ever worked or would work; the simplest and safest technique is just to cap transfers at 32k - in reality it doesn't affect performance at all, so there's no real need to be extra-picky. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Jun 7 12:32:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8D0E6157CC for ; Mon, 7 Jun 1999 12:32:23 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA06379; Mon, 7 Jun 1999 21:31:34 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906071931.VAA06379@freebsd.dk> Subject: Re: wfd.c and ATAPI Zip In-Reply-To: from "Chris D. Faulhaber" at "Jun 7, 1999 3: 4:33 pm" To: jedgar@fxp.org (Chris D. Faulhaber) Date: Mon, 7 Jun 1999 21:31:34 +0200 (CEST) Cc: mike@smith.net.au, junichi@junichi.org, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 It seems Chris D. Faulhaber wrote: > > I have an off-brand (NEC) Zip Drive with: > > which does have buggy firmware; I also have another one with: > > that has no problem when I remove the 64 block limitation. > > In this case, I would use strncmp instead of strcmp to test the first 27 > characters. > > So what you are saying is that we are limiting all Zip drives instead of > being based solely on firmware revision? Any reason for that? Hmm, well in the atapi-fd driver in the new ata/atapi system I only check for !strncmp(atp->atapi_parm->model, "IOMEGA ZIP", 11) which is even more pessimistic. However the overhead added here is small compared to the general speed of the ZIP drive, so its not a problem. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 12:34:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 1D53A15919 for ; Mon, 7 Jun 1999 12:34:24 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id OAA05502 for ; Mon, 7 Jun 1999 14:58:24 -0500 (EST) Date: Mon, 7 Jun 1999 14:58:23 -0500 (EST) From: Alfred Perlstein To: hackers@freebsd.org Subject: netiso tree (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 -Alfred ---------- Forwarded message ---------- Date: Mon, 07 Jun 1999 15:23:57 -0400 From: Spud Taylor To: freebsd-questions@FreeBSD.ORG Subject: netiso tree We have been using Free BSD and BSDI since 1992. There was a descision to eliminate the netiso and netccitt trees in the OS a few years ago. Can these trees still be obtained and where can I obtain them from? I am having a problem reading raw CLNP PDUs because of the way BSD used to do it vs the way it is done now with the isopcbhead and isopcblist. If you could point me in the correct difre4ction, I would appreciate it. We have done extensive kernel programming and are familiar with what it will take to port a netiso tree into our current environment. Thank you for your time and I look forward to hearing an answer from you. Lynn Taylor Senior Engineer Planning Systems Inc McLean, Va. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" 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 Jun 7 12:59:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hydrogen.fircrest.net (metriclient-3.uoregon.edu [128.223.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 224A114C57 for ; Mon, 7 Jun 1999 12:59:23 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id MAA11534; Mon, 7 Jun 1999 12:58:54 -0700 (PDT) Message-ID: <19990607125854.22870@hydrogen.nike.efn.org> Date: Mon, 7 Jun 1999 12:58:54 -0700 From: John-Mark Gurney To: Alfred Perlstein , Spud Taylor Cc: hackers@FreeBSD.ORG Subject: Re: netiso tree (fwd) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Alfred Perlstein on Mon, Jun 07, 1999 at 02:58:23PM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein scribbled this message on Jun 7: > ---------- Forwarded message ---------- > Date: Mon, 07 Jun 1999 15:23:57 -0400 > From: Spud Taylor > To: freebsd-questions@FreeBSD.ORG > Subject: netiso tree > > We have been using Free BSD and BSDI since 1992. There was a descision > to eliminate the netiso and netccitt trees in the OS a few years ago. > Can these trees still be obtained and where can I obtain them from? I > am having a problem reading raw CLNP PDUs because of the way BSD used > to do it vs the way it is done now with the isopcbhead and isopcblist. > If you could point me in the correct difre4ction, I would appreciate it. > We have done extensive kernel programming and are familiar with what it > will take to port a netiso tree into our current environment. Thank > you for your time and I look forward to hearing an answer from you. take a look at cvsup'ing the RELENG_2_1_7_RELEASE brach of the FreeBSD kernel to obtain this code... it looks like that was the last branch that the code was on... or if you can get your hands on the kernel source dist from 2.1.7-R they should have it.. -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 14: 6:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0F4D014E1E for ; Mon, 7 Jun 1999 14:06:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA29567; Mon, 7 Jun 1999 14:06:23 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 Jun 1999 14:06:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199906072106.OAA29567@apollo.backplane.com> To: Brian Feldman Cc: hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... what version of the operating system? -Matt : In the long-standing tradition of deadlocks, I present to you all a new one. :This one locks in getblk, and causes other processes to lock in inode. It's :easy to induce, but I have no idea how I'd go about fixing it myself :(being very new to that part of the kernel.) : Here's the program which induces the deadlock: : :#include :#include :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 14:16:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fionn.sports.gov.uk (bh-cw30-176.pool.dircon.co.uk [194.112.51.176]) by hub.freebsd.org (Postfix) with ESMTP id F22B715827 for ; Mon, 7 Jun 1999 14:15:56 -0700 (PDT) (envelope-from ad@fionn.sports.gov.uk) Received: from localhost ([127.0.0.1]) by fionn.sports.gov.uk with esmtp (Exim 2.12 #1) id 10r6kH-00005t-00; Mon, 7 Jun 1999 21:15:49 +0000 Date: Mon, 7 Jun 1999 21:15:49 +0000 (GMT) From: Andy Doran X-Sender: ad@vmunix.psn.ie To: ornery_101@yahoo.com Cc: hackers@freebsd.org Subject: Re: netiso tree (fwd) 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 'netiso' and 'netccitt' trees are still included in NetBSD. - ad On Mon, 7 Jun 1999, Alfred Perlstein wrote: > ---------- Forwarded message ---------- > Date: Mon, 07 Jun 1999 15:23:57 -0400 > From: Spud Taylor > To: freebsd-questions@FreeBSD.ORG > Subject: netiso tree > > We have been using Free BSD and BSDI since 1992. There was a descision > to eliminate the netiso and netccitt trees in the OS a few years ago. > Can these trees still be obtained and where can I obtain them from? I > am having a problem reading raw CLNP PDUs because of the way BSD used > to do it vs the way it is done now with the isopcbhead and isopcblist. > If you could point me in the correct difre4ction, I would appreciate it. > We have done extensive kernel programming and are familiar with what it > will take to port a netiso tree into our current environment. Thank > you for your time and I look forward to hearing an answer from you. > Lynn Taylor > Senior Engineer > Planning Systems Inc > McLean, Va. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > > > 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 Jun 7 14:51:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 3FC1414BCF for ; Mon, 7 Jun 1999 14:51:48 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id RAA13075 for ; Mon, 7 Jun 1999 17:40:20 -0400 Date: Mon, 7 Jun 1999 17:40:20 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@FreeBSD.ORG Subject: Re: help with I/O optimization with object 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 Mon, 7 Jun 1999, Zhihui Zhang wrote: > > While studying the file ufs_readwrite.c, I see routines like uiomoveco() > that calls vm_uiomove() in vm_map.c. I am almost sure that these are new > in FreeBSD 3.x. The comment in ffs_read() says "not a VM based I/O > requests" == "not headed for the buffer cache". This does not make sense > to me although I understand something about VMIO buffers and non-VMIO > buffers. I hope someone can explain the basic ideas of I/O optimization > with VM object (relating to the OBJ_OPT flag and the global variable > vfs_ioopt) so that I can understand the code easier. > After searching the mailing list archive for some time and tracing down who calls vm_uiomove(), it seems to me that this is the zero copy read stuff used to read data into the current process' address space. However, I do not know when it can be useful or any more details. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 15:38:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id D365514C26 for ; Mon, 7 Jun 1999 15:38:49 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id SAA95014; Mon, 7 Jun 1999 18:38:52 -0400 (EDT) Date: Mon, 7 Jun 1999 18:38:51 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus In-Reply-To: <199906072106.OAA29567@apollo.backplane.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, 7 Jun 1999, Matthew Dillon wrote: > ... what version of the operating system? > > -Matt 4.0-CURRENT > > : In the long-standing tradition of deadlocks, I present to you all a new one. > :This one locks in getblk, and causes other processes to lock in inode. It's > :easy to induce, but I have no idea how I'd go about fixing it myself > :(being very new to that part of the kernel.) > : Here's the program which induces the deadlock: > : > :#include > :#include > :... > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 15:47:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 87A7B15324 for ; Mon, 7 Jun 1999 15:47:40 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id SAA95110; Mon, 7 Jun 1999 18:43:33 -0400 (EDT) Date: Mon, 7 Jun 1999 18:43:33 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alexander Maret Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Strange kernel messages In-Reply-To: <91DA20EC3C3DD211833400A0245A4EA9BA0EB6@erlangen01.axis.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 don't know why it's there, but that seems to be the sysctl tree. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 15:58:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bbs.mpcs.com (bbs.mpcs.com [209.101.88.2]) by hub.freebsd.org (Postfix) with ESMTP id C53AB14CC5 for ; Mon, 7 Jun 1999 15:58:01 -0700 (PDT) (envelope-from hgoldste@bbs.mpcs.com) Received: (from hgoldste@localhost) by bbs.mpcs.com (8.9.3/8.9.3/MPCS spamzap) id SAA22459 for freebsd-hackers@freebsd.org; Mon, 7 Jun 1999 18:57:55 -0400 Date: Mon, 7 Jun 1999 18:57:55 -0400 From: Howard Goldstein Message-Id: <199906072257.SAA22459@bbs.mpcs.com> To: freebsd-hackers@freebsd.org Subject: Re: problem for the VM gurus Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: : On Mon, 7 Jun 1999, Matthew Dillon wrote: : > ... what version of the operating system? : 4.0-CURRENT 3.2R too... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 17:15:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from firee.ia.cp (redion.nttmcl.com [216.69.69.40]) by hub.freebsd.org (Postfix) with ESMTP id 7CC3614BF7 for ; Mon, 7 Jun 1999 17:14:49 -0700 (PDT) (envelope-from gene@nttmcl.com) Received: from localhost (gene@localhost) by firee.ia.cp (8.9.3/8.9.3) with ESMTP id RAA93600 for ; Mon, 7 Jun 1999 17:14:48 -0700 (PDT) (envelope-from gene@nttmcl.com) X-Authentication-Warning: firee.ia.cp: gene owned process doing -bs Date: Mon, 7 Jun 1999 17:14:48 -0700 (PDT) From: "Eugene M. Kim" X-Sender: gene@firee.ia.cp To: hackers@freebsd.org Subject: Session leader releasing the ctty 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 Hello, I'm having a trouble programming a special login shell, and would like to hear any opinions on this. I want this shell (which automatically becomes a session leader) to release its ctty but remain unterminated (the ctty must be taken by its child). However, there seems to be no easy way to do this; termios(4) says one must call setsid() to release its ctty, but setsid(2) says the call will fail if the caller is already a session leader. Would there be any other way for a session leader to release its ctty without terminating itself? TIA. Cheers, Eugene Kim PS. I'm now using a workaround that the shell will forward the SIGHUP that it received because it's a session leader, but this isn't a clean way. :-p -- Eugene M. Kim NTT Multimedia Communications Laboratories Software Developer 250 Cambridge Avenue, Suite 205 +1 650 833 3630 (Voice) Palo Alto, CA 94040, USA +1 650 833 3633 (Fax) mailto:gene@nttmcl.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 17:28:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 119E314C46 for ; Mon, 7 Jun 1999 17:28:03 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id RAA08522; Mon, 7 Jun 1999 17:28:02 -0700 (PDT) Date: Mon, 7 Jun 1999 17:28:01 -0700 (PDT) From: Julian Elischer To: "Eugene M. Kim" Cc: hackers@FreeBSD.ORG Subject: Re: Session leader releasing the ctty 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 you might look to see if 'screen' (in ports) has something that does this when it disconnects from a session. (just an idea) julian On Mon, 7 Jun 1999, Eugene M. Kim wrote: > Hello, > > I'm having a trouble programming a special login shell, and would like > to hear any opinions on this. > > I want this shell (which automatically becomes a session leader) to > release its ctty but remain unterminated (the ctty must be taken by its > child). However, there seems to be no easy way to do this; termios(4) > says one must call setsid() to release its ctty, but setsid(2) says the > call will fail if the caller is already a session leader. > > Would there be any other way for a session leader to release its ctty > without terminating itself? TIA. > > Cheers, > Eugene Kim > > PS. I'm now using a workaround that the shell will forward the SIGHUP > that it received because it's a session leader, but this isn't a clean > way. :-p > > -- > Eugene M. Kim NTT Multimedia Communications Laboratories > Software Developer 250 Cambridge Avenue, Suite 205 > +1 650 833 3630 (Voice) Palo Alto, CA 94040, USA > +1 650 833 3633 (Fax) mailto:gene@nttmcl.com > > > > 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 Jun 7 18:28:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bbs.kitel.co.kr (unknown [210.102.35.84]) by hub.freebsd.org (Postfix) with ESMTP id 9B09315209 for ; Mon, 7 Jun 1999 18:27:29 -0700 (PDT) (envelope-from swjeong@bbs.kitel.co.kr) Received: (from swjeong@localhost) by bbs.kitel.co.kr (8.9.1/8.9.1) id KAA08669 for hackers@FreeBSD.ORG; Tue, 8 Jun 1999 10:31:25 +0900 (KST) (envelope-from swjeong) Date: Tue, 8 Jun 1999 10:31:25 +0900 (KST) From: Jeong Sung Won Message-Id: <199906080131.KAA08669@bbs.kitel.co.kr> To: hackers@FreeBSD.ORG Subject: kernel panic maybe due to VM instability in 3.1R Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using FreeBSD-3.1-RELEASE I met panic. Panic occured at FIONREAD ioctl(). I found it was called at rdchk() at rbsb.c in lrzsz 0.12.16 packages. Before panic, there was kernel warning message --- "b_to_q to a clist with no reserved cblocks". Is it related ? Following is gdb output for core dump. --------- gdb output -------- # gdb -k /sys/compile/MYRI.19990430 vmcore.4 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 3792896 initial pcb at 2e598c panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5480345f fault code = supervisor read, page not present instruction pointer = 0x8:0xf016d01d stack pointer = 0x10:0xfd69bec4 frame pointer = 0x10:0xfd69bf60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 69172 (IMP-lsz-0.12.16) interrupt mask = panic: from debugger panic: from debugger dumping to dev 20401, offset 1572864 dump 256 255 254 253 252 251 250 249 248 ... 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xf016209d in panic (fmt=0xf0277128 "from debugger") at ../../kern/kern_shutdown.c:446 #2 0xf012b3c5 in db_panic (addr=-266940387, have_addr=0, count=1, modif=0xfd69bd48 "") at ../../ddb/db_command.c:432 #3 0xf012b365 in db_command (last_cmdp=0xf02b3920, cmd_table=0xf02b3780, aux_cmd_tablep=0xf02e317c) at ../../ddb/db_command.c:332 #4 0xf012b42a in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf012d77b in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xf023f55e in kdb_trap (type=12, code=0, regs=0xfd69be88) at ../../i386/i386/db_interface.c:157 #7 0xf02497d8 in trap_fatal (frame=0xfd69be88, eva=1417688159) at ../../i386/i386/trap.c:937 #8 0xf02494b7 in trap_pfault (frame=0xfd69be88, usermode=0, eva=1417688159) at ../../i386/i386/trap.c:835 #9 0xf02490ea in trap (frame={tf_es = -31850480, tf_ds = -43843568, tf_edi = 4, tf_esi = -238539008, tf_ebp = -43401376, tf_isp = -43401552, tf_ebx = -238632704, tf_edx = 0, tf_ecx = 1074030207, tf_eax = -238658276, tf_trapno = 12, tf_err = 0, tf_eip = -266940387, tf_cs = 8, tf_eflags = 66050, tf_esp = -43804224, tf_ss = -265588232}) at ../../i386/i386/trap.c:437 #10 0xf016d01d in ioctl (p=0xfd6399c0, uap=0xfd69bf94) at ../../kern/sys_generic.c:445 #11 0xf0249a47 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639696, tf_esi = 84992, tf_ebp = -272642208, tf_isp = -43401244, tf_ebx = 105, tf_edx = 85380, tf_ecx = 38099, tf_eax = 54, tf_trapno = 7, tf_err = 7, tf_eip = 537363601, tf_cs = 31, tf_eflags = 646, tf_esp = -272642224, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #12 0x20078491 in ?? () #13 0x7193 in ?? () #14 0x69f7 in ?? () #15 0x49bd in ?? () #16 0x4450 in ?? () #17 0x3afe in ?? () #18 0x38f8 in ?? () #19 0x1095 in ?? () (kgdb) up 10 #10 0xf016d01d in ioctl (p=0xfd6399c0, uap=0xfd69bf94) at ../../kern/sys_generic.c:445 445 } else if ((com&IOC_OUT) && size) (kgdb) l ioctl 389 /* ARGSUSED */ 390 int 391 ioctl(p, uap) 392 struct proc *p; 393 register struct ioctl_args *uap; 394 { 395 register struct file *fp; 396 register struct filedesc *fdp; 397 register u_long com; 398 int error; (kgdb) p *uap $1 = {Segmentation fault (core dumped) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (gdb paniced here) (kgdb) up #11 0xf0249a47 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639696, tf_esi = 84992, tf_ebp = -272642208, tf_isp = -43401244, tf_ebx = 105, tf_edx = 85380, tf_ecx = 38099, tf_eax = 54, tf_trapno = 7, tf_err = 7, tf_eip = 537363601, tf_cs = 31, tf_eflags = 646, tf_esp = -272642224, tf_ss = 39}) at ../../i386/i386/trap.c:1100 1100 error = (*callp->sy_call)(p, args); (kgdb) l syscall ... 1032 void 1033 syscall(frame) 1034 struct trapframe frame; 1035 { 1036 caddr_t params; 1037 int i; ... 1083 if (params && (i = callp->sy_narg * sizeof(int)) && 1084 (error = copyin(params, (caddr_t)args, (u_int)i))) { ... 1089 goto bad; (kgdb) l 1090 } .... 1095 p->p_retval[0] = 0; 1096 p->p_retval[1] = frame.tf_edx; 1097 1098 STOPEVENT(p, S_SCE, callp->sy_narg); 1099 (kgdb) l 1100 error = (*callp->sy_call)(p, args); 1101 ... (kgdb) i No symbol "i" in current context. (kgdb) ---------- end of gdb output --------- What's the reason of the panic ? VM problem ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 18:46:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hamhae.wdb.co.kr (hamhae.wdb.co.kr [210.92.121.137]) by hub.freebsd.org (Postfix) with ESMTP id 5BBE51502B for ; Mon, 7 Jun 1999 18:45:51 -0700 (PDT) (envelope-from cjh@hamhae.wdb.co.kr) Received: (from cjh@localhost) by hamhae.wdb.co.kr (8.9.3/8.9.3) id KAA50902; Tue, 8 Jun 1999 10:44:46 +0900 (KST) (envelope-from cjh) To: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: junker@jazz.snu.ac.kr, foxfair@news.ks.edu.tw, freebsd-hackers@FreeBSD.ORG Subject: Re: Multilingual Installer for 3.2-RELEASE (Re: pccard boot.flp...) References: <199906071655.BAA10124@afs.ntc.mita.keio.ac.jp> From: "CHOI, Junho" Date: 08 Jun 1999 10:44:46 +0900 In-Reply-To: hosokawa@itc.keio.ac.jp's message of "Tue, 8 Jun 1999 01:55:50 +0900 (JST)" Message-ID: <86r9nn8nzl.fsf@hamhae.wdb.co.kr> Lines: 18 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "HT" == HOSOKAWA Tatsumi writes: HT> Now, the Current Translation Status is: HT> ------------------------------------------------------------------- HT> Japanese Korean HT> ------------------------------------------------------------------- HT> sysinstall messages: almost okay NG HT> help files: almost okay almost okay HT> ------------------------------------------------------------------- It means that I should update my messages.ko_KR translation after last translation? And, what is the meaning, "almost okay"? -- ** Any opinions in this posting are my own and not those of my employers ** CHOI, Junho - Korea FreeBSD Users Group - Web Data Bank Co. Seoul., ROK. (+82-2-515-9941) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 18:58:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id B730B1502B for ; Mon, 7 Jun 1999 18:57:41 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id VAA06360; Mon, 7 Jun 1999 21:57:29 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA05615; Mon, 7 Jun 1999 21:56:59 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA48067; Mon, 7 Jun 1999 21:56:59 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199906080156.VAA48067@bb01f39.unx.sas.com> Subject: Re: sgmlformat & making release In-Reply-To: From Dag-Erling Smorgrav at "Jun 6, 1999 6:56:23 pm" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Mon, 7 Jun 1999 21:56:59 -0400 (EDT) Cc: wilko@yedi.iaf.nl, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (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, I too see this type of failure until I can download the appropriate distfiles into /usr/ports/distfiles... The file /etc/resolv.conf is copied from /etc to the chroot area and is probably ok. I typically find that my upstream domain name server is not responding correctly when this happens. From /usr/src/release/Makefile: if [ -f /etc/resolv.conf ]; then \ cp -p /etc/resolv.conf ${CHROOTDIR}/etc; \ fi Again, From /usr/src/release/Makefile, this should copy any ports from /usr/ports/distfiles into the associated chroot area: if [ -d ${DISTFILES}/ ]; then \ cp -rp ${DISTFILES} ${CHROOTDIR}/usr/ports/distfiles; \ fi Hope this helps. -John > Wilko Bulte writes: > > >> sgmlformat-1.7.tar.gz doesn't seem to exist on this system. > > >> Attempting to fetch from > > http://fallout.campusview.indiana.edu/ports/distfiles/. > > fetch: reading reply from fallout.campusview.indiana.edu: Operation timed > > out > > >> Attempting to fetch from > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/. > > fetch: ftp.freebsd.org: Host name lookup failure > > >> Couldn't fetch it - please try to retrieve this > > >> port manually into /usr/ports/distfiles/ and try again. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > The build is running in a chroot tree which does not have a valid > /etc/resolv.conf. > > > yedi#ls /usr/ports/distfiles > > docbk241.tar.Z isoENTS.zip linuxdoc-1.1.tar.gz > > docbk30.tar.Z jade-1.2.1.tar.gz sgmlformat-1.7.tar.gz > > This is outside the chroot tree. > > DES > - -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > 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 Jun 7 19: 1:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 37CDE1536E for ; Mon, 7 Jun 1999 19:00:26 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA25402; Tue, 8 Jun 1999 02:41:40 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA14092; Tue, 8 Jun 1999 02:40:57 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199906080140.CAA14092@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Eugene M. Kim" Cc: hackers@freebsd.org Subject: Re: Session leader releasing the ctty In-reply-to: Your message of "Mon, 07 Jun 1999 17:14:48 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jun 1999 02:40:57 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I'm having a trouble programming a special login shell, and would like > to hear any opinions on this. > > I want this shell (which automatically becomes a session leader) to > release its ctty but remain unterminated (the ctty must be taken by its > child). However, there seems to be no easy way to do this; termios(4) > says one must call setsid() to release its ctty, but setsid(2) says the > call will fail if the caller is already a session leader. > > Would there be any other way for a session leader to release its ctty > without terminating itself? TIA. You need to also drop your process id so that you're not the owner of the process group that the terminal points at. Check bundle_setsid() in src/usr.sbin/ppp/bundle.c. A second fork() is done here because the parent may continue and doesn't want to figure out how to reap the child - you probably don't need this if the original process is going to go away soon anyway. > Cheers, > Eugene Kim > > PS. I'm now using a workaround that the shell will forward the SIGHUP > that it received because it's a session leader, but this isn't a clean > way. :-p > > -- > Eugene M. Kim NTT Multimedia Communications Laboratories > Software Developer 250 Cambridge Avenue, Suite 205 > +1 650 833 3630 (Voice) Palo Alto, CA 94040, USA > +1 650 833 3633 (Fax) mailto:gene@nttmcl.com -- 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 Jun 7 19: 8: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with ESMTP id 0348F15831 for ; Mon, 7 Jun 1999 19:06:50 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id LAA13965; Tue, 8 Jun 1999 11:06:32 +0900 (JST) Date: Tue, 8 Jun 1999 11:06:32 +0900 (JST) Message-Id: <199906080206.LAA13965@afs.ntc.mita.keio.ac.jp> To: cjh@wdb.co.kr Cc: junker@jazz.snu.ac.kr, foxfair@news.ks.edu.tw, freebsd-hackers@FreeBSD.ORG, hosokawa@itc.keio.ac.jp Subject: Re: Multilingual Installer for 3.2-RELEASE (Re: pccard boot.flp...) In-Reply-To: Your message of "Tue, 8 Jun 1999 10:44:46 JST". <86r9nn8nzl.fsf@hamhae.wdb.co.kr> From: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <86r9nn8nzl.fsf@hamhae.wdb.co.kr> cjh@wdb.co.kr writes: >> It means that I should update my messages.ko_KR translation after last >> translation? And, what is the meaning, "almost okay"? Sorry, I added many message ID's yesterday. The new message.lt_EN can be found in the translation kit. -- HOSOKAWA, Tatsumi Assistant Manager Information Technology Center, Keio University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 23: 5:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5B60C14D28 for ; Mon, 7 Jun 1999 23:04:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA25493; Tue, 8 Jun 1999 00:03:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA03245; Tue, 8 Jun 1999 00:02:14 -0600 (MDT) Message-Id: <199906080602.AAA03245@harmony.village.org> To: Kevin Day Subject: Re: Kernel config script Cc: mike@smith.net.au (Mike Smith), loopd@best.com, hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 30 May 1999 17:13:53 CDT." <199905302213.RAA05198@home.dragondata.com> References: <199905302213.RAA05198@home.dragondata.com> Date: Tue, 08 Jun 1999 00:02:14 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905302213.RAA05198@home.dragondata.com> Kevin Day writes: : 1) The kernel config options are only documented in LINT, which really isn't : meant for that sorta thing, and I'll admit, they're not documented well. : (contrast linux's config where you can hit ? and get a few paragraphs of : info for each option, such as "If I leave this in, and don't have the : hardware, will it cause problems?" etc...) : : 2) It's not the most graceful system for newbies, switching between two : files in a text editor is a bit much for some folks. We're working for the day that this is a completely moot point. There will be very few options to build the kernel with (SMP is the only one that comes to mind but I'm sure there are others). Everything else will be a loadable module. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 23:15: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 01EF114D28 for ; Mon, 7 Jun 1999 23:14:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA25516; Tue, 8 Jun 1999 00:14:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA03298; Tue, 8 Jun 1999 00:13:02 -0600 (MDT) Message-Id: <199906080613.AAA03298@harmony.village.org> To: Robert Huff Subject: Re: Kernel config script Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 31 May 1999 09:07:41 EDT." <14162.35022.502546.522089@r84aap011262.sbo-smr.ma.cable.rcn.com> References: <14162.35022.502546.522089@r84aap011262.sbo-smr.ma.cable.rcn.com> Date: Tue, 08 Jun 1999 00:13:02 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14162.35022.502546.522089@r84aap011262.sbo-smr.ma.cable.rcn.com> Robert Huff writes: : How often _do_ people rebuild their kernels? (On non-testing : machines.) On my stable machines never, or very rarely. I have machines in my basement that tend to have 200-500 day uptimes between reboots (I like my UPS), and I put a new kernel on every 10 reboots or so (note that just because we typically have 200 day uptimes doesn't mean it is 2000 days since I last rebuilt the kernel). On the machine I'm typing on right now, it varies from every couple of minutes to every couple of weeks. I do a 'config HARMONY' only when required. On the machines at work in the test lab, I build between 50 and 200 kernels in a week. I do about 1 config a week, since the kernel is fairly stable (we don't track -current or -stable, but pick good points in time), modulo whatever bug(s) I'm working on. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 23:27:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8305015077 for ; Mon, 7 Jun 1999 23:26:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA25547; Tue, 8 Jun 1999 00:26:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA03373; Tue, 8 Jun 1999 00:24:36 -0600 (MDT) Message-Id: <199906080624.AAA03373@harmony.village.org> To: Christian Murray Subject: Re: m3socks and cvsup Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 01 Jun 1999 21:09:41 +0200." <19990601190941.46F9F2921C@localhost.localdomain> References: <19990601190941.46F9F2921C@localhost.localdomain> Date: Tue, 08 Jun 1999 00:24:36 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990601190941.46F9F2921C@localhost.localdomain> Christian Murray writes: : I have some problems with m3socks and cvsup. I've never been able to make this work. You might try -P m and adding a netcat redirector or 10 on your gateway machine. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 23:36:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BB52814CA3 for ; Mon, 7 Jun 1999 23:35:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA25573; Tue, 8 Jun 1999 00:35:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA03429; Tue, 8 Jun 1999 00:34:01 -0600 (MDT) Message-Id: <199906080634.AAA03429@harmony.village.org> To: Zhihui Zhang Subject: Re: The choice of MAXPHYS Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 03 Jun 1999 10:40:10 EDT." References: Date: Tue, 08 Jun 1999 00:34:01 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Zhihui Zhang writes: : The value of MAXPHYS is chosen to be 64K for the maximum raw I/O transfer : size. I am wondering why it is not set larger. I don't think that it is possible to guarantee that you can do a larger write than 64k on a aha-1542 card given the worst case scatter gather list you can have in FreeBSD. I think that this used to be a common limit. I thought CAM raised the limit somewhat on cards that could support it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 23:43:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id E289214CA3 for ; Mon, 7 Jun 1999 23:42:26 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id IAA10722 for ; Tue, 8 Jun 1999 08:42:25 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id IAA23555 for ; Tue, 8 Jun 1999 08:42:25 +0200 (MET DST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id IAA56994 for ; Tue, 8 Jun 1999 08:42:19 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id GAA05117 for freebsd-hackers@FreeBSD.ORG; Tue, 8 Jun 1999 06:42:19 GMT (envelope-from ust) Date: Tue, 8 Jun 1999 08:42:19 +0200 From: Udo Schweigert To: freebsd-hackers@FreeBSD.ORG Subject: Re: m3socks and cvsup Message-ID: <19990608084217.A5098@alaska.cert.siemens.de> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <19990601190941.46F9F2921C@localhost.localdomain> <199906080624.AAA03373@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906080624.AAA03373@harmony.village.org>; from Warner Losh on Tue, Jun 08, 1999 at 12:24:36AM -0600 X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 08, 1999 at 12:24:36AM -0600, Warner Losh wrote: > In message <19990601190941.46F9F2921C@localhost.localdomain> Christian Murray writes: > : I have some problems with m3socks and cvsup. > > I've never been able to make this work. You might try -P m and adding > a netcat redirector or 10 on your gateway machine. > I'm using it (runsocks cvsup -P m) for a year now and it works without any problems. (Since cvsup 16 the "-P m" is not needed, so "runsocks cvsup" should so it). Regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 48000 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 7 23:55:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A843714CA3 for ; Mon, 7 Jun 1999 23:55:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA25606; Tue, 8 Jun 1999 00:55:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA03505; Tue, 8 Jun 1999 00:53:54 -0600 (MDT) Message-Id: <199906080653.AAA03505@harmony.village.org> To: Jos Backus Subject: Re: The choice of MAXPHYS Cc: Wilko Bulte , zzhang@cs.binghamton.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 03 Jun 1999 23:12:16 +0200." <19990603231216.A36464@hal.mpn.cp.philips.com> References: <19990603231216.A36464@hal.mpn.cp.philips.com> <19990603172907.A20792@hal.mpn.cp.philips.com> <199906031730.TAA00686@yedi.iaf.nl> Date: Tue, 08 Jun 1999 00:53:54 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990603231216.A36464@hal.mpn.cp.philips.com> Jos Backus writes: : On Thu, Jun 03, 1999 at 07:30:20PM +0200, Wilko Bulte wrote: : > 20 bits. But older cards can do no more than 64 kB. : : Indeed, 20 bits (=1 Mbyte) for the address, 16 bits for the transfer counter : (offset). Isn't that 24 bits for addresses? You can dma from an ISA card to anywhere in the first 16M... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 0:38:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BD14314EF9 for ; Tue, 8 Jun 1999 00:38:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA25710; Tue, 8 Jun 1999 01:38:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA03682; Tue, 8 Jun 1999 01:36:21 -0600 (MDT) Message-Id: <199906080736.BAA03682@harmony.village.org> To: Udo Schweigert Subject: Re: m3socks and cvsup Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 08 Jun 1999 08:42:19 +0200." <19990608084217.A5098@alaska.cert.siemens.de> References: <19990608084217.A5098@alaska.cert.siemens.de> <19990601190941.46F9F2921C@localhost.localdomain> <199906080624.AAA03373@harmony.village.org> Date: Tue, 08 Jun 1999 01:36:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990608084217.A5098@alaska.cert.siemens.de> Udo Schweigert writes: : I'm using it (runsocks cvsup -P m) for a year now and it works without : any problems. (Since cvsup 16 the "-P m" is not needed, so "runsocks cvsup" : should so it). Oddd. I can't get mine to work. I always get a destination unreachable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 0:50:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id B855A150B8 for ; Tue, 8 Jun 1999 00:50:08 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id JAA03985 for ; Tue, 8 Jun 1999 09:50:04 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma003980; Tue, 8 Jun 99 09:50:04 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id JAA07807 for ; Tue, 8 Jun 1999 09:50:03 +0200 (MET DST) Received: (qmail 4518 invoked by uid 666); 8 Jun 1999 07:50:24 -0000 Date: Tue, 8 Jun 1999 09:50:24 +0200 From: Jos Backus To: Warner Losh Cc: Wilko Bulte , zzhang@cs.binghamton.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: The choice of MAXPHYS Message-ID: <19990608095024.A4298@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990603231216.A36464@hal.mpn.cp.philips.com> <19990603172907.A20792@hal.mpn.cp.philips.com> <199906031730.TAA00686@yedi.iaf.nl> <19990603231216.A36464@hal.mpn.cp.philips.com> <199906080653.AAA03505@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906080653.AAA03505@harmony.village.org>; from Warner Losh on Tue, Jun 08, 1999 at 12:53:54AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 08, 1999 at 12:53:54AM -0600, Warner Losh wrote: > Isn't that 24 bits for addresses? You can dma from an ISA card to > anywhere in the first 16M... Arrgh, yes, I'm terribly confused. Sorry 'bout that. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 0:57:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 425D614EDB for ; Tue, 8 Jun 1999 00:56:42 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id JAA31345 for ; Tue, 8 Jun 1999 09:56:30 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <02bc01beb184$6f6f09e0$0e00a8c0@neland.dk> From: "Leif Neland" To: "FreeBSD Hackers" Subject: Killing NIC's Date: Tue, 8 Jun 1999 09:56:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have killed my 2.NIC. Both probe and init as usual, and can read from the net (trafshow) but can't transmit. I removed both from the pc, without removing the netcable. (Trying to resolve an IRQ-conflict) Is this a bad-thing (tm) ? If something went broke from this, I would expect it to be something other than the transmitter. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 3: 8:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 7F5F914F97 for ; Tue, 8 Jun 1999 03:08:03 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id MAA22766 for ; Tue, 8 Jun 1999 12:08:02 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id MAA19905 for ; Tue, 8 Jun 1999 12:08:01 +0200 (MET DST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id MAA57505 for ; Tue, 8 Jun 1999 12:07:56 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id KAA92205 for freebsd-hackers@FreeBSD.ORG; Tue, 8 Jun 1999 10:07:56 GMT (envelope-from ust) Date: Tue, 8 Jun 1999 12:07:55 +0200 From: Udo Schweigert To: freebsd-hackers@FreeBSD.ORG Subject: Re: m3socks and cvsup Message-ID: <19990608120755.A92179@alaska.cert.siemens.de> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <19990608084217.A5098@alaska.cert.siemens.de> <19990601190941.46F9F2921C@localhost.localdomain> <199906080624.AAA03373@harmony.village.org> <19990608084217.A5098@alaska.cert.siemens.de> <199906080736.BAA03682@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906080736.BAA03682@harmony.village.org>; from Warner Losh on Tue, Jun 08, 1999 at 01:36:21AM -0600 X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 08, 1999 at 01:36:21AM -0600, Warner Losh wrote: > In message <19990608084217.A5098@alaska.cert.siemens.de> Udo Schweigert writes: > : I'm using it (runsocks cvsup -P m) for a year now and it works without > : any problems. (Since cvsup 16 the "-P m" is not needed, so "runsocks cvsup" > : should so it). > > Oddd. I can't get mine to work. I always get a destination > unreachable. > > Warner Is your cvsup linked dynamic? If not, runsocks wont work. Udo ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 48000 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 7: 1:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.cybersites.com (unknown [207.92.123.2]) by hub.freebsd.org (Postfix) with ESMTP id 7DF6514D6A for ; Tue, 8 Jun 1999 07:01:06 -0700 (PDT) (envelope-from cyouse@cybersites.com) Received: from f8m7n1 (dhcp77.cybersites.com [207.92.123.77]) by ns1.cybersites.com (8.9.3/8.9.3) with SMTP id IAA01728; Tue, 8 Jun 1999 08:57:48 -0400 Message-ID: <006001beb1b6$e16c7be0$4d7b5ccf@f8m7n1> From: "Chuck Youse" To: "Jos Backus" , "Warner Losh" Cc: "Wilko Bulte" , , Subject: Re: The choice of MAXPHYS Date: Tue, 8 Jun 1999 09:57:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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 I believe the DMA chip itself provides 20 bits, and external circuitry extends the remaining 4 bits. Chuck Youse Director of Systems cyouse@cybersites.com -----Original Message----- From: Warner Losh To: Jos Backus Cc: Wilko Bulte ; zzhang@cs.binghamton.edu ; freebsd-hackers@FreeBSD.ORG Date: Tuesday, June 08, 1999 1:54 AM Subject: Re: The choice of MAXPHYS >In message <19990603231216.A36464@hal.mpn.cp.philips.com> Jos Backus writes: >: On Thu, Jun 03, 1999 at 07:30:20PM +0200, Wilko Bulte wrote: >: > 20 bits. But older cards can do no more than 64 kB. >: >: Indeed, 20 bits (=1 Mbyte) for the address, 16 bits for the transfer counter >: (offset). > >Isn't that 24 bits for addresses? You can dma from an ISA card to >anywhere in the first 16M... > >Warner > > >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 Jun 8 7:30:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 41D9C14D86 for ; Tue, 8 Jun 1999 07:29:57 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id PAA40653 for hackers@freebsd.org; Tue, 8 Jun 1999 15:29:54 +0100 (BST) (envelope-from joe) Date: Tue, 8 Jun 1999 15:29:53 +0100 From: Josef Karthauser To: hackers@freebsd.org Subject: Wierd behavour from G++28! Message-ID: <19990608152953.L14211@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Strange. I'm having a wierd time trying to get a package called Swish++ working. It's a C++/STL based program, which the author recommends compiling up with Gcc2.8 or higher. So... I've installed gcc-2.8.1 && glibstdc++-2.8.1.1, and compiled it up. Strangely however, the 'search' part of it core dumps in an unexpected way. gandalf% ./search Segmentation fault (core dumped) gandalf% gdb search search.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `search'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libc.so.3...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 149 } (gdb) bt #0 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 #1 0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149 #2 0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219 (gdb) l What gives? It looks like a library thing. Can anyone put me on the right track please? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (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 Tue Jun 8 7:40:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6D62C14D86 for ; Tue, 8 Jun 1999 07:40:14 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA12181; Tue, 8 Jun 1999 23:40:02 +0900 (JST) Message-ID: <375D19F8.39C6F771@newsguy.com> Date: Tue, 08 Jun 1999 22:26:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FS tuning (Was: File system gets too fragmented ???) References: <199905271415.HAA10721@salsa.gv.tsc.tdk.com> <86lne8h3gj.fsf@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > No, I don't think there's much point in doing that before Kirk > McKusick removes the restrictions on the soft updates code. When that > happens, we can make soft updates non-optional and turn on soft > updates on all file systems by default. I hope *that* doesn't happen, unless the free space problem is corrected first. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "definition of an expert: X means experimental and a spurt is a drip under pressure." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 8:33:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 9E891152EB for ; Tue, 8 Jun 1999 08:32:49 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA09451; Tue, 8 Jun 1999 10:46:30 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA18523; Tue, 8 Jun 1999 10:45:39 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id KAA07034; Tue, 8 Jun 1999 10:45:39 -0400 (EDT) Date: Tue, 8 Jun 1999 10:45:39 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906081445.KAA07034@lakes.dignus.com> To: hackers@FreeBSD.ORG, joe@pavilion.net Subject: Re: Wierd behavour from G++28! In-Reply-To: <19990608152953.L14211@pavilion.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Strange. > > I'm having a wierd time trying to get a package called Swish++ working. > It's a C++/STL based program, which the author recommends compiling up > with Gcc2.8 or higher. > > So... I've installed gcc-2.8.1 && glibstdc++-2.8.1.1, and compiled it > up. Strangely however, the 'search' part of it core dumps in an > unexpected way. > > gandalf% ./search > Segmentation fault (core dumped) > gandalf% gdb search search.core > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > Core was generated by `search'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libm.so.2...done. > Reading symbols from /usr/lib/libc.so.3...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > 149 } > (gdb) bt > #0 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > #1 0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149 > #2 0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219 > (gdb) l > > > What gives? It looks like a library thing. > > Can anyone put me on the right track please? > > Joe Or - it could be that the stream wasn't properly opened and no-one checked for it... Look at line 219 in search.c, it should be a <<-operator operating on a stream of some kind. Then, find where that stream is declared/constructed and ensure everything is all right... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 8:50:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id E8581152EB for ; Tue, 8 Jun 1999 08:50:49 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id QAA66864; Tue, 8 Jun 1999 16:50:22 +0100 (BST) (envelope-from joe) Date: Tue, 8 Jun 1999 16:50:22 +0100 From: Josef Karthauser To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: Wierd behavour from G++28! Message-ID: <19990608165022.B64790@pavilion.net> References: <19990608152953.L14211@pavilion.net> <199906081445.KAA07034@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906081445.KAA07034@lakes.dignus.com>; from Thomas David Rivers on Tue, Jun 08, 1999 at 10:45:39AM -0400 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 08, 1999 at 10:45:39AM -0400, Thomas David Rivers wrote: > > (gdb) bt > > #0 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > > #1 0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149 > > #2 0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219 > > (gdb) l > > > Or - it could be that the stream wasn't properly opened and no-one > checked for it... > > Look at line 219 in search.c, it should be a <<-operator operating > on a stream of some kind. Then, find where that stream is > declared/constructed and ensure everything is all right... 216 file_vector the_index( index_file_name ); 217 if ( !the_index ) { 218 cerr << me << ": could not read index from " 219 << index_file_name << endl; 220 ::exit( 2 ); 221 } (gdb) break 218 Breakpoint 1 at 0x8049941: file search.c, line 218. (gdb) run Starting program: /data/home/joe/src/swish/swish++-2.0/search Breakpoint 1, main (argc=1, argv=0xbfbfdb14) at search.c:219 219 << index_file_name << endl; (gdb) print index_file_name $1 = 0x806bfe2 "the.index" (gdb) print me $2 = 0xbfbfdc35 "search" (gdb) print cerr $3 = 134671820 (gdb) print endl $4 = {} 0x8052d20 (gdb) s 0x80528ed in ostream::operator<< () at /usr/include/ctype.h:149 149 } (gdb) s Program received signal SIGSEGV, Segmentation fault. 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 149 } Is it because the program's compiled using the wrong includes? (/usr/include/ctype.h && /usr/local/bin/g++28) Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (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 Tue Jun 8 9: 3:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 035F915398 for ; Tue, 8 Jun 1999 09:03:08 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id MAA18589; Tue, 8 Jun 1999 12:03:50 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id MAA18651; Tue, 8 Jun 1999 12:03:03 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id MAA07762; Tue, 8 Jun 1999 12:03:03 -0400 (EDT) Date: Tue, 8 Jun 1999 12:03:03 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906081603.MAA07762@lakes.dignus.com> To: joe@pavilion.net, rivers@dignus.com Subject: Re: Wierd behavour from G++28! Cc: hackers@FreeBSD.ORG In-Reply-To: <19990608165022.B64790@pavilion.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Jun 08, 1999 at 10:45:39AM -0400, Thomas David Rivers wrote: > > > (gdb) bt > > > #0 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > > > #1 0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149 > > > #2 0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219 > > > (gdb) l > > > > > > Or - it could be that the stream wasn't properly opened and no-one > > checked for it... > > > > Look at line 219 in search.c, it should be a <<-operator operating > > on a stream of some kind. Then, find where that stream is > > declared/constructed and ensure everything is all right... > > 216 file_vector the_index( index_file_name ); > 217 if ( !the_index ) { > 218 cerr << me << ": could not read index from " > 219 << index_file_name << endl; > 220 ::exit( 2 ); > 221 } > > > (gdb) break 218 > Breakpoint 1 at 0x8049941: file search.c, line 218. > (gdb) run > Starting program: /data/home/joe/src/swish/swish++-2.0/search > > Breakpoint 1, main (argc=1, argv=0xbfbfdb14) at search.c:219 > 219 << index_file_name << endl; > (gdb) print index_file_name > $1 = 0x806bfe2 "the.index" > (gdb) print me > $2 = 0xbfbfdc35 "search" > (gdb) print cerr > $3 = 134671820 > (gdb) print endl > $4 = {} 0x8052d20 > (gdb) s > 0x80528ed in ostream::operator<< () at /usr/include/ctype.h:149 > 149 } > (gdb) s > > Program received signal SIGSEGV, Segmentation fault. > 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > 149 } > > Is it because the program's compiled using the wrong includes? > (/usr/include/ctype.h && /usr/local/bin/g++28) I was guessing that the stream may be wrong - but cerr is likely correctly constructed... You may have mixed up the libraries somehow when you linked... but I'll have to defer that to someone who's used gcc2.8... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 10: 6:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 6E4EC14EAF for ; Tue, 8 Jun 1999 10:06:42 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id SAA85745; Tue, 8 Jun 1999 18:06:22 +0100 (BST) (envelope-from joe) Date: Tue, 8 Jun 1999 18:06:22 +0100 From: Josef Karthauser To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: Wierd behavour from G++28! Message-ID: <19990608180621.Q14211@pavilion.net> References: <19990608165022.B64790@pavilion.net> <199906081603.MAA07762@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906081603.MAA07762@lakes.dignus.com>; from Thomas David Rivers on Tue, Jun 08, 1999 at 12:03:03PM -0400 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 08, 1999 at 12:03:03PM -0400, Thomas David Rivers wrote: > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > > 149 } > > > > Is it because the program's compiled using the wrong includes? > > (/usr/include/ctype.h && /usr/local/bin/g++28) > > I was guessing that the stream may be wrong - but cerr is likely > correctly constructed... > > You may have mixed up the libraries somehow when you linked... but > I'll have to defer that to someone who's used gcc2.8... Can someone comment please? Is this a bug in the way the gcc2.8 is installed, or is it a bug in my understanding? (probably the latter). Tnx, Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (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 Tue Jun 8 10:41:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 7332F14EA4 for ; Tue, 8 Jun 1999 10:41:49 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA04883; Tue, 8 Jun 1999 19:38:02 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA69860; Tue, 8 Jun 1999 19:33:16 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906081733.TAA69860@yedi.iaf.nl> Subject: Re: The choice of MAXPHYS In-Reply-To: <19990608095024.A4298@hal.mpn.cp.philips.com> from Jos Backus at "Jun 8, 1999 9:50:24 am" To: Jos.Backus@nl.origin-it.com Date: Tue, 8 Jun 1999 19:33:16 +0200 (CEST) Cc: imp@harmony.village.org, zzhang@cs.binghamton.edu, 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+ PL43 (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 Jos Backus wrote ... > On Tue, Jun 08, 1999 at 12:53:54AM -0600, Warner Losh wrote: > > Isn't that 24 bits for addresses? You can dma from an ISA card to > > anywhere in the first 16M... > > Arrgh, yes, I'm terribly confused. Sorry 'bout that. Be happy, you're not alone ;-) | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 11:28:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8000614C46 for ; Tue, 8 Jun 1999 11:28:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA27386; Tue, 8 Jun 1999 12:28:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA27411; Tue, 8 Jun 1999 12:27:09 -0600 (MDT) Message-Id: <199906081827.MAA27411@harmony.village.org> To: Udo Schweigert Subject: Re: m3socks and cvsup Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 08 Jun 1999 12:07:55 +0200." <19990608120755.A92179@alaska.cert.siemens.de> References: <19990608120755.A92179@alaska.cert.siemens.de> <19990608084217.A5098@alaska.cert.siemens.de> <19990601190941.46F9F2921C@localhost.localdomain> <199906080624.AAA03373@harmony.village.org> <19990608084217.A5098@alaska.cert.siemens.de> <199906080736.BAA03682@harmony.village.org> Date: Tue, 08 Jun 1999 12:27:09 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990608120755.A92179@alaska.cert.siemens.de> Udo Schweigert writes: : Is your cvsup linked dynamic? If not, runsocks wont work. No. That's the problem... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 12:15:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eyry.econ.iastate.edu (eyry.econ.iastate.edu [129.186.32.221]) by hub.freebsd.org (Postfix) with ESMTP id 44FC514C12 for ; Tue, 8 Jun 1999 12:15:55 -0700 (PDT) (envelope-from hawk@eyry.econ.iastate.edu) Received: from eyry.econ.iastate.edu (localhost [127.0.0.1]) by eyry.econ.iastate.edu (8.9.3/8.9.3) with ESMTP id OAA25538 for ; Tue, 8 Jun 1999 14:16:02 -0500 (CDT) (envelope-from hawk@eyry.econ.iastate.edu) Message-Id: <199906081916.OAA25538@eyry.econ.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@freebsd.org Subject: edited xcircuit to current version, now what? Reply-To: f@eyry.econ.iastate.edu, hawk@eyry.econ.iastate.edu Date: Tue, 08 Jun 1999 14:16:02 -0500 From: "Richard E. Hawkins" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've edited the makefile in the portes, and the source, to install xcircuit 2.0a10 rather than 1.7 (1.7 can't open its own files, it seems). the old patch-aa was *** Imakefile.orig Thu Mar 12 12:22:41 1998 --- Imakefile Sun May 17 15:52:05 1998 *************** *** 31,37 **** # Change the following as desired to suit your environment: #------------------------------------------------------------------------ # ! PREFIX = /usr/local XCIRCUIT_LIB_DIR = $(PREFIX)/lib/xcircuit XCIRCUIT_BIN_DIR = $(PREFIX)/bin XCIRCUIT_MAN_DIR = $(PREFIX)/man/man1 --- 31,37 ---- # Change the following as desired to suit your environment: #------------------------------------------------------------------------ # ! PREFIX ?= /usr/local XCIRCUIT_LIB_DIR = $(PREFIX)/lib/xcircuit XCIRCUIT_BIN_DIR = $(PREFIX)/bin XCIRCUIT_MAN_DIR = $(PREFIX)/man/man1 so I put the ? into that line in Imakefile. Of the second patchfile, the first patch was already in main, and the second added fpsetmask(0) conditionally for freebsd at the beginning of main, so I inserted this. It compiles & installs, then executes, quite nicely. I found instructions on what to do with them once I made them, but I'm not clear on how to make them. I need to make a patch against /usr/ports/cad/xcircuit/work/xcircuit-2.0a10/xcircuit.c, /usr/ports/cad/xcircuit/work/xcircuit-2.0a10/Imakefile, and the Makefile. I presume there's some difference between how I do the first two and the third. And then I expect that there's some kind of CVS meta-patch that gets created, cos that a cvsup will update folks port collection? rick -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 14:40:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [209.90.128.250]) by hub.freebsd.org (Postfix) with ESMTP id C1E8814BE3 for ; Tue, 8 Jun 1999 14:40:51 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id RAA70196 for hackers@freebsd.org; Tue, 8 Jun 1999 17:49:06 -0400 (EDT) Date: Tue, 8 Jun 1999 17:49:06 -0400 From: Dan Moschuk To: hackers@freebsd.org Subject: Segfault in longjmp() ? Message-ID: <19990608174906.E69896@trinsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The machine is a SMP 3.0-RELEASE box. A heavily threaded program is segfaulting in the longjmp() function. Any ideas what would cause this? Regards, Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 14:44:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 254B714BE3 for ; Tue, 8 Jun 1999 14:44:32 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA09187; Tue, 8 Jun 1999 17:44:58 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA19231; Tue, 8 Jun 1999 17:44:19 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id RAA09700; Tue, 8 Jun 1999 17:44:19 -0400 (EDT) Date: Tue, 8 Jun 1999 17:44:19 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906082144.RAA09700@lakes.dignus.com> To: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: Segfault in longjmp() ? In-Reply-To: <19990608174906.E69896@trinsec.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The machine is a SMP 3.0-RELEASE box. > > A heavily threaded program is segfaulting in the longjmp() function. > Any ideas what would cause this? > > Regards, > > Dan > > You could have trashed your jmp_buf... (i.e. you're passing bad data to longjmp().) Just a thought... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 14:49: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 67F1214BE3 for ; Tue, 8 Jun 1999 14:48:57 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA27774; Wed, 9 Jun 1999 08:09:51 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906082209.IAA27774@cimlogic.com.au> Subject: Re: Segfault in longjmp() ? In-Reply-To: <19990608174906.E69896@trinsec.com> from Dan Moschuk at "Jun 8, 1999 5:49: 6 pm" To: dan@trinsec.com (Dan Moschuk) Date: Wed, 9 Jun 1999 08:09:51 +1000 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Dan Moschuk wrote: > > The machine is a SMP 3.0-RELEASE box. > > A heavily threaded program is segfaulting in the longjmp() function. > Any ideas what would cause this? A bug in the thread exit code. This was fixed at the "13th hour" during the release of 3.2. -- 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 Tue Jun 8 15: 1:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 53EB314E1F for ; Tue, 8 Jun 1999 15:01:49 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA25453; Tue, 8 Jun 1999 18:01:00 -0400 (EDT) Date: Tue, 8 Jun 1999 18:01:00 -0400 (EDT) From: Daniel Eischen Message-Id: <199906082201.SAA25453@pcnet1.pcnet.com> To: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: Segfault in longjmp() ? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > The machine is a SMP 3.0-RELEASE box. > > A heavily threaded program is segfaulting in the longjmp() function. > Any ideas what would cause this? Libc_r or Linuxthreads? There are some known problems WRT signal handling in libc_r. I think they've been mostly fixed (with possible exception of signals interrupting signal handlers) with the changes at: ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz If you're having problems with libc_r and these changes don't solve your problem, let me know. Make sure you do a 'make clean' in src/lib/libc_r before building. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 16:34:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 17C0B1589C for ; Tue, 8 Jun 1999 16:34:18 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA19915; Wed, 9 Jun 1999 09:04:06 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA17662; Wed, 9 Jun 1999 09:05:12 +0930 Date: Wed, 9 Jun 1999 09:05:12 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: f@eyry.econ.iastate.edu, hawk@eyry.econ.iastate.edu Cc: freebsd-hackers@freebsd.org Subject: Re: edited xcircuit to current version, now what? In-Reply-To: <199906081916.OAA25538@eyry.econ.iastate.edu> 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, 8 Jun 1999, Richard E. Hawkins wrote: > I've edited the makefile in the portes, and the source, to install > xcircuit 2.0a10 rather than 1.7 (1.7 can't open its own files, it > seems). See the section in the handbook on porting. These kinds of questions are better sent to freebsd-ports where all the porters hang out. Good luck! Kris ---- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 16:53:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id A7EE914EBD for ; Tue, 8 Jun 1999 16:52:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA30306; Wed, 9 Jun 1999 00:41:33 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA23785; Wed, 9 Jun 1999 00:40:46 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199906082340.AAA23785@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Josef Karthauser Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: Wierd behavour from G++28! In-reply-to: Your message of "Tue, 08 Jun 1999 18:06:22 BST." <19990608180621.Q14211@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Jun 1999 00:40:46 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Jun 08, 1999 at 12:03:03PM -0400, Thomas David Rivers wrote: > > > > > > Program received signal SIGSEGV, Segmentation fault. > > > 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149 > > > 149 } > > > > > > Is it because the program's compiled using the wrong includes? > > > (/usr/include/ctype.h && /usr/local/bin/g++28) > > > > I was guessing that the stream may be wrong - but cerr is likely > > correctly constructed... > > > > You may have mixed up the libraries somehow when you linked... but > > I'll have to defer that to someone who's used gcc2.8... > > Can someone comment please? Is this a bug in the way the gcc2.8 is > installed, or is it a bug in my understanding? (probably the latter). Perhaps you need a gcc-compiled version of libstdc++. It's just a guess, but when we shifted to egcs, there were all sorts of problems linking against the gcc-compiled version. > Tnx, > Joe > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] -- 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 Tue Jun 8 23: 8:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id E2E8514BF1; Tue, 8 Jun 1999 23:08:35 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id OAA10226; Wed, 9 Jun 1999 14:07:35 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id OAA24893; Wed, 9 Jun 1999 14:08:32 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id OAA14733; Wed, 9 Jun 1999 14:08:32 +0800 Message-Id: <199906090608.OAA14733@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@freebsd.org, multimedia@freebsd.org Subject: SDL port done yet? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Jun 1999 14:08:31 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while ago, someone mentioned that they were partway through a port of the Simple DirectMedia Layer. Has this been completed? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 8 23:47:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from colin.iconmedialab.fi (colin.iconmedialab.fi [193.66.237.50]) by hub.freebsd.org (Postfix) with ESMTP id 8EA8414F07 for ; Tue, 8 Jun 1999 23:47:25 -0700 (PDT) (envelope-from kaipila@iconmedialab.fi) Received: from colin (colin [193.66.237.50]) by colin.iconmedialab.fi (8.9.3/8.9.3) with ESMTP id JAA27675 for ; Wed, 9 Jun 1999 09:47:04 +0300 (EET DST) Date: Wed, 9 Jun 1999 09:47:03 +0300 (EET DST) From: Antti Kaipila X-Sender: kaipila@colin To: hackers@freebsd.org Subject: CCD and strange hang 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 two 10G hard drives and I have been trying to get them mirrored with ccd. I have got /var (100MB) mirrored fine. But I'm experiencing total hangup of the machine when trying to configure one disk ccd with the slice ment as the second part of the /usr (9380MB) ccd. Here's my slice layout from disk no. 1: wd0s1a 40MB * wd0s1b swap 261MB SWAP wd0s1e 100MB * wd0s1f 9380MB * I don't see anything in the logs. The machine just hangs totaly when I issue the ccdconfig command (ccdconfig ccd2 32 none /dev/wd1s1h) I have 4 ccd drivers in kernel. OS version is FreeBSD 3.2-RELEASE Any ideas? I'm at a loss here. Please CC me, I'm not on the list. Thanks. -- Antti Kaipila To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 0:56:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 31D361521E; Wed, 9 Jun 1999 00:56:13 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: from localhost (daeron@localhost) by Wit401305.student.utwente.nl (8.9.3/8.9.2) with ESMTP id JAA24048; Wed, 9 Jun 1999 09:55:52 +0200 (CEST) (envelope-from daeron@Wit401305.student.utwente.nl) Date: Wed, 9 Jun 1999 09:55:52 +0200 (CEST) From: Pascal Hofstee To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: SDL port done yet? In-Reply-To: <199906090608.OAA14733@ariadne.tensor.pgs.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 Wed, 9 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > A while ago, someone mentioned that they were partway through a port of the > Simple DirectMedia Layer. Has this been completed? Basically the entire SDL library works now on my FreeBSD-3.2-STABLE box ... (as that is where I have the main developer pf the SDL-librray do the porting) The only problem is that the pthread_cancel functions are not in our pthread implementation yet .... -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 1: 5:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 1BC9414E6F for ; Wed, 9 Jun 1999 01:05:25 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id JAA81600; Wed, 9 Jun 1999 09:04:03 +0100 (BST) (envelope-from joe) Date: Wed, 9 Jun 1999 09:04:03 +0100 From: Josef Karthauser To: Brian Somers Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: Wierd behavour from G++28! Message-ID: <19990609090403.A79865@pavilion.net> References: <19990608180621.Q14211@pavilion.net> <199906082340.AAA23785@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906082340.AAA23785@keep.lan.Awfulhak.org>; from Brian Somers on Wed, Jun 09, 1999 at 12:40:46AM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 09, 1999 at 12:40:46AM +0100, Brian Somers wrote: > > > > Can someone comment please? Is this a bug in the way the gcc2.8 is > > installed, or is it a bug in my understanding? (probably the latter). > > Perhaps you need a gcc-compiled version of libstdc++. It's just a > guess, but when we shifted to egcs, there were all sorts of problems > linking against the gcc-compiled version. > Ok. I've compiled up a 4.0-CURRENT box, with EGCS native, and recompiled the program. It still crashes, this time with: Core was generated by `search'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libstdc++.so.3...done. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libc.so.3...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x8053169 in __get_eh_info () at /usr/include/ctype.h:149 149 } (gdb) bt #0 0x8053169 in __get_eh_info () at /usr/include/ctype.h:149 #1 0x8053156 in __get_eh_info () at /usr/include/ctype.h:149 #2 0x8053132 in __get_eh_context () at /usr/include/ctype.h:149 #3 0x8059fda in my_set::my_set (this=0x805ff9c) at search.c:64 #4 0x804d3b9 in global constructors keyed to files () at search.c:64 #5 0x804a5d8 in _start () #6 0x804a25d in _init () (gdb) From search.c: 60 char const* me; // executable name 61 file_index files; 62 word_index words, stop_words, meta_names; 63 bool stem_words; 64 string_set stop_words_found; 65 66 void dump_single_word( char const *word ); 67 void dump_word_window( char const *word, int window_size, int match ); I'm very confused... the programmer is convinced that it works under other platforms, but I'm not getting any joy out of it :( Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (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 Wed Jun 9 1:30:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 1023D14E61; Wed, 9 Jun 1999 01:30:43 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id QAA10505; Wed, 9 Jun 1999 16:29:04 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id QAA05359; Wed, 9 Jun 1999 16:30:00 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id QAA01572; Wed, 9 Jun 1999 16:29:59 +0800 Message-Id: <199906090829.QAA01572@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Pascal Hofstee Cc: hackers@freebsd.org, multimedia@freebsd.org Subject: Re: SDL port done yet? In-reply-to: Your message of "Wed, 09 Jun 1999 09:55:52 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Jun 1999 16:29:59 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 9 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > Basically the entire SDL library works now on my FreeBSD-3.2-STABLE box > ... (as that is where I have the main developer pf the SDL-librray do the > porting) > > The only problem is that the pthread_cancel functions are not in our > pthread implementation yet .... > Hmm. Has he merged the changes into the SDL codebase yet? (what is it, 0.9.13). Is anyone doing anything about the pthread_cancel calls? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 1:35:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 9E8E8153CB; Wed, 9 Jun 1999 01:35:09 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: from localhost (daeron@localhost) by Wit401305.student.utwente.nl (8.9.3/8.9.2) with ESMTP id KAA41271; Wed, 9 Jun 1999 10:35:03 +0200 (CEST) (envelope-from daeron@Wit401305.student.utwente.nl) Date: Wed, 9 Jun 1999 10:35:03 +0200 (CEST) From: Pascal Hofstee To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: hackers@freebsd.org, multimedia@freebsd.org Subject: Re: SDL port done yet? In-Reply-To: <199906090829.QAA01572@ariadne.tensor.pgs.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 Wed, 9 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > Hmm. Has he merged the changes into the SDL codebase yet? (what is it, 0.9.13). Is anyone doing anything about the pthread_cancel calls? As far as I know the changes have been merged into the main SDL code base. (it was basically some very minor changes to the linux-code ... with a rewrite of the cd-audio code) ... as far as the pthread-concel functions are concerned ... i don't really know much about the current status on this issue. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 1:38:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id 6473B14BD6 for ; Wed, 9 Jun 1999 01:38:27 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id DAA65843; Wed, 9 Jun 1999 03:38:13 -0500 (EST) (envelope-from toor) Message-Id: <199906090838.DAA65843@dyson.iquest.net.> Subject: Re: problem for the VM gurus In-Reply-To: <199906072257.SAA22459@bbs.mpcs.com> from Howard Goldstein at "Jun 7, 1999 06:57:55 pm" To: hgoldste@bbs.mpcs.com (Howard Goldstein) Date: Wed, 9 Jun 1999 03:38:13 -0500 (EST) Cc: freebsd-hackers@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Howard Goldstein said: > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: > : On Mon, 7 Jun 1999, Matthew Dillon wrote: > : > ... what version of the operating system? > : 4.0-CURRENT > > 3.2R too... > I just checked the source (CVS) tree, and something bad happend between 1.27 and 1.29 on ufs_readwrite.c. Unless other things had been changed to make the problem go away, the recursive vnode thing was broken then. I am surprised that was changed that long ago. (The breakage is an example of someone making a change, and not either understanding why the code was there, or forgetting to put the alternative into the code.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 4:19:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id BA5BF1541D for ; Wed, 9 Jun 1999 04:19:42 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id HAA16528; Wed, 9 Jun 1999 07:19:41 -0400 (EDT) Received: from thehousleys.net (housley@localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id HAA92911; Wed, 9 Jun 1999 07:19:41 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <375E4DCC.4A7A9506@thehousleys.net> Date: Wed, 09 Jun 1999 07:19:40 -0400 From: "James E. Housley" X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 3.2-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Antti Kaipila Cc: hackers@FreeBSD.ORG Subject: Re: CCD and strange hang References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Antti Kaipila wrote: > > > Any ideas? I'm at a loss here. Please CC me, I'm not on the list. > Have you done sh MAKEDEV ccd0 sh MAKEDEV ccd1 sh MAKEDEV ccd2 sh MAKEDEV ccd3 ? -- James E. Housley PGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 4:26:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id BE8D615401 for ; Wed, 9 Jun 1999 04:26:49 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id HAA28435; Wed, 9 Jun 1999 07:26:44 -0400 (EDT) Date: Wed, 9 Jun 1999 07:26:43 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "John S. Dyson" Cc: Howard Goldstein , freebsd-hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus In-Reply-To: <199906090838.DAA65843@dyson.iquest.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 Wed, 9 Jun 1999, John S. Dyson wrote: > Howard Goldstein said: > > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: > > : On Mon, 7 Jun 1999, Matthew Dillon wrote: > > : > ... what version of the operating system? > > : 4.0-CURRENT > > > > 3.2R too... > > > I just checked the source (CVS) tree, and something bad happend > between 1.27 and 1.29 on ufs_readwrite.c. Unless other things > had been changed to make the problem go away, the recursive vnode > thing was broken then. I am surprised that was changed that long > ago. (The breakage is an example of someone making a change, and > not either understanding why the code was there, or forgetting to > put the alternative into the code.) Is that the limit to Bruce's fu*kup, or did he break it elsewhere, too? It'd be nice to get this reversed since it's been found. And FWIW, semenu seems to be the only one to have anything to handle IN_RECURSE, probably because his NTFS code was recently committed and not mangled. > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 4:36:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 5F32A14C42 for ; Wed, 9 Jun 1999 04:36:49 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 17761 invoked from network); 9 Jun 1999 11:36:47 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 9 Jun 1999 11:36:47 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id GAA15180; Wed, 9 Jun 1999 06:36:45 -0500 (EST) From: "John S. Dyson" Message-Id: <199906091136.GAA15180@dyson.iquest.net> Subject: Re: problem for the VM gurus In-Reply-To: from Brian Feldman at "Jun 9, 99 07:26:43 am" To: green@unixhelp.org (Brian Feldman) Date: Wed, 9 Jun 1999 06:36:45 -0500 (EST) Cc: dyson@iquest.net, hgoldste@bbs.mpcs.com, 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 > On Wed, 9 Jun 1999, John S. Dyson wrote: > > > Howard Goldstein said: > > > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: > > > : On Mon, 7 Jun 1999, Matthew Dillon wrote: > > > : > ... what version of the operating system? > > > : 4.0-CURRENT > > > > > > 3.2R too... > > > > > I just checked the source (CVS) tree, and something bad happend > > between 1.27 and 1.29 on ufs_readwrite.c. Unless other things > > had been changed to make the problem go away, the recursive vnode > > thing was broken then. I am surprised that was changed that long > > ago. (The breakage is an example of someone making a change, and > > not either understanding why the code was there, or forgetting to > > put the alternative into the code.) > > Is that the limit to Bruce's fu*kup, or did he break it elsewhere, too? It'd be > nice to get this reversed since it's been found. And FWIW, semenu seems to > be the only one to have anything to handle IN_RECURSE, probably because his > NTFS code was recently committed and not mangled. > I think that I had most of the filesystems fixed somewhere (in my private tree or in the standard one.) It is easy to make mistakes, but he was also right that there is probably a better way to do it. I suggest putting the recurse stuff back in for a quick fix, and working the problem in more detail in the future. (I could even be wrong if this is where the problem came in -- so much has happened since then :-)). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 4:45:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc1017255-a.srst1.fl.home.com (cc1017255-a.srst1.fl.home.com [24.3.122.197]) by hub.freebsd.org (Postfix) with ESMTP id 3CB5C14F5C for ; Wed, 9 Jun 1999 04:43:51 -0700 (PDT) (envelope-from hg@n2wx.ampr.org) Received: from penny.n2wx.ampr.org (penny.n2wx.ampr.org [172.16.0.5]) by cc1017255-a.srst1.fl.home.com (Postfix) with ESMTP id C75E21E53; Wed, 9 Jun 1999 07:43:46 -0400 (EDT) Received: by penny.n2wx.ampr.org (Postfix, from userid 1000) id F22ACDD; Wed, 9 Jun 1999 07:43:45 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14174.21361.773177.526498@penny.south.mpcs.com> Date: Wed, 9 Jun 1999 07:43:45 -0400 (EDT) From: Howard Goldstein To: dyson@iquest.net Cc: freebsd-hackers@freebsd.org Subject: Re: problem for the VM gurus In-Reply-To: <199906090838.DAA65843@dyson.iquest.net.> References: <199906072257.SAA22459@bbs.mpcs.com> <199906090838.DAA65843@dyson.iquest.net.> X-Mailer: VM 6.62 under Emacs 19.34.1 Organization: disorganization Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson writes: > Howard Goldstein said: > > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: > > : 4.0-CURRENT > > > > 3.2R too... > > > I just checked the source (CVS) tree, and something bad happend > between 1.27 and 1.29 on ufs_readwrite.c. Unless other things > had been changed to make the problem go away, the recursive vnode > thing was broken then. I can pretty easily test patches and try other stuff out on a couple of dozen brand new, architecturally (sp) stressed out (memorywise (zero swap, 16mb RAM, mfsroot) and cpu bandwidth wise (386sx40)) 3.1-R (switchable to 3.2R) systems, if it'd be helpful. Should it bring out clues leading to the fix for 'the' golden page-not-present instability it'd be awesome karma. This very limited environment is especially fragile and highly susceptible to consistently reproducing the popular >= 3.1R page not present panics. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 4:49:59 1999 Delivered-To: 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 (Postfix) with ESMTP id 0BBBB14BD6 for ; Wed, 9 Jun 1999 04:49:55 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.yy.ics.keio.ac.jp [131.113.47.22]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id UAA19396 for ; Wed, 9 Jun 1999 20:49:54 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.2/3.7W) id UAA12941; Wed, 9 Jun 1999 20:49:58 +0900 (JST) Message-Id: <199906091149.UAA12941@lavender.yy.cs.keio.ac.jp> To: hackers@FreeBSD.ORG Subject: [sysinstall] save _ftpPath to /etc/rc.conf X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 09 Jun 1999 20:49:57 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Hackers. I always install FreeBSD via FTP. But sysinstall forgot FTP server name after reboot and restart... I quick hacked sysinstall and it save to /etc/rc.conf as below line and reuse URL. # -- sysinstall generated deltas -- # _ftpPath="ftp://ftp.cc.keio.ac.jp/pub/FreeBSD/" Current problem: o _ftpPath is defined in sysinstall.h. I hope to change appropriate strings. (for example remove ``_'' character) o It can't save media type(FTP, NFS, CDROM...). o I hope to reuse to MASTER_SITE_BACKUP for ports system. MIHIRA Sanpei Yoshiro I will add select box to adduser-->Login shell selection box. --- src/release/sysinstall/media.c.org Mon Jun 7 23:03:13 1999 +++ src/release/sysinstall/media.c Wed Jun 9 20:21:09 1999 @@ -322,33 +322,30 @@ cp = variable_get(VAR_FTP_PATH); /* If we've been through here before ... */ if (!variable_get(VAR_NONINTERACTIVE)) - if (networkDev && cp && msgYesNo("Re-use old FTP site selection values?")) + if (cp && msgYesNo("Re-use old FTP site selection values?") && networkDev) cp = NULL; if (!cp) { dialog_clear_norefresh(); if (!dmenuOpenSimple(&MenuMediaFTP, FALSE)) return DITEM_FAILURE | DITEM_RESTORE; - else - cp = variable_get(VAR_FTP_PATH); - what = DITEM_RESTORE; - } - if (!cp) - return DITEM_FAILURE | what; - else if (!strcmp(cp, "other")) { - variable_set2(VAR_FTP_PATH, "ftp://", 0); - dialog_clear_norefresh(); - cp = variable_get_value(VAR_FTP_PATH, "Please specify the URL of a FreeBSD distribution on a\n" + cp = variable_get(VAR_FTP_PATH); + if (!strcmp(cp, "other")) { + variable_set2(VAR_FTP_PATH, "ftp://", 0); + dialog_clear_norefresh(); + cp = variable_get_value(VAR_FTP_PATH, "Please specify the URL of a FreeBSD distribution on a\n" "remote ftp site. This site must accept either anonymous\n" "ftp or you should have set an ftp username and password\n" "in the Options screen.\n\n" "A URL looks like this: ftp:///\n" "Where is relative to the anonymous ftp directory or the\n" "home directory of the user being logged in as.", 0); - if (!cp || !*cp || !strcmp(cp, "ftp://")) { - variable_unset(VAR_FTP_PATH); - return DITEM_FAILURE | what; + if (!cp || !*cp || !strcmp(cp, "ftp://")) { + variable_unset(VAR_FTP_PATH); + return DITEM_FAILURE | DITEM_RESTORE; + } } + variable_set2(VAR_FTP_PATH, cp, 1); } if (strncmp("ftp://", cp, 6)) { msgConfirm("Sorry, %s is an invalid URL!", cp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 5:28:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 7EB9E15266 for ; Wed, 9 Jun 1999 05:27:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA32760; Wed, 9 Jun 1999 10:13:10 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA57299; Wed, 9 Jun 1999 10:12:23 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199906090912.KAA57299@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Josef Karthauser Cc: Brian Somers , Thomas David Rivers , hackers@FreeBSD.org Subject: Re: Wierd behavour from G++28! In-reply-to: Your message of "Wed, 09 Jun 1999 09:04:03 BST." <19990609090403.A79865@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Jun 1999 10:12:23 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jun 09, 1999 at 12:40:46AM +0100, Brian Somers wrote: > > > > > > Can someone comment please? Is this a bug in the way the gcc2.8 is > > > installed, or is it a bug in my understanding? (probably the latter). > > > > Perhaps you need a gcc-compiled version of libstdc++. It's just a > > guess, but when we shifted to egcs, there were all sorts of problems > > linking against the gcc-compiled version. > > > > Ok. I've compiled up a 4.0-CURRENT box, with EGCS native, and recompiled the > program. It still crashes, this time with: > > Core was generated by `search'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libstdc++.so.3...done. > Reading symbols from /usr/lib/libm.so.2...done. > Reading symbols from /usr/lib/libc.so.3...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x8053169 in __get_eh_info () at /usr/include/ctype.h:149 > 149 } > (gdb) bt > #0 0x8053169 in __get_eh_info () at /usr/include/ctype.h:149 > #1 0x8053156 in __get_eh_info () at /usr/include/ctype.h:149 > #2 0x8053132 in __get_eh_context () at /usr/include/ctype.h:149 > #3 0x8059fda in my_set::my_set (this=0x805ff9c) at search.c:64 > #4 0x804d3b9 in global constructors keyed to files () at search.c:64 > #5 0x804a5d8 in _start () > #6 0x804a25d in _init () > (gdb) > > >From search.c: > 60 char const* me; // executable name > 61 file_index files; > 62 word_index words, stop_words, meta_names; > 63 bool stem_words; > 64 string_set stop_words_found; > 65 > 66 void dump_single_word( char const *word ); > 67 void dump_word_window( char const *word, int window_size, int match ); > > I'm very confused... the programmer is convinced that it works under > other platforms, but I'm not getting any joy out of it :( If you want to send me the program source I can try it out on my boxen. > Joe > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] -- 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 Wed Jun 9 5:34:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 9029915425 for ; Wed, 9 Jun 1999 05:33:55 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 19707 invoked from network); 9 Jun 1999 12:33:50 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 9 Jun 1999 12:33:50 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id HAA00173; Wed, 9 Jun 1999 07:33:43 -0500 (EST) From: "John S. Dyson" Message-Id: <199906091233.HAA00173@dyson.iquest.net> Subject: Re: problem for the VM gurus In-Reply-To: <14174.21361.773177.526498@penny.south.mpcs.com> from Howard Goldstein at "Jun 9, 99 07:43:45 am" To: hgoldste@bbs.mpcs.com (Howard Goldstein) Date: Wed, 9 Jun 1999 07:33:43 -0500 (EST) Cc: dyson@iquest.net, 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 > John S. Dyson writes: > > Howard Goldstein said: > > > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: > > > : 4.0-CURRENT > > > > > > 3.2R too... > > > > > I just checked the source (CVS) tree, and something bad happend > > between 1.27 and 1.29 on ufs_readwrite.c. Unless other things > > had been changed to make the problem go away, the recursive vnode > > thing was broken then. > > I can pretty easily test patches and try other stuff out on a couple > of dozen brand new, architecturally (sp) stressed out (memorywise > (zero swap, 16mb RAM, mfsroot) and cpu bandwidth wise (386sx40)) 3.1-R > (switchable to 3.2R) systems, if it'd be helpful. Should it bring out > clues leading to the fix for 'the' golden page-not-present instability > it'd be awesome karma. This very limited environment is especially > fragile and highly susceptible to consistently reproducing the popular > >= 3.1R page not present panics. > BTW, one more thing that is useful for testing limited memory situations is setting the MAXMEM config variable. Last time that I looked, it allows you to set the number of K of avail mem. If you try to run with less than MAXMEM=4096 or MAXMEM=5120, you'll have troubles through. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 5:36:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 9C17615457 for ; Wed, 9 Jun 1999 05:36:09 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id IAA22459; Wed, 9 Jun 1999 08:32:52 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA20469; Wed, 9 Jun 1999 08:32:18 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id IAA12316; Wed, 9 Jun 1999 08:32:18 -0400 (EDT) Date: Wed, 9 Jun 1999 08:32:18 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906091232.IAA12316@lakes.dignus.com> To: brian@Awfulhak.org, joe@pavilion.net Subject: Re: Wierd behavour from G++28! Cc: hackers@FreeBSD.ORG, rivers@dignus.com In-Reply-To: <19990609090403.A79865@pavilion.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Wed, Jun 09, 1999 at 12:40:46AM +0100, Brian Somers wrote: > > > > > > Can someone comment please? Is this a bug in the way the gcc2.8 is > > > installed, or is it a bug in my understanding? (probably the latter). > > > > Perhaps you need a gcc-compiled version of libstdc++. It's just a > > guess, but when we shifted to egcs, there were all sorts of problems > > linking against the gcc-compiled version. > > > > Ok. I've compiled up a 4.0-CURRENT box, with EGCS native, and recompiled the > program. It still crashes, this time with: > > Core was generated by `search'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libstdc++.so.3...done. > Reading symbols from /usr/lib/libm.so.2...done. > Reading symbols from /usr/lib/libc.so.3...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x8053169 in __get_eh_info () at /usr/include/ctype.h:149 > 149 } > (gdb) bt > #0 0x8053169 in __get_eh_info () at /usr/include/ctype.h:149 > #1 0x8053156 in __get_eh_info () at /usr/include/ctype.h:149 > #2 0x8053132 in __get_eh_context () at /usr/include/ctype.h:149 > #3 0x8059fda in my_set::my_set (this=0x805ff9c) at search.c:64 > #4 0x804d3b9 in global constructors keyed to files () at search.c:64 > #5 0x804a5d8 in _start () > #6 0x804a25d in _init () > (gdb) > > >From search.c: > 60 char const* me; // executable name > 61 file_index files; > 62 word_index words, stop_words, meta_names; > 63 bool stem_words; > 64 string_set stop_words_found; > 65 > 66 void dump_single_word( char const *word ); > 67 void dump_word_window( char const *word, int window_size, int match ); > > I'm very confused... the programmer is convinced that it works under > other platforms, but I'm not getting any joy out of it :( > > Joe Sorry I can't be of more help... I'd have to add that I have a suspicion that something is still not right "library-wise"... that is, the G++ library isn't built right, or the program isn't linking right. For what it's worth - the inline __XXX functions in ctype.h do work correctly... So, I don't believe the problem isn't in the "source" per se... I'd suggest building the library with debugging enabled, linking with that and determining what is wrong. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 6:11:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scorpion.bugsoft.hik.se (scorpion.bugsoft.hik.se [194.47.165.105]) by hub.freebsd.org (Postfix) with ESMTP id 5DC1414C13 for ; Wed, 9 Jun 1999 06:11:30 -0700 (PDT) (envelope-from yottaman@writeme.com) Received: from te31002 ([194.47.173.15]) by scorpion.bugsoft.hik.se (Netscape Messaging Server 3.5) with SMTP id 169 for ; Wed, 9 Jun 1999 15:13:14 +0200 Message-ID: <003901beb279$92b169c0$0fad2fc2@te.hik.se> From: "John Andersson" To: Subject: Bad sectors on vinum volym Date: Wed, 9 Jun 1999 15:11:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have some bad sectors on my vinum volume, fsck reports the following and does not seem to be able to fix it: THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 44609178, 44609179, ***** FILE SYSTEM STILL DIRTY ***** ***** FILE SYSTEM WAS MODIFIED ***** ***** PLEASE RERUN FSCK ***** This was just a cut of the fsck output, it totally reports about 10 sectors that it can't read or write to. I tried to execute the badsect program (badsect /xxx/BAD 44609178 44609179), but it reports: Cannot find dev 061004206 corresponding to /xxx/BAD The volym in question consists of a 5 disc striped plex. Is it possible to run badsect on a vinum volym to fix this? I would prefer not to lose all data on the volym, and since it's about 40G of data I can't backup all data. I run FreeBSD 3.2-Release. It is possible to force a mount and continue to use the volym, but some directories are unaccessible. Any help would be most appreciated, John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 7:20:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web707.mail.yahoo.com (web707.mail.yahoo.com [128.11.23.27]) by hub.freebsd.org (Postfix) with SMTP id 92BA61524F for ; Wed, 9 Jun 1999 07:20:27 -0700 (PDT) (envelope-from fredv6@yahoo.fr) Message-ID: <19990609141810.23491.rocketmail@web707.mail.yahoo.com> Received: from [130.79.75.90] by web707.mail.yahoo.com; Wed, 09 Jun 1999 16:18:10 CEST Date: Wed, 9 Jun 1999 16:18:10 +0200 (CEST) From: Frederic SOULIER Subject: splimp, splnet, ... ? To: freebsd-hackers@freebsd.org 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 Hi there, I'm a newbie in kernel programming, Could someone help me to know in which case should I use splimp, splnet, etc .. levels. I have to copy entirely some mbuf chains and to allocate memory in IP layer. I do not use any specific level (no splxxx), but I think my kernel is not very very stable :) Where can I get some info for that ? Thanks in advance, Fred. PS : Since I'm not in the list please answer to my e-mail. === ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Frederic SOULIER - CS & Networks student @ ULP - FRANCE e-mail : fredv6@yahoo.fr, soulier@dess-info.u-strasbg.fr web : http://dess-info.u-strasbg.fr/~soulier ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ___________________________________________________________ Do You Yahoo!? Votre e-mail @yahoo.fr gratuit sur http://courrier.yahoo.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 8:51:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [209.90.128.250]) by hub.freebsd.org (Postfix) with ESMTP id 0961E14E31 for ; Wed, 9 Jun 1999 08:51:34 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id LAA79929 for hackers@freebsd.org; Wed, 9 Jun 1999 11:59:52 -0400 (EDT) Date: Wed, 9 Jun 1999 11:59:51 -0400 From: Dan Moschuk To: hackers@freebsd.org Subject: hundreds of sockets stuck in TIME_WAIT Message-ID: <19990609115951.A79834@trinsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed on a very high traffic'd webserver, I have just over 4000 sockets stuck in the TIME_WAIT state. Ideally, I want to "bend" the RFC a bit and close the descriptor before it hits that state, or, ignore the 2MSL wait when it enters that state. I take it there is no sysctl switch to trigger this, so, am I going kernel diving? -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 10:20:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id CB5AA14D3E for ; Wed, 9 Jun 1999 10:19:57 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id NAA19889 for ; Wed, 9 Jun 1999 13:08:29 -0400 Date: Wed, 9 Jun 1999 13:08:29 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: What is FTW? 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 In the FAQ of FreeBSD 2.X, 13.12. Alternative layout policies for directories, there is the following sentence: Most filesystems are created from archives that were created by a depth first search (aka ftw). What does ftw stand for (My guess is File Tree Walk)? Can anyone give me examples of programs that create archives from a file tree in a depth first way? Do these programs rebuild the file tree from archive exactly as they were created? Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 10:42:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id E6C2614D23 for ; Wed, 9 Jun 1999 10:42:12 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id TAA02139; Wed, 9 Jun 1999 19:35:15 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id TAA35432; Wed, 9 Jun 1999 19:41:37 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id TAA57133; Wed, 9 Jun 1999 19:42:23 +0200 (CEST) (envelope-from ticso) Date: Wed, 9 Jun 1999 19:42:23 +0200 From: Bernd Walter To: John Andersson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Bad sectors on vinum volym Message-ID: <19990609194223.A57095@cicely8.cicely.de> References: <003901beb279$92b169c0$0fad2fc2@te.hik.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <003901beb279$92b169c0$0fad2fc2@te.hik.se>; from John Andersson on Wed, Jun 09, 1999 at 03:11:23PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 09, 1999 at 03:11:23PM +0200, John Andersson wrote: > I seem to have some bad sectors on my vinum volume, fsck reports the > following and does not seem to be able to fix it: > THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 44609178, 44609179, > > ***** FILE SYSTEM STILL DIRTY ***** > ***** FILE SYSTEM WAS MODIFIED ***** > ***** PLEASE RERUN FSCK ***** > > This was just a cut of the fsck output, it totally reports about 10 sectors > that it can't read or write to. > I tried to execute the badsect program (badsect /xxx/BAD 44609178 44609179), > but it reports: > Cannot find dev 061004206 corresponding to /xxx/BAD > > The volym in question consists of a 5 disc striped plex. > Is it possible to run badsect on a vinum volym to fix this? > I would prefer not to lose all data on the volym, and since it's about 40G > of data I can't backup all data. > I run FreeBSD 3.2-Release. > It is possible to force a mount and continue to use the volym, but some > directories are unaccessible. > Under which version did you create the volume? I remember a problem in the sizecalculation in early vinum versions. You should check the sector numbers and compare them to the partitionsizes? As far as I know bassect has a limited number of bad sectors it can handle, so I asume the problem range is to big. > Any help would be most appreciated, > John. > -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 10:55: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id C0F4514F13 for ; Wed, 9 Jun 1999 10:55:03 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA13333; Wed, 9 Jun 1999 10:55:00 -0700 (PDT) Message-Id: <199906091755.KAA13333@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Dan Moschuk Cc: hackers@freebsd.org Subject: Re: hundreds of sockets stuck in TIME_WAIT In-Reply-To: Your message of "Wed, 09 Jun 1999 11:59:51 EDT." <19990609115951.A79834@trinsec.com> X-Url: http://www.isi.edu/~faber Date: Wed, 09 Jun 1999 10:55:00 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Dan Moschuk wrote: > >I noticed on a very high traffic'd webserver, I have just over 4000 sockets >stuck in the TIME_WAIT state. Ideally, I want to "bend" the RFC a bit and >close the descriptor before it hits that state, or, ignore the 2MSL wait >when it enters that state. Are they casuing you a problem? If so, what? I'm interested because I wrote a paper about this problem (http://www.isi.edu/~faber/pubs/html/infocom99/ for the html, http://www.isi.edu/~faber/pubs/time_wait.ps for postscript) and various people have told me that although the PCBs pile up, the performance effects are minimal in a reasonable OS (specifically in FreeBSD). And more directly for you, if they're not harming your performance, I wouldn't do *anything*. They do serve a purpose. > >I take it there is no sysctl switch to trigger this, so, am I going >kernel diving? I don't think there is one. Although I don't think it's a good idea to turn off the TW state, I think it's pretty easy to do so. I'm going to be away from my email for a few days, so don't be surprised if you respond and don't hear from me immediately. If folks have evidence that accumulating TW states cause a performance problem (although I doubt they do), I would love to know about it. - -- - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBN16qc4b4eisfQ5rpAQEregP/T/AjHQMX0mKdtSKKsmIxE7RI32UxMIV0 1tKS5mEshWwO4Y7PtGrbFHuGYBh9D1PnDcKbHZ9PI/j54zM/yfTYvhkiIsamM4G2 B4/kUPRMzrWQCPX8hKSe3zYz7ZoHjI/mHWj+i3AW18rMtA1M6AoQrNOMyyQFFu8I I4XF9dyFYGE= =6L+A -----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 Wed Jun 9 11:38:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from abalaea.ircache.net (abalaea.scd.ucar.edu [128.117.28.9]) by hub.freebsd.org (Postfix) with ESMTP id 1A91015564 for ; Wed, 9 Jun 1999 11:38:16 -0700 (PDT) (envelope-from glenn@abalaea.ircache.net) Received: from localhost (glenn@localhost) by abalaea.ircache.net (8.9.2/8.9.1) with ESMTP id MAA20169; Wed, 9 Jun 1999 12:37:13 -0600 (MDT) (envelope-from glenn@abalaea.ircache.net) Date: Wed, 9 Jun 1999 12:37:13 -0600 (MDT) From: Glenn Chisholm To: Ted Faber Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: hundreds of sockets stuck in TIME_WAIT In-Reply-To: <199906091755.KAA13333@boreas.isi.edu> 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 > And more directly for you, if they're not harming your performance, I > wouldn't do *anything*. They do serve a purpose. > When benchmarking proxies we find the MSL creates a resource problem for us with Web Polygraph (http://polygraph.ircache.net/). I must admit that we have never measured this as a performance issue. However I believe that Pei Cao's group has and found it to be one due to the way sockets were maintained in the kernel. I will look for a reference for their work. I think that one of her students submitted a patch to correct this issue in FreeBSD, so it may not be a problem in 3.1/3.2. If you do want to hack the MSL : /usr/src/sys/netinet/tcp_timer.h #define TCPTV_MSL ( 3*PR_SLOWHZ) /* max seg lifetime (hah!) */ That will make the MSL 3 seconds. glenn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 12:35:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 4500F15188 for ; Wed, 9 Jun 1999 12:35:08 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA22540 for ; Wed, 9 Jun 1999 14:35:08 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id OAA06443; Wed, 9 Jun 1999 14:35:06 -0500 Message-ID: <19990609143506.11961@right.PCS> Date: Wed, 9 Jun 1999 14:35:06 -0500 From: Jonathan Lemon To: hackers@freebsd.org Subject: Re: hundreds of sockets stuck in TIME_WAIT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >> And more directly for you, if they're not harming your performance, I >> wouldn't do *anything*. They do serve a purpose. >> > >When benchmarking proxies we find the MSL creates a resource problem for >us with Web Polygraph (http://polygraph.ircache.net/). > >I must admit that we have never measured this as a performance issue. >However I believe that Pei Cao's group has and found it to be one due to >the way sockets were maintained in the kernel. I will look for a reference >for their work. I think that one of her students submitted a patch to >correct this issue in FreeBSD, so it may not be a problem in 3.1/3.2. It does become a problem under high load, since the kernel still has to check all the sockets in TIME_WAIT. I have a patch that resolves this problem, but need to integrate it with some of the work that Garret has done. If you need the patch now, look for it on the archives of the freebsd-net mailing list. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 12:53:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from origo.hik.se (origo.hik.se [194.47.161.7]) by hub.freebsd.org (Postfix) with ESMTP id 0CA8B154D1 for ; Wed, 9 Jun 1999 12:53:40 -0700 (PDT) (envelope-from yottaman@writeme.com) Received: from dragon (dragon.bugsoft.hik.se [194.47.165.9]) by origo.hik.se (8.8.8/8.8.8) with SMTP id VAA14038 for ; Wed, 9 Jun 1999 21:53:39 +0200 (MET DST) Message-ID: <006001beb2b1$763d0aa0$09a52fc2@bugsoft.hik.se> From: "John Andersson" To: References: <003901beb279$92b169c0$0fad2fc2@te.hik.se> <19990609205956.B57243@cicely8.cicely.de> Subject: Re: Bad sectors on vinum volym Date: Wed, 9 Jun 1999 21:51:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your response, you are probably right. I created the vinum volym under the 3.1 release (or it may have been the 3.0 release) and I maximized the partition size to the last block with trial and error. When checking the sector number returned by fsck (44609178, ...), it seems to be exactly at the end of the partition size (4460918k per subdrive), altough I have not done the math completly, there seems to be some relation. It would be very interesting to try to use your tool to decrease the filesystem size (or the subdrive size in the plex?). Does it work with vinum too? Either way, this is good news, since there problably does not exists any bad sectors, just some error in the partition size calculation and a complete reconstruction of the vinum volym would fix all problem (hopefully... ;-). /John ----- Original Message ----- From: Bernd Walter To: John Andersson Sent: Wednesday, June 09, 1999 8:59 PM Subject: Re: Bad sectors on vinum volym > On Wed, Jun 09, 1999 at 03:11:23PM +0200, John Andersson wrote: > > I seem to have some bad sectors on my vinum volume, fsck reports the > > following and does not seem to be able to fix it: > > THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 44609178, 44609179, > > > > ***** FILE SYSTEM STILL DIRTY ***** > > ***** FILE SYSTEM WAS MODIFIED ***** > > ***** PLEASE RERUN FSCK ***** > > > > This was just a cut of the fsck output, it totally reports about 10 sectors > > that it can't read or write to. > > I tried to execute the badsect program (badsect /xxx/BAD 44609178 44609179), > > but it reports: > > Cannot find dev 061004206 corresponding to /xxx/BAD > > > > The volym in question consists of a 5 disc striped plex. > > Is it possible to run badsect on a vinum volym to fix this? > > I would prefer not to lose all data on the volym, and since it's about 40G > > of data I can't backup all data. > > I run FreeBSD 3.2-Release. > > It is possible to force a mount and continue to use the volym, but some > > directories are unaccessible. > > > Maybe there is a way to recover the partition without the need to restore > the data (backup would be still a good idea). > If it's the old sizeproblem it should be possible with the new volumesize to > which the recent vinum corrected the partition to use a tool I've written > during the last weeks. > > The tool is build to increase a filesystem after the partition it is on > was increased too. > It should be possible to decrease the filesystem so it won't refer to the > unavailable sectors anymore. > A fsck run after that should remove all references (files, ...) to these > blocks. > My tools still has some bugs - but the won't appear when decreasing the fs. > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de info@cosmo-project.de > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 13:56:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ouch.Oof.NET (ouch.Oof.net [208.212.72.34]) by hub.freebsd.org (Postfix) with ESMTP id 6E40415165 for ; Wed, 9 Jun 1999 13:56:13 -0700 (PDT) (envelope-from marko@Oof.NET) Received: ([[POCMAIL: sender unrevealed]]) œby ouch.Oof.NET (POCmail v4.0) id QAA04847; Wed, 9 Jun 1999 16:56:12 -0400 (EDT) X-POCmail-Authentication-Notice: Unverified sender address. If you NEED to verify, contact . Message-ID: <19990609165612.H6847@oof.net> Date: Wed, 9 Jun 1999 16:56:12 -0400 From: razzle dazzle root beer To: hackers@freebsd.org Subject: accellerated X 5.0 multihead on 3.2-stable with matrox mil G200 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've got an asus XG-DLS dual xeon mainboard with two matrox millenium G200 pci boards with 16 megs of ram each and I'm trying to run Accelerated X v5 on freebsd 3.2-stable. First, I was wondering if anyone else out there is successfully running multihead accelX 5 on freebsd 3+. It seems to initialize both cards, but the secondary one seems out of sync. Xi Graphics still says they dont support freebsd3, but I have heard rumours of people sucessfully running it. Also, even in single monitor more, accelX is extremely slow compared to Xfree, so much that it is practically useless. I suppose I could install freebsd2.2 but I'd give up the second Xeon processor then. :( Any help or information would be greatly appreciated. Thanks. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 14:12:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 68584151E8 for ; Wed, 9 Jun 1999 14:12:28 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.9.3/8.9.3) with ESMTP id PAA47037; Wed, 9 Jun 1999 15:12:24 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Wed, 9 Jun 1999 15:12:23 -0600 (MDT) From: Brian Handy To: razzle dazzle root beer Cc: hackers@FreeBSD.ORG Subject: Re: accellerated X 5.0 multihead on 3.2-stable with matrox mil G200 In-Reply-To: <19990609165612.H6847@oof.net> Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Also, even in single monitor more, accelX is extremely slow compared to Xfree, >so much that it is practically useless. I suppose I could install freebsd2.2 >but I'd give up the second Xeon processor then. :( Wow, is this true? In the past on my machine (MM II w/ 8MB) I found the Xig server to be a hair faster than XFree86. That was only using one machine, and using Xaccel 4.x. Seems strange it would slow down so significantly. I haven't tried doing it under >=3.2 yet, and I may not. I'm holding out for XFree 4.0 with overlay visuals before I plunk down more money for the server. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 14:34:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BD7AA14BCE for ; Wed, 9 Jun 1999 14:34:37 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10rpzY-0005uE-00 for hackers@freebsd.org; Wed, 09 Jun 1999 23:34:36 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Supprting twist for inetd with libwrap Date: Wed, 09 Jun 1999 23:34:36 +0200 Message-ID: <22705.928964076@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm currently working on our libwrap support in inetd. Working with the originators of a few PR's, I've come up with a diff that gets most of what we need right, including the severity option of hosts_options. I'm taking on hosts_options' twist now. The problem with twist is that it execl()'s, which isn't at all cool for the listening inetd (it's not a problem for forked inetd processes). I've put something together that teaches tcp_wrappers' hosts_access() to allow the caller to frob a flag called fork_on_twist. If the flag is set, twist_option() (the function that does the execl) will fo a fork before the execl, with the child doing the execl and the parent failing hosts_access. It suddenly occured to me while I was testing this that I might be going to a lot of trouble under the misguided assumption that a fork is expensive. Am I wrong? Inetd already forks for some internal services and for all external services, so the only extra forks would be for a few of the internal services. Would there be a noticeable impact on inetd's if it _always_ forked before calling hosts_access()? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 16:28:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 062D314EFC for ; Wed, 9 Jun 1999 16:28:56 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id TAA42190; Wed, 9 Jun 1999 19:28:54 -0400 (EDT) Date: Wed, 9 Jun 1999 19:28:53 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Supprting twist for inetd with libwrap In-Reply-To: <22705.928964076@axl.noc.iafrica.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 One of the nice things about Unix has always been low process-spawning overhead. FreeBSD should do quite well, especially, since it is demand-paged and a fork doesn't actually copy much, just the vm map and makes everything COW. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 16:30:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5523F14EFC for ; Wed, 9 Jun 1999 16:30:28 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10rrnf-00079i-00 for hackers@freebsd.org; Thu, 10 Jun 1999 01:30:27 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Re: Supprting twist for inetd with libwrap (solved) In-reply-to: Your message of "Wed, 09 Jun 1999 23:34:36 +0200." <22705.928964076@axl.noc.iafrica.com> Date: Thu, 10 Jun 1999 01:30:27 +0200 Message-ID: <27509.928971027@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 09 Jun 1999 23:34:36 +0200, Sheldon Hearn wrote: > It suddenly occured to me while I was testing this that I might be > going to a lot of trouble under the misguided assumption that a fork is > expensive. Am I wrong? Please disregard my previous post. I was working around a bug I introduced myself. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 17:41:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web107.yahoomail.com (web107.yahoomail.com [205.180.60.74]) by hub.freebsd.org (Postfix) with SMTP id 0836B15455 for ; Wed, 9 Jun 1999 17:41:48 -0700 (PDT) (envelope-from robertbutler@yahoo.com) Message-ID: <19990610004236.16517.rocketmail@web107.yahoomail.com> Received: from [205.226.11.3] by web107.yahoomail.com; Wed, 09 Jun 1999 17:42:36 PDT Date: Wed, 9 Jun 1999 17:42:36 -0700 (PDT) From: Robert Butler Subject: ISDN in freebsd? To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody know where I can get the source code of ISDN support in freebsd? Robert _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 17:53:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id C975915455 for ; Wed, 9 Jun 1999 17:53:52 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip126.houston14.tx.pub-ip.psi.net [38.27.214.126]) by leap.innerx.net (Postfix) with ESMTP id E5F5E370A4; Wed, 9 Jun 1999 20:53:47 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id TAA88584; Wed, 9 Jun 1999 19:52:54 -0500 (CDT) (envelope-from chris) Date: Wed, 9 Jun 1999 19:52:54 -0500 From: Chris Costello To: Robert Butler Cc: hackers@FreeBSD.ORG Subject: Re: ISDN in freebsd? Message-ID: <19990609195253.L57174@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990610004236.16517.rocketmail@web107.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990610004236.16517.rocketmail@web107.yahoomail.com>; from Robert Butler on Wed, Jun 09, 1999 at 05:42:36PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 9, 1999, Robert Butler wrote: > Anybody know where I can get the source code of ISDN > support in freebsd? ftp://ftp.freebsd.org/pub/FreeBSD/branches/-current/src/usr.sbin/i4b/ http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/i4b > > Robert > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Chris Costello All new: The software is not compatible with previous versions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 18:36:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from colnta.acns.ab.ca (clgr000532.hs.telusplanet.net [161.184.82.24]) by hub.freebsd.org (Postfix) with ESMTP id 105E514D9E for ; Wed, 9 Jun 1999 18:36:24 -0700 (PDT) (envelope-from davidc@acns.ab.ca) Received: from acns.ab.ca (localhost [127.0.0.1]) by colnta.acns.ab.ca (8.9.3/8.9.3) with ESMTP id TAA19754 for ; Wed, 9 Jun 1999 19:35:44 GMT (envelope-from davidc@acns.ab.ca) Message-ID: <375EC210.C3AA6E5@acns.ab.ca> Date: Wed, 09 Jun 1999 19:35:44 +0000 From: Chad David Organization: ACNS Inc. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Oracle OCI code on FreeBSD 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 managed to install Oracle 8.0.5 on FreeBSD 3.2-STABLE, and everything seems to be fine, but I am unable to run an OCI program that I am porting from Solaris. I started out with unresolved symbols in libclntsh.so, and I "got ride" of them by relinking libclntsh.so against /usr/compat/linux/lib/libc.so.6. The OCI specific code is compiled into a shared object, and is loaded into my program via dlopen() / dlsym(), which leaves me wondering what happens when a Linux shared object is loaded into a FreeBSD process? Is this possible (linking against linux/lib/libc.so.6) or am I completely out to lunch? Has anybody managed to get an OCI program running on FreeBSD? When I run the program I get hit with SIGBUS as soon as the symbol in my shared object is called. I am not really sure what other details would be helpful, but if anyone is at all interested in the I would be happy to supply more :). Chad David davidc@guild.ab.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 9 21:14:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 83A8214D6F for ; Wed, 9 Jun 1999 21:14:51 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id XAA37296; Wed, 9 Jun 1999 23:14:47 -0500 (CDT) (envelope-from dan) Date: Wed, 9 Jun 1999 23:14:47 -0500 From: Dan Nelson To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Oracle OCI code on FreeBSD Message-ID: <19990609231446.A37094@dan.emsphone.com> References: <375EC210.C3AA6E5@acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <375EC210.C3AA6E5@acns.ab.ca>; from "Chad David" on Wed Jun 9 19:35:44 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 09), Chad David said: > I have managed to install Oracle 8.0.5 on FreeBSD 3.2-STABLE, and > everything seems to be fine, but I am unable to run an OCI program > that I am porting from Solaris. I started out with unresolved > symbols in libclntsh.so, and I "got rid" of them by relinking > libclntsh.so against /usr/compat/linux/lib/libc.so.6. > > The OCI specific code is compiled into a shared object, and is loaded > into my program via dlopen() / dlsym(), which leaves me wondering > what happens when a Linux shared object is loaded into a FreeBSD > process? Is this possible (linking against linux/lib/libc.so.6) or > am I completely out to lunch? Has anybody managed to get an OCI > program running on FreeBSD? Won't work. stdio is completely different from BSD<->Linux, so no fread/fwrite calls will work, struct direct is different (scratch opendir), ioctls are certainly different, errnos don't map the same, signals are different, etc etc etc. > When I run the program I get hit with SIGBUS as soon as the symbol in > my shared object is called. I am not really sure what other details > would be helpful, but if anyone is at all interested in the I would > be happy to supply more :). Install the linux_devel port and resign yourself to building Linux executables whenever you have to talk to Oracle. -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 Wed Jun 9 23:18:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0067214D62 for ; Wed, 9 Jun 1999 23:18:45 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10ryAT-000BKQ-00; Thu, 10 Jun 1999 08:18:25 +0200 From: Sheldon Hearn To: Dan Nelson Cc: Chad David , freebsd-hackers@FreeBSD.ORG Subject: Re: Oracle OCI code on FreeBSD In-reply-to: Your message of "Wed, 09 Jun 1999 23:14:47 EST." <19990609231446.A37094@dan.emsphone.com> Date: Thu, 10 Jun 1999 08:18:25 +0200 Message-ID: <43549.928995505@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 09 Jun 1999 23:14:47 EST, Dan Nelson wrote: > Install the linux_devel port and resign yourself to building Linux > executables whenever you have to talk to Oracle. We've _just_ been through this whole nightmare and resigned ourselves to using a Sparc for talking to Oracle. :-( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 1:43:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id 04A6914BF1 for ; Thu, 10 Jun 1999 01:43:26 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from isjhbex01.is.co.za (isjhbex01.is.co.za [196.26.1.16]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id IAA10431 for ; Thu, 10 Jun 1999 08:28:48 +0200 Received: by isjhbex01.is.co.za with Internet Mail Service (5.5.2232.9) id ; Thu, 10 Jun 1999 08:31:01 +0200 Message-ID: <3D5EC7D2992BD211A95600A0C9CE047F0308DB6C@isjhbex01.is.co.za> From: Geoff Rehmet To: "'hackers@freebsd.org'" Subject: FTP mirror at the Internet Solution (South Africa) Date: Thu, 10 Jun 1999 08:30:58 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We are in the process of commissioning the new Internet Solution ftp site, and it now looks like the FreeBSD mirror is out of its previous state of total disrepair. (see ftp://ftp.is.co.za/pub/FreeBSD) If anyone notices problems, please let me know, or email ftp-admin@is.co.za. We should be going fully live by Monday. For those who are interested - we are currently housing our ftp data on a Netapp F740, where the ftp data occupies a 80G partition. (Unfortunately, we've already filled it!) regards, Geoff Rehmet (Infrastructure Manager, the Internet Solution) -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 2:57: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8A11B14EAA for ; Thu, 10 Jun 1999 02:57:00 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA24287; Thu, 10 Jun 1999 11:56:57 +0200 (CEST) (envelope-from des) To: Arun Sharma Cc: Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: linux and freebsd kernels conceptually different? References: <199906071558.RAA17138@gil.physik.rwth-aachen.de> From: Dag-Erling Smorgrav Date: 10 Jun 1999 11:56:57 +0200 In-Reply-To: Arun Sharma's message of "07 Jun 1999 12:20:56 -0700" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arun Sharma writes: > I'd say most of the differences are in implementation and development > methodology. Linux camp seems to be proud of breaking traditions and > concepts invented after lengthy research. I haven't seen that many > iconoclasts in my short encounter with FreeBSD. You say that as if it's a good thing... I'd amend it to "The Linux camp seems to think it's a good idea to ignore countless man-years of research and development in the field of OS design, and make the same mistakes other people have made, corrected and documented years before them. I haven't seen that many ignorants in my short encounter with FreeBSD." DES -- Dag-Erling Smorgrav - des@flood.ping.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 Jun 10 3:22:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id C7FA214F9B for ; Thu, 10 Jun 1999 03:22:57 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id DAA27419; Thu, 10 Jun 1999 03:17:59 -0700 (PDT) From: Bill Huey Message-Id: <199906101017.DAA27419@mag.ucsd.edu> Subject: Re: linux and freebsd kernels conceptually different? To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Thu, 10 Jun 1999 03:17:58 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Dag-Erling Smorgrav" at Jun 10, 99 11:56:57 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 say that as if it's a good thing... I'd amend it to "The Linux > camp seems to think it's a good idea to ignore countless man-years of > research and development in the field of OS design, and make the same > mistakes other people have made, corrected and documented years before > them. I haven't seen that many ignorants in my short encounter with > FreeBSD." It's a good thing because assumptions about memory useage within the kernel, portability abstractions, internal buffer queue overhead, etc..., need to reexamined to see if they are still relevant. This is always good, assuming that this is done properly with peer review and that folks listen to it. The Linux kernel is quite good in many areas and doesn't deserve the rap that the FreeBSD folks dump onto it. Alost every problematic area, VM, NFS is actively worked on by many qualified folks. The source is very well documented and relatively easy to read. > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 4:20: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with ESMTP id 8DDD114F1B for ; Thu, 10 Jun 1999 04:19:56 -0700 (PDT) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.3/8.9.1) with SMTP id IAA06723 for ; Thu, 10 Jun 1999 08:19:55 -0300 (EST) Date: Thu, 10 Jun 1999 08:19:55 -0300 (EST) From: Paulo Fragoso To: hackers@freebsd.org Subject: PAM + pppd + Radius 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've got a problem with pppd + pam: pppd[304]: no modules loaded for `ppp' service pppd[304]: PAP login failure for ... I've recompiled pppd with -DUSE_PAM, and I've added in pam.conf this: ppp auth required pam_radius.so try_first_pass What is wrong? What does "no modules" mean? Are there anyone using PAM with pppd? Can anyone help me to configure pppd work with PAM? Thanks, Paulo Fragoso. ps.: I'm using radius athentication for login and it's works fine with this line (in pam.conf): login auth required pam_radius.so try_first_pass ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 5:57:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 6421C14CA1; Thu, 10 Jun 1999 05:57:35 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn29.imasy.or.jp [202.227.24.221]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id VAA16619; Thu, 10 Jun 1999 21:57:28 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199906101257.VAA16619@tasogare.imasy.or.jp> To: freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: apmd for FreeBSD X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 10 Jun 1999 21:55:46 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 235 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, folks. graham> ooh apmd, cool. graham> I was wondering if someone had started somthing like this, I'm excited. Sorry to late, now first version of apmd package for FreeBSD is available at apmd(8): http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-usr.sbin.tar.gz 3.2-RELEASE kernel patch: http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-sys-R320.diff.gz if you are using PAO3, kernel patch would be PAO3 kernel patch: http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-sys-PAO3.diff.gz The kernel patches for 2.2-STABLE and -CURRENT are not available for now. Please make contact with me if you need them. Any comments, suggestions, bug-reports, improvements are very much appreciated. I'm looking forward working with you :-) ------------------------------------------------------------------- FreeBSD apmd Package Release Notes (19990610 version) 1. What's apmd package ====================== This apmd package provides a means of handling various APM events from userland code. From apmd.conf, the apmd(8) configuration file, you can select the APM events to be handled from userland and specify the commands for a given event, allowing APM behaviour to be configured flexibly. 2. How to install the apmd package ================================== 2.1 Making the apmd control device file --------------------------------------- apmd(8) uses the new special device file /dev/apmctl. You should create the device file before using apmd as follows: # cd /dev # mknod apmctl c 39 8 2.2 Applying the kernel patch and building a new kernel ------------------------------------------------------- The next step is to apply the patch against the sys source tree. Go to the source directory (eg. /usr/src/ or /usr/PAO3/src/) and run the patch command as follows: # gzip -cd [somewhere]/apmd-sys-R320.diff | patch For PAO3 users, the patch file name would be apmd-sys-PAO3.diff instead of apmd-sys-R320.diff. After this step has completed successfully, build and install a new kernel and reboot your system. 2.3 Making the apmd program --------------------------- Go to src/usr.sbin/ and extract the apmd tarball as follows: # tar xzpvf [somewhere]/apmd-usr.sbin.tar.gz Before doing a make all, you need to copy apm_bios.h in the sys source tree to /usr/include/machine/ first: # cp /sys/i386/include/apm_bios.h /usr/include/machine/ Then do the build and install steps in the apmd directory: # cd src/usr.sbin/apmd # make depend all install 2.4 Setting up the configuration file and userland script --------------------------------------------------------- In src/usr.sbin/apm/etc/ there are example configuration and userland script files which are invoked automatically when the APM BIOS informs apmd of an event, such as suspend request. Copy these files to /etc/apm as follows: # mkdir /etc/apm # cp src/usr.sbin/apm/etc/* /etc/apm/ 3. Running the apmd daemon program ================================== To run apmd(8) in background mode, simply type ``apmd''. # apmd To make a running apmd reload /etc/apm/apmd.conf, send a SIGHUP signal to the apmd(8) process. # kill -HUP [apmd pid] or # killall -HUP apmd apmd has some command line options. For the detials, please refer to the source code :-) 4. Configuration file ===================== The structure of the apmd configuration file is quite simple. For example: apm_event SUSPENDREQ { exec "sync && sync && sync"; exec "sleep 1"; exec "zzz"; } Will cause apmd to recieve the APM event SUSPENDREQ (which may be posted by an LCD close), run the sync command 3 times and wait for a while, then execute zzz (apm -z) to put the system in the suspend state. 4.1 The apm_event keyword ------------------------- `apm_event' is the keyword which indicates the start of configuration for each events. 4.2 APM events -------------- `SUSPENDREQ' is one of the APM event names. You can specify 2 or more events delimited by a comma, executing the same commands for these events. The following are available event names: o Events ignored by the kernel if apmd is running: STANDBYREQ SUSPENDREQ USERSUSPENDREQ BATTERYLOW o Events passed to apmd after kernel handling: NORMRESUME CRITRESUME STANDBYRESUME POWERSTATECHANGE UPDATETIME Other events will not be sent to apmd. 4.3 command line syntax ----------------------- In our example, the next 3 lines begining with `exec' are commands for the event. Each line should be terminated with a semicolon. The command list for the event should be enclosed by `{' and `}'. apmd(8) uses /bin/sh for double-quotation enclosed command execution, just as with system(3). Each command is executed in order until the end of the list is reached or a command finishes with a non-zero status code. apmd(8) will report any failing command's status code via syslog(3). 4.4 Built-in functions ---------------------- You can also specify apmd built-in functions instead of command lines. A built-in function name should be terminated with a semicolon, just as with a command line. The following built-in functions are currently supported: o reject; Reject last request posted by APM BIOS. This can be used to reject a SUSPEND request when the LCD is closed and put the system in a STANDBY state instead. 5. SAMPLES ========== apm_event SUSPENDREQ { exec "/etc/apm/rc.suspend"; } apm_event USERSUSPENDREQ { exec "sync && sync && sync"; exec "sleep 1"; exec "apm -z"; } apm_event NORMRESUME, STANDBYRESUME { exec "/etc/apm/rc.resume"; } # resume event configuration for serial mouse users by # reinitializing a moused(8) connected to a serial port. # #apm_event NORMRESUME { # exec "kill -HUP `cat /var/run/moused.pid`"; #} # suspend request event configuration for ATA HDD users: # execute standby instead of suspend. # #apm_event SUSPENDREQ { # reject; # exec "sync && sync && sync"; # exec "sleep 1"; # exec "apm -Z"; #} 6. Call for developers ====================== The initial version of apmd(8) was implemented primarily to test the kernel support code and was ALPHA quality. Based on that code, the current version was developed by KOIE Hidetaka . We, however, are still groping the features of apmd and its implementation, also inviting your ideas. Documenation is also sparse, and the manpages have not yet been written. We are looking for people who can collaborate with me on this work: Please e-mail iwasaki@jp.freebsd.org if you are interested in working on this. June 1, 1999 Created by: iwasaki@jp.FreeBSD.org Edited by: jkh@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 6:17:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 56F4514F0D; Thu, 10 Jun 1999 06:17:00 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id OAA12528 Thu, 10 Jun 1999 14:16:56 +0100 (BST) Message-ID: <375FBAC9.1C071969@cs.strath.ac.uk> Date: Thu, 10 Jun 1999 14:16:57 +0100 From: Roger Hardiman Organization: Strathclyde University X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.2-STABLE i386) MIME-Version: 1.0 To: multimedia@freebsd.org, hackers@freebsd.org Cc: sos@freebsd.org Subject: IR Remote for AverMedia and FlyVideo Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Several people have asked my recently about supporting the AverMedia remote control and the FlyVideo Remote Control units for their Bt848/Bt878 TV cards. Well, I finally got a reply from AverMedia and after checking on the Linux Infra Red Controller (LIRC) web site, I found the source and specs for the AverMedia and FlyVideo IR modules. I do not have AverMedia or Flyvideo hardware, so I'm not going to look into it, but if owner/hackers of these cards want to knock something up for the Bt848 driver, I'll gladly add it in along side the Hauppauge IR support we already have. Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 7:44:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id BC51115301 for ; Thu, 10 Jun 1999 07:44:29 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id JAA00652; Thu, 10 Jun 1999 09:43:24 -0500 (EST) (envelope-from toor) Message-Id: <199906101443.JAA00652@dyson.iquest.net.> Subject: Re: linux and freebsd kernels conceptually different? In-Reply-To: from Dag-Erling Smorgrav at "Jun 10, 1999 11:56:57 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Thu, 10 Jun 1999 09:43:24 -0500 (EST) Cc: adsharma@home.com (Arun Sharma), kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies), hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Dag-Erling Smorgrav said: > Arun Sharma writes: > > I'd say most of the differences are in implementation and development > > methodology. Linux camp seems to be proud of breaking traditions and > > concepts invented after lengthy research. I haven't seen that many > > iconoclasts in my short encounter with FreeBSD. > > You say that as if it's a good thing... I'd amend it to "The Linux > camp seems to think it's a good idea to ignore countless man-years of > research and development in the field of OS design, and make the same > mistakes other people have made, corrected and documented years before > them. I haven't seen that many ignorants in my short encounter with > FreeBSD." > Anyone that I work with would tell you that I spend MUCH too MUCH time reading technical reports from any available source. I regret knowing only English though (and can read French passably.) It is very important to look at what others have done, because it is quite arrogant to assume that one can create as effectively as the sum of everyone else!!! -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 10:15:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 703F314D6B for ; Thu, 10 Jun 1999 10:15:38 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id NAA00235; Thu, 10 Jun 1999 13:16:19 -0400 (EDT) Message-Id: <199906101716.NAA00235@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 10 Jun 1999 12:11:46 -0400 To: dyson@iquest.net, des@flood.ping.uio.no (Dag-Erling Smorgrav) From: Dennis Subject: Re: linux and freebsd kernels conceptually different? Cc: adsharma@home.com (Arun Sharma), kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies), hackers@FreeBSD.ORG In-Reply-To: <199906101443.JAA00652@dyson.iquest.net.> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:43 AM 6/10/99 -0500, John S. Dyson wrote: >Dag-Erling Smorgrav said: >> Arun Sharma writes: >> > I'd say most of the differences are in implementation and development >> > methodology. Linux camp seems to be proud of breaking traditions and >> > concepts invented after lengthy research. I haven't seen that many >> > iconoclasts in my short encounter with FreeBSD. >> >> You say that as if it's a good thing... I'd amend it to "The Linux >> camp seems to think it's a good idea to ignore countless man-years of >> research and development in the field of OS design, and make the same >> mistakes other people have made, corrected and documented years before >> them. I haven't seen that many ignorants in my short encounter with >> FreeBSD." LOL...these are my thoughts exactly. Linux is what you would do the first time you did something without much experience. They finally caved in on spl type mechanisms, though the mechanisms provided in v2.2 are very crude. Worst of all, most of the OS is undocumented and if you dont ask Alan Cox (or he doesnt feel like giving you an answer) then you are pretty much in the dark. If they would just do it right rather than re-writing the thing every year, but I have little hope. I cant even convince them that is it unreasonable to panic the system because 1 buffer doesnt have enough room for a header. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 10:53:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with ESMTP id C560714D46 for ; Thu, 10 Jun 1999 10:53:51 -0700 (PDT) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.3/8.9.1) with SMTP id OAA22913 for ; Thu, 10 Jun 1999 14:53:49 -0300 (EST) Date: Thu, 10 Jun 1999 14:53:49 -0300 (EST) From: Paulo Fragoso To: hackers@freebsd.org Subject: PAM + pppd + Radius(2) 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, Now I've solved modules problem with pppd. My pam.conf is this: login auth sufficient pam_skey.so login auth requisite pam_cleartext_pass_ok.so login auth required pam_unix.so try_first_pass ppp auth required pam_unix.so try_first_pass When I try use original pppd with PAP authentication it works fine. But when I use recompiled pppd (using -DUSE_PAM in Makefile), pppd returns "Authentication failure": pppd[1692]: rcvd [PAP AuthReq id=0x1 user="?????" password="********"] pppd[1692]: PAP login failure for ????? pppd[1692]: sent [PAP AuthNak id=0x1 "Authentication failure"] pppd[1692]: sent [LCP TermReq id=0x2 "Authentication failed"] pppd[1692]: rcvd [LCP TermAck id=0x2] pppd[1692]: Connection terminated, connected for 1 minutes I'm using getty with ":de#3:pp=/usr/local/etc/pwin:" and my pwin script is: /usr/sbin/pppd debug idle 1200 -detach modem crtscts netmask 255.255.255.128 auth login +pap dns1 200.249.195.3 dns2 200.249.195.5 domain nlink.com.br. I've tried radius athentication with login (pam_radius.so in pam.conf) and it works fine. But with my pppd radius and unix authentication don't work. Are there any bugs with PAM in pppd? Am I doing anything wrong? Why pppd works fine without -DUSE_PAM and when I use same pppd source compiled with -DUSE_PAM it doesn't work (without chaging the conf files)? Can anyone help me to configure (re-compile) pppd work with PAM? Thanks, Paulo Fragoso. ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! 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 Jun 10 11:52:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 993E814ED0 for ; Thu, 10 Jun 1999 11:52:30 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id OAA25864 for ; Thu, 10 Jun 1999 14:41:01 -0400 Date: Thu, 10 Jun 1999 14:41:00 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@FreeBSD.ORG Subject: Re: What is FTW? 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, 9 Jun 1999, Zhihui Zhang wrote: > > In the FAQ of FreeBSD 2.X, 13.12. Alternative layout policies for > directories, there is the following sentence: > > Most filesystems are created from archives that were created by a depth > first search (aka ftw). > > What does ftw stand for (My guess is File Tree Walk)? Can anyone give me > examples of programs that create archives from a file tree in a depth > first way? Do these programs rebuild the file tree from archive exactly as > they were created? > I have just found that ftw does stand for File Tree Walk and there is a C library routine named ftw() (XPG4 standard) in AIX and HP-UX. However, I can not find the same routine in FreeBSD manual pages. Maybe it is not supported by FreeBSD. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 12:25:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pinochet.cityline.ru (pinochet.cityline.ru [195.46.160.34]) by hub.freebsd.org (Postfix) with ESMTP id 5889514CE1 for ; Thu, 10 Jun 1999 12:25:07 -0700 (PDT) (envelope-from alfapri@cityline.ru) Received: from cityline.ru (ppp02-1-106.cityline.ru [195.46.161.106]) by pinochet.cityline.ru (8.9.2/t/08-Oct-1998) with ESMTP id XAA17865 for ; Thu, 10 Jun 1999 23:24:39 +0400 (MSD) Message-ID: <376011AA.606CEA2D@cityline.ru> Date: Thu, 10 Jun 1999 23:27:39 +0400 From: Alexey Ryndin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.org Subject: restrict connection Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need Your advice. It is necessary to restrict network access to some box. All IP addresses of hosts from which it is allowed to connect to the box are known. From some of them it is allowed to use ftp, from some - telnet and so on. What is the best way to solve this problem? It is necessary to filter access as close to the network device as possible. If it is necessary to write some daemon, please tell me which sources & mans I must look throw and all book references will be appreciated. Thanks in advance Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 13:21:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 80B0E14D96 for ; Thu, 10 Jun 1999 13:21:23 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA33396; Thu, 10 Jun 1999 14:21:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA45046; Thu, 10 Jun 1999 14:20:12 -0600 (MDT) Message-Id: <199906102020.OAA45046@harmony.village.org> To: Bill Huey Subject: Re: linux and freebsd kernels conceptually different? Cc: des@flood.ping.uio.no (Dag-Erling Smorgrav), freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Jun 1999 03:17:58 PDT." <199906101017.DAA27419@mag.ucsd.edu> References: <199906101017.DAA27419@mag.ucsd.edu> Date: Thu, 10 Jun 1999 14:20:12 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906101017.DAA27419@mag.ucsd.edu> Bill Huey writes: : It's a good thing because assumptions about memory useage within the kernel, : portability abstractions, internal buffer queue overhead, etc..., need : to reexamined to see if they are still relevant. While it is true that one needs to occasionally reexamine the assumptions that one has built one's system upon in the light of new information, the mere fact that one does so doesn't mean that how things have been done in the past is automatically wrong. Also, there have been years of research in these areas so you'll know what to expect as the CPU speed gets faster, memory gets cheaper, etc. It isn't like the people that have done the years of OS reasearch are stupid and short-sighted. Yet, this is what the message that I've gotten from the Linux folks in the area of kernel development. Maybe it isn't intended, but it sure is offensive. : This is always good, assuming that this is done properly with peer review : and that folks listen to it. Linux isn't peer reviewed in the traditional sense of this meaning, so your whole argument fails because of that. I'd agree if it was entensively peer reviewed, it might be a good thing. It isn't. Linux gets to where it is going by doing things many times quickly, but not necessarily correctly. While there is some value in this approach, it can be quite wasteful. I gave up maintaining my port of Linux to my rPC44 because the internal internal interfaces kept changing at a rate that makes the recent -current newbus integration look and feel stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 13:43:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 5524E156CF for ; Thu, 10 Jun 1999 13:42:49 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id PAA49454; Thu, 10 Jun 1999 15:42:47 -0500 (CDT) (envelope-from dan) Date: Thu, 10 Jun 1999 15:42:47 -0500 From: Dan Nelson To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What is FTW? Message-ID: <19990610154246.A49356@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from "Zhihui Zhang" on Thu Jun 10 14:41:00 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 10), Zhihui Zhang said: > On Wed, 9 Jun 1999, Zhihui Zhang wrote: > > Most filesystems are created from archives that were created by a > > depth first search (aka ftw). > > > > What does ftw stand for (My guess is File Tree Walk)? Can anyone > > give me examples of programs that create archives from a file tree > > in a depth first way? Do these programs rebuild the file tree from > > archive exactly as they were created? > > I have just found that ftw does stand for File Tree Walk and there is a C > library routine named ftw() (XPG4 standard) in AIX and HP-UX. However, I > can not find the same routine in FreeBSD manual pages. Maybe it is not > supported by FreeBSD. There is a set of fts* funtcions in FreeBSD (man fts); it looks like the options are very similar. -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 Thu Jun 10 13:45:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6EAB414D84 for ; Thu, 10 Jun 1999 13:44:58 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA24282 for FreeBSD-hackers@freebsd.org; Thu, 10 Jun 1999 22:02:32 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA86860 for FreeBSD-hackers@freebsd.org; Thu, 10 Jun 1999 21:50:20 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906101950.VAA86860@yedi.iaf.nl> Subject: making release To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Thu, 10 Jun 1999 21:50:20 +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+ PL43 (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 I still don't seem to have the right combination of things to make a release: -------------------------------------------------------------- >>> elf make world completed on Thu Jun 10 08:41:26 GMT 1999 -------------------------------------------------------------- + touch /tmp/.world_done + cd /usr/src/release/sysinstall + make obj /local/ReleaseObj/usr/src/release/sysinstall created for /usr/src/release/sysinstall + cd /usr/src/release + make obj + make doRELEASE mkdir /R chflags -R noschg /R/. cd /usr/src/release/../etc && make distrib-dirs DESTDIR=/R/stage/trees/bin rm -rf /R/* mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /R/stage/trees/bin/ mkdir /R/stage mkdir /R/stage/floppies mkdir /R/stage/trees mkdir /R/stage/dists mkdir /R/stage/kernels for i in bin manpages catpages games proflibs dict info doc compat1x compat20 compat21 compat22 krb des ; do mkdir /R/stage/trees/$i && mkdir /R/stage/dists/$i && mtree -deU -f /usr/src/release/../etc/mtree/BSD.root.dist -p /R/stage/trees/$i > /dev/null && mtree -deU -f /usr/src/release/../etc/mtree/BSD.usr.dist -p /R/stage/trees/$i/usr > /dev/null && mtree -deU -f /usr/src/release/../etc/mtree/BSD.include.dist -p /R/stage/trees/$i/usr/include > /dev/null && mtree -deU -f /usr/src/release/../etc/mtree/BSD.var.dist -p /R/stage/trees/$i/var > /dev/null ; done mtree: /R/stage/trees/bin/: No such file or directory *** Error code 1 1 error *** Error code 2 touch release.1 1 error *** Error code 2 1 error real 134m8.165s user 67m22.453s sys 21m52.421s This was using: time make -j2 release CHROOTDIR=/local/GenRelease/ BUILDNAME=3.2.0.-rel-wkb RELEASETAG=RELENG_3_2_0_RELEASE NODOC=YES NOPORTS=YES NOKERBEROS=YES 2>&1 I hope some seasoned 'releaser' can help me out, maybe offline from this list. Thanks, -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 13:52:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8521814C8E for ; Thu, 10 Jun 1999 13:52:38 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA58410; Thu, 10 Jun 1999 16:52:24 -0400 (EDT) Message-Id: <199906102052.QAA58410@cs.rpi.edu> To: Alexey Ryndin Cc: hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: restrict connection In-Reply-To: Message from Alexey Ryndin of "Thu, 10 Jun 1999 23:27:39 +0400." <376011AA.606CEA2D@cityline.ru> Date: Thu, 10 Jun 1999 16:52:24 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have similiar restraints for a certain number of our machines, we have solved this problem by using FreeBSD's built in firewall (just add 'options IPFIREWALL' to your kernel config script). Here is a *very* simple firewall config to do some such restrictions): You may note that there are mutliple accept lines for this, this is done to allow good security and logging for each connection; without these mutliple steps an attacker could determine what services you are running by forging TCP packets to make it look like connections are already there... add 100 allow all from any to any via lo0 #standard rule for lo0 #log and allow standard telnet from IP1 *only*, and only from IF1 interface add 200 allow log tcp from IP1 to HOSTIP 23 setup in recv IF1 add 200 allow tcp from IP1 to HOSTIP 23 in recv IF1 add 200 allow tcp from HOSTIP 23 to IP1 out xmit IF1 add 200 deny log tcp from any to HOSTIP 23 #Allow ssh connects from a secured subnet add 300 allow log tcp from NET1/NET1MASK to HOSTIP 22 setup in recv IF1 add 300 allow tcp from NET1/NET1MASK to HOSTIP 22 in recv IF1 add 300 allow tcp from HOSTIP 22 to NET1/NET1MASK out xmit IF1 add 300 deny log tcp from any to HOSTIP 23 Wash, rinse, and repeat for your other services. FTP will be a bit tricky since it is a 2-way communication, but I have done it, you just open up a set of ports in the 4000-5000 range, and make sure nothing ever runs on them, and they are outbound connections only, accept only "established" packets in on them. The OS will bind to the first port that it can, and for me so far that has taken into account firewall rules. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 14:31: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id 08CF014DE4 for ; Thu, 10 Jun 1999 14:31:04 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id OAA28416; Thu, 10 Jun 1999 14:25:49 -0700 (PDT) From: Bill Huey Message-Id: <199906102125.OAA28416@mag.ucsd.edu> Subject: Re: linux and freebsd kernels conceptually different? To: imp@harmony.village.org (Warner Losh) Date: Thu, 10 Jun 1999 14:25:49 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199906102020.OAA45046@harmony.village.org> from "Warner Losh" at Jun 10, 99 02:20:12 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 always good, assuming that this is done properly with peer review > : and that folks listen to it. > > Linux isn't peer reviewed in the traditional sense of this meaning, so > your whole argument fails because of that. I'd agree if it was > entensively peer reviewed, it might be a good thing. It isn't. Well, first of all it wasn't a "constructed arguement" so it can't fail in the traditional sense of arguements failing. And I do qualify having open discussions with various folks "peer review" even if Linus himself has sole primary control over the source tree. This is something that I've seen done pretty cooperatively on linux-kernel. There definite technical problems with Linux, but it doesn't seem to measure up to the level of criticism that I've seen directed at it because the source tree is a consistently moving target. > Linux gets to where it is going by doing things many times quickly, > but not necessarily correctly. While there is some value in this > approach, it can be quite wasteful. I gave up maintaining my port of > Linux to my rPC44 because the internal internal interfaces kept > changing at a rate that makes the recent -current newbus integration > look and feel stable. Yeah, that's problematic and short sighted on their part. It's certainly not a question of expertise from what I've seen since there are very competent technical folks with strong acedemic CS backgrounds hanging out on the list. It seems like more of an implementation issues than and acedemic knowledge issue. I don't know what to think about this at this time, since I'm just now getting into understand the Linux source tree. > Warner bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 14:36:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1F01614DE4 for ; Thu, 10 Jun 1999 14:36:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA33520; Thu, 10 Jun 1999 15:36:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA45292; Thu, 10 Jun 1999 15:35:43 -0600 (MDT) Message-Id: <199906102135.PAA45292@harmony.village.org> To: Bill Huey Subject: Re: linux and freebsd kernels conceptually different? Cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 10 Jun 1999 14:25:49 PDT." <199906102125.OAA28416@mag.ucsd.edu> References: <199906102125.OAA28416@mag.ucsd.edu> Date: Thu, 10 Jun 1999 15:35:43 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906102125.OAA28416@mag.ucsd.edu> Bill Huey writes: : Yeah, that's problematic and short sighted on their part. It's certainly : not a question of expertise from what I've seen since there are very : competent technical folks with strong acedemic CS backgrounds hanging : out on the list. It seems like more of an implementation issues than : and acedemic knowledge issue. : : I don't know what to think about this at this time, since I'm just : now getting into understand the Linux source tree. One reason that I stopped was that I couldn't keep up with understanding the changes. This means that all my time for learning linux has been wasted because almost all of it is now obsolete, and has been obsolete for a couple of years now. Most of the time that I've spent learning the BSD internals has paid off as it is still current. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 14:38: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 4B4AA14F49 for ; Thu, 10 Jun 1999 14:37:57 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA098415385; Thu, 10 Jun 1999 13:23:05 -0400 Date: Thu, 10 Jun 1999 13:23:05 -0400 (EDT) From: Bill Fumerola To: Bill Huey Cc: Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: linux and freebsd kernels conceptually different? In-Reply-To: <199906102125.OAA28416@mag.ucsd.edu> 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, 10 Jun 1999, Bill Huey wrote: > There definite technical problems with Linux, but it doesn't seem > to measure up to the level of criticism that I've seen directed > at it because the source tree is a consistently moving target. s#moving#wreckless# - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 14:54:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 7813E1506D for ; Thu, 10 Jun 1999 14:54:14 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.244]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA7112; Thu, 10 Jun 1999 23:54:11 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id XAA07779; Thu, 10 Jun 1999 23:54:51 +0200 (CEST) (envelope-from asmodai) Date: Thu, 10 Jun 1999 23:54:51 +0200 From: Jeroen Ruigrok van der Werven To: Dennis Cc: dyson@iquest.net, Dag-Erling Smorgrav , Arun Sharma , Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: linux and freebsd kernels conceptually different? Message-ID: <19990610235451.A7680@ninth-circle.org> References: <199906101443.JAA00652@dyson.iquest.net.> <199906101716.NAA00235@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199906101716.NAA00235@etinc.com>; from Dennis on Thu, Jun 10, 1999 at 12:11:46PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dennis (dennis@etinc.com) [990610 19:58]: > At 09:43 AM 6/10/99 -0500, John S. Dyson wrote: > >Dag-Erling Smorgrav said: > >> Arun Sharma writes: > >> > I'd say most of the differences are in implementation and development > >> > methodology. Linux camp seems to be proud of breaking traditions and > >> > concepts invented after lengthy research. I haven't seen that many > >> > iconoclasts in my short encounter with FreeBSD. > >> > >> You say that as if it's a good thing... I'd amend it to "The Linux > >> camp seems to think it's a good idea to ignore countless man-years of > >> research and development in the field of OS design, and make the same > >> mistakes other people have made, corrected and documented years before > >> them. I haven't seen that many ignorants in my short encounter with > >> FreeBSD." > > They finally caved in on spl type mechanisms, though the mechanisms > provided in v2.2 are very crude. Worst of all, most of the OS is > undocumented and if you dont ask Alan Cox (or he doesnt feel like giving > you an answer) then you are pretty much in the dark. Seems like a common problem with Linux overall. GTk+ tends to introduce bugs fixed in earlier versions, it's stabilizing somewhat with 1.2.x. Gnome is even worse, it creates bugs from bugfixes or so it seems. Insidious idea that featurebloat is preferred over code stability and maturity... Add to that the general chaotic way of Linuxcoding and not documenting and we have one development OS that sucks for developers. And yet so many of them flock to it *sigh* Hope I can change *BSD for the better in that aspect with the PDP. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The *BSD Programmer's Documentation Project Network/Security Specialist *BSD & (g)VIM : Accept no limitations... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 15:20:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 140AB14C8D for ; Thu, 10 Jun 1999 15:20:34 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id SAA01467 for ; Thu, 10 Jun 1999 18:21:48 -0400 (EDT) Message-Id: <199906102221.SAA01467@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 10 Jun 1999 17:17:13 -0400 To: hackers@freebsd.org From: Dennis Subject: P5 vs Celeron vs PII Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a nutshell, does anyone have a handle on the relative preformance of these are? 233Mhz P5 vs 233Mhz Celeron 333Mhz Celeron vs 333 Mhz PII Thanks Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 15:29:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id 807C014BE5 for ; Thu, 10 Jun 1999 15:29:45 -0700 (PDT) (envelope-from yume@club-internet.fr) Received: from club-internet.fr (St-Lo-1-70.club-internet.fr [194.158.122.70]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id AAA28448 for ; Fri, 11 Jun 1999 00:29:43 +0200 (MET DST) Message-ID: <37603C16.1D82C006@club-internet.fr> Date: Fri, 11 Jun 1999 00:28:38 +0200 From: Frederic Reply-To: yume@club-internet.fr X-Mailer: Mozilla 4.03 [fr] (Win95; I) MIME-Version: 1.0 To: FreeBSD Subject: Subcribe ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I want to subscribe to the list. A+ Frederic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 15:32:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52]) by hub.freebsd.org (Postfix) with ESMTP id 756E514BE5 for ; Thu, 10 Jun 1999 15:32:33 -0700 (PDT) (envelope-from yume@club-internet.fr) Received: from club-internet.fr (St-Lo-1-70.club-internet.fr [194.158.122.70]) by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id AAA28412 for ; Fri, 11 Jun 1999 00:32:28 +0200 (MET DST) Message-ID: <37603CBB.7589A276@club-internet.fr> Date: Fri, 11 Jun 1999 00:31:23 +0200 From: Frederic Reply-To: yume@club-internet.fr X-Mailer: Mozilla 4.03 [fr] (Win95; I) MIME-Version: 1.0 To: FreeBSD Subject: New hacker Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am student in softaware developement I live in France I would like to listen and to participate to your list Take care Frederic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 15:34:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3E37914BE5 for ; Thu, 10 Jun 1999 15:34:36 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id SAA01523 for ; Thu, 10 Jun 1999 18:35:51 -0400 (EDT) Message-Id: <199906102235.SAA01523@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 10 Jun 1999 17:31:15 -0400 To: hackers@freebsd.org From: Dennis Subject: DOC Flash Support 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 support for DiskOnChip Flash Disks? Anyone have any experience? Thanks, Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 15:40:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id A60B61501A for ; Thu, 10 Jun 1999 15:40:55 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id SAA09508; Thu, 10 Jun 1999 18:47:20 -0400 (EDT) Date: Thu, 10 Jun 1999 18:47:19 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: DOC Flash Support In-Reply-To: <199906102235.SAA01523@etinc.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 Yes...there is support in 3.1/3.2/4.0...I believe the driver is included as part of 4.0-CURRENT. PHK wrote the driver under contract with M-Systems, so the driver itself is object code rather than source. I'm currently having very bad experience with a DOC 2K and 3.2-RELEASE and the 3.2 driver...get a nasty atpanic on booting the kernel. Email to the mailing list PHK mentions hasn't yielded a response. Email me privately if you wish to discuss. -marc P.S: Didn't have these probs with Linux! ;-) ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Thu, 10 Jun 1999, Dennis wrote: > > Is there support for DiskOnChip Flash Disks? > > Anyone have any experience? > > Thanks, > > Dennis > > > 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 Jun 10 15:59: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id CA6AC1544E for ; Thu, 10 Jun 1999 15:59:02 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 71511 invoked from network); 10 Jun 1999 22:59:01 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 10 Jun 1999 22:59:01 -0000 Received: from localhost (dscheidt@localhost) by shell-3.enteract.com (8.9.3/8.9.2) with SMTP id RAA24145; Thu, 10 Jun 1999 17:59:01 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-3.enteract.com: dscheidt owned process doing -bs Date: Thu, 10 Jun 1999 17:59:01 -0500 (CDT) From: David Scheidt To: Dennis Cc: hackers@freebsd.org Subject: Re: P5 vs Celeron vs PII In-Reply-To: <199906102221.SAA01467@etinc.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, 10 Jun 1999, Dennis wrote: > In a nutshell, does anyone have a handle on the relative preformance of > these are? > 333Mhz Celeron vs 333 Mhz PII For a typical job mix, it is pretty close to a wash. The PII seems to have a slight advantage, on the order of 5%. If you are compute bound, and the task fits in cache, the Celery has an advantage, since there is no wait state on cache hits. The PII has a much bigger cache, so even though cache hits are more expensive, they are more likely. I am pretty much unable to tell the difference between a Celeron and a PII at the same clock. The vast majority of my desktop computing isn't compute bound, though. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 16:17:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B58714F28 for ; Thu, 10 Jun 1999 16:17:09 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id SAA91343; Thu, 10 Jun 1999 18:17:33 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 10 Jun 1999 18:17:32 -0500 (CDT) From: Chris Dillon To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: P5 vs Celeron vs PII In-Reply-To: <199906102221.SAA01467@etinc.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, 10 Jun 1999, Dennis wrote: > > In a nutshell, does anyone have a handle on the relative preformance of > these are? > > 233Mhz P5 vs 233Mhz Celeron 233MHz P5 (w/L2 cache on motherboard) > 233MHz Celeron (no L2 cache) > 333Mhz Celeron vs 333 Mhz PII In my experience, the Celeron CPUs which have the 128KB full-speed cache are pretty much on-par (though not always) with the PII CPUs with 512KB half-speed cache. I have noticed that in certain computationally-heavy situations that the smaller Celeron cache hurts (cracking a password with John The Ripper, for instance), even though it runs at a higher clock rate. Last time I looked, the price difference was enough that the Celeron gives you more bang for the buck. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 16:30: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from geocities.com (mail10.geocities.com [209.1.224.138]) by hub.freebsd.org (Postfix) with ESMTP id 14BE214DFF for ; Thu, 10 Jun 1999 16:29:24 -0700 (PDT) (envelope-from sylvarnes@geocities.com) Received: from hsf2510 ([158.37.10.111]) by geocities.com (8.9.3/8.9.3) with SMTP id QAA17238; Thu, 10 Jun 1999 16:28:49 -0700 (PDT) Message-Id: <3.0.6.32.19990611012822.0079d930@mail.geocities.com> X-Sender: sylvarnes@mail.geocities.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 11 Jun 1999 01:28:22 +0200 To: Chris Dillon From: "Stein B. Sylvarnes" Subject: Re: P5 vs Celeron vs PII Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199906102221.SAA01467@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 18:17 10.06.99 -0500, Chris Dillon wrote: >On Thu, 10 Jun 1999, Dennis wrote: > >> >> In a nutshell, does anyone have a handle on the relative preformance of >> these are? >> >> 233Mhz P5 vs 233Mhz Celeron >Last time I looked, the price difference was enough that the Celeron >gives you more bang for the buck. > The AMD K6-3 has given best preformance/price, at least here in Norway. The lead has been signifficant, but most vendors have built their PCs with (W)Intel CPUs. For the home-builder/upgrader, the choice has been simple, though. But lately Intel has dropped their prices, and if I was to buy a new CPU now, I would have to choose between PIII and K6-3 (They're pretty much equally fast, AMD a bit faster in Q2 in windoze) anyways Stein B. Sylvarnes {Open, Net, Free}BSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 16:35:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by hub.freebsd.org (Postfix) with ESMTP id 75C5014DFF for ; Thu, 10 Jun 1999 16:35:46 -0700 (PDT) (envelope-from yume@club-internet.fr) Received: from club-internet.fr (Rouen-2-133.club-internet.fr [195.36.136.133]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id BAA09295 for ; Fri, 11 Jun 1999 01:35:44 +0200 (MET DST) Message-ID: <37604B8F.8305001@club-internet.fr> Date: Fri, 11 Jun 1999 01:34:39 +0200 From: Frederic Reply-To: yume@club-internet.fr X-Mailer: Mozilla 4.03 [fr] (Win95; I) MIME-Version: 1.0 To: FreeBSD Subject: Thanks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all for so quick answer and advices. I made all standard procedure to subscribe. I am a student in software development and electronic (70 % of soft) I am know installing and "giving foods" to a web server powered by FreeBSD and Apache That is why I am interesting by the list. I was interesting before because I also use versions of Linux. But but FreeBSD is not a version of Linux ! Right ? Thanks to all. Frederic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 16:59: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E837515311 for ; Thu, 10 Jun 1999 16:58:50 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10sEif-000Mft-00 for freebsd-hackers@FreeBSD.org; Fri, 11 Jun 1999 01:58:49 +0200 From: Sheldon Hearn To: freebsd-hackers@FreeBSD.org Subject: Re: Thanks In-reply-to: Your message of "Fri, 11 Jun 1999 01:34:39 +0200." <37604B8F.8305001@club-internet.fr> Date: Fri, 11 Jun 1999 01:58:49 +0200 Message-ID: <87164.929059129@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Jun 1999 01:34:39 +0200, Frederic wrote: > I am know installing and "giving foods" to a web server > powered by FreeBSD and Apache [...] > But but FreeBSD is not a version of Linux ! Right ? The headers of the mail don't leave me convinced. I still believe the guys at USENIX are getting a little too merry and playing silly buggers on the rest of us. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 17:23:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 0EF1A154AA; Thu, 10 Jun 1999 17:23:51 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA12898; Thu, 10 Jun 1999 17:23:49 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd012866; Thu Jun 10 17:23:46 1999 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA20724; Thu, 10 Jun 1999 17:23:39 -0700 (MST) From: Terry Lambert Message-Id: <199906110023.RAA20724@usr05.primenet.com> Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) To: jb@cimlogic.com.au (John Birrell) Date: Fri, 11 Jun 1999 00:23:39 +0000 (GMT) Cc: thorpej@nas.nasa.gov, dyson@iquest.net, dillon@apollo.backplane.com, Thu@apollo.backplane.com, 3@FreeBSD.ORG, Jun@FreeBSD.ORG, 1999@FreeBSD.ORG, 23.-0500@apollo.backplane.com, nate@mt.sri.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199906050948.TAA17548@cimlogic.com.au> from "John Birrell" at Jun 5, 99 07:48: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 For what it's worth, and to throw another hat into the fray, it seems to me that two things are driving the tension here: 1) Matt is effectively in a position where he no longer has to work, and can now dedicate a significant amount of focussed effort over long intervals at FreeBSD code. 2) The review process currently in force requires review by people who do not have such a luxury of time in which to review the code Matt produces; stated simply: they can't keep up. Having been in a similar position, where an employer was having me spend 8 hours a day working on filesystem code, the changes to which were 85%-90% applicable to FreeBSD, I can sympathize with Matts position. As FreeBSD becomes more and more mainstream (some of you may have heard about IBM's recent acquisition of Whistle, or their bid for FreeBSD based machines to school districts in Hong Kong: that's about as mainstream as FreeBSD can get), the number of people with an equivalent of Matts available time and energy to focus on FreeBSD coding can only increase. I don't know "the simple answer" to the dilemma posed by FreeBSD's increasing success; however, it is clear to me that there is a need to look for such an answer, and to find one -- the sooner the better. Perhaps all of you can discuss this issue at the FreeBSD BOF at Usenix. 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 Jun 10 17:34:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 1F324153C8 for ; Thu, 10 Jun 1999 17:34:06 -0700 (PDT) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id EAA13013; Fri, 11 Jun 1999 04:36:18 +0400 (MSD) Message-Id: <199906110036.EAA13013@aaz.links.ru> Subject: Re: restrict connection In-Reply-To: <376011AA.606CEA2D@cityline.ru> from "Alexey Ryndin" at "Jun 10, 99 11:27:39 pm" To: alfapri@cityline.ru (Alexey Ryndin) Date: Fri, 11 Jun 1999 04:36:18 +0400 (MSD) Cc: hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Alexey Ryndin writes: > I need Your advice. It is necessary to restrict network access to some > box. All IP addresses of hosts from which it is allowed to connect to > the box are known. From some of them it is allowed to use ftp, from some > - telnet and so on. What is the best way to solve this problem? It is > necessary to filter access as close to the network device as possible. > If it is necessary to write some daemon, please tell me which sources & > mans I must look throw and all book references will be appreciated. /usr/ports/security/xinetd -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 10 17:37:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id E60F51523B for ; Thu, 10 Jun 1999 17:37:24 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 16588 invoked from network); 11 Jun 1999 00:37:22 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 11 Jun 1999 00:37:22 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id TAA02293; Thu, 10 Jun 1999 19:37:20 -0500 (EST) From: "John S. Dyson" Message-Id: <199906110037.TAA02293@dyson.iquest.net> Subject: Re: Matt's Commit status (was Re: 3.2-stable, panic #12) In-Reply-To: <199906110023.RAA20724@usr05.primenet.com> from Terry Lambert at "Jun 11, 99 00:23:39 am" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 10 Jun 1999 19:37:20 -0500 (EST) Cc: jb@cimlogic.com.au, thorpej@nas.nasa.gov, dyson@iquest.net, dillon@apollo.backplane.com, Thu@apollo.backplane.com, 3@FreeBSD.ORG, Jun@FreeBSD.ORG, 1999@FreeBSD.ORG, 23.-0500@apollo.backplane.com, nate@mt.sri.com, 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 > > For what it's worth, and to throw another hat into the fray, it > seems to me that two things are driving the tension here: > > 1) Matt is effectively in a position where he no longer has > to work, and can now dedicate a significant amount of > focussed effort over long intervals at FreeBSD code. > > 2) The review process currently in force requires review by > people who do not have such a luxury of time in which to > review the code Matt produces; stated simply: they can't > keep up. > > Having been in a similar position, where an employer was having > me spend 8 hours a day working on filesystem code, the changes > to which were 85%-90% applicable to FreeBSD, I can sympathize > with Matts position. > I can also. Software developers and engineers are NOT interchangeable though. Therefore, the various skills and abilities don't always match the needs... IMO, the best thing that can effectively be done is to continue the way things are going, until appropriate people can be available to keep the pipeline full. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 0:17:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 7E6E514D94 for ; Fri, 11 Jun 1999 00:17:35 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Fri, 11 Jun 1999 09:20:25 +0200 Message-ID: <55586E7391ACD211B9730000C110027617965A@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'yume@club-internet.fr'" , FreeBSD Subject: RE: Thanks Date: Fri, 11 Jun 1999 09:14:59 +0200 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 > -----Original Message----- > From: Frederic [SMTP:yume@club-internet.fr] > Sent: Friday, June 11, 1999 1:35 AM > To: FreeBSD > Subject: Thanks > But but FreeBSD is not a version of Linux ! Right ? > [ML] FreeBSD can behave (almost) as Linux as far as Linux binaries are concerned, but is in fact entirely different internally. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 0:41:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from login-2.eunet.no (login-2.eunet.no [193.71.71.239]) by hub.freebsd.org (Postfix) with ESMTP id E876914CFC for ; Fri, 11 Jun 1999 00:41:27 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (mbendiks@login-1.eunet.no [193.71.71.238]) by login-2.eunet.no (8.9.3/8.9.3/GN) with ESMTP id JAA18950; Fri, 11 Jun 1999 09:41:24 +0200 (CEST) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.8.8/8.8.8) with ESMTP id JAA06088; Fri, 11 Jun 1999 09:41:24 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Fri, 11 Jun 1999 09:41:24 +0200 (CEST) From: Marius Bendiksen To: Bill Fumerola Cc: Bill Huey , Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: linux and freebsd kernels conceptually different? 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 > > at it because the source tree is a consistently moving target. > s#moving#wreckless# s/wreckless/reckless/. wreckless is most certainly not true ;) - marius - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 2: 8:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 34FAE15299; Fri, 11 Jun 1999 02:08:24 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id KAA28022 Fri, 11 Jun 1999 10:08:22 +0100 (BST) Message-ID: <3760D208.C7B2E27@cs.strath.ac.uk> Date: Fri, 11 Jun 1999 10:08:24 +0100 From: Roger Hardiman Organization: Strathclyde University X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: multimedia@freebsd.org, hackers@freebsd.org Subject: Announcing vbidecode, videotext and Teletext Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Recently I added VBI capture support to the Brooktree 848/878 driver (/dev/vbi0) This allows Teletext/Videotext capture and viewing. To complement this I have now added 'vbidecode' and 'videotext' to the ports collection /usr/ports/misc 'vbidecode' lets to decode teletext pages and save them to disk as .vtx files. There is one file for each page / sub-page 'videotext' lets to view/print/save to GIF and PNG the saved .vtx files. It also allows background searching of all teletext pages on disk. Instructions are a bit complicated at this time, but I suggest you read the Teletext instructions at http://telepresence.dmem.strath.ac.uk/bt848 In addition, there is Juha's ASCII .vtx file viewer at http://qn-lpr2-98.quicknet.inet.fi:22/stuff/vtxview.c Good luck Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 3:30:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id 0E12C14D16 for ; Fri, 11 Jun 1999 03:30:32 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id FAA01145; Fri, 11 Jun 1999 05:29:34 -0500 (EST) (envelope-from toor) Message-Id: <199906111029.FAA01145@dyson.iquest.net.> Subject: Re: linux and freebsd kernels conceptually different? In-Reply-To: <199906102135.PAA45292@harmony.village.org> from Warner Losh at "Jun 10, 1999 03:35:43 pm" To: imp@harmony.village.org (Warner Losh) Date: Fri, 11 Jun 1999 05:29:34 -0500 (EST) Cc: billh@mag.ucsd.edu (Bill Huey), freebsd-hackers@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Warner Losh said: > In message <199906102125.OAA28416@mag.ucsd.edu> Bill Huey writes: > : Yeah, that's problematic and short sighted on their part. It's certainly > : not a question of expertise from what I've seen since there are very > : competent technical folks with strong acedemic CS backgrounds hanging > : out on the list. It seems like more of an implementation issues than > : and acedemic knowledge issue. > : > : I don't know what to think about this at this time, since I'm just > : now getting into understand the Linux source tree. > > One reason that I stopped was that I couldn't keep up with > understanding the changes. This means that all my time for learning > linux has been wasted because almost all of it is now obsolete, and > has been obsolete for a couple of years now. Most of the time that > I've spent learning the BSD internals has paid off as it is still > current. > Another thing: Even if one depends on the docs for the VM in the new (Red) Daemon Book, that person isn't too far away from the CURRENT FreeBSD VM code. FreeBSD is likely closer to Lite/2 (even with the VM changes) than almost anyone else, while keeping up technologically. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 3:46: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by hub.freebsd.org (Postfix) with ESMTP id 72FC214C83 for ; Fri, 11 Jun 1999 03:46:02 -0700 (PDT) (envelope-from yume@club-internet.fr) Received: from club-internet.fr (Rouen-1-109.club-internet.fr [195.36.136.109]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id MAA29196; Fri, 11 Jun 1999 12:45:59 +0200 (MET DST) Message-ID: <3760E8A5.4C4C62D7@club-internet.fr> Date: Fri, 11 Jun 1999 12:44:53 +0200 From: Frederic Reply-To: yume@club-internet.fr X-Mailer: Mozilla 4.03 [fr] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Cc: Sheldon Hearn Subject: Re: Thanks References: <87164.929059129@axl.noc.iafrica.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn a écrit: > On Fri, 11 Jun 1999 01:34:39 +0200, Frederic wrote: > > > I am know installing and "giving foods" to a web server > > powered by FreeBSD and Apache > [...] > > But but FreeBSD is not a version of Linux ! Right ? > > The headers of the mail don't leave me convinced. I still believe the > guys at USENIX are getting a little too merry and playing silly buggers > on the rest of us. > > :-) > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Hi, My English is not at the top but in the above of the middle... I do not entirely understand your "intellectual" and subtil answer, I was just trying to place me in the FreeBSD world, like a common introduction as "Where do you come from ?" "I came from..." I just "really" start working on FreeBSD know. It started because I was searching for a Linux version to run the Internet Server and I finally discover FreeBSD which is not a type of Linux (but in the same philosophy, if I can say). So are enough kind to explain to me your mail ? That you sent to everybody in the list. merry = happy, you mean happy like a young dog to be on an operating system list ? You mean they beleive to belong to a professionnal world as if they had an open door to Netscape or MicroSoft ? sorry for the example) silly = stupid, you mean I play like a teenage trying to escape from bugs and thinking like a God of computer deciding without enough background to recompile the soul of the system (the core) ? You give impression to me to be a quick mind maker on people related to all past meetings you have done. Of course they are some people like you imagine me. But I am not a teenage in the bad sens and not in physical or mental age. Maybe my style reflects freshness that was translated into stupid merry emotion. You do not even know me but you make a judgment that classify me in the stupid users and merry noisy teens in the high tech team... What can I say ? In the computer world, discovering, testing developing NEW things is one of the principal mind shape. I think you are very very quick into using that shape. I wish you a merry un - buggy day Mister Hearn. A+ Frederic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 4: 6:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id CC0B21521A for ; Fri, 11 Jun 1999 04:06:33 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10sP8g-0003se-00; Fri, 11 Jun 1999 13:06:22 +0200 From: Sheldon Hearn To: yume@club-internet.fr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Thanks In-reply-to: Your message of "Fri, 11 Jun 1999 12:44:53 +0200." <3760E8A5.4C4C62D7@club-internet.fr> Date: Fri, 11 Jun 1999 13:06:22 +0200 Message-ID: <14919.929099182@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Jun 1999 12:44:53 +0200, Frederic wrote: > My English is not at the top but in the above of the middle... > I do not entirely understand your "intellectual" and subtil answer, Hi Frederic, I must admit, I didn't expect you to receive my message, since I sent it directly to the list. It was silly of me, since your mail did say that you'd just subscribed. > So are enough kind to explain to me your mail ? That you sent to everybody > in the list. Your message to the list was hard to take seriously, because I found it hard to believe that you could find out about the freebsd-hackers mailing list without finding out anything about FreeBSD. Perhaps that's just because I found out about it on the FreeBSD web page. Perhaps the list is advertised elsewhere. Regardless, it was a joke at your expense that has backfired quite poetically to embarrass me no end. Please accept my apologies. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 4:18:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 5C4C1153C1 for ; Fri, 11 Jun 1999 04:17:59 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Fri, 11 Jun 1999 13:16:32 +0200 Message-ID: <55586E7391ACD211B9730000C110027617965E@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'yume@club-internet.fr'" , freebsd-hackers@FreeBSD.ORG Cc: Sheldon Hearn Subject: RE: Thanks Date: Fri, 11 Jun 1999 13:11:04 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Frederic [SMTP:yume@club-internet.fr] > Sent: Friday, June 11, 1999 12:45 PM > To: freebsd-hackers@FreeBSD.ORG > Cc: Sheldon Hearn > Subject: Re: Thanks >=20 > Sheldon Hearn a =E9crit: >=20 > > On Fri, 11 Jun 1999 01:34:39 +0200, Frederic wrote: > > > > > I am know installing and "giving foods" to a web server > > > powered by FreeBSD and Apache > > [...] > > > But but FreeBSD is not a version of Linux ! Right ? > > > > The headers of the mail don't leave me convinced. I still believe > the > > guys at USENIX are getting a little too merry and playing silly > buggers > > on the rest of us. > > > > :-) > > > > Ciao, > > Sheldon. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message >=20 > So are enough kind to explain to me your mail ? That you sent to > everybody > in the list. >=20 [ML] He did not mean to insult you. I think he has a somewhat strange mail delivery path so that he thought you were not a real = person but a joke made by some FreeBSD developers who are currently attending = a UNIX conference. This is obviously not the case. Sorry it came out that way. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 4:47:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 684EB14C98 for ; Fri, 11 Jun 1999 04:47:26 -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 NAA14340; Fri, 11 Jun 1999 13:47:09 +0200 (MET DST) Date: Fri, 11 Jun 1999 13:47:07 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Sheldon Hearn Cc: yume@club-internet.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: Thanks In-Reply-To: <14919.929099182@axl.noc.iafrica.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 What he is also trying to say, without actually saying it, is that you might want to check the FreeBSD website for mailing lists that are more appropriate, with people that can help you in a better way. http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL freebsd-newbies freebsd-questions freebsd-current All available from the same mailing list server (send subscribe to majordomo@freebsd.org). FreeBSD-hackers discusses the internals of FreeBSD. Your English is fine, a lot better than French for most people, so don't worry about that. We are happy to be able to communicate. Have a nice day (it's raining in France I guess, it was in Switzerland yesterday), but have one anyway. Nick On Fri, 11 Jun 1999, Sheldon Hearn wrote: > > > On Fri, 11 Jun 1999 12:44:53 +0200, Frederic wrote: > > > My English is not at the top but in the above of the middle... > > I do not entirely understand your "intellectual" and subtil answer, > > Hi Frederic, > > I must admit, I didn't expect you to receive my message, since I sent it > directly to the list. It was silly of me, since your mail did say that > you'd just subscribed. > > > So are enough kind to explain to me your mail ? That you sent to everybody > > in the list. > > Your message to the list was hard to take seriously, because I found > it hard to believe that you could find out about the freebsd-hackers > mailing list without finding out anything about FreeBSD. > > Perhaps that's just because I found out about it on the FreeBSD web > page. Perhaps the list is advertised elsewhere. > > Regardless, it was a joke at your expense that has backfired quite > poetically to embarrass me no end. > > Please accept my apologies. > > Ciao, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 4:57:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E913D152CD for ; Fri, 11 Jun 1999 04:57:15 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10sPva-0004OD-00; Fri, 11 Jun 1999 13:56:54 +0200 From: Sheldon Hearn To: Nick Hibma Cc: yume@club-internet.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: Thanks In-reply-to: Your message of "Fri, 11 Jun 1999 13:47:07 +0200." Date: Fri, 11 Jun 1999 13:56:54 +0200 Message-ID: <16876.929102214@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Jun 1999 13:47:07 +0200, Nick Hibma wrote: > What he is also trying to say, without actually saying it, is that you > might want to check the FreeBSD website for mailing lists that are more > appropriate, with people that can help you in a better way. Eeek! Nick, that's not what I was trying to say. I was apologizing, and that's all. The freebsd-hackers mailing list is for people who are working on FreeBSD to discuss technical issues relating to FreeBSD development. That's what the charter says, anyway. Given Frederic's apparent intentions, it's the right list to be subscribing to if you read the charter. The fact that the charter doesn't mention that it's a good idea to have been using FreeBSD and tracking its development for a while before you start trying to contribute isn't his problem and I wasn't trying to make it his. The pointers you gave Frederic were appropriate, make no mistake. I just want to make sure that a genuine apology for what must have been quite an offensive message doesn't get watered down. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 5:55:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 2C0C814F0E for ; Fri, 11 Jun 1999 05:55:13 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id NAA01783 Fri, 11 Jun 1999 13:55:03 +0100 (BST) Message-ID: <37610728.7640C257@cs.strath.ac.uk> Date: Fri, 11 Jun 1999 13:55:04 +0100 From: Roger Hardiman Organization: Strathclyde University X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org, new-bus-arch@bostonradio.org Subject: KLD bt848 driver and vm_page_alloc_contig Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there a way to fix vm_page_alloc_contig() so it can allocate contiguous memory once userland has got up and running and memory has been fragmented/filled. I've finished porting the bt848 driver to the newbus framework. You can load/unload the driver with kldload and kldunload. Great for testing. Load test, unload, recompile, repeat... However, the driver needs about 2 meg of contiguous memory allocating. It must be contiguous as hardware writes directly into it. (same applies to the meteor driver and probably some of the sound card drivers) I can start X, and load the 'bktr' driver. But once I run a few apps, and memory fills up, I can no longer allocate the contiguous memory required. Clearly the kernel would need to swap out user process memory pages to make room for the contigous memory vm_page_alloc_contig() requires. Can this be done? Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 6:48:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id BC104154FD for ; Fri, 11 Jun 1999 06:48: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 PAA10444; Fri, 11 Jun 1999 15:48:03 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA26304; Fri, 11 Jun 1999 15:48:02 +0200 (MET DST) Date: Fri, 11 Jun 1999 15:48:01 +0200 From: Eivind Eklund To: Roger Hardiman Cc: hackers@FreeBSD.ORG, new-bus-arch@bostonradio.org Subject: Re: KLD bt848 driver and vm_page_alloc_contig Message-ID: <19990611154801.A26249@bitbox.follo.net> References: <37610728.7640C257@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <37610728.7640C257@cs.strath.ac.uk>; from Roger Hardiman on Fri, Jun 11, 1999 at 01:55:04PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 11, 1999 at 01:55:04PM +0100, Roger Hardiman wrote: > Hi, > > Is there a way to fix > vm_page_alloc_contig() > so it can allocate contiguous memory once userland has got up > and running and memory has been fragmented/filled. John Dyson answered this about 2 years ago with something like 'Yes, but it is a bit of work', and I think that is still true (I don't see any reason it shouldn't be possible, but I don't know the data structures involved well enough to know exactly how to do it. > Clearly the kernel would need to swap out user process memory pages > to make room for the contigous memory vm_page_alloc_contig() > requires. No, not really. The VM mapping internally is virtualized, so you can move pages around without swapping them out. You'd just have to find some place where you want to put the continuous block, and either move all pages in the block away from it, or drop them (if they're clean), in order to be able so you can return the block. It would destroy cache coherence, of course, but that isn't horribly expensive. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 6:58:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id E38EA1539A for ; Fri, 11 Jun 1999 06:58:04 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA129734183; Fri, 11 Jun 1999 05:43:04 -0400 Date: Fri, 11 Jun 1999 05:43:03 -0400 (EDT) From: Bill Fumerola To: Marius Bendiksen Cc: Bill Huey , Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: linux and freebsd kernels conceptually different? 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, 11 Jun 1999, Marius Bendiksen wrote: > > > at it because the source tree is a consistently moving target. > > s#moving#wreckless# > s/wreckless/reckless/. > > wreckless is most certainly not true ;) I hate when I make spelling errors that change the entire message. :< - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 7:10:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from campus.her.itesm.mx (campus.her.itesm.mx [200.36.229.85]) by hub.freebsd.org (Postfix) with ESMTP id 4B0A515409 for ; Fri, 11 Jun 1999 07:10:19 -0700 (PDT) (envelope-from jherrera@campus.her.itesm.mx) Received: from VENTANA ([200.36.231.5]) by campus.her.itesm.mx with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id M39D8J25; Fri, 11 Jun 1999 07:08:14 -0600 Message-ID: <001d01beb414$2a997c00$05e724c8@her.itesm.mx> From: "Lic Jose M. Herrera" To: "Sheldon Hearn" Cc: References: <87164.929059129@axl.noc.iafrica.com> Subject: Re: Thanks Date: Fri, 11 Jun 1999 07:10:31 -0700 Organization: ITESM Campus Sonora Norte MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are right, Sheldon... X-Mailer: Mozilla 4.03 [fr] (Win95; I) And also we have too much work to answer: But but FreeBSD is not a version of Linux ! Right ? Sorry Frederic... :P ----- Original Message ----- From: Sheldon Hearn To: Sent: Thursday, June 10, 1999 4:58 PM Subject: Re: Thanks > > > On Fri, 11 Jun 1999 01:34:39 +0200, Frederic wrote: > > > I am know installing and "giving foods" to a web server > > powered by FreeBSD and Apache > [...] > > But but FreeBSD is not a version of Linux ! Right ? > > The headers of the mail don't leave me convinced. I still believe the > guys at USENIX are getting a little too merry and playing silly buggers > on the rest of us. > > :-) > > Ciao, > Sheldon. > > > 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 Jun 11 7:40:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 45F5714DE8 for ; Fri, 11 Jun 1999 07:40:39 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id KAA70517 for ; Fri, 11 Jun 1999 10:40:38 -0400 (EDT) Message-Id: <199906111440.KAA70517@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: High syscall overhead? Date: Fri, 11 Jun 1999 10:40:37 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just doing some performance testing and I noticed something rather disturbing.... Here is the test program: int main (void) { int count=0; for(count=0;count <10000000;++count) getppid(); return 0; } The time on linux for this program is ~5 seconds (linux "time" reports 3.x, but a wall clock clearly shows 5.x, go fig). FreeBSD reports 18.x seconds?!. I have a dual processor system and decided to parallel run them... it took 52!?! seconds, linux on the same was again about 5. Looking through the exception.s it appears that on entry to the kernel an MP lock is obtained... I thought we had splX(); to protect concurancy in the kernel. I am just curious what's the story with this. On some of my other tests it is clear that FreeBSD is handling concurancy much better than linux (by an equal factor actually, and on "real" tasks like real I/O handling). -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 8: 0:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 3301D151CB; Fri, 11 Jun 1999 08:00:38 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip126.houston14.tx.pub-ip.psi.net [38.27.214.126]) by leap.innerx.net (Postfix) with ESMTP id 930E3370B9; Fri, 11 Jun 1999 11:00:31 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id JAA96358; Fri, 11 Jun 1999 09:59:30 -0500 (CDT) (envelope-from chris) Date: Fri, 11 Jun 1999 09:59:25 -0500 From: Chris Costello To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: High syscall overhead? Message-ID: <19990611095925.V57174@holly.dyndns.org> Reply-To: chris@calldei.com References: <199906111440.KAA70517@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199906111440.KAA70517@cs.rpi.edu>; from David E. Cross on Fri, Jun 11, 1999 at 10:40:37AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 11, 1999, David E. Cross wrote: > Just doing some performance testing and I noticed something rather > disturbing.... > > Here is the test program: > int main (void) > { > int count=0; > for(count=0;count <10000000;++count) > getppid(); > > return 0; > } > > The time on linux for this program is ~5 seconds (linux "time" reports 3.x, but > a wall clock clearly shows 5.x, go fig). FreeBSD reports 18.x seconds?!. I > have a dual processor system and decided to parallel run them... it took > 52!?! seconds, linux on the same was again about 5. Looking through the > exception.s it appears that on entry to the kernel an MP lock is obtained... > I thought we had splX(); to protect concurancy in the kernel. ('sc' being the program above, compiled without optimization, just with cc -o sc sc.c) $ time ./sc 10.04s real 3.89s user 5.64s system I counted between around 9 and a half to 10 and a half seconds on my wall clock (trusty old GE, same model they have in public schools). Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Sun May 30 04:22:23 CDT 1999 root@holly.dyndns.org:/usr/src/sys/compile/Holly Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 67108864 (65536K bytes) sio0: system console avail memory = 62267392 (60808K bytes) SMP specific bug, perhaps? > > I am just curious what's the story with this. On some of my other tests it is > clear that FreeBSD is handling concurancy much better than linux (by an equal > factor actually, and on "real" tasks like real I/O handling). > > -- > David Cross | email: crossd@cs.rpi.edu > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Chris Costello This message transmitted on 100% recycled electrons. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 8:28:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 0F5671526E; Fri, 11 Jun 1999 08:28:17 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA71507; Fri, 11 Jun 1999 11:28:10 -0400 (EDT) Message-Id: <199906111528.LAA71507@cs.rpi.edu> To: chris@calldei.com Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: High syscall overhead? In-Reply-To: Message from Chris Costello of "Fri, 11 Jun 1999 09:59:25 CDT." <19990611095925.V57174@holly.dyndns.org> Date: Fri, 11 Jun 1999 11:28:09 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, here is some additional information from my system: bash-2.02$ cat sc.c int main (void) { int count=0; for(count=0;count <10000000;++count) getppid(); return 0; } bash-2.02$ cc -o sc sc.c bash-2.02$ uptime 11:19AM up 3 hrs, 4 users, load averages: 0.01, 0.01, 0.00 bash-2.02$ time ./sc real 0m18.523s user 0m0.000s sys 0m18.521s bash-2.02$ (date;time ./sc;date) & (date;time ./sc;date) & [3] 516 [4] 517 Fri Jun 11 11:21:51 EDT 1999 [1] Done time ./sc Fri Jun 11 11:21:51 EDT 1999 [2] Done time ./sc bash-2.02$ real 0m52.058s user 0m0.000s sys 0m52.056s real 0m52.056s user 0m0.000s sys 0m52.053s Fri Jun 11 11:22:43 EDT 1999 Fri Jun 11 11:22:43 EDT 1999 bash-2.02$ dmesg | head Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #0: Fri Jun 11 08:18:12 EDT 1999 root@phoenix.home:/usr/src/sys/compile/PHOENIX_DUAL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 268435456 (262144K bytes) avail memory = 257925120 (251880K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02df000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 It is -STABLE from June 7th, mid-day. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 8:43: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226]) by hub.freebsd.org (Postfix) with ESMTP id C2DA215167; Fri, 11 Jun 1999 08:42:57 -0700 (PDT) (envelope-from caesar@fire.starkreality.com) Received: (from caesar@localhost) by fire.starkreality.com (8.9.3/8.9.2) id KAA66007; Fri, 11 Jun 1999 10:41:30 -0500 (CDT) From: "William S. Duncanson" Message-Id: <199906111541.KAA66007@fire.starkreality.com> Subject: Re: High syscall overhead? In-Reply-To: <199906111528.LAA71507@cs.rpi.edu> from "David E. Cross" at "Jun 11, 1999 11:28: 9 am" To: crossd@cs.rpi.edu (David E. Cross) Date: Fri, 11 Jun 1999 10:41:30 -0500 (CDT) Cc: chris@calldei.com, crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 David E. Cross was heard to mumble: > Oops, here is some additional information from my system: > I can reproduce this under -CURRENT: Dual P200MMX running FreeBSD 4.0-CURRENT-990528: fire /home/caesar/src/tmp $ time ./sc real 0m34.695s user 0m20.457s sys 0m13.850s Single P200MMX running RH 6.0 Linux: hindenburg /home/wduncan/src/tmp $ time ./sc 2.24user 5.09system 0:07.53elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (65major+8minor)pagefaults 0swaps -- William S. Duncanson caesar@starkreality.com Smash forehead on keyboard to continue... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 13:46:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D6D4615431 for ; Fri, 11 Jun 1999 13:46:02 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA77498 for ; Fri, 11 Jun 1999 16:45:59 -0400 (EDT) Message-Id: <199906112045.QAA77498@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: -STABLE, panic #15 Date: Fri, 11 Jun 1999 16:45:58 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it has happened again (twice in fact). I am desperately trying to find the source of this. So far my conclusions have led me to a race in unlink and NFS somewhere (still have no clue where). And it is only from Sun clients to date. Also, this started happening in ernest arround when we put the latest patches on our Suns (this hadn't been mentioned before.) seeing how I can reliably reproduce this panic (I am trying today's STABLE now to see if I still can), does anyone have anything they would like me to try. This is reaching critical proportions for us. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 16:41:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id F06A814DAD for ; Fri, 11 Jun 1999 16:41:46 -0700 (PDT) (envelope-from conrad@apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out2.apple.com (8.8.5/8.8.5) with ESMTP id QAA39778 for ; Fri, 11 Jun 1999 16:41:47 -0700 Received: from scv4.apple.com (scv4.apple.com) by mailgate2.apple.com (mailgate2.apple.com- SMTPRS 2.0.15) with ESMTP id ; Fri, 11 Jun 1999 16:41:36 -0700 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv4.apple.com (8.9.3/8.9.3) with ESMTP id QAA63110; Fri, 11 Jun 1999 16:41:35 -0700 X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <199906112045.QAA77498@cs.rpi.edu> MIME-Version: 1.0 Date: Fri, 11 Jun 1999 16:41:29 -0700 To: "David E. Cross" From: Conrad Minshall Subject: Re: -STABLE, panic #15 Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >So far my conclusions >have led me to a race in unlink and NFS somewhere (still have no clue where). >And it is only from Sun clients to date. Also, this started happening in >ernest arround when we put the latest patches on our Suns (this hadn't been >mentioned before.) seeing how I can reliably reproduce this panic (I am trying >today's STABLE now to see if I still can), does anyone have anything they >would like me to try. OK, my NFS internals expertise is on another BSD derivative, but... If you haven't already done so, I suggest you test with all your clients mounting from the server using NFS version 2 rather than 3. Note the Solaris clients probably try V3 first and fallback to V2 so you might be able to disable V3 on your server somehow, saving the admin hassle of changing a large number of clients. Of course if you're using an automounter you already have a central point for the change. -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Apple Computer ... Mac OS X Core Operating Systems ... Filesystems & Kernel Alternative email address: rad@acm.org. "Bother" said Pooh as he uninstalled MS Windows. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 18:52:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id C625214C09 for ; Fri, 11 Jun 1999 18:52:45 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id SAA14366; Fri, 11 Jun 1999 18:51:53 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA09417; Fri, 11 Jun 1999 18:51:53 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA01497; Fri, 11 Jun 99 18:51:30 PDT Message-Id: <3761BD22.782508D3@softweyr.com> Date: Fri, 11 Jun 1999 19:51:30 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: <199906111440.KAA70517@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > Just doing some performance testing and I noticed something rather > disturbing.... > > Here is the test program: > int main (void) > { > int count=0; > for(count=0;count <10000000;++count) > getppid(); > > return 0; > } > > The time on linux for this program is ~5 seconds (linux "time" reports 3.x, but > a wall clock clearly shows 5.x, go fig). FreeBSD reports 18.x seconds?!. I > have a dual processor system and decided to parallel run them... it took > 52!?! seconds, linux on the same was again about 5. Looking through the > exception.s it appears that on entry to the kernel an MP lock is obtained... > I thought we had splX(); to protect concurancy in the kernel. > > I am just curious what's the story with this. On some of my other tests it is > clear that FreeBSD is handling concurancy much better than linux (by an equal > factor actually, and on "real" tasks like real I/O handling). My PII/300 reports: wes@homer$ time ./a.out real 0m12.490s user 0m5.898s sys 0m6.455s Let's see, that's: wes@homer$ bc bc 1.04 Copyright (C) 1991, 1992, 1993, 1994, 1997 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. 10000000/1249 8006 1000000000/1249 800640 800,000 syscalls/sec and you're complaining? Heh. ;^) I suspect this is one of those "optimizations" where the Linux syscall mechanism doesn't actually enter the kernel, since the parent pid is probably stored in the equivalent of the proc struct. True to the Linux "every cycle is precious" ethic, these optimizations are great for looking good on meaningless benchmarks like this one, and make no difference at all in "real life." Try a more meaningful benchmark, one that actually does something in the kernel before returning, and see how they do. Try calling kill or socket/close a few hundred thousand times and see how they do. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 19:16:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 1644D14BEB for ; Fri, 11 Jun 1999 19:16:39 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id WAA01426 for ; Fri, 11 Jun 1999 22:05:06 -0400 Date: Fri, 11 Jun 1999 22:05:06 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: The clean and dirty buffer list of a vnode 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 From the source code of vtruncbuf() in file vfs_subr.c, I find out that the code deals with the case when a buffer linked on the clean or dirty list of a vnode can change its identity (b_xflags flag, b_vp field, or B_DELWRI flag). For example, a buffer's B_VNCLEAN flag is cleared even if it is found on the clean list. Or a buffer's B_DELWRI flag is cleared even if it is found on the dirty list. This is new in FreeBSD 3.x. Can anyone explain to me how can this happen? Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 19:39:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3703314CD4 for ; Fri, 11 Jun 1999 19:38:59 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA81167; Fri, 11 Jun 1999 22:38:53 -0400 (EDT) Message-Id: <199906120238.WAA81167@cs.rpi.edu> To: Conrad Minshall Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: -STABLE, panic #15 In-Reply-To: Message from Conrad Minshall of "Fri, 11 Jun 1999 16:41:29 PDT." Date: Fri, 11 Jun 1999 22:37:15 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I have determined (just today) that the PANIC is only Solaris, and only with NFSv3 (It may be posssible with NFSv2, but my program doesn't do it as quickly.). I have a NFS traffic dump of a mere 19K of all nfs traffic to the machine before the panic. Also, it does NOT ALWAYS cause a panic. 95% of the time it does, the rest of the time it just stops serving NFS. I had it happen again now, and I looked and noticed that all NFSds were in disk-wait, in channel "inode". Things are starting to smell a bit sweater for me. I continue to look arround the kernel source for clues, but it is difficult. a copy of the packet dump is at: http://www.cs.rpi.edu/~crossd/FreeBSD/patoot.1 Please help. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 19:48: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5444714CD4 for ; Fri, 11 Jun 1999 19:47:50 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id TAA14495; Fri, 11 Jun 1999 19:46:55 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id TAA10013; Fri, 11 Jun 1999 19:46:55 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA03904; Fri, 11 Jun 99 19:46:38 PDT Message-Id: <3761CA09.EB525855@softweyr.com> Date: Fri, 11 Jun 1999 20:46:33 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "Stein B. Sylvarnes" Cc: Chris Dillon , hackers@FreeBSD.ORG Subject: Re: P5 vs Celeron vs PII References: <199906102221.SAA01467@etinc.com> <3.0.6.32.19990611012822.0079d930@mail.geocities.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Stein B. Sylvarnes" wrote: > > At 18:17 10.06.99 -0500, Chris Dillon wrote: > >On Thu, 10 Jun 1999, Dennis wrote: > > > >> > >> In a nutshell, does anyone have a handle on the relative preformance of > >> these are? > >> > >> 233Mhz P5 vs 233Mhz Celeron > >Last time I looked, the price difference was enough that the Celeron > >gives you more bang for the buck. > > > The AMD K6-3 has given best preformance/price, at least here in Norway. The > lead has been signifficant, but most vendors have built their PCs with > (W)Intel > CPUs. For the home-builder/upgrader, the choice has been simple, though. > > But lately Intel has dropped their prices, and if I was to buy a new CPU > now, I would have to choose between PIII and K6-3 (They're pretty much > equally fast, AMD a bit faster in Q2 in windoze) Given the following prices, which should be pretty representative in the USA: AMD-K6-2 300MHz / 350MHz / 400MHz / 450MHz 59 / 64 / 91 / 121 AMD-K6-3 400MHz / 450MHz / 500 172 / 245 / SOON Celeron Slot-1 333a / 366 / 400 / 433MHz 69 / 84 / 115 / 135 Pentium II 350MHz / 400MHz / 450MHz 169 / 182 / 245 Pentium III (Katmai) 450 / 500 / 550MHz 259 / 460 / 749 Lessee, the K6-3/400 is much faster than the PII/450 (unless you need floating point) and costs about the same. The PIII/450 is roughly as fast as K6-3/400, but costs a bunch more. The K6-3 is a killer chip, unless you need fast floating point ;^) (sorry, can't say "fast floating point" and "x86" without smiling) or SMP. The K6 motherboard and case will both probably cost less, too. Caution: I'm an AMD "advocate," not to mention a shareholder. I own several K6 systems, and would buy more. YMMV. Their greatest feature, however, is that they are NOT Intel. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 20: 1:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 883D814D13 for ; Fri, 11 Jun 1999 20:01:49 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA81383; Fri, 11 Jun 1999 23:01:43 -0400 (EDT) Message-Id: <199906120301.XAA81383@cs.rpi.edu> To: "David E. Cross" Cc: Conrad Minshall , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: -STABLE, panic #15 In-Reply-To: Message from "David E. Cross" of "Fri, 11 Jun 1999 22:37:15 EDT." <199906120238.WAA81167@cs.rpi.edu> Date: Fri, 11 Jun 1999 23:00:05 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Update, even smaller... 6.5K file, patoot.2 now exists in the same location. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 20:28:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id C98CA14BF3 for ; Fri, 11 Jun 1999 20:28:22 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA81593; Fri, 11 Jun 1999 23:28:19 -0400 (EDT) Message-Id: <199906120328.XAA81593@cs.rpi.edu> To: "David E. Cross" Cc: Conrad Minshall , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: -STABLE, panic #15 In-Reply-To: Message from "David E. Cross" of "Fri, 11 Jun 1999 23:00:05 EDT." <199906120301.XAA81383@cs.rpi.edu> Date: Fri, 11 Jun 1999 23:28:18 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I am hot on the trail... I have found a comonality(sp?) between at least 2 of the Panics. (the 2 I listed)... it is as follows: request: create cp1 request: create cp1 reply: ok reply: error, file exists request: lookup request: lookup (never any response to those.) I am guessting that: the second create gets a lock but never releases it under these conditions. the lookup comes along and *wham*. Note, that almost all of these panics occur within the nfs_lookup routines. I have *one* panic out of all of these (with lockmgr....) that doesn't after I nail this down, I will try to trace that down if it is a seperate panic. I am very close on this, I would feel bad and great at the same time if someone beats me to this. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 20:50:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id 713E814F89 for ; Fri, 11 Jun 1999 20:50:19 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id UAA01670; Fri, 11 Jun 1999 20:45:19 -0700 (PDT) From: Bill Huey Message-Id: <199906120345.UAA01670@mag.ucsd.edu> Subject: Re: High syscall overhead? To: wes@softweyr.com (Wes Peters) Date: Fri, 11 Jun 1999 20:45:19 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <3761BD22.782508D3@softweyr.com> from "Wes Peters" at Jun 11, 99 07:51: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 > Try a more meaningful benchmark, one that actually does something in > the kernel before returning, and see how they do. Try calling kill > or socket/close a few hundred thousand times and see how they do. Or that horribily impracticle wake-one semantics implemented under SMP for the accept() function with recent Linux kernels to prevent overscheduling. Or another really useless thing like releasing a MP lock in the TCP/IP stack the increases user space copies by a factor of 4 times in the Linux kernel. FreeBSD still using a single big kernel lock which slows down certain unimportant things like getting every so slow course grained kernel lock ? Are things breaking with all the new changes in the FreeBSD kernel ? Uh, "yes" to the two above questions ? > Wes Peters Softweyr LLC bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 21: 7:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ivory.lm.com (ivory.telerama.com [205.201.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 31E0C14EA8; Fri, 11 Jun 1999 21:07:17 -0700 (PDT) (envelope-from evs@telerama.com) Received: from mvehpc (d13-23.dyn.telerama.com [205.201.41.215]) by ivory.lm.com (8.8.5/8.6.12) with SMTP id AAA29650; Sat, 12 Jun 1999 00:07:10 -0400 (EDT) Message-ID: <09f401beb488$bb612390$6f27abcd@mvehpc.evs.slip.lm.com> Reply-To: "Mikhail V. Evstiounin" From: "Mikhail V. Evstiounin" To: , "David E. Cross" Cc: , Subject: Re: High syscall overhead? Date: Sat, 12 Jun 1999 00:04:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have installed 3.0-RELEASE FreeBSD on AMD K6, 233MHz, 128MB, ABit Motherboard, not overclocked/ Ran this program, got the following results: 5.2u 8.5s 0:14.02 98.3% 5+171k 0+0io 0pf+0w. :-( -----Original Message----- From: Chris Costello To: David E. Cross Cc: freebsd-hackers@FreeBSD.ORG ; freebsd-smp@FreeBSD.ORG Date: Friday, June 11, 1999 11:01 AM Subject: Re: High syscall overhead? >On Fri, Jun 11, 1999, David E. Cross wrote: >> Just doing some performance testing and I noticed something rather >> disturbing.... >> >> Here is the test program: >> int main (void) >> { >> int count=0; >> for(count=0;count <10000000;++count) >> getppid(); >> >> return 0; >> } >> >> The time on linux for this program is ~5 seconds (linux "time" reports 3.x, but >> a wall clock clearly shows 5.x, go fig). FreeBSD reports 18.x seconds?!. I >> have a dual processor system and decided to parallel run them... it took >> 52!?! seconds, linux on the same was again about 5. Looking through the >> exception.s it appears that on entry to the kernel an MP lock is obtained... >> I thought we had splX(); to protect concurancy in the kernel. > >('sc' being the program above, compiled without optimization, > just with cc -o sc sc.c) >$ time ./sc > 10.04s real 3.89s user 5.64s system > > I counted between around 9 and a half to 10 and a half seconds >on my wall clock (trusty old GE, same model they have in public >schools). > >Copyright (c) 1992-1999 The FreeBSD Project. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. >FreeBSD 4.0-CURRENT #4: Sun May 30 04:22:23 CDT 1999 > root@holly.dyndns.org:/usr/src/sys/compile/Holly >Timecounter "i8254" frequency 1193182 Hz >CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf >real memory = 67108864 (65536K bytes) >sio0: system console >avail memory = 62267392 (60808K bytes) > > SMP specific bug, perhaps? > >> >> I am just curious what's the story with this. On some of my other tests it is >> clear that FreeBSD is handling concurancy much better than linux (by an equal >> factor actually, and on "real" tasks like real I/O handling). >> >> -- >> David Cross | email: crossd@cs.rpi.edu >> Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd >> Rensselaer Polytechnic Institute, | Ph: 518.276.2860 >> Department of Computer Science | Fax: 518.276.4033 >> I speak only for myself. | WinNT:Linux::Linux:FreeBSD >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > >-- >Chris Costello >This message transmitted on 100% recycled electrons. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" 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 Jun 11 22:13:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id E23AD14E67 for ; Fri, 11 Jun 1999 22:13:44 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 57553 invoked from network); 12 Jun 1999 05:13:43 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 12 Jun 1999 05:13:43 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id AAA55650 for ; Sat, 12 Jun 1999 00:13:43 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Sat, 12 Jun 1999 00:13:43 -0500 (CDT) From: David Scheidt To: freebsd-hackers@freebsd.org Subject: softupdates 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 I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying to load the oss driver, which is not too shocking. What was shocking was the damage done to my filesystem. The automatic fsck failed, with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED INODE I=39684. Running fsck manually revealed that all inodes from 39684 to 39743 were in this state, which had to be cleared for the filesystem to be cleaned. Only one of these files, the oss/soundon.log file was likely to have been open. The rest were random .h files, and some groff config stuff. I find that quite disturbing. The machine hasn't got enough space to recover the crash dump. The panic, and at least some damage to /usr seems to be possible to recreate at will, so I can clean up things if it is worth looking into further. Here is what is in /var/log/messages for the first panic: Jun 11 21:18:13 tumbolia /kernel: OSS/FreeBSD loading, address = c0a7d0ac Jun 11 21:18:13 tumbolia /kernel: OSS: 240 minutes of evaluation time left Jun 11 21:37:53 tumbolia /kernel: OSS: 240 minutes of evaluation time left Jun 11 21:37:53 tumbolia /kernel: Jun 11 21:37:53 tumbolia /kernel: Fatal double fault: Jun 11 21:37:53 tumbolia /kernel: eip = 0xc0aacbf0 Jun 11 21:37:53 tumbolia /kernel: esp = 0xc4ca2000 Jun 11 21:37:53 tumbolia /kernel: ebp = 0xc4ca2014 Jun 11 21:37:53 tumbolia /kernel: panic: double fault Jun 11 21:37:53 tumbolia /kernel: Jun 11 21:37:53 tumbolia /kernel: syncing disks... 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 giving up Jun 11 21:37:53 tumbolia /kernel: Automatic reboot in 15 seconds - press a key o n the console to abort David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 11 23:15:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 9C8D01517E for ; Fri, 11 Jun 1999 23:15:16 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990612061516.NWCZ8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Fri, 11 Jun 1999 23:15:16 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id XAA25386; Fri, 11 Jun 1999 23:15:15 -0700 To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: <199906111440.KAA70517@cs.rpi.edu> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 11 Jun 1999 23:15:15 -0700 In-Reply-To: "David E. Cross"'s message of "Fri, 11 Jun 1999 10:40:37 -0400" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" writes: > Looking through the exception.s it appears that on entry to the > kernel an MP lock is obtained... I thought we had splX(); to > protect concurancy in the kernel. Can someone explain to me why is SYSCALL_LOCK necessary ? It certainly seems to hurt system call performance on a MP machine. Also, is there any data on lock contention in FreeBSD ? Is anyone working on decomposing some of the giant locks ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 1:33: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pallas.veritas.com (pallas.veritas.com [204.177.156.25]) by hub.freebsd.org (Postfix) with ESMTP id 1E46515145; Sat, 12 Jun 1999 01:33:03 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com (megami.veritas.com [192.203.46.101]) by pallas.veritas.com (8.9.1a/8.9.1) with SMTP id BAA04617; Sat, 12 Jun 1999 01:33:40 -0700 (PDT) Received: from sigma.veritas.com([192.203.46.125]) (1876 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sat, 12 Jun 1999 01:33:00 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #3 built 1999-Jan-25) Received: from sigma (localhost [127.0.0.1]) by sigma.veritas.com (8.9.2/8.9.1) with ESMTP id BAA40681; Sat, 12 Jun 1999 01:33:00 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Message-Id: <199906120833.BAA40681@sigma.veritas.com> From: Aaron Smith To: Arun Sharma Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: High syscall overhead? In-reply-to: Your message of "11 Jun 1999 23:15:15 PDT." Date: Sat, 12 Jun 1999 01:33:00 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Jun 1999 23:15:15 PDT, Arun Sharma writes: >Can someone explain to me why is SYSCALL_LOCK necessary ? It certainly >seems to hurt system call performance on a MP machine. > >Also, is there any data on lock contention in FreeBSD ? Is anyone >working on decomposing some of the giant locks ? I have a follow-on question: is there any planned work to give FreeBSD some of the basic synch primitives? I would love to help finer-grain the kernel, (having just today built my first SMP FreeBSD system), but first I think I'd need to implement mutexes and condition variables. It looks like there may be spin/sleeplocks and rwlocks, but they're not called that. Is there any work being done in this area? I think implementing the SVR4 synch primitives (mutex, condvars, maybe semas, rwlocks) would be great, since that's what's taught, and they're intuitive. I'm still trying to figure out the deal with "lockmgr". -- Aaron Smith VERITAS Software File System Engineer "I'll call him mini me". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 3:40:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id C224614CDF for ; Sat, 12 Jun 1999 03:40:24 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (crb@fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.3/8.9.3) with SMTP id FAA04934; Sat, 12 Jun 1999 05:40:10 -0500 (EST) (envelope-from crb@ChrisBowman.com) Message-Id: <199906121040.FAA04934@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sat, 12 Jun 1999 06:37:50 -0400 To: Arun Sharma From: "Christopher R. Bowman" Subject: Re: High syscall overhead? Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <"David E. Cross"'s message of "Fri, 11 Jun 1999 10:40:37 -0400"> <199906111440.KAA70517@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:15 PM 6/11/99 -0700, Arun Sharma wrote: >"David E. Cross" writes: > >> Looking through the exception.s it appears that on entry to the >> kernel an MP lock is obtained... I thought we had splX(); to >> protect concurancy in the kernel. > >Can someone explain to me why is SYSCALL_LOCK necessary ? It certainly >seems to hurt system call performance on a MP machine. > >Also, is there any data on lock contention in FreeBSD ? Is anyone >working on decomposing some of the giant locks ? I can't speak authoritatively since I don't know specifically what SYSCALL_LOCK is, but if it is what is often referred to on this list as the Giant Kernel Lock(tm) then the following should generally apply. When dealing with data structures there are often areas of code that must run with out any possibility of being interrupted or executing at the same time as another specific piece of code. By way of example, consider the simple act of incrementing a shared variable. In most modern RISC processors this is essentially 3 instructions: LOAD r2, #var load address of variable var into register r2 LOAD r1,r2 load the value stored in var into cpu register r1 ADD r1,r1,#1 add one to r1 and store result in r1 STORE r2,r1 store the incremented value of var back into memory Suppose that this simple 4 instruction code sequence was interrupted after the second load and before the add, and sometime later execution resumes at the add instruction. Lets first assume that we are on a uniprocessor machine, in which case there are only 2 ways this sequence of instruction can stop before that add and come back later. 1) if we are in user mode then a page boundary can occur between the load and the add, and this could lead to a page fault exception (this would be a page fault on the instruction read for the add). This cannot occur in kernel mode since if we were in kernel mode we would be inside the kernel, and the kernel wires down all of it's code pages (this might change in the future but probably only for pages that can be guaranteed will never be executed again like the startup splash screen code maybe). 2) an interrupt could occur such that the load completes, but the add does not start. This could be for a variety of reasons: perhaps a disk requests has finished, or maybe the sound card needs new data, or a clock interrupt signaling the end of a process quanta may occur. This interrupt may occur weather the code is running in user mode or in kernel mode. In either of the above 2 cases the processor typically saves the current context/state of the processor, switches to and interrupt or excerption context/state, and goes off to execute either a page fault exception handler or an interrupt handler as appropriate for the particular case. If in kernel mode at the time of the interrupt it restores the context and resumes where it was interrupted at the conclusion of the handler. If in user mode the processor may or may not resume executing the user process immediately after the interrupt is processed, but generally (baring a signal delivery for instance) when the process does resume execution it will restore the context/state and resume at the add. Now having examined how the example code could have it's execution interrupted, let us further suppose that the code that executes in between the load and the add also increments the same variable. If it happens to run a similar 4 instruction sequence then we can see that the value that get stored in memory doesn't reflect the desired effect of the 2 pieces of code and it appears as if the variable was incremented only once when it was intended to be incremented twice. If this happens to kernel code it can have catastrophic effects. To avoid this we must have some way of preventing the two pieces of code from intermingling their execution. In the FreeBSD (and all single threaded) kernels this is handled by locking out interrupts around these so called critical sections of code. So, for instance, if a variable was shared with the only network interrupt handler, the kernel would make a x=splnet() call before the second load and an splx(x) call after the store. Since the network interrupt is prevented from being serviced during between the spl calls the kernel is guaranteed that the load, add, store will proceed with out problems, and thus our problem is solved. We can see that this is so: the network interrupt which changes the variable has it's execution delayed until after the kernel updates the variable, and by assumption the other interrupts which may occur and won't be delayed, don't change the variable and thus don't present a problem. Now consider the multiprocessor case. We have the same problem we had with the single processor case, but now we also have a new variant. Suppose that both processors enter the kernel and both want to execute kernel code which will update a variable. If the second processor performs it's load after the same time as the first processor performs that add we again get improper results, and our spl mechanism for delaying interrupts doesn't help for 2 reasons: a) locking out interrupts usually occurs on only one processor, and thus the other processor could still take an interrupt that would lead to a conflict b) even if we assume that we could lock interrupts out of both processors, the 2 processors could both be executing the code as part of plain kernel code, a situation we could have on a uniprocessor machine. Some how we have got to prevent both processors from being in the kernel and executing these types of mutually exclusive code sections. If our kernel code starts out, as ours has, assuming it runs only on uniprocessor machines then usually only the variables and data structures shared with an interrupt are protected. If we then hack on second processor support we have to some how lock the data structures and global variables from simultaneous modification. A simple first order solution would be to lock out other processors from entering the kernel once one processor enters it. To do this we need only add code to start of the syscall to check for other another processor already being in the kernel and to wait for it to exit before we continue. This is the so called Giant Kernel Lock(tm) method since one lock locks the whole kernel code. This is easy to implement and incurs little overhead. If the processors spend most of their time executing user code, then they may only rarely have to wait to enter the kernel. 2 encryption processes may hardly ever enter the kernel, and may execute very efficiently. On the other hand, 2 process that read their pid in a loop might spend most of their time waiting, and thus seem to run almost as if there was only one processor. The alternative to the Giant Kernel Lock(tm) is so called fine grained locking wherein locking is pushed down closer to the data structures. In fine grained locking two processors might be executing in the kernel at the same time, but only if they didn't need the same resources. On might be doing a disk read while the other queues up a character for the serial port. The fine grained lock has the potential for higher parallelism and thus better throughput since process may not have to wait as long, but the larger number of locks with their many required lock and unlock operations add overhead and further the design is more difficult and error prone since the interaction of the numerous locks may result in deadlock or livelock situations every bit as problematical as the problem they try to solve. Well there you have it, I hope this answers some questions you had, I am sure I made a few mistakes here and there, but the overall problem is laid out for you and I am sure others will step in and correct me where I am mistaken. "Now you know, and knowing is half the battle " G.I. Joe, Sunday morning cartoons. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 5:16:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 85A6714DF2 for ; Sat, 12 Jun 1999 05:16:40 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA13526; Sat, 12 Jun 1999 14:16:21 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906121216.OAA13526@freebsd.dk> Subject: Re: High syscall overhead? In-Reply-To: <199906121040.FAA04934@quark.ChrisBowman.com> from "Christopher R. Bowman" at "Jun 12, 1999 6:37:50 am" To: crb@ChrisBowman.com (Christopher R. Bowman) Date: Sat, 12 Jun 1999 14:16:21 +0200 (CEST) Cc: adsharma@home.com, crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 It seems Christopher R. Bowman wrote: [exelent explanation snipped] > The alternative to the Giant Kernel Lock(tm) is so called fine grained locking > wherein locking is pushed down closer to the data structures. In fine grained > locking two processors might be executing in the kernel at the same time, but > only if they didn't need the same resources. On might be doing a disk read > while the other queues up a character for the serial port. The fine grained > lock has the potential for higher parallelism and thus better throughput since > process may not have to wait as long, but the larger number of locks with their > many required lock and unlock operations add overhead and further the design is > more difficult and error prone since the interaction of the numerous locks may > result in deadlock or livelock situations every bit as problematical as the > problem they try to solve. There are also those of us that dont belive in finegrained locking, exactly because of all the small locks you have to check/lock/open, the overhead is not worth it. I think a model where locks placed around resonably sized subsystems is the way to go, and can be made much easier to understand and free from (too many) bugs. I did some experiments some time ago with locks around each devicedriver, the netsubsystem, the vmsubsystem, the filesubsystem and the rest, and it performed admirably. Unfortunately I lost all that work due to "unforeseen physical happenings", but is was not that big a deal to do... I think we should consider it very carefully before going the finegrained lock route, it really doesn't give you that much in real world situations. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 6:39:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id 5A2BB14FDF for ; Sat, 12 Jun 1999 06:39:31 -0700 (PDT) (envelope-from non@ever.sanda.gr.jp) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.8.8/3.6W) with ESMTP id WAA00932; Sat, 12 Jun 1999 22:39:30 +0900 From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id WAA06887; Sat, 12 Jun 1999 22:58:48 +0900 (JST) To: newconfig@jp.freebsd.org Cc: hackers@freebsd.org Subject: sysnewconfig990609-kld990609test8.7.patch.gz In-Reply-To: Your message of "Wed, 09 Jun 1999 03:05:26 +0900" <19990609030526T.uch@nop.or.jp> References: <19990609030526T.uch@nop.or.jp> X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990612225847Z.non@ever.sanda.gr.jp> Date: Sat, 12 Jun 1999 22:58:47 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 255 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, this is brief translation from newconfig-jp ML. New dynamic loader test patch by Uchiyama san for newconfig kernel is avilable. Original messages is [newconfig-jp 2107](Subject: sysnewconfig990609-kld990609test8.7.patch.gz, From: UCHIYAMA Yasushi , Date: Wed, 09 Jun 1999 03:05:26 +0900) ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/sysnewconfig990609-kld990609test8.7.patch.gz is the patch for CVS tree at the date of June 9, 1999. > 1. Do make in directory sys/dconf/config/ and get config(8). 2. With the config(8) configure and compile kernel and loadable modules. 3. Place kernel in / and loadable modules in /modules, then reboot. 4. After reboot, do "kldload registry". New syntax `configoptions' for config(8) has been added. This is to specify either STATIC_CONFIG, DYNAMIC_CONFIG or MODULE_CONFIG. This idea is by Sota san. STATIC_CONFIG ... kernel only with static configuration DYNAMIC_CONFIG ... kernel with dynamic configuration (currently, STATIC_CONFIG and DYNAMIC_CONFIG is the same option) MODULE_CONFIG ... when compiling loadable modules Examples are sys/i386/conf/NEWCONF(static), DKERNEL(dynamic) and DMODULE(module). When you configure kernel, just place configoptions DYNAMIC_CONFIG configoptions STATIC_CONFIG at the top of the file as before. To compile just do: config FOO; cd ../../compile/FOO; make depend; make To compile loadable modules, just place lines that want to do dynamic loading in the configuration file and add, configoptions MODULE_CONFIG machine i386 in top of the file. To compile do: config FOOMODULE; cd ../../compile/FOOMODULE; make With this, you will get *.ko and registry.ko (configuration information). Put them in /modules (cp *.ko /modules). After the system boots, with command "kldload registry", modules that needed are loaded and auto configured. Drivers that directory refer cfdriver, unloading part of the drivers that loaded is not supported. When you do "kldload registry" with the kernel with DKERNEL and DMODULE, drivers are attached as below. Configuration file of loadable module: configoptions MODULE_CONFIG # Loadable module machine i386 options INET # InterNETworking cbb* at pci? dev ? func ? # PCI-CardBus bridges cardbus* at cbb? slot ? pcic0 at isa? iobase 0x3e0 membase 0xd0000 memsize 0x4000 pcic1 at isa? iobase 0x3e2 membase 0xd4000 memsize 0x4000 options PCIC_ISA_INTR_ALLOC_MASK=0xffdf # Mask IRQ 5 pcmcia* at cbb? socket ? pcmcia* at pcic? controller ? socket ? xl* at pci? dev ? func ? tx* at pci? dev ? func ? ne* at pci? dev ? func ? xl* at cardbus? dev ? func ? ep* at cardbus? dev ? func ? ep* at pcmcia? function ? # 3Com 3c589 and 3c562 Ethernet fe* at pcmcia? function ? # MB8696x based Ethernet ne* at pcmcia? function ? # NE2000-compatible Ethernet sn* at pcmcia? function ? # Megahertz Ethernet ne* at isa? iobase 0x280 irq 9 ep* at isa? iobase ? irq ? The log: a0 irq 13: INT 16 interface atkbdc0 at isa0 atkbd0 at isa0 irq 1 intr_establish:irq=1 trigger=edge ipl=tty vga0 at isa0 wdc0 at isa0 irq 14 wd0 at wdc0 unit 0: 5009MB (10258920 sectors), 10856 cyls, 15 heads, 63 S/T, 512 B/S intr_establish:irq=14 trigger=edge ipl=bio intr_establish:irq=0 trigger=pulse ipl=clock intr_establish:irq=8 trigger=pulse ipl=stat changing root device to wd0s1a { dev=-1 func=-1 } cbb-devbase-attribute: [cbb-device] (dynamic)load:cbb [config_devbase_reference: allocate new cfdriver cbb] cbb*cbb requires pci-rescan at pci?attach cbb at pci-interface with cbb_pci [config_add_cfdata: add `cbb at pci' (runtime) (removable)] { slot=-1 } cardbus-devbase-attribute: load:cardbus [cardbus-device] (dynamic)load:cardbus [config_devbase_reference: allocate new cfdriver cardbus] cardbus*cardbus requires cbb-rescan at cbb?attach cardbus at cardslot-interface with cardbus [config_add_cfdata: add `cardbus at cbb' (runtime) (removable)] { iobase=992 iosize=0 membase=851968 memsize=16384 irq=-1 drq=-1 drq2=-1 flag=0 enable=1 imask=0 } pcic-devbase-attribute: [pcic-device] (dynamic)load:pcic [config_devbase_reference: allocate new cfdriver pcic] pcic0pcic requires isa-rescan at isa?attach pcic at isa-interface with pcic_isa load:pcic_isa[config_add_cfdata: add `pcic at isa' (runtime) (removable)] { iobase=994 iosize=0 membase=868352 memsize=16384 irq=-1 drq=-1 drq2=-1 flag=0 enable=1 imask=0 } pcic1 at isa?[config_add_cfdata: add `pcic at isa' (runtime) (removable)] { controller=-1 socket=-1 } pcmcia-devbase-attribute: load:pcmcia [pcmcia-device] (dynamic)load:pcmcia [config_devbase_reference: allocate new cfdriver pcmcia] pcmcia* at cbb?attach pcmcia at pcmciabus-interface with pcmcia [config_add_cfdata: add `pcmcia at cbb' (runtime) (removable)] { controller=-1 socket=-1 } pcmcia*pcmcia requires pcic-rescan at pcic?[config_add_cfdata: add `pcmcia at pcic' (runtime) (removable)] { dev=-1 func=-1 } xl-devbase-attribute: load:ether [xl-device] (dynamic)load:xl [config_devbase_reference: allocate new cfdriver xl] xl* at pci?attach xl at pci-interface with xl [config_add_cfdata: add `xl at pci' (runtime) (removable)] { dev=-1 func=-1 } tx-devbase-attribute: [tx-device] (dynamic)load:tx [config_devbase_reference: allocate new cfdriver tx] tx* at pci?attach tx at pci-interface with tx [config_add_cfdata: add `tx at pci' (runtime) (removable)] { dev=-1 func=-1 } ne-devbase-attribute: load:dp8390nic [ne-device] (dynamic)load:ne [config_devbase_reference: allocate new cfdriver ne] ne* at pci?attach ne at pci-interface with ne_pciload:rtl80x9: rtl80x9 load:ne_pci[config_add_cfdata: add `ne at pci' (runtime) (removable)] { dev=-1 func=-1 } xl*xl requires cardbus-rescan at cardbus?attach xl at cardbus-interface with xl_cardbus load:xl_cardbus[config_add_cfdata: add `xl at cardbus' (runtime) (removable)] { dev=-1 func=-1 } ep-devbase-attribute: load:mii [ep-device] (dynamic)load:ep [config_devbase_reference: allocate new cfdriver ep] ep* at cardbus?attach ep at cardbus-interface with ep_cardbusload:elink: elink load:ep_cardbus[config_add_cfdata: add `ep at cardbus' (runtime) (removable)] { function=-1 irq=-1 } ep*ep requires pcmcia-rescan at pcmcia?attach ep at pcmcia-interface with ep_pcmcia: elink load:ep_pcmcia[config_add_cfdata: add `ep at pcmcia' (runtime) (removable)] { function=-1 irq=-1 } fe-devbase-attribute: load:mb86960 [fe-device] (dynamic)load:fe [config_devbase_reference: allocate new cfdriver fe] fe* at pcmcia?attach fe at pcmcia-interface with mbe_pcmcia load:mbe_pcmcia[config_add_cfdata: add `fe at pcmcia' (runtime) (removable)] { function=-1 irq=-1 } ne* at pcmcia?attach ne at pcmcia-interface with ne_pcmcia: rtl80x9 load:ne_pcmcia[config_add_cfdata: add `ne at pcmcia' (runtime) (removable)] { function=-1 irq=-1 } sn-devbase-attribute: load:smc91cxx [sn-device] (noobject) [config_devbase_reference: allocate new cfdriver sn] sn* at pcmcia?attach sn at pcmcia-interface with sm_pcmcia load:sm_pcmcia[config_add_cfdata: add `sn at pcmcia' (runtime) (removable)] { iobase=640 iosize=0 membase=0 memsize=0 irq=9 drq=-1 drq2=-1 flag=0 enable=1 imask=0 } ne* at isa?attach ne at isa-interface with ne_isa: rtl80x9 load:ne_isa[config_add_cfdata: add `ne at isa' (runtime) (removable)] { iobase=-1 iosize=0 membase=0 memsize=0 irq=-1 drq=-1 drq2=-1 flag=0 enable=1 imask=0 } ep* at isa?attach ep at isa-interface with ep_isa: elink load:ep_isa[config_add_cfdata: add `ep at isa' (runtime) (removable)] rescan=>pci-2 vendor 0x1039 id 0x5513 at pci0 dev 1 func 1: not configured vendor 0x1039 id 0x7001 at pci0 dev 1 func 2: not configured xl0 at pci0 dev 9 func 0: 3Com 3c905B-TX Fast Etherlink XL intr_establish:irq=12 trigger=level ipl=net xl0: Ethernet address: 00:10:4b:11:0d:d1 xl0: autoneg complete, link status good (half-duplex, 100Mbps) tx0 at pci0 dev 10 func 0: SMC 83c170 : address 00:e0:29:26:3f:93, type SMC9432TX, Auto-Neg 100Mbps intr_establish:irq=12 trigger=level ipl=net ne0 at pci0 dev 11 func 0: VIA Technologies VT86C926 Ethernet ne0: Ethernet address 00:40:26:3e:63:f3 intr_establish:irq=10 trigger=level ipl=net ne0: interrupting at irq 10 cbb0 at pci0 dev 12 func 0 (unknown), flags 0 CardBus latency time 0x10 PCI latency time 0x20 intr_establish:irq=11 trigger=level ipl=bio cbb0: interrupting at irq 11 cardbus0 at cbb0 bus 1 device 0 cardbusattach: CardBus card found [0x2] cardbus_attach_card: cb0 start cardbus_attach_card: Vendor 0x10b7, Product 0x5057, CIS 0x90 tuple: LINKTARGET len 5 0x 0: 13 3 43 49 53 tuple: MANFID len 6 0x 0: 20 4 1 1 57 50 tuple: CONFIG_CB len 8 0x 0: 4 6 3 1 0 0 0 0 tuple: CFTABLE_ENTRY_CB len 14 0x 0: 5 c 41 9a 1 b5 1e 1 55 2 30 ff ff 1 tuple: BAR len 8 0x 0: 7 6 11 0 40 0 0 0 tuple: VERS_1 len 59 0x 0: 15 39 5 0 33 43 6f 6d 20 43 6f 72 70 6f 72 61 0x10: 74 69 6f 6e 0 33 43 35 37 35 41 0 46 61 73 74 0x20: 20 45 74 68 65 72 4c 69 6e 6b 20 58 4c 20 50 43 0x30: 20 43 61 72 64 0 30 30 31 0 ff tuple: FUNCID len 4 0x 0: 21 2 6 1 tuple: END len 66 xl1 at cardbus0 dev 0 function 0 3Com 3C575TX (boomerang)xl1: Ethernet address: 00:60:08:b6:f7:5f pcmcia0 at cbb0 slot 0 cbb1 at pci0 dev 12 func 1 (unknown), flags 0 CardBus latency time 0x10 PCI latency time 0x20 intr_establish:irq=10 trigger=level ipl=bio cbb1: interrupting at irq 10 cardbus1 at cbb1 bus 2 device 1 pcmcia1 at cbb1 slot 1 cbb1: a 16-bit pcmcia card found. 5V card fe0 at pcmcia1 function 05V card : RATOC REX-R280 fe0: Ethernet address 00:c0:d0:20:8d:5b pci0: attached child device: [0:0:0 0:1:0 0:19:0 0:9:0 0:10:0 0:11:0 0:12:0 0:12:1 ] rescan=>cbb-2 rescan=>isa-2 pcic0 at isa0 port 0x3e0-0x3e1 maddr 0xd0000 msize 16384: using irq 3 pcic0: controller 0 (Intel 82365SL Revision 1) has sockets A and B intr_establish:irq=3 trigger=edge ipl=tty pcmcia2 at pcic0 controller 0 socket 0 ne1 at pcmcia2 function 0 port 0x340-0x34f port 0x350-0x35f ne1: Planet SmartCOM 2000 Ethernet ne1: Ethernet address 00:00:e8:25:ed:75 pcmcia3 at pcic0 controller 0 socket 1 ep0 at pcmcia3 function 0 port 0x330-0x33f: 3Com 3c589 10Mbps Ethernet ep0: address 00:60:97:8d:d8:e9, 8KB byte-wide FIFO, 5:3 Rx:Tx split ep0: 10baseT, 10base5, 10base2 (default 10baseT) ne2 at isa0 port 0x280-0x29f irq 9 ne2: NE2000 (RTL8019) Ethernet ne2: 10base2, 10baseT, 10baseT-FDX, auto, default auto intr_establish:irq=9 trigger=edge ipl=net ne2: Ethernet address 00:c0:f6:b0:5b:64 ep1 at isa0 port 0x300-0x30f irq 5: 3Com 3C509 Ethernet ep1: address 00:20:af:9b:13:94, 8KB byte-wide FIFO, 5:3 Rx:Tx split ep1: 10baseT, 10base5, 10base2 (default 10baseT) intr_establish:irq=5 trigger=edge ipl=net rescan=>pcic-2 rescan=>cardbus-2 rescan=>pcmcia-2 > --- > UCHIYAMA Yasushi > uch@nop.or.jp // Noriaki Mitsunaga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 7:37: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id 7839A14C07; Sat, 12 Jun 1999 07:37:03 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp524.kt.rim.or.jp [202.247.140.174]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id XAA00232; Sat, 12 Jun 1999 23:37:00 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id XAA12573; Sat, 12 Jun 1999 23:36:58 +0900 (JST) Message-ID: <37627047.D5610AB4@sky.rim.or.jp> Date: Sat, 12 Jun 1999 23:35:51 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.51 [ja] (Win95; I) X-Accept-Language: ja MIME-Version: 1.0 To: FreeBSD-current , FreeBSD-hackers Subject: FYI: CVS commit log mail notification service in Japan Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We set up open majordomo mailing lists of CVS commit log for Japanese local CVS repository. Currently, there are three ML available. To subscribe, send subscribe command to majordomo@jp.freebsd.org as usual: ----- subscribe cvs-newconfig subscribe cvs-pao subscribe cvs-pao3 ----- # cvs-pao means PAO for RELENG_2_2, cvs-pao3 means PAO for RELENG_3. You can also browse Japanese local CVS repository via cvsweb interface. If you want to see it, please visit here: http://www.jp.freebsd.org/cgi/cvsweb.cgi?cvsroot=freebsd-jp -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 9:55:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id 3271E15109 for ; Sat, 12 Jun 1999 09:55:25 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id LAA06434; Sat, 12 Jun 1999 11:53:28 -0500 (EST) (envelope-from toor) Message-Id: <199906121653.LAA06434@dyson.iquest.net.> Subject: Re: High syscall overhead? In-Reply-To: <199906121216.OAA13526@freebsd.dk> from Soren Schmidt at "Jun 12, 1999 02:16:21 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Sat, 12 Jun 1999 11:53:27 -0500 (EST) Cc: crb@ChrisBowman.com (Christopher R. Bowman), adsharma@home.com, crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Soren Schmidt said: [Charset ISO-8859-1 unsupported, filtering to ASCII...] > It seems Christopher R. Bowman wrote: > [exelent explanation snipped] > > The alternative to the Giant Kernel Lock(tm) is so called fine grained locking > > wherein locking is pushed down closer to the data structures. In fine grained > > locking two processors might be executing in the kernel at the same time, but > > only if they didn't need the same resources. On might be doing a disk read > > while the other queues up a character for the serial port. The fine grained > > lock has the potential for higher parallelism and thus better throughput since > > process may not have to wait as long, but the larger number of locks with their > > many required lock and unlock operations add overhead and further the design is > > more difficult and error prone since the interaction of the numerous locks may > > result in deadlock or livelock situations every bit as problematical as the > > problem they try to solve. > > There are also those of us that dont belive in finegrained locking, exactly > because of all the small locks you have to check/lock/open, the overhead is > not worth it. > Finegrained locking either requires developers with IQ's of 200 or higher, or a different kernel structure. I suggest that finegrained locking is cool, and can be intelligently used to mitigate (but not solve) the effects of lots of problems -- however, it would be unwise to embark on an effort to make the FreeBSD kernel into an efficent 16way SMP kernel by using finegrained locking all over the place. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 9:57:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id EDCF815109 for ; Sat, 12 Jun 1999 09:57:54 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id LAA06439; Sat, 12 Jun 1999 11:57:41 -0500 (EST) (envelope-from toor) Message-Id: <199906121657.LAA06439@dyson.iquest.net.> Subject: Re: High syscall overhead? In-Reply-To: <3761BD22.782508D3@softweyr.com> from Wes Peters at "Jun 11, 1999 07:51:30 pm" To: wes@softweyr.com (Wes Peters) Date: Sat, 12 Jun 1999 11:57:41 -0500 (EST) Cc: crossd@cs.rpi.edu (David E. Cross), freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Wes Peters said: > > Try a more meaningful benchmark, one that actually does something in > the kernel before returning, and see how they do. Try calling kill > or socket/close a few hundred thousand times and see how they do. > Historically, my emphasis on FreeBSD kernel work was to make it work best while under load, doing lots of things. By benchmarking the system while the system isn't really doing anything really pessimizes the advantages of the FreeBSD choices. Linux is indeed much faster at doing nothing!!! I suspect that some intrepid individual could improve FreeBSD a little, but the risk/reward would be too severe. Think of it like this: since alot of desktops sit in idle loops much of the time, perhaps the Linux philosophy has been to improve such behavior :-). -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 10:39:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scrabble.freeuk.net (scrabble.freeuk.net [212.126.144.6]) by hub.freebsd.org (Postfix) with ESMTP id C4E6314E30 for ; Sat, 12 Jun 1999 10:39:50 -0700 (PDT) (envelope-from andrew@cream.org) Received: from [212.126.149.114] (helo=cream.org) by scrabble.freeuk.net with esmtp (Exim 2.11 #1) id 10srky-00072q-00 for hackers@freebsd.org; Sat, 12 Jun 1999 17:39:48 +0000 Content-Length: 1055 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: Sat, 12 Jun 1999 18:36:57 +0100 (BST) From: Andrew Boothman To: hackers@freebsd.org Subject: compat22 / ld.so - FAQ Addition Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings! I've noticed that questions- frequently gets many people asking about "ld.so" problems that they've had since upgrading to 3.x from 2.2.x and the answer to their problem is almost always the same. Therefore I'd like to make sure that the following information is accurate before I submit it to the docproj. Thanks! 500a501,511 > > > I've upgraded from 2.2.x to 3.x and now I get ld.so errors >

3.x FreeBSD systems by default use a different binary format from the > 2.2.x systems. For this reason, when upgrading, the libraries that were > used to execute the old 2.2.x binaries are upgraded so that you can > execute the new 3.x binaries. > >

If you need to execute 2.2.x binaries on a 3.x system you should > install the 'compat22' port in /usr/ports/compat22/ which > will install the old 2.2.x libraries. --- Andrew Boothman http://sour.cream.org Unmetered Telecoms. Join the Fight! http://www.unmetered.org.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 10:40:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 03D5E14E84; Sat, 12 Jun 1999 10:40:33 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990612174033.QNET8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Sat, 12 Jun 1999 10:40:33 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id KAA25937; Sat, 12 Jun 1999 10:40:32 -0700 To: Aaron Smith Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: High syscall overhead? References: <199906120833.BAA40681@sigma.veritas.com> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 12 Jun 1999 10:40:32 -0700 In-Reply-To: Aaron Smith's message of "Sat, 12 Jun 1999 01:33:00 -0700" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aaron Smith writes: > I'm still trying to figure out the deal with "lockmgr". I found the following doc useful: http://www.freebsd.org/~fsmp/SMP/Locking.html -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 10:51:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 9B9EB14F6E for ; Sat, 12 Jun 1999 10:51:12 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990612175112.QPDN8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Sat, 12 Jun 1999 10:51:12 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id KAA25968; Sat, 12 Jun 1999 10:51:11 -0700 To: "Christopher R. Bowman" Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: <"David E. Cross"'s message of "Fri, 11 Jun 1999 10:40:37 -0400"> <199906111440.KAA70517@cs.rpi.edu> <199906121040.FAA04934@quark.ChrisBowman.com> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 12 Jun 1999 10:51:11 -0700 In-Reply-To: "Christopher R. Bowman"'s message of "Sat, 12 Jun 1999 06:37:50 -0400" Message-ID: Lines: 31 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Christopher R. Bowman" writes: > > I can't speak authoritatively since I don't know specifically what > SYSCALL_LOCK is, but if it is what is often referred to on this list > as the Giant Kernel Lock(tm) then the following should generally > apply. > You're right. The SYSCALL_LOCK is the same as the giant lock. The name kinda misled me to assume that it's a different lock. i386/i386/lock.h: /* * Some handy macros to allow logical organization and * convenient reassignment of various locks. */ #define FPU_LOCK call _get_fpu_lock #define ALIGN_LOCK call _get_align_lock #define SYSCALL_LOCK call _get_syscall_lock #define ALTSYSCALL_LOCK call _get_altsyscall_lock All of the above routines seem to be identical. But the code is duplicated for some reason. Also, it might be beneficial to define these locks in a header file and inline them, instead of generating a call for each simple_lock. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 11: 9:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id E765214E84 for ; Sat, 12 Jun 1999 11:09:49 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990612180949.QRZF8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Sat, 12 Jun 1999 11:09:49 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id LAA26052; Sat, 12 Jun 1999 11:09:49 -0700 To: dyson@iquest.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: <199906121653.LAA06434@dyson.iquest.net.> From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 12 Jun 1999 11:09:48 -0700 In-Reply-To: "John S. Dyson"'s message of "Sat, 12 Jun 1999 11:53:27 -0500 (EST)" Message-ID: Lines: 35 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" writes: > Finegrained locking either requires developers with IQ's of 200 or higher, > or a different kernel structure. I suggest that finegrained locking is cool, > and can be intelligently used to mitigate (but not solve) the effects of > lots of problems Fine grained locking is hard - but it isn't exactly rocket science. It's been tackled in a number of OSes, papers have been written about it. > -- however, it would be unwise to embark on an effort to make > the FreeBSD kernel into an efficent 16way SMP kernel by using finegrained > locking all over the place. Sure. But 2 and 4-way boxes are becoming more and more mainstream. And any IO bound job is not going to perform well on FreeBSD because of giant locking. One way of tackling the problem is - to implement per lock profiling and detect which locks are being contested heavily and try breaking them down. That would be a practical way of doing things. An alternative way, which requires a good understanding of both the theory and implementation of the kernel is - (a) Implement per subsystem locking (b) Figure out in a "typical" workload, how much time is being spent in which subsystem and try increasing parallelism (i.e. finer grained locking) in subsystems where more time is being spent. The result of this approach should be more logical, cleaner and possibly better performing than the previous one. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 11:16:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 860FA14E84 for ; Sat, 12 Jun 1999 11:16:17 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA08613; Sat, 12 Jun 1999 14:14:09 -0400 (EDT) Date: Sat, 12 Jun 1999 14:14:09 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "John S. Dyson" Cc: Soren Schmidt , "Christopher R. Bowman" , adsharma@home.com, crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? In-Reply-To: <199906121653.LAA06434@dyson.iquest.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 Sat, 12 Jun 1999, John S. Dyson wrote: > Soren Schmidt said: > [Charset ISO-8859-1 unsupported, filtering to ASCII...] > > It seems Christopher R. Bowman wrote: > > [exelent explanation snipped] > > > The alternative to the Giant Kernel Lock(tm) is so called fine grained locking > > > wherein locking is pushed down closer to the data structures. In fine grained > > > locking two processors might be executing in the kernel at the same time, but > > > only if they didn't need the same resources. On might be doing a disk read > > > while the other queues up a character for the serial port. The fine grained > > > lock has the potential for higher parallelism and thus better throughput since > > > process may not have to wait as long, but the larger number of locks with their > > > many required lock and unlock operations add overhead and further the design is > > > more difficult and error prone since the interaction of the numerous locks may > > > result in deadlock or livelock situations every bit as problematical as the > > > problem they try to solve. > > > > There are also those of us that dont belive in finegrained locking, exactly > > because of all the small locks you have to check/lock/open, the overhead is > > not worth it. > > > Finegrained locking either requires developers with IQ's of 200 or higher, > or a different kernel structure. I suggest that finegrained locking is cool, > and can be intelligently used to mitigate (but not solve) the effects of > lots of problems -- however, it would be unwise to embark on an effort to make > the FreeBSD kernel into an efficent 16way SMP kernel by using finegrained > locking all over the place. But your microkernel-hybrid BSD will do 16way SMP with a fully-parallelized kernel? > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 11:23:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id D9FEB14E84 for ; Sat, 12 Jun 1999 11:23:40 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA08760; Sat, 12 Jun 1999 14:23:40 -0400 (EDT) Date: Sat, 12 Jun 1999 14:23:40 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Arun Sharma Cc: dyson@iquest.net, freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? 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 12 Jun 1999, Arun Sharma wrote: > "John S. Dyson" writes: > > > Finegrained locking either requires developers with IQ's of 200 or higher, > > or a different kernel structure. I suggest that finegrained locking is cool, > > and can be intelligently used to mitigate (but not solve) the effects of > > lots of problems > > Fine grained locking is hard - but it isn't exactly rocket > science. It's been tackled in a number of OSes, papers have been > written about it. That's untrue if you're using asynchronous I/O. > > > -- however, it would be unwise to embark on an effort to make > > the FreeBSD kernel into an efficent 16way SMP kernel by using finegrained > > locking all over the place. > > Sure. But 2 and 4-way boxes are becoming more and more mainstream. And > any IO bound job is not going to perform well on FreeBSD because of > giant locking. Not quite as well, but it will still be much faster. Besides, FreeBSD would perform better under load than nearly any other OS, so it's not as if it would be slower than something else. > > One way of tackling the problem is - to implement per lock profiling > and detect which locks are being contested heavily and try breaking > them down. That would be a practical way of doing things. But you can't generalize FreeBSD's usage, can you? > > An alternative way, which requires a good understanding of both the > theory and implementation of the kernel is - > > (a) Implement per subsystem locking That seems to be the most winning solution. > (b) Figure out in a "typical" workload, how much time is being spent > in which subsystem and try increasing parallelism (i.e. finer > grained locking) in subsystems where more time is being spent. Once again, there is no "typical" unless you try to overgeneralize and say "FreeBSD is used mostly for XXX." This would be just an extension of a. But this is much less of a gain (from what I conjecture). It would make sense to have separate locks for, say, at least the I/O subsystems (all in total, not for each one. Why do you want to parallel something that's doing DMA?), FS interfaces, VM/trapping, and networking. > > The result of this approach should be more logical, cleaner and > possibly better performing than the previous one. > > -Arun > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 11:44:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6455614D92 for ; Sat, 12 Jun 1999 11:44:41 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA14011; Sat, 12 Jun 1999 20:44:31 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906121844.UAA14011@freebsd.dk> Subject: Re: High syscall overhead? In-Reply-To: from Arun Sharma at "Jun 12, 1999 11: 9:48 am" To: adsharma@home.com (Arun Sharma) Date: Sat, 12 Jun 1999 20:44:31 +0200 (CEST) Cc: dyson@iquest.net, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 It seems Arun Sharma wrote: > An alternative way, which requires a good understanding of both the > theory and implementation of the kernel is - > > (a) Implement per subsystem locking This was exactly what I experimented with some 7-8 month ago, it showed significant improvements in performance, yet it was relatively easy to do. > (b) Figure out in a "typical" workload, how much time is being spent > in which subsystem and try increasing parallelism (i.e. finer > grained locking) in subsystems where more time is being spent. Well, my simple tests showed no need for this, again its a fine balance between spending the time waiting, and spending the time processing locks. > The result of this approach should be more logical, cleaner and > possibly better performing than the previous one. It sure is easier to understand and to maintain. Maybe I should try it again, and this time keep off-site backups :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 13:23: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5378B14BFA for ; Sat, 12 Jun 1999 13:23:07 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id NAA16231; Sat, 12 Jun 1999 13:14:59 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id NAA05865; Sat, 12 Jun 1999 13:14:59 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA16642; Sat, 12 Jun 99 13:14:30 PDT Message-Id: <3762BFA6.B46F8C39@softweyr.com> Date: Sat, 12 Jun 1999 14:14:30 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Soren Schmidt Cc: Arun Sharma , dyson@iquest.net, freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: <199906121844.UAA14011@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Arun Sharma wrote: > > An alternative way, which requires a good understanding of both the > > theory and implementation of the kernel is - > > > > (a) Implement per subsystem locking > > This was exactly what I experimented with some 7-8 month ago, it > showed significant improvements in performance, yet it was relatively > easy to do. > > > (b) Figure out in a "typical" workload, how much time is being spent > > in which subsystem and try increasing parallelism (i.e. finer > > grained locking) in subsystems where more time is being spent. > > Well, my simple tests showed no need for this, again its a fine > balance between spending the time waiting, and spending the time > processing locks. Implementing some (optional) benchmarking code for the locks would make it pretty simple to do this as a follow-on project, once the initial "several-sorta-big-locks" project is stable. There's always room for improvement. > > The result of this approach should be more logical, cleaner and > > possibly better performing than the previous one. > > It sure is easier to understand and to maintain. Maybe I should > try it again, and this time keep off-site backups :) I have disk space available. ;^) Actually, I have a DLT drive available now, too. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 13:25:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 07BC514CD0 for ; Sat, 12 Jun 1999 13:25:28 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA23074; Sat, 12 Jun 1999 13:25:26 -0700 (PDT) Date: Sat, 12 Jun 1999 13:25:25 -0700 (PDT) From: Julian Elischer To: Conrad Minshall Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: -STABLE, panic #15 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 Thanks conrad.. All the appropriate FreeBSD people were at usenix.. (didn't see you there......) julian On Fri, 11 Jun 1999, Conrad Minshall wrote: > >So far my conclusions > >have led me to a race in unlink and NFS somewhere (still have no clue where). > >And it is only from Sun clients to date. Also, this started happening in > >ernest arround when we put the latest patches on our Suns (this hadn't been > >mentioned before.) seeing how I can reliably reproduce this panic (I am trying > >today's STABLE now to see if I still can), does anyone have anything they > >would like me to try. > > OK, my NFS internals expertise is on another BSD derivative, but... > > If you haven't already done so, I suggest you test with all your clients > mounting from the server using NFS version 2 rather than 3. Note the > Solaris clients probably try V3 first and fallback to V2 so you might be > able to disable V3 on your server somehow, saving the admin hassle of > changing a large number of clients. Of course if you're using an > automounter you already have a central point for the change. > > > -- > Conrad Minshall ... conrad@apple.com ... 408 974-2749 > Apple Computer ... Mac OS X Core Operating Systems ... Filesystems & Kernel > Alternative email address: rad@acm.org. > > "Bother" said Pooh as he uninstalled MS Windows. > Oh gosh I just had to laugh... > > > > > 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 Sat Jun 12 14:12:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id B906D15061 for ; Sat, 12 Jun 1999 14:12:52 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990612211252.RSJE8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Sat, 12 Jun 1999 14:12:52 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id OAA26280; Sat, 12 Jun 1999 14:12:52 -0700 To: Brian Feldman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 12 Jun 1999 14:12:52 -0700 In-Reply-To: Brian Feldman's message of "Sat, 12 Jun 1999 14:23:40 -0400 (EDT)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > > One way of tackling the problem is - to implement per lock profiling > > and detect which locks are being contested heavily and try breaking > > them down. That would be a practical way of doing things. > > But you can't generalize FreeBSD's usage, can you? > While it's true that no one can see all possible uses of FreeBSD, one has to make assumptions about the typical usage - web server, file server etc and use it as the design center, while making sure that it doesn't perform too badly on other less common workloads. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 18: 8:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 102AA14CE4 for ; Sat, 12 Jun 1999 18:08:54 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 18900 invoked from network); 13 Jun 1999 01:08:53 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 13 Jun 1999 01:08:53 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id UAA05697; Sat, 12 Jun 1999 20:08:51 -0500 (EST) From: "John S. Dyson" Message-Id: <199906130108.UAA05697@dyson.iquest.net> Subject: Re: High syscall overhead? In-Reply-To: from Arun Sharma at "Jun 12, 99 11:09:48 am" To: adsharma@home.com (Arun Sharma) Date: Sat, 12 Jun 1999 20:08:51 -0500 (EST) Cc: dyson@iquest.net, 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 > "John S. Dyson" writes: > > > Finegrained locking either requires developers with IQ's of 200 or higher, > > or a different kernel structure. I suggest that finegrained locking is cool, > > and can be intelligently used to mitigate (but not solve) the effects of > > lots of problems > > Fine grained locking is hard - but it isn't exactly rocket > science. It's been tackled in a number of OSes, papers have been > written about it. > I also have played with the SVR4 SMP kernel (the real working one), not some of the toys that called themselves SMP -- but later versions were much better than even what I worked on. I can say that the maintainability of the code sucked, and the problems were due to the ARCHITECTURE of the original kernel. Sure, it can be done, but it has to be done methodically, and simple non-SMP changes preciptate massive SMP changes. The typical monlithic kernels are just the right answer to the wrong problem, if you are talking optimal SMP solutions. > > Sure. But 2 and 4-way boxes are becoming more and more mainstream. And > any IO bound job is not going to perform well on FreeBSD because of > giant locking. > I agree. However, I suggest that finegrained locking will be a loosing proposition. Something in-between is probably good. My brains got fried on trying to figure out a GOOD solution for the FreeBSD kernel. There are no GOOD solutions, but a reasonable compromise is some kind of medium grained scheme. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 19:55:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id 9A1BD15023 for ; Sat, 12 Jun 1999 19:55:06 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id TAA02805; Sat, 12 Jun 1999 19:50:05 -0700 (PDT) From: Bill Huey Message-Id: <199906130250.TAA02805@mag.ucsd.edu> Subject: Re: High syscall overhead? To: dyson@iquest.net Date: Sat, 12 Jun 1999 19:50:05 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199906121657.LAA06439@dyson.iquest.net.> from "John S. Dyson" at Jun 12, 99 11:57:41 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 > > Wes Peters said: > > > > Try a more meaningful benchmark, one that actually does something in > > the kernel before returning, and see how they do. Try calling kill > > or socket/close a few hundred thousand times and see how they do. This will only test how fast the kernel memory allocator will perform with small object. Linux will do well since the memory allocation stuff is pretty standard issue for kernel memory allocators. > Think of it like this: since alot of desktops sit in idle loops much > of the time, perhaps the Linux philosophy has been to improve such > behavior :-). The Linux philosophy already has better performance and will also get you much stronger TCP/IP user land copy performance under SMP since it releases locks around the data copy. This certain is much better that the over simplistic single MP in FreeBSD, which has since been abandon in the Linux kernel. But I guess technical denial works in the FreeBSD community. ;-) More smilie faces ;-) ;-) ;-) > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. bill > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > > > 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 Sat Jun 12 20: 0:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id E730C14C1D for ; Sat, 12 Jun 1999 20:00:16 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id TAA02876; Sat, 12 Jun 1999 19:55:12 -0700 (PDT) From: Bill Huey Message-Id: <199906130255.TAA02876@mag.ucsd.edu> Subject: Re: High syscall overhead? To: toor@dyson.iquest.net (John S. Dyson) Date: Sat, 12 Jun 1999 19:55:12 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199906130108.UAA05697@dyson.iquest.net> from "John S. Dyson" at Jun 12, 99 08:08:51 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 agree. However, I suggest that finegrained locking will be a loosing > proposition. Something in-between is probably good. My brains got fried > on trying to figure out a GOOD solution for the FreeBSD kernel. There > are no GOOD solutions, but a reasonable compromise is some kind of medium > grained scheme. Which is why FreeBSD will go through many of same locking problems in Linux, since they are coming from monolithic kernel origins. Race conditions processor synchronization, per processor cache hit issues, etc... > John bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 20: 9: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id A7AFB14C38 for ; Sat, 12 Jun 1999 20:08:40 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.194] by guepardo.vicosa.com.br with ESMTP (SMTPD32-5.00) id A396195012C; Sun, 13 Jun 1999 00:20:54 -0300 Message-ID: <3762F4E7.17CE49D4@tdnet.com.br> Date: Sun, 13 Jun 1999 00:01:43 +0000 From: Unknow User X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: quota crash my system, how to fix it ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quota crash my system after quotaoff followed by quotaon! I applied a patch (kern/8137), but it did not work! Can anybody explain how could i fix this problem. here goes the patch i applied: *** ufs_quota.c Tue Jul 9 12:51:17 1996 --- /net/www/home/pammy/ufs_quota.c Sat Oct 3 13:25:05 1998 *************** *** 775,781 **** dp = dq->dq_forw; if (dp) dp->dq_back = dq->dq_back; ! *dq->dq_back = dp; } /* * Initialize the contents of the dquot structure. --- 775,783 ---- dp = dq->dq_forw; if (dp) dp->dq_back = dq->dq_back; ! dp = dq->dq_back; ! if (dp) ! dp->dq_forw = dq->dq_forw; } /* * Initialize the contents of the dquot structure. -- "The box said 'Requires Windows 98, NT, Linux or better' so I installed FreeBSD." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 20:20:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id A168514C9E for ; Sat, 12 Jun 1999 20:20:08 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 19300 invoked from network); 13 Jun 1999 03:20:07 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 13 Jun 1999 03:20:07 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id WAA05857; Sat, 12 Jun 1999 22:20:05 -0500 (EST) From: "John S. Dyson" Message-Id: <199906130320.WAA05857@dyson.iquest.net> Subject: Re: High syscall overhead? In-Reply-To: <199906130250.TAA02805@mag.ucsd.edu> from Bill Huey at "Jun 12, 99 07:50:05 pm" To: billh@mag.ucsd.edu (Bill Huey) Date: Sat, 12 Jun 1999 22:20:05 -0500 (EST) Cc: dyson@iquest.net, 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 > > > Think of it like this: since alot of desktops sit in idle loops much > > of the time, perhaps the Linux philosophy has been to improve such > > behavior :-). > > The Linux philosophy already has better performance and will also get > you much stronger TCP/IP user land copy performance under SMP since > it releases locks around the data copy. > In a general sense, FreeBSD will still outperform Linux, however in SMP, FreeBSD is behind... It is alot of fun to look towards the "new" linux VM code, "can you say tweak, tweak???" This is a perfect example of coding vs. design. There is NO need for explicit policies (steal a page here or there in specific places.) When DG and I were first playing with the code, DG admonished me continually to avoid nonsense "policies" and that is probably a very significant contribution in the end. We ended up with a scheme that develops it's own policy, and it is difficult to track what the system is doing, let alone "control" it better than the system can do itself. Note that in a non-trivial WWW server, the system isn't waiting on TCP, but is dealing with CGI. I suspect that it would be very useful for the FreeBSD team for Linux to "improve" their SMP. I hope they create really fine grained locks all over the place... With all of those fine grained locks, they can expand the domain of the optimized spin loop :-). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 21:39:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 52D9314D7B for ; Sat, 12 Jun 1999 21:39:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA65304; Sat, 12 Jun 1999 21:39:25 -0700 (PDT) (envelope-from dillon) Date: Sat, 12 Jun 1999 21:39:25 -0700 (PDT) From: Matthew Dillon Message-Id: <199906130439.VAA65304@apollo.backplane.com> To: hgoldste@bbs.mpcs.com (Howard Goldstein), dyson@iquest.net, freebsd-hackers@FreeBSD.ORG, "John S. Dyson" Subject: Re: problem for the VM gurus References: <199906091233.HAA00173@dyson.iquest.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting. It's an overlapping same-process deadlock with mmap/write. This bug also hits NFS, though in a slightly different way, and also occurs with mmap/write when two processes are mmap'ing two files and write()ing the other descriptor using the map as a buffer. I see a three-stage solution: * We change the API for the VM pager *getpages() code. At the moment the caller busies all pages being passed to getpages() and expects the primary page (but not any of the others) to be returned busied. I also believe that some of the code assumes that the page will not be unbusied at all for the duration of the operation ( though vm_fault was hacked to handle the situation where it might have been ). This API is screwing up NFS and would also make it very difficult for general VFS deadlock avoidance to be implemented properly and for a fix to the specific case being discussed in this thread to be implemented properly. I recommend changing the API such that *ALL* passed pages are unbusied prior to return. The caller of getpages() must then VM lookup the page again. Always. vm_fault already does this, in fact. We would clean up the code and document it to this effect. This change would allow us to immediately fix the self-referential deadlocks and I think it would also allow me to fix a similar bug in NFS trivially. * We hack a fix to deal with the mmap/write case. A permanent vnode locking fix is many months away because core decided to ask Kirk to fix it, which was news to me at the time. However, I agree with the idea of having Kirk fix VNode locking. But since this sort of permanent fix is months away, we really need an interim solution to the mmap/write deadlock case. The easiest interim solution is to break write atomicy. That is, unlock the vnode if the backing store of the uio being written is (A) vnode-pager-backed and (B) not all in-core. This will generally fix all known deadlock situations but at the cost of write atomicy in certain cases. We can use the same hack that pipe code uses and only guarentee write atomicy for small block sizes. We would do this by wiring ( and faulting, if necessary ) the first N pages of the uio prior to locking the vnode. We cannot wire all the pages of the uio since the user may specify a very large buffer - megabytes or gigabytes. * Stage 3: Permanent fix is committed by generally fixing vnode locks and VFS layering. ... which may be 6 months if Kirk agrees to do a complete rewrite of the vnode locking algorithms. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 21:44:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8934D14C57 for ; Sat, 12 Jun 1999 21:44:42 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id AAA17818 for ; Sun, 13 Jun 1999 00:44:50 -0400 (EDT) Date: Sun, 13 Jun 1999 00:44:50 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.org Subject: select(2) breakage 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'm using the attached program which I wrote today (don't ask why, I think I just wanted to beat the heck out of FreeBSD!) I have maxusers 200, a MAXFILES=65536, and the limits set to allow me to use the program fully (all 30000 ports; I don't want to monopolize EVERY port...) When run, select doesn't time out after 60 seconds like it should. Another problem that came up with this: I originally started at port 1024. I monopolized 30000 ports (almost all consecutive, of course). When I try to connect() a TCP socket as non-root, it fails with EAGAIN (I only tracked it far enough down as in_pcbbind().) It seems that eventually it gives up trying to find a port... :-/ Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" /*- * Copyright (c) 1999 Brian Fundakowski Feldman * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $Id$ * */ #include #include #include #include #include #include #include #include #include #include #include int anothersocket(u_short port) { struct sockaddr_in sin; int fd, serrno; if ((fd = socket(PF_INET, SOCK_STREAM, 0)) == -1) return fd; sin.sin_family = AF_INET; sin.sin_port = htons(port); sin.sin_addr.s_addr = htonl(INADDR_ANY); if (bind(fd, (struct sockaddr *)&sin, sizeof(sin)) == -1) { serrno = errno; close(fd); errno = serrno; return -1; } listen(fd, 1); return fd; } int allocatesockets(int *fdvec, u_short *portvec, int nsockets) { int fd, ncreated = 0, serrno; u_short port = 32768; while (nsockets) { if (++port == 65535) break; if ((fd = anothersocket(port)) == -1) if (errno == ENFILE || errno == EMFILE) { serrno = errno; close(fdvec[--ncreated]); errno = serrno; break; } else continue; portvec[ncreated] = port; fdvec[ncreated++] = fd; nsockets--; } return ncreated; } int main(int argc, char **argv) { int fdvec[30000]; u_short portvec[30000]; int nsockets, tmp, highestsock; fd_set odescriptors, ndescriptors; struct timeval timeout; nsockets = allocatesockets(fdvec, portvec, sizeof(fdvec) / sizeof(fdvec[0])); printf("%s started: %d PF_INET SOCK_STREAM sockets ready\n", strrchr(argv[0], '/') + 1, nsockets); highestsock = fdvec[nsockets - 1] + 1; FD_ZERO(&odescriptors); for (tmp = 0; tmp < nsockets; tmp++) FD_SET(fdvec[tmp], &odescriptors); for (;;) { int nfound, curnum, nset; int *selected; u_short *selectedports; const struct timespec sleeper = { 0, 100000000 }; timeout.tv_sec = 60; timeout.tv_usec = 0; ndescriptors = odescriptors; if ((nfound = select(highestsock, &ndescriptors, NULL, NULL, &timeout)) < 1) { if (nfound == -1) perror("select()"); else printf("no select() action"); continue; } selected = malloc(nfound * sizeof(int)); selectedports = malloc(nfound * sizeof(u_short)); for (curnum = nset = 0; nset < nfound; curnum++) { if (!FD_ISSET(fdvec[curnum], &ndescriptors)) continue; selectedports[nset] = portvec[curnum]; selected[nset++] = accept(fdvec[curnum], NULL, NULL); } printf("Sockets ready:\n\t"); for (nset = 0; nset < nfound; nset++) printf("%d,", selectedports[nset]); putchar('\n'); for (nset = 0; nset < nfound; nset++) close(selected[nset]); free(selected); free(selectedports); nanosleep(&sleeper, NULL); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 21:48:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A271614F7D for ; Sat, 12 Jun 1999 21:48:38 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id VAA16685; Sat, 12 Jun 1999 21:44:54 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA17834; Sat, 12 Jun 1999 21:44:55 -0700 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA06779; Sat, 12 Jun 99 21:44:26 PDT Message-Id: <37633725.3BD5BECD@softweyr.com> Date: Sat, 12 Jun 1999 22:44:22 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Bill Huey Cc: dyson@iquest.net, freebsd-hackers@FreeBSD.ORG Subject: Re: High syscall overhead? References: <199906130250.TAA02805@mag.ucsd.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Huey wrote: > > > Think of it like this: since alot of desktops sit in idle loops much > > of the time, perhaps the Linux philosophy has been to improve such > > behavior :-). > > The Linux philosophy already has better performance and will also get > you much stronger TCP/IP user land copy performance under SMP since > it releases locks around the data copy. The Linux philosophy has always been about simplistic cycle counting exercises without understand whether the data had any meaning or not. You've once again displayed your wholehearted participation in this lack of understanding of what the data points might mean to any real- world application. > This certain is much better that the over simplistic single MP in > FreeBSD, which has since been abandon in the Linux kernel. And your deep understanding of the technical issues surrounding such a change lends you the credence to declare it was "abandon", rather that just "moved on from," right? > But I guess technical denial works in the FreeBSD community. ;-) I don't know about the rest of you guys, but this shithead just pole- vaulted onto the top of my email "kill" list. All noise, no content. Bye, Bill. It's been nice not knowing you. In case you're wondering, I know a tiny bit about Linux SMP. I was helping debug support for SMP in LinuxPPC over the phone this week, with one of the developers working on it. I know very little about the SMP support in Linux, but have had a fair amount of experience doing MP work on RISC processors. The engineer working on it needed a couple of good, or even not-so-good questions to get him unstuck; I was happy to provide a peanut gallery. So, explain to me again about that "technical denial" part. Or, better yet, just fuck off and get the hell off our list. This is NOT an appropriate forum for Linux advocacy, which seems to be all you can do. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 23:14:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id CA4AB14D0E for ; Sat, 12 Jun 1999 23:14:24 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id CAA19251 for ; Sun, 13 Jun 1999 02:14:32 -0400 (EDT) Date: Sun, 13 Jun 1999 02:14:32 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.ORG Subject: Just connect(2) breakage (Was Re: select(2) breakage) 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, 13 Jun 1999, Brian Feldman wrote: > I'm using the attached program which I wrote today (don't ask why, I think > I just wanted to beat the heck out of FreeBSD!) I have maxusers 200, a > MAXFILES=65536, and the limits set to allow me to use the program > fully (all 30000 ports; I don't want to monopolize EVERY port...) When > run, select doesn't time out after 60 seconds like it should. Disregard this part! User error (not making sure stdio is flushed). > Another problem that came up with this: I originally started at port 1024. > I monopolized 30000 ports (almost all consecutive, of course). When I try to > connect() a TCP socket as non-root, it fails with EAGAIN (I only tracked it > far enough down as in_pcbbind().) It seems that eventually it gives up trying > to find a port... :-/ This problem is quite real. > > Brian Feldman _ __ ___ ____ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | > http://www.freebsd.org _ |___/___/___/ > " THAT'S WRONG WRONG WRONG!" > > /*- > * Copyright (c) 1999 Brian Fundakowski Feldman > * All rights reserved. > * > * Redistribution and use in source and binary forms, with or without > * modification, are permitted provided that the following conditions > * are met: > * 1. Redistributions of source code must retain the above copyright > * notice, this list of conditions and the following disclaimer. > * 2. Redistributions in binary form must reproduce the above copyright > * notice, this list of conditions and the following disclaimer in the > * documentation and/or other materials provided with the distribution. > * > * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND > * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE > * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE > * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE > * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL > * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS > * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) > * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT > * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY > * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > * SUCH DAMAGE. > * > * $Id$ > * > */ > > #include > #include > #include > #include > > #include > > #include > #include > #include > #include > #include > #include > > int > anothersocket(u_short port) { > struct sockaddr_in sin; > int fd, serrno; > > if ((fd = socket(PF_INET, SOCK_STREAM, 0)) == -1) > return fd; > > sin.sin_family = AF_INET; > sin.sin_port = htons(port); > sin.sin_addr.s_addr = htonl(INADDR_ANY); > if (bind(fd, (struct sockaddr *)&sin, sizeof(sin)) == -1) { > serrno = errno; > close(fd); > errno = serrno; > return -1; > } > > listen(fd, 1); > > return fd; > } > > int > allocatesockets(int *fdvec, u_short *portvec, int nsockets) { > int fd, ncreated = 0, serrno; > u_short port = 32768; > > while (nsockets) { > if (++port == 65535) > break; > if ((fd = anothersocket(port)) == -1) > if (errno == ENFILE || errno == EMFILE) { > serrno = errno; > close(fdvec[--ncreated]); > errno = serrno; > break; > } else > continue; > portvec[ncreated] = port; > fdvec[ncreated++] = fd; > nsockets--; > } > > return ncreated; > } > > int > main(int argc, char **argv) { > int fdvec[30000]; > u_short portvec[30000]; > int nsockets, tmp, highestsock; > fd_set odescriptors, ndescriptors; > struct timeval timeout; > > nsockets = allocatesockets(fdvec, portvec, > sizeof(fdvec) / sizeof(fdvec[0])); > printf("%s started: %d PF_INET SOCK_STREAM sockets ready\n", > strrchr(argv[0], '/') + 1, nsockets); > highestsock = fdvec[nsockets - 1] + 1; > FD_ZERO(&odescriptors); > for (tmp = 0; tmp < nsockets; tmp++) > FD_SET(fdvec[tmp], &odescriptors); > > for (;;) { > int nfound, curnum, nset; > int *selected; > u_short *selectedports; > const struct timespec sleeper = { 0, 100000000 }; > > timeout.tv_sec = 60; > timeout.tv_usec = 0; > > ndescriptors = odescriptors; > if ((nfound = select(highestsock, &ndescriptors, NULL, NULL, > &timeout)) < 1) { > if (nfound == -1) > perror("select()"); > else > printf("no select() action"); > continue; > } > > selected = malloc(nfound * sizeof(int)); > selectedports = malloc(nfound * sizeof(u_short)); > for (curnum = nset = 0; nset < nfound; curnum++) { > if (!FD_ISSET(fdvec[curnum], &ndescriptors)) > continue; > > selectedports[nset] = portvec[curnum]; > selected[nset++] = accept(fdvec[curnum], NULL, NULL); > } > > printf("Sockets ready:\n\t"); > for (nset = 0; nset < nfound; nset++) > printf("%d,", selectedports[nset]); > putchar('\n'); > > for (nset = 0; nset < nfound; nset++) > close(selected[nset]); > > free(selected); > free(selectedports); > nanosleep(&sleeper, NULL); > } > } > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ " THAT'S WRONG WRONG WRONG!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 23:32:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id C9B4514D0E for ; Sat, 12 Jun 1999 23:32:31 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id XAA03037; Sat, 12 Jun 1999 23:24:12 -0700 (PDT) From: Bill Huey Message-Id: <199906130624.XAA03037@mag.ucsd.edu> Subject: Re: High syscall overhead? To: wes@softweyr.com (Wes Peters) Date: Sat, 12 Jun 1999 23:24:11 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <37633725.3BD5BECD@softweyr.com> from "Wes Peters" at Jun 12, 99 10:44:22 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 > The Linux philosophy has always been about simplistic cycle counting > exercises without understand whether the data had any meaning or not. > You've once again displayed your wholehearted participation in this > lack of understanding of what the data points might mean to any real- > world application. Well, the thing I'm talking about isn't a philosophy, because it removed data serialization doing what I suspect is a kernel/user space copy from doing a superficial glance of the code. This is one of the detected bottlenecks in the Mindcraft study that suck copy performance by approximately 4 times. Another things that was included on the like bottleneck list is the waking of all the processes in the process queue when accept() is being called. This was termed the "Thundering Herds" problem, which they solve using a wake-one process implementation of accept(). > denial" part. Or, better yet, just fuck off and get the hell off our > list. This is NOT an appropriate forum for Linux advocacy, which seems > to be all you can do. Well, so far I've heard alot of BS about Linux that isn't exactly true and much of it seems like a bunch of artificial problems that hold against the Linux folks. Most of it is just intentionally misrepresented bullshit. I came on this list initially to just check was the FreeBSD community was like, but what I've gotten since is alot of ego and hostility toward things that aren't completely FreeBSD. That's something that I didn't expect and reading this list has given me a particular negative view of FreeBSD that wasn't present before. In-fighting with the current NFS maintainer and general rudeness to other potential devs make FreeBSD's kernel people look like bunch of dorks whether you like it or not. I'm also not big enough asshole ot put someone on a "kill-list" and is just a reflection of a kind of conservative need to dehumanize other folks so that your selfish comfort is "preserved". > Wes Peters Softweyr LLC bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 12 23:42:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 03C1314CB7 for ; Sat, 12 Jun 1999 23:42:41 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id IAA13786; Sun, 13 Jun 1999 08:35:35 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id IAA49502; Sun, 13 Jun 1999 08:42:07 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id IAA66947; Sun, 13 Jun 1999 08:42:50 +0200 (CEST) (envelope-from ticso) Date: Sun, 13 Jun 1999 08:42:50 +0200 From: Bernd Walter To: David Scheidt Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates problem? Message-ID: <19990613084249.A66895@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from David Scheidt on Sat, Jun 12, 1999 at 12:13:43AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote: > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying > to load the oss driver, which is not too shocking. What was shocking > was the damage done to my filesystem. The automatic fsck failed, > with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED > INODE I=39684. > What kernel-config are you using? I have had several fs-crashes because of a to high configured maxusers. It happens if the kernel wants to use the configured limits but can't because there is not enough space for that high maxuser. In recent releases I can't find any reason to configure it higher than default. Everything else that sometimes need to be higher can be set individualy. It may be that the added driver triggers the already aimed gun. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message