From owner-freebsd-current Sun May 7 02:11:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA12107 for current-outgoing; Sun, 7 May 1995 02:11:12 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA12084 ; Sun, 7 May 1995 02:10:45 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id LAA00256; Sun, 7 May 1995 11:10:23 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id LAA00363; Sun, 7 May 1995 11:10:19 +0200 Message-Id: <199505070910.LAA00363@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org, security@FreeBSD.org Subject: NIS/Kerberos has some strange behaviour... Date: Sun, 07 May 1995 11:10:19 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk Hi (Bill & Garrett) and the rest I have been messing around with Kerberos and NIS for a while now trying to get them to behave, and I have got them 90% co-operating. I have just one problem: When a pleb user tries to log in on a machine that is both a Kerberos client and a NIS client, that user cannot log in using their NIS password. Strangely, the Kerberos password works! Most other NIS functions (ypcat, ypwhich, ypmatch etc) work, but passwd -y does not. On the Kerberos/NIS server, all is well. Kerberos behaves well on both machines. On the client, ypbind -s is run. On the server I run ypserv -dns, yppasswdd -s -f(I prefer to use /etc/master.passwd) and ypserv -s. Any ideas? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sun May 7 02:46:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA13191 for current-outgoing; Sun, 7 May 1995 02:46:22 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA13115 for ; Sun, 7 May 1995 02:43:31 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id TAA28473; Sun, 7 May 1995 19:37:45 +1000 From: michael butler Message-Id: <199505070937.TAA28473@asstdc.scgt.oz.au> Subject: Re: SCSI drive auto error reallocation To: dufault@hda.com (Peter Dufault) Date: Sun, 7 May 1995 19:37:44 +1000 (EST) Cc: current@FreeBSD.org In-Reply-To: <199505061316.JAA15015@hda.com> from "Peter Dufault" at May 6, 95 09:16:23 am Reply-To: imb@scgt.oz.au X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1439 Sender: current-owner@FreeBSD.org Precedence: bulk Peter Dufault writes: > The newest version of "scsi" lets you edit your mode pages. Now that I've > added that you may want to check to see if you have automatic read and > write reallocation enabled. I have three SCSI drives and none did. Nor did mine .. however, I can understand wishing to dynamically reallocate on write failures, but reads ? > The command is "scsi -f /dev/rsd?c -m 1" to dump mode page 1 .. On an ISA machine (running -current, 7/7/95, BusLogic 542B, OLD firmware) this can cause .. May 7 17:46:50 asstdc /kernel: aha0: DMA beyond end Of ISA May 7 17:46:50 asstdc /kernel: biodone: buffer already done .. needless to say the ioctl fails. Not fatal, but interesting. > > hda# scsi -f /dev/rsd2c -m 1 > > AWRE (Auto Write Reallocation Enbld): 1 > > ARRE (Auto Read Reallocation Enbld): 1 > > TB (Transfer Block): 1 > > RC (Read Continuous): 0 > > EER (Enable Early Recovery): 1 > > PER (Post Error): 0 > > DTE (Disable Transfer on Error): 0 > > DCR (Disable Correction): 0 > > Read Retry Count: 18 > > Correction Span: 11 > > Head Offset Count: 0 > > Data Strobe Offset Count: 0 > > Write Retry Count: 18 > > Recovery Time Limit: 0 > If AWRE and ARRE are 0 you want to run the command with the "-e -P 3" > switches to permanently enable read and write reallocation. Could someone please explain 'TB' and 'EER' which seem to differ from teh above on a drive here ? michael From owner-freebsd-current Sun May 7 14:59:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03852 for current-outgoing; Sun, 7 May 1995 14:59:43 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03840 ; Sun, 7 May 1995 14:59:17 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id XAA01030; Sun, 7 May 1995 23:59:04 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id XAA02865; Sun, 7 May 1995 23:59:03 +0200 Message-Id: <199505072159.XAA02865@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org, core@FreeBSD.org Subject: How to roll a release... Date: Sun, 07 May 1995 23:59:03 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk Hi Guys... When 2.0.5-ALPHA/BETA/RELEASE comes out, I'd kinda like to be up to date with local secure tarballs. I've been looking at the release/Makefile, and so far it looks easy. I have some questions though: 1) Is buildname set to the name of the distribution, like FreeBSD-2.0.5-RELEASE? 2) I am going to copy -Rp the sources instead of using cvs. Any problems likely to crop up? 3) Is there anything else I need to know? Apart from 'it will take ar _loooong_ time' :-) 4) Could someone please keep me in touch with when the actual releases get rolled so I can run mine at the same/similar time? Thanks! -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sun May 7 15:09:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA04105 for current-outgoing; Sun, 7 May 1995 15:09:13 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA04090 ; Sun, 7 May 1995 15:09:12 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA10935; Sun, 7 May 1995 15:08:24 -0700 From: Poul-Henning Kamp Message-Id: <199505072208.PAA10935@ref.tfs.com> Subject: Re: How to roll a release... To: mark@grondar.za (Mark Murray) Date: Sun, 7 May 1995 15:08:23 -0700 (PDT) Cc: current@FreeBSD.org, core@FreeBSD.org In-Reply-To: <199505072159.XAA02865@grumble.grondar.za> from "Mark Murray" at May 7, 95 11:59:03 pm Content-Type: text Content-Length: 652 Sender: current-owner@FreeBSD.org Precedence: bulk > 1) Is buildname set to the name of the distribution, like > FreeBSD-2.0.5-RELEASE? yes. 2.0.5-RELEASE? > 2) I am going to copy -Rp the sources instead of using cvs. Any problems > likely to crop up? yes, no. > 3) Is there anything else I need to know? Apart from 'it will take ar > _loooong_ time' :-) 6-20 hours. > 4) Could someone please keep me in touch with when the actual releases get > rolled so I can run mine at the same/similar time? Jordan ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Mon May 8 10:05:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA04869 for current-outgoing; Mon, 8 May 1995 10:05:36 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA04862 for ; Mon, 8 May 1995 10:05:27 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA13096; Mon, 8 May 95 19:04:36 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id TAA08204 for freebsd-current@freefall.cdrom.com; Mon, 8 May 1995 19:16:07 +0200 Date: Mon, 8 May 1995 19:16:07 +0200 From: "Christoph P. Kukulies" Message-Id: <199505081716.TAA08204@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: elm 2.4 port Sender: current-owner@FreeBSD.org Precedence: bulk /usr/ports/mail/elm/work/filter/Makefile has a leading at the beginning of the line following the all: target which breaks make. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Mon May 8 19:58:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01211 for current-outgoing; Mon, 8 May 1995 19:58:29 -0700 Received: from grep.cs.fsu.edu (grep.cs.fsu.edu [128.186.121.152]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA01205 for ; Mon, 8 May 1995 19:58:24 -0700 Received: by grep.cs.fsu.edu (8.6.9/56) id WAA05318; Mon, 8 May 1995 22:58:18 -0400 Date: Mon, 8 May 1995 22:58:18 -0400 From: Gang-Ryung Uh Message-Id: <199505090258.WAA05318@grep.cs.fsu.edu> To: current@FreeBSD.org Subject: DOS partition!! Cc: uh@grep.cs.fsu.edu Sender: current-owner@FreeBSD.org Precedence: bulk Recently, I upgraded FreeBSD from 2.0R to current (May 7). After I did 'make world' & rebuilt the kernel and reboot with the new kernel, I got the following message during the boot. (Obviously I did disk slicing with FreeBSD 2.0R). sd0s1: type 0x6, start 32, end = 819199, size 819168 : OK sd0s2: type 0xa5, start 819200, end = 2074623, size 1255424 : OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 819200, end 2074623, size 1255424 sd0d: start 0, end 2074879, size 2074880 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0e: start 32, end 819199, size 819168 sd0s1: type 0x6, start 32, end = 819199, size 819168 : OK sd0s2: type 0xa5, start 819200, end = 2074623, size 1255424 : OK sd0: rejecting partition in BSD label: it isn't entirely within the slice ... ... Since sd0s1 seems to be referencing the DOS partition, I tried to # cd /dev # ./MAKEDEV sd0s1 bad unit for disk in: sd0s1 So, I checked the MAKEDEV file, but that Bourne shell script does not contain the target sd0s1 (It seems to be outdated!!) If you had similar problem, then would you tell me how can I solve that problem? I just newly subscribe to current mailing list. Thanks very much. --Uh ---------------------- Uh Gang-Ryung e-mail: uh@cs.fsu.edu Work Phone: 644-3366 ---------------------- From owner-freebsd-current Mon May 8 20:18:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA01606 for current-outgoing; Mon, 8 May 1995 20:18:01 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA01600 for ; Mon, 8 May 1995 20:17:52 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id UAA00707; Mon, 8 May 1995 20:16:29 -0700 From: "Rodney W. Grimes" Message-Id: <199505090316.UAA00707@gndrsh.aac.dev.com> Subject: Re: DOS partition!! To: uh@grep.cs.fsu.edu (Gang-Ryung Uh) Date: Mon, 8 May 1995 20:16:29 -0700 (PDT) Cc: current@FreeBSD.org, uh@grep.cs.fsu.edu In-Reply-To: <199505090258.WAA05318@grep.cs.fsu.edu> from "Gang-Ryung Uh" at May 8, 95 10:58:18 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1814 Sender: current-owner@FreeBSD.org Precedence: bulk > > Recently, I upgraded FreeBSD from 2.0R to current (May 7). > After I did 'make world' & rebuilt the kernel and reboot with > the new kernel, I got the following message during the boot. > (Obviously I did disk slicing with FreeBSD 2.0R). > > sd0s1: type 0x6, start 32, end = 819199, size 819168 : OK > sd0s2: type 0xa5, start 819200, end = 2074623, size 1255424 : OK > sd0: rejecting partition in BSD label: it isn't entirely within the slice > sd0: start 819200, end 2074623, size 1255424 > sd0d: start 0, end 2074879, size 2074880 > sd0: rejecting partition in BSD label: it isn't entirely within the slice > sd0e: start 32, end 819199, size 819168 > sd0s1: type 0x6, start 32, end = 819199, size 819168 : OK > sd0s2: type 0xa5, start 819200, end = 2074623, size 1255424 : OK > sd0: rejecting partition in BSD label: it isn't entirely within the slice > ... > ... > > Since sd0s1 seems to be referencing the DOS partition, I tried to > > # cd /dev > # ./MAKEDEV sd0s1 > bad unit for disk in: sd0s1 > > So, I checked the MAKEDEV file, but that Bourne shell script does not > contain the target sd0s1 (It seems to be outdated!!) > > If you had similar problem, then would you tell me how can I solve > that problem? cp /usr/src/etc/etc.i386/MAKEDEV /dev cd /dev sh MAKEDEV sd0 mount /dev/sd0s1 /dos You should edit your disklabel and delete the e: and d: partitions, they are what are causing the above warnings during the boot. > I just newly subscribe to current mailing list. > > Thanks very much. > --Uh > > ---------------------- > Uh Gang-Ryung > > e-mail: uh@cs.fsu.edu > Work Phone: 644-3366 > ---------------------- > > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Mon May 8 21:36:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA03469 for current-outgoing; Mon, 8 May 1995 21:36:01 -0700 Received: from emerald.oz.net (emerald.oz.net [198.68.184.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA03463 for ; Mon, 8 May 1995 21:36:00 -0700 Received: from wsantee.oz.net by emerald.oz.net via SMTP (931110.SGI/930416.SGI) for freebsd-current@freebsd.org id AA25759; Mon, 8 May 95 21:34:00 -0700 Received: (from wsantee@localhost) by wsantee.oz.net (8.6.11/8.6.9) id VAA00350 for freebsd-current@freebsd.org; Mon, 8 May 1995 21:32:50 -0700 From: Wes Santee Message-Id: <199505090432.VAA00350@wsantee.oz.net> Subject: Getting "device not configured" from swapon To: freebsd-current@FreeBSD.org Date: Mon, 8 May 1995 21:32:48 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1275 Sender: current-owner@FreeBSD.org Precedence: bulk Hey all. I just re-sliced my second drive to include another 10 Megs of swap. Now when I boot I get the following message: swapon: /dev/wd1b: device not configured Here is the important disklabel info from /dev/wd1: # size offset fstype [fsize bsize bps/cpg] a: 173400 61455 4.2BSD 1024 8192 16 # (Cyl. 241 - 920) b: 20400 234855 swap # (Cyl. 921 - 1000) c: 193800 61455 unused 0 0 # (Cyl. 241 - 1000) d: 255255 0 unused 0 0 # (Cyl. 0 - 1000) e: 61200 255 unused 0 0 # (Cyl. 1 - 240) and here is the /etc/fstab file: /dev/wd0a / ufs rw 1 1 /dev/wd1a /var ufs rw 1 1 /dev/wd0f /msdos msdos rw 1 1 /dev/wd0b none swap sw 0 0 /dev/wd1b none swap sw 0 0 proc /proc procfs rw 0 0 The /dev/wd0b swap slice is coming up fine. Anybody know what might be going on? I did accidentally newfs /dev/wd1b along with /dev/wd1a but I figured that the swapper would ignore the formatting since it likes a raw slice. This is where the error may lie, but I don't know how to 're-clean' the partition (I tried re-writing the disklabel and only newfs-ing the /dev/wd1a slice). Any help appriciated. Cheers, -Wes From owner-freebsd-current Mon May 8 21:45:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA03551 for current-outgoing; Mon, 8 May 1995 21:45:30 -0700 Received: from emerald.oz.net (emerald.oz.net [198.68.184.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA03544 for ; Mon, 8 May 1995 21:45:28 -0700 Received: from wsantee.oz.net by emerald.oz.net via SMTP (931110.SGI/930416.SGI) for freebsd-current@freebsd.org id AA25872; Mon, 8 May 95 21:43:29 -0700 Received: (from wsantee@localhost) by wsantee.oz.net (8.6.11/8.6.9) id VAA00483 for freebsd-current@freebsd.org; Mon, 8 May 1995 21:42:19 -0700 From: Wes Santee Message-Id: <199505090442.VAA00483@wsantee.oz.net> Subject: Getting error from swapon - solved To: freebsd-current@FreeBSD.org Date: Mon, 8 May 1995 21:42:18 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 203 Sender: current-owner@FreeBSD.org Precedence: bulk Hey all again: Well, ignore my last plea for help regarding swapping...I found the problem. Don't have it configured in the kernel for swapping on the second drive...Now I feel stupid... Cheers, -Wes From owner-freebsd-current Mon May 8 21:47:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA03576 for current-outgoing; Mon, 8 May 1995 21:47:39 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA03570 for ; Mon, 8 May 1995 21:47:35 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id VAA00905; Mon, 8 May 1995 21:47:04 -0700 From: "Rodney W. Grimes" Message-Id: <199505090447.VAA00905@gndrsh.aac.dev.com> Subject: Re: Getting "device not configured" from swapon To: wsantee@wsantee.oz.net (Wes Santee) Date: Mon, 8 May 1995 21:47:03 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199505090432.VAA00350@wsantee.oz.net> from "Wes Santee" at May 8, 95 09:32:48 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1753 Sender: current-owner@FreeBSD.org Precedence: bulk > > Hey all. > > I just re-sliced my second drive to include another 10 Megs of swap. > Now when I boot I get the following message: > > swapon: /dev/wd1b: device not configured > > Here is the important disklabel info from /dev/wd1: > > # size offset fstype [fsize bsize bps/cpg] > a: 173400 61455 4.2BSD 1024 8192 16 # (Cyl. 241 - 920) > b: 20400 234855 swap # (Cyl. 921 - 1000) > c: 193800 61455 unused 0 0 # (Cyl. 241 - 1000) > d: 255255 0 unused 0 0 # (Cyl. 0 - 1000) > e: 61200 255 unused 0 0 # (Cyl. 1 - 240) > > and here is the /etc/fstab file: > > /dev/wd0a / ufs rw 1 1 > /dev/wd1a /var ufs rw 1 1 > /dev/wd0f /msdos msdos rw 1 1 > /dev/wd0b none swap sw 0 0 > /dev/wd1b none swap sw 0 0 > proc /proc procfs rw 0 0 What does ``swapinfo'' say? Do you have ``swap on wd0 and wd1'' in your kernel config file: config kernel root on wd0 swap on wd0 and wd1 dumps on wd0 > The /dev/wd0b swap slice is coming up fine. Anybody know what might > be going on? I did accidentally newfs /dev/wd1b along with /dev/wd1a > but I figured that the swapper would ignore the formatting since it > likes a raw slice. This is where the error may lie, but I don't know > how to 're-clean' the partition (I tried re-writing the disklabel and > only newfs-ing the /dev/wd1a slice). You should disklabel -e -r wd1 and set partiton b: to be what you showed above. The newfs operation probably set b: to be of type 4.2BSD. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue May 9 01:11:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA06030 for current-outgoing; Tue, 9 May 1995 01:11:00 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA06012 for ; Tue, 9 May 1995 01:10:08 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA00484; Tue, 9 May 1995 18:08:42 +1000 Date: Tue, 9 May 1995 18:08:42 +1000 From: Bruce Evans Message-Id: <199505090808.SAA00484@godzilla.zeta.org.au> To: uhclem@nemesis.lonestar.org Subject: Re: bin/389: Problem #FDIV024 Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Number: 389 >>Category: bin >>Synopsis: Simultaneous creation/deletion of dirs corrupts filesystem [FDIV024] I was able to reproduce the hang under -current: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 15 1669 159 0 -14 0 172 488 uihget D+ v2 0:00.05 ls -Fg 15 1619 160 2 -14 0 296 616 ufslk2 D v3 0:02.19 tar xf ../bin 15 1624 160 0 -18 0 296 620 vodead D v3 0:00.88 tar xf ../bin 15 1628 160 1 -14 0 296 616 ufslk2 D v3 0:00.77 tar xf ../bin 15 1632 160 0 -14 0 296 616 ufslk2 D v3 0:00.79 tar xf ../bin 15 1678 160 1 -14 0 160 476 ufslk2 D+ v3 0:00.04 ls -Fg The problems seem to be easier to reproduce on a small file system. I didn't see any on a new 512MB file system but I soon saw them on a 20000 block file system using bin.tar created from the current /usr/src/bin and running lots of tar xf's and rm -rf's concurrently. This was running as non-root. As root you have to worry about something unlinking "." and ".." directory entries. I don't think anything actually does, but tar --unlink might. Bruce From owner-freebsd-current Tue May 9 01:35:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA06491 for current-outgoing; Tue, 9 May 1995 01:35:30 -0700 Received: from inet-user-gw-1.us.oracle.com (inet-user-gw-1.us.oracle.com [192.86.155.82]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA06485 ; Tue, 9 May 1995 01:35:27 -0700 Received: from iesun1.ie.oracle.com by inet-user-gw-1.us.oracle.com with SMTP (8.6.12/37.7) id BAA08902; Tue, 9 May 1995 01:35:22 -0700 Received: by iesun1.ie.oracle.com (4.1/37.3.TJL.1.84) id AA22129; Tue, 9 May 95 09:34:38 BST Message-Id: <9505090834.AA22129@iesun1.ie.oracle.com> From: Henry Chung Subject: re: Getting "device not configured" from swapon To: freebsd-current@FreeBSD.org Date: Tue, 9 May 95 9:34:37 BST Cc: hchung@ie.oracle.com (Henry Chung), owner-freebsd-current@freefall.cdrom.com X-Mailer: ELM [version 2.3 PL11] Sender: current-owner@FreeBSD.org Precedence: bulk Wes, > I just re-sliced my second drive to include another 10 Megs of swap. > Now when I boot I get the following message: > > swapon: /dev/wd1b: device not configured > > Here is the important disklabel info from /dev/wd1: > > # size offset fstype [fsize bsize bps/cpg] > a: 173400 61455 4.2BSD 1024 8192 16 # (Cyl. 241 - 920) > b: 20400 234855 swap # (Cyl. 921 - 1000) > c: 193800 61455 unused 0 0 # (Cyl. 241 - 1000) > d: 255255 0 unused 0 0 # (Cyl. 0 - 1000) > e: 61200 255 unused 0 0 # (Cyl. 1 - 240) > > and here is the /etc/fstab file: > > /dev/wd0a / ufs rw 1 1 > /dev/wd1a /var ufs rw 1 1 > /dev/wd0f /msdos msdos rw 1 1 > /dev/wd0b none swap sw 0 0 > /dev/wd1b none swap sw 0 0 > proc /proc procfs rw 0 0 > > The /dev/wd0b swap slice is coming up fine. Anybody know what might > be going on? I did accidentally newfs /dev/wd1b along with /dev/wd1a > but I figured that the swapper would ignore the formatting since it > likes a raw slice. This is where the error may lie, but I don't know > how to 're-clean' the partition (I tried re-writing the disklabel and > only newfs-ing the /dev/wd1a slice). > > Any help appriciated. I have encounter the same problem. It is because the kernel is not configured to have drive 2 as swap, your kernel probably configured with swap on drive 1 only. Please check your config file for the kernel, then grep for the line config. Edit the file to have swap turn on wd1, rebuild your kernel and reboot the machine. The instruction of how to configure the kernel and rebuild the kernel can be found in the faq. regards, -- Henry From owner-freebsd-current Tue May 9 06:19:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA13820 for current-outgoing; Tue, 9 May 1995 06:19:15 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA13813 for ; Tue, 9 May 1995 06:19:05 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA08055 for current@freebsd.org; Tue, 9 May 1995 23:15:11 +1000 Date: Tue, 9 May 1995 23:15:11 +1000 From: Bruce Evans Message-Id: <199505091315.XAA08055@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: misadventures with parallel port tcp/ip Sender: current-owner@FreeBSD.org Precedence: bulk I tried the parallel port tcp/ip interface and found the following problems: 1) The BIOS probe fails if lp0 is up at the other end. I have two printer ports and lpt0 configured with `port?' so this caused lp0 to take turns working on the port that was not connected at boot time. 2) The system paniced with a null pointer trap in ifa_ifwithaddr() when I tried the following misconfiguration: ifconfig lp0 inet a0 b0 # a0 and b0 are in /etc/hosts route add b0 a0 # back to front route change a0 A NULL gateway was passed from route_output(). 3) Too much is done at a high ipl. I tried replacing the splhigh()s by splimp()s and everything continued to work even with 39000 interrupts/sec in the background (16000 from pcaudio, 2 * 11500 from 16450's). Ping latency increased from 2ms to 9-20ms with all these interrupts on a 486DX/33. 4) net_imask isn't initialized right in isa.c unless SLIP or PPP is configured. It needs to contain the lpt bit or perhaps all of tty_imask if lpt and INET are configured, at least while lp0 is up. This is approximately always. Bruce From owner-freebsd-current Tue May 9 06:54:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA14410 for current-outgoing; Tue, 9 May 1995 06:54:48 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA14403 for ; Tue, 9 May 1995 06:54:37 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA26946; Tue, 9 May 95 15:51:41 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id QAA10399 for freebsd-current@freefall.cdrom.com; Tue, 9 May 1995 16:03:10 +0200 Date: Tue, 9 May 1995 16:03:10 +0200 From: "Christoph P. Kukulies" Message-Id: <199505091403.QAA10399@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: ppp.FAQ (a nit) Sender: current-owner@FreeBSD.org Precedence: bulk While I was reading a FAQ, I found (really a nit): /usr/src/share/FAQ/Text: -rw-r--r-- 1 root wheel 10347 Mar 21 21:19 ports.FAQ -rwxr-xr-x 1 root wheel 9173 Mar 21 21:19 ppp.FAQ ^ ^ ^ -rw-r--r-- 1 root wheel 6977 Mar 21 21:19 slip.FAQ --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Tue May 9 07:06:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15082 for current-outgoing; Tue, 9 May 1995 07:06:13 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA15073 ; Tue, 9 May 1995 07:05:57 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id HAA02937; Tue, 9 May 1995 07:04:36 -0700 From: "Rodney W. Grimes" Message-Id: <199505091404.HAA02937@gndrsh.aac.dev.com> Subject: Re: ppp.FAQ (a nit) To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Tue, 9 May 1995 07:04:36 -0700 (PDT) Cc: FreeBSD-current@FreeBSD.org (FreeBSD current), cvs-committers@FreeBSD.org In-Reply-To: <199505091403.QAA10399@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at May 9, 95 04:03:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 621 Sender: current-owner@FreeBSD.org Precedence: bulk > > While I was reading a FAQ, I found (really a nit): > > /usr/src/share/FAQ/Text: > -rw-r--r-- 1 root wheel 10347 Mar 21 21:19 ports.FAQ > -rwxr-xr-x 1 root wheel 9173 Mar 21 21:19 ppp.FAQ > ^ ^ ^ > -rw-r--r-- 1 root wheel 6977 Mar 21 21:19 slip.FAQ > This has been corrected both in the ~ncvs repository and in /usr/src on Freefall. I did not re run the supscan so it may be up to 8 hours before this change is visible from /usr/src sup's. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue May 9 08:12:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16832 for current-outgoing; Tue, 9 May 1995 08:12:29 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA16826 for ; Tue, 9 May 1995 08:12:25 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA09797; Tue, 9 May 1995 11:11:23 -0400 Date: Tue, 9 May 1995 11:11:23 -0400 From: Garrett Wollman Message-Id: <9505091511.AA09797@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@FreeBSD.org Subject: misadventures with parallel port tcp/ip In-Reply-To: <199505091315.XAA08055@godzilla.zeta.org.au> References: <199505091315.XAA08055@godzilla.zeta.org.au> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > 2) The system paniced with a null pointer trap in ifa_ifwithaddr() when > I tried the following misconfiguration: > ifconfig lp0 inet a0 b0 # a0 and b0 are in /etc/hosts > route add b0 a0 # back to front > route change a0 > A NULL gateway was passed from route_output(). Hmmm. I fixed this bug some months ago, I guess it's back. Work-around: ``don't do that, then''. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue May 9 08:43:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17626 for current-outgoing; Tue, 9 May 1995 08:43:37 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA17620 for ; Tue, 9 May 1995 08:43:34 -0700 Received: by pelican.com (Smail3.1.28.1 #5) id m0s8rRU-000K0kC; Tue, 9 May 95 08:43 WET DST Message-Id: Date: Tue, 9 May 95 08:43 WET DST From: pete@pelican.com (Pete Carah) To: current@FreeBSD.org Subject: Re: elm 2.4 port In-Reply-To: <199505081716.TAA08204@gilberto.physik.rwth-aachen.de> Organization: Pelican Consulting Sender: current-owner@FreeBSD.org Precedence: bulk In article <199505081716.TAA08204@gilberto.physik.rwth-aachen.de> it is written: >/usr/ports/mail/elm/work/filter/Makefile has a leading >at the beginning of the line following the all: target >which breaks make. This is present in the distribution; I made elm yesterday without using the "ports" port and had the same problem. Had to run config again due to a misteak and it recreated the tab (of course), so had to get rid of it again :-( -- Pete From owner-freebsd-current Tue May 9 08:51:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17852 for current-outgoing; Tue, 9 May 1995 08:51:57 -0700 Received: from grendel.csc.smith.edu (grendel.csc.smith.edu [131.229.222.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA17839 ; Tue, 9 May 1995 08:51:48 -0700 Received: from localhost (jfieber@localhost) by grendel.csc.smith.edu (8.6.5/8.6.5) id LAA14450; Tue, 9 May 1995 11:50:44 -0400 From: jfieber@cs.smith.edu (John Fieber) Message-Id: <199505091550.LAA14450@grendel.csc.smith.edu> Subject: Re: ppp.FAQ (a nit) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 9 May 1995 11:50:43 -0400 (EDT) Cc: kuku@gilberto.physik.rwth-aachen.de, FreeBSD-current@FreeBSD.org, cvs-committers@FreeBSD.org In-Reply-To: <199505091404.HAA02937@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 9, 95 07:04:36 am Content-Type: text Content-Length: 495 Sender: current-owner@FreeBSD.org Precedence: bulk > > While I was reading a FAQ, I found (really a nit): > > > > /usr/src/share/FAQ/Text: > > -rw-r--r-- 1 root wheel 10347 Mar 21 21:19 ports.FAQ > > -rwxr-xr-x 1 root wheel 9173 Mar 21 21:19 ppp.FAQ > > ^ ^ ^ > > -rw-r--r-- 1 root wheel 6977 Mar 21 21:19 slip.FAQ > > The entire directory is destined for the graveyard. -john === jfieber@cs.smith.edu ================================================ =================================== Come up and be a kite! --K. Bush === From owner-freebsd-current Tue May 9 13:24:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA24874 for current-outgoing; Tue, 9 May 1995 13:24:10 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA24863 for ; Tue, 9 May 1995 13:24:05 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA03148 ; Tue, 9 May 1995 22:23:35 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id WAA04686 ; Tue, 9 May 1995 22:23:34 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199505092023.WAA04686@blaise.ibp.fr> Subject: Re: Getting "device not configured" from swapon To: wsantee@wsantee.oz.net (Wes Santee) Date: Tue, 9 May 1995 22:23:34 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199505090432.VAA00350@wsantee.oz.net> from "Wes Santee" at May 8, 95 09:32:48 pm X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 736 Sender: current-owner@FreeBSD.org Precedence: bulk > The /dev/wd0b swap slice is coming up fine. Anybody know what might > be going on? I did accidentally newfs /dev/wd1b along with /dev/wd1a > but I figured that the swapper would ignore the formatting since it > likes a raw slice. This is where the error may lie, but I don't know > how to 're-clean' the partition (I tried re-writing the disklabel and > only newfs-ing the /dev/wd1a slice). Did you update the line in your config file : config kernel root on sd0 swap on sd0 and sd1 and sd2 dumps on sd0 ^^^^^^^^^^^^^^^^^^^ with wd0 and wd1 for you of course... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-current Wed May 10 04:20:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA17395 for current-outgoing; Wed, 10 May 1995 04:20:10 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA17381 for ; Wed, 10 May 1995 04:19:47 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA09329 for current@freebsd.org; Wed, 10 May 1995 21:18:35 +1000 Date: Wed, 10 May 1995 21:18:35 +1000 From: Bruce Evans Message-Id: <199505101118.VAA09329@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: cp removes target file Sender: current-owner@FreeBSD.org Precedence: bulk `cp foo bar' removes the target file if there is an error. The relevant Errors may occur during the following operations: mmap errors for mapping the source short writes mmap errors for unmapping the source write errors read errors (if mmapping is not being used) Errors are rare. I've only seen them for: disk full hangup on the target when the target is a tty. Removing the target when the target is a special file is certainly a bug. I think removing the target is a bug in all cases. Removing it removes its attributes as well as its contents. Removing it doesn't help unfill the disk if the target is linked. Removing it may destroy unreplaceable data if the source is not a regular file. Gnu cp doesn't seem to remove the target. Bruce From owner-freebsd-current Wed May 10 04:55:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA18159 for current-outgoing; Wed, 10 May 1995 04:55:36 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA18128 for ; Wed, 10 May 1995 04:54:45 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <43063>; Wed, 10 May 1995 13:53:57 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id JAA17114 for current@freebsd.org; Wed, 10 May 1995 09:46:46 +0200 Date: Wed, 10 May 1995 09:46:46 +0200 From: Julian Howard Stacey Message-Id: <199505100746.JAA17114@vector.eikon.e-technik.tu-muenchen.de> To: current@FreeBSD.org Subject: ctm date levels Sender: current-owner@FreeBSD.org Precedence: bulk It would be convenient if the src/.ctm_status & ports/.ctm_status files had a 2nd line, instead of just: src-cur 601 perhaps it could have: src-cur 601 generated on freefall.cdrom.com this would make it easy for those of us who use ctm to make a our comments more relevent to those who use sup or mirror. Alternately the info could be in a seperate file, perhaps .cvs_status ? In fact, I guess a .cvs_status would be nicer, perhaps this is Rod's area ? Julian S From owner-freebsd-current Wed May 10 09:27:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA25105 for current-outgoing; Wed, 10 May 1995 09:27:07 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA25098 for ; Wed, 10 May 1995 09:27:02 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA13669; Wed, 10 May 95 18:25:40 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id SAA13595 for freebsd-current@freefall.cdrom.com; Wed, 10 May 1995 18:37:06 +0200 Date: Wed, 10 May 1995 18:37:06 +0200 From: "Christoph P. Kukulies" Message-Id: <199505101637.SAA13595@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: bug in /usr/src/etc/rc (netstart) Sender: current-owner@FreeBSD.org Precedence: bulk netstart is started using sh /etc/netstart (that was a . /etc/netstart formerly and it used to work). Now, starting it with sh /etc/netstart $hostname is unknown and the consequences are quite unfriendly. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Wed May 10 09:53:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA25808 for current-outgoing; Wed, 10 May 1995 09:53:05 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA25800 for ; Wed, 10 May 1995 09:53:02 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA08095; Wed, 10 May 1995 09:51:17 -0700 From: "Rodney W. Grimes" Message-Id: <199505101651.JAA08095@gndrsh.aac.dev.com> Subject: Re: bug in /usr/src/etc/rc (netstart) To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Wed, 10 May 1995 09:51:17 -0700 (PDT) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199505101637.SAA13595@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at May 10, 95 06:37:06 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 601 Sender: current-owner@FreeBSD.org Precedence: bulk > > > netstart is started using sh /etc/netstart (that was a . /etc/netstart > formerly and it used to work). Now, starting it with sh /etc/netstart > $hostname is unknown and the consequences are quite unfriendly. Hostname should be set by /etc/sysconfig, /etc/sysconfig is .'ed into /etc/rc. Infact all variables that where set in /etc/netstart should now be set by /etc/sysconfig. Do you infact have /etc/sysconfig 1.11, /etc/rc 1.63 ? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 10 09:59:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA26079 for current-outgoing; Wed, 10 May 1995 09:59:04 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA26069 for ; Wed, 10 May 1995 09:59:02 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA14386; Wed, 10 May 95 18:58:03 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id TAA13691; Wed, 10 May 1995 19:09:29 +0200 Message-Id: <199505101709.TAA13691@gilberto.physik.rwth-aachen.de> Subject: Re: bug in /usr/src/etc/rc (netstart) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 10 May 1995 19:09:28 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com (user alias) In-Reply-To: <199505101651.JAA08095@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 10, 95 09:51:17 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1061 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > netstart is started using sh /etc/netstart (that was a . /etc/netstart > > formerly and it used to work). Now, starting it with sh /etc/netstart > > $hostname is unknown and the consequences are quite unfriendly. > > Hostname should be set by /etc/sysconfig, /etc/sysconfig is .'ed into > /etc/rc. Infact all variables that where set in /etc/netstart should > now be set by /etc/sysconfig. > > Do you infact have /etc/sysconfig 1.11, /etc/rc 1.63 ? My /etc/sysconfig is a 1.9 one (but the diff to 1.11 is not relevant). /etc/rc is 1.63. I will reboot in a minute with a sysconfig 1.11 to be absolutely sure. > > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Wed May 10 14:42:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA05813 for current-outgoing; Wed, 10 May 1995 14:42:49 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA05805 for ; Wed, 10 May 1995 14:42:41 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA20883 for ; Wed, 10 May 1995 23:42:34 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA11903 for freebsd-current@FreeBSD.ORG; Wed, 10 May 1995 23:42:33 +0200 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.6.11/keltia-uucp-1.21) id BAA13453 for freebsd-current@FreeBSD.ORG; Wed, 10 May 1995 01:32:17 +0200 From: Ollivier Robert Message-Id: <199505092332.BAA13453@keltia.frmug.fr.net> Subject: Pkg_info and friends To: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Date: Wed, 10 May 1995 01:32:16 +0200 (MET DST) Reply-To: roberto@keltia.freenix.fr (Ollivier Robert) X-Operating-System: FreeBSD 2.0-BUILT-19950506 ctm#646 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1068 Sender: current-owner@FreeBSD.org Precedence: bulk Jordan, could you please explain what's going on with all the pkg_* programs ? Why do they have to use tar for ? 245 [1:29] root@keltia:compile/KELTIA# setenv PKG_PATH /var/db/pkg 246 [1:29] root@keltia:compile/KELTIA# pkg_info -a tar: unknown option tar: Unknown option. Use 'tar --help' for a complete list of options. Tar extract of failed! Error during unpacking, no info for 'mpeg_lib-1.1' available. tar: unknown option tar: Unknown option. Use 'tar --help' for a complete list of options. Tar extract of failed! Error during unpacking, no info for 'xcdplayer-2.2' available. tar: unknown option tar: Unknown option. Use 'tar --help' for a complete list of options. Tar extract of failed! Error during unpacking, no info for 'xview32_bin' available. Three of my installed packages come from old binary packages and the rest has been installed by the bsd.port.mk when I "make install" a port. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.0-BUILT-19950506 #4: Sat May 6 10:23:04 MET DST 1995 From owner-freebsd-current Wed May 10 15:19:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA07307 for current-outgoing; Wed, 10 May 1995 15:19:57 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA07300 ; Wed, 10 May 1995 15:19:56 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: roberto@keltia.freenix.fr (Ollivier Robert) cc: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Subject: Re: Pkg_info and friends In-reply-to: Your message of "Wed, 10 May 95 01:32:16 +0200." <199505092332.BAA13453@keltia.frmug.fr.net> Date: Wed, 10 May 1995 15:19:51 -0700 Message-ID: <7299.800144391@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Jordan, could you please explain what's going on with all the pkg_* > programs ? Why do they have to use tar for ? Because packages are just smart tarballs.. :-) You need the latest mk files and tar to use the pkg_install suite as it currently stands, though there's also a big in pkg_info which I'll go look at now.. Thanks for reminding me! Jordan From owner-freebsd-current Wed May 10 15:43:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA07938 for current-outgoing; Wed, 10 May 1995 15:43:27 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA07920 for ; Wed, 10 May 1995 15:43:04 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id XAA00336 for current@freebsd.org; Wed, 10 May 1995 23:40:37 +0100 Date: Wed, 10 May 1995 23:40:37 +0100 From: Mark Valentine Message-Id: <199505102240.XAA00336@linus.demon.co.uk> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: current@FreeBSD.org Subject: problem with new biosboot? Sender: current-owner@FreeBSD.org Precedence: bulk > phk 95/05/07 19:03:03 > > Modified: sys/i386/boot/biosboot disk.c > Log: > Make disk.c smart enough to handle disk with "OnTrack Disk manager". > Make it complain if people try to boot from a partition which extends > past 1024 cylinders. This is better than a random reset... Since these boot blocks now tell me that my "partition is out of reach from the bios", I guess I'd better try to understand what might be wrong with my slice/partition configuration. However, I can't follow the code... /* This little trick is for OnTrack DiskManager disks */ boff = dl->d_partitions[part].p_offset - dl->d_partitions[2].p_offset + sector; /* This is a good idea for all disks */ bsize = dl->d_partitions[part].p_size; bend = boff + bsize - 1 ; if (bend / spt > 1024) { printf("partition is out of reach from the bios\n"); return 1; } Why is dl->d_partitions[2].p_offset meaningful even if I don't have OnTrack DiskManager? Why can't my partition be >1024 cylinders? The disk in question is a 1GB SCSI (Quantum PD1050iS), attached to an AHA1542C. # fdisk /dev/sd0 ******* Working on device /dev/sd0 ******* parameters extracted from in-core disklabel are: cylinders=2448 heads=12 sectors/track=69 (828 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2448 heads=12 sectors/track=69 (828 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 The geometry is the untranslated version. The bogus slice isn't what I remember setting it up as when I upgraded to FreeBSD 2.0 (950210 SNAP), but probably happened when I used disklabel -e to specify non-zero RPM, etc. (?) I used what I thought was a correct sizing based on the translated geometry at that time. Curiously, the compatibility device shows me an MBR table with the translated geometry: # fdisk /dev/sd0d ******* Working on device /dev/sd0d ******* parameters extracted from in-core disklabel are: cylinders=1003 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=1003 heads=64 sectors/track=32 (2048 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 Which of these is relevant, and where on the disk is the other one stored?! My disklabel uses translated geometry: # disklabel -r sd0 # /dev/rsd0c: type: SCSI disk: label: MBR based label flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 1003 sectors/unit: 2055096 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 36864 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 17) b: 81920 36864 swap # (Cyl. 18 - 57) c: 2055096 0 unused 0 0 # (Cyl. 0 - 1003*) d: 2055096 0 unused 0 0 # (Cyl. 0 - 1003*) e: 102400 118784 4.2BSD 1024 8192 16 # (Cyl. 58 - 107) f: 512000 221184 4.2BSD 1024 8192 16 # (Cyl. 108 - 357) g: 1024000 733184 4.2BSD 1024 8192 16 # (Cyl. 358 - 857) h: 296960 1757184 4.2BSD 1024 8192 16 # (Cyl. 858 - 1002) I thought maybe partition 'a' shouldn't be at offset 0, but a fresh trial installation on wd0 (again of 950210-SNAP, using the whole disk for FreeBSD) also had this (no manual tweaking on that one). I thought I was beginning to understand all this, and I'd been running without problems for a few months (last disklabel -B sd0 was just after the last change to biosboot before this one). Any pointers as to what I'm not taking in? Cheers, Mark. From owner-freebsd-current Wed May 10 15:52:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA08205 for current-outgoing; Wed, 10 May 1995 15:52:37 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA08199 ; Wed, 10 May 1995 15:52:35 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id AAA21318 ; Thu, 11 May 1995 00:52:24 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id AAA12367 ; Thu, 11 May 1995 00:52:24 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199505102252.AAA12367@blaise.ibp.fr> Subject: Re: Pkg_info and friends To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Thu, 11 May 1995 00:52:23 +0200 (MET DST) Cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org In-Reply-To: <7299.800144391@freefall.cdrom.com> from "Jordan K. Hubbard" at May 10, 95 03:19:51 pm X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 757 Sender: current-owner@FreeBSD.org Precedence: bulk > You need the latest mk files and tar to use the pkg_install suite > as it currently stands, though there's also a big in pkg_info which > I'll go look at now.. Thanks for reminding me! But when you do a "make all install" in a ports subdirectory, it installs the pkg/* files in /var/db/pkg. And I don't have a tarball yet ! Where will pkg_info take its information if not in /var/db/pkg ? It should first look into the db directory and take the information elsewhere if the package is not installed. You can't force people to keep tarballs around when they've been installed. Or am I missing something ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-current Wed May 10 15:58:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA08316 for current-outgoing; Wed, 10 May 1995 15:58:38 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA08310 for ; Wed, 10 May 1995 15:58:38 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA26509; Wed, 10 May 1995 15:58:30 -0700 From: Poul-Henning Kamp Message-Id: <199505102258.PAA26509@ref.tfs.com> Subject: Re: problem with new biosboot? To: mark@linus.demon.co.uk (Mark Valentine) Date: Wed, 10 May 1995 15:58:30 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505102240.XAA00336@linus.demon.co.uk> from "Mark Valentine" at May 10, 95 11:40:37 pm Content-Type: text Content-Length: 1042 Sender: current-owner@FreeBSD.org Precedence: bulk > > Modified: sys/i386/boot/biosboot disk.c > > Log: > > Make disk.c smart enough to handle disk with "OnTrack Disk manager". > > Make it complain if people try to boot from a partition which extends > > past 1024 cylinders. This is better than a random reset... > > Since these boot blocks now tell me that my "partition is out of reach from > the bios", I guess I'd better try to understand what might be wrong with my > slice/partition configuration. However, I can't follow the code... The rule is simple: For the boot-bloks to work, no sector needed to read the kernel must be past cylinder 1023, because we use the bios to read in the kernel. This is uncheckable, and undeterministic, so the check is: the filesystem from which the kernel is read, must have no blocks past cylider 1023. Partition 2 is the entire slice, always. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed May 10 16:04:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA08549 for current-outgoing; Wed, 10 May 1995 16:04:23 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA08542 ; Wed, 10 May 1995 16:04:21 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: roberto@blaise.ibp.fr (Ollivier Robert) cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org Subject: Re: Pkg_info and friends In-reply-to: Your message of "Thu, 11 May 95 00:52:23 +0200." <199505102252.AAA12367@blaise.ibp.fr> Date: Wed, 10 May 1995 16:04:20 -0700 Message-ID: <8540.800147060@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Where will pkg_info take its information if not in /var/db/pkg ? It should > first look into the db directory and take the information elsewhere if the > package is not installed. You can't force people to keep tarballs around > when they've been installed. Or am I missing something ? That was the bug I was referring to - THAT part should work. Go grab the very latest pkg_install suite (I _just_ fixed it) and try again.. Thanks! Jordan From owner-freebsd-current Wed May 10 19:28:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA13387 for current-outgoing; Wed, 10 May 1995 19:28:37 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA13380 for ; Wed, 10 May 1995 19:28:34 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: current@freefall.cdrom.com Subject: new config update. Date: Wed, 10 May 1995 19:28:33 -0700 Message-ID: <13379.800159313@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk The config program has been updated to incorporate a new `conflicts' keyword. This replaces the ALLOW_CONFLICT_* bodge I first stuck in there and is now, at least, device specific rather than kernel-wide. It could all still be much improved, but is nonetheless an improvement over what we had before. Just FYI.. Jordan From owner-freebsd-current Wed May 10 22:07:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA17171 for current-outgoing; Wed, 10 May 1995 22:07:45 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA17162 ; Wed, 10 May 1995 22:07:43 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id WAA00639 ; Wed, 10 May 1995 22:01:03 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id XAA23725; Wed, 10 May 1995 23:08:05 -0600 Date: Wed, 10 May 1995 23:08:05 -0600 From: Nate Williams Message-Id: <199505110508.XAA23725@trout.sri.MT.net> To: "Jordan K. Hubbard" Cc: current@freefall.cdrom.com Subject: Re: new config update. In-Reply-To: <13379.800159313@freefall.cdrom.com> References: <13379.800159313@freefall.cdrom.com> Sender: current-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > The config program has been updated to incorporate a new `conflicts' > keyword. This replaces the ALLOW_CONFLICT_* bodge I first stuck in > there and is now, at least, device specific rather than kernel-wide. > It could all still be much improved, but is nonetheless an improvement > over what we had before. I'm in agreement that it's a botch, but since the reason that it exists in the first place is a botch anyway, it's not too bad of solution. Thanks! Nate From owner-freebsd-current Wed May 10 22:34:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA17618 for current-outgoing; Wed, 10 May 1995 22:34:51 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA17608 for ; Wed, 10 May 1995 22:34:34 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA06311; Thu, 11 May 1995 15:31:22 +1000 Date: Thu, 11 May 1995 15:31:22 +1000 From: Bruce Evans Message-Id: <199505110531.PAA06311@godzilla.zeta.org.au> To: current@FreeBSD.org, mark@linus.demon.co.uk Subject: Re: problem with new biosboot? Sender: current-owner@FreeBSD.org Precedence: bulk > # fdisk /dev/sd0 > ******* Working on device /dev/sd0 ******* > parameters extracted from in-core disklabel are: > cylinders=2448 heads=12 sectors/track=69 (828 blks/cyl) This geometry is a merge of the geometry reported by the drive and the geometry guessed from the partition table. Since the partition table is bogus, and is detected to be so, no geometry was guessed from it, and you ended up with the geometry reported by the drive. > The data for partition 3 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 0, size 50000 (24 Meg), flag 80 > beg: cyl 0/ sector 1/ head 0; > end: cyl 1023/ sector 63/ head 255 >The geometry is the untranslated version. The bogus slice isn't what I >remember setting it up as when I upgraded to FreeBSD 2.0 (950210 SNAP), >but probably happened when I used disklabel -e to specify non-zero RPM, >etc. (?) ... Correct. >Curiously, the compatibility device shows me an MBR table with the translated >geometry: > # fdisk /dev/sd0d > ******* Working on device /dev/sd0d ******* > parameters extracted from in-core disklabel are: > cylinders=1003 heads=64 sectors/track=32 (2048 blks/cyl) It doesn't make any sense to run fdisk on the compatibility slice, especially on the d partition in it. The d partition just happens to start at offset 0 on the whole disk, so fdisk reads the MBR from the right place. It reads the label from a different place (the in-core label for the compatibility slice, which is different from the in-core label for the whole disk). The geometry is whatever you put in the label. >Which of these is relevant, and where on the disk is the other one stored?! Neither is relevant to the current problem :-). The one for the whole disk is constructed when a device on the disk is first opened. It currently just holds the (currently guessed) BIOS geometry. >My disklabel uses translated geometry: > # disklabel -r sd0 > # /dev/rsd0c: > ... > sectors/track: 32 > tracks/cylinder: 64 > sectors/cylinder: 2048 > cylinders: 1003 > ... > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 36864 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 17) Booting from partition 'a' should work. It surely is all below cylinder 1024 in the BIOS geometry, whatever it is, and you don't use bad144. The whole disk is probably below cylinder 1024, so even booting from the 'c' partition should work. I can't explain the problem. Bruce From owner-freebsd-current Wed May 10 23:09:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA18157 for current-outgoing; Wed, 10 May 1995 23:09:35 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA18148 for ; Wed, 10 May 1995 23:09:28 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA07289; Thu, 11 May 1995 16:07:55 +1000 Date: Thu, 11 May 1995 16:07:55 +1000 From: Bruce Evans Message-Id: <199505110607.QAA07289@godzilla.zeta.org.au> To: current@FreeBSD.org, mark@linus.demon.co.uk Subject: Re: problem with new biosboot? Sender: current-owner@FreeBSD.org Precedence: bulk > /* This is a good idea for all disks */ > bsize = dl->d_partitions[part].p_size; > bend = boff + bsize - 1 ; > if (bend / spt > 1024) { ^^^ > printf("partition is out of reach from the bios\n"); > return 1; > } spc should work better :-). It's amazing that spt often works. It works here because bend = 32767 and spt = 32 on one system and 52 on another. Bruce From owner-freebsd-current Thu May 11 01:25:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA20113 for current-outgoing; Thu, 11 May 1995 01:25:27 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA20106 for current; Thu, 11 May 1995 01:25:26 -0700 Date: Thu, 11 May 1995 01:25:26 -0700 From: "Jordan K. Hubbard" Message-Id: <199505110825.BAA20106@freefall.cdrom.com> To: current Subject: config broken for about an hour.. Sender: current-owner@FreeBSD.org Precedence: bulk If you build a kernel with the new config and it promptly obliged you by generating a kernel with all devices disabled by default, I apologise. config wasn't _quite_ in sync with what I meant to do and this is now fixed. Update it and try again! Jordan From owner-freebsd-current Thu May 11 02:03:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA21246 for current-outgoing; Thu, 11 May 1995 02:03:11 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA21208 for ; Thu, 11 May 1995 02:02:47 -0700 Received: by sequent.kiae.su id AA19141 (5.65.kiae-2 ); Thu, 11 May 1995 12:54:22 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 11 May 95 12:54:21 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id CAA00341; Thu, 11 May 1995 02:52:15 +0400 To: "Jordan K. Hubbard" , Ollivier Robert Cc: "FreeBSD Current Users' list" References: <7299.800144391@freefall.cdrom.com> In-Reply-To: <7299.800144391@freefall.cdrom.com>; from "Jordan K. Hubbard" at Wed, 10 May 1995 15:19:51 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 11 May 1995 02:52:14 +0400 X-Mailer: Mail/@ [v2.34 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: Pkg_info and friends Lines: 15 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 667 Sender: current-owner@FreeBSD.org Precedence: bulk In message <7299.800144391@freefall.cdrom.com> Jordan K. Hubbard writes: >You need the latest mk files and tar to use the pkg_install suite >as it currently stands, though there's also a big in pkg_info which >I'll go look at now.. Thanks for reminding me! I got the same diagnostic from pkg_add even with newest tar :-( Unknown option usually is strange 8bit char. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu May 11 04:02:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA28390 for current-outgoing; Thu, 11 May 1995 04:02:50 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA28365 for ; Thu, 11 May 1995 04:02:42 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id MAA01575; Thu, 11 May 1995 12:02:35 +0100 Date: Thu, 11 May 1995 12:02:35 +0100 From: Mark Valentine Message-Id: <199505111102.MAA01575@linus.demon.co.uk> In-Reply-To: Poul-Henning Kamp's message of May 10, 3:58pm X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Poul-Henning Kamp Subject: Re: problem with new biosboot? Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > From: Poul-Henning Kamp > Date: Wed 10 May, 1995 > Subject: Re: problem with new biosboot? > The rule is simple: > > For the boot-bloks to work, no sector needed to read the kernel > must be past cylinder 1023, because we use the bios to read in > the kernel. > > This is uncheckable, and undeterministic, so the check is: > the filesystem from which the kernel is read, must have no blocks > past cylider 1023. > > Partition 2 is the entire slice, always. *ding* My obvious mistake was in assuming I knew the context of the code I was looking at, without checking. I was reading "partition" as "slice" because I thought I was having problems with the slice configuration (the slice is obviously >1024 cylinders in untranslated geometry, whereas my 'a' partition isn't, no matter how you look at it!). OK, now I'm pointed in the right direction, I'll try Bruce's s/spt/spc/ tonight... Cheers, Mark. From owner-freebsd-current Thu May 11 04:40:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA29670 for current-outgoing; Thu, 11 May 1995 04:40:21 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA29664 for ; Thu, 11 May 1995 04:40:10 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id MAA00400; Thu, 11 May 1995 12:39:03 +0100 Date: Thu, 11 May 1995 12:39:03 +0100 From: Mark Valentine Message-Id: <199505111139.MAA00400@linus.demon.co.uk> In-Reply-To: Bruce Evans's message of May 11, 4:07pm X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans , current@FreeBSD.org Subject: Re: problem with new biosboot? Sender: current-owner@FreeBSD.org Precedence: bulk > From: Bruce Evans > Date: Thu 11 May, 1995 > Subject: Re: problem with new biosboot? > > /* This is a good idea for all disks */ > > bsize = dl->d_partitions[part].p_size; > > bend = boff + bsize - 1 ; > > if (bend / spt > 1024) { > ^^^ > > printf("partition is out of reach from the bios\n"); > > return 1; > > } > > spc should work better :-). It's amazing that spt often works. It works > here because bend = 32767 and spt = 32 on one system and 52 on another. Indeed, it certainly works better for me. :-) Thank you! Mark. From owner-freebsd-current Thu May 11 09:19:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA03197 for current-outgoing; Thu, 11 May 1995 09:19:23 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA03191 for ; Thu, 11 May 1995 09:19:22 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id JAA29332; Thu, 11 May 1995 09:18:39 -0700 From: Poul-Henning Kamp Message-Id: <199505111618.JAA29332@ref.tfs.com> Subject: Re: problem with new biosboot? To: bde@zeta.org.au (Bruce Evans) Date: Thu, 11 May 1995 09:18:38 -0700 (PDT) Cc: current@FreeBSD.org, mark@linus.demon.co.uk In-Reply-To: <199505110607.QAA07289@godzilla.zeta.org.au> from "Bruce Evans" at May 11, 95 04:07:55 pm Content-Type: text Content-Length: 697 Sender: current-owner@FreeBSD.org Precedence: bulk > > /* This is a good idea for all disks */ > > bsize = dl->d_partitions[part].p_size; > > bend = boff + bsize - 1 ; > > if (bend / spt > 1024) { > ^^^ > > printf("partition is out of reach from the bios\n"); > > return 1; > > } > > spc should work better :-). It's amazing that spt often works. It works > here because bend = 32767 and spt = 32 on one system and 52 on another. DUH! -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Thu May 11 09:37:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA05077 for current-outgoing; Thu, 11 May 1995 09:37:59 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA04304 for ; Thu, 11 May 1995 09:26:27 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA26082; Thu, 11 May 95 08:13:09 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id IAA15370; Thu, 11 May 1995 08:24:33 +0200 Message-Id: <199505110624.IAA15370@gilberto.physik.rwth-aachen.de> Subject: Re: bug in /usr/src/etc/rc (netstart) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 11 May 1995 08:24:33 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com (user alias) In-Reply-To: <199505101651.JAA08095@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 10, 95 09:51:17 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1284 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > netstart is started using sh /etc/netstart (that was a . /etc/netstart > > formerly and it used to work). Now, starting it with sh /etc/netstart > > $hostname is unknown and the consequences are quite unfriendly. > > Hostname should be set by /etc/sysconfig, /etc/sysconfig is .'ed into > /etc/rc. Infact all variables that where set in /etc/netstart should > now be set by /etc/sysconfig. > > Do you infact have /etc/sysconfig 1.11, /etc/rc 1.63 ? I checked again now definitely with both, sysconfig 1.11, rc 1.63 and when I have the sh /etc/netstart in rc the hostname is not being set. How should it ? I don't need to tell you that a sub shell does not inherit variables that are set in the parent unless the subshell is 'sourced'. It works ok if I replace sh with . (source) (which was in some earlier version of rc anyway). > > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Thu May 11 10:09:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA06108 for current-outgoing; Thu, 11 May 1995 10:09:57 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA06089 for ; Thu, 11 May 1995 10:09:25 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA26346; Thu, 11 May 95 08:37:54 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id IAA15386 for freebsd-current@freefall.cdrom.com; Thu, 11 May 1995 08:49:11 +0200 Date: Thu, 11 May 1995 08:49:11 +0200 From: "Christoph P. Kukulies" Message-Id: <199505110649.IAA15386@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: dial in line Sender: current-owner@FreeBSD.org Precedence: bulk With all the tty name changes in the past and FAQs dedicated to the graveyard, as someone put it, what is the right ttyname for a dial in line. I upgraded my dial in machine to -current and ttyd0 doesn't open when a call arrives, that is the getty sits there and does nothing. Are the settings for modem in rc.serial correct (I mean this dtrwait and crtscts stuff)? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Thu May 11 10:27:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA06919 for current-outgoing; Thu, 11 May 1995 10:27:15 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA06907 for ; Thu, 11 May 1995 10:27:12 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA10530; Thu, 11 May 1995 10:25:39 -0700 From: "Rodney W. Grimes" Message-Id: <199505111725.KAA10530@gndrsh.aac.dev.com> Subject: Re: bug in /usr/src/etc/rc (netstart) To: kuku@gilberto.physik.rwth-aachen.de Date: Thu, 11 May 1995 10:25:39 -0700 (PDT) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199505110624.IAA15370@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at May 11, 95 08:24:33 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1648 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > netstart is started using sh /etc/netstart (that was a . /etc/netstart > > > formerly and it used to work). Now, starting it with sh /etc/netstart > > > $hostname is unknown and the consequences are quite unfriendly. > > > > Hostname should be set by /etc/sysconfig, /etc/sysconfig is .'ed into > > /etc/rc. Infact all variables that where set in /etc/netstart should > > now be set by /etc/sysconfig. > > > > Do you infact have /etc/sysconfig 1.11, /etc/rc 1.63 ? > > I checked again now definitely with both, sysconfig 1.11, rc 1.63 and > when I have the sh /etc/netstart in rc the hostname is not being set. > How should it ? I don't need to tell you that a sub shell does not inherit > variables that are set in the parent unless the subshell is 'sourced'. > > It works ok if I replace sh with . (source) (which was in some > earlier version of rc anyway). I don't like to repeat myself, but ``Hostname is set by /etc/sysconfig, /etc/sysconfig is sourced by /etc/rc''. I know all about sub shell vs sourced file and the effects on variables. I have been writting /etc/rc files for 15 years. Just where are you setting $hostname at? If your not doing it at about line 61 of /etc/sysconfig your not doing it the right way!!! You will note that at line 75 of /etc/rc the file /etc/sysconf is sourced into /etc/rc which means $hostname is defined. You will also note that this is the same way that /etc/netstart now gets this value from /etc/sysconfig. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu May 11 10:41:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA07563 for current-outgoing; Thu, 11 May 1995 10:41:49 -0700 Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA07550 for ; Thu, 11 May 1995 10:41:43 -0700 Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA06025; Thu, 11 May 1995 19:25:20 +0200 From: Luigi Rizzo Message-Id: <199505111725.TAA06025@labinfo.iet.unipi.it> Subject: Re: bug in /usr/src/etc/rc (netstart) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 11 May 1995 19:25:19 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-current@freefall.cdrom.com In-Reply-To: <199505111725.KAA10530@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 11, 95 10:25:20 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 705 Sender: current-owner@FreeBSD.org Precedence: bulk I guess it is worth putting a BIG note near the beginning of /etc/rc, /etc/netstart and similar places that now /etc/sysconfig takes care of a lot of things. People coming from 1.1 or early 2.0 installations might forget this and try to do the wrong thing (such as leaving the hostname in /etc/myname, the defaultrouter in /etc/defaultrouter, etc.) Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 ==================================================================== From owner-freebsd-current Thu May 11 12:05:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA10040 for current-outgoing; Thu, 11 May 1995 12:05:35 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA10025 for ; Thu, 11 May 1995 12:05:20 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA28045; Fri, 12 May 1995 05:03:24 +1000 Date: Fri, 12 May 1995 05:03:24 +1000 From: Bruce Evans Message-Id: <199505111903.FAA28045@godzilla.zeta.org.au> To: freebsd-current@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de Subject: Re: dial in line Sender: current-owner@FreeBSD.org Precedence: bulk >With all the tty name changes in the past and FAQs dedicated to the >graveyard, as someone put it, what is the right ttyname for a dial in line. Whatever is in the current /etc/ttys and /dev/MAKEDEV. Currently ttyd*. >I upgraded my dial in machine to -current and ttyd0 doesn't open when a call >arrives, that is the getty sits there and does nothing. Are the settings for >modem in rc.serial correct (I mean this dtrwait and crtscts stuff)? The correct setting is system dependent. That's why everything in rc.serial is commented out by default. The setting of dtrwait is safe enough but the setting of crtscts may cause problems if the modem doesn't assert CTS except when there is carrier. Bruce From owner-freebsd-current Thu May 11 12:46:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA11676 for current-outgoing; Thu, 11 May 1995 12:46:19 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA11668 for ; Thu, 11 May 1995 12:46:16 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA11377; Thu, 11 May 1995 12:45:12 -0700 From: "Rodney W. Grimes" Message-Id: <199505111945.MAA11377@gndrsh.aac.dev.com> Subject: Re: bug in /usr/src/etc/rc (netstart) To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 11 May 1995 12:45:12 -0700 (PDT) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-current@freefall.cdrom.com In-Reply-To: <199505111725.TAA06025@labinfo.iet.unipi.it> from "Luigi Rizzo" at May 11, 95 07:25:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 712 Sender: current-owner@FreeBSD.org Precedence: bulk > > I guess it is worth putting a BIG note near the beginning of /etc/rc, > /etc/netstart and similar places that now /etc/sysconfig takes care > of a lot of things. People coming from 1.1 or early 2.0 installations > might forget this and try to do the wrong thing (such as leaving > the hostname in /etc/myname, the defaultrouter in /etc/defaultrouter, > etc.) I find that the type of people who do that are also the type of people who don't read big warning notes. Perhaps something in the release notes (an ``upgrade'' section) should cover this. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu May 11 14:08:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA13779 for current-outgoing; Thu, 11 May 1995 14:08:49 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA13773 for ; Thu, 11 May 1995 14:08:43 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14814(3)>; Thu, 11 May 1995 14:03:44 PDT Received: by crevenia.parc.xerox.com id <49859>; Thu, 11 May 1995 14:03:39 -0700 From: Bill Fenner To: current@FreeBSD.org Subject: IP_ACCT set/getsockopts? Message-Id: <95May11.140339pdt.49859@crevenia.parc.xerox.com> Date: Thu, 11 May 1995 14:03:38 PDT Sender: current-owner@FreeBSD.org Precedence: bulk I was munging around with the multicast set/getsockopts, and on my way there, I found: case IP_ACCT_DEL: case IP_ACCT_ADD: case IP_ACCT_CLR: case IP_ACCT_FLUSH: case IP_ACCT_ZERO: ... op = PRCO_SETOPT; if (op) { error=(*ip_acct_ctl_ptr)(optname, *m); if (*m) (void)m_free(*m); } Uh, what? Seems to me that this should be more like if (op == PRCO_SETOPT) { ... } else error = EINVAL; (Unless, of course, having a getsockopt(..,IP_ACCT_ADD,..) panic the kernel is a desired effect...) Bill From owner-freebsd-current Thu May 11 14:40:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA15285 for current-outgoing; Thu, 11 May 1995 14:40:04 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA15273 for ; Thu, 11 May 1995 14:39:56 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA12503; Thu, 11 May 95 23:38:49 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id XAA16952; Thu, 11 May 1995 23:50:14 +0200 Message-Id: <199505112150.XAA16952@gilberto.physik.rwth-aachen.de> Subject: Re: bug in /usr/src/etc/rc (netstart) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 11 May 1995 23:50:13 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com (user alias) In-Reply-To: <199505111725.KAA10530@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 11, 95 10:25:39 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2934 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > > > > > > > netstart is started using sh /etc/netstart (that was a . /etc/netstart > > > > formerly and it used to work). Now, starting it with sh /etc/netstart > > > > $hostname is unknown and the consequences are quite unfriendly. > > > > > > Hostname should be set by /etc/sysconfig, /etc/sysconfig is .'ed into > > > /etc/rc. Infact all variables that where set in /etc/netstart should > > > now be set by /etc/sysconfig. > > > > > > Do you infact have /etc/sysconfig 1.11, /etc/rc 1.63 ? > > > > I checked again now definitely with both, sysconfig 1.11, rc 1.63 and > > when I have the sh /etc/netstart in rc the hostname is not being set. > > How should it ? I don't need to tell you that a sub shell does not inherit > > variables that are set in the parent unless the subshell is 'sourced'. > > > > It works ok if I replace sh with . (source) (which was in some > > earlier version of rc anyway). > > I don't like to repeat myself, but ``Hostname is set by /etc/sysconfig, > /etc/sysconfig is sourced by /etc/rc''. I know all about sub shell vs > sourced file and the effects on variables. I have been writting /etc/rc > files for 15 years. I didn't put this in doubt. > > Just where are you setting $hostname at? If your not doing it at about Exactly there I'm setting hostname. > line 61 of /etc/sysconfig your not doing it the right way!!! > > You will note that at line 75 of /etc/rc the file /etc/sysconf is sourced > into /etc/rc which means $hostname is defined. $hostname (the variable) is defined for rc but not for netstart and when the hostname is set by netstart by the /sbin/hostname $hostname, then hostname *is* empty the way it is being done currently. Excuse me! I'm well aware of myname and defaultrouter being gone and I don't have them any longer. rc sources sysconfig. So rc knows $hostname (the variable). rc shells netstart but the variable $hostname *is* empty in netstart where the actual hostname is being set via the hostname $hostname command. Let's take this little example: let r be rc let s be sysconfig let n bet netstart -------- r --------- #!/bin/sh . s sh n -------- s --------- #!/bin/sh hostname=foo -------- n --------- #!/bin/sh - echo $hostname Now execute r and you will find the the echo in n is empty. A sixpack of beer that something is wrong with the current rc/sysconfig/net start combo. > > You will also note that this is the same way that /etc/netstart now > gets this value from /etc/sysconfig. > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Thu May 11 14:43:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA15324 for current-outgoing; Thu, 11 May 1995 14:43:08 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA15315 for ; Thu, 11 May 1995 14:42:58 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id OAA13278; Thu, 11 May 1995 14:42:35 -0700 From: "Rodney W. Grimes" Message-Id: <199505112142.OAA13278@gndrsh.aac.dev.com> Subject: Re: bug in /usr/src/etc/rc (netstart) To: kuku@gilberto.physik.rwth-aachen.de Date: Thu, 11 May 1995 14:42:34 -0700 (PDT) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199505112150.XAA16952@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at May 11, 95 11:50:13 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3405 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > > > > > > > > > > > > > > netstart is started using sh /etc/netstart (that was a . /etc/netstart > > > > > formerly and it used to work). Now, starting it with sh /etc/netstart > > > > > $hostname is unknown and the consequences are quite unfriendly. > > > > > > > > Hostname should be set by /etc/sysconfig, /etc/sysconfig is .'ed into > > > > /etc/rc. Infact all variables that where set in /etc/netstart should > > > > now be set by /etc/sysconfig. > > > > > > > > Do you infact have /etc/sysconfig 1.11, /etc/rc 1.63 ? > > > > > > I checked again now definitely with both, sysconfig 1.11, rc 1.63 and > > > when I have the sh /etc/netstart in rc the hostname is not being set. > > > How should it ? I don't need to tell you that a sub shell does not inherit > > > variables that are set in the parent unless the subshell is 'sourced'. > > > > > > It works ok if I replace sh with . (source) (which was in some > > > earlier version of rc anyway). > > > > I don't like to repeat myself, but ``Hostname is set by /etc/sysconfig, > > /etc/sysconfig is sourced by /etc/rc''. I know all about sub shell vs > > sourced file and the effects on variables. I have been writting /etc/rc > > files for 15 years. > > I didn't put this in doubt. > > > > > Just where are you setting $hostname at? If your not doing it at about > > Exactly there I'm setting hostname. > > > line 61 of /etc/sysconfig your not doing it the right way!!! > > > > You will note that at line 75 of /etc/rc the file /etc/sysconf is sourced > > into /etc/rc which means $hostname is defined. > > $hostname (the variable) is defined for rc but not for netstart and when the > hostname is set by netstart by the /sbin/hostname $hostname, then > hostname *is* empty the way it is being done currently. Excuse me! > I'm well aware of myname and defaultrouter being gone and I don't have them > any longer. > > rc sources sysconfig. So rc knows $hostname (the variable). > rc shells netstart but the variable $hostname *is* empty in netstart > where the actual hostname is being set via the hostname $hostname command. > > > Let's take this little example: > > let r be rc > let s be sysconfig > let n bet netstart > > -------- r --------- > #!/bin/sh > . s > sh n > -------- s --------- > #!/bin/sh > hostname=foo > -------- n --------- > #!/bin/sh - You missed: . s at line 8, the very first thing done. > echo $hostname > > Now execute r and you will find the the echo in n is empty. > > A sixpack of beer that something is wrong with the current rc/sysconfig/net > start combo. I don't drink, but look at line 8 of /etc/netstart: . /etc/sysconfig > > > > > > You will also note that this is the same way that /etc/netstart now > > gets this value from /etc/sysconfig. > > > > -- > > Rod Grimes rgrimes@gndrsh.aac.dev.com > > Accurate Automation Company Custom computers for FreeBSD > > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 > 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d > e:/usr/src/sys/compile/BLUESGUS i386 > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu May 11 14:49:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA15431 for current-outgoing; Thu, 11 May 1995 14:49:45 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA15425 for ; Thu, 11 May 1995 14:49:39 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA12541; Thu, 11 May 95 23:49:25 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id AAA17010; Fri, 12 May 1995 00:00:50 +0200 Message-Id: <199505112200.AAA17010@gilberto.physik.rwth-aachen.de> Subject: Re: bug in /usr/src/etc/rc (netstart) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Fri, 12 May 1995 00:00:49 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com (user alias) In-Reply-To: <199505112142.OAA13278@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 11, 95 02:42:34 pm From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1252 Sender: current-owner@FreeBSD.org Precedence: bulk > > Let's take this little example: > > > > let r be rc > > let s be sysconfig > > let n bet netstart > > > > -------- r --------- > > #!/bin/sh > > . s > > sh n > > -------- s --------- > > #!/bin/sh > > hostname=foo > > -------- n --------- > > #!/bin/sh - > > You missed: > . s > at line 8, the very first thing done. AARRGGH! I was using netstart 1.26 all the time. Mea culpa. Thousand excuses! > > > echo $hostname > > > > Now execute r and you will find the the echo in n is empty. > > > > A sixpack of beer that something is wrong with the current rc/sysconfig/net > > start combo. > > I don't drink, but look at line 8 of /etc/netstart: > . /etc/sysconfig > > > -- > > > Rod Grimes rgrimes@gndrsh.aac.dev.com > > > Accurate Automation Company Custom computers for FreeBSD > > > > > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > Sorry for the confusion. Shame on me. Red face ///// --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Thu May 11 19:27:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA24677 for current-outgoing; Thu, 11 May 1995 19:27:38 -0700 Received: from netcom.netcom.com (root@netcom.netcom.com [192.100.81.100]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA24671 for ; Thu, 11 May 1995 19:27:35 -0700 Received: by netcom.netcom.com (8.6.12/Netcom) id TAA08603; Thu, 11 May 1995 19:19:53 -0700 Date: Thu, 11 May 1995 19:19:52 -0700 (PDT) From: Manfred Antar X-Sender: mantar@netcom To: FreeBSD current Subject: new psm0 does not work Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk i changed the line in my kernel config file for PS/2 mouse to : device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr as per new LINT file.now at boot up i get this message: psm0 not probed due to IO address conflict with sc0 at 0x60 and no more X.my system is current as of 17:00 5/11/95.i've try using the old config file with: options ALLOW_CONFLICT_IOADDR device psm0 at isa? port "IO_KBD" irq 12 vector psmintr and no go. any help would be appreciated Thanks ============================= | mantar@netcom.com | | Ph. (415) 647-4843 | ============================= From owner-freebsd-current Thu May 11 19:43:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA25607 for current-outgoing; Thu, 11 May 1995 19:43:30 -0700 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA25597 for ; Thu, 11 May 1995 19:43:27 -0700 Received: from ast.com by relay1.UU.NET with SMTP id QQypio15308; Thu, 11 May 1995 22:43:23 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA17001 (5.67b/IDA-1.5 for uunet!freebsd.org!freebsd-current); Thu, 11 May 1995 19:43:27 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Thu, 11 May 95 21:44 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0s9kfA-0004vwC; Thu, 11 May 95 21:41 CDT Message-Id: Date: Thu, 11 May 95 21:41 CDT To: freebsd-current@FreeBSD.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Thu May 11 1995, 21:41:11 CDT Subject: Taylor UUCP and flow control Sender: current-owner@FreeBSD.org Precedence: bulk [0]From: Bruce Evans [0]The correct setting is system dependent. That's why everything in rc.serial [0]is commented out by default. The setting of dtrwait is safe enough but [0]the setting of crtscts may cause problems if the modem doesn't assert CTS [0]except when there is carrier. That reminds me. Taylor UUCP 1.04 and 1.05 both deliberatly disable hardware flow control (-crtscts) when it is running. You have to change the UUCP source (as far as I know) to get hardware flow control to remain on. This happens for incoming and outgoing UUCP sessions. This is the patch I use: *** serial.c.00 Mon May 1 22:43:31 1995 --- serial.c Mon May 1 23:01:54 1995 *************** *** 205,211 **** | OFILL | OFDEL | NLDLY | CRDLY | TABDLY | BSDLY \ | VTDLY | FFDLY) #define ICLEAR_CFLAG (CBAUD | CSIZE | PARENB | PARODD) ! #define ISET_CFLAG (CS8 | CREAD | HUPCL) #define ICLEAR_LFLAG (ISIG | ICANON | XCASE | ECHO | ECHOE | ECHOK \ | ECHONL | NOFLSH | PENDIN) #endif --- 205,212 ---- | OFILL | OFDEL | NLDLY | CRDLY | TABDLY | BSDLY \ | VTDLY | FFDLY) #define ICLEAR_CFLAG (CBAUD | CSIZE | PARENB | PARODD) ! #define ISET_CFLAG (CS8 | CREAD | HUPCL | CRTS_IFLOW | CCTS_OFLOW) ! /*<1>#define ISET_CFLAG (CS8 | CREAD | HUPCL)*/ #define ICLEAR_LFLAG (ISIG | ICANON | XCASE | ECHO | ECHOE | ECHOK \ | ECHONL | NOFLSH | PENDIN) #endif *************** *** 215,221 **** | PARMRK | IMAXBEL) #define ICLEAR_OFLAG (OPOST) #define ICLEAR_CFLAG (CSIZE | PARENB | PARODD) ! #define ISET_CFLAG (CS8 | CREAD | HUPCL) #define ICLEAR_LFLAG (ECHO | ECHOE | ECHOK | ECHONL | ICANON | IEXTEN \ | ISIG | NOFLSH | TOSTOP | PENDIN) #endif --- 216,223 ---- | PARMRK | IMAXBEL) #define ICLEAR_OFLAG (OPOST) #define ICLEAR_CFLAG (CSIZE | PARENB | PARODD) ! #define ISET_CFLAG (CS8 | CREAD | HUPCL | CRTS_IFLOW | CCTS_OFLOW) ! /*<1>#define ISET_CFLAG (CS8 | CREAD | HUPCL)*/ #define ICLEAR_LFLAG (ECHO | ECHOE | ECHOK | ECHONL | ICANON | IEXTEN \ | ISIG | NOFLSH | TOSTOP | PENDIN) #endif *************** *** 3057,3064 **** don't send XON/XOFF characters but we do recognize them. */ if ((q->snew.c_cflag & CRTSCTS) != 0) { ! iset = IXON; ! iclear = IXOFF; fdo = TRUE; break; } --- 3059,3068 ---- don't send XON/XOFF characters but we do recognize them. */ if ((q->snew.c_cflag & CRTSCTS) != 0) { ! /*<1> iset = IXON;*/ ! iset = 0; /*<1>I don't want XON (DC1) eaten!*/ ! /*<1> iclear = IXOFF;*/ ! iclear = IXON | IXOFF; /*<1>*/ fdo = TRUE; break; } The above patch forces hardware full-duplex RTS/CTS flow control on during inbound and outbound UUCP sessions. I have to reapply this patch every time I upgrade my FreeBSD systems. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Fri May 12 04:30:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA27402 for current-outgoing; Fri, 12 May 1995 04:30:19 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA27381 for ; Fri, 12 May 1995 04:29:53 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA23896; Fri, 12 May 1995 21:25:27 +1000 Date: Fri, 12 May 1995 21:25:27 +1000 From: Bruce Evans Message-Id: <199505121125.VAA23896@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, uhclem%nemesis@fw.ast.com Subject: Re: Taylor UUCP and flow control Sender: current-owner@FreeBSD.org Precedence: bulk >[0]The correct setting is system dependent. That's why everything in rc.serial >[0]is commented out by default. The setting of dtrwait is safe enough but >[0]the setting of crtscts may cause problems if the modem doesn't assert CTS >[0]except when there is carrier. >That reminds me. Taylor UUCP 1.04 and 1.05 both deliberatly disable >hardware flow control (-crtscts) when it is running. You have to change >the UUCP source (as far as I know) to get hardware flow control to remain >on. This happens for incoming and outgoing UUCP sessions. I think uucp has an option to set crtscts. It certainly has some ifdefs involving it. The lock bits in ttyid* are meant for handling this problem in applications that don't support crtscts properly. You can set the crtscts bits in ttyid* to lock the initial value of crtscts and the crtscts bits in ttyld* to set the initial value to on. This is done in the modem() example in /etc/rc.serial. The problems occur when you set or lock crtscts for a device that doesn't support it, e.g., if crtscts is locked on on a mouse port, then X will hang forever waiting for CTS. Bruce From owner-freebsd-current Fri May 12 05:53:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA01074 for current-outgoing; Fri, 12 May 1995 05:53:01 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA01041 for ; Fri, 12 May 1995 05:52:35 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id WAA15177 for current@freebsd.org; Fri, 12 May 1995 22:51:57 +1000 From: michael butler Message-Id: <199505121251.WAA15177@asstdc.scgt.oz.au> Subject: sendmail 8.6.12 ? To: current@FreeBSD.org Date: Fri, 12 May 1995 22:51:56 +1000 (EST) Reply-To: imb@scgt.oz.au X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 616 Sender: current-owner@FreeBSD.org Precedence: bulk Could someone please grab the 8.6.12 sendmail patches and update -current ? It helps to make the ident code work and .. from the patch file .. 8.6.12/8.6.12 95/03/28 Fix to IDENT code (it was getting the size of the reply buffer too small, so nothing was ever accepted). Fix from several people, including Allan Johannesen, Shane Castle of the Boulder County Information Services, and Jeff Smith of Warwick University (all arrived within a few hours of each other!). Fix a problem that could cause large jobs to run out of file descriptors on systems that use vfork() rather than fork(). From owner-freebsd-current Fri May 12 10:23:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA13981 for current-outgoing; Fri, 12 May 1995 10:23:34 -0700 Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA13973 for ; Fri, 12 May 1995 10:23:33 -0700 Received: from ast.com by relay4.UU.NET with SMTP id QQypkv24231; Fri, 12 May 1995 13:23:20 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA24350 (5.67b/IDA-1.5 for uunet!FreeBSD.org!freebsd-current); Fri, 12 May 1995 10:23:26 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Fri, 12 May 95 12:24 CDT Received: from trsvax by nemesis.lonestar.org with uucp (Smail3.1.27.1 #18) id m0s9yCj-0004vQC; Fri, 12 May 95 12:08 CDT Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Fri, 12 May 95 11:40 CDT Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Fri, 12 May 95 11:38 CDT Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA01142; Fri, 12 May 95 10:30:29 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505121630.AA01142@cs.weber.edu> Subject: Re: Taylor UUCP and flow control To: uhclem%nemesis@fw.ast.com (Frank Durda IV) Date: Fri, 12 May 95 10:30:28 MDT Cc: freebsd-current@FreeBSD.org (Frank Durda IV) In-Reply-To: from "Frank Durda IV" at May 11, 95 09:41:00 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk ] That reminds me. Taylor UUCP 1.04 and 1.05 both deliberatly disable ] hardware flow control (-crtscts) when it is running. You have to change ] the UUCP source (as far as I know) to get hardware flow control to remain ] on. This happens for incoming and outgoing UUCP sessions. This is because most systems don't handle CTS/RTS correctly prior to DCD being raised on outgoing calls, and act wierd if DCD is lost while CTS or RTS has been deasserted. ] This is the patch I use: [ ... patch elided ... ] ] The above patch forces hardware full-duplex RTS/CTS flow control on during ] inbound and outbound UUCP sessions. ] ] I have to reapply this patch every time I upgrade my FreeBSD systems. I'd be more comfortable if this patch became active only as a command line option whose default was off. This would also make it more likely to be included in the main line so that BSD doesn't have to carry it around on a vendor branch. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri May 12 11:09:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA16832 for current-outgoing; Fri, 12 May 1995 11:09:07 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA16826 for ; Fri, 12 May 1995 11:09:03 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA01296; Fri, 12 May 1995 11:07:14 -0700 From: "Rodney W. Grimes" Message-Id: <199505121807.LAA01296@gndrsh.aac.dev.com> Subject: Re: sendmail 8.6.12 ? To: imb@scgt.oz.au Date: Fri, 12 May 1995 11:07:14 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505121251.WAA15177@asstdc.scgt.oz.au> from "michael butler" at May 12, 95 10:51:56 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1175 Sender: current-owner@FreeBSD.org Precedence: bulk > > Could someone please grab the 8.6.12 sendmail patches and update -current ? > It helps to make the ident code work and .. from the patch file .. > > 8.6.12/8.6.12 95/03/28 > Fix to IDENT code (it was getting the size of the reply buffer > too small, so nothing was ever accepted). Fix from several > people, including Allan Johannesen, Shane Castle of the > Boulder County Information Services, and Jeff Smith of > Warwick University (all arrived within a few hours of > each other!). > Fix a problem that could cause large jobs to run out of > file descriptors on systems that use vfork() rather > than fork(). If you give me a quick pointer to sendmail 8.6.11 and 8.6.12 I will correct the cvs import of 8.6.11 so that I can cleanly import 8.6.12. We have announced the intended code freeze date and I will have to get a ruling on doing this import this late in the game. I do not view this as a critical bug fix, so this may very well get delayed until after 2.0.5 release is cut. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Fri May 12 13:10:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA20507 for current-outgoing; Fri, 12 May 1995 13:10:45 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA20498 for ; Fri, 12 May 1995 13:10:36 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA10071; Fri, 12 May 1995 13:13:36 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA00211; Fri, 12 May 1995 13:10:35 -0700 Message-Id: <199505122010.NAA00211@corbin.Root.COM> To: "Rodney W. Grimes" cc: imb@scgt.oz.au, current@FreeBSD.org Subject: Re: sendmail 8.6.12 ? In-reply-to: Your message of "Fri, 12 May 95 11:07:14 PDT." <199505121807.LAA01296@gndrsh.aac.dev.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 12 May 1995 13:10:31 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >If you give me a quick pointer to sendmail 8.6.11 and 8.6.12 I will >correct the cvs import of 8.6.11 so that I can cleanly import 8.6.12. > >We have announced the intended code freeze date and I will have to >get a ruling on doing this import this late in the game. I do not >view this as a critical bug fix, so this may very well get delayed >until after 2.0.5 release is cut. Let's wait. It's not 2.0.5 material, but should be in 2.1. -DG From owner-freebsd-current Fri May 12 13:15:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA20769 for current-outgoing; Fri, 12 May 1995 13:15:12 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA20762 for ; Fri, 12 May 1995 13:15:07 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id QAA11912; Fri, 12 May 1995 16:16:03 -0400 From: Peter Dufault Message-Id: <199505122016.QAA11912@hda.com> Subject: Strange LKM problems To: current@FreeBSD.org Date: Fri, 12 May 1995 16:16:03 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1743 Sender: current-owner@FreeBSD.org Precedence: bulk I have occasional failures loading up LKM modules, without any obvious reasons. I'm using this "./in" script to install the module: > desmond# cat ./in > modload -v -A /kernel -e sermux_init -o sermux.out sermux_mod.o > ./setldisc /dev/ttyd4 7 > ./setldisc /dev/ttyd5 7 > desmond# And look at this failure: > desmond# ./in > modload: not an a.out format file > TIOCSETD: Operation not supported by device > TIOCSETD: Operation not supported by device > desmond# > desmond# sync > desmond# rm sermux.out > desmond# ./in > Registered line discipline at 7. > sermux loaded. > Module loaded as ID 1 Here you see two load attempts in a row with nothing else happening in between them, and note that it worked fine the second time without my doing anything. In another window I checked the output file on the NFS server that has the object on it: > hda# nm *.out > nm: sermux.out: not object file or archive. so after it failed the first time it wasn't an object file. (I stupidly didn't ls it; I bet it was null). When the load worked it was fine. This is on an NFS mounted partition; the system that is doing the loading is the client. I also had a random crash during the load, and then checking the .out file I had a complaint about the .stab entries. It is as if the file is short sometimes. I've tried to reproduce the problem by continuously loading and unloading the module in a command script but without any luck: If it is going to fail at all, it is the first time after a reboot and then I can't get it to happen again. Any ideas? It is really odd. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri May 12 13:30:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA21337 for current-outgoing; Fri, 12 May 1995 13:30:40 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA21328 for ; Fri, 12 May 1995 13:30:35 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA15044; Fri, 12 May 1995 16:30:26 -0400 Date: Fri, 12 May 1995 16:30:26 -0400 From: Garrett Wollman Message-Id: <9505122030.AA15044@halloran-eldar.lcs.mit.edu> To: Peter Dufault Cc: current@FreeBSD.org Subject: Strange LKM problems In-Reply-To: <199505122016.QAA11912@hda.com> References: <199505122016.QAA11912@hda.com> Sender: current-owner@FreeBSD.org Precedence: bulk < said: >> modload -v -A /kernel -e sermux_init -o sermux.out sermux_mod.o Try `-o /tmp/sermux.out'... > This is on an NFS mounted partition; the system that is doing the > loading is the client. Hmmm. Sounds like it might be an NFS bug (but then again it might not). It does seem inexplicably odd that it should only happen immediately after boot... I've never seen this happen for filesystem modules... -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Fri May 12 15:49:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA12357 for current-outgoing; Fri, 12 May 1995 15:49:14 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA12351 for ; Fri, 12 May 1995 15:49:13 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id AAA13942 ; Sat, 13 May 1995 00:49:09 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id AAA24541 ; Sat, 13 May 1995 00:49:08 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199505122249.AAA24541@blaise.ibp.fr> Subject: Re: sendmail 8.6.12 ? To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 13 May 1995 00:49:08 +0200 (MET DST) Cc: imb@scgt.oz.au, current@FreeBSD.org In-Reply-To: <199505121807.LAA01296@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 12, 95 11:07:14 am X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 477 Sender: current-owner@FreeBSD.org Precedence: bulk > If you give me a quick pointer to sendmail 8.6.11 and 8.6.12 I will > correct the cvs import of 8.6.11 so that I can cleanly import 8.6.12. ftp://ftp.cs.berkeley.edu/ucb/sendmail/* should be near you :-) Why not simply import 8.6.12 ? I don't think we made signifiant changes and we're not the maintainers of the code anyway. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-current Fri May 12 17:16:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA14808 for current-outgoing; Fri, 12 May 1995 17:16:31 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA14800 for ; Fri, 12 May 1995 17:16:23 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id RAA02472; Fri, 12 May 1995 17:14:54 -0700 From: "Rodney W. Grimes" Message-Id: <199505130014.RAA02472@gndrsh.aac.dev.com> Subject: Re: sendmail 8.6.12 ? To: roberto@blaise.ibp.fr (Ollivier Robert) Date: Fri, 12 May 1995 17:14:54 -0700 (PDT) Cc: imb@scgt.oz.au, current@FreeBSD.org In-Reply-To: <199505122249.AAA24541@blaise.ibp.fr> from "Ollivier Robert" at May 13, 95 00:49:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 738 Sender: current-owner@FreeBSD.org Precedence: bulk > > > If you give me a quick pointer to sendmail 8.6.11 and 8.6.12 I will > > correct the cvs import of 8.6.11 so that I can cleanly import 8.6.12. > > ftp://ftp.cs.berkeley.edu/ucb/sendmail/* should be near you :-) Thanks, that was the one I was looking for. > > Why not simply import 8.6.12 ? I don't think we made signifiant changes > and we're not the maintainers of the code anyway. Because we have a tag that says this should be 8.6.11 but from the looks of things it is not quite right, which makes it hard to apply updates if files got screwed on the vendor branch. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Fri May 12 19:38:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA21013 for current-outgoing; Fri, 12 May 1995 19:38:34 -0700 Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA21006 for ; Fri, 12 May 1995 19:38:32 -0700 Received: from ast.com by relay4.UU.NET with SMTP id QQypmg22198; Fri, 12 May 1995 22:38:29 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA00187 (5.67b/IDA-1.5 for uunet!FreeBSD.org!freebsd-current); Fri, 12 May 1995 19:38:29 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Fri, 12 May 95 21:39 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0sA4xA-0004w0C; Fri, 12 May 95 19:21 CDT Message-Id: Date: Fri, 12 May 95 19:21 CDT To: freebsd-current@FreeBSD.org, terry@cs.weber.edu From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Fri May 12 1995, 19:21:07 CDT Subject: Re: Taylor UUCP Sender: current-owner@FreeBSD.org Precedence: bulk [0]From: uhclem%nemesis@fw.ast.com (Frank Durda IV) [0]That reminds me. Taylor UUCP 1.04 and 1.05 both deliberatly disable [0]hardware flow control (-crtscts) when it is running. You have to change [0]the UUCP source (as far as I know) to get hardware flow control to remain [0]on. This happens for incoming and outgoing UUCP sessions. [1]From: terry@cs.weber.edu (Terry Lambert) [1]This is because most systems don't handle CTS/RTS correctly prior to DCD [1]being raised on outgoing calls, and act wierd if DCD is lost while CTS [1]or RTS has been deasserted. Whatever. I was more concerned with the data part of the call, which is the point when Taylor turns this off. Nearly all of the other System V systems I have seen leave RTS/CTS active if you wanted it on. Even SCO. [0]I have to reapply this patch every time I upgrade my FreeBSD systems. [1]I'd be more comfortable if this patch became active only as a command [1]line option whose default was off. This would also make it more likely [1]to be included in the main line so that BSD doesn't have to carry it [1]around on a vendor branch. I wasn't suggesting including it *anywhere* in the production tree in its current form. Instead I was offering it as a way to fix problems that bother Taylor UUCP users every day who are using high baud modems (like Telebits or V.34). FYI, I have also gotten eight or nine letters thanking me for the immediate improvement they got (I was impressed). So maybe the change is more valuable to those of us who still have to move news and mail around via UUCP. Perhaps Ian will eventually implement something to handle this from the sys or dial file, or at least change Taylor UUCP to *not* fiddle with the settings that were set prior to it starting. But for now, that patch is a lifesaver for heavy UUCP users. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Fri May 12 23:42:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA04077 for current-outgoing; Fri, 12 May 1995 23:42:25 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA04054 for ; Fri, 12 May 1995 23:41:58 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id QAA02566 for current@freebsd.org; Sat, 13 May 1995 16:41:14 +1000 From: michael butler Message-Id: <199505130641.QAA02566@asstdc.scgt.oz.au> Subject: kernel panic w/NFS To: current@FreeBSD.org Date: Sat, 13 May 1995 16:41:12 +1000 (EST) Reply-To: imb@scgt.oz.au X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 465 Sender: current-owner@FreeBSD.org Precedence: bulk Whilst copying some files between machines over NFS, I accidentally managed to reboot the server of the pair .. the client then suffered a kernel panic as a direct result. Is it possible to prevent the client from doing this when the server "goes away" ? Whilst it doesn't worry me for local connections, it is conceivable that a link over an ISDN link might also exhibit this behaviour if it goes down at an inappropriate time (as they usually do :-(), michael From owner-freebsd-current Sat May 13 02:17:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA14188 for current-outgoing; Sat, 13 May 1995 02:17:08 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA14160 for ; Sat, 13 May 1995 02:16:43 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA22035; Sat, 13 May 1995 19:14:31 +1000 Date: Sat, 13 May 1995 19:14:31 +1000 From: Bruce Evans Message-Id: <199505130914.TAA22035@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, terry@cs.weber.edu, uhclem%nemesis@fw.ast.com Subject: Re: Taylor UUCP Sender: current-owner@FreeBSD.org Precedence: bulk >[1]This is because most systems don't handle CTS/RTS correctly prior to DCD >[1]being raised on outgoing calls, and act wierd if DCD is lost while CTS >[1]or RTS has been deasserted. >Whatever. I was more concerned with the data part of the call, which >is the point when Taylor turns this off. Nearly all of the other >System V systems I have seen leave RTS/CTS active if you wanted it on. >Even SCO. Actually it seems to turn crtscts on for the sender and off for the receiver, at least when the receiver is spawned by getty. You are supposed to be able to specify the flow control in the `port' file (hardflow y) but it defaults to on anyway. I think the problem is that uucico doesn't know the port when it is spawned by getty, and the port info doesn't get initialized right. Other bugs: 1) You are supposed to be able to check and convert configurations using uuchk and uuconv, but these are installed in the wrong place /usr/libexec/uucp with the wrong ownership uucp:uucp and the wrong permissions 550. 2) If /usr is nfs-mounted and root attempts to run /usr/libexec/uuchk, then the following error is logged: vnode_pager_input: I/O read error vm_fault: pager input (probably hardware) error, PID 212 failure Apparently FreeBSD still has the nfs bug that root can open nfs-mounted files that can't be read (the file permissions lie), and the vm system is as confused about this as everything else. Bruce From owner-freebsd-current Sat May 13 06:55:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA01369 for current-outgoing; Sat, 13 May 1995 06:55:34 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA01362 for ; Sat, 13 May 1995 06:55:31 -0700 Received: by sequent.kiae.su id AA11131 (5.65.kiae-2 ); Sat, 13 May 1995 16:05:56 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 13 May 95 16:05:55 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id QAA00637; Sat, 13 May 1995 16:03:15 +0400 To: Bruce Evans , freebsd-current@FreeBSD.org, terry@cs.weber.edu, uhclem%nemesis@fw.ast.com References: <199505130914.TAA22035@godzilla.zeta.org.au> In-Reply-To: <199505130914.TAA22035@godzilla.zeta.org.au>; from Bruce Evans at Sat, 13 May 1995 19:14:31 +1000 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sat, 13 May 1995 16:03:14 +0400 (MSD) X-Mailer: Mail/@ [v2.35 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: Taylor UUCP Lines: 19 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 747 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199505130914.TAA22035@godzilla.zeta.org.au> Bruce Evans writes: >Other bugs: >1) You are supposed to be able to check and convert configurations using >uuchk and uuconv, but these are installed in the wrong place >/usr/libexec/uucp with the wrong ownership uucp:uucp and the wrong >permissions 550. Wrong place: agree. Mode and permissions: disagree. Normal user must not be able to see phones and passwords from system configuration. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sat May 13 11:25:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA07999 for current-outgoing; Sat, 13 May 1995 11:25:20 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA07993 for ; Sat, 13 May 1995 11:25:18 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id OAA15099; Sat, 13 May 1995 14:26:08 -0400 From: Peter Dufault Message-Id: <199505131826.OAA15099@hda.com> Subject: Re: Strange LKM problems To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Sat, 13 May 1995 14:26:07 -0400 (EDT) Cc: current@FreeBSD.org In-Reply-To: <9505122030.AA15044@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at May 12, 95 04:30:26 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1417 Sender: current-owner@FreeBSD.org Precedence: bulk Garrett Wollman writes: > > < said: > > >> modload -v -A /kernel -e sermux_init -o sermux.out sermux_mod.o > > Try `-o /tmp/sermux.out'... > > > This is on an NFS mounted partition; the system that is doing the > > loading is the client. > > Hmmm. Sounds like it might be an NFS bug (but then again it might > not). It does seem inexplicably odd that it should only happen > immediately after boot... > > I've never seen this happen for filesystem modules... I got it again. Again it was after a boot up. The sermux.out file is corrupt: the first 8K of the output is 0. I saved that file, then just installed again and it worked fine. Both systems are (recent) -current, the server using a 3C509 and the client an NE2000. I'm not getting any error messages from either system. I'm going to try Garrett's suggestion, which I bet will make it go away but isn't so good since I won't have the .out on the server in case I want to poke around in the name list. It is hard to imagine I'm having general NFS problems, since I installed this system using NFS, and then copied over all the source and binaries over with NFS and didn't noticed any problems. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Sat May 13 14:00:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA12318 for current-outgoing; Sat, 13 May 1995 14:00:29 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA12310 ; Sat, 13 May 1995 14:00:27 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: current@freefall.cdrom.com cc: ache@freefall.cdrom.com Subject: Bug in ncftp passive mode handling? Date: Sat, 13 May 1995 14:00:26 -0700 Message-ID: <12309.800398826@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk >From the man page in ncftp: -P toggle passive mode (defaults to on). Useful for work behind firewalls. This tells me that it's ON by default, so ncftp without -P should be passive, right? Hmmmmm! Well, sitting here behind the cisco firewall: chein-as-pc1 {911}# ncftp ftp://freebsd.org/pub/FreeBSD/packages/editors NcFTP 1.9.4 (April 15, 1995) by Mike Gleason, NCEMRSoft. Tip: Don't put a site in your .ncftprc unless you want an 'init' macro. The recent-file saves sites with the last directory you were in, unlike the rc file, while still letting you use sitename abbreviations. freebsd.org:/pub/FreeBSD/packages/editors (Mail) ncftp>ls So then we try it with -P: chein-as-pc1 {916}# ncftp -P ftp://freebsd.org/pub/FreeBSD/packages/editors NcFTP 1.9.4 (April 15, 1995) by Mike Gleason, NCEMRSoft. Tip: You can put set commands in your .ncftprc, by adding lines such as '#set local-dir /usr/tmp' to the file, which will be run at startup. freebsd.org:/pub/FreeBSD/packages/editors (Mail) ncftp>ls aXe-6.1.2.tgz@ mule-2.2.2.tgz@ xhtml-dynamic.tgz@ emacs-19.28.tgz@ vile-5.2.tgz@ xhtml-static.tgz@ jove-4.16b.tgz@ xemacs-19.11.tgz@ xvile-5.2.tgz@ freebsd.org:/pub/FreeBSD/packages/editors (Mail) ncftp> Works fine! Our standard ftp doesn't default to passive mode either - you need to do a `passive' command first. What's the concensus on this? libftp, BTW, doesn't appear to handle passive mode _at all_! Oh well, so much for that particular option in the install.. :-( JOrdan From owner-freebsd-current Sat May 13 15:05:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA13391 for current-outgoing; Sat, 13 May 1995 15:05:20 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA13384 ; Sat, 13 May 1995 15:05:17 -0700 Received: by sequent.kiae.su id AA00540 (5.65.kiae-2 ); Sun, 14 May 1995 02:01:07 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 14 May 95 02:01:06 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id BAA02186; Sun, 14 May 1995 01:59:08 +0400 To: current@freefall.cdrom.com, "Jordan K. Hubbard" References: <12309.800398826@freefall.cdrom.com> In-Reply-To: <12309.800398826@freefall.cdrom.com>; from "Jordan K. Hubbard" at Sat, 13 May 1995 14:00:26 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sun, 14 May 1995 01:59:08 +0400 (MSD) X-Mailer: Mail/@ [v2.35 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: Bug in ncftp passive mode handling? Lines: 24 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 837 Sender: current-owner@FreeBSD.org Precedence: bulk In message <12309.800398826@freefall.cdrom.com> Jordan K. Hubbard writes: >>From the man page in ncftp: > -P toggle passive mode (defaults to on). Useful for > work behind firewalls. >This tells me that it's ON by default, so ncftp without -P should be >passive, right? No, manpage lies. >What's the concensus on this? libftp, BTW, doesn't appear to handle >passive mode _at all_! Oh well, so much for that particular option >in the install.. :-( It handles it, at least PASV command appearse in sourses. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sat May 13 17:34:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA16651 for current-outgoing; Sat, 13 May 1995 17:34:25 -0700 Received: from mpp.com (dialup-3-188.gw.umn.edu [134.84.101.188]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA16644 for ; Sat, 13 May 1995 17:34:15 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id TAA00204; Sat, 13 May 1995 19:31:55 -0500 From: Mike Pritchard Message-Id: <199505140031.TAA00204@mpp.com> Subject: Re: bin/389: Problem #FDIV024 To: bde@zeta.org.au (Bruce Evans) Date: Sat, 13 May 1995 19:31:55 -0500 (CDT) Cc: uhclem@nemesis.lonestar.org, current@FreeBSD.org In-Reply-To: <199505090808.SAA00484@godzilla.zeta.org.au> from "Bruce Evans" at May 9, 95 06:08:42 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2674 Sender: current-owner@FreeBSD.org Precedence: bulk > >>Number: 389 > >>Category: bin > >>Synopsis: Simultaneous creation/deletion of dirs corrupts filesystem [FDIV024] > > I was able to reproduce the hang under -current: > > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 15 1669 159 0 -14 0 172 488 uihget D+ v2 0:00.05 ls -Fg > 15 1619 160 2 -14 0 296 616 ufslk2 D v3 0:02.19 tar xf ../bin > 15 1624 160 0 -18 0 296 620 vodead D v3 0:00.88 tar xf ../bin >... > 15 1678 160 1 -14 0 160 476 ufslk2 D+ v3 0:00.04 ls -Fg > > The problems seem to be easier to reproduce on a small file system. I didn't > see any on a new 512MB file system but I soon saw them on a 20000 block file > system using bin.tar created from the current /usr/src/bin and running lots > of tar xf's and rm -rf's concurrently. > > This was running as non-root. As root you have to worry about something > unlinking "." and ".." directory entries. I don't think anything actually > does, but tar --unlink might. > > Bruce I think I just duplicated the problem in a slightly different manner with a -current kernel that is about 2.5 weeks old at this point. I was in /usr/src doing a "make world", and it had just gotten to the point where it was attempting to compile stuff. I was also running a "du -s /usr" at the same time. The compile blew off with "bad file descriptor". The du also blew off somewhere in the same time frame, complaining about files in /usr/src. Checking the directory the build failed in showed that I had several files that were still present in the directory, but the i-nodes had been released, thus the "bad file descriptor" problems. fsck reported about 4 files in the bad build directory that pointed to unallocated i-nodes, and a few others in some other directories. All the files were either binaries or .o's that would have been removed by "make clean". All my file systems were just fine about 10 hours ago when I last booted, and the machine was idle all day until I started the make/du, so I'm pretty sure that this is when the corruption took place. Since "du" is only opening up directories read-only, and all it does is call "stat" (via the fts* routines), it looks like something in the unlink/directory update routines isn't locking the directory properly, or releasing the lock a bit too soon. It also might have something to do with a stat() being active on the file being deleted. I was running as root in all of the above cases, in case anyone was wondering. -- Mike Pritchard pritc003@maroon.tc.umn.edu "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Sat May 13 21:27:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA23084 for current-outgoing; Sat, 13 May 1995 21:27:52 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA23078 for ; Sat, 13 May 1995 21:27:41 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA13885; Sun, 14 May 1995 14:24:31 +1000 Date: Sun, 14 May 1995 14:24:31 +1000 From: Bruce Evans Message-Id: <199505140424.OAA13885@godzilla.zeta.org.au> To: ache@astral.msk.su, bde@zeta.org.au, freebsd-current@FreeBSD.org, terry@cs.weber.edu, uhclem%nemesis@fw.ast.com Subject: Re: Taylor UUCP Sender: current-owner@FreeBSD.org Precedence: bulk >>uuchk and uuconv, but these are installed in the wrong place >>/usr/libexec/uucp with the wrong ownership uucp:uucp and the wrong >>permissions 550. >Wrong place: agree. >Mode and permissions: disagree. >Normal user must not be able to see phones and passwords from >system configuration. Phones and passwords are in /etc/uucp, not in libexec/uucp :-). The programs aren't setuid so they can't read /etc/uucp/* unless run by root. Bruce From owner-freebsd-current Sat May 13 22:42:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA24032 for current-outgoing; Sat, 13 May 1995 22:42:32 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA24026 for ; Sat, 13 May 1995 22:42:21 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA15966; Sun, 14 May 1995 15:36:49 +1000 Date: Sun, 14 May 1995 15:36:49 +1000 From: Bruce Evans Message-Id: <199505140536.PAA15966@godzilla.zeta.org.au> To: bde@zeta.org.au, pritc003@maroon.tc.umn.edu Subject: Re: bin/389: Problem #FDIV024 Cc: current@FreeBSD.org, uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk >> >>Number: 389 >> >>Category: bin >> >>Synopsis: Simultaneous creation/deletion of dirs corrupts filesystem [FDIV024] >> >> I was able to reproduce the hang under -current: >> >> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND >>... >> 15 1624 160 0 -18 0 296 620 vodead D v3 0:00.88 tar xf ../bin >>... >I think I just duplicated the problem in a slightly different manner >with a -current kernel that is about 2.5 weeks old at this point. David fixed the "vodead" sleep less than 2.5 weeks ago. The fix seems to work here. I never saw the file system corruption problems. Bruce From owner-freebsd-current Sat May 13 23:02:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA24203 for current-outgoing; Sat, 13 May 1995 23:02:20 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA24197 for ; Sat, 13 May 1995 23:02:15 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA16423; Sun, 14 May 1995 16:00:06 +1000 Date: Sun, 14 May 1995 16:00:06 +1000 From: Bruce Evans Message-Id: <199505140600.QAA16423@godzilla.zeta.org.au> To: hsu@clinet.fi Subject: Re: misc/403: FreeBSD 1-compiled tcsh, bash and zsh binaries dump on vt102 Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Number: 403 >>Category: misc >>Synopsis: FreeBSD 1-compiled tcsh, bash and zsh binaries dump on vt102 >>Description: > bash, zsh and tcsh print "Termcap entry too long" when setting >terminal type to vt102 (or larger like vt220). I don't know when this >changed and why, I recompiled the shells on FreeBSD 2 and they work >now. Some termcap entries are very long. In current libraries, tgetent() is more careful to discard junk (mostly spaces) so that the termcap entries are smaller than the braindamaged 1024 byte limit . Old binaries use old libraries so some termcap entries are larger than the limit. >>Fix: > >Recompile the stuff. I guess this isn't dangerous, just wondering >what has changed and will it affect other programs too (none noticed >yet)? The termcap entries are now more complete. Bruce