From owner-freebsd-stable Sun Jul 16 4:27:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 5E0F237B76D for ; Sun, 16 Jul 2000 04:27:04 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 15295962 invoked from network); 16 Jul 2000 11:27:02 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 16 Jul 2000 11:27:02 -0000 Message-ID: <39719CC5.3554B6C5@cybercable.fr> Date: Sun, 16 Jul 2000 13:30:13 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh , freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: config and config -r References: <3970AB23.F76B05CB@cybercable.fr> <200007160541.XAA50804@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <3970AB23.F76B05CB@cybercable.fr> Maxime Henrion writes: > : But after rebooting on this new kernel, I had a page fault before > : any kernel message :/ Is there anything to check in order to know if I > : can use a config instead of a config -r ? If using a config without the > : -r option is dangerous, I think it shouldn't be the default. Is it the > : case ? > > Make depend is required if you ever want to build kernels more than > once. > > Warner Of course, I did a make depend ! I think that if config could be dangerous this way, -r should be its default behaviour. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 4:28:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id D18AA37BD8C for ; Sun, 16 Jul 2000 04:28:27 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id EAA01206; Sun, 16 Jul 2000 04:37:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007161137.EAA01206@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andy Cc: stable@FreeBSD.ORG Subject: Re: Hardware Info In-reply-to: Your message of "Fri, 14 Jul 2000 23:45:19 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Jul 2000 04:37:19 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 14 Jul 2000, Mike Smith wrote: > > > > I use the dmesg.boot as allocated resources, but without counters > > > how do you know how much they have been used? Sure you can estimate, but > > > is there something such as vmstat -i for all allocated resources? > > > > Can you be more specific about "how much they have been used"? > > vmstat -i generates the following on my system: > > interrupt total rate > clk0 irq0 19762681 99 > rtc0 irq8 25293658 127 > pci irq10 418418 2 > wdc0 irq14 964519 4 > Total 46439276 234 > > Is it possible to include DMA, I/O, and other counts in the > output? You might be able to add resource usage for legacy ISA DMA to those numbers, but nobody (sane) uses ISA DMA anymore, and none of the other I/O activities can be cost-effectively tracked. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 4:55:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id AE4E137B726 for ; Sun, 16 Jul 2000 04:55:27 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 15267933 invoked from network); 16 Jul 2000 11:55:25 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 16 Jul 2000 11:55:25 -0000 Message-ID: <3971A36C.AAE5C436@cybercable.fr> Date: Sun, 16 Jul 2000 13:58:36 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: config and config -r Content-Type: multipart/mixed; boundary="------------98842E9E9E87ED802C13B9BA" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------98842E9E9E87ED802C13B9BA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------98842E9E9E87ED802C13B9BA Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3971A336.86490A09@cybercable.fr> Date: Sun, 16 Jul 2000 13:57:42 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Larry Rosenman Subject: Re: config and config -r References: <200007161136.e6GBaxN00600@lerami.lerctr.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The problem is that I _DID_ a make depend after the config -r, and this haven't prevent me to get a kernel which panic'ed. Larry Rosenman wrote: > config without the -r reminds you to run a make depend. > > Larry > > Warner Losh wrote: > > > > > In message <3970AB23.F76B05CB@cybercable.fr> Maxime Henrion writes: > > > : But after rebooting on this new kernel, I had a page fault before > > > : any kernel message :/ Is there anything to check in order to know if I > > > : can use a config instead of a config -r ? If using a config without the > > > : -r option is dangerous, I think it shouldn't be the default. Is it the > > > : case ? > > > > > > Make depend is required if you ever want to build kernels more than > > > once. > > > > > > Warner > > > > Of course, I did a make depend ! > > I think that if config could be dangerous this way, -r should be its default > > behaviour. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 --------------98842E9E9E87ED802C13B9BA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 8:46:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 1885C37B585 for ; Sun, 16 Jul 2000 08:46:08 -0700 (PDT) (envelope-from jim@siteplus.net) Received: from discover.siteplus.net (1Cust81.tnt9.chattanooga.tn.da.uu.net [63.39.120.81]) by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id IAA18643 for ; Sun, 16 Jul 2000 08:46:05 -0700 (PDT) Date: Sun, 16 Jul 2000 11:46:11 -0400 (EDT) From: Jim Weeks To: freebsd-stable@freebsd.org Subject: ed0 on laptop Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will someone please refresh my memory. I finally got around to upgrading my laptop to 4.0-Stable and am having trouble making the kernel recognize my LinkSys EC2T as ed0. It insists on being ed1. Of course if I comment out ed0 in the config file I no longer have the drivers. I don't remember this problem in 3.4 Any suggestions as to what I have missed? -- Jim Weeks -------- A mind is a terrible thing to lose! How I miss mine.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 9: 9:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id DF2FA37BDD5 for ; Sun, 16 Jul 2000 09:09:10 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id DF273137F07 for ; Sun, 16 Jul 2000 12:09:09 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id MAA63748; Sun, 16 Jul 2000 12:09:04 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14705.56864.306311.237436@trooper.velocet.net> Date: Sun, 16 Jul 2000 12:09:04 -0400 (EDT) To: freebsd-stable@freebsd.org Subject: Re: ed0 and isa cards on 4.x X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Have anyone 4.x working with an ISA card and the ed0 device? I can't >>believe that it can be broken for so long without anyone noticing. I >>have been using 4.x on lots of machines here, but all of them with >>pci ethernet cards. >> >>I have tried to install a recent 4.0 snap on a machine with a SMC8216 >>card, but everytime I got the dreaded "ed0 device timeout" message. >>I have tried different interrupts, changed cards, but nothing helped. >>I even tried it on another machine and had the same results. I even >>tried 4.0-RELEASE, but got the same results. Then I tried 3.5-RELEASE >>and that worked without a problem. > Hmmm. That's VERY weird. I'll see if I can find an ISA card around here >and test it out in the lab. It definately sounds like an interrupt problem. >Are you sure that you have your kernel config file right? I just had a friend trying to install a laptop with a pccard ethernet card that was probing as ed1. We were getting the "ed1 device timeout" messages ... and I justed chalked it up to flakey pccard support until now. We did doubly and triply verify the interupt. It was probing as IRQ 3 and was refusing to take an interupt more than 7. IRQ 3 was free (sio1 didn't probe as present) ... and this wasn't working. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 9:14:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 073AE37BE2B for ; Sun, 16 Jul 2000 09:14:57 -0700 (PDT) (envelope-from jim@siteplus.net) Received: from discover.siteplus.net (1Cust81.tnt9.chattanooga.tn.da.uu.net [63.39.120.81]) by scaup.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id JAA15100 for ; Sun, 16 Jul 2000 09:14:55 -0700 (PDT) Date: Sun, 16 Jul 2000 12:15:03 -0400 (EDT) From: Jim Weeks To: freebsd-stable@freebsd.org Subject: Re: ed0 on laptop In-Reply-To: <3971DA5D.551AFF4@thehousleys.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, James Housley wrote: > Remove the definition of ISA? ....... > > Jim > -- > Nothing is fool proof, because fools are too ingenious. > Good Grief. Two heads are always better than one ;_> Thanks, -- Jim Weeks -------- A mind is a terrible thing to lose! How I miss mine.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 9:15:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dcnv.com (mail.dcnv.com [216.33.117.136]) by hub.freebsd.org (Postfix) with ESMTP id 4487837BEB6 for ; Sun, 16 Jul 2000 09:15:14 -0700 (PDT) (envelope-from aedmonds@digitalconvergence.com) Received: from digitalconvergence.com (dallas [207.158.100.67]) by mail.dcnv.com (8.9.3/8.9.3) with ESMTP id LAA47096 for ; Sun, 16 Jul 2000 11:13:55 -0500 (CDT) (envelope-from aedmonds@digitalconvergence.com) Message-ID: <3971DF90.B52A76A7@digitalconvergence.com> Date: Sun, 16 Jul 2000 11:15:12 -0500 From: Alan Edmonds X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: ed0 and isa cards on 4.x References: <14705.56864.306311.237436@trooper.velocet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know I had to change the settings in pccard.conf for my laptop (Dell Lattiude) to recognize the ethernet card. Ensure the memory range and IRQs are correct. I believe the timeout messages are an indication of incorrect interrupt being assigned. -- Alan Edmonds Director of International Technology DigitalConvergence.:Com aedmonds@digitalconvergence.com Phone: +1-214-292-6040 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 9:19:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 2517137BCC1 for ; Sun, 16 Jul 2000 09:19:32 -0700 (PDT) (envelope-from bobj@atlantic.net) Received: from garbonzo.hos.ufl.edu (dialup12.ifas.ufl.edu [128.227.242.52]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id MAA43476 for ; Sun, 16 Jul 2000 12:19:29 -0400 Received: from nancy.cisi.com (nancy.cisi.com [192.168.0.131]) by garbonzo.hos.ufl.edu (8.9.3/8.9.3) with SMTP id MAA45224 for ; Sun, 16 Jul 2000 12:16:27 -0400 (EDT) (envelope-from bobj@atlantic.net) Message-Id: <3.0.6.32.20000716121615.00a2a320@rio.atlantic.net> X-Sender: bobj@rio.atlantic.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 16 Jul 2000 12:16:15 -0400 To: freebsd-stable@freebsd.org From: Bob Johnson Subject: Can't boot if PCCARD drive listed in fstab Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed the 20000715 STABLE snapshot in my old 486 laptop and discovered that if there is a PCMCIA hard drive listed in /etc/fstab the system won't boot. When it checks filesystems during boot, it complains that the PCMCIA drive is not configured, and drops to single user mode. This happens even if the drive has the noauto option in fstab. This means that if a PCMCIA drive is on the system during install, the system won't boot after the install. It also means I can't even have the PCMCIA drive in fstab to make it easy to mount after boot. It seems to me that this is a bit of a bug, that a drive listed as noauto shouldn't be checked on boot. This system has been running 4.0RC3 without this problem, and I updated it from a 4.0-STABLE snapshot around July 7 or so without a problem. The install from the July 15 snap(the one having a problem) was a complete re-install from scratch, using the July 15 snap floppies and FTP from releng4. Am I missing something obvious, or should I submit a PR? -- Bob +-------------------------------------------------------- | Bob Johnson | bobj@atlantic.net +-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 9:34:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 27A0237BFA8 for ; Sun, 16 Jul 2000 09:34:20 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 480369B1C; Sun, 16 Jul 2000 12:34:19 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 3B531BA11; Sun, 16 Jul 2000 12:34:19 -0400 (EDT) Date: Sun, 16 Jul 2000 12:34:19 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Bob Johnson Cc: freebsd-stable@freebsd.org Subject: Re: Can't boot if PCCARD drive listed in fstab In-Reply-To: <3.0.6.32.20000716121615.00a2a320@rio.atlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Bob Johnson wrote: > I installed the 20000715 STABLE snapshot in my old 486 laptop > and discovered that if there is a PCMCIA hard drive listed in > /etc/fstab the system won't boot. > > When it checks filesystems during boot, it complains that the > PCMCIA drive is not configured, and drops to single user > mode. > > This happens even if the drive has the noauto option in > fstab. > What is the Pass # field set to. Anything other than 0 will cause fsck to try and check the filesystem. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 9:51: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from q.closedsrc.org (ip233.gte15.rb1.bel.nwlink.com [209.20.244.233]) by hub.freebsd.org (Postfix) with ESMTP id 0910F37B7ED for ; Sun, 16 Jul 2000 09:50:47 -0700 (PDT) (envelope-from lplist@q.closedsrc.org) Received: from localhost (lplist@localhost) by q.closedsrc.org (8.10.2/8.10.2) with ESMTP id e6GGn4N06236; Sun, 16 Jul 2000 09:49:04 -0700 (PDT) (envelope-from lplist@q.closedsrc.org) Date: Sun, 16 Jul 2000 09:49:04 -0700 (PDT) From: Linh Pham To: Jim Weeks Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ed0 on laptop In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG But two idiots makes for a headache! // Linh Pham // // Proud supporter of FreeBSD and OpenBSD // FreeBSD - http://www.freebsd.org // OpenBSD - http://www.openbsd.org /* "Oregon, n.: Eighty billion gallons of water with no place to go on Saturday night." */ On Sun, 16 Jul 2000, Jim Weeks wrote: > > On Sun, 16 Jul 2000, James Housley wrote: > > > Remove the definition of ISA? ....... > > > > Jim > > -- > > Nothing is fool proof, because fools are too ingenious. > > > > Good Grief. Two heads are always better than one ;_> > > Thanks, > > -- > Jim Weeks > -------- A mind is a terrible thing to lose! How I miss mine.. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 10: 2:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BB68C37B538; Sun, 16 Jul 2000 10:02:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA76140; Sun, 16 Jul 2000 11:02:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA54309; Sun, 16 Jul 2000 11:02:20 -0600 (MDT) Message-Id: <200007161702.LAA54309@harmony.village.org> To: Maxime Henrion Subject: Re: config and config -r Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org In-reply-to: Your message of "Sun, 16 Jul 2000 13:30:13 +0200." <39719CC5.3554B6C5@cybercable.fr> References: <39719CC5.3554B6C5@cybercable.fr> <3970AB23.F76B05CB@cybercable.fr> <200007160541.XAA50804@harmony.village.org> Date: Sun, 16 Jul 2000 11:02:20 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39719CC5.3554B6C5@cybercable.fr> Maxime Henrion writes: : Of course, I did a make depend ! : I think that if config could be dangerous this way, -r should be its default : behaviour. No. I've done literally 1000's of kernel builds and have never, ever had a problem with config's output that would have been solved by doing a config -r. I did used to use config -r to solve these problems, but found that make depend followed by make or worst case make clean (in the case of .o file corruption) followed by a make will fix these problems. I've not used config -r except maybe once or twice in the last two years. Both times it was because the previous config ran out of disk space and created too many zero length files which a new config didn't clean up exactly right. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 10: 7:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 959DE37BBFF for ; Sun, 16 Jul 2000 10:07:32 -0700 (PDT) (envelope-from bobj@atlantic.net) Received: from garbonzo.hos.ufl.edu (dialup6.ifas.ufl.edu [128.227.242.46]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id NAA57590; Sun, 16 Jul 2000 13:07:29 -0400 Received: from nancy.cisi.com (nancy.cisi.com [192.168.0.131]) by garbonzo.hos.ufl.edu (8.9.3/8.9.3) with SMTP id NAA45273; Sun, 16 Jul 2000 13:06:30 -0400 (EDT) (envelope-from bobj@atlantic.net) Message-Id: <3.0.6.32.20000716130617.00a376c0@rio.atlantic.net> X-Sender: bobj@rio.atlantic.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 16 Jul 2000 13:06:17 -0400 To: "Chris D. Faulhaber" From: Bob Johnson Subject: Re: Can't boot if PCCARD drive listed in fstab Cc: freebsd-stable@freebsd.org In-Reply-To: References: <3.0.6.32.20000716121615.00a2a320@rio.atlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:34 PM 07/16/2000 -0400, Chris D. Faulhaber wrote: >On Sun, 16 Jul 2000, Bob Johnson wrote: > >> I installed the 20000715 STABLE snapshot in my old 486 laptop >> and discovered that if there is a PCMCIA hard drive listed in >> /etc/fstab the system won't boot. >> >> When it checks filesystems during boot, it complains that the >> PCMCIA drive is not configured, and drops to single user >> mode. >> >> This happens even if the drive has the noauto option in >> fstab. >> > >What is the Pass # field set to. Anything other than 0 will cause fsck to >try and check the filesystem. Aha! Thanks, that fixed it. I wonder why I never ran into that problem before? I guess it's because I didn't let sysinstall set up the PCMCIA filesystem in the past, and somehow I set it up right when I did it. So now the problem is to figure out how to get sysinstall to correctly set up the PCMCIA filesystem entry in fstab when it is used during the install. Anyone who tries to do what I tried to do (have it put /usr/src on an external drive during install) will end up with a system that doesn't boot until they edit fstab. -- Bob > >----- >Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org >-------------------------------------------------------- >FreeBSD: The Power To Serve - http://www.FreeBSD.org > > +-------------------------------------------------------- | Bob Johnson | bobj@atlantic.net +-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 10:13:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 860AB37B719; Sun, 16 Jul 2000 10:13:19 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000716171318.AEW11071.mail.rdc1.il.home.com@math.missouri.edu>; Sun, 16 Jul 2000 10:13:18 -0700 Message-ID: <3971ECE2.6639D65A@math.missouri.edu> Date: Sun, 16 Jul 2000 12:12:02 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: Maxime Henrion Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: config and config -r References: <3970AB23.F76B05CB@cybercable.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a similar problem once when I changed the processor on my motherboard from a 486 to a 586. I recompiled the kernel but I also got those page faults. I asked on these newsgroups and people suggested the processor was broken. Then I tried config -r (well I didn't know the -r option so I did the equivalent - deleting the compile/XXX directory) and then it worked great. I think that config -r has to be done very occasionally. I guess when it has to be done, it is obvious. Maxime Henrion wrote: > > Hello, > > .......... > > As I didn't want to recompile the whole stuff, I used a config and > not a config -r to build a new kernel, after having changed its > configuration. I removed several devices and I thought that won't cause > any problem, as the objects files for these devices won't be linked into > the kernel. > But after rebooting on this new kernel, I had a page fault before > any kernel message :/ Is there anything to check in order to know if I > can use a config instead of a config -r ? If using a config without the > -r option is dangerous, I think it shouldn't be the default. Is it the > case ? > -- Stephen Montgomery-Smith Department of Mathematics, University of Missouri, Columbia, MO 65211 Phone 573-882-4540, fax 573-882-1869 http://www.math.missouri.edu/~stephen stephen@math.missouri.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 10:48:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B0F2037B5F9; Sun, 16 Jul 2000 10:48:43 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id KAA33926; Sun, 16 Jul 2000 10:48:43 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id KAA37326; Sun, 16 Jul 2000 10:48:43 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200007161748.KAA37326@realtime.exit.com> Subject: Will the urio dev make it to -stable? To: current@freebsd.org Date: Sun, 16 Jul 2000 10:48:43 -0700 (PDT) Cc: stable@freebsd.org Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ...any time soon? It's been in current since 3/16 so it would seem MFCable, but what do I know. Nick? (I run 4-stable and don't plan to run -current any time soon, _and_ I want to buy a Rio 500, but not if I can't hook it to FreeBSD.) Sent to both -current and -stable as both lists seem relevant. Please limit followups, though. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11: 7:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 13FBA37B61D for ; Sun, 16 Jul 2000 11:07:52 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000716180750.BFAA11071.mail.rdc1.il.home.com@math.missouri.edu> for ; Sun, 16 Jul 2000 11:07:50 -0700 Message-ID: <3971F9AA.CB581E24@math.missouri.edu> Date: Sun, 16 Jul 2000 13:06:34 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: What makes the first line in /etc/motd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It I look at the first line in /etc/motd, I see FreeBSD 4.1-RC (MONT) #0: Sat Jul 15 22:45:48 CDT 2000 I am curious is to what program does this. Really, what I am asking is: how do I find out what version of FreeBSD I am using, just by looking at the sources, without building them? When FreeBSD becomes 4.1-STABLE, in which file should I look to see this? Stephen -- Stephen Montgomery-Smith Department of Mathematics, University of Missouri, Columbia, MO 65211 Phone 573-882-4540, fax 573-882-1869 http://www.math.missouri.edu/~stephen stephen@math.missouri.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11: 9: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id DF65237B6C8; Sun, 16 Jul 2000 11:08:58 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 7A964195F4; Sun, 16 Jul 2000 13:08:57 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id NAA53336; Sun, 16 Jul 2000 13:08:57 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Sun, 16 Jul 2000 13:08:52 -0500 From: "Jacques A. Vidrine" To: arnold Cc: freebsd-stable@freebsd.org, markm@freebsd.org Subject: Re: buildworld kerberos5 broken? Message-ID: <20000716130852.A53314@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , arnold , freebsd-stable@freebsd.org, markm@freebsd.org References: <397103DB.2AB0CE48@linuxmail.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <397103DB.2AB0CE48@linuxmail.org>; from arnee@linuxmail.org on Sat, Jul 15, 2000 at 05:37:48PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IIRC, There is a dependency problem ... you cannot MAKE_KERBEROS5 without MAKE_KERBEROS4. You may even need to have Kerberos IV _installed_ before you attempt to MAKE_KERBEROS5-- I'm not sure. This is on my long to-do list to look into, and it is probably on Mark's, too. -- Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On Sat, Jul 15, 2000 at 05:37:48PM -0700, arnold wrote: > stable cvsup as of 7/15/2000 15:45 > > i have been getting this error for the past week with 4.0 stable. > > cmp -s asn1_Key.x asn1_Key.c 2> /dev/null || cp asn1_Key.x asn1_Key.c > > cmp -s asn1_HDBFlags.x asn1_HDBFlags.c 2> /dev/null || cp > asn1_HDBFlags.x asn1_HDBFlags.c > cmp -s asn1_hdb_entry.x asn1_hdb_entry.c 2> /dev/null || cp > asn1_hdb_entry.x asn1_hdb_entry.c > cmp -s asn1_Salt.x asn1_Salt.c 2> /dev/null || cp asn1_Salt.x > asn1_Salt.c > cmp -s asn1_Event.x asn1_Event.c 2> /dev/null || cp asn1_Event.x > asn1_Event.c > rm -f .depend > mkdep -f .depend -a > -I/usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/include > -I/usr/src/kerberos5/lib/libhdb/../../include > -I/usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/krb5 > -I/usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb > -I/usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/asn1 > -I/usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/roken > -I/usr/obj/usr/src/kerberos5/lib/libhdb > -I/usr/obj/usr/src/kerberos5/lib/libhdb/../../lib/libasn1 > -I/usr/src/kerberos5/lib/libhdb/../../include > -I/usr/src/kerberos5/lib/libhdb/../../include -DHAVE_CONFIG_H -DINET6 > -I/usr/obj/usr/src/i386/usr/include > /usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb/keytab.c > /usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb/hdb.c > /usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb/common.c > /usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb/db.c > /usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb/ndbm.c > /usr/src/kerberos5/lib/libhdb/../../../crypto/heimdal/lib/hdb/print.c > hdb_err.c asn1_Key.c asn1_Event.c asn1_HDBFlags.c asn1_hdb_entry.c > asn1_Salt.c > cd /usr/src/kerberos5/lib/libhdb; make _EXTRADEPEND > ===> libkrb5 > test -e /usr/obj/usr/src/kerberos5/lib/libkrb5/asn1_err.et || ln -sf > /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1/asn1_err.et > > rm -f .depend > compile_et asn1_err.et > mkdep -f .depend -a > -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 > -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1 > -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/des > -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/roken > -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/include > -I/usr/obj/usr/src/kerberos5/lib/libkrb5/../../lib/libkrb5 > -I/usr/obj/usr/src/kerberos5/lib/libkrb5/../../lib/libasn1 > -I/usr/src/kerberos5/lib/libkrb5/../../include > -I/usr/src/kerberos5/lib/libkrb5/../../include -DHAVE_CONFIG_H -DINET6 > -I/usr/obj/usr/src/i386/usr/include > /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/des/rc4_skey.c > > ......... > /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/keytab_krb4.c:35: > krb.h: No such file or directory > mkdep: compile failed > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11:10:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.utfors.se (mail.utfors.se [195.58.103.125]) by hub.freebsd.org (Postfix) with ESMTP id 180FF37B7E5 for ; Sun, 16 Jul 2000 11:10:05 -0700 (PDT) (envelope-from watchman@ludd.luth.se) Received: from ludd.luth.se (md4692041.utfors.se [212.105.32.65]) by mail.utfors.se (8.8.8/8.8.8) with ESMTP id UAA17381; Sun, 16 Jul 2000 20:09:46 +0200 (MET DST) Message-ID: <3971FA68.3A3C5F17@ludd.luth.se> Date: Sun, 16 Jul 2000 20:09:44 +0200 From: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Organization: Acne X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en-US MIME-Version: 1.0 To: clefevre@citeweb.net Cc: stable@FreeBSD.ORG Subject: Parallel kernel make Was Re: kernel.debug (was Re: HEADS UP! Always use the 'make buildkernel' target to make your kernels) References: <396F4463.978AE0DA@newsguy.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Cyrille Lefevre wrote: > what about to compile a kernel w/ debugging informations from buildkernel target ? > and about parallel make ? Just for kicks I tried doing a 'make -j4 buildkernel' with KERNEL=SNP40 in /etc/make.conf and /boot/loader.conf. It works, that is the make finished without crashing. I dunno if the binary works, nor if the compile was substantially faster. So, superficially, parallel make of a kernel does work. It sure consumed a lot of resources for a few minutes though. My SETI run ran sloowly. -- Cheers! Joachim - Alltid i harmonisk svängning --- FairLight ------ FairLight ------ FairLight ------ FairLight --- Joachim Strömbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47 Web: http://www.ludd.luth.se/~watchman --------------- Spamfodder: regeringen@regeringen.se --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11:15:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id C31C137B6C8 for ; Sun, 16 Jul 2000 11:15:20 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 4CCAC85D; Sun, 16 Jul 2000 11:15:20 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id LAA28829; Sun, 16 Jul 2000 11:15:19 -0700 (PDT) Message-ID: <3971FBB7.D3BB1C82@cup.hp.com> Date: Sun, 16 Jul 2000 11:15:19 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Montgomery-Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: What makes the first line in /etc/motd References: <3971F9AA.CB581E24@math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Montgomery-Smith wrote: > > It I look at the first line in /etc/motd, I see > > FreeBSD 4.1-RC (MONT) #0: Sat Jul 15 22:45:48 CDT 2000 > > I am curious is to what program does this. uname(1) > Really, what I am asking is: how do I find out what version > of FreeBSD I am using, just by looking at the sources, without > building them? When FreeBSD becomes 4.1-STABLE, in which file > should I look to see this? man 1 uname -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11:22:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id EC7B237B872 for ; Sun, 16 Jul 2000 11:22:34 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000716182234.BMLQ11071.mail.rdc1.il.home.com@math.missouri.edu>; Sun, 16 Jul 2000 11:22:34 -0700 Message-ID: <3971FD1E.21330210@math.missouri.edu> Date: Sun, 16 Jul 2000 13:21:18 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: Marcel Moolenaar Cc: freebsd-stable@FreeBSD.ORG Subject: Re: What makes the first line in /etc/motd References: <3971F9AA.CB581E24@math.missouri.edu> <3971FBB7.D3BB1C82@cup.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, my question was not clear. I did not wish to know what version of FreeBSD binaries I was using. I wanted to know what version of FreeBSD I have in my /usr/src directory, given that /usr/src is more recent than my binaries. Marcel Moolenaar wrote: > > Stephen Montgomery-Smith wrote: > > > > It I look at the first line in /etc/motd, I see > > > > FreeBSD 4.1-RC (MONT) #0: Sat Jul 15 22:45:48 CDT 2000 > > > > I am curious is to what program does this. > > uname(1) > > > Really, what I am asking is: how do I find out what version > > of FreeBSD I am using, just by looking at the sources, without > > building them? When FreeBSD becomes 4.1-STABLE, in which file > > should I look to see this? > > man 1 uname > > -- > Marcel Moolenaar > mail: marcel@cup.hp.com / marcel@FreeBSD.org > tel: (408) 447-4222 -- Stephen Montgomery-Smith Department of Mathematics, University of Missouri, Columbia, MO 65211 Phone 573-882-4540, fax 573-882-1869 http://www.math.missouri.edu/~stephen stephen@math.missouri.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11:28:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 332B537B632 for ; Sun, 16 Jul 2000 11:28:07 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.10.1/8.10.1) id e6GIRnA87244; Sun, 16 Jul 2000 20:27:49 +0200 (SAT) From: John Hay Message-Id: <200007161827.e6GIRnA87244@zibbi.mikom.csir.co.za> Subject: Re: ed0 and isa cards on 4.x In-Reply-To: <200007160509.XAA50555@harmony.village.org> from Warner Losh at "Jul 15, 2000 11:09:43 pm" To: imp@village.org (Warner Losh) Date: Sun, 16 Jul 2000 20:27:49 +0200 (SAT) Cc: jhay@icomtek.co.za (John Hay), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200007150847.e6F8liH45154@zibbi.mikom.csir.co.za> John Hay writes: > : Have anyone 4.x working with an ISA card and the ed0 device? > > Works in 4.0 RELEASE. > > : card, but everytime I got the dreaded "ed0 device timeout" message. > > IRQ is wrong. But FreeBSD-3.5 installs without a problem on the same machine using that ethernet card? And the diagnostics in ezstart is happy with that interrupt? John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 11:29:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id EB20637B632 for ; Sun, 16 Jul 2000 11:29:47 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 971FF275; Sun, 16 Jul 2000 11:29:47 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id LAA29091; Sun, 16 Jul 2000 11:29:46 -0700 (PDT) Message-ID: <3971FF1A.5597C60B@cup.hp.com> Date: Sun, 16 Jul 2000 11:29:46 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Montgomery-Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: What makes the first line in /etc/motd References: <3971F9AA.CB581E24@math.missouri.edu> <3971FBB7.D3BB1C82@cup.hp.com> <3971FD1E.21330210@math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Montgomery-Smith wrote: > > Sorry, my question was not clear. I did not wish to know > what version of FreeBSD binaries I was using. I wanted to > know what version of FreeBSD I have in my /usr/src directory, > given that /usr/src is more recent than my binaries. sys/conf/newvers.sh -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 12:20:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 99C1537B792 for ; Sun, 16 Jul 2000 12:20:14 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.10.1/8.10.1) id e6GJK4A88321; Sun, 16 Jul 2000 21:20:04 +0200 (SAT) From: John Hay Message-Id: <200007161920.e6GJK4A88321@zibbi.mikom.csir.co.za> Subject: Re: ed0 and isa cards on 4.x In-Reply-To: <200007161827.e6GIRnA87244@zibbi.mikom.csir.co.za> from John Hay at "Jul 16, 2000 08:27:49 pm" To: imp@village.org Date: Sun, 16 Jul 2000 21:20:04 +0200 (SAT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : Have anyone 4.x working with an ISA card and the ed0 device? > > > > Works in 4.0 RELEASE. > > > > : card, but everytime I got the dreaded "ed0 device timeout" message. > > > > IRQ is wrong. > > But FreeBSD-3.5 installs without a problem on the same machine using that > ethernet card? And the diagnostics in ezstart is happy with that interrupt? > Ok, I got it working. I have disabled every driver I'm not using and then it works. It is very wierd and I have never suspected it because in the past a driver clash normally caused the probe to fail. For instance if a probe routine do something silly to other hardware. In this case the ed0 driver still probed correctly and everything seemed ok, except that the interrupts don't happen. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 12:23:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id E26C737BFE3 for ; Sun, 16 Jul 2000 12:23:41 -0700 (PDT) (envelope-from noor@comrax.com) Received: by dns.comrax.com (Postfix, from userid 100) id 8A5BB1C982; Sun, 16 Jul 2000 22:23:33 +0300 (IDT) Received: from localhost (localhost [127.0.0.1]) by dns.comrax.com (Postfix) with ESMTP id 8074F16E36 for ; Sun, 16 Jul 2000 22:23:33 +0300 (IDT) Date: Sun, 16 Jul 2000 22:23:33 +0300 (IDT) From: To: freebsd-stable@FreeBSD.ORG Subject: Latest RELENG_4. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, What is the latest FreeBSD-STABLE release, and is it stable enough for a productional system? Thanks, Noor Dawod To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 12:34:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 9CED037B599 for ; Sun, 16 Jul 2000 12:34:14 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id MAA13058; Sun, 16 Jul 2000 12:34:06 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007161934.MAA13058@freeway.dcfinc.com> Subject: Re: Latest RELENG_4. In-Reply-To: from "noor@comrax.com" at "Jul 16, 0 10:23:33 pm" To: noor@comrax.com Date: Sun, 16 Jul 2000 12:34:06 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, noor@comrax.com wrote: > What is the latest FreeBSD-STABLE release, and is it stable enough for > a productional system? Please remember that "STABLE" refers to the stability of the source tree, not of the resulting running system. That is, you should not see developmental work going on in -STABLE. Your question implies some expectation as to uptime and/or crash-proofedness, which isn't what the -STABLE refers to. Every so often, a discussion breaks out about the suitablilty of the names used on the branches, because of the confusion generated by the current (heh) names. Sorry that doesn't directly answer your question. For what it's worth, our production systems are running 3.4-STABLE, and my desktop is 2.2.8. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 13:38:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fingers.noc.uunet.co.za (fingers.noc.uunet.co.za [196.31.1.59]) by hub.freebsd.org (Postfix) with ESMTP id DE9C137B89D for ; Sun, 16 Jul 2000 13:38:27 -0700 (PDT) (envelope-from fingers@fingers.co.za) Received: from localhost (robh@localhost) by fingers.noc.uunet.co.za (8.9.3/8.9.3) with SMTP id WAA86096; Sun, 16 Jul 2000 22:37:50 +0200 (SAST) (envelope-from fingers@fingers.co.za) X-Authentication-Warning: fingers.noc.uunet.co.za: robh owned process doing -bs Date: Sun, 16 Jul 2000 22:37:49 +0200 (SAST) From: fingers X-Sender: robh@fingers.noc.uunet.co.za To: noor@comrax.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Latest RELENG_4. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > What is the latest FreeBSD-STABLE release, and is it stable enough for a > productional system? I did a build yesterday, and it was 4.1RC. I don't know if a very recent build of any strain is good for production boxes, but I'm sure some of the more knowledgeable folk can comment on that. Regards --Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 15: 5:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0947A37B907 for ; Sun, 16 Jul 2000 15:05:49 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00333; Sun, 16 Jul 2000 15:06:27 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Graham Wheeler Cc: "Jordan K. Hubbard" , Kazutaka YOKOTA , freebsd-stable@freebsd.org Subject: Re: FreeBSD-4.0S/psmintr out of sync/Synaptics Touchpad In-reply-to: Your message of "Thu, 06 Jul 2000 10:18:31 +0200." <252f164763d80f7d24a27596529b8450@cequrux.com> Date: Sun, 16 Jul 2000 15:06:27 -0700 Message-ID: <330.963785187@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a multi-part message in MIME format. > --------------715AA62B84C7D3D2EAB84DD8 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > As Jordan as reported a similar problem (or the same problem) with a > regular Logitech mouse in -current, I thought it would be worth posting > my current patches. Well, I tried them (after adding a definition for MOUSE_MODEL_SYNAPTICS to mouse.h) and I'm sorry to say they have no effect on my jumpy mouse. In fact, my jumpy mouse's drug problems have only gotten worse and now buttons get pushed so wildly in addition to the jumpyness that it's becoming a cut-and-paste danger to my windows. :) I've also seen the mouse finally go completely dead, necessitating a reboot, on several occasions. It's definitely to the point where I now have to consider the PS/2 mouse driver unusable for SMP machines running -current and am in search of a serial mouse for poor zippy here. :-) The psm driver isn't suffering from this problem in -stable, thank god, and can still be used safely in the upcoming 4.1-RELEASE. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 15:24:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E8EF37B54B; Sun, 16 Jul 2000 15:24:57 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA89429; Sun, 16 Jul 2000 15:24:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Jul 2000 15:24:56 -0700 (PDT) From: Kris Kennaway To: "Chad R. Larson" Cc: noor@comrax.com, freebsd-stable@FreeBSD.ORG Subject: Re: Latest RELENG_4. In-Reply-To: <200007161934.MAA13058@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Chad R. Larson wrote: > As I recall, noor@comrax.com wrote: > > What is the latest FreeBSD-STABLE release, and is it stable enough for > > a productional system? > > Please remember that "STABLE" refers to the stability of the source > tree, not of the resulting running system. That is, you should not see > developmental work going on in -STABLE. Well, I claim this to be false: the targetted stability *is* of the resulting product. Of course, we sometimes make mistakes - but if you have *any* stability problems you should tell us!! Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 15:27:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D4E1237B59D; Sun, 16 Jul 2000 15:27:09 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA89682; Sun, 16 Jul 2000 15:27:09 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Jul 2000 15:27:04 -0700 (PDT) From: Kris Kennaway To: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Cc: clefevre@citeweb.net, stable@FreeBSD.ORG Subject: Re: Parallel kernel make Was Re: kernel.debug (was Re: HEADS UP! Always use the 'make buildkernel' target to make your kernels) In-Reply-To: <3971FA68.3A3C5F17@ludd.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Joachim [iso-8859-1] Str=F6mbergson wrote: > Just for kicks I tried doing a 'make -j4 buildkernel' with KERNEL=3DSNP40 > in /etc/make.conf and /boot/loader.conf. It works, that is the make > finished without crashing. I dunno if the binary works, nor if the > compile was substantially faster. So, superficially, parallel make of a > kernel does work. Yes, there is no reason why this should not work. > It sure consumed a lot of resources for a few minutes though. My SETI > run ran sloowly. Well, wouldn't you kind of expect this given what you asked the system to do (namely run 4 tasks at once)? However, -j4 is often slightly faster even on uniprocessor systems than -j1 (or "no -j") because it doesn't have to wait on Disk I/O. YMMV, of course. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 15:59:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id CE70437B824 for ; Sun, 16 Jul 2000 15:59:36 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id 3166C3D34; Sun, 16 Jul 2000 18:59:48 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 2C8C45BC2; Sun, 16 Jul 2000 18:59:48 -0400 (EDT) Date: Sun, 16 Jul 2000 18:59:48 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Andreas Ntaflos Cc: freebsd-stable@freebsd.org Subject: Re: is the ensoniq 1371 sound chip supported? In-Reply-To: <3970DA7D.DBC54B12@gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add device pcm to your kernel. (38) sean@pulse: ~ $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jun 29 2000 01:10:19 Installed devices: pcm0: at io 0x1080 irq 5 (1p/1r channels duplex) I've got the same card, and it works perfectly. On Sat, 15 Jul 2000, Andreas Ntaflos wrote: > i have an SB PCI64 sound card, the sound chip is the ensoniq 1371. now i > want to know, is that chip/that soundcard supported with freebsd 4.0/4.1 > RC? > and if yes, where can i find information on how to make it work? > thanks a bunch > > regards > Andreas Ntaflos > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 16: 0:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F391637C002; Sun, 16 Jul 2000 16:00:16 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA91769; Sun, 16 Jul 2000 16:00:16 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Jul 2000 16:00:16 -0700 (PDT) From: Kris Kennaway To: stable@freebsd.org, net@freebsd.org Subject: HEADS UP! Please test new KAME Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I meant to send this out yesterday, but forgot. I have merged the KAME code from -current, which brings 4.1 up to the most recent sources from the KAME project (http://www.kame.net). What does this give us? I'm glad you asked :-) * Signficantly improved IPSEC functionality. In particular, IPSEC security associations must no longer be manually keyed: the new code supports racoon, the KAME IKE daemon, which is located in /usr/ports/security/racoon. Racoon has been shown to interoperate well with other vendor IKE systems, meaning that FreeBSD 4.1 can be used in a heterogeneous IPSEC environment. However, racoon *is* still a work in progress, meaning that there may still be bugs, configuration syntax changes, etc. * About 9 months of fixes and improvements to the IPv6 code relative to what was previously in 4.0. * FreeBSD 4.1 can now be installed on an IPv6-only network - this will be the first release of FreeBSD that never needs to operate using IPv4 at all! ftp7.jp.freebsd.org (Japan #7) is an IPv6-reachable mirror site for installation and package-fetching. * Several additional system utilities (whois, fetch, and possibly others) have gained the ability to operate over IPv6. * FreeBSD 4.1 will ship with numerous IPv6-ready packages including web servers and browsers, all manner of network clients (FTP, IRC, SSH, ...) and network tools. See http://www.freebsd.org/ports/ipv6.html for a list of IPv6-capable ports. * One useful feature of KAME which has not yet been merged across is the ALTQ traffic-shaping system - I hope to get this in time for 4.2. The more experimental KAME code has also not been merged. If you need those features, I suggest you make use of the KAME snapshots from www.kame.net which will become available after 4.1-RELEASE. * I am sure I have forgotten some of the features of the new code :-) The merged changes have been tested in -current for several weeks without incident. The only known problem is that NFS mounts over IPSEC do not seem to work reliably (in my testing environment, at least) - I have seen eventual hangs with IPSEC/ESP mounts and possible data corruption with IPSEC/AH. However, there's of course no way for me to have tested everything, so there may still be bugs which affect operation. There are still 9 days until the scheduled release of 4.1-RELEASE in which to find and correct problems, so I respectfully ask all of you who can test the new code to please do as much as you can *now*, while there's still time, and not after the release has been rolled when it's too late. Thanks! On behalf of the FreeBSD community, I would like to thank the KAME developer team for their tireless work and dedication to the BSD community, and in particular the efforts of Hagino-san, Umemoto-san and Sumikawa-san (I hope I'm not forgetting anyone) for bringing the latest code into FreeBSD. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 17:50:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id C994C37B78E for ; Sun, 16 Jul 2000 17:50:15 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15497258 invoked from network); 17 Jul 2000 00:50:14 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Jul 2000 00:50:14 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id CAA34845; Mon, 17 Jul 2000 02:50:09 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Mon, 17 Jul 2000 02:50:09 +0200 (CEST) To: Kris Kennaway Cc: Joachim =?iso-8859-1?q?Str=F6mbergson?= , clefevre@citeweb.net, stable@FreeBSD.org Subject: Re: Parallel kernel make Was Re: kernel.debug (was Re: HEADS UP! Always use the 'make buildkernel' target to make your kernels) References: Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 17 Jul 2000 02:50:08 +0200 In-Reply-To: Kris Kennaway's message of "Sun, 16 Jul 2000 15:27:04 -0700 (PDT)" Message-ID: Lines: 27 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > On Sun, 16 Jul 2000, Joachim [iso-8859-1] Str=F6mbergson wrote: >=20 > > Just for kicks I tried doing a 'make -j4 buildkernel' with KERNEL=3DSNP= 40 > > in /etc/make.conf and /boot/loader.conf. It works, that is the make > > finished without crashing. I dunno if the binary works, nor if the > > compile was substantially faster. So, superficially, parallel make of a > > kernel does work. >=20 > Yes, there is no reason why this should not work. >=20 > > It sure consumed a lot of resources for a few minutes though. My SETI > > run ran sloowly. >=20 > Well, wouldn't you kind of expect this given what you asked the system to > do (namely run 4 tasks at once)? However, -j4 is often slightly faster > even on uniprocessor systems than -j1 (or "no -j") because it doesn't have > to wait on Disk I/O. YMMV, of course. I do make -j4 buildworld and kernel for month w/o any problems and is really faster than -j1. even on a P166 uniprocessor. Cyrille. --=20 home:mailto:clefevre%no-spam@citeweb.net Supprimer "%no-spam" pour me repon= dre. work:mailto:Cyrille.Lefevre%no-spam@edf.fr Remove "%no-spam" to answer me b= ack. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 18:32:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bmw.cobaka.com (bmw.cobaka.com [209.67.40.174]) by hub.freebsd.org (Postfix) with ESMTP id 393DD37B7B9 for ; Sun, 16 Jul 2000 18:32:15 -0700 (PDT) (envelope-from winter@villaweb.net) Received: from WINTERPC (root@localhost [127.0.0.1]) by bmw.cobaka.com (8.9.3/8.9.1) with SMTP id SAA57884; Sun, 16 Jul 2000 18:38:37 -0700 (PDT) Reply-To: From: "Phil Rosenthal" To: "John Reynolds" Cc: Subject: RE: Upgrading 3.5-STABLE to 4.0-STABLE Date: Sun, 16 Jul 2000 21:40:32 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <14704.42880.885132.716803@whale.home-net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to ignore the "reboot in signle mode" part? It is not possible to get this system into single mode, because it has = to be up, always. it can have a maximum downtime of maybe 45 seconds, which is too long to = go into single mode and compile stuff. I know it is obviously more dangerous to be in multi-user mode, but is = it one of those "better safe than sorry, but it will probably work" = things? --Phil -----Original Message----- From: John Reynolds [mailto:jjreynold@home.com] Sent: Saturday, July 15, 2000 2:04 PM To: winter@villaweb.net Subject: Re: Upgrading 3.5-STABLE to 4.0-STABLE [ On Saturday, July 15, Phil Rosenthal wrote: ] > Is there any way I can safely upgrade 3.5-STABLE to 4.0-STABLE (or is = it 4.1 now?) remotely? > It is not easy to go to the actual server and upgrade... > Thanks, > --Phil I think this is definitely "doable" but it takes knowing exactly what to = do. If you CVSUP the sources to 4.x-STABLE look at /usr/src/UPDATING and read EVERYTHING in the file. If I were you I would absorb everything, write down every single = procedure you would do in order to get this done and then post this with a "am I = correct" message. There are some gotchas in 4.0/4.1 with /etc and OpenSSL, etc. -Jr --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D John Reynolds Chandler Capabilities Engineering, CDS, Intel = Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.5-STABLE. FreeBSD: The Power to = Serve. http://members.home.com/jjreynold/ Come join us!!! @ = http://www.FreeBSD.org/ =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 19:25:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 039AC37B70A for ; Sun, 16 Jul 2000 19:25:12 -0700 (PDT) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.10.1/8.10.1/20000715) id e6H2P3X04736; Sun, 16 Jul 2000 21:25:03 -0500 (CDT) From: Larry Rosenman Message-Id: <200007170225.e6H2P3X04736@lerami.lerctr.org> Subject: Re: Latest RELENG_4. In-Reply-To: "from noor@comrax.com at Jul 16, 2000 10:23:33 pm" To: noor@comrax.com Date: Sun, 16 Jul 2000 21:25:03 -0500 (CDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL79 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We (Internet America) have a BUNCH of 4.0-Stable systems in productuion. It's MUCH more stable than 3.x in heavy network environments. Larrym > > Hello, > > What is the latest FreeBSD-STABLE release, and is it stable enough for a > productional system? > > Thanks, > Noor Dawod > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 19:45: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from s1.elec.uq.edu.au (s1.elec.uq.edu.au [130.102.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 25C1937B83D for ; Sun, 16 Jul 2000 19:45:04 -0700 (PDT) (envelope-from clary@s1.elec.uq.edu.au) Received: (from clary@localhost) by s1.elec.uq.edu.au (8.9.3/8.9.3) id MAA57036 for freebsd-stable@freebsd.org; Mon, 17 Jul 2000 12:44:29 +1000 (EST) (envelope-from clary) From: Clary Harridge Message-Id: <200007170244.MAA57036@s1.elec.uq.edu.au> Subject: buildworld fails on lptcontrol To: freebsd-stable@freebsd.org Date: Mon, 17 Jul 2000 12:44:29 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A recent make world FreeBSD 4.0-STABLE (HOST_NAME) #0: Mon Jul 17 10:01:43 EST 2000 with files supped 13 Jul 2000 fails with ===> usr.sbin/lptcontrol rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/local/src/i386/usr/include /usr/local/src/usr.sbin/lptcontrol/lptcontrol.c /usr/local/src/usr.sbin/lptcontrol/lptcontrol.c:45: dev/ppbus/lptio.h: No such file or directory mkdep: compile failed i.e. the include file dev/ppbus/lptio.h: has not been setup commenting out the build of lptcontrol allows the makeworld to complete -- regards Department of Computer Science and Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-3365-3636 Fax: +61-7-3365-4999 INTERNET: clary@csee.uq.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 19:56:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rollcage.bl.echidna.id.au (rollcage.bl.echidna.id.au [203.6.241.134]) by hub.freebsd.org (Postfix) with ESMTP id AC25737B7A7 for ; Sun, 16 Jul 2000 19:56:03 -0700 (PDT) (envelope-from carl@rollcage.bl.echidna.id.au) Received: (from carl@localhost) by rollcage.bl.echidna.id.au (8.11.0.Beta3/8.11.0.Beta1) id e6H2tvH28081 for freebsd-stable@FreeBSD.ORG; Mon, 17 Jul 2000 12:55:57 +1000 (EST) Date: Mon, 17 Jul 2000 12:55:57 +1000 (EST) Message-Id: <200007170255.e6H2tvH28081@rollcage.bl.echidna.id.au> From: carl@bl.echidna.id.au To: freebsd-stable@FreeBSD.ORG Subject: buildworld problems (4.0-RELEASE to 4.0-STABLE) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day, I've got a copy of 4.0 RELEASE (from the CD) that I've been trying unsuccessfully to update to 4.0-STABLE for the last few weeks. I've been watching this list, and taking note of what I've seen, and my procedure is this : I CVSup the latest source from cvsup3.au.FreeBSD.org (I'm in Australia), which seems to run ok, and then I cd /usr/src and make buildworld. I'm yet to get it to build. The box either reboots part-way through, or I see something like this : cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/pt.c {standard input}: Assembler messages: {standard input}:3968: Warning: end of file not at end of a line; newline inserted {standard input}:6037: Error: no such 386 instruction: `a' {standard input}:6038: Error: no such 386 instruction: `ddl' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. clunker# To make sure there's no bogosity floating around I've done a make clean in /usr/src, but the same error happens. The error moves around (each time I compile it it's different), so do I have bodgey hardware that could cause this, or am I doing something really wrong? The box is : Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #0: Mon Jul 10 21:43:47 EST 2000 carl@clunker.bl.echidna.id.au:/usr/src/sys/compile/clunker2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xf9ff real memory = 67108864 (65536K bytes) avail memory = 61452288 (60012K bytes) Preloaded elf kernel "kernel" at 0xc037a000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 10.0 irq 11 xl0: <3Com 3c900-TPO Etherlink XL> port 0x6100-0x613f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:60:08:34:49:29 xl0: selecting 10baseT transceiver, half duplex xl0: supplying EUI64: 00:60:08:ff:fe:34:49:29 isa0: unexpected tag 14 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 ad0: 3077MB [6253/16/63] at ata0-master using WDMA2 acd0: CDROM at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted xl0: starting DAD for fe80:0001::0260:08ff:fe34:4929 xl0: DAD complete for fe80:0001::0260:08ff:fe34:4929 - no duplicates found xl0: starting DAD for 3ffe:8001:0005:0ed0:0260:08ff:fe34:4929 xl0: DAD complete for 3ffe:8001:0005:0ed0:0260:08ff:fe34:4929 - no duplicates found and my cvsup config file : *default host=cvsup3.au.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default compress src-all Can anyone tell me what I'm doing wrong? thanks for your time, and an excellent product. Carl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 19:58: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 9D80A37B7A7 for ; Sun, 16 Jul 2000 19:58:01 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA63694; Sun, 16 Jul 2000 22:58:00 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sun, 16 Jul 2000 22:58:58 -0400 To: From: Garance A Drosihn Subject: RE: Upgrading 3.5-STABLE to 4.0-STABLE Cc: Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:40 PM -0400 7/16/00, Phil Rosenthal wrote: >Is it possible to ignore the "reboot in single mode" part? > >It is not possible to get this system into single mode, because >it has to be up, always. >it can have a maximum downtime of maybe 45 seconds, which is >too long to go into single mode and compile stuff. >I know it is obviously more dangerous to be in multi-user mode, >but is it one of those "better safe than sorry, but it will >probably work" things? If you have a machine which really has that kind of uptime requirement, then you need to rethink your upgrade strategy. There's no absolute guarantee that everything is going to work after upgrading (particularly when doing a large jump, such as going from 3.5 to 4.0-stable). Even if everything DOES work, it might be that it'll take an extra 30 seconds to boot up. I can not imagine feeling comfortable saying "sure, go ahead, it will 'probably' work" if you really can not afford a minute's worth of downtime. If the upgrade does work 99% of the time, and you happen to hit that other 1%, then you're screwed. I would not want to be responsible for you finding yourself screwed. I realize you probably also have the constraint that you can not spend any money on redundant equipment, but at some point reality will have to set in. Either get redundant equipment, or give up on 45-second maximum downtime, or simply do not do upgrades. That's just my view of things, of course... In my case, I have a machine where the goal for maximum downtime is more like 30 MINUTES, and yet I have a duplicate machine for that case. I'm certainly not going to recommend that you jump into 4.0-stable on a critical production machine without doing some testing of it before switching to it. [aside: on that machine, I'm about 3 hours away from having one year's worth of continuous uptime... :-) ] --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 20: 6:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 0DB0637B7A7 for ; Sun, 16 Jul 2000 20:06:39 -0700 (PDT) (envelope-from tlrobertson@mindspring.com) Received: from reba (user-1054v1c.dsl.mindspring.com [64.82.124.44]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with SMTP id XAA01515 for ; Sun, 16 Jul 2000 23:06:37 -0400 (EDT) Reply-To: From: "Timothy L. Robertson" To: Subject: 4.0-RELEASE to 4.0-STABLE upgrade Date: Sun, 16 Jul 2000 20:06:25 -0700 Message-ID: <001201bfef9b$ff42cb00$0301a8c0@timothyr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I just finished upgrading as the subject line says, and I've noticed two anomalies. 1) On boot I get the message: module_register: module netgraph already exists! linker_file_sysinit "netgraph.ko" failed to register! 17 I use my box as a router to distribute a DSL PPPoE feed to some windows machines with nat and user ppp. Things seem to still work fine, but the message makes me uneasy. 2) My kernel grew from ~2.5MB to over 10MB after the upgrade. kldstat -v looks about the same, and my config file hasn't changed at all. bash-2.03$ uname -a FreeBSD scarlet 4.1-RC FreeBSD 4.1-RC #10: Sun Jul 16 20:26:32 PDT 2000 timothyr@scarlet:/usr/src/sys/compile/DSLROUTE i386 Any pointers appreciated. Thanks, -Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 20:13:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from odin.egate.net (as2.dm.egate.net [216.235.1.5]) by hub.freebsd.org (Postfix) with ESMTP id A0CBF37B93D for ; Sun, 16 Jul 2000 20:13:39 -0700 (PDT) (envelope-from buff@pobox.com) Received: from localhost (buff@localhost) by odin.egate.net (8.9.3/8.9.1) with ESMTP id XAA55998 for ; Sun, 16 Jul 2000 23:13:37 -0400 (EDT) X-Authentication-Warning: odin.egate.net: buff owned process doing -bs Date: Sun, 16 Jul 2000 23:13:35 -0400 (EDT) From: William Denton X-Sender: buff@odin.egate.net To: freebsd-stable@FreeBSD.ORG Subject: Kernel build numbers and kernel-building methods Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After all the recent chat following that heads-up about how to build a world, I gave it a shot and rebuilt my system, gave the buildkernel and installkernel a KERNEL=MYCROFT setting, and adjusted /boot/loader.conf so it'd load /MYCROFT. All went well, but I noticed that the kernel build number reported by uname had changed. It said "FreeBSD 4.0-STABLE #0," while the number had been above 0 before. I rebuilt the system today and it stayed at 0, but then I recompiled the kernel alone (the old way) and now it says "FreeBSD 4.1-RC #6." Does compiling a kernel with make buildkernel not increment this number? If not, shouldn't it? Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 20:21:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 1092A37B941 for ; Sun, 16 Jul 2000 20:21:42 -0700 (PDT) (envelope-from browna4@rpi.edu) Received: from cortez.sss.rpi.edu (browna4@cortez.sss.rpi.edu [128.113.113.33]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA98924 for ; Sun, 16 Jul 2000 23:21:40 -0400 Received: from localhost (browna4@localhost) by cortez.sss.rpi.edu (8.8.5/8.8.6) with SMTP id XAA28978 for ; Sun, 16 Jul 2000 23:21:57 -0400 X-Authentication-Warning: cortez.sss.rpi.edu: browna4 owned process doing -bs Date: Sun, 16 Jul 2000 23:21:57 -0400 (EDT) From: Andrew Fitzglenville Brown X-Sender: browna4@cortez.sss.rpi.edu To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-stable Andrew "Dru" Fitz-Glenville Brown MGMT/STS May 2001 ( Yeah right!) North Hall 218 RPI Residence 110 8th street Troy N.Y. 12180 518-276-7230 browna4@rpi.edu Dru_Brown@hotmail.com Dru_Brown@goplay.com "Dance... even if it's only in your own living room when nobody's watching." "Toeing the fine line between brilliance and madness..." " To er is human, to forgive, divine." " You were placed on this planet to have fun. If you are not having fun, do something about it." "Dance as if no one is watching. Sing as if no one is listening. Love as if you have never been hurt." "The events which transpired five thousand years ago; five years ago or five minutes ago, have determined what will happen five minutes from now; five years from now or five thousand years from now. All history is a current event." -Dr. John Henrik Clarke- "This is like being nibbled to death by... what are those Earth creatures called: feathers, long bills, webbed feet, go 'quack'?" "Cats." "What we call human nature, is actually human habit." "A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly." "Specialization is for insects...." -Robert A. Heinlein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 21:10:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from adsl-151-197-208-173.bellatlantic.net (adsl-151-197-208-173.bellatlantic.net [151.197.208.173]) by hub.freebsd.org (Postfix) with ESMTP id 676FA37B994 for ; Sun, 16 Jul 2000 21:10:15 -0700 (PDT) (envelope-from bleez@bellatlantic.net) Received: from localhost (root@localhost) by adsl-151-197-208-173.bellatlantic.net (8.9.3/8.9.3) with ESMTP id AAA00583; Mon, 17 Jul 2000 00:10:06 -0400 (EDT) (envelope-from bleez@bellatlantic.net) Date: Mon, 17 Jul 2000 00:10:06 -0400 (EDT) From: Bryan Liesner X-Sender: root@adsl-151-197-208-173.bellatlantic.net To: timothyr@timothyr.net Cc: freebsd-stable@freebsd.org Subject: Re: 4.0-RELEASE to 4.0-STABLE upgrade In-Reply-To: <001201bfef9b$ff42cb00$0301a8c0@timothyr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000, Timothy L. Robertson wrote: >Hi All, > >I just finished upgrading as the subject line says, and I've noticed two >anomalies. > >1) On boot I get the message: >module_register: module netgraph already exists! >linker_file_sysinit "netgraph.ko" failed to register! 17 >I use my box as a router to distribute a DSL PPPoE feed to some windows >machines with nat and user ppp. Things seem to still work fine, but the >message makes me uneasy. If you're missing one of the necessary netgraph config items in your config file, when you boot, the module gets loaded in. The loader tried to load netgraph.ko too, which is already present in the compiled kernel. The bare minimum I found for PPPoE to work without loading modules is: options NETGRAPH options NETGRAPH_ETHER options NETGRAPH_PPPOE options NETGRAPH_SOCKET Try that and I'm sure that message will go away. >2) My kernel grew from ~2.5MB to over 10MB after the upgrade. kldstat -v >looks about the same, and my config file hasn't changed at all. Can't answer that one. ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@bellatlantic.net Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 21:16:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 9D8ED37B9F1 for ; Sun, 16 Jul 2000 21:16:17 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000717041615.OTJY11071.mail.rdc1.il.home.com@math.missouri.edu>; Sun, 16 Jul 2000 21:16:15 -0700 Message-ID: <397288A8.914A87A1@math.missouri.edu> Date: Sun, 16 Jul 2000 23:16:40 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: William Denton Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel build numbers and kernel-building methods References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Denton wrote: > > After all the recent chat following that heads-up about how to build a > world, I gave it a shot and rebuilt my system, gave the buildkernel and > installkernel a KERNEL=MYCROFT setting, and adjusted /boot/loader.conf so > it'd load /MYCROFT. All went well, but I noticed that the kernel build > number reported by uname had changed. It said "FreeBSD 4.0-STABLE #0," > while the number had been above 0 before. I rebuilt the system today and > it stayed at 0, but then I recompiled the kernel alone (the old way) and > now it says "FreeBSD 4.1-RC #6." > > Does compiling a kernel with make buildkernel not increment this > number? If not, shouldn't it? > The way I see it, the version number is created by a little script /sys/conf/newvers.sh which figures out the version from a file called make-directory/version, where make-directory is the directory in which you are making the kernel. So for example, version might contain the number '6', in which case your kernel build is 6. (And then after the build, version will contain '7' - if version does not exist, it takes this number to be '0'.) Now when you do the make buildkernel, make-directory is /usr/obj/usr/src/sys/XXX where XXX is the name of your kernel. This directory will be completely deleted before any make (unless you use the -DNOCLEAN option), so you will always have a build number 0. When you do the /usr/sbin/config stuff, make-directory is /sys/compile/XXX This will pick up the version that you had left over from your previous build. (But if you do /usr/sbin/config -r then this directory is deleted, so your build goes back to 0). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 21:47:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 9FA9E37B536 for ; Sun, 16 Jul 2000 21:47:14 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6H4lBB07602; Mon, 17 Jul 2000 06:47:12 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e6H4lBB19548; Mon, 17 Jul 2000 06:47:11 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.10.2/8.10.2/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e6H4lB422789; Mon, 17 Jul 2000 06:47:11 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.10.2/8.10.2/alaska [ $Revision: 1.4 ]) id e6H4lBQ73389; Mon, 17 Jul 2000 04:47:11 GMT Date: Mon, 17 Jul 2000 06:47:11 +0200 From: Udo Schweigert To: Clary Harridge Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildworld fails on lptcontrol Message-ID: <20000717064711.A73322@alaska.cert.siemens.de> Mail-Followup-To: Clary Harridge , freebsd-stable@FreeBSD.ORG References: <200007170244.MAA57036@s1.elec.uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007170244.MAA57036@s1.elec.uq.edu.au>; from clary@elec.uq.edu.au on Mon, Jul 17, 2000 at 12:44:29PM +1000 X-Operating-System: FreeBSD 4.1-RC Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 12:44:29 +1000, Clary Harridge wrote: > A recent make world > > FreeBSD 4.0-STABLE (HOST_NAME) #0: Mon Jul 17 10:01:43 EST 2000 > > with files supped 13 Jul 2000 > > fails with > > ===> usr.sbin/lptcontrol > rm -f .depend > mkdep -f .depend -a -I/usr/obj/usr/local/src/i386/usr/include /usr/local/src/usr.sbin/lptcontrol/lptcontrol.c > /usr/local/src/usr.sbin/lptcontrol/lptcontrol.c:45: dev/ppbus/lptio.h: No such file or directory > mkdep: compile failed > > i.e. the include file dev/ppbus/lptio.h: has not been setup > > commenting out the build of lptcontrol > allows the makeworld to complete > Please cvsup again. It was fixed some days ago. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 22:13:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 2037837B8B9 for ; Sun, 16 Jul 2000 22:13:35 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15940830 invoked from network); 17 Jul 2000 05:13:33 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Jul 2000 05:13:33 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id HAA46005; Mon, 17 Jul 2000 07:13:33 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Mon, 17 Jul 2000 07:13:33 +0200 (CEST) To: carl@bl.echidna.id.au Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildworld problems (4.0-RELEASE to 4.0-STABLE) References: <200007170255.e6H2tvH28081@rollcage.bl.echidna.id.au> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 17 Jul 2000 07:13:31 +0200 In-Reply-To: carl@bl.echidna.id.au's message of "Mon, 17 Jul 2000 12:55:57 +1000 (EST)" Message-ID: Lines: 38 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG carl@bl.echidna.id.au writes: > G'day, > > I've got a copy of 4.0 RELEASE (from the CD) that I've been trying > unsuccessfully to update to 4.0-STABLE for the last few weeks. I've > been watching this list, and taking note of what I've seen, and > my procedure is this : > > I CVSup the latest source from cvsup3.au.FreeBSD.org (I'm in Australia), > which seems to run ok, and then I cd /usr/src > and make buildworld. > > I'm yet to get it to build. > > The box either reboots part-way through, or I see something like this : > [snip] > > To make sure there's no bogosity floating around I've done a make clean > in /usr/src, but the same error happens. The error moves around (each time I > compile it it's different), so do I have bodgey hardware that could > cause this, or am I doing something really wrong? > [snip] just in case, check your memory using http://reality.sgi.com/cbrady/memtest86 sometimes, it's safe to redo a cvsup some times later. because, if you're not lucky, you cvsup files while a commit is done and some files are missing or not in conjoncture between them. also, in case of bad files, try to cvsup from cvsup3.freebsd.org. I don't know how often cvsup3.au.freebsd.org is updated from cvsup3.freebsd.org ? Cyrille. -- home:mailto:clefevre%no-spam@citeweb.net Supprimer "%no-spam" pour me repondre. work:mailto:Cyrille.Lefevre%no-spam@edf.fr Remove "%no-spam" to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jul 16 22:15:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 1E1C337BACC for ; Sun, 16 Jul 2000 22:15:54 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15454423 invoked from network); 17 Jul 2000 05:15:52 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Jul 2000 05:15:52 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id HAA46018; Mon, 17 Jul 2000 07:15:52 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Mon, 17 Jul 2000 07:15:52 +0200 (CEST) To: Clary Harridge Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildworld fails on lptcontrol References: <200007170244.MAA57036@s1.elec.uq.edu.au> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 17 Jul 2000 07:15:51 +0200 In-Reply-To: Clary Harridge's message of "Mon, 17 Jul 2000 12:44:29 +1000 (EST)" Message-ID: Lines: 28 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Clary Harridge writes: > A recent make world > > FreeBSD 4.0-STABLE (HOST_NAME) #0: Mon Jul 17 10:01:43 EST 2000 > > with files supped 13 Jul 2000 cvsup again after a while when files are missing or seem to be bad. usually, that's help. today, fetch.c was missing. some times later, it was ok. > fails with > > ===> usr.sbin/lptcontrol > rm -f .depend > mkdep -f .depend -a -I/usr/obj/usr/local/src/i386/usr/include /usr/local/src/usr.sbin/lptcontrol/lptcontrol.c > /usr/local/src/usr.sbin/lptcontrol/lptcontrol.c:45: dev/ppbus/lptio.h: No such file or directory > mkdep: compile failed > > i.e. the include file dev/ppbus/lptio.h: has not been setup > > commenting out the build of lptcontrol > allows the makeworld to complete Cyrille. -- home:mailto:clefevre%no-spam@citeweb.net Supprimer "%no-spam" pour me repondre. work:mailto:Cyrille.Lefevre%no-spam@edf.fr Remove "%no-spam" to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 1:27:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 4663237B6F9 for ; Mon, 17 Jul 2000 01:27:21 -0700 (PDT) (envelope-from carl@xena.IPAustralia.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id SAA67977 for ; Mon, 17 Jul 2000 18:27:18 +1000 (EST) (envelope-from carl@xena.IPAustralia.gov.au) Received: from xena.aipo.gov.au(10.0.100.52) by pericles.IPAustralia.gov.au via smap (V2.0) id xma067971; Mon, 17 Jul 00 18:27:10 +1000 Received: from newton.aipo.gov.au (newton.aipo.gov.au [10.0.100.18]) by xena.aipo.gov.au (8.9.3/8.9.3) with ESMTP id SAA35696 for ; Mon, 17 Jul 2000 18:29:34 +1000 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id SAA54671 for ; Mon, 17 Jul 2000 18:27:08 +1000 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Mon, 17 Jul 2000 18:27:08 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: stable@freebsd.org Subject: Removing Path prefixing for Linux binaries. (ie to run ADSM) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying to work out a clean way to label linux binaries that I don't want the path prepending done to. This prepending makes the linux ADSM client unusable (for example). I know someone has gone so far as removing the whole /compat/linux path from the linux emulator (ABI interface), and while that doesn't look hard I've been trying to think of a better way. The only thing I can think of so far is to use brandelf to either brand it with a different type (say linuxnp) that has the path removed, (Can I just put that extra type in linux_sysvec.c?) or add some other header information. Does anyone have any better ideas or is interested in working on this? Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 1:28:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw2.dnepr.net (CoreGW2-TBone.dnepr.net [195.24.156.97]) by hub.freebsd.org (Postfix) with ESMTP id 2DDBD37BBE2 for ; Mon, 17 Jul 2000 01:28:47 -0700 (PDT) (envelope-from land@mail.dnepr.net) Received: from daemon.tlk (mizi.dnepr.net [195.24.156.63]) by gw2.dnepr.net (8.8.8/8.6.18/01) with ESMTP id LAA11809 for ; Mon, 17 Jul 2000 11:28:16 +0300 (EET DST) Date: Mon, 17 Jul 2000 11:28:13 +0300 (EEST) From: Andrey Lakhno X-Sender: land@daemon.tlk To: stable@freebsd.org Subject: strange `make` behavior in make tree Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I do something like this: # cd /usr/ports/news/tin # make Ctrl-C # ps And i see: PID TT STAT TIME COMMAND 228 v0 Ss 0:00.15 -bash (bash) 11071 v0 S 0:00.00 /bin/sh -ec (cd /usr/ports/distfiles/; for file in t 11072 v0 S 0:00.00 /bin/sh -ec (cd /usr/ports/distfiles/; for file in t 11086 v0 S 0:00.01 fetch -AP ftp://ftp.no.freebsd.org/pub/FreeBSD/ports/ 11099 v0 R+ 0:00.00 ps [... skipped ...] fetch leaved in background and keep running. Like two other shells. The result doesn't depend on port which i choose. /Andrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 1:36:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw2.dnepr.net (CoreGW2-TBone.dnepr.net [195.24.156.97]) by hub.freebsd.org (Postfix) with ESMTP id EFFE937B76C for ; Mon, 17 Jul 2000 01:36:16 -0700 (PDT) (envelope-from land@mail.dnepr.net) Received: from daemon.tlk (mizi.dnepr.net [195.24.156.63]) by gw2.dnepr.net (8.8.8/8.6.18/01) with ESMTP id LAA13622 for ; Mon, 17 Jul 2000 11:35:57 +0300 (EET DST) Date: Mon, 17 Jul 2000 11:35:54 +0300 (EEST) From: Andrey Lakhno X-Sender: land@daemon.tlk To: stable@FreeBSD.ORG Subject: Re: strange `make` behavior in ports tree In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Andrey Lakhno wrote: Sorry, in first letter was wrong subject. AL> AL>Hi ! AL> AL> I do something like this: AL> AL> # cd /usr/ports/news/tin AL> # make AL> Ctrl-C AL> # ps AL> AL> And i see: AL> AL> PID TT STAT TIME COMMAND AL> 228 v0 Ss 0:00.15 -bash (bash) AL>11071 v0 S 0:00.00 /bin/sh -ec (cd /usr/ports/distfiles/; for file in t AL>11072 v0 S 0:00.00 /bin/sh -ec (cd /usr/ports/distfiles/; for file in t AL>11086 v0 S 0:00.01 fetch -AP ftp://ftp.no.freebsd.org/pub/FreeBSD/ports/ AL>11099 v0 R+ 0:00.00 ps AL>[... skipped ...] AL> AL>fetch leaved in background and keep running. Like two other shells. AL> AL>The result doesn't depend on port which i choose. AL> AL>/Andrey AL> AL> AL> AL>To Unsubscribe: send mail to majordomo@FreeBSD.org AL>with "unsubscribe freebsd-stable" in the body of the message AL> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 1:37:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AC45537B92E for ; Mon, 17 Jul 2000 01:37:20 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA88852; Mon, 17 Jul 2000 01:37:07 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 01:37:07 -0700 From: "David O'Brien" To: Larry Rosenman Cc: freebsd-stable@freebsd.org Subject: Re: SendMail 8.10 (fwd) Message-ID: <20000717013707.A88827@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200007160031.e6G0VRn03113@lerami.lerctr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007160031.e6G0VRn03113@lerami.lerctr.org>; from ler@lerctr.org on Sat, Jul 15, 2000 at 07:31:27PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 15, 2000 at 07:31:27PM -0500, Larry Rosenman wrote: > Any chance of Sendmail 8.10.2 being integrated into -STABLE before > 4.1 goes -RELEASE? I was trying to make this happen, but due to various available time of all the steps involved, it will not make it. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 1:46:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 3EC5237B588 for ; Mon, 17 Jul 2000 01:46:45 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.af.speednet.com.au (andyf@backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id SAA04108 for ; Mon, 17 Jul 2000 18:46:41 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Mon, 17 Jul 2000 18:46:40 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: freebsd-stable@FreeBSD.ORG Subject: pw(8) not disabling passwords Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else having problems with pw(8)?? I can't seem to get the '-h -' option to disable a password: # pw useradd -n test -h 0 Password for user test: # grep test /etc/master.passwd test:$1$aXdmsI7e$IfyjlCEziFg5tp70bkA1o1:1002:1002::0:0:User &:/home/test:/bin/sh # # pw usermod -n test -h - # grep test /etc/master.passwd test:$1$aXdmsI7e$IfyjlCEziFg5tp70bkA1o1:1002:1002::0:0:User &:/home/test:/bin/sh # ...is not what I was expecting! Wild guess: tcsh bug/feature? -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 2: 2:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay1.inwind.it (relay1.inwind.it [212.141.53.67]) by hub.freebsd.org (Postfix) with ESMTP id D47AA37B6F0 for ; Mon, 17 Jul 2000 02:02:51 -0700 (PDT) (envelope-from bartequi@inwind.it) Received: from bartequi.ottodomain.org (212.141.78.2) by relay1.inwind.it; 17 Jul 2000 11:02:46 +0200 From: Salvo Bartolotta Date: Mon, 17 Jul 2000 10:03:49 GMT Message-ID: <20000717.10034900@bartequi.ottodomain.org> Subject: Re: 4.0-RELEASE to 4.0-STABLE upgrade To: Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <001201bfef9b$ff42cb00$0301a8c0@timothyr.net> References: <001201bfef9b$ff42cb00$0301a8c0@timothyr.net> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2) My kernel grew from ~2.5MB to over 10MB after the upgrade. =20 kldstat -v > looks about the same, and my config file hasn't changed at all. > bash-2.03$ uname -a > FreeBSD scarlet 4.1-RC FreeBSD 4.1-RC #10: Sun Jul 16 20:26:32 PDT=20 2000 > timothyr@scarlet:/usr/src/sys/compile/DSLROUTE i386 > Any pointers appreciated. > Thanks, > -Tim Dear Timothy Robertson, you have probably compiled a kernel with debug stuff. As I recall, this should NOT change performance significantly; on the=20 other hand, it allows you to [try to] solve problems when trouble does=20 occur -- which is not a frequent phenomenon/event at any rate. Whether you keep it or not, it is your choice. Despite FreeBSD's=20 stability, it is normally a good policy to employ a debug kernel,=20 given the little to no impact on the system. If you want an "ordinary"=20 kernel, you could recompile it in the standard way (config [-r], make=20 depend, make, make install). Caveat: if you have cvsup'ed your sources again, the **safe** way to=20 go is the new buildworld, build/installkernel, etc. sequence for your=20 first kernel build, as has recently been discussed in the -stable=20 forum. The old method *may* work; however, if you use it, you are on=20 your own :-) Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 2:12:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 3A3A937B769; Mon, 17 Jul 2000 02:12:05 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id LAA89615; Mon, 17 Jul 2000 11:12:04 +0200 (CEST) (envelope-from asmodai) Date: Mon, 17 Jul 2000 11:12:03 +0200 From: Jeroen Ruigrok van der Werven To: jkh@freebsd.org Cc: stable@freebsd.org, phk@freebsd.org, jhb@freebsd.org Subject: Re: bootdisk problems/md related Message-ID: <20000717111203.B80281@lucifer.bart.nl> References: <20000714124536.J58846@lucifer.bart.nl> <20157.963571753@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20157.963571753@localhost>; from jkh@zippy.osd.bsdi.com on Fri, Jul 14, 2000 at 03:49:13AM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000714 12:50], Jordan K. Hubbard (jkh@zippy.osd.bsdi.com) wrote: >I believe the fix for this just got merged. Nope. Bootdisks from the 15th still give me problems. Exact same error messages. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I must be cruel, only to be kind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 2:25:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A738B37B79C; Mon, 17 Jul 2000 02:25:17 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id CAA05033; Mon, 17 Jul 2000 02:26:17 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Jeroen Ruigrok van der Werven Cc: stable@freebsd.org, phk@freebsd.org, jhb@freebsd.org Subject: Re: bootdisk problems/md related In-reply-to: Your message of "Mon, 17 Jul 2000 11:12:03 +0200." <20000717111203.B80281@lucifer.bart.nl> Date: Mon, 17 Jul 2000 02:26:17 -0700 Message-ID: <5030.963825977@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's very strange - we don't see the same problem here. I'll poke around a bit and see if I can reproduce it at all. - Jordan > -On [20000714 12:50], Jordan K. Hubbard (jkh@zippy.osd.bsdi.com) wrote: > >I believe the fix for this just got merged. > > Nope. > > Bootdisks from the 15th still give me problems. > > Exact same error messages. > > -- > Jeroen Ruigrok van der Werven Network- and systemadministrator > VIA Net.Works The Netherlands > BSD: Technical excellence at its best http://www.via-net-works.nl > I must be cruel, only to be kind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 2:35:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 4028F37B7C5; Mon, 17 Jul 2000 02:35:31 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id LAA93847; Mon, 17 Jul 2000 11:35:27 +0200 (CEST) (envelope-from asmodai) Date: Mon, 17 Jul 2000 11:35:26 +0200 From: Jeroen Ruigrok van der Werven To: "Jordan K. Hubbard" Cc: stable@freebsd.org, phk@freebsd.org, jhb@freebsd.org Subject: Re: bootdisk problems/md related Message-ID: <20000717113526.C80281@lucifer.bart.nl> References: <20000717111203.B80281@lucifer.bart.nl> <5030.963825977@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5030.963825977@localhost>; from jkh@zippy.osd.bsdi.com on Mon, Jul 17, 2000 at 02:26:17AM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000717 11:30], Jordan K. Hubbard (jkh@zippy.osd.bsdi.com) wrote: >That's very strange - we don't see the same problem here. I'll >poke around a bit and see if I can reproduce it at all. Thanks. Some older disks did work. I'll go download a bunch of different dates and see if I can pinpoint the date this starts happening. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Pleasure's a sin, and sometimes sin's a pleasure... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 3:55:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.pit.adelphia.net (alpha.pit.adelphia.net [24.48.44.2]) by hub.freebsd.org (Postfix) with ESMTP id 5638437B89C for ; Mon, 17 Jul 2000 03:51:26 -0700 (PDT) (envelope-from nturki@adelphia.net) Received: from Nader (pa-indiana1b-27.pit.adelphia.net [24.50.155.27]) by alpha.pit.adelphia.net (8.9.2/8.9.2) with SMTP id GAA01544 for ; Mon, 17 Jul 2000 06:51:12 -0400 (EDT) Message-ID: <002b01bfefdc$5c247540$1b9b3218@pit.adelphia.net> From: "Nader Turki" To: Subject: ERROR Date: Mon, 17 Jul 2000 06:47:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I'm not sure if this is the write email list but i thought you guys might be the only ones tto help me with such a problem. I got this machine with a 20GB IDE HD, and tried installing FreeBSD few times. But kept getting errors like: syncing disc 1012 1010 1000 bla bla ad0: UDMA ICRC WRITE ERROR blk#1315167 retrying. then the machine wouls reboot in 15 seconds! Anyway, I joined #freebsdhelp on irc and few told me you have a bad HD. So I got a new HD and installed FreeBSD and the installation went smooth no problem. Now when i try adding packages I keep getting the same error again "ad0: UDMA ICRC WRITE ERROR blk #131.... retrying" then i get another error that says: "Jul 17 06:13:55 blue /kernel: ad0: UDMA ICRC WRITE ERROR blk#1341..." I'm sure it's not the Hard Drive! Cand someone help me and tell me why am I getting that error? Thanks, Nader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 5: 5:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from prserv.net (out4.prserv.net [32.97.166.34]) by hub.freebsd.org (Postfix) with ESMTP id 13EC937B52F for ; Mon, 17 Jul 2000 05:05:28 -0700 (PDT) (envelope-from jsachs@iclick.com) Received: from iclick.com ([166.72.10.91]) by prserv.net (out4) with SMTP id <200007171205142390372sb1e>; Mon, 17 Jul 2000 12:05:15 +0000 Message-ID: <3972F657.CECC91AF@iclick.com> Date: Mon, 17 Jul 2000 08:04:39 -0400 From: Jay Sachs Organization: iClick, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: buildworld failure Content-Type: multipart/mixed; boundary="------------04DE4F977C8EFC298FE89D0C" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------04DE4F977C8EFC298FE89D0C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The traditional "config -r; cd ...; make depend && make && make install" works though. I did make buildkernel KERNEL=LUDDITE and it fails making depend in "wi". I've attached the end of the buildkernel script as well as my config file. This was on sources just supped 1/2 hour ago; it did the same last night, on source supped then, except even the traditional method failed. jay --------------04DE4F977C8EFC298FE89D0C Content-Type: text/plain; charset=us-ascii; name="failure.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="failure.txt" {standard input}:2333: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 843. {standard input}:2334: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 849. {standard input}:2337: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 855. {standard input}:2337: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 867. {standard input}:2338: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 885. {standard input}:2341: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 891. {standard input}:2341: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 903. {standard input}:2342: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 921. {standard input}:2345: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 927. {standard input}:2345: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 939. {standard input}:2346: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 957. {standard input}:2348: Error: Subtraction of two symbols in different sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file address 969. {standard input}:2350: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 975. {standard input}:2350: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 987. {standard input}:2351: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1005. {standard input}:2353: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1011. {standard input}:2353: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1023. {standard input}:2354: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1041. {standard input}:2356: Error: Subtraction of two symbols in different sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file address 1053. {standard input}:2371: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1063. {standard input}:2376: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1080. {standard input}:2379: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1103. {standard input}:2382: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1125. {standard input}:2388: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1146. {standard input}:2393: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1164. {standard input}:2396: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1183. {standard input}:2399: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1205. {standard input}:2401: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1224. {standard input}:2404: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1247. {standard input}:2406: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1266. {standard input}:2411: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1308. {standard input}:2414: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1331. {standard input}:2416: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1350. {standard input}:2422: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1392. {standard input}:2428: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1434. {standard input}:2434: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1457. {standard input}:2437: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1473. {standard input}:2440: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1496. {standard input}:2443: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1515. {standard input}:2446: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1538. {standard input}:2449: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1557. *** Error code 1 Stop in /usr/obj/usr/src/sys/LUDDITE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --------------04DE4F977C8EFC298FE89D0C Content-Type: text/plain; charset=us-ascii; name="LUDDITE" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="LUDDITE" machine i386 cpu I686_CPU ident LUDDITE maxusers 8 options INET #InterNETworking #options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=10000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device eisa device pci device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices device ahc # AHA2940 and onboard AIC7xxx devices device scbus # SCSI bus (required) device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? device sc0 at isa? flags 0x100 device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" #pseudo-device gif 4 # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter options ROOTDEVNAME=\"ufs:da0s1a\" # For PnP/PCI sound cards device pcm #options AHC_ALLOW_MEMIO --------------04DE4F977C8EFC298FE89D0C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 5: 7: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from prserv.net (out4.prserv.net [32.97.166.34]) by hub.freebsd.org (Postfix) with ESMTP id 3FE4E37B989 for ; Mon, 17 Jul 2000 05:06:50 -0700 (PDT) (envelope-from jsachs@iclick.com) Received: from iclick.com ([166.72.10.91]) by prserv.net (out4) with SMTP id <2000071712064123900e2qhoe>; Mon, 17 Jul 2000 12:06:43 +0000 Message-ID: <3972F6AF.B0AFC6E8@iclick.com> Date: Mon, 17 Jul 2000 08:06:07 -0400 From: Jay Sachs Organization: iClick, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: buildworld failure References: <3972F657.CECC91AF@iclick.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to followup to my own message, but the log got clipped. Here's a little more detail: ===> wi @ -> /usr/src/sys machine -> /usr/src/sys/i386/include perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/wi/../../i386/isa/if_wi.c cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s {standard input}: Assembler messages: {standard input}:1743: Error: .space specifies non-absolute value {standard input}:2454: Error: undefined symbol L0 in operation setting PTmap {standard input}:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap {standard input}:1711: Error: undefined symbol L0 in operation {standard input}:1711: Error: undefined symbol PAGE_SIZE in operation {standard input}:1712: Error: undefined symbol L0 in operation {standard input}:1712: Error: undefined symbol PDESIZE in operation {standard input}:2454: Error: undefined symbol L0 in operation setting APTmap {standard input}:2454: Error: undefined symbol PDRSHIFT in operation setting APTmap {standard input}:1720: Error: undefined symbol L0 in operation {standard input}:1720: Error: undefined symbol PAGE_SIZE in operation {standard input}:1721: Error: undefined symbol L0 in operation {standard input}:1721: Error: undefined symbol PDESIZE in operation {standard input}:1927: Error: undefined symbol UPAGES in operation {standard input}:1927: Error: undefined symbol PAGE_SIZE in operation {standard input}:2315: Error: undefined symbol BI_ESYMTAB in operation {standard input}:2320: Error: undefined symbol BI_SYMTAB in operation {standard input}:2321: Error: undefined symbol BI_ESYMTAB in operation {standard input}:2325: Error: undefined symbol BI_KERNEND in operation {standard input}:2337: Error: undefined symbol PAGE_SIZE in operation {standard input}:2337: Error: undefined symbol PAGE_SIZE in operation {standard input}:2341: Error: undefined symbol PAGE_SIZE in operation {standard input}:2341: Error: undefined symbol PAGE_SIZE in operation {standard input}:2345: Error: undefined symbol UPAGES in operation {standard input}:2345: Error: undefined symbol PAGE_SIZE in operation {standard input}:2345: Error: undefined symbol UPAGES in operation {standard input}:2345: Error: undefined symbol PAGE_SIZE in operation {standard input}:2350: Error: undefined symbol PAGE_SIZE in operation {standard input}:2350: Error: undefined symbol PAGE_SIZE in operation {standard input}:2353: Error: undefined symbol PAGE_SIZE in operation {standard input}:2353: Error: undefined symbol PAGE_SIZE in operation {standard input}:2410: Error: undefined symbol PAGE_SHIFT in operation {standard input}:2426: Error: undefined symbol PAGE_SHIFT in operation {standard input}:2427: Error: undefined symbol PAGE_SHIFT in operation {standard input}:1853: Error: Subtraction of two symbols in different sections ".tmpstk" {.data section} - "KERNBASE" {*UND* section} at file address 28. {standard input}:1876: Error: Subtraction of two symbols in different sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file address 38. {standard input}:1877: Error: Subtraction of two symbols in different sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file address 43. {standard input}:1889: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 61. {standard input}:1905: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 81. {standard input}:2114: Error: Subtraction of two symbols in different sections "kernelname" {*UND* section} - "KERNBASE" {*UND* section} at file address 371. {standard input}:2142: Error: Subtraction of two symbols in different sections "bootinfo" {.data section} - "KERNBASE" {*UND* section} at file address 411. {standard input}:2162: Error: Subtraction of two symbols in different sections "boothowto" {*UND* section} - "KERNBASE" {*UND* section} at file address 435. {standard input}:2164: Error: Subtraction of two symbols in different sections "bootdev" {*UND* section} - "KERNBASE" {*UND* section} at file address 443. {standard input}:2202: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 495. {standard input}:2207: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 511. {standard input}:2208: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 521. {standard input}:2209: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 531. {standard input}:2210: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 541. {standard input}:2211: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 551. {standard input}:2230: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 592. {standard input}:2257: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 627. {standard input}:2258: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 637. {standard input}:2259: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 647. {standard input}:2265: Error: Subtraction of two symbols in different sections "cpu_high" {.data section} - "KERNBASE" {*UND* section} at file address 662. {standard input}:2266: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 668. {standard input}:2267: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 674. {standard input}:2268: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 680. {standard input}:2269: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 686. {standard input}:2273: Error: Subtraction of two symbols in different sections "cpu_id" {.data section} - "KERNBASE" {*UND* section} at file address 699. {standard input}:2274: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 705. {standard input}:2281: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 722. {standard input}:2287: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 739. {standard input}:2291: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 751. {standard input}:2304: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 762. {standard input}:2312: Error: Subtraction of two symbols in different sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file address 784. {standard input}:2315: Error: Negative of non-absolute symbol KERNBASE {standard input}:2320: Error: Negative of non-absolute symbol KERNBASE {standard input}:2321: Error: Negative of non-absolute symbol KERNBASE {standard input}:2325: Error: Negative of non-absolute symbol KERNBASE {standard input}:2333: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 843. {standard input}:2334: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 849. {standard input}:2337: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 855. {standard input}:2337: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 867. {standard input}:2338: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 885. {standard input}:2341: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 891. {standard input}:2341: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 903. {standard input}:2342: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 921. {standard input}:2345: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 927. {standard input}:2345: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 939. {standard input}:2346: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 957. {standard input}:2348: Error: Subtraction of two symbols in different sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file address 969. {standard input}:2350: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 975. {standard input}:2350: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 987. {standard input}:2351: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1005. {standard input}:2353: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1011. {standard input}:2353: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1023. {standard input}:2354: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1041. {standard input}:2356: Error: Subtraction of two symbols in different sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file address 1053. {standard input}:2371: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1063. {standard input}:2376: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1080. {standard input}:2379: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1103. {standard input}:2382: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1125. {standard input}:2388: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1146. {standard input}:2393: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1164. {standard input}:2396: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1183. {standard input}:2399: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1205. {standard input}:2401: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1224. {standard input}:2404: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1247. {standard input}:2406: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1266. {standard input}:2411: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1308. {standard input}:2414: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1331. {standard input}:2416: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1350. {standard input}:2422: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1392. {standard input}:2428: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1434. {standard input}:2434: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1457. {standard input}:2437: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1473. {standard input}:2440: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1496. {standard input}:2443: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1515. {standard input}:2446: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1538. {standard input}:2449: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1557. *** Error code 1 Stop in /usr/obj/usr/src/sys/LUDDITE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 5: 9:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id DF3AC37B90F for ; Mon, 17 Jul 2000 05:09:17 -0700 (PDT) (envelope-from steve@sse0691.bri.hp.com) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id C61FA1138F; Mon, 17 Jul 2000 14:09:03 +0200 (METDST) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id NAA23573; Mon, 17 Jul 2000 13:06:38 +0100 (BST) Received: (from steve@localhost) by sse0691.bri.hp.com (8.9.3/8.9.3) id NAA35632; Mon, 17 Jul 2000 13:08:57 +0100 (BST) (envelope-from steve) Date: Mon, 17 Jul 2000 13:08:57 +0100 From: Steve Roome To: Nader Turki Cc: freebsd-stable@freebsd.org Subject: Re: ERROR Message-ID: <20000717130857.D26453@moose.bri.hp.com> References: <002b01bfefdc$5c247540$1b9b3218@pit.adelphia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <002b01bfefdc$5c247540$1b9b3218@pit.adelphia.net>; from nturki@adelphia.net on Mon, Jul 17, 2000 at 06:47:10AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 06:47:10AM -0400, Nader Turki wrote: > Hi there, > I'm not sure if this is the write email list but i thought you guys might be > the only ones tto help me with such a problem. > I got this machine with a 20GB IDE HD, and tried installing FreeBSD few > times. But kept getting errors like: > syncing disc 1012 1010 1000 bla bla > ad0: UDMA ICRC WRITE ERROR blk#1315167 retrying. > > then the machine wouls reboot in 15 seconds! > > Anyway, I joined #freebsdhelp on irc and few told me you have a bad HD. So > I got a new HD and installed FreeBSD and the installation went smooth no > problem. > > Now when i try adding packages I keep getting the same error again > "ad0: UDMA ICRC WRITE ERROR blk #131.... retrying" > then i get another error that says: > "Jul 17 06:13:55 blue /kernel: ad0: UDMA ICRC WRITE ERROR blk#1341..." I got a similar problem, possibly identical, with FreeBSD 4.0-RELEASE and a 34222Mb IBM HD (IDE, UDMA66), thinking that the disk was knackered I sent it back and asked for a replacement, they kindly told me it was fine. Some folks on this list told me that FreeBSD 4.0 is fine with my disk. I've concluded that the new ata driver and perhaps the wrong BIOS settings for my disk could have been at fault. I've since repartitioned the disk in such a way that it's working for me, for the time being. Not to start a flame war, you could try the old wd driver, which might work better, as the problem may be with the newer ata driver and some combination of UDMA/LBA. > I'm sure it's not the Hard Drive! Cand someone help me and tell me why am I > getting that error? Try the wd driver, or try the ata driver in pio mode (use sysctl hw to see what that setting is already and then set it to pio mode to see if you have more luck.) Another thing to try is to make sure you've not got any of the AUTO_EOI_* settings in your kernel, as I couldn't get them to work with the ata driver and my disk - which could also be the problem. That's a guess though! Steve P.S. For those folks thinking of flaming me for saying that the ata driver might not be up to it, please don't bother. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 5:14:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 6A32D37B961 for ; Mon, 17 Jul 2000 05:14:29 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id OAA06206 for ; Mon, 17 Jul 2000 14:14:16 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id OAA10300 for ; Mon, 17 Jul 2000 14:11:27 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C125691F.00433584 ; Mon, 17 Jul 2000 14:14:06 +0200 X-Lotus-FromDomain: ALCATEL To: STABLE@freebsd.org Message-ID: Date: Mon, 17 Jul 2000 14:13:57 +0200 Subject: lost mouse when switching back to X Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've recently upgraded two PCs to a recent snapshots (4.0-20000710-STABLE) with the new make world / make kernel procedure (from a 4.0-Release install). From the associated ports tree, I've compiled and installed XFree86 4.01 and KDE 1.1.2 When I switch from X-Windows to the text console and then back to X-windows (Ctrl-Alt-F1, then Alt-F9), the mouse pointer is fixed on the screen (When I move the "physical" mouse, the pointer stays at the same place on the X screen). This happens with both KDE and twm as window managers. I have installed XFree 3.3.6, also from the ports, and the switching from X to the text console and back works as expected - so I use this version. I'm using the system moused (moused_enable="YES" in /etc/rc.conf) TfH PS : extracts from the dmesg : pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 ...... atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 ---------------------------------------------------------- extracts from the 3.3.6 startx log : (--) Mach64: PCI (92) and CONFIG_CHIP_ID (124) don't agree on ChipRev, using PCI value (--) Mach64: Card type: AGP (--) Mach64: Memory type: SGRAM (1:1) (5) (--) Mach64: Clock type: Internal (--) Mach64: Maximum allowed dot-clock: 230.000 MHz (**) Mach64: Mode "1152x864": mode clock = 92.000 (**) Mach64: Mode "640x480": mode clock = 45.800 (**) Mach64: Mode "800x600": mode clock = 60.750 (**) Mach64: Mode "1024x768": mode clock = 85.000 (--) Mach64: Virtual resolution: 1152x864 (--) Mach64: Video RAM: 4096k (--) Mach64: Using hardware cursor (--) Mach64: Using 16 MB aperture @ 0xfd000000 (--) Mach64: Using 4 KB register aperture @ 0xfcfff000 (--) Mach64: Ramdac is Internal (--) Mach64: Ramdac speed: 230 MHz (--) Mach64: Using 8 bits per RGB value (--) Mach64: Pixmap cache: 2 256x256 slots, 8 128x128 slots, 32 64x64 slots (--) Mach64: Font cache: 16 fonts ---------------------------------------------------------- from /etc/X11//XF86Config (config file for 4.0.1) : Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/mouse" EndSection ---------------------------------------------------------- from : /usr/X11R6/lib/X11/XF86Config (config file for 3.3.6) : Section "Pointer" Protocol "PS/2" Device "/dev/mouse" EndSection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 5:38: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from elit.ci.net.ua (elit.ci.net.ua [212.86.96.11]) by hub.freebsd.org (Postfix) with ESMTP id 1D5D537B92E for ; Mon, 17 Jul 2000 05:37:59 -0700 (PDT) (envelope-from acid@ci.net.ua) Received: from localhost (acid@localhost) by elit.ci.net.ua (8.9.3/Who was second?) with ESMTP id PAA69957 for ; Mon, 17 Jul 2000 15:37:43 +0300 (EEST) Date: Mon, 17 Jul 2000 15:37:43 +0300 (EEST) From: "Michael I. Vasilenko" To: stable@freebsd.org Subject: Re: lost mouse when switching back to X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000 Thierry.Herbelot@alcatel.fr wrote: > >From the associated ports tree, I've compiled and installed XFree86 > 4.01 and KDE 1.1.2 > > When I switch from X-Windows to the text console and then back to > X-windows (Ctrl-Alt-F1, then Alt-F9), the mouse pointer is fixed on the > screen (When I move the "physical" mouse, the pointer stays at the same > place on the X screen). > > This happens with both KDE and twm as window managers. The same here. Quick & dirty fix - copy /usr/X11/lib/modules/input/mouse_drv.o from the machine with XFree86 4.0 - I can send this one to you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 5:40:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragonstar.dhs.org (dsl-028-a.resnet.purdue.edu [128.211.161.178]) by hub.freebsd.org (Postfix) with ESMTP id A2CC637B958 for ; Mon, 17 Jul 2000 05:40:27 -0700 (PDT) (envelope-from jonsmith@dragonstar.dhs.org) Received: from localhost (jonsmith@localhost) by dragonstar.dhs.org (8.9.3/8.9.3) with ESMTP id HAA20394; Mon, 17 Jul 2000 07:40:22 -0500 (EST) (envelope-from jonsmith@dragonstar.dhs.org) Date: Mon, 17 Jul 2000 07:40:21 -0500 (EST) From: Jonathan Smith To: Nader Turki Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ERROR In-Reply-To: <002b01bfefdc$5c247540$1b9b3218@pit.adelphia.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What motherboard/drive controller are you using? I've got a couple of picky Asus P5A's that don't work quite right. They accept some drives at UDMA/33 but not others. I installed a promise UltraATA/66 card in one of them and have gotten wonderful service since. j. -- Close your eyes. Now forget what you see. What do you feel? -- My heart. -- Come here. -- Your heart. -- See? We're exactly the same. Jon Smith -- Senior Math Major @ Purdue On Mon, 17 Jul 2000, Nader Turki wrote: > Hi there, > I'm not sure if this is the write email list but i thought you guys might be > the only ones tto help me with such a problem. > I got this machine with a 20GB IDE HD, and tried installing FreeBSD few > times. But kept getting errors like: > syncing disc 1012 1010 1000 bla bla > ad0: UDMA ICRC WRITE ERROR blk#1315167 retrying. > > then the machine wouls reboot in 15 seconds! > > Anyway, I joined #freebsdhelp on irc and few told me you have a bad HD. So > I got a new HD and installed FreeBSD and the installation went smooth no > problem. > > Now when i try adding packages I keep getting the same error again > "ad0: UDMA ICRC WRITE ERROR blk #131.... retrying" > then i get another error that says: > "Jul 17 06:13:55 blue /kernel: ad0: UDMA ICRC WRITE ERROR blk#1341..." > > I'm sure it's not the Hard Drive! Cand someone help me and tell me why am I > getting that error? > > Thanks, > > Nader > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 6:19:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 0C16C37B857 for ; Mon, 17 Jul 2000 06:19:54 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id JAA87742; Mon, 17 Jul 2000 09:20:03 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 17 Jul 2000 09:20:02 -0400 (EDT) From: Adam To: Nader Turki Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ERROR In-Reply-To: <002b01bfefdc$5c247540$1b9b3218@pit.adelphia.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Nader Turki wrote: >Hi there, >I'm not sure if this is the write email list but i thought you guys might be >the only ones tto help me with such a problem. >I got this machine with a 20GB IDE HD, and tried installing FreeBSD few >times. But kept getting errors like: >syncing disc 1012 1010 1000 bla bla >ad0: UDMA ICRC WRITE ERROR blk#1315167 retrying. > >then the machine wouls reboot in 15 seconds! > >Anyway, I joined #freebsdhelp on irc and few told me you have a bad HD. So >I got a new HD and installed FreeBSD and the installation went smooth no >problem. > >Now when i try adding packages I keep getting the same error again >"ad0: UDMA ICRC WRITE ERROR blk #131.... retrying" >then i get another error that says: >"Jul 17 06:13:55 blue /kernel: ad0: UDMA ICRC WRITE ERROR blk#1341..." > >I'm sure it's not the Hard Drive! Cand someone help me and tell me why am I >getting that error? Is it using ata/66 mode? Does it have an ata/66 80 min cable? If so, try a 33 pin cable so it knocks it down to dma/33, I have a drive that didnt work reliably till I did such. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 7:26:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 73DFC37B9B0 for ; Mon, 17 Jul 2000 07:26:26 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id JAA78700 for ; Mon, 17 Jul 2000 09:27:16 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <003401bfeffb$19083020$b8209fc0@campbellmithun.com> From: "Shawn Barnhart" To: Subject: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Mon, 17 Jul 2000 09:27:11 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My buildworld is failing, often in the same places, and always with a signal 11, which I think is a segmentation violation (SIGSEGV). When I first attempted buildworld it died right away. I rebooted the machine and it got further, but died again with the same error. Subsequent attempts died early; reboot and it dies later. I've recently moved this system to an Asus TXP4 motherboard with an AMD K6-233 CPU and a single 128MB stick of PC100 SDRAM. No overclocking or other hardware hackery is being used. The same machine had been running (blush) Windows 2000 since March with little or no problems -- no problem with lockups, blue screens, etc. The FreeBSD install I'm using had previously been running on a generic Dell Pentium 200 and lived through a half-dozen buildworlds without breaking. Since I haven't seen a anyone else's world breaking this way, I'm assuming that this is a hardware problem -- but what kind? Memory? I have a spare Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start? FWIW, I cvsup'd numerous times throughout 16-July, in case I caught things during a commit. -- swb@grasslake.net Hard work often pays off after time, but laziness always pays off now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 7:34:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from botbay.net (botbay.net [151.197.159.116]) by hub.freebsd.org (Postfix) with ESMTP id ECABB37B9E5 for ; Mon, 17 Jul 2000 07:34:44 -0700 (PDT) (envelope-from wcampbel@botbay.net) Received: from localhost (wcampbel@localhost) by botbay.net (8.9.3/8.9.3) with ESMTP id KAA45063; Mon, 17 Jul 2000 10:34:17 -0400 (EDT) (envelope-from wcampbel@botbay.net) Date: Mon, 17 Jul 2000 10:34:17 -0400 (EDT) From: Walter Campbell To: Shawn Barnhart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? In-Reply-To: <003401bfeffb$19083020$b8209fc0@campbellmithun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The FreeBSD install I'm using had previously been running on a generic Dell > Pentium 200 and lived through a half-dozen buildworlds without breaking. > > Since I haven't seen a anyone else's world breaking this way, I'm assuming > that this is a hardware problem -- but what kind? Memory? I have a spare > Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start? > Memory is likely the problem, but also look at the L2 cache and anything else that may cause memory corruption. One of my BSD box was having SIGSEGV's when compiling and occasional reboots. I have had no instability since replacing the L2 cache To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 7:57:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id DFE1E37B9BE for ; Mon, 17 Jul 2000 07:57:55 -0700 (PDT) (envelope-from keith.mackay@home.com) Received: from odin ([24.68.24.241]) by mail.rdc2.on.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20000717145754.ZZGM19444.mail.rdc2.on.home.com@odin> for ; Mon, 17 Jul 2000 07:57:54 -0700 From: "Keith Mackay" To: Subject: bioscall.s Date: Mon, 17 Jul 2000 10:58:06 -0400 Message-ID: <000d01bfefff$6aa12d70$f1184418@asgard> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a known issue in bioscall.s? When I make the kernel, I get an unknown i386 instruction the lines causing this (and there are two which are identical) are lcall *_bioscall_vector when I remove the *, the kernel compiles fine, and there don't seem to be any problems after a reboot Any suggestions? Regards, Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 8: 3:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 36C9837B582 for ; Mon, 17 Jul 2000 08:03:26 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id F32439B1C; Mon, 17 Jul 2000 11:03:24 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id E245BBA11; Mon, 17 Jul 2000 11:03:24 -0400 (EDT) Date: Mon, 17 Jul 2000 11:03:24 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Keith Mackay Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s In-Reply-To: <000d01bfefff$6aa12d70$f1184418@asgard> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Keith Mackay wrote: > Is there a known issue in bioscall.s? > > When I make the kernel, I get an unknown i386 instruction > As usual, read /usr/src/UPDATING (20000706 entry) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 8:10:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gandalf.defero.net (gandalf.defero.net [212.73.3.251]) by hub.freebsd.org (Postfix) with ESMTP id B98BB37B582 for ; Mon, 17 Jul 2000 08:09:34 -0700 (PDT) (envelope-from johan.huldtgren@rixtelecom.se) Received: from drinklikafix ([212.73.4.66]) by gandalf.defero.net (8.9.3/8.9.3) with SMTP id RAA01609 for ; Mon, 17 Jul 2000 17:09:27 +0200 (MET DST) From: "Johan Huldtgren" To: Subject: 2 different problems Date: Mon, 17 Jul 2000 17:09:17 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0000_01BFF011.BD555660" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0000_01BFF011.BD555660 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I just rebuilt world on my two machines, one successfully(well..) and one failed. Both were CVSuped last night(17/7/00), approx 05:00 CET. Now on first machine I followed the officially sanctioned way. Went through all the steps without encountering any problems(as far as I noticed). After I rebooted, I recompiled my custom kernel. To my slight astonishment though my keyboard has reset itself the american default, although my rc.conf clearly specifies that swedish.cp580 is to be used. I figure I can wait until my kernel has compiled before I look deeper into that. Well 20 minutes and a reboot later the problem remains. I also notice that I have no connection to the net anymore, ifconfig -a gives me that my network cards are down. I can find no other reason for all this except that my rc.conf file isn't being read properly. So I copy past all my values from /etc/rc.conf to /etc/defaults/rc.conf and now everything works fine. The rc.conf file is attached. Now my second machine gets as far as "make installworld" it fails on: ln: /usr/share/man/man3/setruid.3.gz: No such file or directory *** Error code 1 the full output is attached. Now I'm sure both my problems are simple and are the results of a lot of work and no sleep. So be gentle :) Sincerely, Johan Huldtgren ------=_NextPart_000_0000_01BFF011.BD555660 Content-Type: application/octet-stream; name="iw.out" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="iw.out" Script started on Mon Jul 17 15:32:14 2000=0A= bash-2.03# shutdown now=08=08=08=08 = =08=08=08=08=08=08=08=08=08=08=08=08last | = more=08=08=08=08=08=08=08=08=08=08=08shutdown =08=08=08 = now=08=08=08=08=08=08=08=08=08=08=08=08 = =08=08=08=08=08=08=08=08=08=08=08=08make -j5 ins=07tallworld cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj = COMPILER_PATH=3D/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/u= sr/bin = LIBRARY_PATH=3D/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/li= b OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec = PERL5LIB=3D/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 make -f = Makefile.inc1 reinstall -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc; make distrib-dirs mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p = /usr/libdata/perl/5.00503/mach cd /; rm -f /sys; ln -s usr/src/sys sys cd /usr/share/locale; `cat /usr/src/etc/locale.alias`; while [ $# -gt = 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done -------------------------------------------------------------- >>> Installing everything.. -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 install =3D=3D=3D> share/info =3D=3D=3D> include if [ -h /usr/include/cam ]; then rm -f /usr/include/cam; fi if [ -h /usr/include/msdosfs ]; then rm -f /usr/include/msdosfs; fi if [ -h /usr/include/net ]; then rm -f /usr/include/net; fi if [ -h /usr/include/netatalk ]; then rm -f /usr/include/netatalk; fi if [ -h /usr/include/netatm ]; then rm -f /usr/include/netatm; fi if [ -h /usr/include/netgraph ]; then rm -f /usr/include/netgraph; fi if [ -h /usr/include/netinet ]; then rm -f /usr/include/netinet; fi if [ -h /usr/include/netinet6 ]; then rm -f /usr/include/netinet6; fi if [ -h /usr/include/netipx ]; then rm -f /usr/include/netipx; fi if [ -h /usr/include/netkey ]; then rm -f /usr/include/netkey; fi if [ -h /usr/include/netncp ]; then rm -f /usr/include/netncp; fi if [ -h /usr/include/netns ]; then rm -f /usr/include/netns; fi if [ -h /usr/include/nfs ]; then rm -f /usr/include/nfs; fi if [ -h /usr/include/ntfs ]; then rm -f /usr/include/ntfs; fi if [ -h /usr/include/nwfs ]; then rm -f /usr/include/nwfs; fi if [ -h /usr/include/pccard ]; then rm -f /usr/include/pccard; fi if [ -h /usr/include/posix4 ]; then rm -f /usr/include/posix4; fi if [ -h /usr/include/sys ]; then rm -f /usr/include/sys; fi if [ -h /usr/include/vm ]; then rm -f /usr/include/vm; fi if [ -h /usr/include/isofs/cd9660 ]; then rm -f = /usr/include/isofs/cd9660; fi if [ -h /usr/include/ufs/ffs ]; then rm -f /usr/include/ufs/ffs; fi if [ -h /usr/include/ufs/mfs ]; then rm -f /usr/include/ufs/mfs; fi if [ -h /usr/include/ufs/ufs ]; then rm -f /usr/include/ufs/ufs; fi if [ -h /usr/include/dev/ppbus ]; then rm -f /usr/include/dev/ppbus; = fi if [ -h /usr/include/dev/usb ]; then rm -f /usr/include/dev/usb; fi if [ -h /usr/include/machine ]; then rm -f /usr/include/machine; fi rm -rf /usr/include/isofs rm -rf /usr/include/ufs rm -rf /usr/include/dev mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p = /usr/include missing: ./dev (created) missing: ./dev/ppbus (created) missing: ./dev/usb (created) missing: ./isofs (created) missing: ./isofs/cd9660 (created) missing: ./ufs (created) missing: ./ufs/ffs (created) missing: ./ufs/mfs (created) missing: ./ufs/ufs (created) cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h = /usr/include/cam cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = msdosfs/*.h /usr/include/msdosfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 net/*.h = /usr/include/net cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netatalk/*.h /usr/include/netatalk cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netatm/*.h /usr/include/netatm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netgraph/*.h /usr/include/netgraph cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netinet/*.h /usr/include/netinet cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netinet6/*.h /usr/include/netinet6 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netipx/*.h /usr/include/netipx cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netkey/*.h /usr/include/netkey cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netncp/*.h /usr/include/netncp cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netns/*.h /usr/include/netns cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 nfs/*.h = /usr/include/nfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ntfs/*.h = /usr/include/ntfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 nwfs/*.h = /usr/include/nwfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = pccard/*.h /usr/include/pccard cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = posix4/*.h /usr/include/posix4 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 sys/*.h = /usr/include/sys cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 vm/*.h = /usr/include/vm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = isofs/cd9660/*.h /usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = ufs/ffs/*.h /usr/include/ufs/ffs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = ufs/mfs/*.h /usr/include/ufs/mfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = ufs/ufs/*.h /usr/include/ufs/ufs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = cam/scsi/*.h /usr/include/cam/scsi cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = dev/ppbus/*.h /usr/include/dev/ppbus cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = dev/usb/*.h /usr/include/dev/usb cd /usr/src/include/../sys/i386/include; install -C -o root -g wheel -m = 444 *.h /usr/include/machine ln -sf ../sys/soundcard.h /usr/include/machine/soundcard.h ln -sf ../sys/joystick.h /usr/include/machine/joystick.h cd /usr/src/include; install -C -o root -g wheel -m 444 a.out.h ar.h = assert.h bitstring.h ctype.h db.h dirent.h disktab.h dlfcn.h elf.h = err.h fnmatch.h fstab.h fts.h glob.h grp.h strhash.h histedit.h = ieeefp.h ifaddrs.h iso646.h limits.h link.h locale.h malloc.h memory.h = mpool.h ndbm.h netdb.h nl_types.h nlist.h objformat.h paths.h = pthread.h pthread_np.h pwd.h ranlib.h regex.h regexp.h resolv.h rune.h = runetype.h setjmp.h sgtty.h signal.h stab.h stddef.h stdio.h stdlib.h = string.h stringlist.h strings.h struct.h sysexits.h tar.h time.h = timers.h ttyent.h unistd.h utime.h utmp.h vis.h /usr/include cd /usr/src/include/arpa; install -C -o root -g wheel -m 444 ftp.h = inet.h nameser.h nameser_compat.h telnet.h tftp.h /usr/include/arpa cd /usr/src/include/protocols; install -C -o root -g wheel -m 444 = dumprestore.h routed.h rwhod.h talkd.h timed.h /usr/include/protocols cd /usr/src/include/rpc; install -C -o root -g wheel -m 444 auth.h = auth_unix.h clnt.h pmap_clnt.h pmap_prot.h pmap_rmt.h rpc.h rpc_com.h = rpc_msg.h svc.h svc_auth.h types.h xdr.h auth_des.h des.h des_crypt.h = /usr/include/rpc install -C -o root -g wheel -m 444 /usr/obj/usr/src/include/osreldate.h = /usr/include ln -sf sys/aio.h /usr/include/aio.h ln -sf sys/errno.h /usr/include/errno.h ln -sf sys/fcntl.h /usr/include/fcntl.h ln -sf sys/inttypes.h /usr/include/inttypes.h ln -sf sys/linker_set.h /usr/include/linker_set.h ln -sf sys/poll.h /usr/include/poll.h ln -sf sys/syslog.h /usr/include/syslog.h ln -sf sys/termios.h /usr/include/termios.h ln -sf sys/ucontext.h /usr/include/ucontext.h ln -sf machine/float.h /usr/include/float.h ln -sf machine/floatingpoint.h /usr/include/floatingpoint.h ln -sf machine/stdarg.h /usr/include/stdarg.h ln -sf machine/varargs.h /usr/include/varargs.h ln -sf posix4/mqueue.h /usr/include/mqueue.h ln -sf posix4/sched.h /usr/include/sched.h ln -sf posix4/semaphore.h /usr/include/semaphore.h =3D=3D=3D> include/rpcsvc install -C -o root -g wheel -m 444 /usr/src/include/rpcsvc/yp_prot.h = /usr/src/include/rpcsvc/ypclnt.h /usr/src/include/rpcsvc/nis_db.h = /usr/src/include/rpcsvc/nis_tags.h /usr/src/include/rpcsvc/nislib.h = /usr/src/include/rpcsvc/bootparam_prot.x = /usr/src/include/rpcsvc/key_prot.x /usr/src/include/rpcsvc/klm_prot.x = /usr/src/include/rpcsvc/mount.x /usr/src/include/rpcsvc/nfs_prot.x = /usr/src/include/rpcsvc/nlm_prot.x /usr/src/include/rpcsvc/rex.x = /usr/src/include/rpcsvc/rnusers.x /usr/src/include/rpcsvc/rquota.x = /usr/src/include/rpcsvc/rstat.x /usr/src/include/rpcsvc/rwall.x = /usr/src/include/rpcsvc/sm_inter.x /usr/src/include/rpcsvc/spray.x = /usr/src/include/rpcsvc/yppasswd.x /usr/src/include/rpcsvc/yp.x = /usr/src/include/rpcsvc/ypxfrd.x /usr/src/include/rpcsvc/ypupdate_prot.x = /usr/src/include/rpcsvc/nis.x /usr/src/include/rpcsvc/nis_cache.x = /usr/src/include/rpcsvc/nis_object.x = /usr/src/include/rpcsvc/nis_callback.x /usr/src/include/rpcsvc/crypt.x = key_prot.h klm_prot.h mount.h nfs_prot.h nlm_prot.h rex.h rnusers.h = rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h = ypupdate_prot.h nis.h nis_cache.h nis_callback.h bootparam_prot.h = crypt.h /usr/include/rpcsvc install -C -o root -g wheel -m 444 key_prot.h /usr/include/rpc =3D=3D=3D> lib =3D=3D=3D> lib/csu/i386-elf install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o install -c -o root -g wheel -m 444 crtbegin.So /usr/lib/crtbeginS.o install -c -o root -g wheel -m 444 crtend.So /usr/lib/crtendS.o =3D=3D=3D> lib/libcom_err cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 = /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include install -c -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 = /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -c -o root -g wheel -m 444 libcom_err.a /usr/lib install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib ln -sf libcom_err.so.2 /usr/lib/libcom_err.so =3D=3D=3D> lib/libcom_err/doc install-info --quiet --defsection=3D"Programming & development tools." = --defentry=3D"* libcom_err: (com_err). A Common Error Description = Library for UNIX." com_err.info /usr/share/info/dir install -c -o root -g wheel -m 444 com_err.info.gz /usr/share/info =3D=3D=3D> lib/libcrypt install -c -o root -g wheel -m 444 crypt.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libscrypt.a /usr/lib install -c -s -o root -g wheel -m 444 -fschg libscrypt.so.2 /usr/lib ln -sf libscrypt.so.2 /usr/lib/libscrypt.so =3D=3D=3D> lib/../secure/lib/libcrypt install -c -o root -g wheel -m 444 crypt.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libdescrypt.a /usr/lib install -c -s -o root -g wheel -m 444 -fschg libdescrypt.so.2 = /usr/lib ln -sf libdescrypt.so.2 /usr/lib/libdescrypt.so =3D=3D=3D> lib/msun install -C -o root -g wheel -m 444 /usr/src/lib/msun/src/math.h = /usr/include install -c -o root -g wheel -m 444 acos.3.gz acosh.3.gz asin.3.gz = asinh.3.gz atan.3.gz atan2.3.gz atanh.3.gz ceil.3.gz cos.3.gz cosh.3.gz = erf.3.gz exp.3.gz fabs.3.gz floor.3.gz fmod.3.gz hypot.3.gz ieee.3.gz = ieee_test.3.gz j0.3.gz lgamma.3.gz math.3.gz rint.3.gz sin.3.gz = sinh.3.gz sqrt.3.gz tan.3.gz tanh.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libm.a /usr/lib /usr/share/man/man3/acosf.3.gz -> /usr/share/man/man3/acos.3.gz install -c -s -o root -g wheel -m 444 libm.so.2 /usr/lib /usr/share/man/man3/acoshf.3.gz -> /usr/share/man/man3/acosh.3.gz /usr/share/man/man3/asinf.3.gz -> /usr/share/man/man3/asin.3.gz /usr/share/man/man3/asinhf.3.gz -> /usr/share/man/man3/asinh.3.gz /usr/share/man/man3/atanf.3.gz -> /usr/share/man/man3/atan.3.gz /usr/share/man/man3/atanhf.3.gz -> /usr/share/man/man3/atanh.3.gz ln -sf libm.so.2 /usr/lib/libm.so /usr/share/man/man3/atan2f.3.gz -> /usr/share/man/man3/atan2.3.gz /usr/share/man/man3/ceilf.3.gz -> /usr/share/man/man3/ceil.3.gz /usr/share/man/man3/cosf.3.gz -> /usr/share/man/man3/cos.3.gz /usr/share/man/man3/coshf.3.gz -> /usr/share/man/man3/cosh.3.gz /usr/share/man/man3/erfc.3.gz -> /usr/share/man/man3/erf.3.gz /usr/share/man/man3/erff.3.gz -> /usr/share/man/man3/erf.3.gz /usr/share/man/man3/erfcf.3.gz -> /usr/share/man/man3/erf.3.gz /usr/share/man/man3/expm1.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log10.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log1p.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/pow.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/expf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp2.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp2f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp10.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp10f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/expm1f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/logf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log2.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log2f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/powf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log10f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log1pf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/fabsf.3.gz -> /usr/share/man/man3/fabs.3.gz /usr/share/man/man3/floorf.3.gz -> /usr/share/man/man3/floor.3.gz /usr/share/man/man3/fmodf.3.gz -> /usr/share/man/man3/fmod.3.gz /usr/share/man/man3/cabs.3.gz -> /usr/share/man/man3/hypot.3.gz /usr/share/man/man3/cabsf.3.gz -> /usr/share/man/man3/hypot.3.gz /usr/share/man/man3/hypotf.3.gz -> /usr/share/man/man3/hypot.3.gz /usr/share/man/man3/copysign.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/copysignf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/finite.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/finitef.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/ilogb.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/ilogbf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/nextafter.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/nextafterf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/remainder.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/remainderf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/scalbn.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/scalbnf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/logb.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/logbf.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/scalb.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/scalbf.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/significand.3.gz -> = /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/significandf.3.gz -> = /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/j1.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/jn.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y0.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y1.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y1f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/yn.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/j0f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/j1f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/jnf.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y0f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/ynf.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/gamma.3.gz -> /usr/share/man/man3/lgamma.3.gz /usr/share/man/man3/lgammaf.3.gz -> /usr/share/man/man3/lgamma.3.gz /usr/share/man/man3/gammaf.3.gz -> /usr/share/man/man3/lgamma.3.gz /usr/share/man/man3/rintf.3.gz -> /usr/share/man/man3/rint.3.gz /usr/share/man/man3/sinf.3.gz -> /usr/share/man/man3/sin.3.gz /usr/share/man/man3/sinhf.3.gz -> /usr/share/man/man3/sinh.3.gz /usr/share/man/man3/cbrt.3.gz -> /usr/share/man/man3/sqrt.3.gz /usr/share/man/man3/cbrtf.3.gz -> /usr/share/man/man3/sqrt.3.gz /usr/share/man/man3/sqrtf.3.gz -> /usr/share/man/man3/sqrt.3.gz /usr/share/man/man3/tanf.3.gz -> /usr/share/man/man3/tan.3.gz /usr/share/man/man3/tanhf.3.gz -> /usr/share/man/man3/tanh.3.gz =3D=3D=3D> lib/libmd cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 md2.h = /usr/include install -c -o root -g wheel -m 444 md2.3.gz md4.3.gz md5.3.gz = ripemd.3.gz sha.3.gz /usr/share/man/man3 cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 md4.h = /usr/include cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 md5.h = /usr/include cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 ripemd.h = /usr/include /usr/share/man/man3/MD2Init.3.gz -> /usr/share/man/man3/md2.3.gz cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 sha.h = /usr/include /usr/share/man/man3/MD2Update.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2Final.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2End.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2File.3.gz -> /usr/share/man/man3/md2.3.gz install -c -o root -g wheel -m 444 libmd.a /usr/lib /usr/share/man/man3/MD2Data.3.gz -> /usr/share/man/man3/md2.3.gz install -c -s -o root -g wheel -m 444 libmd.so.2 /usr/lib /usr/share/man/man3/MD4Init.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Update.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Final.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4End.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4File.3.gz -> /usr/share/man/man3/md4.3.gz ln -sf libmd.so.2 /usr/lib/libmd.so /usr/share/man/man3/MD4Data.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD5Init.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Update.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Final.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5End.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5File.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Data.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/RIPEMD160_Init.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Update.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Final.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Data.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_End.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_File.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/SHA_Init.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Update.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Final.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_End.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_File.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Data.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Init.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Update.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Final.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_End.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_File.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Data.3.gz -> /usr/share/man/man3/sha.3.gz =3D=3D=3D> lib/libncurses install -c -o root -g wheel -m 444 term.7.gz /usr/share/man/man7 install -c -o root -g wheel -m 444 curs_addch.3.gz curs_addchstr.3.gz = curs_addstr.3.gz curs_attr.3.gz curs_beep.3.gz curs_bkgd.3.gz = curs_border.3.gz curs_clear.3.gz curs_color.3.gz curs_delch.3.gz = curs_deleteln.3.gz curs_extend.3.gz curs_getch.3.gz curs_getstr.3.gz = curs_getyx.3.gz curs_inch.3.gz curs_inchstr.3.gz curs_initscr.3.gz = curs_inopts.3.gz curs_insch.3.gz curs_insstr.3.gz curs_instr.3.gz = curs_kernel.3.gz curs_mouse.3.gz curs_move.3.gz curs_outopts.3.gz = curs_overlay.3.gz curs_pad.3.gz curs_print.3.gz curs_printw.3.gz = curs_refresh.3.gz curs_scanw.3.gz curs_scr_dump.3.gz curs_scroll.3.gz = curs_slk.3.gz curs_termattrs.3.gz curs_termcap.3.gz curs_terminfo.3.gz = curs_touch.3.gz curs_util.3.gz curs_window.3.gz define_key.3.gz = dft_fgbg.3.gz keybound.3.gz keyok.3.gz ncurses.3.gz resizeterm.3.gz = wresize.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 term.5.gz terminfo.5.gz = /usr/share/man/man5 install -c -o root -g wheel -m 444 curses.h term.h termcap.h unctrl.h = /usr/include /usr/share/man/man3/curses.3.gz -> /usr/share/man/man3/ncurses.3.gz rm -f /usr/include/ncurses.h /usr/share/man/man3/addch.3.gz -> /usr/share/man/man3/curs_addch.3.gz ln -s curses.h /usr/include/ncurses.h /usr/share/man/man3/echochar.3.gz -> /usr/share/man/man3/curs_addch.3.gz install -c -o root -g wheel -m 444 libncurses.a /usr/lib /usr/share/man/man3/mvaddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/mvwaddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz install -c -s -o root -g wheel -m 444 libncurses.so.5 /usr/lib /usr/share/man/man3/waddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/wechochar.3.gz -> = /usr/share/man/man3/curs_addch.3.gz ln -sf libncurses.so.5 /usr/lib/libncurses.so /usr/share/man/man3/addchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libcurses.a -> libncurses.a /usr/lib/libtermcap.a -> libncurses.a /usr/lib/libtermlib.a -> libncurses.a /usr/share/man/man3/addchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libmytinfo.a -> libncurses.a /usr/lib/libtinfo.a -> libncurses.a /usr/lib/libcurses.so -> libncurses.so /usr/share/man/man3/mvaddchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libtermcap.so -> libncurses.so /usr/lib/libtermlib.so -> libncurses.so /usr/lib/libmytinfo.so -> libncurses.so /usr/share/man/man3/mvaddchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libtinfo.so -> libncurses.so /usr/share/man/man3/mvwaddchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/mvwaddchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/waddchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/waddchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/addnstr.3.gz -> /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/addstr.3.gz -> /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvaddnstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvaddstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvwaddnstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvwaddstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/waddnstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/waddstr.3.gz -> /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/attr_get.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attr_off.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attr_on.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attr_set.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attroff.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attron.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attrset.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/chgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/color_set.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/mvchgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/mvwchgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/standend.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/standout.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_get.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_off.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_on.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_set.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattroff.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattron.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattrset.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wchgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wcolor_set.3.gz -> = /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wstandend.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wstandout.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/beep.3.gz -> /usr/share/man/man3/curs_beep.3.gz /usr/share/man/man3/flash.3.gz -> /usr/share/man/man3/curs_beep.3.gz /usr/share/man/man3/bkgd.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/bkgdset.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/getbkgd.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/wbkgd.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/wbkgdset.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/border.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/box.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/hline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/mvhline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/mvwhline.3.gz -> = /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/mvwvline.3.gz -> = /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/vline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/wborder.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/whline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/wvline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/clear.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/clrtobot.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/clrtoeol.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/erase.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/wclear.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/wclrtobot.3.gz -> = /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/wclrtoeol.3.gz -> = /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/werase.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/can_change_color.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/color_content.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/has_colors.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/init_color.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/init_pair.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/pair_content.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/start_color.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/delch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/mvdelch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/mvwdelch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/wdelch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/deleteln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/insdelln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/insertln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/wdeleteln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/winsdelln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/winsertln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/curses_version.3.gz -> = /usr/share/man/man3/curs_extend.3.gz /usr/share/man/man3/use_extended_names.3.gz -> = /usr/share/man/man3/curs_extend.3.gz /usr/share/man/man3/getch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/has_key.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/mvgetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/mvwgetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/ungetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/wgetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/getnstr.3.gz -> /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/getstr.3.gz -> /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvgetnstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvgetstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvwgetnstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvwgetstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/wgetnstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/wgetstr.3.gz -> /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/getbegyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/getmaxyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/getparyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/getyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/inch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/mvinch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/mvwinch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/winch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/inchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/inchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvinchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvinchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvwinchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvwinchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/winchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/winchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/delscreen.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/endwin.3.gz -> /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/initscr.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/isendwin.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/newterm.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/set_term.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/cbreak.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/echo.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/halfdelay.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/intrflush.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/keypad.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/meta.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/nocbreak.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/nodelay.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/noecho.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/noqiflush.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/noraw.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/notimeout.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/qiflush.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/raw.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/timeout.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/typeahead.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/wtimeout.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/insch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/mvinsch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/mvwinsch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/winsch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/insnstr.3.gz -> /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/insstr.3.gz -> /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvinsnstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvinsstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvwinsnstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvwinsstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/winsnstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/winsstr.3.gz -> /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/innstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/instr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvinnstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvinstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvwinnstr.3.gz -> = /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvwinstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/winnstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/winstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/curs_set.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/def_prog_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/def_shell_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/getsyx.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/napms.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/reset_prog_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/reset_shell_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/resetty.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/ripoffline.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/savetty.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/setsyx.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/getmouse.3.gz -> /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/mouseinterval.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/mousemask.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/ungetmouse.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/wenclose.3.gz -> /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/wmouse_trafo.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/move.3.gz -> /usr/share/man/man3/curs_move.3.gz /usr/share/man/man3/wmove.3.gz -> /usr/share/man/man3/curs_move.3.gz /usr/share/man/man3/clearok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/idcok.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/idlok.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/immedok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/leaveok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/nl.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/nonl.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/scrollok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/setscrreg.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/wsetscrreg.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/copywin.3.gz -> = /usr/share/man/man3/curs_overlay.3.gz /usr/share/man/man3/overlay.3.gz -> = /usr/share/man/man3/curs_overlay.3.gz /usr/share/man/man3/overwrite.3.gz -> = /usr/share/man/man3/curs_overlay.3.gz /usr/share/man/man3/newpad.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/pechochar.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/pnoutrefresh.3.gz -> = /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/prefresh.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/subpad.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/mcprint.3.gz -> /usr/share/man/man3/curs_print.3.gz /usr/share/man/man3/mvprintw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/mvwprintw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/printw.3.gz -> /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/vw_printw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/vwprintw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/wprintw.3.gz -> /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/doupdate.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/redrawwin.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/refresh.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/wnoutrefresh.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/wredrawln.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/wrefresh.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/mvscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/mvwscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/scanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/vw_scanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/vwscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/wscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/scr_dump.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scr_init.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scr_restore.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scr_set.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scrl.3.gz -> /usr/share/man/man3/curs_scroll.3.gz /usr/share/man/man3/scroll.3.gz -> /usr/share/man/man3/curs_scroll.3.gz /usr/share/man/man3/wscrl.3.gz -> /usr/share/man/man3/curs_scroll.3.gz /usr/share/man/man3/slk_attr.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attr_off.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attr_on.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attr_set.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attroff.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attron.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attrset.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_clear.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_color.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_init.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_label.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_noutrefresh.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_refresh.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_restore.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_set.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_touch.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/baudrate.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/erasechar.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/has_ic.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/has_il.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/killchar.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/longname.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/termattrs.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/termname.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/tgetent.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgetflag.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgetnum.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgetstr.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgoto.3.gz -> /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tputs.3.gz -> /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/del_curterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/mvcur.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/putp.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/restartterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/set_curterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/setterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/setupterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tigetflag.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tigetnum.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tigetstr.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tparm.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tputs.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/vidattr.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/vidputs.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/is_linetouched.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/is_wintouched.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/touchline.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/touchwin.3.gz -> /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/untouchwin.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/wtouchln.3.gz -> /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/delay_output.3.gz -> = /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/filter.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/flushinp.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/getwin.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/keyname.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/putwin.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/unctrl.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/use_env.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/delwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/derwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/dupwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/mvderwin.3.gz -> = /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/mvwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/newwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/subwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/syncok.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/wcursyncup.3.gz -> = /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/wsyncdown.3.gz -> = /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/wsyncup.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/use_default_colors.3.gz -> = /usr/share/man/man3/dft_fgbg.3.gz cd /usr/src/lib/libncurses/../../contrib/ncurses/misc ; install -c -o = root -g wheel -m 444 ncurses-intro.html /usr/share/doc/ncurses cd /usr/src/lib/libncurses/../../contrib/ncurses/misc ; install -c -o = root -g wheel -m 444 hackguide.html /usr/share/doc/ncurses =3D=3D=3D> lib/libradius cd /usr/src/lib/libradius && install -C -o root -g wheel -m 444 = radlib.h /usr/include install -c -o root -g wheel -m 444 libradius.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 radius.conf.5.gz /usr/share/man/man5 install -c -o root -g wheel -m 444 libradius.a /usr/lib install -c -s -o root -g wheel -m 444 libradius.so.1 /usr/lib ln -sf libradius.so.1 /usr/lib/libradius.so =3D=3D=3D> lib/libskey cd /usr/src/lib/libskey && install -C -o root -g wheel -m 444 skey.h = /usr/include install -c -o root -g wheel -m 444 skey.1.gz /usr/share/man/man1 install -c -o root -g wheel -m 444 skey.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 skey.access.5.gz /usr/share/man/man5 install -c -o root -g wheel -m 444 libskey.a /usr/lib install -c -s -o root -g wheel -m 444 libskey.so.2 /usr/lib /usr/share/man/man3/skeylookup.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skeyverify.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skeychallenge.3.gz -> /usr/share/man/man3/skey.3.gz ln -sf libskey.so.2 /usr/lib/libskey.so /usr/share/man/man3/skeyinfo.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skeyaccess.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skey_getpass.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skey_crypt.3.gz -> /usr/share/man/man3/skey.3.gz =3D=3D=3D> lib/libtacplus cd /usr/src/lib/libtacplus && install -C -o root -g wheel -m 444 = taclib.h /usr/include install -c -o root -g wheel -m 444 libtacplus.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 tacplus.conf.5.gz = /usr/share/man/man5 install -c -o root -g wheel -m 444 libtacplus.a /usr/lib install -c -s -o root -g wheel -m 444 libtacplus.so.1 /usr/lib ln -sf libtacplus.so.1 /usr/lib/libtacplus.so =3D=3D=3D> lib/libutil cd /usr/src/lib/libutil && install -C -o root -g wheel -m 444 = libutil.h /usr/include install -c -o root -g wheel -m 444 login.3.gz login_auth.3.gz = login_tty.3.gz logout.3.gz logwtmp.3.gz pty.3.gz setproctitle.3.gz = login_cap.3.gz login_class.3.gz login_times.3.gz login_ok.3.gz = _secure_path.3.gz uucplock.3.gz property.3.gz auth.3.gz = realhostname.3.gz realhostname_sa.3.gz trimdomain.3.gz fparseln.3.gz = /usr/share/man/man3 cd /usr/src/lib/libutil && install -C -o root -g wheel -m 444 = login_cap.h /usr/include install -c -o root -g wheel -m 444 login.conf.5.gz auth.conf.5.gz = /usr/share/man/man5 /usr/share/man/man3/properties_read.3.gz -> = /usr/share/man/man3/property.3.gz install -c -o root -g wheel -m 444 libutil.a /usr/lib /usr/share/man/man3/properties_free.3.gz -> = /usr/share/man/man3/property.3.gz install -c -s -o root -g wheel -m 444 libutil.so.3 /usr/lib /usr/share/man/man3/property_find.3.gz -> = /usr/share/man/man3/property.3.gz ln -sf libutil.so.3 /usr/lib/libutil.so /usr/share/man/man3/auth_getval.3.gz -> /usr/share/man/man3/auth.3.gz /usr/share/man/man3/openpty.3.gz -> /usr/share/man/man3/pty.3.gz /usr/share/man/man3/forkpty.3.gz -> /usr/share/man/man3/pty.3.gz /usr/share/man/man3/login_getclassbyname.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_close.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getclass.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getuserclass.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapstr.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcaplist.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getstyle.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcaptime.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapnum.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapsize.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapbool.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getpath.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getpwclass.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/setusercontext.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/setclasscontext.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/setclassenvironment.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/setclassresources.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/parse_lt.3.gz -> = /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_ltm.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_lt.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_ltms.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_lts.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/auth_ttyok.3.gz -> /usr/share/man/man3/login_ok.3.gz /usr/share/man/man3/auth_hostok.3.gz -> = /usr/share/man/man3/login_ok.3.gz /usr/share/man/man3/auth_timeok.3.gz -> = /usr/share/man/man3/login_ok.3.gz /usr/share/man/man3/auth_checknologin.3.gz -> = /usr/share/man/man3/login_auth.3.gz /usr/share/man/man3/auth_cat.3.gz -> /usr/share/man/man3/login_auth.3.gz /usr/share/man/man3/uu_lock.3.gz -> /usr/share/man/man3/uucplock.3.gz /usr/share/man/man3/uu_lock_txfr.3.gz -> = /usr/share/man/man3/uucplock.3.gz /usr/share/man/man3/uu_unlock.3.gz -> /usr/share/man/man3/uucplock.3.gz /usr/share/man/man3/uu_lockerr.3.gz -> /usr/share/man/man3/uucplock.3.gz =3D=3D=3D> lib/compat =3D=3D=3D> lib/compat/compat3x.i386 install -c -o root -g wheel -m 444 libc.so.3 libc_r.so.3 libcurses.so.2 = libdialog.so.3 libedit.so.2 libf2c.so.2 libftpio.so.4 libg++.so.4 = libhistory.so.3 libmytinfo.so.2 libncurses.so.3 libreadline.so.3 = libstdc++.so.2 libtermcap.so.2 libutil.so.2 libwrap.so.2 libxpg4.so.2 = /usr/lib/compat =3D=3D=3D> lib/libalias cd /usr/src/lib/libalias && install -C -o root -g wheel -m 444 alias.h = /usr/include install -c -o root -g wheel -m 444 libalias.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libalias.a /usr/lib install -c -s -o root -g wheel -m 444 libalias.so.4 /usr/lib ln -sf libalias.so.4 /usr/lib/libalias.so =3D=3D=3D> lib/libatm cd /usr/src/lib/libatm && install -C -o root -g wheel -m 444 libatm.h = /usr/include install -c -o root -g wheel -m 444 libatm.a /usr/lib install -c -s -o root -g wheel -m 444 libatm.so.2 /usr/lib ln -sf libatm.so.2 /usr/lib/libatm.so =3D=3D=3D> lib/libbind =3D=3D=3D> lib/libc install -c -o root -g wheel -m 444 creat.2.gz killpg.2.gz sigblock.2.gz = sigpause.2.gz sigsetmask.2.gz sigvec.2.gz i386_get_ioperm.2.gz = i386_get_ldt.2.gz i386_vm86.2.gz _exit.2.gz accept.2.gz access.2.gz = acct.2.gz adjtime.2.gz aio_cancel.2.gz aio_error.2.gz aio_read.2.gz = aio_return.2.gz aio_suspend.2.gz aio_waitcomplete.2.gz aio_write.2.gz = bind.2.gz brk.2.gz chdir.2.gz chflags.2.gz chmod.2.gz chown.2.gz = chroot.2.gz clock_gettime.2.gz close.2.gz connect.2.gz dup.2.gz = execve.2.gz fcntl.2.gz fhopen.2.gz flock.2.gz fork.2.gz fsync.2.gz = getdirentries.2.gz getdtablesize.2.gz getfh.2.gz getfsstat.2.gz = getgid.2.gz getgroups.2.gz getitimer.2.gz getlogin.2.gz getpeername.2.gz = getpgrp.2.gz getpid.2.gz getpriority.2.gz getrlimit.2.gz getrusage.2.gz = getsid.2.gz getsockname.2.gz getsockopt.2.gz gettimeofday.2.gz = getuid.2.gz intro.2.gz ioctl.2.gz issetugid.2.gz jail.2.gz kill.2.gz = kldfind.2.gz kldfirstmod.2.gz kldload.2.gz kldnext.2.gz kldstat.2.gz = kldunload.2.gz ktrace.2.gz kqueue.2.gz link.2.gz listen.2.gz lseek.2.gz = madviinstall -c -o root -g wheel -m 444 btree.3.gz dbopen.3.gz hash.3.gz = mpool.3.gz recno.3.gz gethostid.3.gz setruid.3.gz alarm.3.gz = arc4random.3.gz clock.3.gz confstr.3.gz ctermid.3.gz daemon.3.gz = devname.3.gz directory.3.gz dladdr.3.gz dllockinit.3.gz dlopen.3.gz = err.3.gz exec.3.gz fnmatch.3.gz frexp.3.gz ftok.3.gz fts.3.gz = getbootfile.3.gz getbsize.3.gz getcap.3.gz getcwd.3.gz = getdiskbyname.3.gz getdomainname.3.gz getfsent.3.gz getgrent.3.gz = getgrouplist.3.gz gethostname.3.gz getloadavg.3.gz getmntinfo.3.gz = getnetgrent.3.gz getobjformat.3.gz getpagesize.3.gz getpass.3.gz = getpwent.3.gz getttyent.3.gz getusershell.3.gz getvfsbyname.3.gz = getvfsent.3.gz glob.3.gz initgroups.3.gz isinf.3.gz ldexp.3.gz = lockf.3.gz modf.3.gz msgctl.3.gz msgget.3.gz msgrcv.3.gz msgsnd.3.gz = nice.3.gz nlist.3.gz pause.3.gz popen.3.gz psignal.3.gz pwcache.3.gz = raise.3.gz rand48.3.gz scandir.3.gz setjmp.3.gz setmode.3.gz = siginterrupt.3.gz signal.3.gz sigsetops.3.gz sleep.3.gz stringlist.3.gz = strtofflags.3.gz sysconf.3.gz sysctl.3.gz sysloginstall -c -o root -g = wheel -m 444 euc.4.gz utf2.4.gz /usr/share/man/man4 install -c -o root -g wheel -m 444 tzfile.5.gz publickey.5.gz rpc.5.gz = /usr/share/man/man5 se.2.gz mincore.2.gz minherit.2.gz mkdir.2.gz mkfifo.2.gz mknod.2.gz = mlock.2.gz mmap.2.gz mount.2.gz mprotect.2.gz msync.2.gz munmap.2.gz = nanosleep.2.gz nfssvc.2.gz open.2.gz pathconf.2.gz pipe.2.gz poll.2.gz = profil.2.gz ptrace.2.gz quotactl.2.gz read.2.gz readlink.2.gz = reboot.2.gz recv.2.gz rename.2.gz revoke.2.gz rfork.2.gz rmdir.2.gz = rtprio.2.gz select.2.gz semctl.2.gz semget.2.gz semop.2.gz send.2.gz = sendfile.2.gz setgroups.2.gz setpgid.2.gz setregid.2.gz setresuid.2.gz = setreuid.2.gz setsid.2.gz setuid.2.gz shmat.2.gz shmctl.2.gz shmget.2.gz = shutdown.2.gz sigaction.2.gz sigaltstack.2.gz sigpending.2.gz = sigprocmask.2.gz sigreturn.2.gz sigstack.2.gz sigsuspend.2.gz = socket.2.gz socketpair.2.gz stat.2.gz statfs.2.gz swapon.2.gz = symlink.2.gz sync.2.gz sysarch.2.gz syscall.2.gz truncate.2.gz = umask.2.gz undelete.2.gz unlink.2.gz utimes.2.gz vfork.2.gz wait.2.gz = write.2.gz sched_get_priority_max.2.gz sched_setparam.2.gz = sched_setscheduler.2.gz sched_yield.2.gz /usr/share/man/man2 .3.gz tcgetpgrp.3.gz tcsendbreak.3.gz tcsetattr.3.gz tcsetpgrp.3.gz = time.3.gz times.3.gz timezone.3.gz ttyname.3.gz tzset.3.gz ualarm.3.gz = uname.3.gz unvis.3.gz usleep.3.gz utime.3.gz valloc.3.gz vis.3.gz = moncontrol.3.gz ctype.3.gz isalnum.3.gz isalpha.3.gz isascii.3.gz = isblank.3.gz iscntrl.3.gz isdigit.3.gz isgraph.3.gz islower.3.gz = isprint.3.gz ispunct.3.gz isspace.3.gz isupper.3.gz isxdigit.3.gz = mbrune.3.gz multibyte.3.gz rune.3.gz setlocale.3.gz toascii.3.gz = tolower.3.gz toupper.3.gz addr2ascii.3.gz byteorder.3.gz ethers.3.gz = getaddrinfo.3.gz gethostbyname.3.gz getifaddrs.3.gz getipnodebyname.3.gz = getnameinfo.3.gz getnetent.3.gz getprotoent.3.gz getservent.3.gz = if_indextoname.3.gz inet.3.gz inet6_option_space.3.gz = inet6_rthdr_space.3.gz linkaddr.3.gz rcmd.3.gz resolver.3.gz = catclose.3.gz catgets.3.gz catopen.3.gz regex.3.gz fclose.3.gz = ferror.3.gz fflush.3.gz fgetln.3.gz fgets.3.gz fopen.3.gz fputs.3.gz = fread.3.gz fseek.3.gz funopen.3.gz getc.3.gz mktemp.3.gz printf.3.gz = putc.3.gz remove.3.gz scanf.3.gz sinstall -c -o root -g wheel -m 444 = re_format.7.gz /usr/share/man/man7 etbuf.3.gz stdio.3.gz tmpnam.3.gz ungetc.3.gz abort.3.gz abs.3.gz = alloca.3.gz atexit.3.gz atof.3.gz atoi.3.gz atol.3.gz bsearch.3.gz = div.3.gz exit.3.gz getenv.3.gz getopt.3.gz getsubopt.3.gz labs.3.gz = ldiv.3.gz malloc.3.gz memory.3.gz qsort.3.gz radixsort.3.gz rand.3.gz = random.3.gz realpath.3.gz strtod.3.gz strtol.3.gz strtoul.3.gz = system.3.gz ctime.3.gz strftime.3.gz strptime.3.gz time2posix.3.gz = bcmp.3.gz bcopy.3.gz bstring.3.gz bzero.3.gz ffs.3.gz index.3.gz = memccpy.3.gz memchr.3.gz memcmp.3.gz memcpy.3.gz memmove.3.gz = memset.3.gz rindex.3.gz strcasecmp.3.gz strcat.3.gz strchr.3.gz = strcmp.3.gz strcoll.3.gz strcpy.3.gz strcspn.3.gz strdup.3.gz = strerror.3.gz string.3.gz strlcpy.3.gz strlen.3.gz strmode.3.gz = strpbrk.3.gz strrchr.3.gz strsep.3.gz strspn.3.gz strstr.3.gz = strtok.3.gz strxfrm.3.gz swab.3.gz bindresvport.3.gz des_crypt.3.gz = getrpcent.3.gz getrpcport.3.gz publickey.3.gz rpc.3.gz rpc_secure.3.gz = rtime.3.gz xdr.3.gz /usr/share/man/man3 /usr/share/man/man3/db.3.gz -> /usr/share/man/man3/dbopen.3.gz /usr/share/man/man3/sethostid.3.gz -> /usr/share/man/man3/gethostid.3.gz install -c -o root -g wheel -m 444 libc.a /usr/lib /usr/share/man/man3/setrgid.3.gz -> /usr/share/man/man3/setruid.3.gz ln: /usr/share/man/man3/setruid.3.gz: No such file or directory *** Error code 1 install -c -s -o root -g wheel -m 444 -fschg libc.so.4 /usr/lib ln -sf libc.so.4 /usr/lib/libc.so install -c -o root -g wheel -m 444 libc_pic.a /usr/lib 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error bash-2.03# exit exit =0A= Script done on Mon Jul 17 15:33:22 2000=0A= ------=_NextPart_000_0000_01BFF011.BD555660 Content-Type: application/octet-stream; name="rc.conf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="rc.conf" # This file now contains just the overrides from /etc/defaults/rc.conf=0A= # please make all changes to this file.=0A= =0A= # -- sysinstall generated deltas -- #=0A= keymap=3D"swedish.cp850"=0A= # -- sysinstall generated deltas -- #=0A= #network_interfaces=3D"dc1 dc0 lo0"=0A= ifconfig_dc0=3D"inet 212.73.4.66 netmask 255.255.255.248"=0A= ifconfig_dc1=3D"inet 192.168.100.110 netmask 255.255.255.0"=0A= defaultrouter=3D"212.73.4.65"=0A= hostname=3D"gaiottino.com"=0A= =0A= firewall_enable=3D"YES"=0A= #firewall_type=3D"SIMPLE"=0A= firewall_type=3D"OPEN"=0A= =0A= gateway_enable=3D"YES"=0A= =0A= natd_enable=3D"YES"=0A= natd_interface=3D"dc0"=0A= natd_flags=3D"-s -m -redirect_address 192.168.100.120 212.73.4.69"=0A= natd_flags=3D"-s -m -redirect_port tcp 192.168.100.140:2000-3000 = 2000-3000 -redirect_port udp 192.168.100.140:2000-3000 2000-3000"=0A= natd_flags=3D"-s -m -redirect_port tcp 192.168.100.128:4001-5000 = 4001-5000 -redirect_port udp 192.168.100.128:4001-5000 4001-5000"=0A= =0A= linux_enable=3D"YES"=0A= ------=_NextPart_000_0000_01BFF011.BD555660-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 8:22:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gandalf.defero.net (gandalf.defero.net [212.73.3.251]) by hub.freebsd.org (Postfix) with ESMTP id 115A637BA13 for ; Mon, 17 Jul 2000 08:22:13 -0700 (PDT) (envelope-from johan.huldtgren@rixtelecom.se) Received: from drinklikafix ([212.73.4.66]) by gandalf.defero.net (8.9.3/8.9.3) with SMTP id RAA01763 for ; Mon, 17 Jul 2000 17:22:10 +0200 (MET DST) From: "Johan Huldtgren" To: Subject: 2 different problems Date: Mon, 17 Jul 2000 17:22:00 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0003_01BFF013.842511D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0003_01BFF013.842511D0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I just rebuilt world on my two machines, one successfully(well..) and one failed. Both were CVSuped last night(17/7/00), approx 05:00 CET. Now on first machine I followed the officially sanctioned way. Went through all the steps without encountering any problems(as far as I noticed). After I rebooted, I recompiled my custom kernel. To my slight astonishment though my keyboard has reset itself the american default, although my rc.conf clearly specifies that swedish.cp580 is to be used. I figure I can wait until my kernel has compiled before I look deeper into that. Well 20 minutes and a reboot later the problem remains. I also notice that I have no connection to the net anymore, ifconfig -a gives me that my network cards are down. I can find no other reason for all this except that my rc.conf file isn't being read properly. So I copy past all my values from /etc/rc.conf to /etc/defaults/rc.conf and now everything works fine. The rc.conf file is attached. Now my second machine gets as far as "make installworld" it fails on: ln: /usr/share/man/man3/setruid.3.gz: No such file or directory *** Error code 1 the full output is attached. Now I'm sure both my problems are simple and are the results of a lot of work and no sleep. So be gentle :) Sincerely, Johan Huldtgren ------=_NextPart_000_0003_01BFF013.842511D0 Content-Type: application/octet-stream; name="iw.out" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="iw.out" Script started on Mon Jul 17 15:32:14 2000=0A= bash-2.03# shutdown now=08=08=08=08 = =08=08=08=08=08=08=08=08=08=08=08=08last | = more=08=08=08=08=08=08=08=08=08=08=08shutdown =08=08=08 = now=08=08=08=08=08=08=08=08=08=08=08=08 = =08=08=08=08=08=08=08=08=08=08=08=08make -j5 ins=07tallworld cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj = COMPILER_PATH=3D/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/u= sr/bin = LIBRARY_PATH=3D/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/li= b OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec = PERL5LIB=3D/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 make -f = Makefile.inc1 reinstall -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc; make distrib-dirs mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p = /usr/libdata/perl/5.00503/mach cd /; rm -f /sys; ln -s usr/src/sys sys cd /usr/share/locale; `cat /usr/src/etc/locale.alias`; while [ $# -gt = 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done -------------------------------------------------------------- >>> Installing everything.. -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 install =3D=3D=3D> share/info =3D=3D=3D> include if [ -h /usr/include/cam ]; then rm -f /usr/include/cam; fi if [ -h /usr/include/msdosfs ]; then rm -f /usr/include/msdosfs; fi if [ -h /usr/include/net ]; then rm -f /usr/include/net; fi if [ -h /usr/include/netatalk ]; then rm -f /usr/include/netatalk; fi if [ -h /usr/include/netatm ]; then rm -f /usr/include/netatm; fi if [ -h /usr/include/netgraph ]; then rm -f /usr/include/netgraph; fi if [ -h /usr/include/netinet ]; then rm -f /usr/include/netinet; fi if [ -h /usr/include/netinet6 ]; then rm -f /usr/include/netinet6; fi if [ -h /usr/include/netipx ]; then rm -f /usr/include/netipx; fi if [ -h /usr/include/netkey ]; then rm -f /usr/include/netkey; fi if [ -h /usr/include/netncp ]; then rm -f /usr/include/netncp; fi if [ -h /usr/include/netns ]; then rm -f /usr/include/netns; fi if [ -h /usr/include/nfs ]; then rm -f /usr/include/nfs; fi if [ -h /usr/include/ntfs ]; then rm -f /usr/include/ntfs; fi if [ -h /usr/include/nwfs ]; then rm -f /usr/include/nwfs; fi if [ -h /usr/include/pccard ]; then rm -f /usr/include/pccard; fi if [ -h /usr/include/posix4 ]; then rm -f /usr/include/posix4; fi if [ -h /usr/include/sys ]; then rm -f /usr/include/sys; fi if [ -h /usr/include/vm ]; then rm -f /usr/include/vm; fi if [ -h /usr/include/isofs/cd9660 ]; then rm -f = /usr/include/isofs/cd9660; fi if [ -h /usr/include/ufs/ffs ]; then rm -f /usr/include/ufs/ffs; fi if [ -h /usr/include/ufs/mfs ]; then rm -f /usr/include/ufs/mfs; fi if [ -h /usr/include/ufs/ufs ]; then rm -f /usr/include/ufs/ufs; fi if [ -h /usr/include/dev/ppbus ]; then rm -f /usr/include/dev/ppbus; = fi if [ -h /usr/include/dev/usb ]; then rm -f /usr/include/dev/usb; fi if [ -h /usr/include/machine ]; then rm -f /usr/include/machine; fi rm -rf /usr/include/isofs rm -rf /usr/include/ufs rm -rf /usr/include/dev mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p = /usr/include missing: ./dev (created) missing: ./dev/ppbus (created) missing: ./dev/usb (created) missing: ./isofs (created) missing: ./isofs/cd9660 (created) missing: ./ufs (created) missing: ./ufs/ffs (created) missing: ./ufs/mfs (created) missing: ./ufs/ufs (created) cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h = /usr/include/cam cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = msdosfs/*.h /usr/include/msdosfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 net/*.h = /usr/include/net cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netatalk/*.h /usr/include/netatalk cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netatm/*.h /usr/include/netatm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netgraph/*.h /usr/include/netgraph cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netinet/*.h /usr/include/netinet cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netinet6/*.h /usr/include/netinet6 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netipx/*.h /usr/include/netipx cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netkey/*.h /usr/include/netkey cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netncp/*.h /usr/include/netncp cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = netns/*.h /usr/include/netns cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 nfs/*.h = /usr/include/nfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ntfs/*.h = /usr/include/ntfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 nwfs/*.h = /usr/include/nwfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = pccard/*.h /usr/include/pccard cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = posix4/*.h /usr/include/posix4 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 sys/*.h = /usr/include/sys cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 vm/*.h = /usr/include/vm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = isofs/cd9660/*.h /usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = ufs/ffs/*.h /usr/include/ufs/ffs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = ufs/mfs/*.h /usr/include/ufs/mfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = ufs/ufs/*.h /usr/include/ufs/ufs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = cam/scsi/*.h /usr/include/cam/scsi cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = dev/ppbus/*.h /usr/include/dev/ppbus cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 = dev/usb/*.h /usr/include/dev/usb cd /usr/src/include/../sys/i386/include; install -C -o root -g wheel -m = 444 *.h /usr/include/machine ln -sf ../sys/soundcard.h /usr/include/machine/soundcard.h ln -sf ../sys/joystick.h /usr/include/machine/joystick.h cd /usr/src/include; install -C -o root -g wheel -m 444 a.out.h ar.h = assert.h bitstring.h ctype.h db.h dirent.h disktab.h dlfcn.h elf.h = err.h fnmatch.h fstab.h fts.h glob.h grp.h strhash.h histedit.h = ieeefp.h ifaddrs.h iso646.h limits.h link.h locale.h malloc.h memory.h = mpool.h ndbm.h netdb.h nl_types.h nlist.h objformat.h paths.h = pthread.h pthread_np.h pwd.h ranlib.h regex.h regexp.h resolv.h rune.h = runetype.h setjmp.h sgtty.h signal.h stab.h stddef.h stdio.h stdlib.h = string.h stringlist.h strings.h struct.h sysexits.h tar.h time.h = timers.h ttyent.h unistd.h utime.h utmp.h vis.h /usr/include cd /usr/src/include/arpa; install -C -o root -g wheel -m 444 ftp.h = inet.h nameser.h nameser_compat.h telnet.h tftp.h /usr/include/arpa cd /usr/src/include/protocols; install -C -o root -g wheel -m 444 = dumprestore.h routed.h rwhod.h talkd.h timed.h /usr/include/protocols cd /usr/src/include/rpc; install -C -o root -g wheel -m 444 auth.h = auth_unix.h clnt.h pmap_clnt.h pmap_prot.h pmap_rmt.h rpc.h rpc_com.h = rpc_msg.h svc.h svc_auth.h types.h xdr.h auth_des.h des.h des_crypt.h = /usr/include/rpc install -C -o root -g wheel -m 444 /usr/obj/usr/src/include/osreldate.h = /usr/include ln -sf sys/aio.h /usr/include/aio.h ln -sf sys/errno.h /usr/include/errno.h ln -sf sys/fcntl.h /usr/include/fcntl.h ln -sf sys/inttypes.h /usr/include/inttypes.h ln -sf sys/linker_set.h /usr/include/linker_set.h ln -sf sys/poll.h /usr/include/poll.h ln -sf sys/syslog.h /usr/include/syslog.h ln -sf sys/termios.h /usr/include/termios.h ln -sf sys/ucontext.h /usr/include/ucontext.h ln -sf machine/float.h /usr/include/float.h ln -sf machine/floatingpoint.h /usr/include/floatingpoint.h ln -sf machine/stdarg.h /usr/include/stdarg.h ln -sf machine/varargs.h /usr/include/varargs.h ln -sf posix4/mqueue.h /usr/include/mqueue.h ln -sf posix4/sched.h /usr/include/sched.h ln -sf posix4/semaphore.h /usr/include/semaphore.h =3D=3D=3D> include/rpcsvc install -C -o root -g wheel -m 444 /usr/src/include/rpcsvc/yp_prot.h = /usr/src/include/rpcsvc/ypclnt.h /usr/src/include/rpcsvc/nis_db.h = /usr/src/include/rpcsvc/nis_tags.h /usr/src/include/rpcsvc/nislib.h = /usr/src/include/rpcsvc/bootparam_prot.x = /usr/src/include/rpcsvc/key_prot.x /usr/src/include/rpcsvc/klm_prot.x = /usr/src/include/rpcsvc/mount.x /usr/src/include/rpcsvc/nfs_prot.x = /usr/src/include/rpcsvc/nlm_prot.x /usr/src/include/rpcsvc/rex.x = /usr/src/include/rpcsvc/rnusers.x /usr/src/include/rpcsvc/rquota.x = /usr/src/include/rpcsvc/rstat.x /usr/src/include/rpcsvc/rwall.x = /usr/src/include/rpcsvc/sm_inter.x /usr/src/include/rpcsvc/spray.x = /usr/src/include/rpcsvc/yppasswd.x /usr/src/include/rpcsvc/yp.x = /usr/src/include/rpcsvc/ypxfrd.x /usr/src/include/rpcsvc/ypupdate_prot.x = /usr/src/include/rpcsvc/nis.x /usr/src/include/rpcsvc/nis_cache.x = /usr/src/include/rpcsvc/nis_object.x = /usr/src/include/rpcsvc/nis_callback.x /usr/src/include/rpcsvc/crypt.x = key_prot.h klm_prot.h mount.h nfs_prot.h nlm_prot.h rex.h rnusers.h = rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h = ypupdate_prot.h nis.h nis_cache.h nis_callback.h bootparam_prot.h = crypt.h /usr/include/rpcsvc install -C -o root -g wheel -m 444 key_prot.h /usr/include/rpc =3D=3D=3D> lib =3D=3D=3D> lib/csu/i386-elf install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o install -c -o root -g wheel -m 444 crtbegin.So /usr/lib/crtbeginS.o install -c -o root -g wheel -m 444 crtend.So /usr/lib/crtendS.o =3D=3D=3D> lib/libcom_err cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 = /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include install -c -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 = /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -c -o root -g wheel -m 444 libcom_err.a /usr/lib install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib ln -sf libcom_err.so.2 /usr/lib/libcom_err.so =3D=3D=3D> lib/libcom_err/doc install-info --quiet --defsection=3D"Programming & development tools." = --defentry=3D"* libcom_err: (com_err). A Common Error Description = Library for UNIX." com_err.info /usr/share/info/dir install -c -o root -g wheel -m 444 com_err.info.gz /usr/share/info =3D=3D=3D> lib/libcrypt install -c -o root -g wheel -m 444 crypt.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libscrypt.a /usr/lib install -c -s -o root -g wheel -m 444 -fschg libscrypt.so.2 /usr/lib ln -sf libscrypt.so.2 /usr/lib/libscrypt.so =3D=3D=3D> lib/../secure/lib/libcrypt install -c -o root -g wheel -m 444 crypt.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libdescrypt.a /usr/lib install -c -s -o root -g wheel -m 444 -fschg libdescrypt.so.2 = /usr/lib ln -sf libdescrypt.so.2 /usr/lib/libdescrypt.so =3D=3D=3D> lib/msun install -C -o root -g wheel -m 444 /usr/src/lib/msun/src/math.h = /usr/include install -c -o root -g wheel -m 444 acos.3.gz acosh.3.gz asin.3.gz = asinh.3.gz atan.3.gz atan2.3.gz atanh.3.gz ceil.3.gz cos.3.gz cosh.3.gz = erf.3.gz exp.3.gz fabs.3.gz floor.3.gz fmod.3.gz hypot.3.gz ieee.3.gz = ieee_test.3.gz j0.3.gz lgamma.3.gz math.3.gz rint.3.gz sin.3.gz = sinh.3.gz sqrt.3.gz tan.3.gz tanh.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libm.a /usr/lib /usr/share/man/man3/acosf.3.gz -> /usr/share/man/man3/acos.3.gz install -c -s -o root -g wheel -m 444 libm.so.2 /usr/lib /usr/share/man/man3/acoshf.3.gz -> /usr/share/man/man3/acosh.3.gz /usr/share/man/man3/asinf.3.gz -> /usr/share/man/man3/asin.3.gz /usr/share/man/man3/asinhf.3.gz -> /usr/share/man/man3/asinh.3.gz /usr/share/man/man3/atanf.3.gz -> /usr/share/man/man3/atan.3.gz /usr/share/man/man3/atanhf.3.gz -> /usr/share/man/man3/atanh.3.gz ln -sf libm.so.2 /usr/lib/libm.so /usr/share/man/man3/atan2f.3.gz -> /usr/share/man/man3/atan2.3.gz /usr/share/man/man3/ceilf.3.gz -> /usr/share/man/man3/ceil.3.gz /usr/share/man/man3/cosf.3.gz -> /usr/share/man/man3/cos.3.gz /usr/share/man/man3/coshf.3.gz -> /usr/share/man/man3/cosh.3.gz /usr/share/man/man3/erfc.3.gz -> /usr/share/man/man3/erf.3.gz /usr/share/man/man3/erff.3.gz -> /usr/share/man/man3/erf.3.gz /usr/share/man/man3/erfcf.3.gz -> /usr/share/man/man3/erf.3.gz /usr/share/man/man3/expm1.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log10.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log1p.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/pow.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/expf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp2.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp2f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp10.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/exp10f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/expm1f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/logf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log2.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log2f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/powf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log10f.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/log1pf.3.gz -> /usr/share/man/man3/exp.3.gz /usr/share/man/man3/fabsf.3.gz -> /usr/share/man/man3/fabs.3.gz /usr/share/man/man3/floorf.3.gz -> /usr/share/man/man3/floor.3.gz /usr/share/man/man3/fmodf.3.gz -> /usr/share/man/man3/fmod.3.gz /usr/share/man/man3/cabs.3.gz -> /usr/share/man/man3/hypot.3.gz /usr/share/man/man3/cabsf.3.gz -> /usr/share/man/man3/hypot.3.gz /usr/share/man/man3/hypotf.3.gz -> /usr/share/man/man3/hypot.3.gz /usr/share/man/man3/copysign.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/copysignf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/finite.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/finitef.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/ilogb.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/ilogbf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/nextafter.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/nextafterf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/remainder.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/remainderf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/scalbn.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/scalbnf.3.gz -> /usr/share/man/man3/ieee.3.gz /usr/share/man/man3/logb.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/logbf.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/scalb.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/scalbf.3.gz -> /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/significand.3.gz -> = /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/significandf.3.gz -> = /usr/share/man/man3/ieee_test.3.gz /usr/share/man/man3/j1.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/jn.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y0.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y1.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y1f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/yn.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/j0f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/j1f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/jnf.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/y0f.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/ynf.3.gz -> /usr/share/man/man3/j0.3.gz /usr/share/man/man3/gamma.3.gz -> /usr/share/man/man3/lgamma.3.gz /usr/share/man/man3/lgammaf.3.gz -> /usr/share/man/man3/lgamma.3.gz /usr/share/man/man3/gammaf.3.gz -> /usr/share/man/man3/lgamma.3.gz /usr/share/man/man3/rintf.3.gz -> /usr/share/man/man3/rint.3.gz /usr/share/man/man3/sinf.3.gz -> /usr/share/man/man3/sin.3.gz /usr/share/man/man3/sinhf.3.gz -> /usr/share/man/man3/sinh.3.gz /usr/share/man/man3/cbrt.3.gz -> /usr/share/man/man3/sqrt.3.gz /usr/share/man/man3/cbrtf.3.gz -> /usr/share/man/man3/sqrt.3.gz /usr/share/man/man3/sqrtf.3.gz -> /usr/share/man/man3/sqrt.3.gz /usr/share/man/man3/tanf.3.gz -> /usr/share/man/man3/tan.3.gz /usr/share/man/man3/tanhf.3.gz -> /usr/share/man/man3/tanh.3.gz =3D=3D=3D> lib/libmd cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 md2.h = /usr/include install -c -o root -g wheel -m 444 md2.3.gz md4.3.gz md5.3.gz = ripemd.3.gz sha.3.gz /usr/share/man/man3 cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 md4.h = /usr/include cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 md5.h = /usr/include cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 ripemd.h = /usr/include /usr/share/man/man3/MD2Init.3.gz -> /usr/share/man/man3/md2.3.gz cd /usr/src/lib/libmd && install -C -o root -g wheel -m 444 sha.h = /usr/include /usr/share/man/man3/MD2Update.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2Final.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2End.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2File.3.gz -> /usr/share/man/man3/md2.3.gz install -c -o root -g wheel -m 444 libmd.a /usr/lib /usr/share/man/man3/MD2Data.3.gz -> /usr/share/man/man3/md2.3.gz install -c -s -o root -g wheel -m 444 libmd.so.2 /usr/lib /usr/share/man/man3/MD4Init.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Update.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Final.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4End.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4File.3.gz -> /usr/share/man/man3/md4.3.gz ln -sf libmd.so.2 /usr/lib/libmd.so /usr/share/man/man3/MD4Data.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD5Init.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Update.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Final.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5End.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5File.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Data.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/RIPEMD160_Init.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Update.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Final.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Data.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_End.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_File.3.gz -> = /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/SHA_Init.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Update.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Final.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_End.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_File.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Data.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Init.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Update.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Final.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_End.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_File.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Data.3.gz -> /usr/share/man/man3/sha.3.gz =3D=3D=3D> lib/libncurses install -c -o root -g wheel -m 444 term.7.gz /usr/share/man/man7 install -c -o root -g wheel -m 444 curs_addch.3.gz curs_addchstr.3.gz = curs_addstr.3.gz curs_attr.3.gz curs_beep.3.gz curs_bkgd.3.gz = curs_border.3.gz curs_clear.3.gz curs_color.3.gz curs_delch.3.gz = curs_deleteln.3.gz curs_extend.3.gz curs_getch.3.gz curs_getstr.3.gz = curs_getyx.3.gz curs_inch.3.gz curs_inchstr.3.gz curs_initscr.3.gz = curs_inopts.3.gz curs_insch.3.gz curs_insstr.3.gz curs_instr.3.gz = curs_kernel.3.gz curs_mouse.3.gz curs_move.3.gz curs_outopts.3.gz = curs_overlay.3.gz curs_pad.3.gz curs_print.3.gz curs_printw.3.gz = curs_refresh.3.gz curs_scanw.3.gz curs_scr_dump.3.gz curs_scroll.3.gz = curs_slk.3.gz curs_termattrs.3.gz curs_termcap.3.gz curs_terminfo.3.gz = curs_touch.3.gz curs_util.3.gz curs_window.3.gz define_key.3.gz = dft_fgbg.3.gz keybound.3.gz keyok.3.gz ncurses.3.gz resizeterm.3.gz = wresize.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 term.5.gz terminfo.5.gz = /usr/share/man/man5 install -c -o root -g wheel -m 444 curses.h term.h termcap.h unctrl.h = /usr/include /usr/share/man/man3/curses.3.gz -> /usr/share/man/man3/ncurses.3.gz rm -f /usr/include/ncurses.h /usr/share/man/man3/addch.3.gz -> /usr/share/man/man3/curs_addch.3.gz ln -s curses.h /usr/include/ncurses.h /usr/share/man/man3/echochar.3.gz -> /usr/share/man/man3/curs_addch.3.gz install -c -o root -g wheel -m 444 libncurses.a /usr/lib /usr/share/man/man3/mvaddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/mvwaddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz install -c -s -o root -g wheel -m 444 libncurses.so.5 /usr/lib /usr/share/man/man3/waddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/wechochar.3.gz -> = /usr/share/man/man3/curs_addch.3.gz ln -sf libncurses.so.5 /usr/lib/libncurses.so /usr/share/man/man3/addchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libcurses.a -> libncurses.a /usr/lib/libtermcap.a -> libncurses.a /usr/lib/libtermlib.a -> libncurses.a /usr/share/man/man3/addchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libmytinfo.a -> libncurses.a /usr/lib/libtinfo.a -> libncurses.a /usr/lib/libcurses.so -> libncurses.so /usr/share/man/man3/mvaddchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libtermcap.so -> libncurses.so /usr/lib/libtermlib.so -> libncurses.so /usr/lib/libmytinfo.so -> libncurses.so /usr/share/man/man3/mvaddchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/lib/libtinfo.so -> libncurses.so /usr/share/man/man3/mvwaddchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/mvwaddchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/waddchnstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/waddchstr.3.gz -> = /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/addnstr.3.gz -> /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/addstr.3.gz -> /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvaddnstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvaddstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvwaddnstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/mvwaddstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/waddnstr.3.gz -> = /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/waddstr.3.gz -> /usr/share/man/man3/curs_addstr.3.gz /usr/share/man/man3/attr_get.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attr_off.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attr_on.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attr_set.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attroff.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attron.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/attrset.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/chgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/color_set.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/mvchgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/mvwchgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/standend.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/standout.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_get.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_off.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_on.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattr_set.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattroff.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattron.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wattrset.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wchgat.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wcolor_set.3.gz -> = /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wstandend.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/wstandout.3.gz -> /usr/share/man/man3/curs_attr.3.gz /usr/share/man/man3/beep.3.gz -> /usr/share/man/man3/curs_beep.3.gz /usr/share/man/man3/flash.3.gz -> /usr/share/man/man3/curs_beep.3.gz /usr/share/man/man3/bkgd.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/bkgdset.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/getbkgd.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/wbkgd.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/wbkgdset.3.gz -> /usr/share/man/man3/curs_bkgd.3.gz /usr/share/man/man3/border.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/box.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/hline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/mvhline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/mvwhline.3.gz -> = /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/mvwvline.3.gz -> = /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/vline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/wborder.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/whline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/wvline.3.gz -> /usr/share/man/man3/curs_border.3.gz /usr/share/man/man3/clear.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/clrtobot.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/clrtoeol.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/erase.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/wclear.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/wclrtobot.3.gz -> = /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/wclrtoeol.3.gz -> = /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/werase.3.gz -> /usr/share/man/man3/curs_clear.3.gz /usr/share/man/man3/can_change_color.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/color_content.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/has_colors.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/init_color.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/init_pair.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/pair_content.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/start_color.3.gz -> = /usr/share/man/man3/curs_color.3.gz /usr/share/man/man3/delch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/mvdelch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/mvwdelch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/wdelch.3.gz -> /usr/share/man/man3/curs_delch.3.gz /usr/share/man/man3/deleteln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/insdelln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/insertln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/wdeleteln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/winsdelln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/winsertln.3.gz -> = /usr/share/man/man3/curs_deleteln.3.gz /usr/share/man/man3/curses_version.3.gz -> = /usr/share/man/man3/curs_extend.3.gz /usr/share/man/man3/use_extended_names.3.gz -> = /usr/share/man/man3/curs_extend.3.gz /usr/share/man/man3/getch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/has_key.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/mvgetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/mvwgetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/ungetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/wgetch.3.gz -> /usr/share/man/man3/curs_getch.3.gz /usr/share/man/man3/getnstr.3.gz -> /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/getstr.3.gz -> /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvgetnstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvgetstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvwgetnstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/mvwgetstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/wgetnstr.3.gz -> = /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/wgetstr.3.gz -> /usr/share/man/man3/curs_getstr.3.gz /usr/share/man/man3/getbegyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/getmaxyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/getparyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/getyx.3.gz -> /usr/share/man/man3/curs_getyx.3.gz /usr/share/man/man3/inch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/mvinch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/mvwinch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/winch.3.gz -> /usr/share/man/man3/curs_inch.3.gz /usr/share/man/man3/inchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/inchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvinchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvinchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvwinchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/mvwinchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/winchnstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/winchstr.3.gz -> = /usr/share/man/man3/curs_inchstr.3.gz /usr/share/man/man3/delscreen.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/endwin.3.gz -> /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/initscr.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/isendwin.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/newterm.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/set_term.3.gz -> = /usr/share/man/man3/curs_initscr.3.gz /usr/share/man/man3/cbreak.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/echo.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/halfdelay.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/intrflush.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/keypad.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/meta.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/nocbreak.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/nodelay.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/noecho.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/noqiflush.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/noraw.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/notimeout.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/qiflush.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/raw.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/timeout.3.gz -> /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/typeahead.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/wtimeout.3.gz -> = /usr/share/man/man3/curs_inopts.3.gz /usr/share/man/man3/insch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/mvinsch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/mvwinsch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/winsch.3.gz -> /usr/share/man/man3/curs_insch.3.gz /usr/share/man/man3/insnstr.3.gz -> /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/insstr.3.gz -> /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvinsnstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvinsstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvwinsnstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/mvwinsstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/winsnstr.3.gz -> = /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/winsstr.3.gz -> /usr/share/man/man3/curs_insstr.3.gz /usr/share/man/man3/innstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/instr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvinnstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvinstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvwinnstr.3.gz -> = /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/mvwinstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/winnstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/winstr.3.gz -> /usr/share/man/man3/curs_instr.3.gz /usr/share/man/man3/curs_set.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/def_prog_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/def_shell_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/getsyx.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/napms.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/reset_prog_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/reset_shell_mode.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/resetty.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/ripoffline.3.gz -> = /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/savetty.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/setsyx.3.gz -> /usr/share/man/man3/curs_kernel.3.gz /usr/share/man/man3/getmouse.3.gz -> /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/mouseinterval.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/mousemask.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/ungetmouse.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/wenclose.3.gz -> /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/wmouse_trafo.3.gz -> = /usr/share/man/man3/curs_mouse.3.gz /usr/share/man/man3/move.3.gz -> /usr/share/man/man3/curs_move.3.gz /usr/share/man/man3/wmove.3.gz -> /usr/share/man/man3/curs_move.3.gz /usr/share/man/man3/clearok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/idcok.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/idlok.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/immedok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/leaveok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/nl.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/nonl.3.gz -> /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/scrollok.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/setscrreg.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/wsetscrreg.3.gz -> = /usr/share/man/man3/curs_outopts.3.gz /usr/share/man/man3/copywin.3.gz -> = /usr/share/man/man3/curs_overlay.3.gz /usr/share/man/man3/overlay.3.gz -> = /usr/share/man/man3/curs_overlay.3.gz /usr/share/man/man3/overwrite.3.gz -> = /usr/share/man/man3/curs_overlay.3.gz /usr/share/man/man3/newpad.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/pechochar.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/pnoutrefresh.3.gz -> = /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/prefresh.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/subpad.3.gz -> /usr/share/man/man3/curs_pad.3.gz /usr/share/man/man3/mcprint.3.gz -> /usr/share/man/man3/curs_print.3.gz /usr/share/man/man3/mvprintw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/mvwprintw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/printw.3.gz -> /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/vw_printw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/vwprintw.3.gz -> = /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/wprintw.3.gz -> /usr/share/man/man3/curs_printw.3.gz /usr/share/man/man3/doupdate.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/redrawwin.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/refresh.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/wnoutrefresh.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/wredrawln.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/wrefresh.3.gz -> = /usr/share/man/man3/curs_refresh.3.gz /usr/share/man/man3/mvscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/mvwscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/scanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/vw_scanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/vwscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/wscanw.3.gz -> /usr/share/man/man3/curs_scanw.3.gz /usr/share/man/man3/scr_dump.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scr_init.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scr_restore.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scr_set.3.gz -> = /usr/share/man/man3/curs_scr_dump.3.gz /usr/share/man/man3/scrl.3.gz -> /usr/share/man/man3/curs_scroll.3.gz /usr/share/man/man3/scroll.3.gz -> /usr/share/man/man3/curs_scroll.3.gz /usr/share/man/man3/wscrl.3.gz -> /usr/share/man/man3/curs_scroll.3.gz /usr/share/man/man3/slk_attr.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attr_off.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attr_on.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attr_set.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attroff.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attron.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_attrset.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_clear.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_color.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_init.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_label.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_noutrefresh.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_refresh.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_restore.3.gz -> = /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_set.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/slk_touch.3.gz -> /usr/share/man/man3/curs_slk.3.gz /usr/share/man/man3/baudrate.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/erasechar.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/has_ic.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/has_il.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/killchar.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/longname.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/termattrs.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/termname.3.gz -> = /usr/share/man/man3/curs_termattrs.3.gz /usr/share/man/man3/tgetent.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgetflag.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgetnum.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgetstr.3.gz -> = /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tgoto.3.gz -> /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/tputs.3.gz -> /usr/share/man/man3/curs_termcap.3.gz /usr/share/man/man3/del_curterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/mvcur.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/putp.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/restartterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/set_curterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/setterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/setupterm.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tigetflag.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tigetnum.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tigetstr.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tparm.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/tputs.3.gz -> /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/vidattr.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/vidputs.3.gz -> = /usr/share/man/man3/curs_terminfo.3.gz /usr/share/man/man3/is_linetouched.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/is_wintouched.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/touchline.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/touchwin.3.gz -> /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/untouchwin.3.gz -> = /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/wtouchln.3.gz -> /usr/share/man/man3/curs_touch.3.gz /usr/share/man/man3/delay_output.3.gz -> = /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/filter.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/flushinp.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/getwin.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/keyname.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/putwin.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/unctrl.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/use_env.3.gz -> /usr/share/man/man3/curs_util.3.gz /usr/share/man/man3/delwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/derwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/dupwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/mvderwin.3.gz -> = /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/mvwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/newwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/subwin.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/syncok.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/wcursyncup.3.gz -> = /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/wsyncdown.3.gz -> = /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/wsyncup.3.gz -> /usr/share/man/man3/curs_window.3.gz /usr/share/man/man3/use_default_colors.3.gz -> = /usr/share/man/man3/dft_fgbg.3.gz cd /usr/src/lib/libncurses/../../contrib/ncurses/misc ; install -c -o = root -g wheel -m 444 ncurses-intro.html /usr/share/doc/ncurses cd /usr/src/lib/libncurses/../../contrib/ncurses/misc ; install -c -o = root -g wheel -m 444 hackguide.html /usr/share/doc/ncurses =3D=3D=3D> lib/libradius cd /usr/src/lib/libradius && install -C -o root -g wheel -m 444 = radlib.h /usr/include install -c -o root -g wheel -m 444 libradius.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 radius.conf.5.gz /usr/share/man/man5 install -c -o root -g wheel -m 444 libradius.a /usr/lib install -c -s -o root -g wheel -m 444 libradius.so.1 /usr/lib ln -sf libradius.so.1 /usr/lib/libradius.so =3D=3D=3D> lib/libskey cd /usr/src/lib/libskey && install -C -o root -g wheel -m 444 skey.h = /usr/include install -c -o root -g wheel -m 444 skey.1.gz /usr/share/man/man1 install -c -o root -g wheel -m 444 skey.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 skey.access.5.gz /usr/share/man/man5 install -c -o root -g wheel -m 444 libskey.a /usr/lib install -c -s -o root -g wheel -m 444 libskey.so.2 /usr/lib /usr/share/man/man3/skeylookup.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skeyverify.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skeychallenge.3.gz -> /usr/share/man/man3/skey.3.gz ln -sf libskey.so.2 /usr/lib/libskey.so /usr/share/man/man3/skeyinfo.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skeyaccess.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skey_getpass.3.gz -> /usr/share/man/man3/skey.3.gz /usr/share/man/man3/skey_crypt.3.gz -> /usr/share/man/man3/skey.3.gz =3D=3D=3D> lib/libtacplus cd /usr/src/lib/libtacplus && install -C -o root -g wheel -m 444 = taclib.h /usr/include install -c -o root -g wheel -m 444 libtacplus.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 tacplus.conf.5.gz = /usr/share/man/man5 install -c -o root -g wheel -m 444 libtacplus.a /usr/lib install -c -s -o root -g wheel -m 444 libtacplus.so.1 /usr/lib ln -sf libtacplus.so.1 /usr/lib/libtacplus.so =3D=3D=3D> lib/libutil cd /usr/src/lib/libutil && install -C -o root -g wheel -m 444 = libutil.h /usr/include install -c -o root -g wheel -m 444 login.3.gz login_auth.3.gz = login_tty.3.gz logout.3.gz logwtmp.3.gz pty.3.gz setproctitle.3.gz = login_cap.3.gz login_class.3.gz login_times.3.gz login_ok.3.gz = _secure_path.3.gz uucplock.3.gz property.3.gz auth.3.gz = realhostname.3.gz realhostname_sa.3.gz trimdomain.3.gz fparseln.3.gz = /usr/share/man/man3 cd /usr/src/lib/libutil && install -C -o root -g wheel -m 444 = login_cap.h /usr/include install -c -o root -g wheel -m 444 login.conf.5.gz auth.conf.5.gz = /usr/share/man/man5 /usr/share/man/man3/properties_read.3.gz -> = /usr/share/man/man3/property.3.gz install -c -o root -g wheel -m 444 libutil.a /usr/lib /usr/share/man/man3/properties_free.3.gz -> = /usr/share/man/man3/property.3.gz install -c -s -o root -g wheel -m 444 libutil.so.3 /usr/lib /usr/share/man/man3/property_find.3.gz -> = /usr/share/man/man3/property.3.gz ln -sf libutil.so.3 /usr/lib/libutil.so /usr/share/man/man3/auth_getval.3.gz -> /usr/share/man/man3/auth.3.gz /usr/share/man/man3/openpty.3.gz -> /usr/share/man/man3/pty.3.gz /usr/share/man/man3/forkpty.3.gz -> /usr/share/man/man3/pty.3.gz /usr/share/man/man3/login_getclassbyname.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_close.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getclass.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getuserclass.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapstr.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcaplist.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getstyle.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcaptime.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapnum.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapsize.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getcapbool.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getpath.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/login_getpwclass.3.gz -> = /usr/share/man/man3/login_cap.3.gz /usr/share/man/man3/setusercontext.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/setclasscontext.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/setclassenvironment.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/setclassresources.3.gz -> = /usr/share/man/man3/login_class.3.gz /usr/share/man/man3/parse_lt.3.gz -> = /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_ltm.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_lt.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_ltms.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/in_lts.3.gz -> /usr/share/man/man3/login_times.3.gz /usr/share/man/man3/auth_ttyok.3.gz -> /usr/share/man/man3/login_ok.3.gz /usr/share/man/man3/auth_hostok.3.gz -> = /usr/share/man/man3/login_ok.3.gz /usr/share/man/man3/auth_timeok.3.gz -> = /usr/share/man/man3/login_ok.3.gz /usr/share/man/man3/auth_checknologin.3.gz -> = /usr/share/man/man3/login_auth.3.gz /usr/share/man/man3/auth_cat.3.gz -> /usr/share/man/man3/login_auth.3.gz /usr/share/man/man3/uu_lock.3.gz -> /usr/share/man/man3/uucplock.3.gz /usr/share/man/man3/uu_lock_txfr.3.gz -> = /usr/share/man/man3/uucplock.3.gz /usr/share/man/man3/uu_unlock.3.gz -> /usr/share/man/man3/uucplock.3.gz /usr/share/man/man3/uu_lockerr.3.gz -> /usr/share/man/man3/uucplock.3.gz =3D=3D=3D> lib/compat =3D=3D=3D> lib/compat/compat3x.i386 install -c -o root -g wheel -m 444 libc.so.3 libc_r.so.3 libcurses.so.2 = libdialog.so.3 libedit.so.2 libf2c.so.2 libftpio.so.4 libg++.so.4 = libhistory.so.3 libmytinfo.so.2 libncurses.so.3 libreadline.so.3 = libstdc++.so.2 libtermcap.so.2 libutil.so.2 libwrap.so.2 libxpg4.so.2 = /usr/lib/compat =3D=3D=3D> lib/libalias cd /usr/src/lib/libalias && install -C -o root -g wheel -m 444 alias.h = /usr/include install -c -o root -g wheel -m 444 libalias.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 libalias.a /usr/lib install -c -s -o root -g wheel -m 444 libalias.so.4 /usr/lib ln -sf libalias.so.4 /usr/lib/libalias.so =3D=3D=3D> lib/libatm cd /usr/src/lib/libatm && install -C -o root -g wheel -m 444 libatm.h = /usr/include install -c -o root -g wheel -m 444 libatm.a /usr/lib install -c -s -o root -g wheel -m 444 libatm.so.2 /usr/lib ln -sf libatm.so.2 /usr/lib/libatm.so =3D=3D=3D> lib/libbind =3D=3D=3D> lib/libc install -c -o root -g wheel -m 444 creat.2.gz killpg.2.gz sigblock.2.gz = sigpause.2.gz sigsetmask.2.gz sigvec.2.gz i386_get_ioperm.2.gz = i386_get_ldt.2.gz i386_vm86.2.gz _exit.2.gz accept.2.gz access.2.gz = acct.2.gz adjtime.2.gz aio_cancel.2.gz aio_error.2.gz aio_read.2.gz = aio_return.2.gz aio_suspend.2.gz aio_waitcomplete.2.gz aio_write.2.gz = bind.2.gz brk.2.gz chdir.2.gz chflags.2.gz chmod.2.gz chown.2.gz = chroot.2.gz clock_gettime.2.gz close.2.gz connect.2.gz dup.2.gz = execve.2.gz fcntl.2.gz fhopen.2.gz flock.2.gz fork.2.gz fsync.2.gz = getdirentries.2.gz getdtablesize.2.gz getfh.2.gz getfsstat.2.gz = getgid.2.gz getgroups.2.gz getitimer.2.gz getlogin.2.gz getpeername.2.gz = getpgrp.2.gz getpid.2.gz getpriority.2.gz getrlimit.2.gz getrusage.2.gz = getsid.2.gz getsockname.2.gz getsockopt.2.gz gettimeofday.2.gz = getuid.2.gz intro.2.gz ioctl.2.gz issetugid.2.gz jail.2.gz kill.2.gz = kldfind.2.gz kldfirstmod.2.gz kldload.2.gz kldnext.2.gz kldstat.2.gz = kldunload.2.gz ktrace.2.gz kqueue.2.gz link.2.gz listen.2.gz lseek.2.gz = madviinstall -c -o root -g wheel -m 444 btree.3.gz dbopen.3.gz hash.3.gz = mpool.3.gz recno.3.gz gethostid.3.gz setruid.3.gz alarm.3.gz = arc4random.3.gz clock.3.gz confstr.3.gz ctermid.3.gz daemon.3.gz = devname.3.gz directory.3.gz dladdr.3.gz dllockinit.3.gz dlopen.3.gz = err.3.gz exec.3.gz fnmatch.3.gz frexp.3.gz ftok.3.gz fts.3.gz = getbootfile.3.gz getbsize.3.gz getcap.3.gz getcwd.3.gz = getdiskbyname.3.gz getdomainname.3.gz getfsent.3.gz getgrent.3.gz = getgrouplist.3.gz gethostname.3.gz getloadavg.3.gz getmntinfo.3.gz = getnetgrent.3.gz getobjformat.3.gz getpagesize.3.gz getpass.3.gz = getpwent.3.gz getttyent.3.gz getusershell.3.gz getvfsbyname.3.gz = getvfsent.3.gz glob.3.gz initgroups.3.gz isinf.3.gz ldexp.3.gz = lockf.3.gz modf.3.gz msgctl.3.gz msgget.3.gz msgrcv.3.gz msgsnd.3.gz = nice.3.gz nlist.3.gz pause.3.gz popen.3.gz psignal.3.gz pwcache.3.gz = raise.3.gz rand48.3.gz scandir.3.gz setjmp.3.gz setmode.3.gz = siginterrupt.3.gz signal.3.gz sigsetops.3.gz sleep.3.gz stringlist.3.gz = strtofflags.3.gz sysconf.3.gz sysctl.3.gz sysloginstall -c -o root -g = wheel -m 444 euc.4.gz utf2.4.gz /usr/share/man/man4 install -c -o root -g wheel -m 444 tzfile.5.gz publickey.5.gz rpc.5.gz = /usr/share/man/man5 se.2.gz mincore.2.gz minherit.2.gz mkdir.2.gz mkfifo.2.gz mknod.2.gz = mlock.2.gz mmap.2.gz mount.2.gz mprotect.2.gz msync.2.gz munmap.2.gz = nanosleep.2.gz nfssvc.2.gz open.2.gz pathconf.2.gz pipe.2.gz poll.2.gz = profil.2.gz ptrace.2.gz quotactl.2.gz read.2.gz readlink.2.gz = reboot.2.gz recv.2.gz rename.2.gz revoke.2.gz rfork.2.gz rmdir.2.gz = rtprio.2.gz select.2.gz semctl.2.gz semget.2.gz semop.2.gz send.2.gz = sendfile.2.gz setgroups.2.gz setpgid.2.gz setregid.2.gz setresuid.2.gz = setreuid.2.gz setsid.2.gz setuid.2.gz shmat.2.gz shmctl.2.gz shmget.2.gz = shutdown.2.gz sigaction.2.gz sigaltstack.2.gz sigpending.2.gz = sigprocmask.2.gz sigreturn.2.gz sigstack.2.gz sigsuspend.2.gz = socket.2.gz socketpair.2.gz stat.2.gz statfs.2.gz swapon.2.gz = symlink.2.gz sync.2.gz sysarch.2.gz syscall.2.gz truncate.2.gz = umask.2.gz undelete.2.gz unlink.2.gz utimes.2.gz vfork.2.gz wait.2.gz = write.2.gz sched_get_priority_max.2.gz sched_setparam.2.gz = sched_setscheduler.2.gz sched_yield.2.gz /usr/share/man/man2 .3.gz tcgetpgrp.3.gz tcsendbreak.3.gz tcsetattr.3.gz tcsetpgrp.3.gz = time.3.gz times.3.gz timezone.3.gz ttyname.3.gz tzset.3.gz ualarm.3.gz = uname.3.gz unvis.3.gz usleep.3.gz utime.3.gz valloc.3.gz vis.3.gz = moncontrol.3.gz ctype.3.gz isalnum.3.gz isalpha.3.gz isascii.3.gz = isblank.3.gz iscntrl.3.gz isdigit.3.gz isgraph.3.gz islower.3.gz = isprint.3.gz ispunct.3.gz isspace.3.gz isupper.3.gz isxdigit.3.gz = mbrune.3.gz multibyte.3.gz rune.3.gz setlocale.3.gz toascii.3.gz = tolower.3.gz toupper.3.gz addr2ascii.3.gz byteorder.3.gz ethers.3.gz = getaddrinfo.3.gz gethostbyname.3.gz getifaddrs.3.gz getipnodebyname.3.gz = getnameinfo.3.gz getnetent.3.gz getprotoent.3.gz getservent.3.gz = if_indextoname.3.gz inet.3.gz inet6_option_space.3.gz = inet6_rthdr_space.3.gz linkaddr.3.gz rcmd.3.gz resolver.3.gz = catclose.3.gz catgets.3.gz catopen.3.gz regex.3.gz fclose.3.gz = ferror.3.gz fflush.3.gz fgetln.3.gz fgets.3.gz fopen.3.gz fputs.3.gz = fread.3.gz fseek.3.gz funopen.3.gz getc.3.gz mktemp.3.gz printf.3.gz = putc.3.gz remove.3.gz scanf.3.gz sinstall -c -o root -g wheel -m 444 = re_format.7.gz /usr/share/man/man7 etbuf.3.gz stdio.3.gz tmpnam.3.gz ungetc.3.gz abort.3.gz abs.3.gz = alloca.3.gz atexit.3.gz atof.3.gz atoi.3.gz atol.3.gz bsearch.3.gz = div.3.gz exit.3.gz getenv.3.gz getopt.3.gz getsubopt.3.gz labs.3.gz = ldiv.3.gz malloc.3.gz memory.3.gz qsort.3.gz radixsort.3.gz rand.3.gz = random.3.gz realpath.3.gz strtod.3.gz strtol.3.gz strtoul.3.gz = system.3.gz ctime.3.gz strftime.3.gz strptime.3.gz time2posix.3.gz = bcmp.3.gz bcopy.3.gz bstring.3.gz bzero.3.gz ffs.3.gz index.3.gz = memccpy.3.gz memchr.3.gz memcmp.3.gz memcpy.3.gz memmove.3.gz = memset.3.gz rindex.3.gz strcasecmp.3.gz strcat.3.gz strchr.3.gz = strcmp.3.gz strcoll.3.gz strcpy.3.gz strcspn.3.gz strdup.3.gz = strerror.3.gz string.3.gz strlcpy.3.gz strlen.3.gz strmode.3.gz = strpbrk.3.gz strrchr.3.gz strsep.3.gz strspn.3.gz strstr.3.gz = strtok.3.gz strxfrm.3.gz swab.3.gz bindresvport.3.gz des_crypt.3.gz = getrpcent.3.gz getrpcport.3.gz publickey.3.gz rpc.3.gz rpc_secure.3.gz = rtime.3.gz xdr.3.gz /usr/share/man/man3 /usr/share/man/man3/db.3.gz -> /usr/share/man/man3/dbopen.3.gz /usr/share/man/man3/sethostid.3.gz -> /usr/share/man/man3/gethostid.3.gz install -c -o root -g wheel -m 444 libc.a /usr/lib /usr/share/man/man3/setrgid.3.gz -> /usr/share/man/man3/setruid.3.gz ln: /usr/share/man/man3/setruid.3.gz: No such file or directory *** Error code 1 install -c -s -o root -g wheel -m 444 -fschg libc.so.4 /usr/lib ln -sf libc.so.4 /usr/lib/libc.so install -c -o root -g wheel -m 444 libc_pic.a /usr/lib 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error bash-2.03# exit exit =0A= Script done on Mon Jul 17 15:33:22 2000=0A= ------=_NextPart_000_0003_01BFF013.842511D0 Content-Type: application/octet-stream; name="rc.conf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="rc.conf" # This file now contains just the overrides from /etc/defaults/rc.conf=0A= # please make all changes to this file.=0A= =0A= # -- sysinstall generated deltas -- #=0A= keymap=3D"swedish.cp850"=0A= # -- sysinstall generated deltas -- #=0A= #network_interfaces=3D"dc1 dc0 lo0"=0A= ifconfig_dc0=3D"inet 212.73.4.66 netmask 255.255.255.248"=0A= ifconfig_dc1=3D"inet 192.168.100.110 netmask 255.255.255.0"=0A= defaultrouter=3D"212.73.4.65"=0A= hostname=3D"gaiottino.com"=0A= =0A= firewall_enable=3D"YES"=0A= #firewall_type=3D"SIMPLE"=0A= firewall_type=3D"OPEN"=0A= =0A= gateway_enable=3D"YES"=0A= =0A= natd_enable=3D"YES"=0A= natd_interface=3D"dc0"=0A= natd_flags=3D"-s -m -redirect_address 192.168.100.120 212.73.4.69"=0A= natd_flags=3D"-s -m -redirect_port tcp 192.168.100.140:2000-3000 = 2000-3000 -redirect_port udp 192.168.100.140:2000-3000 2000-3000"=0A= natd_flags=3D"-s -m -redirect_port tcp 192.168.100.128:4001-5000 = 4001-5000 -redirect_port udp 192.168.100.128:4001-5000 4001-5000"=0A= =0A= linux_enable=3D"YES"=0A= ------=_NextPart_000_0003_01BFF013.842511D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 8:30: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.rdc1.sfba.home.com (mail1.rdc1.sfba.home.com [24.0.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 0961B37BBEC for ; Mon, 17 Jul 2000 08:29:36 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail1.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000717152935.UZWY28364.mail1.rdc1.sfba.home.com@beastie.localdomain>; Mon, 17 Jul 2000 08:29:35 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id IAA30056; Mon, 17 Jul 2000 08:40:33 -0700 (PDT) (envelope-from brian) Date: Mon, 17 Jul 2000 08:40:33 -0700 From: "Brian O'Shea" To: Johan Huldtgren Cc: stable@FreeBSD.ORG Subject: Re: 2 different problems Message-ID: <20000717084033.X351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Johan Huldtgren , stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Johan Huldtgren on Mon, Jul 17, 2000 at 05:09:17PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan, Did you run mergemaster after the install completed (and after you backed up /etc)? It looks like the way that /etc/defaults/rc.conf sources /etc/rc.conf might have changed. Just a thought (I havn't cvsupped my system very recently). Cheers, -brian On Mon, Jul 17, 2000 at 05:09:17PM +0200, Johan Huldtgren wrote: > I just rebuilt world on my two machines, one successfully(well..) and one > failed. Both were CVSuped last night(17/7/00), approx 05:00 CET. > > Now on first machine I followed the officially sanctioned way. Went through > all the steps without encountering any problems(as far as I noticed). After > I rebooted, I recompiled my custom kernel. To my slight astonishment though > my keyboard has reset itself the american default, although my rc.conf > clearly specifies that swedish.cp580 is to be used. I figure I can wait > until my kernel has compiled before I look deeper into that. Well 20 minutes > and a reboot later the problem remains. I also notice that I have no > connection to the net anymore, ifconfig -a gives me that my network cards > are down. I can find no other reason for all this except that my rc.conf > file isn't being read properly. So I copy past all my values from > /etc/rc.conf to /etc/defaults/rc.conf and now everything works fine. The > rc.conf file is attached. > > Now my second machine gets as far as "make installworld" it fails on: > > ln: /usr/share/man/man3/setruid.3.gz: No such file or directory > *** Error code 1 > > the full output is attached. > > Now I'm sure both my problems are simple and are the results of a lot of > work and no sleep. So be gentle :) > > Sincerely, > > Johan Huldtgren -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 9:14:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsd.unixvillain.com (sprawly.sprawlnet.com [208.224.169.130]) by hub.freebsd.org (Postfix) with ESMTP id 773B437B523 for ; Mon, 17 Jul 2000 09:14:00 -0700 (PDT) (envelope-from richard@sprawlnet.com) Received: from jedi (jedi.sprawlnet.com [208.224.169.134]) by bsd.unixvillain.com (8.9.3/8.9.2) with SMTP id AAA17544 for ; Tue, 18 Jul 2000 00:18:40 -0400 (EDT) (envelope-from richard@sprawlnet.com) Message-ID: <002c01bff008$fc0a95e0$86a9e0d0@devnull.sprawlnet.com> From: "Rich" To: "freebsd stable" Subject: Maybe someone here has a solution? Date: Mon, 17 Jul 2000 12:06:36 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0029_01BFEFE7.74C366F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0029_01BFEFE7.74C366F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Most of our machines in this office run FreeBSD-3.x or 4.x and I need to = write an application that selects certain info from an Informix = database and displays the results in HTML. The Informix DB is on a SCO = OpenServer 5.x boxen ...=20 I can very easily use APACHE/Mod_Perl + ESQL/C to write this application = ... but I can't find any info on using esql/c on a freebsd box or even = something similar that I can use. Anyone have any idea's or suggestions for th ebest solution? -thanks Rich ------=_NextPart_000_0029_01BFEFE7.74C366F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Most of our machines in this office run = FreeBSD-3.x=20 or 4.x and I need to write an application that selects certain info = from =20 an Informix database and displays the results in HTML. The Informix DB = is on a=20 SCO OpenServer 5.x boxen ...
 
I can very easily use APACHE/Mod_Perl + = ESQL/C to=20 write this application ... but I can't find any info on using esql/c on = a=20 freebsd box or even something similar that I can use.
 
Anyone have any idea's or suggestions = for th ebest=20 solution?
 
-thanks
Rich
 
 
 
 
------=_NextPart_000_0029_01BFEFE7.74C366F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 9:25: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9FA8937B589 for ; Mon, 17 Jul 2000 09:24:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA80590; Mon, 17 Jul 2000 10:24:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA61568; Mon, 17 Jul 2000 10:24:23 -0600 (MDT) Message-Id: <200007171624.KAA61568@harmony.village.org> To: Bob Johnson Subject: Re: Can't boot if PCCARD drive listed in fstab Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 Jul 2000 12:16:15 EDT." <3.0.6.32.20000716121615.00a2a320@rio.atlantic.net> References: <3.0.6.32.20000716121615.00a2a320@rio.atlantic.net> Date: Mon, 17 Jul 2000 10:24:23 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3.0.6.32.20000716121615.00a2a320@rio.atlantic.net> Bob Johnson writes: : I installed the 20000715 STABLE snapshot in my old 486 laptop : and discovered that if there is a PCMCIA hard drive listed in : /etc/fstab the system won't boot. pccard attached devices aren't supported in fstab at this time. Please put pass "0" into the field in the fstab and mount it after pccardd has started. If you are brave, you can copy pccardd to /sbin and start it before fsck runs. We're working on that long term. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 9:40:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 8CF5537BBBE for ; Mon, 17 Jul 2000 09:40:30 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id SAA13433; Mon, 17 Jul 2000 18:40:16 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id SAA19631; Mon, 17 Jul 2000 18:37:12 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C125691F.005B8EEA ; Mon, 17 Jul 2000 18:40:03 +0200 X-Lotus-FromDomain: ALCATEL To: "Michael I. Vasilenko" Cc: stable@freebsd.org Message-ID: Date: Mon, 17 Jul 2000 18:39:54 +0200 Subject: Re: lost mouse when switching back to X Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the tip TfH "Michael I. Vasilenko" on 17/07/2000 14:36:38 To: Thierry HERBELOT/FR/ALCATEL@ALCATEL cc: Subject: Re: lost mouse when switching back to X On Mon, 17 Jul 2000 Thierry.Herbelot@alcatel.fr wrote: > >From the associated ports tree, I've compiled and installed XFree86 > 4.01 and KDE 1.1.2 > > When I switch from X-Windows to the text console and then back to > X-windows (Ctrl-Alt-F1, then Alt-F9), the mouse pointer is fixed on the > screen (When I move the "physical" mouse, the pointer stays at the same > place on the X screen). > > This happens with both KDE and twm as window managers. The same here. Quick & dirty fix - copy /usr/X11/lib/modules/input/mouse_drv.o from the machine with XFree86 4.0 - I can send this one to you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 9:52:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6]) by hub.freebsd.org (Postfix) with ESMTP id D834137B558; Mon, 17 Jul 2000 09:51:54 -0700 (PDT) (envelope-from arnee@linuxmail.org) Received: from linuxmail.org (mg131-167.ricochet.net [204.179.131.167]) by rgate.ricochet.net (8.9.3/8.9.3) with ESMTP id LAA10141; Mon, 17 Jul 2000 11:48:35 -0500 (CDT) Message-ID: <39733951.27C3715@linuxmail.org> Date: Mon, 17 Jul 2000 09:50:25 -0700 From: arnold X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.11-1 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Jacques A. Vidrine" Cc: freebsd-stable@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: buildworld kerberos5 broken? References: <397103DB.2AB0CE48@linuxmail.org> <20000716130852.A53314@hamlet.nectar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jacques A. Vidrine" wrote: > IIRC, There is a dependency problem ... you cannot MAKE_KERBEROS5 > without MAKE_KERBEROS4. You may even need to have Kerberos IV > _installed_ before you attempt to MAKE_KERBEROS5-- I'm not sure. > > This is on my long to-do list to look into, and it is probably on > Mark's, too. > -- > Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org hmmm, that's odd... if i can remember i had build my last stable (right after the release date) and everything compiled fine with kerberos5. even -current (before 4.0release), i believe i was compiling kerberos5 with no problems... then again i could be wrong :-(. but, you're right something is going on here, for the past week... until now over the weekend i have been trying to compile it and no luck. it looks to me like krb.h is not in the -I path when compiling kerberos5. but i still don't understand how i was able to build it before without kerberosIV dependency... hmmm! thanks for the info! arnold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 10: 8:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id C90D137BAA4 for ; Mon, 17 Jul 2000 10:08:41 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6HH8Sb72634; Mon, 17 Jul 2000 10:08:28 -0700 (PDT) Date: Mon, 17 Jul 2000 10:08:27 -0700 (PDT) From: Doug White To: Carl Makin Cc: stable@FreeBSD.ORG Subject: Re: Removing Path prefixing for Linux binaries. (ie to run ADSM) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Carl Makin wrote: > I've been trying to work out a clean way to label linux binaries that I > don't want the path prepending done to. This prepending makes the linux > ADSM client unusable (for example). > > I know someone has gone so far as removing the whole /compat/linux path > from the linux emulator (ABI interface), and while that doesn't look hard > I've been trying to think of a better way. That was me. I still have those patches floating around somewhere, or at minumum they should be in the PR database. > The only thing I can think of so far is to use brandelf to either brand it > with a different type (say linuxnp) that has the path removed, (Can I just > put that extra type in linux_sysvec.c?) or add some other header > information. > > Does anyone have any better ideas or is interested in working on this? -emulation batted this around for a while but I never saw anything come of that discussion. It ends up behing hackish or hackish to flag individual binaries for special treatment. The -emulation group really wanted to set separate translations paths on a binary-by-binary basis, I think. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 10:19:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id E6E4437B5A7; Mon, 17 Jul 2000 10:19:37 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 1ADD7646; Mon, 17 Jul 2000 10:19:34 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id KAA01814; Mon, 17 Jul 2000 10:19:33 -0700 (PDT) Message-ID: <39734025.4AF2C903@cup.hp.com> Date: Mon, 17 Jul 2000 10:19:33 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Carl Makin Cc: stable@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: Removing Path prefixing for Linux binaries. (ie to run ADSM) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc'd to emulation as well] Carl Makin wrote: > I've been trying to work out a clean way to label linux binaries that I > don't want the path prepending done to. This prepending makes the linux > ADSM client unusable (for example). > > Does anyone have any better ideas or is interested in working on this? The prepending is not bad. What is bad is that Linux binaries don't get to see the complete filesystem. I've been thinking about a unionfs type solution, but haven't been able to spend more time on it. Disabling the path prepending for Linux binaries is not a good solution in general, because you would probably end up trying to link FreeBSD libraries that happen to have the same name as the Linux libraries you're actually trying to link in (assuming dynamic linking in this case). You don't have that problem for static linked binaries. No matter how you linked your binary, you also have possible configuration file conflicts... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 10:22:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iencentral.com (mail.iencentral.com [204.85.34.194]) by hub.freebsd.org (Postfix) with ESMTP id 2E99D37BAAD for ; Mon, 17 Jul 2000 10:22:52 -0700 (PDT) (envelope-from dbrooks@iencentral.com) Received: from ouch (firewall.iencentral.com [204.85.34.195]) by iencentral.com (8.9.3/8.9.3) with SMTP id NAA45441; Mon, 17 Jul 2000 13:22:48 -0400 (EDT) (envelope-from dbrooks@iencentral.com) Message-ID: <01c701bff013$5d92a640$0405010a@office.iencentral.com> From: "David E. Brooks Jr" To: "Rich" , "freebsd stable" References: <002c01bff008$fc0a95e0$86a9e0d0@devnull.sprawlnet.com> Subject: Re: Maybe someone here has a solution? Date: Mon, 17 Jul 2000 13:20:55 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C4_01BFEFF1.D6470A80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01C4_01BFEFF1.D6470A80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Alas, Informix doesn't have a native FreeBSD port of their esql/c = product. However, we recently went through a database selection process = and our Informix sales guys managed to get approval for the port (just = esql/c, not the entire database) to be done. We ultimately went with = another database so I don't know the status of the port, but if they = went ahead it would be nearing completion. (And if they didn't, I don't = imagine it would be too difficult to get the project going again). I = suggest contacting your friendly Informix sales rep and see what they = can do for you. -- Dave ----- Original Message -----=20 From: Rich=20 To: freebsd stable=20 Sent: Monday, July 17, 2000 12:06 PM Subject: Maybe someone here has a solution? Most of our machines in this office run FreeBSD-3.x or 4.x and I need = to write an application that selects certain info from an Informix = database and displays the results in HTML. The Informix DB is on a SCO = OpenServer 5.x boxen ...=20 I can very easily use APACHE/Mod_Perl + ESQL/C to write this = application ... but I can't find any info on using esql/c on a freebsd = box or even something similar that I can use. Anyone have any idea's or suggestions for th ebest solution? -thanks Rich ------=_NextPart_000_01C4_01BFEFF1.D6470A80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Alas, Informix doesn't have a native = FreeBSD port=20 of their esql/c product.  However, we recently went through a = database=20 selection process and our Informix sales guys managed to get approval = for the=20 port (just esql/c, not the entire database) to be done.  We = ultimately went=20 with another database so I don't know the status of the port, but if = they went=20 ahead it would be nearing completion.  (And if they didn't, I don't = imagine=20 it would be too difficult to get the project going again).  I = suggest=20 contacting your friendly Informix sales rep and see what they can do for = you.
 
-- Dave
----- Original Message -----
From:=20 Rich=20
To: freebsd stable
Sent: Monday, July 17, 2000 = 12:06=20 PM
Subject: Maybe someone here has = a=20 solution?

Most of our machines in this office = run=20 FreeBSD-3.x or 4.x and I need to write an application that selects = certain=20 info from  an Informix database and displays the results in HTML. = The=20 Informix DB is on a SCO OpenServer 5.x boxen ...
 
I can very easily use APACHE/Mod_Perl = + ESQL/C to=20 write this application ... but I can't find any info on using esql/c = on a=20 freebsd box or even something similar that I can use.
 
Anyone have any idea's or suggestions = for th=20 ebest solution?
 
-thanks
Rich
 
------=_NextPart_000_01C4_01BFEFF1.D6470A80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 10:40:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id DFB4037B5EB for ; Mon, 17 Jul 2000 10:40:17 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from NOMAD (dsl1-160.dynacom.net [206.159.132.160]) by 2711 (Build 101 8.9.3/NT-8.9.3) with SMTP id NAA04482; Sun, 16 Jul 2000 13:01:19 -0700 Message-ID: <006301bfef60$8763d970$0100fea9@NOMAD> Reply-To: "Kent Stewart" From: "Kent Stewart" To: , References: Subject: Re: Latest RELENG_4. Date: Sun, 16 Jul 2000 13:00:45 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG RELENG_4 is in the transition to 4.1 and I wouldn't think so at this point. Kent ----- Original Message ----- From: To: Sent: Sunday, July 16, 2000 12:23 PM Subject: Latest RELENG_4. > > Hello, > > What is the latest FreeBSD-STABLE release, and is it stable enough for a > productional system? > > Thanks, > Noor Dawod > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 10:42:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsd.unixvillain.com (sprawly.sprawlnet.com [208.224.169.130]) by hub.freebsd.org (Postfix) with ESMTP id 18F6637B5EB for ; Mon, 17 Jul 2000 10:42:40 -0700 (PDT) (envelope-from richard@sprawlnet.com) Received: from jedi (jedi.sprawlnet.com [208.224.169.134]) by bsd.unixvillain.com (8.9.3/8.9.2) with SMTP id BAA17756; Tue, 18 Jul 2000 01:47:15 -0400 (EDT) (envelope-from richard@sprawlnet.com) Message-ID: <001601bff015$5bb6a860$86a9e0d0@devnull.sprawlnet.com> From: "Rich" To: "David E. Brooks Jr" , "freebsd stable" References: <002c01bff008$fc0a95e0$86a9e0d0@devnull.sprawlnet.com> <01c701bff013$5d92a640$0405010a@office.iencentral.com> Subject: Re: Maybe someone here has a solution? Date: Mon, 17 Jul 2000 13:35:11 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01BFEFF3.D47BAE70" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0013_01BFEFF3.D47BAE70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable My apologies for misdirecting this email and thank you to those that = responded. -Rich ----- Original Message -----=20 From: David E. Brooks Jr=20 To: Rich ; freebsd stable=20 Sent: Monday, July 17, 2000 1:20 PM Subject: Re: Maybe someone here has a solution? Alas, Informix doesn't have a native FreeBSD port of their esql/c = product. However, we recently went through a database selection process = and our Informix sales guys managed to get approval for the port (just = esql/c, not the entire database) to be done. We ultimately went with = another database so I don't know the status of the port, but if they = went ahead it would be nearing completion. (And if they didn't, I don't = imagine it would be too difficult to get the project going again). I = suggest contacting your friendly Informix sales rep and see what they = can do for you. -- Dave ----- Original Message -----=20 From: Rich=20 To: freebsd stable=20 Sent: Monday, July 17, 2000 12:06 PM Subject: Maybe someone here has a solution? Most of our machines in this office run FreeBSD-3.x or 4.x and I = need to write an application that selects certain info from an Informix = database and displays the results in HTML. The Informix DB is on a SCO = OpenServer 5.x boxen ...=20 I can very easily use APACHE/Mod_Perl + ESQL/C to write this = application ... but I can't find any info on using esql/c on a freebsd = box or even something similar that I can use. Anyone have any idea's or suggestions for th ebest solution? -thanks Rich ------=_NextPart_000_0013_01BFEFF3.D47BAE70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
My apologies for misdirecting this = email and thank=20 you to those that responded.
 
-Rich
----- Original Message -----
From:=20 David E.=20 Brooks Jr
To: Rich ; freebsd stable
Sent: Monday, July 17, 2000 = 1:20 PM
Subject: Re: Maybe someone here = has a=20 solution?

Alas, Informix doesn't have a native = FreeBSD port=20 of their esql/c product.  However, we recently went through a = database=20 selection process and our Informix sales guys managed to get approval = for the=20 port (just esql/c, not the entire database) to be done.  We = ultimately=20 went with another database so I don't know the status of the port, but = if they=20 went ahead it would be nearing completion.  (And if they didn't, = I don't=20 imagine it would be too difficult to get the project going = again).  I=20 suggest contacting your friendly Informix sales rep and see what they = can do=20 for you.
 
-- Dave
----- Original Message -----
From:=20 Rich=20
To: freebsd stable
Sent: Monday, July 17, 2000 = 12:06=20 PM
Subject: Maybe someone here = has a=20 solution?

Most of our machines in this office = run=20 FreeBSD-3.x or 4.x and I need to write an application that selects = certain=20 info from  an Informix database and displays the results in = HTML. The=20 Informix DB is on a SCO OpenServer 5.x boxen ...
 
I can very easily use = APACHE/Mod_Perl + ESQL/C=20 to write this application ... but I can't find any info on using = esql/c on a=20 freebsd box or even something similar that I can use.
 
Anyone have any idea's or = suggestions for th=20 ebest solution?
 
-thanks
Rich
 
------=_NextPart_000_0013_01BFEFF3.D47BAE70-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 11: 3:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6006D37BDF5; Mon, 17 Jul 2000 11:03:30 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA01129; Mon, 17 Jul 2000 11:02:57 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id LAA71860; Mon, 17 Jul 2000 11:02:02 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000717113526.C80281@lucifer.bart.nl> Date: Mon, 17 Jul 2000 11:02:02 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Jeroen Ruigrok van der Werven Subject: Re: bootdisk problems/md related Cc: phk@freebsd.org, stable@freebsd.org, "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Jeroen Ruigrok van der Werven wrote: > -On [20000717 11:30], Jordan K. Hubbard (jkh@zippy.osd.bsdi.com) wrote: >>That's very strange - we don't see the same problem here. I'll >>poke around a bit and see if I can reproduce it at all. > > Thanks. > > Some older disks did work. I'll go download a bunch of different dates > and see if I can pinpoint the date this starts happening. What exact error are you talking about? The md1 fatal error? I _know_ that is fixed in 5.0 and 4.x. If you have some other error, let me know. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 11: 9:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 60EBB37BF97; Mon, 17 Jul 2000 11:08:50 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id UAA39105; Mon, 17 Jul 2000 20:08:44 +0200 (CEST) (envelope-from asmodai) Date: Mon, 17 Jul 2000 20:08:44 +0200 From: Jeroen Ruigrok van der Werven To: John Baldwin Cc: phk@freebsd.org, stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: bootdisk problems/md related Message-ID: <20000717200844.I38656@lucifer.bart.nl> References: <20000717113526.C80281@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jhb@freebsd.org on Mon, Jul 17, 2000 at 11:02:02AM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000717 20:05], John Baldwin (jhb@freebsd.org) wrote: >What exact error are you talking about? The md1 fatal error? The one I posted earlier on in this thread. md related. >I _know_ that is fixed in 5.0 and 4.x. If you have some other >error, let me know. Well, it isn't fixed for my boxen with the disks of the 15th. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl No cord or cable can draw so forcibly, or bind so fast, as love can do with a single thread... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 11:31:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id CA71837BCDA for ; Mon, 17 Jul 2000 11:31:42 -0700 (PDT) (envelope-from rene@canyon.demon.nl) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13EFg2-0004YB-00; Mon, 17 Jul 2000 18:31:38 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id UAA01002; Mon, 17 Jul 2000 20:24:10 +0200 (CEST) (envelope-from rene) Date: Mon, 17 Jul 2000 20:24:10 +0200 From: Rene de Vries To: Johan Huldtgren Cc: freebsd-stable@freebsd.org Subject: Re: 2 different problems Message-ID: <20000717202410.A920@grand.canyon.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from johan.huldtgren@rixtelecom.se on Mon, Jul 17, 2000 at 05:09:17PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan, I've seen problems during an installworld when using -j x (where x > 1). I only do a buildworld using -j 4 and then use ordinary make (without -j) for the install. A -j 5 will sometimes try to create files in a directory one of the other make sub processes still has to make (and this will fail with a message simmilar to yours). Rene On Mon, Jul 17, 2000 at 05:09:17PM +0200, Johan Huldtgren wrote: > Now my second machine gets as far as "make installworld" it fails on: > > ln: /usr/share/man/man3/setruid.3.gz: No such file or directory > *** Error code 1 -- Rene de Vries http://www.tcja.nl mailto:rene@tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 11:51:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 81B5337BA9B for ; Mon, 17 Jul 2000 11:51:44 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id OAA90465 for ; Mon, 17 Jul 2000 14:52:06 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 17 Jul 2000 14:52:05 -0400 (EDT) From: Adam To: stable@freebsd.org Subject: Problem with installworld Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4.0 cd subscription: $25 Time spent installing: 10-15 min cvsup to -stable: ~10-15 min buildworld: 1.5 hours Reading UPDATING: free re-reading email to check for commits: 5 min cvsup again just in case: 5 min a working build/installworld: priceless Did I miss doing something? I'm in the USA but make.conf says I'm not. I didn't tell it that, so something is jumping the gun. (I *did* select michigan from the timezone portion, shouldnt that be enough clue for sysinstall to guess im in USA? After editing make.conf so USA_RESIDENT=yes, it works fine. What about people not in the USA however? ===> secure/lib/librsausa install -c -o root -g wheel -m 444 librsaUSA.a /usr/lib install -c -o root -g wheel -m 444 librsaUSA_p.a /usr/lib install -c -s -o root -g wheel -m 444 librsaUSA.so.1 /usr/lib ln -sf librsaUSA.so.1 /usr/lib/librsaUSA.so ===> secure/lib/librsaintl install -c -o root -g wheel -m 444 librsaINTL.a /usr/lib install: librsaINTL.a: No such file or directory *** Error code 71 Stop in /usr/src/secure/lib/librsaintl. *** Error code 1 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src/secure. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 12:11: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 8526537BC2D for ; Mon, 17 Jul 2000 12:10:56 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id MAA00168; Mon, 17 Jul 2000 12:10:30 -0700 Message-ID: <39735A3A.F638E8FB@urx.com> Date: Mon, 17 Jul 2000 12:10:50 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Adam Cc: stable@FreeBSD.ORG Subject: Re: Problem with installworld References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam wrote: > > 4.0 cd subscription: $25 > Time spent installing: 10-15 min > cvsup to -stable: ~10-15 min > buildworld: 1.5 hours > Reading UPDATING: free > re-reading email to check for commits: 5 min > cvsup again just in case: 5 min > a working build/installworld: priceless ^^^^^^^^^ I have a couple of friends that are artists and I think your first installworld and install kernel would be like selling your first painting for more than $1000 USD. I did it and it worked (pumping hand). > > Did I miss doing something? I'm in the USA but make.conf says I'm not. > I didn't tell it that, so something is jumping the gun. > (I *did* select michigan from the timezone portion, shouldnt that be > enough clue for > sysinstall to guess im in USA? > After editing make.conf so USA_RESIDENT=yes, it works fine. > What about people not in the USA however? They probably cvsup'ed from an international site. I have found that you have to look at make.conf. I don't willingly let anything change it but have noticed in the past that it will be switched back to "NO" occasionally. It is usually a couple of cvsup's later before I see it. Now, I usually check it to make sure it says "YES" before I do a buildworld. I had done a couple of RELENG_4 cvsup's and builds and hadn't checked it. Nothing had changed and it was still set to "YES". I'm am still building a US 4.x-Stable. I can smile again :))). Have a good day, Kent > > ===> secure/lib/librsausa > install -c -o root -g wheel -m 444 librsaUSA.a /usr/lib > install -c -o root -g wheel -m 444 librsaUSA_p.a /usr/lib > install -c -s -o root -g wheel -m 444 librsaUSA.so.1 /usr/lib > ln -sf librsaUSA.so.1 /usr/lib/librsaUSA.so > ===> secure/lib/librsaintl > install -c -o root -g wheel -m 444 librsaINTL.a /usr/lib > install: librsaINTL.a: No such file or directory > *** Error code 71 > Stop in /usr/src/secure/lib/librsaintl. > *** Error code 1 > Stop in /usr/src/secure/lib. > *** Error code 1 > Stop in /usr/src/secure. > *** Error code 1 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 12:26:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id A545F37B560 for ; Mon, 17 Jul 2000 12:26:04 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id MAA15929; Mon, 17 Jul 2000 12:25:58 -0700 (PDT) Message-ID: <39735DC6.BE82F7CB@isi.edu> Date: Mon, 17 Jul 2000 12:25:58 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 To: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: KAME/FreeBSD-stable merge Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is there any reason why the (misnamed, but that's another issue) XBONEHACK option was eliminated during the recent KAME/FreeBSD-stable merge? (File /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, and we'd really like to see it merged into FreeBSD. Below is the short patch that will do the trick. It's very simple, so I don't expect it to cause any problems: --- if_gif.c.fbsd Mon Jul 17 12:20:48 2000 +++ if_gif.c.kame Mon Jul 17 12:16:21 2000 @@ -470,12 +522,14 @@ sc2->gif_psrc->sa_family != src->sa_family || sc2->gif_psrc->sa_len != src->sa_len) continue; +#ifndef XBONEHACK /* can't configure same pair of address onto two gifs */ if (bcmp(sc2->gif_pdst, dst, dst->sa_len) == 0 && bcmp(sc2->gif_psrc, src, src->sa_len) == 0) { error = EADDRNOTAVAIL; goto bad; } +#endif /* can't configure multiple multi-dest interfaces */ #define multidest(x) \ -- Lars Eggert Information Sciences Institute http://www.isi.edu/~larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:30:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manston.placeware.com (manston.placeware.com [209.1.15.21]) by hub.freebsd.org (Postfix) with ESMTP id 8E89137B5D0 for ; Mon, 17 Jul 2000 13:30:43 -0700 (PDT) (envelope-from philippe@le-berre.com) Received: from aberwrach.le-berre.com (dhcp185.placeware.com [209.1.15.185]) by manston.placeware.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id NW6MFFZH; Mon, 17 Jul 2000 13:30:27 -0700 Message-Id: <4.3.2.7.2.20000717130800.00c18840@212.129.1.43> X-Sender: philippe.le.berre/le-berre.com@212.129.1.43 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 17 Jul 2000 13:12:06 -0700 To: stable@FreeBSD.ORG From: Philippe Le Berre Subject: How to installworld remotely? In-Reply-To: <39735A3A.F638E8FB@urx.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After being through the high numbers of emails on the new *build* procedure, I still haven't see any hint on how to handle the make installworld remotely. Can I do it without the shutdown? Can I remotely log on *shutdown* system ? Do I have to fly to the box? Thanks for the help and all my excuses if the answer to this question was in the numerous email on that topic. regards -philippe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:37:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 16E1137BBDB for ; Mon, 17 Jul 2000 13:37:43 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id NAA27699 for ; Mon, 17 Jul 2000 13:37:42 -0700 (PDT) Message-ID: <39736E96.1AC0917B@isi.edu> Date: Mon, 17 Jul 2000 13:37:42 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: buildkernel failure: netinet6/esp_core.c Content-Type: multipart/mixed; boundary="------------CECF4A39C54D39BBB253D1BE" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------CECF4A39C54D39BBB253D1BE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Building a kernel (config file attached) on a freshly updated -stable system fails with: cc -c -O3 -pipe -funroll-loops -fomit-frame-pointer -fno-builtin -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DXBONEHACK -DMAX_GIF_NEST=2147483647 -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet6/esp_core.c ../../netinet6/esp_core.c: In function `esp_descbc_decrypt': ../../netinet6/esp_core.c:319: void value not ignored as it ought to be ../../netinet6/esp_core.c:238: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_descbc_encrypt': ../../netinet6/esp_core.c:440: void value not ignored as it ought to be ../../netinet6/esp_core.c:345: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_decrypt': ../../netinet6/esp_core.c:571: void value not ignored as it ought to be ../../netinet6/esp_core.c:519: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_encrypt': ../../netinet6/esp_core.c:649: void value not ignored as it ought to be ../../netinet6/esp_core.c:598: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_cast128cbc_decrypt': ../../netinet6/esp_core.c:743: void value not ignored as it ought to be ../../netinet6/esp_core.c:687: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_cast128cbc_encrypt': ../../netinet6/esp_core.c:818: void value not ignored as it ought to be ../../netinet6/esp_core.c:765: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_rc5cbc_decrypt': ../../netinet6/esp_core.c:1064: void value not ignored as it ought to be ../../netinet6/esp_core.c:1014: warning: `error' might be used uninitialized in this function ../../netinet6/esp_core.c: In function `esp_rc5cbc_encrypt': ../../netinet6/esp_core.c:1134: void value not ignored as it ought to be ../../netinet6/esp_core.c:1085: warning: `error' might be used uninitialized in this function *** Error code 1 -- Lars Eggert Information Sciences Institute http://www.isi.edu/~larse/ University of Southern California --------------CECF4A39C54D39BBB253D1BE Content-Type: text/plain; charset=us-ascii; name="PRECISION" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="PRECISION" # ---------------------------------------------------------------------------- # $RCSfile: PRECISION,v $ # # $Revision: 1.20 $ # $Author: larse $ # $Date: 2000/07/14 00:28:49 $ # $State: Exp $ # ---------------------------------------------------------------------------- # $Log: PRECISION,v $ # Revision 1.20 2000/07/14 00:28:49 larse # More gifs, no AUTO_EOI1. # # Revision 1.19 2000/06/26 21:11:28 larse # From -stable. # # Revision 1.18 2000/06/06 21:39:39 larse # Systems running kernels with option NFS do not need nfsiod. # # Revision 1.17 2000/06/05 18:13:36 larse # Kernel working on Gateway Solo notebooks now. # # Revision 1.16 2000/06/02 01:19:17 larse # make.conf # # Revision 1.15 2000/05/18 17:35:13 larse # Enabled ATAPI DMA, speaker, perfmon, ktrace, removed some things. # # Revision 1.14 2000/04/26 23:21:50 larse # Enabled more IP goodies in case we need them. # # Revision 1.13 2000/04/25 18:09:28 larse # Support for Hauppauge cards, disabled unneeded SMB/I2C stuff. # # Revision 1.12 2000/04/21 08:20:06 larse # pcf caused problems on dee # # Revision 1.11 2000/04/20 08:47:03 larse # Enabled I2C and SMBus on the NS-8000 Gateways. # # Revision 1.10 2000/04/19 03:15:09 larse # Enabled memory-mapped I/O for aic SCSI adapter. # # Revision 1.9 2000/04/07 22:07:55 larse # More mbuf clusters, more gif interfaces, enabled SMBus. # # Revision 1.8 2000/03/31 01:21:28 larse # Re-enabled non-HARP ATM, HARP cannot deal with Adaptec cards. # # Revision 1.7 2000/03/30 23:03:40 larse # Minor changes, now works on tan (old lab host) and mul (new lab host) # as well has the new office machines. # # Revision 1.6 2000/03/30 14:05:32 larse # Switched to HARP ATM. # # Revision 1.5 2000/03/30 13:08:52 larse # Added options to support lab hosts (works on tan at least). # # Revision 1.4 2000/03/30 11:56:44 larse # Disabled firewall/divert. # # Revision 1.3 2000/03/24 11:07:29 larse # Enabled ATAPI DMA, gif tunnels, disabled LSSR, added PSM_HOOKRESUME. # # Revision 1.2 2000/03/21 13:50:41 larse # Added cvs header. # # ---------------------------------------------------------------------------- # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: # strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL options INCLUDE_CONFIG_FILE # Include this file in kernel makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols machine i386 #cpu I386_CPU #cpu I486_CPU cpu I586_CPU # for our notebooks (Solos/Librettos) cpu I686_CPU # for all other machines ident PRECISION maxusers 128 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required #options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=0 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor #options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #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 device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD #device pass # Passthrough device (direct SCSI access) # RAID controllers #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq ? port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq ? port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) #device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ed #device ex device ep # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse # USB Ethernet #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet # CPU_DISABLE_5X86_LSSER disables load store serialize (i.e. enables # reorder). This option should not be used if you use memory mapped # I/O device(s). # options CPU_DISABLE_5X86_LSSER # CPU_FASTER_5X86_FPU enables faster FPU exception handler. options CPU_FASTER_5X86_FPU # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is # executed. This should be included for ALL kernels that won't run # on a Pentium. # # DISABLED, our notebooks (Solos/Librettos) have Pentiums! # options NO_F00F_HACK # Allow user-mode programs to manipulate their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of)# options USER_LDT #allow user-level control of i386 ldt # TCP_DROP_SYNFIN adds support for ignoring TCP packets with SYN+FIN. This # prevents nmap et al. from identifying the TCP/IP stack, but breaks support # for RFC1644 extensions and is not recommended for web servers. options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN # TCP_RESTRICT_RST adds support for blocking the emission of TCP RST packets. # This is useful on systems which are exposed to SYN floods (e.g. IRC servers) # or any system which one does not want to be easily portscannable. options TCP_RESTRICT_RST #restrict emission of TCP RST options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options INET6 #IPv6 communications protocols # The `gif' pseudo-device implements IPv6 over IP4 tunneling, # IPv4 over IPv6 tunneling, IPv4 over IPv4 tunneling and # IPv6 over IPv6 tunneling. pseudo-device gif 32 #IPv6 and IPv4 tunneling # The `faith' pseudo-device captures packets sent to it and diverts them # to the IPv4/IPv6 translation daemon. #pseudo-device faith 1 #for IPv6 and IPv4 translation # IPFIREWALL enables support for IP firewall construction, in # conjunction with the `ipfw' program. IPFIREWALL_VERBOSE sends # logged packets to the system logger. IPFIREWALL_VERBOSE_LIMIT # limits the number of times a matching entry can be logged. options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=1000 #limit verbosity options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=1000 # IPFIREWALL_DEFAULT_TO_ACCEPT causes the default rule (at boot) to # allow everything. Use with care, if a cracker can crash your # firewall machine, they can get to your protected machines. However, # if you are using it as an as-needed filter for specific problems as # they arise, then this may be for you. Changing the default to 'allow' # means that you won't get stuck if the kernel and /sbin/ipfw binary get # out of sync. options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPV6FIREWALL_DEFAULT_TO_ACCEPT # ICMP_BANDLIM enables icmp error response bandwidth limiting. You # typically want this option as it will help protect the machine from # D.O.S. packet attacks. options ICMP_BANDLIM # DUMMYNET enables the "dummynet" bandwidth limiter. You need # IPFIREWALL as well. See the dummynet(4) manpage for more info. options DUMMYNET # BRIDGE enables bridging between ethernet cards -- see bridge(4). # You can use IPFIREWALL and dummynet together with bridging. #options BRIDGE # IPDIVERT enables the divert IP sockets, used by ``ipfw divert'' options IPDIVERT #divert sockets # MROUTING enables the kernel multicast packet forwarder, which works # with mrouted(8). options MROUTING # Multicast routing # IPSTEALTH enables code to support stealth forwarding (i.e., forwarding # packets without touching the ttl). This can be useful to hide firewalls # from traceroute and similar tools. options IPSTEALTH #support for stealth forwarding options IPFILTER #ipfilter support options IPFILTER_LOG #ipfilter logging # Soft updates is technique for improving file system speed and # making abrupt shutdown less risky. It is not enabled by default due # to copyright restraints on the code that implement it. # # Read ../../ufs/ffs/README.softupdates to learn what you need to # do to enable this. ../../contrib/softupdates/README gives # more details on how they actually work. options SOFTUPDATES pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's #pseudo-device vn #Vnode driver (turns a file into a device) # AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A # interrupt controller. This saves about 0.7-1.25 usec for each interrupt. # This option breaks suspend/resume on some portables. # THIS BREAKS SLEEP SUPPORT ON THE SONY LAPTOPS, POSSIBLY OTHERS. #options AUTO_EOI_1 # To include support for VESA video modes options VESA options SC_HISTORY_SIZE=2000 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode # The newpcm driver (use INSTEAD of snd0 and all VOXWARE drivers!). # Note that motherboard sound devices may require options PNPBIOS. # # Supported cards include: # Creative SoundBlaster ISA PnP/non-PnP # Supports ESS and Avance ISA chips as well. # Gravis UltraSound ISA PnP/non-PnP # Crystal Semiconductor CS461x/428x PCI # Neomagic 256AV (ac97) # Most of the more common ISA/PnP sb/mss/ess compatable cards. # For PnP/PCI sound cards device pcm options PNPBIOS device joy0 at isa? port IO_GAME # Add support for the EXT2FS filesystem of Linux fame. Be a bit # careful with this - the ext2fs code has a tendency to lag behind # changes and not be exercised very much, so mounting read/write could # be dangerous (and even mounting read only could result in panics.) options EXT2FS # Enable the kernel debugger. options DDB # Options for psm: options PSM_HOOKRESUME #hook the system resume event, useful #for some laptops options PSM_RESETAFTERSUSPEND #reset the device at the resume event # ATM related options # # The `en' device provides support for Efficient Networks (ENI) # ENI-155 PCI midway cards, and the Adaptec 155Mbps PCI ATM cards (ANA-59x0). # # atm pseudo-device provides generic atm functions and is required for # atm devices. # NATM enables the netnatm protocol family that can be used to # bypass TCP/IP. # # the current driver supports only PVC operations (no atm-arp, no multicast). # for more details, please read the original documents at # http://www.ccrc.wustl.edu/pub/chuck/tech/bsdatm/bsdatm.html # pseudo-device atm device en options NATM # The 'bktr' device is a PCI video capture device using the Brooktree # bt848/bt848a/bt849a/bt878/bt879 chipset. When used with a TV Tuner it forms a # TV card, eg Miro PC/TV, Hauppauge WinCast/TV WinTV, VideoLogic Captivator, # Intel Smart Video III, AverMedia, IMS Turbo, FlyVideo. # # Brooktree driver has been ported to the new I2C framework. Thus, # you'll need to have the following 3 lines in the kernel config. # device smbus # device iicbus # device iicbb # The iic and smb devices are only needed if you want to control other # I2C slaves connected to the external connector of some cards. device bktr # The aic7xxx driver will attempt to use memory mapped I/O for all PCI # controllers that have it configured only if this option is set. Unfortunately, # this doesn't work on some motherboards, which prevents it from being the # default. options AHC_ALLOW_MEMIO # KTRACE enables the system-call tracing facility ktrace(2). options KTRACE #kernel tracing # PERFMON causes the driver for Pentium/Pentium Pro performance counters # to be compiled. See perfmon(4) for more information. options PERFMON # pca: PCM audio through your PC speaker # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 options PPC_PROBE_CHIPSET # Enable chipset specific detection # (see flags in ppc(4)) # If you are running a machine just as a fileserver for PC and MAC # users, using SAMBA or Netatalk, you may consider setting this option # and keeping all those users' directories on a filesystem that is # mounted with the suiddir option. This gives new files the same # ownership as the directory (similar to group). It's a security hole # if you let these users run programs, so confine it to file-servers # (but it'll save you lots of headaches in those cases). Root owned # directories are exempt and X bits are cleared. The suid bit must be # set on the directory as well; see chmod(1) PC owners can't see/set # ownerships so they keep getting their toes trodden on. This saves # you all the support calls as the filesystem it's used on will act as # they expect: "It's my dir so it must be my file". options SUIDDIR # allow recursive gif tunnels this many levels deep options MAX_GIF_NEST=2147483647 # 2147483647 = INT_MAX # allow multiple tunnels between same two physical interfaces options XBONEHACK --------------CECF4A39C54D39BBB253D1BE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:40:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id E7E9F37BE41 for ; Mon, 17 Jul 2000 13:40:47 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id NAA24766; Mon, 17 Jul 2000 13:40:38 -0700 (PDT) Date: Mon, 17 Jul 2000 13:40:38 -0700 From: Brooks Davis To: Philippe Le Berre Cc: stable@FreeBSD.ORG Subject: Re: How to installworld remotely? Message-ID: <20000717134038.A23145@orion.ac.hmc.edu> References: <39735A3A.F638E8FB@urx.com> <4.3.2.7.2.20000717130800.00c18840@212.129.1.43> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <4.3.2.7.2.20000717130800.00c18840@212.129.1.43>; from philippe@le-berre.com on Mon, Jul 17, 2000 at 01:12:06PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 01:12:06PM -0700, Philippe Le Berre wrote: > After being through the high numbers of emails on the new *build* > procedure, I still haven't see any hint on how to handle the make > installworld remotely. Can I do it without the shutdown? Can I remotely log > on *shutdown* system ? Do I have to fly to the box? I'm assuming that by shutdown you mean single user mode. To use single user mode, you must be at the console (though with a properly connected serial console, you can define "at" rather losely.) People who have tried it generally report success with running instllworld in normal, multiuser mode though shutting down most servers is a good idea while doing so. You should always upgrade your kernel with your userland so it will be necessicary to reboot. If all goes well, this should be fine. If not, you're is serious trouble. I've certaintly done remote upgrades of systems myself, but they haven't been "production" system by any stretch of the imagination. It's generally fine, but in the end you have to make the call. If at all possiable, paractice the upgrade on something non-critial first. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:41:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bmw.cobaka.com (bmw.cobaka.com [209.67.40.174]) by hub.freebsd.org (Postfix) with ESMTP id 4900037BE41 for ; Mon, 17 Jul 2000 13:41:10 -0700 (PDT) (envelope-from winter@villaweb.net) Received: from localhost (winter@localhost) by bmw.cobaka.com (8.9.3/8.9.1) with ESMTP id NAA94370 for ; Mon, 17 Jul 2000 13:47:22 -0700 (PDT) Date: Mon, 17 Jul 2000 13:47:22 -0700 (PDT) From: winter X-Sender: winter@bmw.cobaka.com To: freebsd-stable@freebsd.org Subject: Upgrading to 4.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I got upto the step "cd /usr/src/sys/modules" "make install" I got this error: boxster:/usr/src/sys/modules# make ===> aha Warning: Object directory not changed from original /usr/src/sys/modules/aha make: don't know how to make opt_cam.h. Stop *** Error code 2 Stop. boxster:/usr/src/sys/modules# make install ===> aha install -c -o root -g wheel -m 555 aha.ko /modules install: aha.ko: No such file or directory *** Error code 71 if i go into the aha dir... i get this: boxster:/usr/src/sys/modules/aha# make Warning: Object directory not changed from original /usr/src/sys/modules/aha @ -> /usr/src/sys machine -> /usr/include/machine make: don't know how to make opt_cam.h. Stop Please help! --Phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:43:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail02.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 1922737BC43 for ; Mon, 17 Jul 2000 13:43:24 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave.uhring.com) by mail02.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 1412556; Mon, 17 Jul 2000 16:48:37 -0400 From: David Uhring To: Walter Campbell , Shawn Barnhart Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Mon, 17 Jul 2000 15:40:52 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-stable@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Message-Id: <00071715431400.01465@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Walter Campbell wrote: > > The FreeBSD install I'm using had previously been running on a generic Dell > > Pentium 200 and lived through a half-dozen buildworlds without breaking. > > > > Since I haven't seen a anyone else's world breaking this way, I'm assuming > > that this is a hardware problem -- but what kind? Memory? I have a spare > > Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start? > > > > Memory is likely the problem, but also look at the L2 cache and anything > else that may cause memory corruption. > > One of my BSD box was having SIGSEGV's when compiling and occasional > reboots. I have had no instability since replacing the L2 cache > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message You might also check the cpu temperature during the compile. Using a K6-3/450, my cpu cooler was getting quite hot to the touch during the make and would exit with signal 10 or signal 11. I finally took to cover off the case and set up a box fan to force additional air into the case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:46:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from marble.fbcc.com (ns2.fbcc.com [216.54.252.3]) by hub.freebsd.org (Postfix) with SMTP id C063037BC33 for ; Mon, 17 Jul 2000 13:46:22 -0700 (PDT) (envelope-from jim@jimking.net) Received: (qmail 23753 invoked from network); 17 Jul 2000 20:49:20 -0000 Received: from unknown (HELO bluto.jimking.net) (216.54.255.8) by ns2.fbcc.com with SMTP; 17 Jul 2000 20:49:20 -0000 Received: from jking (jking.lgc.com [134.132.75.164]) by bluto.jimking.net (8.9.3/8.9.3) with SMTP id PAA75114; Mon, 17 Jul 2000 15:46:17 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <009001bff030$0f5e7bd0$a44b8486@jking> From: "Jim King" To: , "Philippe Le Berre" References: <4.3.2.7.2.20000717130800.00c18840@212.129.1.43> Subject: Re: How to installworld remotely? Date: Mon, 17 Jul 2000 15:46:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Philippe Le Berre wrote: > After being through the high numbers of emails on the new *build* > procedure, I still haven't see any hint on how to handle the make > installworld remotely. Can I do it without the shutdown? Can I remotely log > on *shutdown* system ? Do I have to fly to the box? > > Thanks for the help and all my excuses if the answer to this question was > in the numerous email on that topic. I remotely upgraded a couple boxes from 3.4-stable to 4.0-stable. I did it all in multi-user, but I did shut down non-essential stuff while I was doing the upgrade (Apache, INN, etc.) Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:49:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id D5E0437BBD2 for ; Mon, 17 Jul 2000 13:49:15 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA63065; Mon, 17 Jul 2000 13:49:13 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 13:49:13 -0700 From: "David O'Brien" To: Keith Mackay Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s Message-ID: <20000717134913.A63045@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <000d01bfefff$6aa12d70$f1184418@asgard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000d01bfefff$6aa12d70$f1184418@asgard>; from keith.mackay@home.com on Mon, Jul 17, 2000 at 10:58:06AM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote: > Is there a known issue in bioscall.s? Yes, it has been documented all over the place in this mailing list. It is also documented in /usr/src/UPDATING. You should review the expectations of running -STABLE and consider if you are better off just sticking with the released product. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:51:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2DE5C37BCE7 for ; Mon, 17 Jul 2000 13:51:45 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA63079; Mon, 17 Jul 2000 13:51:22 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 13:51:22 -0700 From: "David O'Brien" To: carl@bl.echidna.id.au Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildworld problems (4.0-RELEASE to 4.0-STABLE) Message-ID: <20000717135122.B63045@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200007170255.e6H2tvH28081@rollcage.bl.echidna.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007170255.e6H2tvH28081@rollcage.bl.echidna.id.au>; from carl@bl.echidna.id.au on Mon, Jul 17, 2000 at 12:55:57PM +1000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 12:55:57PM +1000, carl@bl.echidna.id.au wrote: > The box either reboots part-way through, or I see something like this : The machine either has a serious problem, or your /usr/src/* is not consistent with the bits that make up RELENG_4 (4-STABLE), or your /usr/obj/* contains corrupted files. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:53:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from d1o93.telia.com (d1o93.telia.com [194.17.166.241]) by hub.freebsd.org (Postfix) with ESMTP id 7551337BCD9 for ; Mon, 17 Jul 2000 13:53:38 -0700 (PDT) (envelope-from johan.huldtgren@rixtelecom.se) Received: from vaticide (h5fls4o93flexi.telia.com [62.20.226.5]) by d1o93.telia.com (8.8.8/8.8.8) with SMTP id XAA24819 for ; Mon, 17 Jul 2000 23:17:18 +0200 (CEST) From: "Johan Huldtgren" To: Subject: RE: 2 different problems Date: Mon, 17 Jul 2000 22:52:24 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000717202410.A920@grand.canyon.demon.nl> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rene de Vries wrote: > I've seen problems during an installworld when using -j x (where x > 1). I > only do a buildworld using -j 4 and then use ordinary make (without -j) for > the install. A -j 5 will sometimes try to create files in a directory one of > the other make sub processes still has to make (and this will fail with a > message simmilar to yours). Thanks, I made installworld without the -j x flag and it worked fine. Also my apologies for managing to send my original message twice this morning. Sincerely, Johan Huldtgren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:54:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 3D6C537BC50 for ; Mon, 17 Jul 2000 13:54:47 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id NAA00054; Mon, 17 Jul 2000 13:54:43 -0700 Message-ID: <397372A6.3B9A4664@urx.com> Date: Mon, 17 Jul 2000 13:55:02 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildkernel failure: netinet6/esp_core.c References: <39736E96.1AC0917B@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lars Eggert wrote: > > Building a kernel (config file attached) on a freshly updated -stable > system fails with: > > cc -c -O3 -pipe -funroll-loops -fomit-frame-pointer -fno-builtin -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include > -DXBONEHACK -DMAX_GIF_NEST=2147483647 -D_KERNEL -include opt_global.h -elf > -mpreferred-stack-boundary=2 ../../netinet6/esp_core.c > ../../netinet6/esp_core.c: In function `esp_descbc_decrypt': > ../../netinet6/esp_core.c:319: void value not ignored as it ought to be > ../../netinet6/esp_core.c:238: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_descbc_encrypt': > ../../netinet6/esp_core.c:440: void value not ignored as it ought to be > ../../netinet6/esp_core.c:345: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_decrypt': > ../../netinet6/esp_core.c:571: void value not ignored as it ought to be > ../../netinet6/esp_core.c:519: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_encrypt': > ../../netinet6/esp_core.c:649: void value not ignored as it ought to be > ../../netinet6/esp_core.c:598: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_cast128cbc_decrypt': > ../../netinet6/esp_core.c:743: void value not ignored as it ought to be > ../../netinet6/esp_core.c:687: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_cast128cbc_encrypt': > ../../netinet6/esp_core.c:818: void value not ignored as it ought to be > ../../netinet6/esp_core.c:765: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_rc5cbc_decrypt': > ../../netinet6/esp_core.c:1064: void value not ignored as it ought to be > ../../netinet6/esp_core.c:1014: warning: `error' might be used > uninitialized in this function > ../../netinet6/esp_core.c: In function `esp_rc5cbc_encrypt': > ../../netinet6/esp_core.c:1134: void value not ignored as it ought to be > ../../netinet6/esp_core.c:1085: warning: `error' might be used > uninitialized in this function > *** Error code 1 I just finish cvsup'ing and have completed a buildworld and buildkernel without any problems. Did you cvsup'ed such that you have the crypto files since they are part of src-all now days. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 13:58:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5D3B537BBEC; Mon, 17 Jul 2000 13:58:39 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA56912; Mon, 17 Jul 2000 13:58:39 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 13:58:38 -0700 (PDT) From: Kris Kennaway To: Adam Cc: stable@freebsd.org Subject: Re: Problem with installworld In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Adam wrote: > 4.0 cd subscription: $25 > Time spent installing: 10-15 min > cvsup to -stable: ~10-15 min > buildworld: 1.5 hours > Reading UPDATING: free > re-reading email to check for commits: 5 min > cvsup again just in case: 5 min > a working build/installworld: priceless > > > Did I miss doing something? I'm in the USA but make.conf says I'm not. > I didn't tell it that, so something is jumping the gun. Sysinstall had a bug which would put the wrong value in make.conf..it's fixed in later editions. > (I *did* select michigan from the timezone portion, shouldnt that be > enough clue for > sysinstall to guess im in USA? Not necessarily - one might want to install a box with a timezone that isn't local (e.g. GMT). > After editing make.conf so USA_RESIDENT=yes, it works fine. > What about people not in the USA however? They're fine :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14: 0:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1F9A437BC4B; Mon, 17 Jul 2000 14:00:17 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA57189; Mon, 17 Jul 2000 14:00:16 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 14:00:16 -0700 (PDT) From: Kris Kennaway To: Lars Eggert Cc: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: Re: KAME/FreeBSD-stable merge In-Reply-To: <39735DC6.BE82F7CB@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Lars Eggert wrote: > Hi, > > is there any reason why the (misnamed, but that's another issue) XBONEHACK > option was eliminated during the recent KAME/FreeBSD-stable merge? (File > /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, > and we'd really like to see it merged into FreeBSD. I'm not sure. Perhaps itojun felt it wouldn't be necessary outside the KAME snaps. If you guys are thinking of switching to use 4.1-R I'll add it back. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14: 1:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9CFC837BC13; Mon, 17 Jul 2000 14:01:19 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA57318; Mon, 17 Jul 2000 14:01:19 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 14:01:19 -0700 (PDT) From: Kris Kennaway To: Lars Eggert Cc: freebsd-stable@freebsd.org Subject: Re: buildkernel failure: netinet6/esp_core.c In-Reply-To: <39736E96.1AC0917B@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Lars Eggert wrote: > Building a kernel (config file attached) on a freshly updated -stable > system fails with: Did you cvsup the src-sys-crypto collection? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14: 5:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 613F137BC16; Mon, 17 Jul 2000 14:05:28 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA01971; Mon, 17 Jul 2000 14:05:27 -0700 (PDT) Message-ID: <39737517.BAC99265@isi.edu> Date: Mon, 17 Jul 2000 14:05:27 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Kris Kennaway Cc: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: Re: KAME/FreeBSD-stable merge References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > is there any reason why the (misnamed, but that's another issue) XBONEHACK > > option was eliminated during the recent KAME/FreeBSD-stable merge? (File > > /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, > > and we'd really like to see it merged into FreeBSD. > > I'm not sure. Perhaps itojun felt it wouldn't be necessary outside the > KAME snaps. If you guys are thinking of switching to use 4.1-R I'll add it > back. Kris, I'd be great if you could put it back in time for 4.1. Thanks, Lars PS: There's also the KAME kernel option MAX_GIF_NEST that should probably go into the "undocumented" section of LINT. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14: 8:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id D332E37BC13 for ; Mon, 17 Jul 2000 14:08:18 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA02373 for ; Mon, 17 Jul 2000 14:08:17 -0700 (PDT) Message-ID: <397375C1.3BA4E7B3@isi.edu> Date: Mon, 17 Jul 2000 14:08:17 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildkernel failure: netinet6/esp_core.c References: <39736E96.1AC0917B@isi.edu> <397372A6.3B9A4664@urx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: > I just finish cvsup'ing and have completed a buildworld and > buildkernel without any problems. Did you cvsup'ed such that you have > the crypto files since they are part of src-all now days. Of course this was the problem. Thanks, Kent! -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14: 8:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3104.mail.yahoo.com (web3104.mail.yahoo.com [204.71.202.189]) by hub.freebsd.org (Postfix) with SMTP id 77FA137BD81 for ; Mon, 17 Jul 2000 14:08:36 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717210828.7717.qmail@web3104.mail.yahoo.com> Received: from [150.159.224.8] by web3104.mail.yahoo.com; Mon, 17 Jul 2000 14:08:28 PDT Date: Mon, 17 Jul 2000 14:08:28 -0700 (PDT) From: Richard Stanaford Subject: Assembler probs and 4.1-RELEASE... To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone, I saw a message posted earlier regarding assembler problems while compiling BIOS code either during a kernel build or a Buildworld. I too am having such a problem. I was attempting to build a kernel and got some spam regarding invalid assembler instructions while dealing with a file in /tmp. I apologize for being vague, but it's currently hard to grab a dump of the output for the email. I figured I had run in to a bad install when I put 4.0-RELEASE on the system, so I CVSup'ed using RELENG_4 and built the world, which succeeded. The ensuing 'buildkernel' failed for the same reason. I thought that, perhaps, my NOVA conf file was wacky so I ran 'buildkernel' with GENERIC and it died too for the same reason. *Shrug* I'm at a loss. I initially did a binary only install of 4.0-RELEASE and have since added the additional distros such as the name pages and documentation *before* trying to go STABLE. I figure I somehow mangled something and am considering a full reinstallation but I am curious about the impending rollout of 4.1-RELEASE. Since I have not seen a code freeze initiated yet, is that still "a ways" off? If there are any suggestions to help me deal with the apparent assembler problem I would appreciate them before I wipe the install, which I'll probably do anyway because I planned out the filesystems wrong... doh! Thanks for the info, -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:15:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id A579637BC50 for ; Mon, 17 Jul 2000 14:15:44 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id GAA14188; Tue, 18 Jul 2000 06:15:37 +0900 (JST) To: snap-users@kame.net Cc: Lars Eggert , stable@freebsd.org, xbone@ISI.EDU In-reply-to: kris's message of Mon, 17 Jul 2000 14:00:16 MST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 2942) Re: KAME/FreeBSD-stable merge From: itojun@iijlab.net Date: Tue, 18 Jul 2000 06:15:37 +0900 Message-ID: <14186.963868537@coconut.itojun.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> is there any reason why the (misnamed, but that's another issue) XBONEHACK >> option was eliminated during the recent KAME/FreeBSD-stable merge? (File >> /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, >> and we'd really like to see it merged into FreeBSD. - it does not seem like a common option to me (it is just a quickhack for supporting special need at xbone project, which could have been handled as local patch), and it does not seem to me good for integrating into freebsd-current/releases - support issues (who handles questions about it? i don't want to) itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:19:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 8CCD337BD77 for ; Mon, 17 Jul 2000 14:19:10 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id QAA81028; Mon, 17 Jul 2000 16:19:55 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <003901bff034$bfb837b0$b8209fc0@campbellmithun.com> From: "Shawn Barnhart" To: "David Uhring" Cc: References: <00071715431400.01465@dave.uhring.com> Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Mon, 17 Jul 2000 16:19:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "David Uhring" | You might also check the cpu temperature during the compile. Using a K6-3/450, | my cpu cooler was getting quite hot to the touch during the make and would exit | with signal 10 or signal 11. I finally took to cover off the case and set up a | box fan to force additional air into the case. That's an option, too. Is the K6-3 same basic core as the original K6? FWIW I just put a new fan on this one when the old one started making strange noises. Last time I checked it was working OK. Now that you mention it, when I moved my FreeBSD machine to this box I also swapped out most of the accessories. Since my CPU fan uses one of those passthrough power connectors, the kind designed with all the resilliance of pair of $200 sunglasses, it wouldn't surprise me if the fan hasn't even been running, in which case I've probably cooked the CPU by now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:21:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gplsucks.org (work.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 2CD1137C066 for ; Mon, 17 Jul 2000 14:21:37 -0700 (PDT) (envelope-from bwoods2@uswest.net) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.10.2/8.10.2) with ESMTP id e6HLLbF22239; Mon, 17 Jul 2000 14:21:37 -0700 (PDT) Date: Mon, 17 Jul 2000 14:21:36 -0700 (PDT) From: William Woods To: Philippe Le Berre Cc: stable@FreeBSD.ORG Subject: Re: How to installworld remotely? In-Reply-To: <4.3.2.7.2.20000717130800.00c18840@212.129.1.43> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, Philippe, I have been doing remote installworlds for the last year and have had exactly 1 blow up on me and require me to go to the box....... On Mon, 17 Jul 2000, Philippe Le Berre wrote: > Hi, > > After being through the high numbers of emails on the new *build* > procedure, I still haven't see any hint on how to handle the make > installworld remotely. Can I do it without the shutdown? Can I remotely log > on *shutdown* system ? Do I have to fly to the box? > > Thanks for the help and all my excuses if the answer to this question was > in the numerous email on that topic. > > regards > > -philippe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:23:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 0C61A37BC39 for ; Mon, 17 Jul 2000 14:23:07 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15827600 invoked from network); 17 Jul 2000 21:23:01 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Jul 2000 21:23:01 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id XAA02645; Mon, 17 Jul 2000 23:23:00 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Mon, 17 Jul 2000 23:23:00 +0200 (CEST) To: "Shawn Barnhart" Cc: Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? References: <003401bfeffb$19083020$b8209fc0@campbellmithun.com> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 17 Jul 2000 23:22:58 +0200 In-Reply-To: "Shawn Barnhart"'s message of "Mon, 17 Jul 2000 09:27:11 -0500" Message-ID: Lines: 30 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Shawn Barnhart" writes: > My buildworld is failing, often in the same places, and always with a signal > 11, which I think is a segmentation violation (SIGSEGV). When I first > attempted buildworld it died right away. I rebooted the machine and it got > further, but died again with the same error. Subsequent attempts died > early; reboot and it dies later. > > I've recently moved this system to an Asus TXP4 motherboard with an AMD > K6-233 CPU and a single 128MB stick of PC100 SDRAM. No overclocking or > other hardware hackery is being used. The same machine had been running > (blush) Windows 2000 since March with little or no problems -- no problem > with lockups, blue screens, etc. > > The FreeBSD install I'm using had previously been running on a generic Dell > Pentium 200 and lived through a half-dozen buildworlds without breaking. > > Since I haven't seen a anyone else's world breaking this way, I'm assuming > that this is a hardware problem -- but what kind? Memory? I have a spare > Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start? > > FWIW, I cvsup'd numerous times throughout 16-July, in case I caught things > during a commit. try http://reality.sgi.com/cbrady/memtest86, that helped me. Cyrille. -- home:mailto:clefevre%no-spam@citeweb.net Supprimer "%no-spam" pour me repondre. work:mailto:Cyrille.Lefevre%no-spam@edf.fr Remove "%no-spam" to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:32: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 10F7A37B505 for ; Mon, 17 Jul 2000 14:32:05 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA05501; Mon, 17 Jul 2000 14:31:19 -0700 (PDT) Message-ID: <39737B26.6A03BBDE@isi.edu> Date: Mon, 17 Jul 2000 14:31:18 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 To: itojun@iijlab.net Cc: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: Re: (KAME-snap 2942) Re: KAME/FreeBSD-stable merge References: <14186.963868537@coconut.itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG itojun@iijlab.net wrote: > > >> is there any reason why the (misnamed, but that's another issue) XBONEHACK > >> option was eliminated during the recent KAME/FreeBSD-stable merge? (File > >> /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, > >> and we'd really like to see it merged into FreeBSD. > > - it does not seem like a common option to me (it is just a quickhack > for supporting special need at xbone project, which could have been > handled as local patch), and it does not seem to me good for > integrating into freebsd-current/releases The first xbone release has been downloaded a few hundred times in the first few days (I haven't looked at the logs since), and we've been on slashdot, so I'd say there is an audience out there. Also, it seems to me that there are plenty of options in FreeBSD dealing with enabling support for 3rd party software packages, or experimental code for people to play with - off the top of my head: USER_LDT, XSERVER, NULL, PORTAL, UMAP, UNION, PPS_SYNC, ... The xbone switch falls in the same category. > - support issues (who handles questions about it? i don't want to) We will. Please add a comment saying that questions should be sent to xbone@isi.edu. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:32:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3102.mail.yahoo.com (web3102.mail.yahoo.com [204.71.202.187]) by hub.freebsd.org (Postfix) with SMTP id 69CFF37B525 for ; Mon, 17 Jul 2000 14:32:08 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Received: from [150.159.224.8] by web3102.mail.yahoo.com; Mon, 17 Jul 2000 14:32:03 PDT Date: Mon, 17 Jul 2000 14:32:03 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: obrien@FreeBSD.ORG, Keith Mackay Cc: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- David O'Brien wrote: > On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote: > > Is there a known issue in bioscall.s? > > Yes, it has been documented all over the place in this mailing list. > It is also documented in /usr/src/UPDATING. > > You should review the expectations of running -STABLE and consider if you > are better off just sticking with the released product. I have looked at both .. ftp://ftp.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING ftp://cvsup2.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING And I see nothing regarding bioscall.s. If it's not much bother (I have to wonder given the tone of your response) please indicate where this has been documented. Thank you, -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:33:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 07F0A37B529 for ; Mon, 17 Jul 2000 14:33:52 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id GAA14512; Tue, 18 Jul 2000 06:33:50 +0900 (JST) To: snap-users@kame.net Cc: stable@freebsd.org, xbone@ISI.EDU In-reply-to: larse's message of Mon, 17 Jul 2000 14:31:18 MST. <39737B26.6A03BBDE@isi.edu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 2945) Re: KAME/FreeBSD-stable merge From: itojun@iijlab.net Date: Tue, 18 Jul 2000 06:33:50 +0900 Message-ID: <14510.963869630@coconut.itojun.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> - it does not seem like a common option to me (it is just a quickhack >> for supporting special need at xbone project, which could have been >> handled as local patch), and it does not seem to me good for >> integrating into freebsd-current/releases >The first xbone release has been downloaded a few hundred times in the >first few days (I haven't looked at the logs since), and we've been on >slashdot, so I'd say there is an audience out there. > >Also, it seems to me that there are plenty of options in FreeBSD dealing >with enabling support for 3rd party software packages, or experimental code >for people to play with - off the top of my head: USER_LDT, XSERVER, NULL, >PORTAL, UMAP, UNION, PPS_SYNC, ... The xbone switch falls in the same >category. do you have xbone userland tool in freebsd master repository? i believed not. xserver is officially supported by freebsd and userland tools are in the tree. the situation looks different for me. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:34:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C64E037B53D for ; Mon, 17 Jul 2000 14:34:34 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA09105; Mon, 17 Jul 2000 14:34:32 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id OAA73569; Mon, 17 Jul 2000 14:33:37 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000715132554.A31976@mashed.turnip.org.uk> Date: Mon, 17 Jul 2000 14:33:37 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Jonathan Vaughan Subject: RE: installworld failure (sys/boot/mbr) Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jul-00 Jonathan Vaughan wrote: > I have a problem updating to 4.0-STABLE from 4.0-STABLE as of a couple > of weeks ago. > > I did a make buildworld, then buildkernel and installkenrel. > > The installworld fails at this point: > > chown -R root:wheel /usr/share/zoneinfo/* > ===> sys > ===> sys/boot > ===> sys/boot/ficl > ===> sys/boot/i386 > ===> sys/boot/i386/mbr > install -c -o root -g wheel -m 444 mbr /boot > install: mbr: No such file or directory > *** Error code 71 > Stop in /usr/src/sys/boot/i386/mbr. > *** Error code 1 > > > The "mbr" file indeed does not exist in /usr/src/sys/boot/i386/mbr. > It is however present in /usr/obj/usr/src/sys/boot/i386/mbr. That is the right place for it to be, I don't know why things are out of sync for you. How are you running installworld? (i.e., what is the exact command line, etc.) > Is there a workaround for this? I haven't seen this before. > -- > Jonathan Vaughan > jonathan@turnip.org.uk > PGP Key ID: 0x0AF58107 > http://home.clara.net/turnip/pgp.txt | jon@pgpkey.turnip.org.uk | keyservers -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:34:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 4E8F537B53D for ; Mon, 17 Jul 2000 14:34:53 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id OAA00204; Mon, 17 Jul 2000 14:34:52 -0700 Message-ID: <39737C0E.253A29A9@urx.com> Date: Mon, 17 Jul 2000 14:35:10 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Stanaford Cc: stable@FreeBSD.ORG Subject: Re: Assembler probs and 4.1-RELEASE... References: <20000717210828.7717.qmail@web3104.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stanaford wrote: > > Hello everyone, > > I saw a message posted earlier regarding assembler problems while compiling > BIOS code either during a kernel build or a Buildworld. I too am having such a > problem. All you have to do is follow the buildworld, buildkernel, installkernel, and etc. sequence. If you had been following stable like a good boy you would have seen the 1000's of messages about this. On 7/7 O'Brien changed the binutils and the way you make your world and your kernel changed at that moment. You can't expect to cvsup and do the config, make depend, and etc sequence. I just finished cvsuping and have done a buildworld and buildkernel. What is there works. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:38:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id A29AD37B55F for ; Mon, 17 Jul 2000 14:38:22 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA06377; Mon, 17 Jul 2000 14:38:11 -0700 (PDT) Message-ID: <39737CC3.3F02D950@isi.edu> Date: Mon, 17 Jul 2000 14:38:11 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 To: itojun@iijlab.net Cc: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: Re: (KAME-snap 2945) Re: KAME/FreeBSD-stable merge References: <14510.963869630@coconut.itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG itojun@iijlab.net wrote: > > >> - it does not seem like a common option to me (it is just a quickhack > >> for supporting special need at xbone project, which could have been > >> handled as local patch), and it does not seem to me good for > >> integrating into freebsd-current/releases > >The first xbone release has been downloaded a few hundred times in the > >first few days (I haven't looked at the logs since), and we've been on > >slashdot, so I'd say there is an audience out there. > > > >Also, it seems to me that there are plenty of options in FreeBSD dealing > >with enabling support for 3rd party software packages, or experimental code > >for people to play with - off the top of my head: USER_LDT, XSERVER, NULL, > >PORTAL, UMAP, UNION, PPS_SYNC, ... The xbone switch falls in the same > >category. > > do you have xbone userland tool in freebsd master repository? > i believed not. xserver is officially supported by freebsd and > userland tools are in the tree. the situation looks different for me. The xbone port has been submitted to the ports maintainers since 3/20/00. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:38:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7AE6737B637; Mon, 17 Jul 2000 14:38:25 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13EIal-000Pyz-00; Mon, 17 Jul 2000 21:38:24 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA78367; Mon, 17 Jul 2000 23:38:23 +0200 (CEST) (envelope-from wkb) Date: Mon, 17 Jul 2000 23:38:23 +0200 From: Wilko Bulte To: Richard Stanaford Cc: obrien@freebsd.org, Keith Mackay , stable@freebsd.org Subject: Re: bioscall.s Message-ID: <20000717233823.B78153@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000717213203.7240.qmail@web3102.mail.yahoo.com>; from rsstan@yahoo.com on Mon, Jul 17, 2000 at 02:32:03PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 02:32:03PM -0700, Richard Stanaford wrote: > --- David O'Brien wrote: > > On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote: > > > Is there a known issue in bioscall.s? > > > > Yes, it has been documented all over the place in this mailing list. > > It is also documented in /usr/src/UPDATING. > > > > You should review the expectations of running -STABLE and consider if you > > are better off just sticking with the released product. > > > I have looked at both .. > > ftp://ftp.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > ftp://cvsup2.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > > And I see nothing regarding bioscall.s. If it's not much bother (I have to > wonder given the tone of your response) please indicate where this has been > documented. This is it, altough it does not mention bioscall.s explicitly: 20000706: Binutils were updated. In order to build a kernel after this date, you must follow the updating proceedure for building kernels exactly as presented here. You may be able to get away with doing it the old way, but if it breaks, make sure that you've tried the "To build a kernel" section with a fresh /usr/obj first. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:43: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DAEFB37B585; Mon, 17 Jul 2000 14:43:01 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA09423; Mon, 17 Jul 2000 14:43:00 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id OAA73621; Mon, 17 Jul 2000 14:42:05 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000717200844.I38656@lucifer.bart.nl> Date: Mon, 17 Jul 2000 14:42:04 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Jeroen Ruigrok van der Werven Subject: Re: bootdisk problems/md related Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG, phk@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Jeroen Ruigrok van der Werven wrote: > -On [20000717 20:05], John Baldwin (jhb@freebsd.org) wrote: >>What exact error are you talking about? The md1 fatal error? > > The one I posted earlier on in this thread. md related. Well, I don't see it at the moment, but I assume you mean 'FATAL: can't open md1' or some such. >>I _know_ that is fixed in 5.0 and 4.x. If you have some other >>error, let me know. > > Well, it isn't fixed for my boxen with the disks of the 15th. revision 1.117.2.2 date: 2000/07/05 07:20:23; author: jkh; state: Exp; lines: +5 -1 MFC: ignore memory disks What is the version of your devices.c in src/release/sysinstall? Note that 4.1-RC1 doesn't suffer from this problem. I suspect your sources are out of date or have a stick tag. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:43:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 7B7AE37B74E for ; Mon, 17 Jul 2000 14:43:22 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with ESMTP id OAA25015; Mon, 17 Jul 2000 14:43:21 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id OAA01388; Mon, 17 Jul 2000 14:43:21 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id RAA07628; Mon, 17 Jul 2000 17:43:21 -0400 (EDT) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14707.32248.146185.256812@hip186.ch.intel.com> Date: Mon, 17 Jul 2000 14:43:20 -0700 (MST) To: Richard Stanaford Cc: stable@freebsd.org Subject: Re: bioscall.s In-Reply-To: <20000717213203.7240.qmail@web3102.mail.yahoo.com> References: <20000717213203.7240.qmail@web3102.mail.yahoo.com> X-Mailer: VM 6.75 under Emacs 20.6.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Monday, July 17, Richard Stanaford wrote: ] > > I have looked at both .. > > ftp://ftp.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > ftp://cvsup2.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > > And I see nothing regarding bioscall.s. If it's not much bother (I have to > wonder given the tone of your response) please indicate where this has been > documented. Actually, without CVSUP'ing the sources or whatever, the best way to look at "up to date" sources (IMO) is the CVS repos. web interface. http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING Click on the link for the version branded RELENG_4 to get -STABLE's most recent copy: http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING?rev=1.73.2.8 The section on date 20000706 says it all (pretty much). There's nothing specifically mentioning bioscall.s -BUT- with the binutils update (meaning assembler, linker, blah blah blah) there had to be changes made to it. Without an updated "binutils" you can't assemble the file. The "buildkernel" target takes care of these sorts of wierd dependencies that crop up from time to time. The "tone" comes from frustration at what transpired with the binutils update into -STABLE and the whole "buildkernel" discussion. Look back into the mailing list archives for "buildkernel" and you'll find a whole huge thread about it. The developers just want people who "track -stable" to "read -stable" ... -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:44:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.utfors.se (mail.utfors.se [195.58.103.125]) by hub.freebsd.org (Postfix) with ESMTP id 3272137B57F for ; Mon, 17 Jul 2000 14:44:47 -0700 (PDT) (envelope-from watchman@ludd.luth.se) Received: from ludd.luth.se (md46928fb.utfors.se [212.105.40.251]) by mail.utfors.se (8.8.8/8.8.8) with ESMTP id XAA22263 for ; Mon, 17 Jul 2000 23:44:44 +0200 (MET DST) Message-ID: <39737E4B.C95A5705@ludd.luth.se> Date: Mon, 17 Jul 2000 23:44:43 +0200 From: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Organization: Acne X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en-US MIME-Version: 1.0 To: FreeBSD-Stable Subject: Re: Parallel kernel make Was Re: kernel.debug (was Re: HEADS UP! Always use the 'make buildkernel' target to make your kernels) References: <396F4463.978AE0DA@newsguy.com> <3971FA68.3A3C5F17@ludd.luth.se> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! (To Kris et al) No, I didn't expect parallel make of the kernel to give me problems. Cyrille asked if it was possible, I hadn't done it up til now, and I simply verified that it did work. No surprises. Yes, I'm fully aware that make -j4 means that more resources are being allocated that a simple single thread make. I felt that SETI was being slowed down more that my normal make -j(6-8) buildworld usually does. But, this is what I felt, meaning it's not a very strong proof of this actually reflecting the behaviour. Yes, I have a SMP system and do parallel builds on a regular basis. The Handbook suggests -j flags in the area of 6 to 8. I've done some tests and we are talking a few minutes difference between 4 to 8, where a build takes about 70 mins. The total time should drop somewhat on Thursday when I get the new CPU:s (party! :-) As I said, it was for kicks - and to answer Cyrilles question. -- Cheers! Joachim - Alltid i harmonisk svängning --- FairLight ------ FairLight ------ FairLight ------ FairLight --- Joachim Strömbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47 Web: http://www.ludd.luth.se/~watchman --------------- Spamfodder: regeringen@regeringen.se --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:45:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 7C96237B595; Mon, 17 Jul 2000 14:45:07 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 844909B1C; Mon, 17 Jul 2000 17:45:06 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 78D40BA11; Mon, 17 Jul 2000 17:45:06 -0400 (EDT) Date: Mon, 17 Jul 2000 17:45:06 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Richard Stanaford Cc: obrien@FreeBSD.ORG, Keith Mackay , stable@FreeBSD.ORG Subject: Re: bioscall.s In-Reply-To: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Richard Stanaford wrote: > --- David O'Brien wrote: > > On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote: > > > Is there a known issue in bioscall.s? > > > > Yes, it has been documented all over the place in this mailing list. > > It is also documented in /usr/src/UPDATING. > > > > You should review the expectations of running -STABLE and consider if you > > are better off just sticking with the released product. > > > I have looked at both .. > > ftp://ftp.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > ftp://cvsup2.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > > And I see nothing regarding bioscall.s. If it's not much bother (I have to > wonder given the tone of your response) please indicate where this has been > documented. > Once again, see the 20000706 and "To build a kernel" entries in UPDATING. It doesn't get much clearer that that. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:46:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 52B1137B5D1 for ; Mon, 17 Jul 2000 14:46:29 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA09560; Mon, 17 Jul 2000 14:46:27 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id OAA73659; Mon, 17 Jul 2000 14:45:32 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000717210828.7717.qmail@web3104.mail.yahoo.com> Date: Mon, 17 Jul 2000 14:45:31 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Richard Stanaford Subject: RE: Assembler probs and 4.1-RELEASE... Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Richard Stanaford wrote: > Hello everyone, cvsup, then make buildworld, and then make buildkernel. It will work. Don't cvsup between the buildworld and the buildkernel for the best results. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:47:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id DD44837BB34; Mon, 17 Jul 2000 14:47:25 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA92147; Mon, 17 Jul 2000 17:47:49 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 17 Jul 2000 17:47:49 -0400 (EDT) From: Adam To: Kris Kennaway Cc: stable@FreeBSD.org Subject: Re: Problem with installworld In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Kris Kennaway wrote: >On Mon, 17 Jul 2000, Adam wrote: > >> 4.0 cd subscription: $25 >> Time spent installing: 10-15 min >> cvsup to -stable: ~10-15 min >> buildworld: 1.5 hours >> Reading UPDATING: free >> re-reading email to check for commits: 5 min >> cvsup again just in case: 5 min >> a working build/installworld: priceless >> >> >> Did I miss doing something? I'm in the USA but make.conf says I'm not. >> I didn't tell it that, so something is jumping the gun. > >Sysinstall had a bug which would put the wrong value in make.conf..it's >fixed in later editions. Is this not worth a note in UPDATING? Theres *only* four entries in there past 4.0-release, I dont think its asking too much to be read :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:54:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from earth.isni.net (earth.isni.net [208.160.180.2]) by hub.freebsd.org (Postfix) with ESMTP id 8B2B337B524 for ; Mon, 17 Jul 2000 14:54:11 -0700 (PDT) (envelope-from jeff@isni.net) Received: from webdev.isni.net (webdev.isni.net [208.160.180.27]) by earth.isni.net (8.10.2/8.10.2) with ESMTP id e6HLs8I23689 for ; Mon, 17 Jul 2000 17:54:09 -0400 (EDT) Message-Id: <4.3.2.7.0.20000717174939.00aec100@127.0.0.1> X-Sender: jeff/mail.isni.net@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 17 Jul 2000 17:53:14 -0400 To: freebsd-stable@freebsd.org From: Jeff Palmer Subject: failure in 4.1-RC Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all. today a supped 4.1 on two totally seperate servers. Both machines give the exact same error when building the kernel. One machine is a standard (unedited) GENERIC kernel The other machine is modified for smp. both machines fail today with: cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s /tmp/ccZ13259.s: Assembler messages: /tmp/ccZ13259.s:796: Error: operands given don't match any known 386 instruction /tmp/ccZ13259.s:861: Error: operands given don't match any known 386 instruction *** Error code 1 Stop in /usr/src/sys/compile/BACI. Please CC: me directly with any replies. Thanks Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:55: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8C76F37B569; Mon, 17 Jul 2000 14:54:56 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA09936; Mon, 17 Jul 2000 14:54:55 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id OAA73745; Mon, 17 Jul 2000 14:54:00 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Date: Mon, 17 Jul 2000 14:53:59 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Richard Stanaford Subject: Re: bioscall.s Cc: stable@FreeBSD.ORG, Keith Mackay , obrien@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Richard Stanaford wrote: > --- David O'Brien wrote: >> On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote: >> > Is there a known issue in bioscall.s? >> >> Yes, it has been documented all over the place in this mailing list. >> It is also documented in /usr/src/UPDATING. >> >> You should review the expectations of running -STABLE and consider if you >> are better off just sticking with the released product. > > > I have looked at both .. > > ftp://ftp.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > ftp://cvsup2.freebsd.org/pub/FreeBSD/branches/4.0-stable/src/UPDATING > > And I see nothing regarding bioscall.s. If it's not much bother (I have to > wonder given the tone of your response) please indicate where this has been > documented. Mailing list archives. You would have seen literally 50+ messages about assembler errors in the past month if you had been reading this list, which is generally mentioned as a "requirement" of running -stable. As for UPDATING, the relevant entry is that the binutils (which includes the assembler) were upgraded: 20000706: Binutils were updated. In order to build a kernel after this date, you must follow the updating proceedure for building kernels exactly as presented here. You may be able to get away with doing it the old way, but if it breaks, make sure that you've tried the "To build a kernel" section with a fresh /usr/obj first. As you can see if you _read_ this entry, you need to follow "the updating proceedure [sic] for building kernels as presented here": To build a kernel ----------------- cd /usr/src # If you have not already done so, please buildworld here # You will also need to update your config file to 4.0. Usually # people tend to start with GENERIC from 4.0 and hack from there. make buildkernel KERNEL= make installkernel KERNEL= # Verify that the new kernel works, it will be installed as # /YOUR_KERNEL_HERE chflags noschg /kernel chflags noschg /YOUR_KERNEL_HERE mv /kernel /kernel.old mv /YOUR_KERNEL_HERE /kernel chflags schg /kernel The reason some people are rather short over this issue is that this has already been discussed about 50 times on this mailing list in the past month, and after a while answering the same question 50 times gets old. > Thank you, > -Richard -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 14:55:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lychee.itojun.org (dialup1.itojun.org [210.160.95.107]) by hub.freebsd.org (Postfix) with ESMTP id F1FF837B590 for ; Mon, 17 Jul 2000 14:55:12 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost [127.0.0.1]) by itojun.org (8.10.0/3.7W) with ESMTP id e6HLrHa08532; Tue, 18 Jul 2000 06:53:17 +0900 (JST) Message-Id: <200007172153.e6HLrHa08532@itojun.org> To: snap-users@kame.net Cc: stable@freebsd.org, xbone@ISI.EDU In-reply-to: larse's message of Mon, 17 Jul 2000 14:38:11 MST. <39737CC3.3F02D950@isi.edu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 2947) Re: KAME/FreeBSD-stable merge From: Jun-ichiro itojun Hagino Date: Tue, 18 Jul 2000 06:53:17 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> do you have xbone userland tool in freebsd master repository? >> i believed not. xserver is officially supported by freebsd and >> userland tools are in the tree. the situation looks different for me. >The xbone port has been submitted to the ports maintainers since 3/20/00. hmm, up to kris i'd say. normally, such kind of port do require special patch against kernel. i still don't understand why you try this hard to avoid including diffs into your xbone package. if you include diff into your package the problem is solved. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15: 6:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3104.mail.yahoo.com (web3104.mail.yahoo.com [204.71.202.189]) by hub.freebsd.org (Postfix) with SMTP id 27BCA37B74E for ; Mon, 17 Jul 2000 15:06:28 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717220624.14083.qmail@web3104.mail.yahoo.com> Received: from [150.159.224.8] by web3104.mail.yahoo.com; Mon, 17 Jul 2000 15:06:24 PDT Date: Mon, 17 Jul 2000 15:06:24 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- "Chris D. Faulhaber" wrote: > On Mon, 17 Jul 2000, Richard Stanaford wrote: > Once again, see the 20000706 and "To build a kernel" entries in > UPDATING. It doesn't get much clearer that that. As I indicated in a separate message. The kernel build fails after a CVSup and successful buildworld. The method used was buildkernel KERNEL="NOVA". In terms of "clarity," perhaps something was missed. I have not seen anything of consequence to binutils committed to STABLE within the last two days, however it is possible something got trashed during my last update or the src tree was somehow fluxed. I understand that fetch.c was missing a couple days ago. Upon the advice of John Baldwin I'll try another CVSup tonight. My appreciation to him for taking the time to offer a helpful suggestion and not just point out a deficiency in procedure. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15: 6:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 50DFA37B618 for ; Mon, 17 Jul 2000 15:06:07 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA63442; Mon, 17 Jul 2000 15:05:55 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 15:05:55 -0700 From: "David O'Brien" To: Richard Stanaford Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s Message-ID: <20000717150555.A63417@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000717213203.7240.qmail@web3102.mail.yahoo.com>; from rsstan@yahoo.com on Mon, Jul 17, 2000 at 02:32:03PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 02:32:03PM -0700, Richard Stanaford wrote: > > Yes, it has been documented all over the place in this mailing list. > > It is also documented in /usr/src/UPDATING. > > > > You should review the expectations of running -STABLE and consider if you > > are better off just sticking with the released product. ..snip.. > And I see nothing regarding bioscall.s. In the 50+ messages on this topic in this mailing list in the past _2_ weeks, some of them _have_ mentioned bioscall.s explicitly. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:18:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id CA85137B564 for ; Mon, 17 Jul 2000 15:18:19 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id PAA00341; Mon, 17 Jul 2000 15:18:17 -0700 Message-ID: <3973863B.7F108BE2@urx.com> Date: Mon, 17 Jul 2000 15:18:35 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Stanaford Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s References: <20000717220624.14083.qmail@web3104.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stanaford wrote: > > --- "Chris D. Faulhaber" wrote: > > On Mon, 17 Jul 2000, Richard Stanaford wrote: > > > Once again, see the 20000706 and "To build a kernel" entries in > > UPDATING. It doesn't get much clearer that that. > > As I indicated in a separate message. The kernel build fails after a CVSup and > successful buildworld. The method used was buildkernel KERNEL="NOVA". In > terms of "clarity," perhaps something was missed. You need a config file called NOVA. > > I have not seen anything of consequence to binutils committed to STABLE within > the last two days, however it is possible something got trashed during my last > update or the src tree was somehow fluxed. I understand that fetch.c was > missing a couple days ago. There were many going back to 7/7 when O'Brien updated them. See dwarf1.c won't build and **HEADS UP** for the earliest ones. > > Upon the advice of John Baldwin I'll try another CVSup tonight. My > appreciation to him for taking the time to offer a helpful suggestion and not > just point out a deficiency in procedure. I finish doing a buildworld, buildkernel, installkernel, installworld a short time ago. I am running that system right now. It was cvsuped around 1900GMT (12 noon PDT). FWIW, it still says 4.1-RC. Kent > > -Richard > > __________________________________________________ > Do You Yahoo!? > Get Yahoo! Mail – Free email you can access from anywhere! > http://mail.yahoo.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:19:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 6E19137B55B for ; Mon, 17 Jul 2000 15:19:39 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA63600; Mon, 17 Jul 2000 15:19:36 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 15:19:35 -0700 From: "David O'Brien" To: Richard Stanaford Cc: stable@freebsd.org Subject: Re: bioscall.s Message-ID: <20000717151935.A63451@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000717220624.14083.qmail@web3104.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000717220624.14083.qmail@web3104.mail.yahoo.com>; from rsstan@yahoo.com on Mon, Jul 17, 2000 at 03:06:24PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 03:06:24PM -0700, Richard Stanaford wrote: > As I indicated in a separate message. The kernel build fails after a > CVSup and successful buildworld. Does ``as -v'' say "2.10"? -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:20:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 16DA037B57B for ; Mon, 17 Jul 2000 15:20:54 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id PAA00347; Mon, 17 Jul 2000 15:20:33 -0700 Message-ID: <397386C4.BFCA8655@urx.com> Date: Mon, 17 Jul 2000 15:20:52 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Palmer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: failure in 4.1-RC References: <4.3.2.7.0.20000717174939.00aec100@127.0.0.1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It sounds like you didn't do a buildkerne KERNEL=GENRIC and installkernel KERNEL=GENERIC. Kent Jeff Palmer wrote: > > Hello all. > > today a supped 4.1 on two totally seperate servers. > > Both machines give the exact same error when building the kernel. > > One machine is a standard (unedited) GENERIC kernel > The other machine is modified for smp. > > both machines fail today with: > > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. > -I../../../include -D_KERNEL -include opt_global.h > -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s > /tmp/ccZ13259.s: Assembler messages: > /tmp/ccZ13259.s:796: Error: operands given don't match any known 386 > instruction > /tmp/ccZ13259.s:861: Error: operands given don't match any known 386 > instruction > *** Error code 1 > > Stop in /usr/src/sys/compile/BACI. > > Please CC: me directly with any replies. > Thanks > > Jeff > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:22: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2C2C537B57B for ; Mon, 17 Jul 2000 15:21:58 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA63613; Mon, 17 Jul 2000 15:21:37 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 15:21:37 -0700 From: "David O'Brien" To: Jeff Palmer Cc: freebsd-stable@freebsd.org Subject: Re: failure in 4.1-RC Message-ID: <20000717152137.B63451@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <4.3.2.7.0.20000717174939.00aec100@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.2.7.0.20000717174939.00aec100@127.0.0.1>; from jeff@isni.net on Mon, Jul 17, 2000 at 05:53:14PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 05:53:14PM -0400, Jeff Palmer wrote: > today a supped 4.1 on two totally seperate servers. Didn't we just go thru this an hour ago.... <*SIGH*> > both machines fail today with: ..snip.. > /tmp/ccZ13259.s: Assembler messages: > /tmp/ccZ13259.s:796: Error: operands given don't match any known 386 Yes, it has been documented all over the place in this mailing list. It is also documented in /usr/src/UPDATING. You should review the expectations of running -STABLE and consider if you aren't better off just sticking with the released product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:22:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 64F2037B5C4; Mon, 17 Jul 2000 15:22:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA82568; Mon, 17 Jul 2000 16:22:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA65896; Mon, 17 Jul 2000 16:22:30 -0600 (MDT) Message-Id: <200007172222.QAA65896@harmony.village.org> To: Richard Stanaford Subject: Re: bioscall.s Cc: obrien@FreeBSD.ORG, Keith Mackay , stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 14:32:03 PDT." <20000717213203.7240.qmail@web3102.mail.yahoo.com> References: <20000717213203.7240.qmail@web3102.mail.yahoo.com> Date: Mon, 17 Jul 2000 16:22:30 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000717213203.7240.qmail@web3102.mail.yahoo.com> Richard Stanaford writes: : And I see nothing regarding bioscall.s. If it's not much bother (I have to : wonder given the tone of your response) please indicate where this has been : documented. From -stable's UPDATING: 20000706: Binutils were updated. In order to build a kernel after this date, you must follow the updating proceedure for building kernels exactly as presented here. You may be able to get away with doing it the old way, but if it breaks, make sure that you've tried the "To build a kernel" section with a fresh /usr/obj first. Sure, it doesn't say anything about bioscall.s, but it does tell us that you aren't following the recommended proceedures. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:23:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E0C6637B83E for ; Mon, 17 Jul 2000 15:23:35 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA11088; Mon, 17 Jul 2000 15:23:33 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.9.3/8.9.3) id PAA73947; Mon, 17 Jul 2000 15:22:38 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4.3.2.7.0.20000717174939.00aec100@127.0.0.1> Date: Mon, 17 Jul 2000 15:22:38 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Jeff Palmer Subject: RE: failure in 4.1-RC Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jul-00 Jeff Palmer wrote: > Hello all. > > > today a supped 4.1 on two totally seperate servers. > > Both machines give the exact same error when building the kernel. Please build a new world and then use the make buildkernel and make installkernel targets to build your new kernel. See /usr/src/UPDATING, specifically the 20000706 entry for details. Also, if you plan to run -stable, please subscribe to and keep up with the freebsd-stable mailing list. Thanks. > Thanks -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:30: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5A19B37B5E5; Mon, 17 Jul 2000 15:30:00 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA70656; Mon, 17 Jul 2000 15:29:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 15:29:59 -0700 (PDT) From: Kris Kennaway To: Adam Cc: stable@FreeBSD.org Subject: Re: Problem with installworld In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Adam wrote: > Is this not worth a note in UPDATING? Theres *only* four entries in there > past 4.0-release, I dont think its asking too much to be read :) Actually it's not the kind of thing that goes into UPDATING: namely hoops you have to jump through to update your system. This is an erratum and should be listed on http://www.freebsd.org/releases/4.0R/errata.html, except no-one notes bug fixes in the errata for some reason. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:31:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3104.mail.yahoo.com (web3104.mail.yahoo.com [204.71.202.189]) by hub.freebsd.org (Postfix) with SMTP id 8573C37B7EB for ; Mon, 17 Jul 2000 15:31:28 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717223126.16471.qmail@web3104.mail.yahoo.com> Received: from [150.159.224.8] by web3104.mail.yahoo.com; Mon, 17 Jul 2000 15:31:26 PDT Date: Mon, 17 Jul 2000 15:31:26 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: kstewart@urx.com Cc: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Kent Stewart wrote: > > > Richard Stanaford wrote: > > > > --- "Chris D. Faulhaber" wrote: > > > On Mon, 17 Jul 2000, Richard Stanaford wrote: > > > > > Once again, see the 20000706 and "To build a kernel" entries in > > > UPDATING. It doesn't get much clearer that that. > > > > As I indicated in a separate message. The kernel build fails after a CVSup > and > > successful buildworld. The method used was buildkernel KERNEL="NOVA". In > > terms of "clarity," perhaps something was missed. > > You need a config file called NOVA. > I do have a config file named NOVA.. /usr/src/i386/conf/NOVA... hacked from GENERIC. My most recent CVSup was yesterday at about 1900 GMT. Apparently someone else is having the same problem I am and I have reproduced it using the "old" and "new-binutils-friendly" methods... Replace BACI with NOVA for the included dump. cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s /tmp/ccZ13259.s: Assembler messages: /tmp/ccZ13259.s:796: Error: operands given don't match any known 386 instruction /tmp/ccZ13259.s:861: Error: operands given don't match any known 386 instruction *** Error code 1 Stop in /usr/src/sys/compile/BACI. __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:38: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3105.mail.yahoo.com (web3105.mail.yahoo.com [204.71.202.190]) by hub.freebsd.org (Postfix) with SMTP id 9374437B60C for ; Mon, 17 Jul 2000 15:37:52 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717223751.3846.qmail@web3105.mail.yahoo.com> Received: from [150.159.224.8] by web3105.mail.yahoo.com; Mon, 17 Jul 2000 15:37:51 PDT Date: Mon, 17 Jul 2000 15:37:51 -0700 (PDT) From: Richard Stanaford Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- David Uhring wrote: > On Mon, 17 Jul 2000, Walter Campbell wrote: > You might also check the cpu temperature during the compile. Using a > K6-3/450, > my cpu cooler was getting quite hot to the touch during the make and would > exit > with signal 10 or signal 11. I finally took to cover off the case and set up > a > box fan to force additional air into the case. Heh... It's a amazing what a 19-inch Patton steel-bladed air circulator can do for a hard working 486/DX4/100. *snicker* Not a bit of dust on the cards. :-) Okay.. maybe that's overkill and I did have to make sure the PC didn't get blown over... but you gotta use what you've got! lol. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:44:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3102.mail.yahoo.com (web3102.mail.yahoo.com [204.71.202.187]) by hub.freebsd.org (Postfix) with SMTP id 3B4C937B5D9 for ; Mon, 17 Jul 2000 15:44:03 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717224359.15301.qmail@web3102.mail.yahoo.com> Received: from [150.159.224.8] by web3102.mail.yahoo.com; Mon, 17 Jul 2000 15:43:59 PDT Date: Mon, 17 Jul 2000 15:43:59 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- David O'Brien wrote: > On Mon, Jul 17, 2000 at 03:06:24PM -0700, Richard Stanaford wrote: > > As I indicated in a separate message. The kernel build fails after a > > CVSup and successful buildworld. > > Does ``as -v'' say "2.10"? Why wouldn't it if 'make buildworld' was successful? I'll have to look tonight and post accordingly. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:52:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3104.mail.yahoo.com (web3104.mail.yahoo.com [204.71.202.189]) by hub.freebsd.org (Postfix) with SMTP id C5D0337B564 for ; Mon, 17 Jul 2000 15:52:51 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000717225251.18551.qmail@web3104.mail.yahoo.com> Received: from [150.159.224.8] by web3104.mail.yahoo.com; Mon, 17 Jul 2000 15:52:51 PDT Date: Mon, 17 Jul 2000 15:52:51 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: Richard Stanaford , stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Richard Stanaford wrote: > > --- David O'Brien wrote: > > On Mon, Jul 17, 2000 at 03:06:24PM -0700, Richard Stanaford wrote: > > > As I indicated in a separate message. The kernel build fails after a > > > CVSup and successful buildworld. > > > > Does ``as -v'' say "2.10"? > > > Why wouldn't it if 'make buildworld' was successful? I'll have to look > tonight > and post accordingly. > Actually I should revise that. You should now not install the new binaries until you have built and installed a new kernel, which doesn't work because you suppose I have something other than Version 2.10 of 'as'. Correct? Right or wrong I have the version that was comitted to 4.0-RELEASE. I'll look tonight to be sure. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 15:59:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 4E82B37B564 for ; Mon, 17 Jul 2000 15:59:13 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id PAA00505; Mon, 17 Jul 2000 15:59:12 -0700 Message-ID: <39738FD2.B16ABA1B@urx.com> Date: Mon, 17 Jul 2000 15:59:30 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Stanaford Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s References: <20000717223126.16471.qmail@web3104.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stanaford wrote: > > --- Kent Stewart wrote: > > > > > > Richard Stanaford wrote: > > > > > > --- "Chris D. Faulhaber" wrote: > > > > On Mon, 17 Jul 2000, Richard Stanaford wrote: > > > > > > > Once again, see the 20000706 and "To build a kernel" entries in > > > > UPDATING. It doesn't get much clearer that that. > > > > > > As I indicated in a separate message. The kernel build fails after a CVSup > > and > > > successful buildworld. The method used was buildkernel KERNEL="NOVA". In > > > terms of "clarity," perhaps something was missed. > > > > You need a config file called NOVA. > > > > I do have a config file named NOVA.. /usr/src/i386/conf/NOVA... hacked from > GENERIC. My most recent CVSup was yesterday at about 1900 GMT. Apparently > someone else is having the same problem I am and I have reproduced it using the > "old" and "new-binutils-friendly" methods... The only difference between your effort on mine is I cvsup'ed 24 hours later than you did. I have also been following -stable since they started the massive changes on 7/7. I was one of the first people bit by the bioscall.s thing and Warner added the bit about buildkernel. Less than 15 minutes later, I was running a system based on O'Brien's modified /binutils. Since I was one of the first, it was said kindly. The kindness in the responses is developing an edge because of what seems like 100's of people not paying attention or doing any research and continue using the old way. There have been a lot of stuff changed in /etc that mergemaster has to take care of. I have been fighting getting email that FreeBSD.org will buy for several days on a new ISP and the cvs-committs are scattered over three systems and two emailers. I don't know what changed but my 3 hour old cvsup worked. I always thought Murphy picked on me. I have been doing the buildkernel religiously since 7/7 and perhaps, for a change, he passed it around :). I have 3 machines that I am using to follow stable's transition to 4.1. Only one goes down if there are problems. You won't see "as -v" = 2.10.0 unless you have done an installworld. That is probably why you are getting the message. Good luck, Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:24:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kingsqueak.org (cc737825-a.etntwn1.nj.home.com [24.3.202.115]) by hub.freebsd.org (Postfix) with ESMTP id 72E8437B729 for ; Mon, 17 Jul 2000 16:24:42 -0700 (PDT) (envelope-from drmoreau@kingsqueak.org) Received: by kingsqueak.org (Postfix, from userid 1001) id 23F5916E36; Mon, 17 Jul 2000 19:24:41 -0400 (EDT) Date: Mon, 17 Jul 2000 19:24:41 -0400 From: Chris To: Richard Stanaford Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Message-ID: <20000717192441.A44452@kingsqueak.org> Reply-To: Chris References: <20000717223751.3846.qmail@web3105.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <20000717223751.3846.qmail@web3105.mail.yahoo.com>; from rsstan@yahoo.com on Mon, Jul 17, 2000 at 03:37:51PM -0700 Organization: Earn $$$ install a web-cam in yer bathroom. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I like the AMD's, have a K6-3/450 here with a really heavy Alpha heatsink on it and a 27cfm bearing fan. Even with that fan... it just doesn't like make buildworld or building X without the case cover off though. Though it's not a small problem... it still performs well for me overall. My older K6/2 200 here can build all day no problem...the new ones just got really hot. I actually had to give up on fbsd for my work desktop because the cheapie fan on the K6/2 450 I have just wouldn't cut it, even with the case off and the thing would just plain reboot on any moderate sized builds. I just don't have the time at the office to mess with it and my workstation is a management station of sorts as well. On Mon, Jul 17, 2000 at 03:37:51PM -0700, Richard Stanaford wrote: > > --- David Uhring wrote: > > On Mon, 17 Jul 2000, Walter Campbell wrote: > > > You might also check the cpu temperature during the compile. Using a > > K6-3/450, > > my cpu cooler was getting quite hot to the touch during the make and would > > exit > > with signal 10 or signal 11. I finally took to cover off the case and set up > > a > > box fan to force additional air into the case. > > > Heh... It's a amazing what a 19-inch Patton steel-bladed air circulator can do > for a hard working 486/DX4/100. *snicker* Not a bit of dust on the cards. > :-) Okay.. maybe that's overkill and I did have to make sure the PC didn't get > blown over... but you gotta use what you've got! lol. > > -Richard > > __________________________________________________ > Do You Yahoo!? > Get Yahoo! Mail – Free email you can access from anywhere! > http://mail.yahoo.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---end quoted text--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:25:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id C4F5437B87B; Mon, 17 Jul 2000 16:25:48 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id QAA16817; Mon, 17 Jul 2000 16:25:46 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007172325.QAA16817@freeway.dcfinc.com> Subject: Re: Latest RELENG_4. In-Reply-To: from Kris Kennaway at "Jul 16, 0 03:24:56 pm" To: kris@FreeBSD.ORG (Kris Kennaway) Date: Mon, 17 Jul 2000 16:25:46 -0700 (MST) Cc: noor@comrax.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Kris Kennaway wrote: > On Sun, 16 Jul 2000, Chad R. Larson wrote: > >> As I recall, noor@comrax.com wrote: >>> What is the latest FreeBSD-STABLE release, and is it stable enough >>> for a productional system? >> >> Please remember that "STABLE" refers to the stability of the source >> tree, not of the resulting running system. That is, you should not >> see developmental work going on in -STABLE. > > Well, I claim this to be false: the targetted stability *is* of the > resulting product. Of course, we sometimes make mistakes - but if you > have *any* stability problems you should tell us!! Note that I didn't claim the -STABLE systems weren't stable. I just said that the original questioner seemed to have misunderstood the meaning of the tag. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:29:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id A3AE437B876 for ; Mon, 17 Jul 2000 16:29:43 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id QAA00059; Mon, 17 Jul 2000 16:29:41 -0700 Message-ID: <397396F7.5D68C3D6@urx.com> Date: Mon, 17 Jul 2000 16:29:59 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Chris Cc: Richard Stanaford , freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? References: <20000717223751.3846.qmail@web3105.mail.yahoo.com> <20000717192441.A44452@kingsqueak.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris wrote: > > I like the AMD's, have a K6-3/450 here with a really heavy Alpha > heatsink on it and a 27cfm bearing fan. Even with that fan... it just > doesn't like make buildworld or building X without the case cover off > though. Though it's not a small problem... it still performs well for me > overall. My older K6/2 200 here can build all day no problem...the new > ones just got really hot. I had a mid-tower with a similar problem. It had room for two supplemental fans. One in the front of the case and I added one above the PS. I had the one above the PS pulling in cool air and the cpu continued running 40oC or higher. I switched the direction so that it was pushing hot air out of the case and the temperature at the cpu dropped 12+oC. Kent > > I actually had to give up on fbsd for my work desktop because the > cheapie fan on the K6/2 450 I have just wouldn't cut it, even with the > case off and the thing would just plain reboot on any moderate sized > builds. I just don't have the time at the office to mess with it and my > workstation is a management station of sorts as well. > > On Mon, Jul 17, 2000 at 03:37:51PM -0700, Richard Stanaford wrote: > > > > --- David Uhring wrote: > > > On Mon, 17 Jul 2000, Walter Campbell wrote: > > > > > You might also check the cpu temperature during the compile. Using a > > > K6-3/450, > > > my cpu cooler was getting quite hot to the touch during the make and would > > > exit > > > with signal 10 or signal 11. I finally took to cover off the case and set up > > > a > > > box fan to force additional air into the case. > > > > > > Heh... It's a amazing what a 19-inch Patton steel-bladed air circulator can do > > for a hard working 486/DX4/100. *snicker* Not a bit of dust on the cards. > > :-) Okay.. maybe that's overkill and I did have to make sure the PC didn't get > > blown over... but you gotta use what you've got! lol. > > > > -Richard > > > > __________________________________________________ > > Do You Yahoo!? > > Get Yahoo! Mail – Free email you can access from anywhere! > > http://mail.yahoo.com/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > ---end quoted text--- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:32:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3467C37B786; Mon, 17 Jul 2000 16:32:53 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA79139; Mon, 17 Jul 2000 16:32:53 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Jul 2000 16:32:52 -0700 (PDT) From: Kris Kennaway To: "Chad R. Larson" Cc: noor@comrax.com, freebsd-stable@FreeBSD.ORG Subject: Re: Latest RELENG_4. In-Reply-To: <200007172325.QAA16817@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Chad R. Larson wrote: > As I recall, Kris Kennaway wrote: > > On Sun, 16 Jul 2000, Chad R. Larson wrote: > > > >> As I recall, noor@comrax.com wrote: > >>> What is the latest FreeBSD-STABLE release, and is it stable enough > >>> for a productional system? > >> > >> Please remember that "STABLE" refers to the stability of the source > >> tree, not of the resulting running system. That is, you should not > >> see developmental work going on in -STABLE. > > > > Well, I claim this to be false: the targetted stability *is* of the > > resulting product. Of course, we sometimes make mistakes - but if you > > have *any* stability problems you should tell us!! > > Note that I didn't claim the -STABLE systems weren't stable. I just > said that the original questioner seemed to have misunderstood the > meaning of the tag. And I was claiming the same about you :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:37:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 2A32337B74F; Mon, 17 Jul 2000 16:37:24 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 5EACE195F4; Mon, 17 Jul 2000 18:37:23 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id SAA35771; Mon, 17 Jul 2000 18:37:23 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Mon, 17 Jul 2000 18:37:23 -0500 From: "Jacques A. Vidrine" To: arnold Cc: freebsd-stable@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: buildworld kerberos5 broken? Message-ID: <20000717183723.E35672@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , arnold , freebsd-stable@FreeBSD.ORG, markm@FreeBSD.ORG References: <397103DB.2AB0CE48@linuxmail.org> <20000716130852.A53314@hamlet.nectar.com> <39733951.27C3715@linuxmail.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39733951.27C3715@linuxmail.org>; from arnee@linuxmail.org on Mon, Jul 17, 2000 at 09:50:25AM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 09:50:25AM -0700, arnold wrote: > hmmm, that's odd... if i can remember i had build my last stable (right after the > release date) and everything compiled fine with kerberos5. even -current (before > 4.0release), i believe i was compiling kerberos5 with no problems... then again i > could be wrong :-(. but, you're right something is going on here, for the past week... > until now over the weekend i have been trying to compile it and no luck. it looks to > me like krb.h is not in the -I path when compiling kerberos5. but i still don't > understand how i was able to build it before without kerberosIV dependency... hmmm! I didn't notice this breakage either, at first, apparently because the machines I did the build on already had Kerberos IV installed. -- Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:39:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cmailg4.svr.pol.co.uk (cmailg4.svr.pol.co.uk [195.92.195.174]) by hub.freebsd.org (Postfix) with ESMTP id 2F29137B720 for ; Mon, 17 Jul 2000 16:39:10 -0700 (PDT) (envelope-from jonathan@mashed.turnip.org.uk) Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk) by cmailg4.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13EKTc-0007lZ-00 for stable@freebsd.org; Tue, 18 Jul 2000 00:39:08 +0100 Received: from modem-70.eldamar.dialup.pol.co.uk ([62.136.181.70] helo=mashed.turnip.org.uk) by mail17.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13EKTb-0004uo-00 for stable@freebsd.org; Tue, 18 Jul 2000 00:39:07 +0100 Received: (from jonathan@localhost) by mashed.turnip.org.uk (8.9.3/8.9.3) id AAA00438 for stable@freebsd.org; Tue, 18 Jul 2000 00:39:02 +0100 (BST) (envelope-from jonathan) Date: Tue, 18 Jul 2000 00:39:01 +0100 From: Jonathan Vaughan To: stable@freebsd.org Subject: Re: installworld failure (sys/boot/mbr) Message-ID: <20000718003901.A207@mashed.turnip.org.uk> References: <20000715132554.A31976@mashed.turnip.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jhb@FreeBSD.ORG on Mon, Jul 17, 2000 at 02:33:37PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 02:33:37PM -0700, John Baldwin wrote: > > On 15-Jul-00 Jonathan Vaughan wrote: > > The "mbr" file indeed does not exist in /usr/src/sys/boot/i386/mbr. > > It is however present in /usr/obj/usr/src/sys/boot/i386/mbr. > > That is the right place for it to be, I don't know why things are > out of sync for you. How are you running installworld? (i.e., > what is the exact command line, etc.) It looks as though I did a make clean in /usr/src/sys after the buildworld and before buildkernel, deleting these files. -- Jonathan Vaughan jonathan@turnip.org.uk PGP Key ID: 0x0AF58107 http://home.clara.net/turnip/pgp.txt | jon@pgpkey.turnip.org.uk | keyservers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:43:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id D4C0437B720; Mon, 17 Jul 2000 16:43:10 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 81D299B05; Tue, 18 Jul 2000 00:43:07 +0100 (BST) Date: Tue, 18 Jul 2000 00:43:07 +0100 From: Josef Karthauser To: Christopher Forgeron Cc: Kris Kennaway , Josef Karthauser , stable@freebsd.org Subject: Re: Why does my installworld keep breaking here? (fwd) Message-ID: <20000718004307.B12476@pavilion.net> Mail-Followup-To: Josef Karthauser , Christopher Forgeron , Kris Kennaway , Josef Karthauser , stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from kris@FreeBSD.org on Fri, Jul 14, 2000 at 04:32:18PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try this: # cd /usr/src/lib/libc # make obj && make depend && make && make install That should fix it. Joe On Fri, Jul 14, 2000 at 04:32:18PM -0700, Kris Kennaway wrote: > Looks like you managed to break something again, despite your best efforts > :-( > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > ---------- Forwarded message ---------- > Date: Fri, 14 Jul 2000 12:29:41 -0300 > From: Christopher Forgeron > To: stable@freebsd.org > Subject: Why does my installworld keep breaking here? > > Hi, I've been fighting with this for a while; > > I do a make installworld from my newly d/led CVS source tree. Here is the > tail-end of my output. > > ===> lib/libcrypt > install -c -o root -g wheel -m 444 libscrypt.a /usr/lib > install -c -s -o root -g wheel -m 444 -fschg libscrypt.so.2 /usr/lib > /usr/libexec/ld-elf.so.1: install: Undefined symbol "strtofflags" > *** Error code 1 > > Stop in /usr/src/lib/libcrypt. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > I have 4.0-RELEASE, and am trying to upgrade to 4.0-STABLE. I got the > complete src/all from CVS (RELENG4), and I have, and have not gotten all the > crypto, depending on my mood. > > I've done these before, and they worked. On this box, it's dying. > > Anything blindingly stupid that I'm forgetting? > > -- > Christopher Forgeron > Aardvark Computer Solutions, Inc. > 2070 Oxford Street, Suite 200, Halifax, Nova Scotia. B3L-2T2 > Tel: (902) 425-2686 Fax: (902) 425-1550 > cforger@aardvarkinc.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:45:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id EFF4837B7A5; Mon, 17 Jul 2000 16:45:29 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id TAA93137; Mon, 17 Jul 2000 19:45:49 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 17 Jul 2000 19:45:49 -0400 (EDT) From: Adam To: Kris Kennaway Cc: stable@FreeBSD.org Subject: Re: Problem with installworld In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Kris Kennaway wrote: >On Mon, 17 Jul 2000, Adam wrote: > >> Is this not worth a note in UPDATING? Theres *only* four entries in there >> past 4.0-release, I dont think its asking too much to be read :) > >Actually it's not the kind of thing that goes into UPDATING: namely hoops >you have to jump through to update your system. Maybe it should? I was obviously stumbling over this problem when _updating_ my system and since the base system already has (hopefully) working ssh, I'd probably never notice USA_RESIDENT was set to no since I wouldnt have to compile ssh from ports... Besides, it _was_ a hoop I had to jump through. In my mind UPDATING shows the oddball things a person has to do out of the ordinary when going from xx-release or date-xxx to present to upgrade your system without blowing toes off in any manner and causing extra posts to mailing lists asking whats going on??? like this one :) > >This is an erratum and should be listed on >http://www.freebsd.org/releases/4.0R/errata.html, except no-one notes bug >fixes in the errata for some reason. > >Kris > >-- >In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 16:54:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 7EEB437B705 for ; Mon, 17 Jul 2000 16:54:51 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 15882874 invoked from network); 17 Jul 2000 23:54:48 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Jul 2000 23:54:48 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id BAA13072; Tue, 18 Jul 2000 01:54:41 +0200 (CEST) (envelope-from root) From: Cyrille Lefevre Posted-Date: Tue, 18 Jul 2000 01:54:41 +0200 (CEST) Message-Id: <200007172354.BAA13072@gits.dyndns.org> Subject: Re: kernel.debug (was Re: HEADS UP! Always use the 'make buildkernel' target to make your kernels) In-Reply-To: "from Cyrille Lefevre at Jul 16, 2000 07:08:20 am" To: clefevre@citeweb.net Date: Tue, 18 Jul 2000 01:54:41 +0200 (CEST) Cc: "Daniel C. Sobral" , Brad Knowles , Peter van Heusden , stable@FreeBSD.ORG Reply-To: clefevre@citeweb.net Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM963878081-12128-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM963878081-12128-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cyrille Lefevre wrote: > "Daniel C. Sobral" writes: > > > Brad Knowles wrote: > > > > > > At 1:29 PM +0200 2000/7/11, Peter van Heusden wrote: > > > > > > > My only (minor) concern, from a useability point of view, is that there is > > > > no default BUILDKERNEL value - shouldn't it default to GENERIC if nothing > > > > else is specified? That way you won't actually be able to do a > > > > 'buildkernel' without building a kernel. > > > > > > Hmm. Good idea. Until then, this needs to be mentioned in the > > > documentation. > > > > Notice that KERNEL can be set from make.conf, and there is a default in > > there. Either it is commented out, or the complain just apply to the > > first time around, before running mergemaster. well. I reply to myself to follow this thread. about setting KERNEL in /etc/make.conf w/ more than one target makes a make loop using buildkernel. I tried it. much better to use KERNELS instead. also, I've tested the building of multiple kernel w/ debugging informations using // make w/o any problems using the buildkernel target. the patch is in attachement. > also, why the kernel object are in /usr/obj/.../sys/ and not in > /usr/obj/.../sys/compile/ which match more the old way ? nobody answer to that question ? Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr --ELM963878081-12128-0_ Content-Transfer-Encoding: 7bit Content-Type: text/x-patch Content-Disposition: attachment; filename=Makefile.inc1.patch Content-Description: Makefile.inc1.patch --- Makefile.inc1.orig Sat Jun 17 05:43:06 2000 +++ Makefile.inc1 Tue Jul 18 01:50:15 2000 @@ -338,7 +338,7 @@ # be set to cross-build, we have to make sure MACHINE is set # properly. -KERNEL?= GENERIC +KERNELS?= GENERIC # The only exotic MACHINE_ARCH/MACHINE combination valid at this # time is i386/pc98. In all other cases set MACHINE equal to @@ -354,10 +354,17 @@ .if !defined(NOCLEAN) CONFIGARGS+= -r .endif +.if defined(DEBUG) +CONFIGARGS+= -g +KMAKEENV+= DEBUG=-g +.endif +.if defined(JOBS) +KMAKEARGS+= ${JOBS} +.endif BUILDKERNELS= INSTALLKERNEL= -.for _kernel in ${KERNEL} +.for _kernel in ${KERNELS} .if exists(${KRNLCONFDIR}/${_kernel}) BUILDKERNELS+= ${_kernel} .if empty(INSTALLKERNEL) @@ -383,11 +390,12 @@ PATH=${TMPPATH} \ config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} ${_kernel} cd ${KRNLOBJDIR}/${_kernel}; \ - MAKESRCPATH=${KRNLSRCDIR}/dev/aic7xxx \ + MAKESRCPATH=${KRNLSRCDIR}/dev/aic7xxx ${KMAKEENV} \ ${MAKE} -f ${KRNLSRCDIR}/dev/aic7xxx/Makefile; \ ${WMAKEENV} MACHINE=${MACHINE} KERNEL=${_kernel} \ ${MAKE} depend; \ - ${WMAKEENV} MACHINE=${MACHINE} KERNEL=${_kernel} ${MAKE} all + ${WMAKEENV} ${KMAKEENV} MACHINE=${MACHINE} KERNEL=${_kernel} \ + ${MAKE} ${KMAKEARGS} all .endfor # --ELM963878081-12128-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17: 2: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id ADBC437B705 for ; Mon, 17 Jul 2000 17:01:52 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA17101; Mon, 17 Jul 2000 17:01:48 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007180001.RAA17101@freeway.dcfinc.com> Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? In-Reply-To: <003401bfeffb$19083020$b8209fc0@campbellmithun.com> from Shawn Barnhart at "Jul 17, 0 09:27:11 am" To: swb@grasslake.net (Shawn Barnhart) Date: Mon, 17 Jul 2000 17:01:48 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Shawn Barnhart wrote: > The same machine had been running (blush) Windows 2000 since March > with little or no problems -- no problem with lockups, blue screens, > etc. You mean, no problems you've noticed. You may very well be right about no problems, but please be aware that Windows will not detect/report many errors that will trip up FreeBSD. Quiet data corruption is the sometimes result. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17: 7:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 3E8CC37B78B for ; Mon, 17 Jul 2000 17:07:35 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA17178; Mon, 17 Jul 2000 17:07:20 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007180007.RAA17178@freeway.dcfinc.com> Subject: Re: Maybe someone here has a solution? In-Reply-To: <01c701bff013$5d92a640$0405010a@office.iencentral.com> from "David E. Brooks Jr" at "Jul 17, 0 01:20:55 pm" To: dbrooks@iencentral.com (David E. Brooks Jr) Date: Mon, 17 Jul 2000 17:07:20 -0700 (MST) Cc: richard@sprawlnet.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, David E. Brooks Jr wrote: > Alas, Informix doesn't have a native FreeBSD port of their esql/c > product. However, we recently went through a database selection > process and our Informix sales guys managed to get approval for the > port (just esql/c, not the entire database) to be done. We ultimately > went with another database so I don't know the status of the port, but > if they went ahead it would be nearing completion. (And if they > didn't, I don't imagine it would be too difficult to get the project > going again). I suggest contacting your friendly Informix sales rep > and see what they can do for you. We've heard references to the Informix client SDK being ported to FreeBSD as well. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17:20:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id A85DE37B640; Mon, 17 Jul 2000 17:20:32 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA17343; Mon, 17 Jul 2000 17:20:29 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007180020.RAA17343@freeway.dcfinc.com> Subject: Re: bioscall.s In-Reply-To: <20000717233823.B78153@freebie.demon.nl> from Wilko Bulte at "Jul 17, 0 11:38:23 pm" To: wilko@FreeBSD.ORG Date: Mon, 17 Jul 2000 17:20:29 -0700 (MST) Cc: rsstan@yahoo.com, obrien@FreeBSD.ORG, keith.mackay@home.com, stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Wilko Bulte wrote: > 20000706: > Binutils were updated. In order to build a kernel after this > date, you must follow the updating proceedure for building kernels > exactly as presented here. You may be able to get away with doing > it the old way, but if it breaks, make sure that you've tried the > "To build a kernel" section with a fresh /usr/obj first. Could someone please offer a brief explanation about the nature of the change to the binutils? How are they different such that the kernel build method needed change? My original understanding was that the new method used the tools in /usr/obj instead of in /usr/bin, in order to build kernels with freshly built tools, rather than the tools from the previous build. Late postings imply something more complicated has happened. Is that true? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17:30:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kestrel.prod.itd.earthlink.net (kestrel.prod.itd.earthlink.net [207.217.121.155]) by hub.freebsd.org (Postfix) with ESMTP id 59BF437B596 for ; Mon, 17 Jul 2000 17:30:13 -0700 (PDT) (envelope-from eogren@earthlink.net) Received: from rod.darktech.org (ip89.cambridge1.ma.pub-ip.psi.net [38.32.111.89]) by kestrel.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id RAA23383; Mon, 17 Jul 2000 17:30:03 -0700 (PDT) Received: (from eogren@localhost) by rod.darktech.org (8.10.1/8.10.1) id e6I0Evn05119; Mon, 17 Jul 2000 20:14:57 -0400 (EDT) Date: Mon, 17 Jul 2000 20:14:57 -0400 From: Eric Ogren To: Lars Eggert Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildkernel failure: netinet6/esp_core.c Message-ID: <20000717201457.B4413@earthlink.net> References: <39736E96.1AC0917B@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39736E96.1AC0917B@isi.edu>; from larse@ISI.EDU on Mon, Jul 17, 2000 at 01:37:42PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 01:37:42PM -0700, Lars Eggert wrote: > Building a kernel (config file attached) on a freshly updated -stable > system fails with: > > cc -c -O3 -pipe -funroll-loops -fomit-frame-pointer -fno-builtin -Wall ^^^ Try again without using unsupported optimization parameters. (-O is the max supported). Eric > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include > -DXBONEHACK -DMAX_GIF_NEST=2147483647 -D_KERNEL -include opt_global.h -elf > -mpreferred-stack-boundary=2 ../../netinet6/esp_core.c > ../../netinet6/esp_core.c: In function `esp_descbc_decrypt': > ../../netinet6/esp_core.c:319: void value not ignored as it ought to be > ../../netinet6/esp_core.c:238: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_descbc_encrypt': > ../../netinet6/esp_core.c:440: void value not ignored as it ought to be > ../../netinet6/esp_core.c:345: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_decrypt': > ../../netinet6/esp_core.c:571: void value not ignored as it ought to be > ../../netinet6/esp_core.c:519: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_encrypt': > ../../netinet6/esp_core.c:649: void value not ignored as it ought to be > ../../netinet6/esp_core.c:598: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_cast128cbc_decrypt': > ../../netinet6/esp_core.c:743: void value not ignored as it ought to be > ../../netinet6/esp_core.c:687: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_cast128cbc_encrypt': > ../../netinet6/esp_core.c:818: void value not ignored as it ought to be > ../../netinet6/esp_core.c:765: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_rc5cbc_decrypt': > ../../netinet6/esp_core.c:1064: void value not ignored as it ought to be > ../../netinet6/esp_core.c:1014: warning: `error' might be used > uninitialized in this function > ../../netinet6/esp_core.c: In function `esp_rc5cbc_encrypt': > ../../netinet6/esp_core.c:1134: void value not ignored as it ought to be > ../../netinet6/esp_core.c:1085: warning: `error' might be used > uninitialized in this function > *** Error code 1 > > -- > Lars Eggert Information Sciences Institute > http://www.isi.edu/~larse/ University of Southern California > # ---------------------------------------------------------------------------- > # $RCSfile: PRECISION,v $ > # > # $Revision: 1.20 $ > # $Author: larse $ > # $Date: 2000/07/14 00:28:49 $ > # $State: Exp $ > # ---------------------------------------------------------------------------- > # $Log: PRECISION,v $ > # Revision 1.20 2000/07/14 00:28:49 larse > # More gifs, no AUTO_EOI1. > # > # Revision 1.19 2000/06/26 21:11:28 larse > # From -stable. > # > # Revision 1.18 2000/06/06 21:39:39 larse > # Systems running kernels with option NFS do not need nfsiod. > # > # Revision 1.17 2000/06/05 18:13:36 larse > # Kernel working on Gateway Solo notebooks now. > # > # Revision 1.16 2000/06/02 01:19:17 larse > # make.conf > # > # Revision 1.15 2000/05/18 17:35:13 larse > # Enabled ATAPI DMA, speaker, perfmon, ktrace, removed some things. > # > # Revision 1.14 2000/04/26 23:21:50 larse > # Enabled more IP goodies in case we need them. > # > # Revision 1.13 2000/04/25 18:09:28 larse > # Support for Hauppauge cards, disabled unneeded SMB/I2C stuff. > # > # Revision 1.12 2000/04/21 08:20:06 larse > # pcf caused problems on dee > # > # Revision 1.11 2000/04/20 08:47:03 larse > # Enabled I2C and SMBus on the NS-8000 Gateways. > # > # Revision 1.10 2000/04/19 03:15:09 larse > # Enabled memory-mapped I/O for aic SCSI adapter. > # > # Revision 1.9 2000/04/07 22:07:55 larse > # More mbuf clusters, more gif interfaces, enabled SMBus. > # > # Revision 1.8 2000/03/31 01:21:28 larse > # Re-enabled non-HARP ATM, HARP cannot deal with Adaptec cards. > # > # Revision 1.7 2000/03/30 23:03:40 larse > # Minor changes, now works on tan (old lab host) and mul (new lab host) > # as well has the new office machines. > # > # Revision 1.6 2000/03/30 14:05:32 larse > # Switched to HARP ATM. > # > # Revision 1.5 2000/03/30 13:08:52 larse > # Added options to support lab hosts (works on tan at least). > # > # Revision 1.4 2000/03/30 11:56:44 larse > # Disabled firewall/divert. > # > # Revision 1.3 2000/03/24 11:07:29 larse > # Enabled ATAPI DMA, gif tunnels, disabled LSSR, added PSM_HOOKRESUME. > # > # Revision 1.2 2000/03/21 13:50:41 larse > # Added cvs header. > # > # ---------------------------------------------------------------------------- > > # This allows you to actually store this configuration file into > # the kernel binary itself, where it may be later read by saying: > # strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL > options INCLUDE_CONFIG_FILE # Include this file in kernel > > makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > > machine i386 > #cpu I386_CPU > #cpu I486_CPU > cpu I586_CPU # for our notebooks (Solos/Librettos) > cpu I686_CPU # for all other machines > ident PRECISION > maxusers 128 > > #options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options MFS #Memory Filesystem > #options MD_ROOT #MD is a potential root device > options NFS #Network Filesystem > #options NFS_ROOT #NFS usable as root device, NFS required > #options MSDOSFS #MSDOS Filesystem > #options CD9660 #ISO 9660 Filesystem > #options CD9660_ROOT #CD-ROM usable as root, CD9660 required > #options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=0 #Delay (in ms) before probing SCSI > options UCONSOLE #Allow users to grab the console > #options USERCONFIG #boot -c editor > #options VISUAL_USERCONFIG #visual boot -c editor > #options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B #Posix P1003_1B real-time extentions > options _KPOSIX_PRIORITY_SCHEDULING > > # To make an SMP kernel, the next two are needed > #options SMP # Symmetric MultiProcessor Kernel > #options APIC_IO # Symmetric (APIC) I/O > # Optionally these may need tweaked, (defaults shown): > #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 > > device isa > device eisa > device pci > > # Floppy drives > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > #device fd1 at fdc0 drive 1 > > > # ATA and ATAPI devices > #device ata0 at isa? port IO_WD1 irq 14 > #device ata1 at isa? port IO_WD2 irq 15 > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > #options ATA_STATIC_ID #Static device numbering > options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > # SCSI Controllers > #device ahb # EISA AHA1742 family > device ahc # AHA2940 and onboard AIC7xxx devices > #device amd # AMD 53C974 (Teckram DC-390(T)) > #device dpt # DPT Smartcache - See LINT for options! > #device isp # Qlogic family > #device ncr # NCR/Symbios Logic > #device sym # NCR/Symbios Logic (newer chipsets) > > #device adv0 at isa? > #device adw > #device bt0 at isa? > #device aha0 at isa? > #device aic0 at isa? > > # SCSI peripherals > device scbus # SCSI bus (required) > device da # Direct Access (disks) > #device sa # Sequential Access (tape etc) > device cd # CD > #device pass # Passthrough device (direct SCSI access) > > # RAID controllers > #device amr # AMI MegaRAID > #device mlx # Mylex DAC960 family > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > device psm0 at atkbdc? irq 12 > > device vga0 at isa? > > # splash screen/screen saver > pseudo-device splash > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? > > # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver > #device vt0 at isa? > #options XSERVER # support for X server > #options FAT_CURSOR # start with block cursor > # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines > #options PCVT_SCANSET=2 # IBM keyboards are non-std > > # Floating point support - do not disable. > device npx0 at nexus? port IO_NPX irq 13 > > # Power management support (see LINT for more options) > device apm0 at nexus? # Advanced Power Management > > # PCCARD (PCMCIA) support > device card > device pcic0 at isa? irq ? port 0x3e0 iomem 0xd0000 > device pcic1 at isa? irq ? port 0x3e2 iomem 0xd4000 disable > > # Serial (COM) ports > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > device sio2 at isa? disable port IO_COM3 irq 5 > device sio3 at isa? disable port IO_COM4 irq 9 > > # Parallel port > device ppc0 at isa? irq 7 > device ppbus # Parallel port bus (required) > #device lpt # Printer > #device plip # TCP/IP over parallel > #device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > > # PCI Ethernet NICs. > device de # DEC/Intel DC21x4x (``Tulip'') > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > #device tx # SMC 9432TX (83c170 ``EPIC'') > device vx # 3Com 3c590, 3c595 (``Vortex'') > #device wx # Intel Gigabit Ethernet Card (``Wiseman'') > > # PCI Ethernet NICs that use the common MII bus controller code. > device miibus # MII bus support > #device dc # DEC/Intel 21143 and various workalikes > #device rl # RealTek 8129/8139 > #device sf # Adaptec AIC-6915 (``Starfire'') > #device sis # Silicon Integrated Systems SiS 900/SiS 7016 > #device ste # Sundance ST201 (D-Link DFE-550TX) > #device tl # Texas Instruments ThunderLAN > #device vr # VIA Rhine, Rhine II > #device wb # Winbond W89C840F > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # ISA Ethernet NICs. > #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > device ed > #device ex > device ep > # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really > # exists only as a PCMCIA device, so there is no ISA attatement needed > # and resources will always be dynamically assigned by the pccard code. > #device wi > # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will > # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP > # mode (the factory default). If you set the switches on your ISA > # card for a manually chosen I/O address and IRQ, you must specify > # those paremeters here. > #device an > # The probe order of these is presently determined by i386/isa/isa_compat.c. > #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 > #device fe0 at isa? port 0x300 > #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 > #device lnc0 at isa? port 0x280 irq 10 drq 0 > #device cs0 at isa? port 0x300 > #device sn0 at isa? port 0x300 irq 10 > # requires PCCARD (PCMCIA) support to be activated > #device xe0 at isa? > > # Pseudo devices - the number indicates how many units to allocated. > pseudo-device loop # Network loopback > pseudo-device ether # Ethernet support > #pseudo-device sl 1 # Kernel SLIP > #pseudo-device ppp 1 # Kernel PPP > pseudo-device tun # Packet tunnel. > pseudo-device pty # Pseudo-ttys (telnet etc) > #pseudo-device md # Memory "disks" > > # The `bpf' pseudo-device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > pseudo-device bpf #Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > #device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > #device ugen # Generic > #device uhid # "Human Interface Devices" > #device ukbd # Keyboard > #device ulpt # Printer > #device umass # Disks/Mass storage - Requires scbus and da > #device ums # Mouse > # USB Ethernet > #device aue # ADMtek USB ethernet > #device cue # CATC USB ethernet > #device kue # Kawasaki LSI USB ethernet > > # CPU_DISABLE_5X86_LSSER disables load store serialize (i.e. enables > # reorder). This option should not be used if you use memory mapped > # I/O device(s). > # options CPU_DISABLE_5X86_LSSER > > # CPU_FASTER_5X86_FPU enables faster FPU exception handler. > options CPU_FASTER_5X86_FPU > > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is > # executed. This should be included for ALL kernels that won't run > # on a Pentium. > # > # DISABLED, our notebooks (Solos/Librettos) have Pentiums! > # options NO_F00F_HACK > > # Allow user-mode programs to manipulate their local descriptor tables. > # This option is required for the WINE Windows(tm) emulator, and is > # not used by anything else (that we know of)# > options USER_LDT #allow user-level control of i386 ldt > > # TCP_DROP_SYNFIN adds support for ignoring TCP packets with SYN+FIN. This > # prevents nmap et al. from identifying the TCP/IP stack, but breaks support > # for RFC1644 extensions and is not recommended for web servers. > options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN > > # TCP_RESTRICT_RST adds support for blocking the emission of TCP RST packets. > # This is useful on systems which are exposed to SYN floods (e.g. IRC servers) > # or any system which one does not want to be easily portscannable. > options TCP_RESTRICT_RST #restrict emission of TCP RST > > options IPSEC #IP security > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > > options INET6 #IPv6 communications protocols > > # The `gif' pseudo-device implements IPv6 over IP4 tunneling, > # IPv4 over IPv6 tunneling, IPv4 over IPv4 tunneling and > # IPv6 over IPv6 tunneling. > pseudo-device gif 32 #IPv6 and IPv4 tunneling > > # The `faith' pseudo-device captures packets sent to it and diverts them > # to the IPv4/IPv6 translation daemon. > #pseudo-device faith 1 #for IPv6 and IPv4 translation > > # IPFIREWALL enables support for IP firewall construction, in > # conjunction with the `ipfw' program. IPFIREWALL_VERBOSE sends > # logged packets to the system logger. IPFIREWALL_VERBOSE_LIMIT > # limits the number of times a matching entry can be logged. > options IPFIREWALL #firewall > options IPFIREWALL_VERBOSE #print information about > # dropped packets > options IPFIREWALL_FORWARD #enable transparent proxy support > options IPFIREWALL_VERBOSE_LIMIT=1000 #limit verbosity > options IPV6FIREWALL #firewall for IPv6 > options IPV6FIREWALL_VERBOSE > options IPV6FIREWALL_VERBOSE_LIMIT=1000 > > # IPFIREWALL_DEFAULT_TO_ACCEPT causes the default rule (at boot) to > # allow everything. Use with care, if a cracker can crash your > # firewall machine, they can get to your protected machines. However, > # if you are using it as an as-needed filter for specific problems as > # they arise, then this may be for you. Changing the default to 'allow' > # means that you won't get stuck if the kernel and /sbin/ipfw binary get > # out of sync. > options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default > options IPV6FIREWALL_DEFAULT_TO_ACCEPT > > # ICMP_BANDLIM enables icmp error response bandwidth limiting. You > # typically want this option as it will help protect the machine from > # D.O.S. packet attacks. > options ICMP_BANDLIM > > # DUMMYNET enables the "dummynet" bandwidth limiter. You need > # IPFIREWALL as well. See the dummynet(4) manpage for more info. > options DUMMYNET > > # BRIDGE enables bridging between ethernet cards -- see bridge(4). > # You can use IPFIREWALL and dummynet together with bridging. > #options BRIDGE > > # IPDIVERT enables the divert IP sockets, used by ``ipfw divert'' > options IPDIVERT #divert sockets > > # MROUTING enables the kernel multicast packet forwarder, which works > # with mrouted(8). > options MROUTING # Multicast routing > > # IPSTEALTH enables code to support stealth forwarding (i.e., forwarding > # packets without touching the ttl). This can be useful to hide firewalls > # from traceroute and similar tools. > options IPSTEALTH #support for stealth forwarding > > options IPFILTER #ipfilter support > options IPFILTER_LOG #ipfilter logging > > > # Soft updates is technique for improving file system speed and > # making abrupt shutdown less risky. It is not enabled by default due > # to copyright restraints on the code that implement it. > # > # Read ../../ufs/ffs/README.softupdates to learn what you need to > # do to enable this. ../../contrib/softupdates/README gives > # more details on how they actually work. > options SOFTUPDATES > > pseudo-device speaker #Play IBM BASIC-style noises out your speaker > pseudo-device gzip #Exec gzipped a.out's > #pseudo-device vn #Vnode driver (turns a file into a device) > > # AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A > # interrupt controller. This saves about 0.7-1.25 usec for each interrupt. > # This option breaks suspend/resume on some portables. > # THIS BREAKS SLEEP SUPPORT ON THE SONY LAPTOPS, POSSIBLY OTHERS. > #options AUTO_EOI_1 > > # To include support for VESA video modes > options VESA > > options SC_HISTORY_SIZE=2000 # number of history buffer lines > options SC_PIXEL_MODE # add support for the raster text mode > > # The newpcm driver (use INSTEAD of snd0 and all VOXWARE drivers!). > # Note that motherboard sound devices may require options PNPBIOS. > # > # Supported cards include: > # Creative SoundBlaster ISA PnP/non-PnP > # Supports ESS and Avance ISA chips as well. > # Gravis UltraSound ISA PnP/non-PnP > # Crystal Semiconductor CS461x/428x PCI > # Neomagic 256AV (ac97) > # Most of the more common ISA/PnP sb/mss/ess compatable cards. > # For PnP/PCI sound cards > device pcm > options PNPBIOS > > device joy0 at isa? port IO_GAME > > # Add support for the EXT2FS filesystem of Linux fame. Be a bit > # careful with this - the ext2fs code has a tendency to lag behind > # changes and not be exercised very much, so mounting read/write could > # be dangerous (and even mounting read only could result in panics.) > options EXT2FS > > # Enable the kernel debugger. > options DDB > > # Options for psm: > options PSM_HOOKRESUME #hook the system resume event, useful > #for some laptops > options PSM_RESETAFTERSUSPEND #reset the device at the resume event > > # ATM related options > # > # The `en' device provides support for Efficient Networks (ENI) > # ENI-155 PCI midway cards, and the Adaptec 155Mbps PCI ATM cards (ANA-59x0). > # > # atm pseudo-device provides generic atm functions and is required for > # atm devices. > # NATM enables the netnatm protocol family that can be used to > # bypass TCP/IP. > # > # the current driver supports only PVC operations (no atm-arp, no multicast). > # for more details, please read the original documents at > # http://www.ccrc.wustl.edu/pub/chuck/tech/bsdatm/bsdatm.html > # > pseudo-device atm > device en > options NATM > > # The 'bktr' device is a PCI video capture device using the Brooktree > # bt848/bt848a/bt849a/bt878/bt879 chipset. When used with a TV Tuner it forms a > # TV card, eg Miro PC/TV, Hauppauge WinCast/TV WinTV, VideoLogic Captivator, > # Intel Smart Video III, AverMedia, IMS Turbo, FlyVideo. > # > # Brooktree driver has been ported to the new I2C framework. Thus, > # you'll need to have the following 3 lines in the kernel config. > # device smbus > # device iicbus > # device iicbb > # The iic and smb devices are only needed if you want to control other > # I2C slaves connected to the external connector of some cards. > device bktr > > # The aic7xxx driver will attempt to use memory mapped I/O for all PCI > # controllers that have it configured only if this option is set. Unfortunately, > # this doesn't work on some motherboards, which prevents it from being the > # default. > options AHC_ALLOW_MEMIO > > # KTRACE enables the system-call tracing facility ktrace(2). > options KTRACE #kernel tracing > > # PERFMON causes the driver for Pentium/Pentium Pro performance counters > # to be compiled. See perfmon(4) for more information. > options PERFMON > > # pca: PCM audio through your PC speaker > # Not controlled by `snd' > device pca0 at isa? port IO_TIMER1 > > options PPC_PROBE_CHIPSET # Enable chipset specific detection > # (see flags in ppc(4)) > > # If you are running a machine just as a fileserver for PC and MAC > # users, using SAMBA or Netatalk, you may consider setting this option > # and keeping all those users' directories on a filesystem that is > # mounted with the suiddir option. This gives new files the same > # ownership as the directory (similar to group). It's a security hole > # if you let these users run programs, so confine it to file-servers > # (but it'll save you lots of headaches in those cases). Root owned > # directories are exempt and X bits are cleared. The suid bit must be > # set on the directory as well; see chmod(1) PC owners can't see/set > # ownerships so they keep getting their toes trodden on. This saves > # you all the support calls as the filesystem it's used on will act as > # they expect: "It's my dir so it must be my file". > options SUIDDIR > > # allow recursive gif tunnels this many levels deep > options MAX_GIF_NEST=2147483647 # 2147483647 = INT_MAX > > # allow multiple tunnels between same two physical interfaces > options XBONEHACK > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17:33:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 310D437B5EA for ; Mon, 17 Jul 2000 17:33:30 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA17480; Mon, 17 Jul 2000 17:31:58 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007180031.RAA17480@freeway.dcfinc.com> Subject: Re: bioscall.s In-Reply-To: <20000717224359.15301.qmail@web3102.mail.yahoo.com> from Richard Stanaford at "Jul 17, 0 03:43:59 pm" To: rsstan@yahoo.com (Richard Stanaford) Date: Mon, 17 Jul 2000 17:31:58 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Richard Stanaford wrote: > --- David O'Brien wrote: >> On Mon, Jul 17, 2000 at 03:06:24PM -0700, Richard Stanaford wrote: >>> As I indicated in a separate message. The kernel build fails after >>> a CVSup and successful buildworld. >> >> Does ``as -v'' say "2.10"? > > > Why wouldn't it if 'make buildworld' was successful? I'll have to > look tonight and post accordingly. Because until you do a "make installworld" the new assembler is sitting in /usr/obj/usr/src/tmp/usr/bin instead of /usr/bin. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17:37:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id BD87E37B63D for ; Mon, 17 Jul 2000 17:37:19 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id BC6D111CD6E; Mon, 17 Jul 2000 17:37:08 -0700 (PDT) Date: Mon, 17 Jul 2000 17:37:08 -0700 From: R Joseph Wright To: Chris Cc: freebsd-stable@FreeBSD.org Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Message-ID: <20000717173708.A13211@manatee.mammalia.org> References: <20000717223751.3846.qmail@web3105.mail.yahoo.com> <20000717192441.A44452@kingsqueak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000717192441.A44452@kingsqueak.org>; from kingsqueak@kingsqueak.org on Mon, Jul 17, 2000 at 07:24:41PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 07:24:41PM -0400, Chris wrote: > I like the AMD's, have a K6-3/450 here with a really heavy Alpha > heatsink on it and a 27cfm bearing fan. Even with that fan... it just > doesn't like make buildworld or building X without the case cover off > though. Though it's not a small problem... it still performs well for me > overall. My older K6/2 200 here can build all day no problem...the new > ones just got really hot. > > I actually had to give up on fbsd for my work desktop because the > cheapie fan on the K6/2 450 I have just wouldn't cut it, even with the > case off and the thing would just plain reboot on any moderate sized > builds. I just don't have the time at the office to mess with it and my > workstation is a management station of sorts as well. I had these problems with my K6/2 450 until I finally got out the sandpaper and lapped both the CPU and the heatsink. The heatsink needed it much worse than the CPU. I have had only one reboot since I did that while loading the system heavily with an X build. Even one reboot is not good, but it's much better than it was. www.pcpowercooling.com sells heavy duty heatsink/fans for many processors including the K6/2. If my problems ever return I plan to buy one from them. > On Mon, Jul 17, 2000 at 03:37:51PM -0700, Richard Stanaford wrote: > > > > --- David Uhring wrote: > > > On Mon, 17 Jul 2000, Walter Campbell wrote: > > > > > You might also check the cpu temperature during the compile. Using a > > > K6-3/450, > > > my cpu cooler was getting quite hot to the touch during the make and would > > > exit > > > with signal 10 or signal 11. I finally took to cover off the case and set up > > > a > > > box fan to force additional air into the case. > > > > > > Heh... It's a amazing what a 19-inch Patton steel-bladed air circulator can do > > for a hard working 486/DX4/100. *snicker* Not a bit of dust on the cards. > > :-) Okay.. maybe that's overkill and I did have to make sure the PC didn't get > > blown over... but you gotta use what you've got! lol. > > I had access to a heavy duty carpet fan and used it during my upgrade from 3.2 to 4.0 :). It worked! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17:38:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3105.mail.yahoo.com (web3105.mail.yahoo.com [204.71.202.190]) by hub.freebsd.org (Postfix) with SMTP id 4899F37B65A for ; Mon, 17 Jul 2000 17:38:08 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000718003800.14278.qmail@web3105.mail.yahoo.com> Received: from [150.159.224.8] by web3105.mail.yahoo.com; Mon, 17 Jul 2000 17:38:00 PDT Date: Mon, 17 Jul 2000 17:38:00 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: chad@DCFinc.com Cc: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- "Chad R. Larson" wrote: > As I recall, Richard Stanaford wrote: > > --- David O'Brien wrote: > >> On Mon, Jul 17, 2000 at 03:06:24PM -0700, Richard Stanaford wrote: > >>> As I indicated in a separate message. The kernel build fails after > >>> a CVSup and successful buildworld. > >> > >> Does ``as -v'' say "2.10"? > > > > > > Why wouldn't it if 'make buildworld' was successful? I'll have to > > look tonight and post accordingly. > > Because until you do a "make installworld" the new assembler is > sitting in /usr/obj/usr/src/tmp/usr/bin instead of /usr/bin. Right.. but you cannot 'make installworld' until you've built and installed a new kernel with 'make buildkernel' and 'make install kernel' respectivly... but the kernel build is dying due to the assembler being unhappy about something. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 17:45: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 8462A37B7DE for ; Mon, 17 Jul 2000 17:44:59 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 980B18D1; Mon, 17 Jul 2000 17:44:45 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id RAA21883; Mon, 17 Jul 2000 17:44:44 -0700 (PDT) Message-ID: <3973A87C.80A6ADB0@cup.hp.com> Date: Mon, 17 Jul 2000 17:44:44 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: clefevre@citeweb.net Cc: "Daniel C. Sobral" , Brad Knowles , Peter van Heusden , stable@FreeBSD.ORG Subject: Re: kernel.debug (was Re: HEADS UP! Always use the 'make buildkernel'target to make your kernels) References: <200007172354.BAA13072@gits.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cyrille Lefevre wrote: > > > also, why the kernel object are in /usr/obj/.../sys/ and not in > > /usr/obj/.../sys/compile/ which match more the old way ? > > nobody answer to that question ? Because there's basicly no need for having 'compile' in the object directory. Or put differently, /sys/compile is the object directory for a traditional kernel make. To put it even more different: /usr/obj/.../sys better matches / :-) -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 18:13:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 42D0E37B52D for ; Mon, 17 Jul 2000 18:13:42 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id SAA00187; Mon, 17 Jul 2000 18:13:33 -0700 Message-ID: <3973AF4F.119FC16C@urx.com> Date: Mon, 17 Jul 2000 18:13:51 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Stanaford Cc: chad@DCFinc.com, stable@FreeBSD.ORG Subject: Re: bioscall.s References: <20000718003800.14278.qmail@web3105.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stanaford wrote: > > --- "Chad R. Larson" wrote: > > As I recall, Richard Stanaford wrote: > > > --- David O'Brien wrote: > > >> On Mon, Jul 17, 2000 at 03:06:24PM -0700, Richard Stanaford wrote: > > >>> As I indicated in a separate message. The kernel build fails after > > >>> a CVSup and successful buildworld. > > >> > > >> Does ``as -v'' say "2.10"? > > > > > > > > > Why wouldn't it if 'make buildworld' was successful? I'll have to > > > look tonight and post accordingly. > > > > Because until you do a "make installworld" the new assembler is > > sitting in /usr/obj/usr/src/tmp/usr/bin instead of /usr/bin. > > Right.. but you cannot 'make installworld' until you've built and installed a > new kernel with 'make buildkernel' and 'make install kernel' respectivly... but > the kernel build is dying due to the assembler being unhappy about something. Just to make sure that from /usr/src you are doing a make installkernel KERNEL=NOVA Kent > > -Richard > > __________________________________________________ > Do You Yahoo!? > Get Yahoo! Mail – Free email you can access from anywhere! > http://mail.yahoo.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 18:29:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 7CB2937B633 for ; Mon, 17 Jul 2000 18:29:46 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id SAA00239; Mon, 17 Jul 2000 18:29:40 -0700 Message-ID: <3973B316.C4442AAF@urx.com> Date: Mon, 17 Jul 2000 18:29:58 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: R Joseph Wright Cc: Chris , freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? References: <20000717223751.3846.qmail@web3105.mail.yahoo.com> <20000717192441.A44452@kingsqueak.org> <20000717173708.A13211@manatee.mammalia.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG R Joseph Wright wrote: > > On Mon, Jul 17, 2000 at 07:24:41PM -0400, Chris wrote: > > I like the AMD's, have a K6-3/450 here with a really heavy Alpha > > heatsink on it and a 27cfm bearing fan. Even with that fan... it just > > doesn't like make buildworld or building X without the case cover off > > though. Though it's not a small problem... it still performs well for me > > overall. My older K6/2 200 here can build all day no problem...the new > > ones just got really hot. > > > > I actually had to give up on fbsd for my work desktop because the > > cheapie fan on the K6/2 450 I have just wouldn't cut it, even with the > > case off and the thing would just plain reboot on any moderate sized > > builds. I just don't have the time at the office to mess with it and my > > workstation is a management station of sorts as well. > > I had these problems with my K6/2 450 until I finally got out the sandpaper > and lapped both the CPU and the heatsink. The heatsink needed it much worse > than the CPU. I have had only one reboot since I did that while loading the > system heavily with an X build. Even one reboot is not good, but it's much > better than it was. They weren't flat or what. I found I could cook the heat transfer tape using an overclocked Celeron. I replaced the tape with heatsink compound but doing a build of XFree86 3.3.4 had finished cooking the cpu. I remember reading before where you did that and was going to ask you why. > > www.pcpowercooling.com sells heavy duty heatsink/fans for many processors > including the K6/2. If my problems ever return I plan to buy one from them. Another place is http://www.3dfxcool.com/. He has some fans that look like they would lift the case off if you weren't using the cpu as a thrust reverser. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 18:51:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B452837B7D7 for ; Mon, 17 Jul 2000 18:51:48 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA27954; Mon, 17 Jul 2000 18:51:43 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200007180151.SAA27954@gndrsh.dnsmgr.net> Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? In-Reply-To: <20000717223751.3846.qmail@web3105.mail.yahoo.com> from Richard Stanaford at "Jul 17, 2000 03:37:51 pm" To: rsstan@yahoo.com (Richard Stanaford) Date: Mon, 17 Jul 2000 18:51:43 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > --- David Uhring wrote: > > On Mon, 17 Jul 2000, Walter Campbell wrote: > > > You might also check the cpu temperature during the compile. Using a > > K6-3/450, > > my cpu cooler was getting quite hot to the touch during the make and would > > exit > > with signal 10 or signal 11. I finally took to cover off the case and set up > > a > > box fan to force additional air into the case. > > > Heh... It's a amazing what a 19-inch Patton steel-bladed air circulator can do > for a hard working 486/DX4/100. *snicker* Not a bit of dust on the cards. > :-) Okay.. maybe that's overkill and I did have to make sure the PC didn't get > blown over... but you gotta use what you've got! lol. Becareful, you may have eliminated your heat problem, but you have now created an excelent static electricity generator. High volumes of air moving over just about anything will build static at an alarming rate! -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 18:53:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3102.mail.yahoo.com (web3102.mail.yahoo.com [204.71.202.187]) by hub.freebsd.org (Postfix) with SMTP id D091D37B7D7 for ; Mon, 17 Jul 2000 18:53:44 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000718015340.3073.qmail@web3102.mail.yahoo.com> Received: from [150.159.224.8] by web3102.mail.yahoo.com; Mon, 17 Jul 2000 18:53:40 PDT Date: Mon, 17 Jul 2000 18:53:40 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: kstewart@urx.com Cc: chad@DCFinc.com, stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Kent Stewart wrote: > Just to make sure that from /usr/src you are doing a > > make installkernel KERNEL=NOVA I may have used .. make buildkernel KERNEL="NOVA" If the quotes are evil I would have expected it to make more than just 'as' mad. I'm going to CVSup, buildworld, and buildkernel again tonight *without* the quotes to ensure I did it right. I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 18:59:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id DEC9837B818 for ; Mon, 17 Jul 2000 18:59:18 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id SAA00359; Mon, 17 Jul 2000 18:59:15 -0700 Message-ID: <3973BA04.5AB2FFD@urx.com> Date: Mon, 17 Jul 2000 18:59:32 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Stanaford Cc: chad@DCFinc.com, stable@FreeBSD.ORG Subject: Re: bioscall.s References: <20000718015340.3073.qmail@web3102.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stanaford wrote: > > --- Kent Stewart wrote: > > > Just to make sure that from /usr/src you are doing a > > > > make installkernel KERNEL=NOVA > > I may have used .. > > make buildkernel KERNEL="NOVA" The quotes are evil. One my first kernel I left if buildkernel kernel=NOVA and it didn't work just like yours did. That was part of the reason I needed 15 minutes for my first good build on 7/7. > > If the quotes are evil I would have expected it to make more than just 'as' > mad. I'm going to CVSup, buildworld, and buildkernel again tonight *without* > the quotes to ensure I did it right. > > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty. Recently or before 7 July. My first build was on a P-II 400 and it is only slightly faster than my server, which is a Celeron 433. Kent > > -Richard > > __________________________________________________ > Do You Yahoo!? > Get Yahoo! Mail – Free email you can access from anywhere! > http://mail.yahoo.com/ -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 19: 1:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3103.mail.yahoo.com (web3103.mail.yahoo.com [204.71.202.188]) by hub.freebsd.org (Postfix) with SMTP id 3CFE237B7D7 for ; Mon, 17 Jul 2000 19:01:52 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000718020151.27434.qmail@web3103.mail.yahoo.com> Received: from [150.159.224.8] by web3103.mail.yahoo.com; Mon, 17 Jul 2000 19:01:51 PDT Date: Mon, 17 Jul 2000 19:01:51 -0700 (PDT) From: Richard Stanaford Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? To: "Rodney W. Grimes" Cc: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- "Rodney W. Grimes" wrote: > > Becareful, you may have eliminated your heat problem, but you have now > created an excelent static electricity generator. High volumes of air > moving over just about anything will build static at an alarming rate! One word... Febreeze. *snicker* j/k On a serious note you do need to be careful with a fan. They create an oscillating EM field that could corrupt data. Hold a fan next to your computer monitor and watch what it does. *ripple* *ripple* 8-) I did know a guy who ran some air conditioning ductwork down and taped it to the side of his box. I'd be worried about it getting too cold then. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 19: 7:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3106.mail.yahoo.com (web3106.mail.yahoo.com [204.71.202.191]) by hub.freebsd.org (Postfix) with SMTP id EC86C37B818 for ; Mon, 17 Jul 2000 19:07:07 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000718024456.25263.qmail@web3106.mail.yahoo.com> Received: from [150.159.224.8] by web3106.mail.yahoo.com; Mon, 17 Jul 2000 19:44:56 PDT Date: Mon, 17 Jul 2000 19:44:56 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Kent Stewart wrote: > > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from > > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty. > > Recently or before 7 July. My first build was on a P-II 400 and it is > only slightly faster than my server, which is a Celeron 433. Recently. I did a successful upgrade from 4.0-RELEASE to STABLE on the DX4/100 just last week. The changes to binutils had been committed for some time I believe. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 19:17:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id DE66C37B875 for ; Mon, 17 Jul 2000 19:17:11 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 13577907; Mon, 17 Jul 2000 22:17:10 -0400 From: David Uhring To: "Rodney W. Grimes" , rsstan@yahoo.com (Richard Stanaford) Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Mon, 17 Jul 2000 21:08:31 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-stable@FreeBSD.ORG References: <200007180151.SAA27954@gndrsh.dnsmgr.net> In-Reply-To: <200007180151.SAA27954@gndrsh.dnsmgr.net> MIME-Version: 1.0 Message-Id: <00071721171000.27796@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Rodney W. Grimes wrote: > > > > --- David Uhring wrote: > > > On Mon, 17 Jul 2000, Walter Campbell wrote: > > > > > You might also check the cpu temperature during the compile. Using a > > > K6-3/450, > > > my cpu cooler was getting quite hot to the touch during the make and would > > > exit > > > with signal 10 or signal 11. I finally took to cover off the case and set up > > > a > > > box fan to force additional air into the case. > > > > > > Heh... It's a amazing what a 19-inch Patton steel-bladed air circulator can do > > for a hard working 486/DX4/100. *snicker* Not a bit of dust on the cards. > > :-) Okay.. maybe that's overkill and I did have to make sure the PC didn't get > > blown over... but you gotta use what you've got! lol. > > Becareful, you may have eliminated your heat problem, but you have now > created an excelent static electricity generator. High volumes of air > moving over just about anything will build static at an alarming rate! > > > > -- > Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net > With the humidity as it is in the St. Louis area at this time of the year, static electricity buildup is not really much of a concern. For people living in drier areas, this definitely should be considered. At least a few more people are looking for problems in their hardware when their buildworlds fail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 19:17:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 8D16937B8F0 for ; Mon, 17 Jul 2000 19:17:23 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id TAA00406; Mon, 17 Jul 2000 19:17:21 -0700 Message-ID: <3973BE42.E9A9A4BF@urx.com> Date: Mon, 17 Jul 2000 19:17:38 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Stanaford Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s References: <20000718024456.25263.qmail@web3106.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stanaford wrote: > > --- Kent Stewart wrote: > > > > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from > > > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty. > > > > Recently or before 7 July. My first build was on a P-II 400 and it is > > only slightly faster than my server, which is a Celeron 433. > > Recently. > > I did a successful upgrade from 4.0-RELEASE to STABLE on the DX4/100 just last > week. The changes to binutils had been committed for some time I believe. They were just in when I made my system on late 7 July. The other thing is that the kernel it makes will be called NOVA and you either have to setup /boot/loader.conf to use it or do the chflags sequence to mv NOVA kernel. I've been doing the mv sequence. I like being able to build/install-kernel KERNEL=GENERIC. Otherwise kernel.GENERIC goes back to your original release. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 19:49:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sunny.pacific.net.au (sunny.pacific.net.au [210.23.129.40]) by hub.freebsd.org (Postfix) with ESMTP id 9C95337B50D; Mon, 17 Jul 2000 19:49:50 -0700 (PDT) (envelope-from gfm@mira.net) Received: from wisma.pacific.net.au (wisma.pacific.net.au [210.23.129.72]) by sunny.pacific.net.au with ESMTP id MAA27268; Tue, 18 Jul 2000 12:49:46 +1000 (EST) Received: from ppp186.dyn136.pacific.net.au (ppp186.dyn136.pacific.net.au [210.23.136.186]) by wisma.pacific.net.au with SMTP id MAA22071; Tue, 18 Jul 2000 12:49:44 +1000 (EST) From: Graham Menhennitt To: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: XFree86 4.0.1 port fails "don't know how to make: clean" Date: Tue, 18 Jul 2000 12:49:31 +1000 Message-ID: <68h7nsot4mv7omd4hchrtkh7e9mk6l28a6@4ax.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent this to the ports mailing list but didn't get a reply. I'll try here... Has anybody had any success with building the XFree86 4.0.1 port (on 4-Stable, although I doubt that it makes an difference)? I've tried a few times and I always get: don't know how to make: clean in the "doc" directory. When I look at the Makefile in that directory, it has a size of zero bytes!! It's a very clean machine (just installed 4.0, cvsup'ed to 4-Stable, made the world and the kernel, mergemastered, and rebooted). The checksums verified correctly, the extract works ok, the config stuff seems to work, and it starts building. Very soon after, it aborts Does somebody have a clue? Thanks, Graham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 20:20:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id E47C837B93F for ; Mon, 17 Jul 2000 20:20:22 -0700 (PDT) (envelope-from touch@ISI.EDU) Received: from isi.edu (ras01.isi.edu [128.9.176.101]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id UAA29194; Mon, 17 Jul 2000 20:20:09 -0700 (PDT) Message-ID: <3973C882.8FD3C1E0@isi.edu> Date: Mon, 17 Jul 2000 20:01:22 -0700 From: Joe Touch X-Mailer: Mozilla 4.73 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: itojun@iijlab.net Cc: snap-users@kame.net, Lars Eggert , stable@freebsd.org, xbone@ISI.EDU, touch@ISI.EDU Subject: Re: (KAME-snap 2942) Re: KAME/FreeBSD-stable merge References: <14186.963868537@coconut.itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG itojun@iijlab.net wrote: > > >> is there any reason why the (misnamed, but that's another issue) XBONEHACK > >> option was eliminated during the recent KAME/FreeBSD-stable merge? (File > >> /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, > >> and we'd really like to see it merged into FreeBSD. > > - it does not seem like a common option to me (it is just a quickhack > for supporting special need at xbone project, which could have been > handled as local patch), and it does not seem to me good for > integrating into freebsd-current/releases The 'hack' restores general functionality. The current KAME code does not support multiple tunnels between two hosts on a single interface. This restores that capability, which is required for setting up different overlay networks which use the same pairs of hosts. Such capability would be required for a 6-bone and a manually-configured IPSEC tunnel, supporting two separate overlays which both use tunnels between the same two hosts. This is a requirement of multiple overlapping overlays (which have many uses). The X-Bone is just a system that makes such overlays easier to deploy; we don't do anything that can't or wouldn't be done by a reasonable network administrator today. > - support issues (who handles questions about it? i don't want to) We would be happy to. We would also be glad to discuss further with you the issue of decapsulation of these packets, especially how to best determine the virtual interface number to put in the 'recvif' field. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 20:20:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 5F50137B93F for ; Mon, 17 Jul 2000 20:20:33 -0700 (PDT) (envelope-from touch@ISI.EDU) Received: from isi.edu (ras01.isi.edu [128.9.176.101]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id UAA29203; Mon, 17 Jul 2000 20:20:13 -0700 (PDT) Message-ID: <3973CA3A.64ED3A82@isi.edu> Date: Mon, 17 Jul 2000 20:08:42 -0700 From: Joe Touch X-Mailer: Mozilla 4.73 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Jun-ichiro itojun Hagino Cc: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: Re: (KAME-snap 2947) Re: KAME/FreeBSD-stable merge References: <200007172153.e6HLrHa08532@itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun-ichiro itojun Hagino wrote: > > >> do you have xbone userland tool in freebsd master repository? > >> i believed not. xserver is officially supported by freebsd and > >> userland tools are in the tree. the situation looks different for me. > >The xbone port has been submitted to the ports maintainers since 3/20/00. > > hmm, up to kris i'd say. normally, such kind of port do require > special patch against kernel. > i still don't understand why you try this hard to avoid including > diffs into your xbone package. if you include diff into your > package the problem is solved. We believe the patch provides generally useful functionality in KAME We understand that some would not want to use it, and appreciate the desire to make the default behavior prohibit it until the issue of virtual interface demuxing is addressed (though we do have a solution, it appears to be undesired by KAME as a 'layer violation'. we beleive that examining a packet after it is decapsulated, to determine its virtual interface number, is both appropriate and compliant with the layering principle, though). Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 20:33:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 7595537B957 for ; Mon, 17 Jul 2000 20:33:36 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id UAA64996; Mon, 17 Jul 2000 20:33:33 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Jul 2000 20:33:32 -0700 From: "David O'Brien" To: "Chad R. Larson" Cc: stable@FreeBSD.ORG Subject: Re: bioscall.s Message-ID: <20000717203332.A64934@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000717233823.B78153@freebie.demon.nl> <200007180020.RAA17343@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007180020.RAA17343@freeway.dcfinc.com>; from chad@DCFinc.com on Mon, Jul 17, 2000 at 05:20:29PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 05:20:29PM -0700, Chad R. Larson wrote: > Could someone please offer a brief explanation about the nature of > the change to the binutils? Binutils 2.10.0 now accepts (read requires) proper AT&T ASM syntax. Previous versions required a bastardized syntax that was neither proper AT&T nor Intel syntax. > How are they different such that the kernel build method needed change? Older kernel sources are now seen as having syntax errors. This would be the same as if we used a C compiler that required functions to be written like this: void foo(void) [ return; ] and then we updated to an ANSI-C compiler. The .c source in /usr/src/ would have been fixed at the same time the ANSI-C compiler was imported into the base system. Obviously the installed [brain dead] C compiler will not properly compile "void foo(void) { return; }". This is what we are going thru with the assembler. > My original understanding was that the new method used the tools in > /usr/obj instead of in /usr/bin, in order to build kernels with > freshly built tools, rather than the tools from the previous build. Correct. > Late postings imply something more complicated has happened. > Is that true? All I've seen so far is pilot error -- nothing wrong with the method. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 20:50:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id CA4D037B969 for ; Mon, 17 Jul 2000 20:50:06 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.06) with ESMTP id MAA17782; Tue, 18 Jul 2000 12:50:04 +0900 (JST) To: snap-users@kame.net Cc: Lars Eggert , stable@freebsd.org, xbone@ISI.EDU, touch@ISI.EDU In-reply-to: touch's message of Mon, 17 Jul 2000 20:01:22 MST. <3973C882.8FD3C1E0@isi.edu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 2950) Re: KAME/FreeBSD-stable merge From: itojun@iijlab.net Date: Tue, 18 Jul 2000 12:50:04 +0900 Message-ID: <17780.963892204@coconut.itojun.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The 'hack' restores general functionality. the hack brings a buggy behavior back. xbone relied upon the buggy behavior. >The current KAME code does not support multiple tunnels between two >hosts on a single interface. This restores that capability, which is >required for setting up different overlay networks which use the same >pairs of hosts. if you consider inbound packets, it does not make sense to have multiple tunnel interfaces for the same pair of outer addresses . itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 21: 9:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 0EC7037B61F for ; Mon, 17 Jul 2000 21:09:55 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from k6 (k6.grasslake.net [192.168.2.1]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id XAA08092; Mon, 17 Jul 2000 23:10:40 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <000801bff06d$f8f7bcb0$0102a8c0@k6> From: "Shawn Barnhart" To: Cc: References: <200007180001.RAA17101@freeway.dcfinc.com> Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Mon, 17 Jul 2000 23:09:24 -0500 Organization: Grasslake.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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Chad R. Larson" | You mean, no problems you've noticed. You may very well be right | about no problems, but please be aware that Windows will not | detect/report many errors that will trip up FreeBSD. Quiet data | corruption is the sometimes result. Well, I wasn't trying to impune the charater of FreeBSD, but this cpu/ram/mobo combo I pushed pretty hard under Win2k without EVER getting errors. I have 128MB of RAM in it and I often had over 300MB total VM in use. Machine was powered up 24 x 7 and seldom rebooted for ANY reason. If there's a memory glitch, I'm sure it was silent as I didn't get the problems I typically associate with low budget kit and Windows. I've swapped the CPU for an Intel P166 and had another buildworld die, so I don't think the K6 is to blame. I'm going to run memtest all night long and see if it can identify any problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 22:37: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 2041837B6BF for ; Mon, 17 Jul 2000 22:36:59 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id WAA07667; Mon, 17 Jul 2000 22:36:57 -0700 (PDT) Date: Mon, 17 Jul 2000 22:36:57 -0700 From: Brooks Davis To: Richard Stanaford Cc: stable@FreeBSD.ORG, imp@village.org Subject: Re: bioscall.s Message-ID: <20000717223657.A6353@orion.ac.hmc.edu> References: <20000718024456.25263.qmail@web3106.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000718024456.25263.qmail@web3106.mail.yahoo.com>; from rsstan@yahoo.com on Mon, Jul 17, 2000 at 07:44:56PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 07:44:56PM -0700, Richard Stanaford wrote: > Recently. > > I did a successful upgrade from 4.0-RELEASE to STABLE on the DX4/100 just last > week. The changes to binutils had been committed for some time I believe. After watching days of this from various people, I decided to upgrade my STABLE box just to be sure the developers hadn't missed some strange thing. It was a mid March 4.0-STABLE system (just post-release). I sucessfully upgraded my system to 4.1-RC this afternoon via: cd /usr/src cvs update make -j4 buildworld fsck -p mount -a cd /usr/src make installworld mergemaster reboot Everything worked flawlessly (other then a stupid mistake merging /etc/shells changes, but diagnosing and fixing that took a couple of seconds). Just wanted to give a positive report. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 23: 1:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id B4E5237B977 for ; Mon, 17 Jul 2000 23:01:49 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.10.1/8.10.1) id e6I61gP33511 for freebsd-stable@freebsd.org; Tue, 18 Jul 2000 08:01:42 +0200 (SAT) From: John Hay Message-Id: <200007180601.e6I61gP33511@zibbi.mikom.csir.co.za> Subject: /modules/ empty in 4.x snaps To: freebsd-stable@freebsd.org Date: Tue, 18 Jul 2000 08:01:42 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see that the /modules directory is empty in the latest 4.x snaps. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jul 17 23: 4:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id A3F6837B9AE for ; Mon, 17 Jul 2000 23:04:34 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id D4A5B11CD6E; Mon, 17 Jul 2000 23:04:33 -0700 (PDT) Date: Mon, 17 Jul 2000 23:04:33 -0700 From: R Joseph Wright To: Kent Stewart Cc: freebsd-stable@FreeBSD.org Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Message-ID: <20000717230433.A478@manatee.mammalia.org> References: <20000717223751.3846.qmail@web3105.mail.yahoo.com> <20000717192441.A44452@kingsqueak.org> <20000717173708.A13211@manatee.mammalia.org> <3973B316.C4442AAF@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3973B316.C4442AAF@urx.com>; from kstewart@urx.com on Mon, Jul 17, 2000 at 06:29:58PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 06:29:58PM -0700, Kent Stewart wrote: > > > R Joseph Wright wrote: > > > > On Mon, Jul 17, 2000 at 07:24:41PM -0400, Chris wrote: > > > I like the AMD's, have a K6-3/450 here with a really heavy Alpha > > > heatsink on it and a 27cfm bearing fan. Even with that fan... it just > > > doesn't like make buildworld or building X without the case cover off > > > though. Though it's not a small problem... it still performs well for me > > > overall. My older K6/2 200 here can build all day no problem...the new > > > ones just got really hot. > > > > > > I actually had to give up on fbsd for my work desktop because the > > > cheapie fan on the K6/2 450 I have just wouldn't cut it, even with the > > > case off and the thing would just plain reboot on any moderate sized > > > builds. I just don't have the time at the office to mess with it and my > > > workstation is a management station of sorts as well. > > > > I had these problems with my K6/2 450 until I finally got out the sandpaper > > and lapped both the CPU and the heatsink. The heatsink needed it much worse > > than the CPU. I have had only one reboot since I did that while loading the > > system heavily with an X build. Even one reboot is not good, but it's much > > better than it was. > > They weren't flat or what. I found I could cook the heat transfer tape > using an overclocked Celeron. I replaced the tape with heatsink > compound but doing a build of XFree86 3.3.4 had finished cooking the > cpu. I remember reading before where you did that and was going to ask > you why. > The CPU wasn't totally flat, though not as warped as I'd heard they tended to be. The heatsink, OTOH, had a little plateau on the bottom of it about an inch wide. That is the only part of it that was in contact with the CPU, don't ask me why it was designed that way! After I got done with it, the CPU and heatsink fit together so nicely it was like they were drawn together. Then I put a thin layer of heatsink grease between them. The lapping made a big difference because now a much larger surface area is being cooled. > > > > www.pcpowercooling.com sells heavy duty heatsink/fans for many processors > > including the K6/2. If my problems ever return I plan to buy one from them. > > Another place is http://www.3dfxcool.com/. He has some fans that look > like they would lift the case off if you weren't using the cpu as a > thrust reverser. > > Kent > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://www.3-cities.com/~kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > Bomber dropping fire retardant in front of Hanford Wild fire. > http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 0:43:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 91A2637BC18; Tue, 18 Jul 2000 00:43:14 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id JAA46505; Tue, 18 Jul 2000 09:43:12 +0200 (CEST) (envelope-from asmodai) Date: Tue, 18 Jul 2000 09:43:12 +0200 From: Jeroen Ruigrok van der Werven To: John Baldwin Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: bootdisk problems/md related Message-ID: <20000718094312.A45185@lucifer.bart.nl> References: <20000717200844.I38656@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jhb@FreeBSD.ORG on Mon, Jul 17, 2000 at 02:42:04PM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000717 23:45], John Baldwin (jhb@FreeBSD.ORG) wrote: > >On 17-Jul-00 Jeroen Ruigrok van der Werven wrote: >> -On [20000717 20:05], John Baldwin (jhb@freebsd.org) wrote: >>>What exact error are you talking about? The md1 fatal error? >> >> The one I posted earlier on in this thread. md related. > >Well, I don't see it at the moment, but I assume you mean >'FATAL: can't open md1' or some such. Mounting root from ufs:/dev/md0c md0: raw parition size != slice size md0: start 0, end 855, size 856 md0c: start 0, end 5759, size 5760 md0: truncating new parition md0: rejecting partition in BSD label: it isn't entirely within the slice md0: start 0, end 855, size 856 md0a: start 0, size 5759, size 5760 spec_getpages: (#md/2) I/O read failure: (error 22) bp 0xc5f50420 vp 0xcb307ec0 size: 4096, resid: 4096, a_count: 4096, valid: 0x0 nread: 0, reqpage: 0, pindex: 405, pcount: 1 vm_fault: pager read error, pid 1 (swapper) init died (signal 6, exit 0) panic: going nowhere without my init! >>>I _know_ that is fixed in 5.0 and 4.x. If you have some other >>>error, let me know. >> >> Well, it isn't fixed for my boxen with the disks of the 15th. > >revision 1.117.2.2 >date: 2000/07/05 07:20:23; author: jkh; state: Exp; lines: +5 -1 >MFC: ignore memory disks > >What is the version of your devices.c in src/release/sysinstall? >Note that 4.1-RC1 doesn't suffer from this problem. I suspect your >sources are out of date or have a stick tag. No, no. You misunderstood something. ;) I am getting the floppies from releng4.freebsd.org. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Peace with honour... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 1:36:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id AEEC137BB44 for ; Tue, 18 Jul 2000 01:36:36 -0700 (PDT) (envelope-from noor@comrax.com) Received: from NOOR (unknown [156.27.243.27]) by dns.comrax.com (Postfix) with SMTP id 09E3D1C982 for ; Tue, 18 Jul 2000 11:36:29 +0300 (IDT) From: "Noor Dawod" To: "FreeBSD-STABLE Mailing List" Subject: Bus error / Segmentation fault. Date: Tue, 18 Jul 2000 11:34:59 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Disposition-Notification-To: "Noor Dawod" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I've installed FreeBSD 4.1-RC this morning successfully, and it works perfectly. I've then isntalled mysqld with patches successfully, Apache + PHP. I'm doing all of that on a development server we have internally. Then, I've started benchmarking mysqld performance using RadView's WebLoad application, just to send requests to the Apache server which in turn uses connections to mysql databases. Using mysqld's startup parameters, and with 20 max servers of Apache (each can serve 50 connections max), the mysqld starts dying with "Bus error" and "Segmentation fault" errors, and then restarting from safe_mysqld. Now.. I've seen mysqld run on Solaris boxes and never dying even on high loads, which brings me to the question: who's killing mysqld? Is it FreeBSD that kills mysqld because it's taking more resources than normal, or is it mysqld that kills itself? If you have any idea, advises, and why mysqld dies on FreeBSD (and not on Solaris), please share it with us. Thanks... Noor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 1:54:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B615137BCAE; Tue, 18 Jul 2000 01:54:18 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id BAA09408; Tue, 18 Jul 2000 01:55:16 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: committers@freebsd.org Cc: stable@freebsd.org Subject: 4.1-STABLE code freeze on July 20th. Date: Tue, 18 Jul 2000 01:55:16 -0700 Message-ID: <9405.963910516@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Starting on July 20th 18:00 GMT, the RELENG_4 branch should be considered frozen. That means no commits to that branch without running it by me, your friendly homicidal release engineer, first. A lot of people have been running such stuff by me already, and I appreciate that, this simply makes it official. We're also going to start releasing 4.1-RC (release candidate) releases very shortly from ftp://releng4.freebsd.org/pub/FreeBSD so that more advance testing can be done. The release candidates will be provided both in FTP-installable and ISO image format. Thank you. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 5: 5:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by hub.freebsd.org (Postfix) with ESMTP id E8FFF37B5C8 for ; Tue, 18 Jul 2000 05:05:10 -0700 (PDT) (envelope-from marki@paradise.net.nz) Received: from paradise.net.nz (203-79-95-46.apx0.paradise.net.nz [203.79.95.46]) by deborah.paradise.net.nz (8.10.1/8.10.1) with ESMTP id e6IC58L29721 for ; Wed, 19 Jul 2000 00:05:08 +1200 (NZST) Message-ID: <397447ED.4CB5B873@paradise.net.nz> Date: Wed, 19 Jul 2000 00:05:01 +1200 From: Mark Ibell X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: EXPORT of crypto in 4.1-RC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just booted the latest snapshot (0717) off releng4.freebsd.org and was suprised to find the EXPORT restriction on the crypto distribution was still present. Shouldn't this be removed considering the recent changes to U.S. encryption export laws? Cheers, Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 5: 7:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id CE96D37C040 for ; Tue, 18 Jul 2000 05:06:50 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id OAA27175 for ; Tue, 18 Jul 2000 14:06:29 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id OAA25293 for ; Tue, 18 Jul 2000 14:03:47 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C1256920.00428960 ; Tue, 18 Jul 2000 14:06:45 +0200 X-Lotus-FromDomain: ALCATEL To: stable@freebsd.org Message-ID: Date: Tue, 18 Jul 2000 14:06:42 +0200 Subject: broken linux-communicator port ? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm trying to install linux communicator from the ports, but I can't get past one bug : pc-daisy% cd /usr/ports/www/linux-netscape47-communicator/ pc-daisy% su Password: pc-daisy# make install ===> Installing for linux-netscape-communicator-4.73 ===> linux-netscape-communicator-4.73 depends on file: /compat/linux/lib/ld.so - found ===> linux-netscape-communicator-4.73 depends on executable: netscape - found ===> linux-netscape-communicator-4.73 depends on executable: netscape - found ===> linux-netscape-communicator-4.73 depends on shared library: X11.6 - found ELF interpreter /lib/ld-linux.so.2 not found *** Signal 6 Stop in /usr/ports/www/linux-netscape47-communicator. *** Error code 1 Stop in /usr/ports/www/linux-netscape47-communicator. *** Error code 1 Stop in /usr/ports/www/linux-netscape47-communicator. pc-daisy# pc-daisy# pkg_info XFree86-4.0.1 X11R6.4/XFree86 core distribution linux_base-6.1 The base set of packages needed in Linux mode netscape-remote-1.0 Utility to pass commands to running netscape process netscape-wrapper-2000.07.07 Netscape wrapper to avoid multiple invocation and more pc-daisy# pc-daisy# pushd /usr/compat/linux/sbin/ /usr/compat/linux/sbin /usr/ports/www/linux-netscape47-communicator pc-daisy# file * install-info: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, stripped ldconfig: ELF 32-bit LSB executable, Intel 80386, version 1 (Linux), statically linked, stripped sln: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, stripped pc-daisy# uname -v FreeBSD 4.0-20000710-STABLE #0: Wed Jul 12 16:21:36 CEST 2000 (the ports tree is also from 4.0-20000710-STABLE) pc-daisy# pushd /usr/compat/linux/lib/ /usr/compat/linux/lib ~ pc-daisy# ll | more total 9514 -rwxr-xr-x 1 root wheel 344890 Jul 18 13:30 ld-2.1.2.so lrwxr-xr-x 1 root wheel 17 Jul 18 10:18 ld-linux.so.1 -> ld-linux.so.1.9 .5 -rwxr-xr-x 1 root wheel 25034 Mar 22 1999 ld-linux.so.1.9.5 lrwxr-xr-x 1 root wheel 11 Jul 18 10:18 ld-linux.so.2 -> ld-2.1.2.so -rwxr-xr-x 2 root wheel 104236 Mar 22 1999 ld.so -rwxr-xr-x 2 root wheel 104236 Mar 22 1999 ld.so.1.9.5 ...... TIA TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 5: 9:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 8DFD737B5F8; Tue, 18 Jul 2000 05:09:39 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id IAA09569; Tue, 18 Jul 2000 08:09:38 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200007181209.IAA09569@blackhelicopters.org> Subject: Southeast Michigan Users' Group followup To: advocacy@freebsd.org Date: Tue, 18 Jul 2000 08:09:38 -0400 (EDT) Cc: stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I offered a couple weeks ago to organize a Southeast Michigan users' group, and asked people to mail me if they were interested. To date, I've gotten two responses. Counting me, that makes three. This a second call for interested parties. Otherwise, I think it's a bust for right now; I'll try again after BSDCon. (please pardon the crosspost to -stable; this is of marginal interest to most -stable users, but the biggest audience is on -stable. Followups to -advocacy, or just drop me a line.) ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 5:18: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 210A137BF02 for ; Tue, 18 Jul 2000 05:18:02 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id OAA01150 for ; Tue, 18 Jul 2000 14:17:40 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id OAA01756 for ; Tue, 18 Jul 2000 14:14:59 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C1256920.00438C75 ; Tue, 18 Jul 2000 14:17:48 +0200 X-Lotus-FromDomain: ALCATEL To: stable@FreeBSD.ORG Message-ID: Date: Tue, 18 Jul 2000 14:17:36 +0200 Subject: Re: broken linux-communicator port ? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it works fine after enabling the linux emulator TfH Thierry.Herbelot@alcatel.fr on 18/07/2000 14:06:42 To: stable@FreeBSD.ORG cc: (bcc: Thierry HERBELOT/FR/ALCATEL) Subject: broken linux-communicator port ? Hello, I'm trying to install linux communicator from the ports, but I can't get past one bug : pc-daisy% cd /usr/ports/www/linux-netscape47-communicator/ pc-daisy% su Password: pc-daisy# make install ===> Installing for linux-netscape-communicator-4.73 ===> linux-netscape-communicator-4.73 depends on file: /compat/linux/lib/ld.so - found ===> linux-netscape-communicator-4.73 depends on executable: netscape - found ===> linux-netscape-communicator-4.73 depends on executable: netscape - found ===> linux-netscape-communicator-4.73 depends on shared library: X11.6 - found ELF interpreter /lib/ld-linux.so.2 not found *** Signal 6 [SNIP] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 6:43: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id 2E6CE37BAA4 for ; Tue, 18 Jul 2000 06:42:55 -0700 (PDT) (envelope-from jonathan@corpex.com) Received: (qmail 86793 invoked from network); 18 Jul 2000 13:43:45 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 18 Jul 2000 13:43:45 -0000 From: "Jonathan Defries" To: Subject: rocketport and FreeBSD4 Date: Tue, 18 Jul 2000 14:43:08 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying to get a rocketport working and I get something logged in dmesg saying: WARNING: driver rp should register devices with make_dev() (dev_t = "#rp/0x10080") I can't make any cuaR* devices either, the MAKEDEV fails. If I edit MAKDEV and change references for \$first to $first the devices are then made but I cannot cu to them. Could anyone suggest any pointers? There was a single mention of the warning message on the mailing list archive but nothing since. Regards, Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 7:45:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from schnell.net (schnell.net [209.50.225.102]) by hub.freebsd.org (Postfix) with ESMTP id 2F71D37BE49 for ; Tue, 18 Jul 2000 07:45:35 -0700 (PDT) (envelope-from loschert@servint.com) Received: from delft.lan.loschert.net (207-172-86-155.s155.tnt6.rcm.va.dialup.rcn.com [207.172.86.155]) by schnell.net (8.9.3/8.9.3) with ESMTP id KAA29141 for ; Tue, 18 Jul 2000 10:45:34 -0400 (EDT) (envelope-from loschert@servint.com) Received: (qmail 17819 invoked by uid 1000); 18 Jul 2000 14:43:57 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Jul 2000 14:43:57 -0000 Date: Tue, 18 Jul 2000 10:43:57 -0400 (EDT) From: Matt Loschert X-Sender: loschert@delft.lan.loschert.net To: Graham Menhennitt Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: XFree86 4.0.1 port fails "don't know how to make: clean" In-Reply-To: <68h7nsot4mv7omd4hchrtkh7e9mk6l28a6@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Graham Menhennitt wrote: > Has anybody had any success with building the XFree86 4.0.1 port (on > 4-Stable, although I doubt that it makes an difference)? I've tried a few > times and I always get: > don't know how to make: clean > in the "doc" directory. When I look at the Makefile in that directory, it > has a size of zero bytes!! I had no problem building and installing it using the port. I removed it soon after when I couldn't get it to support my video card as well as 3.3.6. Sorry, no ideas other than trying to rm -rf /usr/ports/x11/XFree86-4 and re-suping ports-all. - Matt -- Matt Loschert loschert@servint.com Software Engineer voice (703) 847-1381 ServInt Internet Services fax (703) 847-1383 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 8: 3:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 3869137BDB3 for ; Tue, 18 Jul 2000 08:03:14 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e6IF38U23737; Tue, 18 Jul 2000 08:03:08 -0700 (PDT) Message-Id: <200007181503.e6IF38U23737@ptavv.es.net> To: Chris Cc: Richard Stanaford , freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? In-reply-to: Your message of "Mon, 17 Jul 2000 19:24:41 EDT." <20000717192441.A44452@kingsqueak.org> Date: Tue, 18 Jul 2000 08:03:08 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I, too, have a K6-3/450 and had trouble building 4.0. makeworld would seg-fault at random places, clearly a HW problem. At the urging of several on this list, I upgraded my cooling and put a thermocouple on the chip. It was no where near hot enough to exceed specs at any point I could get the probe on. So... I started looking at memory. I had 2 DIMMs, a 64 MB and a 32 MB. Neither has ECC. One was a Micron board that came with the computer and the other was Compaq board that come with my other system and became a spare when I increased the memory size on it. If I removed the Micron board, the situation did not improve at all. When I pulled the Compaq board, all was well. Of course, cooling the memory batter often makes it work better, so those opening the cab and pointing a fan into it or adding extra cooling may well "fix" a memory problem as well as a CPU problem. While the CPU might occasionally be the problem, if properly heat-sinked and ventilated, I suspect that memory is a more common problem. I saw 128 MB ECC PC133 memory at a very reasonable price at Fry's last week and I'm tempted to upgrade. I suspect it would eliminate a lot of random faults and would port to an Athlon when I upgrade. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 > Date: Mon, 17 Jul 2000 19:24:41 -0400 > From: Chris > Sender: owner-freebsd-stable@FreeBSD.ORG > > I like the AMD's, have a K6-3/450 here with a really heavy Alpha > heatsink on it and a 27cfm bearing fan. Even with that fan... it just > doesn't like make buildworld or building X without the case cover off > though. Though it's not a small problem... it still performs well for me > overall. My older K6/2 200 here can build all day no problem...the new > ones just got really hot. > > I actually had to give up on fbsd for my work desktop because the > cheapie fan on the K6/2 450 I have just wouldn't cut it, even with the > case off and the thing would just plain reboot on any moderate sized > builds. I just don't have the time at the office to mess with it and my > workstation is a management station of sorts as well. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 8:29:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rad3.1stup.com (rad3.1stup.com [209.143.242.34]) by hub.freebsd.org (Postfix) with ESMTP id B92B937C0A9 for ; Tue, 18 Jul 2000 08:29:18 -0700 (PDT) (envelope-from jim@siteplus.net) Received: from veager (JCSNB104-31.splitrock.net [209.156.121.123]) by rad3.1stup.com (8.9.3/8.9.2) with SMTP id IAA19577 for ; Tue, 18 Jul 2000 08:29:06 -0700 Message-ID: <010301bff0cc$eec8e0c0$7b799cd1@siteplus.net> From: "Jim Weeks" To: References: <200007180601.e6I61gP33511@zibbi.mikom.csir.co.za> Subject: Re: /modules/ empty in 4.x snaps Date: Tue, 18 Jul 2000 11:29:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is true. I installed a snap yesterday and ran into dependency problems. This was the last thing I did yesterday and am now away from the machine so I can't give specifics. I will dig them up tomorrow when I return, or maybe someone else has had the same problem. Jim "John Hay" Spoke the words, > I see that the /modules directory is empty in the latest 4.x snaps. > > John ________________________________________________________ 1stUp.com - Free the Web Get your free Internet access at http://www.1stUp.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 8:42:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 1CDFA37BEE3 for ; Tue, 18 Jul 2000 08:42:18 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id SAA33253; Tue, 18 Jul 2000 18:41:38 +0300 (EEST) Date: Tue, 18 Jul 2000 18:41:38 +0300 From: Ruslan Ermilov To: Jim Weeks Cc: freebsd-stable@freebsd.org Subject: Re: /modules/ empty in 4.x snaps Message-ID: <20000718184138.A33155@sunbay.com> Mail-Followup-To: Jim Weeks , freebsd-stable@freebsd.org References: <200007180601.e6I61gP33511@zibbi.mikom.csir.co.za> <010301bff0cc$eec8e0c0$7b799cd1@siteplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <010301bff0cc$eec8e0c0$7b799cd1@siteplus.net>; from jim@siteplus.net on Tue, Jul 18, 2000 at 11:29:13AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 11:29:13AM -0400, Jim Weeks wrote: > This is true. I installed a snap yesterday and ran into dependency > problems. This was the last thing I did yesterday and am now away from the > machine so I can't give specifics. I will dig them up tomorrow when I > return, or maybe someone else has had the same problem. > > Jim > > > "John Hay" > > Spoke the words, > > > I see that the /modules directory is empty in the latest 4.x snaps. > > > > John > I guess this is because modules are now (by default) built as part of the kernel build. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 9: 2: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pille.addcom.de (h-62.96.128.34.user.addcom.de [62.96.128.34]) by hub.freebsd.org (Postfix) with SMTP id 550C437BF13 for ; Tue, 18 Jul 2000 09:01:57 -0700 (PDT) (envelope-from sblank@addcom.de) Received: (qmail 4071 invoked from network); 18 Jul 2000 16:01:53 -0000 Received: from h-62.96.149.223.user.addcom.de (HELO ally.blank.de) (root@62.96.149.223) by pille.addcom.de with SMTP; 18 Jul 2000 16:01:53 -0000 Received: (from sblank@localhost) by ally.blank.de (8.10.2/8.10.2) id e6IFOq308381; Tue, 18 Jul 2000 17:24:52 +0200 (CEST) Date: Tue, 18 Jul 2000 17:24:52 +0200 From: Sascha Blank To: Thierry.Herbelot@alcatel.fr Cc: stable@freebsd.org, jmz@freebsd.org Subject: Re: lost mouse when switching back to X Message-ID: <20000718172452.A8300@ally.blank.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from Thierry.Herbelot@alcatel.fr on Mon, Jul 17, 2000 at 02:13:57PM +0200 Organization: Computer Center of the University of Trier, Germany Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Mon, Jul 17, 2000 at 02:13:57PM +0200, Thierry.Herbelot@alcatel.fr wrote: > When I switch from X-Windows to the text console and then back to > X-windows (Ctrl-Alt-F1, then Alt-F9), the mouse pointer is fixed on the > screen (When I move the "physical" mouse, the pointer stays at the same > place on the X screen). I had this problem on my 4.1-RC machine running XFree86 4.0.1 and moused(8) with a PS/2 mouse as well. So I spent some hours digging through the XFree86 source code and finally came up with a quick'n' dirty patch that cures the problem at least on my system. I haven't contacted the XFree86 people about it yet as I want to hear some more "works for me here too!" before I'll file a PR. Although it's rather late it might be a candidate for inclusion in the ports collection before the 4.1-RELEASE. *** xc/programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c.orig Sat Feb 12 21:45:41 2000 --- xc/programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c Tue Jul 18 17:04:23 2000 *************** *** 165,171 **** --- 165,175 ---- mode.rate = rate > 0 ? rate : -1; mode.resolution = res > 0 ? res : -1; mode.accelfactor = -1; + #ifdef __FreeBSD__ + mode.level = 1; + #else mode.level = -1; + #endif ioctl(pInfo->fd, MOUSE_SETMODE, &mode); } #endif *** xc/programs/Xserver/hw/xfree86/input/mouse/mouse.c.orig Sat Jul 1 01:39:02 2000 --- xc/programs/Xserver/hw/xfree86/input/mouse/mouse.c Tue Jul 18 17:10:51 2000 *************** *** 692,701 **** --- 692,706 ---- pMse->protocolID = protocolID; } } + #ifndef __FreeBSD__ memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara)); + #endif if (automatic) { if (name) { + #ifdef __FreeBSD__ + memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara)); + #endif /* Possible protoPara overrides from SetupAuto. */ for (i = 0; i < sizeof(pMse->protoPara); i++) if (protoPara[i] != -1) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 9:17:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinenut.nosc.mil (pinenut.nosc.mil [198.253.4.217]) by hub.freebsd.org (Postfix) with ESMTP id 4BD0637BEF1 for ; Tue, 18 Jul 2000 09:17:42 -0700 (PDT) (envelope-from syed@pinenut.nosc.mil) Received: (from syed@localhost) by pinenut.nosc.mil (8.9.3/8.9.3) id JAA01444; Tue, 18 Jul 2000 09:17:33 -0700 (PDT) (envelope-from syed) From: User syed Syed Message-Id: <200007181617.JAA01444@pinenut.nosc.mil> Subject: error - make installworld To: freebsd-stable@freebsd.org Date: Tue, 18 Jul 2000 09:17:33 -0700 (PDT) Reply-To: syed@nosc.mil X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG istalled 4.0-STABLE 20000717 snapshot. (followed instructions in UPDATING) did a buildworld off of an nfs mounted /usr/src (CVSUP source) did a buildkernel and installkernel (GENERIC) did not do a MAKEDEV make installworld generates the following error: ===> lib/libc_r install -c -o root -g wheel -m 444 libc_r.a /usr/lib install -c -o root -g wheel -m 444 libc_r_p.a /usr/lib install -c -s -o root -g wheel -m 444 -fschg libc_r.so.4 /usr/lib ln -sf libc_r.so.4 /usr/lib/libc_r.so install -c -o root -g wheel -m 444 pthread_attr.3.gz pthread_cancel.3.gz pthread _cleanup_pop.3.gz pthread_cleanup_push.3.gz pthread_condattr.3.gz pthread_cond_b roadcast.3.gz pthread_cond_destroy.3.gz pthread_cond_init.3.gz pthread_cond_sign al.3.gz pthread_cond_timedwait.3.gz pthread_cond_wait.3.gz pthread_create.3.gz p thread_detach.3.gz pthread_equal.3.gz pthread_exit.3.gz pthread_getspecific.3.gz pthread_join.3.gz pthread_key_create.3.gz pthread_key_delete.3.gz pthread_kill. 3.gz pthread_mutexattr.3.gz pthread_mutex_destroy.3.gz pthread_mutex_init.3.gz p thread_mutex_lock.3.gz pthread_mutex_trylock.3.gz pthread_mutex_unlock.3.gz pthr ead_once.3.gz pthread_rwlock_destroy.3.gz pthread_rwlock_init.3.gz pthread_rwloc k_rdlock.3.gz pthread_rwlock_unlock.3.gz pthread_rwlock_wrlock.3.gz pthread_rwlo ckattr_destroy.3.gz pthread_rwlockattr_getpshared.3.gz pthread_rwlockattr_init.3 .gz pthread_rwlockattr_setpshared.3.gz pthread_schedparam.3.gz pthread_self.3.gz pthread_setspecific.3.gz pthread_sigmask.3.gz pthread_testcancel.3.gz sem_destr oy.3.gz sem_getvalue.3.gz sem_init.3.gz sem_open.3.gz sem_post.3.gz sem_wait.3.g z sigwait.3.gz /usr/share/man/man3 install: pthread_attr.3.gz: No such file or directory *** Error code 71 Stop in /usr/src/lib/libc_r. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 thanks/basit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 11: 2: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 3E9AD37B5F1 for ; Tue, 18 Jul 2000 11:01:51 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id LAA46071 for ; Tue, 18 Jul 2000 11:01:49 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: stable@freebsd.org Subject: Telnet problem under 4.1-RC Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 18 Jul 2000 11:01:49 -0700 Message-ID: <46060.963943309@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I'm seeing an odd telnet problem on 4.1-RC. I track RELENG_4 and just updated my machine (pinhead) from a source checkout and build from 14-15th (Friday-Saturday) including installkernel and mergemaster. All hostname lookups are failing from telnet, but only from telnet and only hostnames. Here's the problem: $ telnet localhost localhost: No address associated with hostname $ nslookup localhost Server: localhost.parag.codegen.com Address: 127.0.0.1 Name: localhost.parag.codegen.com Address: 127.0.0.1 $ ping -c 1 localhost PING localhost.parag.codegen.com (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.167 ms --- localhost.parag.codegen.com ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.167/0.167/0.167/0.000 ms $ telnet 127.0.0.1 Trying 127.0.0.1... Connected to localhost.parag.codegen.com. Escape character is '^]'. login: ^D Connection closed by foreign host. $ ftp/ssh/etc all work fine with the same hostnames. telnet works with an IP address but fails to lookup *any* hostname - local or otherwise - so it doesn't seem to be a telnetd problem. ftp works fine to localhost. I just now updated my copy of the CVS tree and updated /usr/src but nothing in the usr.bin/telnet directory has been updated. I can't spot anything obvious in the CVS logs either. Anyone have any ideas I can try out to figure out what's going on? (Odds are I've forgotten something.) Thanks in advance. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 11:58:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 4906737B8F8 for ; Tue, 18 Jul 2000 11:58:38 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA20068; Tue, 18 Jul 2000 11:58:33 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007181858.LAA20068@freeway.dcfinc.com> Subject: Re: Telnet problem under 4.1-RC In-Reply-To: <46060.963943309@pinhead.parag.codegen.com> from Parag Patel at "Jul 18, 0 11:01:49 am" To: parag@cgt.com (Parag Patel) Date: Tue, 18 Jul 2000 11:58:32 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check your /etc/host.conf file to see if you're using the /etc/hosts file before the nameserver ("hosts" ahead of "bind"). If so, check for a valid entry in your hosts file. When you run "nslookup", it queries the nameserver directly. But most applications call "gethostbyname(3)", which (depending on the contents of /etc/host.conf and /etc/hosts) can return a different result. As I recall, Parag Patel wrote: > All hostname lookups are failing from telnet, but only from telnet and > only hostnames. Here's the problem: > > $ telnet localhost > localhost: No address associated with hostname > $ nslookup localhost > Server: localhost.parag.codegen.com > Address: 127.0.0.1 > > Name: localhost.parag.codegen.com > Address: 127.0.0.1 > > $ ping -c 1 localhost > PING localhost.parag.codegen.com (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.167 ms > > --- localhost.parag.codegen.com ping statistics --- > 1 packets transmitted, 1 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.167/0.167/0.167/0.000 ms > > $ telnet 127.0.0.1 > Trying 127.0.0.1... > Connected to localhost.parag.codegen.com. > Escape character is '^]'. > login: ^D > Connection closed by foreign host. > $ > > ftp/ssh/etc all work fine with the same hostnames. telnet works with an > IP address but fails to lookup *any* hostname - local or otherwise - so > it doesn't seem to be a telnetd problem. ftp works fine to localhost. > > I just now updated my copy of the CVS tree and updated /usr/src but > nothing in the usr.bin/telnet directory has been updated. I can't spot > anything obvious in the CVS logs either. > > Anyone have any ideas I can try out to figure out what's going on? > (Odds are I've forgotten something.) Thanks in advance. > > > -- Parag Patel > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:11: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 72C9E37B9A4 for ; Tue, 18 Jul 2000 12:10:56 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id MAA48372; Tue, 18 Jul 2000 12:10:49 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: chad@DCFinc.com Cc: stable@FreeBSD.ORG Subject: Re: Telnet problem under 4.1-RC In-Reply-To: Message from "Chad R. Larson" of "Tue, 18 Jul 2000 11:58:32 PDT." <200007181858.LAA20068@freeway.dcfinc.com> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 18 Jul 2000 12:10:49 -0700 Message-ID: <48368.963947449@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000 11:58:32 PDT, "Chad R. Larson" wrote: > >Check your /etc/host.conf file to see if you're using the /etc/hosts >file before the nameserver ("hosts" ahead of "bind"). If so, check >for a valid entry in your hosts file. I tried various combinations in /etc/host.conf, even eliminating the "hosts" entry entirely. (All the correct host addrs are also listed in /etc/hosts, even localhost.) It unfortunately makes no difference for telnet which still refuses to lookup the hostname. Screwy. I'm running the standard/default FBSD /etc/host.conf file as built/installed by mergemaster, which appears to be the same as what's under /usr/src/etc/host.conf. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:20:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id CBFDA37B513 for ; Tue, 18 Jul 2000 12:20:36 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 6657 invoked by uid 0); 18 Jul 2000 19:20:34 -0000 Received: from pc19f5d2f.dip.t-dialin.net (HELO speedy.gsinet) (193.159.93.47) by mail.gmx.net with SMTP; 18 Jul 2000 19:20:34 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA09997 for stable@FreeBSD.ORG; Tue, 18 Jul 2000 19:42:02 +0200 Date: Tue, 18 Jul 2000 19:42:02 +0200 From: Gerhard Sittig To: stable@FreeBSD.ORG Subject: Re: bioscall.s Message-ID: <20000718194202.F24476@speedy.gsinet> Mail-Followup-To: stable@FreeBSD.ORG References: <20000718015340.3073.qmail@web3102.mail.yahoo.com> <3973BA04.5AB2FFD@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3973BA04.5AB2FFD@urx.com>; from kstewart@urx.com on Mon, Jul 17, 2000 at 06:59:32PM -0700 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 18:59 -0700, Kent Stewart wrote: > > Richard Stanaford wrote: > > > > make buildkernel KERNEL="NOVA" > > The quotes are evil. One my first kernel I left if buildkernel > kernel=NOVA and it didn't work just like yours did. That was > part of the reason I needed 15 minutes for my first good build > on 7/7. This is somewhat hard to believe. Since you type this at a shell prompt, the shell will "consume" these and make just sees make buildkernel KERNEL=NOVA There must be (have been) something else in the way. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:23:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id CBE5637B94C for ; Tue, 18 Jul 2000 12:23:41 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Jul 2000 20:23:40 +0100 (BST) Date: Tue, 18 Jul 2000 20:23:40 +0100 From: David Malone To: Parag Patel Cc: chad@DCFinc.com, stable@FreeBSD.ORG Subject: Re: Telnet problem under 4.1-RC Message-ID: <20000718202340.A34472@walton.maths.tcd.ie> References: <48368.963947449@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <48368.963947449@pinhead.parag.codegen.com>; from parag@cgt.com on Tue, Jul 18, 2000 at 12:10:49PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 12:10:49PM -0700, Parag Patel wrote: > On Tue, 18 Jul 2000 11:58:32 PDT, "Chad R. Larson" wrote: > >Check your /etc/host.conf file to see if you're using the /etc/hosts > >file before the nameserver ("hosts" ahead of "bind"). If so, check > >for a valid entry in your hosts file. > > I tried various combinations in /etc/host.conf, even eliminating the > "hosts" entry entirely. (All the correct host addrs are also listed in > /etc/hosts, even localhost.) It unfortunately makes no difference for > telnet which still refuses to lookup the hostname. Screwy. > > I'm running the standard/default FBSD /etc/host.conf file as > built/installed by mergemaster, which appears to be the same as what's > under /usr/src/etc/host.conf. I think I noticed this at home, but don't seem to be able to reproduce it in college. I notice that ping seemed to work OK, what happens if you try "ping6"? Maybe this is some sort of IPv6 issue. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:29:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id C326737BA47 for ; Tue, 18 Jul 2000 12:29:37 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13Ed3e-000HCU-00 for stable@freebsd.org; Tue, 18 Jul 2000 20:29:34 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id UAA47277 for stable@freebsd.org; Tue, 18 Jul 2000 20:29:34 +0100 (BST) (envelope-from jcm) Date: Tue, 18 Jul 2000 20:29:33 +0100 From: j mckitrick To: stable@freebsd.org Subject: stupid installkernel question Message-ID: <20000718202933.A47182@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have been reading the makefiles and boot files to try to figure this one out. i ran 'make installkernel KERNEL=MERCURY''and everything works fine. But i have 2 kernels in / One is kernel, one is MERCURY. The modification date on 'kernel' is close to the one for MERCURY. WHich one does my system boot with, and which can be deleted? In /boot, the config files seem to show 'kernel' being booted. If so, why does MERCURY exist? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:32:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 3995E37BBD9 for ; Tue, 18 Jul 2000 12:32:36 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.10.1/8.10.1) with ESMTP id e6IJWTu39094; Tue, 18 Jul 2000 15:32:29 -0400 (EDT) Date: Tue, 18 Jul 2000 15:32:28 -0400 (EDT) From: jack To: "Jordan K. Hubbard" Cc: stable@freebsd.org Subject: Re: 4.1-STABLE code freeze on July 20th. In-Reply-To: <9405.963910516@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Jordan K. Hubbard wrote: > Starting on July 20th 18:00 GMT, the RELENG_4 branch should be > considered frozen. That means no commits to that branch without > running it by me, your friendly homicidal release engineer, first. Perhaps this line in release/Makefile should be smacked with a reality stick. # Where "/some/dir" is the pathname of a directory on a some # filesystem with at least 1000MB of free space, second# du -k -s /usr/release/ 1035223 /usr/release/ And that's with NODOC=YES, NOPORTS=YES :) ---- release/texts/{i386,alpha}/RELNOTES.TXT say: For the latest of these 4.0-stable snapshots, you should always see: ftp://current.freebsd.org/pub/FreeBSD ---- ^^^^^^^ The pnp(4) man page still lists the obsoleted USERCONFIG directives. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:34:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 2B1C437BAA2 for ; Tue, 18 Jul 2000 12:34:03 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id MAA53650; Tue, 18 Jul 2000 12:33:55 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: David Malone Cc: chad@DCFinc.com, stable@FreeBSD.ORG Subject: Re: Telnet problem under 4.1-RC In-Reply-To: Message from David Malone of "Tue, 18 Jul 2000 20:23:40 BST." <20000718202340.A34472@walton.maths.tcd.ie> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 18 Jul 2000 12:33:54 -0700 Message-ID: <53635.963948834@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000 20:23:40 BST, David Malone wrote: > >I think I noticed this at home, but don't seem to be able to >reproduce it in college. I notice that ping seemed to work OK, what >happens if you try "ping6"? Maybe this is some sort of IPv6 issue. Hm - I've been using a kernel without INET6 turned on since I don't need any IP6 stuff here. ping6 simply returns this: $ ping6 localhost ping6: Non-recoverable failure in name resolution $ I'll build a new kernel with INET6 turned back on and see if that makes a difference. In the meantime, I've appended "truss telnet localhost" output below. -- Parag Patel __sysctl(0xbfbff530,0x2,0x280703e8,0xbfbff52c,0x0,0x0) = 0 (0x0) mmap(0x0,32768,0x3,0x1002,-1,0x0) = 671551488 (0x28071000) geteuid() = 1000 (0x3e8) getuid() = 1000 (0x3e8) getegid() = 1000 (0x3e8) getgid() = 1000 (0x3e8) open("/var/run/ld-elf.so.hints",0,00) = 3 (0x3) read(0x3,0xbfbff510,0x80) = 128 (0x80) lseek(3,0x80,0) = 128 (0x80) read(0x3,0x28073100,0x8d) = 141 (0x8d) close(3) = 0 (0x0) access("/usr/lib/libncurses.so.5",0) = 0 (0x0) open("/usr/lib/libncurses.so.5",0,027757772610) = 3 (0x3) fstat(3,0xbfbff558) = 0 (0x0) read(0x3,0xbfbfe528,0x1000) = 4096 (0x1000) mmap(0x0,266240,0x5,0x2,3,0x0) = 671584256 (0x28079000) mmap(0x280ad000,36864,0x3,0x12,3,0x33000) = 671797248 (0x280ad000) mmap(0x280b6000,16384,0x3,0x1012,-1,0x0) = 671834112 (0x280b6000) close(3) = 0 (0x0) access("/usr/lib/libcrypto.so.1",0) = 0 (0x0) open("/usr/lib/libcrypto.so.1",0,027757772610) = 3 (0x3) fstat(3,0xbfbff558) = 0 (0x0) read(0x3,0xbfbfe528,0x1000) = 4096 (0x1000) mmap(0x0,647168,0x5,0x2,3,0x0) = 671850496 (0x280ba000) mmap(0x2814a000,53248,0x3,0x12,3,0x8f000) = 672440320 (0x2814a000) mmap(0x28157000,4096,0x3,0x1012,-1,0x0) = 672493568 (0x28157000) close(3) = 0 (0x0) access("/usr/lib/libcrypt.so.2",0) = 0 (0x0) open("/usr/lib/libcrypt.so.2",0,027757772610) = 3 (0x3) fstat(3,0xbfbff558) = 0 (0x0) read(0x3,0xbfbfe528,0x1000) = 4096 (0x1000) mmap(0x0,12288,0x5,0x2,3,0x0) = 672497664 (0x28158000) mmap(0x28159000,8192,0x3,0x12,3,0x0) = 672501760 (0x28159000) close(3) = 0 (0x0) access("/usr/lib/libmp.so.3",0) = 0 (0x0) open("/usr/lib/libmp.so.3",0,027757772610) = 3 (0x3) fstat(3,0xbfbff558) = 0 (0x0) read(0x3,0xbfbfe528,0x1000) = 4096 (0x1000) mmap(0x0,40960,0x5,0x2,3,0x0) = 672509952 (0x2815b000) mmap(0x28164000,4096,0x3,0x12,3,0x8000) = 672546816 (0x28164000) close(3) = 0 (0x0) access("/usr/lib/libipsec.so.1",0) = 0 (0x0) open("/usr/lib/libipsec.so.1",0,027757772610) = 3 (0x3) fstat(3,0xbfbff558) = 0 (0x0) read(0x3,0xbfbfe528,0x1000) = 4096 (0x1000) mmap(0x0,24576,0x5,0x2,3,0x0) = 672550912 (0x28165000) mmap(0x2816a000,4096,0x3,0x12,3,0x4000) = 672571392 (0x2816a000) close(3) = 0 (0x0) access("/usr/lib/libc.so.4",0) = 0 (0x0) open("/usr/lib/libc.so.4",0,027757772610) = 3 (0x3) fstat(3,0xbfbff558) = 0 (0x0) read(0x3,0xbfbfe528,0x1000) = 4096 (0x1000) mmap(0x0,598016,0x5,0x2,3,0x0) = 672575488 (0x2816b000) mmap(0x281e7000,16384,0x3,0x12,3,0x7b000) = 673083392 (0x281e7000) mmap(0x281eb000,73728,0x3,0x1012,-1,0x0) = 673099776 (0x281eb000) close(3) = 0 (0x0) sigaction(SIGILL,0xbfbff5b0,0xbfbff598) = 0 (0x0) sigprocmask(0x1,0x0,0x2807031c) = 0 (0x0) sigaction(SIGILL,0xbfbff598,0x0) = 0 (0x0) readlink("/etc/malloc.conf",0xbfbff3d4,63) ERR#2 'No such file or directory' mmap(0x0,4096,0x3,0x1002,-1,0x0) = 673173504 (0x281fd000) break(0x8065000) = 0 (0x0) break(0x8066000) = 0 (0x0) break(0x8067000) = 0 (0x0) break(0x8068000) = 0 (0x0) break(0x8069000) = 0 (0x0) __sysctl(0xbfbff45c,0x2,0xbfbff4b0,0xbfbff458,0x0,0x0) = 0 (0x0) ioctl(0,TIOCGETA,0x805f360) = 0 (0x0) sigprocmask(0x1,0x0,0x805f3dc) = 0 (0x0) open("/etc/services",0,0666) = 3 (0x3) fstat(3,0xbfbff2f4) = 0 (0x0) break(0x806b000) = 0 (0x0) read(0x3,0x8069000,0x2000) = 8192 (0x2000) close(3) = 0 (0x0) open("/etc/services",0,0666) = 3 (0x3) fstat(3,0xbfbff2b4) = 0 (0x0) read(0x3,0x8069000,0x2000) = 8192 (0x2000) close(3) = 0 (0x0) open("/etc/services",0,0666) = 3 (0x3) fstat(3,0xbfbff254) = 0 (0x0) read(0x3,0x8069000,0x2000) = 8192 (0x2000) close(3) = 0 (0x0) open("/etc/services",0,0666) = 3 (0x3) fstat(3,0xbfbff2b4) = 0 (0x0) read(0x3,0x8069000,0x2000) = 8192 (0x2000) close(3) = 0 (0x0) open("/etc/services",0,0666) = 3 (0x3) fstat(3,0xbfbff254) = 0 (0x0) read(0x3,0x8069000,0x2000) = 8192 (0x2000) close(3) = 0 (0x0) localhost: No address associated with hostname write(2,0xbfbfee3c,47) = 47 (0x2f) getuid() = 1000 (0x3e8) setuid(0x3e8) = 0 (0x0) exit(0x1) process exit, rval = 256 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:42:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 4B24537B921 for ; Tue, 18 Jul 2000 12:42:14 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 7ABBB195F4; Tue, 18 Jul 2000 14:42:09 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id OAA01552; Tue, 18 Jul 2000 14:42:09 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Tue, 18 Jul 2000 14:42:09 -0500 From: "Jacques A. Vidrine" To: "Jordan K. Hubbard" Cc: Graham Wheeler , Kazutaka YOKOTA , freebsd-stable@freebsd.org Subject: Re: FreeBSD-4.0S/psmintr out of sync/Synaptics Touchpad Message-ID: <20000718144209.A1502@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , "Jordan K. Hubbard" , Graham Wheeler , Kazutaka YOKOTA , freebsd-stable@freebsd.org References: <252f164763d80f7d24a27596529b8450@cequrux.com> <330.963785187@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <330.963785187@localhost>; from jkh@zippy.osd.bsdi.com on Sun, Jul 16, 2000 at 03:06:27PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 16, 2000 at 03:06:27PM -0700, Jordan K. Hubbard wrote: > The psm driver isn't suffering from this problem in -stable, thank > god, and can still be used safely in the upcoming 4.1-RELEASE. Actually, it is here, on a UP system, if this is the message you mean: Jul 18 14:21:18 hamlet /kernel: psmintr: out of sync (00c0 != 0000). The symptoms are as you describe. The mouse in question is a ``Cordless MouseMan Pro''. The problems are /much/ worse with a Microsoft Optical Intellimouse -- so bad as to be unusable. See also PR misc/16969. This is a new system, and the first time I've noticed the problem. I'm just trying to ignore it for the moment :-) -- Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:44:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web3104.mail.yahoo.com (web3104.mail.yahoo.com [204.71.202.189]) by hub.freebsd.org (Postfix) with SMTP id 9972437B9E8 for ; Tue, 18 Jul 2000 12:44:54 -0700 (PDT) (envelope-from rsstan@yahoo.com) Message-ID: <20000718194450.15587.qmail@web3104.mail.yahoo.com> Received: from [150.159.224.8] by web3104.mail.yahoo.com; Tue, 18 Jul 2000 12:44:50 PDT Date: Tue, 18 Jul 2000 12:44:50 -0700 (PDT) From: Richard Stanaford Subject: Re: bioscall.s To: Gerhard Sittig , stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Gerhard Sittig wrote: > > This is somewhat hard to believe. Since you type this at a shell > prompt, the shell will "consume" these and make just sees > > make buildkernel KERNEL=NOVA > > There must be (have been) something else in the way. In the way of what? 'make buildkernel blah' will build the GENERIC kernel by default. Try it. It was the first mistake I made after a successful buildworld on my other box. I didn't correctly argument the command and entered.. make buildkernel NEBULA (Nebula is my DX4/100) and the GENERIC build started. I broke out of it... inputted ... make buildkernel KERNEL="NEBULA" and the build completed just fine. As long as you get the "make buildkernel" correct, it *will* build something. -Richard __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:46:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 3927037B921 for ; Tue, 18 Jul 2000 12:46:30 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id MAA00597; Tue, 18 Jul 2000 12:46:17 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: David Malone , chad@DCFinc.com Cc: stable@FreeBSD.ORG Subject: Re: Telnet problem under 4.1-RC In-Reply-To: Message from Parag Patel of "Tue, 18 Jul 2000 12:33:54 PDT." <53635.963948834@pinhead.parag.codegen.com> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 18 Jul 2000 12:46:17 -0700 Message-ID: <593.963949577@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000 12:33:54 PDT, Parag Patel wrote: > >I'll build a new kernel with INET6 turned back on and see if that makes >a difference. Nope - no difference. Sigh. (No .telnetrc either.) -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 12:51:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 11A1837B513 for ; Tue, 18 Jul 2000 12:51:17 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA25269; Tue, 18 Jul 2000 12:47:43 -0700 (PDT) Date: Tue, 18 Jul 2000 12:47:43 -0700 From: Brooks Davis To: j mckitrick Cc: stable@FreeBSD.ORG Subject: Re: stupid installkernel question Message-ID: <20000718124743.A24589@orion.ac.hmc.edu> References: <20000718202933.A47182@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000718202933.A47182@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Tue, Jul 18, 2000 at 08:29:33PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 08:29:33PM +0100, j mckitrick wrote: > > i have been reading the makefiles and boot files to try to figure this one > out. i ran 'make installkernel KERNEL=MERCURY''and everything works fine. > But i have 2 kernels in / > One is kernel, one is MERCURY. The modification date on 'kernel' is close > to the one for MERCURY. WHich one does my system boot with, and which can > be deleted? > > In /boot, the config files seem to show 'kernel' being booted. If so, why > does MERCURY exist? kernel is almost certaintly entierly unrelated to MERCURY except possiably by coincidence. The installkernel command you gave should install a kernel named /MERCURY and new modules in /modules. You either need to follow the insturctions in UPDATING to replace /kernel with MERCURY or edit your /boot/loader.conf to book /MERCURY instead of /kernel. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 13:13:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 5E06A37B924 for ; Tue, 18 Jul 2000 13:13:52 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.89.241]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000718211303.NXZI3760.mta02-svc.ntlworld.com@parish.my.domain>; Tue, 18 Jul 2000 21:13:03 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id VAA02478; Tue, 18 Jul 2000 21:13:29 +0100 (BST) (envelope-from mark) Date: Tue, 18 Jul 2000 21:13:29 +0100 From: Mark Ovens To: j mckitrick Cc: stable@freebsd.org Subject: Re: stupid installkernel question Message-ID: <20000718211328.E239@parish> References: <20000718202933.A47182@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000718202933.A47182@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Tue, Jul 18, 2000 at 08:29:33PM +0100 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 08:29:33PM +0100, j mckitrick wrote: > > i have been reading the makefiles and boot files to try to figure this one > out. i ran 'make installkernel KERNEL=MERCURY''and everything works fine. > But i have 2 kernels in / > One is kernel, one is MERCURY. The modification date on 'kernel' is close > to the one for MERCURY. WHich one does my system boot with, and which can > be deleted? > > In /boot, the config files seem to show 'kernel' being booted. If so, why > does MERCURY exist? > The one thing that most people seemed to miss in the long "HEADS UP! Always use the 'make buildkernel' target to make" thread was David Bushong's post about using ``makeoptions KERNEL=kernel'' in your kernel config file. My last make world a few days ago I did added that line to my kernel config file (PARISH) and ran: # make buildkernel KERNEL=PARISH # make installkernel KERNEL=PARISH and the new kernel was installed as ``kernel''. There wasn't a PARISH to be seen: # ls -l /kernel* -r-xr-xr-x 1 root wheel 2130600 14 Jul 22:40 /kernel -rw-r--r-- 1 root wheel 0 22 Jan 13:40 /kernel.config -r-xr-xr-x 1 root wheel 2101964 14 Jul 19:54 /kernel.good -r-xr-xr-x 1 root wheel 2101964 21 May 04:24 /kernel.old # (kernel.good was my own manual backup, just in case I misunderstood or got it wrong). HTH > jm > -- > ------------------------------------------------------------------- > Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: > "Your tyranny I was part of, is now cracking on every side. > Now your own life is in danger. Your Empire is on fire." Front 242 > ------------------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 13:19:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0B41937B9C5; Tue, 18 Jul 2000 13:19:06 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA13164; Tue, 18 Jul 2000 13:19:05 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 18 Jul 2000 13:19:05 -0700 (PDT) From: Kris Kennaway To: Parag Patel Cc: stable@freebsd.org Subject: Re: Telnet problem under 4.1-RC In-Reply-To: <46060.963943309@pinhead.parag.codegen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Parag Patel wrote: > Hello. I'm seeing an odd telnet problem on 4.1-RC. I track RELENG_4 > and just updated my machine (pinhead) from a source checkout and build > from 14-15th (Friday-Saturday) including installkernel and mergemaster. > > All hostname lookups are failing from telnet, but only from telnet and > only hostnames. Here's the problem: This looks suspiciously like the result of not having picked up a change to telnet which I committed on Friday night US time (along with the rest of the KAME code). This seems to correlate with your cvsup time - did you perhaps cvsup during my commit window when I asked people not to? ;-) You should have revision 1.21.2.1 of usr.bin/telnet/commands.c - please confirm ASAP whether this is the case. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14: 6:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id EB25D37B556 for ; Tue, 18 Jul 2000 14:06:47 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 7139D15510; Tue, 18 Jul 2000 14:06:46 -0700 (PDT) Date: Tue, 18 Jul 2000 14:06:46 -0700 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: Color ls Message-ID: <20000718140646.B76011@lunatic.oneinsane.net> Reply-To: Ron Rosson Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD lunatic.oneinsane.net 4.0-STABLE X-Moon: The Moon is Waning Gibbous (96% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 2:00PM up 6 days, 14:20, 1 user, load averages: 1.09, 1.05, 1.05 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the change to ls having the 'G' switch addded is there a way to get it to show colors in other than cons25. I read the man page and it is not clear on this. TIA -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ Look at my tagline, ye mighty, and despair! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14: 9:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [198.143.31.30]) by hub.freebsd.org (Postfix) with ESMTP id 4D16237BB47 for ; Tue, 18 Jul 2000 14:09:24 -0700 (PDT) (envelope-from mi@privatelabs.com) Received: from misha.privatelabs.com (misha.privatelabs.com [198.143.31.6]) by privatecube.privatelabs.com (8.9.3/8.9.2) with ESMTP id QAA22565 for ; Tue, 18 Jul 2000 16:08:54 -0400 Received: (from mi@localhost) by misha.privatelabs.com (8.9.3/8.9.3) id RAA08113 for stable@freebsd.org; Tue, 18 Jul 2000 17:07:06 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200007182107.RAA08113@misha.privatelabs.com> Subject: ghostscript port anyone? (clock(3) ?) To: stable@freebsd.org Date: Tue, 18 Jul 2000 17:07:06 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears, the ghostscript-6.01 port no longer builds :( The line: ./obj/genarch ./obj/arch.h hangs forever eating all of the available CPU (or one of the CPUs). The ghostscript's clever way of determining the host's cache size appears to be the culprit :( If I run the line under debugger, whenever I Ctrl-Z it, it is in memset: Program received signal SIGTSTP, Stopped (user). 0x280db81f in memset () from /usr/lib/libc.so.4 (gdb) where #0 0x280db81f in memset () from /usr/lib/libc.so.4 #1 0x804a400 in buf.31 () #2 0x8048a18 in main (argc=2, argv=0xbfbffb50) at ./src/genarch.c:202 #3 0x80484f5 in _start () So it keeps on memset-ing the buffer forever. Take a look at the gs6.01/src/genarch.c:202 and the time_clear function itself. Did our clock(3) change recently? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14:13:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 5552F37BB40 for ; Tue, 18 Jul 2000 14:13:46 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with ESMTP id OAA11051; Tue, 18 Jul 2000 14:13:33 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id OAA22941; Tue, 18 Jul 2000 14:13:32 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id RAA01322; Tue, 18 Jul 2000 17:13:32 -0400 (EDT) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14708.51324.220209.189331@hip186.ch.intel.com> Date: Tue, 18 Jul 2000 14:13:32 -0700 (MST) To: Ron Rosson Subject: Re: Color ls In-Reply-To: <20000718140646.B76011@lunatic.oneinsane.net> References: <20000718140646.B76011@lunatic.oneinsane.net> X-Mailer: VM 6.75 under Emacs 20.6.3 Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Tuesday, July 18, Ron 'The InSaNe One' Rosson wrote: ] > > With the change to ls having the 'G' switch addded is there a way to get > it to show colors in other than cons25. I read the man page and it is > not clear on this. > > TIA Hmmmm. I didn't even see the -G switch get put in there, but I can't make ls output any colors. For years I've always just compiled GNU ls out of fileutils and named it 'gls' and used an alias .... not pretty but it works. There's a utility there in fileutils called dircolors which spews shell code to set an ENV variable (so that GNU ls understands which colors to use) given the appropritate ".dir_colors" file. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14:16:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2D7C937BB82; Tue, 18 Jul 2000 14:16:32 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA20965; Tue, 18 Jul 2000 14:16:32 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 18 Jul 2000 14:16:32 -0700 (PDT) From: Kris Kennaway To: "Ron 'The InSaNe One' Rosson" Cc: freebsd-stable@freebsd.org Subject: Re: Color ls In-Reply-To: <20000718140646.B76011@lunatic.oneinsane.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote: > With the change to ls having the 'G' switch addded is there a way to get > it to show colors in other than cons25. I read the man page and it is > not clear on this. Use a termcap that supports colours. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14:27:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 323B337BB9B; Tue, 18 Jul 2000 14:27:44 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id OAA01815; Tue, 18 Jul 2000 14:27:42 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: Kris Kennaway Cc: stable@FreeBSD.org Subject: Re: Telnet problem under 4.1-RC In-Reply-To: Message from Kris Kennaway of "Tue, 18 Jul 2000 13:19:05 PDT." Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 18 Jul 2000 14:27:42 -0700 Message-ID: <1811.963955662@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000 13:19:05 PDT, Kris Kennaway wrote: > >This looks suspiciously like the result of not having picked up a change >to telnet which I committed on Friday night US time (along with the rest >of the KAME code). This seems to correlate with your cvsup time - did you >perhaps cvsup during my commit window when I asked people not to? ;-) Sure looks like that is indeed what happened. I just now cvsup-ed and updated my source tree, rebuilt and installed telnet, and it seems to work now. Thanks and sorry for the trouble. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14:30:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 128EC37BB79; Tue, 18 Jul 2000 14:30:19 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id OAA01921; Tue, 18 Jul 2000 14:30:17 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: Kris Kennaway , stable@FreeBSD.ORG Subject: Re: Telnet problem under 4.1-RC In-Reply-To: Message from Parag Patel of "Tue, 18 Jul 2000 14:27:42 PDT." <1811.963955662@pinhead.parag.codegen.com> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 18 Jul 2000 14:30:17 -0700 Message-ID: <1912.963955817@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What threw me was that I tried a binary telnet built about 2 months ago from another machine and it also behaved the same, ie badly. I just assumed that since the old telnet didn't work either, that the problem wasn't in telnet but more likely the kernel or libraries. Thanks again! -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14:36:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 9CD5A37B80B for ; Tue, 18 Jul 2000 14:36:55 -0700 (PDT) (envelope-from touch@ISI.EDU) Received: from isi.edu (ras02.isi.edu [128.9.176.102]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA15714; Tue, 18 Jul 2000 14:36:44 -0700 (PDT) Message-ID: <3974BFE9.8789DB61@isi.edu> Date: Tue, 18 Jul 2000 13:36:57 -0700 From: Joe Touch X-Mailer: Mozilla 4.73 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: itojun@iijlab.net Cc: snap-users@kame.net, Lars Eggert , stable@freebsd.org, xbone@ISI.EDU, touch@ISI.EDU Subject: Re: (KAME-snap 2950) Re: KAME/FreeBSD-stable merge References: <17780.963892204@coconut.itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG itojun@iijlab.net wrote: > > >The current KAME code does not support multiple tunnels between two > >hosts on a single interface. This restores that capability, which is > >required for setting up different overlay networks which use the same > >pairs of hosts. > > if you consider inbound packets, it does not make sense to have > multiple tunnel interfaces for the same pair of outer addresses . There are two alternatives: #1- multiple tunnels with the same outer wrapper #2- aliases on a GIF The analogy of #2 is ethernet with aliases; a single outer wrapper (ethernet MAC address) on different inner IP src/dest pairs. We note that it is feasible and possible to assign multiple ethernets the same MAC address with different IP addresses, resulting in #1. We are currently trying to determine if aliases suffice, and will post our results when tests are complete. However, we consider aliases _much_ more of a 'hack' than generalizing the capability of GIF tunnels. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 14:59:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 8CEA837B896; Tue, 18 Jul 2000 14:59:20 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id OAA94887; Tue, 18 Jul 2000 14:59:20 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 14:59:20 -0700 From: Matthew Hunt To: Kris Kennaway Cc: "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000718145920.B94689@wopr.caltech.edu> References: <20000718140646.B76011@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.ORG on Tue, Jul 18, 2000 at 02:16:32PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 02:16:32PM -0700, Kris Kennaway wrote: > On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote: > > > With the change to ls having the 'G' switch addded is there a way to get > > it to show colors in other than cons25. I read the man page and it is > > not clear on this. > > Use a termcap that supports colours. For example, "xterm-color" in an xterm. Does anyone know why XFree86's xterm, as shipped, doesn't set TERM to xterm-color? Is it for fear of an xterm-color entry not existing (either on the local machine, or machines you telnet/ssh to from the xterm)? -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15: 3:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [216.139.128.6]) by hub.freebsd.org (Postfix) with ESMTP id EBEB037BB7B for ; Tue, 18 Jul 2000 15:03:34 -0700 (PDT) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [216.139.128.3]) by mail.nyct.net (8.9.3/8.8.7) with ESMTP id SAA62773 for ; Tue, 18 Jul 2000 18:03:42 -0400 (EDT) (envelope-from efutch@nyct.net) Date: Tue, 18 Jul 2000 18:03:51 -0400 (EDT) From: "Eric D. Futch" To: freebsd-stable@freebsd.org Subject: hosts.allow strangeness? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is confusing the hell out of me :) I don't think I'm missing anything here, but even with "ALL : ALL : deny" in the hosts.allow I can still telnet into this FreeBSD 4.1-RC box. # cat /etc/inetd.conf | grep telnet telnet stream tcp nowait root /usr/libexec/telnetd telnetd -l -h telnet stream tcp6 nowait root /usr/libexec/telnetd telnetd # cat /etc/hosts.allow ALL : ALL : deny (from another computer) # telnet www.xxx.yyy.zzz Trying aaa.bbb.ccc.ddd.... Connected to aaa.bbb.ccc.ddd Escape character is '^]'. login: ^C telnet> quit Feel free to pass the point hat if I really missed something trivial here. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" KNYC: 18-Jul-00 16:51 EDT: 87.1 F (30.6 C), partly cloudy, humidity 38% To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15: 6:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by hub.freebsd.org (Postfix) with ESMTP id 8D98837BB7B for ; Tue, 18 Jul 2000 15:06:20 -0700 (PDT) (envelope-from micheloo@xs4all.nl) Received: from list1.xs4all.nl (list1.xs4all.nl [194.109.6.52]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id AAA29462 for ; Wed, 19 Jul 2000 00:06:18 +0200 (CEST) Received: (from root@localhost) by list1.xs4all.nl (8.9.3/8.9.3) id AAA04657; Wed, 19 Jul 2000 00:06:18 +0200 (CEST) From: micheloo@xs4all.nl (Michel Oosterhof) To: freebsd-stable@freebsd.org X-Via: imploder /usr/local/lib/mail/news2mail/news2mail at list1.xs4all.nl Subject: Default syslog logs Date: 19 Jul 2000 00:06:13 +0200 Organization: XS4ALL, Networking for the masses Message-ID: <8l2kcl$8uj$1@xs3.xs4all.nl> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I only today noticed that the default logging of syslog is not very elaborate. For example, it never showed failed logins by ssh (or succesful logings). Is there any why the default logging priorities are so high that things like this do not get written to file? michel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15:10:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gloria.cord.edu (gloria.cord.edu [138.129.254.6]) by hub.freebsd.org (Postfix) with ESMTP id 0059C37B9A8; Tue, 18 Jul 2000 15:10:19 -0700 (PDT) (envelope-from twschulz@gloria.cord.edu) Received: from localhost (twschulz@localhost) by gloria.cord.edu (8.9.0/8.9.1) with ESMTP id RAA15515; Tue, 18 Jul 2000 17:10:04 -0500 (CDT) Date: Tue, 18 Jul 2000 17:10:04 -0500 (CDT) From: Trenton Schulz To: Matthew Hunt Cc: Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-Reply-To: <20000718145920.B94689@wopr.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Matthew Hunt wrote: > On Tue, Jul 18, 2000 at 02:16:32PM -0700, Kris Kennaway wrote: > > On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote: > > > > > With the change to ls having the 'G' switch addded is there a way to get > > > it to show colors in other than cons25. I read the man page and it is > > > not clear on this. > > > > Use a termcap that supports colours. > > For example, "xterm-color" in an xterm. > > Does anyone know why XFree86's xterm, as shipped, doesn't set > TERM to xterm-color? Is it for fear of an xterm-color entry > not existing (either on the local machine, or machines you > telnet/ssh to from the xterm)? I pretty sure that is the culprit. I know that on a sparc-netbsd machine I login to on a regular basis doesn't have an xterm-color. And I've known friends who've been bitten by this on other Unices. In the end, it's probably better just to modify .Xdefaults to make your xterm "look color" -- Trenton Schulz twschulz@cord.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15:17:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 49C2237B6CF for ; Tue, 18 Jul 2000 15:17:21 -0700 (PDT) (envelope-from gshapiro@gshapiro.net) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.0.Gamma1/8.11.0.Gamma1) id e6IMHF003202; Tue, 18 Jul 2000 15:17:15 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14708.55147.55500.614625@horsey.gshapiro.net> Date: Tue, 18 Jul 2000 15:17:15 -0700 (PDT) From: Gregory Neil Shapiro To: "Eric D. Futch" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: hosts.allow strangeness? In-Reply-To: References: X-Mailer: VM 6.75 under 21.2 (beta34) "Molpe" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG efutch> This is confusing the hell out of me :) I don't think I'm missing efutch> anything here, but even with "ALL : ALL : deny" in the hosts.allow efutch> I can still telnet into this FreeBSD 4.1-RC box. efutch> # cat /etc/inetd.conf | grep telnet efutch> telnet stream tcp nowait root /usr/libexec/telnetd telnetd -l -h efutch> telnet stream tcp6 nowait root /usr/libexec/telnetd telnetd efutch> # cat /etc/hosts.allow efutch> ALL : ALL : deny Are you starting inetd with -w? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15:18:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 14DB537BB5B for ; Tue, 18 Jul 2000 15:18:38 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.10.1/8.10.1) with ESMTP id e6IMIXu46321; Tue, 18 Jul 2000 18:18:33 -0400 (EDT) Date: Tue, 18 Jul 2000 18:18:32 -0400 (EDT) From: jack To: "Eric D. Futch" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: hosts.allow strangeness? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Eric D. Futch wrote: > This is confusing the hell out of me :) I don't think I'm missing > anything here, but even with "ALL : ALL : deny" in the hosts.allow I can > still telnet into this FreeBSD 4.1-RC box. Was inetd(8) started with the -w flag? -w Turn on TCP Wrapping for external services. See the IMPLEMENTATION NOTES section for more information on TCP Wrappers support. -W Turn on TCP Wrapping for internal services which are built in to inetd. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15:19: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [216.139.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 8D30F37B57D for ; Tue, 18 Jul 2000 15:19:03 -0700 (PDT) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [216.139.128.3]) by mail.nyct.net (8.9.3/8.8.7) with ESMTP id SAA66327 for ; Tue, 18 Jul 2000 18:19:20 -0400 (EDT) (envelope-from efutch@nyct.net) Date: Tue, 18 Jul 2000 18:19:29 -0400 (EDT) From: "Eric D. Futch" To: freebsd-stable@FreeBSD.ORG Subject: Re: hosts.allow strangeness? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok never mind :) Forgot to add -w to inetd when I killed/restarted it. Thanks to "J. Westfall" for pointing out my mistake. Pointy hat please :) (I've already started a collection). -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" KNYC: 18-Jul-00 17:51 EDT: 86.0 F (30.0 C), partly cloudy, humidity 33% On Tue, 18 Jul 2000, Eric D. Futch wrote: >This is confusing the hell out of me :) I don't think I'm missing >anything here, but even with "ALL : ALL : deny" in the hosts.allow I can >still telnet into this FreeBSD 4.1-RC box. > ># cat /etc/inetd.conf | grep telnet >telnet stream tcp nowait root /usr/libexec/telnetd telnetd -l -h >telnet stream tcp6 nowait root /usr/libexec/telnetd telnetd > ># cat /etc/hosts.allow >ALL : ALL : deny > >(from another computer) ># telnet www.xxx.yyy.zzz >Trying aaa.bbb.ccc.ddd.... >Connected to aaa.bbb.ccc.ddd >Escape character is '^]'. >login: ^C >telnet> quit > >Feel free to pass the point hat if I really missed something trivial here. > >-- >Eric Futch New York Connect.Net, Ltd. >efutch@nyct.net Technical Support Staff >http://www.nyct.net (212) 293-2620 >"Bringing New York The Internet Access It Deserves" >KNYC: 18-Jul-00 16:51 EDT: 87.1 F (30.6 C), partly cloudy, humidity 38% > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 15:54:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 1148237BDD7 for ; Tue, 18 Jul 2000 15:54:40 -0700 (PDT) (envelope-from jcwells@nwlink.com) Received: from utah (jcwells@utah.nwlink.com [209.20.130.41]) by smtp.nwlink.com (8.9.3/8.9.3) with SMTP id PAA05614; Tue, 18 Jul 2000 15:54:33 -0700 (PDT) Date: Tue, 18 Jul 2000 16:06:28 -0700 (PDT) From: "Jason C. Wells" X-Sender: jcwells@utah To: Philippe Le Berre Cc: stable@FreeBSD.ORG Subject: Re: How to installworld remotely? In-Reply-To: <4.3.2.7.2.20000717130800.00c18840@212.129.1.43> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Philippe Le Berre wrote: > After being through the high numbers of emails on the new *build* > procedure, I still haven't see any hint on how to handle the make > installworld remotely. Can I do it without the shutdown? Can I remotely log > on *shutdown* system ? Do I have to fly to the box? If you reboot a freshly installed world and kernel remotely you are very much flirting with disaster. If your current install is working just fine, I say the risk outways the benefit. If your current install is crashing for what ever reason, then it might be worth it to risk the reboot. What is your tolerance for pain? :) I would not risk a short notice airfare where waiting for a more opportune time is possible. Do you know an admin who lives near the box? This is just my $.02. Thank you, Jason C. Wells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 16:51:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front002.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id C91C737B81B for ; Tue, 18 Jul 2000 16:51:42 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave.uhring.com) by front002.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 13368283; Tue, 18 Jul 2000 19:50:41 -0400 From: David Uhring To: sean@rentul.net Subject: Re: is the ensoniq 1371 sound chip supported? Date: Tue, 18 Jul 2000 18:46:55 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-stable@freebsd.org MIME-Version: 1.0 Message-Id: <00071818513700.03027@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't get mine to work, either. The kernel is compiled with device pcm and dmesg shows that the kernel recognizes the card. What /dev/ have to be made? There is no pcm0 in /dev and MAKEDEV reports no such device, although pcm0 appears in dmesg. Running RELENG_4 compiled 12 Jul 00. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 16:56:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 5DB1037B88C for ; Tue, 18 Jul 2000 16:56:55 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id RAA29835; Tue, 18 Jul 2000 17:56:34 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id RAA07204; Tue, 18 Jul 2000 17:56:32 -0600 (MDT) (envelope-from nate) Date: Tue, 18 Jul 2000 17:56:32 -0600 (MDT) Message-Id: <200007182356.RAA07204@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jacques A. Vidrine" Cc: "Jordan K. Hubbard" , Graham Wheeler , Kazutaka YOKOTA , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD-4.0S/psmintr out of sync/Synaptics Touchpad In-Reply-To: <20000718144209.A1502@hamlet.nectar.com> References: <252f164763d80f7d24a27596529b8450@cequrux.com> <330.963785187@localhost> <20000718144209.A1502@hamlet.nectar.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The psm driver isn't suffering from this problem in -stable, thank > > god, and can still be used safely in the upcoming 4.1-RELEASE. > > Actually, it is here, on a UP system, if this is the message you mean: > Jul 18 14:21:18 hamlet /kernel: psmintr: out of sync (00c0 != 0000). > > The symptoms are as you describe. The mouse in question is a > ``Cordless MouseMan Pro''. The problems are /much/ worse with a > Microsoft Optical Intellimouse -- so bad as to be unusable. See also PR > misc/16969. > > This is a new system, and the first time I've noticed the problem. I'm > just trying to ignore it for the moment :-) FWIW, I have these problems on a UP system with a Cordless Mouseman, but if I plug in my old-reliable logitech ps/2 mouse and have it probed at bootup, *then* switch to my wireless mouse (I know, I could blow up my controller that way), everything works fine. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 16:59:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 6CCE537BC13; Tue, 18 Jul 2000 16:58:56 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13EhDP-000E2g-00; Wed, 19 Jul 2000 00:55:55 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13EhDP-000NAZ-00; Wed, 19 Jul 2000 00:55:55 +0100 Date: Wed, 19 Jul 2000 00:55:55 +0100 From: Ben Smithurst To: Matthew Hunt Cc: Kris Kennaway , Ron 'The InSaNe One' Rosson , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719005555.W4668@strontium.scientia.demon.co.uk> References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="lHNupHuuosULgVTo" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000718145920.B94689@wopr.caltech.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --lHNupHuuosULgVTo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Matthew Hunt wrote: > Does anyone know why XFree86's xterm, as shipped, doesn't set > TERM to xterm-color? Is it for fear of an xterm-color entry > not existing (either on the local machine, or machines you > telnet/ssh to from the xterm)? ok, next question. If that's the case, why don't we change our termcap so that "xterm" and "xterm-color" are the same thing, and "xterm-mono" is there for people who _reall_ don't want color, or have a monochrome display, or whatever. It seems really dumb not to have colour by default, but perhaps there's a good reason. /me runs away for fear of annoying people by even daring to suggest this. --=20 Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / --lHNupHuuosULgVTo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: LNCk8nYa3wajxBYC+FS4TbdyzRdol39O iQCVAwUBOXTuiisPVtiZOS99AQGoJAP+KO0XEh73cpR0SIKZpboWhjFZZxdZ5YvR T9HELpP2SMOdOeWg+Rk5oaKN7bFj20stzcCb9j0DNLEFwa8apjxWGGHn6CzE9g0+ b7FB0QV/8kr3DPHtKWmeeVmxcpkK43xJS3Y9mG9AqHz65BigQPoXEyAbmXcRy5wR YO4tES9+bdQ= =0/D8 -----END PGP SIGNATURE----- --lHNupHuuosULgVTo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17: 4:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 525CD37B82F; Tue, 18 Jul 2000 17:04:22 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id RAA97677; Tue, 18 Jul 2000 17:04:20 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 17:04:20 -0700 From: Matthew Hunt To: Ben Smithurst Cc: Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000718170420.A97601@wopr.caltech.edu> References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719005555.W4668@strontium.scientia.demon.co.uk>; from ben@freebsd.org on Wed, Jul 19, 2000 at 12:55:55AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 12:55:55AM +0100, Ben Smithurst wrote: > If that's the case, why don't we change our termcap so that "xterm" and > "xterm-color" are the same thing, and "xterm-mono" is there for people > who _reall_ don't want color, or have a monochrome display, or whatever. > It seems really dumb not to have colour by default, but perhaps there's > a good reason. FWIW, I've just tried "TERM=xterm-color ls -G" inside a Solaris xterm, which does not support color. Nothing bad happened. The xterm just ignored the color codes instead of producing any sort of garbage. Unless anyone knows of an xterm that barfs on color codes, I would support this change. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17: 6:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id 40E3637BF1A for ; Tue, 18 Jul 2000 17:06:09 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id A4F3315510; Tue, 18 Jul 2000 17:05:47 -0700 (PDT) Date: Tue, 18 Jul 2000 17:05:47 -0700 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000718170547.A79907@lunatic.oneinsane.net> Reply-To: insane@lunatic.oneinsane.net Mail-Followup-To: freebsd-stable@freebsd.org References: <20000718145920.B94689@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from twschulz@gloria.cord.edu on Tue, Jul 18, 2000 at 05:10:04PM -0500 X-Operating-System: FreeBSD lunatic.oneinsane.net 4.0-STABLE X-Moon: The Moon is Waning Gibbous (95% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 5:04PM up 6 days, 17:24, 1 user, load averages: 1.65, 1.34, 1.13 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Trenton Schulz was heard blurting out: > On Tue, 18 Jul 2000, Matthew Hunt wrote: > > > On Tue, Jul 18, 2000 at 02:16:32PM -0700, Kris Kennaway wrote: > > > On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote: > > > > > > > With the change to ls having the 'G' switch addded is there a way to get > > > > it to show colors in other than cons25. I read the man page and it is > > > > not clear on this. > > > > > > Use a termcap that supports colours. > > > > For example, "xterm-color" in an xterm. > > > > Does anyone know why XFree86's xterm, as shipped, doesn't set > > TERM to xterm-color? Is it for fear of an xterm-color entry > > not existing (either on the local machine, or machines you > > telnet/ssh to from the xterm)? > > I pretty sure that is the culprit. I know that on a sparc-netbsd machine I > login to on a regular basis doesn't have an xterm-color. And I've known > friends who've been bitten by this on other Unices. In the end, it's > probably better just to modify .Xdefaults to make your xterm "look color" > How does one in .Xdefaults make your xterm "look color" TIA -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ Excuse me, but can anyone tell me what's going on here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17: 8:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 47BF337BC49; Tue, 18 Jul 2000 17:08:41 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 4C6E29B06; Wed, 19 Jul 2000 01:08:41 +0100 (BST) Date: Wed, 19 Jul 2000 01:08:41 +0100 From: Josef Karthauser To: Matthew Hunt Cc: Ben Smithurst , Kris Kennaway , Ron 'The InSaNe One' Rosson , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719010841.I20505@pavilion.net> Mail-Followup-To: Josef Karthauser , Matthew Hunt , Ben Smithurst , Kris Kennaway , Ron 'The InSaNe One' Rosson , freebsd-stable@FreeBSD.ORG References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000718170420.A97601@wopr.caltech.edu>; from mph@astro.caltech.edu on Tue, Jul 18, 2000 at 05:04:20PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:04:20PM -0700, Matthew Hunt wrote: > > FWIW, I've just tried "TERM=xterm-color ls -G" inside a > Solaris xterm, which does not support color. Nothing bad happened. > The xterm just ignored the color codes instead of producing any > sort of garbage. > > Unless anyone knows of an xterm that barfs on color codes, I would > support this change. joe@cuddy[503]: export TERM=xterm-color joe@cuddy[504]: vi xterm-color: Unknown terminal type Visual needs addressable cursor or upline capability :q joe@cuddy[505]: uname -a SunOS cuddy 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-1 Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:11:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 7FC6337B9E9; Tue, 18 Jul 2000 17:11:45 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id RAA97822; Tue, 18 Jul 2000 17:11:41 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 17:11:41 -0700 From: Matthew Hunt To: Josef Karthauser , Ben Smithurst , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000718171141.A97774@wopr.caltech.edu> References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> <20000719010841.I20505@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719010841.I20505@pavilion.net>; from joe@pavilion.net on Wed, Jul 19, 2000 at 01:08:41AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote: > joe@cuddy[503]: export TERM=xterm-color > joe@cuddy[504]: vi > xterm-color: Unknown terminal type > Visual needs addressable cursor or upline capability > :q > joe@cuddy[505]: uname -a > SunOS cuddy 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-1 That's not the issue. What we want to do is have TERM=xterm be the same as xterm-color is now. If you log in to a FreeBSD box from your Sun, and *then* set TERM=xterm-color and run things on the FreeBSD box, do the color escape sequences screw anything up? -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:12:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id B507137B64B for ; Tue, 18 Jul 2000 17:12:05 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id B862B9B06; Wed, 19 Jul 2000 01:12:07 +0100 (BST) Date: Wed, 19 Jul 2000 01:12:07 +0100 From: Josef Karthauser To: Ron 'The InSaNe One' Rosson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719011207.J20505@pavilion.net> Mail-Followup-To: Josef Karthauser , Ron 'The InSaNe One' Rosson , freebsd-stable@FreeBSD.ORG References: <20000718145920.B94689@wopr.caltech.edu> <20000718170547.A79907@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000718170547.A79907@lunatic.oneinsane.net>; from insane@lunatic.oneinsane.net on Tue, Jul 18, 2000 at 05:05:47PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:05:47PM -0700, Ron 'The InSaNe One' Rosson wrote: > > I pretty sure that is the culprit. I know that on a sparc-netbsd machine I > > login to on a regular basis doesn't have an xterm-color. And I've known > > friends who've been bitten by this on other Unices. In the end, it's > > probably better just to modify .Xdefaults to make your xterm "look color" > > > > How does one in .Xdefaults make your xterm "look color" I put this in .Xdefaults for rxvt: Rxvt*termName: xterm-color Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:12:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 6A1DF37B64B; Tue, 18 Jul 2000 17:12:32 -0700 (PDT) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.10.1/8.10.1/20000715) id e6J0CRE24318; Tue, 18 Jul 2000 19:12:27 -0500 (CDT) From: Larry Rosenman Message-Id: <200007190012.e6J0CRE24318@lerami.lerctr.org> Subject: Re: Color ls In-Reply-To: <20000719005555.W4668@strontium.scientia.demon.co.uk> "from Ben Smithurst at Jul 19, 2000 00:55:55 am" To: Ben Smithurst Date: Tue, 18 Jul 2000 19:12:27 -0500 (CDT) Cc: Matthew Hunt , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL79 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, I had a similar issue with dtterm coming into a FreeBSD box from SCO UnixWare 7. DTTERM does color, but the DTTERM /etc/termcap didn't work for vim. Adding the same lines to the dtterm termcap as for xterm-color fixed it as well. Larry -- Start of PGP signed section. > Matthew Hunt wrote: > > > Does anyone know why XFree86's xterm, as shipped, doesn't set > > TERM to xterm-color? Is it for fear of an xterm-color entry > > not existing (either on the local machine, or machines you > > telnet/ssh to from the xterm)? > > ok, next question. > > If that's the case, why don't we change our termcap so that "xterm" and > "xterm-color" are the same thing, and "xterm-mono" is there for people > who _reall_ don't want color, or have a monochrome display, or whatever. > It seems really dumb not to have colour by default, but perhaps there's > a good reason. > > /me runs away for fear of annoying people by even daring to suggest this. > > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > FreeBSD Documentation Project / -- End of PGP section, PGP failed! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:17:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 9699837BC7D; Tue, 18 Jul 2000 17:17:22 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 5C1229B05; Wed, 19 Jul 2000 01:17:26 +0100 (BST) Date: Wed, 19 Jul 2000 01:17:26 +0100 From: Josef Karthauser To: Matthew Hunt Cc: Ben Smithurst , Kris Kennaway , Ron 'The InSaNe One' Rosson , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719011726.K20505@pavilion.net> Mail-Followup-To: Josef Karthauser , Matthew Hunt , Ben Smithurst , Kris Kennaway , Ron 'The InSaNe One' Rosson , freebsd-stable@FreeBSD.ORG References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> <20000719010841.I20505@pavilion.net> <20000718171141.A97774@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000718171141.A97774@wopr.caltech.edu>; from mph@astro.caltech.edu on Tue, Jul 18, 2000 at 05:11:41PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:11:41PM -0700, Matthew Hunt wrote: > On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote: > > > joe@cuddy[503]: export TERM=xterm-color > > joe@cuddy[504]: vi > > xterm-color: Unknown terminal type > > Visual needs addressable cursor or upline capability > > :q > > joe@cuddy[505]: uname -a > > SunOS cuddy 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-1 > > That's not the issue. It is if my sun inherits the TERM from my FreeBSD box. That said it's the sun that's borked here, not us. > What we want to do is have TERM=xterm be the same as xterm-color > is now. > > If you log in to a FreeBSD box from your Sun, and *then* set > TERM=xterm-color and run things on the FreeBSD box, do the color > escape sequences screw anything up? I've no idea, I've only got remote access to the sun, it's not mine, and it's not forwarding X11 connections properly over ssh :*( sorry. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:23: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 2C29A37BB58 for ; Tue, 18 Jul 2000 17:23:03 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA20235; Tue, 18 Jul 2000 17:31:48 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007190031.RAA20235@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hunt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-reply-to: Your message of "Tue, 18 Jul 2000 17:11:41 PDT." <20000718171141.A97774@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 17:31:47 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote: > > > joe@cuddy[503]: export TERM=xterm-color > > joe@cuddy[504]: vi > > xterm-color: Unknown terminal type > > Visual needs addressable cursor or upline capability > > :q > > joe@cuddy[505]: uname -a > > SunOS cuddy 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-1 > > That's not the issue. > > What we want to do is have TERM=xterm be the same as xterm-color > is now. > > If you log in to a FreeBSD box from your Sun, and *then* set > TERM=xterm-color and run things on the FreeBSD box, do the color > escape sequences screw anything up? Yes. Any program that expects colour to work. The correct fix here is to tell your xterms to identify themselves as xterm-color. This will then proceed to break anyone that wants to use an xtern to talk to a system that doesn't know what xterm-color is. The more correct fix here is to stop worrying about fucking colourised ls output and focus on the seventeen dozen more important things that need your angst. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:25:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id C7F6E37BC2B; Tue, 18 Jul 2000 17:25:20 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id RAA98189; Tue, 18 Jul 2000 17:25:17 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 17:25:17 -0700 From: Matthew Hunt To: Josef Karthauser , Ben Smithurst , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000718172517.A98089@wopr.caltech.edu> References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> <20000719010841.I20505@pavilion.net> <20000718171141.A97774@wopr.caltech.edu> <20000719011726.K20505@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719011726.K20505@pavilion.net>; from joe@pavilion.net on Wed, Jul 19, 2000 at 01:17:26AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 01:17:26AM +0100, Josef Karthauser wrote: > > That's not the issue. > > It is if my sun inherits the TERM from my FreeBSD box. That said > it's the sun that's borked here, not us. If we make the change that we are considering, then you will set TERM=xterm on your FreeBSD box. Things will run in color on your FreeBSD box. When you ssh to your Sun, the inherited value of TERM will work correctly, albeit without color. This seems to me like the best possibile situation. To reiterate: If we change termcap on FreeBSD so that "xterm" contains color support, then you set TERM=xterm everywhere and never use "xterm-color". The only times this is bad are: - If you have an xterm on some foreign platform which is screwed up by escape codes. None have been reported thus far. - If you log in to a machine which is like FreeBSD is now; you won't get color unless you switch back to "xterm-color". The goal is to have TERM=xterm do the color thing when possible and not give the problem you describe by setting TERM=xterm-color and logging in to a Sun. Matt -- Matthew Hunt * Inertia is a property http://www.pobox.com/~mph/ * of matter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:28:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 9417B37B50B; Tue, 18 Jul 2000 17:28:26 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id RAA98236; Tue, 18 Jul 2000 17:28:25 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 17:28:25 -0700 From: Matthew Hunt To: Mike Smith Cc: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000718172825.B98089@wopr.caltech.edu> References: <20000718171141.A97774@wopr.caltech.edu> <200007190031.RAA20235@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007190031.RAA20235@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jul 18, 2000 at 05:31:47PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote: > Yes. Any program that expects colour to work. In what sense? The color codes are absorbed by xterm and it looks like it probably does without doing color stuff. Do you know of a program which actually has problems? > The correct fix here is to tell your xterms to identify themselves as > xterm-color. This will then proceed to break anyone that wants to use an > xtern to talk to a system that doesn't know what xterm-color is. Yeah. Believe it or not, I log in to lots of random Suns and don't like having to reset TERM. > The more correct fix here is to stop worrying about fucking colourised ls > output and focus on the seventeen dozen more important things that need > your angst. I don't like colorized ls. I do like colorized mutt. But thanks for telling me what I should care about. Tell me what my proposed solution breaks, for real. -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:31:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 97E8737B81B; Tue, 18 Jul 2000 17:31:27 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id E0A6D9B06; Wed, 19 Jul 2000 01:31:30 +0100 (BST) Date: Wed, 19 Jul 2000 01:31:30 +0100 From: Josef Karthauser To: Mike Smith Cc: Matthew Hunt , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719013130.N20505@pavilion.net> Mail-Followup-To: Josef Karthauser , Mike Smith , Matthew Hunt , freebsd-stable@FreeBSD.ORG References: <20000718171141.A97774@wopr.caltech.edu> <200007190031.RAA20235@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007190031.RAA20235@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Tue, Jul 18, 2000 at 05:31:47PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote: > > The more correct fix here is to stop worrying about fucking colourised ls > output and focus on the seventeen dozen more important things that need > your angst. > Hear hear. :) More important right now is sleep :) Night night. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:35:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 4350037BC4F for ; Tue, 18 Jul 2000 17:35:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA20342; Tue, 18 Jul 2000 17:44:29 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007190044.RAA20342@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hunt Cc: freebsd-stable@freebsd.org Subject: Re: Color ls In-reply-to: Your message of "Tue, 18 Jul 2000 17:28:25 PDT." <20000718172825.B98089@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 17:44:29 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote: > > > Yes. Any program that expects colour to work. > > In what sense? The color codes are absorbed by xterm and it > looks like it probably does without doing color stuff. Do you > know of a program which actually has problems? I can think of dozens. Try anything that depends on colour to identify eg. menu selections. > > The correct fix here is to tell your xterms to identify themselves as > > xterm-color. This will then proceed to break anyone that wants to use an > > xtern to talk to a system that doesn't know what xterm-color is. > > Yeah. Believe it or not, I log in to lots of random Suns and don't > like having to reset TERM. So fix your Sun systems so that they recognise xterm-color. > > The more correct fix here is to stop worrying about fucking colourised ls > > output and focus on the seventeen dozen more important things that need > > your angst. > > I don't like colorized ls. I do like colorized mutt. But thanks > for telling me what I should care about. Tell me what my proposed > solution breaks, for real. The xterm terminal definition does not support colour. It is an error to corrupt our terminal capabilities database such that we use the xterm-color definitions for a terminal identifying itself as 'xterm'. If you want Mutt to work, set your terminal type correctly. If you have to access a broken remote host, fix your exported terminal type correctly. You are attempting to rationalise "wrong" behaviour, and that's just plain "wrong". -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:36:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 95C1D37B9C4; Tue, 18 Jul 2000 17:36:10 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 328EC9B05; Wed, 19 Jul 2000 01:36:06 +0100 (BST) Date: Wed, 19 Jul 2000 01:36:06 +0100 From: Josef Karthauser To: Matthew Hunt Cc: Mike Smith , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719013606.O20505@pavilion.net> Mail-Followup-To: Josef Karthauser , Matthew Hunt , Mike Smith , freebsd-stable@FreeBSD.ORG References: <20000718171141.A97774@wopr.caltech.edu> <200007190031.RAA20235@mass.osd.bsdi.com> <20000718172825.B98089@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000718172825.B98089@wopr.caltech.edu>; from mph@astro.caltech.edu on Tue, Jul 18, 2000 at 05:28:25PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:28:25PM -0700, Matthew Hunt wrote: > I don't like colorized ls. I do like colorized mutt. I like colourized vim and mutt :) Colourised sleep is next on my agenda. (But that's a private commit). Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:37:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 0E20F37B64B for ; Tue, 18 Jul 2000 17:36:38 -0700 (PDT) (envelope-from carl@xena.IPAustralia.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id KAA23984; Wed, 19 Jul 2000 10:36:23 +1000 (EST) (envelope-from carl@xena.IPAustralia.gov.au) Received: from xena.aipo.gov.au(10.0.100.52) by pericles.IPAustralia.gov.au via smap (V2.0) id xma023974; Wed, 19 Jul 00 10:36:11 +1000 Received: from newton.aipo.gov.au (newton.aipo.gov.au [10.0.100.18]) by xena.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA41649; Wed, 19 Jul 2000 10:38:45 +1000 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA69152; Wed, 19 Jul 2000 10:36:11 +1000 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Wed, 19 Jul 2000 10:36:11 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Matthew Hunt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-Reply-To: <20000718172517.A98089@wopr.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Matthew Hunt wrote: > To reiterate: If we change termcap on FreeBSD so that "xterm" > contains color support, then you set TERM=xterm everywhere and > never use "xterm-color". The only times this is bad are: XFree86 comes with updated xterm termcap and terminfo files. Just use those. BTW, why arn't we using terminfo? Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:42:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id E251A37BF26; Tue, 18 Jul 2000 17:42:19 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id RAA98588; Tue, 18 Jul 2000 17:42:19 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 17:42:18 -0700 From: Matthew Hunt To: Mike Smith Cc: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000718174218.A98458@wopr.caltech.edu> References: <20000718172825.B98089@wopr.caltech.edu> <200007190044.RAA20342@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007190044.RAA20342@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jul 18, 2000 at 05:44:29PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:44:29PM -0700, Mike Smith wrote: > I can think of dozens. Try anything that depends on colour to identify > eg. menu selections. I'm soliciting a specific example, because in my experience they usually simultaneously indicate the selection by inverse video or some sort of visible cursor. > So fix your Sun systems so that they recognise xterm-color. I don't administer the Suns. > You are attempting to rationalise "wrong" behaviour, and that's just > plain "wrong". OK, you're actually starting to be useful instead of just telling me to shut up. There's an increasing number of questions about this since ls -G, and I'm trying to figure out how to make life easier for new users and the people who have to deal with them. So, is the answer to use ~/.ssh/environment to set TERMCAP to the xterm-color entry? Should we put something in the Handbook describing this process? -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 17:55:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id CACEB37B50B for ; Tue, 18 Jul 2000 17:55:25 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id 1B3FF11CD28; Tue, 18 Jul 2000 17:55:25 -0700 (PDT) Date: Tue, 18 Jul 2000 17:55:25 -0700 From: R Joseph Wright To: Matthew Hunt Cc: freebsd-stable@FreeBSD.org Subject: Re: Color ls Message-ID: <20000718175525.A10074@manatee.mammalia.org> References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000718170420.A97601@wopr.caltech.edu>; from mph@astro.caltech.edu on Tue, Jul 18, 2000 at 05:04:20PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:04:20PM -0700, Matthew Hunt wrote: > On Wed, Jul 19, 2000 at 12:55:55AM +0100, Ben Smithurst wrote: > > > If that's the case, why don't we change our termcap so that "xterm" and > > "xterm-color" are the same thing, and "xterm-mono" is there for people > > who _reall_ don't want color, or have a monochrome display, or whatever. > > It seems really dumb not to have colour by default, but perhaps there's > > a good reason. > > FWIW, I've just tried "TERM=xterm-color ls -G" inside a > Solaris xterm, which does not support color. Nothing bad happened. > The xterm just ignored the color codes instead of producing any > sort of garbage. > > Unless anyone knows of an xterm that barfs on color codes, I would > support this change. I changed xterm to xterm-color in /etc/ttys, restarted init, went into X, and 'echo $TERM' did not show xterm-color. However, I did TERM=xterm-color and it worked. The thing that really bugs me about ls is the lack of bright colors like you get with gnuls. The blue is so dark it blends in with the black background of the console. I spent several hours looking through the code to see if I could change that, but alas I did not understand it :-(. And, sorry to rant, but the default colors are horrid, too! Do 'ls -G /dev' to see what I mean. AAaaarh! > -- > Matthew Hunt * Stay close to the Vorlon. > http://www.pobox.com/~mph/ * > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18: 1: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 7A81037B526 for ; Tue, 18 Jul 2000 18:01:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA20514; Tue, 18 Jul 2000 18:09:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007190109.SAA20514@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hunt Cc: freebsd-stable@freebsd.org Subject: Re: Color ls In-reply-to: Your message of "Tue, 18 Jul 2000 17:42:18 PDT." <20000718174218.A98458@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 18:09:58 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So fix your Sun systems so that they recognise xterm-color. > > I don't administer the Suns. But somebody does, and if you need them to talk to a colour terminal they need to be fixed. > > You are attempting to rationalise "wrong" behaviour, and that's just > > plain "wrong". > > OK, you're actually starting to be useful instead of just telling > me to shut up. There's an increasing number of questions about this > since ls -G, and I'm trying to figure out how to make life easier > for new users and the people who have to deal with them. > > So, is the answer to use ~/.ssh/environment to set TERMCAP to > the xterm-color entry? Should we put something in the Handbook > describing this process? No. The correct answer is to fix your xterm to identify itself as xterm-color, and then when you are forced to use a broken system use whatever mechanism is most appropriate to select an alternative terminal type (.ssh/environment would be useful here, for example). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18:10:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.102.114]) by hub.freebsd.org (Postfix) with ESMTP id 897B137B8A9; Tue, 18 Jul 2000 18:10:48 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.3) id SAA99563; Tue, 18 Jul 2000 18:10:48 -0700 (PDT) (envelope-from mph) Date: Tue, 18 Jul 2000 18:10:48 -0700 From: Matthew Hunt To: Mike Smith Cc: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000718181048.A99509@wopr.caltech.edu> References: <20000718174218.A98458@wopr.caltech.edu> <200007190109.SAA20514@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007190109.SAA20514@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jul 18, 2000 at 06:09:58PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 06:09:58PM -0700, Mike Smith wrote: > > So, is the answer to use ~/.ssh/environment to set TERMCAP to > > the xterm-color entry? Should we put something in the Handbook > > describing this process? > > No. The correct answer is to fix your xterm to identify itself as > xterm-color, and then when you are forced to use a broken system use > whatever mechanism is most appropriate to select an alternative terminal > type (.ssh/environment would be useful here, for example). (I think you're agreeing with what I wrote, actually, although I omitted the "use TERM=xterm-color" on FreeBSD step.) So, should we: - Change the XFree86 ports so that app-defaults/XTerm sets the terminal type to xterm-color, and - Put something in the Handbook about "what do I do when I log in to my Sun and it complains about xterm-color", describing .ssh/environment etc.? ? -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18:12:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id CA40C37B6E6 for ; Tue, 18 Jul 2000 18:12:55 -0700 (PDT) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6J1CrS85812; Tue, 18 Jul 2000 19:12:53 -0600 (MDT) Message-Id: <200007190112.e6J1CrS85812@orthanc.ab.ca> To: Matthew Hunt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-reply-to: Your message of "Tue, 18 Jul 2000 17:42:18 PDT." <20000718174218.A98458@wopr.caltech.edu> Date: Tue, 18 Jul 2000 19:12:53 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Matthew" == Matthew Hunt writes: >> So fix your Sun systems so that they recognise xterm-color. Matthew> I don't administer the Suns. Then 'man -s 4 terminfo' and read up on the TERMINFO environment variable. After that, create a ~/terminfo/... hierarchy on the Sun, copy the xterm-color termcap entry to the Sun, run captoinfo(1m), compile the result with tic(1m), and populate your private terminfo tree with the resulting xterm-color terminfo entry. Adjust .profile or .login as appropriate and away you go. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18:14:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 04A3137B7CC; Tue, 18 Jul 2000 18:14:22 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id VAA04910; Tue, 18 Jul 2000 21:14:57 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Tue, 18 Jul 2000 21:14:57 -0400 (EDT) From: "Brandon D. Valentine" To: Mike Smith Cc: Matthew Hunt , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-Reply-To: <200007190044.RAA20342@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jul 2000, Mike Smith wrote: >If you want Mutt to work, set your terminal type correctly. If you have >to access a broken remote host, fix your exported terminal type correctly. Furthermore, learn to write a decent .cshrc or .shrc file and check the values of `uname -s` and `arch` to determine what to set the terminal environment variable to. If I didn't take care of this I could never log into anything from my irix workstation without manually setting term types. The iris-ansi-net term type doesn't work right just about anywhere. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18:36:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 4DFF337B91C for ; Tue, 18 Jul 2000 18:36:46 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA20697; Tue, 18 Jul 2000 18:45:38 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007190145.SAA20697@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hunt Cc: freebsd-stable@freebsd.org Subject: Re: Color ls In-reply-to: Your message of "Tue, 18 Jul 2000 18:10:48 PDT." <20000718181048.A99509@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 18:45:38 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, should we: > > - Change the XFree86 ports so that app-defaults/XTerm sets the terminal > type to xterm-color, and We've generally maintained that we should ship whatever the XFree86 people send us. What's their take on this? > - Put something in the Handbook about "what do I do when I log in to my > Sun and it complains about xterm-color", describing .ssh/environment > etc.? Definitely. You might want to talk about what to do when it complains about cons25 as well. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18:43:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gourmet.uchicago.edu (gourmet.uchicago.edu [128.135.44.24]) by hub.freebsd.org (Postfix) with ESMTP id E620E37B82F for ; Tue, 18 Jul 2000 18:43:09 -0700 (PDT) (envelope-from czhang@gourmet.uchicago.edu) Received: from localhost (czhang@localhost) by gourmet.uchicago.edu (8.9.3/8.9.3) with ESMTP id UAA03100; Tue, 18 Jul 2000 20:41:53 -0500 (CDT) (envelope-from czhang@gourmet.uchicago.edu) Date: Tue, 18 Jul 2000 20:41:52 -0500 (CDT) From: Chi Zhang To: David Uhring Cc: sean@rentul.net, freebsd-stable@FreeBSD.ORG Subject: Re: is the ensoniq 1371 sound chip supported? In-Reply-To: <00071818513700.03027@dave.uhring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG use /dev/snd0, I use ensoniq 1371 for a couple of days, it works well. On Tue, 18 Jul 2000, David Uhring wrote: > I can't get mine to work, either. The kernel is compiled with device pcm and > dmesg shows that the kernel recognizes the card. What /dev/ have to > be made? There is no pcm0 in /dev and MAKEDEV reports no such device, although > pcm0 appears in dmesg. Running RELENG_4 compiled 12 Jul 00. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 18:44: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sparenix.metronet.com (sparenix.metronet.com [207.170.106.3]) by hub.freebsd.org (Postfix) with SMTP id 907DF37B82F for ; Tue, 18 Jul 2000 18:43:59 -0700 (PDT) (envelope-from jmanley@metronet.com) Received: (qmail 26683 invoked by uid 7770); 19 Jul 2000 01:43:48 -0000 Received: from fcn105-22.tmi.net (HELO jwmhome) (207.170.105.22) by sparenix.metronet.com with SMTP; 19 Jul 2000 01:43:48 -0000 Message-ID: <001001bff122$b3176460$0100a8c0@lmtas.lmco.com> From: "Jim Manley" To: Subject: ifconfig cause system to hang (was 4.1-RC causes system to hang) Date: Tue, 18 Jul 2000 20:43:10 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01BFF0F8.C92D2D40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01BFF0F8.C92D2D40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In a previous post I stated that when I boot my system and loaded the = kernel I compiled using the 4.1-RC sources, my system hung. I was able = to boot into single user mode from the kernel I built using the 17 July = "GENERIC" kernel config file. When I run the "ifconfig ep0 inet = 192.168.0.3 mask 255.255.255.0" command, the system hangs. I've compared my old kernel config with the GENERIC config file and = don't have any real difference. Ideas? ------=_NextPart_000_000D_01BFF0F8.C92D2D40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
In a previous post I stated that when I = boot my=20 system and loaded the kernel I compiled using the 4.1-RC sources, my = system=20 hung.  I was able to boot into single user mode from the kernel I = built=20 using the 17 July "GENERIC" kernel config file.  When I run the = "ifconfig=20 ep0 inet 192.168.0.3 mask 255.255.255.0" command, the system = hangs.
 
I've compared my old kernel config with = the GENERIC=20 config file and don't have any real difference.
 
Ideas?
------=_NextPart_000_000D_01BFF0F8.C92D2D40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 19:38: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id E2CFE37B54E; Tue, 18 Jul 2000 19:38:01 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id WAA97974; Tue, 18 Jul 2000 22:40:51 -0400 (EDT) From: Brian Hechinger Message-Id: <200007190240.WAA97974@entropy.tmok.com> Subject: Re: Color ls In-Reply-To: <200007190109.SAA20514@mass.osd.bsdi.com> from Mike Smith at "Jul 18, 2000 6: 9:58 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Tue, 18 Jul 2000 22:40:50 -0400 (EDT) Cc: mph@astro.caltech.edu, freebsd-stable@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith drunkenly mumbled... > > > So fix your Sun systems so that they recognise xterm-color. > > > > I don't administer the Suns. > > But somebody does, and if you need them to talk to a colour terminal they > need to be fixed. and speaking as a terribly old school administrator, i would think to myself, "stupid color ls is for wankerware loving lusers." as i made it work for you. sure, lusers really annoy us, but doing what you ask to make your job "easier" is sorta what our job is all about, so with a few exceptions, we will happily make the change for you. being a long time solaris administrator, i can say that there are numerous problems with the OS. we all know it, so we aren't supprised when people ask us to do things like this. god i miss SunOS 4.x, but at least i don't administrate irix. Brian "Color? We don't need no stinkin' color" Hechinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 19:42: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by hub.freebsd.org (Postfix) with ESMTP id 8C70937B54E for ; Tue, 18 Jul 2000 19:41:56 -0700 (PDT) (envelope-from michaelw@iprg.nokia.com) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id TAA26087 for ; Tue, 18 Jul 2000 19:41:55 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id TAA01687 for ; Tue, 18 Jul 2000 19:41:52 -0700 From: michaelw@iprg.nokia.com X-Virus-Scanned: Tue, 18 Jul 2000 19:41:52 -0700 Nokia Silicon Valley Email Exploit Scanner Received: from brakescr.iprg.nokia.com (205.226.1.186) by darkstar.iprg.nokia.com(WTS.12.69) smtpdTHeqV7; Tue, 18 Jul 2000 19:41:48 PDT Received: (michaelw@localhost) by brakescr.iprg.nokia.com (8.9.3/8.6.12) id TAA43747 for freebsd-stable@FreeBSD.ORG; Tue, 18 Jul 2000 19:41:51 -0700 (PDT) Date: Tue, 18 Jul 2000 19:41:51 -0700 (PDT) Message-Id: <200007190241.TAA43747@brakescr.iprg.nokia.com> To: freebsd-stable@FreeBSD.ORG Subject: first buildworld Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG argh... stage 4 fails, seem to be missing the ARCH in the path ? All help appreciated. Tx, Mike -------------------------------------------------------------- >>> stage 4: populating /usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/include -------------------------------------------------------------- cd /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/libexec:/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/bin LIBRARY_PATH=/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/lib:/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/libexec PERL5LIB=/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/libdata/perl/5.006 DESTDIR=/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386 INSTALL="sh /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/tools/install.sh" PATH=/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/sbin:/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/bin:/usr/obj/net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/i386/usr/games:/sbin:/b! in:/usr/sbin:/usr/bin make -f Ma kefile.inc1 SHARED=symlinks includes cd /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/include; make -B all install cd: can't cd to /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src/include *** Error code 2 Stop in /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src. *** Error code 1 Stop in /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src. *** Error code 1 Stop in /net/servo/home/michaelw/SOURCE_TREES/4.0-build/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 20:18: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 9ABEC37B5EA; Tue, 18 Jul 2000 20:18:06 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13EkN3-0005gM-00; Wed, 19 Jul 2000 04:18:05 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id EAA52575; Wed, 19 Jul 2000 04:18:05 +0100 (BST) (envelope-from jcm) Date: Wed, 19 Jul 2000 04:18:04 +0100 From: j mckitrick To: wonko@entropy.tmok.com Cc: Mike Smith , mph@astro.caltech.edu, freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000719041804.A52522@dogma.freebsd-uk.eu.org> References: <200007190109.SAA20514@mass.osd.bsdi.com> <200007190240.WAA97974@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007190240.WAA97974@entropy.tmok.com>; from wonko@users.tmok.com on Tue, Jul 18, 2000 at 10:40:50PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > sure, lusers really annoy us, but doing what you ask to make your job "easier" > is sorta what our job is all about, so with a few exceptions, we will happily > make the change for you. Speaking as a newcomer to BSD, it's hard to say we are forward looking and have decent multimedia ability when we can't easily get 'ls' to show color. Maybe multimedia, color, sound, etc aren't important to 'old school' computer people, but let's face it: computing isn't what it used to be. Old school OS's never imagined video playback, point-and-click, speech synthesis, 3D game cards, and real-time online gaming. But they are here. They also never thought they would see spreadsheets, wysiwig word processors, desktop publishing, and other 'productive' endeavors become widespread and accessible to the average joe. It's time to sell out. Colorls isn't THAT big of a deal if it makes people happy. Adding it will make more people happy than leaving it out will. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 21:11:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail02.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 13BDF37BC88 for ; Tue, 18 Jul 2000 21:11:14 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave.uhring.com) by mail02.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 1503599 for freebsd-stable@freebsd.org; Wed, 19 Jul 2000 00:16:30 -0400 From: David Uhring To: freebsd-stable@freebsd.org Subject: Re: is the ensoniq 1371 sound chip supported? Date: Tue, 18 Jul 2000 23:03:17 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00071823111000.22466@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I finally realized that having changed sound cards in this machine that it might be necessary to remake /dev/snd0. I am pleased to report that my SB PCI128 aka es1373 is now working just fine under RealPlayer7. My apologies to all for my rant about documentation, but the simple fact is that I can't find any. Not in Handbook, not in man pages, not in archives of mailing lists. Is there someone sufficiently knowledgeable about sound under FreeBSD who is willing to at least kludge draft something to document sound? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:13:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id A962537B545 for ; Tue, 18 Jul 2000 22:13:54 -0700 (PDT) (envelope-from kdulzo@caffeine.gerp.org) Received: (qmail 22766 invoked by uid 100); 19 Jul 2000 05:01:40 -0000 Date: Wed, 19 Jul 2000 00:01:40 -0500 From: "Kevin M. Dulzo" To: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000719000140.A4627@caffeine.gerp.org> Reply-To: kdulzo@gerp.org References: <20000718181048.A99509@wopr.caltech.edu> <200007190145.SAA20697@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007190145.SAA20697@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jul 18, 2000 at 06:45:38PM -0700 X-Operating-System: OpenBSD caffeine 2.7 CAFFEINE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 06:45:38PM -0700, Mike Smith wrote: > > Definitely. You might want to talk about what to do when it complains > about cons25 as well. > right ways or wrong ways aside, try man termcap(5)/terminfo on your destination system. Solaris I know for a fact supports a ~/.termcap (indirectly) and terminfo databases. Its how I used to admin 30+ Solaris boxes from my happy freebsd workstation. Crop the cons25|* entries youd like and tic them on the machine as needed. Can do the same with xterm-color. Good Luck, -Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:16:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 7889D37B5C6; Tue, 18 Jul 2000 22:16:56 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id 489303D34; Wed, 19 Jul 2000 01:17:30 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 43A235BC2; Wed, 19 Jul 2000 01:17:30 -0400 (EDT) Date: Wed, 19 Jul 2000 01:17:30 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Kris Kennaway Cc: Ron 'The InSaNe One' Rosson , freebsd-stable@freebsd.org Subject: Re: Color ls In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any reason a termcap that will support this cannot be part of a default isntall? or base system? On Tue, 18 Jul 2000, Kris Kennaway wrote: > On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote: > > > With the change to ls having the 'G' switch addded is there a way to get > > it to show colors in other than cons25. I read the man page and it is > > not clear on this. > > Use a termcap that supports colours. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ==================================================================== Sean Lutner (insert meaningless mine's bigger than yours title here) sean@rentul.net http://www.rentul.net ==================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:24:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id E431137B6E6; Tue, 18 Jul 2000 22:24:53 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id A2C3D3D34; Wed, 19 Jul 2000 01:25:33 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 9D8FD5BC2; Wed, 19 Jul 2000 01:25:33 -0400 (EDT) Date: Wed, 19 Jul 2000 01:25:33 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Kris Kennaway Cc: Ron 'The InSaNe One' Rosson , freebsd-stable@freebsd.org Subject: Re: Color ls In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry bout that previous post. I replied before reading the remaining slue of messages. On Wed, 19 Jul 2000, Sean Lutner wrote: > Is there any reason a termcap that will support this cannot be part of a > default isntall? or base system? > > > On Tue, 18 Jul 2000, Kris Kennaway wrote: > > > On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote: > > > > > With the change to ls having the 'G' switch addded is there a way to get > > > it to show colors in other than cons25. I read the man page and it is > > > not clear on this. > > > > Use a termcap that supports colours. > > > > Kris > > > > -- > > In God we Trust -- all others must submit an X.509 certificate. > > -- Charles Forsythe > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > ==================================================================== > Sean Lutner (insert meaningless mine's bigger than yours title here) > sean@rentul.net > http://www.rentul.net > ==================================================================== > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:25:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 3EF3D37BD2C for ; Tue, 18 Jul 2000 22:25:51 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 13EmMc-0001Bk-00 for freebsd-stable@freebsd.org; Wed, 19 Jul 2000 01:25:46 -0400 Date: Wed, 19 Jul 2000 01:25:45 -0400 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000719012545.E29813@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <20000718181048.A99509@wopr.caltech.edu> <200007190145.SAA20697@mass.osd.bsdi.com> <20000719000140.A4627@caffeine.gerp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719000140.A4627@caffeine.gerp.org>; from kdulzo@caffeine.gerp.org on Wed, Jul 19, 2000 at 12:01:40AM -0500 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kevin M. Dulzo" probably said: > right ways or wrong ways aside, try man termcap(5)/terminfo on your > destination system. Solaris I know for a fact supports a ~/.termcap > (indirectly) and terminfo databases. Its how I used to admin 30+ Solaris > boxes from my happy freebsd workstation. Crop the cons25|* entries youd like > and tic them on the machine as needed. Can do the same with xterm-color. There is already a terminfo entry for at386 on all remotely recent Solaris boxes, for the Solaris x86 console, which works with cons25. As a tcsh user, I put this in my .cshrc file on the Solaris boxes; if ( $?TERM ) then if ( "$TERM" == "cons25" ) setenv TERM at386 endif When I install Solaris machines I do; cd /usr/share/lib/terminfo/c ; ln -s ../a/at386 cons25 I'm mostly a Solaris admin. Either seems to work fine for me, although I don't push the FreeBSD console much anymore, and is less effort than getting the termcap/terminfo entries together :) Unfortunately there isn't an entry that I know of that works for colour xterms, but that can be solved as described above. I don't use them, so don't need it. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:31:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 26C6537BCD4 for ; Tue, 18 Jul 2000 22:31:35 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA13975 for ; Wed, 19 Jul 2000 12:31:05 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 19 Jul 2000 12:31:05 +0700 (NSS) From: Max Khon To: stable@freebsd.org Subject: 4.0-20000714-SNAP on 486 DX2-66 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! yesterday I have succesfully installed 4.0-20000714-SNAP (I have built it by myself) on 486 DX2-66 machine (3.4/3.5-RELEASE refused to install there -- hangs while installing probably related to bugs in wd driver) everything seems to work fine generating DSA key takes 20 minutes (no less!) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:40:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id CEF6737BCDB; Tue, 18 Jul 2000 22:40:23 -0700 (PDT) (envelope-from mike@adept.org) Received: by snafu.adept.org (Postfix, from userid 1000) id 03F179EE01; Tue, 18 Jul 2000 22:40:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id F170E9B001; Tue, 18 Jul 2000 22:40:19 -0700 (PDT) Date: Tue, 18 Jul 2000 22:40:19 -0700 (PDT) From: Mike Hoskins To: j mckitrick Cc: wonko@entropy.tmok.com, Mike Smith , mph@astro.caltech.edu, freebsd-stable@freebsd.org Subject: Re: Color ls In-Reply-To: <20000719041804.A52522@dogma.freebsd-uk.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, j mckitrick wrote: > It's time to sell out. Colorls isn't THAT big of a deal if it makes people > happy. Adding it will make more people happy than leaving it out will. [155]mike@storm{mike}$ echo $TERM xterm-color [156]mike@storm{mike}$ ls -G 'Adding it will...' ? It's already been added. This discussion isn't about adding color ls support, it's about people understanding how to configure their terminal(s). Along those lines... 'color' isn't a default ls behavior. That's why you have to add an argument (-G) to make it appear. Reading ls(1) tells one how to do that. With that in mind... 'xterm-color' isn't a default xterm terminal type. I think the problem is, ls(1) doesn't mention anything about needing 'xterm-color' for -G to work. I know... This duscussion's been had before. I'm not saying it's ls(1)'s job to educate the polulace on termcap, but if ls(1) isn't specifically going to expalin that -G won't work without xterm-color (and, don't get me wrong, I think the user should have to specify xterm-color if they want it...), shouldn't it at least point to termcap(5)? Personally, I think it'd just be easier to include 'requires TERM=xterm-color' with ls(1)'s explanation of -G, but that's just MO. I have to admit... I don't generally use color ls. If it makes some faction (even a very small one) of users happy though, I'm happy we support it - and we do support it... We support is a lot better than gnuls, IMCO. Ever try redirecting gnuls through more or less? What a mess. Doing the same with ours works perfectly. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 22:58: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id A91A237BCE2 for ; Tue, 18 Jul 2000 22:58:05 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id A6D9011CD28; Tue, 18 Jul 2000 22:58:03 -0700 (PDT) Date: Tue, 18 Jul 2000 22:58:03 -0700 From: R Joseph Wright To: Mike Hoskins Cc: freebsd-stable@FreeBSD.org Subject: Re: Color ls Message-ID: <20000718225803.B11027@manatee.mammalia.org> References: <20000719041804.A52522@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mike@adept.org on Tue, Jul 18, 2000 at 10:40:19PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 10:40:19PM -0700, Mike Hoskins wrote: > On Wed, 19 Jul 2000, j mckitrick wrote: > > > It's time to sell out. Colorls isn't THAT big of a deal if it makes people > > happy. Adding it will make more people happy than leaving it out will. > > [155]mike@storm{mike}$ echo $TERM > xterm-color > [156]mike@storm{mike}$ ls -G > > > 'Adding it will...' ? It's already been added. This discussion isn't > about adding color ls support, it's about people understanding how to > configure their terminal(s). > > Along those lines... 'color' isn't a default ls behavior. That's why > you have to add an argument (-G) to make it appear. Reading ls(1) tells > one how to do that. With that in mind... 'xterm-color' isn't a default > xterm terminal type. I think the problem is, ls(1) doesn't mention > anything about needing 'xterm-color' for -G to work. > > I know... This duscussion's been had before. I'm not saying it's ls(1)'s > job to educate the polulace on termcap, but if ls(1) isn't specifically > going to expalin that -G won't work without xterm-color (and, don't get me > wrong, I think the user should have to specify xterm-color if they want > it...), shouldn't it at least point to termcap(5)? > > Personally, I think it'd just be easier to include 'requires > TERM=xterm-color' with ls(1)'s explanation of -G, but that's just MO. > > I have to admit... I don't generally use color ls. If it makes some > faction (even a very small one) of users happy though, I'm happy we > support it - and we do support it... We support is a lot better than > gnuls, IMCO. Ever try redirecting gnuls through more or less? What a > mess. Doing the same with ours works perfectly. > This is not so. You have to use it like 'gnuls --color=auto' and there will be no such mess. Gnuls also shows colors in the standard xterm without any of this termcap insanity or TERM=xterm-color nonsense. It's also much easier on the eyes, at least for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jul 18 23:55:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iserver.itworks.com.au (iserver.itworks.com.au [203.32.61.10]) by hub.freebsd.org (Postfix) with SMTP id 282C437BCFF for ; Tue, 18 Jul 2000 23:55:48 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: (qmail 67967 invoked from network); 19 Jul 2000 06:55:45 -0000 Received: from maybe.itworks.com.au (203.36.209.235) by iserver.itworks.com.au with SMTP; 19 Jul 2000 06:55:45 -0000 Received: (qmail 61880 invoked from network); 19 Jul 2000 06:55:45 -0000 Received: from maybe.itworks.com.au (HELO maybe) (203.36.209.235) by maybe.itworks.com.au with SMTP; 19 Jul 2000 06:55:45 -0000 Date: Wed, 19 Jul 2000 16:55:45 +1000 (EST) From: Gavin Cameron To: stable@freebsd.org Subject: Stable broken in lib/libc_r Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, While installing a stable world from yesterday the 'make install' dies while installing the man pages for lib/libc_r Here's the error: install -c -o root -g wheel -m 444 pthread_attr.3.gz pthread_cancel.3.gz pthread_cleanup_pop.3.gz pthread_cleanup_push.3.gz pthread_condattr.3.gz pthread_cond_broadcast.3.gz pthread_cond_destroy.3.gz pthread_cond_init.3.gz pthread_cond_signal.3.gz pthread_cond_timedwait.3.gz pthread_cond_wait.3.gz pthread_create.3.gz pthread_detach.3.gz pthread_equal.3.gz pthread_exit.3.gz pthread_getspecific.3.gz pthread_join.3.gz pthread_key_create.3.gz pthread_key_delete.3.gz pthread_kill.3.gz pthread_mutexattr.3.gz pthread_mutex_destroy.3.gz pthread_mutex_init.3.gz pthread_mutex_lock.3.gz pthread_mutex_trylock.3.gz pthread_mutex_unlock.3.gz pthread_once.3.gz pthread_rwlock_destroy.3.gz pthread_rwlock_init.3.gz pthread_rwlock_rdlock.3.gz pthread_rwlock_unlock.3.gz pthread_rwlock_wrlock.3.gz pthread_rwlockattr_destroy.3.gz pthread_rwlockattr_getpshared.3.gz pthread_rwlockattr_init.3.gz pthread_rwlockattr_setpshared.3.gz pthread_schedparam.3.gz pthread_self.3.gz pthread_setspecific.3.gz pthread_sigmask.3.gz pthread_testcancel.3.gz sem_destroy.3.gz sem_getvalue.3.gz sem_init.3.gz sem_open.3.gz sem_post.3.gz sem_wait.3.gz sigwait.3.gz /usr/share/man/man3 install: pthread_attr.3.gz: No such file or directory *** Error code 71 Ideas? Ta Gavin []-----------------------------------+------------------------------------[] | Gavin Cameron | ITworks Consulting | | Ph : +61 3 9642 5477 | Level 8, 488 Bourke Street | | Fax : +61 3 9642 5499 | Melbourne, Victoria | | Email : gavin@itworks.com.au | Australia, 3000 | []-----------------------------------+------------------------------------[] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 0:41:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id DF2B137BD59 for ; Wed, 19 Jul 2000 00:41:51 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id AAA01601; Wed, 19 Jul 2000 00:41:17 -0700 Message-ID: <39755BB9.E210F727@urx.com> Date: Wed, 19 Jul 2000 00:41:45 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gavin Cameron Cc: stable@FreeBSD.ORG Subject: Re: Stable broken in lib/libc_r References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gavin Cameron wrote: > > Hi, > > While installing a stable world from yesterday the 'make install' dies > while installing the man pages for lib/libc_r > > Here's the error: > > install -c -o root -g wheel -m 444 pthread_attr.3.gz pthread_cancel.3.gz > pthread_cleanup_pop.3.gz pthread_cleanup_push.3.gz pthread_condattr.3.gz > pthread_cond_broadcast.3.gz pthread_cond_destroy.3.gz > pthread_cond_init.3.gz pthread_cond_signal.3.gz > pthread_cond_timedwait.3.gz pthread_cond_wait.3.gz pthread_create.3.gz > pthread_detach.3.gz pthread_equal.3.gz pthread_exit.3.gz > pthread_getspecific.3.gz pthread_join.3.gz pthread_key_create.3.gz > pthread_key_delete.3.gz pthread_kill.3.gz pthread_mutexattr.3.gz > pthread_mutex_destroy.3.gz pthread_mutex_init.3.gz pthread_mutex_lock.3.gz > pthread_mutex_trylock.3.gz pthread_mutex_unlock.3.gz pthread_once.3.gz > pthread_rwlock_destroy.3.gz pthread_rwlock_init.3.gz > pthread_rwlock_rdlock.3.gz pthread_rwlock_unlock.3.gz > pthread_rwlock_wrlock.3.gz pthread_rwlockattr_destroy.3.gz > pthread_rwlockattr_getpshared.3.gz pthread_rwlockattr_init.3.gz > pthread_rwlockattr_setpshared.3.gz pthread_schedparam.3.gz > pthread_self.3.gz pthread_setspecific.3.gz pthread_sigmask.3.gz > pthread_testcancel.3.gz sem_destroy.3.gz sem_getvalue.3.gz sem_init.3.gz > sem_open.3.gz sem_post.3.gz sem_wait.3.gz sigwait.3.gz > /usr/share/man/man3 > install: pthread_attr.3.gz: No such file or directory > *** Error code 71 > > Ideas? Re-cvsup. There was a message in cvs-all that your missing file was added. I cvsup'ed and looked in /usr/src/lib/libc_r/man and it was there. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 1: 1:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id C83FE37BC59 for ; Wed, 19 Jul 2000 01:01:42 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id JAA14424; Wed, 19 Jul 2000 09:09:15 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000718170547.A79907@lunatic.oneinsane.net> Date: Wed, 19 Jul 2000 09:09:15 +0100 (IST) From: "Steve O'Hara-Smith" To: "Ron 'The InSaNe One' Rosson" Subject: Re: Color ls Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jul-00 Ron 'The InSaNe One' Rosson wrote: > How does one in .Xdefaults make your xterm "look color" I have *customization: -color In my .Xdefaults which takes care of xterm and quite a lot of other apps as well. -- Steve O'Hara-Smith http://sohara.webhop.net/ A Better Way To Focus The Sun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 1:43: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id CFC7937BA23 for ; Wed, 19 Jul 2000 01:43:02 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id BAA01697 for ; Wed, 19 Jul 2000 01:43:01 -0700 Message-ID: <39756A30.A1044395@urx.com> Date: Wed, 19 Jul 2000 01:43:28 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Stable Subject: Stable 4.1-RC will not compile nametoaddr.c. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On RELENG_4 cvsup'ed at 0130 am PDT (0830 GMT) 19 July, you get the following error cc -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DH AVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -D INET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../ contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpcap/ ../../contrib/libpcap/nametoaddr.c -o nametoaddr.o /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types f or `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `e ther_hostton' *** Error code 1 Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 1:47:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snoopie.yi.org (003-010.dsl.popsite.net [64.24.3.10]) by hub.freebsd.org (Postfix) with ESMTP id 99B1F37BA98 for ; Wed, 19 Jul 2000 01:47:11 -0700 (PDT) (envelope-from brueggma@snoopie.yi.org) Received: from localhost (brueggma@localhost) by snoopie.yi.org (8.9.3/8.9.3) with ESMTP id DAA41067 for ; Wed, 19 Jul 2000 03:47:33 -0500 (CDT) (envelope-from brueggma@snoopie.yi.org) Date: Wed, 19 Jul 2000 03:47:32 -0500 (CDT) From: Eric Brueggmann To: freebsd-stable@freebsd.org Subject: make buildworld fails. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just did a cvsup to RELENG_4 (3:00am) CST, and tried to "make buildworld" but the compilation failed. snoopie# make buildworld ..... ===> libpcap cc -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c -o nametoaddr.o cc -fpic -DPIC -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c -o nametoaddr.So cc -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c grammar.c -o grammar.o cc -fpic -DPIC -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c grammar.c -o grammar.So /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error snoopie# (long lines may have wrapped - I'm using pico/pine) Please let me know if you need more info. Thanks for any help, Eric Brueggmann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 1:51:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 3840A37BAC9 for ; Wed, 19 Jul 2000 01:51:36 -0700 (PDT) (envelope-from jjreynold@cx587235-a.chnd1.az.home.com) Received: (from jjreynold@localhost) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) id BAA95748 for stable@freebsd.org; Wed, 19 Jul 2000 01:51:35 -0700 (MST) (envelope-from jjreynold) Date: Wed, 19 Jul 2000 01:51:35 -0700 (MST) From: John Reynolds Message-Id: <200007190851.BAA95748@cx587235-a.chnd1.az.home.com> To: stable@freebsd.org Subject: buildworld breakage as of 1:49am 7/19/2000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I apologize in advance if I missed a "HEADS UP" regarding instability in the source tree within the last few hours (my -stable subscription gets sent to another address I don't have access to here). I was trying to buildworld just now with CVSup'ed sources as of about 1:30am today. I've tried CVSup'ing since then but there have been no source changes. The following is the tail end of the breakage: ===> libpcap ... cc -fpic -DPIC -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c -o nametoaddr.So /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.5-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 1:57: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id CB83637BC7A for ; Wed, 19 Jul 2000 01:56:56 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id BAA01718; Wed, 19 Jul 2000 01:56:53 -0700 Message-ID: <39756D70.3B05AF97@urx.com> Date: Wed, 19 Jul 2000 01:57:20 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: John Reynolds Cc: stable@FreeBSD.ORG Subject: Re: buildworld breakage as of 1:49am 7/19/2000 References: <200007190851.BAA95748@cx587235-a.chnd1.az.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Reynolds wrote: > > Hello all, > > I apologize in advance if I missed a "HEADS UP" regarding instability in the > source tree within the last few hours (my -stable subscription gets sent to > another address I don't have access to here). > > I was trying to buildworld just now with CVSup'ed sources as of about 1:30am > today. I've tried CVSup'ing since then but there have been no source changes. I had the same thing happen. I did find that cvsup at this time of day only required 90 seconds via DSL. FWIW, you're the 3rd to report the problem. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 2:36:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wysoft.tzo.com (c481444-a.bremtn1.wa.home.com [24.12.235.202]) by hub.freebsd.org (Postfix) with ESMTP id 11CE137BDE4 for ; Wed, 19 Jul 2000 02:36:44 -0700 (PDT) (envelope-from wysoft@wysoft.tzo.com) Received: from localhost (wysoft@localhost) by wysoft.tzo.com (8.10.1/8.10.1) with ESMTP id e6J9WYW18962 for ; Wed, 19 Jul 2000 02:32:34 -0700 (PDT) Date: Wed, 19 Jul 2000 02:32:34 -0700 (PDT) From: Jeff Wyman To: stable@freebsd.org Subject: Small handbook error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was reading the handbook section on make buildworld (http://www.freebsd.org/handbook/makeworld.html) and I noticed that under section 18.4.2, a 386DX is referred to as having an integrated FPU. It then goes on to reccomend certain steps that might break FPU functions on a 386DX that might be using FPU emulation. This could cause grief for some people that don't notice this. I'm a complete idiot who doesn't even know how to make diffs, so I thought I'd just let everybody know right away instead of figuring out how to write a diff and holding out on you all for the time that may take - I'm a slow learner. Don't worry, I'll read the man page next time I've got more free time :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 4: 4:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from elit.ci.net.ua (elit.ci.net.ua [212.86.96.11]) by hub.freebsd.org (Postfix) with ESMTP id 416A337BE33 for ; Wed, 19 Jul 2000 04:04:18 -0700 (PDT) (envelope-from acid@ci.net.ua) Received: from localhost (acid@localhost) by elit.ci.net.ua (8.9.3/Who was second?) with ESMTP id OAA04085 for ; Wed, 19 Jul 2000 14:04:06 +0300 (EEST) Date: Wed, 19 Jul 2000 14:04:06 +0300 (EEST) From: Michael Vasilenko To: freebsd-stable@freebsd.org Subject: slow system clock on 3.5-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Recently I've updated one of old routers - K5/100Mhz from 3.3-RELEASE to 3.5-STABLE and discovered one "feature" - system clock now goes sloooow, 1 'machine' second is like 3-5 'normal' seconds. Kernel config is slightly modified GENERIC. Where is the bug and how fix it ? dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.5-STABLE #0: Tue Jul 18 11:43:14 EEST 2000 root@hamlet.ci.net.ua:/usr/src/sys/compile/HAMLET Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 99716391 Hz CPU: AMD K5 model 0 (99.72-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x501 Stepping = 1 Features=0x3bf real memory = 16777216 (16384K bytes) avail memory = 14041088 (13712K bytes) Preloaded elf kernel "kernel" at 0xc0280000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x00 int a irq 11 on pci0.13.0 de0: rev 0x11 int a irq 10 on pci0.15.0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:80:48:ea:5c:e7 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio4 at 0x2a0-0x2a7 flags 0x481 on isa sio4: type 16550A (multiport master) sio5 at 0x2a8-0x2af flags 0x481 on isa sio5: type 16550A (multiport) sio6 at 0x2b0-0x2b7 flags 0x481 on isa sio6: type 16550A (multiport) sio7 at 0x2b8-0x2bf flags 0x481 on isa sio7: type 16550A (multiport) sio8 at 0x2c0-0x2c7 flags 0x481 on isa sio8: type 16550A (multiport) sio9 at 0x2c8-0x2cf flags 0x481 on isa sio9: type 16550A (multiport) sio10 at 0x2d0-0x2d7 flags 0x481 on isa sio10: type 16550A (multiport) sio11 at 0x2d8-0x2df irq 5 flags 0x481 on isa sio11: type 16550A (multiport) sio12 at 0x180-0x187 flags 0x1381 on isa sio12: type 16550A (multiport) sio13 at 0x188-0x18f flags 0x1381 on isa sio13: type 16550A (multiport) sio14 at 0x190-0x197 flags 0x1381 on isa sio14: type 16550A (multiport) sio15 at 0x198-0x19f flags 0x1381 on isa sio15: type 16550A (multiport) sio16 at 0x1a0-0x1a7 flags 0x1381 on isa sio16: type 16550A (multiport) sio17 at 0x1a8-0x1af flags 0x1381 on isa sio17: type 16550A (multiport) sio18 at 0x1b0-0x1b7 flags 0x1381 on isa sio18: type 16550A (multiport) sio19 at 0x1b8-0x1bf irq 7 flags 0x1381 on isa sio19: type 16550A (multiport master) fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1225MB (2509920 sectors), 2490 cyls, 16 heads, 63 S/T, 512 B/S vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface de0: enabling 10baseT port IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default DUMMYNET initialized (000212) IP Filter: initialized. Default = pass all, Logging = enabled changing root device to wd0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 4:27:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from unix.za.net (unix.za.net [196.7.89.10]) by hub.freebsd.org (Postfix) with ESMTP id 0AFCF37BAE3 for ; Wed, 19 Jul 2000 04:27:32 -0700 (PDT) (envelope-from daniel@unix.za.net) Received: from daniel (helo=localhost) by unix.za.net with local-esmtp (Exim 3.14 #1) id 13Erze-000Mmx-00; Wed, 19 Jul 2000 13:26:26 +0200 Date: Wed, 19 Jul 2000 13:26:25 +0200 (SAST) From: Daniel Schroder To: Michael Vasilenko Cc: freebsd-stable@freebsd.org Subject: Re: slow system clock on 3.5-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is an option , often used with dummynet , HZ=10 or something like that. That affects your clock speed. I assume you changing it for more efficient bandwidth shaping. Only thing I can think of offhand :) --Daniel Schroder (Private email daniel@unix.za.net) Unix users .. South Africa To : freebsd-stable@freebsd.org From : Michael Vasilenko date : Jul 19 Address : acid@ci.net.ua Quality is a standard .. not a selling point On Wed, 19 Jul 2000, Michael Vasilenko wrote: > Hello ! > > Recently I've updated one of old routers - K5/100Mhz > from 3.3-RELEASE to 3.5-STABLE and discovered one "feature" - > system clock now goes sloooow, 1 'machine' second is like 3-5 > 'normal' seconds. > > Kernel config is slightly modified GENERIC. > > Where is the bug and how fix it ? > > dmesg: > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.5-STABLE #0: Tue Jul 18 11:43:14 EEST 2000 > root@hamlet.ci.net.ua:/usr/src/sys/compile/HAMLET > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 99716391 Hz > CPU: AMD K5 model 0 (99.72-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x501 Stepping = 1 > Features=0x3bf > real memory = 16777216 (16384K bytes) > avail memory = 14041088 (13712K bytes) > Preloaded elf kernel "kernel" at 0xc0280000. > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > chip1: rev 0x01 on pci0.7.0 > ide_pci0: rev 0x00 on pci0.7.1 > vga0: rev 0x00 int a irq 11 on pci0.13.0 > de0: rev 0x11 int a irq 10 on pci0.15.0 > de0: 21041 [10Mb/s] pass 1.1 > de0: address 00:80:48:ea:5c:e7 > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > sio4 at 0x2a0-0x2a7 flags 0x481 on isa > sio4: type 16550A (multiport master) > sio5 at 0x2a8-0x2af flags 0x481 on isa > sio5: type 16550A (multiport) > sio6 at 0x2b0-0x2b7 flags 0x481 on isa > sio6: type 16550A (multiport) > sio7 at 0x2b8-0x2bf flags 0x481 on isa > sio7: type 16550A (multiport) > sio8 at 0x2c0-0x2c7 flags 0x481 on isa > sio8: type 16550A (multiport) > sio9 at 0x2c8-0x2cf flags 0x481 on isa > sio9: type 16550A (multiport) > sio10 at 0x2d0-0x2d7 flags 0x481 on isa > sio10: type 16550A (multiport) > sio11 at 0x2d8-0x2df irq 5 flags 0x481 on isa > sio11: type 16550A (multiport) > sio12 at 0x180-0x187 flags 0x1381 on isa > sio12: type 16550A (multiport) > sio13 at 0x188-0x18f flags 0x1381 on isa > sio13: type 16550A (multiport) > sio14 at 0x190-0x197 flags 0x1381 on isa > sio14: type 16550A (multiport) > sio15 at 0x198-0x19f flags 0x1381 on isa > sio15: type 16550A (multiport) > sio16 at 0x1a0-0x1a7 flags 0x1381 on isa > sio16: type 16550A (multiport) > sio17 at 0x1a8-0x1af flags 0x1381 on isa > sio17: type 16550A (multiport) > sio18 at 0x1b0-0x1b7 flags 0x1381 on isa > sio18: type 16550A (multiport) > sio19 at 0x1b8-0x1bf irq 7 flags 0x1381 on isa > sio19: type 16550A (multiport master) > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 1225MB (2509920 sectors), 2490 cyls, 16 heads, 63 S/T, 512 B/S > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > de0: enabling 10baseT port > IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default > DUMMYNET initialized (000212) > IP Filter: initialized. Default = pass all, Logging = enabled > changing root device to wd0s1a > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 4:36:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from elit.ci.net.ua (elit.ci.net.ua [212.86.96.11]) by hub.freebsd.org (Postfix) with ESMTP id 0307037BC40 for ; Wed, 19 Jul 2000 04:36:49 -0700 (PDT) (envelope-from acid@ci.net.ua) Received: from localhost (acid@localhost) by elit.ci.net.ua (8.9.3/Who was second?) with ESMTP id OAA04713; Wed, 19 Jul 2000 14:35:49 +0300 (EEST) Date: Wed, 19 Jul 2000 14:35:49 +0300 (EEST) From: Michael Vasilenko To: Daniel Schroder Cc: freebsd-stable@freebsd.org Subject: Re: slow system clock on 3.5-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Daniel Schroder wrote: > There is an option , often used with dummynet , HZ=10 > or something like that. That affects your clock speed. > I assume you changing it for more efficient bandwidth > shaping. Only thing I can think of offhand :) No, I didn't touch it. Btw, which is value of HZ by default on x86 - 100 ? > > Recently I've updated one of old routers - K5/100Mhz > > from 3.3-RELEASE to 3.5-STABLE and discovered one "feature" - > > system clock now goes sloooow, 1 'machine' second is like 3-5 > > 'normal' seconds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 4:52:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lilzcvp.liwest.at (lilzcvp.liwest.at [212.33.32.230]) by hub.freebsd.org (Postfix) with SMTP id 2AD5137BA21; Wed, 19 Jul 2000 04:52:40 -0700 (PDT) (envelope-from bernhard.valenti@liwest.at) Received: from [212.33.57.70] by lilzcvp.relay.liwest.at (NTMail 4.30.0012/AB8573.63.b914fe78) with ESMTP id hyfwbaaa for ; Wed, 19 Jul 2000 13:52:19 +0100 Content-Length: 1144 Message-ID: X-Mailer: XFMail 1.4.6 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 19 Jul 2000 13:52:19 +0200 (CEST) From: bernhard.valenti@liwest.at To: freebsd-ports@freebsd.org, freebsd-stable@freebsd.org Subject: sblive driver/speakfrealy broken Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i just installed speakfreely from ports on my 4.0-stable with sblive soundcard. when i try to talk with sfmike ( eg: press space ) i get: wedge@cipher:~ > sfmike 10.0.0.51 Space bar switches talk/pause, Esc or "q" to quit, "." for chat text Talk: sfmike: unable to initialise audio. Unable to initialise audio. `awedge`a@`acipher`a:~ > i have to reset the terminal cause its messed up then. sfspeaker works fine though. not shure wether i should mail that to ports or stable list ( might be driver problem or speakfreely ) so i mailed both. anyone have any suggestions, fixes ? regards, bernhard valenti - ---------------------------------- E-Mail: bernhard.valenti@liwest.at Date: 19-Jul-2000 Time: 13:44:13 - ---------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE5dZZzaOk3gylcpTURAtxeAJ9cDbv9XYBZPkCa3i0maa1Sm0XdogCfaH61 /aUHW+ANAH19ZWDcJzdBwlE= =JKnJ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 5:23:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id C178E37B969 for ; Wed, 19 Jul 2000 05:23:42 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id HAA78794; Wed, 19 Jul 2000 07:23:36 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00071818513700.03027@dave.uhring.com> Date: Wed, 19 Jul 2000 07:23:36 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: David Uhring Subject: Re: is the ensoniq 1371 sound chip supported? Cc: freebsd-stable@FreeBSD.ORG, sean@rentul.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jul-00 David Uhring wrote: > I can't get mine to work, either. The kernel is compiled with device pcm > and > dmesg shows that the kernel recognizes the card. What /dev/ have to > be made? There is no pcm0 in /dev and MAKEDEV reports no such device, > although > pcm0 appears in dmesg. Running RELENG_4 compiled 12 Jul 00. In your kernel config file: device pcm device sbc (the es1371 *is* a Soundblaster-compatible) In /dev, do "./MAKEDEV snd0". Works great for me! -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 5:33:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsa-1-as01-7-a48.gd.uol.com.br (bsa-1-as01-7-a48.gd.uol.com.br [200.197.118.48]) by hub.freebsd.org (Postfix) with ESMTP id 81EB837B530 for ; Wed, 19 Jul 2000 05:33:34 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 769 invoked by uid 1001); 19 Jul 2000 12:33:16 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Wed, 19 Jul 2000 09:32:54 -0300 To: freebsd-stable@freebsd.org Subject: shutdown -p == shutdown -h ? Message-ID: <20000719093254.A763@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering why is shutdown -p behaving exactly like shutdown -r? I have both apm and apmd running. Is it due to the non-MFCed acpi code? Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 5:39:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F33837B56A for ; Wed, 19 Jul 2000 05:39:09 -0700 (PDT) (envelope-from simond@bumper.jellybaby.net) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id NAA93315; Wed, 19 Jul 2000 13:38:55 +0100 (BST) (envelope-from simond) Date: Wed, 19 Jul 2000 13:38:55 +0100 From: simond@irrelevant.org To: Mario Sergio Fujikawa Ferreira Cc: freebsd-stable@FreeBSD.ORG Subject: Re: shutdown -p == shutdown -h ? Message-ID: <20000719133855.E91771@irrelevant.org> References: <20000719093254.A763@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000719093254.A763@Fedaykin.here>; from lioux@uol.com.br on Wed, Jul 19, 2000 at 09:32:54AM -0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 09:32:54AM -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I was wondering why is shutdown -p behaving exactly > like shutdown -r? > I have both apm and apmd running. > Is it due to the non-MFCed acpi code? I get the same effect, but with the additional "feature" that once I turn my PC off when I let go of the power button it turns itself on again, -p used to work fine, no idea what happened. If it helps I'm using a k6-2/450 on a FIC-2013 MVP3 motherboard -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 5:44: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 769F737BE3C for ; Wed, 19 Jul 2000 05:43:56 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from k6 (k6.grasslake.net [192.168.2.1]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id HAA00318 for ; Wed, 19 Jul 2000 07:44:50 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <003c01bff17e$f6d85810$0102a8c0@k6> From: "Shawn Barnhart" To: Subject: natd changes? Date: Wed, 19 Jul 2000 07:43:39 -0500 Organization: Grasslake.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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After finally sorting out my "new" hardware's issues (bad stick of SDRAM, for those who care) and getting world to build again, I've noticed that natd has changed. Gone is the -pptp_alias option, replaced with the much more functional -redirect_proto option. Since I was a user of the old facility for a Cisco-Cisco GRE tunnel, this kind of caught me off guard. I did a quickie search of mailing lists and didn't find anything recent mentioning natd and pptp. No gripes mind you, we've now got generalized IP protocol redirection and not the application specific stuff we had before. But when did this change? (No probs with the binutils change, UPDATING is my new friend..) -- swb@grasslake.net Hard work often pays off after time, but laziness always pays off now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 5:52:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server26.ilap.com (server26-main.ilap.com [216.223.128.41]) by hub.freebsd.org (Postfix) with ESMTP id 3C7F337B97E for ; Wed, 19 Jul 2000 05:52:25 -0700 (PDT) (envelope-from phorechuk@docucom.ca) Received: from horechup (server11.docucom.ca [216.223.156.11]) by server26.ilap.com (Pro-8.9.3/8.9.3/ILAP.COM Internet Light and Power Inc.) with SMTP id IAA01378 for ; Wed, 19 Jul 2000 08:52:24 -0400 (EDT) Message-ID: <036901bff177$d8bb0280$73f8d7a5@docucom.ca> Reply-To: "Paul Horechuk" From: "Paul Horechuk" To: References: Subject: Linux emulation Date: Wed, 19 Jul 2000 07:52:42 -0400 Organization: DocuCom Imaging Solutions MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am currently running FreeBSD stable v3.5, as a result of a successful upgrade via cvsup. I've installed the linux_base-6.1 and several other libraries from the various linux packages. I needed RedHat 6.1 emulation to install an Amiga SDK (see www.amiga.com). At first this was failing due to missing the lingtk_1.2.so.6 (or something real close to that). After locating the appropriate package from ftp.ca.freebsd.org, the SDK was able to run. Now, when I supply my developer ID to obtain a System ID, the program returns a "not available" message and a socket error about a missing protocol. The Amiga developer team suggested that I take the question here, hoping that someone may know more about the protocols required for the Linux emulation. The process involves querying the network card (Netgear FX310A) for its MAC address. The card DOES work, and is providing on demand internet access via the tun0 device, to a Win95 station. I can use the Linux Netscape software for internet access on this FreeBSD box. Although Linux emulation has been configured in the kernel and Linux software does run, are there changes since FreeBSD 3.5 that would require an upgrade to 4.x? More information is available on request, but I need a direction to pursue. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 6: 5:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 6929237BD9A for ; Wed, 19 Jul 2000 06:05:49 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id QAA63138; Wed, 19 Jul 2000 16:04:36 +0300 (EEST) Date: Wed, 19 Jul 2000 16:04:36 +0300 From: Ruslan Ermilov To: Shawn Barnhart Cc: stable@FreeBSD.org Subject: Re: natd changes? Message-ID: <20000719160436.A62577@sunbay.com> Reply-To: stable@FreeBSD.org Mail-Followup-To: Shawn Barnhart , stable@FreeBSD.org References: <003c01bff17e$f6d85810$0102a8c0@k6> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <003c01bff17e$f6d85810$0102a8c0@k6>; from swb@grasslake.net on Wed, Jul 19, 2000 at 07:43:39AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 07:43:39AM -0500, Shawn Barnhart wrote: > After finally sorting out my "new" hardware's issues (bad stick of > SDRAM, for those who care) and getting world to build again, I've > noticed that natd has changed. Gone is the -pptp_alias option, replaced > with the much more functional -redirect_proto option. > > Since I was a user of the old facility for a Cisco-Cisco GRE tunnel, > this kind of caught me off guard. I did a quickie search of mailing > lists and didn't find anything recent mentioning natd and pptp. No > gripes mind you, we've now got generalized IP protocol redirection and > not the application specific stuff we had before. But when did this > change? > Here is the summary of changes into libalias(3) and natd(8) since 4.0-RELEASE: - Load Sharing using IP Network Address Translation (RFC 2391, LSNAT) - New options: -redirect_proto, -target_addr and -punch_fw - Removed -pptpalias since this is now done transparently by libalias(3) Note that you DO NOT need -redirect_proto for PPTP through NAT to work, this is now done transparently in libalias(3) and much better: - Multiple PPTP clients behind NAT to the same or different servers. - Single PPTP server behind NAT -- you just need to redirect TCP port 1723 to a local machine. Multiple servers behind NAT is possible but would require a simple API change. Please see manual page for details. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 6:10:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 9EA4837BE89; Wed, 19 Jul 2000 06:10:29 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id PAA08814; Wed, 19 Jul 2000 15:09:58 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id PAA00725; Wed, 19 Jul 2000 15:07:22 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C1256921.00484186 ; Wed, 19 Jul 2000 15:09:13 +0200 X-Lotus-FromDomain: ALCATEL To: Sascha Blank Cc: stable@FreeBSD.ORG, jmz@FreeBSD.ORG Message-ID: Date: Wed, 19 Jul 2000 15:08:39 +0200 Subject: Re: lost mouse when switching back to X Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, a bit late, but .... I've used your patch, but it does not apply completely clean (some converted to ?) I've patched manually the sources like you said, rebuilt XFree 4.01, reinstalled, and it seems to work **quite fine** (at least switching to the text console and back works as expected) Thanks a lot TfH Sascha Blank on 18/07/2000 17:24:52 To: Thierry HERBELOT/FR/ALCATEL@ALCATEL cc: stable@FreeBSD.ORG, jmz@FreeBSD.ORG Subject: Re: lost mouse when switching back to X Hello, On Mon, Jul 17, 2000 at 02:13:57PM +0200, Thierry.Herbelot@alcatel.fr wrote: > When I switch from X-Windows to the text console and then back to > X-windows (Ctrl-Alt-F1, then Alt-F9), the mouse pointer is fixed on the > screen (When I move the "physical" mouse, the pointer stays at the same > place on the X screen). I had this problem on my 4.1-RC machine running XFree86 4.0.1 and moused(8) with a PS/2 mouse as well. So I spent some hours digging through the XFree86 source code and finally came up with a quick'n' dirty patch that cures the problem at least on my system. I haven't contacted the XFree86 people about it yet as I want to hear some more "works for me here too!" before I'll file a PR. Although it's rather late it might be a candidate for inclusion in the ports collection before the 4.1-RELEASE. *** xc/programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c.orig Sat Feb 12 21:45:41 2000 --- xc/programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c Tue Jul 18 17:04:23 2000 *************** *** 165,171 **** --- 165,175 ---- mode.rate = rate > 0 ? rate : -1; mode.resolution = res > 0 ? res : -1; mode.accelfactor = -1; + #ifdef __FreeBSD__ + mode.level = 1; + #else mode.level = -1; + #endif ioctl(pInfo->fd, MOUSE_SETMODE, &mode); } #endif *** xc/programs/Xserver/hw/xfree86/input/mouse/mouse.c.orig Sat Jul 1 01:39:02 2000 --- xc/programs/Xserver/hw/xfree86/input/mouse/mouse.c Tue Jul 18 17:10:51 2000 *************** *** 692,701 **** --- 692,706 ---- pMse->protocolID = protocolID; } } + #ifndef __FreeBSD__ memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara)); + #endif if (automatic) { if (name) { + #ifdef __FreeBSD__ + memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara)); + #endif /* Possible protoPara overrides from SetupAuto. */ for (i = 0; i < sizeof(pMse->protoPara); i++) if (protoPara[i] != -1) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 6:20:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id B2FBF37B5EE for ; Wed, 19 Jul 2000 06:20:50 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 12801 invoked by uid 0); 19 Jul 2000 13:20:48 -0000 Received: from pc19f5d71.dip.t-dialin.net (HELO speedy.gsinet) (193.159.93.113) by mail.gmx.net with SMTP; 19 Jul 2000 13:20:48 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id HAA11588 for stable@FreeBSD.ORG; Wed, 19 Jul 2000 07:02:31 +0200 Date: Wed, 19 Jul 2000 07:02:31 +0200 From: Gerhard Sittig To: stable@FreeBSD.ORG Subject: Re: bioscall.s Message-ID: <20000719070231.K24476@speedy.gsinet> Mail-Followup-To: stable@FreeBSD.ORG References: <20000718015340.3073.qmail@web3102.mail.yahoo.com> <3973BA04.5AB2FFD@urx.com> <20000718194202.F24476@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000718194202.F24476@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Tue, Jul 18, 2000 at 07:42:02PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To clear this up a little more ... On Tue, Jul 18, 2000 at 19:42 +0200, Gerhard Sittig wrote: > On Mon, Jul 17, 2000 at 18:59 -0700, Kent Stewart wrote: > > > > Richard Stanaford wrote: > > > > > > make buildkernel KERNEL="NOVA" > > > > The quotes are evil. [ ... ] ^^^^^^^^^^^^^^^^^^^ > > This is somewhat hard to believe. [ ... ] Everything else was since I read the message as "with quotes it won't compile, without it does". But I understand this was not the problem and we're done discussing this. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 6:30:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 61E6237BF33; Wed, 19 Jul 2000 06:30:07 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id PAA20593; Wed, 19 Jul 2000 15:29:35 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id PAA11464; Wed, 19 Jul 2000 15:27:00 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C1256921.004A21A1 ; Wed, 19 Jul 2000 15:29:42 +0200 X-Lotus-FromDomain: ALCATEL To: bernhard.valenti@liwest.at Cc: freebsd-ports@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Message-ID: Date: Wed, 19 Jul 2000 15:28:15 +0200 Subject: Re: sblive driver/speakfrealy broken Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have tried to use the sepakfreely port and I've seen that it is only compatible with "OSS" soud driver of the 3.x branch : the pcm driver of 3.x or the "newpcm" driver of 4.x seem to be missing one ioctl (which nobody seems interested in adding to the native pcm driver) TfH BtW : speakfreely should be marked as "FORBIDDEN" on the 4.x branch (as long as the sound driver has not been upgraded) (note to the porters : I **know** that FreeBSD is mainly a user-supported OS and that resources are scarce, so we have to live with such inconveniencies) bernhard.valenti@liwest.at on 19/07/2000 13:52:19 To: freebsd-ports@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG cc: (bcc: Thierry HERBELOT/FR/ALCATEL) Subject: sblive driver/speakfrealy broken -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i just installed speakfreely from ports on my 4.0-stable with sblive soundcard. when i try to talk with sfmike ( eg: press space ) i get: wedge@cipher:~ > sfmike 10.0.0.51 Space bar switches talk/pause, Esc or "q" to quit, "." for chat text Talk: sfmike: unable to initialise audio. Unable to initialise audio. `awedge`a@`acipher`a:~ > i have to reset the terminal cause its messed up then. sfspeaker works fine though. not shure wether i should mail that to ports or stable list ( might be driver problem or speakfreely ) so i mailed both. anyone have any suggestions, fixes ? regards, bernhard valenti - ---------------------------------- E-Mail: bernhard.valenti@liwest.at Date: 19-Jul-2000 Time: 13:44:13 - ---------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE5dZZzaOk3gylcpTURAtxeAJ9cDbv9XYBZPkCa3i0maa1Sm0XdogCfaH61 /aUHW+ANAH19ZWDcJzdBwlE= =JKnJ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 6:38:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from forge.aber.nu (forge.aber.nu [151.189.45.20]) by hub.freebsd.org (Postfix) with ESMTP id CBCE437B5EE for ; Wed, 19 Jul 2000 06:38:47 -0700 (PDT) (envelope-from freddy@forge.aber.nu) Received: by forge.aber.nu (Postfix, from userid 1013) id 7E10F47D9; Wed, 19 Jul 2000 15:38:13 +0200 (CEST) Date: Wed, 19 Jul 2000 15:38:13 +0200 From: freddy@forge.aber.nu To: freebsd-stable@freebsd.org Subject: make world failure (4.1-RC) Message-ID: <20000719153813.B30069@forge.aber.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a problem: I'm currently running 4.1-RC (Saturday) and now I wanted to upgrade the source again, what I did by CVSupping it. (before that I deleted /usr/src to have a fresh source-tree) After that step I did a "make world" which failes after some minutes: [...] ".depend", line 408: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Any ideas how I can fix that? Thank you, Freddy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7: 8:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 303B037B60A for ; Wed, 19 Jul 2000 07:08:29 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id B26D09B05; Wed, 19 Jul 2000 15:08:36 +0100 (BST) Date: Wed, 19 Jul 2000 15:08:36 +0100 From: Josef Karthauser To: R Joseph Wright Cc: Matthew Hunt , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719150836.K630@pavilion.net> Mail-Followup-To: Josef Karthauser , R Joseph Wright , Matthew Hunt , freebsd-stable@FreeBSD.ORG References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> <20000718175525.A10074@manatee.mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000718175525.A10074@manatee.mammalia.org>; from rjoseph@mammalia.org on Tue, Jul 18, 2000 at 05:55:25PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:55:25PM -0700, R Joseph Wright wrote: > > The thing that really bugs me about ls is the lack of bright colors like you > get with gnuls. The blue is so dark it blends in with the black background > of the console. I spent several hours looking through the code to see if I > could change that, but alas I did not understand it :-(. > And, sorry to rant, but the default colors are horrid, too! Do 'ls -G /dev' > to see what I mean. AAaaarh! > Colours are always a personal preference. No answer is right for everyone. Read the manual page for ls and define your own colours in your environment. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:15: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id E9D3237B60A for ; Wed, 19 Jul 2000 07:14:57 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id JAA02543 for ; Wed, 19 Jul 2000 09:15:47 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <00f401bff18b$d5557940$b8209fc0@campbellmithun.com> From: "Shawn Barnhart" To: References: <003c01bff17e$f6d85810$0102a8c0@k6> <20000719160436.A62577@sunbay.com> Subject: Re: natd changes? Date: Wed, 19 Jul 2000 09:15:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Ruslan Ermilov" | Here is the summary of changes into libalias(3) and natd(8) since | 4.0-RELEASE: | | - Load Sharing using IP Network Address Translation (RFC 2391, LSNAT) | - New options: -redirect_proto, -target_addr and -punch_fw | - Removed -pptpalias since this is now done transparently by libalias(3) | | Note that you DO NOT need -redirect_proto for PPTP through NAT to work, | this is now done transparently in libalias(3) and much better: Do you need it for passing non-PPTP, ie router-router, GRE traffic? Or any of the "other" IP protocols? | - Multiple PPTP clients behind NAT to the same or different servers. | | - Single PPTP server behind NAT -- you just need to redirect TCP | port 1723 to a local machine. Multiple servers behind NAT is | possible but would require a simple API change. | | Please see manual page for details. Which one? Neither natd(8) or libalias(3) mentions PPTP other than to give the author(s) credit for writing support for it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:18:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 5466337B60A for ; Wed, 19 Jul 2000 07:18:28 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id HAA22989; Wed, 19 Jul 2000 07:18:20 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007191418.HAA22989@freeway.dcfinc.com> Subject: Re: Color ls In-Reply-To: <20000718225803.B11027@manatee.mammalia.org> from R Joseph Wright at "Jul 18, 0 10:58:03 pm" To: rjoseph@mammalia.org (R Joseph Wright) Date: Wed, 19 Jul 2000 07:18:20 -0700 (MST) Cc: mike@adept.org, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, R Joseph Wright wrote: > This is not so. You have to use it like 'gnuls --color=auto' and > there will be no such mess. Gnuls also shows colors in the standard > xterm without any of this termcap insanity or TERM=xterm-color > nonsense. It's also much easier on the eyes, at least for me. So, I'm on this 2.2.8-STABLE machine, running the xterm that came with it. I telnet to a 3.4 machine, type "echo $TERM" and get "xterms". I type "colorls -G" and get colors. What's all the fuss about? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:24: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 8E0E437BE1E for ; Wed, 19 Jul 2000 07:23:52 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id KAA11121; Wed, 19 Jul 2000 10:24:18 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Wed, 19 Jul 2000 10:24:18 -0400 (EDT) From: "Brandon D. Valentine" To: John Reynolds Cc: stable@FreeBSD.ORG Subject: Re: buildworld breakage as of 1:49am 7/19/2000 In-Reply-To: <200007190851.BAA95748@cx587235-a.chnd1.az.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, John Reynolds wrote: >Hello all, > >I apologize in advance if I missed a "HEADS UP" regarding instability in the >source tree within the last few hours (my -stable subscription gets sent to >another address I don't have access to here). For future reference if you cannot read your stable mail before you cvsup, you can always read it on the web at: http://docs.FreeBSD.org/mail/ Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:25:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 6190937BDF0; Wed, 19 Jul 2000 07:25:09 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id PAA36741; Wed, 19 Jul 2000 15:25:05 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA07457; Wed, 19 Jul 2000 15:25:01 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007191425.PAA07457@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hunt Cc: Josef Karthauser , Ben Smithurst , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.org, brian@Awfulhak.org Subject: Re: Color ls In-Reply-To: Message from Matthew Hunt of "Tue, 18 Jul 2000 17:11:41 PDT." <20000718171141.A97774@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 15:25:01 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote: > > > joe@cuddy[503]: export TERM=xterm-color > > joe@cuddy[504]: vi > > xterm-color: Unknown terminal type > > Visual needs addressable cursor or upline capability > > :q > > joe@cuddy[505]: uname -a > > SunOS cuddy 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-1 > > That's not the issue. > > What we want to do is have TERM=xterm be the same as xterm-color > is now. > > If you log in to a FreeBSD box from your Sun, and *then* set > TERM=xterm-color and run things on the FreeBSD box, do the color > escape sequences screw anything up? Despite being against ls -G, I'd certainly advocate this change... I'm surprised this hasn't already been done. The never-to-be-committed evil is ``alias ls="ls -G"'' in /etc/profile ! > -- > Matthew Hunt * Stay close to the Vorlon. > http://www.pobox.com/~mph/ * -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:26:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 47E6B37BE1E for ; Wed, 19 Jul 2000 07:26:30 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13Euno-000C1Z-00; Wed, 19 Jul 2000 15:26:24 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA57249; Wed, 19 Jul 2000 15:26:24 +0100 (BST) (envelope-from jcm) Date: Wed, 19 Jul 2000 15:26:24 +0100 From: j mckitrick To: "Chad R. Larson" Cc: R Joseph Wright , mike@adept.org, freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000719152624.A57101@dogma.freebsd-uk.eu.org> References: <20000718225803.B11027@manatee.mammalia.org> <200007191418.HAA22989@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007191418.HAA22989@freeway.dcfinc.com>; from chad@DCFinc.com on Wed, Jul 19, 2000 at 07:18:20AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 07:18:20AM -0700, Chad R. Larson wrote: > So, I'm on this 2.2.8-STABLE machine, running the xterm that came > with it. I telnet to a 3.4 machine, type "echo $TERM" and get > "xterms". I type "colorls -G" and get colors. What's all the fuss > about? Going out on a limb here.... IIUC, i believe some older machines (solaris?) do not have termcaps that allow color xterms thru telnet connections. Or something like that. So your setup works fine, but if you telnet to a SOlaris box, it might not work is Solaris doesn't have a termcap for 'xterms' or 'xterm-color'. I should add this is the default config, right? It can be changed, of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:29:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id D654937BE8B; Wed, 19 Jul 2000 07:29:15 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13EuqY-0006dV-00; Wed, 19 Jul 2000 15:29:14 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA57288; Wed, 19 Jul 2000 15:29:13 +0100 (BST) (envelope-from jcm) Date: Wed, 19 Jul 2000 15:29:13 +0100 From: j mckitrick To: Brian Somers Cc: Matthew Hunt , Josef Karthauser , Ben Smithurst , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@freebsd.org Subject: Re: Color ls Message-ID: <20000719152913.B57101@dogma.freebsd-uk.eu.org> References: <200007191425.PAA07457@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007191425.PAA07457@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Jul 19, 2000 at 03:25:01PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 03:25:01PM +0100, Brian Somers wrote: > I'm surprised this hasn't already been done. The never-to-be-committed > evil is ``alias ls="ls -G"'' in /etc/profile ! What about in ~/.profile ? ;) jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:35:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id B1C2237BEF3; Wed, 19 Jul 2000 07:35:37 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id PAA36860; Wed, 19 Jul 2000 15:35:33 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA07594; Wed, 19 Jul 2000 15:35:30 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007191435.PAA07594@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Somers Cc: Matthew Hunt , Josef Karthauser , Ben Smithurst , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.org, brian@Awfulhak.org Subject: Re: Color ls In-Reply-To: Message from Brian Somers of "Wed, 19 Jul 2000 15:25:01 BST." <200007191425.PAA07457@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 15:35:30 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > > What we want to do is have TERM=xterm be the same as xterm-color > > is now. [.....] I wrote: > Despite being against ls -G, I'd certainly advocate this change... > I'm surprised this hasn't already been done. The never-to-be-committed > evil is ``alias ls="ls -G"'' in /etc/profile ! Let me retract that (it's been a long day!). As Mike Smith points out, if FreeBSD's xterm can do color, it should be setting TERM to color-xterm. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:38:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rock.ctm.ru (rock.ctm.ru [195.131.63.33]) by hub.freebsd.org (Postfix) with SMTP id 3531437BFB0 for ; Wed, 19 Jul 2000 07:38:31 -0700 (PDT) (envelope-from kest@ctm.ru) Received: (qmail 5109 invoked from network); 19 Jul 2000 13:46:05 -0000 Received: from unknown (HELO gremlin) (192.168.1.109) by 192.168.1.6 with SMTP; 19 Jul 2000 13:46:05 -0000 Date: Wed, 19 Jul 2000 18:40:22 -0000 To: freebsd-stable@FreeBSD.org From: kest@ctm.ru Subject: Subscribe me, plz Reply-To: kest@ctm.ru Organization: CTM Ltd. X-Mailer: Opera 4.01 build 754 X-Priority: Normal Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20000719143831.3531437BFB0@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:42:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.isltd.insignia.com (gatekeeper.isltd.insignia.com [195.153.60.130]) by hub.freebsd.org (Postfix) with ESMTP id A115E37BDF0; Wed, 19 Jul 2000 07:42:11 -0700 (PDT) (envelope-from martin.hopkins@insignia.com) Received: from saracen.isltd.insignia.com (saracen.isltd.insignia.com [193.112.17.171]) by gatekeeper.isltd.insignia.com (8.9.3/8.9.3) with ESMTP id PAA09354; Wed, 19 Jul 2000 15:40:43 +0100 (BST) Received: from luggage.isltd.insignia.com (luggage.isltd.insignia.com [193.112.17.47]) by saracen.isltd.insignia.com (8.8.4/BSCF-1.2) with SMTP id PAA11899; Wed, 19 Jul 2000 15:40:39 +0100 (BST) From: Martin Hopkins MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14709.48615.161851.90182@luggage.isltd.insignia.com> Date: Wed, 19 Jul 2000 15:40:39 +0100 (BST) To: Brian Somers Cc: Matthew Hunt , Josef Karthauser , Ben Smithurst , Kris Kennaway , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-Reply-To: <200007191425.PAA07457@hak.lan.Awfulhak.org> References: <20000718171141.A97774@wopr.caltech.edu> <200007191425.PAA07457@hak.lan.Awfulhak.org> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Brian" == Brian Somers writes: >> On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote: >> >> > joe@cuddy[503]: export TERM=xterm-color >> > joe@cuddy[504]: vi >> > xterm-color: Unknown terminal type >> > Visual needs addressable cursor or upline capability >> > :q >> > joe@cuddy[505]: uname -a >> > SunOS cuddy 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-1 >> >> That's not the issue. >> >> What we want to do is have TERM=xterm be the same as xterm-color >> is now. >> >> If you log in to a FreeBSD box from your Sun, and *then* set >> TERM=xterm-color and run things on the FreeBSD box, do the color >> escape sequences screw anything up? Brian> Despite being against ls -G, I'd certainly advocate this change... Brian> I'm surprised this hasn't already been done. The never-to-be-committed Brian> evil is ``alias ls="ls -G"'' in /etc/profile ! or /usr/share/skel/dot.profile Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:43:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D9A0A37BD57 for ; Wed, 19 Jul 2000 07:43:32 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id RAA67373; Wed, 19 Jul 2000 17:43:14 +0300 (EEST) Date: Wed, 19 Jul 2000 17:43:14 +0300 From: Ruslan Ermilov To: Shawn Barnhart Cc: stable@FreeBSD.ORG Subject: Re: natd changes? Message-ID: <20000719174314.A66673@sunbay.com> Mail-Followup-To: Shawn Barnhart , stable@FreeBSD.ORG References: <003c01bff17e$f6d85810$0102a8c0@k6> <20000719160436.A62577@sunbay.com> <00f401bff18b$d5557940$b8209fc0@campbellmithun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <00f401bff18b$d5557940$b8209fc0@campbellmithun.com>; from swb@grasslake.net on Wed, Jul 19, 2000 at 09:15:46AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 09:15:46AM -0500, Shawn Barnhart wrote: > ----- Original Message ----- > From: "Ruslan Ermilov" > > | Here is the summary of changes into libalias(3) and natd(8) since > | 4.0-RELEASE: > | > | - Load Sharing using IP Network Address Translation (RFC 2391, LSNAT) > | - New options: -redirect_proto, -target_addr and -punch_fw > | - Removed -pptpalias since this is now done transparently by libalias(3) > | > | Note that you DO NOT need -redirect_proto for PPTP through NAT to work, > | this is now done transparently in libalias(3) and much better: > > Do you need it for passing non-PPTP, ie router-router, GRE traffic? Or any > of the "other" IP protocols? > Yes, `-redirect_proto gre foo' will redirect non-PPTP GRE traffic to local host `foo' while it is simultaneously possible to run PPTP from multiple local clients and it should be handled correctly. In other words, libalias(3) checks whether the particular GRE packet belongs to an already established PPTP session, and if it does, it takes the proper address from this PPTP session. Otherwise, it checks for -redirect_proto rules. > | - Multiple PPTP clients behind NAT to the same or different servers. > | > | - Single PPTP server behind NAT -- you just need to redirect TCP > | port 1723 to a local machine. Multiple servers behind NAT is > | possible but would require a simple API change. > | > | Please see manual page for details. > > Which one? Neither natd(8) or libalias(3) mentions PPTP other than to give > the author(s) credit for writing support for it. > I meant for other options like -lsnat, -punch_fw and -target_address. I think we need to add the PPTP info to both libalias(3) and natd(8) manpages, but it will happen after my vacation. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:46:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from home.se (smtp1.home.se [195.66.45.70]) by hub.freebsd.org (Postfix) with ESMTP id 40A0B37C0BD for ; Wed, 19 Jul 2000 07:46:36 -0700 (PDT) (envelope-from alastyr@home.se) Received: from Sorcery (cvx-sto-1-109.ppp.netlink.se [212.242.103.13]) by home.se (8.8.8/8.8.7) with ESMTP id QAA74632 for ; Wed, 19 Jul 2000 16:46:33 +0200 (CEST) Date: Wed, 19 Jul 2000 16:45:24 +0000 (GMT) From: Joel Lindau X-Sender: nevyn@Sorcery.se To: freebsd-stable@freebsd.org Subject: Issues with './MAKEDEV snd' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-9 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have two boxes both running FreeBSD 4.1-RC. A couple of days ago i decided to compile a kernel with support for the soundcard in the second computer. Everything seemed to be ok. My soundcard is found etc. [ -- ] sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 pcm1: on sbc0 [ -- ] But when i try to './MAKEDEV snd' i get the following errors: [ -- ] (root@Infinite):/dev:# ./MAKEDEV snd expr: syntax error bad node: mknod mixer [ -- ] In /dev/sndstat everything seems to be ok. [ -- ] FreeBSD Audio Driver (newpcm) Jul 18 2000 17:53:48 Installed devices: pcm1: at io 0x220 irq 5 drq 1:5 (1p/1r channels) [ -- ] But /dev/dsp isn=B4t working, which is also first of all being linked to itself instead of /dev/dsp0. Not having a working soundcard on that computer isn't really a fatal issue. But today i thought i should try './MAKEDEV snd' on my main computer where i have a soundblaster pci128 just to see if it works there. It got the same error output as before. This seems pretty odd, cause i know it has worked before in 4.0-RELEASE. I also asked a irc-friend with=20 a less recent build to try the same and he got the same errors. Any ideas ?=20 /-- =09Joel Lindau =09Nevyn -- #FreeBSD.se, #unix.se =09=09=09=09=09--/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 7:56:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sohara.dyndns.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 7B19637B696; Wed, 19 Jul 2000 07:56:20 -0700 (PDT) (envelope-from steve@sohara.dyndns.org) Received: (from steve@localhost) by sohara.dyndns.org (8.9.3/8.9.3) id QAA20862; Wed, 19 Jul 2000 16:03:22 +0100 (IST) (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200007191435.PAA07594@hak.lan.Awfulhak.org> Date: Wed, 19 Jul 2000 16:03:21 +0100 (IST) From: "Steve O'Hara-Smith" To: Brian Somers Subject: Re: Color ls Cc: freebsd-stable@FreeBSD.org, "Ron 'The InSaNe One' Rosson" , Kris Kennaway , Ben Smithurst , Josef Karthauser , Matthew Hunt Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jul-00 Brian Somers wrote: > Let me retract that (it's been a long day!). As Mike Smith points > out, if FreeBSD's xterm can do color, it should be setting TERM to > color-xterm. Everybody seems to have missed this but there is a mechanism to make xterm set TERM to xterm-color which also makes most other X apps work in colour. The trick is *customization: -color In .Xdefaults (or anything else that sets X resources). I gather (I have not tested) that this even does the right thing if you run an xterm on a mono X-Server. -- Steve O'Hara-Smith http://sohara.webhop.net/ A Better Way To Focus The Sun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 8:14:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 381C037BDDC for ; Wed, 19 Jul 2000 08:14:51 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id EF87A450; Wed, 19 Jul 2000 08:14:49 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id IAA03547; Wed, 19 Jul 2000 08:14:48 -0700 (PDT) Message-ID: <3975C5E8.CEA8E9A0@cup.hp.com> Date: Wed, 19 Jul 2000 08:14:48 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Paul Horechuk Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation References: <036901bff177$d8bb0280$73f8d7a5@docucom.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul Horechuk wrote: > > emulation. The process involves querying the network card (Netgear FX310A) > for its MAC address. The card DOES work, and is providing on demand internet Look at any Linuxulator messages with dmesg(8) (or in /var/log/messages). It may be possible that we need to implement some ioctls... > Although Linux emulation has been configured in the kernel and Linux > software does run, are there changes since FreeBSD 3.5 that would require an > upgrade to 4.x? Yes. I suggest upgrading to 4-stable. This does not guarantee that the problem goes away, but does guarantee that we can have it fixed. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 8:17:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 0FBDE37C0ED for ; Wed, 19 Jul 2000 08:17:07 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000719151706.QKBA11071.mail.rdc1.il.home.com@math.missouri.edu> for ; Wed, 19 Jul 2000 08:17:06 -0700 Message-ID: <3975C623.1EFBFAE8@math.missouri.edu> Date: Wed, 19 Jul 2000 10:15:47 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: Small handbook error References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeff Wyman wrote: > > > I'm a complete idiot who doesn't even know how to make diffs, so I thought > I'd just let everybody know right away instead of figuring out how to > write a diff and holding out on you all for the time that may take - I'm > a slow learner. > The hardest thing about making diffs is to remember which order to put the files. Do you say: diff -c new-file old-file or diff -c old-file new-file ? Alas, neither the man page for diff, nor the man page for patch are that helpful - they give hints about this, but nothing explicit. If someone tells me authoritively what the answer is, maybe I'll submit a send-pr changing the man pages for diff and patch so that they are more explicit on this issue. (I always figure it out by a process of trial and error.) -- Stephen Montgomery-Smith Department of Mathematics, University of Missouri, Columbia, MO 65211 Phone 573-882-4540, fax 573-882-1869 http://www.math.missouri.edu/~stephen stephen@math.missouri.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 8:30:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 3536937BED8 for ; Wed, 19 Jul 2000 08:30:52 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id RAA44667; Wed, 19 Jul 2000 17:30:51 +0200 (CEST) (envelope-from olli) Date: Wed, 19 Jul 2000 17:30:51 +0200 (CEST) Message-Id: <200007191530.RAA44667@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Issues with './MAKEDEV snd' X-Newsgroups: list.freebsd-stable In-Reply-To: <8l4fvt$24vi$1@atlantis.rz.tu-clausthal.de> Organization: Administration TU Clausthal MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In list.freebsd-stable Joel Lindau wrote: > But when i try to './MAKEDEV snd' i get the following errors: > [...] Use ``./MAKEDEV snd1'' (because your card was probed as pcm1). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 8:37:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id A986B37BEF5 for ; Wed, 19 Jul 2000 08:37:39 -0700 (PDT) (envelope-from fred@veriohosting.com) Received: by gatekeeper.veriohosting.com; Wed, 19 Jul 2000 09:37:37 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma003500; Wed, 19 Jul 00 09:37:29 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id JAA12593; Wed, 19 Jul 2000 09:37:29 -0600 (MDT) Date: Wed, 19 Jul 2000 09:46:05 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: simond@irrelevant.org Cc: Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG Subject: Re: shutdown -p == shutdown -h ? In-Reply-To: <20000719133855.E91771@irrelevant.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that -p and -h work the same (ie dont powerdown) when apmd isn't running on my toshiba 300CT laptop. If, however, I have apmd running correctly, then shutdown -p powers the box down and shutdown -h brings it to the point where it sasy 'it's ok to shut down your box now...' Fred On Wed, 19 Jul 2000 simond@irrelevant.org wrote: > On Wed, Jul 19, 2000 at 09:32:54AM -0300, Mario Sergio Fujikawa Ferreira wrote: > > Hi, > > > > I was wondering why is shutdown -p behaving exactly > > like shutdown -r? > > I have both apm and apmd running. > > Is it due to the non-MFCed acpi code? > > I get the same effect, but with the additional "feature" that once I > turn my PC off when I let go of the power button it turns itself on > again, -p used to work fine, no idea what happened. > > If it helps I'm using a k6-2/450 on a FIC-2013 MVP3 motherboard > > -- > Simon Dick simond@irrelevant.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Fred Clift - fred@veriohosting.com -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 8:46:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from home.se (smtp1.home.se [195.66.45.70]) by hub.freebsd.org (Postfix) with ESMTP id B144F37BF3D for ; Wed, 19 Jul 2000 08:46:09 -0700 (PDT) (envelope-from alastyr@home.se) Received: from Sorcery (cvx-sto-1-109.ppp.netlink.se [212.242.103.13]) by home.se (8.8.8/8.8.7) with ESMTP id RAA85166 for ; Wed, 19 Jul 2000 17:46:06 +0200 (CEST) Date: Wed, 19 Jul 2000 17:44:56 +0000 (GMT) From: Joel Lindau X-Sender: nevyn@Sorcery.se To: freebsd-stable@FreeBSD.ORG Subject: Re: Issues with './MAKEDEV snd' In-Reply-To: <200007191530.RAA44667@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-9 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh, stupid of me. It works on both boxes now, with snd1 on that box and snd0 on the other. Thanks for pointing it out. /-- =09Joel Lindau =09Nevyn -- #FreeBSD.se, #unix.se =09=09=09=09=09--/ On Wed, 19 Jul 2000, Oliver Fromme wrote: > In list.freebsd-stable Joel Lindau wrote: > > But when i try to './MAKEDEV snd' i get the following errors: > > [...] >=20 > Use ``./MAKEDEV snd1'' (because your card was probed as pcm1). >=20 > Regards > Oliver >=20 > --=20 > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > Addresses will change soon!! If in doubt: www.fromme.com >=20 > "In jedem St=FCck Kohle wartet ein Diamant auf seine Geburt" > (Terry Pratchett) >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 9: 9: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hyde.ssec.wisc.edu (hyde.ssec.wisc.edu [144.92.108.217]) by hub.freebsd.org (Postfix) with ESMTP id BFBBC37BF1D for ; Wed, 19 Jul 2000 09:08:57 -0700 (PDT) (envelope-from dglo@hyde.ssec.wisc.edu) Received: from hyde.ssec.wisc.edu (dglo@localhost [127.0.0.1]) by hyde.ssec.wisc.edu (8.9.3/8.9.3) with ESMTP id LAA26196; Wed, 19 Jul 2000 11:08:37 -0500 (CDT) Message-Id: <200007191608.LAA26196@hyde.ssec.wisc.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Steve O'Hara-Smith" Cc: "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-reply-to: Your message of "Wed, 19 Jul 2000 09:09:15 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 11:08:37 -0500 From: Dave Glowacki Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steve O'Hara-Smith" wrote: > > On 19-Jul-00 Ron 'The InSaNe One' Rosson wrote: > > How does one in .Xdefaults make your xterm "look color" > > I have > > *customization: -color > > In my .Xdefaults which takes care of xterm and quite a lot of other > apps as well. My .Xdefaults file (which has been hacked on for over 12 years, yikes!) has: #ifdef COLOR *customization: -color #else *customization: -mono #endif In the (increasingly unlikely) event that you ever run on a monochrome system, this will do the right thing... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 9:30:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by hub.freebsd.org (Postfix) with ESMTP id CAF7037BF76 for ; Wed, 19 Jul 2000 09:30:27 -0700 (PDT) (envelope-from bmah@cisco.com) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.0.Beta3/8.11.0.Beta3) id e6JGTmU67196; Wed, 19 Jul 2000 09:29:48 -0700 (PDT) (envelope-from bmah) Message-Id: <200007191629.e6JGTmU67196@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: ru@sunbay.com Cc: stable@FreeBSD.ORG Subject: Re: natd changes? In-Reply-To: <20000719160436.A62577@sunbay.com> References: <003c01bff17e$f6d85810$0102a8c0@k6> <20000719160436.A62577@sunbay.com> Comments: In-reply-to Ruslan Ermilov message dated "Wed, 19 Jul 2000 16:04:36 +0300." From: bmah@cisco.com (Bruce A. Mah) Reply-To: bmah@cisco.com X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-273678308P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 09:29:48 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-273678308P Content-Type: text/plain; charset=us-ascii If memory serves me right, Ruslan Ermilov wrote: > Here is the summary of changes into libalias(3) and natd(8) since > 4.0-RELEASE: > > - Load Sharing using IP Network Address Translation (RFC 2391, LSNAT) > - New options: -redirect_proto, -target_addr and -punch_fw > - Removed -pptpalias since this is now done transparently by libalias(3) Just a suggestion...would it be a good idea to put an appropriate item in RELNOTES.TXT? Bruce. --==_Exmh_-273678308P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: dxzLvJfsRyK5Cgn4lS0Hj91MfNVnAk9Q iQA/AwUBOXXXfNjKMXFboFLDEQL+2wCgkakQxRkilOD+6mP68PeltgAMPx8AoI2n x/EtyjTIfajGoRnlozjnfK9/ =eJUV -----END PGP SIGNATURE----- --==_Exmh_-273678308P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10: 0: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [198.143.31.30]) by hub.freebsd.org (Postfix) with ESMTP id CECDA37BF28 for ; Wed, 19 Jul 2000 09:59:59 -0700 (PDT) (envelope-from mi@virtual-estates.net) Received: from misha.privatelabs.com (misha.privatelabs.com [198.143.31.6]) by privatecube.privatelabs.com (8.9.3/8.9.2) with ESMTP id LAA01990 for ; Wed, 19 Jul 2000 11:58:59 -0400 Received: from virtual-estates.net (localhost [127.0.0.1]) by misha.privatelabs.com (8.9.3/8.9.3) with ESMTP id MAA11202 for ; Wed, 19 Jul 2000 12:55:51 -0400 (EDT) (envelope-from mi@virtual-estates.net) Message-Id: <200007191655.MAA11202@misha.privatelabs.com> Date: Wed, 19 Jul 2000 12:55:48 -0400 (EDT) From: mi@aldan.algebra.com, UNEXPECTED_DATA_AFTER_ADDRESS@.SYNTAX-ERROR Subject: Re: Issues with './MAKEDEV snd' To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200007191530.RAA44667@dorifer.heim3.tu-clausthal.de> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Jul, Oliver Fromme wrote: = In list.freebsd-stable Joel Lindau wrote: = > But when i try to './MAKEDEV snd' i get the following errors: = > [...] = = Use ``./MAKEDEV snd1'' (because your card was probed as pcm1). Which means, he should not have ``device pcm0'' in the kernel -- only ``device pcm''. Right? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10: 5: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id DCBD937B62A for ; Wed, 19 Jul 2000 10:04:57 -0700 (PDT) (envelope-from fred@veriohosting.com) Received: by gatekeeper.veriohosting.com; Wed, 19 Jul 2000 11:04:56 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma026043; Wed, 19 Jul 00 11:04:30 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id LAA21281; Wed, 19 Jul 2000 11:04:29 -0600 (MDT) Date: Wed, 19 Jul 2000 11:13:06 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: simond@irrelevant.org Cc: Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG Subject: Re: shutdown -p == shutdown -h ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I intended to say with this post, which I sent prematurely, that I had the same problem when my bios settings for my apm stuff changed and/or when I screwed up my apm settings without knowing it. So, any hardware or new kernel configs recently that might have broken your apm? -- Fred Clift - fred@veriohosting.com -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10:11: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 89FE637BF35 for ; Wed, 19 Jul 2000 10:10:56 -0700 (PDT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id e6JHAs911032 for ; Wed, 19 Jul 2000 19:10:54 +0200 (CEST) Received: from rose.lpthe.jussieu.fr ([134.157.10.102]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id TAA18602 for ; Wed, 19 Jul 2000 19:10:52 +0200 (MET DST) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.9.3/8.9.3) id OAA00525 for freebsd-stable@FreeBSD.ORG; Wed, 19 Jul 2000 14:30:03 +0200 (CEST) (envelope-from michel) Date: Wed, 19 Jul 2000 14:30:03 +0200 From: Michel Talon To: freebsd-stable@FreeBSD.ORG Subject: Re: Color ls Message-ID: <20000719143003.A453@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> <20000718175525.A10074@manatee.mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000718175525.A10074@manatee.mammalia.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 05:55:25PM -0700, R Joseph Wright wrote: > On Tue, Jul 18, 2000 at 05:04:20PM -0700, Matthew Hunt wrote: > The thing that really bugs me about ls is the lack of bright colors like you > get with gnuls. The blue is so dark it blends in with the black background > of the console. I spent several hours looking through the code to see if I > could change that, but alas I did not understand it :-(. > And, sorry to rant, but the default colors are horrid, too! Do 'ls -G /dev' > to see what I mean. AAaaarh! > Programs like mutt, tin etc. use ansi colors. You can change the corresponding colors in .Xdefaults or similar. For example i have: XTerm*VT100.Translations: #override \n\ F2: set-scrollbar(toggle)\n\ Prior: scroll-back(1,halfpage)\n\ Next: scroll-forw(1,halfpage) XTerm*VT100*colorMode: on XTerm*VT100*colorBDMode: on XTerm*VT100*colorBD: blue XTerm*VT100*colorULMode: on XTerm*VT100*colorUL: magenta XTerm*VT100*color2: black XTerm*VT100*color3: magenta XTerm.VT100.eightBitInput: true XTerm.VT100.eightBitOutput: true XTerm.VT100*underLine: false XTerm.VT100*cursorColor: lime green XTerm*VT100*saveLines: 400 XTerm*termName: xterm-color XTerm*loginShell: true because i was not able to read yellow color on my laptop. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10:27:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 31BF537B6C2 for ; Wed, 19 Jul 2000 10:27:42 -0700 (PDT) (envelope-from rivas45@sprintmail.com) Received: from sprintmail.com (sdn-ar-003njnbruP263.dialsprint.net [168.191.61.153]) by snipe.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id KAA19572; Wed, 19 Jul 2000 10:27:19 -0700 (PDT) Message-ID: <3975E4E9.AD7BAA66@sprintmail.com> Date: Wed, 19 Jul 2000 13:27:05 -0400 From: Eric Rivas X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.5-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dave Glowacki Cc: "Steve O'Hara-Smith" , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls References: <200007191608.LAA26196@hyde.ssec.wisc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Glowacki wrote: > > "Steve O'Hara-Smith" wrote: > > > > On 19-Jul-00 Ron 'The InSaNe One' Rosson wrote: > > > How does one in .Xdefaults make your xterm "look color" > > > > I have > > > > *customization: -color > > > > In my .Xdefaults which takes care of xterm and quite a lot of other > > apps as well. Is it me or does anyone else remember colorls showing color with out doing the .Xdefaults or $TERM=xterm-color thing. > > My .Xdefaults file (which has been hacked on for over 12 years, yikes!) > has: > > #ifdef COLOR > *customization: -color > #else > *customization: -mono > #endif > > In the (increasingly unlikely) event that you ever run on a > monochrome system, this will do the right thing... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Eric J. Rivas WWW: http://home.sprintmail.com/~rivas45/ ICQ: 61930546 "I can't wait till I'm out of school, so I can start learning things!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10:30:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cmailg6.svr.pol.co.uk (cmailg6.svr.pol.co.uk [195.92.195.176]) by hub.freebsd.org (Postfix) with ESMTP id 65D2037BF94 for ; Wed, 19 Jul 2000 10:30:25 -0700 (PDT) (envelope-from rich@dynamite.org) Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk) by cmailg6.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13Exfr-0003LQ-00 for freebsd-stable@freebsd.org; Wed, 19 Jul 2000 18:30:23 +0100 Received: from modem-84.ereinion.dialup.pol.co.uk ([62.136.196.84] helo=bluescreen.kill-9.org.uk) by mail17.svr.pol.co.uk with smtp (Exim 3.13 #0) id 13Exfq-0004k7-00 for freebsd-stable@freebsd.org; Wed, 19 Jul 2000 18:30:23 +0100 Received: from bluescreen (unverified [192.168.1.2]) by bluescreen.kill-9.org.uk (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 19 Jul 2000 18:25:03 +0100 From: "Rich Wood" Organization: dynamite.org To: Josef Karthauser , freebsd-stable@FreeBSD.ORG Date: Wed, 19 Jul 2000 18:25:03 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Color ls Reply-To: rich@dynamite.org Message-ID: <3975F27F.6063.23D8E72B@localhost> In-reply-to: <20000719013606.O20505@pavilion.net> References: <20000718172825.B98089@wopr.caltech.edu>; from mph@astro.caltech.edu on Tue, Jul 18, 2000 at 05:28:25PM -0700 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Jul 2000, at 1:36, Josef Karthauser wrote: > I like colourized vim and mutt :) Colourised sleep is next on > my agenda. (But that's a private commit). Brian persuaded you away from color-ppp then? :-) Rich -- rich@dynamite.org rich@FreeBSD.org.uk If that's what they call normal, I'd rather be insane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10:31:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hyde.ssec.wisc.edu (hyde.ssec.wisc.edu [144.92.108.217]) by hub.freebsd.org (Postfix) with ESMTP id 5AFF337BFA4 for ; Wed, 19 Jul 2000 10:31:51 -0700 (PDT) (envelope-from dglo@hyde.ssec.wisc.edu) Received: from hyde.ssec.wisc.edu (dglo@localhost [127.0.0.1]) by hyde.ssec.wisc.edu (8.9.3/8.9.3) with ESMTP id MAA10677; Wed, 19 Jul 2000 12:31:41 -0500 (CDT) Message-Id: <200007191731.MAA10677@hyde.ssec.wisc.edu> To: Eric Rivas Cc: "Steve O'Hara-Smith" , "Ron 'The InSaNe One' Rosson" , freebsd-stable@FreeBSD.ORG Subject: Re: Color ls In-reply-to: Your message of "Wed, 19 Jul 2000 13:27:05 EDT." <3975E4E9.AD7BAA66@sprintmail.com> Date: Wed, 19 Jul 2000 12:31:41 -0500 From: Dave Glowacki Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Rivas wrote: > Is it me or does anyone else remember colorls showing color with out > doing the .Xdefaults or $TERM=xterm-color thing. It did by just blatting the xterm-specific escape codes whenever it displayed color (without checking the TERM type.) This wasn't necessarily the right thing to do if you'd logged onto your machine from your Palm :-) Now, it's using termcap to deduce whether or not the terminal supports color, so you need to use the color-enabled xterm-color definition. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 10:34:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 2F31D37BFA3 for ; Wed, 19 Jul 2000 10:34:24 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id KAA03011; Wed, 19 Jul 2000 10:34:22 -0700 Message-ID: <3975E6B7.581EC743@urx.com> Date: Wed, 19 Jul 2000 10:34:47 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: John Reynolds Cc: stable@FreeBSD.ORG, Eric Brueggmann Subject: Re: buildworld breakage as of 1:49am 7/19/2000 References: <200007190851.BAA95748@cx587235-a.chnd1.az.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was a commit to fix nametoaddr.c worldbreakage. I'm cvsup'ing right now. Kent John Reynolds wrote: > > Hello all, > > I apologize in advance if I missed a "HEADS UP" regarding instability in the > source tree within the last few hours (my -stable subscription gets sent to > another address I don't have access to here). > > I was trying to buildworld just now with CVSup'ed sources as of about 1:30am > today. I've tried CVSup'ing since then but there have been no source changes. > > The following is the tail end of the breakage: > > ===> libpcap > ... > cc -fpic -DPIC -O -pipe -I. -Dyylval=pcap_lval -DHAVE_SYS_IOCCOM_H=1 -DHAVE_SYS_SOCKIO_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_SOCKADDR_SA_LEN=1 -DLBL_ALIGN=1 -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap -I/usr/src/lib/libpcap/../../contrib/libpcap/lbl -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c -o nametoaddr.So > /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' > /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' > /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:370: conflicting types for `ether_hostton' > /usr/obj/usr/src/i386/usr/include/net/ethernet.h:111: previous declaration of `ether_hostton' > *** Error code 1 > *** Error code 1 > 2 errors > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation > jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running > jjreynold@home.com FreeBSD 3.5-STABLE. FreeBSD: The Power to Serve. > http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 11:10: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5F52837B51B; Wed, 19 Jul 2000 11:09:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA93190; Wed, 19 Jul 2000 12:09:55 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA83108; Wed, 19 Jul 2000 12:09:50 -0600 (MDT) Message-Id: <200007191809.MAA83108@harmony.village.org> To: chad@DCFinc.com Subject: Re: bioscall.s Cc: wilko@FreeBSD.ORG, rsstan@yahoo.com, obrien@FreeBSD.ORG, keith.mackay@home.com, stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 17:20:29 PDT." <200007180020.RAA17343@freeway.dcfinc.com> References: <200007180020.RAA17343@freeway.dcfinc.com> Date: Wed, 19 Jul 2000 12:09:50 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007180020.RAA17343@freeway.dcfinc.com> "Chad R. Larson" writes: : Could someone please offer a brief explanation about the nature of : the change to the binutils? How are they different such that the : kernel build method needed change? They fix a number of borken instructions that we had worked around in odd ways before. Now, the work arounds are no longer needed and have been removed. Some of the work arounds don't work or produce working binarys now (iirc). : My original understanding was that the new method used the tools in : /usr/obj instead of in /usr/bin, in order to build kernels with : freshly built tools, rather than the tools from the previous build. : Late postings imply something more complicated has happened. : Is that true? No. It is just a matter of needing up to date tools. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 11:16:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 770D237BFB2 for ; Wed, 19 Jul 2000 11:16:49 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 16753190 invoked from network); 19 Jul 2000 17:56:41 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 19 Jul 2000 17:56:41 -0000 Message-ID: <3975EC95.5E74A4C0@cybercable.fr> Date: Wed, 19 Jul 2000 19:59:49 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Montgomery-Smith , freebsd-stable@freebsd.org Subject: Re: Small handbook error References: <3975C623.1EFBFAE8@math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Its diff -c old-file new-file Regards, Maxime Henrion Stephen Montgomery-Smith wrote: > Jeff Wyman wrote: > > > > > > I'm a complete idiot who doesn't even know how to make diffs, so I thought > > I'd just let everybody know right away instead of figuring out how to > > write a diff and holding out on you all for the time that may take - I'm > > a slow learner. > > > > The hardest thing about making diffs is to remember which order to put > the files. Do you say: > > diff -c new-file old-file > > or > > diff -c old-file new-file ? > > Alas, neither the man page for diff, nor the man page for patch are > that helpful - they give hints about this, but nothing explicit. > > If someone tells me authoritively what the answer is, maybe I'll submit > a send-pr changing the man pages for diff and patch so that they are > more explicit on this issue. > > (I always figure it out by a process of trial and error.) > > -- > Stephen Montgomery-Smith > Department of Mathematics, University of Missouri, Columbia, MO 65211 > Phone 573-882-4540, fax 573-882-1869 > http://www.math.missouri.edu/~stephen stephen@math.missouri.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 11:22: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id B722F37BFEE for ; Wed, 19 Jul 2000 11:21:59 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id DCF6811CD6E; Wed, 19 Jul 2000 11:21:58 -0700 (PDT) Date: Wed, 19 Jul 2000 11:21:58 -0700 From: R Joseph Wright To: Josef Karthauser Cc: freebsd-stable@FreeBSD.org Subject: Re: Color ls Message-ID: <20000719112158.A13347@manatee.mammalia.org> References: <20000718140646.B76011@lunatic.oneinsane.net> <20000718145920.B94689@wopr.caltech.edu> <20000719005555.W4668@strontium.scientia.demon.co.uk> <20000718170420.A97601@wopr.caltech.edu> <20000718175525.A10074@manatee.mammalia.org> <20000719150836.K630@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719150836.K630@pavilion.net>; from joe@pavilion.net on Wed, Jul 19, 2000 at 03:08:36PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 03:08:36PM +0100, Josef Karthauser wrote: > On Tue, Jul 18, 2000 at 05:55:25PM -0700, R Joseph Wright wrote: > > > > The thing that really bugs me about ls is the lack of bright colors like you > > get with gnuls. The blue is so dark it blends in with the black background > > of the console. I spent several hours looking through the code to see if I > > could change that, but alas I did not understand it :-(. > > And, sorry to rant, but the default colors are horrid, too! Do 'ls -G /dev' > > to see what I mean. AAaaarh! > > > > Colours are always a personal preference. No answer is right for everyone. > Read the manual page for ls and define your own colours in your environment. > Absolutely. That's why I said (hopefully in good humor) the *default* colors are horrid. However, you can change the defaults all you want, but you still will not get bright color like you get with gnuls. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 11:57:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 8D65B37B7A4; Wed, 19 Jul 2000 11:57:05 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA03228; Wed, 19 Jul 2000 19:46:51 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA09244; Wed, 19 Jul 2000 19:21:32 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007191821.TAA09244@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Steve O'Hara-Smith" Cc: Brian Somers , freebsd-stable@FreeBSD.ORG, "Ron 'The InSaNe One' Rosson" , Kris Kennaway , Ben Smithurst , Josef Karthauser , Matthew Hunt , brian@Awfulhak.org Subject: Re: Color ls In-Reply-To: Message from "Steve O'Hara-Smith" of "Wed, 19 Jul 2000 16:03:21 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 19:21:31 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Everybody seems to have missed this but there is a mechanism to make > xterm set TERM to xterm-color which also makes most other X apps work in > colour. The trick is > > *customization: -color > > In .Xdefaults (or anything else that sets X resources). This doesn't appear to have any effect under XFree86-3.3.6. > I gather (I have not tested) that this even does the right thing if you > run an xterm on a mono X-Server. > > -- > Steve O'Hara-Smith > > http://sohara.webhop.net/ A Better Way To Focus The Sun -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 12: 9:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by hub.freebsd.org (Postfix) with ESMTP id 7C92037B8B7; Wed, 19 Jul 2000 12:09:45 -0700 (PDT) (envelope-from bmah@cisco.com) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.0.Beta3/8.11.0.Beta3) id e6JJ8YJ01331; Wed, 19 Jul 2000 12:08:34 -0700 (PDT) (envelope-from bmah) Message-Id: <200007191908.e6JJ8YJ01331@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Brian Somers Cc: "Steve O'Hara-Smith" , freebsd-stable@FreeBSD.ORG, "Ron 'The InSaNe One' Rosson" , Kris Kennaway , Ben Smithurst , Josef Karthauser , Matthew Hunt Subject: Re: Color ls In-Reply-To: <200007191821.TAA09244@hak.lan.Awfulhak.org> References: <200007191821.TAA09244@hak.lan.Awfulhak.org> Comments: In-reply-to Brian Somers message dated "Wed, 19 Jul 2000 19:21:31 +0100." From: bmah@cisco.com (Bruce A. Mah) Reply-To: bmah@cisco.com X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_970481908P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 12:08:34 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_970481908P Content-Type: text/plain; charset=us-ascii If memory serves me right, Brian Somers wrote: > > *customization: -color > > > > In .Xdefaults (or anything else that sets X resources). > > This doesn't appear to have any effect under XFree86-3.3.6. Confirmed here...I did this on XFree86-3.3.6 on a RELENG_4 machine and I still didn't get my colored bikesh^H^H^H^H^H^Hxterm. Bruce. --==_Exmh_970481908P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: pMG58E43BdRsPzse3uL6iUbTqSI+E5AP iQA/AwUBOXX8sdjKMXFboFLDEQIDYgCePolRzOml5IY3mt5duzOP9KmsQuEAoJ1e iWze91nvF0tcDIaiEyuxXFwh =Z0zA -----END PGP SIGNATURE----- --==_Exmh_970481908P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 12:40:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from KIWI-Computer.com (kiwi-computer.com [63.224.10.3]) by hub.freebsd.org (Postfix) with ESMTP id 8119E37B743; Wed, 19 Jul 2000 12:40:14 -0700 (PDT) (envelope-from freebsd@KIWI-Computer.com) Received: (from freebsd@localhost) by KIWI-Computer.com (8.9.3/8.9.3) id OAA52353; Wed, 19 Jul 2000 14:39:07 -0500 (CDT) (envelope-from freebsd) From: FreeBSD Message-Id: <200007191939.OAA52353@KIWI-Computer.com> Subject: Re: Color ls In-Reply-To: <200007191908.e6JJ8YJ01331@bmah-freebsd-0.cisco.com> from "Bruce A. Mah" at "Jul 19, 2000 12:08:34 pm" To: bmah@cisco.com Date: Wed, 19 Jul 2000 14:39:07 -0500 (CDT) Cc: Brian Somers , "Steve O'Hara-Smith" , freebsd-stable@FreeBSD.ORG, "Ron 'The InSaNe One' Rosson" , Kris Kennaway , Ben Smithurst , Josef Karthauser , Matthew Hunt X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > *customization: -color > > >=20 > > > In .Xdefaults (or anything else that sets X resources). > >=20 > > This doesn't appear to have any effect under XFree86-3.3.6. >=20 > Confirmed here...I did this on XFree86-3.3.6 on a RELENG_4 machine and=20 > I still didn't get my colored bikesh^H^H^H^H^H^Hxterm. Do you guys have the following (or equivalent) lines in ~/.xinitrc (ro ~/.xsession if you use a display manager): xrdb -merge ~/.Xdefaults ??A=7F It seems to work for me (could be other configurations I have enabled tho...) Good luck, -- Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 12:50: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front002.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 1348C37BC83 for ; Wed, 19 Jul 2000 12:50:03 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave) by front002.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 13469736; Wed, 19 Jul 2000 15:49:01 -0400 From: David Uhring To: Conrad Sabatier Subject: Re: is the ensoniq 1371 sound chip supported? Date: Wed, 19 Jul 2000 14:50:01 -0500 X-Mailer: KMail [version 1.1.50] Content-Type: text/plain Cc: freebsd-stable@FreeBSD.ORG, sean@rentul.net References: In-Reply-To: MIME-Version: 1.0 Message-Id: <00071914500101.02917@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Conrad Sabatier wrote: > On 18-Jul-00 David Uhring wrote: > > I can't get mine to work, either. The kernel is compiled with device > > pcm and > > dmesg shows that the kernel recognizes the card. What /dev/ > > have to be made? There is no pcm0 in /dev and MAKEDEV reports no such > > device, although > > pcm0 appears in dmesg. Running RELENG_4 compiled 12 Jul 00. > > In your kernel config file: > > device pcm > device sbc > > (the es1371 *is* a Soundblaster-compatible) > > In /dev, do "./MAKEDEV snd0". > > Works great for me! Kerneld was already configured correctly. I was unaware it is necessary to MAKEDEV sndX again after switching sound cards. Found the problem, thanks to the group. The es1373 works fine now. Documentation for sound is severely lacking in the man's, the Handbook & the mailing lists. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 12:56:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wysoft.tzo.com (c481444-a.bremtn1.wa.home.com [24.12.235.202]) by hub.freebsd.org (Postfix) with ESMTP id 1EF8137C199 for ; Wed, 19 Jul 2000 12:56:19 -0700 (PDT) (envelope-from wysoft@wysoft.tzo.com) Received: from localhost (wysoft@localhost) by wysoft.tzo.com (8.10.1/8.10.1) with ESMTP id e6JJpwG19682; Wed, 19 Jul 2000 12:51:59 -0700 (PDT) Date: Wed, 19 Jul 2000 12:51:58 -0700 (PDT) From: Jeff Wyman To: Maxime Henrion Cc: Stephen Montgomery-Smith , freebsd-stable@FreeBSD.ORG Subject: Re: Small handbook error In-Reply-To: <3975EC95.5E74A4C0@cybercable.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No no no.. I don't know how to write diffs :) On Wed, 19 Jul 2000, Maxime Henrion wrote: > Its diff -c old-file new-file > > Regards, > > Maxime Henrion > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13: 5:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 7CD7837C012 for ; Wed, 19 Jul 2000 13:05:43 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 6255 invoked from network); 19 Jul 2000 20:05:42 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 19 Jul 2000 20:05:42 -0000 Message-ID: <39760AD1.F6FD7B8F@cybercable.fr> Date: Wed, 19 Jul 2000 22:08:49 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Wyman , freebsd-stable@freebsd.org Subject: Re: Small handbook error References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was replying to Stephen Montgomery-Smith :) Jeff Wyman wrote: > No no no.. I don't know how to write diffs :) > > On Wed, 19 Jul 2000, Maxime Henrion wrote: > > > Its diff -c old-file new-file > > > > Regards, > > > > Maxime Henrion > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:11:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsa-1-as01-7-a20.gd.uol.com.br (bsa-1-as01-7-a20.gd.uol.com.br [200.197.118.20]) by hub.freebsd.org (Postfix) with ESMTP id 2948537C031 for ; Wed, 19 Jul 2000 13:10:44 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 500 invoked by uid 1001); 19 Jul 2000 20:04:58 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Wed, 19 Jul 2000 17:04:35 -0300 To: freebsd-stable@freebsd.org Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Message-ID: <20000719170435.A210@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Before blaming freebsd, either sigbus errors or signal 11 should be checked for either bad hardware or memory. You could check some free memory checking software. For DOS, you can get GoldMemory and DocMemory. Both can be found at http://www.download.com/ For FreeBSD, you can cvsup the latest ports tree and try sysutils/memtest. This nifty utility has been mentioned on this thread and it is quite nice. I just added the port yesterday. ps: I am not endorsing any of the aforementioned software. I am just mentioning their claim to work as memory tester's. Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:11:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsa-1-as01-7-a20.gd.uol.com.br (bsa-1-as01-7-a20.gd.uol.com.br [200.197.118.20]) by hub.freebsd.org (Postfix) with ESMTP id 40C8F37C03C for ; Wed, 19 Jul 2000 13:11:26 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 735 invoked by uid 1001); 19 Jul 2000 20:11:12 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Wed, 19 Jul 2000 17:10:50 -0300 To: simond@irrelevant.org Cc: Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG Subject: Re: shutdown -p == shutdown -h ? Message-ID: <20000719171050.B561@Fedaykin.here> References: <20000719093254.A763@Fedaykin.here> <20000719133855.E91771@irrelevant.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719133855.E91771@irrelevant.org>; from simond@irrelevant.org on Wed, Jul 19, 2000 at 01:38:33PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 01:38:33PM +0100, simond@irrelevant.org wrote: > On Wed, Jul 19, 2000 at 09:32:54AM -0300, Mario Sergio Fujikawa Ferreira wrote: > > Hi, > > > > I was wondering why is shutdown -p behaving exactly > > like shutdown -r? > > I have both apm and apmd running. > > Is it due to the non-MFCed acpi code? > > I get the same effect, but with the additional "feature" that once I > turn my PC off when I let go of the power button it turns itself on > again, -p used to work fine, no idea what happened. Yeah, same feeling. It is not working. > If it helps I'm using a k6-2/450 on a FIC-2013 MVP3 motherboard I am using a k6-3/400 on a FIC-VA503+ MVP3 motherboard with the latest availtable bios JE439: APM 1.2 and ACPI 1.0. Pretty annoying. Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:16: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A05CA37C033 for ; Wed, 19 Jul 2000 13:15:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA93908; Wed, 19 Jul 2000 14:15:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA84274; Wed, 19 Jul 2000 14:15:51 -0600 (MDT) Message-Id: <200007192015.OAA84274@harmony.village.org> To: Gerhard Sittig Subject: Re: bioscall.s Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jul 2000 07:02:31 +0200." <20000719070231.K24476@speedy.gsinet> References: <20000719070231.K24476@speedy.gsinet> <20000718015340.3073.qmail@web3102.mail.yahoo.com> <3973BA04.5AB2FFD@urx.com> <20000718194202.F24476@speedy.gsinet> Date: Wed, 19 Jul 2000 14:15:51 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000719070231.K24476@speedy.gsinet> Gerhard Sittig writes: : To clear this up a little more ... : : On Tue, Jul 18, 2000 at 19:42 +0200, Gerhard Sittig wrote: : > On Mon, Jul 17, 2000 at 18:59 -0700, Kent Stewart wrote: : > > : > > Richard Stanaford wrote: : > > > : > > > make buildkernel KERNEL="NOVA" : > > : > > The quotes are evil. [ ... ] : ^^^^^^^^^^^^^^^^^^^ : > : > This is somewhat hard to believe. [ ... ] : : Everything else was since I read the message as "with quotes it : won't compile, without it does". But I understand this was not : the problem and we're done discussing this. :) Quotes work just fine. The shell strips them off before make sees them. Make will see 'KERNEL=NOVA' for any of the following args: KERNEL="NOVA" KERNEL='NOVA' "KERNEL="NOVA "KERNEL=NOVA" Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:16:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsa-1-as01-7-a20.gd.uol.com.br (bsa-1-as01-7-a20.gd.uol.com.br [200.197.118.20]) by hub.freebsd.org (Postfix) with ESMTP id 041AE37B6B1 for ; Wed, 19 Jul 2000 13:16:05 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 844 invoked by uid 1001); 19 Jul 2000 20:16:22 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Wed, 19 Jul 2000 17:16:00 -0300 To: Fred Clift Cc: simond@irrelevant.org, Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG Subject: Re: shutdown -p == shutdown -h ? Message-ID: <20000719171600.D561@Fedaykin.here> References: <20000719133855.E91771@irrelevant.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from fred@veriohosting.com on Wed, Jul 19, 2000 at 09:45:43AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 09:45:43AM -0600, Fred Clift wrote: > > I noticed that -p and -h work the same (ie dont powerdown) when apmd isn't > running on my toshiba 300CT laptop. If, however, I have apmd running > correctly, then shutdown -p powers the box down and shutdown -h brings it > to the point where it sasy 'it's ok to shut down your box now...' I am annoyed here that -h is just not working as supposed. I am happy that it is working for someone. :) It means I might get it working here. What really annoys me is the fact that Windows gets it right. zzz is clearly working. However, that might not be a good check. I am using plain /etc/apmd.conf from stable sources as of yesterday MD5 (apmd.conf) = becbdd3779fe95e431beca206fc5d485 Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:17:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A129237C066 for ; Wed, 19 Jul 2000 13:17:31 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA93917; Wed, 19 Jul 2000 14:17:24 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA84294; Wed, 19 Jul 2000 14:17:23 -0600 (MDT) Message-Id: <200007192017.OAA84294@harmony.village.org> To: Fred Clift Subject: Re: shutdown -p == shutdown -h ? Cc: simond@irrelevant.org, Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jul 2000 09:46:05 MDT." References: Date: Wed, 19 Jul 2000 14:17:23 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Fred Clift writes: : I noticed that -p and -h work the same (ie dont powerdown) when apmd isn't : running on my toshiba 300CT laptop. If, however, I have apmd running : correctly, then shutdown -p powers the box down and shutdown -h brings it : to the point where it sasy 'it's ok to shut down your box now...' On my Sony VAOI running current shutdown -p (or halt -p) do exactly the same thing: They turn the machine off. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:18: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id 3A9A037C0FC for ; Wed, 19 Jul 2000 13:17:54 -0700 (PDT) (envelope-from noor@comrax.com) Received: from localhost (noor@localhost) by dns.comrax.com (8.9.3/8.9.3) with ESMTP id XAA78682 for ; Wed, 19 Jul 2000 23:17:49 +0300 (IDT) (envelope-from noor@comrax.com) X-Authentication-Warning: dns.comrax.com: noor owned process doing -bs Date: Wed, 19 Jul 2000 23:17:49 +0300 (IDT) From: To: freebsd-stable@FreeBSD.ORG Subject: MySQL on FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I've upgraded our FreeBSD box this morning to 4.1-RC. The machine runs httpd and mysqld mainly. PHP runs as a module on httpd. Anyways, mysqld is acting strangely on our FreeBSD box (P-II 350Mhz, 256MB, SCSI-II card & disk). Usually the machine is 90-95% idling, and from time to time, mysqld uses 20% from the CPU, but after that it rests back to 0-1%. The problem is that when mysqld reaches approximately 25-30% of CPU usage, it dies with a 'Segmentation fault' or 'Bus error' error message, and starts again from a shell script. Now, I've seen mysqld (same configuration) run on Solaris systems with CPU loads up to 50-60%, without dying once! Although it keeps the disk spinning, but it doesn't ever die. The configuration of FreeBSD is "as is", no optimizations were applied, and no kernel parameter was altered. mysqld's parameteres are "factory" defaults. If anyone knows how to make mysqld NOT die on such low CPU loads, and know how to fix this (either by altering FreeBSD's parameteres, or mysqld's), then please elaborate. I've tried playing with both parameters, but it's not helping... mysqld keeps dying sooner or later, and even sometimes it returns empty results. Thanks for your help. Noor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:32:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell.wetworks.org (shell.wetworks.org [63.160.175.19]) by hub.freebsd.org (Postfix) with SMTP id EC5AE37B8DF for ; Wed, 19 Jul 2000 13:32:25 -0700 (PDT) (envelope-from abc@shell.wetworks.org) Received: (qmail 91466 invoked by uid 1000); 19 Jul 2000 20:32:26 -0000 Date: Wed, 19 Jul 2000 16:32:26 -0400 From: Alan Clegg To: freebsd-stable@FreeBSD.ORG Subject: Re: shutdown -p == shutdown -h ? Message-ID: <20000719163226.A91367@shell.wetworks.org> References: <200007192017.OAA84294@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007192017.OAA84294@harmony.village.org>; from imp@village.org on Wed, Jul 19, 2000 at 02:17:23PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An SMTP stream claimed that Warner Losh muttered: > On my Sony VAOI running current shutdown -p (or halt -p) do exactly > the same thing: They turn the machine off. As does my Winbook. Now, I don't have a stable clock (off 6 seconds per minute), but I can power-off (and sleep). AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:34:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 6F78437C018 for ; Wed, 19 Jul 2000 13:34:15 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id PAA03261; Wed, 19 Jul 2000 15:35:03 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <000e01bff1c0$c2abb130$b8209fc0@campbellmithun.com> From: "Shawn Barnhart" To: "Mario Sergio Fujikawa Ferreira" , References: <20000719170435.A210@Fedaykin.here> Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Wed, 19 Jul 2000 15:34:38 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Mario Sergio Fujikawa Ferreira" To: | Before blaming freebsd, either sigbus errors or | signal 11 should be checked for either bad hardware or memory. I don't know why people assume I'm blaming FreeBSD. I had someone else telling me not to blame FreeBSD, too, and believe me I don't. Even though I've only been using FreeBSD for a few months (after years of Linux abuse), I have YET to have a world break (on any of the three machines I'm currently running it on)other than on this glitch or when the comitters declare open season on -STABLE. I was ALREADY assuming broken hardware, and was surprised that the pounding the machine got under Windows didn't reveal any problems. From my original message: --- Since I haven't seen a anyone else's world breaking this way, I'm assuming that this is a hardware problem -- but what kind? Memory? I have a spare Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start? --- The postscript to this story is I ran memtest86 (after getting the suggestion from here) overnight and it reported errors in my RAM. Replaced with a fresh stick of RAM and all is well. (As an aside, I was checking for info on my board, an Asus TXP4, on USENET and supposedly it will do an unadvertised 75 and 83Mhz FSB. Anyone know how overclockable K6-233 CPUs are?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:36: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 97A5537C05B for ; Wed, 19 Jul 2000 13:35:59 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6JKZrr09628; Wed, 19 Jul 2000 13:35:53 -0700 (PDT) Date: Wed, 19 Jul 2000 13:35:53 -0700 From: Alfred Perlstein To: noor@comrax.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MySQL on FreeBSD Message-ID: <20000719133552.X13979@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from noor@comrax.com on Wed, Jul 19, 2000 at 11:17:49PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * noor@comrax.com [000719 13:27] wrote: > Hello all, > > I've upgraded our FreeBSD box this morning to 4.1-RC. The machine runs > httpd and mysqld mainly. PHP runs as a module on httpd. > > Anyways, mysqld is acting strangely on our FreeBSD box (P-II 350Mhz, > 256MB, SCSI-II card & disk). Usually the machine is 90-95% idling, and > from time to time, mysqld uses 20% from the CPU, but after that it rests > back to 0-1%. The problem is that when mysqld reaches approximately 25-30% > of CPU usage, it dies with a 'Segmentation fault' or 'Bus error' error > message, and starts again from a shell script. I would be most helpful if you could post a stack trace. find the mysqld.core file and do this: gdb /path/to/mysqld /path/to/mysqld.core then type "bt" show us the results, it would be even more helpful if you could compile libc_r and mysqld with debugging symbols and give us a traceback from that. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:43:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [206.79.44.166]) by hub.freebsd.org (Postfix) with ESMTP id 3BDC337C0DB; Wed, 19 Jul 2000 13:43:08 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id RAA21031; Wed, 19 Jul 2000 17:41:59 GMT (envelope-from nik) Date: Wed, 19 Jul 2000 17:41:59 +0000 From: Nik Clayton To: Michael Lucas Cc: advocacy@freebsd.org, stable@freebsd.org Subject: Re: Southeast Michigan Users' Group followup Message-ID: <20000719174158.A20996@kilt.nothing-going-on.org> References: <200007181209.IAA09569@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007181209.IAA09569@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Jul 18, 2000 at 08:09:38AM -0400 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael, On Tue, Jul 18, 2000 at 08:09:38AM -0400, Michael Lucas wrote: > I offered a couple weeks ago to organize a Southeast Michigan users' > group, and asked people to mail me if they were interested. > > To date, I've gotten two responses. Counting me, that makes three. Based on personal experience, just go ahead and do it. I tried your approach when I tried setting up a UK FreeBSD user group. Response from the mailing lists was apathetic. Then Lee Johnston did exactly the right thing, and set up some mailing lists and a website and announced that the UK UG existed. Suddenly people came crawling out of the woodwork to subscribe :-) N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:44:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id D3DB837C091 for ; Wed, 19 Jul 2000 13:44:16 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id NAA03625; Wed, 19 Jul 2000 13:43:48 -0700 Message-ID: <3976131B.67E97D9E@urx.com> Date: Wed, 19 Jul 2000 13:44:11 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Shawn Barnhart Cc: Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? References: <20000719170435.A210@Fedaykin.here> <000e01bff1c0$c2abb130$b8209fc0@campbellmithun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shawn Barnhart wrote: > > ----- Original Message ----- > From: "Mario Sergio Fujikawa Ferreira" > To: > > | Before blaming freebsd, either sigbus errors or > | signal 11 should be checked for either bad hardware or memory. > > I don't know why people assume I'm blaming FreeBSD. I had someone else > telling me not to blame FreeBSD, too, and believe me I don't. Even though > I've only been using FreeBSD for a few months (after years of Linux abuse), > I have YET to have a world break (on any of the three machines I'm currently > running it on)other than on this glitch or when the comitters declare open > season on -STABLE. I was ALREADY assuming broken hardware, and was surprised > that the pounding the machine got under Windows didn't reveal any problems. > > >From my original message: > > --- > > Since I haven't seen a anyone else's world breaking this way, I'm assuming > that this is a hardware problem -- but what kind? Memory? I have a spare > Pentium 166 CPU and extra SDRAM I can swap, any clues as to where to start? I overclocked a Celeron 300a and it wouldn't signal 11 but hang in the middle of building XFree86 3.3.4. I pulled the heat sink off and it had melted the thermal tape. Make sure you don't have overheating but replacing a stick (or pair) of memory may be your first choice. I was using 64MB SDRAM and had several spares. That didn't change anything and that is when the heatsink came off. The Celeron 300a died completely shortly after that. Good cooling was too late. Kent > > --- > > The postscript to this story is I ran memtest86 (after getting the > suggestion from here) overnight and it reported errors in my RAM. Replaced > with a fresh stick of RAM and all is well. > > (As an aside, I was checking for info on my board, an Asus TXP4, on USENET > and supposedly it will do an unadvertised 75 and 83Mhz FSB. Anyone know how > overclockable K6-233 CPUs are?) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 13:55: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by hub.freebsd.org (Postfix) with ESMTP id 5A88637C065; Wed, 19 Jul 2000 13:54:51 -0700 (PDT) (envelope-from bmah@cisco.com) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.0.Beta3/8.11.0.Beta3) id e6JKreV03123; Wed, 19 Jul 2000 13:53:40 -0700 (PDT) (envelope-from bmah) Message-Id: <200007192053.e6JKreV03123@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: FreeBSD Cc: bmah@cisco.com, Brian Somers , "Steve O'Hara-Smith" , freebsd-stable@FreeBSD.ORG, "Ron 'The InSaNe One' Rosson" , Kris Kennaway , Ben Smithurst , Josef Karthauser , Matthew Hunt Subject: Re: Color ls In-Reply-To: <200007191939.OAA52353@KIWI-Computer.com> References: <200007191939.OAA52353@KIWI-Computer.com> Comments: In-reply-to FreeBSD message dated "Wed, 19 Jul 2000 14:39:07 -0500." From: bmah@cisco.com (Bruce A. Mah) Reply-To: bmah@cisco.com X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_977735408P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 19 Jul 2000 13:53:40 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_977735408P Content-Type: text/plain; charset=us-ascii If memory serves me right, FreeBSD wrote: > > > > *customization: -color > > > > > > > > In .Xdefaults (or anything else that sets X resources). > > > > > > This doesn't appear to have any effect under XFree86-3.3.6. > > > > Confirmed here...I did this on XFree86-3.3.6 on a RELENG_4 machine and > > I still didn't get my colored bikesh^H^H^H^H^H^Hxterm. > > Do you guys have the following (or equivalent) lines in ~/.xinitrc (ro > ~/.xsession if you use a display manager): > > xrdb -merge ~/.Xdefaults Yes I do, but that's not the problem: bmah-freebsd-0:bmah% xrdb -query | grep customization *customization: -color bmah-freebsd-0:bmah% which xterm /usr/X11R6/bin/xterm bmah-freebsd-0:bmah% xterm & [switch windows] bmah-freebsd-0:bmah% echo $TERM xterm bmah-freebsd-0:bmah% uname -a FreeBSD bmah-freebsd-0.cisco.com 4.1-RC FreeBSD 4.1-RC #0: Mon Jul 17 12:09:54 PDT 2000 root@bmah-freebsd-0.cisco.com:/usr/src/sys/compile/NIMITZ i386 bmah-freebsd-0:bmah% xdpyinfo | grep vendor vendor string: The XFree86 Project, Inc vendor release number: 3360 I'm not a big fan of multi-colored xterms, but it'd be nice to document how this works, for people who are. Bruce. --==_Exmh_977735408P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: hUQaD2H4m0EwPwp0s52t2ubGgwBcMqr7 iQA/AwUBOXYVVNjKMXFboFLDEQI9KgCfUhcuKEsZn7pL941PKiW2fOETED4AoOKC nlmhxsL83+2O3vgC4K6RGJez =Ix3s -----END PGP SIGNATURE----- --==_Exmh_977735408P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 14:18: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from raditex.se (gandalf.raditex.se [192.5.36.18]) by hub.freebsd.org (Postfix) with ESMTP id E254837B514 for ; Wed, 19 Jul 2000 14:18:00 -0700 (PDT) (envelope-from kaj@raditex.se) Received: (from kaj@localhost) by raditex.se (8.9.3/8.9.3) id XAA61205; Wed, 19 Jul 2000 23:17:44 +0200 (CEST) (envelope-from kaj@raditex.se) X-Authentication-Warning: frodo.sickla.raditex.se: kaj set sender to kaj@raditex.se using -f To: Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MySQL on FreeBSD References: From: Rasmus Kaj Cc: Rasmus Kaj Organization: Raditex AB - http://Raditex.se/ X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Date: 19 Jul 2000 23:17:44 +0200 In-Reply-To: 's message of "Wed, 19 Jul 2000 23:17:49 +0300 (IDT)" Message-ID: <84u2dlsttz.fsf@frodo.sickla.raditex.se> Lines: 25 User-Agent: Gnus/5.0806 (Gnus v5.8.6) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "n" == noor writes: n> Hello all, n> I've upgraded our FreeBSD box this morning to 4.1-RC. The machine runs n> httpd and mysqld mainly. PHP runs as a module on httpd. n> Anyways, mysqld is acting strangely on our FreeBSD box (P-II n> 350Mhz, 256MB, SCSI-II card & disk). Usually the machine is 90-95% n> idling, [ ... ] The problem is that when mysqld reaches n> approximately 25-30% of CPU usage, it dies with a 'Segmentation n> fault' or 'Bus error' error message, and starts again from a shell n> script. So, you're seeing random crashes when you load the machine. Does other heavy loading (povray, make buildworld, setiathome, etc) work flawlessly? Otherwise, I'd say this is probably hardware error (maybe bad memory or broken fan). See "My programs occasionally die with ``Signal 11'' errors." in chapter 3, Troubleshooting, of the FAQ. -- Rasmus Kaj -------------------- rasmus@kaj.se - http://Raditex.se/~kaj/ \ Deja Moo: The feeling that you've heard this bullshit before \------------------------------------------------- http://Raditex.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 14:27:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 923F837C036; Wed, 19 Jul 2000 14:27:00 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA03881; Wed, 19 Jul 2000 22:22:41 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA52194; Wed, 19 Jul 2000 22:22:39 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007192122.WAA52194@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: bmah@cisco.com Cc: FreeBSD , Brian Somers , "Steve O'Hara-Smith" , freebsd-stable@FreeBSD.org, "Ron 'The InSaNe One' Rosson" , Kris Kennaway , Ben Smithurst , Josef Karthauser , Matthew Hunt , brian@Awfulhak.org Subject: Re: Color ls In-Reply-To: Message from bmah@cisco.com (Bruce A. Mah) of "Wed, 19 Jul 2000 13:53:40 PDT." <200007192053.e6JKreV03123@bmah-freebsd-0.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 22:22:39 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ditto here on FreeBSD-current. > If memory serves me right, FreeBSD wrote: > > > > > *customization: -color > > > > > > > > > > In .Xdefaults (or anything else that sets X resources). > > > > > > > > This doesn't appear to have any effect under XFree86-3.3.6. > > > > > > Confirmed here...I did this on XFree86-3.3.6 on a RELENG_4 machine and > > > I still didn't get my colored bikesh^H^H^H^H^H^Hxterm. > > > > Do you guys have the following (or equivalent) lines in ~/.xinitrc (ro > > ~/.xsession if you use a display manager): > > > > xrdb -merge ~/.Xdefaults > > Yes I do, but that's not the problem: > > bmah-freebsd-0:bmah% xrdb -query | grep customization > *customization: -color > bmah-freebsd-0:bmah% which xterm > /usr/X11R6/bin/xterm > bmah-freebsd-0:bmah% xterm & > > [switch windows] > > bmah-freebsd-0:bmah% echo $TERM > xterm > bmah-freebsd-0:bmah% uname -a > FreeBSD bmah-freebsd-0.cisco.com 4.1-RC FreeBSD 4.1-RC #0: Mon Jul 17 12:09:54 PDT 2000 root@bmah-freebsd-0.cisco.com:/usr/src/sys/compile/NIMITZ i386 > bmah-freebsd-0:bmah% xdpyinfo | grep vendor > vendor string: The XFree86 Project, Inc > vendor release number: 3360 > > I'm not a big fan of multi-colored xterms, but it'd be nice to document > how this works, for people who are. > > Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 14:44:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5347337C022 for ; Wed, 19 Jul 2000 14:44:08 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13F0tz-000GlQ-00; Wed, 19 Jul 2000 21:57:11 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13F0tz-000Fbn-00; Wed, 19 Jul 2000 21:57:11 +0100 Date: Wed, 19 Jul 2000 21:57:11 +0100 From: Ben Smithurst To: Jeff Wyman Cc: stable@freebsd.org Subject: Re: Small handbook error Message-ID: <20000719215711.C75784@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="t0UkRYy7tHLRMCai" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --t0UkRYy7tHLRMCai Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jeff Wyman wrote: > I'm a complete idiot who doesn't even know how to make diffs, so I > thought I'd just let everybody know right away instead of figuring out > how to write a diff and holding out on you all for the time that may > take - I'm a slow learner. $ cp foo foo.orig $ your-favourite-editor foo $ diff -u foo.orig foo > foo.diff and that's about it. :-) Note that if you're sending a diff for documentation, diffs to the SGML source are best because that's the format the documentation is maintained in. (Well, the stuff under doc/ anyway, manpages are different of course.) But if you don't have the SGML source installed, a diff to the HTML would probably almost be sufficient to get the problem fixed. --=20 Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / --t0UkRYy7tHLRMCai Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: X7COSSND7TgfVVp6WtVViRyXKaly0bbZ iQCVAwUBOXYWJisPVtiZOS99AQGJ9AP/dmyvNO84Yz81fp/euhBk6AUMadRzSVSl FxK6xAZM+5kiS4q0/gizp7sumtgrxIrdfa5BS8cVK2oaInidFKA5L8H7u51RY3sd 4fWp01Sg2QH/TiH9iJnwhoJBqbHhKhqbB1bUiIiW22lUI7R68JtR6g3H/8vMjmsa usobZCZj9Ik= =uuPg -----END PGP SIGNATURE----- --t0UkRYy7tHLRMCai-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 14:44:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 303C637C0BC for ; Wed, 19 Jul 2000 14:44:13 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13F0lq-000GlD-00; Wed, 19 Jul 2000 21:48:46 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13F0lp-000DTt-00; Wed, 19 Jul 2000 21:48:45 +0100 Date: Wed, 19 Jul 2000 21:48:45 +0100 From: Ben Smithurst To: Stephen Montgomery-Smith Cc: stable@FreeBSD.ORG Subject: Re: Small handbook error Message-ID: <20000719214845.B75784@strontium.scientia.demon.co.uk> References: <3975C623.1EFBFAE8@math.missouri.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="V0207lvV8h4k8FAm" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3975C623.1EFBFAE8@math.missouri.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --V0207lvV8h4k8FAm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Stephen Montgomery-Smith wrote: > diff -c new-file old-file >=20 > or >=20 > diff -c old-file new-file ? SYNOPSIS diff [options] from-file to-file That will create a diff which takes you from "from-file" to "to-file", so "from-file" is the original, "to-file" is your edited copy. i.e. $ cp foo.c foo.c.orig $ vi foo.c $ diff -u foo.c.orig foo.c --=20 Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / --V0207lvV8h4k8FAm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: sV15DiPwluW8t7qRD8sT22zHYi+itnP5 iQCVAwUBOXYULCsPVtiZOS99AQHFKgP/RuMuxTVYU37U/pONsmxzcjjxuDczj/BZ TJYIR0gPCYuP7Y9fikIr4fOx6zdqP2vkcxj9l5ztQzZG628XMvvj08TICALVF7mU 3juhhAnXCZc/xI81Ap9Ou/4VVFxB2j41x+f+etZw/w7P0FAdIVczPvW+zCXJqTt/ /4C0OjRUDZY= =I9Xq -----END PGP SIGNATURE----- --V0207lvV8h4k8FAm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 14:45:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id 0EA7737C06C for ; Wed, 19 Jul 2000 14:45:22 -0700 (PDT) (envelope-from noor@comrax.com) Received: from localhost (noor@localhost) by dns.comrax.com (8.9.3/8.9.3) with ESMTP id AAA88834; Thu, 20 Jul 2000 00:44:43 +0300 (IDT) (envelope-from noor@comrax.com) X-Authentication-Warning: dns.comrax.com: noor owned process doing -bs Date: Thu, 20 Jul 2000 00:44:43 +0300 (IDT) From: To: Rasmus Kaj Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MySQL on FreeBSD In-Reply-To: <84u2dlsttz.fsf@frodo.sickla.raditex.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This only happens with MySQL; I have no problems with other daemons, and no problems with make buildworld, and make installworld. Hardware is the last cause I'd think of. Noor On 19 Jul 2000, Rasmus Kaj wrote: > >>>>> "n" == noor writes: > > n> Hello all, > n> I've upgraded our FreeBSD box this morning to 4.1-RC. The machine runs > n> httpd and mysqld mainly. PHP runs as a module on httpd. > > n> Anyways, mysqld is acting strangely on our FreeBSD box (P-II > n> 350Mhz, 256MB, SCSI-II card & disk). Usually the machine is 90-95% > n> idling, [ ... ] The problem is that when mysqld reaches > n> approximately 25-30% of CPU usage, it dies with a 'Segmentation > n> fault' or 'Bus error' error message, and starts again from a shell > n> script. > > So, you're seeing random crashes when you load the machine. Does other > heavy loading (povray, make buildworld, setiathome, etc) work > flawlessly? > > Otherwise, I'd say this is probably hardware error (maybe bad memory > or broken fan). See "My programs occasionally die with ``Signal 11'' > errors." in chapter 3, Troubleshooting, of the FAQ. > > -- > Rasmus Kaj -------------------- rasmus@kaj.se - http://Raditex.se/~kaj/ > \ Deja Moo: The feeling that you've heard this bullshit before > \------------------------------------------------- http://Raditex.se/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 15:49:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mike.dhis.org (hiper1-d75.stk.cwnet.com [209.142.56.75]) by hub.freebsd.org (Postfix) with ESMTP id B8C0237B775 for ; Wed, 19 Jul 2000 15:49:13 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (ogre.lan [192.168.100.1]) by mike.dhis.org (Postfix) with ESMTP id 99B4ED5; Wed, 19 Jul 2000 15:48:11 -0700 (PDT) Message-ID: <3976302B.D46605AD@es.co.nz> Date: Wed, 19 Jul 2000 15:48:11 -0700 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: kstewart@urx.com Cc: R Joseph Wright , Chris , freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? References: <20000717223751.3846.qmail@web3105.mail.yahoo.com> <20000717192441.A44452@kingsqueak.org> <20000717173708.A13211@manatee.mammalia.org> <3973B316.C4442AAF@urx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: > > > > www.pcpowercooling.com sells heavy duty heatsink/fans for many processors > > including the K6/2. If my problems ever return I plan to buy one from them. > > Another place is http://www.3dfxcool.com/. He has some fans that look > like they would lift the case off if you weren't using the cpu as a > thrust reverser. I'd have to recommend 2cooltek (www.2cooltek.com) Great prices, excellent packaging and FAST door to door delivery. Not to mention the reviews and benchmarks the guy does personally on his stock. -mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16: 3:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id E64FB37B538 for ; Wed, 19 Jul 2000 16:03:31 -0700 (PDT) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id BAA06336; Thu, 20 Jul 2000 01:03:30 +0200 (MET DST) Received: by adv.iae.nl (Postfix, from userid 100) id 077F122E3; Thu, 20 Jul 2000 01:03:20 +0200 (CEST) Date: Thu, 20 Jul 2000 01:03:20 +0200 To: Kent Stewart Cc: stable@freebsd.org Subject: ipfilter broken in stable Message-ID: <20000720010320.A7162@adv.iae.nl> References: <200007191438.HAA34890@freefall.freebsd.org> <20000719201244.EABEC22E3@adv.iae.nl> <39760CD6.FEC30572@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39760CD6.FEC30572@urx.com>; from kstewart@urx.com on Wed, Jul 19, 2000 at 01:17:26PM -0700 From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: >Arjan de Vet wrote: >> >> In article <3975F60D.3B7FDAE8@urx.com> you write: >> >> >Ip_state.c and ip_nat.c are killing a 4.1-rc buildworld the error >> >message is >> >> [...] >> >> Although Darren tried to merge 3.4.8 into stable there are still a lot >> of differences between current and stable w.r.t. ipfilter. [...] >Good luck on the conflicts. So far, I haven't seen anyone else >complain. That's because it's not in the default GENERIC kernel I guess. On the ipfilter mailing list I've seen one complaint so far. I've sent Darren a mail asking him to fix ipfilter in stable before the code freeze (19 hours from now). Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16: 9:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 5077337B538 for ; Wed, 19 Jul 2000 16:09:39 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.88.246]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000719230936.ZNMC26680.mta01-svc.ntlworld.com@parish.my.domain> for ; Thu, 20 Jul 2000 00:09:36 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id AAA02640 for stable@freebsd.org; Thu, 20 Jul 2000 00:09:15 +0100 (BST) (envelope-from mark) Date: Thu, 20 Jul 2000 00:09:15 +0100 From: Mark Ovens To: stable@freebsd.org Subject: Question about -DNOCLEAN when building the world Message-ID: <20000720000915.B239@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What exactly is -DNOCLEAN supposed to do when building the world? I always make clean in /usr/src and completely remove /usr/obj after making the world (disk space) so there's nothing to clean but I still see lots of ``rm -rf'' scrolling by even when using -DNOCLEAN. Looking in /usr/src/Makefile.inc1 I find: .if !defined(NOCLEAN) rm -rf ${WORLDTMP} .else for dir in bin games include lib sbin; do \ rm -rf ${WORLDTMP}/usr/$$dir; \ done rm -f ${WORLDTMP}/sys # XXX - Work-around for broken cc/cc_tools/Makefile. # This is beyond dirty... rm -f ${OBJTREE}${.CURDIR}/gnu/usr.bin/cc/cc_tools/.depend .endif so it appears t still be doing a selective clean (on either non-existent dirs or ones that have been newly created). What is the reason for this? Is it just a "belt and braces" action? -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:16:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4BC6337B78C for ; Wed, 19 Jul 2000 16:16:26 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id BAA57221; Thu, 20 Jul 2000 01:16:24 +0200 (CEST) (envelope-from olli) Date: Thu, 20 Jul 2000 01:16:24 +0200 (CEST) Message-Id: <200007192316.BAA57221@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Issues with './MAKEDEV snd' X-Newsgroups: list.freebsd-stable In-Reply-To: <8l4n0b$2b5k$1@atlantis.rz.tu-clausthal.de> Organization: Administration TU Clausthal MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In list.freebsd-stable mi@aldan.algebra.com, wrote: > On 19 Jul, Oliver Fromme wrote: > = In list.freebsd-stable Joel Lindau wrote: > = > But when i try to './MAKEDEV snd' i get the following errors: > = > [...] > = > = Use ``./MAKEDEV snd1'' (because your card was probed as pcm1). > > Which means, he should not have ``device pcm0'' in the kernel -- only > ``device pcm''. Right? I believe it doesn't make a difference. (Someone correct me please if I'm wrong.) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:24:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 7B7C837B6E3 for ; Wed, 19 Jul 2000 16:24:12 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 022103F8C; Wed, 19 Jul 2000 16:24:10 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id QAA24398; Wed, 19 Jul 2000 16:24:10 -0700 (PDT) Message-ID: <3976389A.A76FD2CD@cup.hp.com> Date: Wed, 19 Jul 2000 16:24:10 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Ovens Cc: stable@FreeBSD.ORG Subject: Re: Question about -DNOCLEAN when building the world References: <20000720000915.B239@parish> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > > What exactly is -DNOCLEAN supposed to do when building the world? It prevents cleaning of objects that otherwise need to be rebuilt. > so it appears t still be doing a selective clean (on either > non-existent dirs or ones that have been newly created). > > What is the reason for this? Is it just a "belt and braces" action? We install binaries under the object tree. The directories in which we install these binaries will be cleaned because we don't have dependency information on them. We do not clean any object directories, so we only need to do the actual install and not the rebuild. HTH, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:30: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 0951437B721 for ; Wed, 19 Jul 2000 16:30:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6JNTQQ11201; Wed, 19 Jul 2000 16:29:41 -0700 (PDT) Date: Wed, 19 Jul 2000 16:29:26 -0700 (PDT) From: Doug White To: Arjan de Vet Cc: Kent Stewart , stable@FreeBSD.ORG Subject: Re: ipfilter broken in stable In-Reply-To: <20000720010320.A7162@adv.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Arjan de Vet wrote: > Kent Stewart wrote: > > >Arjan de Vet wrote: > >> > >> In article <3975F60D.3B7FDAE8@urx.com> you write: > >> > >> >Ip_state.c and ip_nat.c are killing a 4.1-rc buildworld the error > >> >message is > >> > >> [...] > >> > >> Although Darren tried to merge 3.4.8 into stable there are still a lot > >> of differences between current and stable w.r.t. ipfilter. > > [...] > > >Good luck on the conflicts. So far, I haven't seen anyone else > >complain. > > That's because it's not in the default GENERIC kernel I guess. On the > ipfilter mailing list I've seen one complaint so far. I've sent Darren a > mail asking him to fix ipfilter in stable before the code freeze (19 > hours from now). Still broken: mkdep -f .depend -a -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/obj/usr/src/usr.sbin/ipftest -I/usr/src/usr.sbin/ipftest/../../sys/netinet -I/usr/src/usr.sbin/ipftest/../../sys -I/usr/src/usr.sbin/ipftest/../../contrib/ipfilter -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipt.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/parse.c /usr/src/usr.sbin/ipftest/../../sys/netinet/fil.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipft_sn.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipft_ef.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipft_td.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipft_pc.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/opt.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipft_tx.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/misc.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_frag.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_state.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_nat.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_proxy.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_auth.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/ipft_hx.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_fil.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/natparse.c /usr/src/usr.sbin/ipftest/../../contrib/ipfilter/facpri.c /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_state.c:334: macro `GETUNIT' used with too many (2) args /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_state.c:380: macro `GETUNIT' used with too many (2) args /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_state.c:384: macro `GETUNIT' used with too many (2) args /usr/src/usr.sbin/ipftest/../../sys/netinet/ip_nat.c:1574: macro `NAT_HASH_FN' used with too many (3) args mkdep: compile failed Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:35:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id C0A8B37B747 for ; Wed, 19 Jul 2000 16:35:13 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA29659; Wed, 19 Jul 2000 16:33:39 -0700 (PDT) (envelope-from obrien) Date: Wed, 19 Jul 2000 16:33:38 -0700 From: "David O'Brien" To: Mark Ovens Cc: stable@freebsd.org Subject: Re: Question about -DNOCLEAN when building the world Message-ID: <20000719163338.A29474@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000720000915.B239@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000720000915.B239@parish>; from mark@ukug.uk.freebsd.org on Thu, Jul 20, 2000 at 12:09:15AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 12:09:15AM +0100, Mark Ovens wrote: > What exactly is -DNOCLEAN supposed to do when building the world? I > always make clean in /usr/src You would want to ``make cleandir'' to make sure you have a squeaky clean /usr/src/ -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:39:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id B953537B75D; Wed, 19 Jul 2000 16:39:31 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave.uhring.com) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 13706886; Wed, 19 Jul 2000 19:39:30 -0400 From: David Uhring To: freebsd-stable@FreeBSD.ORG, Oliver Fromme , freebsd-stable@FreeBSD.ORG Subject: Re: Issues with './MAKEDEV snd' Date: Wed, 19 Jul 2000 18:36:57 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <200007192316.BAA57221@dorifer.heim3.tu-clausthal.de> In-Reply-To: <200007192316.BAA57221@dorifer.heim3.tu-clausthal.de> MIME-Version: 1.0 Message-Id: <00071918392901.00302@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Oliver Fromme wrote: > In list.freebsd-stable mi@aldan.algebra.com, wrote: > > On 19 Jul, Oliver Fromme wrote: > > = In list.freebsd-stable Joel Lindau wrote: > > = > But when i try to './MAKEDEV snd' i get the following errors: > > = > [...] > > = > > = Use ``./MAKEDEV snd1'' (because your card was probed as pcm1). > > > > Which means, he should not have ``device pcm0'' in the kernel -- only > > ``device pcm''. Right? > > I believe it doesn't make a difference. > (Someone correct me please if I'm wrong.) > > Regards > Oliver > > -- > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > Addresses will change soon!! If in doubt: www.fromme.com > > "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" > (Terry Pratchett) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I'm afraid it really does make a difference. I was using a SB 16 and when I did a ./MAKEDEV snd0, I could not get the card to work. Taking a closer look at dmesg, the card appeared as sbc1. So, I took a flyer and did ./MAKEDEV snd1 and lo and behold, I had sound. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:49:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 94AFE37B75D for ; Wed, 19 Jul 2000 16:49:09 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id BAA57902; Thu, 20 Jul 2000 01:49:03 +0200 (CEST) (envelope-from olli) Date: Thu, 20 Jul 2000 01:49:03 +0200 (CEST) Message-Id: <200007192349.BAA57902@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Issues with './MAKEDEV snd' X-Newsgroups: list.freebsd-stable In-Reply-To: <8l5e9j$2tiu$1@atlantis.rz.tu-clausthal.de> Organization: Administration TU Clausthal MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In list.freebsd-stable David Uhring wrote: > On Wed, 19 Jul 2000, Oliver Fromme wrote: > > In list.freebsd-stable mi@aldan.algebra.com, wrote: > > > Which means, he should not have ``device pcm0'' in the kernel -- only > > > ``device pcm''. Right? > > > > I believe it doesn't make a difference. > > (Someone correct me please if I'm wrong.) > > I'm afraid it really does make a difference. I was using a SB 16 and when I > did a ./MAKEDEV snd0, I could not get the card to work. Read the question again please -- it was about whether the device entry in the _kernel_ makes any difference (``device pcm0'' vs. ``device pcm''). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:51: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 5B70E37B7AF for ; Wed, 19 Jul 2000 16:50:56 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.88.246]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000720005011.XHCK3760.mta02-svc.ntlworld.com@parish.my.domain>; Thu, 20 Jul 2000 00:50:11 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id AAA02962; Thu, 20 Jul 2000 00:50:33 +0100 (BST) (envelope-from mark) Date: Thu, 20 Jul 2000 00:50:33 +0100 From: Mark Ovens To: Marcel Moolenaar Cc: stable@FreeBSD.ORG Subject: Re: Question about -DNOCLEAN when building the world Message-ID: <20000720005032.C239@parish> References: <20000720000915.B239@parish> <3976389A.A76FD2CD@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3976389A.A76FD2CD@cup.hp.com>; from marcel@cup.hp.com on Wed, Jul 19, 2000 at 04:24:10PM -0700 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 04:24:10PM -0700, Marcel Moolenaar wrote: > Mark Ovens wrote: > > > > What exactly is -DNOCLEAN supposed to do when building the world? > > It prevents cleaning of objects that otherwise need to be rebuilt. > > > so it appears t still be doing a selective clean (on either > > non-existent dirs or ones that have been newly created). > > > > What is the reason for this? Is it just a "belt and braces" action? > > We install binaries under the object tree. The directories in which we > install these binaries will be cleaned because we don't have dependency > information on them. We do not clean any object directories, so we only > need to do the actual install and not the rebuild. > I think I understand, but if /usr/obj has to be created (because it didn't exist) does that not guarantee that it *is* clean? Or does make(1) have no way of knowing that /usr/obj has been newly created? > HTH, > > -- > Marcel Moolenaar > mail: marcel@cup.hp.com / marcel@FreeBSD.org > tel: (408) 447-4222 -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:51:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 3437937B7AF; Wed, 19 Jul 2000 16:51:12 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.88.246]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000720005027.XHDG3760.mta02-svc.ntlworld.com@parish.my.domain>; Thu, 20 Jul 2000 00:50:27 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id AAA02978; Thu, 20 Jul 2000 00:50:49 +0100 (BST) (envelope-from mark) Date: Thu, 20 Jul 2000 00:50:49 +0100 From: Mark Ovens To: "David O'Brien" Cc: stable@freebsd.org Subject: Re: Question about -DNOCLEAN when building the world Message-ID: <20000720005049.D239@parish> References: <20000720000915.B239@parish> <20000719163338.A29474@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719163338.A29474@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Jul 19, 2000 at 04:33:38PM -0700 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 04:33:38PM -0700, David O'Brien wrote: > On Thu, Jul 20, 2000 at 12:09:15AM +0100, Mark Ovens wrote: > > What exactly is -DNOCLEAN supposed to do when building the world? I > > always make clean in /usr/src > > You would want to ``make cleandir'' to make sure you have a squeaky clean > /usr/src/ > Ah, thanks for the pointer. > > -- > -- David (obrien@FreeBSD.org) -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 16:57: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 4E98037BE22 for ; Wed, 19 Jul 2000 16:57:03 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 0104E401D; Wed, 19 Jul 2000 16:56:59 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id QAA26046; Wed, 19 Jul 2000 16:56:59 -0700 (PDT) Message-ID: <3976404B.B566470F@cup.hp.com> Date: Wed, 19 Jul 2000 16:56:59 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Ovens Cc: stable@FreeBSD.ORG Subject: Re: Question about -DNOCLEAN when building the world References: <20000720000915.B239@parish> <3976389A.A76FD2CD@cup.hp.com> <20000720005032.C239@parish> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > > I think I understand, but if /usr/obj has to be created (because it > didn't exist) does that not guarantee that it *is* clean? Or does > make(1) have no way of knowing that /usr/obj has been newly created? I didn't see an advantage of adding tests to see if files/directories actual exist before removing them. We're not saving precious time by doing that. We could prevent doing a recursive 'make clean' for all the directories if the object tree is empty. The side-effect we now have is that the source tree is cleaned is the object directory does not exist... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 17: 2:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by hub.freebsd.org (Postfix) with ESMTP id CEF9037B84B for ; Wed, 19 Jul 2000 17:02:29 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.88.246]) by mta03-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000720000222.DLKW16423.mta03-svc.ntlworld.com@parish.my.domain>; Thu, 20 Jul 2000 01:02:22 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id BAA12394; Thu, 20 Jul 2000 01:02:01 +0100 (BST) (envelope-from mark) Date: Thu, 20 Jul 2000 01:02:01 +0100 From: Mark Ovens To: Marcel Moolenaar Cc: stable@FreeBSD.ORG Subject: Re: Question about -DNOCLEAN when building the world Message-ID: <20000720010201.E239@parish> References: <20000720000915.B239@parish> <3976389A.A76FD2CD@cup.hp.com> <20000720005032.C239@parish> <3976404B.B566470F@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3976404B.B566470F@cup.hp.com>; from marcel@cup.hp.com on Wed, Jul 19, 2000 at 04:56:59PM -0700 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 04:56:59PM -0700, Marcel Moolenaar wrote: > Mark Ovens wrote: > > > > I think I understand, but if /usr/obj has to be created (because it > > didn't exist) does that not guarantee that it *is* clean? Or does > > make(1) have no way of knowing that /usr/obj has been newly created? > > I didn't see an advantage of adding tests to see if files/directories > actual exist before removing them. We're not saving precious time by > doing that. > OK, it was time saving that I was thinking about. Thanks for the explanation. > We could prevent doing a recursive 'make clean' for all the directories > if the object tree is empty. The side-effect we now have is that the > source tree is cleaned is the object directory does not exist... > > -- > Marcel Moolenaar > mail: marcel@cup.hp.com / marcel@FreeBSD.org > tel: (408) 447-4222 -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 17:14:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 5EEC537B824 for ; Wed, 19 Jul 2000 17:14:18 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA30083; Wed, 19 Jul 2000 17:13:53 -0700 (PDT) (envelope-from obrien) Date: Wed, 19 Jul 2000 17:13:52 -0700 From: "David O'Brien" To: freddy@forge.aber.nu Cc: freebsd-stable@freebsd.org Subject: Re: make world failure (4.1-RC) Message-ID: <20000719171352.B29474@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000719153813.B30069@forge.aber.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719153813.B30069@forge.aber.nu>; from freddy@forge.aber.nu on Wed, Jul 19, 2000 at 03:38:13PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 03:38:13PM +0200, freddy@forge.aber.nu wrote: > I have a problem: I'm currently running 4.1-RC (Saturday) and now I wanted ..snip.. > ".depend", line 408: Need an operator > make: fatal errors encountered -- cannot continue That is a typical error message you get if you have a conflict when you update your sources via ``cvs update''. If you do use ``cvs'' to update your source, do a ``cvs diff'' to see if that is indead the case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 17:48:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7E17B37BC26; Wed, 19 Jul 2000 17:48:42 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA39255; Wed, 19 Jul 2000 17:48:42 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 19 Jul 2000 17:48:36 -0700 (PDT) From: Kris Kennaway To: Lars Eggert Cc: snap-users@kame.net, stable@freebsd.org, xbone@ISI.EDU Subject: Re: KAME/FreeBSD-stable merge In-Reply-To: <39735DC6.BE82F7CB@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Lars Eggert wrote: > is there any reason why the (misnamed, but that's another issue) XBONEHACK > option was eliminated during the recent KAME/FreeBSD-stable merge? (File > /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME, > and we'd really like to see it merged into FreeBSD. I've committed this for now, but I'd like to see you guys reach some kind of consensus with KAME about how to do what you need in a mutually-acceptable fashion. I'd like to replace this with whatever that solution is before 4.2-RELEASE. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 17:56: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2780C37B765; Wed, 19 Jul 2000 17:55:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA30602; Wed, 19 Jul 2000 17:55:58 -0700 (PDT) (envelope-from obrien) Date: Wed, 19 Jul 2000 17:55:58 -0700 From: "David O'Brien" To: alpha@freebsd.org, stable@freebsd.org Subject: 4.1-RC snapshot on ftp.freebsd.org Message-ID: <20000719175558.A30579@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have placed a 4.1-20000718-RC DEC Alpha snapshot at ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000718-RC/ Enjoy! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 18:33:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 7F47837B931 for ; Wed, 19 Jul 2000 18:33:07 -0700 (PDT) (envelope-from mike@adept.org) Received: by snafu.adept.org (Postfix, from userid 1000) id A2C869EE01; Wed, 19 Jul 2000 18:33:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 9A4029B001; Wed, 19 Jul 2000 18:33:01 -0700 (PDT) Date: Wed, 19 Jul 2000 18:33:01 -0700 (PDT) From: Mike Hoskins To: Shawn Barnhart Cc: Mario Sergio Fujikawa Ferreira , freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? In-Reply-To: <000e01bff1c0$c2abb130$b8209fc0@campbellmithun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Shawn Barnhart wrote: > (As an aside, I was checking for info on my board, an Asus TXP4, on USENET > and supposedly it will do an unadvertised 75 and 83Mhz FSB. Anyone know how > overclockable K6-233 CPUs are?) You'll get ~250Mhz if you're lucky... K6 233's weren't very 'overclockable' due to their high voltage levels. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 19:19:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 441FD37B5B9; Wed, 19 Jul 2000 19:19:25 -0700 (PDT) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.10.1/8.10.1/20000715) id e6K2JN200126; Wed, 19 Jul 2000 21:19:23 -0500 (CDT) From: Larry Rosenman Message-Id: <200007200219.e6K2JN200126@lerami.lerctr.org> Subject: Re: cvs commit: src/contrib/ipfilter ip_ftp_pxy.c parse.c In-Reply-To: <200007192334.QAA30603@freefall.freebsd.org> "from Darren Reed at Jul 19, 2000 04:34:30 pm" To: Darren Reed Date: Wed, 19 Jul 2000 21:19:23 -0500 (CDT) Cc: freebsd-stable@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL79 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears that IPF is still broken in current RELENG_4.... ===> sbin/ipf cc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/src/sbin/ipf/../../sys/netinet -I/usr/src/sbin/ipf/../../contrib/ipfilter -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/ipf/../../contrib/ipfilter/ipf.c cc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/src/sbin/ipf/../../sys/netinet -I/usr/src/sbin/ipf/../../contrib/ipfilter -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/ipf/../../contrib/ipfilter/parse.c cc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/src/sbin/ipf/../../sys/netinet -I/usr/src/sbin/ipf/../../contrib/ipfilter -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/ipf/../../contrib/ipfilter/opt.c cc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/src/sbin/ipf/../../sys/netinet -I/usr/src/sbin/ipf/../../contrib/ipfilter -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/ipf/../../contrib/ipfilter/facpri.c cc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/src/sbin/ipf/../../sys/netinet -I/usr/src/sbin/ipf/../../contrib/ipfilter -I/usr/obj/usr/src/i386/usr/include -static -o ipf ipf.o parse.o opt.o facpri.o ipf.o: In function `procfile': ipf.o(.text+0x349): undefined reference to `initparse' parse.o: In function `parse': parse.o(.text+0x3ec): undefined reference to `ratoui' parse.o(.text+0x9e7): undefined reference to `ratoi' parse.o(.text+0xa23): undefined reference to `proto' parse.o(.text+0xa7d): undefined reference to `proto' parse.o(.text+0xa92): undefined reference to `proto' parse.o(.text+0xaed): undefined reference to `proto' parse.o(.text+0xb00): undefined reference to `proto' parse.o(.text+0xb28): more undefined references to `proto' follow parse.o: In function `parse': parse.o(.text+0xced): undefined reference to `hostmask' parse.o(.text+0xdbd): undefined reference to `hostmask' parse.o(.text+0xe96): undefined reference to `tcp_flags' parse.o(.text+0x1039): undefined reference to `ratoui' parse.o(.text+0x10bd): undefined reference to `ratoui' parse.o: In function `to_interface': parse.o(.text+0x1332): undefined reference to `hostnum' parse.o: In function `addicmp': parse.o(.text+0x1a7e): undefined reference to `ratoi' parse.o(.text+0x1b82): undefined reference to `ratoi' parse.o: In function `icmpcode': parse.o(.text+0x1c47): undefined reference to `ratoi' parse.o: In function `printfr': parse.o(.text+0x214a): undefined reference to `printhostmask' parse.o(.text+0x2166): undefined reference to `printportcmp' parse.o(.text+0x21a2): undefined reference to `printhostmask' parse.o(.text+0x21be): undefined reference to `printportcmp' parse.o(.text+0x23b5): undefined reference to `flagset' parse.o(.text+0x23ba): undefined reference to `flags' parse.o(.text+0x23c0): undefined reference to `flagset' parse.o(.text+0x2485): undefined reference to `flagset' parse.o(.text+0x248a): undefined reference to `flags' parse.o(.text+0x2490): undefined reference to `flagset' *** Error code 1 Stop in /usr/src/sbin/ipf. *** Error code 1 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. lerbsd# > darrenr 2000/07/19 16:34:30 PDT > > Modified files: (Branch: RELENG_4) > contrib/ipfilter ip_ftp_pxy.c parse.c > Log: > cleanup > > Revision Changes Path > 1.1.1.5.2.3 +0 -2 src/contrib/ipfilter/ip_ftp_pxy.c > 1.1.1.10.2.3 +0 -7 src/contrib/ipfilter/parse.c > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe cvs-all" in the body of the message > > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 19:20:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 8C4EC37B983 for ; Wed, 19 Jul 2000 19:20:41 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 4641 invoked by uid 0); 20 Jul 2000 02:20:39 -0000 Received: from pc19f5a9a.dip.t-dialin.net (HELO speedy.gsinet) (193.159.90.154) by mail.gmx.net with SMTP; 20 Jul 2000 02:20:39 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA12997 for stable@FreeBSD.ORG; Wed, 19 Jul 2000 21:54:25 +0200 Date: Wed, 19 Jul 2000 21:54:25 +0200 From: Gerhard Sittig To: stable@FreeBSD.ORG Subject: Re: Small handbook error Message-ID: <20000719215425.O24476@speedy.gsinet> Mail-Followup-To: stable@FreeBSD.ORG References: <3975C623.1EFBFAE8@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3975C623.1EFBFAE8@math.missouri.edu>; from stephen@math.missouri.edu on Wed, Jul 19, 2000 at 10:15:47AM -0500 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 10:15 -0500, Stephen Montgomery-Smith wrote: > > The hardest thing about making diffs is to remember which order > to put the files. Do you say: > > diff -c new-file old-file > > or > > diff -c old-file new-file ? Try to read it like this: "show me what to do to get _from_ file1 _to_ file2" which will make you write down "diff -c old new". Unless you want to learn how to downgrade. :) So it's not just about "what's different" but more about documenting a development heading for a direction. And I feel the invocation is quite intuitive once you get the above "interpretation". virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 20:12:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zeus.larp.com (zeus.larp.com [38.209.52.245]) by hub.freebsd.org (Postfix) with ESMTP id 9166237BA77 for ; Wed, 19 Jul 2000 20:12:14 -0700 (PDT) (envelope-from asmo@zeus.larp.com) Received: from localhost (asmo@localhost) by zeus.larp.com (8.10.2/8.10.2) with ESMTP id e6K3EOk02183 for ; Wed, 19 Jul 2000 23:14:25 -0400 Date: Wed, 19 Jul 2000 23:14:24 -0400 (EDT) From: Justin To: freebsd-stable@freebsd.org Subject: Upgrading from 4.0release to 4.0stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does nayone know a current or updated DOC or LINK to this info, or is it as simple as a 3.4 release to 3.4 stable procedure? If anyone has any tips please send them my way @ asmo@bck.org I am not yet subscribed to the mailing list. Thanks for any assistance you can provide me! Justin -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 20:12:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wysoft.tzo.com (c481444-a.bremtn1.wa.home.com [24.12.235.202]) by hub.freebsd.org (Postfix) with ESMTP id D328537BA56; Wed, 19 Jul 2000 20:12:36 -0700 (PDT) (envelope-from wysoft@wysoft.tzo.com) Received: from localhost (wysoft@localhost) by wysoft.tzo.com (8.10.1/8.10.1) with ESMTP id e6K38NT20250; Wed, 19 Jul 2000 20:08:23 -0700 (PDT) Date: Wed, 19 Jul 2000 20:08:22 -0700 (PDT) From: Jeff Wyman To: Ben Smithurst Cc: stable@FreeBSD.org Subject: Re: Small handbook error In-Reply-To: <20000719215711.C75784@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for helping a kid out :) On Wed, 19 Jul 2000, Ben Smithurst wrote: > Jeff Wyman wrote: > > > I'm a complete idiot who doesn't even know how to make diffs, so I > > thought I'd just let everybody know right away instead of figuring out > > how to write a diff and holding out on you all for the time that may > > take - I'm a slow learner. > > $ cp foo foo.orig > $ your-favourite-editor foo > > $ diff -u foo.orig foo > foo.diff > > and that's about it. :-) > > Note that if you're sending a diff for documentation, diffs to the > SGML source are best because that's the format the documentation is > maintained in. (Well, the stuff under doc/ anyway, manpages are > different of course.) But if you don't have the SGML source installed, > a diff to the HTML would probably almost be sufficient to get the > problem fixed. > > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > FreeBSD Documentation Project / > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 20:23:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 6620737B667 for ; Wed, 19 Jul 2000 20:23:28 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id UAA00581; Wed, 19 Jul 2000 20:23:14 -0700 Message-ID: <397670B8.48BF4801@urx.com> Date: Wed, 19 Jul 2000 20:23:36 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Justin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading from 4.0release to 4.0stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin wrote: > > Does nayone know a current or updated DOC or LINK to this info, or is it > as simple as a 3.4 release to 3.4 stable procedure? If anyone has any tips > please send them my way @ asmo@bck.org > > I am not yet subscribed to the mailing list. > > Thanks for any assistance you can provide me! You have to cvsup and then read /usr/src/UPDATING. You can cvsup now but I don't if it will build. It was broken all day and I'm in the middle of a buildworld. Someone else may have finished their buildworld. Will try the "make buildkernel KERNEL=" next. Kent > > Justin > > -- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 20:41:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 1CFBD37B667 for ; Wed, 19 Jul 2000 20:41:18 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Wed Jul 19 23:39:30 2000 -0400 Received: by sn1exchmbx.nextvenue.com with Internet Mail Service (5.5.2650.21) id <3987SJGR>; Wed, 19 Jul 2000 23:36:54 -0400 Message-ID: <712384017032D411AD7B0001023D799B07CA14@sn1exchmbx.nextvenue.com> From: Nick Evans To: "'freebsd-stable@freebsd.org'" Subject: FW: URGENT: FreeBSD-4 Testing. Date: Wed, 19 Jul 2000 23:36:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFF1FB.BC79FDE0" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFF1FB.BC79FDE0 Content-Type: text/plain; charset="iso-8859-1" Hope this helps IPFilter people... -----Original Message----- From: Darren Reed [mailto:darrenr@reed.wattle.id.au] Sent: Wednesday, July 19, 2000 7:38 PM To: pir@pir.net Cc: ipfilter@coombs.anu.edu.au Subject: Re: URGENT: FreeBSD-4 Testing. In some email I received from Peter Radcliffe, sie wrote: > cvsuped just now; > > ===> usr.sbin/ipftest [...] I've just finished messing around with CVS for FreeBSD (both -current and -stable). All the requisite changes should now be there. For some reason, when I did the pullup from the vendor branch, I screwed up (being after midnight and me needing sleep probably didn't help). Darren ------_=_NextPart_001_01BFF1FB.BC79FDE0 Content-Type: text/html; charset="iso-8859-1" FW: URGENT: FreeBSD-4 Testing.

Hope this helps IPFilter people...

-----Original Message-----
From: Darren Reed [mailto:darrenr@reed.wattle.id.au]
Sent: Wednesday, July 19, 2000 7:38 PM
To: pir@pir.net
Cc: ipfilter@coombs.anu.edu.au
Subject: Re: URGENT: FreeBSD-4 Testing.


In some email I received from Peter Radcliffe, sie wrote:
> cvsuped just now;
>
> ===> usr.sbin/ipftest
[...]

I've just finished messing around with CVS for FreeBSD (both -current
and -stable).  All the requisite changes should now be there.

For some reason, when I did the pullup from the vendor branch, I screwed
up (being after midnight and me needing sleep probably didn't help).

Darren

------_=_NextPart_001_01BFF1FB.BC79FDE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 20:43:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 1336D37B667 for ; Wed, 19 Jul 2000 20:43:14 -0700 (PDT) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.10.1/8.10.1/20000715) id e6K3hAN04165; Wed, 19 Jul 2000 22:43:10 -0500 (CDT) From: Larry Rosenman Message-Id: <200007200343.e6K3hAN04165@lerami.lerctr.org> Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: <712384017032D411AD7B0001023D799B07CA14@sn1exchmbx.nextvenue.com> "from Nick Evans at Jul 19, 2000 11:36:49 pm" To: Nick Evans Date: Wed, 19 Jul 2000 22:43:10 -0500 (CDT) Cc: "'freebsd-stable@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL79 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's still broke at the moment. ipf (the command) is still broken. Larry Rosenman [ Charset ISO-8859-1 unsupported, converting... ] > Hope this helps IPFilter people... > > -----Original Message----- > From: Darren Reed [mailto:darrenr@reed.wattle.id.au] > Sent: Wednesday, July 19, 2000 7:38 PM > To: pir@pir.net > Cc: ipfilter@coombs.anu.edu.au > Subject: Re: URGENT: FreeBSD-4 Testing. > > > In some email I received from Peter Radcliffe, sie wrote: > > cvsuped just now; > > > > ===> usr.sbin/ipftest > [...] > > I've just finished messing around with CVS for FreeBSD (both -current > and -stable). All the requisite changes should now be there. > > For some reason, when I did the pullup from the vendor branch, I screwed > up (being after midnight and me needing sleep probably didn't help). > > Darren -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 21:41: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evelake.pdl.cs.cmu.edu (EVELAKE.PDL.CS.CMU.EDU [128.2.189.75]) by hub.freebsd.org (Postfix) with SMTP id 32AD637BA86 for ; Wed, 19 Jul 2000 21:40:56 -0700 (PDT) (envelope-from magus+@evelake.pdl.cs.cmu.edu) To: Larry Rosenman Cc: "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. References: <200007200343.e6K3hAN04165@lerami.lerctr.org> From: Nat Lanza Date: 20 Jul 2000 00:40:16 -0400 In-Reply-To: Larry Rosenman's message of "Wed, 19 Jul 2000 22:43:10 -0500 (CDT)" Message-ID: Lines: 36 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Rosenman writes: > It's still broke at the moment. > > ipf (the command) is still broken. The fix looks pretty simple, though. It looks like the makefile in src/sbin/ipf just isn't including common.c in the SRCS line. I've patched my local copy, and I'm rebuilding my world to make sure that that's the problem. Anyway, here's the patch. Untested, but I believe it should work. ---- snip ---- --- sbin/ipf/Makefile.old Thu Jul 20 00:37:57 2000 +++ sbin/ipf/Makefile Thu Jul 20 00:36:04 2000 @@ -6,7 +6,7 @@ MAN4= ipf.4 MAN5= ipf.5 MAN8= ipf.8 -SRCS= ipf.c parse.c opt.c facpri.c +SRCS= ipf.c parse.c opt.c facpri.c common.c CFLAGS+=-DIPL_NAME=\"/dev/ipl\" -I- -I${.CURDIR}/../../sys/netinet -I${.CURDIR}/../../contrib/ipfilter MAINTAINER= guido@freebsd.org ---- snip ---- --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 21:59:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A02FB37B92F; Wed, 19 Jul 2000 21:59:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA66135; Wed, 19 Jul 2000 21:59:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 19 Jul 2000 21:59:23 -0700 (PDT) From: Kris Kennaway To: Nat Lanza Cc: Larry Rosenman , "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Jul 2000, Nat Lanza wrote: > > It's still broke at the moment. > > > > ipf (the command) is still broken. > > The fix looks pretty simple, though. It looks like the makefile in > src/sbin/ipf just isn't including common.c in the SRCS line. Patch committed. Let's see if anything else is still broken *sigh* Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 22: 4: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evelake.pdl.cs.cmu.edu (EVELAKE.PDL.CS.CMU.EDU [128.2.189.75]) by hub.freebsd.org (Postfix) with SMTP id 05DDB37BAC1; Wed, 19 Jul 2000 22:04:04 -0700 (PDT) (envelope-from magus+@evelake.pdl.cs.cmu.edu) To: Kris Kennaway Cc: "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. References: From: Nat Lanza Date: 20 Jul 2000 01:03:57 -0400 In-Reply-To: Kris Kennaway's message of "Wed, 19 Jul 2000 21:59:23 -0700 (PDT)" Message-ID: Lines: 40 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > On 20 Jul 2000, Nat Lanza wrote: > > > > It's still broke at the moment. > > > > > > ipf (the command) is still broken. > > > > The fix looks pretty simple, though. It looks like the makefile in > > src/sbin/ipf just isn't including common.c in the SRCS line. > > Patch committed. Let's see if anything else is still broken *sigh* Looks like ipfstat has the exact same problem: ---- snip ---- --- sbin/ipfstat/Makefile.old Thu Jul 20 01:01:40 2000 +++ sbin/ipfstat/Makefile Thu Jul 20 01:01:48 2000 @@ -4,7 +4,7 @@ PROG= ipfstat MAN8= ipfstat.8 -SRCS= fils.c parse.c opt.c kmem.c facpri.c +SRCS= fils.c parse.c opt.c kmem.c facpri.c common.c CFLAGS+=-DIPL_NAME=\"/dev/ipl\" -I- -I${.CURDIR}/../../sys/netinet -I${.CURDIR}/../../sys -I${.CURDIR}/../../contrib/ipfilter MAINTAINER= guido@freebsd.org ---- snip ---- FWIW, the -CURRENT versions (v1.5) of the ipf and ipfstat makefiles have common.c added to them; I guess Darren just forgot to pull those changes down. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 22:15:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 607E137BF3A; Wed, 19 Jul 2000 22:15:52 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA70643; Wed, 19 Jul 2000 22:15:52 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 19 Jul 2000 22:15:52 -0700 (PDT) From: Kris Kennaway To: Nat Lanza Cc: "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Jul 2000, Nat Lanza wrote: > > Patch committed. Let's see if anything else is still broken *sigh* > > Looks like ipfstat has the exact same problem: Patch committed. Let's see if anything else is still broken *sigh* Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 22:28:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from adsl-151-197-200-119.bellatlantic.net (adsl-151-197-200-119.bellatlantic.net [151.197.200.119]) by hub.freebsd.org (Postfix) with ESMTP id 658DA37BAF0; Wed, 19 Jul 2000 22:28:28 -0700 (PDT) (envelope-from bleez@bellatlantic.net) Received: from localhost (root@localhost) by adsl-151-197-200-119.bellatlantic.net (8.9.3/8.9.3) with ESMTP id BAA63587; Thu, 20 Jul 2000 01:28:25 -0400 (EDT) (envelope-from bleez@bellatlantic.net) Date: Thu, 20 Jul 2000 01:28:25 -0400 (EDT) From: Bryan Liesner X-Sender: root@adsl-151-197-200-119.bellatlantic.net To: Kris Kennaway Cc: Nat Lanza , "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Kris Kennaway wrote: >On 20 Jul 2000, Nat Lanza wrote: > >> > Patch committed. Let's see if anything else is still broken *sigh* >> >> Looks like ipfstat has the exact same problem: > >Patch committed. Let's see if anything else is still broken *sigh* One more - ipnat is missing common.c from the SRCS line. ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@bellatlantic.net Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 22:47: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (ztown3-3-80.adsl.one.net [216.23.29.80]) by hub.freebsd.org (Postfix) with ESMTP id 2B0F737BBA5 for ; Wed, 19 Jul 2000 22:46:57 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id BAA27835; Thu, 20 Jul 2000 01:52:31 -0400 (EDT) (envelope-from cokane) Date: Thu, 20 Jul 2000 01:52:31 -0400 From: Coleman Kane To: Max Khon Cc: stable@freebsd.org Subject: Re: 4.0-20000714-SNAP on 486 DX2-66 Message-ID: <20000720015231.C27667@cokane.yi.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from fjoe@iclub.nsu.ru on Wed, Jul 19, 2000 at 01:34:48AM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excellent, man. That's totally awesome. I love old hardware that's made use of. Max Khon had the audacity to say: > hi, there! > > yesterday I have succesfully installed 4.0-20000714-SNAP > (I have built it by myself) on 486 DX2-66 machine > (3.4/3.5-RELEASE refused to install there -- hangs while installing > probably related to bugs in wd driver) > > everything seems to work fine > generating DSA key takes 20 minutes (no less!) > > /fjoe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 22:47:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A9DBD37BB7E; Wed, 19 Jul 2000 22:47:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA76319; Wed, 19 Jul 2000 22:47:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 19 Jul 2000 22:47:15 -0700 (PDT) From: Kris Kennaway To: Bryan Liesner Cc: Nat Lanza , "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Bryan Liesner wrote: > >> > Patch committed. Let's see if anything else is still broken *sigh* > >> > >> Looks like ipfstat has the exact same problem: > > > >Patch committed. Let's see if anything else is still broken *sigh* > > One more - ipnat is missing common.c from the SRCS line. Patch committed. Let's see if anything else is still broken *sigh* Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 23:15:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evelake.pdl.cs.cmu.edu (EVELAKE.PDL.CS.CMU.EDU [128.2.189.75]) by hub.freebsd.org (Postfix) with SMTP id 2C4FA37BAAB; Wed, 19 Jul 2000 23:15:28 -0700 (PDT) (envelope-from magus+@evelake.pdl.cs.cmu.edu) To: Kris Kennaway Cc: Bryan Liesner , "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. References: From: Nat Lanza Date: 20 Jul 2000 02:14:58 -0400 In-Reply-To: Kris Kennaway's message of "Wed, 19 Jul 2000 22:47:15 -0700 (PDT)" Message-ID: Lines: 27 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > Patch committed. Let's see if anything else is still broken *sigh* ipftest as well: ---- snip ---- --- usr.sbin/ipftest/Makefile.old Thu Jul 20 02:13:24 2000 +++ usr.sbin/ipftest/Makefile Thu Jul 20 02:13:34 2000 @@ -8,7 +8,7 @@ SRCS= opt_ipfilter.h \ ipt.c parse.c fil.c ipft_sn.c ipft_ef.c ipft_td.c ipft_pc.c opt.c \ ipft_tx.c misc.c ip_frag.c ip_state.c ip_nat.c ip_proxy.c \ - ip_auth.c ipft_hx.c ip_fil.c natparse.c facpri.c + ip_auth.c ipft_hx.c ip_fil.c natparse.c facpri.c common.c CFLAGS+=-DIPL_NAME=\"/dev/ipl\" -I- -I${.OBJDIR} -I${.CURDIR}/../../sys/netinet -I${.CURDIR}/../../sys -I${.CURDIR}/../../contrib/ipfilter ---- snip ---- --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 23:32:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evelake.pdl.cs.cmu.edu (EVELAKE.PDL.CS.CMU.EDU [128.2.189.75]) by hub.freebsd.org (Postfix) with SMTP id 4C75F37BAAB; Wed, 19 Jul 2000 23:31:01 -0700 (PDT) (envelope-from magus+@evelake.pdl.cs.cmu.edu) To: Kris Kennaway Cc: Bryan Liesner , "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. References: From: Nat Lanza Date: 20 Jul 2000 02:30:36 -0400 In-Reply-To: Nat Lanza's message of "20 Jul 2000 02:14:58 -0400" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like that's it; after the ipftest test, my 'buildworld -DNOCLEAN' finishes without bombing out again. I'm running a full buildworld from scratch to make sure things are really okay, though. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 23:33:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 6F4F637BAAB for ; Wed, 19 Jul 2000 23:33:43 -0700 (PDT) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id IAA05811; Thu, 20 Jul 2000 08:33:39 +0200 (MET DST) Received: by adv.iae.nl (Postfix, from userid 100) id 8223C22E3; Thu, 20 Jul 2000 08:33:22 +0200 (CEST) To: magus@cs.cmu.edu Subject: Re: FW: URGENT: FreeBSD-4 Testing. X-Newsgroups: list.freebsd.stable In-Reply-To: References: Organization: Eindhoven, the Netherlands Cc: stable@freebsd.org Message-Id: <20000720063322.8223C22E3@adv.iae.nl> Date: Thu, 20 Jul 2000 08:33:22 +0200 (CEST) From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Kris Kennaway writes: > >> Patch committed. Let's see if anything else is still broken *sigh* > >ipftest as well: *sigh* indeed This should be a rather complete list of ipfilter binaries: [/usr/src] devet@adv> fgrep -l ipfilter sbin/*/Makefile usr.sbin/*/Makefile sbin/ipf/Makefile sbin/ipfstat/Makefile sbin/ipmon/Makefile sbin/ipnat/Makefile usr.sbin/ipftest/Makefile usr.sbin/ipresend/Makefile usr.sbin/ipsend/Makefile usr.sbin/iptest/Makefile I think the sbin parts have all been fixed, it would be nice if someone with commit privileges could fix all usr.sbin parts. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 23:42:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iserver.itworks.com.au (iserver.itworks.com.au [203.32.61.10]) by hub.freebsd.org (Postfix) with SMTP id CA3A637BAF5 for ; Wed, 19 Jul 2000 23:42:25 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: (qmail 81278 invoked from network); 20 Jul 2000 06:42:22 -0000 Received: from maybe.itworks.com.au (203.36.209.235) by iserver.itworks.com.au with SMTP; 20 Jul 2000 06:42:22 -0000 Received: (qmail 6318 invoked from network); 20 Jul 2000 06:42:22 -0000 Received: from maybe.itworks.com.au (HELO maybe) (203.36.209.235) by maybe.itworks.com.au with SMTP; 20 Jul 2000 06:42:22 -0000 Date: Thu, 20 Jul 2000 16:42:22 +1000 (EST) From: Gavin Cameron To: stable@freebsd.org Subject: Stable broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From a cvsupped stable this morning I'm getting the following error in /sbin/ipf cc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/home/src/FreeBSD4/src/sbin/ipf/../../sys/netinet -I/home/src/FreeBSD4/src/sbin/ipf/../../contrib/ipfilter -I/usr/obj/home/src/FreeBSD4/src/i386/usr/include -static -o ipf ipf.o parse.o opt.o facpri.o ipf.o: In function `procfile': ipf.o(.text+0x349): undefined reference to `initparse' parse.o: In function `parse': parse.o(.text+0x3ec): undefined reference to `ratoui' parse.o(.text+0x9e7): undefined reference to `ratoi' parse.o(.text+0xa23): undefined reference to `proto' parse.o(.text+0xa7d): undefined reference to `proto' parse.o(.text+0xa92): undefined reference to `proto' parse.o(.text+0xaed): undefined reference to `proto' parse.o(.text+0xb00): undefined reference to `proto' parse.o(.text+0xb28): more undefined references to `proto' follow parse.o: In function `parse': parse.o(.text+0xced): undefined reference to `hostmask' parse.o(.text+0xdbd): undefined reference to `hostmask' parse.o(.text+0xe96): undefined reference to `tcp_flags' parse.o(.text+0x1039): undefined reference to `ratoui' parse.o(.text+0x10bd): undefined reference to `ratoui' parse.o: In function `to_interface': parse.o(.text+0x1332): undefined reference to `hostnum' parse.o: In function `addicmp': parse.o(.text+0x1a7e): undefined reference to `ratoi' parse.o(.text+0x1b82): undefined reference to `ratoi' parse.o: In function `icmpcode': parse.o(.text+0x1c47): undefined reference to `ratoi' parse.o: In function `printfr': parse.o(.text+0x214a): undefined reference to `printhostmask' parse.o(.text+0x2166): undefined reference to `printportcmp' parse.o(.text+0x21a2): undefined reference to `printhostmask' parse.o(.text+0x21be): undefined reference to `printportcmp' parse.o(.text+0x23b5): undefined reference to `flagset' parse.o(.text+0x23ba): undefined reference to `flags' parse.o(.text+0x23c0): undefined reference to `flagset' parse.o(.text+0x2485): undefined reference to `flagset' parse.o(.text+0x248a): undefined reference to `flags' parse.o(.text+0x2490): undefined reference to `flagset' *** Error code 1 Stop in /home/src/FreeBSD4/src/sbin/ipf. Gavin []-----------------------------------+------------------------------------[] | Gavin Cameron | ITworks Consulting | | Ph : +61 3 9642 5477 | Level 8, 488 Bourke Street | | Fax : +61 3 9642 5499 | Melbourne, Victoria | | Email : gavin@itworks.com.au | Australia, 3000 | []-----------------------------------+------------------------------------[] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 19 23:47:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 17BC737BC5E; Wed, 19 Jul 2000 23:47:47 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA83289; Wed, 19 Jul 2000 23:47:46 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 19 Jul 2000 23:47:46 -0700 (PDT) From: Kris Kennaway To: Nat Lanza Cc: Bryan Liesner , "'freebsd-stable@freebsd.org'" , Darren Reed Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Jul 2000, Nat Lanza wrote: > Looks like that's it; after the ipftest test, my 'buildworld -DNOCLEAN' > finishes without bombing out again. Here's hoping. Your build machine must be faster than mine :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0: 3:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C706D37BAD7; Thu, 20 Jul 2000 00:03:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id AAA85071; Thu, 20 Jul 2000 00:03:21 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 20 Jul 2000 00:03:16 -0700 (PDT) From: Kris Kennaway To: Gavin Cameron Cc: stable@freebsd.org Subject: Re: Stable broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Gavin Cameron wrote: > >From a cvsupped stable this morning I'm getting the following error in > /sbin/ipf Yes, and if you'd been following -stable you'd have saved yourself the trouble. I've committed one more patch which I hope will fix things now (for the record, it wasn't me who broke all this ;-) My buildworld is still underway, so I won't be sure for an hour or so. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0: 9:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vega.uli.it (vega.uli.it [62.212.0.2]) by hub.freebsd.org (Postfix) with ESMTP id A0AB337BAD7 for ; Thu, 20 Jul 2000 00:09:15 -0700 (PDT) (envelope-from olgeni@uli.it) Received: from olgeni.uli.it (olgeni.uli.it [62.212.0.22]) by vega.uli.it (Postfix) with ESMTP id B49C43B013 for ; Thu, 20 Jul 2000 09:09:13 +0200 (CEST) Date: Thu, 20 Jul 2000 09:10:21 +0200 (CEST) From: Jimmy Olgeni X-Sender: olgeni@olgeni.localdomain.net To: freebsd-stable@freebsd.org Subject: vinum and shutdown cache sync Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have a vinum stripe (ad1 and da1, on 4.1-RC). If I run the "halt" command the system stops the "bufdaemon" and "syncer" processes, then I get an error message like (da1:ahc0:0:0:0) SYNCHRONIZE CACHE CDB 35 0 0 0 0 0 0 0 0 0 (da1:ahc0:0:0:0) ERROR CODE 96 The SCSI hard disk led then stays ON, and the kernel waits for a key to reboot, as usual. At the next reboot the vinum drive come up clean and works. This does not happen in an IDE only setup. If I do a "mount /mnt/stripe", "vinum stop" before "halt" I don't get this message. Any ideas? Jimmy --- vinum setup: Drive vinumdrive0: Device /dev/ad1e Created on olgeni.localdomain.net at Tue Jul 18 19:55:28 2000 Config last updated Thu Jul 20 08:40:39 2000 Size: 3243631104 bytes (3093 MB) volume vinum0 state up plex name vinum0.p0 state up org striped 1024s vol vinum0 sd name vinum0.p0.s0 drive vinumdrive0 plex vinum0.p0 state up len 4690944s driveoffset 265s plexoffset 0s sd name vinum0.p0.s1 drive vinumdrive1 plex vinum0.p0 state up len 4690944s driveoffset 265s plexoffset 1024s Drive /dev/ad1e: 3093 MB (3243631104 bytes) Drive vinumdrive1: Device /dev/da1e Created on olgeni.localdomain.net at Tue Jul 18 19:55:28 2000 Config last updated Thu Jul 20 08:40:39 2000 Size: 2402271232 bytes (2290 MB) volume vinum0 state up plex name vinum0.p0 state up org striped 1024s vol vinum0 sd name vinum0.p0.s0 drive vinumdrive0 plex vinum0.p0 state up len 4690944s driveoffset 265s plexoffset 0s sd name vinum0.p0.s1 drive vinumdrive1 plex vinum0.p0 state up len 4690944s driveoffset 265s plexoffset 1024s Drive /dev/da1e: 2290 MB (2402271232 bytes) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0:10:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id BE1F737BC78; Thu, 20 Jul 2000 00:10:48 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id AAA01208; Thu, 20 Jul 2000 00:10:47 -0700 Message-ID: <3976A60C.BE9DE986@urx.com> Date: Thu, 20 Jul 2000 00:11:08 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Gavin Cameron , stable@FreeBSD.ORG Subject: Re: Stable broken References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Thu, 20 Jul 2000, Gavin Cameron wrote: > > > >From a cvsupped stable this morning I'm getting the following error in > > /sbin/ipf > > Yes, and if you'd been following -stable you'd have saved yourself the > trouble. I've committed one more patch which I hope will fix things now > (for the record, it wasn't me who broke all this ;-) My buildworld is > still underway, so I won't be sure for an hour or so. I thought the whole world was follow you all. Everytime you thought it was fixed all of the US cvsup sites that I use hit their limit :). I had never been rejected by cvsup7 until tonight. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0:15:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 2E94437B840 for ; Thu, 20 Jul 2000 00:15:11 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA06236; Thu, 20 Jul 2000 00:15:05 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <3976A6F9.111C93FA@gorean.org> Date: Thu, 20 Jul 2000 00:15:05 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eric D. Futch" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: hosts.allow strangeness? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Eric D. Futch" wrote: > > Ok never mind :) Forgot to add -w to inetd when I killed/restarted it. If you change inetd.conf you need to -HUP inetd, or kill it and restart it. You don't need to do either if you just change hosts.allow. The next time someone tries to connect to your machine the conf file will be read again. HTH, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0:26:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3A4D837B840; Thu, 20 Jul 2000 00:26:15 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA52614; Thu, 20 Jul 2000 09:26:10 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: "Jordan K. Hubbard" Cc: committers@FreeBSD.org, stable@FreeBSD.org Subject: Re: 4.1-STABLE code freeze on July 20th. References: <9405.963910516@localhost> From: Dag-Erling Smorgrav Date: 20 Jul 2000 09:26:10 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Tue, 18 Jul 2000 01:55:16 -0700" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=-=-= "Jordan K. Hubbard" writes: > [...] We're also going to > start releasing 4.1-RC (release candidate) releases very shortly from > ftp://releng4.freebsd.org/pub/FreeBSD so that more advance testing can > be done. Please fix ftpd on releng4! :) I've attached an updated patch. --=-=-= Content-Disposition: attachment; filename=ftpd.diff Content-Description: patch Index: ftpd.c =================================================================== RCS file: /home/ncvs/src/libexec/ftpd/ftpd.c,v retrieving revision 1.64 diff -u -r1.64 ftpd.c --- ftpd.c 2000/06/26 05:36:09 1.64 +++ ftpd.c 2000/07/20 07:20:48 @@ -139,6 +139,7 @@ int anon_only = 0; /* Only anonymous ftp allowed */ int guest; int dochroot; +int have_tar; int stats; int statfd = -1; int type; @@ -1302,6 +1303,9 @@ goto bad; } + /* Check the availability of tar */ + have_tar = (access(_PATH_TAR, X_OK) == 0); + /* * Display a login message, if it exists. * N.B. reply(230,) must follow the message. @@ -1379,15 +1383,34 @@ retrieve(cmd, name) char *cmd, *name; { + char dir[MAXPATHLEN]; FILE *fin, *dout; struct stat st; int (*closefunc) __P((FILE *)); time_t start; + size_t len; if (cmd == 0) { fin = fopen(name, "r"), closefunc = fclose; st.st_size = 0; - } else { + } + if (cmd == 0 && fin == NULL && errno == ENOENT && have_tar) { + len = strlen(name) - 4; + if (len > 0 && len < MAXPATHLEN && + (strcmp(name + len, ".tar") == 0 || + strcmp(name + len, ".tgz") == 0)) { + strncpy(dir, name, len); + dir[len] = 0; + if (stat(dir, &st) != -1 && S_ISDIR(st.st_mode)) { + if (name[len + 3] == 'z') + cmd = _PATH_TAR " -zcf - %s"; + else + cmd = _PATH_TAR " -cf - %s"; + name = dir; + } + } + } + if (cmd != 0) { char line[BUFSIZ]; (void) snprintf(line, sizeof(line), cmd, name), name = line; Index: popen.c =================================================================== RCS file: /home/ncvs/src/libexec/ftpd/popen.c,v retrieving revision 1.18 diff -u -r1.18 popen.c --- popen.c 2000/01/27 09:28:21 1.18 +++ popen.c 2000/07/20 01:41:14 @@ -132,7 +132,6 @@ dup2(pdes[1], STDOUT_FILENO); (void)close(pdes[1]); } - dup2(STDOUT_FILENO, STDERR_FILENO); /* stderr too! */ (void)close(pdes[0]); } else { if (pdes[0] != STDIN_FILENO) { Index: paths.h =================================================================== RCS file: /home/ncvs/src/include/paths.h,v retrieving revision 1.9 diff -u -r1.9 paths.h --- paths.h 1999/01/11 09:07:41 1.9 +++ paths.h 2000/07/20 00:32:34 @@ -59,6 +59,7 @@ #define _PATH_NOLOGIN "/var/run/nologin" #define _PATH_SENDMAIL "/usr/sbin/sendmail" #define _PATH_SHELLS "/etc/shells" +#define _PATH_TAR "/usr/bin/tar" #define _PATH_TTY "/dev/tty" #define _PATH_UNIX "don't use _PATH_UNIX" #define _PATH_VI "/usr/bin/vi" --=-=-= DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0:33:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 4E4BF37BED5; Thu, 20 Jul 2000 00:33:14 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6K7X7B19975; Thu, 20 Jul 2000 09:33:08 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6K7X6P08753; Thu, 20 Jul 2000 09:33:06 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.10.2/8.10.2/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e6K7X6437436; Thu, 20 Jul 2000 09:33:06 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.10.2/8.10.2/alaska [ $Revision: 1.4 ]) id e6K7X5e00663; Thu, 20 Jul 2000 07:33:05 GMT Date: Thu, 20 Jul 2000 09:33:05 +0200 From: Udo Schweigert To: Kent Stewart Cc: Kris Kennaway , Gavin Cameron , stable@FreeBSD.ORG Subject: What does -RC mean? was: Re: Stable broken Message-ID: <20000720093305.A367@alaska.cert.siemens.de> References: <3976A60C.BE9DE986@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3976A60C.BE9DE986@urx.com>; from kstewart@urx.com on Thu, Jul 20, 2000 at 12:11:08AM -0700 X-Operating-System: FreeBSD 4.1-RC Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 00:11:08 -0700, Kent Stewart wrote: > > > Kris Kennaway wrote: > > > > On Thu, 20 Jul 2000, Gavin Cameron wrote: > > > > > >From a cvsupped stable this morning I'm getting the following error in > > > /sbin/ipf > > > > Yes, and if you'd been following -stable you'd have saved yourself the > > trouble. I've committed one more patch which I hope will fix things now > > (for the record, it wasn't me who broke all this ;-) My buildworld is > > still underway, so I won't be sure for an hour or so. > > I thought the whole world was follow you all. Everytime you thought it > was fixed all of the US cvsup sites that I use hit their limit :). I > had never been rejected by cvsup7 until tonight. > This is due to the fact that the in ports tree the tag RELEASE_4_1_0 has been added and so cvsup takes much longer since each file in the ports tree has to be changed. Anyway: it is a little bit annoying that the -stable branch keeps to be broken especially since it is labeled as a "release candidate" (4.1-RC). To my understanding a "release candidate" should only be changed if serious problems are detected (and not, for example, to bring in ipfilter update to -current and -stable at the same time, without testing period in -current). I thought having a release candidate should ensure that the final release is as stable as can be. Every change to the release candidate would normally result in a restart of the testing period. Other oppinions out there? Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0:45: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 9C7F437BAF9; Thu, 20 Jul 2000 00:44:46 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13FB0a-000L2X-01; Thu, 20 Jul 2000 07:44:41 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id JAA06446; Thu, 20 Jul 2000 09:32:34 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Jul 2000 09:32:34 +0200 From: Wilko Bulte To: "David O'Brien" Cc: alpha@freebsd.org, stable@freebsd.org Subject: Re: 4.1-RC snapshot on ftp.freebsd.org Message-ID: <20000720093233.A6432@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000719175558.A30579@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000719175558.A30579@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Jul 19, 2000 at 05:55:58PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 05:55:58PM -0700, David O'Brien wrote: > I have placed a 4.1-20000718-RC DEC Alpha snapshot at > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.1-20000718-RC/ > > Enjoy! No :-( It has no /boot and no kernel... And I wanted to see if I could get a bootable CD... -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 0:58:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 5BE8A37BBFE; Thu, 20 Jul 2000 00:58:14 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id AAA01307; Thu, 20 Jul 2000 00:58:11 -0700 Message-ID: <3976B127.9E42BC4E@urx.com> Date: Thu, 20 Jul 2000 00:58:31 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Udo Schweigert Cc: Kris Kennaway , Gavin Cameron , stable@FreeBSD.ORG Subject: Re: What does -RC mean? was: Re: Stable broken References: <3976A60C.BE9DE986@urx.com> <20000720093305.A367@alaska.cert.siemens.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Udo Schweigert wrote: > > On Thu, Jul 20, 2000 at 00:11:08 -0700, Kent Stewart wrote: > > > > > > Kris Kennaway wrote: > > > > > > On Thu, 20 Jul 2000, Gavin Cameron wrote: > > > > > > > >From a cvsupped stable this morning I'm getting the following error in > > > > /sbin/ipf > > > > > > Yes, and if you'd been following -stable you'd have saved yourself the > > > trouble. I've committed one more patch which I hope will fix things now > > > (for the record, it wasn't me who broke all this ;-) My buildworld is > > > still underway, so I won't be sure for an hour or so. > > > > I thought the whole world was follow you all. Everytime you thought it > > was fixed all of the US cvsup sites that I use hit their limit :). I > > had never been rejected by cvsup7 until tonight. > > > > This is due to the fact that the in ports tree the tag RELEASE_4_1_0 has > been added and so cvsup takes much longer since each file in the ports tree > has to be changed. It did jump from 5 or 6 minutes to 20+. > > Anyway: it is a little bit annoying that the -stable branch keeps to be broken > especially since it is labeled as a "release candidate" (4.1-RC). To my > understanding a "release candidate" should only be changed if serious problems > are detected (and not, for example, to bring in ipfilter update to -current and > -stable at the same time, without testing period in -current). I thought having > a release candidate should ensure that the final release is as stable as can be. > Every change to the release candidate would normally result in a restart of the > testing period. There were a couple of concurrent failures. The ipfilter problem wasn't seen on my end until nametoaddr.c was fixed. We found nametoaddr.c was broken almost 24 hours ago. Messages popped up separated by 4 minutes. It was fixed this morning about 8 hours later and then ipfilter hit. I guess the code freeze time has been reached now and we can see what we have. My first buildworld just finished. Now, I will see what my buildkernel does. Kent > > Other oppinions out there? > > Regards > -- > Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 > ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 > D-81730 Muenchen / Germany | email : ust@cert.siemens.de > PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 1:13:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id D902D37BC0F; Thu, 20 Jul 2000 01:13:31 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id KAA74049; Thu, 20 Jul 2000 10:13:16 +0200 (CEST) (envelope-from asmodai) Date: Thu, 20 Jul 2000 10:13:16 +0200 From: Jeroen Ruigrok van der Werven To: Dag-Erling Smorgrav Cc: "Jordan K. Hubbard" , committers@FreeBSD.org, stable@FreeBSD.org Subject: Re: 4.1-STABLE code freeze on July 20th. Message-ID: <20000720101315.B73802@lucifer.bart.nl> References: <9405.963910516@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from des@flood.ping.uio.no on Thu, Jul 20, 2000 at 09:26:10AM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000720 09:30], Dag-Erling Smorgrav (des@flood.ping.uio.no) wrote: >"Jordan K. Hubbard" writes: >> [...] We're also going to >> start releasing 4.1-RC (release candidate) releases very shortly from >> ftp://releng4.freebsd.org/pub/FreeBSD so that more advance testing can >> be done. > >Please fix ftpd on releng4! :) > >I've attached an updated patch. Is this worth bumping ftpd's version from 6.00LS to another one? -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl The way to love anything is to realize that it might be lost... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 2:10:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 150F037BE0E; Thu, 20 Jul 2000 02:10:19 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id LAA97511; Thu, 20 Jul 2000 11:10:17 +0200 (CEST) (envelope-from asmodai) Date: Thu, 20 Jul 2000 11:10:16 +0200 From: Jeroen Ruigrok van der Werven To: John Baldwin Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: bootdisk problems/md related Message-ID: <20000720111016.F73802@lucifer.bart.nl> References: <20000717200844.I38656@lucifer.bart.nl> <20000718094312.A45185@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000718094312.A45185@lucifer.bart.nl>; from jruigrok@via-net-works.nl on Tue, Jul 18, 2000 at 09:43:12AM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000718 09:45], Jeroen Ruigrok van der Werven (jruigrok@via-net-works.nl) wrote: >-On [20000717 23:45], John Baldwin (jhb@FreeBSD.ORG) wrote: >>On 17-Jul-00 Jeroen Ruigrok van der Werven wrote: >>> -On [20000717 20:05], John Baldwin (jhb@freebsd.org) wrote: >Mounting root from ufs:/dev/md0c >md0: raw parition size != slice size >md0: start 0, end 855, size 856 >md0c: start 0, end 5759, size 5760 >md0: truncating new parition >md0: rejecting partition in BSD label: it isn't entirely within the slice >md0: start 0, end 855, size 856 >md0a: start 0, size 5759, size 5760 >spec_getpages: (#md/2) I/O read failure: (error 22) bp 0xc5f50420 vp 0xcb307ec0 > size: 4096, resid: 4096, a_count: 4096, valid: 0x0 > nread: 0, reqpage: 0, pindex: 405, pcount: 1 >vm_fault: pager read error, pid 1 (swapper) >init died (signal 6, exit 0) >panic: going nowhere without my init! Disks from 0718 still produce this error. I now get another cute thing before booting the kernel: zf_read: fill error. I'll go grab a bunch of new disks and try to boot from that. Let you know. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I came, I saw, I conquered... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 2:21:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CA0A237BE9A; Thu, 20 Jul 2000 02:21:28 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6K9LOe01373; Thu, 20 Jul 2000 02:21:24 -0700 (PDT) Date: Thu, 20 Jul 2000 02:21:24 -0700 From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: "Jordan K. Hubbard" , committers@FreeBSD.org, stable@FreeBSD.org Subject: Re: 4.1-STABLE code freeze on July 20th. Message-ID: <20000720022124.H13979@fw.wintelcom.net> References: <9405.963910516@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from des@flood.ping.uio.no on Thu, Jul 20, 2000 at 09:26:10AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dag-Erling Smorgrav [000720 00:29] wrote: > "Jordan K. Hubbard" writes: > > [...] We're also going to > > start releasing 4.1-RC (release candidate) releases very shortly from > > ftp://releng4.freebsd.org/pub/FreeBSD so that more advance testing can > > be done. > > Please fix ftpd on releng4! :) > > I've attached an updated patch. > I think you can cause some serious problem with directories with spaces in them, basically being able to send extra flags to tar? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 2:38:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 2AE8337B625; Thu, 20 Jul 2000 02:38:11 -0700 (PDT) (envelope-from asmodai@lucifer.ninth-circle.org) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id LAA05796; Thu, 20 Jul 2000 11:38:09 +0200 (CEST) (envelope-from asmodai) Date: Thu, 20 Jul 2000 11:38:08 +0200 From: Jeroen Ruigrok van der Werven To: John Baldwin Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: bootdisk problems/md related Message-ID: <20000720113805.H73802@lucifer.bart.nl> References: <20000717200844.I38656@lucifer.bart.nl> <20000718094312.A45185@lucifer.bart.nl> <20000720111016.F73802@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000720111016.F73802@lucifer.bart.nl>; from jruigrok@via-net-works.nl on Thu, Jul 20, 2000 at 11:10:16AM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000720 11:15], Jeroen Ruigrok van der Werven (jruigrok@via-net-works.nl) wrote: >Disks from 0718 still produce this error. > >I now get another cute thing before booting the kernel: > >zf_read: fill error. > >I'll go grab a bunch of new disks and try to boot from that. Hmmm. How I hate floppies. I tried the image on a few and got the above errors. I just grabbed a few other ones to try them and they work. *sigh* Sorry for the trouble guys. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl And I'm learning the highs and lows of the fake promises... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 4: 1:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 43AFF37BBA5; Thu, 20 Jul 2000 04:01:30 -0700 (PDT) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id LAA20700; Thu, 20 Jul 2000 11:01:23 GMT From: Darren Reed Message-Id: <200007201100.VAA12899@avalon.reed.wattle.id.au> Subject: Re: FW: URGENT: FreeBSD-4 Testing. In-Reply-To: from Nat Lanza at "Jul 20, 0 02:30:36 am" To: magus@cs.cmu.edu (Nat Lanza) Date: Thu, 20 Jul 2000 21:00:55 +1000 (EST) Cc: kris@FreeBSD.org, bleez@bellatlantic.net, freebsd-stable@FreeBSD.org, darrenr@reed.wattle.id.au X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Nat Lanza, sie wrote: > > Looks like that's it; after the ipftest test, my 'buildworld -DNOCLEAN' > finishes without bombing out again. > > I'm running a full buildworld from scratch to make sure things are > really okay, though. Thanks for the help during the day guys, I was at work and unable to do anything constructive. I *never* want to do that again. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 4:40:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CBB5F37B744; Thu, 20 Jul 2000 04:40:37 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA53616; Thu, 20 Jul 2000 13:40:33 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Alfred Perlstein Cc: "Jordan K. Hubbard" , committers@FreeBSD.org, stable@FreeBSD.org Subject: Re: 4.1-STABLE code freeze on July 20th. References: <9405.963910516@localhost> <20000720022124.H13979@fw.wintelcom.net> From: Dag-Erling Smorgrav Date: 20 Jul 2000 13:40:32 +0200 In-Reply-To: Alfred Perlstein's message of "Thu, 20 Jul 2000 02:21:24 -0700" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > I think you can cause some serious problem with directories with > spaces in them, basically being able to send extra flags to tar? The only option you're allowed to mix with filenames is -C, which is harmless, I think. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 20 5:33: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.145.166]) by hub.freebsd.org (Postfix) with SMTP id 2DE8237BA97 for ; Thu, 20 Jul 2000 05:32:21 -0700 (PDT) (envelope-from avatar@www.mmlab.cse.yzu.edu.tw) Received: (qmail 72016 invoked from network); 20 Jul 2000 12:31:40 -0000 Received: from www.mmlab.cse.yzu.edu.tw (HELO www.mmlab.cse.yzu.edu.tw.) (@140.138.145.166) by www.mmlab.cse.yzu.edu.tw with SMTP; 20 Jul 2000 12:31:40 -0000 Date: Thu, 20 Jul 2000 20:31:40 +0800 (CST) From: Tai-hwa Liang To: freebsd-stable@FreeBSD.org Subject: -stable ISA PnP config(controller pnp0) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried to upgrade from 3.4-RELEASE to 4.1-RC hours ago, and noticed that "controller pnp0" was removed from kernel configuration; furthermore, it seems that the "pnp" config option was also removed from "boot -c" editor. Without the ISA PnP configuration support, my SoundBlaster 16 PnP would unable to playback MIDI synth via VOXWARE snd driver(sb_reset_dsp failed during system startup). It also seems that the newpcm driver in 4-stable still doesn't support MIDI synth(/dev/sequencer) as the pcm0 device in 3-stable; therefore, I have to use VOXWARE to play with MIDI synth before new-midi being merged in the tree. Is there any workaround for me to manually config my ISA PnP device in 4-stable such that the VOXWARE snd driver can detect my sound card? Can anyone enlighten me the relation between PNPBIOS and "controller pnp0?" TIA. FYI(4.1-RC with PNPBIOS, snd, sb0, sbxvi0 & sbmidi0): sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sb_reset_dsp failed sb_reset_dsp failed ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown0: at iomem 0-0x9ffff,0x100000-0xfffffff,0xe8000-0xeffff,0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xcd000-0xcffff,0xfffe0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x75 irq 8 on isa0 unknown: can't assign resources unknown3: at port 0xf0 irq 13 on isa0 unknown4: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown5: at port 0x61 on isa0 unknown6: at port 0xcf8-0xcff on isa0 unknown7: at port 0xe400-0xe47f,0xe800-0xe83f on isa0 unknown8: