From owner-freebsd-stable Sun Nov 30 09:17:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA19011 for stable-outgoing; Sun, 30 Nov 1997 09:17:22 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from roma.coe.ufrj.br (root@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA19006 for ; Sun, 30 Nov 1997 09:17:14 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by roma.coe.ufrj.br (8.8.7/8.8.7) with ESMTP id PAA09559 for ; Sun, 30 Nov 1997 15:17:06 -0200 (EDT) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id PAA06628; Sun, 30 Nov 1997 15:16:56 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199711301716.PAA06628@gaia.coppe.ufrj.br> Subject: Re: IPX router problems In-Reply-To: from Mark at "Nov 26, 97 01:59:07 pm" To: mark.wild@cableinet.co.uk (Mark) Date: Sun, 30 Nov 1997 15:16:56 -0200 (EDT) Cc: freebsd-stable@FreeBSD.ORG@coe.ufrj.br X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk #define quoting(Mark) // Unfortunately there's no chance of moving to Eth. II. You don't need to move to ethernet II. You just need to bind ethernet_ii to the server's interface, and bind *another* IPX network to it. I've always ran netware with 2 or even 3 frames for IPX in each interface, and there's no problem in doing that. The only problem is that, since each bind is a different "network", each broadcast will be sent once for each bind. Also, traffic from a host through the router should go first to the server to be converted from 802.3 to ethernet_ii. In this sense, the server is also acting as a router between the frametypes. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-stable Sun Nov 30 15:32:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13880 for stable-outgoing; Sun, 30 Nov 1997 15:32:57 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13852 for ; Sun, 30 Nov 1997 15:32:50 -0800 (PST) (envelope-from bsdstab@shadows.aeon.net) Received: (from bsdstab@localhost) by shadows.aeon.net (8.8.8/8.8.3) id BAA26546; Mon, 1 Dec 1997 01:35:00 +0200 (EET) From: mika ruohotie Message-Id: <199711302335.BAA26546@shadows.aeon.net> Subject: Re: ide bus mastering In-Reply-To: from Doug Russell at "Nov 28, 97 04:23:09 pm" To: drussell@saturn-tech.com (Doug Russell) Date: Mon, 1 Dec 1997 01:35:00 +0200 (EET) Cc: jayrich@room101.sysc.com, freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On the other hand, I don't know of any cases where the DMA driver messed > up either, so perhaps we could all get together and make a decision as to > whether it is "good" enough to go into -stable yet. i dunno which one it was, probably rather my drive... last wednesday my wd34000 udma and asus tx97-e fell over for some unknown reason. what i had after that was mostly just files listed as inodes on all filesystems that i had running at the moment... since i lost parts of /dev and all /var (not /var/mail or /var/log which are separate silesystems) there wasnt much left i could boot up... good for me, things like /usr /usr/ports /usr/src all live in other filesystems, and /home too (lost parts of it also, no big deal) ofcourse, i recovered easily, took new drive, had to install 2.2.2 into it, didnt have other cdroms available, and then copied my -current leftovers over it. booted up as -current in less than an hour. facts: 1. i dont like wd34000, the drive i had acted strangely few times 2. i was running on 83MHz bus speed, i never slow that down 3. i was running filesystems async,noatime so basicly, i asked to blow up my filesystem, and i'm in no way saying it was the dma code. oh yeah, more facts: 5. i'm getting few small scsi drives, i'm sick of eide =) 6. i didnt lose anything i'd miss mickey From owner-freebsd-stable Sun Nov 30 16:07:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15760 for stable-outgoing; Sun, 30 Nov 1997 16:07:30 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA15755 for ; Sun, 30 Nov 1997 16:07:22 -0800 (PST) (envelope-from pantzer@ludd.luth.se) Received: from brother.ludd.luth.se.ludd (pantzer@brother.ludd.luth.se [130.240.16.78]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id BAA01164; Mon, 1 Dec 1997 01:07:07 +0100 Received: from localhost by brother.ludd.luth.se.ludd (4.1/SMI-4.1) id AA08573; Mon, 1 Dec 97 01:07:01 +0100 Date: Mon, 1 Dec 1997 01:07:01 +0100 (MET) From: Mattias Pantzare To: Justen Stepka Cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: CPU Load In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 29 Nov 1997, Justen Stepka wrote: > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), > when I did this the overall system preformance increased dramiticly. The > problem that I noticed was that when using NFS/NIS the CPU load climbs to > about 4.0+, is there a special reason that this might be happening? The load value is not CPU load. It is the average number of processes ready to run or waiting for disk I/O to complete. So it is normal for a NFS server to have a high load, as it is often waiting for disk I/O. From owner-freebsd-stable Sun Nov 30 20:34:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02478 for stable-outgoing; Sun, 30 Nov 1997 20:34:33 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from room101.sysc.com (qmailr@richmojm2.student.rose-hulman.edu [137.112.206.126]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA02470 for ; Sun, 30 Nov 1997 20:34:29 -0800 (PST) (envelope-from jayrich@room101.sysc.com) Received: (qmail 8034 invoked by uid 1000); 1 Dec 1997 04:34:12 -0000 Date: Sun, 30 Nov 1997 23:34:12 -0500 (EST) From: "Jay M. Richmond" To: freebsd-stable@freebsd.org Subject: Re: ide bus mastering In-Reply-To: <199711302335.BAA26546@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Dec 1997, mika ruohotie wrote: > > On the other hand, I don't know of any cases where the DMA driver messed > > up either, so perhaps we could all get together and make a decision as to > > whether it is "good" enough to go into -stable yet. > > 1. i dont like wd34000, the drive i had acted strangely few times > 2. i was running on 83MHz bus speed, i never slow that down > 3. i was running filesystems async,noatime I doubt that was due to the bus mastering driver too. Perhaps this could work a lkm and -stable users could "test" it, maybe even make it a kernel option or something, before it becomes part of the branch. Would someone be willing to do this? I would but I don't have the knowledge. Doug mentioned something about a patch to support bus mastering was already available for -stable, and that it was easy to find. Maybe I'm just blind, but does anyone know where this patch is located? Thanks for your time, Jay jayrich@sysc.com From owner-freebsd-stable Sun Nov 30 23:15:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA14033 for stable-outgoing; Sun, 30 Nov 1997 23:15:39 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA14013 for ; Sun, 30 Nov 1997 23:15:32 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xcQ3z-00006T-00; Sun, 30 Nov 1997 23:14:39 -0800 Date: Sun, 30 Nov 1997 23:14:34 -0800 (PST) From: Tom To: Mattias Pantzare cc: Justen Stepka , FreeBSD-stable@freebsd.org Subject: Re: CPU Load In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Dec 1997, Mattias Pantzare wrote: > On Sat, 29 Nov 1997, Justen Stepka wrote: > > > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), > > when I did this the overall system preformance increased dramiticly. The > > problem that I noticed was that when using NFS/NIS the CPU load climbs to > > about 4.0+, is there a special reason that this might be happening? > > The load value is not CPU load. It is the average number of processes > ready to run or waiting for disk I/O to complete. No, it is the average number of processes that are ready-to-run. Processes waiting for disk io (or any io) are not ready to run. > So it is normal for a NFS server to have a high load, as it is often > waiting for disk I/O. It is normal for NFS servers to have a low load, because NFS serving is not CPU intensive, and io bound. A load of 4+ for a NFS server is not normal. I would suggest determining which processes are using CPU time. Tom From owner-freebsd-stable Mon Dec 1 00:22:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA19169 for stable-outgoing; Mon, 1 Dec 1997 00:22:03 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from relay7.jaring.my (relay7.jaring.my [192.228.128.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA19159 for ; Mon, 1 Dec 1997 00:21:56 -0800 (PST) (envelope-from jahan@pc.jaring.my) Received: from pc.jaring.my (j50.ptl32.jaring.my [161.142.114.184]) by relay7.jaring.my (8.8.7/8.8.7) with ESMTP id QAA19368 for ; Mon, 1 Dec 1997 16:21:22 +0800 (MYT) Message-ID: <34826931.7D0A6983@pc.jaring.my> Date: Mon, 01 Dec 1997 14:37:21 +0700 From: jahan Reply-To: jahan@jjsoft.com Organization: J & J Software Solutions X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Sorry. But, why cant I su ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The group is wheel but can't su, can some one tell me ? Sorry that I ask here. From owner-freebsd-stable Mon Dec 1 00:28:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA19645 for stable-outgoing; Mon, 1 Dec 1997 00:28:38 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA19639 for ; Mon, 1 Dec 1997 00:28:35 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA02884; Mon, 1 Dec 1997 00:29:37 -0800 (PST) Message-Id: <199712010829.AAA02884@implode.root.com> To: Tom cc: Mattias Pantzare , Justen Stepka , FreeBSD-stable@FreeBSD.ORG Subject: Re: CPU Load In-reply-to: Your message of "Sun, 30 Nov 1997 23:14:34 PST." From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Dec 1997 00:29:37 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >On Mon, 1 Dec 1997, Mattias Pantzare wrote: > >> On Sat, 29 Nov 1997, Justen Stepka wrote: >> >> > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), >> > when I did this the overall system preformance increased dramiticly. The >> > problem that I noticed was that when using NFS/NIS the CPU load climbs to >> > about 4.0+, is there a special reason that this might be happening? >> >> The load value is not CPU load. It is the average number of processes >> ready to run or waiting for disk I/O to complete. > > No, it is the average number of processes that are ready-to-run. >Processes waiting for disk io (or any io) are not ready to run. Mattias Pantzare is correct. The load average is the number of runnable processes plus the number of processes in a short-term (disk) wait. It's meant to indicate the overall effect on interactive users, not necessarily just the use of the CPU. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Dec 1 01:31:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA23869 for stable-outgoing; Mon, 1 Dec 1997 01:31:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from odyssey.apana.org.au (odyssey.apana.org.au [203.11.114.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA23859 for ; Mon, 1 Dec 1997 01:31:42 -0800 (PST) (envelope-from dean@odyssey.apana.org.au) Received: from odyssey.apana.org.au (localhost.apana.org.au [127.0.0.1]) by odyssey.apana.org.au (8.8.7/8.8.7) with SMTP id RAA27166; Mon, 1 Dec 1997 17:30:36 +0800 (WST) Date: Mon, 1 Dec 1997 17:30:36 +0800 (WST) From: Dean Hollister To: jahan@jjsoft.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: Sorry. But, why cant I su ? In-Reply-To: <34826931.7D0A6983@pc.jaring.my> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Dec 1997, jahan wrote: > The group is wheel but can't su, can some one tell me ? Are you in the wheel group? You MUST be in the wheel group to su. Regards, d. +-------------------------------------------------------+ | Dean Hollister, | deanh@iinet.net.au | | Perth, Western Australia. | dean@odyssey.apana.org.au | +-------------------------------------------------------+ From owner-freebsd-stable Mon Dec 1 08:41:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19672 for stable-outgoing; Mon, 1 Dec 1997 08:41:30 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from adsdevelop.autodebit.com (adsdevelop.autodebit.com [204.50.245.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA19666 for ; Mon, 1 Dec 1997 08:41:25 -0800 (PST) (envelope-from davidg@autodebit.com) Received: by adsdevelop.autodebit.com with Microsoft Exchange (IMC 4.0.837.3) id <01BCFE34.73E6EEC0@adsdevelop.autodebit.com>; Mon, 1 Dec 1997 08:38:09 -0800 Message-ID: From: David Green-Seed To: "'FreeBSD-stable@FreeBSD.ORG'" Subject: bind fails Date: Mon, 1 Dec 1997 08:38:08 -0800 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm having troubles binding a socket to 127.0.0.1 - the error message says cannot assign address. Binding to 0.0.0.0 is no problem (of course). My machine is using ppp, and has no fixed ip address. Any help/hints would be appreciated. Dave. _________________________ David Green-Seed davidg@autodebit.com Automated Debit Systems From owner-freebsd-stable Mon Dec 1 09:09:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21562 for stable-outgoing; Mon, 1 Dec 1997 09:09:07 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from relay7.jaring.my (relay7.jaring.my [192.228.128.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21547 for ; Mon, 1 Dec 1997 09:08:53 -0800 (PST) (envelope-from jahan@pc.jaring.my) Received: from pc.jaring.my (j42.ptl37.jaring.my [161.142.115.116]) by relay7.jaring.my (8.8.7/8.8.7) with ESMTP id BAA21023 for ; Tue, 2 Dec 1997 01:08:40 +0800 (MYT) Message-ID: <3482F879.C23FCFFA@pc.jaring.my> Date: Tue, 02 Dec 1997 00:48:41 +0700 From: jahan Reply-To: jahan@jjsoft.com Organization: J & J Software Solutions X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: FreeBSD-stable@freebsd.org Subject: SU thing: here it is Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OS FreeBSD 2.2.1, why cannot su ? what am I missing. Group is right. See the output below. $ id uid=1000(jahan) gid=0(wheel) groups=0(wheel) $ su root su: you are not in the correct group to su root. $ From owner-freebsd-stable Mon Dec 1 09:36:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA24526 for stable-outgoing; Mon, 1 Dec 1997 09:36:47 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA24520 for ; Mon, 1 Dec 1997 09:36:44 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xcZjl-0006jz-00; Mon, 1 Dec 1997 09:34:25 -0800 Date: Mon, 1 Dec 1997 09:34:24 -0800 (PST) From: Tom To: David Greenman cc: Mattias Pantzare , Justen Stepka , FreeBSD-stable@freebsd.org Subject: Re: CPU Load In-Reply-To: <199712010829.AAA02884@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Dec 1997, David Greenman wrote: > >On Mon, 1 Dec 1997, Mattias Pantzare wrote: > > > >> On Sat, 29 Nov 1997, Justen Stepka wrote: > >> > >> > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), > >> > when I did this the overall system preformance increased dramiticly. The > >> > problem that I noticed was that when using NFS/NIS the CPU load climbs to > >> > about 4.0+, is there a special reason that this might be happening? > >> > >> The load value is not CPU load. It is the average number of processes > >> ready to run or waiting for disk I/O to complete. > > > > No, it is the average number of processes that are ready-to-run. > >Processes waiting for disk io (or any io) are not ready to run. > > Mattias Pantzare is correct. The load average is the number of runnable > processes plus the number of processes in a short-term (disk) wait. It's > meant to indicate the overall effect on interactive users, not necessarily > just the use of the CPU. Short term disk wait? Is there a long term disk wait too? What is the difference? There seem to be some differences in how different Unix systems calculate the load average. Linux seems to do something quite different for one. > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project Tom From owner-freebsd-stable Mon Dec 1 11:36:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06734 for stable-outgoing; Mon, 1 Dec 1997 11:36:47 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06724 for ; Mon, 1 Dec 1997 11:36:44 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA08439; Mon, 1 Dec 1997 11:35:30 -0800 (PST) Message-Id: <199712011935.LAA08439@implode.root.com> To: Tom cc: Mattias Pantzare , Justen Stepka , FreeBSD-stable@freebsd.org Subject: Re: CPU Load In-reply-to: Your message of "Mon, 01 Dec 1997 09:34:24 PST." From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Dec 1997 11:35:30 -0800 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Mattias Pantzare is correct. The load average is the number of runnable >> processes plus the number of processes in a short-term (disk) wait. It's >> meant to indicate the overall effect on interactive users, not necessarily >> just the use of the CPU. > > Short term disk wait? Is there a long term disk wait too? What is the >difference? You read that wrong. All disk waits are short term. Contrast that with tty waits which are considered long term. > There seem to be some differences in how different Unix systems >calculate the load average. Linux seems to do something quite different >for one. I don't know about Linux, but traditional Unix has always calculated the load average as a function of CPU+disk. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Dec 1 11:39:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07082 for stable-outgoing; Mon, 1 Dec 1997 11:39:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from python.shoal.net.au (perrya@python.shoal.net.au [203.26.44.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07074 for ; Mon, 1 Dec 1997 11:39:44 -0800 (PST) (envelope-from perrya@python.shoal.net.au) Received: from localhost (perrya@localhost) by python.shoal.net.au (8.8.6/8.8.5) with SMTP id GAA02305; Tue, 2 Dec 1997 06:39:08 +1100 (EST) Date: Tue, 2 Dec 1997 06:39:08 +1100 (EST) From: Andrew To: jahan@jjsoft.com cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: SU thing: here it is In-Reply-To: <3482F879.C23FCFFA@pc.jaring.my> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Have a look in /etc/group and see if you are in the wheel line like this: wheel:*:0:root,jahan if not, change it so you are. Andrew Perry perrya@shoal.net.au On Tue, 2 Dec 1997, jahan wrote: > Date: Tue, 02 Dec 1997 00:48:41 +0700 > From: jahan > Reply-To: jahan@jjsoft.com > To: FreeBSD-stable@FreeBSD.ORG > Subject: SU thing: here it is > > OS FreeBSD 2.2.1, > > why cannot su ? what am I missing. Group is right. > > See the output below. > > > $ id > uid=1000(jahan) gid=0(wheel) groups=0(wheel) > $ su root > su: you are not in the correct group to su root. > $ > > > From owner-freebsd-stable Mon Dec 1 13:05:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA17733 for stable-outgoing; Mon, 1 Dec 1997 13:05:19 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from bullfrog.winternet.com (jstepka@bullfrog.winternet.com [204.246.64.212]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA17718 for ; Mon, 1 Dec 1997 13:05:07 -0800 (PST) (envelope-from jstepka@bullfrog.winternet.com) Received: from localhost (jstepka@localhost) by bullfrog.winternet.com (8.8.5/8.8.5) with SMTP id OAA18636; Mon, 1 Dec 1997 14:59:44 -0600 (CST) Date: Mon, 1 Dec 1997 14:59:35 -0600 (CST) From: Justen Stepka To: Tom cc: Mattias Pantzare , Justen Stepka , FreeBSD-stable@freebsd.org Subject: Re: CPU Load In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 30 Nov 1997, Tom wrote: > > On Mon, 1 Dec 1997, Mattias Pantzare wrote: > > > On Sat, 29 Nov 1997, Justen Stepka wrote: > > > > > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), > > > when I did this the overall system preformance increased dramiticly. The > > > problem that I noticed was that when using NFS/NIS the CPU load climbs to > > > about 4.0+, is there a special reason that this might be happening? > > > > The load value is not CPU load. It is the average number of processes > > ready to run or waiting for disk I/O to complete. > > No, it is the average number of processes that are ready-to-run. > Processes waiting for disk io (or any io) are not ready to run. > > > So it is normal for a NFS server to have a high load, as it is often > > waiting for disk I/O. > > It is normal for NFS servers to have a low load, because NFS serving is > not CPU intensive, and io bound. > > A load of 4+ for a NFS server is not normal. I would suggest > determining which processes are using CPU time. the processes that are taking so much CPU time are the nsfd daemons, there are two of them with a 35%+ WCPU and CPU. Justen Stepka From owner-freebsd-stable Mon Dec 1 13:57:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA23670 for stable-outgoing; Mon, 1 Dec 1997 13:57:54 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from legend.sat.txdirect.net (root@legend.sat.txdirect.net [209.142.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA23665 for ; Mon, 1 Dec 1997 13:57:49 -0800 (PST) (envelope-from chad@txdirect.net) Received: from velocity (velocity.sat.txdirect.net [209.142.76.11]) by legend.sat.txdirect.net (8.8.7/8.8.7) with SMTP id PAA06586; Mon, 1 Dec 1997 15:52:35 -0600 (CST) Received: by localhost with Microsoft MAPI; Mon, 1 Dec 1997 15:52:33 -0600 Message-ID: From: Chad Scott To: "'Justen Stepka'" , Tom Cc: Mattias Pantzare , "FreeBSD-stable@freebsd.org" Subject: RE: CPU Load Date: Mon, 1 Dec 1997 15:52:33 -0600 Organization: Internet Direct, Incorporated X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 54 TEXT Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The "Load Average" on a UNIX machine is the average number of *BLOCKED* processes because of unavailable resources. Whether they're blocked from CPU or Disk I/O doesn't matter. They fact that they are blocked is what matters. A load of 4.0 on an NFS server is *not* normal because you have four processes that are blocked from lack of resources. This means you've got too little hardware to handle the requests you're getting. Chad Scott Network Operations Internet Direct, Incorporated -----Original Message----- From: Justen Stepka [SMTP:jstepka@chaos.winternet.com] Sent: Monday, December 01, 1997 3:50 PM To: Tom Cc: Mattias Pantzare; Justen Stepka; FreeBSD-stable@freebsd.org Subject: Re: CPU Load On Sun, 30 Nov 1997, Tom wrote: > > On Mon, 1 Dec 1997, Mattias Pantzare wrote: > > > On Sat, 29 Nov 1997, Justen Stepka wrote: > > > > > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), > > > when I did this the overall system preformance increased dramiticly. The > > > problem that I noticed was that when using NFS/NIS the CPU load climbs to > > > about 4.0+, is there a special reason that this might be happening? > > > > The load value is not CPU load. It is the average number of processes > > ready to run or waiting for disk I/O to complete. > > No, it is the average number of processes that are ready-to-run. > Processes waiting for disk io (or any io) are not ready to run. > > > So it is normal for a NFS server to have a high load, as it is often > > waiting for disk I/O. > > It is normal for NFS servers to have a low load, because NFS serving is > not CPU intensive, and io bound. > > A load of 4+ for a NFS server is not normal. I would suggest > determining which processes are using CPU time. the processes that are taking so much CPU time are the nsfd daemons, there are two of them with a 35%+ WCPU and CPU. Justen Stepka From owner-freebsd-stable Mon Dec 1 18:30:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA16233 for stable-outgoing; Mon, 1 Dec 1997 18:30:07 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from odyssey.apana.org.au (odyssey.apana.org.au [203.11.114.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA16198 for ; Mon, 1 Dec 1997 18:29:57 -0800 (PST) (envelope-from dean@odyssey.apana.org.au) Received: from odyssey.apana.org.au (localhost.apana.org.au [127.0.0.1]) by odyssey.apana.org.au (8.8.7/8.8.7) with SMTP id KAA11635; Tue, 2 Dec 1997 10:28:59 +0800 (WST) Date: Tue, 2 Dec 1997 10:28:59 +0800 (WST) From: Dean Hollister To: jahan@jjsoft.com cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: SU thing: here it is In-Reply-To: <3482F879.C23FCFFA@pc.jaring.my> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Dec 1997, jahan wrote: > OS FreeBSD 2.2.1, > > why cannot su ? what am I missing. Group is right. > > See the output below. > > > $ id > uid=1000(jahan) gid=0(wheel) groups=0(wheel) > $ su root > su: you are not in the correct group to su root. > $ Are you in the group file. Ie, /etc/group Login as root, and do: vi /etc/group The wheel group will need to look something like: wheel:*:0:root,jahan,user,user,user where "user" are any other users who want su access. Regards, d. +-------------------------------------------------------+ | Dean Hollister, | deanh@iinet.net.au | | Perth, Western Australia. | dean@odyssey.apana.org.au | +-------------------------------------------------------+ From owner-freebsd-stable Mon Dec 1 19:17:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA19749 for stable-outgoing; Mon, 1 Dec 1997 19:17:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from kinclaith.pdl.cs.cmu.edu (KINCLAITH.PDL.CS.CMU.EDU [128.2.189.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA19733 for ; Mon, 1 Dec 1997 19:17:46 -0800 (PST) (envelope-from dpetrou@KINCLAITH.PDL.CS.CMU.EDU) Message-Id: <199712020317.TAA19733@hub.freebsd.org> Subject: RE: CPU Load To: freebsd-stable@freebsd.org Date: Mon, 1 Dec 1997 22:17:39 -0500 (EST) From: David Petrou X-Mailer: ELM [version 2.4 PL25-40] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that there's a lot of misinformation being posted here re: cpu load. Just look at the relevant code from vm/vm_meter.c: static void loadav(struct loadavg *avg) { register int i, nrun; register struct proc *p; for (nrun = 0, p = allproc.lh_first; p != 0; p = p->p_list.le_next) { switch (p->p_stat) { case SSLEEP: if (p->p_priority > PZERO || p->p_slptime != 0) continue; /* fall through */ case SRUN: case SIDL: nrun++; } } for (i = 0; i < 3; i++) avg->ldavg[i] = (cexp[i] * avg->ldavg[i] + nrun * FSCALE * (FSCALE - cexp[i])) >> FSHIFT; } The important part is nrun... If a process is in SRUN or SIDL or it has a higher priority (lower numerically) than PZERO _AND_ it has slept less than a second, the process is counted. (That last clause covers fast disk operations...) David From owner-freebsd-stable Tue Dec 2 08:29:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA12226 for stable-outgoing; Tue, 2 Dec 1997 08:29:47 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mars.wexpress.com (drow@mars.wexpress.com [205.216.244.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12218 for ; Tue, 2 Dec 1997 08:29:44 -0800 (PST) (envelope-from drow@chwest.org) Received: from localhost (drow@localhost) by mars.wexpress.com (8.8.8/8.8.5) with SMTP id LAA14036 for ; Tue, 2 Dec 1997 11:28:16 -0500 (EST) Date: Tue, 2 Dec 1997 11:28:16 -0500 (EST) From: Dan Jacobowitz X-Sender: drow@mars.wexpress.com To: freebsd-stable@freebsd.org Subject: ipfw between kernel versions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just attempted to upgrade a 2.2.2 machine to 2.2.5 kernel, and I ran into a little problem. As near as I have been able to tell, the ipfw ioctl's changed between the two, causing ipfw to fail and not put in place the allow all rules needed to counter the default policy - thus no network. Is my interpretation of this correct? Should I just install 2.2.5 ipfw? (I'm going to make installworld after I get the kernel in, but based on past experience I want to do those two seperately.) Will the 2.2.5 ipfw work with a 2.2.2 kernel at all? From owner-freebsd-stable Tue Dec 2 09:55:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18513 for stable-outgoing; Tue, 2 Dec 1997 09:55:46 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from relay7.jaring.my (relay7.jaring.my [192.228.128.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18503 for ; Tue, 2 Dec 1997 09:55:42 -0800 (PST) (envelope-from jahan@pc.jaring.my) Received: from pc.jaring.my (j5.ptl38.jaring.my [161.142.115.19]) by relay7.jaring.my (8.8.7/8.8.7) with ESMTP id BAA01724; Wed, 3 Dec 1997 01:54:39 +0800 (MYT) Message-ID: <34845678.543BC9E7@pc.jaring.my> Date: Wed, 03 Dec 1997 01:42:00 +0700 From: jahan Reply-To: jahan@jjsoft.com Organization: J & J Software Solutions X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Dean Hollister CC: jahan@jjsoft.com, FreeBSD-stable@FreeBSD.ORG Subject: Re: SU thing: here it is References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes it works, thank you very much. Dean Hollister wrote: > > On Tue, 2 Dec 1997, jahan wrote: > > > OS FreeBSD 2.2.1, > > > > why cannot su ? what am I missing. Group is right. > > > > See the output below. > > > > > > $ id > > uid=1000(jahan) gid=0(wheel) groups=0(wheel) > > $ su root > > su: you are not in the correct group to su root. > > $ > > Are you in the group file. Ie, /etc/group > > Login as root, and do: > > vi /etc/group > > The wheel group will need to look something like: > > wheel:*:0:root,jahan,user,user,user > > where "user" are any other users who want su access. > > Regards, > > d. > > +-------------------------------------------------------+ > | Dean Hollister, | deanh@iinet.net.au | > | Perth, Western Australia. | dean@odyssey.apana.org.au | > +-------------------------------------------------------+ From owner-freebsd-stable Tue Dec 2 09:56:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18667 for stable-outgoing; Tue, 2 Dec 1997 09:56:45 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18662 for ; Tue, 2 Dec 1997 09:56:43 -0800 (PST) (envelope-from nash@Venus.mcs.net) Received: from Venus.mcs.net (nash@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA02731; Tue, 2 Dec 1997 11:56:42 -0600 (CST) Received: from localhost (nash@localhost) by Venus.mcs.net (8.8.7/8.8.2) with SMTP id LAA09566; Tue, 2 Dec 1997 11:56:42 -0600 (CST) Date: Tue, 2 Dec 1997 11:56:41 -0600 (CST) From: Alex Nash To: Dan Jacobowitz cc: freebsd-stable@freebsd.org Subject: Re: ipfw between kernel versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Dec 1997, Dan Jacobowitz wrote: > I just attempted to upgrade a 2.2.2 machine to 2.2.5 kernel, and I ran > into a little problem. As near as I have been able to tell, the ipfw > ioctl's changed between the two, causing ipfw to fail and not put in place > the allow all rules needed to counter the default policy - thus no > network. > > Is my interpretation of this correct? Should I just install 2.2.5 ipfw? Installing 2.2.5 ipfw would be enough to fix the problem. But you're better off remaking everything. > (I'm going to make installworld after I get the kernel in, but based on > past experience I want to do those two seperately.) > > Will the 2.2.5 ipfw work with a 2.2.2 kernel at all? 2.2.5 ipfw will not work with 2.2.2-RELEASE kernels, but will work with 2.2.2-STABLE after August 21st. Alex From owner-freebsd-stable Tue Dec 2 11:59:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28238 for stable-outgoing; Tue, 2 Dec 1997 11:59:23 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mars.wexpress.com (drow@mars.wexpress.com [205.216.244.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28224 for ; Tue, 2 Dec 1997 11:59:18 -0800 (PST) (envelope-from drow@chwest.org) Received: from localhost (drow@localhost) by mars.wexpress.com (8.8.8/8.8.5) with SMTP id OAA14923; Tue, 2 Dec 1997 14:57:41 -0500 (EST) Date: Tue, 2 Dec 1997 14:57:41 -0500 (EST) From: Dan Jacobowitz X-Sender: drow@mars.wexpress.com To: Alex Nash cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw between kernel versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Dec 1997, Alex Nash wrote: > On Tue, 2 Dec 1997, Dan Jacobowitz wrote: > > > I just attempted to upgrade a 2.2.2 machine to 2.2.5 kernel, and I ran > > into a little problem. As near as I have been able to tell, the ipfw > > ioctl's changed between the two, causing ipfw to fail and not put in place > > the allow all rules needed to counter the default policy - thus no > > network. > > > > Is my interpretation of this correct? Should I just install 2.2.5 ipfw? > > Installing 2.2.5 ipfw would be enough to fix the problem. But you're > better off remaking everything. I will - just want the kernel functional first. > > (I'm going to make installworld after I get the kernel in, but based on > > past experience I want to do those two seperately.) > > > > Will the 2.2.5 ipfw work with a 2.2.2 kernel at all? > > 2.2.5 ipfw will not work with 2.2.2-RELEASE kernels, but will work with > 2.2.2-STABLE after August 21st. What about /lkm/ipfw_mod.o? Should I upgrade the lkms immediately with kernel or wait until I make world? Does 2.2.5 ipfw use the lkm? It strikes me as a little odd that the lkms are not included in the kernel tree; wouldn't it make more sense to have perhaps /sys/lkm? I'm sure there's a good reason why not, but I don't see what it is. Alex, thank you for your help. From owner-freebsd-stable Tue Dec 2 12:36:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01232 for stable-outgoing; Tue, 2 Dec 1997 12:36:34 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mail.san.rr.com (ns.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01224 for ; Tue, 2 Dec 1997 12:36:31 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dt051n19.san.rr.com [204.210.32.25]) by mail.san.rr.com (8.8.7/8.8.7) with ESMTP id MAA10856; Tue, 2 Dec 1997 12:36:58 -0800 (PST) Message-ID: <34847131.F91E29D8@dal.net> Date: Tue, 02 Dec 1997 12:36:01 -0800 From: Studded X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-11-30-STABLE i386) MIME-Version: 1.0 To: Dan Jacobowitz CC: freebsd-stable@freebsd.org Subject: Re: ipfw between kernel versions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dan Jacobowitz wrote: > > I just attempted to upgrade a 2.2.2 machine to 2.2.5 kernel, and I ran > into a little problem. As near as I have been able to tell, the ipfw > ioctl's changed between the two, causing ipfw to fail and not put in place > the allow all rules needed to counter the default policy - thus no > network. > > Is my interpretation of this correct? Yes. > Should I just install 2.2.5 ipfw? No. > (I'm going to make installworld after I get the kernel in, but based on > past experience I want to do those two seperately.) > > Will the 2.2.5 ipfw work with a 2.2.2 kernel at all? No. I'm not sure what past experience you've had, but everything I've ever read, in addition to vast experience indicates that your best course of action is to make the world, build and install a new kernel, then reboot. In fact, due to the changes in ipfw I highly recommend doing make -DCLOBBER world (in addition to whatever you usually use, -DNOPROFILE is common) because it's possible that the old include files are causing problems during make world to 2.2.5. Another point of possible interest, Alex was kind enough to import the option to make the default ipfw rule "allow" instead of "deny" from -Current, which sounds like it might help you. See LINT for the details. Good luck, Doug From owner-freebsd-stable Tue Dec 2 13:49:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA07257 for stable-outgoing; Tue, 2 Dec 1997 13:49:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA07251 for ; Tue, 2 Dec 1997 13:49:06 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA16339; Wed, 3 Dec 1997 08:48:59 +1100 (EST) Date: Wed, 3 Dec 1997 08:48:58 +1100 (EST) From: "Daniel O'Callaghan" To: Dan Jacobowitz cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw between kernel versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Dec 1997, Dan Jacobowitz wrote: > > 2.2.5 ipfw will not work with 2.2.2-RELEASE kernels, but will work with > > 2.2.2-STABLE after August 21st. > > What about /lkm/ipfw_mod.o? Should I upgrade the lkms immediately with > kernel or wait until I make world? Does 2.2.5 ipfw use the lkm? > > It strikes me as a little odd that the lkms are not included in the kernel > tree; wouldn't it make more sense to have perhaps /sys/lkm? I'm sure > there's a good reason why not, but I don't see what it is. If you build a kernel with IPFIREWALL, the lkm is not used. In 2.2.5 rc.conf and rc.network were changed to so that the lkm will be loaded if required. Since lkms are loaded early in the boot process, they need to be available before /usr and other filesystems are mounted, hence /lkm needs to be in the root partition. Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-stable Tue Dec 2 16:48:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20785 for stable-outgoing; Tue, 2 Dec 1997 16:48:32 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mars.wexpress.com (drow@mars.wexpress.com [205.216.244.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA20766 for ; Tue, 2 Dec 1997 16:48:20 -0800 (PST) (envelope-from drow@chwest.org) Received: from localhost (drow@localhost) by mars.wexpress.com (8.8.8/8.8.5) with SMTP id TAA23654; Tue, 2 Dec 1997 19:46:47 -0500 (EST) Date: Tue, 2 Dec 1997 19:46:47 -0500 (EST) From: Dan Jacobowitz X-Sender: drow@mars.wexpress.com To: Derrick Baumer cc: freebsd-stable@freebsd.org Subject: Re: ipfw between kernel versions In-Reply-To: <199712022144.NAA00472@bduk.dukpad.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You aren't missing anything, but none of those are really an issue. You do occasionally need to update 'config', but unless a serious bug crops up in make or gcc there is no need to upgrade them. The kernel itself builds independently of all libraries and all standard header files; pretty much all source it needs is in /usr/src/sys. On Tue, 2 Dec 1997, Derrick Baumer wrote: > >On Tue, 2 Dec 1997, Alex Nash wrote: > > > >> On Tue, 2 Dec 1997, Dan Jacobowitz wrote: > >> > >I will - just want the kernel functional first. > > > >> > (I'm going to make installworld after I get the kernel in, but based on > >> > past experience I want to do those two seperately.) > etc... > > Been following this for a little while and I'm curious about one thing: > When you remake the world, you're remaking everything, including the > compiler and libraries and everything, right? So if you build the kernel > with your current system, you're not getting the benefits of whatever > (possible) changes have been made to the make program, the compiler, > the libraries, etc... Wouldn't it be better to make world first and > THEN make the kernel with the new stuff? > > Or am I missing something? > > Derrick Baumer > bduk@wave.net From owner-freebsd-stable Wed Dec 3 05:00:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA06330 for stable-outgoing; Wed, 3 Dec 1997 05:00:08 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from roguetrader.com (root@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA06317 for ; Wed, 3 Dec 1997 05:00:05 -0800 (PST) (envelope-from root@roguetrader.com) Received: (from root@localhost) by roguetrader.com (8.8.5/8.8.5) id GAA25953; Wed, 3 Dec 1997 06:00:06 -0700 (MST) Date: Wed, 3 Dec 1997 06:00:06 -0700 (MST) Message-Id: <199712031300.GAA25953@roguetrader.com> Subject: ERRATA NOTICE: FreeBSD 2.2.5-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.5-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/ERRATA.TXT The last update was sent: Sat Nov 8 15:58:56 1997 This update is sent: Wed Dec 3 06:00:05 1997 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o Intel "F00F bug" enables users to hang machines with Pentium processors if they have access to the machine and can compile small C programs. Fix: Update to the 2.2-stable version of the kernel or apply the patch found in: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/updates/f00f.diff.2.2 From owner-freebsd-stable Wed Dec 3 07:20:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15432 for stable-outgoing; Wed, 3 Dec 1997 07:20:50 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from megaweapon.zigg.com (pm378-23.dialip.mich.net [198.110.71.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15416 for ; Wed, 3 Dec 1997 07:20:39 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.7) with SMTP id JAA00679; Wed, 3 Dec 1997 09:36:39 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Wed, 3 Dec 1997 09:36:33 -0500 (EST) From: Matt Behrens To: freebsd-errata-update@roguetrader.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: ERRATA NOTICE: FreeBSD 2.2.5-RELEASE In-Reply-To: <199712031300.GAA25953@roguetrader.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Dec 1997 freebsd-errata-update@roguetrader.com wrote: > o Intel "F00F bug" enables users to hang machines with Pentium processors > if they have access to the machine and can compile small C programs. For accuracy's sake, we should leave out "can compile small C programs". You can bring in programs via ftp very easily that have been compiled on another machine. Otherwise someone might assume that if they have a box with a restricted compiler they're safe. Matt Behrens | Help bring a free realtime communication http://www.zigg.com/ | system to the Internet. Join the NetPager matt@zigg.com | Project! http://www.zigg.com/netpager/ From owner-freebsd-stable Wed Dec 3 15:50:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA24562 for stable-outgoing; Wed, 3 Dec 1997 15:50:36 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA24543 for ; Wed, 3 Dec 1997 15:50:29 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA11980; Wed, 3 Dec 1997 15:49:50 -0800 (PST) To: Matt Behrens cc: freebsd-errata-update@roguetrader.com, freebsd-stable@FreeBSD.ORG Subject: Re: ERRATA NOTICE: FreeBSD 2.2.5-RELEASE In-reply-to: Your message of "Wed, 03 Dec 1997 09:36:33 EST." Date: Wed, 03 Dec 1997 15:49:50 -0800 Message-ID: <11977.881192990@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Fair point - changed. > On Wed, 3 Dec 1997 freebsd-errata-update@roguetrader.com wrote: > > > o Intel "F00F bug" enables users to hang machines with Pentium processors > > if they have access to the machine and can compile small C programs. > > For accuracy's sake, we should leave out "can compile small C programs". > You can bring in programs via ftp very easily that have been compiled on > another machine. Otherwise someone might assume that if they have a box > with a restricted compiler they're safe. > > Matt Behrens | Help bring a free realtime communication > http://www.zigg.com/ | system to the Internet. Join the NetPager > matt@zigg.com | Project! http://www.zigg.com/netpager/ > From owner-freebsd-stable Wed Dec 3 17:00:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29473 for stable-outgoing; Wed, 3 Dec 1997 17:00:00 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from roguetrader.com (root@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29465 for ; Wed, 3 Dec 1997 16:59:57 -0800 (PST) (envelope-from root@roguetrader.com) Received: (from root@localhost) by roguetrader.com (8.8.5/8.8.5) id SAA28095; Wed, 3 Dec 1997 18:00:02 -0700 (MST) Date: Wed, 3 Dec 1997 18:00:02 -0700 (MST) Message-Id: <199712040100.SAA28095@roguetrader.com> Subject: ERRATA NOTICE: FreeBSD 2.2.5-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.5-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/ERRATA.TXT The last update was sent: Tue Dec 2 22:48:12 1997 This update is sent: Wed Dec 3 18:00:02 1997 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: if they have access to the machine and can execute programs. From owner-freebsd-stable Thu Dec 4 07:12:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA27856 for stable-outgoing; Thu, 4 Dec 1997 07:12:12 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-49.ix.netcom.com [207.93.143.177]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA27848 for ; Thu, 4 Dec 1997 07:12:08 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id HAA01752; Thu, 4 Dec 1997 07:12:06 -0800 (PST) Date: Thu, 4 Dec 1997 07:12:06 -0800 (PST) Message-Id: <199712041512.HAA01752@silvia.HIP.Berkeley.EDU> To: stable@freebsd.org Subject: rc564 weirdness From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just noticed that rc564, started with idprio 31, sometimes goes to sleep and doesn't come back after a huge compilation. This is what it looks like now on one of our 2.2-stable (Aug 14 vintage) machines: === >> ps glx UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 569 13352 1 110 -18 19 816 72 vmopar DN ?? 20327:27.01 rc564 569 5730 5728 0 10 0 812 716 wait Ss p0 0:00.89 -bash (bash) 569 9870 5730 1 28 0 624 268 - R+ p0 0:00.00 ps -glx === I'm not sure if you can tell from this, but if I look with "top", the process is not taking up any CPU time anymore, even when the machine is idle. The rc564 binary is on an NFS server (2.2-stable, Oct 31), if that makes any difference. Also, on another machine, I didn't realize that rc564 is still there and started it again, and the second one immediately went to sleep too. I'm not sure if it's waiting on the same thing, I didn't ps glx that one. Satoshi From owner-freebsd-stable Thu Dec 4 12:17:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA24728 for stable-outgoing; Thu, 4 Dec 1997 12:17:42 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from yoshida.com (gateway.yoshida.com [204.203.122.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA24702 for ; Thu, 4 Dec 1997 12:17:36 -0800 (PST) (envelope-from davidc@oiapdx.yoshida.com) Received: by yoshida.com with Novell_GroupWise; Thu, 04 Dec 1997 12:17:14 -0800 Message-ID: <34870FAC.706E@oiapdx.yoshida.com> Date: Thu, 04 Dec 1997 12:16:44 -0800 From: David Chamberlain Organization: Oregon International Airfreight, Inc. X-Mailer: Mozilla 3.04 (WinNT; U) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: make world fails Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Below is an excerpt from my 'make world' log. I am pretty new to this stuff and definatly not a developer. Can anyone help me figure out why this is happening? My sources are from CVSup and the last sup I did was on Dec 2 at 1:00 am from the stable tree. Thanks in Advance David Chamberlain Oregon International Airfreight, Inc. install -c -s -o bin -g bin -m 555 pmap_dump /usr/sbin ===> usr.sbin/ppp install -c -s -o root -g network -m 4550 ppp /usr/sbin *** Error code 67 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- *************************************************************************** * Opinions expressed are my own and * To reply, please remove the spam * * do not represent the opinions of * filter characters from my mail * * any other sane human being. * address * *************************************************************************** From owner-freebsd-stable Thu Dec 4 14:33:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA10553 for stable-outgoing; Thu, 4 Dec 1997 14:33:10 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from gelemna.ft-wayne.in.us (fw4-10.fwi.com [207.202.57.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA10547 for ; Thu, 4 Dec 1997 14:33:05 -0800 (PST) (envelope-from croyle@gelemna.ft-wayne.in.us) Received: (from croyle@localhost) by gelemna.ft-wayne.in.us (8.8.8/8.8.5) id RAA04195; Thu, 4 Dec 1997 17:33:32 -0500 (EST) To: freebsd-stable@FreeBSD.ORG Subject: Re: make world fails References: <34870FAC.706E@oiapdx.yoshida.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Don Croyle Date: 04 Dec 1997 17:33:31 -0500 Organization: Minimal at best In-Reply-To: David Chamberlain's message of "Thu, 04 Dec 1997 12:16:44 -0800" Message-ID: <86sos8rb5w.fsf@gelemna.ft-wayne.in.us> Lines: 24 X-Mailer: Quassia Gnus v0.17/XEmacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David Chamberlain writes: > Below is an excerpt from my 'make world' log. I am pretty new to this > stuff and definatly not a developer. Can anyone help me figure out why > this is happening? My sources are from CVSup and the last sup I did was > on Dec 2 at 1:00 am from the stable tree. > install -c -s -o bin -g bin -m 555 pmap_dump /usr/sbin > ===> usr.sbin/ppp > install -c -s -o root -g network -m 4550 ppp /usr/sbin > *** Error code 67 You need to add: network:*:69: to /etc/group. It would probably be a good idea to go through /usr/src/etc in general and merge the changes into /etc. It isn't done automatically because blindly updating possibly customized configuration files would be asking for trouble. -- I've always wanted to be a dilettante, | Usenet II -- because but I've never quite been ready to make | it's time for October the commitment. | http://www.usenet2.org From owner-freebsd-stable Thu Dec 4 16:54:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20885 for stable-outgoing; Thu, 4 Dec 1997 16:54:22 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mars.wexpress.com (drow@mars.wexpress.com [205.216.244.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA20874 for ; Thu, 4 Dec 1997 16:54:13 -0800 (PST) (envelope-from drow@chwest.org) Received: from localhost (drow@localhost) by mars.wexpress.com (8.8.8/8.8.5) with SMTP id TAA04104 for ; Thu, 4 Dec 1997 19:52:46 -0500 (EST) Date: Thu, 4 Dec 1997 19:52:46 -0500 (EST) From: Dan Jacobowitz X-Sender: drow@mars.wexpress.com To: freebsd-stable@freebsd.org Subject: pine and pico in make worl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For some reason, make world seems to be automatically installing a wierd version of pine/pico; it's 3.95LJsomething, and the first status message is garbled in what I think are an extended character set. After that status messages are English. Installing 3.96 fixes the problem. From owner-freebsd-stable Thu Dec 4 18:23:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA28609 for stable-outgoing; Thu, 4 Dec 1997 18:23:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from megaweapon.zigg.com (tcgr-210.dialup.alliance.net [207.74.43.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA28598 for ; Thu, 4 Dec 1997 18:23:34 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.7) with SMTP id VAA17217; Thu, 4 Dec 1997 21:23:52 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Thu, 4 Dec 1997 21:23:52 -0500 (EST) From: Matt Behrens Reply-To: Matt Behrens To: Dan Jacobowitz cc: freebsd-stable@freebsd.org Subject: Re: pine and pico in make worl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 4 Dec 1997, Dan Jacobowitz wrote: > For some reason, make world seems to be automatically installing a wierd > version of pine/pico; it's 3.95LJsomething, and the first status message > is garbled in what I think are an extended character set. After that > status messages are English. That can't be; pine & pico are ports, not in the -STABLE build... Matt Behrens | Support the anti-spam amendment! http://www.zigg.com/ | Visit http://www.cauce.org/ From owner-freebsd-stable Thu Dec 4 18:37:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29520 for stable-outgoing; Thu, 4 Dec 1997 18:37:11 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mars.wexpress.com (drow@mars.wexpress.com [205.216.244.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA29513 for ; Thu, 4 Dec 1997 18:37:05 -0800 (PST) (envelope-from drow@chwest.org) Received: from localhost (drow@localhost) by mars.wexpress.com (8.8.8/8.8.5) with SMTP id VAA04694; Thu, 4 Dec 1997 21:35:25 -0500 (EST) Date: Thu, 4 Dec 1997 21:35:25 -0500 (EST) From: Dan Jacobowitz X-Sender: drow@mars.wexpress.com To: Derrick Baumer cc: freebsd-stable@freebsd.org Subject: Re: pine and pico in make world In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ditto to those who've replied - no, it is not in make world. None the less, the problem manifested immediately after a make world. Any ideas? Apparently the version of pico itself is unchanged, I stand corrected; none the less, what could have caused it to suddenly switch languages temporarily? It was not a fluke; the same thing happened each use. On Thu, 4 Dec 1997, Derrick Baumer wrote: > > On Thu, 4 Dec 1997, Dan Jacobowitz wrote: > > > > > For some reason, make world seems to be automatically installing a wierd > > version of pine/pico; it's 3.95LJsomething, and the first status message > > is garbled in what I think are an extended character set. After that > > status messages are English. > > > > Installing 3.96 fixes the problem. > > > > Is pine installed by make world? I had to install pine via the ports > collection. I don't think pine comes as part of the source tree, does it? > > Derrick Baumer > bduk@wave.net > > From owner-freebsd-stable Thu Dec 4 20:05:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08870 for stable-outgoing; Thu, 4 Dec 1997 20:05:45 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mars.wexpress.com (drow@mars.wexpress.com [205.216.244.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA08855 for ; Thu, 4 Dec 1997 20:05:37 -0800 (PST) (envelope-from drow@chwest.org) Received: from localhost (drow@localhost) by mars.wexpress.com (8.8.8/8.8.5) with SMTP id XAA05472 for ; Thu, 4 Dec 1997 23:03:46 -0500 (EST) Date: Thu, 4 Dec 1997 23:03:46 -0500 (EST) From: Dan Jacobowitz X-Sender: drow@mars.wexpress.com To: freebsd-stable@freebsd.org Subject: Perl and setuid scripts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the perl documentation it constantly refers to how certain BSDs set shell scripts to non-suid due to insecurity. Having browsed the relevant (I think) portions of kern_exec.c and imgact_shell.c, I do not think FreeBSD is one of them. Right? That would go along with the fact that perl is apparently built without the suid emulation (-DDOSUID). BUT - as soon as I made world, overwriting my former perl - first a 4.0 which came with FreeBSD 2.2.2 however that was compiled, and then a 5.004 built with -DDOSUID against the advice of the Configure program's freebsd default - with the2.2.5 copy of 4.0 built without -DDOSUID, suid perl scripts completely stopped working. What the heck am I missing here? The script is definitely NOT being run setuid ($< == $> == my-real-id-not-the-scripts-suid). Is something broken, or am I just blind and confused? From owner-freebsd-stable Fri Dec 5 07:05:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02952 for stable-outgoing; Fri, 5 Dec 1997 07:05:52 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02945 for ; Fri, 5 Dec 1997 07:05:48 -0800 (PST) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id KAA01661; Fri, 5 Dec 1997 10:03:01 -0500 (EST) Date: Fri, 5 Dec 1997 10:03:01 -0500 (EST) From: Charles Owens To: Dan Jacobowitz cc: freebsd-stable@FreeBSD.ORG Subject: Re: Perl and setuid scripts In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 4 Dec 1997, Dan Jacobowitz wrote: > > In the perl documentation it constantly refers to how certain BSDs set > shell scripts to non-suid due to insecurity. Having browsed the relevant > (I think) portions of kern_exec.c and imgact_shell.c, I do not think > FreeBSD is one of them. > > Right? > > That would go along with the fact that perl is apparently built without > the suid emulation (-DDOSUID). > > BUT - as soon as I made world, overwriting my former perl - first a 4.0 > which came with FreeBSD 2.2.2 however that was compiled, and then a 5.004 > built with -DDOSUID against the advice of the Configure program's freebsd > default - with the2.2.5 copy of 4.0 built without -DDOSUID, suid perl > scripts completely stopped working. > > What the heck am I missing here? The script is definitely NOT being run > setuid ($< == $> == my-real-id-not-the-scripts-suid). Is something > broken, or am I just blind and confused? I've had to mess with this a few times myself, with varying degrees of annoyance. Just this week, on a 2.2-970618-RELENG system I noticed that suid perl scripts were not working. I was using Perl 5.003 from the 2.2 packages. To get past this I built Perl 5.004 in the ports tree. Just did a plain make;make install. Suid scripts are working fine again. I seem to recall that 4.0 had some security issues, so suid scripts are now deliverately not supported for it. Did you build your 5.004 manually or in the ports tree? The port includes a number of setuid-related patches that I'm guessing are needed for the feature to work. Good luck, --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-stable Sat Dec 6 00:28:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA00611 for stable-outgoing; Sat, 6 Dec 1997 00:28:13 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from dt051n19.san.rr.com (dt051n19.san.rr.com [204.210.32.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA00599 for ; Sat, 6 Dec 1997 00:28:07 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (localhost [127.0.0.1]) by dt051n19.san.rr.com (8.8.8/8.8.8) with ESMTP id AAA01105; Sat, 6 Dec 1997 00:28:04 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <34890C94.972D09DC@dal.net> Date: Sat, 06 Dec 1997 00:28:04 -0800 From: Studded X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Interested in patches for dhcp in rc.*? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A lot of people have been asking about our support for DHCP, and as cable modems become more popular, I think that those requests will increase. I use one, and I've been working on integrating it into my system. I've got things going basically the way I want them, and it occured to me that adding options for it into rc.conf and rc.network would be useful. I can hack the scripts and submit patches, but before I do the work I wanted to check on whether it has a reasonable chance of being committed. I was planning on putting something to the effect of dhcp_client_enable (yes/no) and dhcp_client_args (pathname and arguments) in the "Network daemon" section of rc.conf, and putting the check for it first in rc.network since if you don't run it first some of the things in rc.network will conflict. I'd also be interested in suggestions for other/better ways to handle it. One reason for not including something like this would be that it's not actually part of our distribution, and I don't see anything else in rc.conf that falls into that category. OTOH, this isn't something that runs properly if it's placed in rc.local. If you are thinking of incorporating one into the FreeBSD distribution, I'd like to highly recommend the ISC stuff. They guy that's working on DHCP for ISC has been very helpful, and shows interest in making what has been a linux-dominated project more friendly to FreeBSD. (Thanks also to Justin Seeger for maintaining our port of it.) They are in a "just about to be beta" stage right now, and actively soliciting suggestions. The only thing I have use for is the client, but if some of y'all wanted to try out the other parts of the package (server, client, relay, statmsg, sysconfd) and let them know where there are FreeBSD difficulties I'm sure they'd appreciate it. For more info, check out http://www.isc.org/dhcp-dev.html. Looking forward to your comments, Doug From owner-freebsd-stable Sat Dec 6 01:24:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA03491 for stable-outgoing; Sat, 6 Dec 1997 01:24:27 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA03486 for ; Sat, 6 Dec 1997 01:24:24 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA19869; Sat, 6 Dec 1997 01:24:32 -0800 (PST) To: Studded cc: freebsd-stable@FreeBSD.ORG Subject: Re: Interested in patches for dhcp in rc.*? In-reply-to: Your message of "Sat, 06 Dec 1997 00:28:04 PST." <34890C94.972D09DC@dal.net> Date: Sat, 06 Dec 1997 01:24:32 -0800 Message-ID: <19865.881400272@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > A lot of people have been asking about our support for DHCP, and as Yep! > system. I've got things going basically the way I want them, and it > occured to me that adding options for it into rc.conf and rc.network > would be useful. I can hack the scripts and submit patches, but before I > do the work I wanted to check on whether it has a reasonable chance of > being committed. Well, it's a multi-dimensional problem. The first part is bringing dhcp support into the system, perhaps using the NetBSD version as a starting point (though their makefiles are a little different, having the ability to mix the subdir and port/lib includes the way they do - envy :). Then the dhcp client libraries will intrinsically be available to things like sysinstall, which could use it to support dhcp configuration of all the IP values during installation. :) Then you add all the rc glue to use it and voila, you're done! When can you start? :-) Jordan From owner-freebsd-stable Sat Dec 6 02:16:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA06010 for stable-outgoing; Sat, 6 Dec 1997 02:16:55 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA06005 for ; Sat, 6 Dec 1997 02:16:49 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dt051n19.san.rr.com [204.210.32.25]) by mail.san.rr.com (8.8.7/8.8.7) with ESMTP id CAA25580; Sat, 6 Dec 1997 02:16:30 -0800 (PST) Message-ID: <348925A4.72009EBC@dal.net> Date: Sat, 06 Dec 1997 02:15:00 -0800 From: Studded X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: freebsd-stable@FreeBSD.ORG Subject: Re: Interested in patches for dhcp in rc.*? References: <19865.881400272@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > Well, it's a multi-dimensional problem. The first part is bringing > dhcp support into the system, If you want to make this the first step, then I will retreat into the background again (on this issue anyway :). I have no C coding ability, but sh is within my range. My thinking was that since we have two good clients in the ports collection, it might be useful to make things easier for people to incorporate it into their systems. > perhaps using the NetBSD version as a > starting point (though their makefiles are a little different, having > the ability to mix the subdir and port/lib includes the way they do - > envy :). Then the dhcp client libraries will intrinsically be > available to things like sysinstall, which could use it to support > dhcp configuration of all the IP values during installation. :) I'm not familiar with netbsd. FWIW, as far as I can tell there are no dhclient libs with the ISC version, and the client is about 90k when stripped, but that includes support for numerous options that wouldn't be needed for sysinstall. > Then you add all the rc glue to use it and voila, you're done! > When can you start? :-) Hehehe.. I wish I could help with actual code. I did send in some improvements for the FreeBSD version of the ISC's dhclient script, and Justin sent in the patches from our port which they guy from ISC indicated to me would likely be included. Putting the options in rc.network aren't terribly urgent, since as long as you get all the options right starting dhclient from rc.local works. My goal is to reduce the frustration for those coming after me, but I won't pass up a more complete solution. :) Thanks for the response, Doug From owner-freebsd-stable Sat Dec 6 04:12:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA13226 for stable-outgoing; Sat, 6 Dec 1997 04:12:33 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from cycu.edu.tw (sunss106.cc.cycu.edu.tw [140.135.18.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA13213 for ; Sat, 6 Dec 1997 04:12:23 -0800 (PST) (envelope-from sxxxxxxx@sunss106.cc.cycu.edu.tw) Received: from cchp15.cc.cycu.edu.tw ([140.135.153.115]) by cycu.edu.tw (8.8.7/8.8.7) with ESMTP id UAA17354 for ; Sat, 6 Dec 1997 20:12:49 +0800 (CST) Message-ID: <34893DCF.626F6978@mbox.cycu.edu.tw> Date: Sat, 06 Dec 1997 19:58:07 +0800 From: "B06機房" Organization: 中原大學電算中心 X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: joint the party X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I want to join the party of you...freebsd group..and please do mail me list about the freebsd matter or news. Thank you very much...see ya. From owner-freebsd-stable Sat Dec 6 10:49:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA05615 for stable-outgoing; Sat, 6 Dec 1997 10:49:08 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA05610 for ; Sat, 6 Dec 1997 10:49:04 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dt051n19.san.rr.com [204.210.32.25]) by mail.san.rr.com (8.8.7/8.8.7) with ESMTP id KAA00157; Sat, 6 Dec 1997 10:49:26 -0800 (PST) Message-ID: <34899DD9.21955D8B@dal.net> Date: Sat, 06 Dec 1997 10:47:53 -0800 From: Studded X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: Nate Williams CC: freebsd-stable@freebsd.org Subject: Re: Interested in patches for dhcp in rc.*? References: <34890C94.972D09DC@dal.net> <199712061804.LAA06159@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > > A lot of people have been asking about our support for DHCP, and as > > cable modems become more popular, I think that those requests will > > increase. I use one, and I've been working on integrating it into my > > system. I've got things going basically the way I want them, and it > > occured to me that adding options for it into rc.conf and rc.network > > would be useful. > > Would it be possible to have the ISC/DHCP port 'patch' the system easily > for these kinds of things, or better yet add a new 'rc' file that gets > run *after* rc.conf but before rc.network, thereby relying less on > FreeBSD's changing file? Unless I'm missing something, this would involve patching rc instead of rc.network, which seemed to me to be a more serious thing. In either case, you'd still want an option to prevent it from loading, since you don't always want to bring it up on boot. My thinking was to keep the dhcp_client options in rc.conf very generic so that at some point in the future when we integrate it into the base system, rc.conf won't have to be changed. > Then, you'd have the best of both worlds, the > ability to keep the 'base' stuff clean from non-existant FreeBSD > sources, and also the flexibility of being able to have the new > functionality at boot time. I did note the concern regarding including options for things that are not part of FreeBSD in my original post. The use of dhcp is growing in popularity, so I thought it would be nice to get out ahead of the curve with scripting hooks now that could be tied into later when we have sources in the tree. > Ff/when DHCP gets integrated into the tree I think it should get 'hooks' > in the standard files. Agreed. Doug From owner-freebsd-stable Sat Dec 6 11:23:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07321 for stable-outgoing; Sat, 6 Dec 1997 11:23:02 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from lynx.syix.com (root@ns1.syix.com [206.245.231.9] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07314 for ; Sat, 6 Dec 1997 11:22:54 -0800 (PST) (envelope-from dave@syix.com) Received: from cage.syix.com (cage.syix.com [209.60.182.130]) by lynx.syix.com (8.8.8/8.8.7) with SMTP id LAA21588 for ; Sat, 6 Dec 1997 11:22:52 -0800 (PST) Message-Id: <3.0.2.32.19971206112246.008bb5a0@syix.com> X-Sender: dave@syix.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Sat, 06 Dec 1997 11:22:46 -0800 To: freebsd-stable@freebsd.org From: Dave Overton Subject: Make World Fails Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am rather new to the FBSD world, but not so new to BSD... Anyway, I have ran a make world after doing a "cvsup stable-supfile", all went along fine for a while, then it did this.... cc -O -I/usr/src/gnu/usr.bin/awk -DGAWK -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/awk/builtin.c /usr/src/gnu/usr.bin/awk/builtin.c: In function `sub_common': /usr/src/gnu/usr.bin/awk/builtin.c:1123: `researc' undeclared (first use this function) /usr/src/gnu/usr.bin/awk/builtin.c:1123: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/awk/builtin.c:1123: for each function it appears in.) /usr/src/gnu/usr.bin/awk/builtin.c:1123: parse error at null character *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. What are the "un-official" ways to fix this error, or ones like it? What do I do next? I figured my options are: 1. Dig around in builtin.c and see what is wrong. 2. re-cvsup and hope that its fixed since 2 am this morning 3. send some weird undocumented or hidden command (or series of commands) that I would only know if I had been reading this list since day one. (only been reading it a few days) HELP! BTW, although much of FBSD is easy to work with, I find a bit of it VERY confusing to a new user. Try for instance setting up a ccd0 spool the first time, or adding an additional hard drive WITHOUT mount points defined.... (like for a ccd0 news spool) Dave Overton dave@syix.com http://www.syix.com/ Voice 916-751-8873 Fax 916-751-8871 Premier Internet to Yuba/Sutter/Butte/Colusa Counties, California From owner-freebsd-stable Sat Dec 6 15:10:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22521 for stable-outgoing; Sat, 6 Dec 1997 15:10:43 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA22509 for ; Sat, 6 Dec 1997 15:10:38 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA08460 for ; Sat, 6 Dec 1997 16:10:36 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA06830; Sat, 6 Dec 1997 16:10:35 -0700 Date: Sat, 6 Dec 1997 16:10:35 -0700 Message-Id: <199712062310.QAA06830@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@freebsd.org Subject: Re: Interested in patches for dhcp in rc.*? X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try again after hub rejected things... ------- start of forwarded message ------- From: Nate Williams To: Studded Date: Sat, 6 Dec 1997 11:04:11 -0700 > A lot of people have been asking about our support for DHCP, and as > cable modems become more popular, I think that those requests will > increase. I use one, and I've been working on integrating it into my > system. I've got things going basically the way I want them, and it > occured to me that adding options for it into rc.conf and rc.network > would be useful. Would it be possible to have the ISC/DHCP port 'patch' the system easily for these kinds of things, or better yet add a new 'rc' file that gets run *after* rc.conf but before rc.network, thereby relying less on FreeBSD's changing file? Then, you'd have the best of both worlds, the ability to keep the 'base' stuff clean from non-existant FreeBSD sources, and also the flexibility of being able to have the new functionality at boot time. Ff/when DHCP gets integrated into the tree I think it should get 'hooks' in the standard files. Nate ------- end of forwarded message ------- From owner-freebsd-stable Sat Dec 6 17:08:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01528 for stable-outgoing; Sat, 6 Dec 1997 17:08:59 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from argon.linkzone.com (argon.linkzone.com [204.182.59.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01522 for ; Sat, 6 Dec 1997 17:08:56 -0800 (PST) (envelope-from mlt@linkzone.com) Received: from localhost (mlt@localhost) by argon.linkzone.com (8.8.5/8.8.5) with SMTP id SAA26700 for ; Sat, 6 Dec 1997 18:04:13 GMT Date: Sat, 6 Dec 1997 18:04:13 +0000 (GMT) From: Mark Turrin To: freebsd-stable Subject: Getting anonymous ftp to work Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm having trouble getting the anonymous ftp function to work. Regular ftp for individual users works fine but anonymous does not. I'm running 2.2.2 Here's the session: $ ftp argon Connected to argon.linkzone.com. 220- Hi and welcome to the ftp archive of chaos 220 argon.linkzone.com FTP server (Version 6.00) ready. Name (argon:mlt): anonymous 331 Guest login ok, send your email address as password. Password: 550 Can't set guest privileges. Login failed. ftp> I tried setting this up using the sysinstall program in /stand but still no luck. It outputs the files and the anonymous chroot directory but "she no worky". Getting the following errors in the /var/log/message file when attempting anonymous ftp access: Dec 6 17:56:21 argon inetd[26676]: login_getclass: unknown class 'root' Dec 6 17:56:57 argon inetd[26681]: login_getclass: unknown class 'root' Dec 6 17:57:15 argon ftpd[26681]: login_getclass: unknown class 'root' Any help appreciated. ___________________________________________________________________ Mark L. Turrin Drag me, drop me, treat me like an object! mlt@linkzone.com From owner-freebsd-stable Sat Dec 6 17:49:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04176 for stable-outgoing; Sat, 6 Dec 1997 17:49:32 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04171 for ; Sat, 6 Dec 1997 17:49:29 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id RAA02290; Sat, 6 Dec 1997 17:49:16 -0800 (PST) (envelope-from jdp) Message-Id: <199712070149.RAA02290@austin.polstra.com> To: dave@syix.com Subject: Re: Make World Fails In-Reply-To: <3.0.2.32.19971206112246.008bb5a0@syix.com> References: <3.0.2.32.19971206112246.008bb5a0@syix.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Sat, 06 Dec 1997 17:49:15 -0800 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <3.0.2.32.19971206112246.008bb5a0@syix.com>, Dave Overton wrote: > I am rather new to the FBSD world, but not so new to BSD... Anyway, I have > ran a make world after doing a "cvsup stable-supfile", all went along fine > for a while, then it did this.... > > cc -O -I/usr/src/gnu/usr.bin/awk -DGAWK > -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/awk/builtin.c > /usr/src/gnu/usr.bin/awk/builtin.c: In function `sub_common': > /usr/src/gnu/usr.bin/awk/builtin.c:1123: `researc' undeclared (first use > this function) > /usr/src/gnu/usr.bin/awk/builtin.c:1123: (Each undeclared identifier is > reported only once > /usr/src/gnu/usr.bin/awk/builtin.c:1123: for each function it appears in.) > /usr/src/gnu/usr.bin/awk/builtin.c:1123: parse error at null character Your file is corrupted. Have you been seeing any signs of disk errors or filesystem problems or RAM problems? I'd run fsck if I were you. Please move the bad file to someplace safe, then run cvsup again. If the new one comes out the same, let me know and I'll check up on whatever mirror site you're updating from. But I strongly suspect that the problem is in your system rather than at the mirror site, because of the MD5 checksumming that CVSup does. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Sat Dec 6 18:24:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06538 for stable-outgoing; Sat, 6 Dec 1997 18:24:00 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06524 for ; Sat, 6 Dec 1997 18:23:53 -0800 (PST) (envelope-from arg1197@arg1.demon.co.uk) Received: from rocket.arg.sj.co.uk (server.arg.sj.co.uk [10.5.0.1]) by arg1.demon.co.uk (8.8.5/8.8.5) with SMTP id CAA20637; Sun, 7 Dec 1997 02:23:47 GMT Message-ID: <348A088E.167EB0E7@arg1.demon.co.uk> Date: Sun, 07 Dec 1997 02:23:10 +0000 From: Andrew Gordon X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: kern/2573 - NFS hangs with mmap() Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The above PR - apparently fixed in current a long time ago - still appears to be present in 2.2-stable. Any advice would be appreciated - I don't know how to find the changes that corresponded to the closing of the PR with a view to putting them in 2.2 (other than doing a brute force search of the CVS repository for likely checkin messages). From owner-freebsd-stable Sat Dec 6 18:31:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07316 for stable-outgoing; Sat, 6 Dec 1997 18:31:53 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA07299 for ; Sat, 6 Dec 1997 18:31:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xeWVU-0000MY-00; Sat, 6 Dec 1997 18:31:44 -0800 Date: Sat, 6 Dec 1997 18:31:41 -0800 (PST) From: Tom To: Mark Turrin cc: freebsd-stable Subject: Re: Getting anonymous ftp to work In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 6 Dec 1997, Mark Turrin wrote: > Hello, > > I'm having trouble getting the anonymous ftp function to work. Regular > ftp for individual users works fine but anonymous does not. Belongs on the freebsd-questions list... ...but you probably do not have a user called "ftp". You should make one, and set this users home directory to your anon area. Tom From owner-freebsd-stable Sat Dec 6 19:55:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA11733 for stable-outgoing; Sat, 6 Dec 1997 19:55:50 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from lynx.syix.com (root@206-245-231-9.ipv4.intur.net [206.245.231.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA11727 for ; Sat, 6 Dec 1997 19:55:46 -0800 (PST) (envelope-from dave@syix.com) Received: from cage.syix.com (cage.syix.com [209.60.182.130]) by lynx.syix.com (8.8.8/8.8.7) with SMTP id TAA07725 for ; Sat, 6 Dec 1997 19:55:46 -0800 (PST) Message-Id: <3.0.2.32.19971206195010.00b0c670@syix.com> X-Sender: dave@syix.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Sat, 06 Dec 1997 19:50:10 -0800 To: stable@FreeBSD.ORG From: Dave Overton Subject: Re: Make World Fails In-Reply-To: <199712070149.RAA02290@austin.polstra.com> References: <3.0.2.32.19971206112246.008bb5a0@syix.com> <3.0.2.32.19971206112246.008bb5a0@syix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 05:49 PM 12/6/97 -0800, you wrote: >In article <3.0.2.32.19971206112246.008bb5a0@syix.com>, >Dave Overton wrote: >> I am rather new to the FBSD world, but not so new to BSD... Anyway, I have >> ran a make world after doing a "cvsup stable-supfile", all went along fine >> for a while, then it did this.... >> >> cc -O -I/usr/src/gnu/usr.bin/awk -DGAWK >> -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/awk/builtin.c >> /usr/src/gnu/usr.bin/awk/builtin.c: In function `sub_common': >> /usr/src/gnu/usr.bin/awk/builtin.c:1123: `researc' undeclared (first use >> this function) >> /usr/src/gnu/usr.bin/awk/builtin.c:1123: (Each undeclared identifier is >> reported only once >> /usr/src/gnu/usr.bin/awk/builtin.c:1123: for each function it appears in.) >> /usr/src/gnu/usr.bin/awk/builtin.c:1123: parse error at null character > >Your file is corrupted. Have you been seeing any signs of disk errors >or filesystem problems or RAM problems? I'd run fsck if I were you. > >Please move the bad file to someplace safe, then run cvsup again. >If the new one comes out the same, let me know and I'll check up on >whatever mirror site you're updating from. But I strongly suspect >that the problem is in your system rather than at the mirror site, >because of the MD5 checksumming that CVSup does. > Thanks to all of you that took time to answer my stupid (after you told me what was wrong...) question. For info, the file was corrupted, it had the right date and size, just a bunch of NULL characters in it, about the middle of line 1123 to about line 1130... Just ftp'd another copy of it, overwrote it, and started the make world again, and all went fine. (except the wait of course) Disk will be fsck'd later, when I can touch the machine if it fails. Thanks again! Dave Dave Overton dave@syix.com http://www.syix.com/ Voice 916-751-8873 Fax 916-751-8871 Premier Internet to Yuba/Sutter/Butte/Colusa Counties, California From owner-freebsd-stable Sat Dec 6 23:44:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24530 for stable-outgoing; Sat, 6 Dec 1997 23:44:07 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24520 for ; Sat, 6 Dec 1997 23:44:01 -0800 (PST) (envelope-from mark@quickweb.com) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id CAA09936; Sun, 7 Dec 1997 02:45:36 -0500 (EST) Message-ID: <19971207024536.62366@vmunix.com> Date: Sun, 7 Dec 1997 02:45:36 -0500 From: Mark Mayo To: freebsd-stable@freebsd.org Subject: -stable kernel on sept. system? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I have a system that was installed from a September 25 2.2-SNAP, and then cvsup'ed to -stable on the 26th (including a make world). I'd like to update the kernel with the latest from -RELENG_2_2 to get the LAND bug fix, etc. The machine is literally in the middle of nowhere (the artic circle) so getting to it is difficult and I'd have to install the kernel remotely and reboot the machine from 1000km away.... Needless to say, minimizing the chance of a problem with a new kernel is fairly important :-) So I'm wondering if I'll have any problems if I mix a -stable kernel with a 2 month old system? Will I need to rebuild any LKMs or things like ps, w, and so on?? I'm really hoping to be able to just "drop in" the new kernel and be done with it! :-) TIA for any suggestions, -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU