From owner-freebsd-current Sun Oct 26 00:15:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22625 for current-outgoing; Sun, 26 Oct 1997 00:15:05 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from sweden.it.earthlink.net (sweden-c.it.earthlink.net [204.250.46.50]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA22608 for ; Sun, 26 Oct 1997 00:14:56 -0700 (PDT) (envelope-from rfbent@earthlink.net) From: rfbent@earthlink.net Received: from user900.meznet4.net (1Cust239.tnt1.broken-arrow.ok.da.uu.net [208.254.16.239]) by sweden.it.earthlink.net (8.8.7/8.8.5) with SMTP id AAA12287; Sun, 26 Oct 1997 00:13:08 -0700 (PDT) Message-Id: <199710260713.AAA12287@sweden.it.earthlink.net> To: cumeater@eighteen.net Subject: MONEY MIRACLE ! *! Reply-To: rfbent@earthlink.net Date: Fri, 11 Oct 97 22:24:52 EST Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Filterd Via The Remove List At http://www.antispam.org *** Important Message - Sent Using The Zenith Bulk Emailer *** For Your FREE Copy Of This Program - http://www.ultra-mail.com/zenithDear On-Line Friend: I have received this letter at least three times during the last two months, so I gave in and said "Well, lets see if it really works". To keep a long story short, I have received over $12,000 in cash in less than four weeks. I am now a true believer!!! This is a "One-time message", you were randomly selected to receive this. If you have interest in this, please "DO NOT CLICK REPLY" Use the contact information in this message. Thank You! ***PRINT THIS FOR FUTURE REFERENCE*** The following income opportunity is one you may be interested in taking a look at, it can be started with $5 DOLLARS $5 and the income return is Tremendous !~!~! You are about to make at least $50,000 in less than 90 days! Please read the program...Then read it again !!! The money making potential is fantastic! In this program you are looking at the most profitable money making program you may ever see. It has demonstrated proven ability to generate large sums of money. This is a legitimate "LEGAL" money making opportunity. No contact with people, no hard work, and best of all you never have to leave the house..."Except to collect the money from your mailbox" Simply follow these simple instructions, and your dream will come true! This electronic Multi-Level-Marketing program works every time! Thousands of people have used it to generate huge amounts of capital, to start their own business...to take a vacation...to become debt-free etc. AN OVERVIEW OF THIS EXTRAORDINARY ELECTRONIC MULT-LEVEL-MARKETING PROGRAM We sell thousands of people a product for $5.00 that costs us next to nothing to produce and e-mail. As with all Multi-Level-Businesses, we build our business by recruiting new partners and selling our products. Every state in the U.S. allows you to recruit new Multi-Level business on-line (with your computer). The product in this program is a series of four businesses and financial reports. Each $5.00 order you receive by "Snail-Mail" will include the e-mail address of a sender. To fill each order, you simply e-mail the product to the buyer. THAT'S IT !...the $5.00 is yours! This is the Greatest electronic Multi-Level-Marketing business anywhere !!! FOLLOW THESE INSTRUCTIONS EXACTLY! ***** I N S T R U C T I O N S ***** THIS IS WHAT YOU HAVE TO DO: 1. Order all 4 reports listed and numbered from the list below. For each report send $5.00 CASH, YOUR E-MAIL ADDRESS and YOUR RETURN POSTAL ADDRESS (in case of a problem) to each person listed. When you order, make sure you request each SPECIFIC report. You will need all four reports, because you will be sending them on your computer and reselling them. 2. IMPORTANT-DO NOT alter the names, or their sequence other than instructed in this program! Or you will not profit the way you should. Replace the name and address under REPORT #1 with yours, moving the one that was there down to REPORT #2. Move the name and address under REPORT #2 to #3. Move the name and address under REPORT #3 to REPORT #4. The name and address that was under REPORT #4 is dropped from the list and is NO DOUBT on the way to the bank. When doing this, PLEASE make certain you copy everyone's name and address ACCURATELY!!! Also, DO NOT move the REPORT/PRODUCT positions. 3. Take this entire program text, including the corrected names list, and save it on your computer. Now you're ready to start a massive advertising campaign on the WORLDWIDE WEB! Advertising on the WEB is so very inexpensive, with HUNDREDS of FREE places to advertise. You could use e-mail ads such as the one you are reading now! There are many "Bulk e-mail Companies" that will advertise for you. Use any search engine to find these services. Use keywords like: "e-mail advertising... or try Bulk e-mail" START YOUR AD CAMPAIGN AS SOON AS YOU CAN !!! ALWAYS PROVIDE SAME-DAY SERVICE ON ALL ORDERS REQUIRED REPORTS *****Order each REPORT by NUMBER and NAME***** Always send $5.00 cash(concealed) for each order requesting the specific reports by NAME and NUMBER. Always send FIRST CLASS or PRIORTY MAIL and provide your e-mail address for quick delivery. Always Send A Self-Addressed Stamped Envelope! REPORT #1: "HOW TO MAKE $250,000 THROUGH MULTI-LEVEL MARKETING SALES" ORDER REPORT #1 FROM: RFB 8210 E. 71 Street, #158 Tulsa, OK 74011 REPORT #2: "MAJOR CORPORATIONS AND MULT-LEVEL SALES" ORDER REPORT #2 FROM: CCM ENT. P.O.Box 1235 Mooresville, N.C. 28115 REPORT #3: "SOURCES FOR THE BEST MAILING LISTS" ORDER REPORT #3 FROM: FF ENT. P.O. BOX 4375 Lancaster, CA 92160 REPORT #4: "EVALUATING MULTI-LEVEL SALES PROGRAMS" ORDER REPORT #4 FROM: GES ENT. P.O.BOX 601162 SAN DIEGO, CA 92160 HERE'S HOW THIS AMAZING PLAN WILL MAKE YOU MONEY BEYOND YOUR DREAMS !!! Let's say you decide to start small just to see how it goes. Assume your goal is to recruit 10 people to participate on your first level. (placing a lot of FREE ads on the Internet could EASILY get a better response), Also assume that everyone else in YOUR BUILDING ORGANIZATION gets ONLY 10 downline members. Follow this example for the STAGGERING results below. 1 Level - Your 10 members with $5.00 2 Level - 10 members from those 10 ($5 x 100) 3 Level - 10 members from those 100 ($5 x 1,000) 4 Level - 10 members from those 1,000 ($5 x 10,000) THE FIGURES FOR THE ABOVE!!! Level 1 = $50.00 Level 2 = $500.00 Level 3 = $5,000.00 Level 4 = $50,000.00 THIS TOTALS~~> $55,550.00 Remember friends, this is assuming that the people who participate only recruit 10 people each. Dare to think for a moment what would happen if everyone got 20 people to participate! Some people get 100's of recruits! THINK ABOUT IT! By the way...your cost to participate in this is practically nothing. You obviously already have an Internet connection and e-mail is FREE!!! REPORT #3 will show you how the best methods for bulk emailing and purchasing email lists. REMEMBER: Approx. 250,000 new people get on line monthly! ORDER YOUR REPORTS NOW!!! ***** tips for success***** Treat this as your business! Send for the four reports "IMMEDIATELY" so you will have them when the orders start coming in, because: When you receive a $5.00 order, you MUST send out the requested product/report to comply with the U. S. Postal & Lottery Laws, Title 18, Sections 1302 and 1341 or Title 18, Section 3005 in the U. S. Code, also Code of Federal Regs. Vol 16, Sections 255 and 436 which state that "A product or service must be exchanged for money received." * ALWAYS PROVIDE SAME-DAY SERVICE ON THE ORDERS YOU RECEIVE. * * Be patient and persistent with this program. If you follow the instructions exactly...results WILL UNDOUBTEDLY BE SUCCESS! * * ABOVE ALL, HAVE FAITH IN YOURSELF THAT YOU CAN SUCCEED! *****your success guideline***** The checkpoint that guarantees your success is simply this: You must receive 5 to 10 orders for report #1! If you don't within four weeks, advertise more and send out more programs until you do. Then, a couple of weeks later you should receive at least 100 orders for REPORT #2. If you don't, advertise more and send out more programs until you do. Once you have received 100 orders for REPORT #2, YOU CAN RELAX...because you will be on your way to the bank! -OR- You can DOUBLE your efforts! REMEMBER: Every time your name is moved down the list you are in front of a DIFFERENT report, so you can KEEP TRACK of your PROGRESS by watching what report the people are ordering from you. It's That Easy!!! NOTE: IF YOU NEED HELP with starting a business, registering a business name, how income tax is handled, etc., contact your local office of the Small Business Administration (a Federal agency) for free help and answers to questions. Also, the Internal Revenue Service offers free via telephone and free seminars about business taxes. *****testimonials***** This program does work, but you must follow it EXACTLY! Especially the rule of not trying to place your name in a different position. It won't work, you'll lose a lot of money. I'm living proof that it works. It really is a great opportunity to make relatively easy money, with little cost to you. If you do choose to participate, follow the program exactly, and you'll be on your way to financial security. If you are a fellow Christian and are in financial trouble like I was, consider this a sign. I did! Good Luck & God Bless you, Sincerely, Chris Johnson P.S. Do you have any Idea what 11,700 $5 bills ($58,500) looks like piled on the kitchen table?...Its AWESOME !!! ******************** My name is Frank. My wife Doris and I live in Bel-Air, MD. I am a cost accountant with a major U. S. Corporation and I make pretty good money. When I received the program I grumbled to Doris about receiving "junk mail"! I made fun of the whole thing, spouting my knowledge of the population and percentages involved. I "knew" it wouldn't work. Doris totally ignored my supposed intelligence and jumped right in with both feet. I made merciless fun of her, and was ready to lay the old "I told you so" on her when the thing didn't work... well, the laugh was on me! Within two weeks she had received over 50 responses, Within 45 days she had received over $147,200 in $5 dollar bills!!! I WAS STUNED!!! I was sure that I had it all figured and that it wouldn't work...I am a believer now. I have joined Doris in her "little" hobby. I did have seven more years until retirement, but I think of the "rat race" and it's not for me...We owe it all to MLM. Frank T., Bel-Air, MD ******************** I just want to pass along my best wishes and encouragement to you. Any doubts you have will vanish when your first orders come in. I even checked with the U. S. Post Office to verify that the plan was legal. It definently is! IT WORKS!!! Paul Johnson, Raleigh, NC ******************** This is the only realistic money-making offer I've ever received. I participated because this plan truly makes sense. I was surprised when the $5 bills started filling my mailbox. By the time it tapered off I had received over 8,000 orders with over $40,000 in cash. Dozens of people have sent warm personal notes too, sharing the news of their good fortunes! It's been WONDERFUL. Carl Winlow, Tulsa, OK ******************** The main reason for this letter is to convince you that this system is honest, lawful, extremely profitable, and is a way to get a large amount of money in a short time. I was approached several times before I checked this out. I joined just to see what one could expect in return for the minimal effort and money required. Initially I let no one in the organization know that I was an attorney and, to my astonishment, I received $34,470.00 in the first 14 weeks, with money still coming in. Sincerely yours, Phillip A. Brown ******************** This plan works like Gang-Busters!!! So far I have had 9,735 total orders...OVER $48,000!!! I hope I have sparked your own excitement, if you follow the program exactly, you could have the same success I have, If not better. Your success is right around the corner, but you must do a little work. Good Luck! G. Bank ******************** Not being a gambling type, it took me several weeks to make up my mind to participate in this plan. But conservative that I am I decided that the initial investment was so little that there was just no way that I could get enough orders to at least get my money back. Boy was I surprised when I found my mediem-sized post office box crammed with orders. After that it got so over-loaded that I had to start picking up the mail at the window. I'll make more money this year than any 10 years of my life before. Th nice thing about this deal is that it doesn't matter where you live in the U. S. the people live. There simply isn't a better investment with a faster return. Mary Rockland, Lansing, MI ******************** I had received this program before. I deleted it, but later I wondered if I should have given it a try. Ofcourse, I had no idea who to contact to get another copy, so I had to wait until I was E-Mailed another program...11 months passed then it came...I didn't delete this one!...I made $41,000 on the first try!! D. Wilburn, Muncie, IN From owner-freebsd-current Sun Oct 26 14:05:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23022 for current-outgoing; Sun, 26 Oct 1997 14:05:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA23000 for ; Sun, 26 Oct 1997 14:04:59 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 1982 invoked from network); 26 Oct 1997 22:04:51 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 26 Oct 1997 22:04:51 -0000 Received: (from root@localhost) by mordred.cs.ucla.edu (8.8.7/8.8.7) id OAA05984 for freebsd-current@freebsd.org; Sun, 26 Oct 1997 14:04:44 -0800 (PST) (envelope-from scottm) From: Scott Michel Message-Id: <199710262204.OAA05984@mordred.cs.ucla.edu> Subject: rpc_svcout.c To: freebsd-current@freebsd.org Date: Sun, 26 Oct 1997 14:04:44 -0800 (PST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Somehow, on the latest current snap, this file has gone missing. From owner-freebsd-current Sun Oct 26 18:19:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06380 for current-outgoing; Sun, 26 Oct 1997 18:19:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06375 for ; Sun, 26 Oct 1997 18:19:45 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id CAA11441 for ; Mon, 27 Oct 1997 02:19:43 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id DAA00414; Mon, 27 Oct 1997 03:19:42 +0100 (MET) Date: Mon, 27 Oct 1997 03:19:42 +0100 (MET) Message-Id: <199710270219.DAA00414@bitbox.follo.net> From: Eivind Eklund To: freebsd-current@freebsd.org Subject: Directories disappearing? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Starting approx a week ago, directories have started to disappear from my -current system. It only seem to affect directories in which files are added/removed (both operations have had directories disappearing under my feet). Anybody else that are having the same problem? Any suspect changes? I've not had enough disk activity for the files in the directories to go away through proper unlinks - I've had a a directory with 3000 files disappear with nary a sound from the disk. fsck is not reporting any problems with the disk this has happened on. Eivind. From owner-freebsd-current Sun Oct 26 18:24:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06548 for current-outgoing; Sun, 26 Oct 1997 18:24:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06514 for ; Sun, 26 Oct 1997 18:23:54 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id CAA11461 for ; Mon, 27 Oct 1997 02:23:51 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id DAA00430; Mon, 27 Oct 1997 03:23:51 +0100 (MET) Date: Mon, 27 Oct 1997 03:23:51 +0100 (MET) Message-Id: <199710270223.DAA00430@bitbox.follo.net> From: Eivind Eklund To: freebsd-current@freebsd.org Subject: Missing dirs Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Forget the 3500 files dir disappearing - that dir had just lost an index file, and I though it was gone with the others. But there still are 3 dirs that have mysteriously disappeared without a trace; dirs I have been working in that just said 'poof'. Eivind. From owner-freebsd-current Sun Oct 26 19:04:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08269 for current-outgoing; Sun, 26 Oct 1997 19:04:50 -0800 (PST) (envelope-from owner-freebsd-current) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08264 for ; Sun, 26 Oct 1997 19:04:42 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by earth.mat.net (8.8.7/8.6.12) with SMTP id WAA28407 for ; Sun, 26 Oct 1997 22:04:34 -0500 (EST) Date: Sun, 26 Oct 1997 20:59:47 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-current@FreeBSD.org Subject: Pine strangeness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I am suddenly noticing, when using pine, that sometimes my outgoing messages cause pine to hang. I can no long use ^Z to suspend pine, and no other keyboard keys work. I can use kill procno -STOP to suspend it, but no other signals seem to free it. The state ps sees is "S+", the man page on ps says thats "process sleeping for less than 20 seconds". Believe me, I've waited far longer than that. Oh, my environment is -current, on an SMP box. I'd like to fix this myself; does anyone have any tips I could use for doing this, next time it hangs? I'm going to replace my pine binary with one compiled with debug symbols ... but maybe something else could tell me what pine could be hung with? I don't have any indication yet what's really causing it, so I can't make it reoccur with any regularity. It's happened 3 times in the last week. As anyone reading this list knows, there's a lot of mail going thru it. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Oct 26 19:39:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10310 for current-outgoing; Sun, 26 Oct 1997 19:39:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10304 for ; Sun, 26 Oct 1997 19:39:56 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by earth.mat.net (8.8.7/8.6.12) with SMTP id WAA29853; Sun, 26 Oct 1997 22:39:47 -0500 (EST) Date: Sun, 26 Oct 1997 21:38:56 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Eivind Eklund cc: freebsd-current@FreeBSD.ORG Subject: Re: Directories disappearing? In-Reply-To: <199710270219.DAA00414@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, Eivind Eklund wrote: > > Starting approx a week ago, directories have started to disappear from > my -current system. It only seem to affect directories in which files > are added/removed (both operations have had directories disappearing > under my feet). > > Anybody else that are having the same problem? Any suspect changes? > I've not had enough disk activity for the files in the directories to > go away through proper unlinks - I've had a a directory with 3000 > files disappear with nary a sound from the disk. > > fsck is not reporting any problems with the disk this has happened on. Tell more. Are you running SMP? Have you looked into your archive, are the files really gone, or unhooked from cvs? I'm suddenly having problems with my mailer locking up on sending a message, I suspect it has to do with locking, and it's not common enough for it to be reproducible yet. I don't know ... it sounds like we need more data. > > Eivind. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Oct 26 20:40:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13595 for current-outgoing; Sun, 26 Oct 1997 20:40:00 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fragile.ideal.net.au (rob@fragile.ideal.net.au [203.20.241.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13584 for ; Sun, 26 Oct 1997 20:39:50 -0800 (PST) (envelope-from rob@ideal.net.au) Received: from localhost (rob@localhost) by fragile.ideal.net.au (8.8.6/8.8.5) with SMTP id PAA06029 for ; Mon, 27 Oct 1997 15:39:36 +1100 (EST) Date: Mon, 27 Oct 1997 15:39:36 +1100 (EST) From: Rob Wise To: current@freebsd.org Subject: sound blaster 16 on dual pentium motherboard Message-ID: X-WonK: Hmm MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I recently changed my fbsd workstation from a single P100 motherboard to a dual P100 motherboard. All the hardware is the same except for the addition of a multi i/o controller since it isn't done on the motherboard. After booting up on the new board I am unable to detect the sound card. I'm about 99% sure this is a freebsd problem because win95 will detect it on the same hardware. it used to detect as: Aug 19 12:53:53 magnesium /kernel: sb0 at 0x220-0x22f irq 5 drq 1 on isa Aug 19 12:53:53 magnesium /kernel: sb0: Aug 19 12:53:53 magnesium /kernel: sbxvi0 drq 5 on isa Aug 19 12:53:53 magnesium /kernel: sbxvi0: Aug 19 12:53:53 magnesium /kernel: sbmidi0 at 0x330-0x331 on isa Aug 19 12:53:53 magnesium /kernel: sbmidi0: now i get: Oct 23 13:47:54 magnesium /kernel: sb0 not found at 0x220 Oct 23 13:47:54 magnesium /kernel: sbxvi0 not found Oct 23 13:47:54 magnesium /kernel: sbmidi0 not found at 0x330 The motherboard is an old Gigabyte Dual P90/P100 board. Anybody else noticed this? Any debugging I should be providing you guys with? Thanks, Rob From owner-freebsd-current Sun Oct 26 21:31:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16189 for current-outgoing; Sun, 26 Oct 1997 21:31:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16173 for ; Sun, 26 Oct 1997 21:31:30 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id IAA06562; Mon, 27 Oct 1997 08:30:52 +0300 (MSK) (envelope-from ache) Date: Mon, 27 Oct 1997 08:30:50 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Chuck Robey cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Pine strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 26 Oct 1997, Chuck Robey wrote: > I am suddenly noticing, when using pine, that sometimes my outgoing > messages cause pine to hang. I can no long use ^Z to suspend pine, and no > other keyboard keys work. I can use kill procno -STOP to suspend it, but > no other signals seem to free it. The state ps sees is "S+", the man page > on ps says thats "process sleeping for less than 20 seconds". Believe me, > I've waited far longer than that. Oh, my environment is -current, on an > SMP box. Pine needs lots of memory for big mailboxes. Try to increase your datasize limit via login.conf -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Sun Oct 26 22:23:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18466 for current-outgoing; Sun, 26 Oct 1997 22:23:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18461 for ; Sun, 26 Oct 1997 22:23:48 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id HAA16183; Mon, 27 Oct 1997 07:22:51 +0100 (CET) To: Eivind Eklund cc: freebsd-current@freebsd.org Subject: Re: Directories disappearing? In-reply-to: Your message of "Mon, 27 Oct 1997 03:19:42 +0100." <199710270219.DAA00414@bitbox.follo.net> Date: Mon, 27 Oct 1997 07:22:51 +0100 Message-ID: <16181.877933371@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could you at least give us some details, like what kind of filesystem ??? Poul-Henning In message <199710270219.DAA00414@bitbox.follo.net>, Eivind Eklund writes: > >Starting approx a week ago, directories have started to disappear from >my -current system. It only seem to affect directories in which files >are added/removed (both operations have had directories disappearing >under my feet). > >Anybody else that are having the same problem? Any suspect changes? >I've not had enough disk activity for the files in the directories to >go away through proper unlinks - I've had a a directory with 3000 >files disappear with nary a sound from the disk. > >fsck is not reporting any problems with the disk this has happened on. > >Eivind. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Sun Oct 26 22:31:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18786 for current-outgoing; Sun, 26 Oct 1997 22:31:14 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18779 for ; Sun, 26 Oct 1997 22:31:10 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id BAA22869; Mon, 27 Oct 1997 01:30:41 -0500 (EST) Date: Mon, 27 Oct 1997 01:30:41 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Chuck Robey cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Pine strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 26 Oct 1997, Chuck Robey wrote: > I am suddenly noticing, when using pine, that sometimes my outgoing > messages cause pine to hang. I can no long use ^Z to suspend pine, and no > other keyboard keys work. I can use kill procno -STOP to suspend it, but Try the enable-background-sending option on config and see if that helps. Read the help screen for that option for details. -john From owner-freebsd-current Sun Oct 26 23:03:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20418 for current-outgoing; Sun, 26 Oct 1997 23:03:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA20411 for ; Sun, 26 Oct 1997 23:03:06 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xPjCL-0006JV-00; Sun, 26 Oct 1997 23:02:49 -0800 Date: Sun, 26 Oct 1997 23:02:43 -0800 (PST) From: Tom To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: Chuck Robey , FreeBSD-current@freebsd.org Subject: Re: Pine strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id XAA20413 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ× wrote: > On Sun, 26 Oct 1997, Chuck Robey wrote: > > > I am suddenly noticing, when using pine, that sometimes my outgoing > > messages cause pine to hang. I can no long use ^Z to suspend pine, and no > > other keyboard keys work. I can use kill procno -STOP to suspend it, but > > no other signals seem to free it. The state ps sees is "S+", the man page > > on ps says thats "process sleeping for less than 20 seconds". Believe me, > > I've waited far longer than that. Oh, my environment is -current, on an > > SMP box. > > Pine needs lots of memory for big mailboxes. Try to increase your datasize > limit via login.conf In this case he is sending e-mail, so I don't think that is it. I've have this exact same problem with pine. My solution was to switch it to SMTP. By default, pine exec /usr/sbin/sendmail with a bunch of options and pipes the message in. You can set it to contact sendmail on the localhost instead, and use SMPT (just set "mail-server" settting to enable this feature). I have never had it hang when doing this. I suspect a problem with the params that Pine execs sendmail with. Or, perhaps a big with pipes in Pine. > -- > Andrey A. Chernov > > http://www.nagual.pp.ru/~ache/ > > > Tom From owner-freebsd-current Mon Oct 27 00:15:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA25390 for current-outgoing; Mon, 27 Oct 1997 00:15:58 -0800 (PST) (envelope-from owner-freebsd-current) Received: from g23.relcom.ru (g23.relcom.ru [193.125.152.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA25374 for ; Mon, 27 Oct 1997 00:15:46 -0800 (PST) (envelope-from maxim@mas2000.msk.ru) Received: from d150.z193-124-241.relcom.ru (d150.z193-124-241.relcom.ru [193.124.241.150]) by g23.relcom.ru (8.7.5.R.ML.S/Relcom-2A) with SMTP id LAA28694 for ;Mon, 27 Oct 1997 11:05:08 +0300 (MSK) Received: from [100.0.0.52] by diamond.mas2000.msk.ru (NTMail 3.02.13) with ESMTP id ha003569 for ; Mon, 27 Oct 1997 10:50:22 +0300 Message-Id: <3.0.32.19971026234716.0069b2ac@100.0.0.2> X-Sender: maxim@100.0.0.2 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 26 Oct 1997 23:47:17 +0300 To: Alex From: Maxim Surdu Subject: Re: out of swap space causes hang Cc: current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I had the same problem on my DualPentium 166 with 64Mb RAM and 128 Swap..... Also I have a 4 Mb Diamond 3000 (VirgeVX Chipset) so I have used X server running 24bpp mode... I had problems I could describe here if I may: Under linux emulation I couldnt run Problem Solution Staroffice 3.1 Change X server to 16bpp mode Desc: It simply hangs (seems like out of swap memory!!! but It doesn't) PixMap Change X server to 16bpp mode Desc: When you try to start it as root it hangs! When it starts from user shell it writes Couldn't calloc. Any other problems? Hope it helps >I decided to edit a little xpm today with pixmap. As it was saving the >pixmap, which apparently is a very memory & time consuming process, my >computer decided to just completely hang, no panic no nothing. Since this >is the second time this has happened to me today (totally different >circumstances), I decided to check the logs. Right before the copytight >message of my latest boot the last message that seemed strange was >/kernel: swap_pager: out of space. Now I have 128Mb swap and 64Mb ram, >and I'm running a make world a few weeks old and a kernel a few days old. >Kinda annoying. Anyone else seeing this? ---------------------- Regards from Maxim Surdu maxim@mas2000.msk.ru From owner-freebsd-current Mon Oct 27 05:46:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA20466 for current-outgoing; Mon, 27 Oct 1997 05:46:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA20459 for ; Mon, 27 Oct 1997 05:46:09 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 8289 invoked from network); 27 Oct 1997 13:46:02 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 27 Oct 1997 13:46:02 -0000 From: "Evan Champion" To: Subject: 971026 wouldn't let me set timezone Date: Mon, 27 Oct 1997 08:46:02 -0500 Message-ID: <01bce2de$aa206c80$513654c7@cello.synapse.net> 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.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just a note that 3.0-current-971026's sysinstall won't let me set the timezone. It seems that the timezone option is just a no-op. It also failed installing one of the XFree card-specific servers (sorry, I don't remember which one). Evan From owner-freebsd-current Mon Oct 27 07:51:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA27693 for current-outgoing; Mon, 27 Oct 1997 07:51:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA27687 for ; Mon, 27 Oct 1997 07:51:07 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.7/8.8.5) with SMTP id JAA11937; Mon, 27 Oct 1997 09:49:52 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Mon, 27 Oct 1997 09:49:51 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: John Fieber cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Pine strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, John Fieber wrote: > On Sun, 26 Oct 1997, Chuck Robey wrote: > > > I am suddenly noticing, when using pine, that sometimes my outgoing > > messages cause pine to hang. I can no long use ^Z to suspend pine, and no > > other keyboard keys work. I can use kill procno -STOP to suspend it, but > > Try the enable-background-sending option on config and see if > that helps. Read the help screen for that option for details. Good guess, but I already had that one set ... > > -john > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Oct 27 08:24:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA29833 for current-outgoing; Mon, 27 Oct 1997 08:24:40 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA29824 for ; Mon, 27 Oct 1997 08:24:29 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA29772; Mon, 27 Oct 1997 16:24:22 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id RAA02237; Mon, 27 Oct 1997 17:24:21 +0100 (MET) Date: Mon, 27 Oct 1997 17:24:21 +0100 (MET) Message-Id: <199710271624.RAA02237@bitbox.follo.net> From: Eivind Eklund To: Poul-Henning Kamp CC: perhaps@yes.no, freebsd-current@FreeBSD.ORG In-reply-to: Poul-Henning Kamp's message of Mon, 27 Oct 1997 07:22:51 +0100 Subject: Re: Directories disappearing? References: <199710270219.DAA00414@bitbox.follo.net> <16181.877933371@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Could you at least give us some details, like what kind of filesystem ??? UFS, mounted noatime. None of the times I lost data it was mounted async - one of them it had been mounted async earlier that session, for the last one I don't think it had (but it might have been; I'm mount -u'ing that filesystem back and forth with/without async fairly often). I know it wasn't async at the time, as that was the first thing I checked each time the dirs disappeared. The two first dirs to disappear were newly created with <10 files/subdirs in each, the last was an old directory I was removing some files in; it had about 20 files in it at the time it disappeared. This has happened for me on two different disks, both mounted from a 2940. Any more details that are of interest? (I though the UFS fact was obvious, but in 20/20 hindsight I see it should be stated explicitly.) Eivind. From owner-freebsd-current Mon Oct 27 08:27:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA00101 for current-outgoing; Mon, 27 Oct 1997 08:27:38 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA29994 for ; Mon, 27 Oct 1997 08:27:31 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA29800; Mon, 27 Oct 1997 16:27:20 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id RAA02255; Mon, 27 Oct 1997 17:27:20 +0100 (MET) Date: Mon, 27 Oct 1997 17:27:20 +0100 (MET) Message-Id: <199710271627.RAA02255@bitbox.follo.net> From: Eivind Eklund To: Chuck Robey CC: perhaps@yes.no, freebsd-current@FreeBSD.ORG In-reply-to: Chuck Robey's message of Sun, 26 Oct 1997 21:38:56 -0500 (EST) Subject: Re: Directories disappearing? References: <199710270219.DAA00414@bitbox.follo.net> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 27 Oct 1997, Eivind Eklund wrote: > > > > > Starting approx a week ago, directories have started to disappear from > > my -current system. It only seem to affect directories in which files > > are added/removed (both operations have had directories disappearing > > under my feet). > > > > Anybody else that are having the same problem? Any suspect changes? > > I've not had enough disk activity for the files in the directories to > > go away through proper unlinks - I've had a a directory with 3000 > > files disappear with nary a sound from the disk. > > > > fsck is not reporting any problems with the disk this has happened on. > > Tell more. Are you running SMP? Have you looked into your archive, are > the files really gone, or unhooked from cvs? Most of them weren't CVS-related. I'm not running SMP; single processor PPro 200 with 64 MB RAM, 3 SCSI-disks on an Adaptec 2940. 128MB swap (yes, too little - old system). This was on an UFS with noatime, but NOT async. See my mail to PHK for other details of exactly what kind of directories that disappeared. Eivind. From owner-freebsd-current Mon Oct 27 09:46:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA09014 for current-outgoing; Mon, 27 Oct 1997 09:46:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08991 for ; Mon, 27 Oct 1997 09:46:11 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id KAA14512 for ; Mon, 27 Oct 1997 10:46:10 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA00725; Mon, 27 Oct 1997 10:46:08 -0700 (MST) Date: Mon, 27 Oct 1997 10:46:08 -0700 (MST) Message-Id: <199710271746.KAA00725@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: Weird kernel message X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk pmap_collect: collecting pv entries -- increase PMAP_SHPGPERPROC This is on a stock kernel with little use (my laptop), so it seems silly that I would have to bump up the defaults. Nate From owner-freebsd-current Mon Oct 27 10:02:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10554 for current-outgoing; Mon, 27 Oct 1997 10:02:48 -0800 (PST) (envelope-from owner-freebsd-current) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA10533 for ; Mon, 27 Oct 1997 10:02:31 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 6321 invoked by uid 1001); 27 Oct 1997 18:02:25 +0000 (GMT) To: perhaps@yes.no Cc: freebsd-current@FreeBSD.ORG Subject: Re: Directories disappearing? In-Reply-To: Your message of "Mon, 27 Oct 1997 17:24:21 +0100 (MET)" References: <199710271624.RAA02237@bitbox.follo.net> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 27 Oct 1997 19:02:25 +0100 Message-ID: <6319.877975345@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > None of the times I lost data it was mounted async - one of them it > had been mounted async earlier that session, for the last one I don't > think it had (but it might have been; I'm mount -u'ing that filesystem > back and forth with/without async fairly often). This may or may not be of relevance... For a while during the 2.2-x-SNAP period I tried to run with a readonly /usr, and change it to read/write with mount -u when I needed to update it. I often ended up with a corrupted file system, and sometimes with a panic. Fortunately, fsck was able to fix the problems. (I quit trying to use a readonly /usr because of these problems.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Mon Oct 27 10:12:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11402 for current-outgoing; Mon, 27 Oct 1997 10:12:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA11387 for ; Mon, 27 Oct 1997 10:12:52 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id TAA01330; Mon, 27 Oct 1997 19:11:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Eivind Eklund cc: freebsd-current@FreeBSD.ORG Subject: Re: Directories disappearing? In-reply-to: Your message of "Mon, 27 Oct 1997 17:24:21 +0100." <199710271624.RAA02237@bitbox.follo.net> Date: Mon, 27 Oct 1997 19:11:49 +0100 Message-ID: <1328.877975909@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710271624.RAA02237@bitbox.follo.net>, Eivind Eklund writes: > >This has happened for me on two different disks, both mounted from a >2940. > >Any more details that are of interest? (I though the UFS fact was >obvious, but in 20/20 hindsight I see it should be stated explicitly.) Anything you can think of. It would be great if we could find a way to reproduce this... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Mon Oct 27 10:42:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13404 for current-outgoing; Mon, 27 Oct 1997 10:42:02 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13397 for ; Mon, 27 Oct 1997 10:41:59 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA14972; Mon, 27 Oct 1997 11:41:35 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA01233; Mon, 27 Oct 1997 11:41:31 -0700 (MST) Date: Mon, 27 Oct 1997 11:41:31 -0700 (MST) Message-Id: <199710271841.LAA01233@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= Cc: Mark Murray , Nate Williams , current@freebsd.org Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) In-Reply-To: References: <199710271827.UAA29423@greenpeace.grondar.za> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Moved to -current from cvs-committers ] " fingerd uses up all the resources that Apache needs " > It seems inetd must be fixed somehow to stop using nobody limits. Maybe, but I think you hit the nail on the head below. > I am not sure, how to fix inetd at this time, maybe we need to handle > nobody name specially (and use daemon limits in this case), or maybe > just use daemon limits for _all_ entries in inetd.conf... > Any ideas? I think that every new process spawned from inetd should have it's own 'private' nobody limits, and not 'share' a set of limits for every process spawned from inetd. Nate From owner-freebsd-current Mon Oct 27 10:54:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14507 for current-outgoing; Mon, 27 Oct 1997 10:54:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14480 for ; Mon, 27 Oct 1997 10:53:51 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id VAA01222; Mon, 27 Oct 1997 21:53:24 +0300 (MSK) (envelope-from ache) Date: Mon, 27 Oct 1997 21:53:21 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Nate Williams cc: Mark Murray , current@freebsd.org Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) In-Reply-To: <199710271841.LAA01233@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, Nate Williams wrote: > [ Moved to -current from cvs-committers ] > > " fingerd uses up all the resources that Apache needs " No. Inetd assumes that nobody have some particular limits (which is against Mark nobody definition) and run fingerd with this limits. > > I am not sure, how to fix inetd at this time, maybe we need to handle > > nobody name specially (and use daemon limits in this case), or maybe > > just use daemon limits for _all_ entries in inetd.conf... > > Any ideas? > > I think that every new process spawned from inetd should have it's own > 'private' nobody limits, and not 'share' a set of limits for every > process spawned from inetd. Please explain, I not understand well what you say. Some time ago inetd runs all process with the limits it was started by rc, i.e. daemon class limits. Recently it was changed to take user field from inetd.conf and set this user limits (which is wrong for nobody case since we can't suppose some particular limits there). Right now I think checking for nobody name and set default daemon limits will be enough solution. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Mon Oct 27 11:06:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15417 for current-outgoing; Mon, 27 Oct 1997 11:06:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15406 for ; Mon, 27 Oct 1997 11:06:47 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (AFfCJXS2ZpmNMUXJGbrSAJ44a+F6BvJE@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id VAA17793; Mon, 27 Oct 1997 21:06:22 +0200 (SAT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (YHzXb+QojYpdeSGQKJHGo1HlXRgkheZu@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id VAA29746; Mon, 27 Oct 1997 21:06:01 +0200 (SAST) Message-Id: <199710271906.VAA29746@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: Nate Williams , Mark Murray , current@freebsd.org Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Oct 1997 21:06:00 +0200 From: Mark Murray Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= wrote: > > I think that every new process spawned from inetd should have it's own > > 'private' nobody limits, and not 'share' a set of limits for every > > process spawned from inetd. > > Please explain, I not understand well what you say. I think what Nate means is this: There should be some way of telling inetd that it should start each process as the nominated user-class, so there must be an extra filed in inet.conf (?) to specify this. I like this idea, but suggest it be optional for backwards compatability. Suggestion: make the syntax for "user" [/[/]], instead of the current . and are allowed to be blank, and default appropriately. > Some time ago inetd runs all process with the limits it was started by rc, > i.e. daemon class limits. Recently it was changed to take user field from > inetd.conf and set this user limits (which is wrong for nobody case since > we can't suppose some particular limits there). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Nate's solution fixes this. > Right now I think checking for nobody name and set default daemon limits > will be enough solution. ...as a patch in Apache? As a workaround, I suppose. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Mon Oct 27 12:04:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19566 for current-outgoing; Mon, 27 Oct 1997 12:04:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19533 for ; Mon, 27 Oct 1997 12:04:10 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id XAA01715; Mon, 27 Oct 1997 23:03:51 +0300 (MSK) (envelope-from ache) Date: Mon, 27 Oct 1997 23:03:49 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Mark Murray cc: Nate Williams , current@freebsd.org Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) In-Reply-To: <199710271906.VAA29746@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, Mark Murray wrote: > Suggestion: make the syntax for "user" [/[/]], > instead of the current . and are allowed to > be blank, and default appropriately. Well, group is not really needed, traditional behaviour is always set passwd group and nobody claims he need to change that. For a while I plan to implement [/] syntax soon and then back out master.passwd patch. If loginclass was ommited, it will be defaulted to daemon as supposed. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Mon Oct 27 12:10:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA20381 for current-outgoing; Mon, 27 Oct 1997 12:10:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA20369 for ; Mon, 27 Oct 1997 12:10:35 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (WcysVCt6yx6hcigpEWfNbCI4qayCJcqz@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id WAA17898; Mon, 27 Oct 1997 22:10:03 +0200 (SAT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (3wfnLTk/JB17BrvquX8A8g371QeY42Yf@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id WAA21958; Mon, 27 Oct 1997 22:09:33 +0200 (SAST) Message-Id: <199710272009.WAA21958@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: Mark Murray , Nate Williams , current@freebsd.org Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Oct 1997 22:09:32 +0200 From: Mark Murray Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= wrote: > Well, group is not really needed, traditional behaviour is always set > passwd group and nobody claims he need to change that. (I assume you meant user's group.) True. I put it in for orthogonality. I won't get passionate about it. > For a while I plan to implement [/] syntax soon > and then back out master.passwd patch. If loginclass was ommited, it will > be defaulted to daemon as supposed. Cool! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Mon Oct 27 13:00:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA25974 for current-outgoing; Mon, 27 Oct 1997 13:00:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pobox1.oit.umass.edu (mailhub.oit.umass.edu [128.119.166.151]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA25877 for ; Mon, 27 Oct 1997 12:59:56 -0800 (PST) (envelope-from gpavelcak@philos.umass.edu) Received: from lessing.oit.umass.edu by pobox1.oit.umass.edu (PMDF V5.1-10 #20973) with ESMTP id <0EIQ00CFYA6ZQZ@pobox1.oit.umass.edu> for freebsd-current@freebsd.org; Mon, 27 Oct 1997 15:56:59 -0500 (EST) Received: (from gp@localhost) by lessing.oit.umass.edu (8.8.3/8.8.6) id PAA28510; Mon, 27 Oct 1997 15:56:57 -0500 (EST) Date: Mon, 27 Oct 1997 15:56:57 -0500 (EST) From: Gregory Pavelcak Subject: Re: After make world: "file system mount failed" In-reply-to: To: dwhite@resnet.uoregon.edu Cc: freebsd-current@freebsd.org Message-id: <199710272056.PAA28510@lessing.oit.umass.edu> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL25] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 27 Oct 1997, Greg Pavelcak wrote: > > > mount: exec mount_ not found in /sbin, /usr/sbin: No such file or > > directory > > Filesystem mount failed, startup aborted > > This implies that an entry in /etc/fstab neglected to specify an FS type. > # cat /etc/fstab /dev/wd0s1b none swap sw 0 0 /dev/wd0a / ufs rw 1 1 /dev/wd0s1f /usr ufs rw 1 1 /dev/wd0s1e /var ufs rw 1 1 proc /proc procfs rw 0 0 > > # mount -u / > > mount: exec mount_ not found in /sbin, /usr/sbin: No such file or > > directory > > > > # mount -a -t ufs > > mount: ufs filesystem is not available (this 3 times) > > > > Does the stuff in "share" have anything to do with this problem. SInce > > the build quit there the first time, I did "make -DNOSHARE world" but > > forgot to go into /usr/src/share and try to make that stuff. > > No, the necessary binaries (mount_*) are in /sbin, which should be built > normally. Do they actually exist? > > This is what I have: > > gdi,ttyp1,/sbin,17>ls -l mount_* > -r-xr-xr-x 1 bin bin 49152 Oct 20 09:35 mount_cd9660* > -r-xr-xr-x 5 bin bin 49152 Oct 20 09:35 mount_devfs* > -r-xr-xr-x 1 bin bin 49152 Oct 20 09:35 mount_ext2fs* > -r-xr-xr-x 5 bin bin 49152 Oct 20 09:35 mount_fdesc* > -r-xr-xr-x 5 bin bin 49152 Oct 20 09:35 mount_kernfs* > -r-xr-xr-x 1 bin bin 49152 Oct 20 09:35 mount_lfs* > -r-xr-xr-x 2 bin bin 122880 Oct 20 09:35 mount_mfs* > -r-sr-xr-x 1 root bin 139264 Oct 20 09:35 mount_msdos* > -r-xr-xr-x 1 bin bin 122880 Oct 20 09:35 mount_nfs* > -r-xr-xr-x 1 bin bin 53248 Oct 20 09:35 mount_null* > -r-xr-xr-x 1 bin bin 204800 Oct 20 09:35 mount_portal* > -r-xr-xr-x 5 bin bin 49152 Oct 20 09:35 mount_procfs* > -r-xr-xr-x 5 bin bin 49152 Oct 20 09:35 mount_std* > -r-xr-xr-x 1 bin bin 61440 Oct 20 09:35 mount_umap* > -r-xr-xr-x 1 bin bin 53248 Oct 20 09:35 mount_union* Same here. Well some different sizes, but they're all present. > > If you are following -current you should be subscribed to, and ask > questions in, the freebsd-current mailing list. I am. OK. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > Thanks. Greg From owner-freebsd-current Mon Oct 27 14:59:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA03416 for current-outgoing; Mon, 27 Oct 1997 14:59:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA03411 for ; Mon, 27 Oct 1997 14:59:42 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.5) with SMTP id OAA13467; Mon, 27 Oct 1997 14:59:25 -0800 (PST) Date: Mon, 27 Oct 1997 14:59:25 -0800 (PST) From: Doug White Reply-To: Doug White To: Gregory Pavelcak cc: freebsd-current@freebsd.org Subject: Re: After make world: "file system mount failed" In-Reply-To: <199710272056.PAA28510@lessing.oit.umass.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, Gregory Pavelcak wrote: > > > mount: exec mount_ not found in /sbin, /usr/sbin: No such file or > > > directory > > > > This implies that an entry in /etc/fstab neglected to specify an FS type. > > > # cat /etc/fstab Guess not. > > This is what I have: > > > > gdi,ttyp1,/sbin,17>ls -l mount_* > > Same here. Well some different sizes, but they're all present. Hm. It looks like mount already understands how to mount ufs volumes without any special help. I know that the mount() interface changed from 2.x to 3.0-CURRENT; did you update your mount* programs appropriately? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Mon Oct 27 15:18:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA04812 for current-outgoing; Mon, 27 Oct 1997 15:18:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA04782 for ; Mon, 27 Oct 1997 15:17:52 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id JAA14748; Tue, 28 Oct 1997 09:47:32 +1030 (CST) Message-ID: <19971028094732.57881@lemis.com> Date: Tue, 28 Oct 1997 09:47:32 +1030 From: Greg Lehey To: Evan Champion Cc: freebsd-current@FreeBSD.ORG Subject: Re: 971026 wouldn't let me set timezone References: <01bce2de$aa206c80$513654c7@cello.synapse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <01bce2de$aa206c80$513654c7@cello.synapse.net>; from Evan Champion on Mon, Oct 27, 1997 at 08:46:02AM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Oct 27, 1997 at 08:46:02AM -0500, Evan Champion wrote: > Just a note that 3.0-current-971026's sysinstall won't let me set the > timezone. It seems that the timezone option is just a no-op. I don't understand. What do you mean by "setting the timezone"? Assuming that you're on the US East Coast, you would do something like: # cp /usr/share/zoneinfo/America/New_York /etc/localtime Are you saying this failed? > It also failed installing one of the XFree card-specific servers (sorry, I > don't remember which one). Well, you can't really expect anybody to help you then, can you? Greg From owner-freebsd-current Mon Oct 27 15:40:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA06227 for current-outgoing; Mon, 27 Oct 1997 15:40:36 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA06221 for ; Mon, 27 Oct 1997 15:40:31 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 8326 invoked from network); 27 Oct 1997 23:40:28 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 27 Oct 1997 23:40:28 -0000 From: "Evan Champion" To: "Greg Lehey" Cc: Subject: Re: 971026 wouldn't let me set timezone Date: Mon, 27 Oct 1997 18:40:27 -0500 Message-ID: <01bce331$b4366e60$513654c7@cello.synapse.net> 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.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I don't understand. What do you mean by "setting the timezone"? >Assuming that you're on the US East Coast, you would do something >like: As I wrote in the original message, I'm saying that sysinstall won't let me do it. The timezone-setting option in sysinstall seems to be a no-op; you click on it, and absolutely nothing happens. It's supposed to bring up that menu that lets me pick what country etc. I'm in, and nothing at all happens. >> It also failed installing one of the XFree card-specific servers (sorry, I >> don't remember which one). > >Well, you can't really expect anybody to help you then, can you? Maybe I won't report it next time and then it really won't help anyone. After spending 5 hours trying to load FreeBSD the last thing I thought of was "gee, maybe I should write that one down." If I'm lucky, -current will eat itself, and I can enjoy another 5 hours of downloading, and maybe I will write it down next time. The file exists but it fails gunzip'ing after a couple hundred K, so all that should be required is for someone to go to the XFree86 dist and gzip -t everything (which probably isn't such a bad idea in general as the XFree distribution doesn't get updated very often). I tried reloading the file 3 times so I'm sure it's not a figment of my computer's imagination... Evan From owner-freebsd-current Mon Oct 27 15:45:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA06538 for current-outgoing; Mon, 27 Oct 1997 15:45:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA06497 for ; Mon, 27 Oct 1997 15:44:59 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA14860; Tue, 28 Oct 1997 10:14:46 +1030 (CST) Message-ID: <19971028101446.08677@lemis.com> Date: Tue, 28 Oct 1997 10:14:46 +1030 From: Greg Lehey To: Evan Champion Cc: freebsd-current@FreeBSD.ORG Subject: Re: 971026 wouldn't let me set timezone References: <01bce331$b4366e60$513654c7@cello.synapse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <01bce331$b4366e60$513654c7@cello.synapse.net>; from Evan Champion on Mon, Oct 27, 1997 at 06:40:27PM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Oct 27, 1997 at 06:40:27PM -0500, Evan Champion wrote: >> I don't understand. What do you mean by "setting the timezone"? >> Assuming that you're on the US East Coast, you would do something >> like: > > > As I wrote in the original message, I'm saying that sysinstall won't let me > do it. The timezone-setting option in sysinstall seems to be a no-op; you > click on it, and absolutely nothing happens. It's supposed to bring up that > menu that lets me pick what country etc. I'm in, and nothing at all happens. Ah, now I understand. I haven't kept the original message, but I can't recall seeing a mention of sysinstall. If I missed that, my apologies. >>> It also failed installing one of the XFree card-specific servers (sorry, > I >>> don't remember which one). >> >> Well, you can't really expect anybody to help you then, can you? > > > Maybe I won't report it next time and then it really won't help anyone. > > After spending 5 hours trying to load FreeBSD the last thing I thought of > was "gee, maybe I should write that one down." If I'm lucky, -current will > eat itself, and I can enjoy another 5 hours of downloading, and maybe I will > write it down next time. Sure, I can understand that you get a bit frustrated after lots of messing around. It happens to all of us. But seriously, what do you expect anybody to be able to do with a statement like the one above? > The file exists but it fails gunzip'ing after a couple hundred K, so all > that should be required is for someone to go to the XFree86 dist and gzip -t > everything (which probably isn't such a bad idea in general as the XFree > distribution doesn't get updated very often). I tried reloading the file 3 > times so I'm sure it's not a figment of my computer's imagination... Yes, but it could be on your CD-ROM. You could have done the gzip -t yourself. BTW, your mailer mauls text. Note the >>> quotes above? This is a "feature" of many Microsoft mailers. I've been told you can turn it off, but I don't know how. Greg From owner-freebsd-current Mon Oct 27 15:59:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA07547 for current-outgoing; Mon, 27 Oct 1997 15:59:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA07536 for ; Mon, 27 Oct 1997 15:59:22 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 9998 invoked from network); 27 Oct 1997 23:58:50 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 27 Oct 1997 23:58:50 -0000 From: "Evan Champion" To: "Greg Lehey" Cc: Subject: Re: 971026 wouldn't let me set timezone Date: Mon, 27 Oct 1997 18:58:49 -0500 Message-ID: <01bce334$4512dd40$513654c7@cello.synapse.net> 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.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Yes, but it could be on your CD-ROM. You could have done the gzip -t >yourself. I was loading off current.freebsd.org. Unless I missed something, 3.0-current-971026 isn't on CDROM yet... I would also hope it wouldn't take 5 hours to load off a CD-ROM :-) >BTW, your mailer mauls text. Note the >>> quotes above? This is a >"feature" of many Microsoft mailers. I've been told you can turn it >off, but I don't know how. There are a lot of "features" in Outlook Express, most of which I have no idea how to get around. The thing is a piece of junk, but it's less of a piece of junk than my alternatives. Evan From owner-freebsd-current Mon Oct 27 17:27:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA13238 for current-outgoing; Mon, 27 Oct 1997 17:27:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA13228 for ; Mon, 27 Oct 1997 17:27:48 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id UAA05529; Mon, 27 Oct 1997 20:27:40 -0500 (EST) From: "John S. Dyson" Message-Id: <199710280127.UAA05529@dyson.iquest.net> Subject: Re: Weird kernel message In-Reply-To: <199710271746.KAA00725@rocky.mt.sri.com> from Nate Williams at "Oct 27, 97 10:46:08 am" To: nate@mt.sri.com (Nate Williams) Date: Mon, 27 Oct 1997 20:27:40 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams said: > pmap_collect: collecting pv entries -- increase PMAP_SHPGPERPROC > > This is on a stock kernel with little use (my laptop), so it seems silly > that I would have to bump up the defaults. > I hopefully have fixed this message in -current. The message should come out only on a system where there are lots of pages being shared by lots of processes. I think that the message was being triggered before appropriate initialization. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Mon Oct 27 17:49:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14612 for current-outgoing; Mon, 27 Oct 1997 17:49:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14605 for ; Mon, 27 Oct 1997 17:49:08 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id SAA17816; Mon, 27 Oct 1997 18:49:05 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id SAA03643; Mon, 27 Oct 1997 18:49:02 -0700 (MST) Date: Mon, 27 Oct 1997 18:49:02 -0700 (MST) Message-Id: <199710280149.SAA03643@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "John S. Dyson" Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Weird kernel message In-Reply-To: <199710280127.UAA05529@dyson.iquest.net> References: <199710271746.KAA00725@rocky.mt.sri.com> <199710280127.UAA05529@dyson.iquest.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > pmap_collect: collecting pv entries -- increase PMAP_SHPGPERPROC > > > > This is on a stock kernel with little use (my laptop), so it seems silly > > that I would have to bump up the defaults. > > > I hopefully have fixed this message in -current. The message should come > out only on a system where there are lots of pages being shared by lots > of processes. I think that the message was being triggered before appropriate > initialization. OK, I updated the code and will make/install a new kernel. If you don't hear anything from me assume it works, otherwise I'll email again. :) Nate From owner-freebsd-current Mon Oct 27 18:47:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA18039 for current-outgoing; Mon, 27 Oct 1997 18:47:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA18034 for ; Mon, 27 Oct 1997 18:47:27 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.7/8.8.5) with SMTP id VAA14524 for ; Mon, 27 Oct 1997 21:44:57 -0500 (EST) Date: Mon, 27 Oct 1997 21:44:57 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: current@freebsd.org Subject: ftp install-current snapshot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've never posted here before, so don't shoot me if this is a stupid question... I went through the archives, but did not find anything relevant, so here it goes: I'm trying to install a -current snapshot (tried both 10/24 and 10/22) on a test box, and all goes well until starting the ftp install. I choose current.freebsd.org, and after about 20 seconds I get a message stating that it could not log in as the connection was in "the wrong state". Logging into ftp.freebsd.org worked, except the snap I wanted wasn't there. If this is a known problem with sysinstall, could someone refer me to an earlier snap from which I could work? Thanks much, Charles From owner-freebsd-current Mon Oct 27 20:14:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA23104 for current-outgoing; Mon, 27 Oct 1997 20:14:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.5.84]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA23098 for ; Mon, 27 Oct 1997 20:14:24 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.7/8.8.7) id VAA15299; Mon, 27 Oct 1997 21:14:24 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd015297; Mon Oct 27 21:14:21 1997 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id VAA06316; Mon, 27 Oct 1997 21:14:17 -0700 (MST) From: Terry Lambert Message-Id: <199710280414.VAA06316@usr08.primenet.com> Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) To: mark@grondar.za (Mark Murray) Date: Tue, 28 Oct 1997 04:14:17 +0000 (GMT) Cc: ache@nagual.pp.ru, nate@mt.sri.com, mark@grondar.za, current@FreeBSD.ORG In-Reply-To: <199710271906.VAA29746@greenpeace.grondar.za> from "Mark Murray" at Oct 27, 97 09:06:00 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Suggestion: make the syntax for "user" [/[/]], > instead of the current . and are allowed to > be blank, and default appropriately. I like this. I think the seperator should be ".", as in "chown user.group". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Oct 27 20:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA23265 for current-outgoing; Mon, 27 Oct 1997 20:16:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA23255 for ; Mon, 27 Oct 1997 20:16:37 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id VAA21894; Mon, 27 Oct 1997 21:16:36 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd021887; Mon Oct 27 21:16:30 1997 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id VAA06387; Mon, 27 Oct 1997 21:16:28 -0700 (MST) From: Terry Lambert Message-Id: <199710280416.VAA06387@usr08.primenet.com> Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) To: mark@grondar.za (Mark Murray) Date: Tue, 28 Oct 1997 04:16:28 +0000 (GMT) Cc: ache@nagual.pp.ru, mark@grondar.za, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <199710272009.WAA21958@greenpeace.grondar.za> from "Mark Murray" at Oct 27, 97 10:09:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Well, group is not really needed, traditional behaviour is always set > > passwd group and nobody claims he need to change that. > > (I assume you meant user's group.) True. I put it in for orthogonality. > I won't get passionate about it. I like group. Mostly because "daemon.mail.daemon" has a nice ring to it to get rid of SGID on MTA's. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Oct 27 20:36:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24527 for current-outgoing; Mon, 27 Oct 1997 20:36:00 -0800 (PST) (envelope-from owner-freebsd-current) Received: from tower.my.domain (nscs22p12.remote.umass.edu [128.119.179.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA24507 for ; Mon, 27 Oct 1997 20:35:49 -0800 (PST) (envelope-from gp@tower.my.domain) Received: (from root@localhost) by tower.my.domain (8.8.7/8.8.7) id SAA20256; Mon, 27 Oct 1997 18:31:13 -0500 (EST) (envelope-from gp) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 27 Oct 1997 18:24:56 -0500 (EST) From: Greg Pavelcak To: Doug White Subject: Re: After make world: "file system mount failed" Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 27-Oct-97 Doug White wrote: >On Mon, 27 Oct 1997, Gregory Pavelcak wrote: > >> > > mount: exec mount_ not found in /sbin, /usr/sbin: No such file >or >> > > directory >> > >> > This implies that an entry in /etc/fstab neglected to specify an >FS type. >> > >> # cat /etc/fstab > >Guess not. > >> > This is what I have: >> > >> > gdi,ttyp1,/sbin,17>ls -l mount_* >> >> Same here. Well some different sizes, but they're all present. > >Hm. It looks like mount already understands how to mount ufs volumes >without any special help. I know that the mount() interface changed >from >2.x to 3.0-CURRENT; did you update your mount* programs appropriately? > Depends on what would constitute doing that. I didn't have anything customized on this machine, so I just did make world, make distribution. I started by rebuilding config, but it looks like I forgot to make a new kernel before I built the world. Boot-up reports a 2.2.2-RELEASE kernel. Perhaps that's my problem? If so, is there any way to get a -current kernel over there. As I said, I am running the same sources on another machine. I thought about making a release on it; I have just enough space, but that failed with libalias_p.a not found. I really don't know what I'm doing there though. I need to read some docs. Anyway, any more ideas would be greatly appreciated. It apparently took almost 24 hrs for this make world with the p100 but only 8MB RAM. I'd rather not have to start from scratch. Thanks again. Greg >Doug White | University of Oregon >Internet: dwhite@resnet.uoregon.edu | Residence Networking >Assistant >http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Mon Oct 27 20:37:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24693 for current-outgoing; Mon, 27 Oct 1997 20:37:00 -0800 (PST) (envelope-from owner-freebsd-current) Received: from tower.my.domain (nscs22p12.remote.umass.edu [128.119.179.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA24673 for ; Mon, 27 Oct 1997 20:36:52 -0800 (PST) (envelope-from gp@tower.my.domain) Received: (from root@localhost) by tower.my.domain (8.8.7/8.8.7) id XAA00442; Mon, 27 Oct 1997 23:35:02 -0500 (EST) (envelope-from gp) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 27 Oct 1997 23:34:57 -0500 (EST) From: Greg Pavelcak To: Greg Pavelcak Subject: Re: After make world: "file system mount failed" Cc: freebsd-current@freebsd.org, Doug White Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 27-Oct-97 Greg Pavelcak wrote: > >On 27-Oct-97 Doug White wrote: >>On Mon, 27 Oct 1997, Gregory Pavelcak wrote: >> >>> > > mount: exec mount_ not found in /sbin, /usr/sbin: No such file >>or >>> > > directory >>> > >>> > This implies that an entry in /etc/fstab neglected to specify an >>FS type. >>> > >>> # cat /etc/fstab >> >>Guess not. >> >>> > This is what I have: >>> > >>> > gdi,ttyp1,/sbin,17>ls -l mount_* >>> >>> Same here. Well some different sizes, but they're all present. >> >>Hm. It looks like mount already understands how to mount ufs volumes >>without any special help. I know that the mount() interface changed >>from >>2.x to 3.0-CURRENT; did you update your mount* programs >appropriately? >> >Depends on what would constitute doing that. I didn't have anything >customized on this machine, so I just did make world, make >distribution. I started by rebuilding config, but it looks like I >forgot to make a new kernel before I built the world. Boot-up reports >a >2.2.2-RELEASE kernel. Perhaps that's my problem? If so, is there any >way to get a -current kernel over there. As I said, I am running the >same sources on another machine. I thought about making a release on >it; I have just enough space, but that failed with libalias_p.a not >found. I really don't know what I'm doing there though. I need to read >some docs. > >Anyway, any more ideas would be greatly appreciated. It apparently >took >almost 24 hrs for this make world with the p100 but only 8MB RAM. I'd >rather not have to start from scratch. > >Thanks again. > >Greg > > > >>Doug White | University of Oregon >>Internet: dwhite@resnet.uoregon.edu | Residence Networking >>Assistant >>http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Mon Oct 27 20:50:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA25585 for current-outgoing; Mon, 27 Oct 1997 20:50:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA25577 for ; Mon, 27 Oct 1997 20:50:30 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id UAA03372; Mon, 27 Oct 1997 20:50:18 -0800 (PST) Message-ID: <19971027205018.44557@hydrogen.nike.efn.org> Date: Mon, 27 Oct 1997 20:50:18 -0800 From: John-Mark Gurney To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) References: <199710271906.VAA29746@greenpeace.grondar.za> <199710280414.VAA06316@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199710280414.VAA06316@usr08.primenet.com>; from Terry Lambert on Tue, Oct 28, 1997 at 04:14:17AM +0000 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert scribbled this message on Oct 28: > > Suggestion: make the syntax for "user" [/[/]], > > instead of the current . and are allowed to > > be blank, and default appropriately. > > I like this. > > I think the seperator should be ".", as in "chown user.group". well.. we should be keeping with the times and use `:'... on Solaris you can't use `.' as a seperator (it's REALLY anoying)... from the chown manpage: COMPATIBILITY Previous versions of the chown utility used the dot (``.'') character to distinguish the group name. This has been changed to be a colon (``:'') character so that user and group names may contain the dot character. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Mon Oct 27 21:56:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA28973 for current-outgoing; Mon, 27 Oct 1997 21:56:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA28966 for ; Mon, 27 Oct 1997 21:56:46 -0800 (PST) (envelope-from marcs@znep.com) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.7/8.8.7) with UUCP id WAA11308; Mon, 27 Oct 1997 22:56:36 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id XAA13452; Mon, 27 Oct 1997 23:01:33 -0700 (MST) Date: Mon, 27 Oct 1997 23:01:32 -0700 (MST) From: Marc Slemko To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) In-Reply-To: <199710280414.VAA06316@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 Oct 1997, Terry Lambert wrote: > > Suggestion: make the syntax for "user" [/[/]], > > instead of the current . and are allowed to > > be blank, and default appropriately. > > I like this. > > I think the seperator should be ".", as in "chown user.group". What, we just get rid of using '.' as the preferred seperator for chown in favour of ':' and now you want to bring back '.' for something else? From owner-freebsd-current Mon Oct 27 23:21:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02850 for current-outgoing; Mon, 27 Oct 1997 23:21:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA02845 for ; Mon, 27 Oct 1997 23:21:06 -0800 (PST) (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.8.7/RBI-Z14) with ESMTP id IAA00167 for ; Tue, 28 Oct 1997 08:20:58 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id IAA07601 for freebsd-current@freefall.cdrom.com; Tue, 28 Oct 1997 08:33:36 +0100 (MET) Date: Tue, 28 Oct 1997 08:33:36 +0100 (MET) From: Christoph Kukulies Message-Id: <199710280733.IAA07601@gil.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: de0 driver messages Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Since switching a 2.2.2-system to -current I'm seeing these : Oct 27 09:19:58 blues /kernel: de0: receive: 00:80:12:34:56:78: bad crc Oct 27 09:54:40 blues /kernel: de0: receive: 00:80:12:34:56:78: bad crc Oct 27 10:17:11 blues /kernel: de0: receive: 00:80:12:34:56:78: alignment error Oct 27 10:39:41 blues /kernel: de0: receive: 00:80:12:34:56:78: alignment error Oct 27 10:59:12 blues /kernel: de0: receive: 00:80:12:34:56:78: alignment error Oct 27 13:29:08 blues /kernel: de0: receive: 00:80:12:34:56:78: bad crc I saw some discussion about de0 pass by. Is there some new code I can test? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Oct 27 23:23:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02996 for current-outgoing; Mon, 27 Oct 1997 23:23:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA02991 for ; Mon, 27 Oct 1997 23:23:39 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.5) with SMTP id XAA14125; Mon, 27 Oct 1997 23:23:29 -0800 (PST) Date: Mon, 27 Oct 1997 23:23:29 -0800 (PST) From: Doug White Reply-To: Doug White To: Greg Pavelcak cc: freebsd-current@FreeBSD.ORG Subject: Re: After make world: "file system mount failed" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, Greg Pavelcak wrote: > >Hm. It looks like mount already understands how to mount ufs volumes > >without any special help. I know that the mount() interface changed > >from > >2.x to 3.0-CURRENT; did you update your mount* programs appropriately? > > > Depends on what would constitute doing that. I didn't have anything > customized on this machine, so I just did make world, make > distribution. I started by rebuilding config, but it looks like I > forgot to make a new kernel before I built the world. Boot-up reports a > 2.2.2-RELEASE kernel. Perhaps that's my problem? If so, is there any > way to get a -current kernel over there. Doooh! I just remembered that -- make world doesn't build a kernel! Make up a 2.2.2 install/fixit floppy set and use the fixit floppy to mount the filesystems, then build & install a new kernel. The fixit floppy will have appropriate copies of mount present so that should work. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Mon Oct 27 23:49:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA04955 for current-outgoing; Mon, 27 Oct 1997 23:49:50 -0800 (PST) (envelope-from owner-freebsd-current) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA04942 for ; Mon, 27 Oct 1997 23:49:41 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.7/D) id KAA29334; Tue, 28 Oct 1997 10:49:11 +0300 (MSK) Posted-Date: Tue, 28 Oct 1997 10:49:11 +0300 (MSK) Message-ID: <19971028104910.43916@demos.su> Date: Tue, 28 Oct 1997 10:49:10 +0300 From: "Mikhail A. Sokolov" To: current@freebsd.org Subject: current/nfs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, there are two machines here which missbehave in very odd and different way: One machine runs 19971011-current and 'hangs' pretty regularily, then tries to reboot, tries to sync and there hangs. The machine has pretty hard task to be an nfs server for 5 others with up to 6000 interrupts/second, motherboard is intel PR440FX, 2xppro200, there are enough swap/memory space. Yet another missbehaves even funny: there is a jumper G, which will overlock processors to 233Mhz, which we happily did (970926-SNAP there). When we try to start it with 19971011-current kernel and processors at 200Mhz, it will yell it can't start second CPU, - mp_lock 1000005, abort trap. It will do ok on 233Mhz with 19971011-current, as well as 970926-SNAP. Ideas? -- -mishania From owner-freebsd-current Tue Oct 28 04:41:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20075 for current-outgoing; Tue, 28 Oct 1997 04:41:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mailhost (user-2k7i8bm.dialup.mindspring.com [168.121.33.118]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA20069 for ; Tue, 28 Oct 1997 04:41:39 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0xQAy1-000G5LC; Tue, 28 Oct 97 07:41 EST Message-ID: <3455DD85.7C6DFFBE@mindspring.com> Date: Tue, 28 Oct 1997 07:41:41 -0500 From: Ron Bolin X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: StarOffice on 3.0 current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone had success in the getting Staroffice pakcage to run on 3.0? I installed it and the linux devel/lib packages, but it just hangs. I can run other linux programs Adobie Acrobat, and Wingz, but SO won't. StarOffice "setup" tries to run first, but it hangs after a lot of disk activity. I checked, my LD_LIBRARY_PATH includes the SO libs too. Got any ideas? Thanks Ron -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-6875 Web: http://www.mindspring.com/~rlb ------------------------------------------------------------------------------- From owner-freebsd-current Tue Oct 28 05:10:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21533 for current-outgoing; Tue, 28 Oct 1997 05:10:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from nagual.pp.ru (ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA21479 for ; Tue, 28 Oct 1997 05:09:41 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.8.7/8.8.7) id QAA00762; Tue, 28 Oct 1997 16:08:46 +0300 (MSK) (envelope-from ache) Date: Tue, 28 Oct 1997 16:08:44 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Marc Slemko cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997, Marc Slemko wrote: > What, we just get rid of using '.' as the preferred seperator for chown in > favour of ':' and now you want to bring back '.' for something else? [.group] cause great troubles with login classes to make it very hard to implement and nobody seems need it really, so I not do this part. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Tue Oct 28 05:44:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23490 for current-outgoing; Tue, 28 Oct 1997 05:44:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23484; Tue, 28 Oct 1997 05:44:27 -0800 (PST) (envelope-from p.richards@elsevier.co.uk) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id NAA03714; Tue, 28 Oct 1997 13:43:10 GMT Received: from screavie.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP); Tue, 28 Oct 1997 13:43:32 +0000 Received: from tees.elsevier.co.uk (tees.elsevier.co.uk [193.131.192.70]) by screavie.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id NAA22627; Tue, 28 Oct 1997 13:43:29 GMT Received: (from dpr@localhost) by tees.elsevier.co.uk (8.8.5/8.8.5) id NAA00473; Tue, 28 Oct 1997 13:43:29 GMT To: questions@freebsd.org Cc: current@freebsd.org Subject: Retrieving data from a totally hosed filesystem From: Paul Richards Date: 28 Oct 1997 13:43:28 +0000 Message-ID: <57pvoqypdr.fsf@tees.elsevier.co.uk> Lines: 51 X-Mailer: Gnus v5.4.37/Emacs 19.30 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is Cc'd to current since I think there's a problem with fsck (see below). I totally trashed a partition on my hard disk a week ago ( I was playing with bootblocks and scsi adapter setttings!) and I'd like to try and retrieve data from, not critical but I'm curious how to go about it since it's happened. Somehow I trashed the disklabel on the FreeBSD partition but by using a combination of guesswork and memory I rebuilt one and most of my partitions re-appeared without problem. One however didn't. fsck said the superblock was invalid so, casting caution to the wind I told fsck to use an alternate. Many coredumps of fsck later (I had to delete some inodes using fsdb in order to get fsck to complete stage1) I had a totally unravelled filesystem. fsck then tried to put all these files into lost+found but aborted because it ran out of space in lost+found (which is why I've cc'd this to current). So, now I'm curious about two things 1) fsck claims it will auto-expand lost+found if it needs to. This seems to be very broken since it doesn't. I'm not sure the strategy of building lost+found on the fly is a good one since there was no space on this partition and it doesn't look like fsck is able to to get enough space for the directory information. That might not actually be the problem since the corruption is quite serious but the lost+found directory has been created and fsck does start to place files in it so I'm suspicious that this is the problem (i.e. not able to get find enough space). Either lost+found should be pre-allocated as it used to be or we should find a way of getting fsck to build lost+found somewhere else. I started hacking fsck to try and do this but didn't get very far with it, the basic idea of changing the lost+found directory path didn't seem to work. 2) Has anyone got any bright ideas as to how I can salvage as much of the data from this partition as is possible. Since the actual data is not corrupted (a dd of the partition shows all the data is still untouched) there might be a way to extract the data from the partition and reconstruct a filesystem in another area of the disk. Seems like an interesting challenge to me and I was wondering if anyone had any tools as a starting point. If nothing else, I suspect it should be possible to get the unlinked inodes connected to a directory as fsck should have done in lost+found and at least retrieve the data in those files. -- Dr Paul Richards. IT, Product Application Development. Email: p.richards@elsevier.co.uk Phone: x3155 From owner-freebsd-current Tue Oct 28 08:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA01548 for current-outgoing; Tue, 28 Oct 1997 08:16:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA01541 for ; Tue, 28 Oct 1997 08:16:35 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id JAA23337; Tue, 28 Oct 1997 09:16:04 -0700 (MST) Message-Id: <199710281616.JAA23337@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Mikhail A. Sokolov" cc: current@FreeBSD.ORG Subject: Re: current/nfs In-reply-to: Your message of "Tue, 28 Oct 1997 10:49:10 +0300." <19971028104910.43916@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Oct 1997 09:16:04 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > One machine runs 19971011-current and 'hangs' pretty regularily, then > tries to reboot, tries to sync and there hangs. The machine has pretty hard > task to be an nfs server for 5 others with up to 6000 interrupts/second, > motherboard is intel PR440FX, 2xppro200, there are enough swap/memory space. be more specific, what messages come out when it hangs/reboots? --- > Yet another missbehaves even funny: there is a jumper G, which will overlock > processors to 233Mhz, which we happily did (970926-SNAP there). When we try to > start it with 19971011-current kernel and processors at 200Mhz, it will > yell it can't start second CPU, - mp_lock 1000005, abort trap. It will do ok > on 233Mhz with 19971011-current, as well as 970926-SNAP. this is probably the race fixed by: fsmp 1997/10/12 17:01:56 PDT Modified files: sys/i386/isa ipl.s Revision Changes Path 1.18 +5 -1 src/sys/i386/isa/ipl.s -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Tue Oct 28 08:45:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03041 for current-outgoing; Tue, 28 Oct 1997 08:45:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03036 for ; Tue, 28 Oct 1997 08:45:06 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id RAA00588; Tue, 28 Oct 1997 17:44:57 +0100 (MET) Message-Id: <199710281644.RAA00588@sos.freebsd.dk> Subject: Re: StarOffice on 3.0 current In-Reply-To: <3455DD85.7C6DFFBE@mindspring.com> from Ron Bolin at "Oct 28, 97 07:41:41 am" To: rlb@mindspring.com (Ron Bolin) Date: Tue, 28 Oct 1997 17:44:57 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Ron Bolin who wrote: > Has anyone had success in the getting Staroffice pakcage to run on 3.0? > I installed it and the linux devel/lib packages, but it just hangs. > > I can run other linux programs Adobie Acrobat, and Wingz, but SO won't. > StarOffice "setup" tries to run first, but it hangs after a lot of disk > activity. > I checked, my LD_LIBRARY_PATH includes the SO libs too. > > Got any ideas? You must be doing something wrong, it works just fine here (and has been since day one)... Check your DNS settings for linux as staroffice apparently tries to find the name of the workstation that way.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Tue Oct 28 08:49:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03298 for current-outgoing; Tue, 28 Oct 1997 08:49:36 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.5.84]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03292 for ; Tue, 28 Oct 1997 08:49:32 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.7/8.8.7) id JAA29446; Tue, 28 Oct 1997 09:49:29 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd029418; Tue Oct 28 09:49:19 1997 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id JAA24638; Tue, 28 Oct 1997 09:49:17 -0700 (MST) From: Terry Lambert Message-Id: <199710281649.JAA24638@usr06.primenet.com> Subject: Re: Inetd & login class bug (was Re: cvs commit: src/etc master.passwd) To: marcs@znep.com (Marc Slemko) Date: Tue, 28 Oct 1997 16:49:17 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Marc Slemko" at Oct 27, 97 11:01:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Suggestion: make the syntax for "user" [/[/]], > > > instead of the current . and are allowed to > > > be blank, and default appropriately. > > > > I like this. > > > > I think the seperator should be ".", as in "chown user.group". > > What, we just get rid of using '.' as the preferred seperator for chown in > favour of ':' and now you want to bring back '.' for something else? Did that change actually get in??? I thought a ':' was the AntiChr^H^H^HPOSIX according to some people... OK. Let me correct it: It should be *whatever* chown uses as a seperator. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Oct 28 09:00:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA04026 for current-outgoing; Tue, 28 Oct 1997 09:00:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA04014; Tue, 28 Oct 1997 09:00:50 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.7/8.8.5) id JAA18177; Tue, 28 Oct 1997 09:01:14 -0800 (PST) From: Steve Kargl Message-Id: <199710281701.JAA18177@troutmask.apl.washington.edu> Subject: Re: Retrieving data from a totally hosed filesystem In-Reply-To: <57pvoqypdr.fsf@tees.elsevier.co.uk> from Paul Richards at "Oct 28, 97 01:43:28 pm" To: p.richards@elsevier.co.uk (Paul Richards) Date: Tue, 28 Oct 1997 09:01:14 -0800 (PST) Cc: questions@FreeBSD.ORG, current@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-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Paul Richards: > > This is Cc'd to current since I think there's a problem with fsck (see > below). > > > I totally trashed a partition on my hard disk a week ago ( I was > playing with bootblocks and scsi adapter setttings!) and I'd like to > try and retrieve data from, not critical but I'm curious how to go > about it since it's happened. > [description of fsck and lost+found deleted] I would use the backup tape I made before I started to experiment with the disk subsystems. man dump man restore -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~kargl/sgk.html From owner-freebsd-current Tue Oct 28 09:38:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06331 for current-outgoing; Tue, 28 Oct 1997 09:38:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA06324 for ; Tue, 28 Oct 1997 09:38:17 -0800 (PST) (envelope-from bsampley@bsampley.vip.best.com) Received: from bsampley (bsampley.vip.best.com [206.184.160.196]) by proxy4.ba.best.com (8.8.7/8.8.BEST) with SMTP id JAA13146; Tue, 28 Oct 1997 09:34:35 -0800 (PST) Date: Tue, 28 Oct 1997 09:31:13 -0800 (PST) From: Burton Sampley X-Sender: bsampley@bsampley To: Ron Bolin cc: FreeBSD Current Mailing List Subject: Re: StarOffice on 3.0 current In-Reply-To: <3455DD85.7C6DFFBE@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- I'm running -current (last cvsup'ed & make world on 09/11/97) and Staroffice (built from 'ports'). It depends on how it was installed the frist time you tried to run it. When I did the 'local' install to a user's $HOME dir, it puked. I then un-installed and chose the install option that installs only a 'stub' in the local dir and everything else in something like /usr/local/*?*. It runs, but I'm getting some strange graphics. Some of the icons appear as a black square with a grey border. When I move the pointer over the icon a dialog box pops up with what the icon does (and it actually functions as expected). When I open a new file some of these icons change to the appropriate icon. It all seems to work, so I didn't waste too much time worrying about it. On Tue, 28 Oct 1997, Ron Bolin wrote: > Has anyone had success in the getting Staroffice pakcage to run on 3.0? > I installed it and the linux devel/lib packages, but it just hangs. > > I can run other linux programs Adobie Acrobat, and Wingz, but SO won't. > StarOffice "setup" tries to run first, but it hangs after a lot of disk > activity. > I checked, my LD_LIBRARY_PATH includes the SO libs too. > > Got any ideas? > > > Thanks > > Ron > > -- > ------------------------------------------------------------------------------- > Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net > E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb > Ph: 770-729-2929 Ext 249 Hm: 770-992-6875 Web: http://www.mindspring.com/~rlb > ------------------------------------------------------------------------------- > > > > - --------------- Burton Sampley bsampley@best.com or bsampley@haywire.csuhayward.edu PGP key available at http://www.best.com/~bsampley/pgp.html -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNFYhaHt2O8KJtMdBAQFMkgP/afmca8/y/7umZI7vJPZpdB6syiTvgE+z hPIEPMuUmivcJ/9DcdD6PeudPP2rENCxsZC2RwTTucW2h5itQMxsPwFlL+7yhIoB Y0vVHHhVTyg6e/u8YT5X+yuV85qxYmPHNnlxS0BHi3GSG5Z+k/eweMRbhD39gYya EMBMHtYJpmQ= =tcYW -----END PGP SIGNATURE----- From owner-freebsd-current Tue Oct 28 09:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06653 for current-outgoing; Tue, 28 Oct 1997 09:41:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA06627; Tue, 28 Oct 1997 09:40:57 -0800 (PST) (envelope-from p.richards@elsevier.co.uk) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id RAA14627; Tue, 28 Oct 1997 17:39:31 GMT Received: from screavie.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP); Tue, 28 Oct 1997 17:39:53 +0000 Received: from tees.elsevier.co.uk (tees.elsevier.co.uk [193.131.192.70]) by screavie.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id RAA25560; Tue, 28 Oct 1997 17:39:49 GMT Received: (from dpr@localhost) by tees.elsevier.co.uk (8.8.5/8.8.5) id RAA00563; Tue, 28 Oct 1997 17:39:49 GMT To: Steve Kargl Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Retrieving data from a totally hosed filesystem References: <199710281701.JAA18177@troutmask.apl.washington.edu> From: Paul Richards Date: 28 Oct 1997 17:39:48 +0000 In-Reply-To: Steve Kargl's message of Tue, 28 Oct 1997 09:01:14 -0800 (PST) Message-ID: <57n2jtzt0b.fsf@tees.elsevier.co.uk> Lines: 20 X-Mailer: Gnus v5.4.37/Emacs 19.30 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Kargl writes: > I would use the backup tape I made before I started to experiment > with the disk subsystems. > > man dump > man restore :-) I don't back up the boxes I play on, I think in future I will though since I lost some play things I didn't want to lose. This is more of a "fun" exercise though to see how much can actually be retrieved since the raw data is actually on the disk. -- Dr Paul Richards. IT, Product Application Development. Email: p.richards@elsevier.co.uk Phone: x3155 From owner-freebsd-current Tue Oct 28 10:03:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08379 for current-outgoing; Tue, 28 Oct 1997 10:03:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08369 for ; Tue, 28 Oct 1997 10:03:38 -0800 (PST) (envelope-from Daniel_Sobral@voga.com.br) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id PAA08696 for ; Tue, 28 Oct 1997 15:02:30 -0300 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 0325653E.00631723 ; Tue, 28 Oct 1997 15:02:19 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: current@FreeBSD.ORG Message-ID: <0325653E.00626440.00@papagaio.voga.com.br> Date: Tue, 28 Oct 1997 15:02:15 -0300 Subject: Re: nullfs & current UPDATE! Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Yeah, that's a week-old message I'm replying to, so what? ;-) ] > > + struct vnode *vp = ap->a_vp; > > + struct null_node *xp = VTONULL(vp); > > + struct vnode *lowervp = xp->null_lowervp; > By the powers vested in us, we hereby announce that as of this > _____Tir 21 Okt 1997 21:35:09 CEST____ > it has been satisfied to us that the attached email fully and > entirely prove to us that the insight and persistence needed > for successful VFS hacking is present in the necessary amount in > _____Mr Ollivier Robert _____ > and therefore let it be know that he from this day on in his > good right to carry the title of > _____ VFS hacker ____ > with all the rights, duties, priviledges and ensignia that goes > with this title. I thought that kind of variable declaration was against style(9), and likely to provoke anger among the smp-enlightened. From owner-freebsd-current Tue Oct 28 10:07:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08684 for current-outgoing; Tue, 28 Oct 1997 10:07:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mailhost (user-2k7i8bm.dialup.mindspring.com [168.121.33.118]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA08668 for ; Tue, 28 Oct 1997 10:06:58 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0xQG2Z-000G5LC; Tue, 28 Oct 97 13:06 EST Message-ID: <345629C0.134062C9@mindspring.com> Date: Tue, 28 Oct 1997 13:06:56 -0500 From: Ron Bolin X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: StarOffice on 3.0 current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well I found some more info on my problem. Thanks to those that suggested several problem areas. I found that SO is sitting on a select call, waiting for something. After about 10 minutes it timesout and displays the program. I'll need to run this down, must be something to do with how SO finds my display. BTW, This system is a single Pent 133 32MB, ATI Mach64 2MB video, all SCSI peripherials. Ron -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-6875 Web: http://www.mindspring.com/~rlb ------------------------------------------------------------------------------- From owner-freebsd-current Tue Oct 28 10:38:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10918 for current-outgoing; Tue, 28 Oct 1997 10:38:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA10909 for ; Tue, 28 Oct 1997 10:38:02 -0800 (PST) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id NAA06497 for current@freebsd.org; Tue, 28 Oct 1997 13:37:41 -0500 (EST) From: Keith Mitchell Message-Id: <199710281837.NAA06497@weenix.guru.org> Subject: Small Problem with Linux Emul To: current@freebsd.org Date: Tue, 28 Oct 1997 13:37:41 -0500 (EST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been trying to get the linux version of the Quake server to work under 3.0-CURRENT to no avail. It works fine under 2.2-STABLE and 2.2.5. At a quick glance, it looks like the problem may be in the 4.3 COMPAT network stuff (specifically recv). A ktrace resulted in: 304 qwsv CALL old.recv(0xc,0xefbfdbb8) 304 qwsv RET old.recv -1 errno -11 Unknown error: -11 This happens a number of times. Also (but probably related) network address that it does manage to recive in recv calls come back garbled. i.e. 192.246.40.12 comes back as 24.220.191.239 I am running -CURRENT from about 3 weeks ago. I tried to update last night, but there was a problem with the compile that I didn't have time to look into. Perhaps I will get to that tonight. I didn't see any changes in this code in the past few weeks (in the commit messages), however. I have reinstalled the latest linux_lib stuff, but that doesn't seem to matter. Any ideas? -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved From owner-freebsd-current Tue Oct 28 11:19:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA13854 for current-outgoing; Tue, 28 Oct 1997 11:19:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.5.84]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA13827; Tue, 28 Oct 1997 11:19:15 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.7/8.8.7) id MAA18347; Tue, 28 Oct 1997 12:19:02 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd018322; Tue Oct 28 12:18:48 1997 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA04726; Tue, 28 Oct 1997 12:18:45 -0700 (MST) From: Terry Lambert Message-Id: <199710281918.MAA04726@usr06.primenet.com> Subject: Re: Retrieving data from a totally hosed filesystem To: p.richards@elsevier.co.uk (Paul Richards) Date: Tue, 28 Oct 1997 19:18:45 +0000 (GMT) Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <57pvoqypdr.fsf@tees.elsevier.co.uk> from "Paul Richards" at Oct 28, 97 01:43:28 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Why do these things come in flocks? 8-(. > This is Cc'd to current since I think there's a problem with fsck (see > below). No, there isn't (see below). > I totally trashed a partition on my hard disk a week ago ( I was > playing with bootblocks and scsi adapter setttings!) and I'd like to > try and retrieve data from, not critical but I'm curious how to go > about it since it's happened. This is a bug in the slice code, and in user accesibility of SCSI adapter settings. 8-). Only the first can be fixed in software... > Somehow I trashed the disklabel on the FreeBSD partition but > by using a combination of guesswork and memory I rebuilt one > and most of my partitions re-appeared without problem. One > however didn't. fsck said the superblock was invalid so, casting > caution to the wind I told fsck to use an alternate. Here is where you purchased your handbasket from the Infernal Transportation Authority. Unless this was your first partition (in which case, you probably blew the data on it during the writes you were doing, and there's no hope of a sane recovery without great effort), the reason you were unable to find a superblock is that you had the wrong start sector for the partition in your disklabel. At this point, you should have grovelled forward from the last successfully mounted partition's last superblock looking for the FS magic number. This would locate the first superblock, and therefore the start of the disk. You can know the real superblock from duplicates by knowing that the first superblock on an FS will have a filled in "last mounted on" string for the last place it was mounted. Duplicates won't, unless they are used for a mount and successful unmount. The message reported by fsck is of ultimate importantance. I doubt it said exactly "invalid". Generally, it complains about the magic number (corrupt or what you are pointing at is not a superblock), or about corruption (the non-variable parts of the superblock don't match the contents of the first backup). > Many coredumps of fsck later (I had to delete some inodes using > fsdb in order to get fsck to complete stage1) I had a totally > unravelled filesystem. Yes. It was corrupt as heck at this point. The problem is that fsck is a tool for doing two things: 1) In the event of a partial hardware failure, fsck returns the device to a know state so that you may back it up and discard the original device. What you had doesn't qualify, because the data was not corrupted by a hardware failure. The difference is that with a hardware failure, you can distinguish bad data from good data by virtue of hardware errors returned by the driver. 2) In event of a crash (power outage, etc.), fcsk can be used to deterministically back up exactly one failed transaction and return the FS metadata to a correct consistent state (an async mount gives you a 1 in 2^(n-1) chance of fsck guessing correctly -- a snowball's chance in hell). For what you did, fsck is not an appropriate tool to fix the damage. > fsck then tried to put all these files into lost+found but aborted > because it ran out of space in lost+found (which is why I've cc'd > this to current). > > So, now I'm curious about two things > > 1) fsck claims it will auto-expand lost+found if it needs to. This > seems to be very broken since it doesn't. I'm not sure the strategy of > building lost+found on the fly is a good one since there was no space > on this partition and it doesn't look like fsck is able to > to get enough space for the directory information. Prior to 4.4BSD, newfs reserved 8k of directory entry blocks as a "reserve". In 4.3BSD, directories could only grow, never shrink. This meant that if you created a large number of files and then removed them, the only way the directory entry blocks could be recovered was to delete and recreate the directory. This became more of a problem as things like news servers and terminfo and other things which abuse the FS directory structure as a database became more prevalent. In 4.4BSD, trailing empty directory blocks are ftruncate'd off the end of a directory. One consequence of this is that the first time you fsck, get something in lost+found, and remove it, your 8k reserve drops to one directory entry (it has to keep one block for "." and ".."). So it's usseless to pre-reserve space. Now the file names in lost+found that get created are "#"; on average, this takes more longwords (directory entry data is 4 byte aligned and null terminated) than average file names of 7 characters or less. This means that if you have a huge number of files to recover, you will use more directory blocks in the recovery than they used in their original directory. So even though the formerly occupied directory blocks are recovered for reuse earlier in the fsck, they may not contain enough space to complete the creation of the lost+found. Luckily, you followed the rules, and kept a 10% reserve space free on your disk, right? One of the points of the reserve is to make the block allocation rapid and relatively efficient (it is, in the limit, a hash function, and Knuth's "Seminumerical Algorithms" shows hashes degrade exponentially, so you really don't want to go over an 85% fill -- a 10% reserve lets you go to 90% fill). Another reason, however (if you care nothing about how fast your system runs), is that that space may be needed by root for system recovery (like you found out) or other administrative tasks. IMO, you wre probably recovering transh (to a large extent) because of an invalid starting offset. It's possible that a full recovery could take much more than the total disk space in the FS, depending on what random data ended up in what inodes or indirect blocks. > That might not actually be the problem since the corruption is quite > serious but the lost+found directory has been created and fsck does > start to place files in it so I'm suspicious that this is the > problem (i.e. not able to get find enough space). Either lost+found > should be pre-allocated as it used to be See above... in any case, the allocation was only 8k. > or we should find a way of getting fsck to build lost+found somewhere > else. I started hacking fsck to try and do this but didn't get very > far with it, the basic idea of changing the lost+found directory path > didn't seem to work. Technically, unless root sucked up the reserve and didn't give it back, there is supposed to be enough reserve to recover a hard drive from even catastrophic hardware failure. But your corruption was worse than any expectable catastrophic hardware failure, short of crashing the directory entry blocks and most of the reserve blocks, simultaneously. BTW: root sucking up reserve and not giving it back is a pilot error; if this happened here, avoid doing this in the future... 8-(. > 2) Has anyone got any bright ideas as to how I can salvage as much of > the data from this partition as is possible. Since the actual data is > not corrupted (a dd of the partition shows all the data is still > untouched) there might be a way to extract the data from the partition > and reconstruct a filesystem in another area of the disk. Seems like > an interesting challenge to me and I was wondering if anyone had any > tools as a starting point. If nothing else, I suspect it should be > possible to get the unlinked inodes connected to a directory as fsck > should have done in lost+found and at least retrieve the data in those > files. The easiest way would be to mount it read-only, ignoring the clean bit, and copy off what you could. You may need to hack things to make this work Then you should be able to blow the reference count on the inodes you copied off to zero, which will make them go away before more lost+found allocations are necessary. You will either need to write a tool to do this, or use fsdb to clri the inodes. This space can then be used by a subsequent fsck to continue to populate lost+found. One or two large files should be enough. Under *no* circumstances should you fudge the "clean bit" on the disk to get a read/write mount to avoid the pain of doing a clri. A single allocation or timestamp update on a bogus FS could render the rest of the data permanently unrecoverable. If you fudge the clean bit as part of your hacking, you *must* fudge it back to dirty to be sure to trigger the fsck -- a read-only mount is the only kind of mount you should use on this thing! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Oct 28 11:28:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14399 for current-outgoing; Tue, 28 Oct 1997 11:28:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14390 for ; Tue, 28 Oct 1997 11:28:20 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id UAA00549; Tue, 28 Oct 1997 20:26:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Daniel Sobral" cc: current@FreeBSD.ORG Subject: Re: nullfs & current UPDATE! In-reply-to: Your message of "Tue, 28 Oct 1997 15:02:15 -0300." <0325653E.00626440.00@papagaio.voga.com.br> Date: Tue, 28 Oct 1997 20:26:22 +0100 Message-ID: <547.878066782@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <0325653E.00626440.00@papagaio.voga.com.br>, "Daniel Sobral" writes: >> > + struct vnode *vp = ap->a_vp; >> > + struct null_node *xp = VTONULL(vp); >> > + struct vnode *lowervp = xp->null_lowervp; >I thought that kind of variable declaration was against style(9), and >likely to provoke anger among the smp-enlightened. I can't see why particular the smp-cursed should care, but the general sentiment on style(9) is that it lacks a implicit rule number zero: Stay in whatever style is in the file you modify. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Tue Oct 28 11:30:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14551 for current-outgoing; Tue, 28 Oct 1997 11:30:02 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14514 for ; Tue, 28 Oct 1997 11:29:57 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id UAA00560; Tue, 28 Oct 1997 20:27:36 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ron Bolin cc: FreeBSD Current Mailing List Subject: Re: StarOffice on 3.0 current In-reply-to: Your message of "Tue, 28 Oct 1997 13:06:56 EST." <345629C0.134062C9@mindspring.com> Date: Tue, 28 Oct 1997 20:27:34 +0100 Message-ID: <558.878066854@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <345629C0.134062C9@mindspring.com>, Ron Bolin writes: >Well I found some more info on my problem. Thanks to those that >suggested >several problem areas. > >I found that SO is sitting on a select call, waiting for something. >After about 10 minutes DNS, no doubt. Any linux emulation people who can tell what to do ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Tue Oct 28 11:38:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15036 for current-outgoing; Tue, 28 Oct 1997 11:38:36 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA15031 for ; Tue, 28 Oct 1997 11:38:33 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xQHSe-0001AB-00; Tue, 28 Oct 1997 11:37:56 -0800 Date: Tue, 28 Oct 1997 11:37:53 -0800 (PST) From: Tom To: Keith Mitchell cc: current@freebsd.org Subject: Re: Small Problem with Linux Emul In-Reply-To: <199710281837.NAA06497@weenix.guru.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 Oct 1997, Keith Mitchell wrote: ... > Any ideas? Use the BSDI quake server. It uses less CPU than the linux server, because it doesn't require add as much overhead. > -- > Keith Mitchell Head Administrator: acm.vt.edu > Email: kmitch@weenix.guru.org PGP key available upon request > http://weenix.guru.org/~kmitch > Address and URL (c) 1997 Keith Mitchell - All Rights Reserved > > Tom From owner-freebsd-current Tue Oct 28 12:39:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18906 for current-outgoing; Tue, 28 Oct 1997 12:39:47 -0800 (PST) (envelope-from owner-freebsd-current) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18893 for ; Tue, 28 Oct 1997 12:39:40 -0800 (PST) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id PAA10601; Tue, 28 Oct 1997 15:39:08 -0500 (EST) From: Keith Mitchell Message-Id: <199710282039.PAA10601@weenix.guru.org> Subject: Re: Small Problem with Linux Emul In-Reply-To: from Tom at "Oct 28, 97 11:37:53 am" To: tom@uniserve.com (Tom) Date: Tue, 28 Oct 1997 15:39:08 -0500 (EST) Cc: current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Use the BSDI quake server. It uses less CPU than the linux server, > because it doesn't require add as much overhead. I would, but it is the 1.64 level server that crashes on half the maps I have tried and also has quite a few bugs in it that have been fixed in the 2.01 server (which only exists for linux/solaris). -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch From owner-freebsd-current Tue Oct 28 12:46:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19408 for current-outgoing; Tue, 28 Oct 1997 12:46:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from news.NL.net (news.NL.net [193.78.240.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19387 for ; Tue, 28 Oct 1997 12:46:41 -0800 (PST) (envelope-from jos@oce.nl) Received: from smtp01.oce.nl ([134.188.1.25] HELO smtp01.oce.nl ident: NO-IDENT-SERVICE [port 1154]) by news.NL.net with SMTP id <2914547-461>; Tue, 28 Oct 1997 21:46:27 +0100 Received: by smtp01.oce.nl (5.x/SMI-SVR4) id AA11494; Tue, 28 Oct 1997 21:46:03 +0100 >Return-Path: Received: (qmail 3506 invoked from network); 28 Oct 1997 20:44:07 -0000 Received: from st1-jos.oce.nl (134.188.60.60) by ns-venlo.oce.nl with SMTP; 28 Oct 1997 20:44:07 -0000 Received: (qmail 22153 invoked by uid 911); 28 Oct 1997 20:41:56 -0000 Message-Id: <19971028204156.22152.qmail@st1-jos.oce.nl> Cc: Terry Lambert To: p.richards@elsevier.co.uk (Paul Richards) Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Retrieving data from a totally hosed filesystem In-Reply-To: Your message of "Tue, 28 Oct 1997 19:18:45 GMT." <199710281918.MAA04726@usr06.primenet.com> Date: Tue, 28 Oct 1997 21:41:56 +0100 From: Jos Backus Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710281918.MAA04726@usr06.primenet.com> you wrote: >> Seems like an interesting challenge to me and I was wondering if anyone had >> any tools as a starting point. Risking to be held a babbling fool, may I suggest that you have a look at ftp://koobera.math.uic.edu/pub/software/ufsread-0.50.shar.gz ? Groetjes, Jos -- Jos Backus _/ _/_/_/ CIM-ISGA/IS _/ _/ _/ Oce-Technologies B.V. _/ _/_/_/ Venlo, The Netherlands _/ _/ _/ _/ jos@oce.nl _/_/ _/_/_/ #include From owner-freebsd-current Tue Oct 28 14:53:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27961 for current-outgoing; Tue, 28 Oct 1997 14:53:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from seera.pl.hn.cp (usr15-dialup34.mix1.Sacramento.mci.net [166.55.6.162]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA27954 for ; Tue, 28 Oct 1997 14:53:22 -0800 (PST) (envelope-from gene@seera.pl.hn.cp) Received: (from gene@localhost) by seera.pl.hn.cp (8.8.7/8.8.7) id OAA01520; Tue, 28 Oct 1997 14:52:51 -0800 (PST) (envelope-from gene) From: Minsung Kim Message-Id: <199710282252.OAA01520@seera.pl.hn.cp> Subject: Re: StarOffice on 3.0 current In-Reply-To: <558.878066854@critter.freebsd.dk> from Poul-Henning Kamp at "Oct 28, 97 08:27:34 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 28 Oct 1997 14:52:49 -0800 (PST) Cc: freebsd-current@freebsd.org Reply-To: gene@nttlabs.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message <345629C0.134062C9@mindspring.com>, Ron Bolin writes: > >Well I found some more info on my problem. Thanks to those that > >suggested > >several problem areas. > > > >I found that SO is sitting on a select call, waiting for something. > >After about 10 minutes > > DNS, no doubt. Yes, it's DNS. I also had the same problem some weeks ago. I noticed that a UDP socket for name service is created during the hang, so I set up a local DNS and traced what SO looked up, and oh boy, SO was looking up tens of domain names which include some German domain names ending with ".de" -- I don't know why, though. :-) > > Any linux emulation people who can tell what to do ? Unfortunately, it seems that there's nothing much we can do about this since we cannot stop SO from doing DNS queries. However, there's a *silly* workaround. Temporarily bring down the network interfaces through which nameservers are reached during SO is launching. This will make all DNS lookups fail immediately. ;-) > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > -- Gene Minsung Kim http://seera.nttlabs.com/~gene/ Software Developer mailto:gene@nttlabs.com NTT America, Inc., Multimedia Communications Laboratories From owner-freebsd-current Tue Oct 28 15:47:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA01388 for current-outgoing; Tue, 28 Oct 1997 15:47:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA01370 for ; Tue, 28 Oct 1997 15:47:32 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id PAA07722; Tue, 28 Oct 1997 15:40:45 -0800 (PST) Date: Tue, 28 Oct 1997 15:40:45 -0800 (PST) Message-Id: <199710282340.PAA07722@silvia.HIP.Berkeley.EDU> To: mike@smith.net.au CC: helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org In-reply-to: <199710202332.JAA02439@word.smith.net.au> (message from Mike Smith on Tue, 21 Oct 1997 09:02:50 +0930) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, it seems more and more people are tripping over this one. Building and bebooting with a new kernel is not a solution to many, as one of the goals of the buildworld/installworld split was to be able to build world on the fileserver (which could be running something as old as 2.1.5) and install it on the client without disrupting the server at all. So, let's get to the real solution. I don't want to point my big fat fingers (well they really are, you can come see me!) to anyone but Poul-Henning appears to be the one that made the change initially with Peter trying to fix it. What do you think, guys? :) Satoshi ------- The cvs log of src/lib/libc/gen/getcwd.c says: : 1.14 Tue Sep 16 6:00:50 1997 by peter CVS Tags: HEAD Put a system call not present checking wrapper around the call to __getcwd(). I've got this libc code running on one of my machines at the moment without the __getcwd() syscall being present. : 1.11 Sun Sep 14 16:57:16 1997 by phk Add __getcwd() syscall, and have getcwd() take a shot at it. If your kernel doesn't support __getcwd() or if __getcwd() cannot deliver because of cache expiry, it does the canonical thing. From owner-freebsd-current Tue Oct 28 15:53:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA01778 for current-outgoing; Tue, 28 Oct 1997 15:53:38 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA01762 for ; Tue, 28 Oct 1997 15:53:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA19741; Wed, 29 Oct 1997 10:23:14 +1030 (CST) Message-ID: <19971029102314.63978@lemis.com> Date: Wed, 29 Oct 1997 10:23:14 +1030 From: Greg Lehey To: Ron Bolin Cc: FreeBSD Current Mailing List Subject: Re: StarOffice on 3.0 current References: <3455DD85.7C6DFFBE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <3455DD85.7C6DFFBE@mindspring.com>; from Ron Bolin on Tue, Oct 28, 1997 at 07:41:41AM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 28, 1997 at 07:41:41AM -0500, Ron Bolin wrote: > Has anyone had success in the getting Staroffice pakcage to run on 3.0? > I installed it and the linux devel/lib packages, but it just hangs. Give it 10 minutes or more. As somebody else commented, there seems to be a DNS problem, and sooner or later it gives up. After that, it runs "normally", which by comparison with other programs is slow. Greg From owner-freebsd-current Tue Oct 28 19:12:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14145 for current-outgoing; Tue, 28 Oct 1997 19:12:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from thelab.hub.org (ppp-142.halifax-01.ican.net [206.231.248.142]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14140 for ; Tue, 28 Oct 1997 19:12:38 -0800 (PST) (envelope-from scrappy@hub.org) Received: from thelab.hub.org (localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id XAA00960 for ; Tue, 28 Oct 1997 23:12:22 -0400 (AST) Date: Tue, 28 Oct 1997 23:12:21 -0400 (AST) From: The Hermit Hacker To: current@freebsd.org Subject: rc5 client under -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone running the v2 rc5 client from rc5.distributed.net under 3.0-CURRENT? I'm running 3.0 from Sept 28th, and each time I try to run it, it *totally* locks up my system...I have to actually turn off the computer and turn it back on again. Has anyone else experienced something similar? If not, then I'll upgrade to the most current before investigating further... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-current Tue Oct 28 20:28:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18012 for current-outgoing; Tue, 28 Oct 1997 20:28:28 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (garbanzo@congo-106.ppp.hooked.net [206.169.227.106]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18006 for ; Tue, 28 Oct 1997 20:28:24 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id UAA03931 for ; Tue, 28 Oct 1997 20:29:14 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 28 Oct 1997 20:29:14 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: Re: rc5 client under -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 Oct 1997, The Hermit Hacker wrote: > > Anyone running the v2 rc5 client from rc5.distributed.net under > 3.0-CURRENT? I'm running 3.0 from Sept 28th, and each time I try to run > it, it *totally* locks up my system...I have to actually turn off the > computer and turn it back on again. > > Has anyone else experienced something similar? If not, then I'll upgrade to > the most current before investigating further... No, I'm running current with the 64bit rc5 program and a kernel from Oct 26, and it works just fine. No problems whatsoever, in fact it's faster than the 56bit client was for me. - alex From owner-freebsd-current Tue Oct 28 22:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA23575 for current-outgoing; Tue, 28 Oct 1997 22:22:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA23558 for ; Tue, 28 Oct 1997 22:21:54 -0800 (PST) (envelope-from ken@plutotech.com) Received: (from ken@localhost) by pluto.plutotech.com (8.8.7/8.8.5) id XAA29894; Tue, 28 Oct 1997 23:21:51 -0700 (MST) From: Kenneth Merry Message-Id: <199710290621.XAA29894@pluto.plutotech.com> Subject: Re: rc5 client under -current In-Reply-To: from Alex at "Oct 28, 97 08:29:14 pm" To: garbanzo@hooked.net (Alex) Date: Tue, 28 Oct 1997 23:21:51 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alex wrote... > > > On Tue, 28 Oct 1997, The Hermit Hacker wrote: > > > > > Anyone running the v2 rc5 client from rc5.distributed.net under > > 3.0-CURRENT? I'm running 3.0 from Sept 28th, and each time I try to run > > it, it *totally* locks up my system...I have to actually turn off the > > computer and turn it back on again. > > > > Has anyone else experienced something similar? If not, then I'll upgrade to > > the most current before investigating further... > > No, I'm running current with the 64bit rc5 program and a kernel from Oct > 26, and it works just fine. No problems whatsoever, in fact it's faster > than the 56bit client was for me. I tried it out with a kernel from October 26th on my SMP box; I ran two copies of it simultaneously without a problem. (I was trying to reproduce PR kern/4859. The guy who filed that PR was running 3.0-971002-SNAP.) If you're having trouble with it, I'd suggest getting newer sources, since it doesn't seem to be a problem now. Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-current Tue Oct 28 22:43:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA24549 for current-outgoing; Tue, 28 Oct 1997 22:43:17 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA24543 for ; Tue, 28 Oct 1997 22:43:12 -0800 (PST) (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.8.7/RBI-Z14) with ESMTP id HAA26535 for ; Wed, 29 Oct 1997 07:43:07 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id HAA13296 for freebsd-current@freefall.cdrom.com; Wed, 29 Oct 1997 07:56:07 +0100 (MET) Date: Wed, 29 Oct 1997 07:56:07 +0100 (MET) From: Christoph Kukulies Message-Id: <199710290656.HAA13296@gil.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: tcsh maxproc limit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I had a limit maxproc 80 in my .login (tcsh) and since I moved a 2.2.2 machine to -current I'm getting: limit: maxproc: Can't set limit 32 seems to be the limit I can set it to. Do I have to rebuild tcsh or is it a different problem? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Oct 28 22:46:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA24816 for current-outgoing; Tue, 28 Oct 1997 22:46:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA24811 for ; Tue, 28 Oct 1997 22:46:33 -0800 (PST) (envelope-from murray@pooh.cdrom.com) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.5/8.7.3) with SMTP id WAA05554; Tue, 28 Oct 1997 22:45:26 -0800 (PST) Date: Tue, 28 Oct 1997 22:45:25 -0800 (PST) From: Murray Stokely To: The Hermit Hacker cc: current@FreeBSD.ORG Subject: Re: rc5 client under -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 Oct 1997, The Hermit Hacker wrote: % Anyone running the v2 rc5 client from rc5.distributed.net under % 3.0-CURRENT? I'm running 3.0 from Sept 28th, and each time I try to run % it, it *totally* locks up my system...I have to actually turn off the % computer and turn it back on again. % % Has anyone else experienced something similar? If not, then I'll upgrade to % the most current before investigating further... The 64bit client is working fine on several -current boxes here. Murray Stokely From owner-freebsd-current Tue Oct 28 23:00:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25539 for current-outgoing; Tue, 28 Oct 1997 23:00:17 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25531 for ; Tue, 28 Oct 1997 23:00:13 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id HAA01440; Wed, 29 Oct 1997 07:58:28 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: asami@cs.berkeley.edu (Satoshi Asami) cc: mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build In-reply-to: Your message of "Tue, 28 Oct 1997 15:40:45 PST." <199710282340.PAA07722@silvia.HIP.Berkeley.EDU> Date: Wed, 29 Oct 1997 07:58:27 +0100 Message-ID: <1438.878108307@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710282340.PAA07722@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: >Well, it seems more and more people are tripping over this one. >Building and bebooting with a new kernel is not a solution to many, as >one of the goals of the buildworld/installworld split was to be able >to build world on the fileserver (which could be running something as >old as 2.1.5) and install it on the client without disrupting the >server at all. > >So, let's get to the real solution. I don't want to point my big fat >fingers (well they really are, you can come see me!) to anyone but >Poul-Henning appears to be the one that made the change initially with >Peter trying to fix it. > >What do you think, guys? :) I may be dense here, but what do you think is the "real" solution ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Tue Oct 28 23:06:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25900 for current-outgoing; Tue, 28 Oct 1997 23:06:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25882 for ; Tue, 28 Oct 1997 23:06:23 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA16634; Tue, 28 Oct 1997 23:04:57 -0800 (PST) Date: Tue, 28 Oct 1997 23:04:57 -0800 (PST) Message-Id: <199710290704.XAA16634@silvia.HIP.Berkeley.EDU> To: phk@critter.freebsd.dk CC: mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org In-reply-to: <1438.878108307@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 29 Oct 1997 07:58:27 +0100) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I may be dense here, but what do you think is the "real" solution ? I wouldn't be asking here if I knew. ;) Do you know why it doesn't work now? Your commit message appears to indicate that this is supposed to work. Could the fact that the environment variables are pointing to the newly built shared libraries have something to do with this? (Just a wild guess.) Satoshi From owner-freebsd-current Tue Oct 28 23:20:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA26435 for current-outgoing; Tue, 28 Oct 1997 23:20:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA26430 for ; Tue, 28 Oct 1997 23:20:12 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA23260; Tue, 28 Oct 1997 23:16:12 -0800 (PST) Date: Tue, 28 Oct 1997 23:16:12 -0800 (PST) Message-Id: <199710290716.XAA23260@silvia.HIP.Berkeley.EDU> To: phk@critter.freebsd.dk CC: mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org In-reply-to: <1657.878108917@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 29 Oct 1997 08:08:37 +0100) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Well, my take on this is that you're trying to do the impossible. Well, I have been talking about this for a long time. I wonder where you were. * If you want make world to run on it's own binaries/libs, then the * kernel has to support those, and short of making kludges like the * one Peter has put around the __getcwd() (Which I thought worked ??) * there is no way to guarantee that it can be done. A kludge is fine. * Besides, doing a make world on -current sources on a 2.X machine * falls way short of the goal. All of /etc is still the old stuff. * * I think it is time to say: * * If you want to get from 2.X to 3.X, you install a 3.X snapshot I'm afraid you are *completely* missing the point, Kamp-san. People want to build -current on a 2.X fileserver so they can install it on a 3.X client. (Or vice versa.) It was working until the getcwd() change went in. Peter thought he could fix it. We are now trying to see why it doesn't work. I'll let Terry take care of the rest to educate you on the difference of the host system and the target system. (I can't believe I'm saying this. ;) Satoshi From owner-freebsd-current Tue Oct 28 23:25:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA26676 for current-outgoing; Tue, 28 Oct 1997 23:25:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA26665 for ; Tue, 28 Oct 1997 23:25:38 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id IAA01413; Wed, 29 Oct 1997 08:25:10 +0100 (MET) Message-Id: <199710290725.IAA01413@sos.freebsd.dk> Subject: Re: StarOffice on 3.0 current In-Reply-To: <19971029102314.63978@lemis.com> from Greg Lehey at "Oct 29, 97 10:23:14 am" To: grog@lemis.com (Greg Lehey) Date: Wed, 29 Oct 1997 08:25:10 +0100 (MET) Cc: rlb@mindspring.com, freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Greg Lehey who wrote: > On Tue, Oct 28, 1997 at 07:41:41AM -0500, Ron Bolin wrote: > > Has anyone had success in the getting Staroffice pakcage to run on 3.0? > > I installed it and the linux devel/lib packages, but it just hangs. > > Give it 10 minutes or more. As somebody else commented, there seems > to be a DNS problem, and sooner or later it gives up. After that, it > runs "normally", which by comparison with other programs is slow. Hmm, just get the _linux_ DNS set up proberly like its done in linux-libs-2.4 then it will work. I don't se it running 'slow' here, in fact its a pleasure to use (P6@233/96M system) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Tue Oct 28 23:33:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA27222 for current-outgoing; Tue, 28 Oct 1997 23:33:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA27210 for ; Tue, 28 Oct 1997 23:33:02 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id XAA19555; Tue, 28 Oct 1997 23:29:01 -0800 (PST) Message-ID: <19971028232900.58006@hydrogen.nike.efn.org> Date: Tue, 28 Oct 1997 23:29:00 -0800 From: John-Mark Gurney To: Poul-Henning Kamp Cc: Satoshi Asami , mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build References: <199710282340.PAA07722@silvia.HIP.Berkeley.EDU> <1438.878108307@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <1438.878108307@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Oct 29, 1997 at 07:58:27AM +0100 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp scribbled this message on Oct 29: > In message <199710282340.PAA07722@silvia.HIP.Berkeley.EDU>, Satoshi Asami write > s: > >Well, it seems more and more people are tripping over this one. > >Building and bebooting with a new kernel is not a solution to many, as > >one of the goals of the buildworld/installworld split was to be able > >to build world on the fileserver (which could be running something as > >old as 2.1.5) and install it on the client without disrupting the > >server at all. > > > >So, let's get to the real solution. I don't want to point my big fat > >fingers (well they really are, you can come see me!) to anyone but > >Poul-Henning appears to be the one that made the change initially with > >Peter trying to fix it. > > > >What do you think, guys? :) > > I may be dense here, but what do you think is the "real" solution ? well.. I'm pretty sure that this was happening BEFORE this commit went into the tree... I took share/termcap out of the Makefile on: hydrogen,ttypf,~/FreeBSD-checkout/current/src/share,507$ls -l Makefile -rw-r--r-- 1 jmg wheel 198 Aug 25 07:33 Makefile and the latest revision of that file was Sat Jul 19 15:17:41 1997... so you need to search earlier than that... not sure how far back this started... it was only a bit before then that I was able to do a buildworld... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Tue Oct 28 23:53:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA28588 for current-outgoing; Tue, 28 Oct 1997 23:53:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA28577 for ; Tue, 28 Oct 1997 23:53:15 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id XAA00994; Tue, 28 Oct 1997 23:53:11 -0800 (PST) Message-ID: <19971028235309.25355@hydrogen.nike.efn.org> Date: Tue, 28 Oct 1997 23:53:09 -0800 From: John-Mark Gurney To: Satoshi Asami Cc: freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build References: <1657.878108917@critter.freebsd.dk> <199710290716.XAA23260@silvia.HIP.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199710290716.XAA23260@silvia.HIP.Berkeley.EDU>; from Satoshi Asami on Tue, Oct 28, 1997 at 11:16:12PM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami scribbled this message on Oct 28: > * Besides, doing a make world on -current sources on a 2.X machine > * falls way short of the goal. All of /etc is still the old stuff. > * > * I think it is time to say: > * > * If you want to get from 2.X to 3.X, you install a 3.X snapshot > > I'm afraid you are *completely* missing the point, Kamp-san. People > want to build -current on a 2.X fileserver so they can install it on a > 3.X client. (Or vice versa.) It was working until the getcwd() > change went in. Peter thought he could fix it. We are now trying to > see why it doesn't work. well.. if any body wants a core from vi, I can get you one... know how anoying it is to acidentally type vi from your "-current build environment session" and have it core dump?? :) how do I get the syscall off it? and I hope your not going to say KTRACE, as I don't have it compiled into my kernel right now... oh... and I'm still turning out worlds on my 2.2.1-R box... (I plan on getting my notebook up to -current with the buildworld that's running now)... I've been tempted to add the following to our src/Makefile: :) rome: @echo "Sorry, but Rome wasn't built in a day." -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Wed Oct 29 00:31:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA01379 for current-outgoing; Wed, 29 Oct 1997 00:31:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA01372 for ; Wed, 29 Oct 1997 00:31:27 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id JAA06018; Wed, 29 Oct 1997 09:30:52 +0100 (MET) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id IAA01659; Wed, 29 Oct 1997 08:08:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: asami@cs.berkeley.edu (Satoshi Asami) cc: mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build In-reply-to: Your message of "Tue, 28 Oct 1997 23:04:57 PST." <199710290704.XAA16634@silvia.HIP.Berkeley.EDU> Date: Wed, 29 Oct 1997 08:08:37 +0100 Message-ID: <1657.878108917@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710290704.XAA16634@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * I may be dense here, but what do you think is the "real" solution ? > >I wouldn't be asking here if I knew. ;) > >Do you know why it doesn't work now? Your commit message appears to >indicate that this is supposed to work. Could the fact that the >environment variables are pointing to the newly built shared libraries >have something to do with this? (Just a wild guess.) Well, my take on this is that you're trying to do the impossible. If you want make world to run on it's own binaries/libs, then the kernel has to support those, and short of making kludges like the one Peter has put around the __getcwd() (Which I thought worked ??) there is no way to guarantee that it can be done. Besides, doing a make world on -current sources on a 2.X machine falls way short of the goal. All of /etc is still the old stuff. I think it is time to say: If you want to get from 2.X to 3.X, you install a 3.X snapshot -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Wed Oct 29 00:38:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA01702 for current-outgoing; Wed, 29 Oct 1997 00:38:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA01689 for ; Wed, 29 Oct 1997 00:38:22 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id JAA06040; Wed, 29 Oct 1997 09:37:46 +0100 (MET) Received: from critter.freebsd.dk (localhost.dk.tfs.com [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id JAA00848; Wed, 29 Oct 1997 09:36:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: asami@cs.berkeley.edu (Satoshi Asami) cc: mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build In-reply-to: Your message of "Tue, 28 Oct 1997 23:16:12 PST." <199710290716.XAA23260@silvia.HIP.Berkeley.EDU> Date: Wed, 29 Oct 1997 09:36:54 +0100 Message-ID: <846.878114214@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710290716.XAA23260@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * If you want to get from 2.X to 3.X, you install a 3.X snapshot > >I'm afraid you are *completely* missing the point, Kamp-san. People >want to build -current on a 2.X fileserver so they can install it on a >3.X client. (Or vice versa.) It was working until the getcwd() >change went in. Peter thought he could fix it. We are now trying to >see why it doesn't work. I'm sorry Satoshi-san, then people should install a 3.X snap on a client, NFS mount their diskspace and make world that way. >I'll let Terry take care of the rest to educate you on the difference >of the host system and the target system. (I can't believe I'm saying >this. ;) You don't need to that. But imagine for a moment that we're talking about compiling a alpha-world on a i386 machine and you will quickly realize why the very thing you are complaining about is an instance of "the wrong thing to do". So rather than complaining about __getcwd(), you should either realize that you are asking for something we cannot currently do or alternatively make it so we can do it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Wed Oct 29 01:29:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA04546 for current-outgoing; Wed, 29 Oct 1997 01:29:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA04541 for ; Wed, 29 Oct 1997 01:29:36 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA14235; Wed, 29 Oct 1997 01:29:21 -0800 (PST) Date: Wed, 29 Oct 1997 01:29:21 -0800 (PST) Message-Id: <199710290929.BAA14235@silvia.HIP.Berkeley.EDU> To: phk@critter.freebsd.dk CC: freebsd-current@freefall.FreeBSD.org In-reply-to: <846.878114214@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 29 Oct 1997 09:36:54 +0100) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I'm sorry Satoshi-san, then people should install a 3.X snap on * a client, NFS mount their diskspace and make world that way. That always worked, but it is horrendously slow. Besides, how about "make release"? Doesn't that thing build a target world on the host system? * You don't need to that. But imagine for a moment that we're talking * about compiling a alpha-world on a i386 machine and you will quickly * realize why the very thing you are complaining about is an instance of * "the wrong thing to do". So rather than complaining about __getcwd(), * you should either realize that you are asking for something we cannot * currently do or alternatively make it so we can do it. You like to knock down your own strawman don't you? ;) Extrapolating into the future, you can prove anything is bound to be doomed. Rhetoric doesn't do any good here. You just made life very hard for people to upgrade, as well as negating a large part of my few month's work of work. I'm trying to fix it. If you are just going to try to justify why you broke that, there is no need for that. (That's why I said "I don't want to point fingers.") If you are not willing to help, just say so, and I won't bother you again. Satoshi From owner-freebsd-current Wed Oct 29 02:12:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA06870 for current-outgoing; Wed, 29 Oct 1997 02:12:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA06865 for ; Wed, 29 Oct 1997 02:12:02 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id LAA06396; Wed, 29 Oct 1997 11:11:29 +0100 (MET) Received: from critter.freebsd.dk (localhost.dk.tfs.com [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id LAA01128; Wed, 29 Oct 1997 11:10:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: asami@cs.berkeley.edu (Satoshi Asami) cc: freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build In-reply-to: Your message of "Wed, 29 Oct 1997 01:29:21 PST." <199710290929.BAA14235@silvia.HIP.Berkeley.EDU> Date: Wed, 29 Oct 1997 11:10:37 +0100 Message-ID: <1126.878119837@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710290929.BAA14235@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * I'm sorry Satoshi-san, then people should install a 3.X snap on > * a client, NFS mount their diskspace and make world that way. > >That always worked, but it is horrendously slow. Besides, how about >"make release"? Doesn't that thing build a target world on the host >system? And wouldn't that work over NFS as well ? You lost me... >You just made life very >hard for people to upgrade, as well as negating a large part of my few >month's work of work. I just wastly improve the speed of getcwd(), yes. Are you trying to stop progress in the name of transisition ? I can't see any reason why make world should need to run any program that is linked to the newly compiled libc... And in that respect I think that most of your work is headed the wrong direction... >I'm trying to fix it. If you are just going to try to justify why you >broke that, there is no need for that. (That's why I said "I don't >want to point fingers.") If you are not willing to help, just say so, >and I won't bother you again. I'm very willing to help, but only if we attack the correct problem: "How can I compile my FreeBSD sources on a foreign platform". rather than "How do I avoid the most obvious problems compiling on an outdated FreeBSD system". I actually belive that cross-compiling is better than native compiling because you cannot make the kind of shortcuts that way which is giving us trouble now. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Wed Oct 29 02:38:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA07900 for current-outgoing; Wed, 29 Oct 1997 02:38:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA07886 for ; Wed, 29 Oct 1997 02:38:09 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.7/D) id NAA19182; Wed, 29 Oct 1997 13:36:44 +0300 (MSK) Posted-Date: Wed, 29 Oct 1997 13:36:44 +0300 (MSK) Message-ID: <19971029133643.17087@demos.su> Date: Wed, 29 Oct 1997 13:36:43 +0300 From: "Mikhail A. Sokolov" To: Steve Passe Cc: current@FreeBSD.ORG Subject: Re: current/nfs References: <19971028104910.43916@demos.su> <199710281616.JAA23337@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 In-Reply-To: <199710281616.JAA23337@Ilsa.StevesCafe.com>; from Steve Passe on Tue, Oct 28, 1997 at 09:16:04AM -0700 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 28, 1997 at 09:16:04AM -0700, Steve Passe wrote: # Hi, # > One machine runs 19971011-current and 'hangs' pretty regularily, then # > tries to reboot, tries to sync and there hangs. The machine has pretty hard # > task to be an nfs server for 5 others with up to 6000 interrupts/second, # > motherboard is intel PR440FX, 2xppro200, there are enough swap/memory space. # # be more specific, what messages come out when it hangs/reboots? 'Cannot switch to CPU 0' \n 'Syncing disks' (or what's that message..) and won't reboot. That's last one I caught yesterday, all other cases were just 'Syncing' and there we stale. Now I made it non-SMP :-(, awaiting ... Btw, what's that when it has 2 cpu's, the average load is _always_ >1,3, where when the second processor is not enabled, it's _always_ (exept when they start some perl :-)) > 0,60 ? It's peer (2.2.2+security fixes) would casually yelp that nfs server is not responding, the find it (in a second or so) and finally hang in a frozen state with a 'nfsbiostat panic'. #> yell it can't start second CPU, - mp_lock 1000005, abort trap. It will do ok #> on 233Mhz with 19971011-current, as well as 970926-SNAP. # this is probably the race fixed by: Thank you. # Steve Passe -- -mishania, stressed. From owner-freebsd-current Wed Oct 29 03:10:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA09264 for current-outgoing; Wed, 29 Oct 1997 03:10:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA09257 for ; Wed, 29 Oct 1997 03:10:55 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id DAA14491; Wed, 29 Oct 1997 03:08:13 -0800 (PST) Date: Wed, 29 Oct 1997 03:08:13 -0800 (PST) Message-Id: <199710291108.DAA14491@silvia.HIP.Berkeley.EDU> To: phk@critter.freebsd.dk CC: freebsd-current@freefall.FreeBSD.org In-reply-to: <1126.878119837@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 29 Oct 1997 11:10:37 +0100) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Are you trying to stop progress in the name of transisition ? Absolutely not. If that wasn't obvious, let me state it here. * I can't see any reason why make world should need to run any program * that is linked to the newly compiled libc... And in that respect I * think that most of your work is headed the wrong direction... That is because some of the tools required to build the world may need functions that only exist in new libraries. It has always been that way, I haven't changed it. * I'm very willing to help, but only if we attack the correct problem: * * "How can I compile my FreeBSD sources on a foreign platform". Here you go again, throwing a smokescreen. I don't mind you planning ahead, go ahead and think about it all you like. I will take that as a "no", so please stop changing the subject. :( Satoshi From owner-freebsd-current Wed Oct 29 03:20:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA09869 for current-outgoing; Wed, 29 Oct 1997 03:20:20 -0800 (PST) (envelope-from owner-freebsd-current) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA09857 for ; Wed, 29 Oct 1997 03:20:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id MAA06665; Wed, 29 Oct 1997 12:19:42 +0100 (MET) Received: from critter.freebsd.dk (localhost.dk.tfs.com [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id MAA01380; Wed, 29 Oct 1997 12:18:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: asami@cs.berkeley.edu (Satoshi Asami) cc: freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build In-reply-to: Your message of "Wed, 29 Oct 1997 03:08:13 PST." <199710291108.DAA14491@silvia.HIP.Berkeley.EDU> Date: Wed, 29 Oct 1997 12:18:51 +0100 Message-ID: <1378.878123931@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710291108.DAA14491@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * I'm very willing to help, but only if we attack the correct problem: > * > * "How can I compile my FreeBSD sources on a foreign platform". > >Here you go again, throwing a smokescreen. I don't mind you planning >ahead, go ahead and think about it all you like. I will take that as >a "no", so please stop changing the subject. :( I'm not changing the subject, you asked if I cared to help, and I told you what I felt like helping with: If you want to kluge a solution for to be able to compile current on 2.X systems, go ahead, I have no interest in that. (This kind of thing breaks easily if new syscalls are added). If you want to improve our build process to become more independent of the hosting platform, I will happily help you. (This kind of thing is far more robust in the face of source changes). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Wed Oct 29 03:24:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA10013 for current-outgoing; Wed, 29 Oct 1997 03:24:43 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA10004 for ; Wed, 29 Oct 1997 03:24:38 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id DAA14565; Wed, 29 Oct 1997 03:24:19 -0800 (PST) Date: Wed, 29 Oct 1997 03:24:19 -0800 (PST) Message-Id: <199710291124.DAA14565@silvia.HIP.Berkeley.EDU> To: peter@spinner.netplex.com.au CC: freebsd-current@freefall.FreeBSD.org In-reply-to: <1126.878119837@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 29 Oct 1997 11:10:37 +0100) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Peter, I took a look at your patch (attached below for the readers' convenience): =================================================================== RCS file: /home/ncvs/src/lib/libc/gen/getcwd.c,v retrieving revision 1.13 retrieving revision 1.14 diff -p -u -r1.13 -r1.14 --- src/lib/libc/gen/getcwd.c 1997/09/15 17:40:15 1.13 +++ /home/ncvs/src/lib/libc/gen/getcwd.c 1997/09/16 06:00:50 1.14 @@ -45,11 +45,14 @@ static char sccsid[] = "@(#)getcwd.c 8.5 #include #include #include +#include #define ISDOT(dp) \ (dp->d_name[0] == '.' && (dp->d_name[1] == '\0' || \ (dp->d_name[1] == '.' && dp->d_name[2] == '\0'))) +static int have__getcwd = 1; /* 0 = no, 1 = perhaps, 2 = yes */ + char * getcwd(pt, size) char *pt; @@ -89,17 +92,40 @@ getcwd(pt, size) return (NULL); ept = pt + ptsize; } - if (!__getcwd(pt, ept - pt)) { - if (*pt != '/') { - bpt = pt; - ept = pt + strlen(pt) - 1; - while (bpt < ept) { - c = *bpt; - *bpt++ = *ept; - *ept-- = c; + if (have__getcwd) { + struct sigaction sa, osa; + int sigsys_installed = 0; + int ret; + + if (have__getcwd == 1) { /* unsure? */ + bzero(&sa, sizeof(sa)); + sa.sa_handler = SIG_IGN; + if (sigaction(SIGSYS, &sa, &osa) >= 0) + sigsys_installed = 1; + } + ret = __getcwd(pt, ept - pt); + if (sigsys_installed == 1) { + int oerrno = errno; + sigaction(SIGSYS, &osa, NULL); + errno = oerrno; + } + /* XXX a bogus syscall seems to return EINVAL(!) */ + if (ret < 0 && (errno == ENOSYS || errno == EINVAL)) + have__getcwd = 0; + else if (have__getcwd == 1) + have__getcwd = 2; /* yep, remember we have it */ + if (ret == 0) { + if (*pt != '/') { + bpt = pt; + ept = pt + strlen(pt) - 1; + while (bpt < ept) { + c = *bpt; + *bpt++ = *ept; + *ept-- = c; + } } + return (pt); } - return (pt); } bpt = ept - 1; *bpt = '\0'; ======= It appears to be fine, I can't find anything wrong with it except the "else if (have__getcwd == 1)" is sort of redundant ("else" is good enough here). This is what I know about the "make world" problem: (1) It only breaks on some programs, most notably vi during termcap compilation. There should be some other programs before vi that use getcwd(), I wonder why they don't die. (2) It only breaks on older systems, like 2.1.5 or 2.2.2. I think it works on a recent 2.2-stable (I'm not sure, testing now). Do you have any idea what's going on? Especially (2), was there a matching commit that went into RELENG_2_2 at that time? Thanks Satoshi From owner-freebsd-current Wed Oct 29 03:50:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA11244 for current-outgoing; Wed, 29 Oct 1997 03:50:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA11228 for ; Wed, 29 Oct 1997 03:50:23 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id DAA12135; Wed, 29 Oct 1997 03:50:16 -0800 (PST) Message-ID: <19971029035016.24540@hydrogen.nike.efn.org> Date: Wed, 29 Oct 1997 03:50:16 -0800 From: John-Mark Gurney To: Satoshi Asami Cc: peter@spinner.netplex.com.au, freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build References: <1126.878119837@critter.freebsd.dk> <199710291124.DAA14565@silvia.HIP.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199710291124.DAA14565@silvia.HIP.Berkeley.EDU>; from Satoshi Asami on Wed, Oct 29, 1997 at 03:24:19AM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami scribbled this message on Oct 29: > This is what I know about the "make world" problem: > > (1) It only breaks on some programs, most notably vi during termcap > compilation. There should be some other programs before vi that > use getcwd(), I wonder why they don't die. > > (2) It only breaks on older systems, like 2.1.5 or 2.2.2. I think it > works on a recent 2.2-stable (I'm not sure, testing now). > > Do you have any idea what's going on? Especially (2), was there a > matching commit that went into RELENG_2_2 at that time? I looked at the diffs between 2.2.1 and 2.2.5, and it looks like the call that we might be hitting is the new issuid... I KNOW that this was before the getcwd syscall was added... (haven't you gotten my last few posts on the subject??)... termcap building failed on a buildworld around late august which is before the getcwd syscalls... ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Wed Oct 29 05:28:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA15485 for current-outgoing; Wed, 29 Oct 1997 05:28:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA15480 for ; Wed, 29 Oct 1997 05:28:42 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id AAA14486; Thu, 30 Oct 1997 00:23:29 +1100 Date: Thu, 30 Oct 1997 00:23:29 +1100 From: Bruce Evans Message-Id: <199710291323.AAA14486@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, gurney_j@efn.org Subject: Re: bad system call - world build Cc: freebsd-current@freefall.FreeBSD.org, peter@spinner.netplex.com.au Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> This is what I know about the "make world" problem: >> >> (1) It only breaks on some programs, most notably vi during termcap >> compilation. There should be some other programs before vi that >> use getcwd(), I wonder why they don't die. >... >I looked at the diffs between 2.2.1 and 2.2.5, and it looks like the >call that we might be hitting is the new issuid... I KNOW that this I thought this was well known. getcwd() is a library function with a standard interface, so incompatibilities are easy to avoid, and are avoided. issetugid() is a syscall with a new interface. It can't possibly work with old kernels. Unfortunately, ex(1) uses it, at least for the termcap script. It is surprising that it isn't used more for `make world', since it is sometimes called by setlocale(). Bruce From owner-freebsd-current Wed Oct 29 06:34:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA18810 for current-outgoing; Wed, 29 Oct 1997 06:34:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA18799 for ; Wed, 29 Oct 1997 06:34:29 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00928; Thu, 30 Oct 1997 00:58:54 +1030 (CST) Message-Id: <199710291428.AAA00928@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp cc: Ron Bolin , FreeBSD Current Mailing List Subject: Re: StarOffice on 3.0 current In-reply-to: Your message of "Tue, 28 Oct 1997 20:27:34 BST." <558.878066854@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Oct 1997 00:58:52 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In message <345629C0.134062C9@mindspring.com>, Ron Bolin writes: > >Well I found some more info on my problem. Thanks to those that > >suggested > >several problem areas. > > > >I found that SO is sitting on a select call, waiting for something. > >After about 10 minutes > > DNS, no doubt. > > Any linux emulation people who can tell what to do ? There appear to be some DNS-related problems with Linux emulation and -current. It's possible that the resolver in the current linux-lib kit requires some more careful configuration. Make sure that you have /compat/linux/etc/host.conf and /compat/linux/ etc/resolv.conf set up just for starters. mike From owner-freebsd-current Wed Oct 29 07:05:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20516 for current-outgoing; Wed, 29 Oct 1997 07:05:21 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20492 for ; Wed, 29 Oct 1997 07:05:13 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id BAA01138; Thu, 30 Oct 1997 01:31:09 +1030 (CST) Message-Id: <199710291501.BAA01138@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Keith Mitchell cc: current@freebsd.org Subject: Re: Small Problem with Linux Emul In-reply-to: Your message of "Tue, 28 Oct 1997 13:37:41 CDT." <199710281837.NAA06497@weenix.guru.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Oct 1997 01:31:06 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have been trying to get the linux version of the Quake server to work > under 3.0-CURRENT to no avail. It works fine under 2.2-STABLE and 2.2.5. > > At a quick glance, it looks like the problem may be in the 4.3 COMPAT > network stuff (specifically recv). A ktrace resulted in: > > 304 qwsv CALL old.recv(0xc,0xefbfdbb8) > 304 qwsv RET old.recv -1 errno -11 Unknown error: -11 You should be aware that Linux has different syscall numbers, but kdump has no way of knowing that this is a dump from a Linux executable. The above is probably recvfrom(); you can trace this through linux_socket.c and into kern_uipc.c. mike From owner-freebsd-current Wed Oct 29 12:02:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09473 for current-outgoing; Wed, 29 Oct 1997 12:02:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (ala-ca26-02.ix.netcom.com [207.93.42.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09463 for ; Wed, 29 Oct 1997 12:02:19 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id MAA29347; Wed, 29 Oct 1997 12:01:45 -0800 (PST) Date: Wed, 29 Oct 1997 12:01:45 -0800 (PST) Message-Id: <199710292001.MAA29347@silvia.HIP.Berkeley.EDU> To: gurney_j@resnet.uoregon.edu CC: peter@spinner.netplex.com.au, freebsd-current@freefall.FreeBSD.org In-reply-to: <19971029035016.24540@hydrogen.nike.efn.org> (message from John-Mark Gurney on Wed, 29 Oct 1997 03:50:16 -0800) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I looked at the diffs between 2.2.1 and 2.2.5, and it looks like the * call that we might be hitting is the new issuid... I KNOW that this * was before the getcwd syscall was added... (haven't you gotten my last * few posts on the subject??)... termcap building failed on a buildworld * around late august which is before the getcwd syscalls... Aww. Sorry, I thought it was getcwd() because everyone was saying so. That's what I get for sticking my head into something I'm not familiar with. Sorry, Poul-Henning. ;) Satoshi From owner-freebsd-current Wed Oct 29 12:16:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10553 for current-outgoing; Wed, 29 Oct 1997 12:16:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from silvia.HIP.Berkeley.EDU (ala-ca26-02.ix.netcom.com [207.93.42.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10547 for ; Wed, 29 Oct 1997 12:16:04 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id MAA29407; Wed, 29 Oct 1997 12:15:12 -0800 (PST) Date: Wed, 29 Oct 1997 12:15:12 -0800 (PST) Message-Id: <199710292015.MAA29407@silvia.HIP.Berkeley.EDU> To: bde@zeta.org.au CC: gurney_j@efn.org, freebsd-current@freefall.FreeBSD.org, peter@spinner.netplex.com.au In-reply-to: <199710291323.AAA14486@godzilla.zeta.org.au> (message from Bruce Evans on Thu, 30 Oct 1997 00:23:29 +1100) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I thought this was well known. getcwd() is a library function with a Well, I have heard from more than one person on this list that it was getcwd(). I sometimes believe things you know. ;) * standard interface, so incompatibilities are easy to avoid, and are * avoided. issetugid() is a syscall with a new interface. It can't * possibly work with old kernels. Unfortunately, ex(1) uses it, at * least for the termcap script. It is surprising that it isn't used * more for `make world', since it is sometimes called by setlocale(). Hmm. So it breaks somewhere between 2.2.2 and 2.2.5? Sorry for being slow, why is it that people aren't complaining on -stable? There should be someone trying to build 2.2-stable on a 2.2.2 or 2.1.X system. At any rate, dying with issetugid() in termcap building (of all places) is sort of ingenious. I hope we can do something about it.... Satoshi From owner-freebsd-current Wed Oct 29 12:24:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11166 for current-outgoing; Wed, 29 Oct 1997 12:24:48 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA11157 for ; Wed, 29 Oct 1997 12:24:43 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xQefK-0000T7-00; Wed, 29 Oct 1997 12:24:34 -0800 Date: Wed, 29 Oct 1997 12:24:31 -0800 (PST) From: Tom To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: tcsh maxproc limit In-Reply-To: <199710290656.HAA13296@gil.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 29 Oct 1997, Christoph Kukulies wrote: > I had a limit maxproc 80 in my .login (tcsh) and since I moved a > 2.2.2 machine to -current I'm getting: > > limit: maxproc: Can't set limit > > 32 seems to be the limit I can set it to. Do I have to rebuild tcsh > or is it a different problem? You can't set the limit higher than the hard limit. It seems the sysadmin has set the hard limit to 32. > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > Tom From owner-freebsd-current Wed Oct 29 12:45:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12738 for current-outgoing; Wed, 29 Oct 1997 12:45:28 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA12722 for ; Wed, 29 Oct 1997 12:45:19 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id NAA18032; Wed, 29 Oct 1997 13:45:17 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd018001; Wed Oct 29 13:45:07 1997 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA19346; Wed, 29 Oct 1997 13:44:56 -0700 (MST) From: Terry Lambert Message-Id: <199710292044.NAA19346@usr07.primenet.com> Subject: Re: Small Problem with Linux Emul To: kmitch@weenix.guru.org (Keith Mitchell) Date: Wed, 29 Oct 1997 20:44:55 +0000 (GMT) Cc: tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <199710282039.PAA10601@weenix.guru.org> from "Keith Mitchell" at Oct 28, 97 03:39:08 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Use the BSDI quake server. It uses less CPU than the linux server, > > because it doesn't require add as much overhead. > > I would, but it is the 1.64 level server that crashes on half the maps I have > tried and also has quite a few bugs in it that have been fixed in the > 2.01 server (which only exists for linux/solaris). Plus doing that wouldn't get the Linux emulation bug fixed. Were those "ie:" number for "scrambled address" real numbers? If you can, you should convert them to hex, and look at the output of netstat -rn and arp -a to see if they are coming from a route, gateway, NATD or other IP address "translator", or if the hex values match the actual physical addresses, etc.. Probably it's one of those strange "raw packet" receives, and the FreeBSD flag values aren't the same as the Linux ones, and the stub in the emulator needs fixed. Or it could be a really hairy problem instead... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Oct 29 14:57:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22484 for current-outgoing; Wed, 29 Oct 1997 14:57:58 -0800 (PST) (envelope-from owner-freebsd-current) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA22479 for ; Wed, 29 Oct 1997 14:57:56 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA16083; Wed, 29 Oct 1997 15:54:20 -0700 (MST) From: Terry Lambert Message-Id: <199710292254.PAA16083@usr02.primenet.com> Subject: Re: bad system call - world build To: asami@cs.berkeley.edu (Satoshi Asami) Date: Wed, 29 Oct 1997 22:54:18 +0000 (GMT) Cc: phk@critter.freebsd.dk, mike@smith.net.au, helbig@Informatik.BA-Stuttgart.DE, freebsd-current@freefall.FreeBSD.org In-Reply-To: <199710290704.XAA16634@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Oct 28, 97 11:04:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * I may be dense here, but what do you think is the "real" solution ? > > I wouldn't be asking here if I knew. ;) > > Do you know why it doesn't work now? Your commit message appears to > indicate that this is supposed to work. Could the fact that the > environment variables are pointing to the newly built shared libraries > have something to do with this? (Just a wild guess.) I thought that if getcwd() returned ENOSYS, then the library fell back to the old code? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Oct 29 15:08:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA23248 for current-outgoing; Wed, 29 Oct 1997 15:08:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA23241 for ; Wed, 29 Oct 1997 15:08:47 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA16732; Wed, 29 Oct 1997 16:07:11 -0700 (MST) From: Terry Lambert Message-Id: <199710292307.QAA16732@usr02.primenet.com> Subject: Re: bad system call - world build To: asami@cs.berkeley.edu (Satoshi Asami) Date: Wed, 29 Oct 1997 23:07:10 +0000 (GMT) Cc: phk@critter.freebsd.dk, freebsd-current@freefall.FreeBSD.org In-Reply-To: <199710291108.DAA14491@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Oct 29, 97 03:08:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * I can't see any reason why make world should need to run any program > * that is linked to the newly compiled libc... And in that respect I > * think that most of your work is headed the wrong direction... > > That is because some of the tools required to build the world may need > functions that only exist in new libraries. It has always been that > way, I haven't changed it. I have to agree with Poul on this particular one. If you are depending on intermediate tools, then a cross-build is out of the question. Most likely, the intermediate tools should be targeted to the build environment, not the target environment. Better would be if there were no intermediate tools needed at all. > * I'm very willing to help, but only if we attack the correct problem: > * > * "How can I compile my FreeBSD sources on a foreign platform". > > Here you go again, throwing a smokescreen. I don't mind you planning > ahead, go ahead and think about it all you like. I will take that as > a "no", so please stop changing the subject. :( I agree with Poul on this one, too. This is the real problem; just because the architecture is the same, it's no less a cross-build. The getcwd() code already has to be able to fall back in the case that the data wasn't in cache in the kernel. The library wrapper should treat ENOSYS as this kind of failure as well, and the problem will go away. Now I'm kind of glad Poul rejected my suggestion to move the old code into the kernel... it leaves you an "out". But I still think that any code in your build tree should not be run unless it's installed. I had a bear of a time when the .mk file changes to use the "strip" feature of "ld" instead of just calling "strip". Now *that* was a gratuitous change, dwarfed only by assembly syntax changes (and those are GNU bugs, and are therefore out of our control). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Oct 29 15:53:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25959 for current-outgoing; Wed, 29 Oct 1997 15:53:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA25954 for ; Wed, 29 Oct 1997 15:53:24 -0800 (PST) (envelope-from bin@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14840 for current@freebsd.org; Thu, 30 Oct 1997 00:53:15 +0100 Received: (from bin@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id XAA02014 for current@freebsd.org; Wed, 29 Oct 1997 23:02:21 +0100 (MET) Date: Wed, 29 Oct 1997 23:02:21 +0100 (MET) From: Binaries Commands and Source Message-Id: <199710292202.XAA02014@uriah.heep.sax.de> To: current@freebsd.org Subject: LINT in -current doesn't compile Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DSPX_HACK -DSIMPLELOCK_DEBUG -DSI_DEBUG -DSCSI_2_DEF -DNPX_DEBUG -DLOCKF_DEBUG -DEXT2FS -DDEBUG -DCLUSTERDEBUG -DBOOTP_COMPAT -DBOOTP_NFSV3 -DBOOTP_NFSROOT -DBOOTP -DPOWERFAIL_NMI -DNATM -DLINT_PCCARD_HACK -DFDSEEKWAIT=16 -DNSWAPDEV=20 -DMFS_AUTOLOAD -DMFS_ROOT=10 -DDEVFS -DMSDOSFS -DLFS -DNQNFS -DNFS -DFFS -DIPDIVERT -DTCP_COMPAT_42 -DNETATALK -DIPTUNNEL -DIPXIP -DIPX -DINET -DDIAGNOSTIC -DMD5 -DCOMPAT_43 -DFAILSAFE -DKERNEL -include opt_global.h ../../net/if_fddisubr.c ../../net/if_fddisubr.c: In function `fddi_output': ../../net/if_fddisubr.c:230: too many arguments to function `at_ifawithnet' *** Error code 1 Stop. From owner-freebsd-current Wed Oct 29 17:00:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA00349 for current-outgoing; Wed, 29 Oct 1997 17:00:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA00344 for ; Wed, 29 Oct 1997 17:00:42 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA20057; Wed, 29 Oct 1997 16:50:43 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020055; Thu Oct 30 00:50:36 1997 Date: Wed, 29 Oct 1997 16:48:55 -0800 (PST) From: Julian Elischer To: Binaries Commands and Source cc: current@FreeBSD.ORG Subject: Re: LINT in -current doesn't compile In-Reply-To: <199710292202.XAA02014@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk fixed a few hours after being broken.. 1/ remove the 2nd arg, or 2/ grab a new copy of that file.. julian On Wed, 29 Oct 1997, Binaries Commands and Source wrote: > cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DSPX_HACK -DSIMPLELOCK_DEBUG -DSI_DEBUG -DSCSI_2_DEF -DNPX_DEBUG -DLOCKF_DEBUG -DEXT2FS -DDEBUG -DCLUSTERDEBUG -DBOOTP_COMPAT -DBOOTP_NFSV3 -DBOOTP_NFSROOT -DBOOTP -DPOWERFAIL_NMI -DNATM -DLINT_PCCARD_HACK -DFDSEEKWAIT=16 -DNSWAPDEV=20 -DMFS_AUTOLOAD -DMFS_ROOT=10 -DDEVFS -DMSDOSFS -DLFS -DNQNFS -DNFS -DFFS -DIPDIVERT -DTCP_COMPAT_42 -DNETATALK -DIPTUNNEL -DIPXIP -DIPX -DINET -DDIAGNOSTIC -DMD5 -DCOMPAT_43 -DFAILSAFE -DKERNEL -include opt_global.h ../../net/if_fddisubr.c > ../../net/if_fddisubr.c: In function `fddi_output': > ../../net/if_fddisubr.c:230: too many arguments to function `at_ifawithnet' > *** Error code 1 > > Stop. > From owner-freebsd-current Wed Oct 29 18:07:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04540 for current-outgoing; Wed, 29 Oct 1997 18:07:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA04530 for ; Wed, 29 Oct 1997 18:06:56 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 1671 invoked by uid 1000); 30 Oct 1997 02:07:21 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Wed, 29 Oct 1997 18:07:21 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: Are We Losing Interrupts? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'll, I noticed a problem for about 2-3 weeks now; At times, after the fsck -p in /etc/rc, the system simply stops. The symptoms, on the DPT driver are that the card delivers an interrupt but the driver never sees it. Dropping into the kernel debugger reveals nothing. The system is in default idle. The situation can be improved by power-cycling the machines. It happens on the same machine, with the same driver, that older kernels (last I have for sure is from 24-Aug but the problem is newer than than) have absolutely no problem with. It was verified on enough hardware of sufficient veriety to exclude hardware from the equation. The reason I suspect interrupt delivery is that I can monitor, via LEDs on the DPT that the interrupt was delivered, but the interrupt routine does not get called. Normally we observe a flurry of disk activity, and network activity immediately after fsck -p is done. This is exactly where it stops. Is this a hint? How do I research it some more? (not the obvious, this I have done :-) --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Wed Oct 29 18:07:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04560 for current-outgoing; Wed, 29 Oct 1997 18:07:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA04539 for ; Wed, 29 Oct 1997 18:07:01 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 1674 invoked by uid 1000); 30 Oct 1997 02:07:21 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Wed, 29 Oct 1997 18:07:21 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: Large Memory Panic - Reminder Requested Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Me Again, Equipped a system with 512MB of RAM, configured the kernel to knwo of such and booted: Panic: bounce buffers out of memory range I know this issue came before. I have trouble locating the patches and am not certain how pertinent they are to -current of today. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Wed Oct 29 18:07:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04567 for current-outgoing; Wed, 29 Oct 1997 18:07:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA04531 for ; Wed, 29 Oct 1997 18:06:56 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 1677 invoked by uid 1000); 30 Oct 1997 02:07:21 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Wed, 29 Oct 1997 18:07:21 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: dummy_mount - Who are you? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am getting, in df: /dev/sd0a 127134 121210 -4246 104% / devfs 32 32 0 100% dummy_mount procfs 8 8 0 100% /proc /dev/sd1s1a 127134 27310 89654 23% /tmp and the kernel complains, on a regular basis that it: cannot get superblock describing dummy_mount This last message is not in the logs (?) --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Wed Oct 29 18:49:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06651 for current-outgoing; Wed, 29 Oct 1997 18:49:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from bubble.didi.com (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06643 for ; Wed, 29 Oct 1997 18:49:33 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.7) id SAA02034; Wed, 29 Oct 1997 18:49:12 -0800 (PST) (envelope-from asami) Date: Wed, 29 Oct 1997 18:49:12 -0800 (PST) Message-Id: <199710300249.SAA02034@bubble.didi.com> To: bde@zeta.org.au, gurney_j@efn.org, freebsd-current@freefall.FreeBSD.org, peter@spinner.netplex.com.au In-reply-to: <199710292015.MAA29407@silvia.HIP.Berkeley.EDU> (asami@cs.berkeley.edu) Subject: Re: bad system call - world build From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Hmm. So it breaks somewhere between 2.2.2 and 2.2.5? Sorry for being * slow, why is it that people aren't complaining on -stable? There * should be someone trying to build 2.2-stable on a 2.2.2 or 2.1.X system. Actually, my question should have been: why does it work if you build 3.0-current on 2.2-stable (as of now)? I just confirmed that I can build 3.0 on my 2.2-stable machine, can build 2.2-stable on 2.1.5R but not 3.0-current on 2.1.5R. (I don't have 2.2.2R.) Satoshi From owner-freebsd-current Wed Oct 29 20:00:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10970 for current-outgoing; Wed, 29 Oct 1997 20:00:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA10963 for ; Wed, 29 Oct 1997 20:00:13 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id OAA00720; Thu, 30 Oct 1997 14:29:58 +1030 (CST) Message-ID: <19971030142957.40703@lemis.com> Date: Thu, 30 Oct 1997 14:29:57 +1030 From: Greg Lehey To: Mike Smith Cc: Poul-Henning Kamp , Ron Bolin , FreeBSD Current Mailing List Subject: Re: StarOffice on 3.0 current References: <558.878066854@critter.freebsd.dk> <199710291428.AAA00928@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84e In-Reply-To: <199710291428.AAA00928@word.smith.net.au>; from Mike Smith on Thu, Oct 30, 1997 at 12:58:52AM +1030 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 30, 1997 at 12:58:52AM +1030, Mike Smith wrote: >> In message <345629C0.134062C9@mindspring.com>, Ron Bolin writes: >>> Well I found some more info on my problem. Thanks to those that >>> suggested >>> several problem areas. >>> >>> I found that SO is sitting on a select call, waiting for something. >>> After about 10 minutes >> >> DNS, no doubt. >> >> Any linux emulation people who can tell what to do ? > > There appear to be some DNS-related problems with Linux emulation and > -current. It's possible that the resolver in the current linux-lib kit > requires some more careful configuration. I don't think that configuration is enough. There's some bug in there. > Make sure that you have /compat/linux/etc/host.conf and /compat/linux/ > etc/resolv.conf set up just for starters. OK. I have: /compat/linux/etc/host.conf: order hosts, bind multi on /compat/linux/etc/resolv.conf: domain lemis.com nameserver freebie.lemis.com nameserver allegro.lemis.com When I start swrite3, I get: === root@freebie (/dev/ttyp3) /var/log 31 -> tcpdump -i lo0 tcpdump: listening on lo0 14:22:54.314055 freebie.lemis.com.vpac > freebie.lemis.com.domain: 38277+ A? freebie.lemis.com. (35) 14:22:54.315149 freebie.lemis.com.domain > freebie.lemis.com.vpac: 38277* 1/3/3 (173) 14:22:55.199337 localhost.lemis.com.vpvd > localhost.lemis.com.domain: 638+ (46) 14:22:55.200375 localhost.lemis.com.domain > localhost.lemis.com.vpvd: 638* 1/3/3 (214) 14:22:56.305923 localhost.lemis.com.vpvc > localhost.lemis.com.domain: 639+ (40) 14:22:56.306661 localhost.lemis.com.domain > localhost.lemis.com.vpvc: 639* 1/2/2 (169) 14:22:59.336849 freebie.lemis.com.atm-zip-office > freebie.lemis.com.domain: 38277+ A? freebie.lemis.com. (35) 14:22:59.337906 freebie.lemis.com.domain > freebie.lemis.com.atm-zip-office: 38277* 1/3/3 (173) 14:23:09.354423 freebie.lemis.com.ncube-lm > freebie.lemis.com.domain: 38277+ A? freebie.lemis.com. (35) 14:23:09.355234 freebie.lemis.com.domain > freebie.lemis.com.ncube-lm: 38277* 1/3/3 (173) 14:23:29.372461 freebie.lemis.com.rna-lm > freebie.lemis.com.domain: 38277+ A? freebie.lemis.com. (35) 14:23:29.373271 freebie.lemis.com.domain > freebie.lemis.com.rna-lm: 38277* 1/3/3 (173) It would appear that the messages from localhost belong there, though I can't work out what they're doing, but it's equally obvious that messages are being sent to the name server, and that it's replying. More detailled examination shows that the data returned are correct. Obviously this isn't a resolv.conf question: it's found out where to send the requests, but it looks as if it can't interpret the results. Later it goes on to look for freebie.lemis.com.lemis.com, a sure sign that it didn't get the answer it wanted the first time round: 14:29:20.577688 freebie.lemis.com.vistium-share > freebie.lemis.com.domain: 38282+ A? freebie.lemis.com.lemis.com. (45) 4500 0049 6fe9 0000 * 4011 0fdc d17d d699 E~~Ioé~~@~ÿÌÁmÆ~ d17d d699 0609 0035 * 0035 7dfe a69a 0100 ÁmÆ~~~~5~5}þ~~~~ 0001 0000 0000 0000 * 0766 7265 6562 6965 ~~~~~~~~~freebie 056c 656d 6973 0363 * 6f6d 056c 656d 6973 ~lemis~com~lemis 0363 6f6d 0000 0100 01 ~com~~~~~ 14:29:20.578201 freebie.lemis.com.domain > freebie.lemis.com.vistium-share: 38282 NXDomain* 0/1/0 (103) 4500 0083 6fea 0000 * 4011 0fa1 d17d d699 E~~~oê~~@~ÿ~ÁmÆ~ d17d d699 0035 0609 * 006f 0d82 a69a 9693 ÁmÆ~~5~~~oýr~~~~ 0001 0000 0001 0000 * 0766 7265 6562 6965 ~~~~~~~~~freebie 056c 656d 6973 0363 * 6f6d 056c 656d 6973 ~lemis~com~lemis 0363 6f6d 0000 0100 * 0105 6c65 6d69 7303 ~com~~~~~~lemis~ 636f 6d00 0006 0001 * 0001 5180 0025 0766 com~~~~~~~Q~~%~f 7265 6562 6965 d13d * 0467 726f 67c0 2d05 reebieÁ-~grogÀ-~ dabb 0900 0151 8000 * 001c 2000 94e6 0000 Ê«~~~Q~~~~ ~~Ö~~ 0151 80 ~Q~ Greg From owner-freebsd-current Wed Oct 29 20:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10999 for current-outgoing; Wed, 29 Oct 1997 20:00:28 -0800 (PST) (envelope-from owner-freebsd-current) Received: from thelab.hub.org (ppp-001.m4-1.hal.ican.net [142.154.180.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA10986 for ; Wed, 29 Oct 1997 20:00:23 -0800 (PST) (envelope-from scrappy@hub.org) Received: from thelab.hub.org (localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id XAA01011; Wed, 29 Oct 1997 23:59:05 -0400 (AST) Date: Wed, 29 Oct 1997 23:59:04 -0400 (AST) From: The Hermit Hacker To: Kenneth Merry cc: Alex , current@FreeBSD.ORG Subject: Re: rc5 client under -current In-Reply-To: <199710290621.XAA29894@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 Oct 1997, Kenneth Merry wrote: > I tried it out with a kernel from October 26th on my SMP box; I ran > two copies of it simultaneously without a problem. (I was trying to > reproduce PR kern/4859. The guy who filed that PR was running > 3.0-971002-SNAP.) > > If you're having trouble with it, I'd suggest getting newer > sources, since it doesn't seem to be a problem now. Did it tonight and all runs great. Seems to have just been an old kernel. Thanks to all... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-current Wed Oct 29 20:29:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA12846 for current-outgoing; Wed, 29 Oct 1997 20:29:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA12839 for ; Wed, 29 Oct 1997 20:29:33 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id PAA12612; Thu, 30 Oct 1997 15:24:25 +1100 Date: Thu, 30 Oct 1997 15:24:25 +1100 From: Bruce Evans Message-Id: <199710300424.PAA12612@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, bde@zeta.org.au, freebsd-current@freefall.FreeBSD.org, gurney_j@efn.org, peter@spinner.netplex.com.au Subject: Re: bad system call - world build Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Actually, my question should have been: why does it work if you build >3.0-current on 2.2-stable (as of now)? I just confirmed that I can 2.2-"stable" has issetugid() in the kernel. >build 3.0 on my 2.2-stable machine, can build 2.2-stable on 2.1.5R but >not 3.0-current on 2.1.5R. (I don't have 2.2.2R.) That is because of a missing features in 2.2-"stable". It doesn't actually use issetugid() in libc/gen/glob.c, libc/nls/msgcat.c or libtermcap/termcap.c, although it uses it in libc/locale/setlocale.c and libc/locale/setrunelocale.c For libtermcap there is also a library version numbering problem. libtermcap.so's linked to libc.so.2.2 can't expect to find issetugid() in libc even if the kernel has it. This was fixed in -current by bumping the _major_ number of libtermcap. Bruce From owner-freebsd-current Wed Oct 29 20:50:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13652 for current-outgoing; Wed, 29 Oct 1997 20:50:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13639 for ; Wed, 29 Oct 1997 20:50:34 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA24967; Wed, 29 Oct 1997 20:42:07 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd024956; Thu Oct 30 04:42:01 1997 Date: Wed, 29 Oct 1997 20:40:19 -0800 (PST) From: Julian Elischer To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG Subject: Re: dummy_mount - Who are you? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ahh yes, This is the kernel's internal mounting of the devfs. I had thought I had not exported the line of code that actually does this, but it appears that it slipped past me.. The DEVFS is mounted internally to the kernel. You cannot get to it. (hense the name..'hidden mount' might be a better name) This is not needed yet, but will be soon. I don't see that error message, but are you sure it's the KERNEL giving that message? All is ok, it's just htat I didn't realise that I'd exported that 'feature' yet. I'll look into it later tonight. "don't Panic" On Wed, 29 Oct 1997, Simon Shapiro wrote: > I am getting, in df: > > /dev/sd0a 127134 121210 -4246 104% / > devfs 32 32 0 100% dummy_mount > procfs 8 8 0 100% /proc > /dev/sd1s1a 127134 27310 89654 23% /tmp > > and the kernel complains, on a regular basis that it: > > cannot get superblock describing dummy_mount > > This last message is not in the logs (?) > > > --- > > > Sincerely Yours, > > Simon Shapiro Atlas Telecom > Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 > Shimon@i-Connect.Net Voice: 503.799.2313 > From owner-freebsd-current Wed Oct 29 22:33:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18646 for current-outgoing; Wed, 29 Oct 1997 22:33:41 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18641 for ; Wed, 29 Oct 1997 22:33:38 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id HAA01206; Thu, 30 Oct 1997 07:32:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: asami@cs.berkeley.edu (Satoshi Asami) cc: gurney_j@resnet.uoregon.edu, peter@spinner.netplex.com.au, freebsd-current@freefall.FreeBSD.org Subject: Re: bad system call - world build In-reply-to: Your message of "Wed, 29 Oct 1997 12:01:45 PST." <199710292001.MAA29347@silvia.HIP.Berkeley.EDU> Date: Thu, 30 Oct 1997 07:32:16 +0100 Message-ID: <1204.878193136@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710292001.MAA29347@silvia.HIP.Berkeley.EDU>, Satoshi Asami write s: > * I looked at the diffs between 2.2.1 and 2.2.5, and it looks like the > * call that we might be hitting is the new issuid... I KNOW that this > * was before the getcwd syscall was added... (haven't you gotten my last > * few posts on the subject??)... termcap building failed on a buildworld > * around late august which is before the getcwd syscalls... > >Aww. Sorry, I thought it was getcwd() because everyone was saying so. > >That's what I get for sticking my head into something I'm not familiar >with. Sorry, Poul-Henning. ;) That's OK, I guess we're closer to even now :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Wed Oct 29 23:36:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21275 for current-outgoing; Wed, 29 Oct 1997 23:36:02 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sinbin.demos.su (sinbin.demos.su [194.87.5.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA21240 for ; Wed, 29 Oct 1997 23:35:56 -0800 (PST) (envelope-from bag@sinbin.demos.su) Received: by sinbin.demos.su id KAA09980; (8.6.12/D) Thu, 30 Oct 1997 10:35:03 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199710300735.KAA09980@sinbin.demos.su> Subject: Re: Small Problem with Linux Emul In-Reply-To: <199710292044.NAA19346@usr07.primenet.com> from "Terry Lambert" at "Oct 29, 97 08:44:55 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: tlambert@primenet.com (Terry Lambert) Date: Thu, 30 Oct 1997 10:35:02 +0300 (MSK) Cc: kmitch@weenix.guru.org, tom@uniserve.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Use the BSDI quake server. It uses less CPU than the linux server, > > > because it doesn't require add as much overhead. > > > > I would, but it is the 1.64 level server that crashes on half the maps I have > > tried and also has quite a few bugs in it that have been fixed in the > > 2.01 server (which only exists for linux/solaris). > > Plus doing that wouldn't get the Linux emulation bug fixed. we succesfully used 2.0 server with linux emulator before Sep 97 after some changes in -current kernel in Sep server starts, but have no connection ... now it not work in 3.0-971012-SNAP ... Alex. > > Were those "ie:" number for "scrambled address" real numbers? > > If you can, you should convert them to hex, and look at the output > of netstat -rn and arp -a to see if they are coming from a route, > gateway, NATD or other IP address "translator", or if the hex values > match the actual physical addresses, etc.. > > Probably it's one of those strange "raw packet" receives, and the > FreeBSD flag values aren't the same as the Linux ones, and the stub > in the emulator needs fixed. > > Or it could be a really hairy problem instead... 8-(. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-current Thu Oct 30 00:44:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA25322 for current-outgoing; Thu, 30 Oct 1997 00:44:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA25317 for ; Thu, 30 Oct 1997 00:44:47 -0800 (PST) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.7/8.7.3) id JAA00974 for freebsd-current@freebsd.org; Thu, 30 Oct 1997 09:44:45 +0100 (MET) From: Holm Tiffe Message-Id: <199710300844.JAA00974@magnet.geophysik.tu-freiberg.de> Subject: Guys, what is happening with DNS and Linux-Emu ? To: freebsd-current@freebsd.org Date: Thu, 30 Oct 1997 09:44:44 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, There are currently 2 threads about this problem ("Star Office on 3.0 current" and "Small Problem with Linux Emul") in -current. I've noticed, that DNS resolving under the Linux-Emu on my machines with -current i'nt working since 08/20/97. I've reinstalled the linux_lib, double checked the files in /compat/linux/etc and so on. One of my machines is an SMP P6 with applixware installed, this machine has had a working DNS with a -current from 08/15/97 until I've updated this roadrunner to -current. (10/28/97) Because of this, I think, bad config files in /compat/linux/etc could'nt be the trigger of this problem. The DNS in the FreeBSD "universe" is working flawlessly. The nameserver get the question and I think it replays ok. But the results semms to be not interpreted correctly... The only person I know who has a -current with a working DNS seems to be Søren Schmidt . Any suggestions ? Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Strasse der Einheit 26 * * 09599 Freiberg Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* From owner-freebsd-current Thu Oct 30 05:49:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA09374 for current-outgoing; Thu, 30 Oct 1997 05:49:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA09368 for ; Thu, 30 Oct 1997 05:49:46 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA27541; Fri, 31 Oct 1997 00:19:43 +1030 From: Kristian Kennaway Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA01649; Fri, 31 Oct 1997 00:19:42 +1030 Message-Id: <9710301349.AA01649@bragg> Subject: Crappy modem upload bandwidth To: freebsd-current@freebsd.org (FreeBSD Current) Date: Fri, 31 Oct 1997 00:19:42 +1030 (CST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For the past week or so I've been plagued by a strange problem which I'd been unable to track down until tonight: I'm getting exceedingly bad upload speeds from my 14.4k modem (i.e. sending from my computer to the world). Downloading is fine, and I get the expected 1.3k+/second download rates, but it slows to an average of like 50 bps when I try and upload. What seems to happen is that the modem sends in very short bursts "bursts" at close to full-speed, then idles for a minute or more before doing the next one. Before this happened, I had no problems uploading from my computer.. This is causing problems with trying to do things like cvsup (it sends out about 180 protos, and then sits there doing nothing for the next 10-15 minutes before dying with a "Detailer failed: Premature EOF from server". I was running current from about Oct 21 or before when I first noticed the problem - I've just downloaded the entire src tree from the 27th, make world'ed and made a new kernel, but the problem hasnt gone away. Is this likely to be a problem with the OS, or a hardware problem with my modem? Kris From owner-freebsd-current Thu Oct 30 06:16:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10886 for current-outgoing; Thu, 30 Oct 1997 06:16:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10864 for ; Thu, 30 Oct 1997 06:16:36 -0800 (PST) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id JAA08987; Thu, 30 Oct 1997 09:16:00 -0500 (EST) From: Keith Mitchell Message-Id: <199710301416.JAA08987@weenix.guru.org> Subject: Re: Small Problem with Linux Emul In-Reply-To: <199710292044.NAA19346@usr07.primenet.com> from Terry Lambert at "Oct 29, 97 08:44:55 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 30 Oct 1997 09:15:59 -0500 (EST) Cc: current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Plus doing that wouldn't get the Linux emulation bug fixed. > > Were those "ie:" number for "scrambled address" real numbers? > > If you can, you should convert them to hex, and look at the output > of netstat -rn and arp -a to see if they are coming from a route, > gateway, NATD or other IP address "translator", or if the hex values > match the actual physical addresses, etc.. I converted them to hex, but they didn't match anything in arp or netstat. The port number comes back garbled too. 192.246.40.12:27003 comes back as 232.212.191.239:49135 (E8.D4.BF.EF) -or sometimes- 216.142.4.8:49135 (D8.8E.04.08) The ip address that actually comes back is not always the same either. The port number does seem to reamin the same though. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch From owner-freebsd-current Thu Oct 30 06:21:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA11245 for current-outgoing; Thu, 30 Oct 1997 06:21:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA11235 for ; Thu, 30 Oct 1997 06:21:16 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA01090 for ; Fri, 31 Oct 1997 00:47:43 +1030 (CST) Message-Id: <199710301417.AAA01090@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@freebsd.org Subject: Staying -current with FreeBSD (rev 2) Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-13658490450" Date: Fri, 31 Oct 1997 00:47:41 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multipart MIME message. --==_Exmh_-13658490450 Content-Type: text/plain; charset=us-ascii Thanks to everyone for the suggestions; sorry for the lag in getting this version out. Again, any comments, expansions, extra text, etc. would be appreciated. Please circulate, photocopy, fax, xerox, mimeo, steno, staple, tack, glue, or otherwise forward this anywhere you think it may either help or receive commentary. Thanks. Mike --==_Exmh_-13658490450 Content-Type: text/plain; name="sc"; charset=us-ascii Content-Description: sc Content-Disposition: attachment; filename="sc" Staying -current with FreeBSD r2 ====================================================================== Maintained by Mike Smith FreeBSD-current represents the bleeding edge of FreeBSD development. It's where all the new features, performance improvements and bugfixes are unleashed on the user community. If you are interested in developing for FreeBSD, or just want the heady thrill of getting all the latest stuff first, -current is what you want. FreeBSD-current changes daily, and like any new product it goes through patches of instability and unreliability. This is part and parcel of using -current; if you don't think you can deal with it, now is a good time to opt out. A -release or -stable version will still give you excellent service, and with greatly improved dependability. However, there are a lot of people that do run FreeBSD-current, and many use nothing else. If you are serious about contributing to ongoing FreeBSD development, you may need to run -current too. In order to help new -current users, and old ones with bad habits, this is a guide to getting along with FreeBSD-current. If you're having problems, check here first because if you don't, you may find your (quite valid) complaint ignored simply because there's not enough information for anyone to do anything about it, and you just might find the information you need to get you going again. Notes ----- If you're going to be running FreeBSD-current, it's assumed that you are reasonably familiar with FreeBSD. No attempt will be made here to explain basic operating procedure or commands; if this sounds too complicated then it probably is. Command examples here should work with any shell. Where there are potential differences, an example of each form will be given. Preparation ----------- If you are not subscribed to the FreeBSD-current mailing list, you should do this first. Running -current and not reading the mailing list is like driving at night with duct tape over your eyes and jellybeans in your ears; ie. not a good idea. Another mailing list worth subscribing to is the cvs-all list. Every change made to the FreeBSD source tree is accompanied by a mail message sent to this list. These messages contain the name(s) of the file(s) affected, the name of the person making the change, and a description of the change itself. Reading this list can provide you with valuable insight into the directions that -current is taking, as well as advance warning of possible problems or fixes. There are other cvs-* lists which may be more suitable, depending on your field of interest. Read the -current mailing list for a few days before starting with FreeBSD-current; it's possible that you might have picked a really bad time to start. If there are problems, people will be discussing them; wait for a resolution to be announced, or for other people to indicate that the problem has been solved. If you're not sure after a few days, post a short message asking whether people think that it's OK to go ahead. As you become more familiar with the atmosphere and the people on -current, you will learn to judge what constitutes "really bad" and what is merely "interesting". Remember that while FreeBSD-current is a development environment, the desired result is indeed a stable platform and if something is broken people will be working to fix it. Starting -------- Once you're subscribed to the -current mailing list, there are a couple of different ways to get FreeBSD-current onto your system. Which is best for you will depend on your circumstances. - FTP: You can install a FreeBSD-current snapshot via FTP just like a release version. FreeBSD-current snapshots are normally built daily and can be downloaded from ftp://current.freebsd.org/. When installing you can either start from scratch, or upgrade an existing system. - CDROM: Walnut Creek CDROM occasionally release a FreeBSD-current snapshot CDROM, and other vendors may too. These are generally a bargain, as they come with a copy of the CVS repository which can save you a lot of download time. You can install from a snapshot CDROM in exactly the same fashion as you would a release version. Be careful though; a snapshot more than a few months old may be just as tough to upgrade from as a previous release. - Bootstrap: If you have the FreeBSD CVS repository on your system you can checkout a copy of the -current source tree and bootstrap a previous release system. You can also get the -current source using CVSup or CTM (see below). Bootstrapping may take a little perseverance, but that's good practice for later. Note that bootstrapping from anything older than the most recent release is something best left to the truly adventurous. If you have problems bootstrapping and really can't get -current going any other way then you should post a concise message to the FreeBSD-current mailing list clearly detailing what you are trying to do, the release you are bootstrapping from and any error messages that you receive during the process. Keeping -current ---------------- Once you have a -current system up and running, congratulations, it's obsolete! FreeBSD-current changes daily, and part of running a -current system is keeping up to date. There are two parts to keeping your system -current; getting the source, and building it. You can obtain the source in two forms; either the raw source tree, or the CVS repository. The former requires around 200MB of disk space, the latter perhaps twice times that; expect these values to grow with time. The raw source tree is all that's required to build the source, however the CVS repository is useful if you are interested in tracking or becoming involved with development. In particular, the CVS repository can be invaluable if you are trying to locate a new problem. There are two distribution strategies in common use for keeping your source up to date, named after the tools used to perform the updating: CVSup and CTM. CVSup ''''' CVSup replaces an older tool, 'sup' (the Source Update Protocol), and is the preferred method for tracking the -current source tree. It requires an active network connection and provides guaranteed-accuracy updates of your CVS repository or checked-out source tree. CVSup can also repair a damaged or modified repository or tree. If you have a -stable or -current system up and running, sample control files for CVSup are located in /usr/share/examples/cvsup. You can get CVSup itself from the FreeBSD ports collection. CTM ''' CTM can be interpreted as 'CVS Thru eMail'; it provides updates for your CVS repository or source tree via email messages. CTM is ideal if your network connection is indirect, expensive or otherwise cannot support CVSup. Documentation for the CTM programs is included with the system, start with 'man ctm', and check the handbook for more details. Checking out with CVS ''''''''''''''''''''' If you are fetching the CVS repository there is one important step required before you can build anything. This is known as "checking out" the source; literally you will generate a complete copy of the -current source tree from the information in the repository. The source tree can be anywhere, but the intermediate files generated during the build will be placed under /usr/obj. If the filesystem containing /usr doesn't have ~150MB of free space, you will need to create a directory elsewhere and use a symbolic link. To check out the source tree, go to where the 'src' directory is to be located and set the CVSROOT environment variable to point to the location of your CVS repository. Using a csh-like shell: # setenv CVSROOT or with an sh-like shell: # export CVSROOT= Then issue the command: # cvs checkout src This will create a directory 'src' and populate it with the source tree. When the repository is updated by CVSup or CTM you can propagate the changes to this source tree by making the src directory your current directory and saying: # cvs update -Pd If you have been making changes to your source tree, CVS will try to merge these changes with any updates it makes. You should watch the output from the update command and note any merges; these should be checked before you go any further to make sure they won't cause any problems. Identifying these merges is easier if you make CVS run quieter, eg. # cvs -q update -Pd If in doubt, remove the file(s) in question and rerun the update, which will replace them with fresh copies. Building the World '''''''''''''''''' Once you have your source tree checked out, make sure the 'src' tree is reachable as /usr/src, become root and change to the /usr/src directory. Now is the time to select your build options. If you've built the FreeBSD tree before, you will be familiar with these. Options are set via environment variables, by editing /etc/make.conf, or by passing them on the commandline when you build the tree. We will use the last method here. To set an option when invoking 'make', specify its name as an argument to the '-D' option, ie. to set the option VARIABLE, you would add '-DVARIABLE' to the 'make' commandline. The common variables and their uses are: NOCLEAN Do not clean out the old build tree. This can save on build time, but may introduce subtle problems. NOSECURE Do not build the export-restricted modules. If you haven't downloaded the source for these, then you won't want to try to build them. This is a good option to use if you are not in the USA. NOGAMES Don't rebuild the games. If you don't have or want them installed, set this. NOSHARE Don't rebuild /usr/share. This can save some time, and if /usr/share (containing manpages, data files and examples) hasn't changed much it won't cause you any trouble. NOPROFILE Don't build the profiling libraries. If you're not doing any development involving profiling, this can save a considerable amount of time and space. If you don't know what profiling libraries are, you don't want them. Once your options are set, start the build. It's generally a good idea to keep a record of the build, in case there are problems and you want to look over it. There are two good ways to do this. The first uses the 'script' command, which arranges a transcript of a session. You would say: # script Script started, output file is typescript # make world When the build has finished, use 'exit' to close the script. The second method runs the build in the background, and watches it with the 'tail' command. The advantage of this method is that you can let the build run without having to watch it all the time; you can come back to check on it at your leisure. To do this, you would say: # make world >& makelog & # tail -f makelog You can hit ^C at any time to exit the 'tail' command, and then reissue it whenever you want to check on the build. A world build transcript generated like this will generally be around the 7 megabyte mark; you should make sure you have space for it. If you are unsure about whether the build will work, and would prefer to make sure it builds properly before allowing it to install over your running system, you can use the 'buildworld' rather than 'world' target. This will compile everything, but not install it. Once you are happy that the build has completed OK, you can invoke the 'installworld' target, which will install the built world. If your 'buildworld' is failing on something that you think is trivial you can add the '-k' option to the make command. This will cause make to continue after an error, rather than stopping the build. If you have built with '-k' you should examine the build log very carefully before proceeding to install, as it is possible to make an enormous mess like this. Building the Kernel ''''''''''''''''''' Changes in -current often require coordinated rebuilding of both the 'world' (userland) and the kernel. Normally you should build a new kernel after you have built the world, but before you reboot. There are a couple of important points to bear in mind regarding the kernel: - The 'config' program is closely tied to the kernel. It is normally built as part of userland, but it can also be built manually with # cd /usr/src/usr.sbin/config # make depend all install clean clendepend Using an outdated 'config' program can cause strange errors when configuring or building a kernel, althought 'config' does its best to determine whether it is out of date and complain accordingly. - The kernel and LKMs are closely related. Mismatches can cause fatal kernel errors or strange behaviour. LKMs are also built as part of userland, but can be regenerated and reinstalled with # cd /usr/src/lkm # make depend all install clean cleandepend Note that both of these examples assume that your source tree is under /usr/src; if you've put it elsewhere, adjust them accordingly. Changes to -current may require matching changes in your kernel configuration file. These are normally reflected in changes to the LINT or GENERIC files, and/or described in messages posted to the mailing list. Once the kernel has been built and installed, reboot the system. It is generally a good idea to do this at this point, in order to ensure that the running kernel and userland programs correspond. When Things go Wrong -------------------- Problems with FreeBSD-current can generally be divided into three groups: - It won't build. - It won't boot. - Something funny happens when... It won't Build '''''''''''''' If it won't build, and the reason isn't immediately obvious, there are several steps you should take. Always remember to go through these in order; skipping them may miss the problem. In some cases, the only remedy is to wait for someone to fix the problem before you can go on. - Completely remove the object tree and start again. You can do this with: # chflags -R noschg /usr/obj/ # rm -rf /usr/obj/* Normally the 'world' target will do this for you, unless you have NOCLEAN or one of the related non-cleaning options set. The 'chflags' command removes the system-immutable flag which is set on some of the intermediate files generated during the build process. This flag renders files unchangable (and undeletable) as a security and safety measure. Its use on intermediate files can be considered a 'feature'. - If you have a local copy of the CVS repository, completely remove the source tree, check out a new copy and try building it again. Make sure you make a backup of your kernel configuration files before doing this. - Update your local sources, either by waiting for the next CTM mail, or re-running CVSup. If you are using a local CVS repository don't forget to update the checked-out soruce tree with the 'cvs update' command described above. It is possible that your last update came in the middle of a compound change to the source tree, and that updating is all it will take to correct the problem. - Wait a day or two, and watch the mailing list for messages about your problem. If the problem is widespread (ie. not a result of local circumstances) then other people will have encountered it, and a fix is likely to be discussed rapidly. While you are waiting, try investigating the problem yourself. The build process isn't magic, and the error messages are emitted when it fails can often provide you with helpful clues. If you think you have found a problem, try fixing it yourself. If you are using a local CVS repository or CVSup and you make a mess of a file, just delete it and update again; the file will be magically replaced. You need to be a bit more careful if you are fetching the source tree directly with CTM. - If you cannot obtain a clean build after a couple of days of watching the list and updating your source tree, you should post a message to the -current list describing your problem. It is extremely important that you provide enough information to diagnose your problem; without this information your post is likely to be ignored because it represents a great deal of work. At the very least, your post should include: x The last update date of your source tree. If you are using CVSup, the time at which you last ran CVSup, and the server you updated from. If you are using CTM, the number of the last CTM delta that you have applied. x An excerpt from the the end of the build transcript above. Try to include the last few lines of commands before the "error 1" lines, as these will generally contain information needed to locate the problem. x A list of all the build options that were enabled. You may be asked for additional information, or to try various things; be prepared to become involved in solving your problem, and look to learn from the experience. In time, you may be able to apply the solutions you have discovered to someone else's problem, and in turn help them out. It Won't Boot ''''''''''''' Occasionally you will encounter a newly-built kernel that won't boot. "Won't boot" may mean that it produces a panic message, or a fatal trap while starting up, or the system may freeze up, or reboot spontaenously. There can be a number of reasons for these failures; the two most common are: - You have stale LKMs. - A new change to the kernel is broken. You should always check for an LKM problem before suspecting that the kernel is broken. It is easy to check whether you have such a problem: - Boot single-user (specify '-s' at the boot: prompt) - Mount the root filesystem read/write: # mount / - Move the LKM directory out of the way: # mv /lkm /lkm.bad - Continue to multi-user: # exit If this fixes your problem, then you should remove all of the old LKMs, and install a new set. This can be achieved with: # mv /lkm.bad /lkm # rm -rf /lkm/* # cd /usr/src/lkm # make depend all install clean cleandepend Note that both this technique and the one above for config may make temporary files in the source tree; this is dirty but expedient. If the kernel doesn't get to the single-user stage, or if it still fails, then it is likely that the kernel is broken. You should boot the backup kernel, which is a copy of the previous kernel which was made when you installed the new one. This is achieved by entering the name of the backup kernel at the 'boot:' prompt; it's normally called 'kernel.old'. If you are experimenting with new kernels, you will want to make another backup, as everytime you install a kernel the backup is overwritten with the current kernel; two bad kernels in a row would leave you unable to boot. You can copy the backup kernel over the newer kernel with the commands: # chflags noschg /kernel # cp /kernel.old /kerne # chflags schg /kernel Once you have your system up and running again in this fashion, you should again keep an eye on the FreeBSD-current mailing list. It's possible that your problem will already have been noticed, and a fix may have been made already. If your problem persists after several days and several rebuilds, you can participate in tracking it down as follows. It is important to provide a lot of information about kernel problems, as they can be very subtle. You should build a kernel with the debugger enabled, ie. with options DDB in the configuration file. Ideally, the kernel should be configured with the '-g' flag to config, and installed in this form. Be aware that this will result in a kernel that may be up to 10 megabytes in size, as it includes copious debugging information. When the system panics, or encounters a trap, it will print a message giving details of the panic or trap, and leave the system in the debugger at the 'ddb>' prompt. At this point, you should make a note of all of this information. It is important that you do this, as it identifies the basic nature of the problem, its location and the state of the system when the problem occurred. You should then issue the 'trace' command to ddb, and note all of its output. This provides more vital information as to the state of the system. Armed with this information, you are ready to post to the FreeBSD-current mailing list. You should include in your message: - The trap/panic message and 'trace' output. - The last update date/CTM number from which the kernel was built. - Your hardware configuration details. - The kernel configuration file from which the kernel was generated. - The activity which causes the problem (booting, heavy load, etc.) If your problem is due to a fault which is triggered by your system configuration or load profile you may be asked to try making changes to the source in order to locate a suitable fix. These changes are often provided in the form of patches, which are discussed below. There is a lot more that you can do with a debugging-enabled kernel; see the online handbook for more details on this. Something Funny happens When... ''''''''''''''''''''''''''''''' You may notice that the new kernel or userland doesn't behave 'quite right'. A command may behave differently, or the system may not respond as it did previously under some circumstances. In the worst case, you may find that the kernel may panic or encounter a fatal trap. Under these circumstances, it is important to characterise the nature of the fault. This means that you should attempt to establish, by trial and error, exactly what it is that is causing the problem to manifest. It may be a combination of arguments to a command; a particular sort of system load, or any of many other things. If the system is panicing or stopping on a trap, build and install a kernel with DDB and preferably debugging enabled as above. Otherwise, gather as much information about the problem and any identified causes for it, and watch the FreeBSD-current mailing list. If the problem isn't discussed after a couple of days, post your findings. As always, provide as much information as you believe may be relevant, and be prepared to become involved in finding the solution. How Often? ---------- Now you are running -current, how often should you update? This will depend on your personal schedule, the load and demand on your system, and the general health of -current. In general once a week is a good number if you are keen to keep up to date. Once a month is good if you want to avoid falling too far behind. Another alternative is to wait for a few days after a new major feature of interest is announced, to make sure it is stable and worthwhile. Wrapup ------ FreeBSD-current can be a rewarding and useful environment. Users of -current provide vital feedback to the developer community, who in turn depend on this feedback as a check on their work. -current users must be prepared to work with developers in the pursuit of a stable, reliable, high-performance system, and in turn developers must work with users towards the same goals. Using -current can be a lot more work than a release or -stable version, but the rewards: - Improved performance. - New features and fixes, sooner. - A sense of directly contributing to the ongoing development of FreeBSD. can be well worth the effort. Patching it Up (sidebar) -------------- When you are chasing a problem with your -current system, or if you want to try out something so new that it hasn't been added yet, you may encounter 'patch' or 'diff' files. Often someone will send you one saying "here, try this". These files contain information which allows you to make automated changes to your source tree. They are fed as input to the 'patch' program, usually as: # patch -p < It is important to be in the correct directory when applying a patch. If you can't establish this from the details at the top of the patch file, be sure to ask the author. You can check that a patch will apply by supplying the '-C' option to patch; if any parts are rejected, the patch will not apply cleanly. Note that if you apply a patch to your source tree, CTM will no longer be able to update the file(s) patched. The patch program makes a backup of patched files with the suffix '.orig'; after you have tested a patch you may wish to move these files back to their original names. If you are using a CVS repository, CVS will try to merge your patched changes with new changes to the repository. This can occasionally result in files that cannot be used to build from, as they contain merge comments. The easiest way to deal with such a file is to delete it and then say: # cvs update -Pd If you are using CVSup to update your source tree directly, it will replace any patched files with the current version when you update. --==_Exmh_-13658490450-- From owner-freebsd-current Thu Oct 30 07:29:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15094 for current-outgoing; Thu, 30 Oct 1997 07:29:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15085 for ; Thu, 30 Oct 1997 07:29:23 -0800 (PST) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.7/8.8.5) id PAA07158 for freebsd-current@freebsd.org; Thu, 30 Oct 1997 15:29:04 GMT From: Adam David Message-Id: <199710301529.PAA07158@veda.is> Subject: MFS ? To: freebsd-current@freebsd.org Date: Thu, 30 Oct 1997 15:29:03 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed a commit involving MFS the other day, but it didn't say anything about this fixing MFS so I guess it's still in the no-go zone? What would happen if I tried to use MFS with it broken? Would it just not run, or would it grow legs and stomp all over the place? -- Adam David From owner-freebsd-current Thu Oct 30 08:31:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18267 for current-outgoing; Thu, 30 Oct 1997 08:31:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18244 for ; Thu, 30 Oct 1997 08:30:59 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id RAA00316; Thu, 30 Oct 1997 17:20:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Adam David cc: freebsd-current@FreeBSD.ORG Subject: Re: MFS ? In-reply-to: Your message of "Thu, 30 Oct 1997 15:29:03 GMT." <199710301529.PAA07158@veda.is> Date: Thu, 30 Oct 1997 17:20:32 +0100 Message-ID: <314.878228432@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710301529.PAA07158@veda.is>, Adam David writes: >I noticed a commit involving MFS the other day, but it didn't say anything >about this fixing MFS so I guess it's still in the no-go zone? It was to remove a non-fatal warning. > >What would happen if I tried to use MFS with it broken? Would it just not >run, or would it grow legs and stomp all over the place? Have I missed a report on it being broken ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Thu Oct 30 09:21:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22533 for current-outgoing; Thu, 30 Oct 1997 09:21:00 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA22527 for ; Thu, 30 Oct 1997 09:20:56 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xQyGt-0005fN-00; Thu, 30 Oct 1997 09:20:39 -0800 Date: Thu, 30 Oct 1997 09:20:36 -0800 (PST) From: Tom To: Kristian Kennaway cc: FreeBSD Current Subject: Re: Crappy modem upload bandwidth In-Reply-To: <9710301349.AA01649@bragg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 31 Oct 1997, Kristian Kennaway wrote: > rates, but it slows to an average of like 50 bps when I try and upload. > What seems to happen is that the modem sends in very short bursts > "bursts" at close to full-speed, then idles for a minute or more before > doing the next one. Before this happened, I had no problems uploading > from my computer.. Sounds like flow control between your computer and modem is not working right. The modem should be set for hardware flow control. What is happening, is that the computer to modem speed is 38400 (probably), but the modem-to-modem speed is 14400. This poses a problem when sending data, as at 38400 the modem's buffers will very quickly fill up. The modem should be using flow control to stop the computer until its buffers drain out. Either the modem isn't using flow control, or the PC isn't listening for it. Tom From owner-freebsd-current Thu Oct 30 10:42:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA28653 for current-outgoing; Thu, 30 Oct 1997 10:42:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA28647 for ; Thu, 30 Oct 1997 10:42:09 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id TAA00396; Thu, 30 Oct 1997 19:42:00 +0100 (MET) Message-Id: <199710301842.TAA00396@sos.freebsd.dk> Subject: Re: Guys, what is happening with DNS and Linux-Emu ? In-Reply-To: <199710300844.JAA00974@magnet.geophysik.tu-freiberg.de> from Holm Tiffe at "Oct 30, 97 09:44:44 am" To: freebsd@magnet.geophysik.tu-freiberg.de (Holm Tiffe) Date: Thu, 30 Oct 1997 19:41:54 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Holm Tiffe who wrote: > Hi, > > There are currently 2 threads about this problem ("Star Office on > 3.0 current" and "Small Problem with Linux Emul") in -current. > > I've noticed, that DNS resolving under the Linux-Emu on my machines > with -current i'nt working since 08/20/97. > I've reinstalled the linux_lib, double checked the files in > /compat/linux/etc and so on. > > One of my machines is an SMP P6 with applixware installed, > this machine has had a working DNS with a -current from 08/15/97 > until I've updated this roadrunner to -current. (10/28/97) > > Because of this, I think, bad config files in /compat/linux/etc > could'nt be the trigger of this problem. > > The DNS in the FreeBSD "universe" is working flawlessly. > > The nameserver get the question and I think it replays ok. > But the results semms to be not interpreted correctly... > > The only person I know who has a -current with a working DNS > seems to be Søren Schmidt . I have just tried again, with a fresh install of StarOffice & the linix libs. It just works... It takes exactly 14 secs from I hit enter until swriter3 is ready to use... I dont see any problems here, sorry.... Could you "lend" me the linux telnet you are using, maybe that can make something surface ..... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Thu Oct 30 10:42:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA28701 for current-outgoing; Thu, 30 Oct 1997 10:42:43 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA28684 for ; Thu, 30 Oct 1997 10:42:36 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id KAA22442 for ; Thu, 30 Oct 1997 10:42:03 -0800 (PST) Message-ID: <3458D4FA.92638954@excite.com> Date: Thu, 30 Oct 1997 10:42:02 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: broken SMP support? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ever since after Oct-23, I could not successfully compile a bootable current-SMP kernel. Anyone have the same experience? How can I fix this? Kingson From owner-freebsd-current Thu Oct 30 10:54:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA29603 for current-outgoing; Thu, 30 Oct 1997 10:54:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA29579 for ; Thu, 30 Oct 1997 10:54:40 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (4DW+lmmDZxFQ8tV9Y42tXCSwOZiHuK2Z@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id UAA24405; Thu, 30 Oct 1997 20:54:41 +0200 (SAT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (sCWKSQ3Mh+G+f+KN9qakmrC3B29PbOch@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id UAA00986; Thu, 30 Oct 1997 20:54:26 +0200 (SAST) Message-Id: <199710301854.UAA00986@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: kingson@excite.com cc: freebsd-current@FreeBSD.ORG Subject: Re: broken SMP support? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Oct 1997 20:54:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kingson Gunawan wrote: > Ever since after Oct-23, I could not successfully compile a bootable > current-SMP kernel. Anyone have the same experience? How can I fix > this? I've booted several. Post your configuration. That is essential information. Lots of deatail about the failure is also needed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Thu Oct 30 10:58:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA29889 for current-outgoing; Thu, 30 Oct 1997 10:58:56 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA29879 for ; Thu, 30 Oct 1997 10:58:40 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 23852 invoked by uid 1000); 30 Oct 1997 18:59:03 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 30 Oct 1997 10:59:03 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: Julian Elischer Subject: Re: dummy_mount - Who are you? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Julian Elischer; On 30-Oct-97 you wrote: > ahh > yes, > > This is the kernel's internal mounting of the devfs. > I had thought I had not exported the line of code that > actually does this, but it appears that it slipped past me.. > The DEVFS is mounted internally to the kernel. You cannot > get to it. (hense the name..'hidden mount' might be a better name) > This is not needed yet, but will be soon. > I don't see that error message, but are you sure it's the KERNEL > giving that message? No. All I see on the console is the message. It does not show in the logs at all. > All is ok, it's just htat I didn't realise that I'd exported that > 'feature' yet. Almost. umount -a barfs on it too. Maybe the message comes from mountd? > I'll look into it later tonight. > > "don't Panic" Nanhhh. I have much worse problems in life :-) --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 10:59:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA29931 for current-outgoing; Thu, 30 Oct 1997 10:59:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA29913 for ; Thu, 30 Oct 1997 10:59:05 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 23884 invoked by uid 1000); 30 Oct 1997 18:59:05 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Thu, 30 Oct 1997 10:59:04 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: sgmlfmt - again... Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'll As far back as the 25th of this month this problem was corrected. Now we get again: chflags -R noschg /R/stage/trees touch release.2 cd /usr/doc && make all distribute DISTDIR=/R/stage/trees ===> FAQ sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml sgmlfmt: not found *** Error code 1 Yuck. sgmlfmt is not installed in /usr/bin of the build :-( --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 11:00:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00145 for current-outgoing; Thu, 30 Oct 1997 11:00:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA29964 for ; Thu, 30 Oct 1997 10:59:37 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 23891 invoked by uid 1000); 30 Oct 1997 18:59:05 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 30 Oct 1997 10:59:05 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: Simon Shapiro Subject: RE: Are We Losing Interrupts? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Simon Shapiro; On 30-Oct-97 you wrote: ... Yup we are. I added a simple routine to the DPT driver; at one second intervals, it forces the interrupt service routine to run. If there was no interrupt pending, we do nothing. If there was, we conplain and increment a counter. Here are the results since last night boot: Oct 30 08:39:04 sendero /kernel.sendero-smp: dpt 0: 37 lost Interrupts Recovered Oct 30 08:44:54 sendero /kernel.sendero-smp: dpt 1: 126 lost Interrupts Recovered I would not pay all that much attention to the smp issue; we are getting the exact same thing with a UP kernel. --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 11:06:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00687 for current-outgoing; Thu, 30 Oct 1997 11:06:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00678 for ; Thu, 30 Oct 1997 11:06:42 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id LAA26538; Thu, 30 Oct 1997 11:05:15 -0800 (PST) Message-ID: <3458DA6B.57934A2E@excite.com> Date: Thu, 30 Oct 1997 11:05:15 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Mark Murray CC: freebsd-current@FreeBSD.ORG Subject: Re: broken SMP support? References: <199710301854.UAA00986@greenpeace.grondar.za> Content-Type: multipart/mixed; boundary="------------F6D186285306B86CE966F5C8" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------F6D186285306B86CE966F5C8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Murray wrote: > > Kingson Gunawan wrote: > > Ever since after Oct-23, I could not successfully compile a bootable > > current-SMP kernel. Anyone have the same experience? How can I fix > > this? > > I've booted several. > > Post your configuration. That is essential information. Lots of deatail > about the failure is also needed. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org I've attached my config file with this email. The resulting kernel blank the screen (so I can't see what's there) and just reboot the machine. Kingson --------------F6D186285306B86CE966F5C8 Content-Type: text/plain; charset=us-ascii; name="CARNAGE" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="CARNAGE" # $Id: SMP-GENERIC,v 1.9 1997/10/28 07:24:35 joerg Exp $ machine "i386" cpu "I686_CPU" ident CARNAGE maxusers 50 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs # Lets always enable the kernel debugger for SMP. options DDB options DDB_UNATTENDED options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG # options "MD5" config kernel root on sd0 dumps on sd0 controller isa0 # controller eisa0 controller pci0 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ahc0 controller scbus0 device sd0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console # device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 options XSERVER # include code for XFree86 options FAT_CURSOR # start with block cursor device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device fxp0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 # device opl0 at isa? port 0x388 --------------F6D186285306B86CE966F5C8-- From owner-freebsd-current Thu Oct 30 11:21:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01954 for current-outgoing; Thu, 30 Oct 1997 11:21:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA01767 for ; Thu, 30 Oct 1997 11:20:06 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (KtT4zBGWAid+uGU0mnF+Zo4+PyHzMynC@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id VAA24448; Thu, 30 Oct 1997 21:20:05 +0200 (SAT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (sdV662NO+FTBmFLgdBsOyJa4mkqBn8rv@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id VAA01109; Thu, 30 Oct 1997 21:19:49 +0200 (SAST) Message-Id: <199710301919.VAA01109@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: kingson@excite.com cc: Mark Murray , freebsd-current@FreeBSD.ORG Subject: Re: broken SMP support? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Oct 1997 21:19:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kingson Gunawan wrote: > > > Ever since after Oct-23, I could not successfully compile a bootable > > > current-SMP kernel. Anyone have the same experience? How can I fix > > > this? > > > > I've booted several. > > > > Post your configuration. That is essential information. Lots of deatail > > about the failure is also needed. > > > > M > > -- > > Mark Murray > > Join the anti-SPAM movement: http://www.cauce.org > > > I've attached my config file with this email. The resulting kernel > blank the screen (so I can't see what's there) and just reboot the > machine. You still need to post more. What is your hardware? Dig around a bit and see if you can anticipate what others may ask you to do. Post the results. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Thu Oct 30 11:41:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03570 for current-outgoing; Thu, 30 Oct 1997 11:41:43 -0800 (PST) (envelope-from owner-freebsd-current) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03551 for ; Thu, 30 Oct 1997 11:41:38 -0800 (PST) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.7/8.8.5) id TAA14160; Thu, 30 Oct 1997 19:37:38 GMT From: Adam David Message-Id: <199710301937.TAA14160@veda.is> Subject: Re: MFS ? In-Reply-To: <314.878228432@critter.freebsd.dk> from Poul-Henning Kamp at "Oct 30, 97 05:20:32 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 30 Oct 1997 19:37:37 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >What would happen if I tried to use MFS with it broken? Would it just not > >run, or would it grow legs and stomp all over the place? > > Have I missed a report on it being broken ? > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." [from October 19th - 23rd]... ==== quote Joao Carlos Mendes Luis said: > #define quoting(John S. Dyson) > // My first-cut attempt of fixing MFS only helped a little. It is broken, > // and please don't bother using it until I, PHK or someone else fixes it. > // I am working on it right now. > > Talking about MFS remembered me about this. > > How hard would it be to implement Sun's tmpfs ? It's lots more > efficient in terms of memory use and speed than mfs. > I have been thinking about something like that (except more of a cross between the two.) Maybe I'll do something this week (I am ill.) -- John dyson@freebsd.org ==== unquote From owner-freebsd-current Thu Oct 30 12:30:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08004 for current-outgoing; Thu, 30 Oct 1997 12:30:38 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA07986 for ; Thu, 30 Oct 1997 12:30:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA00801; Thu, 30 Oct 1997 21:29:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Adam David cc: freebsd-current@FreeBSD.ORG Subject: Re: MFS ? In-reply-to: Your message of "Thu, 30 Oct 1997 19:37:37 GMT." <199710301937.TAA14160@veda.is> Date: Thu, 30 Oct 1997 21:29:28 +0100 Message-ID: <799.878243368@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That was fixed longer time ago. I belive MFS is as (dys)functional as always. Poul-Henning In message <199710301937.TAA14160@veda.is>, Adam David writes: >> >What would happen if I tried to use MFS with it broken? Would it just not >> >run, or would it grow legs and stomp all over the place? >> >> Have I missed a report on it being broken ? >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." > >[from October 19th - 23rd]... > >==== quote >Joao Carlos Mendes Luis said: >> #define quoting(John S. Dyson) >> // My first-cut attempt of fixing MFS only helped a little. It is broken, >> // and please don't bother using it until I, PHK or someone else fixes it. >> // I am working on it right now. >> >> Talking about MFS remembered me about this. >> >> How hard would it be to implement Sun's tmpfs ? It's lots more >> efficient in terms of memory use and speed than mfs. >> >I have been thinking about something like that (except more of a cross betwe >en >the two.) Maybe I'll do something this week (I am ill.) > >-- >John >dyson@freebsd.org >==== unquote -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Thu Oct 30 12:45:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09263 for current-outgoing; Thu, 30 Oct 1997 12:45:22 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09245 for ; Thu, 30 Oct 1997 12:45:12 -0800 (PST) (envelope-from ken@plutotech.com) Received: (from ken@localhost) by pluto.plutotech.com (8.8.7/8.8.5) id NAA05622; Thu, 30 Oct 1997 13:44:50 -0700 (MST) From: Kenneth Merry Message-Id: <199710302044.NAA05622@pluto.plutotech.com> Subject: Re: broken SMP support? In-Reply-To: <3458DA6B.57934A2E@excite.com> from Kingson Gunawan at "Oct 30, 97 11:05:15 am" To: kingson@excite.com Date: Thu, 30 Oct 1997 13:44:50 -0700 (MST) Cc: mark@grondar.za, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kingson Gunawan wrote... > I've attached my config file with this email. The resulting kernel > blank the screen (so I can't see what's there) and just reboot the > machine. One other thing that will definitely help out is if you can run the following command and send the results back to the list: mptable -verbose -dmesg You can run this with a uniprocessor kernel. > options BOUNCE_BUFFERS #include support for DMA bounce buffers You don't need bounce buffers, you don't have any controllers that require it. > options UCONSOLE #Allow users to grab the console > options FAILSAFE #Be conservative I would remove failsafe as well. Also, what hardware are you running with? (motherboard, CPUs, memory, video cards, network cards, etc..) It's possible (yeah, I know this is a reach) that this could be a pcvt problem. Has anyone run PCVT with a SMP kernel? Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-current Thu Oct 30 13:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11952 for current-outgoing; Thu, 30 Oct 1997 13:22:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA11932 for ; Thu, 30 Oct 1997 13:21:52 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 9897 invoked from network); 30 Oct 1997 21:21:37 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 30 Oct 1997 21:21:37 -0000 From: "Evan Champion" To: Subject: Corrupt file in X11R6, 971030 bin broken Date: Thu, 30 Oct 1997 16:21:29 -0500 Message-ID: <01bce579$c9cd26c0$513654c7@cello.synapse.net> 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.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The package that I reported broken in X11R6 is X3319WSN. It reports "unexpected end of file". In addition, 971030's bin distribution has a checksum error. I tried installing 3 times from current.freebsd.org, all with the same problem. Evan From owner-freebsd-current Thu Oct 30 13:29:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA12402 for current-outgoing; Thu, 30 Oct 1997 13:29:40 -0800 (PST) (envelope-from owner-freebsd-current) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA12386 for ; Thu, 30 Oct 1997 13:29:35 -0800 (PST) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.7/8.8.5) id VAA18404; Thu, 30 Oct 1997 21:25:18 GMT From: Adam David Message-Id: <199710302125.VAA18404@veda.is> Subject: Re: MFS ? In-Reply-To: <799.878243368@critter.freebsd.dk> from Poul-Henning Kamp at "Oct 30, 97 09:29:28 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 30 Oct 1997 21:25:16 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > That was fixed longer time ago. > > I belive MFS is as (dys)functional as always. > > Poul-Henning OK, different meaning of the word "broken" ;) thanks -- Adam David From owner-freebsd-current Thu Oct 30 13:43:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA13199 for current-outgoing; Thu, 30 Oct 1997 13:43:17 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA13194 for ; Thu, 30 Oct 1997 13:43:13 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id NAA04262; Thu, 30 Oct 1997 13:42:48 -0800 (PST) To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG Subject: Re: sgmlfmt - again... In-reply-to: Your message of "Thu, 30 Oct 1997 10:59:04 PST." Date: Thu, 30 Oct 1997 13:42:48 -0800 Message-ID: <4257.878247768@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml > sgmlfmt: not found > *** Error code 1 > > Yuck. sgmlfmt is not installed in /usr/bin of the build :-( And hasn't been for months now. You need to install sgmlfmt from the port version (see ports/textproc for the appropriate utilities) in order to build the docs (which have also been unbundled for months now). Jordan From owner-freebsd-current Thu Oct 30 13:59:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA13932 for current-outgoing; Thu, 30 Oct 1997 13:59:27 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA13924 for ; Thu, 30 Oct 1997 13:59:16 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA26922 for ; Thu, 30 Oct 1997 21:58:53 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA07764; Thu, 30 Oct 1997 22:58:53 +0100 (MET) Date: Thu, 30 Oct 1997 22:58:53 +0100 (MET) Message-Id: <199710302158.WAA07764@bitbox.follo.net> From: Eivind Eklund To: freebsd-current@freebsd.org Subject: My missing directories Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Another one disappeared today. That's the forth (fifth?) one so far. However, it made me notice something - all (but one?) of these were directly from my homedir, and one subdir down from my homedir is NOT where I do most of my work. And the 'but one' one was when using CVS, and I wouldn't put it beyond being a CVS anormality. (I also don't remember it too clearly, as it didn't seem significant at the time - just easily regeneretable files and something I believed was CVS related until the other dirs started vanishing.) Eivind. From owner-freebsd-current Thu Oct 30 14:35:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA16333 for current-outgoing; Thu, 30 Oct 1997 14:35:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA16320 for ; Thu, 30 Oct 1997 14:35:17 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id OAA11692; Thu, 30 Oct 1997 14:34:12 -0800 (PST) Message-ID: <34590B63.F4BD5063@excite.com> Date: Thu, 30 Oct 1997 14:34:11 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Simon Shapiro CC: freebsd-current@FreeBSD.ORG Subject: Re: broken SMP support? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Simon, right after the boot prompt screen, the kernel blanks out the screen (I simply could not catch what's there). Then, the machine just rebooted. BTW, here is my hardware config: dual PII-266 on Air P6KDI m/b 512MB RAM 8 - 4.1GB IBM DCAS-34330UW SCSI hd's Adaptec 2940UW/PCI (I am thinking about replacing this with DPT SR-4) Intel EE 100B/pro fast ethernet card (PCI) Matshita 8x CD-ROM drive Matrox Millenium (MGA) w/ 4mb The thing is that I've been successful in compiling SMP-kernel up until the Oct 22-SNAP. Really wierd. Kingson Simon Shapiro wrote: > > Hi Kingson Gunawan; On 30-Oct-97 you wrote: > > Ever since after Oct-23, I could not successfully compile a bootable > > current-SMP kernel. Anyone have the same experience? How can I fix > > this? > > > > Kingson > > Nope. It builds fine and boots fine, except for the lost interrupts > problem I reported. What are your symptoms? > > --- > If Microsoft Built Cars: > > Every time they repainted the lines on the road, you'd have to buy a new > car. > > Sincerely Yours, > > Simon Shapiro Atlas Telecom > Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 > Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 14:35:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA16389 for current-outgoing; Thu, 30 Oct 1997 14:35:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA16384 for ; Thu, 30 Oct 1997 14:35:57 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id OAA11890 for ; Thu, 30 Oct 1997 14:35:24 -0800 (PST) Message-ID: <34590BAB.98F7A2BA@excite.com> Date: Thu, 30 Oct 1997 14:35:23 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am planning to configure a huge (20+GB)RAID volume, and just happen to have a DPT controller sitting around. Have anyone done this successfully? Is this a better config compared to using ccd? Kingson From owner-freebsd-current Thu Oct 30 15:33:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA20629 for current-outgoing; Thu, 30 Oct 1997 15:33:56 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA20624 for ; Thu, 30 Oct 1997 15:33:53 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xR45M-00002G-00; Thu, 30 Oct 1997 15:33:08 -0800 Date: Thu, 30 Oct 1997 15:33:04 -0800 (PST) From: Tom To: Kingson Gunawan cc: freebsd-current@freebsd.org Subject: Re: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? In-Reply-To: <34590BAB.98F7A2BA@excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 30 Oct 1997, Kingson Gunawan wrote: > I am planning to configure a huge (20+GB)RAID volume, and just happen to > have a DPT controller sitting around. Have anyone done this > successfully? Is this a better config compared to using ccd? 20GB is pretty small for drive arrays. Compared to ccd? Well, it can RAID5 which ccd can't, but write performance suffers a bit in RAID5. If you have 6 or 10 drives, you might might to make two RAID5 arrays, and then use ccd on them. But it all depends on what you want to do, and what RAID level you are going to use. > Kingson > > Tom From owner-freebsd-current Thu Oct 30 15:35:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA20795 for current-outgoing; Thu, 30 Oct 1997 15:35:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA20772 for ; Thu, 30 Oct 1997 15:34:59 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id PAA26642; Thu, 30 Oct 1997 15:33:55 -0800 (PST) Message-ID: <34591962.E15237A4@excite.com> Date: Thu, 30 Oct 1997 15:33:54 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Kenneth Merry CC: freebsd-current@FreeBSD.ORG Subject: Re: broken SMP support? References: <199710302328.QAA13645@pluto.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Kenneth, here it is... Strange indeed... Kingson # mptable -verbose -dmesg -groupe =============================================================================== MPTable, version 2.0.15 looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009fc00 searching CMOS 'top of mem' @ 0x0009f800 (638K) searching default 'top of mem' @ 0x0009fc00 (639K) searching BIOS @ 0x000f0000 searching extended BIOS @ 0x000e0000 MP FPS NOT found, suggest trying -grope option!!! Kenneth Merry wrote: > > Kingson Gunawan wrote... > > Hi Kenneth, > > here is the output... (running the uni-kernel). > > > > Kingson > > > > > > # mptable -verbose -dmesg > > > > =============================================================================== > > > > MPTable, version 2.0.15 > > > > looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009fc00 > > searching CMOS 'top of mem' @ 0x0009f800 (638K) > > searching default 'top of mem' @ 0x0009fc00 (639K) > > searching BIOS @ 0x000f0000 > > searching extended BIOS @ 0x000e0000 > > > > MP FPS NOT found, > > suggest trying -grope option!!! > > Strange indeed. Try using the -grope option as well, i.e.: > > mptable -verbose -dmesg -grope > > And CC it to the FreeBSD-current mailing list as well. If mptable > can't get the right information out of your motherboard, there are folks on > -current who would like to know... > > Ken > -- > Kenneth Merry > ken@plutotech.com From owner-freebsd-current Thu Oct 30 15:38:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA21048 for current-outgoing; Thu, 30 Oct 1997 15:38:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA21036 for ; Thu, 30 Oct 1997 15:38:15 -0800 (PST) (envelope-from kingson@excite.com) Received: from excite.com (batik [204.62.245.185]) by kaos.atext.com (8.8.5/8.8.5) with ESMTP id PAA27089; Thu, 30 Oct 1997 15:37:36 -0800 (PST) Message-ID: <34591A3C.B81619A2@excite.com> Date: Thu, 30 Oct 1997 15:37:32 -0800 From: Kingson Gunawan Reply-To: kingson@excite.com Organization: Excite Inc. X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Tom CC: freebsd-current@FreeBSD.ORG Subject: Re: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom, I am planning to use RAID 0 (no mirroring), just a straight stripping. BTW, potentially, I will need to grow the array up to around 120GB. However, that's somewhat in the future. This array will be read intensive. Kingson Tom wrote: > > On Thu, 30 Oct 1997, Kingson Gunawan wrote: > > > I am planning to configure a huge (20+GB)RAID volume, and just happen to > > have a DPT controller sitting around. Have anyone done this > > successfully? Is this a better config compared to using ccd? > > 20GB is pretty small for drive arrays. Compared to ccd? Well, it can > RAID5 which ccd can't, but write performance suffers a bit in RAID5. > > If you have 6 or 10 drives, you might might to make two RAID5 arrays, > and then use ccd on them. > > But it all depends on what you want to do, and what RAID level you are > going to use. > > > Kingson > > > > > > Tom From owner-freebsd-current Thu Oct 30 15:53:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA21993 for current-outgoing; Thu, 30 Oct 1997 15:53:36 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA21986 for ; Thu, 30 Oct 1997 15:53:32 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xR4P4-0000Bv-00; Thu, 30 Oct 1997 15:53:30 -0800 Date: Thu, 30 Oct 1997 15:53:25 -0800 (PST) From: Tom To: Kingson Gunawan cc: freebsd-current@freebsd.org Subject: Re: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? In-Reply-To: <34591A3C.B81619A2@excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 30 Oct 1997, Kingson Gunawan wrote: > Hi Tom, > I am planning to use RAID 0 (no mirroring), just a straight stripping. > BTW, potentially, I will need to grow the array up to around 120GB. > However, that's somewhat in the future. > This array will be read intensive. You will probably want RAID 5. Reliability of large array is equal to the reliability of one drive divided by the number of drives. Unless reliability is not a concern. > Kingson Tom From owner-freebsd-current Thu Oct 30 17:35:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA28548 for current-outgoing; Thu, 30 Oct 1997 17:35:50 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA28536 for ; Thu, 30 Oct 1997 17:35:43 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 23721 invoked by uid 1000); 31 Oct 1997 01:36:05 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <34590BAB.98F7A2BA@excite.com> Date: Thu, 30 Oct 1997 17:36:05 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: kingson@excite.com Subject: RE: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Kingson Gunawan; On 30-Oct-97 you wrote: > I am planning to configure a huge (20+GB)RAID volume, and just happen to > have a DPT controller sitting around. Have anyone done this > successfully? Is this a better config compared to using ccd? Simpler, more reliable, and O/S independant. Oh, quite faster too. But still not in the source tree. Patches only. --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 17:35:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA28553 for current-outgoing; Thu, 30 Oct 1997 17:35:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA28537 for ; Thu, 30 Oct 1997 17:35:44 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 23726 invoked by uid 1000); 31 Oct 1997 01:36:05 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <34591A3C.B81619A2@excite.com> Date: Thu, 30 Oct 1997 17:36:05 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: kingson@excite.com Subject: Re: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? Cc: freebsd-current@FreeBSD.ORG, Tom Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Kingson Gunawan; On 30-Oct-97 you wrote: > Hi Tom, > I am planning to use RAID 0 (no mirroring), just a straight stripping. > BTW, potentially, I will need to grow the array up to around 120GB. > However, that's somewhat in the future. > This array will be read intensive. Read performance improves with array size. Write performance will degrade with array size (Raid-5), but the rate of degradation is not linear, nor exponential. Expect to write about 5-6MB/Sec. Read at double or better. We max out around 1740 RAID I/O operations per second. Compare that to other controllers. Also keep in mind that ccd consumes processor memory and cycles, while a DPT will do it all on-board with exactly one interrupt per access. A CCD striped four wide will generate four times as many interrupts. Luck? We are shipping FT transaction processing systems based on exactly that. Uptime is in the weeks (we stop for upgrades :-), and no known crashes. Zero data loss. An IMPORTANT (again, VERY IMPORTANT) factor in successfull SCSI array is quality of disks, enclosures, cabling and power. BTW, the DPT will do ECC over its own memory, all the way into the disk sector, so bus glitches, minor errors, etc. are corrected in real time. If you have 120GB on-line, that may be important. We have only 16GB on entry level systems but the monetary value of the database is well worth the expense :-) --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 17:59:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA00908 for current-outgoing; Thu, 30 Oct 1997 17:59:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.5.84]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA00903 for ; Thu, 30 Oct 1997 17:59:08 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.7/8.8.7) id SAA10332; Thu, 30 Oct 1997 18:58:44 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd010294; Thu Oct 30 18:58:33 1997 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id SAA08878; Thu, 30 Oct 1997 18:58:28 -0700 (MST) From: Terry Lambert Message-Id: <199710310158.SAA08878@usr09.primenet.com> Subject: Re: Small Problem with Linux Emul To: bag@sinbin.demos.su (Alex G. Bulushev) Date: Fri, 31 Oct 1997 01:58:27 +0000 (GMT) Cc: tlambert@primenet.com, kmitch@weenix.guru.org, tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <199710300735.KAA09980@sinbin.demos.su> from "Alex G. Bulushev" at Oct 30, 97 10:35:02 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > we succesfully used 2.0 server with linux emulator before Sep 97 > after some changes in -current kernel in Sep server starts, but > have no connection ... > now it not work in 3.0-971012-SNAP ... cd /usr/src cvs diff -D 1997/10/01 -D 1997/10/30 | more ??? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Oct 30 18:00:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA01127 for current-outgoing; Thu, 30 Oct 1997 18:00:40 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA01113 for ; Thu, 30 Oct 1997 18:00:33 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id TAA22117; Thu, 30 Oct 1997 19:00:26 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd022112; Thu Oct 30 19:00:20 1997 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id TAA09179; Thu, 30 Oct 1997 19:00:17 -0700 (MST) From: Terry Lambert Message-Id: <199710310200.TAA09179@usr09.primenet.com> Subject: Re: Small Problem with Linux Emul To: kmitch@weenix.guru.org (Keith Mitchell) Date: Fri, 31 Oct 1997 02:00:17 +0000 (GMT) Cc: tlambert@primenet.com, current@freebsd.org In-Reply-To: <199710301416.JAA08987@weenix.guru.org> from "Keith Mitchell" at Oct 30, 97 09:15:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > If you can, you should convert them to hex, and look at the output > > of netstat -rn and arp -a to see if they are coming from a route, > > gateway, NATD or other IP address "translator", or if the hex values > > match the actual physical addresses, etc.. > > I converted them to hex, but they didn't match anything in arp or netstat. > The port number comes back garbled too. > > 192.246.40.12:27003 > > comes back as > > 232.212.191.239:49135 (E8.D4.BF.EF) -or sometimes- > 216.142.4.8:49135 (D8.8E.04.08) > > The ip address that actually comes back is not always the same either. The > port number does seem to reamin the same though. Are you using IP aliases? Is the other end using IP aliases, and not being careful to send on the interface it received on? Other than you seriously digging, I have no answer; I can't repeat it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Oct 30 18:38:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA03313 for current-outgoing; Thu, 30 Oct 1997 18:38:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA03299 for ; Thu, 30 Oct 1997 18:38:04 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id VAA22946; Thu, 30 Oct 1997 21:34:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199710310234.VAA22946@dyson.iquest.net> Subject: Re: MFS ? In-Reply-To: <799.878243368@critter.freebsd.dk> from Poul-Henning Kamp at "Oct 30, 97 09:29:28 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 30 Oct 1997 21:34:05 -0500 (EST) Cc: adam@veda.is, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp said: > > That was fixed longer time ago. > > I belive MFS is as (dys)functional as always. > Seems to work again after PHK's fix. It still needs to be fixed to avoid the context switch, and unnecessary copying. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Thu Oct 30 19:31:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06324 for current-outgoing; Thu, 30 Oct 1997 19:31:57 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA06313 for ; Thu, 30 Oct 1997 19:31:54 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id UAA03424; Thu, 30 Oct 1997 20:31:43 -0700 (MST) Message-Id: <199710310331.UAA03424@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: kingson@excite.com cc: Kenneth Merry , freebsd-current@FreeBSD.ORG Subject: Re: broken SMP support? In-reply-to: Your message of "Thu, 30 Oct 1997 15:33:54 PST." <34591962.E15237A4@excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Oct 1997 20:31:43 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > Hi Kenneth, > here it is... Strange indeed... > > Kingson > > > # mptable -verbose -dmesg -groupe > > =============================================================================== > > MPTable, version 2.0.15 > > looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009fc00 > searching CMOS 'top of mem' @ 0x0009f800 (638K) > searching default 'top of mem' @ 0x0009fc00 (639K) > searching BIOS @ 0x000f0000 > searching extended BIOS @ 0x000e0000 > > MP FPS NOT found, There is NO way this machine will run an SMP kernel if it can't find the MP table! Remove: options DDB_UNATTENDED this will allow you to see the problem, which will be a complaint about the missing MP table. If this machine used to run SMP, then the BIOS has been changed, or the hardware has been changed or gone south... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Thu Oct 30 20:07:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08183 for current-outgoing; Thu, 30 Oct 1997 20:07:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA08176 for ; Thu, 30 Oct 1997 20:07:42 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 23452 invoked by uid 1000); 31 Oct 1997 04:08:09 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <3459446A.F24E0CA9@excite.com> Date: Thu, 30 Oct 1997 20:08:09 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: kingson@excite.com, freebsd-current@freebsd.org Subject: Re: Any luck with DPT SmartRaid 4 and SMP FreeBSD-current??? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Kingson Gunawan; On 31-Oct-97 you wrote: > Simon, > do you have or could you create a boot floppy image file that would > recognize the DPT card? Yup. Try ftp://sendero-ppp.i-connect.net/FreeBSD/3.0-9710*/floppies --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 20:29:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA09323 for current-outgoing; Thu, 30 Oct 1997 20:29:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA09317 for ; Thu, 30 Oct 1997 20:29:02 -0800 (PST) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id XAA03075; Thu, 30 Oct 1997 23:28:25 -0500 (EST) From: Keith Mitchell Message-Id: <199710310428.XAA03075@weenix.guru.org> Subject: Re: Small Problem with Linux Emul In-Reply-To: <199710310200.TAA09179@usr09.primenet.com> from Terry Lambert at "Oct 31, 97 02:00:17 am" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 30 Oct 1997 23:28:25 -0500 (EST) Cc: current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are you using IP aliases? No, but the machine is multihomed (two de0 devices). The 2.2.5 machine that works is running IP aliases though. > Is the other end using IP aliases, and not being careful to send on the > interface it received on? I don't think so. I know that it doesn't work from a Win95/NT4 machine that has only one IP address, but the addresses I listed earlier are the master quake servers (the ones that keep the lists of servers). I imagine that they are running Linux, but I don't really know. > Other than you seriously digging, I have no answer; I can't repeat it. Hmm, would it make a difference if I only ifconfiged one of the interfaces, yet left them both in the computer (they're on the same card). Are you trying to replicate it with a quakeworld server or some generic Linux net application? I will do a little more digging/experimentation to see if I can find out any more info. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved From owner-freebsd-current Thu Oct 30 22:58:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16899 for current-outgoing; Thu, 30 Oct 1997 22:58:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA16891 for ; Thu, 30 Oct 1997 22:58:43 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 13312 invoked by uid 1000); 31 Oct 1997 06:59:11 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Thu, 30 Oct 1997 22:59:11 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: LINT Kernel Question... Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Am getting, tonight, the following (and more): loading kernel cd9660_node.o: Undefined symbol `_simple_lock_init' referenced from text segment cd9660_node.o: Undefined symbol `__simple_lock' referenced from text segment ... kern_lock.o: Undefined symbol `__simple_unlock' referenced from text segment kern_lock.o: Undefined symbol `__simple_lock' referenced from text segment ... vfs_conf.o: More undefined symbol __simple_lock refs follow vfs_subr.o: Undefined symbol `_simple_lock_init' referenced from text segment What have I done? :-) --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 23:04:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA17262 for current-outgoing; Thu, 30 Oct 1997 23:04:56 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA17257 for ; Thu, 30 Oct 1997 23:04:53 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id XAA07971; Thu, 30 Oct 1997 23:04:37 -0800 (PST) To: "Evan Champion" cc: freebsd-current@FreeBSD.ORG Subject: Re: Corrupt file in X11R6, 971030 bin broken In-reply-to: Your message of "Thu, 30 Oct 1997 16:21:29 EST." <01bce579$c9cd26c0$513654c7@cello.synapse.net> Date: Thu, 30 Oct 1997 23:04:36 -0800 Message-ID: <7967.878281476@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The package that I reported broken in X11R6 is X3319WSN. It reports > "unexpected end of file". Fixed, thanks. > In addition, 971030's bin distribution has a checksum error. I tried > installing 3 times from current.freebsd.org, all with the same problem. Hmmmm. This one I can't reproduce - the distribtion on current.freebsd.org would appear to be just fine. How are you downloading this stuff and where is the error occurring? Jordan From owner-freebsd-current Thu Oct 30 23:15:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA17934 for current-outgoing; Thu, 30 Oct 1997 23:15:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA17928 for ; Thu, 30 Oct 1997 23:15:45 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 15178 invoked by uid 1000); 31 Oct 1997 07:16:11 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Thu, 30 Oct 1997 23:16:11 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: More on LINT Kernel Failure to compile Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think I found the problem but know not how to proceed: In (for example, /usr/src/sys/isofs/cd9660/cd9660_node.c one sees: int cd9660_init(vfsp) struct vfsconf *vfsp; { isohashtbl = hashinit(desiredvnodes, M_ISOFSMNT, &isohash); simple_lock_init(&cd9660_ihash_slock); return (0); } While /usr/src/sys/i386/include/lock.h says: #if !defined(SIMPLELOCK_DEBUG) && NCPUS > 1 /* * This set of defines turns on the real functions in i386/isa/apic_ipl.s. */ #define simple_lock_init(alp) s_lock_init(alp) #define simple_lock(alp) s_lock(alp) #define simple_lock_try(alp) s_lock_try(alp) #define simple_unlock(alp) s_unlock(alp) #endif /* !SIMPLELOCK_DEBUG && NCPUS > 1 */ So, if we debug simple locks or have only one CPU, what defines these symbols? I know how to cause it to compile, but I know not what the author means to have in case these conditions are false. --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 30 23:39:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19060 for current-outgoing; Thu, 30 Oct 1997 23:39:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA19049 for ; Thu, 30 Oct 1997 23:38:59 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id XAA23730; Thu, 30 Oct 1997 23:38:47 -0800 (PST) Message-ID: <19971030233846.44353@hydrogen.nike.efn.org> Date: Thu, 30 Oct 1997 23:38:46 -0800 From: John-Mark Gurney To: Simon Shapiro Cc: freebsd-current@FreeBSD.ORG Subject: Re: More on LINT Kernel Failure to compile References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Simon Shapiro on Thu, Oct 30, 1997 at 11:16:11PM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro scribbled this message on Oct 30: > While /usr/src/sys/i386/include/lock.h says: > > #if !defined(SIMPLELOCK_DEBUG) && NCPUS > 1 > /* > * This set of defines turns on the real functions in i386/isa/apic_ipl.s. > */ > #define simple_lock_init(alp) s_lock_init(alp) > #define simple_lock(alp) s_lock(alp) > #define simple_lock_try(alp) s_lock_try(alp) > #define simple_unlock(alp) s_unlock(alp) > > #endif /* !SIMPLELOCK_DEBUG && NCPUS > 1 */ > > So, if we debug simple locks or have only one CPU, what defines these > symbols? I hate to ask you, but could you use grep a bit more?? here is how I found out where these symbols are defined: $ gren ^simple_lock_init kern/* kern_lock.c:simple_lock_init(alp) $ vi kern/kern_lock.c /^simple_lock_init see that a few lines further down is: void _simple_lock(alp, id, l) struct simplelock *alp; then I do: $ grep _simple_lock sys/* lock.h:int _simple_lock_try __P((struct simplelock *alp, const char *, int)); lock.h:#define simple_lock_try(alp) _simple_lock_try(alp, __FILE__, __LINE__) lock.h:void _simple_lock __P((struct simplelock *alp, const char *, int)); lock.h:#define simple_lock(alp) _simple_lock(alp, __FILE__, __LINE__) proc.h: short p_simple_locks; /* DEBUG: count of held simple locks */ the above took me maybe a minute... and composing this message took about five... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Fri Oct 31 00:13:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA20614 for current-outgoing; Fri, 31 Oct 1997 00:13:38 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA20609 for ; Fri, 31 Oct 1997 00:13:35 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id TAA07799; Fri, 31 Oct 1997 19:11:05 +1100 Date: Fri, 31 Oct 1997 19:11:05 +1100 From: Bruce Evans Message-Id: <199710310811.TAA07799@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, Shimon@i-Connect.Net Subject: Re: LINT Kernel Question... Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Am getting, tonight, the following (and more): > >loading kernel >cd9660_node.o: Undefined symbol `_simple_lock_init' referenced from text >segment >cd9660_node.o: Undefined symbol `__simple_lock' referenced from text segment >... >What have I done? :-) Nothing. This bug has been around for about 2 months (since SMP started using simple locks a lot). Option SIMPLELOCK_DEBUG does not work with NCPUS > 1. LINT sets this option, but LINT is poorly maintained, and apparently no one uses the option (I once used it to debug locking for NCPUS == 1). Bruce From owner-freebsd-current Fri Oct 31 00:40:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA21773 for current-outgoing; Fri, 31 Oct 1997 00:40:15 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA21768 for ; Fri, 31 Oct 1997 00:40:13 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA29548 for ; Fri, 31 Oct 1997 00:38:21 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029546; Fri Oct 31 08:38:17 1997 Date: Fri, 31 Oct 1997 00:36:32 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: Anyone else see this (broken ddb)? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk boot a new -current kernel with: Boot: -sd when the kernel comes to a stop in the debugger add: break vfs_mountrootfs cont when the system breaks on vfs_mountrootfs() try trace or step and get more pagefaults.. Does any one else see this? (I updates my sources today) julian From owner-freebsd-current Fri Oct 31 04:40:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA02381 for current-outgoing; Fri, 31 Oct 1997 04:40:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from cuervo.atl.netchannel.net (firewall-user@cuervo.netchannel.net [205.229.200.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA02374 for ; Fri, 31 Oct 1997 04:40:51 -0800 (PST) (envelope-from rbolin@netchannel.net) Received: by cuervo.atl.netchannel.net; id HAA12684; Fri, 31 Oct 1997 07:32:43 -0500 Received: from hermes.atl.netchannel.net(172.30.5.22) by cuervo.atl.netchannel.net via smap (3.2) id xma012681; Fri, 31 Oct 97 07:32:13 -0500 Received: from 207.205.32.104 by hermes.atl.netchannel.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id VZ3ZHKG4; Fri, 31 Oct 1997 07:46:08 -0500 Message-ID: <3459D1B4.2195FA5A@netchannel.net> Date: Fri, 31 Oct 1997 07:40:20 -0500 From: Ron Bolin X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: current usleep type conflict in unistd.h Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In building current from 10-30-97 I have the following error after doing a make world. /usleep.c -o usleep.po /usr/src/lib/libc/../libc/gen/usleep.c:47: conflicting types for `usleep' /usr/include/unistd.h:191: previous declaration of `usleep' *** Error code 1 In /usr/include/unistd.h the return type for usleep is void void usleep __P((unsigned int)); in usleep.c it is int usleep(useconds) Will the real usleep please stand up and be identified. Thanks Ron -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-6875 Web: http://www.mindspring.com/~rlb From owner-freebsd-current Fri Oct 31 06:09:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA07603 for current-outgoing; Fri, 31 Oct 1997 06:09:25 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA07592 for ; Fri, 31 Oct 1997 06:09:19 -0800 (PST) (envelope-from evanc@cello.synapse.net) Received: (qmail 24955 invoked from network); 31 Oct 1997 14:09:17 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 31 Oct 1997 14:09:17 -0000 Date: Fri, 31 Oct 1997 09:09:14 -0500 (EST) From: Evan Champion To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: Corrupt file in X11R6, 971030 bin broken In-Reply-To: <7967.878281476@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 30 Oct 1997, Jordan K. Hubbard wrote: > > In addition, 971030's bin distribution has a checksum error. I tried > > installing 3 times from current.freebsd.org, all with the same problem. > > Hmmmm. This one I can't reproduce - the distribtion on current.freebsd.org > would appear to be just fine. How are you downloading this stuff > and where is the error occurring? I'm downloading over PPP. The error occured in /usr/libexec, which was the major problem becasuse ld.so never got installed which made the installation kind of useless. As I said, I did it 3 times. I then installed 971029, and it worked just fine the first time. Evan From owner-freebsd-current Fri Oct 31 06:22:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA09405 for current-outgoing; Fri, 31 Oct 1997 06:22:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sinbin.demos.su (sinbin.demos.su [194.87.5.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA09347 for ; Fri, 31 Oct 1997 06:21:48 -0800 (PST) (envelope-from bag@sinbin.demos.su) Received: by sinbin.demos.su id RAA02226; (8.6.12/D) Fri, 31 Oct 1997 17:20:45 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199710311420.RAA02226@sinbin.demos.su> Subject: Re: current/nfs In-Reply-To: <19971029133643.17087@demos.su> from "Mikhail A. Sokolov" at "Oct 29, 97 01:36:43 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: smp@csn.net Date: Fri, 31 Oct 1997 17:20:45 +0300 (MSK) Cc: current@FreeBSD.ORG, mishania@demos.su X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, Oct 28, 1997 at 09:16:04AM -0700, Steve Passe wrote: > # Hi, > # > One machine runs 19971011-current and 'hangs' pretty regularily, then > # > tries to reboot, tries to sync and there hangs. The machine has pretty hard > # > task to be an nfs server for 5 others with up to 6000 interrupts/second, > # > motherboard is intel PR440FX, 2xppro200, there are enough swap/memory space. > # > # be more specific, what messages come out when it hangs/reboots? > > 'Cannot switch to CPU 0' \n 'Syncing disks' (or what's that message..) and > won't reboot. That's last one I caught yesterday, all other cases were just > 'Syncing' and there we stale. Now I made it non-SMP :-(, awaiting ... now we use identical 4 fbsd boxes with intel pr440fx, each with 2 intel EE/100 100base-T full-duplex, one is nfs server and 3 nfs clients nfs clients works fine with 3.0-971011 and 971012-SNAP kernel/SMP nfs server hangs 1-3 times a day with SMP kernel 971011 and 971012 latest src's not tested ... with nonSMP kernel 971012 it works without troubles: 5:14ÐÐ up 3 days, 1:01, 23 users, load averages: 0.47, 0.54, 0.56 > > Btw, what's that when it has 2 cpu's, the average load is _always_ >1,3, where > when the second processor is not enabled, it's _always_ (exept when they > start some perl :-)) > 0,60 ? > > It's peer (2.2.2+security fixes) would casually yelp that nfs server is not > responding, the find it (in a second or so) and finally hang in a frozen > state with a 'nfsbiostat panic'. > > > #> yell it can't start second CPU, - mp_lock 1000005, abort trap. It will do ok > #> on 233Mhz with 19971011-current, as well as 970926-SNAP. > > # this is probably the race fixed by: with 971012-SNAP it works on 200 and 233 MHz, thanks ... Alex. > > Thank you. > > # Steve Passe > > -- > -mishania, stressed. > From owner-freebsd-current Fri Oct 31 06:30:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10560 for current-outgoing; Fri, 31 Oct 1997 06:30:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10547 for ; Fri, 31 Oct 1997 06:30:46 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id JAA07622; Fri, 31 Oct 1997 09:29:48 -0500 (EST) Date: Fri, 31 Oct 1997 09:29:48 -0500 (EST) From: John Fieber To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG Subject: Re: sgmlfmt - again... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 30 Oct 1997, Simon Shapiro wrote: > chflags -R noschg /R/stage/trees > touch release.2 > cd /usr/doc && make all distribute DISTDIR=/R/stage/trees > ===> FAQ > sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml > sgmlfmt: not found > *** Error code 1 One reason the doc tree was removed from the source tree to allow removing the SGML tools from the source tree. The tools are now in the ports collection. Ultimately, the docs themselves should be wrapped up as ports so they can express proper dependencies on sgmlfmt. -john From owner-freebsd-current Fri Oct 31 09:33:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21881 for current-outgoing; Fri, 31 Oct 1997 09:33:40 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA21873 for ; Fri, 31 Oct 1997 09:33:32 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 15190 invoked by uid 1000); 31 Oct 1997 17:34:02 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19971030233846.44353@hydrogen.nike.efn.org> Date: Fri, 31 Oct 1997 09:34:01 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: John-Mark Gurney Subject: Re: More on LINT Kernel Failure to compile Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi John-Mark Gurney; On 31-Oct-97 you wrote: > Simon Shapiro scribbled this message on Oct 30: > > While /usr/src/sys/i386/include/lock.h says: > > > > #if !defined(SIMPLELOCK_DEBUG) && NCPUS > 1 > > /* > > * This set of defines turns on the real functions in > > i386/isa/apic_ipl.s. > > */ > > #define simple_lock_init(alp) s_lock_init(alp) > > #define simple_lock(alp) s_lock(alp) > > #define simple_lock_try(alp) s_lock_try(alp) > > #define simple_unlock(alp) s_unlock(alp) > > > > #endif /* !SIMPLELOCK_DEBUG && NCPUS > 1 */ > > > > So, if we debug simple locks or have only one CPU, what defines these > > symbols? > > I hate to ask you, but could you use grep a bit more?? here is how I > found out where these symbols are defined: ... As usual I completely failed to make my point: Had I had to compile the LINT kernel, I know how to do it. The problem is that I assumed (hate that word :-) that the LINT kernel is sort of standard sanity check for sources and is supposed to compile all by itself, without me ``assisting'' it. As a bystander to this project, when I find failures of this nature, I know of no other course of action than to post a note like I did. > Live in Peace, destroy Micro$oft, support free software, run FreeBSD This I agree with. completely :-) --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Fri Oct 31 10:19:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24918 for current-outgoing; Fri, 31 Oct 1997 10:19:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24905 for ; Fri, 31 Oct 1997 10:19:44 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.7/8.8.5) with SMTP id MAA17303; Fri, 31 Oct 1997 12:17:47 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Fri, 31 Oct 1997 12:17:46 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Simon Shapiro cc: John-Mark Gurney , freebsd-current@FreeBSD.ORG Subject: Re: More on LINT Kernel Failure to compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 31 Oct 1997, Simon Shapiro wrote: > ... > > As usual I completely failed to make my point: > > Had I had to compile the LINT kernel, I know how to do it. The problem is > that I assumed (hate that word :-) that the LINT kernel is sort of standard > sanity check for sources and is supposed to compile all by itself, without > me ``assisting'' it. I thought that the LINT file was only intended to yield a maximal set of sources, suitable for linting, and could not compile, because many of the options chosen for lint would be mutually exclusive. No one would ever, ever be intended to run a LINT kernel. If you added some off the wall option and wanted to (at least minimally) document it, the first place you'd stop would be to insert the option into LINT, with some appropriate comments. > > Simon Shapiro Atlas Telecom > Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 > Shimon@i-Connect.Net Voice: 503.799.2313 > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Fri Oct 31 11:13:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28387 for current-outgoing; Fri, 31 Oct 1997 11:13:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28378 for ; Fri, 31 Oct 1997 11:13:39 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA21334; Fri, 31 Oct 1997 12:13:23 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA25540; Fri, 31 Oct 1997 12:13:20 -0700 (MST) Date: Fri, 31 Oct 1997 12:13:20 -0700 (MST) Message-Id: <199710311913.MAA25540@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: Simon Shapiro , John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: More on LINT Kernel Failure to compile In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Had I had to compile the LINT kernel, I know how to do it. The problem is > > that I assumed (hate that word :-) that the LINT kernel is sort of standard > > sanity check for sources and is supposed to compile all by itself, without > > me ``assisting'' it. > > I thought that the LINT file was only intended to yield a maximal set of > sources, suitable for linting, and could not compile, because many of the > options chosen for lint would be mutually exclusive. No one would ever, > ever be intended to run a LINT kernel. Close. It's *supposed* to compile (and link) so you can see any errors in the system, but it will never run. Nate From owner-freebsd-current Fri Oct 31 12:14:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02267 for current-outgoing; Fri, 31 Oct 1997 12:14:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02261 for ; Fri, 31 Oct 1997 12:14:53 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id MAA23649; Fri, 31 Oct 1997 12:14:32 -0800 (PST) To: Simon Shapiro cc: John-Mark Gurney , freebsd-current@FreeBSD.ORG Subject: Re: More on LINT Kernel Failure to compile In-reply-to: Your message of "Fri, 31 Oct 1997 09:34:01 PST." Date: Fri, 31 Oct 1997 12:14:32 -0800 Message-ID: <23644.878328872@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Had I had to compile the LINT kernel, I know how to do it. The problem is > that I assumed (hate that word :-) that the LINT kernel is sort of standard > sanity check for sources and is supposed to compile all by itself, without > me ``assisting'' it. And this is entirely correct. It used to be incumbent on people to keep LINT in working order for exactly that reason and it's quite unfortunate that this has been slacked off on a bit in -current recently. It was never anyone's intention that a LINT kernel be bootable, but it was supposed to at least compile and, now that it doesn't, will be hiding any number of problems from detection in that manner. It should be fixed by whomever broke it last, to paraphrase Bruce. Jordan From owner-freebsd-current Fri Oct 31 13:29:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06205 for current-outgoing; Fri, 31 Oct 1997 13:29:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA06192 for ; Fri, 31 Oct 1997 13:28:44 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 19808 invoked by uid 1000); 31 Oct 1997 21:29:02 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <23644.878328872@time.cdrom.com> Date: Fri, 31 Oct 1997 13:29:02 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: More on LINT Kernel Failure to compile Cc: John-Mark Gurney , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 31-Oct-97 you wrote: > > Had I had to compile the LINT kernel, I know how to do it. The problem > > is > > that I assumed (hate that word :-) that the LINT kernel is sort of > > standard > > sanity check for sources and is supposed to compile all by itself, > > without > > me ``assisting'' it. > > And this is entirely correct. It used to be incumbent on people to > keep LINT in working order for exactly that reason and it's quite > unfortunate that this has been slacked off on a bit in -current > recently. It was never anyone's intention that a LINT kernel be > bootable, but it was supposed to at least compile and, now that it > doesn't, will be hiding any number of problems from detection in that > manner. It should be fixed by whomever broke it last, to paraphrase > Bruce. If no one in particular is maintainig LINT, I just volunteered. I'll add it to my short list of things to do :-) Simon From owner-freebsd-current Fri Oct 31 14:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08407 for current-outgoing; Fri, 31 Oct 1997 14:01:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08402 for ; Fri, 31 Oct 1997 14:01:48 -0800 (PST) (envelope-from bartol@salk.edu) Received: from dale.salk.edu (dale [198.202.70.112]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id OAA10749 for ; Fri, 31 Oct 1997 14:01:41 -0800 (PST) Date: Fri, 31 Oct 1997 14:01:40 -0800 (PST) From: Tom Bartol To: freebsd-current@freebsd.org Subject: kernel make failure in new sound driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just successfully did a make world after cvsupping this morning but I get a failure while trying to make the kernel with the sound driver enabled. I assume the failure has to do with the new sound driver code which was just committed this morning. I get lots of "undeclared" variable errors, a sample of which is: ../../i386/isa/sound/dev_table.c:51: `num_sound_drivers' undeclared (first use this function) etc... Thanks, Tom From owner-freebsd-current Fri Oct 31 15:36:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13024 for current-outgoing; Fri, 31 Oct 1997 15:36:47 -0800 (PST) (envelope-from owner-freebsd-current) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13018 for ; Fri, 31 Oct 1997 15:36:44 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA25088; Fri, 31 Oct 1997 16:36:23 -0700 (MST) From: Terry Lambert Message-Id: <199710312336.QAA25088@usr01.primenet.com> Subject: Re: Small Problem with Linux Emul To: kmitch@weenix.guru.org (Keith Mitchell) Date: Fri, 31 Oct 1997 23:36:22 +0000 (GMT) Cc: tlambert@primenet.com, current@freebsd.org In-Reply-To: <199710310428.XAA03075@weenix.guru.org> from "Keith Mitchell" at Oct 30, 97 11:28:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Other than you seriously digging, I have no answer; I can't repeat it. > > Hmm, would it make a difference if I only ifconfiged one of the > interfaces, yet left them both in the computer (they're on the > same card). Heh. Ask the hardware, not me... 8-). > Are you trying to replicate it with a quakeworld server or some > generic Linux net application? Generic. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Oct 31 18:29:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22557 for current-outgoing; Fri, 31 Oct 1997 18:29:52 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA22541 for ; Fri, 31 Oct 1997 18:29:45 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 26040 invoked by uid 1000); 1 Nov 1997 02:30:11 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-100797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 31 Oct 1997 18:30:11 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: Tom Bartol Subject: RE: kernel make failure in new sound driver Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Bartol; On 31-Oct-97 you wrote: > > Hi, > > I just successfully did a make world after cvsupping this morning but I > get a failure while trying to make the kernel with the sound driver > enabled. I assume the failure has to do with the new sound driver code > which was just committed this morning. I get lots of "undeclared" > variable errors, a sample of which is: > > ../../i386/isa/sound/dev_table.c:51: `num_sound_drivers' undeclared > (first > use this function) > > etc... > > Thanks, > > Tom Yup. Sick puppy... :-( --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Fri Oct 31 19:41:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26223 for current-outgoing; Fri, 31 Oct 1997 19:41:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA26213 for ; Fri, 31 Oct 1997 19:41:17 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 7673 invoked by uid 1000); 1 Nov 1997 03:41:37 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-103097 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Fri, 31 Oct 1997 19:41:37 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: Minor kernel compile warnings... Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am getting these warnings. some are trivial (and I would have loved) to fix, some require whoever wrote them to decide: ../../kern/kern_malloc.c ../../kern/kern_malloc.c: In function `malloc': ../../kern/kern_malloc.c:136: warning: passing arg 3 of `tsleep' discards `const' from pointer target type ../../kern/kern_time.c ../../kern/kern_time.c:69: warning: function declaration isn't a prototype ../../miscfs/fdesc/fdesc_vnops.c ../../miscfs/fdesc/fdesc_vnops.c: In function `fdesc_lookup': ../../miscfs/fdesc/fdesc_vnops.c:198: warning: `fd' might be used uninitialized in this function ../../miscfs/union/union_subr.c ../../miscfs/union/union_subr.c: In function `union_allocvp': ../../miscfs/union/union_subr.c:298: warning: `hash' might be used uninitialized in this function make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /usr/src/3.0/src/sys/compile/SENDERO [ I wish I knew what that means :-) ] ../../pci/pci_compat.c ../../pci/pci_compat.c: In function `pci_map_int': ../../pci/pci_compat.c:172: warning: passing arg 3 of `intr_create' from incompatible pointer type I've seen this one before. Why cannot the argument here be cast? ../../ufs/lfs/lfs_segment.c ../../ufs/lfs/lfs_segment.c: In function `lfs_vunref': ../../ufs/lfs/lfs_segment.c:1232: warning: nested extern declaration of `vnode_free_list_slock' ../../ufs/lfs/lfs_segment.c:1233: warning: nested extern declaration of `vnode_free_list' ../../i386/i386/db_interface.c ../../i386/i386/db_interface.c: In function `kdb_trap': ../../i386/i386/db_interface.c:73: warning: variable `ddb_mode' might be clobbered by `longjmp' or `vfork' ../../i386/i386/initcpu.c ../../i386/i386/initcpu.c: In function `cyrixreg': ../../i386/i386/initcpu.c:522: warning: `ccr0' might be used uninitialized in this function ../../i386/i386/initcpu.c:522: warning: `ccr4' might be used uninitialized in this function ../../i386/i386/initcpu.c:522: warning: `ccr5' might be used uninitialized in this function ../../i386/i386/initcpu.c:522: warning: `pcr0' might be used uninitialized in this function ../../i386/isa/sound/audio.c ../../i386/isa/sound/audio.c: In function `audio_poll': ../../i386/isa/sound/audio.c:446: warning: implicit declaration of function `DMAbuf_poll' ../../i386/isa/sound/dmabuf.c ../../i386/isa/sound/dmabuf.c: In function `reorganize_buffers': ../../i386/isa/sound/dmabuf.c:143: warning: implicit declaration of function `fillw' ../../i386/isa/sound/dmabuf.c: At top level: ../../i386/isa/sound/dmabuf.c:1386: warning: no previous prototype for `DMAbuf_poll' ../../i386/isa/sound/sb_dsp.c ../../i386/isa/sound/sb_dsp.c:220: warning: no previous prototype for `dsp_speaker' ../../i386/isa/syscons.c ../../i386/isa/syscons.c: In function `scioctl': ../../i386/isa/syscons.c:907: warning: `i' might be used uninitialized in this function --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Fri Oct 31 20:38:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA29464 for current-outgoing; Fri, 31 Oct 1997 20:38:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29459 for ; Fri, 31 Oct 1997 20:38:10 -0800 (PST) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id XAA26885; Fri, 31 Oct 1997 23:38:01 -0500 (EST) From: Keith Mitchell Message-Id: <199711010438.XAA26885@weenix.guru.org> Subject: Re: Small Problem with Linux Emul In-Reply-To: <199710312336.QAA25088@usr01.primenet.com> from Terry Lambert at "Oct 31, 97 11:36:22 pm" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 31 Oct 1997 23:38:00 -0500 (EST) Cc: current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > generic Linux net application? > > Generic. Ok, I compiled both telnet and archie for linux and discovered the DNS problem. If I telnet to a name, then it doesn't work. If I telnet to an IP it works fine. The Quake server uses udp and the IP address logged may be through DNS calls (I really don't know since the source isn't avail). Archie fails in a similar way. the Quake server is probably suffering from the same problem. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved From owner-freebsd-current Fri Oct 31 22:29:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03704 for current-outgoing; Fri, 31 Oct 1997 22:29:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03692 for ; Fri, 31 Oct 1997 22:29:33 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (Ib+qsWQcNwR0Ir/xtINsRszIbkOnDjg3@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id IAA29926; Sat, 1 Nov 1997 08:29:40 +0200 (SAT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (PP7wKHm8LWKnTL9YT5+rc1JvfFXlXGYH@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id IAA05940; Sat, 1 Nov 1997 08:29:34 +0200 (SAST) Message-Id: <199711010629.IAA05940@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: Simon Shapiro cc: Tom Bartol , freebsd-current@FreeBSD.ORG Subject: Re: kernel make failure in new sound driver Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Nov 1997 08:29:33 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > I just successfully did a make world after cvsupping this morning but I > > get a failure while trying to make the kernel with the sound driver > > enabled. I assume the failure has to do with the new sound driver code > > which was just committed this morning. I get lots of "undeclared" > > variable errors, a sample of which is: > > > > ../../i386/isa/sound/dev_table.c:51: `num_sound_drivers' undeclared > > (first > > use this function) > > Yup. Sick puppy... :-( Please read commit mail. CVS hosed a commit, and it took a few hours to correct. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Sat Nov 1 00:03:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA06705 for current-outgoing; Sat, 1 Nov 1997 00:03:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA06688 for ; Sat, 1 Nov 1997 00:03:00 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 1303 invoked from network); 1 Nov 1997 08:02:58 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 1 Nov 1997 08:02:58 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.7/8.8.7) id AAA02500 for freebsd-current@freebsd.org; Sat, 1 Nov 1997 00:02:58 -0800 (PST) (envelope-from scottm) Date: Sat, 1 Nov 1997 00:02:58 -0800 (PST) From: Scott Michel Message-Id: <199711010802.AAA02500@mordred.cs.ucla.edu> To: freebsd-current@freebsd.org Subject: missing pages on cache queue: 1 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Any idea how to track down this little piece o'nastiness? Oct 31 23:59:39 mordred /kernel: vm_page_alloc(ZERO): missing pages on cache queue: 1 Oct 31 23:59:44 mordred last message repeated 3 times I was running python 1.4 at the time, and had hit ^c to terminate it. Other than that, not much else was going on at the time (other than X and a shell.) -scooter From owner-freebsd-current Sat Nov 1 04:07:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA16777 for current-outgoing; Sat, 1 Nov 1997 04:07:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp2.xs4all.nl (smtp2.xs4all.nl [194.109.6.52]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA16770 for ; Sat, 1 Nov 1997 04:07:27 -0800 (PST) (envelope-from plm@muon.xs4all.nl) Received: from asterix.xs4all.nl (root@asterix.xs4all.nl [194.109.6.11]) by smtp2.xs4all.nl (8.8.6/XS4ALL) with ESMTP id NAA03909 for ; Sat, 1 Nov 1997 13:07:25 +0100 (CET) Received: from muon.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.8.6/8.8.6) with UUCP id NAA16103 for freebsd-current@freebsd.org; Sat, 1 Nov 1997 13:06:26 +0100 (MET) Received: (from plm@localhost) by muon.xs4all.nl (8.8.7/8.7.3) id LAA18719; Sat, 1 Nov 1997 11:28:58 +0100 (MET) To: freebsd-current@freebsd.org Subject: Re: sgmlfmt - again... References: <87iuueo077.fsf@totally-fudged-out-message-id> From: Peter Mutsaers Date: 01 Nov 1997 11:28:58 +0100 In-Reply-To: "Jordan K. Hubbard"'s message of Thu, 30 Oct 1997 13:42:48 -0800 Message-ID: <8767qc29hx.fsf@muon.xs4all.nl> Lines: 27 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> On Thu, 30 Oct 1997 13:42:48 -0800, "Jordan K. Hubbard" >> said: >> sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml >> sgmlfmt: not found >> *** Error code 1 >> >> Yuck. sgmlfmt is not installed in /usr/bin of the build :-( JKH> And hasn't been for months now. You need to install sgmlfmt JKH> from the port version (see ports/textproc for the appropriate JKH> utilities) in order to build the docs (which have also been JKH> unbundled for months now). Which is very unfortunate, because building sgmlfmt depends on numerous other programs, that require quite some space (and RAM) to be built. I several times could'nt install it because of lack of swapspace, while I have 48MB RAM + 81MB of swap. It would be very nice if the current (latin1) versions of the FAQ and Handbook would always be available by other means, so that I no longer need to have sgmlfmt. -- /\_/\ ( o.o ) Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know ) ^ ( plm@xs4all.nl | the Netherlands | what I'm doing. From owner-freebsd-current Sat Nov 1 05:50:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA19661 for current-outgoing; Sat, 1 Nov 1997 05:50:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA19656 for ; Sat, 1 Nov 1997 05:50:49 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id IAA04263; Sat, 1 Nov 1997 08:50:46 -0500 (EST) Date: Sat, 1 Nov 1997 08:50:46 -0500 (EST) From: John Fieber To: Peter Mutsaers cc: freebsd-current@FreeBSD.ORG Subject: Re: sgmlfmt - again... In-Reply-To: <8767qc29hx.fsf@muon.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1 Nov 1997, Peter Mutsaers wrote: > Which is very unfortunate, because building sgmlfmt depends on > numerous other programs, that require quite some space (and RAM) to be > built. This is why the tools were removed from the source tree--The bloat is unjustified. Check your memory limits (ulimit). You may need to boost them a bit to compile jade/sp. Failing that, you can install the package. -john From owner-freebsd-current Sat Nov 1 14:58:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12713 for current-outgoing; Sat, 1 Nov 1997 14:58:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA12703 for ; Sat, 1 Nov 1997 14:58:45 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 1229 invoked by uid 1000); 1 Nov 1997 22:59:15 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-103097 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sat, 01 Nov 1997 14:59:15 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: panic: free vnode isn't Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On today's -current. Willing to do anything moral and legal to help eradicate this one. --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sat Nov 1 22:22:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA02838 for current-outgoing; Sat, 1 Nov 1997 22:22:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gforce.bellsouth.net (host-32-96-78-76.msy.bellsouth.net [32.96.78.76]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA02831 for ; Sat, 1 Nov 1997 22:22:02 -0800 (PST) (envelope-from glenn@gforce.bellsouth.net) Received: from gforce.bellsouth.net (localhost.bellsouth.net [127.0.0.1]) by gforce.bellsouth.net (8.8.7/8.8.7) with ESMTP id AAA01858 for ; Sun, 2 Nov 1997 00:20:18 -0600 (CST) (envelope-from glenn@gforce.bellsouth.net) Message-Id: <199711020620.AAA01858@gforce.bellsouth.net> X-Mailer: exmh version 2.0zeta 7/24/97 From: Glenn Johnson To: freebsd-current@freebsd.org Subject: CDROM no longer working after 'make world' Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Nov 1997 00:20:17 -0600 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I just did a cvsup followed by a 'make world' today for -current. After doing this, I can no longer access my CD-ROM drive. I get a 'device not configured' message when I try to mount a CD. It is a Mitsumi FX001DE ATAPI drive that was working fine before the 'make world'. I rebuilt the device using MAKEDEV but this did not help. -- Glenn Johnson gljohns@bellsouth.net From owner-freebsd-current Sat Nov 1 22:43:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03754 for current-outgoing; Sat, 1 Nov 1997 22:43:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA03746 for ; Sat, 1 Nov 1997 22:43:25 -0800 (PST) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 13663 invoked by uid 1000); 2 Nov 1997 06:43:41 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-103097 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199711020620.AAA01858@gforce.bellsouth.net> Date: Sat, 01 Nov 1997 22:43:41 -0800 (PST) Organization: Atlas Telecom From: Simon Shapiro To: Glenn Johnson Subject: RE: CDROM no longer working after 'make world' Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Glenn Johnson; On 02-Nov-97 you wrote: > Greetings, > > I just did a cvsup followed by a 'make world' today for -current. After > doing > this, I can no longer access my CD-ROM drive. I get a 'device not > configured' > message when I try to mount a CD. It is a Mitsumi FX001DE ATAPI drive > that was > working fine before the 'make world'. I rebuilt the device using MAKEDEV > but > this did not help. Yup. Same kernel configuration, same machine, same problem. You will notice that dd from the device does work. Looks like the cd9660 filesystem is not well today. --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sat Nov 1 22:59:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA04288 for current-outgoing; Sat, 1 Nov 1997 22:59:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA04283 for ; Sat, 1 Nov 1997 22:59:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA12383; Sat, 1 Nov 1997 22:59:10 -0800 (PST) To: Glenn Johnson cc: freebsd-current@FreeBSD.ORG Subject: Re: CDROM no longer working after 'make world' In-reply-to: Your message of "Sun, 02 Nov 1997 00:20:17 CST." <199711020620.AAA01858@gforce.bellsouth.net> Date: Sat, 01 Nov 1997 22:59:10 -0800 Message-ID: <12379.878453950@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just did a cvsup followed by a 'make world' today for -current. After doing > this, I can no longer access my CD-ROM drive. I get a 'device not configured' > message when I try to mount a CD. It is a Mitsumi FX001DE ATAPI drive that wa But this makes no sense since: 1. The ATAPI CDROM driver is in your kernel. 2. `make world' does not update your kernel. I would suggest that something else happened here. Jordan From owner-freebsd-current Sat Nov 1 23:19:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA05108 for current-outgoing; Sat, 1 Nov 1997 23:19:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gforce.bellsouth.net (host-32-96-78-107.msy.bellsouth.net [32.96.78.107]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA05100 for ; Sat, 1 Nov 1997 23:19:07 -0800 (PST) (envelope-from glenn@gforce.bellsouth.net) Received: from gforce.bellsouth.net (localhost.bellsouth.net [127.0.0.1]) by gforce.bellsouth.net (8.8.7/8.8.7) with ESMTP id BAA02221; Sun, 2 Nov 1997 01:16:55 -0600 (CST) (envelope-from glenn@gforce.bellsouth.net) Message-Id: <199711020716.BAA02221@gforce.bellsouth.net> X-Mailer: exmh version 2.0zeta 7/24/97 From: Glenn Johnson To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: CDROM no longer working after 'make world' In-reply-to: Your message of "Sat, 01 Nov 1997 22:59:10 PST." <12379.878453950@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Nov 1997 01:16:55 -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I just did a cvsup followed by a 'make world' today for -current. After doing > > this, I can no longer access my CD-ROM drive. I get a 'device not configured' > > message when I try to mount a CD. It is a Mitsumi FX001DE ATAPI drive that wa > > But this makes no sense since: > > 1. The ATAPI CDROM driver is in your kernel. > > 2. `make world' does not update your kernel. > > I would suggest that something else happened here. > > Jordan > Oh yeah, I forgot to mention that I also rebuilt the kernel after the 'make world'. I do that routinely after a 'make world' so I tend to think of it as one job, but I should have specified that. Sorry. -- Glenn Johnson gljohns@bellsouth.net