From owner-freebsd-current Sun Mar 26 00:18:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA03743 for current-outgoing; Sun, 26 Mar 1995 00:18:29 -0800 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 AAA03667; Sun, 26 Mar 1995 00:15:17 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id KAA03681; Sun, 26 Mar 1995 10:15:02 +0200 Message-Id: <199503260815.KAA03681@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org cc: freebsd-bugs@freefall.cdrom.com Subject: Re: conf/273: syslogd no longer gets loaded at boot time Date: Sun, 26 Mar 1995 10:14:59 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > > >Number: 273 > >Category: conf > >Synopsis: syslogd no longer gets loaded at boot time > >Description: > > At boot time syslogd craps out with "cant bind to requested address" > > >How-To-Repeat: > > Reboot :-) > > >Fix: > > run syslogd as root. A whole bunch of queued messages (hardware id stuff from > the boot) gets dumped to the screen. Better Fix: move the loading of syslogd to _after_ . /etc/netstart This is how it was done before the great rc reorganise. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sun Mar 26 00:22:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA03796 for current-outgoing; Sun, 26 Mar 1995 00:22:14 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA03788 for ; Sun, 26 Mar 1995 00:22:10 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA16933; Sun, 26 Mar 1995 10:22:00 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id KAA15969 for freebsd-current@FreeBSD.org; Sun, 26 Mar 1995 10:21:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id KAA08539 for freebsd-current@FreeBSD.org; Sun, 26 Mar 1995 10:06:01 +0200 From: J Wunsch Message-Id: <199503260806.KAA08539@uriah.heep.sax.de> Subject: Re: Invalid DOSpartition table may be a bad idea To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 26 Mar 1995 10:05:58 +0200 (MET DST) In-Reply-To: from "Frank Durda IV" at Mar 25, 95 04:58:00 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 637 Sender: current-owner@FreeBSD.org Precedence: bulk As Frank Durda IV wrote: > > To avoid user problems, we may not want to put drives that our stuff is on > in a state where we will get wiped-out if the user happens to boot a > Windows 95 floppy, which late this year will be (sadly) one of the most ^^^^^^^^^^^^^^ > common operating systems on the planet. Did they announce the century the `95' belongs to? :-] (It's my understanding of KleinWeich, that `95' will expand to the term `Not before Dec 31, 95', btw.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 26 00:48:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA04502 for current-outgoing; Sun, 26 Mar 1995 00:48:26 -0800 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 AAA04496 for ; Sun, 26 Mar 1995 00:48:24 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA16778; Sun, 26 Mar 95 10:48:08 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id KAA24281 for freebsd-current@freefall.cdrom.com; Sun, 26 Mar 1995 10:53:56 +0200 Date: Sun, 26 Mar 1995 10:53:56 +0200 From: "Christoph P. Kukulies" Message-Id: <199503260853.KAA24281@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: commit lists Sender: current-owner@FreeBSD.org Precedence: bulk After the recent restructuring of the commit lists I'm receiving commit mails doubly. It was stated that subscribers had been removed from one of the lists automatically to avoid these double messages. Obviously this is not the case for me. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Sun Mar 26 04:47:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA15702 for current-outgoing; Sun, 26 Mar 1995 04:47:27 -0800 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA15692 for ; Sun, 26 Mar 1995 04:47:26 -0800 Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id HAA22298 for current@freebsd.org; Sun, 26 Mar 1995 07:47:18 -0500 Received: by starkhome.cs.sunysb.edu (8.6.11/1.34) id HAA04691; Sun, 26 Mar 1995 07:40:28 -0500 Date: Sun, 26 Mar 1995 07:40:28 -0500 From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Message-Id: <199503261240.HAA04691@starkhome.cs.sunysb.edu> To: "Christoph P. Kukulies" Cc: current@FreeBSD.org In-reply-to: "Christoph P. Kukulies"'s message of Sun, 26 Mar 1995 10:53:56 +0200 Subject: commit lists Sender: current-owner@FreeBSD.org Precedence: bulk >After the recent restructuring of the commit lists I'm receiving >commit mails doubly. It was stated that subscribers had been >removed from one of the lists automatically to avoid these double >messages. Obviously this is not the case for me. I am also receiving double commit mail. I mailed to majordomo asking to be removed from "freebsd-commit", but this hasn't helped (at least not yet). - Gene From owner-freebsd-current Sun Mar 26 04:54:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA16096 for current-outgoing; Sun, 26 Mar 1995 04:54:15 -0800 Received: from kryten.atinc.com (kryten.atinc.com [198.138.38.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA16087 for ; Sun, 26 Mar 1995 04:54:13 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id HAA16482; Sun, 26 Mar 1995 07:47:20 -0500 Date: Sun, 26 Mar 1995 07:47:20 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: commit lists To: "Christoph P. Kukulies" cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199503260853.KAA24281@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Sun, 26 Mar 1995, Christoph P. Kukulies wrote: > After the recent restructuring of the commit lists I'm receiving > commit mails doubly. It was stated that subscribers had been > removed from one of the lists automatically to avoid these double > messages. Obviously this is not the case for me. hmmm...i see that you are still subscribed to both cvs-all and freebsd-commit. ;( seems that you are not the only one. rather there were 24 people still subscribed to both. grrr.. (sort...sort...comm -12....unsubscribe...work this time please!) i will fix that right now. sorry. for those of you with 2 mailing addresses....well. you can unusbscribe yourselves. easier than me trying to identify your two addresses. > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 > 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 > > Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Sun Mar 26 05:01:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA16287 for current-outgoing; Sun, 26 Mar 1995 05:01:46 -0800 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 FAA16272 for ; Sun, 26 Mar 1995 05:01:42 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA17302; Sun, 26 Mar 95 15:01:30 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id PAA24956 for freebsd-current@freefall.cdrom.com; Sun, 26 Mar 1995 15:07:17 +0200 Date: Sun, 26 Mar 1995 15:07:17 +0200 From: "Christoph P. Kukulies" Message-Id: <199503261307.PAA24956@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: hash.h missing in libforms Sender: current-owner@FreeBSD.org Precedence: bulk in /usr/src/lib/libforms: fields.c forms.c menu.c have #include which isn't there. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Sun Mar 26 06:39:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA17391 for current-outgoing; Sun, 26 Mar 1995 06:39:52 -0800 Received: from inet-gw-3.pa.dec.com (inet-gw-3.pa.dec.com [16.1.0.33]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA17385; Sun, 26 Mar 1995 06:39:51 -0800 Received: from dude.pcs.dec.com by inet-gw-3.pa.dec.com (5.65/24Feb95) id AA13272; Sun, 26 Mar 95 06:39:22 -0800 Received: by dude.pcs.dec.com (/\=-/\ Smail3.1.16.1 #16.37) id ; Sun, 26 Mar 95 16:36 MSZ Message-Id: From: me@dude.pcs.dec.com ( Michael Elbel ) Subject: Re: cvs commit: src/sys/scsi sd.c To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Sun, 26 Mar 1995 16:36:37 +0200 (MSZ) Cc: me@FreeBSD.org, bde@zeta.org.au, current@FreeBSD.org Reply-To: me@FreeBSD.org (Michael Elbel) In-Reply-To: <199503252208.OAA19222@ref.tfs.com> from "Poul-Henning Kamp" at Mar 25, 95 02:08:10 pm X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1387 Sender: current-owner@FreeBSD.org Precedence: bulk > > Hrrm, both of my FreeBSD disks use the whole drive starting at sector 0, > > there aren't any slices on them. The slice changes don't allow me to mount > > them any more. Is this on purpose, I.e. do I *have* to fdisk my disks > > or is the code supposed to work with FreeBSD covering the whole disk? > > Yes, you have to slice them, the good news is that you don't loose any > disk-space doing so :-) Erm, how's that? Originally the while disk was used for partitions, now there's 32 sectors less (standard 64/32 translation). Or am I missing something obvious besides the possibility that there were 32 spare sectors in the last cylinder. Nevertheless, I can't get my 2 Gig Quantum Empire to be accepted by the new kernel. The new code seems to insist on checking the sector start and size information against the C/H/S begin and end information. I finally managed to fdisk it in a way that the slice code accepts the start after remembering that track sectors are starting at 1 instead of 0. However, I haven't found a way to make it happy about the end yet. I simply can't have the slice end beyond cylinder 1023 - I guess this is the usual bios limit, right? So, how am I supposed to get my disk to be recognized fully? I don't want to lose that Gig ;-) Michael -- Michael Elbel, Digital-PCS GmbH, Muenchen, Germany - me@FreeBSD.org Fermentation fault (coors dumped) From owner-freebsd-current Sun Mar 26 06:49:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA17471 for current-outgoing; Sun, 26 Mar 1995 06:49:46 -0800 Received: from inet-gw-3.pa.dec.com (inet-gw-3.pa.dec.com [16.1.0.33]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA17465 for ; Sun, 26 Mar 1995 06:49:45 -0800 Received: from tartufo.pcs.dec.com by inet-gw-3.pa.dec.com (5.65/24Feb95) id AA13868; Sun, 26 Mar 95 06:46:39 -0800 Received: by tartufo.pcs.dec.com (/\=-/\ Smail3.1.16.1 #16.39) id ; Sun, 26 Mar 95 16:45 MSZ Message-Id: Date: Sun, 26 Mar 95 16:45 MSZ From: me@tartufo.pcs.dec.com (Michael Elbel) To: bde@zeta.org.au Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/scsi sd.c Newsgroups: pcs.freebsd.current References: <199503252105.HAA00247@godzilla.zeta.org.au> Reply-To: me@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk In pcs.freebsd.current you write: >If there is no DOSpartition table then there is one slice (the whole >disk). Unfortunately you have to have a DOSpartition table to boot with >biosboot, and disklabel -B writes a dummy DOSpartition table whether you >want it or not. Fortunately it writes an _invalid_ DOSpartition table. Hmm, I don't boot off this disk. >Early versions rejected all invalid DOSpartition tables and gave one >slice (the whole disk), but that seemed too dangerous. The 95/03/23 >version gave one slice of size 50000 sectors for the dummy table. The Aah, that's why the slice code complained about the slice being smaller than the partition in the disklabel. >current version rejects just one invalid table (the dummy one) and >gives one slice (the whole disk). Ok, I'll get the latest stuff and make myself a new kernel then. Michael -- Michael Elbel, Digital-PCS GmbH, Muenchen, Germany - me@FreeBSD.org Fermentation fault (coors dumped) From owner-freebsd-current Sun Mar 26 08:24:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19693 for current-outgoing; Sun, 26 Mar 1995 08:24:26 -0800 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 IAA19667; Sun, 26 Mar 1995 08:23:43 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA27027; Mon, 27 Mar 1995 02:20:44 +1000 Date: Mon, 27 Mar 1995 02:20:44 +1000 From: Bruce Evans Message-Id: <199503261620.CAA27027@godzilla.zeta.org.au> To: current@FreeBSD.org, mark@grondar.za Subject: Re: conf/273: syslogd no longer gets loaded at boot time Cc: freebsd-bugs@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> >Description: >> >> At boot time syslogd craps out with "cant bind to requested address" >> >> >How-To-Repeat: >> >> Reboot :-) >> >> >Fix: >> >> run syslogd as root. A whole bunch of queued messages (hardware id stuff from >> the boot) gets dumped to the screen. >Better Fix: move the loading of syslogd to _after_ . /etc/netstart This is not quite right either: 1) messages logged by the processes started in /etc/netstart may be lost. 2) syslogd complains about /var/run/utmp being removed and a few "wall" messages may be lost. >This is how it was done before the great rc reorganise. Then it was quite right. Parts of the apparently chaotic order of starting up processes were to avoid problems such as the above. Bruce From owner-freebsd-current Sun Mar 26 08:39:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19864 for current-outgoing; Sun, 26 Mar 1995 08:39:18 -0800 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 IAA19858 for ; Sun, 26 Mar 1995 08:39:11 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA17941; Sun, 26 Mar 95 18:38:44 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id SAA25400 for freebsd-current@freefall.cdrom.com; Sun, 26 Mar 1995 18:44:31 +0200 Date: Sun, 26 Mar 1995 18:44:31 +0200 From: "Christoph P. Kukulies" Message-Id: <199503261644.SAA25400@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: can't mount (slices - sd driver) Sender: current-owner@FreeBSD.org Precedence: bulk With a yesterday's kernel I suddenly cannot mount all partitions due to some changes in the slicing code of the sd driver I think. I saw some commit messages regarding sd.c but at that time I didn't pay attention to it. Now I cannot see e.g. my home partition any longer. dmesg: FreeBSD 2.1.0-Development #0: Sun Mar 26 18:26:08 MET DST 1995 root@jazz:/home/src/sys/compile/JAZZGUS CPU: i486DX (486-class CPU) real memory = 33161216 (8096 pages) avail memory = 30773248 (7513 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x200-0x21f irq 5 on isa ed0: address 00:20:e4:80:6d:61, type NE2000 (16 bit) bpf: ed0 attached sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: (NEC 72065B) [0: fd0: 1.44MB 3.5in] npx0 on motherboard npx0: INT 16 interface gus0 at 0x220 irq 11 drq 1 on isa gus0: Probing for devices on the pci0 bus: configuration mode 2 allows 16 devices. chip0 rev 4 on pci0:0 ncr0 rev 1 int a irq 9 on pci0:1 reg20: virtual=0xf4796000 physical=0xfbfef000 size=0x100 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) ncr0 waiting for scsi devices to settle (ncr0:0:0): "SEAGATE ST31200N 8008" is a type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1006MB (2061108 512 byte sectors) (ncr0:1:0): "QUANTUM MAVERICK 540S 0901" is a type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 516MB (1057758 512 byte sectors) chip1 rev 3 on pci0:2 vga0 rev 0 on pci0:6 pci0: uses 256 bytes of memory from fbfef000 upto fbfef0ff. pci0: uses 256 bytes of I/O space from e800 upto e8ff. changing root device to sd0a sd0s1: start 1517568, end = 2060287, size 542720: OK sd0s2: start 411648, end = 901119, size 489472: OK sd0s3: start 901120, end = 1517567, size 616448: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 411648, end 901119, size 489472 sd0d: start 0, end 2061107, size 2061108 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0g: start 901120, end 1517567, size 616448 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 1517568, end 2060287, size 542720 sd1s1: start 32, end = 501759, size 501728: OK sd1s2: start 501760, end = 749567, size 247808: OK sd1s3: start 749568, end = 817151, size 67584: OK sd0s1: start 1517568, end = 2060287, size 542720: OK sd0s2: start 411648, end = 901119, size 489472: OK sd0s3: start 901120, end = 1517567, size 616448: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 411648, end 901119, size 489472 sd0d: start 0, end 2061107, size 2061108 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0g: start 901120, end 1517567, size 616448 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 1517568, end 2060287, size 542720 bpf: lo0 attached bpf: sl0 attached bpf: sl1 attached sd0s1: start 1517568, end = 2060287, size 542720: OK sd0s2: start 411648, end = 901119, size 489472: OK sd0s3: start 901120, end = 1517567, size 616448: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 411648, end 901119, size 489472 sd0d: start 0, end 2061107, size 2061108 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0g: start 901120, end 1517567, size 616448 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 1517568, end 2060287, size 542720 sd1s1: start 32, end = 501759, size 501728: OK sd1s2: start 501760, end = 749567, size 247808: OK sd1s3: start 749568, end = 817151, size 67584: OK disklabel -r sd0: # /dev/rsd0c: type: SCSI disk: seagate_31200 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 1024 sectors/unit: 2097152 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: 38912 411648 4.2BSD 1024 8192 16 # (Cyl. 201 - 219) b: 92160 450560 swap # (Cyl. 220 - 264) c: 489472 411648 unused 0 0 # (Cyl. 201 - 439) d: 2061108 0 unused 0 0 # (Cyl. 0 - 1006*) e: 358400 542720 4.2BSD 1024 8192 16 # (Cyl. 265 - 439) g: 616448 901120 4.2BSD 1024 8192 16 # (Cyl. 440 - 740) h: 542720 1517568 MSDOS # (Cyl. 741 - 1005) --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Sun Mar 26 08:48:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA20003 for current-outgoing; Sun, 26 Mar 1995 08:48:40 -0800 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 IAA19995 for ; Sun, 26 Mar 1995 08:48:30 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA27307; Mon, 27 Mar 1995 02:46:07 +1000 Date: Mon, 27 Mar 1995 02:46:07 +1000 From: Bruce Evans Message-Id: <199503261646.CAA27307@godzilla.zeta.org.au> To: current@FreeBSD.org, uhclem@nemesis.lonestar.org Subject: Re: Invalid DOSpartition table may be a bad idea Sender: current-owner@FreeBSD.org Precedence: bulk >[2]If there is no DOSpartition table then there is one slice (the whole >[2]disk). Unfortunately you have to have a DOSpartition table to boot with >[2]biosboot, and disklabel -B writes a dummy DOSpartition table whether you >[2]want it or not. Fortunately it writes an _invalid_ DOSpartition table. >If I understand what you are saying here, this may be a bad thing. >Windows 95 (which I have to run on some systems at work) takes a disk with >a missing or invalid partition table as an open invitation to automatically >initialize the entire disk for Windows 95 by putting a "use entire disk" >DOS partition table in there. The FreeBSD invalid DOSpartition table is historical baggage. I haven't been able to eradicate it. Perhaps Windows 95 will do a better job :-). What does Windows 95 consider to be an invalid table? We want a table with one partition that covers the whole disk _including_ the MBR to be valid, but that may be an invalid table for DOS. The slice driver does the following validity checks: 1) Last 2 bytes in MBR must be 0x55, 0xAA, else table is ignored. 2) For each partition, the C/H/S start and end must equal the logical start and end, else a warning is printed. The logical start and end are always considered valid. If the logical start or end corresponds to a C >= 1024, then no warning is printed in the following cases: a) C = 1023, H = max, S = max. b) C = correct mod 1024, H = correct, S = correct. It doesn't do any overlap or ordering checks. Bruce From owner-freebsd-current Sun Mar 26 08:59:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA20109 for current-outgoing; Sun, 26 Mar 1995 08:59:10 -0800 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 IAA20098; Sun, 26 Mar 1995 08:58:57 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA27419; Mon, 27 Mar 1995 02:55:14 +1000 Date: Mon, 27 Mar 1995 02:55:14 +1000 From: Bruce Evans Message-Id: <199503261655.CAA27419@godzilla.zeta.org.au> To: brian@mediacity.com, phk@ref.tfs.com Subject: Re: cvs commit: src/sys/scsi sd.c Cc: bde@zeta.org.au, current@FreeBSD.org, me@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >I'm still lost. Around 95/03/23 08:09:02 -current wouldn't bring up >my f partition anymore. That version didn't compensate for all of the historical bugs. >It does however boot, mount a and e correctly and then pukes on f saying >can't read sectors 16-31, not a BSD labelled drive. My f partition is >about 1.6GB. The whole drive was used for FreeBSD. The boot messages probably say that the FreeBSD slice has size 50000. 50000 is smaller than the whole drive, and only worked because of inadequate error checking. >I remember the install code talking about slicing and having to install >slice 1 (0) as the FreeBSD slice. Is there another level of slicing? >How does one "slice" a drive? Put a valid DOSpartition table on it. Bruce From owner-freebsd-current Sun Mar 26 09:10:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA20207 for current-outgoing; Sun, 26 Mar 1995 09:10:15 -0800 Received: from clinet.fi (root@clinet.fi [193.64.6.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA20201 for ; Sun, 26 Mar 1995 09:10:12 -0800 Received: from zetor.clinet.fi (root@zetor.clinet.fi [193.64.6.8]) by clinet.fi (8.6.10/8.6.4) with ESMTP id UAA20398; Sun, 26 Mar 1995 20:09:54 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by zetor.clinet.fi (8.6.10/8.6.4) id UAA08986; Sun, 26 Mar 1995 20:09:53 +0300 Date: Sun, 26 Mar 1995 20:09:53 +0300 Message-Id: <199503261709.UAA08986@zetor.clinet.fi> To: roberto@blaise.ibp.fr (Ollivier Robert) Cc: hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freefall.cdrom.com Subject: Re: Innd In-Reply-To: <9503231915.AA08773@blaise.ibp.fr> References: <199503231719.TAA23687@katiska.clinet.fi> <9503231915.AA08773@blaise.ibp.fr> Organization: Helsinki University of Technology, Otaniemi, Finland Sender: current-owner@FreeBSD.org Precedence: bulk Ollivier Robert writes: > > Mar 23 18:04:53 katiska innd: ME cant link sfnet/keskustelu/uskonto/20146 and sfnet/keskustelu/ihmissuhteet/8107 File exists > Don't use ACT_MMAP in config.data for the reading of the active file. Removed MMAP, and it seems to be stable now. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Sun Mar 26 09:26:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA20355 for current-outgoing; Sun, 26 Mar 1995 09:26:13 -0800 Received: from isis.wu-wien.ac.at (isis.wu-wien.ac.at [137.208.8.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA20349 for ; Sun, 26 Mar 1995 09:26:11 -0800 Received: from idefix.wu-wien.ac.at (idefix) by isis.wu-wien.ac.at with SMTP id AA05096 (5.65c/IDA-1.4.4 for ); Sun, 26 Mar 1995 19:26:00 +0200 Received: from slip-66.wu-wien.ac.at by idefix.wu-wien.ac.at (AIX 3.2/UCB 5.64/4.03) id AA22096; Sun, 26 Mar 1995 19:25:57 +0200 From: h9026173@falbala.wu-wien.ac.at (Gerald Hartmann) To: current@FreeBSD.org Subject: FreeBSD for Acorn RiscPC Reply-To: h9026173@falbala.wu-wien.ac.at Date: Sun, 26 Mar 1995 19:23:03 +0100 Message-Id: <19950326.192303.81@falbala.wu-wien.ac.at> X-Mailer: Archimedes TTFN Version 0.36 Sender: current-owner@FreeBSD.org Precedence: bulk Is there a port of FreeBSD for Acorn RiscPC? Where? Gerald -- --================================-- Gerald Hartmann h9026173@falbala.wu-wien.ac.at --================================-- ... ILLITERATE? Write for a free brochure... From owner-freebsd-current Sun Mar 26 09:28:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA20396 for current-outgoing; Sun, 26 Mar 1995 09:28:22 -0800 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 JAA20388 for ; Sun, 26 Mar 1995 09:28:15 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA27758 for current@freebsd.org; Mon, 27 Mar 1995 03:23:16 +1000 Date: Mon, 27 Mar 1995 03:23:16 +1000 From: Bruce Evans Message-Id: <199503261723.DAA27758@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: shared library versioning Sender: current-owner@FreeBSD.org Precedence: bulk The recent change to the msync() interface strictly requires incrementing the major number of libc.so. Bruce From owner-freebsd-current Sun Mar 26 11:03:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22065 for current-outgoing; Sun, 26 Mar 1995 11:03:43 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA22059 for ; Sun, 26 Mar 1995 11:03:41 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA05171; Sun, 26 Mar 1995 11:03:31 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA03679; Sun, 26 Mar 1995 11:03:30 -0800 Message-Id: <199503261903.LAA03679@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Bruce Evans cc: current@FreeBSD.org Subject: Re: shared library versioning In-reply-to: Your message of "Mon, 27 Mar 95 03:23:16 +1000." <199503261723.DAA27758@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 11:03:25 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >The recent change to the msync() interface strictly requires incrementing >the major number of libc.so. I don't agree. The library itself should remain unchanged. Things would be different if I had added a new syscall...but that's not what happend - I just added an additional argument, and libc doesn't know about how many arguments a syscall has. -DG From owner-freebsd-current Sun Mar 26 11:13:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22263 for current-outgoing; Sun, 26 Mar 1995 11:13:32 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA22257 for ; Sun, 26 Mar 1995 11:13:27 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA25533; Sun, 26 Mar 1995 21:13:06 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) id VAA20131; Sun, 26 Mar 1995 21:13:06 +0200 From: mw@sax.sax.de (Martin Welk) Message-Id: <199503261913.VAA20131@sax.sax.de> Subject: FreeBSD problems - VM bug? To: current@freefall.cdrom.com Date: Sun, 26 Mar 1995 21:13:06 +0200 (MET DST) Cc: mw@pandora.sax.de Reply-To: mw@pandora.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 2400 Sender: current-owner@FreeBSD.org Precedence: bulk Good Morning, Joerg Wunsch suggested to write my FreeBSD problems to this list. My configuration looks like this: a simple 386DX-40 based machine with 387 coprocessor, 8 meg RAM, ET4000 VGA adapter (1 meg RAM), Adaptec 1542B SCSI host adapter, 3 hard disks (Rodime 3259TS, 210 meg, Seagate ST41200N, about 1 gig, Maxtor, about 240 meg), Toshiba XM3401B CD-ROM, Wangtek 5150ES tape streamer, two serial ports (one with a 16550 FIFO chip), two parallel ports, game port, WD8013EBT network adapter clone. I have also a second Ethernet adapter, an original WD8003EB (got this as a present :-) ) but my problems occured before inserting that thing so I think that's not the problem. I used FreeBSD-1.1-Release until last week without problems, including UUCP, network (local network, ftp, telnet, NFS) and now I run into big problems... Now I've installed FreeBSD-950210-SNAP and a newer kernel release (dated on March, 23th) - Joerg was so friendly to build a new kernel at his machine for me, because... - Building a new kernel didn't work. Using the old kernel I got a "cc1: got fatal signal 11" message while running ``make depend'' at /usr/src/sys/compile/THEATRE. With the newer kernel this works fine but when compiling the kernel I get: ../../kern/subr_prf.c: In function '*' (where * has to be replaced by panic, uprintf, tprintf, ttyprintf, log, addlog, printf, sprintf) too many arguments to function `__builtin_next_arg' - I cannot use ``man'' - it says: groff: troff: Resource deadlock avoided - So I decided to try to compile groff/troff and so on and went to /usr/src/gnu/usr.bin/ngroff and said ``make'' - when compiling troff it says: ``cc: Internal compiler error: program cpp got fatal signal 11'' and exits. These are the facts - I don't know enough about the FreeBSD internals, I'm more like an administrator and user of this fine system (yes, and we also want to use FreeBSD in our company on a machine running as a CD-ROM and file server). That's why I use to ask Joerg when I have that kind of problems :-) He has similar problems with one of his machines, an older 386SX-16-based one. His 486DX-33 EISA machine works very fine and that's why we can't find a solution to this problem no. Can anybody help me? I don't get the FreeBSD-current mailing list, so please send a Cc to me. Thanks in advance for any help! Greetings, Martin From owner-freebsd-current Sun Mar 26 11:33:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22744 for current-outgoing; Sun, 26 Mar 1995 11:33:34 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA22736 for ; Sun, 26 Mar 1995 11:33:32 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA09844; Sun, 26 Mar 95 12:26:54 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503261926.AA09844@cs.weber.edu> Subject: Re: Invalid DOSpartition table may be a bad idea To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 26 Mar 95 12:26:53 MST Cc: freebsd-current@FreeBSD.org In-Reply-To: <199503260806.KAA08539@uriah.heep.sax.de> from "J Wunsch" at Mar 26, 95 10:05:58 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > > To avoid user problems, we may not want to put drives that our stuff is on > > in a state where we will get wiped-out if the user happens to boot a > > Windows 95 floppy, which late this year will be (sadly) one of the most > ^^^^^^^^^^^^^^ > > common operating systems on the planet. > > Did they announce the century the `95' belongs to? :-] > > (It's my understanding of KleinWeich, that `95' will expand to the > term `Not before Dec 31, 95', btw.) The target date I have seen is August 1995. I have to say that the most recent beta is *much* more reliable than previous betas, and that the use interface is quite "pretty". On the other hand, the number of animations is staggering, and makes it feel more like a toy that previous versions of windows. IMO, they hired some ex-Commodore people there somewhere. 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 Sun Mar 26 11:37:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22805 for current-outgoing; Sun, 26 Mar 1995 11:37:16 -0800 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 LAA22797 for ; Sun, 26 Mar 1995 11:37:12 -0800 Received: by sequent.kiae.su id AA10452 (5.65.kiae-2 ); Sun, 26 Mar 1995 22:32:50 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 26 Mar 95 22:32:50 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id XAA00900; Sun, 26 Mar 1995 23:06:42 +0400 To: Heikki Suonsivu , Ollivier Robert Cc: freebsd-current@freefall.cdrom.com References: <199503231719.TAA23687@katiska.clinet.fi> <9503231915.AA08773@blaise.ibp.fr> <199503261709.UAA08986@zetor.clinet.fi> In-Reply-To: <199503261709.UAA08986@zetor.clinet.fi>; from Heikki Suonsivu at Sun, 26 Mar 1995 20:09:53 +0300 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sun, 26 Mar 1995 23:06:41 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: Innd Lines: 19 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 743 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199503261709.UAA08986@zetor.clinet.fi> Heikki Suonsivu writes: >Ollivier Robert writes: > > > Mar 23 18:04:53 katiska innd: ME cant link sfnet/keskustelu/uskonto/20146 and sfnet/keskustelu/ihmissuhteet/8107 File exists > > Don't use ACT_MMAP in config.data for the reading of the active file. >Removed MMAP, and it seems to be stable now. All this mess comes becomes msync() and munmap() don't update modification times at all. -- 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 Sun Mar 26 11:44:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22917 for current-outgoing; Sun, 26 Mar 1995 11:44:19 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA22909 for ; Sun, 26 Mar 1995 11:44:16 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA05282; Sun, 26 Mar 1995 11:44:05 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA00398; Sun, 26 Mar 1995 11:44:05 -0800 Message-Id: <199503261944.LAA00398@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: "Andrey A. Chernov, Black Mage" cc: Heikki Suonsivu , Ollivier Robert , freebsd-current@freefall.cdrom.com Subject: Re: Innd In-reply-to: Your message of "Sun, 26 Mar 95 23:06:41 +0400." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 11:43:59 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >>Ollivier Robert writes: >> > > Mar 23 18:04:53 katiska innd: ME cant link sfnet/keskustelu/uskonto/20146 and sfnet/keskustelu/ihmissuhteet/8107 File exists > >> > Don't use ACT_MMAP in config.data for the reading of the active file. > >>Removed MMAP, and it seems to be stable now. > >All this mess comes becomes msync() and munmap() don't update >modification times at all. Even worse, writing to mmaped files is very broken in -current. John spent the entire weekend fixing this. I should be committing the fixes for this during the day today. -DG From owner-freebsd-current Sun Mar 26 11:48:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22961 for current-outgoing; Sun, 26 Mar 1995 11:48:27 -0800 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 LAA22953 for ; Sun, 26 Mar 1995 11:48:16 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA29708; Mon, 27 Mar 1995 05:45:16 +1000 Date: Mon, 27 Mar 1995 05:45:16 +1000 From: Bruce Evans Message-Id: <199503261945.FAA29708@godzilla.zeta.org.au> To: bde@zeta.org.au, davidg@Root.COM Subject: Re: shared library versioning Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>The recent change to the msync() interface strictly requires incrementing >>the major number of libc.so. > I don't agree. The library itself should remain unchanged. Things would be >different if I had added a new syscall...but that's not what happend - I just >added an additional argument, and libc doesn't know about how many arguments a >syscall has. Yes, this problem can't be solved in the library. A new syscall is required. Old callers don't supply the additional arg. Bruce From owner-freebsd-current Sun Mar 26 11:49:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22989 for current-outgoing; Sun, 26 Mar 1995 11:49:16 -0800 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA22982 for ; Sun, 26 Mar 1995 11:49:14 -0800 Received: from ast.com by relay2.UU.NET with SMTP id QQyitr06823; Sun, 26 Mar 1995 14:48:57 -0500 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA20134 (5.67b/IDA-1.5 for uunet!munnari!zeta.org.au!bde); Sun, 26 Mar 1995 11:52:55 -0800 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Sun, 26 Mar 95 19:47 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0rsyCK-0004vsC; Sun, 26 Mar 95 13:42 CST Message-Id: Date: Sun, 26 Mar 95 13:42 CST To: bde@zeta.org.au, current@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sun Mar 26 1995, 13:42:04 CST Subject: Re: Invalid DOSpartition table may be a bad idea Cc: uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk [2]Bruce writes: [2]If there is no DOSpartition table then there is one slice (the whole [2]disk). Unfortunately you have to have a DOSpartition table to boot with [2]biosboot, and disklabel -B writes a dummy DOSpartition table whether you [2]want it or not. Fortunately it writes an _invalid_ DOSpartition table. [3]Frank writes: [3]If I understand what you are saying here, this may be a bad thing. [3]Windows 95 (which I have to run on some systems at work) takes a disk with [3]a missing or invalid partition table as an open invitation to automatically [3]initialize the entire disk for Windows 95 by putting a "use entire disk" [3]DOS partition table in there. [4]Bruce writes: [4]The FreeBSD invalid DOSpartition table is historical baggage. I haven't [4]been able to eradicate it. Perhaps Windows 95 will do a better job :-). [4]What does Windows 95 consider to be an invalid table? We want a table [4]with one partition that covers the whole disk _including_ the MBR to [4]be valid, but that may be an invalid table for DOS. I will see if I can find exactly what makes Win95 punt. The feeble documentation says Win95 verifies a checksum, but I don't exactly believe that since I don't think there is one. I know someone on the Win 95 program team and he may be able to get an answer quickly. Apparently the reason this was done in Win 95 was to speed factory installs, but no factory I know does a real install on each system. They simply download an image of a system that was installed earlier over the network and onto the drives. I guess for service reinstalls after a drive gets blown-away it will save a step or two. [4]The slice driver does the following validity checks: [4]1) Last 2 bytes in MBR must be 0x55, 0xAA, else table is ignored. [4]2) For each partition, the C/H/S start and end must equal the logical [4] start and end, else a warning is printed. The logical start and end [4] are always considered valid. If the logical start or end corresponds [4] to a C >= 1024, then no warning is printed in the following cases: [4] a) C = 1023, H = max, S = max. [4] b) C = correct mod 1024, H = correct, S = correct. [4] [4]It doesn't do any overlap or ordering checks. Thanks for the checklist. Frank Durda IV |"Made Free, as free as the or uhclem%nemesis@trsvax.ast.com (Internet)| courts know, as long as the ...letni!rwsys!nemesis!uhclem | code flows, it's free, B-S-D." ...decvax!trsvax.fw.ast.com!nemesis!uhclem | :-) - FDIV (1995) From owner-freebsd-current Sun Mar 26 11:53:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA23075 for current-outgoing; Sun, 26 Mar 1995 11:53:42 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA23067 for ; Sun, 26 Mar 1995 11:53:39 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA05385; Sun, 26 Mar 1995 11:53:29 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA00456; Sun, 26 Mar 1995 11:53:29 -0800 Message-Id: <199503261953.LAA00456@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Bruce Evans cc: current@FreeBSD.org Subject: Re: shared library versioning In-reply-to: Your message of "Mon, 27 Mar 95 05:45:16 +1000." <199503261945.FAA29708@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 11:53:28 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >>>The recent change to the msync() interface strictly requires incrementing >>>the major number of libc.so. > >> I don't agree. The library itself should remain unchanged. Things would be >>different if I had added a new syscall...but that's not what happend - I just >>added an additional argument, and libc doesn't know about how many arguments a >>syscall has. > >Yes, this problem can't be solved in the library. A new syscall is required. >Old callers don't supply the additional arg. In other cases this would be true...but msync has never worked correctly in FreeBSD - it always returned EINVAL because of bugs in it. I just fixed this a few days ago. In the current scheme, passing garbage to msync() for the flags will be no worse than the previous behavior. I suggest we just leave it alone unless you have some other reason to bump the libc major number. -DG From owner-freebsd-current Sun Mar 26 12:21:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA24357 for current-outgoing; Sun, 26 Mar 1995 12:21:49 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA24346 for ; Sun, 26 Mar 1995 12:21:41 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA26508; Sun, 26 Mar 1995 22:21:23 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id WAA20639; Sun, 26 Mar 1995 22:21:21 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id WAA12485; Sun, 26 Mar 1995 22:15:49 +0200 From: J Wunsch Message-Id: <199503262015.WAA12485@uriah.heep.sax.de> Subject: Re: FreeBSD problems - VM bug? To: mw@pandora.sax.de Date: Sun, 26 Mar 1995 22:15:47 +0200 (MET DST) Cc: current@freefall.cdrom.com In-Reply-To: <199503261913.VAA20131@sax.sax.de> from "Martin Welk" at Mar 26, 95 09:13:06 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 552 Sender: current-owner@FreeBSD.org Precedence: bulk As Martin Welk wrote: > > That's why I use to ask Joerg when I have that kind of problems :-) > > He has similar problems with one of his machines, an older > 386SX-16-based one. No, not similar -- other problems. :-/ But i've reported them earlier, they seem to be related to heavy NFS server activity. Martin's problems appear to me like the kind of things ``which we believed to be already solved''. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Mar 26 12:27:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA24561 for current-outgoing; Sun, 26 Mar 1995 12:27:09 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA24554; Sun, 26 Mar 1995 12:27:08 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Christoph P. Kukulies" cc: freebsd-current@freefall.cdrom.com Subject: Re: hash.h missing in libforms In-reply-to: Your message of "Sun, 26 Mar 95 15:07:17 +0200." <199503261307.PAA24956@gilberto.physik.rwth-aachen.de> Date: Sun, 26 Mar 1995 12:27:08 -0800 Message-ID: <24553.796249628@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk You need to update.. > > in /usr/src/lib/libforms: fields.c forms.c menu.c have #include > which isn't there. > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 > 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Sun Mar 26 14:01:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA00448 for current-outgoing; Sun, 26 Mar 1995 14:01:23 -0800 Received: from obiwan.pmr.com ([199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA00440 for ; Sun, 26 Mar 1995 14:01:20 -0800 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0rt0MS-000300C; Sun, 26 Mar 95 16:00 CST Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: tgetnum wierdness on -current To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Sun, 26 Mar 1995 16:00:40 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 586 Sender: current-owner@FreeBSD.org Precedence: bulk On -current I have observed that tgetnum will *always* return 65 for the number of lines when running in a remote xterm (running on a 1.1.5.1 system w/XFree86 3.1.1). A local xterm or the console seems to be correct. Is there a known compatibility problem between -current and 1.1.5.1 with xterms or is it likely that I'm doing something wrong? -- Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob Austin, TX or: @uudell.us.dell.com:obiwan!bob 512-258-4224 (home), 512-838-3914 (work) or: obiwan%bob@uunet.uu.net From owner-freebsd-current Sun Mar 26 14:22:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03361 for current-outgoing; Sun, 26 Mar 1995 14:22:42 -0800 Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03355 for ; Sun, 26 Mar 1995 14:22:40 -0800 Received: from metal.ops.neosoft.com (root@glenn-slip45.nmt.edu [129.138.5.145]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id QAA23326; Sun, 26 Mar 1995 16:22:28 -0600 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id PAA04563; Sun, 26 Mar 1995 15:22:24 -0700 From: Scott Mace Message-Id: <199503262222.PAA04563@metal.ops.neosoft.com> Subject: Re: FreeBSD problems - VM bug? To: mw@pandora.sax.de Date: Sun, 26 Mar 1995 15:22:24 -0700 (MST) Cc: current@freefall.cdrom.com In-Reply-To: <199503261913.VAA20131@sax.sax.de> from "Martin Welk" at Mar 26, 95 09:13:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1542 Sender: current-owner@FreeBSD.org Precedence: bulk I experienced the random singal 11's back then when my -current was about equal to the SNAP. I no longer get those problems with the latest -current. The problem seemed to hinge around -O2 optimization instead of -O. The solution for me was to recompile the world with -O instead of -O2. I think the best solution for anyone running the 02 SNAP is that they should upgrade to the latest SNAP (its a pain but probably more feasable than recompiling everything). Like I said, -O2 does not seem to cause these problems anymore. I havn't seen a singal 11 for quite some time. Scott > > Now I've installed FreeBSD-950210-SNAP and a newer kernel release > (dated on March, 23th) - Joerg was so friendly to build a new kernel > at his machine for me, because... > > - Building a new kernel didn't work. Using the old kernel I got a > "cc1: got fatal signal 11" message while running ``make depend'' at > /usr/src/sys/compile/THEATRE. > With the newer kernel this works fine but when compiling the kernel > I get: ../../kern/subr_prf.c: In function '*' > (where * has to be replaced by panic, uprintf, tprintf, ttyprintf, > log, addlog, printf, sprintf) > too many arguments to function `__builtin_next_arg' > > - I cannot use ``man'' - it says: > groff: troff: Resource deadlock avoided > > - So I decided to try to compile groff/troff and so on and went to > /usr/src/gnu/usr.bin/ngroff and said ``make'' - when compiling troff > it says: ``cc: Internal compiler error: program cpp got fatal signal > 11'' and exits. From owner-freebsd-current Sun Mar 26 14:38:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA06292 for current-outgoing; Sun, 26 Mar 1995 14:38:01 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA06284 for ; Sun, 26 Mar 1995 14:37:57 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id OAA05928; Sun, 26 Mar 1995 14:37:45 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id OAA00314; Sun, 26 Mar 1995 14:37:45 -0800 Message-Id: <199503262237.OAA00314@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Scott Mace cc: mw@pandora.sax.de, current@freefall.cdrom.com Subject: Re: FreeBSD problems - VM bug? In-reply-to: Your message of "Sun, 26 Mar 95 15:22:24 MST." <199503262222.PAA04563@metal.ops.neosoft.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 14:37:43 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >I experienced the random singal 11's back then when my -current was about >equal to the SNAP. I no longer get those problems with the latest -current. >The problem seemed to hinge around -O2 optimization instead of -O. > >The solution for me was to recompile the world with -O instead of -O2. >I think the best solution for anyone running the 02 SNAP is that they >should upgrade to the latest SNAP (its a pain but probably more feasable >than recompiling everything). > >Like I said, -O2 does not seem to cause these problems anymore. I havn't >seen a singal 11 for quite some time. I don't think the problem is in any way related to -O2 optimization. There were a whole slew of VM bugs that were fixed in post-0210 SNAP that were causing problems. As far as I know, the entire source tree except the kernel is still built -O2. -DG From owner-freebsd-current Sun Mar 26 15:32:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA16197 for current-outgoing; Sun, 26 Mar 1995 15:32:27 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA16181 for ; Sun, 26 Mar 1995 15:32:24 -0800 Received: by sovcom.kiae.su id AA23906 (5.65.kiae-2 ); Mon, 27 Mar 1995 03:26:43 +0400 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 27 Mar 95 03:26:42 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id DAA02082; Mon, 27 Mar 1995 03:22:02 +0400 To: Bob Willcox , freebsd-current References: In-Reply-To: ; from Bob Willcox at Sun, 26 Mar 1995 16:00:40 -0600 (CST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 27 Mar 1995 03:22:01 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: tgetnum wierdness on -current Lines: 18 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 873 Sender: current-owner@FreeBSD.org Precedence: bulk In message Bob Willcox writes: >On -current I have observed that tgetnum will *always* return 65 >for the number of lines when running in a remote xterm (running on >a 1.1.5.1 system w/XFree86 3.1.1). A local xterm or the console >seems to be correct. Is there a known compatibility problem between >-current and 1.1.5.1 with xterms or is it likely that I'm doing >something wrong? I don't see any problem here, tgetnum("li") always return what exactly specified in termcap, nothing more. It is per-program task use ioctl to get window dims. -- 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 Sun Mar 26 15:33:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA16377 for current-outgoing; Sun, 26 Mar 1995 15:33:06 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA16356 for ; Sun, 26 Mar 1995 15:33:03 -0800 Received: by sovcom.kiae.su id AA23903 (5.65.kiae-2 ); Mon, 27 Mar 1995 03:26:39 +0400 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 27 Mar 95 03:26:35 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id DAA02060; Mon, 27 Mar 1995 03:18:18 +0400 To: bde@zeta.org.au, davidg@Root.COM Cc: current@FreeBSD.org References: <199503261945.FAA29708@godzilla.zeta.org.au> In-Reply-To: <199503261945.FAA29708@godzilla.zeta.org.au>; from Bruce Evans at Mon, 27 Mar 1995 05:45:16 +1000 Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 27 Mar 1995 03:18:17 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: shared library versioning Lines: 24 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1090 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199503261945.FAA29708@godzilla.zeta.org.au> Bruce Evans writes: >>>The recent change to the msync() interface strictly requires incrementing >>>the major number of libc.so. >> I don't agree. The library itself should remain unchanged. Things would be >>different if I had added a new syscall...but that's not what happend - I just >>added an additional argument, and libc doesn't know about how many arguments a >>syscall has. >Yes, this problem can't be solved in the library. A new syscall is required. >Old callers don't supply the additional arg. AFAIK, no system pgms use msync(). Applications which use msync() is broken in any case, even in old system due to msync() broken, so they needs recompile. I don't see a reason for new syscall because old one never works. -- 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 Sun Mar 26 15:52:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA20188 for current-outgoing; Sun, 26 Mar 1995 15:52:58 -0800 Received: from obiwan.pmr.com ([199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA20168 for ; Sun, 26 Mar 1995 15:52:54 -0800 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0rt26U-000300C; Sun, 26 Mar 95 17:52 CST Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: tgetnum wierdness on -current To: ache@astral.msk.su (Andrey A. Chernov, Black Mage) Date: Sun, 26 Mar 1995 17:52:18 -0600 (CST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: from "Andrey A. Chernov, Black Mage" at Mar 27, 95 03:22:01 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1449 Sender: current-owner@FreeBSD.org Precedence: bulk Andrey A. Chernov, Black Mage wrote: > > In message Bob Willcox writes: > > >On -current I have observed that tgetnum will *always* return 65 > >for the number of lines when running in a remote xterm (running on > >a 1.1.5.1 system w/XFree86 3.1.1). A local xterm or the console > >seems to be correct. Is there a known compatibility problem between > >-current and 1.1.5.1 with xterms or is it likely that I'm doing > >something wrong? > > I don't see any problem here, tgetnum("li") always return > what exactly specified in termcap, nothing more. > It is per-program task use ioctl to get window dims. Except that here my xterm termcap entry specifies line number as 24, yet tgetnum("li") returns 65 when executed in a remote xterm, regardless of window size or termcap setting. On a related problem I'm having, the ioctl call in setterm() in curses is failing on the second and subquent calls to setterm(). (This is why I saw the tgetnum("li") problem.) It works ok the first time, but resizing the window exposes the failure when the application does another initscr(). The application (and curses) then thinks the window has 65 rows and misbehaves accordingly. -- Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob Austin, TX or: @uudell.us.dell.com:obiwan!bob 512-258-4224 (home), 512-838-3914 (work) or: obiwan%bob@uunet.uu.net From owner-freebsd-current Sun Mar 26 16:47:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA27551 for current-outgoing; Sun, 26 Mar 1995 16:47:53 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA27545 for ; Sun, 26 Mar 1995 16:47:49 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id TAA00702 for freebsd-current@freefall.cdrom.com; Sun, 26 Mar 1995 19:47:38 -0500 From: John Capo Message-Id: <199503270047.TAA00702@irbs.com> Subject: Slice errors To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Sun, 26 Mar 1995 19:47:37 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1855 Sender: current-owner@FreeBSD.org Precedence: bulk I have a -current system with 3 Conner CP30200 SCSI drives. I have been using a C/H/S geometry of XXX/8/256 since Rodney mentioned this as the optimum geometry for SCSI disks and ufs. Prior to that I used XXX/64/32 as reported by the Adaptec controller. With the new slice scheme I get this error for all drives: sd0: raw partition size != slice size sd0: start 0, end 416107, size 416108 sd0c: start 0, end 413695, size 413696 The capacity reported for these drives is 416108 blocks. It appears to be complaining that the slice is 416108 blocks but partition c is only 413696 blocks. Ok, I'll make the c partition == 416108, who cares. Disklabel says, partition c extends past end of unit and does not write the label. There are no DOS partitions on these Conner drives, 100% FreeBSD. All of my partitions end on cylinder boundaries due to bad experiences in the past. Do I have to use the bogus geometry reorted by the drive and rework all of my labels for this message to go away? I have another system with a 1Gig SCSI disk that has a DOS partiton and a FreeBSD partition. The physical disk is larger than my c partition but I do not get any error messages. The capacity of this disk is 2031705 blocks. sd0s1: start 32, end = 409599, size 409568: OK sd0s2: start 409600, end = 2031615, size 1622016: OK FreeBSD fdisk continues to report bogus partitions. I had to partition the disk several times with pfdisk.exe before I could get the new slice stuff to work properly. I know that this is not what is on the disk. 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 John Capo From owner-freebsd-current Sun Mar 26 17:12:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA28681 for current-outgoing; Sun, 26 Mar 1995 17:12:38 -0800 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 RAA28675 for ; Sun, 26 Mar 1995 17:12:34 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id RAA12403; Sun, 26 Mar 1995 17:12:04 -0800 From: "Rodney W. Grimes" Message-Id: <199503270112.RAA12403@gndrsh.aac.dev.com> Subject: Re: Slice errors To: jc@irbs.com (John Capo) Date: Sun, 26 Mar 1995 17:12:03 -0800 (PST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199503270047.TAA00702@irbs.com> from "John Capo" at Mar 26, 95 07:47:37 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 3416 Sender: current-owner@FreeBSD.org Precedence: bulk > > I have a -current system with 3 Conner CP30200 SCSI drives. I have > been using a C/H/S geometry of XXX/8/256 since Rodney mentioned > this as the optimum geometry for SCSI disks and ufs. Prior to that > I used XXX/64/32 as reported by the Adaptec controller. My 8/256 optimizations no longer apply, this has been fixed in other ways and I would suggest now that you go back to the standard adaptec xxx/64/32 translation. Since 8*256 == 64*32 this should not effect your disklabel in any way. > With the new slice scheme I get this error for all drives: > > sd0: raw partition size != slice size > sd0: start 0, end 416107, size 416108 > sd0c: start 0, end 413695, size 413696 > > The capacity reported for these drives is 416108 blocks. It appears > to be complaining that the slice is 416108 blocks but partition c > is only 413696 blocks. Ok, I'll make the c partition == 416108, > who cares. Disklabel says, partition c extends past end of unit > and does not write the label. There are no DOS partitions on these > Conner drives, 100% FreeBSD. This drive should be translated into 203/64/32, c: should be 415744 blocks You will loose 364 blocks due to cylinder bondaries. > > All of my partitions end on cylinder boundaries due to bad experiences > in the past. Do I have to use the bogus geometry reorted by the > drive and rework all of my labels for this message to go away? > > I have another system with a 1Gig SCSI disk that has a DOS partiton > and a FreeBSD partition. The physical disk is larger than my c > partition but I do not get any error messages. The capacity of this > disk is 2031705 blocks. > > sd0s1: start 32, end = 409599, size 409568: OK > sd0s2: start 409600, end = 2031615, size 1622016: OK > > FreeBSD fdisk continues to report bogus partitions. I had to > partition the disk several times with pfdisk.exe before I could > get the new slice stuff to work properly. I know that this is not > what is on the disk. > > 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 Use fdisk -u to correct the partition table so that size==size of your BSD c or d partition and things should be fine. What you see above is the bogus partition table that gets installed if you install new boot blocks. Your final fdisk output should look something like this: ******* Working on device /dev/rsd0d ******* parameters extracted from in-core disklabel are: cylinders=203 heads=64 sectors/track=32 (2048 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=203 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,(386BSD) start 0, size 415744 (203 Meg), flag 80 beg: cyl 0/ sector 1/ head 0; end: cyl 202/ sector 32/ head 63 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun Mar 26 17:36:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA29520 for current-outgoing; Sun, 26 Mar 1995 17:36:32 -0800 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA29513 for ; Sun, 26 Mar 1995 17:36:30 -0800 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA19781; Mon, 27 Mar 95 02:36:53 +0100 Date: Mon, 27 Mar 95 02:36:53 +0100 From: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Message-Id: <9503270136.AA19781@cabri.obs-besancon.fr> To: freebsd-current@freefall.cdrom.com Subject: sd errors X-Mailer: Emacs Sender: current-owner@FreeBSD.org Precedence: bulk With a -current kernel (03/25) I get the following messages after boot: /kernel: sd0: raw partition size != slice size /kernel: sd0: start 0, end 2065249, size 2065250 /kernel: sd0c: start 0, end 2390975, size 2390976 /kernel: sd0: truncating raw partition /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice /kernel: sd0: start 0, end 2065249, size 2065250 /kernel: sd0d: start 0, end 2390975, size 2390976 /kernel: sd1: raw partition size != slice size /kernel: sd1: start 0, end 1075648, size 1075649 /kernel: sd1c: start 0, end 1075451, size 1075452 /kernel: sd1: raw partition size != slice size /kernel: sd1: start 0, end 1075648, size 1075649 /kernel: sd1c: start 0, end 1075451, size 1075452 The drives were newfs/labelled a long time ago (1.1.5). On both disks, the c partition stands the whole disk. It not is not mounted for sd0, but mounted for sd1. Is there a way to solve this? (NO don't tell me to newfs my drives!) Jean-Marc ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr Observatoire de Besancon | F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr ========================================================================= From owner-freebsd-current Sun Mar 26 18:33:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA00860 for current-outgoing; Sun, 26 Mar 1995 18:33:25 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA00854 for ; Sun, 26 Mar 1995 18:33:24 -0800 Received: (from mmead@localhost) by goof.com (8.6.11/8.6.9) id VAA01444 for current@freebsd.org; Sun, 26 Mar 1995 21:33:14 -0500 From: "matthew c. mead" Message-Id: <199503270233.VAA01444@goof.com> Subject: GUS sound To: current@FreeBSD.org Date: Sun, 26 Mar 1995 21:33:14 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 484 Sender: current-owner@FreeBSD.org Precedence: bulk I just grabbed the current sources tonight and am running them - anyone know if anything's changed with the sound driver lately? Any leads on what's wrong? Thanks! -matt -- Matthew C. Mead -> Virginia Tech Center for Transportation Research - -> Multiple Platform System and Network Administration Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other ---- ------- WWW -> http://www.goof.com/~mmead --- ----- From owner-freebsd-current Sun Mar 26 18:57:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01180 for current-outgoing; Sun, 26 Mar 1995 18:57:55 -0800 Received: from kbrown.oldcampus.yale.edu (root@kbrown.oldcampus.yale.edu [130.132.128.124]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA01170 for ; Sun, 26 Mar 1995 18:57:54 -0800 Date: Sun, 26 Mar 1995 21:57:36 -0500 (EST) From: -Vince- To: FreeBSD-current@freefall.cdrom.com Subject: -current kernel won't compile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk -current kernel as of 16:08PM PST 3/26/95 won't compile, any ideas? loading kernel if_ether.o: Undefined symbol `_inet_ntoa' referenced from text segment if_ether.o: Undefined symbol `_inet_ntoa' referenced from text segment if_ether.o: Undefined symbol `_inet_ntoa' referenced from text segment if_ether.o: Undefined symbol `_inet_ntoa' referenced from text segment ip_input.o: Undefined symbol `_inet_ntoa' referenced from text segment ip_input.o: Undefined symbol `_inet_ntoa' referenced from text segment *** Error code 1 Stop. Cheers, Vince E-mail: vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. root@berkeley.circlestar.com,(o o) San Francisco, California USA _________________________oOO__(_)__OOo_____________________________ | There are many forms of science but only physics is the quantum | | leap of the 21st Century. | \_________________________________________________________________/ uPoy@physics.ucla.edu UCLA Physics/Electrical Engineering Los Angeles, California USA GUS Digest Adminstrator Advanced Gravis UltraSound Card - The ultimate in soundcard technology System Administrator - bigbang.HIP.Berkeley.EDU From owner-freebsd-current Sun Mar 26 18:57:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01187 for current-outgoing; Sun, 26 Mar 1995 18:57:58 -0800 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 SAA01177 for ; Sun, 26 Mar 1995 18:57:55 -0800 Received: by sequent.kiae.su id AA28058 (5.65.kiae-2 ); Mon, 27 Mar 1995 05:49:37 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 27 Mar 95 05:49:36 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id GAA00476; Mon, 27 Mar 1995 06:50:59 +0400 To: Bob Willcox Cc: freebsd-current@freefall.cdrom.com References: In-Reply-To: ; from Bob Willcox at Sun, 26 Mar 1995 17:52:18 -0600 (CST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 27 Mar 1995 06:50:58 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: tgetnum wierdness on -current Lines: 41 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1912 Sender: current-owner@FreeBSD.org Precedence: bulk In message Bob Willcox writes: >Andrey A. Chernov, Black Mage wrote: >> >> In message Bob Willcox writes: >> >> >On -current I have observed that tgetnum will *always* return 65 >> >for the number of lines when running in a remote xterm (running on >> >a 1.1.5.1 system w/XFree86 3.1.1). A local xterm or the console >> >seems to be correct. Is there a known compatibility problem between >> >-current and 1.1.5.1 with xterms or is it likely that I'm doing >> >something wrong? >> >> I don't see any problem here, tgetnum("li") always return >> what exactly specified in termcap, nothing more. >> It is per-program task use ioctl to get window dims. >Except that here my xterm termcap entry specifies line number as >24, yet tgetnum("li") returns 65 when executed in a remote xterm, >regardless of window size or termcap setting. What do you mean by "executed in a remote xterm"? As I understand, you need to check environment (TERM,TERMCAP) and termcap file on _remote_ system... >On a related problem I'm having, the ioctl call in setterm() in >curses is failing on the second and subquent calls to setterm(). >(This is why I saw the tgetnum("li") problem.) It works ok the >first time, but resizing the window exposes the failure when the >application does another initscr(). The application (and curses) >then thinks the window has 65 rows and misbehaves accordingly. I don't think that application can use several initscr()s, only one. But you can use several endwin()s freely, next refresh() must restore screen modes after endwin(). -- 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 Sun Mar 26 19:20:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01712 for current-outgoing; Sun, 26 Mar 1995 19:20:25 -0800 Received: from obiwan.pmr.com ([199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA01706 for ; Sun, 26 Mar 1995 19:20:19 -0800 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0rt5LG-00030fC; Sun, 26 Mar 95 21:19 CST Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: tgetnum wierdness on -current To: ache@astral.msk.su (Andrey A. Chernov Black Mage) Date: Sun, 26 Mar 1995 21:19:45 -0600 (CST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: from "Andrey A. Chernov, Black Mage" at Mar 27, 95 06:50:58 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2207 Sender: current-owner@FreeBSD.org Precedence: bulk Andrey A. Chernov, Black Mage wrote: > > In message Bob Willcox writes: > >Except that here my xterm termcap entry specifies line number as > >24, yet tgetnum("li") returns 65 when executed in a remote xterm, > >regardless of window size or termcap setting. > > What do you mean by "executed in a remote xterm"? > As I understand, you need to check environment (TERM,TERMCAP) > and termcap file on _remote_ system... >From an xterm on one system (running FreeBSD 1.1.5.1) I am rlogining into another system (running FreeBSD -current built today). The termcap file on the remote (-current) system looks ok and has a line count of 24 (li#24). However, if I do a tgetnum("li") (or the tput li command) the output value is 65. From a virtual console or xterm on the -current system I get the correct output from tgetnum("li"). > > >On a related problem I'm having, the ioctl call in setterm() in > >curses is failing on the second and subquent calls to setterm(). > >(This is why I saw the tgetnum("li") problem.) It works ok the > >first time, but resizing the window exposes the failure when the > >application does another initscr(). The application (and curses) > >then thinks the window has 65 rows and misbehaves accordingly. > > I don't think that application can use several initscr()s, only one. > But you can use several endwin()s freely, next refresh() must > restore screen modes after endwin(). The application in question is files-2.2p1 that I am trying to port to run on FreeBSD. Whenever it receives a SIGWINCH signal it terminates the current window by calling endwin() then reinstates it by calling initscr(). It also calls wrefresh() for each of its logical windows plus a number of other initializations. I can email you the file that handles all of this if you would like (its about 1000 lines). I have had little experience with curses and can't really tell if what is being done is ligitmate or not. -- Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob Austin, TX or: @uudell.us.dell.com:obiwan!bob 512-258-4224 (home), 512-838-3914 (work) or: obiwan%bob@uunet.uu.net From owner-freebsd-current Sun Mar 26 19:45:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA02527 for current-outgoing; Sun, 26 Mar 1995 19:45:13 -0800 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA02520 for ; Sun, 26 Mar 1995 19:45:07 -0800 Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id WAA23367 for current@freebsd.org; Sun, 26 Mar 1995 22:44:59 -0500 Received: by starkhome.cs.sunysb.edu (8.6.11/1.34) id WAA06229; Sun, 26 Mar 1995 22:44:17 -0500 Date: Sun, 26 Mar 1995 22:44:17 -0500 From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Message-Id: <199503270344.WAA06229@starkhome.cs.sunysb.edu> To: current@FreeBSD.org Subject: Kernel time and xntpd Sender: current-owner@FreeBSD.org Precedence: bulk I have been running xntpd for awhile now on some of my FreeBSD systems, and it seems that xntpd has to perform a step adjustment of about -0.14 sec approximately once an hour to stay in sync with a non-FreeBSD remote time source. This is an error of about 40ppm. On the other hand, other FreeBSD systems seem to stay in sync with a FreeBSD master with a stability of less than 1ppm. This would seem to indicate that there are still errors in the kernel timekeeping in FreeBSD. Are any currently known? - Gene From owner-freebsd-current Sun Mar 26 20:48:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA03543 for current-outgoing; Sun, 26 Mar 1995 20:48:53 -0800 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 UAA03537 for ; Sun, 26 Mar 1995 20:48:45 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA07627; Mon, 27 Mar 1995 14:44:42 +1000 Date: Mon, 27 Mar 1995 14:44:42 +1000 From: Bruce Evans Message-Id: <199503270444.OAA07627@godzilla.zeta.org.au> To: current@FreeBSD.org, starkhome!gene@sbstark.cs.sunysb.edu Subject: Re: Kernel time and xntpd Sender: current-owner@FreeBSD.org Precedence: bulk >I have been running xntpd for awhile now on some of my FreeBSD systems, >and it seems that xntpd has to perform a step adjustment of about >-0.14 sec approximately once an hour to stay in sync with a non-FreeBSD >remote time source. This is an error of about 40ppm. On the other hand, >other FreeBSD systems seem to stay in sync with a FreeBSD master with >a stability of less than 1ppm. This would seem to indicate that there >are still errors in the kernel timekeeping in FreeBSD. Are any currently >known? The 8254 timer frequency is very hardware dependent. I have two systems that have a relative drift of 3.6 seconds/hour. One drifts forwards, the other backwards. The frequency should be calibrated. This is easier if you have an accurate clock to calibrate it agains (the RTC is said to be less accurate and/or more unstable). Try changing TIMER_FREQ to ((int) (NOMINAL_TIMER_FREQ * (1 + 0.14 / 3600))). Bruce From owner-freebsd-current Sun Mar 26 21:10:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA03971 for current-outgoing; Sun, 26 Mar 1995 21:10:16 -0800 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA03965 for ; Sun, 26 Mar 1995 21:10:13 -0800 Received: from corto.inria.fr (root@corto.inria.fr [128.93.11.2]) by concorde.inria.fr (8.6.10/8.6.9) with ESMTP id HAA11871 for ; Mon, 27 Mar 1995 07:09:47 +0200 Received: from alix.inria.fr (alix.inria.fr [128.93.11.42]) by corto.inria.fr (8.6.8/8.6.6) with ESMTP id HAA21470 for ; Mon, 27 Mar 1995 07:09:39 +0200 From: Herve Soulard Received: (soulard@localhost) by alix.inria.fr (8.6.10/8.6.6) id HAA09648 for current@freebsd.org; Mon, 27 Mar 1995 07:09:48 +0200 Date: Mon, 27 Mar 1995 07:09:48 +0200 Message-Id: <199503270509.HAA09648@alix.inria.fr> To: current@FreeBSD.org Subject: Problem with newfs. Sender: current-owner@FreeBSD.org Precedence: bulk Hi, I've tried to install the last SNAP but it fails on newfs my root partition with the following messages (plenty): wd0a: wdstart: timeout waiting for DRQ writing fsbn 304 of 304-319 (wd0 bn 170432; cn 343 tn 9 sn 25) wd0: status 53 error 4 The 950210 SNAP worked fine. Herve Soulard. From owner-freebsd-current Sun Mar 26 21:16:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04394 for current-outgoing; Sun, 26 Mar 1995 21:16:26 -0800 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 VAA04387 for ; Sun, 26 Mar 1995 21:16:24 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id VAA24530; Sun, 26 Mar 1995 21:16:11 -0800 From: Poul-Henning Kamp Message-Id: <199503270516.VAA24530@ref.tfs.com> Subject: Re: Problem with newfs. To: Herve.Soulard@inria.fr (Herve Soulard) Date: Sun, 26 Mar 1995 21:16:10 -0800 (PST) Cc: current@FreeBSD.org In-Reply-To: <199503270509.HAA09648@alix.inria.fr> from "Herve Soulard" at Mar 27, 95 07:09:48 am Content-Type: text Content-Length: 493 Sender: current-owner@FreeBSD.org Precedence: bulk > Hi, > > I've tried to install the last SNAP but it fails on newfs my > root partition with the following messages (plenty): > > wd0a: wdstart: timeout waiting for DRQ writing fsbn 304 of 304-319 > (wd0 bn 170432; cn 343 tn 9 sn 25) wd0: status 53 > error 4 What kind of disk ? -- 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 Sun Mar 26 21:28:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04508 for current-outgoing; Sun, 26 Mar 1995 21:28:40 -0800 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 VAA04498 for ; Sun, 26 Mar 1995 21:28:22 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA08376; Mon, 27 Mar 1995 15:25:40 +1000 Date: Mon, 27 Mar 1995 15:25:40 +1000 From: Bruce Evans Message-Id: <199503270525.PAA08376@godzilla.zeta.org.au> To: freebsd-current@freefall.cdrom.com, jc@irbs.com Subject: Re: Slice errors Sender: current-owner@FreeBSD.org Precedence: bulk >I have a -current system with 3 Conner CP30200 SCSI drives. I have >been using a C/H/S geometry of XXX/8/256 since Rodney mentioned >this as the optimum geometry for SCSI disks and ufs. Prior to that >I used XXX/64/32 as reported by the Adaptec controller. >With the new slice scheme I get this error for all drives: > sd0: raw partition size != slice size > sd0: start 0, end 416107, size 416108 > sd0c: start 0, end 413695, size 413696 >The capacity reported for these drives is 416108 blocks. It appears >to be complaining that the slice is 416108 blocks but partition c >is only 413696 blocks. 416108 - 413696 = 2412 = 2048(one cylinder) + 364. It used to be hard avoid the size being rounded to a cylinder boundary (editing the label with `disklabel -e' always rounded it). The off by one error for the number of cylinders may have been from believing the BIOS geometry instead of the geometry that was printed by the the driver. The BIOS sometimes subtracts one from the number of of cylinders. >Ok, I'll make the c partition == 416108, >who cares. Disklabel says, partition c extends past end of unit >and does not write the label. There are no DOS partitions on these >Conner drives, 100% FreeBSD. I can't explain this. Is the fdisk output that you quoted (with 50000 sectors) for this drive. >All of my partitions end on cylinder boundaries due to bad experiences >in the past. I don't know of any problems with partitions not ending on cylinder boundaries except in the user interface. >Do I have to use the bogus geometry reorted by the >drive and rework all of my labels for this message to go away? No. >I have another system with a 1Gig SCSI disk that has a DOS partiton >and a FreeBSD partition. The physical disk is larger than my c >partition but I do not get any error messages. The capacity of this >disk is 2031705 blocks. > sd0s1: start 32, end = 409599, size 409568: OK > sd0s2: start 409600, end = 2031615, size 1622016: OK The c partition should have the same size as the slice (smaller than the physical disk of you have more than one (nonempty) slice). Bruce From owner-freebsd-current Sun Mar 26 21:38:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04629 for current-outgoing; Sun, 26 Mar 1995 21:38:35 -0800 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 VAA04623 for ; Sun, 26 Mar 1995 21:38:20 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA08650; Mon, 27 Mar 1995 15:36:47 +1000 Date: Mon, 27 Mar 1995 15:36:47 +1000 From: Bruce Evans Message-Id: <199503270536.PAA08650@godzilla.zeta.org.au> To: jc@irbs.com, rgrimes@gndrsh.aac.dev.com Subject: Re: Slice errors Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> 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 >Use fdisk -u to correct the partition table so that size==size of >your BSD c or d partition and things should be fine. What you see >above is the bogus partition table that gets installed if you install >new boot blocks. This advice no longer applies. The bogus partition table is specially handled to make it work. Changing it risks introducing bugs and changes will be blown away by new boot blocks. Bruce From owner-freebsd-current Sun Mar 26 21:41:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04729 for current-outgoing; Sun, 26 Mar 1995 21:41:50 -0800 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 VAA04723 for ; Sun, 26 Mar 1995 21:41:47 -0800 Received: by sequent.kiae.su id AA04338 (5.65.kiae-2 ); Mon, 27 Mar 1995 08:36:20 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 27 Mar 95 08:36:19 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id JAA00257; Mon, 27 Mar 1995 09:33:14 +0400 To: Bob Willcox Cc: freebsd-current@freefall.cdrom.com References: In-Reply-To: ; from Bob Willcox at Sun, 26 Mar 1995 21:19:45 -0600 (CST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 27 Mar 1995 09:33:13 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: tgetnum wierdness on -current Lines: 50 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 2375 Sender: current-owner@FreeBSD.org Precedence: bulk In message Bob Willcox writes: >Andrey A. Chernov, Black Mage wrote: >> >> In message Bob Willcox writes: >> >Except that here my xterm termcap entry specifies line number as >> >24, yet tgetnum("li") returns 65 when executed in a remote xterm, >> >regardless of window size or termcap setting. >> >> What do you mean by "executed in a remote xterm"? >> As I understand, you need to check environment (TERM,TERMCAP) >> and termcap file on _remote_ system... >>From an xterm on one system (running FreeBSD 1.1.5.1) I am rlogining >into another system (running FreeBSD -current built today). The >termcap file on the remote (-current) system looks ok and has a >line count of 24 (li#24). However, if I do a tgetnum("li") (or >the tput li command) the output value is 65. From a virtual console >or xterm on the -current system I get the correct output from >tgetnum("li"). Terminal entry can comes from various sources: /usr/share/misc/termcap ~/.termcap $TERMCAP f.e. To be shure just use one of the tests coming from lib/termlib/TEST, I think it is test1, compile it on -current with -ltermcap and run it on remote xterm. It just print out terminal entry, then seek li= there. If li=65, check various sources mentioned above, if all of them says li=24, there can be bug in tgetent, if all sources and output says li=24, there is bug in tgetnum. >The application in question is files-2.2p1 that I am trying to port >to run on FreeBSD. Whenever it receives a SIGWINCH signal it >terminates the current window by calling endwin() then reinstates >it by calling initscr(). It also calls wrefresh() for each of its >logical windows plus a number of other initializations. It is right method when window changes. Please specify more detaily which ioctl failed in setterm(). >I can email you the file that handles all of this if you would like >(its about 1000 lines). I have had little experience with curses >and can't really tell if what is being done is ligitmate or not. I don't have enough time now... -- 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 Sun Mar 26 21:47:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04913 for current-outgoing; Sun, 26 Mar 1995 21:47:59 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA04906; Sun, 26 Mar 1995 21:47:58 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Herve Soulard cc: current@FreeBSD.org Subject: Re: Problem with newfs. In-reply-to: Your message of "Mon, 27 Mar 95 07:09:48 +0200." <199503270509.HAA09648@alix.inria.fr> Date: Sun, 26 Mar 1995 21:47:58 -0800 Message-ID: <4904.796283278@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > wd0a: wdstart: timeout waiting for DRQ writing fsbn 304 of 304-319 > (wd0 bn 170432; cn 343 tn 9 sn 25) wd0: status 53 > error 4 > > The 950210 SNAP worked fine. &^*()%$#@*!! This is the second such report. Thank you for reporting it. I am beginning to get the feeling that something is not altogether kosher in the wd driver now! :-( Jordan From owner-freebsd-current Sun Mar 26 21:50:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04949 for current-outgoing; Sun, 26 Mar 1995 21:50:05 -0800 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 VAA04943 for ; Sun, 26 Mar 1995 21:50:03 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id VAA13052; Sun, 26 Mar 1995 21:48:41 -0800 From: "Rodney W. Grimes" Message-Id: <199503270548.VAA13052@gndrsh.aac.dev.com> Subject: Re: Slice errors To: bde@zeta.org.au (Bruce Evans) Date: Sun, 26 Mar 1995 21:48:41 -0800 (PST) Cc: jc@irbs.com, freebsd-current@freefall.cdrom.com In-Reply-To: <199503270536.PAA08650@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 95 03:36:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1323 Sender: current-owner@FreeBSD.org Precedence: bulk > > >> 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 > > >Use fdisk -u to correct the partition table so that size==size of > >your BSD c or d partition and things should be fine. What you see > >above is the bogus partition table that gets installed if you install > >new boot blocks. > > This advice no longer applies. The bogus partition table is specially > handled to make it work. Changing it risks introducing bugs and > changes will be blown away by new boot blocks. That advise got the chap up and running from private email I got back from him. And he now has given me a patch for fdisk that fixes some real stupid errors (writting 0 as a value for beginning sector if you let it calculate the beg/end C/H/S addresses). I am using that advice here on all my machines and it is much happier about this than allowing the bogus 500000 block boot stuff live!!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun Mar 26 21:53:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA05005 for current-outgoing; Sun, 26 Mar 1995 21:53:39 -0800 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 VAA04997 for ; Sun, 26 Mar 1995 21:53:24 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA08940; Mon, 27 Mar 1995 15:52:27 +1000 Date: Mon, 27 Mar 1995 15:52:27 +1000 From: Bruce Evans Message-Id: <199503270552.PAA08940@godzilla.zeta.org.au> To: freebsd-current@freefall.cdrom.com, jmz@cabri.obs-besancon.fr Subject: Re: sd errors Sender: current-owner@FreeBSD.org Precedence: bulk >With a -current kernel (03/25) I get the following messages after boot: >/kernel: sd0: raw partition size != slice size >/kernel: sd0: start 0, end 2065249, size 2065250 >/kernel: sd0c: start 0, end 2390975, size 2390976 >/kernel: sd0: truncating raw partition >/kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice >/kernel: sd0: start 0, end 2065249, size 2065250 >/kernel: sd0d: start 0, end 2390975, size 2390976 >/kernel: sd1: raw partition size != slice size >/kernel: sd1: start 0, end 1075648, size 1075649 >/kernel: sd1c: start 0, end 1075451, size 1075452 >/kernel: sd1: raw partition size != slice size >/kernel: sd1: start 0, end 1075648, size 1075649 >/kernel: sd1c: start 0, end 1075451, size 1075452 >The drives were newfs/labelled a long time ago (1.1.5). On both disks, >the c partition stands the whole disk. It not is not mounted for sd0, >but mounted for sd1. Is there a way to solve this? (NO don't tell me >to newfs my drives!) These errors are probably harmless. The c partitions apparently weren't the whole disk. This may have been caused by rounding their size to a cylinder boundary. The end of the c partition isn't critical for sd drives so fixing it should not do anything except the stop the warnings. The end of the c partition is critical for old wd drives (the bad sector table goes there). If you remove the d partition, 1.1.5 may have problems. The 2.x sd driver silently ignores what the disklabel says about the d partition and replaces it by the whole disk (offset 0 and size reported by the drive), so removing it should not cause any compatibility problems for 2.x. Bruce From owner-freebsd-current Sun Mar 26 22:06:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA05136 for current-outgoing; Sun, 26 Mar 1995 22:06:01 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA05130; Sun, 26 Mar 1995 22:05:58 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id WAA00249; Sun, 26 Mar 1995 22:05:46 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id WAA04930; Sun, 26 Mar 1995 22:05:45 -0800 Message-Id: <199503270605.WAA04930@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: Herve Soulard , current@FreeBSD.org Subject: Re: Problem with newfs. In-reply-to: Your message of "Sun, 26 Mar 95 21:47:58 PST." <4904.796283278@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 22:05:44 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >> wd0a: wdstart: timeout waiting for DRQ writing fsbn 304 of 304-319 >> (wd0 bn 170432; cn 343 tn 9 sn 25) wd0: status 53 >> error 4 >> >> The 950210 SNAP worked fine. > >&^*()%$#@*!! > >This is the second such report. Thank you for reporting it. I am >beginning to get the feeling that something is not altogether kosher >in the wd driver now! :-( John thinks that it is the multi-block I/O code. Apparantly some drives say they can do it but can't. The solution that will be implemented is a kernel 'flags' option to enable it (disabled my default). -DG From owner-freebsd-current Sun Mar 26 22:29:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA05577 for current-outgoing; Sun, 26 Mar 1995 22:29:16 -0800 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 WAA05566 for ; Sun, 26 Mar 1995 22:29:03 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA09705; Mon, 27 Mar 1995 16:26:49 +1000 Date: Mon, 27 Mar 1995 16:26:49 +1000 From: Bruce Evans Message-Id: <199503270626.QAA09705@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Subject: Re: Slice errors Cc: freebsd-current@freefall.cdrom.com, jc@irbs.com Sender: current-owner@FreeBSD.org Precedence: bulk >> >Use fdisk -u to correct the partition table so that size==size of >> >your BSD c or d partition and things should be fine. What you see >> >above is the bogus partition table that gets installed if you install >> >new boot blocks. >> >> This advice no longer applies. The bogus partition table is specially >> handled to make it work. Changing it risks introducing bugs and >> changes will be blown away by new boot blocks. >That advise got the chap up and running from private email I got >back from him. And he now has given me a patch for fdisk that >fixes some real stupid errors (writting 0 as a value for beginning >sector if you let it calculate the beg/end C/H/S addresses). I introduced that bug :-(. There was no way to delete a partition using fdisk. There is still no way to clear all the active flags. Setting the size AND the base of a partition should clear everything. (It's convenient to have empty partitions with a nonzero base. It stops some (braindamaged) systems from reordering the partition numbers.) >I am using that advice here on all my machines and it is much happier >about this than allowing the bogus 500000 block boot stuff live!!! I want the invalid table to just work. I tested it, but only on a floppy, so I want to see more bug reports about it if there are any bugs. Bruce From owner-freebsd-current Sun Mar 26 22:38:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA05711 for current-outgoing; Sun, 26 Mar 1995 22:38:50 -0800 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 WAA05704; Sun, 26 Mar 1995 22:38:31 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA09991; Mon, 27 Mar 1995 16:35:31 +1000 Date: Mon, 27 Mar 1995 16:35:31 +1000 From: Bruce Evans Message-Id: <199503270635.QAA09991@godzilla.zeta.org.au> To: davidg@Root.COM, jkh@freefall.cdrom.com Subject: Re: Problem with newfs. Cc: Herve.Soulard@inria.fr, current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>> wd0a: wdstart: timeout waiting for DRQ writing fsbn 304 of 304-319 >>> (wd0 bn 170432; cn 343 tn 9 sn 25) wd0: status 53 >>> error 4 >>> >>> The 950210 SNAP worked fine. >> >>&^*()%$#@*!! >> >>This is the second such report. Thank you for reporting it. I am >>beginning to get the feeling that something is not altogether kosher >>in the wd driver now! :-( > John thinks that it is the multi-block I/O code. Apparantly some drives say >they can do it but can't. The solution that will be implemented is a kernel >'flags' option to enable it (disabled my default). It could also be from reducing a delay from 11 times the spec. to only 2 times. Bruce From owner-freebsd-current Sun Mar 26 22:42:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA05782 for current-outgoing; Sun, 26 Mar 1995 22:42:12 -0800 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 WAA05769 for ; Sun, 26 Mar 1995 22:42:09 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id WAA13215; Sun, 26 Mar 1995 22:39:06 -0800 From: "Rodney W. Grimes" Message-Id: <199503270639.WAA13215@gndrsh.aac.dev.com> Subject: Re: Slice errors To: bde@zeta.org.au (Bruce Evans) Date: Sun, 26 Mar 1995 22:39:06 -0800 (PST) Cc: bde@zeta.org.au, freebsd-current@freefall.cdrom.com, jc@irbs.com In-Reply-To: <199503270626.QAA09705@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 95 04:26:49 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1992 Sender: current-owner@FreeBSD.org Precedence: bulk > > >> >Use fdisk -u to correct the partition table so that size==size of > >> >your BSD c or d partition and things should be fine. What you see > >> >above is the bogus partition table that gets installed if you install > >> >new boot blocks. > >> > >> This advice no longer applies. The bogus partition table is specially > >> handled to make it work. Changing it risks introducing bugs and > >> changes will be blown away by new boot blocks. > > >That advise got the chap up and running from private email I got > >back from him. And he now has given me a patch for fdisk that > >fixes some real stupid errors (writting 0 as a value for beginning > >sector if you let it calculate the beg/end C/H/S addresses). > > I introduced that bug :-(. There was no way to delete a partition > using fdisk. There is still no way to clear all the active flags. > Setting the size AND the base of a partition should clear everything. > (It's convenient to have empty partitions with a nonzero base. It > stops some (braindamaged) systems from reordering the partition > numbers.) Yes there was a way to delete partitions using fdisk, I've been using it to do that for a very long time. You had to say ``y'' to the specify beg/end C/H/S and manual set them all to zero. Your changes serously broke the usability of fdisk in that it now always writes a very invalid partition if the user lets fdisk pick the beg/end values :-(. You want to fix it or should I? > >I am using that advice here on all my machines and it is much happier > >about this than allowing the bogus 500000 block boot stuff live!!! > > I want the invalid table to just work. I tested it, but only on a > floppy, so I want to see more bug reports about it if there are any > bugs. You won't see any from me on it, I always run with a valid partition table. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun Mar 26 23:08:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA07445 for current-outgoing; Sun, 26 Mar 1995 23:08:11 -0800 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 XAA07423 for ; Sun, 26 Mar 1995 23:08:06 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA10742; Mon, 27 Mar 1995 17:03:40 +1000 Date: Mon, 27 Mar 1995 17:03:40 +1000 From: Bruce Evans Message-Id: <199503270703.RAA10742@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Subject: Re: Slice errors Cc: freebsd-current@freefall.cdrom.com, jc@irbs.com Sender: current-owner@FreeBSD.org Precedence: bulk >Yes there was a way to delete partitions using fdisk, I've been using >it to do that for a very long time. You had to say ``y'' to the >specify beg/end C/H/S and manual set them all to zero. Your changes >serously broke the usability of fdisk in that it now always writes >a very invalid partition if the user lets fdisk pick the beg/end >values :-(. It's not clear that valid partitions can start at 0. You can still create such partitions by saying ``y'' to the question and correcting the S value. >You want to fix it or should I? You fix it. >> >I am using that advice here on all my machines and it is much happier >> >about this than allowing the bogus 500000 block boot stuff live!!! >> >> I want the invalid table to just work. I tested it, but only on a >> floppy, so I want to see more bug reports about it if there are any >> bugs. >You won't see any from me on it, I always run with a valid partition >table. I've always had a minimal valid partition table of size 17 (C=1, H=1, S=17) in my biosboot/start.S, but I don't have any partitions that start at 0 here, and someone named rgrimes ;-) said that it didn't work in general, so I didn't commit the change. Bruce From owner-freebsd-current Sun Mar 26 23:28:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA09928 for current-outgoing; Sun, 26 Mar 1995 23:28:25 -0800 Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA09914 for ; Sun, 26 Mar 1995 23:28:22 -0800 Received: from metal.ops.neosoft.com (root@glenn-slip45.nmt.edu [129.138.5.145]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id BAA24865 for ; Mon, 27 Mar 1995 01:28:07 -0600 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id AAA07410 for current@freebsd.org; Mon, 27 Mar 1995 00:28:02 -0700 From: Scott Mace Message-Id: <199503270728.AAA07410@metal.ops.neosoft.com> Subject: weird stuff since the slice changes To: current@FreeBSD.org Date: Mon, 27 Mar 1995 00:28:01 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 757 Sender: current-owner@FreeBSD.org Precedence: bulk Eversince the the new stuff I get the following: sd0s1: start 32, end = 509951, size 509920: OK sd0s3: start 509952, end = 641023, size 131072: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 509952, end 641023, size 131072 sd0d: start 0, end 641675, size 641676 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0g: start 32, end 509951, size 509920 sd1s1: start 0, end = 4194057, size 4194058: OK sd1s1: start 0, end = 4194057, size 4194058: OK sd1s1: start 0, end = 4194057, size 4194058: OK I built these partitions with a 2.0 release boot disk way back when... My first drive has a DOS and small freebsd partition and the second drive is all freebsd. Any suggested action? Scott From owner-freebsd-current Mon Mar 27 00:00:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA13204 for current-outgoing; Mon, 27 Mar 1995 00:00:23 -0800 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA13190 for ; Mon, 27 Mar 1995 00:00:20 -0800 Received: by pelican.com (Smail3.1.28.1 #5) id m0rt9iW-000K0iC; Mon, 27 Mar 95 00:00 WET Message-Id: Date: Mon, 27 Mar 95 00:00 WET From: pete@pelican.com (Pete Carah) To: current@FreeBSD.org Subject: Re: Innd In-Reply-To: References: <199503231719.TAA23687@katiska.clinet.fi> <9503231915.AA08773@blaise.ibp.fr> <199503261709.UAA08986@zetor.clinet.fi> Organization: Pelican Consulting Sender: current-owner@FreeBSD.org Precedence: bulk ... >> > Don't use ACT_MMAP in config.data for the reading of the active file. >>Removed MMAP, and it seems to be stable now. In article ache writes: >All this mess comes becomes msync() and munmap() don't update >modification times at all. That may not be the only reason - note that innd cores about once/day on an sgi indigo under 4.0.5 if mmap is used, and runs for months without it, and there mmap behaves supposedly OK (and it really was the only change). Either innd doesn't really handle mmap right or sgi isn't much better than we are :-) (and I've taken to not using mmap-active at all...) -- Pete From owner-freebsd-current Mon Mar 27 01:02:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA20956 for current-outgoing; Mon, 27 Mar 1995 01:02:59 -0800 Received: from reinfra.regent.e-technik.tu-muenchen.de (root@reinfra.regent.e-technik.tu-muenchen.de [129.187.230.226]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA20873 for ; Mon, 27 Mar 1995 01:02:28 -0800 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by reinfra.regent.e-technik.tu-muenchen.de with SMTP id <18905>; Mon, 27 Mar 1995 11:02:06 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id AAA20140 for current%freebsd.org@regent.e-technik.tu-muenchen.de; Mon, 27 Mar 1995 00:57:47 +0200 Date: Mon, 27 Mar 1995 00:57:47 +0200 From: Julian Howard Stacey Message-Id: <199503262257.AAA20140@vector.eikon.e-technik.tu-muenchen.de> To: current@FreeBSD.org Subject: amusing buglet with nfs & msdos file systems Sender: current-owner@FreeBSD.org Precedence: bulk Here's a strange bug using nfs & msdos file systems .... All the files in the target directory come out zero size, when nfs copying from one host's /dos to another host's /dos, if target /dos is 755 root. Detail follows: With 2 hosts, called `lion' & `vector', with nfs mounts of all directories such that lion:/dos appears as vector:/host/lion/dos etcetera... (vector runs a 10 day old current, lion about the same, the symptom/fault/phenomena has been the same the last few weeks). vector ttyp6 9 % pwd /dos2/bin/vsl vector ttyp6 8 % tar cf - * | ( cd /host/lion/dos/bin/vsl ; tar xf - ) < 0 size files created, as said > I got round the problem with: vector ttyp6 10 % tar cf /host/lion/tmp/t * lion ttyp1 1 % tar xf /tmp/t I had to go superuser on `lion' though; as before `su' I got: lion ttyp1 9 % tar xf /tmp/t tar: Could not create file cat.exe : Permission denied .... etc .... Looking further: lion ttyp1 6 % pwd ; ls -al | head /dos/bin/vsl drwxr-xr-x 1 root wheel 2048 Mar 19 16:21 ./ drwxr-xr-x 1 root wheel 2048 Mar 19 16:21 ../ lion ttyp1 8 % cd /dos ; ls -al | head drwxr-xr-x 1 root wheel 16384 Jan 1 1980 ./ drwxr-xr-x 19 root wheel 1024 Mar 19 15:32 ../ lion ttyp1 11 % cd / ; sx umount /dos ; ls -al drwxr-xr-x 2 root wheel 512 Mar 4 17:27 dos/ lion ttyp1 14 % sx chmod 777 /dos ; sx mount /dos vector ttyp6 11 % tar cf - * | ( cd /host/lion/dos/bin/vsl ; tar xf - ) lion ttyp1 16 % cd dos/bin/vsl ; ls -l | more -rwxrwxrwx 1 root wheel 18285 Nov 17 03:19 addcr.exe* -rwxrwxrwx 1 root wheel 17037 Nov 17 03:19 brackets.exe* PS sx is a little suid 0 program running thing. --- Julian Stacey , +49 89 268616 (Don't Use: ) From owner-freebsd-current Mon Mar 27 01:56:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA27619 for current-outgoing; Mon, 27 Mar 1995 01:56:12 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA27604 for ; Mon, 27 Mar 1995 01:56:04 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id KAA06202; Mon, 27 Mar 1995 10:54:07 +0100 From: Paul Richards Message-Id: <199503270954.KAA06202@isl.cf.ac.uk> Subject: Re: shared library versioning To: davidg@Root.COM Date: Mon, 27 Mar 1995 10:54:06 +0100 (BST) Cc: bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199503261953.LAA00456@corbin.Root.COM> from "David Greenman" at Mar 26, 95 11:53:28 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 715 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to David Greenman who said > > In other cases this would be true...but msync has never worked correctly in > FreeBSD - it always returned EINVAL because of bugs in it. I just fixed this a > few days ago. In the current scheme, passing garbage to msync() for the flags > will be no worse than the previous behavior. I suggest we just leave it alone > unless you have some other reason to bump the libc major number. > Jordan's just added new hash code..... -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Mon Mar 27 02:24:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00781 for current-outgoing; Mon, 27 Mar 1995 02:24:46 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA00754 for ; Mon, 27 Mar 1995 02:24:37 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id SAA00680; Mon, 27 Mar 1995 18:24:58 GMT Date: Mon, 27 Mar 1995 18:24:58 +0000 () From: Brian Tao To: FREEBSD-CURRENT-L Subject: Re: Problem with newfs. In-Reply-To: <4904.796283278@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Sun, 26 Mar 1995, Jordan K. Hubbard wrote: > > This is the second such report. Thank you for reporting it. I am > beginning to get the feeling that something is not altogether kosher > in the wd driver now! :-( Uh oh... I will be installing the latest snapshot on a few other machines in my department, but they all run IDE drives. I'll be sure to keep 950322 and 950210 handy just in case. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Mon Mar 27 03:27:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA05369 for current-outgoing; Mon, 27 Mar 1995 03:27:56 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA05283 for ; Mon, 27 Mar 1995 03:26:43 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA12303; Mon, 27 Mar 1995 12:58:46 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id MAA25295 for current@freefall.cdrom.com; Mon, 27 Mar 1995 12:58:46 +0200 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id MAA29588; Mon, 27 Mar 1995 12:42:07 +0200 From: j@narcisa.sax.de (J Wunsch) Message-Id: <199503271042.MAA29588@bonnie.tcd-dresden.de> Subject: Re: FreeBSD problems - VM bug? To: davidg@Root.COM Date: Mon, 27 Mar 1995 12:42:07 +0200 (MET DST) Cc: smace@metal-mail.neosoft.com, mw@pandora.sax.de, current@freefall.cdrom.com Reply-To: joerg_wunsch@uriah.heep.sax.de In-Reply-To: <199503262237.OAA00314@corbin.Root.COM> from "David Greenman" at Mar 26, 95 02:37:43 pm X-Phone: +49-351-2012 669 Reply-To: joerg_wunsch@uriah.heep.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 881 Sender: current-owner@FreeBSD.org Precedence: bulk As David Greenman wrote: | | >I experienced the random singal 11's back then when my -current was about | >equal to the SNAP. I no longer get those problems with the latest -current. | >The problem seemed to hinge around -O2 optimization instead of -O. ... | I don't think the problem is in any way related to -O2 optimization. There | were a whole slew of VM bugs that were fixed in post-0210 SNAP that were | causing problems. As far as I know, the entire source tree except the kernel | is still built -O2. But you realized that Martin's kernel is of 950221, David? (Only his binaries are from the 950210-SNAP.) That's why i directed him to the -current list. -- cheers, J"org private: joerg_wunsch@uriah.heep.sax.de http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 27 05:18:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA08943 for current-outgoing; Mon, 27 Mar 1995 05:18:09 -0800 Received: from obiwan.pmr.com ([199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA08934 for ; Mon, 27 Mar 1995 05:18:05 -0800 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0rtEff-00030WC; Mon, 27 Mar 95 07:17 CST Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: tgetnum wierdness on -current To: ache@astral.msk.su (Andrey A. Chernov Black Mage) Date: Mon, 27 Mar 1995 07:17:26 -0600 (CST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: from "Andrey A. Chernov, Black Mage" at Mar 27, 95 09:33:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2137 Sender: current-owner@FreeBSD.org Precedence: bulk Andrey A. Chernov, Black Mage wrote: > > Terminal entry can comes from various sources: /usr/share/misc/termcap > ~/.termcap $TERMCAP f.e. > To be shure just use one of the tests coming from lib/termlib/TEST, > I think it is test1, compile it on -current with -ltermcap and > run it on remote xterm. It just print out > terminal entry, then seek li= there. If li=65, check various > sources mentioned above, if all of them says li=24, there can be > bug in tgetent, if all sources and output says li=24, there > is bug in tgetnum. Well, the termcap entry for xterm in -current does, indeed, specify a line number of 65, so that is where the 65 is coming from and that would seem to exonerate tgetnum. > > >The application in question is files-2.2p1 that I am trying to port > >to run on FreeBSD. Whenever it receives a SIGWINCH signal it > >terminates the current window by calling endwin() then reinstates > >it by calling initscr(). It also calls wrefresh() for each of its > >logical windows plus a number of other initializations. > > It is right method when window changes. > Please specify more detaily which ioctl failed in setterm(). It (the files program) does an endwin() followed by an ioctl(0, TIOCGWINSZ, &win_ws) to get the new window sizes (which works). Then it does an initscr() which calls setterm() which attempts an ioctl(STDERR_FILENO, TIOCGWINSZ, &win) that fails. setterm() then defaults to using the termcap values for lines and columns. The only significant difference appears to be the file descriptor. A file descriptor of 0 works, whereas, 2 does not. Poking around a bit more in the source for files I see that it will (under some circumstances that I have not yet nailed down) close and reopen stderr. Could this be the cause of the problem? I don't know stderr is opened to at the momemt (of the failure). I will have to dig more into this. -- Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob Austin, TX or: @uudell.us.dell.com:obiwan!bob 512-258-4224 (home), 512-838-3914 (work) or: obiwan%bob@uunet.uu.net From owner-freebsd-current Mon Mar 27 05:29:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA09329 for current-outgoing; Mon, 27 Mar 1995 05:29:34 -0800 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 FAA09299 for ; Mon, 27 Mar 1995 05:28:47 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA19834; Mon, 27 Mar 1995 23:24:51 +1000 Date: Mon, 27 Mar 1995 23:24:51 +1000 From: Bruce Evans Message-Id: <199503271324.XAA19834@godzilla.zeta.org.au> To: davidg@Root.COM, paul@isl.cf.ac.uk Subject: Re: shared library versioning Cc: bde@zeta.org.au, current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >> .. >> will be no worse than the previous behavior. I suggest we just leave it alone >> unless you have some other reason to bump the libc major number. >> >Jordan's just added new hash code..... There is no problem for new interfaces, except possibly from namespace pollution. Bruce From owner-freebsd-current Mon Mar 27 05:29:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA09337 for current-outgoing; Mon, 27 Mar 1995 05:29:39 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA09330 for ; Mon, 27 Mar 1995 05:29:35 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id IAA06005; Mon, 27 Mar 1995 08:27:57 -0500 From: John Capo Message-Id: <199503271327.IAA06005@irbs.com> Subject: Re: Slice errors To: bde@zeta.org.au (Bruce Evans) Date: Mon, 27 Mar 1995 08:27:56 -0500 (EST) Cc: freebsd-current@freefall.cdrom.com (freebsd-current) In-Reply-To: <199503270525.PAA08376@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 95 03:25:40 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: 2717 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: > > >I have a -current system with 3 Conner CP30200 SCSI drives. I have > >been using a C/H/S geometry of XXX/8/256 since Rodney mentioned > >this as the optimum geometry for SCSI disks and ufs. Prior to that > >I used XXX/64/32 as reported by the Adaptec controller. > > >With the new slice scheme I get this error for all drives: > > > sd0: raw partition size != slice size > > sd0: start 0, end 416107, size 416108 > > sd0c: start 0, end 413695, size 413696 > > >The capacity reported for these drives is 416108 blocks. It appears > >to be complaining that the slice is 416108 blocks but partition c > >is only 413696 blocks. > > 416108 - 413696 = 2412 = 2048(one cylinder) + 364. It used to be hard > avoid the size being rounded to a cylinder boundary (editing the label > with `disklabel -e' always rounded it). The off by one error for the > number of cylinders may have been from believing the BIOS geometry > instead of the geometry that was printed by the the driver. The BIOS > sometimes subtracts one from the number of of cylinders. > > >Ok, I'll make the c partition == 416108, > >who cares. Disklabel says, partition c extends past end of unit > >and does not write the label. There are no DOS partitions on these > >Conner drives, 100% FreeBSD. > > I can't explain this. Is the fdisk output that you quoted (with 50000 > sectors) for this drive. This was with the 50000 block disklabel. I tried to label it with in unmounted in multi-user and in single user. The old label was still there. I have seen the warning before that a partition extended past the end of the unit but it always wrote the label anyway. > > >All of my partitions end on cylinder boundaries due to bad experiences > >in the past. > > I don't know of any problems with partitions not ending on cylinder > boundaries except in the user interface. I had serious problems with not ending on cylinder boundaries at one point. I have not been willing do try it any other way since. I don't mind wasting a bit of disk space. > > >Do I have to use the bogus geometry reorted by the > >drive and rework all of my labels for this message to go away? > > No. > > >I have another system with a 1Gig SCSI disk that has a DOS partiton > >and a FreeBSD partition. The physical disk is larger than my c > >partition but I do not get any error messages. The capacity of this > >disk is 2031705 blocks. > > > sd0s1: start 32, end = 409599, size 409568: OK > > sd0s2: start 409600, end = 2031615, size 1622016: OK > > The c partition should have the same size as the slice (smaller than > the physical disk of you have more than one (nonempty) slice). > > Bruce > -- John Capo From owner-freebsd-current Mon Mar 27 05:33:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA09453 for current-outgoing; Mon, 27 Mar 1995 05:33:17 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA09447 for ; Mon, 27 Mar 1995 05:33:14 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id IAA06068; Mon, 27 Mar 1995 08:32:18 -0500 From: John Capo Message-Id: <199503271332.IAA06068@irbs.com> Subject: Re: Slice errors To: bde@zeta.org.au (Bruce Evans) Date: Mon, 27 Mar 1995 08:32:17 -0500 (EST) Cc: freebsd-current@freefall.cdrom.com (freebsd-current) In-Reply-To: <199503270536.PAA08650@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 95 03:36:47 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: 1248 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: > > >> 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 > > >Use fdisk -u to correct the partition table so that size==size of > >your BSD c or d partition and things should be fine. What you see > >above is the bogus partition table that gets installed if you install > >new boot blocks. > > This advice no longer applies. The bogus partition table is specially > handled to make it work. Changing it risks introducing bugs and > changes will be blown away by new boot blocks. > > Bruce > Maybe that is why I only write new boot blocks when it absolutely necessary. The label was found and I was able to use the drive. I just wanted to get rid of the "raw partition size != slice size" message. I had to either increase the size of the c partition, which disklabel would not do for some reaseon, or reduce the slice size. Is there a reason that writing boot blocks can't re-write whatever partition table exixts? -- John Capo From owner-freebsd-current Mon Mar 27 05:36:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA09550 for current-outgoing; Mon, 27 Mar 1995 05:36:03 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA09541 for ; Mon, 27 Mar 1995 05:35:53 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id OAA10199; Mon, 27 Mar 1995 14:35:18 +0100 From: Paul Richards Message-Id: <199503271335.OAA10199@isl.cf.ac.uk> Subject: Re: shared library versioning To: bde@zeta.org.au (Bruce Evans) Date: Mon, 27 Mar 1995 14:35:17 +0100 (BST) Cc: davidg@Root.COM, bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199503271324.XAA19834@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 95 11:24:51 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 776 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Bruce Evans who said > > >> .. > >> will be no worse than the previous behavior. I suggest we just leave it alone > >> unless you have some other reason to bump the libc major number. > >> > > >Jordan's just added new hash code..... > > There is no problem for new interfaces, except possibly from namespace > pollution. How do we deal witht the problem of binaries that use the new interface being run on older systems with the old library? Are we bumping the minor number, does the linker do anything about this? -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Mon Mar 27 06:12:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA10532 for current-outgoing; Mon, 27 Mar 1995 06:12:17 -0800 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 GAA10525 for ; Mon, 27 Mar 1995 06:12:05 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA20934; Tue, 28 Mar 1995 00:03:13 +1000 Date: Tue, 28 Mar 1995 00:03:13 +1000 From: Bruce Evans Message-Id: <199503271403.AAA20934@godzilla.zeta.org.au> To: bde@zeta.org.au, jc@irbs.com Subject: Re: Slice errors Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> This advice no longer applies. The bogus partition table is specially >> handled to make it work. Changing it risks introducing bugs and >> changes will be blown away by new boot blocks. >Maybe that is why I only write new boot blocks when it absolutely >necessary. The label was found and I was able to use the drive. >I just wanted to get rid of the "raw partition size != slice size" >message. I had to either increase the size of the c partition, >which disklabel would not do for some reaseon, or reduce the slice >size. The current version of disklabel can handle it (you must initialize su# in disktab and/or secperunit in `disklabel -e'). You can safely increase the size of the c partition to the size of the disk without changing the size of the partitions with file systems (keep them ending on cylinder boundaries). >Is there a reason that writing boot blocks can't re-write whatever >partition table exixts? disklabel(8) doesn't know that the partition table exists. It did in 1.1.5. That was wrong. Bruce From owner-freebsd-current Mon Mar 27 06:19:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA10655 for current-outgoing; Mon, 27 Mar 1995 06:19:08 -0800 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 GAA10649 for ; Mon, 27 Mar 1995 06:18:56 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA21244; Tue, 28 Mar 1995 00:16:45 +1000 Date: Tue, 28 Mar 1995 00:16:45 +1000 From: Bruce Evans Message-Id: <199503271416.AAA21244@godzilla.zeta.org.au> To: bde@zeta.org.au, paul@isl.cf.ac.uk Subject: Re: shared library versioning Cc: current@FreeBSD.org, davidg@Root.COM Sender: current-owner@FreeBSD.org Precedence: bulk >> >Jordan's just added new hash code..... >> >> There is no problem for new interfaces, except possibly from namespace >> pollution. >How do we deal witht the problem of binaries that use the new interface >being run on older systems with the old library? Are we bumping the minor >number, does the linker do anything about this? New binaries won't work with old libraries. We haven't bumped the minor number yet. I'm not sure how ld.so handles missing functions. New stuff should be added to special libraries for this and other reasons (the interfaces are more likely to change...). Bruce From owner-freebsd-current Mon Mar 27 11:23:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00295 for current-outgoing; Mon, 27 Mar 1995 11:23:57 -0800 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 LAA00273 for ; Mon, 27 Mar 1995 11:23:40 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA26467; Tue, 28 Mar 1995 03:44:22 +1000 Date: Tue, 28 Mar 1995 03:44:22 +1000 From: Bruce Evans Message-Id: <199503271744.DAA26467@godzilla.zeta.org.au> To: paul@isl.cf.ac.uk, wollman@halloran-eldar.lcs.mit.edu Subject: Re: shared library versioning Cc: bde@zeta.org.au, current@FreeBSD.org, davidg@Root.COM Sender: current-owner@FreeBSD.org Precedence: bulk >I didn't see a bump, but as a result of this change, it should be. Why just for this change? I don't want the version number bumped, I want more care taken to avoid having to bump it for unimportant changes. Bruce From owner-freebsd-current Mon Mar 27 11:27:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00477 for current-outgoing; Mon, 27 Mar 1995 11:27:36 -0800 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 LAA00463 for ; Mon, 27 Mar 1995 11:27:32 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA10247; Mon, 27 Mar 1995 13:19:30 -0500 Date: Mon, 27 Mar 1995 13:19:30 -0500 From: Garrett Wollman Message-Id: <9503271819.AA10247@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: shared library versioning In-Reply-To: <199503271744.DAA26467@godzilla.zeta.org.au> References: <199503271744.DAA26467@godzilla.zeta.org.au> Sender: current-owner@FreeBSD.org Precedence: bulk < said: >> I didn't see a bump, but as a result of this change, it should be. > Why just for this change? I don't want the version number bumped, I > want more care taken to avoid having to bump it for unimportant > changes. Because when a new function is added to a library, the minor version number needs to be incremented, so that users don't get confused. -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 Mon Mar 27 11:27:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00497 for current-outgoing; Mon, 27 Mar 1995 11:27:43 -0800 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 LAA00490 for ; Mon, 27 Mar 1995 11:27:41 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA10078; Mon, 27 Mar 1995 11:21:09 -0500 Date: Mon, 27 Mar 1995 11:21:09 -0500 From: Garrett Wollman Message-Id: <9503271621.AA10078@halloran-eldar.lcs.mit.edu> To: Paul Richards Cc: bde@zeta.org.au (Bruce Evans), davidg@Root.COM, current@FreeBSD.org Subject: Re: shared library versioning In-Reply-To: <199503271335.OAA10199@isl.cf.ac.uk> References: <199503271324.XAA19834@godzilla.zeta.org.au> <199503271335.OAA10199@isl.cf.ac.uk> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > How do we deal witht the problem of binaries that use the new interface > being run on older systems with the old library? Are we bumping the minor > number, does the linker do anything about this? I didn't see a bump, but as a result of this change, it should be. -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 Mon Mar 27 11:29:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00634 for current-outgoing; Mon, 27 Mar 1995 11:29:24 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA00611 for ; Mon, 27 Mar 1995 11:29:07 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23928; Mon, 27 Mar 1995 19:56:21 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA27331 for freebsd-current@FreeBSD.org; Mon, 27 Mar 1995 19:56:20 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id TAA16103 for freebsd-current@FreeBSD.org; Mon, 27 Mar 1995 19:26:23 +0200 From: J Wunsch Message-Id: <199503271726.TAA16103@uriah.heep.sax.de> Subject: Re: FreeBSD problems - VM bug? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 27 Mar 1995 19:26:22 +0200 (MET DST) In-Reply-To: from "Brian Tao" at Mar 27, 95 05:46:44 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 442 Sender: current-owner@FreeBSD.org Precedence: bulk As Brian Tao wrote: > > On Sun, 26 Mar 1995, J Wunsch wrote: > > > > But i've reported them earlier, they seem to be related to heavy > > NFS server activity. > > NFS *server* and not *client* related problems? Yes, server. Sorta ``external disk'' i've been using to compile a release on. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 27 11:35:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA01479 for current-outgoing; Mon, 27 Mar 1995 11:35:58 -0800 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 LAA01423 for ; Mon, 27 Mar 1995 11:35:43 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id UAA23773 for ; Mon, 27 Mar 1995 20:09:04 +0200 Message-Id: <199503271809.UAA23773@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: Small patch for ncftp-1.9.? Date: Mon, 27 Mar 1995 20:09:04 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk Hi I noticed that the current version of ncftp dos not do the very useful job af warning me about mail as my work version does. This patch will will fix this for bash(1) if MAILPATH is exported: (please apply in src/usr.bin/ncftp) *** main.#CTM# Fri Mar 10 08:11:20 1995 --- main.c Mon Mar 27 20:03:11 1995 *************** *** 461,466 **** --- 461,468 ---- (void) Strncpy(uinfo.homedir, pw->pw_dir); cp = getenv("MAIL"); if (cp == NULL) + cp = getenv("MAILPATH"); + if (cp == NULL) cp = getenv("mail"); if (cp == NULL) (void) sprintf(str, "/usr/spool/mail/%s", uinfo.username); -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Mar 27 11:48:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA02467 for current-outgoing; Mon, 27 Mar 1995 11:48:43 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA02459 for ; Mon, 27 Mar 1995 11:48:35 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id JAA02055; Mon, 27 Mar 1995 09:17:08 -0700 Date: Mon, 27 Mar 1995 09:17:08 -0700 Message-Id: <199503271617.JAA02055@trout.sri.MT.net> To: Paul Richards Cc: bde@zeta.org.au (Bruce Evans), davidg@Root.COM, current@FreeBSD.org Subject: Re: shared library versioning In-Reply-To: <199503271335.OAA10199@isl.cf.ac.uk> References: <199503271324.XAA19834@godzilla.zeta.org.au> <199503271335.OAA10199@isl.cf.ac.uk> Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk > > >> .. > > >> unless you have some other reason to bump the libc major number. > > >> > > > > >Jordan's just added new hash code..... > > > > There is no problem for new interfaces, except possibly from namespace > > pollution. > > How do we deal witht the problem of binaries that use the new interface > being run on older systems with the old library? Are we bumping the minor > number, does the linker do anything about this? We *should* be bumping the minor number. If no-one gets to it (freefall appears to be down now), I'll try and get to it. Nate From owner-freebsd-current Mon Mar 27 12:06:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA05079 for current-outgoing; Mon, 27 Mar 1995 12:06:43 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA03101 for ; Mon, 27 Mar 1995 12:03:37 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA22900; Mon, 27 Mar 1995 19:01:23 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA27024 for freebsd-current@FreeBSD.org; Mon, 27 Mar 1995 19:01:22 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id SAA15488 for freebsd-current@FreeBSD.org; Mon, 27 Mar 1995 18:56:34 +0200 From: J Wunsch Message-Id: <199503271656.SAA15488@uriah.heep.sax.de> Subject: Re: Problem with newfs. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 27 Mar 1995 18:56:33 +0200 (MET DST) In-Reply-To: <199503270605.WAA04930@corbin.Root.COM> from "David Greenman" at Mar 26, 95 10:05:44 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 567 Sender: current-owner@FreeBSD.org Precedence: bulk As David Greenman wrote: > > John thinks that it is the multi-block I/O code. Apparantly some drives say > they can do it but can't. The solution that will be implemented is a kernel > 'flags' option to enable it (disabled my default). Is this perchance also a problem for my old AHA-1540A controller? It used to work up until 2.0 (something around the 2.0-Release), but i get hangs on heavy NFS (or disk?) load now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 27 12:09:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA05175 for current-outgoing; Mon, 27 Mar 1995 12:09:46 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA05163 for ; Mon, 27 Mar 1995 12:09:42 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA02906; Mon, 27 Mar 95 10:11:47 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503271711.AA02906@cs.weber.edu> Subject: Re: shared library versioning To: bde@zeta.org.au (Bruce Evans) Date: Mon, 27 Mar 95 10:11:46 MST Cc: davidg@Root.COM, paul@isl.cf.ac.uk, bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199503271324.XAA19834@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 95 11:24:51 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > >> will be no worse than the previous behavior. I suggest we just leave it alone > >> unless you have some other reason to bump the libc major number. > >> > > >Jordan's just added new hash code..... > > There is no problem for new interfaces, except possibly from namespace > pollution. I agree about the _major_ version number not needing a change when you only add interfaces -- you only change it when you delete/alter the existing ones; however, this *must* bump the _minor_ version number! 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 Mon Mar 27 12:15:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06347 for current-outgoing; Mon, 27 Mar 1995 12:15:59 -0800 Received: from nlsys.demon.co.uk (nlsys.demon.co.uk [158.152.125.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA06340 for ; Mon, 27 Mar 1995 12:15:54 -0800 Received: (from dfr@localhost) by nlsys.demon.co.uk (8.6.10/8.6.9) id VAA05203; Mon, 27 Mar 1995 21:06:26 +0100 Date: Mon, 27 Mar 1995 21:06:26 +0100 (BST) From: Doug Rabson To: Bob Willcox cc: "Andrey A. Chernov Black Mage" , freebsd-current@freefall.cdrom.com Subject: Re: tgetnum wierdness on -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 27 Mar 1995, Bob Willcox wrote: > [snip] > > to get the new window sizes (which works). Then it does an initscr() > which calls setterm() which attempts an > > ioctl(STDERR_FILENO, TIOCGWINSZ, &win) This is bogus. It should be using the internal variable __tty_fileno which is set up when curses initialises. Unless anyone can think of a good reason that it is using stderr, I will change this. > [snip] -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891 From owner-freebsd-current Mon Mar 27 12:35:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06731 for current-outgoing; Mon, 27 Mar 1995 12:35:46 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA06724 for ; Mon, 27 Mar 1995 12:35:41 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id MAA01954; Mon, 27 Mar 1995 12:35:32 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id MAA00304; Mon, 27 Mar 1995 12:35:32 -0800 Message-Id: <199503272035.MAA00304@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de cc: smace@metal-mail.neosoft.com, mw@pandora.sax.de, current@freefall.cdrom.com Subject: Re: FreeBSD problems - VM bug? In-reply-to: Your message of "Mon, 27 Mar 95 12:42:07 +0200." <199503271042.MAA29588@bonnie.tcd-dresden.de> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 12:35:23 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >As David Greenman wrote: >| >| >I experienced the random singal 11's back then when my -current was about >| >equal to the SNAP. I no longer get those problems with the latest -current. >| >The problem seemed to hinge around -O2 optimization instead of -O. >... >| I don't think the problem is in any way related to -O2 optimization. There >| were a whole slew of VM bugs that were fixed in post-0210 SNAP that were >| causing problems. As far as I know, the entire source tree except the kernel >| is still built -O2. > >But you realized that Martin's kernel is of 950221, David? (Only his >binaries are from the 950210-SNAP.) That doesn't matter. Most of the serious bugs were fixed in the last 2 weeks. -DG From owner-freebsd-current Mon Mar 27 12:47:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07032 for current-outgoing; Mon, 27 Mar 1995 12:47:34 -0800 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 MAA07021 for ; Mon, 27 Mar 1995 12:47:25 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id WAA17537 for ; Mon, 27 Mar 1995 22:47:14 +0200 Message-Id: <199503272047.WAA17537@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: To all the ctm'mers... Date: Mon, 27 Mar 1995 22:47:09 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk Hi Is anyone else noticing this? I have done ZERO investigation. The relevant ctm's apply perfectly OK by hand afterward. This is an elk^h^h^hextract from the logfile. 1995-03-26 18:01 ports-cur.0295.gz 1/1 stored 1995-03-26 18:01 ports-cur.0295.gz complete 1995-03-26 18:01 ctm: ctm: not found 1995-03-26 18:01 ctm failed to apply ports-cur.0293.gz 1995-03-27 00:19 ports-cur.0296.gz 1/1 stored 1995-03-27 00:19 ports-cur.0296.gz complete 1995-03-27 00:19 ctm: ctm: not found 1995-03-27 00:19 ctm failed to apply ports-cur.0293.gz The appropriate mail alias looks like: ctm-port: "|/usr/sbin/ctm_rmail -l /var/log/ctmportlog -p /usr/ctm/piece -d /usr/ctm/pdone -b /usr/ports" -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Mar 27 12:54:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07143 for current-outgoing; Mon, 27 Mar 1995 12:54:15 -0800 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 MAA07137 for ; Mon, 27 Mar 1995 12:54:13 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id MAA29672; Mon, 27 Mar 1995 12:53:52 -0800 From: Poul-Henning Kamp Message-Id: <199503272053.MAA29672@ref.tfs.com> Subject: Re: To all the ctm'mers... To: mark@grondar.za (Mark Murray) Date: Mon, 27 Mar 1995 12:53:52 -0800 (PST) Cc: current@FreeBSD.org In-Reply-To: <199503272047.WAA17537@grunt.grondar.za> from "Mark Murray" at Mar 27, 95 10:47:09 pm Content-Type: text Content-Length: 955 Sender: current-owner@FreeBSD.org Precedence: bulk > Is anyone else noticing this? I have done ZERO investigation. The relevant > ctm's apply perfectly OK by hand afterward. This is an elk^h^h^hextract > from the logfile. > > 1995-03-26 18:01 ports-cur.0295.gz 1/1 stored > 1995-03-26 18:01 ports-cur.0295.gz complete > 1995-03-26 18:01 ctm: ctm: not found > 1995-03-26 18:01 ctm failed to apply ports-cur.0293.gz > 1995-03-27 00:19 ports-cur.0296.gz 1/1 stored > 1995-03-27 00:19 ports-cur.0296.gz complete > 1995-03-27 00:19 ctm: ctm: not found > 1995-03-27 00:19 ctm failed to apply ports-cur.0293.gz > > The appropriate mail alias looks like: > > ctm-port: "|/usr/sbin/ctm_rmail -l /var/log/ctmportlog -p /usr/ctm/piece -d /usr/ctm/pdone -b /usr/ports" You need to set the path to include /usr/sbin to find "ctm"... -- 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 Mar 27 13:02:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07404 for current-outgoing; Mon, 27 Mar 1995 13:02:29 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA07398 for ; Mon, 27 Mar 1995 13:02:23 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA02054; Mon, 27 Mar 1995 13:02:20 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA00352; Mon, 27 Mar 1995 13:02:20 -0800 Message-Id: <199503272102.NAA00352@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Problem with newfs. In-reply-to: Your message of "Mon, 27 Mar 95 18:56:33 +0200." <199503271656.SAA15488@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 13:02:20 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >As David Greenman wrote: >> >> John thinks that it is the multi-block I/O code. Apparantly some drives say >> they can do it but can't. The solution that will be implemented is a kernel >> 'flags' option to enable it (disabled my default). > >Is this perchance also a problem for my old AHA-1540A controller? It >used to work up until 2.0 (something around the 2.0-Release), but i >get hangs on heavy NFS (or disk?) load now. No, I'm refering only to the wd driver. -DG From owner-freebsd-current Mon Mar 27 13:37:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA09668 for current-outgoing; Mon, 27 Mar 1995 13:37:53 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA09656; Mon, 27 Mar 1995 13:37:46 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Garrett Wollman cc: Paul Richards , bde@zeta.org.au (Bruce Evans), davidg@Root.COM, current@FreeBSD.org Subject: Re: shared library versioning In-reply-to: Your message of "Mon, 27 Mar 95 11:21:09 EST." <9503271621.AA10078@halloran-eldar.lcs.mit.edu> Date: Mon, 27 Mar 1995 13:37:42 -0800 Message-ID: <9650.796340262@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > I didn't see a bump, but as a result of this change, it should be. So instead of said binaries failing catastrophically on a link error, they just fail to find the library in question and fail catastrophically on a missing library? I somehow fail to see the point. Jordan From owner-freebsd-current Mon Mar 27 13:43:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10217 for current-outgoing; Mon, 27 Mar 1995 13:43:19 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA10187; Mon, 27 Mar 1995 13:43:02 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA02243; Mon, 27 Mar 1995 13:42:54 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA00465; Mon, 27 Mar 1995 13:42:54 -0800 Message-Id: <199503272142.NAA00465@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@FreeBSD.org Subject: Re: shared library versioning In-reply-to: Your message of "Mon, 27 Mar 95 13:37:42 PST." <9650.796340262@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 13:42:53 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >> I didn't see a bump, but as a result of this change, it should be. > >So instead of said binaries failing catastrophically on a link >error, they just fail to find the library in question and fail >catastrophically on a missing library? No, ld.so looks for the highest rev library with the same major number. -DG From owner-freebsd-current Mon Mar 27 13:43:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10218 for current-outgoing; Mon, 27 Mar 1995 13:43:19 -0800 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 NAA10186; Mon, 27 Mar 1995 13:43:02 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA29986; Mon, 27 Mar 1995 13:43:01 -0800 From: Poul-Henning Kamp Message-Id: <199503272143.NAA29986@ref.tfs.com> Subject: Re: shared library versioning To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Mon, 27 Mar 1995 13:43:01 -0800 (PST) Cc: wollman@halloran-eldar.lcs.mit.edu, paul@isl.cf.ac.uk, bde@zeta.org.au, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <9650.796340262@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 27, 95 01:37:42 pm Content-Type: text Content-Length: 668 Sender: current-owner@FreeBSD.org Precedence: bulk > > I didn't see a bump, but as a result of this change, it should be. > > So instead of said binaries failing catastrophically on a link > error, they just fail to find the library in question and fail > catastrophically on a missing library? > > I somehow fail to see the point. So do I. This will make >ALL< 2.1 binaries fail on a 2.0 system, leaving the version number as it was would only have a few 2.1 binaries (as of yet nonexistent ones) fail on a 2.0 system. revert please. -- 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 Mar 27 13:47:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10641 for current-outgoing; Mon, 27 Mar 1995 13:47:27 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA10607; Mon, 27 Mar 1995 13:47:09 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id OAA03534; Mon, 27 Mar 1995 14:51:20 -0700 Date: Mon, 27 Mar 1995 14:51:20 -0700 From: Nate Williams Message-Id: <199503272151.OAA03534@trout.sri.MT.net> In-Reply-To: "Jordan K. Hubbard" "Re: shared library versioning" (Mar 27, 1:37pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Jordan K. Hubbard" , Garrett Wollman Subject: Re: shared library versioning Cc: Paul Richards , bde@zeta.org.au (Bruce Evans), davidg@Root.COM, current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > > I didn't see a bump, but as a result of this change, it should be. > > So instead of said binaries failing catastrophically on a link > error, they just fail to find the library in question and fail > catastrophically on a missing library? > > I somehow fail to see the point. If we don't bump the shlib #, any binaries that are linked against the new library will think libc.so.2.0 is adequate. Which means IF that binary is moved to a machine that contains a *real* (2.0R) libc.so.2.0 it will fail at runtime because of a missing symbol. The binaries obviously link fine since they are linked against a library that contains all of the necessary symbols. But, libc.so.2.0 to the rest of the world (especially consider the change I made earlier) do not contain the strhash() routines. Programs linked against libc.so.2.0 will run with libc.so.2.1 since the run-time loader will use any minor library >= the original version, but not a minor number less than it was linked against. Clear as mud? Nate From owner-freebsd-current Mon Mar 27 13:47:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10673 for current-outgoing; Mon, 27 Mar 1995 13:47:42 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA10544 for ; Mon, 27 Mar 1995 13:46:24 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA27909; Mon, 27 Mar 1995 23:44:00 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id XAA29300 for freebsd-current@FreeBSD.org; Mon, 27 Mar 1995 23:43:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id XAA21180 for freebsd-current@FreeBSD.org; Mon, 27 Mar 1995 23:37:19 +0200 From: J Wunsch Message-Id: <199503272137.XAA21180@uriah.heep.sax.de> Subject: pcemu port To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 27 Mar 1995 23:37:19 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 651 Sender: current-owner@FreeBSD.org Precedence: bulk I've just been commiting a port of David Hedley's ``pcemu'' 8086 PC emulator. I've done the best i can to give people a reasonable starting point, including a small bootstrapper that can be booted from instead of the DOS floppy image that's normally required. I need some feedback to see if i got everything right. Q: Do i have to set some EXEC_DEPENDS in the Makefile for a port that requires several things from the X11 package to build? (bdftopcf and mkfontdir are being used during `make install'.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 27 13:50:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10802 for current-outgoing; Mon, 27 Mar 1995 13:50:22 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA10789; Mon, 27 Mar 1995 13:50:13 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id OAA03571; Mon, 27 Mar 1995 14:54:19 -0700 Date: Mon, 27 Mar 1995 14:54:19 -0700 From: Nate Williams Message-Id: <199503272154.OAA03571@trout.sri.MT.net> In-Reply-To: Poul-Henning Kamp "Re: shared library versioning" (Mar 27, 1:43pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Poul-Henning Kamp , jkh@freefall.cdrom.com (Jordan K. Hubbard) Subject: Re: shared library versioning Cc: davidg@Root.COM, current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > > > I didn't see a bump, but as a result of this change, it should be. > > > > So instead of said binaries failing catastrophically on a link > > error, they just fail to find the library in question and fail > > catastrophically on a missing library? > > > > I somehow fail to see the point. > > So do I. > This will make >ALL< 2.1 binaries fail on a 2.0 system, leaving the > version number as it was would only have a few 2.1 binaries (as of yet > nonexistent ones) fail on a 2.0 system. And rightly so. If we want to use shlibs, you need to pay the price of compatability. Having *most* of the binaries work is not acceptable when all the binaries will work is simple and only wastes space. If folks want to run 2.1 binaries on their 2.1 machines, then they need the 2.1 libraries as well. They go hand in hand. (Assuming the ld changes don't bite them). If they want, they can delete the 2.0 libraries as so far all of them are un-necessary and can be replaced by the 2.1 versions. You can't have it both ways. Nate From owner-freebsd-current Mon Mar 27 13:51:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10853 for current-outgoing; Mon, 27 Mar 1995 13:51:55 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA10844 for ; Mon, 27 Mar 1995 13:51:37 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id OAA03596; Mon, 27 Mar 1995 14:55:45 -0700 Date: Mon, 27 Mar 1995 14:55:45 -0700 From: Nate Williams Message-Id: <199503272155.OAA03596@trout.sri.MT.net> In-Reply-To: Poul-Henning Kamp "Re: shared library versioning" (Mar 27, 1:47pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Poul-Henning Kamp Subject: Re: shared library versioning Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > > >> I didn't see a bump, but as a result of this change, it should be. > > > > > >So instead of said binaries failing catastrophically on a link > > >error, they just fail to find the library in question and fail > > >catastrophically on a missing library? > > > > No, ld.so looks for the highest rev library with the same major number. > > "higher than or equal to" what they are linked against that is... > > see my other msg. See my other mesg. :-) Nate From owner-freebsd-current Mon Mar 27 13:53:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10887 for current-outgoing; Mon, 27 Mar 1995 13:53:12 -0800 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 NAA10880; Mon, 27 Mar 1995 13:52:57 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA00192; Mon, 27 Mar 1995 13:52:49 -0800 From: Poul-Henning Kamp Message-Id: <199503272152.NAA00192@ref.tfs.com> Subject: Re: shared library versioning To: nate@trout.sri.MT.net (Nate Williams) Date: Mon, 27 Mar 1995 13:52:48 -0800 (PST) Cc: jkh@freefall.cdrom.com, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <199503272154.OAA03571@trout.sri.MT.net> from "Nate Williams" at Mar 27, 95 02:54:19 pm Content-Type: text Content-Length: 1526 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > I didn't see a bump, but as a result of this change, it should be. > > > > > > So instead of said binaries failing catastrophically on a link > > > error, they just fail to find the library in question and fail > > > catastrophically on a missing library? > > > > > > I somehow fail to see the point. > > > > So do I. > > This will make >ALL< 2.1 binaries fail on a 2.0 system, leaving the > > version number as it was would only have a few 2.1 binaries (as of yet > > nonexistent ones) fail on a 2.0 system. > > And rightly so. If we want to use shlibs, you need to pay the price of > compatability. Having *most* of the binaries work is not acceptable when > all the binaries will work is simple and only wastes space. > > If folks want to run 2.1 binaries on their 2.1 machines, then they need > the 2.1 libraries as well. They go hand in hand. (Assuming the ld > changes don't bite them). If they want, they can delete the 2.0 > libraries as so far all of them are un-necessary and can be replaced by > the 2.1 versions. > > You can't have it both ways. No I can't. But until somebody actually uses that particular symbol for something, then I don't really want to see 2.1 being >that< incompatible. Alternatively we shoule decide that this is the way it will be, and bump the number at any and all release hereafter. -- 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 Mar 27 14:05:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA11161 for current-outgoing; Mon, 27 Mar 1995 14:05:53 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA11151 for ; Mon, 27 Mar 1995 14:05:43 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id PAA03636; Mon, 27 Mar 1995 15:09:51 -0700 Date: Mon, 27 Mar 1995 15:09:51 -0700 From: Nate Williams Message-Id: <199503272209.PAA03636@trout.sri.MT.net> In-Reply-To: Poul-Henning Kamp "Re: shared library versioning" (Mar 27, 1:52pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Poul-Henning Kamp Subject: Re: shared library versioning Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk [ adding strhash() functions to libc and shared lib bumping ] > > If folks want to run 2.1 binaries on their 2.1 machines, then they need > > the 2.1 libraries as well. They go hand in hand. (Assuming the ld > > changes don't bite them). If they want, they can delete the 2.0 > > libraries as so far all of them are un-necessary and can be replaced by > > the 2.1 versions. > > > > You can't have it both ways. > > No I can't. But until somebody actually uses that particular symbol for > something, then I don't really want to see 2.1 being >that< incompatible. If that symbol is not needed, then it can be removed from the library and the shared library doesn't need to be bumped. But, I assumed they were added because they were going to be used, so there are going to be program(s) using them. I guess I assumed it would be silly for Jordan to add something to libc that he wasn't planning on using. And, it's not that incompatible. That why shared libraries are the way they are. Everything is 'updwards' compatible, but nothing is guaranteed to be downwards compatible. > Alternatively we shoule decide that this is the way it will be, and bump > the number at any and all release hereafter. Why? If the libraries don't change, then why bump the number? The point of shared number versions is to allow you to change the number IFF it needs to change, and not when it doesn't need to. The numbering scheme goes as follows.: 1) Major numbers == same interface and calling convention. If you modify a function's parameters & type, then the major # needs to be bumped. There is no way a program who thinks msync() needs 3 parameters is going to work against a library that uses 2. We've ignored that change in FreeBSD since according to David and Ache, msync() never worked anyway so a program using it was broken before the interface changed. 2) Minor #'S. If the same routines exist as have always existed, but we are adding new functionality then bump the minor # so we can differentiate between a shlib containing ONLY the old routines and a shlib containing the OLD + NEW routines. Else, we will get run-time errors when new programs which expect the new routines are run in system which contain only the old shlib. Your response to bump the minor # only when programs are added to the system is irrelevant which use the new functionality because of the implicit assumption that the functionality was added because it was going to be used. Therefore, we must bump the minor # when the library changes since that is what changed, not the programs. Nate From owner-freebsd-current Mon Mar 27 14:18:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA11706 for current-outgoing; Mon, 27 Mar 1995 14:18:49 -0800 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 OAA11699 for ; Mon, 27 Mar 1995 14:18:43 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA11072; Mon, 27 Mar 1995 17:18:36 -0500 Date: Mon, 27 Mar 1995 17:18:36 -0500 From: Garrett Wollman Message-Id: <9503272218.AA11072@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.org Subject: Re: shared library versioning In-Reply-To: <199503272152.NAA00192@ref.tfs.com> References: <199503272154.OAA03571@trout.sri.MT.net> <199503272152.NAA00192@ref.tfs.com> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > No I can't. But until somebody actually uses that particular symbol for > something, then I don't really want to see 2.1 being >that< incompatible. > Alternatively we shoule decide that this is the way it will be, and bump > the number at any and all release hereafter. No, I don't think so. Only libraries whose interface has changed should be bumped, and said bumping should occur at most once during the release cycle. -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 Mon Mar 27 14:26:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA11870 for current-outgoing; Mon, 27 Mar 1995 14:26:15 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA11864 for ; Mon, 27 Mar 1995 14:26:03 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id PAA03724; Mon, 27 Mar 1995 15:30:12 -0700 Date: Mon, 27 Mar 1995 15:30:12 -0700 From: Nate Williams Message-Id: <199503272230.PAA03724@trout.sri.MT.net> In-Reply-To: Garrett Wollman "Re: shared library versioning" (Mar 27, 5:18pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Garrett Wollman Subject: Re: shared library versioning Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > < said: > > > No I can't. But until somebody actually uses that particular symbol for > > something, then I don't really want to see 2.1 being >that< incompatible. > > > Alternatively we shoule decide that this is the way it will be, and bump > > the number at any and all release hereafter. > > No, I don't think so. Only libraries whose interface has changed > should be bumped, and said bumping should occur at most once during > the release cycle. Just in case it wasn't obvious, I'm in complete agreement with Garrett here. I don't think the library should be bumped again in this release, but it needed to be done for reasons already explained, and now was as good a time as any to do it. Nate From owner-freebsd-current Mon Mar 27 15:11:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA13203 for current-outgoing; Mon, 27 Mar 1995 15:11:58 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA13149 for ; Mon, 27 Mar 1995 15:11:45 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA27914; Mon, 27 Mar 1995 23:44:01 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id XAA29303; Mon, 27 Mar 1995 23:44:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id XAA21208; Mon, 27 Mar 1995 23:40:02 +0200 From: J Wunsch Message-Id: <199503272140.XAA21208@uriah.heep.sax.de> Subject: Re: FreeBSD problems - VM bug? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 27 Mar 1995 23:40:01 +0200 (MET DST) Cc: mw@pandora.sax.de (Martin Welk) In-Reply-To: <199503272035.MAA00304@corbin.Root.COM> from "David Greenman" at Mar 27, 95 12:35:23 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 409 Sender: current-owner@FreeBSD.org Precedence: bulk As David Greenman wrote: > > >But you realized that Martin's kernel is of 950221, David? (Only his > >binaries are from the 950210-SNAP.) > > That doesn't matter. Most of the serious bugs were fixed in the last 2 > weeks. Oooops. Sorry, i meant 95*03*21. ! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Mar 27 16:56:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA15733 for current-outgoing; Mon, 27 Mar 1995 16:56:40 -0800 Received: from obiwan.pmr.com ([199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA15727 for ; Mon, 27 Mar 1995 16:56:38 -0800 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0rtPZt-00030qC; Mon, 27 Mar 95 18:56 CST Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: tgetnum wierdness on -current To: dfr@nlsys.demon.co.uk (Doug Rabson) Date: Mon, 27 Mar 1995 18:56:12 -0600 (CST) Cc: ache@astral.msk.su, freebsd-current@freefall.cdrom.com In-Reply-To: from "Doug Rabson" at Mar 27, 95 09:06:26 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 823 Sender: current-owner@FreeBSD.org Precedence: bulk Doug Rabson wrote: > > On Mon, 27 Mar 1995, Bob Willcox wrote: > > > [snip] > > > > to get the new window sizes (which works). Then it does an initscr() > > which calls setterm() which attempts an > > > > ioctl(STDERR_FILENO, TIOCGWINSZ, &win) > > This is bogus. It should be using the internal variable __tty_fileno > which is set up when curses initialises. Unless anyone can think of a > good reason that it is using stderr, I will change this. Changing the ioctl in setterm() to use __tty_fileno did, indeed, fix the problem with resizing windows in files. Thanks. -- Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob Austin, TX or: @uudell.us.dell.com:obiwan!bob 512-258-4224 (home), 512-838-3914 (work) or: obiwan%bob@uunet.uu.net From owner-freebsd-current Mon Mar 27 19:50:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA19864 for current-outgoing; Mon, 27 Mar 1995 19:50:26 -0800 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA19857; Mon, 27 Mar 1995 19:50:22 -0800 Received: from ast.com by relay2.UU.NET with SMTP id QQyiyp06787; Mon, 27 Mar 1995 22:50:16 -0500 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA27459 (5.67b/IDA-1.5 for uunet!freebsd.org!hackers); Mon, 27 Mar 1995 19:54:14 -0800 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Mon, 27 Mar 95 21:48 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0rtRW8-0004vvC; Mon, 27 Mar 95 21:00 CST Message-Id: Date: Mon, 27 Mar 95 21:00 CST To: current@FreeBSD.org, hackers@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Reply-To: uhclem%nemesis@fw.ast.com Sent: Mon Mar 27 1995, 21:00:27 CST Subject: Are you using the matcd driver? Cc: uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk If you are using the matcd driver for Panasonic/Creative/Matsushita CD-ROM drives, please answer these questions by mail ASAP: 1. What model host interface are you using? Please send the name and the model number if you know it. (If it is a SoundBlaster card, look on the upper left part of the card for the model number, something like "CTnnnn".) 2. What are the brands and model numbers of the CD-ROM drives you are using with the matcd driver? (The model number should be displayed when the system boots.) Naturally if you are encountering any problems, include that. I already know that xcdplayer and other audio disc players aren't working on the version in -current or in the 0322 SNAP. A new version will be available shortly that has the missing functions plus some bizzare features. Thanks again for the information. It will be added to the list of known-working hardware configurations in the man page. Send your information to: uhclem%nemesis@fw.ast.com (two "e"s in nemesis) Frank Durda IV |Baldrick: But Mr. G, I've got a or uhclem%nemesis@trsvax.ast.com (Internet)|cunning plan. Just add "95" to ...letni!rwsys!nemesis!uhclem |the end of your product name and ...decvax!trsvax.fw.ast.com!nemesis!uhclem |people will think its better. :-) BillG: That's the worst plan ever, but its the only one we've got. I might use it as the price too." From owner-freebsd-current Mon Mar 27 20:31:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA22616 for current-outgoing; Mon, 27 Mar 1995 20:31:10 -0800 Received: from easynet.com (easyr.easynet.net [198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA22606 for ; Mon, 27 Mar 1995 20:31:03 -0800 Received: by easynet.com (Smail3.1.28.1 #7) id m0rtSlh-000rcdC; Mon, 27 Mar 95 20:20 WET Message-Id: From: brian@mediacity.com (Brian Litzinger) Subject: hylafax doesn't with work with shared libraries To: freebsd-current@FreeBSD.org Date: Mon, 27 Mar 1995 20:20:36 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 405 Sender: current-owner@FreeBSD.org Precedence: bulk I compiled hylafax beta 111 (flexfax) with -current (032695) and the faxstat command reports something like invalid response 'ld.so ....' from server. Recompiled everything with -static, and it works fine. hylafax beta 110 worked fine without -static about 1 week ago. Then I was running SNAP-021095 with -current kernel. Now I'm running SNAP-032295 with -current. Brian Litzinger brian@easynet.com From owner-freebsd-current Mon Mar 27 21:01:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA24577 for current-outgoing; Mon, 27 Mar 1995 21:01:56 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA24568 for ; Mon, 27 Mar 1995 21:01:50 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id WAA04596; Mon, 27 Mar 1995 22:05:59 -0700 Date: Mon, 27 Mar 1995 22:05:59 -0700 Message-Id: <199503280505.WAA04596@trout.sri.MT.net> To: brian@mediacity.com (Brian Litzinger) Cc: freebsd-current@FreeBSD.org Subject: Re: hylafax doesn't with work with shared libraries In-Reply-To: References: Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk Brian Litzinger writes: > I compiled hylafax beta 111 (flexfax) with -current (032695) and the faxstat > command reports something like invalid response 'ld.so ....' from > server. That generally happens when one of the programs is compiled with the wrong load flags. This happened in the early days of the shared libs when we changed our default a.out format, but it shouldn't do anything now. Are you sure there isn't some special ld flags that were added? Try doing a file on the resulting executables to see if they show up as FreeBSD executables. Nate From owner-freebsd-current Mon Mar 27 21:05:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA24690 for current-outgoing; Mon, 27 Mar 1995 21:05:33 -0800 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA24666; Mon, 27 Mar 1995 21:05:18 -0800 Received: from ast.com by relay2.UU.NET with SMTP id QQyiyu04490; Tue, 28 Mar 1995 00:05:13 -0500 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA27696 (5.67b/IDA-1.5 for uunet!freebsd.org!freebsd-current); Mon, 27 Mar 1995 21:09:12 -0800 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Mon, 27 Mar 95 23:04 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0rtTLY-0004vrC; Mon, 27 Mar 95 22:57 CST Message-Id: Date: Mon, 27 Mar 95 22:57 CST To: freebsd-bugs@FreeBSD.org, freebsd-current@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Mon Mar 27 1995, 22:57:40 CST Subject: No declaration for bounds_check_with_label Cc: uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk Could we locate a nice include file and include: extern int bounds_check_with_label(struct buf *bp, struct disklabel *lp, int wlabel); Several different drivers have to references this and it has no declaration. The function is in machdep.c. Perhaps in devconf.h? Frank Durda IV |"When Windows runs low on memory, or uhclem%nemesis@trsvax.ast.com (Internet)| it gets very unstable." ...letni!rwsys!nemesis!uhclem | - Unnamed Microsoft Windows ...decvax!trsvax.fw.ast.com!nemesis!uhclem | designer, 1992 Really! From owner-freebsd-current Mon Mar 27 21:12:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA24939 for current-outgoing; Mon, 27 Mar 1995 21:12:11 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA24923; Mon, 27 Mar 1995 21:11:55 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id VAA03007; Mon, 27 Mar 1995 21:11:50 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id VAA00602; Mon, 27 Mar 1995 21:11:50 -0800 Message-Id: <199503280511.VAA00602@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: uhclem@nemesis.lonestar.org (Frank Durda IV) cc: freebsd-bugs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: No declaration for bounds_check_with_label In-reply-to: Your message of "Mon, 27 Mar 95 22:57:00 CST." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 21:11:49 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >Could we locate a nice include file and include: > >extern int bounds_check_with_label(struct buf *bp, struct disklabel *lp, > int wlabel); > >Several different drivers have to references this and it has no >declaration. The function is in machdep.c. It's declaration is in sys/disklabel.h. -DG From owner-freebsd-current Mon Mar 27 21:54:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA26021 for current-outgoing; Mon, 27 Mar 1995 21:54:24 -0800 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 VAA26013 for ; Mon, 27 Mar 1995 21:54:18 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id HAA22355; Tue, 28 Mar 1995 07:53:52 +0200 Message-Id: <199503280553.HAA22355@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: Poul-Henning Kamp cc: current@FreeBSD.org Subject: Re: To all the ctm'mers... Date: Tue, 28 Mar 1995 07:53:52 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > > ctm-port: "|/usr/sbin/ctm_rmail -l /var/log/ctmportlog -p /usr/ctm/piece -d /usr/ctm/pdone -b /usr/ports" > > You need to set the path to include /usr/sbin to find "ctm"... Sure. But _where_? Where does sendmail get a path from? Thanks! M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Mar 27 22:06:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA27300 for current-outgoing; Mon, 27 Mar 1995 22:06:20 -0800 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 WAA27294 for ; Mon, 27 Mar 1995 22:06:19 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id WAA02430; Mon, 27 Mar 1995 22:05:56 -0800 From: Poul-Henning Kamp Message-Id: <199503280605.WAA02430@ref.tfs.com> Subject: Re: To all the ctm'mers... To: mark@grondar.za (Mark Murray) Date: Mon, 27 Mar 1995 22:05:55 -0800 (PST) Cc: current@FreeBSD.org In-Reply-To: <199503280553.HAA22355@grunt.grondar.za> from "Mark Murray" at Mar 28, 95 07:53:52 am Content-Type: text Content-Length: 679 Sender: current-owner@FreeBSD.org Precedence: bulk > > > ctm-port: "|/usr/sbin/ctm_rmail -l /var/log/ctmportlog -p /usr/ctm/piece -d > /usr/ctm/pdone -b /usr/ports" > > > > You need to set the path to include /usr/sbin to find "ctm"... > > Sure. But _where_? Where does sendmail get a path from? I use this: ctm-cvs-cur: "| PATH=$PATH:/usr/sbin /usr/sbin/ctm_rmail -l /archive/CTM_mail /log -p /archive/CTM_mail -d /archive/CTM -b /home/ncvs" and it works, but is gross... I belive ctm_rmail should use an absolute path to the ctm program. -- 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 Mar 27 22:10:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA27367 for current-outgoing; Mon, 27 Mar 1995 22:10:17 -0800 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 WAA27356 for ; Mon, 27 Mar 1995 22:10:00 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id IAA22705; Tue, 28 Mar 1995 08:09:38 +0200 Message-Id: <199503280609.IAA22705@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: Poul-Henning Kamp cc: mark@grondar.za (Mark Murray), current@FreeBSD.org Subject: Re: To all the ctm'mers... Date: Tue, 28 Mar 1995 08:09:37 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > > Sure. But _where_? Where does sendmail get a path from? > > I use this: > ctm-cvs-cur: "| PATH=$PATH:/usr/sbin /usr/sbin/ctm_rmail -l /archive/CTM_m ail > /log -p /archive/CTM_mail -d /archive/CTM -b /home/ncvs" > > and it works, but is gross... > > I belive ctm_rmail should use an absolute path to the ctm program. How about assuming that ctm is in the same directory as ctm_rmail? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Mon Mar 27 23:19:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA29735 for current-outgoing; Mon, 27 Mar 1995 23:19:31 -0800 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 XAA29726; Mon, 27 Mar 1995 23:19:14 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA13866; Tue, 28 Mar 1995 17:14:53 +1000 Date: Tue, 28 Mar 1995 17:14:53 +1000 From: Bruce Evans Message-Id: <199503280714.RAA13866@godzilla.zeta.org.au> To: freebsd-bugs@FreeBSD.org, freebsd-current@FreeBSD.org, uhclem@nemesis.lonestar.org Subject: Re: No declaration for bounds_check_with_label Sender: current-owner@FreeBSD.org Precedence: bulk >Could we locate a nice include file and include: >extern int bounds_check_with_label(struct buf *bp, struct disklabel *lp, > int wlabel); >Several different drivers have to references this and it has no >declaration. The function is in machdep.c. It is declared in (since revision 1.11 1995/03/16), but will go away. Please update your driver(s) to use disk slices (dscheck()) so that bounds_check_with_label() can go away ASAP. See recent changes to sd.c. for examples. Unsliced unlabeled read-only disks are simpler to handle. dsopen() will eventually have a `struct diskgeom' arg (the struct will be something like `struct disk_parms' in sd.c) so that a dummy label doesn't have to be created in 1001 different cdrom drivers. The disk slice module also handles all for the DIOC* ioctls so that drivers don't have to and correctly tracks open partitions. Most scsi and cd drivers incorrectly track open partitions. Some of them incorrectly declare their close function so they don't even know about the `fmt' arg which is required for distinguishing closes of the cdev from closes of the bdev. Bruce From owner-freebsd-current Mon Mar 27 23:38:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA00530 for current-outgoing; Mon, 27 Mar 1995 23:38:13 -0800 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 XAA00516 for ; Mon, 27 Mar 1995 23:38:04 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA05817; Tue, 28 Mar 95 09:37:55 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id JAA02693; Tue, 28 Mar 1995 09:43:38 +0200 Message-Id: <199503280743.JAA02693@gilberto.physik.rwth-aachen.de> Subject: Re: FreeBSD problems - VM bug? To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 28 Mar 1995 09:43:37 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com (user alias) In-Reply-To: <199503272140.XAA21208@uriah.heep.sax.de> from "J Wunsch" at Mar 27, 95 11:40:01 pm From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 978 Sender: current-owner@FreeBSD.org Precedence: bulk > > As David Greenman wrote: > > > > >But you realized that Martin's kernel is of 950221, David? (Only his > > >binaries are from the 950210-SNAP.) I wouldn't trust that mix. I had all sorts of trouble when mixing a 950210 with later kernels. 950210-SNAP hadn't been very trustable. Did Martin upgrade to -current or do a full install from 950321-SNAP? Do the VM problems persist? I have a 386SX-16 8MB, IDE, (Morse board) and I'm running some 95 SNAP on it w/o problems. > > > > That doesn't matter. Most of the serious bugs were fixed in the last 2 > > weeks. > > Oooops. Sorry, i meant 95*03*21. ! > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ > Never trust an operating system you don't have sources for. ;-) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Tue Mar 28 02:27:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA06416 for current-outgoing; Tue, 28 Mar 1995 02:27:33 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA06408 for ; Tue, 28 Mar 1995 02:27:20 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id LAA17860; Tue, 28 Mar 1995 11:27:22 +0100 From: Paul Richards Message-Id: <199503281027.LAA17860@isl.cf.ac.uk> Subject: Re: shared library versioning To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Tue, 28 Mar 1995 11:27:21 +0100 (BST) Cc: phk@ref.tfs.com, current@FreeBSD.org In-Reply-To: <9503272218.AA11072@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Mar 27, 95 05:18:36 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 739 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Garrett Wollman who said > > No, I don't think so. Only libraries whose interface has changed > should be bumped, and said bumping should occur at most once during > the release cycle. Yeah, I agree with this. During the release cycle we can handle any library problems ourselves by recompiling what we need to. We maybe should have some mechanism for tracking this so that we know when changing the libraries that someone has already bumped the numbers since the last release. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Tue Mar 28 02:44:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA07113 for current-outgoing; Tue, 28 Mar 1995 02:44:52 -0800 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 CAA07103 for ; Tue, 28 Mar 1995 02:44:35 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA19653; Tue, 28 Mar 1995 20:38:35 +1000 Date: Tue, 28 Mar 1995 20:38:35 +1000 From: Bruce Evans Message-Id: <199503281038.UAA19653@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@halloran-eldar.lcs.mit.edu Subject: Re: shared library versioning Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>> I didn't see a bump, but as a result of this change, it should be. >> Why just for this change? I don't want the version number bumped, I >> want more care taken to avoid having to bump it for unimportant >> changes. >Because when a new function is added to a library, the minor version >number needs to be incremented, so that users don't get confused. I asked why just for this change. New globals in the application's namespace have been introduced in the following libraries since 2.0R: libc: only the strhash globals. libdialog: many new globals. libforms: many new globals. Many interface changes. libg++: some regexp globals removed. libgcc: many globals removed, but we've already fixed the problems. libncurses: many new globals. Some removed. Some renamed. libreadline: many new globals. One removed. libtermcap: one new global. The strhash module should be moved to some more volatile library so that the version number of libc can be left alone. The minor or major version number of the others should be bumped for 2.1. Bruce From owner-freebsd-current Tue Mar 28 02:55:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA07464 for current-outgoing; Tue, 28 Mar 1995 02:55:39 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA07450 for ; Tue, 28 Mar 1995 02:55:29 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id LAA18030; Tue, 28 Mar 1995 11:55:04 +0100 From: Paul Richards Message-Id: <199503281055.LAA18030@isl.cf.ac.uk> Subject: Re: shared library versioning To: bde@zeta.org.au (Bruce Evans) Date: Tue, 28 Mar 1995 11:55:03 +0100 (BST) Cc: bde@zeta.org.au, wollman@halloran-eldar.lcs.mit.edu, current@FreeBSD.org In-Reply-To: <199503281038.UAA19653@godzilla.zeta.org.au> from "Bruce Evans" at Mar 28, 95 08:38:35 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1706 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Bruce Evans who said > >Because when a new function is added to a library, the minor version > >number needs to be incremented, so that users don't get confused. > > I asked why just for this change. New globals in the application's > namespace have been introduced in the following libraries since 2.0R: Because we've just realised it needs doing :-) > > libc: only the strhash globals. > libdialog: many new globals. > libforms: many new globals. Many interface changes. > libg++: some regexp globals removed. > libgcc: many globals removed, but we've already fixed the problems. > libncurses: many new globals. Some removed. Some renamed. > libreadline: many new globals. One removed. > libtermcap: one new global. > We'll have to go and fix all these soon. > The strhash module should be moved to some more volatile library so > that the version number of libc can be left alone. The minor or major > version number of the others should be bumped for 2.1. I'm not so sure adding strhash to libc was such a good idea, it was a bit of a rushed decision on mine and Jordan's part. My main reason, apart from Bruce's points, is that it's not an expected component of libc and we've therefore made anything that uses strhash very non-portable. We should pull strhash out into a separate library which we can take with us to other platforms if we ever need to. There are probably other components of libc that we could do the same for. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Tue Mar 28 03:04:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA07800 for current-outgoing; Tue, 28 Mar 1995 03:04:52 -0800 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 DAA07791; Tue, 28 Mar 1995 03:04:31 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA20354; Tue, 28 Mar 1995 21:02:24 +1000 Date: Tue, 28 Mar 1995 21:02:24 +1000 From: Bruce Evans Message-Id: <199503281102.VAA20354@godzilla.zeta.org.au> To: jkh@freefall.cdrom.com, phk@ref.tfs.com Subject: Re: shared library versioning Cc: bde@zeta.org.au, current@FreeBSD.org, davidg@Root.COM, paul@isl.cf.ac.uk, wollman@halloran-eldar.lcs.mit.edu Sender: current-owner@FreeBSD.org Precedence: bulk >> > I didn't see a bump, but as a result of this change, it should be. >> >> So instead of said binaries failing catastrophically on a link >> error, they just fail to find the library in question and fail >> catastrophically on a missing library? >> >> I somehow fail to see the point. >So do I. The point is that it fails cleaner if the library is missing. I just tested this. I removed strhash.o from libc.so and tried running a version of dmenu that was linked while strhash.o was in libc. dmenu runs OK in the empty directory /tmp. but in the dmenu directory it runs long enough to mess up the tty mode and then exits when it tries to call an nonexistent function. >This will make >ALL< 2.1 binaries fail on a 2.0 system, leaving the >version number as it was would only have a few 2.1 binaries (as of yet >nonexistent ones) fail on a 2.0 system. The ones that call the libraries that I listed in previous mail (mostly curses-based apps) have to fail, but there's no need to have the ones that are only linked to libc fail. >revert please. I agree. Put strhash.o in libjkh or somewhere. Bruce From owner-freebsd-current Tue Mar 28 04:08:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA10763 for current-outgoing; Tue, 28 Mar 1995 04:08:48 -0800 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 EAA10756 for ; Tue, 28 Mar 1995 04:08:34 -0800 Received: by sequent.kiae.su id AA07938 (5.65.kiae-2 ); Tue, 28 Mar 1995 14:58:33 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 28 Mar 95 14:58:32 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id QAA04927; Tue, 28 Mar 1995 16:00:10 +0400 To: Bruce Evans , jkh@freefall.cdrom.com, phk@ref.tfs.com Cc: current@FreeBSD.org, davidg@Root.COM, paul@isl.cf.ac.uk, wollman@halloran-eldar.lcs.mit.edu References: <199503281102.VAA20354@godzilla.zeta.org.au> In-Reply-To: <199503281102.VAA20354@godzilla.zeta.org.au>; from Bruce Evans at Tue, 28 Mar 1995 21:02:24 +1000 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 28 Mar 1995 16:00:10 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: shared library versioning Lines: 14 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 474 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199503281102.VAA20354@godzilla.zeta.org.au> Bruce Evans writes: >>revert please. >I agree. Put strhash.o in libjkh or somewhere. I agree too. Maybe libinstall? -- 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 Tue Mar 28 08:12:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19873 for current-outgoing; Tue, 28 Mar 1995 08:12:06 -0800 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 IAA19867 for ; Tue, 28 Mar 1995 08:12:04 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA12354; Tue, 28 Mar 1995 11:11:07 -0500 Date: Tue, 28 Mar 1995 11:11:07 -0500 From: Garrett Wollman Message-Id: <9503281611.AA12354@halloran-eldar.lcs.mit.edu> To: Paul Richards Cc: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman), phk@ref.tfs.com, current@FreeBSD.org Subject: Re: shared library versioning In-Reply-To: <199503281027.LAA17860@isl.cf.ac.uk> References: <9503272218.AA11072@halloran-eldar.lcs.mit.edu> <199503281027.LAA17860@isl.cf.ac.uk> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > Yeah, I agree with this. During the release cycle we can handle any > library problems ourselves by recompiling what we need to. > We maybe should have some mechanism for tracking this so that we know when > changing the libraries that someone has already bumped the numbers since the > last release. Well, all that's really needed is a file (I propose /usr/share/misc/shlib-numbers) which lists the shared-libraries and minor numbers used in each release. I will do this today if somebody doesn't beat me to it. -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 Mar 28 08:19:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19954 for current-outgoing; Tue, 28 Mar 1995 08:19:48 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA19948 for ; Tue, 28 Mar 1995 08:19:13 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id RAA14861; Tue, 28 Mar 1995 17:18:45 +0100 From: Paul Richards Message-Id: <199503281618.RAA14861@isl.cf.ac.uk> Subject: Re: shared library versioning To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Tue, 28 Mar 1995 17:18:44 +0100 (BST) Cc: wollman@halloran-eldar.lcs.mit.edu, phk@ref.tfs.com, current@FreeBSD.org In-Reply-To: <9503281611.AA12354@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Mar 28, 95 11:11:07 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1257 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Garrett Wollman who said > > < said: > > > Yeah, I agree with this. During the release cycle we can handle any > > library problems ourselves by recompiling what we need to. > > > We maybe should have some mechanism for tracking this so that we know when > > changing the libraries that someone has already bumped the numbers since the > > last release. > > Well, all that's really needed is a file (I propose > /usr/share/misc/shlib-numbers) which lists the shared-libraries and > minor numbers used in each release. I will do this today if somebody > doesn't beat me to it. I'm not sure I like that idea, since people will forget to either check the file or keep it up to date. I'd prefer some comment in the Makefile that flags that the library beens bumped and then have a script which runs through the tree removing these comments as part of the release process so they're clean at the start of the next release. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Tue Mar 28 08:22:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19999 for current-outgoing; Tue, 28 Mar 1995 08:22:45 -0800 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 IAA19993 for ; Tue, 28 Mar 1995 08:22:44 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA12372; Tue, 28 Mar 1995 11:22:27 -0500 Date: Tue, 28 Mar 1995 11:22:27 -0500 From: Garrett Wollman Message-Id: <9503281622.AA12372@halloran-eldar.lcs.mit.edu> To: Paul Richards Cc: current@FreeBSD.org Subject: Re: shared library versioning In-Reply-To: <199503281618.RAA14861@isl.cf.ac.uk> References: <9503281611.AA12354@halloran-eldar.lcs.mit.edu> <199503281618.RAA14861@isl.cf.ac.uk> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > I'd prefer some comment in the Makefile that flags that the library beens > bumped and then have a script which runs through the tree removing these > comments as part of the release process so they're clean at the start of the > next release. This doesn't help users when the question is ``I just got a program that requires the `bletch' library version 69.17. What release is that from?'' -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 Mar 28 10:00:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22660 for current-outgoing; Tue, 28 Mar 1995 10:00:03 -0800 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 JAA22645 for ; Tue, 28 Mar 1995 09:59:56 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id TAA01578 for ; Tue, 28 Mar 1995 19:59:40 +0200 Message-Id: <199503281759.TAA01578@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: Patch for systat... Date: Tue, 28 Mar 1995 19:59:39 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk Hi I got irritated with not seeing the interrupt numbers in a (crowded) "systat -vmstat" display, so I fixed it. Here is a patch to please be applied in src/usr.bin/systat ----------------------------8<------------------------------------ *** vmstat.c#ctm# Sat Mar 25 14:46:00 1995 --- vmstat.c Tue Mar 28 19:48:44 1995 *************** *** 170,176 **** #define PAGEROW 2 /* uses 4 rows and 26 cols */ #define PAGECOL 36 #define INTSROW 2 /* uses all rows to bottom and 17 cols */ ! #define INTSCOL 63 #define PROCSROW 7 /* uses 2 rows and 20 cols */ #define PROCSCOL 0 #define GENSTATROW 7 /* uses 2 rows and 30 cols */ --- 170,176 ---- #define PAGEROW 2 /* uses 4 rows and 26 cols */ #define PAGECOL 36 #define INTSROW 2 /* uses all rows to bottom and 17 cols */ ! #define INTSCOL 61 #define PROCSROW 7 /* uses 2 rows and 20 cols */ #define PROCSCOL 0 #define GENSTATROW 7 /* uses 2 rows and 30 cols */ *************** *** 333,339 **** for (i = 0; i < nintr; i++) { if (intrloc[i] == 0) continue; ! mvprintw(intrloc[i], INTSCOL + 9, "%-8.8s", intrname[i]); } } --- 333,339 ---- for (i = 0; i < nintr; i++) { if (intrloc[i] == 0) continue; ! mvprintw(intrloc[i], INTSCOL + 9, "%-10.10s", intrname[i]); } } *************** *** 389,403 **** if (nextintsrow == LINES) continue; intrloc[i] = nextintsrow++; ! mvprintw(intrloc[i], INTSCOL + 9, "%-8.8s", intrname[i]); } X(intrcnt); l = (int)((float)s.intrcnt[i]/etime + 0.5); inttotal += l; ! putint(l, intrloc[i], INTSCOL, 8); } ! putint(inttotal, INTSROW + 1, INTSCOL, 8); Z(ncs_goodhits); Z(ncs_badhits); Z(ncs_miss); Z(ncs_long); Z(ncs_pass2); Z(ncs_2passes); Z(ncs_neghits); s.nchcount = nchtotal.ncs_goodhits + nchtotal.ncs_badhits + --- 389,403 ---- if (nextintsrow == LINES) continue; intrloc[i] = nextintsrow++; ! mvprintw(intrloc[i], INTSCOL + 9, "%-10.10s", intrname[i]); } X(intrcnt); l = (int)((float)s.intrcnt[i]/etime + 0.5); inttotal += l; ! putint(l, intrloc[i], INTSCOL + 2, 6); } ! putint(inttotal, INTSROW + 1, INTSCOL + 2, 6); Z(ncs_goodhits); Z(ncs_badhits); Z(ncs_miss); Z(ncs_long); Z(ncs_pass2); Z(ncs_2passes); Z(ncs_neghits); s.nchcount = nchtotal.ncs_goodhits + nchtotal.ncs_badhits + ----------------------------8<------------------------------------ Thanks! M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Tue Mar 28 10:16:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23021 for current-outgoing; Tue, 28 Mar 1995 10:16:25 -0800 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA23015; Tue, 28 Mar 1995 10:16:20 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.11/8.6.11) id LAA11924; Tue, 28 Mar 1995 11:17:56 -0700 Message-Id: <199503281817.LAA11924@rocky.sri.MT.net> From: Nate Williams Date: Tue, 28 Mar 1995 11:17:56 -0700 In-Reply-To: "Nate Williams" "cvs commit: src/share/mk bsd.lib.mk" (Mar 28, 9:54) Reply-To: Nate Williams X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: CVS-commiters@freefall.cdrom.com, cvs-share@freefall.cdrom.com Subject: Re: cvs commit: src/share/mk bsd.lib.mk Cc: current@FreeBSD.org, jkh@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > nate 95/03/28 09:54:12 > > Modified: share/mk bsd.lib.mk > Log: > *Really* strip out unused local symbols from shared objects. Okay, this should fix the problem Jordan was having with the static hash function being visible outside of the routine. Note, there are apparently still some 'stripping' bugs that exist in ld that Bruce pointed out, and I have a pretty good idea Bruce would like to see those symbols be visible, but until we get ld to be happy with the local symbols intact, the above change needed to be made. Current users. This change should cause you no problems whatsoever, but I would recommend re-building your libraries simply because there are symbols in them that don't need to be there, and those may cause linker problems at a later date with other programs who use some of the libraries internal symbols. This will cause the libraries for 2.1R to be safe with the current ld. Nate From owner-freebsd-current Tue Mar 28 11:46:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25307 for current-outgoing; Tue, 28 Mar 1995 11:46:14 -0800 Received: from catfish.dataplex.net ([199.183.109.243]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA25297 for ; Tue, 28 Mar 1995 11:46:12 -0800 Received: from [199.183.109.242] (cod [199.183.109.242]) by catfish.dataplex.net (8.6.9/8.6.9) with SMTP id NAA19104; Tue, 28 Mar 1995 13:44:51 -0600 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 28 Mar 1995 13:44:53 -0600 To: Paul Richards From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: shared library versioning Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >> Well, all that's really needed is a file (I propose >> /usr/share/misc/shlib-numbers) which lists the shared-libraries and >> minor numbers used in each release. I will do this today if somebody >> doesn't beat me to it. > >I'm not sure I like that idea, since people will forget to either check the >file or keep it up to date. > >I'd prefer some comment in the Makefile that flags that the library beens >bumped and then have a script which runs through the tree removing these >comments as part of the release process so they're clean at the start of the >next release. Actually, this COULD be automatic. As I see it, any change to the libraries that requires a version number change is a reflaction of a change in the header files. Therefore a make rule than "library version cookie" depends on "headers", would generate the proper increment. The only problem that I see is that my own local version numbers might get bumped numerous times between releases. To address that, either I would have to manually rebuild my executables after a release or we need some sort of major.minor.sub numbering scheme which allows us to "jump" to the next minor number with an actual release. These would be easy to find... If the sub number is not zero, we need to bump the minor number. IMHO, if we were to use such a scheme, the minor number should either stay the same (if nothing changed) or it should match the release number that includes the change. ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Tue Mar 28 15:48:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA01010 for current-outgoing; Tue, 28 Mar 1995 15:48:29 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA01003; Tue, 28 Mar 1995 15:48:28 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: current@freefall.cdrom.com cc: se@freefall.cdrom.com Subject: NCR support broken in 950322-SNAP? Date: Tue, 28 Mar 1995 15:48:28 -0800 Message-ID: <1002.796434508@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk I can get the exact text of the message if necessary, but just trying to install 950322-SNAP on an NCR machine just caused an assertion failure in ncr.c followed by general failure. Unfortunately, it cleared the screen shortly thereafter before I could copy it down, but I can reproduce it as necessary. I'm not sure it's necessary in any case as I just saw a very similar (well, identical) failure report from someone else (WITH the text :), so I'm getting the feeling that the NCR driver is simply broken in -current. Anyone care to try and verify this? Thanks! Jordan From owner-freebsd-current Tue Mar 28 18:17:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02605 for current-outgoing; Tue, 28 Mar 1995 18:17:39 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA02599; Tue, 28 Mar 1995 18:17:32 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id KAA06206; Wed, 29 Mar 1995 10:18:03 GMT Date: Wed, 29 Mar 1995 10:18:03 +0000 () From: Brian Tao To: "Jordan K. Hubbard" cc: current@freefall.cdrom.com, se@freefall.cdrom.com Subject: Re: NCR support broken in 950322-SNAP? In-Reply-To: <1002.796434508@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 28 Mar 1995, Jordan K. Hubbard wrote: > > I can get the exact text of the message if necessary, but just trying > to install 950322-SNAP on an NCR machine just caused an assertion failure > in ncr.c followed by general failure. I've installed the 950322 snapshot on my ASUS 486PVI-AP4 motherboard with the NCR53c810 controller and a Quantum Empire 1080S without any problems. I *did* get an error right after giving the NFS install part my hostname, but it doesn't have anything to do with the NCR code. The screen cleared and went on to the next dialog before I could read it though. :( Something about /etc/sysconfig not being there, I think? I'll try to pin it down later this week when I go do another FreeBSD install. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Tue Mar 28 18:39:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03006 for current-outgoing; Tue, 28 Mar 1995 18:39:40 -0800 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA02990 for ; Tue, 28 Mar 1995 18:39:32 -0800 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <05853-0@bunyip.cc.uq.oz.au>; Wed, 29 Mar 1995 12:38:31 +1000 Received: from orion.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id MAA00483; Wed, 29 Mar 1995 12:39:20 +1000 Received: by orion.devetir.qld.gov.au (8.6.10/DEVETIR-0.2a) id MAA29753; Wed, 29 Mar 1995 12:36:32 +1000 Date: Wed, 29 Mar 1995 12:36:32 +1000 From: Stephen McKay Message-Id: <199503290236.MAA29753@orion.devetir.qld.gov.au> To: Mark Murray cc: Poul-Henning Kamp , syssgm@devetir.qld.gov.au, freebsd-current@FreeBSD.org Subject: Re: To all the ctm'mers... Sender: current-owner@FreeBSD.org Precedence: bulk Mark Murray writes: >> > Sure. But _where_? Where does sendmail get a path from? >> >> I use this: >> ctm-cvs-cur: "| PATH=$PATH:/usr/sbin /usr/sbin/ctm_rmail -l /archive/CTM_m >ail >> /log -p /archive/CTM_mail -d /archive/CTM -b /home/ncvs" >> >> and it works, but is gross... >> >> I belive ctm_rmail should use an absolute path to the ctm program. > >How about assuming that ctm is in the same directory as ctm_rmail? [Disclaimer: I've lost 4 days mail due to a tragic error, so I've missed the start of this. I haven't found the mail archives either. FAQ maintainer, wherefor art thou?] As the ctm_rmail author, and the person who made Poul remove the absolute path to ctm, I should explain myself. I think it is a trivial matter to arrange for the PATH to be correct, and a non-trivial matter to change a builtin pathname. I actually run the ctm system on a non-FreeBSD box (and NFS mount the result to a test FreeBSD box), and therefore see the added flexibility as well worth it. My incoming mail situation isn't simple: my .forward calls MH slocal which runs through my .maildelivery which calls /usr/syssgm/bin/ctm_incoming which does the hard work. So, translating, someone like yourself could use an entry in /etc/aliases: ctm-cvs-cur: "| /foo/bar/ctm_incoming" and have /foo/bar/ctm_incoming contain something like: #! /bin/sh PATH="your favourite path" export PATH cd /place/for/goodies || exit 1 exec ctm_rmail -f -l log -p pieces -d deltas -b /current/src Now, that wasn't too hard, was it? :-) Stephen. From owner-freebsd-current Tue Mar 28 18:42:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03177 for current-outgoing; Tue, 28 Mar 1995 18:42:09 -0800 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 SAA03171 for ; Tue, 28 Mar 1995 18:42:07 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id SAA06250; Tue, 28 Mar 1995 18:41:28 -0800 From: Poul-Henning Kamp Message-Id: <199503290241.SAA06250@ref.tfs.com> Subject: Re: To all the ctm'mers... To: syssgm@devetir.qld.gov.au (Stephen McKay) Date: Tue, 28 Mar 1995 18:41:28 -0800 (PST) Cc: mark@grondar.za, syssgm@devetir.qld.gov.au, freebsd-current@FreeBSD.org In-Reply-To: <199503290236.MAA29753@orion.devetir.qld.gov.au> from "Stephen McKay" at Mar 29, 95 12:36:32 pm Content-Type: text Content-Length: 459 Sender: current-owner@FreeBSD.org Precedence: bulk > [Disclaimer: I've lost 4 days mail due to a tragic error, so I've missed the > start of this. I haven't found the mail archives either. FAQ maintainer, > wherefor art thou?] Stephen thanks for the explanation. BTW: Submissions to the faq should be sent to faq@freebsd.org -- 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 Tue Mar 28 22:08:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA22817 for current-outgoing; Tue, 28 Mar 1995 22:08:01 -0800 Received: from kksys.skypoint.net (kksys.skypoint.net [199.86.32.5]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA22810 for ; Tue, 28 Mar 1995 22:07:57 -0800 Received: from starfire.mn.org by kksys.skypoint.net with smtp (Smail3.1.29.1 #2) id m0rtqvF-0004n5C; Wed, 29 Mar 95 00:08 CST Received: (from john@localhost) by starfire.mn.org (8.6.8/1.2.1) id AAA23974 for current@freebsd.org; Wed, 29 Mar 1995 00:06:33 -0600 From: John Lind Message-Id: <199503290606.AAA23974@starfire.mn.org> Subject: Minor bumps with 2.0-950322-SNAP To: current@FreeBSD.org Date: Wed, 29 Mar 1995 00:06:32 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1467 Sender: current-owner@FreeBSD.org Precedence: bulk First of all, congratulations to all on another fine SNAP! Things just keep getting better and better. This was a clean install on a newly configured 486DX2/66,bt0,barracuda 2.15Gb lashup with a WD8013 as ed1. After the first time I enter the full domain name, some sort of error flashes on the F1 screen, but too quickly to see, after which the question is repeated. On answering the question again, things appear to proceed correctly. No errors are recorded on vt1(F2). Then, after selected FTP load and setting the IP address, netmask, gateway, and name server, and selecting bin, man pages, src, security, and XFree86, it seems to start transferring, but examining screen vt1(F2) shows: NcFTP: Could not get your passwd entry! (9): Bad file descriptor If you abort the installation process during FTP file transfer, the displays on vt0 get pretty messed up. I'd be more specific, but I'm pretty sure that you'll see what I mean if you try it. Also, I think that I was fighting with a bad 10baseT cable and ended up switching to the BNC connector to do the install, but just for the record, what are the appropriate other flags (if any) to use the UTP connector on a WD8013EBT? I checked the FAQ's, and INSTALL, README, and RELNOTES, but didn't find this information. Thanks again to you diligent folks working on this marvelous resource! John Lind, Starfire Consulting Services E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417 From owner-freebsd-current Tue Mar 28 22:32:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA09624 for current-outgoing; Tue, 28 Mar 1995 22:32:55 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA09618 for ; Tue, 28 Mar 1995 22:32:53 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id WAA05865; Tue, 28 Mar 1995 22:32:39 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id WAA00267; Tue, 28 Mar 1995 22:32:39 -0800 Message-Id: <199503290632.WAA00267@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: John Lind cc: current@FreeBSD.org Subject: Re: Minor bumps with 2.0-950322-SNAP In-reply-to: Your message of "Wed, 29 Mar 95 00:06:32 CST." <199503290606.AAA23974@starfire.mn.org> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 28 Mar 1995 22:32:38 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >Also, I think that I was fighting with a bad 10baseT cable and ended >up switching to the BNC connector to do the install, but just for the >record, what are the appropriate other flags (if any) to use the UTP >connector on a WD8013EBT? I checked the FAQ's, and INSTALL, README, >and RELNOTES, but didn't find this information. The connection type isn't controlled in the driver for the 80x3 cards. It has to be set on the card (via jumper or softconfig, whichever is appropriate). -DG From owner-freebsd-current Tue Mar 28 23:40:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11175 for current-outgoing; Tue, 28 Mar 1995 23:40:28 -0800 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 XAA11158 for ; Tue, 28 Mar 1995 23:39:46 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA21500; Wed, 29 Mar 1995 17:33:20 +1000 Date: Wed, 29 Mar 1995 17:33:20 +1000 From: Bruce Evans Message-Id: <199503290733.RAA21500@godzilla.zeta.org.au> To: pst@shockwave.com Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Synopsis: the new slice code is bitching about my old slices >1) It looks like the implicit label stuff for unlabeled disks is > non-functional? I cannot ask disklable to read the pseudo-label off > of sd1 So we need the pseudo-label on all BSD slices? Perhaps a read-only one on non-BSD slices? This would make it possible to determine the type and size of all slices using standard ioctls and utilities (fdisk is nonstandard and doesn't support extended partitions). There are some semantic problems with modifiying pseudo-labels. All the slices and labels are currently reread on first-opens to pick up any changes to the DOSpartition table (changes to labels are handled better). Modifications are thus going to be lost immediately (instead of at the next boot) unless you keep another device on the drive open. Bruce From owner-freebsd-current Tue Mar 28 23:46:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11240 for current-outgoing; Tue, 28 Mar 1995 23:46:11 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11233; Tue, 28 Mar 1995 23:46:07 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id XAA00427; Tue, 28 Mar 1995 23:45:29 -0800 Message-Id: <199503290745.XAA00427@precipice.shockwave.com> To: jkh@FreeBSD.org, phk@FreeBSD.org cc: current@FreeBSD.org Subject: grumbles from the grave Date: Tue, 28 Mar 1995 23:45:29 -0800 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk I -am- retired, but the reorganization of the rc scripts has been annoying me, so I've gone through and redone them. I've kept all of the spirit of sysconfig et al (in fact, sysconfig hasn't changed at all), but I've fixed all of the ordering problems that I could find or recognize and moved things so they actually make better sense (and are closer to BSD spirit in functionality). This stuff has been tested thoroughly in as many bizzare configurations as I could handle. -->>> This stuff does NOT include any changes made since 1pm yesterday. I am not giving this to you as diffs because diffs don't make sense here. Comments: (a) sysconfig is still used to do all configuration. I was not going to change that out from under you.... a user never need edit netstart or rc* unless they're being very weird. (b) rc.maint has been folded back into rc. It is just unworkable as a separate chunk because of ordering bogosities (c) netstart does what it says... it starts up enough of the network to get up, it doesn't start every bloody daemon that might talk to a socket... netstart ifconfig's the devices and sets up routing if configured to do so. (d) nfs disks are mounted immediately after netstart completes (e) syslog is started as early as possible (right after nfs) so that error messages can get logged to remote syslog servers properly (f) named is started (there is an argument that says that named should be started before syslogd because if you are the dns server for your domain, you'd like named to resolve remote hosts in syslog.conf, but this is a minority case and the trivial workarround is to put the syslog host in /etc/hosts or use an /etc/resolv.conf -- why? because you want syslog to catch named errors, which is a MUCH more important and likely occurance) (g) NOW all of the rest of the network daemons such as the time stuff, RPC, NIS, NFS, Kerberos and inetd are started (h) the rest of the generic stuff is done (cron/printer/sendmail) (i) shared libraries are set (j) /etc/rc.i386 is run (this does FreeBSD/386 specific stuff like ibcs2, xtend, and all of the syscons stuff (this is actually started as /etc/rc.`uname -m` (k) the syscons stuff has gotten a serious cleaning to make it consistent with rc conventions (l) rc.local has had the comments about syscons removed (they are not relevant to this file now) and the full name of the kernel has been restored to /etc/motd So, please make the following changes: replace src/etc/netstart with this new one replace src/etc/rc with this new one replace src/etc/rc.local with this new one remove src/etc/rc.maint and rules, it is no longer needed add src/etc/i386/rc.i386 and a makefile install rule ^^^^ OK, -now- I'm retired. # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # netstart # rc # rc.i386 # rc.local # echo x - netstart sed 's/^X//' >netstart << 'END-of-netstart' X#!/bin/sh - X# X# $Id: netstart,v 1.2 1995/03/26 18:18:59 wpaul Exp $ X# From: @(#)netstart 5.9 (Berkeley) 3/30/91 X X# my-name is my symbolic name X# my-netmask is specified in /etc/networks X# Xif [ -z "`hostname -s`" ] ; then X hostname $hostname Xfi X X# Set the domainname if we're using NIS Xif [ -z "`domainname`" -a -e "/etc/defaultdomain" ] ; then X domainname=`cat /etc/defaultdomain` X domainname $domainname Xfi X Xfor i in /etc/hostname.* Xdo X ifn=`expr $i : '/etc/hostname\.\(.*\)'` X if [ -e /etc/hostname.$ifn ]; then X if [ -e /etc/start_if.$ifn ]; then X sh /etc/start_if.$ifn $ifn X fi X ifconfig $ifn `cat /etc/hostname.$ifn` X ifconfig $ifn X fi Xdone X X# set the address for the loopback interface Xifconfig lo0 inet localhost X X# set interface for multicasts to default interface X# this needs to happen before router discovery Xroute add 224.0.0.0 -netmask 0xf0000000 -interface $hostname X Xif [ -n "$defaultrouter" -a "x$defaultrouter" != "xNO" ] ; then X route add default $defaultrouter Xelif [ -f /etc/defaultrouter ] ; then X route add default `cat /etc/defaultrouter` Xfi X X# use loopback, not the wire X# route add $hostname localhost X Xif [ "x$gated" != "xNO" -o "x$routedflags" != "xNO" ] ; then X echo -n starting routing daemons: X X # $gated and $routedflags are imported from /etc/sysconfig. X # If $gated == YES, gated is used; otherwise routed. X # If $routedflags == NO, routed isn't run. X X if [ "X${gated}" = X"YES" -a -r /etc/gated.conf ]; then X echo -n ' gated'; gated $gatedflags X elif [ "X${routedflags}" != X"NO" ]; then X echo -n ' routed'; routed $routedflags X fi X X echo '.' Xfi END-of-netstart echo x - rc sed 's/^X//' >rc << 'END-of-rc' X#!/bin/sh X# $Id: rc,v 1.56 1995/03/26 18:18:58 wpaul Exp $ X# From: @(#)rc 5.27 (Berkeley) 6/5/91 X X# System startup script run by init on autoboot X# or after single-user. X# Output and error are redirected to console by init, X# and the console is the controlling terminal. X Xstty status '^T' X X# Set shell to ignore SIGINT (2), but not children; X# shell catches SIGQUIT (3) and returns to single user after fsck. Xtrap : 2 Xtrap : 3 # shouldn't be needed X XHOME=/; export HOME XPATH=/sbin:/bin:/usr/sbin:/usr/bin Xexport PATH X Xswapon -a X Xif [ $1x = autobootx ] Xthen X echo Automatic reboot in progress... X fsck -p X case $? in X 0) X ;; X 2) X exit 1 X ;; X 4) X reboot X echo "reboot failed... help!" X exit 1 X ;; X 8) X echo "Automatic file system check failed... help!" X exit 1 X ;; X 12) X echo "Reboot interrupted" X exit 1 X ;; X 130) X # interrupt before catcher installed X exit 1 X ;; X *) X echo "Unknown error in reboot" X exit 1 X ;; X esac Xelse X echo Skipping disk checks ... Xfi X Xtrap "echo 'Reboot interrupted'; exit 1" 3 X X# root must be read/write both for NFS diskless and for VFS LKMs before X# proceeding any further. Xmount -u -o rw / X Xumount -a >/dev/null 2>&1 Xmount -a -t nonfs X X# If the machine runs wall CMOS clock (compatible with MSDOS), X# activate following line by creating empty file /etc/wall_cmos_clock X# If this file not exist, following line does nothing (assumed X# the machine runs UTC CMOS clock). See adjkerntz(8) for details. Xadjkerntz -i X X# If there is a global system configuration file, suck it in. Xif [ -f /etc/sysconfig ]; then X . /etc/sysconfig Xfi X X# configure serial devices Xif [ -f /etc/rc.serial ]; then X . /etc/rc.serial Xfi X X# start up the network Xif [ -f /etc/netstart ]; then X . /etc/netstart Xfi X Xmount -a -t nfs >/dev/null 2>&1 & # XXX shouldn't need background X X# Whack the pty perms back into shape. Xchmod 666 /dev/tty[pqrs]* X X# clean up left-over files Xrm -f /etc/nologin Xrm -f /var/spool/lock/* Xrm -f /var/spool/uucp/.Temp/* Xrm -f /dev/log X(cd /var/run && { rm -rf -- *; cp /dev/null utmp; chmod 644 utmp; }) X Xecho clearing /tmp X X# prune quickly with one rm, then use find to clean up /tmp/[lq]* X# (not needed with mfs /tmp, but doesn't hurt there...) X(cd /tmp && rm -rf [a-km-pr-zA-Z]* && X find -d . ! -name . ! -name lost+found ! -name quotas -exec rm -rf -- {} \;) X X# /var/crash should be a directory or a symbolic link X# to the crash directory if core dumps are to be saved. Xif [ "X${savecore}" = X"YES" -a -d /var/crash ]; then X echo -n checking for core dump... X savecore /var/crash Xfi X X# snapshot any kernel -c changes back to disk Xecho 'recording kernel -c changes' X/sbin/dset -q X X# Check the quotas Xif [ "X${check_quotas}" = X"YES" ]; then X echo 'checking quotas:' X quotacheck -a X echo ' done.' X quotaon -a Xfi X X# start system logging and name service (named needs to start before syslogd X# if you don't have a /etc/resolv.conf) X# Xecho -n starting system daemons: X Xecho ' syslogd.'; syslogd X Xecho -n starting network daemons: X X# $namedflags is imported from /etc/sysconfig Xif [ "X${namedflags}" != "XNO" ]; then X echo -n ' named'; named $namedflags Xfi X X# $ntpdate and $xntpdflags are imported from /etc/sysconfig. X# If $ntpdate != NO, run ntpdate $ntpdate to set the date correctly. X# If $xntpdflags != NO, start xntpd. Xif [ "X${ntpdate}" != X"NO" -o "X${xntpdflags}" != X"NO" ]; then X if [ "X${tickadjflags}" != X"NO" ]; then X echo -n ' tickadj'; tickadj ${tickadjflags--Aq} X fi X X if [ "X${ntpdate}" != X"NO" ]; then X echo -n ' ntpdate'; ntpdate ${ntpdate} >/dev/null 2>&1 X fi X X if [ "X${xntpdflags}" != X"NO" ]; then X echo -n ' xntpd'; xntpd ${xntpdflags} X fi Xfi X X# $timedflags is imported from /etc/sysconfig; X# if $timedflags == NO, timed isn't run. Xif [ "X${timedflags}" != X"NO" ]; then X echo -n ' timed'; timed $timedflags Xfi X X# Portmapper should always be run, to provide RPC services for inetd. Xif [ -x /usr/sbin/portmap ]; then X echo -n ' portmap'; portmap Xfi X X# Start ypserv if we're an NIS server. X# Run yppasswdd only on the NIS master server Xif [ "X${nis_serverflags}" != X"NO" ]; then X echo -n ' ypserv'; ypserv ${nis_serverflags} X X if [ "X${yppasswddflags}" != X"NO" ]; then X echo -n ' yppasswdd'; yppasswdd ${yppasswddflags} X fi Xfi X X# Start ypbind if we're an NIS client Xif [ "X${nis_clientflags}" != X"NO" ]; then X echo -n ' ypbind'; ypbind ${nis_clientflags} Xfi X X# $rwhod is imported from /etc/sysconfig; X# if $rwhod is set to YES, rwhod is run. Xif [ "X${rwhod}" = X"YES" ]; then X echo -n ' rwhod'; rwhod Xfi X Xif [ "X${nfs_server}" = X"YES" -a -r /etc/exports ]; then X echo -n ' mountd'; mountd X echo -n ' nfsd'; nfsd -u -t 4 Xfi X Xif [ "X${nfs_client}" = X"YES" ]; then X echo -n ' nfsiod'; nfsiod -n 4 Xfi X Xif [ "X${amdflags}" != X"NO" ]; then X echo -n ' amd'; amd ${amdflags} Xfi X X# Kerberos runs ONLY on the Kerberos server machine Xif [ "X${kerberos_server}" = X"YES" ]; then X echo -n ' kerberos'; kerberos >> /var/log/kerberos.log & X echo -n ' kadmind'; \ X (sleep 20; /usr/sbin/kadmind -n >/dev/null 2>&1 &) & Xfi X Xecho -n ' inetd'; inetd Xecho '.' X X# build ps databases Xkvm_mkdb Xdev_mkdb X X# check the password temp/lock file Xif [ -f /etc/ptmp ] Xthen X logger -s -p auth.err \ X "password file may be incorrect -- /etc/ptmp exists" Xfi X X# Recover vi editor files. Xvirecovery=/var/tmp/vi.recover/recover.* Xif [ "$virecovery" != "/var/tmp/vi.recover/recover.*" ]; then X echo 'Recovering vi editor sessions' X for i in $virecovery; do X sendmail -t < $i X done Xfi X Xif [ "X${accounting}" = X"YES" -a -d /var/account ]; then X echo 'turning on accounting'; accton /var/account/acct Xfi X X# Now start up miscellaneous daemons that don't belong anywhere else X# Xecho -n standard daemons: Xecho -n ' cron'; cron Xecho -n ' printer'; lpd X X# $sendmail_flags is imported from /etc/sysconfig; X# if $sendmail_flags is something other than NO, sendmail is run. Xif [ "X${sendmail_flags}" != X"NO" -a -r /etc/sendmail.cf ]; then X echo -n ' sendmail'; sendmail ${sendmail_flags} Xfi X Xecho '.' X X# Make shared lib searching a little faster. Leave /usr/lib first if you X# add your own entries or you may come to grief. Xif [ -x /sbin/ldconfig ]; then X _LDC=/usr/lib X if [ -d /usr/X11R6/lib ]; then _LDC="${_LDC} /usr/X11R6/lib" ; fi X if [ -d /usr/X386/lib ]; then _LDC="${_LDC} /usr/X386/lib" ; fi X if [ -d /usr/local/lib ]; then _LDC="${_LDC} /usr/local/lib" ; fi X if [ -d /usr/gnu/lib ]; then _LDC="${_LDC} /usr/gnu/lib" ; fi X echo 'setting ldconfig path:' ${_LDC} X ldconfig ${_LDC} Xfi X X# configure implementation specific stuff Xarch=`uname -m` Xif [ -f /etc/rc.$arch ]; then X . /etc/rc.$arch Xfi X X# Do traditional (but rather obsolete) rc.local file if it exists. Xif [ -f /etc/rc.local ]; then X sh /etc/rc.local Xfi X Xdate Xexit 0 END-of-rc echo x - rc.i386 sed 's/^X//' >rc.i386 << 'END-of-rc.i386' X#!/bin/sh - X# X# $Id$ X# Do i386 specific processing X# X Xecho -n 'enabling FreeBSD/386 options:' X X# Start the SCO binary emulation if requested. Xif [ "X${ibcs2}" = X"YES" ]; then X echo -n ' ibcs2'; ibcs2 Xfi X Xif [ "X${xtend}" != X"NO" -a -x /usr/libexec/xtend ]; then X echo -n ' xtend'; /usr/libexec/xtend Xfi X X########################################################################## X####### Syscons section ######## X########################################################################## X X# don't change these, they're modified below Xkbdadjust=NO Xvidadjust=NO X X[ "X${keymap}" != X"NO" -o "X${keyrate}" != X"NO" ] && kbdadjust=YES X[ "X${scrnmap}" != X"NO" -o "X${font8x16}" != X"NO" -o \ X "X${font8x14}" != X"NO" -o "X${font8x8}" != X"NO" -o \ X "X${blanktime}" != X"NO" ] && vidadjust=YES X X[ "X${kbdadjust}" != X"NO" ] && echo -n ' [kbdcontrol:' X X# keymap Xif [ "X${keymap}" != X"NO" ]; then X echo -n ' keymap'; kbdcontrol -l ${keymap} Xfi X X# keyrate Xif [ "X${keyrate}" != X"NO" ]; then X echo -n ' keyrate'; kbdcontrol -r ${keyrate} Xfi X X[ "X${kbdadjust}" != X"NO" ] && echo ']' X X X[ "X${vidadjust}" != X"NO" ] && echo -n ' [vidcontrol:' X X# screen mapping Xif [ "X${scrnmap}" != X"NO" ]; then X echo -n ' screen_map'; vidcontrol -l ${scrnmap} Xfi X X# font 8x16 Xif [ "X${font8x16}" != X"NO" ]; then X echo -n ' font8x16'; vidcontrol -f 8x16 ${font8x16} Xfi X X# font 8x14 Xif [ "X${font8x14}" != X"NO" ]; then X echo -n ' font8x14'; vidcontrol -f 8x14 ${font8x14} Xfi X X# font 8x8 Xif [ "X${font8x8}" != X"NO" ]; then X echo -n ' font8x8'; vidcontrol -f 8x8 ${font8x8} Xfi X X# blank time Xif [ "X${blanktime}" != X"NO" ]; then X echo -n ' blank_time'; vidcontrol -t ${blanktime} Xfi X X[ "X${vidadjust}" != X"NO" ] && echo ']' X X# screen saver Xif [ "X${saver}" != X"NO" ] ; then X echo -n ' screensaver: ' X modstat | grep _saver || modload -u -o /tmp/saver_mod -e \ X saver_init -q /lkm/${saver}_saver_mod.o Xfi END-of-rc.i386 echo x - rc.local sed 's/^X//' >rc.local << 'END-of-rc.local' X# X# site-specific startup actions, daemons X# X# $Id: rc.local,v 1.16 1995/03/16 16:58:01 wollman Exp $ X# X XT=/tmp/_motd Xrm -f $T Xuname -v | sed -e 's/199[0-9]/&\ X/' > $T Xecho "" >> $T Xsed '1,/^$/d' < /etc/motd >> $T Xcp $T /etc/motd Xchmod 644 /etc/motd Xrm -f $T X_HOST=`hostname` X Xecho -n 'starting local daemons:' X X# put your local stuff here X Xecho '.' END-of-rc.local exit From owner-freebsd-current Tue Mar 28 23:46:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11255 for current-outgoing; Tue, 28 Mar 1995 23:46:32 -0800 Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11249 for ; Tue, 28 Mar 1995 23:46:31 -0800 Received: from metal.ops.neosoft.com (root@glenn-slip44.nmt.edu [129.138.5.144]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id BAA12113 for ; Wed, 29 Mar 1995 01:46:20 -0600 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id AAA00361 for current@freebsd.org; Wed, 29 Mar 1995 00:46:17 -0700 From: Scott Mace Message-Id: <199503290746.AAA00361@metal.ops.neosoft.com> Subject: new slice stuff... finally got it working. To: current@FreeBSD.org Date: Wed, 29 Mar 1995 00:46:16 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1040 Sender: current-owner@FreeBSD.org Precedence: bulk I Think I've finally got everything functional. I redid my filesystems totally, (even though it theoretically wasn't necessary). Here is some info about my system. I'm posting this so that it might help others fix their systems. This was my old config under 2.0: sd0: 249 meg DOS, 64 meg freebsd (root) sd1: 64 meg (var), 64 megs swap, 1928 usr. My new config is as follows: sd0: 313 meg DOS sd1: 64meg root, 64 var, 64 swap, rest usr. 1. I backed everything up. 2. used msdos fdisk on sd0. (left the booteasy MBR alone). 3. Used the march snap disk to setup sd1. The sd1 mounts are pretty simple. I used /dev/sd0s1 for the dos mount. I also experimented with a 249DOS/65meg freebsd layout on sd0. I first used the dos fdisk to layout the dos partition in slice 1. I then did: fdisk -u /dev/rsd0 to add my freebsd partition. I had to run disklabel on /dev/rsd0s2 not /dev/rsd0d. Be REAL sure you have to new slicce devices in /dev or there isn't too much of a chance it will work. Hope this helps some people, Scott From owner-freebsd-current Tue Mar 28 23:49:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11327 for current-outgoing; Tue, 28 Mar 1995 23:49:59 -0800 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 XAA11321; Tue, 28 Mar 1995 23:49:58 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id XAA07558; Tue, 28 Mar 1995 23:49:49 -0800 From: Poul-Henning Kamp Message-Id: <199503290749.XAA07558@ref.tfs.com> Subject: Re: grumbles from the grave To: pst@shockwave.com (Paul Traina) Date: Tue, 28 Mar 1995 23:49:49 -0800 (PST) Cc: jkh@FreeBSD.org, phk@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199503290745.XAA00427@precipice.shockwave.com> from "Paul Traina" at Mar 28, 95 11:45:29 pm Content-Type: text Content-Length: 432 Sender: current-owner@FreeBSD.org Precedence: bulk > OK, -now- I'm retired. Paul, I think I know more than enough about why, I just want to say thanks! You're one of the few FreeBSD people I havn't got around to talk to here in the bay, I'd still like to get a chance to do that some day, after 2.1. -- 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 Tue Mar 28 23:53:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11382 for current-outgoing; Tue, 28 Mar 1995 23:53:03 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11376 for ; Tue, 28 Mar 1995 23:53:02 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id XAA00497; Tue, 28 Mar 1995 23:51:42 -0800 Message-Id: <199503290751.XAA00497@precipice.shockwave.com> To: Bruce Evans cc: current@FreeBSD.org Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Wed, 29 Mar 1995 17:33:20 +1000." <199503290733.RAA21500@godzilla.zeta.org.au> Date: Tue, 28 Mar 1995 23:51:41 -0800 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk No, what you have done is absolutely right. Disklabel should not be able to read a bsd pseudolabel if there is no BSD label there. All concerns I have are gone. From: Bruce Evans Subject: Re: kern/280: new slice manager totally confused about old slice dis >>ks >>Synopsis: the new slice code is bitching about my old slices >1) It looks like the implicit label stuff for unlabeled disks is > non-functional? I cannot ask disklable to read the pseudo-label off > of sd1 So we need the pseudo-label on all BSD slices? Perhaps a read-only one on non-BSD slices? This would make it possible to determine the type and size of all slices using standard ioctls and utilities (fdisk is nonstandard and doesn't support extended partitions). There are some semantic problems with modifiying pseudo-labels. All the slices and labels are currently reread on first-opens to pick up any changes to the DOSpartition table (changes to labels are handled better). Modifications are thus going to be lost immediately (instead of at the next boot) unless you keep another device on the drive open. Bruce From owner-freebsd-current Wed Mar 29 00:43:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA11893 for current-outgoing; Wed, 29 Mar 1995 00:43:36 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA11887; Wed, 29 Mar 1995 00:43:35 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id AAA00332; Wed, 29 Mar 1995 00:42:25 -0800 Message-Id: <199503290842.AAA00332@precipice.shockwave.com> To: Poul-Henning Kamp cc: jkh@FreeBSD.org, phk@FreeBSD.org, current@FreeBSD.org Subject: Re: grumbles from the grave In-reply-to: Your message of "Tue, 28 Mar 1995 23:49:49 PST." <199503290749.XAA07558@ref.tfs.com> Date: Wed, 29 Mar 1995 00:42:25 -0800 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk Ditto, it would be fun to see the real folks. From: Poul-Henning Kamp Subject: Re: grumbles from the grave > OK, -now- I'm retired. Paul, I think I know more than enough about why, I just want to say thanks! You're one of the few FreeBSD people I havn't got around to talk to here in the bay, I'd still like to get a chance to do that some day, after 2.1. -- 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 Mar 29 01:05:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12238 for current-outgoing; Wed, 29 Mar 1995 01:05:39 -0800 Received: from netbsd.csie.nctu.edu.tw (root@netbsd.csie.nctu.edu.tw [140.113.17.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA12229 for ; Wed, 29 Mar 1995 01:05:31 -0800 Received: (from jdli@localhost) by netbsd.csie.nctu.edu.tw (8.6.11/8.6.9) id RAA05966 for freebsd-current@FreeBSD.ORG; Wed, 29 Mar 1995 17:01:41 +0800 Date: Wed, 29 Mar 1995 17:01:41 +0800 From: ¡¹ ¤p¤p¬P¥ú ¡¹ Message-Id: <199503290901.RAA05966@netbsd.csie.nctu.edu.tw> To: freebsd-current@FreeBSD.org Subject: New slice code Sender: current-owner@FreeBSD.org Precedence: bulk Hi : The new SNAP came with new slice code, does it improve anything? Does it mean that I can mount a DOS-extend partition ? Or even I can install FreeBSD in extend partition like Linux ? Thanks a lot !! :) From owner-freebsd-current Wed Mar 29 01:27:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12976 for current-outgoing; Wed, 29 Mar 1995 01:27:04 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA12929 for ; Wed, 29 Mar 1995 01:25:41 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA13441; Wed, 29 Mar 1995 11:23:52 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id LAA05475 for freebsd-current@FreeBSD.org; Wed, 29 Mar 1995 11:23:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id KAA26101 for freebsd-current@FreeBSD.org; Wed, 29 Mar 1995 10:41:39 +0200 From: J Wunsch Message-Id: <199503290841.KAA26101@uriah.heep.sax.de> Subject: Re: FreeBSD problems - VM bug? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 29 Mar 1995 10:41:38 +0200 (MET DST) In-Reply-To: <199503280743.JAA02693@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Mar 28, 95 09:43:37 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 954 Sender: current-owner@FreeBSD.org Precedence: bulk As Christoph Kukulies wrote: > > > Oooops. Sorry, i meant 95*03*21. ! > I wouldn't trust that mix. I had all sorts of trouble when mixing > a 950210 with later kernels. 950210-SNAP hadn't been very trustable. > Did Martin upgrade to -current or do a full install from 950321-SNAP? > Do the VM problems persist? The 950321 SNAP didn't appear yet on our ftp server (it's mirrored across several hops). And my attempts to compile Martin a private SNAP failed miserably due to the reported frequent NFS server hangs. (I had to use an old SX/16 as an external disk in order to put all the releases stuff there.) > I have a 386SX-16 8MB, IDE, (Morse board) and I'm running some 95 SNAP on > it w/o problems. Even as a heavy-loaded NFS server? That's all where my box is failing, everything else works fine. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Mar 29 01:44:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA21931 for current-outgoing; Wed, 29 Mar 1995 01:44:02 -0800 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 BAA21814 for ; Wed, 29 Mar 1995 01:43:54 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA25614; Wed, 29 Mar 1995 19:40:45 +1000 Date: Wed, 29 Mar 1995 19:40:45 +1000 From: Bruce Evans Message-Id: <199503290940.TAA25614@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, jdli@netbsd.csie.nctu.edu.tw Subject: Re: New slice code Sender: current-owner@FreeBSD.org Precedence: bulk > The new SNAP came with new slice code, does it improve anything? Is there a new SNAP? :-) The slice code went in immediately after the last one was released to avoid breaking the SNAP. > Does it mean that I can mount a DOS-extend partition ? Or even Yes. You could do that before by putting the offsets in the label. > I can install FreeBSD in extend partition like Linux ? This should work, except fdisk'ing and booting from such partitions is currently not supported. Bruce From owner-freebsd-current Wed Mar 29 02:47:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA10876 for current-outgoing; Wed, 29 Mar 1995 02:47:15 -0800 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 CAA10761 for ; Wed, 29 Mar 1995 02:46:59 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA19230; Wed, 29 Mar 95 12:46:13 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id MAA06397; Wed, 29 Mar 1995 12:51:53 +0200 Message-Id: <199503291051.MAA06397@gilberto.physik.rwth-aachen.de> Subject: Re: FreeBSD problems - VM bug? To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 29 Mar 1995 12:51:52 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com (user alias) In-Reply-To: <199503290841.KAA26101@uriah.heep.sax.de> from "J Wunsch" at Mar 29, 95 10:41:38 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1280 Sender: current-owner@FreeBSD.org Precedence: bulk > > As Christoph Kukulies wrote: > > > > > Oooops. Sorry, i meant 95*03*21. ! > > > I wouldn't trust that mix. I had all sorts of trouble when mixing > > a 950210 with later kernels. 950210-SNAP hadn't been very trustable. > > Did Martin upgrade to -current or do a full install from 950321-SNAP? > > Do the VM problems persist? > > The 950321 SNAP didn't appear yet on our ftp server (it's mirrored > across several hops). And my attempts to compile Martin a private > SNAP failed miserably due to the reported frequent NFS server hangs. > (I had to use an old SX/16 as an external disk in order to put all > the releases stuff there.) > > > I have a 386SX-16 8MB, IDE, (Morse board) and I'm running some 95 SNAP on > > it w/o problems. > > Even as a heavy-loaded NFS server? That's all where my box is failing, > everything else works fine. No, not as a NFS server. Would it help, if I send you a tape? > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ > Never trust an operating system you don't have sources for. ;-) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Mar 22 04:54:59 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Wed Mar 29 09:41:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA22669 for current-outgoing; Wed, 29 Mar 1995 09:41:44 -0800 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 JAA22663 for ; Wed, 29 Mar 1995 09:41:43 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id JAA08861; Wed, 29 Mar 1995 09:41:11 -0800 From: Poul-Henning Kamp Message-Id: <199503291741.JAA08861@ref.tfs.com> Subject: Re: New slice code To: jdli@netbsd.csie.nctu.edu.tw (¡¹ ¤p¤p¬P¥ú ¡¹) Date: Wed, 29 Mar 1995 09:41:11 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199503290901.RAA05966@netbsd.csie.nctu.edu.tw> from "¡¹ ¤p¤p¬P¥ú ¡¹" at Mar 29, 95 05:01:41 pm Content-Type: text Content-Length: 455 Sender: current-owner@FreeBSD.org Precedence: bulk > Hi : > > The new SNAP came with new slice code, does it improve anything? > Does it mean that I can mount a DOS-extend partition ? Or even > I can install FreeBSD in extend partition like Linux ? > The 950322 SNAP does not have the slice code. It improves A LOT! -- 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 Mar 29 09:53:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA23180 for current-outgoing; Wed, 29 Mar 1995 09:53:49 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA23170 for ; Wed, 29 Mar 1995 09:53:44 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id KAA15485 for current@FreeBSD.org; Wed, 29 Mar 1995 10:57:52 -0700 Date: Wed, 29 Mar 1995 10:57:52 -0700 From: Nate Williams Message-Id: <199503291757.KAA15485@trout.sri.MT.net> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: current@FreeBSD.org Subject: Kernel compile 'feature' of new SNAP Sender: current-owner@FreeBSD.org Precedence: bulk In the quest to make the kernel compile out of the source tree w/out using the system includes, we have made it more difficult (and confusing) for people who want to build custom kernels. A user send me email late last night complaining he couldn't build a kernel. Apparently it died during a make depend cause it couldn't find . Everything worked fine on my box, so I wan't sure why it didn't work until I looked at the Makefile. The line INCLUDES= -nostdinc makes it impossible for folks to do what they have always done, which is to download the kerndist and build a custom kernel. We either need to document this (a good idea), or change the default behavior to use the system includes. I prefer the latter since most folks who will build kernels are users and not developers, but I'm not the one making the decision. Would using an ENVIRONMENT variable be acceptable? Current: # Not ready for -I- yet. #include "foo.h" where foo.h is in the srcdir fails. INCLUDES= -nostdinc -I. -I$S -I$S/sys -I$S/../include Proposed # Not ready for -I- yet. #include "foo.h" where foo.h is in the srcdir fails. .if defined(SRC_INCLUDES) INCLUDES= -nostdinc -I$S/../include .endif INCLUDES+= -I. -I$S -I$S/sys What we did was remove the above parameters from the INCLDUES lines and everything worked fine. Nate From owner-freebsd-current Wed Mar 29 11:09:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26173 for current-outgoing; Wed, 29 Mar 1995 11:09:38 -0800 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26167 for ; Wed, 29 Mar 1995 11:09:32 -0800 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id NAA13518; Wed, 29 Mar 1995 13:09:07 -0600 Received: by olympus (4.1/TSS2.1) id AA10409; Wed, 29 Mar 95 13:07:32 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9503291907.AA10409@olympus> Subject: chflags should be compiled static To: current@FreeBSD.org Date: Wed, 29 Mar 1995 13:07:31 -0600 (CST) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 861 Sender: current-owner@FreeBSD.org Precedence: bulk I had a merry adventure. On a make world, I got a corrupted libc.so.2.1. Needless to say, the phrase ld.so failed became very familiar to me, very quickly. Unfortunately, libc.so.2.1 is installed with the schg option. I was unable to remove the offending library as I could not disable this option because chflags said ld.so failed. ld.so is similarly locked down. I managed to get around this by moving the directory and copying the needed libraries into the new /usr/lib. This should be avoided by making this tools static. Reasoning: If I have to use the tool to fix the library, the tool should not depend on the library. Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Wed Mar 29 11:24:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26679 for current-outgoing; Wed, 29 Mar 1995 11:24:26 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26669 for ; Wed, 29 Mar 1995 11:24:21 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id MAA00344; Wed, 29 Mar 1995 12:28:23 -0700 Date: Wed, 29 Mar 1995 12:28:23 -0700 From: Nate Williams Message-Id: <199503291928.MAA00344@trout.sri.MT.net> In-Reply-To: faulkner@mpd.tandem.com (Boyd Faulkner) "chflags should be compiled static" (Mar 29, 1:07pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: faulkner@mpd.tandem.com (Boyd Faulkner), current@FreeBSD.org Subject: Re: chflags should be compiled static Sender: current-owner@FreeBSD.org Precedence: bulk > Reasoning: If I have to use the tool to fix the library, the tool should > not depend on the library. Agreed. I'd even go so far as to say that it should go into /sbin. [ Donning my asbestos underware for the flame fest to follow ] Nate From owner-freebsd-current Wed Mar 29 11:25:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26745 for current-outgoing; Wed, 29 Mar 1995 11:25:23 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26738 for ; Wed, 29 Mar 1995 11:25:19 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id OAA19211 for freebsd-current@freefall.cdrom.com; Wed, 29 Mar 1995 14:25:08 -0500 From: John Capo Message-Id: <199503291925.OAA19211@irbs.com> Subject: warning: `SDUNIT' redefined To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Wed, 29 Mar 1995 14:25:07 -0500 (EST) Reply-To: jc@irbs.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 343 Sender: current-owner@FreeBSD.org Precedence: bulk This has been around for several days. The result appears to be the same. ../../scsi/sd.c:58: warning: `SDUNIT' redefined ../../scsi/sd.c:54: warning: this is the location of the previous definition ../../scsi/sd.c:62: warning: `SDSETUNIT' redefined ../../scsi/sd.c:55: warning: this is the location of the previous definition -- John Capo From owner-freebsd-current Wed Mar 29 11:28:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26837 for current-outgoing; Wed, 29 Mar 1995 11:28:43 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26819 for ; Wed, 29 Mar 1995 11:28:38 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id OAA19400 for freebsd-current@freefall.cdrom.com; Wed, 29 Mar 1995 14:28:25 -0500 From: John Capo Message-Id: <199503291928.OAA19400@irbs.com> Subject: Re: chflags should be compiled static To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Wed, 29 Mar 1995 14:28:24 -0500 (EST) In-Reply-To: <9503291907.AA10409@olympus> from "Boyd Faulkner" at Mar 29, 95 01:07:31 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: 768 Sender: current-owner@FreeBSD.org Precedence: bulk Boyd Faulkner writes: > > I had a merry adventure. On a make world, I got a corrupted libc.so.2.1. > Needless to say, the phrase ld.so failed became very familiar to me, very > quickly. > > Unfortunately, libc.so.2.1 is installed with the schg option. I was unable > to remove the offending library as I could not disable this option because > chflags said ld.so failed. ld.so is similarly locked down. I managed > to get around this by moving the directory and copying the needed libraries > into the new /usr/lib. This should be avoided by making this tools static. > Reasoning: If I have to use the tool to fix the library, the tool should > not depend on the library. And put it in /sbin or /bin please. I recently did similar handstands. -- John Capo From owner-freebsd-current Wed Mar 29 11:48:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA27401 for current-outgoing; Wed, 29 Mar 1995 11:48:40 -0800 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 LAA27394 for ; Wed, 29 Mar 1995 11:48:35 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA11057; Thu, 30 Mar 1995 05:47:20 +1000 Date: Thu, 30 Mar 1995 05:47:20 +1000 From: Bruce Evans Message-Id: <199503291947.FAA11057@godzilla.zeta.org.au> To: current@FreeBSD.org, nate@trout.sri.MT.net Subject: Re: Kernel compile 'feature' of new SNAP Sender: current-owner@FreeBSD.org Precedence: bulk >In the quest to make the kernel compile out of the source tree w/out >using the system includes, we have made it more difficult (and >confusing) for people who want to build custom kernels. A user send me >... >Would using an ENVIRONMENT variable be acceptable? No. >Current: ># Not ready for -I- yet. #include "foo.h" where foo.h is in the srcdir fails. >INCLUDES= -nostdinc -I. -I$S -I$S/sys -I$S/../include Adding -I/usr/include to the end should be good enough. It will only do the wrong thing for people who who have populated $S/../include but forgot. Bruce From owner-freebsd-current Wed Mar 29 12:01:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27628 for current-outgoing; Wed, 29 Mar 1995 12:01:57 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA27622 for ; Wed, 29 Mar 1995 12:01:53 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id NAA00511; Wed, 29 Mar 1995 13:05:47 -0700 Date: Wed, 29 Mar 1995 13:05:47 -0700 From: Nate Williams Message-Id: <199503292005.NAA00511@trout.sri.MT.net> In-Reply-To: Bruce Evans "Re: Kernel compile 'feature' of new SNAP" (Mar 30, 5:47am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans , current@FreeBSD.org Subject: Re: Kernel compile 'feature' of new SNAP Sender: current-owner@FreeBSD.org Precedence: bulk [ Kernel compiles fail if the user doesn't have the /usr/src/include tree installed. ] > Adding -I/usr/include to the end should be good enough. It will only do > the wrong thing for people who who have populated $S/../include but > forgot. Are you implying that they may have a /usr/src/include tree that's out of sync with /usr/src/sys and which would screw up the kernel compile because of the addition of -I/usr/include? Nate ps. I think the solution Bruce proposes is workable, and if no one objects I'd like to see it committed. From owner-freebsd-current Wed Mar 29 12:29:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28237 for current-outgoing; Wed, 29 Mar 1995 12:29:33 -0800 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 MAA28229 for ; Wed, 29 Mar 1995 12:29:26 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA12289; Thu, 30 Mar 1995 06:23:40 +1000 Date: Thu, 30 Mar 1995 06:23:40 +1000 From: Bruce Evans Message-Id: <199503292023.GAA12289@godzilla.zeta.org.au> To: bde@zeta.org.au, current@FreeBSD.org, nate@trout.sri.MT.net Subject: Re: Kernel compile 'feature' of new SNAP Sender: current-owner@FreeBSD.org Precedence: bulk >> Adding -I/usr/include to the end should be good enough. It will only do >> the wrong thing for people who who have populated $S/../include but >> forgot. >Are you implying that they may have a /usr/src/include tree that's out >of sync with /usr/src/sys and which would screw up the kernel compile >because of the addition of -I/usr/include? Unlikely, but who knows. Actually, genassym should be built with the host includes for at least . It runs on the host. I thought genassym was neat when I first saw it, but it is bad for cross-compiling. Bruce From owner-freebsd-current Wed Mar 29 12:34:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28352 for current-outgoing; Wed, 29 Mar 1995 12:34:30 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA28339 for ; Wed, 29 Mar 1995 12:34:27 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id PAA00517; Wed, 29 Mar 1995 15:12:04 -0500 From: Peter Dufault Message-Id: <199503292012.PAA00517@hda.com> Subject: Re: warning: `SDUNIT' redefined To: jc@irbs.com Date: Wed, 29 Mar 1995 15:12:03 -0500 (EST) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199503291925.OAA19211@irbs.com> from "John Capo" at Mar 29, 95 02:25:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 742 Sender: current-owner@FreeBSD.org Precedence: bulk John Capo writes: > > This has been around for several days. The result appears to be > the same. > > ../../scsi/sd.c:58: warning: `SDUNIT' redefined > ../../scsi/sd.c:54: warning: this is the location of the previous definition > ../../scsi/sd.c:62: warning: `SDSETUNIT' redefined > ../../scsi/sd.c:55: warning: this is the location of the previous definition > Yes, I have that fixed locally but it will be a few days before I move in the new code. Anyone really annoyed can rip out the old definitions and keep Bruce's. If you can wait a few more days I'll do it. -- 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 Wed Mar 29 17:18:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA10972 for current-outgoing; Wed, 29 Mar 1995 17:18:55 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA10965; Wed, 29 Mar 1995 17:18:54 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: se@freefall.cdrom.com cc: current@freefall.cdrom.com Subject: NCR failure described in more detail. Date: Wed, 29 Mar 1995 17:18:53 -0800 Message-ID: <10964.796526333@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk Ok, here's the message I get when I first select "Install" from the 950322-SNAP boot floppy: assertion: cp == np->header.cp failed: file "../../pci/ncr.c" line 5243 ncr0 targ 6?: ERROR (80:100) (e-29-0) (8/13) @ (10d4:e000000). reg: da 10 0 13 47 8 6 1f 0 e 86 29 80 1 1 0. ncr0: restart (fatal error) ... I've tried the NCR controller at IRQ 9 (where it was by default) and then at IRQ 11 when I noticed that it was at the evil 2/9 IRQ. Same problem in both cases. Does this give you any clues? Motherboard is P5/90 OPTI chipset with an AMI bios (the really gross graphical one that uses the mouse! :-). Jordan From owner-freebsd-current Wed Mar 29 18:40:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA11873 for current-outgoing; Wed, 29 Mar 1995 18:40:08 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA11866; Wed, 29 Mar 1995 18:40:07 -0800 Message-Id: <199503300240.SAA11866@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: se@freefall.cdrom.com, current@freefall.cdrom.com, jmacd@freefall.cdrom.com Subject: Re: NCR failure described in more detail. In-reply-to: Your message of "Wed, 29 Mar 95 17:18:53 PST." <10964.796526333@freefall.cdrom.com> Date: Wed, 29 Mar 1995 18:40:06 -0800 From: Joshua Peck Macdonald Sender: current-owner@FreeBSD.org Precedence: bulk I have that same setup!!!! It sucks!!!!!! I finally ended up with my NCR on irq 12. Get a new motherboard get a new motherboard get a new motherboard. I have to remove my serial card in order to set up the BIOS because otherwise the mouse driven-ness is so broken that I can't do anything. I'd appreciate knowing whats up though, too, because my computer failed to install the 3-22 SNAP also. -josh From owner-freebsd-current Wed Mar 29 22:05:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA15945 for current-outgoing; Wed, 29 Mar 1995 22:05:37 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA15938 for current; Wed, 29 Mar 1995 22:05:36 -0800 Date: Wed, 29 Mar 1995 22:05:36 -0800 From: "Jordan K. Hubbard" Message-Id: <199503300605.WAA15938@freefall.cdrom.com> To: current Subject: dlopen() and Garrett's comments on fn pointers! Sender: current-owner@FreeBSD.org Precedence: bulk In case no one has noticed, the dlsym() routine returns a void* for both function and data pointers! :-) Jordan From owner-freebsd-current Thu Mar 30 01:16:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA20452 for current-outgoing; Thu, 30 Mar 1995 01:16:51 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA20385 for ; Thu, 30 Mar 1995 01:16:25 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id BAA09241; Fri, 31 Mar 1995 01:15:52 +0800 Date: Thu, 30 Mar 1995 17:15:49 +0000 () From: Brian Tao To: Nate Williams cc: current@FreeBSD.org Subject: Re: Kernel compile 'feature' of new SNAP In-Reply-To: <199503291757.KAA15485@trout.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Wed, 29 Mar 1995, Nate Williams wrote: > > In the quest to make the kernel compile out of the source tree w/out > using the system includes, we have made it more difficult (and > confusing) for people who want to build custom kernels. A user send me > email late last night complaining he couldn't build a kernel. > Apparently it died during a make depend cause it couldn't find . All I did was mv /usr/src/sys up to /usr/sys for the compile so that the relative path ../../include/stdio.h found /usr/include. Kernel compiled without any complaints and it seems to work fine for me. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Thu Mar 30 07:30:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA00378 for current-outgoing; Thu, 30 Mar 1995 07:30:49 -0800 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 HAA00372; Thu, 30 Mar 1995 07:30:46 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA16296; Thu, 30 Mar 1995 10:30:26 -0500 Date: Thu, 30 Mar 1995 10:30:26 -0500 From: Garrett Wollman Message-Id: <9503301530.AA16296@halloran-eldar.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: current@freefall.cdrom.com Subject: dlopen() and Garrett's comments on fn pointers! In-Reply-To: <199503300605.WAA15938@freefall.cdrom.com> References: <199503300605.WAA15938@freefall.cdrom.com> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > In case no one has noticed, the dlsym() routine returns a void* for > both function and data pointers! :-) Yup. You have to take an intermediate step through a large-enough integer (like unsigned long) in order to do it without diagnostics. (The result is still implementation-defined.) -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 Thu Mar 30 08:17:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA02001 for current-outgoing; Thu, 30 Mar 1995 08:17:28 -0800 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA01995 for ; Thu, 30 Mar 1995 08:17:26 -0800 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id KAA24204; Thu, 30 Mar 1995 10:16:57 -0600 Received: by olympus (4.1/TSS2.1) id AA12267; Thu, 30 Mar 95 10:15:22 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9503301615.AA12267@olympus> Subject: as will not compile for me. To: current@FreeBSD.org Date: Thu, 30 Mar 1995 10:15:21 -0600 (CST) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 3753 Sender: current-owner@FreeBSD.org Precedence: bulk I cannot get current "as" to compile. Everything else did and is installed. I blew away the "as" source and resupped in case I had bad files. Here is a sample. [root@catburg] /usr/src/gnu/usr.bin/as > make cc -O2 -DNON_BROKEN_WORDS -DPIC -I/usr/src/gnu/usr.bin/as -I/usr/src/gnu/usr.bin/as/obj -I/usr/src/gnu/usr.bin/as/config -DOLD_GAS -DSIGTY=void -Derror=as_fatal -DSUB_SEGMENT_ALIGN=4 -DFREEBSD_AOUT -c /usr/src/gnu/usr.bin/as/config/tc-i386.c In file included from /usr/src/gnu/usr.bin/as/as.h:404, from /usr/src/gnu/usr.bin/as/config/tc-i386.c:31: /usr/src/gnu/usr.bin/as/struc-symbol.h:29: parse error before `obj_symbol_type' /usr/src/gnu/usr.bin/as/struc-symbol.h:29: warning: no semicolon at end of struct or union /usr/src/gnu/usr.bin/as/struc-symbol.h:56: parse error before `}' In file included from /usr/src/gnu/usr.bin/as/as.h:405, from /usr/src/gnu/usr.bin/as/config/tc-i386.c:31: /usr/src/gnu/usr.bin/as/write.h:64: field `fx_r_type' has incomplete type /usr/src/gnu/usr.bin/as/write.h:98: warning: parameter has incomplete type In file included from /usr/src/gnu/usr.bin/as/as.h:412, from /usr/src/gnu/usr.bin/as/config/tc-i386.c:31: /usr/src/gnu/usr.bin/as/tc.h:61: parse error before `*' /usr/src/gnu/usr.bin/as/tc.h:69: parse error before `*' /usr/src/gnu/usr.bin/as/tc.h:73: parse error before `*' In file included from /usr/src/gnu/usr.bin/as/as.h:413, from /usr/src/gnu/usr.bin/as/config/tc-i386.c:31: /usr/src/gnu/usr.bin/as/obj.h:29: parse error before `*' /usr/src/gnu/usr.bin/as/obj.h:33: parse error before `object_headers' /usr/src/gnu/usr.bin/as/obj.h:43: parse error before `*' In file included from /usr/src/gnu/usr.bin/as/config/tc-i386.c:34: /usr/src/gnu/usr.bin/as/opcode/i386.h:22: parse error before `i386_optab' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: braces around scalar initializer for `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: initialization makes integer from pointer without a cast /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: `None' undeclared here (not in a function) /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: `DW' undeclared here (not in a function) /usr/src/gnu/usr.bin/as/opcode/i386.h:26: `NoModrm' undeclared here (not in a function) /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: `Disp32' undeclared here (not in a function) /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: `Acc' undeclared here (not in a function) /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:26: warning: excess elements in scalar initializer after `i386_optab[0]' /usr/src/gnu/usr.bin/as/opcode/i386.h:27: warning: braces around scalar initializer for `i386_optab[1]' /usr/src/gnu/usr.bin/as/opcode/i386.h:27: warning: initialization makes integer from pointer without a cast etc... every line of opcode/i386.h draws a complaint. What gives? Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Thu Mar 30 12:00:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07261 for current-outgoing; Thu, 30 Mar 1995 12:00:23 -0800 Received: from main.statsci.com (main.statsci.com [198.145.125.110]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA07255 for ; Thu, 30 Mar 1995 12:00:21 -0800 Received: by main.statsci.com (Smail3.1.28.1 #9) id m0ruQNw-000r3tC; Thu, 30 Mar 95 12:00 PST Message-Id: To: freebsd-current@FreeBSD.org Subject: 2.0-950322-SNAP installation problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 1995 12:00:59 -0800 From: Scott Blachowicz Sender: current-owner@FreeBSD.org Precedence: bulk Hi- I just pulled down the 950322-SNAP tree to use as my first attempt at installing FreeBSD on my home system. That system is: Pentium-90; 16 Mb RAM; 256K cache CAF Tech motherboard / SiS chipset / Award 4.50G BIOS PCI IDE - boot disk NCR 8150S PCI SCSI - Toshiba 3501 CDROM, Exabyte EXB-8200 8mm drive ATI Mach64 (2Mb)/17" display Sound Blaster AWE32 network card (can "be" NE2000 among other personalities) floppy/2S/1P/game card one 3.5" floppy drive; no 5.25" floppy drive I've tried using both RAWRITE & RAWRITE3 from the tools/dos-tools directory to put a gunzip'd boot.flp.gz onto a 3.5" diskette, then boot from that. My first attempt (with RAWRITE) ended up having my boot process completely ignore the inserted diskette. My 2nd & 3rd attempts using RAWRITE3 ended up just sitting there spinning the diskette drive for a while before I came back and tried CTRL-ALT-DEL with no results and the RESET button. I then pulled the boot floppy out. The reboot sequence got to the point where I think it normally scans the system & spits out the NCR SDMS BIOS banner (from my NCR 8150S card) and just hung. I power cycled and got the same hang. I then turned the system off for a while (hours) and turned it back on - it came up fine. So, does anyone have any idea 1) what I'm doing wrong? 2) how I can do it right? 3) what the heck is happening here? Thanx! Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc. 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org From owner-freebsd-current Thu Mar 30 13:48:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA11150 for current-outgoing; Thu, 30 Mar 1995 13:48:36 -0800 Received: from palmer.demon.co.uk (root@palmer.demon.co.uk [158.152.50.150]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA11144 for ; Thu, 30 Mar 1995 13:48:16 -0800 Received: from localhost (gary@localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.9/8.6.9) with SMTP id WAA03742 for ; Thu, 30 Mar 1995 22:47:23 +0100 X-Authentication-Warning: palmer.demon.co.uk: Host localhost didn't use HELO protocol To: FreeBSD-Current Subject: man ppp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3738.796600040.1@palmer.demon.co.uk> Date: Thu, 30 Mar 1995 22:47:21 +0100 Message-ID: <3739.796600041@palmer.demon.co.uk> From: Gary Palmer Sender: current-owner@FreeBSD.org Precedence: bulk Someone want to delve into this man page and tidy it up? The english is kinda convoluted in places and (for me anyhow) difficult to follow! In places I wouldn't even dare to try to re-write it as I dunno what's meant! Gary From owner-freebsd-current Thu Mar 30 16:41:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA04489 for current-outgoing; Thu, 30 Mar 1995 16:41:31 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA04483; Thu, 30 Mar 1995 16:41:30 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id QAA00401; Thu, 30 Mar 1995 16:41:29 -0800 Message-Id: <199503310041.QAA00401@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org cc: wollman@FreeBSD.org Subject: rfc 1323 Support Date: Thu, 30 Mar 1995 16:41:29 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk David just uncovered the problem that has prevented me from talking to other -current machines from behind my slip connection. It seems that either the VJ header compression implementation in FreeBSD or that of the annex I use is not up to snuff with rfc 1323. The cure to all of my problems was to do a: sysctl -w net.inet.tcp.rfc1323=0 I will be talking to the annex gods here at Cal to see what they have to say about this, but even if it is an annex problem not a FreeBSD SLIP problem, should this stuff be enabled by default? __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Thu Mar 30 17:20:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA07840 for current-outgoing; Thu, 30 Mar 1995 17:20:04 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA07828 for ; Thu, 30 Mar 1995 17:20:02 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id RAA00586; Thu, 30 Mar 1995 17:20:01 -0800 Message-Id: <199503310120.RAA00586@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org cc: temp@temptation.interlog.com Subject: D-Link support? Date: Thu, 30 Mar 1995 17:20:00 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk Is there any work being done on either of these two cards? ------- Forwarded Message From: Temptation Subject: Re: SMC and D-Link support? To: "Justin T. Gibbs" In-Reply-To: <199503310035.QAA00332@estienne.cs.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > What chipset is on the card? It might be supported by another driver, or > there may be work in progres on it. One chip is Sonic, and the other is PLX tehnology inc. A NE3200 compt. card should work. there is one in the linux code, but it seems to only support 1000-A000 which this card doesn't support, it's up in the C000-E000 range. I tried going thro the code, but I couldn't find where they are setting the address. ------ End Forwarded Message From owner-freebsd-current Thu Mar 30 18:03:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA09706 for current-outgoing; Thu, 30 Mar 1995 18:03:05 -0800 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 SAA09700 for ; Thu, 30 Mar 1995 18:03:04 -0800 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14623(4)>; Thu, 30 Mar 1995 18:02:21 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <49864>; Thu, 30 Mar 1995 18:02:12 -0800 X-Mailer: exmh version 1.6gamma- 3/28/95 To: Stephen McKay cc: Mark Murray , Poul-Henning Kamp , freebsd-current@FreeBSD.org Subject: Re: To all the ctm'mers... In-reply-to: Your message of "Tue, 28 Mar 95 18:36:32 PST." <199503290236.MAA29753@orion.devetir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 1995 18:02:05 PST From: Bill Fenner Message-Id: <95Mar30.180212pst.49864@crevenia.parc.xerox.com> Sender: current-owner@FreeBSD.org Precedence: bulk In message <199503290236.MAA29753@orion.devetir.qld.gov.au> you write: >So, translating, someone like yourself could use an entry in /etc/aliases: > > ctm-cvs-cur: "| /foo/bar/ctm_incoming" > >and have /foo/bar/ctm_incoming contain something like: > > #! /bin/sh > PATH="your favourite path" > export PATH > cd /place/for/goodies || exit 1 This is one of my biggest pet peeves. Do people actually *like* seeing "Returned mail: unknown mailer error 1"? For this particular case, I would suggest "exit 72", "Critical OS file missing", or perhaps "exit 69", "Service Unavailable". (/usr/include/sys/sysexits.h) (the majordomo wrapper used to just exit(1), exit(2),... for impossible conditions. Impossible conditions happen all the time, everywhere around the world...) Bill From owner-freebsd-current Fri Mar 31 00:08:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA27703 for current-outgoing; Fri, 31 Mar 1995 00:08:28 -0800 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA27667; Fri, 31 Mar 1995 00:08:22 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.11/8.6.11) id BAA28573; Fri, 31 Mar 1995 01:10:02 -0700 Message-Id: <199503310810.BAA28573@rocky.sri.MT.net> From: Nate Williams Date: Fri, 31 Mar 1995 01:10:02 -0700 In-Reply-To: "Nate Williams" "cvs commit: src/gnu/usr.bin Makefile" (Mar 31, 0:00) Reply-To: Nate Williams X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: CVS-commiters@freefall.cdrom.com Subject: Announce: New Version of CVS ( was Re: cvs commit: src/gnu/usr.bin Makefile) Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > nate 95/03/31 00:00:07 > > Modified: gnu/usr.bin Makefile > Log: > Temporarily disable building CVS to avoid anyone hosing up their CVS > tree until a bit more testing is done. > > Submitted by: rgrimes@gndrsh.aac.dev.com "Rod Grimes" Rod asked me to disable the build of CVS until we test the bits a bit more, but it does compile and my testing have been positive. If you want to risk it go ahead and build/install it. However, since CVS is critical to many folks, he felt it would be unsafe to have folks use the new binary until it was beat on a bit more. On that note, J.T. Conklin has done alot of work in making this version of CVS *much* faster on 4.4BSD derived systems. Also, he has made some additional speedups that I will be putting in CVS after 2.1 which speed it up even more. Since CVS is such a big bottleneck for all of our operations, I felt getting a faster version of CVS certainly couldn't hurt. If you can, please test this out on your machines. I don't forsee any problems whatsoever, but it's better to be safe than sorry. I'd like to see freefall get updated binaries in the next couple weeks. Nate From owner-freebsd-current Fri Mar 31 00:13:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA28827 for current-outgoing; Fri, 31 Mar 1995 00:13:46 -0800 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA28815 for ; Fri, 31 Mar 1995 00:13:44 -0800 Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB) id AA24012; Fri, 31 Mar 1995 10:13:33 --100 Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1) id AA00934; Fri, 31 Mar 95 10:13:25 +0200 To: current@FreeBSD.org Subject: Re: rfc 1323 Support In-Reply-To: Your message of Thu, 30 Mar 1995 16:41:29 -0800 Date: Fri, 31 Mar 1995 10:13:24 +0200 Message-Id: <933.796637604@utis156.cs.utwente.nl> From: Andras Olah content-length: 860 Sender: current-owner@FreeBSD.org Precedence: bulk On Thu, 30 Mar 1995 16:41:29 -0800, "Justin T. Gibbs" wrote: > David just uncovered the problem that has prevented me from talking to > other -current machines from behind my slip connection. It seems that > either the VJ header compression implementation in FreeBSD or that of > the annex I use is not up to snuff with rfc 1323. The cure to all > of my problems was to do a: > > sysctl -w net.inet.tcp.rfc1323=0 > > I will be talking to the annex gods here at Cal to see what they have to > say about this, but even if it is an annex problem not a FreeBSD SLIP > problem, should this stuff be enabled by default? This problem has just recently been discussed on comp.unix.bsd under the subject line: `BSD newtworking kills terminal server !' A posting from Michael L. VanLoon indicated that he already got a patch for a Xyplex terminal server. Andras From owner-freebsd-current Fri Mar 31 00:26:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA01369 for current-outgoing; Fri, 31 Mar 1995 00:26:05 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA01362 for ; Fri, 31 Mar 1995 00:26:05 -0800 Received: (from jkh@localhost) by time.cdrom.com (8.6.11/8.6.9) id AAA03683 for current; Fri, 31 Mar 1995 00:26:03 -0800 Date: Fri, 31 Mar 1995 00:26:03 -0800 From: "Jordan K. Hubbard" Message-Id: <199503310826.AAA03683@time.cdrom.com> To: current@FreeBSD.org Subject: Compiling LINT Sender: current-owner@FreeBSD.org Precedence: bulk Error 1: 128 -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 ../../net/if_fddisubr.c ../../net/if_fddisubr.c: In function `fddi_input': ../../net/if_fddisubr.c:486: `ac' undeclared (first use this function) ../../net/if_fddisubr.c:486: (Each undeclared identifier is reported only once ../../net/if_fddisubr.c:486: for each function it appears in.) ../../net/if_fddisubr.c:487: `eh' undeclared (first use this function) Error 2: ../../i386/isa/cx.c: In function `cxrinta': ../../i386/isa/cx.c:788: `RISA_OVERRUN' undeclared (first use this function) ../../i386/isa/cx.c:788: (Each undeclared identifier is reported only once ../../i386/isa/cx.c:788: for each function it appears in.) Errors in make all: ent -Wredundant-decls -DPSEUDO_LKM -c /usr/src/lkm/if_sl/../../sys/net/if_sl.c /usr/src/lkm/if_sl/../../sys/net/if_sl.c: In function `sl_outfill': /usr/src/lkm/if_sl/../../sys/net/if_sl.c:979: structure has no member named `t_out' Foo. Jordan From owner-freebsd-current Fri Mar 31 01:35:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA10121 for current-outgoing; Fri, 31 Mar 1995 01:35:44 -0800 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 BAA10114 for ; Fri, 31 Mar 1995 01:35:40 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.11/jtpda-5.0) with SMTP id LAA02906 ; Fri, 31 Mar 1995 11:36:02 +0200 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA19006; Fri, 31 Mar 95 11:35:31 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <9503310935.AA19006@blaise.ibp.fr> Subject: Re: Announce: New Version of CVS ( was Re: cvs commit: src/gnu/usr.bin Makefile) To: nate@sneezy.sri.com Date: Fri, 31 Mar 1995 11:35:31 +0200 (MET DST) Cc: current@FreeBSD.org (Current's list FreeBSD) In-Reply-To: <199503310810.BAA28573@rocky.sri.MT.net> from "Nate Williams" at Mar 31, 95 01:10:02 am X-Operating-System: FreeBSD 2.1.0-Development ctm#480 X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 526 Sender: current-owner@FreeBSD.org Precedence: bulk > If you can, please test this out on your machines. I don't forsee any > problems whatsoever, but it's better to be safe than sorry. I'd like to > see freefall get updated binaries in the next couple weeks. > I'm using it on my machine for at least one month and I' didn't have any problem with it. Seems faster even without J.T. Conklin improvements I saw on the cvs list. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #7: Thu Mar 23 00:28:31 MET 1995 From owner-freebsd-current Fri Mar 31 03:07:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA14004 for current-outgoing; Fri, 31 Mar 1995 03:07:28 -0800 Received: from easynet.com (easyr.easynet.net [198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA13995 for ; Fri, 31 Mar 1995 03:07:24 -0800 Received: by easynet.com (Smail3.1.28.1 #7) id m0rueOZ-000rccC; Fri, 31 Mar 95 02:57 WET Message-Id: From: brian@mediacity.com (Brian Litzinger) Subject: cyb2.0bf To: freebsd-current@FreeBSD.org Date: Fri, 31 Mar 1995 02:57:38 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 40769 Sender: current-owner@FreeBSD.org Precedence: bulk Following is a modified version of the cyb driver which includes: ttyinput speedups for raw input increased the fifo interrupt point a little updated to 2.1.0-Development scheme Brian Litzinger brian@easynet.com # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # readme.src # cybreg.h # cl-cd1400.h # cyb.c # echo x - readme.src sed 's/^X//' >readme.src << 'END-of-readme.src' XCyclades Cyclom 8Y/8Yo/16Y driver for FreeBSD 2.1.0-Development X XBy Brian E. Litzinger X XCopyright 1995 By Brian E. Litzinger X X-------------------------------------------------------------------- X XYou must reverse the sense of RTS and DTR in the Cyclades manual! X XThis driver reverses their usage to correctly implement full duplex Xhardware handshaking. X XWhich means, there is no DTR on the 8Y RJ12 connector. The DTR pin Xin the manual becomes RTS. DTR does exist in the 16Y and the 8Yo. X XIn your i386/conf/LOCAL or whatever file you must add the following lines: Xand you should make sure the fields match what you set on the board. X Xdevice cyb0 at isa? tty irq 15 iomem 0xd8000 iosiz 8192 vector cybintr X XAdd this near the end of i386/conf/files.i386: X Xi386/isa/cyb.c optional cyb device-driver X Xsomewhere in i386/i386/conf.c add: X X#include "cyb.h" X#if NCYB > 0 Xd_open_t cybopen; Xd_close_t cybclose; Xd_ioctl_t cybioctl; Xd_rdwr_t cybread, cybwrite; Xd_select_t cybselect; Xd_stop_t cybstop; Xd_ttycv_t cybdevtotty; X#define cybreset nxreset X#define cybmmap nxmmap X#define cybstrategy nxstrategy X#else X#define cybopen (d_open_t *)enxio X#define cybclose (d_close_t *)enxio X#define cybioctl (d_ioctl_t *)enxio X#define cybread (d_rdwr_t *)enxio X#define cybwrite (d_rdwr_t *)enxio X#define cybselect (d_select_t *)enxio X#define cybstop (d_stop_t *)enxio X#define cybdevtotty nxdevtotty X#define cybreset nxreset X#define cybmmap nxmmap X#define cybstrategy nxstrategy X#endif X Xthen in i386/i386/conf.c add to the cdevsw structure X X { cybopen, cybclose, cybread, cybwrite, /*48*/ X cybioctl, cybstop, cybreset, cybdevtotty, /* cyb */ X ttselect, cybmmap, cybstrategy }, X XYou may want to replace the existing /*48*/ with this one, or you might Xwant to put it in the local /*20*/ spot. X XLastly, put cyb.c, and the *.h files in i386/isa X XThen do a config and make depend and make and install and boot the new Xkernel. X XYou should see the following in the boot text or from dmesg: X Xcy returned 46 Xcy returned 46 Xcy returned 46 Xcy returned 46 Xcyb at 0x0 irq 15 maddr 0xd0000 msize 8192 X ports 16 X XAssuming you have 16Y so configured. X XNow go to the /dev directory and mknod the devices: X Xmknod ttyi0 c 48 0 0 # remember, major # may be different Xmknod ttyi1 c 48 0 1 X... X XYou also need to set the permissions appropriately: XFor bidir operations that would probably be: uucp:wheel XFor normal ops that would probably be: root:????? X XBest of luck. X XBrian Litzinger XP.O. Box 82 XBoulder Creek, CA 95006 END-of-readme.src echo x - cybreg.h sed 's/^X//' >cybreg.h << 'END-of-cybreg.h' X/*- X * Copyright (c) 1994 By Brian E. Litzinger, All rights reserved. X */ X X/* X * Definitions for Cyclades 8Y and 16Y Cyclom cards. X */ X X X/* X * Address mapping between Cirrus Logic CD1400 chip internal registers X * and ISA port addresses: X * X */ X#define CY_ADDR(reg) (reg) X X/* Input Byte from CL CD1400 register */ X#define rinb(base, reg) (*((base)+CY_ADDR(reg))) X X/* Output Byte to CL CD1400 register */ X#define routb(base, reg, val) (*((base)+CY_ADDR(reg))=val) X X#define CY_NPORT 16 /* decoder recognizes 16 addresses... */ X X#define CD1400_MEMSIZE 0x400 X#define cy_RESET_16 0x1400 /* cyclom-16y reset */ X#define cy_CLEAR_INTR 0x1800 /* intr ack address */ X#define CYCLOM_CLOCK 25000000 /* baud rate clock */ X#define CD1400_CLOCK_25_1MS 0x31 X#define CD1400_NO_OF_CHANNELS 4 X#define CD1400_MAX_FIFO_SIZE 12 X X END-of-cybreg.h echo x - cl-cd1400.h sed 's/^X//' >cl-cd1400.h << 'END-of-cl-cd1400.h' X/*- X * Copyright (c) 1994 By Brian E. Litzinger, All rights reserved. X */ X X/* X * Definitions for Cirrus Logic CL-CD1400 4-port async mux chip X */ X X#define CD1400_NCHAN 4 /* Total number of channels */ X#define CD1400_TPC 16 /* Ticks per character */ X X/* X * Global Registers X */ X#define CD1400_GFRCR 2*0x40 /* global firmware revision code */ X#define CD1400_CAR 2*0x68 /* channel access */ X#define CD1400_GCR 2*0x4b /* global config */ X#define CD1400_SVRR 2*0x67 /* service request */ X#define CD1400_RICR 2*0x44 /* receive intr channel */ X#define CD1400_TICR 2*0x45 /* transmit intr channel */ X#define CD1400_MICR 2*0x46 /* modem intr channel */ X#define CD1400_RIR 2*0x6B /* receive interrupt status */ X#define CD1400_TIR 2*0x6A /* transmit interrupt status */ X#define CD1400_MIR 2*0x69 /* modem interrupt status */ X#define CD1400_PPR 2*0x7e X X/* X Virtual Registers X*/ X#define CD1400_RIVR 2*0x43 /* receive intr vector */ X#define CD1400_TIVR 2*0x42 /* transmit intr vector */ X#define CD1400_MIVR 2*0x41 /* modem intr vector */ X#define CD1400_LIVR 2*0x18 /* local intr vector */ X#define CD1400_TDR 2*0x63 /* tx data */ X#define CD1400_RDSR 2*0x62 /* rx data/status */ X#define CD1400_MISR 2*0x4c /* modem intr status */ X#define CD1400_EOSRR 2*0x60 /* end of service request */ X X X X/* X * Channel Registers X */ X#define CD1400_LIVR 2*0x18 /* local intr vector */ X#define CD1400_CCR 2*0x05 /* channel control */ X#define CD1400_SRER 2*0x06 /* service request enable */ X#define CD1400_COR1 2*0x08 /* channel option 1 */ X#define CD1400_COR2 2*0x09 /* channel option 2 */ X#define CD1400_COR3 2*0x0A /* channel option 3 */ X#define CD1400_COR4 2*0x1E /* channel option 4 */ X#define CD1400_COR5 2*0x1F /* channel option 5 */ X#define CD1400_CCSR 2*0x0b /* channel control status */ X#define CD1400_RDCR 2*0x0e /* rx data count */ X#define CD1400_SCHR1 2*0x1A /* special character 1 */ X#define CD1400_SCHR2 2*0x1B /* special character 2 */ X#define CD1400_SCHR3 2*0x1C /* special character 3 */ X#define CD1400_SCHR4 2*0x1D /* special character 4 */ X#define CD1400_SCRL 2*0x22 /* special char range, low */ X#define CD1400_SCRH 2*0x23 /* special char range, high */ X#define CD1400_LNC 2*0x24 /* LNext character */ X#define CD1400_MCOR1 2*0x15 /* modem change 1 */ X#define CD1400_MCOR2 2*0x16 /* modem change 2 */ X#define CD1400_RTPR 2*0x21 /* receive timeout period */ X#define CD1400_MSVR1 2*0x6c /* modem signals */ X#define CD1400_MSVR2 2*0x6d /* modem signals */ X X#define CD1400_RBPR 2*0x78 /* receive baud rate period */ X#define CD1400_RCOR 2*0x7C /* receive clock option */ X#define CD1400_TBPR 2*0x72 /* transmit baud rate period */ X#define CD1400_TCOR 2*0x76 /* transmit clock option */ X X/* X * Channel Address Register X */ X#define CAR_CHAN 0x7 /* Channel Number Mask */ X X/* X * Channel Command Register X * (commands in groups can be OR-ed) X */ X#define CCR_HARDRESET 0x81 /* Reset the chip */ X X#define CCR_SOFTRESET 0x80 /* Soft Channel Reset */ X X#define CCR_CORCHG1 0x42 /* Channel Option Register 1 Changed */ X#define CCR_CORCHG2 0x44 /* Channel Option Register 2 Changed */ X#define CCR_CORCHG3 0x48 /* Channel Option Register 3 Changed */ X X#define CCR_SSCH1 0x21 /* Send Special Character 1 */ X X#define CCR_SSCH2 0x22 /* Send Special Character 2 */ X X#define CCR_SSCH3 0x23 /* Send Special Character 3 */ X X#define CCR_SSCH4 0x24 /* Send Special Character 4 */ X X#define CCR_TXEN 0x18 /* Enable Transmitter */ X#define CCR_RXEN 0x12 /* Enable Receiver */ X X#define CCR_TXDIS 0x14 /* Diasable Transmitter */ X#define CCR_RXDIS 0x11 /* Diasable Receiver */ X X/* X * Channel Option Register 1 X */ X#define COR1_ODDP 0x80 /* Odd Parity */ X#define COR1_PARMODE 0x60 /* Parity Mode mask */ X#define COR1_NOPAR 0x0 /* No Parity */ X#define COR1_FORCEPAR 0x20 /* Force Parity */ X#define COR1_NORMPAR 0x40 /* Normal Parity */ X#define COR1_IGNORE 0x10 /* Ignore Parity on RX */ X#define COR1_STOPBITS 0xc /* Number of Stop Bits */ X#define COR1_1SB 0x0 /* 1 Stop Bit */ X#define COR1_15SB 0x4 /* 1.5 Stop Bits */ X#define COR1_2SB 0x8 /* 2 Stop Bits */ X#define COR1_CHARLEN 0x3 /* Character Length */ X#define COR1_5BITS 0x0 /* 5 bits */ X#define COR1_6BITS 0x1 /* 6 bits */ X#define COR1_7BITS 0x2 /* 7 bits */ X#define COR1_8BITS 0x3 /* 8 bits */ X X/* X * Channel Option Register 2 X */ X#define COR2_IXM 0x80 /* Implied XON mode */ X#define COR2_TXIBE 0x40 /* Enable In-Band (XON/XOFF) Flow Control */ X#define COR2_ETC 0x20 /* Embedded Tx Commands Enable */ X#define COR2_LLM 0x10 /* Local Loopback Mode */ X#define COR2_RLM 0x8 /* Remote Loopback Mode */ X#define COR2_RTSAO 0x4 /* RTS Automatic Output Enable */ X#define COR2_CTSAE 0x2 /* CTS Automatic Enable */ X#define COR2_DSRAE 0x1 /* DSR Automatic Enable */ X X/* X * Channel Option Register 3 X */ X#define COR3_XONCH 0x80 /* XON is a pair of characters (spec. 1&3) */ X#define COR3_XOFFCH 0x40 /* XOFF is a pair of characters (2&4) */ X#define COR3_FCT 0x20 /* Flow-Control Transparency Mode */ X#define COR3_SCDE 0x10 /* Special Character Detection Enable */ X#define COR3_RXTH 0xf /* RX FIFO Threshold value (1-12) */ X X/* X Channel Option Register 4 X*/ X#define COR4_IGNCR 0x80 X#define COR4_ICRNL 0x40 X#define COR4_INLCR 0x20 X#define COR4_IGNBRK 0x10 X#define COR4_NBRKINT 0x08 X#define COR4_PFOEXCP 0x00 X#define COR4_PFOGOOD 0x01 X#define COR4_PFODISC 0x02 X#define COR4_PFONULL 0x03 X#define COR4_PFOMARK 0x04 X X/* X Channel Option Register 5 X*/ X X#define COR5_ISTRIP 0x80 X#define COR5_IEXTEN 0x40 X#define COR5_ONLCR 0x02 X#define COR5_OCRNL 0x01 X X/* X * Modem Change Option Register 1 X */ X#define MCOR1_DSRZD 0x80 /* Detect 0->1 transition of DSR */ X#define MCOR1_CTSZD 0x40 /* Detect 0->1 transition of CTS */ X#define MCOR1_RIZD 0x20 /* Detect 0->1 transition of RI */ X#define MCOR1_CDZD 0x10 /* Detect 0->1 transition of CD */ X#define MCOR1_DTRTH 0xf /* Automatic DTR flow control Threshold (1-12)*/ X#define MCOR1_NODTRFC 0x0 /* Automatic DTR flow control disabled */ X X/* X * Modem Change Option Register 2 X */ X#define MCOR2_DSROD 0x80 /* Detect 1->0 transition of DSR */ X#define MCOR2_CTSOD 0x40 /* Detect 1->0 transition of CTS */ X#define MCOR2_RIOD 0x20 /* Detect 1->0 transition of RI */ X#define MCOR2_CDOD 0x10 /* Detect 1->0 transition of CD */ X X/* X * Modem Signal Value Registers X */ X#define MSVR2_DSR 0x80 /* Current state of DSR input */ X#define MSVR2_CTS 0x40 /* Current state of CTS input */ X#define MSVR2_RI 0x20 /* Current state of RI input */ X#define MSVR2_CD 0x10 /* Current state of CD input */ X#define MSVR2_DTR 0x02 /* Current state of DTR output */ X X#define MSVR1_RTS 0x01 /* Current state of RTS output */ X X/* X * Escape characters X */ X#define CD1400_C_ESC 0x0 /* Escape character */ X#define CD1400_C_SBRK 0x81 /* Start sending BREAK */ X#define CD1400_C_DELAY 0x82 /* Delay output */ X#define CD1400_C_EBRK 0x83 /* Stop sending BREAK */ X X#define MISR_CDCHG 0x10 X X X#define CD1400_SVRR_RX 0x01 X#define CD1400_SVRR_TX 0x02 X#define CD1400_SVRR_MDM 0x04 X X#define SRER_MDM 0x80 X#define SRER_RXD 0x10 X#define SRER_TXD 0x04 X#define SRER_NNDT 0x01 END-of-cl-cd1400.h echo x - cyb.c sed 's/^X//' >cyb.c << 'END-of-cyb.c' X/*- X * Copyright (c) 1995 By Brian E. Litzinger. All rights reserved. X * X * X */ X X/* X X*/ X/* X * cyclades X */ X X#include "cyb.h" X#if NCYB > 0 X/* #define CYDEBUG 1 */ X X#include X#include X#include X#include X#include X#include X#include X#include X#include X#include X#include X#include X#include "sys/devconf.h" X X#include "machine/cpufunc.h" X#include "machine/clock.h" X X#include "i386/isa/isa.h" X#include "i386/isa/isa_device.h" X#include "i386/isa/icu.h" X X#include "i386/isa/cybreg.h" X#include "i386/isa/cl-cd1400.h" X X#define POLLSLICE 100 /*ms*/ X X X#define dprintf(x) /* */ X#define UNIT(dev) (((dev)>>5)&0x03) X#define LINE(dev) ((dev)&0x1f) X X#define MAX_CHAN 16 X#define FastRawInput X X Xstruct cybsoftc { X struct tty cyb_tty[MAX_CHAN]; /* Per-channel tty structures */ X short cy_softdtr; /* software copy of DTR */ X short cy_txint; /* TX interrupt is in progress */ X short cy_inintr; /* Interrupt in progess */ X short cy_pollactive; /* Polling active */ X caddr_t cy_addr[MAX_CHAN]; /* base i/o address */ X char cy_init[MAX_CHAN]; /* line has been inited since reset */ X char cy_cmd[MAX_CHAN]; /* command bytes per channels */ X char cy_pendesc[MAX_CHAN]; /* pending escapes */ X u_int cy_orun[MAX_CHAN]; /* overruns */ X unsigned char cy_srer[MAX_CHAN]; X caddr_t cy_base; X int cy_NbrCD1400s; X int cy_NbrPorts; X struct kern_devconf kdc; /* kernel configuration database info */ X} cybsoftc[NCYB]; X X/* X * cybmctl commands X */ Xenum cybmctl_cmds { GET, SET, BIS, BIC }; X Xint cybprobe __P((struct isa_device *)); Xint cybattach __P((struct isa_device *)); Xint cybopen __P((dev_t, int, int, struct proc *)); Xint cybclose __P((dev_t, int, int, struct proc *)); Xint cybread __P((dev_t, struct uio *, int)); Xint cybwrite __P((dev_t, struct uio *, int)); Xvoid cybintr __P((int)); Xvoid cybstart __P((struct tty *)); Xint cybioctl __P((dev_t, int, caddr_t, int, struct proc *)); Xstatic void cybchancmd __P((caddr_t, int)); Xint cybparam __P((struct tty *, struct termios *)); Xint cybselect __P((dev_t, int, struct proc *)); Xvoid cybstop __P((struct tty *, int)); Xstatic void cybcd1400init __P((int)); Xstatic int cybmctl __P((dev_t, enum cybmctl_cmds, int)); Xstatic int cybspeed __P((long, int *)); Xstatic void cybpoll(); X Xstruct isa_driver cybdriver = { cybprobe, cybattach, "cyb" }; X Xstatic struct kern_devconf kdc_tm_template = { X 0, 0, 0, /* filled in by dev_attach */ X "cyb", 0, { MDDT_ISA, 0, "tty" }, X isa_generic_externalize, 0, 0, ISA_EXTERNALLEN, X &kdc_isa0, /* parent */ X 0, /* parentdata */ X DC_UNCONFIGURED, X "Cyclades-BEL" /* description */ X}; X X Xstatic inline void Xcyb_registerdev(struct isa_device *id, const char *descr) X{ X struct kern_devconf *kdc = &cybsoftc[id->id_unit].kdc; X char *longdescr; X *kdc = kdc_tm_template; X kdc->kdc_unit = id->id_unit; X kdc->kdc_parentdata = id; X kdc->kdc_description = descr; X dev_attach(kdc); X} X X/* X * Probe routine X */ Xint Xcybprobe(struct isa_device *isa_dev) { X struct cybsoftc *sc = &cybsoftc[isa_dev->id_unit]; X X int i,j; X caddr_t b; X int flags; X int ports; X int NbrCD1400s; X unsigned char version; X X X cyb_registerdev(isa_dev,"Cyclades-BEL"); X X#define TEST_FOR_NbrCD1400s 4 X X NbrCD1400s = 0; X X b = isa_dev->id_maddr; X X (void) rinb(b,cy_RESET_16); X DELAY(500); X X for (i=0; icy_NbrCD1400s = NbrCD1400s; X return (NbrCD1400s>0); X} X X/* X * Attach routine X */ Xint Xcybattach(struct isa_device *isa_dev) { X register struct cybsoftc *sc = &cybsoftc[isa_dev->id_unit]; X register caddr_t base; X caddr_t b; X int flags; X int i,j,k; X X X sc->cy_NbrPorts = sc->cy_NbrCD1400s * 4; X printf(" ports %d",sc->cy_NbrPorts); X X X sc->cy_base = b = isa_dev->id_maddr; X X for (i=0,k=0;icy_NbrCD1400s;i++) { X base = b + i * CD1400_MEMSIZE; X routb(base, CD1400_PPR, CD1400_CLOCK_25_1MS); X for (j=0;jcy_addr[k] = base; X /* cy_channel_init */ X routb(base, CD1400_CAR, j&0x03); X cybchancmd(base,CCR_SOFTRESET); X routb(base, CD1400_LIVR, 0); X } X } X X routb(b,cy_CLEAR_INTR,0); /* Clear interrupts */ X X /* Initialize interrupt/id structures */ X X bzero(&sc->cyb_tty,sizeof(struct tty)*MAX_CHAN); X X#if 0 X strcpy(sc->cy_ttydev.tty_name, cycd.cd_name); X sc->cy_ttydev.tty_unit = sc->cy_dev.dv_unit; X sc->cy_ttydev.tty_base = sc->cy_dev.dv_unit * 16; X sc->cy_ttydev.tty_count = sc->cy_NbrPorts; X sc->cy_ttydev.tty_ttys = sc->cy_tty; X tty_attach(&sc->cy_ttydev); X#endif X sc->cy_inintr = 0; X sc->cy_pollactive = 1; X#ifdef cy_STATS X sc->cy_statclk = 1000; /* 1000ms = 1 sec */ X#endif X timeout((timeout_func_t)cybpoll,(caddr_t)sc,POLLSLICE); X printf("\n"); X return(1); X} X X/* X * Open line X */ Xint Xcybopen(dev, flag, mode, p) X dev_t dev; X int flag; X int mode; X struct proc *p; X{ X register struct tty *tp; X int s; X int error; X register caddr_t base; X int unit, chan; X struct cybsoftc *sc; X X unit = UNIT(dev); X sc = &cybsoftc[unit]; X if (sc == 0) { X dprintf(("&cybsoftc[%d]=0 error\n",unit)); X return (ENXIO); X } X X chan = LINE(dev); X if (chan >= sc->cy_NbrPorts) { X dprintf(("chan %d>NbrPorts",chan)); X return (ENXIO); X } X tp = &sc->cyb_tty[chan]; X base = sc->cy_addr[chan]; X dprintf(("cybopen: base %lx, chan %d\n",base,chan)); X tp->t_oproc = cybstart; X tp->t_param = cybparam; X tp->t_dev = dev; X if ((tp->t_state & TS_ISOPEN) == 0) { X tp->t_state |= TS_WOPEN; X if (tp->t_ispeed == 0) { X tp->t_iflag = 0; X tp->t_oflag = 0; X tp->t_cflag = TTYDEF_CFLAG; X tp->t_lflag = 0; X tp->t_ispeed = tp->t_ospeed = TTYDEF_SPEED; X } X cybparam(tp, &tp->t_termios); X ttsetwater(tp); X } else if ((tp->t_state & TS_XCLUDE) && p->p_ucred->cr_uid != 0) X return (EBUSY); X X error = 0; X s = spltty(); X (void) cybmctl(dev, SET, TIOCM_DTR|TIOCM_RTS); X X routb(base, CD1400_CAR, chan&0x03); X if (rinb(base, CD1400_MSVR2) & MSVR2_CD) { X dprintf(("CD PRESENT\n")); X tp->t_state |= TS_CARR_ON; X } X if (!(flag & O_NONBLOCK)) { X while (!(tp->t_cflag & CLOCAL) && !(tp->t_state & TS_CARR_ON)) { X tp->t_state |= TS_WOPEN; X error = ttysleep(tp, (caddr_t)&tp->t_rawq, X TTIPRI | PCATCH, ttopen, 0); X if (error) { X /* X * Disable line and drop DTR. X * Note, this is wrong if another open might X * be in progress. X */ X#if 1 X /*cybchancmd(base, CCR_TXDIS | CCR_RXDIS);*/ X sc->cy_init[chan] = 0; X (void) cybmctl(dev, SET, 0); X#endif X break; X } X } X } X splx(s); X if (error == 0) X error = (*linesw[tp->t_line].l_open)(dev, tp); X#ifdef cy_STATS X sc->stats_ints_xmit[chan] = 0; X sc->stats_ints_recv[chan] = 0; X sc->stats_ints_mdm [chan] = 0; X#endif X return (error); X} X X/* X * Close line X */ Xint Xcybclose(dev, flag, mode, p) X dev_t dev; X int flag; X int mode; X struct proc *p; X{ X struct cybsoftc *sc = &cybsoftc[UNIT(dev)]; X int chan = LINE(dev); X register struct tty *tp = &sc->cyb_tty[chan]; X register caddr_t base = sc->cy_addr[chan]; X int s; X X dprintf(("cybclose: chan %d\n",chan)); X X s = spltty(); X (*linesw[tp->t_line].l_close)(tp, flag); X X /* Disable line */ X routb(base, CD1400_CAR, chan&0x03); X cybchancmd(base, CCR_TXDIS | CCR_RXDIS); X sc->cy_init[chan] = 0; X routb(base, CD1400_SRER, sc->cy_srer[chan]=0); X X /* Hang up */ X if ((tp->t_cflag & HUPCL) || (tp->t_state & TS_WOPEN) || X (tp->t_state & TS_ISOPEN) == 0) X (void) cybmctl(dev, SET, 0); X X ttyclose(tp); X splx(s); X if (sc->cy_orun[chan]) { X log(LOG_ERR, "cy%d line %d: %d overruns\n", UNIT(dev), chan, X sc->cy_orun[chan]); X sc->cy_orun[chan] = 0; X } X#ifdef cy_STATS X { X int i; X printf("cy%d:%d\n\t", UNIT(dev), LINE(dev)); X for (i = 0; i < 3; i++) X printf("I%d=%x ", i, int_cnt[minor(dev)][i]); X for (i = 0; i < 2; i++) X printf("L%d=%x ", i, loops[UNIT(dev)][i]); X printf("\n"); X } X#endif X return (0); X} X X/* X * Read from line X */ Xint Xcybread(dev, uio, flag) X dev_t dev; X struct uio *uio; X int flag; X{ X struct cybsoftc *sc = &cybsoftc[UNIT(dev)]; X struct tty *tp = &sc->cyb_tty[LINE(dev)]; X X dprintf(("cybread:\n")); X return ((*linesw[(u_char)tp->t_line].l_read)(tp, uio, flag)); X} X X/* X * Write to line X */ Xint Xcybwrite(dev, uio, flag) X dev_t dev; X struct uio *uio; X int flag; X{ X struct cybsoftc *sc = &cybsoftc[UNIT(dev)]; X struct tty *tp = &sc->cyb_tty[LINE(dev)]; X X dprintf(("cybwrite:\n")); X return ((*linesw[(u_char)tp->t_line].l_write)(tp, uio, flag)); X} X Xstruct tty * Xcybdevtotty(dev_t dev) X{ X int chan; X struct cybsoftc *sc; X int unit; X X /* X * XXX UNIT() hacks on dev, should hack on minor(dev). X */ X unit = UNIT(dev); X /* X * XXX minor bits aren't fully decoded. This guarantees that X * 0 <= unit < 0x20, so the following indexing is guaranteed valid. X */ X sc = &cybsoftc[unit]; X /* X * XXX sc is guaranteed != NULL now. The following check will be X * required when we resurrect dynamic allocation. X */ X if (sc == NULL) X return (NULL); X chan = LINE(dev); X if (chan >= sc->cy_NbrPorts) X return (NULL); X return (&sc->cyb_tty[chan]); X} X X#ifdef wrong_for_FreeBSD_2_0_and_unused_for_FreeBSD_2_1 Xint Xcybselect(dev, flag, p) X dev_t dev; X int flag; X struct proc *p; X{ X /* WARNING *** FreeBSD *** */ X return (ttselect(dev, flag, p)); X} X#endif X Xstatic void Xcybpoll(sc) X struct cybsoftc *sc; X{ X register struct tty *tp; X register caddr_t base; X register int chan; X int s; X X s = spltty(); X if (sc->cy_inintr==0) { X for (chan=0;chancy_NbrPorts;chan++) { X tp = &sc->cyb_tty[chan]; X X if (tp->t_state&TS_BUSY /*&& (sc->cy_srer[chan]&SRER_TXD)==0*/) { X base = sc->cy_addr[chan]; X dprintf(("prodding %d\n",chan)); X routb(base, CD1400_CAR, chan&0x03); X routb(base, CD1400_SRER, sc->cy_srer[chan]=SRER_MDM|SRER_RXD|SRER_TXD); X } X } X } X#ifdef cy_STATS X sc->cy_statclk -= POLLSLICE; X if (sc->cy_statclk<=0) { X X sc->cy_statclk = 1000; /* 1000ms = 1 sec */ X } X#endif X splx(s); X if (sc->cy_pollactive) X timeout((timeout_func_t)cybpoll,(caddr_t)sc,POLLSLICE); X} X X/* X * Interrupt routine X */ Xvoid Xcybintr(int unit) X{ X struct cybsoftc *sc = &cybsoftc[0/*unit WARN *** */]; X struct tty *tp; X int b, c; X unsigned cnt; X int chan; X caddr_t base; X int cd; X int domore; X X sc->cy_inintr = 1; X dprintf(("cybintr:\n")); X more: X domore = 0; X for (cd=0;cdcy_NbrCD1400s;cd++) { X base = sc->cy_addr[cd*4]; /* WARNING */ X X dprintf(("*I%d*\n", unit)); X if (base == 0) { X printf("cy%d: bogus interrupt\n", unit); X sc->cy_inintr = 0; X } X X /* Read Board Status Register */ X dprintf(("reading from %lx\n",(unsigned long)base)); X while (b=rinb(base,CD1400_SVRR)) { X domore = 1; X /* X * Need to add some code to allow return if this card is hogging X */ X X /* Receiver interrupt */ X if (b & CD1400_SVRR_RX) { X unsigned char save_rir = rinb(base,CD1400_RIR); X int chan = cd*CD1400_NO_OF_CHANNELS + (save_rir&0x03); X unsigned char save_car = rinb(base,CD1400_CAR); X routb(base,CD1400_CAR,save_rir); X X tp = &sc->cyb_tty[chan]; X#ifdef cy_STATS X sc->stats_ints_recv[chan]++; X#endif X X switch(rinb(base,CD1400_RIVR)&0x07) { X X case 3: X /* Get the count of received characters */ X cnt = rinb(base, CD1400_RDCR); X X /* If the line wasn't opened, throw data into bit bucket */ X if ((tp->t_state & TS_ISOPEN) == 0) { X while (cnt--) X (void) rinb(base, CD1400_RDSR); X goto rxout; X } X X#ifdef FastRawInput X if ((tp->t_line == 0) && X !(tp->t_iflag & (ICRNL|IMAXBEL|INLCR)) && X !(tp->t_lflag & (ECHO|ECHONL|ICANON|IEXTEN|ISIG|PENDIN))&& X !(tp->t_state & (TS_CNTTB|TS_LNCH)) && cnt>0 ) { X unsigned char buf[32]; /* *** WARNING *** */ X unsigned char *p = buf; X int i = cnt; X while (i--) { X *p++ = ((rinb(base, CD1400_RDSR))&0xff); X } X i = b_to_q(buf,cnt,&tp->t_rawq); X ttwakeup(tp); X } else X#endif X { X while (cnt--) { X c = ((rinb(base, CD1400_RDSR))&0xff); X (*linesw[tp->t_line].l_rint)(c, tp); X } X } X break; X X case 7: X (void) rinb(base,CD1400_RDSR); /* Get status */ X (void) rinb(base,CD1400_RDSR); /* Get bad data */ X break; X } X X rxout: X routb(base,CD1400_RIR,save_rir&0x3f); X routb(base,CD1400_CAR,save_car); X } X X X X /* TX interrupt? */ X if (b & CD1400_SVRR_TX) { X unsigned char save_tir = rinb(base,CD1400_TIR); X int chan = cd*CD1400_NO_OF_CHANNELS + (save_tir&0x03); X unsigned char save_car = rinb(base,CD1400_CAR); X routb(base,CD1400_CAR,save_tir); X X tp = &sc->cyb_tty[chan]; X#ifdef cy_STATS X sc->stats_ints_xmit[chan]++; X#endif X X /* (Re-)start transmit */ X if (tp->t_state & TS_FLUSH) { X tp->t_state &= ~(TS_BUSY|TS_FLUSH); X /* Disable TX interrupts */ X routb(base, CD1400_SRER, sc->cy_srer[chan]=SRER_MDM|SRER_RXD); X } else { X tp->t_state &= ~TS_BUSY; X sc->cy_txint = 1; X (*linesw[tp->t_line].l_start)(tp); X sc->cy_txint = 0; X /* If nothing to send, disable TX interrupts */ X if ((tp->t_state&TS_BUSY) == 0) X routb(base, CD1400_SRER, sc->cy_srer[chan]=SRER_MDM|SRER_RXD); X X } X routb(base, CD1400_TIR,(save_tir & 0x3f)); X routb(base, CD1400_CAR,save_car); X X } X /* goto out */ X X /* Modem Ctl interrupt? */ X if (b & CD1400_SVRR_MDM) { X unsigned char save_mir = rinb(base,CD1400_MIR); X int chan = cd * CD1400_NO_OF_CHANNELS + (save_mir & 0x3); X unsigned char save_car = rinb(base,CD1400_CAR); X routb(base,CD1400_CAR,save_mir); X X tp = &sc->cyb_tty[chan]; X#ifdef cy_STATS X sc->stats_ints_mdm[chan]++; X#endif X X if ((rinb(base, CD1400_MISR) & MISR_CDCHG)) { X /* Get the value of CD */ X if (rinb(base,CD1400_MSVR2) & MSVR2_CD) X (void) (*linesw[tp->t_line].l_modem)(tp, 1); X else if ((*linesw[tp->t_line].l_modem)(tp, 0) == 0) X (void) cybmctl(tp->t_dev, SET, 0); X X /* WARNING: May need to clear change bits here */ X } X routb(base,CD1400_MIR,save_mir&0x3f); X routb(base,CD1400_CAR,save_car); X X } X } X } X if (domore) goto more; X sc->cy_inintr = 0; X routb(sc->cy_base, cy_CLEAR_INTR, 0); X} X X/* X * Start transmission X */ Xvoid Xcybstart(tp) X register struct tty *tp; X{ X register caddr_t base; X register c, count; X int s, chan; X register struct cybsoftc *sc; X X dprintf(("cybstart:\n")); X /* X * Check if there is work to do and we're able to do more. X */ X s = spltty(); X if (tp->t_state & TS_BUSY X || (tp->t_state & (TS_TIMEOUT|TS_TTSTOP)) X#if 0 /* *** FreeBSD WARNING *** */ X && (tp->t_state & (TS_XON_PEND|TS_XOFF_PEND)) == 0) X#endif X ) { X dprintf(("leaving early\n")); X goto out; X } X X if (tp->t_outq.c_cc <= tp->t_lowat) { X if (tp->t_state & TS_ASLEEP) { X tp->t_state &= ~TS_ASLEEP; X wakeup((caddr_t)&tp->t_outq); X } X selwakeup(&tp->t_wsel); X } X X sc = &cybsoftc[UNIT(tp->t_dev)]; X chan = LINE(tp->t_dev); /* *** WARNING *** */ X base = sc->cy_addr[chan]; X X /* X * If not in interrupt context, TDR is not available. X * Simply enable TX interrupt if there is output to be done. X */ X if (sc->cy_txint == 0) { X if (tp->t_outq.c_cc || X /*tp->t_state & (TS_XON_PEND|TS_XOFF_PEND) || freeBSD WARN *** */ X sc->cy_cmd[chan] || sc->cy_pendesc[chan]) { X tp->t_state |= TS_BUSY; X routb(base, CD1400_CAR, chan&0x03); X routb(base, CD1400_SRER, sc->cy_srer[chan]=SRER_MDM|SRER_RXD|SRER_TXD); X } X dprintf(("leaving with TXD ints enabled\n")); X goto out; X } X X /* X * Process pending commands X */ X count = CD1400_MAX_FIFO_SIZE; X if (c = sc->cy_cmd[chan]) { X sc->cy_cmd[chan] = 0; X routb(base, CD1400_TDR, CD1400_C_ESC); X routb(base, CD1400_TDR, c); X count -= 2; X } X if (sc->cy_pendesc[chan]) { X sc->cy_pendesc[chan] = 0; X routb(base, CD1400_TDR, CD1400_C_ESC); X count--; X } X X X#if 0 /* *** FreeBSD WARNING *** */ X if (tp->t_state & (TS_XON_PEND|TS_XOFF_PEND)) { X if (tp->t_state & TS_XON_PEND) { X routb(base, CD1400_TDR, tp->t_cc[VSTART]); X tp->t_state &= ~TS_XON_PEND; X } else { X routb(base, CD1400_TDR, tp->t_cc[VSTOP]); X tp->t_state &= ~TS_XOFF_PEND; X } X if (tp->t_state & (TS_TIMEOUT|TS_TTSTOP)) X count = 0; X else X count--; X } X#endif X X /* X * Run regular output queue X */ X while (tp->t_outq.c_cc && count--) { X c = getc(&tp->t_outq); X if (c == CD1400_C_ESC) { X if (count == 0) /* oops */ X sc->cy_pendesc[chan]++; X else { X routb(base, CD1400_TDR, CD1400_C_ESC); X count--; X } X } X dprintf(("txd: %c (%x)\n",(c<0x20||c>0x7e)?' ':c,c)); X routb(base, CD1400_TDR, c); X } X if (countt_outq.c_cc*/) X tp->t_state |= TS_BUSY; X Xout: X splx(s); X} X X/* X * Ioctl routine X */ Xint Xcybioctl(dev, cmd, data, flag, p) X dev_t dev; X int cmd; X caddr_t data; X int flag; X struct proc *p; X{ X register struct cybsoftc *sc = &cybsoftc[UNIT(dev)]; X register struct tty *tp = &sc->cyb_tty[LINE(dev)]; X register int error; X int s; X X dprintf(("cybioctl:\n")); X error = (*linesw[tp->t_line].l_ioctl)(tp, cmd, data, flag, p); X if (error >= 0) X return (error); X error = ttioctl(tp, cmd, data, flag); X if (error >= 0) X return (error); X X s = spltty(); X switch (cmd) { X case TIOCSBRK: X /* Start sending BREAK */ X sc->cy_cmd[LINE(tp->t_dev)] = CD1400_C_SBRK; X cybstart(tp); X break; X X case TIOCCBRK: X /* Stop sending BREAK */ X sc->cy_cmd[LINE(tp->t_dev)] = CD1400_C_EBRK; X cybstart(tp); X break; X X case TIOCSDTR: /* set DTR */ X (void) cybmctl(dev, BIS, TIOCM_DTR); X break; X X case TIOCCDTR: /* clear DTR */ X (void) cybmctl(dev, BIC, TIOCM_DTR); X break; X X case TIOCMSET: X (void) cybmctl(dev, SET, * (int *) data); X break; X X case TIOCMBIS: X (void) cybmctl(dev, BIS, * (int *) data); X break; X X case TIOCMBIC: X (void) cybmctl(dev, BIC, * (int *) data); X break; X X case TIOCMGET: X * (int *) data = cybmctl(dev, GET, 0); X break; X X default: X splx(s); X return (ENOTTY); X } X splx(s); X return (0); X} X Xstatic int cyb_fifothresh_lo = 9; /* FIFO depth, half of FIFO, < 38.4k */ Xstatic int cyb_fifothresh_hi = 6; /* FIFO depth, >= 38.4k */ X Xstatic int cyb_doenable = 0; /* should not be needed, defeats optimization if set */ X/* X * Set parameters and enable the line X */ Xint Xcybparam(tp, t) X register struct tty *tp; X register struct termios *t; X{ X int s, chan; X register struct cybsoftc *sc; X register caddr_t base; X int iprescaler, oprescaler; X int ispeed, ospeed; X int cflag = t->c_cflag; X int iflag = t->c_iflag; X /* X c is initialized to 0, eventhough it isn't necessary, to stop X gnu gcc 2.6.2 from emitting a warning that it may be used X uninitialized. X */ X register c = 0; X X dprintf(("cybparam:\n")); X /* short-circuit the common case where there is no hardware change */ X X if (tp->t_cflag == t->c_cflag && tp->t_state&TS_ISOPEN && X tp->t_iflag == t->c_iflag && X tp->t_ispeed == t->c_ispeed && tp->t_ospeed == t->c_ospeed) X return (0); X X if ((tp->t_cflag & CLOCAL) == 0 && t->c_cflag & CLOCAL) X wakeup((caddr_t) &tp->t_rawq); X X tp->t_ispeed = t->c_ispeed; X tp->t_ospeed = t->c_ospeed; X tp->t_cflag = t->c_cflag; X tp->t_iflag = t->c_iflag; X X /* Select line */ X sc = &cybsoftc[UNIT(tp->t_dev)]; X chan = LINE(tp->t_dev); X base = sc->cy_addr[chan]; X s = spltty(); X routb(base, CD1400_CAR, chan&0x03); X X /* ospeed == 0 is for HANGUP */ X if (tp->t_ospeed == 0) { X (void) cybmctl(tp->t_dev, SET, 0); X cybchancmd(base, CCR_TXDIS | CCR_RXDIS); X sc->cy_init[chan] = 0; X splx(s); X return (0); X } X X if ((ospeed = cybspeed(t->c_ospeed, &oprescaler)) < 0) { X splx(s); X return(EINVAL); X } X routb(base,CD1400_TBPR,ospeed); X routb(base,CD1400_TCOR,oprescaler); X X if ((ispeed = cybspeed(t->c_ispeed, &iprescaler)) < 0) { X splx(s); X return(EINVAL); X } X routb(base,CD1400_RBPR,ispeed); X routb(base,CD1400_RCOR,iprescaler); X X /* Load COR1 */ X switch (tp->t_cflag & CSIZE) { X case CS5: X c = COR1_5BITS; X break; X case CS6: X c = COR1_6BITS; X break; X case CS7: X c = COR1_7BITS; X break; X case CS8: X c = COR1_8BITS; X break; X } X#if 0 X printf("%s ",tp->t_cflag & CSTOPB ? "CSTOPB":"!CSTOPB"); X printf("%s ",tp->t_cflag & PARENB ? "PARENB":"!PARENB"); X printf("%s ",tp->t_cflag & PARODD ? "PARODD":"!PARODD"); X printf("%s ",tp->t_cflag & PARODD ? "PARODD":"!PARODD"); X#endif X if (tp->t_cflag & CSTOPB) X c |= COR1_2SB; X if (tp->t_cflag & PARENB) { X c |= COR1_NORMPAR; X if (tp->t_cflag & PARODD) X c |= COR1_ODDP; X#if 0 X if ((tp->t_iflag & INPCK) == 0) X c |= COR1_IGNORE; X#endif X } else X c |= COR1_IGNORE; X routb(base, CD1400_COR1, c); X dprintf(("cor1=%x\n",c)); X X /* Load COR2 */ X c = COR2_ETC; X if (tp->t_cflag & CCTS_OFLOW) X c |= COR2_CTSAE; X#ifdef wrong X /* X * COR2_RTSAO enables traditional RTS (high when there is something X * to transmit), not RTR (high when ready to receive). X */ X if (tp->t_cflag & CRTS_IFLOW) X c |= COR2_RTSAO; X#endif X X /* there should be some logic to enable on-chip Xon/Xoff flow ctl */ X routb(base, CD1400_COR2, c); X dprintf(("cor2=%x\n",c)); X X /* Load COR3 */ X if (tp->t_ispeed >= 38400) X routb(base, CD1400_COR3, cyb_fifothresh_hi); /* FIFO depth */ X else X routb(base, CD1400_COR3, cyb_fifothresh_lo); /* FIFO depth */ X /* set the Receive Timeout Period to 20ms */ X routb(base, CD1400_RTPR, 20); X X /* Inform CD1400 engine about new values in COR registers */ X cybchancmd(base, CCR_CORCHG1 | CCR_CORCHG2 | CCR_CORCHG3); X DELAY(500); X X /* Load COR4 */ X c = 0; X if (iflag&IGNCR) X c |= COR4_IGNCR; X if (iflag&IGNBRK) X c |= COR4_IGNBRK; X if (!(iflag&BRKINT)) X c |= COR4_NBRKINT; X if (iflag&IGNPAR) X c |= COR4_PFODISC; X else { X if (iflag&PARMRK) X c |= COR4_PFOMARK; X else X c |= COR4_PFONULL; X } X routb(base,CD1400_COR4,c); X dprintf(("cor4=%x\n",c)); X X /* Load COR5 */ X c = 0; X if (iflag&ISTRIP) X c |= COR5_ISTRIP; X if (t->c_iflag&IEXTEN) X c |= COR5_IEXTEN; X routb(base,CD1400_COR5,c); X dprintf(("cor5=%x\n",c)); X X X c = 0; X if (tp->t_cflag & CRTS_IFLOW) X c |= 8; X routb(base, CD1400_MCOR1, MCOR1_CDZD|6); /* WARNING */ X X dprintf(("cybparam:1\n")); X if (sc->cy_init[chan] == 0 || cyb_doenable) { X sc->cy_init[chan] = 1; X /* Load modem control parameters */ X routb(base, CD1400_MCOR2, MCOR2_CDOD); X X /* Finally enable transmitter and receiver */ X cybchancmd(base, CCR_TXEN | CCR_RXEN); X routb(base, CD1400_SRER, sc->cy_srer[chan]=SRER_MDM|SRER_RXD); /* WARNING */ X dprintf(("cybparam:2\n")); X } X splx(s); X dprintf(("cybparam:d\n")); X return (0); X} X X/* X * Write a command to the Channel Command Register, X * making sure it is not busy before writing the command. X * The channel must already have been selected. X */ Xstatic void Xcybchancmd(base, cmd) X caddr_t base; X int cmd; X{ X int i; X X for (i = 0; i < 100; i++) { X if (rinb(base, CD1400_CCR) == 0) X goto ready; X DELAY(100); X } X printf("cy: ccr not ready\n"); Xready: X routb(base, CD1400_CCR, cmd); X} X X/* X * Stop output on a line X */ X/*ARGSUSED*/ Xvoid Xcybstop(tp, flag) X register struct tty *tp; X int flag; X{ X int s; X X s = spltty(); X if (tp->t_state & TS_BUSY) { X if ((tp->t_state & TS_TTSTOP) == 0) X tp->t_state |= TS_FLUSH; X } X splx(s); X} X X/* X * Modem control routine. X */ Xstatic int Xcybmctl(dev, cmd, bits) X dev_t dev; X enum cybmctl_cmds cmd; X int bits; X{ X register struct cybsoftc *sc = &cybsoftc[UNIT(dev)]; X register line = LINE(dev); X register caddr_t base = sc->cy_addr[line]; X register msvr; X X dprintf(("cybmctl%x: cmd=%d bits=%x base=%lx\n", X minor(dev), cmd, bits, (unsigned long)base)); X X routb(base, CD1400_CAR, line&0x03); X X switch (cmd) { X case GET: X msvr = rinb(base, CD1400_MSVR2); X bits = TIOCM_LE; X if (msvr & MSVR2_DTR) X bits |= TIOCM_DTR; X if (msvr & MSVR2_CTS) X bits |= TIOCM_CTS; X if (msvr & MSVR2_DSR) X bits |= TIOCM_DSR; X if (msvr & MSVR2_CD) X bits |= TIOCM_CAR; X if (msvr & MSVR2_RI) X bits |= TIOCM_RI; X msvr = rinb(base, CD1400_MSVR1); X if (msvr & MSVR1_RTS) X bits |= TIOCM_RTS; X return (bits); X X case SET: X if (bits&TIOCM_DTR) { X sc->cy_softdtr |= 1 << line; X routb(base, CD1400_MSVR1,MSVR1_RTS); X } else { X sc->cy_softdtr &= ~(1 << line); X routb(base, CD1400_MSVR1,0x00); /* lower RTS */ X } X break; X X case BIS: X#if 0 X if (bits & TIOCM_RTS) X routb(base, CD1400_MSVR2, MSVR2_RTS); X#endif X if (bits & TIOCM_DTR) { X sc->cy_softdtr |= 1 << line; X routb(base, CD1400_MSVR1,MSVR1_RTS); X } X X break; X X case BIC: X#if 0 X if (bits & TIOCM_RTS) X routb(base, CD1400_MSVR, 0); X#endif X if (bits & TIOCM_DTR) { X sc->cy_softdtr &= ~(1 << line); X routb(base, CD1400_MSVR1,0x00); /* lower RTS */ X } X break; X } X X /* Enable/disable receiver on open/close */ X if (cmd == SET) { X routb(base, CD1400_CAR, line&0x03); X if (bits == 0) { X cybchancmd(base, CCR_RXDIS); X } else { X cybchancmd(base, CCR_RXEN); X } X } X return (0); X} X Xstatic int Xcybspeed(speed, prescaler_io) X long speed; X int *prescaler_io; X{ X int actual; X int error; X int divider; X int prescaler; X int prescaler_unit; X X if (speed == 0) X return 0; X X if (speed < 0 || speed > 150000) X return -1; X X /* determine which prescaler to use */ X for (prescaler_unit = 4, prescaler = 2048; prescaler_unit; X prescaler_unit--, prescaler >>= 2) { X if (CYCLOM_CLOCK/prescaler/speed > 63) X break; X } X X divider = (CYCLOM_CLOCK/prescaler*2/speed + 1)/2; /* round off */ X if (divider > 255) X divider = 255; X actual = CYCLOM_CLOCK/prescaler/divider; X error = ((actual-speed)*2000/speed +1)/2; /* percentage */ X X /* 3.0% max error tolerance */ X if (error < -30 || error > 30) X return -1; X X#if 0 X printf("speed = %ld\n",speed); X printf("prescaler = %d (%d)\n", prescaler, prescaler_unit); X printf("divider = %d (%x)\n", divider, divider); X printf("actual = %d\n", actual); X printf("error = %d\n", error); X#endif X X *prescaler_io = prescaler_unit; X return divider; X} X#endif /* NCYB > 0 */ END-of-cyb.c exit From owner-freebsd-current Fri Mar 31 04:02:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA16813 for current-outgoing; Fri, 31 Mar 1995 04:02:13 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA16800 for ; Fri, 31 Mar 1995 04:02:10 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id EAA02623 for ; Fri, 31 Mar 1995 04:02:07 -0800 Message-Id: <199503311202.EAA02623@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: Floppy drive access overhead? Date: Fri, 31 Mar 1995 04:02:07 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk One of the best demos I've ever done with OS/2 is to format a floppy in the background and then run an avi or other "real time" task in the forground. OS/2 doesn't skip a beat, formats the floppy just as fast as under DOS, and your mouse pointer never freezes. Under FreeBSD, I get "jerky" system behavior at best. Does anyone know why we have this problem and how it can be fixed? __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Fri Mar 31 06:18:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA20802 for current-outgoing; Fri, 31 Mar 1995 06:18:11 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA20796 for ; Fri, 31 Mar 1995 06:18:10 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id GAA02986 for ; Fri, 31 Mar 1995 06:18:07 -0800 Message-Id: <199503311418.GAA02986@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: Bug fixes to aic7xxx driver Date: Fri, 31 Mar 1995 06:18:07 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk I just did some rather extensive patching to the aic7xxx driver. I'd appreciate it if anyone running this driver would pick up the new files and send me feedback. This fixes the "QOUTCOUNT==0" problem as well as (I believe) fixes some of the tagged queuing problems of the last release. The files you need: ftp.cdrom.com:/pub/FreeBSD/FreeBSD-current/src/sys/i386/scsi/* ftp.cdrom.com:/pub/FreeBSD/FreeBSD-current/src/sys/i386/isa/aic7770.c ftp.cdrom.com:/pub/FreeBSD/FreeBSD-current/src/sys/pci/aic7870.c ftp.cdrom.com:/pub/FreeBSD/FreeBSD-current/src/sys/gnu/misc/aic7xxx/* Make sure the files you grab are dated the 31st. I'm not sure what time the sup update happens over there, so be sure you don't pick up the old copies. __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Fri Mar 31 07:41:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA22688 for current-outgoing; Fri, 31 Mar 1995 07:41:00 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA22680 for ; Fri, 31 Mar 1995 07:40:53 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id IAA19413; Fri, 31 Mar 1995 08:44:52 -0700 Date: Fri, 31 Mar 1995 08:44:52 -0700 Message-Id: <199503311544.IAA19413@trout.sri.MT.net> To: roberto@blaise.ibp.fr (Ollivier Robert) Cc: nate@sneezy.sri.com, current@FreeBSD.org (Current's list FreeBSD) Subject: Re: Announce: New Version of CVS ( was Re: cvs commit: src/gnu/usr.bin Makefile) In-Reply-To: <9503310935.AA19006@blaise.ibp.fr> References: <199503310810.BAA28573@rocky.sri.MT.net> <9503310935.AA19006@blaise.ibp.fr> Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk > > If you can, please test this out on your machines. I don't forsee any > > problems whatsoever, but it's better to be safe than sorry. I'd like to > > see freefall get updated binaries in the next couple weeks. > > > > I'm using it on my machine for at least one month and I' didn't have any > problem with it. Seems faster even without J.T. Conklin improvements I > saw on the cvs list. Write, but alot of the CVS speedups are in the stock code. J.T. made some FS speedups that are dependant on 4.4 systems which make the stat's an order of magnitude faster. Those are already in 1.4A, and are aside from the other speedups posted. Nate From owner-freebsd-current Fri Mar 31 08:10:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA24903 for current-outgoing; Fri, 31 Mar 1995 08:10:21 -0800 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 IAA24895; Fri, 31 Mar 1995 08:10:19 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA18339; Fri, 31 Mar 1995 11:10:07 -0500 Date: Fri, 31 Mar 1995 11:10:07 -0500 From: Garrett Wollman Message-Id: <9503311610.AA18339@halloran-eldar.lcs.mit.edu> To: "Justin T. Gibbs" Cc: current@FreeBSD.org, wollman@FreeBSD.org Subject: rfc 1323 Support In-Reply-To: <199503310041.QAA00401@estienne.cs.berkeley.edu> References: <199503310041.QAA00401@estienne.cs.berkeley.edu> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > I will be talking to the annex gods here at Cal to see what they have to > say about this, but even if it is an annex problem not a FreeBSD SLIP > problem, should this stuff be enabled by default? Absolutely. One of FreeBSD's strengths is that it does the right thing for TCP right out of the box, where many other vendors still don't even get the MSS right.... -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 Mar 31 08:34:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA25806 for current-outgoing; Fri, 31 Mar 1995 08:34:22 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA25796; Fri, 31 Mar 1995 08:34:21 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id IAA03184; Fri, 31 Mar 1995 08:34:15 -0800 Message-Id: <199503311634.IAA03184@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: Garrett Wollman cc: current@FreeBSD.org, wollman@FreeBSD.org Subject: Re: rfc 1323 Support In-reply-to: Your message of "Fri, 31 Mar 1995 11:10:07 EST." <9503311610.AA18339@halloran-eldar.lcs.mit.edu> Date: Fri, 31 Mar 1995 08:34:15 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk ><keley.edu> said: > >> I will be talking to the annex gods here at Cal to see what they have to >> say about this, but even if it is an annex problem not a FreeBSD SLIP >> problem, should this stuff be enabled by default? > >Absolutely. One of FreeBSD's strengths is that it does the right >thing for TCP right out of the box, where many other vendors still >don't even get the MSS right.... > >-GAWollman Just make sure it is in bold type in the FAQ and install notes then. I don't think that I'm the only one who gets to the net via SLIP, and this problem didn't have an obvious solution. What made it look even worse was that it only affected connections to other FreeBSD machines. If left without an easily found explanation, even though FreeBSD is "doing the right thing", this feature could harm FreeBSD's reputation. I've heard that TTCP over slip with header compress is a losing configuration anyhow. Can we disable it in that configuration? > >-- >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 peopl >e >MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Fri Mar 31 08:47:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA26753 for current-outgoing; Fri, 31 Mar 1995 08:47:11 -0800 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 IAA26745 for ; Fri, 31 Mar 1995 08:47:09 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA18415; Fri, 31 Mar 1995 11:47:02 -0500 Date: Fri, 31 Mar 1995 11:47:02 -0500 From: Garrett Wollman Message-Id: <9503311647.AA18415@halloran-eldar.lcs.mit.edu> To: "Justin T. Gibbs" Cc: current@FreeBSD.org Subject: Re: rfc 1323 Support In-Reply-To: <199503311634.IAA03184@estienne.cs.berkeley.edu> References: <9503311610.AA18339@halloran-eldar.lcs.mit.edu> <199503311634.IAA03184@estienne.cs.berkeley.edu> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > I've heard that TTCP over slip with header compress is a losing > configuration anyhow. I'd love to know where you heard that since I'm not aware of anyone anywhere who has yet created applications using T/TCP as a transport mechanism. The WWW people would like to, but FreeBSD-current constitutes the entire installed base outside of a few Suns at ISI and on the DARTnet. (Sometimes it's lonely at the leading edge...) -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 Mar 31 09:16:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA27576 for current-outgoing; Fri, 31 Mar 1995 09:16:11 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA27570 for ; Fri, 31 Mar 1995 09:16:10 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id JAA03354; Fri, 31 Mar 1995 09:16:05 -0800 Message-Id: <199503311716.JAA03354@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: Garrett Wollman cc: current@FreeBSD.org Subject: Re: rfc 1323 Support In-reply-to: Your message of "Fri, 31 Mar 1995 11:47:02 EST." <9503311647.AA18415@halloran-eldar.lcs.mit.edu> Date: Fri, 31 Mar 1995 09:16:05 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk ><keley.edu> said: > >> I've heard that TTCP over slip with header compress is a losing >> configuration anyhow. > >I'd love to know where you heard that since I'm not aware of anyone >anywhere who has yet created applications using T/TCP as a transport >mechanism. The WWW people would like to, but FreeBSD-current >constitutes the entire installed base outside of a few Suns at ISI and >on the DARTnet. (Sometimes it's lonely at the leading edge...) DG mentioned it. Something to do with the timestamping. I'm not too up on TTCP myself to say more. > >-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 peopl >e >MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Fri Mar 31 09:33:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA28397 for current-outgoing; Fri, 31 Mar 1995 09:33:01 -0800 Received: from ansley.com ([155.229.16.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA28390 for ; Fri, 31 Mar 1995 09:32:53 -0800 Received: (from gja@localhost) by ansley.com (8.6.9/8.6.9) id MAA02964 for freebsd-current@freebsd.org; Fri, 31 Mar 1995 12:32:57 -0500 Date: Fri, 31 Mar 1995 12:32:57 -0500 From: Greg Ansley Message-Id: <199503311732.MAA02964@ansley.com> To: freebsd-current@FreeBSD.org Subject: FIX for bpf_filter.c Sender: current-owner@FreeBSD.org Precedence: bulk Could someone please commit this patch for the bpf_filter option. In rare cases, when the filter specified accesses an multi-byte value that is split across mbuf's, the value loaded is incorrect. And if you are very unlucky (like me) it will index off the end of the mbuf and into an unallocated page and panic the system. If you look at the code you will discover the the index *k* is added to the pointer *cp* and the used AGAIN as a subscript. Greg Ansley Ansley & Associates, Inc. In /usr/src/net: --- bpf_filter.c~ Fri Mar 31 12:25:10 1995 +++ bpf_filter.c Fri Mar 31 12:26:28 1995 @@ -112,14 +112,14 @@ switch (len - k) { case 1: - return (cp[k] << 24) | (np[0] << 16) | (np[1] << 8) | np[2]; + return (cp[0] << 24) | (np[0] << 16) | (np[1] << 8) | np[2]; case 2: - return (cp[k] << 24) | (cp[k + 1] << 16) | (np[0] << 8) | + return (cp[0] << 24) | (cp[1] << 16) | (np[0] << 8) | np[1]; default: - return (cp[k] << 24) | (cp[k + 1] << 16) | (cp[k + 2] << 8) | + return (cp[0] << 24) | (cp[1] << 16) | (cp[2] << 8) | np[0]; } bad: @@ -153,7 +153,7 @@ if (m0 == 0) goto bad; *err = 0; - return (cp[k] << 8) | mtod(m0, u_char *)[0]; + return (cp[0] << 8) | mtod(m0, u_char *)[0]; bad: *err = 1; return 0; From owner-freebsd-current Fri Mar 31 09:37:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA28789 for current-outgoing; Fri, 31 Mar 1995 09:37:43 -0800 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 JAA28767; Fri, 31 Mar 1995 09:37:30 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA07088; Sat, 1 Apr 1995 03:35:38 +1000 Date: Sat, 1 Apr 1995 03:35:38 +1000 From: Bruce Evans Message-Id: <199503311735.DAA07088@godzilla.zeta.org.au> To: jkh@freefall.cdrom.com, wollman@halloran-eldar.lcs.mit.edu Subject: Re: dlopen() and Garrett's comments on fn pointers! Cc: current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> In case no one has noticed, the dlsym() routine returns a void* for >> both function and data pointers! :-) >Yup. You have to take an intermediate step through a large-enough >integer (like unsigned long) in order to do it without diagnostics. >(The result is still implementation-defined.) Interesting. dlsym() does the following: long addr; /* WRONG large-enough integral type * (subject to unwanted overflow traps * and 1's complement conversions). */ ... addr = np->nz_value; /* nz_value is RIGHT large-enough type * (unsigned long). */ ... /* sometimes adjust `addr' */ return (void *)addr; /* match the losing interface */ The rules for unportable casts are: 1. pointer -> integral: this may be done for some implementation defined integral type. The result is implementation defined. Casting to an integral type smaller than this type is undefined. Where do we define this type? :-) 2. integral -> pointer: this may always be done. The result is implementation defined. [others omitted]. n. object pointer <-> function pointer: never allowed (but rules 1-2 allow pointer -> big integral -> pointer). dlsym() should return the large-enough integral type and let the caller cast it. Rule 2 should not be used to mask errors. The intermediate step actually makes the cast implementation defined instead of undefined. gcc on i*86's apparently prints more diagnostics for the undefined case but you can't depend on this - it can do whatever for the undefined case, including silently making it work, and it should warn for implementation defined cases iff a cast loses information. None of this should apply to the forms library unless you have dynamic forms and want to write pointers to the forms objects and functions to disk. Bruce From owner-freebsd-current Fri Mar 31 11:56:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA02261 for current-outgoing; Fri, 31 Mar 1995 11:56:16 -0800 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA02253 for ; Fri, 31 Mar 1995 11:56:12 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.11/8.6.11) id MAA29936; Fri, 31 Mar 1995 12:57:50 -0700 Date: Fri, 31 Mar 1995 12:57:50 -0700 Message-Id: <199503311957.MAA29936@rocky.sri.MT.net> To: current@FreeBSD.org Subject: CVS speedups ( was Re: cvs commit: src/gnu/usr.bin/cvs/cvs lock.c) Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk > Modified: gnu/usr.bin/cvs/cvs lock.c > Log: > The enclosed patch contains two separate improvements to CVS' ... Okay. Rather than make the changes available someplace where they'd get lost or forgotten, I decided to bring them in on a branch revision. That way we can merge them into the main branch easily and they won't get lost. If you want to try out a version of CVS with the performance enhancements by J.T. Conklin and you have access to the CVS repository, do a 'cvs co -r jt_spdup cvs'. Nate From owner-freebsd-current Fri Mar 31 15:21:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10766 for current-outgoing; Fri, 31 Mar 1995 15:21:25 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA10729 for ; Fri, 31 Mar 1995 15:20:17 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23267; Fri, 31 Mar 1995 23:09:44 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id XAA22994 for freebsd-current@FreeBSD.org; Fri, 31 Mar 1995 23:09:44 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id XAA09495 for freebsd-current@FreeBSD.org; Fri, 31 Mar 1995 23:07:37 +0200 From: J Wunsch Message-Id: <199503312107.XAA09495@uriah.heep.sax.de> Subject: Re: Floppy drive access overhead? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 31 Mar 1995 23:07:36 +0200 (MET DST) In-Reply-To: <199503311202.EAA02623@estienne.cs.berkeley.edu> from "Justin T. Gibbs" at Mar 31, 95 04:02:07 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 746 Sender: current-owner@FreeBSD.org Precedence: bulk As Justin T. Gibbs wrote: > [formatting floppies] > . Under FreeBSD, I get "jerky" system > behavior at best. Does anyone know why we have this problem > and how it can be fixed? I can't confirm this. Adaptecs however (at least the old ones) are known to be broken. They hog the bus for too long and cause the floppy driver to get DMA overruns all the time when heavy SCSI activity is going on. The floppy driver silently retries the failed transmissions, but it costs allot of time (and is absolutely not optimized -- it simply waits a whole revolution instead of trying other sectors first). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Mar 31 15:38:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA11118 for current-outgoing; Fri, 31 Mar 1995 15:38:57 -0800 Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA11112 for ; Fri, 31 Mar 1995 15:38:55 -0800 Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (8.6.11/8.6.10/MOT-3.6) with ESMTP id RAA02726 for ; Fri, 31 Mar 1995 17:38:19 -0600 Received: from hook.wdgarl.wes.mot.com (hook.wdgarl.wes.mot.com [129.188.122.160]) by pobox.mot.com (8.6.11/8.6.10/MOT-3.6) with SMTP id RAA25358 for ; Fri, 31 Mar 1995 17:38:18 -0600 Received: from malcolm.wdgarl.wes.mot.com by hook.wdgarl.wes.mot.com with SMTP (1.38.193.4/16.2) id AA19352; Fri, 31 Mar 1995 17:38:18 -0600 Message-Id: <9503312338.AA19352@hook.wdgarl.wes.mot.com> To: current@FreeBSD.org Subject: Re: rfc 1323 Support In-Reply-To: Your message of "Fri, 31 Mar 1995 11:47:02 CST." <9503311647.AA18415@halloran-eldar.lcs.mit.edu> Date: Fri, 31 Mar 1995 17:38:17 -0600 From: Mike Pearce Sender: current-owner@FreeBSD.org Precedence: bulk > > I've heard that TTCP over slip with header compress is a losing > > configuration anyhow. > > I'd love to know where you heard that since I'm not aware of anyone > anywhere who has yet created applications using T/TCP as a transport > mechanism. The WWW people would like to, but FreeBSD-current > constitutes the entire installed base outside of a few Suns at ISI and > on the DARTnet. (Sometimes it's lonely at the leading edge...) I've been experimenting with TTCP here. TTCP requires rfc1323 timestamps, so TCP header compression won't work with it. Header compression works when only certain parts of the TCP+IP header change in a predictable fashion. The timestamp options will be different for every packet, so the compressor will always be replacing the current packet template and sending it as type SL_TYPE_UNCOMPRESSED_TCP. 8-( Mike -- Mike Pearce, Staff Engineer, Motorola WDGARL, Schaumburg, IL email: pearce@hook.wdgarl.wes.mot.com From owner-freebsd-current Fri Mar 31 16:21:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA11938 for current-outgoing; Fri, 31 Mar 1995 16:21:12 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA11932 for ; Fri, 31 Mar 1995 16:21:11 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id QAA04851; Fri, 31 Mar 1995 16:12:44 -0800 Message-Id: <199504010012.QAA04851@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Floppy drive access overhead? In-reply-to: Your message of "Fri, 31 Mar 1995 23:07:36 +0200." <199503312107.XAA09495@uriah.heep.sax.de> Date: Fri, 31 Mar 1995 16:12:44 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >As Justin T. Gibbs wrote: >> >[formatting floppies] > >> . Under FreeBSD, I get "jerky" system >> behavior at best. Does anyone know why we have this problem >> and how it can be fixed? > >I can't confirm this. > >Adaptecs however (at least the old ones) are known to be broken. They >hog the bus for too long and cause the floppy driver to get DMA >overruns all the time when heavy SCSI activity is going on. The >floppy driver silently retries the failed transmissions, but it costs >allot of time (and is absolutely not optimized -- it simply waits a >whole revolution instead of trying other sectors first). Its a problem with msdosfs that David has a fix for. It was only happening when writing to msdos floppies. > >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Fri Mar 31 19:07:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA25775 for current-outgoing; Fri, 31 Mar 1995 19:07:28 -0800 Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA25768 for ; Fri, 31 Mar 1995 19:07:25 -0800 Received: (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.11/PHILMAIL-1.11) id TAA24876; Fri, 31 Mar 1995 19:07:16 -0800 Date: Fri, 31 Mar 1995 19:07:14 -0800 From: Richard Chang To: FreeBSD-current@freefall.cdrom.com Subject: snoop device Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Hi, I would like to know how to use the snoop device.... Can someone help me? Thanks. --richardc From owner-freebsd-current Fri Mar 31 19:14:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA26483 for current-outgoing; Fri, 31 Mar 1995 19:14:16 -0800 Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA26477 for ; Fri, 31 Mar 1995 19:14:11 -0800 Received: (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.11/PHILMAIL-1.11) id TAA25621; Fri, 31 Mar 1995 19:13:56 -0800 Date: Fri, 31 Mar 1995 19:13:52 -0800 From: Richard Chang To: FreeBSD-current@freefall.cdrom.com Subject: ppp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Hi, I need help getting ppp working under -current as it worked fine under 2.0-RELEASE. Here is the setup I'm using... bigbang# kermit so I use kermit to dial and start the ppp on the ppp server on my providers side and then hit ctrl-z to suspend kermit then I kill the kermit process... Is there a kermit that would allow me to quit it without dropping DTR since I do have AT&D0 set on the modem. bigbang# ppp This calls /usr/sbin/pppd /dev/cua00 115200 Here is my /etc/ppp/options file: bigbang# more /etc/ppp/options crtscts # enable hardware flow control modem # modem control line noipdefault # remote PPP server must supply your IP address. # if the remote host doesn't send your IP during IPCP # negotiation , remove this option passive # wait for LCP packets domain bigbang.HIP.Berkeley.EDU # put your domain name here #<136.152.64.1> #<136.152.76.173>:<136.152.64.1> # put the IP of remote PPP host here # it will be used to route packets via PPP link # if you didn't specified the noipdefault option # change this line to : defaultroute # put this if you want that PPP server will be your # default router bigbang# What am I doing wrong? Any help would be greatly appreciated. Thanks. --richardc From owner-freebsd-current Fri Mar 31 20:54:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA29464 for current-outgoing; Fri, 31 Mar 1995 20:54:56 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA29455 for ; Fri, 31 Mar 1995 20:54:48 -0800 Received: from jsdinc.root.com (uucp@localhost) by Root.COM (8.6.8/8.6.5) with UUCP id UAA18612; Fri, 31 Mar 1995 20:54:13 -0800 Received: (root@localhost) by jsdinc.root.com (8.6.11/8.6.5) id WAA01344; Fri, 31 Mar 1995 22:29:14 GMT From: "John S. Dyson" Message-Id: <199503312229.WAA01344@jsdinc.root.com> Subject: Re: Problem with newfs. To: inria.fr!Herve.Soulard@implode.root.com (Herve Soulard) Date: Fri, 31 Mar 1995 22:29:13 +0000 () Cc: current@FreeBSD.org In-Reply-To: <199503270509.HAA09648@alix.inria.fr> from "Herve Soulard" at Mar 27, 95 07:09:48 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 548 Sender: current-owner@FreeBSD.org Precedence: bulk > > > Hi, > > I've tried to install the last SNAP but it fails on newfs my > root partition with the following messages (plenty): > > wd0a: wdstart: timeout waiting for DRQ writing fsbn 304 of 304-319 > (wd0 bn 170432; cn 343 tn 9 sn 25) wd0: status 53 > error 4 > > The 950210 SNAP worked fine. > Try re-compiling wd.c with NSECS_MULTI == 1, there might be a problem with the drive working with the multi-block code. If it solves your problem, we'll probably have to make it the default. John dyson@root.com From owner-freebsd-current Sat Apr 1 01:02:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA29150 for current-outgoing; Sat, 1 Apr 1995 01:02:12 -0800 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 BAA29119 for ; Sat, 1 Apr 1995 01:02:04 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA23828; Sat, 1 Apr 95 11:00:44 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id LAA16697 for freebsd-current@freefall.cdrom.com; Sat, 1 Apr 1995 11:05:49 +0200 Message-Id: <199504010905.LAA16697@gilberto.physik.rwth-aachen.de> Subject: makewhatis (wrong indent value:``'') To: freebsd-current@freefall.cdrom.com (user alias) Date: Sat, 1 Apr 1995 11:05:48 +0200 (MET DST) From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 368 Sender: current-owner@FreeBSD.org Precedence: bulk cd /usr/src/share/man && make makedb makewhatis /usr/share/man Ignore wrong indent value: ``'' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Should one care about this? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Sat Apr 1 05:15:13 MET DST 1995 root@blues:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Sat Apr 1 01:12:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA29977 for current-outgoing; Sat, 1 Apr 1995 01:12:51 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA29970 for ; Sat, 1 Apr 1995 01:12:45 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA11502; Sat, 1 Apr 1995 11:12:35 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id LAA27284 for freebsd-current@FreeBSD.org; Sat, 1 Apr 1995 11:12:35 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id LAA14446 for freebsd-current@FreeBSD.org; Sat, 1 Apr 1995 11:11:29 +0200 From: J Wunsch Message-Id: <199504010911.LAA14446@uriah.heep.sax.de> Subject: Re: makewhatis (wrong indent value:``'') To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 1 Apr 1995 11:11:28 +0200 (MET DST) In-Reply-To: <199504010905.LAA16697@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Apr 1, 95 11:05:48 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 397 Sender: current-owner@FreeBSD.org Precedence: bulk As Christoph Kukulies wrote: > > cd /usr/src/share/man && make makedb > makewhatis /usr/share/man > Ignore wrong indent value: ``'' > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Should one care about this? Gonna look into this (or forward to Wolfram), thanks. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Apr 1 03:35:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA05265 for current-outgoing; Sat, 1 Apr 1995 03:35:41 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA05257 for ; Sat, 1 Apr 1995 03:35:36 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id TAA13313; Sat, 1 Apr 1995 19:19:28 +0800 Date: Sat, 1 Apr 1995 19:19:27 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: New installation notes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk I just spent the better part of my Saturday afternoon helping a colleague get started with FreeBSD. 90% of the problems were, as usual, due to the idiosyncratic PC hardware architecture. ;-) I want to fire off this note while the experience is still fresh in my mind because there are a few things that can be improved upon. Hardware is a 90-MHz Pentium, ASUS motherboard (not sure which one, but it uses the SiS chipset), Adaptec AHA-2940 controller, two Quantum Maverick 540-meg drives (sd0 is FreeBSD, sd1 is MS-DOS), Accton NE2000-compatible Ethernet, Phoenix Vision864 S3 PCI graphics card (1 megabyte) and 16 megabytes of RAM. Initially the kernel was having trouble with the 2940, reportings errors during boot such as "cmd fail" or "ahc0: board not responding". After fiddling with the system for half an hour, it was finally able to boot up to the installation stage. I'm not quite sure what I did to make it work. I suspect it may have something to do with changing its IRQ from 12 to 10, and/or pulling out the SB/AWE32 sound card (which is on IRQ 5) and the attached NEC Multispin 4x CD-ROM drive. When the installer finally did come up, both drives showed up as sd0 and sd1 with the expected partitioning. I fdisked sd0 and told it to use the entire drive for FreeBSD. However, when I went to disklabel sd0, it defaulted with an MSDOS partition (sd0e) the size of the entire slice. I deleted it and then went to allocate the filesystems. Was I supposed to leave a small MS-DOS filesystem for the boot manager? My intention was to have the boot manager come up and ask me to select DOS (booting off the second drive) or BSD (booting off the first drive). Is this possible, and if so, how do I specify this? Does it have something to do with importing an MS-DOS disk slice as a FreeBSD partition? Currently, the computer boots straight into FreeBSD. After the disklabelling, I chose an NFS install. Everything went smoothly up to point where it asks for the pathname to the dist files. I typed in an incorrect pathname, it said it couldn't find the files, then proceeded to the final step! Would it be possible to have it loop back to the package selection routine or (better yet) prompt the user again for a pathname? I restarted the installer, went through the same questions about network parameters, but again I made a small typo (so I'm stupid, but that's not the issue ;-)). I didn't feel like doing it all over again, so I just dropped to a shell and completed the rest of the install by hand. Better error handling, IMHO, would go a long way towards dispelling FreeBSD's hard-to-install reputation. For example, if I type in the wrong IP address or hostname, I have to start all over again to correct one mistake. Or if the network card's IRQ doesn't match what's in the kernel, ifconfig will fail with repeated "device timeout" errors. Could the installer catch these errors and handle them gracefully? Once everything was installed, I rebooted with kernel -c (to accomodate ed1 on IRQ 15), edited a handful of /etc files, rebooted again and created the user accounts. All in all, pretty smooth sailing once the kernel could recognize the Adaptec. I ran iozone to check it out but it could only muster around 1.7MB/sec read/write while my 486DX4/100 NCR-equipped system hits 2.5-2.6MB/sec. Both used "iozone 50 65536" and were handling a normal multiuser load with no swapping occurring. I need to recompile the kernel anyway and I'll try Justin's new aic7xxx drivers at the same time. BTW, the proud owner is thoroughly impressed with what he can do with his machine now. :) In fact, he hinted that wiping out his MS-DOS drive and replacing it with more UNIX file space is a definite possibility. :) -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Sat Apr 1 04:32:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09356 for current-outgoing; Sat, 1 Apr 1995 04:32:34 -0800 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 EAA09347 for ; Sat, 1 Apr 1995 04:32:22 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA08606; Sat, 1 Apr 1995 22:30:09 +1000 Date: Sat, 1 Apr 1995 22:30:09 +1000 From: Bruce Evans Message-Id: <199504011230.WAA08606@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw Subject: Re: New installation notes Sender: current-owner@FreeBSD.org Precedence: bulk > When the installer finally did come up, both drives showed up as >sd0 and sd1 with the expected partitioning. I fdisked sd0 and told it >to use the entire drive for FreeBSD. However, when I went to >disklabel sd0, it defaulted with an MSDOS partition (sd0e) the size of >the entire slice. I deleted it and then went to allocate the >filesystems. Was I supposed to leave a small MS-DOS filesystem for >the boot manager? My intention was to have the boot manager come up >and ask me to select DOS (booting off the second drive) or BSD >(booting off the first drive). Is this possible, and if so, how do I >specify this? Does it have something to do with importing an MS-DOS >disk slice as a FreeBSD partition? Currently, the computer boots >straight into FreeBSD. The whole drive can't be used for BSD if there is a boot manager because if the whole drive is used for BSD then there is no space left for the boot manager. An MSDOS partition shouldn't be necessary and shouldn't be created. Just create a BSD partition starting somewhere after the boot manager. Bruce From owner-freebsd-current Sat Apr 1 05:05:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA10255 for current-outgoing; Sat, 1 Apr 1995 05:05:32 -0800 Received: from vinkku.hut.fi (vode@vinkku.hut.fi [130.233.245.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA10247 for ; Sat, 1 Apr 1995 05:05:27 -0800 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id QAA05147; Sat, 1 Apr 1995 16:05:16 +0300 Date: Sat, 1 Apr 1995 16:05:16 +0300 From: Kai Vorma Message-Id: <199504011305.QAA05147@vinkku.hut.fi> To: current@FreeBSD.org Subject: panic: update: rofs mod Reply-to: Kai.Vorma@hut.fi Sender: current-owner@FreeBSD.org Precedence: bulk I upgraded my kernel today to latest level (sources supped at Sat Apr 1 12:21:11 EET DST) and rebooted my machine. Because it was my first kernel using disk slices I decided to play safe and boot into single-user mode. I got lots of warnings from sd0d sd0d: start 0, end 2117631, size 2117632 sd0: rejecting partition in BSD label: it isn't entirely within the slice but otherwise all seemed OK. I run 'disklabel sd0' to see that all partitions were still there and rebooted again: # reboot syncing disks... done fs = / panic: update: rofs mod [ I managed to get system core dump if somebody is interested ] Then I brought the system to multi-user and used disklabel -e to get rid of that offending sd0d partition. Then I rebooted again to singe-user and found out that reboot no longer causes panic. The only strange thing now is that the slice code prints out my partitions thrice: sd0s1: start 32, end = 204799, size 204768: OK sd0s2: start 204800, end = 2117631, size 1912832: OK sd0s1: start 32, end = 204799, size 204768: OK sd0s2: start 204800, end = 2117631, size 1912832: OK sd0s1: start 32, end = 204799, size 204768: OK sd0s2: start 204800, end = 2117631, size 1912832: OK Is that normal? ..vode From owner-freebsd-current Sat Apr 1 05:23:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA10622 for current-outgoing; Sat, 1 Apr 1995 05:23:12 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA10609 for ; Sat, 1 Apr 1995 05:23:05 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id FAA19194; Sat, 1 Apr 1995 05:22:53 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id FAA01508; Sat, 1 Apr 1995 05:22:53 -0800 Message-Id: <199504011322.FAA01508@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Kai.Vorma@hut.fi cc: current@FreeBSD.org Subject: Re: panic: update: rofs mod In-reply-to: Your message of "Sat, 01 Apr 95 16:05:16 +0300." <199504011305.QAA05147@vinkku.hut.fi> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 01 Apr 1995 05:22:52 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk ># reboot >syncing disks... done >fs = / >panic: update: rofs mod There is a check in FFS for attempts to write out dirty buffers on a read-only filesystem. I was able to get the machine to panic with the above on reboot by using tunefs on / (I must have incorrectly used the block special device). I suppose there is a bug somewhere not returning EROFS when writing to RO-mounted block devices. I seem to recall that prior to 4.4-lite the system wouldn't let you do anything with a mounted block device. -DG From owner-freebsd-current Sat Apr 1 06:05:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA11997 for current-outgoing; Sat, 1 Apr 1995 06:05:44 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA11981 for ; Sat, 1 Apr 1995 06:05:36 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id VAA13866; Sat, 1 Apr 1995 21:13:27 +0800 Date: Sat, 1 Apr 1995 21:13:27 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: /usr/src/sys/sys/vnioctl.h Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk First time compiling a -current kernel... hope I'm not missing something obvious. I want vnode support in the new kernel, but I get this when trying to compile /usr/src/sys/dev/vn/vn.c: ../../dev/vn/vn.c: In function `vnioctl': ../../dev/vn/vn.c:443: `VNIOCSET' undeclared (first use this function) ../../dev/vn/vn.c:443: (Each undeclared identifier is reported only once ../../dev/vn/vn.c:443: for each function it appears in.) ../../dev/vn/vn.c:492: `VNIOCCLR' undeclared (first use this function) ../../dev/vn/vn.c:510: warning: unreachable code at beginning of switch statement *** Error code 1 Looking in : /* * Before you can use a unit, it must be configured with VNIOCSET. * The configuration persists across opens and closes of the device; * an VNIOCCLR must be used to reset a configuration. An attempt to * VNIOCSET an already active unit will return EBUSY. */ #define VNIOCATTACH _IOWR('F', 0, struct vn_ioctl) /* attach file */ #define VNIOCDETACH _IOWR('F', 1, struct vn_ioctl) /* detach disk */ #define VNIOCGSET _IOWR('F', 2, u_long ) /* set global option */ #define VNIOCGCLEAR _IOWR('F', 3, u_long ) /* reset --//-- */ #define VNIOCUSET _IOWR('F', 4, u_long ) /* set unit option */ #define VNIOCUCLEAR _IOWR('F', 5, u_long ) /* reset --//-- */ The #defines for VNIOCSET and VNIOCCLR are nowhere to be found. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Sat Apr 1 06:38:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA12644 for current-outgoing; Sat, 1 Apr 1995 06:38:06 -0800 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 GAA12638 for ; Sat, 1 Apr 1995 06:37:55 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA12680; Sun, 2 Apr 1995 00:33:30 +1000 Date: Sun, 2 Apr 1995 00:33:30 +1000 From: Bruce Evans Message-Id: <199504011433.AAA12680@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw Subject: Re: /usr/src/sys/sys/vnioctl.h Sender: current-owner@FreeBSD.org Precedence: bulk > First time compiling a -current kernel... hope I'm not missing >something obvious. I want vnode support in the new kernel, but I get >this when trying to compile /usr/src/sys/dev/vn/vn.c: >../../dev/vn/vn.c: In function `vnioctl': >../../dev/vn/vn.c:443: `VNIOCSET' undeclared (first use this function) >... You somehow have an old version of vn.c. > Looking in : >/* > * Before you can use a unit, it must be configured with VNIOCSET. > * The configuration persists across opens and closes of the device; > * an VNIOCCLR must be used to reset a configuration. An attempt to > * VNIOCSET an already active unit will return EBUSY. > */ >#define VNIOCATTACH _IOWR('F', 0, struct vn_ioctl) /* attach file */ >#define VNIOCDETACH _IOWR('F', 1, struct vn_ioctl) /* detach disk */ >#define VNIOCGSET _IOWR('F', 2, u_long ) /* set global option */ >#define VNIOCGCLEAR _IOWR('F', 3, u_long ) /* reset --//-- */ >#define VNIOCUSET _IOWR('F', 4, u_long ) /* set unit option */ >#define VNIOCUCLEAR _IOWR('F', 5, u_long ) /* reset --//-- */ > The #defines for VNIOCSET and VNIOCCLR are nowhere to be found. This is the current version. The comment no longer matches the code. Bruce From owner-freebsd-current Sat Apr 1 06:47:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA12754 for current-outgoing; Sat, 1 Apr 1995 06:47:52 -0800 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 GAA12748 for ; Sat, 1 Apr 1995 06:47:47 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA12819; Sun, 2 Apr 1995 00:43:34 +1000 Date: Sun, 2 Apr 1995 00:43:34 +1000 From: Bruce Evans Message-Id: <199504011443.AAA12819@godzilla.zeta.org.au> To: Kai.Vorma@hut.fi Subject: Re: panic: update: rofs mod Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >sd0d: start 0, end 2117631, size 2117632 >sd0: rejecting partition in BSD label: it isn't entirely within the slice >but otherwise all seemed OK. I run 'disklabel sd0' to see that all >partitions were still there and rebooted again: ># reboot >syncing disks... done >fs = / >panic: update: rofs mod Did you get this without writing to the block device? `disklabel sd0' should use the character device (and not write to it). >Then I brought the system to multi-user and used disklabel -e to get >rid of that offending sd0d partition. Then I rebooted again to >singe-user and found out that reboot no longer causes panic. This is hard to explain. >The only strange thing now is that the slice code prints out my >partitions thrice: >sd0s1: start 32, end = 204799, size 204768: OK >sd0s2: start 204800, end = 2117631, size 1912832: OK >sd0s1: start 32, end = 204799, size 204768: OK >sd0s2: start 204800, end = 2117631, size 1912832: OK >sd0s1: start 32, end = 204799, size 204768: OK >sd0s2: start 204800, end = 2117631, size 1912832: OK >Is that normal? Yes. See old FreeBSD-current mail. Bruce From owner-freebsd-current Sat Apr 1 06:56:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA12945 for current-outgoing; Sat, 1 Apr 1995 06:56:33 -0800 Received: from vinkku.hut.fi (vode@vinkku.hut.fi [130.233.245.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA12939 for ; Sat, 1 Apr 1995 06:56:31 -0800 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id RAA08554; Sat, 1 Apr 1995 17:55:53 +0300 Date: Sat, 1 Apr 1995 17:55:53 +0300 From: Kai Vorma Message-Id: <199504011455.RAA08554@vinkku.hut.fi> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: panic: update: rofs mod In-Reply-To: <199504011443.AAA12819@godzilla.zeta.org.au> References: <199504011443.AAA12819@godzilla.zeta.org.au> Reply-To: Kai.Vorma@hut.fi Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: > Did you get this without writing to the block device? `disklabel sd0' > should use the character device (and not write to it). Yes. Does the slice code try to update disklabel when it found illegal entry (I had illegal d-partition and now obsolete h-partition for DOS-partition) or something? I cannot remember doing any write before rebooting. > Yes. See old FreeBSD-current mail. Sorry, I have deleted old mails and the FreeBSD Mail Archives WWW-page on www.freebsd.com is badly out of date. ..vode From owner-freebsd-current Sat Apr 1 07:15:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA13820 for current-outgoing; Sat, 1 Apr 1995 07:15:02 -0800 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 HAA13801 for ; Sat, 1 Apr 1995 07:14:51 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA13249; Sun, 2 Apr 1995 01:08:15 +1000 Date: Sun, 2 Apr 1995 01:08:15 +1000 From: Bruce Evans Message-Id: <199504011508.BAA13249@godzilla.zeta.org.au> To: Kai.Vorma@hut.fi Subject: Re: panic: update: rofs mod Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > > Did you get this without writing to the block device? `disklabel sd0' > > should use the character device (and not write to it). >Yes. Does the slice code try to update disklabel when it found illegal >entry (I had illegal d-partition and now obsolete h-partition for >DOS-partition) or something? I cannot remember doing any write before >rebooting. The slice code should never write to the disk unless you tell it to. Both the d-partition and any DOS-partitions outside the BSD slice are now obsolete. The slice code complains about them because it doesn't know exactly what to do about them. You might want to keep them for compatibility. This is easy to do by ignoring the warning and not running disklabel to kill the warning OR to make any other changes. The label writing routine is fussier than the label reading routine and won't allow writing the obsolete partitions. You might not even notice that they were gone if there was no warning. Bruce From owner-freebsd-current Sat Apr 1 07:35:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA14657 for current-outgoing; Sat, 1 Apr 1995 07:35:41 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA14649 for ; Sat, 1 Apr 1995 07:35:38 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id WAA14333; Sat, 1 Apr 1995 22:27:49 +0800 Date: Sat, 1 Apr 1995 22:27:48 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: 2.0-950322-SNAP kernel source? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk I feel stupid for asking this, but where are the kernel sources for the 950322 snapshot? I had them on my system, but then removed them once I had the kernel tweaked, but now I need them again and I can't find them anywhere on the FTP site. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Sat Apr 1 07:41:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA14845 for current-outgoing; Sat, 1 Apr 1995 07:41:02 -0800 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 HAA14838 for ; Sat, 1 Apr 1995 07:41:00 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with SMTP id RAA17415 ; Sat, 1 Apr 1995 17:41:22 +0200 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA09660; Sat, 1 Apr 95 17:40:49 +0200 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.6.11/keltia-uucp-1.21) id RAA05603; Sat, 1 Apr 1995 17:39:53 +0200 From: Ollivier Robert Message-Id: <199504011539.RAA05603@keltia.frmug.fr.net> Subject: Re: CVS speedups ( was Re: cvs commit: src/gnu/usr.bin/cvs/cvs lock.c) To: nate@sneezy.sri.com Date: Sat, 1 Apr 1995 17:39:51 +0200 (MET DST) Cc: CVS-commiters@freefall.cdrom.com, freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Reply-To: roberto@blaise.ibp.fr (Ollivier Robert) In-Reply-To: <199503311954.MAA29912@rocky.sri.MT.net> from "Nate Williams" at Mar 31, 95 12:54:46 pm X-Operating-System: FreeBSD 2.1.0-Development ctm#487 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: 446 Sender: current-owner@FreeBSD.org Precedence: bulk It seems that Nate Williams said: > So, if you want to try out a version of CVS with the performance > enhancements by J.T. Conklin and you have access to the CVS repository, > do a 'cvs co -r jt_sbdup cvs'. Make it "'cvs co -r jt_spdup cvs" and all will be OK :-) ^ -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.1.0-Development #11: Sat Mar 25 20:19:59 MET 1995 From owner-freebsd-current Sat Apr 1 08:48:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17059 for current-outgoing; Sat, 1 Apr 1995 08:48:12 -0800 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 IAA17049 for ; Sat, 1 Apr 1995 08:47:55 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id SAA06261; Sat, 1 Apr 1995 18:46:22 +0200 Message-Id: <199504011646.SAA06261@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: Bruce Evans cc: Kai.Vorma@hut.fi, current@FreeBSD.org Subject: Re: panic: update: rofs mod Date: Sat, 01 Apr 1995 18:46:21 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > Both the d-partition and any DOS-partitions outside the BSD slice are > now obsolete. The slice code complains about them because it doesn't > know exactly what to do about them. You might want to keep them for > compatibility. This is easy to do by ignoring the warning and not > running disklabel to kill the warning OR to make any other changes. > The label writing routine is fussier than the label reading routine > and won't allow writing the obsolete partitions. You might not even > notice that they were gone if there was no warning. I've been watching this thread for a while, hoping to learn something. I picked up quite a bit, thanks. I had similar problems to Kai, but I remembered the changes, so no panic. what I cannot get round is this: (please bear with me) I am running current (ctm 471) with a 2-3 day old kernel. > Mar 31 12:42:49 grunt /kernel: sd0s4: start 1, end = 412359, size 412359: OK > Mar 31 12:42:49 grunt /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice (**) > Mar 31 12:42:50 grunt /kernel: sd0: start 1, end 412359, size 412359 > Mar 31 12:42:50 grunt /kernel: sd0d: start 0, end 415599, size 415600 (x3) (**) This I can fix by getting rid of the "d" partition, right? EXCEPT I get this when I exit disklabel: > # /dev/rsd0c: > type: SCSI > disk: > label: MBR based label > flags: > bytes/sector: 512 > sectors/track: 61 > tracks/cylinder: 4 > sectors/cylinder: 244 > cylinders: 1689 > sectors/unit: 412359 > rpm: 3600 (was zero) > interleave: 1 (was zero) > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 4 partitions: (was eight) > # Hsize offset fstype [fsize bsize bps/cpg] > a: 40960 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 167*) > b: 65536 40960 swap # (Cyl. 167*- 436*) > c: 412359 0 unused # (Cyl. 0 - 1689*) > e: 305152 106496 4.2BSD 1024 8192 16 # (Cyl. 436*- 1687*) [exit] > Warning, unused partition e: size 305152 offset 106496 > disklabel: ioctl DIOCSDINFO: Open partition would move or shrink > re-edit the label? [y]: n 1) What does the DIOCSDINFO mean? 2) e is most certainly not unused! The logfile continues: > Mar 31 12:42:50 grunt /kernel: sd1s4: start 1, end = 2045651, size 2045651 > Mar 31 12:42:50 grunt /kernel: sd1s4: C/H/S end 933/6/34 (222291) != end 2045651: invalid (+++) > Mar 31 12:42:51 grunt /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice (**) > Mar 31 12:42:51 grunt /kernel: sd1: start 1, end 2045651, size 2045651 > Mar 31 12:42:51 grunt /kernel: sd1d: start 0, end 2056007, size 2056008 (x2) (**) above is the same 'd' partition problem as above, and I cannot get rid of it either for the same reasons. (+++) is wierd. Ths is a 1GB SCSI disk, and the variable (or whatever) used to hold the number of tracks seems a little messed up. Here is an fdisk session > bash# fdisk -u /dev/rsd1c > ******* Working on device /dev/rsd1c ******* > parameters extracted from in-core disklabel are: > cylinders=2981 heads=7 sectors/track=98 (686 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=2981 heads=7 sectors/track=98 (686 blks/cyl) ** These are OK > > Do you want to change our idea of what BIOS thinks ? [n] > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 0 is: > > Do you want to change it? [n] > The data for partition 1 is: > > Do you want to change it? [n] > The data for partition 2 is: > > Do you want to change it? [n] > The data for partition 3 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 1, size 2045651 (998 Meg), flag 80 > beg: cyl 0/ sector 2/ head 0; > end: cyl 933/ sector 34/ head 6 > Do you want to change it? [n] y > Supply a decimal value for "sysid" [165] > Supply a decimal value for "start" [1] > Supply a decimal value for "size" [2045651] > Explicitly specifiy beg/end address ? [n] y > Supply a decimal value for "beginning cylinder" [0] > Supply a decimal value for "beginning head" [0] > Supply a decimal value for "beginning sector" [2] > Supply a decimal value for "ending cylinder" [933] 2981 ** Look here! > Supply a decimal value for "ending head" [6] > Supply a decimal value for "ending sector" [34] > sysid 165,(FreeBSD/NetBSD/386BSD) > start 1, size 2045651 (998 Meg), flag 80 > beg: cyl 0/ sector 2/ head 0; > end: cyl 933/ sector 34/ head 6 ** WTF?? > Are we happy with this entry? [n] ** Of course not! > Supply a decimal value for "sysid" [165] ^C ** Outta here! Any pointers? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sat Apr 1 09:15:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA18251 for current-outgoing; Sat, 1 Apr 1995 09:15:07 -0800 Received: from rivers.oscs.montana.edu (rivers.oscs.montana.edu [192.31.215.70]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA18243 for ; Sat, 1 Apr 1995 09:15:06 -0800 Received: by rivers.oscs.montana.edu (5.65/DEC-Ultrix/4.3) id AA14705; Sat, 1 Apr 1995 10:14:13 -0700 Date: Sat, 1 Apr 1995 10:14:12 -0700 (MST) From: Jason Boerner To: Bruce Evans Cc: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw Subject: Re: New installation notes In-Reply-To: <199504011230.WAA08606@godzilla.zeta.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Sat, 1 Apr 1995, Bruce Evans wrote: > > The whole drive can't be used for BSD if there is a boot manager > because if the whole drive is used for BSD then there is no space > left for the boot manager. An MSDOS partition shouldn't be necessary > and shouldn't be created. Just create a BSD partition starting > somewhere after the boot manager. > How is this done? Thanks From owner-freebsd-current Sat Apr 1 09:25:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA18601 for current-outgoing; Sat, 1 Apr 1995 09:25:31 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA18595 for ; Sat, 1 Apr 1995 09:25:29 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id JAA10069; Sat, 1 Apr 1995 09:24:56 -0800 Message-Id: <199504011724.JAA10069@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: Brian Tao cc: FREEBSD-CURRENT-L Subject: Re: New installation notes In-reply-to: Your message of "Sat, 01 Apr 1995 19:19:27 +0800." Date: Sat, 01 Apr 1995 09:24:56 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk > I just spent the better part of my Saturday afternoon helping a >colleague get started with FreeBSD. 90% of the problems were, as >usual, due to the idiosyncratic PC hardware architecture. ;-) I want >to fire off this note while the experience is still fresh in my mind >because there are a few things that can be improved upon. > > Hardware is a 90-MHz Pentium, ASUS motherboard (not sure which >one, but it uses the SiS chipset), Adaptec AHA-2940 controller, two >Quantum Maverick 540-meg drives (sd0 is FreeBSD, sd1 is MS-DOS), >Accton NE2000-compatible Ethernet, Phoenix Vision864 S3 PCI graphics >card (1 megabyte) and 16 megabytes of RAM. > > Initially the kernel was having trouble with the 2940, reportings >errors during boot such as "cmd fail" or "ahc0: board not responding". >After fiddling with the system for half an hour, it was finally able >to boot up to the installation stage. I'm not quite sure what I did >to make it work. I suspect it may have something to do with changing >its IRQ from 12 to 10, and/or pulling out the SB/AWE32 sound card >(which is on IRQ 5) and the attached NEC Multispin 4x CD-ROM drive. > Did you ever reattach the Nec 4x? It was either that or a conflicting IRQ. > Once everything was installed, I rebooted with kernel -c (to >accomodate ed1 on IRQ 15), edited a handful of /etc files, rebooted >again and created the user accounts. All in all, pretty smooth >sailing once the kernel could recognize the Adaptec. I ran iozone to >check it out but it could only muster around 1.7MB/sec read/write >while my 486DX4/100 NCR-equipped system hits 2.5-2.6MB/sec. Both used >"iozone 50 65536" and were handling a normal multiuser load with no >swapping occurring. I need to recompile the kernel anyway and I'll >try Justin's new aic7xxx drivers at the same time. Were you using the exact same drives? The best test would be to place the controllers in the same machine and test against the same exact drives. I'm been getting ~5MB/s out of the driver for some time now to a Quantum Empire 2100. > > BTW, the proud owner is thoroughly impressed with what he can do >with his machine now. :) In fact, he hinted that wiping out his >MS-DOS drive and replacing it with more UNIX file space is a definite >possibility. :) Another convert!!! :) >-- >Brian ("Though this be madness, yet there is method in't") Tao >taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org > -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Sat Apr 1 09:37:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA21307 for current-outgoing; Sat, 1 Apr 1995 09:37:32 -0800 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 JAA21298 for ; Sat, 1 Apr 1995 09:37:26 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA16054 for current@freebsd.org; Sun, 2 Apr 1995 03:34:20 +1000 Date: Sun, 2 Apr 1995 03:34:20 +1000 From: Bruce Evans Message-Id: <199504011734.DAA16054@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: sysconfig Sender: current-owner@FreeBSD.org Precedence: bulk I'm now fairly happy with the way /etc/rc stuff is done. I've noticed a problem with the way sysconfig is used: netstart, (etc.) doesn't source it directly, so netstart only work when sourced from rc. netstart should probably source sysconfig for itself and be run by `sh' instead of `.' from rc. The "#!/bin/sh" line in netstart is bogus now because netstart isn't self-supporting; it is also bogus because netstart is installed with perms 644. Bruce From owner-freebsd-current Sat Apr 1 10:05:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23116 for current-outgoing; Sat, 1 Apr 1995 10:05:46 -0800 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA23110 for ; Sat, 1 Apr 1995 10:05:40 -0800 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id BAA18768; Sun, 2 Apr 1995 01:22:25 +0800 Date: Sun, 2 Apr 1995 01:22:24 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Re: New installation notes In-Reply-To: <199504011230.WAA08606@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Sat, 1 Apr 1995, Bruce Evans wrote: > > The whole drive can't be used for BSD if there is a boot manager > because if the whole drive is used for BSD then there is no space > left for the boot manager. An MSDOS partition shouldn't be necessary > and shouldn't be created. Just create a BSD partition starting > somewhere after the boot manager. How do I tell the boot manager that the DOS partition is on another drive? It never bothers to ask. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Sat Apr 1 10:48:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23728 for current-outgoing; Sat, 1 Apr 1995 10:48:19 -0800 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 KAA23701 for ; Sat, 1 Apr 1995 10:47:59 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA17673; Sun, 2 Apr 1995 04:42:06 +1000 Date: Sun, 2 Apr 1995 04:42:06 +1000 From: Bruce Evans Message-Id: <199504011842.EAA17673@godzilla.zeta.org.au> To: bde@zeta.org.au, mark@grondar.za Subject: Re: panic: update: rofs mod Cc: Kai.Vorma@hut.fi, current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >I had similar problems to Kai, but I remembered the changes, so no panic. >what I cannot get round is this: (please bear with me) >I am running current (ctm 471) with a 2-3 day old kernel. >> Mar 31 12:42:49 grunt /kernel: sd0s4: start 1, end = 412359, size 412359: OK >> Mar 31 12:42:49 grunt /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice (**) >> Mar 31 12:42:50 grunt /kernel: sd0: start 1, end 412359, size 412359 >> Mar 31 12:42:50 grunt /kernel: sd0d: start 0, end 415599, size 415600 >(x3) >(**) This I can fix by getting rid of the "d" partition, right? Yes. >EXCEPT I get this when I exit disklabel: >> ... >> 4 partitions: (was eight) >> # Hsize offset fstype [fsize bsize bps/cpg] >> a: 40960 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 167*) >> b: 65536 40960 swap # (Cyl. 167*- 436*) >> c: 412359 0 unused # (Cyl. 0 - 1689*) >> e: 305152 106496 4.2BSD 1024 8192 16 # (Cyl. 436*- 1687*) >[exit] >> Warning, unused partition e: size 305152 offset 106496 >> disklabel: ioctl DIOCSDINFO: Open partition would move or shrink >> re-edit the label? [y]: n >1) What does the DIOCSDINFO mean? It's the name of the ioctl that failed. This is perhaps more useful to know about than "Open partition would move or shrink". There is no errno to describe the failure in this much detail, so disklabel(1) guesses an error message which in this case is worse than useless. >2) e is most certainly not unused! You need 5 partitions to reach the 'e' partition (a-e, with d empty). I always use 8. This doesn't waste any space. >The logfile continues: >> Mar 31 12:42:50 grunt /kernel: sd1s4: start 1, end = 2045651, size 2045651 >> Mar 31 12:42:50 grunt /kernel: sd1s4: C/H/S end 933/6/34 (222291) != end 2045651: invalid (+++) >> ... >(+++) is wierd. Ths is a 1GB SCSI disk, and the variable (or whatever) used >to hold the number of tracks seems a little messed up. >Here is an fdisk session >> bash# fdisk -u /dev/rsd1c >> ... >> cylinders=2981 heads=7 sectors/track=98 (686 blks/cyl) ** These are OK >> ... >> The data for partition 3 is: >> sysid 165,(FreeBSD/NetBSD/386BSD) >> start 1, size 2045651 (998 Meg), flag 80 >> beg: cyl 0/ sector 2/ head 0; >> end: cyl 933/ sector 34/ head 6 >> ... >> Supply a decimal value for "size" [2045651] >> Explicitly specifiy beg/end address ? [n] y >> Supply a decimal value for "beginning cylinder" [0] >> Supply a decimal value for "beginning head" [0] >> Supply a decimal value for "beginning sector" [2] >> Supply a decimal value for "ending cylinder" [933] 2981 ** Look here! >> Supply a decimal value for "ending head" [6] >> Supply a decimal value for "ending sector" [34] >> sysid 165,(FreeBSD/NetBSD/386BSD) >> start 1, size 2045651 (998 Meg), flag 80 >> beg: cyl 0/ sector 2/ head 0; >> end: cyl 933/ sector 34/ head 6 ** WTF?? >> Are we happy with this entry? [n] ** Of course not! >> Supply a decimal value for "sysid" [165] ^C ** Outta here! First, the ending cylinder can't be 2981 because there are only 10 bits for it in the partition table so it must be < 1024. fdisk silently truncates it mod 1024 when it calculates it from `start+size' and silently truncates it mod 1024 when you try to fix it. There is a compatibility kludge that allows large cylinders if they are only correct mod 1024. See old commit mail. For this to work, at least one of the partitions should have ending head and cylinder numbers that agree with the BIOS geometry. fdisk should enforce this (it doesn't). You only have one partition, and its ending H/S is 6/34 which is unrelated to the geometry (H=7, S=98) so the compatibility kludge fails. The bootstrap apparently manages to succeed because the 6/34 is good enough to translate the label sector number (because the label is on a very early sector). If the BSD slice isn't first, then it is essential for some ending H/S to be maximal, but this usually occurs because the OS's that created the other slices did a better job of setting the ending H/S suitably for FreeBSD than FreeBSD does for itself :-(. 2981/7/98 is an unusual geometry for 1GB scsi drives/controllers. Most controllers translate to nnnn/64/32 where nnnn < 1024 so there are less problems, especially if you don't try to use all the sectors on the disk and round to an (apparent) cylinder boundary. Rounding to a cylinder boundary should have worked for your disk too, but you can't use it if you have something on the disk above the rounding point. There is another compatibility kludge that allows large cylinders if they are replaced by 1023 and the ending H/S are replaced by the maximum H/S values. See old commit mail. This kludge probably applies in your case: set the ending C/H/S to 1023/6/98 and leave the size alone. Bruce From owner-freebsd-current Sat Apr 1 11:22:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25497 for current-outgoing; Sat, 1 Apr 1995 11:22:33 -0800 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 LAA25484 for ; Sat, 1 Apr 1995 11:22:23 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA18604; Sun, 2 Apr 1995 05:20:23 +1000 Date: Sun, 2 Apr 1995 05:20:23 +1000 From: Bruce Evans Message-Id: <199504011920.FAA18604@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw Subject: Re: New installation notes Sender: current-owner@FreeBSD.org Precedence: bulk >> The whole drive can't be used for BSD if there is a boot manager >> because if the whole drive is used for BSD then there is no space >> left for the boot manager. An MSDOS partition shouldn't be necessary > How do I tell the boot manager that the DOS partition is on >another drive? It never bothers to ask. It depends on the boot manager. A good one should allow booting from all nonempty partitions on all drives. Bruce From owner-freebsd-current Sat Apr 1 11:32:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26306 for current-outgoing; Sat, 1 Apr 1995 11:32:43 -0800 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 LAA26292 for ; Sat, 1 Apr 1995 11:32:37 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA18841; Sun, 2 Apr 1995 05:27:10 +1000 Date: Sun, 2 Apr 1995 05:27:10 +1000 From: Bruce Evans Message-Id: <199504011927.FAA18841@godzilla.zeta.org.au> To: bde@zeta.org.au, chaos@rivers.oscs.montana.edu Subject: Re: New installation notes Cc: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw Sender: current-owner@FreeBSD.org Precedence: bulk >> The whole drive can't be used for BSD if there is a boot manager >> because if the whole drive is used for BSD then there is no space >> left for the boot manager. An MSDOS partition shouldn't be necessary >> and shouldn't be created. Just create a BSD partition starting >> somewhere after the boot manager. >> >How is this done? I'm not sure how to do it with sysinstall. With FreeBSD fdisk, pick a good starting place (the second track on the first cylinder is good) and create a FreeBSD partition as usual. FreeBSD partitions are just partitions with type 165. You can start with a suitably placed foreign partition and change the type (don't go the other way, there may be internal requirements). Bruce From owner-freebsd-current Sat Apr 1 12:00:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27355 for current-outgoing; Sat, 1 Apr 1995 12:00:00 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA27349 for ; Sat, 1 Apr 1995 11:59:59 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id LAA10683 for ; Sat, 1 Apr 1995 11:59:50 -0800 Message-Id: <199504011959.LAA10683@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: FTP data sessions Date: Sat, 01 Apr 1995 11:59:50 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk FTP data transmissions hang going across my SLIP line to other 2.0R+ machines. Connect and login work fine. __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Sat Apr 1 13:47:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01860 for current-outgoing; Sat, 1 Apr 1995 13:47:15 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01854 for ; Sat, 1 Apr 1995 13:47:13 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id NAA11027 for ; Sat, 1 Apr 1995 13:47:03 -0800 Message-Id: <199504012147.NAA11027@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: rfc1644 Date: Sat, 01 Apr 1995 13:47:03 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk A sysctl -w net.inet.tcp.rfc1644=0 fixes the ftp and remote X hangs over slip for me. Is rfc1644 dependant on rfc1323 at all? I guess its time for me to go read up on the rfcs. Hmm Garrett's home page doesn't list these two. Anyone have a source? BTW, these are DEFINITE FAQ entries. __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Sat Apr 1 19:26:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA21007 for current-outgoing; Sat, 1 Apr 1995 19:26:29 -0800 Received: from merde.dis.org (root@[204.188.108.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA20943; Sat, 1 Apr 1995 19:24:11 -0800 Received: from localhost.dis.org.0.0.127.IN-ADDR.ARPA (localhost.dis.org.0.0.127.IN-ADDR.ARPA [127.0.0.1]) by merde.dis.org (8.6.11/8.6.11) with SMTP id TAA29839; Sat, 1 Apr 1995 19:23:17 -0800 Message-Id: <199504020323.TAA29839@merde.dis.org> X-Authentication-Warning: merde.dis.org: Host localhost.dis.org.0.0.127.IN-ADDR.ARPA didn't use HELO protocol To: current@FreeBSD.org cc: freebsd-questions@FreeBSD.org Subject: wd0: interrupt timeout X-Phone: (510) 849-2230 X-Snail-address: 2560 Bancroft way #51;Berkeley CA 94704-1700 X-Geek: GCS d--(-), p, c+++, l-, u+, e+, m* s++/+, n- h++ f+ g+ w+ t+ r y++ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29834.796792995.1@merde.dis.org> Date: Sat, 01 Apr 1995 19:23:16 -0800 From: Pete Shipley Sender: current-owner@FreeBSD.org Precedence: bulk When I upgraded from 2.0-950210-SNAP to 2.0-950322-SNAP I started getting kernel panics during boot (thus went back to 2.0-950210-SNAP). now when I use -current I get the following: wd0: interrupt timeout: wd0: status 58 error 0 wd0: interrupt timeout: wd0: status 59 error 4 wd0: interrupt timeout: wd0: status d0 error 4 wb0b: wdstart: timeout waiting to give command writing fsbn 840 or 840-863 (wd0bn 49992; cn 82 tn 3 sn 22) wd0: wdunwedge failed:o and the system seem to hang, I have to power cycle the system to reboot, if I just hit the reset switch it will not boot. -Pete From owner-freebsd-current Sat Apr 1 22:38:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA24451 for current-outgoing; Sat, 1 Apr 1995 22:38:57 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA24444; Sat, 1 Apr 1995 22:38:56 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Justin T. Gibbs" cc: Garrett Wollman , steve@simon.chi.il.us (Steven E. Piette), current@FreeBSD.org Subject: Re: Ethernet interface AUI, UTP and BNC ports In-reply-to: Your message of "Thu, 09 Mar 95 14:23:30 PST." <199503092223.OAA00478@estienne.cs.berkeley.edu> Date: Sat, 01 Apr 1995 22:38:56 -0800 Message-ID: <24443.796804736@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Can you give a rough outline of the work needed so that others can start > it if you don't have the time? I'm so sick of answering the link2 questions, > that I'd like to make this happen as soon as possible. What's the story with this? Jordan From owner-freebsd-current Sat Apr 1 22:46:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA24562 for current-outgoing; Sat, 1 Apr 1995 22:46:26 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA24556 for ; Sat, 1 Apr 1995 22:46:25 -0800 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id WAA14076; Sat, 1 Apr 1995 22:44:50 -0800 Message-Id: <199504020644.WAA14076@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: Garrett Wollman , steve@simon.chi.il.us (Steven E. Piette), current@FreeBSD.org Subject: Re: Ethernet interface AUI, UTP and BNC ports In-reply-to: Your message of "Sat, 01 Apr 1995 22:38:56 PST." <24443.796804736@freefall.cdrom.com> Date: Sat, 01 Apr 1995 22:44:49 -0800 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >> Can you give a rough outline of the work needed so that others can start >> it if you don't have the time? I'm so sick of answering the link2 questions >, >> that I'd like to make this happen as soon as possible. > >What's the story with this? > > Jordan I don't have time to do it. There was someone else that was interested in doing it. -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Sat Apr 1 23:37:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA25485 for current-outgoing; Sat, 1 Apr 1995 23:37:58 -0800 Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA25479 for ; Sat, 1 Apr 1995 23:37:56 -0800 Received: (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.11/PHILMAIL-1.11) id XAA22717; Sat, 1 Apr 1995 23:37:42 -0800 Date: Sat, 1 Apr 1995 23:37:40 -0800 From: Richard Chang To: FreeBSD-current@freefall.cdrom.com Subject: sup not working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk I can't get sup working when I switch from slip to ppp earlier today while everything under ppp works fine. Is the supserver at freefall down or is something wrong on my end? This is all I get... bigbang# sup -vzo supfile SUP 8.26 (4.3 BSD) for file supfile at Apr 1 23:37:42 It just sits here and does nothing afterwards... Thanks for any help in advance! --richardc